Service Level Management
Objective: Service Level Management (SLM) aims to negotiate Service Level Agreements with the customers and to design services in accordance with the agreed service level targets. This ITIL process is also responsible for ensuring that all Operational Level Agreements and Underpinning Contracts are appropriate, and to monitor and report on service levels.
Part of: Service Design
Process Owner: Service Level Manager
Process Description
Service Level Management has been completely redesigned in ITIL 2011 following the introduction of the Design Coordination process.
Coordinating activities have been removed.
Service Level Management is now mainly responsible for gathering service requirements, as well as monitoring and reporting with regards to agreed service levels.
The process overview of Service Level Management (.JPG) shows the key information flows (see fig. 1).
ITIL 4 refers to 'Service Level Management' as a service management practice.
Sub-Processes
These are the Service Level Management sub-processes and their process objectives:
Maintenance of the SLM Framework
- Process Objective: To design and maintain the underlying structure of the Customer Agreement Portfolio, and to provide templates for the various SLM documents.
Identification of Service Requirements
- Process Objective: To capture desired outcomes (requirements from the customer viewpoint) for new services or major service modifications. The service requirements are to be documented and submitted to an initial evaluation, so that alternatives may be sought at an early stage for requirements which are not technically or economically feasible.
Agreements Sign-Off and Service Activation
- Process Objective: To have all relevant contracts signed off after completion of Service Transition, and to check if Service Acceptance Criteria are fulfilled. In particular, this process makes sure that all relevant OLAs are signed off by their Service Owners, and that the SLA is signed off by the customer.
Service Level Monitoring and Reporting
- Process Objective: To monitor achieved service levels and compare them with agreed service level targets ("Service Level Report"). This information is circulated to customers and all other relevant parties, as a basis for measures to improve service quality.
Definitions
The following ITIL terms and acronyms (information objects) are used in ITIL Service Level Management to represent process outputs and inputs:
Customer Agreement Portfolio
- While the Service Catalogue holds a complete list of the services managed by the service provider, the Customer Agreement Portfolio contains all Service Agreements which provide the framework for delivering services to specific customers.
Operational Level Agreement (OLA)
- An agreement between an IT service provider and another part of the same organization. An OLA supports the IT service provider's delivery of services to customers. The OLA defines the goods or services to be provided and the responsibilities of both parties. For example there could be an OLA - between the IT service provider and a procurement department to obtain hardware in agreed times - between the Service Desk and a support group to provide Incident resolution in agreed times (see also: ITIL Checklist SLA - OLA).
Outline of Service Requirements
- The desired outcome of a service, stated in terms of required service functionality (utility) and service levels (warranty). Based on this information, detailed service requirements are specified during the Service Design stage.
Service Acceptance Criteria (SAC)
- A set of criteria used for service acceptance testing to ensure that an IT service meets its functionality and quality requirements and that the service provider is ready to operate the new service when it has been deployed.
Service Level Agreement (SLA)
- An agreement between an IT service provider and a customer. The SLA describes the IT service, documents service level targets, and specifies the responsibilities of the IT service provider and the customer. A single SLA may cover multiple services or multiple customers (see also: ITIL Checklist SLA - OLA).
Service Level Report
- The Service Level Report gives insight into a service provider's ability to deliver the agreed service quality. To this purpose, it compares the agreed and actually achieved service levels, and also includes information on the usage of services, ongoing measures for service improvement, and any exceptional events. A Service Level Report is issued by the service provider for its customers, IT management and other Service Management processes. A similar report is also created by an external service supplier to document its achieved service performance.
Service Level Requirements (SLR)
- The Service Level Requirements document contains the requirements for a service from the client viewpoint, defining detailed service level targets, mutual responsibilities, and other requirements specific to a certain (group of) customers. As the service enters new stages of its life cycle, the SLR document evolves into a draft Service Level Agreement.
SLM Document Templates
- Templates for the various documents used within Service Level Management, e.g. Service Level Requirements, Service Level Agreements, Operational Level Agreements, Underpinning Contracts, Service Acceptance Criteria, ...
Templates | KPIs
- Key Performance Indicators (KPIs) Service Level Management
- Service Level Management templates and checklists:
Roles | Responsibilities
Service Level Manager - Process Owner
- The Service Level Manager is responsible for negotiating Service Level Agreements and ensuring that these are met. He makes sure that all IT Service Management processes, Operational Level Agreements and Underpinning Contracts are appropriate for the agreed service level targets. The Service Level Manager also monitors and reports on service levels.
Service Owner
- The Service Owner is responsible for delivering a particular service within the agreed service levels. Typically, he acts as the counterpart of the Service Level Manager when negotiating Operational Level Agreements (OLAs). Often, the Service Owner will lead a team of technical specialists or an internal support unit.
| ITIL Role / Sub-Process | Service Level Manager | Service Owner | Business Relationship Manager[3] | Applications Analyst[3] | Technical Analyst[3] | Other roles involved |
|---|---|---|---|---|---|---|
| Maintenance of the SLM Framework | A[1]R[2] | - | - | - | - | - |
| Identification of Service Requirements | AR | - | R | R | R | R[4] |
| Agreements Sign-Off and Service Activation | AR | R | - | - | - | - |
| Service Level Monitoring and Reporting | AR | - | - | - | - | - |
Remarks
[1] A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Service Level Management process.
[2] R: Responsible according to the RACI Model: Those who do the work to achieve a task within Service Level Management.
[3] see → Role descriptions ...
[4] Capacity Manager, Availability Manager, IT Service Continuity Manager, and Financial Manager (see → Role descriptions ...)
Notes
By: Stefan Kempter 
, IT Process Maps.
Process Description › Sub-Processes › Definitions › Templates › Roles
