Capabilities Inventory and Attributes

Enterprise Architecture depends on this inventory as the primary lens through which it describes the current and target state of the enterprise. The Capability Map — derived from this inventory — is the stable, agreed-upon vocabulary for describing what the enterprise does. Without it, architectural assessments, target state designs, and roadmaps are built on informal and inconsistent terminology. Enterprise Architecture uses this inventory to identify capability gaps, define the target capability state, and build roadmaps that connect technology change to business capability improvement. Every inventory contributes to the Enterprise Model; the Capabilities Inventory contributes the business lens through which all other Enterprise Model nodes are interpreted.

Application Portfolio Management (APM) depends on this inventory for investment discipline. Without the Capabilities Inventory as the bridge between applications and outcomes, portfolio rationalization decisions are made on technical criteria alone — cost, age, and redundancy — rather than on business impact. With it, APM can answer: what happens to our ability to perform Capability X if we retire Application Y? Which Capabilities are supported by a single application, creating single-point-of-failure exposure? Which Capabilities have no supporting applications, representing technology portfolio gaps? Which Capabilities are over-served by redundant application investments, surfacing rationalization opportunities?

Technology Portfolio Management (TPM) depends on this inventory to govern technology investment by capability priority. Without the Capabilities Inventory, technology investment decisions are made technology-first rather than capability-first. With it, TPM can direct investment toward technologies that enable high-priority, high-gap Capabilities and away from technologies that support Capabilities the enterprise has decided to disinvest. The Investment Priority and Assessed Maturity attributes are the primary inputs to TPM’s rationalization model.

The Enterprise Model depends on this inventory as the governing layer that connects organizational intent to organizational execution. Capabilities form the most connected Noun Type in the Enterprise Model graph, participating in typed relationships with Applications, Value Streams, Organizational Units, Data and Information Types, IT Portfolios, Processes, Vendors, and Regulatory Obligations. These relationships make the Capability the hub through which AI agents can traverse from business strategy to technology execution to compliance posture in a single path. Capability-anchored queries are how the Enterprise Model answers cross-cutting questions that no single inventory can answer alone.