Public transport - Network and Timetable Exchange (NeTEx) - Part 3: Public transport fares exchange format
|Publication Date:||1 April 2020|
|ICS Code (IT applications in transport):||35.240.60|
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/31) 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.
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.
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.
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 longdistance 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.
1 Under preparation.