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: QFRGinger9
New Today: 4
New Yesterday: 40
Overall: 236392

People Online:
Visitors: 182
Members: 3
Total: 185 .



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 - Problem Record / Known Error Relationship
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Problem Record / Known Error Relationship

Post new topic   Reply to topic    ITIL Forum Index -> Problem Management
View previous topic :: View next topic  
Author Message

Joined: Oct 28, 2013
Posts: 1

PostPosted: Tue Oct 29, 2013 5:06 am    Post subject: Problem Record / Known Error Relationship Reply with quote

Over the last year I've worked to implement problem management in my

IT dept. While I think we've come a long way (from virtually nothing), I think our process may need some re-working to mature further. One of these re-workings is to implement a KEDB and better utilize the known error process.

Previously, we only use(d) known errors in the instance that the resolution for a problem was not implemented (for whatever reason, ex. maybe too expensive, or something), so we classify the PR as a “Known Error”, because it’s known, and the business accepts the risk, + we have a workaround, and close the PR (it’s “known”…no use to let it needlessly age).

So up to this point our process looks like:

Problem Process:

A PR is opened, worked, root cause identified, workaround applied (in the interim, if needed)“fixed” (eliminated), PR updated and closed. (note that at no time does this become a KE).

Known Error Process:
A PR is opened, worked, root cause identified, workaround applied, but it is not “fixed” b/c the business either accepts the occurrence, or the fix would not be viable, etc. etc., so it is a “known error” in that we know about it, have a workaround, but are not eliminating the root cause.

However, this has caused a few issues:

1) Root causes for problems are usually identified and fixed in short order – ex, a router goes down, it’s found to be faulty hardware, the hardware is replaced, etc. etc. – and in these instances the transition stage to known error seems redundant, however

2) Sometimes things are just “fixed”, instead of having the root cause eliminated, so often we find ourselves closing PR’s when the situation has been remedied, and not asking the Q – what have we done to make sure this never happens again

3) Sometimes the root cause cannot be determined, so what to do with the problem record at that point

So I guess my question is what advice do you have on defining and transitioning b/t PR and KE’s, and what is the status / relationship b/t the closure of either.

Separately, do you do any kind of reviews (monthly?, by criticallity?) by which you look at the active problems, decide what is viable to work on, and what not, or what is an acceptable "root cause" (Ex: Sometimes we known X MPLS will just fail, and we don't have a workaround) and then for one's you either aren't going to dedicate time to, or accept that the workaround is good enough, what to do with those active problem records (since "technically" they haven't been eliminated).

Thanks for any input you can give,
Back to top
View user's profile

Joined: Jan 09, 2013
Posts: 4

PostPosted: Fri Nov 08, 2013 2:02 pm    Post subject: Reply with quote

Interesting question and I imagine that everyone will have a slightly different opinion.

In my humble opinion, once the root cause of a Problem is known, it's no longer a problem but is a Known Error, simply because you know what's causing it now, irrespective of whether you have a workaround or a solution.

In our tool, it's a matter of changing the status from "Problem" to "Known Error", which in itself becomes a KEDB. The trick is to clean it up when Known Errors are eliminated through attrition (system with KE no longer in use), etc...

Known Errors can either be ignored (if there's no impact), managed via application of a workaround, or resolved ("fixed"). How you manage those records is up to you, but we use a mixture of status and closure code which works well enough in our environment. E.g. For one you'd manage via a workaround rather than fix, the status is "Closed" and the Closure Code is "Managed via workaround". A simple search will show you what you need and also provide you with the workaround.

We review weekly, just to make sure our priorities are right and that our workarounds are as robust as possible.
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Problem Management 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.