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.
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 - Feasibility of working on a problem
Joined: May 23, 2008 Posts: 18 Location: Toronto, ON, Canada
Posted: Tue Mar 10, 2009 12:46 am Post subject: Feasibility of working on a problem
Hello Everyone, wanted to post this to our brain trust to see what (if anything) people are doing on this front. As the problem manager for my organiation I have been tasked with creating a cost/benefit statement to determine if IS should commit resources to working on a particular problem. This is a departure form how we have operated in the past (current economic climate I suppose) where our criteria for identifying and workign on problems reactivley as a result of incidents was enough. So after thinking about this I have developed a crude worksheet to input as much incident information as I can along with estimates for effort to determine root cause. Then using some math convert everything into hours as my common term and then use that to create a "rating" where everything above 1.0 means we save money and below 1.0 means it costs money to work on that specific problem. I've shared the line items below so you have an idea of the questions I am asking. I am really interested to know if anyone was undertaken this kind of evaluation in their process and if so, how are you doing it?
Thanks,
Brian
A Impact Thus Far
How many Incidents Logged?
Avg. time to restore service?
Avg. priority of incidents?
Avg. urgency of incidents?
Resource Impact
Business Impact
Total Impact of Problem
Avg. Impact per Incident
B Potential Impact in next 12 months
Avg. # of Incidents per month
Potential Impact over next year
C Estimate to determine Root Cause & Solution Options
Estimated # of hrs of PbM Mgr
Estimated # of hrs of PbM Assignee
# of SME's required
Estimate # of hrs of SME
Joined: Oct 13, 2006 Posts: 116 Location: South Africa
Posted: Tue Mar 10, 2009 11:41 pm Post subject:
I support any move to make the decision more objective as to whether to work on a specific problem. And the details you've laid out seem to be a good basis.
I think you could extend it quite easily to plan for avoiding incidents that haven't yet occurred - addressing some of the "proactive pm" that John mentions.
But you might also need to include some scenarios or risk/likelihood of fixing. (Maybe this is in your feasibility part.) After all, it's pretty rare that we know in advance how long it's going to take to fix a problem.
Joined: May 23, 2008 Posts: 18 Location: Toronto, ON, Canada
Posted: Wed Mar 11, 2009 1:36 am Post subject:
I'm positioning this as a method to get as far as root cause only because to all of oyur points, you have no idea what the solution is going to look like. I'm going to tackle the proactive part next, wanted to get the easy part done first then build on it. Thanks for the sanity check.
Brian
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