Posted: Fri Jul 18, 2008 3:08 pm Post subject: Questions on Incident Classification
Dear ITIL gurus,
I learn about ITIL while I am trying to find a good classification of issues. In one of the article "8 Steps to Better Incident Classification" by Hank Marquis in 2006, it mentions that ITIL has described 3 types of incidents:
2) Service Request
3) Assistance Enquiry
and 7 categories:
It has also mentioned an attribute called "Sub-category" with examples:
- Hardware: Workstation, printer, monitor, phone, etc.
- Software: Order Entry, AR/AP, etc.
- Accommondation: Moves, Adds, Changes, etc.
So, my questions are:
1. Are these classifications really defined in ITIL? I have no access to the ITIL publication yet.
2. Are these categories applied to all 3 types of incident? If not, does ITIL define the categories for the other 2 types of incidents?
3. What is the "Accommodation" category? I am confused by the examples.
4. Is there Subcategories defined in ITIL?
5. Which category does "Operating System" or "Security Patch" fitted into?
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Fri Jul 18, 2008 4:58 pm Post subject:
these classifications are examples of possible classification schemes. ITIL does not prescribe anything and therefore if you use these or other classifications you must define for yourself what they mean.
It is, of course generally a very good idea (ITIL best practice) to classify incidents in some way, in order to better manage and analyse your service performance.
so the answers to your questions are as follows:
2. No and no.
3. Whatever you want it to be.
5. whatever one (or more than one) that you want it to.
Personally I don't like to refer to service requests or assistance enquiries (information requests) or (a fourth possible group) change requests as incidents. The reason that some people do is because of the way that their service desk software (or their implementation of it) likes to lump everything that gets recorded as an incident. I like to reserve the word incident for service abberations. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum