Services Inventory and Attributes - Relationship attributes for the Services Inventory
Services Inventory and Attributes
Chapter 30. Relationship attributes for the Services Inventory
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Service Group and Portfolio Membership | Service Groups organize related Services operationally; Service Portfolios organize them at the strategic governance level — both per the Service Management Best Practices document. |
| Service Hierarchy | Parent Service, Child Services, and Component Services capture the hierarchical and dependency structure of Services — enabling impact analysis when a parent or component Service is affected. |
| Cross-Inventory Relationships | Related Products, Processes, Contracts, Incidents, Problems, and Service Records connect the Service into the broader Enterprise Model graph. |
| Operational Linkages | Related Service Records is a query reference (not a list of individual transactions) — the operational records themselves live in the ITSM platform. |
Quick Q&A
Question: Why does the Relationship category not duplicate relationships already captured in other attribute categories?
Question: Why is Related Service Records a query reference rather than a list of Semantic IDs?
Read More Below
Relationship attributes capture the cross-Service and cross-inventory relationships that position each Service in the Enterprise Model graph. These relationships enable graph traversal across the enterprise’s typed semantic surface and support impact analysis, dependency mapping, and portfolio reasoning.
| Attribute Name | Maturity | Description and Notes |
|---|---|---|
Service Group Membership [Multi-Value] | Walk | Description — The Service Group(s) this Service belongs to. Service Groups organize related Services by fulfillment responsibility, service area, requester community, operational capability, or business context. Benefit(s) — Connects the Service to its operational grouping. Supports group-level governance and reporting. Source — Manual. Examples — SVCG-ACCESS-MANAGEMENT, SVCG-END-USER-SUPPORT Notes — Services may belong to multiple Groups. Refer to the IF4IT Service Management Best Practices document for Service Group governance. |
Service Portfolio Membership [Multi-Value] | Walk | Description — The Service Portfolio(s) this Service belongs to. Service Portfolios are higher-level governance views across related Services. Benefit(s) — Connects the Service to its portfolio structure. Supports portfolio-level governance, strategy, investment, and lifecycle balance management. Source — Manual. Examples — SVCP-END-USER-SERVICES, SVCP-API-SERVICES Notes — Refer to the IF4IT Service Management Best Practices document for Service Portfolio governance. |
Parent Service [Hierarchical] | Walk | Description — For Services that are children of a broader Service, the Semantic ID of the parent Service. Benefit(s) — Supports hierarchical Service modeling — common for Services that decompose into sub-Services. Source — Manual. Examples — SVC-ONBOARDING-WORKFORCE (parent of SVC-ONBOARDING-EMPLOYEE) Notes — Empty for Services without a parent. |
Child Services [Multi-Value] | Walk | Description — For Services that decompose into sub-Services, the Semantic IDs of the child Services. Benefit(s) — Supports hierarchical Service modeling. Enables parent-level governance of decomposed Services. Source — Manual. Examples — SVC-ONBOARDING-EMPLOYEE, SVC-ONBOARDING-CONTRACTOR Notes — Empty for Services without child Services. |
Component Services [Multi-Value] | Walk | Description — Other Services this Service depends on as components. Benefit(s) — Surfaces inter-Service dependencies. Enables impact analysis when a component Service is affected. Source — Manual. Examples — SVC-IAM-AUTHENTICATION, SVC-EMAIL-DELIVERY Notes — A Service may depend on multiple component Services. Record all material dependencies. |
Related Products [Multi-Value] | Walk | Description — Products this Service is part of or supports. References the planned Products Inventory by Semantic ID. Benefit(s) — Connects Services to Products. Supports joint Product / Service portfolio analysis. Source — Manual. Examples — PROD-CUSTOMER-PLATFORM, PROD-EMPLOYEE-EXPERIENCE Notes — Refer to the planned Products Inventory for Product governance. |
Related Processes [Multi-Value] | Walk | Description — Processes that exercise this Service. References the planned Processes Inventory by Semantic ID. Benefit(s) — Connects Services to Processes. Enables Process owners to understand which Services they depend on. Source — Manual. Examples — PROC-NEW-HIRE-ONBOARDING, PROC-CUSTOMER-SUPPORT Notes — Refer to the planned Processes Inventory for Process governance. |
Related Contracts [Multi-Value] | Walk | Description — Contracts associated with this Service beyond the Governing Contract Reference. References the planned Contracts and Agreements Inventory. Benefit(s) — Captures the full contractual surface around the Service. Supports compliance and contract management. Source — Manual. Examples — CON-SALESFORCE-DPA, CON-SALESFORCE-BAA Notes — For Services governed by multiple contracts (e.g., a Master Services Agreement plus separate Data Processing Agreement and Business Associate Agreement), record all here. |
Related Incidents [Multi-Value] | Walk | Description — Incident records associated with this Service. References the planned Incidents Inventory by Semantic ID. Benefit(s) — Connects Services to historical incidents. Supports incident pattern analysis and Service health assessment. Source — Derived. Examples — INC-2026-0142, INC-2026-0203 Notes — Refer to the planned Incidents Inventory. May be Derived from ITSM platform in mature implementations. |
Related Problems [Multi-Value] | Walk | Description — Problem records associated with this Service. References the planned Problems Inventory by Semantic ID. Benefit(s) — Connects Services to documented Problems. Supports root-cause analysis and Service improvement prioritization. Source — Derived. Examples — PRB-2026-0011, PRB-2026-0023 Notes — Refer to the planned Problems Inventory. |
Related Service Records [Multi-Value] | Walk | Description — A reference to the Service Records system query that returns the operational records for this Service. The Services Inventory does not store individual Service Records — those are governed in the ITSM platform or equivalent system. Benefit(s) — Provides the link from the Service definition to operational Service Record data. Supports auditors and Service Owners in finding the operational record evidence. Source — Manual. Examples — ServiceNow query URL; Jira JQL filter; API Gateway log query Notes — A reference, not a list of individual Service Records. The Service Records themselves live in the operational system. |
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. Relationship attributes for the Services Inventory | Services Inventory and Attributes. https://if4it.org/best-practices/services-inventory-and-attributes/relationship-attributes-for-the-services-inventory/ (accessed 2026-07-23).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers