Service Level Management: Difference between revisions
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
<meta property="fb:admins" content="100002592864414" /> | <meta property="fb:admins" content="100002592864414" /> | ||
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/9/9f/Service-level-management.jpg" /> | <meta property="og:image" content="https://wiki.en.it-processmaps.com/images/9/9f/Service-level-management.jpg" /> | ||
<meta property="og:image:width" content=" | <meta property="og:image:width" content="1200" /> | ||
<meta property="og:image:height" content=" | <meta property="og:image:height" content="1200" /> | ||
<meta name="twitter:card" content="summary"> | |||
<meta name="twitter:site" content="@itprocessmaps"> | |||
<meta name="twitter:creator" content="@itprocessmaps"> | |||
<meta name="twitter:title" content="Service Level Management | IT Process Wiki"> | |||
<meta name="twitter:description" content="Service Level Management aims to negotiate Service Level Agreements with the customers and to design services in accordance with the agreed service level targets."> | |||
<meta name="twitter:image" content="https://wiki.en.it-processmaps.com/images/thumb/9/9f/Service-level-management.jpg/600px-Service-level-management.jpg"> | |||
<meta name="twitter:image:alt" content="Overview of Service Level Management: This image illustrates the Service Level Management process according to ITIL, highlighting the most important interfaces of Service Level Management, its sub-processes and their interrelationships."> | |||
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | <link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
Line 38: | Line 45: | ||
==Process Description== | ==Process Description== | ||
[[Image:Service-level-management.jpg|right|thumb|500px|alt=Service Level Management ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Service-level-management.jpg|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_service_level_management_itilv3.pdf Service Level Management]]] | |||
[[Image:Service-level-management.jpg|right|thumb| | Service Level Management has been completely redesigned in ITIL 2011 following the introduction of the [[ITIL Design Coordination|Design Coordination]] process. | ||
Coordinating activities have been removed. | Coordinating activities have been removed. | ||
Line 45: | Line 52: | ||
Service Level Management is now mainly responsible for [[#Service Level Management Requirements|gathering service requirements]], as well as [[#ITIL Service Level Management Reporting|monitoring and reporting]] with regards to [[#Service Level Management Agreements|agreed service levels]]. | Service Level Management is now mainly responsible for [[#Service Level Management Requirements|gathering service requirements]], as well as [[#ITIL Service Level Management Reporting|monitoring and reporting]] with regards to [[#Service Level Management Agreements|agreed service levels]]. | ||
The process overview of [[Media:Service-level-management.jpg|Service Level Management (.JPG)]] shows the key information flows (see | The process overview of [[Media:Service-level-management.jpg|Service Level Management (.JPG)]] shows the key information flows (see fig. 1). | ||
[[ITIL 4]] refers to 'Service Level Management' as a [[ITIL_4#Service_management_practices|service management practice]]. | |||
==Sub-Processes== | ==Sub-Processes== | ||
Line 55: | Line 62: | ||
<p><span itemprop="name" content="Service Level Management sub-processes:">These are the <strong class="selflink">Service Level Management</strong> sub-processes and their process objectives:</span> | <p><span itemprop="name" content="Service Level Management sub-processes:">These are the <strong class="selflink">Service Level Management</strong> sub-processes and their process objectives:</span> | ||
</p> | </p> | ||
<p><b><span id="Service_Level_Management_Framework" itemprop="itemListElement">Maintenance of the SLM Framework</span></b> | <p><b><span id="Service_Level_Management_Framework" itemprop="itemListElement">Maintenance of the SLM Framework</span></b> | ||
</p> | </p> | ||
<ul><li itemprop="description">Process Objective: To design and maintain the underlying structure of the <a href="/index.php/Service_Level_Management#Customer_Agreement_Portfolio" title="Service Level Management">Customer Agreement Portfolio</a>, and to provide <a href="/index.php/Service_Level_Management#SLM_Document_Templates" title="Service Level Management">templates for the various SLM documents</a>. | <ul><li itemprop="description">Process Objective: To design and maintain the underlying structure of the <a href="/index.php/Service_Level_Management#Customer_Agreement_Portfolio" title="Service Level Management">Customer Agreement Portfolio</a>, and to provide <a href="/index.php/Service_Level_Management#SLM_Document_Templates" title="Service Level Management">templates for the various SLM documents</a>. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Service_Level_Management_Requirements" itemprop="itemListElement">Identification of Service Requirements</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Process Objective: To capture desired outcomes (requirements from the customer viewpoint) for new services or major service modifications. The <a href="/index.php/Service_Level_Management#Service_Requirements" title="Service Level Management">service requirements</a> 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. | <ul><li itemprop="description">Process Objective: To capture desired outcomes (requirements from the customer viewpoint) for new services or major service modifications. The <a href="/index.php/Service_Level_Management#Service_Requirements" title="Service Level Management">service requirements</a> 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. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Service_Level_Management_Agreements" itemprop="itemListElement">Agreements Sign-Off and Service Activation</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Process Objective: To have all relevant contracts signed off after completion of Service Transition, and to check if <a href="/index.php/Service_Level_Management#SAC" title="Service Level Management">Service Acceptance Criteria</a> are fulfilled. In particular, this process makes sure that all relevant <a href="/index.php/Service_Level_Management#OLA" title="Service Level Management">OLAs</a> are signed off by their <a href="/index.php/Service_Level_Management#Service_Owner" title="Service Level Management">Service Owners</a>, and that the <a href="/index.php/Service_Level_Management#SLA" title="Service Level Management">SLA</a> is signed off by the customer. | <ul><li itemprop="description">Process Objective: To have all relevant contracts signed off after completion of Service Transition, and to check if <a href="/index.php/Service_Level_Management#SAC" title="Service Level Management">Service Acceptance Criteria</a> are fulfilled. In particular, this process makes sure that all relevant <a href="/index.php/Service_Level_Management#OLA" title="Service Level Management">OLAs</a> are signed off by their <a href="/index.php/Service_Level_Management#Service_Owner" title="Service Level Management">Service Owners</a>, and that the <a href="/index.php/Service_Level_Management#SLA" title="Service Level Management">SLA</a> is signed off by the customer. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="ITIL_Service_Level_Management_Reporting" itemprop="itemListElement">Service Level Monitoring and Reporting</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Process Objective: To monitor achieved service levels and compare them with agreed service level targets ("<a href="/index.php/Service_Level_Management#Service_Level_Report" title="Service Level Management">Service Level Report</a>"). This information is circulated to customers and all other relevant parties, as a basis for measures to improve service quality. | <ul><li itemprop="description">Process Objective: To monitor achieved service levels and compare them with agreed service level targets ("<a href="/index.php/Service_Level_Management#Service_Level_Report" title="Service Level Management">Service Level Report</a>"). This information is circulated to customers and all other relevant parties, as a basis for measures to improve service quality. | ||
</li></ul> | </li></ul> | ||
</div><!-- end of schema.org/ItemList --><p></html> | </div><!-- end of schema.org/ItemList --><p></html> | ||
==Definitions== | ==Definitions== | ||
Line 82: | Line 84: | ||
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | <html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList --> | ||
<meta itemprop="itemListOrder" content="Ascending" /> | <meta itemprop="itemListOrder" content="Ascending" /> | ||
<p><span itemprop="name">The following <a href="/index.php/ | <p><span itemprop="name">The following <a href="/index.php/ITIL_Glossary#ITIL_Glossary_A-Z" title="ITIL Glossary">ITIL terms and acronyms</a> (<i>information objects</i>) are used in ITIL Service Level Management to represent process outputs and inputs:</span> | ||
</p> | </p> | ||
<p><b><span id="Customer_Agreement_Portfolio" itemprop="itemListElement">Customer Agreement Portfolio</span></b> | <p><b><span id="Customer_Agreement_Portfolio" itemprop="itemListElement">Customer Agreement Portfolio</span></b> | ||
</p> | </p> | ||
<ul><li itemprop="description">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. | <ul><li itemprop="description">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. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="OLA" itemprop="itemListElement">Operational Level Agreement (OLA)</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">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: <a href="/index.php/Checklist_SLA_OLA" title="Checklist SLA OLA">ITIL Checklist SLA - OLA</a>). | <ul><li itemprop="description">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: <a href="/index.php/Checklist_SLA_OLA" title="Checklist SLA OLA">ITIL Checklist SLA - OLA</a>). | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Service_Requirements" itemprop="itemListElement">Outline of Service Requirements</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">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. | <ul><li itemprop="description">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. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="SAC" itemprop="itemListElement">Service Acceptance Criteria (SAC)</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">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. | <ul><li itemprop="description">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. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="SLA" itemprop="itemListElement">Service Level Agreement (SLA)</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">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: <a href="/index.php/Checklist_SLA_OLA" title="Checklist SLA OLA">ITIL Checklist SLA - OLA</a>). | <ul><li itemprop="description">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: <a href="/index.php/Checklist_SLA_OLA" title="Checklist SLA OLA">ITIL Checklist SLA - OLA</a>). | ||
</li></ul> | </li></ul> | ||
<p><b><span id="Service_Level_Report" itemprop="itemListElement">Service Level Report</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">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. | <ul><li itemprop="description">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. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="SLR" itemprop="itemListElement">Service Level Requirements (SLR)</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">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 <a href="/index.php/Service_Level_Management#SLA" title="Service Level Management">Service Level Agreement</a>. | <ul><li itemprop="description">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 <a href="/index.php/Service_Level_Management#SLA" title="Service Level Management">Service Level Agreement</a>. | ||
</li></ul> | </li></ul> | ||
<p><b><span id="SLM_Document_Templates" itemprop="itemListElement">SLM Document Templates</span></b> | |||
</p> | </p> | ||
<ul><li itemprop="description">Templates for the various documents used within Service Level Management, e.g. <a href="/index.php/Service_Level_Management#SLR" title="Service Level Management">Service Level Requirements</a>, <a href="/index.php/Service_Level_Management#SLA" title="Service Level Management">Service Level Agreements</a>, <a href="/index.php/Service_Level_Management#OLA" title="Service Level Management">Operational Level Agreements</a>, <a href="/index.php/Supplier_Management#UC" title="Supplier Management">Underpinning Contracts</a>, <a href="/index.php/Service_Level_Management#SAC" title="Service Level Management">Service Acceptance Criteria</a>, ... | <ul><li itemprop="description">Templates for the various documents used within Service Level Management, e.g. <a href="/index.php/Service_Level_Management#SLR" title="Service Level Management">Service Level Requirements</a>, <a href="/index.php/Service_Level_Management#SLA" title="Service Level Management">Service Level Agreements</a>, <a href="/index.php/Service_Level_Management#OLA" title="Service Level Management">Operational Level Agreements</a>, <a href="/index.php/Supplier_Management#UC" title="Supplier Management">Underpinning Contracts</a>, <a href="/index.php/Service_Level_Management#SAC" title="Service Level Management">Service Acceptance Criteria</a>, ... | ||
</li></ul> | </li></ul> | ||
</div><!-- end of schema.org/ItemList --><p></html> | </div><!-- end of schema.org/ItemList --><p></html> | ||
==<span id="Checklists_.7C_KPIs">Templates | KPIs</span>== | ==<span id="Checklists_.7C_KPIs">Templates | KPIs</span>== | ||
Line 140: | Line 133: | ||
</ul></li> | </ul></li> | ||
</ul><p></html> | </ul><p></html> | ||
==Roles | Responsibilities== | ==Roles | Responsibilities== | ||
Line 146: | Line 138: | ||
'''<span id="Service Level Manager">Service Level Manager - Process Owner</span>''' | '''<span id="Service Level Manager">Service Level Manager - Process Owner</span>''' | ||
*The Service Level Manager is responsible for negotiating [[Service Level Management#SLA|Service Level Agreements]] and ensuring that these are met. He makes sure that all IT Service Management processes, [[Service Level Management#OLA|Operational Level Agreements]] and Underpinning Contracts are appropriate for the agreed service level targets. The Service Level Manager also monitors and [[Service Level Management#Service Level Report|reports on service levels]]. | *The Service Level Manager is responsible for negotiating [[Service Level Management#SLA|Service Level Agreements]] and ensuring that these are met. He makes sure that all IT Service Management processes, [[Service Level Management#OLA|Operational Level Agreements]] and Underpinning Contracts are appropriate for the agreed service level targets. The Service Level Manager also monitors and [[Service Level Management#Service Level Report|reports on service levels]]. | ||
'''<span id="Service Owner">Service Owner</span>''' | '''<span id="Service Owner">Service Owner</span>''' | ||
Line 153: | Line 144: | ||
<p> </p> | <p> </p> | ||
{| | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|style=" | |+ style="background:#013b5e; color:#ffffff; font-size: 120%" colspan="7"|'''<span id="RACI-Matrix-Service-Level-Management">Responsibility Matrix: ITIL Service Level Management</span>''' | ||
|- | |- | ||
!style="background:#ffffee; width: 50%; text-align:center" | ITIL Role | !style="background:#ffffee; width: 50%; text-align:center" | ITIL Role / Sub-Process | ||
! style="background:# | ! style="background:#eeeeee;" | [[Service Level Management#Service Level Manager|Service Level Manager]] | ||
! style="background:# | ! style="background:#eeeeee;" | [[Service Level Management#Service Owner|Service Owner]] | ||
! style="background:# | ! style="background:#eeeeee;" | Business Relationship Manager[[Service Level Management#Team|<small>[3]</small>]] | ||
! style="background:# | ! style="background:#eeeeee;" | Applications Analyst[[Service Level Management#Team|<small>[3]</small>]] | ||
! style="background:# | ! style="background:#eeeeee;" | Technical Analyst[[Service Level Management#Team|<small>[3]</small>]] | ||
! style="background:# | ! style="background:#eeeeee;" | Other roles involved | ||
|- | |- | ||
|style="text-align:left;" |[[#Service Level Management Framework|Maintenance of the SLM Framework]] | |style="text-align:left;" |[[#Service Level Management Framework|Maintenance of the SLM Framework]] | ||
Line 198: | Line 189: | ||
|- | |- | ||
|} | |} | ||
'''Remarks''' | '''Remarks''' | ||
Line 210: | Line 199: | ||
<span id="ITIL Service Level Management Roles">[4] Capacity Manager, Availability Manager, IT Service Continuity Manager, and Financial Manager (see [[ITIL Roles|→ Role descriptions ...]])</span> | <span id="ITIL Service Level Management Roles">[4] Capacity Manager, Availability Manager, IT Service Continuity Manager, and Financial Manager (see [[ITIL Roles|→ Role descriptions ...]])</span> | ||
==Notes== | ==Notes== | ||
Line 256: | Line 243: | ||
<link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" /> | <link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" /> | ||
<link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/9/9f/Service-level-management.jpg" /> | <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/9/9f/Service-level-management.jpg" /> | ||
<span id="https://wiki.en.it-processmaps.com/images/9/9f/Service-level-management.jpg" itemprop="image" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="caption" content="Service Level Management"> | |||
<meta itemprop="contentUrl" content="https://wiki.en.it-processmaps.com/images/9/9f/Service-level-management.jpg" /> | |||
<meta itemprop="width" content="1200" /> | |||
<meta itemprop="height" content="1200" /> | |||
<meta itemprop="representativeOfPage" content="true"/> | |||
<meta itemprop="dateCreated" content="2011-09-19" /> | |||
<meta itemprop="dateModified" content="2020-06-20" /> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://wiki.en.it-processmaps.com/images/thumb/9/9f/Service-level-management.jpg/600px-Service-level-management.jpg" /> | |||
<meta itemprop="width" content="600" /> | |||
<meta itemprop="height" content="600" /> | |||
</span> | |||
<meta itemprop="keywords" content="Service Level Management" /> | |||
<meta itemprop="keywords" content="ITIL Service Level Management" /> | |||
</span> | |||
<link itemprop="author" href="https://www.linkedin.com/in/stefankempter" /> | <link itemprop="author" href="https://www.linkedin.com/in/stefankempter" /> | ||
<meta itemprop="author" content="Stefan Kempter" /> | <meta itemprop="author" content="Stefan Kempter" /> | ||
Line 262: | Line 265: | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL | [[Category:ITIL 2011]][[Category:ITIL V3]][[Category:ITIL process]][[Category:Service Design|Service Level Management]][[Category:Service Level Management|!]] | ||
<!-- --- --> | <!-- --- --> |
Revision as of 17:01, 23 July 2020
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