Checklist Service Level Requirements (SLR): Difference between revisions

From IT Process Wiki
No edit summary
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''ITIL Process''': [[Service Delivery]] - [[Service Level Management]]
<itpmch><title>Checklist Service Level Requirements (SLR) | IT Process Wiki</title>
<meta name="keywords" content="service level requirements, service level requirement, service level requirements template, itil slr, slr itil" />
<meta name="description" content="The Service Level Requirements (SLR) document contains the requirements of the IT Service from the client viewpoint; it is a for the Service ..." />
</itpmch>
<imagemap>
Image:ITIL-Wiki-deutsch.jpg|right|Checklist Service Level Requirements (SLR) - Template Service Level Requirements (SLR)
default [https://wiki.de.it-processmaps.com/index.php/Checkliste_Service_Level_Requirements_-_SLR diese Seite auf Deutsch]
desc none
</imagemap>
<br style="clear:both;"/>


'''Checklist Category''': [[ITIL-Checklists#Checklists for Service Level Management|Checklists for Service Level Management]]
<p>&nbsp;</p>


'''ITIL Process''': [[ITIL Service Design]] - [[Service Level Management]]
'''Checklist Category''': [[ITIL-Checklists|ITIL Templates]] - Service Level Management
'''Source''': Checklist "Service Level Requirements - SLR" from the ITIL Process Map V2 &nbsp;| &#11208;&nbsp; [https://en.it-processmaps.com/products/itil-process-map.html ITIL Process Map V3]
<p>&nbsp;</p>


The Service Level Requirements document contains the requirements of the IT Service from the client viewpoint; it is a for the Service Specification Sheet and the Service Level Agreement, which further expand the specifications shown here:
The Service Level Requirements document contains the requirements of the IT Service from the client viewpoint; it is a for the Service Specification Sheet and the Service Level Agreement, which further expand the specifications shown here:
Line 31: Line 47:
***** Reaction and resolution times (according to priorities, definition of priorities e.g. for the classification of Incidents)  
***** 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
**** Requirements for the maintenance of the Service in the event of a disaster
<p>&nbsp;</p>
<html>By:&#160;&#160;Stefan Kempter&#160;<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: -->
[[Category:Checklist (ITIL)|Service Level Requirements SLR]]
[[Category:Service Level Management|Service Level Requirements SLR]]
<!-- --- -->

Latest revision as of 20:02, 29 March 2019

Checklist Service Level Requirements (SLR) - Template Service Level Requirements (SLR)
Checklist Service Level Requirements (SLR) - Template Service Level Requirements (SLR)


 

ITIL Process: ITIL Service Design - Service Level Management

Checklist Category: ITIL Templates - Service Level Management

Source: Checklist "Service Level Requirements - SLR" from the ITIL Process Map V2  | ⯈  ITIL Process Map V3

 

The Service Level Requirements document contains the requirements of the IT Service from the client viewpoint; it is a for the Service Specification Sheet and the Service Level Agreement, which further expand the specifications shown here:

  • Name of the Service
  • Clearance information (with location and date)
    • Service Level Manager
    • Client
  • 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

 

By:  Stefan Kempter , IT Process Maps.