CEN/TS 16614-1:2020

Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport network topology exchange format

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.

Öffentlicher Verkehr - Netzwerk- und Fahrplan-Austausch (NeTEx) - Teil 1: Austauschformat für Netzwerk-Topologie im öffentlichen Verkehr

Transport Public - Échanges des informations planifiées (NeTEx) - Partie 1: Topologie du réseau

Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 1. del: Izmenjavni format za topologijo omrežja javnega prevoza

General Information

• Status: Published
• Publication Date: 28-Apr-2020
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: CEN/TC 278 - Road transport and traffic telematics
• Drafting Committee: CEN/TC 278/WG 3 - Public transport (PT)
• Directive: 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
• Directive: 2016/797/EU - Directive (EU) 2016/797 of the European Parliament and of the Council of 11 May 2016 on the interoperability of the rail system within the European Union (Text with EEA relevance)
• Mandate: M/453 - Standardisation mandate addressed to CEN, CENELEC and ETSI in the field of information and communication technologies to support the interoperability of co-operative for intelligent transport in the european community
• Mandate: M/456 - Mandate to CEN for the development of European standards to establish the petrol vapour recovery efficiency of new Stage II petrol vapour recovery equipment and the in-use performance of such equipment once installed at service stations.
• Ref Project: SIST-TS CEN/TS 16614-1:2020 - Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport network topology exchange format

Relations

• Replaces: CEN/TS 16614-1:2014 - Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport network topology exchange format
• Effective Date: 11-May-2020

Standards Content (Sample)

SLOVENSKI STANDARD
01-julij-2020
Nadomešča:
SIST-TS CEN/TS 16614-1:2014
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 1. del:
Izmenjavni format za topologijo omrežja javnega prevoza
Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport
network topology exchange format
Öffentlicher Verkehr - Netzwerk- und Fahrplan-Austausch (NeTEx) - Teil 1:
Austauschformat für Netzwerk-Topologie im öffentlichen Verkehr
Transport Public - Échanges des informations planifiées (NeTEx) - Partie 1: Topologie du
réseau
Ta slovenski standard je istoveten z: CEN/TS 16614-1:2020
ICS:
03.220.01 Transport na splošno Transport in general
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

CEN/TS 16614-1
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
April 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.60 Supersedes CEN/TS 16614-1:2014
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Part 1: Public transport network topology
exchange format
Transport Public - Échanges des informations Öffentlicher Verkehr - Netzwerk- und Fahrplan-
planifiées (NeTEx) - Partie 1: Topologie du réseau Austausch (NeTEx) - Teil 1: Austauschformat für
Netzwerk-Topologie im öffentlichen Verkehr
This Technical Specification (CEN/TS) was approved by CEN on 8 December 2019 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16614-1:2020 E
worldwide for CEN national Members.

Contents Page
European foreword . 6
1 Scope . 8
1.1 General . 8
1.2 Transport modes . 8
1.3 Compatibility with existing standards and recommendations . 8
2 Normative references . 8
3 Terms and definitions . 9
4 Symbols and abbreviations . 63
5 Use Cases for Network Topology Exchange . 65
5.1 Purpose . 65
5.2 Actors and Use Case Types . 65
5.2.1 Actors . 65
5.2.2 Delivery Use Cases . 66
5.2.3 Content Use Cases . 67
5.2.4 Object Lifecycle Support Use Cases . 69
5.2.5 Security Use Cases . 69
5.2.6 Excluded Use Cases . 69
5.3 Use Cases . 70
5.3.1 Requirements Table . 70
5.3.2 Collection of Use Cases . 77
6 Generic Physical Model and XSD mapping rules . 110
6.1 Introduction . 110
6.2 Model Driven Design . 110
6.3 Models – levels of abstraction. . 111
6.4 Open Implementation and technology use . 112
6.5 Models versus Protocols . 113
6.6 Modularisation . 113
6.7 Summary of Modelling Approach . 114
6.7.1 General . 114
6.7.2 Use of packages in NeTEx models . 115
6.8 Model transforms and Traceability . 116
6.8.1 General . 116
6.8.2 Conceptual Model UML Package . 116
6.8.3 Physical Model UML Container Packages and Mapping from Conceptual model . 116
6.8.4 XSD Model subschemas and Mapping from Physical model . 117
6.8.5 Summary of Basic Mapping . 117
6.9 Physical model to XSD schema mapping notes . 118
6.10 Uniqueness of reference and Namespaces . 119
6.11 Handling of inheritance . 119
6.12 NeTEx Notation, presentation and naming conventions . 119
6.12.1 General . 119
6.12.2 Presentation of Element Names . 120
6.12.3 Presentation of Data Type Names . 120
6.12.4 Naming conventions . 120
6.12.5 Presentation of UML Diagrams . 121
6.12.6 Use of Stereotypes . 122
6.12.7 Use of Colour . 122
6.13 Mapping between models in NeTEx . 122
6.13.1 Common Design Patterns in NeTEx . 122
6.13.2 Mapping Example – Thing Model . 123
6.13.3 Mapping Example – Handling Inheritance the SubThing Model . 131
7 NeTEx Framework - Conceptual and Physical data model . 136
7.1 Introduction. 136
7.2 Implementing Transmodel framework features in NeTEx . 137
7.3 Versions & Validity . 138
7.3.1 Introduction. 138
7.3.2 Version & Validity – Model Dependencies . 138
7.3.3 Generic Entity . 139
7.3.4 Generic Version . 149
7.3.5 Implementing relationships in NeTEx . 163
7.3.6 Generic Version Frame . 169
7.3.7 Generic Validity . 191
7.4 Responsibility . 199
7.4.1 Introduction. 199
7.4.2 Responsibility – Model Dependencies . 200
7.4.3 Generic Responsibility . 201
7.4.4 Responsibility Role . 215
7.4.5 AlternativeText . 223
7.4.6 Alternative Name . 226
7.4.7 Generic Organisation . 230
7.5 Generic Frames . 247
7.5.1 Composite Frame . 248
7.5.2 General Frame . 249
7.6 Generic Framework Model . 251
7.6.1 Generic Framework – Model Dependencies . 252
7.6.2 Unit & Utility Base Types .
...