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: MPoate
New Today: 50
New Yesterday: 76
Overall: 143388

People Online:
Visitors: 73
Members: 1
Total: 74 .

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

KPIs for Problem Management

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





PostPosted: Fri Nov 11, 2005 8:48 am    Post subject: KPIs for Problem Management Reply with quote

Does anyone have some good KPIs (Key Performance Indicators) for Problem Management in place in their organization? We are trying to gage what constitutes success for Problem Managment and how to best measure our performance. I have done some research and have only found a few measurements.
- MTTR (Mean time to resolve) < X days
- reduce # incidents
- close 50% problems within a month
Back to top
rjp
Senior Itiler


Joined: Mar 12, 2005
Posts: 255
Location: Melbourne, Australia

PostPosted: Sat Nov 12, 2005 4:50 pm    Post subject: Reply with quote

The real objective of problem management is the reduction of incidents - particularly those that are caused by changes.

KPIs for PM should align with this objective and show the how well, over time, it is reducing the volume of incidents.
Back to top
View user's profile Send e-mail AIM Address Yahoo Messenger
eisbergsk
Senior Itiler


Joined: Nov 01, 2004
Posts: 81
Location: Sask, Canada

PostPosted: Tue Nov 15, 2005 8:47 am    Post subject: KPIs for PM Reply with quote

There are excellent KPIs for PM in the ‘Planning to Implement Service Management’ book, organized around 3 Critical Success Factors
1. Improve service quality
2. minimize impact of problems
3. reduce the cost to Users of Problems

Depending on the maturity of your organization, you might have to find variations of these for your organization. It can also help to have indicators that are by month, by quarter, and annual.

One of the earliest KPIs I remember from training is that "PM Nirvana" would be a 1:1:1 ratio between incidents, problems and known errors. At my company, that KPI is best measured year over year.

Hope this helps!
/Sharon
Back to top
View user's profile Send e-mail
alanlm143
Newbie
Newbie


Joined: Dec 06, 2005
Posts: 5

PostPosted: Wed Dec 07, 2005 2:21 am    Post subject: Reply with quote

My 2 Cent input

% Number of problem record closed within the targeted specific time frame.
% reduction of time to implement fixes to known Errors
% reduction of time of undiagnosed problem.
Back to top
View user's profile
javierarcal
Senior Itiler


Joined: May 27, 2005
Posts: 79
Location: Madrid-Spain

PostPosted: Wed Dec 14, 2005 1:21 am    Post subject: More KPIs for problem Managenemt Reply with quote

Hi all,

I am implementing Problem Managenemt rigth now and we are going to work with the following metrics to define OLAs and KPIs

- Time spent since the first incident linked to a problem is opened till the proper problem is opened.

- Time spent between a problem is open till a workaround or a permanent solution is provided.

- MTBF since a problem is closed till the same failure happens again.

- Diffence between the Number of incidents solved in first call before problem managent was implented and afterwards


We try to measure if we are more proative after Problem Management has been implemented.

Hope it helps
Javier
_________________
--
Javier G. Arcal
PhD Engineer by Universidad Politécnica de Madrid
ITIL V3 Accredited Trainer
ITIL Service Manager® Certified by EXIN
ITIL Foundation® Certified by UK ISEB
ITIL Consultant and Trainer
Email: javier.arcal@gmail.com
MSN: javierrmad
Back to top
View user's profile Send e-mail
taiger
Newbie
Newbie


Joined: Dec 28, 2005
Posts: 8
Location: The netherlands

PostPosted: Fri Dec 30, 2005 9:09 pm    Post subject: Reply with quote

Hi all,

i'm thinking of using the following metrics ;

- number of incidents joined to a problem record ( or known error record )
- number of incidents solved by using a workaround
- number of incidents solved by service desk ( should be increasing )
- number of workarounds deliverd by incident management

Regards
Frank
_________________
"if you aim at nothing, that's what you're likely going to hit"
Back to top
View user's profile
rjp
Senior Itiler


Joined: Mar 12, 2005
Posts: 255
Location: Melbourne, Australia

PostPosted: Sun Jan 01, 2006 1:18 am    Post subject: Reply with quote

Reprise:

The final objective of Problem Management is to reduce and prevent incidents - so that is always going to be the main KPI of the PM process outcomes.

You can also attempt to measure the efficiency of the process itself - number of problems resolved by the applicaation of previous solution, or measurements of resource usage - time, materials, etc.

And remember you are looking for changes over time - but not a never-ending trend. It will be 'natural' for incidents to peak after major releases of updated or new technology/services. Analysing the 'rate-of-decay' of those peaks will show you more about improvements in the process that simple month-to-month comparrisons.

BTW: Attenuating the severity of those 'peaks' over time is the responsibility of other processes.
Back to top
View user's profile Send e-mail AIM Address Yahoo Messenger
greeers
Newbie
Newbie


Joined: Aug 23, 2006
Posts: 1

PostPosted: Thu Aug 24, 2006 12:58 am    Post subject: Problem managment KPIs Reply with quote

I am measured on the following:

% assigned calls open longer than target maximum duration
% of all (not just assigned) high priority calls open longer than target maximum duration
% calls raised as a result of trend analysis of incidents

The second one is very problematic to me as there are a low number of high priority problem cases so the change in that measure from month to month tends to be extreme.
Back to top
View user's profile
eisbergsk
Senior Itiler


Joined: Nov 01, 2004
Posts: 81
Location: Sask, Canada

PostPosted: Thu Aug 24, 2006 2:50 am    Post subject: Measuring Problem Mgmt success Reply with quote

There are lots of things that can be measured. The question is, what action do you want to be taken by to whom the measurements get reported ? For my current organization, I report to upper mgmt, & I've had to keep it simple. (Also, make sure to keep the definition of Incident & Problem clear, as has been discussed in other threads):

1. What percentage of Incidents in a month are from 'previously identified but not yet resolved' Problems? Current Target: 20%. Current Reality: 30-40%. Action needed: technical staff must be allowed to develop robust workarounds if resolution is not apparent, and be able to deliver them to the Help Desk quickly. (yeah - its an issue Sad )

2. What percentage of Problems have 0 Incidents after the Problem was first identified? (i.e. Problem mitigated but not resolved)? Current Target: 90%. Current Reality: 80-85%. Action needed: technical staff must be allowed to develop robust mitigation if resolution is not apparent, and be able to implement it quickly. (do you see a pattern? nb. this one HAS improved)

3. How fast are Problems resolved?: Current Target: 80% in 1Quarter. Current Reality: 50-70%. Action needed: technical staff must be allowed to develop solutions, and be able to test, request change & implement them quickly. (yeah, uh huh)

On the plus side, tracking problems that come 'back from the dead' is not an issue because we are so slow and try so hard to make sure that every solution is 'just right', that we have fewer than 2 in a year, and those are usually procedural.

The biggest issue that has emerged is that there is insufficient staff to fight their way through the excessively labourious procedures we have. That's something management can sink their teeth into. I hope. But hey, I'm an optimist. I'm also reporting June & July result in todays Managers meeting, which you will notice is being help on August 23.

"Ever forward, smiling"
/Sharon E.
Back to top
View user's profile Send e-mail
winz
Itiler


Joined: Sep 27, 2006
Posts: 29

PostPosted: Tue Oct 31, 2006 3:02 pm    Post subject: Reply with quote

Hi Folks,

Below is a consolidated list. Some of them might be repeatable, please excuse me for that.

    MTTR (Mean time to resolve) < X days
    Reduced # of incidents
    Close more than 50% problems within a month
    Quality measures
    Reduce the cost to Users of Problems
    % reduction of time to implement fixes to known Errors
    % reduction of time of undiagnosed problem
    Time spent since the first incident linked to a problem is opened till the proper problem is opened.
    Time spent between a problem is open till a workaround or a permanent solution is provided.
    MTBF (Mean Time Between Failures) since a problem is closed till the same failure happens again.
    Number of incidents joined to a problem record ( or known error record )
    Number of incidents solved by service desk ( should be increasing )
    Number of workarounds deliverd by incident management
    % assigned calls open longer than target maximum duration
    % of all (not just assigned) high priority calls open longer than target maximum duration
    % calls raised as a result of trend analysis of incidents
    What percentage of Incidents in a month are from 'previously identified but not yet resolved' Problems? Target: <20%
    What percentage of Problems have 0 Incidents after the Problem was first identified? (i.e. Problem mitigated but not resolved)? Target: 90%
    How fast are Problems resolved?: Target should be: 85%
    Customer Satisfaction Surveys
    Percentage reduction of the impact of Problems on Users
    Percentage reduction in the number of Problems escalated (missed target)
    Increased percentage of proactive Changes raised by Problem Management, particularly from Major Incident and Problem reviews.


Hope this helps...

Cheerz
winz
_________________
"Look at Frustration as a positive thing. It is the frustration that drives you to improve"
Back to top
View user's profile Send e-mail
winz
Itiler


Joined: Sep 27, 2006
Posts: 29

PostPosted: Tue Oct 31, 2006 3:03 pm    Post subject: Reply with quote

Note: Many of the points are taken from the inputs given in the same forum.
_________________
"Look at Frustration as a positive thing. It is the frustration that drives you to improve"
Back to top
View user's profile Send e-mail
itilerfiddler
Newbie
Newbie


Joined: Dec 18, 2006
Posts: 2

PostPosted: Tue Dec 19, 2006 3:02 am    Post subject: QUESTUION FOR WINZ Reply with quote

Hello Winz,



How would you present the following below and in what format, and do you have any examples of your work ? THANK YOU VERY MUCH ALL YOUR INPUT IS GREATLY APPRECIATED !!!!!!!!


Shocked Shocked Shocked Shocked Shocked
Quote:
Hi Folks,

Below is a consolidated list. Some of them might be repeatable, please excuse me for that.



MTTR (Mean time to resolve) < X days
Reduced # of incidents
Close more than 50% problems within a month
Quality measures
Reduce the cost to Users of Problems
% reduction of time to implement fixes to known Errors
% reduction of time of undiagnosed problem
Time spent since the first incident linked to a problem is opened till the proper problem is opened.
Time spent between a problem is open till a workaround or a permanent solution is provided.
MTBF (Mean Time Between Failures) since a problem is closed till the same failure happens again.
Number of incidents joined to a problem record ( or known error record )
Number of incidents solved by service desk ( should be increasing )
Number of workarounds deliverd by incident management
% assigned calls open longer than target maximum duration
% of all (not just assigned) high priority calls open longer than target maximum duration
% calls raised as a result of trend analysis of incidents
What percentage of Incidents in a month are from 'previously identified but not yet resolved' Problems? Target: <20%
What percentage of Problems have 0 Incidents after the Problem was first identified? (i.e. Problem mitigated but not resolved)? Target: 90%
How fast are Problems resolved?: Target should be: 85%
Customer Satisfaction Surveys
Percentage reduction of the impact of Problems on Users
Percentage reduction in the number of Problems escalated (missed target)
Increased percentage of proactive Changes raised by Problem Management, particularly from Major Incident and Problem reviews.
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.