Signalling Design Hand Book

Network Rail Standards
Attachment notice
To access individual modules referenced within this standard, blue active links are provided from the relevant
index pages where these are listed. Clicking on a specific reference will lead to the corresponding document.
Please ensure to open bookmarks for easier navigation within the document and to access index of modules.
Alternatively, you may use the search fac ility to search for a specific document by using the
complete document reference number such as NR/L3/SIG/30082/002 in the search field.
Proceed to document u
Copyright Network Rail

Provided by IHS under license with Network Rail
No reproduction or networking permitted without license from IHS
Licensee=Kier Professional Services Ltd/1121225001, User=Anchi, Mallikarjuna

Not for Resale, 05/06/2015 05:07:43 MDT
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Information for users


--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
User information
This Network Rail standard contains colour-coding according to the following Red
AmberGreen classification.
Red requirements No variations, could stop the railway
Red requirements shall always be complied with and achieved.
Red requirements shall be presented in a red box with the word shall or
expressed as a direct instruction.
Accountability for the efficacy of red requirements lies with the Professional
Head/Standard Owner.
Red requirements are monitored for compliance.
Corrective actions shall be enforced if variations are discovered through

functional checks (e.g. engineering verification visits, audit or Operations SelfAssurance).
Amber requirements Controlled variations, approved risk analysis and

mitigation
Amber requirements shall be complied with unless variation has been

approved in advance.
Amber requirements shall be presented with an amber sidebar and with the word
shall or expressed as a direct instruction.
Accountability for the efficacy of these requirements lies with the Professional
Head/Standard Owner, or their nominated Delegated Authority.
Amber requirements are monitored for compliance.
Variations may be permitted. Variations are approved by the Standard Owner or

through existing Delegated Authority arrangements.
Corrective actions shall be enforced if non-approved variations are discovered

through functional checks (e.g. engineering verification visits, audit or Operations
Self-Assurance).
Green Guidance
Guidance is based on good practice. Guidance represents supporting information

to help achieve Red and Amber requirements.
Guidance shall be presented with a dotted green sidebar and with the word
should (usually in notes) or as a direct instruction.
Guidance
is not mandatory and is not monitored for compliance.
Alternative solutions may be used. Alternative solutions do not need to be

formally approved.
Decisions made by a competent person to use alternative solutions should be

backed up by appropriate evidence or documentation.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 2 of 100
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Issue record
Issue Date
Comments
August 2000
New Document
April 2001
Minor Revisions
December 2003
Minor Revisions
June 2011
Name-change & Modularisation of handbook and

former guidance notes, inclusion of: RT/E/G/11710
as appendix E. Addition of modules A & B, see
index on page 3 below.
September 2011
Amended references due to withdrawal of

NR/L3/SIG/30018 & New index following the
introduction of Modules in the X01 X99 series.
December 2011
Module X21 reissued
March 2012
Amendment to the process for managing and

undertaking non-conceptual design, affects section
7.2 & Module A1 sections 8.3; 8.3.2 & 8.3.3
June 2012
Changes to the X series of modules
Sept 2014
Incorporation of signal duty holder requirements

from GK/RT0044 (1) into module B7
Compliance
This Network Rail standard is mandatory and shall be complied with by Network Rail
and its contractors if applicable from 06/09/2014.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
When this standard is implemented, it is permissible for all projects that have
formally completed GRIP Stage 3 (Option Selection) to continue to comply with the
issue of any relevant Network Rail standards current when GRIP Stage 3 was
completed and not to comply with requirements contained herein, unless stipulated
otherwise in the scope of this standard.
Disclaimer
In issuing this document for its stated purpose, Network Rail makes no warranties,
express or implied, that compliance with all or any documents it issues is sufficient
on its own to confirm safe systems of work or operation. Users are reminded of their
own duties under health and safety legislation.
Supply
Copies of documents are available electronically, within Network Rails organisation.
Hard copies of this document may be available to Network Rail people on request to
the relevant controlled publication distributor. Other organisations may obtain copies
of this from an approved distributor.
Page 3 of 100


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
NR/L2/SIG/11201 - Index of signalling design handbook A Modules

MODULE NUMBER & TITLE
ISSUE
Date

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
NR/L2/SIG/11201
Signalling Design Handbook
06/09/2014
Mod A1
Outline Project Specifications (OPS) for Signalling Schemes
03/03/2012
Mod A2
Minimum Requirements for design details
03/09/2011
Mod A3
Assessment of signalling Systems before Signalling Design Alterations
04/06/2011
Mod A4
Design Specification Guidelines
03/09/2011
Mod A5
Occupational Safety
04/06/2011
Mod A6
Safety Hazards requiring retrospective work
03/09/2011
Mod A7
Correlation of Signalling Records
04/06/2011
Mod A8
Design Record and Production control
04/06/2011
Mod A9
Safety System
04/06/2011
Mod A10
Configuration Control
04/06/2011
Mod A11
Operating Requirements Review
04/06/2011
Mod A12
Design Modifications
04/06/2011
Mod A13
Certification Process
04/06/2011
Mod A14
Source Record Updating
04/06/2011
Mod A15
Arrangement and Presentation
04/06/2011
Mod A16
Temporary Work
04/06/2011
Mod A17
Symbols for plans and sketches used in Signalling Applications
04/06/2011
Mod A18
Signalling Design Control Tables
04/06/2011
Mod A18/AppA
Conventions, General Notes, Dollar Notes and Signallers Route Lists
04/06/2011
Mod A18/AppB
RRI Signal and aspect control tables
04/06/2011
Mod A18/AppC
RRI point and ground frame control tables
04/06/2011
Mod A18/AppD
Control tables for level crossings
04/06/2011
Mod A18/AppE
Control tables for train warning and protection systems
04/06/2011
Mod A18/AppF
Control Tables For Staff Protection Systems (TOWS)
04/06/2011
Mod A18/AppG
Control Tables For Block Systems & Electro-mechanical
04/06/2011
Mod A18/AppH
SSI Control Tables
04/06/2011
Mod A18/AppJ
SIMIS W Control Tables
04/06/2011
Page 4 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
ISSUE
NR/L2/SIG/11201
014
06/09/2014
Date
Mod A19
Symbols for Signalling Circuit Diagrams
04/06/2011
Mod A20
Dependability
04/06/2011
Mod A21
Verification Process
04/06/2011
Mod A22
Overlapping and Parallel Signalling Design
04/06/2011
NR/L2/SIG/11201 - Index of signalling design handbook B Modules

ISSUE
DATE
04/06/2011

Mod B1
Circuits - General Introduction
Mod B2
Circuits - Conflicting Standards
04/06/2011
Mod B3
Circuits - General
03/09/2011
Mod B4
Circuits Fusing & Looping of Signalling Circuits
04/06/2011
Mod B5
Circuits Electromagnetic Compatibility of Electronic Equipment
04/06/2011
Mod B6
Circuits Insulation and Earthing for Occupational Safety
04/06/2011
Mod B7
Interlockings General
06/09/2014
Mod B8
Interlockings Lever Frame Interlocking Guidelines
04/06/2011
Mod B9
Interlockings Free-Wired Route Setting Interlocking Guidelines
04/06/2011
Mod B10
Interlockings Geographical Relay Interlocking Guidelines
04/06/2011
Mod B11
Interlockings Electronic Interlocking Guidelines
04/06/2011
Mod B12
Transmission Systems - (Cable terminations & Cable routes)
04/06/2011
Mod B13
Points - General
04/06/2011
Mod B14
Points Point Fittings (Supplementary Information)
04/06/2011
Mod B15
Points Relay Circuits
04/06/2011
Mod B16
Points SSI Application
04/06/2011
Mod B17
Signals General
04/06/2011
Mod B18
Signals Semaphore Signals (Supplementary Information0
04/06/2011
Mod B19
Signals Relay Circuits
04/06/2011
Page 5 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
Mod B20
Signals SSI Application
NR/L2/SIG/11201
014
06/09/2014
ISSUE
DATE
04/06/2011
NR/L2/SIG/11201 - Index of signalling design handbook X Modules

ISSUE
DATE
03/09/2011

Mod X01
Level Crossings - General
Mod X02
Level Crossings - Common Design Requirements
02/06/2012
Mod X10
Level Crossings - Automatic Half Barriers (AHB)
03/09/2011
Mod X11
Level Crossings - Automatic Barrier Crossing Locally Monitored (ABCL)
02/06/2012
Mod X12
Level Crossings - Automatic Open Crossing Locally Monitored (AOCL)
02/06/2012
Mod X13
Level Crossings - Automatic Open Crossing Locally Monitored Plus Barriers (AOCL + B)
03/09/2011
Mod X14
Level Crossings - Open Crossing With Additional Flashing Lights
03/09/2011
Mod X20
Level Crossings - Manned Gated Crossings (MG)
03/09/2011
Mod X21
Level Crossings - Manually Controlled Barriers With Obstacle Detector (MCB-OD)
02/06/2012
Mod X22
Level Crossings - Manually Controlled Barriers (MCB)
02/06/2012
Mod X23
Level Crossings - Manually Controlled Barriers With Closed Circuit Television (MCB-CCTV)
03/09/2011
Mod X24
Level Crossings - On Call Barriers (MCB-OC)
02/06/2012
Mod X25
Level Crossings - Wicket Gate Magnetic Locks
03/09/2011
Mod X30
Level Crossings - Traincrew Operated Gates (TOG)
03/09/2011
Mod X31
Level Crossings - Traincrew Operated Barriers (TOB)
03/09/2011
Mod X40
Level Crossings - Miniature Stop Lights (MSL)
02/06/2012
Mod X41
Level Crossings - User Worked Barriers
03/09/2011
Mod X42
Level Crossings - Power Operated Gate Openers (POGO)
03/09/2011
Mod X99
Level Crossings - History Of Level Crossing Protection
03/09/2011
Page 6 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Contents
1 Purpose
2 Scope
3 Reference documentation
4 Definitions
16
5 Compliance
16
7 Signalling Scheme Conception
19
8 Design Process
24
9 Overlapping and Parallel Design
26
10 Approval and Acceptance
28
11 Design Changes
33
12 Certification and Issue
34
13 Maintenance of Records
34
14 Configuration Control
35
15 Special Cases of Design Production
39
16 Presentation and Convention
41
17 Health and Safety
42
18 System Safety
42
19 Dependability
45
20 Retention of Documentation
47
Appendix A Signalling Design Records CAD Data Requirements
48
Appendix B Signalling Design Records SSI Data Requirements
58
Appendix C Signalling Design Records Electronic Systems Data Requirements
61
Appendix D Signalling Design Records IECC Data Requirements
65
Appendix E Definitions, Related Documents & Subject Index
79
Page 7 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
6 Competence and Responsibilities 17
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
1 Purpose
This standard sets out mandatory requirements and mandates standards for the
production of signalling design detail to support:
a) safe development and design of new and altered signalling systems impacting
on Network Rail controlled infrastructure;
b) safe interfaces between all parties and systems;
c) design details are prepared and presented clearly, accurately, consistently
and unambiguously; and
d) clients specified requirements are met and the design is fit for purpose.
2 Scope
This standard lays down the requirements for:
a) the design of signalling works applicable to the infrastructure;
b) the design of signalling systems, whether lineside or train-borne;
c) the design of software and data used in programmable signalling systems;
and
d) the tools, including software, used in design.
It applies from scheme conception through to acceptance into service or, where
applicable, to decommissioning and disposal.
3 Reference documentation
3.1 Railway Group Standards
GC/RT5021
Track System Requirements
GC/RT5033
Terminal Tracks - Requirements for Buffer Stops, Arresting

Devices and End Impact Walls
GE/GN8537
Guidance on Signal Positioning and Visibility
GE/RT8000
Rule Book
GE/RT8018
Mechanical Trainstop Systems
GE/RT8024
Persons Working On or Near to AC Electrified Lines
GE/RT8030
Requirements for the Train Protection and Warning System

(TPWS)
GE/RT8035
Automatic Warning System (AWS)
GE/RT8037
Signal Positioning and Visibility
GE/RT8106
Management of Safety Related Control, Command and

Signalling (CCS) System Failures
Page 8 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
GE/RT8270
Assessment of Compatibility of Rolling Stock and Infrastructure
GI/RT7006
Prevention and Mitigation of Overruns - Risk Assessment
GI/RT7033
Lineside Operational Safety Signs
GK/EH V609
Safe Working Procedures for D.C. Electrified Lines
GK/ES 1683
The Design, Installation and Testing of Earthing Systems For

Signalling and Telecommunications Purposes
GK/GN0802
Glossary of Signalling Terms
GK/RT0009
Identification of Signalling and Related Equipment
GK/RT0025
Signalling Control Centres
GK/RT0028
Infrastructure Based Train Detection Interface Requirements
GK/RT0029
Train Activated Warning Systems
GK/RT0034
Lineside Signal Spacing
GK/RT0038
Signing of Permissible Speeds and Speed Restrictions
GK/RT0039
Semaphore and Mechanical Signalling
GK/RT0041
Track Circuit Block
GK/RT0042
Absolute Block
GK/RT0044
Controls for Signalling a Train onto an Occupied Line
GK/RT0045
Lineside Signals, Indicators and Layout of Signals
GK/RT0051
Single Line Control
GK/RT0054
Radio Electronic Token Block
GK/RT 0060
Interlocking Principles
GK/RT0061
Shunters Releases, Ground Frames, Switch Panels and Gate

Boxes
GK/RT0063
Approach Locking and Train Operated Route Release
GK/RT0064
Provision of Overlaps, Flank Protection and Trapping
GK/RT0192
Level Crossing Interface Requirements
GK/RT0210
Asset Management for the Safety of Signalling and Operational

Telecommunication Systems and Equipment
GK/RT0212 Signalling
Lockout Systems to Protect Railway Undertaking
Personnel
GL/RT1253
Mitigation of DC Stray Current Effects
GL/RT1254
Electrified Lines Traction Bonding
GM/RT2450
Qualification of Suppliers of Safety Critical Engineering Products

and Services
GO/RT3215
Requirements for the Weekly Operating Notice, Periodical

Operating Notice and Sectional Appendix
Page 9 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
GS/ES 1937
Engineering specification - SSI trackside data link surge

protection module
GT/TD INT100
Earthing and Equipotential Bonding of Telecommunications

Equipment
HS (G) 47
Avoiding danger from underground services
RIS-1800-ENE
Rail Industry Standard for Network and Depot Interface

Management - Isolation Documentation
RIS-7700-INS
Rail Industry Standard for Station Infrastructure
NR/GN/CPR/401
Guidance on Contractual Health and Safety Requirements
NR/GN/ELP/27022
Design & Install of Negative Bonding & Associated

Equipment for DC Electrified Lines
NR/GN/ELP/45002
The Installation of Electric Point Heating
NR/GN/SIG/CAT005
Index of Network Rail Documents relating to Signalling &

Communications Equipment Typical Circuits
NR/GN/SIG/11774
Clamp Lock Handbook
NR/GN/SIG/11821
Siting Requirements for Lineside Apparatus Housings
NR/GN/SIG/19012
SIGTAN 012 Cables and Wiring used for Signalling Systems
NR/GN/SIG/19014
SIGTAN 014 Mechanical Handbook
NR/GN/SIG/19015
SIGTAN 015 Relay Plugboard Problems
NR/GN/SIG/19016
SIGTAN 016 Westinghouse M3 Point Machine
NR/GN/SIG/19020
Signalling Equipment Technical Advice Notice (SIGTAN020)

Signalling Relays
NR/GN/SIG/19254
SIGWEN 003 GEC-GS Type HW Point Machine
NR/L1/CTM/001
Competence Management
NR/L1/INF/02232
Information Security Policy
NR/L2/INI/CP1030
Working safely in the vicinity of buried services
NR/L2/EBM/STP001 Managing
Network Rail Standards
NR/L2/ELP/40045
Electric Point Heating
NR/L2/HSS/020
Safety Validation of Organisational and Safety Management

System Change
NR/L2/INF/02018
Standard for the Management of Safety Related

Infrastructure records (formerly NR/SP/INF/02018)
NR/L2/OCS/085
Permissive Platform Working

Page 10 of 100


--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
3.2 Network Rail Company Standards
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/RSE/100
Network Rail Acceptance Panel processes
NR/L2/SIG/00005 Railwa
NR/L2/SIG/10064
014
06/09/2014
y Signalling Cable
General Instructions to Staff Working on S & T Equipment
NR/L2/SIG/10157 Si
gnal Sighting
NR/L2/SIG/10160
Signal Engineering: Implementation of IRSE Licensing

Scheme Route to Competence
NR/L2/SIG/11010
Management of Signalling & Communication Systems
NR/L2/SIG/11107 Silver
Migration
NR/L2/SIG/11129
Life Management of Signalling Relays, Searchlight and

Electro-mechanical and Banner Signals
NR/L2/SIG/11231
Signal Maintenance Testing Handbook
NR/L2/SIG/11630
BR930 Series Pin Code Allocations and Contact

Arrangements
NR/L2/SIG/17002
SSI Applications Manual Contents
NR/L2/SIG/30009
Signalling Principles Handbook
NR/L2/SIG/30014
Signalling Works Testing Handbook
NR/SIG/10663 Signal
Maintenance Specifications
NR/L3/SIG/11303
Signalling Installation Handbook
NR/L3/SIG/19272
Signalling Equipment Workshop Engineering Notice

(SIGWEN021) Signalling Relays
NR/L3/SIG/CAT003
Index of Network Rail Documents Relating to Signalling and

Communications Equipment: Part 1 - Mechanical & Electrical
Drawings
NR/PS/SIG/11755
DC Track Circuits
NR/PS/SIG/11762
Track Circuit Assister Interference Detectors
NR/SP/CIV/044
Design & Construction of Undertrack Crossings
NR/SP/ELP/21085
Specification for Design of Earthing & Bonding Systems for

25Kv AC Electrical Lines
NR/L2/ENV/015
Contract Requirements - Environment
NR/SP/ERG/24017 Control
Room Design Specification, Process and Guidance
NR/SP/OHS/069
Lineside Facilities for Personnel Safety
NR/SP/SIG/02023
Requirements for TASS Infrastructure System Design
NR/SP/SIG/10015
Rail Clamp Point Lock - Performance Spec for the

Microswitch with Independent Contacts
NR/SP/SIG/10060
Vital Signalling Timer
Page 11 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/SP/SIG/10131 Requirement
Schemes
NR/L2/SIG/11201
014
06/09/2014
Specification for Signals On Controls for SSI
NR/SP/SIG/10133
Train Protection and Warning System (TPWS) Signalling

Interface Design Requirements
NR/SP/SIG/10137
Train Protection and Warning System (TPWS) Selection of

New Signals And Other Locations For Provision of TPWS
NR/SP/SIG/11130
Requirements for the Provision of SPAD Alarms at Signalling

Control Centres
NR/SIG/11231
Signalling Maintenance Testing Handbook
NR/SP/SIG/11752
Train Detection
NR/SP/SIG/14200
Prevention and Mitigation of Overruns - Risk Assessment

Tools
NR/SP/SIG/17004
Requirement Specification for the SSI Technical Terminal
RT/LS/CAT004
Index of Railtrack Documents Relating to Signalling and

Communications Equipment: Part 1 - Signalling Structure
Drawings
NR/GN/SIG/CAT006
Index of Railtrack Documents Relating to Signalling and

Communications Equipment: Part 1 - Equipments and
Systems Specifications
3.3 Network Rail Forms
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
QF901
Request for Handover of Source Records
QF902
Solid State Interlocking Data Requests and Returns
QF909
Authorisation to Browse
QF910
Requests for Prints of Source Records
QF911
Authorisation to Transfer a Projects Source Records for

Continuance of the Project
QF915
Return of As Built Records
QF921
Electronic Systems Data and Software Requests and

Returns
QF924
Integrated Electronic Control Centre Data Requests and

Returns
QF925
Request for Solid State Interlocking Control Centre Identity

Number
3.4 Standards And Application Standards

BR 817
Electro Hydraulic Power Equipment for Point Operation
BR 818
Self Supporting Aerial Electric Cable for Railway Signalling

(Metric Units)
Page 12 of 100


NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
BR 819
Earthing & Bonding of Telecommunications Cable Sheats

Separate Screening Conductors & Associated Lineside
Equipment in A.C. Electrified Areas
BR 880
Specification for Aluminuim Cored Insulated Cables for

Railway Signalling Power Supplies
BR 901
Specification for Flasher Unit Level Crossing Road Signals
BR 902
Specification for Electrical Requirements of High Voltage

Electric Point Machines for Railway Signalling Purposes
BR 903
Electrical
Requirements for Standard Colour Light Signals
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
BR 923
Specification for Moving Iron Direct Current Polar Line

Relays for Railway Signalling
BR 925
Specification for Electro-Magnetic Indicator for Railway

Signalling
BR 967
Railway Signalling Apparatus: Environmental Conditions
BR 991
Flashing Signal Aspect Control Unit
BR 998
Electric Point Detectors
BR 1612
Specification
for renovation and construction of cable routes
BR 1615
Relocatable Equipment Buildings for S&T Use
BR 1820
Spec for earthing and bonding of separate screening

conductors and associated lines
BR 1822
Steel/Polymer Laminate Tape And Oversheath For Plastic

Sheathed Cables
BR 1844
110 volt, 100 watt heater for clamp lock
BR 1901
Solid State Interlocking Lineside Points module
BR 1902
Specification for solid state interlocking lineside signal

module
BR 1904A
Solid Sate Interlocking Data Link Module Mkiii
BR 1905A
Solid Sate Interlocking Multiprocessor Module (Mkii)
BR 1906
Solid state interlocking long distance terminal
BR 1908
Solid state interlocking panel processor module (MK11)
BR 1911
Solid state interlocking processor memory module Mk11
BR 1921
Interlocking a panel multiplex system with a solid state

interlocking
BR 1932
Twin data link type polyethylene insulated and polyethylene

sheath
BR 1974
Multicore railway signalling cables with re-formed

terminations
Page 13 of 100

NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
BR 1975
Clamp Lock Disconnection Box for use with Pre0formed

terminated cable
BR 1990
Specification For Preparation of EPROMs for Railway

Signalling Applications
BR 1992
Specification fro Orange Polyethylene Pipe Used for

signalling cable protection
BR 3006
Environmental Specification For Solid State Interlocking

Equipment In Trackside Location Casks Part 1- Electrical
Environment
BR 13422
50Hz Single Phase AC Electrification, Immunisation of

Signalling and Telecommunications Systems Against
Electrical Interference
SSI 8003
SSI Applications manual
SSI 8150
SSI Software Record
SSI 8505
SSI Data Procedures
3.5 British And European Standards

BS 469
Specification for electric lamps for railway signalling
BS 561
Specification for alternating-current line relays doubleelement 3-position (for railway signalling)
BS 581
Specification for electrically-driven point-operating machines

for railways
BS 714 (1950)
Specification. Cartridge fuse-links for use in railway-signalling

circuits
BS 1745
Specification for alternating-current relays for railway

signalling: track relays (double-element, 2-position), line
relays (single-element, 2-position)
BS 2754
Protection against electric shock. Live working
BS 3506
Specification for unplasticized PVC pipe for industrial uses
BS 4778
Quality vocabulary. Availability, reliability and maintainability

terms. Guide to concepts and related definitions
BS 5760
Reliability of systems, equipment and components
BS 6004
Electric cables. PVC insulated, non-armoured cables for

voltages up to and including 450/750 V, for electric power,
lighting and internal wiring
BS 7430
Code of practice for earthing
BS 7645
Code for designation of colours
BS 7671
Requirements for electrical installations. IEE Wiring

Regulations. Seventeenth edition
Page 14 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
BS 8888
Technical product specification: Specification for defining,

specifying and graphically representing products
BS ISO 80000-1
Quantities and units
BS ISO/IEC 90003
Software Engineering - Guidelines for the application of ISO

9001:2000 to computer software
BS EN ISO 9001
Quality management systems. Requirements
BS EN 50121-4:2000 Railway applications. Electromagnetic compatibility. Emission

and immunity of the signalling and telecommunications
apparatus
BS EN 50122-1
Railway applications. Fixed installations. Protective

provisions relating to electrical safety and earthing
BS EN 50122-2
Railway applications. Fixed installations. Electrical safety,

earthing and the return circuit. Provisions against the effects
of stray currents caused by d.c. traction systems
BS EN 50126
Railway applications. The specification and demonstration of

reliability, availability, maintainability and safety (RAMS)
BS EN 50128
Railway applications. Software for railway control and

protection systems
BS EN 50129
Railway applications. Safety related electronic systems for

signalling
BS EN 50160
Voltage characteristics of electricity supplied by public

electricity networks
BS EN 60297-3-101:
2004
Mechanical structures for electronic equipment. Dimensions

of mechanical structures of the 482,6 mm (19 in) series.
Subracks and associated plug-in units
BS EN 60529
Degrees of Protection Provided by Enclosures
BS EN 60617
Graphical symbols for diagrams
BS EN 61082
Preparation of documents used in electrotechnology
BS EN 61386-1
Specification for conduit systems for cable management.

General requirements
BS EN 61508
Functional safety of electrical/electronic/programmable

electronic safety-related systems
BS EN ISO 9001
Quality management systems. Requirements
DD ENV 50129
Railway applications. Safety related electronic systems for

signalling
EHQ/CP/S/030
Preparation of Isolation Diagrams And Instructions For A.C

Electrified Lines
Page 15 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
BS EN 50121-1:2000 Railway applications. Electromagnetic compatibility. General
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
3.6 Legislation
1983c16
Level Crossing Act 1983 (amended by SI 1997/487)
96/48/EC
Directive on the interoperability of the trans-European highspeed rail system
2001/16/EC
Directive on the interoperability of the trans-European

conventional rail system
HS (G) 47
Avoiding danger from underground services
SI 1994/157
Railways and Other Transport Systems (Approval of Works,

Plant and Equipment) Regulations 1994
SI 1994/3140
Construction (Design and Management) Regulations 1994

(amended by SI 2000/2380)
SI 1997/487
Level Crossing Regulations 1997
SI 1999/3242
Management of Health and Safety at Work Regulations 1999
SI 2000/2380
Construction (Design and Management) (Amendment)

Regulations 2000
SI 2002/1166
Railways (Interoperability) (High-Speed) Regulations 2002
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
3.7 Guidance
L59
HSE/HMRI Guide to the Approval of Railway Works, Plant

and Equipment
Hazards Forum
Safety-related systems. Guidance for engineers
4 Definitions
Terms and definitions are provided in Appendix E
A glossary of general signalling terms is given in GK/GN0802. Where no definition is
included in Appendix E, that given in GK/GN0802 should be used.
Safety terms are also defined in GK/GN0802.
5 Compliance
The design parameters and type approval processes concerning individual items of
equipment used in the systems are dealt with in NR/L2/RSE/100.
Where the guidelines given in the standards referenced, are not complied with an
application for authority for non-compliance with this standard (NR/L2/SIG/11201)
shall be sought.
The procedure for submitting such applications is detailed in NR/L2/EBM/STP001.
Alternative proposals shall deliver the same or better level of safety integrity.
Page 16 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
5.1 Conformity of Presentation

Signalling works shall be designed to this standard, except where existing design
details conform to previous standards of presentation and the partial use of this
standard would result in confusing information being presented.
In such cases, the previous standards of presentation, format, symbols and units
should be used where appropriate. Conformity of presentation to this standard shall
be considered if the design details are redrawn. It shall be documented in the design
standard which design details are to be redrawn in conjunction with the project.
5.2 Conformity to Technical Standards
The standards to which the works are designed shall be documented at each
scheme phase. Generally the control and approval document is the scheme plan.
As a minimum, the appropriate signalling principles and design standards shall be
recorded at the date of scheme plan approval.
Guidelines are given in NR/L2/SIG/11201 - Module A11.
The alteration of existing installations that conform to previous technical standards is
considered in GK/GN0802.
5.3 Changes to Standards
When a new or amended Railway Group Standard or Company Standard is issued
after the scheme plan has been approved for detailed development, Network Rail
shall determine whether that standard is to be applied. The reasons for not
implementing a change shall be logged on the design standard, or supplement
thereto.
Where current standards cannot be complied with, for any reason, a formal
derogation shall be obtained in accordance with NR/L2/EBM/STP/001.
When a new or amended Railway Group Standard or Company Standard specifies
retrospective action, an implementation plan shall be added to the design standard,
or supplement thereto.
Retrospective work is considered further in NR/L2/SIG/11201 - Module A6.
6 Competence and Responsibilities
6.1 Design Authority Qualification
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Supplier qualification shall be in accordance with GM/RT2450.

All signalling design work shall take place within a management system compliant
with BS EN ISO 9001, or similar.
Network Rail shall be satisfied that the design authority is competent and will allocate
adequate resources to perform its responsibilities under the Construction (Design
Page 17 of 100


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
and Management) Regulations 1994, as described in NR/L2/INI/CP0047 and

NR/GN/CPR/401.
6.2 Interface Management
Network Rail shall control interfaces between design authorities in accordance with
section 9. Relationships between design authorities shall be defined in the design
standard.
The design authority shall have in place processes for managing interfaces between
authorities, disciplines, functions and sub-contractors so as to confirm a safe and
timely flow of information. These shall pay particular attention to the controls
necessary to mitigate those risks over which there is otherwise no direct check.
Guidelines on the interdisciplinary checks necessary in the preparation of design
details are given in NR/L2/SIG/11201 Module A2.
The approval for construction process (see Section 10.6) shall confirm that the
appropriate checks have been undertaken.
Design processes shall interface with the construction and testing procedures given
in NR/L3/SIG/11303 and NR/L2/SIG/30014, respectively. In particular, the design
shall facilitate a safe method of construction (see Section 17) and independent
validation that the system performs to the clients requirements and the design
standard, i.e. it shall be constructable and testable.
The design authority shall be reasonably satisfied that any sub-contractors employed
are competent in the appropriate field and will allocate adequate resources to
perform their responsibilities. In order to bear the responsibility for works performed
by its sub-contractors, the design authority shall confirm an adequate level of
verification and validation of the works.
6.3 Competence of Personnel

All work shall be undertaken by, or under the close direction of, personnel who have
documented proof of competence, in accordance with NR/L1/CTM/001 and who
have been authorised to undertake the work. The necessary competence
management systems are described in NR/L1/CTM/001.
A register of competent designers, together with their initials and fields of
competence, shall be maintained by the design authority and be available for
inspection by Network Rail.
6.4 Competence Requirements for Correlation Staff
Staff engaged to undertake correlation activities shall be further trained and
assessed as competent to perform the tasks detailed in NR/L2/SIG/11201 Modules
A3 & A7.
Page 18 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
For the control of system interfaces, see Section 14.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
6.5 Design Producer Responsibility

A clearly presented functional design, accurately reflecting the clients requirements,
shall be produced by a designer, known as the producer. Producers shall check
their own design, correct any errors revealed and certify it, before passing it to an
independent checker, together with any supporting documentation, such as
calculations and/or safety analysis.The process is described in Section 8.
6.6 Design Checker Responsibility
Checking shall be carried out by a designer, known as the checker, who shall remain
independent of the production for the particular design throughout the design
process. All design details produced shall be certified by the checker before issue.
The process is described in Section 8.3.
6.7 Responsible Design Engineer
Prior to issue of design details, the responsible design engineer shall approve the
design for construction, in accordance with Section 10.6
NOTE That a responsible design engineer, appointed in connection with a design contract, may also
be the contractor's responsible engineer.
6.8 Responsibility of All Personnel

It is the responsibility of all personnel to be vigilant and to advise the appropriate
authority of any deficiency observed that might compromise the safety of the
signalling system or of personnel.
7 Signalling Scheme Conception
The initial phases of a signalling scheme, associated with any new or altered
signalling system, shall include the following, to a degree commensurate with the
extent and type of work proposed:
7.1 Client Remit
The sponsors requirements shall be stated in a brief to enable the outline project
specification to be prepared. This will generally be specified in terms of train
operations and dependability (see Section 19).
7.2 Outline Project Specification (OPS) or Equivalent Documentation
This shall be prepared by a person deemed technically competent by the project
manager. The process is detailed in NR/L2/SIG/11201 Module A1, which shall be
Page 19 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
A single responsible design engineer shall be appointed for each project, or series of
commissionings, to confirm that all stages of design and development is directed and
checked by competent personnel and is compliant to the specified requirements,
including the appropriate level of safety and dependability.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
followed to a degree commensurate with the size and complexity of the works
proposed.
Alternatively, in the case of non-conceptual work, a design remit shall be used (see
NR/L3/SIG/30075/Form A).
Feasibility studies, where required, shall generally be undertaken at this phase.
7.3 Scheme Plan
A scheme plan shall be developed from the client remit and OPS, or equivalent, by
means of the processes described in this Standard, in order to obtain approval in
principle for the scheme, in accordance with Section 10.3. The scheme plan may be
omitted where no change to the existing signalling plan is proposed.
Where the extent and type of work proposed is sufficiently restricted and it is stated
in the OPS or PIF, a scheme plan extract or dimensioned sketch may be used.
Where applicable, stage scheme plans shall be derived from the approved scheme
plan before producing the engineering details, and, where required for approval,
shall be submitted at a subsequent phase.
Guidelines on the minimum content of the scheme plan (and associated
documentation) and considerations associated with stage scheme plans are given in
NR/L2/SIG/11201 Module A2.
7.4 Site Surveys
Where practicable, a recent milepost and gradient survey shall be obtained as a
basis for the scheme plan.
The sighting of lineside signs, signals and indicators shall be undertaken as soon as
practicable following scheme approval, in accordance with GE/RT8037. The likely
resulting amendments to the scheme plan are described in NR/L2/SIG/11201
Module A2.
Equipment likely to be affected by the proposed work shall be examined by a
competent signal engineer who shall make an assessment of any factors which
might introduce special risks during the execution of the work. The process is
detailed in NR/L2/SIG/11201 Module A3.
Other site surveys, where necessary, shall generally be undertaken at this phase.
7.5 Design Specification
Following scheme plan approval, it is appropriate to commence the design
specification phase.
A design specification shall be produced for signalling works to satisfy the clients
requirements. The design specification shall be subject to acceptance by Network
Rail. It shall originate from the OPS or equivalent.
The design specification shall consider the following:
Items (a) to (d) are mandatory for statutory approval purposes.
Page 20 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
The standards to which the works are to be designed shall be referenced on the
scheme plan (or associated documentation), in accordance with Section 5.2.
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
a) project description and extent of works (including policy on redundant asset

recovery);
b) the standards to which the works are to be designed;
c) proposed timescales (including those for the supply of closure lists to the
tester in charge and the completion of final records);
d) the different means to be used to assure safety (and the interfaces in a hybrid
approach), such as risk assessment, together with any mitigation or control
measures arising (see Sections 17 and 18);
e) any safety cases or type approval required for new systems or equipment
(see Section 18.3);
f) any relevant information from the design specification of the existing
installation;
g) assurance of competent and adequately resourced personnel (see Section 6);
h) relationships between design authorities, as well as interfaces with other
authorities, disciplines, functions and sub-contractors (see Section 6.2);
i) the extent of correlation required, together with any responsibilities for
subsequent updating and remedial action (see Section 7.7);
j) any factors identified in an assessment of the proposed works (see
NR/L2/SIG/11201 Module A2);
k) stagework and testing strategies, for constructability and testability;
l) environmental considerations;
m) train operating requirements;
n) dependability requirements (see Section 19);
o) other design parameters and assumptions, such as permissible speeds,
headway, type of electrification, etc. (see NR/L2/SIG/11201 Module A2);
p) design production methodology (see Section 8.2), including arrangements for
record updating and any redrawing necessary;
q) any requirement for overlapping or parallel design, with the necessary control
measures (see Section 9);
r) any special control measures or relaxations granted for the special cases
described in Section 15, such as whether all previously designed works have
been commissioned, and, if not, the means of controlling any discrepancies
arising;
s) design check recording methodology (see Section 9);
t) means of applying configuration control, particularly to software systems (see
Section 14);
u) responsibilities for collating documentation to be submitted for Network Rail
approval and statutory approval (see Section 10);
v) system interfaces (see Sections 14.6 and 14.8);
Page 21 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
w) other information necessary to enable the control tables and engineering

details to be compiled from the scheme plan; and
x) method of controlling and authorising changes to the project, including
changes to the clients requirements, scheme plan and design specification,
etc.
As the scheme progresses, a log of significant changes or variations to the scheme
shall be appended to the design specification, together with the date and reason for
each change. Decisions taken with respect to the implementation of changed
standards (see Section 5.3) shall be similarly recorded. Significant change shall be
defined in the design specification. (The concept is used further in Sections 10.5,
10.6, 11.1, 11.2, 18.3.2 and 18.4.)
Guidelines on the production method, acceptance and format of the design
specification are given in NR/L2/SIG/11201 - Module A4.
A copy of the current accepted design specification shall be held by Network Rail. It
shall subsequently be retained in the health and safety file.
In the special cases described in Section 15.2, where the extent and type of work
proposed is sufficiently restricted, a recognised method statement may be used in
lieu of a design specification.
7.6 Health and Safety Documentation
This section applies where the signalling works fall within the scope of the
Construction (Design and Management) Regulations. Guidelines are given in
NR/L2/SIG/11201 - Module A5.
7.6.1 Health and Safety Plan
A health and safety plan shall be adequately developed by the principal contractor
and accepted by Network Rail, before construction work commences on site. It shall
include, as a minimum, the following items from a health and safety perspective:
a) project description and proposed timescales;
b) assurance of competent and adequately resourced personnel, with roles and
responsibilities;
c) any relevant information from an existing health and safety file;
d) review of the major safety and environmental hazards, including any factors
identified in an assessment of the proposed works (see NR/L2/SIG/11201
Module A3);
e) hazard identification relating to each element of the work, together with any
hazards to be eliminated or risk control measures to be designed (see
Section 17);
f) additional safety information to enable a competent contractor to put
appropriate precautions in place, including personal protective equipment
and warning devices (see Section 17); and
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
g) safety arrangements for the project, including method statements and site
rules, access points, permissible train speeds, procedures for the safe

Page 22 of 100
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
operation of plant, control of hazardous substances, fire safety, electrical

safety, etc.
7.6.2 Health and Safety File
At appropriate phases of the scheme, the design authority shall contribute to a health
and safety file that is compiled by the planning supervisor and retained for the life of
the installation. The following information shall typically be submitted for inclusion or
reference on the file:
a) the design specification;
b) the design records, together with explanations of unusual design features;
c) the standards to which the works are designed (see Section 5.2);
d) known safety hazards that have been addressed and those that have not
been addressed (see NR/L2/SIG/11201 Module A6);
e) decisions based on risk assessment, with reference to any specific safety
cases (see Section 18);
f) evidence that the signalling system depicted on the engineering details
consists of approved sub-systems and equipment working within their
application criteria (see NR/L2/RSE/100);
g) operating manuals and procedures;
h) maintenance manuals and procedures; and
i) any other information on risks to be managed during operation, maintenance,
or future works on the completed infrastructure.
7.7 Correlation
Before any alterations are made to the design of a signalling system a check shall be
made to confirm that the system correlates accurately with the records which will
form the basis of the design alterations. Any deficiencies found shall be
investigated. The process is detailed in NR/L2/SIG/11201 - ModuleA7.
The design authority shall confirm correlation is undertaken before construction work
commences on site, unless the design records bear a recent correlation date for the
current version. The other circumstances in which a waiver may be obtained from
the Route Asset Manager (S&T) are given in NR/L2/SIG/11201 - Module A7.
Correlation working copies shall be obtained from the current master record (or,
where work is in progress and it is agreed in the design specification to allow parallel
processes, from a production copy).
7.7.1 Scope
The scope of the proposed correlation, together with any responsibilities for
subsequent updating and remedial action, shall be agreed in the OPS, or equivalent,
and design specification.
Page 23 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Guidance on defining the scope of correlation, in terms of the level of detail and
method of correlating the different functional elements, is given in NR/L2/SIG/11201
- Module A7.
Where part of a record sheet requires to be correlated, correlation shall be
undertaken on the whole sheet, unless otherwise agreed in the design specification.
This does not apply to sheets containing analysis (e.g. of fuses, contacts, cable
cores or transmission channels), where correlation may be limited to the function(s)
concerned.
7.7.2 Correlation Records

All inconsistencies discovered shall be recorded and shall be verified by independent
checking.
The authority performing the correlation shall confirm that:
a) any deficiencies identified are investigated;
b) maintenance records on site are temporarily endorsed and certified with any
corrections;
c) the source records and any production copies affected by the correlation
process are corrected to the correlation copies;
d) updated security copies are supplied to the records custodian; and
e) updated maintenance records are provided within an appropriate timescale.
Where the whole of a sheet has been correlated and updated with any necessary
corrections, the date correlated and the updated version shall be entered in the last
full correlation field on the title block of the source record.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
8 Design Process
The design authority shall have in place a process for preparing complete sets of
production design details. The methodology to be used for each commissioning
shall be stated in the design specification.
The scheme plan shall be developed from the client remit and OPS or equivalent.
Control tables and engineering details shall be produced, in turn, from an approved
scheme plan and design specification.
The complete range of design details is defined in NR/L2/SIG/11201 - Module A2.
8.1 Design Objectives
The design shall seek to achieve the following objectives:
a) clear, accurate, consistent and unambiguous presentation;
b) compliance with the referenced standards (see Section 5.2);
Page 24 of 100

NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
c) compliance with the clients requirements, as reflected in the design

specification (see Section 7.5);
d) complete control of design documentation (see Section 14);
e) an appropriate level of safety (see Sections 17 and 18);
f) completeness (see NR/L2/SIG/11201 - Module A2);
g) facilitation of construction (including stagework) and testing; and
h) a functional design that is fit for purpose.
The presentation and convention to be used is given in Section 16.
8.2 Production Process
Production of alterations shall generally be undertaken on the medium for
production, which is either the source record, or a copy of the source record.
Production shall only commence when:
a) the source record has been updated to any commissioning modifications for
any alteration due to be commissioned prior to the alteration concerned,
unless the relaxation given in Section 9.1(a) is used; and
b) a security copy has been made, where necessary to record the current state
of the infrastructure between each commissioning.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
The source record itself shall only be altered when approval in principle has been
received and there is an assurance that the commissioning will take place.
There is no restriction on the creation of source records for new work, as distinct
from alterations to existing installations.
8.3 Verification and Validation Process
The checker and producer are required to adopt a systematic approach to the
checking process, so as to confirm that the design objectives (see Section 8.1) are
achieved. In particular the checker and producer are to take into account the
guidance in BS EN 61508 on validation and verification and the Hazards Forum's:
Safety-related systems: Guidance for engineers.
The independent check shall be rigorous and comprehensive, and place no reliance
on the testing process revealing any residual errors. It shall include the following
features:
a) first principles are used;
b) any assumptions made are justified;
c) hazards are identified and the associated risks controlled;
d) calculations and/or functional safety analysis are performed where
appropriate;
e) appropriate check and/or error recording processes;
f) new work and interfaces are 100% checked;
Page 25 of 100


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
g) existing installations are 100% checked in the relevant areas of circuitry or

data altered;
h) any copying of earlier designs, or use of standard computer aided design
(CAD) cells, are treated as new work; and
i) certification is provided in accordance with Section 11.
The checker and producer are required to adopt a systematic approach to
documenting the checking and error reporting processes in an auditable manner.
The methodology to be used shall be stated in the design specification.
8.4 Correspondence with Source Records
Design details shall only be submitted for acceptance or approval for construction
when the source records are in the possession of the responsible design engineer
(see Section 10). The source records shall remain in the possession of the
responsible design engineer until the final records are completed.
A relaxation is available for minor alterations where Section 15.2, cases (b) or (c),
apply.
8.5 Design Guidelines
Guidelines on the production process and methodology, including the medium for
production, are given in NR/L2/SIG/11201 - Module A8.
Guidelines on the checking process, including the documentary evidence, are given
in NR/L2/SIG/11201 - Module A21.
9 Overlapping and Parallel Design
9.1 Overlapping Alterations
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Special controls shall be implemented where it is necessary to relax the design

process to allow successive stages or alterations to follow in close succession, in the
same signal box area. Production, updating and version control shall be strictly
applied in accordance with Sections 8.2, 13.2 and 14, respectively, except as
follows:
a) the production of a subsequent alteration may be commenced as soon as any
common source records have been updated in anticipation of the previous
commissioning, provided that the same responsible design engineer has been
appointed to oversee all overlapping alterations and security copies have
been taken where necessary for record purposes;
b) source records may be updated as soon as an alteration has been checked,
provided that the same responsible design engineer has been appointed to
oversee all overlapping alterations and security copies have been taken
where necessary for production purposes.
The responsible design engineer shall be appointed by the design authority before
the design of the first alteration is commenced.
If commissioning dates have not already been defined, the responsible design
engineer shall nominate an assumed order in which the commissionings are to be
Page 26 of 100


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
treated, with reference to the draft staging and testing strategy, and tester in charge,
if appointed.
The alterations shall be designed on this basis. If the nomination proves incorrect,
each alteration shall be modified as necessary to allow for the new commissioning
order. The latest planned commissioning order shall be stated in the design
specification, or supplement thereto.
This process will be facilitated by arranging simple interfaces between each
alteration and agreeing the usage of spare fuses, cable cores and relay bases, etc.
Where (due for instance to the proximity of multiple overlapping alterations, or
limitations on competence of the design authority) it is not practicable for one design
authority to be responsible for all work, Network Rail shall appoint a responsible
design engineer to oversee all work, co-ordinate the roles of the individual
responsible design engineers, and manage their conflicting requirements in
accordance with this Standard.
Further controls relating to overlapping alterations are given in NR/L2/SIG/11201 Modules A12 & A14.
9.2 Parallel Processes
Where it is desired to run phases of a project concurrently rather than consecutively,
in order to meet compressed timescales, special controls shall be implemented by
the responsible design engineer to confirm the integrity of the processes.
A risk assessment shall be used to determine suitable and sufficient control
measures to reduce risks so far as is reasonably practicable. These shall be stated
in the design specification, or supplement thereto.
9.2.1 Processes Run Concurrently
Processes that affect more than one alteration shall not be run in parallel, except as
permitted in Section 9.1.
Examples of processes associated with a single alteration that could be run in
parallel, with appropriate control measures, include:
a) the production of control tables before scheme plan approval;
b) the production of engineering details before the control tables are checked;
c) the production of engineering details before site surveys are undertaken;
d) correlation to production copies whilst work is in progress;
e) pre-wiring apparatus housings before the engineering details are approved for
construction;
f) record updating before the commencement of construction;
g) commencing work on site before a letter of no objection to proposals is
received; and
h) other parallel processes not expressly prohibited by this Standard.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 27 of 100
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
9.2.2 Special Controls

Examples of additional controls include:
a) a tracking system to confirm that modifications generated by one process are
updated in all concurrent processes;
b) use of controlled multiple sets of modification sheets to update all overlapping
alterations, instead of revising individual drawings;
c) enhanced lines of communication between the design, construction and
testing functions; and/or
d) a means of recovery should the amount of rework escalate out of control.
9.2.3 Suitability of Parallel Processes
The benefits of running parallel processes decline rapidly as the following situations
are approached:
a) the time spent on assessing the risks and devising and implementing
additional controls outweighs the time saved by process compression;
b) it is likely that the amount of rework generated by a change in one process
(requiring rework in all the concurrent processes) will outweigh the time saved
by process compression.
Parallel processes shall not be used unless the safety risk resulting from the above
considerations is as low as reasonably practicable (e.g. unless the business cost of
not compressing timescales is grossly disproportional to the safety cost of doing so).
Parallel processes may only be used where the safety risk of delaying
commissioning by applying consecutive processes is greater than the safety risk due
to the reduced integrity of concurrent processes.
See NR/L2/SIG/11201 - Module A9, for an example of the risk calculations required.
10 Approval and Acceptance
10.1 Principle
Signalling works and systems shall undergo suitable processes to demonstrate that
they are safe, dependable and fit for purpose in the particular application and
environment in which they are to be used, before they are taken into service.
Specifically, they shall conform to the principle for approval laid down in the Grip
Manual, and comply with the Railways and Other Guided Transport Systems
(Approval of Works, Plant and Equipment) Regulations 1994 for statutory approval.
10.2 Scheme Phases
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Processes shall be in place for the content of each of the following phases to be
agreed with all necessary bodies, so as to achieve the above principle:
a) scheme plan (approval in principle);

Page 28 of 100
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
b) design specification, for acceptance by Network Rail (see Section 7.5);

c) stage scheme plan (where required for approval);
e) testing and commissioning strategy (see NR/L2/SIG/30014); and
f) the completed works (statutory approval).
10.3 Approval in Principle (Design Authority and Network Rail)
Scheme plan approval shall denote approval in principle for the scheme.
All signalling works, including stagework, require approval in principle, except for the
following:
a) maintenance works;
b) like-for-like replacements with approved equipment that do not reduce
standards of safety; and
c) other works that result in no change to the signalling plan or associated
documentation.
Network Rail shall record the approval status of the scheme in the approval and
version panel on the scheme plan (see NR/L2/SIG/11201 - Module A10).
10.3.1 Responsible Design Engineers Role
The scheme plan and ancillary information (see NR/L2/SIG/11201 - Module A2) shall
be initially approved by the responsible design engineer in confirmation that the
following items are complete:
a) the appropriate standards to be used in Section 10.2 (d) have been
referenced (see Section 5.2);
b) the scheme plan has been designed and signed by a competent person (see
Section 6.4); and
c) the scheme plan has been checked and signed by a competent person who is
sufficiently independent (see Section 6.5).
The approval copy shall then be signed by the responsible design engineer.
10.3.2 Network Rails Role
The documentation shall subsequently be submitted to Network Rail for approval.
Network Rail shall review the scheme plan to confirm that:
a) the proposed scheme is feasible, meets the requirements of the remit and the
OPS or equivalent, and is therefore fit for purpose; and
b) the safety of railway operations and safe interworking are in place, having
reviewed the proposed signalling facilities using the requirements given in
NR/L2/SIG/11201 - Module A11.
Page 29 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
d) engineering details (approval for construction);
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
10.3.3 Project Approval (Network Rail)

The project manager is required to compile a project safety case for approval by
Network Rail at certain scheme phases. This is to demonstrate that changes to the
infrastructure are designed to maintain or improve the safety of railway operations.
The following signalling documentation shall be made available to the project
manager for this purpose:
a) the health & safety plan and health & safety file (see Section 7.6);
b) any risk assessment reports and similar documentation not included in the
above (see Section 18.2); and
c) contractors safety cases.
10.4 Acceptance of Engineering Details (Network Rail)
Network Rail shall have in place procedures for the acceptance of engineering
details, including significant modifications, before construction commences.
10.5 Approval for Construction (Design Authority)
All engineering details depicted on the approval and issues record (AIR), and any
other significant modifications, require approval for construction.
Before the engineering details are issued for construction purposes (or data
installation), the engineering details shall be approved by the responsible design
engineer in confirmation that the following items are complete:
a) the scheme plan has been approved by Network Rail (see Section 10.3.2);
b) the engineering details are in conformity with the design specification (see
Section 7.5) and the testing and stagework strategy;
c) the original design parameters and assumptions stated in the design
specification are still valid;
d) the engineering details have been designed and signed by a competent
person (see Section 6.4);
e) the engineering details have been checked and signed by a competent person
who is independent (see Section 6.5);
f) the interdisciplinary engineering details have been additionally checked and
signed by nominated responsible engineers/managers in each relevant
discipline;
g) the source records are in the possession of the responsible design engineer;
Page 30 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
The approval copy shall then be signed for Network Rail production, i.e. for the
operation of trains and signal boxes (including compatibility with trains that have
route acceptance), and for Network Rail local infrastructure, i.e. for infrastructure
compatibility and policy (all disciplines).
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
h) the standards referenced on the scheme plan are set out on a certificate of
compliance, together with a statement of any non compliances (see Section
5.2);
i) all health and safety risks have been assessed and appropriate control
measures introduced, in accordance with the Construction (Design and
Management) Regulations 1994 (see Section 17);
j) the signalling system depicted on the engineering details provides an
adequate level of safety for railway operations (see Section 18);
k) the signalling system depicted on the engineering details consists of approved
sub-systems and equipment working within their application criteria (see
NR/L2/RSE/100);
l) any application safety cases required have been accepted (see Section 18.3);
and
m) any software used in a safety-related system provides an adequate level of
safety and is suitably validated (see NR/L2/SIG/11201 - Module A11).
Approval status shall be recorded in the approved for construction column on the
AIR, which shall be signed by the responsible design engineer, as described in
Section 14.5.
10.6 Statutory Approval (HMRI)
Signalling schemes shall be approved in accordance with the HMRI Guide to the
Approval of Railway Works, Plant and Equipment.
All signalling works require statutory approval, except for the following:
a) maintenance works;
b) like-for-like replacements with approved equipment that do not reduce
standards of safety;
c) signal sighting amendments;
d) level crossings for the sole use of employees;
e) stageworks where the overall scheme is programmed to extend over less than
18 months from the first commissioning, or where temporary stageworks are
to be in use for less than 6 months; and
f) works covered by the Interoperability Regulations (see Section 10.7.5).
Network Rail shall record the approval status of the scheme in the approval and
version panel on the scheme plan (see NR/L2/SIG/11201 - Module A10).
10.6.1 Major Works
Network Rail shall submit outline proposals for major works, including the scheme
plan and design specification, to HMRI, together with equivalent documentation for
any other discipline involved, and agree timescales for further submissions. A letter
of no objection to concept shall be obtained before detailed design is commenced.
Page 31 of 100
--``,``,,`,,,`,`,


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
HMRI generally consider new railways and larger schemes on existing railways as
major works. However, the following are generally regarded as minor works:
a) signalling works associated with minor track alterations (unless affecting the
layout risk model);
b) the transfer of control from one signal box to another (unless altering the
interlocking);
c) the removal or inhibition of signalled routes; and
d) simple temporary level crossings.
10.6.2 Level Crossing Works
In the case of work on a level crossing, at a public vehicle road, an order shall be
made under the Level Crossings Act 1983, as amended by the Level Crossings
Regulations 1997, before the level crossing protection arrangements are altered.
10.6.3 All Works

Before work is started on the railway, unless a timescale has been previously
agreed, Network Rail shall submit detailed proposals to HMRI for all works requiring
statutory approval. A letter of no objection to proposals shall then be obtained. The
documentation to be submitted for a signalling scheme generally consists of the
following:
a) design specification;
b) a list of the standards referenced on the scheme plan set out on a certificate
of compliance, together with a statement of any non compliances;
c) a statement of the level of safety provided (see BS EN 50129);
d) scheme plan (including a site plan);
e) for a level crossing, the level crossing ground plan, as required by HMRI;
f) for a new signal box or other building, general arrangement, plan and
elevation drawings;
g) control tables;
h) details of any non standard features;
i) any undertaking in respect of single line control; and
j) certificates of conformity for new sub-systems and equipment (including
software) that are type approved, or a safety case (see Section 18.3), in order
to gain type approval.
Page 32 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
The signalling works associated with the level crossing require statutory approval in
the standard way.
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
10.6.4 Inspection and Taking into Use
Works may not be taken into use until approval has been granted, unless this would
cause severe disruption to train services. However, it is usual for a formal inspection
to be conducted after works have been brought into use as a precursor to the
granting of statutory approval.
Any remedial design work following formal inspection shall be undertaken as if it
were a separate signalling alteration.
10.6.5 Interoperability
Works covered by the Interoperability Regulations (see references) require
assessment by a Notified Body.
For these works, approval by HMRI under the Railways and Other Transport
Systems (Approval of Works, Plant and Equipment) Regulations is not required.
11 Design Changes
11.1 Scheme Plan Amendment
Significant amendments to the scheme plan, subsequent to approval in principle,
shall be subject to re-approval. Note that compliance to subsequently introduced or
revised Railway Group Standards or Company Standards may be required, in
accordance with the new approval date.
Relevant changes shall also be submitted to HMRI.
Scheme plan changes shall be recorded and certified in the approval and version
panel, where each amendment shall be given a consecutive amendment letter. The
reasons for each change shall be recorded in the design specification, or supplement
thereto.
Guidelines on scheme plan version control are given in NR/L2/SIG/11201 - Module
A10.
11.2 Modification to Engineering Details
The design authority shall have in place a process of post-production modification
version control and associated documentation. To confirm:
a) unique identification of each modification;
b) full traceability and configuration control;
c) accurate and complete maintenance records on site at all times;
d) expeditious updating of final records;
e) compatibility with construction procedures, to enable installers to record the
extent of work completed; and
Page 33 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Following completion of the works, a certificate of completion of railway works, plant

or equipment requiring approval shall be submitted to advise that the works are
ready for inspection.
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
f) compatibility with testing procedures (see NR/L2/SIG/30014).

Testing procedures require every modification issued after the test copy to be
registered by obtaining a test log number from the tester in charge.
Guidelines on the methodology, version recording and issuing details to suit differing
construction and testing phases are given in NR/L2/SIG/11201, Module A12.
Modifications to engineering details shall be approved for construction in the
standard manner on the AIR (see Section 14.5). The reasons for any significant
change shall be recorded in the design specification. Where changes to safety
cases are necessary, see Section 18.3.2.
12 Certification and Issue
12.1 Certification of Design Details
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Design details shall be identifiable to producer and checker in an auditable manner.

Certification shall take the form of printed and signed initials, and date. These shall
be added to the master record and, where applicable, to copy prints, but the source
record shall bear no certification.
Guidelines on certification are given in NR/L2/SIG/11201, Module A13.
12.2 Issue of Production Details
The design authority shall have a process in place to confirm the timely issue of
production design details for approval, interdisciplinary checking, construction and
testing purposes. Issue copies shall be certified to demonstrate correspondence
with the production office copy (including colour balance where applicable) and the
AIR.
The source records shall be in the possession of the responsible design engineer at
the time the production copies are issued for construction, until the final records are
completed. (For relaxations, see Section 15.2.)
12.3 Issue of Record Details
A process shall be in place to confirm the timely issue of signalling records for
correlation and maintenance purposes, as described in Section 13.2. Issue copies
shall be certified to demonstrate correspondence with the master record and index.
13 Maintenance of Records
The management processes for those responsible for either production, ownership,
custody or use of records shall be in accordance with NR/L1/INF/02232 and the
supporting standards, NR/L2/INF/02018.
13.1 Security and Durability
Network Rail shall confirm that procedures are in place to maintain security and
prevent unauthorised use of records. Recipients of source records shall keep them
in a secure environment and prevent unauthorised use.
Page 34 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
The design authority shall confirm that the medium for records maintains the security
of information and that the durability is commensurate with the life time of the
records. It shall also be capable of delivering a print of consistent intensity that is fit
for purpose. The durability of site records shall be commensurate with the
environment in which they are to be kept.
Network Rail shall confirm that compatibility can be maintained, particularly for data
storage, through developing technology. See also Section 14.7.
13.2 Updating of Records
The design authority shall have in place a process of record updating to suit
construction and modification phases.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
So as to simplify the modification process, source records that require updating shall
not generally be updated prior to commencement of construction, unless the
relaxation for overlapping work, given in Section 9.1(b), allows it.
Maintenance records on site shall be maintained up to date with the current state of
the infrastructure at all times. When it is necessary to endorse a previous
maintenance copy with a modification (or correction as in Section 7.7.2, or alteration
as in Section 15.2) in order to provide a temporary maintenance copy, this shall be
replaced with a final record copy within an appropriate timescale. When source
records are retained by the design authority after commissioning, in order to create
the final records, a security copy shall be supplied to the records custodian.
Final records, including the source record, signed master record and AIR, shall be
provided to the records custodian within 6 weeks of stageworks or final
commissioning, unless otherwise agreed in the design specification.
Guidelines on updating are given in NR/L2/SIG/11201, Module A14.
13.3 Handover and Handback
Network Rail shall have in place procedures to control the exchange of source
records between records custodian and design authority. These procedures as a
minimum shall confirm:
a) the completeness of returned items to the records custodian;
b) the validity of returned items;
c) the quality of returned items;
d) evidence of accuracy and approval.
Any superseded source records shall be returned to the records custodian for
cancellation.
14 Configuration Control
14.1 Identification of Design Details
All types of design details shall be uniquely identifiable.
Page 35 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Drawings shall be identifiable by means of a title block that is an integral part of the
design. A standard drawing template with border and title block shall be supplied to
the design authority by the records custodian. The title block shall contain, as a
minimum, the following information:
a) drawing number (see Section 14.2);
b) current version;
c) issue date;
d) last full correlation date and updated version;
e) name of infrastructure Manager i.e. Network Rail;
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
f) name of records custodian;

g) signal box or control point;
h) interlocking control area;
i) design detail type and/or description;
j) scale and other notes, as necessary; and
k) space for use on production copies for design authority name, reference
number and certification.
Certain types of design detail, e.g. those maintained on data storage media, may be
identified with simplified title blocks or labels.
Guidelines are given in NR/L2/SIG/11201 - Module A10.
14.2 Numbering System
Design authorities shall have in place a procedure for the unique numbering of
scheme plans (and other drawings commenced prior to approval in principle), with a
capability of linking multiple drawings and identifying amendment status (see Section
11.1).
The records custodian shall specify the unique numbering of all signalling design
details that reflect the current state of the infrastructure, with a capability of
identifying the last alteration and modification status (see Section 14.5). The design
authority shall request such numbers, as necessary, from the records custodian.
See Section 5.1 for alterations to existing drawings.
14.3 Indexing
A fully comprehensive system of indexing all signalling design details shall be
provided, that incorporates the current version of each document. Index sheets shall
be provided for each group of design details, grouped both by geographical area
and, where appropriate, by type. Geographical grouping shall generally be to
interlocking areas, so as to facilitate the guidelines of NR/L2/SIG/11010, but detailed
guidance is given in NR/L2/SIG/11201, Module A15.
Guidelines on the presentation of index sheets for both production and record
purposes are given in NR/L2/SIG/11201 - Module A10.
Page 36 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
14.4 Closure Lists

Index sheets shall also make provision for use as closure lists to define the version
of design details to be used in the testing activity. Where work is apportioned, a
separate closure list shall be provided for each stage and for each work package.
The timescale for the issue of closure lists shall be stated in the design specification.
Any modification required after the issue of the closure list shall be controlled in a
manner agreed with the tester in charge, generally by registering a test log number.
14.5 Change Recording
A system of engineering design version control shall be provided to give unique
identification and full traceability for each alteration and each modification state
associated with an alteration. (For version control of scheme plans, and other
drawings commenced prior to approval in principle, see Section 11.1.)
For this purpose, a designer shall prepare an AIR sheet for each alteration, generally
for a particular interlocking area. Separate rows shall be used for each modification
state issued and also for the issue of the closure list and the issue of maintenance
records.
The following columns shall be provided:
a) version - alteration letters (to identify the commissioning) supplied by the
records custodian;
b) version - change number (to indicate the modification state);
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
c) description of the change;

d) drawing numbers issued;
e) approved for construction;
f) prepared for issue; and
g) distribution list.
The responsible design engineers signed and printed initials and date in the
approved for construction column shall signify that approval has been received for
the appropriate row, in accordance with Section 10.6. The prepared for issue
column shall be similarly certified to demonstrate correspondence of the appropriate
row with the sheets being issued, that they have been approved for construction and
that each individual sheet has been certified in accordance with Section 12. For
traceability, the name of the design authority shall appear in the title block of the AIR
sheet.
The entry for the final issue of records shall confirm that all changes including post
commissioning modifications have been incorporated in the issue.
Guidelines on change recording are given in NR/L2/SIG/11201 - Module A10.
Page 37 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
14.6 Software Control

Data driven systems shall be controlled in an equivalent manner to that described in
Sections 14.1 to 14.5. Newly introduced systems shall conform to BS ISO/IEC
90003 and BS EN 50128.
In particular, means of identifying a version of software to the infrastructure alteration
shall be provided, generally in the form of a software status record index sheet to
accompany the data storage medium.
When undertaking alterations, the design authority shall confirm that software /
hardware Interfaces are compatible.
Guidelines on software approval are given in NR/L2/SIG/11201 - Module A11.
14.7 Software Drawing and Data Tools
Configuration control shall also be provided for software design tools and templates.
Data filenames shall be identifiable to the electronic system and sub-system and
shall include the version and sub-version.
CAD production design files shall include the drawing number and alteration letters,
but not the change number, in the filename, so as to confirm that only the latest
version of the alteration is retained.
Guidelines on the control of CAD files are given in NR/L2/SIG/11201 - Module A8.
Where necessary to confirm onward compatibility through developing technology,
the records custodian shall specify software to be used for the production and
storage of design details in electronic form.
The generic requirements for different types of data are given in Appendices A to D.
Guidelines for layout plans and other types of design details are given in
NR/L2/SIG/11201, Module A15.
In addition, software tools used in the production of newly introduced safety-related
data driven systems, including both the system program and the geographical data,
shall conform to BS EN 50128.
14.8 Systems and Equipment
To confirm that new signalling systems are comprised only of sub-systems and
equipment approved in accordance with NR/L2/RSE/100, and to enable them to be
managed to confirm continued conformance with the Standard, approval and
application criteria for their whole life-cycle, the sub-systems and equipment shall be
uniquely specified in the design details, together with any ancillary information
necessary to define the application criteria. As a minimum, the following information
shall be provided:
a) equipment type, style, Standard number or approval identification;
b) modification state or Standard version; and
c) coding configuration, where applicable.
Guidelines on the means of showing this information on design details are given in
Page 38 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
When undertaking alterations, the design authority shall confirm that system and
sub-system interfaces are compatible, and that the safety integrity of a system is not
degraded by an interface of a lower safety integrity.
15 Special Cases of Design Production
15.1 Special Control Measures
Network Rail and the design authority shall agree the application of special controls
to confirm the accuracy of records, and the safe progress of work, in the following
situations:
a) where a commissioning is cancelled or re-ordered;
b) where records are known to have been updated to a previous alteration that
was never carried out;
c) where alterations in the same signal box area are required to take place in
close succession (the special controls to be applied in this case are given in
Section 9.1);
d) where processes are run in parallel in order to meet reduced timescales (see
Section 9.2).
15.2 Relaxations
Certain relaxations in the production and issue processes are permitted in the
following special cases:
a) temporary work, to allow temporary alterations to be undertaken without
altering the source records, provided they are held;
b) non conceptual work, to allow minor alterations to be made on maintenance
records without holding the source records; the records custodian to be
informed of the alterations within 48 hours;
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
c) genuinely like-for-like work, to allow minor renewals to be shown on

maintenance records without holding or altering the source records.
In the last two cases, design specification and approval may be dispensed with,
provided the work is undertaken in accordance with a recognised method statement.
There is no relaxation from the requirement for independent checking and testing
(see NR/L3/SIG/11231).
Guidelines are given in NR/L2/SIG/11201, Module A1.
Relaxations in the technical requirements for temporary work are given in
Page 39 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
15.3 Stagework
Each stage to be commissioned on a separate date shall be treated as a separate
alteration (with a separate stage scheme plan where applicable). A separate set of
design details shall be produced for each stage, irrespective of the timescale
between stages.
If it is necessary to divide work for one stage into separate packages because of
external safety-related constraints, such as possession availability, each package
shall generally be treated as a separate alteration. However, a number of work
packages may be issued as a single alteration if all the following apply:
a) the packages are independent of each other (i.e. may be undertaken in any
order without affecting the others), as regards design, installation and testing;
b) installation activities present a low risk (as a minimum, the correlation
requirements have been satisfied);
c) none of the packages are part of a multi-stage project;
d) each package is clearly and suitably identified on the design details;
e) maintenance record copies are provided and annotated at each juncture, in
accordance with NR/L2/SIG/11201, Module A1, to show which packages have
been brought into use; and
f) the issue of multiple work packages as a single alteration is identified and
agreed in the design specification.
Relaxations for overlapping alterations are given in Section 9.1.
Guidelines on the presentation of partially commissioned circuitry are given in
Generally, circuits, cables and equipment made redundant by the abolition or change
of facilities shall be shown to be removed in full on design details, as described in
NR/L2/SIG/11201 - Module A2. (Spare terminals, etc., with all wiring removed are
generally shown left in situ as they can be reused. Where cable cores become
spare as a result of circuit alterations, disconnection links at intermediate locations
and their associated jumpers shall be shown removed from the terminals.)
However, an exception may be granted to allow out of use circuitry and equipment,
where wiring remains connected, to remain in situ, in certain special cases described
in NR/L2/SIG/11201, Module A16.
All out of use equipment, fuses and links shall be permanently labelled as such. A
note to that effect shall be provided on the design details.
Guidelines on the presentation of out of use circuitry are given in NR/L2/SIG/11201,
Module A1.
Page 40 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
15.4 Recovery of Redundant Assets
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
16 Presentation and Convention

Design details shall be produced in a form that facilitates the provision of a
comprehensive set of design records.
Guidelines on the arrangement, minimum requirements and conventions for specific
types of design details are given in NR/L2/SIG/11201, Module A15.
See Section 5.1 for alterations to existing drawings.
16.1 Sizes and Clarity
Drawings shall generally comply with metric sizes, unless otherwise specified by the
records custodian.
Fonts used shall distinguish between numerals and letters, and shall be legible
under all expected site conditions.
The layout of drawings shall allow sufficient room for construction and testing staff to
mark the progress of their work by the application of tick marking and, where
practicable, for designers to add modifications.
Guidelines are given in NR/L2/SIG/11201, Module A15.
16.2 Colour Presentation
Red and green colouring shall generally be used on production copies of design
details to indicate changes as follows:
Red
= new equipment to be installed or commissioned.
Green = redundant equipment to be recovered.

Guidelines and special conventions are given in NR/L2/SIG/11201, Module A15.
The design authority shall have in place a process for preparing production design
details in red and green, either on the same sheet by means of the one drawing
method, or on separate sheets by the two drawing method.
Guidelines on the production process are given in NR/L2/SIG/11201 - Module A8.
16.3 Symbols and Format
Symbols used on design details and their format shall comply with the following
standards, except where covered by an explanation on the drawing or reference
sheet:
a) layout plans - NR/L2/SIG/11201, Module A17;
b) control tables - NR/L2/SIG/11201, Module A18;
c) signalling control centres - GK/RT0025; (as mandated by TI 157)
d) circuit diagrams - NR/L2/SIG/11201, Module A19;
e) bonding plans - NR/L2/SIG/11201, Module A17;
f) level crossing ground plans - NR/L2/SIG/11201, Module A1 and X02;
g) mechanical locking charts - to be identified on each drawing;
h) other mechanical drawings - BS 8888;
Page 41 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
i) other manufacturing or construction details, including power distribution plans

and drawings with electronic or telecommunication components - BS EN
60617 and BS EN 61082;
j) risk and reliability models - BS 5760.
16.4 Units and Dimensions
Numerical units and dimensions shall generally conform to BS ISO 80000-1, using SI
units (Systme International dUnits) wherever practicable.
Guidelines on layout plans are given in NR/L2/SIG/11201, Module A15.
17 Health and Safety
In the design of signalling systems, provision shall be made for the health and safety
of personnel at risk (e.g. installers, testers, maintainers and operators) by means of a
systematic approach to task risk assessment, in accordance with the Management of
Health and Safety at Work Regulations 1999 and the Construction (Design and
Management) Regulations 1994.
See also NR/L2/INI/CP0047 and NR/GN/CPR/401 for application of the regulations.
Three options are available for each identified hazard so as to reduce the risk to be
as low as reasonably practicable, balancing the cost with the degree of risk reduction
achieved. The following are in order of effectiveness:
a) eliminate the hazard from the design;
b) general control by isolating from, or minimising the risk within the design; or
c) individual control by procedures, training and provision of personal protective
equipment.
Where risks cannot be eliminated at source, additional information shall be provided
in health and safety plans, and/or noted on design details to help staff manage the
risks.
A table of general examples is given in NR/L2/SIG/11201 - Module A5. Designers
shall take notice of these examples in the design of signalling works.
Detailed guidance on particular hazards is given in NR/L2/SIG/11201, Module A6.
18 System Safety
The means of demonstrating safety shall be stated in the design specification and
can include one or more of the following processes:
18.1 Functional Safety Analysis
When applying, or interfacing, established circuit and system principles in a manner
which has not been catered for in those circuits or systems, due note shall be taken
of the effect of the following upon the resulting system:
Page 42 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
a) relay and solid state time constraints;

b) transmission time constraints;
c) repeat relay circuitry;
d) interlocking boundaries;
f) power interruptions;
g) any deviations from the original design assumptions;
h) other failures; and
i) other significant hazards.
The objective is to demonstrate that the system attains the required safety integrity.
The parameters and considerations to confirm the integrity of safety critical circuitry
are given in NR/L2/SIG/11201, Module B3.
Where the issues are sufficiently complex to warrant it, a risk assessment shall be
undertaken.
Documentation shall be prepared, recording these effects (with supporting
calculations, where necessary) which will provide an audit trail of the designers
conversion of the scheme plan and control tables into engineering details.
An application example is given in NR/L2/SIG/11201 - Module A9.
18.2 Risk Assessment Techniques
Risk assessment is a useful design tool for determining which control measures are
likely to give the greatest safety benefit in terms of the cost incurred, and
demonstrating that sufficient mitigation has been applied for the residual risk to be
acceptable.
Risk assessment shall be preceded by a process of hazard identification that
systematically considers all possible system interactions (both internal and external)
and is commensurate with the degree to which the system is already proven in
operation. Novel systems, applications or environments require a team-based
approach, such as a hazard and operability study (HAZOP).
In practice, risk assessment techniques shall be applied to signalling works and
systems as follows:
a) in selecting an appropriate type of signalling system;
b) wherever systems or interfaces are proposed that have no applicable code of
practice and no established safety record;
c) in assessing hazards associated with the application or environment in which
the system is to be used, particularly where there is any deviation from the
original design assumptions;
Page 43 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
e) location interfaces;
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
d) when it is proposed to alter an installation that does not conform to current

standards;
e) wherever temporary alterations are proposed;
f) where the adequacy of current or previous practices is in doubt;
g) wherever a Railway Group Standard or Company Standard requires risks to
be assessed;
h) where required by the Infrastructure Manager i.e. Network Rail; or
i) to achieve a safe method of work (see Section 17 for task risk assessment).
The responsible design engineer shall confirm that all risk assessments are fully
documented. The degree of detail in the risk assessment shall be commensurate
with the degree of change.
An application example is given in NR/L2/SIG/11201 - Module A9. General
guidance on the assessment of risk is given in NR/L2/HSS/020.
18.3 Safety Cases
Safety cases facilitate the granting of safety approval and record how safety risks are
identified, managed and controlled. NR/L2/HSS/020 explains the degree of change
that should be managed by means of a safety case. The following categories of
safety case are described in BS EN 50129:
a) specific application safety case for the design and implementation of a whole
system at a particular installation (see Section 10);
b) generic application safety case for a particular architecture of sub-systems
with a wide application, for systems approval; and
c) generic product safety case for a particular item of equipment with a wide
application, for type approval (see NR/L2/RSE/100).
18.3.1 Safety Case Content
a) a description of the activity; and
b) a risk assessment, i.e. hazard identification and assessment of the
consequences.
A safety case shall generally also contain evidence of safety, including verification at
various phases of development and validation of the final product to the initial
specification. (The design process of verification is laid down in Section 8.3 and the
testing process of validation in NR/L2/SIG/30014.)
The format given in BS EN 50129 shall be used wherever practicable, so as to
facilitate cross acceptance and hence expedite the approval process.
Page 44 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
The minimum content of a safety case is summarised as:
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
18.3.2 Controlling Changes

Subsequent significant changes or modifications shall be controlled in a similar
manner, such as:
a) by means of a supplementary safety case (e.g. for infrastructure works); or
b) by amending the original safety case (e.g. for a product).
(However, changes that are not significant need only be risk assessed by the design
authority and Network Rail informed.)
18.4 Historical Operating Experience
The safety integrity of systems and software may be based on historical operating
experience instead of probabilistic considerations. This approach requires certain
periods of hazard-free experience (depending on the safety integrity level
applicable).
Provided that any known deficiencies are addressed, it may be assumed that an
existing system with a reasonable historical base meets the requirements of this
approach.
For this method to be valid, the following shall be true:
a) the operating experience relates to the same version or modification state of
the system;
c) the operating environment and design parameters are equivalent.
(However, deviations that are not significant need only be risk assessed by the
design authority and Network Rail informed.)
This approach may also be used to demonstrate a higher achievable safety integrity
level than that originally predicted.
19 Dependability
Safety will not generally be achieved unless an acceptable level of dependability, i.e.
reliability, availability, maintainability and safety (RAMS), is incorporated within the
design.
19.1 The RAMS Concept
Safety and availability are attributes of dependability that directly affect the quality of
the railway service and any impairment will cause a hazard, or disruption,
respectively. Reliability, or degree of freedom from failures, supports both safety and
availability. Maintainability, or ease of prevention or correction of faults and failures,
supports reliability and availability.
Page 45 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
b) the application of the system is the same; and
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
The architecture of the system hierarchy is significant. A fault condition within a subsystem may cause that sub-system to fail. A sub-system failure may cause the
whole system to fail, or, depending on the system architecture, another sub-system
may be capable of maintaining the availability of the system. A system failure that is
unprotected may cause a safety hazard. Once a fault state exists within a subsystem, its maintainability affects whether that state can be detected and restored
before a system failure occurs. System architecture is considered further in
GK/GN0802.
Details of a Standard that will satisfy the RAMS requirements and optimise the
RAMS combination throughout a system life-cycle are given in BS EN 50126.
Further guidelines on dependability are given in NR/L2/SIG/11201, Module A20.
19.2 Availability
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Where non-availability presents a safety hazard, e.g. where trains would have to be
called past signals at danger, and otherwise where determined by Network Rail, the
risk-based approach shall be extended to include availability, requiring safety risks to
train operations to be reduced to an acceptable level by improving availability.
The following techniques shall be used where it is necessary to improve the
availability of the signalling system:
a) The primary means is to reduce random hardware failures by improving the
reliability of system components.
b) The secondary means is to build redundancy into the system architecture, or
provide diverse systems.
c) The tertiary means is by graceful degradation.
Risk assessments similar to that described in NR/L2/SIG/11201 - Module A9, may
be performed in order to demonstrate the suitability of the technique chosen.
Availability enhancement techniques are considered further in GK/GN0802.
19.3 Reliability
Signalling systems shall be designed to be as reliable as reasonably practicable, so
as to:
a) minimise failures that contribute to a degradation in the safety of the signalling
system;
b) maximise operational availability; and
c) minimise the life-cycle cost of the system.
d) Maintainability
Design features that assist preventative and corrective maintenance shall be
considered with the Route Asset Manager (S&T), in conjunction with the forming of
his future maintenance policy.
Ease of maintenance will maximise operational availability by reducing recovery
times after failure and minimise the life-cycle cost of the system.
Page 46 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
20 Retention of Documentation
Documentation solely associated with the production and checking process shall be
retained by the design authority for six months after commissioning or, where
applicable, until Her Majestys Railway Inspectorate (HMRI) have inspected and
reported on the works, whichever is the later.
Documentation associated with the approval of systems and equipment shall be
retained in accordance with NR/L2/RSE/100.
For the medium for retention, see Section 13.1.
Page 47 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Documentation associated with the signalling system, including its design, operation
and maintenance, shall be retained on the health and safety file for the life of the
installation (see Section 7.6.2).
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Appendix A
Signalling Design Records CAD Data Requirements
This appendix (formerly LSS01) details the requirements of NR/L2/INF/02018, with
respect to CAD data, both production and handback.
It specifies:
the CAD software and associated Network Rail supplied resources to be used;
and
the media and format acceptable for returned data.
This instruction applies to CAD source documents handed back to the Custodian of
Signalling Records.
During production it need not be applied provided that before handback all data,
filenames and directory structures are altered to comply.
A.1 CAD Software Requirements
CAD source documents shall be returned to the Custodian of Signalling Records in
Bentley Microstation (.dgn) file format.
If the design is performed using another CAD package the design authority shall
check the data after the translation to Microstation format to confirm the success of
the translation and the conformity of the data to this standard especially with regard
to the location of text. The design authority shall be responsible for the creation and
use of borders equivalent to those specified in Section A.5.2, below.
Cells and symbols used shall conform to relevant standards (see Section 16.3 of this
Standard).
Signalling Plans shall be drawn using intelligent software which allows for change of
scale and mileage within a design and the measurement of signal to signal distances
and which is fully compatible with the Custodian of Signalling Records existing
Microstation drawn CAD plans.
Any additional CAD software or extensions shall be authorised, in writing, by the
Custodian of Signalling Records before use.
A.1.1 Other File Formats
The design authority shall ascertain when inspecting the records during the tender
process whether any of the electronic source drawings are in a non-Microstation
format. Any such records which are amended shall be redrawn as Microstation files.
There are few such files.
A.1.2 Raster Files
Raster files shall not be used without prior written authorisation by the Custodian of
Signalling Records.
A small number of historical source documents are hybrid raster/vector files. Special
arrangements may be required for amending these files. The preferred solution is to
redraw as vector files.
Apply to the Custodian of Signalling Records for details.
--``,``,,`,,,`,`,```,,`,,`,````

Page 48 of 100
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
A.1.3 Network Rail Supplied Resources

Standard borders and fonts are specified by the Custodian of Signalling Records and
are provided in Microstation format.
The following resources are provided to be used with Microstation :
library
b) rt_a0.dgn -
seed file for A0 drawings
c) rt_a1.dgn -
d) rt_a2.dgn -
e) rt_a3.dgn -
f) rt_a4.dgn -
g) rt_air .dgn
h) plseed2d.dgn
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
a) rt_font.rsc- font
seed file for AIR sheet (optional)

seed file for signalling plans
i) plborder.dgn border reference file for signalling plans

j) rt.cel k) rt.lis
cell library of A0-A4 borders and other cells
l) rtcel.dgn -
listing of rt.cel
drawings showing cell library contents
These resources shall be used unaltered and no other such resources may be used
without written authority of the Custodian of Signalling Records. (This shall not be
withheld unreasonably.) Where additional resources have been authorised they
shall be supplied to the Custodian of Signalling Records on handback of the data.
A.2 Records Return
Only the CAD data which is the source document accompanying a master record is
to be returned.
The CAD files of Records of Change (ROC) Sheets or Approval and Issues Record
(AIR) Sheets shall not be returned to the Custodian, nor should project files such as
scheme plans.
A.2.1 Media
The preferred media for issue and handback of CAD data is Compact Disc readable
by standard PCsMS-DOS PCs. Multi-session CDs may be used.
3 1.44 MB MS-DOS floppy discs may be used for small quantities of data. PKZIP
may be used to compress the data.
The filenames and directory structure of returned data shall be as specified below.
If neither of the above options are available then the Custodian of Signalling Records
can accept data written by the UNIX CPIO command on 8mm low density Exabyte
tapes. Full command details shall be listed on the tape label.
Due to variations between different types of UNIX a compatibility test shall be
performed before such tapes are acceptable i.e. the contractor shall supply a
Page 49 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Any other media shall be used only with prior authorisation in writing from the
Custodian of Signalling Records.
A.2.2 Data Listing
All returned media shall be accompanied by a data listing containing the names and
directory structure of the files and the corresponding drawing numbers.
Details of savesets, zip files and any compression used shall also be supplied.
Files which have been renamed shall also be listed with both old and new names
shown.
A.3 File Naming and Directory Structure
A.3.1 File Names
CAD filenames shall follow MS-DOS naming conventions with the extension dgn,
i.e. up to 8 characters.dgn
Directory names shall be 8 or fewer characters with no extension. Longer filenames
shall be permitted as circumstances permit.
CAD filenames shall be clearly and logically derived from the drawing number of the
signalling record. The combination of directory structure and filename shall fully
describe the signalling record. The version of the drawing is not required as part of
the filename of the source document.
Only one drawing shall be contained within each design file.
A.3.2 Directory Structure
The directory structure to be used for returned CAD files shall be that of the Records
Centre storing the Signalling Records as, for historical reasons, there are differences
in structures between Records Centres.
See Section A.6 for details of the requirements of each Records Centre.
A.4 Fonts
The font library, rt_font.rsc, supplied contains fonts which have been used in the
past. The preferred font for new work is font 50. Other fonts can be used for
conformity with existing work or when appropriate.
Font 50 has been improved by Bombardier Transportation (formerly Adtranz Signal
Ltd) who have given permission for Network Rail to distribute it for use on Network
Rail projects. This replaces the existing font 50 in the library.
Page 50 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
sample data tape and the Custodian of Signalling Records shall be able to extract
the data.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
A.4.1 Modification to Font 50

a) Minor changes to character formation to improve clarity:
ASTERISK *
Made larger
HASH # Made larger
Capital Q Q Tail made longer
b) The full Greek alphabet, both upper and lower case, and useful symbols such
as greater than or equal to have been added.
To place the extended characters use /nnn in the text string
where nnn is taken from the table below.
UPPER CASE
\197
\198
\199
\200
\201
\202
\203
\204
\205
\206
\207
\208
\209
\210
\211
lower case
\229
\242
\230
\243
\212
\231
\244
\213
\232
\245
\214
\233
\246
\215
\234
\247
\216
\235
\248
\217
\236
\249
\218
\237
\250
\219
\238
\251
\220
\239
\252
\221
\240
\253
\222
\241
\254
Table A.1 Adtranz Font 50 - Extended Characters
Symbols
\190
\191
\192
\193
\194
\195
\196
A.5 Drawing Standards

These specify the minimum good practice to be used to allow the data to be easily
amended by different design authorities.
All design details shall be contained within the design file. The border shall be a
Network Rail supplied cell located and locked on level 63.
Reference files, for borders or otherwise, are not to be used without special written
authority from the Custodian of Signalling Records.
A.5.2 Borders
The borders supplied by the Custodian shall be used either as seed files or from the
cell libraries.
The borders of existing drawing shall be replaced as they are amended by the
design authority. It may be necessary to unlock the existing border.
Borders are to be placed on level 63 and locked.
Page 51 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
A.5.1 Reference Files
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
If level 63 is used for design details then the details shall be moved to an available
level and the border placed on 63.
For new drawings the border is placed with the lower left hand corner at 0,0. For
existing drawings the border is placed coincident with the drawing. Slight
modification of the drawing may be necessary to confirm clarity.
A.5.3 Levels
Historical CAD data held by the Custodian contains many different level structures
which are not documented.
This makes it more difficult for unfamiliar designers to amend them.
Details of the level structure used by the design authority shall be supplied with the
returned records to the Custodian. These details shall indicate the levels used, the
purpose for each level and which levels are unused or not printed for the Master
Record. This level structure shall be consistent and all returned records shall
conform to it. The level structure may specify different levels to be used for the
various types of signalling record i.e. for wiring and plans.
If the design authority maintains a standard level structure then this may be supplied
once to the Custodian and referred to by each Records return.
Details of any level structure used, which indicates non printing levels, shall be
placed below the title block and outside the border in construction class in each and
every design file. This shall be applied to existing data as it is amended.
In the absence of a formal level structure all design details (with the exception of the
border on level 63) shall be on level 1.
Details of some of the level structures used in the past can the obtained from the
Custodian of Signalling Records.
A.5.4 Scaling
The borders as supplied are drawn at a 1:1 scale i.e. the A3 border is 420mm x 297
mm.
Printing an A3 border on to A3 cut paper automatically shrinks the border (or cuts off
an edge) by an amount dependant on the plotter but typically a few millimetres
(similarly for other border sizes).
a) Non Scaled Drawings
For non scaled drawings this is not normally significant. The design authority
shall confirm that the resultant print conforms to relevant standards as regards
clarity, accuracy and ambiguity particularly with respect to text. All such drawings
shall be printed on the correct sized media as close to the true border size as
possible for the plotter being used.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 52 of 100
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
b) Scaled Drawings
It may be necessary to plot scaled drawings on oversized paper which is then cut
down. If this is not possible then the border may be shrunk slightly to fit by the
designer. Details of the new border size shall be placed within the border, below
the title block, next to and the same size as the existing text CAD A3(or
whatever the paper size is) and of weight 0 i.e.
X=290mm, Y=205mm CAD - A3
c) It is permissible to cut off part of the outer border when plotting onto cut
sheets providing the message CAD GENERATED: ALTERATIONS TO BE
MADE ON DESIGN FILE ONLY still appears clearly on the plot.
A.5.5 Drafting Technique
a) The enter data fields in the cell title shall be used for the title block
information.
b) All design files shall be compressed before return using the Microstation
compress design command.
c) All unnecessary elements both inside and outside the border shall be
removed before return.
d) All design files shall have their setting saved with view 1 displayed on with the
title block clearly readable before return.
e) Design shall generally be performed using grid and unit locks.
f) The Microstation default linestyles shall be used.
g) Unless the Master Print is coloured all printing elements in a design file shall
be colour 0, black.
0 black (in Microstation this is generally displayed as white as the

background is dark)
1 dark blue
2 green
3 red
4 yello w
5 purple
6 orange
7 light blue
i) Construction class shall not be used for details which appear on the Master
Record.
j) Shared cells shall not be used.
Page 53 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
h) If the source document returned to the Custodian contains coloured elements

then the Microstation default colour table shall be used. In general only
colours 0-7 shall be used where:
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
k) Signalling components shall be placed as groups of elements or cells such

that all the elements in a component will move and delete as one. Text
associated with a component shall normally be part of the group/cell.
If a circuit is itself placed as a single cell when it is dropped for amending each
component produced shall also be a cell.
l) All wiring shall be placed as single line strings between components and shall
not run through components in such a way as to be deceptive if the
components were to be removed.
n) Any explanatory notes not appearing on the master record which may be
necessary shall be in construction class and shall normally be below the title
block.
A.5.6 Printing
Not all elements in a design file are shown on the Master Record.
Source documents returned to the Custodian of Signalling Records shall have their
settings saved displaying only elements which are on the Master Record.
Construction class shall also be displayed if required.
A.6 Individual Record Centre Requirements
A.6.1 York Records Centre Directory Structure
The following directory structure shall be used for all CAD data returned to York
Records Centre:
control centre1 \ locality code2 \ function code2 \ filename.dgn
where
1
is the signalling control centre the design belongs to.
locality & function codes are derived from the drawing number of the file. The
current York Records Centre drawing numbering system being used. The function
code shall be the drawing Identity code suffixed with the name of the equipment if
relevant, i.e. location 4321 would have function code L_4321 L being the identity
code for location and 4321 the name of the location. Index sheets for locations
should be kept with the locations.
EXAMPLE
For a York design drawing number 01e1f l so220 sheet 1, the directory structure is
york \ 01e1f \ l_so220 \ 0001.dgn
The contractors project name/number may be used as the parent directory followed
by the above.
Contact the Custodian of Signalling Records for details of the York drawing
numbering system.
Page 54 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
m) Weights 1 and 2 are preferred but other weights may be used as appropriate.
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
A.6.2 Croydon Records Centre Directory Structure

The following directory structure shall be used for all CAD data returned to Croydon
Records Centre:
interlocking code1 \ function code2 \ filename.dgn
where
1
is the interlocking code used in the Croydon Records Centre drawing numbering
system.
2
is the function code used in the Croydon Records Centre drawing numbering
system. Function Codes should be suffixed with the name of the equipment if
relevant.
i.e.
e_rroom1 & e_rroom2 for an installation with 2 relay rooms
Each location is to be stored separately as EL_locname.

i.e.
el_22 for loc 22
Index sheets of locations should be kept with the location drawings

For a London Bridge location el321 sheet 1, the directory structure is
1LB \ el_321 \ 0001.dgn
The contractors project name/number may be used as the parent directory followed
by the above.
Contact the Custodian of Signalling Records for details of the Croydon
drawing numbering system.
A.6.3 Birmingham Records Centre Directory Structure
The following directory structure shall be used for all CAD data returned to
Birmingham Records Centre:
interlocking1 \ function code2 \ filename.dgn
where
1
is the signalling interlocking the design belongs to.
Apply to the Custodian of Signalling Records for the correct interlocking.

2
function codes are detailed below
The contractors project name/number may be used as the top directory followed by
the above.
EXAMPLE
For a Snow Hill location plan, snowloc1.dgn, the directory structure would be
snowhill / plans / snowloc1.dgn
Page 55 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
EXAMPLE
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
A.6.3.1 Birmingham Records Centre Function Code list
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
sb Signal
box
rr
Relay
Room (may use rr_name if required)
er Equipment
Room (may use er_name if required)
panels
Panel Faceplate
vdu
VDU layouts for IECC
diag
Other schematic diagram
plans
Signalling, loc area and bonding plans
lx
Level Crossing Ground Plan
ctab
Control Table
locname
Location
rlist
Route List
td Train
Describer
misc
Miscellaneous
core
Cable & core plans
Contact the Custodian of Signalling Records for clarification.
A.6.4 Glasgow Records Centre Directory Structure
The following directory structure shall be used for all CAD data returned to Glasgow
Records Centre:
control area1 \ interlocking1 \ function code2 \ filename.dgn
where
1
standard abbreviations are obtained from the Custodian of Signalling Records.

All drawings which cover more than one installation in a signalling centre shall be
located under the signalbox /control centre installation.
2
is derived from the function code list below
EXAMPLE
For an Edinburgh Haymarket signalling plan, M1.dgn, the directory structure would
be
edinburg \ haymarke \ plans \ M1.dgn
The contractors project name/number may be used as the top directory followed by
the above.
A.6.4.1 Glasgow Records Centre Function Code list
Mechanical Boxes
For a small box all files may be stored in two subdirectories - M & E with the filename
showing the function, i.e. E23-1.dgn. Apply to the Custodian of Signalling Records
for decision.
Multiple locations are to be named E23_loc1, E23_loc2, etc. for locations with long
names the location name shall be used, i.e. wickloc1 wickloc2.
Page 56 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Signal Centres - Power Boxes

Contact the Custodian of Signalling Records for clarification.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Page 57 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Appendix B
Signalling Design Records SSI Data Requirements
respect to SSI data, both production and handback.
It specifies:
the method of version control to be used;
the method of issue of records;
the media and format acceptable for returned data; and
the method of issue of version control.
B.1 Requests
All requests for SSI data records shall be made in accordance with NR/L2/INF/02018
and shall be sent to the relevant Custodian of Signalling Records. All requests shall
be made using form QF902, with one form used per interlocking and one form per
common.dbase. These are available from any Records Centre.
The Records Centre responsible for the signalling infrastructure shall then pass on
the request to York Records Centre. York Records Centre have responsibility for
maintaining and supporting SSI data for all Network Rail installations. All electronic
data and associated paperwork will then be issued direct to the contractor from York
with the local Records Centre being given confirmation of issue.
All requests for Information Only copies shall be on form QF902, and clearly specify
which files are required. This shall normally be issued as a paper copy. If the
request is for an electronic copy it shall state the format of data required, i.e. UNIX or
DOS. There is no requirement to return this data to York Records Centre. These
shall under no circumstances be treated as masters.
B.2 Issue of Source Data
Due to the high intrinsic value of source data, the issue of data to the contractor shall
be as follows:
For intermediate commissionings, data shall be returned to be held as security

copies. A paper issue shall then take place to enable the contractor to continue
working.
Paper copies shall take the form of a single issue requiring acknowledgement of
receipt.
Page 58 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
MC2 shall be issued for loading onto the contractors system. This shall then be
returned unaltered to York Records Centre before MC1 is issued for verification.
After MC1 has been used to verify the data held on the contractors system it shall
then be returned, unaltered, to York Records Centre to be held as the security copy.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
B.3 Returns
(These shall comply with all relevant documentation standards and procedures, e.g.
BR1990, SSI 8150 and SSI 8505).
After a commissioning all data and associated paperwork shall be returned by the
contractor directly to the York Records Centre for verification and storage. These
shall be accompanied by a QF902 clearly showing all returns:
1. Two data discs clearly identified as MC1 and MC2. (common.dbase to be
backed up separately from INTERLOCKING.data and .dbase). These shall
contain a full set of files as per null-scheme with no extra files present.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
2. Two sets of all Verification Master EPROMs (Gold and Silver) in separately
labelled electrostatic containers. These shall be labelled in accordance with
BR1990.
3. A copy of the signed on-site ISSR after final commissioning.
4. All CISRs created as part of the scheme, from initial release to final
commissioning with the final CISR signed off as commissioned, (The
intermediate CISRs can be photocopies).
5. A full printout of all interlocking files, bound together. This shall be produced
from the final version of data. The front sheet of the printout shall contain a
validating signature, date and CISR number.
6. For alterations, a single difference list of the scheme from the initial version
to the final release for all altered interlockings, signed and dated, and with the
two versions of data clearly identified.
7. A copy of the techterm tape clearly identified with the interlocking and current
CISR number.
8. A disc containing a copy of the tag files clearly identified with the interlocking
and current CISR number.
NOTE These are minimum requirements.
For multistage schemes all data and paperwork held for the intermediate
commissioned version(s) shall also be sent to the York Records Centre to be held for
Security purposes, until such time as the scheme is fully commissioned and the final
data is returned. For these intermediate returns only items 1-4 are required.
However the final return shall encompass any changes from the previous stages in
the return of items 5-8. The difference list applies to the change between the initial
state and the final stage. If the stage is cancelled the deferred items 5-8 shall be
produced.
B.4 CISR Numbers
All work to be carried out on an SSI interlocking, including new schemes, requires
the allocation of version control as per SSI 8505. The allocation of the next available
CISR number is the responsibility of York Records Centre. For new schemes it is
the responsibility of the contractor to obtain approval, from York Records Centre, for
the new INTERLOCKING name(s) and proposed interlocking number(s). This would
normally be at the same time as the request for the original CISR number(s). All
requests for CISR numbers shall be made using QF902. For new interlockings
Page 59 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
these will be issued as requested and for existing interlockings these will normally
be issued with the initial release of data. The contractor shall then be responsible for
all increments to the CISR until the final records are returned, at which time control
will revert to York Records Centre.
All requests for new Control Centre Numbers shall be made using QF925, available
from all Records Centres. This shall be completed and sent to the Records Centre
responsible for the relevant signalling infrastructure. They shall process the request
and send it to York Records Centre who shall issue the new number. Note that for
Baseband interlockings a number shall be allocated which falls outside the current
accepted range of DWS numbers. This number can be ignored in scheme set-up
but shall be utilised in the creation of the CISR record.
Page 60 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
B.5 Control Centre Numbers
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
Appendix C
Signalling Design Records Electronic Systems Data Requirements
Recognising the different nature of electronic data records this appendix (formerly
LSS003) details the additional requirements to NR/L2/INF/02018, with respect to:
Requests for Maintenance or Information Only copies.
The handover from Network Rail of source records for the purpose of alteration.
The management of version control and numbering of electronic data records.
The provision of further information in support of NR/L2/SIG/11201, Modules A8 &
A10, for producing electronic data as built records.
The handback of signalling electronic data records by the contractor to the Custodian
of Signalling Records.
C.1 Requests
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
All requests involving Electronic Systems Data records shall be made in accordance
with NR/L2/INF/02018 and shall be sent to the appropriate Custodian of Signalling
Records where copies of relevant forms: QF901, QF910, QF915 and QF921 can be
obtained.
Requests for source Data and Data listings shall be authorised by form QF901with
the system specific details recorded on form QF921 which shall be attached to
QF901. Only one Electronic Systems data shall be requested per form.
Requests for Maintenance or Information Only copies shall be authorised by form
QF910 with the system specific details recorded on form QF921 which shall be
attached to QF910, only one Electronic Systems data shall be requested per form.
There is no requirement to return Information Only data copies. These shall under
no circumstances be treated as masters.
The authorising QF901 and QF910 shall list the System name followed by See
attached form QF921 for details of Systems data required. Requests for source and
information only copies of the same data shall always be separately authorised on
the appropriate forms.
Requests unaccompanied by a completed QF921 will be rejected and returned to the
Project Manager. Whether accompanying another form or not QF921 always
requires the requesters sig0nature and date.
Drawings relating to Electronic Systems shall be requested using QF901 or QF910
only. Manuals will generally only be available as Source documents, using QF901,
or by browsing at a Records Centre.
Historical Electronic Systems whose data media is not compatible with a standard
IBM PC, i.e. 8 disks or paper tape, may not be available as Information Only copies
and may be dealt with using different though similar processes to those described
here. Requests shall still be made as above. Contact the Records Centre for
details.
The preferred media for the data disks of PC based systems is compact disc.
Historical data may be on other media which will be transferred to CD over time.
Data transferred to CD by the Records Centre will be in the following directory
Page 61 of 100


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
The Network Rail Project Manager shall be informed when Records are unavailable
in order for him to take appropriate action.
C.2 Handover
The requirements of Section 13 of this Standard and NR/L2/INF/02018 shall be
applied with the addition of the following:
One copy of the data, Master Disk 1 (MD1), shall be issued to the Design Authority
for amendment. This copy will be integrity checked by the Records Custodian before
issue*. This check confirms that the data supplied is identical to that originally
received by the Records Custodian. Acknowledgement of receipt is required.
If the Design Authority requires further verification then MD1 shall be loaded onto the
Design Authorities system, returned unaltered to the Records Centre and the second
independent copy, Master Disk 2, MD2, requested using QF921. The Design
Authority may then verify one copy against the other. MD2 should then be returned
to the Records Custodian. It is the Design Authorities responsibility to decide when
such verification is required.
Paper copies shall take the form of a single issue with acknowledgement of receipt
required.
* The integrity check is not possible for historical non-PC based systems. In such
cases the Design Authority shall always request MD2 as above.
C.3 Version Control
The requirement for Version Control as described in Section 14 of this Standard;
NR/L2/SIG/11201, Module A10; and NR/L2/INF/02018 shall be applied with the
additional/emphasised requirements:
Version Control shall be requested using form QF921 by the contractor from the
Records Centre at the time of requesting the electronic systems data. Only the
supplied alteration letters may be applied and any deviations or additions shall be
authorised by the Records Centre prior to use.
Status record index sheets should be provided for each master data disc belonging
to each electronic system. The status record index should list each and every data
file and give its current software version. The version number (first part) should be
incremented (and the subversion reset to zero) for each commissioning that
necessitates a data change. The subversion (second part) should be incremented
each time the data is changed prior to re-testing. EPROMs should also be identified
by means of status record indexes.
Status record indexes should be treated as design details in the same way as index
sheets, complete with a standard title block bearing a drawing number and version
with alteration letters.
Page 62 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
structure - drive: \ system name disk n \ version i.e. euston1 \ aa1. (If the system
is comprised of only 1 disc then disk n may be omitted)
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
C.3.1 Approval and Issues Record sheet (AIR)

The AIR sheet shall detail the Status Record Index sheets and state whether the
data has been altered, abolished or newly created. The AIR sheet shall also detail
any changes to manuals or drawings as detailed in Section 14.5 of this Standard.
C.3.2 Numbering of Records
The Custodian of Signalling Records shall provide guidelines which shall be followed
for the numbering of new electronic records, manuals and data listings and status
record index sheets as stated in Section 14.2 of this Standard.
C.4 Production of Signalling Design in Respect to Electronic Media
Data Disk/Media Labelling:
Status Record Index Sheets:
Data Files:
The initials of the producer and checker certify

that the data is an exact copy of the
commissioned data.
One sheet per master data disk, EPROM or
equivalent. For data disks each data file and its
current software version shall be listed.
Data files shall each have a title block applied at
the beginning which incorporates the listing
name, drawing number, software version and the
initials of producer and checker.
An End Of File marker shall be applied at the
end to show completeness.
Applying a title block to the printed listing alone
is not acceptable.
Table C.1 Labels, Index Sheets and Title Blocks

Examples of labels, index sheets and title blocks may be found in NR/L2/SIG/11201,
Module A10.
C.5 Handback of Electronic Data
The requirements of Section 13 of this Standard; NR/L2/SIG/11201, Modules A8 &
A10; and NR/L2/INF/02018 shall be applied with the following additional /
emphasised requirements:
For multi-stage schemes all data and paperwork held for the intermediate
commissioned version shall be sent to the Records Custodian to be held for Security
purposes, until such time as the scheme is fully commissioned and the final data is
returned.
The preferred media for the handback and storage of PC based systems is Compact
Disc. Systems which are comprised of multiple floppy discs may, if practical, be
returned on 1 CD for MD1 and another for MD2 with the contents of each floppy disc
occupying a separate directory on the CD.
Page 63 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
The requirements of Section 14 of this Standard; NR/L2/SIG/11201, Modules A8 &

A10; and NR/L2/INF/02018 are to be applied. The following items are particularly
emphasised:
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Returns to the Custodian of Signalling Records shall be listed on two forms QF915
and QF921 and consist of:
On Form QF921
Status Record Index Sheet/s.

2 data discs clearly identified as MD1 and MD2. (preferred media CD)
Source data listings (which each have title blocks): A complete listing of
the installation.
If applicable, 2 EPROMs in separate, labelled electrostatic containers
(See BR1990).
Sysgen report.
The System Generation Software, if issued, shall be returned.
System Generation Software (if Train Describer is new)
On Form QF915
2 sets of the System Instruction Manuals (if System is new)

2 copies of site specific Manuals (including any drawings that
form part of the manual)
Drawings / CAD Data.
AIR sheet
QF915 shall also list the System name followed by See attached form QF921 for
details of Systems data returned.
Electronic media shall be transmitted by hand or recognised courier in suitable
packaging to protect the media from physical, electromagnetic, electrostatic damage.
An acceptance check will be carried out for all electronic systems data records by
the Records Custodian. Acceptance / Rejection will be communicated in accordance
with NR/L2/INF/02018. The Design Authority shall retain a copy of the returned data
until acceptance has been confirmed by the Records Custodian.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 64 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Appendix D
Signalling Design Records IECC Data Requirements
respect to IECC data, both production and handback.
It specifies:
the method of request to be used;
the method of issue of records; and
the media and format acceptable for returned data.
D.1 Introduction
York Records Centre has responsibility for managing and supporting all IECC data
for Network Rail installations. All source data is the property of Network Rail and
release of this is only made to authorised persons. Source data will only be issued
to one Design Authority at a time. The Data handling is operated by a data
management company on behalf of Network Rail. To obtain further details contact
the York Records Centre Manager on 01904 524674 (Railnet 03 74674).
D.2 Requests
All requests for retrieval of IECC data records shall be made in accordance with
NR/L2/INF/02018 and shall be sent to the Custodian of Signalling Records
appropriate to the Route, as follows:
All requests for master records for alteration shall be initially made using
QF901 Request for Handover of Source Records.
All requests for information only copies shall be initially made using QF909
Authorisation to Browse.
Once authorisation has been received QF924 shall be completed. Only one form
shall be used for each IECC system. These are available from all Network Rail
Signalling Records Centres. The completed form shall then be sent to the Records
Centre responsible for the Route signalling infrastructure.
It is the responsibility of the Design Authority to clearly state what is required and to
provide all relevant information.
The responsible Route Records Centre shall pass on the request to York Records
Centre. All electronic data and associated paperwork will then be issued direct to
the Design Authority with confirmation of issue forwarded to the Route Records
Centre.
All Returns of IECC data and associated paperwork shall be made in accordance
with NR/L2/INF/02018, using QF924, with one form used per IECC system. These
returns shall be sent direct to the data Management company responsible for storing
the IECC data on Network Rail's behalf. They are responsible for processing the
data and documentation and then passing the request to York Records Centre for
acceptance/rejection.
All other IECC associated Signalling records shall be returned to the Records Centre
responsible for the signalling infrastructure as per NR/L2/INF/02018.
Page 65 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
For all requests the data transfer shall normally take the form of a tape of the
complete IECC system using a 6150 or DC600A standard cartridge tape with a
maximum data capacity of 150 Mbytes. (Other media only by prior agreement with
York Records Centre). All contents shall be in cpio format using relative pathnames,
containing a list of contents and labelled with identifier and date. The Directory
structure shall be as per the convention detailed later with standard filenames used.
The tape shall be readable and complete.
Acknowledgement of receipt is required for all issues.
D.3 Issue of Data
D.3.1 Issue of Data for Alteration
The issue of data to the Design Authority by the Contracted Data Management
company shall take the form of a single issue of:
a tape of the complete IECC system,

also containing a file listing of all of the files released.
D.3.2 Issue of Information Only Data

All requests for Information Only copies shall be made on form QF924, after
receiving authorisation using QF909, and shall clearly specify which data is required.
This shall normally be issued as an electronic copy in tape format. There is no
requirement to return this data to York. These shall under no circumstances be
treated as masters.
Other documentation may be issued on request. Paper copies shall take the form of
a single issue.
EPROMs may also be required for reference purposes. Each EPROM issued will
have a label affixed which will identify the EPROMs IECC, board, socket number
and the checksum in addition to the subsystem to which it belongs; this will be a
copy of the original EPROM label.
D.4 Returns
This section defines the minimum IECC data and associated documentation required
from a data contractor/ system builder contractor.
All associated IECC records such as; site specific IECC system drawings altered,
created or deleted, on CAD and paper format, Screen layouts, Site Specific
drawings, TD Maps and Control Tables, ARS Specification, ARS Route Lists, Long
Route List, ECS Specifications, Thread Specification, Key Location Drawings,
Stepping Drawings, Misc. Keyboard Commands etc. shall be returned to the
Records Centre responsible for the signalling infrastructure together with their
associated QF915 and AIR sheet.
D.4.1 IECC Site Specific Data
(These shall comply with all relevant documentation standards and procedures.)
After a commissioning all data and associated paperwork shall be returned by the
Design Authority directly to the Contracted Data Management company for
Page 66 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
verification and storage. For multistage schemes, all data and paperwork held for
any intermediate commissioned version shall be sent immediately after each
commissioning, to be checked and held as a security copy, until such time as the
scheme is fully commissioned and the final data is returned.
Returns requirements:
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Data Release Note. This document defines the changes made to the data and
released for building into a system.
Site Release note. This will identify the IECC that the EPROMs belong to
and defines the modules and versions used to generate the system. The
Release note will have a list of the EPROMs that should be present in the
IECC on a subsystem by subsystem basis. It will list the board, socket
number and the checksum for each EPROM. Changed EPROMs will be
highlighted in this document.
Description of change document. This document will describe what has

changed and why the changes have taken place. This will, as a minimum,
define the subsystems which have changed, the parts of the signalled area
affected by the change, and the code variant type and version the data has
been designed to be used with.
A full set of all altered or new EPROMs. Each EPROM will have a label
affixed which will identify the EPROMs IECC, board, socket number and
checksum, in addition to the subsystem to which it belongs. The EPROMs
will be returned in labelled electrostatic containers. This is in addition to any
sets produced for site.
A copy of any prom.log files produced. These are electronic files taken from
the build system which holds the details of the EPROM labels.
Acceptance Certificate. This certificate will signify that the changes have
been accepted and installed in the live IECC site system. It requires to be
signed by a responsible Network Rail person.
Statement of Integrity. A signed statement that the data sent for storage on
the system is the same as that installed in the live IECC system on site.
FAST files. All FAST files, including any created as part of the scheme, will
be returned as testing records. These shall comprise the .inc, .fat and .log
files.
Subsystem data files shall comprise all of the following (where present):
SDS1(DIS1),
SDS2(DIS2), SDS3(DIS3)
GWS
ARS
ISM
RII1,
RII2, RII3
ECS
IGS
FBS1, FBS2, FBS3, FBS4, FBS5, FBS6, FBS7, FBS8, FBS9
FBSA
Service
data
Page 67 of 100

NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
Create
TD Maps
Create
Screen Data
SSI
Identities
Common
Data
SIM and any associated SSI Images
Test Files (FAST) files
RII-SSI files RII-SSI Image files
NOTE Where convenient, some of the supporting paperwork can be combined into one document as
long as all of the relevant details are present.
D.4.2 Code Custodian Documentation

Code, Compiler and Utility Tools are provided by the Code Custodian.
DC600A Tape (or other by prior agreement) in cpio format.
Description of the change. This will define the variant, version and the parts
of the IECC that have changed in subsystem terms.
D.4.3 TTP
DC600A Tape (or other by agreement) in cpio format
Description of changes. A description of the contents of the tape and the sites
to which it applies. There will be an outline description of the change and the
dates when installed on site.
D.5 File Naming Convention

A file has a name which is composed of two parts, a prefix and an extension
separated by a full stop:
prefix.[extension]
where [ ] is missing in some cases.
The term used to refer to the whole name is filename, while the components are
referred to as prefix and extension. Some of the file names used do not have an
extension and the prefix alone defines the filename.
D.5.1 CPF Files
The primary Central Parameter File (CPF) source file will have the filename cpf1.
Secondary CPF input files will have the filename ser.cpf2.
D.5.2 Service Files
Service data consists of two levels of data, however, it is only level 2 data which is of
concern here; level 1 files are automatically generated from level 2 source files.
Page 68 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
D.5.2.1 Level 2 Source Files

Source data is split between default and custom files. The custom files have
filenames defined as follows, with no extension:
Sso
taskc
qets1
qeti1
qets2
qeti2
rcmc
pass
Site Specific Overview File,

Custom Task Table File,
Primary Quiet and Enquiry Time File for the signalling network,
Primary Quiet and Enquiry Time File for the information network,
Secondary Quiet and Enquiry Time File for the signalling network,
Secondary Quiet and Enquiry Time File for the information network,
Custom RCM Mapping File,
BRX password File. (Upgrade 1 and above)
In addition to the above files a number of default files are required for the service
compiler, they have a prefix of ser and an extension as defined below:
tasks
taski
ssic
rcm
queue
Task Table Default File for the signalling network,

Task Table Default File for the information network,
SSIC ROM Default File,
RCM Default Mapping File,
Message Queue File.
EXAMPLE - ser.tasks
D.5.3 Identity Files
D.5.3.1 SSI, RII, and IECC Identity Files
Source text files will have the SSI and IECC specific characters assigned as follows.
The prefix will define which interlocking the identity file belongs to. Normally where
the actual interlocking name is short enough the prefix will be the identity of the
interlocking. However, where the actual interlocking name is longer than eight
characters, a suitable mnemonic will be substituted.
Files prepared using the SSI Data Preparation System are given the following
extensions in the common area:
sig
pts
rou
tcs
flg
qst
pfm
prr
signals,
points,
routes,
track circuits,
flags,
panel requests,
Points Free To Move file (for ARS),
Prove Route Request file (for ARS).
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 69 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
In the SSI area the files retain their standard SSI identities, e.g.:
SIG.id
PTS.id
ROU.id
TCS.id
FLG.id
QST.id
PFM.dat
PRR.dat
signals,
points,
routes,
track circuits,
flags,
panel requests,
Points Free To Move file (for ARS),
Prove Route Request file (for ARS).
Files with the extension listed below are not used by Data Preparation for
subsystems other than RII and SIM, but may be supplied by the SSI data preparers
and are listed below for completeness:
BUT
ELT
INT
IND
OPT
Button identities;
Elapsed timer identities;
Information file;
Information file;
Information file.
D.5.4 IECC Alias Files

IECC Alias files will have the file extension als. These are used to rename SSI
identities into names of the type that can be used by IECC. The following files will be
processed by the IECC Alias Renamer tool:
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
SIG
PTS
ROU
TCS
FLG
QST
signals,
points,
routes,
track circuits,
flags,
panel requests,
EXAMPLE - SIG.als
D.5.5 SDS, DIS and FBS Files
D.5.5.1 SDS, DIS Data: Relational and Screen Files
The rules for the filename extension for SDS relational data is as listed below:
pqs panel
requests,
pnt
points,
snl
signals,
tct
track circuits,
rot
routes,
srt
sub routes,
rel
releases,
sba
sub areas,
lth
latches,
alm
alarms,
hit
hit areas,
iso
isolations,
dsb descrip
tion berths,
stp
step data,
int
initialisation.
Page 70 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
The prefix of the listed relational data files will be determined by the interlocking to
which the file refers. The rules for the prefix naming are the same as those given in
Section D.6.5 (Identity Files).
The make file, is a listing of the files to be used by the compiler and is given the
filename mak.
The compiler input text file (as prompted during compilation) will contain the standard
settings for the relational compiler.
The file Ipadd will contain the DIS Internet Protocol address.
Screen files will have a prefix determined by the view number to which they refer and
the extension SA. The Create program, which generates encoded image files,
generates filenames entirely in upper case, these file names will be retained.
D.5.6 Keyboard and TDMAP Data
The following filenames with no extension will be used for the keyboard compiler
source files:
gif George input file;
kyx keyboard cross reference file.
D.5.7 SDS and FBS File Name Examples

Listed below are examples of the file naming convention for SDS and FBS files:
lsbg.stp Liverpool Street, SDS file, SDS workstation one, relational data, Bethnal
Green interlocking, step data;
VW1.SA SDS screen file for view 1;
gif keyboard compiler input file.
D.5.8 ARS Files
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
ARS Detail Files will have the following filenames in upper case with no extension as
shown below:
DSIG
DLINK
DRTE
DRLS
DTCT
DFLG
DBER
DSTP
DLOC
DINS
DRLE
DSEG
DPER
DMIS
signal details,
link file,
route detail,
release detail,
track circuit detail,
flag detail,
berth detail,
TD stepping detail,
location detail,
key location insertion rules,
key location line/path rules,
inter-location path segment detail,
timetable period detail,
miscellaneous detail.
Page 71 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
The ARS logical files converted from the SSI .pfm and .prr files during ARS Data
Preparation will be given a prefix identifying the interlocking, as described in Section
D.6.5 (Identity Files), and the following extensions in accordance with the ARS Data
Preparation Guide:
DPM Points Free To Move,
DRA Route Availability,
DLC Logical
Conditions.
D.5.9 GWS Files

There is one source file written specifically for the GWS compiler, in addition the
compiler uses the CPF source files defined in Section D.5.1 (CPF Files). The GWSspecific source file has the filename gws, with no extension.
D.5.10 IGS Files
IGS filenames are in upper case with no extension as defined below:
DIEC
DPCS
DISM
DTTP
DGWS
DSDS
DSSI
DARS
DPIS
DSIS
DSIG
DBER
DSTP
DAAB
DLOC
DINS
DREL
DSEG
DPER
DPEC
DMIS
Integrated Electronic Control Centre detail,

External Communications System detail,
IECC System monitor detail,
Timetable Processor system detail,
Gateway system detail,
Signalling Display System detail,
Solid State Interlocking detail,
Automatic Route setting detail,
Customer Information System detail,
Staff Information System detail,
Signalling items detail,
Berth detail,
TD stepping detail,
Adjacent area berth detail,
Location detail,
Key location insertion rules,
Key location line/path rules,
Inter-location path segment detail,
Timetable period detail,
Customer information event detail,
Miscellaneous detail.
Page 72 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
There will be one set of DPM, DRA and DLC files per interlocking.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
D.5.11 ISM File

sso Site
userid
ismin
arsin
pcsin
riiin
techa
techb
sdsalm
actn
board
stati
stats
diagm
Specific Overview File,

User Identities and Passwords File,
ISM Specific External TTL Input Definitions File,
ARS Specific State Input Definitions File,
PCS Specific State Input Definitions File,
RII specific State input definitions File,
ISM, ARS and PCS Specific Alarms to Technician Part A File,
ISM, ARS and PCS Specific Alarms to Technician Part B File,
SDS System Specific Alarms. i.e. Alarms emanating from the SDS subsystem,
ISM Alarm Actions Definition File,
Board Configuration File,
ISM Status Time-outs Information Network File,
ISM Status Time-outs Signalling Network File,
ISM Network Diagram Definition File.
D.5.12 PCS Files

PCS source file prefixes have the first letter set to a scheme identifier and the
second letter set to p. The extensions are as follows:
pcs
dpcn
PCS Overview file,

Remote System file.
The Remote System files have a number n (n=1-16) appended to the end of the
extension which is the number of the remote system to which the Remote System
file refers.
D.5.13 ECS Files
ECS source files prefixes have the first letter set to a scheme identifier and the
second letter set to x. The extensions are as follows:
Ecs ECS
Overview file,
Remn Remote System file.
The Remote System files have a number n (n=1-16) appended to the end of the
extension which is the number of the remote system to which the Remote System
file refers.
For example, the filename lx.ecs refers to the Liverpool Street ECS Overview file and
lx.rem1 refers to the Liverpool Street Remote System file for remote system 1.
In addition a protocol file will be required to define the protocol types in the scheme.
This file will be called daxprotocol.
Where there is more than 1 ECS then a number representing the ECS shall be
appended to the name.
D.5.14 RII Files
The RII files are split between the SSI-like files and system files.
Page 73 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
ISM source files have the following filenames with no extensions:
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
D.5.15 System Files

The system files define the protocol and configuration of the subsystem. Each file
has an extension consisting of the letter c. The prefixes are as follows:
nidtcfg
IDT configuration file. Where n is the number of the TNP board number +1,
ncicfg
NCI configuration,
almtxt
Alarm text,
ctlrout
Control Routing,
nfcpconf FCP configuration. Where n is the number of the FCP board number +1,
nhsgdata Housing data. Where n is the number of the SCP board number +1,
nspctxt
Alarm modifier data. Where n is the number of the SCP board number +1,
nspecidx Fault reporting data. Where n is the number of the SCP board number +1,
config.file RII configuration file.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
D.5.16 SSI-like Files

The SSI-like files are developed as pseudo SSI data on an SSI Design Workstation,
which will use a number of database files in the construction of the SSI output data
for use in the compilers.
A complete backup of the SSI scheme data is required to guarantee all the relevant
source data is captured.
D.5.17 TD map Files
Four characters are assigned to the prefix of each map file, using the name entered
by the signaller on requesting the map for display.
The Create program generates filenames entirely in upper case, with the extensions
SA and DU; these filenames will be retained. (N.B. SA is generally the primary file).
An example of the file naming convention for TD map files is:
MAP1.SA TD map source file for MAP1
D.5.18 Simulator Files

The simulator is part of the data testing facilities used for testing an IECC and is
therefore not part of the normal data which is in a live IECC. Because there are
several types of simulator in existence used by different Design Authorities it is not
possible to prescribe filenames as the requirements will vary with the particular
Design Authority testing facilities. However all SIM files are required including IECC
files and SSI-like image files as well.
Page 74 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
D.5.19 FAST Files

These files are used as a test aid for the IECC system and do not form part of a live
system. The standard naming convention for these files is to be:
.fat
The basic test file prior to compilation,
.inc
The include file. This is the subroutine file for the specific area under test,
.log
The test file after completion of test run and containing the responses.
D.6 Directory Naming and Structure Convention

The directory structure is based around the concept of dividing the data between
subsystems and general components.
An assumption with the convention is that each IECC scheme will have a unique
home directory and all source data will be stored in relevant sub-directories. On the
Network Rail Records Group data storage computer all files will be stored in Source
Code Control System (SCCS) format. However, data will be distributed and received
in the form of ASCII text files with the exception of part of the RII subsystem and
simulator. These directories and associated files will be transferred using path
names that are relative to the scheme directory.
D.6.1 Subsystems
There will be one directory per subsystem. Where more than one subsystem of a
particular type potentially exists then there will be sub-directories below the
subsystem type directory in each instance. Exceptions to the general rule are
subsystems SDS, DIS and FBS. There will either be a DIS subsystem or an SDS
subsystem used as a workstation and data will be stored as if it were from an SDS
regardless. The SDS (DIS) subsystem directories will be used to store the relational
and keyboard data only, the display data will be stored elsewhere. With FBS, only
the keyboard data will be stored under the FB directories.
D.6.2 Display Data
The display data for a workstation is maintained under the directory called create. A
sub-directory is used to store the TD maps called tdmap. There is also a subdirectory for each workstation called SDSn, where n is the number of the
workstation.
D.6.3 RII SSI-Like Data
The RII components will be stored in sub-directories under the directory RII_SSI.
There will be one main sub-directory for each RII. The structure under these
directories will be an image of that found for the site on the SSI design workstation.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`--

Page 75 of 100
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
D.6.4 SIM SSI-Like Data

The SIM components will be stored in sub-directories under the directory SIM_SSI.
There will be one main sub-directory for each SIM. The structure under these
directories will be an image of that found for the site on the SSI design workstation.
D.6.5 Identity Files
The SSI sub-directory will be used to hold the true identity files for the interlockings,
while the COMMON sub-directories will be used to hold the actual identity, some of
which may contain aliased names. Where there are no aliases in an identity file then
there will be an equivalent copy of the SSI directory file in the COMMON directory.
D.6.6 Service Data
There will be a directory called SERVICE containing two sub-directories default and
custom. Files, defined in Section D.5.2.1 , with the prefix ser will be stored in the
default sub-directory, while the other service files will be stored in the custom subdirectory.
D.6.7 Test Files
Where test files exist these will reside in a directory TEST_FILES. There will be two
sub-directories SIM and FAST, for simulator and FAST files respectively. If a
number of simulators exist for a scheme then each will have its own sub-directory.
D.6.8 Structure: Partial Examples
An example partial directory structure is shown below:
SERVICE
COMMON
int1
SSI
SDS
ARS
ECS
int1
ECS1
default
SDS1
SDS2
custom
Page 76 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
There will be two directories for these files, SSI and COMMON. Under each there
will be a sub-directory for each interlocking (RRI) which will be named after the
interlocking to which the files belong. Where the name of the interlocking is longer
than eight characters then a suitable mnemonic will be used instead.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Another example partial directory structure is shown below:
create
COMMON
int1
RII_SSI
RII1
SDS
FB
RII
SDS1
RII1
tdmap
FB1
FB2
SDS1
D.7 Abbreviations
ARS The Automatic Route setting Subsystem (ARS) determines the optimum
routing of trains in the area based on the timetable, their current position, their
importance and their destination. It automatically requests the required routes
when they are free to be set.
DIS
The Flexible Display Subsystem (DIS) is a functional replacement for SDS

which employs standard PC based display technology in place of the
proprietary graphics controller used by SDS.
ECS The External Communications Subsystem (ECS) provides an interface

between the information networks and systems which cannot use the IECC
system's communications protocols or data notations. Non-IECC type Fringe
Boxes communicate via the ECS.
FAST Factory Acceptance System Testing. This is a system using a number of
script files to systematically test IECC data by manipulating SSI memory
location values and making the tester answer a question with regard to an
expected indication. The answers to the questions are logged for later
inspection
FBS The Fringe Box Subsystem (FBS) provides a Train Describer map, interpose
and cancel facilities for the fringe signaller, via a monitor and keyboard. There
is a maximum of 16 per IECC.
GWS The Gateway Subsystem (GWS) provides a link between the Signalling
Network and the Information Network. It transfers information between the
two networks when the source and destination are not on the same network.
It also provides a buffer storage facility (database) between the two networks.
IFP
The Interface Processor (IFP) has been superseded by RII. The IFP fulfils the
same purpose as RII but it is not a true IECC subsystem since it has a
different hardware and software architecture based on SSI technology rather
than IECC. With the introduction of IECC upgrade 001, IFP is no longer
supported.
IGS
The Information Generator Subsystem (IGS) monitors the operation of, and
gathers information from, DISs, SDSs, SSIs and RIIs in order to follow train
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 77 of 100
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
movements in the IECC area. The IGS is also informed, by the TTP, of the
current timetable. It uses this information to drive up to 4 customer
information systems (CIS) and a staff information system (SIS). The IGS also
logs train performance statistics to cartridge tape.
ISM
The IECC System Monitor Subsystem (ISM) monitors the operation of all
IECC subsystems and the two networks, and reports the IECC system status
to maintenance staff. It also provides aids to the technician for fault finding
and for reconfiguration of the IECC.
NDS The Network Communications and Duplication Services (NDS) is part of the
underlying software which is present in all IECC subsystems. It manages the
network communications and subsystem duplication services.
PCS The Protocol Converter Subsystem (PCS) has been superseded by ECS. The
PCS fulfils the same purpose as ECS but is less flexible and has a less
developed functionality. With the introduction of IECC Upgrade 001, PCS is
no longer supported.
RII
The Relay Interlocking Interface Subsystem (RII) enables a relay interlocking

to be interfaced to an IECC system. This avoids the need to replace a relay
interlocking with an SSI, usually for economic reasons.
SDS The Signalling Display Subsystem (SDS) provides the operating interface
between the IECC system (and hence the railway) and the signaller. There
are a maximum of three per IECC.
SSI
The Solid State Interlocking (SSI) system is a programmable electronic

system which is used in place of relay interlockings on new installations. It
provides the primary interlocking features necessary to confirm the safety of
the railway. It is a separate system and not a subsystem of the IECC.
TTP
The Timetable Processor Subsystem (TTP) contains the timetable information

for the IECC and the surrounding areas. This information is used by ARS.
Page 78 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
Appendix E Definitions, Related Documents & Subject Index

E.1 Definitions
85%ile Rule
The average speed of 85% of vehicles in a sample of 100
A.C. ELECTRIFIED AREA
An electrified area equipped for a.c. electric traction; including a buffer zone,
where the track circuit equipment is immunised against the a.c. traction
frequency, extending generally for at least 3000m along any lines equipped
solely for d.c. traction.
A.C. IMMUNE RELAY
A d.c. relay which is immune to operation by a.c. of specified voltage and

frequency.
ABNORMAL (conditions)
Extreme loading on a part of the railway system (e.g. as a result of extended

delays on one part of the service impinging on another). [source: RSPG]
ACCEPTABLE (risk)
Associated with a risk that is either:
Unplanned, uncontrolled event giving rise to death, injury, ill-health, damage or

other loss.
ALTERATIONS
Changes to existing installations (including the provision of new signalling) which

form part or all of a self contained scheme. A single alteration is by definition one
which is designed to be commissioned on a single occasion.
AMBER
As in amber warning lights on road traffic lights. This standard uses amber
when referring to this light, but custom and practice in signalling circuitry is to
refer to yellow instead of amber. This is allowed
AMENDMENTS
Changes to the design details which are required to be carried out as a result of a
change in scope of the original standard. These should generally result in an
amendment to a scheme plan.
ANTI-PRESELECTION
The prevention of preselection of a signalling function, thus maintaining the

protection of the signalling system should a wrong side failure occur
APPARATUS
A product with an intrinsic function intended for the end-user and supplied or
taken into service as a single commercial unit. [source: EMC Regs - modified]
APPARATUS CASE
An apparatus housing which is intended for unprotected outdoor use, is smaller

than a building or REB and is usually capable of being transported as a made-up
unit. It is usually of metallic construction. The wooden equivalent is commonly
known as an apparatus cupboard
APPARATUS CUPBOARD
An apparatus housing which is intended for unprotected outdoor use, is smaller

than a building or REB and is usually capable of being transported as a made-up
unit It is usually of wooden construction. The metal equivalent is commonly
known as an apparatus case.
APPARATUS HOUSlNG
This is provided to house relays and / or other equipment at lineside locations or

interlockings, and may consist of an apparatus case, apparatus cupboard
disconnection box, equipment room, REB, signal box, control centre, or other
equipment building.
APPLICATION CRITERIA
Document(s) specifying the constraints applied to the installation and

maintenance of a system or an item of equipment in order that if can be
guaranteed to deliver the performance attributes stated in the system or
equipment standard.
APPORTIONMENT
A process whereby the dependability elements for a system are sub-divided

between various items which comprise the system to provide individual targets.
[source BS EN 50126]
Page 79 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
ACCEPTANCE (product or
engineering details)
ACCIDENT
tolerable AND as low as reasonably practicable; or

negligible
The status given by Network Rail before use is permitted.
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
APPROVAL
The status given by the requisite authority when the product or works complies in
all respects with the standard and addresses all identified risks.
APPROVAL AND ISSUES

RECORD (AIR)
A summary sheet created at the start of a signalling alteration, for version control
purposes, to track approvals, issues and modifications.
APPROVAL IN PRINCIPAL
The status given to a signalling scheme when the Scheme Plan is approved.
APPROVED FOR
CONSTRUCTION
The status given to engineering details by the responsible design engineer

following acceptance by Network Rail.
ARAAFOAL
At red, alight and free of approach locking
ASSESSMENT
The undertaking of an investigation in order to arrive at a judgement, based on

evidence, of the suitability of a product, competence of a person or acceptability
of a risk. [source: BS EN 50126 expanded]
ATC
Another train coming
AUTHORISATION
The formal permission to use a product within specified application constraints.

[source: BS EN 50126]
AUTOMATIC FUNCTlON
A signalling function that, under ordinary operation, is operated automatically

by the passage of trains and is not interlocked with any other signalling
function. The function is generally associated with a particular signal box from
which its operation is supervised, unless some form of local monitoring is
provided.
The state of the function when there are no trains present is designated normal.
AUTOMATIC LEVEL
CROSSING
AUXILIARY (optical
system)
AVAILABILITY
AHB, AOCL, ABCL.

NOTE: MCB with auto lower and MSL are not defined as automatic in RSP&G
Duplicate lamp or filament on hot or cold stand-by.

The probability that a system will be able to perform its required functions under
given conditions at a stated instant of time or over a given time interval assuming
the required external resources are provided. [source: BS ENV 50129)
AVAILABLE
The state of an item when it is capable of performing its required functions in the
defined condition of use. [source: BS 4778]
BACK (B) CONTACT
A contact of a relay which is made when the relay is released and broken when it
is operated.
BACK FEED
An inadvertent feed which has arisen at an intermediate point within a circuit due
to the uncontrolled combination of positions of several pieces of control
equipment.
BARRIER CROSSINGS
OPERATED BY RAILWAY
STAFF
BASIC EVENT
MCB, MCB-CCTV, MCB-OD, TOB
BEARER
An item of steel or concrete of non-standard dimensions used to support the track

in switch and crossing (S&C) areas. (See also sleeper and timber)
BIASED RELAY
A d.c. relay which only operates when a d.c. supply of the correct polarity and
voltage is applied to the coil.
See fundamental cause.
Otherwise referred to as a 2-position polar relay.

BONDING PLAN
A detailed plan of the track layout showing individual rails and position of IRJs,
together with track circuit feed and relay connections with polarities, cross
bonds, structure bonds, impedance bonds, etc., as applicable. This term may
also include track plans and negative Bonding Plans in d.c. electrified areas.
BR930 SERIES (relay)
A miniature plug-in relay in one of the following styles (see NR/L2/SIG/11630):

BR930, BR931, BR932, BR933, BR934, BR935, BR936, BR937, BR938, BR939,
BR940, BR941, BR942, BR943, BR945, BR946, BR947, BR949, BR960, BR961,
BR962, BR963, BR964, BR966 (all variants) or BR968.
Page 80 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


NR/L2/SIG/11201
014
06/09/2014
CABLE CORE PLAN
A plan showing the allocation of signalling functions or systems to specific

cores in multicore and data link cables.
CABLE ROUTE PLAN
A layout plan showing the position of principal cable routes relative to signal
boxes or interlockings and locations.
This plan is generally combined with the location area plan
CABLE SCHEMATlC PLAN
A plan showing all signalling and power distribution cables required, together with
sizes, to be installed between signal boxes or interlockings and locations.
CAB SECURE RADIO

(CSR)
A form of radio telephone system provided as an alternative to a signal post

telephone system. Facilities include secrecy of call under normal operations,
emergency override calls and system wide broadcasts.
CATCH POINT
A point (switch and tiebar only), on running line gradients to de-rail wagons etc.,
running away in the wrong direction.
CENTRAL PROCESSING
UNIT (CPU)
The central part of an electronic system or sub-system that manipulates data. It

receives inputs from various interfaces, processes them in accordance with the
control program and geographical data in the memory and returns the resulting
outputs to the interfaces.
CERTlFICATE OF
COMPLETION
CERTIFICATE OF
COMPLIANCE
CERTIFICATE OF
CONFORMITY (plant or
equipment)
CHANGE CONTROL
Advice that works are ready for inspection.
CHANGE-OVER CONTACT
See dependent contact
CHECK RAIL
See figure under switches and crossing.
CIRCUIT CONTROLLER
A circuit switching device containing a number of contact bands, each of which

may be individually cut to length and adjusted to make and break separate
circuits at appropriate points in the cycle. The bands are operated by a
mechanical device, such as a lever or signal.
CIRCUIT DIAGRAMS
A collection of individual drawings showing the equipment layout and circuit

arrangement associated with a location, an interlocking or signal box.
CLASS I EQUIPMENT
Electrical equipment that requires the connection of the exposed-conductiveparts to a protective conductor connected to earth, to protect personal safety.
See BS 2754.
CLASS II EQUIPMENT
Electrical equipment with double or reinforced insulation, either to prevent contact

with exposed-conductive-parts, or to prevent against contact between such
parts and live parts. The insulation is not therefore to be pierced by screws.
Such equipment is never connected to earth. See BS 2754.
CLOSURE LIST
Final Index of design details issued to the tester in charge.
CLOSURE PANEL (track)
See figure under switches and crossings.
CLOSURE RAIL
COMMON CAUSE
FAILURE (CCF)
A failure which is the result of an event(s) which, because of dependencies,

causes a coincidence of failure states of components in two or more separate
channels of a redundancy system, leading to the defined system failing to
perform its intended function. [source: BS EN 61508]
COMMON RAIL
The rail of a single rail track circuit that is electrically common to one or more
adjacent track circuits or forms the traction return path where an isolated single
rail track circuit is provided.
A statement of conformity to requirements and standards.

A statement of compliance with type approval.
See configuration control.
Page 81 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
In non-electrified areas the common rail is bonded with track circuit bonding. In
electrified areas the common rail is known as the traction return rail and carries
the traction return current. It is therefore bonded with traction return bonding.
Also referred to as single rail or traction rail.
COMMON RAIL BONDING
(CR)
A track circuit arrangement where only one rail (the Insulated Rail) is used with
IRJs to separate the track circuits. The other ran (the common rail) is
electrically continuous but is not used for traction return purposes.
COMPETENT PERSON
A person who has the qualifications or certification, experience and ability

necessary to perform a particular task.
COMPREHENSIVE
APPROACH LOCKING
A form of approach locking on a signal, by which the approach locking is only

effective when a train is approaching in order to afford maximum train operating
flexibility. It uses look-back circuitry or logic to ascertain the line occupancy
between a given signal at danger and the sighting point of the signal displaying
the first caution aspect for the signal under consideration.
CONCENTRATOR
A facility to connect several telephone circuits to one terminal and thus avoid the
need for a telephone instrument for each circuit.
CONFIGURATlON
(system)
CONFIGURATION
CONTROL
The structuring and interconnection of the hardware and software of a system.

A procedure to confirm that the functional and physical characteristics of a design
or product are adequately identified and that changes to these characteristics are
controlled and traceable throughout the life-cycle of the design or product, by
recording its version or modification state.
Also known as version control.
CONSTRUCTION
The carrying out of any building, civil engineering or other engineering work,
particularly that which falls within the scope of the Construction (Design and
Management) Regulations 1994.
Also know as installation.
CONTACTOR
A relay with heavy duty contacts.
CONTINUITY BONDING
Fishplate bonding specifically provided for traction return purposes, i.e. on nontrack circuited lines in electrified areas, including non-electrified sidings, etc. Rail
to rail bonding is required and cross bonding may also be provided.
It is denoted by the addition of a ccc symbol on the bonding plan.
CONTROL AREA
The area of railway controlled or supervised by a particular signal box or control

centre, as defined by the signalling Plan.
Also known as signal box control area.
CONTROL POINT
A signal box (including control centre), gate box or ground frame (including
ground switch panel or shunting frame).
CONTROLLED FUNCTION
A signalling function that, under ordinary operation, is controlled from the signal
box (or other control point) to which the function is allocated and may be
interlocked with other signalling functions.
CORRECTIVE
MAINTENANCE
The maintenance carried out after fault recognition and intended to put a product
into a state in which it can perform a required function. (BS EN 50126)
CORRELATION
The comparison of the configuration and version status of a system with the
design records to confirm that the two are in agreement.
CORRELATION
DIAGRAMS
A copy of the signalling design records, issued for correlation purposes and
endorsed Correlation Copy. Correlation diagrams are generally derived from
the latest version of the source record or copied from the master record.
CROSS BOND
A jumper cable cross connecting the common rails or centre points of

impedance bonds of parallel tracks to form a mesh of alternative paths, e.g. for
traction return current.
CROSSING ANGLE
CROSSING BACK
Page 82 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
CROSSING LENGTH
(LEVEL CROSSING)
Applicable to any vehicular crossing. At a crossing equipped with gates or full

barriers, it is the distance between the gates or barriers across the railway
measured down the centre of the road. At an open crossing or one equipped with
half barriers, It is the distance between the give way or stop line down the centre
of the crossing, to a point at which a road vehicle would be clear of the railway or
crossing equipment on the far side.
CROSSING NOSE
CROSSING USERS
(LEVEL CROSSING)
People crossing the railway on or at a level crossing. This includes pedestrians,

horse-riders and occupants of road and agricultural vehicles.
CUSTODIAN (of records)
The organisation appointed Network Rail to take care of master records.

Also known as records custodian.
CUT-SECTION (location)
Non-preferred term; see repeater location.
CUT-SECTION (track
circuit)
A method of reducing the continuous length of a track circuit by the use of

individual track circuits, each one controlling a common final track repeat relay, or
equivalent. These are indicated as one track circuit on the signallers panel.
CUT-OFF CONTACT
(relay)
A front contact of a latched relay, internally wired in series with the release coil
such that the coil cannot be energised unless the relay is in the operated
position. Also known as economising contact.
D.C. ELECTRIFIED AREA
An electrified area equipped for d.c. electric traction; including a buffer zone
where the track circuit equipment is immunised against the d.c. traction voltage,
extending generally for at least 3000m along any lines equipped solely for a.c.
traction. (The distance is subject to specialist assessment and verification.)
DARK MODE
On failure, the level crossing enters Dark Mode where all lamps are
extinguished, audible warnings silenced and crossing users are expected to use
the telephone to obtain assistance
DATA (signalling)
Site specific geographical and control information in an electronic form, which

may be of a safety-critical nature or otherwise. In order to be used in an
electronic system or sub-system, data from master data files is usually
permanently stored in an EPROM (erasable programmable read only memory).
DATA COLLECTION AREA
The area of railway over which the train describer or IECC gathers information
about train movements. It extends beyond the control area of the signal box.
DATA LINK
A serial data transmission system.

In SSI systems, this refers to the link between the interlocking and the lineside
location and may take the form of a baseband unmodulated trackside data link
cable, or a long line link using standard telecommunications PCM equipment.
Internal data link cables are also provided between the modules in an SSI cubicle
and, where applicable, between modules in adjacent interlocking cubicles.
DCI
Drivers crossing indicator, includes drivers white light and drivers red light
DECISION POINT
Applies to user-worked crossings, footpath crossings and bridleway crossings. It

is a point where guidance on crossing safely is visible and at which a decision to
cross or wait can be made in safety.
DE-ENERGISED (relay)
See released.
DEFECT
See fault, defect, error, failure, mistake.
DEGRADED CONDITIONS
The state of the part of the railway system when it continues to operate in a
restricted manner due to the failure of one or more components. (source: RSPG)
DEMODULATOR
See modem.
DEPENDABILITY
The ability of a product to perform one or several required functions under given
conditions. See also RAMS. (source: BS EN 50126)
Page 83 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
This is also known as a multi-section track circuit.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
DEPENDENT CONTACT
NR/L2/SIG/11201
014
06/09/2014
A contact set which consists of a front contact, a back contact and one arm
shared between them, with not more than one contact path made at any one
time.
Also referred to as change-over contact.
A wide term including standard and the production of drawings, design details
and bills of quantity (including standard of systems or equipment). (source: CDM
Regulations - modified)
DESIGN AUTHORITY
Network Rail or such other organisation as is contracted by Network Rail to

undertake specified design work on a system or on the infrastructure.
DESIGN DETAILS
(signalling)
Any plans, control tables, engineering details and data, which are required to
sufficiently define signalling systems and equipment for production or record
purposes.
DESIGN RECORDS
Design Details defining the current state of the infrastructure.
DISCONNECTION BOX
An apparatus housing for unprotected outdoor use, which is intended to contain

mainly terminations and is commonly smaller than an apparatus case.
DISCREPANCY
The discovery of a difference between the signalling design records and the
signalling infrastructure observed on site.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
DESIGN
DISPROVED WRONG SIDE

FAILURE
A failure which was reported as wrong side but where the failure was
conclusively shown not to have occurred or to have been a right side failure.
DIVERSITY
A means of achieving all or part of the specified requirements in more than one
independent and dissimilar manner. (source: BS ENV 50129)
DOUBLE-COIL A.C. VANE

RELAY
A double element relay with separate local and control (or track) coils which are
required to attain a particular phase relationship for the relay to operate.
DOUBLE-CUT (circuit)
The inclusion of controls in both feed and return legs in order to mitigate the risk
associated with a false feed or earth fault.
DOUBLE-JUNCTION
The point of junction of two double track routes. It comprises two turnouts and a
crossing.
DOUBLE-POLE (lamp)
A double-filament lamp in which both filaments are connected permanently in

parallel. (source: BS 469)
DOUBLE-RAIL TRACK
CIRCUIT
A track circuit, either jointless, or defined by IRJs in both rails at all its
extremities. On electrified lines, both rails carry traction return current.
DOUBLE-RAIL TRACK
CIRCUIT BONDING (DR)
A track circuit arrangement where both rails are fitted with IRJs, or tuned zones
are used to completely isolate a track circuit.
DOUBLE-WOUND
A relay fitted with two electrically independent operating coils. Application of

rated voltage across either coil causes the relay to operate.
DOWN TIME
The time interval during which a product is in a down state. (source: BS EN

50126)
DPI
Drivers points indicator. Provided at some TOB stop boards that are co sited with
RETB & NSKT block posts
DRACAS
An acronym meaning Data Recording and Corrective Action System.
DRIVER ONLY
OPERATION (DOO) RADIO
DROP-AWAY TIME (track
circuit)
A form of Cab Secure Radio especially provided to facilitate driver only operation.
The time between the application of a shunt to the rails and the front contacts of
track relay (TR) fully opening.
The converse is pick-up time.
DROP AWAY (DA)

VOLTAGE (relay)
The maximum voltage applied to an operated relay coil at which the last front
contact breaks.
DROP SHUNT
The maximum value of non-inductive resistance which, when placed across the
rails, causes the track relay to fully open its front contact.
DRL
Drivers red light.
Page 84 of 100

NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
DUAL ELECTRIFIED AREA
An electrified area meeting the criteria of both an a.c. electrified area and a
d.c. electrified area.
DWL
Drivers white light
EARTH FAULT
Unintentional contact between a circuit conductor and a conductive part at earth

potential, by which an earth fault current may flow.
EARTH FAULT DETECTOR
A permanent device, wired to the busbars, that will detect an earth fault on the
power supply and give an alarm that will alert the maintainer.
Also known as earth leakage detector.
EARTH FAULT LOOP

IMPEDANCE
The impedance of the earth fault current loop starting and ending at the point of
earth fault. (source: BS 7671 extract)
EARTH LEAKAGE
DETECTOR
ECONOMISING CONTACT
(lever lock)
See earth fault detector.
ECONOMISING CONTACT
(relay)
ELECTRIC TRACTION
ENGINEER
ELECTRICAL SYSTEM
See cut-off contact.
A contact internally wired in series with the coil such that the lock coil is not
energised when the lever is in the full travel position. Alternatively the function
may be controlled externally (which is the only available method where cut-off is
required at other than a full travel position).
Engineer responsible for the electric traction fixed equipment.

An installation, identified by the relationship that the source and the exposedconductive-parts of the installation have to earth:
TN system: where one or more points of the energy source are directly
earthed, the exposed-conductive-parts of the installation being connected
to that point by protective conductors, either completely separate from the
neutral or return conductors (TN-S), with the neutral and protective functions
combined in a single conductor throughout the system (TN-C), or with the
neutral and protective functions combined in a single conductor in part of the
system (TN-C-S).
TT system: where one point of the energy source is directly earthed, the
exposed-conductive-parts of the installation being locally earthed,
independent of the source earth electrodes.
IT system: where there is no connection between the live parts and earth, the
exposed-conductive-parts of the installation being locally earthed, e.g. an
unearthed signalling power supply.
(source: BS 7671 adapted)
ELECTRIFIED AREA
An area of railway encompassing all lines equipped for electric traction, extended
to include any non-electrified lines or sidings. The area also includes a buffer
zone where track circuit equipment is immunised against traction interference,
extending generally for at least 800m, or the length of two track circuits with
double IRJs, whichever is the further, beyond the end of the electrified line.
See also a.c. electrified area, d.c. electrified area and dual electrified area.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
EMERGENCY SITUATION
A current unforeseen or unplanned event which has life threatening or extreme

loss implications and requires immediate attention (e.g. a fire). (source: RSPG)
ENERGISED
See operated.
ENGINEERING DETAILS
(signalling)
EQUIPOTENTIAL
BONDING
Design details from which a signalling system is constructed.
ERROR
The confirmation of a discrepancy after independent verification. It may be

classified as a clerical error, a records error, a design error, or an installation
error.
ERTMS
European rail traffic management system
Electrical connection maintaining various exposed-conductive-parts and

extraneous-conductive-parts at substantially the same potential. It need not
include a direct connection to earth. (source: BS 7671 augmented)
Page 85 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
EXPOSED-CONDUCTIVEPART
A conductive part of equipment that can be touched and which is not a live part
but which may become live under fault conditions. (source: BS 7671)
EXTERNAL (circuit or
power supply)
EXTRA LOW VOLTAGE
Failing to wholly meet the internal criteria.
EXTRANEOUSCONDUCTIVE-PART
A conductive part liable to introduce a potential, generally earth potential, and not
forming part of the electrical installation, e.g. structural metalwork. (source: BS
7671 augmented)
FAIL-SAFE
A concept which is incorporated into the design of a product such that in the
event of failure, it enters or remains in a safe state. (source: BS ENV 50129)
FAILURE
The termination of an item to perform a required function. (source: BS 4778)
See voltage, nominal.
FAILURE
CLASSIFICATION
FAULT TOLERANCE
Classification of a Failure as Right Side, Wrong Side, protected, etc.
FAULT, DEFECT, ERROR,

FAILURE, MISTAKE
The cause of an error is a fault (for example a hardware defect) which resides
temporarily or permanently in the product. An error is that part of the product
state which is liable to lead to a failure. A failure occurs when the delivered
service deviates from the intended service. A failure is the effect of an error on
the intended service. A mistake occurs when human action (at any phase of the
life-cycle) may result in unintended product behaviour. (source: BS EN 50126
modified)
FAULTING
See corrective maintenance.
FEED
Power Supply phase (BX) or positive (B) connection.
The attribute of an item that makes it able to perform a required function in the
presence of certain given sub-item faults. (source: BS EN 61508)
In some cases may be used as a composite term to incorporate both feed and
return (e.g. track circuit feed).
FISHPLATE BOND
Provided to confirm electrical continuity between two rails mechanically

connected, e.g. by a steel fishplate, common chairs, or other bolted connection.
Also referred to as fishplate type bond, or rail joint bond.
FISHPLATE TYPE BOND
See fishplate bond.
FIXED DATA
See system program.
FREE-WIRED
INTERLOCKING
A relay interlocking that comprises individually wired relays rather than pre-wired
sets of relays.
FREQUENCY DIVISION
MULTIPLEX (FDM)
A data transmission system that uses unique frequencies to separate channels

over a single pair of conductors.
FREQUENCY ROTATION
The sequential application of specified frequencies.
FRONT (F) CONTACT
A contact which is made when the relay is operated and broken when it is
released.
FUNCTIONAL EARTHING
The connection to earth necessary for the proper functioning of electrical

equipment, i.e. an earth return. This may be used for telecommunications
purposes, but is no longer permitted for new signalling circuits. Conductors for
functional earthing are identified by the colour cream. (source: BS 7671
augmented)
FUNCTIONAL SAFETY
ANALYSIS
Assessment of elements within a safety system to demonstrate that it attains the

required safety integrity.
FUNCTIONAL UNIT
An entity of hardware or software, or both, capable of accomplishing a specified

purpose. (source: BS ENV 50129)
Page 86 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
See also fault, defect, error, failure, mistake, common cause failure, random
hardware failure, and systematic failure and fault, defect, error, failure,
mistake.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
FUNDAMENTAL CAUSE
(failure)
NR/L2/SIG/11201
014
06/09/2014
A primary deficiency or prevailing condition which permitted the immediate

cause to lead to a wrong side failure.
GEOGRAPHICAL DATA
Fixed information stored in EPROMs that configures an electronic system or subsystem to the requirements of a particular site.
GEOGRAPHICAL
INTERLOCKING
A route relay interlocking in which standard pre-wired sets or relays are provided
for each signalling function, arranged and electrically interconnected in a
geographical manner.
GRACEFUL
DEGRADATION
A means by which a more complex control sub-system has the facility to switch
into some other (more restricted) mode of operation if a particular input fails, or if
availability is otherwise reduced by some means.
GUARANTEED POWER
SUPPLY
HAND OPERATION
(Level crossings)
HAZARD
See secure power supply.
HEADWAY CHART
A time / distance graph based on standard braking and acceleration curves that
may be used to determine optimum signal positions.
HEAVY (H) DUTY

CONTACT (relay)
A relay contact that is rated to make and break a current of up to 30A. These
generally have magnetic blow out to suppress the arc, but are not guaranteed to
be non-weld and so the relay shall be down proved.
HEEL (of switch)
HIGH CURRENT D.C.

ELECTRIFIED AREA
A d.c. electrified area capable of supplying trains with a peak total traction
current in excess of 6.5kA.
HMRI
Her majestys railway inspectorate
IMMEDIATE CAUSE
(failure)
IMPEDANCE BOND
A direct act, omission or equipment fault which triggered the failure.
A facility to allow manual operation of barriers during, for instance, power failure
A physical situation with a potential for human injury. (source: BS EN 61508)
Special device which presents a low impedance to traction current and a higher
impedance to track circuit current.
INCIDENT (near miss)
An unplanned, uncontrolled event, which under different circumstances could

have resulted in an accident.
INDEX (configuration
control)
A listing of design details for the configuration control of signalling systems

(including status record index sheets for software).
INFRASTRUCTURE
MANAGER
INSTALLATION (activity)
The person who

In relation to infrastructure other than a station, is responsible for developing
and maintaining that infrastructure or, in relation to a station, the person who is
responsible for managing and operating that station, except that it shall not
include any person solely on the basis that he carries out the construction of that
infrastructure or station or its maintenance, repair or alteration; and
Manages and uses that infrastructure or station, or permits it to be used, for the
operation of a vehicle; (source: ROGS 2006)
See construction.
INSTALLATION
(infrastructure)
That part of the signalling system associated with the infrastructure at a

particular place.
INSULATED BLOCK JOINT

(IBJ)
INSULATED RAIL
Non-preferred term; see insulated rail joint.

The rail of a single rail track circuit that is fitted with IRJs to separate adjacent
track circuits. The insulated rail is always bonded with track circuit bonding, as
it does not carry traction return current.
Also known as signal rail.
Page 87 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Also known as Basic Event.
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
INSULATED RAIL JOINT
(IRJ)
014
06/09/2014
A method of joining rail ends together whilst maintaining electrical insulation

between them.
An alternative non-preferred term is insulated block joint (IBJ)
INTERLOCKING (building)
The (generally dedicated) building housing the interlocking system, where

separate from the signal box (or other control point).
INTERLOCKING
(equipment)
INTERLOCKING (system)
The equipment that performs the role required of the interlocking system.
INTERLOCKING AREA
The area of railway controlled by a particular interlocking, extended up to a

boundary with each other adjacent interlocking controlled by the same or another
signal box.
INTERNAL (circuit)
A circuit that does not leave the apparatus housing in which it originates and
which is fed from a busbar which feeds only internal circuits. This includes the
feed to an isolated transformer supplying an external circuit. Circuits that extend
between adjacent apparatus housings may be considered to be internal if they
are run in a protective non-conducting duct and are judged to be away from any
environment that might be susceptible to earth faults.
INTERNAL (power supply)
A power supply feeding only internal circuits. Also known as local power supply
INTOLERABLE (risk)
Associated with a risk that is greater than the upper limit of tolerability
JOINT HOPPlNG
Where fast moving short vehicles pass from one track circuit to the next, the
difference between the pick-up and drop-away times can cause the vehicle to
momentarily be undetected.
JOINTED TRACK ClRCUIT
A track circuit whose extremities are defined by the use of IRJs.
JOINTLESS TRACK
CIRCUlT
A track circuit whose extremities are defined by the use of tuned circuit
techniques, The extreme limits of a jointless track circuit area are either defined
by the use of IRJs or by the use of a tuned circuit between the rails.
JUMPER
An interconnecting cable (commonly single core) between two termination points

within an apparatus housing.
JUMPER CABLE (track

circuit / traction)
An interconnecting cable (commonly single core) between two pieces of rail that
are not adjacent, for track circuit or traction purposes. This includes midpoint
connections to impedance bonds.
JUNCTION INDICATOR (JI)
A route indicator that has category one (long range) performance and displays
the route at a signal by means of a line of white lights.
KEYBOARD
An interface between an operator and a system facilitating the input of

commands or data.
LAMP PROVING RELAY
A neutral d.c. relay designed to operate from the current supplied to signal lamps
and to release when lamp or lamps burn out. Some relays incorporate a bridge
rectifier to operate from a.c. lamp currents.
LATCH
A memory location that switches between two states, representing a particular

signalling function. The states are commonly known as set and unset.
LATCHED RELAY
A relay that switches between two states, representing a particular signalling

function, and stays in the last set position when the operating feed is removed.
The states are known as operated and released.
LEFT HAND RELAY
The left hand half of a twin relay as viewed from the front. In a 930 series twin
relay this controls the contacts in banks C and D.
LEVEL CROSSING
GROUND PLAN
A scaled and dimensioned drawing showing the position of all equipment, utilities
and associated features in the vicinity of the level crossing, and the detail
necessary for engineering, operating and statutory requirements.
LEVEL CROSSING ORDER
A statutory instrument from the secretary of state for transport describing the
application of the RSPG to a specific level crossing. Formerly known as section
order.
The safety-critical locking provided between signalling functions in accordance

with control tables.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 88 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
LEVER (OR SWITCH)

NOMENCLATURE PLATE
A plate fixed to a lever or adjacent to a switch, describing the lever / switch

function, together with order of pulling details.
LIFE-CYCLE COST
The total cost of ownership of an item taking into account all the costs of
acquisition, personnel training, operation, maintenance, modification and
disposal. (source: BS 4778)
Also known as whole-life cost.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
LIKE-FOR-LIKE WORK
The removal and restoration of an item of equipment (including a cable

renewals), where the work does not require any update to signalling design
details.
LINE CIRCUIT
An external relay circuit, which is not an trackside circuit.
LINESIDE APPARATUS
HOUSING
LINESIDE LOCATION
See apparatus housing.
LOCAL PANEL
A panel (sometimes simplified) provided at the interlocking and capable of being

used to take over control from the main panel at the signal box. It may also be
used as a maintainers monitoring panel, when the operating function is not in
use.
LOCAL POWER SUPPLY
See internal power supply.
LOCATION
A group of all signalling lineside apparatus housings (including buildings) at a

particular site and the equipment contained therein. (This excludes apparatus
housings that perform a main interlocking function, although some
interlocking local to ground frames or level crossings may be included.)
See location.
Alternatively known as lineside location.

LOCATION AREA PLAN
A scale layout plan showing every signalling location, together with their
identities, position and type of cases, interlocking boundaries, certain equipment
identities (e.g. TFMs) and the area of signalling equipment that is controlled by
each location.
This plan is generally a sub-version of the scheme plan or signalling plan.
LOW VOLTAGE
See voltage, nominal.
LOW VOLTAGE ALARM
See under voltage detector.
MAIN (optical system)
Primary lamp or filament of a duplicated pair.
MAIN CABLE
A twin or multicore lineside cable carrying signalling functions or power

supplies between apparatus housings.
MAIN EARTHING
TERMINAL (MET)
The terminal or bar provided for the connection of protective conductors,

including equipotential bonding conductors, and conductors for functional
earthing if any, to the means of earthing. (source: BS 7671)
MAINTAINABILITY
The ability of a product under given conditions, to be retained in, or restored to, a
state in which it can perform its required function. (source: BS ENV 50129)
MAINTAINED LOCKING
An alternative to the term route locking. (see GK/GN0802)
MAINTAINERS
MONITORING PANEL
An indication panel situated at the interlocking that repeats the indications sent to
the signaller and allows the maintainer to observe the state of the interlocking. It
also indicates various fault conditions. This may be combined with a test panel.
MAINTAINERS TERMINAL
This consists of a VDU, keyboard and printer connected to a solid state

interlocking, or an IECC system monitor sub-system. It is used to obtain
essential fault diagnostic information and also acts as an interface with the
system to enable restrictive controls on the equipment to be set.
Also known as technicians terminal.
MAINTENANCE
The combination of all technical and administrative actions, including supervision

actions, intended to retain a product in, or restore it to, a state in which it can
perform a required function. (source: BS EN 50126)
MAINTENANCE RECORDS
Design records kept on site for maintenance purposes.
Page 89 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
MAJOR WORKS
Any infrastructure alterations which are outside the scope for minor works.
MAKE-BEFORE-BREAK
CONTACTS
A pair of relay contacts, where at each state of the relay only one of the pair is
made, but which during transit momentarily have both contacts made.
MASTER RECORD
The certified signalling design record from which duplicates are obtained for
issue.
See also source record.
MECHANICAL LOCKING
CHART
A plan showing the arrangement of mechanical locking components to achieve

the mechanical locking control tables.
MECHANICAL LOCKING
CONTROL TABLES
A tabulation of the locking between signalling functions associated with a

mechanical lever frame.
MEDIUM (M) DUTY

CONTACT
A relay contact that is rated to make and break a non-inductive current of 3A to

6A.
MESHED CIRCUIT
Complex circuitry feeding more than one relay, where the same could be
achieved by independent circuits, thereby requiring duplication of contacts. Not
all paths in a meshed circuit are applicable to all relays.
MICROCORE
A parallel data transmission system using a multicore cable having a large

number of small diameter conductors. Interface buffer relays may be provided at
each end.
MINIATURE ROUTE
INDICATOR (MI)
An alphanumeric route indicator having category three (short range) performance

(equivalent to the former stencil route indicator).
MINOR WORKS
Infrastructure Alterations which are listed as such in HSE/HMRI Guide to the

Approval of Railway Works, Plant and Equipment.
MISTAKE
MOD STATE
See modification status.
MODEM
An electronic device that converts a signal to make it suitable for transmission

(modulator) or reception (demodulator) of information over a particular medium.
MODIFICATION STATUS
The detail that defines the particular version of the design or standard,
appropriate to the functional and physical characteristics of an item of equipment
or system, and is recorded under configuration control procedures.
MODIFICATIONS
Changes to the design details which are required to be carried out after they have
been officially issued, usually as a result of installation, testing and
commissioning activities.
MODULATOR
See modem.
MONITORED (level
crossing)
Checked by the observation of indications which provide the signaller with the
status of equipment.
MOVEMENT AUTHORITY
Permission for a train to run to a specific location.
MROT
Minimum road open time, the time after the level crossing road traffic light signals
have ceased to show before they show again for another train
MSL
MULTI-PROCESSOR
MODULE (MPM)
Miniature stop lights.

NOTE: MWL was an older name for this crossing type
The part of an SSI system that performs the interlocking. Each SSI cubicle
contains three MPMs that control the signalling using a majority voting technique
to confirm safety and availability.
MULTI-SECTION (track
circuit)
NATIONAL RADIO
NETWORK (NRN)
NEGLIGIBLE (risk)
See cut-section.
NEUTRAL RELAY
A d.c. relay which operates with either polarity of supply to the coil.
A radio telephone system provided specially to facilitate railway operations.

Associated with a risk that is less than the lower (broadly acceptable) limit of
tolerability.
Page 90 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Colloquially known as mod state.
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
014
06/09/2014
NON-CONCEPTUAL
WORK
Work which is based directly on an applicable existing proven design and does
not introduce new design features to a system.
NON-SAFETY-CONTACT
A relay contact that is not a safety contact. This includes metal to metal contacts
for medium duty use, where both elements are made of silver, silver cadmium
oxide, or 60/40 silver palladium.
NON-SAFETY-RELATED
A signalling function or sub-system where operational safety and the integrity of

the interlocking are not directly affected. Manual intervention, where a failure
would be noticed, may be part of the process.
Formerly known also as non-vital.
NON-VITAL
See non-safety-related.
NORMAL (function)
Position of a lever when it is fully back in the lever frame. The un-operated or
quiescent state of a two-state system.
The converse is reverse.
NORMAL CONTACT
A contact in a polar relay, which is closed when the relay is operated to the
normal position.
NORMAL (conditions)
The operating conditions which a part of a railway is designed to accommodate.

This would include peaks, e.g. rush hours, and troughs in demand experienced
during the day. (source: RSPG)
OPERATE COIL
A winding which when energised at the rated voltage and frequency, causes the
armature of a relay to move to the operate position.
OPERATE TIME (relay)
The time interval between the energisation of the relay coil and the first front
contact making.
The converse is release time.
OPERATE VOLTAGE
(relay)
The minimum voltage applied to a released relay coil at which the last front
contact makes.
Also known as pick-up (pu) voltage.
OPERATED (relay)
The state of a relay when the armature is energised, picked up (PU), or latched,
all front contacts are made and all back contacts are broken.
Also known as energised, and colloquially as picked or up. The converse is
Released.
OPERATING NOTICE
DIAGRAM
A simplified layout plan for publication in, or with, the signalling alterations section
of an operating notice.
OPTICAL FIBRE
An optically transparent fibre consisting of a central core surrounded by a

cladding of lower refractive index and used to transmit lights by means of multiple
internal reflections.
ORDINARY ACTING (relay)
A relay without a particular stated specialised operating characteristic.
OUT OF USE
Non-operational equipment that is still connected to the infrastructure.

See also spare.
OUTLINE PROJECT
STANDARD (OPS)
OVERLAPPING DESIGN
A document listing the principal elements of proposed works.

Design undertaken in a compressed timescale such that activities relating to
different alterations which would usually be undertaken sequentially are
undertaken concurrently. This is only permitted where one design engineer is
identified as having overall responsibility for the interface between the successive
design alterations.
OVERLAY TRACK
CIRCUIT
A track circuit which can be superimposed over another, neither having any effect
on the other and both operating independently.
PARALLEL (bonding)
The method of bonding rail sections with diverse parallel electrical paths for
availability. track circuit bonding in this mode is non-fail-safe, since failure of
a single jumper cable, fishplate bond, or IRJ will not necessarily release the
track circuit relay, and hence could result in loss of vehicle detection.
Page 91 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
PARALLEL DESIGN
Design undertaken in a compressed timescale such that activities relating to the

same alteration which would usually be undertaken sequentially are undertaken
concurrently.
PARALLEL (data link)
A means of data transmission by which many discrete bits of information are sent
at the same time along a microcore link.
PICK-UP (PU) SHUNT
The minimum value of resistance between the two running rails at which the track
relay just closes its front contacts.
PICK-UP (PU) VOLTAGE

(relay)
PICK-UP TIME (track
circuit)
See operate voltage.

The time between the removal of a shunt to the rails and the first front contact of
the track relay (TR) making.
The converse is drop-away time.
PIN-CODE
See registration pin-code.
PLUG-IN
The attribute of an item of electrical equipment which can be replaced without

disconnecting any wiring.
PLUGBOARD
The permanent mounting block and termination for external wiring, for use with
plug-in equipment.
POLAR (relay)
A relay with two operated positions (normal and reverse) and a central,
released state. The operated position depends upon the direction of the current
or phase of the current in the operating circuit. A polar relay may not have
contacts in the Released position.
An alternative non-preferred term is polarised (relay).
See also biased relay (sometimes referred to as a 2-position polar rely).
POLARISED CIRCUIT
A circuit where the resulting operation is dependent on the polarity or phase

angle of the feed.
POLARISED (relay)
Non-preferred term; see polar (relay).
PRESELECTION
The selection of a signalling function prior to the conditions becoming available,

so that it is automatically set when some other function is restored. This could
result in a protected wrong side failure becoming unprotected.
PREVENTATIVE
MAINTENANCE
The maintenance carried out at predetermined intervals or according to

prescribed criteria and intended to reduce the probability of failure or the
degradation of the functioning of an item. (source: BS EN 50126)
PRIMARY FUNCTION
RELAY
The relay by which the logic required to control a signalling function is brought
together. It is the first relay in a chain that directly controls all safety-critical
signalling functions. it is the only function relay which has back contacts valid
for use in safety-critical functions.
PRODUCT ACCEPTANCE
Authorisation of a product type for use. See NR/L2/RSE/100
PROGRAMMABLE LOGIC
CONTROLLER (PLC)
A self-contained electronic sub-system that manipulates date. It receives inputs

from an interface, processes them in accordance with the system program and
geographical data in its memory and returns the resulting outputs to the
interface.
PROJECT ENGINEER
Senior Engineer within the Project responsible for the work.
PROTECTIVE
CONDUCTOR
A conductor used for some measures of protection against electric shock and
intended for connecting together any of the following parts:
exposed-conductive-parts;
extraneous-conductive-parts;
the main earthing terminal;
earth electrode(s);
the earthed point of the source or an artificial neutral.
Protective conductors are identified by the colours green and yellow. (source: BS
7671 augmented)
Page 92 of 100
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
PUBLIC EMERGENCY
TELEPHONE SYSTEM
(PETS)
A special telephone system for use at level crossings, which includes provision
for proving that handset connections are intact and also for the transmission of
level crossing status indications. The speech path has priority over other
facilities.
PULSE CODE
MODULATION (PCM)
A serial data transmission system by which many channels of information are

passed over a data link, by use of a multiplexer.
QUARTZ HALOGEN LAMP
See Tungsten Halogen Lamp.
RAIL JOINT BOND
See fishplate bond.
RAIL SECTION (track

circuit)
A section of one running rail continuously electrically bonded with its extremities
defined by IRJs, and within which all continuity connections are by fishplate
bonds. It may extend over several track circuits as the common rail) or only
part of a track circuit.
RAMS
An acronym meaning a combination of reliability, availability, maintainability

and Safety. See also dependability. (source: BS EN 50126)
RANDOM HARDWARE
FAILURE
Failures occurring at random times, which result from a variety of degraded

mechanism in the hardware.
Note 1) There are many degradation mechanisms occurring at different rates in
different components and since manufacturing tolerances cause components to
fail due to these mechanisms after different times in operation, failures of a total
equipment comprising many components occur at predictable rates but at
unpredictable (i.e. random) times.
Note 2) A major distinguishing feature between random hardware failures and
systematic failures is that system failure rates (or other appropriate measure),
arising from random hardware failures, can be predicted with reasonable
accuracy but systematic failures, by their very nature cannot be accurately
predicted. That is, system failure rates arising from random hardware failures
can be quantified with reasonable accuracy but those arising from systematic
failures cannot be accurately quantified. (source: BS EN 61508)
RECEIVER (Rx)
An electronic device that converts, filters or decodes into a discrete output,

information that has been received from another site.
RECORD
Information bearing media, irrespective of date or physical format, created or

received in the course of carrying out the duties and functions of an undertaking,
and subsequently retained by the undertaking or its successors as evidence, as a
reference source, or to meet legal or regulatory obligations.
RECORDS CUSTODIAN
See custodian (of records).
RED BOND
A traction bond that has been designated as being dangerous to staff if

disconnected. It is marked red to draw attention to its importance and to aid
inspection. Special procedures are in place for the reporting of damage to a red
bond.
REDUNDANCY
The provision of one or more additional elements, usually identical, to achieve or

maintain availability under failure of one or more of those elements. (source:
BS ENV 50129)
REGISTRATION PIN-CODE
A series of locating pins assembled in a unique pattern to prevent equipment

being incorrectly used. The unique pattern also acts as a means of identification
for a specific style and variant of a relay.
The term registration pin-code is commonly abbreviated to pin-code.
RELEASE COIL
A winding which, when energised at the rated voltage, disengages the latching
mechanism and causes the relay to release.
RELEASE TIME (relay)
The time interval between the removal of the supply (at rated voltage) to the relay
coil and the last front contact breaking.
The converse is operate time.
Page 93 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
RELEASED (relay)
NR/L2/SIG/11201
014
06/09/2014
The state of a relay when the armature is de-energised, dropped away (DA), or
unlatched, all back contacts are made and all front contacts are broken.
Also known as de-energised and colloquially as dropped or down.
The converse is operated.
RELIABILITY
The ability of an item to perform a required function under stated conditions for a
stated period of time. (source: BS ENV 50129)
RELOCATABLE
EQUIPMENT BUILDING
(REB)
REPEATER LOCATION
Apparatus housing to standard BR 1615 or equivalent.

A lineside location where all line circuits are interrupted by the provision of
repeat relays for the purpose of limiting interference voltage.
Also known as cut-section location.
RESIDUAL VOLTAGE
The voltage remaining across the rails or relay of a track circuit after the feed has
been disconnected.
It may be caused by mutual interference between adjacent single rail track
circuits, the battery effect of the track formation, cathodic protection measures,
or d.c. traction return or other stray currents.
RESOLVED (failure)
At the time of closure of the investigation, the engineer is satisfied that a fault
occurred and the cause has been established.
RESPONSIBLE DESIGN
ENGINEER
Person directly employed by the design authority who has delegated

responsibility for the design, development, safety and dependability of an
engineering discipline associated with an infrastructure project.
RESPONSIBLE ENGINEER
Engineer responsible for an alteration to the signalling infrastructure, or the

records thereof, or otherwise taking responsibility for correlation.
NOTE In the case of design alterations, this may be the responsible design
engineer, or, in the case of contracted work, it may be the contractor's
responsible engineer. Alternatively, the responsible engineer may be appointed
by the Route Asset Manager (S&T).
RETB
Radio Electronic Token Block
RETURN
Power supply neutral (NX) or negative (N) connection.

The converse is feed.
Position of a lever when it is pulled fully forward in the lever frame. The operated
state of a two-state system.
REVERSE (function)
The converse is normal.

REVERSE CONTACT
A contact, in a polar relay, which is closed when the relay is operated to the
reverse position.
RIGHT HAND RELAY
The right hand half of a twin relay as viewed from the front. In a 930 series twin
relay this controls the contacts in banks A and B.
RIGHT SIDE FAILURE
A failure which does not result in the protection normally provided by the
signalling system being reduced.
ROUTE HOLDING
An alternative to the term route locking (see GK/GN0802).
RSP&G (Applicable to
level crossings)
Railway safety principles and guidance/part 2/section E Guidance on level

crossings
RTL
Road Traffic Light
SAFE STATE
Any one of the following:
SAFETY CONTACT
the state of the last valid request at the interlocking; or

correspondence with the state of the trackside equipment; or
the most restrictive state.
A relay contact that is specified for safety purposes in the 930 series standards.
These are non-weld contacts, generally silver to carbon for ordinary use. For
medium duty use, the contact elements may be of silver impregnated graphite
(SIG) and silver.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 94 of 100
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
SAFETY-CRITICAL
FAILURE
SAFETY INTEGRITY (SI)
014
06/09/2014
Alternative term to wrong side failure.

The probability of a safety-related system satisfactorily performing the required
functions under all the stated conditions within a stated period of time. (source:
BS EN 61508)
SAFETY INTEGRITY
LEVEL (SIL))
One of four possible discrete levels for specifying the safety integrity
requirements of the safety functions to be allocated to the safety-related systems.
Safety Integrity Level 4 has the highest level of safety integrity; Safety Integrity
Level 1 has the lowest. Safety Integrity Level 0 is non-safety-related. (source:
BS EN 61508 augmented)
SAFETY-CRITICAL
Carries direct responsibility for safety. (source: BS ENV 50129)
SAFETY-CRITICAL
FAILURE
SAFETY-RELATED
See wrong side failure.
SCHEME PLAN
A longitudinally scaled layout plan, based on the record signalling plan, that is
produced to depict proposed new or altered signalling systems.
SECTION ORDER
An obsolete term, see level crossing order.
SECONDARY
PROTECTION
SECURE POWER SUPPLY
A back-up safety feature that protects from harm under failure conditions.
Carries responsibility for safety (direct or indirect). (source: BS ENV 50129)
A power supply system that can be relied upon to keep certain safety-critical
signalling functions operating for a predetermined minimum time, in the event
of a total failure of the main incoming supply.
Also known as guaranteed power supply.
SECURITY COPY
The duplicate of a master record provided as a substitute when a master record

is not available at its normal location.
SELECTIVE (TELEPHONE
SYSTEM)
A system with many telephones on one circuit, where one telephone may call
another chosen telephone without all the other telephones receiving the call.
SENSITIVE RELAY
Generally a neutral relay with a high coil resistance and low power consumption.
It may be used to give accurate timings in conjunction with a capacitor / resistor
unit.
SERIAL (data link)
A means of data transmission by which many discrete bits of information are

encoded and sent in turn along a data link
SERIES BONDING
The fail-safe method of bonding track circuits with rail sections connected in
series, such that the failure of a single jumper cable, fishplate bond, or IRJ
results in de-energisation of the track circuit.
SHEATH (cable)
An outer protective layer of a cable containing the insulated conductor(s).
SHORT CIRCUIT BOND
A jumper cable between the rails immediately beyond the final track circuit IRJs,
in order to detect double joint failure. This is the only bonding required on nontrack circuited lines in non-electrified areas.
SIGNAL BOX CONTROL

AREA
SIGNAL BOX NOTES
See control area.
SIGNAL RAIL
Non-preferred term; see insulated rail.
SIGNAL SIGHTING FORM
A form that depicts the profile, location and other details of each signal as agreed
by the signal sighting committee.
SIGNAL SPACING
PARAMETERS
A tabular representation of the parameters (such as braking distances and

average gradients) that may influence the relative positioning of signals.
SIGNALLERS AREA
The area of railway controlled or supervised by any one signaller, as defined by

the boundaries between control panel sections or signalling workstations.
A list of the key features of a signal box, or control centre, including any functions
that are not clear from the signalling / scheme plan.
Formerly known as signalmans area.
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---

Page 95 of 100

Ref:
Issue: 9
Date: 06/09/2
Compliance date:
SIGNALLERS ROUTE
LIST
NR/L2/SIG/11201
014
06/09/2014
A list of all point ends and releases between the entrance and exit signals of a
signalled route, showing the position to which each is required to be set. Route
lists are employed by the signaller when any power operated points are to be
operated manually, or when the points in route setting systems are to be set by
the individual point controls.
SIGNALLING FUNCTION
Final discrete component of a signalling system listed on control tables with a

unique identity (such as signals, points, train detection devices, releases and
level crossing barriers) and the circuitry or logic by which it is controlled an / or
proved.
Signalling functions are allocated (as defined by the control tables) to a specific
interlocking controlled by a particular signal box (or other control point) and are
given a unique identity within a particular signallers area.
SIGNALLING PLAN
A longitudinally scaled layout plan defining a signal box control area and
showing the signalling functions allocated to the signal box with their identities.
Where applicable, it is extended to include the data collection area.
This plan is generally a derivative of the scheme plan.
SIGNALLING SYSTEM
SIGNALLING
WORKSTATION
Equipment, circuitry and software associated with:

lines ide signals;
poi nt operation;
level crossings;
train detection;
trainborne equipment conveying information about the state of the line;
operational telecommunications (excluding electrification control systems and
electrification telephones); and
fixed trackside safety systems.
A workstation controlled by a signalling display sub-system with facilities for
signalling control by trackerball and keyboard together with signalling display
monitors and a general purpose VDU.
SIGNALMANS AREA
Obsolete term, see signallers area.
SIGNALMANS ROUTE
LIST
SIGNIFICANT FAILURE
Obsolete term, see signallers route list.
SINGLE CUT (circuit)
The inclusion of controls in either the feed or return leg, but not both, to be used
only where there is no significant risk of false feeds or earth faults. (See double
cut.)
SINGLE RAIL
Non-preferred term; see common rail.
SINGLE RAIL (SR)

BONDING
CONFIGURATION
A track circuit arrangement where only one rail (the insulated rail) is used with
IRJs to separate the track circuits. The other rail (the common rail) is
electrically continuous and is used for traction return purposes.
SINGLE RAIL (SR)

BONDING
CONFIGURATION
A jointed track circuit with IRJs in only one rail (the insulated rail) that is series
bonded (except for the presence of spurs of limited length at Switches and
Crossings). The other rail, known as the common rail, is electrically common to
one or more adjacent track circuits.
SLEEPER
An item of wood, steel or concrete of standard dimensions, used to support and

gauge the track. (See bearer and timber.)
SLOW ACTING RELAY
A relay in which both operation and release are intentionally delayed.
SLOW TO OPERATE
RELAY
A relay in which the operation is intentionally delayed and the operate time is
significantly longer than the release time.
SLOW TO RELEASE
RELAY
A relay in which the release is intentionally delayed and the release time is
significantly longer than the operate time.
A wrong side failure which by its seriousness or because of its volume

introduces a risk requiring attention.
Page 96 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Formerly known as signalmans route list.
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
SOURCE RECORD
(signalling)
NR/L2/SIG/11201
014
06/09/2014
The signalling design record that does not bear the certification and from which
the medium for production is derived. Examples are a negative or CAD file.
See also master record.
SPARE
Equipment not connected to any part of the infrastructure. See also out of use.
SPUR (track circuit)
A section of running rail required to be electrically common to a series bonded

rail, but which is not itself in series.
STAGGER (electrical)
The phase or polarity difference between one track circuit and the next, or
between the rails on either side of an IRJ within one track circuit.
STAGGER (physical)
Occurs where two IRJs in a pair of rails are not exactly opposite each other, thus
creating a dead section between track circuits or within a track circuit.
STANDARD ROUTE
INDICATOR (SI)
An alphanumeric route indicator having category two (medium range)

performance (equivalent to the former theatre type route indicator).
STANDBY
The state of an item when it is available but not required to be operating.

(source: BS 4778)
STATE (of a function)
Position or action of the equipment. Examples of complementary states are:

operated / released, normal / reverse, on / off, raised / lowered, locked / free,
enabled / inhibited, energised / de-energised.
STATE (of the

infrastructure)
STATUS RECORD INDEX
SHEET (software)
Configuration of an installation.
STOCK RAIL
STRIKE-IN POINT
Initiation point for the operating sequence at an automatic level crossing, an

MCB-CCTV with auto lower facilities, or an MSL
STRUCTURE BOND
A bond required in A.C. Electrified Areas, that connects adjacent lineside metal
structures to the traction return rail system, where required to confirm staff safety
through equipotential zoning.
SUPERVISED (level
crossing)
SUPERVISORY (circuit)
Checked by visual observation, either directly or by use of CCTV.
SWITCH NOMENCLATURE
PLATE
SWITCH RAIL
See lever (or switch) nomenclature plate.
SWITCH REINFORCING
BOND
A jumper cable installed around the switch in S&C, in order to strengthen the
fishplate bonds between the switch and crossing components and also to link two
spur ends together, so improving the integrity of a parallel bonded rail section.
SWITCH TOE
A list of design details and their versions for the configuration control of
software (including ISSR and CISR for SSI systems).
Control or indication circuit, particularly in respect of electric traction power

supplies.
Page 97 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
In data driven systems this is stored as variable data.
NR/L2/SIG/11201
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
SWITCHES AND
CROSSINGS (S&C)
014
06/09/2014
Sections of track other than plain line. See the figure below for constituent parts.
Closure Panels
Heel Of Switch Rail
Crossing Angle
Switch Toes
Switch Rails
Stock Rails
Crossing Nose
Check Rail
Closure Rails
Crossing Back
SYSTEM PROGRAM
The software necessary to drive a programmable electronic system.

Also known as fixed data.
SYSTEMATIC FAILURES
Failures due to errors (including mistakes or acts of omission) in any safety lifecycle activity which cause it to fail under some particular combination of inputs or
under some particular environmental condition. Systematic failures could arise in
any safety life-cycle phase.
Examples of systematic failure include:
Systematic failures due to errors in the safety requirements standard;
Systematic failures due to errors in the design, manufacture, installation,

operation of the hardware;
Systematic failures due to errors in the design, implementation etc. of the

software.
(source: BS EN 61508)
SYSTEMS APPROVAL
Approval granted to systems.
TABLE OF SIGNAL
ROUTES
A comprehensive list of signal routes. They may either be shown on, or

accompany copies of, the signalling / scheme plan.
TAIL CABLE
A cable between trackside or on-track signalling equipment and other such

equipment or a lineside apparatus housing.
For track circuits, see also track cable.
TECHNICIANS TERMINAL
See maintainers terminal.
TEMPORARY WORK
Alterations which remain in use for a limited period of time.
TERMINAL LINE
The length of plain line approaching buffer stops. Single rail traction return is
adequate for the final 300m of such lines in d.c. electrified areas, as traction
return current is low.
TEST PANEL
A control panel provided at the interlocking for testing or maintenance purposes.

It may be provided temporarily for a commissioning or the function may be
performed by the local panel.
TESTER IN CHARGE (TIC)
Signalling engineer responsible for the testing and commissioning of new and
altered signalling systems.
THROUGH CIRCUIT
An external circuit drawn in entirety from supply to destination.
TIMBER
An item of wood of non-standard dimensions, used to support the track in S&C

areas. (See also bearer and sleeper.)
Page 98 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
Wing Rails
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
TIME DIVISION
MULTIPLEX (TDM)
A non-safety-critical serial data transmission system that addresses each

channel in turn and converts it into a unique digital code. It is generally used to
transmit operating controls and indications between a signal box and
interlockings.
TIME ELEMENT RELAY
A relay, whose timing contacts do not change state until a predetermined time
after operation or release, as appropriate.
Commonly known as timer.
TIMER
See time element relay.
TOLERABLE (risk)
Associated with a risk that is within the limits of upper and lower tolerability.
TOUCH POTENTIAL
The potential difference between a persons hand which is touching an exposedconductive-part and any other part of the body which is touching another
exposed-conductive-part at a different potential.
TPWS
Train Protection and Warning System
TRACK CABLE
A track circuit tail cable which connects directly to the rails.
TRACK CIRCUIT
ACTUATOR (TCA)
TRACK CIRCUIT
ACTUATOR
INTERFERENCE
DETECTOR (TCAID)
TRACK CIRCUIT
ASSISTER (TCA)
Non-preferred term, see track circuit assister.

Non-preferred term, see track circuit assister interference detector.
A device fitted to a vehicle which cause a 165kHz signal to pass between the
wheels of the vehicle and assists in the breakdown of the insulation at the wheel
to rail interface due to leaf-fall, rust etc.
TRACK CIRCUIT
ASSISTER
INTERFERENCE
DETECTOR (TCAID)
TRACK CIRCUIT
BONDING
A device fitted to the track which, when it detects the presence of a 165kHz
signal in the rail, causes the track circuit to show occupied.
TRACK CIRCUIT
INTERRUPTER
A device that records the passage of a vehicle by causing a permanent

disconnection within the track circuit until the device has been renewed.
TRACK JUMPING
Occurs when a fast moving vehicle passes over a very short track circuit (or a
short arm of a longer track circuit) and fails to de-energise the track relay.
TRACK RELAY (TR)
Generally a neutral relay with a low coil resistance and low power consumption,
which acts as part of a track circuit. It is either connected directly to the rails, or
via a capacitor or tuner unit.
TRACKSIDE CIRCUIT
An external circuit run to, or via, an item of trackside or on-track signalling

equipment in a tail cable.
TRACKSIDE FUNCTIONAL
MODULE (TFM)
SSI signal or points modules situated in lineside locations to operate and prove
trackside equipment and interface with the data link from the interlocking via the
data link module.
TRACTION BOND
A cable specifically provided for continuity of traction return current, although it

may additionally carry track circuit current.
TRACTION RAIL
See common rail.
TRACTION RETURN
BONDING
The bonding required to carry the traction return current on both ac and dc
electrified lines. Traction return bonding is generally parallel bonded.
TRANSMITTER (Tx)
An electronic device that converts, modulates or encodes a discrete input, into a

form that is suitable for sending to another site.
TRANSPOSITION BOND
A jumper cable provided where track circuit polarities and / or traction return rails
change sides across a pair of IRJs, or transposition joints. Purposes included
the correction of track circuit polarity stagger or traction current imbalance, or to
facilitate series bonding in S&C.
--``,``,,`,,,`,`,```,,`,,`,````

The connection of one rail or component of a track circuit to another rail or

component, so as to confirm electrical continuity. On rails carrying traction return
current its function is performed by the traction return bonding.
Page 99 of 100
Ref:
Issue: 9
Date: 06/09/2
Compliance date:
NR/L2/SIG/11201
014
06/09/2014
TRANSPOSITION JOINT
An IRJ where transposition bonds are used to transpose the traction and / or
track circuit rails.
TRAP POINT
A point (usually switch and tiebar only), inserted in sidings etc., to unauthorised
movements away from a running line.
TRESPASS GUARDS
Arris rails evenly spaced on bearers between both fence lines that make stepping
off the level crossing surface difficult
TRIPLE-POLE (lamp)
A double-filament lamp in which one end of each filament is connected to the cap
shell and the other ends of the filaments are connected one to each contact
plate. (source: BS 469)
TUNGSTEN HALOGEN
LAMP
A lamp in which the tungsten filament is enclosed in a gas filled quartz bulb
containing a quantity of a halogen.
TWIN RELAY
A unit which contains two electrically and mechanically independent relays.
TYPE APPROVAL
Approval granted to an individual product.
UNDER VOLTAGE
DETECTOR
A permanent device, wired to the busbars, to inhibit operation and / or give an

alarm to alert the maintainer, when the voltage falls below an acceptable level.
Also known as low voltage alarm.
UNINTERRUPTABLE
POWER SUPPLY (UPS)
A power supply with a secondary source which is capable of providing an

uninterrupted changeover in the event of a failure of the incoming supply. It
generally consists of low maintenance cells, a charger, voltage regulator, and
monitoring, changeover and bypass devices.
UNRESOLVED (failure)
At the time of closure, exhaustive testing has failed to reveal the fault but the
possibility of a fault has not been totally eliminated.
UPDATE
The process of revising the source record in accordance with the commissioning
of Alterations, Amendments or modifications to design details.
VALIDATION
Confirmation by examination and provision of objective evidence that the

particular requirements for a specific intended use have been fulfilled. (source:
BS EN 61508)
VARIABLE DATA
Information associated with a data-driven system which records the real-time

state of signalling functions.
VAS
Vehicle activated signs
VERIFICATION
Confirmation by examination and provision of objective evidence that the

specified requirements have been fulfilled. (source: BS EN 61508)
VERSION CONTROL
See configuration control.
VISUAL DISPLAY UNIT

(VDU) MAP LAYOUT
A full size layout plan that details the information to be displayed for each screen
overview or detailed view on a VDU.
VOLTAGE, NOMINAL
Voltage by which an installation (or part of an installation) is designated. The

following ranges of nominal voltage (r.m.s. values for a.c.) are defined:
WHOLE-LIFE COST
Extra-low. Generally not exceeding 50V a.c. or 120V ripple-free d.c., whether
between conductors or to earth;
Low. Generally exceeding extra-low voltage but not exceeding 1,000V a.c. or
1,500 d.c. between conductors, or 600V a.c. or 900V d.c. between conductors
and earth. (source: BS 7671 amended)
See life-cycle cost.
WING RAIL
WRONG SIDE FAILURE
A Failure which results in the protection normally provided by the signalling

system being reduced.
Also known as safety-critical failure.

YELLOW BOND
A jumper cable that is necessary to confirm the electrical integrity of a track circuit
that is fully or partially parallel bonded. It is marked yellow to draw attention to
its importance and to aid inspection.
Page 100 of 100

--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---


25/05/2010 - Version 1
Standards Briefing Note

Ref: NR/SIG/11201
Title: Signalling Design Handbook
Publication Date: 06/09/2014
Standard Owner: Professional Head [Signalling and Controls]
Non-Compliance rep (NRNC): Professional Head [Signalling and Controls]
Further information contact: Peter Evans
Purpose:
This standard, sets out mandatory requirements and
mandates standards for the production of signalling
design detail to support:
a) safe development and design of new and altered
signalling systems impacting on Network Rail
controlled infrastructure;
d) clients specified requirements are met and the

design is fit for purpose
Compliance Date: 06/09/2014

Tel: 07766 396216
Scope:
This standard lays down the requirements for:
a) the design of signalling works applicable to the
infrastructure;
b) the design of signalling systems, whether line side
or train-borne;
c) the design of software and data used in
programmable signalling systems; and
b) safe interfaces between all parties and systems;

c) design details are prepared and presented
clearly, accurately, consistently and
unambiguously; and
Issue: 9
d) the tools, including software, used in design.

It applies from scheme conception through to acceptance
into service or, where applicable, to decommissioning and
disposal.
Whats New/ Whats Changed and Why:
Module B7, Clause 3.2.6 has been updated to capture single duty holder requirements from the withdrawn RGS
GK/RT0044 (1)
Module B3, Incorporate requirements from LI/320 into module
Affected documents:
Reference
Impact
NR/SIG/11201 ISSUE 8
Superseded
NR/L2/SIG/11201/B7 ISSUE 5
Superseded
NR/L2/SIG/11201/B3 ISSUE 5
Superseded
NR/BS/LI/320 ISSUE 1
Withdrawn
Briefing requirements: Where Technical briefing (T) is required, the specific Post title is indicated. These posts have specific responsibilities
within this standard and receive briefing as part of the Implementation Programme. For Awareness briefing (A) the Post title is not mandatory.
Please see http://ccms2.hiav.networkrail.co.uk/webtop/drl/objectId/09013b5b804504da for guidance.
Post
Team
Function
Head of Engineering/Signalling
Infrastructure Projects
Infrastructure Projects
Workforce Development Specilists
Training Delivery
Human Resources
Route Asset Managers ([Signalling]
Route
Network Operations
Briefing
(A-Awareness/
T-Technical)
--``,``,,`,,,`,`,```,,`,,`,`````-`-`,,`,,`,`,,`---
*NOTE: Contractors are responsible for arranging and undertaking their own Technical and Awareness Briefings in accordance with their own processes and procedure



Signalling Design Hand Book

Uploaded by

Copyright:

Available Formats

Signalling Design Hand Book

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Signalling Design Hand Book

Uploaded by

Copyright:

Available Formats

What are the different classifications of requirements mentioned in the document?

What are the different classifications of requirements mentioned in the document?

What are the responsibilities associated with red requirements?

What are the responsibilities associated with red requirements?

Network Rail Standards

Copyright Network Rail

Licensee=Kier Professional Services Ltd/1121225001, User=Anchi, Mallikarjuna

Information for users

Copyright Network Rail

Licensee=Kier Professional Services Ltd/1121225001, User=Anchi, Mallikarjuna

Red requirements shall always be complied with and achieved.

Red requirements are monitored for compliance.

Corrective actions shall be enforced if variations are discovered through

Amber requirements Controlled variations, approved risk analysis and

Amber requirements shall be complied with unless variation has been

Amber requirements are monitored for compliance.

Variations may be permitted. Variations are approved by the Standard Owner or

Corrective actions shall be enforced if non-approved variations are discovered

Guidance is based on good practice. Guidance represents supporting information

is not mandatory and is not monitored for compliance.

Alternative solutions may be used. Alternative solutions do not need to be

Decisions made by a competent person to use alternative solutions should be

Copyright Network Rail

Name-change & Modularisation of handbook and

Amended references due to withdrawal of

Module X21 reissued

Amendment to the process for managing and

Changes to the X series of modules

Incorporation of signal duty holder requirements

Licensee=Kier Professional Services Ltd/1121225001, User=Anchi, Mallikarjuna

Copyright Network Rail

NR/L2/SIG/11201 - Index of signalling design handbook A Modules

Licensee=Kier Professional Services Ltd/1121225001, User=Anchi, Mallikarjuna

Signalling Design Handbook

Outline Project Specifications (OPS) for Signalling Schemes

Minimum Requirements for design details

Assessment of signalling Systems before Signalling Design Alterations

Design Specification Guidelines

Safety Hazards requiring retrospective work

Correlation of Signalling Records

Design Record and Production control

Operating Requirements Review

Source Record Updating

Arrangement and Presentation

Symbols for plans and sketches used in Signalling Applications

Signalling Design Control Tables

Conventions, General Notes, Dollar Notes and Signallers Route Lists

RRI Signal and aspect control tables

RRI point and ground frame control tables

Control tables for level crossings

Control tables for train warning and protection systems

Control Tables For Staff Protection Systems (TOWS)

Control Tables For Block Systems & Electro-mechanical

SSI Control Tables

SIMIS W Control Tables

Copyright Network Rail

MODULE NUMBER & TITLE

Symbols for Signalling Circuit Diagrams

Overlapping and Parallel Signalling Design