Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD CEN ISO TS 16401 — Evaluation of EFC Equipment for Conformity to ISO/TS 17575-2 (Test Suite Structure and Abstract Test Suite)
Electronic Fee Collection — Evaluation of Equipment for Conformity to ISO/TS 17575-2 — Technical Specification Series
💰 PD CEN ISO TS 16401 is a series of technical specifications (TS) published by the British Standards Institution (BSI), concerned with evaluation of electronic fee collection (EFC) equipment for conformity to ISO/TS 17575-2. Prepared by ISO/TC 204 in collaboration with CEN/TC 278 (secretariat held by NEN) and implemented in the UK as a CEN/TS, the series provides a structured test methodology for determining whether EFC equipment conforms to ISO/TS 17575-2, the EFC application-layer data-exchange specification. This batch covers Part 1, Test suite structure and test purposes, and Part 2, Abstract test suite (both 2012 editions), which together form the conformance-test system for ISO/TS 17575-2.
💡 ISO/TS 17575-2 defines the data structures and behaviour of user data interchange (application interface) in an EFC system; PD CEN ISO TS 16401 answers “how do we verify that a device conforms to that specification?” — the two are used together.
1. Scope and Series Composition 📌
This series addresses the conformity evaluation of EFC equipment (in particular on-board units and their application layer) designed and declared against ISO/TS 17575-2. It primarily serves:
- Equipment manufacturers: to verify that the product design meets the specification.
- Certification and test bodies: to execute standardised, reproducible conformance tests.
- Operators and procurers: to use conformance test reports as the basis for equipment acceptance and mutual recognition.
| Standard | Edition | Subject | Primary Role |
|---|---|---|---|
| PD CEN ISO/TS 16401-1:2012 | 2012-03 | Test suite structure and test purposes | Defines test-suite organisation and the purpose of each test |
| PD CEN ISO/TS 16401-2:2012 | 2012-03 | Abstract test suite | Provides an executable set of abstract test cases |
⚠️ A Technical Specification (TS) is provisional; CEN’s initial maintenance period is three years. Always check the latest revision and publication status when citing, and avoid withdrawn editions.
2. Part 1: Test Suite Structure and Test Purposes 🔬
Part 1 provides the organisation of the test suite and the purpose of each test for the conformity evaluation. Its main content:
- Defines how the test suite is grouped and organised so that it covers the different clauses and functional modules of the specification.
- Gives each test a clear test purpose, explaining what it verifies and why it is needed.
- Establishes traceability between tests and specification clauses, ensuring complete coverage.
- Provides the structural skeleton and test-case organisation principles for the abstract test suite (Part 2).
✅ Clear test purposes are key to good conformance testing: every test should be able to answer “which requirement of the specification does this test verify?”, avoiding purposeless, hard-to-trace tests.
3. Part 2: Abstract Test Suite 🔧
Part 2 provides the Abstract Test Suite (ATS), i.e., a set of implementation-independent, executable abstract test cases. Its core content:
- Concretises the Part 1 test purposes into test cases covering normal, boundary, and exceptional paths.
- Defines each test case’s preconditions, test steps, and expected results.
- Provides abstract test methods from which concrete test scripts can be derived for different platforms.
- Supports item-by-item verification of the application-layer data-exchange behaviour defined by ISO/TS 17575-2.
💡 An “abstract” test suite is platform-independent; test-tool vendors can derive concrete executable scripts from it. It standardises the test logic so that laboratories do not produce incomparable results by designing their own tests.
4. Conformance-Test Points and Implementation 📊
| Dimension | Part 1 Emphasis | Part 2 Emphasis |
|---|---|---|
| Deliverable | Test-suite structure and test purposes | Abstract test suite (test cases) |
| Covered object | Overall clauses of ISO/TS 17575-2 | Item-by-item validation of application-layer data exchange |
| Traceability | Test–clause mapping | Test-case–test-purpose mapping |
| Implementation level | Organisation and planning | Basis for executable test scripts |
⚠️ Conformance verdicts are valid only against the consistency and testability preconditions declared by the specification; if the declared specification version differs from the test-suite baseline, the test conclusion does not hold.
5. Engineering Practice and Application Advice 🛠️
- 🔍 Test planning: plan the test campaign using the Part 1 test-suite structure, defining coverage and test purposes.
- 🔗 Test-case derivation: derive executable scripts for a specific test platform from the Part 2 abstract test suite.
- 📋 Conformity declaration: require manufacturers to provide a declaration of conformity and the corresponding test report, stating the specification version used.
- 📊 Defect management: trace conformance findings back to clauses, forming a defect list with a closed correction loop.
6. FAQ ❓
Q: What is the relationship between PD CEN ISO TS 16401 and ISO/TS 17575-2?
A: ISO/TS 17575-2 defines the EFC application-layer data-exchange specification; PD CEN ISO TS 16401 provides the conformity-evaluation method for determining whether equipment conforms to it.
A: ISO/TS 17575-2 defines the EFC application-layer data-exchange specification; PD CEN ISO TS 16401 provides the conformity-evaluation method for determining whether equipment conforms to it.
Q: What is the difference between Parts 1 and 2?
A: Part 1 defines the test-suite structure and test purposes; Part 2 provides the executable abstract test suite (a set of test cases).
A: Part 1 defines the test-suite structure and test purposes; Part 2 provides the executable abstract test suite (a set of test cases).
Q: What is an Abstract Test Suite (ATS)?
A: A set of implementation-independent, executable abstract test cases defining preconditions, steps, and expected results, from which tools can derive concrete scripts.
A: A set of implementation-independent, executable abstract test cases defining preconditions, steps, and expected results, from which tools can derive concrete scripts.
Q: Is this series mandatory?
A: No. It is a Technical Specification (TS), a provisional guidance document, often cited by procurement and certification schemes.
A: No. It is a Technical Specification (TS), a provisional guidance document, often cited by procurement and certification schemes.
Q: How does this series help mutual recognition of EFC equipment?
A: A unified test suite and test purposes allow equipment from different vendors to be assessed under the same standard, providing a consistency basis for cross-vendor, cross-operator mutual recognition.
A: A unified test suite and test purposes allow equipment from different vendors to be assessed under the same standard, providing a consistency basis for cross-vendor, cross-operator mutual recognition.