Service Level Management - ITIL V2: Difference between revisions

From IT Process Wiki
No edit summary
 
Line 1: Line 1:
<seo metakeywords="service level management itil v2" metadescription="&#8594; See also Service Level Management ITIL V3. Process Objective: ... tasks of maintaining the IT Organization's Service Catalogue and reaching binding agreements ..." />
<itpmch><title>Service Level Management - ITIL V2 | IT Process Wiki</title>
<meta name="keywords" content="service level management itil v2" />
<meta name="description" content="&#8594; See also Service Level Management ITIL V3. Process Objective: ... tasks of maintaining the IT Organization's Service Catalogue and reaching binding agreements ..." />
</itpmch>
<imagemap>
<imagemap>
Image:ITIL-Wiki-deutsch.jpg|right|ITIL V2 Service Level Management
Image:ITIL-Wiki-deutsch.jpg|right|ITIL V2 Service Level Management
Line 15: Line 18:
'''Process Owner''': [[#Service-Level-Manager-ITIL-V2|Service Level Manager]]
'''Process Owner''': [[#Service-Level-Manager-ITIL-V2|Service Level Manager]]


<p>&nbsp;</p>


==Sub-Processes==
==Sub-Processes==


[[Image:overview_slm.jpg|frame|none|Overview of Service Level Management]]
[[Image:overview_slm.jpg|thumb|724px|none|link=https://wiki.en.it-processmaps.com/index.php/File:Overview_slm.jpg|Overview of Service Level Management]]
 


;Maintain Structures for Service Level Management
'''Maintain Structures for Service Level Management'''
:Process objective: The multitude of documents used within Service  Level Management are to be adjusted in such a  manner, that they correspond to the  requirements of new or changed IT Services.
:Process objective: The multitude of documents used within Service  Level Management are to be adjusted in such a  manner, that they correspond to the  requirements of new or changed IT Services.


;Define Service Requirements
'''Define Service Requirements'''
:Process objective: Requirements from the client viewpoint with regards to a new or altered IT Service are to be documented and submitted to an initial evaluation, so that alternatives may be developed at an early stage for requirements which are not technically or economically feasable.
*Process objective: Requirements from the client viewpoint with regards to a new or altered IT Service are to be documented and submitted to an initial evaluation, so that alternatives may be developed at an early stage for requirements which are not technically or economically feasible.
 
;Create [[ITIL Glossary#Service Specification Sheet|Service Specification Sheet]]
:Process objective: The requirements of a new or altered IT Service are described in more detail, and specifications are drawn up as to how the Service is created from an IT viewpoint and how the invoicing takes place.


;Negotiate and agree Contractual Regulations for the Service
'''Create [[ITIL Glossary#Service Specification Sheet|Service Specification Sheet]]'''
:Process objective: Finalisation of binding agreements to an IT Service between the IT Organisation and the client-side, a well as ensuring sufficient Service Levels with internal and external Service providers, which support the provision of the Service.
*Process objective: The requirements of a new or altered IT Service are described in more detail, and specifications are drawn up as to how the Service is created from an IT viewpoint and how the invoicing takes place.


;Prepare Service Implementation
'''Negotiate and agree Contractual Regulations for the Service'''
:Process objective: Identification of preconditions, which must be established for the implementation of the new or altered Service, so that a correspondoing Change Request may be compiled.
*Process objective: Finalization of binding agreements to an IT Service between the IT Organization and the client-side, a well as ensuring sufficient Service Levels with internal and external Service providers, which support the provision of the Service.


;Commission Service Implementation
'''Prepare Service Implementation'''
:Process objective: After clearance of the Change, the implementation of the IT Service is to be planned in further detail; the Service Level Manager subsequently commissions the technical experts in Application or Infrastructure Management to start the implementation.
*Process objective: Identification of preconditions, which must be established for the implementation of the new or altered Service, so that a corresponding Change Request may be compiled.


;Carry out [[ITIL Glossary#Service Level Report|Service Level Reporting]]
'''Commission Service Implementation'''
:Process objective: It is to be given account of the attained Service quality as well as potential counter-measures for the correction of infringements to the agreed Service Levels.
*Process objective: After clearance of the Change, the implementation of the IT Service is to be planned in further detail; the Service Level Manager subsequently commissions the technical experts in Application or Infrastructure Management to start the implementation.


;Process Complaints and Carry out SLA Reviews
'''Carry out [[ITIL Glossary#Service Level Report|Service Level Reporting]]'''
:Process objective: Investigation of the agreed Service Levels, in order to ensure that the SLAs are still adequate for client requirements; processing of complaints and where necessary, assume corrective measures.
*Process objective: It is to be given account of the attained Service quality as well as potential counter-measures for the correction of infringements to the agreed Service Levels.


'''Process Complaints and Carry out SLA Reviews'''
*Process objective: Investigation of the agreed Service Levels, in order to ensure that the SLAs are still adequate for client requirements; processing of complaints and where necessary, assume corrective measures.


==Involved Roles==
==Involved Roles==
* [[Capacity Management - ITIL V2#Involved Roles|Capacity Manager]]
*[[Capacity Management - ITIL V2#Involved Roles|Capacity Manager]]
* '''<span id="Client">Client (Contract Partner)</span>''': In the first instance the Client is the opposite number of the Service Level Manager during the negotiation of Service Level Agreements. He is therefore responsible for the fact that the defined Service Levels are sufficient for the fulfillment of business objectives, and that the charges estimated for this purpose are justified from the Business perspective.  
*'''<span id="Client">Client (Contract Partner)</span>''': In the first instance the Client is the opposite number of the Service Level Manager during the negotiation of Service Level Agreements. He is therefore responsible for the fact that the defined Service Levels are sufficient for the fulfillment of business objectives, and that the charges estimated for this purpose are justified from the Business perspective.  
* [[Financial Management for IT Services#Involved Roles|Financial Manager]]
*[[Financial Management for IT Services#Involved Roles|Financial Manager]]
* [[IT Service Continuity Management - ITIL V2#Involved Roles|IT Service Continuity Manager]]
*[[IT Service Continuity Management - ITIL V2#Involved Roles|IT Service Continuity Manager]]
* '''<span id="Service-Level-Manager-ITIL-V2">Service Level Manager</span>''': In ITIL V2 the Service Level Manager has the task of caring for the IT Organisation's Service Catalogue and the exact description of the requirements of quality and quantity of the IT Services. Service Level Agreements (SLAs) are agreed upon at the interface with the client. The Service Level Manager is responsible for the monitoring of the agreed quality parameters and if necessary introduces counteractive measures.
*'''<span id="Service-Level-Manager-ITIL-V2">Service Level Manager</span>''': In ITIL V2 the Service Level Manager has the task of caring for the IT Organization's Service Catalogue and the exact description of the requirements of quality and quantity of the IT Services. Service Level Agreements (SLAs) are agreed upon at the interface with the client. The Service Level Manager is responsible for the monitoring of the agreed quality parameters and if necessary introduces counteractive measures.


==Related Checklists and KPIs==
==Related Checklists and KPIs==
==== Checklists ====
 
====Checklists====
*[[Checklist Service Level Agreement (SLA)]]
*[[Checklist Service Level Agreement (SLA)]]
*[[Checklist Operational Level Agreement (OLA)]]
*[[Checklist Operational Level Agreement (OLA)]]
*[[ITIL-Checklists#Service Level Management|More Service Level Management templates ...]]
*[[ITIL-Checklists#Service Level Management|More Service Level Management templates ...]]


==== KPIs ====
====KPIs====
*[[KPIs Service Level Management|Key Performance Indicators "Service Level Management" according to ITIL V2]]
*[[KPIs Service Level Management|Key Performance Indicators "Service Level Management" according to ITIL V2]]
<p>&nbsp;</p>


==Related [[ITIL Glossary]] Terms==
==Related [[ITIL Glossary]] Terms==
* [[ITIL Glossary/_ITIL_Terms_S#Service Level Requirements (SLR)|Service Level Requirements (SLR)]]
*[[ITIL Glossary/_ITIL_Terms_S#Service Level Requirements (SLR)|Service Level Requirements (SLR)]]
* [[ITIL Glossary/_ITIL_Terms_S#Service Specification Sheet|Service Specification Sheet]]
*[[ITIL Glossary/_ITIL_Terms_S#Service Specification Sheet|Service Specification Sheet]]
* [[ITIL Glossary/_ITIL_Terms_S#Service Level Agreement (SLA)|Service Level Agreement (SLA)]]
*[[ITIL Glossary/_ITIL_Terms_S#Service Level Agreement (SLA)|Service Level Agreement (SLA)]]
* [[ITIL Glossary/_ITIL_Terms_S#Service Catalogue|Service Catalogue]]
*[[ITIL Glossary/_ITIL_Terms_S#Service Catalogue|Service Catalogue]]
* [[ITIL Glossary/_ITIL_Terms_O#Operational Level Agreement (OLA)|Operational Level Agreement (OLA)]]
*[[ITIL Glossary/_ITIL_Terms_O#Operational Level Agreement (OLA)|Operational Level Agreement (OLA)]]
* [[ITIL Glossary/_ITIL_Terms_U#Underpinning Contract (UC)|Underpinning Contract (UC)]]
*[[ITIL Glossary/_ITIL_Terms_U#Underpinning Contract (UC)|Underpinning Contract (UC)]]
* [[ITIL Glossary/_ITIL_Terms_S#Service Quality Plan (SQP)|Service Quality Plan (SQP)]]
*[[ITIL Glossary/_ITIL_Terms_S#Service Quality Plan (SQP)|Service Quality Plan (SQP)]]
* [[ITIL Glossary/_ITIL_Terms_S#Service Improvement Plan (SIP)|Service Improvement Plan (SIP)]]
*[[ITIL Glossary/_ITIL_Terms_S#Service Improvement Plan (SIP)|Service Improvement Plan (SIP)]]
* [[ITIL Glossary/_ITIL_Terms_S#Service Level Report|Service Level Report]]
*[[ITIL Glossary/_ITIL_Terms_S#Service Level Report|Service Level Report]]
 
<p>&nbsp;</p>


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Delivery|Service Level Management - ITIL V2]][[Category:Service Level Management]]
[[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Delivery|Service Level Management - ITIL V2]][[Category:Service Level Management]]
<!-- --- -->
<!-- --- -->

Latest revision as of 17:56, 4 February 2016

ITIL V2 Service Level Management
ITIL V2 Service Level Management


ITIL Version: ITIL V2 see also Service Level Management - ITIL V3

Process-Objective: Service Level Management has the tasks of maintaining the IT Organization's Service Catalogue and reaching binding agreements for internal and external Service Performances. At the interface with the client, Service Level Agreements are agreed. The Service Level Manager is responsible for the monitoring of the agreed quality parameters and where necessary resorts to counter-measures. The adequate provision of internal IT Services is secured via Operational Level Agreements and Underpinning Contracts (OLAs/ UCs).

Part of: Service Delivery

Process Owner: Service Level Manager

 

Sub-Processes

Overview of Service Level Management

Maintain Structures for Service Level Management

Process objective: The multitude of documents used within Service Level Management are to be adjusted in such a manner, that they correspond to the requirements of new or changed IT Services.

Define Service Requirements

  • Process objective: Requirements from the client viewpoint with regards to a new or altered IT Service are to be documented and submitted to an initial evaluation, so that alternatives may be developed at an early stage for requirements which are not technically or economically feasible.

Create Service Specification Sheet

  • Process objective: The requirements of a new or altered IT Service are described in more detail, and specifications are drawn up as to how the Service is created from an IT viewpoint and how the invoicing takes place.

Negotiate and agree Contractual Regulations for the Service

  • Process objective: Finalization of binding agreements to an IT Service between the IT Organization and the client-side, a well as ensuring sufficient Service Levels with internal and external Service providers, which support the provision of the Service.

Prepare Service Implementation

  • Process objective: Identification of preconditions, which must be established for the implementation of the new or altered Service, so that a corresponding Change Request may be compiled.

Commission Service Implementation

  • Process objective: After clearance of the Change, the implementation of the IT Service is to be planned in further detail; the Service Level Manager subsequently commissions the technical experts in Application or Infrastructure Management to start the implementation.

Carry out Service Level Reporting

  • Process objective: It is to be given account of the attained Service quality as well as potential counter-measures for the correction of infringements to the agreed Service Levels.

Process Complaints and Carry out SLA Reviews

  • Process objective: Investigation of the agreed Service Levels, in order to ensure that the SLAs are still adequate for client requirements; processing of complaints and where necessary, assume corrective measures.

Involved Roles

  • Capacity Manager
  • Client (Contract Partner): In the first instance the Client is the opposite number of the Service Level Manager during the negotiation of Service Level Agreements. He is therefore responsible for the fact that the defined Service Levels are sufficient for the fulfillment of business objectives, and that the charges estimated for this purpose are justified from the Business perspective.
  • Financial Manager
  • IT Service Continuity Manager
  • Service Level Manager: In ITIL V2 the Service Level Manager has the task of caring for the IT Organization's Service Catalogue and the exact description of the requirements of quality and quantity of the IT Services. Service Level Agreements (SLAs) are agreed upon at the interface with the client. The Service Level Manager is responsible for the monitoring of the agreed quality parameters and if necessary introduces counteractive measures.

Related Checklists and KPIs

Checklists

KPIs

Related ITIL Glossary Terms