Services Inventory and Attributes - Understand what the Services Inventory governs
Services Inventory and Attributes
Chapter 3. Understand what the Services Inventory governs
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Eight-Point Service Definition | The structural criteria that distinguish a governed Service from an informal activity, an Application, a Process, or a catalog placeholder — the foundation of inventory inclusion. |
| Boundary Discipline | A Service is not an Application (which enables Services), not a Process (which exercises Services), not a Capability (which Services realize), and not a Service Record (which is one transaction of a Service). |
| Inclusion Threshold | A catalog entry without defined ownership, expectations, inputs, outputs, and supporting tools is a placeholder — not a Service — and should be excluded or upgraded before it enters the inventory. |
Quick Q&A
Question: Why does this inventory exclude undefined or informal activities that practitioners call "services"?
Question: What happens when an Application that the enterprise already governs also gets called a Service?
Read More Below
The Services Inventory governs every Service the enterprise has chosen to govern as a managed value-delivery asset — every named, owned, defined offering that meets the criteria of a governed Service per the IF4IT Single Service Definition Pattern. A governed Service has a clearly identified and accountable Service Owner; a clearly defined purpose and description; clearly defined performance expectations consisting of Service Indicators, Service Objectives, and Service Agreements; clearly defined inputs and outputs; a clearly defined Service Manager; clearly defined Service Providers / Service Actors; and clearly defined supporting tools and technologies. A Noun Instance in this inventory is a single Service — not a Service Request, a Service Record, a Service Ticket, an Application, a Capability, or a Process. The inventory governs Service definitions; the operational systems of record govern Service transactions and Service performance.
Services that do not meet the eight-point Service Definition criteria do not belong in this inventory. An informal team activity is not a Service. An application that has not been deliberately exposed as a governed Service is not a Service — it is an enabling asset that may participate in one or more Services. A process that orchestrates work without an accountable Service Owner is not a Service — it is a Process governed by the Processes Inventory. A Service Catalog entry is not automatically a governed Service; if it has been published without the eight definitional elements in place, it is a placeholder, not a Service. The Services Inventory governs the Services the enterprise has actually defined, owned, and committed to govern — not the broader set of activities, applications, or processes that practitioners may informally call “services.”
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. Understand what the Services Inventory governs | Services Inventory and Attributes. https://if4it.org/best-practices/services-inventory-and-attributes/understand-what-the-services-inventory-governs/ (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