The Service Value Chain (SVC)

What Is the Service Value Chain?

The Service Value Chain (SVC) is the central element of the Service Value System. It is an operating model that outlines the key activities required to respond to demand and facilitate value creation.

The SVC provides:

• A set of interconnected activities that an organization performs
• The ability to create many different value streams by combining activities in different sequences
• Flexibility to adapt to different types of work (incident handling, new service development, etc.)

The Six Activities

Activity	One-Line Purpose
Plan	Ensure shared understanding of vision, current status, and improvement direction
Improve	Ensure continual improvement of practices, services, and SVC activities
Engage	Provide a good understanding of stakeholder needs and ensure transparency
Design and Transition	Ensure products and services meet stakeholder expectations
Obtain/Build	Ensure service components are available when and where needed
Deliver and Support	Ensure services are delivered and supported per agreed specifications

---

The Six Activities in Detail

Plan

Purpose: Ensure a shared understanding of the vision, current status, and improvement direction for all four dimensions and all products and services across the organization.

Key inputs:

• Policies, requirements, and constraints from governance
• Consolidated demands and opportunities
• Value chain performance information
• Improvement initiatives and plans
• Knowledge and information about third-party components

Key outputs:

• Strategic, tactical, and operational plans
• Portfolio decisions for Design and Transition
• Architectures and policies for all activities
• Improvement opportunities for the Improve activity

Exam Tip: Plan is the only activity that receives inputs from governance. It also feeds all other activities. It's the "direction-setting" activity.

---

Improve

Purpose: Ensure continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management.

Key inputs:

• Product and service performance information
• Stakeholder feedback
• Performance information and improvement opportunities from all activities
• Knowledge and information about new/changed products/services

Key outputs:

• Improvement initiatives and plans to all activities
• Value chain performance information to Plan
• Improvement status reports to stakeholders via Engage
• Contract and agreement requirements for Engage

Exam Tip: Improve applies to all value chain activities, not just the Deliver & Support phase. It is not a separate "improvement process" — it's an ongoing activity woven throughout the entire SVC.

---

Engage

Purpose: Provide a good understanding of stakeholder needs, transparency, continual engagement, and good relationships with all stakeholders.

Key inputs:

• Product and service portfolio (provided by Plan)
• High-level demand for services and products from customers
• Requests and feedback from users
• Incidents, service requests, and feedback from users
• Market opportunities from existing/potential customers

Key outputs:

• Consolidated demands and opportunities to Plan
• Requirements to Design and Transition
• Change or project initiation requests to Obtain/Build
• Support tasks to Deliver & Support
• Improvement opportunities to Improve

Exam Tip: Engage is the primary interface with external stakeholders (customers, users, suppliers). It captures demand and translates it for internal activities. All external communication flows through Engage.

---

Design and Transition

Purpose: Ensure that products and services continually meet stakeholder expectations for quality, cost, and time to market.

Key inputs:

• Portfolio decisions from Plan
• Architectures and policies from Plan
• Requirements from Engage
• Improvement initiatives from Improve
• Knowledge and information about new/changed products/services from Obtain/Build

Key outputs:

• New and changed products and services to Deliver & Support
• Knowledge and information about products/services to all activities
• Performance information to Improve and Plan
• Contract and agreement requirements to Engage

Exam Tip: Design and Transition is where new or changed services are designed and tested before release. It ensures services meet quality, cost, and time expectations. Questions often ask: which activity ensures a new service meets stakeholder expectations before release? — Design and Transition.

---

Obtain/Build

Purpose: Ensure that service components are available when and where they are needed, and meet agreed specifications.

Key inputs:

• Architectures and policies from Plan
• Requirements and specifications from Design and Transition
• Change or project initiation requests from Engage
• Contracts and agreements with external suppliers from Engage
• Improvement initiatives from Improve

Key outputs:

• Service components to Deliver & Support and Design & Transition
• Knowledge and information about new/changed components to all activities
• Performance information to Improve and Plan

Exam Tip: Obtain/Build is about procuring and building the components needed to deliver services — hardware, software, cloud resources, people, or anything else. It is NOT about designing the service (that's Design & Transition); it's about getting the building blocks.

---

Deliver and Support

Purpose: Ensure that services are delivered and supported according to agreed specifications and stakeholders' expectations.

Key inputs:

• New and changed products and services from Design & Transition
• Service components from Obtain/Build
• Improvement initiatives from Improve
• User support tasks from Engage
• Knowledge and information about products/services

Key outputs:

• Services delivered to customers and users
• Performance information to Improve and Plan (via Engage)
• Improvement opportunities to Improve
• Service performance information to Engage

Exam Tip: Deliver and Support is where day-to-day service delivery and incident/request handling happens. It's the most "operational" of all the activities. The service desk and incident management practice primarily support this activity.

---

Value Streams

A value stream is a series of steps an organization undertakes to create and deliver products and services to a service consumer.

Value streams are specific combinations of SVC activities. Different scenarios produce different value streams:

Scenario	Typical SVC Activities Involved
User raises an incident	Engage → Deliver & Support → (Improve)
New service request	Engage → Design & Transition → Obtain/Build → Deliver & Support
Strategic planning	Plan → Engage → (all as needed)
Continual improvement	Improve → Plan → (all as needed)

Key Points About Value Streams

• There is no single prescribed path through the SVC
• Activities can be performed in any order and repeatedly
• All activities interact with Improve and Plan
• Value streams are tailored to each organization and scenario

---

The SVC and Practices

The SVC activities are not processes — they are broad categories of work. Practices provide the detailed methods, tools, and knowledge needed to carry out SVC activities.

For example:

• Incident Management practice supports → Deliver & Support activity
• Change Enablement practice supports → Design & Transition and Obtain/Build
• Service Desk practice supports → Engage and Deliver & Support
• Continual Improvement practice supports → Improve activity

---

Exam Summary Table

Activity	Key Purpose Word	Common Question Pattern
Plan	Shared understanding / direction	"Which activity ensures the organization has a shared direction?"
Improve	Continual improvement	"Which activity applies to all SVC activities?"
Engage	Stakeholder needs / external interface	"Which activity is the primary interface with customers?"
Design and Transition	Quality, cost, time to market	"Which activity ensures new services meet expectations?"
Obtain/Build	Service components available	"Which activity ensures components are procured/built?"
Deliver and Support	Day-to-day delivery	"Which activity handles incidents and service requests?"

Key Numbers to Remember

• 6 activities in the Service Value Chain
• SVC is the central element of the SVS
• Activities combine into value streams (no fixed sequence)
• All activities interact with Improve and Plan

Common Traps

• "Plan" ≠ "project planning" — it's about shared organizational direction
• "Improve" is embedded throughout, not just at the end
• "Engage" is external-facing; don't confuse with "Collaborate and promote visibility" (a guiding principle)
• "Obtain/Build" includes both buying (obtain) and making (build)