The Value of Incident Models

An “incident” is defined as an unplanned interruption to an IT service, the reduction in the quality of an IT service or the failure of a CI that has not yet impacted an IT service. The purpose of incident management is to restore a service to normal operations as quickly as possible by minimizing the impact of incidents on IT services.

Incident Management is the process responsible for managing the lifecycle of all incidents by ensuring, that standardized methods and procedures are utilized to record, respond and report on all incidents. Additionally this process should increase the visibility and communication of incidents to the business and the IT support staff and thereby allowing greater alignment of incident management to the overall IT and business strategies.

In a normal IT environment the IT organization may be dealing with a large number of incidents and many of these are repeatable, something that has happened before and very well may happen again in the future. In these instances, it can be advantageous for organizations to create standardized incident models. Through this activity we can create predefined steps for detecting, diagnosing, repairing, recovering and restoring IT services which will allow us to effectively utilize our resources to increase availability or up time.

Incident models should have some basic requirements including:

Steps to be taken to handle the incident.
Predefined chronological order these steps should be taken in, with dependencies defined
Responsibilities of who should do what (even can build some RACI components)
Any precautions that may need to be adhered to.
Time scales and or thresholds.
Escalations procedures if necessary.
Preserve any evidence for later investigations.

By utilizing these simple tools, it can greatly increase the IT supports staffs value and ability to:

Reduce unplanned labor and cost.
Detect and resolve incidents more effective and efficiently. (Less downtime)
Align incident management to current business priorities.
Identify areas of weakness in our environment, through trending historical incident records.
Identify areas for training opportunities for both business and IT staff.

Comments

MMO said…

Thank you for this artcile,
but... "...many of these are repeatable, something that has happened before and very well may happen again in the future..." this the definition of a PROBLEM? itily speaking isn't it?

June 16, 2014 at 6:40 AM

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group. As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...

Search