5.2 The Service Value Chain and Its Six Activities

The Service Value Chain as an Operating Model

The service value chain (SVC) is the central element of the service value system. AXELOS describes it as "an operating model which outlines the key activities required to respond to demand and facilitate value realization through the creation and management of products and services."

The value chain is flexible: its activities can be combined in many sequences, and each can draw on different practices and resources depending on the situation. This is what lets one operating model handle everything from a routine service request to a major new product launch. The SVC takes demand and opportunity in, and through its activities produces products and services that deliver value.

The Foundation exam expects you to know the six activities by name and to know the purpose of each one. They are not steps in a fixed order — "value chain" here does not mean a strict pipeline. Instead, the six activities interconnect, each receiving inputs and creating outputs that may feed any of the others.

The value chain matters because it is the part of the SVS that actually does the work of converting demand into value. The guiding principles and governance steer the organization, and continual improvement keeps it healthy, but it is the value chain — supported by the practices — that performs the concrete activities required to create, deliver, and improve services. Every product or service an organization offers is produced by some path through these same six activities, which is why understanding them is foundational to understanding ITIL 4 as a whole.

The Six Value Chain Activities

A helpful way to remember the set is the phrase "Plan, Improve, Engage, Design, Obtain, Deliver." Note that plan and improve apply across the whole chain (they are about direction and betterment of everything), whereas engage, design and transition, obtain/build, and deliver and support describe the flow of work from understanding a need to running the live service.

How the Activities Interconnect

Each activity transforms inputs into outputs. For example, engage turns customer and stakeholder demand into a clear understanding of requirements; design and transition turns those requirements (plus product specifications) into new or changed services ready for use; obtain/build turns specifications and contracts into the service components needed; and deliver and support turns those components and user requests into ongoing service and user support.

Plan feeds direction into all of them, and improve receives information from all of them — performance data, feedback, and improvement opportunities — and pushes betterment back out.

Because the activities exchange inputs and outputs in many directions, the SVC is not linear. The same six activities are reused over and over, recombined to suit each kind of work the organization faces. This reuse and recombination is exactly what makes the value chain a powerful, adaptable operating model rather than a rigid sequence of steps.

Distinguishing the Activities the Exam Confuses

Foundation candidates lose marks by mixing up activities with similar-sounding purposes. Use these distinctions:

• Plan vs Improve: Both span the whole chain, but plan is about setting a shared vision, status, and direction across the four dimensions; improve is about ongoing betterment of products, services, and practices. Plan looks forward to where you intend to go; improve continually raises the bar everywhere.
• Engage vs Deliver and support: Engage is about understanding stakeholders and maintaining relationships (it faces outward to customers, users, suppliers, and partners); deliver and support is about running the live service and providing user support day to day.
• Design and transition vs Obtain/build: Design and transition ensures a new or changed service meets expectations for quality, cost, and time to market and is ready for live use; obtain/build ensures the components (whether built in-house or procured) are available where and when needed and meet specification.

Inputs and Outputs Are Everywhere

A defining feature of the value chain is that every activity both receives inputs and creates outputs, and any activity's output can become another's input. For instance, improvement opportunities surfaced by deliver and support feed improve; product and service requirements from engage feed design and transition and plan; and new service components from obtain/build feed design and transition and deliver and support. There is no single fixed start or end point.

This many-to-many flow is precisely why ITIL calls the value chain an operating model rather than a process: it describes a set of capabilities that the organization arranges and rearranges to meet whatever demand arrives, which is what gives the SVS its flexibility and its resistance to siloed working.