Last updated on: June 25, 2020
- Incident definition
- ITIL incident management life cycle/process flow
- Incident management roles and responsibilities
- Incident management best practices
- Incident management benefits and advantages
- Incident management software feature checklist
- Incident management KPIs
- Difference between incident, problem, change and asset
- ITIL glossary for incident management
ITIL glossary for incident management
An unplanned interruption to an IT service or reduction in the quality of an IT service. Failure of a configuration item, even if it has not yet affected a service, is also an incident (e.g. failure of one disk from a mirror set).
The process of discovering an incident.
Creating and maintaining a record of an incident in the form of a ticket.
Recording an incident with due diligence so that it's placed under the appropriate category.
Closing an open incident ticket once the incident has been resolved.
Incident escalation rules
A set of rules defining the hierarchy for escalating incidents, including triggers that lead to escalations. Triggers are usually based on incident severity and resolution time.
Managing the life cycle of all incidents to restore normal service operation as quickly as possible and minimize business impact.
Incident management report
A series of reports produced by the incident manager for various target groups (e.g. teams responsible for IT management, service level management, other service management processes, or incident management itself).
The person responsible for the effective implementation of the incident management process and carrying out reporting. Also represents the first stage of escalation if an incident is not able to be resolved within the agreed service level.
Contains the predefined steps that should be taken to deal with a particular type of incident.
Tracking 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.
Assigning priorities to incidents and defining what constitutes a major Incident.
A collection of data with all details of an incident, documenting the history of the incident from registration to closure.
A report that includes information about incidents, how they were handled, and other data that can help measure the performance of the incident management process.
The workaround or correction that fixes the incident and restores service to its best quality.
How far along an incident is in the incident management process. Common statuses include:
- New : An incident that has been logged but not yet worked on.
- Assigned : An incident that has been received in the IT help desk and assigned to a technician.
- In progress : An incident that has been assigned to a technician and is in the process of receiving a resolution.
- On hold or pending : An incident that has been temporarily put on hold.
- Resolved : An incident that was worked on by a technician and has received a resolution.
- Closed : An incident that was closed once the resolution was acknowledged by the end user.
Incident management implementation kit
An exclusive package of a feature checklist and incident management presentations.
Comprehensive list of must-have features that you can use as a benchmark for your IT service desk.
Detailed presentations with specific use cases to get started with ITIL incident management.