SAF and ITIL Version 5
Nature and status of the approach
ITIL® Version 5 is PeopleCert's current guidance line for managing digital products and services. As of the analysis date, the release is being introduced in stages; ITIL 4 remains available, and existing knowledge and certifications continue to be recognized. Version 5 is the baseline for this comparison, while ITIL 4 is used only to explain transition.
Purpose and audience
ITIL helps organizations create value through digital products and services across their lifecycle. Its audience includes executives, product and service owners, service management, delivery, operations, support, development, and transformation teams.
Management scope and unit
Version 5 considers digital products and services, their lifecycle, value streams, practices, governance, and continual improvement. SAF does not introduce Product into its core: a product may group services and connect them to an investment or market package. A SAF Service remains a meaningful outcome for its recipient.
Concepts and SAF mappings
| ITIL Version 5 | Nearest concept in SAF | Type / confidence | Boundary |
|---|---|---|---|
| Service | Service | Direct / high | ITIL details value co-creation and service relationships. |
| Service offering | Service plus a variant of terms and channels | Composite / medium | Offering is not introduced as a new core type. |
| Digital product | Grouping of services, systems, components, and investments | Composite / medium | This is a management boundary distinct from a SAF System. |
| Stakeholder, consumer, customer, user | Actor with a role | Partial / high | SAF intentionally consolidates role types. |
| Value stream | Chain of processes, capabilities, and outcomes | Composite / medium | A value stream is not a single process. |
| Management practice | Capability, processes, actors, and external resources | Composite / high | A practice is broader than a process. |
| Information and technology dimension | Information objects, applications, and infrastructure | Composite / medium | A dimension is an area of consideration, not an object. |
Relationships
ITIL connects the provider, consumers, and stakeholders through value co-creation. A product enables a provider to form one or more service offerings; value streams and practices organize lifecycle work. In SAF, these relationships translate into the chain “an Actor receives a Service through a Channel,” “a Process realizes a Service,” “a Process requires a Capability,” and “a System supports a Capability.”
Lifecycle and organization of work
The public description of Version 5 covers discovery, design, build, transition, operation, delivery, support, and continual improvement of digital products and services. These activities should not be modeled as states of one component. SAF stores the current or target arrangement, while ITIL manages the flow of work between states.
Roles and governance
ITIL uses roles and responsibilities in product and service teams, governance, and stakeholder relationships. SAF links an owner to an object, but it does not replace the responsibility model, team organization, or authority for approving a change.
Measures, maturity, and adaptation
Version 5 emphasizes outcomes, cost, risk, experience, resilience, and continual improvement. A measure remains a possible management extension to SAF: the core only needs a link to its definition and an aggregated state. SAF maturity levels are not equivalent to the ITIL Maturity Model.
Using the approaches together
SAF provides architectural traceability for a service; ITIL organizes its lifecycle and ways of working. A practical contract includes a stable service_id, a service offering link to the SAF Service, a product link to a set of services and systems, and operational-record links to the service and affected configuration.
Mapping limitations
Detailed official ITIL materials are licensed. This analysis uses public PeopleCert pages and does not reproduce definitions, diagrams, practice lists, or restricted content. The staged release of Version 5 means that this page should be reviewed when its public structure changes.