Services Inventory and Attributes

Realizing Applications

[Multi-Value]

Description — The Applications that enable this Service. References the Applications Inventory by Semantic ID. Aligns with the eighth element of the IF4IT Single Service Definition Pattern (supporting tools and technologies) and with the IF4IT Service Management Best Practices guidance that Applications enable Services.

Benefit(s) — Connects Services to Applications in the Enterprise Model. Enables APM-led impact analysis: when an Application changes, which Services are affected? Supports Service Owner awareness of Application dependencies.

Source — Manual.

Examples — APP-CRM-SALESFORCE, APP-IAM-OKTA, APP-ITSM-SERVICENOW

Notes — Refer to the IF4IT Applications Inventory and Attributes document for Application governance. The IF4IT Service Management Best Practices document is explicit that Applications are not automatically Services — this attribute records the enabling-relationship between governed Applications and the Service.

Realizing Technologies

[Multi-Value]

Description — The Technologies the Service depends on, beyond the Applications already captured in Realizing Applications. References the Software Technologies Inventory by Semantic ID where the technology is governed there. Aligns with the eighth element of the IF4IT Single Service Definition Pattern.

Benefit(s) — Connects Services to Technologies in the Enterprise Model. Enables TPM-led impact analysis: when a Technology reaches end-of-life or is rationalized, which Services are affected? Supports Service Owner awareness of underlying Technology dependencies.

Source — Manual.

Examples — TECH-DB-POSTGRES, TECH-MSG-KAFKA, TECH-RUNTIME-NODE

Notes — Refer to the IF4IT Technology Portfolio Management Best Practices document for Technology governance. For technologies governed in the Software Technologies Inventory or related Technology inventories, reference by Semantic ID.

Realizing Integrations

[Multi-Value]

Description — The Integrations the Service depends on. References the Integrations Inventory by Semantic ID.

Benefit(s) — Connects Services to the Integrations Inventory, enabling impact analysis when integrations change. Supports troubleshooting Service degradation traceable to integration health.

Source — Manual.

Examples — INT-CRM-TO-BILLING, INT-IAM-TO-EMAIL

Notes — Refer to the IF4IT Integrations Inventory and Attributes document for Integration governance.

Description — The hosting model under which the Service operates. Drives Service-level governance choices for security, compliance, and operational continuity.

Benefit(s) — Enables cloud-portfolio analysis: which Services run where, and where does cloud dependency concentrate? Supports cloud strategy and risk decisions informed by Service-level data.

Source — Manual.

Examples — On-Premise, Private Cloud, Public Cloud (AWS), Public Cloud (Azure), Public Cloud (GCP), Hybrid, Multi-Cloud

Notes — Valid values include the public cloud provider where Public Cloud is the model. Hybrid indicates a Service that operates across on-premise and cloud; Multi-Cloud indicates a Service that operates across multiple public clouds.

Description — Whether and how the Service exposes an API. For Services that expose APIs, references the APIs Inventory by Semantic ID where the API is governed there.

Benefit(s) — Connects technology-delivered Services to the API governance discipline. Enables consumer-facing API governance and supports API rationalization decisions.

Source — Manual.

Examples — No API; REST API (API-CUSTOMER-LOOKUP-V1); GraphQL API; gRPC API; Event-Driven API

Notes — For Services with no API surface, record "No API". For Services with multiple APIs, reference all in Notes. Refer to the planned APIs Inventory for API governance.