How to measure the performance of the YaSM service lifecycle processes? The following tables provide you with suggestions for quantitative and qualitative process metrics.
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.
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.
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 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, ...