Technical Note - TN 027: 2016 · d) QSDP 75 – ‘Configuration Change and Control of Trackside...

Technical Note - TN 027: 2016

© State of NSW through Transport for NSW of 1

For queries regarding this document

[email protected] www.asa.transport.nsw.gov.au

Technical Note - TN 027: 2016 Issued date: 15 April 2016

Effective date: 15 April 2016

Subject: Withdrawal of EGG 1542 ATP Trackside Design Guideline

This technical note is issued by the Asset Standards Authority (ASA) as a notification to remove

from use RailCorp standard EGG 1542 ATP Trackside Design Guideline, Version 1.0. This

technical note advises that the published standard EGG 1542 is withdrawn.

Requirements and guidance associated with the trackside design process are now captured as

part of the automatic train protection (ATP) project and the System Integrator's processes,

guidelines and specifications. Refer to the advanced train control migration system (AMS) project

for details.

Authorisation:

Technical content prepared by

Checked and approved by

Interdisciplinary coordination checked by

Authorised for release

Signature

Date

Name Daniel Oakes Peter McGregor John Paff Graham Bradshaw

Position Principal Engineer Technical Standards

Lead Signals and Control Systems Engineer

A/Chief Engineer Director Network Standards and Services

mailto:[email protected]

mailto:[email protected]

http://www.asa.transport.nsw.gov.au/

Engi

neer

ing

Proc

edur

e

0

2

,

f 17

Engineering Procedure Signals Guideline

EGG 1542

ATP TRACKSIDE DESIGN GUIDELINE

Version 1.

Issued September 201

Owner: Chief Engineer, Signals and Control Systems

Approved by:

Warwick Allison Chief Engineer Signals and Control Systems

Authorised by:

Geoff Yarrow Principle Engineer Signals and Control Systems

Disclaimer This document was prepared for use on the RailCorp Network only. RailCorp makes no warranties, express or implied, that compliance with the contents of this document shall be sufficient to ensure safe systems or work or operation. It is the document user’s sole responsibility to ensure that thecopy of the document it is viewing is the current version of the document as in use by RailCorp. RailCorp accepts no liability whatsoever in relation to the use of this document by any party, and RailCorp excludes any liability which arises in any manner by the use of this document. Copyright The information in this document is protected by Copyright and no part of this document may be reproduced, alteredstored or transmitted by any person without the prior consent of RailCorp.

UNCONTROLLED WHEN PRINTED Page 1 oWith

draw

n un

der T

N 0

27: 2

016

RailCorp Engineering Procedure — Signals — Guideline ATP Trackside Design Guideline EGG 1542

Document control

Version Date Summary of change 1.0 September 2012 New document – First release

Summary of changes from previous version

Summary of change Section Document Created All

© RailCorp Page 2 of 17 Issued September 2012 UNCONTROLLED WHEN PRINTED Version 1.0 With

draw

n un

der T

N 0

27: 2

016


© RailCorp Page 3 of 17 Issued September 2012 UNCONTROLLED WHEN PRINTED Version 1.0

Contents

T1 Background .............................................................................................................................5 T

2 Purpose....................................................................................................................................5 3 Definitions................................................................................................................................5 4 Applicable Documents ...........................................................................................................5 5 Design Process .......................................................................................................................7 5.1 Overview ...................................................................................................................................7 5.2 System Requirements...............................................................................................................8

5.2.1 RailCorp ETCS Requirement Specification ...............................................................8 5.3 System Definition ......................................................................................................................8

5.3.1 Signal Design Principle – ESG 100.31 ‘ATP’ ............................................................8 5.3.1.1 Engineering Standards, Signals – Design Guidelines ATP .......................8

5.3.2 Circuit Design Standards ATP...................................................................................8 5.3.3 ATP Construction Drawings M05 500 – 599 .............................................................8 5.3.4 ETCS Signalling Application Principles .....................................................................8

5.3.4.1 META Signals.............................................................................................8 5.3.5 ETCS Encoder Standard Configuration Definition ....................................................9

5.3.5.1 META LEU .................................................................................................9 5.3.6 ETCS Level 1 Specific Data Validation Rules ...........................................................9 5.3.7 ETCS Level 1 Data Preparation Process ................................................................10 5.3.8 ETCS Level 1 Data Validation Process ...................................................................10 5.3.9 Geographical Data Acquisition Process ..................................................................10

5.4 Preliminary Design ..................................................................................................................10 5.4.1 Signalling Functional Specification (SFS)................................................................11

5.4.1.1 Design Inputs ...........................................................................................12 5.4.1.2 Design Outputs.........................................................................................12

5.4.2 Signalling Plan Design.............................................................................................12 5.4.2.1 Design Inputs ...........................................................................................13 5.4.2.2 Design Outputs.........................................................................................13

5.4.3 Geographical Data Acquisition ................................................................................13 5.4.3.1 Inputs........................................................................................................13 5.4.3.2 Outputs.....................................................................................................14

5.4.4 Aspect Sequence Chart Production ........................................................................14 5.4.4.1 Design Inputs ...........................................................................................14 5.4.4.2 Design Outputs.........................................................................................14

5.4.5 ETCS Control Table Design ....................................................................................14 5.4.5.1 Design Inputs ...........................................................................................15 5.4.5.2 Design Outputs.........................................................................................15

5.5 Detailed Design.......................................................................................................................15 5.5.1 Circuit Book – Signal/LEU Interface Design............................................................15

5.5.1.1 Design Inputs ...........................................................................................15 5.5.1.2 Design Outputs.........................................................................................16

5.5.2 Data Production .......................................................................................................16 5.5.2.1 Data Preparation ......................................................................................16

With

draw

n un

der T

N 0

27: 2

016



5.5.2.2 Data Validation .........................................................................................17 6 Competencies/Authority.......................................................................................................17

With

draw

n un

der T

N 0

27: 2

016



1 Background ATP is a control system that protects the train by ceiling speed supervision as well as supervising the braking distance to the limit of authority.

The ATP system to be used on the RailCorp network is the European Train Control System (ETCS). ETCS Level 1 provides ‘spot transmission’ from the trackside at pre-defined locations, and is ‘integrated’ into the existing signalling system where the existing signal controls is maintained.

2 Purpose The purpose of this guideline is to provide further details of the design tasks associated with the ETCS Level 1 ATP trackside design process (Preliminary and Detailed Design).

3 Definitions Term Definition Note

ATP Automatic Train Protection

ETCS European Train Control System

SVL Supervised Location ATP Overlap, Danger Point etc…

IMU Inertial Measurement Unit

GPS Global Positioning System

4 Applicable Documents • Signal Design Principle - ESG 100.31 ‘ATP’.

• Circuit Design Standards ATP.

• EGG 1633 – Alstom ETCS Level 1 Data Preparation Process.

• EGG 1634 – Alstom ETCS Level 1 Data Validation Process.

• EGG 1635 – Alstom ETCS Signalling Application Principles.

• EGG 1636 – Encoder Standard Configuration Definition.

• EGG 1637 – Alstom ETCS Level 1 Specific Data Validation Rules

• EGG 1638 – ESAP Exception Report Analysis

• SPG 0703 ‘Signalling Documentation and Drawings’

• EGG 1544 Measurement of Geographical Data For ATP

• Signals - Design Quality Procedures (QSDP’s)

a) QSDP 72 – Trackside ‘ETCS Data Control, Preparation and Validation’

b) QSDP 73 – ‘Storage of Trackside ATP Data Files’

With

draw

n un

der T

N 0

27: 2

016



c) QSDP 74 – ‘Control of LEU & Balise ETCS Data Files’

d) QSDP 75 – ‘Configuration Change and Control of Trackside ATP Data’

e) QSDP 81 – ‘ATP Trackside Design’

f) EGG 1542 – Design Guideline for Supervised Locations

With

draw

n un

der T

N 0

27: 2

016


5 Design Process

5.1 Overview Refer to the following figure for the trackside design process overview. The figure identifies the key elements of each design phase:

Syst

em

Req

uire

men

tsS

yste

m D

efin

ition

Pre

limin

ary

Des

ign

Det

aile

d D

esig

n

Figure 1 – ATP Trackside Design Process Overview


draw

n un

der T

N 0

27: 2

016



5.2 System Requirements

5.2.1 RailCorp ETCS Requirement Specification The requirement specifications are derived from the UNISIG & ERA specifications, and have been developed to accommodate the specific RailCorp operational requirements for the network, in consultation with key stakeholders.

5.3 System Definition

5.3.1 Signal Design Principle – ESG 100.31 ‘ATP’ The signal design principle ESG 100.31 has been published as part of the existing RailCorp signal design principles to govern the design and implementation of an ETCS level 1 system on the RailCorp network. The principle has been derived from the RailCorp ETCS Requirement Specifications and ERA requirement.

5.3.1.1 Engineering Standards, Signals – Design Guidelines ATP To support the application of the signal design principle ESG 100.31 ‘ATP’, a set of design guidelines is available to assist the designer in applying the principles.

5.3.2 Circuit Design Standards ATP To support the trackside system definition and enable the signalling/LEU interface design (circuit books), generic standard typical circuits have been produced to assist in the detail design.

The circuit design standards are used as ‘typical’ circuit drawings based on the current infrastructure types used on the RailCorp network, interfaced with the ETCS equipment. Designers shall select and apply the appropriate typical circuit when carrying out the circuit book design.

The circuit design standards are developed from ESG 100.31 and the equipment characterisation.

5.3.3 ATP Construction Drawings M05 500 – 599 For the trackside installation of ATP equipment, drawings are used for the construction phase of the project and show the approved physical installation arrangements for the equipment.

5.3.4 ETCS Signalling Application Principles The purpose of the application principles is to describe the generic rules applicable to configuring the ETCS data for Alstom LEU and Balise use. The document describes a number of automatic rules characterised by generic META Objects, which represents the most common of the signalling configurations as well as manual rules to be implemented by the ETCS data designer.

5.3.4.1 META Signals META Signals are used by the Alstom Data preparation tool (GOLIAT) to represent the signals applicable to the RailCorp network. The ETCS Signalling Application Principles describes the functionality of GOLIATH, and defines/lists all the generic META Signals to be applied.

With

draw

n un

der T

N 0

27: 2

016


META Signals are pre-configured objects describing generic functions associated with different types of signals (route, aspect sequence or block). Their utilisation through the Alstom data preparation tool enables automatic data production.

A key input for the production of the META Signals is a generic set of aspect sequences that are representative of the RailCorp network.. The figure below provides a description of the META Signal Structure:

Figure 2 - META Signal Aspects

5.3.5 ETCS Encoder Standard Configuration Definition The encoder standard configuration definition (ESCD) summarises the LEU Inputs to META signal mapping for all the generic signal configurations.

The various signal route aspect configurations and associated generic LEU inputs, are detailed in the definition document and mapped to its META signal reference ID, which is used in the data preparation and validation design activity.

5.3.5.1 META LEU The objective of the ESCD document is to produce a specification for the development of META LEU applicable to RailCorp Network

META LEU’s are generic objects defining the expected hardware behaviour of the LEU. Amongst others, it includes LEU inputs mapping and current detection thresholds.

5.3.6 ETCS Level 1 Specific Data Validation Rules The specific data validation rules are derived from the ETCS Signalling Application Principles, through the use of the Validation Activity Matrix. Its purpose is to capture any specific ETCS rules, as identified by the ETCS Signalling Application Principle, which are then translated into automatic scripts and used by the DVT (Data Validation Tool) to perform the trackside validation.


draw

n un

der T

N 0

27: 2

016



5.3.7 ETCS Level 1 Data Preparation Process The ETCS Level 1 Data Preparation Guideline document provides overall guideline on how the ETCS-Level 1 trackside data preparation shall be undertaken. It provides a step by step description of the activities to performed, their inputs, outputs and actors. It also provides insight into what information shall be automated and the steps to take when manual input is required.

5.3.8 ETCS Level 1 Data Validation Process The ETCS Level 1 Trackside Data Validation Process document provides an overall guideline on all engineering activities and sub-activities involved in ETCS Level 1 trackside data validation. The document describes the data validation system structure and methodology, while providing detail procedures on validation tool configuration and step by step sequence of the data validation process.

The document guides users through the main activities, instructing on how to obtain and assess specific information where required.

5.3.9 Geographical Data Acquisition Process An essential input to the ETCS data design process is the compilation of accurate descriptions of ATP related track infrastructure elements and the gradient of the track. Amongst other things, gradients and the relative distances between track elements are used in the design process to calculate the limits of authority, distance between odometry calibration balises and speed profile length.

Several approaches may be used depending on the type of design activity.

• New Railway Infrastructure – scheme plans and layout drawings, including signalling plans should be suitably dimensioned in the approved design to satisfy the identification and placement of ETCS elements. The infrastructure data will be manually entered into the data preparation tools. The actual position of the installation will be certified to confirm validity prior to commissioning.

• Existing Railway Infrastructure – the majority of ATP installations will be as a retro-fit to existing signalling infrastructure, or as part of MPM re-signalling schemes. In these cases, an approved measurement specification will be used to collect the required geographic data using video imagery and analysis coupled with precise GPS/IMU positioning of location/distance and gradient. The output will be provided as a RailML dataset that automatically feeds into the data preparation tools.

When cases arise where it is impracticable to perform automated measurement techniques on a small section of railway (siding or yard) manual measurement using approved methodology may be used to collect the required data. This could include but not be limited to distance measuring wheels.

Refer to Engineering Guideline EGG 1544 – Measurement of Geographical Data For ATP.

5.4 Preliminary Design The Preliminary Design phase includes all the activities needed to gather the critical inputs required to undertake the detailed design of the ETCS data and Signal/LEU Interface Design (circuit books).

With

draw

n un

der T

N 0

27: 2

016



Note: Where preliminary design is carried out by a third party, refer to TMGA 1510 for the design process, and QSDP 4 ‘Independent Design Review for External Organisations’.

All design task deliverables shall be in accordance with the following specifications:

• SPG 703 – ‘Signalling Documentation and Drawings’

5.4.1 Signalling Functional Specification (SFS) As per any major signalling project, a signalling functional specification shall be produced to outline and define the scope of the project/scheme, focussing on ATP related aspects. The Signalling Functional Specification aims to identify and capture the requirements by the customer and develop a document which provides the scope of works to the designer for the ATP design arrangements, and the installer.

The project roll-out specifies the limits of the ETCS implementation for the particular Signalling Functional Specification.

The designer shall develop the Signalling Functional Specification as per QSDP 44 – ‘Signalling Functional Specification’, followed by the following design, review, and verification and approval process:

• QSDP: 7 – ‘Design Review Process’

• QSDP 8 - ‘Independent Verification’

• QSDP 9 – ‘Approval of Signal Designs’

As part of the approval process, rail operations and relevant stakeholders shall be consulted and provide input into the Signalling Functional Specification as necessary.

The following design elements shall be summarised in the Signalling Functional Specification (as per QSDP 44):

• Speed Profiles

• Calibration Balise Placement

• Infill Selection and Positioning

• Transition Border Placement and reverse direction speeds

• Repositioning Balise Groups - Selection and Placement

• Metal Masses

• Fixed Release Speeds and Low Release Speeds

• Pre-indication Locations and look ahead requirements

• Supervised Locations (including distance and overlap timer start locations)

• Operational Modes

• An overview of the trackside architecture, interface type (contact or current sensing) and the possible configuration of multiple LEU’s

• List the non-standard signal balise group arrangements, including space constraints and special construction issues.

• Special Operational Requirements, i.e. Overset Shunt, ‘Look-Ahead’ With

draw

n un

der T

N 0

27: 2

016



• National values

• Unwired Sections of Track

• Section Timers

• Other non-generic balise groups (i.e. ETCS TSR...)

• Other non-standard ETCS arrangements.

A preliminary version of the Signalling Functional Specification is produced, based on information available from the signalling plan/s and circuit book/s. This preliminary Signalling Functional Specification includes the Drivers Diagram (or scheme plan) to reflect positions of the balises. When more accurate information is provided through Geographical data acquisition, the final Signalling Functional Specification is produced, reviewed, approved and issued.

5.4.1.1 Design Inputs • Existing Signalling Plans

• Existing Circuit Books

• ESG 100.31 ‘ATP’

• Circuit Design Standards ATP

• ETCS Site Surveys (where required)

• Aspect sequences

5.4.1.2 Design Outputs • Signalling Functional Specification (including Drivers Diagram)

5.4.2 Signalling Plan Design Following approval of the Signalling Functional Specification, the signalling plan shall be designed to reflect those functional requirements. In accordance with QSDP 20 ‘Track Plans and Signalling Plans’, the signalling plans shall include:

• Danger Point/Overlap Location and Distance

• Route Holding Release Timer Start Location

• Balise Locations

In addition, the following information is included:

• Non-Standard operational modes

• Big Metal Mass Start and Finish Locations

The signalling plan/s shall be designed to QSDP 20 – ‘Track Plans/Signalling Plans’, and subject to the design, review, verification and approval process. A preliminary version of the Signalling Plan/s is produced prior to the geographical data acquisition.

Following the acquisition of the geographical data, the signalling plan shall be updated to reflect the ATP data, and other subsequent signalling documentation.

With

draw

n un

der T

N 0

27: 2

016


The geographical survey may highlight subtle differences in the recorded kilometerage against the asset kilometerage recorded on the signalling plan. The signalling plan is required to be updated to reflect the ATP kilometerage for all surveyed infrastructure.

Note – The existing kilometerages are not to be removed from signalling documentation as these values exist across other asset databases.

Refer to the following example:

Figure 3 – Surveyed ATP Kilometerage and Asset Kilometerage

The updated signalling plan shall be subject to the review, verification and approval process.

5.4.2.1 Design Inputs • ESG 100.31 ‘ATP’

• Signalling Functional Specification

5.4.2.2 Design Outputs • Signalling Plans

5.4.3 Geographical Data Acquisition Following the initial design of the signalling plan, the plan shall be submitted for geographical data acquisition.

All specific ETCS components identified on the signalling plan are required to be surveyed on site, refer to Engineering Guideline EGG 1544 – Measurement of Geographical Data for ATP.

The surveyed information will then be collated and configured in the ETCS database. Part of the data acquisition shall include collection and simplification of gradient data.

5.4.3.1 Inputs • Signalling Plan


draw

n un

der T

N 0

27: 2

016



5.4.3.2 Outputs • Advanced Geographical Data File (RailML)

• Manual Measurement of Geographical Data (RailML)

5.4.4 Aspect Sequence Chart Production Aspect sequence charts are used for the data preparation process to enable the correct allocation of META Signals.

Where aspect sequence charts exist today, the format shall be converted to the correct format as specified in QSDP 80 – ‘Aspect Sequence Charts’. Where no records exist, the new template shall be used.

Aspect sequence charts are produced from the signal controls for the particular area. These signal controls may be derived from the existing control tables but the preference is that the circuit books shall be used as the main input for the aspect sequence chart production (Note – Existing control tables can be used after correlation against the circuit books).

The aspect sequence charts shall be treated as a ‘Design’ and subject to the review, verification and approval process.

5.4.4.1 Design Inputs • Existing Circuit Books, or

• Circuit Book and Control Tables

5.4.4.2 Design Outputs • Aspect Sequence Chart

5.4.5 ETCS Control Table Design Note – ETCS Control Tables are only required where Signal/LEU interface design (circuit books) are unavailable due to scheduling constraints and for non-standard META signal arrangements. The control tables are used to assist data preparation/validation and test/commission activities.

The control tables are only produced as part of the preliminary design and will not be maintained as a signalling record following the trackside commissioning.

To support the data preparation process and test/commission activities, the ETCS Control Tables shall specify the masks (LEU inputs/signalling controls) for each signalled route aspect.

The SFS will identify all the applicable signals routes to which the control tables shall apply. The designer specifies all the required signalling inputs as per the specific movement authority, and in the specific ETCS control table format. The ETCS Control Table shall form part of the circuit book design for the associated signal.

The ETCS Control Table shall contain the following information:

• Input Allocation

• LEU input control relay (e.g.: 100HR, A1/A2)

With

draw

n un

der T

N 0

27: 2

016



• Overlap timer duration

• MM_Count

• Current sensing configuration – The current sensing parameters

• META signal reference

5.4.5.1 Design Inputs • Circuit Design Standards ATP

• Circuit books

• Interlocking Control Tables/Interlocking Data

• ESG 100.31

• Encoder Standard Configuration Definition

• Signalling Functional Specification (look ahead information)

• ETCS Signalling Application Principles

• Aspect Sequence Charts

5.4.5.2 Design Outputs • ETCS Control Table

5.5 Detailed Design

5.5.1 Circuit Book – Signal/LEU Interface Design For each signal/LEU interface configuration (i.e. Relay interlocking, double light colour light signal, etc), the applicable standard circuit shall be used (refer to the Circuit Design Standards ATP). Where no applicable standard circuit exists, the closest configuration shall be selected as the ‘typical circuit’. Design alterations shall be based on the selected standard circuit and the necessary modifications carried out to suit the particular infrastructure type (included in the design alterations). Note – All design alterations shall comply with the principle ESG 100.31.

The signal/LEU interface design shall be carried out in accordance with QSDP 3 – ‘Circuit Books’, and subject to the RailCorp review, verification and approval process.

For each circuit book design, the version of the applicable data files (LEU & Balise) shall be included as part of the design.

Where time constraints require the data to be produced concurrently with the Circuit Books, the ETCS Control Table shall be used as an input.

The Circuit books are subject to the review, verification and approval process.

5.5.1.1 Design Inputs • Circuit Design Standards ATP


With

draw

n un

der T

N 0

27: 2

016



• Existing Circuit Book

• ETCS control table (where applicable)

5.5.1.2 Design Outputs • Circuit Book Design

5.5.2 Data Production The Data preparation and validation process shall be subject to QSDP 72 – ‘Trackside ETCS Data Control, Preparation and Validation’

5.5.2.1 Data Preparation The data preparation process follows the completion of the geographical data acquisition, signalling plans, aspect sequence charts and ETCS control tables design.

During this activity, the infrastructure data base is finalised, the allocation of META signals is carried out and the automatic data generation/manual modification is performed.

The files exported during this process are issued to the verification & validation team. After successful validation and approval, the data is released to site for testing and commissioning.

5.5.2.1.1 Design Inputs

• Signalling plans


• ETCS signalling applications principles (including exception report)

• Geographical data (RailML database)

• Manual Measurements

• Aspect sequence charts

• ETCS control table


• Simplified gradients

• Validation reports

• Data release note for preparation

5.5.2.1.2 Design Outputs

• Configured RailML database

• Data Release Note for Validation

• Release Note Installation

• Approved Data Release Note for Validation

With

draw

n un

der T

N 0

27: 2

016



5.5.2.2 Data Validation The Data Validation process commences when the Data Preparation is completed and the data files are released for validation.

This activity consists in an independent validation of the data. The validation is performed using tools different to those used for Data Preparation. Inputs used for data validation can be the same as the inputs used for data generation as long as they are following another validation mechanism.

During this activity, the infrastructure database and reference files are created. The RailML Data Base is imported, and scripts are executed. Where the scripts are not able to automatically cover the database, the validation is performed manually.

In addition, functional scenarios can be executed utilising an onboard ATP emulator. This is generally used to validate the functionality between onboard and trackside.

5.5.2.2.1 Design Inputs

• Signalling plans


• Validation rules (Including exception report)

• Configured RailML database

• Geographical data (RailML database)

• ETCS control table


• Raw gradients

• Data release note for validation

5.5.2.2.2 Design Outputs

• Validation reports

• LEU/Balise ETCS data files

• Approved Data Release note for Construction

6 Competencies/Authority Authority to perform verification of design is provided by an authorisation for that activity in the Competency Certificate. Supervisors should allocate staff according to the complexity of the task and the authority obtained.

With

draw

n un

der T

N 0

27: 2

016

Technical Note - TN 027: 2016 · d) QSDP 75 – ‘Configuration Change and Control of Trackside...

Documents

Transcript of Technical Note - TN 027: 2016 · d) QSDP 75 – ‘Configuration Change and Control of Trackside...