SAF and ITSM
Nature and status of the approach
IT Service Management is a field of practice for managing IT services, not a single standard, product, or metamodel. ITIL, ISO/IEC 20000, and FitSM formalize this field in different ways. This page therefore uses the common ground of official public descriptions rather than a “canonical ITSM object.”
Purpose and audience
ITSM helps a provider organize the creation, delivery, support, and improvement of services according to consumer needs. Its audience includes service and process owners, the service desk, operations, development, suppliers, IT leaders, and service consumers.
SAF serves architects and company participants who need a shared business, application, and infrastructure model. The approaches intersect around a service and the chain that realizes it.
Management scope and unit
ITSM's primary unit is the service and its delivery relationship. A particular practice additionally manages service offerings, the catalog, service levels, configuration, assets, requests, incidents, problems, changes, releases, and knowledge.
A SAF service describes a meaningful outcome for a recipient. It is a sound architecture anchor but does not replace a service offering with variants, price, support hours, and an SLA.
Concepts and SAF mappings
| ITSM concept | Closest SAF concept | Type / confidence | Boundary |
|---|---|---|---|
| Service | Service | Direct / high | ITSM usually details terms, support, and provider-consumer relationships. |
| Consumer, customer, user | Actor | Partial / high | Roles are distinguished through attributes or an external role model. |
| Contact point, service desk, portal | Channel and actor | Composite / medium | A channel does not include the team and its accountability. |
| Practice or process | Process and capability | Composite / medium | A practice includes people, knowledge, partners, and technology, not only a work sequence. |
| Service configuration | System, component, deployment, resource, and their relationships | Composite / high | A CI is a management role, not a new universal architecture type. |
| Operational record | Information object as data | Not applicable / medium | A record does not become an independent SAF architecture object. |
Relationships
The minimum bridge runs from actor to service and channel, then through process and capability to the system and its components. ITSM adds “offering belongs to service,” “level is set for service,” “CI supports service,” “record affects service or CI,” and “change modifies managed configuration.”
Lifecycle and organization of work
ITSM covers planning, design, transition, delivery, support, and improvement. Specific approaches may express these through processes, practices, or value streams. SAF retains a durable picture and should not become a journal of every step. Operational changes update SAF only when an architecture-significant fact changes.
Roles and governance
Common roles include provider, consumer, customer, user, sponsor, service owner, process owner, and practitioner. SAF represents all of them as actors with different roles. Authority over a lifecycle is expressed through an “owns” relationship, while operational assignment remains in the external work system.
Measures, maturity, and tailoring
ITSM measures outcomes, quality, availability, response and recovery times, satisfaction, volume, and work flow. SAF can reference a measure definition and aggregated state without storing every measurement. ITSM maturity cannot be renamed as SAF levels: SAF levels assess relationship completeness and architecture-model governance.
Using the approaches together
- SAF defines the stable service identifier and its architecture realization chain.
- The service catalog specializes the offering, terms, and target consumers.
- The CMDB maps CIs to SAF objects through a separate mapping rule.
- Operational records reference the service and CIs.
- Aggregated operational facts help validate architecture decisions.
Mapping limitations
ITSM is not one organization or specification. Terminology differs across ITIL, ISO/IEC 20000, FitSM, tools, and local processes. The mappings on this page are analytical common ground and do not demonstrate SAF compatibility with a particular implementation.