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

THE ITIL BOOKS

The five ITIL books can be obtained directly from the publisher's website:
HERE

Or as downloadable PDFs: HERE

Current Membership

Latest: JasperDumm
New Today: 49
New Yesterday: 101
Overall: 217349

People Online:
Visitors: 154
Members: 1
Total: 155 .

Login
Nickname

Password

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
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.


Search



Languages
Select Interface Language:


Advertising
Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Problem raised to investigate an incident
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Problem raised to investigate an incident

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


Joined: May 18, 2016
Posts: 2

PostPosted: Wed May 18, 2016 5:05 pm    Post subject: Problem raised to investigate an incident Reply with quote

Hi guys,

I'm new to ITIL and I'm currently working in reducing our huge queue of open problems.

I've noticed that a lot of these problems were raised after a single incident only because the user was not happy with closing the incident until more investigation was done regarding the root cause.

Is this the right way to proceed? These are usually low priority incidents so the problem never gets any attention and it just sits there forever.

It seems like the problems should not have been created in the first place and maybe the user should have been told that sadly other incidents have a higher priority and we just can't do a root cause analysis on this at the moment.

Any advice on how to tackle this type of situations?

Thanks for your help Smile
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3575
Location: London, UK

PostPosted: Thu May 19, 2016 4:24 am    Post subject: Reply with quote

You have been hit by one of the most common mis usages of ITIL processes.

First. :Lets talk about Incident Management (IM)

IM goal is to restore the service. Not provide an explanation as to why it happened.
The action that is taken to restore the service is usually all that is required

Service disabled.Server rebooted.
Done. next Incident

Problem mgmt is time consuming and may not result in a solution as the reason may never be known.

The process for PM is in two parts - Reactive and Proactive

Proactive - is when yo look at tyour infrastructure and find Single points of failures or weak IT assets that can or will cause incidents and replace them

Reactive is taking the conditions of a incident (set of incidents) and try to find out the why it is happening.

The way it should go is as follows

An incident is created - the team working on it works to restore the service.
As part of that - they say.. hey this incident should be looked into as a problem.

This is a problem record candidate

The PM Manager would have a set of criteria as to what Problems are going to be worked on - and how much time is to be spent on each and record how much time has been used trying to find the underlying root cause.

Incidents have SLAs
Problems dont.

So if there are 200 PM candidates, the PM manager - says you work on these 3 or 4 and rejects the rest.

This should be stated in your policy documents
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
mvbc85
Newbie
Newbie


Joined: May 18, 2016
Posts: 2

PostPosted: Thu May 19, 2016 2:56 pm    Post subject: Reply with quote

Thanks a lot for the reply, UKVIKING

It all makes sense, and hopefully we'll get to a point where we'll be able to work like that.

For now the main question that I have is about managing the user's expectations.

Should the team push back and let the user know that finding the cause for a low priority one-off incident will not happen?

Or should problems be automatically raised as soon as the user request it and then the Problem Manager have the task of communicating with the user in the case that their problem will not be worked on?

In this case all the users are within the same company, so I would expect them to understand if they are not at the top of the priority list, but maybe that's just wishful thinking
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3575
Location: London, UK

PostPosted: Thu May 19, 2016 3:55 pm    Post subject: Reply with quote

First, are you an internal service desk or do you provide services externally.

Either way, you need to produce a document explaining the purpose and goal of IM and PM

In addition, PM work should be well defined
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
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 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.