www.itsmwatch.com»  ITIL»  Index

8 Steps to Better Incident Classification


Sep 7, 2006
By

Hank Marquis





A Simple Classification Scheme

As I mentioned before, configuration items should form the basis for incident classification. There are two basic methods available: you can classify incidents based on the system or service under question (e.g., “email”); or you can classify on the physical configuration item (e.g., “workstation”).

You could start using physical configuration items and, as you mature and document services using a service catalog, you could expand to include services.

Regardless of classifying on service or configuration item (CI), you should include at least the following three fields: Type, Category, and Sub-category.

The type field helps concentrate the required support, and often aids in prioritization as well. There are three basic types in the ITIL: Fault, Service Request, Assistance Inquiry.

After identifying the type of incident, the category is used to select a technology domain. When setting up your categories try to keep them to as few as possible.

If you are going to have a system based on classification of physical CIs then a simple list of ITIL CI types works well. The ITIL describes the following categories: Hardware, Software, Network, People, Process, Accommodation, and Documentation.

The Sub-category field specifies more detail. Entries will be quite specific to your organization and less generic than type or category. Again, it is best to start with a small list. Following are some examples:

  • Hardware: Workstation, printer, monitor, phone, etc.
  • Software: Order entry, AR/AP, etc.
  • Accommodation: Moves, Adds, Changes, etc.

    Such a classification system might look as follows:

  • Type: Fault
  • Category: Software
  • Sub-category: Database
  • Note: User reports "SQL error" when looking up customer "H.Marquis"

    Notice how user reported symptoms are in the notes. The diagnosis is based on CI, and can now specifically route to the right group for restoration.

    This type of system is pretty easy to develop, and the required scripts are small. You will also find it very effective for routing incidents to the right support group.

    The Benefits

    A simple, yet effective classification system provides many benefits:

  • Quickly finds workarounds and fixes to incidents.
  • Properly routes incidents to the correct support group.
  • Speeds diagnoses by collecting the right information.
  • Helps build and maintain a knowledge base
  • Improves the efficiency of technical groups.
  • Enhances customer satisfaction.
  • Increases user productivity.
  • Establishes a strong base for proactive operations.

    In the end, the benefits far outweigh the work involved.

    Hank Marquis is a managing partner and CTO at itSM Solutions, an ITSM education and mentoring company.



  • Comments  (click to add your comment)

    Comments

      Name or nickname

      Email address

      Website

      Write comment
      You have characters left. (Maximum characters: 1200).

       


      IT Management Daily Newsletter




      Most Popular