Capabilities Inventory and Attributes - Relationship Attributes for the Capabilities Inventory

Capabilities Inventory and Attributes

Chapter 29. Relationship Attributes for the Capabilities Inventory

Relationship attributes connect each Capability to related Noun Instances in other inventories, forming the edges of the Enterprise Model graph for the Capability Noun Type.

Every attribute in this category is Calculated or Derived from records in other inventories. No manual data entry is required for any attribute in this category. Do not create data entry fields for any attribute listed here.

Attribute Name	Maturity	Description and Notes
Supporting Applications [Multi-Value]	Run	Description — The Applications that support or enable this Capability, referenced by Semantic ID from the Applications Inventory. Benefit(s) — The primary cross-inventory relationship for capability-driven portfolio governance. Source — Derived Notes — Derived from the Applications Inventory: when an Application record references this Capability, that Application’s Semantic ID is reflected here.
Parent Value Streams [Multi-Value]	Run	Description — The Value Streams that this Capability composes or contributes to, referenced by Semantic ID from the Value Streams Inventory. Benefit(s) — Connects the capability map to the enterprise value delivery model. Source — Derived Notes — Derived from the Value Streams Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Owning Organizational Units [Multi-Value]	Run	Description — The Organizational Units that own and perform this Capability, referenced by Semantic ID from the Organizational Units Inventory. Benefit(s) — Maps organizational accountability to the capability map. Source — Derived Notes — Derived from the Organizational Units Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Related IT Portfolios [Multi-Value]	Run	Description — The IT Portfolios that govern investments in this Capability area, referenced by Semantic ID from the IT Portfolios Inventory. Benefit(s) — Connects capability governance to portfolio governance. Source — Derived Notes — Derived from the IT Portfolios Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Related Processes [Multi-Value]	Run	Description — The Processes that operationalize this Capability — the sequenced activities that realize the Capability’s outcomes in practice. Referenced by Semantic ID from the Processes Inventory. Benefit(s) — Connects the stable Capability layer to the volatile Process layer. Surfaces which Capabilities are realized by which sequenced workflows. Source — Derived Notes — Derived from the Processes Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Related Vendors [Multi-Value]	Run	Description — The Vendors whose products or services materially support delivery of this Capability, referenced by Semantic ID from the Vendors Inventory. Benefit(s) — Surfaces vendor dependencies at the capability level — beyond what the Outsourcing Provider attribute captures for fully outsourced delivery. Source — Derived Notes — Derived from the Vendors Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Related Regulatory Obligations [Multi-Value]	Run	Description — The Regulatory Obligations to which this Capability is subject, referenced by Semantic ID from the Regulatory Obligations Inventory. Benefit(s) — Connects the capability map to the structured regulatory obligation register, complementing the descriptive Regulatory Obligations attribute in the Compliance and Regulatory Attributes category. Source — Derived Notes — Derived from the Regulatory Obligations Inventory when published. Refer to the IF4IT Enterprise Inventory Management Best Practices document.
Child Capabilities [Multi-Value]	Run	Description — All direct child Capabilities of this Capability in the hierarchy. Benefit(s) — Enables hierarchical navigation of the capability map from any node without traversing the full hierarchy. Source — Calculated Notes — Calculated from within the Capabilities Inventory itself. Self-referential relationship.

Legal Disclaimers