L1-CHE-PRO-043 v1 - Signalling Arrangement Plans Approvals

Download as pdf or txt
Download as pdf or txt
You are on page 1of 6

PROCEDURE

SIGNALLING ARRANGEMENT PLAN APPROVALS


L1-CHE-PRO-043 Version: 1 Effective from: 26th September 2018

Approval

Amendment Record

Approval Date Version Description


26/09/2018 1 Initial Issue

Approving Manager: Executive Dir. Network Integration Approval Date: 26/09/2018 Next Review Date: 26/09//2020
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 1 of 6
PROCEDURE
SIGNALLING ARRANGEMENT PLAN APPROVALS
L1-CHE-PRO-043 Version: 1 Effective from: 26th September 2018

Table of Contents

1. Purpose ........................................................................................................................ 3

2. Scope ........................................................................................................................... 3

3. Abbreviations and Acronyms ..................................................................................... 3

4. Background ................................................................................................................. 3

5. The Issue ..................................................................................................................... 3

6. The Requirement ......................................................................................................... 4

7. Responsibilities ........................................................................................................... 4

8. Recording of Approvals .............................................................................................. 6

9. Dispute(s)..................................................................................................................... 6

10. References ................................................................................................................... 6

Approving Manager: Executive Dir. Network Integration Approval Date: 26/09/2018 Next Review Date: 26/09//2020
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 2 of 6
PROCEDURE
SIGNALLING ARRANGEMENT PLAN APPROVALS
L1-CHE-PRO-043 Version: 1 Effective from: 26th September 2018

1. Purpose
The purpose of this procedure is to clarify the MTM stakeholders required to approve
Signalling Arrangement Plans (SAPs).

2. Scope
This procedure defines the MTM stakeholder positions and their limits of authority
associated with the authorization of SAPs for both internal and external projects. It also
defines how this authorisation shall be recorded.
This procedure L1-CHE-STD-004, section 7.2 and L1-CHE-STD-036, section 5.3.

3. Abbreviations and Acronyms


IFC Issued for Construction
MTM Metro Trains Melbourne
SAP Signalling Arrangement Plan
SME Subject Matter Expert
SPAD Signal Passed At Danger

4. Background
SAPs are the basis upon which railway signalling systems are designed. It is essential that
SAPs properly consider:
• Signalling Principles (including rail safety and infrastructure maintenance)
• Network Operations (including headways and capacity)
• Drivability and train operation (including signal sighting and SPAD mitigation)
• Human Factors
• Availability and reliability
The requirements for stakeholder approval are not clearly defined in MTM standards and
procedures.
This document clarifies MTM’s requirements for approval of SAPs.

5. The Issue
The SAP is an Engineering design drawing for which Engineering is ultimately held
accountable. SAPs have traditionally been approved for IFC by engineering staff. However,
there is a requirement to take into account other MTM stakeholder requirements.
Engineering staff have understood the need to consult these other MTM stakeholders prior
to approval although this consultation has occurred in an informal and inconsistent manner.
It is necessary to formalise the SAP approval process to improve project delivery outcomes
and limit late changes to signalling arrangements. The table below identifies the positions
that shall approve SAPs before achieving IFC. The table also defines the limits of authority
of each approver.
It is important to remember that SAPs remain a signal engineering drawing. Signal
engineering principles (which have been developed over the years to mitigate identified rail
safety issues) shall generally take precedence over other MTM stakeholder inputs.

Approving Manager: Executive Dir. Network Integration Approval Date: 26/09/2018 Next Review Date: 26/09//2020
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 3 of 6
PROCEDURE
SIGNALLING ARRANGEMENT PLAN APPROVALS
L1-CHE-PRO-043 Version: 1 Effective from: 26th September 2018

6. The Requirement
SAPs, whether produced internally by MTM or by external parties, shall not proceed to IFC
status until approved by the persons holding the MTM stakeholder positions (or their
appointed delegates) as stated in Table 1 below.
In addition, consultation with both the Signal Sighting Committee Chair and MTM Human
Factors specialists shall occur prior to a SAP proceeding to IFC.

7. Responsibilities
All projects required to modify SAPs shall be responsible for obtaining the required
endorsements from the MTM stakeholders listed in the table contained within section 8
below. Should the modifications affect other ARTO’s then endorsements from those
ARTO’s will need to be obtained and recorded in accordance with the requirements of the
ARTO concerned.
The nominated signatories (or their appointed delegates) of each of the MTM stakeholders
listed in the table below shall be responsible for authorising matters relating to their area of
knowledge within the business.

Approving Manager: Executive Dir. Network Integration Approval Date: 26/09/2018 Next Review Date: 26/09//2020
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 4 of 6
PROCEDURE
SIGNALLING ARRANGEMENT PLAN APPROVALS
L1-CHE-PRO-043 Version: 1 Effective from: 26th September 2018

Table 1 - Areas of Accountability and Authorisation


The table below provides details of areas of accountability and examples of authorisation limits for stakeholders required to approve SAP’s.

Stakeholder Area of Accountability Authorisation Limits


Signalling Standards and Principles Compliance with Signalling Standards and Principles
Signal Sighting Co-ordination of Signal Sighting Committee and Signal Sighting Committee acceptance in principle to the positioning of
new or altered signals.
Public Safety Position of crossings in respect to signals and platforms
Signalling System Safety Safe signalled movement of trains (joint responsibility with Network Safety)
Head of Signalling related requirements contained within documents such as the FOR and PRS (joint responsibility with
Engineering - Project Requirements
Operations)
Signals
Discipline consultation Track, Civil, Structures, Overheads, Electrical, Asset Management/Infrastructure delivery
Equipment Type/Configuration Track circuits, Point Machines etc.(in consultation with Asset Management/Infrastructure delivery)
Maintainability Staff safety and equipment accessibility (in consultation with Asset Management/Infrastructure delivery)
Reliability and Availability Ensuring the reliability and availability meets business requirements
Human Factors Consult with Human Factors specialists to ensure all human factor issues have been considered & mitigated against.
Safe signalled movement of trains (joint responsibility with Engineering – see above)
Safeworking of Train Movements
Safe non-routed movement of trains (joint responsibility with Operations)
Head of Compliance with Book of Rules Ensuring book of rules requirements are adhered to.
Network Safety Operating Procedures Ensuring adequate safe working procedures are in place if required
Human Factors Consult with Human Factors specialists to ensure all human factor issues have been considered & mitigated against.
Non-timetabled movements
Safeworking of train movements
Safe non-routed movement of trains (joint responsibility with Network Safety - see above)
Routing Requirements /Operational
Director of Ensuring all required movements are provided.
Flexibility
Operations Signal Controllers Operational Interface with Signalling System
Train Operational Safety Driver Interface with the railway system
Human Factors Consult with Human Factors specialists to ensure all human factor issues have been considered & mitigated against.

Approving Manager: Executive Dir. Network Integration Approval Date: 26/09/2018 Next Review Date: 26/09//2020
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 5 of 6
PROCEDURE
SIGNALLING ARRANGEMENT PLAN APPROVALS
L1-CHE-PRO-043 Version: 1 Effective from: 26th September 2018

8. Recording of Approvals
The designer shall, when producing a SAP, include a ‘stamp’ containing the information
detailed below. This stamp shall be positioned in the bottom right hand corner of the
drawing just above the drawing border title block. The use of digital signature is accepted
as evidence of approval.
SIGNALLING ARRANGEMENT PLAN APPROVAL
STAKEHOLDER NAME SIGNATURE DATE
Head of Engineering -
Signals
Head of Network Safety

Director of Operations

9. Dispute(s)
The Chief Engineer shall be responsible for arbitrating should the need arise and shall
have the final decision where an impasse exists.

10. References
Ref. Document Number
Document Title
No.
1 Signalling Design Technical Review Procedure L1-CHE-PRO-035
2 MTM Design and Technical Review Procedure L1-NAM-PRO-002
3 MTM LXRP Design and Technical Review Procedure L1-PRJ-PRO-009
4 Signalling Principles and Configuration Requirements L1-CHE-STD-036
5 Signal Sighting Standard L1-CHE-STD-004

Approving Manager: Executive Dir. Network Integration Approval Date: 26/09/2018 Next Review Date: 26/09//2020
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 6 of 6

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy