I85PREP
⌘ K
ITIL 4 SLM study materials
ITIL 4 SLM study resources

ITIL 4 SLM: Service level management practices and techniques

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

All guide sections

Service level management practices and techniques

Domain 3 covers how SLM is actually performed: the workflow, the SLA structures, the techniques for gathering requirements and monitoring, and the roles involved.

The workflow

  1. Engage the customer and capture SLRs from business outcomes, complaints and service reviews - not from whatever monitoring happens to collect.
  2. Negotiate: every extra nine costs money, so present the trade-off between level and cost.
  3. Agree and document the SLA with SLOs, measurement method, exclusions and review cycle.
  4. Monitor continuously against the agreed source.
  5. Report to the audience that needs it.
  6. Review on a scheduled cycle and drive improvement actions.

SLA structures

  • Service-based: one SLA per service, applied to all its customers.
  • Customer-based: one SLA per customer or customer group, covering several services.
  • Multi-level: corporate level (standard terms for the whole organization), customer level (segment-specific targets), service level (per-service SLOs). This avoids duplicating common clauses. Tiered offerings (bronze, silver, gold) are a commercial technique rather than an ITIL requirement, and each tier must still be measurable and OLA-backed.

Techniques

Requirements workshops, complaint and incident trend analysis, customer surveys, benchmarking, synthetic transactions for end-to-end measurement, sampling where full instrumentation is impractical, dashboards, and service review meetings with minutes and owned actions.

Roles

The service level manager owns the SLA portfolio and runs reviews; the service owner is accountable for a service meeting its targets; customers sign; internal teams own OLAs; suppliers own UCs.

Worked example

A managed service provider with three customer segments builds a multi-level structure: one corporate SLA for security, hours and escalation; a customer-level SLA per segment with different response targets; service-level SLOs per offering. Each SLO traces to an OLA with the service desk and a UC with the data-centre provider.

Traps

A forty-page SLA nobody reads; negotiating with someone who lacks authority to accept risk; tiers that are never separately measured; an SLA with no underpinning OLA.