Checklist Service Level Agreement (SLA): Difference between revisions
From IT Process Wiki
mNo edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 12: | Line 12: | ||
<p> </p> | <p> </p> | ||
'''→ see also:''' [[Checklist SLA OLA|Checklist SLA | '''→ see also:''' [[Checklist SLA OLA|ITIL Checklist Service Level Agreement SLA]], ''enhanced with many additions'' | ||
'''ITIL Process''': ITIL V2 [[Service Delivery]] - [[Service Level Management]] | '''ITIL Process''': ITIL V2 [[Service Delivery]] - [[Service Level Management]] | ||
| Line 18: | Line 18: | ||
'''Checklist Category''': [[ITIL-Checklists#Checklists for Service Level Management|Checklists for Service Level Management]] | '''Checklist Category''': [[ITIL-Checklists#Checklists for Service Level Management|Checklists for Service Level Management]] | ||
'''Source''': Checklist "Service Level Agreement - SLA" from the [https://en.it-processmaps.com/products/ | '''Source''': Checklist "Service Level Agreement - SLA" from the ITIL Process Map V2 | ⯈ [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3] | ||
<p> </p> | <p> </p> | ||
| Line 31: | Line 31: | ||
** Name of the Service Provider | ** Name of the Service Provider | ||
** Name of the Service recipient | ** Name of the Service recipient | ||
** Contact partners/ persons in charge (on client-side as well as on the side of the IT | ** Contact partners/ persons in charge (on client-side as well as on the side of the IT Organization) for | ||
*** Contractual changes | *** Contractual changes | ||
*** Complaints and suggestions | *** Complaints and suggestions | ||
| Line 71: | Line 71: | ||
* Responsibilities | * Responsibilities | ||
** Of the client (also within the field of IT Security) | ** Of the client (also within the field of IT Security) | ||
** Responsibilities and liability of the IT | ** Responsibilities and liability of the IT Organization | ||
* Quality assurance and Service Level Reporting | * Quality assurance and Service Level Reporting | ||
** Measurement procedures | ** Measurement procedures | ||
| Line 88: | Line 88: | ||
<p> </p> | <p> </p> | ||
<html><a rel="author" href="https:// | <html>By:  Stefan Kempter <a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</html> | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
Latest revision as of 10:59, 30 March 2019
→ see also: ITIL Checklist Service Level Agreement SLA, enhanced with many additions
ITIL Process: ITIL V2 Service Delivery - Service Level Management
Checklist Category: Checklists for Service Level Management
Source: Checklist "Service Level Agreement - SLA" from the ITIL Process Map V2 | ⯈ ITIL Process Map V3
The Service Level Agreement contains the contractually relevant data for an IT Service:
- Name of the IT Service
- Clearance information (with location and date)
- Service Level Manager
- Client representative
- Contact persons
- Name of the Service Provider
- Name of the Service recipient
- Contact partners/ persons in charge (on client-side as well as on the side of the IT Organization) for
- Contractual changes
- Complaints and suggestions
- Escalations in the case of contractual infringements
- Service reviews
- Emergencies
- Contract duration
- Contract start
- Contract end
- Rules for changes to the SLA
- How are requests for change submitted (deletions, additions or changes to components of the SLA)?
- How are the requests for change and their implementation controlled?
- Who is responsible for the clearance of the changes?
- Rules for termination of the SLA
- Service description
- Short description of Service
- Users of the IT Service on the client-side
- Breakdown of the offered Service into Service groups, e.g. along infrastructure components or IT applications
- For each Service group:
- Which Services are offered, e.g.
- Handling of Service interruptions (by telephone, by remote access, on site?)
- User Services (user administration, installation, …)
- What quality is required of the offered Services, e.g.
- Service times
- Availability requirements
- Number of interruptions allowed
- Availability thresholds (xx,xx %)
- Downtimes for maintenance (number of allowed downtimes, pre-notification periods)
- Procedure for announcing interruptions to the Service (planned/ unplanned)
- Performance requirements
- Required capacity (lower/upper limit) for the Service
- Allowed workload/ usage of the Service
- Response times from applications
- Reaction and resolution times (according to priorities, definition of priorities e.g. for the classification of Incidents)
- Requirements for the maintenance of the Service in the event of a disaster
- Which Services are offered, e.g.
- Relations to other IT Services
- Procedures for requesting the IT Service
- Requests possible by telephone/fax/mail, ... (addresses, telephone numbers, etc.)
- Responsibilities
- Of the client (also within the field of IT Security)
- Responsibilities and liability of the IT Organization
- Quality assurance and Service Level Reporting
- Measurement procedures
- Which indicators
- With which measurement procedures
- At which intervals
- Collated into which reports
- SLA Reviews
- Intervals at which SLA reviews are to be held
- Measurement procedures
- Service accounting
- Costs for the provision of the Service
- Accounting method for the Service
- Intervals for invoicing
- Glossary
By: Stefan Kempter 
, IT Process Maps.
