20 Easy to Use ITIL Metrics
posted by John Spacey, June 27, 2016ITIL breaks major IT functions down into nice bite sized processes — ripe to be measured with metrics. Here are 20 of our favorite metrics for ITIL processes:
Incident and Problem Management
1. Percentage of Incidents Resolved by First Level SupportSupport costs can be dramatically reduced when first line support resolves basic issues such as user training, password problems, menu navigation issues etc... The target for this metric is often set above 80%.
2. Mean Time to Repair (MTTR)
Average time to fix an incident. Often the most closely watched ITIL related metric. It is not unusual for MTTR reporting to go to CxO level executives.
3. Percentage of Incidents Categorized as Problems
The percentage of incidents that are deemed to be the result of problems.
4. Problems Outstanding
The total number of problems that are unresolved.
Service Desk
5. Missed CallsThe number of times someone called the help desk, were put on hold and eventually hung up. May include the number of times someone called when the help desk was closed. Impacts customer service and core metrics such as MTTR.
6. Customer Satisfaction
Usually captured in a survey. Try not to go overboard: asking for feedback in an inappropriate way can irritate customers.
7. Staff Turnover
Service Desk jobs can be stressful — retaining experienced staff is critical to optimizing core ITIL metrics.
Change Management
8.Number of Successful Changes (change throughput)Change throughput is a good measure of change management productivity.
9. Percentage of Failed Changes
A change management quality metric — can impact customer satisfaction and availability management.
10. Change Backlog
Total number of changes waiting in the queue.
11. Mean RFC (Request for Change) Turnaround Time (MRTT)
The average time it takes to implement a change after it is requested.
Release Management
12. Percentage of Failed ReleasesThe percentage of releases that fail — a key Release Management quality metric.
13. Total Release Downtime (TRD)
Total downtime due to release activity.
Availability Management
14. Total DowntimeTotal downtimes broken down by service.
15. Total SLA Violations
Number of times that the availability terms laid out in SLAs were violated.
IT Financial Management
16. Percentage of Projects Within BudgetThe percentage of projects that did not go over/under their prescribed budget.
17. Total Actual vs Budgeted Costs
Total actual project costs as a percentage of budgeted project costs. Calculated for an entire project portfolio. A number over 100% indicates over spending.
Service Level Management
18. Total SLA violationsThe number of SLA violations in a given period.
19. Mean Time to Resolve SLA Violations
The average time it takes to restore SLA compliance when a violation occurs.
Configuration Management
20. CI Data QualityPercentage of CIs with data issues. Can be determined by sampling methods.
ITIL Dashboards
ITIL metrics represent critical decision support data and are often presented in a dashboard to Cx0s.
Multifactor Authentication Explained
How to confirm the identity of users and entities.
|
|
Continuous Controls Monitoring for Transactions (CCM-T) is a governance, risk and compliance technology. There are 4 typical functions of a CCM system. |
|
It's all about engaging customers, partners and employees. |
|
In the real world, SOA often fails. |
|
Take a few minutes to learn about the Zachman Framework — a framework for Enterprise Architecture. |
Recently on Simplicable
| 9 ITIL Implementation Challengesposted by Anna MarITIL implementation is no cakewalk. ITIL impacts your entire organization — your business, your IT department and your inflight projects. |
| The 9 Principles Of Soa Designposted by Anna MarService-oriented Architecture (SOA) is as simple as can be — it can all be boiled down to these 9 principles. |
| What Big Data Really Meansposted by John SpaceyThe 3 things you need to know to cut through the big data hype. |
| The 5 Levels of Enterprise Integrationposted by Anna MarEnterprise Integration has traditionally focused on moving data from one database to another. Recent technology trends have challenged this approach. |
