Process overview: Service level management
Process overview: Service level management
Process Overview: Service Level Management
Summary
Service Level Management (SLM) is an ITSM process that focuses on establishing and maintaining effective service level agreements (SLAs) between the service provider and its customers. It aims to ensure that the agreed-upon levels of service quality are consistently met and that customer expectations are fulfilled.
The primary objective of Service Level Management is to align IT services with the needs of the business, ensuring that the services delivered are in line with the defined service levels. This involves proactive planning, negotiation, and monitoring of SLAs to meet customer requirements and improve customer satisfaction.
Use Cases
The process includes the high-level use cases listed below. Descriptions of these use cases can be found on their respective pages, accessible through the links provided below. These dedicated pages delve deeper into the use cases, example scenarios, workflows, results, and benefits associated with each use case, offering a granular view of their roles within the process.
- Defining Service Level Agreements
- Defining Business Hours
- Managing service level agreements
- Service level reporting
Use Case Diagram
Rules for Calculating Service Level Compliance
The service management tool ensures service level compliance as part of the Incident management and Service request management processes. The following technical process flow describes the process for performing SLA calculations from a technical perspective.
Technical process flow describing the process for calculating
By default, the solution assumes that a Default SLA has been defined. In case the multiple SLAs have been configured, the strictest SLA will be found.
The process involves finding the strictest SLA, in case several SLAs have been defined. The solution checks the SLAs found through the following paths.
- Customer -> Customer VIP SLA
- Organization -> Organization SLA
- Service -> Service Level
- Self-Service item -> SLA
Note
It is recommended to define the SLAs based on services in the service catalog. By defining SLAs per service, you can establish clear expectations and ensure that each service is supported by appropriate performance targets and service commitments. This approach allows for greater flexibility and granularity in managing and monitoring service levels, as different services may have varying requirements and priorities.
The following process timeline for the Incident management and Service request management processes shows the key metrics related to the service level management process: the Response time and Resolution time.
Process timeline for the Incident management and Service request management
Terminology
| Term | Explanation |
| Service Level Management (SLM) | The process of managing and maintaining the agreed-upon service levels outlined in the SLAs. SLM involves monitoring, measuring, and reporting on service performance, as well as taking actions to improve or maintain service levels. |
| Service level agreement (SLA) | A formal agreement between a service provider and a customer that defines the level of service to be provided. It outlines the specific performance targets (Response time and Resolution time). The SLAs are represented by Service level datacards in the service management tool. |
| Response time | The amount of time it takes for a service provider to respond to a customer's request or query. It is measured from the moment the request is received (Ticket created) until the provider acknowledges the issue by changing the status of the Ticket. Response time is a critical metric in assessing the timeliness of service delivery. |
| Resolution time | The duration or timeframe within which a service provider commits to resolving an incident or fulfilling a request after it has been reported (Ticket created). Resolution time represents the maximum allowable time to restore the service to normal operation, provide a solution to the customer, or fulfill the request. It is an important metric in incident management and service request management and is defined in SLAs to ensure timely resolution and fulfillment. |
| Business hours | The designated hours during which a service provider is available to deliver services or support to customers. Business hours are typically defined as part of SLAs and may vary based on the organization's working schedule or customer requirements. Service level targets may differ during and outside of business hours. |
| SLAFinder | A handler in the service management tool, which finds the strictest SLA from predefined SLA paths. |
| SLADeadline | A handler in the service management tool, which calculates the target time (date & time) based on predefined rules. |
Prerequisites
-
Clear service definitions
- Clearly define the services being provided and ensure a common understanding of the scope, components, and boundaries of each service. This includes identifying service dependencies, interfaces, and any associated service level requirements.
-
A service catalog
- Develop a comprehensive service catalog that includes detailed descriptions of all services offered, along with their associated service levels, performance metrics, and targets. The service catalog serves as a central repository of information and helps set clear expectations with customers.
-
Customer requirements
- Understand the specific requirements, needs, and expectations of the customers or stakeholders. This involves conducting thorough discussions, interviews, and surveys to gather customer input and insights on desired service levels, response times, availability, and other critical factors.
-
Metrics and Measurements
- Establish a set of meaningful metrics and measurements to assess service performance. These metrics should be aligned with business objectives and customer expectations. Required metrics include response time and resolution time.
-
Monitoring and Reporting
- Utilize the ready-made service level management reporting capabilities to track service performance against defined SLAs. Define also reporting schedules to provide timely visibility into service performance.
Benefits
-
Clear expectations
- The process helps establish clear and agreed-upon service levels, performance metrics, and targets through SLAs. This ensures that both service providers and customers have a common understanding of what to expect, fostering transparency and avoiding misunderstandings.
-
Improved customer satisfaction
- By defining and meeting service level targets, the process enhances customer satisfaction. Customers can rely on consistent and predictable service performance, leading to increased trust, loyalty, and positive experiences.
-
Performance monitoring and accountability
- The process includes monitoring and tracking service performance against defined SLAs. This enables service providers to proactively identify and address performance gaps, ensuring accountability for meeting service commitments and maintaining high-quality service levels.
-
Efficient resource allocation
- Service level management helps in allocating resources effectively based on the agreed-upon service levels. This ensures that resources, such as personnel, infrastructure, and budget, are allocated optimally, resulting in improved operational efficiency and cost-effectiveness.
Actors and Roles
| Actor | Description | Roles in Efecte Service Management Tool (ESM) |
| End user | A person who uses the products or services the company provides. | N/A |
| Service Desk agent | Provides customer support to end users. The Service Desk agent belongs to a Support group that acts as a first point of contact for end users. |
Service Desk Agent |
| 3rd part actors | 3rd party actors are often vendors that provide IT services to the company. | N/A |
Table of Contents