SAF and FitSM
Nature and status of the approach
FitSM is a freely available family of lightweight ITSM standards, including support for federated environments. As of the analysis date, version 3.0 is current: FitSM-0 provides the overview and vocabulary, FitSM-1 the requirements, FitSM-2 recommended activities, FitSM-3 the role model, FitSM-4 and FitSM-5 templates and guides, and FitSM-6 capability and maturity assessment.
Purpose and audience
FitSM offers an attainable minimum service-management framework for organizations where a full-scale ITSM program would be disproportionate. It is especially useful for smaller organizations and federations of providers with limited shared hierarchy. This makes FitSM a natural external complement to SAF's Startup and Stable Business profiles.
Management scope and unit
The subject is a lightweight service management system, its processes, roles, and documents. The service and the management work around it remain the main units. The architectural structure of systems and infrastructure is not prescribed in detail and can be represented in SAF.
Concepts and SAF mappings
| FitSM | Nearest concept in SAF | Type / confidence | Boundary |
|---|---|---|---|
| Service and service portfolio | Service and its grouping | Partial / high | A portfolio is a view or external register. |
| Customer, user, service owner | Actor with a role | Partial / high | Role distinctions are retained as attributes. |
| Process | Process and Capability | Composite / medium | A FitSM process includes management responsibilities. |
| Service reporting and documents | Information Object or external artifact | Partial / medium | An operational report does not become a SAF business object. |
| Configuration item | Mapping to multiple SAF types | Composite / high | A CI is not a Component and may represent a Service, System, Deployment, or document. |
| Incident, request, problem, change | External operational record linked to SAF | Not applicable / high | These records are outside the 13 core types. |
Relationships
FitSM operationalizes relationships such as “a service has an owner,” “a consumer uses a service,” “a CI supports a service,” “an incident affects a service or CI,” and “a change modifies configuration.” SAF adds traceability from a service to processes, capabilities, and architectural components.
Lifecycle and organization of work
FitSM specifies requirements and recommended activities for service planning and delivery, relationships, changes, operations, and improvement. These activities should refer to SAF, not be copied into it as a task graph. An architecturally significant result of a change updates the corresponding SAF object or relationship.
Roles and governance
FitSM's role model helps specialize SAF's generic Actor: service owner, process owner, process manager, process executor, and other roles. At a small scale, one person may combine roles without creating duplicate Actor records.
Measures, maturity, and adaptation
FitSM-6 provides a distinct model for assessing process capability and overall ITSM maturity. It does not correspond to the “Catalog — Connected Model — Governed Model” levels. An organization may simultaneously have a governed SAF model and weak operational processes, or a mature service desk and incomplete architectural traceability.
Using the approaches together
An initial implementation only needs to connect the FitSM catalog to stable SAF Service identifiers, assign owners, and identify critical systems. At the connected level, CIs and operational records are added. At the governed level, sources, currency, measures, and change impacts are checked.
Mapping limitations
FitSM is intentionally lighter than other approaches and is not a reduced SAF metamodel. FitSM's stated compatibility with ITIL and ISO/IEC 20000 does not imply that a particular organization automatically conforms to those sources, nor does it extend to SAF.