Checklist Incident Escalation: Difference between revisions

From IT Process Wiki
No edit summary
 
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''ITIL Process''': [[Service Support]] - [[Service Desk and Incident Management]]
<itpmch><title>Checklist Incident Escalation | IT Process Wiki</title>
<meta name="keywords" content="incident escalation, incident escalation process" />
<meta name="description" content="The Escalation of Incidents follows pre-defined rules: Defined triggers for Escalations, i.e. combinations of degree of severity of an Incident ..." />
</itpmch>
<imagemap>
Image:ITIL-Wiki-deutsch.jpg|right|Checklist Incident Escalation - Template Incident Escalation
default [https://wiki.de.it-processmaps.com/index.php/Checkliste_Incident-Eskalation diese Seite auf Deutsch]
desc none
</imagemap>
<br style="clear:both;"/>


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


'''ITIL Process''': [[ITIL Service Operation]] - [[Incident Management]]
'''Checklist Category''': [[ITIL-Checklists|ITIL Templates]] - Incident Management / Service Desk
'''Source''': Checklist "Incident Escalation" 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 Escalation of Incidents follows pre-defined rules:
The Escalation of Incidents follows pre-defined rules:
Line 9: Line 25:
**Degree of severity of an Incident (severe Incidents are, for example, immediately escalated)
**Degree of severity of an Incident (severe Incidents are, for example, immediately escalated)
**Duration (an Escalation occurs, if the Incident was not resolved within a pre-determined period, as for example the maximum resolution times agreed within the SLAs)
**Duration (an Escalation occurs, if the Incident was not resolved within a pre-determined period, as for example the maximum resolution times agreed within the SLAs)
**In an ideal case this would be system-controlled triggered by customisable Escalation rules   
**In an ideal case this would be system-controlled triggered by customizable Escalation rules   
*Defined Escalation levels in the form of an Escalation Hierarchy, for example
*Defined Escalation levels in the form of an Escalation Hierarchy, for example
**1st Level Support
**1st Level Support
Line 16: Line 32:
**CIO  
**CIO  
*Assigned triggers to the Escalation Hierarchy (conditions/ rules, which lead to the Escalation to a particular level within the Escalation Hierarchy)
*Assigned triggers to the Escalation Hierarchy (conditions/ rules, which lead to the Escalation to a particular level within the Escalation Hierarchy)
<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)|Incident Escalation]]
[[Category:Incident Management|Incident Escalation]]
<!-- --- -->

Latest revision as of 18:58, 29 March 2019

Checklist Incident Escalation - Template Incident Escalation
Checklist Incident Escalation - Template Incident Escalation


 

ITIL Process: ITIL Service Operation - Incident Management

Checklist Category: ITIL Templates - Incident Management / Service Desk

Source: Checklist "Incident Escalation" from the ITIL Process Map V2  | ⯈  ITIL Process Map V3

 

The Escalation of Incidents follows pre-defined rules:

  • Defined triggers for Escalations, i.e. combinations of
    • Degree of severity of an Incident (severe Incidents are, for example, immediately escalated)
    • Duration (an Escalation occurs, if the Incident was not resolved within a pre-determined period, as for example the maximum resolution times agreed within the SLAs)
    • In an ideal case this would be system-controlled triggered by customizable Escalation rules
  • Defined Escalation levels in the form of an Escalation Hierarchy, for example
    • 1st Level Support
    • Incident Manager
    • Manager of Data Processing Centre
    • CIO
  • Assigned triggers to the Escalation Hierarchy (conditions/ rules, which lead to the Escalation to a particular level within the Escalation Hierarchy)

 

By:  Stefan Kempter , IT Process Maps.