UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

close
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

close
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

NR/L2/RSE/100/03

Network Rail Assurance Panel Processes: The Application of the Interoperability Regulations for Insfrastructure Projects

active, Most Current
Buy Now
Organization: NR
Publication Date: 5 December 2015
Status: active
Page Count: 23
scope:

This standard specifies the process to be followed by projects to obtain an authorisation under the Railway (Interoperability) Regulations.

NOTE: For instances where an ISV is required but not an authorisation or working in compliance with the relevant TSI, projects with clearly defined stages of configuration outputs can precede with the process of authorisation as stated in section 4.5. A migration strategy should be prepared in conjunction with the PAS/SD as this will formulate the final authorisation for putting into use

It applies:

a) where an infrastructure project requires an authorisation but Network Rail is not the project entity;

b) where another contracting entity contracts works to Network Rail and requires them to undertake the role of project entity;

c) to the introduction of new or major modifications of rolling stock including wagons or other specialist vehicles (yellow plant in train formations) permitted to run on the mainline railway

NOTE 1 NR/L2/RSE/100/04 provides requirements on the introduction of new or modified vehicles.

NOTE 2 Network Rail Yellow Fleet follow all Vehicle Compatibility requirements if moving under its own power.

NOTE 3 NR/L2/RSE/100/02 specifies the process to comply with the Common Safety Method for Risk Evaluation and Assessment.

NOTE 4 Guidance for Sponsors on Railway (Interoperability) Regulations is available in the Sponsors Handbook.

NOTE 5 Projects should note that the essential requirements for Interoperability are specified in the relevant TSI and in other supporting documents, specified in Appendix B. The complete set of requirements should be demonstrated as 'met' in the Technical File.

Purpose

This standard allows Network Rail to comply with Commission Recommendation 2014/897/EU on the authorisation for the placing in service of structural subsystems and vehicles. For the structural subsystems concerned refer to the TSI Matrix in Appendix B.

NOTE 1 Conformance with this standard will not enable full compliance with the legislation referenced in the standard. Users are advised to consult legislation and associated guidance available from the European Railway Agency (ERA), the Office of Rail and Road (ORR) and the Rail Safety and Standards Board (RSSB).

The standard is part of a suite of processes governed by Network Rail Assurance Panel (NRAP) to provide appropriate review prior to projects, products and vehicles being placed into service. The other modules in the suite are:

NR/L2/RSE/100/01 Network Rail Assurance Panel

NR/L2/RSE/100/02 Application of the Common Safety Method for Risk Evaluation and Assessment

NR/L2/RSE/100/04 Introduction of new or modified vehicles

NR/L2/RSE/100/05 Product introduction and change to Network Rail operational infrastructure

NR/L2/RSE/100/06 How to decide what needs product acceptance via NR/L2/RSE/100/05

NR/L2/RSE/100/07 System Review Panels

Document History

NR/L2/RSE/100/03
December 5, 2015
Network Rail Assurance Panel Processes: The Application of the Interoperability Regulations for Insfrastructure Projects
This standard specifies the process to be followed by projects to obtain an authorisation under the Railway (Interoperability) Regulations. NOTE: For instances where an ISV is required but not an...
December 3, 2011
Acceptance Panel Processes: Compliance with Interoperability Regulations for Infrastructure Projects
This module specifies the process to be followed if NRAP have indicated that an infrastructure project might be interoperable. It also applies where a project might be interoperable but Network Rail...

References

Advertisement