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: KGoodisso
New Today: 17
New Yesterday: 49
Overall: 146046

People Online:
Visitors: 80
Members: 0
Total: 80

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 - How does ITIL define unresolve issue or unresolvable issues
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

How does ITIL define unresolve issue or unresolvable issues

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


Joined: Jul 11, 2007
Posts: 2

PostPosted: Wed Jul 11, 2007 6:49 pm    Post subject: How does ITIL define unresolve issue or unresolvable issues Reply with quote

Does anybody know how ITIL would be dealing with unresolvable issues? i.e. issue that have no resolution or are to costly to resolve etc ...
Back to top
View user's profile
dboylan
Senior Itiler


Joined: Jan 03, 2007
Posts: 189
Location: Redmond, WA

PostPosted: Wed Jul 11, 2007 11:02 pm    Post subject: Reply with quote

Yes, ITIL says that any Incident that cannot be resolved (the Service cannot be restored) should be referred to the Problem Management process. The Problem Management Process will do the necessary analysis to determine the Root Cause, CI at fault, and Workarounds. If Problem Management is unable to determine Root Cause, workaround or CI at fault, then it remains an open Problem in the Problem Management database.

The fact that the Problem has never been changed to Known Error doesn't prevent Problem Management from raising a Request for . But the Change Management process must be aware that the risk of failure for a Change applied to an undiagnosed Problem is much higher than for a Change for a Problem that that has been investigated to the Known Error stage. But ultimately it is the responsibility of the Change approvers to either accept the risk and approve the Change Request, or deny it and continue to live with the failed infrastructure.
Back to top
View user's profile
ThomasL
Newbie
Newbie


Joined: Jul 11, 2007
Posts: 2

PostPosted: Wed Jul 11, 2007 11:29 pm    Post subject: Reply with quote

Thanks for that explanation, so that would suggest that I would have to keep the issue open as no resolution was provided. Is that correct?
Back to top
View user's profile
dboylan
Senior Itiler


Joined: Jan 03, 2007
Posts: 189
Location: Redmond, WA

PostPosted: Thu Jul 12, 2007 3:07 am    Post subject: Reply with quote

That is correct. And it is not unusual to have multiple unresolved/open Problems in the Problem Management Database.

Assuming you have an active PM system and limited resources, the Problem team should focus on high priority Problems. Low priority Problems may never get the required attention for proper investigation.
Back to top
View user's profile
LizGallacher
Senior Itiler


Joined: Aug 31, 2005
Posts: 550
Location: UK

PostPosted: Thu Jul 12, 2007 8:52 am    Post subject: Reply with quote

Remember that relatively low priority Problems may be the cause of numerous repat incidents and downtime, even if the impact of each is small. Over time, the workload on the Service Desk and the impact to the business mounts up. High Priority Problems will always get attention (Whether you have formal Problem management in place or not - eradicating repeated low priority incidents never gets the same time spent on it. So, don't forget those lower priority ones!!
_________________
Liz Gallacher,
ITIL EXPERT
Accredited ITIL and ISO/IEC20000 Trainer and Consultant - Freelance
Back to top
View user's profile Send e-mail 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 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.