FprCEN/TS 16614-3
(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
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 3.
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 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
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2025
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 - Echanges des informations planifiées (NeTEx) - Partie 3: Echange
des informations tarifaires pour le transport public
Ta slovenski standard je istoveten z: FprCEN/TS 16614-3
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
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
October 2025
ICS Will supersede CEN/TS 16614-3:2020
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 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 16614-3:2025 E
worldwide for CEN national Members.
Contents Page
European foreword . 8
Introduction . 9
1 Scope . 10
1.1 General . 10
1.2 Fares scope . 10
1.3 Transport modes . 10
1.4 Compatibility with existing standards and recommendations . 11
2 Normative references . 12
3 Terms and definitions . 12
4 Symbols and abbreviations . 30
5 Use Cases for Fare Exchange . 30
5.1 Purpose . 30
5.2 Business context . 30
5.2.1 Fare planning process . 30
5.3 Actors and use case types . 35
5.3.1 Use Cases for Fare Policy . 37
5.3.2 Use Cases for Organisation of Fare Policy Usage . 38
5.4 Excluded Use Cases . 38
5.5 Use Cases . 39
5.5.1 Collection of Use Cases . 39
6 Generic Physical Model and XSD mapping rules . 63
7 Public Transport Fares – Conceptual and physical data model . 63
7.1 Introduction . 63
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 Fares Use of Version Frames . 73
7.3.2 Fare Frame . 74
7.4 Fare Price Frame . 90
7.5 Reusable Fare Components . 93
7.5.1 Fare Zone . 93
7.5.2 Fare Facility . 114
7.5.3 Vehicle Seating (DEPRECATED) . 117
7.6 Fare Structure . 118
7.6.1 Fare Structure – Model dependencies . 118
7.6.2 Common Fare Structure . 119
7.6.3 Geographical Fare Structure. 126
7.6.4 Time Fare Structure . 136
7.6.5 Quality Fare Structure . 145
7.6.6 Fare Structure Element . 155
7.6.7 Distance Matrix Element . 187
7.6.8 Validable & Controllable Elements . 200
7.7 Access Rights Description . 210
7.7.1 Access Right Parameters . 211
7.7.2 Fare Product . 377
7.8 Pricing . 430
7.8.1 Fare Calculation Parameters . 430
7.8.2 Fare Price . 446
7.8.3 Fare Table . 460
7.9 Sales Description . 493
7.9.1 Fare Sales Distribution . 493
7.9.2 Type of Travel Document . 504
7.9.3 Medium Application MODEL . 509
7.9.4 Sales Offer Package . 517
8 Sales Transactions . 547
8.1 Sales Transaction – Model dependencies . 547
8.1.1 Sales Transaction Frame . 549
8.1.2 Fare Contract . 553
8.1.3 Customer Eligibility . 569
8.1.4 Payment Means . 575
8.1.5 Travel Preferences . 578
8.1.6 Fare Contract – XML Examples. . 579
8.1.7 Retail . 580
8.1.8 Sales Transaction . 586
8.1.9 Travel Specification . 601
8.1.10 Customer Purchase Package . 617
8.1.11 Spot Allocation . 646
Annex A (normative) Extensions to NeTEx Part 1 & 2 . 652
Annex B (informative) ERA – TAP TSI annexes B1, B2 and B3 mapping . 653
B.1 Summary of mapping of B1 (NRT) fares . 653
B.2 Summary of mapping of B2 (IRT) fares . 653
B.3 Summary of mapping of B3 (Special) fares . 654
Annex C (informative) NeTEx Passenger Information Query model . 656
C.1 PiRequest . 656
C.1.1 PI Request dependencies . 656
C.1.2 Pi Request . 658
C.1.2.1 Common PI Query . 658
C.1.2.1.1 PiRequest – Conceptual MODEL – Overview . 659
C.1.2.1.2 PiRequest – Conceptual MODEL – Details . 660
C.1.2.1.3 PiRequest – Physical model – Details . 660
C.1.2.1.4 PiRequest – Attributes and XSD. 661
C.1.2.1.4.1 PiDelivery – Model Element . 661
C.1.2.1.4.2 PassengerRequest – Model Element . 661
C.1.2.1.4.3 PassengerRequestPolicy – Model Element . 661
C.1.2.1.4.4 TypeOfRequest – Model Element . 662
C.1.2.2 Location Query . 662
C.1.2.2.1 Location Request – Conceptual MODEL . 663
C.1.2.2.2 Location Request – Physical model – Overview . 663
C.1.2.2.3 Location Request – Physical model – Details . 664
C.1.2.2.4 Location – Attributes and XSD . 665
C.1.2.2.4.1 LocationDelivery – Model Element . 665
C.1.2.2.4.2 LocationRequest – Model Element . 666
C.1.2.2.4.3 LocationRequestFilter – Model Element . 666
C.1.2.2.4.4 LocationRequestPolicy – Model Element . 667
C.1.2.3 TripQuery . 667
C.1.2.3.1 Trip Request – Conceptual MODEL . 668
C.1.2.3.2 Trip Request – Physical model – Overview . 668
C.1.2.3.3 Trip Request – Physical model – Details . 669
C.1.2.3.4 Trip Request – Attributes and XSD . 670
C.1.2.3.4.1 TripDelivery – Model Element . 670
C.1.2.3.4.2 TripRequest – Model Element . 671
C.1.2.3.5 TripRequestPlace – Model Element . 672
C.1.2.3.5.1 TripAccessConstraint – Model Element . 672
C.1.2.3.5.2 ViaRequestPlace – Model Element . 672
C.1.2.3.5.3 TripRequestFilter – Model Element . 673
C.1.2.3.5.4 AccessibilityRequestFilter – Model Element . 673
C.1.2.3.5.5 FareProductFilter – Model Element . 674
C.1.2.3.5.6 TripRequestPolicy – Model Element . 675
C.1.2.3.6 Stop Departure Query . 677
C.1.2.3.7 Stop Departure Request – Conceptual MODEL . 677
C.1.2.3.8 Stop Departure Request – Physical model – Overview . 677
C.1.2.3.9 Stop Departure Request – Physical model – Details . 678
C.1.2.3.10 Stop Departure Request – Attributes and XSD . 679
C.1.2.3.10.1 StopDepartureDelivery – Model Element . 679
C.1.2.3.10.2 StopDepartureRequest – Model Element . 680
C.1.2.3.10.3 StopDepartureRequestFilter – Model Element . 680
C.1.2.3.10.4 StopDepartureRequestPolicy – Model Element . 681
C.1.2.4 Schedule Query . 681
C.1.2.4.1 Schedule Request – Conceptual MODEL . 682
C.1.2.4.2 Schedule Request – Physical model – Overview . 682
C.1.2.4.3 Schedule Request – Physical model – Details . 683
C.1.2.4.4 Schedule Request – Attributes and XSD. 684
C.1.2.4.4.1 ScheduleDelivery – Model Element . 684
C.1.2.4.4.2 ScheduleRequest – Model Element. 685
C.1.2.4.4.3 ScheduleRequestFilter – Model Element . 685
C.1.2.4.4.4 ScheduleRequestPolicy – Model Element . 686
C.1.2.5 Trip Fare Query . 686
C.1.2.5.1 Common Fare Request Model . 686
C.1.2.5.1.1 Common Fare Request – Conceptual MODEL . 687
C.1.2.5.1.2 Common Fare Request – Physical model – Overview . 687
C.1.2.5.1.3 Common Fare Request – Physical model – Details . 688
C.1.2.5.1.4 Common Fare Request – Attributes and XSD . 689
C.1.2.5.2 Single Trip Fare Request Model . 691
C.1.2.5.2.1 Single Trip Fare Request – Conceptual MODEL . 691
C.1.2.5.2.2 Single Trip Fare Request – Physical model – Overview . 691
C.1.2.5.2.3 Single Trip Fare Request – Physical model – Details . 692
C.1.2.5.2.4 Single Trip Fare Request – Attributes and XSD . 693
C.1.2.5.3 Repeated Trip Fare Request Model . 694
C.1.2.5.3.1 Repeated Trip Fare Request – Conceptual MODEL . 695
C.1.2.5.3.2 Repeated Trip Fare Request – Physical model – Overview . 695
C.1.2.5.3.3 Repeated Trip Fare Request – Physical model – Details . 696
C.1.2.5.3.4 Repeated Trip Fare Request – Attributes and XSD . 697
Annex D (informative) How to go from a trip (from NeTEx Part 1&2) to a fare ? . 699
D.1 Passenger Trip . 699
D.1.1 Passenger Trip Model . 699
D.1.1.1 Passenger Trip – Conceptual MODEL . 699
D.1.1.2 Passenger Trip – Physical model – Overview . 701
D.1.1.3 Passenger Trip – Physical model – Details . 703
D.1.1.4 Passenger Trip – Attributes and XSD . 703
D.1.1.4.1 TripPattern – Model Element . 703
D.1.1.4.2 Trip – Model Element . 704
D.1.1.4.3 PtTrip – Model Element . 704
D.1.1.4.4 NonPtTrip – Model Element . 705
D.1.1.4.5 MixedTrip – Model Element . 705
D.1.1.5 Leg – Model Element . 705
D.1.1.6 RideLeg – Model Element . 706
D.1.1.7 PtRideLeg – Model Element. 706
D.1.1.8 TransferLeg – Model Element . 707
D.1.1.9 AccessLeg – Model Element . 707
D.1.1.10 LegTrack – Model Element . 708
D.1.2 Connection Leg Model . 708
D.1.2.1 Connection Leg – Conceptual MODEL . 708
D.1.2.2 PT Connection Leg – Physical model . 709
D.1.2.1 Connection Leg – Attributes and XSD . 710
D.1.2.1.1 PtConnectionLeg – Model Element . 710
D.1.3 Passenger Fare Offer Model . 712
D.1.3.1 Passenger Fare Offer – Conceptual MODEL . 712
D.1.3.2 Passenger Fare Offer – Physical model – Overview . 713
D.1.3.3 Passenger Fare Offer – Physical model – Details . 714
D.1.3.1 PT Fare Offer – Attributes and XSD . 714
D.1.3.1.1 PtFareOffer – Model Element . 714
Annex E (informative) Model for Parking Tariffs . 716
E.1 Parking Tariff . 716
E.1.1 Parking Tariff – Conceptual MODEL . 716
E.1.1.1.1 Parking Tariff – Physical model . 717
E.1.1.1.2 Parking Tariff – Attributes and XSD . 718
E.1.1.1.2.1 ParkingTariff – Model Element . 718
E.1.1.1.2.2 ParkingChargeBand – Model Element . 719
E.1.1.1.2.3 ParkingPrice . 720
Annex F (informative) Changes in Version . 722
F.1 Introduction . 722
F.2 General Changes . 722
F.3 List of Changes in 1.1 . 722
F.4 List of Changes in 2.0 . 729
Bibliography . 731
European foreword
This document (FprCEN/TS 16614-3: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-3:2021.
This document has been prepared under a Standardization Request given to CEN by the European
Commission and the European Free Trade Association and supports essential requirements of
EU Directive(s) /Regulation(s).
In addition, it supports the fundamental requirements for Urban Rail of CEN-CENELEC Guide 26.
This document presents Part 5 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. 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.
The full NeTEx 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 description of the passenger information European profile.
— Part 5 (this document) is the description of the alternative modes exchange format.
— Part 6 is the description of the European passenger information accessibility profile.
Part 1 is fully standalone. Parts 2,3, 4, 5 and 6 rely on Part 1 and possibly any other previous part.
The XML schema can be downloaded from http://netex-cen.eu (or directly from
https://github.com/NeTEx-CEN/NeTEx), 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; 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 the Parts 1 & 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 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 Part 1 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 is 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 and air journeys, but there has
not been any specific consideration of any additional requirements that apply specifically to air
transport.
Such modes can be operated, conventionally according to a fixed timetable, or flexibly as demand
responsive services.
Under development
Additionally, NeTEx v2.0 takes into account the alternative modes of operation such as cycle hire, taxis,
car-pooling, ride sharing. They have both network (i.e., places where services may be accessed),
service (i.e., the available services and how to book them), and fare aspects (i.e., the costs of different
services).
NeTEx v2.0 distinguishes the following types of 'mode of operation':
— conventional mode of operation: the legacy method of operation which is provided as a
scheduled and/or flexible publicly advertised flexible transport offer. This method of operation is
either following a fixed schedule and fixed routes or linked to a fixed network/schedule but offering
flexibility, in order for instance, to optimise the service or to satisfy passenger demand;
— alternative mode of operation: any publicly advertised mode of operation different from the
conventional mode of operation, in particular vehicle sharing, vehicle rental and vehicle pooling; and
— personal mode of operation: a private mode of transport excluding any publicly advertised use.
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 organisations; 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 following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at https://www.electropedia.org/
For the purposes of this document, the terms and definitions given in CEN/TS 16614-1:2019 and the
following apply.
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 accor
...
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...