Ne L2 TRK 3100

Network Rail Standards
Supplementary Information
The following information is associated with Network Rail Standard:

NR/L2/TRK/3100 Issue 5
Additional Content Access

Click the links below to access non PDF related content associated with this
standard.
Word Documents
 NR/L2/TK/3100/SU001
 NR/L2/TK/3100/SU002
 NR/L2/TK/3100/SU005
 NR/L2/TK/3100/SU504
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
If you have any questions, or need assistance, please contact IHS Support
Information accessed via the links above is the property of the Copyright holder
IHS Additional Content Page
Copyright Network Rail

Provided by IHS Markit under license with Network Rail Licensee=ABB Lilmited - Power Systems Rail/1121223005, User=Whitfield, Asa
No reproduction or networking permitted without license from IHS Not for Resale, 01/14/2021 13:41:39 MST
Network Rail Standards
Module information
Information for users
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 facility 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
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Compliance date: 01 June 2019
Level2
Manual
Topographic, engineering, land and measured

building surveying - Strategy and general
Approvals
~ont•~~~~
Chris Preston,
Technical Lead
Gareth Evans,
Standard and Control Document Owner
Approved for publication by:
~ ... .... ...... .. ....·~

.. .......,.. :>i...-:::--:-:
_ _..... ~~.... ..... ....... .. .. .. ... .... ...... ... ... .. ... ...•
John Winn ifrith,

Standards and Controls Management Team
This document is the property of Network Rail. It shall not be reproduced in whole or part nor disclosed to a third
party without the written permission of Network Rail.
© Copyright 2019 Network Rail.
Uncontrolled copy once printed from its electronic source.

Published and Issued by Network Rail, 2nd Floor, One Eversholt Street, London, NW1 2DN.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Compliance date: 01June 2019
User information
This Network Rail document contains colour-coding according to the following
Red–Amber–Green classification.
Red requirements – no variations permitted

• Red requirements are to be complied with and achieved at all times.
• Red requirements are presented in a red box.
• Red requirements are monitored for compliance.
• Non-compliances will be investigated and corrective actions enforced.
Amber requirements – variations permitted subject to approved risk analysis

and mitigation
• Amber requirements are to be complied with unless an approved variation is in
place.
• Amber requirements are presented with an amber sidebar.
• Amber requirements are monitored for compliance.
• Variations can only be approved through the national variations process.
• Non-approved variations will be investigated and corrective actions enforced.
Green guidance – to be used unless alternative solutions are followed
• Guidance should be followed unless an alternative solution produces a better
result.
• Guidance is presented with a dotted green sidebar.
• Guidance is not monitored for compliance.
• Alternative solutions should be documented to demonstrate effective control.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 2 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Compliance
This Network Rail standard/control document is mandatory and shall be complied
with by Network Rail Infrastructure Limited and its contractors if applicable from 01
June 2019.
Where it is considered not reasonably practicable1 to comply with the requirements in
this standard/control document, permission to comply with a specified alternative
should be sought in accordance with the Network Rail standards and controls
process, or with the Railway Group Standards Code if applicable.
If this standard/control document contains requirements that are designed to
demonstrate compliance with legislation they shall be complied with irrespective of a
project’s Governance for Railway Investment Projects (GRIP) stage. In all other
circumstances, projects that have formally completed GRIP Stage 3 (Option
Selection) may continue to comply with any relevant Network Rail standards/control
documents that were current when GRIP Stage 3 was completed.
NOTE 1: Legislation includes Technical Specifications for Interoperability (TSIs).
NOTE 2: The relationship of this standard/control document with legislation and/or
external standards is described in the purpose of this standard.
Disclaimer
In issuing this standard/control document for its stated purpose, Network Rail
Infrastructure Limited makes no warranties, expressed or implied, that compliance
with all or any standards/control documents it issues is sufficient on its own to
provide safety or compliance with legislation. Users are reminded of their own duties
under legislation.
Compliance with a Network Rail standard/control document does not, of itself, confer
immunity from legal obligations.
Where Network Rail Infrastructure Limited has granted permission to copy extracts
from Network Rail standards or control documents, Network Rail Infrastructure
Limited accepts no responsibility for, nor any liability in connection with, the use of
such extracts, or any claims arising there from.
This disclaimer applies to all forms of media in which extracts from Network Rail
standards and control documents might be reproduced.
Supply
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Copies of standards/control documents are available electronically, within Network

Rail’s organisation. Hard copies of this document might be available to Network Rail
people on request to the relevant controlled publication distributor. Other
organisations can obtain copies of this standard/control document from an approved
distributor.
1 This can include gross proportionate project costs with the agreement of the Network Rail Assurance
Panel (NRAP).
Page 3 of 76
OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Issue record
Issue Date Comments
1 September 2010
2 June 2017
3 September 2017 Minor errors in Issue 2 updated
4 December 2017 Cover sheet updated. Table 1 updated with

NR/L3/TRK/3104 republished as
NR/L2/TRK/3100/MOD04
5 March 2019 Table 1 updated with NR/L3/TRK/3105

republished as NR/L2/TRK/3100/MOD05
Reference documentation
NR/L1/INI/CP1010 Policy on working safely in the vicinity of buried

services
NR/L2/INI/CP1030 Working safely in the vicinity of buried services
NR/L2/INI/EDT/CP0091 Specification for Computer Aided Design
NR/L3/MTC/PL0094 Planning and documenting the Safe System Of

Work Arrangements
NR/L2/INI/02009 Engineering Management for Projects
NR/L2/ELP/21088 General Maintenance Parameters for Overhead

Line Electrification Equipment
NR/L2/TRK/2102 Design and Construction of Track
Benchmarks to GNSS heighting RICS (Royal Institution of Chartered Surveyors)

– Virtually level. Guidance note.
OSGB36. A guide to Co-ordinate systems. Produced by
the OS.
BS 1192:2007 Collaborative production of architectural,
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 4 of 76
OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
engineering and construction information– Code

of practice
PAS 1192-2:2013, Specification for information management for

the capital/delivery phase of construction
projects using building information modelling. It
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
specifies requirements for achieving building
information modelling (BIM) Level 2
PAS 1192-3:2014 Specification for information management for

the operational phase of assets using building
information modelling. It specifies the
requirements for information management to
achieve building information modelling (BIM)
Level 2 in relation to the operation and
maintenance of assets (buildings and
infrastructure).
PAS 1192-5:2015 Collaborative production of information. Fulfilling

employer’s information exchange requirements
using COBie. Code of practice. This British
Standard defines a methodology for the transfer
between parties of structured information
relating to Facilities, including buildings and
infrastructure. It defines expectations for the
design and construction project phases prior to
handover and acquisition and the subsequent
in-use phase.
PAS 1192-5:2015 Specification for security-minded building

information modelling, digital built environments
and smart asset management
Survey4BIM, Digital plan of works (DPOW)
Guidelines for the use of GNSS in land surveying and mapping. (RICS guidance
note). 2nd edition (GN 11/2010).
Guidance notes for GNSS network RTK surveying in Great Britain (Issue 4, May
2015 ©TSA)
Page 5 of 76
OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Contents
1 Purpose .................................................................................................................. 9
2 Scope ...................................................................................................................... 9
3 List of Modules .................................................................................................... 10
Table 1 – NR/L2/TRK/3100 modules ........................................................................ 10
4 Definitions ............................................................................................................ 10
5 Roles and responsibilities .................................................................................. 14
6 Planning ............................................................................................................... 15
6.1 Project Survey Strategy (PSS) ........................................................................... 15
Figure 1 – Project Survey strategy ........................................................................... 15
6.2 Planning for GRIP 2 to GRIP 8 stages ............................................................... 16
6.3 Data Users.......................................................................................................... 17
6.4 Survey data/information management ................................................................ 17
7 Survey risk management .................................................................................... 18
Table 2 – Example of simple risk register ................................................................. 19
Table 3 – Example of risk management table........................................................... 20
8 Site access planning ........................................................................................... 21
9 Accuracy, GRIP and survey techniques ............................................................ 21
Table 4 – Survey accuracy bands and survey techniques ........................................ 22
Table 5 – Discipline accuracy bands ........................................................................ 23
Table 6 – Survey purpose, techniques and GRIP stages 2, 3, 4, 5 & 7 .................... 26
Table 7 – Survey purpose, techniques and GRIP stage 3, 4, 5 & 6.......................... 27
Table 8 – Survey purpose, techniques and GRIP stages 5, 6 and 7 ........................ 28
10 Survey grids ....................................................................................................... 29
10.1 Choice of survey grids ...................................................................................... 29
Table 9 – Survey Grid choices.................................................................................. 29
10.2 WGS84 and ETRS89........................................................................................ 30
10.2.1 General .......................................................................................................... 30
10.2.2 OSGB36 ........................................................................................................ 30
Figure 2 – Spherical earth meets flat paper .............................................................. 31
10.2.3 Absolute project grid (APG) ........................................................................... 31
10.2.4 Use of pre-existing survey grid ...................................................................... 33
10.2.5 Local project grid (LPG) ................................................................................. 33
Table 10 – Local scale factor in terms of National Grid Eastings.............................. 35
10.2.6 Level datum ................................................................................................... 36
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 6 of 76
OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
10.2.7 Accuracy and adjustment of horizontal and vertical PGMs ............................ 37

10.2.8 Longitudinal metreage ................................................................................... 37
Figure 3 – Zero mileage datum at York station ......................................................... 38
10.3 Permanent ground markers (PGMs) ................................................................. 39
10.3.1 Location and design of permanent ground markers ...................................... 39
11 GNSS surveys .................................................................................................... 40
12 Surveying outputs ............................................................................................. 41
12.1 Survey report .................................................................................................... 41
12.2 Survey PGM network ........................................................................................ 41
12.2.1 Schedule of permanent survey control stations ............................................. 42
12.2.2 Horizontal and Vertical control network diagrams .......................................... 42
Figure 4 – GNSS example ........................................................................................ 43
Figure 5 – Conventional traversing example ............................................................ 43
12.3 Survey BIM/CAD/GIS Deliverables ................................................................... 44
12.4 Data preparation ............................................................................................... 44
13 Survey data management and quality assurance ........................................... 45
13.1 General ............................................................................................................. 45
13.2 Survey shelf-life, Data maintenance and Survey requirements strategy........... 45
Table 11 – Examples of data types .......................................................................... 47
13.3 Survey QA verification and validation ............................................................... 47
13.4 Survey site verification ...................................................................................... 48
13.4.1 PGM verification ............................................................................................ 48
Table 12 – PGM verification ..................................................................................... 48
13.4.2 Detail survey verification ................................................................................ 48
Figure 6 – Six dimensions for bridge abutments....................................................... 49
13.5 Survey validation .............................................................................................. 49
14 Setting out – Survey Grid and PGMs ............................................................... 50
15 Site photographs ............................................................................................... 51
Appendix A - Removed .......................................................................................... 52
Appendix B - Permanent ground marker types ................................................... 53
Figure B-1 – Permanent Ground Marker Type 1 (for dense, very stable paved
surfaces) ................................................................................................................. 53
Figure B-2 – Permanent Ground Marker Type 2 (for non-agricultural sites and
unpaved surfaces) .................................................................................................... 54
Figure B-3 – Concrete PGM ..................................................................................... 55
Figure B-4 – Example of Concrete PGM .................................................................. 55
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 7 of 76
OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure B-5 – Example of Type 4 PGM in OLE mast base ........................................ 56

Figure B-6 – Example of nail and marker arrangement for Type 4 ........................... 56
Figure B-7 – Type 5 example of TMG/spigot/stud .................................................... 56
Figure B-8 – Leica GPH1 prism holder on Type 5 .................................................... 57
Figure B-9 – Dimensions for Type 5 spigot arrangement ......................................... 58
Figure B-10 – “Forced centring”Type 6 survey pillar ................................................. 59
Figure B-11 – Type 6 example of “Forced centring” survey pillar ............................. 59
Figure B-12 – Type 6 alternative design of “Forced centring” survey pillar ............... 60
Figure B-13 – Type 6 head of “Forced centring” survey pillar ................................... 60
Figure B-14 – Type 6 example of “Forced centring” survey pillar ............................. 61
Figure B-15 – Type 6 pillar construction diagram ..................................................... 61
Figure B-16 – Type 7 14TK400 Instrument Wall clamp (Code: 3604070) ................ 62
Figure B-17 – Type 7 demountable Table Mounting System (Code: 0301061) ........ 62
Figure B-18 – Type 8 – BRE Levelling bolts ............................................................. 62
Figure B-19 – Type 9 Leica 360◦ mini prism for permanent installation .................... 63
Appendix C - PGM data examples ......................................................................... 64
Figure C-1 – Example of completed PGM Witness Diagram .................................... 64
Figure C-2 – Example of PGM schedule .................................................................. 65
Figure C-3 – PGM creation method .......................................................................... 65
Appendix D - Snakegrid routes ............................................................................. 66
Figure D-1 – Snakegrid routes.................................................................................. 66
Appendix E - Survey report templates .................................................................. 67
Table E-1 – RILA 360 accuracy ................................................................................ 70
Appendix F - Data derived from terrestrial laser scanning ................................. 75
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 8 of 76
OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
1 Purpose
The standard sets out requirements for the project manager and engineer to specify
topographic survey work, by identifying key stages to deliver good quality work for
current and future needs. This lowers the risks associated with poor survey work for
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
projects. “Survey once and use many times” also provides better value for the money
spent.
2 Scope
The standard specifies all surveying activities for which a co-ordinated (in relation to
a survey grid) Topographic, Engineering, Land, or Measured Building survey is
required. This standard is applicable to individual project scopes during the life-cycle
of a renewal or project.
It specifically excludes ground investigation, geotechnical, building condition,
dilapidation surveys and surveys associated with Network Rail owned and operated
measurement trains.
It is for the use of Project Managers, Designated Project Engineers (DPE) or project
teams, in consultation with a geospatial engineer (Client’s Survey Manager).
The standard also explains how an appropriate topographic survey forms the basis
of BIM by reference to the Survey4BIM Digital plan of works and the various parts of
PAS 1192 Parts 2 to 5.
This is the main document that provides a strategy and general introduction,
establishing some basic principles to be applied across all disciplines.
This standard is intended to be used with the modules associated with the discipline
and related to the type of survey required.
NOTE: For example, where a track survey and then a design for S&C renewal is needed, this
standard and Module 1 would be consulted to understand what is required. A project survey strategy
would be defined as specified in this standard and the detailed specification would be derived from
Module 1.
Page 9 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
3 List of Modules
Module Number Title Issue Date
01 Track surveying (formerly 2 Sept 2017

NR/L3/TRK/3101) including track, platform
extensions, level crossings, underground
services, gauging, implementation of S&C,
geospatial monitoring and slab track
installation
02 Civils and Buildings - Not written
03 Survey and mapping techniques guidance 2 Sept 2017

note (formerly NR/GN/TRK/3103)
04 Asset data extraction & Topographic 1 Dec 2017

survey (formerly NR/L3/TRK/3104)
05 Topographic, engineering, land and 1 Mar 2019

measured building surveying - Overhead
Line Electrification (formerly
NR/L3/TRK/3105)
Table 1 – NR/L2/TRK/3100 modules
4 Definitions
For the purposes of this standard, the terms and definitions in this clause apply.
Absolute accuracy
The measure to which an object or point conforms to its true location within a chosen
coordinate system.
BIM
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Building information modelling

A process used from cradle to grave to design, create, manage and dispose of an
asset. It relies on collaboration between all organisations involved with the asset
during its lifetime.
BEP
BIM execution plan
The means by which an organisation will provide data to comply with the client’s EIR.
Page 10 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
CDE
Common data environment
This is used for BIM to provide a “single definition of the truth” that enables all
collaborative project participants to base their work on the same base information.
CORS
Continuously operating reference system
This may be used to define positions on the ground utilising GNSS receivers linking
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
to OS Net by mobile phone through one of Ordnance Survey’s partners such as
“Leica Smart Net”, “Trimble VRS Now” or “Topcon TopNet Live”. This also enables
Real time kinematic (Network RTK) surveying.
Digital Railway
A programme set up to safeguard the future of the railway to increase capacity,
improve performance, provide a safer working environment, reduce carbon
emissions, all at a lower running cost. It includes the ORBIS (Offering Rail Better
Information Sources) programme, Network Telecom and Asset Information Services.
DSM/DEM
Digital surface or elevation model
A computer generated surface representing the surface of the ground from which
contours and volumes may be derived or digital elevation model encompassing the
heights of vegetation, other natural and man-made features.
EIR
Employer’s information requirements
A document produced by the client explaining the manner in which the information
required for a BIM model is to be provided. It also explains the way in which the data
will be managed and by whom.
ETRF89
European Terrestrial Reference Framework
Physical realisation of the ETRS fixed to the Eurasian Plate as defined in 1989, the
framework upon which GNSS in Europe works.
ETRS89
European Terrestrial Reference System defining parameters of the origin, scale,
orientation and adopted ellipsoid.
GNSS
Global Navigation Satellites Systems including GPS, Glonass & Galileo.
GRIP
Guide to Railway investment Projects detailing the stages all projects must pass
through.
Page 11 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Level Datum
The level obtained directly from GNSS in ETRS89 and converted to OS Newlyn
datum utilising a transformation available directly from OS website.
NOTE 1: To achieve compatibility between adjacent permanent ground markers (PGMs) they should
be orthometrically levelled.
NOTE 2: OS Benchmarks are no longer maintained.
LiDAR
Light Detection and Ranging
Remote sensing technology that measures properties of scattered light to find range
and/or other information of a distant target using laser pulses. The range to an object
is determined by measuring the time delay between transmission of a pulse and
detection of the reflected signal.
OSGB36/OSNG
The Ordnance Survey grid
NOTE 3: A direct link to it can be obtained by using GNSS equipment with “OS Net” and Ordnance
Survey Active Network GNSS locations.
Point Cloud
A series of individual co-ordinated points in X, Y and Z that can be collected from
aerial sensors, for example LiDAR, or from the ground using terrestrial laser
scanners or ground based LiDAR systems. Millions of points are provided from such
sensors (each technique has different accuracies) that in their base form are simply
a series of X, Y and Z points with minimal identification attached. Data needs to be
abstracted using automation and manual intervention to provide further meaningful
information.
Primary PGMs
First Order survey monuments (permanent ground markers) providing the primary
planimetric and vertical control (benchmarks) for the survey
Relative accuracy
It is the comparison of a calculated measurement between surveyed points and the
true measure. On making this comparison it is essential to know if the coordinate
system itself is based on true distances or is projected (scaled). The relative
accuracy of the calculated measurement depends on the combination of the
absolute accuracy of the points and the observational method of capture.
Reference chainage/metreage
A longitudinal reference system that is used by all disciplines as a reference system.
It will have a well defined datum and is usually now measured in kilometres and
metres not miles and chains/yards. The datum will be based on a long lasting feature
such as tunnel portal or bridge abutment.
Page 12 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
RINM
Rail infrastructure network model
A link and node network enabling other data sets to be linked to it and thereby
displayed against others in a GIS.
Secondary PGMs
Second Order permanent ground markers between the primary PGMs.
Snakegrid
A specialised map projection, an absolute project grid that is bespoke for a defined
long and thin project area. It differs from the Ordnance Survey grid in that it does not
need to use a scale factor.
Survey Grid
Geodetic framework upon which the survey is based.
Tertiary control
Third order ground markers, usually trackside, between the secondary control
Terrestrial Laser Scanning

TLS
Survey technique involving the use of a survey grade laser scanning instrument to
collect tens of thousands of measurement points per second and millions of points
per setup by rotation through a 360 degree field of view.
NOTE 4: The instrument can be mounted in a fixed position (static) or moving position (kinematic)
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
such as on a track measurement device.
Track measuring device

TMD
Device formerly known as a track trolley, such as Amberg GRP FX series, Trimble
GEDO range and other manufacturers’ track geospatial measurement devices.
TMG/spigot/stud Track machine guidance points

Survey marker installed to enable a survey prism to be attached directly.
NOTE 5: These might replace the third order PGMs in some areas. They are usually installed in OLE
masts or other fixed vertical structures.
Tolerance
The acceptable difference between a design and what is set-out or built.
Total station
Combined electronic theodolite and EDM measuring equipment that also includes a
computer for computations and measured data storage.
Trig heighting
A technique to obtain the height of a location by measuring the VA (vertical angle)
and SDi (Slope distance) that is computed to get the horizontal distance to the point.
Page 13 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
NOTE 6: To obtain best results this should be done from a minimum of two independent instrument
set ups.
Scan point cloud publishing software

An example of such software is Leica Truview publishing and viewing software
providing an instrument position view of scan data with a reflectivity light image or
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Red, Green, Blue image superimposed on the co-ordinated points.
UAS/Drone
Unmanned aerial system that may be used for inspection, vertical and oblique
imagery and LiDAR data capture. This technology is constantly evolving with other
sensors becoming available.
5 Roles and responsibilities

Full details of project responsibilities for posts underlined are given in
NR/L2/INI/2009. Brief summaries are included here.
Client’s Survey Manager (CSM)

Network Rail project representative acting as Client Survey Manager. The CSM is
required to have an up to date understanding of surveying including the range of
datasets available and types that may be collected that are needed for the project
purpose.
In addition, the CSM is involved in the strategic direction of the project and works
closely with the Project information (BIM).
Contractor’s Engineering Manager (CEM)

Person within every design and/or construction organisation contracted to Network
Rail, (or to a party other than Network Rail where agreed with Network Rail) with
overall accountability for all engineering activities applicable to that specific Contract
including those subcontracted out.
Contractors Responsible Engineer (CRE)

Person within a design and/or construction organisation contracted to Network Rail,
with accountability for the day-to-day management and co-ordination of the technical
and engineering activities within a specific engineering discipline.
Designated Project Engineer (DPE)

Person appointed by Network Rail accountable for the coordination and integration
of technical and engineering aspects of a specific project.
The DPE may also act as the Project Engineer (PE) for a single engineering
discipline. The DPE may delegate responsibilities defined by this standard but
remains accountable for execution on each project.
Project Engineer (PE)

Person appointed by Network Rail accountable to the DPE for day-to-day
management and co-ordination of technical and engineering aspects of a project for
a single engineering discipline.
Page 14 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Project Information Manager

A Network Rail representative who is responsible for setting up and maintaining the
Common data environment associated with BIM and, managing access for project
collaborators.
6 Planning
6.1 Project Survey Strategy (PSS)

A Project Survey strategy shall be created by the Project Manager with assistance
from the CSM prior to the commencement of work.
NOTE: This is to achieve the integration of all survey and asset information data.
Figure 1 – Project Survey strategy

The items given in Figure 1 shall be included in the PSS.
The PSS shall be updated as the project moves between GRIP stages.
NOTE: This is because it will evolve during the course of the project.
The PSS shall be split into the following three sections:
a) planning for GRIP 2 to GRIP 8 stages;
b) Common Data Environment users; and
c) survey data management.
Page 15 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
6.2 Planning for GRIP 2 to GRIP 8 stages

The planning for Grip 2 to GRIP 8 stages shall include:
a) the Employer’s information requirement and BIM Strategy in line with BS1192,
part 2, with a whole life cycle view of the project being considered
encompassing each GRIP stage up to 8, including hand back to maintenance
and data provision to Asset information at project close down;
b) definition of survey budget associated with the associated risks for each GRIP
phase;
c) sources of any existing survey data for the area in question;
NOTE 1: For example, in the initial planning stage and early GRIP stages the use of aerial
survey data via the Geo-RINM viewer (GRV) might provide sufficient data or assist in the
identification of any addition survey requirement.
d) survey procurement plan and how this fits within the overall project
procurement strategy;
e) definition of the form of tender;
f) the structure of the Tender review team;
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
g) definition of the commercial/technical scoring spilt with risks acknowledged in

writing by a Project Manager when commercially favourable bids with limited
technical abilities are favoured;
h) the scope and extent of the project;
i) the definition of the survey grid(s) and for what purpose;
j) chainage/metreage to be used by ALL disciplines;
k) identification of the named post to plan and book track access; and
NOTE 2: This should be addressed at the earliest opportunity. The last opportunity is T-12
weeks. See clause 7.
l) how the sourcing of underground services records for the project area from
Network records team (NRG) will be managed, as specified in
NR/L2/INI/CP1030.
NOTE 3: An aspiration is that the underground services records will be made available via the
Geo-RINM viewer in a format suitable for use in CAD software and for loading into the CDE for
BIM.
Page 16 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
6.3 Data Users

The PSS and the EIR for BIM shall define:
a) the main disciplines involved and any additional disciplines plus their data
needs;
b) what the designers for the project shall receive;
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
NOTE 1: e.g. will the design for track be done by Hallade or 3D methods?
c) what the construction contractor will be provided with and the methodology we
want them to use to enable construction;
d) the data required by the maintainer for hand-over/hand-back at the end of the
project to enable the maintenance of the infrastructure; and
NOTE 2: This may include any future requirement that is yet to be defined.
e) the data required by Asset Information (AIS) for hand-back at the end of the
project to enable update or improvement of the asset information data.
NOTE 3: A template for an EIR for completion is available from an NR IP representative
6.4 Survey data/information management

NOTE 1: The survey is needed for all aspects of a project in a consistent fashion (i.e. property,
engineering, design, maintenance, monitoring, inspection, set-out installation and hand-back.
NOTE 2: BIM process (PAS 1192) sets out the best practice for information management. These
principles should be followed even if not mandated on particular projects.
The project Information Manager shall determine rules for survey information
management and complete the EIR.
This shall include:
a) definition of the Common Data Environment – system for robust storage,
sharing and management of information between all participants of project or
maintenance;
b) determination of formats and interoperability rules to enable instant availability
of survey information through the Common Data Environment; and
c) how survey information/data shall be prepared and delivered to comply with
the EIR.
Page 17 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Survey data/information management shall include definition of the role of CSM. The
CSM shall:
d) undertake assurance checks to verify and validate (accept) the pre-existing
and new survey data. Critical items requiring assurance shall be identified in
the project risk register. The degree of checks to be undertaken shall be
associated with the project risk register created by the Project Manager or
Designated Project Engineer and updated throughout the course of the
project;
e) manage the interfaces between survey suppliers and audit the survey
contractors;
f) maintain and update the survey data on an ongoing basis during the project
life cycle, including the hand back period;
g) manage the survey grid as specified in clause 10; and
h) manage the longitudinal chainage/metreage system as specified in 10.2.8.
NOTE 3: For example, when track alignment design is being considered the start point of the design
metreage is required to be defined or, for an OLE survey, a longitudinal metreage may be defined
relative to the track ELR and chainage system. For signalling such a metreage system may
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
commence at the centre-line of a signal box.
7 Survey risk management

A survey risk register shall be set up by the Project Manager or designated Project
Engineer with assistance from the CSM.
NOTE 1: The Project Manager or designated Project Engineer wants a survey that they have
confidence in and, if obvious errors are found, they will lose that. Gross errors can cause
consequential losses on other parts of the project, such as delay and additional costs.
NOTE 2: An example of a simple risk register is given as Table 2. It is not exhaustive and other risks
may be identified.
Page 18 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Cause of risk Consequence Owner Mitigation

Poor NR client Incorrect data Project manager/ Use CSM with up to date survey
understanding of being collated or Engineering design data knowledge
survey data procured causing manager
delay and
additional costs
Contract
participants change
between design Delay in Contracts and Validate site survey by desk top
(GRIP5) and programme procurement means
construction
(GRIP6)
Change
Research interfacing projects,
Validity/verification management.
Project manager recurring checks for changes,
of outputs Delays and cost
data management
overrun
Lack of available Delay in
Project manager Negotiation with other parties
resource programme
Delay in
Competence and programme due to Project manager/ CSM to advise on appropriate
capability of survey poor deliverables Contracts and companies providing full range of
company from multiple procurement services, not only from “Link-up”
suppliers
Delay in Plan 6 months or more ahead
Site Access Project manager
programme and book possessions
Use standard documentation to
Engineering design
Surveyor revisit, outlaw inappropriate local grid
Poor specification manager/CSM/Spon
Delay solutions and plan for access to
sor
allow pre-survey visit
CSM to advise appropriate
Multidiscipline Engineering design
Revisit, Delays and modern survey techniques that
scope poorly manager/CSM/Spon
cost overrun collect all data needed in one
defined sor
visit
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Project survey strategy

Project manager/
developed to enable Survey to
Survey planning Unforeseen costs Engineering design
be part of “whole life project
manager/CSM
costs”.
Permanent ground Project manager/ Buried services searches carried
marker (PGM) Delay Engineering design out 6 months in advance for site
installations manager/CSM (12 week min. needed)
External company procedures
Gross Errors Revisit, Delay Survey company
and NR checking process
Possible resurvey Project manager/
Survey data Project survey strategy defines
when already Engineering design
management how this will be done
completed manager/CSM
Project manager/ Provision shall be made for
Survey PGMs are Delay in
Engineering design maintenance of PGMs between
destroyed programme
manager/CSM all project stages
Table 2 – Example of simple risk register
Page 19 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Identified risk and likelihood should be compared against impact to derive a risk
rating.
NOTE 3: An example of identified risk and likelihood is given as Table 3.
Likelihood
Rating Before/After
Risk Impact Control measure control measure
control measure
Incompetence 4 5 CSM to advise on appropriate companies not 20

of survey only from “Link-up” or successor
1 5 5
company
Site Access 4 5 Plan 6 months or more ahead and book 20

possessions
3 5 15
Survey 4 4 Project survey strategy developed to enable 16

planning Survey to be part of “whole life project costs”.
1 2 2
Poor 4 5 Use standard documentation defining survey 20

specification grid and plan for access to allow pre-survey
2 3 6
visit
Multidiscipline 4 4 CSM to advise appropriate modern survey 16

scope poorly techniques that collect all data needed in one
3 3 9
defined visit
Survey 4 4 Project survey strategy developed to enable 16

planning Survey to be part of “whole life project costs”.
1 2 2
Weather 3 4 Contract to define if day rate or fixed price 12

service. Plan work when bad weather least
2 4 8
likely.
Permanent 5 4 Buried services searches carried out six- 20

ground month in advance for site (12 week minimum
2 2 4
marker (PGM) turn round needed).
installations
CAT used on site
Gross Errors 3 5 Company procedures and Network Rail 15

checking process
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
1 2 3
Survey data 4 4 Project survey strategy and EIR defines how 16

management this will be done
2 2 4
KEY
1 is low, 5 is high.
Table 3 – Example of risk management table
Page 20 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
NOTE 4: Application of control measures brings risks down to manageable level. Further control
measures can be needed to address the risk. Such a concept allows focusing on critical aspects of
survey planning.
8 Site access planning

At the earliest stage, when it is established that a ground survey, train borne survey
or aerial survey (UAS/Drone) will be required, the Project Manager shall define the
site access requirements as specified in NR/L3/MTC/PL0094.
NOTE: Access to the track to undertake permanent way surveys is strictly controlled and can have a
lead time of six months to enable possessions in a green zone to be booked and arranged. It might be
possible to “piggy-back” another possession, arranged for a different purpose, but careful planning
and consideration of the other planned activities is needed so that these do not prevent the survey
taking place (e.g. storage of materials trains awaiting access to track renewals site) at the location
needed. In some instances, red zone working might be accepted but this is unlikely.
9 Accuracy, GRIP and survey techniques

NOTE 1: This is a complex subject and only the briefest of explanations is given here.
NOTE 2: Accuracy is defined statistically as the root mean square error (rmse) or maximum
tolerance. The rmse is equivalent to 68% tolerance and 90% tolerance is 1.65 times the rmse when a
representative sample of points is tested. Thus, an rmse of 5 mm (Band 1 Accuracy below) indicates
that when a representative sample of 100 points is tested not less than 68 will be better than 5 mm
(68% probability) and not less than 90 points will be correct to better than 8 mm (90% probability).
Any errors exceeding three times the rmse, in this case 15 mm may be regarded as mistakes.
NOTE 3: By way of further explanation on the application of accuracy, surveying accuracy is a
complex relationship between a number of different potential sources of random errors comprising the
“Survey system”. Each part of the system might have an accuracy or “standard error” associated with
it and as combination the following formula applies where suffix m is resultant standard error and
suffixes 1 to 3 are individual errors:
m= √(12 + 22 + 32) (1)
EXAMPLE
This example shows the effect of combining survey tolerance and setting out
tolerance (construction tolerance).
Consider the scenario when a point is to be set-out or marked out on the ground
from a PGM.
PGM installation accuracy of 5 mm in relation to the survey grid.
Accuracy of setting up over PGM or centring error 1.5 mm
Total station accuracy of 1” Angular accuracy and 3 mm 2 part per million of
distance.
Target accuracy 3 mm
Point to be set out is 50 m away.
Therefore, using equation (1), the final accuracy of point set-out is 6 mm in relation
to the PGM or in relation to another point set-out from same location 12 mm.
Band number shall always be referred to when accuracy is discussed.
Page 21 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Absolute accuracy Relative accuracy

of points mm (68% between points (see
probab.) notes) mm (68% probab.)
Correlated Uncorrelated
Band Horizontal Vertical H V H V Survey technique
Band Direct measurement of steelwork with
N/A N/A 3 3 disto/steel tape
0
1” Total station topographical survey.
Band
5 5 4 4 7 7 UAS/Drone (See NOTE 4)
1
Terrestrial laser scanning (see NOTE 5)
Band RILA System 3 see NOTE 3
8 12 5 5
1A
Band
10 10 7 7 14 14
2
Band RILA-Track only
10 15 7 11
2A
Band GNSS Survey accuracy receivers (tripod
10 20 7 14 14 28 mounted)
2B
Band GNSS Survey accuracy receivers (pole
15 25 11 18 21 35 mounted).
2C
Band LiDAR augmented with RILA
25 20 18 14 35 28
2D
Band UAS/Drone or conventional Aerial imagery
25 25 18 18 35 35 and mapping - at low flying height
3
Band Aerial imagery mapping & LiDAR
50 30 36 28 71 57
3A Vehicle mounted LiDAR
Band GNSS hand held receivers –GIS data
100 50 71 36 141 71 collection
4
NOTE 1: Survey accuracy is often based upon objective judgement rather than qualitative
measurement as all possible scenarios and combinations cannot be considered.
NOTE 2: Relative accuracy needs to assess if all the measurements of the system are uncorrelated
that is completely independently measured or not. In many cases they are correlated.
NOTE 3: RILA System 3 measurements are always correlated thereby improving the relative
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
accuracy. When modelling objects (using multiple points from the point cloud) the relative accuracy
between objects is +/-5mm in X, Y & Z.
NOTE 4: UAS or Drone technology using low flying, vertical and oblique imagery with ground PGMs
only accepted for rails. Platform gauging not yet accepted but future tests might change this. Only
maximum 500m range from pilot. Other UAS or Drone techniques typically provide Band 3 accuracy.
NOTE 5: Train borne and terrestrial laser scanning measurements are only accepted for rails and
platform gauging under exceptional circumstances but future tests might change this.
Table 4 – Survey accuracy bands and survey techniques
Page 22 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Discipline Type of work Accuracy Band
Platform surfacing 1
Coping 1
Tunnel walls 1
Steelwork 2
Foundation 2
Civil
Brickwork/blockwork 2
Earthworks 3
Troughing 3
Underground 3
services/Utilities
Plain line alignment 1 & 1A

S&C alignment 1 & 1A
Datum plates 1
Pway Within structure gauge 1
Drainage 2
Formation 3
Sand or bottom ballast 3
Steelwork 1
Wiring, incl. Height & 1A & 2 (See notes 6 and
OLE Staggers plus registration 10)
Foundations 2
Positioning (Longitudinal) 3
Ironwork 1
Signals Positioning 3
Sighting 4
Table 5 – Discipline accuracy bands

NOTE 6: Existing approved single measurement laser OLE height & stagger gauges will only achieve
a measurement tolerance of +/- 15mm (Band 2A). This is specified in NR/L2/ELP/21088. (Although
the laser module itself is capable, the gauge design and human error in measurement introduce
inaccuracies).
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 23 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
The Project Engineer or DPE shall verify that the survey accuracies as detailed in
Table 4 and Error! Reference source not found. are appropriate for their needs by
consultation with the CSM.
Band number shall always be referred to when accuracy is discussed.
NOTE 7: Where different accuracy surveying techniques have been used for various features within
a survey, Table 2 should be added to any drawing title box to reflect this and referred to in any
“metadata” associated with the survey model file.
NOTE 8: NR/L2/TRK/2102, Table A.1 specifies values in relation to variation from design.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
NOTE 9: Accuracy Band 1 at 5mm is worst case scenario between adjacent observed points but in
practice the relative accuracy between points 10m apart when measured with a properly adjusted and
calibrated total station would conform to the requirements specified in NR/L2/TRK/2102, Table A.1
NOTE 10: Construction and as-built accuracy requirements for OLE are given in
NR/L2/TRK/3100/MOD5, Table 3.
Table 6, Table 7 and Table 8 give Survey purpose, techniques and various GRIP
stages when they should be used.
Page 24 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Survey Absolute Relative Technique (s) GRIP PGM/Fixed point requirement Notes
purpose Accuracy Accuracy stage
Band Band
X, Y Z X, Y Z
E.1.1 Track 3A 3A 3A 3 Aerial imagery or 2 or PGMs off track needed to enable fix to Geo-RINM viewer data (GRV) from Aerial
feasibility A aerial LiDAR and early 3 survey grid survey may be used at no additional
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
study mapping extra cost.
Surveyors NOT trackside.
E.1.2 OLE design 2A 2D 2A 2 RILA-Track and 3 PGMs off track needed to enable fix to RILA-Track survey acts as additional
D aerial LiDAR survey grid for LiDAR PGMs to improve the height accuracy of
combined the LiDAR.
Suitable for Plain Line OLE assessment.
E.1.3 Track design 1A 1 1(see 1 RILA-System 3 3 None Relative accuracy at Band 1 (suitable for
gauge (see notes structure gauging except platforms).
clearance notes ) (surveyors NOT trackside).
assessment )
E.1. 4 Track design 1A 1 to 2 1 1 1” Total station 3 or 4 Full survey PGMs required in hierarchy Traditional approach to track surveying
topo survey with as defined in NR/L2/TRK/3100 Clauses but with points of every 5 to 10 m (as per
hand held detail 10.2.3 and 10.2.7 NR/L2/TRK/3100/MOD1).
pole Surveyors are trackside.
E.1.5 Track design 1 1 1 1 1” Total station 3, 4 or Full survey PGMs required in hierarchy Gives highest accuracy and points every
topo survey using 5 as defined in NR/L2/TRK/3100 Clauses 20mm possible.
single TMD. 10.2.3 and 10.2.7 Surveyors are trackside except where
See also Table 4 UAS/Drones used
NOTE 4
E.1.6 Track design 1 to 2 1 to 2 1 1 Survey using 3, 4 or Full survey PGMs as defined in Gives high accuracy and points every
single TMD with 5 NR/L2/TRK/3100 Clauses 10.2.3 and 20mm possible.
Inertial navigation 10.2.7 Surveyors are trackside.
unit (IMU)
E.1.7 Track design 1 1 1 1 Survey using two 3, 4 or Full survey PGMs as defined in Gives highest accuracy and points every
TMDs 5 NR/L2/TRK/3100 Clauses 10.2.3 and 20mm possible.
10.2.7 Surveyors are trackside.
Page 25 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Band Band
X, Y Z X, Y Z
E.1.8 Track design 1A 1A 1A 1 RILA System 3- 3, 4 or OS Active network PGMs and virtual RILA-Track only is suitable for plain line
plain line, A Linked to video for 5 reference system. track geometry. S&C areas need greater
S&C and S&C componentry PGMs or TMG/Fixed points needed 6 foot accuracy from RILA System 3 and
OLE Height later for installation Rail profiles from RILA-Track. Supports
and stagger some gauge analysis (see 1.3). Points at
every 67mm to 1m along route, at speed
of 75mph.
Surveyors NOT trackside.
E.1.9 Asset 4 4 4 4 RILA System 3 or 7 Survey linked to ETRS89/OSGB36 Surveyors NOT trackside.
information. Rail Vehicle
mounted 360 deg.
Laser scanner.
Table 6 – Survey purpose, techniques and GRIP stages 2, 3, 4, 5 & 7
Page 26 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Survey Absolute Relative Technique (s) GRIP PGM/Fixed point Notes

purpose Accuracy Accuracy stage requirement
Band Band
X, Y Z X, Y Z
E.2.1 Track 2 2 2 2 3” Total station and 6 Full survey PGMs required Formation design model required.
formation hand held prism in hierarchy as defined in Possible delays due to line of sight obstruction.
construction target or dozer NR/L2/TRK/3100 Clauses Method for cuttings or tunnels.
mounted prism 10.2.3 and 10.2.7 Surveyors trackside.
target UAS/Drones could be used for as-built assurance
where minimal obstructions
E.2.2 Track 2C 2C 2C 2 GNSS Survey 6 OS Active network PGMs Formation design model required.
formation C accuracy receivers and virtual reference No delays due to line of sight obstruction except where
construction –pole mounted or system. no view of sky in cuttings or tunnels.
dozer mounted No additional PGMs or Surveyors trackside.
TMG/Fixed points needed
E.2.3 Rail 1 1 1 1 1” Total station topo 6 Full survey PGMs required Gives highest accuracy and points every 20mm
installation survey using single in hierarchy as defined in possible.
TMD NR/L2/TRK/3100 Clauses Prior survey of “run-ins and outs” needed. Line of sight
10.2.3 and 10.2.7 obstruction issues.
Surveyors trackside.
E.2.4 Track design 1 to 2 1 1 1 RILA System 3 plus 3, 4 or 5 Temporary fixed points Allows validation of design from previous RILA-Track
and Rail to using single TMD only for linking RILA Track survey by single TMD Inertial navigation unit (IMU)
alignment 2 Inertial navigation alignment + RILA360 data utilising common fixed points prior to tamping and
plain line unit (IMU). with single TMD Inertial validation post tamping.
See also Table 4 navigation unit (IMU) Minimal surveyors trackside.
Note 4 alignment
E.2.5 Track design 1 to 2 1 1 1 Survey using single 3, 4 or 5 Full survey PGMs required Gives highest accuracy and points every 20mm
to TMD Inertial in hierarchy as defined in possible.
2 navigation unit NR/L2/TRK/3100 Clauses Surveyors trackside.
(IMU). See also 10.2.3 and 10.2.7
Table 4 Note 4
E.2.6 Rail 1 1 1 1 Survey using two 6 Full survey PGMs required Gives highest accuracy and points every 20mm
installation TMDs in hierarchy as defined in possible.
NR/L2/TRK/3100 Clauses Fewer delays due to line of sight obstruction.
10.2.3 and 10.2.7 Surveyors trackside.
Table 7 – Survey purpose, techniques and GRIP stage 3, 4, 5 & 6
Page 27 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Band Band
X, Y Z X, Y Z
E.3.1 Track 2A 2 2A 2A RILA-Track 5 OS Active network PGMs and High resolution of points at every
Maintenance A virtual reference system. 1m to 67mm at speed of 75mph.
Pre-Tamping No additional PGMs or Surveyors NOT trackside.
TMG/Fixed points needed
E.3.2 Pre-Tamping 1 1 1 1 1” Total station topo 5 Full survey PGMs required in Gives highest accuracy and points
survey using single TMD hierarchy as defined in every 20mm possible.
NR/L2/TRK/3100 Clauses 10.2.3 Surveyors trackside.
and 10.2.7
E.3.3 Pre-Tamping 1 1 1 1 Survey using two TMDs 5 Full survey PGMs required in Gives highest accuracy and points
hierarchy as above, if available, every 20mm possible but at 1 to
or use localised Co-ordinated 5m usual.
TMG/Fixed points. Surveyors trackside.
E.3.4 Post- 1 1 1 1 1” Total station topo 6 or 7 Full survey PGMs required in Gives highest accuracy and points
Tamping – survey using single TMD hierarchy as above Pre- every 20mm possible.
As-builts Tamping Surveyors trackside.
E.3.5 Track renewal 1 to 1 1 1 Survey using single TMD 3, 4 or 5 Full survey PGMs required in Gives high accuracy and points
or 2 to with Inertial navigation hierarchy as above Pre- every 20mm possible.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
enhancement 2 unit (IMU) Tamping Surveyors trackside.
design
E.3.6 Post- 1 1 1 1 Survey or using two 6 or 7 Full survey PGMs required in Gives highest accuracy and points
Tamping – TMDs hierarchy as defined in every 20mm possible but at 1 to
As-builts NR/L2/TRK/3100 Clauses 10.2.3 5m usual.
and 10.2.7 if available or use Surveyors trackside.
localised Co-ordinated
TMG/Fixed points.
E.3.7 Post- 2A 2 2A 2A RILA-Track 6 or 7 OS Active network PGMs and High resolution of points at every
Tamping – A virtual reference system. 1m to 67mm at speed of 75mph.
geometry As- No additional PGMs or Surveyors NOT trackside.
builts TMG/Fixed points needed See also E3.4.
Table 8 – Survey purpose, techniques and GRIP stages 5, 6 and 7
Page 28 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
10 Survey grids
10.1 Choice of survey grids

NOTE 1: A project grid is important as it enables the curved earth to be mathematically defined as a
plane. A number of variations may be appropriate. The best to use is dependent on the nature of the
project and what other pre-existing infrastructure it is required to interface with.
A project requiring a survey shall utilise one of the following types of survey grids
where applicable:
a) WGS84/ETRS89;
b) Ordnance Survey national grid (OSGB36);
c) bespoke design of Absolute project grid (APG);
d) a pre-existing survey grid (e.g. the London Survey grid (LSG)); or
e) local project grid (LPG).
The Project Manager or designated Project Engineer shall consult with the CSM to
define the appropriate survey grid and longitudinal chainage or metreage to be used.
NOTE 2: A description of these grids is shown in Table 9.
Grid When Comments
WGS84/ETRS89 (see 10.2.1) Establishment of new grid for an Based on GNSS observations
area giving Latitude and longitude
values
Ordnance Survey national grid Allows linking to existing OS Need to apply a Scale factor
(OSGB36) (see 10.2.2) mapping and National
framework.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Absolute project grid (APG) (see Bespoke grid for specified Example is “Snakegrid” for a
10.2.3) purpose long thin project like a railway
with high accuracy needs and
length greater than 10 Km.
Existing survey grid (see 10.2.4) New project abuts or overlaps Care needed if grid extended
an existing project with pre- that additional errors are not
existing grid that may be introduced as not working from
extended “whole to part”.
Local project grid (LPG) (see Simple grid that may be based Prudent to alter origin values so
10.2.5) on abridged OSGB36 values they are not confused with
but with unity scale factor. Use OSGB36 co-ordinates
when away from areas with
APG.
Table 9 – Survey Grid choices
Page 29 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
The survey grid shall be defined by a continuously operating reference system

(CORS) such as OS Net or on the ground by a network of permanent ground
markers (PGMs) that are based on a hierarchy of Primary, Secondary or Tertiary
PGMs.
NOTE 3: Once PGMs are defined on the ground, their preservation is essential to maintaining the
absolute accuracy and usefulness of the survey grid. Around 5% per annum might be destroyed so
some form of maintenance is advised.
NOTE 4: Utilising a survey grid which is tied to National Grid monumentation (OSGB36, ETRF89,
LSG) via GNSS surveying provides centimetric reassurance of PGM position and re-establishment.
NOTE 5: PGM networks should be sufficiently accurate to facilitate future engineering setting-out.
Only slab track setting-out requires tolerances of 2 mm in location. CORS may be used with machine
control for earthworks and formation construction utilising earth moving machines.
10.2 WGS84 and ETRS89
10.2.1 General
NOTE: WGS84 (World Geodetic System grid 1984) is the worldwide co-ordinate grid on which GNSS
measurements are made. However, Global datums such as ITRS and WGS84 are not suitable for
national mapping, as tectonic movements of the Earth’s surface are apparent in these. Britain is
moving at 2 5 mm per year north-east with respect to ITRS. Over a decade such a change would be
significant in national mapping (the difference between ETRS89 and ITRS co-ordinates in Britain in by
2019 is expected to be about 500mm). To remove this effect, a fixed epoch GNSS co-ordinate system
is used - ETRS89. This represents all GNSS co-ordinates at the tectonic epoch 1989.0. A
transformation is used to convert WGS84 co-ordinates to ETRS89.
ETRF89 and EUREF is a European 3D reference grid based solely on space techniques
The co-ordinate system that GNSS measures to directly in Europe is set up to be ETRS89.
In day-to-day usage, this grid system shall be converted into one of the following four
grid systems for general usage:
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
a) OSG36;
b) Absolute project grid (APG);
c) pre-existing survey grid; or
d) local project grid (LPG).
10.2.2 OSGB36
NOTE 1: In the earliest stages of most projects, it is best to utilise the national survey grid, whose
infrastructure is provided by the GB national mapping organisation, the Ordnance Survey (OS). This
enables the use of the mapping, point clouds and aerial imagery data accessed from Network Rail’s
Geo RINM viewer (GRV). However, there are limitations to this grid in that it is based on a Transverse
Mercator map projection that introduces a scale factor, depending on how far the location is away
from the central meridian (a line running north south). Read 10.2.5 on LPG for a measure of the size
of the Scale Factors introduced. Distances also need to be reduced to mean sea level (MSL). This
means that a distance measured on the ground will not be the same as that measured from a CAD
drawing of the same place.
NOTE 2: For more information on OSGB36, read A guide to Co-ordinate systems, produced by the
OS.
Page 30 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure 2 – Spherical earth meets flat paper

(Source RICS Client guide series - Map projection scale factor - avoid the potential
dangers of scale factor)
NOTE 3: Figure 2 demonstrates the manner in which the Scale factor (SF) is applied using OSGB36.
The diagram is a section west to East across the UK. There are two locations where the SF is 1 and
everywhere else it varies depending on the Easting co-ordinates. Table 10 gives the OSGB36
Eastings and the SF for that location.
10.2.3 Absolute project grid (APG)

NOTE 1: The limitations of OSGB36 may be overcome by using an absolute project grid. This is a
bespoke project grid designed for use on a particular project and has carefully defined criteria
allowing its use within a defined area.
An example of this is the “Snakegrid” concept, which may be used for any geographically long and
thin project over 10 km in length. This grid has been defined by using an approximate centreline of the
main route, known as a trend line and using bespoke algorithms, which incorporate the effects of
reduction to mean sea level (MSL) and scale factor so that errors will be no greater than 1/50,000 or
20 mm per kilometre (20 ppm). Consequently, all work using such a grid can be computed without the
application of a scale factor or consideration of reduction to MSL.
Such grids have been established for numerous routes (see Appendix D - ). Levels are based on OS
Newlyn datum and where new work is proposed in these areas these grids should be utilised to avoid
the confusion of a proliferation of survey grids.
A GNSS based PGM survey shall be carried out to form the main co-ordinate
framework or network.
NOTE 2: GNSS surveys are specified in clause 11.
Initially all PGMs shall be computed using GNSS WGS84/ETRS89 co-ordinates.
Baselines shall also be observed to a minimum of three Ordnance Survey Active
Network GNSS locations to form a gross error check. Rinex data for these three OS
points and precise ephemeris data shall be downloaded and used for post
processing.
Real-time active net GNSS co-ordination for primary, secondary or tertiary PGMs
shall not be used.
For high precision engineering survey networks (i.e. rail survey or setting out works
to sub-centimetre accuracy), GNSS techniques shall be used as part of a network of
permanent ground markers (PGMs).
Page 31 of 76

--```,,`,`,`,,,``
OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
The network shall consist of a hierarchy of PGMs as follows:

a) Primary – 1st Order: establish in pairs, with a good view on to the railway
located with a maximum spacing of 10 Km and a minimum interval of 5 Km;
b) Secondary – 2nd Order: establish in pairs, with a good view on to the railway.
The maximum interval shall be 2 Km and the minimum interval for 2nd Order
shall be 1 Km;
NOTE 3: In some situations, the Secondary may be omitted and the Primary spacing cut down to
that of the Secondary. See 10.2.7 for accuracy of PGM network.
c) Tertiary – 3rd Order: establish as the detailed work progresses.
NOTE 4: This might often not be using GNSS techniques but conventional total station traversing
as detailed in the Track surveying module NR/L2/TRK/3100/MOD01.
For longitudinal track surveys, they shall either be:
d) located at a maximum spacing of 200m but not less than 100m apart; or
e) TMGs established in OLE masts (or other stable structures) at a maximum
spacing of 80m on both sides and not established directly opposite one
another on OLE masts or the same portal structure.
TMGs are best inserted 400 to 550mm above the plane of the rails but on occasions,
where this is not physically possible, they should be inserted as close to this as is
practicable.
Where TMGs are installed for S&C surveys, they shall be established at a maximum
spacing of 50m in suitable structures.
NOTE 5: In locations where access to attach prisms is problematical TMGs may be replaced with
mini prisms as per Appendix B - , 10 Type 9. These are left in-situ permanently.
NOTE 6: Surveying for TMGs is specified in NR/L2/TRK/3100/MOD01.
For aerial survey and LiDAR uses (see also NR/L2/TRK/3100/MOD03), the Tertiary
network shall be linked to the ground control points used to relate the aerial survey
models directly to the ground.
This allows the 2D photography or LiDAR data to be converted to the same survey
grid and turned into 3D digital models.
For safety and security, all primary and secondary PGMs shall be established in
pairs a minimum 500m apart and fixed into secure, immovable objects. At least one
of the pair shall have a clear sighting onto the railway.
NOTE 7: In the majority of cases these will be on or next to highway or pedestrian bridges or tunnels.
Survey PGMs shall be located where there is a good view of the sky with no
obstructions.
NOTE 8: This is to enable GNSS use.
Primary or secondary PGMs established on OLE mast bases shall not be used.
This is because of “multipath” issues with GNSS techniques in these locations.
Cable stays may be used for primary or secondary PGMs.
Page 32 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
NOTE 9: Consideration should be given to surrounding vegetation growth or future land use in urban
areas that could cause obstructions to PGMs.
NOTE 10: Software exists to convert from GNSS ERTS89 latitude and longitude coordinates for
discreet PGM locations to a Snakegrid, in the form of “Snakegrid points” software or to convert CAD
files or other file formats from OSGB36 to a Snakegrid through Microstation DGN specific software or
FME software and the Snakegrid workbench. More details on the Snakegrid are available from the
Snakegrid website.
10.2.4 Use of pre-existing survey grid

Where new work interfaces with an existing survey grid, the new work shall be tied in
to the former work by utilising the survey network set-up as part of the original
project as the Primary PGMs, then creating Secondary and Tertiary PGMs in
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
locations suitable for use on the new project.

When using an existing grid, the PGMs being used shall be verified on site and
validated.
Details of the pre-existing project grid shall be sought from the CSM of that project.
NOTE: An example of this is where the surveys for the Thameslink programme were tied into the
London Survey grid (LSG).
10.2.5 Local project grid (LPG)

NOTE 1: This form of grid is suitable for use within a project area up to 10 km in length.
A GNSS control survey shall be carried out to form the main co-ordinate framework
as before.
At an agreed location a grid origin and orientation shall be defined (related to
OSGB36) to give positive co-ordinates and unity scale factor, within the area being
considered.
This is shown in the example below.
EXAMPLE
An example of the application of a local project grid is given as follows:
Install and set up survey control ground framework for the site as per
requirements for the topographic survey needs.
Fix the location of a minimum of three PGMs using GNSS to provide OSGB36
grid co-ordinate values. The use of OS Smart Net (accuracy 15 to 25 mm) is
only appropriate to provide a link to OSGB36 and should not be used to provide
high accuracy PGMs for track works unless also traversed as a check.
“Take out the join” to compute the bearings and OS grid distances between the
PGMs from the Easting and Northing co-ordinates.
One of the PGMs should be chosen, usually one in the middle of the site, or
another by agreement with CSM and the bearing to one other PGM should be
kept fixed.
A false origin for the local project grid should be created based on the OS six
figure OSGB36 co-ordinates by removing the first two figures off the Easting and
Page 33 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Northing for the fixed PGM. Then, using the false origin co-ordinates (local
project grid (LPG)) and the fixed bearing to the accepted PGM, compute the co-
ordinates of all other PGMs.
To convert from OSGB36 to local project grid, a scale factor needs to be applied.
Table 10 shows the local scale factor in terms of National Grid Eastings at 10
Km intervals. 400 Km is the central meridian. The two columns of the National
Grid Eastings indicate that two points the same distance from, but on opposite
sides of, the central meridian have the same local scale factor.
The effects of the reduction of lengths to and from mean sea level need not
concern us here as differences in level are not significant enough over a small
site area to require attention. A height of 1000 ft above mean sea level will
produce a difference of one part in 20,000.
Grid distances from OSGB36 need to be converted into distances on the ground
before they can be used for computations on the local project grid.
Page 34 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Local project grid distance d = OS grid distance D ÷ Scale factor (SF) (1)
National Grid Eastings Local scale factor
400 km 400 km 0.99960

390 410 0.99960
380 420 0.99961
370 430 0.99961
360 440 0.99962
350 450 0.99963
340 460 0.99965
330 470 0.99966
320 480 0.99968
310 490 0.99970
300 500 0.99972
290 510 0.99975
280 520 0.99978
270 530 0.99981
260 540 0.99984
250 550 0.99988
240 560 0.99992
230 570 0.99996
220 580 1.00000
210 590 1.00004
200 600 1.00009
190 610 1.00014
180 620 1.00020
170 630 1.00025
160 640 1.00031
150 650 1.00037
140 660 1.00043
130 670 1.00050
Table 10 – Local scale factor in terms of National Grid Eastings

NOTE 2: EXAMPLE continued from previous page.
Observed OSGB36 co-ordinates:
PGM1 521,300.000E 191,941.000N
PGM2 521,700.000E 191941.000N
PGM1 to PGM2 Bg = 90º Dist =400 m
Page 35 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
To Convert to Local project grid

From Table 4 at 521 km Easting SF is between 0.99978 (520 km) and
0.99981 (530 km).
Scale Factor = (0.1  0.00003) + 0.99978 = 0.999783
d = D ÷ SF from equation (1)
d = 400 ÷ 0.999783 = 400.087
Therefore the new PGM values in local project grid are:

PGM1 1300.000E 1941.000N
PGM2 1700.087E 1941.000N
For all Primary and Secondary PGMs, ETRS89 (GNSS), OSGB36 (OSNG) and APG
or LPG grid values shall be derived and included on a co-ordinate schedule.
10.2.6 Level datum

NOTE 1: Ordnance Survey benchmarks throughout the UK have now been superseded by GNSS
derived heights. The RICS (Royal Institution of Chartered Surveyors) guidance note ‘Benchmarks to
GNSS heighting – Virtually level’ should be consulted to understand further.
Heights shall be derived by GNSS for primary and secondary PGMs and
transformed to OS Newlyn datum using the transformation OSGM02 for projects at
GRIP 3 or above before September 2016 and OSGM15 or successor (from OS web-
site) for projects not at GRIP 3 or above before September 2016.
NOTE 2: A tool is available from the OS web-site to allow conversion from new OSGM15 height
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
values to older OSGM02 values where this presents difficulties with linking into existing survey PGM
values upon which designs have been based.
The post-processing of GNSS surveys shall be undertaken.
NOTE 3: This is to achieve the maximum accuracy of derived heights and traceability of survey
quality.
Double run levelling shall be undertaken between PGMs with standard levelling
techniques. Comparisons with already published values shall be made and any
discrepancies highlighted and agreement reached with the CSM on the final values
to be used.
NOTE 4: A relationship also exists between OS Newlyn datum and Chart datum, associated with
works around rivers and tidal areas. This relationship should be known and noted on deliverables
when relevant. Other datums have been used in the past such as the “OS Liverpool” datum and in
Scotland the “Caithness” datum, so where a new survey is related to legacy data, care should be
taken to use the appropriate datum. When interoperability with Europe, for gradient considerations is
needed, the height datum used in Europe (European vertical reference system – EVRS) should be
used. This is based on the Normaal Amsterdams Peil (NAP).
Page 36 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
10.2.7 Accuracy and adjustment of horizontal and vertical PGMs

The primary PGMs shall be designed, observed, calculated and adjusted so that the
direct distance between adjacent PGMs, calculated from the adjusted co-ordinates,
is not in error by more than 1 in 100,000 (10mm per km) unless linking to an existing
survey grid that was created to a less accurate requirement.
For distances between adjacent primary PGMs of less than 200m, the maximum
error shall not be greater than ±2 mm.
The secondary PGMs shall be designed, observed, calculated, adjusted and
checked so that the direct distance between adjacent PGMs, calculated from the
adjusted co-ordinates, is not in error by more than 1 in 75,000 (13.3 mm per km) or
shall link to an existing survey grid that was created to a less accurate requirement.
For distances between adjacent survey control stations of less than 200m, the
maximum error shall not be greater than ±3 mm.
The height difference between any two points used as principal survey stations or
other bench marks shall not be in error by more than ±(12√k) mm, where k is the
distance in kilometres between the points being considered, or ±3 mm, whichever is
the greater.
NOTE 1: For slab track or high precision setting-out permanent ground marker networks, see
NR/L2/TRK/3100/MOD01, Appendix D and for geospatial monitoring see NR/L2/TRK/3100/MOD01,
Appendix C.
The accuracy requirement for Tertiary PGMs shall be dependent on their intended
use.
I.e. if the works to be undertaken require a survey system to deliver Band 1
accuracy, the accuracy of the tertiary PGMs will be required to equal that of the next
level up in the hierarchy of primary or secondary PGMs.
The CSM shall use their discretion to accept lesser accuracies for PGM fixing where
mitigating circumstances exist.
NOTE 2: E.g. bad weather.
10.2.8 Longitudinal metreage

At the project outset a unique location shall be defined as the origin of the running
metreage or “single line of way”.
Figure 3 shows an old example of a well-defined datum for the Engineer’s Line
Reference mileages at York station.
Page 37 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure 3 – Zero mileage datum at York station

The PM and/or DPE (especially for multi-disciplinary projects) shall agree the
proposed metreage system with the CSM.
NOTE 1: This does not have to start at 0m and is usually set to be 1000 m or similar.
The datum start point for a design project shall be made to coincide with a clearly
defined location on the ground that is unlikely to change, such as the start of a
tunnel, bridge or other structure or a clear understanding of the metreage for a
clearly defined location on the ground that is unlikely to change shall be agreed.
Mileposts are often destroyed or physically moved during track renewals work, so
they are not suitable.
For most projects a project reference metreage is created (preferably based on an
Absolute Project Grid e.g. a Snakegrid, to avoid distance errors associated with the
OS national grid).
This metreage shall be constructed from a master metreage string, based on existing
rail alignments using existing LiDAR or OS mapping data as a background.
The project reference metreage shall not be used for any setting-out or positioning of
site assets. All site setting out shall be carried out using 3D coordinates appropriate
to the relevant survey grid.
NOTE 2: The purpose of the project reference metreage is to aid design and location of key features.
Any asset may be referenced to this metreage string.
A design reference string shall be based along the centre line of a rail alignment.
NOTE 3: A design reference metreage might differ from the project reference metreage due to
alterations in design alignment geometry.
Features other than rail position, such as signals, OLE gantries, etc. shall be
positioned on site using 3D coordinates with the work undertaken by a competent
site engineer.
Page 38 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
This also avoids the issue of normal offsets from straight or curved track that would
require definition of the process to be employed.
NOTE 4: There has previously been confusion with features positioned on site to a project reference
metreage value but using a design reference metreage value visibly marked on track 3D coordinate
positioning removes this potential source of error.
NOTE 5: Signal sighting forms include co-ordinate locations.
NOTE 6: Five-mile diagrams can be viewed in parallel with the ELR dataset on the Geo-RINM Viewer
which is defined in OSBG36.
NOTE 7: The ability of co-ordinate systems to define both metreage distance and location precisely
means these can now be considered the only accurate way to preserve and maintain a metreage
reference system.
10.3 Permanent ground markers (PGMs)
10.3.1 Location and design of permanent ground markers

NOTE 1: Permanent ground markers fall into two different categories:
a) photo control or ground control points (GCP) (temporary use) such as corners of manholes or
buildings (easily identified from aerial photography). These may reused for small local surveys
as per LPG clause 10.2.5.
b) PGMs to be constructed as survey monuments for longer term use.
All PGMs shall be stable for at least five years after installation. They shall be in
protected locations suitable for frequent access.
PGMs shall be used as benchmarks for height except where located on rooftops.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
NOTE 2: Where practicable, PGMs should not be located within 3.0m of any rail.
NOTE 3: PGM types are shown in Appendix B - . The Survey contractor may choose the most
appropriate marker for each location from this selection. Alternative designs may be accepted when
agreed by the CSM.
When locating any survey PGMs on site, they shall be positioned to give visibility of
both of the work area and the sky.
PGMs shall be easily and safely accessible and positioned to enable accurate
establishment of their relative positions.
They shall be located so that they are not destroyed during the
design/implementation phases of the project.
PGMs shall not be “feno” type markers, which shall only be considered as temporary
GMs unless surrounded with concrete.
PGMs shall be a nail in a concrete base, structure or metalled surface unless agreed
with the CSM.
PGMs shall conform to NR/L2/INI/CP1030.
PGMs shall have a precise centring point with an accessible level contact point for
levelling staves.
For PGMs external to Network Rail’s boundary, arrangements shall be made by the
Survey Contractor with adjacent land owners for the construction of PGMs.
Page 39 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
This might include Local Authorities for PGMs on public highways for which a licence
might be required.
The distance between pairs of Primary and Secondary PGMs in the same vicinity
shall be 500 m, or greater if line of sight is possible.
Each PGM shall be visible from at least two other PGMs at ground level.
NOTE 4: Buried services information requests are specified in NR/L1/INI/CP1010. The data is
available from the national records team (NRG) or viewable from GRV. They require a T-12 week
period for requests for information to be processed.
11 GNSS surveys
The establishment of Survey PGMs shall be undertaken utilising GNSS techniques
requiring Land Surveying grade GNSS receivers, unless agreed with CSM and
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
recorded in the Project survey strategy.
NOTE 1: These are Dual frequency receivers capable of receiving signals from GPS, Glonass and
Beidou, Compass, Galileo, or others when available. These are not the same type of receivers used
for the collection of Asset Information for input into a Geographical Information System (GIS).
For PGM surveys, ETRS89 co-ordinates (observed directly by GNSS receivers)
(Latitude and Longitude format not Cartesian ETRS89 co-ordinates) shall be
obtained, unless agreed with CSM and recorded in the Project survey strategy.
NOTE 2: ETRS89 co-ordinates are then capable of being converted into the project’s chosen survey
grid whereas simple local project grid Cartesian co-ordinates might not be.
NOTE 3: There was an update of the transformation model in 2015 (published in August 2016) and
depending on the stage the project has reached either the old OSGN02 or OSGN15 model in
GridInQuest software should be used. If in doubt contact a qualified survey engineer.
Notes for use of GNSS are provided in NR/L2/TRK/3100/MOD03.
Industry’s best practice shall be utilised as defined in the following documents (or
future updated versions):
1) Guidelines for the use of GNSS in land surveying and mapping. RICS
guidance note. 2nd edition (GN 11/2010).
2) Guidance notes for GNSS network RTK surveying in Great Britain Issue 4,
May 2015 ©TSA
Page 40 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
12 Surveying outputs
12.1 Survey report

On completion of the fieldwork and PGM adjustment, a comprehensive survey report
shall be prepared. This shall include:
a) introduction and date survey carried out, including a summary of the planned
and actual programme of work and delivery schedule;
b) scope of survey works and deliverables;
NOTE 1: This may be extracted from the survey remit or brief.
c) a description of the methods, equipment, survey software (capture and
processing), and staff employed on the project;
d) survey difficulties encountered;
e) survey PGM network (see 12.2 for details);
f) description of the method of adjustment of the horizontal and vertical net
including GNSS;
g) this shall show the traverse closure or statistical analysis of the least squares
adjustment of the network. Confirmation of survey accuracy required against
that achieved shall be provided;
h) a section in the report describing the Quality assurance procedures used to
test the accuracy, completeness and reliability of data giving the results of
tests applied including an interpretation of results supplied;
NOTE 2: Supplying a QMS certificate only is not acceptable.
i) comments on the specification and results and recommendations for future
work; and
j) a draft of the report shall be submitted for comment and amendment by the
CSM.
NOTE 3: A template of suggested headings for alternative survey platforms has been included as
Appendix E.
12.2 Survey PGM network

A PGM witness diagram shall be produced for each PGM unless they consist of a
nail or TMG installed in an OLE base or mast.
The PGM witness diagram shall show its general location with dimensions to at least
three easily recognisable and durable points.
These may use form NR/L2/TRK/3100/SU001 or variations providing all the
information is present.
This shall be accepted at the discretion of the CSM.
NOTE 1: Co-ordinates should be omitted and reference made to the schedule specified in 12.2.1.
This is so that a new set of witness diagrams does not have to be issued each time updates are often
made to a co-ordinate listing.
Page 41 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
NOTE 2: A bespoke “Witness diagram App” has been developed for those with an NR “Apple iPad”
and an NR e-mail address. This enables the correct format to be created and many fields to be
completed in a simpler way. It is available from the NR App store.
12.2.1 Schedule of permanent survey control stations

A schedule shall be prepared giving a-d in MS Excel format.
a) PGM name/identifier and order in comments (Primary, etc.);
b) ELR and mileage;
c) plan co-ordinates Easting (X), Northing (Y) (ETRS89, OSGB36 and APG or
LPG) and, where new values have been computed, if these supersede
previous values. Details of traverse or other calculations and closures shall be
provided to back this up;
d) level (Z) value;
e) type of PGM, e.g. PK Nail, Brass rivet.
f) comments, e.g. Integrity of point (i.e. stable/unstable, destroyed), not found,
and ease of use.
Information shall also be given about the derivation of the PGM.
NOTE 1: See Appendix C for a PGM Schedule example.
The style used shall be that shown in Appendix C - , Figure C-2.
All information regarding the PGMs (whether new installations or those previously
installed) shall be provided to the CSM.
12.2.2 Horizontal and Vertical control network diagrams

A schematic or true to scale (TTS) plan in 3D Microstation v8, *.DGN format or a
legible network diagram shall be provided of the PGM network showing the PGM
designation, horizontal and vertical interrelationship between PGMs with a full
explanation of what is being provided.
NOTE: Examples are given in Figure 4 for GNSS and Figure 5 for Conventional traversing. The
traverse diagram may include the distances, angles and reduced level of PGMs.
Page 42 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure 4 – GNSS example
Figure 5 – Conventional traversing example
Page 43 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
12.3 Survey BIM/CAD/GIS Deliverables

The deliverables listed shall be provided by the survey contractor:
a) final electronic survey data files prepared as a full cartographic three-
dimensional string digital ground model in accordance with
NR/L2/INI/EDT/CP0091. The data shall be prepared in sections of no greater
than 10Km in length or any project specific requirement;
b) Land XML v1.1 format (or more recent equivalent) output of 3D survey;
c) ArcGIS shapefile or of a format etc. shall be agreed with CSM. Intended for
use with NR Asset Information systems.
d) data suitable for input into Balfour Beatty Rail Projects Clear route 2 software
for gauging, passing clearance and platform clearance assessment when
specified; and
e) any data from raw survey data files collected on site to survey calculations
undertaken at any time and details of any quality assurance (QA) undertaken
at Network Rail’s request.
Site photographs at time of the survey may be required, as specified in clause 15.
In relation to laser scan surveys, where undertaken, f - i shall apply.
f) All registered point clouds in native format plus supporting databases used to
generate unified and cleaned databases shall be provided. The files shall be
supplied in the same database structure they were created in with consistent
file names to achieve functioning reference files.
g) All files suitable for publishing on web enabled software such as, for example,
Leica Truview, Point tools or other similar software systems shall also be
delivered (image resolution to be a minimum of 2048  2048 and encoding
error at 200 m shall be 0.04 m).
h) Scan data from TMD mounted or other kinematic scanning shall be provided
in *.LAS. *.PTS, *POD or RCS formats.
i) All registration log files related to scan processing (static) showing control
point and cloud to cloud registration residuals shall be provided.
Network Rail shall have ownership rights to all data generated from scan surveys,
whether delivered or not by the supplier, including the right to a free copy of all data
for archive and security of access.
Data derived from terrestrial laser scanning shall be as specified in Appendix F - .
12.4 Data preparation

The contractor may use survey systems other than Microstation V8 or later to
prepare data.
Any such data shall be converted completely and without omission or distortion to
Microstation V8 or later format in 3D prior to delivery by agreement with the CSM.
Page 44 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
To allow survey data validation, data shall also be provided as ArcGIS Shapefiles
and Land XML v1.1 format or similar current version by agreement with the CSM.
The Survey contractor shall self-certify data in accordance with Error! Reference
source not found. form.
Where other data formats are required (i.e. *.IMP, TruView, 3D models), the supplier
shall confirm the delivery format software required by Network Rail and achieve full
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
compatibility.
The contractor shall be responsible for the costs of maintaining software versions
and formats of deliverables with the current requirements of Network Rail.
13 Survey data management and quality assurance
13.1 General
The CSM shall oversee technical acceptance of digital survey data. The CSM shall
delegate tasks within the checklists to appropriately competent staff as required.
13.2 Survey shelf-life, Data maintenance and Survey requirements strategy

NOTE 1: All survey data should be assumed to have a “shelf life”. Confidence in the data will
diminish over a period of time as the data becomes older. It is the responsibility of the Project
Manager, Designated Project Engineer or Discipline Engineering Manager, in consultation with the
CSM, to assess if the existing data is appropriate and what kind of assurance processes need to be
undertaken, to assure that the data is “fit for the purpose” to which it will be put. The “shelf life” of
survey data may be extended by undertaking a limited resurvey or simple measurements at critical
locations.
For example, a plain line permanent way survey will have a “shelf-life” of a maximum of six months as
the track position can be moved by the passage of trains or, in the worst case scenario, the track
might have been tamped, changing its position. In critical areas, an embargo on tamping might need
to be agreed with the Maintainer.
PGM data has a longer “shelf-life” and can be expected to last a minimum of five years providing it
has been installed in a robust manner, in solid surfaces.
For Signalling or OLE surveys, the accuracy of the surveys is not required to be of the same order
(see Error! Reference source not found.) and, therefore, the “shelf life” may be extended. However,
it is possible to use more accurate data for a purpose that requires less accurate data, but not
vice versa.
Where existing data has been identified as “fit for purpose”, the Project Manager,
Designated Project Engineer or Discipline Engineering Manager shall include in the
Project Survey strategy any additional survey needs, plus ongoing maintenance and
update requirements over the project’s life-cycle, including the hand back period.
RAG methodology shall be used, i.e.:
• Red: high risk;
• Amber: medium risk;
• Green: low risk.
NOTE 2: The list of data types given in Table 11 is not comprehensive. Table 11 should only be used
as a guide.
Page 45 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 46 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Checking Risk
Data type Consequence Comments
method (RAG)
PGMs Unable to locate Proving survey Red Used for whole life of
and overlay and audit. project and afterwards.
information from Facilitates “joined up
See 13.5.1.
different thinking” and planning
disciplines
Platform Delay and Design Comparison Green Cost implication

surfacing and rework against other
coping available data
sources e.g.
imagery
Tunnel walls Clearance Review of survey Red Major additional costs

infringement data for for re survey and re
redundancy of assessment of
observations clearances
Ironwork Design rework Review of survey Amber Some additional costs

data for
redundancy of
observations
Foundation Minor rework Dimension Green Some additional costs

consistency
Dimension
Brickwork/ Design rework Green
consistency
blockwork
Earthworks Design rework Use DTM and Green Design checks should
compare cross prevent abortive site
Troughing Re-positioning of
sections for construction works
new structures to
significant
avoid clashes
differences
Avoids additional
Green construction costs
Plain line, S&C Delay and Design Use standard Red Significant additional
alignment rework checking costs
techniques as
given in 13.4.2
Datum plates Delay and Design Use standard Amber Significant additional
rework checking costs
techniques as
given in 13.4.2.
Page 47 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Checking Risk
Data type Consequence Comments
method (RAG)
Drainage Delay Derive long Green Ultimately all would

sections along give increased
drainage runs maintenance costs.
and sense check
Costs savings from

Formation, Sand Additional Site checks reduced materials
or bottom ballast materials used against design needed
Green
and likely poor
track quality
OLE Wiring, Delay and Design Derive long Red Some additional costs
including Height rework sections along
and Staggers wire runs and
sense check
Table 11 – Examples of data types
13.3 Survey QA verification and validation

Proving surveys and quality audits may be carried out by a project representative
and CSM or the Survey contractor or consultant dependant on the risks identified in
the survey risk register.
Risks associated with critical items requiring QA verification and validation shall be
listed in the survey risk register as specified in clause 7.
All field observations, field sheets and edits undertaken on those prior to use,
calculations, digital files, and the order they have been run in shall be retained and a
complete audit trail kept for possible inspection.
Some site verification and office data validation shall be undertaken.
NOTE 1: This may involve a resurvey of 10% of existing information in critical areas by a third party
contractor. This is to achieve confidence in the surveys performed by the survey contractors.
Confidence in our suppliers will be built up over a period of time and less verification of data on site
will then be required.
Two forms of QA verification and validation might be needed:
• Prior to design – QA verification and validation of an existing or a new survey;
• Prior to construction of the design – Identifying changes that have taken place rendering the
design in need of updating or the PGMs being destroyed that are required for the setting out
and them needing to be replaced.
The identification of high risk items from the survey risk register shall define how the
QA verification and validation is undertaken.
NOTE 2: Issues prior to construction might have an especially significant impact and thereby
introduce major risk to the implementation.
Page 48 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
13.4 Survey site verification
13.4.1 PGM verification

NOTE 1: Using PGM witness diagrams, the locations of these PGMs will be found and their suitability
verified by completing NR/L2/TRK/3100/SU002.
A sample of 20% shall be verified for the first occasion with a new supplier.
After an appropriate level of satisfaction has been achieved, the sample size may be
gradually reduced to 5%.
NOTE 2: An example is given in Table 12.
Sample Unacceptable No. not to

Verification size
No. of PGMs be exceeded before next
Audit No.
% lower level of audit
1 20 20% (4) 2
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
2 20 10% (2) 1
3 20 5% (1) N/A
Table 12 – PGM verification

NOTE 3: When a network of survey ground markers has been established, a re-measure of a
traverse leg (angle and distance) and the difference in level between the PGMs will provide a check
on that part of the traverse. Ideally, a different process to check the PGMs will be used to provide an
independent verification, e.g. when the PGM network has been established by GNSS, a conventional
closed traverse would be used to verify the results and vice versa.
NOTE 4: As an alternative to the project undertaking a check, in many instances, this data will be
utilised by a third party and their own measurements will provide the assurance that the data is
correct.
13.4.2 Detail survey verification

NOTE 1: A similar concept to that explained for the PGM verification should be undertaken for the
detail survey. Over a number of jobs, by the same survey contractor, the degree of verification may be
relaxed if errors are not encountered.
NOTE 2: Using a plot of the site, as required, verification will check the relative locations of points of
detail. Some of this verification may be achieved utilising site photographs and other available data
such as video survey data and OS Mastermap or Aerial orthophotos (True to scale imagery). This will
provide a means of identifying that the relative position of features appears to be correct.
Where certain dimensions are classed as “critical” or perceived as “high risk” in the
survey risk register, a site visit shall be undertaken by the CSM or a project
representative to check a proportion of these.
NOTE 3: For instance, the clearance to a structure as derived from a digital ground model or the “six
dimensions” defining the squareness of bridge abutments for an over bridge, as shown in Figure 6.
This is particularly critical when the bridge is a skew structure
Page 49 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure 6 – Six dimensions for bridge abutments
13.5 Survey validation

NOTE: This exercise concentrates on the survey data provided. Does the data meet the specification
in terms of technical content?
The DPE shall oversee acceptance of survey data and carrying out assurance
checks.
The DPE may discharge this duty to the CSM.
The Survey supplier shall complete a self-certification Quality Assurance check form
(Please see Error! Reference source not found. and NR/L2/TRK/3100/SU005).
The CSM shall review the submitted form and decide if further independent checks
are required.
Where discrepancies are found in survey data (errors, omissions or noncompliance),
they shall be reported to the supplier, DPE and PM.
Where discrepancies are reported to the survey supplier and they fail to take
effective remedial actions the Project Manager shall be notified of any non-
compliance with requirements.
The survey supplier shall provide any records requested by NR for assurance and
audit purposes.
Page 50 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
14 Setting out – Survey Grid and PGMs

NOTE 1: This is when a design of new construction is marked out on the ground in three-dimensional
space for construction implementation. It is also known as “Dimensional control”.
Any suppliers using the survey grid for setting-out shall make contact with the CSM
to acquire details of relevant survey PGMs for their works.
Usually, tertiary PGMs will be the ones predominantly used for setting out.
The project grid, as supplied by NR, shall be referred to for all works carried out.
NOTE 2: There is a need here to be aware of working within multi-disciplinary projects. The supplier
might be setting out track position from survey PGMs that they have established and might need to tie
into a new platform where a different supplier is to set-out platform coping stones to their own PGMs,
the potential for errors here is increased if both suppliers are not working from an approved source of
survey PGMs.
Prior to construction, the PGM network shall be revisited by the Implementation
contractor to verify and validate what was done before. If any are missing they shall
notify the CSM and any PGMs which have been destroyed shall be replaced. This
shall be carried out at the earliest opportunity so as to allow for any replacement
PGMs to be reinstated and validated at least T-16 weeks.
This is to allow for any possession access and the works to take place. This should
then also allow time for the supplier to validate setting out data from the new PGMs.
All additional PGMs shall be traversed into the grid and meet closure errors as per
NR/L2/TRK/3100/MOD01. Elevations for any PGMs shall be determined by separate
double run levelling.
A survey PGM report shall be provided for all new survey PGMs installed, as per
Clause 12.
Often the PGMs might be located in areas where construction is to take place.
Suitably located primary construction PGMs shall be installed and co-ordinated in
areas clear of the construction work, unlikely to be damaged by site activities.
Wooden pegs shall not be used as PGMs.
This is as they are liable to damage and not robust for site works.
NOTE 3: Some have called this the “Iron ring”.
Only surveyors/setting out engineers shall geospatially co-ordinate PGMs as
approved by the CSM. Any site PGMs geospatially co-ordinated by the supplier shall
be approved and verified by the CSM and meet the requirements detailed in the
Project Survey Strategy prior to any construction work commencing.
NOTE 4: For the purposes of using site based 3D machine control for excavation and ballasting there
will need to be adequate survey PGMs throughout the excavation areas. These are necessary to
provide a clear line of sight from the total station to the prism mounted on the dozer mast. Additional
PGMs may be required in these areas to allow for obstacles that will affect the line of sight, e.g.
engineering trains, existing site features.
NOTE 5: Most of the techniques and equipment used are the same as conventional surveying and
setting out is simply another application of engineering surveying.
NOTE 6: Further details on setting out in the generic form can be found in “Surveying for Engineers”
– Uren & Price or Setting out procedures for the Modern Built Environment – CIRIA publication.
Page 51 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
When specific locations have been set-out using co-ordinates, a record of the “as
set-out” value shall be recorded and compared directly with the “as designed”
location in such a way as to able to be reviewed and signed off by the CSM as a QA
check.
NOTE 7: Where TMDs are being used for Survey/DVS/As-built data surveys, the supplier should
provide survey PGMs at the extents of the design string. These limit extent positions should be
chainage based (from design rail string limits) and where site features allow, should be based within
5m of the end of a design string position.
All equipment used shall have a manufacturer’s approved, in date calibration

certificate.
It is the engineer/surveyor’s responsibility to check all equipment prior to use is fit for
purpose.
15 Site photographs
NOTE 1: Site photographs are an invaluable aid to understanding a site. They might not be needed
for all surveys. A visit to the site during daylight is necessary for meaningful photographs.
Where site photographs are created, they shall be taken at a defined location, either
using survey grid co-ordinates or ELR and chainage and with the direction facing
being identified (up/down, east/west, facing low mileage direction or in direction of
increasing mileage, etc.).
Details for recording digital photographs are given within NR/L3/TRK/3100/MOD05,
7.6 and an optional Photo log sheet form NR/L3/TRK/3105/SU501 is also available.
NOTE 2: A sensible rule of thumb is to always take with back to low mileage and any photo without a
direction indicated should be assumed thus.
NOTE 3: A useful means of identifying photo locations is to use the Google Earth or OS Mastermap
of the site and annotate the photo number at the location and the direction in which the photos have
been taken by an arrow.
NOTE 4: Photographs of the site may form a project survey deliverable.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 52 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Appendix A - Removed
Page 53 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Appendix B - Permanent ground marker types
B.1 General
Whenever possible, survey consumables such as ground markers, paint and
fieldbooks should be sourced by users from sustainable sources. The use of spray
paints and “professional graffiti” should be kept to an absolute minimum.
PGM materials shall be used that are long lasting.
Ground markers shall be installed as specified in NR/L2/INI/CP1030.
NOTE: This specifies a prior records search and a CAT scan being undertaken to locate possible
buried services.
B.2 Permanent Ground Marker Type 1
Figure B-1 – Permanent Ground Marker Type 1 (for dense, very stable paved
surfaces)
Page 54 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
B.3 Permanent Ground Marker Type 2

--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Figure B-2 – Permanent Ground Marker Type 2 (for non-agricultural sites and
unpaved surfaces)
B.4 Permanent Ground marker Type 3

A rust resistant steel rod, nominal length 20 mm  1.0 m, centre-punched on top to
form a reference, shall be driven to refusal and surrounded by minimum 450 mm
diameter  500 mm deep concrete backfill.
The top shall be flush with the ground.
A simple arrangement as shown in Figure B-3 and Figure B-4 is suitable for GMs to
be stable for two to five years. Such a GM arrangement is suitable for Tertiary order
control surveys
Page 55 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
The point may either be a nail, bolt or a pot marked steel pin, set in the concrete.
Figure B-3 – Concrete PGM
Figure B-4 – Example of Concrete PGM
B.5 Permanent Ground marker Type 4

Permanent Ground Marker (For dense, stable paved surfaces).
A simple “PK” type nail will be needed in such surfaces where the addition of a
coloured washer might invite vandalism.
Page 56 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure B-5 – Example of Type 4 PGM in OLE mast base
Figure B-6 – Example of nail and marker arrangement for Type 4
B.6 Track Machine guidance point (TMG/spigot/stud) Type 5

For details on installation methods, contact the CSM.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Figure B-7 – Type 5 example of TMG/spigot/stud
Page 57 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure B-8 – Leica GPH1 prism holder on Type 5

Alternative types of TMG points do exist. However, all new installations should
conform to the dimensions given for the spigot arrangement, in Figure B-9.
Tolerance in manufacture shall be 0.1 mm. Any variance from this shall be
accepted by the CSM.
a) Centre of prism to prism mount TMG clip on point shall be fixed at 67 mm.
b) Top of TMG to prism mount TMG clip on point shall be fixed at 9 mm.
c) The shank length should be 38 mm (Palas not now used).
d) The diameter of the TMG top to bottom is 12 mm.
The 19 mm TMG mounting nut width that may be another smaller AF size.
Page 58 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure B-9 – Dimensions for Type 5 spigot arrangement
B.7 Non-OLE Route Pillar Type 6

For Primary or Secondary work or where an accurate first order PGM is required for
a construction site, a “forced centring” pillar arrangement shall be used.
The instrument sits on top of the pillar eliminating centring errors.
The 150 mm plastic pipe shall not be made of ribbed drainage pipe and shall be filled
with concrete (not earth). The completed pillar shall be firm and not wobble.
The pipe may be of circular or rectangular cross-section and may be shorter (of the
order of 800 mm above ground level) if it is to be used for mounting datum plates or
TMG/spigots/studs.
However, the requirements of relating to the positioning of TMG shall still be
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
satisfied.
Page 59 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure B-10 – “Forced centring”Type 6 survey pillar
NOTE 1: Photographs courtesy of West Coast Rugby project and North London Line improvements
Canyon monitoring project
Figure B-11 – Type 6 example of “Forced centring” survey pillar
Page 60 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure B-12 – Type 6 alternative design of “Forced centring” survey pillar
Figure B-13 – Type 6 head of “Forced centring” survey pillar

NOTE 2: Screw thread on which to attach the survey instrument or target.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 61 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Figure B-14 – Type 6 example of “Forced centring” survey pillar
Figure B-15 – Type 6 pillar construction diagram

NOTE 3: Cube of concrete 1.25  1.25  1.25 m, four 20 mm L-shaped rebar fixed with cruciform,
250 mm diameter drainage pipe filled with concrete at same time as cube topped with pillar plate.
Pipe extends above top of cube by between 1.0 m and 1.4 m.
B.8 Type 7 - Demountable tables

Type 7 - Demountable tables should be para bolted to a vertical surface. These
examples are from the SCC Catalogue. There are significant cost differences based
on stability of the table.
Page 62 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Figure B-16 – Type 7 14TK400 Instrument Wall clamp (Code: 3604070)
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Figure B-17 – Type 7 demountable Table Mounting System (Code: 0301061)
B.9 Type 8 – BRE Levelling bolts

The shape and design of this bolt may be varied with possible savings to be made
on material of construction, but M10 screw fitting should remain.
Figure B-18 – Type 8 – BRE Levelling bolts
Page 63 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
B.10 Type 9 – 360◦ mini prism for permanent installation

This allows the prism to be permanently fixed to a vertical structure or wall, allowing
time saving and overcoming difficulty of access in multi-tracked areas with limited
possession availability. The shape and design of the mount may be different but
example shown is for use in areas where prism security might also be a problem and
allows the prism to be targeted from any direction.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Figure B-19 – Type 9 Leica 360◦ mini prism for permanent installation
Page 64 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Appendix C - PGM data examples
Variations of the witness diagram providing all information is present shall be

accepted at the discretion of the CSM.
The PGM co-ordinate values may be included or reference may be made to a co-
ordinate schedule or listing (when co-ordinates are still to be computed). The level is
assumed to be the orthometric level unless stated otherwise.
The correct project grid name shall be referenced.
NOTE 1: An iDevice App is available to assist in the creation of the approved style of witness
diagram. Contact the CSM for details of availability. This will use Open Map data for the location map
instead of OS mapping.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Figure C-1 – Example of completed PGM Witness Diagram
Page 65 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Method note Verified (Date)
PGM Miles.chains/ Ellipsoid Eastings Northings

ELR Line Latitude Longitude Height Remarks Plan Height Plan Height
Id. yds Height (Grid) (Grid)
Rivet and disc 01

LEC 01 Dec
G7921 79.0462 UM 110.025 204679.807 199862.588 110.025 in OLE mast PRE EH Dec
1 07
base 07
Rivet and disc 25

LEC 15 June
G7927 79.0610 UM 109.529 204579.304 199979.053 109.529 in OLE mast TR PD1S May
1 07
base 07
Figure C-2 – Example of PGM schedule

Plan Height
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
PRE Primary PGM existing co-ords accepted EH Existing height value accepted
PRG Primary PGM fixed by GNSS GNSS Fixed by GNSS observations
SDE Secondary PGM existing co-ords accepted PD2D Levelled from agreed project datum by double run
SDG Secondary PGM fixed from GNSS PD1S Levelled from agreed project datum by single run
TR Tertiary PGM fixed form secondary TH Trig heighting
FT Fourth order fixed from side shot
RP Remote point not able to be occupied, fixed by multiple observations
Figure C-3 – PGM creation method

NOTE 2: These abbreviations are to be used with the method note in Figure C-2.
Page 66 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Appendix D - Snakegrid routes
Figure D-1 – Snakegrid routes

NOTE: A regularly updated listing of ELRs covered by current Snakegrids can be made available.
Page 67 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Appendix E - Survey report templates
E.1 Ground based survey report template

Introduction
This should include the Scope of survey works, date survey carried out, including a
summary of the planned and actual programme of work and delivery schedule.
Personnel and Equipment
This should be a description of the survey equipment, surveying software (capture
and processing), and staff employed on the project. This should include details of
difficulties encountered in completing the work, e.g. track access, missing Client
provided PGMs, etc.
Methodology
Survey PGM Network
This should be a description of the methods employed, the numbers of PGMs and
the hierarchy employed covering: Primary horizontal control, Secondary horizontal
control, Tertiary horizontal control and Vertical control network.
Adjustment procedure
This should provide a description of the method of adjustment of the horizontal and
vertical net including GNSS and Star*Net listing (.txt file) or computations (as
provided in an Appendix). This should show those PGMs held fixed, those allowed to
float, residuals, standard errors of PGMs and error ellipses. Where conventional
traversing has been used the report is to highlight the traverse closures. The report
is to compare survey accuracy against what is required.
A multi paged listing from software without PGMs held fixed, those allowed to float,
residuals, standard errors of PGMs and error ellipses or traverse closures
highlighted is not acceptable.
It should include a quality management report describing the Quality assurance
procedures used to test the accuracy, completeness and reliability of data in the
field, during the processing and the results of tests including an interpretation of
results supplied.
Detail Survey
Evidence of track survey overlaps should be given for track surveys.
Deliverables
This should be an explanation and listing of what has been delivered.
Page 68 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Conclusions and recommendations

This should include comments on the specification, results and lessons learnt for
future work.
Appendices
Client Supplied Fixed Control
Horizontal and vertical control network diagrams (True to scale or schematic)
Least Squares network adjustment summary report
Comparison of any GNSS Network with OS Active Ties
Levelling Schematic diagram and Misclosure Reports
Traverse PGM Observations, Bowditch Traverse Closures and/or Least Squares
Block Adjustment of Traversing/ TMGs
GNSS Derived Height / Spirit Level Height Comparison
Schedule of PGMs and TMGs in MS Excel format
PGM Witness Diagrams
E.2 Train borne surveying survey report template

Introduction
This should include the extents and a summary of the technical requirements of the
survey works.
Programme
Include the date of survey, a summary of the planned and actual programme of work
and the delivery schedule.
Details of the train paths should be added to enable precise time that the data was
collected.
difficulties encountered in completing the work, e.g. track access, missing Client
provided PGMs, etc.
Methodology
This should Include a brief description of technical principles.
The survey grid and level datum shall be defined using the names of any Snakegrid
and Ordnance Survey transformation model used.
Survey PGM Network
This should be a description of the methods employed, if GNSS base stations are
used, the numbers of PGMs and the hierarchy employed covering: Primary
horizontal PGMs and Secondary horizontal PGMs (if used).
Page 69 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
This shall include any levelling to improve the GNSS heighting accuracy.
A GNSS Network diagram should be included for each separate day that train
operations are used showing which CORS GNSS Active stations and base stations
have been used
Adjustment procedure
A description shall be provided of how the GNSS data and data from the track
measurement tool are combined with the CORS system used (OS Net) and any new
or existing PGMs.
This should provide a description of the method of adjustment of the horizontal and
vertical networks including those PGMs held fixed, those allowed to float, residuals,
standard errors of PGMs and error ellipses.
Track alignment accuracy statements
An understanding of the survey accuracy is required and an example approach is
given below for the runs on a particular route.
A total of twelve measurement lines were completed between DD/MM/YY and
DD/MM/YY with the following accuracies being achieved.
Overview of the standard deviations for plan position as shown in example below;
Example
- Amount of points with a standard deviation XY less than 0.010m: 141194 (95.4%).
- Average standard deviation XY 0.005m.
Overview of the standard deviations for elevation
- Amount of points with a standard deviation Z less than 0.010m: 101804 (68.8%).
- Average standard deviation Z 0.011m.
Number of points with a standard deviation cant smaller or equal to 3mm: 146187 (98.7%). Average
standard deviation cant 0.2mm.
Where adjacent tracks are fixed together using an additional data source, e.g. a 360 degree laser
scanner, the track distance correction range applied is given:
After track distance correction:
- Corrections Z are -0.001 +/- 0.024m.
- Corrections XY are 0.000 +/- 0.008m.
Standard Deviations after correction are 0.005m in XY and 0.011m in Z.
360 scanner processing
The methodology should be explained but will vary depending on the deliverables
required from the survey.
Page 70 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
NOTE 1: An example is given here when using RILA 360.

At the outset, a trajectory for the survey run, through the combination of the GNSS
receiver and the inertial measurement unit data streams, will be computed using the
scan data only.
For gauging requirements, the scan profiles are then shifted to the trajectory using
time stamps and the known offsets from the calculated trajectory line.
The quality management shall be explained in summary form.
Having got the RILA 360 track alignment, this is then matched with the RILA Track
alignment (held fixed) to provide a single consistent dataset.
360 scanner accuracy statements
Relative accuracy is calculated with respect to the separately measured and
computed track alignment during the matching process combining track alignment
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
from track measurement system and 360 scanning system.
Absolute accuracy takes into account the standard deviation of the 360 scan data to
give an indication of the global accuracy of the trajectory.
NOTE 2: An example of a table giving RILA 360 accuracy is given below.
Relative XY (mm) Z(mm)
Minimum shift 0 0
Maximum shift 101 58
Average shift 4 4
St dev 4 4
Absolute XY (mm) Z(mm)
St dev 6 13
Table E-1 – RILA 360 accuracy
Page 71 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Quality Assurance
Explain the quality assurance approach that is taken with specific rail features such
as:
• Switch toe details including numbers, crossing noses and knuckles of S&C
with type (i.e. C11 this information is usually found on the side of the crossing
unit and for switches on the heel blocks) are noted and annotated.
• Where differential cant exists between the through line and turn-out, this is
indicated by “2L” being written on the base plate known as “two-levelling”).
The positions should be surveyed and noted at each base plate location.
• Welds and type.
• Transition rails (UIC 60E1/UIC60ER to 113A/UIC 56E1, etc.).
• Position of twist on twist rails (indicating inclined and vertical).
• Cable troughs, cable runs and pits (including within the four-foot: UTX, depth
and size).
• If the extent of the relaying is known then the height of the rail is to be found
using rail callipers so that the appropriate lift fishplates can be provided –
height between top of sleeper and bottom of rail.
• Switch heater units, including type, (gas, electric, strip, cartridge, or pad) as
applicable and controls (including all cubicles and transformers and their
identification numbers.
Lessons learned
Include any comments on the specification and results along with recommendations
for future work of this nature.
Deliverables
This should be an explanation of how the deliverables have been derived if not
included in the Methodology and a listing of what has been delivered.
A typical example is given below of required data extraction that may be by route
section and mileage or by structure. This may be provided in an appendix.
Page 72 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Required data extraction by section and mileage

A.1 - Data required by section and mileage
A.2 - Structure list and requirements
• Standard Deviation report as part of the alignment deliverable file, with

reference to a chainage/mileage location, so that poor SD locations can be
easily identified.
• *.krdz file (RILA Track) or a *.csv file. These formats are both ASCII (text)
files, with explanation of what is represented in the columns and the delimiter.
• Quality assurance notes for abstracted features
• Quality assurance checks for point cloud ‘ghosting’ issues, particularly in 3-4
track areas where multiple point clouds are integrated.
Page 73 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Deliverables to include;
• *LAS and *POD files in survey grid defined in specification:
• Both *.LAS and *.POD files need to be delivered in manageable sizes.
200x200m tiles give average POD size files of 1-2GB, depending on terrain.
• HD video (ran in daylight hours).
• RGB data (again if possible to capture in daylight hours).
• ScO gauging files (if required).
• DGN model of rail alignment.
E.3 Aerial survey report template

NOTE 1: This is applicable to conventional aerial survey by fixed wing, helicopter of remotely piloted
aerial systems such as Drones of unattended aerial vehicles (UAV) collecting topographical data.
Further information about the use of UAVs can be found in NR/L2/TRK/3100/MOD03.
Introduction
This should include the extents and a summary of the technical requirements of the
aerial survey works including the datasets commissioned e.g. RGB vertical imagery
and any derived products e.g. digital elevation or digital surface models.
Programme
Include the dates of data capture, a summary of the planned and actual programme
of work and the delivery schedule.
difficulties encountered in completing the work, e.g. problems of accessing restricted
airspace, weather conditions etc.
Methodology
Include a brief description of technical principles including the sensors for data
capture for each type of dataset delivered.
A flow chart of the processing approach should be provided.
The survey grid and level datum used shall be included plus the names of any
Snakegrid and Ordnance Survey transformation model used.
Information relating to the Ground control points (GCP) and Ground control areas
(GCA) shall be provided.
Details of the co-ordinated points (GCP) used during the aerial photography
processing to orientate the 3D model to the actual ground shall be provided.
NOTE 2: These are points of detail on the ground which are visible in the imagery and are spaced
out along the area to be surveyed.
Page 74 of 76
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
A representation of these using background imagery should be provided along with a

co-ordinate schedule and witness diagrams.
The GCA is used as gross error check of LiDAR datasets and is comprised of
independently observed points on a flat hard metalled surface such as a car park.
These usually comprise of a 5m x 5m grid of points. A table detailing the fit between
the LiDAR data and the CGA is to be provided in terms of the average difference,
route mean square error and the standard deviation.
Examples shall be given of GCA using an imagery background.
A description of the Quality Assurance process shall be provided for all datasets.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
Page 75 of 76

OFFICIAL
Ref: NR/L2/TRK/3100
Issue: 5
Date: 02 March 2019
Appendix F - Data derived from terrestrial laser scanning

NOTE 1: Registered point clouds are the basic deliverable from laser scanned surveys. Point cloud
may also be delivered from aerial LiDAR surveys but the comments below are intended to address
ground based collection only.
Where laser scanning is used for surveying, a registered point cloud shall be a
deliverable.
Where RGB (Red Green Blue) colour registration is used, photographs may also be
included in the deliverables.
A topographical survey specification shall include all the following deliverables as
outputs from the 3D laser scan surveys:
NOTE 2: Items a) and b) imply the use of Leica Geosystem scanners and software but this does not
exclude the use of other manufacturers kit that can provide similar outputs which can be analysed in
in alternative manufacturer’s software.
a) registered point cloud data in Scanworld, combined and unified database
outputs. (*.IMP files);
NOTE 3: This can include RGB (colour) registration.
b) published scan clouds – including index file – in light intensity and/or colour
format. Published TruView images shall have an image resolution of 2048 
2048 with an encoding error at 200 m of 0.04 m;
c) POD formatted pointcloud (Bentley native point cloud format enabling usage
direct in Bentley suite of software).
In addition one of the following may be required:
I. 3D Wire frame model: a 3D CAD model that simply uses line work to produce
a framework (e.g. the outline of the side of a cube);
II. 3D Surface model: joining lines in a series of blocks to define surfaces e.g. all
the surfaces of a cube given and linked to one another;
NOTE 4: This should allow sections and simple floor plans to be constructed.
III. 3D Surface plus model: as with ii) but with the addition of main features such
as doorways, windows, main structural members;
IV. 3D Solid Model: the level of detail and accuracy of model in relation to
surveyed features should be determined on a project by project basis and
location by location where appropriate.
NOTE 6: Solid models are generally more appropriate for design work than as-built detail.
For further guidance on modelling scan data that is appropriate for BIM usage refer
to the Survey4BIM Digital plan of works and the further outputs from the Survey4BIM
task group especially related to “Level of detail” and the other Big 5 Challenges such
as Accuracy, Interoperability, Metadata and Generalisation.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
During the lifetime of this document significant survey industry outputs will explain
these in more detail.
Page 76 of 76

Standard and control document briefing note
Ref: NR/L2/TRK/3100 Issue: 5
Title: Topographic, engineering, land and measured building surveying – Strategy and general
Publication date: 02 March 2019 Compliance Date: 01 June 2019
Standard/Control Document Owner: Professional Head of Track
Non-compliance rep (Approver of TRACKER applications): Chris Preston, Senior Engineer, STE
Technical lead/contact for briefings: Chris Preston, Senior Engineer Tel: 07515 627050
Purpose: Scope:
The standard sets out requirements for the project manager and This is the main document that provides a strategy and general
engineer to specify topographic survey work, by identifying key introduction, establishing some basic principles to be applied
stages to deliver good quality work for current and future needs. across all disciplines. Other documents covering the main
This lowers the risks associated with poor survey work for disciplines, in the previous suite of standards, are now included as
projects. “Survey once and use many times” also provides better modules.
value for the money spent. It is for the use of Project Managers, Designated Project
Engineers (DPE) or project teams, in consultation with a
geospatial engineer (Client’s Survey Manager).
The standard also explains how an appropriate topographic
survey forms the basis of BIM by reference to the Survey4BIM
Digital plan of works and the various parts of PAS 1192 Parts 2 to
5.
This standard is intended to be used with the Module documents
associated with the discipline and related to the type of survey
required.
Overview of change
In general terms the main NR/L2/TRK/3100 document has been updated with Band 5 being removed from Table 4 and some of
Tables 4, 5 and 6 altered to include use of UAS/Drones and reflect changes to Module 5.
NR/L2/TRK/3100/MOD5 has been rationalised from NR/L3/TRK/3105, the main changes have been made in Clause 6. Addition of
updated, clearer Figures in Appendix C, C1 to C6 and C8 to C18 and Figures C2, C3, C9, C12, C13 and C15 showing UK Master
Series examples.
An update to form NR/L3/TRK/3105/SU504 (now NR/L2/TRK/3100/SU504).
Detail of change
Section(s)/clause(s) Summary of changes

NR/L2/TRK/3100
Table 4 Band 5 removed as DCS & NMT use relative positioning only rather than absolute co-ordinate
positioning.
Table 4 Reference made to UAS/Drones in Band 1 and Band 3 accuracy rows of table and also NOTE 4.
Table 5 Addition of NOTE 5 referring to NR/L2/TRK/3100/MOD5 Error! Reference source not found..
Table 6 RILA Track+Rila 360 replaced by RILA System 3 updated technology name.
Table 6 E.1.5 In notes column “Surveyors are trackside except where UAS/Drones used” has been added.
Table 6 E.2.1 In notes column “UAS/Drones could be used for as-built assurance where minimal obstructions,” has
been added
Appendix A Removed but previous version Appendix names have been left the same as significantly referenced
in other previously published documents.
NR/L2/TRK/3100/MOD5
7.4 Clause suggests that Any survey associated with OLE design shall also be related to the “Track
position strategy”, referenced in NR/L2/ELP/27715-05.
Additional items for consideration are also given in Clause 6.4 associated with surface type when
gauging is a consideration.
When a track survey is refreshed after 6 months to give confirmation of any changes so shall the
relationship to OLE wire.
There are changes to Table 1 Survey types and GRIP stages.
7.5 This includes mention of RILA System 3 for height and stagger surveys.
7.6 Clause has now included use of train borne video systems but requires that whole width of
structures and tracks are included in the images.
7.7 This clause on Portal Booms has been refreshed with further clarity and diagrams.
7.8 Measurement conventions have been made more explicit and a diagram provided.
7.9 Clarifies use of template cross sections where no existing diagrams available to record
measurements.
7.10 Clause on Tunnel and Bridge Profile Surveys has been updated diagrams. Survey form
NR/L3/TRK/3105/SU504 has been updated to Issue 2 to clarify the conventions to be used for
recording track curvature.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---
7.11
Copyright Network Rail Deliverables identified within the survey matrix in Appendix B have been updated.
9 Now highlights the fact that site inspections should be achieved using video and point cloud data
and that site walk-outs shall be a last resort after all other data sources are exhausted.
Appendix B Removed and replaced by Matrix of Survey requirements.
Appendix C New clearer diagrams Figures C1 to C6 and C8 to C18 have replaced previous ones.
UK Master series 1 diagrams added as Figures C2, C3, C9, C12, C13 and C15.
NR/L3/TRK/3105/SU504 Second last line on form has small change to “High rail
ISSUE 2: BRIDGE AND
TUNNEL PROFILE FORM
Reasons for change

The changes have been made to reflect practices now becoming the norm within current projects within NR/L2/TRK/3100 and in
Module 5 for electrification projects allowing projects more flexibility to define their requirements.
Affected documents:
Reference Impact
NR/L3/TRK/3105/SU504 ISSUE 1 Superseded
NR/L2/TRK/3100 ISSUE 4 Superseded
NR/L3/TRK/3105 ISSUE 1 Withdrawn
NR/L2/TRK/3100/MOD05 ISSUE 1 New
NR/L3/TRK/3105/SU504 ISSUE 1 Withdrawn
NR/L2/TRK/3105/SU504 ISSUE 1 New
Briefing requirements:
Will Briefing Management System be used to deliver the briefing to posts listed below? No
Technical briefings are given to those who have specific responsibilities within this standard/control document.
Awareness briefings are given to those who might be affected by the content but have no specific responsibilities within the standard/control document.
Details of the briefing arrangements are included in the associated briefing programme.
All posts identified for briefing must be as described in OrgPlus.
Briefing Post Responsible for

(A-Awareness/ Function cascade briefing?
T-Technical) Y/N
A Route Asset Manager [E&P] Route Businesses Y
A Route Asset Manager [Track] Route Businesses N
A E&P Maintenance Engineer Route Businesses N
T Principal Design Engineer [E&P] All functions Y
T Senior Design Engineer [E&P] All functions N
T Design Engineer [E&P] All functions N
T Senior Project Engineer [E&P] All functions Y
A Principal Design Engineer [Track] All functions N
A Senior Design Engineer [Track] All functions N
A Design Engineer [Track] All functions N
A Senior Project Engineer [Track] All functions N
T Senior Design Engineer [Civils] Infrastructure Projects Y
T Senior Project Engineer [Civils] Infrastructure Projects Y
A Programme Engineering Manager [Track] Infrastructure Projects N
T Principal Design Engineer (HO) Infrastructure Projects Y
A Project Manager Infrastructure Projects N
T Project Engineer [E&P] Infrastructure Projects N
A Programme Manager Infrastructure Projects N
Route Businesses, Works
A
Programme Manager Delivery N
NOTE: Contractors are responsible for arranging and undertaking their own Technical and Awareness Briefings in accordance with their own processes
and procedures.
--```,,`,`,`,,,``,```,,`,,,,``,,-`-`,,`,,`,`,,`---


Ne L2 TRK 3100

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

Ne L2 TRK 3100

Uploaded by

Copyright:

Available Formats

Network Rail Standards

The following information is associated with Network Rail Standard:

Additional Content Access

IHS Additional Content Page

Copyright Network Rail

Information for users

Copyright Network Rail

Topographic, engineering, land and measured

Approved for publication by:

~ ... .... ...... .. ....·~

John Winn ifrith,

Uncontrolled copy once printed from its electronic source.

Copyright Network Rail

Red requirements – no variations permitted

Amber requirements – variations permitted subject to approved risk analysis

Copyright Network Rail

Copies of standards/control documents are available electronically, within Network

Issue Date Comments

3 September 2017 Minor errors in Issue 2 updated

4 December 2017 Cover sheet updated. Table 1 updated with

5 March 2019 Table 1 updated with NR/L3/TRK/3105

NR/L1/INI/CP1010 Policy on working safely in the vicinity of buried

NR/L2/INI/CP1030 Working safely in the vicinity of buried services

NR/L2/INI/EDT/CP0091 Specification for Computer Aided Design

NR/L3/MTC/PL0094 Planning and documenting the Safe System Of

NR/L2/INI/02009 Engineering Management for Projects

NR/L2/ELP/21088 General Maintenance Parameters for Overhead

NR/L2/TRK/2102 Design and Construction of Track

Benchmarks to GNSS heighting RICS (Royal Institution of Chartered Surveyors)

BS 1192:2007 Collaborative production of architectural,

engineering and construction information– Code

PAS 1192-2:2013, Specification for information management for

PAS 1192-3:2014 Specification for information management for

PAS 1192-5:2015 Collaborative production of information. Fulfilling

PAS 1192-5:2015 Specification for security-minded building

Survey4BIM, Digital plan of works (DPOW)

10.2.7 Accuracy and adjustment of horizontal and vertical PGMs ............................ 37

Figure B-5 – Example of Type 4 PGM in OLE mast base ........................................ 56

Copyright Network Rail

Module Number Title Issue Date

01 Track surveying (formerly 2 Sept 2017

02 Civils and Buildings - Not written

03 Survey and mapping techniques guidance 2 Sept 2017

04 Asset data extraction & Topographic 1 Dec 2017

05 Topographic, engineering, land and 1 Mar 2019

Table 1 – NR/L2/TRK/3100 modules

Building information modelling

Copyright Network Rail

Copyright Network Rail

Copyright Network Rail

Terrestrial Laser Scanning

Track measuring device

TMG/spigot/stud Track machine guidance points

Copyright Network Rail

Scan point cloud publishing software

5 Roles and responsibilities

Client’s Survey Manager (CSM)

Contractor’s Engineering Manager (CEM)

Contractors Responsible Engineer (CRE)

Designated Project Engineer (DPE)

Project Engineer (PE)

Copyright Network Rail

Project Information Manager