ITIL 4 Foundation Training Course

The service value system, usually written SVS, describes how all the components and activities of an organization work together as a system to enable value creation. It is ITIL 4's top-level model: everything else in the framework is either a component of the SVS or something a component contains.

The syllabus asks you to describe the SVS, which means knowing three things — what goes into it, what comes out, and what sits inside. Those three take about a paragraph each, and they are worth learning precisely because the SVS supplies the vocabulary the rest of the exam assumes.

Inputs and output

The SVS takes two inputs: opportunity and demand. It produces one output: value.

• Opportunity represents options or possibilities to add value for stakeholders or otherwise improve the organization. Opportunity is prospective. It is the new market, the emerging technology, the unmet need nobody has asked for yet.
• Demand is the need or desire for products and services among internal and external consumers. Demand is present-tense and expressed. It is the request that arrives, the requirement that is stated, the volume that has to be handled.

The distinction is examinable and simple to hold: demand is what consumers are asking for now; opportunity is what the organization could do that nobody has asked for. An organization that responds only to demand never innovates. An organization that pursues only opportunity fails at the work in front of it. The SVS accepts both.

The output is value, in the module 1 sense: perceived benefits, usefulness, and importance, co-created with the consumer, for the consumer, the organization, and other stakeholders.

The five components

Between the inputs and the output sit five components. You should be able to list all five, because a straightforward recall question here is likely and the distractors are usually a real component swapped for a plausible non-component such as "governance framework", "service lifecycle", or "the four dimensions".

• Guiding principles. Seven recommendations that guide the organization in all circumstances. They shape how everything else in the system is done.
• Governance. The means by which the organization is directed and controlled. Governance sets direction, establishes policy, and monitors performance against it.
• Service value chain. A set of six interconnected activities that convert inputs into outputs. This is the operating model at the center of the SVS.
• Practices. Thirty-four sets of organizational resources designed for performing work or accomplishing an objective. Practices are drawn on by the value chain activities.
• Continual improvement. A recurring activity performed at every level to ensure performance continually meets stakeholder expectations. It is both a component of the SVS and a practice, and it applies to every other component.

Note the layering. The service value chain is one of the five components, not a synonym for the SVS. Practices are drawn on by the value chain, not sequenced after it. And continual improvement wraps the whole thing rather than sitting at the end.

The problem the SVS exists to solve

ITIL is explicit about why the model is framed as a system: the SVS exists to prevent organizational silos. The failure it names is an organization in which each function optimizes its own work, information does not cross boundaries, and priorities are set locally. In such an organization each part can be performing well while the service the consumer experiences is slow, inconsistent, and unimprovable, because no one owns the whole.

The SVS answers this by describing the organization as a system with defined inputs, interacting components, and a single output that everything is accountable to. Two properties follow, and both are examinable:

• Flexibility. The SVS is not a fixed sequence. The value chain activities can be combined in many different ways, forming multiple value streams for different kinds of work. A major incident and a new feature both travel through the value chain and take entirely different paths through it.
• Adaptability. Because the components interact rather than sit in a queue, the organization can change how it responds to a new kind of demand without redesigning the whole system.

Governance, briefly

Governance is the component candidates are least confident about, largely because ITIL treats it at a high level at Foundation. Governance is the means by which an organization is directed and controlled. The governing body evaluates the organization and its position, directs by setting strategy and policy, and monitors performance and compliance against that direction. The distinction from management is worth holding: governance sets direction and constraint; management operates within it. Governance is a component of the SVS because direction has to come from somewhere, and an organization that improves without direction improves in arbitrary directions.

How the components interact

A useful way to hold the model: demand and opportunity arrive at the organization. Governance sets the direction and constraints within which the organization may respond. The guiding principles shape how the organization approaches the work. The service value chain is where the work is organized into activities. The practices supply the resources and capabilities those activities draw on. Continual improvement operates on all of it, and on itself. The result is value.

That sentence is close to a complete answer to any Foundation-level question about how the SVS works, and it costs a few minutes to memorize.

Where this leaves you for the rest of the syllabus

Everything remaining on the exam is inside this model. Module 5 opens up the service value chain component. Modules 6 and 7 open up the practices component — module 6 at the level of purpose and definition, module 7 in operational detail. The guiding principles from module 2 are a component of the SVS, and the four dimensions from module 3 apply to the SVS as a whole and to every service within it.

That is why one question is a misleading measure of this module's importance. The single SVS question is easy marks if you know the five components and the inputs and output. The larger benefit is that the remaining thirty-nine questions stop feeling like an unconnected inventory of terms and start reading as parts of one described system, which is a substantially easier thing to remember under time pressure.