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: ElbaRicht
New Today: 41
New Yesterday: 66
Overall: 142260

People Online:
Visitors: 69
Members: 0
Total: 69

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

Lost in statistics

 
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message
viv121
Senior Itiler


Joined: Dec 15, 2007
Posts: 113

PostPosted: Fri Mar 19, 2010 6:35 pm    Post subject: Lost in statistics Reply with quote

Hi All,

Came across an interesting query. Like all organizations, my organization is also working on improving on the total age of the incidents. For the baselining purpose, we took the information for the last quarter of 2009 which were around 180,000 helpdesk incidents. To find the age of an Incident, we subtracted the open time and close time to get the age of one incident. We summed up all the ages and divided the number by 180,000 to get a value and we termed it as Baseline MTTR value.

My question is that what we call as MTTR and expand as Mean time to repair, is it actually the average time to repair or should be have the median( 50th percentile of 180,000 datapoints) or midspread/inter-quartile value to be closest to the actual MTTR. In the number of tickets, we will have a number of outliars ( resolved in 1 minute, resolved in 30 days etc) and average might actually not work. From the purist point of view, MTTR is expanded as Mean Time to repair. How would that be expanded from a practical point of view.

We tried some lies and damn lies to the business. Statistics appears to be the last resort.

Not an ITIL question surely but may be a best practice question. Appreciate any help.
_________________
regards,

Vivek
"the only statistics you can trust are those you falsified yourself"
Winston Churchill
Back to top
View user's profile Send e-mail
UKVIKING
Senior Itiler


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

PostPosted: Fri Mar 19, 2010 7:01 pm    Post subject: Reply with quote

Viv

incident 19123 is different from incident 22045

you can do some LDLaS on the following which would treat all incidents the same - all cats are grey at night

key points -
service impacted
raised
initial action by SD
escalate to resolver group
communication with service customers
service restored

This would depend upon whether your tool differentiates in your ticket
between the service impact / restore DTG and the ticket open, last touched, closed DTG

If you merely use the open/close DTG to calc age of the ticket and then gather them all and do standard deviation, average, mean, median, high, low overall.

Take the following into consideration

what tickets are created by SD Staff, via autogenerated email from customer users, automated by NMS / Monitoring / Alerts / etc ; etc

You should divide these into the distinct groups that the LDLaS would reflect more accurately

Thn you take the statistical data that you have gathered, arrange in a periodic manner - monthly, weekly. daily so that you can see if the STDDEV, average, mean, median, high, low for the entire range and each of the periods

The above can be done for tickets that have a classification system of some type associated with it

And then rinse lather repeat for management

But.... what does this really do besides fullfilling some MBA Graduate in a senior mgmt desire to see numbers... {Note: The same can be achieved using random number generation]

The real issue and LDLaS usage should be used this way

Volume by day or hour - where the ticket volume grows - this helps with planning staff numbers

etc
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Fri Mar 19, 2010 7:29 pm    Post subject: Reply with quote

Viv,

didn't like my response yesterday then?

John, of course has it. You have to turn your question on its head. There is no such thing as the "actual...average". Mean, median and mode are all equally valid statistical averages, but they tell you different things.

So, as John said, you identify what you actually want to know and what you want to do with what you want to know and then you apply operations of data recording, gathering and analysing to meet that.

Just to get a bit pedantic (I lost another game of chess last night - that's the only two games I have played for the club this season!) if the purist definition is not the same as the practical definition, then one of them is incorrect.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Back to top
View user's profile Send e-mail
viv121
Senior Itiler


Joined: Dec 15, 2007
Posts: 113

PostPosted: Sat Mar 20, 2010 6:09 am    Post subject: Reply with quote

Diarmid,

How are you managing loss after loss in chess? Who's (check)mating you mate?

John, liked the concept of LDaS really. I'll get into this report generator utility to get some control charts in place. The control chart will help me understand why 19123 is different from incident 22045.

Cheers

Viv
_________________
regards,

Vivek
"the only statistics you can trust are those you falsified yourself"
Winston Churchill
Back to top
View user's profile Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk 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.