The ITIL Service Value System (SVS) represents how the various components and activities of the organization work together to facilitate value creation through IT-enabled services. It maps how demand and opportunity are transformed into tangible value for stakeholders.

The SVS ensures that the organization continually co-creates value with all stakeholders through the use and management of products and services. The key inputs to the SVS are opportunity and demand, and the output of the SVS is value.

Components of the SVS

The SVS includes the following core components:

  1. Guiding Principles: Recommendations that guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.
  2. Governance: The means by which an organization is directed and controlled, ensuring alignment with overall business strategy.
  3. Service Value Chain: A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
  4. Practices: Sets of organizational resources designed for performing work or accomplishing an objective.
  5. Continual Improvement: A recurring organizational activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.

The Service Value Chain (SVC)

At the heart of the SVS is the Service Value Chain. This is the operating model for service management. It outlines six key activities that can be combined in various ways to form multiple value streams. These activities are not linear; they are flexible and designed to interact with each other.

The six value chain activities are:

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 organization.
  • Key Focus: Strategic planning, portfolio management, policy creation, and aligning IT capabilities with business goals.

2. Improve

  • Purpose: To ensure continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management.
  • Key Focus: Identifying opportunities for enhancement, executing improvement initiatives, and measuring the impact of changes.

3. Engage

  • Purpose: To provide a good understanding of stakeholder needs, transparency, and continual engagement and good relationships with all stakeholders.
  • Key Focus: Capturing demand, managing customer and supplier relationships, communicating expectations, and facilitating user support.

4. Design and Transition

  • Purpose: To ensure that products and services continually meet stakeholder expectations for quality, costs, and time to market.
  • Key Focus: Translating requirements into service designs, managing changes, creating new or modifying existing services, and ensuring seamless deployment into the live environment.

5. Obtain / Build

  • Purpose: To ensure that service components are available when and where they are needed, and meet agreed specifications.
  • Key Focus: Software development, procuring third-party software or hardware, and building the necessary infrastructure to support service delivery.

6. Deliver and Support

  • Purpose: To ensure that services are delivered and supported according to agreed specifications and stakeholders’ expectations.
  • Key Focus: Day-to-day operations, incident resolution, fulfilling service requests, and managing the ongoing performance of the live services.

Value Streams

The Service Value Chain is not a rigid, linear process. Instead, organizations respond to specific scenarios or demands by creating Value Streams. A value stream is a specific journey through the value chain activities.

For example, resolving a major incident might involve moving from Engage (user reports issue), directly to Deliver and Support (initial troubleshooting), then to Improve (identifying a permanent fix), and back to Engage (updating the user). Developing a new software feature would trace a very different path through Engage, Plan, Design and transition, Obtain/build, and finally Deliver and support. By keeping the value chain flexible, ITIL 4 supports Agile, DevOps, and traditional waterfall approaches alike.