Understand how the Capabilities Inventory relates to other inventories

The Capabilities Inventory has a direct seeding relationship with the Applications Inventory and Attributes. Applications support Capabilities — every Application record references one or more Capabilities it enables. The Capabilities Inventory is authoritative for Capability definitions; the Applications Inventory is authoritative for Application records and for the specific mapping of Applications to Capabilities. The connecting attribute is the Capability Semantic ID, carried in the Applications Inventory’s Supported Capabilities attribute.

The Capabilities Inventory feeds the Value Streams Inventory (not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition in the Noun Type taxonomy). Value Streams are composed of Capabilities. A Value Stream record will reference the Capabilities it orchestrates to deliver value to a customer or stakeholder.

The Capabilities Inventory connects to the Organizational Units Inventory (not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document). Organizational Units own and perform Capabilities. This relationship — captured in the Capabilities Inventory through both the Owning Organization and Service Organization attributes in the Ownership and Stakeholder category, and through the Owning Organizational Units derived attribute in the Relationship Attributes category — is the primary accountability and operational-delivery mapping in the Enterprise Model.

The Capabilities Inventory connects to the Data and Information Inventory and Attributes. Capabilities consume input data and produce output data, captured in this inventory’s Data and Information Attributes category. The Data and Information Inventory governs the Data and Information Types that flow through Capabilities, and the connecting attribute is the Capability Semantic ID, referenced from data and information records in the Data and Information Inventory.

The Capabilities Inventory informs the IT Portfolios Inventory (not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document). IT portfolio investment decisions are most defensible when grounded in capability priority and maturity assessment.

The Capabilities Inventory connects to the Processes Inventory (not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document). Processes operationalize Capabilities — a Process describes the sequenced activities that realize a Capability’s outcomes in practice. The Capability is the stable outcome; the Process is the volatile method.

The Capabilities Inventory connects to the Vendors Inventory and Attributes. Vendors materially support delivery of Capabilities through products, services, and outsourced work. This relationship complements the Outsourcing Provider attribute in the Vendor and Supplier Attributes category by capturing the full set of vendor relationships beyond fully outsourced delivery.

The Capabilities Inventory connects to the Regulatory Obligations Inventory (not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document). Regulatory Obligations bind Capabilities — when a regulation creates an enterprise obligation, that obligation is materially performed within one or more Capabilities. This relationship complements the Regulatory Obligations attribute in the Compliance and Regulatory Attributes category by linking to the structured obligation register rather than capturing obligation text descriptively.