# Commission Implementing Decision of 26 November 2014 on the common specifications of the register of railway infrastructure            and repealing Implementing Decision 2011/633/EU (notified under document C(2014) 8784) (Text with EEA relevance) (2014/880/EU)            (repealed)         

        - Previous
        - Next

U.K.

# Commission Implementing Decision

# of 26 November 2014

# on the common specifications of the register of railway infrastructure and repealing Implementing Decision 2011/633/EU

# *(notified under document C(2014) 8784)*

# (Text with EEA relevance)

# (2014/880/EU) (repealed)

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to Directive 2008/57/EC of the European Parliament and of the Council of 17 June 2008 on the interoperability                           of the rail system within the Community(1), and in particular Article 35(2) thereof,                        

Whereas:

(1)On the basis of Article 35 of Directive 2008/57/EC, the Commission adopted Implementing Decision 2011/633/EU(2).

(2)On the basis of a recommendation of the European Railway Agency (the Agency), complementary common specifications are needed                              to make data of the registers easily accessible. These registers should be made available for consultation via a computerised                              common user interface set up and managed by the Agency. Member States, with the help of the Agency, should cooperate to ensure                              that the registers are operational, contain all the data and are interconnected.

(3)Implementing Decision 2011/633/EU should therefore be repealed.

(4)The measures provided for in this Decision are in accordance with the opinion of the Committee established in accordance with                              Article 29(1) of Directive 2008/57/EC.

HAS ADOPTED THIS DECISION:

# Article 1U.K.

1.The common specifications for the register of railway infrastructure as referred to in Article 35 of Directive 2008/57/EC                        are set out in the Annex to this Decision*.*                  

2.The registers of infrastructure of Member States shall be made available for consultation via a common user interface set                        up and managed by the Agency.                  

3.The common user interface referred to in paragraph 2 shall be a web-based application facilitating access to the data contained                        in the registers of infrastructure. It shall be operational not later than 15 days after the date of application referred                        to in Article 8.                  

# Article 2U.K.

1.Each Member State shall ensure that its register of infrastructure is computerised and fulfils the requirements of the common                        specifications referred to in Article 1 not later than eight months after the date of application.                  

2.Member States shall ensure that their registers of infrastructure are interconnected and connected to the common user interface                        eight months after that interface becomes operational at the latest.                  

# Article 3U.K.

The Agency shall publish a guide on the application of the common specifications for the register of infrastructure not later                     than 15 days after the date of application and shall keep it up to date. This application guide shall provide, if appropriate,                     a reference to the relevant provisions of the Technical Specifications of Interoperability (TSIs) for each parameter.                  

# Article 4U.K.

When progress in the development of TSIs or in the implementation of the registers of infrastructure so requires, the Agency                     shall recommend updates of the common specifications.                  

# Article 5U.K.

1.Member States shall ensure that the necessary data are collected and inserted in their registers of infrastructure in accordance                        with paragraphs 2 to 6. They shall ensure that these data are reliable and up to date.                  

2.Data relating to infrastructures for freight corridors defined in the Annex to Regulation (EU) No 913/2010 of the European                        Parliament and of the Council(3) in the version in force on 1 January 2013 shall be collected and inserted in the register of infrastructure not later than                        9 months after the date of application.                  

3.Data relating to infrastructures placed in service after the entry into force of Directive 2008/57/EC and by the date of application                        of this Decision at the latest, other than the data referred to in paragraph 2, shall be collected and inserted in the national                        register of infrastructure not later than nine months after this date.                  

4.Data relating to infrastructures placed in service before the entry into force of Directive 2008/57/EC, other than the data                        referred to in paragraph 2, shall be collected and inserted in the register of infrastructure in accordance with the national                        implementation plan referred to in Article 6(1) by 16 March 2017 at the latest.                  

5.Data relating to private sidings placed in service before the entry into force of Directive 2008/57/EC shall be collected                        and inserted in the register of infrastructure in accordance with the national implementation plan referred to in Article                        6(1) by 16 March 2019 at the latest.                  

6.Data relating to network not covered by TSIs shall be collected and inserted in the register of infrastructure in accordance                        with the national implementation plan referred to in Article 6(1) by 16 March 2019 at the latest.                  

7.Data relating to infrastructures placed in service after the entry into force of this Decision shall be inserted in the register                        of infrastructure as soon as the infrastructures are placed into service and as soon as the common user interface becomes                        operational.                  

# Article 6U.K.

1.Each Member State shall draft a national plan and a timetable for the implementation of the obligations referred to in Article                        5. It shall notify any delays or difficulties to fulfil the provisions of art 5 and the Commission shall grant, where appropriate,                        an extension to the deadline foreseen. The national implementation plan shall be submitted to the Commission not later than                        six months after the date of application.                  

2.Each Member State shall nominate an entity in charge of setting up and maintaining its register of infrastructure and notify                        the Commission thereof not later than three months after the date of application.                  

These entities shall send to the Agency three months after the date of their notification and henceforth every four months,                     a progress report on the implementation of the register of infrastructure.                  

3.The Agency shall coordinate, monitor and support the implementation of the registers of infrastructure. It shall set up a                        group composed of representatives of the entities in charge of setting up and maintaining the registers of infrastructure                        and coordinate its works. The Agency shall regularly report to the Commission on progress in implementing this Decision.                  

# Article 7U.K.

Commission implementing Decision 2011/633/EU is repealed with effect from the date of application set out in Article 8.

# Article 8U.K.

This Decision shall apply from 1 January 2015.

# Article 9U.K.

This Decision is addressed to the Member States and to the European Railway Agency.

Done at Brussels, 26 November 2014.

*For the Commission*                            

Violeta Bulc                            

*Member of the Commission*                            

## ANNEXU.K.

### 1.**INTRODUCTION**U.K.

#### 1.1.**Technical scope**U.K.

##### 1.1.1.This specification concerns data about the following subsystems of the Union rail system:U.K.

the infrastructure structural subsystem,

the energy structural subsystem, and

the trackside control-command and signalling subsystem.

##### 1.1.2.These subsystems are included in the list of subsystems in Annex II (1) to Directive 2008/57/EC.U.K.

#### 1.2.**Geographical scope**U.K.

The geographical scope of this specification is the European Union rail system as determined by Directive 2008/57/EC. It excludes                     the cases referred to in Article 1(3) of Directive 2008/57/EC.                  

### 2.**PURPOSE**U.K.

#### 2.1.**General**U.K.

The main purpose of the register of infrastructure provided for in article 35 of Directive 2008/57/EC (RINF) is to provide                     transparency on the characteristics of the network. The information provided by the RINF is used for planning purposes in                     designing new trains, for assisting the assessment of compatibility of trains with routes before the start of operation and                     for use as a reference database. Therefore the RINF supports the processes described hereafter.                  

#### 2.2.**Designing Rolling Stock subsystems**U.K.

Parameters from the RINF shall be used to identify infrastructure characteristics for the intended use of the rolling stock.

#### 2.3.**Ensuring technical compatibility for fixed installations**U.K.

##### 2.3.1.The notified body checks the conformity of the subsystems with the applicable TSI(s). Verification of interfaces for technical                        compatibility with the network into which a subsystem is incorporated may be ensured by consulting the RINF.U.K.

##### 2.3.2.The body designated by each Member State checks the conformity of the subsystems when national rules apply and the RINF may                        be consulted to verify the interfaces for technical compatibility in these cases.U.K.

#### 2.4.**Monitoring progress of interoperability of the European Union railway network**U.K.

Transparency about the progress of interoperability shall be ensured to monitor regularly the development of a European Union                     interoperable network.                  

#### 2.5.**Ascertaining route compatibility for proposed train service**U.K.

##### 2.5.1.Compatibility with the route for the proposed train service is checked before the railway undertaking procures access to the                        network from the infrastructure manager. The railway undertaking must be sure that the route intended to be used is capable                        of supporting its train.U.K.

##### 2.5.2.The railway undertaking chooses vehicles considering any restrictions on the authorisation for placing in service and a possible                        route for the train intended to run:U.K.

all vehicles in the train must comply with the requirements applicable on the routes over which the train will run and

the train as a combination of vehicles must comply with the technical constraints of the route concerned.

### 3.**COMMON FEATURES**U.K.

The features set out in this Annex are common to all registers of infrastructure of the Member States.

#### 3.1.**Definitions**U.K.

For the purpose of these specifications:

‘section of line’ (SoL) means the part of line between adjacent operational points and may consist of several tracks;

‘operational point’(OP) means any location for train service operations, where train services may begin and end or change                              route and where passenger or freight services may be provided; ‘operational point’ means also any location at boundaries between                              Member States or infrastructure managers;                           

‘running track’ means any track used for train service movements; passing loops and meeting loops on plain line or track connections                              only required for train operation are not published;                           

‘siding’ means any track within an operational point, which is not used for operational routing of a train.

#### 3.2.**Railway network structure for the RINF**U.K.

##### 3.2.1.For the purpose of the RINF, each Member State shall subdivide its railway network into sections of line and operational points.U.K.

##### 3.2.2.Items to be published for ‘section of line’ related to infrastructure, energy and track-side control-command and signalling                        subsystems shall be assigned to the infrastructure element ‘running track’.U.K.

##### 3.2.3.Items to be published for ‘operational point’ related to infrastructure subsystem shall be assigned to the infrastructure                        elements ‘running track’ and ‘siding’.U.K.

#### 3.3.**Items for the RINF**U.K.

##### 3.3.1.Items and format of items shall be published in accordance with the Table.U.K.

##### 3.3.2.The RINF Application Guide referred to in Article 3 shall define the specific format and the governance process of the data                        listed in the Table presented as:U.K.

a single or multiple selection from a predefined list,

a CharacterString or the predefined CharacterString or

a number indicated inside square brackets

##### 3.3.3.All parameters of the RINF are mandatory unless otherwise specified in the Table. Any information relevant to the parameters                        is provided in the Table.U.K.

###### *Table*

**Items for the Register of Infrastructure**

### 4.**HIGH LEVEL SYSTEM OVERVIEW**U.K.

#### 4.1.**RINF system**U.K.

The architecture of the RINF system is presented in the Figure.

##### *Figure***RINF system**U.K.

#### 4.2.**Administration of the Common User Interface**U.K.

The common user interface (CUI) shall be a web based application set up, managed and maintained by the Agency.

The Agency shall make available to the NREs the following files and documents to be used for the setting up of the registers                     of infrastructure and connecting them with the common user interface (CUI);                  
          -  User manual; 
          -  Specification of the structure of the files for the transmission of data. 

The Agency shall make available to the RINF users an Application Guide describing the way the registers of infrastructure                     of each Member States are to be connected to the CUI and the functionalities and utilities provided by the CUI. Where appropriate,                     this guide will be updated.                  

#### 4.3.**Minimum required functionality of the CUI**U.K.

The CUI shall provide at least the following functionalities:
          -  User Management: the CUI administrator must be able to manage users' access rights. 
          -  Information Auditing: the CUI administrator must be able to view the logs of all user activity performed on the CUI as a list                           of the activities that have been performed by CUI users within a particular timeframe.                         
          -  Connectivity and Authentication: the registered CUI users must be able to connect to the CUI via internet and use its functionalities                           according to their rights.                         
          -  Search for RINF data including OPs and/or SoLs with particular RINF characteristics. 
          -  Select an OP or a SoL and view its RINF details: the CUI users must be able to define a geographical area using the map interface                           and the CUI provides the available RINF data requested by the users for this area.                         
          -  View RINF information for a specified subset of lines and OPs in a defined area via a map interface. 
          -  Visual Representation of RINF items on digital map: the users, through the CUI, must be able to navigate, select an item depicted                           on the map and retrieve any relevant RINF information.                         
          -  Validation, Upload & Reception of the full RINF data sets provided by a national register entity. 

#### 4.4.**Operating mode**U.K.

The RINF system provides two main interfaces via the CUI:
          -  One is used by the register of infrastructure of each Member State in order to provide/upload copies of their full RINF data; 
          -  The other is used by CUI users in order to connect to the RINF system and retrieve RINF information. 

The CUI central database will be fed with copies of the full sets of RINF data maintained at the register of infrastructure                     of each Member State. In particular, NREs shall undertake the responsibility to create files that encapsulate the full set                     of RINF data available in their register of infrastructure following the specifications of the Table of this Annex. They shall                     make regular updates, at least every three months, of items that are in their register of infrastructure. One update should                     coincide with the annual publication of the Network Statement.                  

Then NREs shall upload the files to the CUI through a dedicated interface provided for this operation. A specific module will                     facilitate the validation and uploading of data provided by NREs.                  

The CUI central database shall make data sent by NREs publicly available without any modification.

The basic functionality of the CUI shall allow users to searches and retrieves RINF data.

The CUI shall retain the complete historical record of all the data made available by NREs. Those records shall be stored                     for 2 years from the date of withdrawal of the data.                  

The Agency, as administrator of the CUI, shall provide access to users upon request.

Answers to the queries initiated by the CUI users shall be provided within 24 hours from the moment the query was initiated.

#### 4.5.**Availability**U.K.

The Common User Interface shall be available 7 days a week, from 02:00 GMT — 21:00 GMT, depending on daylight savings time.                     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**U.K.

The application guide for the common specifications referred to in Article 3 of this Decision shall be made publicly available                     by the Agency on its website. It shall contain:                  

items and their corresponding data as specified as section 3.3 and in the Table. 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 as set out in the Table of this Decision;                           

detailed definitions and specifications for concepts and parameters;

presentation of provisions for modelling the network for the purpose of RINF and collecting data with relevant explanations                              and examples;                           

procedures for validation and submission of RINF data from registers of infrastructure of the Member States to the CUI.

The Application Guide shall provide explanations on the specifications referred to in the Annex to this Decision which are                     necessary for the proper development of the RINF system.                  

1

OJ L 191, 18.7.2008, p. 1.                           

2

Commission Implementing Decision 2011/633/EU of 15 September 2011 on the common specifications of the register of railway                              infrastructure (OJ L 256, 1.10.2011, p. 1).                           

3

Regulation (EU) No 913/2010 of the European Parliament and the Council of 22 September 2010 concerning a European rail network                              for competitive freight (OJ L 276, 20.10.2010, p. 22).