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).

  • Technical specification
    124 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical specification
    177 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    177 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    177 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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

  • Technical specification
    49 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical specification
    622 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    622 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    10 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    7 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical specification
    103 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the general rules for an on-board data communication system between the different systems that may be used within public transport vehicles, based on the Internet Protocol (IPv4, [3] and IPv6, [4]). This includes operational support systems, passenger information systems, fare collection systems, etc.
This document describes:
-   the requirements for an on board IP network;
-   the overview architecture and components for an IP based on-board network;
-   the modular structure of the network architecture;
-   the Service Oriented Architecture (SOA) approach, and approach to defining services.
Systems directly related to the safe operation of the vehicle (including propulsion management, brake systems, door opening systems) are excluded from the scope of this document and are dealt with in other standardization bodies. However, the architecture described in this document may be used for support services such as safety information messages. Interfaces to safety-critical systems should be provided through dedicated gateways with appropriate security provisions; for the purposes of this document, these are regarded as simply external information sources.
This document is designed primarily for vehicles with a fixed primary structure, where networks can be installed on a permanent basis and the system configuration task consists largely of the integration, adjustment or removal of the functional end systems that produce and/or consume data. Public transport vehicles consisting of units linked temporarily for operational purposes (specifically, trains in which individual engines, cars or consists are routinely connected and disconnected) require additional mechanisms to enable the communications network itself to reconfigure. Such mechanisms are provided through other standards, notably the IEC 61375 series [5].

  • Technical specification
    26 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies transactions and data for Compliance Checking - Secure Monitoring. The Scope of this document consists of:
—-   the concept and involved processes for Secure Monitoring;
-   the definition of transactions and data;
-   the use of the OBE compliance checking transaction as specified in EN ISO 12813, for the purpose of Compliance Checking - Secure Monitoring;
-   the use of back end transactions as specified in EN ISO 12855, for the purpose of Compliance Checking – Secure Monitoring. This includes definitions for the use of optional elements and reserved attributes;
-   a specification of technical and organizational security measures involved in Secure Monitoring, on top of measures provided for in the EFC Security Framework;
-   the interrelations between different options in the OBE, TSP and TC domain and their high level impacts.
NOTE   Outside the Scope of this document is: The information exchange between OBE and TR, choices related to compliance checking policies e.g. which options are used, whether undetected/unexpected observations are applied, whether fixed, transportable or mobile compliance checking are deployed, locations and intensity of checking of itinerary freezing and checking of toll declaration, details of procedures and criteria for assessing the validity or plausibility of Itinerary Records.

  • Technical specification
    87 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical report
    48 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the requirements for the secure application module (SAM) used in the secure monitoring compliance checking concept. It specifies two different configurations of a SAM:
-   trusted recorder, for use inside an OBE;
-   verification SAM, for use in other EFC system entities.
This document describes
-   terms and definitions used to describe the two Secure Application Module configurations;
-   operation of the two Secure Application Modules in the secure monitoring compliance checking concept;
-   functional requirements for the two Secure Application Modules configurations, including a classification of different security levels;
-   the interface, by means of transactions, messages and data elements, between an OBE or front end and the trusted recorder;
-   requirements on basic security primitives and key management procedures to support Secure Monitoring using a trusted recorder.
This document is consistent with the EFC architecture as defined in EN ISO 17573-1 and the derived suite of standards and Technical Specifications, especially CEN/TS 16702-1 and CEN ISO/TS 19299.
The following is outside the scope of this document:
-   The life cycle of a Secure Application Module and the way in which this is managed;
-   The interface commands needed to get a Secure Application Module in an operational state;
-   The interface definition of the verification SAM;
-   Definition of a hardware platform for the implementation of a Secure Application Module.

  • Technical specification
    54 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines requirements for short-range communication for the purposes of compliance checking in autonomous electronic fee collecting systems. Compliance checking communication (CCC) takes place between a road vehicle's on-board equipment (OBE) and an interrogator (roadside mounted equipment, mobile device or hand-held unit), and serves to establish whether the data that are delivered by the OBE correctly reflect the road usage of the corresponding vehicle according to the rules of the pertinent toll regime.
The operator of the compliance checking interrogator is assumed to be part of the toll charging role as defined in ISO 17573-1. The CCC permits identification of the OBE, vehicle and contract, and verification of whether the driver has fulfilled his obligations and the checking status and performance of the OBE. The CCC reads, but does not write, OBE data.
This document is applicable to OBE in an autonomous mode of operation; it is not applicable to compliance checking in dedicated short-range communication (DSRC)-based charging systems.
It defines data syntax and semantics, but not a communication sequence. All the attributes defined herein are required in any OBE claimed to be compliant with this document, even if some values are set to "not defined" in cases where certain functionality is not present in an OBE. The interrogator is free to choose which attributes are read in the data retrieval phase, as well as the sequence in which they are read. In order to achieve compatibility with existing systems, the communication makes use of the attributes defined in ISO 14906 wherever useful.
The CCC is suitable for a range of short-range communication media. Specific definitions are given for the CEN-DSRC as specified in EN 15509, as well as for the use of ISO CALM IR, the Italian DSRC as specified in ETSI ES 200 674-1, ARIB DSRC and WAVE DSRC as alternatives to the CEN-DSRC. The attributes and functions defined are for compliance checking by means of the DSRC communication services provided by DSRC application layer, with the CCC attributes and functions made available to the CCC applications at the roadside equipment (RSE) and OBE. The attributes and functions are defined on the level of application data units (ADU).
The definition of the CCC includes:
— the application interface between OBE and RSE (as depicted in Figure 2);
— use of the generic DSRC application layer as specified in ISO 15628 and EN 12834;
— CCC data type specifications given in Annex A;
— a protocol implementation conformance statement (PICS) proforma is given in Annex B;
— use of the CEN-DSRC stack as specified in EN 15509, or other equivalent DSRC stacks as described in Annex C, Annex D, Annex E and Annex F;
— security services for mutual authentication of the communication partners and for signing of data (see Annex H);
— an example CCC transaction is presented in Annex G;
— the informative Annex I highlights how to use this document for the European electronic toll service (as defined in Commission Decision 2009/750/EC).
Test specifications are not within the scope of this document.

  • Standard
    62 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Technical Specification defines additional data to be sent in the event that an eCall is triggered, as part of the MSD, in the case where the vehicle is an automated vehicle or an autonomous vehicle, to identify :
1) The vehicle is an automated/autonomous vehicle
2) The number of persons on board at the time of the incident
3) Whether or not the vehicle has rolled over
4) Whether the pedestrian airbag has been deployed
5) Whether it is (a) driver initiated automation or (b) centrally controlled automation
6) And if (b) coordinates to contact the vehicle controller.

  • Technical specification
    19 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document constitutes the 3rd edition of CEN/TS 16794-1. It sets out the technical requirements to be met by contactless Public Transport (PT) devices in order to be able to interface together using the ISO/IEC 14443 series contactless communications protocol.
This document applies to PT devices:
-   PT readers which are contactless fare management system terminals acting as a PCD contactless reader based on the ISO/IEC 14443 series;
-   PT objects which are contactless fare media acting as a PICC contactless object based on the ISO/IEC 14443 series.
This edition addresses interoperability of consumer-market NFC mobile devices, compliant to NFC Forum specifications, with above mentioned PT devices, aligns with the 4th edition of the ISO/IEC 14443 series and maintains the possibility for PT readers to comply with the requirements from EMV Contactless Interface Specification [1] and the present document.
An interface–oriented test approach is used to evaluate the conformity of PT devices and is defined in CEN/TS 16794-2.
Application-to-application exchanges executed once contactless communication has been established at RF level fall outside the scope of this document. In line with the rules on independence between OSI protocol layers, this document works on the assumption that application-to-application exchanges are not contingent on the type of contactless communication established or the parameters used for the low-level protocol layers that serve as the platform for these application-to-application exchanges.

  • Technical specification
    38 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines and specifies 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 data content, structure and relationships necessary and the communications specification, in such a way that they are independent from any defined technical platform.
This document establishes specifications for data exchange between any two instances of the following actors:
— Traffic Information Centres (TIC);
— Traffic Control Centres/Traffic Management Centres (TCC/TMC);
— Service Providers (SP).
This document can be applied for use by other actors, e.g. car park operators.
This document includes the following types of information:
— the use cases and associated requirements, and features relative to different exchange situations;
— the different functional exchange profiles;
— the abstract elements for protocols;
— the data model for exchange (informational structures, relationships, roles, attributes and associated data types required).
In order to set up a new technical exchange framework, it is necessary to associate one functional exchange profile with a technical platform providing an interoperability domain where plug-and-play interoperability at technical level can be expected. The definition of such interoperability domains is not part of this document but can be found in other standards or technical specifications, e.g. ISO 14827‑3. This document is restricted to data exchange. Definition of payload content models is beyond the scope of this document.

  • Technical specification
    131 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document comes as a complement to the technical requirements expressed in CEN/TS 16794 1, for ensuring contactless communication interoperability between Public Transport (PT) devices or between PT devices compliant to CEN/TS 16794-1 and NFC mobiles devices compliant to NFC Forum specifications.
This document lists all the test conditions to be performed on a PT reader or a PT object in order to ensure that all the requirements specified in CEN/TS 16794 1 are met for the PT device under test.
This document applies to PT devices only:
-   PT readers which are contactless fare management system terminals acting as a PCD contactless reader based on the ISO/IEC 14443 series;
-   PT objects which are contactless fare media acting as a PICC contactless object based on the ISO/IEC 14443 series.
This document applies solely to the contactless communication layers described in Parts 1 to 4 of the ISO/IEC 14443 series. Application-to-application exchanges executed once contactless communication has been established at RF level fall outside the scope of this document. However, a test application will be used so as to make end-to-end transactions during tests on the RF communication layer.
This document does not duplicate the contents of the ISO/IEC 14443 series or ISO/IEC DIS 10373-6 standard. It makes reference to the ISO/IEC DIS 10373 6 applicable test methods, specifies the test conditions to be used and describes the additional specific test conditions that may be run.
The list of test conditions applicable to the PT device under test will be conditioned by the Information Conformance Statement (ICS) declaration made by the device manufacturer. For each test case, the test conditions are clearly specified in order to determine the pertinence to run or not the test case in accordance with the device capabilities or in accordance with the device manufacturer’s choice.
In order to facilitate the test report issuance, a test report template is included in Annex A of this document.
Although this document aims at becoming the primary basis for certification of contactless communication protocol applicable to PT readers and PT objects, it does not describe any certification or qualification processes as such processes should be defined between local or global transit industry stakeholders.

  • Technical specification
    32 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical specification
    26 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical specification
    57 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical specification
    97 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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

  • Technical specification
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 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.

  • Standard
    123 pages
    English language
    sale 10% off
    e-Library read for
    1 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 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
(...)

  • Standard
    174 pages
    English language
    sale 10% off
    e-Library read for
    1 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 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.

  • Standard
    85 pages
    English language
    sale 10% off
    e-Library read for
    1 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 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.

  • Standard
    175 pages
    English language
    sale 10% off
    e-Library read for
    1 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 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).

  • Standard
    407 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the architecture of electronic fee collection (EFC) system environments, in which a customer with one contract may use a vehicle in a variety of toll domains with a different toll charger for each domain.
EFC systems conforming to this document can be used for various purposes including road (network) tolling, area tolling, collecting fees for the usage of bridges, tunnels, ferries, for access or for parking. From a technical point of view the considered toll systems may identify vehicles subject to tolling by means of electronic equipment on-board in a vehicle or by other means (e.g. automatic number plate recognition, ANPR).
From a process point of view the architectural description focuses on toll determination, toll charging, and the associated enforcement measures. The actual collection of the toll, i.e. collecting payments, is outside of the scope of this document.
The architecture in this document is defined with no more details than required for an overall overview, a common language, an identification of the need for and interactions among other standards, and the drafting of these standards.
This document as a whole provides:
— the enterprise view on the architecture, which is concerned with the purpose, scope and policies governing the activities of the specified system within the organization of which it is a part;
— the terms and definitions for common use in an EFC environment;
— a decomposition of the EFC systems environment into its main enterprise objects;
— the roles and responsibilities of the main actors. This document does not impose that all roles perform all indicated responsibilities. It should also be clear that the responsibilities of a role may be shared between two or more actors. Mandating the performance of certain responsibilities is the task of standards derived from this architecture;
— identification of the provided services by means of action diagrams that underline the needed standardised exchanges;
— identification of the interoperability interfaces for EFC systems, in specialised standards (specified or to be specified).

  • Standard
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines an eCall "Optional Additional Data" concept for 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.
This document defines:
a)   Protocol requirements to ensure phone user consent to the provision of the linked 'phone number to the PSAP in the event of an eCall triggering incident;
b)   Definition of the OAD concept "Linked mobile Telephone Number" (LTN);
c)   Privacy provisions;
d)   Advice to PSAPs on the use of the eCall OAD LTN;
e)   Example of an in-vehicle sequence generating the LTN OAD and forwarding it as part of the MSD.
For clarity, the communications media protocols and methods for the transmission of the eCall message are not specified in this document.

  • Technical specification
    22 pages
    English language
    sale 10% off
    e-Library read for
    1 day

A Technical Report with informative and didactical material to users.

  • Technical report
    1265 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical specification
    245 pages
    English language
    sale 10% off
    e-Library read for
    1 day

2.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. (...)

  • Technical report
    131 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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.

  • Technical report
    55 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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

  • Technical specification
    17 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides a suite of tests in order to assess the central equipment of toll chargers and toll service providers for compliancy towards the requirements listed in CEN/TS 16986. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific Test Purposes defined in CEN/TS 17154-1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).

  • Technical specification
    28 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the test suite structure (TSS) and test purposes (TP) to test conformity of central equipment of both toll chargers and toll service providers versus CEN/TS 16986.
It further provides templates for the protocol conformance test reports (PCTR) for the implementation under tests (IUT) for both the toll charger and the toll service provider.
This document contains the technical provisions to perform conformance testing of functional and dynamic behaviour of implementations conforming to CEN/TS 16986.
NOTE   The specifications in this Part provide the base for the tree and tabular combined notation (TTCN) of the test cases and steps which are provided in CEN/TS 17154 2.

  • Technical specification
    244 pages
    English language
    sale 10% off
    e-Library read for
    1 day

In respect of 112-eCall (operating requirements defined in EN 16072), this document defines specifications for the provision of eCall via satellite communications networks (Satellite-IMS-112-eCall and Satellite-TPS-eCall).
As with the existing provisions for eCall for Classes M1/N1 vehicles, these are specified within the paradigm of OEM fit equipment at the point of manufacture.
This document includes only the requirements for the provision of Satellite IMS-112-eCall using satellite telecommunications and Satellite-TPS-eCall.
NOTE   The 112-eCall paradigm involves a direct call from the vehicle to the most appropriate PSAP. (Third party service provision by comparison, involves the support of an intermediary third party service provider (TPSP) before the call is forwarded to the PSAP.)

  • Technical specification
    20 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document:
-   illustrates quality and performance criteria, and approaches to their evaluation, for the operation of traffic management systems, including factors affecting the effective integration of field and centre systems and services, and
-   specifies a data model for system status and faults of components of traffic management systems.
This document provides supporting information in a use case for the use of the quality and performance criteria, considering design, procurement, and performance management.

  • Technical specification
    67 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides a description for voluntarily consenting vendors (subsequently referred to as 'participating service providers’), who wish to provide TPS-eCall service in an open market environment, where users can select and change the service provider. It focusses on the use case 'TPS-eCall service', as standardized in EN 16102, only (and for clarification, does not apply in respect of 112-eCall, where no TPS provider is involved.)
The document determines the preconditions, requirements and functional means needed in order that users of a TPS-eCall service can choose and change her/his preferred service provider (TPSP) out of a range of available TPSPs, who are participating in the open market provisions determined in this specification.
Outside the scope of this document are:
a)   any commercial considerations (e.g. whether the service is offered for free or a charged service or part of a commercial service package offer),
b)   any contractual considerations (e.g. how a service contract between an user and a TPSP is established),
c)   any IT-security related issues in conjunction with the TPS in-vehicle system,
d)   any considerations regarding communication costs (for voice and data) related to the TPS-eCall service
e)   any PSAP related considerations (towards the PSAPs there is no impact related to provider change, since any TPSP needs to negotiate acceptance of its service offering with the PSAPs in the countries where the service is provided, before such service can be provided).

  • Technical specification
    24 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    24 pages
    English language
    sale 10% off
    e-Library read for
    1 day

In respect of 112-eCall (operating requirements defined in EN 16072), this document defines adaptations to eCall specifications defined in EN 16072 and other related documents to enable the provision of eCall for powered two wheel vehicles (vehicle centred).
As with the existing provisions for eCall for Category M1/N1 vehicles, these are specified within the paradigm of being OEM fit equipment supplied with new vehicles.
For the purposes of the present document, the P2WV ‘L’ categories, as defined in Directive 2002/24/EC, Regulation (EU) No 168/2013, UNECE and as referenced/specified in EN 15722 apply.
This document includes only the requirements for Category L1 and L3 powered two wheel vehicles (vehicle based) with the exception of L1e-A (powered cycle), although CEN/TS 17249 6 may reference other ‘L’ subcategories to use this document. (It will be noted that the categories L1 to L7 include 2, 3 and 4 wheel types e.g. motorcycles, tricycles and quadricycles.)
NOTE 1   Other Technical Specifications may be prepared for other UNECE category ‘L’ variants.
NOTE 2   The provision of eCall for vehicles via the aftermarket (post sale and registration) will be the subject of other work, and in respect of the operational requirements for any such aftermarket solutions for powered two wheel vehicles (vehicle centred), will use the specifications of this document as a principle reference point.
NOTE 3   The 112-eCall paradigm involves a direct call from the vehicle to the most appropriate PSAP. (Third party service provision by comparison, involves the support of an intermediary third party service provider before the call is forwarded to the PSAP.) The specifications herein relate only to the provision of 112-eCall or IMS-112-eCall (3.10), and do not provide specifications for third party service provision of eCall.
NOTE 4   Some of the elements of this document will require further in depth analysis before they can be implemented in a European Standard. These elements are included in this document however to document the current state of development of a European Standard. The current state of development on these elements justifies their inclusion in this document, but further assessment and analysis might require an amendment before implementation into a European Standard. (This is a normal evolution from a Technical Specification to a European Standard.)

  • Technical specification
    23 pages
    English language
    sale 10% off
    e-Library read for
    1 day

In respect of 112-eCall (operating requirements defined in EN 16072), this document defines adaptations to eCall specifications defined in EN 16072 and other related Standards to enable the provision of eCall for tricycle and quadricycle vehicles (vehicle centred) UNECE (UNECE ECE/TRANS/WP.29/78/Rev.4) vehicle categories L2, L4, L5, L6, L7. As with the existing provisions for eCall for Category M1/N1 vehicles, these are specified within the paradigm of being OEM fit equipment supplied with new vehicles.
This document includes only the requirements for Category L2, L4, L5, L6 and L7 Tricycles and Quadricycles (vehicle centred).
NOTE 1   The 112-eCall paradigm involves a direct call from the vehicle to the most appropriate PSAP (Third party service provision by comparison, involves the support of an intermediary third party service provider before the call is forwarded to the PSAP). The specifications herein relate only to the provision of 112-eCall or IMS-112-eCall, and do not provide specifications for third party service provision of eCall.
NOTE 2   Some of the elements of this document will require further in-depth analysis before they can be implemented in a European Standard. The current state of development on these elements justifies their inclusion in this document, but further assessment and analysis might require an amendment before implementation into a European Standard.

  • Technical specification
    15 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This European Standard series (EN 16157) 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 series 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 series 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 series 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 EN 16157 series specifies the informational structures, relationships, roles, attributes and associated data types, for the implementation of the location referencing systems used in association with the different publications defined in the Datex II framework. It also defines a DATEX II publication for exchanging predefined locations. This is part of the DATEX II platform independent data model.

  • Standard
    222 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The scope of this project is to extend eCall to other classes of vehicle, including HGVs, P2WVs, busses and coaches and agricultural/forestry vehicles

  • Technical specification
    30 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The intention of this document is to review what was done to envision the limits of the proposed technique and related schemes which will be described and to define what could be submitted to standards. Concepts which are to be used for BLE in IFM are based on a highly spread technology which is BLE. This is not limited to any trademark or proprietary scheme. Therefore any person having a smartphone can use this technology with prerequisite to have a Bluetooth version greater than 4.0 and a dedicated application on board the smartphone.
The background of this document is related to usage in Account Based Ticketing frame (see related document made in ISO/TC 204/WG 8). There is no information related to the IFM itself.

  • Technical report
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies and defines component facets required to support 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 data content, data structure and relationships, communications specification.
This document 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 document 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 can be applicable for use by other actors.
This document 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,
-   information about operator initiated actions - including both advisory and mandatory measures,
-   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 information and advice relating to use of the road network.
This part of EN 16157 specifies common informational structures, relationships, roles, attributes and associated data types required for publishing information within the DATEX II framework. This is specified as a DATEX II sub-model which is part of the DATEX II platform independent model, but this part only covers common elements that are used by more than one publication. It excludes those elements that relate to location information which are specified in FprEN 16157 2.

  • Standard
    160 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document 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 document 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 document 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 can be applicable for use by other actors.
This document 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 document specifies the informational structures, relationships, roles, attributes and associated data types required for publishing situation traffic and travel information within the DATEX II framework. This is specified as a DATEX II Situation Publication sub-model which is part of the DATEX II platform independent model, but this part excludes those elements that relate to:
-   location information which are specified in FprEN 16157 2;
-   common information elements, which are specified in EN 16157 7.

  • Standard
    161 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies and defines components required to support the exchange and shared use of data and information in the field of traffic and travel.
The components include the framework and context for the modelling approach, data content, data structure and relationships.
This document 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 document 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 can be applicable for use by other actors.
This document 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,
-   information about operator-initiated actions - including both advisory and mandatory measures,
-   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 information and advice relating to use of the road network.
This part of EN 16157 specifies the DATEX II framework of all parts of this European Standard, the context of use and the modelling approach taken and used throughout this European Standard. This approach is described using formal methods and provides the mandatory reference framework for all other parts.

  • Standard
    34 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The Scope of this document is limited to the provision of eCall from a commercial vehicle prime mover /rigid body truck designed for conveying cargo (UNECE Category N).
Within the context of 112-eCall (operating requirements defined in EN 16072), this document defines specifications for the provision of 112-eCall for regulated commercial vehicles, including rigid body trucks and variants thereof, prime mover and trailer combinations (sometimes called "semi’s", road trains [one prime mover with multiple trailers]) and other regulated commercial vehicles (for example vans carrying medical supplies or radioactive material).
As with the existing provisions for 112-eCall for Category M1/N1 vehicles, these are specified within the paradigm of being OEM fit equipment supplied with new vehicles.
The work of CEN/TS 16405 is adopted and extended in this document. (A revised edition of CEN/TS 16405(:2018) will remain the principal reference document for the content and definition of the commercial vehicle optional additional data set.)
This document specifies the requirements for the use of 112-eCall by a commercial vehicle prime mover /rigid body truck and determines circumstances where it is appropriate to additionally provide new optional additional data as determined in CEN/TS 16405(:2018 or later) as Schema C for use in a packet switched environment which is not constrained by the 140 byte limit.
Unless superseded by European Regulation on some future date, all data schemas specified in CEN/TS 16405 are "Optional Additional Data" (OAD) concepts, as enabled in accordance with EN 15722 as part of the minimum set of data. As OAD they, and the elements within them, are, by definition, "optional" with use at the discretion of the operator of the vehicle.
NOTE 1   The provision of eCall from IVS located within trailers is not included in this document.
NOTE 2   The provision of eCall for vehicles via the aftermarket (post sale and registration) will be the subject of other work, and in respect of the operational requirements for any such aftermarket solutions for commercial vehicles, will use this document as a principle reference point.
NOTE 3   The 112-eCall paradigm involves a direct call from the vehicle to the most appropriate PSAP. (Third party service provision by comparison, involves the support of an intermediary third party service provider before the call is forwarded to the PSAP). The specifications herein relate only to the provision of 112-eCall or IMS-112-eCall, and do not provide specifications for third party service provision of eCall, although in the case of 112-eCall for commercial vehicles, links to third party provision of service aspects (such as cargo contents) may be required.

  • Technical specification
    14 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the application interface in the context of electronic fee collection (EFC) systems using the dedicated short-range communication (DSRC).

  • Standard
    133 pages
    English language
    sale 10% off
    e-Library read for
    1 day