Digital Railway Operations and Maintenance Rules and Standards Frameworkdigitalrailway.co.uk/.../04/...O-M-Rules-and-Standards-Framework-v1.0… · ENs European Standards ITT Invitation

Reference 158875-NWR-PLN-OPP-000002

Issue/Ver: 1.0

Date: 28/03/2019

Digital Railway – Operations and Maintenance Rules and Standards Framework

Prepared by: Justin Monk Senior Operations Interface Manager JM-280319-0003 Date: 28/03/2019 Reviewed by: David Nicholson System Integration and Interface Manager DJN-29032019-0100

Date:29/03/2019

Approved by: Rubina Greenwood Head of System Requirements and Integration RNG-290319-0092 Date: 29/03/2019

Page 2 of 98


Issue/Ver: 1.0

Date: 28/03/2019

Electronic file reference: https://digitalrailway.ipss-

hdms.co.uk/DigitalRail/Search/QuickLink.aspx?n=158875-NWR-PLN-OPP-

000002&t=3&d=Main%5cDIGITAL-RAIL-Production&sc=Global&r=01&i=view

Disclaimer

Group Digital Railway has used its best endeavours to ensure that the content, layout and text of this document are accurate, complete and suitable for its stated purpose. It makes no warranties, expressed or implied, that compliance with the contents of this document will be sufficient to ensure safe systems of work or operation. Group Digital Railway will not be liable to pay compensation in respect of the content or subsequent use of this document for any purpose other than its stated purpose or for any purpose other than that for which it was prepared, except where it can be shown to have acted in bad faith or there has been wilful default.

© Copyright 2019 Group Digital Railway.

This document is the property of Group Digital Railway. It shall not be reproduced in whole or in part without the written permission of Group Digital Railway.

Document owner: Rubina Greenwood, Head of System Requirements and Integration

Version History

Issue Date Comments

0.1 28/02/2019 1st draft issued for Level 0 review

0.2 05/03/2019 Updated to address Level 0 review comments

0.3 06/03/2019 Issued for Level 1 review

0.4 26/03/2019 Updated to address Level 1 review comments

1.0 28/03/2019 Issued for publication

Exclusions

These are items currently missing from this version of the document that should be included in a later publication.

None

Assumptions

These are items upon which the validity of this document relies, and which will be delivered by others. Non-delivery of these items will necessitate a change to this document.

None

Dependencies

These are items upon which the validity of this document depends. Any changes to the referenced document may require further changes to this document.

• The Standards reviewed in this framework, released by the RSSB, were as per the version issued at 1st December 2018 – RGS Catalogue Dec 2018.

https://digitalrailway.ipss-hdms.co.uk/DigitalRail/Search/QuickLink.aspx?n=158875-NWR-PLN-OPP-000002&t=3&d=Main%5cDIGITAL-RAIL-Production&sc=Global&r=01&i=view



Page 3 of 98


Issue/Ver: 1.0

Date: 28/03/2019

Content

ABBREVIATIONS AND GLOSSARY ...................................................................................................... 4

REFERENCES ........................................................................................................................................ 5

1 INTRODUCTION ........................................................................................................................... 6

1.1 Background ............................................................................................................................... 6

1.2 Purpose .................................................................................................................................... 7

1.3 Scope ........................................................................................................................................ 7

1.4 Document maintenance ............................................................................................................ 7

2 EXISTING NATIONALLY-APPLICABLE RULES AND STANDARDS IN THE RAILWAY INDUSTRY

2.1 Overview ................................................................................................................................... 9

2.2 National Operations Publications ............................................................................................. 9

2.3 Standards ............................................................................................................................... 10

2.4 Code & Strategies ................................................................................................................... 10

2.5 Other Organisations’ Documents ........................................................................................... 10

2.6 Signs ....................................................................................................................................... 11

3 METHODOLOGY: REVIEW PROCESSES AND APPROACH TAKEN ..................................... 12

3.1 Pre–work ................................................................................................................................. 12

3.2 Rules and Standards Reviewing Exercise ............................................................................. 13

3.3 BoD Review Exercise ............................................................................................................. 14

3.4 JDG Comparison Exercise ..................................................................................................... 15

4 REVIEW OUTCOMES ................................................................................................................ 17

4.1 Summary of Rules and Standards Review Outcomes ........................................................... 17

4.2 Summary of Comparison with JDG’s Review Work ............................................................... 18

4.3 Summary of Comparison of BoD Scenarios with Rules and Standards ................................ 18

4.4 Overall Result Summary ......................................................................................................... 18

5 ROADMAP FOR THE DEVELOPMENT OF NATIONALLY-APPLICABLE RULES, STANDARDS AND PROCESSES ........................................................................................................ 20

5.1 Standards Revision and Development Work .......................................................................... 20

5.2 Roadmap ................................................................................................................................ 20

6 CONCLUSIONS AND RECOMMENDATIONS ........................................................................... 21

7 APPENDIX A: RULES AND STANDARDS REVIEWING OUTCOMES ..................................... 22

8 APPENDIX B: BOD REVIEW OUTCOMES ................................................................................ 83

Page 4 of 98


Issue/Ver: 1.0

Date: 28/03/2019

Abbreviations and glossary

Abbreviations are explained in full on first use within this document. A comprehensive list of abbreviations and definitions is contained in the Glossary [RI1]. Here is the list of abbreviations and glossary which have not been included in the Glossary [RI1].

Abbreviation Description

ATOC Association of Train Operating Company

DUPs Driver User Procedures

ENs European Standards

ITT Invitation to Tender

JDG Joint Development Group

M&EE NG Mechanical and Electrical Engineers Network Group

NSRs National Safety Rules

PoSA Proceed on Sight Authority

PQQ Pre-Qualification Questionnaire

Page 5 of 98


Issue/Ver: 1.0

Date: 28/03/2019

Dependent References

An update to one of these references requires an update to this document.

RD1 Digital Railway Requirements Framework, 153819-NWR-PLN-ESE-000011, v2.0

RD2 Digital Railway Programme – System Management Plan, 153819-NWR-PLN-MPM-000002, v8.0

RD3 Digital Railway – GB Generic Customer Requirements Specification for Operations and Maintenance, 153819-NWR-PLN-ESE-000014, v2.0

RD4 Not used

RD5 Digital Railway - SoS Basis of Design, 153819-NWR-REP-ESE-000002, V2.3

RD6 Digital Railway – Integrated Concept of Operations, 000000-NWR-PLN-MPM-000005, v1.0

RD7 RGS Catalogue Dec 2018, RSSB

RD8 Engineering Rules Gap Analysis and Impact Assessment Report, 147883-NWR-REP-CPO-000001, v1.0

RD9 Generic Outcome-based Business Requirements for Digital Railway Technologies, 000000-NWR-MAN-000002, v1.1

RD10 Digital Railway Strategy, v1.0

RD11 Digital Railway – System of Systems (SoS) System Definition, 153821-NWR-REP-ESE-000002, v5.0

RD12 RGSC03 – An Industry Strategy for Standards 2016- 2019, Iss 1

RD13 Standards Manual - Managing standards for the mainline railway system, Iss 3

RD14 SoS Architecture v5.0, 153819-NWR-DRG-ESE-000003, v5.0

Informative References

These references have no material bearing on the content of this document but are referenced within it. Unless otherwise specified, reference should be made to the latest version of the documents.

RI1 Digital Railway – Glossary of Terms & Abbreviations, 153819-NWR-SPE-ESE-000001

Page 6 of 98


Issue/Ver: 1.0

Date: 28/03/2019

1 Introduction

Digital Railway (DR) is a rail industry-wide initiative designed to benefit Great Britain’s economy through more effective train operation, customer experience and industry adaptability, enabled by accelerating the application of digital technologies to the railway. Background to the Digital Railway can be found in more detail in the Digital Railway System Management Plan [RD2] and the Digital Railway System of Systems System Definition Document (SoS SDD) [RD11]. The benefits of a Digital Railway are captured in the Generic Outcome-based Business Requirements for Digital Railway Technologies [RD9].

Requirements for Digital Railway (DR) technologies are expected to form part of contracts for Deployment Projects. Pre-Qualification Questionnaires (PQQs) and Invitations to Tender (ITTs) for some Deployment Projects have already been issued. The System Requirements & Integration (SR&I) Team has been remitted to produce the necessary Customer and Digital Railway Requirements for these projects to use. They have developed a suite of requirements documentation which is outlined in the Digital Railway Requirements Framework [RD1] and discussed in detail in the Digital Railway System Management Plan [RD2]. Figure 1, which is extracted from [RD1], shows the high-level structure of the suite of requirements.

Figure 1 Structure of SR&I Suite of Requirements

Operations and Maintenance (O&M) is one of the core component systems of the SoS. The Digital Railway Operations and Maintenance Customer Requirements Specification [RD3] was produced and published in November 2018. Feedback from some of the early deployments has highlighted an urgent need for clarity on changes that will be needed to the rail industry’s Rules and Standards both to support DR deployments and ensure national compatibility.

Page 7 of 98


Issue/Ver: 1.0

Date: 28/03/2019

The introduction of Digital Railway systems will fundamentally change the way that the GB Railway is operated and maintained. Some of the changes that will be introduced will result in changes to nationally-applicable Rules and Standards in order for there to be consistency of operations, rules and driving experience across different deployment areas. Some of those changes will be deployment-specific and result in local changes to Rules and Standards. However, it is critical that operations should be as consistent as possible to provide for a railway that can be safely operated without changes in practice across deployment boundaries.

This Operations and Maintenance Rules and Standards Framework has been produced to support Deployment Projects by identifying those areas of national- applicable Rules and Standards that need to be reviewed in more detail with a view to initiating a change activity.

The scope of nationally-applicable Rules and Standards is broad. Recognising the importance of Deployment Projects having clarity over the areas of change in nationally-applicable Rules and Standards in order to design their deployment model, it was agreed that a high-level review of National Rules and Standards should provide initial input to Deployment Projects by the end of CP5. This Rules and Standards framework captures the outcomes of that review and provides recommendations for more detailed reviews, as well as potential revision of some of the Rules and Standards following closely in CP6.

The scope of this framework addresses only those nationally-applicable Rules and Standards by reviewing the following areas:

• existing National Operations Publications, Rail Industry Standards, Railway Group Standards and supporting documents (including Code & Strategies, Other Organisations’ Documents, and Signs) as per the version published 1st Dec 2018 by the Rail Safety and Standards Board (RSSB) [RD7] - to identify potential changes required; and

• the scenarios in the Digital Railway SoS Basis of Design (BoD) [RD5] - to identify the potential need for new Rules or Standards.

This framework does not review those Rules and Standards which are managed and updated locally, for example, Network Rail Company Standards.

This Framework focuses on three key areas:

• It provides a high-level overview and roadmap showing the areas of existing nationally-applicable Rules and Standards that are likely to be impacted by the introduction of DR technologies.

• It provides the likely timescales by which more detailed guidance on those potential changes can be provided.

• It identifies areas in which potential new Rules and Standards may need to be introduced.

This document is owned by the Head of System Requirements and Integration within the Digital Railway Programme (DRP).

It is envisaged that the following criteria will be used to support the impact assessment of the proposed changes with a view to determining whether any proposed change should be implemented:

• The ability of the proposed changes to meet the business needs of the GB railway;

Page 8 of 98


Issue/Ver: 1.0

Date: 28/03/2019

• The ability of the proposed changes to realise the vision set out in the Concept of Operations (ConOps) [RD6];

• Technical and operational compatibility with deployment projects procured against an earlier version of this document; and

• The ability for the supplier to be innovative.

Page 9 of 98


Issue/Ver: 1.0

Date: 28/03/2019

2 Existing Nationally-Applicable Rules and Standards in the Railway Industry

In developing this Rules and Standards framework, it was first important to identify the full range of available Rules and Standards for consideration prior to selecting those elements which are both nationally-applicable and able to be influenced by the DRP. A rule or standard is an agreed way of doing something. Currently, there are seven strategic modules identified by the RSSB in their Industry Strategy for Standards [RD12]:

• National Technical Rules (Railway Group Standards)

• National Safety Rules (Railway Group Standards)

• National Operations Publications

• Rail Industry Standards

• Technical Specifications for Interoperability (TSIs)

• British, European and International Standards

• Company and Project Standards

As a result of Digital Railway technologies implementation, most standards within those seven strategic modules will be impacted subject to technical assessments by various parties. This review has focused on Standards at the GB railway system level with mandatory compliance, which include:

• Railway Group Standards;

• Rail Industry Standards, and

• National Operations Publications.

The Digital Railway Programme does not have the ability to influence directly TSIs, British, European and International Standards, or Company- and Project-Specific Standards, and so this review has not addressed these documents.

In addition, further investigation reveals that the Standards at GB railway system level are made of five main categories within the Standards Catalogue Version of Dec 2018 downloaded from the RSSB website [RD7]:

• National Operations Publications

• Standards (including Railway Group Standards and Rail Industry Standards)

• Code & Strategies

• Other Organisations’ Documents

• Signs

The review outcome was structured by adopting these five categories and further detail on their relevance and purpose is given in the next section.

The National Operations Publications comprise the Rule Book, the White Pages (the Working Manual for Rail Staff: Freight Train Operations (GO/RT3056)) and the Pink Pages (the Working Manual for Rail Staff: Handling and Carriage of Dangerous Goods (GO/RT3053)).

• The Rule Book is the best-known National Operations Publication. It consists of three types of documents: o Modules containing instructions for front-line operating personnel (e.g. drivers, signallers

and shunters) which apply across the mainline network and are designed to manage safety across the interface between Railway Undertakings (RUs) and the Infrastructure Manager (IM). Modules are relevant to both RU and IM staff.

Page 10 of 98


Issue/Ver: 1.0

Date: 28/03/2019

o Handbooks containing instructions that are carried out by personnel holding competencies in relation to staff protection, engineering activity or operation of equipment.

o Forms which are supplementary documents in support of modules and handbooks, and which provide structured templates for users.

• The White Pages is used by all staff concerned with the acceptance, planning, handling, conveyance, marshalling, and movement of freight traffic.

• The Pink Pages is used by all staff concerned with the classification, acceptance, identification, marshalling, movement, and loading of dangerous goods.

Within the Standards, there are six main sub-categories:

• Railway Group Standards (RGSs) include National Technical Rules (NTRs) and National Safety Rules (NSRs): o NTRs are those Rules (Standards) which, amongst other things, the Interoperability

Directive requires each Member State to promulgate in the absence of a Technical Specification for Interoperability (TSI) requirement (for further information, see: https://www.rssb.co.uk/standards-and-the-rail-industry/standards-explained/national-technical-rules).

o NSRs are common railway safety requirements that are imposed by the government and regulator on those operating the railway.

• Rail Industry Standards (RISs) are developed collectively by the Industry, facilitated by the RSSB, and are, therefore, an efficient way of producing standards that companies can adopt as their own standards. RISs define functional or technical requirements to be met in circumstances where Railway Group Standards are not necessary for the management of the railway system. RISs are railway-specific standards: they contain requirements applicable to sub-systems, or they set out rules about how sub-systems should be operated or managed. They compensate for the absence of an industry-wide deviations process, providing an appropriate and necessary level of standardisation for requirements not within the scope of NTRs or NSRs.

• Guidance Notes are documents produced under the procedures set out in the Manual [RD13]; they provide helpful information relating to the management and/or operation of the railway system and its sub-systems.

• Codes of Practice are documents that define agreed and sufficient means (but not the only means) of meeting identified sets of mandatory requirements within RGSs.

• Good Practice Guidance details recognised good practice for use by Railway Undertakings. Such guidance complements RGSs and covers both engineering and operations topics.

• RGS Forms are documents which support the usage of Railway Groups Standards.

Code and Strategy documents published by the RSSB set up strategic directions for the future development of Standards for various areas, such as the European Railway Traffic Management System (ERTMS).

These documents are published by the RSSB on behalf of other organisations, such as the Association of Train Operating Companies (ATOC) and the Mechanical and Electrical Engineers’ Network Group (M&EE NG).

Page 11 of 98


Issue/Ver: 1.0

Date: 28/03/2019

These documents provide design details for the layout of lineside operational and lineside safety signs. Their use is generally mandated in another subject-specific standard.

Page 12 of 98


Issue/Ver: 1.0

Date: 28/03/2019

3 Methodology: Review Processes and Approach Taken

An approach of reviewing and initiating revision of nationally-applicable Rules and Standards, when combined with the application of DR CRSs and DRRs, will help to ensure interoperability in both systems and processes.

A Deployment Project may involve changes to both trackside infrastructure and on-board systems necessary to achieve a successful deployment of DR technologies. Alternatively, some Deployment Projects may choose only to install some of the technologies on offer, for example, only implementing the European Train Control System (ETCS).

To ensure that the various potential deployment combinations were considered by this review, the remit required the development of requirements and support for the Digital Railway systems as given in the SoS SDD [RD11] and summarised below:

• Integrated Traffic Management System (TMS)

• ETCS without lineside signals - both Trackside and Onboard elements

• Connected Driver Advisory System (C-DAS)

• Various enabling systems, e.g. Telecoms, Linked Information Exchange (LINX), Key Management System (KMS); those enabling systems, however, were not part of the scope of this review.

This framework addresses the SoS deliverables and the DR technologies, but only in the context of the Rules and Standards for Operations & Maintenance (O&M). In order to provide the maximum benefit for the Deployment Projects, the impact on O&M Rules of each of the technologies has been considered separately, so that Deployment Projects can see where their deployment configuration will impact O&M Rules. There are many more deliverables, and these are set out in the System Management Plan [RD2].

The review process is shown in Figure 2:

Figure 2 Rule and Standards Review Process

Table 1 Magnitude of the Standards

Catalogue Total # Total Pages #

NATIONAL OPERATIONS PUBLICATIONS 110 8,318

STANDARDS 211 8,693

Code of Practice 7 154

Good Practice Guide 4 406

Guidance Note 55 2,467

Rail Industry Standard 94 4,337

RGS Form 10 76

Standard 41 1,253

CODE & STRATEGIES 15 552

Code ＆ Manual 2 84

Strategy 13 468

OTHER ORGANISATION DOCUMENTS 129 2,328

SIGNS 133 133

Grand Total 598 20,024

Page 13 of 98


Issue/Ver: 1.0

Date: 28/03/2019

An initial analysis of the document types and their magnitude was conducted to understand the scope of the reviewing exercise. As shown in Table 1, there were 598 documents across the Standards Catalogue [RD7], comprising 20,024 pages in total.

A standardised reviewing approach was introduced and involved answering the questions in Table 2. The purpose of those questions was to assess the relevance of the DR technology implementations, to estimate the timescale of changes for each document, and to explain the purpose of the changes. Detailed assessment of the intent of each question is further explained in Table 2.

This review was carried out by Subject Matter Experts (SMEs) in the DRP SR&I O&M Team with an operational and maintenance background and addressed: planning, signalling operation, train operation, and operational maintenance. All SMEs had direct working experience with operations. The entire catalogue of Standards was allocated to individuals within the team; however, where discussion with other SMEs was required, it was requested and tracked. Finally, a Level 0 review was carried out to provide assurance. This review activity was to identify any need for more detailed review and potential changes to existing Rules and Standards.

Table 2 Exam Questions for Standards Reviewing Exercise

Systems Questions Assessment Expected value

ETCS

Are there any changes required for ETCS deployment?

To assess whether the existing content of the document needs to be changed if ETCS is deployed.

"Y" or "N"

If so, what is the estimated scale of changes required?

To assess the timescale/effort required for potential changes. This is based on the % change of pages divided by the total pages in the document. If less than 50%, it will be a minor change. If greater than, or equal to, 50%, it is categorised as a major change.

N/A, Minor or Major

Are any new topics required for ETCS deployment?

To assess whether new topics will need to be added to the document if ETCS is deployed.

"Y" or "N"

TMS

Are there any changes required for TMS deployment?

To assess whether the existing content of the document needs to be changed if TMS is deployed.

"Y" or "N"


To assess the timescale/effort required for potential changes. This is based on the % change of pages divided by the total pages in the document. If less than 50%, it will be a minor change. If greater than, or equal to, 50%, it is categorised as a major change.

N/A, Minor or Major

Are any new topics required for TMS deployment?

To assess whether new topics will need to be added to the document if TMS is deployed.

"Y" or "N"

C-DAS

Are there any changes required for C-DAS deployment?

To assess whether the existing content of the document needs to be changed if C-DAS is deployed.

"Y" or "N"


To assess the timescale/effort required for potential changes. This is based on the % change of pages divided by the total pages in the document. If less than 50%, it will be a

N/A, Minor or Major

Page 14 of 98


Issue/Ver: 1.0

Date: 28/03/2019

Systems Questions Assessment Expected value

minor change. If greater than, or equal to, 50%, it is categorised as a major change.

Are any new topics required for C-DAS deployment?

To assess whether new topics will need to be added to the document if C-DAS is deployed.

"Y" or "N"

SoS Why are changes required?

To explain the reasoning supporting the changes under four headings: General (generic comments on the document, where thought relevant), ETCS, TMS, and C-DAS.

Statement of justifications

Each reviewer carried out their own independent assessment of their allocated set of documents, based on their experience and knowledge, by answering the questions in Table 2. Discussions with other team members and/or Lead Architects who had domain knowledge were facilitated to enable a judgement to be made. Review outcomes are summarised in Section 4 and fully documented in Appendix A.

The DRP is using the Enterprise Architecture (EA) formal methodology as a means of modelling those elements of the rail network impacted by the introduction of Digital Railway technologies as a set of capabilities that provide the rail service. The DRP SR&I team have employed EA as one of their systems engineering activities due to the complex relationships between entities (which are all linked by the common goal of providing a rail service). To support the EA activity, specific scenarios were identified as being critical to the normal operation of the railway. These scenarios were expanded upon by industry SMEs in a series of workshops. This resulted in a scenario diagram depicting how the rail system should operate. The scenarios are captured in the BoD [RD5]. The following scenarios were reviewed in this framework:

• Operate Network to the Current Plan • Safely Command a Train • Provide Information to Signaller • Interface with Adjacent non-Digital Railway Control Systems • Train Preparation • Manage Train Service Information • Safely Operate the Train • Provide Information to Driver • Optimise Train Movement • Identify Train and Location (Infrastructure) • Identify Train and Location (Onboard) • Monitor Train Movements against Current Plan • Manage Incidents • Manage Crew and Stock Information • Optimise Current Plan • Safe Working Site Warning • Possessions Planning • Manage Possession • Short Notice Possessions • Control, Command & Signalling (CCS) Failure • Control Centre Failure • Emergency • Infrastructure Fault • Train-Based Fault • Monitor Digital Railway Health • What-if Analysis

Page 15 of 98


Issue/Ver: 1.0

Date: 28/03/2019

• Provide Information to Planning • Train Dispatch and • Transfer Signalling Control.

The reviewing team reviewed each scenario and its sub-scenarios to identify any new additions required to Rules and Standards; the outcomes are documented in Appendix B.

Part-way through this review exercise of existing Rules and Standards, it became apparent that a similar piece of work with an overlapping scope had already been completed by the Joint Development Group (JDG), and a report produced with their findings and recommendations [RD8]. The authors of that report were a group of SMEs with a mainly engineering competence set.

This high-level review exercise was carried out by SMEs with an operational background and addressed: planning, signalling operation, train operations, and operational maintenance. As such, although there are overlaps in scope, it is likely that this review brings a different perspective to the JDG review.

The Joint Development Group (JDG) Engineering Rules Gap Analysis and Impact Assessment Report [RD8] focused on (the scope was extracted from the report):

• reviewing all Network Rail CCS Standards, including their content and clauses;

• undertaking a GAP analysis/impact assessment of all current Network Rail CCS Standards impacted by the introduction of Digital Railway technologies;

• providing a definition of the Standards applicable to DR schemes with respect to the DR technologies;

• identifying conflicts and requirements for deviation; and

• reviewing all process and engineering management Standards currently undertaken in the delivery and assurance of conventional CCS projects.

The following publications were reviewed:

• All Railway Group Standards and Guidance Notes;

• All Rule Book Modules;

• All Railway Industry Standards and Industry Good Practice Guides;

• All Industry Codes of Practice;

• All Network Rail Company Standards listed in the Network Rail preliminary assessment; and

• All Network Rail Company Standards published after 02/10/2015 (the date that the preliminary assessment was carried out).

A comparison analysis of the scope of both exercises was undertaken as per Figure 3.

Figure 3 Scope comparison between this framework and JDG's work

Page 16 of 98


Issue/Ver: 1.0

Date: 28/03/2019

For the area of overlap, a comparison analysis was carried out on the outcomes of the two reviews. This comparison was used to provide a level of assurance that both results were valid. It resulted in the following actions:

• In the case where the two studies agreed, no further action was taken.

• Where the two studies had different outcomes, the findings were revisited, and views were clarified. This resulted in some changes, but some discrepancies remain.

The final review outcomes were updated and are documented in Appendix A.

Page 17 of 98


Issue/Ver: 1.0

Date: 28/03/2019

4 Review Outcomes

By following the review process described in Section 0, 598 documents in total were reviewed from the 1st Dec 2018 version downloaded from the RSSB website. The outcome of the review is summarised below from the statistics of the results set out in Table 3. These are given as:

• The Rules and Standards Review statistics for each of the primary systems: ETCS, TMS and C-DAS;

• Comparison with the outcomes of the JDG review placed into the context of these results;

• Description of the BoD review; and

• An overall summary.

ETCS:

• The study has highlighted that 113 (19%) documents require further review and updating for the purpose of ETCS deployment, of which 70 (12%) are estimated to need minor update and 43 (7%) are estimated to need major update.

• National Operations Publications require major overhaul to support ETCS deployment, especially, the Rule Book Modules and Manuals. Seven out of 26 handbooks also require further detailed review.

• Twenty-five out of 94 (27%) Rail Industry Standards require update, of which 20 (21%) are estimated to need minor update and five (5%) are estimated to need major update.

• Nine out of 41 (22%) Rail Group Standards require update, of which seven (17%) are estimated to need minor update and two (5%) are estimated to need major update.

• Some supporting documents, e.g. Guidance Notes (nine out of 55 (16%)) and RGS Forms (six out of 10 (60%)) are estimated to require considerable effort to update and so need further detailed review.

• It is worth mentioning that there is no need to review the Codes of Practice further as most of the documents in this category are recommendations for non-DR technologies which are outside of the scope of this work.

TMS:

• The results show that 38 (6%) of the same documents need to be modified for the purpose of TMS deployment, of which 24 (4%) are classed as requiring ‘minor update’ and 14 (2%) ‘major update’.

• As with the ETCS deployment, the National Operations Publications require a considerable amount of effort to update, especially some of the Rule Book Modules, e.g. RB Module: DC and RB Module: OTM.

• Seven out of 94 (7%) Rail Industry Standards require further minor update.

C-DAS:

• In addition, the results show that 33 (6%) of those documents need to be modified for the purpose of C-DAS deployment, of which 21 (4%) are classed as requiring ‘minor update’ and 12 (2%) ‘major update’.

• There are only a few documents 12 requiring major changes for the purpose of C-DAS deployment. This possibly reflects the fact that the current Standards do not address C-DAS functionality.

SoS:

Page 18 of 98


Issue/Ver: 1.0

Date: 28/03/2019

• From a GB Rail Industry perspective, for the purpose of deploying the Digital Railway System (made up of ETCS, TMS and C-DAS), this framework assessed that there are 183 (31%) documents requiring further detailed review, of which 65 are National Operations Publications, 109 are Standards, one is a Code and Strategy, six are Other Organisations’ Documents, and four are Signs.

• The review team considered there to be many examples where simply adding to or amending existing Rules or Standards could make communicating the concepts behind an entirely new digital railway difficult. As such, the industry should consider taking a step back and looking at options for restructuring the Rules and Standards to accommodate this scale of change in the best way.

• The review outcomes of the JDG comparisons exercise have been consolidated into the Rules and Standards review exercise documented at Appendix A, which shows strong alignment between the two reviews but, in some limited cases, different outcomes.

• The fact that the two exercises have not produced identical results is acceptable as their scopes of work were different and review teams had different experiences. It is of interest, however, that the high-level conclusions of the JDG’s work are similar to those of this work. Firstly, the amount of potential change is great, and secondly, it may be more efficient to consider the restructuring of existing and new documents to accommodate new technologies in the best way rather than adapting the existing ones.

• For the BoD review outcomes, see Appendix B. The conclusions of the BoD review do not generally propose any specific changes to an existing document because the purpose of this review was to identify potential areas where the existing Rules and Standards do not address some aspects of a DR implementation. As such, the manner in which such changes to the Rules and Standards are to be implemented has to be decided at an Industry level. For this reason, the BoD review has identified where the actions required will be subject to change but has deliberately not identified which documents would change.

• It is clear from all levels of this review (and the previous JDG review) that the scope of change required in the Rules and Standards framework is great, with c.31% of existing documentation requiring change. Additionally, to accommodate all the scenarios outlined in the BoD, additional Rules and Standards will be required which do not fit into the existing documentation.

• It is also clear that, with these identified changes, there is a real risk that the revised documentation could easily become unwieldy and difficult to use, thus introducing risk into the GB railway through increased uncertainty. A roadmap to address these issues is presented in section 5, and conclusions and recommendations are set out in Section 6.

Page 19 of 98


Issue/Ver: 1.0

Date: 28/03/2019

Table 3 Review Outcomes Statistics

Notes: explanations of table from left to right

• Column “Catalogue” represents the standard catalogue as of downloaded from the RSSB website. • Column “#” represents the total number of standards reviewed under each category. • Columns for ETCS, TMS and C-DAS:

o Column “#” represents the total number of standards requiring updates. Column “#%” represents the total number of standards requiring updates / the total number of standards in each category. o Column “Minor” represents the total number of standards requiring minor update. Column “Minor%” represents the total number of standards requiring minor update / the total number of standards in each category. o Column “Major” represents the total number of standards requiring major update. Column “Major%” represents the total number of standards requiring Major update / the total number of standards in each category.

• Column “Change Request #” represents the total number of standards requiring update affected by at least one deployment. Column “Change Request %” represents the % of the total number of standards requiring update affected by at least one deployment / the total number of standards in each category.

Catalogue # # Minor Major # Minor Major # Minor Major #% Minor% Major% #% Minor% Major% #% Minor% Major%

NATIONAL OPERATIONS PUBLICATIONS 110 53 26 27 19 9 10 10 1 9 48% 24% 25% 17% 8% 9% 9% 1% 8% 62 56%

Briefing Leaflet 1 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

GERT8001 Changes to National Operations Publications 1 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Handbook 26 7 6 1 4 3 1 1 - 1 27% 23% 4% 15% 12% 4% 4% 0% 4% 15 58%

Pink Pages (GORT3053) 4 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

RB Form 32 20 1 19 2 - 2 1 - 1 63% 3% 59% 6% 0% 6% 3% 0% 3% 20 63%

RB Modules:AC 1 1 1 - - - - - - - 100% 100% 0% 0% 0% 0% 0% 0% 0% 1 100%

RB Modules:DC 1 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

RB Modules:G 1 1 1 - - - - 1 1 - 100% 100% 0% 0% 0% 0% 100% 100% 0% 1 100%

RB Modules:Glossary 1 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

RB Modules:Issue History 1 1 - 1 1 - 1 1 - 1 100% 0% 100% 100% 0% 100% 100% 0% 100% 1 100%

RB Modules:M 3 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

RB Modules:OTM 1 1 1 - 1 1 - - - - 100% 100% 0% 100% 100% 0% 0% 0% 0% 1 100%

RB Modules:P 2 1 1 - - - - - - - 50% 50% 0% 0% 0% 0% 0% 0% 0% 1 50%

RB Modules:PoSA 1 1 1 - - - - - - - 100% 100% 0% 0% 0% 0% 0% 0% 0% 1 100%

RB Modules:S 3 2 2 - - - - - - - 67% 67% 0% 0% 0% 0% 0% 0% 0% 2 67%

RB Modules:SP 1 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

RB Modules:SS 2 2 2 - - - - - - - 100% 100% 0% 0% 0% 0% 0% 0% 0% 2 100%

RB Modules:T 3 2 2 - 3 3 - - - - 67% 67% 0% 100% 100% 0% 0% 0% 0% 3 100%

RB Modules:TS 10 4 4 - 1 1 - - - - 40% 40% 0% 10% 10% 0% 0% 0% 0% 4 40%

RB Modules:TW 4 1 1 - - - - - - - 25% 25% 0% 0% 0% 0% 0% 0% 0% 1 25%

RS Handbooks 3 2 2 - - - - - - - 67% 67% 0% 0% 0% 0% 0% 0% 0% 2 67%

White Pages (GORT3056) 2 1 1 - 1 1 - - - - 50% 50% 0% 50% 50% 0% 0% 0% 0% 1 50%

Manual 6 6 - 6 6 - 6 6 - 6 100% 0% 100% 100% 0% 100% 100% 0% 100% 6 100%

STANDARDS 211 51 41 10 16 13 3 22 19 3 24% 19% 5% 8% 6% 1% 10% 9% 1% 109 52%

Code of Practice 7 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Good Practice Guide 4 2 2 - 1 1 - 2 2 - 50% 50% 0% 25% 25% 0% 50% 50% 0% 4 100%

Guidance Note 55 9 9 - 4 4 - 3 3 - 16% 16% 0% 7% 7% 0% 5% 5% 0% 22 40%

Rail Industry Standard 94 25 20 5 7 7 - 9 9 - 27% 21% 5% 7% 7% 0% 10% 10% 0% 59 63%

RGS Form 10 6 3 3 4 1 3 6 3 3 60% 30% 30% 40% 10% 30% 60% 30% 30% 6 60%

Standard 41 9 7 2 - - - 2 2 - 22% 17% 5% 0% 0% 0% 5% 5% 0% 18 44%

CODE & STRATEGIES 15 1 - 1 1 - 1 - - - 7% 0% 7% 7% 0% 7% 0% 0% 0% 1 7%

Code ＆ Manual 2 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Strategy 13 1 - 1 1 - 1 - - - 8% 0% 8% 8% 0% 8% 0% 0% 0% 1 8%

OTHER ORGANISATION DOCUMENTS 129 4 3 1 2 2 - 1 1 - 3% 2% 1% 2% 2% 0% 1% 1% 0% 7 5%

M and EE:Code of practice 39 1 1 - - - - - - - 3% 3% 0% 0% 0% 0% 0% 0% 0% 1 3%

M and EE:Poster 30 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

RDG:Code of Practice 7 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

RDG:Good Practice Guide 9 1 1 - 1 1 - - - - 11% 11% 0% 11% 11% 0% 0% 0% 0% 2 22%

RDG:Guidance Note 44 2 1 1 1 1 - 1 1 - 5% 2% 2% 2% 2% 0% 2% 2% 0% 4 9%

SIGNS 133 4 - 4 - - - - - - 3% 0% 3% 0% 0% 0% 0% 0% 0% 4 3%

Lineside Operational Signs:Approach to Level Crossings Signs5 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Lineside Operational Signs:Communications Signs 15 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Lineside Operational Signs:Electrical Traction Signs 6 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Lineside Operational Signs:Geographically Specific Signs 2 2 - 2 - - - - - - 100% 0% 100% 0% 0% 0% 0% 0% 0% 2 100%

Lineside Operational Signs:Identification Signs 11 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Lineside Operational Signs:Limits for Engineering Possessions Signs3 1 - 1 - - - - - - 33% 0% 33% 0% 0% 0% 0% 0% 0% 1 33%

Lineside Operational Signs:Miscellaneous Signs 21 1 - 1 - - - - - - 5% 0% 5% 0% 0% 0% 0% 0% 0% 1 5%

Lineside Operational Signs:Speed Signs 23 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Lineside Operational Signs:Train Protection Signs 14 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Lineside Safety Signs:Infrastructure Managers Signs 10 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Lineside Safety Signs:Signs for the Public 23 - - - - - - - - - 0% 0% 0% 0% 0% 0% 0% 0% 0% - 0%

Grand Total 598 113 70 43 38 24 14 33 21 12 19% 12% 7% 6% 4% 2% 6% 4% 2% 183 31%

Change

Request#

Change

Request%

TMS C-DASAs of 1st of Dec 2018 downloaded from RSSB ETCS TMS C-DAS ETCS

Standards (Railway Group Standards)

Page 20 of 98


Issue/Ver: 1.0

Date: 28/03/2019

5 Roadmap for the Development of Nationally-Applicable Rules, Standards and Processes

The nationally-applicable Rules and Standards are governed via a well-understood national process which must be followed. In most cases, the actual revision work is conducted through cross-industry activity overseen by the RSSB. A question remains as to which party should initiate the change process.

At this time, no decision has been made as to who will be responsible for the initiation of change to National Operations Publications, RGS or RIS documents, etc. The accepted principle is that the first Deployment Project which needs the change will initiate that change process and start the industry-wide consultation and development activity.

When document preparation starts, there is a reasonable argument that some of the nationally-applicable changes should be initiated by the DRP and, given that the preparation/change process for many of these nationally-applicable Standards is likely to take 18-24 months, as a minimum, it is then imperative that the change process start sooner rather than later. That said, the DRP is not currently remitted or funded to commence these change activities. The following section shows a potential roadmap for these changes to be initiated and applied, and this timeline should be noted by Deployment Projects to ensure that the change process is either initiated OR that appropriate interim measures are put in place (and approved as part of the safety argument) in plenty of time to allow deployments to ‘go live’ in line with their business cases.

This section provides a high-level roadmap, showing the areas of nationally-applicable Rules and Standards that are likely to be impacted by the introduction of DR technologies and the likely timescales within which the DRP will provide more detailed guidance on those likely changes.

The definitive reference for changing nationally-applicable Standards is the RSSB Standards Manual (‘Managing standards for the mainline railway system’) [RD13]. This document describes the process by which Standards may be changed but does not provide indicative timelines for different kinds of change. As such, an indicative time period of 18-24 months has been included in this initial version of Rules and Standards Framework.

It is recommended that an appropriate individual be appointed to lead engagement with both the RSSB and the Industry regarding Rules and Standards change. It is also recommended that the appointed individual engage with the RSSB at the earliest opportunity to agree an appropriate way forward for expediting the required volume of Rule and Standards changes to facilitate the smooth introduction into service of Digital Railway technologies. Figure 4 gives an indicative timeline for initiating and completing Rules and Standards change associated with the Operation and Maintenance of Digital Railway technologies. The timelines for the change process are based on the experience of a team when going through initiation of the change and industry consultation, and then introducing the change process. Typically, this can be achieved in 18 months (darker blue) but can run to 24 months (lighter shade of blue). In practice, the timelines for individual changes may vary significantly, but this illustration will help Deployment Projects to plan the initiation of any changes required to align with their anticipated deployment timescales.

Page 21 of 98


Issue/Ver: 1.0

Date: 28/03/2019

Figure 4 High-Level Roadmap for Rules and Standards Change

6 Conclusions and Recommendations

This work has identified that:

• the amount of work required to revise existing Rules and Standards or document new ones for the Digital Railway is significant.

• the time available to prepare and/or revise this documentation is limited if it is to be available for the early Deployment Projects. The management of modern digital systems requires specific documented practices to be successful; the success and effectiveness of the DR projects will be at risk if the supporting documents do not represent best practice.

• specifically, if the volumes of change identified are applied to existing documentation, there is a risk that the revised documentation will become overly complex and difficult to use by the GB Rail Industry.

It would seem imperative that the railway industry as a whole embrace the Rules and Standards required by the Digital Railway. Therefore, the following recommendations are made:

• A decision should be made sooner rather than later to agree which party will initiate the change process for Rules and Standards identified in this framework.

• Funding for the change process for Rules and Standards should be secured at the earliest opportunity.

• Serious consideration should be given to the best and most appropriate structure for revised or added Rules and Standards in order that it can best meet the objectives of providing clear and transparent rules regarding the implementation and operation of a digital railway.

• A dedicated team should be set up to manage the changes to Rules and Standards. This team will engage with the various industry parties and work to support the RSSB and Standards committees to enable this work to be completed on time and within cost.

Month (s) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Lead manager appointed to co-ordinate

Rule and Standards change with the

industry and RSSB

t

Decision on who should initiate which

changest

Identification and engagement with

appropriate Standards Committees

Rule Book Change Process (18 -24 months)

RGS Change Process (18-24 Months)

RIS Change Process (18-24 Months)

Page 22 of 98


Issue/Ver: 1.0

Date: 28/03/2019

7 Appendix A: Rules and Standards Reviewing Outcomes

Note: the review outcomes of this exercise were based on the version of Standards Catalogues Dec 2018 downloaded from the RSSB. The standards catalogues are updated every three months and any document updated should be reviewed and updated by following the methodology described in section 0.

Document Detail ETCS TMS C-DAS Others

Document Number Title

Are there any changes

required for ETCS

deployment?

If so, what is the estimate

scale of changes required?

Are there any new topics required for

ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?



Are there any new topics

required for C-DAS

deployment?

Why are changes required?

(To explain the reasoning supporting the decision for the changes or not under

four headings.)

Document changes

recommended?

BR1654 Iss 2 Radio Electronic Token Block System

N N/A Y N N/A Y N N/A Y General: It is possible that the existing RETB schemes will have to be interfaced to a neighbouring ETCS and C-DAS projects, and at some time the equipment will become life-expired. It may be that rolling-stock specifically fitted for RETB is not acceptable. The migration of a RETB control point into a neighbouring ROC might be preferred. At first sight it would seem that C-DAS would have no purpose along an RETB controlled line. However, depending on the suitability of the timetable modification elements of C-DAS it could become a useful aid at times of traffic disruption. If interfacing or replacement intentions arise, allowance is made here for specific ETCS, TMS and C-DAS docs. ETCS: See above. TMS: See above. C-DAS: See above.

Y

Form RT3119-A Iss 7 Provisional SPAD Data Collection Form (Infrastructure Manager)

N N/A N N N/A N N N/A N General: This form concerns the pre-DR context. ETCS: N/A TMS: N/A C-DAS: N/A

N

Form RT3119-B Iss 7 Provisional SPAD Data Collection Form (Railway Undertaking)

N N/A N N N/A N N N/A N General: This form concerns the pre-DR context. ETCS: N/A TMS: N/A C-DAS: N/A

N

Form RT3119-C Iss 2 Provisional ERTMS SPAD Data Collection Form (Infrastructure Manager)

Y Minor N N N/A N Y Minor N General: This form is prepared for the DR context, but does not refer to C-DAS. ETCS: Minor updates allowed for. TMS: N/A C-DAS: Any C-DAS arrangements should be recorded.

Y

Form RT3119-D Iss 2 Provisional ERTMS SPAD Data Collection Form (Railway Undertaking)

Y Minor N N N/A N Y Minor N General: This form is prepared for the DR context, but does not refer to C-DAS. ETCS: All the train data should be required. TMS: N/A C-DAS: Any C-DAS displays should be recorded.

Y

Form RT3973-CON Iss 1 Advice to Train Crews - Conveyance of Containers

Y Major N Y Major N Y Major N General: The need to accommodate km/h is noted. ETCS: ETCS train data should include the exceptional permissible speeds (amendable en route?). TMS: Copy should be held on the TMS. C-DAS: C-DAS data could require amending by train crew.

Y

Form RT3973-EXL Iss 1 Advice to Train Crews - Conveyance of Exceptional Loads

Y Major N Y Major N Y Major N General: The need to accommodate km/h is noted. ETCS: ETCS train data should include the exceptional permissible speeds (amendable en route?). TMS: Copy should be held on the TMS.

Y

Page 23 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

C-DAS: C-DAS data could require amending by train crew.

Form RT3973-HAW Iss 1 Advice to Train Crew - Conveyance of Heavy Axle Weight

Y Major N Y Major N Y Major N General: The need to accommodate km/h is noted. ETCS: ETCS train data should include the exceptional permissible speeds (amendable en route?). TMS: Copy should be held on the TMS. C-DAS: C-DAS data could require amending by train crew.

Y

Form RT3973-NUC Iss 1 Advice to Train Crews - Conveyance of Radioactive Flask

Y Minor N Y Minor N Y Minor N General: The need to accommodate km/h is noted. ETCS: ETCS train data should include the exceptional permissible speeds (amendable en route?). TMS: Copy should be held on the TMS. C-DAS: C-DAS data could require amending by train crew.

Y

Form RT8106 Iss 1 Example Failure Data Collection Form

N N/A N N N/A N N N/A N General: The form is very high level and is not intended for particular equipment. How it is to be used is not clear. ETCS: N/A TMS: N/A C-DAS: N/A

N

Form RT8250 Iss 3 Urgent Safety-Related Defect Report Form

N N/A N N N/A N N N/A N General: The form is very high level and is not intended for particular equipment. It refers to GERT8250 for completion instructions. ETCS: N/A TMS: N/A C-DAS: N/A

N

GCGN5612 Iss 2 Rail Traffic Loading Requirements for the Design of Railway Structures

N N/A Y N N/A N N N/A N General: This document does not appear to address route availability issues, but addresses the loading design issues. It is recent and refers to TSIs, but the interface to the train data for ETCS is not apparent. ETCS: This project uses an axle load parameter stated in para 5.5 and repeated in table 1 of the SDD. TMS: N/A C-DAS: N/A

Y

GCRT5021 Iss 5 Track System Requirements N N/A Y N N/A N N N/A N General: N/A ETCS: This document avoids requirements related to sleepers and in-track equipment. It makes note of the requirements to accommodate track-circuits. There may be a better place, but for the moment the need to accommodate cable routing, balises and axle-counters is noted here. TMS: N/A C-DAS: N/A

Y

GEGN8502 Iss 1 Operation of Trams and Light Rail or Metro Vehicles Over Railtrack Controlled Infrastructure

N N/A Y N N/A N N N/A N General: Not of a detail that implies any particular solution. Refers to radio as well. ETCS: The use of ETCS on tram/trains has to be anticipated. Preliminary work should be set out. TMS: N/A C-DAS: N/A

Y

GEGN8516 Iss 1 Guidance on Recording and Monitoring of Spoken Safety Communications

N N/A N N N/A Y N N/A N General: Relevant to TMS, but no changes identified at the level of detail provided. ETCS: N/A

Y

Page 24 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: See above. C-DAS: N/A

GEGN8532 Iss 5 Guidance on 'Signals, Railway Track, Explosive' (also known as 'Detonators')

N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GEGN8540 Iss 2 Guidance on Low Adhesion between the Wheel and the Rail - Managing the Risk

N N/A Y N N/A Y N N/A Y General: See below. ETCS: ETCS introduces the possibility of amending the train brake rate for protection purposes. This feature should be part of this standard. It has implications for ETCS, TMS and C-DAS. TMS: See above. C-DAS: See above.

Y

GEGN8570 Iss 2 Guidance on the Management of Drugs and Alcohol


N

GEGN8573 Iss 4 Guidance on Gauging and Platform Distances

Y Minor N N N/A Y N N/A Y General: In itself the document has no direct implications for ETCS, C-DAS or TMS except that the train data required for ETCS is derived from the loading gauge data defined in the appendices of GMRT8073. This parameter is required for route setting (infrastructure route limits) and possibly for out of gauge situations, a special permissible speed. ETCS: this project uses a loading gauge parameter stated in para 5.5 and repeated in table 1 of the SDD. Compatibility with this guidance should be checked. TMS: See above. C-DAS: Speeds higher than any special permissible speeds should not be displayed.

Y

GEGN8578 Iss 3 Guidance on the Use of On-Train Satellite Positioning Technology Based Locator for Railway Applications

N N/A Y N N/A N N N/A N General: This document provides a framework in which vehicle systems can harmonise and share GNSS data. Individual systems using separate GNSS systems is undesirable e.g. limitations on aerial fitment. C-DAS is likely to use GNSS. Special provisions are not expected. ETCS: In the future ETCS is likely to use GNSS as a component of speed and location systems. Special provisions e.g. safety requirements, may be necessary. TMS: N/A C-DAS: N/A

Y

GEGN8579 Iss 1 Guidance on Digital Wireless Technology for Train Operators

N N/A Y N N/A N N N/A N General: This document provides a framework in which vehicle systems can harmonise and share wireless systems. C-DAS is likely to use wireless communications. Special provisions are not expected. ETCS: The document addresses security and key management. ETCS is not expected to use on train wireless systems in the near future. However, interfacing to vehicle wired and wireless communications is a possibility because of the benefits offered. TMS: N/A C-DAS: N/A

Y

Page 25 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GEGN8607 Iss 2 Guidance on the Use of Escrow Agreements for Rail Applications

N N/A Y N N/A Y N N/A Y General: The document is written around non-signalling systems e.g. traction. It is adequate in that context. Extension for ETCS, TMS and C-DAS could be considered. ETCS: It does provide a framework in which the future management of a safety SIL 4 system could be assured in the event of the non-availability of a supplier. Additional considerations could be required. TMS: See above. C-DAS: See above.

Y

GEGN8611 Iss 1 Guidance on the Application of the Control Command and Signalling TSI

N N/A N N N/A N N N/A N General: The document is recent and is presumed fit for purpose. ETCS: N/A TMS: N/A C-DAS: N/A

N

GEGN8614 Iss 1 Guidance on Axlebox Condition Monitoring - Hot Axlebox Detection

N N/A N N N/A N N N/A N General: This document is not of the detail to specify the interface to a control-centre. For ETCS, there should be no need for a limitation to place a hot box detector near a balise. For TMS, this project has set out its aspirations for interfacing to trackside objects. ETCS: N/A TMS: N/A C-DAS: N/A

N

GEGN8618 Iss 1 Guidance on Mechanical Trainstop System

N N/A N N N/A Y N N/A N General: This document does not address the specifics of dual signalling, other than the provision of overlaps. The specific TMS and ETCS projects will address their needs according to the use of their infrastructure by London Underground. For ETCS, the use of train stops implies the use of lineside signalling. ETCS: N/A TMS: The control centres will need to know when a train is tripped and have sufficient information to manage the situation. C-DAS: N/A

Y

GEGN8628 Iss 1 Guidance on Preparation for and Operation during Winter

N N/A Y N N/A N N N/A N General: The document addresses mechanical issues, e.g. S&C, couplers. ETCS: There could be a need to introduce snow clearance from balises, especially on lesser used mountainous routes with slow running. TMS: N/A C-DAS: N/A

Y

GEGN8646 Iss 1 Guidance on the Common Safety Method for Risk Evaluation and Assessment


N

GEGN8650 Iss 1 Guidance on High-Integrity Software-Based Systems for Railway Applications

N N/A N N N/A N N N/A N General: The document is recent and relevant to ETCS. TMS and C-DAS will have to address safety in the wider context of these projects on the operational railway, but the projects themselves ought not to be safety-critical. No changes for ETCS are expected. ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 26 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GEGN8651 Iss 1 Guidance Note for Safe Integration of CCS Systems with Train Operations

Y Minor Y Y Minor Y Y Minor Y General: The document addresses normal working only. It makes no mention of degraded modes. It does not specifically address a particular system or subsystem. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERT8006 Iss 2 Assessment of Compatibility of Rail Vehicle Weights and Underline Bridges

Y Minor N N N/A Y N N/A N General: In itself the document has no direct implications for ETCS, C-DAS or TMS except that the train data required for ETCS is derived from the RA number defined in appendix A. This parameter is required for calculating permissible speeds, maximum advisory speed, and route setting (infrastructure route limits). ETCS: This project uses an axle load parameter stated in para 5.5 and repeated in table 1 of the SDD. TMS: This information could be required for certain functions. C-DAS: N/A

Y

GERT8014 Iss 2 Axlebox Condition Monitoring - Hot Axlebox Detection

N N/A N N N/A N N N/A N General: This document is not of the detail to specify the interface to a control-centre. For ETCS, there should be no need for a limitation to place a hot box detector near a balise. For TMS, this project has set out its aspirations for interfacing to trackside objects. ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8018 Iss 2 Mechanical Trainstop System Interface

N N/A N N N/A Y N N/A N General: This document does not address the specifics of dual signalling, other than the provision of overlaps. The specific TMS and ETCS projects will address their needs according to the use of their infrastructure by London Underground. For ETCS, the use of train stops implies the use of lineside signalling. ETCS: N/A TMS: The control centres will need to know when a train is tripped and have sufficient information to manage the situation. C-DAS: N/A

Y

GERT8073 Iss 3 Requirements for the Application of Standard Vehicle Gauges.

Y Minor N N N/A Y N N/A N General: In itself the document has no direct implications for ETCS, C-DAS or TMS except that the train data required for ETCS is derived from the loading gauge data defined in the appendices. This parameter is required for route setting (infrastructure route limits) and possibly for out of gauge situations, a special permissible speed. ETCS: This project uses a loading gauge parameter stated in para 5.5 and repeated in table 1 of the SDD. For C-DAS, speeds higher than any special permissible speeds should not be displayed. TMS: See above. C-DAS: N/A

Y

GERT8075 Iss 3 AWS and TPWS Interface Requirements


N

Page 27 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GERT8273 Iss 1 Assessment of Compatibility of Rolling Stock and Infrastructure - Gauging and Stepping Distances

N N/A Y N N/A Y N N/A Y General: N/A ETCS: this project uses a loading gauge parameter stated in para 5.5 and repeated in table 1 of the SDD. Compatibility with this document should be checked. TMS: the relationship with route-setting and route availability needs to be checked. C-DAS: the need to know of and implement any special permissible speeds that could be imposed needs to be checked. Speeds higher than these values should not be displayed.

Y

GERT8402 Iss 2 ERTMS/ETCS DMI National Requirements

N N/A N N N/A N N N/A N General: The document is current. No change should be required. ETCS: N/A TMS: N/A C-DAS: N/A

N

GIGN5633 Iss 1 Recommendations for the Risk Assessment of Buffer Stops and End Impact Walls

Y Minor Y N N/A N N N/A N General: The document does not address the role of train protection in the context of buffer stops. The document may be correct in that the risk is greatest in the context of degraded modes, e.g. train protection not available. This can be mitigated in several ways such as the automatic enforcement of a speed limit in this case. The subject has to be addressed. ETCS: See above. TMS: N/A C-DAS: N/A

Y

GIGN7608 Iss 2 Guidance on the Infrastructure Technical Specification for Interoperability


N

GIGN7619 Iss 2 Guidance on the Safety in Railway Tunnels Technical Specification for Interoperability

N N/A N N N/A Y N N/A N General: The document is recent and is presumed fit for purpose. ETCS: N/A TMS: Interfaces, unspecified are required. C-DAS: N/A

Y

GIGN7621 Iss 1 Guidance for the Development and Design Considerations of Passenger Rolling Stock Depots

N N/A N N N/A N N N/A N General: Signalling is discussed. For, ETCS cannot be excluded but requires no new text. For TMS, local control arrangements are discussed. ETCS: N/A TMS: N/A C-DAS: N/A

N

GIGN7633 Iss 1 Guidance on Lineside Signs Y Minor N N N/A N N N/A N General: The signs are for the pre-DR railway. This document defines the format of the signs, it does not mandate their use. As for ETCS in Full Supervision, the need for signs is unlikely. However, degraded and special working will have to be considered. ETCS: The decision on which signs are to be used should be set out in the appropriate standard with the relevant caveats. TMS: N/A C-DAS: N/A

Y

GIGN7634 Iss 1 Index for Lineside Signs N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 28 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GIRT7020 Iss 1 GB Requirements for Platform Height, Platform Offset and Platform Width


N

GIRT7033 Iss 3 Lineside Signs N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GIRT7073 Iss 2 Requirements for the Position of Infrastructure and for Defining and Maintaining Clearances

Y Minor Y N N/A Y Y Minor N General: Para 3.6.8.3 has implications for ETCS and C-DAS. ETCS: Balise requirements are required in appendix A. (And TPWS?). TMS: This has implications for safe and exceptional routing of trains of differing characteristics through infrastructure with differing characteristics. C-DAS: There could be a requirement for C-DAS to know of special speed limits.

Y

GKGN0554 Iss 2 Guidance on Radio Electronic Token Block (RETB)

N N/A Y N N/A N N N/A N General: N/A ETCS: If a transition with ETCS does arise in the future, it would probably be addressed in RIS-0036-CCS. TMS: N/A C-DAS: N/A

Y

GKGN0602 Iss 1 Guidance on Train Rooftop Antenna Positioning

N N/A N N N/A N N N/A N General: GSM-R (data) requirements will be addressed elsewhere. ETCS: N/A TMS: N/A C-DAS: N/A

N

GKGN0655 Iss 1 Guidance on Block System Interface Requirements

N N/A Y N N/A N N N/A N General: This document applies to pre-DR arrangements. In principle, ETCS is described by the TSIs and the standards set out in the annex A specifications, plus the standards supporting the GB application. ETCS should not need to be part of this document. However, where ETCS becomes used with these pre-DR arrangements additional sections could be required. ETCS: See above. TMS: N/A C-DAS: N/A

Y

GKGN0657 Iss 1 Guidance on Lineside Signal and Indicator Product Design and Assessment Requirements

Y Minor N N N/A N N N/A N General: This document refers to pre-DR lineside hardware. ETCS requirements would be better elsewhere. ETCS: The ETCS stop marker is not included. TMS: N/A C-DAS: N/A

Y

GKGN0802 Iss 1 Glossary of Signalling Terms Y Minor N Y Minor N Y Minor N General: The various projects may wish to add their key terms to the standard. ETCS: see above. TMS: see above. C-DAS: see above.

Y

GKRT0028 Iss 3 Infrastructure Based Train Detection Interface Requirements

N N/A N N N/A N N N/A N General: The document is current. No change should be required. ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 29 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GKRT0055 Iss 1 Block System Interface Requirements

N N/A Y N N/A N N N/A N General: This document applies to pre-DR arrangements. In principle, ETCS is described by the TSIs and the standards set out in the annex A specifications, plus the standards supporting the GB application. ETCS should not need to be part of this document. However, where ETCS becomes used with these pre-DR arrangements additional sections could be required. ETCS: See above. TMS: N/A C-DAS: N/A

Y

GKRT0057 Iss 1 Lineside Signal and Indicator Product Design and Assessment Requirements

Y Minor N N N/A N N N/A N General: This document refers to pre-DR lineside hardware. ETCS requirements would be better elsewhere. ETCS: The ETCS stop marker is not included. TMS: N/A C-DAS: N/A

Y

GKRT0075 Iss 5 Requirements for Minimum Signalling Braking and Deceleration Distances

Y Major Y N N/A N N N/A N General: This is a topic that requires review to meet ETCS requirements. ETCS: ETCS has a specific harmonised approach to the definition of brake-rate data that is dealt with in GMRT2045 iss4. TMS: N/A C-DAS: N/A

Y

GLGN1600 Iss 1 Guidance on the Energy TSI N N/A N N N/A Y N N/A N General: The document is recent and is presumed fit for purpose. ETCS: N/A TMS: Interfaces, unspecified, are required. C-DAS: N/A

Y

GLGN1610 Iss 1 Guidance on AC Energy Subsystem and Interfaces to Rolling Stock Subsystem

Y Minor Y N N/A N N N/A N General: for TMS. TMS will require interfaces to and information from traction systems, but they perhaps would not belong in this document. ETCS: ETCS includes functions for the switching of AC traction systems. Their use and restrictions on their use will need to be set out in this document. TMS: N/A C-DAS: N/A

Y

GLGN1612 Iss 1 Guidance on DC Conductor Rail Energy Subsystem and Interfaces to Rolling Stock Subsystem

N N/A N N N/A N N N/A N General: TMS will require interfaces to and information from traction systems, but they perhaps would not belong in this document. ETCS: N/A TMS: N/A C-DAS: N/A

N

GLGN1620 Iss 1 Guidance on the Application of the Control of Electromagnetic Fields at Work Regulations

N N/A N N N/A N N N/A N General: This document is up to date. It refers to the Eurobalise reader for example. ETCS: N/A TMS: N/A C-DAS: N/A

N

GLRT1210 Iss 1 AC Energy Subsystem and Interfaces to Rolling Stock Subsystem

Y Minor Y N N/A N N N/A N General: TMS will require interfaces to and information from traction systems, but they perhaps would not belong in this document. ETCS: ETCS includes functions for the switching of AC traction systems. Their use and restrictions on their use will need to be set out in this document. TMS: N/A C-DAS: N/A

Y

Page 30 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GLRT1212 Iss 1 DC Conductor Rail Energy Subsystem and Interfaces to Rolling Stock Subsystem

N N/A N N N/A N N N/A N General: TMS will require interfaces to and information from traction systems, but they perhaps would not belong in this document. ETCS: N/A TMS: N/A C-DAS: N/A

N

GMGN2460 Iss 1 Guidance on Compliance with Noise and Vibration Legislation in the Railway Environment


N

GMGN2571 Iss 1 Guidance on the Storage and Recommissioning of Traction and Rolling Stock


N

GMGN2606 Iss 1 Guidance on the Fitment and Functionality of Forward and Rear Facing Cameras on Rolling Stock


N

GMGN2607 Iss 1 Guidance on the Braking Requirements for Hauling Unbraked Multiple Units in Freight Trains


N

GMGN2611 Iss 1 Guidance on Rolling Stock Subsystem and Interfaces to AC Energy Subsystem

Y Minor N Y Minor N N N/A N General: N/A ETCS: ETCS has the functionality to control the pantograph and circuit breakers on a locomotive. Para 3.8 refers. If this functionality is to be used in the UK amendments to the document may be needed. TMS: If the ETCS functionality is retained for the UK, the necessary control functions will be required. C-DAS: N/A

Y

GMGN2613 Iss 1 Guidance on Rolling Stock Subsystem and Interfaces to DC Conductor Rail Energy Subsystem


N

GMGN2615 Iss 2 Guidance on the Locomotives and Passenger Rolling Stock TSI


N

GMGN2630 Iss 1 Guidance on Rail Vehicle Fire Safety


N

GMGN2642 Iss 1 Guidance on Wheel / Rail Low Adhesion Measurement


N

GMGN2643 Iss 1 Guidance on Wheel / Rail Low Adhesion Simulation


N

GMGN2646 Iss 1 Guidance on Axle Bearing Maintenance

N N/A N N N/A N N N/A N General: N/A ETCS: N/A

N

Page 31 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

GMGN2685 Iss 1 Guidance on Lifting, Jacking, Recovery and Emergency Movement of Rail Vehicles


N

GMGN2686 Iss 1 Guidance on Rail Vehicle Bodyshell, Bogie and Suspension Elements


N

GMGN2687 Iss 1 Guidance on Rail Vehicle Interior Structures and Secondary Structural Elements


N

GMGN2688 Iss 2 Guidance on Designing Rail Freight Wagons for use on the GB Mainline Railway


N

GMGN2689 Iss 2 Guidance on Mechanical Coupling of Rail Vehicles


N

GMGN2695 Iss 1 Guidance on Testing of Wheel Slide Protection Systems Fitted on Rail Vehicles


N

GMRC2513 Iss 1 Commentary on Permissible Track Forces for Railway Vehicles


N

GMRC2531 Iss 1 Recommendations for Rail Vehicle Emergency Lighting


N

GMRC2532 Iss 1 Recommendations for Rail Vehicles Emergency and Safety Equipment


N

GMRC2533 Iss 1 Recommendations for Communication of Rail Vehicle Emergency & Safety Information


N

GMRC2534 Iss 1 Recommendations for Rail Vehicle Emergency Evacuation


N

GMRC2542 Iss 1 Recommendations for Determination of Aerodynamic Rolling Moment Coefficient


N

GMRC2641 Iss 2 Recommendations for Vehicle Static Testing


N

Page 32 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GMRT2045 Iss 4 Compatibility Requirements for Braking Systems of Rail Vehicles

N N/A N N N/A N N N/A N General: This document covers the range of subjects necessary. For ETCS, it includes the relationship with ETCS data input. For TMS, it addresses the derivation of train consist performance for train planning purposes. For C-DAS, Brake rates for a given consist will be necessary for C-DAS to derive accurate estimates of train performance. ETCS: N/A TMS: N/A C-DAS: N/A

N

GMRT2100 Iss 5 Requirements for Rail Vehicle Structures


N

GMRT2111 Iss 1 Rolling Stock Subsystem and Interface to AC Energy Subsystem

N N/A Y N N/A N N N/A N General: N/A ETCS: 1. If adopted, the control of AC traction equipment by ETCS may need to be added. 2. The ETCS has the ability to disconnect the traction power in the event of emergency braking. If adopted it may need to be added. (but would normally be implemented through a function common to all equipment that has the ability to call the emergency brakes). TMS: N/A C-DAS: N/A

Y

GMRT2113 Iss 1 Rolling Stock Subsystem and Interfaces to DC Conductor Rail Energy Subsystem


N

GMRT2130 Iss 4 Vehicle Fire, Safety and Evacuation N N/A Y N N/A N N N/A Y General: No requirements specific to equipment ancillary to traction e.g. ETCS, C-DAS onboard have been found. There is a need for such equipment to be considered. ETCS: See above. TMS: N/A C-DAS: See above.

Y

GMRT2131 Iss 1 Audibility and Visibility of Trains. N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GMRT2132 Iss 1 On-board Energy Metering for Billing Purposes


N

GMRT2141 Iss 3 Resistance of Railway Vehicles to Derailment and Roll-Over


N

GMRT2142 Iss 4 Resistance of Railway Vehicles to Roll-Over in Gales


N

GMRT2160 Iss 4 Environment Inside Railway Vehicles (Audibility of detonators)


N

Page 33 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GMRT2161 Iss 1 Requirements for Driving Cabs of Railway Vehicles

Y Minor N N N/A N Y Minor N General: This document dates from before the development of ETCS and C-DAS. ETCS: References to RIS-0797-CCS and RIS-0798-CCS are required as a minimum. The interfaces between these documents requires structuring. TMS: N/A C-DAS: References will be required.

Y

GMRT2162 Iss 3 Traincrew Access to and Egress from Railway Vehicles


N

GMRT2173 Iss 2 Requirements for the Size of Vehicles and Position of Equipment

N N/A Y N N/A N N N/A Y General: There may be a need to include aerials in the scope of this document, which is concerned with the swept envelope of a vehicle. GSM-R: Radio aerial. ETCS: See above. TMS: N/A C-DAS: See above.

Y

GMRT2176 Iss 1 Air Quality and Lighting Environment for Traincrew Inside Railway Vehicles


N

GMRT2185 Iss 2 Train Safety Systems Y Major N N N/A N N N/A N General: this document is pre-DR. If it is to remain it will need updating with ETCS and Radio. ETCS: See above. TMS: N/A C-DAS: N/A

Y

GMRT2400 Iss 6 Engineering Design of On-track Machines in Running Mode

Y Minor N N N/A N N N/A N General: Signalling related equipment is referred to. ETCS: When the policy for OTMs is decided the requirements will have to be added. TMS: N/A C-DAS: N/A

Y

GMRT2461 Iss 3 Sanding Equipment N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GMRT2466 Iss 4 Railway Wheelsets N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GMRT2472 Iss 2 Requirements for Data Recorders on Trains

N N/A N N N/A N N N/A Y General: The document is up to date. ETCS: N/A TMS: N/A C-DAS: Recording of some C-DAS data could be required.

Y

GMRT2477 Iss 3 Compatibility Requirements for Track Circuit Assisters (TCAs) on Rail Vehicles


N

GMRT2491 Iss 2 Design Requirements for a Driver's Reminder Appliance (DRA)


N

Page 34 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GMTT0088 Iss 1 Permissible Track Forces for Railway Vehicles


N

GOGN3518 Iss 1 Guidance on Incident Response Planning & Management


N

GOGN3615 Iss 2 Guidance on the Operation and Traffic Management Technical Specification for Interoperability


N

GOGN3653 Iss 3 Guidance for Safe Freight Train Operation


N

GOGN3655 Iss 2 Guidance on Medical Fitness for Railway Safety Critical Workers

Y Minor N Y Minor N Y Minor N General: The use of in-cab display screens for signalling purposes could increase the requirement for near field vision to be as effective as far field, without the need to exchange or add or remove visual aids. TMS is not concerned with driver requirements. ETCS: The ability to hear warning and information sounds emitted by the ETCS and C-DAS systems should be included. TMS: The comments on vison could be relevant to TMS. C-DAS: C-DAS requirements are considered to be covered by ETCS requirements.

Y

GOGN3676 Iss 3 Guidance on the Carriage of Dangerous Goods by Rail


N

GOGN3677 Iss 1 Guidance on Operational Criteria for the Provision of Lineside Telephony Following GSM-R Introduction


N

GOOTS303 Iss 1 Secondary Door Locking - Operational Requirements


N

RIS-0009-CCS Iss 1 Identification of Signalling and Related Equipment

Y Minor N N N/A Y Y Minor Y General: In the future the objective and roles of identification will become more complex. This document will need to set out to whom the identification is addressed and for what reason. ETCS: ETCS will be the principle signalling system. The structure of the current document does not reflect this. TMS: The role of Train Identities is evolving. The RUs could have lineside equipment in the future. Ownership and responsibilities of such equipment should be clearly identified. C-DAS: The document will need to reflect that RUs could have ownership of some equipment at the trackside - in ROCs for example.

Y

Page 35 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

RIS-0036-CCS Iss 1 Transitions Between Signalling Systems

N N/A Y N N/A Y N N/A Y General: The document will need restructuring. GSM-R: Radio transitions will need adding. ETCS: An annex for ETCS is required. TMS: The need for transition data to be displayed has to be considered. C-DAS: C-DAS transitions will need adding.

Y

RIS-0077-CCS Iss 1 Ground Frames and Shunters' Releases

Y Minor Y N N/A Y N N/A N General: N/A ETCS: ETCS interface and controls to RBC required. TMS: TMS interface required C-DAS: N/A

Y

RIS-0212-CCS Iss 1 Signalling Lockout Systems to Protect Railway Undertaking Personnel

N N/A Y N N/A N N N/A N General: The RIS is set into the case of the interface between a key device and an interlocking and its use. ETCS: ETCS adds an RBC and onboard logic to this interface. The following need to be addressed: 1. Terminology e.g. protecting signal to become protecting stop marker. 2. The logic of the RIS with respect to ETCS modes required should be reviewed. 3. The GN specific cases should be set into an ETCS context. Additional cases may be required. TMS: N/A C-DAS: N/A

Y

RIS-0386-CCS Iss 1 Rail Industry Standard on Signal Overrun Risk Evaluation and Assessment

Y Major Y N N/A N N N/A N General: The current standard is by definition appropriate for the existing railway. ETCS: When ETCS is introduced the fundamental basis of the risk assessment is changed. There are two cases: 1. The ATP function afforded by ETCS is known not to be available in the case being considered, although the zone concerned is believed to be limited by the ETCS speed control. 2. The operating railway believes and behaves as if the ATP function afforded by ETCS is functioning, but it is not. Note: not all ETCS intervention curves are effective down to zero speed. The topic becomes therefore an exercise in determining when ETCS could not be effective and the risk of this leading to an accident. It is quite a separate topic from the current document, but the intention is the same. TMS: N/A C-DAS: N/A

Y

RIS-0700-CCS Iss 2 Internet Access on Trains for Customer and Operational Railway Purposes

N N/A Y N N/A Y N N/A Y General: This standard is a global standard encompassing a wide range of modern technologies. It is not suitable for specific ETCS, TMS or C-DAS requirements. It does mix both commercial and operating requirements. Two separate documents should be considered, but this is not fundamental to the present exercise. ETCS: See above. TMS: See above. C-DAS: See above.

Y

RIS-0703-CCS Iss 1.1 Signalling Layout and Signal Aspect Sequence Requirements

Y Minor Y N N/A N N N/A N General: N/A ETCS: It is possible the PoSA aspect be used with ETCS OS or SR modes where the route is locked,

Y

Page 36 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

but a MA cannot be given. Specific cases should be added, if they exist. If not intended to be so used the reason and rational ought to be added. TMS: N/A C-DAS: N/A

RIS-0707-CCS Iss 1 Management of Safety Related Control, Command and Signalling System

N N/A Y N N/A Y N N/A Y General: This standard is recent and has a structure that accommodates additional systems quite readily. It could include additional requirements on new systems to include failure detection and fault recording and its sharing automatically. ETCS: It is ETCS ready, but has no detail. TMS: See above. C-DAS: C-DAS is not safety related, and a whole system approach is required to ensure that it remains so.

Y

RIS-0708-CCS Iss 1 ERTMS/ETCS National Values N N/A Y Y Minor N N N/A N General: N/A ETCS: In some cases, e.g. adhesion parameters, the standard says a change can be commanded by the "trackside". This is supposed it is believed to be the signaller and would require an appropriate function in the TMS system. TMS: See above. C-DAS: N/A

Y

RIS-0711-CCS Iss 1 Interface Requirements for Connected Driver Advisory System

N N/A N N N/A Y N N/A Y General: N/A. ETCS: N/A. TMS: See below. C-DAS: Some updating is provided for in the document. The changes through experience ought not to be large.

Y

RIS-0713-CCS Iss 1.1 Lineside Signalling Layout Driveability Assessment Requirements

N N/A Y N N/A N N N/A Y General: This standard is specifically for lineside signals. A similar document will be required to support ETCS. Some of the precursors in this standard are relevant to the ETCS case. However, the fundamentals are such that a separate document is required. ETCS: See above. TMS: N/A C-DAS: The driveability of C-DAS displays will be an important issue to address.

Y

RIS-0725-CCS Iss 1 Electromagnetic Compatibility of Train Detection Infrastructure with Rail Vehicles

N N/A Y N N/A N N N/A N General: Despite its title, this document does not address axle counters. A check will be made to see if these requirements are elsewhere, which will be the preferred method of train detection in UK ETCS level 2. ETCS: See above. TMS: N/A C-DAS: N/A

Y

RIS-0728-CCS Iss 1 Infrastructure Based Train Detection Systems


N

RIS-0734-CCS Iss 1 Signing of Permissible Speeds N N/A Y N N/A N Y Minor N General: This document does not refer to ETCS, TMS or C-DAS. ETCS: The need for lineside speed signs can be expected to remain, even in the presence of cab signalling. There will be scenarios of failed displays, unfitted trains and cases where the cab display would not apply.

Y

Page 37 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

The document currently requires that the signs are placed at the location of the permissible speed change. The case of conflict with the cab-display has to be considered. This will occur by a few 10s of metres because the display responds to the speed control curves of which there are several possible, including any speed measurement margins and overlap equivalents. The behaviour of the intervention function has to be considered and the signs placed to control the risk of unjustified interventions. TMS: N/A C-DAS: A requirement for C-DAS not to display any value higher than the prevailing permissible speed and permissible train speed may be required.

RIS-0735-CCS Iss 1 Signing of Temporary and Emergency Speed Restrictions

N N/A Y N N/A Y Y Minor N General: This document does not refer to ETCS, TMS or C-DAS. ETCS: The need for lineside speed signs can be expected to remain, even in the presence of cab signalling. There will be scenarios of failed displays, unfitted trains and cases where the cab display would not apply. The document currently requires that the signs are placed at the location of the speed change. In ETCS TSRs will be controlled by balises. The data in the balises will need to be consistent with the signage (consistent with the boundaries of the work site). The case of conflict with the cab-display has to be considered. This will occur by a few 10s of metres because the display responds to the speed control curves of which there are several possible, including any speed measurement margins and overlap equivalents. The behaviour of the intervention function has to be considered to control the risk of unjustified interventions. TMS: A facility to manage TSR entries into the RBC and their cancellation will be required. Coordination with the placement and removal of signage will be required. C-DAS: A requirement for C-DAS not to display any value higher than the temporary permissible speed and permissible train speed may be required.

Y

RIS-0737-CCS Iss 1 Rail Industry Standard for Signal Sighting Assessment Requirements

N N/A N N N/A N N N/A N General: The document applies only to lineside signals. The equivalent document is required for stop markers, however the context is different. Normally cab-signalling will be available and used. The stop markers are normally read at low speed and when the train is close. The exact specification will be dependent upon the rules adopted for degraded operation. ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-0743-CCS Iss1 ERTMS Key Management N N/A N N N/A N N N/A N General: Considered fit for purpose. ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 38 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

RIS-0744-CCS Iss 1 Permissive Working Risk Assessment and Risk Controls

N N/A Y N N/A N N N/A N General: The document is ETCS ready. ETCS: Comments. 1. The document would be more complete if it addressed ETCS Staff Responsible mode. If it is not to be used the reasons could be set out. 2. The PoSA is a permissive MA used when a block is indicating occupied due to a train detection fault and the route is however locked. A mention is required. TMS: N/A C-DAS: N/A

Y

RIS-0758-CCS Iss 1.1 Lineside Signal Aspects and Indications


N

RIS-0775-CCS Iss 2 AWS and TPWS Application Requirements


N

RIS-0784-CCS Iss 1 The Management of Packet 44 Applications

N N/A Y N N/A Y Y Minor N General: N/A ETCS: New applications could be identified. TMS: New applications could be identified. C-DAS: New applications could be identified.

Y

RIS-0792-CCS Iss 1 Level Crossing Operational Interfaces with Trains

Y Major Y N N/A Y N N/A Y General: The document applies only to current conventional arrangements. ETCS: The ETCS and cab-signalling interface to level crossings could involve change of mode, cab indications in certain cases and use with lineside indications and signs where they remain. A document of some 25 pages could be required to address the ETCS interfaces. TMS: Some additions for TMS are implied. C-DAS: C-DAS may be supressed on the approach to Level Crossing.

Y

RIS-0794-CCS Iss 2 GSM-R Train Voice Radio Systems N N/A N N N/A Y N N/A N General: N/A ETCS: N/A TMS: The TMS system definition document ref 153821-NWR-REP-ESE-000004 para 5.5.2 requires that voice communication interfaces are to be part of TMS. The standard will need to define the GSM-R system facilities to be provided. C-DAS: N/A

Y

RIS-0796-CCS Iss 1 Train to Infrastructure RFID Compatibility

N N/A N N N/A N N N/A N General: It is not possible that RFID derived data is ultimately not used in the TMS. However, the standard addresses the physical detail of RFID tags and readers, not the use of the data. As the base assumption is that the data is fed to stakeholder (Inc. NR) systems independent of the TMS. The DRS system definition document (figure 1) shows interfaces to independent business systems, but these are limited to the TMS. ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-0797-CCS Iss 1 ERTMS/ETCS Baseline 3 Onboard Subsystem Requirements: Retrofit

N N/A N N N/A N N N/A Y General: Considered fit for purpose. ETCS: N/A TMS: N/A C-DAS: C-DAS will require the same type of

Y

Page 39 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

document. A check will be made to determine if one is planned.

RIS-0798-CCS Iss 1 ERTMS/ETCS Baseline 3 Onboard Subsystem Requirements: New Trains

N N/A Y N N/A N N N/A Y General: N/A ETCS: Considered functionally complete, but experience may indicate that some of the traction power and isolation related requirements will need to evolve. TMS: N/A C-DAS: C-DAS will require the same type of document. A check will be made to determine if one is planned.

Y

RIS-1530-PLT Iss 6 Rail Industry Standard for Technical Requirements for On-Track Plant and their Associated Equipment and Trolleys

Y Minor Y N N/A N N N/A Y General: N/A ETCS: On-Track plant qualifying as rail vehicles will require cab signalling and possibly ATP functions. Additional sections are required for both of these unless they are to be operated under special instructions when self-powered in normal traffic (travelling). TMS: N/A C-DAS: These vehicles could require some C-DAS functionality if the operators thought it to be beneficial.

Y

RIS-1700-PLT Iss 3 Rail Industry Standard for Safe Use of Plant for Infrastructure Work

Y Minor N N N/A N N N/A N General: It is thought unlikely that C-DAS equipment could be involved. ETCS: Para 4.1.1.5 does not refer to AWS or TPWS equipment that is fixed to one or more sleepers. If this were to be included, then ETCS track equipment should be mentioned. Any onboard ETCS equipment could require programmed inspection. TMS: N/A C-DAS: N/A

Y

RIS-1701-PLT Iss 4 Rail Industry Standard for Portable and Transportable Plant Used for Infrastructure Work


N

RIS-1702-PLT Iss 2 Rail Industry Standard for the Design of On- track Machines in Working and Travelling Modes

Y Minor Y Y Minor Y Y Minor N General: The document does not address signalling, but includes data recording. It is thought that it should address the policy for onboard ETCS and C-DAS equipment. ETCS: See above TMS: Knowledge of plant characteristics will be useful. C-DAS: See above.

Y

RIS-1710-PLT Iss 2 Engineering Certification of Railborne Plant and the Assessment of Non-Railborne Plant

N N/A N Y Minor Y N N/A N General: See TMS ETCS: N/A TMS: It is thought possible that a control centre may need to be aware of any limitations or conditions on the use of plant. C-DAS: N/A

Y

RIS-1800-ENE Iss 1 Rail Industry Standard for Network and Depot Interface Management - Isolation Documentation

N N/A N N N/A Y N N/A N General: This document refers to electrification. ETCS: N/A TMS: The standard does not currently include any interface requirements to a control centre. It seems likely that with the integrated features that are part of the TMS that this will change. C-DAS: N/A

Y

Page 40 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

RIS-1854-ENE Iss 1 750 V and 1500 V DC Overhead Lines and corresponding Rolling Stock requirements

N N/A Y N N/A Y N N/A N General: ETCS, and by definition the TMS system, are capable of providing automation functions for traction power switching. ETCS: See above. Packet 44 may be pertinent. TMS: Where the requirements of a route are not met by a vehicle, the entry of the vehicle into the route can be prevented under normal operations or special operations put in place. C-DAS: N/A

Y

RIS-1855-ENE Iss 1 Low Voltage Power Supplies in Electrified Areas

N N/A N N N/A Y N N/A N General: N/A ETCS: N/A TMS: The standard does not currently include any interface requirements to a control system for monitoring purposes. It seems likely that with the integrated features that are part of the TMS that this will change. C-DAS: N/A

Y

RIS-2003-RST Iss 1 Certification and Registration of Heritage Rail Vehicles Operating on the GB Mainline Railway

N N/A N N N/A Y N N/A N General: The document does refer to in appendix B "safety systems" requiring to be confirmed to be operational. Specific requirements are not expected to be contained in this document. For C-DAS, always an option but not seen to be a requirement. ETCS: N/A TMS: When there are routes that do not have conventional signalling the control centre will require knowledge of the train fitment to manage re-routing if it should be required. C-DAS: N/A

Y

RIS-2004-RST Iss 1 Rail Vehicle Maintenance Y Minor Y N N/A N N N/A N General: The document makes adequate reference to onboard signalling and communications equipment. ETCS: However, the reference to speed measurement equipment appears inadequate. ETCS speed measurement requirements have a different specification and will include systems other than tachos, particularly for accuracy and slip/slide precautions. TMS: N/A C-DAS: N/A

Y

RIS-2273-RST Iss 2 Post Incident and Post Accident Testing of Rail Vehicles

Y Major Y N N/A N Y Minor N General: The document makes a general reference to signalling, but has no detailed requirements. ETCS: It gives some attention to speed measurement, which in an ETCS context should be seen as part of the onboard signalling system. When restructured for ETCS the document should evolve in a significant way. The braking interfaces with ETCS will require more attention. The DMI will also require attention. TMS: N/A C-DAS: It could be necessary to consider whether any C-DAS information could have been a factor.

Y

RIS-2453-RST Iss 1 Vehicle Registration, Marking and Numbering

Y Minor Y N N/A N Y Minor Y General: This document requires a review to determine to what extent the onboard equipment, i.e. ETCS options and status, other signalling equipment and C-DAS equipment should be reflected in the vehicle registration, marking and numbering. The additions could be extensive.

Y

Page 41 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

ETCS: See above. TMS: N/A C-DAS: See above.

RIS-2700-RST Iss 1 Rail Industry Standard for Verification of Conformity of Engineering Change to Rail Vehicles

N N/A Y N N/A N N N/A Y General: In its scope, this document certainly should include onboard signalling equipment and its signalling interfaces. There is no mention of conventional signalling and control systems, so their inclusion represents a significant extension. ETCS: See above. TMS: N/A C-DAS: See above.

Y

RIS-2701-RST Iss 1 Rail Industry Standard for NDT Processes on Rail Vehicles


N

RIS-2702-RST Iss 2 In-Service Examination and Reference Limits for Freight Wagons


N

RIS-2703-RST Iss 2 Driver Controlled Operation (DCO) On-Train Camera/Monitors (OTCM)


N

RIS-2704-RST Iss 1 Rail Industry Standard for Wheelsets Handling and Storage


N

RIS-2705-RST Iss 2 Rail Industry Standard for Crippling and Release of Freight Wagons


N

RIS-2706-RST Iss 1 Rail industry Standard for recording of Rolling Stock Data

Y Minor N N N/A N N N/A Y General: The document includes provision of ETCS as ERTMS and GSM-R and this is intended for UK purposes. It would seem that the sharing of data on interoperable systems will have to be undertaken on a European scale. ETCS: See above. TMS: N/A C-DAS: It seems probable that the C-DAS fitment should be recorded.

Y

RIS-2708-RST Iss 1 Rail Industry Standard Freight Technical Committee Audit Protocol

N N/A Y N N/A N N N/A N General: The standard is addressed to wagons, but appears to be equally applicable to locomotives, but this is not clear. If applicable to locomotives it is also applicable to ETCS and a mention may be necessary (unless the maintenance of locomotives is dealt with in another document). ETCS: See above. TMS: N/A C-DAS: N/A

Y

RIS-2709-RST Iss 1 Rail Industry Standard for the Identification of Roller Bearings Defects


N

Page 42 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

RIS-2710-RST Iss 1 Magnetic Track Brakes Y Minor N N N/A N N N/A N General: N/A ETCS: Only Ansaldo balises are listed in the annexes. There are others. The onboard balise readers are not mentioned. TMS: N/A C-DAS: N/A

Y

RIS-2747-RST Iss 1 Functioning and Control of Exterior Doors on Passenger Vehicles

N N/A Y N N/A N N N/A N General: Only if SDO is accommodated in the ETCS as a standard function will a change be required for ETCS. No role for TMS foreseen. ETCS: This is a function that could be implemented by packet 44. TMS: N/A C-DAS: N/A.

Y

RIS-2750-RST Iss 1 Supplier Assurance N N/A N N N/A N N N/A N General: This document has relevance to all supply activities. ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-2766-RST Iss 1 Rail Industry Standard for Wheelsets

N N/A Y N N/A N N N/A Y General: There is a need for some modern onboard systems to be quite accurate with wheel diameter measurement. This document does not seem to be the best place to address this. ETCS: See above. TMS: N/A C-DAS: See above.

Y

RIS-2770-RST Iss 1 Movement of Continental Wagons on the GB Network

N N/A N N N/A Y N N/A N General: N/A ETCS: N/A TMS: The TMS may need to have data describing the train consist and any limitations that result from specific wagons. Perhaps the needs of the TMS will have to be referenced in the document. C-DAS: N/A

Y

RIS-2773-RST Iss 1 Format for Vehicle Gauging Data N N/A N N N/A N N N/A N General: This document sets out gauging practice before the derivation of ETCS-type or RA-type information. A new document is recommended. ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-2777-RST Iss 1 Functionality and Management of Track Circuit Assisters (TCAs) on Rail Vehicles

N N/A N Y Minor Y N N/A N General: N/A ETCS: N/A TMS: there could be a need for TMS to know which vehicles are fitted should train re-routing be required. C-DAS: N/A

Y

RIS-2790-RST Iss 1 Rail Industry Standard for Compatibility for Rail Vehicle Couplings and Interconnectors

N N/A N Y Minor Y N N/A N General: N/A ETCS: N/A TMS: Knowledge of the compatibility of vehicles would need to be part of TMS. Section 3 could need development. C-DAS: N/A

Y

RIS-2795-RST Iss 2 Track to Train RFID Compatibility N N/A N N N/A N N N/A N General: Interference with Eurobalise frequencies is not expected. ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 43 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

RIS-3118-TOM Iss 1 Incident Response Planning & Management

N N/A N N N/A N N N/A N General: This document sits above the details of CCS systems. ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-3119-TOM Iss 2.1 Rail Industry Standard for Accident and Incident Investigation

Y Minor Y N N/A N N N/A N General: N/A ETCS: The document mentions ERTMS in a couple of places. However, the section on SPADs is about conventional signalling and should a SPAD occur under ETCS control a different approach is required and different reasons are implied. There will be (has to be) a European obligation to report ETCS related incidents and this will have to be added. There should also be a more informal requirement to share "lessons learnt". These comments suggest changes to appendices L and P, and perhaps a new section on European reporting. Forms RT3119C/D have been produced for ERTMS/ETCS SPADS. TMS: N/A C-DAS: N/A

Y

RIS-3215-TOM Iss 1 Weekly Operating Notice, Periodical Operating Notice and the Sectional Appendix


N

RIS-3279-TOM Iss 1 High Visibility Clothing N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-3350-TOM Iss 1 Communication of Urgent Operating Advice


N

RIS-3413-TOM Iss 2 Provision of Information and Signs for Access on the Railway


N

RIS-3436-TOM Iss 1 Information for Safe Train Operation Y Major N N N/A Y N N/A Y General: N/A ETCS & GSM-R: Where the rail vehicle is a locomotive or includes a multiple unit cab there would seem to be a need to enhance this standard to set out the type of ETCS and radio fitment, and C-DAS compatibility. Labels for the failure of safety critical equipment would seem to be necessary, although AWS /TPWS does not seem to be included. TMS: TMS should include the facilities to enter and distribute the information required, but there would have to be back-up arrangements in the event this feature has failed. C-DAS: See above.

Y

RIS-3437-TOM Iss 2 Defective On-Train Equipment Y Minor Y N N/A N N N/A N General: N/A ETCS: This document attempts to cater for ETCS. It would seem that it needs some revision. A number of issues arise: 1. The detail of the operations to undertake in the event of failure: not clear enough in some cases. 2. The effect and significance of a failure of

Y

Page 44 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

speedometer and vigilance/DSD. 3. The cab display(s) fail with a working ATP. 4. The relationship between ETCS failures and AWS/TPWS failures. TMS: N/A C-DAS: N/A

RIS-3440-TOM Iss 2 Operation of Heritage Trains Y Minor N N N/A Y N N/A Y General: This document does not refer to CCS equipment, neither conventional nor ETCS or C-DAS, although conventional radio and signalling equipment is fitted at least on some items of heritage traction. These matters may be covered elsewhere and a check will be made. ETCS: See above. TMS: See above. C-DAS: See above.

Y

RIS-3451-TOM Iss 1 Train Drivers - suitability and Medical Fitness Requirements

Y Minor N N N/A N Y Minor N General: The use of in-cab display screens for signalling purposes could increase the requirement for near field vision to be as effective as far field, without the need to exchange or add or remove visual aids. TMS is not concerned with driver requirements. ETCS: The ability to hear warning and information sounds emitted by the ETCS and C-DAS systems should be included. TMS: N/A C-DAS: C-Das requirements are considered to be covered by ETCS requirements.

Y

RIS-3452-TOM Iss 1 Train Movement - Medical Fitness Requirements

N N/A Y N N/A Y N N/A Y General: The document needs to be written in terms of the displays used for TMS, ETCS, Radio and handheld displays and the light and sounds that they emit, as well as the conventional needs for far distance sight and hearing. ETCS: As above. TMS: As above. C-DAS: As above. GSM-R: As above.

Y

RIS-3600-TOM Iss 1 Operational Security Response Planning

N N/A Y N N/A Y N N/A Y General: There is a need to set out the threat from IT-based attacks and mandate the measures to be used to combat this threat. The identification of the need for key-point protection should also be added. ETCS: See above. TMS: See above. C-DAS: See above.

Y

RIS-3701-TOM Iss 1 Rail Industry Standard for a Confidential Reporting System for Rail Staff


N

RIS-3702-TOM Iss 2 Rail Industry Standard for Management of Route Knowledge for Drivers, Train Managers, Guards and Driver Managers

Y Major Y N N/A Y N N/A Y General: ETCS, C-DAS and GSM-R, it can be argued, should reduce the need for route knowledge. A driver can readily obtain advice via the radio, which provides an availability of communication that the railway has never had. On the other hand when one of these systems fails fallback arrangements have to be employed that (should be) are never called upon in normal service. Yet competency is required as, of course, some failures can be expected to occur. A shift from conventional route knowledge to an

Y

Page 45 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

emphasis on competence in handling degraded conditions could result. These considerations can be expected to change the emphasis for route knowledge and the manner in which it is prepared: more prepared contingency plans for example held on mobile devices. ETCS: See above. TMS: The loss of a modern control point can be expected to have a severe effect upon a wide geographic area. At the minimum it needs to possible for trains to safely reach a point where de-training of passengers can be safely undertaken, and without unreasonable delay. C-DAS: see above.

RIS-3703-TOM Iss 3 Passenger Train Dispatch and Platform Safety Measures

Y Minor Y Y Minor Y Y Minor N General: A detailed document that will need much change to accommodate ETCS and possibly TMS deployment. In the first instance it is reasonable to expect these projects to be resolving the issues introduced by them, but the standard itself will still need development. ETCS: See above. TMS: See above. C-DAS: Dwell times could be modified.

Y

RIS-3708-TOM Iss 2 Arrangements Concerning the Non- Operation of Track Circuits During the Leaf Fall Contamination Period

N N/A N N N/A N N N/A Y General: N/A ETCS: N/A TMS: N/A C-DAS: The speed display value may need reducing. The control room predictive algorithm will need to take the lower speed into account.

Y

RIS-3751-TOM Iss 3 Rail Industry Standard for Train Driver Selection


N

RIS-3776-TOM Iss 1 Rail Industry Standard on the Use of Mobile Telephonic Equipment in Driving Cabs


N

RIS-3780-TOM Iss 1 Operational Requirements for GSM-R Radio

N N/A Y N N/A N N N/A Y General: The document is written in the context of voice communication only. It requires additional text to accommodate the use of radio for data exchange. This may consider the use of more than one radio and the requirements on the infrastructure equipment. A separate document could be preferred. ETCS: Data transmission should be set out. TMS: N/A C-DAS: Data transmission if to be used for C-DAS should be set out.

Y

RIS-4472-RST Iss 1 Engineering Requirements for Steam Locomotives and other Heritage Rail Vehicles

Y Minor N N N/A N N N/A Y General: Train safety system are referenced. ETCS: ETCS needs to be added. TMS: N/A C-DAS: C-DAS if to be used for heritage movements needs to be added.

Y

RIS-7016-INS Iss 1 Interface between Station Platforms, Track, Trains and Buffer Stops

N N/A Y N N/A N N N/A N General: N/A ETCS: The risk assessment should take into account the protection afforded by the ATP function of ETCS if all trains using the station are fitted.

Y

Page 46 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

RIS-7700-INS Iss 3 Rail Industry Standard for Station Infrastructure

N N/A Y N N/A N N N/A N General: N/A ETCS: The risk assessment should take into account the protection afforded by the ATP function of ETCS if all trains using the station are fitted. TMS: N/A C-DAS: N/A

Y

RIS-7701-INS Iss 1 Rail Industry Standard for Automatic Ticket Gates at Stations


N

RIS-7702-INS Iss 1 Rail Industry Standard for Lighting at Stations


N

RIS-7704-INS Iss 1 Calculation of Enhanced Permissible Speeds for Tilting Trains


N

RIS-8012-CCS Iss 1 Controlling the Speed of Tilting Trains through Curves

N N/A N N N/A N N N/A N General: It is believed that this function is NOT part of the standard ETCS toolbox. It is implemented as Packet 44. It is not thought that this function would become part of the core ETCS, as it would be a major data modification. ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-8019-CCS Iss 1 Tilting Trains: Controlling Tilt Systems to Maintain Clearances

N N/A N N N/A N N N/A N General: It is believed that this function is NOT part of the standard ETCS toolbox. It is implemented as Packet 44. ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-8034-CCS Iss 1 Maintenance of Signal and Operational Sign Visibility

Y Minor N N N/A N N N/A N General: The document addresses conventional lineside signals and signs. ETCS: Para 2.1.1 needs the inclusion of ETCS stop markers, unless these are to be considered included in the meaning of signs. TMS: N/A C-DAS: N/A

Y

RIS-8040-TOM Iss 1 Low Adhesion between the Wheel and the Rail - Managing the Risk

N N/A Y N N/A Y N N/A Y General: See below. ETCS: ETCS introduces the possibility of amending the train brake rate for protection purposes. It could be implemented by the TMS. This feature should be part of this standard. It has implications for ETCS, TMS and C-DAS. TMS: See above. C-DAS: See above.

Y

RIS-8046-TOM Iss 1 Spoken Safety Communications N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

RIS-8047-TOM Iss 2 Reporting of Safety Related Information


N

Page 47 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

RIS-8048-CCS Iss 1 Positioning of Lineside Telephones Y Minor N Y Minor N N N/A N General: The document requires updating for ETCS and operational purposes. It is possible that the installation of GSM-R will lead to the requirements for most telephones to be withdrawn. ETCS: See above. TMS: See above. C-DAS: N/A

Y

RIS-8060-CCS Iss 1 Engineering Requirements for Dispatch of Trains from Platforms


N

RIS-8070-TOM Iss 1 Testing Railway Safety Critical Workers for Drugs and Alcohol


N

RIS-8072-CCS Iss 1 ERTMS National Identities Management


N

RIS-8217-TOM Iss 1 Introduction and Use of Axle Counters - Managing the Risk


N

RIS-8250-RST Iss 1 Reporting High Risk Defects Y Minor N N N/A N N N/A N General: N/A ETCS: ETCS equipment should be covered by a similar requirement. TMS: N/A C-DAS: N/A

Y

RIS-8270-RST Iss 1 Route Level Assessment of Technical Compatibility between Vehicles and Infrastructure

Y Minor N N N/A N N N/A Y General: N/A ETCS: The document includes references to ETCS/ERTMS. These are not of the detail that allows compatibility between various versions of ETCS or its data to be assured. These issues will need review as the project proceeds. TMS: N/A C-DAS: See ETCS.

Y

RS100 Iss 1 Good Practice Guide on Competence Development

Y Minor N Y Minor N Y Minor N General: The increase in in-cab screens associated with ETCS should be reflected in the text of this document. There is scope for a section on the introduction of new technologies into the working environment. ETCS: Examples of competence work with ETCS-type screens could be given. I expect there are some. TMS: Likewise, TMS screens can be expected to become more numerous (more options) and again should figure in the text. C-DAS: C-DAS should not in itself be as complex as ETCS, but it will be another screen in the cab which will be quite different from the past.

Y

RS232 Iss 1 Good Practice Guide on Cognitive and Individual Risk Factors

Y Minor Y N N/A Y Y Minor Y General: The document is a general presentation of human factors set in the context of train driving. Mention is made of drivers, signallers, possessions, AWS, some failure modes, and

Y

Page 48 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

lineside signals, but in the context of the pre-digital railway. ETCS: The causes of error in reading screens should be addressed. Much of the rest will remain valid, but the ETCS context should be prominent. The discussion on SPADs in the context of ATP is less critical, but the situations (failure and operational) when the ATP is not active will occur regularly, and if less often and so less practised where does that leave competence? Very important to address these issues. TMS: Control centres and signallers are becoming different places. A section on driving and a section on control centres may be appropriate. C-DAS: HF will have an important role to play in C-DAS. An early contribution from a revision of this document could be important.

RS504 Iss 1 Fatigue Management - A Good Practice Guide

N N/A Y N N/A Y N N/A Y General: A thorough document but in the context of the emphasis on screens in the working environment an understanding of fatigue seems to be relevant and should be added. ETCS: See above. TMS: See above. C-DAS: See above.

Y

RS800 Iss 1 Managing drivers on routes undergoing significant change.

N N/A Y N N/A N N N/A Y General: This document is up to date and thorough at a non-specific level. For ETCS and C-DAS project specific documents are needed. ETCS: See above. TMS: N/A C-DAS: See above.

Y

Form NR3180 Iss 12-18 Line Blockage Form Y Minor N N N/A N N N/A N General: introduction of SCWS and TMS will likely remove the need for this form. It is currently up to date for ETCS. ETCS: The term 'Block Marker' is used but the widely used European term is 'Stop Marker'. Decision should be made as to whether consistency with Europe or current term used in UK is maintained. Additional protection to be reviewed to ensure all possibilities are listed. TMS: N/A C-DAS: N/A

Y

Form NR3189 Iss 1 Signal Passed at Danger (SPAD) or Train Trip or Unauthorised Movement


N

Form NR3190 Iss 1 Emergency Special Working Ticket Y Major N N N/A N N N/A N General: N/A ETCS: The term 'Block Marker' is used but the widely used European term is 'Stop Marker'. Decision should be made as to whether consistency with Europe or current term used in UK is maintained. TMS: N/A C-DAS: N/A

Y

Form RT3112 12-03 Blocking of Lines for Electric Traction Purposes - AE Form


N

Form RT3113 12-03 Blocking of Lines for Electric Traction Purposes - AT Form


N

Page 49 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

Form RT3114 12-03 Blocking of Lines for Electric Traction Purpose - AS Form


N

Form RT3116 12-18 Overhead Line Permit N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Form RT3154 12-03 Pilotman's Form for Working of Single Lines and Bi-Directional Lines by Pilotman


N

Form RT3154 ERTMS Iss 06-13 Pilotman's form for working of single and bi directional ERTMS lines by pilotman

Y Major N N N/A N N N/A N General: Other fallback arrangement may be preferred in ETCS. ETCS: 'In connection with…' currently has two options, one of which is 'failure of signalling equipment'. If it is agreed that signalling equipment encompasses all the new ETCS technology, then no change required. If not, it will require rewording. TMS: N/A C-DAS: N/A

Y

Form RT3155 12-03 Signaller's Form for Working of Single and Bi-Directional Lines by Pilotman


N

Form RT3155 ERTMS Iss 06-13 Signaller's form for working of single and bi- directional ERTMS lines by pilotman

Y Major N N N/A N N N/A N General: Other fallback arrangement may be preferred in ETCS. ETCS: 'In connection with…' currently has two options, one of which is 'failure of signalling equipment'. If it is agreed that signalling equipment encompasses all the new ETCS technology, then no change required. If not, it will require rewording. TMS: N/A C-DAS: N/A

Y

Form RT3156 ERTMS Iss 06-13 Driver's ticket for working of single and bi- directional ERTMS lines by pilotman

Y Major N N N/A N N N/A N General: Other fallback arrangement may be preferred in ETCS. ETCS: The term 'Block Marker' is used but the widely used European term is 'Stop Marker'. Decision should be made as to whether consistency with Europe or current term used in UK is maintained. Additional protection to be reviewed to ensure all possibilities are listed. TMS: N/A C-DAS: N/A

Y

Form RT3156 Iss 3 Drivers Ticket for Working of Single and Bi- Directional Lines by Pilotman


N

Form RT3177 Iss 6 Modified Working Arrangements Driver's Ticket

Y Major N N N/A N N N/A N General; N/A ETCS: the form only references Signals and mph. It should be reviewed to take into account references to 'Block/Stop Markers' and km/h.

Y

Page 50 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

Form RT3183 Iss 06-14 Agent's Point Setting Form N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Form RT3184 Iss 12-14 Temporary Block Working Ticket Y Major N N N/A N N N/A N General: N/A ETCS: the form only references Signals and mph. It should be reviewed to take into account references to 'Block/Stop Markers' and km/h. TMS: N/A C-DAS: N/A

Y

Form RT3185 Iss 12-15 Reporting a signal / AWS / TPWS / ATP / TVM failure or irregularity

Y Major N N N/A N N N/A N General: N/A ETCS: The term 'Block Marker' is used but the widely used European term is 'Stop Marker'. Decision should be made as to whether consistency with Europe or current term used in UK is maintained. TMS: N/A C-DAS: N/A

Y

Form RT3186 Iss 12-13 Release of signalling controls Y Major N Y Major N N N/A N General: May require new form to be created for ERTMS lines or current form to be updated in accordance with the points raised below. ETCS: the form only references Signals. It should be reviewed to take into account references to 'Block/Stop Markers'. Where 'interlocking' is referenced it should be updated to include 'RCB area' TMS: If it is agreed that signalling controls encompasses all the new TMS technology then no change required. If not, it will require rewording. C-DAS: N/A

Y

Form RT3187 Iss 12-13 Signal engineering work Y Major N Y Major N N N/A N General: N/A ETCS: The form references Signals. It should be reviewed to take into account references to 'Block/Stop Markers TMS: 'confirmation with other signallers' section could potentially reference TMS dependent on how it is deployed. May be confirmed to another signaller in an automated/digitised way instead of 'told'. C-DAS: N/A

Y

Form RT3188 02-05 Activation of TPWS other than a signal passed at danger (SPAD)

Y Major N N N/A N Y Major N General: Potential for the whole form to change or a new one created alongside current form as the automatic brakes would be conducted via ETCS itself. ETCS: Automatic brakes would be conducted via ETCS itself. The form only references Signals. It should be reviewed to take into account references to 'Block/Stop Markers'. TMS: N/A C-DAS: May need to reference a reason being faulty CDAS equipment.

Y

Form RT3191 Iss 12-16 Pilotman's Single Line Working Form

Y Major N N N/A N N N/A N General: N/A ETCS: The form only references mph. It should be reviewed to take into account references to km/h. TMS: N/A C-DAS: N/A

Y

Page 51 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Form RT3192 Iss 06-14 Signaller's Single Line Working Form

Y Major N N N/A N N N/A N General: N/A ETCS: The form only references mph. It should be reviewed to take into account references to km/h. TMS: N/A C-DAS: N/A

Y

Form RT3193 Iss 12-14 Driver's Single Line Working Ticket Y Major N N N/A N N N/A N General: N/A ETCS: Reference to the block marker needs to be included. TMS: N/A C-DAS: N/A

Y

Form RT3198 ERTMS Iss 12-15 Possession arrangements form (T3 ERTMS)

Y Major N N N/A N N N/A N General: Introduction of SCWS or TMS will likely make this an automated process so no need for the form. ETCS: Section that states 'Possession to be taken around train at signal' - should also reference block/stop marker. TMS: N/A C-DAS: N/A

Y

Form RT3198 Iss 12-14 Possession Arrangements Form N N/A N N N/A N N N/A N General: it is derisible to avoid making control centre equipment safety critical. TMS safety related system may be introduced on a non ETCS line and may use a different protection arrangement then current options presented. ETCS: N/A TMS: N/A C-DAS: N/A

N

Form RT3199 ERTMS Iss 12-15 Engineering Supervisor's Certificate N N/A N N N/A N N N/A N General: The introduction of TMS - safety means we will take possessions differently so the form may become void. ETCS: N/A TMS: N/A C-DAS: N/A

N

Form RT3199 Iss 12-14 Work-site Certificate N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Form RTWO01 Iss 12-13 Written Order 01 Permission To Start In SR Or To Pass An EOA Form


Y

Form RTWO02 Iss 12-13 Written Order 02 Permission to Proceed After Train Trip Form


Y

Form RTWO03 Iss 12-13 Written Order 03 Instruction to Run At Caution Form

Y Major N N N/A N N N/A N General: N/A ETCS: The term 'Block Marker' is used but the widely used European term is 'Stop Marker'. Decision should be made as to whether consistency with Europe or current term used in

Y

Page 52 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

UK is maintained. TMS: N/A C-DAS: N/A

Form RTWO04 Iss 12-13 Written Order 04 Permission to Make a Wrong-Direction Movement Form


Y

Form RTWO05 Iss 12-13 Written Order 05 Permission To Proceed Under Modified Working Arrangements on Single and Bi-Directional Lines Form


Y

GERT8000-AC Iss 5 AC electrified lines Y Minor N N N/A N N N/A N General: Terminology should be consistent with current ETCS language (Block Marker vs Stop Marker). -Section 11.3 Should be updated to include "all lineside signs and DMI indications" ETCS: See above. TMS: N/A C-DAS: N/A

Y

GERT8000-DC Iss 4 DC electrified lines N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-G1 Iss 6 General safety responsibilities and personal track safety for non-track workers

Y Minor N N N/A N Y Minor N General: N/A ETCS/CDAS: Communication examples between signaller and driver to potentially include display screen messages. TMS: N/A

Y

GERT8000-Gloss Iss 5 Glossary of Railway Terminology N N/A N N N/A N N N/A N General: None of the terms used in the O&M CRS appear in the glossary (some may not need to - will require more in-depth analysis). ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-HB1 Iss 4 General duties and track safety for track workers

Y Minor N N N/A Y N N/A N General: Updates to align with the introduction of new safety systems. ETCS: If a new safety system is introduced as identified by the current system definition (SCWS), Section 5.6 will need to be updated. TMS: If TMS protection is used there may be additional considerations for Signallers and workers when undertaking possessions. C-DAS: N/A

Y

GERT8000-HB10 Iss 4 Duties of the COSS or SWL and person in charge when using a hand trolley


N

GERT8000-HB11 ERTMS Iss 2 Duties of the person in charge of the possession (PICOP) on ERTMS

Y Minor N N N/A Y N N/A N General: Currently up to date, however, new safety systems will likely enable a change.

Y

Page 53 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

lines where lineside signals are not provided

ETCS: Possessions may be able to be taken independently of the Signaller which would result a complete module update. TMS: The TMS may require other methods for handback. C-DAS: N/A

GERT8000-HB11 Iss 6 Duties of the person in charge of the possession (PICOP)

N N/A N N N/A Y N N/A N General: Current forms may not be used as the procession could be taken using digital means. ETCS: N/A TMS: Section 4.1, planned possessions may be automatic with the introduction of SCWS and TMS Protection. C-DAS: N/A

Y

GERT8000-HB12 ERTMS Iss 2 Duties of the engineering supervisor (ES) or safe work leader (SWL) in a possession on ERTMS lines where lineside signals are not provided

N N/A N N N/A Y N N/A N General: Updates to align with the introduction of new safety systems. ETCS: N/A TMS: If TMS protection is used there may be additional considerations for Signallers and workers when undertaking possessions. Automation of taking possessions. C-DAS: N/A

Y

GERT8000-HB12 Iss 6 Duties of the engineering supervisor (ES) or safe work leader (SWL) in a possession

N N/A N N N/A N N N/A N General: Update general details if forms become digital records. ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-HB13 Iss 2 Duties of the person in charge of the siding possession (PICOS)

N N/A N N N/A Y N N/A N General: N/A

ETCS: N/A TMS: If TMS protection is used there may be additional considerations for Signallers and workers when undertaking possessions. Automation of taking possessions C-DAS: N/A

Y

GERT8000-HB14 Iss 2 Duties of the person in charge of loading and unloading rail vehicles during engineering work


N

GERT8000-HB15 ERTMS Iss 3 Duties of the machine controller (MC) and on-track plant operator on ERTMS lines where lineside signals are not provided


N

GERT8000-HB15 Iss 5 Duties of the machine controller (MC) and on-track plant operator


N

GERT8000-HB16 Iss 4 AC electrified lines N N/A Y Y Minor N N N/A N General: N/A ETCS: Section 10, If specified the symbols are available on the DMI TMS: Section 10, If specified the symbols are available on the DMI via the ETCS trackside through the TMS signalling Control Layer. C-DAS: N/A

Y

GERT8000-HB17 Iss 3 DC electrified lines N N/A N N N/A N N N/A N General:N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 54 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GERT8000-HB18 Iss 4 Duties of a level crossing attendant N N/A N N N/A Y N N/A N General: Automatic system may be introduced. ETCS: N/A TMS: Potentially with the introduction of TMS and the TMS protection layer or SCWS. C-DAS: N/A

Y

GERT8000-HB19 Iss 3 Work on signalling equipment - duties of the signalling technician

N N/A N N N/A Y N N/A N General: Forms may become digitalised. ETCS: N/A TMS: Unavailable equipment will need to be captured to enable the TMS to appropriately replan. C-DAS: N/A

Y

GERT8000-HB2 Iss 2 Instructions for track workers who use emergency protection equipment

N N/A Y N N/A Y N N/A N General: A TMS or ETCS integrated safety system such as SCWS will change emergency stop procedures. ETCS: See above. TMS: See above. C-DAS: N/A

Y

GERT8000-HB20 Iss 2 General duties of a safe work leader (SWL) working outside a possession

Y Minor N N N/A Y N N/A N General: N/A ETCS: Update section 4.7 for use of SCWS. TMS: Update section for use of TMS Protection. C-DAS: N/A

Y

GERT8000-HB21 Iss 4 Safe work leader (SWL) blocking a line

N N/A N Y Minor N N N/A N General: N/A ETCS: N/A TMS: Sections 3, 5 Granting/ handing back of the Line blockage might not be through the Signaller but via automation on a separate device. C-DAS: N/A

Y

GERT8000-HB3 Iss 3 Duties of the lookout and site warden

Y Minor N N N/A N N N/A N General: N/A ETCS: If SCWS is introduced section 4, 5, 6 and 7 may need an update. TMS: N/A C-DAS: N/A

Y

GERT8000-HB4 Iss 2 Duties of a points operator and route- setting agent - moving and securing points by hand

N N/A N N N/A N N N/A N General: If a DMWS (Degraded Mode Working System) is introduced but this is not included as part of the SoS. ETCS: N/A TMS: N/A C-DAS: N/A

Y

GERT8000-HB5 Iss 2 Handsignalling duties N N/A N N N/A N N N/A N General: If a DMWS (Degraded Mode Working System) is introduced but this is not included as part of the SoS. ETCS: N/A TMS: N/A C-DAS: N/A

Y

GERT8000-HB6 Iss 5 General duties of an individual working alone (IWA)

Y Minor N N N/A N N N/A N General: N/A ETCS: section 3.3 blocking the line will need to refer to marker boards TMS: N/A C-DAS: N/A

Y

GERT8000-HB7 Iss 5 General duties of a controller of site safety (COSS)


N

GERT8000-HB8 Iss 7 IWA, COSS or PC blocking a line Y Minor N Y Minor N N N/A N General: N/A ETCS: Sections 3, 5 Granting/ handing back of the Line blockage might not be through the

Y

Page 55 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Signaller but via automation on a separate device. TMS: Section 5 if the line blockage is taken automatically. C-DAS: N/A

GERT8000-HB9 ERTMS Iss 2 IWA or COSS setting up safe systems of work within possessions on ERTMS lines where lineside signals are not provided


N

GERT8000-HB9 Iss 6 IWA or COSS setting up safe systems of work within possessions


N

GERT8000-Issue HB Iss 10 Rule Book Hand Book Issue History Y Major N Y Major N Y Major N General: Update to capture changes in rulebook for relevant systems. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERM8000-master-module Iss 6

Master Module Manual Y Major N Y Major N Y Major N General: This manual will be updated when relevant system update. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERM8000-possessionworkers Iss 3

Possession Workers Manual Y Major N Y Major N Y Major N General: This manual will be updated when relevant system update. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERM8000- signallersignallingtechnician Iss 6

Signaller and Signalling Technician Manual

Y Major N Y Major N Y Major N General: This manual will be updated when relevant system update. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERM8000-trackworkers Iss 5 Track Workers Manual Y Major N Y Major N Y Major N General: This manual will be updated when relevant system update. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERM8000-traindriver Iss 6 Train Driver Manual Y Major N Y Major N Y Major N General: This manual will be updated when relevant system update. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERM8000- trainoperationsstaff Iss 6

Train Operations Staff Manual Y Major N Y Major N Y Major N General: This manual will be updated when relevant system update. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERT8000-Issue Iss 29 Rule Book Module Issue History Y Major N Y Major N Y Major N General: Update to capture changes in rulebook for relevant systems. ETCS: See above. TMS: See above. C-DAS: See above.

Y

GERT8000-M1 Iss 5 Dealing with a train accident or train evacuation


N

Page 56 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GERT8000-M2 Iss 6 Train stopped by train failure N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-M3 Iss 2 Managing incidents, floods and snow


N

GERT8000-OTM Iss 8 Working of on-track machines (OTM)

Y Minor N Y Minor N N N/A N General: N/A ETCS: An ETCS fitment could be required. It maybe cab signalling only, not an ATP. TMS: Update for TMS dependent on how Traffic Management and possessions are going to work together. Sections that need focussing on are 2, 3 and 4. CDAS: N/A

Y

GERT8000-P1 Iss 6 Single line working Y Minor N N N/A N N N/A N General: N/A ETCS: In ETCS schemes that do not have full bi-directional working, Rule Book Module P1 will need to be reviewed for "Controlling Wrong Direction Movements" - arranging hand signallers opposite Block Markers at locations where the train returns to the proper line; Use of hand signallers where the single line is divided; Route is set and an MA can be issued at the end of the SLW; Review references to clearing and obeying signals and incorporate new diagrams for signals away layout. TMS: N/A C-DAS: N/A

Y

GERT8000-P2 Iss 4 Working single and bi-directional lines by pilotman


N

GERT8000-PoSA Iss 3 Proceed-on-Sight Authority (PoSA) Y Minor Y N N/A N N N/A N General: N/A ETCS: The current PoSA module refers to ERTMS but only applies to an overlay installation. Consideration needs to be given to an ETCS signals away railway where the use of OS MAs does not exactly replicate the meaning of a flashing aspect on a PoSA signal but could be used for the same scenario. Discussion needs to include whether the driver needs to be informed of the reason for the OS MA or not. The meaning is the route is locked, but an MA cannot be given. TMS: N/A C-DAS: N/A

Y

GERT8000-RBBL Iss 32 Rule Book Briefing Leaflet N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-S4 Iss 5 Trains or shunting movements detained on running lines


N

Page 57 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GERT8000-S5 Iss 8 Passing a signal at danger or an end of authority (EoA) without a movement authority (MA)

Y Minor N N N/A N N N/A N General: N/A ETCS: Consideration needs to be given to see whether section 5 (ESW) and section 6 (TBW) are methods of working that can be safely applied on an ETCS signals away railway. TMS: N/A C-DAS: N/A

Y

GERT8000-S7 Iss 3 Observing and obeying fixed signals: Train warning systems: Reporting signalling failures and irregularities

Y Minor Y N N/A N N N/A N General: N/A ETCS: The use of OS MAs has the potential to be used more often to prevent passing an EoA without an MA. Consideration needs to be given for a RB module or other publication explaining the use and meaning of OS MAs in various scenarios and when the driver must be advised of the circumstances. TMS: N/A C-DAS: N/A

Y

GERT8000-SP Iss 5 Speeds N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-SS1 Iss 6 Station duties and train dispatch Y Minor N N N/A N N N/A N General: N/A ETCS: Rule Book Module SS1, section 3 "Train Despatch" needs to be reviewed to ensure safety and appropriateness for an ETCS signals away railway. For example, the heading in section 3.1 is not appropriate and consideration needs to be given to the meaning of an "OFF" indicator which will need be redefined for an ETCS signals away railway. TMS: N/A C-DAS: N/A

Y

GERT8000-SS2 Iss 5 Shunting Y Minor N N N/A N N N/A N General: N/A ETCS: section 5.1"General" should be reviewed to ensure it is safe and appropriate for an ETCS signals away railway. TMS: N/A C-DAS: N/A

Y

GERT8000-T10 Iss 4 Duties of a designated person (DP) and people working on rail vehicles

Y Minor N Y Minor N N N/A N General: N/A ETCS: Update vehicle/line protection in 3.3, 4.3, 5. TMS: Update vehicle/line protection in 3.3, 4.3, 5. C-DAS: N/A

Y

GERT8000-T3 ERTMS Iss 4 Possession of an ERTMS running line for engineering work where lineside signals are not provided

Y Minor N Y Minor N N N/A N General: N/A ETCS: Block marker references, suggest it's changed to Stop Marker in line with the agreed European Term. TMS: Dependent on how TMS will interface with possessions. Will the train register be incorporated into TMS? C-DAS: N/A

Y

GERT8000-T3 Iss 8 Possession of a running line for engineering work

N N/A N Y Minor N N N/A N General: N/A ETCS: N/A TMS: Dependent on how TMS will interface with possessions. Will the train register be incorporated into TMS? If so, sections that should be changed are 1.2, 2, 3, 4, 6, 7 and 8. C-DAS: N/A

Y

Page 58 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GERT8000-TS1 Iss 13 General signalling regulations Y Minor N Y Minor N N N/A N General: Terminology should be consistent with current ETCS language (Block Marker vs Stop Marker). - A thorough review should be undertaken to look at the terms 'Block Marker and EoA' These are sometimes used interchangeably throughout the document, and they mean different things. Specifics: Section 13 requires a review to take into account TMS Protection Sections 17 and 18 should be reviewed to consider whether stopping trains is still necessary if we can apply a TSR ( this might fit neatly in section 22). C-DAS should be not required as a condition for a train to operate. ETCS: See above. TMS: See above. C-DAS: N/A

Y

GERT8000-TS10 Iss 4 ERTMS level 2 train signalling regulations

Y Minor N N N/A N N N/A N General: Terminology should be consistent with current ETCS language (Block Marker vs Stop Marker). - A thorough review should be undertaken to look at the terms 'Block Marker, RSP, and EoA' These are sometimes used interchangeably throughout the document, and they mean different things. ETCS: See above.

TM: N/A C-DAS: N/A

Y

GERT8000-TS11 Iss 3 Failure of, or work on, signalling equipment - signallers' regulations

Y Minor N N N/A N N N/A N General: Terminology should be consistent with current ETCS language (Block Marker vs Stop Marker). In addition, there are currently having a number of LEU balises associated with a signal and behave similarly to a TPWS. ATP equipment is missing, as are power change over balises. ETCS: See above. TMS: N/A C-DAS: N/A

Y

GERT8000-TS2 Iss 5 Track circuit block regulations N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-TS3 Iss 6 Absolute block regulations N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-TS4 Iss 4 Electric token block regulations N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-TS5 Iss 4 Tokenless block regulations N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-TS7 Iss 5 No-signaller token regulations N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 59 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GERT8000-TS8 Iss 4 One-train working regulations N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-TS9 Iss 4 Level crossings - signallers' regulations

Y Minor Y N N/A Y N N/A N General: Terminology should be consistent with current ETCS language (Block Marker vs Stop Marker). - New section required to cover passing over a failed LX in OS mode ETCS: See above. TMS: See above. C-DAS: N/A

Y

GERT8000-TW1 Iss 13 Preparation and movement of trains Y Minor N N N/A N N N/A N General: N/A ETCS: There will be an addition to the Driver-Guard Comms around giving the Ready to Start (RA). There will be an addition to the Permissive Working arrangements. There will need to be an addition to Route and Traction Knowledge. TMS: N/A C-DAS: N/A

Y

GERT8000-TW5 Iss 9 Preparation and movement of trains: Defective or isolated vehicles and on-train equipment

N N/A N N N/A N N N/A N General: For ETCS, Section 4.5 if the AWS is defective or Isolated - add in if overlay is applicable or not. ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-TW7 Iss 7 Wrong-direction movements N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GERT8000-TW8 Iss 8 Level crossings - drivers' instructions


N

GERT8001 Iss 60 Changes to National Operations Publications for December 2018


N

GORT3053 Iss 6.1 Working Manual for Rail Staff Handling and Carriage of Dangerous Goods


N

GORT3053-1 Iss 8.1 Working Manual for Rail Staff Handling and Carriage of Dangerous Goods - Appendix 1 - List of Dangerous Goods with their United Nations Number, Dangerous Goods Class and TOPS Commodity Code

N N/A N N N/A N N N/A N

General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GORT3053-2 Iss 6 Working Manual for Rail Staff Handling and Carriage of Dangerous Goods - Appendix 2 - Bulk Traffic Dangerous Goods, Wagon and Container Separation Distance Requirements / Prohibitions

N N/A N N N/A N N N/A N

General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 60 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

GORT3053-PPBL Iss 4.1 Pink Pages Briefing Leaflet N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

GORT3056 Iss 5 Working Manual for Rail Staff - Freight Train Operations

Y Minor N Y Minor N N N/A N General: ETCS to take into account the need for marshalling of units with translators possibly? ETCS and TMS Out of Gauge loads could be assisted with the control of movements over certain locations where restrictions may apply. ETCS: See above. TMS: See above. C-DAS: N/A

Y

GORT3056-WPBL Iss 2 White Pages Briefing Leaflet N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

RS521 Iss 5 Signals, Handsignals, Indicators and Signs Handbook

Y Minor N N N/A N N N/A N General: System degraded mode must also be considered. ETCS: Signage around the station area may be required for signals away in ETCS operation which would indicate when a MA has been given to the Driver so that the Guard and Station Staff can complete Train Dispatch procedure i.e. replacement for OFF or incorporation of MA within the definition of an OFF indicator. RA procedure may also need to incorporate MA being granted prior to giving the RA. Section 5.8 "Off" indicators and Section 5.10 "Right Away Indicators. TMS: N/A C-DAS: N/A

Y

RS522 Iss 3 AWS and TPWS Handbook Y Minor N N N/A N N N/A N General: N/A ETCS: Additional Guidance required for the operation of AWS/TPWS with ETCS Level 2 overlay. Number of pages for changing is only an estimate and may be higher. Section 1 AWS and Section 2 TPWS. TMS: N/A C-DAS: N/A

Y

RS523 GSM-R Iss 1.2 GSM-R Handbook N N/A N N N/A N N N/A N General: Registration and de-registration where it may impact on ETCS only. This would detail additional clauses around these topic areas. Section 4 Registration and 9 Deregistration (possibly). This is dependent upon the requirements adopted for the registration and de-registration for the ETCS data specification. ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AA01 Iss 1 Commencement of AWS gap N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AA02 Iss 1 Termination of AWS gap N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 61 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Sign AA03 Iss 1 Commencement of special AWS working


N

Sign AA04 Iss 1 Termination of special AWS working N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AA05 Iss 1 Permanently installed AWS cancelling indicator


N

Sign AB01 Iss 1 Warning of the start of cab-signalling


N

Sign AB02 Iss 1 Indication of start of cab-signalling N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AB03 Iss 1 Indication of end of cab-signalling N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AB04 Iss 1 TVM block marker N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AB05 Iss 1 Cab signalling shunt entry board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AB06 Iss 1 Radio electronic token block: loop clear marker


N

Sign AB07 Iss 1 Start / end of cab signalling directional arrows


N

Sign AB08 Iss 1 ETCS stop marker N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AB09 Iss 1 ETCS block marker passable plate N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AC01 Iss 1 Controlled signal identification plate N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AC02 Iss 1 Distant signal sign and identification plate


N

Page 62 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

Sign AC03 Iss 1 Automatic signal sign and identification plate


N

Sign AC04 Iss 1 Semi-automatic signal sign and identification plate


N

Sign AC05 Iss 1 Intermediate block home signal sign and identification plate


N

Sign AC06 Iss 1 CSR alias plate N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AC07 Iss 1 SPAD indicator sign and identification plate


N

Sign AC08 Iss 1 Points indicator sign N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AC09 Iss 1 Ground position light signal identification plate


N

Sign AC10 Iss 1 Points identification plates N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AC11 Iss 1 ETCS identification plate N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AC12 Iss 1 GSM-R alias plate N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AD01k Iss 1 Permissible speed indicators (km/h) N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AD01m Iss 1 Permissible speed indicators (mph) N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AD02k Iss 1 Permissible speed indicators (km/h) for limited clearance


N

Page 63 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Sign AD02m Iss 1 Permissible speed indicators (mph) for limited clearance


N

Sign AD03k Iss 1 Permissible speed warning indicators (km/h)


N

Sign AD03m Iss 1 Permissible speed warning indicators (mph)


N

Sign AD04k Iss 1 Permissible speed warning indicators (km/h) for limited clearance


N

Sign AD04m Iss 1 Permissible speed warning indicators (mph) for limited clearance


N

Sign AD05 Iss 1 Permissible speed directional arrows


N

Sign AE01m Iss 1 Enhanced permissible speed indicators


N

Sign AE02m Iss 1 Enhanced permissible speed indicators (limited clearance)


N

Sign AE03m Iss 1 Enhanced permissible speed warning indicators


N

Sign AE04m Iss 1 Enhanced permissible speed warning indicators (limited clearance)


N

Sign AF01 Iss 1 Emergency indicator N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AF02k Iss 1 Temporary speed restriction warning boards (km/h)


N

Sign AF02m Iss 1 Temporary speed restriction warning boards (mph)


N

Sign AF04k Iss 1 Temporary speed restriction speed indicators (km/h)


N

Page 64 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

Sign AF04m Iss 1 Temporary speed restriction speed indicator (mph)


N

Sign AF05 Iss 1 Temporary speed restriction directional arrows


N

Sign AF06 Iss 1 Temporary speed restriction termination indicator


N

Sign AF07 Iss 1 Temporary speed restriction spate indicator


N

Sign AF08 Iss 1 Temporary speed restriction AWS cancelling indicator


N

Sign AG01 Iss 1 Possession limit board Y Major N N N/A N N N/A N General: N/A ETCS: The sign has been designed as red 'in according with 'Signal red' defined in GK/RT0057'. Would require review in line with any updates to GK/RT0057 on an ETCS railway where 2/3/4 aspect signals don’t exist. TMS: N/A C-DAS: N/A

Y

Sign AG02 Iss 1 Worksite entrance marker N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AG03 Iss 1 Worksite exit marker N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AH01 Iss 1 Level crossing warning sign N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AH02m Iss 1 Open level crossing combined speed restriction / whistleboard


N

Sign AH03m Iss 1 Automatic level crossing restriction board


N

Sign AH04m Iss 1 Automatic level crossing wrong direction speed restriction board


N

Page 65 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Sign AH05 Iss 1 Level crossing sighting board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AJ01 Iss 1 Neutral section warning board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AJ02 Iss 1 Neutral section indication board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AJ03 Iss 1 Lower pantograph N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AJ04 Iss 1 Warning of traction system changeover


N

Sign AJ05 Iss 1 25 kV AC electrification boundary - entering


N

Sign AJ06 Iss 1 750 V DC electrification boundary - entering


N

Sign AK101 Iss 1 Signal reminder board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK102 Iss 1 Countdown markers N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK103 Iss 1 Line identification board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK104 Iss 1 Platform Stop Markers N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK105 Iss 1 Mid-platform train berth markers N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK201k Iss 1 Kilometre Posts N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK201m Iss 1 Mile Posts N N/A N N N/A N N N/A N General: N/A ETCS: N/A

N

Page 66 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

Sign AK202 Iss 1 Gradient sign N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK203 Iss 1 Whistle board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK204 Iss 1 Spring catch board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK205 Iss 1 Rear clear marker N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK206 Iss 1 Train class specific instruction N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK207 Iss 1 Train class specific no entry N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK208 Iss 1 Coasting board N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK209 Iss 1 Miscellaneous instructions to train crew


N

Sign AK210 Iss 1 Warnings for train crew N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK211 Iss 1 Sandite markers N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK212 Iss 1 Infrastructure location names, information and references


N

Sign AK213 Iss 1 Bridge identity plates N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign AK214 Iss 1 Termination of adhesion condition N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Page 67 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Sign BA01 Iss 1 High visibility clothing obligatory N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign BA02 Iss 1 Warnings N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign BA03 Iss 1 Access prohibited sign N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign BA04 Iss 1 Limited clearance sign N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign BA05 Iss 1 No refuges sign N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign BB01 Iss 1 Text signs N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign BC01 Iss 1 Signs at access points - information N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign BD01 Iss 1 Electrical hazard N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign CA01 Iss 1 Danger from passing trains N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign CA02 Iss 1 Mind the gap / step N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign CA03 Iss 1 Danger - No unauthorised access N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign CB01 Iss 1 Electrical hazard: warnings to the public


N

Sign CC01 Iss 1 Supplementary sign at crossings where trains pass in excess of 100 mph


N

Sign CC02 Iss 1 Supplementary sign for level crossings


N

Page 68 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

Sign CC03 Iss 1 Warning sign for a non-vehicular crossing (PCR diagram 101)


N

Sign CC04 Iss 1 Instructions for use at a vehicular crossing without a telephone (PCR diagram 102)


N

Sign CC05 Iss 1 Instructions for use at a vehicular crossing with a telephone (PCR diagram 103)


N

Sign CC06 Iss 1 Private level crossings: operating instructions for barrier (PCR diagram 104)


N

Sign CC07 Iss 1 Sign indicating the penalty for failure to shut a gate at a vehicular crossing (PCR diagram 105)


N

Sign CC08 Iss 1 Signs for use with miniature red / green lights with and without a telephone (PCR diagrams 107 and 108)


N

Sign CC09 Iss 1 Instructions for use at a crossing with miniature red / green lights and user- operated gates (PCR diagram 109)


N

Sign CC11 Iss 1 Reminder at a crossing with user-operated gates (PCR diagram 111)


N

Sign CC12 Iss 1 Reminder at a crossing with user-operated barriers (PCR diagram 112)


N

Sign CC13 Iss 1 Sign at a vehicular crossing where there are overhead electric wires and the road approaches are on a gradient (PCR diagram 113)


N

Sign CC14 Iss 1 Instructions to non-vehicular traffic at a crossing with miniature stop lights (PCR diagram 114)


N

Sign CC15 Iss 1 Instructions at a crossing with gates (PCR diagram 115)


N

Sign CC16 Iss 1 Supplementary sign where crossing is used for animal traffic (PCR diagram 118)


N

Page 69 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

Sign CC17 Iss 1 Horse riders to dismount at crossings where there are overhead electric lines


N

Sign CD01 Iss 1 Bridge strike information N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign DA01 Iss 1 Telephone number N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign DA02 Iss 1 White diamond N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign DA03 Iss 1 White diamond with 'X' N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign DB01 Iss 1 Signal post telephone N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign DB02 Iss 1 Signal post telephone - limited clearance label


N

Sign DB03 Iss 1 Lineside telephone N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign DB04 Iss 1 Emergency telephone N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign DB06 Iss 1 Telephone for routine use by railway staff


N

Sign DC01 Iss 1 Entering and leaving a GSM-R radio zone marker


N

Sign DC02 Iss 1 Cab secure radio channel change marker


N

Sign DC03 Iss 1 National radio network channel change marker


N

Page 70 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Sign DC04 Iss 1 RETB channel change marker N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Sign DC05 Iss 1 Combined End of GSM-R and National Radio Network Channel Change Marker


N

Sign DC06 Iss 1 Entering and leaving an IVRS zone marker


N

Sign DD01 Iss 1 GSM-R common shunt group access code


N

Sign DD02 Iss 1 GSM-R signal box phone number sign


N

Sign DD03 Iss 1 GSM-R signal box phone number short code


N

Sign DEV-AK102-01 Deviation for countdown markers Y Major N N N/A N N N/A N General: N/A ETCS: Refers to Miles. Whilst this is specifically for the Wessex Route, if ETCS is to be deployed on Wessex then this would have to be reviewed to consider Kilometres. TMS: N/A C-DAS: N/A

Y

Sign DEV-AK102-02 Deviation for countdown markers Y Major N N N/A N N N/A N General: N/A ETCS: Refers to Miles. Whilst this is specifically for the Scotland Route, if ETCS is to be deployed on Scotland then this would have to be reviewed to consider Kilometres. TMS: N/A C-DAS: N/A

Y

Sign CC10 Iss 1 Instructions for Use at a Crossing with Miniature Stop Lights and User-Operated Barriers (PCR diagram 110).


N

Sign AF03 Iss 2 Temporary Speed Restriction Repeater Warning Board


N

Sign AK215 Iss 1 End of Emergency special Working Y Major N N N/A N N N/A N General: N/A ETCS: Readability distance is stated in mph. May need to give an equivalent distance in km/h with it. TMS: N/A C-DAS: N/A

Y

ISCC-008 Iss 1 GB Strategic Direction for the Conventional Rail Freight Wagon TSI


N

Page 71 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

ISCC-010 Iss 1 Strategic Direction for Revised Locomotive and Passenger Rolling Stock (LOC&PAS) TSI


N

ISCC-011 Iss 1 Strategic Direction for the Combined High Speed and Conventional Energy TSI


N

ISCC-012 Iss 1 Strategic Direction for Revised Infrastructure (INF) TSI


N

ISCC-016 Iss 2 Strategic Direction for Control Command and Signalling (CCS) TSI


N

ISCC-017 Iss 1 Strategic Direction for the OPE TSI annexes


N

ISCC-022 Iss 1 Strategic Direction for the Noise TSI N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

ISCC-023 Iss 1 Strategic Direction for Safety in Railway Tunnels TSI


N

ISCC-024 Iss 1 Strategic Direction for the PRM TSI N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

NS-GSM-R-CELL-9501 Iss 1 GSM-R Radio - Guidance on GSM-R Cell Planning Consultation


N

RGSC01 Iss 4 Railway Group Standards Code N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

RGSC02 Iss 3 Standards Manual N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

RGSC03 Iss 1 An Industry Strategy for Standards 2016 - 2019


N

RSSB-ERTMS-OC Iss 2 Operational Concept for ERTMS Y Major N Y Major N N N/A N General: Complete overhaul may be required and be replaced with an Operational Concept for Digital Railway that would incorporate ERTMS and GB Mainline Railway where it hasn’t been deployed yet ETCS: 'Block Marker' is referred to as 'Stop

Y

Page 72 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Marker' which isn't consistent with the other documents however has suggested they all be changed to Stop Marker as this is the accepted European Term. Processes are detailed throughout such as start-up and driver entering cab. This could be updated dependent on the process updates as per O&M CRS requirements. TMS: As above regarding processes. C-DAS: N/A

RSSB-GBMR-OC Iss 2 Operational Concept for the GB Mainline Railway

N N/A N N N/A N N N/A N General: Complete overhaul may be required and be replaced with an Operational Concept for Digital Railway that would incorporate ERTMS and GB Mainline Railway where it hasn’t been deployed yet. ETCS: N/A TMS: N/A C-DAS: N/A

N

AP0002 Iss 1 Code of Practice for Audit Protocol for Supply of Machine / Crane Controllers


N

ATOCACOPEC01003 Iss 1B Approved Code of Practice - Supplier Accreditation Scheme


N

ATOCACOPEC01006 Iss 3.5 Management of Rail Vehicle Engineering Change


N

ATOCACOPEC01007 Iss 1 Approved Code of Practice - The Elements of Management of Safety Critical Components on Trains


N

ATOCACOPEC01009 Iss 2 Approved Code of Practice - Approvals Process for GSM-R Cab Mobile Fitment


N

ATOCACOPOITC2015 Iss 1 Approved Code of Practice: Operational Planning and Implementation of Timetable Change


N

ATOCECGN002 Iss 3.3 The ATOC Guide to Vehicle Change


N

ATOCECGN003 Iss 1.1 Guidance Note - Management of Rolling Stock Maintenance Records


N

ATOCECGN004 Iss 1 Guidance Note - ETCS Cab Human Factors Design Guidance


N

Page 73 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

ATOCFLUGN001 Iss 3 ATOC / Network Rail Guidance Note - Contingency Planning Arrangements for a Flu Pandemic


N

ATOCGN ERTMS 001 Iss 1 ATOC Guidance Note - L-NTC Principle Considerations for Driver Training


N

ATOCGN ERTMS 002 Iss 1 L-2 ETCS Principle Considerations for Driver Training

Y Major N N N/A N N N/A N General: N/A ETCS: To consider any updates or amendments including lessons learnt from Cambrian, Thameslink commissioning and GW/Crossrail development since the publication of this document in January 2015. TMS: N/A C-DAS: N/A

Y

ATOCGN001 Iss 4 Use of Data Recorders N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

ATOCGN003 Iss 7 The Training of On-Train Staff in On-Train Emergency Procedures


N

ATOCGN009 Iss 3 Investigation of Station Stopping Incidents

N N/A N Y Minor N Y Minor N General: N/A ETCS: N/A TMS: Section 10; TMS becomes a source of evidence. C-DAS: Section 10 also becomes a source of evidence and should prevent such occurrences.

Y

ATOCGN010 Iss 1 ATOC Guidance Note - Managing the Risk to Passengers and Staff from the Use of Contracted Road Services


N

ATOCGN013 Iss 2 ATOC Guidance Note - Control of Risk Posed by the Presence of Legionella Bacteria in On-Train Non-potable Water Systems


N

ATOCGN019 Iss 2 Developing Train Driving Policies Aligned with Non-Technical Skills

Y Minor N N N/A N N N/A N General: N/A ETCS: Page 10 point no.6 "When on the move" should also refer to obeying the DMI. TMS: N/A C-DAS: N/A

Y

ATOCGN021 Iss 2 Provision of Drinking Water for On-Train Use


N

ATOCGN022 Iss 1 ATOC Guidance Note - Safe Management of Pushchairs and Wheelchairs on Station Platforms


N

ATOCGN024 Iss 1 ATOC Guidance Note - Selection and Management of Contractors


N

Page 74 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

ATOCGN027 Iss 1 ATOC Guidance Note - Winter Arrangements for Stations


N

ATOCGN028 Iss 1 Prosecution Policy N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

ATOCGN029 Iss 1 Responding to Vulnerable Persons N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

ATOCGN030 Iss 1 Developing Incident Care Team Capabilities

N N/A N N N/A Y N N/A N General: The ICT Champion role may benefit from having access to "read only" TMS information to assist with decision making during disruption. ETCS: N/A TMS: See above. C-DAS: N/A

Y

ATOCGN031 Iss 1.1 Security Briefings by the BTP N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

ATOCGN032 Iss 1 Information Sharing Protocol with the BTP


N

ATOCGN033 Iss 1 Station Incident Response Planning N N/A N N N/A N N N/A N General: "Read only" TMS information may benefit station incident response planning and subsequent decision making when there is perturbation to BAU? ETCS: N/A TMS: N/A C-DAS: N/A

N

ATOCGN034 Iss 1 Logging and Loggists N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

ATOCGN036 Iss 1 Risks & Opportunities from ROCs and TM


N

ATOCGN038 Iss 1 Guidance Note - Data Protection Requirements During and After Incidents


N

ATOCGPG005 Iss 2 ATOC Good Practice Guide - Controller Recruitment, Training and Competence

N N/A N Y Minor N N N/A N General: N/A ETCS: N/A TMS: Review Appendix 1, the Performance Criteria column will need to include using TMS, where deployed. C-DAS: N/A

Y

ATOCGPG006 Iss 1 ATOC Good Practice Guide - Control Centres: Business Process Manual


N

Page 75 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

ATOCGPG012 Iss 1 Safe Use of Station Vehicles N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

ATOCGPG013 Iss 1 Access to the Driving Cabs of a Train Operator's Trains by the Staff of Another Train Operator for the Purposes of Route Learning or Route Refreshing


N

ATOCGPG014 Iss 1 ATOC Train Operators Safety Group Good Practice Guide - De-icing Agents for On Station Use


N

ATOCGPG015 Iss 1 ATOC Good Practice Guide - Control of Smoking


N

ATOCGPG016 Iss 1 ATOC Good Practice Guide - Management of Sub-Standard Performance by Train Drivers


N

ATOCNR GN SP01 Iss 3 ATOC / Network Rail Guidance Note - Meeting the Needs of Passengers when Trains are Stranded


N

COP0 Iss 4 Code of Practice for M&EE Documents


N

COP0001 Iss 7 Operator Competency Standards for On Track Plant


N

COP0002 Iss 10 Code of Practice for Planning for the Use of Mobile Operated Plant


N

COP0005 Iss 5 Code of Practice for Handling Serviceable Rail with RRV Excavator Cranes Including Thimbling


N

COP0007 Iss 6 Code of Practice for On, Off and Cross Tracking of On Track Plant (OTP)


N

COP0008 Iss 6 Code of Practice for Tandem Lifting with Two Excavator Cranes


N

COP0010 Iss 3 Code of Practice for Safety Critical Maintenance Elements of Small Plant and Equipment


N

Page 76 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

COP0011 issue 5 Code of Practice for Planning and Executing Lifting Operations


N

COP0012 Iss 6 Code of Practice for Defect Reporting for OTP, Plant and Equipment


N

COP0013 Iss 5 Code of Practice for Maintenance, Operation and Testing of Track Jacks


N

COP0014 Iss 6 Code of Practice for Trailers and Attachments with RRVs and RMMMs


N

COP0015 Iss 4 Code of Practice for Load Lifting Points on Road Rail Excavator Cranes


N

COP0016 Iss 4 Code of Practice for OTP Machine / Crane Controller Checklists


N

COP0017 Iss 3 Code of Practice for Loading of OTP


N

COP0018 Iss 5 Code of Practice for Rail Mounted Manually Propelled Equipment


N

COP0019 Iss 4 Code of Practice for Action to be Taken in the Event of an Accident or Incident involving OTP


N

COP0021 Iss 4 Code of Practice for Safe use of Quick Hitches


N

COP0022 Iss 1 Code of Practice for Pulling Rail with Road- Rail Excavator Cranes


N

COP0023 Iss 1 Code of Practice for Demountable MEWP and Lifting Equipment


N

COP0024 Iss 5 Code of Practice for Use and Loading of MEWPs


N

COP0025 Iss 3 Code of Practice for Brake Testing of RRVs


N

Page 77 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

COP0026 Iss 2 Code of Practice for Flailing Operations using OTP


N

COP0027 Iss 3 Code of Practice for OTP Recovery N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

COP0029 Iss 1 Code of Practice for the Independence and Competence of LOLER Through Examiners


N

COP0030 Iss 2 Code of Practice for Lifting Operations Using Manually Propelled Rail Mounted Gantries


N

COP0031 Iss 1 Code of Practice for Safe Use of Remote Controls


N

COP0032 Iss 2 Code of Practice for Any Line Open (ALO) Working


N

COP0033 Iss 1 Code of Practice for Gainig Assurance When Procuring OTP Services


N

COP0034 Iss 1 Code of Practice for Piling using OTP


N

COP0035 Iss 1 Code of Practice for Plant Modules on Rail Wagons and Trailers


N

COP0036 Iss 1 Code of Practice for Management of Points within Engineering Work Sites


N

COP0037 Iss 1 Code of Practice for Haulage Capabilities of On Track Machines


N

COP0038 Iss 1 Code of Practice for Defective OTP Safety Critical Equipment


N

COP0100 Issue 8 Code of Practice for Management of Operational Risk and SPAD Avoidance Strategy


N

Page 78 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

COP0111 Iss 8 Code of Practice for Hiring in of Conductor Drivers


N

COP0125 Iss 3 Code of Practice for Management of Sidings Safety Surveys


N

COP0126 Iss 1 Code of Practice for Management of OTM Speeds within T3 Engineering Possessions

Y Minor N N N/A N N N/A N General: N/A ETCS: Section 1, clause 1.2 of Supporting Documents needs to include "Possession of an ERTMS running line for engineering work where lineside signals are not provided." Appendix A, Professional Driving Key Principles - the list of examples in the "Give consideration to factors such as" should include ETCS Stop Markers (Block Markers). Appendix B, second paragraph, should refer to ETCS drivers driving according to the information displayed on the cab display (DMI). TMS: N/A C-DAS: N/A

Y

COP0128 Iss 1 Code of Practice for Route Knowledge within Possessions


N

Poster 09 Iss 1 Points Run Through N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster 11 Iss 1 Distributor Isolating Cock (DIC) N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster 12 Iss 1 Have you had your brief N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster 13 Iss 1 OTM Movements Involving Route Conductors


N

Poster 19 Iss 1 Points Run Through Within Possessions


N

Poster 20 Iss 1 Drivers Reminder: Before traversing Handpoints within Depots, Yards and Sidings


N

Poster 23 Iss 1 Use of GSM-R within T3 possessions


N

Page 79 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

Poster I1 Iss 1 Riding on OTP N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster I2 Iss 1 Securing of Loads N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster I3 Iss 1 Seasonal Operating of OTP N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster L1 Iss 1 RCI Motion Cut N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster L2 Iss 2 OTP Tandem Lift N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster L3 Iss 1 Crane Controller Competence for Twin Jib Cranes


N

Poster L4 Iss 1 Lift & Carry in Road Mode N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster L5 Iss 2 Using outriggers on plant N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster L6 Iss 1 Lifting accessories misuse N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster L7 Iss 2 Rated Capacity Indicator (RCI) Status Indicator Lights


N

Poster L8 Iss 1 Mechanical Movement Limiting Device Awareness


N

Poster L9 Iss 1 Rail Handling - Rail Turner Awareness


N

Poster OTM 4 Iss 1 On Who's Authority N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster OTM 5 Iss 1 Preventing Points Run Through in Possessions


N

Page 80 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

TMS: N/A C-DAS: N/A

Poster OTM1 Iss 3 Autumn Poster 2018 N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster OTM2 Iss 3 Winter Poster 2018 N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster OTM3 Iss 1 OTM - Movements Authority and Associated Speeds Within a T3 Possession


N

Poster P10 Iss 1 Plant Exclusion Zones N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster P2 Iss 1 MEWP Planning N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster P4 Iss 2 RRV Braking N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster P6 Iss 1 OTP Points Run Through N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster P8 Iss 1 AFFF Fire Extinguishers N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

Poster P9 Iss 1 Misuse of MEWPs N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

RDGACOP011 Iss 16 Joint Industry Provision of Humanitarian Response Following A Major Passenger Rail Incident


N

RDGACOP016 Iss 4 Incident Response - Duties of Primary Support Operators


N

RDGACOPEC01008EMU Iss 2 Approved Code of Practice – EMU Tightlock Coupler and Autoconnector Maintenance


N

RDG-AWG Manual Iss 6 Managing Low Adhesion Y Minor N N N/A N N N/A N General: 1. Under Full Supervision, block markers will normally read at low speed.

Y

Page 81 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

2. When dealing with lower adhesion, it is possible to consider reducing the available brake rate in the train data.

ETCS: The Adhesion Working Group should consider whether the principles of section 4.6.1 "The Sighting of Signals" also affects the sighting of ETCS Stop Markers (Block Markers) on an ETCS signals away railway. Cognisance should be taken of section 6.3.7 on page 153 which states that low adhesion "may increase the problems particularly where lineside signalling is to be removed". TMS: N/A C-DAS: N/A

RDGECGN005 Iss 2 Guidance Note - On Train Satellite Navigation Equipment/Darwin Interface


N

RDGGN011 Iss 3 Guidance Note - Emergency Planning - Knowledge, Understanding and Responsibilities


N

RDGGN012 Iss 2 Planning For and Responding To National Fuel Shortages


N

RDGGN014 Iss 3 Major Incidents - Preparation of Aide- Mémoires for Senior Managers


N

RDGGN015 Iss 3 Guidance Note - Extreme Weather Arrangements, including Failure or Non- Availability of On-Train Environment Control Systems


N

RDGGN016 Iss 3 Competence of Train Operator Liaison Officers (TOLOs)


N

RDGGN017 Iss 3 Competence of Station Incident Officers (SIOs)


N

RDGGN018 Iss 2 Guidance Note - Responding to Ill / Injured Passengers on Trains


N

RDGGN023 Iss 2 Guidance Note – Checklist for Major Incident Response


N

RDGGN025 Iss 2 Guidance Note - Post Incident Management of Personal Property


N

Page 82 of 98


Issue/Ver: 1.0

Date: 28/03/2019




required for ETCS

deployment?




ETCS deployment?


required for TMS

deployment?




TMS deployment?


required for C-DAS

deployment?




required for C-DAS

deployment?



four headings.)

Document changes

recommended?

RDGGN026 Iss 2 Guidance Note - Planning for Special Events


N

RDGGN037 Iss 1 Guidance Note - Contingency Planning for Power Outages


N

RDGGN040 Iss 1 Delivering Good Schemes - Conventional Re-signalling


N

RDGGN041 Iss 2 Train Driving Licences and Certificates Regulations


N

RDGGN043 Iss 1 Guidance Note - Developing a Base Roster


N

RDGGN044 Iss 1 Guidance Note – Proposals to Reduce Permissible Speed Restrictions


N

RDGGNGSM-R001 Iss 2 Managing GSM-R Train Radio N N/A N N N/A N N N/A N General: N/A ETCS: N/A TMS: N/A C-DAS: N/A

N

RDGGNNTI001 Iss 1 Guidance Note - Delivering Good Schemes - ETCS


N

Page 83 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019

8 Appendix B: BoD Review Outcomes

BoD Scenarios BoD Sub-scenarios

Suggested additions to Rules & Standards

(Grey means no additions identified, white means

changes are implied)

1.Overview of scenarios

2. Operate

Network To

Current Plan

Perform Manual

Activity

No additions envisaged to national operational rules

other than the changes identified in the reviewing of

existing Rules and Standards.

Manually determine

next regulation action




Automatically

determine next

regulation action




Interface with

Mainline

Entrance/Exits




Issue written orders

It can be expected that, after issuing written orders,

the railway will enter a degraded mode (except in

exceptional circumstances). Any changes to degraded

modes identified by the Rules and Standards review

exercise should be considered. It is expected that new

rules, applicable nationally, for order of precedence for

different modes of communication will be developed to

meet the requirement of CRS-O&M-89 [RD3].

Infrastructure change

is required


other than the changes identified in the review of


Generate control

request




Send control request




Page 84 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





3. Safely

Command Train

Communicate with

Adjacent

Interlockings

If ETCS is in Full Supervision (FS) mode, there should

be no changes to route-setting rules affecting

communication between interlockings (although there

could be some scope for simplification of the current

practices). In other modes, such as degraded

conditions, there might be changes affecting rules.

(Note, this comment is applicable for Driver and

Signaller only). Communication between Radio Block

Centres (RBCs) is determined by ETCS specifications

and is not in the scope of this comment.

Validate Control

Request




Configure Railway

Infrastructure




Verify Infrastructure

Safe




Update State of

Railway




Generate Movement

Authority




Send Movement

Authority




Page 85 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Set Signal Aspect




4. Provide

Information to

Signaller

Collate Information




Display Information




5. Interface with

adjacent non-

Digital Railway

Control Systems

Mainline Control &

Non-Mainline Control

Liaise




Update Current Plan;

Optimise Current

Plan




Safely Command

Trains; Safely

Command Non-

Mainline

Infrastructure




6. Train

preparation

Systems Check An extension of today’s requirements for systems

checks is required.

Manage Train

Service Data

As with GSM-R, the driver will need to enter train and

service information into the DR system.

Train Ready for

Driver Operation

The set of data required to describe the train as ready

for operation will be different from the current set.

Enter/Update/Confirm

Train Information

The driver will need to enter, update and confirm train

and service information into the DR system.

Page 86 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





7. Manage Train

Service

Information

Operating mode

request Use of ETCS modes is subject to new rules.

Change to Shunt

Mode Use of ETCS modes is subject to new rules.

Change mode from

Shunting to Standby Use of ETCS modes is subject to new rules.

Publish Train Service

Data

Unless the driver is required to confirm that an event is

to happen, or that it has happened, no additions are

envisaged to national operational rules other than the

changes identified in the review of existing Rules and

Standards.

8. Safely Operate

the Train

Start of Mission

New rules concerning the display of operational

information in the new form on the Driver Machine

Interface (DMI) are required. The driver is required to

be able to understand that the train is safe to move.

Determine Movement

Operation

New rules concerning the display of operational

information in the new form on the DMI are required.

The driver is required to be able to understand that the

train is safe to move.

Start Train Movement




Provide Information

to Driver

New rules concerning the display of information in the

new form on the DMI are required. The driver is

required to be able to understand the incoming

information.

Operate a Train The driver requires rules to understand the train

operation supervision Information.

Update Location of a

Train



existing Rules and Standards. The updating of the

train’s position in the ETCS coordinate system for

ETCS purposes is handled by the ETCS specifications

and is not part of this scenario.

Page 87 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Ensure Stopping

Distance is

Maintained



existing Rules and Standards. The handling of the

train should be unchanged.

Control Speed of

Train

The facility to impose Temporary Speed Restrictions

(TSRs) and remove them will be subject to a different

procedure and should be much more flexible. This

should make emergency possessions much easier to

put in place.

Speed Warning

Required

The driver needs the rules to react to the warning,

which will be given on the DMI.

Apply Service Brake



existing Rules and Standards. If ETCS pre-empts the

driver, new rules are required to set out if and how the

driver will take control back from the system.

Apply Emergency

Brake



existing Rules and Standards. If ETCS pre-empts the

driver, at conventional speeds the driver will not take

control back except under the procedure “Liaise with

control”.

Liaise with Control to

Resume Operation

The driver needs the rules to apply the procedure to

take back control of the train.

Stop Train The driver needs the rules to interpret the DMI.

End Mission

The rules defining the state of the train and all its

equipment upon ending the mission need to be set

out. For example, in what state is the ETCS to be left?

(Transition from

an ETCS Area)

Transition between

Signalling Systems

The rules setting out the information on the DMI and

the other cab displays, driver actions and responses to

failures need to be set out.

The driver is responsible for observing that any

automated functions occur correctly. If they do not, the

driver needs to take actions according to rules.

Page 88 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





(Transition into

ETCS Area)

Transition between

Signalling Systems

The rules setting out the information on the DMI and

the other cab displays, driver actions and responses to

failures need to be set out.

The driver is responsible for observing that any

automated functions occur correctly. If they do not, the

driver needs to take actions according to rules.

Driver Failed to

Acknowledge

The driver needs the rules to interpret the DMI. The

rules should state the system reactions if

acknowledgements are not made.

9. Provide

Information to

Driver

Collate Information

The driver needs the rules to interpret the DMI.

The driver is always responsible for ensuring he/she is

receiving rational information.

Provide Information

The driver needs the rules to interpret the DMI.

The driver is always responsible for ensuring he/she is

providing rational information as expected by the

system.

10. Optimise

Train Movement

Determine Maximum

Permissible Speed




Determine Expected

Arrival Time




Calculate Safe

Optimal Speed




Provide Information

to Driver The driver needs the rules to interpret the C-DAS DMI.

Transmit Estimated

Train Arrival Times

No changes envisaged to national operational rules

except possibly something more accurate.

11. Identify Train

and Location

(Infrastructure)

Process Headcode

Message




Page 89 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Process Train

Stepping Message







Determine Track

Occupation status




Process Train

Stepping Rules




Publish Train

Stepping




Raise Unexpected

Occupation Alarm




12. Identify Train

and Location

(Onboard)

Process New Train

Identity; Transmit

Train Identity

The driver needs rules to enter data into the systems.

National coordination is required to develop rules

applicable to all Driver User Procedures (DUPs).

Determine Train

Location; Transmit

New Train Location

to Trackside

Equipment







13. Monitor Train

Movements

against Current

Plan

Determine if train

movements are

within the agreed

tolerances of the

current plan

The tolerances will need to be defined. Several

categories of timekeeping may be required. The rules

for those categories need to be set out, and they may

not be the same for all operators.

Update train

predictions



existing Rules and Standards. More accuracy and

dependability of the predictions should be possible.

Page 90 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Monitor Infrastructure

Against Control

Requests




Tolerances Exceeded

Various scenarios and criteria for responding to

disruption to the agreed timetable will need to be

considered. These will have to be set out in a detailed

document with guidance for the traffic controllers on

obtaining agreement to an optimised plan.

Raise alarm

This is assumed to be in parallel with the previous

scenario and precedes the response planning when

tolerances are exceeded.

14. Manage

Incidents

Receive Incident

Task Request




Automatically

Perform Task




Request Operator

Perform task




Transmit confirmation

of task completion




15. Manage Stock

& Crew

Information

Receive Stock and

Crew constraints

This is assumed to be in parallel with the item

“Tolerances exceeded”.

Optimise Current

Plan



considered. These will have to be set out in a detailed

document with guidance for the traffic controllers on

obtaining agreement to an optimised plan.

16. Optimise

Current Plan

Collate Information A statement of the information to be collated is

required.

Collate List of

Mission Change

Requests




Page 91 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Optimise Plan



considered.

Identify and Resolve

Conflicts; Determine

Plan Sensitivity to

Change

These will have to be set out in a detailed document.

Agree New Plan Guidance for the traffic controllers on obtaining

agreement to an optimised plan is required.

Publish Current Plan




17. Safe Working

Site Warning

Monitor Area (trigger

points)




18. Possessions

Planning

Receive Possessions

Plan




Plan constraints

The facility to impose TSRs and remove them could be

subjected to a different procedure under Digital

Railway via an external tool. This would facilitate

taking of possessions for routine or emergency

repairs.

Feedback to planning




19. Manage

Possession

The rules concerning new possession management

process and tools will be developed. The safety

objectives will remain the same.

Possession warning




Page 92 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Request Start

Possession




Possession Rejected




Possession Allowed




Remove Possession




OK to remove




Extend possession




20. Short notice

possessions

The rules concerning new short notice possession

management process will be developed.

Raise Urgent

Possession Request

The facility to impose TSRs and remove them will be

subjected to a different procedure via an external tool.

This would facilitate taking of possessions for

emergency repairs.

Provide Information

to Signaller




Transfer control




Page 93 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





21. CCS Failure

The reporting of a CCS failure to TMS will follow a

standardise procedure. In the event of a TMS fault, a

neighbouring TMS will act as a backup, refer to 22.

Fault Disables

Primary Signalling

Functionality

In this case under ETCS a broader range of options is

available, if the decision is taken to take advantage of

them. A major revision of degraded working rules

should be undertaken.

Retrieve Information

from Failed Systems

Guidance to use this information for investigation is

required.

Is Alternative

Signalling Method

Available?

National rules will need to be updated to reflect the

“alternative signalling method available”.

Failover to Backup

System See “Control Centre Failure”.

Working by pilotman

(Module p2 - RSSB)

National rules will need to be updated to reflect the

“alternative signalling method available”.

Operate Degraded

Signalling

Functionality (CRS-

SoS-113)

Over junctions and busy routes, the Proceed on Sight

Authority (PoSA) offers adequate functionality. It would

be installed on stop markers. It would be used with an

appropriate ETCS mode.

22. Control

Centre Failure

Digital Railway

Equipment

Operational?

A hierarchical approach to control architecture is

essential for availability, as is the case where the

interlockings can be controlled independently of the

rail traffic management system. Rules for transfer of

control would be required. This has advantages in

commissioning, possessions and some failures.

Is Railway

Controlable from

Remote Location?

Ideally the first line of response is to use a

neighbouring control centre. Design for this purpose

would be required. This would be one part of a

hierarchical control architecture.

Switch Control to a

Remote Location

Rules for transfer of control would be required. see

“Transfer Signalling Control”

Page 94 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





23. Emergency

Initiator?

A structured rule approach to all the options available

to respond to an emergency is required. GSM-R (voice

and data), ETCS and interlocking systems have such

functions.

Stop all trains in

affected area

It is not always rational to stop all trains in an area.

Guidance is required.

For Each Train in

Area

In developing rules, consider which circumstances

enable trains to benefit from being allowed to continue.

24. Infrastructure

Fault

Raise or update an

Infrastructure Fault

The consideration of the degraded options for the

railway should lead to more effective degraded

operations. New rules would be required. The fault

reporting procedure may become more centralised

and responsive via the TMS.

Update Infrastructure

Availability




Update Limitations

Emergency Speed Restrictions (not limited to 20 mph)

are more likely to be used, perhaps with On Sight (OS)

or Staff Responsible (SR) mode perhaps supported by

PoSAs, otherwise no changes are envisaged to

national operational rules.

Optimise Current

Plan See “Optimise Current Plan”.

25. Train Based

Fault

Raise or update an

On Train Fault




Train Able to Move




Make train safe and

mark train as

unmovable




Page 95 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Publish Train

Limitations




Make train safe and

mark train as

unmovable




Organise Rescue




Optimise Current

Plan See “Optimise Current Plan”.

Raise Alert See “Optimise Current Plan”. (traffic timetable alarms).

26. Monitor Digital

Railway Health

Log Health

Information




Active Monitoring




Health check

Analysis




Notification 'Warning

Digital Railway

System NOT

Operational

Degraded mode advance preparation, e.g. interlocking

failed, routes blocked, points failed, control centre

closed and much more can all be prepared in advance

and held on the TMS. A national strategy is required to

develop rules.

Publish Health check

Status




Page 96 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Raise Faults




27. What-If

Analysis

Create Simulated

Scenario




Capture State of

Railway




Analyse Impact to the

Plan




Commit Changes to

the Plan




Discard Changes to

the Plan




28. Provide

Information to

Planning

Publish statistics

regarding actual train

movements against

previous daily

timetable

The planning rules could be changed which will

require different information to be published.

Analyse Received

Daily Plan for

Conflicts

The planning rules could be changed which will

require different information to be published.

Page 97 of 98

Reference TBD

Issue/Ver: 0.1

Date: TBD


Issue/Ver: 1.0

Date: 28/03/2019





Confirm Plan is

Conflict Free; De-

conflict Current Plan;

Publish De-conflicted

Plan to Timetable

Planning




29. Train Dispatch

Prepare train for

dispatch

Needs revision. Nationally applicable rules for

dispatching trains in the absence of lineside signals

are required.

Check Train Ready;

Dispatch Train




30. Transfer

Signalling Control

Receive Request for

Transfer of Control

Area

These types of rules and procedures enforced by the

(in this case the TMS) system are quite common in the

control world.

Accept request to

transfer control;

Receiving Signaller

validates transfer of

control complete?

A set of rules should be set up for the operators and

suppliers that will enable a standard and efficient

procedure for the transfer of TMS control functionality

to be established.

Transfer Control to

New Location?

Transfer will occur when all conditions for the transfer

are met. There may be occasions when control should

be taken, rather than granted.

Thought should be given to the fire resilience of the

systems involved, and their buildings, such that no one

event is likely to make a handover impossible. This

should be true down to the level of interlockings.