🔗 The Service Value Chain (SVC)

An operating model that outlines the key activities required to respond to demand and facilitate value realisation

---

Table of Contents

1. Why This Module Matters
2. The Six Activities
3. Activity 1: Plan
4. Activity 2: Improve
5. Activity 3: Engage
6. Activity 4: Design & Transition
7. Activity 5: Obtain / Build
8. Activity 6: Deliver & Support
9. Value Streams: Combining SVC Activities
10. SVC Activities Quick Reference

---

Why This Module Matters

The SVC carries 2 exam marks. You need to describe the purpose of each of the six activities and understand their interconnected nature.

---

The Six Activities

flowchart LR
    D["📥 Demand /\nOpportunity"]

    subgraph SVC["Service Value Chain"]
        PL["📋 Plan"]
        IM["🔄 Improve"]
        EN["🤝 Engage"]
        DT["🎨 Design &\nTransition"]
        OB["🔨 Obtain /\nBuild"]
        DS["🚀 Deliver &\nSupport"]
    end

    VAL["🌟 Value /\nProducts &\nServices"]

    D --> PL & EN & IM
    PL <--> DT & OB & DS
    EN <--> DT & OB & DS
    IM <--> DT & OB & DS
    DT <--> OB
    DS --> VAL
    OB --> VAL
    EN --> VAL

⚠ Exam Caveat: The SVC activities are not sequential — they are interconnected and can be combined in many different ways to form value streams that match specific scenarios. There is no single fixed order.

---

Activity 1: Plan

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

Inputs	Outputs
Policies and requirements from governance	Strategic, tactical, and operational plans
Improvement initiatives	Portfolio decisions
Demand and opportunities	Architectures and policies

What it enables:

• Alignment between strategy and delivery
• A shared understanding of direction across all teams
• Portfolio management decisions

---

Activity 2: Improve

Purpose: To ensure continual improvement of products, services, and practices across all value chain activities and the four dimensions.

Inputs	Outputs
Product and service performance information	Improvement initiatives
Stakeholder feedback	Improvement status reports
Performance against plans	Change requests to other activities

What it enables:

• Continual improvement embedded at every level (not just a separate “CI project”)
• Learning from incidents, feedback, and measurements
• Input into planning and all other SVC activities

⚠ Exam Caveat: Improve feeds into every other activity. It is the only activity that has direct links to all others. This makes it unique — it is not just one step in a sequence but an ongoing thread running through the entire SVC.

---

Activity 3: Engage

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

Inputs	Outputs
Consolidated demands and opportunities	Requirements and feedback for other activities
Feedback from users and customers	Service performance reports for customers
Product and service performance information	Contracts and agreements with suppliers

What it enables:

• The single interface with customers, users, and external partners
• Capturing and prioritising demand
• Managing contracts and service level agreements

⚠ Exam Caveat: “Engage” is where the service desk and relationship management practice live in the context of the SVC. It is the organisation’s front door — managing the ongoing relationship with all stakeholders.

---

Activity 4: Design & Transition

Purpose: To ensure that products and services continually meet stakeholder expectations for quality, costs, and time to market.

Inputs	Outputs
Portfolio decisions	Requirements and specifications
Architectures and policies	Solutions and components for Obtain/Build
Change requests	Test results and deployment packages

What it enables:

• Designing new or changed services to meet requirements
• Managing the transition to production (ensuring changes do not disrupt existing services)
• Balancing speed of change with risk and quality

---

Activity 5: Obtain / Build

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

Inputs	Outputs
Architectures and specifications	Service components for Deliver & Support
Contracts with suppliers	Knowledge and information
Change requests	Performance information and improvement opportunities

What it enables:

• Acquiring, building, or configuring service components (whether bought or built internally)
• Managing the supply chain for components
• Ensuring readiness for deployment

---

Activity 6: Deliver & Support

Purpose: To ensure that services are delivered and supported according to agreed specifications and stakeholders’ expectations.

Inputs	Outputs
New and changed services from D&T / O&B	Services delivered to customers/users
Contracts and agreements from Engage	Support information and improvement opportunities
Service components	Performance data

What it enables:

• Day-to-day operation and support of live services
• Handling incidents, service requests, and operational events
• Feeding performance data back into Improve and Engage

---

Value Streams: Combining SVC Activities

A value stream is a specific combination of SVC activities tailored to a particular scenario. Different scenarios produce different value streams.

gantt
    title Example Value Streams — How SVC Activities Combine
    dateFormat X
    axisFormat %s

    section New Service Deployment
    Plan            :a1, 0, 1
    Engage          :a2, 1, 2
    Design & Transition :a3, 2, 4
    Obtain / Build  :a4, 3, 5
    Deliver & Support :a5, 5, 6
    Improve         :a6, 0, 6

    section Incident Resolution
    Engage (user reports) :b1, 0, 1
    Deliver & Support :b2, 1, 3
    Improve (post-incident) :b3, 3, 4

    section Service Request Fulfilment
    Engage (request) :c1, 0, 1
    Obtain / Build   :c2, 1, 2
    Deliver & Support :c3, 2, 3

⚠ Exam Caveat: The Gantt above shows how the same six activities combine differently for different scenarios. The exam may show a scenario (e.g. “a user reports a service outage”) and ask which SVC activities are most involved. For an incident: primarily Engage and Deliver & Support; for a new service: primarily Plan, Design & Transition, Obtain/Build.

---

SVC Activities Quick Reference

Activity	One-line Purpose	Key Practices
Plan	Shared vision and direction	Strategy management, portfolio management
Improve	Ongoing improvement at all levels	Continual improvement
Engage	Stakeholder relationships and demand	Service desk, relationship management, SLM
Design & Transition	New and changed services meet requirements	Change enablement, release management
Obtain / Build	Components available when needed	Deployment management, IT asset management
Deliver & Support	Live services operating and supported	Incident management, service request management

---

← 04 — Service Value System

06 — Practices Overview →