Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC TS 25025:2019 — IT Service Quality Measures
ISO/IEC TS 25025 — Technical Specification Overview
Introduction to ISO/IEC TS 25025
ISO/IEC TS 25025:2019 is a companion Technical Specification to TS 25011, providing a comprehensive set of quantitative measures for evaluating the quality of IT services. While TS 25011 defines what service quality means through its quality models, TS 25025 answers the practical question of how to measure it. This specification defines a measurement framework comprising base measures, derived measures, and quality measure elements that map directly to the service quality characteristics defined in TS 25011.
TS 25025 bridges the gap between abstract quality models and operational measurement, enabling organizations to implement objective, repeatable, and comparable service quality evaluations.
The specification organizes measures according to the two quality models from TS 25011: measures for service quality in use characteristics (effectiveness, efficiency, satisfaction, freedom from risk, context coverage) and measures for service product quality characteristics (functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, portability). Each measure includes a precise definition, measurement formula, scale type, unit of measurement, and guidance on interpretation.
For engineers and service managers, TS 25025 provides the toolset needed to move from subjective service quality assessments to data-driven quality management. The measures are designed to be applicable across different types of IT services — from infrastructure services to platform services to software-as-a-service — while accommodating the specific characteristics of each service type through tailored measurement guidance.
Key Measurement Areas and Practical Application
Service Quality in Use Measures
The quality in use measures focus on outcomes as experienced by service stakeholders. Key measurement areas include:
| Quality Characteristic | Example Measure | Measurement Approach | Engineering Application |
|---|---|---|---|
| Effectiveness | Task completion rate | Ratio of successfully completed service tasks to total attempted tasks over a specified period | Use as primary SLA metric for service outcome quality; benchmark against industry peers |
| Efficiency | Time per service transaction | Average elapsed time from service request submission to completion | Identify bottlenecks in service delivery workflows; set efficiency targets for automated vs. manual processes |
| Satisfaction | Customer satisfaction score | Mean score from standardized satisfaction survey on a 1-5 or 1-10 Likert scale | Correlate with operational metrics to identify satisfaction drivers; track trends quarterly |
| Freedom from Risk | Service availability | Percentage of agreed service time during which the service is accessible and functional | Set availability targets with appropriate credit regimes; distinguish planned vs. unplanned downtime in reporting |
| Context Coverage | Accessibility compliance rate | Percentage of service functions accessible to users with disabilities | Design for WCAG compliance; test with assistive technologies across multiple platforms |
When selecting measures from TS 25025, avoid the common mistake of measuring only what is easy to measure. A balanced measurement framework should cover all relevant quality characteristics, not just the most quantifiable ones. Some characteristics, such as satisfaction and context coverage, require qualitative or mixed-method approaches.
Service Product Quality Measures
From the provider’s engineering perspective, the following measurement areas are particularly relevant:
| Characteristic | Key Measures | Measurement Frequency | Practical Insight |
|---|---|---|---|
| Functional Suitability | Functional completeness, functional correctness, functional appropriateness | Per release cycle | Measure functional coverage against requirements traceability matrix; track feature usage to identify underutilized functions |
| Performance Efficiency | Response time, throughput, resource utilization, capacity margin | Continuous monitoring | Establish performance budgets; implement auto-scaling based on measured demand patterns |
| Reliability | Mean time between failures (MTBF), mean time to restore (MTTR), fault density | Continuous monitoring with monthly reporting | Use MTBF/MTTR trends to assess reliability improvement initiatives; target MTTR reduction through automated incident response |
| Security | Security incident count, vulnerability remediation time, access control effectiveness | Continuous with weekly review | Implement security information and event management (SIEM); track mean time to detect (MTTD) and mean time to respond (MTTR) for security events |
| Maintainability | Modification cycle time, change failure rate, configuration drift | Per change cycle | Measure lead time for changes; track change failure rate as a key indicator of process maturity |
Implementing a TS 25025-Based Measurement Program
Implementing a measurement program based on TS 25025 requires careful planning and organizational commitment. The recommended implementation approach follows these steps:
Step 1 — Measurement Needs Analysis: Identify the key stakeholders and their information needs. Different stakeholders (service consumers, service providers, regulators, auditors) require different measures and levels of aggregation.
Step 2 — Measure Selection: Select measures from the TS 25025 catalog that align with identified information needs and organizational goals. Avoid selecting too many measures — focus on a core set of 10-15 key measures that provide actionable insights.
Step 3 — Operational Definition: For each selected measure, define the operational details including data sources, collection frequency, calculation formulas, reporting format, and escalation thresholds. TS 25025 provides the standard definitions, but organizations must tailor them to their specific context.
Step 4 — Tooling and Automation: Implement measurement collection and reporting tools. Where possible, automate data collection to reduce manual effort and ensure consistency. Service management platforms, monitoring systems, and business intelligence tools can all contribute to the measurement infrastructure.
Step 5 — Baseline and Target Setting: Collect baseline measurements over an initial period (typically 2-3 measurement cycles) to establish current performance levels. Use these baselines, together with business requirements and industry benchmarks, to set realistic but challenging targets.
A measurement program that is not reviewed and acted upon is worse than no measurement program at all — it consumes resources while creating the illusion of quality management. TS 25025-based measures must be integrated into regular service reviews and management decision-making processes.
Step 6 — Continuous Improvement: Review measurement results regularly in service management forums. Use statistical process control techniques to distinguish common cause variation from special cause variation. When measures indicate performance degradation, initiate problem management activities to identify and address root causes.
TS 25025 represents an essential tool for any organization serious about IT service quality. By providing a standardized measurement framework aligned with the TS 25011 quality models, it enables objective, comparable, and actionable service quality evaluation across the entire service portfolio.
Frequently Asked Questions
Q1: How many measures does TS 25025 define?
A: TS 25025 defines over 100 measures covering both the service quality in use model and the service product quality model. Not all measures are applicable to every service; organizations should select a subset based on their specific needs and context.
A: TS 25025 defines over 100 measures covering both the service quality in use model and the service product quality model. Not all measures are applicable to every service; organizations should select a subset based on their specific needs and context.
Q2: Can TS 25025 measures be automated?
A: Many measures can be automated, particularly those related to performance efficiency, reliability, and security. Measures related to satisfaction and context coverage typically require manual data collection through surveys and usability testing, though sentiment analysis tools can provide partial automation.
A: Many measures can be automated, particularly those related to performance efficiency, reliability, and security. Measures related to satisfaction and context coverage typically require manual data collection through surveys and usability testing, though sentiment analysis tools can provide partial automation.
Q3: How does TS 25025 relate to ISO/IEC 25023?
A: ISO/IEC 25023 defines measures for system and software product quality, while TS 25025 specifically addresses IT service quality measures. They share a common measurement framework approach but target different domains — software products vs. IT services.
A: ISO/IEC 25023 defines measures for system and software product quality, while TS 25025 specifically addresses IT service quality measures. They share a common measurement framework approach but target different domains — software products vs. IT services.
Q4: Is TS 25025 suitable for measuring microservices-based architectures?
A: Yes, TS 25025 can be applied to modern distributed architectures. However, additional consideration must be given to measuring end-to-end service quality across multiple microservices, as individual component measures do not necessarily aggregate linearly to overall service quality.
A: Yes, TS 25025 can be applied to modern distributed architectures. However, additional consideration must be given to measuring end-to-end service quality across multiple microservices, as individual component measures do not necessarily aggregate linearly to overall service quality.
