Skip to main content

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?

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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 than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th