Legalize / European Union / Implementing Regulation

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)

Type Implementing Regulation

Publication 2026-02-10

State In force

Text As published

Department European Commission, MOVE

Source EUR-Lex

articles 27

This is the act as published. Later amendments are not folded into the text below: each one is a separate act in this repository and an entry in this law's history.

Reform history JSON API

Until proof of compliance of their telematics applications is provided pursuant to Article 18, telematics stakeholders shall report to the Agency, using the automated web application referred to in paragraph 1, setting out in an accurate and transparent manner the status of their implementation and their implementation plans to meet the milestones set out in Appendix G of the Annex, in accordance with the following conditions:

(a) no later than 2 September 2027, each infrastructure manager shall report in the following areas:

(i) capacity management;

(ii) train preparation;

(iii) traffic management;

(b) no later than 2 March 2028:

(i) each freight railway undertaking shall report in the areas of train preparation and the management of freight wagons and their load;

(ii) each operator of rail freight service facilities shall report in the area of traffic management;

(iii) each station manager shall report in the area of rail ticketing and rail passenger travel information;

(iv) each passenger railway undertaking shall report in the areas of train preparation, rail ticketing and rail passenger travel information.

Telematics stakeholders shall coordinate their efforts in drawing up their implementation plans. Each Member State shall support national coordination or delegate the task to the national contact point.

The Agency shall publish aggregated figures about the status of the implementation and the implementation plans per Member State and at Union level, linked to the network size for infrastructure managers and to market share of railway undertakings expressed as tonnes/km and passengers/km, respectively.

Article 18

Compliance assessment

The Agency shall provide a web application enabling telematics stakeholders to automatically self-assess individual messages.

The Agency shall publish a user manual describing the different functions of the web applications.

Each telematics stakeholder subject to reporting obligations pursuant to Article 17 shall self-assess the compliance of its telematics applications only in relation to the data shared using the web application referred to in paragraph 1 before the implementation deadlines set out in Article 16. Individual messages self-assessed shall comply with the testing procedure set out in point 1.6 of the Annex and Appendix D.1 thereto.

Where self-assessment results are positive, the web application referred to in paragraph 1 shall automatically perform all the following functions:

(a) issue an evidence-based declaration providing to the self-assessed telematics stakeholder and to the Agency a presumption of compliance of self-assessed messages and associated telematics applications with the provisions of this Regulation;

(b) compile the relevant information associated with this self-assessment as set out in point 1 of Appendix D.1 to the Annex;

Where a telematics application has received a positive compliance assessment delivered and published by the Agency before the date of entry into force of this Regulation, such an assessment shall remain valid unless changes are made to it.

Changes to a telematics application shall be self-assessed where such changes have an impact on any of the following matters:

(a) the data elements, data structure or sequence to be shared pursuant to Article 7(3);

(b) the implementation of a new or updated API or web UI;

In the case a justified alleged non-compliance of a telematics application used by a telematic stakeholder, or where there is justified doubt, the Agency shall, on its own initiative or upon request of the Commission, a Union body, a public sector body or a telematics stakeholder, evaluate the correctness of the self-assessment based on the relevant information compiled pursuant to paragraph 3(b) and in accordance with the testing procedure set out in Appendix D.2.

The Agency shall inform the requesting entity and the telematics stakeholder using the telematics applications evaluated of the result, of its evaluation that may be used for follow-up actions, including enforcement by a national safety authority as defined in Article 3, point (7), of Directive (EU) 2016/798, or other national authorities responsible for the implementation of this Regulation.

The Agency shall also evaluate the correctness of the self-assessment on the basis of the information compiled in accordance with paragraph 3(b) for projects of telematics applications where an application for Union financial support has been submitted.

Upon request, the Agency may also perform such evaluation for projects not subject to Union financial support as a service pursuant to Article 64(2), point (d), and Article 80(2), point (c), of Regulation (EU) 2016/796.

The Agency shall set out, publish and apply the procedures and deadlines to evaluate the correctness of the self-assessment for the purposes of paragraphs 6, 7 and 8.

Article 19

Innovative solutions

Where a telematics stakeholder intends to use an innovative solution for a telematics application not envisaged by this Regulation, it shall submit the technical file associated with the proposed innovative solution to the Commission for analysis and declare how the interoperability of interfaces with other compliant telematics stakeholders can be ensured. The Commission shall request the opinion of the Agency pursuant to Article 10(2) of Regulation (EU) 2016/796 on the proposed innovative solution.

Where the Agency’s opinion is negative, the innovative solution proposed cannot be applied.

Where the Agency’s opinion is positive, the appropriate functional and interface specification and the testing procedure to allow the use of such innovative solution shall be developed and may subsequently be included as part of the revision process laid down in Article 5 of Directive (EU) 2016/797.

In addition to paragraph 3, the Agency may consider in its positive opinion that the innovative solution constitutes an acceptable means of compliance pursuant to Article 6(3) of Directive (EU) 2016/797. In that case, that positive opinion may be used to assess the compliance of the innovative solution with this Regulation.

Article 20

National contact point

Member States shall designate a national contact point (‘NCP’), independent from railway undertakings or other applicants, among the representatives of either a public sector body or an infrastructure manager and ensure appropriate resources.

Where a Member State decides to appoint different actors in relation to the processes referred to in Article 2(1) and the tasks referred to in paragraph 3 of this Article, the designated NCP shall ensure coordination of those actors at national level and remains the single point of contact for the Agency, the Commission, and other relevant organisations.

The NCP shall carry out the following tasks:

(a) act as Member State representative in the working party referred to in Article 22, cooperate with the Agency and other NCPs, and share with the working party relevant operational views and issues reported by telematics stakeholders in a transparent and non-discriminatory manner;

(b) collect relevant market shares and contact details of telematics stakeholders covered by Article 17, and share them with the Agency;

(c) facilitate contacts between Member States, telematics stakeholders at national level, the Agency, the Commission, and other relevant organisations;

(d) support a coordinated implementation of the provisions of this Regulation by facilitating:

(i) return of experience and exchange of best practices among telematics stakeholders at national level, as well as at Union level in the working party referred to in Article 22;

(ii) coordination of infrastructure managers’ implementation plans and consultation of other telematics stakeholders through the rail sector representative bodies listed by the Commission pursuant to Article 38(4) of Regulation (EU) 2016/796;

(iii) integration of prospective telematics stakeholders informing them about the applicable framework.

By 2 December 2026, each Member State shall communicate to the Agency the details of the designated NCP. The Agency shall publish those details.

Article 21

Cooperation and coordination

Infrastructure managers shall cooperate within the European network of infrastructure managers, referred to in Article 7f of Directive 2012/34/EU and in consultation with operators of rail freight service facilities, railway undertakings and other telematics stakeholders to coordinate the following:

(a) the development of common sector specifications for a common Union API and common Union web user interfaces referred to in Article 14(5), point (a), of this Regulation;

(b) their implementation plans at Union level and the consultation with other telematics stakeholders active at national level with the support of national contact points.

Freight railway undertakings shall cooperate on the development of a common sector specification for a common Union API and common Union web user interfaces referred to in Article 14(6).

Operators of rail freight service facilities shall cooperate on the development of a common sector specification for a common Union API and common Union web user interfaces referred to in Article 14(5), point (b).

By 30 September 2027, infrastructure managers, freight railway undertakings and operators of rail freight service facilities shall deliver within the process managed by the Agency referred in Article 5 of Directive (EU) 2016/797 their respective common sector specifications resulting from their tasks under paragraphs 1, 2 and 3 of this Article taking into account the work of the Europe’s Rail Joint Undertaking established in Title IV of Council Regulation (EU) 2021/2085 [^ntr37-L_202600253EN.000101-E0037].

Article 22

ERA working party on telematics

The working party or parties established by the Agency pursuant to Chapter 2 of Regulation (EU) 2016/796 shall assist the Agency in applying and further developing the functional and technical specifications set out in this Regulation, in particular in the following tasks of the Agency:

(a) ensure relevant coordination and cooperation of telematics stakeholders to guarantee implementation and application of this Regulation;

(b) ensure cooperation of national contact points at Union level and harmonised and coordinated implementation of their tasks across the Union;

(d) develop and maintain the user manual referred to in Article 9(1), second subparagraph and the procedure referred to in Article 9(2) for submitting requests for the assignment of reference codes;

(e) harmonise, where relevant, the network-specific data requirements referred in accordance with Article 11(3);

(f) develop and maintain the procedure referred to in Article 12(1) and maintain the harmonised specifications issued by the Agency in accordance with Article 12;

(g) provide guidance for the development of sector specifications supporting the update of harmonised specifications referred to in Articles 12 and 21;

(h) design, implement, maintain and ensure the automation of data import supporting the reporting obligations referred to in Article 17;

(i) maintain the testing procedures referred to in point 1.6 of the Annex and Appendix D.1 thereto;

(j) implement future developments of this Regulation referred to in Article 23;

(k) facilitate exchange between and collect best practices from telematics stakeholders at Union level;

(l) reflect on the need for follow-up action by the Agency, the Commission, or the Member States, where relevant;

(m) shape and contribute to the implementation of follow-up actions to the feedback provided by the working parties;

(n) identify and prepare strategic topics related to the digitalisation of the rail system with an impact on the subsystem telematics applications for discussion in a wider policy context;

(o) report to the Commission pursuant to Article 24.

Article 23

Future developments

By 31 December 2028, the Agency shall make, taking into account the work of the Europe’s Rail Joint Undertaking established in Title IV of Regulation (EU) 2021/2085 and the common specifications referred to in Article 21(4) of this Regulation, a recommendation to the Commission pursuant to Article 19(1), point (a), of Regulation (EU) 2016/796 for the update of the functional and technical specifications laid down in this Regulation with the following objectives and conduct on an impact assessment for that recommendation pursuant to Article 8 of Regulation (EU) 2016/796:

(a) reflecting regulatory and technical developments affecting the rail system;

(b) converting the list of specific data requirements based on positively assessed national rules referred to in Article 11(5) of this Regulation into harmonised specifications, specific cases, or open point as appropriate;

(d) updating the references to the specifications referred to in Article 12 of this Regulation;

(e) as part of the technical specifications referenced in Appendix C to the Annex to this Regulation, ensuring appropriate and backward compatible transition from technical documents referenced in this Regulation and other specifications compatible and interoperable with those documents to relevant European standards referred to in Regulation (EU) No 1025/2012.

CHAPTER 4 TRANSITIONAL AND FINAL PROVISIONS

Article 24

Report

The report submitted by the Agency pursuant to Article 35(4) of Regulation (EU) 2016/796 shall include an analysis of the effectiveness of this Regulation and the progress made towards achieving interoperability of the telematics subsystem of the Union rail system.

Reporting on implementation shall be based on information collected by the Agency pursuant to Article 17 of this Regulation.

For the purposes of Article 40(2) of Regulation (EU) 2016/796, the Agency shall publish an overview of Union-funded projects and its analysis of innovative outputs relating to the provisions of this Regulation, as well as its proposals for follow-up action necessary to ensure the coordinated development corresponding applications in the Union and a harmonised and coordinated implementation.

Article 25

Repeal

Regulations (EU) No 454/2011 and (EU) No 1305/2014 are repealed.

References to the repealed Regulations shall be construed as references to this Regulation.

Article 26

Transitional measures

Until the Agency provides the web applications referred to in Article 9(1), it shall assign codes through existing databases managed jointly by infrastructure managers, or by operators of rail freight service facilities or by a group of railway undertakings. For that purpose, the stakeholders managing those databases shall grant the Agency access to those databases for use.

Article 27

Entry into force and application

This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.

The following Articles shall apply from 2 September 2026:

(a) Article 8(1), points (a), (c) and (d), and Article 8(2);

(b) Article 9(2);

(d) Article 12(1).

Article 9(3) to (6) shall apply from 15 March 2026.

The following Articles shall apply from 2 March 2027:

(a) Article 8(1)(b);

(b) Article 9(1);

(d) Article 18.

This Regulation shall be binding in its entirety and directly applicable in all Member States.

Done at Brussels, 6 February 2026.

For the Commission

The President

Ursula VON DER LEYEN

[^ntr1-L_202600253EN.000101-E0001]: OJ L 138, 26.5.2016, p. 44, ELI: http://data.europa.eu/eli/dir/2016/797/oj.

[^ntr2-L_202600253EN.000101-E0002]: Commission Regulation (EU) No 454/2011 of 5 May 2011 on the technical specification for interoperability relating to the subsystem ‘telematics applications for passenger services’ of the trans-European rail system (OJ L 123, 12.5.2011, p. 11, ELI: http://data.europa.eu/eli/reg/2011/454/oj).

[^ntr3-L_202600253EN.000101-E0003]: Commission Regulation (EU) No 1305/2014 of 11 December 2014 on the technical specification for interoperability relating to the telematics applications for freight subsystem of the rail system in the European Union (OJ L 356, 12.12.2014, p. 438, ELI: http://data.europa.eu/eli/reg/2014/1305/oj).

[^ntr4-L_202600253EN.000101-E0004]: Commission Delegated Decision (EU) 2017/1474 of 8 June 2017 supplementing Directive (EU) 2016/797 of the European Parliament and of the Council with regard to specific objectives for the drafting, adoption and review of technical specifications for interoperability (OJ L 210, 15.8.2017, p. 5, ELI: http://data.europa.eu/eli/dec_del/2017/1474/oj).

[^ntr5-L_202600253EN.000101-E0005]: The recommendation of the Agency of 25 January 2022 on TAP TSI, and the recommendation of the Agency of 27 January 2022 on TAF TSI.

[^ntr6-L_202600253EN.000101-E0006]: Directive 2012/34/EU of the European Parliament and of the Council of 21 November 2012 establishing a single European railway area (recast) (OJ L 343, 14.12.2012, p. 32, ELI: http://data.europa.eu/eli/dir/2012/34/oj).

[^ntr7-L_202600253EN.000101-E0007]: Regulation (EU) 2024/1679 of the European Parliament and of the Council of 13 June 2024 on Union guidelines for the development of the trans-European transport network, amending Regulations (EU) 2021/1153 and (EU) No 913/2010 and repealing Regulation (EU) No 1315/2013 (OJ L, 2024/1679, 28.6.2024, ELI: http://data.europa.eu/eli/reg/2024/1679/oj).

[^ntr8-L_202600253EN.000101-E0008]: Directive (EU) 2016/798 of the European Parliament and of the Council of 11 May 2016 on railway safety (recast) (OJ L 138, 26.5.2016, p. 102, ELI: http://data.europa.eu/eli/dir/2016/798/oj).

[^ntr9-L_202600253EN.000101-E0009]: Commission Implementing Regulation (EU) 2017/2177 of 22 November 2017 on access to service facilities and rail-related services (OJ L 307, 23.11.2017, p. 1, ELI: http://data.europa.eu/eli/reg_impl/2017/2177/oj).

[^ntr10-L_202600253EN.000101-E0010]: Commission Delegated Regulation (EU) 2017/1926 of 31 May 2017 supplementing Directive 2010/40/EU of the European Parliament and of the Council with regard to the provision of EU-wide multimodal travel information services (OJ L 272, 21.10.2017, p. 1, ELI: http://data.europa.eu/eli/reg_del/2017/1926/oj).

[^ntr11-L_202600253EN.000101-E0011]: Regulation (EU) 2020/1056 of the European Parliament and of the Council of 15 July 2020 on electronic freight transport information (OJ L 249, 31.7.2020, p. 33, ELI: http://data.europa.eu/eli/reg/2020/1056/oj).

[^ntr12-L_202600253EN.000101-E0012]: Regulation (EU) 2021/782 of the European Parliament and of the Council of 29 April 2021 on rail passengers’ rights and obligations (recast) (OJ L 172, 17.5.2021, p. 1, ELI: http://data.europa.eu/eli/reg/2021/782/oj).

[^ntr13-L_202600253EN.000101-E0013]: Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 on harmonised rules on fair access to and use of data and amending Regulation (EU) 2017/2394 and Directive (EU) 2020/1828 (Data Act) (OJ L, 2023/2854, 22.12.2023, ELI: http://data.europa.eu/eli/reg/2023/2854/oj).

[^ntr14-L_202600253EN.000101-E0014]: Regulation (EU) 2022/868 of the European Parliament and of the Council of 30 May 2022 on European data governance (Data Governance Act) (OJ L 152, 3.6.2022, p. 1, ELI: http://data.europa.eu/eli/reg/2022/868/oj).

[^ntr15-L_202600253EN.000101-E0015]: Regulation (EU) 2021/782 of the European Parliament and of the Council of 29 April 2021 on rail passengers’ rights and obligations (OJ L 172, 17.5.2021, p. 1, ELI: http://data.europa.eu/eli/reg/2021/782/oj).

[^ntr16-L_202600253EN.000101-E0016]: Solutions specified in the ERA technical document B.5:

A1: TAP TSI legacy binary messages-based API;

A2: TAP TSI legacy XML/SOAP-based API;

B1: The Open Sales and Distribution Model (OSDM) JSON/REST based API;

B2: The Transmodel (EN12896) and JSON/REST based Open Mobility Sales API (OMSA).

[^ntr17-L_202600253EN.000101-E0017]: Regulation (EU) No 1025/2012 of the European Parliament and of the Council of 25 October 2012 on European standardisation, amending Council Directives 89/686/EEC and 93/15/EEC and Directives 94/9/EC, 94/25/EC, 95/16/EC, 97/23/EC, 98/34/EC, 2004/22/EC, 2007/23/EC, 2009/23/EC and 2009/105/EC of the European Parliament and of the Council and repealing Council Decision 87/95/EEC and Decision No 1673/2006/EC of the European Parliament and of the Council (OJ L 316, 14.11.2012, p. 12, ELI: http://data.europa.eu/eli/reg/2012/1025/oj).

[^ntr19-L_202600253EN.000101-E0019]: Regulation (EC) No 223/2009 of the European Parliament and of the Council of 11 March 2009 on European statistics and repealing Regulation (EC, Euratom) No 1101/2008 of the European Parliament and of the Council on the transmission of data subject to statistical confidentiality to the Statistical Office of the European Communities, Council Regulation (EC) No 322/97 on Community Statistics, and Council Decision 89/382/EEC, Euratom establishing a Committee on the Statistical Programmes of the European Communities (OJ L 87, 31.3.2009, p. 164, ELI: http://data.europa.eu/eli/reg/2009/223/oj).

[^ntr20-L_202600253EN.000101-E0020]: OJ C 240, 24.7.2014, p. 1.

[^ntr21-L_202600253EN.000101-E0021]: Commission Implementing Decision (EU) 2017/863 of 18 May 2017 updating the open source software licence EUPL to further facilitate the sharing and reuse of software developed by public administrations (OJ L 128, 19.5.2017, p. 59, ELI: http://data.europa.eu/eli/dec_impl/2017/863/oj).

[^ntr22-L_202600253EN.000101-E0022]: Regulation (EU) 2016/796 of the European Parliament and of the Council of 11 May 2016 on the European Union Agency for Railways and repealing Regulation (EC) No 881/2004 (OJ L 138, 26.5.2016, p. 1, ELI: http://data.europa.eu/eli/reg/2016/796/oj).

[^ntr23-L_202600253EN.000101-E0023]: Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (OJ L 119, 4.5.2016, p. 1, ELI: http://data.europa.eu/eli/reg/2016/679/oj).

[^ntr24-L_202600253EN.000101-E0024]: Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC (OJ L 295, 21.11.2018, p. 39, ELI: http://data.europa.eu/eli/reg/2018/1725/oj).

[^ntr25-L_202600253EN.000101-E0025]: Directive 2012/34/EU of the European Parliament and of the Council of 21 November 2012 establishing a single European railway area (recast) (OJ L 343, 14.12.2012, p. 32, ELI: http://data.europa.eu/eli/dir/2012/34/oj).

[^ntr26-L_202600253EN.000101-E0026]: Directive (EU) 2016/798 of the European Parliament and of the Council of 11 May 2016 on railway safety (OJ L 138, 26.5.2016, p. 102, ELI: http://data.europa.eu/eli/dir/2016/798/oj).

[^ntr27-L_202600253EN.000101-E0027]: Commission Implementing Regulation (EU) 2019/773 of 16 May 2019 on the technical specification for interoperability relating to the operation and traffic management subsystem of the rail system within the European Union and repealing Decision 2012/757/EU (OJ L 139I, 27.5.2019, p. 5, ELI: http://data.europa.eu/eli/reg_impl/2019/773/oj).

[^ntr28-L_202600253EN.000101-E0028]: Commission Implementing Regulation (EU) 2023/1695 of 10 August 2023 on the technical specification for interoperability relating to the control-command and signalling subsystems of the rail system in the European Union and repealing Regulation (EU) 2016/919 (OJ L 222, 8.9.2023, p. 380, ELI: http://data.europa.eu/eli/reg_impl/2023/1695/oj).

[^ntr29-L_202600253EN.000101-E0029]: Commission Regulation (EU) No 1300/2014 of 18 November 2014 on the technical specifications for interoperability relating to accessibility of the Union’s rail system for persons with disabilities and persons with reduced mobility (OJ L 356, 12.12.2014, p. 110, ELI: http://data.europa.eu/eli/reg/2014/1300/oj).

[^ntr30-L_202600253EN.000101-E0030]: Commission Regulation (EU) No 1304/2014 of 26 November 2014 on the technical specification for interoperability relating to the subsystem ‘rolling stock — noise’ amending Decision 2008/232/EC and repealing Decision 2011/229/EU (OJ L 356, 12.12.2014, p. 421, ELI: http://data.europa.eu/eli/reg/2014/1304/oj).

[^ntr31-L_202600253EN.000101-E0031]: Commission Regulation (EU) No 1301/2014 of 18 November 2014 on the technical specifications for interoperability relating to the energy subsystem of the rail system in the Union (OJ L 356, 12.12.2014, p. 179, ELI: http://data.europa.eu/eli/reg/2014/1301/oj).

[^ntr32-L_202600253EN.000101-E0032]: Commission Regulation (EU) No 1302/2014 of 18 November 2014 concerning a technical specification for interoperability relating to the rolling stock — locomotives and passenger rolling stock subsystem of the rail system in the European Union (OJ L 356, 12.12.2014, p. 228, ELI: http://data.europa.eu/eli/reg/2014/1302/oj).

[^ntr33-L_202600253EN.000101-E0033]: European Data Protection Supervisor’s opinion C2025-0228.

[^ntr34-L_202600253EN.000101-E0034]: Council Regulation No 11 concerning the abolition of discrimination in transport rates and conditions, in implementation of Article 79(3) of the Treaty establishing the European Economic Community (OJ 52, 16.8.1960, p. 1121, ELI: http://data.europa.eu/eli/reg/1960/11/oj).

[^ntr35-L_202600253EN.000101-E0035]: Directive 2008/68/EC of the European Parliament and of the Council of 24 September 2008 on the inland transport of dangerous goods (OJ L 260, 30.9.2008, p. 13, ELI: http://data.europa.eu/eli/dir/2008/68/oj).

[^ntr36-L_202600253EN.000101-E0036]: Regulation (EC) No 1370/2007 of the European Parliament and of the Council of 23 October 2007 on public passenger transport services by rail and by road and repealing Council Regulations (EEC) Nos 1191/69 and 1107/70 (OJ L 315, 3.12.2007, p. 1, ELI: http://data.europa.eu/eli/reg/2007/1370/oj).

[^ntr37-L_202600253EN.000101-E0037]: Council Regulation (EU) 2021/2085 of 19 November 2021 establishing the Joint Undertakings under Horizon Europe and repealing Regulations (EC) No 219/2007, (EU) No 557/2014, (EU) No 558/2014, (EU) No 559/2014, (EU) No 560/2014, (EU) No 561/2014 and (EU) No 642/2014 (OJ L 427, 30.11.2021, p. 17, ELI: http://data.europa.eu/eli/reg/2021/2085/oj).

ANNEX

TABLE OF CONTENT


1.	Common requirements	33

---	---	---
1.1.	Essential requirements	33

---	---	---
1.2.	Common reference data	33

---	---	---
1.2.1.	Organisation reference data	33

---	---	---
1.2.2.	Location reference data	33

---	---	---
1.3.	Cybersecurity	34

---	---	---
1.4.	Data presentation	34

---	---	---
1.5.	Data quality criteria	34

---	---	---
1.5.1.	Accuracy	34

---	---	---
1.5.2.	Completeness	35

---	---	---
1.5.3.	Consistency	35

---	---	---
1.5.4.	Timeliness	35

---	---	---
1.5.5.	Uniqueness	35

---	---	---
1.6.	Compliance assessment	35

---	---	---
1.7.	Telematics applications	36

---	---	---
1.7.1.	Web user interfaces for capacity management, train preparation and traffic management	36

---	---	---
1.7.2.	Web user interfaces for the management of freight wagons and their load	36

---	---	---
2.	Capacity management, train preparation, and traffic management	36

---	---	---
2.1.	Object identifiers	36

---	---	---
2.1.1.	General	36

---	---	---
2.1.2.	Reference train identifier	36

---	---	---
2.1.3.	Train object	37

---	---	---
2.1.4.	Path request object	37

---	---	---
2.1.5.	Path object	37

---	---	---
2.1.6.	Route object	37

---	---	---
2.1.7.	Case reference object	38

---	---	---
2.2.	Strategic management of infrastructure capacity	38

---	---	---
2.3.	Capacity allocation	38

---	---	---
2.3.1.	General	38

---	---	---
2.3.2.	Path request	39

---	---	---
2.3.3.	Path details	39

---	---	---
2.3.4.	Path confirmed	40

---	---	---
2.3.5.	Path details refused	40

---	---	---
2.3.6.	Path cancelled	40

---	---	---
2.3.7.	Path not available	40

---	---	---
2.3.8.	Receipt confirmation	40

---	---	---
2.3.9.	Capacity allocation coordination process	41

---	---	---
2.3.10.	Working timetable	41

---	---	---
2.4.	Planned capacity restrictions	41

---	---	---
2.4.1.	Coordination of planned capacity restrictions	41

---	---	---
2.4.2.	Consultation of stakeholders affected by planned capacity restrictions	41

---	---	---
2.4.3.	Publication of planned capacity restrictions	41

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

---	---	---
2.5.	Train preparation	41

---	---	---
2.5.1.	Train composition	41

---	---	---
2.5.2.	Train ready	43

---	---	---
2.5.3.	Train readiness forecast	44

---	---	---
2.6.	Reporting of train traffic data	44

---	---	---
2.6.1.	General	44

---	---	---
2.6.2.	Reporting points	45

---	---	---
2.6.3.	Train running information	45

---	---	---
2.6.4.	Train forecast information	45

---	---	---
2.6.5.	Train delay cause	46

---	---	---
2.6.6.	Service disruption information	46

---	---	---
2.6.7.	Path modification in operation	46

---	---	---
2.7.	Historic record of train related data	47

---	---	---
2.8.	Data sharing with other stakeholders	47

---	---	---
3.	Management of freight wagons and their load	47

---	---	---
3.1.	Electronic rail freight transport information	47

---	---	---
3.1.1.	Electronic consignment note (‘eCN’)	47

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

---	---	---
3.2.	Movements of freight wagons and their load	48

---	---	---
3.2.1.	Wagon running information	49

---	---	---
3.2.1.1.	Geo-localisation of freight wagons	49

---	---	---
3.2.1.2.	Wagon status	49

---	---	---
3.2.1.3.	Wagon ready for movement	49

---	---	---
3.2.1.4.	Wagon pulled	50

---	---	---
3.2.1.5.	Wagon departure from origin	50

---	---	---
3.2.1.6.	Wagon arrival at intermediate location	50

---	---	---
3.2.1.7.	Wagon departure from intermediate location	50

---	---	---
3.2.1.8.	Wagon handed over	50

---	---	---
3.2.1.9.	Wagon taken over	51

---	---	---
3.2.1.10.	Wagon irregularity	51

---	---	---
3.2.1.11.	Wagon irregularity rectified	51

---	---	---
3.2.1.12.	Wagon arrival at destination	51

---	---	---
3.2.1.13.	Wagon delivered	51

---	---	---
3.2.2.	Intermodal loading unit movement	51

---	---	---
3.2.3.	Wagon forecast information	51

---	---	---
3.3.	Freight-specific reference data	52

---	---	---
3.3.1.	General	52

---	---	---
3.3.2.	Rolling stock reference databases	53

---	---	---
3.3.3.	Intermodal loading unit reference databases	53

---	---	---
3.3.4.	Wagon and intermodal loading unit operational databases	54

---	---	---
3.3.4.1.	General	54

---	---	---
3.3.4.2.	Loading of the freight wagon	55

---	---	---
3.3.4.3.	Loaded freight wagon on journey	55

---	---	---
3.3.4.4.	Empty freight wagon on journey	55

---	---	---
3.3.4.5.	Unloading of the freight wagon	55

---	---	---
3.3.4.6.	Empty freight wagon under fleet management control	55

---	---	---
3.4.	Data sharing with other stakeholders	55

---	---	---
4.	Rail ticketing in relation to passenger rail transport services and rail passenger travel information	56

---	---	---
4.1.	General	56

---	---	---
4.2.	Passenger timetable data	56

---	---	---
4.2.1.	Passenger timetable data	56

---	---	---
4.2.2.	Passenger timetable data of connection times	57

---	---	---
4.2.2.1.	Minimum connection times	58

---	---	---
4.2.2.2.	Connection times within one station	59

---	---	---
4.2.2.3.	Connection times between two stations	60

---	---	---
4.2.2.4.	Calculation of connection time	60

---	---	---
4.3.	Tariff data	60

---	---	---
4.3.1.	Tariff data for passenger rail transport services	60

---	---	---
4.3.2.	Management of rules for ticket issuing and ticket inspections	62

---	---	---
4.3.3.	Information about the online sales channels of railway undertakings	62

---	---	---
4.4.	Conditions of carriage	62

---	---	---
4.4.1.	General	62

---	---	---
4.4.2.	Conditions for the carriage of passengers	63

---	---	---
4.4.3.	Conditions of carriage and assistance for persons with disabilities and persons with reduced mobility (‘PRM’)	63

---	---	---
4.4.3.1.	Accessibility of rolling stock	63

---	---	---
4.4.3.2.	Accessibility of stations	64

---	---	---
4.4.4.	Condition for the carriage of luggage	64

---	---	---
4.4.5.	Conditions for the carriage of bicycles	64

---	---	---
4.4.6.	Conditions for the carriage of cars, motorcycles and boats (‘cars’)	64

---	---	---
4.5.	Availability and reservations	65

---	---	---
4.5.1.	General	65

---	---	---
4.5.2.	Availability and reservation request	66

---	---	---
4.5.3.	Availability and reservation response	66

---	---	---
4.5.4.	Availability of and reservations for PRM assistance	66

---	---	---
4.5.5.	Availability of and reservations for bicycle places	66

---	---	---
4.5.6.	Availability and reservations for the carriage of cars	67

---	---	---
4.6.	Tickets issuing for product distribution	67

---	---	---
4.6.1.	Security elements for electronic delivery	67

---	---	---
4.6.2.	Dossier reference	67

---	---	---
4.6.3.	Types and formats of tickets	67

---	---	---
4.6.4.	Ticket control and ticket state modification	67

---	---	---
4.6.4.1.	Ticket annotation	68

---	---	---
4.6.4.2.	Reimbursement or compensation request	68

---	---	---
4.7.	Rail passenger travel information during the journey	68

---	---	---
4.7.1.	Information in the station	68

---	---	---
4.7.1.1.	General	68

---	---	---
4.7.1.2.	Train departures	69

---	---	---
4.7.1.3.	Train arrivals	69

---	---	---
4.7.1.4.	Deviations from scheduled information	69

---	---	---
4.7.2.	Information in the vehicle	70

---	---	---
4.8.	Common reference data for rail ticketing	70

---	---	---
4.9.	Data sharing with other stakeholders	71

---	---	---
5.	List of specific cases	71

---	---	---
5.1.	General	71

---	---	---
5.2.	List of specific cases	71

---	---	---
APPENDIX A	INTERFACES IN RELATION TO OTHER SUBSYSTEMS	72

---	---	---
A.1	Interoperability requirements related to accessibility	72

---	---	---
A.2	Interoperability requirements related to capacity management, train preparation and traffic management	72

---	---	---
A.3	Interoperability requirements related to noise	73

---	---	---
A.4	Interoperability requirements related to control-command and signalling	74

---	---	---
A.5	Interoperability requirements related to energy	74

---	---	---
A.6	Interoperability requirements related to locomotives and passenger rolling stock	74

---	---	---
APPENDIX B	LIST OF OPEN POINTS	75

---	---	---
APPENDIX C	LIST OF REFERENCED STANDARDS AND TECHNICAL DOCUMENTS	76

---	---	---
C.0	Semantic versioning of technical documents	76

---	---	---
C.1	List of common referenced technical documents	76

---	---	---
C.2	List of referenced technical documents specific to data sharing in relation to capacity management, traffic management, and train preparation	77

---	---	---
C.3	List of referenced technical documents to data sharing specific for the management of freight wagons and their load	77

---	---	---
C.4	List of referenced specifications specific to rail ticketing in relation to passenger rail transport services and rail passenger travel information	77

---	---	---
C.4.A	List of referenced standards	77

---	---	---
C.4.B	List of referenced technical documents	79

---	---	---
APPENDIX D	TESTING PROCEDURES FOR COMPLIANCE ASSESSMENT	80

---	---	---
D.1	Self-assessment and evidence-based declaration for individual IT messages	80

---	---	---
D.2	Evaluation of the correctness of self-assessment	80

---	---	---
D.3	Specific testing procedures for rail ticketing	81

---	---	---
D.3.A	Passenger timetable	81

---	---	---
D.3.B	Tariffs	81

---	---	---
D.3.C	Availability check and reservation	81

---	---	---
APPENDIX E	ACCURACY OF FORECAST INFORMATION FOR TRAIN AND FREIGHT WAGON MOVEMENTS	82

---	---	---
APPENDIX F	ESSENTIAL REQUIREMENTS	83

---	---	---
APPENDIX G	IMPLEMENTATION MILESTONES	85

1. COMMON REQUIREMENTS

1.1. Essential requirements

(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.2. Common reference data [^ntr1-L_202600253EN.002801-E0001]

(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.2.1. Organisation reference data

(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.2.2. Location reference data

(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].

1.3. Cybersecurity

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

(a) implement cybersecurity risk-management measures in accordance with Directives (EU) 2022/2555 [^ntr2-L_202600253EN.002801-E0002] and (EU) 2022/2557 [^ntr3-L_202600253EN.002801-E0003] 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];

1.4. Data presentation

(1) The Agency shall ensure semantic versioning of the ERA Ontology referred to in Article 7, the specifications of which are referenced in Appendix C, index [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].

1.5. Data quality criteria

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.5.1. Accuracy

(1) Data shared pursuant to this Regulation shall be recorded once as primary data without any intermediate processing, transformation or aggregation by the data holder, that is to say the telematics stakeholder 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.5.2. Completeness

(1) Before sharing data, the data holder shall ensure that its telematics applications check the completeness and compliance of the data shared against the metadata referred to in Article 8.

(2) The data 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.5.3. Consistency

(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.5.4. Timeliness

(1) Telematics stakeholders shall share up-to-date data.

(2) The data holder shall ensure that its telematics applications enable data updates as soon as they are available. The data holder shall set out response times for enquiries and user types in the detailed specifications of its telematics applications.

(3) The timeliness of the data shall be measured as the percentage of data shared within a specified threshold time frame.

(4) Data timeliness shall comply with threshold requirements laid down for each function by the data holder without prejudice to applicable rules, in particular the rules for the transport of dangerous goods.

1.5.5. Uniqueness

(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 %.

1.6. Compliance assessment

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.7. Telematics applications

(1) Except for the processes referred to in Article 2(1), point (c), for which the specifications set out in Section 4 apply, the application programming interfaces (‘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).

1.7.1. Web user interfaces for capacity management, train preparation and traffic management

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.

1.7.2. Web user interfaces for the management of freight wagons and their load

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.

2. CAPACITY MANAGEMENT, TRAIN PREPARATION, AND TRAFFIC MANAGEMENT

(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.

2.1. Object identifiers

2.1.1. General

(1) The main object identifiers set out in points 2.1.2 to 2.1.7 shall be shared between the different telematics stakeholders involved in a rail transport service, and 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].

2.1.2. Reference train identifier

(1) The objects referred to in points 2.1.3 to 2.1.7 shall be embedded in messages exchanged pursuant to points 2.2 to 2.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.

2.1.3. Train object

(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;

(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.

2.1.4. Path request object

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

2.1.5. Path object

(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.

2.1.6. Route object

(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);

(d) corresponding planned dates according to the working timetable.

2.1.7. Case reference object

(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.

2.2. Strategic management of infrastructure capacity

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.

2.3. Capacity allocation

2.3.1. General

(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.

2.3.2. Path request

(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.

2.3.3. Path details

(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.

2.3.4. Path confirmed

(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.

(4) Upon receipt of the ‘PathDetailsMessage’ confirming the booking, the applicant shall also send this message to the railway undertakings involved in that path and to the lead railway undertaking. In the case of a freight rail transport service, the lead railway undertaking shall forward the confirmation to freight customers.

(5) A train path confirmed by the applicant in accordance with point (1) whose confirmation of receipt has been acknowledged by the receiving infrastructure manager in accordance with point (3) is considered as allocated and corresponding capacity rights are to be considered by both parties as granted.

2.3.5. Path details refused

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

(2) Where the path offered by the infrastructure manager in accordance with point 2.3.3 is refused, the applicant shall send back a ‘PathDetailsRefusedMessage’.

2.3.6. Path cancelled

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

(2) To cancel all or part of a path that has been confirmed in accordance with point 2.3.4, the applicant shall send a ‘PathCanceledMessage’ to the infrastructure manager which is responsible for the capacity rights granted.

2.3.7. Path not available

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

(2) Where a path allocated is no longer available or has been changed, the infrastructure manager responsible for the path allocated shall send a ‘PathNotAvailableMessage’ to the applicant as soon as it becomes aware of such a change.

Reading this document does not replace reading the official text published in the Official Journal of the European Union. We assume no responsibility for any inaccuracies arising from the conversion of the original to this format.

This text is published under EUR-Lex's own terms of reuse, not a Legalize or public-domain licence. EUR-Lex
Creative Commons Attribution 4.0 International (CC BY 4.0)
© European Union, https://eur-lex.europa.eu — Source: EUR-Lex (Publications Office of the European Union). Reused under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence. Only EU legislation published in the printed Official Journal of the European Union is deemed authentic; consolidated texts are reproduced here for documentation purposes and have been reformatted to Markdown.