Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD CEN ISO TR 24014 — Public Transport Interoperable Fare Management System (IFMS) Technical Report Series (Business Practices and Multi-Application Media)
Public Transport — Interoperable Fare Management System (IFMS) Technical Report Series
🚌 PD CEN ISO TR 24014 is a series of technical reports (TR) published by the British Standards Institution (BSI) adopting joint CEN/ISO work, concerned with the Interoperable Fare Management System (IFMS) for public transport. Prepared by ISO/TC 204 “Intelligent transport systems” in collaboration with CEN/TC 278 “Intelligent transport systems” (secretariat held by NEN), the series establishes an interoperable, extensible framework of fare management rules that can be shared across operators, fare media, and charging policies. This batch covers Part 2, Business practices, and Part 3, Complementary concepts to Part 1 for multi-application media, which together with Part 1 form the complete IFMS rule framework.
💡 A Technical Report is a non-mandatory, guidance-type document and does not impose legal obligations on contracting parties. Its value lies in providing harmonised, reusable business and technical methods that help operators reduce ambiguity when procuring, building, and operating interoperable fare systems.
1. Scope and Series Framework 📌
The PD CEN ISO TR 24014 series addresses fare management involving multiple stakeholders (operators, fare-service providers, clearing houses, equipment and media suppliers). Its central concept is the Set of Rules: a body of rules agreed by stakeholders to govern fare business and data exchange. The series is modular, composed of several parts:
| Part | Standard | Subject | Role |
|---|---|---|---|
| Part 1 | ISO/TR 24014-1 | IFMS overall framework and basic concepts | Framework TR |
| Part 2 | PD CEN ISO/TR 24014-2:2013 | Business practices | Set of Rules structure and business entities |
| Part 3 | PD CEN ISO/TR 24014-3:2013 | Complementary concepts to Part 1 for multi-application media | Media and multi-application scenarios |
⚠️ Per the national foreword, Parts 2 and 3 together with Part 1 supersede BS EN ISO 24014-1:2007, which is withdrawn upon publication of Part 1. Note the version-replacement relationship when citing this series.
2. Structure and Classification of the Set of Rules 🔧
Part 2, Business practices, systematically describes the structure of the Set of Rules. The Set of Rules is not a single document but a hierarchy of a core part and an extra part, together with a classification method and a table form:
- Classification of the Set of Rules: rules are categorised by scope, stakeholders, and business domain for easier retrieval and maintenance.
- Table form: rules are presented in tabular form so stakeholders can quickly locate and cross-reference them.
- Structure of the core part: the invariant, general clauses that all stakeholders must observe.
- Structure of the extra part: extensible clauses that vary by application scenario, available to specific markets or operators.
- Transformation into business entities: a method for mapping the Set of Rules structure into business entities so it can be instantiated in an information system.
- Three-dimensional model: a “function–stakeholder–data” model describing collaboration among functional modules.
✅ The structured expression of the Set of Rules is the core contribution of this series: it translates abstract fare rules into executable, verifiable, and auditable business entities, providing a common basis for later information-system implementation and conformance testing.
3. Multi-Application Media Complementary Concepts 📇
Part 3, Complementary concepts to Part 1 for multi-application media, supplements Part 1 for the realistic case of one medium carrying multiple applications (for example a single smart card holding transit, metro, parking, and retail e-wallet applications). Key points include:
- Defining the security-domain partitioning and access-rights management of each application on the medium, preventing cross-application unauthorized access.
- Specifying data isolation requirements when fare data and non-fare application data coexist on the same medium.
- Supplementing mechanisms for combining and resolving conflicts among fare Set of Rules in multi-application scenarios.
- Providing supplementary concepts and operational guidance for the media lifecycle (issuance, personalisation, blocking, reissue, and deactivation).
💡 Multi-application media are the common form of real fare systems: a single card or mobile wallet often carries several fare and payment applications. Part 3 matters precisely because it lets the IFMS framework accommodate such composite media rather than only single-application tickets.
4. Key Business-Practice Points 📊
Drawing on the business-practice content of Part 2, the following points should be considered when implementing an interoperable fare system:
| Business Stage | Practice Point | Set of Rules Element |
|---|---|---|
| Rule definition | Define the scope, stakeholders, and applicable scenarios of the fare rules | Classification, core/extra parts |
| Media management | Govern media issuance, personalisation, blocking, and recovery | Media lifecycle, security domains |
| Multi-application coexistence | Ensure data isolation and access control across applications | Multi-application concepts (Part 3) |
| Data exchange | Harmonise data models and interfaces so all parties interoperate | Business-entity transformation, 3D model |
| Clearing and settlement | Define fare allocation, settlement, and reconciliation rules | Business practices (Part 2) |
⚠️ The Technical Report does not mandate specific numeric requirements; fares, limits, and security policies must be set by operators under local regulation and commercial contracts. The series offers a citable rule framework and methods.
5. Engineering Practice and Application Advice 🛠️
- 🔍 Requirements modelling: early in system design, capture fare rules in the tabular Set of Rules form, distinguishing core from extra parts to avoid requirements drift.
- 🔗 Interface design: define data models and interface contracts using the business-entity transformation method so that equipment and back-office systems from different vendors interoperate.
- 📋 Compliance verification: for multi-application media systems, verify each application’s security domain and permissions, and perform cross-application access and penetration testing.
- 📊 Operational monitoring: establish fare clearing and reconciliation processes, and validate the completeness and consistency of transactions on multi-application media.
6. FAQ ❓
Q: Is PD CEN ISO TR 24014 mandatory?
A: No. It is a Technical Report (TR), a guidance document that does not impose contractual requirements. Fare business rules should be agreed by operators under local regulation and contracts.
A: No. It is a Technical Report (TR), a guidance document that does not impose contractual requirements. Fare business rules should be agreed by operators under local regulation and contracts.
Q: How does this series relate to BS EN ISO 24014-1:2007?
A: Parts 2 and 3, together with Part 1, supersede BS EN ISO 24014-1:2007, which is withdrawn upon publication of Part 1.
A: Parts 2 and 3, together with Part 1, supersede BS EN ISO 24014-1:2007, which is withdrawn upon publication of Part 1.
Q: What is the difference between the core and extra parts of the Set of Rules?
A: The core part contains invariant general clauses that all stakeholders must observe; the extra part contains extensible clauses that vary by scenario and are available to specific markets or operators.
A: The core part contains invariant general clauses that all stakeholders must observe; the extra part contains extensible clauses that vary by scenario and are available to specific markets or operators.
Q: Why is multi-application media described separately?
A: Because real fare systems often carry several applications on the same medium (smart card / mobile wallet), requiring additional security-domain partitioning, data isolation, and combination rules to ensure cross-application safety and interoperability.
A: Because real fare systems often carry several applications on the same medium (smart card / mobile wallet), requiring additional security-domain partitioning, data isolation, and combination rules to ensure cross-application safety and interoperability.
Q: How does this series help system implementation?
A: It provides a structured, reusable rule framework that translates abstract fare rules into business entities and data models, supporting system design, interface definition, and conformance verification.
A: It provides a structured, reusable rule framework that translates abstract fare rules into business entities and data models, supporting system design, interface definition, and conformance verification.