Services Inventory and Attributes

The Services Inventory does not exist in isolation. It connects to other inventories in the IF4IT Enterprise Inventory Management taxonomy through typed, governed relationships that together form the Service-centered portion of the Enterprise Model. The relationships described here are the most important ones; the complete relationship surface is enumerated in the Relationship Attributes category of this document and elaborated in the Relationships to Other Inventories subsection at the end.

The Services Inventory has a foundational relationship with the IF4IT Capabilities Inventory and Attributes. Services realize Capabilities — every governed Service exists to make one or more Capabilities operationally available to a Service Requester Community. The Capability is the standing ability; the Service is the contracted, delivered, governed offering through which that ability becomes accessible. A Capability without any Services realizing it is an unrealized strategic intent; a Service that does not realize a Capability is a misclassified activity. The Services Inventory connects to the Capabilities Inventory through the Capability Realization attribute, enabling enterprise-wide analysis of which Capabilities are well-supported by Services, which are under-served, and where the Service portfolio is misaligned with Capability strategy.

The Services Inventory has a foundational relationship with the IF4IT Applications Inventory and Attributes. Applications enable Services — a single Application may enable many Services, and a single Service may depend on many Applications. The Service Management Best Practices document is explicit that Applications are not automatically Services: an Application is a software solution that runs in an operating environment to support one or more business or technical capabilities, while a Service is a defined, governed offering with its own boundaries, requesters, expectations, and outcomes. The Services Inventory connects to the Applications Inventory through the Realizing Applications attribute, enabling APM to evaluate Application changes through the lens of Service impact and enabling Service Management to evaluate Service health through the lens of Application dependency.

The Services Inventory has a foundational relationship with the IF4IT Vendors Inventory and Attributes. Services consumed from external providers — cloud services, SaaS subscriptions, managed services, professional services — are sourced from Vendors governed in the Vendors Inventory. The Services Inventory connects to the Vendors Inventory through the Primary Vendor and Subcontracted Vendors attributes, enabling joint analysis of Vendor concentration risk at the Service level: which Services depend on which Vendors, which Vendors deliver which Services, and where the enterprise carries concentration risk that would be invisible from either inventory in isolation.

The Services Inventory has a foundational relationship with the Contracts and Agreements Inventory. The Contracts and Agreements Inventory is planned as part of the IF4IT Noun Type taxonomy — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition. Governing Contracts and Service Agreements that establish the legal and commercial terms of consumed Services are the artifacts through which Service-level commitments become contractual obligations. The Services Inventory connects to the Contracts and Agreements Inventory through the Governing Contract Reference and Service Agreement Reference attributes, enabling compliance and contract teams to traverse from any Service to the contracts that govern it and from any contract to the Services it covers.

The Services Inventory has a foundational relationship with the Products Inventory and Attributes. The Products Inventory is planned as part of the IF4IT Noun Type taxonomy — refer to the IF4IT Enterprise Inventory Management Best Practices document for its current definition. Products and Services are peer offerings in many enterprises: a Product may include one or more Services as part of its delivery (post-sale support, professional services, managed services), and a Service may enable or operationalize a Product. The Services Inventory connects to the Products Inventory through the Related Products attribute. The conceptual boundary between Product and Service is settled by enterprise convention rather than IF4IT mandate; many offerings are governed in both inventories with reciprocal relationship attributes.