NR/L1/XNG/100/06
Level Crossing Asset Policy: Level Crossing Asset Data and Information
Organization: | NR |
Publication Date: | 7 March 2020 |
Status: | active |
Page Count: | 14 |
scope:
2.1 General
The scope of this module includes:
a) any data or information used for the management of level crossings through the lifecycle of the level crossing asset system including, creation, renewal,
operation and maintenance, decommissioning and disposal ;
b) any data or information used to inform level crossing investment decisions or work bank planning;
c) any data or information collected through census or monitoring of level crossing usage; and
d) any data or information used for the purpose of internal or external corporate reporting in the area of level crossings.
NOTE: Auxiliary or complimentary systems associated with level crossings that have no direct interface to the signaller, user or signalling system in the management and control of level crossings
are also considered within scope of the module e.g. Red Light Safety Cameras, event recording systems, surveillance camera systems and census recording systems.
This module focuses on five key areas:
a) data capture and collection including definition and quality standards;
b) data and information ownership, maintenance, management and governance;
c) the migration of locally held and /or unstructured data and information to corporate data formats and systems.
d) data and information processes and system tools; and
e) data and information security.
2.2 Roles and Responsibilities
This module applies to:
a) Route Level Crossing Managers;
b) Route Asset Managers [Track and Lineside], [Signalling] and [Electrical Power];
c) equivalent posts in Network Rail Telecom;
d) operational posts responsible for the management of risk of the level crossing estate;
e) all Network Rail staff responsible for the management of level crossing asset data and Route defined roles responsible for the management of asset data.
ISO 8000 specifies 3 generic data roles across three processes.
Purpose
This module sets out Network Rail's strategy to:
a) manage level crossing data and information; and
b) its specification, collection and use.
It supports the level crossing asset policy by:
a) supporting the reduction in level crossing safety risk through better decision making;
b) reducing the overall operational cost of level crossings through increased use of asset data information;
c) reducing the overall total whole life cost of level crossings including initial capital cost of installation, on-going maintenance and lifetime support; and
d) moving reliance for the management of level crossings from people to technology.
NOTE: This includes the migration of locally held unstructured data and information into corporate systems.
The module:
a) provides clarity about Network Rail's strategy and intentions in the area of level crossing data and information management;
b) gives broad guidance to suppliers and potential suppliers of level crossing technology, informing their asset management plan and investments in
product development;
c) through the asset information specification, allow a better understanding of asset data supply requirements;
d) sets out ownership, accountabilities and governance for level crossing asset data and information reporting in a devolved business model between
operationally accountable roles and a central strategic design authority with key stakeholders;
e) develops a consistent asset condition data set for passive crossings to inform interventions and investment decisions;
f) brings together and makes more readily available cross functional asset condition data to inform interventions and investment decisions for the active
level crossing system;
g) brings together and makes more readily available a wide range of data covering performance, safety risk, reliability, usage and configuration currently
held in different data bases and spreadsheets, structured and unstructured and in different formats;
h) develops and implements a level crossing asset data and information strategy consistent with the requirements of the Network Rail asset data policy
Document History

