Service Level Management Process
ISO/IEC 20000 Toolkit Version 9 ŠCertiKit
Service Level Management Process
Implementation Guidance (The header page and this section must be removed from final version of the document)
Purpose of this document The Service Level Management Process defines the approach that will be taken by the service provider in this area, including the structure of SLA(s) adopted.
Areas of the standard addressed The following areas of the ISO/IEC 20000:2018 standard are addressed by this document: 8.3.3 Service level management
General Guidance Our main recommendation in this area is to keep it as simple as possible; an overly complicated structure of SLAs may confuse your customer(s) and make reporting against the SLA a time-consuming task. Try to ensure that relevant service requirements are captured and are available for review during the certification audit.
Review Frequency We would recommend that this document is reviewed annually.
Toolkit Version Number ISO/IEC 20000 Toolkit Version 9 ©CertiKit.
Document Fields This document may contain fields which need to be updated with your own information, including a field for Organization Name that is linked to the custom document property “Organization Name”. To update this field (and any others that may exist in this document): 1. Update the custom document property “Organization Name” by clicking File > Info > Properties > Advanced Properties > Custom > Organization Name 2. Press Ctrl a on the keyboard to select all text in the document (or use Select,
Version 1
Page 2 of 21
[Insert date]
Service Level Management Process
Select All on the ribbon) 3. Press F9 on the keyboard to update all fields 4. When prompted, choose the option to just update TOC page numbers If you wish to permanently convert the fields in this document to text i.e. so that they are no longer updateable, then you will need to click into each occurrence of the field and press Ctrl Shift F9. If you would like to make all fields in the document visible, then go to File > Options > Advanced > Show document content > Field shading and set this to “Always�. This can be useful to check that you have updated all fields correctly. Further detail on the above procedure can be found in the Toolkit Completion Instructions.
Copyright notice Except for any third-party works included in this document, as identified in this document, this document has been authored by CertiKit, and is Š copyright CertiKit except as stated below. CertiKit is a company registered in England and Wales with company number 6432088.
Licence terms This document is licensed on and subject to the standard licence terms of CertiKit, available on request, or by download from our website. All other rights are reserved. Unless you have purchased this product you only have an evaluation licence. If this product was purchased, a full licence is granted to the person identified as the licensee in the relevant purchase order. The standard licence terms include special terms relating to any third-party copyright included in this document.
Disclaimer Please Note: Your use of and reliance on this document template is at your sole risk. Document templates are intended to be used as a starting point only from which you will create your own document and to which you will apply all reasonable quality checks before use. Therefore, please note that it is your responsibility to ensure that the content of any document you create that is based on our templates is correct and appropriate for your needs and complies with relevant laws in your country. You should take all reasonable and proper legal and other professional advice before using this document. CertiKit makes no claims, promises, or guarantees about the accuracy, completeness, or adequacy of our document
Version 1
Page 3 of 21
[Insert date]
Service Level Management Process
templates, assumes no duty of care to any person with respect its document templates or their contents, and expressly excludes and disclaims liability for any cost, expense, loss or damage suffered or incurred in reliance on our document templates, or in expectation of our document templates meeting your needs, including (without limitation) as a result of misstatements, errors and omissions in their contents.
Version 1
Page 4 of 21
[Insert date]
Service Level Management Process
[Replace with your logo]
Service Level Management Process
Document Ref. Version: Dated: Document Author: Document Owner:
Version 1
Page 5 of 21
SMS-DOC-083-7 1 [Insert date]
[Insert date]
Service Level Management Process
Revision History Version Date
Revision Author
Summary of Changes
Distribution Name
Title
Approval Name
Version 1
Position
Signature
Page 6 of 21
Date
[Insert date]
Service Level Management Process
Contents 1
INTRODUCTION ....................................................................................................................................... 8 1.1 1.2 1.3 1.4
2
PURPOSE ................................................................................................................................................... 8 OBJECTIVES .............................................................................................................................................. 8 SCOPE ....................................................................................................................................................... 9 SERVICE LEVEL MANAGEMENT STRUCTURE ............................................................................................ 9
SERVICE LEVEL MANAGEMENT PROCESS .................................................................................. 11 2.1 PROCESS TRIGGERS ................................................................................................................................. 11 2.2 PROCESS INPUTS ..................................................................................................................................... 11 2.3 PROCESS NARRATIVE .............................................................................................................................. 12 2.3.1 Define Services ............................................................................................................................. 13 2.3.2 Agree Service Requirements ......................................................................................................... 13 2.3.3 Negotiate Service Level Agreement(s) .......................................................................................... 13 2.3.4 Monitor Performance Against Targets ......................................................................................... 13 2.3.5 Review ........................................................................................................................................... 13 2.4 PROCESS OUTPUTS .................................................................................................................................. 14 2.5 PROCESS ROLES AND RESPONSIBILITIES ................................................................................................. 14 2.5.1 Service Level Manager ................................................................................................................. 14 2.5.2 Customer ....................................................................................................................................... 14 2.5.3 Service Desk Analyst ..................................................................................................................... 14 2.6 RACI CHART .......................................................................................................................................... 15
3
SERVICE LEVEL MANAGEMENT TOOLS ....................................................................................... 16 3.1 3.2 3.3 3.4 3.5
4
SERVICE DESK SYSTEM............................................................................................................................ 16 EMAIL ..................................................................................................................................................... 16 INTRANET................................................................................................................................................ 16 AVAILABILITY MONITORING TOOLS ....................................................................................................... 16 OFFICE PRODUCTIVITY TOOLS ................................................................................................................ 16
COMMUNICATION AND TRAINING ................................................................................................. 17 4.1 4.2 4.3 4.4
CUSTOMERS AND IT MANAGEMENT ....................................................................................................... 17 PROCESS PERFORMANCE ......................................................................................................................... 17 COMMUNICATION RELATED TO CHANGES .............................................................................................. 17 TRAINING FOR SERVICE LEVEL MANAGEMENT ....................................................................................... 17
5
INTERFACES AND DEPENDENCIES ................................................................................................. 19
6
REPORTING ............................................................................................................................................ 20
7
CONCLUSION.......................................................................................................................................... 21
List of Figures FIGURE 1 - STRUCTURE OF SLAS, OLAS AND UPCS ................................................................................................ 10 FIGURE 2 - SERVICE LEVEL MANAGEMENT PROCESS ................................................................................................. 12
List of Tables TABLE 1 - RACI MATRIX.......................................................................................................................................... 15 TABLE 2 - INTERFACES AND DEPENDENCIES ............................................................................................................. 19 TABLE 3 - KEY PERFORMANCE INDICATORS.............................................................................................................. 20
Version 1
Page 7 of 21
[Insert date]
Service Level Management Process
1
Introduction
1.1
Purpose
This process document defines how the process of service level management will be implemented within [Organization Name]. Service level management is key to the delivery of an effective service and one that is recognised as such by users and customers. Significant effort must be dedicated to ensuring that the levels of service provided are those required by the business and that early warning is available if these are starting to decline, allowing proactive action to be taken as part of a managed improvement programme. The approach to service level management at [Organization Name] must also take account of the fact that IT services provided to the user are sourced from a variety of different organisations. This means that an effective structure of Service Level Agreements (SLAs), Underpinning Contracts (UPCs) and Operational Level Agreements (OLAs) must be in place and their service levels co-ordinated with each other. Although there were existing service level targets established particularly in the Service Desk area, these were largely historical and had not been formally agreed with the business, so a process of collecting Service Level Requirements (SLRs) was undertaken to align the delivery of the IT service with business priorities. This was achieved via a series of meetings with representative parts of the organisation. This document defines how the process of service level management is implemented within [Organization Name]. It should be read in conjunction with the following related documents: • • • 1.2
Service Level Management Policy Service Catalogue Management Process Service Catalogue Objectives
The objectives of the service level management process are to: • • •
Define the way in which service levels will be managed and reported on so that consistency is achieved within the IT organization and a sound basis for decision-making is provided Ensure that the management of service levels takes due account of business priorities and helps to maximise business productivity Foster an effective and efficient approach to the management of services that presents a positive image to the business and maintains user satisfaction
Version 1
Page 8 of 21
[Insert date]
Service Level Management Process
• 1.3
Ensure that information about service levels is communicated to the relevant parties in a timely and accurate manner at all times Scope
The scope of this process is defined according to the following parameters: • • • •
Organizational o [List organizations and parts of those organizations covered] Geographical o [List locations from which service levels will be reported and managed] Services o [Define the services covered by the process] Technical o [If necessary, cover the technology managed via this process]
This process covers all services defined in the service catalogue. The following areas are specifically excluded from this process: [Describe any areas that need to be clearly stated as outside the scope]
1.4
Service Level Management Structure
The overall structure of SLAs, OLAs and UPCs (Under-Pinning Contracts) within [Organization Name] is depicted in the diagram on the following page.
Version 1
Page 9 of 21
[Insert date]
Service Level Management Process
Customer A
Customer B
Customer C
Service Level Agreement
Service Catalogue
Service Provider
OLA
Internal Service Providers
SLA
Other Service Providers
UPC
Third Party Suppliers
UPC
Sub-Contractors
Figure 1 - Structure of SLAs, OLAs and UPCs
[This diagram may need to be amended if you have more than one SLA with different customers.]
Version 1
Page 10 of 21
[Insert date]
Service Level Management Process
2 Service Level Management Process 2.1
Process Triggers
The service level management process is initiated as a result of one or more of the following triggers: • • • 2.2
A new service starts to be defined via the design and transition of new or changed services process Significant changes are made to an existing service, including decommissioning As a result of regular service reviews or audits
Process Inputs
The process of service level management requires a number of inputs in order to be able to function effectively. These may not always be available but will ideally be: • • • • • • • •
Service definitions Service requirements Information about planned service outages Details of the scope and timing of changes being implemented under change management (including those for which an outage is not expected) Key business operation cycles e.g. peak times at which service outages may become more urgent Organizational and contact information Availability of key support resources User and customer communication about service and satisfaction levels
Version 1
Page 11 of 21
[Insert date]
Service Level Management Process
2.3
Process Narrative
The process of service level management within [Organization Name] is shown in the following diagram.
Define services
Agree service requirements
Negotiate Service Level Agreement(s)
Monitor performance against targets
Review
Figure 2 - Service level management process
This process is explained in the following sections.
Version 1
Page 12 of 21
[Insert date]
Service Level Management Process
2.3.1
Define Services
The services provided to the customer by the service provider are defined in the service catalogue. This is agreed between the service provider and the customer and represents the customer’s view of the services provided i.e. all of the services should be recognisable by one or more customers. As part of the service catalogue the organization that actually provides the service to the user is recorded, including third parties. Where appropriate the service is broken down into its components and the provider of each of those service components identified. Dependencies between service components are also shown. 2.3.2
Agree Service Requirements
For each of the services defined in the service catalogue, a set of service requirements will be documented. These will represent the starting point for the negotiation of the SLA. For new or changed services, requirements will be defined as part of the Design and Transition of New or Changed Services process. 2.3.3
Negotiate Service Level Agreement(s)
The terms of the SLA are discussed based on the service requirements and the ability of the service provider to meet them. An agreement is reached and appropriate targets for service levels are set. 2.3.4
Monitor Performance Against Targets
A quarterly service report is produced containing details of performance against the SLA targets and reviewed with customers at a face-to-face meeting to provide the opportunity for discussion and feedback. These reports and feedback are input to a Service Improvement Plan (SIP) which provides a vehicle for the managed development of the services on an on-going basis. 2.3.5
Review
User satisfaction surveys will also be carried out, both on an individual incident basis and across all user departments. In addition to quarterly review meetings with management, Business relationship meetings are held with specific departments to solicit views and feedback from users directly. A full review of the SLA and service catalogue is held on an annual basis at which time the continued suitability of the service level targets is considered and any changes agreed.
Version 1
Page 13 of 21
[Insert date]
Service Level Management Process
2.4
Process Outputs
The service level management process has the following outputs: • • • 2.5
Service catalogue Service Level Agreement Service Reports Process Roles and Responsibilities
The following roles have the stated responsibilities within the service level management process. 2.5.1
• • • • • 2.5.2
• • • • • 2.5.3
• • •
Service Level Manager
Owner of the Service Level Management process Responsible for identifying improvements to the process and ensuring it is adequately resourced Provides information regarding the success rates of the process Runs the process on a day-to-day basis Ensures that annual reviews are carried out Customer
Provides information about service requirements Agrees the definition of the service catalogue Participates in negotiation of the SLA Provides feedback on service performance Attends review meetings Service Desk Analyst
Records information about performance against the SLA Manages incidents to SLA guidelines Implements many of the terms of the SLA on a day to day basis
Version 1
Page 14 of 21
[Insert date]
Service Level Management Process
2.6
RACI Chart
The table below clarifies the responsibilities at each step using the RACI system, i.e.: R= Responsible
A= Accountable
C= Consulted
Role: SL Manager Step Define services Agree service requirements Negotiate SLA Monitor performance Review
I= Informed
Customer
A/R C A/R A/R A/R
R A/R R I R
Service Desk Analyst I I I R I
Table 1 - RACI matrix
Version 1
Page 15 of 21
[Insert date]
Service Level Management Process
3 Service Level Management Tools There are a number of key software tools that underpin an effective service level management process. These are subject to change as requirements and technology are updated and so specific systems are not described here. However the main types of tools that play a significant part in the process within [Organization Name] are as follows. 3.1
Service desk system
The service desk system provides key items of information regarding the availability of services and the degree of success in addressing incidents associated with them. The reporting module allows useful graphs to be presented regarding success against SLA targets and service trends. 3.2
The email system is key to communication between the service level manager and the customer. In addition to allowing discussion about levels of service, it also provides an easily-automated method of keeping users informed of the status of the services they use. 3.3
Intranet
The intranet provides a window for the user into the IT organization in general and service level management in particular. Reports on service performance against the SLA can easily be made available via the intranet. 3.4
Availability Monitoring Tools
Software tools which report on and record periods of service downtime are useful in establishing the reliability of services in an objective way. 3.5
Office Productivity Tools
Tools such as spreadsheets and word processors allow reports to be easily produced in a professional manner and analysis of service statistics to be performed and presented.
Version 1
Page 16 of 21
[Insert date]
Service Level Management Process
4 Communication and Training The service level management process is all about communication and there are various forms of this that must take place for the process to be effective. These are described below. 4.1
Customers and IT Management
Communication should take place with the customers of the IT service with regard to SLAs and the management of IT concerning resource utilisation and allocation. Depending on the health of the process it may be appropriate to hold regular meetings with customers and IT management to discuss the performance and agree any actions to improve it. 4.2
Process Performance
It is important that the performance of the service level management process is monitored and reported upon on a regular basis in order to assess whether SLAs are being met and whether the process is operating as expected. The content of performance reports is set out in section 6 of this document but it is vital that the reports are not only produced but are also communicated to the appropriate audience. 4.3
Communication Related to Changes
Changes to the IT environment can have a significant impact on the delivery of an effective IT service and service level management must be aware of any changes that are due to take place prior to them happening. The service level management process manager must have visibility of the change management schedule as a minimum and ideally will be briefed on any changes with the potential to give rise to service outages. This may be a regular meeting or carried out on an ad-hoc basis according to the frequency of occurrence of such changes. 4.4
Training for Service Level Management
In addition to a well-defined process and appropriate software tools it is essential that the people aspects of service level management are adequately addressed. The process requires that training be provided to all participants in order that it runs as smoothly as possible. The main areas in which training will be required are as follows. •
The service level management process itself, including the activities, roles and responsibilities involved
Version 1
Page 17 of 21
[Insert date]
Service Level Management Process
• • • •
Service level management tools such as the service desk system reporting, intranet and office productivity Soft skills such as customer service, dealing with difficult conversations and avoiding technical jargon The basics of the technology and how it is implemented within [Organization Name] The business, its structure, locations, priorities and people
In addition, training should be provided to customers regarding the purpose, objectives and activities of the service level management process. This training may be provided via short workshops and supplemented by on demand resources such as videos and user guides.
Version 1
Page 18 of 21
[Insert date]
Service Level Management Process
5 Interfaces and Dependencies The service level management process has a number of interfaces and dependencies with other processes within service management. These are outlined here and are described in further detail in the relevant procedural documentation. Process Business Relationship Management
Information Security Management Capacity Management Availability Management Supplier Management Change Management Release and Deployment Management
Inputs to Service Level Management from the named process Updates regarding business changes e.g. staff movers and leavers Business awareness and knowledge Feedback regarding user and customer satisfaction levels Alerts regarding current threats to services Advance warning of possible capacity constraints affecting service Understanding of availability measures in place Information regarding changes within suppliers e.g. contact details and support structure Notice of upcoming changes that may give rise to incidents or outages Consultation regarding timing of deployment of releases Deployment schedules
Outputs from Service Level Management to the named process Reports on service performance Communication regarding ongoing issues and potential outages
Details of outages that could be information security-related e.g. denial of service attacks Information regarding service level requirements Reports on incidents affecting availability, including lengths of outages Service level requirements Feedback on the effects of changes on service levels Feedback about service level issues resulting from deployments
Table 2 - Interfaces and dependencies
Version 1
Page 19 of 21
[Insert date]
Service Level Management Process
6 Reporting Reports on service levels will be produced on a monthly basis and consolidated into the IT Service Report every quarter. The following KPIs will be used on a regular basis to evidence the successful operation of the service level management process: KPI Ref. KPI1 KPI2 KPI3 KPI4 KPI5 KPI6 KPI7
Key Performance Indicator Number of services for which service level targets are met Number and percentage of services for which an SLA is in place Percentage of service reports produced on time Percentage of service meetings held on time User satisfaction scores from user surveys Customer satisfaction scores from customer surveys Number of complaints about the service level management service
Table 3 - Key performance indicators
Version 1
Page 20 of 21
[Insert date]
Service Level Management Process
7 Conclusion Service level management is a key process which seeks to match business requirements and perceptions with the day to day delivery of IT services. As such, it has a wide variety of areas to communicate with and bring together into a coherent and consistent message for the business customers of the services. It is important that this process is able to capture and present an accurate, objective view of how well services are being delivered so that difficult and often costly decisions can be made about the prioritization of resources within the organization.
Version 1
Page 21 of 21
[Insert date]