Commission Implementing Regulation (EU) 2026/253 of 6 February 2026 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 (TEL TSI) and repealing Regulations (EU) No 454/2011 (TAP TSI) and (EU) No 1305/2014 (TAF TSI)

• (3) Where an alternative to a path that is no longer available or has been changed is available, each infrastructure manager responsible for the path allocated, or part of it, shall offer that alternative and send to the applicant a ‘PathDetailsMessage’ in accordance with point 2.3.3, which shall be read alongside the ‘PathNotAvailableMessage’ referred to in point (2). In such cases, the following conditions shall also apply:

• (a) where such an alternative is offered, the applicant is not required to send a ‘PathRequestMessage’ under point 2.3.2;

• (b) where such an alternative is not available, each infrastructure manager responsible for the path allocated, or part of it, shall immediately send the applicant a ‘PathNotAvailableMessage’.

2.3.8.   Receipt confirmation

• (1) The ‘ReceiptConfirmationMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (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 ‘ReceiptConfirmationMessage’ to the telematics stakeholder which sent the original message.

2.3.9.   Capacity allocation coordination process

Aspects relating to the interoperability of data for 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 in Appendix B to this Annex.

2.3.10.   Working timetable

Each infrastructure manager 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-ND 4.0 licence or any other equivalent or less restrictive open licence or any other equivalent or less restrictive access conditions mutually agreed upon by the involved stakeholders.

2.4.   Planned capacity restrictions

2.4.1.   Coordination of planned capacity restrictions

Aspects relating to the interoperability of data sharing for to the coordination of planned capacity restrictions are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed in Appendix B to this Annex.

2.4.2.   Consultation of stakeholders affected by planned capacity restrictions

Aspects relating to the interoperability of data sharing for 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 in Appendix B to this Annex.

2.4.3.   Publication of planned capacity restrictions

Aspects relating to the interoperability of data sharing for the publication of 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 in Appendix B to this Annex.

2.4.4.   Temporary changes to the nominal infrastructure characteristics resulting from a planned capacity restriction

The publication of temporary changes of nominal infrastructure characteristics through temporary values of the network parameters in the RINF pursuant to OPE TSI, as referred to in Appendix A to this Annex, may be automated through a common European API used to share data relating to temporary capacity restrictions in accordance with points 2.4.1, 2.4.2, and 2.4.3.

2.5.   Train preparation

2.5.1.   Train composition

• (1) The ‘TrainCompositionMessage’ for freight rail transport services and the ‘PassengerTrainCompositionMessage’ for passenger rail transport services, referred hereafter as ‘train composition messages’, shall be in accordance with the specifications referenced in Appendix C, index [1].

• (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 manager responsible for the network of departure solely in relation to the sections of the path where the train is to run.

• (3) In the case of an intermodal transport service, the freight railway undertaking responsible for the operation of a train that is part of a path arriving at a rail freight service facility where the composed train is to be unloaded shall send a ‘TrainCompositionMessage’ to the operator of that rail freight service facility.

• (4) Each infrastructure manager, solely in relation to the sections of the rail transport service operated on its network according to a path, shall grant access pursuant to Articles 4 and 5 to train composition data it receives.

• (5) Where an infrastructure manager grants access to train composition data pursuant to Articles 4 and 5, it shall consistently reuse the information contained in ‘train composition messages’ received from railway undertakings pursuant to point (2) of that point and from station managers pursuant to point 4.7.1.1(3), and grant access to that data for use under the conditions of the Creative Commons BY-NC-ND 4.0 licence or any other equivalent or less restrictive open licence or any other equivalent or less restrictive access conditions mutually agreed upon by the involved stakeholders.

• (6) Where a railway undertaking shares train composition data with an infrastructure manager or an operator of rail freight service facilities in accordance with points (2) or (3), 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 sharing that data pursuant to Article 5 and point 2.5.1(5).

• (7) Where access to train composition data is restricted from the public pursuant to Article 5, paragraphs (3) or (4), each infrastructure manager shall ensure that other telematics stakeholders can access that data pursuant to Article 4 through the common Union web UI referred in Article 5(1).

• (8) In the cases referred to in Article 5(6), train composition data shall only be sent bilaterally by the railway undertaking to relevant telematics stakeholders pursuant to Article 4.

• (9) 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.

• (10) 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 shall send a new ‘train composition message’ or communicates the new train composition in accordance with Appendix C to the OPE TSI.

• (11) The ‘TrainCompositionMessage’ shall contain parameters providing for compliance of the composition of the train with the specific rules for the operation of freight 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 specified in point 2.3.

• (12) The ‘TrainCompositionMessage’ shall make it possible to identify any intermodal loading unit loaded on freight wagons.

• (13) The ‘TrainCompositionMessage’ shall make it possible to identify freight wagons transporting dangerous goods. Where at least one freight wagon is part of a train that transports dangerous goods, the access to the train composition data shall be restricted from the public pursuant to Article 5(3) for this entire train.

• (14) The ‘train composition message’ shall allow to identify where a rail transport service is operated for the armed forces, if relevant.

• (15) The ‘PassengerTrainCompositionMessage’ shall include seating maps, at least for trains where it is possible to reserve a seat, and the location of on-board facilities such as classes, coaches accessible to PRM and bike spaces, where available.

The ‘PassengerTrainCompositionMessage’ shall constitute an appropriate format and technical means respectively within the meaning of Articles 9(3) and 10(4) of Regulation (EU) 2021/782 to grant digital access to information related to on-board services and facilities as part of information during the journey referred to in the Part II of Annex II to that Regulation and meeting corresponding obligations under Articles 9(2) and 10(5) of that Regulation.

• (16) The ‘train composition messages’ shall include the information required to support the energy settlement process pursuant to Regulation (EU) No 1301/2014 (‘ENE TSI’), as referred to in Appendix A. It shall include in particular the European vehicle number of the traction units that is part of that train and that is referred to as consumption point id of the on-board energy measurement systems pursuant to Regulation (EU) No 1302/2014 (‘Loc&Pas TSI’), as referred to in Appendix A, and the total mass of the train. This information shall be part of the train composition message at departure time pursuant to paragraph (2), or at the latest 48 hours after departure in case of anomaly. The infrastructure manager shall share that data with relevant energy settlement systems pursuant to ENE TSI.

• (17) Where the recipient of a ‘train composition message’ use the data contained in that message for the safety of operations in accordance with point 1.1, paragraphs (2) and (3), or where agreed with the data holder of that message, the recipient shall acknowledge its reception by sending a ‘ReceiptConfirmationMessage’ in accordance with the specifications referenced in Appendix C, index [1], to the original sender.

2.5.2.   Train ready

• (1) Where a railway undertaking responsible for the movement of a train is ready to timely access the network in accordance with the working timetable and associated allocated path, including when this path has been modified by the infrastructure manager upon request of this railway undertaking pursuant to point 2.3.1(8), the obligations laid down in this point shall be deemed to have been fulfilled.

• (2) Where either Railway Mobile Radio (RMR) systems or ‘Start of mission’ procedure in ETCS L2 in accordance with the Annex to 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 through its network statement, the obligations laid down in point 2.5.2 shall be deemed to have been fulfilled.

• (3) Where either Railway Mobile Radio (RMR) systems or ‘Start of mission’ procedure in ETCS L2 in accordance with the Annex to the CCS TSI, as referred to in Appendix A, are notified by the infrastructure manager responsible for the network of departure through the RINF as functions to be rolled out within 5 years after the milestone set out in Appendix G, alternatives means to the obligations laid down in points (6), (7) and (8) may be mandated for use by the infrastructure manager responsible for the network of departure through its network statement.

• (4) Where a railway undertaking responsible for the movement of a train is ready to access the network following a delay compared to the working timetable and associated allocated path, it shall inform the infrastructure manager responsible for the network of departure in accordance with points (6), (7) and (8).

• (5) Where a railway undertaking responsible for the movement of a train is ready to access the network in advance of the working timetable and associated allocated path, it may inform the infrastructure manager responsible for the network of departure in accordance with points (6), (7) and (8).

• (6) The ‘TrainReadyMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (7) Where a railway undertaking responsible for the movement of a train is to inform the infrastructure manager 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 ‘TrainReadyMessage’ before departure to the infrastructure manager responsible for the network of departure.

• (8) Where the infrastructure manager receiving a ‘TrainReadyMessage’ pursuant to paragraph (4) uses the data contained in that message for the safety of operations in accordance with point 1.1, paragraph (3), or for energy settlement purposes, or where agreed with the sending undertaking, the infrastructure manager shall acknowledge receipt.

2.5.3.   Train readiness forecast

• (1) Where a railway undertaking is not ready to start a train according to the working timetable or its allocated path, including when this path has been modified by the infrastructure manager upon request of this railway undertaking pursuant to point 2.3.1(8), or is delayed due to any anomaly affecting that train or its operation having possible repercussions on the train’s running prior to departure, it shall, in order to provide forecast information about its readiness to access the network, send to the infrastructure manager responsible for the network of departure a ‘TrainReadyMessage’ bearing the status ‘NotReady’, including:

• (a) an estimate of how long the delay will last via the elements ‘TrainDelay’ and ‘TrainReadyTime’;

• (b) an assessment of its cause via the element ‘DelayCause’

• (2) A new ‘TrainReadyMessage’ shall be sent as soon as new or updated information is available.

• (3) Where the infrastructure manager receiving a ‘TrainReadyMessage’ pursuant to paragraph (1) uses it for the safety of operations in accordance with point 1.1, paragraph (3), or where agreed with the sending undertaking, the infrastructure manager 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, referred to hereafter as ‘train traffic messages’, shall be in accordance with the specifications referenced in Appendix C, index [1]:

• (a) the ‘TrainRunningInformationMessage’ specified in point 2.6.3;

• (b) the ‘TrainRunningForecastMessage’ specified in point 2.6.4;

• (c) the ‘TrainDelayCauseMessage’ specified in point 2.6.5;

• (d) the ‘TrainRunningInterruptionMessage’ specified in point 2.6.6.

• (3) Infrastructure managers and operators of rail freight 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 Articles 4 and 5 to train traffic data based on the information contained in ‘train traffic messages’;

• (b) unless not required by and bilaterally agreed with a railway undertaking, shall send ‘train traffic messages’ to railway undertakings in relation to the rail transport services they operate;

• (c) shall send ‘train traffic messages’ to other infrastructure managers in accordance with Article 4 in the case of a rail transport service subject to multi-network processes;

• (d) may send ‘train traffic messages’ to other telematics stakeholders in accordance with Article 4, upon request of that stakeholder and where bilaterally agreed as a service.

In the cases referred to in Article 5(5), the subpoint (a) of this point shall not apply and subpoint (b) of this point shall be mandatory to apply.

• (4) Where an infrastructure manager or an operator of rail freight service facilities grants access to train traffic data pursuant to Article 5, it shall consistently reuse 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 equivalent or less restrictive open licence or any other equivalent or less restrictive access conditions mutually agreed upon by the involved stakeholders.

• (5) Where the shunting and stabling of freight wagons is performed as single wagonload transport in a rail freight service facility, train traffic data shall be shared pursuant to Articles 4 and in accordance with point 3.2.1.

• (6) Where freight wagons are operated as a block train in a rail freight service facility, the operator of that facility shall share train traffic data pursuant to Articles 4 and 5 based on ‘train traffic messages’ referred in point (2). For that purpose, a reference to the identifier of that train for the associated path departing from that facility shall be used. Where that facility is the final destination of that block train, the identifier of that train for the associated path arriving to that facility shall be used.

• (7) ‘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.

• (8) 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 consistently reuse 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 freight service facilities, and the railway undertaking or the intermodal transport operator in relation to a train:

• (a) departure points;

• (b) points where responsibility for capacity management or traffic management changes between consecutive infrastructure managers or allocation bodies, or between infrastructure managers and operators of rail freight service facilities (‘point of handover’);

• (c) points where responsibility for the operation of a train changes between consecutive railway undertakings, intermodal transport operators, or any combination between them (‘point of interchange’);

• (d) points where the train arrives at and departs from rail passenger stations and rail freight service facilities and any other intermediary stops scheduled;

• (e) destination points.

2.6.3.   Train running information

• (1) The ‘TrainRunningInformationMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (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 freight service facilities shall send a ‘TrainRunningInformationMessage’ upon departure from and arrival of a train at reporting points.

2.6.4.   Train forecast information

• (1) The ‘TrainRunningForecastMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (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 freight service facilities shall send a ‘TrainRunningForecastMessage’.

• (3) For delays at departure point or additional delays between two reporting points that are estimated to last more than 15 minutes for freight trains or more than 5 minutes for passenger trains, or as otherwise required by the performance monitoring regime pursuant to OPE TSI, as referred to in Appendix A, a new ‘TrainRunningForecastMessage’ shall be sent.

• (4) ‘TrainRunningForecastMessage’ shall make it possible to gauge, ex post, the accuracy of the estimate made by means of this forecast and shall include its expected accuracy in accordance with the methodology set out in Appendix E.

2.6.5.   Train delay cause

• (1) The ‘TrainDelayCauseMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) As soon as the cause of delay is known, including in the case of a first assumption, and where there is an update on the cause of delay, the infrastructure manager or the operator of rail freight service facilities shall send a ‘TrainDelay CauseMessage’ 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 ‘TrainRunningInterruptionMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (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 freight service facilities shall send the following messages:

• (a) where the length of the delay is not known: a ‘TrainRunningInterruptionMessage;

• (b) where the length of the delay is known:

• (i) a ‘TrainRunningForecastMessage’ in accordance with point 2.6.4;

• (ii) a ‘TrainDelayCauseMessage’ 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 freight service facilities responsible for the network where the service disruption occurred. Where relevant, the receiving infrastructure manager or operator of rail freight service facilities shall send updated information in accordance with point 2.6.1.

2.6.7.   Path modification in operation

• (1) In the event of modifications to a path beyond the threshold referred to in point 2.3.1(8), the infrastructure managers or operators of rail freight service facilities responsible for this path shall notify the railway undertakings concerned about the intended modifications of that path on their respective network.

• (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 in Appendix B.

• (3) If the agreed continuation of a passenger rail transport service involves the rerouting via a different route, its partial cancellation, or the removal or addition of intermediate stops, the infrastructure manager responsible for that rail transport service shall send a ‘PathDetailsMessage’, as referred to in point 2.3.3, containing information relating to the path section modification in accordance with point 2.6.1.

2.7.   Historic record of train related data

To record data pertaining to the running of both passenger and freight trains pursuant to OPE TSI, as referred to in Appendix A, after train arrival at destination, each infrastructure manager and each operator of rail freight service facilities shall grant access to an historic record of the following data pursuant to Articles 4 and 5 via a common Union web user interface (‘web UI’), at the latest from 24 hours and for at least 12 months:

• (a) working timetable, as referred to in point 2.3.10

• (b) reference train identifier as referred to in point 2.1.2;

• (c) for passenger trains only: passenger train identification number of the train as the ‘RetailServiceId’ in combination with the reference train identifier referred to in point 2.1.2;

• (d) reporting locations and associated train status, as part of train running information referred to in point 2.6.3;

• (e) actual running date and time, as part of train running information referred to in point 2.6.3;

• (f) delay and cause of delay, if any, as part of train running information and train delay cause information referred to in points 2.6.3 and 2.6.5 respectively;

• (g) train composition, as referred to in point 2.5.1, that for freight rail transport services shall be limited to:

• (i) the European vehicle number of all vehicles in the train;

• (ii) the position of all vehicles in the train;

• (iii) in the case of intermodal transport, the type of the intermodal loading units and their identifier.

2.8.   Data sharing with other stakeholders

Infrastructure managers, operators of rail freight service facilities and railway undertakings shall share data in accordance with Article 4 and the requirements laid down in Section 2 of this Annex with other telematics stakeholders responsible for managing connections with other modes of transport.

3. MANAGEMENT OF FREIGHT WAGONS AND THEIR LOAD

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 (‘eCN’)

• (1) The ‘ConsignmentNoteMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) A consignment note exchanged electronically by means of a ‘ConsignmentNoteMessage’ signed using means that comply with the requirements for qualified electronic seals in accordance with Regulation (EU) No 910/2014 of the European Parliament and of the Council [^ntr4-L_202600253EN.002801-E0004] shall be considered as an electronic record of data, that is an electronic consignment note (‘eCN’), equivalent to a paper-based consignment note.

• (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 ‘ConsignmentNoteMessage’ to all railway undertakings involved in the rail transport service,

• (b) the lead railway undertaking may share the information contained in the ‘ConsignmentNoteMessage’ 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, it shall consistently reuse the data contained in the ‘ConsignmentNoteMessage’ referred to in this point, and where relevant in the ‘TrainCompositionMessage’ referred to in point 2.5.1.

3.1.2.   Reservation, payment and invoicing systems for freight rail transport services

Aspects relating to the interoperability of data sharing and associated systems for the reservation, payment and invoicing of freight rail transport services, including services based on intermodal oriented timetable integrating buffer times and milestones in multi-modal freight terminals, are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed in Appendix B.

3.2.   Movements of freight wagons and their load

• (1) Railway undertakings involved in the same freight rail transport service operated as single wagonload transport shall mutually exchange information and individually ensure the monitoring of the location and status of the freight wagons, or set of freight wagons, for which they are responsible for the data relating to the movements of freight wagons and their load 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 freight wagons or set of freight wagons, and their load, using the information provided by the railway undertakings involved in the same freight rail transport service operated as single wagonload transport.

• (3) The current location and status of the load, intermodal loading units in particular, shall be monitored based on the location and status of the freight wagons onto which the load is positioned.

• (4) Freight railway undertakings may contribute to the development of common Union web UIs referred to in Article 14(6) and Article 21 for granting access to data relating to the movements of freight wagons and their load. Where a group of freight railway undertakings jointly provide for use such common Union web UIs, that application shall grant access to data relating to the movements of freight wagons and their load to relevant telematics stakeholders pursuant to Article 4 and for use of that data under the conditions of the Creative Commons BY-NC-SA 4.0 licence or any other equivalent or less restrictive open licence or any other equivalent or less restrictive access conditions mutually agreed upon by the involved stakeholders.

3.2.1.   Wagon running information

3.2.1.1.   Geo-localisation of freight wagons

• (1) Where geo-localisation devices are fitted on freight wagons, the data holder of geo-localisation based positioning data shall grant access to that data to other telematics stakeholders using these freight wagons, or where relevant other telematics stakeholders, pursuant to Article 4.

• (2) Aspects relating to the interoperability of data sharing in relation to the geo-localisation-based positioning of freight wagons are identified as an ‘open point’ in accordance with Article 4(6) of Directive (EU) 2016/797 and are listed in Appendix B to this Annex.

3.2.1.2.   Wagon status

• (1) The ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) For telematics stakeholders involved in a freight rail transport service operated as single wagonload transport to have continuous knowledge of the current location and status of freight wagons:

• (a) the railway undertaking responsible for the movement of a freight wagon or set of freight wagons shall send a ‘WagonStatusMessage’ to the lead railway undertaking;

• (b) the lead railway undertaking shall send a ‘WagonStatusMessage’, upon request, to other relevant telematics stakeholders pursuant to Article 4, in particular to the other railway undertakings involved in that freight rail transport service operated as single wagonload transport.

• (3) Where a telematics stakeholder sends a ‘WagonStatusMessage’, it shall specify to which event type that message relates to in accordance with points 3.2.1.3 to 3.2.1.13.

• (4) Unless a common wagon and intermodal loading unit operation database in accordance with point 3.3.3 is available, or common Union web UIs referred in point 1.7.2 have been used, ‘WagonStatusMessage’ shall be exchanged bilaterally pursuant to Article 4 via a telematics application referred to in Article 14 and point 1.7.

• (5) To have continuous knowledge of the current location and status of freight wagons in a freight rail transport service not operated as single wagonload transport, telematics stakeholders involved in that transport service may voluntarily apply the requirements set out in points 3.2.1.2 to 3.2.1.13 based on contractual provisions.

3.2.1.3.   Wagon ready for movement

• (1) The event type ‘Wagon Ready To Pull’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where the loader or where relevant the filler of a freight 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 the role of the railway undertaking as referred to in the Article 4 of Directive (EU) 2016/798, and therefore that the freight 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 ‘WagonStatusMessage’, with the event type ‘Wagon Ready To Pull’ in accordance with point 3.2.1.2 (2) of this Annex, to the outbound railway undertaking expected to pull or push that freight wagon from this location.

• (3) In the case of intermodal transport, where an operator of rail freight service facilities is responsible for loading or unloading a set of freight wagons, it shall send to the lead railway undertaking a ‘TrainRunningInformationMessage’ referred to in point 2.6.1, subpoint (6), and in point 2.6.3, containing the location and status of the train, and confirming the train closure, that is to say that the loaded or unloaded set of freight wagons parked at the reporting point is ready for movement without jeopardising the safety of the load in accordance with OPE TSI.

• (4) 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 freight wagon that is part of a single wagonload transport, 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 in Appendix B to this Annex.

3.2.1.4.   Wagon pulled

• (1) The event type ‘Wagon Pulled’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where a freight wagon has been pulled or pushed from a specified loading or unloading location, the outbound railway undertaking responsible for that freight wagon shall send a ‘WagonStatusMessage’ 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’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where a freight wagon has left with a train a rail freight service facility of origin, the outbound railway undertaking responsible for that train shall send a ‘WagonStatusMessage’ 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’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where a freight wagon arrived at a specified intermediate location with a train, the railway undertaking of arrival responsible for that train shall send a ‘WagonStatusMessage’ 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’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where a freight wagon left a specified intermediate location with a train, the outbound railway undertaking responsible for that train shall send a ‘WagonStatusMessage’ 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’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where the responsibility for a freight wagon’s movement has changed between successive railway undertakings and where the freight wagon has been physically handed over by the railway undertaking of arrival to the next undertaking at a specified point of interchange, the railway undertaking of arrival shall send a ‘WagonStatusMessage’ 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’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where the responsibility for a freight wagon’s movement has changed between successive undertakings and where the freight wagon has been physically taken over by the railway undertaking of departure from the previous railway undertaking at a specified point of interchange, the railway undertaking of departure shall send a ‘WagonStatusMessage’ with the event type ‘Wagon Taken Over’, in accordance with point 3.2.1.2(2).

3.2.1.10.   Wagon irregularity

• (1) The event type ‘WagonJourneyIrregularity’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where an irregular event relating to the freight wagon or its load requires an action to be taken that may interrupt its transportation, the railway undertaking responsible for that freight wagon shall send a ‘WagonStatusMessage’ with the event type ‘WagonJourneyIrregularity’, 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 irregularity rectified

• (1) The event type ‘Wagon Journey Rectified’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where a freight wagon journey irregularity has been rectified, the railway undertaking responsible for that freight wagon shall send a ‘WagonStatusMessage’ 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’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where a freight wagon arrived with a train at a rail freight service facility of destination, the railway undertaking of arrival responsible for that train shall send a ‘WagonStatusMessage’ 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’ of the ‘WagonStatusMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) Where a freight wagon has been delivered to the loading or unloading location, the railway undertaking of arrival responsible for this freight wagon or set of freight wagons shall send a ‘WagonStatusMessage’ 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 in Appendix B to this Annex.

3.2.3.   Wagon forecast information

• (1) The wagon forecast message (‘WagonETI_ETAMessage’) shall be in accordance with the specifications referenced in Appendix C, index [1].

• (2) To provide other telematics stakeholders involved in a rail transport service operated as single wagonload transport with wagon forecast information, either confirming agreed timings or notifying any changes, each railway undertaking shall send, as part of the ‘WagonETI_ETAMessage’, the wagon forecast information at destination (‘ETA’) or the wagon forecast information at point of interchange (‘ETI’) to:

• (a) the lead railway undertaking;

• (b) the next railway undertaking, if any, to which the freight wagon will be handed over at point of interchange.

• (3) Each railway undertaking, shall monitor the physical transport of a load and, no later than the time of departure from the origin, or from the last point of interchange, shall calculate wagon forecast information relating to the following event types and reporting points:

• (a) at the next point of interchange: ‘wagon handed over’ specified in point 3.2.1.8;

• (b) at destination: ‘wagon delivered’ specified in point 3.2.1.13.

• (4) Each railways undertaking 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 freight service facilities:

• (i) the ‘PathDetailsMessage’ specified in point 2.3.3;

• (ii) the ‘TrainRunningInformationMessage’ specified in point 2.6.3;

• (iii) the ‘TrainRunningForecastMessage’ specified in point 2.6.4;

• (b) the information (‘ETA’ or ‘ETI’) contained in ‘WagonETI_ETAMessage’ received from the previous railway undertaking, if any, from which freight wagons were taken over at a point of interchange.

• (5) Where a railway undertaking shares or grants access to wagon forecast information, it shall ensure that the quality of this information 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.

• (6) The lead railway undertaking shall compare the wagon forecast information (‘ETA’) based on ‘WagonETI_ETAMessage’ received from a railway undertaking with the timings agreed with the freight customers (‘ArrivalTimeAtLocation’), and inform the railway undertakings involved.

3.3.   Freight-specific reference data

3.3.1.   General

• (1) To support train preparation in accordance with point 2.5 and freight wagon operation in accordance with point 3.2.1, each vehicle keeper shall ensure rolling stock reference data sharing through standardised and federated rolling stock reference databases as referred to in point 3.3.2.

• (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 standardised and federated ILU reference databases as referred to in point 3.3.3;

• (b) each keeper of freight wagons and each keeper of ILUs may ensure data sharing of the operational status of their freight wagons and ILUs through the standardised and federated freight wagon and ILU operation databases, respectively, as referred to in point 3.3.4.

• (3) Telematics stakeholders responsible for freight-specific reference data pursuant to points (1) and (2) shall manage their reference data in accordance with Articles 8(4) and 10 and grant access to them for use under the conditions of the Creative Commons BY-ND 4.0 licence or any other equivalent or less restrictive open 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 and federated rolling stock reference databases (‘RSRDs’) at Union level in accordance with the specifications referenced in Appendix C, index [103].

• (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 [103], 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 [^ntr5-L_202600253EN.002801-E0005], in particular ‘administrative data’ referred to in point (5)(a) of this section and ‘design data’ referred to in point (5) (b) of this section;

• (b) the European register of authorised types of vehicles (ERATV) set up in accordance with Article 48 of Directive (EU) 2016/797 and Commission Implementing Decision 2011/665/EU [^ntr6-L_202600253EN.002801-E0006], in particular ‘design data’ referred to in point (5)(b) of this section.

• (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 or any other equivalent or less restrictive open 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 Section 3.

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 standardised and federated reference databases for intermodal loading units (ILUs) in accordance with points (3), (4) and (5) and the specifications referenced in Appendix C, indexes [103] and [1].

• (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 identifier of ILUs, including all types of semi-trailers, in accordance with the specifications referenced in Appendix C, index [2];

• (b) the ILU type (container, swap body or semi-trailer) and its compatibility with freight wagons and routes in accordance with the specifications referenced in Appendix C, index [2];

• (c) relevant load 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 or any other equivalent or less restrictive open 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 [2];

• (b) design data:

ILU reference data relating to the technical characteristics of ILUs, in particular data required by operators of rail freight 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.6 and of freight 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 freight service facilities involved and the lead railway undertaking in accordance with point 2.6 down into freight 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:

• (a) the rolling stock reference databases referred to in point 3.3.2 of this Annex, in particular vehicle numbers as registered in the European Vehicle Register (EVR) in accordance with Implementing Decision (EU) 2018/1614;

• (b) 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, when available, the operational status data of freight wagons referred to in point 3.3.4.

• (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 standardised and federated 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 pursuant to the Article 4(1), including vehicle keepers and fleet managers, and to the 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 data about freight wagon status 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 freight wagons and ILUs undergo pursuant to applicable legislation.

• (7) The WIMO databases shall contain real-time data relating to the movement of a freight wagon or an ILU from departure until its final delivery at freight customer sidings. The data shall include wagon running information referred to in point 3.2.1 and wagon forecast information referred to in point 3.2.3.

• (8) Train traffic data, wagon running and forecast information, and information relating to the movement of ILUs, shall be shared through the WIMO databases by railway undertakings at the latest at the release time of the freight wagon or the ILU by the freight customer that is referred to in the contract of carriage. The release time is the first entry shared by the railway undertaking of departure at the rail freight service facility of origin (the ‘outbound railway undertaking’) in the WIMO databases for the movement of a freight wagon or an ILU for an identified freight rail transport service.

3.3.4.2.   Loading of the freight wagon

The outbound railway undertaking shall register the status ‘loading of the freight wagon’ and grant access to it in the WIMO databases. It shall apply this status until the termination of the loading is notified to it by the freight customer that is referred to in the contract of carriage.

3.3.4.3.   Loaded freight wagon on journey

The outbound railway undertaking shall register the status ‘loaded freight wagon on journey’ and grant access to it in the WIMO databases upon departure from origin, in accordance with point 3.2.1.5, of a freight wagon that is loaded.

3.3.4.4.   Empty freight wagon on journey

The outbound railway undertaking shall register the status ‘empty freight wagon on journey’ and grant access to it in the WIMO databases upon departure from origin, in accordance with point 3.2.1.5, of a freight wagon that is empty.

3.3.4.5.   Unloading of the freight wagon

The railway undertaking of arrival at a rail freight service facility of destination (the ‘inbound railway undertaking’) shall register the status ‘unloading of the freight wagon’ and grant access to it in the WIMO databases. It shall apply this status until the termination of the unloading is notified to it by the freight customer that is referred to in the contract of carriage.

3.3.4.6.   Empty freight wagon under fleet management control

The inbound railway undertaking shall register the status ‘empty freight wagon under fleet management control’ in the WIMO databases to reflect the availability of an empty freight wagon with specified characteristics.

3.4.   Data sharing with other stakeholders

Infrastructure managers, operators of rail freight 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 PASSENGER RAIL TRANSPORT SERVICES AND RAIL PASSENGER TRAVEL INFORMATION

4.1.   General

• (1) The provisions of Section 4 lay down the requirements for interoperable data sharing required to carry out the processes referred to in Article 2(1), point (c), for any passenger rail transport service operated in the Union.

• (2) Rights to access rail ticketing data are laid down in Articles 4 and 6.

• (3) Rail ticketing data shall consist of 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

The provisions of this point apply to all passenger rail transport services.

• (1) Passenger timetable data shared pursuant to Article 6(1) 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) passenger train identification number of a train as the ‘RetailServiceId’ in combination with the reference train identifier referred to in points 2.1.2 to 2.1.5;

• (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) rail 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 rail transport services, including public time of arrival, public time of departure and public passing times;

• (k) stops with passenger boarding or alighting restrictions;

• (l) overnight trains;

• (m) crossing of time zones;

• (n) pricing regime and reservation details;

• (o) organisation identifier of the data holder specified in point 1.2.1;

• (p) service facilities as defined in Article 3, point (11), of Directive (EU) 2012/34;

• (q) accessibility of the train in accordance with point 4.4.3.1, including scheduled existence of priority seats, wheelchair spaces, universal sleeping compartments;

• (r) service extras;

• (s) connection times between passenger transport services specified in point 4.2.2;

• (t) station list;

• (u) existing direct, and indirect where known, online sales channels of distributors where live availability of rail products can be checked.

• (3) Each railway undertaking, or where relevant the data holder, shall grant access to all its passenger timetable data in accordance with Article 6(1) for use under the conditions of the Creative Commons BY-NC-ND 4.0 licence or any other equivalent or less restrictive open licence or any other equivalent or less restrictive access conditions mutually agreed upon by the involved stakeholders.

• (4) No later than one week after the final working timetable of a passenger rail transport service has been published by the infrastructure managers concerned, each railway undertaking concerned, or where relevant the data holder, shall grant access to the annual passenger timetable data of that service in accordance with Article 6(1).

• (5) No later than three weeks before an update to the annual passenger timetable of a passenger rail transport service takes effect, each railway undertaking concerned, or where relevant the data holder, shall update the annual passenger timetable data in relation to that service in accordance with Article 6(1). The annual passenger timetable data of that service shall also be updated where it is impacted by the discontinuation of passenger rail 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 passenger rail transport service.

• (6) Each railway undertaking, or where relevant the data holder, shall grant access 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 passenger rail transport service, with or without intermediate station stops, is operated or intended to be operated by several railway undertakings, the lead railway undertaking designated pursuant to Article 13 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 part of a passenger rail transport service operated by a single railway undertaking, this undertaking shall remain responsible for granting access pursuant to Article 6 to the data aggregated by the lead railway undertaking.

• (8) Passenger timetable data shared pursuant to Article 6(1) shall constitute:

• (a) an appropriate format and technical means respectively within the meaning of Articles 9(3) and 10(4) of Regulation (EU) 2021/782 to grant digital access to time schedules as part of pre-journey information referred to in the Part I of Annex II to that Regulation and meeting corresponding obligations under Articles 9(1) and 10(5) of that Regulation;

• (b) a digital machine-readable format within the meaning of Article 4(1), point (b), of Commission Delegated Regulation (EU) 2017/1926 to grant access digitally to timetables and planned interchanges referred to in the point 1.1(d), subpoints (v) and (vi), of the Annex to that Regulation as part of static travel data.

4.2.2.   Passenger timetable data of connection times

• (1) Passenger timetable data of connection times shared pursuant to Article 6(2) 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 to passenger timetable data of connection times in accordance with Article 6(2) for use under the conditions of the Creative Commons BY-NC-ND 4.0 licence or any other equivalent or less restrictive open licence or any other equivalent or less restrictive access conditions mutually agreed upon by the involved stakeholders.

• (4) No later than one week after the final working timetable of a passenger rail transport service has been published by the infrastructure managers concerned, each station manager concerned, or where relevant the infrastructure manager or the data holder, shall grant access in accordance with Article 6(2) to the connection times that are applicable to that service for the upcoming annual passenger timetable.

• (5) No later than three weeks before an update to the annual passenger timetable connection times takes effect, station managers, or where relevant infrastructure managers or data holders, responsible for those changes shall update the corresponding passenger timetable data in accordance with Article 6(2). A station manager, or where relevant an infrastructure manager or the data holder, may exceptionally apply emergency updates within shorter deadlines.

• (6) Each station manager concerned, or where relevant the infrastructure manager or the data holder, shall grant access 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.

• (8) Passenger timetable data of connection times shared pursuant to Article 6(2) shall constitute a digital machine-readable format within the meaning of Article 4(1), point (b), of Commission Delegated Regulation (EU) 2017/1926 to grant access digitally to default transfer times at interchanges referred to in the point 1.1 (d), subpoints (i) and (ii) of the Annex to that Regulation as part of static travel data.

4.2.2.1.   Minimum connection times

• (1) Stations managers shall establish in accordance with the following table the minimum connection times pursuant to Article 15 considering the public arrival time of the inbound passenger transport service and the public departure time of the outbound passenger transport 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
Within one station	Default minimum connection time in a station.	Station manager, or where relevant infrastructure manager	Mandatory
Within one station	Minimum connection time for a specific type of passenger transport service operated by a specific undertaking.	Station manager, or where relevant infrastructure manager	Optional
Within one station	Minimum connection time for a specific type of passenger transport service, regardless of the undertaking operating that type of service.	Station manager, or where relevant infrastructure manager	Optional
Within one station	Minimum connection time for a specific undertaking, regardless of the type of passenger transport service.	Station manager, or where relevant infrastructure manager	Optional
Between two stations	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
Between two stations	Minimum connection time for a specific type of passenger transport service operated by a specific undertaking.	Station managers, or where relevant infrastructure managers, that are involved	Optional
Between two stations	Minimum connection time for a specific type of passenger transport service, regardless of the undertaking operating that type of service.	Station managers, or where relevant infrastructure managers, that are involved	Optional
Between two stations	Minimum connection time for a specific undertaking, regardless of the type of passenger transport service.	Station managers, or where relevant infrastructure managers, that are involved	Optional

• (2) For stations with a single platform that are not served by any scheduled passenger transport services other than rail, the minimum connection time in that station shall correspond to the duration of train stops in that station or be null.

4.2.2.2.   Connection times within one station

Connection times applicable within a single station shall be used as follows:

• (a) where a minimum connection time is established for a specific pair of outbound and inbound 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 established between the outbound passenger transport services of a specific undertaking in relation to a specific type of service or brand name and the inbound 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 established between the outbound passenger transport services of a specific type of service or brand name and the inbound 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 established between a specific outbound undertaking and a specific inbound 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) are met, the default minimum connection time specified for that station shall be applied by station managers, railway undertakings, distributors and retailers.

4.2.2.3.   Connection times between two stations

Connection times applicable between two stations shall be used as follows:

• (a) where a minimum connection time is established between a specific outbound undertaking in relation to a specific type of passenger transport service or brand name and a specific inbound undertaking in relation to a specific type of passenger transport 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 established between the outbound passenger transport services of a specific type of service or brand name and the inbound 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 established between a specific outbound undertaking and a specific inbound 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 established between two stations, it shall be applied by station managers, railway undertakings, distributors and retailers as the minimum connection time between those stations;

• (e) where none of the conditions set out in points (a) to (d) are met, 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 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.   Tariff data for passenger rail transport services

• (1) Tariff data shared pursuant to Article 6(3) shall comply with the specifications referenced in Appendix C, indexes [P.3] and [B.16].

• (2) For direct access to and commercial use of tariff data pursuant to the second sentence of Article 6(3), and pending the future developments listed to in Article 23, points (c) and (e), the use of other data formats fully compatible and interoperable with the specifications referenced in Appendix C, indexes [P.7] may be agreed on contractual basis.

• (3) The tariff data shall contain passenger rail transport services, or part of such services, and at least the following information:

• (a) all the existing tariffs and associated tables of prices, including common, special or discounted prices and travel passes, excluding those applicable to the employees of the data holder, or to employees of other companies provided they were commercially agreed as special business-to-business tariffs;

• (b) information whether a price is yielded, that is subject to dynamic pricing such as yield management or capacity considerations, as well as information on the ranges applied to that price per category;