Applications Inventory and Attributes - Integration Summary attributes for the Applications Inventory

Applications Inventory and Attributes

Integration Summary attributes for the Applications Inventory

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. These attributes are system-populated from the relationship or calculation logic described in each attribute’s Source section. Do not create data entry fields for any attribute in this category.

Integration Summary attributes provide a summary view of each application’s integration profile at the application record level.

Attribute Name	Maturity	Description and Notes
Total Integration Count	Walk	Description — The total number of active integrations — both inbound and outbound — in which this application participates as a source or target entity. Includes all integration types: API, file transfer, message queue, event stream, database link, ETL/ELT, and EDI. Benefit(s) — The single most important proxy for migration complexity and retirement impact. Applications with high integration counts require proportionally greater effort to migrate or retire. Without this count, migration and retirement complexity is consistently and substantially underestimated. Source — Calculated from the Integrations Inventory: count of all Integrations Inventory records where this application's Semantic Identifier appears as either the Source Entity Identifier or the Target Entity Identifier and Lifecycle Status is Active. Examples — 47 (SAP S/4HANA — hub for enterprise financial data), 12 (Salesforce CRM — connected to ERP, marketing, and support systems), 3 (internal wiki — SSO, LDAP, backup only)
Inbound Integration Count	Walk	Description — The number of active integrations delivering data or services into this application from upstream entities. Benefit(s) — Quantifies the number of upstream dependencies the application has — the entities that must be assessed, renegotiated, or replaced when this application is migrated or retired. Source — Calculated from the Integrations Inventory: count of records where this application's Semantic Identifier appears as the Target Entity Identifier and Lifecycle Status is Active.
Outbound Integration Count	Walk	Description — The number of active integrations through which this application delivers data or services to downstream entities. Benefit(s) — Quantifies the number of downstream entities that depend on this application as a data or service source — the entities that will break or lose data if this application is changed or retired without coordinated integration remediation. Source — Calculated from the Integrations Inventory: count of records where this application's Semantic Identifier appears as the Source Entity Identifier and Lifecycle Status is Active.
Integration Criticality Rating	Walk	Description — An assessment of the business criticality of this application's integrations — how severely the failure of integrations connected to this application would affect business operations. Benefit(s) — Determines the resilience, monitoring, and governance requirements for the application's integration estate. Applications with Critical Integration Criticality ratings require integration-level SLAs, active monitoring, and incident response procedures proportionate to the business impact of integration failure. Source — Derived from the Integrations Inventory: the highest Integration Criticality Rating value among all active Integrations Inventory records associated with this application. Notes — Valid values: Low, Medium, High, Critical.
API Exposure Scope	Walk	Description — The scope of the application's API exposure — whether it exposes interfaces for Internal consumption only, External consumption (accessible to internet-facing clients), or Partner consumption (accessible to defined external business partners through governed channels). Benefit(s) — Determines the security governance requirements, change management obligations, and contractual implications associated with the application's interfaces. Externally or partner-exposed APIs carry versioning obligations and consumer notification processes that internal-only APIs do not. Source — Manually Entered. Notes — Valid values: Internal Only, Partner, External, None.
Key Upstream Entity Dependencies [Multi-Value]	Walk	Description — The entities from which this application receives critical data or services — the upstream dependencies whose unavailability or change would impair this application's function. Benefit(s) — Enables chain-of-impact analysis when upstream entities are changed, retired, or experience outages. Applications with undocumented upstream dependencies create surprise dependencies that surface only during incidents. Source — Derived from the Integrations Inventory: the Source Entity Identifiers of all active Integrations Inventory records where this application appears as the Target Entity Identifier and Integration Criticality Rating is High or Critical.
Key Downstream Entity Dependencies [Multi-Value]	Walk	Description — The entities that depend on this application as a data source or service provider — the downstream consumers whose function would be impaired if this application is changed, retired, or experiences an outage. Benefit(s) — The most critical dependency attribute for retirement and migration planning. The downstream impact of retiring or migrating an application is determined entirely by the scope and criticality of its downstream dependencies. Source — Derived from the Integrations Inventory: the Target Entity Identifiers of all active Integrations Inventory records where this application appears as the Source Entity Identifier and Integration Criticality Rating is High or Critical.

Legal Disclaimers