Service Management Metrics: Difference between revisions

From YaSM Service Management Wiki
No edit summary
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<itpmch><title>Service Management Metrics | YaSM Service Management Wiki</title>
<itpmch><title>Service Management Metrics | YaSM Wiki</title>
<meta name="keywords" content="yasm metrics, service management metrics, yasm kpi, yasm kpis, service management kpis, yasm key performance indicators" />
<meta name="keywords" content="yasm metrics, service management metrics, yasm kpi, yasm kpis, service management kpis, yasm key performance indicators" />
<meta name="description" content="Process metrics (at times also referred to as 'key performance indicators' or 'KPIs') are used to assess if the service management processes are running according to expectations." />
<meta name="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 property="og:url" content="https://yasm.com/wiki/en/index.php/Service_Management_Metrics" />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/Service_Management_Metrics" />
<meta property="og:title" content="Service Management Metrics | YaSM Service Management Wiki" />
<meta property="og:title" content="Service Management Metrics | YaSM Service Management Wiki" />
<meta property="og:description" content="Process metrics (at times also referred to as 'key performance indicators' or 'KPIs') are used to assess if the service management processes are running according to expectations." />
<meta property="og: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 property="og:site_name" content="YaSM">
<meta property="og:site_name" content="YaSM Service Management">
<meta property="og:type" content="article" />
<meta property="og:type" content="article" />
<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-metric/16x9/Service-management-metrics-yasm.jpg" />
<meta property="fb:admins" content="100002035253209" />
<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:width" content="1200" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="900" />
<meta property="og:image:height" content="675" />
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@yasmcom">
<meta name="twitter:creator" content="@yasmcom">
<meta name="twitter:title" content="Service Management Metrics | YaSM Wiki">
<meta name="twitter:description" content="Process metrics (Key Performance Indicators or 'KPIs') are used to assess if the service management 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: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" />
</itpmch>
</itpmch>
<html><div class="floatright"><div class="noresize"><map name="ImageMap_yasm-wiki-share"><area href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FService_Management_Metrics&hl=en_US&source=YaSM%20Wiki" class="plainlinks" rel="nofollow" shape="rect" coords="55,0,99,36" alt="share this page on LinkedIn" title="share this page on LinkedIn"/><area href="https://twitter.com/intent/tweet?url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FService_Management_Metrics&text=%23YaSMwiki%20%7C%20The%20most%20important%20service%20management%20metrics%0A%E2%96%BA&lang=en&via=yasmcom" class="plainlinks" rel="nofollow" shape="rect" coords="97,0,140,36" alt="share this page on Twitter" title="share this page on Twitter"/></map><img alt="share this page" src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-share.png" width="140" height="36" usemap="#ImageMap_yasm-wiki-share"/></div></div><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/Service-Management-Kennzahlen"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:left;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/></html>
<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/Service-Management-Kennzahlen"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/></html>
<p>&nbsp;</p>
<p>&nbsp;</p>


<span id="md-webpage-description" itemprop="description"><i>Process metrics</i> (at times also referred to as 'key performance indicators' or 'KPIs') are used to assess if the service management processes are running according to expectations.</span>
<span id="md-webpage-description" itemprop="description"><b><span style="color:#465674;">Service management metrics</span></b> (at times also referred to as '<b><span style="color:#465674;">key performance indicators</span></b>' or '<b><span style="color:#465674;">KPIs</span></b>') are used to assess if the processes are running according to expectations.</span>


'''Proceed to:''' [[#KPIS_for_lifecycle_processes|Process metrics for the service lifecycle processes]] | [[#KPIs_for_supporting_processes|Process metrics for the supporting service management processes]]
<html><div itemid="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject">
 
<p>&nbsp;</p>
 
==Defining process metrics==
 
<html><div 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">
<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." />
<meta itemprop="width" content="1200" />
<meta itemprop="width" content="1200" />
Line 41: Line 24:
<meta itemprop="keywords" content="yasm metrics" />
<meta itemprop="keywords" content="yasm metrics" />
<meta itemprop="keywords" content="service management kpis" />
<meta itemprop="keywords" content="service management kpis" />
<meta itemprop="dateCreated" content="2018-11-30" />
<meta itemprop="dateCreated" 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="datePublished" content="2018-11-30" />
<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" />
   <meta itemprop="width" content="480" />
   <meta itemprop="width" content="480" />
   <meta itemprop="height" content="360" />
   <meta itemprop="height" content="360" />
  <meta itemprop="dateCreated" content="2014-05-03" />
  <meta itemprop="datePublished" content="2014-06-05" />
  <meta itemprop="dateModified" content="2018-12-02" />
</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>
<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>
 
<figure class="mw-halign-right" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg" title="Service management metrics"><img srcset="https://yasm.com/wiki/en/img/yasm-metric/Yasm-process-metrics.jpg 480w, https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-metric/Yasm-process-metrics.jpg" fetchpriority="high" decoding="async" width="480" height="360" class="mw-file-element" alt="Service management metrics (Key Performance Indicators - KPIs) are used to measure the performance of the YaSM service management processes." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg" title="Service management metrics">Service management metrics</a></b><br />Metrics (KPIs) to measure the YaSM service management processes.</span></figcaption></figure></div></html>


<p>Defining KPIs is above all about deciding what exactly is considered "successful" process execution. Once this is established, suitable metrics 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.</html>
<span style="word-wrap:normal;">[[#Defining_process_metrics|Defining KPIs]] is above all about deciding what exactly is considered "successful" process execution.</span>
 
<html>Once this is established, suitable <a href="#Quantitative_and_qualitative_metrics" title="Quantitative and qualitative KPIs">quantitative and qualitative metrics</a> for the service management processes (the <a href="#KPIs_for_lifecycle_processes" title="KPIs for the lifecycle processes in service management">service lifecycle processes</a> and <a href="#KPIs_for_supporting_processes" title="KPIs for the supporting processes in service management">the supporting processes</a>) 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.</html>
<p>&nbsp;</p>
 
==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.
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&reg; [[#ITIL|[1]]], COBIT&reg; [[#COBIT|[2]]]  and USMBOK&trade; [[#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.
Generally speaking, there is no shortage of recommendations for [[Service Management|service management]] metrics. If further ideas are needed, the various service management frameworks like ITIL&reg; [[#ITIL|[1]]], COBIT&reg; [[#COBIT|[2]]]  and USMBOK&trade; [[#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'':
A widely accepted principle holds that process metrics should be ''SMART'':
Line 63: Line 63:
*Result-oriented
*Result-oriented
* Timely.
* Timely.
<p>&nbsp;</p>


==Quantitative and qualitative metrics==
==Quantitative and qualitative metrics==
Line 73: Line 71:


*<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.
<p>&nbsp;</p>
<p>&nbsp;</p>


==<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 YaSM service lifecycle processes? The following tables provide you with suggestions for quantitative and qualitative process metrics.


<p id="lp-metrics">&nbsp;</p>
<span id="lp-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.</span>


===<span id="metrics-lp1">Metrics for the service strategy process</span>===
===<span id="metrics-lp1">Metrics for the service strategy process</span>===
Line 86: Line 81:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Set the strategic direction"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Set the strategic direction"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of strategic reviews
|Number of strategic reviews
Line 103: Line 98:
*Number of strategic initiatives launched during the reporting period.
*Number of strategic initiatives launched during the reporting period.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Share of strategic objectives pursued through initiatives
|Share of strategic objectives pursued through initiatives
Line 139: Line 134:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Design new or changed services"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Design new or changed services"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of service designs
|Number of service designs
Line 156: Line 151:
*Number of requirements specifications produced for infrastructure items or other service components which were needed to provide new or significantly changed services.
*Number of requirements specifications produced for infrastructure items or other service components which were needed to provide new or significantly changed services.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Percentage of new services introduced using the service design process
|Percentage of new services introduced using the service design process
Line 188: Line 183:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Build new or changed services"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Build new or changed services"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of new services implemented
|Number of new services implemented
Line 201: Line 196:
*Number of tests and test cases carried out, possibly grouped by services to be implemented, test types, ...
*Number of tests and test cases carried out, possibly grouped by services to be implemented, test types, ...
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Percentage of new services introduced using the service build process
|Percentage of new services introduced using the service build process
Line 245: Line 240:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Operate the services"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Operate the services"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of services monitored
|Number of services monitored
Line 262: Line 257:
*Number of events generated by event monitoring systems, grouped by categories (e.g. events related to particular systems, events requiring human interaction, events triggering an automated response, ...).
*Number of events generated by event monitoring systems, grouped by categories (e.g. events related to particular systems, events requiring human interaction, events triggering an automated response, ...).
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Share of monitored services
|Share of monitored services
Line 302: Line 297:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Resolve incidents and service requests"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Resolve incidents and service requests"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of incidents and service requests
|Number of incidents and service requests
Line 315: Line 310:
*Number of incidents resolved by invoking the special procedure for major incidents.
*Number of incidents resolved by invoking the special procedure for major incidents.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Average initial response time
|Average initial response time
Line 363: Line 358:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Resolve problems"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Resolve problems"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of resolved problems
|Number of resolved problems
Line 376: Line 371:
*Number of workarounds provided to incident management.
*Number of workarounds provided to incident management.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Average resolution time
|Average resolution time
Line 408: Line 403:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Improve the services"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Improve the services"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of service reviews
|Number of service reviews
Line 417: Line 412:
*Number of formal service reviews carried out during the reporting period.
*Number of formal service reviews carried out during the reporting period.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of identified weaknesses
|Number of identified weaknesses
Line 439: Line 434:
==<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 YaSM supporting service management processes? The following tables provide you with suggestions for quantitative and qualitative process metrics.
<span id="sp-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.</span>
 
<p id="sp-metrics">&nbsp;</p>


===<span id="metrics-sp1">Metrics for the SMS process</span>===
===<span id="metrics-sp1">Metrics for the SMS process</span>===
Line 447: Line 440:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Set up and maintain the service management system"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Set up and maintain the service management system"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of documented processes
|Number of documented processes
Line 460: Line 453:
*Number of formal process reviews and audits carried out during the reporting period.
*Number of formal process reviews and audits carried out during the reporting period.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Share of processes with defined service owners
|Share of processes with defined service owners
Line 500: Line 493:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Maintain the service portfolio"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Maintain the service portfolio"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of services
|Number of services
Line 521: Line 514:
*Number of services that were retired.
*Number of services that were retired.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Services documented in the services portfolio
|Services documented in the services portfolio
Line 549: Line 542:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage customer relationships"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage customer relationships"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of customer meetings
|Number of customer meetings
Line 566: Line 559:
*Number of received customer complaints during the reporting period.
*Number of received customer complaints during the reporting period.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Customer satisfaction
|Customer satisfaction
Line 602: Line 595:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage configuration information"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage configuration information"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of CI types
|Number of CI types
Line 619: Line 612:
*Number of recorded changes to configuration items, possibly grouped by CI types.
*Number of recorded changes to configuration items, possibly grouped by CI types.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of incidents owing to inaccurate CMS Information
|Number of incidents owing to inaccurate CMS Information
Line 659: Line 652:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Assess and coordinate changes"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Assess and coordinate changes"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of change assessments
|Number of change assessments
Line 688: Line 681:
*Number of changes that were subjected to a review after implementation, possibly grouped by change types, related configuration items, ...
*Number of changes that were subjected to a review after implementation, possibly grouped by change types, related configuration items, ...
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Time for change authorization/ rejection
|Time for change authorization/ rejection
Line 720: Line 713:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage projects"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage projects"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of projects
|Number of projects
Line 729: Line 722:
*Number of projects started, in progress and completed during the reporting period.
*Number of projects started, in progress and completed during the reporting period.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Percentage of projects with project charters
|Percentage of projects with project charters
Line 757: Line 750:
<p>&nbsp;</p>
<p>&nbsp;</p>


===<span id="metrics-sp7">Metrics for the security process</span>===
===<span id="metrics-sp7">Metrics for the security management process</span>===


{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Ensure security"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Ensure security"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of security risks
|Number of security risks
Line 778: Line 771:
*Number of security alerts issued by the security manager, possibly grouped by type of security threat, services affected, infrastructure components affected, ...
*Number of security alerts issued by the security manager, possibly grouped by type of security threat, services affected, infrastructure components affected, ...
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Percentage of security risks with risk responses
|Percentage of security risks with risk responses
Line 822: Line 815:
<p>&nbsp;</p>
<p>&nbsp;</p>


===<span id="metrics-sp8">Metrics for the disaster preparation process</span>===
===<span id="metrics-sp8">Metrics for the service continuity management process</span>===


{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Prepare for disaster events"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Ensure continuity"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of managed disaster events
|Number of managed critical events
|
|
*Number of (types of) disaster events for which prevention measures are deemed necessary and which are managed through the register of managed disaster events.
*Number of (types of) critical, disruptive events for which prevention measures are deemed necessary and which are managed through the register of managed critical events.
|-
|-
|Number of continuity plans
|Number of continuity plans
Line 839: Line 832:
*Number of continuity plans maintained by the continuity manager.
*Number of continuity plans maintained by the continuity manager.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Percentage of managed disaster events covered by continuity arrangements
|Percentage of managed critical events covered by continuity arrangements
|
|
*Percentage of identified and managed disaster events which are covered by suitable continuity plans.
*Percentage of identified and managed critical, disruptive events which are covered by suitable continuity plans.
|-
|-
|Number of implemented continuity arrangements
|Number of implemented continuity arrangements
|
|
*Number of continuity arrangements which were implemented in response to newly identified threats from disaster events.
*Number of continuity arrangements which were implemented in response to newly identified threats from critical events.
|-
|-
|Time for implementation of continuity arrangements
|Time for implementation of continuity arrangements
|
|
*Average duration from the identification of a new threat from a disaster event to the implementation of a suitable response.
*Average duration from the identification of a new threat from a critical event to the implementation of a suitable response.
|-
|-
|Number of disaster events
|Number of critical events
|
|
*Number of disaster events occurred during the reporting period.
*Number of critical events occurred during the reporting period.
|-
|-
|Number of disaster events with continuity arrangements in place
|Number of critical events with continuity arrangements in place
|
|
*Number of disaster events occurred during the reporting period for which a suitable continuity plan was in place.
*Number of critical events occurred during the reporting period for which a suitable continuity plan was in place.
|-
|-
|Number of continuity training sessions
|Number of continuity training sessions
Line 874: Line 867:
*Number of issues identified during continuity tests to be addressed by continuity improvement initiatives.
*Number of issues identified during continuity tests to be addressed by continuity improvement initiatives.
|}
|}
<p style="float:right;">&#8594; [[SP8: Prepare for disaster events|Process description]] | &#8594; [[#sp-metrics|top]]</p>
<p style="float:right;">&#8594; [[SP8: Ensure continuity|Process description]] | &#8594; [[#sp-metrics|top]]</p>


<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>


===<span id="metrics-sp9">Metrics for the compliance process</span>===
===<span id="metrics-sp9">Metrics for the compliance management process</span>===


{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Ensure compliance"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Ensure compliance"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Total number of compliance requirements
|Total number of compliance requirements
Line 900: Line 893:
*Number of compliance requirements removed from the compliance register during the reporting period, possibly grouped by types of requirements.
*Number of compliance requirements removed from the compliance register during the reporting period, possibly grouped by types of requirements.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Percentage of compliance requirements with controls in place
|Percentage of compliance requirements with controls in place
Line 936: Line 929:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage human resources"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage human resources"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of staff
|Number of staff
Line 957: Line 950:
*Number of employees who left the service provider organization during the reporting period.
*Number of employees who left the service provider organization during the reporting period.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of skills added
|Number of skills added
Line 985: Line 978:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage suppliers"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage suppliers"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Number of suppliers
|Number of suppliers
Line 1,010: Line 1,003:
*Number of purchase orders processed, possibly grouped by product categories, purchase order types (e.g. orders for non-standard products and services, orders for standard products), ...
*Number of purchase orders processed, possibly grouped by product categories, purchase order types (e.g. orders for non-standard products and services, orders for standard products), ...
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Share of external services covered by agreements
|Share of external services covered by agreements
Line 1,046: Line 1,039:
{| class="wikitable" style="background: white;"
{| class="wikitable" style="background: white;"
|-
|-
!style="background:#379988; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage service financials"
|+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage service financials"
|-
|-
!style="background:#eeeeee; width:35%"|Quantitative process metrics
!style="background:#eeeeee; width:30%"|Quantitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Total budget
|Total budget
Line 1,059: Line 1,052:
*Percentage of budget increase or decrease compared to the previous budgeting period, possibly broken down into cost and revenue categories.
*Percentage of budget increase or decrease compared to the previous budgeting period, possibly broken down into cost and revenue categories.
|-
|-
!style="background:#eeeeee; width:35%"|Qualitative process metrics
!style="background:#eeeeee; width:30%"|Qualitative process metrics
!style="background:#eeeeee; width:65%"|Definition
!style="background:#eeeeee; width:70%"|Definition
|-
|-
|Adherence to financial forecasts
|Adherence to financial forecasts
Line 1,096: Line 1,089:
[3] <span id="USMBOK">USMBOK&trade; is a registered trade mark of Virtual Knowledge Solutions International Incorporated (VKSII).</span>
[3] <span id="USMBOK">USMBOK&trade; is a registered trade mark of Virtual Knowledge Solutions International Incorporated (VKSII).</span>


<html>By:&#160;&#160;Andrea Kempter&#160;<a rel="author" href="https://plus.google.com/113316270668629760475/about"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a>&#160;&#160;and&#160;&#160;Stefan Kempter&#160;<a href="https://plus.google.com/111925560448291102517/about"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Contributor: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.
<html>By:&#160;&#160;Andrea Kempter&#160;<a rel="author" href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a>&#160;&#160;and&#160;&#160;Stefan Kempter&#160;<a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Contributor: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 1,111: Line 1,104:
<meta itemprop="position" content="2" /></span> ›
<meta itemprop="position" content="2" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Metrics#KPIS_for_lifecycle_processes">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/Service_Management_Metrics#KPIs_for_lifecycle_processes">
<span itemprop="name">KPIs for lifecycle processes</span></a>
<span itemprop="name">KPIs for lifecycle processes</span></a>
<meta itemprop="position" content="3" /></span> ›
<meta itemprop="position" content="3" /></span> ›
Line 1,125: Line 1,118:
   <meta itemprop="Headline" content="Service management metrics" />
   <meta itemprop="Headline" content="Service management metrics" />
   <meta itemprop="alternativeHeadline" content="YaSM metrics" />
   <meta itemprop="alternativeHeadline" content="YaSM metrics" />
  <meta itemprop="alternativeHeadline" content="YService management KPIs" />
   <link itemprop="url" href="https://yasm.com/wiki/en/index.php/Service_Management_Metrics" />
   <link itemprop="url" href="https://yasm.com/wiki/en/index.php/Service_Management_Metrics" />
   <meta itemprop="about" content="service management metrics" />
   <meta itemprop="about" content="service management metrics" />

Latest revision as of 15:29, 24 July 2024

auf Deutsch


 

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.

Service management metrics (Key Performance Indicators - KPIs) are used to measure the performance of the YaSM service management processes.
Fig. 1: Service management metrics
Metrics (KPIs) to measure the YaSM service management processes.

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

Process metrics: "Set the strategic direction"
Quantitative process metrics Definition
Number of strategic reviews
  • Number of strategic reviews performed during the reporting period.
Number of strategic objectives
  • Number of strategic objectives defined following strategic reviews.
Number of strategic initiatives
  • Number of strategic initiatives launched during the reporting period.
Qualitative process metrics Definition
Share of strategic objectives pursued through initiatives
  • Percentage of strategic objectives which are being actively pursued with defined strategic initiatives.
Number of successful strategic initiatives
  • Number of strategic initiatives which were successfully completed during the reporting period.
Number of new services introduced
  • Number of new or significantly changed services which were introduced following a strategic review.
Number of service improvements implemented
  • Number of service improvements implemented due to insights gained during strategic reviews.
Number of services retired due to strategic reviews
  • Number of services which were retired due to insights gained during a strategic review.
Number of process improvements implemented
  • Number of process improvements implemented due to insights gained during strategic reviews.

Process description | → top

 

 

Metrics for the service design process

Process metrics: "Design new or changed services"
Quantitative process metrics Definition
Number of service designs
  • Number of new or significantly changed services designed during the reporting period.
Number of service implementation blueprints
  • Number of implementation blueprints produced for new or significantly changed services.
Number of requirements specifications
  • Number of requirements specifications produced for infrastructure items or other service components which were needed to provide new or significantly changed services.
Qualitative process metrics Definition
Percentage of new services introduced using the service design process
  • Percentage of new or significantly changed services which were introduced using the documented service design process vs. new services introduced without using that process.
Number of renegotiated service requirements
  • Number of new or significantly changed services where the original requirements had to be renegotiated during the design phase, possibly grouped by reasons like "Economically unfeasible", "Technically unfeasible", ...
Number of services unexpectedly impacted
  • Number of other services which were unexpectedly found to be impacted by the introduction of new or significantly changed services, due to errors made during the service design phase.
Completeness of service implementation blueprints
  • Percentage of service implementation blueprints which covered all required aspects. There may be one metric for every aspect covered, for example "Percentage of blueprints covering capacity and performance aspects", "Percentage of blueprints covering availability aspects", ...
Percentage of designed services not delivering the expected outcomes
  • Percentage of new or significantly changed services that failed to deliver the expected outcomes due to errors made during the service design phase.

Process description | → top

 

 

Metrics for the service build process

Process metrics: "Build new or changed services"
Quantitative process metrics Definition
Number of new services implemented
  • Number of new or significantly changed services implemented during the reporting period.
Number of tests and test cases
  • Number of tests and test cases carried out, possibly grouped by services to be implemented, test types, ...
Qualitative process metrics Definition
Percentage of new services introduced using the service build process
  • Percentage of new or significantly changed services which were introduced using the documented service build process vs. new services introduced without using that process.
Duration of service implementation
  • Duration of service implementation projects from autho-rization of the service development project to confirmation of service readiness.
Percentage of automatic software distribution
  • Percentage of software components deployed by means of automated distribution.
Percentage of failed component acceptance tests
  • Percentage of service components which failed to pass acceptance tests.
Number of identified errors
  • Number of identified errors during testing, possibly grouped by services to be implemented, test types, ...
Time for error fixing
  • Average times until re-submission of fixed components after errors were found, possibly grouped by services to be imple-mented, component types, ...
Incidents caused by new service components
  • Number of incidents attributable to newly deployed service components, grouped by services and service components.
Percentage of implemented services not delivering the expected outcomes
  • Percentage of new or significantly changed services which failed to deliver the expected outcomes due to errors made during the service build phase.

Process description | → top

 

 

Metrics for the service operation process

Process metrics: "Operate the services"
Quantitative process metrics Definition
Number of services monitored
  • Number of services which are constantly monitored in order to pro-actively avoid service interruptions or deficiencies in service quality.
Number of services where quality is measured and reported
  • Number of services whose quality levels are regularly measured and reported, as a basis for improving the services.
Number of generated significant events
  • Number of events generated by event monitoring systems, grouped by categories (e.g. events related to particular systems, events requiring human interaction, events triggering an automated response, ...).
Qualitative process metrics Definition
Share of monitored services
  • Percentage of services which are constantly monitored.
Share of automated responses to events
  • Number of events where an automated response is triggered vs. the total number of events requiring a response.
Share of services with quality reporting
  • Percentage of services whose quality levels are regularly measured and reported.
Number of service incidents due to inadequate maintenance
  • Number of service incidents which could have been avoided by more adequate preventive maintenance.
Number of service level breaches
  • Number of service levels breached, possibly grouped by types of service level, services, clients, ...
Unused capacity
  • Percentage of capacity reserves at times of normal and maximum demand, possibly grouped by services, systems, ...
Number of improvement initiatives
  • Number of issues detected during service quality reporting which result in a service improvement initiative being started.

Process description | → top

 

 

Metrics for the incident resolution process

Process metrics: "Resolve incidents and service requests"
Quantitative process metrics Definition
Number of incidents and service requests
  • Number of incidents and service requests logged by 1st level support, possibly grouped by priorities, categories, clients, ...
Number of major incidents
  • Number of incidents resolved by invoking the special procedure for major incidents.
Qualitative process metrics Definition
Average initial response time
  • Average delay between the time a user reported an incident or service request and the time that 1st level support responded to that incident or request, possibly grouped by priorities, categories, clients, ...
Average resolution time
  • Average time for resolving incidents or service requests, possibly grouped by priorities, categories, clients, ...
Resolution within agreed time
  • Percentage of incidents and service requests resolved within the target resolution times specified in the service agreements, possibly grouped by priorities, categories, clients, ...
First time resolution rate
  • Percentage of incidents and service requests resolved by 1st level support during the first call, possibly grouped by priorities, categories, clients, ...
Number of standard incidents and service requests
  • Number of incidents and service requests which were resolved by applying known resolution methods (typically defined in incident models) , possibly grouped by priorities, categories, clients, ...
Incidents resolved remotely
  • Number of incidents and service requests resolved remotely (i.e. without carrying out work at the user's location), possibly grouped by priorities, categories, clients, ...
Incidents resolved pro-actively
  • Number of incidents reported and resolved pro-actively (i.e. incidents resolved before impacting business processes on the client side), possibly grouped by priorities, categories, clients, ...
Share of escalated incidents
  • Percentage of incidents where a hierarchic escalation occurred.
Average resolution effort
  • Average work effort for resolving incidents and service requests, possibly grouped by priorities, categories, clients, ...

Process description | → top

 

 

Metrics for the problem resolution process

Process metrics: "Resolve problems"
Quantitative process metrics Definition
Number of resolved problems
  • Number of resolved problems, possibly grouped by priorities, categories, ...
Number of workarounds
  • Number of workarounds provided to incident management.
Qualitative process metrics Definition
Average resolution time
  • Average time for resolving problems, possibly grouped by priorities, categories, ...
Problems identified pro-actively
  • Percentage of problems raised as part of the pro-active problem identification process.
Number of incidents per known problem
  • Number of reported incidents linked to the same problem after a problem has been identified.
Average time until identification of the cause
  • Average time between problem registration and identification of the underlying cause.
Average resolution effort
  • Average work effort for resolving problems, possibly grouped by priorities, categories, ...

Process description | → top

 

 

Metrics for the service improvement process

Process metrics: "Improve the services"
Quantitative process metrics Definition
Number of service reviews
  • Number of formal service reviews carried out during the reporting period.
Qualitative process metrics Definition
Number of identified weaknesses
  • Number of weaknesses to be addressed by improvement initiatives which were identified during service reviews, possibly grouped by services.
Number of defined service improvement initiatives
  • Number of defined improvement initiatives, resulting from identified weaknesses during service reviews, possibly grouped by services.
Number of successful service improvement Initiatives
  • Number of service improvement initiatives which were completed successfully during the reporting period, possibly grouped by services.

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

Process metrics: "Set up and maintain the service management system"
Quantitative process metrics Definition
Number of documented processes
  • Number or service management processes which are documented in the process model.
Number of process reviews and audits
  • Number of formal process reviews and audits carried out during the reporting period.
Qualitative process metrics Definition
Share of processes with defined service owners
  • Percentage of service management processes which are assigned to a process owner.
Share of processes with defined process metrics
  • Percentage of service management processes where process metrics are defined, measured and acted upon.
Share of processes with regular reviews
  • Percentage of service management processes which are subjected to regular process reviews or audits according to the process review plan.
Number of identified weaknesses
  • Number of weaknesses to be addressed by improvement initiatives which were identified during process reviews or audits, possibly grouped by processes.
Number of defined process improvement initiatives
  • Number of defined improvement initiatives, resulting from identified weaknesses during process reviews or audits, possibly grouped by processes.
Number of successful process improvement Initiatives
  • Number of process improvement initiatives which were completed successfully during the reporting period, possibly grouped by processes.
Number of changes to the service management policies
  • Number of changes to the service management policies resulting from process reviews or audits, possibly grouped by policies.

Process description | → top

 

 

Metrics for the portfolio maintenance process

Process metrics: "Maintain the service portfolio"
Quantitative process metrics Definition
Number of services
  • Number of services managed through the service portfolio, grouped by customer and (internally or externally supplied) supporting services.
Number of new services
  • Number of services added to the service portfolio during the reporting period.
Number of changed services
  • Number of services in the service portfolio where new versions have been introduced.
Number of retired services
  • Number of services that were retired.
Qualitative process metrics Definition
Services documented in the services portfolio
  • Percentage of services offered by the service provider which are documented in the service portfolio.
Services defined by service definitions
  • Percentage of services in the service portfolio which are defined by authorized service definitions.
Services covered by agreements
  • Percentage of services in the service portfolio which are covered by agreements (i.e. customer services covered by customer service agreements and supporting services covered by operational or external service agreements).
Number of detected service inconsistencies
  • Number of inconsistencies between service definitions detected during service portfolio reviews (especially inconsistencies between customer services and supporting services).

Process description | → top

 

 

Metrics for the CRM process

Process metrics: "Manage customer relationships"
Quantitative process metrics Definition
Number of customer meetings
  • Number of formal customer meetings held during the reporting period.
Number of customer satisfaction surveys
  • Number of formal customer satisfaction surveys carried out during the reporting period.
Number of customer complaints
  • Number of received customer complaints during the reporting period.
Qualitative process metrics Definition
Customer satisfaction
  • Average measured customer satisfaction for each service, determined by means of customer satisfaction surveys.
Number of accepted customer complaints
  • Number of received customer complaints which were accepted (deemed justified and acted upon).
Number of new services introduced
  • Number of new or significantly changed services introduced due to insights gained during customer meetings or satisfaction surveys.
Number of service improvements implemented
  • Number of service improvements implemented due to insights gained during customer meetings or satisfaction surveys.
Number of new customers
  • Number of newly won customers during the reporting period.
Number of lost customers
  • Number of customers which were lost to competing service providers.

Process description | → top

 

 

Metrics for the configuration management process

Process metrics: "Manage configuration information"
Quantitative process metrics Definition
Number of CI types
  • Number of configuration item types managed through the configuration management system (CMS).
Number of CIs
  • Number of configuration items managed through the configuration management system (CMS), possibly grouped by CI types.
Number of changes to CIs
  • Number of recorded changes to configuration items, possibly grouped by CI types.
Qualitative process metrics Definition
Number of incidents owing to inaccurate CMS Information
  • Number of service incidents reported where the underlying cause of the incident was the result of inaccurate configuration information.
Verification frequency
  • Frequency of physical verifications of configuration information in the CMS.
Share of automatic verification
  • Percentage of configuration items in the CMS for which detection and verification can be done in an automated way.
Effort for CMS verifications
  • Average work effort for physical verifications of the CMS contents.
CMS coverage
  • Percentage of infrastructure components for which data is kept in the CMS.
Number of unauthorized changes detected
  • Number of unauthorized changes identified as a result of an audit.
Number of CMS errors
  • Number of errors found in the CMS as a result of an audit.

Process description | → top

 

 

Metrics for the change assessment process

Process metrics: "Assess and coordinate changes"
Quantitative process metrics Definition
Number of change assessments
  • Number of proposed changes (RFCs) assessed by the change assessment process, possibly grouped by change types, related configuration items, ...
Number of changes
  • Number of changes implemented, possibly grouped by change types, related configuration items, ...
Number of major changes
  • Number of major changes assessed by the change assessment process.
Number of emergency changes
  • Number of emergency RFCs assessed by the change assessment process.
Number of change models
  • Number of defined pre-authorized standard changes, documented in change models.
Number of post-implementation reviews
  • Number of changes that were subjected to a review after implementation, possibly grouped by change types, related configuration items, ...
Qualitative process metrics Definition
Time for change authorization/ rejection
  • Average time from registering an RFC with the change manager until a decision on the RFC is reached (i.e. until it is either approved or rejected).
Change authorization rate
  • Number of authorized vs. rejected RFCs.
Change success rate
  • Percentage of changes implemented successfully.
Number of unauthorized changes
  • Number of changes that were implemented without authorization (identified, for example, during configuration audits).
Number of change-related incidents
  • Number of unexpected service incidents caused by the implementation of authorized changes.

Process description | → top

 

 

Metrics for the project management process

Process metrics: "Manage projects"
Quantitative process metrics Definition
Number of projects
  • Number of projects started, in progress and completed during the reporting period.
Qualitative process metrics Definition
Percentage of projects with project charters
  • Percentage of projects which were started with a signed project charter in place.
Number of changes to project scope
  • Number of changes to the project scope after project start, per project.
Adherence to planned resources
  • Actual vs. planned consumption of financial and human resources, per project-
Adherence to project schedule
  • Actual vs. planned milestone and project completion dates, per project.
Number of cancelled projects
  • Number of projects that have ended without achieving their stated goals.

Process description | → top

 

 

Metrics for the security management process

Process metrics: "Ensure security"
Quantitative process metrics Definition
Number of security risks
  • Number of risks managed through the register of security risk.
Number of security policies
  • Number of underpinning security policies maintained and published by the security manager.
Number of security alerts
  • Number of security alerts issued by the security manager, possibly grouped by type of security threat, services affected, infrastructure components affected, ...
Qualitative process metrics Definition
Percentage of security risks with risk responses
  • Percentage of identified security risks which are covered by suitable risk responses.
Number of implemented security improvements
  • Number of security improvements which were implemented in response to newly identified security threats.
Time for implementation of risk responses
  • Average duration from the identification of a new security risk to the implementation of a suitable response.
Number of security breaches
  • Number of detected security breaches, possibly grouped by type of security breach, services affected, infrastructure components affected, ...
Number of security incidents
  • Number of reported security incidents, possibly grouped by incident priority, services affected, infrastructure components affected, ...
Number of security-related service downtimes
  • Number of security incidents causing service s to be unavailable.
Number of security training sessions
  • Number of security training sessions carried out, possibly grouped by type of training, target group, ...
Number of security tests
  • Number of security tests carried out, possibly grouped by type of test, security systems or mechanisms tested, ...
Number of identified issues during security tests
  • Number of identified issues during security tests to be addressed by security improvement initiatives.

Process description | → top

 

 

Metrics for the service continuity management process

Process metrics: "Ensure continuity"
Quantitative process metrics Definition
Number of managed critical events
  • Number of (types of) critical, disruptive events for which prevention measures are deemed necessary and which are managed through the register of managed critical events.
Number of continuity plans
  • Number of continuity plans maintained by the continuity manager.
Qualitative process metrics Definition
Percentage of managed critical events covered by continuity arrangements
  • Percentage of identified and managed critical, disruptive events which are covered by suitable continuity plans.
Number of implemented continuity arrangements
  • Number of continuity arrangements which were implemented in response to newly identified threats from critical events.
Time for implementation of continuity arrangements
  • Average duration from the identification of a new threat from a critical event to the implementation of a suitable response.
Number of critical events
  • Number of critical events occurred during the reporting period.
Number of critical events with continuity arrangements in place
  • Number of critical events occurred during the reporting period for which a suitable continuity plan was in place.
Number of continuity training sessions
  • Number of continuity training sessions carried out, possibly grouped by types of training, target groups, ...
Number of continuity tests
  • Number of continuity tests carried out, possibly grouped by types of continuity arrangements, ...
Number of issues identified during continuity tests
  • Number of issues identified during continuity tests to be addressed by continuity improvement initiatives.

Process description | → top

 

 

Metrics for the compliance management process

Process metrics: "Ensure compliance"
Quantitative process metrics Definition
Total number of compliance requirements
  • Number of compliance requirements managed through the compliance register, possibly grouped by types of requirements (e.g. legal, ISO standard, internal policy, ...).
Number of added compliance requirements
  • Number of compliance requirements added to the compliance register during the reporting period due to new laws or regulations, possibly grouped by types of requirements.
Number of removed compliance requirements
  • Number of compliance requirements removed from the compliance register during the reporting period, possibly grouped by types of requirements.
Qualitative process metrics Definition
Percentage of compliance requirements with controls in place
  • Percentage of compliance requirements where conformity is ensured through suitable controls or mechanisms, including defined responsibilities for their implementation and operation.
Percentage of compliance requirements covered by reviews
  • Percentage of compliance requirements which are covered by regular compliance reviews and audits.
Number of compliance reviews
  • Number of compliance reviews and audits carried out.
Number of issues identified during compliance reviews
  • Number of non-compliance issues identified during compliance reviews and audits, which are to be addressed for example by modifications to processes or services.
Number of issues reported outside compliance reviews
  • Number of non-compliance issues reported outside of formal compliance reviews and audits.
Time for fixing compliance issues
  • Average time lag between identification and resolution of non-compliance issues.

Process description | → top

 

 

Metrics for the HR management process

Process metrics: "Manage human resources"
Quantitative process metrics Definition
Number of staff
  • Total number of staff employed by the service provider organization.
Number of skills
  • Number of skills managed through the skills inventory.
Number of staff entering the organization
  • Number of employees who joined the service provider organization during the reporting period.
Number of staff leaving the organization
  • Number of employees who left the service provider organization during the reporting period.
Qualitative process metrics Definition
Number of skills added
  • Number of skills added to the skills inventory during the reporting period.
Number of skills removed
  • Number of skills removed from the skills inventory during the reporting period.
Number of skill development measures
  • Number of measures carried out through a skills development plan to improve the skills of individual employees, possibly grouped by type of skill, type of training, ...
Share of skills covered by development plans
  • Percentage of skills in the skills register for which training and education is managed through a skills development plan.

Process description | → top

 

 

Metrics for the supplier management process

Process metrics: "Manage suppliers"
Quantitative process metrics Definition
Number of suppliers
  • Number of external suppliers, possibly grouped by types, status, ...
Number of preferred suppliers
  • Number of external suppliers with "preferred supplier" status.
Number of new suppliers
  • Number of suppliers added to the supplier portfolio during the reporting period.
Number of terminated supplier agreements
  • Number of suppliers whose contracts were terminated during the reporting period.
Number of purchase orders
  • Number of purchase orders processed, possibly grouped by product categories, purchase order types (e.g. orders for non-standard products and services, orders for standard products), ...
Qualitative process metrics Definition
Share of external services covered by agreements
  • Percentage of externally supplied supporting services which are covered by external service agreements and corresponding service definitions.
Share of preferred suppliers
  • Share of goods and services procured from external suppliers with "preferred supplier" status, as a percentage of the value of all purchase orders.
Share of reviewed agreements
  • Percentage of supplier agreements which were reviewed for continued relevance during the reporting period.
Number of supplier meetings
  • Number of formal supplier meetings held during the reporting period.
Number of detected contract breaches
  • Number of contract breaches, for example detected during supplier review meetings or service reviews.
Time for issuing purchase orders
  • Average time between receiving internal purchasing requests and sending out purchase orders to suppliers, possibly grouped by product categories, purchase order types, ...

Process description | → top

 

 

Metrics for the financial management process

Process metrics: "Manage service financials"
Quantitative process metrics Definition
Total budget
  • Total budget of the service provider organization, possibly broken down into cost and revenue categories.
Budget change on previous period
  • Percentage of budget increase or decrease compared to the previous budgeting period, possibly broken down into cost and revenue categories.
Qualitative process metrics Definition
Adherence to financial forecasts
  • Deviation between predicted and actual spending and revenues, possibly grouped by cost and revenue categories.
Share of costs allocated to services
  • Percentage of overall costs which are allocated to the provision of particular services, possibly grouped by cost categories.
Share of charged services
  • Percentage of services where the customers are charged for service provision.
Share of profitable services
  • Percentage of customer services where revenues exceed the cost for service provisioning.
Share of investments with business cases
  • Percentage of investments approved during the reporting period where the budget request included an assessment of costs vs. benefits.
Share of investments with realized benefits
  • Percentage of investments made during the reporting period where the predicted benefits were realized.

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 Contributor: Stefan Kempter, IT Process Maps GbR, IT Process Maps.

 

Defining process metrics  › Quantitative and qualitative metrics  › KPIs for lifecycle processes  › KPIs for supporting processes