Application portfolio management for enterprise architects
Application portfolio management (APM) is the enterprise architecture discipline of inventorying every application a firm runs, scoring each against business value and technical fit, and making explicit invest/migrate/tolerate/eliminate decisions. This page shows the APM cycle as a BPMN 2.0 process map - the Gartner TIME framework as a working flow rather than a quadrant chart.
By Jack Finnegan ยท Updated 21 May 2026
What application portfolio management actually is
The CMDB has 4,000 entries and none of them say which capability they support
Four pieces of a working APM programme
Application inventory
A single inventory across all sources (CMDB, procurement, finance, shadow IT discovery). Without a clean inventory, scoring is fiction.
Scoring (TIME)
Business value on one axis, technical fit on the other, with the categories (tolerate, invest, migrate, eliminate) falling out of the quadrant the application lands in.
Capability mapping
Attach every application to one or more business capabilities so duplication and gaps surface at portfolio level rather than per-application.
Decisions and execution
The point of APM is to produce decisions that feed into the modernization programme. Without explicit decisions and an execution path, the portfolio chart is theatre.
APM as a process map
The end-to-end APM cycle - inventory, score, group by capability, decide, plan retirement vs invest/migrate/tolerate plan, execute, monitor.
Application portfolio management as a process map
Application portfolio management (APM) rendered as a BPMN 2.0 process. The flow inventories applications, scores each against the Gartner TIME framework (tolerate, invest, migrate, eliminate), groups by business capability, decides per-application actions, and feeds back into the modernization programme.
- Inventory applications - the current as-is portfolio plus the in-flight build pipeline.
- Score each application against business value and technical fit (TIME: tolerate, invest, migrate, eliminate).
- Group applications by business capability so duplication and gaps are visible.
- For each application, decide an action: tolerate, invest, migrate, or eliminate.
- If eliminate is the decision, plan retirement. Otherwise issue the recommendation to the modernization programme.
- Execute, monitor outcomes against the portfolio score, and re-run the review on an agreed cadence.
Frequently asked questions
What is application portfolio management?
Application portfolio management (APM) is the enterprise architecture discipline of treating the firm's application estate as a portfolio - making explicit, time-bounded decisions about which applications to invest in, which to migrate to new platforms, which to merely tolerate, and which to eliminate. The discipline produces a portfolio view (often using Gartner's TIME framework) that enterprise architecture, IT finance, and the transformation office use to drive modernization decisions.
What is the Gartner TIME framework?
TIME is the canonical APM scoring framework Gartner published: Tolerate (keep as-is, low value but no urgent need to change), Invest (high business value and good fit, deepen the investment), Migrate (high value but poor fit, move to a better platform), Eliminate (low value and poor fit, decommission). Each application falls into one of the four quadrants of a business-value vs technical-fit chart, and the quadrant dictates the action.
What is the difference between APM and a CMDB?
A CMDB (configuration management database) is an IT-facing inventory of configuration items - applications, servers, network devices, services - and their relationships. APM is a business-facing portfolio view that scores applications against business value and technical fit and groups them by business capability. The CMDB is one input to APM but not a substitute - the CMDB tells you what you have; APM tells you what to do about it.
How does APM relate to application modernization?
APM produces the decision; modernization executes it. The TIME score says "this application should migrate" or "this application should be eliminated"; the modernization programme then picks the seven-Rs strategy and runs the migration. Without APM, modernization decisions are made one application at a time without portfolio context; without modernization, APM produces decisions that never get executed.
How does process mapping fit into APM?
Process maps make capability mapping concrete. To map an application to a capability you need to see the processes the application supports - and a BPMN process map showing the steps, decisions, and handoffs is the artefact that lets enterprise architecture, the business owner, and the application owner agree on what the application actually does. APM that operates only on application names and short descriptions misses duplication that is visible only at the process level.
Does BA Copilot replace ServiceNow APM / SAP LeanIX / Bizzdesign Hopex?
No. BA Copilot is the modelling layer - it produces the process maps and capability maps that feed the APM platforms. ServiceNow APM (rebranded ServiceNow Enterprise Architecture in the Xanadu release, September 2024), SAP LeanIX (acquired by SAP in 2023), Bizzdesign Hopex (post the 2024-2025 Bizzdesign-MEGA-Alfabet merger), and Ardoq own the portfolio data model, the scoring workflow, and the dashboards. BA Copilot integrates by producing the BPMN diagrams those platforms can embed alongside their portfolio views.
14 Years in BPMN
I'm Jack Finnegan. I've spent fourteen years working hands-on with BPMN, as an analyst, an engineer, and a product director, where I felt every sharp edge of legacy business process platforms.
BA Copilot is the platform I wanted on every one of these projects: AI-first process management, which treats BPMN as a first-class output rather than an export afterthought.
Turn the application list into a portfolio
Open the APM lifecycle template, score your applications on TIME, and produce the BPMN process maps that make capability mapping defensible.