CEN/TS 16614-3:2020
(Main)Public transport - Network and Timetable Exchange (NeTEx) - Part 3: Public transport fares exchange format
Public transport - Network and Timetable Exchange (NeTEx) - Part 3: Public transport fares exchange format
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.
Öffentlicher Verkehr - Netzwerk- und Fahrplan Austausch (NeTEx) - Teil 3: Austauschformat für das Fahrgeld im öffentlichen Verkehr
Transport Public - Echanges des informations planifiées (NeTEx) - Partie 3: Echange des informations tarifaires pour le transport public
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 3. del: Format za izmenjavo informacij o vozovnicah
General Information
- Status
- Published
- Publication Date
- 14-Apr-2020
- Technical Committee
- CEN/TC 278 - Road transport and traffic telematics
- Drafting Committee
- CEN/TC 278/WG 3 - Public transport (PT)
- Current Stage
- 9092 - Decision on results of review/2YR ENQ - revise - Review Enquiry
- Start Date
- 11-Jun-2024
- Completion Date
- 14-Apr-2025
Relations
- Effective Date
- 22-Apr-2020
- Effective Date
- 19-Jun-2024
Overview - CEN/TS 16614-3:2020 (NeTEx Part 3)
CEN/TS 16614-3:2020 defines the NeTEx public transport fares exchange format used to exchange structured fare information between systems. Part 3 of NeTEx extends the network and timetable models in Parts 1 & 2 to describe fare structures, fare products, sales offers and the metadata needed to present fares to passengers and to integrate fares with journey planning and AVMS (Automated Vehicle Monitoring Systems). NeTEx Part 3 is based on and refines Transmodel V5.1, IFOPT and SIRI to provide a consistent XML/XSD mapping for scheduled transport and fares.
Key topics and technical requirements
- Fare model and data scope: supports flat, zonal, distance-based, time-dependent, stage, PAYG, season passes and other fare structures.
- Fare products and conditions: models the attributes, eligibility rules and complex conditions (temporal, user-group, concession rules) attached to fare products.
- Pricing vs. price data: allows exchange of price parameters and actual prices but does not define pricing algorithms-Fare Management Systems handle calculation logic.
- Sales and retail metadata: describes sales channels, travel documents, sales offers and retail packages to enable integration with front‑end retail and passenger information systems.
- Validation & control elements: includes elements to represent what can be validated or controlled (e.g., tickets, access rights).
- Technical artifacts: conceptual and physical data models, XSD mapping rules, version frames and guidance for mapping to other frameworks (e.g., TAP TSI).
- Coverage of modes: applicable to rail, bus, coach, metro, tram, ferry (and potential airport/airfare description).
Practical applications and users
Who benefits:
- Public transport authorities and regional fare planners - to exchange and harmonize fare rules across operators or regions.
- IT vendors and system integrators - for building journey planners, passenger information systems, AVMS and fare management integrations.
- Ticketing and retail platforms - to ingest standardized fare offers and sales metadata (upstream data feed).
- Mobility-as-a-Service (MaaS) providers and aggregators - to combine network, timetable and fare data for multimodal journey offers.
Practical uses:
- Sharing complete fare catalogs between agencies and third‑party trip planners.
- Publishing fare conditions and price data in customer-facing apps.
- Feeding fare attributes into journey planners to compute best-value itineraries (pricing logic remains with fare engines).
Related standards
- Transmodel V5.1 (EN 12986) - conceptual public transport data model.
- IFOPT (EN 28701) - identification of public transport access points.
- SIRI (CEN/TS 15531 / EN 15531) - real-time information exchange.
- NeTEx Parts 1 & 2 - network topology and timetable exchange formats.
- TAP-TSI mapping guidance included in the standard’s annexes.
CEN/TS 16614-3:2020 is a practical, interoperable specification for organizations exchanging structured fare information to support passenger information, journey planning and operational systems.
Frequently Asked Questions
CEN/TS 16614-3:2020 is a technical specification published by the European Committee for Standardization (CEN). Its full title is "Public transport - Network and Timetable Exchange (NeTEx) - Part 3: Public transport fares exchange format". This standard covers: 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.
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.
CEN/TS 16614-3:2020 is classified under the following ICS (International Classification for Standards) categories: 35.240.60 - IT applications in transport. The ICS classification helps identify the subject area and facilitates finding related standards.
CEN/TS 16614-3:2020 has the following relationships with other standards: It is inter standard links to CEN/TS 16614-3:2016, FprCEN/TS 16614-3. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
CEN/TS 16614-3:2020 is associated with the following European legislation: EU Directives/Regulations: 2010/40/EU, 2016/797/EU; Standardization Mandates: M/453, M/456. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
You can purchase CEN/TS 16614-3:2020 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of CEN standards.
Standards Content (Sample)
SLOVENSKI STANDARD
01-junij-2020
Nadomešča:
SIST-TS CEN/TS 16614-3:2016
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 3. del:
Format za izmenjavo informacij o vozovnicah
Public transport - Network and Timetable Exchange (NeTEx) - Part 3: Public transport
fares exchange format
Öffentlicher Verkehr - Netzwerk- und Fahrplan Austausch (NeTEx) - Teil 3:
Austauschformat für das Fahrgeld im öffentlichen Verkehr
Transport public - Echange des données de réseau et d'horaires (NeTEx) - Partie 3 :
Format d'échange d'informations voyageurs concernant le réseau de transport public
Ta slovenski standard je istoveten z: CEN/TS 16614-3: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-3
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
April 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.60 Supersedes CEN/TS 16614-3:2016
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Part 3: Public transport fares exchange format
Transport Public - Echanges des informations Öffentlicher Verkehr - Netzwerk- und Fahrplan
planifiées (NeTEx) - Partie 3: Echange des informations Austausch (NeTEx) - Teil 3: Austauschformat für das
tarifaires pour le transport public Fahrgeld im öffentlichen Verkehr
This Technical Specification (CEN/TS) was approved by CEN on 2 March 2020 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-3:2020 E
worldwide for CEN national Members.
CEN/TS 16614-3
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
April 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.60 Supersedes CEN/TS 16614-3:2016
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Part 3: Public transport fares exchange format
Transport Public - Echanges des informations Öffentlicher Verkehr - Netzwerk- und Fahrplan
planifiées (NeTEx) - Partie 3: Echange des informations Austausch (NeTEx) - Teil 3: Austauschformat für das
tarifaires pour le transport public Fahrgeld im öffentlichen Verkehr
This Technical Specification (CEN/TS) was approved by CEN on 2 March 2020 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-3:2020 E
worldwide for CEN national Members.
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
1.1 General . 6
1.2 Fares scope . 6
1.3 Transport modes . 7
1.4 Compatibility with existing standards and recommendations . 7
2 Normative references . 7
3 Terms and definitions . 8
4 Symbols and abbreviations . 27
5 Use Cases for Fare Exchange . 28
5.1 Purpose . 28
5.2 Business context . 28
5.2.1 Fare planning process . 28
5.3 Actors and use case types . 33
5.3.1 Use Cases for Fare Policy . 36
5.3.2 Use Cases for Organisation of Fare Policy Usage . 36
5.4 Excluded Use Cases . 37
5.5 Use Cases . 37
5.5.1 Collection of Use Cases . 37
6 Generic Physical Model and XSD mapping rules . 64
7 Public Transport Fares – Conceptual and physical data model . 64
7.1 Introduction . 64
7.2 Conceptual Model overview . 64
7.2.1 Functional Domains . 64
7.2.2 Data Model Overview . 66
7.2.3 Main Concepts . 68
7.3 Fare Model dependencies . 72
7.3.1 NeTEx Part3 Use of Version Frames . 74
7.3.2 Fare Frame . 75
7.4 Reusable Fare Components . 92
7.4.1 Fare Zone . 92
7.4.2 Fare Facility . 111
7.4.3 Vehicle Seating . 114
7.5 Fare Structure . 115
7.5.1 Fare Structure – Model dependencies . 115
7.5.2 Common Fare Structure . 116
7.5.3 Geographical Fare Structure. 123
7.5.4 Time Fare Structure . 132
7.5.5 Quality Fare Structure . 140
7.5.6 Fare Structure Element . 150
7.5.7 Distance Matrix Element . 178
7.5.8 Validable & Controllable Elements . 189
7.6 Access Rights Description . 200
7.6.1 Access Right Parameters . 200
7.6.2 Fare Product . 338
7.7 Pricing . 383
7.7.1 Fare Calculation Parameters . 383
7.7.2 Fare Price . 398
7.7.3 Fare Table . 411
7.8 Sales Description . 436
7.8.1 Fare Sales Distribution . 436
7.8.2 Type of Travel Document . 447
7.8.3 Sales Offer Package . 451
8 Sales Transactions . 477
8.1 Sales Transaction – Model dependencies . 477
8.1.1 Sales Transaction Frame . 478
8.1.2 Fare Contract . 482
8.1.3 Customer Eligibility . 498
8.1.4 Retail . 502
8.1.5 Sales Transaction . 508
8.1.6 Travel Specification . 519
8.1.7 Customer Purchase Package . 533
Annex A (normative) Extensions to NeTEx Part1 & 2 . 551
Annex B (informative) ERA – TAP TSI annexes B1, B2 and B3 mapping . 552
B.1 Summary of mapping of B1 (NRT) fares . 552
.2 Summary of mapping of B2 (IRT) fares . 552
B
B.3 Summary of mapping of B3 (Special) fares . 553
Annex C (informative) NeTEx Passenger Information Query model . 554
C.1 PiRequest . 554
C.1.1 PI Request dependencies . 554
C.1.2 Pi Request . 556
Annex D (informative) How to go from a trip (from NeTEx Part1&2) to a fare ?. 594
D.1 Passenger Trip . 594
D.1.1 Passenger Trip Model . 594
D.1.2 Passenger Fare Offer Model . 603
Annex E (informative) Proposed model for Parking Tariff . 608
E.1 Parking Tariff . 608
E.1.1 Parking Tariff – Conceptual MODEL . 608
Annex F (informative) Changes in Version 1.1 . 615
F.1 Introduction . 615
F.2 General Changes . 615
F.3 List of Changes . 615
Bibliography . 621
European foreword
This document (CEN/TS 16614-3:2020) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes CEN/TS 16614-3:2016.
This document presents Part 3 of the European Technical Specification known as “NeTEx”. NeTEx
provides a framework for specifying communications and data exchange protocols for
organisations wishing to exchange scheduled Information relating to public transport operations.
This Technical Specification is made up of three 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 1 is fully standalone, and part 2 and 3 rely on part 1.
The XML schema can be downloaded 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 style and use camelcase style with no spaces
(TypeOfEntity for example).
According to the CEN/CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to announce this document: 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 the United Kingdom.
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; publicising fares, issuing tickets
and receipts; providing real-time information on service running, and so on.
The first two parts of the European Technical Specification NeTEx specify a Network and Timetable
Exchange for Public Transport. 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 a real-time data.
This document (NeTEx – Part 3) specifies exchanges of Public Transport fares between systems and
organisations. It is a complement to Part 1 and Part 2 in the sense that it uses a subset of concepts
defined there.
Well-defined, open interfaces have a crucial role in improving the economic and technical viability of
Public Transport Information Systems of all kinds. Using standardised 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 standard will improve a number of features of public transport information and service
management: Interoperability – the standard will facilitate interoperability between information
processing systems of the transport operators by: (i) introducing common architectures for message
exchange; (ii) introducing a modular set of compatible information services, (iii) using common data
models and schemas for the messages exchanged for each service; and (iv) introducing a consistent
approach to data management.
Technical advantages include the following: a modular reusing of a common communication layer
shared with SIRI for all the various technical services enables cost-effective implementations, and
makes the standard readily extensible in future.
1 Scope
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 Part 3 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 Part 1 and Part 2 and
the Fare Collection data model defined in Transmodel V51. See the use cases below for the overall scope
of Part 3. 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.
Under preparation.
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.
1.4 Compatibility with existing standards and recommendations
The overall approach for the definition of fares within NeTEx Part 3 follows the approach used by
Transmodel V5.1, namely the definition of access rights rather than of just products.
This approach, used in Transmodel V5.1 (Fare Collection data model) to specify the access rights related
to the urban public transport (for all urban modes) has been extended to cover access rights for long-
distance rail.
NOTE The concepts from Transmodel V5.1 and IFOPT used and/or modified by NeTEx are incorporated into
Transmodel V6 to guarantee compatibility and coherence of standards.
Concepts covered in NeTEx Part 1 and 2 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
and train routing restrictions.
In the case of long distance train access rights, 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. These relate in particular to the B1 (Non Reservation Tickets),
B2 (Integrated Reservation Tickets) and B3 (Special Fares) along with various UIC Leaflets.
As regards the other exchange protocols for network and timetable exchanges, a formal compatibility is
ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), BISON (The Netherlands)
and NOPTIS (Nordic Public Transport Interface Standard).
The exchange of data in NeTEx format can be undertaken using a variety of protocols. For example:
through dedicated web services, through data file exchanges, or by using the SIRI exchange protocol as
described in part 2 of the SIRI documentation. NeTEx adds additional services using the common SIRI
transport mechanism.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
CEN/TS 16614-1, Public transport — Network and Timetable Exchange (NeTEx) — Part 1: Public
transport network topology exchange format
3 Terms and definitions
For the purposes of this document, the terms and definitions given in CEN/TS 16614-1:2019 and the
following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• ISO Online browsing platform: available at https://www.iso.org/obp
• IEC Electropedia: available at http://www.electropedia.org/
NOTE A lot of definitions are shared with Transmodel (EN 12896): special attention was paid to the
consistency of definitions, keeping exactly the same wording. The italic bracket name at the beginning of the
definition is a package name that will help the reader to find the related concept in the UML data model.
3.1
access right in product
(Fare Product MODEL)
VALIDABLE ELEMENT as a part of a PRE-ASSIGNED FARE PRODUCT, including its possible order in the
set of all VALIDABLE ELEMENTs grouped together to define the access right assigned to that PRE-
ASSIGNED FARE PRODUCT
3.2
access right parameter assignment
(Validity Parameters MODEL)
assignment of a fare collection parameter (referring to geography, time, quality or usage) to an element
of a fare system (access right, validated access, control mean, etc.)
3.3
amount of price unit
(Fare Product MODEL)
FARE PRODUCT consisting in a stored value of PRICE UNITs: an amount of money on an electronic
purse, amount of units on a value card etc.
3.4
blacklist
(Fare Contract MODEL)
list of identified TRAVEL DOCUMENTs or CONTRACTs the validity of which has been cancelled
temporarily or permanently, for a specific reason like loss of the document, technical malfunction, no
credit on bank account, offences committed by the customer, etc.
3.5
border point
(Fare Zone MODEL)
POINT on the Network marking a boundary for the fare calculation
Note 1 to entry: May or may not be a SCHEDULED STOP POINT
3.6
cancelling
(Cancelling Usage Parameters MODEL)
Parameter giving conditions for cancelling of a purchased access right
3.7
capped discount right
(Fare Product MODEL)
specialisation of SALE DISCOUNT RIGHT where the discount is expressed as a rule specifying a ceiling for a given
time interval
Note 1 to entry: For example, the London Oyster card fare, which charges for each journey until travel equivalent
to a day pass has been consumed after which further travel is free at that day
3.8
capping rule
(Fare Product MODEL)
capping limit for a given time interval, where the capping is expressed by another product
Note 1 to entry: For example, the London Oyster card fare, which charges for each journey until travel equivalent
to a day pass for the mode of travel has been consumed
3.9
capping rule price
(Fare Product MODEL)
set of all possible price features of a CAPPING RULE: default total price, discount in value or percentage
etc.
3.10
cell
(Fare Table MODEL)
unique individual combination of features within a FARE TABLE, used to associate a FARE PRICE with a
fare element
3.11
charging moment
(Fare Product MODEL)
classification of FARE PRODUCTs according to the payment method and the account location: pre-
payment with cancellation (throw-away), pre-payment with debit on a value card, pre-payment without
consumption registration (pass), post-payment etc.
3.12
charging policy
(Charging Usage Parameters MODEL)
Parameter governing minimum amount and credit allowed when consuming a FARE PRODUCT
3.13
commercial profile
(Eligibility Usage Parameters MODEL)
category of users depending on their commercial relations with the operator (frequency of use, amount
of purchase etc.), often used for allowing discounts
3.14
companion profile
(Eligibility Usage Parameters MODEL)
number and characteristics of the persons entitled to travel in a group or as companions to another
USER PROFILE
3.15
controllable element
(Validable Element MODEL)
smallest controllable element of public transport consumption, all along which any VALIDITY
PARAMETER ASSIGNMENT remains valid
3.16
controllable element in sequence
(Validable Element MODEL)
CONTROLLABLE ELEMENT as a part of a FARE STRUCTURE ELEMENT, including its possible order in
the sequence of CONTROLLABLE ELEMENTs grouped together to form that FARE STRUCTURE
ELEMENT, and its possible quantitative limitation
3.17
controllable element price
(Validable Element MODEL)
set of all possible price features of a CONTROLLABLE ELEMENT: default total price, discount in value or
percentage etc.
3.18
customer
(Fare Contract MODEL)
identified person or organisation involved in a fare process
Note 1 to entry: There may be a CONTRACT between the CUSTOMER and the OPERATOR or the AUTHORITY ruling
the consumption of services
3.19
discounting rule
(Fare Calculation Parameters MODEL)
price calculation rule determined by a set of discounts, depending upon a USAGE PARAMETER, to be
applied to a FARE PRICE
3.20
distance matrix element
(Distance Matrix Element MODEL)
cell of an origin-destination matrix for TARIFF ZONEs or STOP POINTs, expressing a fare distance for
the corresponding trip: value in km, number of fare units etc.
3.21
distance matrix element price
(Distance Matrix Element MODEL)
set of all possible price features of a DISTANCE MATRIX ELEMENT: default total price etc.
3.22
distribution assignment
(Sales Offer Package MODEL)
assignment of the COUNTRY and/or DISTRIBUTION CHANNEL through which a product may or may not
be distributed
3.23
distribution channel
(Sales Distribution MODEL)
type of outlet for selling of a product
3.24
eligibility
(Use Case)
required characteristics of a customer to be able to purchase a product
3.25
eligibility change policy
(Eligibility Parameters MODEL)
Parameter indicating the action to be taken when a user’s eligibility status changes
3.26
entitlement constraint
(Entitlement Parameters MODEL)
Constraints on choices for an dependent entitled product relative to the required choices for the
prerequisite entitling product
3.27
entitlement given
(Entitlement Parameters MODEL)
Parameter indicating whether a particular FARE PRODUCT provides an entitlement to buy or use an
access right
3.28
entitlement product
(Fare Product MODEL)
precondition to access a service or to purchase a FARE PRODUCT issued by an organisation that may not be a PT
operator (e.g.military card)
3.29
entitlement required
(Entitlement Parameters MODEL)
Parameter indicating whether a particular FARE PRODUCT requires an entitlement to by or use an
access right
3.30
exchanging
(Booking Usage Parameters MODEL)
Whether and how the access right may be exchanged for another access right
3.31
fare
(Use Case)
From the customer perspective: the amount that a customer has to pay for a journey or for acquiring a
product
3.32
fare day type
(Fare Calculation Parameters MODEL)
type of day used in the fare collection domain, characterised by one or more properties which affect the
definition of access rights and prices in the fare system
3.33
fare demand factor
(Quality Fare Structure MODEL)
named set of parameters defining a period of travel with a given price, for example off peak, peak, super
off peak, etc.
3.34
fare element in sequence
(Common Fare Structure MODEL)
FARE ELEMENT as a part of an ELEMENT, including its possible order in the sequence of FARE
ELEMENTs
3.35
fare frame
(Fare Frame MODEL)
set of all fare data defined for a specific VEHICLE MODE to which the same VALIDITY CONDITIONs have
been assigned
3.36
fare frame defaults
(Fare Frame MODEL)
Set of pricing parameters and values to apply to an individual element in the frame if no explicit value is
specified on the element
3.37
fare interval
(Common Fare Structure MODEL)
interval based aspect of the fare structure
3.38
fare point in pattern
(Fare Zone MODEL)
POINT IN PATTERN which represents the start or end of a FARE SECTION, or a point used to define a
SERIES CONSTRAINT
3.39
fare price
(Fare Price MODEL)
Price features DEFINED BY DEFAULT characterizing different PRICE GROUPs
3.40
fare product
(Fare Product MODEL)
immaterial marketable element (access rights, discount rights, etc.), specific to a CHARGING MOMENT
3.41
fare product price
(Fare Product MODEL)
set of all possible price features of a FARE PRODUCT: default total price, discount in value or percentage
etc.
3.42
fare quota factor
(Quality Fare Structure MODEL)
named set of parameters defining a number of quota fares available of a given denomination
3.43
fare scheduled stop point
(Fare Zone MODEL)
specialisation of SCHEDULED STOP POINT describing a stop with fare accounting and routing
characteristics
3.44
fare section
(Fare Zone MODEL)
subdivision of a JOURNEY PATTERN consisting of consecutive POINTs IN JOURNEY PATTERN, used to
define an element of the fare structure
3.45
fare structure
(Use Case)
Set of parameters that determine the basic tariffs
3.46
fare structure element
(Fare Structure Element MODEL)
sequence or set of CONTROLLABLE ELEMENTs to which rules for limitation of access rights and
calculation of prices (fare structure) are applied
3.47
fare structure element in sequence
(Fare Structure Element MODEL)
FARE STRUCTURE ELEMENT as a part of a VALIDABLE ELEMENT, including its possible order in the
sequence of FARE STRUCTURE ELEMENTs forming that VALIDABLE ELEMENT, and its possible
quantitative limitation
3.48
fare structure element price
(Fare Structure Element MODEL)
set of all possible price features of a FARE STRUCTURE ELEMENT: default total price, discount in value
or percentage etc.
3.49
fare structure factor
(Common Fare Structure MODEL)
factor influencing access rights definition or calculation of prices
3.50
fare table
(Fare Table MODEL)
grouping of prices (specialization of PRICE GROUP) that may be associated with all or any of DISTANCE
MATRIX ELEMENT, FARE STRUCTURE ELEMENT GEOGRAPHICAL INTERVAL, GROUP OF ACCESS
RIGHT PARAMETER, CLASS OF USE, OPERATOR, VEHICLE MODE, FARE PRODUCT
3.51
fare unit
(Common Fare Structure MODEL)
unit associated with a FARE STRUCTURE FACTOR
3.52
fare zone
(Fare Zone MODEL)
specialization of TARIFF ZONE to include FARE SECTIONs
3.53
frequency of use
(Travel Usage Parameters MODEL)
limits of usage frequency for a FARE PRODUCT (or one of its components) or a SALES OFFER PACKAGE during a
specific VALIDITY PERIOD
Note 1 to entry: There may be different tariffs depending on how often the right is consumed during the period
3.54
fulfilment method
(Sales Distribution MODEL)
means by which the ticket is delivered to the CUSTOMER, e.g online, collection, etc.
3.55
fulfilment method price
(Sales Distribution MODEL)
set of all possible price features of a FULFILMENT METHOD default total price etc.
3.56
generic parameter assignment
(Validity Parameters MODEL)
VALIDITY PARAMETER ASSIGNMENT specifying generic access rights for a class of products (e.g. a time band limit
- 7 to 10 a.m - for trips made with a student pass)
3.57
geographical interval
(Geographical Fare Structure MODEL)
geographical interval specifying access rights for the FARE STRUCTURE ELEMENTs within the range of
this interval: 0-5 km, 4-6 zones etc.
3.58
geographical interval price
(Geographical Fare Structure MODEL)
set of all possible price features of a GEOGRAPHICAL INTERVAL: default total price etc.
3.59
geographical structure factor
(Geographical Fare Structure MODEL)
value of a GEOGRAPHICAL INTERVAL or a DISTANCE MATRIX ELEMENT expressed by a
GEOGRAPHICAL UNIT
3.60
geographical unit
(Geographical Fare Structure MODEL)
unit for calculating geographical graduated fares
3.61
geographical unit price
(Geographical Fare Structure MODEL)
set of all possible price features of a GEOGRAPHICAL UNIT: default total price etc.
3.62
group of distance matrix elements
(Distance Matrix Element MODEL)
grouping of DISTANCE MATRIX ELEMENTS
Note 1 to entry: May be used to provide reusable Origin / Destination pairs (and associate them with a PRICE)
3.63
group of distribution channels
(Sales Distribution MODEL)
grouping of DISTRIBUTION CHANNELs
3.64
group of sales offer packages
(Sales Offer Package MODEL)
grouping of SALES OFFER PACKAGEs
3.65
group ticket
(Eligibility Usage Parameters MODEL)
number and characteristics of persons entitled to travel in addition to the holder of an access right
3.66
interchanging
(Travel Usage Parameters MODEL)
Limitations on making changes within a trip
3.67
limiting rule
(Fare Calculation Parameters MODEL)
Rule for limiting the results of a price calculation
3.68
luggage allowance
(Luggage Usage Parameters MODEL)
number and characteristics (weight, volume) of luggage that a holder of an access right is entitled to
carry
3.69
minimum stay
(Travel Usage Parameters MODEL)
Details of any minimum stay at the destination required to use the product
3.70
month validity offset
(Fare Calculation Parameters MODEL)
Days before (negative) or after (positive) the start of the month that a product with a calendar period
driven activation becomes valid
3.71
network validity parameter
(Validity Parameters MODEL)
type of VALIDITY PARAMETER related to the network structure
3.72
organisational validity parameter
(Validity Parameters MODEL)
type of VALIDITY PARAMETER related to organisational issues
3.73
parking charge band
(Parking Tariff MODEL)
Parking charges that describe the cost of using a PARKING or PARKING AREfor a given period
3.74
...
SLOVENSKI STANDARD
01-junij-2020
Nadomešča:
SIST-TS CEN/TS 16614-3:2016
Javni prevoz - Izmenjava omrežnih in voznorednih podatkov (NeTEx) - 3. del:
Format za izmenjavo informacij o vozovnicah
Public transport - Network and Timetable Exchange (NeTEx) - Part 3: Public transport
fares exchange format
Öffentlicher Verkehr - Netzwerk- und Fahrplan Austausch (NeTEx) - Teil 3:
Austauschformat für das Fahrgeld im öffentlichen Verkehr
Transport public - Echange des données de réseau et d'horaires (NeTEx) - Partie 3 :
Format d'échange d'informations voyageurs concernant le réseau de transport public
Ta slovenski standard je istoveten z: CEN/TS 16614-3:2020
ICS:
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-3
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
April 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.60 Supersedes CEN/TS 16614-3:2016
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Part 3: Public transport fares exchange format
Transport Public - Echanges des informations Öffentlicher Verkehr - Netzwerk- und Fahrplan
planifiées (NeTEx) - Partie 3: Echange des informations Austausch (NeTEx) - Teil 3: Austauschformat für das
tarifaires pour le transport public Fahrgeld im öffentlichen Verkehr
This Technical Specification (CEN/TS) was approved by CEN on 2 March 2020 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-3:2020 E
worldwide for CEN national Members.
CEN/TS 16614-3
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
April 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.60 Supersedes CEN/TS 16614-3:2016
English Version
Public transport - Network and Timetable Exchange
(NeTEx) - Part 3: Public transport fares exchange format
Transport Public - Echanges des informations Öffentlicher Verkehr - Netzwerk- und Fahrplan
planifiées (NeTEx) - Partie 3: Echange des informations Austausch (NeTEx) - Teil 3: Austauschformat für das
tarifaires pour le transport public Fahrgeld im öffentlichen Verkehr
This Technical Specification (CEN/TS) was approved by CEN on 2 March 2020 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-3:2020 E
worldwide for CEN national Members.
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
1.1 General . 6
1.2 Fares scope . 6
1.3 Transport modes . 7
1.4 Compatibility with existing standards and recommendations . 7
2 Normative references . 7
3 Terms and definitions . 8
4 Symbols and abbreviations . 27
5 Use Cases for Fare Exchange . 28
5.1 Purpose . 28
5.2 Business context . 28
5.2.1 Fare planning process . 28
5.3 Actors and use case types . 33
5.3.1 Use Cases for Fare Policy . 36
5.3.2 Use Cases for Organisation of Fare Policy Usage . 36
5.4 Excluded Use Cases . 37
5.5 Use Cases . 37
5.5.1 Collection of Use Cases . 37
6 Generic Physical Model and XSD mapping rules . 64
7 Public Transport Fares – Conceptual and physical data model . 64
7.1 Introduction . 64
7.2 Conceptual Model overview . 64
7.2.1 Functional Domains . 64
7.2.2 Data Model Overview . 66
7.2.3 Main Concepts . 68
7.3 Fare Model dependencies . 72
7.3.1 NeTEx Part3 Use of Version Frames . 74
7.3.2 Fare Frame . 75
7.4 Reusable Fare Components . 92
7.4.1 Fare Zone . 92
7.4.2 Fare Facility . 111
7.4.3 Vehicle Seating . 114
7.5 Fare Structure . 115
7.5.1 Fare Structure – Model dependencies . 115
7.5.2 Common Fare Structure . 116
7.5.3 Geographical Fare Structure. 123
7.5.4 Time Fare Structure . 132
7.5.5 Quality Fare Structure . 140
7.5.6 Fare Structure Element . 150
7.5.7 Distance Matrix Element . 178
7.5.8 Validable & Controllable Elements . 189
7.6 Access Rights Description . 200
7.6.1 Access Right Parameters . 200
7.6.2 Fare Product . 338
7.7 Pricing . 383
7.7.1 Fare Calculation Parameters . 383
7.7.2 Fare Price . 398
7.7.3 Fare Table . 411
7.8 Sales Description . 436
7.8.1 Fare Sales Distribution . 436
7.8.2 Type of Travel Document . 447
7.8.3 Sales Offer Package . 451
8 Sales Transactions . 477
8.1 Sales Transaction – Model dependencies . 477
8.1.1 Sales Transaction Frame . 478
8.1.2 Fare Contract . 482
8.1.3 Customer Eligibility . 498
8.1.4 Retail . 502
8.1.5 Sales Transaction . 508
8.1.6 Travel Specification . 519
8.1.7 Customer Purchase Package . 533
Annex A (normative) Extensions to NeTEx Part1 & 2 . 551
Annex B (informative) ERA – TAP TSI annexes B1, B2 and B3 mapping . 552
B.1 Summary of mapping of B1 (NRT) fares . 552
.2 Summary of mapping of B2 (IRT) fares . 552
B
B.3 Summary of mapping of B3 (Special) fares . 553
Annex C (informative) NeTEx Passenger Information Query model . 554
C.1 PiRequest . 554
C.1.1 PI Request dependencies . 554
C.1.2 Pi Request . 556
Annex D (informative) How to go from a trip (from NeTEx Part1&2) to a fare ?. 594
D.1 Passenger Trip . 594
D.1.1 Passenger Trip Model . 594
D.1.2 Passenger Fare Offer Model . 603
Annex E (informative) Proposed model for Parking Tariff . 608
E.1 Parking Tariff . 608
E.1.1 Parking Tariff – Conceptual MODEL . 608
Annex F (informative) Changes in Version 1.1 . 615
F.1 Introduction . 615
F.2 General Changes . 615
F.3 List of Changes . 615
Bibliography . 621
European foreword
This document (CEN/TS 16614-3:2020) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes CEN/TS 16614-3:2016.
This document presents Part 3 of the European Technical Specification known as “NeTEx”. NeTEx
provides a framework for specifying communications and data exchange protocols for
organisations wishing to exchange scheduled Information relating to public transport operations.
This Technical Specification is made up of three 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 1 is fully standalone, and part 2 and 3 rely on part 1.
The XML schema can be downloaded 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 style and use camelcase style with no spaces
(TypeOfEntity for example).
According to the CEN/CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to announce this document: 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 the United Kingdom.
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; publicising fares, issuing tickets
and receipts; providing real-time information on service running, and so on.
The first two parts of the European Technical Specification NeTEx specify a Network and Timetable
Exchange for Public Transport. 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 a real-time data.
This document (NeTEx – Part 3) specifies exchanges of Public Transport fares between systems and
organisations. It is a complement to Part 1 and Part 2 in the sense that it uses a subset of concepts
defined there.
Well-defined, open interfaces have a crucial role in improving the economic and technical viability of
Public Transport Information Systems of all kinds. Using standardised 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 standard will improve a number of features of public transport information and service
management: Interoperability – the standard will facilitate interoperability between information
processing systems of the transport operators by: (i) introducing common architectures for message
exchange; (ii) introducing a modular set of compatible information services, (iii) using common data
models and schemas for the messages exchanged for each service; and (iv) introducing a consistent
approach to data management.
Technical advantages include the following: a modular reusing of a common communication layer
shared with SIRI for all the various technical services enables cost-effective implementations, and
makes the standard readily extensible in future.
1 Scope
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 Part 3 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 Part 1 and Part 2 and
the Fare Collection data model defined in Transmodel V51. See the use cases below for the overall scope
of Part 3. 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.
Under preparation.
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.
1.4 Compatibility with existing standards and recommendations
The overall approach for the definition of fares within NeTEx Part 3 follows the approach used by
Transmodel V5.1, namely the definition of access rights rather than of just products.
This approach, used in Transmodel V5.1 (Fare Collection data model) to specify the access rights related
to the urban public transport (for all urban modes) has been extended to cover access rights for long-
distance rail.
NOTE The concepts from Transmodel V5.1 and IFOPT used and/or modified by NeTEx are incorporated into
Transmodel V6 to guarantee compatibility and coherence of standards.
Concepts covered in NeTEx Part 1 and 2 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
and train routing restrictions.
In the case of long distance train access rights, 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. These relate in particular to the B1 (Non Reservation Tickets),
B2 (Integrated Reservation Tickets) and B3 (Special Fares) along with various UIC Leaflets.
As regards the other exchange protocols for network and timetable exchanges, a formal compatibility is
ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), BISON (The Netherlands)
and NOPTIS (Nordic Public Transport Interface Standard).
The exchange of data in NeTEx format can be undertaken using a variety of protocols. For example:
through dedicated web services, through data file exchanges, or by using the SIRI exchange protocol as
described in part 2 of the SIRI documentation. NeTEx adds additional services using the common SIRI
transport mechanism.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
CEN/TS 16614-1, Public transport — Network and Timetable Exchange (NeTEx) — Part 1: Public
transport network topology exchange format
3 Terms and definitions
For the purposes of this document, the terms and definitions given in CEN/TS 16614-1:2019 and the
following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• ISO Online browsing platform: available at https://www.iso.org/obp
• IEC Electropedia: available at http://www.electropedia.org/
NOTE A lot of definitions are shared with Transmodel (EN 12896): special attention was paid to the
consistency of definitions, keeping exactly the same wording. The italic bracket name at the beginning of the
definition is a package name that will help the reader to find the related concept in the UML data model.
3.1
access right in product
(Fare Product MODEL)
VALIDABLE ELEMENT as a part of a PRE-ASSIGNED FARE PRODUCT, including its possible order in the
set of all VALIDABLE ELEMENTs grouped together to define the access right assigned to that PRE-
ASSIGNED FARE PRODUCT
3.2
access right parameter assignment
(Validity Parameters MODEL)
assignment of a fare collection parameter (referring to geography, time, quality or usage) to an element
of a fare system (access right, validated access, control mean, etc.)
3.3
amount of price unit
(Fare Product MODEL)
FARE PRODUCT consisting in a stored value of PRICE UNITs: an amount of money on an electronic
purse, amount of units on a value card etc.
3.4
blacklist
(Fare Contract MODEL)
list of identified TRAVEL DOCUMENTs or CONTRACTs the validity of which has been cancelled
temporarily or permanently, for a specific reason like loss of the document, technical malfunction, no
credit on bank account, offences committed by the customer, etc.
3.5
border point
(Fare Zone MODEL)
POINT on the Network marking a boundary for the fare calculation
Note 1 to entry: May or may not be a SCHEDULED STOP POINT
3.6
cancelling
(Cancelling Usage Parameters MODEL)
Parameter giving conditions for cancelling of a purchased access right
3.7
capped discount right
(Fare Product MODEL)
specialisation of SALE DISCOUNT RIGHT where the discount is expressed as a rule specifying a ceiling for a given
time interval
Note 1 to entry: For example, the London Oyster card fare, which charges for each journey until travel equivalent
to a day pass has been consumed after which further travel is free at that day
3.8
capping rule
(Fare Product MODEL)
capping limit for a given time interval, where the capping is expressed by another product
Note 1 to entry: For example, the London Oyster card fare, which charges for each journey until travel equivalent
to a day pass for the mode of travel has been consumed
3.9
capping rule price
(Fare Product MODEL)
set of all possible price features of a CAPPING RULE: default total price, discount in value or percentage
etc.
3.10
cell
(Fare Table MODEL)
unique individual combination of features within a FARE TABLE, used to associate a FARE PRICE with a
fare element
3.11
charging moment
(Fare Product MODEL)
classification of FARE PRODUCTs according to the payment method and the account location: pre-
payment with cancellation (throw-away), pre-payment with debit on a value card, pre-payment without
consumption registration (pass), post-payment etc.
3.12
charging policy
(Charging Usage Parameters MODEL)
Parameter governing minimum amount and credit allowed when consuming a FARE PRODUCT
3.13
commercial profile
(Eligibility Usage Parameters MODEL)
category of users depending on their commercial relations with the operator (frequency of use, amount
of purchase etc.), often used for allowing discounts
3.14
companion profile
(Eligibility Usage Parameters MODEL)
number and characteristics of the persons entitled to travel in a group or as companions to another
USER PROFILE
3.15
controllable element
(Validable Element MODEL)
smallest controllable element of public transport consumption, all along which any VALIDITY
PARAMETER ASSIGNMENT remains valid
3.16
controllable element in sequence
(Validable Element MODEL)
CONTROLLABLE ELEMENT as a part of a FARE STRUCTURE ELEMENT, including its possible order in
the sequence of CONTROLLABLE ELEMENTs grouped together to form that FARE STRUCTURE
ELEMENT, and its possible quantitative limitation
3.17
controllable element price
(Validable Element MODEL)
set of all possible price features of a CONTROLLABLE ELEMENT: default total price, discount in value or
percentage etc.
3.18
customer
(Fare Contract MODEL)
identified person or organisation involved in a fare process
Note 1 to entry: There may be a CONTRACT between the CUSTOMER and the OPERATOR or the AUTHORITY ruling
the consumption of services
3.19
discounting rule
(Fare Calculation Parameters MODEL)
price calculation rule determined by a set of discounts, depending upon a USAGE PARAMETER, to be
applied to a FARE PRICE
3.20
distance matrix element
(Distance Matrix Element MODEL)
cell of an origin-destination matrix for TARIFF ZONEs or STOP POINTs, expressing a fare distance for
the corresponding trip: value in km, number of fare units etc.
3.21
distance matrix element price
(Distance Matrix Element MODEL)
set of all possible price features of a DISTANCE MATRIX ELEMENT: default total price etc.
3.22
distribution assignment
(Sales Offer Package MODEL)
assignment of the COUNTRY and/or DISTRIBUTION CHANNEL through which a product may or may not
be distributed
3.23
distribution channel
(Sales Distribution MODEL)
type of outlet for selling of a product
3.24
eligibility
(Use Case)
required characteristics of a customer to be able to purchase a product
3.25
eligibility change policy
(Eligibility Parameters MODEL)
Parameter indicating the action to be taken when a user’s eligibility status changes
3.26
entitlement constraint
(Entitlement Parameters MODEL)
Constraints on choices for an dependent entitled product relative to the required choices for the
prerequisite entitling product
3.27
entitlement given
(Entitlement Parameters MODEL)
Parameter indicating whether a particular FARE PRODUCT provides an entitlement to buy or use an
access right
3.28
entitlement product
(Fare Product MODEL)
precondition to access a service or to purchase a FARE PRODUCT issued by an organisation that may not be a PT
operator (e.g.military card)
3.29
entitlement required
(Entitlement Parameters MODEL)
Parameter indicating whether a particular FARE PRODUCT requires an entitlement to by or use an
access right
3.30
exchanging
(Booking Usage Parameters MODEL)
Whether and how the access right may be exchanged for another access right
3.31
fare
(Use Case)
From the customer perspective: the amount that a customer has to pay for a journey or for acquiring a
product
3.32
fare day type
(Fare Calculation Parameters MODEL)
type of day used in the fare collection domain, characterised by one or more properties which affect the
definition of access rights and prices in the fare system
3.33
fare demand factor
(Quality Fare Structure MODEL)
named set of parameters defining a period of travel with a given price, for example off peak, peak, super
off peak, etc.
3.34
fare element in sequence
(Common Fare Structure MODEL)
FARE ELEMENT as a part of an ELEMENT, including its possible order in the sequence of FARE
ELEMENTs
3.35
fare frame
(Fare Frame MODEL)
set of all fare data defined for a specific VEHICLE MODE to which the same VALIDITY CONDITIONs have
been assigned
3.36
fare frame defaults
(Fare Frame MODEL)
Set of pricing parameters and values to apply to an individual element in the frame if no explicit value is
specified on the element
3.37
fare interval
(Common Fare Structure MODEL)
interval based aspect of the fare structure
3.38
fare point in pattern
(Fare Zone MODEL)
POINT IN PATTERN which represents the start or end of a FARE SECTION, or a point used to define a
SERIES CONSTRAINT
3.39
fare price
(Fare Price MODEL)
Price features DEFINED BY DEFAULT characterizing different PRICE GROUPs
3.40
fare product
(Fare Product MODEL)
immaterial marketable element (access rights, discount rights, etc.), specific to a CHARGING MOMENT
3.41
fare product price
(Fare Product MODEL)
set of all possible price features of a FARE PRODUCT: default total price, discount in value or percentage
etc.
3.42
fare quota factor
(Quality Fare Structure MODEL)
named set of parameters defining a number of quota fares available of a given denomination
3.43
fare scheduled stop point
(Fare Zone MODEL)
specialisation of SCHEDULED STOP POINT describing a stop with fare accounting and routing
characteristics
3.44
fare section
(Fare Zone MODEL)
subdivision of a JOURNEY PATTERN consisting of consecutive POINTs IN JOURNEY PATTERN, used to
define an element of the fare structure
3.45
fare structure
(Use Case)
Set of parameters that determine the basic tariffs
3.46
fare structure element
(Fare Structure Element MODEL)
sequence or set of CONTROLLABLE ELEMENTs to which rules for limitation of access rights and
calculation of prices (fare structure) are applied
3.47
fare structure element in sequence
(Fare Structure Element MODEL)
FARE STRUCTURE ELEMENT as a part of a VALIDABLE ELEMENT, including its possible order in the
sequence of FARE STRUCTURE ELEMENTs forming that VALIDABLE ELEMENT, and its possible
quantitative limitation
3.48
fare structure element price
(Fare Structure Element MODEL)
set of all possible price features of a FARE STRUCTURE ELEMENT: default total price, discount in value
or percentage etc.
3.49
fare structure factor
(Common Fare Structure MODEL)
factor influencing access rights definition or calculation of prices
3.50
fare table
(Fare Table MODEL)
grouping of prices (specialization of PRICE GROUP) that may be associated with all or any of DISTANCE
MATRIX ELEMENT, FARE STRUCTURE ELEMENT GEOGRAPHICAL INTERVAL, GROUP OF ACCESS
RIGHT PARAMETER, CLASS OF USE, OPERATOR, VEHICLE MODE, FARE PRODUCT
3.51
fare unit
(Common Fare Structure MODEL)
unit associated with a FARE STRUCTURE FACTOR
3.52
fare zone
(Fare Zone MODEL)
specialization of TARIFF ZONE to include FARE SECTIONs
3.53
frequency of use
(Travel Usage Parameters MODEL)
limits of usage frequency for a FARE PRODUCT (or one of its components) or a SALES OFFER PACKAGE during a
specific VALIDITY PERIOD
Note 1 to entry: There may be different tariffs depending on how often the right is consumed during the period
3.54
fulfilment method
(Sales Distribution MODEL)
means by which the ticket is delivered to the CUSTOMER, e.g online, collection, etc.
3.55
fulfilment method price
(Sales Distribution MODEL)
set of all possible price features of a FULFILMENT METHOD default total price etc.
3.56
generic parameter assignment
(Validity Parameters MODEL)
VALIDITY PARAMETER ASSIGNMENT specifying generic access rights for a class of products (e.g. a time band limit
- 7 to 10 a.m - for trips made with a student pass)
3.57
geographical interval
(Geographical Fare Structure MODEL)
geographical interval specifying access rights for the FARE STRUCTURE ELEMENTs within the range of
this interval: 0-5 km, 4-6 zones etc.
3.58
geographical interval price
(Geographical Fare Structure MODEL)
set of all possible price features of a GEOGRAPHICAL INTERVAL: default total price etc.
3.59
geographical structure factor
(Geographical Fare Structure MODEL)
value of a GEOGRAPHICAL INTERVAL or a DISTANCE MATRIX ELEMENT expressed by a
GEOGRAPHICAL UNIT
3.60
geographical unit
(Geographical Fare Structure MODEL)
unit for calculating geographical graduated fares
3.61
geographical unit price
(Geographical Fare Structure MODEL)
set of all possible price features of a GEOGRAPHICAL UNIT: default total price etc.
3.62
group of distance matrix elements
(Distance Matrix Element MODEL)
grouping of DISTANCE MATRIX ELEMENTS
Note 1 to entry: May be used to provide reusable Origin / Destination pairs (and associate them with a PRICE)
3.63
group of distribution channels
(Sales Distribution MODEL)
grouping of DISTRIBUTION CHANNELs
3.64
group of sales offer packages
(Sales Offer Package MODEL)
grouping of SALES OFFER PACKAGEs
3.65
group ticket
(Eligibility Usage Parameters MODEL)
number and characteristics of persons entitled to travel in addition to the holder of an access right
3.66
interchanging
(Travel Usage Parameters MODEL)
Limitations on making changes within a trip
3.67
limiting rule
(Fare Calculation Parameters MODEL)
Rule for limiting the results of a price calculation
3.68
luggage allowance
(Luggage Usage Parameters MODEL)
number and characteristics (weight, volume) of luggage that a holder of an access right is entitled to
carry
3.69
minimum stay
(Travel Usage Parameters MODEL)
Details of any minimum stay at the destination required to use the product
3.70
month validity offset
(Fare Calculation Parameters MODEL)
Days before (negative) or after (positive) the start of the month that a product with a calendar period
driven activation becomes valid
3.71
network validity parameter
(Validity Parameters MODEL)
type of VALIDITY PARAMETER related to the network structure
3.72
organisational validity parameter
(Validity Parameters MODEL)
type of VALIDITY PARAMETER related to organisational issues
3.73
parking charge band
(Parking Tariff MODEL)
Parking charges that describe the cost of using a PARKING or PARKING AREfor a given period
3.74
parking price
(Parking Tariff MODEL)
specialisati
...
記事タイトル：CEN/TS 16614-3:2020 - 公共交通 - ネットワークおよび時刻表交換（NeTEx）- 第3部門：公共交通料金交換形式 記事内容： 1.1 一般 NeTExはスケジュールデータ（ネットワーク、時刻表、料金情報）の交換に特化しています。それはTransmodel V5.1（EN 12986）、IFOPT（EN 28701）、およびSIRI（CEN/TS 15531-4/5およびEN 15531-1/2/3）に基づいており、公共交通サービスに関する乗客情報や自動化された車両監視システム（AVMS）に関する情報の交換をサポートしています。 注意：NeTExはTransmodelとIFOPTの改良および実装であり、これらの概念の定義と説明は、それぞれの標準から直接抽出され、NeTExで再利用されます。時にはNeTExの文脈に合うように適応されます。NeTExが対象とするデータ交換は、主に乗客情報システムとAVMSにトランジットスケジューリングシステムのデータを提供することに向けられていますが、これに制限されず、NeTExは輸送データ交換の他の多くの使用事例にも効果的な解決策を提供できます。 1.2 料金の範囲 NeTExの第3部では、特に第1部と第2部で定義された基になるネットワークおよび時刻表モデル、およびTransmodel V51で定義された料金収集データモデルに関連する料金構造と料金データの交換に関心があります。第3部全体の範囲については、以下の使用事例を参照してください。要約すると、次の目的のためのデータに関与します： （i）公共交通で発生するさまざまな料金構造を記述すること（例：一律料金、区域料金、時間依存料金、距離に基づく料金、ステージ料金、利用時に支払う料金、シーズンパスなど）。 （ii）これらの料金構造を持つ購入可能な料金商品を記述し、特定の料金に関連する条件を記述します。たとえば、特定のユーザーグループに制限されたり、時間制限がある場合など、これらの条件は複雑な場合があります。 （iii）実際の価格データの交換を許可します。ただし、NeTEx自体は価格アルゴリズムや料金の計算方法を指定しません。これは料金管理システムの関心事です。料金を説明または正当化するために必要な価格計算に必要なさまざまなパラメータを交換するために使用されることがあります。 NeTExは小売システムよりも上位のシステムと見なされ、旅程計画とネットワークデータと統合して料金データを管理し、公衆に提供する情報システムと補完的であり、料金を販売する小売システムやその使用を検証する制御システムとは異なります。 NeTExの範囲の詳細については、「除外された使用事例」を参照してください。 1.3 交通モード NeTExは列車、バス、コーチ、メトロ、トラム、フェリーなどのすべての公共交通モードを考慮しています。空港、航空旅行、および航空料金も記述することはできますが、航空輸送固有の追加要件については特に考慮されていません。
The article is about CEN/TS 16614-3:2020, which is a standard for the exchange of public transport fare information. It is based on other standards such as Transmodel, IFOPT, and SIRI, and supports the exchange of data for passenger information and Automated Vehicle Monitoring Systems. The scope of this standard is to describe fare structures, fare products, and conditions attached to fares. It also allows for the exchange of actual price data and includes attributes and descriptions for presenting fares to the public. NeTEx is intended to be used upstream of retail systems and is applicable to all mass public transport modes. While it can describe airports and air fares, there are no specific requirements for air transport included in the standard.
기사 제목: CEN/TS 16614-3:2020 - 대중교통 - 네트워크 및 시간표 교환 (NeTEx) - 제3부: 대중교통 요금 교환 형식 기사 내용: 1.1 일반 NeTEx는 예정된 데이터 (네트워크, 시간표 및 요금 정보)의 교환을 위해 개발되었습니다. 이것은 Transmodel V5.1 (EN 12986), IFOPT (EN 28701) 및 SIRI (CEN/TS 15531-4/5 및 EN 15531-1/2/3)를 기반으로 하며, 대중 교통 서비스에 대한 승객 정보 및 자동화 차량 모니터링 시스템 (AVMS)에 대한 정보 교환을 지원합니다. 참고: NeTEx는 Transmodel과 IFOPT의 세분화와 구현이며, 이러한 개념의 정의와 설명은 해당 표준에서 직접 추출되어 NeTEx에서 재사용되며, 때로는 NeTEx의 맥락에 맞게 적응이 이루어집니다. NeTEx가 대부분 승객 정보 시스템과 AVMS에 대한 운송 일정 시스템 데이터를 제공하기 위해 대상으로 하는 데이터 교환은 단정적으로 이것으로 제한되지 않으며, NeTEx는 교통 데이터 교환에 대한 많은 다른 사용 사례에 대한 효과적인 해결책을 제공할 수 있습니다. 1.2 요금 범위 NeTEx의 이 부분인 Part3는 특히 Part1과 Part2에서 정의된 밑바탕이 되는 네트워크 및 시간표 모델 및 Transmodel V51에서 정의된 요금 수집 데이터 모델과 관련된 요금 구조와 요금 데이터의 교환에 관심을 가지고 있습니다. Part3의 전반적인 범위에 대한 사용 사례에 대해 아래를 참조하십시오. 요약하면 다음과 같은 목적으로 데이터에 관여합니다: (i) 대중 교통에서 발생하는 다양한 요금 구조를 설명하는 것 (예: 고정 요금, 구역 요금, 시간 제한 요금, 거리에 따른 요금, 단계 요금, 출발하면 지불하는 요금, 시즌 패스 등). (ii) 이러한 요금 구조를 가진 구매 가능한 요금 상품을 설명하고, 특정 요금에 부여될 수 있는 조건을 설명합니다. 예를 들어, 특정 사용자 그룹에 제한되거나 시간 제한이 있는 경우입니다. 이러한 조건은 복잡할 수 있습니다. (iii) 실제 가격 데이터를 교환할 수 있도록 합니다. 그러나 NeTEx 자체로는 요금 계산을 위한 가격 알고리즘이나 요금을 계산하는 방법을 지정하지 않습니다. 이는 요금 관리 시스템의 관심사입니다. 요금 계산을 설명하거나 정당화하는 데 필요한 다양한 매개 변수를 교환하는 데 사용될 수 있습니다. NeTEx는 소매 시스템보다 상위 시스템으로 간주되며, 운송 일정 및 네트워크 데이터와 함께 요금 데이터를 관리하고 대중에게 제공하는 정보 시스템과 보충적이며 구별되며, 요금을 판매하는 소매 시스템 및 사용의 검증을 수행하는 제어 시스템과는 구별됩니다. NeTEx의 범위에 대한 추가 정보는 "제외된 사용 사례"를 참조하십시오. 1.3 교통 수단 NeTEx는 기차, 버스, 코치, 메트로, 트램, 페리 및 이들의 하위 모드와 같은 모든 대중교통 수단을 고려합니다. 공항, 항공 여행 및 항공 요금도 설명할 수 있지만, 항공 운송에 특정적으로 적용되는 추가 요구 사항에 대한 고려는 없었습니다.
[article title: CEN/TS 16614-3:2020 - 대중 교통 - 네트워크 및 시간표 교환 (NeTEx) - 일부 3: 대중 교통 요금 교환 형식] article content: 1.1 일반 NeTEx는 예약된 데이터 (네트워크, 시간표 및 요금 정보)의 교환을 위해 개발되었습니다. 이는 Transmodel V5.1 (EN 12986), IFOPT (EN 28701) 및 SIRI (CEN/TS 15531-4/5와 EN 15531-1/2/3)을 기반으로 하며, 대중 교통 서비스에 대한 승객 정보와 자동화 차량 모니터링 시스템 (AVMS) 운영에 관련된 정보 교환을 지원합니다. 참고: NeTEx는 Transmodel과 IFOPT의 개념을 세분화하고 구현한 것입니다. 이러한 개념의 정의와 설명은 해당 표준에서 직접 추출되어 NeTEx에서 재사용되며, NeTEx 맥락에 맞게 필요에 따라 조정됩니다. NeTEx가 대부분의 데이터 교환을 승객 정보 시스템과 AVMS에 대한 대중 교통 예약 시스템 데이터 공급을 위해 지향하고 있지만 이에 제한되지는 않으며, 교통 데이터 교환에 다양한 다른 용도에도 효과적인 솔루션을 제공할 수 있습니다. 1.2 요금 범위 NeTEx의 일부 3은 주로 일부 1과 일부 2에서 정의된 기본 네트워크 및 시간표 모델과 Transmodel V51에서 정의된 요금 수집 데이터 모델과 관련하여 요금 구조와 요금 데이터의 교환에 특히 관심이 있습니다. Part3의 전반적인 범위에 대한 사용 사례는 아래에서 확인할 수 있습니다. 요약하자면 다음과 같은 목적으로 데이터에 관련한 사항을 다루고 있습니다: (i) 대중 교통에서 발생하는 다양한 요금 구조를 설명하기 위해 (예: 일정 요금, 지역 요금, 시간에 따른 요금, 거리 기반 요금, 단계 요금, 사용시 요금, 시즌 패스 등). (ii) 이러한 요금 구조를 가진 구매 가능한 요금 상품 및 특정 요금에 부여될 수 있는 조건을 설명하기 위해, 예를 들어 특정 사용자 그룹에 제한되었거나 시간적 제한이 있는 경우 등. 이러한 조건은 복잡할 수 있습니다. (iii) 실제 가격 데이터를 교환할 수 있도록 합니다. 그러나 NeTEx 자체적으로 요금 산출 알고리즘이나 요금이 어떻게 계산되어야 하는지를 명시하지는 않습니다. 이는 요금 관리 시스템의 역할입니다. 요금 설명이나 정당화에 필요한 요금 산출 계산에 필요한 다양한 매개 변수를 교환하는 데 사용될 수 있습니다. NeTEx는 소매 시스템의 상위에 위치하며 요금 데이터를 대중에게 제공하기 위해 여행 계획 및 네트워크 데이터와 통합되는 것으로 간주되어야 합니다. 이는 요금을 판매하는 소매 시스템 및 요금 사용을 확인하는 제어 시스템과 별개이며, NeTEx의 범위와 요금 관리 시스템 사이의 경계에 대한 자세한 정보는 아래의 "제외된 사용 사례"에서 확인할 수 있습니다. 1.3 교통 수단 NeTEx는 기차, 버스, 코치, 지하철, 트램, 페리 및 이들의 하위 모드를 포함한 모든 대중 교통 수단을 고려합니다. 공항, 비행 및 항공 요금을 설명할 수 있지만, 항공 운송에 특별히 적용되는 추가 요구 사항에 대한 특별한 고려는 없었습니다.
The article introduces CEN/TS 16614-3:2020, which is a standard for the exchange of public transport data. It is based on existing standards such as Transmodel, IFOPT, and SIRI, and supports the exchange of information related to network, timetable, fare structures, and fare data. It can be used for passenger information systems and Automated Vehicle Monitoring Systems. NeTEx is not restricted to these purposes and can be used for various other transport data exchange use cases. The scope of Part 3 of NeTEx specifically focuses on fare structures, fare products, pricing data, and descriptions of fares and their conditions. It covers all mass public transport modes but does not have specific considerations for air transport.
記事のタイトル: CEN/TS 16614-3:2020 - 公共交通機関 - ネットワーク及び時刻表交換（NeTEx）- 部分3: 公共交通機関運賃交換形式 記事内容: 1.1 一般 NeTExはスケジュールデータ（ネットワーク、時刻表、運賃情報）の交換に特化しています。Transmodel V5.1（EN 12986）、IFOPT（EN 28701）およびSIRI（CEN/TS 15531-4/5およびEN 15531-1/2/3）に基づいており、公共交通サービスに関連する情報を乗客情報システムや自動車監視システム（AVMS）に提供するための情報交換をサポートしています。 注意: NeTExはTransmodelおよびIFOPTの改良・実装であり、これらの概念の定義と説明はそれぞれの標準から直接抽出され、NeTExではそのまままたは一部適応して再利用されることがあります。NeTExの対象となるデータ交換は主に乗客情報システムとAVMSにトランジットスケジューリングシステムからのデータを提供するために向けられていますが、これに限定されず、他のさまざまな交通データ交換の用途にも効果的なソリューションを提供することができます。 1.2 運賃の範囲 NeTExのこのPart3は、Part1およびPart2で定義された基礎となるネットワークおよび時刻表モデル、およびTransmodel V51で定義された運賃収集データモデルに関連する運賃構造と運賃データの交換に重点を置いています。Part3の全体的な範囲は以下の用途に関連するデータに関与しています： (i) 公共交通機関で発生する様々な運賃構造を説明するために（均一運賃、ゾーン別運賃、時間依存運賃、距離別運賃、階段運賃、ペイアズユーゴータイプの運賃、季節券など）。 (ii) これらの運賃構造を持つ購入可能な運賃製品および特定の運賃に付随する条件を説明するために、例えば特定の使用者グループに制限されるか、時間的な制約がある場合など。これらの条件は複雑なものもあります。 (iii) 実際の価格データを交換するための機能を提供します。ただし、NeTEx自体は価格算出アルゴリズムや運賃の計算方法を指定していません。これは運賃管理システムの役割です。運賃の説明や販売・使用条件のために必要なさまざまな価格計算に必要なパラメータを交換するために使用されることがあります。 NeTExは小売システムより上流に位置し、運賃データを公開情報システムの旅程計画およびネットワークデータと統合し管理するためのものと考えるべきです。これは運賃を販売する小売システムや使用の検証を行う制御システムとは異なります。詳細は「除外される使用用途」を参照してください。 1.3 交通モード NeTExは列車、バス、コーチ、地下鉄、トラム、フェリーなどのすべての大量公共交通機関モードを考慮しています。空港や航空旅行、航空運賃を記述することもできますが、航空輸送に特に適用される追加要件については特に考慮されていません。
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...