Service Management Metrics: Difference between revisions
No edit summary |
No edit summary |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
<itpmch><title>Service Management Metrics | YaSM | <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="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="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." /> | ||
Line 5: | Line 5: | ||
<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="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: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="og:image" content="https://yasm.com/wiki/en/img/yasm-metric/16x9/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="675" /> | <meta property="og:image:height" content="675" /> | ||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
Line 25: | Line 15: | ||
<p> </p> | <p> </p> | ||
<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"><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> | ||
<html><div | <html><div itemid="https://yasm.com/wiki/en/img/yasm-metric/Service-management-metrics-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject"> | ||
<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 54: | Line 43: | ||
<meta itemprop="datePublished" content="2019-06-16" /> | <meta itemprop="datePublished" content="2019-06-16" /> | ||
</span> | </span> | ||
<span style="word-wrap:normal;">[[#Defining_process_metrics|Defining | <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> | ||
<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> | <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> </p> | <p> </p> | ||
Line 66: | Line 55: | ||
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® [[#ITIL|[1]]], COBIT® [[#COBIT|[2]]] and USMBOK™ [[#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® [[#ITIL|[1]]], COBIT® [[#COBIT|[2]]] and USMBOK™ [[#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 92: | Line 81: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Set the strategic direction" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 145: | Line 134: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Design new or changed services" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 194: | Line 183: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Build new or changed services" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 251: | Line 240: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Operate the services" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 308: | Line 297: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Resolve incidents and service requests" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 369: | Line 358: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Resolve problems" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 414: | Line 403: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Improve the services" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 451: | Line 440: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Set up and maintain the service management system" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 504: | Line 493: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Maintain the service portfolio" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 553: | Line 542: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage customer relationships" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 606: | Line 595: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage configuration information" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 663: | Line 652: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Assess and coordinate changes" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 724: | Line 713: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage projects" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 761: | Line 750: | ||
<p> </p> | <p> </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:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Ensure security" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 826: | Line 815: | ||
<p> </p> | <p> </p> | ||
===<span id="metrics-sp8">Metrics for the | ===<span id="metrics-sp8">Metrics for the service continuity management process</span>=== | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Ensure continuity" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
!style="background:#eeeeee; width:70%"|Definition | !style="background:#eeeeee; width:70%"|Definition | ||
|- | |- | ||
|Number of managed | |Number of managed critical events | ||
| | | | ||
*Number of (types of) | *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 846: | Line 835: | ||
!style="background:#eeeeee; width:70%"|Definition | !style="background:#eeeeee; width:70%"|Definition | ||
|- | |- | ||
|Percentage of managed | |Percentage of managed critical events covered by continuity arrangements | ||
| | | | ||
*Percentage of identified and managed | *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 | *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 | *Average duration from the identification of a new threat from a critical event to the implementation of a suitable response. | ||
|- | |- | ||
|Number of | |Number of critical events | ||
| | | | ||
*Number of | *Number of critical events occurred during the reporting period. | ||
|- | |- | ||
|Number of | |Number of critical events with continuity arrangements in place | ||
| | | | ||
*Number of | *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 878: | 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;">→ [[SP8: | <p style="float:right;">→ [[SP8: Ensure continuity|Process description]] | → [[#sp-metrics|top]]</p> | ||
<p> </p> | <p> </p> | ||
<p> </p> | <p> </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:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Ensure compliance" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 940: | Line 929: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage human resources" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 989: | Line 978: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage suppliers" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 1,050: | Line 1,039: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
|+ style="background:# | |+ style="background:#465674; color:#ffffff; font-size: 110%" colspan="2"|Process metrics: "Manage service financials" | ||
|- | |- | ||
!style="background:#eeeeee; width:30%"|Quantitative process metrics | !style="background:#eeeeee; width:30%"|Quantitative process metrics | ||
Line 1,129: | 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
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 management 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 service continuity management process
Quantitative process metrics | Definition |
---|---|
Number of managed critical events |
|
Number of continuity plans |
|
Qualitative process metrics | Definition |
Percentage of managed critical events covered by continuity arrangements |
|
Number of implemented continuity arrangements |
|
Time for implementation of continuity arrangements |
|
Number of critical events |
|
Number of critical 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 management 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