35.240.60 - IT applications in transport
ICS 35.240.60 Details
IT applications in transport
IT-Anwendungen in Verkehr, Handel, Verwaltung
Application des TI dans le transport
Uporabniške rešitve IT v prometu
General Information
Frequently Asked Questions
ICS 35.240.60 is a classification code in the International Classification for Standards (ICS) system. It covers "IT applications in transport". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 1979 standards classified under ICS 35.240.60 (IT applications in transport). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.60 - IT applications in transport
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document specifies the data exchange requirements between related systems within the smart city for electric vehicle (EV)-based demand response (DR) services utilizing nomadic devices as follows: EV-based DR service for demand reduction, called “demand response” during the shortage of reserve on electric grid or in response to a fine dust warning issued according to an air quality forecast; EV-based DR for demand increase, called “reverse demand response”, instead of curtailment during excess electricity generation by renewable energy sources such as the sun and wind. This document defines the requirements of main actors such as the EV, nomadic device, smart city cloud, charging station and service provider to support EV-based DR services. This document also defines the data set and data processing procedure requirements for EV-based DR services.
- Standard26 pagesEnglish languagesale 15% off
This document specifies electronic fee collection (EFC) requirements for the preparation and evaluation of security requirements specifications, referred to as protection profiles (PP) in the ISO/IEC 15408 series and in ISO/IEC TR 15446.
- Draft54 pagesEnglish languagee-Library read for1 day
This document incorporates data structures used by all other data domains of Transmodel. It is composed of the following data packages:
- versions and validity;
- responsibility;
- generic framework;
- reusable components;
- explicit frames referring to generic data.
The data structures represented in this part are either generic patterns that can be explicitly reused in other domains (e.g., a generic model for version frames, a generic grouping mechanism, etc.) or are referenced by different other parts (e.g., service calendar model).
This document itself is composed of the following parts:
- main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
- Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts present in the main document, together with their definitions (normative);
- Annex B, indicating the data model evolutions (informative),
- Annex C, presenting the Transmodel development history (informative),
- Annex D, describing all conventions, methodology and notations for conceptual modelling (informative),
- Annex E, providing a clear overview to help readers understand the core principles, structure, and purpose of Transmodel (informative),
- Annex F, providing information on the Functional domains and Modes of operation (informative).
- Annex G, providing details of the significant technical changes between this document and EN 12896-1:2015 (informative).
- Standard264 pagesEnglish languagee-Library read for1 day
This document covers:
— Provision of a catalogue of fares
— Request for specific fare offers (including specific search criteria),
— Selection of one or several formal offers by the customer (pre-purchase),
— Initiation of the purchase,
— Commitment to buy,
— Reservation of a place on a specific journey,
— Reception of evidence of the purchase,
— Management after purchase (basic after-sale actions),
— All interactions that can be related to a persistent identity.
These functions can be seen as the minimum required for the data flow of reservation from the travellers’ perspective.
Though some of the studied APIs have functions beyond just reservation and involving other parties, the following activities are not in scope of this document nor the CoRoM project:
— Creation and distribution of the travel document,
— Travel planning,
— Payment interfaces with banking information systems,
— Validation of purchased access rights during travel,
— Control of purchased access rights during travel
- Technical report159 pagesEnglish languagee-Library read for1 day
This document is composed of the following data packages:
— Driver;
— Driver Schedule;
— Rostering;
— Personnel Disposition;
— Driver Control Action.
This document itself is composed of the following parts:
— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
— Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts presented in the main document together with their definitions (normative);
— Annex B presenting the model evolution (informative).
— Annex C, providing details of the significant technical changes between this document and EN 12896-7:2019 (informative)
- Standard53 pagesEnglish languagee-Library read for1 day
This document entitled “Public transport – Reference data model – Part 5: Fare Management” is composed of the following data packages:
⎯ Fare Structure;
⎯ Access Right Assignment;
⎯ Fare Pricing;
⎯ Sales Description;
⎯ Sales Transaction;
⎯ Fare Roles;
⎯ Validation and Control;
⎯ Explicit Frames for Fares.
This document itself is composed of the following parts:
⎯ Main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
⎯ Annex A, containing the data dictionary and attribute tables, i.e., the list of all the concepts presented in the main document together with the definitions (normative);
⎯ Annex B, presenting the model evolution (informative).
⎯ Annex C, providing details of the significant technical changes between this document and EN 12896-5:2019 (informative)
- Standard292 pagesEnglish languagee-Library read for1 day
This document specifies data model structures that are applicable for traffic management applications in the urban environment. This document addresses data concepts to support the exchange of traffic management plans, rerouting and extensions of the existing DATEX II core model to better support application to the urban environment.
- Technical specification104 pagesEnglish languagee-Library read for1 day
This document incorporates the following main data packages:
- Network Description;
- Fixed Object;
- Tactical Planning Components;
- Explicit Frame.
It is composed of the following parts:
- main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
- Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
- Annex B presenting the model evolution (informative).
- Annex C, providing details of the significant technical changes between this document and EN 12896-2:2016 (informative).
- Standard187 pagesEnglish languagee-Library read for1 day
This document incorporates the following main data packages:
- Dated Production Components;
- Call;
- Dated Call;
- Production Plan;
- Detecting & Monitoring;
- Situation;
- Messaging;
- Control Action;
- Operational Event & Incident;
- Facility Monitoring & Availability;
- Occupancy.
It is composed of the following parts:
- main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
- Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
- Annex B presenting the model evolution (informative);
- Annex C detailing the mapping to DATEX-II and SIRI (informative).
- Annex D, providing details of the significant technical changes between this document and EN 12896 4:2019 (informative).
- Standard89 pagesEnglish languagee-Library read for1 day
- Amendment7 pagesEnglish languagee-Library read for1 day
The document incorporates the following main data packages:
- Trip Description;
- Passenger Information Queries.
It is composed of the following parts:
- main document representing the data model for the concepts shared by the different fare domains covered by Transmodel (normative);
- Annex A, containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with the definitions (normative);
- Annex B presenting the model evolution (informative).
- Annex C, providing details of the significant technical changes between this document and EN 12896 6:2019 (informative).
- Standard130 pagesEnglish languagee-Library read for1 day
The present document is composed of the following data packages:
— journey and Interchange;
— vehicle Journey Assignment;
— journey Times;
— block and Vehicle Service;
— dated Journey;
— explicit Frame.
This document itself is composed of the following parts:
— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
— Annex B presenting the model evolution (informative);
— Annex C, providing details of the significant technical changes between this document and EN 12896-1:2015 (informative)
- Standard90 pagesEnglish languagee-Library read for1 day
This document specifies electronic fee collection (EFC) requirements for the preparation and evaluation of security requirements specifications, referred to as protection profiles (PP) in the ISO/IEC 15408 series and in ISO/IEC TR 15446.
- Standard47 pagesEnglish languagesale 15% off
- Standard52 pagesFrench languagesale 15% off
The scope of this document is the definition of the functional interface between the TDC and other train systems. These "Other Train Systems" are the train systems interfacing with the TDC excluding the displays (CLC/TR 50542-2), ETCS/STM onboard (Subset-121) and already designed class B ATP systems.
The functional interface deals with data exchanged between the TDC and these train systems as shown in Figure 1.
The TDC is defined in document CLC/TR 50542-1.
(...)
- Technical report11 pagesEnglish languagee-Library read for1 day
- Standard93 pagesEnglish languagesale 15% off
This document is applicable to safety-related electronic systems using for digital communication purposes a transmission system which was not necessarily designed for safety-related applications. For transmission systems where the risk of unauthorized access is not negligible, the document defines the interface to the applicable cybersecurity standards.
Both safety-related equipment and non-safety-related equipment can be connected to the transmission system.
This document gives the specific requirements needed to achieve safety-related communication between safety-related equipment connected to the transmission system, while the general system requirements including allocation of safety requirements and content of the safety case are defined in EN 50129.
This document is not applicable to existing systems which had already been accepted prior to the release of this document. However, so far as reasonably practicable, it is applicable to modifications and extensions to existing systems, subsystems and equipment.
This document does not specify:
- the transmission system;
- equipment connected to the transmission system;
- solutions (e.g. for interoperability);
- which kind of data are safety-related and which are not.
A safety-related equipment connected through an open transmission system can be subjected to many different cybersecurity threats, against which an overall program is defined encompassing management, technical and operational aspects.
- Standard64 pagesEnglish languagee-Library read for1 day
This document is applicable to safety-related electronic systems (including subsystems and equipment) for railway signalling applications.
This document applies to generic systems (i.e. generic products or systems defining a class of applications), as well as to systems for specific applications.
The scope of this document and its relationship with other CENELEC standards are shown in Figure 1.
This document is applicable only to the functional safety of systems. It does not deal with other aspects of safety such as occupational health and safety of personnel or potential threats created by the technology regardless of their intended functions (e.g. presence of sharp edges, presence of electric voltage, presence of combustible material). Cybersecurity aspects of functional safety are addressed only to the extent consistent with the application of the relevant standards, where needed.
This document applies to all the phases of the life cycle of a safety-related electronic system, focusing in particular on phases from 4 (specification of system requirements) to 10 (system acceptance) as defined in EN 50126 1:2017.
Requirements for systems which are not related to safety are outside the scope of this document.
This document is not necessarily applicable to systems, subsystems or equipment which had already been accepted prior to the date of withdrawal (dow) of the standards conflicting with this document. However, so far as reasonably practicable, it is applicable to modifications and extensions to such systems, subsystems and equipment.
NOTE In the case of partial modifications, it can happen that the system can no longer be declared compliant with a single version of the standard, meaning that the modified part will be compliant with the current version and the unmodified parts will be compliant with the previous version.
This document is primarily applicable to systems, subsystems or equipment which have been specifically designed and manufactured for railway signalling applications. It is also applicable, to the extent of 6.2, to general-purpose or industrial equipment (e.g. power supplies, display screens, or other commercial off the shelf items) which is procured for use as part of a safety-related electronic system.
This document is aimed at railway duty holders, railway suppliers, and assessors as well as at safety authorities, although it does not define an approval process to be applied by the safety authorities.
- Standard140 pagesEnglish languagee-Library read for1 day
This document specifies requirements for an application interface between dedicated short-range communication on-board equipment (DSRC-OBE) and external in-vehicle devices to make DSRC-OBE applicable for diversified electronic fee collection (EFC) systems. This document applies to: — definitions of the application interface between DSRC-OBE and external in-vehicle devices; — definitions of data groups and data elements.
- Standard22 pagesEnglish languagesale 15% off
This document contains test results on RLAN interference to CEN DSRC devices, including the setup and execution of the tests, along with the main findings
- Draft37 pagesEnglish languagee-Library read for1 day
The scope of the proposed work item will be:
- The context of the work done within CoRoM,
- The data information flow and steps required for purchasing any multimodal travel (including basic after sale), from the perspective of travellers,
- How to use Transmodel (EN 12896) to represent them (only Transmodel based concepts and data structure should be taken into account),
- A study of a range of existing APIs and their functionalities, which include OSDM, TOMP-API, BoB, Entur API, FerryGateway, (EU) 454/2011 (TAP TSI) etc.
- The implication of such study for Transmodel (EN 12896)
- The implication of such study on the purchase APIs taking into account the Transmodel approach.
The last part of this proposed work item will inform the revision of Transmodel Parts 5 and 6 (EN 12896-5 and EN 12896-6) and NeTEx Part 3 (TS 16614-3).
This TR covers the following functional scope:
- Provision of a catalogue / fares consultation
- Request for specific fare offers (including criteria)
- Selection of a formal offer by the customer (pre-purchase)
- Initiate the purchase
o commitment to buy
o reservation
o evidence of the purchase
- Manage after purchase (basic after-sale actions)
- All interactions can be related to persistent identity
The following items are not in scope:
- creation and distribution of the travel document
- travel planning
- payment as interface with bank SI
- access right validation
- access right control
- Technical report159 pagesEnglish languagee-Library read for1 day
This document defines an ontology for service level concepts defined for the transport domain using terms specified in ISO/IEC 5087-1 and ISO/IEC 5087-2. The values for service-level concepts defined in this document are intended to be managed by the transport domain but accessible by multiple city services and stakeholders.
- Technical specification48 pagesEnglish languagesale 15% off
- Amendment7 pagesEnglish languagee-Library read for1 day
This document provides a collection of use cases specific to the domain of intelligent transport systems that take advantage of big data technologies and artificial intelligence (AI) techniques.
- Technical report65 pagesEnglish languagesale 15% off
- Standard1 pageEnglish languagesale 15% off
- Standard1 pageFrench languagesale 15% off
This document is applicable to safety-related electronic systems using for digital communication purposes a transmission system which was not necessarily designed for safety-related applications. For transmission systems where the risk of unauthorized access is not negligible, the document defines the interface to the applicable cybersecurity standards. Both safety-related equipment and non-safety-related equipment can be connected to the transmission system. This document gives the specific requirements needed to achieve safety-related communication between safety-related equipment connected to the transmission system, while the general system requirements including allocation of safety requirements and content of the safety case are defined in EN 50129. This document is not applicable to existing systems which had already been accepted prior to the release of this document. However, so far as reasonably practicable, it is applicable to modifications and extensions to existing systems, subsystems and equipment. This document does not specify: - the transmission system; - equipment connected to the transmission system; - solutions (e.g. for interoperability); - which kind of data are safety-related and which are not. A safety-related equipment connected through an open transmission system can be subjected to many different cybersecurity threats, against which an overall program is defined encompassing management, technical and operational aspects.
- Standard64 pagesEnglish languagee-Library read for1 day
This document specifies data model structures that are applicable for traffic management applications in the urban environment. This document addresses data concepts to support the exchange of traffic management plans, rerouting and extensions of the existing DATEX II core model to better support application to the urban environment.
- Technical specification104 pagesEnglish languagee-Library read for1 day
This document incorporates the following main data packages:
- Dated Production Components;
- Call;
- Dated Call;
- Production Plan;
- Detecting & Monitoring;
- Situation;
- Messaging;
- Control Action;
- Operational Event & Incident;
- Facility Monitoring & Availability;
- Occupancy.
It is composed of the following parts:
- main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
- Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
- Annex B presenting the model evolution (informative);
- Annex C detailing the mapping to DATEX-II and SIRI (informative).
- Annex D, providing details of the significant technical changes between this document and EN 12896 4:2019 (informative).
- Standard89 pagesEnglish languagee-Library read for1 day
The document incorporates the following main data packages:
- Trip Description;
- Passenger Information Queries.
It is composed of the following parts:
- main document representing the data model for the concepts shared by the different fare domains covered by Transmodel (normative);
- Annex A, containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with the definitions (normative);
- Annex B presenting the model evolution (informative).
- Annex C, providing details of the significant technical changes between this document and EN 12896 6:2019 (informative).
- Standard130 pagesEnglish languagee-Library read for1 day
1.1 General Scope of the Standard
The main objective of the present standard is to present the Reference Data Model for Public Transport, based on:
- the Reference Data Model, EN12896, known as Transmodel V5.1,
- CEN EN 28701, known as IFOPT,
incorporating the requirements of
- EN 15531-1 to -3 and TS 15531-4 and -5: Service interface for real-time information relating to public transport operations (SIRI),
- TS 16614-1 and 2: Network and Timetable Exchange (NeTEx), in particular, the specific needs for long distance train operation.
A particular attention is drawn to the data model structure and methodology:
- the data model is described in a modular form in order to facilitate the understanding and the use of the model,
- the data model is entirely described in UML.
In particular, a Reference Data Model kernel is described, referring to the data domain:
- Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.
This part corresponds to the Transmodel V5.1 Network Description extended by the IFOPT relevant parts.
Furthermore, the following functional domains are considered:
- Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules)
- Passenger Information (planned and real-time)
- Fare Management (fare structure, sales, validation, control)
- Operations Monitoring and Control: operating day-related data, vehicle follow-up , control actions
- Management Information and Statistics (including data dedicated to service performance indicators).
- Driver Management:
- Driver Scheduling (day-type related driver schedules),
- Rostering (ordering of driver duties into sequences according to some chosen methods),
- Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance).
The data modules dedicated to cover most functions of the above domains will be specified.
Several concepts are shared by the different functional domains. This data domain is called “Common Concepts”.
1.2 Functional Domain Description
The different functional domains taken into account in the present standard and of which the data have been represented as the reference data model are described in “Public Transport Reference Data Model - Part 1: Common Concepts”.
They are:
- Public Transport Network and Stop Description
- Timing Information and Vehicle scheduling
- Passenger information
- Fare Management
- Operations monitoring and control
- Management information
- Personnel Management: Driver Scheduling, Rostering, Personnel Disposition.
The aspects of multi-modal operation and multiple operators’ environment are also taken into account.
1.3 Particular Scope of this Document
The present European Standard entitled “Reference Data Model for Public Transport – Part 3: Timing Information and Vehicle Scheduling”. incorporates
- Journey and Journey Times Model: describes the time-related information at the level of vehicle journeys, i.e. planned timing for the vehicles at day-type level.
- Dated Journey Model: describes the link of the timing information for a single operating day and the day type related timing,
- Passing Times Model: describes all the different types of passing times for the day type related information,
- Vehicle Service Model: describes the information related the work of vehicles as planned for days types. It constitutes the main part of the Vehicle Scheduling Data Domain.
- Vehicle Journey Assignment Model: describes operational assignments (advertised vehicle labels, stopping positions) related to particular vehicle journeys.
This document itself is composed of the following parts:
- Main document (normative) representing the data model,
(...)
- Standard90 pagesEnglish languagee-Library read for1 day
1.1 General Scope of the Standard
The main objective of the present standard is to present the Reference Data Model for Public Transport, based on:
- the Reference Data Model, EN 12896, known as Transmodel V5.1;
- EN 28701:2012, Intelligent transport systems - Public transport - Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this European Standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication;
incorporating the requirements of:
- EN 15531-1 to -3 and CEN/TS 15531-4 and -5: Public transport - Service interface for real-time information relating to public transport operations (SIRI);
- CEN/TS 16614-1 and -2: Public transport - Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation.
Particular attention is drawn to the data model structure and methodology:
- the data model is described in a modular form in order to facilitate the understanding and the use of the model;
- the data model is entirely described in UML.
The following functional domains are considered:
- Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places;
- Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules);
- Passenger Information (planned and real-time);
- Fare Management (fare structure, sales, validation, control);
- Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions;
- Driver Management:
- Driver Scheduling (day-type related driver schedules),
- Rostering (ordering of driver duties into sequences according to some chosen methods),
- Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance);
- Management Information and Statistics (including data dedicated to service performance indicators).
The data modules dedicated to cover most functions of the above domains will be specified.
Several concepts are shared by the different functional domains. This data domain is called "Common Concepts".
1.2 Functional Domain Description
The different functional domains (enumerated above) taken into account in the present document, and of which the data have been represented as the reference model, are described in EN 12896-1, Public transport - Reference data model - Part 1: Common concepts.
1.3 Particular Scope of this Document
The present document entitled Public transport - Reference data model - Part 7: Driver management incorporates the following data packages:
- Driver Scheduling;
Rostering;
- Personnel Disposition;
- Driver Control Actions.
This document itself is composed of the following parts:
- Main document (normative) presenting the data model for the concepts shared by the different domains covered by Transmodel,
- Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions,
- Annex B (normative), providing a complement to EN 12896-1:2016, particularly useful for Parts 4 to 8 of the Public Transport Reference Data Model; and
- Annex C (informative), indicating the data model evolutions.
- Standard53 pagesEnglish languagee-Library read for1 day
This document incorporates the following main data packages:
- Network Description;
- Fixed Object;
- Tactical Planning Components;
- Explicit Frame.
It is composed of the following parts:
- main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
- Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
- Annex B presenting the model evolution (informative).
- Annex C, providing details of the significant technical changes between this document and EN 12896-2:2016 (informative).
- Standard187 pagesEnglish languagee-Library read for1 day
This document entitled “Public transport – Reference data model – Part 5: Fare Management” is composed of the following data packages:
⎯ Fare Structure;
⎯ Access Right Assignment;
⎯ Fare Pricing;
⎯ Sales Description;
⎯ Sales Transaction;
⎯ Fare Roles;
⎯ Validation and Control;
⎯ Explicit Frames for Fares.
This document itself is composed of the following parts:
⎯ Main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
⎯ Annex A, containing the data dictionary and attribute tables, i.e., the list of all the concepts presented in the main document together with the definitions (normative);
⎯ Annex B, presenting the model evolution (informative).
⎯ Annex C, providing details of the significant technical changes between this document and EN 12896-5:2019 (informative)
- Standard292 pagesEnglish languagee-Library read for1 day
This document incorporates data structures used by all other data domains of Transmodel. It is composed of the following data packages:
- versions and validity;
- responsibility;
- generic framework;
- reusable components;
- explicit frames referring to generic data.
The data structures represented in this part are either generic patterns that can be explicitly reused in other domains (e.g., a generic model for version frames, a generic grouping mechanism, etc.) or are referenced by different other parts (e.g., service calendar model).
This document itself is composed of the following parts:
- main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
- Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts present in the main document, together with their definitions (normative);
- Annex B, indicating the data model evolutions (informative),
- Annex C, presenting the Transmodel development history (informative),
- Annex D, describing all conventions, methodology and notations for conceptual modelling (informative),
- Annex E, providing a clear overview to help readers understand the core principles, structure, and purpose of Transmodel (informative),
- Annex F, providing information on the Functional domains and Modes of operation (informative).
- Annex G, providing details of the significant technical changes between this document and EN 12896-1:2015 (informative).
- Standard264 pagesEnglish languagee-Library read for1 day
This document provides good practice that can be adopted by any service provider, not limited to e-hailing and p-hailing operators, for the implementation of work-related road traffic safety (RTS) management. This document is applicable to any service provider to offer further protection to the drivers for digital platform providers as well as other road users through the adoption of a proactive approach to manage work-related road risks.
- Standard22 pagesEnglish languagesale 15% off
This document specifies guidelines and requirements for the creation and use of intelligent transport system (ITS) station facilities layer service "message sets" (ITS-MsgSets). This includes specification of the basic structure of ITS-MsgSets, the creation of a message as a concatenation of messages from ITS-MsgSets, and the reception of respective messages.
- Technical specification15 pagesEnglish languagesale 15% off
The scope of this document is the definition of the functional interface between the TDC and other train systems. These "Other Train Systems" are the train systems interfacing with the TDC excluding the displays (CLC/TR 50542-2), ETCS/STM onboard (Subset-121) and already designed class B ATP systems. The functional interface deals with data exchanged between the TDC and these train systems as shown in Figure 1. The TDC is defined in document CLC/TR 50542-1. (...)
- Technical report11 pagesEnglish languagee-Library read for1 day
IEC 61375-1:2026 applies to the architecture of data communication systems in open trains, i.e. it covers the architecture of a communication system for the data communication between vehicles of the said open trains, the data communication within the vehicles and the data communication from train to the ground. The applicability of IEC 61375-1 to the train network technologies allows for interoperability of individual vehicles within open trains in international traffic. The data communication systems inside vehicles are given as recommended solutions to cope with the said TCN. In any case, proof of compatibility between a proposed train backbone and a proposed consist network will have to be brought by the supplier. IEC 61375-1 might be additionally applicable to closed trains and multiple unit trains when so agreed between purchaser and supplier. This fourth edition cancels and replaces the third edition published in 2012. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Extension of train backbone topologies: aggregated and segregated topology;
b) Added independent consist orientation check with segregated train backbone topology;
c) Introduction of wireless technologies: wireless train backbone and wireless consist network;
d) Possibility of virtual networks;
e) Definition of data classes and protocol requirements suitable for the OMTS domain;
f) New clause about cybersecurity in train communication networks.
- Standard66 pagesEnglish languagee-Library read for1 day
This document presents Part 2 of the European Technical Specification known as “NeTEx”. NeTEx provides a framework for specifying communications and data exchange protocols for organisations wishing to exchange scheduled Information relating to public transport operations. As defined by Transmodel, 'Public transport' has to be understood as services advertised and available for use by the general public carried out by any means of transport.
This Technical Specification is made up of six parts defining a single European Standard, which provides a complete exchange format for public transport networks, timetable description and fare information.
Part 1 is the description of the public transport network topology exchange format. It also contains use case shared with part 2, and modelling rules and the description of a framework shared by all parts.
Part 2 is the description of the scheduled timetables exchange format.
Part 3 is the description of the fare information exchange format.
Part 4 is the description of the European passenger information profile.
Part 5 is the description of the alternative modes exchange format.
Part 6 is the description of the European passenger information accessibility profile.
Part 1 is fully standalone, and parts 2, 3, 4, 5 and 6 rely on Part 1 and possibly any previous part..
The XML schema can be downloaded from http://netex-cen.eu (or directly from https://github.com/NeTEx-CEN/NeTEx), along with available guidance on its use, example XML files, and case studies of national and local deployments.
This document is highly technical, and a special care has been taken to keep the text readable. In particular a set of formatting conventions is followed that enhances the usual CEN writing rules in order to distinguish references to elements of the formal models within text:
Transmodel terms and NeTEx conceptual model elements are in capital letters (JOURNEY PATTERN for example).
NeTEx physical model names are in bold italic font and use CamelCase style with no spaces (JourneyPattern, for example).
NeTEx physical model attribute types are in italic font and use CamelCase style with no spaces (TypeOfEntity, for example).
- Technical specification326 pagesEnglish languagee-Library read for1 day
This document is a profile of CEN/TS 16614 series. It focuses on information relevant to feed passenger information services and excludes operational and fares information.
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V6 (EN 12986) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems.
As for most data exchange standards, defining subsets of data and dedicated rules for some specific use case is of great help for implementers and for the overall interoperability. This subset is usually called profile and this profile targets passenger information as only use case.
- Technical specification272 pagesEnglish languagee-Library read for1 day
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V6.2 (EN 12896 series) and SIRI (CEN/TS 15531-4/-5 and EN 15531-1/-2/-3) and supports the exchange of information of relevance for passenger information about public transport services and also for running Automated Vehicle Monitoring Systems (AVMS).
NOTE Many NeTEx concepts are taken directly from Transmodel. The definitions and explanation of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptions in order to fit the NeTEx context.
Although the data exchanges targeted by NeTEx are predominantly oriented towards provisioning passenger information systems and AVMS with data from public transport scheduling systems, it is not restricted to this purpose. NeTEx can also provide an effective solution to many other use cases for transport data exchange.
- Technical specification1257 pagesEnglish languagee-Library read for1 day
This document establishes a framework and specifies electronic fee collection (EFC) functions for the personalization process of on-board equipment (OBE) used for EFC.
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
This document is applicable to the EFC interface, e.g. using dedicated short-range communication or integrated circuit(s) card, between the personalization equipment (PE) and OBE as shown in Figure 1.
This document does not cover the following:
whether the personalization functionality resides completely in the PE or whether this functionality instead resides in a central system, where the PE is more or less “transparent”;
the exact application command or message structures for the EFC personalization functionality (these are dependent on the communication media and are described in subsequent parts of the ISO 21719 series);
the test procedures for evaluation of an implementation for conformity to the requirements in this document;
setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party).
NOTE Some of the issues listed above are subject to separate documents prepared by ISO/TC 204, CEN/TC 278 and the European Telecommunications Standards Institute – Electromagnetic compatibility and Radio Spectrum Matters (ETSI ERM).
- Standard16 pagesEnglish languagee-Library read for1 day
This document specifies common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the “fundamentals and concepts” of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models.
Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features.
The EN 9300-1XX series is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX series.
As technology matures, additional parts will be released in order to support new requirements within the aerospace community.
1.2 In Scope
This document specifies:
- the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information;
- the document structure of the EN 9300-1XX series, and the links between all these parts;
- the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of archive information packages for CAD data.
1.3 Out of scope
The following are out of scope for this part:
- long-term archiving of CAD 2D drawings;
- other CAD specialization disciplines, such as electrical harnesses, composite.
- Standard53 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Technical specification732 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Technical specification518 pagesEnglish languagee-Library read for1 day
This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However, as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12), ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document.
This document specifies the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE, NR and their successors) as:
1) In-Vehicle System (IVS)/vehicle,
2) Mobile Network Operator (MNO),
3) Public Safety Answering Point (PSAP),
and to provide conformance tests for actor groups 1) – 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service.
NOTE 2 Third party eCall systems (TPS-eCall) are not within the scope of this deliverable. This is because the core TPS-eCall standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider.
NOTE 3 These conformance tests are based on the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and
revise Conformance Test Procedures (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 112-eCall (Pan European eCall) tests provided in EN 16454 are
specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable.
This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO’s, and PSAPs, required to ensure and demonstrate compliance to EN 17184.
The scope covers conformance testing of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
- Standard188 pagesEnglish languagee-Library read for1 day
In respect of pan European eCall (operating requirements defined in EN 16072), this document defines
the high level application protocols, procedures and processes required to provide the eCall service via
a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and
wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a
PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is
initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched
networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks
(PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12)
ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the
appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks
are available) are out of scope of this document.
NOTE 1 The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to
automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003 or IMS packet switched network) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2 HLAP requirements for third party services supporting eCall can be found in EN 16102.
This document makes reference to those provisions but does not duplicate them.
- Standard38 pagesEnglish languagee-Library read for1 day
This document specifies common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the “fundamentals and concepts” of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models.
Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features.
The EN 9300-1XX series is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX series.
As technology matures, additional parts will be released in order to support new requirements within the aerospace community.
1.2 In Scope
This document specifies:
- the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information;
- the document structure of the EN 9300-1XX series, and the links between all these parts;
- the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of archive information packages for CAD data.
1.3 Out of scope
The following are out of scope for this part:
- long-term archiving of CAD 2D drawings;
- other CAD specialization disciplines, such as electrical harnesses, composite.
- Standard53 pagesEnglish languagee-Library read for1 day
Motorway chauffeur systems (MCS) perform Level 3 automated driving on limited access motorways with the presence of a fallback-ready user (FRU). This document describes a framework of MCS including system characteristics, system states and transition conditions and system functions. This document specifies requirements for the basic set of functionalities of a MCS, and test procedures to verify these requirements. The requirements include vehicle operation to perform the entire dynamic driving task (DDT) within the current lane of travel, to issue a request to intervene (RTI) before disengaging, and to extend operation and temporarily continue to perform the DDT after issuing an RTI. Requirements and test procedures for additional functionalities (such as lane changing) are provided in other parts of the ISO 23792 series. Means related to setting a destination and selecting a route to reach the destination are not within the scope of this document. This document applies to MCS installed in light vehicles[9].
- Standard38 pagesEnglish languagesale 15% off
This document specifies the requirements for discretionary lane change (DLC) for motorway chauffeur systems (MCS) that perform Level 3 automated driving on limited access motorways. It also specifies the test procedures to verify the requirements. DLC is an additional functionality that can be added to an MCS conforming to the general requirements specified in ISO/TS 23792-1. Means related to setting a destination and selecting a route to reach the destination are not in the scope of this document. This document applies to the system installed in light vehicles.
- Standard21 pagesEnglish languagesale 15% off
This document establishes a framework and specifies electronic fee collection (EFC) functions for the personalization process of on-board equipment (OBE) used for EFC.
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
This document is applicable to the EFC interface, e.g. using dedicated short-range communication or integrated circuit(s) card, between the personalization equipment (PE) and OBE as shown in Figure 1.
This document does not cover the following:
whether the personalization functionality resides completely in the PE or whether this functionality instead resides in a central system, where the PE is more or less “transparent”;
the exact application command or message structures for the EFC personalization functionality (these are dependent on the communication media and are described in subsequent parts of the ISO 21719 series);
the test procedures for evaluation of an implementation for conformity to the requirements in this document;
setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party).
NOTE Some of the issues listed above are subject to separate documents prepared by ISO/TC 204, CEN/TC 278 and the European Telecommunications Standards Institute – Electromagnetic compatibility and Radio Spectrum Matters (ETSI ERM).
- Standard16 pagesEnglish languagee-Library read for1 day