Call Us: Malaysia +603 8605 3610 | Singapore +65 3158 4294|

IT Service Level Management Framework

//IT Service Level Management Framework

IT Service Level Management Framework

IT Service Level Management Framework


Information Technology (IT), once seen as only for “software development,” has now found its way into all types of organizations. Businesses that fail to embrace IT and IT leaders who fail to be strategic partners to their business leaders will also fail to lead the business towards their competitive advantage. This is especially true when many business leaders see IT as a costly organizational unit that needs to be controlled.

So, what does it really mean for an IT organization to be a strategic partner?  Does providing solutions to a business problem alone make fulfil this role?

IT organizations should not just provide solutions and solve business problems, but should understand what creates business value and align IT service delivery and management to do so. Value-driven IT service management organization is what brings quality of service to drive business outcomes.

How then do we achieve delivery and management of IT services?

Service Level Management (SLM) as a process must be incorporated by every organization to deliver an agreed level of quality IT services. SLM should incorporate the usage of Service Level Agreements (SLAs), and supported operational documents such as Operational Level Agreement (OLAs) and Underpinning contracts (UCs) to ensure IT services are measured for quality, supported and delivered in a structured, consistent and professional manner applying global best practices and standards.

SLM must incorporate continual alignment between customers of IT and delivery of IT services, provide a consistent interface to the customers who are using IT services.

In this document we provide a framework and schema that details activities to be included in SLM process and provide recommended directives and schema which organizations can use to define service levels targets and operational service procedures to support value creation to business.

The content of this paper is based on best practices as defined on the ITIL® framework.

Purpose and Objectives

The purpose of the SLM process is to ensure that IT organizations can deliver all current and planned IT services to agreed achievable targets as described in the SLA. This is executed by defining, negotiating, agreeing, documenting, monitoring, measuring, reporting and reviewing the level of IT service targets, through instigation of corrective actions to continually improve the level of service delivered.

The SLM process should ensure specific and measurable targets are developed for the IT services being delivered to their customer. Customer satisfaction and overall user experience should be monitored and improved to ensure a positive user’s perception that results from the use or anticipated use of the IT services.

SLM processes should include development of relationships with the business, documenting negotiations and agreements, and the monitoring, measurement and reporting of current and future service level requirements and service level agreements. For all IT services delivered to the business, respective supporting operational level agreements must be developed, agreed between the operational units and managed.

In conjunction with supplier management, the SLM process must review all supplier agreements and related underpinning contracts to ensure targets are aligned to deliver SLA targets to customer.

Proactive prevention of service failures identifies gaps and steps to mitigate service risks and improvement of quality of service levels in concurrence with all other supporting processes must be included in SLM process. Continual Service Improvement (CSI) register should be created to document all improvement opportunities identified to improve the quality of IT services delivered to customer.

High-Level Process Model

The purpose of this section is to provide a High-Level view of an organization’s SLM process. The SLM high-level process flow diagram defines each of the SLM activities. The content in this section has been designed to follow ITIL best practices. Organizations that already have SLAs in place should monitor and report on existing service levels. For new or changed services, the process should start with the defining service level requirements.

Before beginning the activities to establish Service Level Requirements (SLRs) and SLAs, an organization must establish and document a framework for SLM and a structure for SLAs.  At a very high level, ITIL defines key activities for the SLM Process.  These process activities are illustrated in the Service Level Management High Level Process Flow diagram on the following page.

Service Level Management Process Design

Service Level Management Process Design

SLM High-Level Process Activity Descriptions

The Service Level Management Process can be broken down into the following key activities:

1.0 Determine SLR

Determining, documenting and agreeing on requirements for new services and producing SLRs is one of the earliest activities of the SLM process. SLR is a customer requirement of IT services based on business objectives and primarily relates to the warranty of services. What level of services are required by the customer for them to be able to receive the value of utility of the service?

2.0 Monitoring Requirements

Based on SLRs, SLM will need to work with Availability, Capacity, IT Service Continuity and Information Security Management to identify, agree and document the monitoring requirements.

3.0, 3.0(a), 3.0(b) Negotiate and document SLA and supporting documents

The SLA should detail the service level targets to be achieved and specify the responsibilities of both the IT service provider and customer. SLM should interface with all those involved in service provisioning, ensuring that the targets are achievable, and both the internal supporting team and external suppliers have clear expectations of what will be required of them to support the achievement of SLA targets are agreed and documented in OLA and UC respectively.

4.0 Monitor Service Performance against SLA

The performance of service against the established SLA is to be monitored. Only the commonly agreed upon monitorable and measurable performance targets should be included in the SLA. It is essential that monitoring matches the customer’s true perception of service.

5.0  Produce Service reports

Once an SLA is in place with service performance targets documented, service and operational reporting mechanisms, intervals and formats must be defined and agreed with customers. The report should also include any trends or specific actions being undertaken to improve service quality.

6.0 Conduct Service Reviews

Review meetings must be held on a regular basis with customers (or their representatives) to review the service achievement in the last period and to preview any issues for the coming period. Attention should be focused on each breach of service level to determine exactly what caused the loss of service and what can be done to prevent any recurrence.

7.0 Initiate Service Improvement Plan

The constant need for improvement needs to be balanced and focused on those areas most likely to give the greatest business benefit.

In the event of exceptions where service targets are not being met or are close to breaching, OLAs and contracts should be reviewed to see where service provider failures may be impacting the service.  In some cases, this input may justify instigating a Service Improvement Program (SIP).

For areas where the service level is not achievable, a review of the SLA should be conducted, and new targets discussed. Creating a Service Improvement Plan may necessitate working with Continual Service Improvement.

8.0 Measure and Improve CSAT

A systematic process to measure and manage customer’s expectation and perception of quality of services received. This activity should include periodic questionnaires, survey, feedback, review and analysis of customer’s complaints and compliments.

9.0 Reviewing and revising SLA, service scope, OLA and UC

All Service Level Management documentation, including SLAs, OLAs and contracts should be reviewed on a periodic (at least annual) basis. These documents should be governed under Change and Service Asset & Configuration Management control and reviewed and updated using the activities of those processes.

Download the full White Paper

You can download the full white paper by clicking on the link below:

By |2018-07-31T15:18:02+00:00July 31st, 2018|ITIL®|0 Comments

Leave A Comment