Integrations Inventory and Attributes

The Integrations Inventory is one of 38 recognized Noun Types in the IF4IT Enterprise Inventory Management taxonomy — the master catalog of all enterprise inventory types. The full taxonomy, its governance principles, and the Inventory of Inventories are documented in the IF4IT Enterprise Inventory Management Best Practices document. Practitioners should read that document to understand how the Integrations Inventory fits within the broader enterprise governance framework.

The six most closely related Noun Types to Integration, with their named relationships: (1) Application — an Application is the most common entity appearing as Source or Target in an Integration; the Integrations Inventory is the primary source of application coupling and dependency data for APM. Refer to the Applications Inventory and Attributes for the published Applications Inventory. (2) Software Technology — the Integration Technology attribute of every Integration record directly seeds and reconciles the Software Technologies Inventory; every distinct integration tool in use enterprise-wide surfaces here first. The Software Technologies Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. (3) Capability — an Integration enables the execution of one or more Capabilities by delivering the data those Capabilities require. The Capabilities Inventory and Attributes is published. (4) Data and Information Type — the Integration Payload maps to one or more Data and Information Types; the Integrations Inventory is the primary source of enterprise data flow lineage. The Data and Information Types Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. (5) Environment — an Integration connects a specific Source Environment to a specific Target Environment; the Integrations Inventory is the primary source of cross-environment data flow governance. The Environments Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. (6) Data Sensitivity Type — the Data Sensitivities attribute on each Integration record maps to formal Data Sensitivity Type records; the Integrations Inventory is the primary source of per-flow sensitivity governance. The Data Sensitivity Types Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document.

The Integration Noun Type is not the same as an Application, a Technology, a Data Type, or a Capability. It is the governed connection between them — the reified relationship that makes the Enterprise Model graph traversable. An integration exists because two entities need to exchange data or information; it disappears when they no longer do. Its identity is defined by what it connects, what it carries, through which technology, and in which environments — not by who built it or which team maintains it.