Service Management Metrics: Difference between revisions
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
<meta property="fb:admins" content="100002035253209" /> | <meta property="fb:admins" content="100002035253209" /> | ||
<meta property="fb:admins" content="100002592864414" /> | <meta property="fb:admins" content="100002592864414" /> | ||
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg" /> | <meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-metric/16x9/Service-management-metrics-yasm.jpg" /> | ||
<meta property="og:image:width" content="1200" /> | <meta property="og:image:width" content="1200" /> | ||
<meta property="og:image:height" content=" | <meta property="og:image:height" content="675" /> | ||
<meta name="twitter:card" content="summary_large_image"> | <meta name="twitter:card" content="summary_large_image"> | ||
<meta name="twitter:site" content="@yasmcom"> | <meta name="twitter:site" content="@yasmcom"> | ||
<meta name="twitter:creator" content="@yasmcom"> | <meta name="twitter:creator" content="@yasmcom"> | ||
<meta name="twitter:title" content="Service Management Metrics | <meta name="twitter:title" content="Service Management Metrics"> | ||
<meta name="twitter:description" content="Service management metrics (at times also referred to as 'key performance indicators' or 'KPIs') are used to assess if processes are running according to expectations."> | <meta name="twitter:description" content="Service management metrics (at times also referred to as 'key performance indicators' or 'KPIs') are used to assess if processes are running according to expectations."> | ||
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg"> | <meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-metric/16x9/Service-management-metrics-yasm.jpg"> | ||
<meta name="twitter:image:alt" content="Service management metrics (Key Performance Indicators - KPIs) are used to measure the performance of the YaSM service management processes."> | <meta name="twitter:image:alt" content="Service management metrics (Key Performance Indicators - KPIs) are used to measure the performance of the YaSM service management processes."> | ||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
Line 27: | Line 27: | ||
<span id="md-webpage-description" itemprop="description">Service management metrics (at times also referred to as 'key performance indicators' or 'KPIs') are used to assess if the processes are running according to expectations.</span> | <span id="md-webpage-description" itemprop="description">Service management metrics (at times also referred to as 'key performance indicators' or 'KPIs') are used to assess if the processes are running according to expectations.</span> | ||
<html><div itemscope itemtype="https://schema.org/ImageObject"> | <html><div id="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject"> | ||
<a href="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg" title="Service management metrics" itemprop="contentUrl"> | <a href="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg" title="Service management metrics" itemprop="contentUrl"> | ||
<meta itemprop="caption" content="Service management metrics: Suitable metrics (KPIs) to measure the YaSM service management processes." /> | <meta itemprop="caption" content="Service management metrics: Suitable metrics (KPIs) to measure the YaSM service management processes." /> | ||
Line 38: | Line 38: | ||
<meta itemprop="datePublished" content="2016-04-24" /> | <meta itemprop="datePublished" content="2016-04-24" /> | ||
<meta itemprop="dateModified" content="2018-12-02" /> | <meta itemprop="dateModified" content="2018-12-02" /> | ||
<meta itemprop="representativeOfPage" content="true"/> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | <span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | ||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-metric/Yasm-process-metrics.jpg" /> | <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-metric/Yasm-process-metrics.jpg" /> | ||
Line 45: | Line 46: | ||
<meta itemprop="datePublished" content="2014-06-05" /> | <meta itemprop="datePublished" content="2014-06-05" /> | ||
<meta itemprop="dateModified" content="2018-12-02" /> | <meta itemprop="dateModified" content="2018-12-02" /> | ||
</span> | |||
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject"> | |||
<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-metric/16x9/Service-management-metrics-yasm.jpg" /> | |||
<meta itemprop="width" content="1200" /> | |||
<meta itemprop="height" content="675" /> | |||
<meta itemprop="dateCreated" content="2019-06-16" /> | |||
<meta itemprop="datePublished" content="2019-06-16" /> | |||
</span> | </span> | ||
<img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-metric/Yasm-process-metrics.jpg" width="480" height="360" title="Service management metrics" alt="Service management metrics (Key Performance Indicators - KPIs) are used to measure the performance of the YaSM service management processes." /></a></div></html> | <img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-metric/Yasm-process-metrics.jpg" width="480" height="360" title="Service management metrics" alt="Service management metrics (Key Performance Indicators - KPIs) are used to measure the performance of the YaSM service management processes." /></a></div></html> | ||
Line 66: | Line 74: | ||
*Result-oriented | *Result-oriented | ||
* Timely. | * Timely. | ||
==Quantitative and qualitative metrics== | ==Quantitative and qualitative metrics== | ||
Line 76: | Line 82: | ||
*<i>Qualitative metrics</i> have a more direct relationship to successful process execution. For example, if a service provider aims to resolve a high percentage of incidents directly in 1st level support, the 1st-line resolution rate would be a suitable qualitative metric. | *<i>Qualitative metrics</i> have a more direct relationship to successful process execution. For example, if a service provider aims to resolve a high percentage of incidents directly in 1st level support, the 1st-line resolution rate would be a suitable qualitative metric. | ||
==<span id="metrics-lp">KPIs for lifecycle processes</span>== | ==<span id="metrics-lp">KPIs for lifecycle processes</span>== | ||
How to measure the performance of the service lifecycle processes in the YaSM service management model? The following tables provide you with suggestions for quantitative and qualitative process metrics. | How to measure the performance of the [[Service_Management_Processes#Service_lifecycle_processes|service lifecycle processes]] in the YaSM service management model? The following tables provide you with suggestions for quantitative and qualitative process metrics. | ||
<p id="lp-metrics"> </p> | <p id="lp-metrics"> </p> | ||
Line 135: | Line 138: | ||
<p style="float:right;">→ [[LP1: Set the strategic direction|Process description]] | → [[#lp-metrics|top]]</p> | <p style="float:right;">→ [[LP1: Set the strategic direction|Process description]] | → [[#lp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 184: | Line 186: | ||
<p style="float:right;">→ [[LP2: Design new or changed services|Process description]] | → [[#lp-metrics|top]]</p> | <p style="float:right;">→ [[LP2: Design new or changed services|Process description]] | → [[#lp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 241: | Line 242: | ||
<p style="float:right;">→ [[LP3: Build new or changed services|Process description]] | → [[#lp-metrics|top]]</p> | <p style="float:right;">→ [[LP3: Build new or changed services|Process description]] | → [[#lp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 298: | Line 298: | ||
<p style="float:right;">→ [[LP4: Operate the services|Process description]] | → [[#lp-metrics|top]]</p> | <p style="float:right;">→ [[LP4: Operate the services|Process description]] | → [[#lp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 359: | Line 358: | ||
<p style="float:right;">→ [[LP4.6: Resolve incidents and service requests|Process description]] | → [[#lp-metrics|top]]</p> | <p style="float:right;">→ [[LP4.6: Resolve incidents and service requests|Process description]] | → [[#lp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 404: | Line 402: | ||
<p style="float:right;">→ [[LP4.7: Resolve problems|Process description]] | → [[#lp-metrics|top]]</p> | <p style="float:right;">→ [[LP4.7: Resolve problems|Process description]] | → [[#lp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 442: | Line 439: | ||
==<span id="metrics-sp">KPIs for supporting processes</span>== | ==<span id="metrics-sp">KPIs for supporting processes</span>== | ||
How to measure the performance of the supporting processes in the YaSM service management model? The following tables provide you with suggestions for quantitative and qualitative process metrics. | How to measure the performance of the [[Service_Management_Processes#Supporting_processes|supporting processes]] in the YaSM service management model? The following tables provide you with suggestions for quantitative and qualitative process metrics. | ||
<p id="sp-metrics"> </p> | <p id="sp-metrics"> </p> | ||
Line 496: | Line 493: | ||
<p style="float:right;">→ [[SP1: Set up and maintain the service management system|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP1: Set up and maintain the service management system|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 545: | Line 541: | ||
<p style="float:right;">→ [[SP2: Maintain the service portfolio|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP2: Maintain the service portfolio|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 598: | Line 593: | ||
<p style="float:right;">→ [[SP3: Manage customer relationships|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP3: Manage customer relationships|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 655: | Line 649: | ||
<p style="float:right;">→ [[SP4: Manage configuration information|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP4: Manage configuration information|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 716: | Line 709: | ||
<p style="float:right;">→ [[SP5: Assess and coordinate changes|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP5: Assess and coordinate changes|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 757: | Line 749: | ||
<p style="float:right;">→ [[SP6: Manage projects|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP6: Manage projects|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 822: | Line 813: | ||
<p style="float:right;">→ [[SP7: Ensure security|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP7: Ensure security|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 879: | Line 869: | ||
<p style="float:right;">→ [[SP8: Prepare for disaster events|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP8: Prepare for disaster events|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 932: | Line 921: | ||
<p style="float:right;">→ [[SP9: Ensure compliance|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP9: Ensure compliance|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 981: | Line 969: | ||
<p style="float:right;">→ [[SP10: Manage human resources|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP10: Manage human resources|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 1,042: | Line 1,029: | ||
<p style="float:right;">→ [[SP11: Manage suppliers|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP11: Manage suppliers|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Line 1,091: | Line 1,077: | ||
<p style="float:right;">→ [[SP12: Manage service financials|Process description]] | → [[#sp-metrics|top]]</p> | <p style="float:right;">→ [[SP12: Manage service financials|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
Revision as of 11:36, 16 June 2019
Service management metrics (at times also referred to as 'key performance indicators' or 'KPIs') are used to assess if the processes are running according to expectations.
Defining KPIs is above all about deciding what exactly is considered "successful" process execution.
Once this is established, suitable quantitative and qualitative metrics for the service management processes (the service lifecycle processes and the supporting processes) can be defined and subsequently measured. The process owners are then in a position to evaluate the quality of their processes, which in turn is the basis for process improvement.
Defining process metrics
The exact definitions of the metrics will vary depending on the nature of the service provider organization, so the key performance indicators contained in this wiki can only be suggestions.
Generally speaking, there is no shortage of recommendations for service management metrics. If further ideas are needed, the various service management frameworks like ITIL® [1], COBIT® [2] and USMBOK™ [3] may be consulted - but we advise using a focused set of metrics or KPIs that can be managed and acted upon in the long term.
A widely accepted principle holds that process metrics should be SMART:
- Specific
- Measurable
- Achievable
- Result-oriented
- Timely.
Quantitative and qualitative metrics
When developing sets of process KPIs, a distinction is often made between quantitative metrics and qualitative metrics (although the line between the two may at times be blurred):
- As the name suggests, quantitative metrics are typically straightforward measurements of volumes and frequencies (e.g. the number of service requests reported to 1st level support). Such metrics may not say much about the quality of the service request fulfillment process, but they can be useful for managing the resources required to fulfill service requests.
- Qualitative metrics have a more direct relationship to successful process execution. For example, if a service provider aims to resolve a high percentage of incidents directly in 1st level support, the 1st-line resolution rate would be a suitable qualitative metric.
KPIs for lifecycle processes
How to measure the performance of the service lifecycle processes in the YaSM service management model? The following tables provide you with suggestions for quantitative and qualitative process metrics.
Metrics for the service strategy process
Quantitative process metrics | Definition |
---|---|
Number of strategic reviews |
|
Number of strategic objectives |
|
Number of strategic initiatives |
|
Qualitative process metrics | Definition |
Share of strategic objectives pursued through initiatives |
|
Number of successful strategic initiatives |
|
Number of new services introduced |
|
Number of service improvements implemented |
|
Number of services retired due to strategic reviews |
|
Number of process improvements implemented |
|
→ Process description | → top
Metrics for the service design process
Quantitative process metrics | Definition |
---|---|
Number of service designs |
|
Number of service implementation blueprints |
|
Number of requirements specifications |
|
Qualitative process metrics | Definition |
Percentage of new services introduced using the service design process |
|
Number of renegotiated service requirements |
|
Number of services unexpectedly impacted |
|
Completeness of service implementation blueprints |
|
Percentage of designed services not delivering the expected outcomes |
|
→ Process description | → top
Metrics for the service build process
Quantitative process metrics | Definition |
---|---|
Number of new services implemented |
|
Number of tests and test cases |
|
Qualitative process metrics | Definition |
Percentage of new services introduced using the service build process |
|
Duration of service implementation |
|
Percentage of automatic software distribution |
|
Percentage of failed component acceptance tests |
|
Number of identified errors |
|
Time for error fixing |
|
Incidents caused by new service components |
|
Percentage of implemented services not delivering the expected outcomes |
|
→ Process description | → top
Metrics for the service operation process
Quantitative process metrics | Definition |
---|---|
Number of services monitored |
|
Number of services where quality is measured and reported |
|
Number of generated significant events |
|
Qualitative process metrics | Definition |
Share of monitored services |
|
Share of automated responses to events |
|
Share of services with quality reporting |
|
Number of service incidents due to inadequate maintenance |
|
Number of service level breaches |
|
Unused capacity |
|
Number of improvement initiatives |
|
→ Process description | → top
Metrics for the incident resolution process
Quantitative process metrics | Definition |
---|---|
Number of incidents and service requests |
|
Number of major incidents |
|
Qualitative process metrics | Definition |
Average initial response time |
|
Average resolution time |
|
Resolution within agreed time |
|
First time resolution rate |
|
Number of standard incidents and service requests |
|
Incidents resolved remotely |
|
Incidents resolved pro-actively |
|
Share of escalated incidents |
|
Average resolution effort |
|
→ Process description | → top
Metrics for the problem resolution process
Quantitative process metrics | Definition |
---|---|
Number of resolved problems |
|
Number of workarounds |
|
Qualitative process metrics | Definition |
Average resolution time |
|
Problems identified pro-actively |
|
Number of incidents per known problem |
|
Average time until identification of the cause |
|
Average resolution effort |
|
→ Process description | → top
Metrics for the service improvement process
Quantitative process metrics | Definition |
---|---|
Number of service reviews |
|
Qualitative process metrics | Definition |
Number of identified weaknesses |
|
Number of defined service improvement initiatives |
|
Number of successful service improvement Initiatives |
|
→ Process description | → top
KPIs for supporting processes
How to measure the performance of the supporting processes in the YaSM service management model? The following tables provide you with suggestions for quantitative and qualitative process metrics.
Metrics for the SMS process
Quantitative process metrics | Definition |
---|---|
Number of documented processes |
|
Number of process reviews and audits |
|
Qualitative process metrics | Definition |
Share of processes with defined service owners |
|
Share of processes with defined process metrics |
|
Share of processes with regular reviews |
|
Number of identified weaknesses |
|
Number of defined process improvement initiatives |
|
Number of successful process improvement Initiatives |
|
Number of changes to the service management policies |
|
→ Process description | → top
Metrics for the portfolio maintenance process
Quantitative process metrics | Definition |
---|---|
Number of services |
|
Number of new services |
|
Number of changed services |
|
Number of retired services |
|
Qualitative process metrics | Definition |
Services documented in the services portfolio |
|
Services defined by service definitions |
|
Services covered by agreements |
|
Number of detected service inconsistencies |
|
→ Process description | → top
Metrics for the CRM process
Quantitative process metrics | Definition |
---|---|
Number of customer meetings |
|
Number of customer satisfaction surveys |
|
Number of customer complaints |
|
Qualitative process metrics | Definition |
Customer satisfaction |
|
Number of accepted customer complaints |
|
Number of new services introduced |
|
Number of service improvements implemented |
|
Number of new customers |
|
Number of lost customers |
|
→ Process description | → top
Metrics for the configuration management process
Quantitative process metrics | Definition |
---|---|
Number of CI types |
|
Number of CIs |
|
Number of changes to CIs |
|
Qualitative process metrics | Definition |
Number of incidents owing to inaccurate CMS Information |
|
Verification frequency |
|
Share of automatic verification |
|
Effort for CMS verifications |
|
CMS coverage |
|
Number of unauthorized changes detected |
|
Number of CMS errors |
|
→ Process description | → top
Metrics for the change assessment process
Quantitative process metrics | Definition |
---|---|
Number of change assessments |
|
Number of changes |
|
Number of major changes |
|
Number of emergency changes |
|
Number of change models |
|
Number of post-implementation reviews |
|
Qualitative process metrics | Definition |
Time for change authorization/ rejection |
|
Change authorization rate |
|
Change success rate |
|
Number of unauthorized changes |
|
Number of change-related incidents |
|
→ Process description | → top
Metrics for the project management process
Quantitative process metrics | Definition |
---|---|
Number of projects |
|
Qualitative process metrics | Definition |
Percentage of projects with project charters |
|
Number of changes to project scope |
|
Adherence to planned resources |
|
Adherence to project schedule |
|
Number of cancelled projects |
|
→ Process description | → top
Metrics for the security process
Quantitative process metrics | Definition |
---|---|
Number of security risks |
|
Number of security policies |
|
Number of security alerts |
|
Qualitative process metrics | Definition |
Percentage of security risks with risk responses |
|
Number of implemented security improvements |
|
Time for implementation of risk responses |
|
Number of security breaches |
|
Number of security incidents |
|
Number of security-related service downtimes |
|
Number of security training sessions |
|
Number of security tests |
|
Number of identified issues during security tests |
|
→ Process description | → top
Metrics for the disaster preparation process
Quantitative process metrics | Definition |
---|---|
Number of managed disaster events |
|
Number of continuity plans |
|
Qualitative process metrics | Definition |
Percentage of managed disaster events covered by continuity arrangements |
|
Number of implemented continuity arrangements |
|
Time for implementation of continuity arrangements |
|
Number of disaster events |
|
Number of disaster events with continuity arrangements in place |
|
Number of continuity training sessions |
|
Number of continuity tests |
|
Number of issues identified during continuity tests |
|
→ Process description | → top
Metrics for the compliance process
Quantitative process metrics | Definition |
---|---|
Total number of compliance requirements |
|
Number of added compliance requirements |
|
Number of removed compliance requirements |
|
Qualitative process metrics | Definition |
Percentage of compliance requirements with controls in place |
|
Percentage of compliance requirements covered by reviews |
|
Number of compliance reviews |
|
Number of issues identified during compliance reviews |
|
Number of issues reported outside compliance reviews |
|
Time for fixing compliance issues |
|
→ Process description | → top
Metrics for the HR management process
Quantitative process metrics | Definition |
---|---|
Number of staff |
|
Number of skills |
|
Number of staff entering the organization |
|
Number of staff leaving the organization |
|
Qualitative process metrics | Definition |
Number of skills added |
|
Number of skills removed |
|
Number of skill development measures |
|
Share of skills covered by development plans |
|
→ Process description | → top
Metrics for the supplier management process
Quantitative process metrics | Definition |
---|---|
Number of suppliers |
|
Number of preferred suppliers |
|
Number of new suppliers |
|
Number of terminated supplier agreements |
|
Number of purchase orders |
|
Qualitative process metrics | Definition |
Share of external services covered by agreements |
|
Share of preferred suppliers |
|
Share of reviewed agreements |
|
Number of supplier meetings |
|
Number of detected contract breaches |
|
Time for issuing purchase orders |
|
→ Process description | → top
Metrics for the financial management process
Quantitative process metrics | Definition |
---|---|
Total budget |
|
Budget change on previous period |
|
Qualitative process metrics | Definition |
Adherence to financial forecasts |
|
Share of costs allocated to services |
|
Share of charged services |
|
Share of profitable services |
|
Share of investments with business cases |
|
Share of investments with realized benefits |
|
→ Process description | → top
Notes
[1] ITIL® is a registered trade mark of AXELOS Limited.
[2] COBIT® is a registered trademark of ISACA (Information Systems Audit and Control Association).
[3] USMBOK™ is a registered trade mark of Virtual Knowledge Solutions International Incorporated (VKSII).
By: Andrea Kempter and Stefan Kempter , IT Process Maps.
Defining process metrics › Quantitative and qualitative metrics › KPIs for lifecycle processes › KPIs for supporting processes