ISO/TC 204/WG 8 - Public transport/emergency
Transports publics/urgences
General Information
This document specifies the general framework and the automated driving bus (ADB) system components for operating ADBs in public transport networks, including: a) the general framework and the operation scheme for public transport systems in cooperation with ADBs; b) definitions of system components for operating ADBs; and c) definitions of functions and requirements of each system component for providing transport services with ADBs. This document is applicable to bodies in public transport systems and services including transportation operators, public transport governing authorities and relevant industries.
- Standard35 pagesEnglish languagesale 15% off
This document specifies an open, XML-based data format which enables an efficient and unambiguous exchange of static information concerning the operational functionality of the infrastructure, rolling stock and timetable of a track-bound transportation system. The main objective is to enable heterogeneous railway applications to communicate with each other. The purpose of the data format is to facilitate common (integrated) planning of track-bound operations between organizations in the transportation sector. Railway Data Exchange (RailDax) serves as a data exchange format between applications used for railway service planning: connecting information about infrastructure, rolling stock and timetable basics which are necessary for capacity management and timetable planning. This document describes infrastructure and rolling stock from an operational perspective. To achieve this, the infrastructure and rolling stock is described with a clearly defined meaning from an operational perspective. RailDax will typically be used by railway authorities, train operators, infrastructure managers and suppliers to the railway industry for communication between applications serving the use cases listed in Clause 7 in this document.
- Technical specification73 pagesEnglish languagesale 15% off
This document presents methods to establish technical interoperability between the contactless interfaces of NFC mobile devices and those of public transport readers and customer media. It provides information on how to apply these for public transport fare management systems which are using ISO/IEC 14443 and/or ISO/IEC 18092 and/or EMV® Contactless Interface Specification[1] [9] as a basis for contactless communication. This document deals with the application of standards, specifications and certification schemes from other organizations and standards bodies. These organizations and standards bodies are solely responsible for the content and the maintenance of these standards, specifications and certification schemes. This document focuses on the technical interoperability of the contactless interfaces of NFC mobile devices and public transport devices. The goal is to reliably support communication and the exchange of data. Syntactic and semantic interoperability, i.e. the support for a particular public transport fare management application, is not covered by this document. However, practical experience shows that if technical interoperability is established successfully, the adoption of a specific public transport application can typically be achieved by loading the fare management system’s particular application software onto the NFC mobile device. [1] This trade name is provided for reasons of public interest or public safety. This information is given for the convenience of users of this document and does not constitute an endorsement by ISO.
- Technical report11 pagesEnglish languagesale 15% off
This document gives guidelines 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 document is applicable to bodies in public transport and related services which agree that their systems need to interoperate. This document defines a conceptual framework which is independent of organizational and physical implementation. Any reference within this document to organizational or physical implementation is purely informative. This document defines a reference functional architecture for IFMSs and establishes the requirements that are relevant for ensuring 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 media, — management of applications, — management of products, — security management, and — certification, registration, and identification. This document defines the following main elements: — identification of the different sets of functions in relation to the overall IFMS and services and media from non-transport systems which interact with fare management systems; — a generic model of an IFMS describing the logical and functional architecture and the interfaces within the system, with other IFMSs and with services and media from non-transport systems; — use cases describing the interactions and data flows between the different sets of functions; — security requirements. In its annexes, this document provides a framework for mobility platforms that integrate fare management and travel information for inter- and multimodal travel (see Annex A). It also elaborates on specific subjects covered in document and offers some national examples with regard to IFMS implementations (see Annex B, Annex C, Annex D and Annex E). This document does not define: — 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; NOTE The 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).
- Standard81 pagesEnglish languagesale 15% off
- Standard85 pagesFrench languagesale 15% off
- Draft81 pagesEnglish languagesale 15% off
This document describes the characteristics of a Common Transport Service Account System (CTSA). It presents the common transport service account framework and associated use cases. The objective of the CTSA role model is to cover relevant transport services, the payment methods, the account types where the user of the service is charged for the service and that requires a more overall role and responsibilities model. The model also defines external stakeholders that impact and border the model, that is, the general financial (banking) system. The framework assumes an account-based system where charges for services are calculated and charged in the account system. The main idea behind the CTSA framework is to provide a transport service user with the benefit of seamless acquisition of access rights to multiple transport services by multiple service / operator managers through a common transport account. This framework assumes a technology-agnostic front end with respect to the payment media and reading equipment. The focus of this framework is the back-office / account management system as a vehicle to integrate multiple transport services and managers. A new set of terms are introduced in this document to distinguish the convergence of a common approach for payment for transportation services from more traditional models using "smart cards" or electronic tickets. The model describes a move towards common or linked mobility accounts for all traveller payment needs, whether for parking, tolls, public transport and other disruptive mode options (e.g., bikeshare, carshare, microtransit, micromobility), inclusive of commercial payment and benefit models.
- Technical report32 pagesEnglish languagesale 15% off
- Draft32 pagesEnglish languagesale 15% off
ISO/TR 20526:2017 provides a state of the art of the components that make up account-based ticketing as currently understood. This state of the art can be used to identify those aspects where international standardization or coordination can lead to benefits. These will then be proposed as normal ISO work items, independent of this document.
- Technical report23 pagesEnglish languagesale 15% off
ISO/TR 19083-1:2016 - defines the framework for the ISO/TR 19083 series of standards related to emergency evacuation and disaster response and recovery, - establishes the criteria under which public transport should support evacuations and disaster response and recovery based on the magnitude of the disaster and the location as these factors drive the policies, directives and plans for each countries disaster prevention/evacuation systems, - identifies the types of agencies and organizations involved in a regionally supported evacuation and disaster, - defines the roles and responsibilities public transport entities should provide in planning, preparing for, and conducting evacuations and disaster response and recovery efforts in support of regional authorities, - recommends the type of information required and necessary actions to be followed by public transport to ensure efficient and effective transportation in response to recovery from a disaster, - provides a concept of operation describing the characteristics of the EEDRR Decision Support System from the viewpoint of an individual who will use the system for public transport disaster support, it is the guiding document for public transport services operators who voluntarily wish to develop EEDRR Decision Support Systems, and - identifies guidelines to improve coordination among regional authorities when public transport disaster support is required.
- Technical report54 pagesEnglish languagesale 15% off
ISO/TR 17185-2:2015 compares and contrasts public transport standards that were developed by different regions and countries. It uses the CEN Transmodel classes as a reference to compare standard data concept descriptions of public transport user information. The purpose of this Technical Report is to understand the concepts described by existing standards and specifications that cover public transport passenger information.
- Technical report143 pagesEnglish languagesale 15% off
ISO/TR 17185-3:2015 is to define high level general requirements of journey planning systems by standardizing use cases. This part of ISO 17185 defines basic requirements for implementing the journey planning system, from the viewpoint that the public transport users should be provided with convenient tool to make his or her journey more efficient ones. In order to realize the desirable journey planning system, public transport information has to be efficiently processed and provided to public transport users in an appropriate way by using currently available regional standards. This part of ISO 17185 does not standardize specific information interfaces such as data format or a stop point numbering system and so on but currently available regional standards established by regional and national groups are suggested to be applied. ISO 17185 is composed of the following parts: - Part 1: Standards framework for public information systems: (International Standard) - Part 2: Data and Interface standards catalogue and cross reference: (Technical Report) - Part 3: Use cases for journey planning systems and their inter-operation: (Technical Report)
- Technical report49 pagesEnglish languagesale 15% off
ISO 17185-1:2014 defines the framework for the realization of efficient public transport user information provision to surface public transport users including international worldwide travellers. In the surface public transport user information provision area, a set of regional and national standards have already been established by related regional and national standardizing bodies. ISO 17185-1:2014 defines basic framework for user information provision for surface public transport users, from the viewpoint that the surface public transport users should be provided with proper static and real-time information when it is most desired and effective. In order to realize the desirable information provision, surface public transport information has to be efficiently gathered, processed, and provided to surface public transport users in an appropriate way by using currently available regional standards. ISO 17185-1:2014 does not aim to define a new part of ISO 17185 that supersede current regional and national standards related to surface public transport. It aims to define the basic framework of surface public transport user information provision by esteeming existing regional standards and wisely using them. ISO 17185-1:2014 does not aim to define specific information interfaces such as data format or a stop point numbering system. The currently available regional standards established by regional and national groups are suggested to be applied in that scope.
- Standard20 pagesEnglish languagesale 15% off
ISO/TR 24014-2:2013 introduces a generic conceptual framework that can be applied to all Interoperable Fare Management Systems (IFMS) compliant with ISO 24014-1, as the basis for business practices relating to the conceptual framework for an IFMS, which is described in ISO 24014-1. This generic conceptual framework comprises three parts: structure of Set of Rules; collaboration of functional models; integration of Set of Rules.
- Technical report25 pagesEnglish languagesale 15% off
- Technical report30 pagesEnglish languagesale 15% off
- Technical report34 pagesFrench languagesale 15% off
ISO/TR 24014-3:2013 describes how to implement Interoperable Fare Management (IFM) applications in a multi-application environment, and the additional roles and use cases that appear.
- Technical report39 pagesEnglish languagesale 15% off
ISO 22951:2009 relates to systems that use priority signal control functions to help emergency vehicles operate. This type of system is composed of a traffic management centre, in‑vehicle units, roadside communication units, and roadside units. Public transport vehicles such as buses are also targeted to receive priority signal control service. The scope of standardization includes message sets and data dictionary related to the communications as follows: between a roadside communication unit and each in-vehicle unit, between a roadside communication unit and other roadside units, between in-vehicle units and roadside units. ISO 22951:2009 concerns only information related to priority signal control and does not deal with information provision such as that of the situations at scenes. Since it is necessary to handle public transport vehicles in accordance with the conditions of individual cities and regions, the section in the messages and the data dictionary that are concerned with priority signal control for the vehicles are treated as an option. Furthermore, the standardization does not depend on the type of communication medium used.
- Standard50 pagesEnglish languagesale 15% off
ISO 24014-1:2015 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. ISO 24014-1:2015 is applicable to bodies in public transport and related services which agree that their systems need to interoperate. While ISO 24014-1:2015 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. ISO 24014-1:2015 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. ISO 24014-1:2015 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; NOTE The 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).
- Standard60 pagesEnglish languagesale 15% off
- Standard61 pagesFrench languagesale 15% off
ISO 24014-1:2007 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. ISO 24014-1:2007 is applicable to bodies in public transport and related services which agree that their systems need to interoperate. While ISO 24014-1:2007 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. ISO 24014-1:2007 covers the definition of a conceptual framework, which is independent of organisational and physical implementation. Any reference within ISO 24014-1:2007 to organisational or physical implementation is purely informative. The objective of ISO 24014-1:2007 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; certification, registration and identification. ISO 24014-1:2007 defines the following main elements: identification of the different functional entities 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 functional entities; security requirements. ISO 24014-1:2007 excludes consideration of 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, which are proposed by other standardisation committees; the financial aspects of fare management systems (e.g. customer payments, method of payment, settlement, apportionment, reconciliation).
- Standard63 pagesEnglish languagesale 15% off
- Standard81 pagesFrench languagesale 15% off