LegalizeCommission Implementing Regulation (EU) 2019/777 of 16 May 2019 on the common specifications for the register of railway infrastructure and repealing Implementing Decision 2014/880/EU (Text with EEA relevance.)
4. HIGH LEVEL SYSTEM OVERVIEW
4.1. Register of infrastructure system
The architecture of the registers of infrastructure system shall be as follows:
4.2. Administration of the RINF application
The RINF application shall be a web-based application set up, managed, maintained and administered by the Agency.
The Agency shall make available to infrastructure managers the following files and documents that shall be used for submitting the data to the RINF application:
(a) user manual;
(b) specification of the structure of the files for the transmission of data;
(c) description of codes for preparing the files — Data provision guide describing the validation process of the transmitted files;
(d) the ERA vocabulary.
4.3. Minimum required functionality of the RINF application
The RINF application shall provide at least the following functionalities:
(a) user management: the Agency must be able to manage users' access rights;
(b) information auditing: RINF application must enable viewing the logs of activity of registered users, connectivity and authentication;
(c) connectivity and authentication: the registered RINF application users must be able to connect to the RINF application via internet and use its functionalities according to their rights;
(d) search for the register of infrastructure data including OPs and/or SoLs, including data validity dates;
(e) visual representation of data of the register of infrastructure allowing publication of thematic maps;
(f) list of tracks of SoLs and OPs which are part of a route defined by the user and export the corresponding characteristics;
(g) deliver a timestamped export file each time the export of characteristics resulting from a search is intended to be used by a railway undertaking in accordance with Article 23(1) of Directive (EU) 2016/797;
(h) application programming interface (API) and/or an open querying endpoint;
(i) validation, upload and reception of the data sets provided by an Infrastructure Manager.
4.4. Operating mode
The register of infrastructure system shall provide three main interfaces via the RINF application:
(a) one to be used by the infrastructure managers in order to submit their set of data;
(b) one to be used by RINF application users in order to connect to the system and retrieve information
(c) one to be used by Railway Undertakings for subscription for notifications of changes in the infrastructure they operate on.
The RINF application central database shall make data provided by infrastructure managers publicly available without any modification.
The basic functionality of the RINF application shall allow users to search and retrieve data of register of infrastructure.
The RINF application shall retain the complete historical record of data made available by the infrastructure managers. Those records shall be stored for two years from the date of withdrawal of the data.
The Agency, as administrator of the RINF application, shall provide access to users upon request. Answers to the queries initiated by the RINF application users shall be provided within 24 hours from the moment the query was initiated. Infrastructure Managers shall be able to keep their data updated directly in RINF, following the specifications of Table 1 and submit it to the RINF application in accordance with Article 5.
Infrastructure Managers shall upload the files to the RINF application through a dedicated interface provided for this operation. A specific module shall facilitate the validation and uploading of data.
4.5. Availability
The RINF application shall be available seven days a week. The unavailability of the system shall be minimal during maintenance.
In the case of failure outside the normal working hours of the Agency, the actions to restore the service shall start the next Agency working day.
5. APPLICATION GUIDE FOR THE COMMON SPECIFICATIONS
The application guide for the common specifications referred to in Article 7 shall be made publicly available by the Agency on its website and updated as appropriate in compliance with the ERA Vocabulary referred to in Article 7a and referenced in Appendix A-1, index [A].
It shall provide extended definitions of all the objects and parameters of the register of infrastructure and guidance on the most common situations and on solutions for modelling the railway network.
It shall contain in particular:
(b) items and their corresponding description as specified as section 3.3 and in Table 1. For each field, at least its format, limit of value, conditions under which parameter is applicable and mandatory, railway technical rules for parameters values, reference to TSIs and other technical documents related to items of the register of infrastructure;
(c) detailed definitions and specifications for parameters;
(d) presentation of provisions for modelling the network and collecting data with relevant explanations and examples;
(e) procedures for validation and submission of data from registers of infrastructure of the Member States to the RINF application.
The application guide shall provide explanations on the specifications referred to in this Annex which are necessary for the proper development of the register of infrastructure system.
Appendix A
A-1 Technical documents (available on ERA website)
| Index | Characteristics to be assessed | RINF point | Mandatory technical document point |
|---|---|---|---|
| [A] | ERA Vocabulary ERA/TD/Vocabulary version 3.0.0 (released on 2023-03-29) | ||
| [B] | ERA Technical Document on codification of combined transport ERA/TD/2023-01/CCT version 1.1 (realased on 2023-03-21) | ||
| [B.1] | Codification of lines | Table 1, 1.1.1.1.3.4 1.1.1.1.3.5 1.1.1.1.3.8 1.1.1.1.3.9 | 2.1 |
| [C] | SUBSET-026 System Requirements Specification TSI CCS, Appendix A, index [4] | ||
| [C.1] | ETCS M_version | Table 1, 1.1.1.3.2.10 1.2.1.1.1.10 | Chapter 7, Section 7.5.1.79 |
| [C.2] | ETCS trackside engineered to transmit Track Conditions | Table 1, 1.1.1.3.2.12 1.1.1.3.2.12.1 1.2.1.1.1.12 1.2.1.1.1.12.1 | Chapter 5, section 5.18.1.1 |
| [C.3] | Cant Deficiency used for the basic Static Speed Profile (SSP) | Table 1, 1.1.1.3.2.14 1.1.1.3.2.14.1 1.2.1.1.1.14 1.2.1.1.1.14.1 | Chapter 7, section 7.5.1.82.1 |
| [C.4] | Rejection of a train by an ETCS Radio Block Center | Table 1, 1.1.1.3.2.15 1.2.1.1.1.15 | Chapter 5, section 5.4 |
| [C.5] | ETCS National Values | Table 1, 1.1.1.3.2.16.1 1.2.1.1.1.16.1 | Chapter 7, section 7.5.1.17 |
| Table 1, 1.1.1.3.2.16.2 1.2.1.1.1.16.2 | Chapter 7, section 7.5.1.123 | ||
| Table 1, 1.1.1.3.2.16.3 1.2.1.1.1.16.3 | Chapter 7, section 7.5.1.161 | ||
| Table 1, 1.1.1.3.2.16.4 1.2.1.1.1.16.4 | Chapter 7, section 7.5.1.163 | ||
| Table 1, 1.1.1.3.2.16.5 1.2.1.1.1.16.5 | Chapter 7, section 7.5.1.15 | ||
| Table 1, 1.1.1.3.2.16.6 1.2.1.1.1.16.6 | Chapter 7, section 7.5.1.149 | ||
| Table 1, 1.1.1.3.2.16.7 1.2.1.1.1.16.7 | Chapter 7, section 7.5.1.16 | ||
| Table 1, 1.1.1.3.2.16.8 1.2.1.1.1.16.8 | Chapter 7, section 7.5.1.148 | ||
| Table 1, 1.1.1.3.2.16.9 1.2.1.1.1.16.9 | Chapter 7, section 7.5.1.74 | ||
| Table 1, 1.1.1.3.2.16.10 1.2.1.1.1.16.10 | Chapter 7, section 7.5.1.75 | ||
| Table 1, 1.1.1.3.2.16.11 1.2.1.1.1.16.11 | Chapter 7, section 7.5.1.122 | ||
| Table 1, 1.1.1.3.2.16.13 1.2.1.1.1.16.13 | — Packet 3 (for M_VERSION above 2.0): Chapter 7, 7.4.2.1.1 — Packet 203 (for M_VERSION 1.1): SRS Chapter 6, 6.5.1.5.22, | ||
| [C.6] | ID and phone number of ERTMS/ETCS Radio Block Center | Table 1, 1.1.1.3.2.17 1.2.1.1.1.17 | Chapter 7, 7.5.1.86, 7.5.1.95 and 7.5.1.96 |
| [C.7] | GSM-R version | Table 1, 1.1.1.3.3.1 1.2.1.1.2.1 | Relevant point(s) |
| [C.8] | Radio Network ID | Table 1, 1.1.1.3.3.13 1.2.1.1.2.13 | Chapter 7, 7.5.1.91.1 |
| [C.9] | ATO System version | Table 1, 1.1.1.3.13.2 1.2.1.1.10.2 | Chapter 1, 1.0.0 |
| [D] | ERA/ERTMS/033281 - V 5.0 Interfaces between Control-Command and Signalling Trackside and other Subsystems TSI CCS, Appendix A, index [77] | ||
| [D.1] | Frequency bands for detection | Table 1, 1.1.1.3.4.2 1.2.1.1.3.2 | Relevant point(s) |
| [D.2] | Vehicle impedance | Table 1, 1.1.1.3.4.2.2 1.2.1.1.3.2.2 | 3.2.2.1 |
| [D.3] | Type of track circuits | Table 1, 1.1.1.3.7.1.2 1.2.1.1.6.1 | Relevant point(s) |
| [D.4] | Type of axle counters | Table 1, 1.1.1.3.7.1.2 1.2.1.1.6.1 | Relevant point(s) |
| [E] | EIRENE FRS GSM-R Functional Requirements Specification TSI CCS, Appendix A, index [32] | ||
| [E.1] | GSM-R version | 1.1.1.3.3.1 1.2.1.1.2.1 | Relevant point(s) |
| [F] | EIRENE SRS GSM-R System Requirements Specification TSI CCS, Appendix A, index [33] | ||
| [F.1] | GSM-R version | 1.1.1.3.3.1 1.2.1.1.2.1 | Relevant point(s) |
A-2 Standards
| Index | Characteristics to be assessed | RINF point | Mandatory technical document point |
|---|---|---|---|
| [1] | EN50163:2004 Supply voltages of traction systems | ||
| [1.1] | Umax2 | Table 1, 1.1.1.2.2.1.3 | Table 1 |
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.