Objective: ITIL Incident Management aims to manage the lifecycle of all Incidents. The primary objective of Incident Management is to return the IT service to users as quickly as possible.
Part of: Service Operation
Process Owner: Incident Manager
Incident Management according to ITIL V3 distinguishes between Incidents (Service Interruptions) and Service Requests (standard requests from users, e.g. password resets). Service Requests are no longer fulfilled by Incident Management; instead there is a new process called Request Fulfilment.
There is a dedicated process in ITIL V3 for dealing with emergencies ("Handling of Major Incidents"). Furthermore a process interface was added between Event Management and Incident Management. Significant Events are triggering the creation of an Incident.
ITIL 2011 describes Incident Management in greater detail:
Guidance has been improved in Incident Management on how to prioritize an Incident (see Checklist Incident Prioritization Guideline).
Additional steps have been added to Incident Resolution by 1st Level Support to explain that Incidents should be matched (if possible) to existing Problems and Known Errors.
Incident Resolution by 1st Level Support and Incident Resolution by 2nd Level Support have been considerably expanded to provide clearer guidance on when to invoke Problem Management from Incident Management. The emphasis is now on restoring services as quickly as possible, and to seek the help of Problem Management if the underlying cause of an Incident cannot be resolved with a minor Change and/or within the committed resolution time.
The Incident Management sub-process Incident Closure and Evaluation now states more clearly that it is important to check whether there are new Problems, Workarounds or Known Errors that must be submitted to Problem Management.
The process overview of ITIL Incident Management is showing the most important interfaces (see Figure 1).
These are the ITIL Incident Management sub-processes and their process objectives:
Incident Management Support
- Process Objective: ITIL Incident Management Support aims to provide and maintain the tools, processes, skills and rules for an effective and efficient handling of Incidents.
Incident Logging and Categorization
- Process Objective: To record and prioritize the Incident with appropriate diligence, in order to facilitate a swift and effective resolution.
Immediate Incident Resolution by 1st Level Support
- Process Objective: To solve an Incident (service interruption) within the agreed time schedule. The aim is the fast recovery of the IT service, where necessary with the aid of a Workaround. As soon as it becomes clear that 1st Level Support is not able to resolve the Incident itself or when target times for 1st level resolution are exceeded, the Incident is transferred to a suitable group within 2nd Level Support.
Incident Resolution by 2nd Level Support
- Process Objective: To solve an Incident (service interruption) within the agreed time schedule. The aim is the fast recovery of the service, where necessary by means of a Workaround. If required, specialist support groups or third-party suppliers (3rd Level Support) are involved. If the correction of the root cause is not possible, a Problem Record is created and the error-correction transferred to Problem Management.
Handling of Major Incidents
- Process Objective: To resolve a Major Incident. Major Incidents cause serious interruptions of business activities and must be resolved with greater urgency. The aim is the fast recovery of the service, where necessary by means of a Workaround. If required, specialist support groups or third-party suppliers (3rd Level Support) are involved. If the correction of the root cause is not possible, a Problem Record is created and the error-correction transferred to Problem Management.
Incident Monitoring and Escalation
- Process Objective: To continuously monitor the processing status of outstanding Incidents, so that counter-measures may be introduced as soon as possible if service levels are likely to be breached.
Incident Closure and Evaluation
- Process Objective: To submit the Incident Record to a final quality control before it is closed. The aim is to make sure that the Incident is actually resolved and that all information required to describe the Incident's life-cycle is supplied in sufficient detail. In addition to this, findings from the resolution of the Incident are to be recorded for future use.
Pro-Active User Information
- Process Objective: To inform users of service failures as soon as these are known to the Service Desk, so that users are in a position to adjust themselves to interruptions. Proactive user information also aims to reduce the number of inquiries by users. This process is also responsible for distributing other information to users, e.g. security alerts.
Incident Management Reporting
- Process Objective: ITIL Incident Management Reporting aims to supply Incident-related information to the other Service Management processes, and to ensure that that improvement potentials are derived from past Incidents.
The following ITIL terms and acronyms (information objects) are used in the ITIL Incident Management process to represent process outputs and inputs:
- An Incident is defined as an unplanned interruption or reduction in quality of an IT service (a Service Interruption).
Incident Escalation Rules
- A set of rules defining a hierarchy for escalating Incidents, and triggers which lead to escalations. Triggers are usually based on Incident severity and resolution times. See also: Checklist Incident Priority
Incident Management Report
- A report supplying Incident-related information to the other Service Management processes.
- An Incident Model contains the pre-defined steps that should be taken for dealing with a particular type of Incident. This is a way to ensure that routinely occurring Incidents are handled efficiently and effectively.
Incident Prioritization Guideline
- The Incident Prioritization Guideline describes the rules for assigning priorities to Incidents, including the definition of what constitutes a Major Incident. Since Incident Management escalation rules are usually based on priorities, assigning the correct priority to an Incident is essential for triggering appropriate escalations. See also: Checklist Incident Prioritization Guideline
- A set of data with all details of an Incident, documenting the history of the Incident from registration to closure. An Incident is defined as an unplanned interruption or reduction in quality of an IT service. Every event that could potentially impair an IT service in the future is also an Incident (e.g. the failure of one hard-drive of a set of mirrored drives). See also: ITIL Checklist Incident Record
Incident Status Information
- A message containing the present status of an Incident sent to a user who earlier reported a service interruption. Status information is typically provided to users at various points during an Incident's lifecycle.
- Major Incidents cause serious interruptions of business activities and must be solved with greater urgency. See also: Checklist Incident Priority: Major Incidents.
Major Incident Review
- A Major Incident Review takes place after a Major Incident has occurred. The review documents the Incident's underlying causes (if known) and the complete resolution history, and identifies opportunities for improving the handling of future Major Incidents.
Notification of Service Failure
- The reporting of a service failure to the Service Desk, for example by a user via telephone or e-mail, or by a system monitoring tool.
Pro-Active User Information
- A notification to users of existing or imminent service failures even if the users are not yet aware of the interruptions, so that users are in a position to prepare themselves for a period of service unavailability.
- An inquiry regarding the present status of an Incident or Service Request, usually from a user who earlier reported an Incident or submitted a request.
- A request to support the resolution of an Incident or Problem, usually issued from the Incident or Problem Management processes when further assistance is needed from technical experts.
- Escalation regarding the processing of an Incident or Service Request, initiated by a user experiencing delays or a failure to restore their services.
- Self-help information for users supplied by the Service Desk, usually as part of the Support Pages on the intranet.
Templates | KPIs
- Key Performance Indicators (KPIs) Incident Management
- Incident Management templates and checklists:
Roles | Responsibilities
Incident Manager - Process Owner
- The Incident Manager is responsible for the effective implementation of the Incident Management process and carries out the corresponding reporting. He represents the first stage of escalation for Incidents, should these not be resolvable within the agreed Service Levels.
1st Level Support
- The responsibility of 1st Level Support is to register and classify received Incidents and to undertake an immediate effort in order to restore a failed IT service as quickly as possible. If no ad-hoc solution can be achieved, 1st Level Support will transfer the Incident to expert technical support groups (2nd Level Support). 1st Level Support also keeps users informed about their Incidents' status at agreed intervals.
2nd Level Support
- 2nd Level Support takes over Incidents which cannot be solved immediately with the means of 1st Level Support. If necessary, it will request external support, e.g. from software or hardware manufacturers. The aim is to restore a failed IT service as quickly as possible. If no solution can be found, the 2nd Level Support passes on the Incident to Problem Management.
3rd Level Support
- 3rd Level Support is typically located at hardware or software manufacturers (third-party suppliers). Its services are requested by 2nd Level Support if required for solving an Incident. The aim is to restore a failed IT Service as quickly as possible.
Major Incident Team
- A dynamically established team of IT managers and technical experts, usually under the leadership of the Incident Manager, formulated to concentrate on the resolution of a Major Incident.
|Responsibility Matrix: ITIL Incident Management|
|ITIL Role / Sub-Process [Details]||Incident Manager||1st Level Support||2nd Level Support||Major Incident Team||Applications Analyst||Technical Analyst||IT Operator|
|Incident Management Support||AR||-||-||-||-||-||-|
|Incident Logging and Categorization||A||R||-||-||-||-||-|
|Immediate Incident Resolution by 1st Level Support||A||R||-||-||-||-||-|
|Incident Resolution by 2nd Level Support||A||-||R||-||R||R||R|
|Handling of Major Incidents||AR||R||-||R||-||-||R|
|Incident Monitoring and Escalation||AR||R||-||-||-||-||-|
|Incident Closure and Evaluation||A||R||-||-||-||-||-|
|Pro-Active User Information||A||R||-||-||-||-||-|
|Incident Management Reporting||AR||-||-||-||-||-||-|
 A: Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Incident Management process.
 R: Responsible according to the RACI Model: Those who do the work to achieve a task within Incident Management.
 see → Role descriptions...
 In cooperation, as required. 2nd Level Support Groups often include Applications Analysts and/ or Technical Analysts.
Watch the video: "The ITIL Process Map - Introduction" [Duration: 10:58 min.]
The introductory ITIL Process Map video shows samples of the ITIL process templates with contents from Service Operation and Incident Management processes, including the
- high-level view of the ITIL Service Lifecycle (Level 0)
- overview of the Service Operation process (Level 1)
- overview of ITIL Incident Management (Level 2)
- detailed process flow for the process "Incident Management: Incident Resolution by 1st Level Support" (Level 3)
[ Infobox ]
|Link to this page:||http://wiki.en.it-processmaps.com/index.php/Incident_Management|
|Languages:||English | Deutsch | español|
|Image:||ITIL Incident Management (.JPG)|
|Author:||Stefan Kempter, IT Process Maps|