Interoperability is a European Commission initiative to promote a single market in the rail sector.
What is interoperability all about?
The Railways (Interoperability) Regulations 2011 (RIR) came into force on 16 January 2012 and implement the EC Directive 2008/57/EC on the interoperability of the UK rail system. They apply to new, major, upgraded or renewed infrastructure and rolling stock. Applicants have to follow a framework and seek an authorisation from us, to place the infrastructure or rolling stock into service.
Approach to authorisations
We have updated our policy document relating to the progressive approach to infrastructure authorisation. This replaces the policy document we published back in 2017.
The policy has been refreshed to reflect the following:
- Inclusion of more relevant examples of the application of the policy;
- Further clarifying the role of parties involved in the process; and
- Refined language and terminology to provide greater consistency.
The refreshed policy document maintains the aims of the original policy– to enable applicants to propose grouping together what would currently be separate authorisation applications into one overall application. In this scenario we will authorise the placing in service of a single structural subsystem once, even where the structural subsystem consists of a number of work packages. This means that for a large project or program of work which is undertaken in separate phases, the applicant can streamline its authorisation process and seek to reduce the need to obtain separate authorisations throughout the duration of the project or program of work.
We will continue to monitor the effectiveness of the policy.
The Directive 2008/57/EC
Consolidated Railways Interoperability Directive 2008/57/EC incorporates the amendments made by Commission Directive 2009/131/EC of 16 October 2009 and Commission Directive 2011/18/EU of 01 March 2011.
Directive 2008/57/EC incorporates requirements originally held in the Railway Safety Directive 2004/49/EC relating to the placing into service of rolling stock. The 2008 Directive was later amended by Directive 2009/131/EC (amending Annex VII) and 2011/18/EU (amending Annexes II, V and VI). The amendments caused the verification procedure for subsystems to split in two parts; an EC verification procedure by a Notified Body and a 'verification procedure in the case of national rules' by a Designated Body. The amendment also split the Control-Command and Signalling subsystem into two new subsystems; trackside CCS and on-board CCS.
What is the purpose of the Directive?
The Railway Interoperability Directive 2008/57/EC sets out the conditions to be met to achieve interoperability within the Community rail system. These conditions are met through the processes of:
- Placing in service
- Operation and maintenance of parts in the system
- Professional qualifications and health and safety conditions of staff who contribute to its operation and maintenance
Generally the Directives aim to:
- ensure common Technical Specifications for Interoperability (TSI's) are applied across Europe's railways;
- establish a common European verification and authorisation process for placing new, upgraded or renewed infrastructure or rolling stock in service; and
- provide a process for putting certain rail components knows as interoperability constituents onto the rail market.
The Railways (Interoperability) Regulations 2011
The Railways (Interoperability) Regulations 2011 transpose the Directive into National Law. RIR 2011 revoked the RIR 2006.There are no transitional provisions.
Some of the key changes from the 2006 regulations include:
- Widening the scope of the authorisation regime, meaning an authorisation is required for the first use of vehicles and infrastructure both on and off the Trans European Network (TEN);
- Changes to the structure and content of technical files;
- Enabling conditions and restrictions to apply to authorisations (this means if an authorisation for all of the UK network is technically impractical this can be taken into account);
- Not to require a mandatory authorisation for vehicles first authorised in another Member State;
- Enable a voluntary process of vehicle authorisation in the UK when a vehicle is already authorised in another Member State;
- Enabling a streamlined "type" authorisation process to obtain an authorisation to place an identical vehicle or subsystem into service;
- A type authorisation for non-vehicles and subsystems;
- A new requirement for owners of infrastructure to publish data on their infrastructure and meet their requirements of an EU infrastructure register specification;
- Ensure owners of vehicles supply data for a vehicle register in line with a European specification;
- An appeal mechanism so an applicant can appeal about a safety authority decision to the Secretary of State. In Northern Ireland, where the safety authority is DRDNI, an appeal can be made to DRDNI; and
- A dispensation provision to enable the use after 31 December 2019 of older vehicles which have been made accessible but which do not fully comply with accessibility standards.
Technical Specifications for Interoperability (TSIs)
Technical Specifications for Interoperability (TSIs) define the technical standards required to satisfy the essential requirements set out in the Directive to achieve interoperability. These requirements include safety, reliability and availability, health, environmental protection and technical compatibility along with others specific to certain subsystems. The development process for TSIs are managed and published by the European Rail Agency (ERA).
The key stages in the process for development of a TSI are:
- Drafting and development of the TSI by the ERA
- Recommendation of the draft TSI by the Railway Interoperability and Safety Committee (RISC)
- Adoption of the TSI in a decision by the European Commission (EC)
- Notification of the EC decision to Member States (by formal letter)
- Publication of the TSI in the Official Journal (OJ) of the European Union
- The TSI 'becoming applicable' (i.e. coming into force)
National Technical Rules (NTRs)
National Technical Rules (NTRs) are those standards which the Directive requires each Member State to notify to the commission where it contains an identified 'open point' or where a derogation from a TSI has been notified. The notified NTRs will not supplement the TSIs on performance related issues, nor repeat requirements instructed by the TSIs.
The Rail Safety and Standards Board (RSSB) is responsible, on behalf of the rail industry, for proposing to the Department for Transport, those standards that should be notified against each of the TSIs for use on the GB mainline. The purpose of the notified NTRs is to provide additional controls to ensure that the essential requirements, as specified in the Directive, are met. Other NTR's are notified in a similar way for all networks including High Speed 1, the Channel Tunnel and Northern Ireland.
How to make an application for authorisation
The Project Entity must seek an authorisation before placing the structural subsystem into service. We grant the authorisation for placing into service (APIS). An application for APIS should be made in respect of any structural subsystem if:
- The authorisation is required under regulation 4(1)- a first authorisation;
- An authorisation is not required under regulation 4(1) as regulation 3(2) or (5)(a) applies, however the person nevertheless wants an authorisation- a voluntary first authorisation;
- An authorisation is not required under regulation 4(1) as regulation 4(1)(c) applies, but the person nevertheless wants an authorisation- a voluntary re-authorisation.
In accordance to regulation 5(2), the Project Entity must make the application to ORR in writing accompanied by the technical file, in accordance with regulation 17(2)(a) and relevant parts of the revised Annex VI of the Directive, and the verification declaration.
The application for authorisation must comply with regulations 4, 15 and 16 of the RIR 2011.
There is no mandatory time limit for us to determine an application or authorisation; however, applicants should build four weeks into their project timescales.