2010/40/EU - Directive 2010/40/EU of the European Parliament and of the Council of 7 July 2010 on the framework for the deployment of Intelligent Transport Systems in the field of road transport and for interfaces with other modes of transport Text with EEA relevance

This document specifies a global transport data management (GTDM) framework composed of
— global transport basic data model,
— global transport access control data model,
— global transport function monitor data model, and
— sensor and control network data model
to support data exchange between applications.
This document defines standardized data classes in a Global Transport Data Format (GTDF), and the
means to manage them.
Application and role-based access control to resources in GTDF are specified in accordance with
IEEE 1609.2 certificates.
This document specifies GTDM as an ITS-S capability which is an optional feature (ITS-capabilities are
specified in ISO 24102-6).
The GT access control (GTAC) data model specifies access permissions to data and function control by
defining role-based mechanisms.
The GT function monitor (GTFM) data model specifies a configuration method to generate a flow logic
for monitoring purposes, e.g. observing data parameters with respect of a defined limit.

This European Standard (EN 16157 series) specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
This European Standard is applicable to:
-   Traffic and travel information which is of relevance to road networks (non-urban and urban),
-   Public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service),
-   Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This European Standard establishes specifications for data exchange between any two instances of the following actors:
-   Traffic Information Centres (TICs),
-   Traffic Control Centres (TCCs),
-   Service Providers (SPs),
Use of this European Standard may be applicable for use by other actors.
This European Standard series covers, at least, the following types of informational content:
-   Road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment,
-   Operator initiated actions,
-   Road traffic measurement data, status data, and travel time data,
-   Travel information relevant to road users, including weather and environmental information,
-   Road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies the informational structures, relationships, roles, attributes and associated data types required for publishing variable message sign information within the Datex II framework. This is specified in two publications, a DATEX II VMS Table Publication sub-model and a VMS Publication sub-model, which are part of the DATEX II platform independent model, but this part excludes those elements that relate to:
-   location information which are specified in EN 16157-2,
-   common information elements, which are specified in EN 16157-7,
-   situation information which are specified in EN 16157-3.
The VMS Table Publication supports the occasional exchange of tables containing generally static reference information about deployed VMS which enable subsequent efficient references to be made to pre-defined static information relating to those VMS. The VMS Publication supports the exchange of the graphic and textual content of one or several VMS plus any status information on device configuration that aid the comprehension of the informational content. This content is potentially subject to rapid change.
These publications are not intended to support the control or configuration of VMS equipment. Each is part of the DATEX II platform independent model.

This document specifies a methodology to define ITS-S communication profiles (ITS-SCPs) based on standardized communication protocols to interconnect trusted devices. These profiles enable secure information exchange between such trusted devices, including secure low-latency information exchange, in different configurations. The present document also normatively specifies some ITS-SCPs based on the methodology, yet without the intent of covering all possible cases, in order to exemplify the methodology.
Configurations of trusted devices for which this document defines ITS-SCPs include:
a) ITS station communication units (ITS-SCU) of the same ITS station unit (ITS-SU), i.e. station-internal communications;
b) an ITS-SU and an external entity such as a sensor and control network (SCN), or a service in the Internet;
c) ITS-SUs.
Other ITS-SCPs can be specified at a later stage.
The specifications given in this document can also be applied to unsecured communications and can be applied to groupcast communications as well.

This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluating the
conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and
RSE to support interoperability between different equipment supplied by different manufacturers.
ISO 12813 defines requirements on the compliance check communication (CCC) interface level, but
not for the RSE or OBE internal functional behaviour. Consequently, tests regarding OBE and/or RSE
functional behaviour remain outside the scope of this document.

This document specifies the in-vehicle information (IVI) data structures that are required by different
intelligent transport system (ITS) services for exchanging information between ITS Stations (ITS-S).
A general, extensible data structure is specified, which is split into structures called containers to
accommodate current-day information. Transmitted information includes IVI such as contextual
speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, locationbased
services, re-routing. The information in the containers is organized in sub-structures called data
frames and data elements, which are described in terms of its content and its syntax.
The data structures are specified as communications agnostic. This document does not provide the
communication protocols. This document provides scenarios for usage of the data structure, e.g. in case
of real time, short-range communications.

This document specifies a generic position, velocity and time (PVT) service. It further specifies
the PVT service within the ITS station (ITS-S) facilities layer (ISO 21217) and its interface to other
functionalities in an ITS-S such as:
— ITS-S application processes (ITS-S-APs), defined in ISO 21217;
— the generic facilities service handler (FSH) functionality of the ITS station facilities layer, defined in
ISO/TS 17429.
This document specifies:
— a PVT service which, dependent on a specific implementation, uses a variety of positioning-related
sources such as global navigation satellite systems (GNSSs, e.g. GALILEO, GLONASS and GPS),
roadside infrastructure, cellular infrastructure, kinematic state sensors, vision sensors;
— a PVT service which merges data from the above-mentioned positioning-related sources and
provides the PVT output parameters (carrying the PVT information) including the associated
quality (e.g. accuracy);
— how the PVT service is integrated as an ITS-S capability of the ITS station facilities layer;
— the interface function calls and responses (Service Access Point – service primitives) between the
PVT ITS-S capability and other functionalities of the ITS station architecture;
— optionally, the PVT service as a capability of the ITS-S facilities layer; see ISO 24102-6;
— an ASN.1 module C-itsPvt, providing ASN.1 type and value definitions (in Annex A);
— an implementation conformance statement proforma (in Annex B), as a basis for assessment of
conformity to this document.
NOTE It is outside the scope of this document to define the associated conformance evaluation test
procedures.

This document defines an information security framework for all organizational and technical entities
of an EFC scheme and for the related interfaces, based on the system architecture defined in ISO 17573-1.
The security framework describes a set of security requirements and associated security measures.
Annex D contains a list of potential threats to EFC systems and a possible relation to the defined
security requirements. These threats can be used for a threat analysis to identify the relevant security
requirements for an EFC system.
The relevant security measures to secure EFC systems can then be derived from the identified security
requirements.

This document specifies the standard data concepts that comprise the "Minimum Set of Data" (MSD) to be transferred from a vehicle to a 'Public Safety Answering Point' (PSAP) in the event of a crash or emergency via an 'eCall' communication transaction.
Optional additional data concepts may also be transferred.
The communications media protocols and methods for the transmission of the eCall message are not specified in this document.

This project specifies the fifth part of the DATEX II European Standard which deals with the one or more publication sub-model(s) within the DATEX II model that support the exchange of measured and elaborated information.
These publications are intended to support the exchange of informational content from the organisation having the measures and creating elaborated data to other organisations providing ITS services or onward information exchange. It also includes the exchange of static information about measurement sites.
This is specified in three submodels, a DATEX II Measurement Site Table Publication submodel, a DATEX II Measured Data Publication submodel and a DATEX II Elaborated Data Publication submodel.

This document specifies the fast service announcement protocol (FSAP) for general purposes in ITS.
It references and supports all features of ISO/TS 16460, especially supporting the service response
message (SRM) and related features in addition to the service announcement message (SAM), which
enables only very basic features.
FSAP supports locally advertised ITS services uniquely identified by an ITS application identifier
(ITS-AID).
This document specifies message formats and related basic protocol procedures by reference to
ISO/TS 16460, and further related protocol requirements for operation of FSAP in the context of an ITS
station specified in ISO 21217.
This document illustrates its relations to service announcement protocols specified by ETSI TC ITS
and IEEE.

This document constitutes a part of the CEN 16157 DATEX II series of standards and technical specifications. This series specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel. The component facets include the framework and context for exchanges, the modelling approach, the data content, the data structure and relationships and the communications specification.
Part 9, this document, specifies additional data model structures that are applicable for traffic signal management applications in the urban environment. This part specifies data concepts to support the exchange of traffic signal status messaging, intersection geometry definition and attribution in a consistent way with existing C-ITS standards and technical specifications.
It establishes specifications for data exchange between any two instances of the following actors:
- Traffic Information Centres (TICs),
- Traffic Control Centres (TCCs),
- Service Providers (SPs).
Use of this document may be applicable for use by other actors.

1.1   General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V6 (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 transit scheduling systems, it is not restricted to this purpose and NeTEx can also provide an effective solution to many other use cases for transport data exchange.
1.2   Transport modes
All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports and air journeys, but there has not been any specific consideration of any additional requirements that apply specifically to air transport.
1.3   Compatibility with existing standards and recommendations
Concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and related organizations; stations and related equipment; journey coupling and journey parts; train composition and facilities; planned passing times; timetable versions and validity conditions.
In the case of long distance train the NeTEx takes into account the requirements formulated by the ERA (European Rail Agency) - TAP/TSI (Telematics Applications for Passenger/ Technical Specification for Interoperability, entered into force on 13 May 2011 as the Commission Regulation (EU) No 454/2011), based on UIC directives.
As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (The Netherlands) and NOPTIS (Nordic Public Transport Interface Standard).
The data exchange is possible either through dedicated web services, through data file exchanges, or using the SIRI exchange protocol as described in part 2 of the SIRI documentation.

a) A TM interface standard to enable exchange network performance data (e.g. traffic conditions, travel times) and planned and unplanned events/incidents (e.g. roadworks, road/bridge/tunnel closures, bad weather, road surface conditions) which are not currently covered by DATEX II.
b) A TM interface standard to enable the provision of appropriate and relevant traffic information (e.g. congestion and travel times) to users, across a variety of platforms.

This document constitutes a Part of the CEN 16157 DATEX II series of standards and technical specifications. This series specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel. The component facets include the framework and context for exchanges, the modelling approach, the data content, the data structure and relationships and the communications specification.
Part 8, this document, specifies additional data model structures that are applicable for traffic management applications in the urban environment. This Part addresses data concepts to support the exchange of Traffic Management Plans, rerouting, extensions of the existing DATEX II core model to better support application to the urban environment.
It establishes specifications for data exchange between any two instances of the following actors:
- Traffic Information Centres (TICs),
- Traffic Control Centres (TCCs),
- Service Providers (SPs).
Use of this document may be applicable for use by other actors.

1.1   General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V5.1 (EN 12986), IFOPT (CEN/TS 28701) 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.
NOTE   Many NeTEx concepts are taken directly from Transmodel and IFOPT; the definitions and explanation of these concepts are extracted directly from the respective standards and reused in NeTEx, sometimes with further adaptions in order to fit the NETEx context.
The data exchanges targeted by NeTEx are predominantly oriented towards passenger information and also for data exchange between transit scheduling systems and AVMS (Automated Vehicle Monitoring Systems). However it is not restricted to these purposes, and NeTEx can provide an effective solution to many other use cases for transport exchange.
1.2   Transport modes
Most public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tram-way, ferry, and their submodes. It is possible to describe airports and air journeys, but there has not been any specific consideration of any additional provisions that apply especially to air transport.
1.3   Compatibility with existing standards and recommendations
The concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and related organizations; stations and related equipment; journey coupling and journey parts; train com-position and facilities; planned passing times; timetable versions and validity conditions.
In the case of long distance train the NeTEx takes into account the requirements formulated by the ERA (European Rail Agency) – TAP/TSI (Telematics Applications for Passenger/ Technical Specification for Interoperability, entered into force on 13 May 2011 as the Commission Regulation (EU) No 454/2011), based on UIC directives.
As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (Netherland) and NOPTIS (Nordic Public Transport Interface Standard).
The data exchange is possible either through dedicated web services, through data file exchanges, or using the SIRI exchange protocol as described in part 2 of the SIRI documentation.

1.1   General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V5.1 (EN 12986), IFOPT (EN 28701) 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   NeTEx is a refinement and an implementation of Transmodel and IFOPT; the definitions and explanations of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptations 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 transit scheduling systems, it is not restricted to this purpose and NeTEx can also provide an effective solution to many other use cases for transport data exchange.
1.2   Fares scope
This Part3 of NeTEx, is specifically concerned with the exchange of fare structures and fare data, using data models that relate to the underlying network and timetable models defined in Part1 and Part2 and the Fare Collection data model defined in Transmodel V51. See the use cases below for the overall scope of Part3. In summary, it is concerned with data for the following purposes:
(i)   To describe the many various possible fare structures that arise in public transport (for example, flat fares, zonal fares, time dependent fares, distance-based fares, stage fares, pay as you go fares, season passes, etc., etc.).
(ii)   To describe the fare products that may be purchased having these fare structures and to describe the conditions that may attach to particular fares, for example if restricted to specific groups of users, or subject to temporal restrictions. These conditions may be complex.
(i)   To allow actual price data to be exchanged. Note however that NeTEx does not itself specify pricing algorithms or how fares should be calculated. This is the concern of Fare Management Systems. It may be used may be used to exchange various parameters required for pricing calculations that are needed to explain or justify a fare.
(iii)   To include the attributes and the text descriptions necessary to present fares and their conditions of sale and use to the public.
NeTEx should be regarded as being ‘upstream’ of retail systems and allows fare data to be managed and integrated with journey planning and network data in public facing information systems. It is complementary to and distinct from the ‘downstream’ ticketing and retail systems that sell fares and of the control systems that validate their use. See ‘Excluded Use Cases’ below for further information on the boundaries of NeTEx with Fare Management Systems.
1.3   Transport modes
All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports, air journeys, and air fares, but there has not been any specific consideration of any additional requirements that apply specifically to air transport.

This TS will focus on the principal aspects of urban ITS where vendor lock-in is a technical and financial problem: primarily centre-tofield communications and traffic management systems. It will cover the following scope:
- Analysis of vendor lock-in challenges, and mitigation and migration options
- Technical options for interworking multiple vendors' products
- Review of principal approaches taken to date to implement these options in comunity frameworks and specifications
- Translation between frameworks/products
- Technical and management protocols to achieve interworking, using product/interface adaptation, translation products, replacement/reengineering, and other migration strategies

This technical specification 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.

This document defines new modes in a reference data model, in order to allow integration of these modes into urban multimodal travel services (e.g. trip planning systems).

This document will provide a background to the relevance of standards concerning mixed vendor environments in the context of urban-ITS. It will describe key mixed vendor environments interfaces.
It will define:
- Open specifications for sensor systems: existing open specifications and provides common specifications
- Open specifications for traffic control: existing open specifications and provides common specifications
- Open specifications for traffic information: existing open specifications and provides common specifications
- Open specifications for public transport information systems: existing open specifications and provides common specifications
- Open specifications for distributed C-ITS: existing open specifications and provides common specifications
- Open specifications for central systems: existing open specifications and provides common specifications
It will describe openly plied proprietary standards and extant communications protocols that can be used in mixed vendor environments in the context of urban-ITS.

This TS will focus on the principal aspects of urban ITS where vendor lock-in is a technical and financial problem: primarily centre-tofield communications and traffic management systems. It will cover the following scope:
- Analysis of vendor lock-in challenges, and mitigation and migration options
- Technical options for interworking multiple vendors' products
- Review of principal approaches taken to date to implement these options in comunity frameworks and specifications
- Translation between frameworks/products
- Technical and management protocols to achieve interworking, using product/interface adaptation, translation products, replacement/reengineering, and other migration strategies

This technical specification 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.

1.1   General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V5.1 (EN 12986), IFOPT (EN 28701) 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   NeTEx is a refinement and an implementation of Transmodel and IFOPT; the definitions and explanations of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptations 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 transit scheduling systems, it is not restricted to this purpose and NeTEx can also provide an effective solution to many other use cases for transport data exchange.
1.2   Fares scope
This Part3 of NeTEx, is specifically concerned with the exchange of fare structures and fare data, using data models that relate to the underlying network and timetable models defined in Part1 and Part2 and the Fare Collection data model defined in Transmodel V51. See the use cases below for the overall scope of Part3. In summary, it is concerned with data for the following purposes:
(i)   To describe the many various possible fare structures that arise in public transport (for example, flat fares, zonal fares, time dependent fares, distance-based fares, stage fares, pay as you go fares, season passes, etc., etc.).
(ii)   To describe the fare products that may be purchased having these fare structures and to describe the conditions that may attach to particular fares, for example if restricted to specific groups of users, or subject to temporal restrictions. These conditions may be complex.
(i)   To allow actual price data to be exchanged. Note however that NeTEx does not itself specify pricing algorithms or how fares should be calculated. This is the concern of Fare Management Systems. It may be used may be used to exchange various parameters required for pricing calculations that are needed to explain or justify a fare.
(iii)   To include the attributes and the text descriptions necessary to present fares and their conditions of sale and use to the public.
NeTEx should be regarded as being ‘upstream’ of retail systems and allows fare data to be managed and integrated with journey planning and network data in public facing information systems. It is complementary to and distinct from the ‘downstream’ ticketing and retail systems that sell fares and of the control systems that validate their use. See ‘Excluded Use Cases’ below for further information on the boundaries of NeTEx with Fare Management Systems.
1.3   Transport modes
All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports, air journeys, and air fares, but there has not been any specific consideration of any additional requirements that apply specifically to air transport.

This document defines new modes in a reference data model, in order to allow integration of these modes into urban multimodal travel services (e.g. trip planning systems).

This document will provide a background to the relevance of standards concerning mixed vendor environments in the context of urban-ITS. It will describe key mixed vendor environments interfaces.
It will define:
- Open specifications for sensor systems: existing open specifications and provides common specifications
- Open specifications for traffic control: existing open specifications and provides common specifications
- Open specifications for traffic information: existing open specifications and provides common specifications
- Open specifications for public transport information systems: existing open specifications and provides common specifications
- Open specifications for distributed C-ITS: existing open specifications and provides common specifications
- Open specifications for central systems: existing open specifications and provides common specifications
It will describe openly plied proprietary standards and extant communications protocols that can be used in mixed vendor environments in the context of urban-ITS.

This document will provide specifications for a “Concept of Operations (CONOPS) for the introduction and maintenance of a “Mixed Vendor Environment” (MVE) in the domain of urban-ITS. Structured as:
PART I "Context and issues to be addressed"
Describing the context, background, objective of the MVE Guide, and the architectural context.
PART II "Work concepts"
Examines aspects of system design and architecture , and presents the basic knowledge required for the application of Part III.
PART III "Practice"
Provides system design and procurement on three levels against the background of a procedure model.
- user level
- conceptual explanation
- examples.
PART IV "Outlook"
Specifies guidance and requirements for the application of MVE for future business.

This document will provide specifications for a “Concept of Operations (CONOPS) for the introduction and maintenance of a “Mixed Vendor Environment” (MVE) in the domain of urban-ITS. Structured as:
PART I "Context and issues to be addressed"
Describing the context, background, objective of the MVE Guide, and the architectural context.
PART II "Work concepts"
Examines aspects of system design and architecture , and presents the basic knowledge required for the application of Part III.
PART III "Practice"
Provides system design and procurement on three levels against the background of a procedure model.
- user level
- conceptual explanation
- examples.
PART IV "Outlook"
Specifies guidance and requirements for the application of MVE for future business.

This document provides
• information, guidance and specifications on how
o to set up an air quality and emissions management policy;
o to deploy reliable and scalable technologies to monitor air quality on a continuous or regular basis;
o to react with adequate measures;
o to specify air quality levels for triggering a scenario;
• a toolkit of parameters and data definitions that a regulator can use;
• means to measure the air quality required by relevant EU directives
• to specify use of TS Intelligent transport systems - Urban-ITS - 'Controlled Zone' management using C-ITS, for the purposes of geofenced controlled zones for emissions management
NOTE: In order to maximise European harmonisation, it is recommended that this specification is used in combination with a module of standardised data concepts, however, this version of this document, which is focussed on policies and procedures, does not provide these data concept specifications.

This document provides information and specifications enabling management of road traffic in controlled zones applying geofencing. Specifically, this document provides
-   a "Controlled Zone Data Dictionary" (CZDD) for management of controlled zones providing an extendible toolkit that regulators can use e.g. to inform potential CZ users, e.g. vehicles, about
   -   the CZ area, i.e. the geographical boundaries of the CZ;
   -   CZ access conditions including exempts;
   -   time windows indicating when these CZ access conditions are applicable, allowing the potential CZ users to select an appropriate routing, either by pre-trip planning or ad hoc re-routing,
   -   and illustrations and guidelines on how to use this toolkit.
The toolkit is designed in compliance with the general ITS station and communications architecture specified in ISO 21217, and optionally applicable C-ITS protocols and procedures, e.g. ISO 22418:2018 [8] on "Service Announcement", EN ISO 18750 on the "Local Dynamic Map", and EN ISO 17419 [5] on globally unique identifiers.
Enforcement is out of scope of this document.

This document provides
• information, guidance and specifications on how
o to set up an air quality and emissions management policy;
o to deploy reliable and scalable technologies to monitor air quality on a continuous or regular basis;
o to react with adequate measures;
o to specify air quality levels for triggering a scenario;
• a toolkit of parameters and data definitions that a regulator can use;
• means to measure the air quality required by relevant EU directives
• to specify use of TS Intelligent transport systems - Urban-ITS - 'Controlled Zone' management using C-ITS, for the purposes of geofenced controlled zones for emissions management
NOTE: In order to maximise European harmonisation, it is recommended that this specification is used in combination with a module of standardised data concepts, however, this version of this document, which is focussed on policies and procedures, does not provide these data concept specifications.

This document specifies requirements, recommendations, and permissions related to translations between location referencing methods applicable in the urban transport environment.

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 standard, 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) representing 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.

The data model dedicated to cover a wide range of use cases of the domain Management Information & Statistics (in particuar a subset of use cases described by the project OpRa – Operational Raw Data) will be specified, in particular: data used for statistics and registered data from which service quality indicators may be derived.
The following transport modes will be considered: bus, metro, tramway, trolleybus, ferry, coach, long distance rail. Particular attention will be drawn to the data model structure and methodology: the data model will be described in UML, in a modular form in order to facilitate the understanding and use of the model.
The model will take into account a range of extension requests formulated by users, but also, in order to guarantee a coherence of the overall model (Part 1 to 8), of the domains modelled in Parts 1 to 3:
Public transport - Reference data model - Part 1: Common Concepts, describing concepts shared by the different functional domains
Public transport - Reference data model - Part 2: Public Transport Network, describing routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.
Public transport - Reference data model - Part 3: Timing Information and Vehicle Scheduling, describing runtimes, vehicle journeys, day type-related vehicle schedules.

1.1   General scope of the standard
The main objective of the present document is to present the Reference Data Model for Public Transport, based on:
-   the Reference Data Model, EN12896, known as Transmodel V5.1;
-   EN 28701:2012, 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 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: Service interface for real-time information relating to public transport operations (SIRI);
-   CEN/TS 16614-1 and -2: 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 standard, and of which the data have been represented as the reference model, are described in "Public Transport Reference Data Model - Part 1: Common Concepts".
1.3   Particular Scope of this document
The present European Standard entitled "Reference Data Model for Public Transport - Part 6: Passenger Information" incorporates the following main data packages:
-   Trip Description;
-   Passenger Queries.
This document itself is composed of the following parts:
-   Main document (normative) representing the data model for the concepts shared by the different fare 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 EN12896-1:2016, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model;
-   Annex C (informative), indicating the data model evolutions;
-   Annex D (informative), indicating the high-level equivalences of the example passenger information functional requests to the capabilities of other standards;
-   Annex E (informative), providing an example set of commonly found passenger information functional requests and data dictionary for the elements used in the examples.

The data modules dedicated to cover most functions of the domain Operations Monitoring and Control will be specified, in particular: vehicle detecting and monitoring, events & control actions, messaging. This part will take into account SIRI and align with SIRI as far as possible.
The following transport modes will be considered: bus, metro, tramway, trolleybus, ferry, coach, long distance rail. Particular attention will be drawn to the data model structure and methodology: the data model will be described in UML, in a modular form in order to facilitate the understanding and use of the model.
The model will take into account a range of extension requests formulated by users, but also, in order to guarantee a coherence of the overall model (Part 1 to 8), of the domains modelled in Parts 1 to 3:
Public transport - Reference data model - Part 1: Common Concepts, describing concepts shared by the different functional domains
Public transport - Reference data model - Part 2: Public Transport Network, describing routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.
Public transport - Reference data model - Part 3: Timing Information and Vehicle Scheduling, describing runtimes, vehicle journeys, day type-related vehicle schedules.

The data modules dedicated to cover most functions of the domain Fare Management will be specified, in particular: fare structure, sales, validation & control of access rights. The achievements of Transmodel V5.1 and NeTEx will be taken into account.
The following transport modes will be considered: bus, metro, tramway, trolleybus, ferry, coach, long distance rail. Particular attention will be drawn to the data model structure and methodology: the data model will be described in UML, in a modular form in order to facilitate the understanding and use of the model.
The model will take into account a range of extension requests formulated by users, but also, in order to guarantee a coherence of the overall model (Part 1 to 8), of the domains modelled in Parts 1 to 3:
Public transport - Reference data model - Part 1: Common Concepts, describing concepts shared by the different functional domains
Public transport - Reference data model - Part 2: Public Transport Network, describing routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places.
Public transport - Reference data model - Part 3: Timing Information and Vehicle Scheduling, describing runtimes, vehicle journeys, day type-related vehicle schedules.

This document contains specifications for a set of ITS station security services required to ensure the authenticity of the source and integrity of information exchanged between trusted entities:
— devices operated as bounded secured managed entities, i.e. "ITS Station Communication Units" (ITS-SCU) and "ITS station units" (ITS-SU) specified in ISO 21217, and
— between ITS-SUs (composed of one or several ITS-SCUs) and external trusted entities such as sensor and control networks.
These services include authentication and secure session establishment which are required to exchange information in a trusted and secure manner.
These services are essential for many ITS applications and services including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2[5]), and roadside/infrastructure related services.

A Technical Report with informative and didactical material to users.

This document specifies requirements, recommendations, and permissions related to translations between location referencing methods applicable in the urban transport environment.

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 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:2016, 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 4: Operations monitoring and control incorporates the following data packages:
-   Dated Production Components MODEL;
-   Call MODEL;
-   Production Plan MODEL;
-   Detecting and Monitoring MODEL;
-   Control Action MODEL;
-   Event and Incident MODEL;
-   Messaging MODEL;
-   Situation MODEL; and
-   Facility Monitoring and Availability MODEL.
The data structures represented in this part form descriptions of data that are specific to operations for an operational day (as opposed to those planned for day types). They reference to structures as described in EN 12896-1:2016, such as version frames or generic grouping mechanisms, but also to EN 12896-2:2016 and EN 12896-3:2016.
This document itself is composed of the following parts:
-   Main document (normative) presenting the data model for the domain Operations Monitoring and Control;
-   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;
-   Annex C (informative), indicating the data model evolutions; and
(...)

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.

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 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: 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:2016, 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 8: Management information & statistics describes how to structure data which refers to the planning stages (e.g. timetables, run times, driver rosters, etc.) and/or to the daily actual production, and which is registered for different purposes, in particular to build service performance indicators. The data model is based on a generic design pattern, Generic Loggable Objects Model (provided in the Additional Common Concepts part -  Annex B), and incorporates the following data packages:
-   Logging Time and Place, providing additions to the Generic Loggable Objects Model,
-   Recorded Objects,
-   Recorded Use of Services,
-   Service Journey Performance.
The last three packages show how the recorded data contributes to the implementation of indicators.
This document itself is composed of the following parts:
-   Main document (normative),
-   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;
-   Annex C (informative), indicating the data model evolution from the previous version.

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 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 standard, and of which the data have been represented as the reference model, are described in EN 12896-1:2016, 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 6: Passenger information, incorporates the following main data packages:
-   Trip Description;
-   Passenger Queries.
This document itself is composed of the following parts:
-   Main document (normative) representing the data model for the concepts shared by the different fare 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;
-   Annex C (informative), indicating the data model evolutions;
-   Annex D (informative), indicating the high-level equivalences of the example passenger information functional requests to the capabilities of other standards;
-   Annex E (informative), providing an example set of commonly found passenger information functional requests and data dictionary for the elements used in the examples.

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 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 standard, and of which the data have been represented as the reference model, are described in EN 12896-1:2016, 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 5: Fare Management addresses Fare Information for Public Transport and incorporates 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 (normative) representing the data model for the concepts shared by the different fare 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 the "Common Concepts" domain, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model,
Annex C (informative), indicating the data model evolutions from previous versions of Transmodel (EN 12896:2006).

A Technical Report with informative and didactical material to users.

This document defines the message, data structures, and data elements to support exchanges between
the roadside equipment and vehicles to address applications to improve safety, mobility and
environmental efficiency. In order to verify that the defined messages will satisfy these applications, a
systems engineering process has been employed that traces use cases to requirements and
requirements to messages and data concepts.
This document consists of a single document that contains the base specification and a series of
annexes. The base specification lists the derived information requirements (labelled informative) and
references to other standards for message definitions where available. Annex A contains descriptions of
the use cases addressed by this document. Annexes B and C contain traceability matrices that relate use
cases to requirements and requirements to the message definitions (i.e. data frames and data elements).
The next annexes list the base message requirements and application-oriented specific requirements
(requirements traceability matrix) that map to the message and data concepts to be implemented. As
such, an implementation consists of the base plus an additional group of extensions within this
document.
Details on information requirements, for other than SPaT, MAP, SSM, and SRM messages are provided in
other International Standards. The focus of this document is to specify the details of the SPaT, MAP,
SSM, and SRM supporting the use cases defined in this document. Adoption of these messages varies by
region and their adoption can occur over a significant time period.
This document covers the interface between roadside equipment and vehicles. Applications, their
internal algorithms, and the logical distribution of application functionality over any specific system
architecture are outside the scope of this document.

1.1   Introduction
The OpRa work scope is the definition of a minimum set of Public Transport raw data needed as PT quantitative analysis enabling factor. To obtain this considering all the several aspects involved in this complex domain, the work has been conducted through the following phases:
1)   assessment;
2)   use cases definition and classification;
3)   indicators definition;
4)   raw data identification.
OpRa work does not go into the field of service quality measurement and reporting: service quality analysis will of course use data provided by OpRa, but quality definition remains a contractual level issue between a Public Transport Authority and a Public Transport Operator or an operator’s internal choice for a purely private service. OpRa mainly only reports unbiased actual data (i.e. measured or observed), described and aggregated in a shared and understandable way.
The OpRa work documented in detail in this document is coherent with EU Directive 2010/40. In particular, it relates to the Article 4  of the Delegated Regulation EU 2017/1926 , as regards the historic data. OpRa proposes to complement NeTEx (dedicated to the static scheduled information), for the historic data based on the underlying conceptual data reference model Transmodel EN 12896, similarly to the requirement of the Delegated Regulation EU 2017/1926 referring to the static scheduled information .
1.2   Assessment phase
The assessment phase has been conducted studying the following aspects:
•   national scenarios for public transport raw data and statistics exchange, to identify indicators needs and usage;
•   public transport KPI definition in research projects to consider what has been already done in literature and research;
•   relations with public transport EU norms, to be coherent with already existent PT norms.
Moreover, involved actors and stakeholders have been identified like: Public Transport Authority (PTA), Public Transport Agencies, Public Transport Operator (PTO), system integrators and passengers, analysing public transportation Planning and Operation process, that have been divided into five main stages to group all the activates that characterize the Public Transport Service:
•   strategic planning: definition of network elements (lines, stops), main service parameters (vehicles sizes, operation intervals, service intervals for important time demand types), and guaranteed interchanges are planned;
•   tactical planning: operators plan their resource usage (vehicles, rolling stock, personnel), with detailed timetables for each resource unit;
•   before travel: all planned networks and timetables are published. Passengers and other types of clients can plan their use of the offered transportation services via printed and electronic media, and make their reservations as needed;
•   in-travel: the transportation service is conducted. Real-time information exchange is available while this takes place and can be recorded;
•   study and control: in this stage, operators and authorities review the history of actual operations, which could lead to improvements through operational changes, or an optimization of strategic and tactical planning.
The PTA and PTO are interested in all the defined stages, meanwhile from the passenger point of view; only the last three stages are relevant (all the preparation work being hidden).
During the assessment the most relevant research projects results have been considered and a deep analysis of the roles and usage of Public Transport Standards have been completed to guarantee a coherent approach of OpRa.
The first four stages are under the scope of NeTEx (Network Timetable Exchange) and SIRI (Service Interface for Real Time Information) and the last stage is the additional scope to be covered by OpRa. All these standards are compliant with the European Public Transport Reference Data Model (Transmodel).

This Technical Specification provides the Protocol Implementation Conformance Statement (PICS) pro forma for Conformance test specification for the Contextual Speed Information Service as defined in CEN ISO/TS 17426:2016 in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7.

This document presents:
-   a concise tutorial on location referencing methods;
-   applicable location referencing specifications, standards and directives;
-   an introduction into challenges given by a multiplicity of different location referencing systems.