ITIL 4 SLM study materials
ITIL 4 SLM study resources

ITIL 4 SLM: Service level management and the ITIL 4 service value system

ITIL 4 SLM · Work through your exam, one topic at a time.

All guide sections

Service level management and the ITIL 4 service value system

Domain 2 asks where SLM sits in the ITIL 4 service value system (SVS) and how it connects to other practices. Questions typically give a scenario and ask which value chain activity or practice is engaged.

SLM in the SVS

The SVS has five components: guiding principles, governance, the service value chain, practices and continual improvement. SLM is one of the 17 service management practices - a set of organizational resources designed for performing work, not a lifecycle stage. It contributes across all six value chain activities:

  • Plan: targets reflect business strategy and portfolio decisions.
  • Improve: breaches and review actions feed the improvement register.
  • Engage: the core - SLRs, negotiation, reviews, complaints.
  • Design and transition: SLRs constrain design; an SLA the design cannot meet is a defect.
  • Obtain and build: supplier contracts and components must support the targets.
  • Deliver and support: targets drive prioritization and escalation.

Interfaces that get examined

Business relationship management (the customer relationship), service catalogue management (accurate service descriptions), service desk and incident management (priority setting), availability, capacity and continuity management (the mechanics behind the numbers), measurement and reporting (the data), supplier and problem management, and continual improvement.

Principles in play

Focus on value - agree targets customers care about. Collaborate and promote visibility - co-create SLAs and publish results. Keep it simple and practical - three meaningful SLOs beat forty unread pages. Progress iteratively - start with the critical services.

Worked example

An HR portal is being designed. SLM is engaged in Plan to confirm which workforce outcomes matter, in Engage to capture SLRs, in Design and transition to test achievability, in Obtain and build to set the hosting UC, and in Deliver and support to prioritize incidents against agreed targets.

Traps

Assuming SLM lives only in deliver and support; treating SLM as policing rather than value co-creation; letting the service catalogue drift so SLAs describe services that no longer exist.