BS EN ISO 24014-1:2015
$215.11
Public transport. Interoperable fare management system – Architecture
Published By | Publication Date | Number of Pages |
BSI | 2015 | 72 |
This part of ISO 24014 provides the basis for the development of multi-operator/multi-service Interoperable public surface (including subways) transport Fare Management Systems (IFMSs) on a national and international level.
This part of ISO 24014 is applicable to bodies in public transport and related services which agree that their systems need to interoperate.
While this part of ISO 24014 does not imply that existing interoperable fare management systems need to be changed, it applies so far as it is practically possible to extensions of these.
This part of ISO 24014 covers the definition of a conceptual framework which is independent of organisational and physical implementation. Any reference within this part of ISO 24014 to organisational or physical implementation is purely informative.
The objective of this part of ISO 24014 is to define a reference functional architecture for IFMSs and to identify the requirements that are relevant to ensure interoperability between several actors in the context of the use of electronic tickets.
The IFMS includes all the functions involved in the fare management process such as
-
management of application,
-
management of products,
-
security management, and
-
certification, registration, and identification.
This part of ISO 24014 defines the following main elements:
-
identification of the different set of functions in relation to the overall fare management system;
-
a generic model of IFMS describing the logical and functional architecture and the interfaces within the system and with other IFMSs;
-
use cases describing the interactions and data flows between the different set of functions;
-
security requirements.
This part of ISO 24014 excludes consideration of the following:
-
the physical medium and its management;
-
the technical aspects of the interface between the medium and the medium access device;
-
the data exchanges between the medium and the medium access device;
NOTEThe data exchanges between the Medium and the Medium Access Device are proposed by other standardization committees.
-
the financial aspects of fare management systems (e.g. customer payments, method of payment, settlement, apportionment, reconciliation).
PDF Catalog
PDF Pages | PDF Title |
---|---|
4 | Foreword Endorsement notice |
7 | Foreword |
8 | Introduction |
9 | 1 Scope |
10 | 2 Terms and definitions |
12 | 3 Abbreviated terms 4 Requirements |
13 | 5 Conceptual framework |
14 | 5.1 Description of IFM-roles |
16 | 5.2 Basic framework of the generic IFM functional model |
17 | 6 Use Case description for the IFM functional model 6.1 Certification |
18 | 6.1.1 Certification of Organization 6.1.2 Certification of Components 6.1.3 Certification of Application Specification and Template |
19 | 6.1.4 Certification of Product Specification and Template 6.2 Registration 6.2.1 Registration of Organization |
20 | 6.2.2 Registration of Component 6.2.3 Registration of Application Template 6.2.4 Registration of Application 6.2.5 Registration of Product Template |
21 | 6.2.6 Registration of Product 6.3 Management of Application 6.3.1 Dissemination of Application Template |
22 | 6.3.2 Acquisition of Application 6.3.3 Termination of Application Template |
23 | 6.3.4 Termination of Application |
24 | 6.4 Management of Product 6.4.1 Dissemination of Product Template |
25 | 6.4.2 Termination of Product Template 6.4.3 Management of Action List |
26 | 6.4.4 Acquisition of Product 6.4.5 Modification of Product parameter |
27 | 6.4.6 Termination of Product 6.4.7 Use and inspection of Product |
28 | 6.4.8 Collection of data |
29 | 6.4.9 Forwarding data 6.4.10 Generation and distribution of clearing reports |
30 | 6.5 Security management 6.5.1 Monitoring of IFM processes and IFM data life cycle |
31 | 6.5.2 Management of IFM security keys 6.5.3 Management of security lists |
33 | 6.6 Customer Service Management (optional) |
34 | 7 System interface identification 8 Identification 8.1 General 8.2 Numbering scheme 8.3 Prerequisites |
35 | 9 Security in IFMSs 9.1 Protection of the interests of the public 9.2 Assets to be protected |
36 | 9.3 General IFM security requirements |
37 | Annex A (informative) Information flow within the IFM |
47 | Annex B (informative) Examples of implementation |
56 | Annex C (informative) List of terms which are defined both in this part of ISO 24014 (IFMSA) and in APTA — UTFS |
57 | Annex D (informative) Example of Action List processes |
62 | Annex E (informative) Security domain, threats, and Protection Profiles |
66 | Annex F (informative) Media centric management and back-office centric management |
68 | Bibliography |