🛣️ PD CEN ISO TS 14907 is a series of technical specifications (TS) published by the British Standards Institution (BSI), concerned with test procedures for user equipment (on-board units, OBU) and fixed equipment (roadside equipment, RSE) in Electronic Fee Collection (EFC) systems. Prepared by ISO/TC 204 in collaboration with CEN/TC 278 and implemented in the UK as a CEN/TS, this batch covers Part 1, Description of test procedures (2015, superseding DD CEN ISO/TS 14907-1:2010), and Part 2, Conformance test for the on-board unit application interface (2016, superseding DD CEN ISO/TS 14907-2:2011). Together they provide a common test methodology for the interoperable deployment of EFC equipment across operators and countries.
💡 A Technical Specification (TS) is provisional in nature; CEN’s initial maintenance period is three years, after which member bodies decide whether to convert it into a European Standard (EN). When adopting a TS, monitor its version evolution and verify the latest revision.
1. Scope and Series Composition 📌
The series addresses testing of two categories of EFC equipment:
- User equipment (on-board unit, OBU): the device installed on a vehicle that participates in the charging transaction.
- Fixed equipment (roadside equipment, RSE / dedicated short-range communication, DSRC, sites): the device installed on the road or at a toll point that communicates with the OBU and completes the charging process.
| Standard | Edition | Subject | Primary Role |
| PD CEN ISO/TS 14907-1:2015 | 2015-09 | Description of test procedures | Defines test methods and test-process framework |
| PD CEN ISO/TS 14907-2:2016 | 2016-08 | Conformance test for the on-board unit application interface | Specifies OBU application-interface conformance testing |
⚠️ Each part replaces its earlier DD-series edition (2010 / 2011); always cite the latest version number and avoid using withdrawn editions.
2. Part 1: Description of Test Procedures 🔬
Part 1 provides the overall description of test procedures for EFC user and fixed equipment, forming the methodological basis for carrying out various EFC tests (functional, performance, interoperability). Its main content:
- Establishes the test objects, objectives, and applicable environment (laboratory or on-site/road environment).
- Specifies the preparation, execution, and recording steps to ensure reproducibility and traceability.
- Describes the supporting equipment and reference environment required (e.g., the DSRC communication link, reference OBU/RSE).
- Defines result interpretation and reporting requirements.
✅ A unified description of test procedures is the prerequisite for “same test, same result”: any laboratory following the same procedure yields comparable results, supporting mutual recognition of EFC equipment across vendors.
3. Part 2: On-Board Unit Application Interface Conformance Testing 🔧
Part 2 focuses on conformance testing of the OBU application interface. Its core objectives:
- Verify that the OBU’s externally exposed application interface conforms to the behaviour and data formats defined by the specification.
- Check each requirement of the application interface via conformance test cases, covering both normal and exceptional paths.
- Provide a conformance-level basis for OBU interoperability certification, reducing compatibility problems between equipment from different vendors.
💡 Conformance testing asks “does it meet the specification?”, while interoperability testing asks “can it work with the counterpart?”. Part 2 addresses the former and is a prerequisite stage for later interoperability certification.
4. Test-Method Points and Implementation 📊
| Test Dimension | Part 1 Emphasis | Part 2 Emphasis |
| Test object | User and fixed equipment as a whole | On-board unit application interface |
| Test type | Functional, performance, interoperability framework | Conformance test cases |
| Environment | Laboratory / on-site description | Primarily DSRC communication link |
| Output | Reproducible test steps and reporting requirements | Conformance verdict (pass/fail) |
⚠️ Before conformance testing, confirm the specification version and interface baseline declared by the OBU under test; a version mismatch invalidates the test result.
5. Engineering Practice and Application Advice 🛠️
- 🔍 Requirements mapping: when procuring OBU/RSE, translate the test requirements of the TS into acceptance clauses, requiring the supplier to provide a conformance report for the declared version.
- 🔗 Interface baseline management: use the Part 2 application-interface definition as the interface baseline and manage subsequent changes.
- 📋 Laboratory selection: select an independent laboratory with the appropriate capability, and follow Part 1’s step descriptions to ensure a traceable test process.
- 📊 Result archiving: retain conformance reports and raw records as evidence for equipment certification and warranty traceability.
6. FAQ ❓
Q: Is PD CEN ISO TS 14907 mandatory?
A: No. It is a Technical Specification (TS), a provisional guidance document, but it is often cited by procurement and certification schemes as a basis for acceptance and certification.
Q: How do Parts 1 and 2 divide the work?
A: Part 1 describes test procedures and the method framework; Part 2 focuses on conformance test cases and verdicts for the OBU application interface.
Q: What is the difference between conformance and interoperability testing?
A: Conformance testing verifies that equipment meets the specification; interoperability testing verifies that equipment from different vendors actually works together. The two are complementary.
Q: Which earlier editions does this series replace?
A: Part 1 replaces DD CEN ISO/TS 14907-1:2010; Part 2 replaces DD CEN ISO/TS 14907-2:2011.
Q: How does this series help cross-operator EFC interoperability?
A: Unified test procedures allow equipment from different vendors to be assessed under the same standard, providing the technical basis for cross-operator, cross-country EFC mutual recognition and interoperability.