Integrations Inventory and Attributes - Relationship attributes for the Integrations Inventory

Integrations Inventory and Attributes

Relationship attributes for the Integrations Inventory

Relationship attributes connect each Integration to related Noun Instances in other inventories, forming the edges of the Enterprise Model graph for the Integration 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
Source Inventory Reference	Run	Description — The Semantic ID of the source entity in its governing Noun Type inventory — the formal cross-inventory reference connecting this integration record to the source entity’s authoritative record. Benefit(s) — Enables bidirectional traversal: from the source entity’s inventory record to all integrations it participates in as a source. Feeds integration count metrics into the source entity’s governing inventory as a Calculated attribute. Source — Derived. Notes — Derived from the governing inventory for the Source Entity Type. When Source Entity Type = Application, this references the Applications Inventory. When Source Entity Type = Database, this references the Data Stores Inventory, and so on.
Target Inventory Reference	Run	Description — The Semantic ID of the target entity in its governing Noun Type inventory — the formal cross-inventory reference connecting this integration record to the target entity’s authoritative record. Benefit(s) — Enables bidirectional traversal from the target entity’s inventory record to all integrations it participates in as a target. Integration count from the target side is a key indicator of target system coupling. Source — Derived. Notes — Mirrors Source Inventory Reference. Derived from the governing inventory for the Target Entity Type.
Related Capabilities [Multi-Value]	Run	Description — The business Capabilities that this integration enables or supports, referenced by Semantic ID from the Capabilities Inventory. Benefit(s) — Connects the integration map to the capability map. Enables capability-level integration dependency analysis: which capabilities would be impaired if this integration failed? Source — Derived. Notes — Derived from the Capabilities Inventory when published.
Related Software Technologies [Multi-Value]	Run	Description — The Software Technology records in the Software Technologies Inventory that implement or support this integration, referenced by Semantic ID. Benefit(s) — The Integration Technology attribute at Crawl maturity seeds this derived relationship at Run maturity. Enables TPM to query: which integrations depend on this technology? How many integrations are affected by a planned technology retirement? Source — Derived. Notes — Derived from the Software Technologies Inventory. Every distinct Integration Technology value across all integration records nominates a Software Technology record.
Related Data Sensitivity Types [Multi-Value]	Run	Description — The formal Data Sensitivity Type records from the Data Sensitivity Types Inventory that correspond to the values in the Data Sensitivities attribute. Benefit(s) — Connects the per-integration sensitivity tagging to the governed Data Sensitivity Types taxonomy. Enables enterprise-level queries: how many integrations carry PII? Which PII-carrying integrations lack encryption? Source — Derived. Notes — Derived from the Data Sensitivity Types Inventory when published.
Upstream Integrations [Multi-Value]	Run	Description — Integration records in this inventory that must successfully complete before this integration can execute — the dependencies this integration has on other integrations. Benefit(s) — Produces the full integration dependency graph. When an upstream integration fails, this attribute immediately identifies all downstream integrations that are blocked or at risk. Source — Calculated. Notes — Self-referential within the Integrations Inventory. Calculated from integration orchestration metadata or pipeline definitions.
Downstream Integrations [Multi-Value]	Run	Description — Integration records in this inventory that depend on this integration’s successful completion — what this integration feeds. Benefit(s) — The mirror of Upstream Integrations. Together, Upstream and Downstream produce the complete integration dependency graph — the enterprise’s hidden complexity map. Source — Calculated. Notes — Self-referential within the Integrations Inventory. Calculated from integration orchestration metadata or pipeline definitions.

Legal Disclaimers