Incident Management Overview at UChicago IT Services


Purpose

Incident management seeks to minimize the negative impact of incidents by restoring normal service operation as quickly as possible.

Definition

An incident is an unplanned interruption to an IT service or a reduction in the quality of an IT service.

Objectives

The objectives of IT Incident Management are to:

Process Flow

At a very high level, the Incident Management process includes eight process activities:

Incident process flow from identification to closure
  • Identification - Incidents are detected and reported.
  • Logging - All relevant information relating to the nature of the Incident must be documented.
  • Categorization & Prioritization - Incidents are categorized and prioritized to facilitate a swift and effective resolution.
  • Initial Diagnosis - A diagnosis is carried out to try to discover the full symptoms of the incident.
  • Escalation - When the Service Desk cannot resolve the incident, the incident is escalated for further support (functional escalation).  If incidents are more serious, the appropriate IT managers must be notified (hierarchic escalation).
  • Investigation & Diagnosis - When there is no known solution, the incident is investigated.
  • Resolution & Recovery - Once the solution (or acceptable workaround) has been found, the issue can be resolved.
  • Incident Closure - The Service Desk confirms that the incident is resolved and that the user is satisfied and then the incident can be closed.

Key Terminology