INTEROPERABILITY UNIT RAIL SYSTEM REGISTER OF INFRASTRUCTURE

EUROPEAN RAILWAY AGENCY

File : Registro Infrastrutture IU-RINF-

090211-Spec 0.8.doc

PAGE 1 OF 25

INTEROPERABILITY UNIT

RAIL SYSTEM

REGISTER OF INFRASTRUCTURE

Reference: IU-RINF-090211-Spec 0.8 Document Type :

Specification

Version : Draft

Date : 02/12/2009

Edited by Reviewed by Approved by

Name Jan-Christian ARMS

Maciej SAWICKI

Martin SCHROEDER

Andrzej HARASSEK Jean-Charles PICHANT

Position Project Officers Adviser Head of Unit

Date

&

Signat .

xx/yy/2009 xx/yy/2009 xx/yy/2009

European Railway Agency

Register of Infrastructure

IU-RINF-090211-Spec 0.8 Version Draft /25

AMENDMENT RECORD

Version Date Section number

Modification/description Author

0.1 25/02/2009 All First draft Jan-Christian ARMS

Maciej SAWICKI

Martin SCHROEDER

0.2 26/02/2009

09/03/2009

2-4 Revision after 2nd WG and editorial review

Jan-Christian ARMS

Maciej SAWICKI

0.3 23/04/2009 3-4, Annex A

Revision after 3rd WG Jan-Christian ARMS

0.6 30/10/2009 4, 5 Revision after 5th SG Jan-Christian ARMS

0.8 02/12/2009 5, 6 Revision after 6th WG Jan-Christian ARMS




Table of Contents 1. Introduction........................................................................................... 7

1.1 Background to the assignment............................................................. 7

1.2 Summary ...................................................................................... 7

2. Abbreviations and references ..................................................................... 8

2.1 Abbreviations ................................................................................. 8

2.2 Reference Documents ...................................................................... 9

3. Legal framework....................................................................................11

3.1 Register of Infrastructure and related legislation.......................................11

3.2 Network statement and related legislation ..............................................11

3.3 Comparison ..................................................................................12

4. Purpose and scope ................................................................................13

4.1 Purpose .......................................................................................13

4.1.1 Requirements from the Directive ................................................... 13

4.1.2 Application of the Register of Infrastructure ...................................... 13

4.2 Geographical scope ........................................................................14

4.3 Technical scope .............................................................................14

5. Information indicated in TSIs.....................................................................16

5.1 General procedure ..........................................................................16

5.2 Railway network structure for RINF ......................................................16

5.3 Conventions..................................................................................18

5.3.1 Operational points properties ....................................................... 18

5.3.2 Platforms ............................................................................... 18

5.3.3 Information on open points of TSIs ................................................ 19

5.4 Main features of the Infrastructure subsystem .........................................19

5.5 Main features of the Energy subsystem .................................................19

5.6 Main features of the Control, Command and Signalling subsystem ................19

6. Information on infrastructure indicated in the Network Statement .........................20

7. Format of the register .............................................................................21

8. Management of the register ......................................................................22

9. Instructions for use.................................................................................23

10. Implementation.................................................................................24

Annex A – Items for Register of Infrastructure ...................................................25




Table of Figures Figure 1: Structure of the railway network for the register ............................... 17

Figure 2: Data structure in the Register of Infrastructure................................. 17

Figure 3: Description of operational points .................................................. 18

Figure 4: Platforms for the purpose of RINF ................................................. 19




Table of tables Table 1 : Abbreviations ................................................................................ 8

Table 2 : Reference documents ..................................................................... 9

Table 3 : Comparison of Register of Infrastructure and Network Statement ............... 12




1. Introduction

1.1 Background to the assignment

The activity of the WG ‘Register of Infrastructure’ scheduled in the ERA work programme 2009 [1] is based on Article 18 of Regulation 1335/2008 [2] amending Regulation 881/2004 establishing a European Railway Agency (ERA) and Article 35 (2) of Directive 2008/57/EC [3] on the Interoperability of the Rail System within the Community.

According to the Agency Regulation [2] and the Interoperability Directive [3] the Agency shall draw up and recommend to the Commission a common specification for the Register of Infrastructure, which shall be adopted ‘in accordance with the regulatory procedure referred to in Article 29(3)’. This specification on the Register of Infrastructure shall comprise essential information ‘regarding its presentation and format, revision cycle and instructions for use, taking into account an appropriate transition period for infrastructures placed in service before the entry into force of this Directive.’

The ERA work programme 2009 sets the deadline for the draft of this specification to December 2009.

1.2 Summary




2. Abbreviations and references

2.1 Abbreviations

Table 1 : Abbreviations

Abbreviation Definition

AEIF European Association for Railway Interoperability

(Association Européenne pour l’Interopérabilité Ferroviaire)

BP Basic Parameter

CEN European Committee for Standardisation

(Comité Européen de Normalisation)

CER Community of European Railway and Infrastructure Companies

CCS Control-Command and Signalling

CR Conventional Rail

CSG Conformity Survey Group

DG TREN Directorate-General Energy and Transport

EC European Commission

EIM European Rail Infrastructure Managers

EN European Standards

ENE Energy

ENV European Pre-standard (published for testing)

ERA European Railway Agency (also referred to as Agency)

ERFA European Rail Freight Association

ERTMS European Rail Traffic Management System

HS High-Speed

IC Interoperability Constituent

IG Interface Group

RINF Register of Infrastructure

LOC Locomotives and traction units (abbreviation for loc. and tr. units TSI)

IM Infrastructure Manager

INF Infrastructure

MS Member State

NoBo Notified Body

NB-Rail Coordination Group of Notified Bodies




Table 1 : Abbreviations

Abbreviation Definition

NSA National Safety Authority

OJ Official Journal of the European Union

OPE Operation and traffic management

PAS Passenger Carriages

prEN Draft European Standard

PRM People with reduced mobility

RNE RailNetEurope

RG Restricted Group

RRS Register of Rolling STock

RST Rolling Stock

SRT Safety in Railway Tunnels

TEN Trans-European Networks

TSI Technical Specification for Interoperability

UIP International Union of Private Wagons

UIRR International Union of combined Road-Rail transport companies

(Union Internationale des sociétés de transport combiné Rail-Route)

UITP International Association of Public Transport

(Union Internationale des Transports Publics)

UNIFE Association of the European Railway Industries

(Union des Industries Ferroviaires Européennes)

2.2 Reference Documents

Table 2 : Reference documents

Ref. N° Document Reference Title

[1] AB Decision n° 24/2008 ERA Work Programme 2009

[2] Regulation (EC) No 1335/2008

Amending Regulation (EC) No 881/2004 establishing a European Railway Agency (Agency Regulation)

[3] Directive 2008/57/EC Interoperability of the rail system within the Community

[4] Directive 2001/14/EC Allocation of railway infrastructure capacity and the levying of charges for the use of railway infrastructure and safety certification

[5] Decision 2008/217/EC Technical specification for interoperability relating to the ‘infrastructure’ subsystem of the trans-European high-speed rail system




Ref. N° Document Reference Title

[6] IU-INF-081210-TSI 3.0 Final draft TSI concerning the technical specification for interoperability relating to the ‘infrastructure’ sub-system of the trans-European conventional rail system

[7] Decision 2008/284/EC Technical specification for interoperability relating to the ‘energy’ sub-system of the trans-European high-speed rail system

[8] IU-ENE-090120-TSI 3.0 Final draft TSI concerning the technical specification for interoperability relating to the ‘enegy’ sub-system of the trans-European conventional rail system

[9] Decision 2006/860/EC Technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European high speed rail system

[10] Decision 2006/679/EC Technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European conventional rail system

[11] Decision 2008/231/EC Technical specification of interoperability relating to the operation subsystem of the trans-European high-speed rail system

[12] Decision 2006/920/EC Technical specification of interoperability relating to the subsystem ‘Traffic Operation and Management’ of the trans-European conventional rail system

[13] Decision 2008/163/EC Technical specification of interoperability relating to ‘safety in railway tunnels’ in the trans-European conventional and high-speed rail system

[14] Decision 2008/164/EC Technical specification of interoperability relating to ‘persons with reduced mobility’ in the trans-European conventional and high-speed rail system

[15] Decision 2008/232/EC Technical specification for interoperability relating to the ‘rolling stock’ sub-system of the trans-European high-speed rail system

[16] Decision 2006/861/EC Technical specification of interoperability relating to the subsystem rolling stock — freight wagons of the trans-European conventional rail system

[17] Report RINF WG

[18] RNE Network Statement, Common structure and implementation guide, approved by RNE – WG Network Statement at 30 March 2006




3. Legal framework

3.1 Register of Infrastructure and related legislat ion

Directive 2008/57/EC [3], hereafter referred to as the Interoperability Directive or the Directive, establishes ‘the conditions to be met to achieve interoperability within the Community rail system’. This must lead to an optimal level of technical harmonisation to:

• facilitate, improve and develop international rail transport services within the European Union (Article 1 (2a))

• contribute to the interoperability of the rail system within the Community (Article 1 (2c)).

The Interoperability Directive sets out in Article 35 (1) the obligation for Member States ‘to ensure that a Register of Infrastructure is published and updated on the basis of a revision cycle’ to be defined in this specification. This register shall ‘indicate the main features of each subsystem or part subsystem involved (e.g. the basic parameters) and their correlation with the features laid down under and precisely indicated in the applicable TSIs’.

Article 19 (1) of the Agency Regulation [2] gives requirements for the accessibility of documents and registers. According to point (h) ‘The Agency shall make publicly accessible ...the link to the registers of infrastructure’.

All future references to ‘Articles’ in this document refer to the Interoperability Directive 2008/57/EC, unless stated.

3.2 Network statement and related legislation

In addition to the Register of Infrastructure required by the Interoperability Directive [3], Directive 2001/14/EC [4] introduces the requirement for a ‘Network Statement’.

Article 1 (1) of Directive 2001/14/EC ‘concerns the principles and procedures to be applied with regard to the setting and charging of railway infrastructure charges and the allocation of railway infrastructure capacity’. It ‘applies to the use of railway infrastructure for domestic and international rail services’ (Article 1 (2)).

Article 3 of Directive 2001/14/EC sets out the requirements for a network statement. The IM shall ‘publish a network statement obtainable against payment’ not exceeding the publication costs. It shall set out ‘the nature of the infrastructure which is available to railway undertakings’ and ‘the conditions for access to the relevant railway infrastructure’. Publication of the network




statement shall be at least ‘four months in advance of the deadline for requests for infrastructure capacity’.

3.3 Comparison

A comparison of European legislation as described in sections 3.1 and 3.2 identifies differences between Registers of Infrastructure and Network Statements as shown in table 3.

Table 3 : Comparison of Register of Infrastructure and Network Statement

Register of Infrastructure (2008/57/EC)

Network Statement

(2001/14/EC)

Scope of Directive Optimal level of technical structural and functional harmonisation leading to interoperability

Railway infrastructure charging and capacity allocation

Application (geographical

scope)

Community rail system Infrastructure for domestic and international rail services

Publication Member State shall ensure publication

Infrastructure Manager shall publish

Availability and Revision cycle

To be defined four months in advance of the deadline for requests for infrastructure capacity

Structure Specification regarding its presentation and format, revision cycle and instructions for use

Annex I of 2001/14/EC mentions three sections of the document

Requirements for presentation, format and instructions for

use

mandated not mandated

Both public sources of information about railway infrastructure mandated in two European Directives as compared in table 3 show different legal requirements. For those reasons the Register of Infrastructure and the Network Statement cannot be merged or treated as a single document.

However, there is a certain overlap regarding technical items describing railway infrastructure. Directive 2008/57/EC links the content of RINF to the functional description of the subsystem (BPs while Directive 2001/14/EC requires for a section describing the nature of infrastructure. Chapter 7 of this specification describes a possible handling of both public sources taking account of the items in question and avoiding their double handling.




4. Purpose and scope

4.1 Purpose

4.1.1 Requirements from the Directive

The requirements for the purpose of the Register of Infrastructure in this section are derived from the Interoperability Directive [3] and are listed in their order in which they appear within the Directive.

Article 1 (‘Purpose and scope’) is generally valid for the Register of Infrastructure required by the Directive. It must support technical harmonisation to ‘facilitate, improve and develop international rail transport services’ and ‘contribute to the interoperability of the rail system’.

Article 17 (3) (‘Conformity with TSIs and national rules’) permits MSs to choose not to notify rules and restrictions of strictly local nature. However it is a requirement that in such cases, the MS ‘...shall mention such rules and restrictions in the infrastructure registers...’.

Article 18 (2) (‘Procedure for establishing EC declaration of verification’) requires the task of the NoBo responsible for the ‘EC’ verification of a subsystem to cover the ‘verification of the interfaces of the subsystem in question with the system into which it is incorporated, based on the information available in the relevant TSI and in the registers.

Article 35 (1) (‘Register of Infrastructure’) requires each Member State to ensure that a register of infrastructure is published and updated on the basis of the revision cycle. The register shall indicate the main features of each subsystem or part of subsystem involved (e.g. the basic parameters) and their correlation with the features laid down under the applicable TSIs and therefore each TSI shall indicate precisely what information must be included in the register of infrastructure.

Article 39 (3) (‘Reports and information’) requires the Agency to develop and update a tool capable of providing a chart on the interoperability level of the rail system. ‘That tool shall use the information included in the registers’ provided for in the Directive.

4.1.2 Application of the Register of Infrastructure

This section considers the expectations of the railway sector in the interpretation of the requirements of the Interoperability Directive.

The conformity assessment for EC verification of a subsystem by the NoBo is established by the TSIs including the interfaces between subsystems. The




NoBo shall check the interfaces using RINF in accordance with the requirements of the relevant TSI and article 18 (2).

The procedure for placing rolling stock into service following the EC declaration of verification described in Article 15 (1), asks the MS to ensure that this is only possible by meeting the essential requirements when ‘integrated into the rail system’. In particular ‘ the technical compatibility of these subsystems with the systems into which they are being integrated’ shall be assessed. The RINF will enable and expedite the assessment of technical compatibility for Rolling Stock designated and put into service for a specific area of infrastructure and the technical compatibility between the other subsystems.

Rolling Stock conforming to the Rolling Stock TSIs is not automatically compatible with all lines conforming to the Infrastructure TSI. Both TSIs provide for choices, including the basic parameters forming an interface between the subsystems such as the harmonised European structure and vehicle gauges. For example, a GC gauge vehicle is not compatible with a GB gauge tunnel. The use of registers will facilitate this compatibility assessment for the capability of a vehicle to run on a specific line, which is outside of the EC verification procedure for planning purposes.

The Register of Infrastructure will be used as a core reference by the Agency to track progress towards a European interoperable Network as provided for in Article 39 (2). At the same time it will provide useful information for the railway sector about the current technical characteristics of European infrastructure for the development of new products and services. This is also needed for upgraded and renewed RST, to check that modifications will not have a negative impact on the area of use.

The Register of Infrastructure can also be used as an initial tool for considering cross-acceptance of vehicles, especially existing vehicles which have not been EC verified.

4.2 Geographical scope

The geographical scope of RINF is the Community rail system stated in Article 1 (1) of the Directive, taking into account possible exclusions. It may include lines excluded by MSs but which are connected to the Community rail system, in line with the Directive (limited set of data).

4.3 Technical scope

The technical scope of RINF in correlation with the features laid down under the applicable TSIs have currently been assessed for the TEN only. The




geographical scope of RINF (as described in section 4.2) and the technical scope of the TSIs are therefore not consistent. The future extension of the scope of the TSIs to the Community rail system will consequently have an influence on the specification of RINF.

Features for RINF are laid down under the following applicable TSIs and respectable sections thereof:

• Infrastructure subsystem of the trans-European high-speed rail system, Annex D [5]

• Infrastructure subsystem of the trans-European conventional rail system, Annex D [6]

• Energy subsystem of the trans-European high-speed rail system, Annex D [7]

• Energy subsystem of the trans-European conventional rail system, Annex C [8]

• Control-command and signalling subsystem of the trans-European high speed rail system, Annex C [9]

• Control-command and signalling subsystem of the trans-European high speed rail system, Annex C [10]

• Traffic Operation and Management of the trans-European high-speed rail system, Annex D [11]

• Traffic Operation and Management of the trans-European conventional rail system, Annex D [12]

• Safety in railway tunnels in the trans-European conventional and high-speed rail system, Annex A [13]

• Persons with reduced mobility in the trans-European conventional and high-speed rail system, section 4.1.8 [14]

• Rolling stock sub-system of the trans-European high-speed rail system, section 4.8.1 [15]

• Subsystem rolling stock — freight wagons of the trans-European conventional rail system, Annex KK [16]




5. Information indicated in TSIs

5.1 General procedure

Chapter 5 aims at specifying the set of items required for RINF in the view of its purpose (see section 4.1.2 of this specification). The TSIs listed in section 4.3 have been drafted at different times and under the responsibility of various working groups. There was not a clear and single view of the registers at those times, which led to subsystem specific sets of items.

Subsequently it was necessary to harmonise the information when putting it together to get a consistent set of items. The RINF WG has selected a subset of information deemed to be necessary to satisfy the requirements of the Directive, which is given in Annex A to this specification. More information and reasons for this selection can be taken from the report [17] accompanying the RINF specification.

Annex A sets out for each item the content to be reported, its unit of measurement and type of data. It has to be stated, that for specific information a distinction is necessary between lines verified against a TSI and existing lines. Those lines, whether TEN or off-TEN lines, have not been built to harmonised rules, so that other limit values have to be reported.

5.2 Railway network structure for RINF

For the purpose of RINF

• the railway network is considered to be a series of operational points connected by sections.

• a line is a sequence of one or more sections, which may consist of several tracks

• operational points are locations for train service operations for example where train services can begin and end, change route and where passenger or freight services are provided

• stopping points for passengers on plain line are also regarded as operational points

• operational points may be locations where basic parameters of a subsystem are changing

• sidings on plain line (passing loops) or track connections only required for train operation do not need to be published (otherwise they are considered to be operational points and need to be included)




Figure 1 shows an example of the railway network structure of RINF, the elements of which belonging to different IMs.

Line 2

Figure 1: Structure of the railway network for the register

Article 35 (1) of the Interoperability Directive requires MS to ensure the publication of the register. According Article 19 [2] the Agency shall make the links to the Registers of Infrastructure publically available.

Consequently information in RINF will be arranged at the highest level per Member State as displayed in figure 2.

Figure 2: Data structure in the Register of Infrastructure

The next lower level is separated according to the structure of the railway network in section and operational point.

Different elements of the infrastructure belong to section or operational point. Different parameters of several subsystems (TSIs) are assigned to those




elements following the relevant requirements. For example, information about the INF subsystem for sidings differs to a large extent to the INF data for main tracks.

The values of the parameters to take into consideration checking the compatibility between the rolling stock and the rest of the subsystems will be the most restrictive of the sections where the vehicle runs.

The name of IM and the line identification are assumed to be parameters of each single element of sections or operational points.

5.3 Conventions

5.3.1 Operational points properties

For the purpose of RINF, generally it is assumed, that the point where two sections meet is the location of the operational point.

Usually technical information linked to tracks of a section is also valid for the related main tracks of the operational point, therefore it is not necessary to publish it for the operational point. In case of having more restrictive values of the parameters between a section and the operational point next to it, this technical data will be published also for the operational point.

Figure 3: Description of operational points

5.3.2 Platforms

Locations where passenger services are provided for the purpose of RINF are classified as operational points. Information on platforms in the RINF data structure exists therefore only for operational points. A separate set of information is given for each platform edge related to the respective track. Figure 4 displays the example of a middle platform consisting of two platform edges.




Figure 4: Platforms for the purpose of RINF

5.3.3 Information on open points of TSIs

Open points in TSIs are basic parameters important for interoperability for which no harmonised specification yet exists. National rules apply as long as the open points will be closed when revising TSIs.

Provisions for open points will be introduced in RINF to give the possibility for publishing national rules. The data will have to be updated when harmonised rules have been developed.

5.4 Main features of the Infrastructure subsystem

Features of the INF subsystem to be recorded in RINF are specified in the INF and OPE TSIs, the SRT and PRM TSI and in the HS RST and CR WAG TSI [5, 6 and 11 to 16].

All items listed in those technical specifications sum up together to a number of 124 parameters, a certain number of which is mentioned in several documents. The whole list of items is given in the report [17] accompanying this RINF specification. A set of 25 parameters have considered to be necessary for RINF corresponding its purpose. The origin(s) of all parameters and reasons to include or exclude them are reported in [17].

5.5 Main features of the Energy subsystem

5.6 Main features of the Control, Command and Signa lling subsystem




6. Information on infrastructure indicated in the Network Statement A comparison of European legislation in section 3.3 of this specification compared the differences between RINF and the Network Statement concluding that both documents cannot be merged or treated as a single document.

However technical information on infrastructure is to a certain extent similar in both specifications. A common structure for implementing the Network Statement has been set up and published by RailNetEurope (RNE) in 2006 [18] as a voluntary guideline. Missing a mandated guideline, content and structure of the Network Statement published may vary between IMs.

The RNE guide specifies in chapter 3 details about the implementation of technical infrastructure data. Annex B to this specification shows the comments of the RINF WG on the level of compliance in detail of this information to the one set out for RINF.

Main headings of the implementation guide in chapter 3 are as follows:

1) Introduction

2) Extent of network

3) Network description

4) Traffic restrictions

5) Availability of the infrastructure

6) Passenger terminals

7) Freight terminals

8) Service facilities

9) Infrastructure development

Information related to headings 1 to 4 concerning technical characteristics of the network is generally available in RINF, much more detailed in most of the cases. Headings 5 to 8 detail information for customers linked to operation or commercial issues for specific locations of the network outside the scope of RINF. Development of infrastructure allows a view to future network improvements, while RINF demonstrates the actual abilities of the infrastructure.

In order to avoid data discrepancies and with respect to the level of consistence of information on technical characteristics published in both documents, the Network Statement could refer to RINF for information belonging to headings 1 to 4.




7. Format of the register Unit of measurement, Structure, language, Values for information,

interface to Rolling stock register




8. Management of the register Presentation, update, exchange of information (output of data),

interfaces (e.g. dream)

To limit the amount of work needed to create and maintain the register




9. Instructions for use Not for operational purposes, responsibilities and liability, availability

(conditions), consistency and management of documents (TSIs),

change control management




10. Implementation transition period before entry into force of the Directive (existing lines

regardless of TEN), planning of implementation, European publication,

focus on business needs to begin with important European corridors,

difference of scope between RINF and TSIs

The revision cycle of the register shall guarantee updated data for existing line. It shall also specify for new lines the process to establish the register (time plan …)

Save as far as possible the capital investment, which has been executed

Existing network not TSI compliant

TSIs are either TEN HS or TEN CR

Danger that some BPs are missing to cover the whole rail system

glossary of terms




Annex A – Items for Register of Infrastructure

INTEROPERABILITY UNIT RAIL SYSTEM REGISTER OF INFRASTRUCTURE

Documents

Transcript of INTEROPERABILITY UNIT RAIL SYSTEM REGISTER OF INFRASTRUCTURE