COMMISSION IMPLEMENTING REGULATION (EU) …/...
of XXX
on a technical specification relating to the telematics subsystem of the rail system in the European Union for interoperability of data sharing in rail transport
and repealing Regulations (EU) No 454/2011 and (EU) No 1305/2014
(Text with EEA relevance)
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Directive (EU) 2016/797 of the European Parliament and of the Council of 11 May 2016 on the interoperability of the rail system within the European Union, and in particular Article 5(11) thereof,
Whereas:
(1)Point 1(b), third indent, of Annex II to Directive (EU) 2016/797 lists ‘telematics applications for passenger and freight services’ as a subsystem of the rail system that is described in point 2.6 of that Annex. Points 1.6.2 and 2.7 of Annex III to that Directive set out the essential requirements for that subsystem.
(2)The technical specifications applicable to the ‘telematics applications for passenger and freight services’ subsystem are currently set out in Commission Regulation (EU) No 454/2011, which relates to telematics applications for passenger services (‘TAP TSI’), and Commission Regulation (EU) No 1305/2014, which relates to telematics applications for the freight subsystem (‘TAF TSI’). Pursuant to Commission Delegated Decision (EU) 2017/1474, those two regulations are to be revised on the basis of a coherent set of objectives, which the Commission is to integrate into one technical specification for interoperability (‘TSI’), in order to take into account open source and open data architecture requirements, facilitate the emergence of through-ticketing, integrated ticketing and multimodal travel information and reservation systems, improve the performance of rail freight, facilitate logistics and operations of combined and multi-modal transport, include data that is to be exchanged with safety related applications and allow the European Union Agency for Railways (‘the Agency’) to assess the compliance of the telematics applications deployed against the requirement of the TSIs.
(3)Taking into account the relevant recommendations of the Agency, it is necessary to set out common technical and functional requirements for digital information sharing through interoperable data in respect of rail passenger and rail freight services. Those requirements should meet the changing needs of the rail sector and support the implementation of Union legislation in the single European rail area and the trans-European transport network (TEN-T), such as rail safety, network capacity management and network information, intermodal and multimodal digital information, paperless freight transport, rail passenger rights or reservation systems for integrated ticketing.
(4)In order to align the data sharing protocols relating to the telematics subsystem with the horizontal Union rules in this area, this Regulation should cover information systems and data sharing between data holders, on the one hand, and data recipients or data users, on the other, consistently with Regulation (EU) 2023/2854 of the European Parliament and of the Council, in particular Chapters III to V thereof, and Regulation (EU) 2022/868 of the European Parliament and of the Council.
(5)Rail related processes within the scope of this Regulation should cover capacity and traffic management, including the management of connections between trains and with other modes of transport, the management of freight wagons and their loading as well as the production of accompanying electronic freight documents and rail ticketing including the issuing of tickets across operators and modes of transport as well as rail passenger travel information. As a result, the definition of telematics stakeholders should include not only the rail infrastructure managers and railway undertakings but also any other stakeholders that carry out tasks which are part of those rail related processes.
(6)To ensure clear responsibilities in processes related to ticketing, it is necessary to specify that a railway undertaking or ticket vendor, as defined in Article 3, point (5), of Regulation (EU) 2021/782, may have one or more of the roles of ‘distributor’ or a ‘retailer’ of rail products, or as an ‘issuer’ of rail tickets. Relations between those entities may be subject to contracts the terms and conditions of which may be subject to Union or national legislation, including competition law and horizontal rules on data sharing.
(7)In order to develop the competitiveness of rail transport and to remove technical barriers, notably through the digitalisation of rail related processes, this Regulation should take stock of the proposals made in the Ministerial Declaration ‘Rail freight corridors to boost international rail freight’ endorsed by the Member States, Switzerland and Norway on 21 June 2016 in Rotterdam. In line with those proposals, it is therefore appropriate to lay down rules on data sharing within the logistic chain, including terminals and intermodal transport operators, on sharing up-to-date and forecast information about the movements of trains and the status of freight wagons and their loading to make rail freight transport more attractive and to better align intermodal logistics processes, and to harmonise safety and operational rules. Those rules should apply to telematics stakeholders having legal or contractual obligations to carry the rail related processes in the scope of this Regulation or those having an operational responsibility in those processes. A telematics stakeholder may have an operational responsibility that does not result directly from a legal or contractual obligation for example where train traffic information impacts different railway undertakings operating trains on the same network and their service providers or different rail transport services on that network and associated service providers.
(8)The operation of trains throughout the single European railway area requires seamless access to and interconnection with the information and communication systems used by the stakeholders involved in accordance with the latest technical developments, and should cater for testing of innovation.
(9)The Commission’s Guidelines on recommended standard licences, datasets and charging for the re-use of documents identify Creative Commons (‘CC’) licences as a recommended standard for public licences. CC licences are developed by a non-profit organisation and have become a leading licensing solution for public information across the world. It is therefore appropriate to refer to the most recent version of the CC licence suite, namely CC 4.0. In order to allow for additional arrangements due to ad hoc specificities of the data available for use, it should also be possible to use an open licence equivalent to the CC licence suite, as long as associated arrangements do not restrict the possibilities for reusing the data. It should also be possible to use an open licence equivalent to the CC licence suite, under certain conditions.
(10)Free access to information disseminated for public use is a fundamental right. Restricted availability of digital information on existing train services and routes, such as train traffic and timetable including conditions of carriage and connection times between access nodes, hinders potential customers from making informed decisions on their preferred transport options as well as the development of innovative applications or machine learning methods that may be integrated into an artificial intelligence. Therefore, that digital information should be available online for reuse in accordance with relevant access conditions set out under standard public licences, except where it should not be disclosed for train operations such as the transport of dangerous goods or military that are subject to security measures, or where commercial or personal data relating to the identification of business and associated owner should be protected. To ensure its maximum impact and to facilitate its use, that digital information should be available for reuse with minimal legal restrictions and free-of-charge. It should also be machine-readable, provided by means of application programming interfaces (‘APIs’) and, where relevant, provided as bulk download.
(11)Information relating to passenger services is mostly public under national or Union law. Therefore, technical conditions should be set for telematics stakeholders holding such information to grant access for use to the respective data sets.
(12)Urban nodes, as defined in Article 3, point (6), of Regulation (EU) 2024/1679, play an important role in the TEN-T network as starting points or destinations (‘first and last mile’) and are points of transfer within or between different passenger transport modes. Access to transport and travel information should reduce the detrimental effect of capacity bottlenecks and insufficient network connectivity. To foster the combination of transport services, information on access nodes in the same urban node may be grouped in one or more meta stations and digital information for journey planning, namely the timetable of passenger rail transport services and associated conditions of carriage, and the minimum connection time between different access nodes, should be publicly available online for use under standard and open public licences.
(13)In order to enable the telematics stakeholders concerned to provide passengers with information in accordance with Regulation (EU) 2021/782 of the European Parliament and of the Council and to allow ticket vendors to easily compare the rail products that are offered to them by railway undertakings, it is necessary to establish national access points as single points of access to accurate, complete, and up-to-date rail travel and traffic data based on specified data quality requirements.
(14)Horizontal Union rules on terms and conditions for business-to-business data sharing are set out in Article 8 of Regulation (EU) 2023/2854. As a consequence, any fees and charges for data sharing and access to data for use, or the use of telematics applications as APIs and web user interfaces, or the access for use to reference data pursuant to this Regulation should be reasonable and proportionate to the legitimate costs incurred for setting up, maintaining and using such APIs, web user interfaces or reference data.
(15)Horizontal essential requirements for interoperability of data, data sharing mechanisms and services, common European data spaces, data processing services, and for smart contracts executing data sharing agreements are laid down in Chapter VIII of Regulation (EU) 2023/2854. In order to help the rail sector fulfil those horizontal requirements and bring about a common European mobility data space which is interoperable with other European data spaces, a common central repository creating a single source of reference data and common Ontology for the Union rail system should be established and published through the EU Open Data Portal to cover the data necessary to implement the provisions of this Regulation. That repository should be based on an open data architecture and provide significant benefits as regards discoverability, accessibility, ease of collaboration, consistency and flexibility within rail data management. As system authority for telematics applications of the Union rail system, the Agency should be responsible pursuant to Article 23(1) and (3) of Regulation (EU) 2016/796 of the European Parliament and of the Council for the management of that repository and for the reference data necessary to share data in accordance with this Regulation. An appropriate transition period should be ensured to bring together data from the databases managed jointly by infrastructure managers or by a group of railway undertakings.
(16)Regulations (EU) 2016/679 and (EU) 2018/1725 of the European Parliament and of the Council apply in the context of processing of personal data in the application of this Regulation. Therefore, telematics stakeholders should use a single reference identifier when identifying their organisation and role in rail related processes. That identifier may be associated to personal data within the meaning of Regulation (EU) 2016/679 and Regulation (EU) 2018/1725.
(17)Network-specific data requirements (such as parameters or identifiers that are part of messages or messages specific to a network) used or intended to be used for data sharing as part of the deployment of the telematics subsystem or any national legal provision requiring their existence, should be based on national rules, within the meaning of Article 2, point (30), of Directive (EU) 2016/797 and Article 3, point (8) of Directive (EU) 2016/798 of the European Parliament and of the Council, that are positively assessed in accordance with Articles 25 and 26 of Regulation (EU) 2016/796.
(18)In order to update the specifications referenced in this Regulation, the Agency should define, publish and apply a change control management procedure pursuant to Articles 5(9) and 23(2) of Regulation (EU) 2016/796. To ensure a coordinated development of telematics applications and monitor their deployment in the Union pursuant to Article 23(1) and (4) of Regulation (EU) 2016/796, the Agency should identify updates for these specifications and where relevant propose implementation dates for their application.
(19)A framework should be established for railway undertakings sharing roles and responsibilities for the operation of a direct train across one or more networks to ensure consistent data sharing throughout the whole journey.
(20)For multi-network digital processes to be fit for the delivery of the single European railway area, telematics applications for interoperable data sharing should be based on standardise APIs and web user interfaces. The interfaces between those tools and users should comply with the minimum rules on ergonomics and health protection.
(21)To facilitate digital access to data sharing systems for capacity management, train preparation, and train traffic management, one infrastructure manager in each Member State could act as single point of contact, in particular in relation to multi-network rail transport services.
(22)To ensure fair competition between railway undertakings and to guarantee full transparency and non-discriminatory access to their service facilities pursuant to Article 13 of Directive 2012/34/EU, station managers should define the default minimum time for passengers to connect the access nodes of different passenger transport services.
(23)In order to set out the strategy for the application of this Regulation pursuant to Article 4(3), point (h), of Directive (EU) 2016/797, including the provisions applicable to the existing subsystem and the stages to be completed for a gradual transition to a target subsystem pursuant to point (f) of that Article, a timescale and the gradual milestones pursuant to Article 4(4) of that Directive should be established.
(24)To assist the Commission pursuant to Article 23(4) of Regulation (EU) 2016/796 in the monitoring of the deployment of telematics applications in accordance with this Regulation, the Agency should automate the digital collection information from telematics stakeholders on their implementation plans and the status of implementation of this Regulation and publish figures aggregated at national and Union level. Reporting obligations should be limited to key telematics stakeholders and to the monitoring of implementation until compliance with the requirements of this Regulation is achieved.
(25)To facilitate the monitoring of the deployment of telematics applications in accordance with this Regulation and enable follow-up actions, this Regulation should allow the Agency as system authority for telematics to assess the compliance of telematics applications with this Regulation in case of doubt or complaints based on self-declaration of telematics stakeholders. To that end, the Agency should develop web applications enabling telematics stakeholders to automate their self-declaration of compliance based on the testing procedures specified in this Regulation and to notify the corresponding results to the Agency.
(26)To foster the advancement of this TSI by the Agency, the Commission should entrust the Agency pursuant to Article 40(2) of Regulation (EU) 2016/796 with the task of promoting innovation that aims at improving the use of new information technologies, timetable information and tracking and tracing systems.
(27)In order to facilitate a coordinated and harmonised implementation of this Regulation at national and Union level, national contact points (‘NCP’), established pursuant to Article 5(3) of Regulation (EU) No 1305/2014 and Article 6 of Regulation (EU) No 454/2011, should support the Agency. To allow a coherent implementation between freight and passenger services, the tasks of the NCP should be undertaken by one single entity. An infrastructure manager may be tasked with acting as the NCP, where necessary in cooperation with other entities providing specific expertise.
(28)In order to ensure consistency of the information on passenger rail transport services related to access nodes for multimodal purposes with the single source of reference data at Union level, data holders should consistently use reference data such as location codes assigned by the Agency when providing access to data via national access points. To that effect, the NCP should facilitate interaction between national telematics stakeholders and the Member States, which are responsible for setting up national access points.
(29)The Agency, acting as the system authority for telematics applications pursuant to Article 23 of Regulation (EU) 2016/796, should coordinate the development of telematics applications, manage change requests and system versions and monitor the deployment of telematics applications through relevant working parties established pursuant to Chapter 2 of that Regulation.
(30)Since certain terms reflecting the structure of the data shared are widely accepted and used in one language, such terms in the Annex should remain in the widely accepted technical language used for telematics
(31)This Regulation should be aligned with other TSIs developed pursuant to Directive (EU) 2016/797, in particular with Commission Implementing Regulation (EU) 2019/773 for operation and traffic management (‘OPE TSI’), Commission Implementing Regulation (EU) 2023/1695 regarding control-command and signalling (‘CCS TSI’), Commission Regulation (EU) No 1300/2014 regarding persons with disabilities and persons with reduced mobility (‘PRM TSI’), and Commission Regulation (EU) No 1304/2014 regarding rolling stock (‘NOI TSI’).
(32)Point 4.2.3.3.2 of the Annex to Implementing Regulation (EU) 2019/773 requires the railway undertaking to inform the infrastructure manager when a train is ready for access to the network. Currently, that requirement is implemented in different ways depending on infrastructure characteristics (for example, Railway Mobile Radio (RMR) systems, dedicated interlocking at departure point, dedicated telematics message). Point 4.2.4 of Annex I to Implementing Regulation (EU) 2023/1695 sets out requirements for mobile communication functions for railways (RMR), which for GSM-R Voice and operational communication applications mandate the application of system requirements specification referenced in index [33] of Appendix A to that Annex. These requirements specify the dialling code to be used for ‘train ready’ and ‘train not ready’ respectively. For the purposes of this Regulation, those options for communicating on train readiness should be limited and harmonised.
(33)Regulations (EU) No 454/2011 and (EU) No 1305/2014 should therefore be repealed.
(34)To allow for sufficient return on investments of projects which aim at implementing the telematics subsystem in accordance with Regulations (EU) No 454/2011 and (EU) No 1305/2014 and which, on the date of entry into force of this Regulation, are at an advanced stage of development within the meaning of Article 2, point (23), of Directive (EU) 2016/797, it is necessary to set an appropriate transition period for corresponding telematics stakeholders to comply with this Regulation, without prejudice to Article 7(1), point (a), of that Directive.
(35)To support the digitalisation of rail related processes within rail service facilities and to facilitate a gradual and timely implementation of interoperable data sharing by their operators, it is necessary to set an appropriate transition period for operators of rail service facilities to comply with this Regulation.
(36)To facilitate a gradual and timely deployment of the technical tools to be provided by the Agency for the coordinated development of telematics applications in the Union and the management of their specifications, the date of application of this Regulation should be deferred in relation to the delivery by the Agency of those tools.
(37)The European Data Protection Supervisor was consulted in accordance with Article 42(1) of Regulation (EU) 2018/1725 and delivered an opinion on [xx°xxxx°2025].
(38)The measures provided for in this Regulation are in accordance with the opinion of the committee referred to in Article 51 of Directive (EU) 2016/797,
HAS ADOPTED THIS REGULATION:
Chapter 1
General provisions
Article 1
Subject matter
This Regulation lays down common, specific and interface requirements for interoperable data sharing in rail transport by establishing a technical specification for interoperability (TSI) relating to the ‘telematics applications for passenger and freight services’ subsystem of the rail system in the Union, as set out in the Annex.
Article 2
Scope
1.This Regulation applies to ‘telematics applications for passenger and freight services’ referred to in point 1(b), third indent, of Annex II to Directive (EU) 2016/797 and described in point 2.6 of that Annex, with regard to the following processes:
(a)as regards both freight services and passenger services:
(i)capacity management;
(ii)train preparation;
(iii)traffic management;
(b)as regards freight services only: management of freight wagons and their loading;
(c)as regards passenger services only:
(i)rail ticketing;
(ii)rail passenger travel information.
2.This Regulation applies to the Union rail system.
3.In the case of rail transport services leaving or entering the Union to or from a third country not subject to the application of this Regulation or similar rules under an international agreement, telematics stakeholders may apply alternative measures between the border and the border station designated for cross-border operations.
Article 3
Definitions
For the purposes of this Regulation, the following definitions apply:
(1)‘data’ means a machine-readable representation of acts, facts or information and any compilation of such acts, facts or information intended to be shared in a harmonised and structured format;
(2)‘data sharing’ means the provision of data by a data holder to a data recipient for the purpose of the joint or individual use of such data, directly or through an intermediary, for example under open or commercial licences subject to a fee or free of charge;
(3)‘rail ticketing’ means the process comprising at least one of the following in relation to passenger rail transport services:
(a)the digital presentation of such services for journey planning;
(b)the digital checking of the availability or reservation of corresponding rail products for sales;
(c)the issuing of digital tickets;
(d)the digital handling of after sale processes;
(1)‘rail product’ means a tailored passenger rail transport service linked to a fare and to the conditions of carriage, and which proof of purchase is a ticket or a reservation;
(2)‘ticket’ means a ticket as defined in Article 3, point (7), of Regulation (EU) 2021/782;
(3)‘reservation’ means a reservation as defined in Article 3, point (8), of Regulation (EU) 2021/782;
(4)‘rail transport service’ means a scheduled service for carriage by rail between a point of departure and a point of arrival and covers transport services for goods, passengers, luggage, bicycles or cars, and tailored transport arrangements, as well as passenger assistance including services for re-routing and journey continuation;
(5)‘operator of rail service facility’ means any public or private entity responsible for managing one or more rail passenger stations or multimodal freight terminals of the trans-European transport network listed in Annex II to Regulation (EU) 2024/1679 to facilitate the supply of one or more services referred to in points 2, 3 and 4 of Annex II to Directive 2012/34/EU;
(6)‘telematics stakeholder’ means the following data holders or data recipients whose activities entail the use of telematics applications for passenger and freight services’:
(a)railway undertakings;
(b)infrastructure managers;
(c)operators of rail service facilities;
(d)intermodal transport operators;
(e)applicants for capacity allocation;
(f)railway undertakings or ticket vendors, as defined in Article 3, point (5), of Regulation (EU) 2021/782, where those undertakings or vendors act as either a retailer, a distributor or an issuer in the processes referred to in Article 2(1), point (c);
(g)freight customers;
(h)entities in charge of maintenance as defined Article 3, point (20), of Directive (EU) 2016/798;
(i)third-party service providers that either have an operational responsibility in the functioning of the rail system or in supporting the delivery of passenger or freight rail transport services, or that are contracted to monitor the movements of trains or the flow of passengers or goods;
(j)holders of a transport contract relating to a specific train or to a specific type of rail transport service;
(k)any other entity that is involved in the operation of telematics applications, in relation to the elements of the subsystem referred to in point 2.6 of Annex II to Directive (EU) 2016/797;
(1)‘Union bodies’ means Union bodies as defined in Article 2, point (27), of Regulation (EU) 2023/2854;
(2)‘public sector body’ means public sector body as defined in Article 2, point (28), of Regulation (EU) 2023/2854;
(3)‘data holder’ means a natural or legal person that has the right to use or an obligation to produce and make available data;
(4)‘data recipient’ means a natural or legal person that has the right to access for use the data produced and made available by the data holder under specified access conditions for use;
(5)‘access to data’ means the right to consult the data with or without having control of that data and distinctively from other rights and obligations relating to the use of that data for non-commercial or commercial purposes;
(6)‘national access point’ means a national access point within the meaning of Article 3 of Commission Delegated Regulation (EU) 2017/1926;
(7)‘ERA Ontology’ means a technical document issued by the Agency pursuant to Article 4(8) of Directive (EU) 2016/797, setting out human-readable and machine-readable data definitions and presentations and the associated quality and accuracy requirements for data elements of the Union rail system;
(8)‘data element’ means a field, value, or attribute of the data shared, which is structured in a consistent manner with the overall protocol used for data sharing and carries essential information that contributes to the meaning and purpose of the data shared, enabling data sharing between systems, applications or organisations;
(9)‘reference data’ means standardised and interoperable single identifiers to be used as a basis for data sharing in a specific domain;
(10)‘metadata’ means metadata as defined in Article 2, point (2), of Regulation (EU) 2023/2854;
(11)‘application programming interface’ or ‘API’ means a set of functions, procedures, definitions and protocols for interoperable data sharing between telematics applications;
(12)‘station manager’ means a station manager as defined in Article 3, point (3), of Regulation (EU) 2021/782;
(13)‘minimum connection time’ means the minimum amount of time that is considered by the station managers involved to be sufficient for a passenger to connect between the access nodes of two consecutive passenger transport services included in a journey;
(14)‘person with disabilities’ and ‘person with reduced mobility’ means person with disabilities and person with reduced mobility as defined in point 2.2 of the Annex to Commission Regulation (EU) No 1300/2014;
(15)‘journey’ means an end-to-end trip of a passenger that can include multiple legs;
(16)‘boarding time limit’ means the point in time when access to the train, platform or station is closed in preparation for departure and after which passengers are no longer allowed to board;
(17)‘alighting time’ means the point in time when the doors of the train are opened at the destination platform or terminal and disembarkation is allowed;
(18)‘working timetable’ means working timetable as defined in Article 3, point (28), of Directive 2012/34/EU that is used for capacity and traffic management as referred to in Section 2 of the Annex to this Regulation;
(19)‘meta station’ means a geofence area within a functional urban area, including an urban node listed in Annex II to Regulation (EU) 2024/1679, that may extend across multiple Member States and where distinct stations can be reached by connecting urban transport modes and urban transport services, whether scheduled or unscheduled;
(20)‘access node’ means access node as defined in Article 2, point (25), of Delegated Regulation (EU) 2017/1926;
(21)‘applicant’ means applicant as defined in Article 3, point (19), of Directive 2012/34/EU;
(22)‘passenger timetable’ means the date and time of transport services offered by a railway undertaking during a given time interval that is used in the context of rail ticketing and rail passenger travel information referred to in Section 4 of the Annex;
(23)‘shunting operator’ means an operator responsible for shunting movements as defined in Table 1 of the Annex to Implementing Regulation (EU) 2019/773;
(24)‘freight customer’ means the entity that has issued the consignment note and which may be an intermodal transport operator or a fleet manager of empty wagons;
(25)‘intermodal transport operator’ means an entity that organises freight transport services connecting two or more freight terminals with more than one transport mode and which may be a shipper, a logistics service provider, or a freight forwarder;
(26)‘consignment note’ means a transport document referred to in Article 6 of Council Regulation No 11;
(27)‘distributor’ means an entity that has the legal and technical capacity to combine rail products of one or more railway undertakings into an offer, for an issuer or a retailer, and that has autonomous rights to use its own journey planner and to check the availability of fares for a rail transport services;
(28)‘issuer’ means an entity that has the legal and technical capacity to issue, for a retailer, a ticket identifying the parties to the transport contract;
(29)‘attributing system’ means the railway undertaking’s digital system that hosts the online catalogue of individual transport services and that enables distributors to check the availability of those services and make reservations;
(30)‘retailer’ means an entity that has the legal and technical capacity to sell a rail product offered by a distributor with a fixed fare without autonomous rights to amend the content or conditions of the fare but that can use its own pricing engine to apply fees or reductions;
(31)‘tariff’ means the amount linked to specific categories or set of fares for a given transport service;
(32)‘fare’ means the amount fixed by a distributor for a given rail product offered to a retailer;
(33)‘ticket control organisation’ or ‘TCO’ means an organisation empowered to inspect passenger tickets, including at platform access doors;
(34)‘data quality’ means the degree to which the characteristics of data satisfy the stated and implied level of accuracy, completeness, consistency, timeliness and uniqueness of datasets, and their ability to create actionable insights for other users under specified conditions.
Chapter 2
General rules and principles
Article 4
Data sharing between telematics stakeholders and rights to access data
1.Where telematics shareholders have rights or obligations on the basis of a legal or contractual provisions in relation to the processes referred to in Article 2(1), they shall share data specified in the Annex that are necessary to carry out those processes or provide mutual access for use to that data.
Except for the processes referred to in Article 2(1), point (c)(i), those rights and obligations referred to in the first subparagraph may also result from an operational responsibility.
2.Upon request of the Commission, of a Union body or of a public sector body, telematics stakeholders that hold data specified in the Annex shall grant access to those data for one the following purposes:
(a)the monitoring of the establishment of the single European rail area;
(b)the development of rail interoperability and safety in the Union;
(c)the control or the monitoring of the flow of passengers or goods in the Union.
Article 5
Access to train traffic data and train composition data
1.In addition to the obligations set out in Article 4, each infrastructure manager and each operator of rail service facilities shall grant via a publicly available common Union web user interface, public and free of charge access to the following data in accordance with the specifications and access conditions as follows:
(a)working timetable data referred to in point 2.3 of the Annex;
(b)train traffic data referred to in point 2.6 of the Annex;
(c)train composition data referred to in point 2.5.1 of the Annex that infrastructure managers and operators of rail service facilities receive from railway undertakings.
2.A Member State or an infrastructure manager may restrict public access to the data referred to in paragraph 1 for those trains whose operation is subject to national security measures.
3.Upon request of a freight railway undertaking and without prejudice to the rights of other telematic stakeholders to access that data pursuant to Article 4, an infrastructure manager or an operator of rail service facilities shall restrict access to the public for the following elements of the data referred to in paragraph 1, point (c), received from that undertaking:
(a)the identifier of that undertaking in accordance with Article 7(1);
(b)the wagons’ technical data and wagons’ operational data.
Article 6
Access to data for journey planning of passenger services and to tariff data
1.In addition to the obligations set out in Article 4, each passenger railway undertaking shall grant public and free of charge access to data specified in points 4.2.1 and 4.4 of the Annex regarding the passenger timetable of the rail transport service that it operates and for corresponding conditions of carriage, respectively. Access shall be granted via the national access points in accordance with the specifications and access conditions set out in the Annex.
2.In addition to the obligations set out in Article 4, each station manager shall grant public and free of charge access to data specified in point 4.2.2 of the Annex regarding connection times between access nodes. Access shall be granted via the national access points in accordance with the specifications and access conditions set out in the Annex.
3.In addition to the obligations set out in Article 4, access to tariff data that are specified in point 4.3 of the Annex, including for yielded tariffs, shall be granted in accordance with the specifications and access conditions set out in that point, as follows:
(a)where information on tariffs for a rail passenger transport service is made available to the public on the basis of legal provisions, the railway undertaking operating that service shall grant public access to that data via national access points;
(b)where information on tariffs for a rail passenger transport service is made available on the basis of contractual agreements, the railway undertaking operating that service shall grant access to that data at least via national access points; those agreements may set out additional terms and conditions for the use of that data.
4.The obligation to grant access to data pursuant to paragraphs 1, 2 and 3 shall also apply to any other holder of those data, where relevant.
Article 7
Cybersecurity and data format
1.Telematics stakeholders, Union bodies and public sector bodies involved in the implementation of this Regulation shall be identified through a single identifier of their organisation assigned and validated in accordance with Article 9.
2.Where a telematics stakeholder shares and grants access to data pursuant to this Regulation, it shall ensure that the communication networks and protocols, systems, interfaces or databases it uses comply with the cybersecurity measures set out in point 1.3 of the Annex.
3.Where a telematics stakeholder shares and grants access to data pursuant to this Regulation, it shall comply with the data format specified in the data catalogue elements referred to in point 1.4 of the Annex as subsets of the ERA Ontology.
4.The Agency shall ensure that the ERA Ontology and associated specific data catalogue elements reflect regulatory and technical developments affecting the Union rail system.
Article 8
Common central repository and reference data
1.The Agency shall maintain a common central repository as a single source of common Union rail data for telematics. The repository shall be made available to the public and shall store the following information:
(a)metadata and associated specific data catalogue elements, that are referred to in point 1.4 of the Annex as a subset of the ERA Ontology, specifying the content and the structure of the data;
(b)a list of certification authorities for public key infrastructure (‘PKI’) established in accordance with the requirements set out in point 1.3 of the Annex;
(c)common reference data, referred to in Article 9, managed by the Agency;
(d)a link to access the source of freight specific reference data, referred to in point 3.3 of the Annex, managed by the rail sector.
2.The Agency shall enable any telematics stakeholder to subscribe to automated notifications regarding any update to the information associated with the common central repository.
3.A telematics stakeholder may replicate for its own operational use the data available in the common central repository.
4.The Agency and each telematics stakeholder responsible for reference data shall take the following steps:
(a)make publicly available and free of charge their reference data for reuse in accordance with the specifications and access conditions set out in the Annex, as well as the service level conditions applied to their availability and accessibility;
(b)manage allocation, maintenance and storage of, and access to, their reference data in a transparent, fair, reasonable, and non-discriminatory manner.
Article 9
Governance of common reference data
1.The Agency shall manage and assign common reference data in the form of single reference identifiers (‘codes’), used or intended to be used by telematics stakeholders in respect of the processes referred to in Article 2(1) to identify the following data elements:
(a)geographical points (‘location codes’) referred to in point 1.2.1 of the Annex;
(b)entities (‘organisation codes’) involved in data sharing in accordance with acts adopted pursuant to Directive (EU) 2016/797 or Directive (EU) 2016/798 or Directive 2012/34/EU of the European Parliament and of the Council, referred to in point 1.2.2 of the Annex;
(c)ticketing aspects (‘code lists for ticketing’) referred to in point 4.8 of the Annex.
2.A telematics stakeholder shall submit to the Agency requests for the assignment of codes. The request shall be in accordance with the specifications for common reference data set out in point 1.2 of the Annex.
3.The Agency shall provide telematics stakeholders with web applications to allow them to submit requests for the assignment of codes and the updating of associated data elements. The Agency shall publish a user manual describing the different functions of the web applications.
4.The Agency shall publish and apply the procedures for managing requests for the assignment of codes and the updating of associated data elements, including associated language arrangements in accordance with Article 74 of Regulation (EU) 2016/796 and deadlines. That manual shall provide guidance to telematics stakeholders for the submission of requests.
5.Where a telematics stakeholder submits a request for the assignment of a location code outside of the scope of the Union’s rail network referred to in Annex I, point 1, of Directive (EU) 2016/797, the Agency shall assign a location code as a virtual extension of the rail network (‘virtual location code’) in the following cases:
(a)where the location is used by transport services that replace rail transport services temporarily;
(b)where the location is used by transport services sold as rail transport services that are not operated by railway undertakings;
(c)where the location is considered a meta station.
6.The Agency shall link the location codes with relevant infrastructure data available in the register of the railway infrastructure (the ‘RINF’) referred to in Article 49 of Directive (EU) 2016/797 and store them.
7.By [14 December 2025], each infrastructure manager and each operator of rail service facilities shall link the relevant infrastructure data in the RINF with the location codes assigned to them before the entry into force of this Regulation.
8.Where, for passenger rail transport services, a telematics stakeholder refers to access nodes via national access points, it shall use location codes managed and assigned by the Agency pursuant this Article.
Article 10
Data quality
1.The Agency and each telematics stakeholder shall ensure that their reference data comply with the data quality criteria and nominal values set out in point 1.5 of the Annex and meet an appropriate level of integrity and reliability.
2.Where a telematics stakeholder shares or grants access to data pursuant to this Regulation, it shall ensure that that data meets an appropriate level of integrity and reliability, contains the reference data referred to in paragraph 1, and complies with the data quality criteria and nominal values set out in point 1.5 of the Annex.
3.Each telematics stakeholder shall ensure that data replicated from the common central repository preserves the same quality level.
4.Where a telematics stakeholder shares or grants access to data pursuant to this Regulation, it shall perform quality assurance checks. Any deficiencies identified in the data quality shall be corrected as soon as possible.
5.Each telematics stakeholder shall establish processes for recurrent quality assurance checks against each of the data quality criteria, for at least a selection of routes and locations of reference.
Article 11
Network-specific data requirements
1.By [Publication Office: date of entry into force + 9 months], each infrastructure manager shall notify to its national safety authority the network-specific data requirements it applies or intends to apply and a justification thereof, and shall inform the national contact point accordingly.
2.National safety authorities shall verify the justification provided by the infrastructure managers and that the network-specific data requirements referred to in paragraph 1 are within the scope of a national rule that has been positively assessed by the Agency pursuant to Articles 25 and 26 of Regulation (EU) 2016/796.
3.Each infrastructure manager shall notify to the Agency its network-specific data requirements positively assessed by the national safety authority pursuant to paragraph 2 using a template provided by the Agency to notify such data requirements.
4.The Agency shall publish a machine-readable list of network-specific data requirements notified to it pursuant to paragraph 3.
5.Telematics stakeholders shall only apply those network-specific data requirements that are published by the Agency in accordance with paragraph 4.
Article 12
Updates to referenced specifications
1.The Agency shall manage a change control management procedure to update the specifications referenced in Appendix C of the Annex to this Regulation.
2.Where the Agency issues opinions pursuant to Article 10(2) and (3), or Article 19(1), point (d), of Regulation (EU) 2016/796 identifying updates constituting acceptable means of compliance, it shall, where relevant, propose implementation dates for their application.
3.The Agency shall keep Member States informed of the activities pursuant to paragraphs 2 and 3 through the committee referred to in Article 51(1) of Directive (EU) 2016/797.
Article 13
Lead railway undertaking
1.Where a direct rail transport service is operated or intended to be operated by several railway undertakings, those undertakings shall designate one of them to be the lead railway undertaking responsible to ensure, for the entire service, consistency and integration of the data shared and made accessible pursuant to this Regulation.
Where a direct rail transport service is operated or intended to be operated by a single railway undertaking, that undertaking shall be the lead railway undertaking.
2.The lead railway undertaking shall be responsible for the following tasks that are part of the processes referred to in Article 2(1):
(a)integrating consistently the identification number of the train (‘reference train identifier’) with other object identifiers in accordance with the specifications set out in point 2.1 of the Annex;
(b)coordinating the railway undertakings and other applicants involved in relation to capacity management in accordance with the specifications set out in point 2.3 of the Annex;
(c)aggregating passenger timetable data for that service, in accordance with the specifications set out in point 4.2 of the Annex, where it differs from the working timetable;
(d)monitoring the movement of freight wagons and their loading;
(e)integrating and sharing consignment note data in case of a freight service and act as a single point of contact for that service.
3.At least for the tasks referred to in paragraph 2, the lead railway undertaking shall act as a single point of contact for data sharing in relation to a direct rail transport service.
Article 14
Telematics application for data sharing
1.Where a telematics stakeholder shares or grants access to data pursuant to this Regulation, it shall use a telematics application. That application shall be an application programming interface (‘API’) for machine-to-machine data sharing or a web user interface (‘web UI’) for human-to-machine data sharing provided by another telematics stakeholder as an alternative.
2.Each telematics stakeholder shall ensure that the telematics applications it uses or provides comply with the specifications set out in point 1.7 of the Annex and ensures non-discriminatory data sharing.
3.Two or more telematics stakeholders may jointly use or provide one telematics application.
4.In the areas of capacity management, train preparation and traffic management, each infrastructure manager shall both use an API and provide web UIs for its network as part of the minimum access package laid down in point 1 of Annex II to Directive 2012/34/EU.
5.In the areas of multi-network capacity management, train preparation and traffic management:
(a)infrastructure managers shall jointly both use a common Union API and provide common Union web UIs;
(b)operators of rail freight service facilities may jointly use a common Union API and provide common Union web UIs.
6.In the area of the management of freight wagons and their loading, freight railway undertakings or operators of rail service facilities may jointly use a common Union API and provide common Union web UIs.
Article 15
Connection time and passenger information in stations
1.Each station manager or infrastructure manager shall, for the stations under its responsibility, define in a neutral and non-discriminatory manner, the following minimum connection times in accordance with the requirements set out in point 4.2.2.1 of the Annex and where relevant in cooperation with other station or infrastructure managers:
(a)the minimum connection time between access nodes of:
(i)different passenger rail transport services within the station;
(ii)different passenger rail transport services of different stations that are part of the same meta station;
(iii)different passenger rail transport services and other scheduled passenger transport services that serve the same station and may be connected;
(b)the minimum connection time adapted to persons with disabilities and persons with reduced mobility;
(c)the minimum connection time adapted to a passenger transporting a bicycle.
2.Each station manager or infrastructure manager shall, for the stations under its responsibility, gather information on the additional time requested by railway undertakings or public authorities for the check-in of passengers, bicycles, or luggage, and include that additional time in the minimum connection time where it is part of the conditions of carriage.
3.Each station manager or infrastructure manager shall, for the stations under its responsibility, define in a neutral and non-discriminatory manner, the most appropriate information system to be installed in the station to provide integrated train traffic and train composition rail passenger information in the station area in accordance with the requirements set out in point 4.7.1 of the Annex.
4.For the purposes of paragraphs 1, 2 and 3 of this Article, passenger railway undertakings, passenger organisations, station managers, infrastructure managers and, where appropriate, the competent authority as defined in Article 2, point (b), of Regulation (EC) No 1370/2007 of the European Parliament and of the Council, shall cooperate with a station manager or an infrastructure manager upon the latter’s request.
Chapter 3
Implementation
Article 16
Implementation deadlines
1.Each telematics stakeholder shall ensure that any new telematics applications it deploys after the entry into force of this Regulation comply with this Regulation.
2.As regards its existing telematics application, each telematics stakeholder shall follow the milestones set out in Appendix G of the Annex to ensure that those applications and the data shared or made accessible through them comply with this Regulation for the following processes carried out in relation to the working timetables that apply after:
(a)[14 December 2025], as regards rail ticketing and rail passenger travel information;
(b)[13 December 2026], as regards capacity management, train preparation, traffic management and the management of wagons.
3.For the purposes of paragraph 2, point (b), an additional transitional period of [12 months] shall apply to operators of rail service facilities.
4.Where the planning or the implementation of the telematics subsystem in accordance with Regulations (EU) No 454/2011 or (EU) No 1305/2014 has reached a point where its compliance with this Regulation may compromise the viability of the putting into service of this subsystem, the deadlines set out in paragraphs 2 and 3 may extended by [12 months].
Article 17
Reporting obligations
1.Until proof of compliance of their telematics applications is provided pursuant to Article 18, the following telematics stakeholders shall report in an accurate and transparent manner on the status of their implementation and about their implementation plans to meet the milestones set out in Appendix G of the Annex, in accordance with the following conditions:
(a)in areas of capacity management, train preparation and traffic management:
each infrastructure manager shall report no later than [Publication Office: date of entry into force + 9 months];
(b)in the area of train preparation:
each railway undertaking shall report no later than [Publication Office: date of entry into force + 18 months];
(c)in the area of the management of freight wagons and their loading:
each freight railway undertaking shall report no later than [Publication Office: date of entry into force + 18 months];
(d)in areas of rail ticketing and rail passenger travel information:
each passenger railway undertaking and each station manager shall report no later than [Publication Office: date of entry into force + 18 months].
2.Telematics stakeholders shall coordinate their efforts in drawing up their implementation plans. Each Member State shall support national coordination or delegate the task to the national contact point.
3.The Agency shall provide a web application supporting telematics stakeholders’ reporting. That web application shall enable automated data import from telematics applications deployed by telematics stakeholders to support their implementation reporting.
4.The Agency shall publish aggregated figures about the status of the implementation and the implementation plans per Member State and at Union level, linked to the network size for infrastructure managers and to market share of railway undertakings expressed as tonnes/km and passengers/km, respectively.
Article 18
Compliance assessment
1.Each telematics stakeholder subject to reporting obligations pursuant to Article 17 shall self-assess the compliance of its telematics applications in relation to the data shared and submit corresponding results to the Agency. Telematics applications in use on the date of entry into force of this Regulation shall be assessed before the implementation deadlines set out in Article 16 in relation to the data shared though them.
2.The Agency shall provide a web application enabling telematics stakeholders to submit individual messages for automated self-assessment as a means to provide a presumption of compliance of their telematics applications. The submission shall comply with the testing procedure set out in point 1.6 of the Annex. The Agency shall publish a user manual describing the different functions of the web applications.
3.Where self-assessment results are positive, the web application shall perform all the following functions:
(a)issue an automated evidence-based declaration providing to the submitting telematics stakeholder and to the Agency a presumption of compliance of submitted messages;
(b)compile the associated use-case documentation;
(c)generate and publish a list of telematics applications which are presumed to be compliant.
4.Where a telematics stakeholder uses a telematics application to share data specified in the Annex, compliance shall only be subject to a self-assessment of that telematics application.
5.Where a telematics application has been subject to a positive compliance assessment delivered and published by the Agency before the date of entry into force of this Regulation, such an assessment shall remain valid unless changes are made to it.
6.Changes to a telematics application shall be subject to a new self-assessment where such changes have an impact on one of the following:
(a)the data elements or data structure to be shared pursuant to this Regulation;
(b)the implementation of a new or updated telematics application;
(c)the functional implementation of the processes referred to in Article 2(1).
7.In case of alleged non-compliance of a telematics application of a telematic stakeholder, or in case of doubt, the Agency shall, upon request of an authority or another telematics stakeholder, evaluate the correctness of the self-assessment based on the use-case documentation submitted. The Agency shall inform the requesting entity and the submitting telematics stakeholder of the result of its evaluation.
8.For projects for telematics applications in respect of which an application for Union financial support has been submitted, the Agency may evaluate the correctness of the self-assessment on the basis of the use case documentation submitted.
9.The Agency may lay down the procedures for evaluating the correctness of the self-assessment for the purposes of paragraphs 7 and 8, including deadlines.
Article 19
Innovative solutions
1.Where a telematics stakeholder intends to use an innovative solution for a telematics application not envisaged by this Regulation, it shall submit the technical file associated with the proposed innovative solution to the Commission for analysis and declare how interoperable interfaces with other telematics stakeholders can be ensured. The Commission shall request the opinion of the Agency pursuant to Article 10(2) of Regulation (EU) 2016/796 on the proposed innovative solution.
2.Where the Agency’s opinion is negative, the innovative solution proposed cannot be applied.
3.Where the Agency’s opinion is positive, the appropriate functional and interface specification and the testing procedure to allow the use of such innovative solution shall be developed and may subsequently be included as part of the revision process laid down in Article 5 of Directive (EU) 2016/797.
4.In addition to the provisions of paragraph 3, the Agency may consider in its positive opinion that the innovative solution constitutes an acceptable means of compliance pursuant to Article 6(3) of Directive (EU) 2016/797. In that case, that positive opinion may be used to assess the compliance of the innovative solution with this Regulation.
Article 20
National contact point
1.Member States shall designate a national contact point (‘NCP’) with appropriate resources to carry out the following tasks:
(a)act as Member State representative in the working party referred to in Article 22, cooperate with the Agency and other NCPs, and share with the working party relevant operational views and issues reported by telematics stakeholders in a transparent and non-discriminatory manner;
(b)collect and share with the Agency relevant market shares and contact details of telematics stakeholders subject to Article 17;
(c)facilitate contacts between Member States, telematics stakeholders at national level, the Agency, the Commission, and other relevant organisations;
(d)support a coordinated implementation of the provisions of this Regulation by facilitating:
(i)return of experience and exchange of best practices among telematics stakeholders at national level, as well as at Union level in the working party referred to in Article 22;
(ii)coordination of infrastructure managers' implementation plans and consultation of other telematics stakeholders through the rail sector representative bodies listed by the Commission pursuant to Article 38(4) of Regulation (EU) 2016/796;
(iii)integration of prospective telematics stakeholders informing them about the applicable framework.
2.Member States shall designate an NCP among the representatives of either of the following entities:
(a)a public sector body independent from railway undertakings or other applicants;
(b)an infrastructure manager.
3.For the purposes of paragraph 1, where a Member State decides to appoint different actors in relation to the processes referred to in Article 2(1), it shall designate an entity acting as NCP responsible for ensuring coordination of such actors at national level and providing a single contact point for the Agency, the Commission, and other relevant organisations.
4.By [Publication Office: date of entry into force + 12 months], each Member State shall communicate to the Agency the details of the designated NCP. The Agency shall publish such details.
5.Where a Member State has not explicitly designated an NCP pursuant to paragraph 4, the Agency shall address the main infrastructure manager in that Member State considered as the responsible NCP.
Article 21
Cooperation and coordination
1.Infrastructure managers shall cooperate within the European network of infrastructure managers, referred to in Article 7f of Directive 2012/34/EU and in consultation with operators of rail service facilities and other stakeholders to coordinate the following:
(a)the development of common sector specifications for
a common Union API and common Union web user interfaces referred to in Article 14(5), point (a), of this Regulation;
(b)their implementation plans at Union level and consult other telematics stakeholders active at national level with the support of national contact points.
2.Freight railway undertakings shall cooperate on the development of a common sector specification for a common Union API and common Union web user interfaces referred to in Article 14(6).
3.Freight operators of rail service facilities shall cooperate on the development of a common sector specification for a common Union API and common Union web user interfaces referred to in Article 14(5), point (b), and (6).
4.By 31 December 2027, infrastructure managers, freight railway undertakings and freight operators of rail service facilities shall deliver within the process managed by the Agency referred in Article 5 of Directive (EU) 2016/797 their respective common sector specifications resulting from their tasks under paragraphs 1, 2 and 3 of this Article.
Article 22
ERA working party on telematics
The working party or parties established by the Agency pursuant to Chapter 2 of Regulation (EU) 2016/796 shall assist the Agency in applying and further developing the functional and technical specifications set out in this Regulation, in particular in the following tasks of the Agency:
(a)ensure relevant coordination and cooperation of telematics stakeholders to guarantee implementation and application of this Regulation;
(b)ensure cooperation of national contact points at Union level and harmonised and coordinated implementation of their tasks across the Union;
(c)monitor the quality of the common reference data referred to in Article 9;
(d)develop and maintain the user manual for submitting requests for the allocation of reference codes referred to in Article 9(4);
(e)harmonise, where relevant, the network-specific data requirements referred to in Article 11;
(f)maintain the referenced specifications issued by the Agency referred to in Article 12;
(g)provide guidance for the development of sector specifications supporting the update of referenced specifications referred to in Articles 12 and 21;
(h)design, implement, maintain and ensure the automation of data import in relation to the reporting obligations referred to in Article 17;
(i)maintain the testing procedures referred to in Article 18;
(j)implement future developments of this Regulation referred to in Article 23;
(k)facilitate exchange between and collect best practices from telematics stakeholders at Union level;
(l)reflect on the need for follow-up action by the Agency, the Commission, or the Member States, where relevant;
(m)shape and contribute to the implementation of follow-up actions to the feedback provided by the working parties;
(n)identify and prepare strategic topics related to the digitalisation of the rail system for discussion in a wider policy context;
(o)report to the Commission pursuant to Article 24.
Article 23
Future developments
By 31 December 2028, the Agency shall make a recommendation to the Commission pursuant to Article 19(1), point (a), of Regulation (EU) 2016/796 for the update of the functional and technical specifications laid down in this Regulation with the following objectives:
(a)reflecting regulatory and technical developments affecting the rail system;
(b)converting the list of specific data requirements based on positively assessed national rules referred to in Article 11(5) of this Regulation into harmonised specifications, specific cases, or open point as appropriate;
(c)closing the list of open points in Appendix B of the Annex to this Regulation;
(d)updating the references to the specifications referred to in Article 12 of this Regulation;
(e)as regards the technical specifications referenced in Appendix C of the Annex, ensuring appropriate transition from technical documents issued by the Agency to relevant Union standards referred to in Regulation (EU) No 1025/2012 of the European Parliament and of the Council.
(f)taking into account the common specifications referred to in Article 21(3) of this Regulation.
Chapter 4
Transitional and final provisions
Article 24
Report
1.The report submitted by the Agency pursuant to Article 35(4) of Regulation (EU) 2016/796 shall include an analysis of the effectiveness of this Regulation and the progress made towards achieving interoperability of the telematics subsystem of the Union rail system.
2.Reporting on implementation shall be based on information collected by the Agency pursuant to Article 17 of this Regulation.
3.For the purpose of Article 40(2) of Regulation (EU) 2016/796, the Agency shall publish an overview of Union-funded projects and its analysis of innovative outputs relating to the provisions of this Regulation, as well as its proposals for follow-up action necessary to ensure the coordinated development corresponding applications in the Union and a harmonised and coordinated implementation.
Article 25
Repeal
1.Regulations (EU) No 454/2011 and (EU) No 1305/2014 are repealed.
2.References to the repealed Regulations shall be construed as references to this Regulation.
Article 26
Transitional measures
Until the Agency provides the web applications referred to in Article 9(3), it shall assign codes through existing databases managed jointly by infrastructure managers, or by freight operators of rail service facilities or by a group of railway undertakings. For that purpose, the stakeholders managing those databases shall grant access for use to the Agency.
Article 27
Entry into force and application
1.This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.
2.The provisions of the following articles shall apply from [31 December 2025]:
(a)Article 8(1) and (2);
(b)Article 9(3) and (4);
(c)Article 17(3);
(d)Article 18(2) and (3).
3.This Regulation shall be binding in its entirety and directly applicable in all Member States.
Done at Brussels,
For the Commission
The President
Ursula von der Leyen
ANNEX
Table of content
1.Common requirements
1.1.Essential requirements1
1.2.Common reference data1
1.2.1.Organisation reference file1
1.2.2.Location reference file1
1.3.Cybersecurity1
1.4.Data presentation2
1.5.Data quality criteria2
1.5.1.Accuracy2
1.5.2.Completeness2
1.5.3.Consistency3
1.5.4.Timeliness3
1.5.5.Uniqueness3
1.6.Compliance assessment3
1.7.Telematics applications3
1.7.1.Web user interfaces for capacity management, train preparation and traffic management4
1.7.2.Web user interfaces for the management of freight wagons and their loading4
2.Capacity management, train preparation, and traffic management4
2.1.Object identifiers4
2.1.1.General4
2.1.2.Reference train identifier5
2.1.3.Train object5
2.1.4.Path request object5
2.1.5.Path object6
2.1.6.Route object6
2.1.7.Case reference object6
2.2.Strategic management of infrastructure capacity7
2.3.Capacity allocation7
2.3.1.General7
2.3.2.Path request8
2.3.3.Path details8
2.3.4.Path confirmed8
2.3.5.Path details refused9
2.3.6.Path cancelled9
2.3.7.Path not available9
2.3.8.Receipt confirmation10
2.3.9.Capacity allocation coordination process10
2.3.10.Working timetable10
2.4.Capacity restrictions10
2.4.1.Coordination of capacity restrictions10
2.4.2.Consultation of stakeholders affected by capacity restrictions10
2.4.3.Publication of capacity restrictions11
2.4.4.Changes of nominal infrastructure characteristics resulting part of a capacity restriction11
2.5.Train preparation11
2.5.1.Train composition11
2.5.2.Train ready12
2.6.Reporting of train traffic data13
2.6.1.General13
2.6.2.Reporting points14
2.6.3.Train running information14
2.6.4.Train forecast information14
2.6.5.Train delay cause15
2.6.6.Service disruption information15
2.6.7.Path section modification15
2.6.8.Historical record of train traffic data16
2.7.Data sharing with other stakeholders16
3.Management of freight wagons and their loading16
3.1.Electronic rail freight transport information16
3.1.1.Electronic consignment note16
3.1.2.Booking systems for freight services17
3.2.Movements of freight wagons and their loading17
3.2.1.Wagon running information18
3.2.1.1.Geo-localisation of freight wagons18
3.2.1.2.Wagon status18
3.2.1.3.Wagon ready for movement19
3.2.1.4.Wagon pulled19
3.2.1.5.Wagon departure from origin19
3.2.1.6.Wagon arrival at intermediate location20
3.2.1.7.Wagon departure from intermediate location20
3.2.1.8.Wagon handed over20
3.2.1.9.Wagon taken over20
3.2.1.10.Wagon journey irregularity20
3.2.1.11.Wagon journey rectified21
3.2.1.12.Wagon arrival at destination21
3.2.1.13.Wagon delivered21
3.2.2.Intermodal loading unit movement21
3.2.3.Wagon forecast information21
3.3.Freight-specific reference files22
3.3.1.General22
3.3.2.Rolling stock reference databases23
3.3.3.Intermodal loading unit reference databases24
3.3.4.Wagon and intermodal loading unit operational databases25
3.3.4.1.General25
3.3.4.2.Loading of the rolling stock26
3.3.4.3.Loaded rolling stock on journey26
3.3.4.4.Empty rolling stock on journey26
3.3.4.5.Unloading of rolling stock26
3.3.4.6.Empty wagon under fleet management control26
3.4.Data sharing with other stakeholders26
4.Rail ticketing in relation to rail passenger services and rail passenger travel information27
4.1.General27
4.2.Passenger timetable data27
4.2.1.Passenger timetable data of rail passenger transport services27
4.2.2.Passenger timetable data of connection times28
4.2.2.1.Definition and maintenance of minimum connection times29
4.2.2.2.Connection times in one location30
4.2.2.3.Connection times between two locations31
4.2.2.4.Calculation of connection time31
4.3.Tariff data32
4.3.1.Fares data of rail passenger transport services32
4.3.2.Management of rail ticketing and ticket check rules33
4.3.3.Information about the online sales channels of railway undertakings33
4.4.Conditions of carriage33
4.4.1.General33
4.4.2.Conditions for the carriage of passengers34
4.4.3.Conditions of carriage and assistance for persons with disabilities and persons with reduced mobility (‘PRM’)34
4.4.3.1.Accessibility of rolling stock34
4.4.3.2.Accessibility of station35
4.4.4.Condition for the carriage of registered luggage35
4.4.5.Conditions for the carriage of bicycles35
4.4.6.Conditions for carriage of cars, motorcycles and boats (‘cars’)36
4.5.Availability and reservations36
4.5.1.General36
4.5.2.Availability and reservation request37
4.5.3.Availability and reservation response38
4.5.4.Availability of and reservations for PRM assistance38
4.5.5.Availability of and reservations for bicycle places38
4.5.6.Availability and reservations for cars38
4.6.Security elements for product distribution39
4.6.1.Security elements for electronic delivery39
4.6.2.Dossier reference39
4.6.3.Fulfilment methods39
4.6.3.1.General39
4.6.3.2.Direct fulfilment methods40
4.6.3.3.Indirect fulfilment methods40
4.6.4.Ticket control and ticket state modification41
4.6.4.1.Ticket annotation41
4.6.4.2.Reimbursement or compensation request41
4.7.Passenger travel information during the journey42
4.7.1.Information in the station42
4.7.1.1.General42
4.7.1.2.Train departures42
4.7.1.3.Train arrivals43
4.7.1.4.Deviations from scheduled times43
4.7.2.Information in the vehicle43
4.8.Common reference data for rail ticketing44
4.9.Data sharing with other stakeholders45
5.List of specific cases45
5.1.General45
5.2.List of specific cases45
APPENDIX A INTERFACES IN RELATION TO OTHER SUBSYSTEMS46
A.1Interoperability requirements related to accessibility46
A.2Interoperability requirements related to capacity management, train preparation and traffic management47
A.3Interoperability requirements related to noise48
A.4Interoperability requirements related to control-command and signalling48
APPENDIX B LIST OF OPEN POINTS49
APPENDIX C LIST OF REFERENCED STANDARDS AND TECHNICAL DOCUMENTS51
Semantic versioning of technical documents51
C.1List of common referenced technical documents51
C.2List of referenced technical documents specific to data sharing in relation to capacity management, traffic management, and train preparation52
C.3List of referenced technical documents to data sharing specific for the management of freight wagons and their loading53
C.4List of referenced specifications specific to rail ticketing in relation to rail passenger transport services and rail passenger travel information53
C.4.AList of referenced standards53
C.4.BList of referenced technical documents55
APPENDIX D TESTING PROCEDURES FOR COMPLIANCE ASSESSMENT57
D.1Testing procedures for telematics applications57
D.2Evidence-based declaration for individual IT messages58
D.3Specific testing procedures for rail ticketing58
D.3.APassenger timetable58
D.3.BTariffs58
D.3.CAvailability check and reservation58
D.3.EBarcodes59
APPENDIX E ACCURACY OF FORECAST INFORMATION FOR TRAIN AND WAGON MOVEMENTS60
APPENDIX F ESSENTIAL REQUIREMENTS62
APPENDIX G IMPLEMENTATION MILESTONES64
1.Common requirements
1.1.Essential requirements
The essential requirements of the subsystem ‘telematics applications for passenger and freight services’ referred to in point 1(b), third indent, of Annex II to Directive (EU) 2016/797 and described in point 2.6 of that Annex are laid down in Appendix F to this Annex.
1.2.Common reference data
(1)The procedure for the assignment of codes referred to in Article 9 is set out in the specifications referenced in Appendix C, index [1].
(2)The Agency shall manage common reference data in accordance with Articles 8 and 9 and the specifications referenced in Appendix C, index [1] and grant access for use to it under the conditions of the Creative Commons BY-ND 4.0 licence.
1.2.1.Organisation reference file
(1)The data presentation of an organisation code shall comply with the specifications referenced in Appendix C, index [2].
(2)Until 31 December 2025, a specific range of organisation codes shall be reserved for allocation to organisations under the scope of this Regulation and specified in the specifications referred in point (1).
1.2.2.Location reference file
(1)Any reference to a geographical point necessary for data sharing subject to this Regulation shall be identified with a single location code.
(2)The data presentation of a location code shall comply with the specifications referenced in Appendix C, index [2].
1.3.Cybersecurity
For the purpose Article 7(2), each telematics stakeholder shall implement cybersecurity risk-management measures in accordance with Directives (EU) 2022/2555 and (EU) 2022/2557 of the European Parliament and of the Council, including the use of public key infrastructure (‘PKI’) in accordance with the specifications referenced in Appendix C, index [3]. The communication protocols it uses shall belong to the Transmission Control Protocol / Internet Protocol (TCP/IP) suite.
1.4.Data presentation
(1)The Agency shall ensure semantic versioning of the ERA Ontology referred to in Article 7, the specifications of which are referenced in Appendix C, index [2], and shall ensure access to all applicable versions through its website.
(2)The Agency shall ensure that the ERA Ontology is compatible with the following data catalogue elements:
(a)the technical specifications referenced in Appendix C, index [105], for the purposes of the processes referred to in Article 2, paragraphs (1) and (2);
(b)the technical specifications referenced in Appendix C, index [P.7], for the purposes of the processes referred to in Article 2(3).
(3)The sequence of the messages to be exchanged pursuant this Regulation shall comply with the specifications referenced in Appendix C, index [100].
1.5.Data quality criteria
For the purposes of identifying a deficiency of data quality as part of the quality assurance check referred to in Article 10(4) and (5), a telematics stakeholder shall measure the deviation of quality from the nominal value (%) set out for each criteria, and where relevant take corrective action aiming at meeting this value.
1.5.1.Accuracy
(1)Data shared pursuant to this Regulation shall be recorded once as primary data without any intermediate processing, transformation or aggregation by the data holder, that is to say the telematics stakeholder who generated the data. Telematics stakeholders shall be given access to primary data in accordance with Article 4.
(2)The accuracy of the data shall be measured as the percentage of the values stored as part of the reference data that are correct in comparison with the actual value.
(3)The values stored as part of the reference data shall be 100% accurate.
1.5.2.Completeness
(1)Before sharing data, the data holder shall ensure that its telematics applications check the completeness and compliance of the data shared against the metadata referred to in Article 8.
(2)The data user, that is to say the telematics stakeholder using the data, shall ensure that its telematics applications check the completeness and compliance of the data consumed against the metadata.
(3)The completeness of the data shall be measured as the percentage of mandatory data fields that contain values.
(4)Data shall be 100% complete.
1.5.3.Consistency
(1)The data holder shall ensure that its telematics applications operate in accordance with the business rules guaranteeing data consistency.
(2)Where data consistency needs to be checked against different sources and versions of the reference data, the data holder shall implement validation procedures before interface data are generated or a new data version becomes operational. The data duplicated from the reference data shall be validated against the business rules.
(3)The data holder shall be identified through its organisation code as part of the data it shares.
(4)The consistency of the data shall be measured as the percentage of matching values across tables, files, and records, and across processes.
(5)Data shall be 100% consistent.
1.5.4.Timeliness
(1)Telematics stakeholders shall share up-to-date data.
(2)The data holder shall ensure that its telematics applications enable data updates as soon as they are available. The data holder shall set out response times for enquiries and user types in the detailed specifications of its telematics applications.
(3)The timeliness of the data shall be measured as the percentage of data shared within a specified threshold time frame.
(4)Data timeliness shall comply with threshold requirements laid down per function by the data holder.
1.5.5.Uniqueness
(1)The data holder shall ensure that there is no duplication of records in data shared. It shall identify and eliminate any redundant records using deduplication tools, automated where possible.
(2)The uniqueness of the data shall be measured as the complement of the percentage of duplicates across tables, files, and records to 100%.
(3)Data shall be 100% unique.
1.6.Compliance assessment
Telematics stakeholders shall pursuant to Article 18 self-assess the compliance of the telematics applications they deploy to implement this Regulation against the testing procedures and the evidence-based declaration provided in Appendix D.
1.7.Telematics applications
(1)Except for the processes referred to in Article 2(1), point (c), for which the specifications set out in Section 4 apply, the application programming interfaces (‘API’) and web user interfaces (‘UI’) referred to in Article 14 that are deployed by telematics stakeholders shall comply with the specifications for common interface referenced in Appendix C, index [104].
(2)The specifications referenced in Appendix C, index [2], shall be used to ensure format validity, authenticity and integrity of received or transmitted data in relation to the information available in the common central repository referred to in Article 8. To that end, the data catalogue elements referred to in Article 7(3) and set out in point 1.4(2) of this Annex shall be linked to the APIs and web user interfaces referred to in point (1).
1.7.1.Web user interfaces for capacity management, train preparation and traffic management
Aspects relating to the interoperability of web user interfaces for capacity management, train preparation and traffic management, pursuant to Article 14 of this Regulation, are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
1.7.2.Web user interfaces for the management of freight wagons and their loading
Aspects relating to the interoperability of web user interfaces for the management of freight wagons and their loading, pursuant to Article 14 of this Regulation, are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
2.Capacity management, train preparation, and traffic management
(1)The provisions of this Section lay down the requirements for interoperable data sharing required to carry out the processes referred to in Article 2(1), point (a).
(2)Data relating to capacity management, train preparation, and traffic management, shall be shared by means of an API or a web user interfaces in accordance with Article 14 and point 1.7.
(3)In areas of capacity management, train preparation, and traffic management of a specific rail transport service, telematics stakeholders subject to Article 4 shall share, mutually access and use for operational and non-commercial purposes, both free-of-charge, data relating to the trains part of that rail transport service.
2.1.Object identifiers
2.1.1.General
(1)The main object identifiers set out in points 2.1.2 to 2.1.7 shall be shared between the different telematics stakeholders involved in a rail transport service, and used consistently by them. Those objects shall be marked with unique identifiers in the planning phase of that rail transport service and used consistently in areas of train preparation and traffic management for that rail transport service.
(2)Object identifiers shall be in accordance with the specifications referenced in Appendix C, index [2].
2.1.2.Reference train identifier
(1)The objects referred to in points 2.1.3 to 2.1.7 shall be embedded in messages exchanged pursuant to points 2.2 to 2.7, using a unique and stable identifier of the train, known as the reference train identifier, or ‘reference train ID’, for the complete lifecycle of the train and related objects across networks.
(2)The lead railway undertaking shall specify the ‘reference train ID’.
(3)The ‘reference train ID’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(4)Where a rail transport service is operated or intended to be operated by several railway undertakings along that service, the lead railway undertaking shall coordinate the railway undertakings operating that service by integrating consistently the objects referred to in points 2.1.3 to 2.1.7.
2.1.3.Train object
(1)The ‘train’ object, linked to the ‘reference train ID’, shall be specified by the lead railway undertaking.
(2)Once consistently integrated by the lead railway undertaking responsible for coordinating the applicants for the same rail transport service, the corresponding ‘train’ object shall be sent by each applicant to the infrastructure managers and operators of rail service facilities involved along the route of that service by means of the following elements:
–the ‘reference trainID’ in accordance with point 2.1.2;
–the ‘route’ object in accordance with point 2.1.6 and with the ‘path request’ object in accordance with point 2.1.4;
–the elements of the messages relating to:
–capacity allocation referred to in point 2.3;
–train preparation as referred to in point 2.5.
(3)The ‘train’ object describes the planned train for a rail transport service and its entire route.
2.1.4.Path request object
(1)The ‘path request’ object, linked to the ‘reference train ID’, shall be specified by the lead railway undertaking.
(2)Once consistently integrated by the lead railway undertaking responsible for coordinating the applicants for the same rail transport service, the corresponding ‘path request’ object shall be sent by each applicant to the infrastructure managers and operators of rail service facilities involved along the route of that service.
(3)The ‘path request’ describes the details of the path requested for the planned train on the network. It shall contain, as attribute, the identification of the lead railway undertaking. It may include, as attribute, the expected Operational Train Number (‘OTN’).
2.1.5.Path object
(1)The ‘path’ object, linked to the ‘reference train ID’, shall be specified by the infrastructure manager or operator of rail service facilities responsible for specifying the corresponding path on its network.
(2)The ‘path’ object shall be sent by the infrastructure manager or operator of rail service facilities to the applicant.
(3)The ‘path’ object describes the details of the path allocated for a train. Infrastructure managers and operators of rail service facilities involved along the route of that train shall coordinate between themselves the ‘path’ object.
(4)Where the ‘path’ object is part of the ‘path request’ object referred to in point 2.1.5, it shall contain, as attribute, the OTN, which may change along the lifecycle of the path or the linked train.
2.1.6.Route object
(1)The ‘route’ object, linked to the ‘reference train ID’, shall be specified by the lead railway undertaking. It refers to the geographical line of operation from a point of departure to a point of destination.
(2)Once consistently integrated by the lead railway undertaking responsible for coordinating the applicants for the same rail transport service, the ‘route’ object shall be sent by the applicant to all infrastructure managers and operators of rail service facilities involved along the route of that service.
(3)The ‘route’ object describes the minimum information about the entire route for which an infrastructure manager or operator of rail service facilities needs to perform their duties including assessing the ‘path request’.
(4)The ‘route’ shall contain at least the following information:
(a)point of origin;
(b)points of handover agreed between two infrastructure managers or operators of rail service facilities, where the responsibility for the operation of the rail infrastructure changes from one to another;
(c)point of destination;
(d)corresponding planned dates and time according to the working timetable.
2.1.7.Case reference object
(1)The ‘case reference’ object shall be specified by its issuer.
(2)Where a specific object or data are used or intended to be used by a telematics stakeholder, they shall be gathered into or referred to as a dedicated ‘case reference object’ subject to the process referred to in Article 11.
(3)Aspects relating to the interoperability of data sharing in relation to the identification of shunting trains in rail service facilities are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
2.2.Strategic management of infrastructure capacity
Aspects relating to the interoperability of data sharing in relation to the strategic management of infrastructure capacity are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
2.3.Capacity allocation
2.3.1.General
(1)Without prejudice to the definition of ‘train path’ in Article 3, point (27), of Directive 2012/34/EU in relation to a rail transport service, and the definition of ‘service facility capacity’ in Article 3, point (4), of Commission Implementing Regulation (EU) 2017/2177 solely in relation to the sections of that rail transport service operated in a rail service facility, the requested, accepted and actual data to be stored pursuant to the Annex to Commission Implementing Regulation (EU) 2019/773 (OPE TSI), as referred to in Appendix A to this Annex, concerning the capacity rights and the characteristics of the train for each section of these rights, including sections in rail service facilities, are designated hereafter as ‘path’.
(2)In the process of the allocation of infrastructure capacity referred to in Chapter IV Section 3 of Directive 2012/34/EU, the messages referred to in points 2.3.2 to 2.3.9 of this Annex shall be exchanged between the applicant and the infrastructure manager or the allocation body designated in accordance with Article 7a(3) of that Directive using an API or a web user interface referred to in Article 14 and point 1.7 of the Annex to this Regulation.
(3)In the process of the allocation of rail service facilities capacity referred to in Article 13 of Directive 2012/34/EU and Articles 7 to 9 of Implementing Regulation (EU) 2017/2177, the messages referred to in points 2.3.2 to 2.3.9 of this Annex shall be exchanged between the applicant and the operator of rail service facilities solely in relation to the sections of a rail transport service subject to the allocation of a path using an API or a web user interface referred to in Article 14 of this Regulation.
(4)Aspects relating to the interoperability of data sharing in relation to the planning of shunting movements and stabling in rail service facilities are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
(5)In the case of multi-network capacity allocation involving more than one infrastructure manager or operator of rail service facilities along a train route, the infrastructure managers and operators of rail service facilities involved shall, pursuant to Article 40(1) of Directive 2012/34/EU, coordinate their allocation processes to ensure consistency of corresponding outcomes. Applicants for multi-network capacity may use the common Union API or a common Union web interface referred to in Article 14(5) of this Regulation.
(6)Where more than one railway undertaking operates a rail transport service, the railway undertaking involved may designate the lead railway undertaking as the applicant for the overall route of that service. The lead railway undertaking shall at least ensure the coordination of the applicants and their allocation processes, integrating consistently the object identifiers referred to in point 2.1 for the overall route of that service.
(7)In case of an ad hoc request for the allocation of infrastructure capacity in relation to a train with a departure time in less than [45 minutes] at the time of the request, information relating to corresponding path shall be communicated as part of a path section modification in accordance with point 2.6.7.
(8)In the case of freight rail transport services, where the actual characteristics of the consignment require the path allocated to be adapted, the information contained in the ‘Consignment Note’ message referred to in point 3.1.1 shall be used for a path request.
(9)Messages exchanged for the allocation of a path for a freight rail transport service shall contain information identifying quieter routes intended for operation, if any, in accordance with the Annex to Commission Implementing Regulation (EU) 2023/1694 (NOI TSI), as referred to in Appendix A to this Annex.
(10)The working timetable reflects the paths that are confirmed as allocated.
2.3.2.Path request
(1)The ‘Path Request’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)To request a path, the applicant shall send a ‘Path Request’ message to the infrastructure managers and operators of service facilities concerned.
2.3.3.Path details
(1)The ‘Path Details’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)In response to a ‘Path Request’ message received from an applicant in accordance with point 2.3.2, infrastructure managers and operators of service facilities shall each send a ‘Path Details’ message to specify the details of the path offered to the applicant.
2.3.4.Path confirmed
(1)The ‘Path Confirmed’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)To confirm the allocation of the path proposed by an infrastructure manager or an operator of service facilities in the ‘Path Details’ message referred to in point 2.3.3, the applicant shall send back the ‘Path Confirmed’ message.
(3)Upon receipt of the message ‘Path confirmed’ message, the receiving infrastructure manager or operator of rail service facilities shall acknowledge its receipt by sending the originating applicant a ‘Path Details’ message confirming the booking and integrate corresponding path in its working timetable.
(4)Upon receipt of the ‘Path Details’ message confirming the booking, the applicant shall also send this message to the railway undertakings involved in that path and to the lead railway undertaking. In the case of freight rail transport services, the lead railway undertaking shall forward this booking confirmation to freight customers.
(5)A train path confirmed by the applicant in accordance with point (1) whose confirmation of receipt has been acknowledged by the receiving infrastructure manager or operator of service facilities in accordance with point (3) is considered as allocated and corresponding capacity rights are to be considered by both parties as granted.
2.3.5.Path details refused
(1)The ‘Path Details Refused’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)If the path proposed by the infrastructure manager or operator of service facilities in accordance with point 2.3.3 is refused, the applicant shall send back a ‘Path Details Refused’ message.
2.3.6.Path cancelled
(1)The ‘Path Cancelled’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)To cancel all or part of a path that has been confirmed in accordance with point 2.3.4, the applicant shall send a ‘Path Cancelled’ message to the infrastructure manager or operator of service facilities affected which are responsible for the capacity rights granted on their network.
2.3.7.Path not available
(1)The ‘Path Not Available’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where a path allocated is no longer available, or in the event of a change to the path allocated, the infrastructure manager or operator of rail service facilities responsible for the path allocated on their network shall send a ‘Path Not Available’ message to the applicant as soon as they become aware of such a change.
(3)Where an alternative to a path that is no longer available or has been changed becomes available, each infrastructure manager or operator of rail service facilities responsible for the path, or part of it, allocated on its network, shall propose that alternative and send it to the applicant by means of a ‘Path Details’ message in accordance with point 2.3.3, which shall be read alongside the ‘Path Not Available’ message referred to in point (2). In such case, the following conditions shall also apply:
(a)where such an alternative is proposed, the applicant is not required to send a ‘Path Request’ message under point 2.3.2;
(b)where such an alternative is not available, each infrastructure manager or operator of rail service facilities responsible for the path, or part of it, allocated on its network, shall immediately send the applicant a ‘Path Not Available’ message.
2.3.8.Receipt confirmation
(1)The ‘Receipt Confirmation’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)The recipient of the messages referred to in points 2.3.2, 2.3.3, 2.3.5, 2.3.6, and 2.3.7 shall acknowledge receipt by sending a ‘Receipt Confirmation’ message to the telematics stakeholder which sent the original message.
2.3.9.Capacity allocation coordination process
Aspects relating to the interoperability of data sharing in relation to the electronic form of the information disclosed in case of conflict resolution referred to in Article 46 of Directive 2012/34/EU are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
2.3.10.Working timetable
Each infrastructure management and operator of rail service facilities shall integrate the paths that are considered as allocated in accordance with point 2.3.4, points (3) and (5), and make them available as part of its working timetable data in accordance with Article 5 under the conditions of the Creative Commons BY-SA 4.0 licence or any other less restrictive open licence part of the Creative Common suite.
2.4.Capacity restrictions
2.4.1.Coordination of capacity restrictions
Aspects relating to the interoperability of data sharing in relation to the coordination of capacity restrictions are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
2.4.2.Consultation of stakeholders affected by capacity restrictions
Aspects relating to the interoperability of data sharing in relation to the consultation of stakeholders affected by planned capacity restrictions in accordance with Articles 43 and 53 of Directive 2012/34/EU are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
2.4.3.Publication of capacity restrictions
Aspects relating to the interoperability of data sharing in relation to the publication of capacity restrictions in accordance with Articles 43 and 53 of Directive 2012/34/EU are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
2.4.4.Changes of nominal infrastructure characteristics resulting part of a capacity restriction
(1)Where a change of nominal infrastructure characteristics results from a planned capacity restriction, either permanent or temporary, and affects the running of trains, the infrastructure manager shall publish these changes pursuant to OPE TSI, as referred to in Appendix A to this Annex, by means of the register of infrastructure (‘RINF’) referred in Article 49 of Directive (EU) 2016/797.
(2)Aspects relating to the interoperability of data sharing relating to a change of nominal infrastructure characteristics due to an unplanned capacity restriction, either permanent or temporary, that affects the running of trains, are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
(3)Where a capacity restriction has an impact on an allocated path, it shall in addition be communicated in accordance with the capacity allocation process set out point 2.3.
2.5.Train preparation
2.5.1.Train composition
(1)The ‘Freight Train Composition’ message and the ‘Passenger Train Composition’ message (‘Train Composition’ messages) shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Any railway undertaking responsible for the operation of a train shall send a ‘train composition’ message to confirm that the composed train is in running order pursuant to OPE TSI, as referred to in Appendix A, to the infrastructure managers or operators of rail service facilities responsible for the network of departure solely in relation to the sections of the path where the train is to run.
(3)Where a railway undertaking shares train composition data with an infrastructure manager or an operator of rail service facilities in accordance with point (2), it may request that the commercial use of that data is subject to a contractual agreement unless such use is covered by the open licence used by the infrastructure manager or the operator of rail service facilities sharing that data pursuant to Article 5 and point 2.5.1(4).
(4)Each infrastructure manager and each operator of rail service facilities, solely in relation to the sections of the rail transport service operated on its network according to a path, shall grant access pursuant to Article 5 to train composition data.
(5)Where an infrastructure manager or an operator of rail service facilities grants access to train composition data pursuant to Article 5, it shall reuse consistently the information contained in ‘train composition’ messages received from railway undertakings and grant access to that data under the conditions of the Creative Commons BY-NC-SA 4.0 licence or any other less restrictive open licence part of the Creative Common suite.
(6)Where public access to train composition data is restricted pursuant to Article 5(2) or (3), each infrastructure manager and each operator of rail service facilities shall ensure other telematics stakeholders can access that data pursuant to Article 4 through the common Union web UI referred in Article 5(1).
(7)Where, before or after departure, the composition of a train has been modified, the railway undertaking responsible for the operation of that train shall send an updated ‘train composition’ message with a reference to the location where the composition changed.
(8)Where disruption or emergencies arising during train operation entail a change in the parameters of the train composition, with possible repercussions on the train traffic data referred to in point 2.6, the railway undertaking responsible for that train communicates the new train composition in accordance with Appendix C to the OPE TSI and may also send a new ‘train composition’ message.
(9)The ‘Freight Train Composition’ message shall contain parameters providing for compliance of the composition of the train with the specific rules for the operation of wagons on quieter routes pursuant to NOI TSI, as referred to in Appendix A to this Annex. The identification of quieter routes intended for operation shall be consistent with the details of the path allocated as defined in point 2.3.
(10)The ‘Freight Train Composition’ message shall make it possible to identify any intermodal loading unit loaded on wagons.
(11)The ‘Passenger Train Composition’ message shall include seating maps and the location of on-board facilities such as coaches accessible to PRM and bike spaces, where available.
(12)The recipient of a ‘train composition’ message shall acknowledge its reception by sending a ‘Receipt Confirmation’ message in accordance with the specifications referenced in Appendix C, index [2], to the original sender.
2.5.2.Train ready
(1)Where either Railway Mobile Radio (RMR) systems or ‘Start of mission’ procedure in ETCS L2 in accordance with Annex to Commission Implementing Regulation (EU) 2023/1695 (CCS TSI), as referred to in Appendix A, are available as reported in the RINF and mandated for use by the infrastructure manager responsible for the network of departure, the obligations laid down in points (3), (4) and (6) are deemed to have been fulfilled.
(2)The ‘Train Ready’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(3)Where a railway undertaking responsible for the movement of a train provides information pursuant to OPE TSI, as referred to in Appendix A, about the status of that train in terms of its readiness to access the network, this railway undertaking shall send a ‘Train Ready’ message before departure to the infrastructure manager responsible for the network of departure.
(4)Based on common safety methods for risk assessment, the infrastructure shall set out, and further specify, through agreement with railway undertakings, the safety aspects relevant to the reuse in operation of such information for safety purposes.
(5)Where a railway undertaking is not ready to start according to the working timetable or is delayed, it shall, in order to provide train forecast information about its readiness to access to the network, send a ‘Train Ready’ message bearing the status ‘not ready’ as well as an estimate of how long the delay will last and an assessment of its cause. A new ‘Train Ready’ message shall be sent as soon as new or updated information is available.
(6)Where an infrastructure manager receives a ‘Train Ready’ message pursuant to point (3), it shall acknowledge receipt.
2.6.Reporting of train traffic data
2.6.1.General
(1)Whereas working timetable data reflects the paths allocated and confirmed pursuant to point 2.3, train traffic data, including information about train running and train forecast, contains the data necessary to dynamically update the working timetable.
(2)The following messages containing train traffic data (‘train traffic messages’) shall be in accordance with the specifications referenced in Appendix C, index [2]:
(a)‘Train Running Information’ specified in point 2.6.3;
(b)‘Train Running Forecast’ specified in point 2.6.4;
(c)‘Train Delay Cause’ specified in point 2.6.5;
(d)‘Train Running Interruption’ specified in point 2.6.6.
(3)Infrastructure managers and operators of rail service facilities, solely in relation to the sections of each rail transport service operated on their network according to a path, and where relevant other data holders:
(a)shall grant access pursuant to Article 5 to train traffic data based on the information contained in train traffic messages;
(b)may send train traffic messages to railway undertakings in relation to the rail transport services they operate and to other relevant telematics stakeholders in accordance with Article 4.
(4)Where an infrastructure manager or an operator of rail service facilities grants access to train traffic data pursuant to Article 5, it shall reuse consistently the information contained in train traffic messages and grant access to that data under conditions of the Creative Commons BY-SA 4.0 licence or any other less restrictive open licence part of the Creative Common suite.
(5)Traffic data relating to the shunting and stabling of freight wagons in rail service facilities shall be shared in accordance with point 3.2.1.
(6)Train traffic messages shall constitute appropriate technical means within the meaning of Article 10(4) of Regulation (EU) 2021/782, of meeting the obligations under Article 10 of Regulation (EU) 2021/782, and of providing traffic and travel information of passenger rail transport services.
(7)Where an infrastructure manager or a passenger railway undertaking shares via national access points dynamic travel and traffic data in accordance with Article 5 of Commission Delegated Regulation (EU) 2017/1926, it shall reuse consistently the data contained in train traffic messages and apply the specifications set out in point 4.9(d).
2.6.2.Reporting points
Messages containing train traffic data, shall be sent at least at the following reporting points, and at any other point where the train is passing through, as agreed between the infrastructure manager or the operator of rail service facilities, and the railway undertaking in relation to a train:
(a)departure points;
(b)where responsibility for traffic management changes between consecutive infrastructure managers or between infrastructure managers and operators of rail service facilities (‘point of handover’);
(c)where responsibility for the operation of a train changes between consecutive railway undertakings, shunting operators in rail service facilities, intermodal transport operators, or any combination between them (‘point of interchange’);
(d)where the train arrives at and departs from stations and terminals and any other intermediary stops scheduled;
(e)destination points.
2.6.3.Train running information
(1)The ‘Train Running Information’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)To report about the train position in real time pursuant to OPE TSI, as referred to in Appendix A, the infrastructure manager or the operator of rail service facilities shall send a ‘Train Running Information’ message upon departure from and arrival of a train at reporting points.
2.6.4.Train forecast information
(1)‘Train Running Forecast’ messages shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)To provide information about deviations from scheduled dates and times whenever they occur pursuant to OPE TSI, as referred to in Appendix A, and therefore to provide an estimate of the date and time of departure or arrival of a train from or at a reporting point, the infrastructure manager or operator of rail service facilities shall send a ‘Train Running Forecast’ message.
(3)For delays estimated to last more than 10 minutes, or as otherwise required by the performance monitoring regime pursuant to OPE TSI, as referred to in Appendix A, between two reporting points and the corresponding updates, a new ‘Train Running Forecast’ message shall be sent.
(4)‘Train Running Forecast’ messages shall make it possible to gauge, ex post, the accuracy of the estimate made by means of this forecast and include its expected accuracy in accordance with the methodology set out in Appendix E.
2.6.5.Train delay cause
(1)The ‘Train Delay Cause’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)As soon as the cause of delay is known, known also as first assumption, and where there is an update on the cause of delay, the infrastructure manager or the operator of rail service facilities shall send a ‘Train Delay Cause’ message to provide information about deviations from scheduled times pursuant to OPE TSI, as referred to in Appendix A, whenever they occur for that train.
2.6.6.Service disruption information
(1)The ‘Train Running Interruption’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)To provide information about disruption to a rail transport service (‘service disruption’) due to an unplanned stop, and describing this disruption and its location pursuant to OPE TSI, as referred to in Appendix A, the infrastructure manager or operator of rail service facilities shall send the following messages:
(a)where the length of the delay is not known: a ‘Train Running Interruption’ message;
(b)where the length of the delay is known:
(i)‘Train Running Forecast’ message in accordance with point 2.6.4;
(ii)‘Train Delay Cause’ message in accordance with point 2.6.5.
(3)To provide information about service disruption arising from the operation of a train, the railway undertaking responsible for that train shall send the messages referred to in point (2)(a) and (b) to the infrastructure manager or operator of rail service facilities responsible for the network where the service disruption occurred. Where relevant, the receiving infrastructure manager or operator of rail service facilities shall send updated information in accordance with point 2.6.1.
2.6.7.Path section modification
(1)In the event of modifications to a train beyond the threshold referred to in point 2.3.1(7), the infrastructure manager or operator of rail service facilities responsible for the path of that train on its network shall share information with the railway undertakings concerned about the intended path and where relevant to its modifications.
(2)Without prejudice to point (3), aspects relating to the interoperability of data sharing in relation to the information referred to in point (1) are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B.
(3)If the agreed continuation of a passenger train involves rerouting, cancellation, partial cancellation, or the removal or addition of stops, the infrastructure manager responsible for that train shall send a ‘Train Running Forecast’ message containing information relating to the path section modification in accordance with point 2.6.1.
2.6.8.Historical record of train traffic data
To record data pertaining to the running of both passenger and freight trains pursuant to OPE TSI, as referred to in Appendix A, each infrastructure manager and each operator of rail service facilities shall grant access to an historical record of the following data pursuant to Article 5 for at least 12 months after the termination of the train service:
(a)for passenger trains only: passenger train identification number;
(b)‘reference train ID’;
(c)reporting locations and associated train status;
(d)actual running date and time;
(e)delay and cause of delay, if any.
2.7.Data sharing with other stakeholders
Infrastructure managers, operators of service facilities and railway undertakings shall share data in accordance with Article 4 and the requirements laid down in point 2 with other telematics stakeholders responsible for managing connections with other modes of transport.
3.Management of freight wagons and their loading
The provisions of this Section lay down the requirements for interoperable data sharing required to carry out the processes referred to in Article 2(1), point (b).
3.1.Electronic rail freight transport information
3.1.1.Electronic consignment note
(1)A consignment note exchanged electronically by means of a ‘Consignment Note’ message and bearing electronic signatures pursuant to Regulation (EU) No 910/2014 of the European Parliament and of the Council shall be considered as an electronic record of data equivalent to a paper-based consignment note.
(2)The ‘Consignment Note’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(3)The electronic consignment note shall be exchanged as follows:
(a)based on consignment information provided by the freight customer to the lead railway undertaking as single point of contact, the lead railway undertaking shall send a ‘Consignment Note’ message to all railway undertakings involved in the transport service,
(b)the lead railway undertaking may share the information contained in ‘Consignment Note’ messages with the relevant telematics stakeholders pursuant to Article 4.
(4)An electronic consignment note sent pursuant to point (3) is considered sufficient for the recipients to be able to perform their parts of the contract of carriage until arrival at destination or interchange with the next stakeholder.
(5)Where the lead railway undertaking sends data to the competent authorities pursuant to Article 4 of Regulation (EU) 2020/1056 of the European Parliament and of the Council, it shall re use consistently the data contained in the ‘Consignment Note’ message referred to in this point, and where relevant in the ‘Freight Train Composition’ message referred to in point 2.5.1.
3.1.2.Booking systems for freight rail transport services
Aspects relating to the interoperability of data sharing and associated systems for the booking of freight rail transport services by freight customers, including for availability check and reservation of such services based on intermodal oriented timetable integrating buffer times and milestones in multi-modal freight terminals for departure and arrival on such services and decision making on their availability, are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B.
3.2.Movements of freight wagons and their loading
(1)Railway undertakings involved in the same freight rail transport service shall mutually exchange information and individually ensure the monitoring of the location and status of the freight wagons, or set of wagons, for which they are responsible for the data relating to the movements of freight wagons and their loading set out in points 3.2.1 to 3.2.3.
(2)The lead railway undertaking shall have an overview of the current location and status of the wagons or set of wagons, and their loading, using the information provided by railway undertakings and operators of rail service facilities involved in the same freight rail transport service.
(3)The current location and status of the loading, intermodal loading units in particular, shall be monitored based on the location and status of the wagons onto which the loading is.
(4)Freight railway undertakings may contribute to the development of common Union web user interfaces referred to in Article 14(6) and Article 21 for granting access to data relating to the movements of freight wagons and their loading. Where a group of freight railway undertakings jointly provide for use such common Union web user interfaces, that application shall grant access to data relating to the movements of freight wagons and their loading to relevant telematics stakeholders pursuant to Article 4 and under the conditions of the Creative Commons BY-NC-SA 4.0 licence or any other less restrictive open licence part of the Creative Common suite.
3.2.1.Wagon running information
3.2.1.1.Geo-localisation of freight wagons
(1)Where geo-localisation devices are fitted on wagons, vehicle keepers shall, upon request, provide freight railway undertakings operating these wagons the corresponding geo-localisation based wagons positioning pursuant to Regulation (EU) 2023/2854.
(2)Receiving railway undertakings may reuse this data as appropriate for the continuous monitoring of wagons positioning through the messages referred to in point 3.2.1.2.
(3)Data relating to geo-localisation-based wagons positioning provided by vehicle keepers shall include at least:
(a)the latest position of the wagon, including location, date and time;
(b)the loading status of the wagon where supported by the geo-localisation device.
3.2.1.2.Wagon status
(1)The ‘wagon status’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)For other telematics stakeholder involved in a rail transport service to have continuous knowledge of the current location and status of the wagons:
(a)the railway undertaking or the shunting operator in a rail service facility (‘undertaking’) responsible for the movement of a wagon or set of wagons shall send a ‘wagon status’ message to the following telematics stakeholders pursuant to Article 4:
(i)the lead railway undertaking;
(ii)other railway undertakings;
(b)the lead railway undertaking shall send a ‘wagon status’ message to relevant telematics stakeholders pursuant to Article 4.
(3)Operators of rail service facilities may share the information on the movement of wagons in their facilities contained in the ‘wagon status’ messages they receive as relevant telematics stakeholders pursuant to Article 4.
(4)Operators of rail service facilities shall, in a centralised manner at the level of each rail service facility or grouping of rail service facilities, monitor the current location and status of freight wagons and their loading at least at the entry into and exit from their facilities. In such a case, they shall send ‘wagon status’ messages to the intermodal transport operators pursuant to Article 4.
(5)Where a telematics stakeholder sends a ‘wagon status’ message, it shall specify to which event type that message relates to in accordance with points 3.2.1.3 to 3.2.1.13.
(6)Unless a common wagon and intermodal loading unit operation database in accordance with point 3.3.3 is available, or common Union web user interfaces referred in point 1.7.2 have been used, ‘wagon status’ messages shall be exchanged bilaterally via a telematics application referred to in Article 14 and point 1.7.
3.2.1.3.Wagon ready for movement
(1)The event type ‘wagon ready to pull’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where the loader or where relevant the filler of the wagon, both of which are defined in Article 3 of Directive (EU) 2016/798, have informed the lead railway undertaking that their load, if any, is ready for movement, without prejudice to Article 4 of Directive (EU) 2016/798, and therefore that the wagon can be pulled or pushed from a specified loading or unloading location, the lead railway undertaking shall, without jeopardising the safety of the load in accordance with OPE TSI, as referred to in Appendix A to this Annex, send a ‘wagon status’ message with the event type ‘wagon ready to pull’ in accordance with point 3.2.1.2(2) of this Annex to the undertaking of origin expected to pull or push that wagon from this location.
(3)The lead railway undertaking shall, on the basis of common safety methods for risk assessment, set out the safety aspects relevant to the reuse in operation of such information for safety purposes and shall add further relevant details by agreement with the loader or where relevant the filler of the wagon.
(4)In the case of combined transport, where the operator of rail service facilities may be responsible for loading or unloading a set of wagons, they shall send the lead railway undertaking a ‘Train Running Information’ message containing the appropriate train location status and confirming the train closure and to inform them that the loaded or unloaded set of wagons parked at the reporting point is ready for movement without jeopardising the safety of the load in accordance with OPE TSI.
(5)In other cases, aspects relating to the interoperability of data sharing in relation to the readiness of the load for movement between the loader or the filler of a wagon, one the one hand, and the lead railway undertaking, one the other hand, are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
3.2.1.4.Wagon pulled
(1)The event type ‘wagon pulled’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where a wagon has been pulled or pushed from a specified loading or unloading location, the undertaking of origin responsible for that wagon shall send a ‘wagon status’ message with the event type ‘wagon pulled’, in accordance with point 3.2.1.2(2).
3.2.1.5.Wagon departure from origin
(1)The event type ‘wagon left origin’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where a wagon has left with a train the departure rail service facility, the railway undertaking of origin responsible for that train shall send a ‘wagon status’ message with the event type ‘wagon left origin’, in accordance with point 3.2.1.2(2).
3.2.1.6.Wagon arrival at intermediate location
(1)The event type ‘wagon arrival’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where a wagon arrived with a train at a specified intermediate location, the undertaking of arrival responsible for that train shall send a ‘wagon status’ message with the event type ‘wagon arrival’, in accordance with point 3.2.1.2(2).
3.2.1.7.Wagon departure from intermediate location
(1)The event type ‘wagon departure’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where a wagon left with a train a specified intermediate location, the undertaking of origin responsible for that train shall send a ‘wagon status’ message with the event type ‘wagon departure’, in accordance with point 3.2.1.2(2).
3.2.1.8.Wagon handed over
(1)The event type ‘wagon handed over’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where the responsibility of a wagon movement changes between successive undertakings and where the wagon has been physically handed over by the undertaking of arrival to the next undertaking at a specified point of interchange, the undertaking of arrival shall send a ‘wagon status’ message with the event type ‘wagon handed over’, in accordance with point 3.2.1.2(2).
3.2.1.9.Wagon taken over
(1)The event type ‘wagon taken over’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where the responsibility of a wagon movement changes between successive undertakings and where the wagon has been physically taken over by the undertaking of departure from the previous undertaking at a specified point of interchange, the undertaking of departure shall send a ‘wagon status’ message with the event type ‘wagon taken over’, in accordance with point 3.2.1.2(2).
3.2.1.10.Wagon journey irregularity
(1)The event type ‘wagon journey irregularity’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where an irregular event relating to the wagon or its load requires an action to be taken that may interrupt its transportation, the undertaking responsible for that wagon shall send a ‘wagon status’ message with the event type ‘wagon journey irregularity’, in accordance with point 3.2.1.2(2), to provide information on the event including further details about the nature of the irregularity and its consequences.
3.2.1.11.Wagon journey rectified
(1)The event type ‘wagon journey rectified’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where a wagon journey irregularity is rectified, the undertaking responsible for that wagon shall send a ‘wagon status’ message with the event type ‘wagon journey rectified’, in accordance with point 3.2.1.2(2).
3.2.1.12.Wagon arrival at destination
(1)The event type ‘wagon reached destination’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where a wagon arrived with a train at a rail service facility of destination, the railway undertaking of arrival responsible for that train shall send a ‘wagon status’ message with the event type ‘wagon reached destination’, in accordance with point 3.2.1.2(2).
3.2.1.13.Wagon delivered
(1)The event type ‘wagon delivered’ shall be in accordance with the specifications referenced in Appendix C, index [2].
(2)Where a wagon has been delivered to the loading or unloading location, the undertaking of arrival responsible for this wagon or set of wagons shall send a ‘wagon status’ message with the event type ‘wagon delivered’, in accordance with point 3.2.1.2(2).
3.2.2.Intermodal loading unit movement
Aspects relating to the interoperability of data sharing in relation to the movement of intermodal loading units are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
3.2.3.Wagon forecast information
(1)The transport of a loading by rail shall be monitored at wagon level.
(2)For intermodal transport, the transport of a loading shall also be monitored at the level of each intermodal loading unit.
(3)Each railway undertaking and each operator of rail service facilities at their facilities, shall monitor the physical transport of a loading and, no later than the time of departure from origin, or from last point of interchange, they shall calculate wagon forecast information relating to the following event types and reporting points:
(a)wagon handed over at the next point of interchange;
(b)wagon delivered at destination.
(4)Each railways undertaking and where relevant each operator of rail service facilities shall calculate and update wagon forecast information based at least on the following information:
(a)the information contained in the following messages received from infrastructure managers and operators of rail service facilities:
(i)‘Path Details’ specified in point 2.3.3;
(ii)‘Train Running Information’ specified in point 2.6.3;
(iii)‘Train Forecast information’ specified in point 2.6.4;
(b)the information contained in ‘Wagon forecast’ messages received from the previous railway undertaking, if any, from which wagons are taken over at a point of interchange.
(5)‘Wagon forecast’ message shall be in accordance with the specifications referenced in Appendix C, index [2].
(6)To provide wagon forecast information, either confirming agreed timings or notifying any changes, each railway undertaking and where relevant an operator of rail service facilities shall send a ‘Wagon forecast’ message to the following:
(a)the lead railway undertaking;
(b)the next railway undertaking, if any, to which the wagon will be handed over at point of interchange;
(c)the next operator of the rail service facility, if any, where the wagon will be handed over to shunting operators at point of interchange;
(d)freight customers that are specified in the contract of carriage.
(7)Where a railway undertaking or an operator of rail service facilities shares or grants access to wagon forecast information, they shall ensure that the quality of the ‘Wagon forecast’ messages is sufficient for the lead railway undertaking to assess its accuracy in accordance with point 1.5 and the ex post measurement methodology set out in Appendix E.
(8)The lead railway undertaking shall compare the wagon forecast information based on ‘Wagon forecast’ messages received from a railway undertaking or an operator of rail service facilities with the timings agreed with the freight customers.
3.3.Freight-specific reference files
3.3.1.General
(1)To support freight train preparation in accordance with point 2.5 and wagon operation in accordance with point 3.2.1, each wagon keeper shall ensure rolling stock reference data sharing through common European rolling stock reference databases as referred to in point 3.3.2 and.
(2)To support the operation of intermodal transport in accordance with point 3.2.2:
(a)each keeper of intermodal loading units (‘ILUs’) shall ensure ILU reference data sharing through common and centralised ILU EU reference databases as referred to in point 3.3.3;
(b)each keeper of wagons and each keeper of ILUs may ensure data sharing of the operational status of their wagons and ILUs through the common wagon and ILU operation databases, respectively, as referred to in point 3.3.4.
(3)Telematics stakeholders responsible for freight-specific reference files pursuant to points (1) and (2) shall manage their reference data in accordance with Article 8(4) and grant access for use to them under the conditions of the Creative Commons BY-ND 4.0 licence.
3.3.2.Rolling stock reference databases
(1)Under the coordination of the Agency, vehicle keepers shall cooperate to set up, manage and maintain standardised rolling stock reference databases (‘RSRDs’) at Union level in accordance with the specifications referenced in Appendix C, index [2].
(2)Vehicle keepers are responsible for populating and maintaining rolling stock reference data in an RSRD in accordance with the specifications referenced in Appendix C, index [1], and shall ensure data quality. To that end, vehicle keepers shall ensure that data shared are up to date and reflect accurately the status of the processes that the vehicle shall undergo in accordance with the applicable legislation.
(3)For the purpose of point (1), vehicle keepers shall reuse in the RSRD any rolling stock reference data from the following registers:
(a)the European Vehicle Register (EVR) set up by the Agency in accordance with Article 47 of Directive (EU) 2016/797 and Commission Implementing Decision (EU) 2018/1614, in particular ‘administrative data’ referred to in point (5)(a) of this point and ‘design data’ referred to in point (5)(b) of this point;
(b)the European register of authorised types of vehicle (ERATV) set up in accordance with Article 48 of Directive (EU) 2016/797 and Commission Implementing Decision 2011/665/EU, in particular ‘design data’ referred to in point (5)(b) of this point.
(4)To minimise the volume of data shared for operational purposes and to increase the efficiency of freight wagon operations referred to in point 3.3.1, vehicle keepers shall ensure that RSRDs make the rolling stock reference data easily and fairly accessible to telematics stakeholders pursuant to Article 4 and under the conditions of the Creative Commons BY-ND 4.0 licence.
(5)Reference data shared in a RSRD shall be grouped as follows:
(a)administrative data:
Vehicle reference data referred to in point (3)(a) of this point, relating to the authorisation of the vehicle and its registration in accordance with Articles 21 and 22 of Directive (EU) 2016/797;
(b)design data:
Vehicle reference data specified in points (3)(a) and (3)(b) relating to the technical characteristics of the rolling stock, especially data required by railway undertakings for the management of capacity and traffic in relation to their trains in accordance with Section 2, and for the management of freight wagons in accordance with point 3.2.
3.3.3.Intermodal loading unit reference databases
(1)Under the coordination of the Agency, keepers of intermodal loading units (‘ILU keepers’) shall cooperate to set up, manage and maintain common and centralised reference databases for intermodal loading units (ILUs) in accordance with points (3) to (5) and the specifications referenced in Appendix C, indexes [1] and [2].
(2)ILU keepers shall be responsible for populating and maintaining quality data in the databases referred to in point (1). To that end, ILU keepers shall ensure that data shared are up to date and reflect accurately the status of the processes that the ILU undergoes in accordance with the applicable legislation.
(3)Reference data shall be made public through the databases referred to in point (1) and shall include the following data:
(a)the identification of ILUs, including all types of semi-trailers, in accordance with the specifications referenced in Appendix C, index [4];
(b)the ILU type (container, swap body or semi-trailer) and its compatibility with wagons and routes in accordance with the specifications referenced in Appendix C, index [4];
(c)relevant loading characteristics, weights and dimensions.
(4)To minimise the volume of data shared for operational purposes and to increase the efficiency of ILU movements referred to in point 3.2.2, ILU keepers shall ensure that the databases referred to in point (1) make the ILU reference data easily and fairly accessible to telematics stakeholders pursuant to Article 4 and under the conditions of the Creative Commons BY-ND 4.0 licence.
(5)Reference data shared in accordance with point (3) shall be grouped as follows:
(a)administrative data:
ILU reference data relating to the certification of ILUs and their registration in accordance with the technical specifications referenced in Appendix C, index [4];
(b)design data:
ILU reference data relating to the technical characteristics of ILUs, in particular data required by operators of service facilities and railway undertakings for train preparation in accordance with point 2.5 and ILU movements in accordance with point 3.2.2.
3.3.4.Wagon and intermodal loading unit operational databases
3.3.4.1.General
(1)To ensure the tracking of train movement in accordance with point 2.7 and of wagon and intermodal loading unit (ILU) movement in accordance with point 3.2 and associated communications between the lead railway undertaking and other railway undertakings involved, the railway undertaking may break the train movement data shared with infrastructure managers and operators of rail service facilities involved and the lead railway undertaking in accordance with point 2.7 down into wagon movement data in accordance with point 3.2.1 and data relating to the movement of ILUs in accordance with point 3.2.2. In such cases, these data shall be shared in accordance with points (4) to (8) of this point.
(2)Operational communications between the lead railway undertaking and other railway undertaking involved shall be based on reference data shared through: (i) the rolling stock reference databases referred to in point 3.3.2 of this Annex, in particular wagon numbers as registered in the European Vehicle Register (EVR) in accordance with Implementing Decision (EU) 2018/1614; and (ii) the ILU reference databases referred to in point 3.3.3 of this Annex, in particular ILU numbers in accordance with point 3.3.3(3)(a) of this Annex.
(3)Train traffic data shared in accordance with point 2.6 by railway undertakings shall also be based on the operational status data of freight wagons referred to in point 3.3.4 when available.
(4)To minimise the volume of data shared for operational purposes and for freight customer information and to increase the efficiency of the management of freight wagons and ILUs as referred to in point 3.2, each railway undertaking may cooperate to set up, manage, and maintain common wagon and intermodal loading unit operational (‘WIMO’) reference databases in accordance with the specifications referenced in Appendix C, index [102].
(5)The WIMO databases shall make the operational status data of freight wagons and ILUs referred to in point 3.3.4 easily and fairly accessible to all telematics stakeholders involved in the transport service, including vehicle keepers and fleet managers, and to freight customers that are referred to in the contract of carriage. Corresponding data sharing shall be achieved through a telematics application in accordance with Article 14 and point 1.7.
(6)Each railway undertaking shall be responsible for populating and maintaining quality wagon status data in WIMO databases. To that end, each railway undertaking shall ensure that data shared are up to date and reflect accurately the status of the processes that wagons and ILUs must undergo in accordance with the applicable legislation.
(7)The WIMO databases shall contain real-time data relating to the movement of a wagon or an ILU from departure until its final delivery at freight customer sidings. The data shall include wagon running information and wagon forecast information.
(8)Train traffic data, wagon running information, and information relating to the movement of ILUs, shall be shared through the WIMO databases at the latest when the release time of the wagon or the ILU is received from the freight customer that is referred to in the contract of carriage. The release time shall be defined as the first entry shared in the WIMO databases for the movement of a wagon or an ILU for an identified rail transport service.
3.3.4.2.Loading of the rolling stock
Each railway undertaking of origin shall register the status ‘loading of the rolling stock’ and grant access to it in the WIMO database to until the termination of such an event is notified by the freight customer that is referred to in the contract of carriage.
3.3.4.3.Loaded rolling stock on journey
Each railway undertaking shall register the status ‘loaded wagon on journey’ and grant access to it in the WIMO database upon departure from origin, in accordance with point 3.2.1.5, of a loaded wagon.
3.3.4.4.Empty rolling stock on journey
Each railway undertaking shall register the status ‘empty wagon on journey’ and grant access to it in the WIMO database upon departure from origin, in accordance with point 3.2.1.5, of an empty wagon.
3.3.4.5.Unloading of rolling stock
The railway undertaking of arrival at destination rail service facilities shall register the status ‘unloading of the rolling stock’ and grant access to it in the WIMO database until the termination of such an event.
3.3.4.6.Empty wagon under fleet management control
Each railway undertaking shall register the status ‘empty wagon under fleet management control’ in the WIMO database, in case of such an event, to reflect the availability of a vehicle with specified characteristics.
3.4.Data sharing with other stakeholders
Infrastructure managers, operators of rail service facilities and railway undertakings shall share data with other telematics stakeholders responsible for managing connections with other modes of transport in accordance with Article 4 and the requirements laid down in Section 3.
4.Rail ticketing in relation to rail passenger services and rail passenger travel information
4.1. General
(1)The provisions of this Section lay down the requirements for interoperable data sharing required to carry out the processes referred to in Article 2(1), point (c), for any rail passenger transport service operated in the Union.
(2)Rights to access for use rail ticketing data are laid down in Articles 4 and 6.
(3)Rail ticketing data shall be based on the following:
(a)passenger timetable data specified in point 4.2;
(b)tariff data shared specified in point 4.3;
(c)data relating to conditions of carriage specified in point 4.4.
4.2.Passenger timetable data
4.2.1.Passenger timetable data of rail passenger transport services
The provisions of this point apply to any rail passenger transport services.
(1)Passenger timetable data shall comply with the specifications referenced in Appendix C, indexes [P.2] and [P.4].
(2)The passenger timetable data shall contain at least the following information:
(a)basic principles of train variants;
(b)retail representation of a train as part of the path details data referred to in point 2.4.3;
(c)different possible ways of representing days of operation;
(d)train type, brand name and, where different than rail, the associated mode of transport;
(e)transport service relationships;
(f)coach groups attached to trains;
(g)train joining to and splitting from;
(h)through-connections with a different train identifier connected (‘connecting to’);
(i)through connections with change of train identifier (‘change of service number’);
(j)details of transport services, including public arrival, public departure and passing times;
(k)stops with passenger traffic restrictions;
(l)overnight trains;
(m)crossing of time zones;
(n)pricing regime and reservation details;
(o)organisation identifier of the data provider specified in point 1.2.2;
(p)organisation identifier specified in point 1.2.2 for the reservation and distribution provider in accordance with point 4.3.1(2);
(q)service facilities;
(r)accessibility of the train in accordance with point 4.4.3.1, including scheduled existence of priority seats, wheelchair spaces, universal sleeping compartments;
(s)service extras;
(t)connection times between passenger transport services specified in point 4.2.2;
(u)station list.
(3)Each railway undertaking or where relevant the data holder shall grant access for use to passenger timetable data in accordance with Article 6(1) under the conditions of the Creative Commons BY-NC-SA 4.0 licence or any less restrictive open licence part of the Creative Common suite.
(4)At the latest 1 week after the final working timetable of a passenger rail transport service has been published by the infrastructure managers concerned, each railway undertaking or where relevant the data holder concerned shall grant access for use to the annual passenger timetable data of that service in accordance with Article 6(1).
(5)At the latest 3 weeks before an update to the annual passenger timetable of a rail transport service takes effect, each railway undertaking or where relevant the data holder concerned shall update the annual passenger timetable data in accordance with Article 6(1) of that service. The annual passenger timetable data shall be updated in line with information relating to the discontinuation of rail passenger transport services pursuant to Article 8 of Regulation (EU) 2021/782. A railway undertaking or where relevant the data holder may under exceptional circumstances apply emergency updates within shorter deadlines to its annual passenger timetable of a rail transport service.
(6)Each railway undertaking or where relevant the data holder shall grant access for use to passenger timetable data in accordance with Article 6(1) for at least 12 months after arrival of corresponding passenger rail transport service.
(7)Where a direct rail passenger transport service is operated or intended to be operated by several railway undertakings, the lead railway undertaking shall coordinate with all other railway undertakings operating that service to aggregate passenger timetable data for all stops served by that service. For each individual parts of a rail passenger transport service operated by a single railway undertaking, this undertaking shall remain responsible for granting access to the data aggregated by the lead railway undertaking.
4.2.2.Passenger timetable data of connection times
(1)Passenger timetable data of connection times shall comply with the specifications referenced in Appendix C, indexes [P.2] and [P.4].
(2)The passenger timetable data of connection times shall contain at least the following information:
(a)connection times in the station (the ‘default minimum connection time’);
(b)connection times between different locations in the station (e.g. parts of the station, platforms), if appropriate;
(c)connection times between the station and stations in the neighbourhood, if appropriate.
(3)Each station manager or where relevant the data holder shall grant access for use to passenger timetable data of connection times in accordance with Article 6(2) under the conditions of the Creative Commons BY-NC-SA 4.0 licence or any less restrictive open licence part of the Creative Common suite.
(4)At least 1 week after the final working timetable of a passenger rail transport service has been published by the infrastructure managers concerned, each station manager or where relevant, each infrastructure manager that are concerned shall grant access for use in accordance with Article 6(2) to the connection times that are applicable to that service for the upcoming annual passenger timetable.
(5)At the latest 3 weeks before an update to the annual passenger timetable connection times takes effect, station managers or where relevant infrastructure managers responsible for those changes shall update corresponding passenger timetable data in accordance with Article 6(2). A station manager or where relevant an infrastructure manager may exceptionally apply emergency updates within shorter deadlines.
(6)Each station manager or where relevant each infrastructure manager concerned shall grant access for use in accordance with Article 6(2) to data relating to its passenger timetable of connection times for at least 12 months after the end of validity of that data.
(7)Where a station manager, a railway undertaking, a distributor or a retailer combine or connect two or more passenger rail transport services, they shall use the connection times published in accordance with Article 6(2) and in accordance with points 4.2.2.2 and 4.2.2.3.
4.2.2.1.Definition and maintenance of minimum connection times
(1)Stations managers shall define in accordance with the following table the minimum connection times pursuant to Article 15 considering the alighting time of the arriving service and the boarding time limit of the departing service, including the additional time that may be required for the check-in of passengers, bicycles, or luggage:
|
|
Minimum connection time
|
Party responsible
|
Mandatory /
optional
|
|
In one location
|
Default minimum connection time in a station
|
Station manager or where relevant infrastructure manager
|
Mandatory
|
|
|
Minimum connection time for a specific type of passenger transport services operated by a specific undertaking
|
|
Optional
|
|
|
Minimum connection time for a specific type of passenger transport services, regardless of the undertaking operating that services
|
|
Optional
|
|
|
Minimum connection time for a specific undertaking, regardless of the type of passenger transport services
|
|
Optional
|
|
Between two locations
|
Default minimum connection time between two stations
|
Station managers or where relevant, infrastructure managers that are involved
|
Mandatory for stations belonging to the same meta station
|
|
|
Minimum connection time for a specific type of passenger transport services operated by a specific undertaking
|
|
Optional
|
|
|
Minimum connection time for a specific type of passenger transport services, regardless of the undertaking operating that service
|
|
Optional
|
|
|
Minimum connection time for a specific undertaking, regardless of the type of passenger transport services
|
|
Optional
|
(2)For stations with a single platform and that are not served by other scheduled passenger transport services than rail, the minimum connection time in that station shall corresponds to the duration of train stops in that station or be null.
4.2.2.2.Connection times in one location
Connection times applicable in a single location shall be used as follows:
(a)where a minimum connection time is specified for a specific pair of delivering and receiving passenger transport services, it shall be applied by station managers, railway undertakings, distributors and retailers as the minimum connection time between those services;
(b)where a minimum connection time is specified between the delivering passenger transport services of a specific undertaking in relation to a specific type of service or brand name and the receiving passenger transport services of a specific undertaking in relation to a specific type of service or brand name, it shall be applied by station managers, railway undertakings, distributors and retailers as the minimum connection time between those specific services;
(c)where a minimum connection time is specified between the delivering passenger transport services of a specific type of service or brand name and the receiving passenger transport services of a specific type of service or brand name, regardless of the operating undertakings involved, it shall be applied by station managers, railway undertakings, distributors and retailers as the minimum connection time between those specific types of services;
(d)where a minimum connection time is specified between a specific delivering undertaking and a specific receiving undertaking, regardless of the type of service or brand name of the passenger transport services involved, it shall be applied by station managers, railway undertakings, distributors and retailers as the minimum connection time between the passenger transport services of those specific undertakings;
(e)where none of the conditions set out in points (a) to (d) occur, the default minimum connection time specified for that the location shall be applied by station managers, railway undertakings, distributors and retailers.
4.2.2.3.Connection times between two locations
Connection times applicable between two locations shall be used as follows:
(a)where a minimum connection time is specified between a specific delivering undertaking in relation to a specific type of service or brand name and a specific receiving undertaking in relation to a specific type of service or brand name, it shall be applied by station managers, railway undertakings, distributors and retailers as the minimum connection time between those specific services;
(b)where a minimum connection time is specified between the delivering passenger transport services of a specific type of service or brand name and the receiving passenger transport services of a specific type of service or brand name, regardless of the operating undertakings involved, it shall be applied by station managers, railway undertakings, distributors and retailers as the minimum connection time between those specific types of services;
(c)where a minimum connection time is specified between a specific delivering undertaking and a specific receiving undertaking, regardless of the type or brand name of the passenger transport services involved, it shall be applied by station managers, railway undertakings, distributors and retailers as minimum connection time between the passenger transport services of those specific undertakings;
(d)where a default minimum connection time is specified between two locations, it shall be applied by station managers, railway undertakings, distributors and retailers as the minimum connection time between those locations;
(e)where none of the conditions set out in points (a) to (d) occur, no minimum connection time may be applied.
4.2.2.4.Calculation of connection time
Aspects relating to the interoperability of the calculation of the following aspects are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex:
(1)connection time for passengers;
(2)connection time adapted to persons with disabilities and persons with reduced mobility;
(3)connection time adapted for passengers transporting a bicycle;
(4)additional time for the check-in of passengers, bicycles or luggage.
4.3.Tariff data
4.3.1.Fares data of rail passenger transport services
(1)Tariff data shall comply with the specifications referenced in Appendix C, indexes [P.3] and [B.xx].
(2)The tariff data shall contain passenger rail transport services, or part of such services, and at least the following information:
(a)the tariffs and associated tables of fares, or the structure of fares for tariffs indicated as subject to yield management or capacity considerations;
(b)existing direct and indirect online sales channels of authorised distributors where live availability of offers can be checked;
(c)a link to the applicable general and specific conditions of carriage in accordance with point 4.4;
(d)all pre-journey tariff related information necessary for authorised retailers that is defined in Annex II to Regulation (EU) 2021/782;
(e)all information necessary for authorised issuers to issue tickets in accordance with the following specifications:
(i)the specifications referenced in Appendix C, indexes [B.11] and [B.12];
(ii)point
4.5
where the tariff is subject to an availability check or reservation;
(iii)point
4.6
for security elements;
(f)rail ticketing and ticket check rules specified in point 4.3.2.
(3)Each railway undertaking or where relevant the data holder shall grant access for use to its tariff data in accordance with Article 6(3) under the conditions of the Creative Commons BY-ND 4.0 licence or any less restrictive open licence part of the Creative Common suite.
(4)At the latest 1 week after the final working timetable of a passenger rail transport service has been published by the infrastructure managers that are concerned, each railway undertaking or where relevant the data holder shall grant access for use to the tariff data of that service in accordance with Article 6(3) to ensure that this service can be purchased in advance without prejudice to other tariffs for the same service which would be made accessible in accordance with their respective sales conditions.
(5)At least 6 days before an update to the tariff of a rail transport service takes effect and without prejudice to other tariffs for the same service which would be made accessible in accordance with their respective sales conditions, the railway undertaking or where relevant the data holder responsible for those changes shall grant access to corresponding data in accordance with Article 6(3).
4.3.2.Management of rail ticketing and ticket check rules
(1)To implement rail ticketing and ticket check rules consistently between railway undertakings, distributors, issuers and ticket control organisations, each railway undertaking shall grant access for use to:
(a)the conditions of carriage specified in point 4.4;
(b)the rail ticketing and ticket check rules.
(2) Each railway undertaking or where relevant the data holder shall share the description of rail ticketing and ticket check rules as structured data in a machine-readable format with any distributor or any issuer that is authorised to re-link to the availability of their products and with ticket control organisations. Aspects relating to the technical interoperability of corresponding data sharing are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
4.3.3.Information about the online sales channels of railway undertakings
Where a telematics stakeholder involved in journey planning as part of rail ticketing processes, presents information resulting from journey planning based on data accessed under Articles 4 to 6 for rail products it is neither authorised as a retailer to sell nor as a distributor to relink to their availability through the attributing system of the railway undertakings involved, it shall at least point directly to the railway undertakings’ authorised sales channels referred to in point 4.3.1(2)(b) where availability can be checked by an authorised distributor.
4.4.Conditions of carriage
4.4.1.General
(1)Data relating to the conditions of carriage shall contain the information listed in points 4.4.2 to 4.4.6.
(2)Each railway undertaking shall for the passenger transport services it is operating grant access for use to data relating to the conditions of carriage of pursuant to Article 6(1) and under the conditions of the Creative Commons BY-NC-SA 4.0 licence or any less restrictive open licence part of the Creative Common suite.
(3)Each railway undertaking shall publish and display on its official website the conditions of carriage applicable to the rail transport services it operates.
(4)Where a retailer presents a passenger transport service, it shall display on its website and mobile applications the conditions of carriage based on data it has access to in accordance with point (2) or via a link to the publication of relevant railway undertaking in accordance with point (4).
(5)Website and mobile applications used to display the conditions of carriage pursuant to points (4) and (5) shall be perceivable, operable, understandable and robust in accordance with the requirements for accessibility set out in the specifications referenced in Appendix C, index [P.6].
(6)The presentation of the conditions of carriage shall be displayed in a clearly identified manner and shall be accessible in accordance with Article 22 of Regulation (EU) 2021/782 and the specifications laid down in the Annex to Commission Regulation (EU) No 1300/2014 (PRM TSI), as referred to in Appendix A to this Annex.
(7)At least 6 days before an update to the conditions of carriage of a rail transport service takes effect, the railway undertakings responsible for those changes shall grant access to corresponding data pursuant to Article 6. The railway undertakings shall list the points which have been changed compared to the previous version. For each change, they shall maintain the access to the earlier version of the data for at least 1 year after it has ceased to apply.
4.4.2.Conditions for the carriage of passengers
Each railway undertaking or where relevant the retailer shall draw the attention of passengers to the following information relating to conditions of carriage of passenger:
(a)the railway undertaking’s conditions of carriage;
(b)information about passenger rights pursuant to Article 30 of Regulation (EU) 2021/782;
(c)the accepted means of payment;
(d)sales and after-sales conditions, especially for the exchange and reimbursement of tickets;
(e)procedures for the submission of complaints without prejudice to and in compliance with Article 18 of Regulation (EU) 2021/782.
4.4.3.Conditions of carriage and assistance for persons with disabilities and persons with reduced mobility (‘PRM’)
4.4.3.1.Accessibility of rolling stock
Each railway undertaking or where relevant the retailer shall draw the attention of passengers to the following information relating to the accessibility of rolling stock:
(a)the train types and train numbers where PRM facilities are available (the line number where no train number is to be publicly available);
(b)the types and minimum quantities of PRM facilities in the trains as specified in the PRM TSI, referred to in Appendix A to this Annex, under normal operating conditions;
(c)the methods for requesting assistance in boarding and disembarking from trains, in particular the following information:
(i)notice period;
(ii)points of contact for requesting assistance, including the email address and telephone number of the offices for PRM assistance;
(iii)operating hours;
(iv)conditions under which assistance is provided in accordance with Articles 23 and 24 of Regulation (EU) 2021/782;
(d)the maximum size and weight of wheelchairs, including the weight of the passenger, permitted without prejudice to the PRM TSI, as referred to in Appendix A to this Annex;
(e)transport conditions for accompanying persons and/or animals;
(f)a link where the conditions of access to the station are available in accordance with point 4.4.3.2.
4.4.3.2.Accessibility of station
(1)Each railway undertaking or where relevant the retailer shall draw the attention of passengers to information relating to the accessibility of stations of departure and arrival based on the accessibility data referred to in point (2), where available.
(2)Each station manager or where relevant the infrastructure manager or the data holder as the entity in charge of collecting, maintaining and exchanging accessibility data in accordance with Article 7a of the PRM TSI, shall collect, convert and transfer that data to the European railway stations accessibility database (‘ERSAD’) hosted by the Agency in accordance with the PRM TSI, as referred to in Appendix A to this Annex, and format set out in the specifications referenced in Appendix C, index [B.15], of this Annex, under the access conditions of the Creative Commons BY-NC-SA 4.0 licence or any less restrictive open licence part of the Creative Common suite.
(3)Accessibility data as referred to in point (1) shall include information relating to the accessibility of station and associated facilities, including whether the station is classified as accessible for PRM and whether it is staffed for PRM assistance.
4.4.4.Condition for the carriage of registered luggage
Each railway undertaking or where relevant the retailer shall draw the attention of passengers to information relating to the conditions of carriage for registered luggage where a service for luggage registration is offered.
4.4.5.Conditions for the carriage of bicycles
(1)Each railway undertaking or where relevant the retailer shall draw the attention of passengers to the following information relating to conditions of carriage of bicycles where the carriage of bicycles is offered in accordance with Article 6 of Regulation (EU) 2021/782:
(a)the types and numbers of trains on which the carriage of bicycles is available and where no train number is available for the public, the line number, including the types and the number of bicycles permitted;
(b)particular times and periods when the carriage of bicycles may be restricted;
(c)any applicable fares for the carriage of bicycles;
(d)whether a specific reservation for a bicycle place in the train is required and the method to be used to reserve one, including the following:
(i) the notice period;
(ii) details of specific sales channels for the reservation of a bicycle place and operating hours, if applicable;
(e)up-to-date information on the availability of capacity for the transport of bicycles.
(2)Each railway undertaking shall indicate if the transport of bicycles is not offered.
4.4.6.Conditions for carriage of cars, motorcycles and boats (‘cars’)
Each railway undertaking or where relevant the retailer shall draw the attention of passengers to the following information relating to conditions for carriage of cars where a service for the carriage of cars is offered:
(a)the types and numbers of trains on which the carriage of cars is available;
(b)particular times and periods when the carriage of cars is available;
(c)the standard fares for the carriage of cars, including fares for the accommodation of passengers where accommodation is offered by the railway undertaking;
(d)the specific address and time for the loading of cars onto the train;
(e)the specific address and time of arrival of the train at the station of destination for the unloading of cars from the train;
(f)size, weight and other limitations for the transport of cars.
4.5.Availability and reservations
4.5.1.General
(1)Authorisation to provide a service for confirmed personalised arrangements, namely a reservation, such as transportation, accommodation or assistance, may upon request of the distributor be part of a single transaction combining both a transport contract and one or more specified type of assistance or specific type of accommodation.
(2)Alternatively, a reservation may concern, in addition to the transport contract, only the selling of a ticket (a booking) for a specified type of assistance or a specific place of accommodation (any type of passenger accommodation such as a seat, couchette, sleeping compartment, priority seat or wheelchair space). It may also concern the reservation of a transport service related to the carriage of luggage or a car or the reservation of a bicycle space.
(3)The availability of a rail product shall refer to an offer which can be purchased by a passenger at a given point in time for the following services:
(a)a specified type of assistance;
(b)a specified type of accommodation;
(c)the carriage of luggage, a car or a bicycle space; or
(d)yield managed fares.
Offers shall indicate that a rail product is proposed as part of a catalogue, although it may not be available, that is to say it may be sold out or not be applicable for purchase by a passenger at a given point in time for a specific train and is subject to an availability check.
(4)Availability and reservation data of rail products that are subject to an availability check shall be exchanged between authorised distributors and the respective attributing systems of the railway undertakings involved, in accordance with Article 10 of Regulation (EU) 2021/782.
(5)It shall be possible for any distributor, providing either a direct or an indirect sales channel as referred to in point 4.3.1(b), to combine rail products into offers in a fair, transparent and non-discriminatory manner independently of the railway undertakings involved. The distributor shall be able to retrieve the trip information from its journey planner and then determine from its pricing engine the associated fares or range of fares for each leg of the passenger journey as a whole or, where applicable, for parts of it Both the journey planner and the pricing engine of the distributor shall be able to use data accessed pursuant to Articles 4 and 6 of this Regulation. Distributors, that are by definition authorised to check the availability of and reserve a rail product, shall relink those offers to their respective availability through the attributing system of the railway undertaking and allow those offers to be booked.
(6)Specifications relating to the combination of products available from the distributor reconciling trips with available tariffs and proposing available offers to the retailer, as well as corresponding communications between the distributor and the retailer, are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
(7)Except for the specifications relating to the APIs to be used by distributors used to check the availability or reserve a rail product that are set out in point 4.5, the specifications relating to the APIs used to book a rail product are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
4.5.2.Availability and reservation request
(1)Distributors shall ensure that their distribution system enable to share the requests from customers (retailers or clients) for availability or reservation of a specified rail product with the railway undertakings concerned through their attributing systems, in accordance with the specifications referenced in Appendix C, index [B.5].
(2)In accordance with Part III of Annex II to Regulation (EU) 2021/782, the different types of reservation requests shall be as follows:
(a)availability request;
(b)reservation request;
(c)partial cancellation request;
(d)full cancellation request.
4.5.3.Availability and reservation response
(1)If a request for availability or reservation has been made by the distributor in accordance with point
4.5.2
, the attributing system of the respective railway undertakings shall share a response with the requesting distribution system of the distributor in relation to the passenger transport services requested and in accordance with the specifications referenced in Appendix C, index [B.5]14.
(2)The different types of reservation responses are as follows:
(a)reply about availability;
(b)confirmation of a reservation request;
(c)confirmation of a partial cancellation request;
(d)confirmation of a complete cancellation request;
(e)replacement proposal;
(f)negative reply.
4.5.4.Availability of and reservations for PRM assistance
(1)Each railway undertaking and each distributor shall ensure that their attributing system and their distribution system respectively are able to share data relating to the carriage and assistance of PRM in accordance with the specifications referenced in Appendix C, index [B.10].
(2)Each railway undertaking shall ensure that its attributing system is able to issue a confirmation number for the reservation of PRM assistance for each departure and arrival of each passenger rail transport service reserved. A confirmation number gives the passenger the guarantee and confidence that the assistance will be provided and establishes accountability and responsibility of the railway undertaking for the provision of assistance.
4.5.5.Availability of and reservations for bicycle places
At least for passenger transport services where a reservation for bicycle places is required in accordance with Article 6(1) of Regulation (EU) 2021/782, each railway undertaking shall ensure that its attributing system is able to handle a check for the availability of or a reservation of bicycles places in accordance with the specifications laid down in points
4.5.2
and
4.5.3
of this Annex.
4.5.6.Availability and reservations for cars
At least for passenger transport services offering the carriage of cars, each railway undertaking shall ensure that its attributing system is able to handle a check for the availability of or a reservation for the carriage of cars in accordance with the specifications laid down in points
4.5.2
and
4.5.3
.
4.6.Security elements for product distribution
The issuer is responsible for the fulfilment of tickets, including the reporting of issued tickets to the railway undertakings concerned.
4.6.1.Security elements for electronic delivery
(1)Each issuer of a ticket or a reservation for a passenger transport service shall generate the security data in accordance with the specification referenced in Appendix C, index [B.12], as soon as the booking status and sales transaction data have been successfully sent to the distribution system of the distributor.
(2)To ensure that the authenticity of the security elements can be checked by relevant ticket control organisations, the issuer shall create those security elements for electronic delivery using a public key infrastructure (PKI) in accordance with point 1.3.
4.6.2.Dossier reference
(1)Each issuer shall produce a dossier reference in accordance with the specifications referenced in Appendix C, index [B.5], to report the tickets or reservations it issued to the railway undertakings concerned. Each issuer shall perform the following actions:
(a)link the dossier reference with all data concerning the ticket;
(b)register the dossier reference in the attributing system of the railway undertakings concerned;
(c)include the dossier reference on the ticket or reservation of the passenger.
(2)Each issuer shall perform the process set out in point (1) as soon as the booking status and sales transaction data have been successfully sent to the distribution system of the distributor.
4.6.3.Fulfilment methods
4.6.3.1.General
(1)Each railway undertaking and ticket control organisation shall accept tickets issued electronically in accordance with the specifications referenced in Appendix C, index [B.11], except in any of the following case:
(a)the ticket is not appropriate for the passenger journey being undertaken;
(b)the ticket control organisation has reasonable grounds to suspect fraud;
(c)the ticket is not being used in accordance with the conditions of carriage referred to in point 4.4
4.4
.
(2)For the purposes of issuing tickets, each issuer shall use at least one of the fulfilment methods set out in points 4.6.3.2 and 4.6.3.3 to deliver the rail product purchased to the customer.
(3)The same fulfilment methods shall be accepted by railway undertakings for both sales performed by one of the railway undertakings involved (‘direct sales’) and those performed by an independent issuer (‘indirect sales’).
4.6.3.2.Direct fulfilment methods
(1)For cross-border and international tickets, the following conditions shall apply where an issuer uses direct fulfilment methods:
(a)each issuer shall issue tickets of the following types as laid down in the specifications referenced in Appendix C, index [B.11]:
(i)ticket and reservation;
(ii)ticket only;
(iii)reservation only;
(iv)supplements;
(v)boarding pass;
(vi)ticket only or ticket and reservation for special fares in conjunction with national railcards;
(vii)ticket only or ticket and reservation for Group ticket;
(viii)international rail passes;
(ix)accompanied vehicle coupon;
(b)each issuer shall use the format laid down in the specifications referenced in Appendix C, index [B.11], corresponding to the type referred to in point (a).
(2)For domestic, that is to say not cross-border, tickets, where an issuer uses direct fulfilment methods, it may use one of the following format laid down in the specifications referenced in Appendix C, index [B.11]:
(a)rail combined ticket 2 (RCT2);
(b)rail credit card size ticket (RCCST).
4.6.3.3.Indirect fulfilment methods
(1)For cross-border and international tickets, the following conditions shall apply where an issuer uses indirect fulfilment methods:
(a)each issuer shall issue tickets of one of the following types as laid down in the specifications referenced in Appendix C, index [B.11]:
(i)non-integrated reservation ticket (NRT): travel only;
(ii)non-integrated reservation ticket (NRT) + reservation: travel and reservation;
(iii)non-integrated reservation ticket (NRT) + supplement: travel and supplement;
(iv)non-integrated reservation ticket + reservation + supplement: travel, reservation and supplement;
(v)integrated-reservation ticket (IRT): travel and reservation;
(b)each issuer shall use one of the following formats laid down in the specifications referenced in Appendix C, index [B.11], for electronic delivery, namely ticket on departure or manifest on list:
(i)A4 ticket via electronic delivery for visual inspection by barcode readers;
(ii)flexible ticket via electronic delivery for visual inspection by barcode readers.
(2)For domestic, that is to say not cross-border, tickets, where an issuer uses indirect fulfilment methods, it shall use one of the following formats laid down in the specifications referenced in Appendix C, index [B.11], for electronic delivery, namely ticket on departure or manifest on list, and visual inspection by ticket control organisation through barcode readers:
(a)A4 ticket ;
(b)flexible ticket.
4.6.4.Ticket control and ticket state modification
Ticket control organisations that have received security certificates for ticketing from the issuer shall share ticket control data and ticket state changes with ticket issuers in accordance with points 4.6.4.1 and 4.6.4.2.
4.6.4.1.Ticket annotation
(1)The ‘ticket annotation’ message and the ‘ticket check’ message shall be in accordance with the specifications referenced in Appendix C, index [B.14].
(2)A ticket control organisation shall send a ‘Ticket annotation’ message including a ‘ticket check’ message in due time to the issuer of the ticket and to other ticket control organisations involved in the ticket check and ticket annotation.
4.6.4.2.Reimbursement or compensation request
(1)The requesting distribution system of the distributor shall send reimbursement and compensation requests on behalf of passengers to the attributing system of the railway undertakings concerned in respect of the relevant ticket or through-ticket.
(2)The structure of passengers’ reimbursement or compensation requests shall comply with Commission Implementing Regulation (EU) 2024/949. The corresponding specifications for interoperable data sharing between a distributor and railway undertaking concerned are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
4.7.Passenger travel information during the journey
4.7.1.Information in the station
4.7.1.1.General
(1)Each station manager shall provide passengers in the station pursuant to Article 9(2) of Regulation (EU) 2021/782 with visual and spoken passenger travel information that is accessible in accordance with Article 22 of Regulation (EU) 2021/782 and the specifications laid down in the PRM TSI, as referred to in Appendix A of this Annex.
(2)Each station manager or where relevant the data holder shall integrate information they hold in relation to the station, including platforms and where relevant platform sections, where trains are intended to stop, in accordance with the specifications referenced in Appendix C, indexes [P.2] and [P.4], of this Annex with the following information relating to the arrival and departure of trains:
(a)train traffic based on data contained in the messages received pursuant to point 2.7;
(b)train composition based on data contained in the messages received pursuant to point 2.6.1.
(3)Each station manager or where relevant the data holder shall grant access for use to the information integrated pursuant to point (2) to other telematics stakeholders in accordance with Article 4 and via national access points under the conditions of the Creative Commons BY-SA 4.0 licence or any other less restrictive open licence part of the Creative Common suite.
(4)The provisions of point (1) apply without prejudice to the provisions of the PRM TSI, as referred to in Appendix A of this Annex, to stations where information systems, namely voice announcements or dynamic visual devices as displays, are renewed, upgraded or newly installed.
(5)Each station manager or where relevant each infrastructure manager shall decide in accordance with Article 15(3) and (4) on the following points:
(a)the type of information systems, namelyvoice announcements or dynamic visual devices as displays, installed;
(b)the point in time when the information is provided;
(c)the location in the station where the information systems are installed.
4.7.1.2.Train departures
Each station manager shall provide passengers in the station with at least the following train departure information:
(a)train type and train number;
(b)stations of destination;
(c)any intermediate station stops;
(d)departure time;
(e)departure platform or track;
(f)correspondence between platform sections and carriage numbers, where applicable.
4.7.1.3.Train arrivals
Each station manager shall provide passengers in the station with at least the following train arrival information:
(a)train type and train number;
(b)stations of origin;
(c)any intermediate station stops;
(d)arrival time;
(e)arrival platform or track;
(f)correspondence between platform sections and carriage numbers, where applicable.
4.7.1.4.Deviations from scheduled times
(1)Where a passenger transport service deviates from the working timetable, the infrastructure managers concerned shall provide station managers in due time with relevant traffic and travel information and deviations from the scheduled information as set out in point (3) and in accordance with the specifications referenced in Appendix C, index [2].
(2)In the event of deviation from the scheduled information, each station manager shall provide passengers in the station with real-time running and forecast information. Corresponding deviations shall be clearly identified for the attention of the passengers in the station.
(3)Deviations from the scheduled information shall include at least the following information based on train traffic data as set out in point 2.7:
(a)delays and reasons for delay, if known, as part of the train delay cause;
(b)change of track or platform, as part of the train running information;
(c)full or partial cancellation of a train and rerouting, as part of the train journey modification information.
4.7.2.Information in the vehicle
(1)Each railway undertaking shall provide passengers within the vehicle pursuant to Article 9(2) of Regulation (EU) 2021/782 with up-to-date customer information that is accessible in accordance with Article 22 of Regulation (EU) 2021/782 and the specifications laid down in the PRM TSI, as referred to in Appendix A of this Annex. Such information shall be integrated on the basis of train traffic data contained in the messages received pursuant to point
2.6
of this Annex.
(2)The provisions of point (1) shall apply, without prejudice to the provisions of the PRM TSI, as referred to in Appendix A of this Annex, to new rolling stock and to renewed or upgraded rolling stock where information systems, namely voice announcements or displays, are renewed, upgraded or newly installed.
(3)Each railway undertaking shall provide passengers in the vehicle with at least the following information:
(a)at station of departure and at any intermediate station stops:
(i)the train type and number;
(ii)the final destinations;
(iii)any intermediate stations ahead;
(iv)the scheduled arrival time at final destination and intermediate stops;
(b)the estimated departure time, reasons for delay, if known, and other information about the disruption;
(c)the name of the next station before arrival at any intermediate stations;;
(d)before arrival at any major intermediate station and at the final destination:
(i)the name of the next station;
(ii)the scheduled arrival time;
(iii)the estimated arrival time, reasons for delay, if known, and other information about the disruption;
(iv)the next main connecting services, at the discretion of the railway undertaking.
(4)Each railway undertaking shall decide on:
(a)the type of information systems, namelydisplays and voice announcements, installed;
(b)the point in time when the information is provided;
(c)the location in a train where the information systems are installed.
4.8.Common reference data for rail ticketing
(1)The Agency shall manage the following common code lists for rail ticketing as common reference data in accordance with Articles 8 and 9 and the specifications referenced in Appendix C, index [1] and grant access for use to them under the conditions of the Creative Commons BY-ND 4.0 licence:
(a)reference file for European reservation systems;
(b)reference file of codes for passenger timetable data;
(c)reference file of codes for tariff data;
(d)message-dataset catalogue;
(e)passenger code list;
(f)any other files and code lists needed for the use of the technical documents referenced in Appendix C.
(2)Common code lists for rail ticketing shall be in accordance with the specifications referenced in Appendix C, index [2].
4.9.Data sharing with other stakeholders
For the purpose of data sharing by infrastructure managers, operators of rail facilities and railway undertakings with other telematics stakeholders that are responsible for the management of connections between passenger trains and other modes of passenger transport and of other modes of transport managed as part of or in replacement of rail passenger transport services, the requirements laid down in Section 4 apply to data shared pursuant to Article 4. Such data shall be compliant only with the following specifications referenced in Appendix C:
(a)for reference locations specified in point 1.2.2: index [P.1];
(b)for passenger timetable data specified in point 4.2: indexes [P.2] and [P.4];
(c)for tariff data specified in point 4.3: indexes [P.3] and [B.xx];
(d)for data relating to passenger travel information during the train journey, including dynamic travel and traffic data in accordance with Article 5 of the MMTIS Regulation: index [P.5] based on information contained in the messages referred to in point 2.6.1(1).
5.List of specific cases
5.1.General
(1)Railway undertakings subject to a positive self-assessment in accordance with Article 18 shall not be prevented by a specific case from accessing corresponding network.
(2)The specific cases as listed in point 5.2 describe special provisions that are needed and authorised on particular networks of each Member State and include interface requirements subject to specific cases declared in other acts adopted under Directives (EU) 2016/797 or (EU) 2016/798. Specific cases are classified as either of the following:
(a)‘P’ case: permanent;
(b)‘T’ case: temporary, where corresponding interoperability requirements shall be met by a specified date.
5.2.List of specific cases
There are no specific cases indicated for this TSI.
APPENDIX A
INTERFACES IN RELATION TO OTHER SUBSYSTEMS
Interfaces of the ‘telematics applications’ subsystem in relation to other subsystems are described below.
A.1Interoperability requirements related to accessibility
The table below sets out the links between the requirements in the Annex to this TSI (the ‘Telematics TSI’) and the Annex to Regulation (EU) No 1300/2014 (PRM TSI).
A.2Interoperability requirements related to capacity management, train preparation and traffic management
The table below sets out the safety-relevant links between the requirements of the Annex to this TSI (the ‘Telematics TSI’) and the Annex to Implementing Regulation (EU) 2019/773 (OPE TSI).
|
Requirement
|
Reference in the Telematics TSI
|
Reference in the OPE TSI
|
|
Identification of trains
|
2.1
|
Object identifiers
|
4.2.3.2
|
Identification of trains
|
|
Capacity allocation
|
2.3
|
Capacity allocation
|
4.2.3.1
4.2.3.2
|
Train planning and timetable
Identification of trains
|
|
Temporary restrictions or modification
|
2.4.3
|
Publication of capacity restrictions
|
4.2.1.2.2
4.8.1
|
Route book
Additional information on infrastructure
|
|
Train preparation
|
2.5.1
|
Train composition
|
4.2.2.5.2
4.2.2.7
|
Train composition
Ensuring that the train is in running order
|
|
|
2.5.2
|
Train ready
|
4.2.3.3
|
Train departure
|
|
Train reporting
|
2.6.3
2.6.4
|
Train running information
Train forecast information
|
4.2.3.4.2
|
Train reporting
|
|
|
3.2.3
Appendix E
|
Wagon forecast information
Accuracy of forecast information for train and wagon movements
|
4.2.3.4.4.
|
Operational quality
|
|
|
2.6.8
|
Historical record of train traffic data
|
4.2.3.5
|
Data recording
|
|
Wagon reporting
|
3.2.1.3
|
Wagon ready for movement
|
4.2.2.4.1
|
Safety of load
|
A.3Interoperability requirements related to noise
The following table sets out the links between the requirements in the Annex to this TSI (the ‘Telematics TSI’) and the Annex to Regulation (EU) No 1304/2014 (NOI TSI).
|
Requirement
|
Reference in the Telematics TSI
|
Reference in the NOI TSI
|
|
Capacity allocation
|
2.3
|
Capacity allocation
|
Appendix D
|
Quieter routes
|
|
Train preparation
|
2.5.1
|
Train composition
|
4.4.
7.2.2
|
Specific rules for the operation of wagons on quieter routes
Additional provisions for the application of this TSI to existing wagons
|
A.4Interoperability requirements related to control-command and signalling
The following table sets out the links between the requirements in the Annex to this TSI (the ‘Telematics TSI’) and in the Annex I to Implementing Regulation (EU) 2023/1695 (CCS TSI).
|
Requirement
|
Reference in the Telematics TSI
|
Reference in the CCS TSI
|
|
Train preparation
|
2.5.2
|
Train ready
|
4.2.4.2
|
Voice and operational communication applications
|
|
|
|
|
|
‘Start of mission’ procedure in ETCS L2
|
APPENDIX B
LIST OF OPEN POINTS
The following table sets out the requirements and testing procedures for telematics that are open points in accordance with Article 4(6) of Directive (EU) 2016/797. The testing procedures to be applied to assess compliance with those requirements are also open points.
|
Telematics TSI point
|
Open point
|
|
Requirements
|
|
1.7.1
|
Web user interfaces for capacity management, train preparation, and traffic management
|
|
1.7.2
|
Web user interfaces for the management of freight wagons and their loading
|
|
2.1.7 (3)
|
Identification of shunting trains in rail service facilities
|
|
2.2
|
Strategic management of infrastructure capacity
|
|
2.3.1 (4)
|
Planning of shunting movements and stabling in rail service facilities
|
|
2.3.9
|
Capacity allocation coordination process
|
|
2.4.1
|
Coordination of capacity restrictions
|
|
2.4.2
|
Consultation of stakeholders affected by planned capacity restrictions
|
|
2.4.3
|
Publication of capacity restrictions
|
|
2.4.4 (2)
|
Changes of nominal infrastructure characteristics resulting from an unplanned capacity restriction
|
|
2.6.7
|
Path section modification
|
|
3.1.2
|
Booking systems for freight rail transport services
|
|
3.2.1.3 (5)
|
Load ready for movement
|
|
3.2.2
|
Movement of intermodal loading units
|
|
4.2.2.4
|
Calculation of connection times and additional times for check-in
|
|
4.3.2
|
Management of rail ticketing and ticket check rules
|
|
4.5.1
|
Combination of products and communications between distributors and retailers
|
|
4.5.1
|
Booking application programming interface
|
|
4.6.4.2
|
Reimbursement or compensation requests
|
|
Testing procedures
|
|
Appendix D.3.B
|
Testing procedures for tariff data
|
|
Appendix D.3.C
|
Testing procedures for passenger-specific reference files
|
|
Appendix D.3.D
|
Testing procedures for booking functions
|
APPENDIX C
LIST OF REFERENCED STANDARDS AND
TECHNICAL DOCUMENTS
Semantic versioning of technical documents
(1)While only baseline versions of technical documents are listed below, further minor and maintenance releases of a referenced version may be issued by the Agency as an acceptable means of compliance in accordance with Article 12.
(2)Where an update of a technical document triggers a new baseline, that update shall include an indicative transition period for application pending further revision of this Regulation updating the references listed in Tables C.1 to C.4.
C.1List of common referenced technical documents
|
Index
|
Characteristics to be assessed
|
Telematics TSI point
|
Mandatory standard point
|
|
[1]
|
ERA-TD-XXX – Version 1
Reference files
|
|
|
Common reference data
|
|
|
Organisations reference file
|
1.2.1
|
|
|
|
Locations reference file
|
1.2.2
|
|
|
|
Freight specific reference data
|
|
|
Rolling stock reference databases
|
3.3.2(1)
|
|
|
|
Intermodal loading unit reference databases
|
3.3.3(1)
|
|
|
|
Common reference data for rail ticketing
|
|
|
Reference file for European reservation systems
|
4.8
|
|
|
|
Reference file of codes for passenger timetable data
|
|
|
|
|
Reference file of codes for tariff data
|
|
|
|
|
Message-dataset catalogue
|
|
|
|
|
Passenger code list
|
|
|
|
[2]
|
ERA Ontology – Version 4
Ontology of the rail system
|
|
|
|
1.4
|
|
|
[3]
|
ERA-TD-XXX – Version 1
Public key infrastructure (PKI)
|
|
|
Asymmetric or symmetric encryption, public key infrastructure (‘PKI’)
|
1.3(1)
|
|
|
[4]
|
ERA/TD/2023-01/CCT – Version 1
Facilitation of combined transport
|
|
|
Identifiers of ILUs
|
3.3.3(3)(a)
|
|
|
|
Compatibility of ILUs with wagons and routes
|
3.3.3(3)(b)
|
|
|
[100]
|
ERA-TD-100 – Version 4
Figure and sequence diagrams of telematics messages
|
|
|
Capacity allocation
|
2.3
|
|
|
|
Train preparation
|
2.5
|
|
|
|
Train traffic data
|
2.6
|
|
|
|
Movement of freight wagons
|
3.2.1
|
|
C.2List of referenced technical documents specific to data sharing in relation to capacity management, traffic management, and train preparation
|
Index
|
Characteristics to be assessed
|
Telematics TSI point
|
Mandatory standard point
|
|
[104]
|
ERA-TD-104 – Version 4
Common interface
|
|
|
Application programming interface (‘API’)
|
1.7(1)
|
|
|
[105]
|
ERA-TD-105 – Version 3
Data and message model
|
|
|
Data presentation
|
1.4(2)(a)
|
|
C.3List of referenced technical documents to data sharing specific for the management of freight wagons and their loading
|
Index
|
Characteristics to be assessed
|
Telematics TSI point
|
Mandatory standard point
|
|
[102]
|
ERA-TD-102 – Version 4
Common wagon and intermodal loading unit operational (‘WIMO’) database
|
|
|
Common wagon and intermodal loading unit operational (‘WIMO’) database
|
3.3.4.1(4)
|
|
C.4List of referenced specifications specific to rail ticketing in relation to rail passenger transport services and rail passenger travel information
C.4.AList of referenced standards
|
Index
|
Characteristics to be assessed
|
Telematics TSI point
|
Mandatory standard point
|
|
[P.1]
|
CEN/TS 16614-1:2020
Public transport – Network and Timetable Exchange (NeTEx) – Part 1: Public transport network topology exchange format
|
|
|
Sharing of reference locations data sharing with other modes of transport
|
4.9
|
|
|
[P.2]
|
CEN/TS 16614-2:2020
Public transport – Network and Timetable Exchange (NeTEx) – Part 2: Public transport scheduled timetables exchange format
|
|
|
Passenger timetable data for rail passenger transport services
|
4.2.1(1)
|
|
|
|
Passenger timetable data of connection times
|
4.2.2(1)
|
|
|
|
Passenger timetable data sharing with other modes of transport
|
4.9
|
|
|
|
Passenger travel information within the station
|
4.7.1
|
|
|
[P.3]
|
CEN/TS 16614-3:2020
Public transport – Network and Timetable Exchange (NeTEx) – Part 3: Public transport fares exchange format
|
|
|
Fares data for rail passenger transport services
|
4.3.1(1)
|
|
|
|
Fares data sharing with other modes of transport
|
4.9
|
|
|
[P.4]
|
CEN/TS 16614-4:2020
Public transport - Network and Timetable Exchange (NeTEx) – Part 4: Passenger Information European Profile
|
|
|
Passenger timetable data for rail passenger transport services
|
4.2.1(1)
|
|
|
|
Passenger timetable data of connection times
|
4.2.2(1)
|
|
|
|
Passenger timetable data sharing with other modes of transport
|
4.9
|
|
|
|
Passenger travel information within the station
|
4.7.1
|
|
|
[P.5]
|
EN 15531:2015
Public transport – Service interface for real-time information relating to public transport operations – Part 2: Communications
|
|
|
Data sharing with other modes of transport in relation to passenger travel information during train journeys
|
4.9
|
|
|
[P.6]
|
EN 301549:2021
Accessibility requirements for ICT products and services
|
|
|
Accessibility of information intended for passenger
|
|
|
Accessibility of website and mobile applications used to present the conditions of carriage to passengers
|
4.4.1(6)
|
|
|
[P.7]
|
EN 12896-1:2016
Public transport – Reference data model – Part 1: Common concepts
|
|
|
Data presentation
|
1.4(2)(b)
|
|
C.4.BList of referenced technical documents
|
Index
|
Characteristics to be assessed
|
Telematics TSI point
|
Mandatory standard point
|
|
[B.5]
|
ERA/TD/2009-07/INT – Version 1
Electronic reservation of seats/berths and electronic production of travel documents – Exchange of messages
|
|
|
Availability and reservation request
|
4.5.2(1)
|
|
|
|
Availability and reservation response
|
4.5.3(1)
|
|
|
|
Dossier reference
|
4.6.2(1)
|
|
|
[B.10]
|
ERA/TD/2010-01/INT – Version 1 of xx.xx.2025
Electronic reservation of assistance for persons with reduced mobility – Exchange of messages
|
|
|
Availability of and reservation for PRM assistance
|
4.5.4(1)
|
|
|
[B.11]
|
ERA-REC-122/TD/01 – Version 2
Layout for electronically issued rail passenger tickets
|
|
|
Tariff data necessary for authorised distributors and issuers to issue tickets
|
4.3.1(2)(e)
|
|
|
|
Electronically issued rail passenger tickets
|
4.6.3.1(1)
|
|
|
|
Direct fulfilment methods
|
|
|
Cross-border and international tickets type
|
4.6.3.2(1)(a)
|
|
|
|
Cross-border and international tickets format
|
4.6.3.2(1)(b)
|
|
|
|
Domestic tickets format
|
4.6.3.2(2)
|
|
|
|
Indirect fulfilment methods
|
|
|
Cross-border and international tickets type
|
4.6.3.3(1)(a)
|
|
|
|
Cross-border and international tickets format
|
4.6.3.3(1)(b)
|
|
|
|
Domestic tickets format
|
4.6.3.3(2)
|
|
|
[B.12]
|
ERA-REC-122/TD/02 – Version 2
Digital security elements for rail ticketing
|
|
|
Tariff data necessary for authorised distributors and issuers to issue tickets
|
4.3.1(2)(e)
|
|
|
|
Security elements for electronic delivery
|
4.6.1(1)
|
|
|
|
Compliance assessment testing procedure for bar code
|
Appendix D.3.E
|
|
|
[B.xx]
|
ERA/TD/xxx –Version 1
European Fares Information Profile
|
|
|
Fares data sharing for rail passenger transport services
|
4.3.1(1)
|
|
|
|
Fares data sharing with other modes of transport
|
4.9
|
|
|
[B.14]
|
ERA/TD/xxx –Version 1
e-Ticket Exchange for Control
|
|
|
Ticket annotation
|
4.6.4.1
|
|
|
[B.15]
|
ERA/TD/xxx –Version 1
European Passenger Information Railway Station Accessibility Profile
|
|
|
Condition of access to the station
|
4.4.3.2(1)
|
|
|
[B.yy]
|
ERA/TD/xxx –Version 1
Testing procedure for timetable data
|
|
|
Compliance assessment testing procedure for passenger timetable data
|
Appendix D.3.A
|
|
APPENDIX D
TESTING PROCEDURES FOR COMPLIANCE ASSESSMENT
D.1Testing procedures for telematics applications
(1)Deployment in production of telematics applications by telematics stakeholders for the implementation of this Regulation shall be subject to an assessment of the compliance of the data shared against the requirements laid down in the Regulation. Self-assessment performed by telematics stakeholders and notified to the Agency in accordance with Article 18 shall be accompanied by the following use-case documentation:
(a)functions covered and reference to corresponding points of this Regulation;
(b)a list and documentation of messages (including their sequence) tested against the specifications referenced in the Regulation, and corresponding automated evidence-based declaration of compliance as referred to in point D.2;
(c)a description of the telematics applications using telematics messages as referred to in the Regulation;
(d)a description of the communication interface of the telematics applications used and to be assessed against the requirements for application programming interface laid down in point 1.7;
(e)the version of the specifications referenced in Appendix C, as implemented and subject to compliance assessment;
(f)RDF files of the telematics applications and their corresponding RDF SHACL files.
(2)Where the Agency checks the correctness of the automated evidence-based declaration of compliance resulting from self-testing, it shall, within 3 months of confirming completeness of the information submitted as listed in point (2), report its opinion on whether the telematics application deployed complies with this TSI. Its report shall cover at least the following aspects:
(a)compliance of all mandatory elements contained in the messages;
(b)compliance of the messages themselves;
(c)compliance of the sequence of messages.
(3)For the purpose of point (1)(f), applicants may submit XML files to the Agency to determine whether corresponding messages carry the mandatory elements laid down in this Regulation. In such cases, the applicant shall submit to the Agency the description of the message structure and associated data elements and fields as well as the XSD files used.
(4)For requests submitted to the Agency for correctness checks of the automated evidence-based declaration of compliance resulting from self-testing in accordance with Article 18(4), the use-case document referred to in subpoint (1) of this point shall also include background information and a timeline of the project to be assessed.
(5)Where an existing compliance assessment is to be renewed in accordance with Article 18(6), the application for compliance assessment submitted to the Agency pursuant to point (1) shall be limited to the elements affected by the changes to be assessed. Such applications shall also include a reference to the previous compliance assessment reports delivered by the Agency in relation to the telematics applications for which a new assessment is requested.
D.2Evidence-based declaration for individual IT messages
(1)To facilitate the testing of messages referred to in point D.1(1)(b) and their sequence, telematics stakeholders shall self-assess the compliance of individual messages deployed and used for the purposes of implementing this Regulation.
(2)The Agency shall make available a web application for assessing message compliance where telematics stakeholders are to submit relevant files in accordance with points D.1(1)(f) and D.1(2) for automated testing against the specifications referenced in Appendix C, index [2].
(3)After submission, the web application referred to in point (2) shall issue an automated acknowledgment of receipt and compliance assessment result to be used by the submitting telematics stakeholder as an evidence-based declaration of compliance for the messages or sequence of messages tested.
D.3Specific testing procedures for rail ticketing
D.3.APassenger timetable
Testing procedures for assessment of compliance against the requirements laid down in point 4.2 of this Annex shall be in accordance with the specifications referenced in Appendix C, index [B.yy].
D.3.BTariffs
(1)Testing procedures for assessment of compliance against the requirements laid down in point 4.3 of this Annex are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
(2)Pending the development of relevant testing procedures pursuant to Article 23, point (c), automatic converters and validators based on an open architecture may be used by telematics stakeholders to self-assess the compatibility and interoperability of the data shared and the processes implemented against the specifications set out in point 4.3.
D.3.CAvailability check and reservation
(1)Testing procedures for assessment of compliance against the requirements laid down in point 4.5 of this Annex are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed accordingly in Appendix B to this Annex.
(2)Pending the development of relevant testing procedures pursuant to Article 23, point (c), automatic validators based on an open architecture may be used by telematics stakeholders to self-assess the compatibility and interoperability of the data shared and the processes implemented against the specifications set out in point 4.5.
D.3.EBarcodes
Testing procedures for assessment of compliance against the requirements for indirect fulfilment methods laid down in point 4.6.3.3 shall be in line with the specification referenced in Appendix C, index [B.12].
APPENDIX E
ACCURACY OF FORECAST INFORMATION FOR TRAIN AND WAGON MOVEMENTS
(1)Since the train forecast information referred to in point 2.6.4 and the wagon forecast information referred to in point 3.2.3 refer to the predicted time of arrival of a train and of a wagon and its loading, respectively, at an agreed reporting point, it will be used by stakeholders and customers involved in the transport service to plan subsequent operations or onward connections.
(2)Since both the train forecast information referred to in point 2.6.4 and the wagon forecast information referred to in point 3.2.3 are an estimate that derive from the time originally planned in the working timetable +/- the deviation from the working timetable that occurred during the train service, the originator of such a forecast shall perform the following:
(a)carry out an ex post measurement of the accuracy of its forecast in accordance with Article 10 in order to create confidence in the data to be reused by the recipient for the planning of subsequent operation;
(b)ensure that the recipient of the forecast referred to in point (a) is informed of the expected accuracy of the forecast based on earlier train runs.
(3)As an alternative to linear time-shifting methods commonly applied by some telematics stakeholders for the purposes of point (2)(a), others may apply different methods or use internal algorithm-based machine learning methods that may be integrated into an artificial intelligence to achieve more accurate and intelligent insights.
(4)For the purpose of point (2), recurrent quality assurance checks on the accuracy of forecast information are laid down as follows:
(a)absolute error:
The ‘absolute error’ is calculated as the absolute value of the difference between the actual date and time of arrival at a specified reporting point and the forecast date and time of arrival at that reporting point;
(b)relative error:
To put the ‘absolute error’ at a specified reporting point in perspective with the duration of the remaining train journey, a ‘relative error’ is calculated as the ratio or percentage obtained by dividing the ‘absolute error’ by the ‘duration of the remaining train journey’;
The ‘duration of the remaining train journey’ is calculated as the difference between the actual date and time of the arrival of a train at the reporting point and the time when the corresponding forecast information has been provided;
(c)accuracy:
The recurrent quality assurance checks on the ‘accuracy’ are calculated as the complement of the ‘relative error’ to 100%.
(5)Where a data holder, that is to say the originator of the data, performs recurrent quality assurance checks as referred to in point (3), it shall assess the accuracy of the data as a stochastic probability of the statistical values of the forecast information at a specified reporting point for a group composed of previous services.
(6)A data holder shall perform quality assurance checks on the accuracy of train forecast information only once that train has arrived to, or after that wagon and its loading have been handed over or delivered at, the reporting point subject to the forecast. Quality assurance checks shall hence be based only on historical data.
(7)Indicators resulting from measurements defined in point (3) shall be available through the common Union web UI referred to in Article 5.
APPENDIX F
ESSENTIAL REQUIREMENTS
|
TelematicsTSI point
|
Element of the telematics subsystem
|
Essential requirements as referred to in Annex III to Directive (EU) 2016/797
|
|
|
|
Safety
|
Reliability and availability
|
Health
|
Environmental protection
|
Technical compatibility
|
Accessibility
|
|
1.2
|
Common reference files
|
|
X
|
|
|
X
|
|
|
1.3
|
Security
|
|
X
|
|
|
X
|
|
|
1.4
|
Data presentation
|
|
|
|
|
X
|
|
|
1.5
|
Data quality
|
|
X
|
|
|
X
|
|
|
1.7
|
APIs
|
|
X
|
|
|
X
|
|
|
|
Web UIs
|
|
X
|
X
|
|
X
|
X
|
|
2.1
|
Object identifiers
|
|
|
|
|
X
|
|
|
2.2
|
Strategic management of infrastructure capacity
|
|
x
|
|
X
|
X
|
|
|
2.3
|
Capacity allocation
|
|
X
|
|
X
|
X
|
|
|
2.4
|
Capacity restrictions
|
|
x
|
|
X
|
x
|
|
|
2.5.1
|
Train composition
|
|
X
|
|
X
|
X
|
|
|
2.5.2
|
Train ready
|
|
X
|
|
|
X
|
|
|
2.6
|
Train traffic data
|
|
X
|
|
|
X
|
|
|
3.1.1
|
Consignment note
|
|
|
|
|
X
|
|
|
3.2
|
Movements of freight wagons and their loading
|
|
X
|
|
|
X
|
|
|
3.3
|
Freight-specific reference files
|
|
X
|
|
X
|
X
|
|
|
4.2
|
Passenger timetable data
|
|
|
|
|
X
|
X
|
|
4.3
|
Tariff data
|
|
|
|
|
X
|
|
|
4.4
|
Conditions of carriage
|
|
|
|
|
X
|
X
|
|
4.5
|
Availability and reservation
|
|
|
|
|
X
|
X
|
|
4.6
|
Security elements for product distribution
|
|
X
|
|
|
X
|
|
|
4.7
|
Passenger travel information during the train journey
|
|
|
X
|
|
X
|
X
|
|
4.8
|
Common reference data for rail ticketing
|
|
X
|
|
|
X
|
|
APPENDIX G
IMPLEMENTATION MILESTONES
(1)The subsystem shall be considered to have been deployed by a telematics stakeholder in accordance with this Regulation when the data sharing requirements and messages have been fully implemented in accordance with the specifications set out in this Annex and when corresponding telematics applications used for data sharing have been declared as compliant with this Regulation pursuant to Article 18 and point 1.6 of this Annex and are fully operational (first day of operation).
(2)To fulfil the deadlines laid down in Article 16(2), (3) and (4), each telematics stakeholder shall deploy the telematics subsystem in accordance with the milestones set out in the following table:
|
Functions
|
Basic parameters
|
Milestone
|
|
Capacity management
|
2.1 – Object identifiers
|
[1.3.2026]
|
|
|
2.3 – Capacity allocation
2.4.4 – Changes of infrastructure characteristics due to capacity restrictions
|
[1.3.2026]
[1.3.2026]
|
|
Train preparation
|
2.5.1 – Train composition
·freight train composition
·passenger train composition
Error! Reference source not found.
|
[13.12.2026]
[13.12.2026]
|
|
|
2.5.2 – Train ready
|
[13.12.2026]
|
|
Traffic management
|
2.6 – Train traffic data
|
[13.12.2026]
|
|
Management of freight wagons and their loading
|
3.1.1 – Consignment note
|
[13.12.2026]
|
|
|
|
|
|
|
3.2.1 – Wagon running information
|
[13.12.2026]
|
|
|
3.2.3 – Wagon forecast information
|
[13.12.2026]
|
|
Reference files and databases
|
1.2 – Common reference files
·organisations
·locations
|
[14.12.2025]
|
|
|
3.3.2 – Rolling stock reference data bases
|
[14.12.2025]
|
|
|
3.3.3 – Intermodal loading unit reference databases
|
[14.12.2025]
|
|
|
4.8 – Common reference data for rail ticketing
|
[14.12.2025]
|
|
Rail ticketing of passenger rail services
|
4.2 – Passenger timetable data
|
[14.12.2025]
|
|
|
4.3 – Tariff data
|
|
|
|
4.4 – Conditions of carriage
|
|
|
|
4.5 – Availability and reservations
|
|
|
|
4.6 – Security elements for product distribution
|
|
|
|
4.8 – Common reference data for rail ticketing
|
|
|
Passenger travel information
|
4.7 – Passenger travel information during the train journey
|
[13.12.2026]
|