Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
· Home
· Content
· Feedback
· News
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: IngridMc
New Today: 25
New Yesterday: 34
Overall: 231597

People Online:
Visitors: 127
Members: 2
Total: 129 .



Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

NOTE: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


Select Interface Language:

Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Incident Classifications
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Incident Classifications

Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message

Joined: May 24, 2006
Posts: 14

PostPosted: Thu May 25, 2006 1:48 am    Post subject: Incident Classifications Reply with quote

Hello ITIL folk,

I am trying to come up with some new classifications for our call types that come through our service desk but we are having probelms deciding how to best classify the incidents.

Should we classify them by symptom, or service offered, or service affected... etc...?

Any help here would be much appreciated.
Thanks in advance,
Back to top
View user's profile

Joined: Jun 01, 2006
Posts: 3
Location: Norway

PostPosted: Thu Jun 01, 2006 6:07 pm    Post subject: Reply with quote

We recently had a huge debate on how to classify our incidents and came up with the following principle:

Always log what the customer or user describes as the symptoms, and connect them to the service the customer or user states beeing affected.

Our "inbound" classification should always give answer to the question: What is the customer trying to do (class.), but can't, and where (service) is he or she trying to do it?

We then added an "outbound" classification, to answer the question "what did WE do to resolve the incident?" (to be filled out before closing the ticket).

By doing it like this, we hope to faciliate knowledge management, and re-use solutions by searching on the symptoms, rather than the solution.

Good luck, BAX.

J. Bryde
The Norwegian Correctional Services IT-Centre
Back to top
View user's profile Visit poster's website

Joined: May 24, 2006
Posts: 14

PostPosted: Thu Jun 01, 2006 6:18 pm    Post subject: Reply with quote

Many thanks for your reply.

That does make a lot of sense and would solve the problem of trying to fit our current classifications (based on symptoms) in to our intended classifications (based on service).

I will feed this in to our debates and hopefully it will put us on the right tracks.

Thanks again for your time.
Paul R Baxter
IT Support Analyst/DBA
University of Leeds, UK
Back to top
View user's profile

Joined: May 24, 2006
Posts: 14

PostPosted: Wed Jun 14, 2006 8:20 pm    Post subject: Further Assistance Required Reply with quote

Hello Again, sorry to dig this one up...

We are looking at defining our incident classifications based on:

Service >> System >> Incident

Service is the service lifted from our service definitions (e.g. email services)
System is the system affected ( e.g. Outlook Exchange) regardless of server or client issue
and Incindent is the nature of the call - i.e. Login problem, client issue, Quota increase request ....etc....

We feel this structure is good but have a problem...
The problem we are having, is that the list of incidents seems too generic for some call types, but for others, we can go in to great detail.

For example:
For logging Calls relating to our student service system we have:

Student Service Systems >> JoeBloggs Student Info System >> Login Problem, Functional Issue, Connection Issue.

As for Outlook Exchange types:

Email Services >> Outlook Exchange >> Login Problems, Outlook client issues, GAL Issues, etc.. the list goes on...

So the difference between these two is that one of them shows all types of symptoms and the other is more classified in to Access problem, functional problem, connection problem.

We seek consistency in our incident types. should we have a list of all possible symptoms or have them more generic and less descript?
There are benefits and drawbacks to each , but we dont want a mixture of the two.

We are nearly there, so any advice on this would be most useful!!!
Many thanks in advance,
Paul R Baxter
IT Support Analyst/DBA
University of Leeds, UK
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk All times are GMT + 10 Hours
Page 1 of 1

Jump to:  
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

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003

Forums ©


Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.