Integrations Inventory and Attributes

Integrations enable Capabilities — many business capabilities depend on data flowing from one system to another to function. An Invoice Processing capability requires integration flows that deliver supplier invoices from procurement systems to accounts payable systems. A Customer Onboarding capability requires integration flows that distribute customer data to CRM, ERP, and identity management systems. The Integrations Inventory documents which integrations support which capabilities through its Related Capabilities relationship attribute.

The connecting attribute is the Capability Semantic ID referenced in the Related Capabilities relationship attribute of integration records. The Capabilities Inventory and Attributes is published and available. When this relationship is maintained, capability-level impact analysis becomes possible: if a specific integration fails, which capabilities are impaired? If an integration must be retired, which capabilities require alternative data flow paths before retirement can proceed?

When established at Run maturity, this relationship enables a complete capability-to-integration dependency view in the Enterprise Model. Business leaders can understand the integration infrastructure their capabilities depend on; integration architects can understand the capability implications of integration changes. This connection is one of the primary ways the Integrations Inventory strengthens the APM and Enterprise Architecture disciplines simultaneously.