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: RWessel
New Today: 17
New Yesterday: 53
Overall: 145938

People Online:
Visitors: 62
Members: 4
Total: 66 .

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 - Problem Resolve tool
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Problem Resolve tool

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


Joined: Sep 11, 2007
Posts: 2

PostPosted: Wed Sep 12, 2007 12:53 am    Post subject: Problem Resolve tool Reply with quote

Hello!

First post.

I started working as a Problem Manager for a large account this summer. At any given moment we have around 400 open problem records, our team consists of 10 people, and we deal with about 100 diffrent systems.

ITIL and Problem Management is very new to me, I have worked as a software developer for the last 10 years, but wanted to try something new. I still have a _lot_ to learn, but have not regreted my decision a single moment.

Anyway, let me get to the point(s):

Can you recommend any tools for problem determination?
Has anyone come up with a "Cheat-Sheet" for problem management?
And just for the heck of it; what is your definition of an excellent Root Cause?

Thanks, and have a nice day.
Anders.
Back to top
View user's profile
JoePearson
Senior Itiler


Joined: Oct 13, 2006
Posts: 116
Location: South Africa

PostPosted: Wed Sep 12, 2007 5:14 am    Post subject: Reply with quote

OK ... Problem Management day.

Hi Anders - welcome!

I'll assume that your organisation has a clear and ITIL-consistent distinction between incidents and problems. If that's not the case, post back.

Do your responsibilities include resolving problems - or managing the process?

Problem determination tools and cheat-sheets are usually technology specific, and focused on resolution rather than process. There are some problem determination techniques, like Ishikawa diagrams (start with Wikipedia), that are generic and useful - especially for those most pleasant of problems, the inter-disciplinary ones.

But I hope you're managing the process - logging and tracking at least - because if no one is, then your company isn't doing problem management.

The first thing you should do is some analysis of common characteristics of problems - are particular services, technologies, departments, etc commonly involved. Those areas might benefit from p-d tools and cheat sheets (even standard diagnostic scripts or knowledge base articles that can go back to the Service Desk).

And ... root causes. A root cause is the cause which, if rectified, will prevent the problem from recurring, in the most efficient way and with the widest scope. By most efficient I mean you can't get a greater quality improvement by going back to the cause of the root cause (everything is caused by something else, but eventually you get diminishing returns. And by widest scope I mean you don't just fix the known error in one place, you fix it everywhere.

An example which I picked up years ago:
- a service outage occurred
- the outage was caused by an apparent server crash, but the crash was in fact a controlled automatic shutdown
- the shutdown was caused by a thermal overload being detected
- the thermal overload was caused by the server getting too hot, which was caused by the room getting too hot (possible causes relating to the server fans and the rack fans being faulty were eliminated)
- the cause of the room getting too hot was a failure of a room temperature sensor (possible cause relating to the aircon units was eliminated)
- the failure of the sensor was due to not following prescribed maintenance checks (not a product quality problem)

By ensuring that maintenance procedures for all environmental items are correctly followed (in all server rooms!) a greater and more sustainable prevention of future problems is achieved than if the aircon was serviced, or the single sensor replaced.
Back to top
View user's profile Visit poster's website
jpgilles
Senior Itiler


Joined: Mar 29, 2007
Posts: 123
Location: FRance

PostPosted: Thu Sep 13, 2007 10:29 pm    Post subject: Reply with quote

thanks Joe: that's a wonderful example of what a root cause is....

However, let me challenge you on this: just for fun and also to highlight some issue with cause determination and how far to go....

The reason why prescribed maintenance checks were not followed was because the maintenance folks were not serious at work and spent more time talking than working.

The reason for this was:
option 1) for what they are paid, they think what they do is enough
option 2) HR insisted on selected somebody with broader skills than required so they would be capable of evolutions and the guys got bored.

1) the change required to fix the situation in option 1 would be: upgrade their salary
2) the one required in option 2 would be : fire the HR department head

A common solution would be : get that service outsourced to a third party with signed SLA where they would have to pay penalty fees is the situation happens again....
_________________
JP Gilles
Back to top
View user's profile Send e-mail
JoePearson
Senior Itiler


Joined: Oct 13, 2006
Posts: 116
Location: South Africa

PostPosted: Tue Sep 18, 2007 12:39 am    Post subject: Reply with quote

Smile

But the maintenance was already outsourced. The outsource provider management underpaid its staff and promised them greater job satisfaction so both your 1 and 2 apply. Also, the staff were not as motivated in the success of the client company as the previous in-house staff were. The outsource company invested most of its resources in lawyers to write tight contracts and fight any claims for penalty pay-outs. Root cause: bad contract. Possible solution: in-source those maintenance functions! Very Happy
Back to top
View user's profile Visit poster's website
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.