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: AlisaTon
New Today: 20
New Yesterday: 37
Overall: 231705

People Online:
Visitors: 126
Members: 0
Total: 126



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 - Is there a "Root Cause" of KEs from development?!
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Is there a "Root Cause" of KEs from development?!

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

Joined: Apr 02, 2007
Posts: 4

PostPosted: Tue Apr 03, 2007 1:34 am    Post subject: Is there a "Root Cause" of KEs from development?! Reply with quote

Hello all,

New subscriber and keen Service Management chap here I would be interested to hear opinion on something please

An organisation I am working with is starting to push on getting Known Error (KE) info from new and upgraded services. These are highlighted through a formal Service Introduction process.

The KEs are getting logged in the Problem Management tool and assigned appropriately, to be investigated for fixing. That aspect is fine, but there is very recently a call to add the same Root Cause categorisation as is recorded for reactive Problems.

I'm uncomfortable with this as it really feels like it is different information. Capturing the RC info for reactive Problems tells us where we have deficiencies to address - Do you think you can actually have a 'root cause' for a KE that has come from Service Introduction? If so there is surely a requirement to highlight it as non-reactive? It just doesn't feel right!

Any thoughts gratefully received.

Many thanks,
Back to top
View user's profile

Joined: May 14, 2007
Posts: 5
Location: USA

PostPosted: Tue May 15, 2007 1:05 am    Post subject: Release Notes Reply with quote

Understanding your question correctly... Yes you can have RC from Dev. Those are the issues they are still working on or decided not to resolve when going live with the specific change. You definately like to keep track of those in the (logical) KEDB.
Back to top
View user's profile
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.