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: pearlieil2
New Today: 28
New Yesterday: 27
Overall: 231740

People Online:
Visitors: 155
Members: 0
Total: 155



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 categories ->Symptoms & Problem categories-&
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Incident categories ->Symptoms & Problem categories-&

Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion
View previous topic :: View next topic  
Author Message
Senior Itiler

Joined: May 27, 2005
Posts: 79
Location: Madrid-Spain

PostPosted: Sat Dec 17, 2005 1:35 am    Post subject: Incident categories ->Symptoms & Problem categories-& Reply with quote


I am implementing problem management, in a big company, we are thinking in defining different categories for Incident Management and for problem management.

Our idea is that Incident Management categories will be based in the symptoms of the failure detected and that Problem Management will base its categories in the true root cause of the problem.

For e.g. In a web application many users have “Error Http:// 500” so they cannot authenticate, we can classified this incident as “Software->Application->User authentication”

Afterwards Problem Management team detected is a problem of data base configuration, so the problem associated to this incidents will be classified as “Software->Database->Configuration”

Please let me know you thoughts about defining:

Incident categories based in Symptoms

Problem categories based in Root cause
Javier G. Arcal
PhD Engineer by Universidad Politécnica de Madrid
ITIL V3 Accredited Trainer
ITIL Service Manager® Certified by EXIN
ITIL Foundation® Certified by UK ISEB
ITIL Consultant and Trainer
MSN: javierrmad
Back to top
View user's profile Send e-mail

Joined: May 13, 2004
Posts: 31

PostPosted: Sat Dec 17, 2005 9:31 am    Post subject: Interesting. Reply with quote

Sounds interesting. I like your concept. But keep in mind that you have to relate the Incidents to the Problems in a one to one or a one to many basis.

My main concern here would be not necessarily the technicalities of having Incident records and Problem records related, but rather the metrics and reporting. So for example if I wanted to have reports Problems and the Incidents they cause, I want to make sure that I'm catching all the related records. I would not want to have a report in which I miss an Incident or two. My rationale being that usually a single Problem is linked to multiple Incidents.

This is just a very technical (tool related) concern. Your original idea about having different categories for Incidents and Problems is excellent.


audentes fortuna juvat
Back to top
View user's profile MSN Messenger

Joined: Jan 17, 2006
Posts: 13
Location: France

PostPosted: Thu Jan 19, 2006 7:25 am    Post subject: Base your incident categories on the services you provide... Reply with quote

I think it is an excellent approach. Base your incident categories on the services you provide, and the type of Incident the user faces... it will be easier to categorize for the support team, will match the customer point of view.

For categorizing the problems, use a "root cause" approach. This is what will make most sense from the problem management point of view.

Regaring the reporting question, as incidents should be linked to problems, you should not have any orphean problems, and should be able to build the reports you need, if your reporting tool allows for it...
Better have remorse than regrets Wink
Back to top
View user's profile Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Discussion 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.