FprCEN/TS 16614-1

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

16614 (NeTEx) is composed of a series of standards:
-   Part 1: Description of the public transport network topology exchange format.
-   Part 2: Description of the scheduled timetables exchange format.
-   Part 3: Description of the fare information exchange format.
-   Part 4: Description of the passenger information European profile (EPIP).
-   Part 5: Description of the alternative modes exchange format.
-   Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 1.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
-   Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
-   Physical layout of compound vehicles (e.g. train composition),
-   Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.

Ö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: Not Published
• Publication Date: 04-Mar-2026
• Technical Committee: CEN/TC 278 - Road transport and traffic telematics
• Drafting Committee: CEN/TC 278/WG 3 - Public transport (PT)
• Current Stage: 5020 - Submission to Vote - Formal Approval
• Start Date: 16-Oct-2025
• Due Date: 09-Sep-2025
• Completion Date: 16-Oct-2025
• 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)
• Ref Project: kSIST-TS FprCEN/TS 16614-1:2025 - Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport network topology exchange format

Relations

• Revises: CEN/TS 16614-1:2020 - Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport network topology exchange format
• Effective Date: 19-Jun-2024

Standards Content (Sample)

SLOVENSKI STANDARD
01-december-2025
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: FprCEN/TS 16614-1
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.

FINAL DRAFT
TECHNICAL SPECIFICATION
FprCEN/TS 16641-1
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
October 2025
ICS Will supersede CEN/TS 16614-1:2020
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 draft Technical Specification is submitted to CEN members for Vote. It has been drawn up by the Technical Committee
CEN/TC 278.
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, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.

Warning : This document is not a Technical Specification. It is distributed for review and comments. It is subject to change
without notice and shall not be referred to as a Technical Specification.

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
© 2025 CEN All rights of exploitation in any form and by any means reserved Ref. No. FprCEN/TS 16641-1:2025 E
worldwide for CEN national Members.

Contents Page
European foreword . 7
1 Scope . 9
1.1 General . 9
1.2 Transport modes . 9
1.3 Compatibility with existing standards and recommendations . 9
2 Normative references . 10
3 Terms and definitions . 10
4 Symbols and abbreviations . 73
5 Use Cases for Network Topology Exchange . 75
5.1 Purpose . 75
5.2 Actors and Use Case Types . 75
5.2.1 Actors . 75
5.2.2 Delivery Use Cases . 76
5.2.3 Content Use Cases . 77
5.2.4 Object Lifecycle Support Use Cases . 79
5.2.5 Security Use Cases . 79
5.2.6 Excluded Use Cases . 79
5.3 Use Cases . 80
5.3.1 Requirements Table . 80
5.3.2 Collection of Use Cases . 87
6 Generic Physical Model and XSD mapping rules . 120
6.1 Introduction . 120
6.2 Model Driven Design . 120
6.3 Models – levels of abstraction. . 121
6.4 Open Implementation and technology use . 122
6.5 Models versus Protocols . 123
6.6 Modularisation . 123
6.7 Summary of Modelling Approach . 124
6.7.1 General . 124
6.7.2 Use of packages in NeTEx models . 125
6.8 Model transforms and Traceability . 126
6.8.1 General . 126
6.8.2 Conceptual Model UML Package . 126
6.8.3 Physical Model UML Container Packages and Mapping from Conceptual model . 126
6.8.4 XSD Model subschemas and Mapping from Physical model . 127
6.8.5 Summary of Basic Mapping . 127
6.9 Physical model to XSD schema mapping notes . 128
6.10 Uniqueness of reference and Namespaces . 129
6.11 Handling of inheritance . 129
6.12 NeTEx Notation, presentation and naming conventions . 129
6.12.1 General . 129
6.12.2 Presentation of Element Names . 129
6.12.3 Presentation of Data Type Names . 130
6.12.4 Naming conventions . 130
6.12.5 Presentation of UML Diagrams . 131
6.12.6 Use of Stereotypes . 132
6.12.7 Use of Colour . 132
6.13 Mapping between models in NeTEx . 132
6.13.1 Common Design Patterns in NeTEx . 132
6.13.2 Mapping Example – Thing Model . 132
6.13.3 Mapping Example – Handling Inheritance the SubThing Model . 140
7 NeTEx Framework - Conceptual and Physical data model . 145
7.1 Introduction. 145
7.2 Implementing Transmodel framework features in NeTEx . 149
7.3 Versions & Validity . 149
7.3.1 Introduction. 149
7.3.2 Version & Validity – Model Dependencies . 150
7.3.3 Generic Entity . 150
7.3.4 Generic Version . 159
7.3.5 Implementing relationships in NeTEx . 171
7.3.6 Generic Version Frame . 177
7.3.7 Generic Validity . 198
7.4 Responsibility . 206
7.4.1 Introduction. 206
7.4.2 Responsibility – Model Dependencies . 207
7.4.3 Generic ResponsibilityGeneric RESPONSIBILITY – Conceptual MODEL . 207
7.4.4 Responsibility Role . 221
7.4.5 AlternativeText . 231
7.5 Data Source . 234
7.5.1 DATA SOURCE – Physical Model . 234
7.5.2 Data Source – Attributes and XSD . 235
7.5.3 Alternative Name . 236
7.6 Generic Organisation . 240
7.6.2 Generic ORGANISATION – Conceptual MODEL . 240
7.6.3 Generic Organisation – Physical Model . 241
7.6.4 Organisation – Attributes and XSD . 245
7.7 Generic Frames . 263
7.7.1 Composite Frame . 263
7.7.2 General Frame . 265
7.8 Generic Framework Model . 268
7.8.1 Generic Framework – Model Dependencies . 268
7.8.2 Unit & Utility Base Types . 269
7.8.3 Location . 284
7.8.4 Generic Grouping . 288
7.8.5 Generic Point & Link . 296
7.8.6 Generic Section . 306
7.8.7 Generic Point & Link Sequence . 312
7.8.8 Generic Zone and Feature . 318
7.8.9 Generic Path & Navigation . 328
7.8.10 Generic Layer . 337
7.8.11 Generic Projection . 340
7.8.12 Generic Place . 358
7.8.13 Generic Assignment . 365
7.8.14 Generic Loggable . 367
7.8.15 Generic Security List . 370
8 Reusable Component Models . 376
8.1.1 Reusable Components – Model Dependencies . 376
8.1.2 Resource Frame . 378
8.2 Reusable Time Element Models . 383
8.2.1 Service Calendar . 383
8.2.2 Availability Condition . 404
8.3 Reusable Mode Models . 409
8.3.1 Transport Mode . 409
8.3.2 Transport Submode . 415
8.3.3 Modes and Modes of Operation . 420
8.4 Reusable Place and Organisation Models. 431
8.4.1 Topographic Place . 431
8.4.2 Transport Organisation . 447
8.4.3 Additional Organisations . 460
8.5 Reusable Vehicle Type Models . 466
8.5.1 Vehicle Type . 466
8.5.2 Vehicle Type Classifications . 485
8.5.3 Service Requirements. 489
8.5.4 Fleet Equipment Profile . 494
8.5.5 Recharging Equipment Profile . 500
8.5.6 Train Type . 504
8.5.7 Train Element Type . 517
8.5.8 Deck Plan . 523
8.5.9 Deck Path . 552
8.5.10 Seating Plan . 564
8.5.11 Seat Affinity . 574
8.6 Reusable Vehicle Models . 577
8.6.1 Vehicle . 577
8.6.2 Fleet . 585
8.6.3 Train Composition . 589
8.7 Reusable Equipment Models . 590
8.7.1 Facility . 590
8.7.2 Generic Equipment . 627
8.7.3 Actual Vehicle Equipment . 643
8.7.4 Vehicle Passenger Equipment . 645
8.7.5 Energy Equipment . 651
8.7.6 Spot Equipment . 658
8.7.7 DeckSensor Equipment . 664
8.8 Reusable Message Models . 668
8.8.1 Notice . 668
8.8.2 Notice Assignment . 675
8.9 Reusable General Element Models. 680
8.9.1 Service Restrictions . 680
8.9.2 Booking Arrangements . 687
8.9.3 Environmental Properties . 693
8.9.4 Accessibility . 705
8.9.5 Schematic Map . 723
8.9.6 Check Constraint . 730
9 Part 1 – The Network Topology . 739
9.1 Network Description – Model dependencies . 740
9.2 Network Description – Version Frarmes . 741
9.2.1 Infrastructure Frame . 741
9.2.2 Service Frame . 745
9.3 Network Description – Subsystem. 749
9.3.1 Network Infrastructure . 749
9.3.2 Activation. 769
9.3.3 Vehicle & Crew Point . 775
9.3.4 Lines and Routes . 781
9.3.5 Line Network . 815
9.3.6 Timing Pattern . 822
9.3.7 Flexible Network . 832
9.4 Fixed Objects – Subsystem . 845
9.4.1 Fixed Objects – Model Dependencies. 845
9.4.2 Site Frame . 846
9.4.3 Site . 851
9.4.4 Site Paths . 876
9.4.5 Navigation Path . 888
9.4.6 Stop Place. 909
9.4.7 Flexible Stop Place . 943
9.4.8 Taxi Place . 950
9.4.9 Point Of Interest . 955
9.4.10 Parking . 968
9.4.11 Vehicle Stopping . 992
9.4.12 Associating Equipment with Places . 1000
9.4.13 Equipment Description. 1001
9.4.14 Accessibility Coverage . 1100
9.4.15 Accessibility Coverage of Paths . 1101
9.4.16 Recharging Point Assignment . 1102
9.5 Tactical Planning Components – Subsystem . 1105
9.5.1 Tactical Planning – Model Dependencies . 1105
9.5.2 Connections & Transfer times . 1106
9.5.3 Journey Pattern . 1120
9.5.4 Service Pattern . 1134
9.5.5 Common Section . 1159
9.5.6 Routing Constraints . 1162
9.5.7 Time Demand Type . 1168
9.5.8 Passenger Stop Assignment . 1175
9.5.9 Path Assignment . 1188
9.5.10 Passenger Information Equipment . 1191
10 NeTEx Service Interface . 1200
10.1 Introduction. 1200
10.2 Protocols versus payload . 1200
10.3 NeTEx Publication XSD schema . 1201
10.3.1 NeTEx Publication Delivery – Physical Model . 1201
10.3.2 Publication Delivery – Attributes and XSD . 1206
10.3.3 XML Examples of Publications . 1212
10.4 NeTEx SIRI-NX services XSD schema . 1213
10.4.1 Brief overview of SIRI communication layer . 1214
10.4.2 SIRI ServiceRequest wrapper . 1216
10.4.3 SIRI ServiceDelivery . 1218
10.4.4 Data Object Service [SIRI-NX] . 1221
10.5 Use of NeTEx with SOAP / WSDL . 1227
10.5.1 Web Services . 1227
10.5.2 SOAP (Simple Object Access Protocol) . 1227
10.5.3 WSDL (Web Services Definition Language) . 1227
10.5.4 NeTEx WSDL . 1228
Annex A (informative) Mapping with existing standards . 1230
A.1 Introduction . 1230
A.2 VDV 452 Mapping . 1234
A.3 NOPTIS Mapping . 1234
A.4 NEPTUNE (Trident /Chouette profile) . 1235
A.4.1 Foreword . 1235
A.4.2 NEPTUNE . 1235
A.4.3 NEPTUNE to NeTEx mapping information . 1236
A.5 ERA mapping . 1237
A.5.1 Foreword . 1237
A.5.2 Explanation of the mapping . 1238
A.5.2.1 Structure of mapping excel-file . 1238
A.5.2.2 Hierarchy of EDIFACT . 1238
A.5.2.2.1 Explanation of the mapping . 1238
A.5.3 Limitations . 1239
A.6 TransXChange, NaPTAN & NPTG mappings . 1240
A.6.1 Foreword . 1240
A.6.2 TransXChange to NeTEx mapping information . 1240
Annex B (informative) Advisory . 1241
B.1 Introduction . 1241
B.2 Train Composition . 1241
B.2.1 TRAIN COMPOSITION – Conceptual MODEL . 1241
B.2.2 TrainComposition – Physical Model . 1242
B.2.3 TrainComposition – Attributes and XSD . 1243
B.2.3.1 TrainComposition – Model Element . 1243
B.2.3.2 TrainCompositionComponent – Model Element . 1244
B.2.3.3 TrainCompositionCoupling – Model Element . 1244
B.2.3.4 CompoundTrainComposition – Model Element . 1244
B.2.3.5 CompositionInCompoundTrainComposition – Model Element. 1245
Annex C (informative) Summary of Changes . 1246
C.1.1 Introduction . 1246
C.2 General Changes . 1246
C.2.1 Part1 – Changes to Reusable Components . 1247
C.2.2 Part1 – Changes to Network Description . 1247
C.2.3 Part1 – Changes to Fixed Objects . 1248
C.1 Changes for NeTEx 2.0 . 1249
Bibliography . 1256

European foreword
This document (FprCEN/TS 16614-1:2025) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.

This document is currently submitted to the Vote on TS.

This document will supersede CEN/TS 16614-1:2019.

This document presents Part 1 of the Technical Specification known as “NeTEx”. NeTEx provides a
framework for specifying communications and data exchange protocols for organisations wishing to
exchange scheduled Information relating to public transport operations. As defined by Transmodel,
'Public transport' has to be understood as services advertised and available for use by the general public
carried out by any means of transport.

This Technical Specification is made up of six parts defining a single European Standard series, which
provides a complete exchange format for public transport networks, timetable description and fare
information.
⎯ Part 1 is the description of the public transport network topology exchange format. It also
contains use cases shared with part 2, and modelling rules and the description of a framework
shared by all parts.
⎯ Part 2 is the description of the scheduled timetables exchange format.
⎯ Part 3 is the description of the fare information exchange format.
⎯ Part 4 is the European profile for exchanging timetables with the netex data exchange format.
⎯ Part 5 is the description of the alternative transport modes data exchange format.
⎯ Part 6 is the description of the European passenger information accessibility profile.

Part 1 is fully standalone, and Parts 2, 3, 4, 5 and 6 rely on Part 1 and possibly any other previous part.

The XML schema can be downloaded from https://github.com/NeTEx-CEN/NeTEx and additional
information are available from http://netex-cen.eu, along with available guidance on its use, example
XML files, and case studies of national and local deployments.

This document is highly technical, and a special care has been taken to keep the text readable. In
particular a set of formatting conventions is followed that enhances the usual CEN writing rules in order
to distinguish references to elements of the formal models within text:
⎯ Transmodel terms and NeTEx conceptual model elements are in capital letters (JOURNEY
PATTERN for example).
⎯ NeTEx physical model names are in bold italic font and use CamelCase style with no spaces
(JourneyPattern, for example).
⎯ NeTEx physical model attribute types are in italic font and use CamelCase style with no spaces
(TypeOfEntity, for example).
Introduction
Public transport services rely increasingly on information systems to ensure reliable, efficient operation
and widely accessible, accurate passenger information. These systems are used for a range of specific
purposes: setting schedules and timetables; managing vehicle fleets; issuing tickets and receipts;
providing real-time information on service running, and so on.

This document specifies a Network and Timetable Exchange (NeTEx) standard for Public Transport (PT).
It is intended to be used to exchange data relating to scheduled public transport between the systems of
PT organisations. It can also be seen as complementary to the SIRI (Service Interface for Real-time
Information) standard, as SIRI needs a prior exchange of reference data from NeTEx’s scope to provide
the necessary context for the subsequent exchange of real-time data.

Well-defined and open interfaces have a crucial role in improving the economic and technical viability of
Public Transport Information Systems of all kinds. Using standardized interfaces, systems can be
implemented as discrete pluggable modules that can be chosen from a wide variety of suppliers in a
competitive market, rather than as monolithic proprietary systems from a single supplier. Interfaces also
allow the systematic automated testing of each functional module, vital for managing the complexity of
increasing large and dynamic systems. Furthermore, individual functional modules can be replaced or
evolved, without unexpected breakages of obscurely dependent function.

This document will improve a number of
...