scope:

This document is applicable to all Network Rail (NR) employees and contractors involved in the installation, alteration and decommissioning of NR's telecoms assets. It covers the requirements for asset data and circuit allocations only and excludes telecoms drawings and other records. A list of the telecoms asset types requiring asset data to be recorded can be found in Appendix A.

Purpose

This standard sets out Network Rail's strategy to:

• Manage telecommunication asset data; and

• Its specification, collection and use.

It supports the Telecommunications Asset Policy (NR/L1/TEL/30102) by:

• supporting the reduction in telecommunication asset safety risk through better informed decision making;

• reducing the overall operational cost of telecommunication assets through increased use of asset data;

• improving the total whole life cost management of telecommunication assets including the initial capital cost of installation, on-going maintenance and lifetime support.

This standard:

• Through the asset information specification, allows a better understanding of the data supply requirements,

• Details a consistent approach to the asset data provided on Network Rail's telecommunications assets.

Having correct asset data in NR's approved asset management system drives preventative maintenance tasking and work arising reporting. It also enables the correct allocation of fault reports and safety related telecoms faults against a specific asset; this also assists in highlighting repetitive failures.

For circuit allocations and supporting infrastructure, if circuits supporting the operational railway are not designated as "live" and clearly identified, then a loss of service will not be detected and reported for attendance by the appropriate maintenance organisation. In addition, any disconnection planning will not be robust and could lead to unexpected loss of service and potential train delays.

The standard sets out the types of telecommunication assets that require data to be held, what information needs to be recorded on an asset and where the data is stored.