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.
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.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
I am thinking today about incidents and problems. For me as a "new itilier" is still hard to realize where exactly the border is. According to Itil Operations book, problem is the cause of one or more incidents. When we resolve an incident at some point we find the cause (or the underlying problem) and we are starting to work on resolving that problem so it will not generate any more incidents. So far so good! That means for me that every incident has an underlying problem, sometimes we know it from the beginning, sometimes not. And that arise my doubts. Do we need to register a problem for every incident? If we know the cause at the moment we are informed about an incident what should we register and work on - incident or problem?
Appreciate your help.
Welcome to arguably one of the most confusing aspect of ITIL Service Support (or Service Operations). I've seen a couple discussions that went on for seemingly weeks.
Check the "Does a Major Incident automatically lead to the creation of a problem record?" discussion within LinkedIn's "ITIL v2 / v3 Service Management (ITSM) and ISO 20000 + Subgroups" for more information than you want. _________________ Ruth Mason
USA
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Fri Apr 16, 2010 11:48 pm Post subject:
ruth,
that discussion is almost an advanced course all on its own.
There are at least 6 candidate threads right here and going no further back than last July that also probably help: "Problem v's Incident", "Incident to Problem", "At least one incident ticket must be associated to a problem", "Couple of basic problem management questions!", plus some more you can find easily by their titles.
Victoria,
Be aware from the start that some "experts" insist that any incident should spark off a problem record unless there is already one open that covers it. Others say that that is rubbish and both sides back up their case by referring to ITIL. The most important points are to work out what your own situation requires and don't forget that different people see a different scope for what constitutes a problem.
Two further related "advanced courses" in the same Linkedin group are "What is the root cause in this scenario?" and "Is there a problem in ITIL definition of Problem Management?"
By advanced course, I mean there is an awful lot of reading to do and some of the contributors have strong opinions and you have to sort the wheat from the chaff yourself. Still you've got all weekend now _________________ "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
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Sat Apr 17, 2010 12:42 am Post subject:
Don't blame you, Ruth. It goes on a bit, but there is good material in it and some good contributors even if some of them seem full of themselves at times. _________________ "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