1 ANNEX, Regulation (EU) 2026/253

In forcesince 6 Feb 2026
(1)

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 in accordance with point 2.7 of Annex III to that Directive.

(2)

In addition to the levels of integrity and dependability set out in the specifications referenced in Appendix C, index [104], [1] and [106], for the storage or sharing of data pursuant to this Regulation as referred to in the column ‘Safety’ of Appendix F, data holders and data recipients may apply additional levels where such data is intended to be used for the safety of operations not covered by the control command and signalling subsystems.

(3)

Additional levels of integrity and dependability for data stored or shared pursuant to this Regulation intended to be used for the safety of operations 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. Where data stored or shared pursuant to this Regulation is intended to be used in operation by telematics stakeholders for the safety of operations, suitable additional levels of integrity and dependability shall be set out in their safety management system based on common safety methods for risk evaluation and assessment and specified through agreement. Such an agreement shall not constitute an obstacle to access the network.

(4)

Additional levels agreed by telematics stakeholders shall be delivered within the process managed by the Agency referred in Article 5 of Directive (EU) 2016/797.

(1)

The procedure for the assignment of codes referred to in Article 9 is set out in the specifications referenced in Appendix C, index [103].

(2)

The Agency shall manage common reference data in accordance with Articles 8 and 9 and the specifications referenced in Appendix C, index [103] and grant access to those data for use under the conditions of the EUPL 1.2 licence.

(1)

The data presentation of an organisation code shall comply with the specifications referenced in Appendix C, index [1].

(2)

Until 31 December 2025, a specific range of organisation codes shall be reserved for organisations falling within the scope of this Regulation.

(1)

Any reference to a geographical point necessary for data sharing pursuant 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 [1].

For the purposes of Article 7(2), each telematics stakeholder shall:

(a)

implement cybersecurity risk-management measures in accordance with Directives (EU) 2022/2555 [Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union , amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive) (OJ L 333, 27.12.2022, p. 80, ELI: http://data.europa.eu/eli/dir/2022/2555/oj).] and (EU) 2022/2557 [Directive (EU) 2022/2557 of the European Parliament and of the Council of 14 December 2022 on the resilience of critical entities and repealing Council Directive 2008/114/EC (OJ L 333, 27.12.2022, p. 164, ELI: http://data.europa.eu/eli/dir/2022/2557/oj).] of the European Parliament and of the Council;

(b)

use public key infrastructure (‘PKI’) in accordance with the specifications referenced in Appendix C, index [106];

(c)

use communication protocols belonging to the Transmission Control Protocol / Internet Protocol (TCP/IP) suite.

(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 [1]. The Agency shall ensure access to all applicable versions for use under the conditions of the EUPL 1.2 licence.

(2)

The Agency shall ensure through the change control management procedure referred to in Article 12 that the ERA Ontology is compatible with the following data catalogue elements and includes them as subsets:

(a)

the technical specifications referenced in Appendix C, index [105], for the purposes of the processes referred to in Article 2(1), points (a) and (b);

(b)

the technical specifications referenced in Appendix C, indexes [P.7], [B.5], [B.10], and [B.14], for the purposes of the processes referred to in Article 2(1), point (c).

(3)

Data, objects and messages shared pursuant to this Regulation shall be serialised in a format mutually agreed upon by the involved stakeholders that comply with the subsets listed in point 1.4(2), as included in the ERA Ontology.

(4)

The sequence of the messages to be exchanged pursuant this Regulation shall comply with the specifications referenced in Appendix C, index [100].

For the purposes of identifying a deficiency in data quality as part of the quality assurance check referred to in Article 10, paragraphs (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)

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 which 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 referred to in points 1.2, 3.3 and 4.8 that are correct in comparison with the actual value of the primary data.

(3)

The nominal accuracy is 100 %.

(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 recipient, that is to say the telematics stakeholder using the data, shall ensure that its telematics applications check the completeness and compliance of the data used against the metadata.

(3)

The completeness of the data shall be measured as the percentage of mandatory data fields that contain values.

(4)

The nominal completeness is 100 %.

(1)

The data holder shall ensure that its telematics applications operate in accordance with the business rules established by the data holder to guarantee data consistency.

(2)

Where data consistency needs to be checked against different sources and versions of the reference data referred to in points 1.2, 3.3 and 4.8, 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, and records, and across processes.

(5)

The nominal consistency is 100 %.

(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 for each function by the data holder without prejudice to applicable rules, in particular the rules for the transport of dangerous goods.

(1)

The data holder shall ensure that there are no duplicated records in the data shared. It shall identify and eliminate any redundant records in the data shared 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 and records to 100 %.

(3)

The nominal uniqueness is 100 %.

Pursuant to Article 18, telematics stakeholders shall self-assess, in relation to the data shared, the compliance of the telematics applications they use to implement this Regulation against the testing procedures and the evidence-based declaration set out in Appendix D.

(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 (‘APIs’) and web user interfaces (‘web UIs’) 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 [1], 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 UIs referred to in point (1).

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

Aspects relating to the interoperability of web UIs in the area of the management of freight wagons and their load, 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 in Appendix B to this Annex.

(1)

Section 2 lays down the requirements for interoperable data sharing required to carry out the processes referred to in Article 2(1), point (a).

(2)

Data in the areas of capacity management, train preparation, and traffic management, shall be shared by means of an API or a web UI in accordance with Article 14 and point 1.7.

(3)

In the areas of capacity management, train preparation, and traffic management of a rail transport service, telematics stakeholders subject to Article 4 shall mutually share, grant access and use, for operational and non-commercial purposes, all free-of-charge, data relating to the trains that are part of this rail transport service.

(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 consistently used by them. Those objects shall be marked with unique identifiers in the planning phase of that rail transport service and consistently used in the 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 [1].

(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.8, using a unique and stable identifier of the train, that is the reference train identifier (object type ‘TR’, as part of the ‘PlannedTransportIdentifier’) for the complete lifecycle of the train and the related objects across networks.

(2)

The lead railway undertaking shall specify the reference train identifier.

(3)

The reference train identifier shall be in accordance with the specifications referenced in Appendix C, index [1].

(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 the objects referred to in points 2.1.3 to 2.1.7.

(1)

The train object (‘TrainID’), linked to the reference train identifier referred to in point 2.1.2, 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 ‘TrainID’ shall be sent by each applicant to the infrastructure managers involved along the route of that service by means of the following elements:

(a)

the reference train identifier in accordance with point 2.1.2;

(b)

the route object in accordance with point 2.1.6 and the ‘path request’ object in accordance with point 2.1.4;

(c)

the elements of the messages relating to:

(i)

capacity allocation referred to in point 2.3;

(ii)

train preparation as referred to in point 2.5.

(3)

The ‘TrainID’ describes the planned train for a rail transport service and its entire route.

(1)

The path request object (‘PathRequestID’), linked to the reference train identifier referred to in point 2.1.2, 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 involved along the route of that service.

(3)

The path request object describes the details of the path requested for the planned train on the network. It shall contain, as attribute, the identifier of the lead railway undertaking. It may contain, as attribute, the expected operational train number (‘OperationalTrainNumberIdentifier’). It may also contain, as attribute, the commercial train number (‘RetailServiceId’)

(1)

The path object (object type ‘PA’, as part of the ‘PlannedTransportIdentifier’) shall be specified by the infrastructure manager which is responsible for corresponding path on its network.

(2)

The path object shall be sent by the infrastructure manager to the applicant.

(3)

The path object describes the details of the path allocated for a train. Infrastructure managers involved along the route of that train shall coordinate between themselves the path objects.

(4)

Where a specific train number is specified by the applicant as part of the path request object referred to in point 2.1.4(3), the path object sent by the infrastructure manager to the applicant shall contain, as attribute, the train number assigned, which may change along the lifecycle of the path or the linked train.

(1)

The route object (object type ‘RO’, as part of the ‘PlannedTransportIdentifier’) shall be specified by the lead railway undertaking. It refers to the geographical line of operation from a point of origin to a point of destination.

(2)

Once consistently integrated by the lead railway undertaking responsible for coordinating the applicants for a single rail transport service, the route object shall be sent by the applicant to all infrastructure managers involved along the route of that service.

(3)

The route object describes the minimum information about the entire route for which an infrastructure manager needs to perform its duties including the analysis of the ‘path request’.

(4)

The route object shall contain at least the following information:

(a)

point of origin;

(b)

points of handover as referred in point 2.6.2 (b);

(c)

point of destination;

(d)

corresponding planned dates according to the working timetable.

(1)

The case reference object (object type ‘CR’, as part of the ‘PlannedTransportIdentifier’) shall be specified by the holder of that data.

(2)

Where a specific object or data are used or intended to be used by a telematics stakeholder, they shall be part of a dedicated ‘case reference object’ subject to the process referred to in Article 11.

(3)

Except for block trains referred to in point 2.6.1 (6), aspects relating to the interoperability of data sharing for the identification of shunting movements, including in rail freight service facilities, 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.

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

(1)

The data required and allocated pursuant to the Annex to Implementing Regulation (EU) 2019/773 (‘OPE TSI’), as referred to in Appendix A to this Annex, in relation to the capacity rights and the characteristics of the train for each section of these rights, including the sections in rail freight service facilities, are designated hereafter as ‘path’.

The first paragraph of this point is 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 Implementing Regulation (EU) 2017/2177, solely in relation to the sections of that rail transport service operated in a rail freight service facility.

(2)

Where allocating infrastructure capacity referred to in Section 3 of Chapter IV 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 UI referred to in Article 14 and point 1.7 of the Annex to this Regulation.

(3)

Where allocating capacity in rail freight service facilities referred to in Article 13 of Directive 2012/34/EU and Articles 7, 8 and 9 of Implementing Regulation (EU) 2017/2177, solely in relation to the sections of a freight rail transport service subject to the allocation of a path, 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 for the network connected to those rail freight service facilities using an API or a web UI referred to in Article 14 and point 1.7 of the Annex to this Regulation.

(4)

Aspects relating to the interoperability of data sharing for the planning of shunting movements and stabling 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.

(5)

In the case of multi-network processes in the area of capacity allocation that involve more than one infrastructure manager or operator of rail freight service facilities along a train route, the infrastructure managers and operators of rail freight 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 capacity across multiple networks may use the common Union API or a common Union web UI referred to in Article 14(5) of this Regulation.

Aspects relating to the interoperability of data sharing for the coordination of multi-network processes in the area of capacity management 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.

(6)

Where more than one railway undertaking operates a rail transport service, the railway undertakings 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 pursuant to Article 13(1), point (b), integrating the object identifiers referred to in point 2.1 for the overall route of that service.

(7)

In the case of an intermodal transport service, the railway undertakings involved may delegate the role of lead railway undertaking or applicant to an intermodal transport operator for the overall route of corresponding freight rail transport service.

(8)

In case of a short-notice request for the allocation of infrastructure capacity close to departure or during real-time operations, information relating to corresponding path shall be communicated as part of a path section modification in accordance with point 2.6.7.

The time threshold related to the remaining time until the departure of a train at the time of the request for capacity allocation from which this request is to be considered ad hoc is 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.

(9)

In the case of a freight rail transport service where the actual characteristics of the consignment require the path allocated to be adapted, the information contained in the ‘ConsignmentNoteMessage’ referred to in point 3.1.1 shall be used as part of a path section modification in accordance with point 2.6.7.

(10)

Messages exchanged for the allocation of a path relating to a freight rail transport service shall contain information identifying quieter routes intended for operation, if any, in accordance with the Annex to Regulation (EU) No 1304/2014 (NOI TSI), as referred to in Appendix A to this Annex.

(11)

In the case of an intermodal transport service, the messages exchanged in accordance with points (2) and (3) for the allocation of paths for corresponding freight rail transport service shall contain information relating to the maximum profile of the intermodal loading units intended to be used for that service.

(12)

The working timetable reflects the paths that are confirmed as allocated.

(1)

The ‘PathRequestMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

(2)

To request a path, the applicant shall send a ‘PathRequestMessage’ to the infrastructure managers concerned.

(1)

The ‘PathDetailsMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

(2)

In response to a ‘PathRequestMessage’ received from an applicant in accordance with point 2.3.2, each infrastructure manager shall send a ‘PathDetailsMessage’ to specify the details of the path offered to the applicant.

(1)

The ‘PathConfirmedMessage’ shall be in accordance with the specifications referenced in Appendix C, index [1].

(2)

To confirm the allocation of the path offered by an infrastructure manager in the ‘PathDetailsMessage’ referred to in point 2.3.3, the applicant shall send back the ‘PathConfirmedMessage’.

(3)

Upon receipt of the ‘PathConfirmedMessage’, the receiving infrastructure manager shall acknowledge its receipt by sending the originating applicant a ‘PathDetailsMessage’ confirming the booking and integrate the corresponding path in its working timetable.

This article is long: the rest is at the official publication.