📊 PD CEN ISO TS 17444 is a series of technical specifications (TS) published by the British Standards Institution (BSI), concerned with the charging performance of Electronic Fee Collection (EFC) systems. Prepared by ISO/TC 204 in collaboration with CEN/TC 278, the series provides a set of performance metrics and an examination framework for the accuracy of EFC charging (covering on-board units, roadside equipment, and back-office charging systems). This batch covers Part 1, Metrics (2012), and Part 2, Examination Framework (2013), providing a standardised way to quantify the core question: “is the fee that should be charged charged correctly and in full?”.
⚠️ Charging performance directly affects operator revenue and user trust: undercharging causes revenue loss, while overcharging damages user confidence. By using unified metrics and examination methods, this series enables parties to objectively evaluate and continuously improve EFC charging quality.
1. Scope and Series Composition 📌
This series applies to the performance evaluation of charging-related functions in an EFC system, covering the full chain from transaction occurrence to back-office settlement. The primary audiences:
- EFC system operators: to assess current charging quality and set improvement targets.
- Equipment and system suppliers: to provide performance data available for examination.
- Regulators and auditors: to conduct independent evaluation against unified metrics.
| Standard | Edition | Subject | Primary Role |
| PD CEN ISO/TS 17444-1:2012 | 2012-10 | Metrics | Defines charging-performance metrics |
| PD CEN ISO/TS 17444-2:2013 | 2013-11 | Examination Framework | Specifies the method and framework for applying metrics |
💡 A Technical Specification (TS) is provisional; CEN’s initial maintenance period is three years. Always check the latest revision and publication status when citing.
2. Part 1: Charging Performance Metrics 🔬
Part 1 defines the metrics used to evaluate EFC charging performance. The core directions:
- Charging-completeness metrics: evaluate whether “the fee that should be collected is collected completely and in time”, including a quantified expression of transaction success rate.
- Charging-accuracy metrics: evaluate whether “the amount actually charged equals the amount that should be charged”, characterising amount-level deviation.
- Error classification and statistics: define and unify the classification and statistical basis for undercharging, overcharging, and wrong-charging cases.
- Data acquisition and basis: specify the data sources, observation window, and statistical basis needed to compute metrics, ensuring comparability.
✅ A unified metric basis is the prerequisite for cross-system, cross-operator comparability: only when all parties compute using the same formula and data basis do charging-performance figures become meaningful for horizontal comparison and longitudinal trend tracking.
3. Part 2: Examination Framework 🔧
Part 2 specifies how to apply the metrics to conduct an examination, bringing the metrics into operational practice:
- Defines the examination objective: the question to be answered (e.g., whether system charging performance meets the contractually agreed level).
- Specifies examination methods: how to collect samples, how to run the observation period, and how to handle anomalous data.
- Provides result analysis and reporting requirements, supporting traceability of the examination conclusion.
- Establishes the correspondence between metrics and examination scenarios, covering normal operation, fault recovery, and other states.
⚠️ The reliability of an examination conclusion depends on sample representativeness and observation-period length: too small a sample or too short a period can produce statistically insignificant conclusions. Follow Part 2’s requirements on sampling and methods when conducting an examination.
4. Technical Points and Implementation Path 📊
| Stage | Part 1 Emphasis | Part 2 Emphasis |
| Definition | Metric system and statistical basis | Examination objectives and scenarios |
| Method | Metric formulas and data sources | Sampling, observation period, data processing |
| Output | Computable performance metrics | Examination conclusions and reports |
| Application | Horizontal comparison, trend tracking | Compliance determination, remediation verification |
💡 In practice, embed the Part 1 metrics into the operational monitoring system for continuous calculation, and conduct independent examinations periodically under the Part 2 framework, forming a dual-track mechanism of “daily monitoring + periodic examination”.
5. Engineering Practice and Application Advice 🛠️
- 🔍 Contract alignment: cite this series’ metrics and examination methods in EFC contracts and service-level agreements (SLAs), defining performance thresholds and assessment mechanisms.
- 📊 Instrumentation: instrument the transaction chain to capture the data needed for metric computation, ensuring data completeness and consistent basis.
- 📋 Periodic examination: establish a periodic examination plan under the Part 2 framework and conduct independent, traceable checks on charging performance.
- 🔧 Continuous improvement: use metric trends to identify weak points (e.g., communication failures, settlement discrepancies) and drive a closed improvement loop.
6. FAQ ❓
Q: What is charging performance?
A: It is the completeness and accuracy of an EFC system when collecting the fee that should be charged, quantified by metrics asking “was everything that should be charged charged, and was it charged correctly?”.
Q: How do Parts 1 and 2 divide the work?
A: Part 1 defines the metrics and statistical basis; Part 2 specifies the method and framework for applying the metrics to conduct an examination.
Q: Is this series mandatory?
A: No. It is a Technical Specification (TS), a provisional guidance document, often incorporated into contracts and SLA assessment.
Q: How is charging performance made comparable across systems?
A: By computing using the unified Part 1 metric formulas and data basis, and conducting examinations using the unified Part 2 method.
Q: What practical value does this series offer to operations?
A: It turns abstract quality requirements into quantifiable, examinable metrics, helping operators detect under- and over-charging, protecting revenue and user trust.