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

Current Membership

Latest: VYKP
New Today: 54
New Yesterday: 73
Overall: 150103

People Online:
Visitors: 53
Members: 3
Total: 56 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

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.


The Itil Community Forum: Forums

ITIL :: View topic - Incident Management - KEDB or HDKB?
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Incident Management - KEDB or HDKB?

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


Joined: Apr 27, 2011
Posts: 2

PostPosted: Thu Apr 28, 2011 7:49 am    Post subject: Incident Management - KEDB or HDKB? Reply with quote

I believe that all workarounds should be captured in Known Error Database. Suppose for a particular incident, the Incident Management team is not able to find any documented workaround in the KEDB. Since they have to meet SLAs, lets say that the Incident Management team uses its expertize to come up with a valid workaround that restored service. Now they want this workaround to be added to the KEDB. My question is 1. Once they submit the workaround to Problem Management, should problem mgmt raise a problem record and then map it to a Known Error Record and then add this workaround to KEDB after validating it or Can they add the workaround directly to the KEDB without creating a problem record? 2. What is the recommended way by ITIL v3 in these cases? 3. Should all workarounds reside in one KEDB or is it OK for various Incident Management teams to have their own Knowledge Bases?

Thanks and Regards
Umakant
Back to top
View user's profile
Marcel
Senior Itiler


Joined: Sep 21, 2006
Posts: 63
Location: USA

PostPosted: Thu Apr 28, 2011 11:47 pm    Post subject: Reply with quote

Quote:
1. Once they submit the workaround to Problem Management, should problem mgmt raise a problem record and then map it to a Known Error Record and then add this workaround to KEDB after validating it or Can they add the workaround directly to the KEDB without creating a problem record?


Identifying, vetting, and publishing workarounds is a responsibility of Problem Mgmt. When reviewing the incident(s) that triggered the problem investigation, Problem Mgmt may determine that the on-the-fly corrective action that was taken as part of Incident Mgmt is a valid workaround for the problem that would be fine to use for future occurrences of the problem. Problem Mgmt will then make sure it gets published following whatever mechanism you have in place. For some organizations that may mean to open a Known Error record even though root cause is not known at the time. In other organizations the workaround may be documented in the Problem record because a Known Error would not be raised until after root cause has been determined. This all depends on your implementation (see the other thread you started about having one record vs separate records).

Quote:
2. What is the recommended way by ITIL v3 in these cases?


ITIL does not give a specific recommendation on exactly how to do this. What you will see is that 'workarounds' are a deliverable of the Problem Mgmt process. What you will also find is ambiguity about Known Errors. While defined as a problem for which the root cause is known AND a workaround is available (I'm emphasizing "AND" here), ITIL v3 will also say that a Known Error may be raised earlier if deemed beneficial. Unfortunately no guidance is given as to when this would be beneficial and how this relates to the much stricter definition. You are on your own Very Happy

Quote:
3. Should all workarounds reside in one KEDB or is it OK for various Incident Management teams to have their own Knowledge Bases?


This too is up to you and is truly just a decision about the technical implementation. Having all records in a single database does not mean you can't give each team 'exclusive views' to the records that matter to them. Having separate databases does not mean you can't provide a logical view that pulls records from both databases. Without knowing why you are asking this question, my first response would be to just have a single database (less maintenance) and ensure through functionality and process that the teams don't interfere which each other if that is your concern. Again, it's up to you. No general rules here.
_________________
Manager of Problem Management
Fortune 100 Company
ITIL Certified
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 http://www.nukecops.com

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.