Professional Documents
Culture Documents
8110-600-052 (4.1)
8110-600-052 (4.1)
Document History
Rev Date Prepared by Reviewed by Authorised by Comments
1.10 08-Apr-2013 Control Systems Engineering Control Systems Engineering A/General Manager Network & Removal of Manager Infrastructure
Manager L Sanchez Manager L Sanchez Infrastructure Rob Davies Systems
2.00 09-04-2014 A/Control Systems Engineer YL Control Systems Supervisor S A/Control Systems Engineering Removal of Application for System
Phay Williams Mgr. A Nurman Changes form, referencing 8130-600-010
General review
3.00 07/11/2018 Control Systems Team Leader, Manager Operational Director Operational Systems & Reformatted to PTA standard
M Law Technology, J Reeve Technology, Information Updated to reflect migration into standard
Engineer Operational Technology – Dan Kerr IT change management process
Technology, T Tran Removal of reference to document
Operational Systems Team number 8130-600-010
Leader , D Cohn Template and format review
Technical Writer, Jo Turbett
4.00 26-06-2019 Manager Operational Engineer Operational Director Operational Systems & Updates to Table 3 to align with data in
Technology – J Reeve Technology, T Tran Technology, Information Service Now
Technology – Dan Kerr Updates to Table 1 to reference new
documents
Minor updates to Sections 2.1 and 2.6
4.01 08/06/2020 Manager Operational Engineer Operational A/Director Operational Systems Annual review and updates to Tables 1
Technology – J Reeve Technology, T Tran & Technology, Information and 3
Technology – R Taylor
Table of Contents
1. Introduction .................................................................................................... 7
1.1 Document Purpose............................................................................................................. 7
1.2 Audience and Applicability.................................................................................................. 7
1.2.1 Document Applicability/Scope......................................................................................... 8
1.2.2 Document Exclusions ..................................................................................................... 9
1.3 Roles and Responsibilities.................................................................................................. 9
2. Key Concepts ............................................................................................... 10
2.1 Guiding Principles ............................................................................................................ 10
2.2 Documentation and Record Keeping ................................................................................ 11
2.3 Consultation ..................................................................................................................... 11
2.4 Software........................................................................................................................... 12
2.5 Version Control ................................................................................................................ 12
2.6 Emergency Works............................................................................................................ 12
3. Glossary ........................................................................................................ 12
4. Abbreviations and Acronyms...................................................................... 13
List of Tables
Table 1: Related Documents............................................................................................................. 6
Table 2: Document Audience............................................................................................................ 7
Table 3: Business Services............................................................................................................... 8
Table 4: Description of Roles ............................................................................................................ 9
Table 5: Terms and Definitions ....................................................................................................... 13
Table 6: Abbreviations and Acronyms............................................................................................. 13
Related Documents
Table 1: Related Documents
Document Number Name
8070-250-001 Process: IT Change Management Process
8110-600-023 Procedure: Archiving of System Data Software & Equipment
8130-600-010 Form: Application for System Changes
8190-700-005 Code of Practice: Control Systems Security
8190-700-006 Code of Practice: Control Systems Design
8990-250-001 Code of Practice: Testing and Commissioning of Control Systems
8990-250-002 Code of Practice: Operational Technology Systems
8990-250-003 Code of Practice: Information Technology Service Management
A3929117 OT System RACI’s
9502-000-001 PTA Risk Management Policy
9500-000-004 Records Management Manual
1. Introduction
Change Management is important to the Public Transport Authority as it ensures
standardised methods and processes are used to ensure efficient and prompt handling of all
change. Through this process the impact of change related incidents to both service quality
and day to day operations are minimised.
Role
Operational Technology/PTA Contractors
This procedure does not include changes to timetable data in train scheduling software (i.e.
Vizirail and Austrics) or work done as part of routine maintenance activities carried out by
Operational Technology staff. Any routine changes, however, which have the potential to
impact production environments or users shall be treated as a change.
A more detailed breakdown of exclusions in relation to change management within the
Operational Technology area can be found within the Operational Technology Code of
Practice RACI models (Objective Reference: A3929117).
Role Description
PTA officer allocated the task of overseeing and supervising the maintenance
Operational Technology and servicing of all equipment related to the operation of train control and
Team Leaders operational systems assets. Has the authority to reject any changes covered
under the scope of this procedure.
Operational Technology PTA officer or contractor allocated the task of maintaining and servicing all
Officer, comprising of: equipment related to the operation of train control and operational system
a. Control Systems Officers assets. Has the delegated authority to perform or witness changes on behalf of
b. Operational Systems the Manager Operational Technology. Also has the authority to halt works if
Support Officers/ deemed to be unsafe, detrimental to the operation of the asset/system or
Administrators contrary to the submitted work plans.
Operational Technology PTA Officer allocated by the PTA to provide technical and engineering oversight
Engineers for work undertaken on PTA’s Operational Technology assets and systems.
Project Managers The person or group appointed by the PTA to manage a project.
The person or group appointed by the PTA to manage technical or engineering
Project Engineers aspects of a project, including the submission of change requests through the
ITSM toolset.
The person nominated and approved by the Communications Engineer
Manager, Signal Engineering Manager or Operational Technology Manager with
Commissioning Engineer/s
the responsibility and authority to oversee the commissioning of new or altered
works.
The person designated to test new or altered works within the scope of a
Testing Engineer/s
contract or job.
An organisation or individual contracted or sub-contracted to perform works for
Operational PTA, including the delivery of services, supply of goods and installation. Has the
Technology/PTA Contractor authority to perform changes once approvals have been given in accordance
with this procedure.
2. Key Concepts
c. Where possible standard changes shall be used to reduce the need for approvals,
however this does not negate to provide at least 3 working days’ notice of the change.
If a standard change is unsuccessful, the standard change shall be suspended and
reviewed. Standard changes shall be used where the level of risk is Low (1-6) as
described by the PTA Document: 9502-000-001 Risk Management Policy.
d. Exemptions to the above mentioned points may be granted in exceptional
circumstances with the prior approval from the Manager Operational Technology or
their approved delegate. In these situations, a change request shall be raised after the
event and categorised as either an ‘Unauthorised Normal’ change or Retrospective
Emergency Change through the ITSM toolset.
2.3 Consultation
Stakeholders or System Owners shall be consulted if any possibility exists of disruption to
either infrastructure or train services. These stakeholders or System Owners may include,
but are not limited to:
2.4 Software
Archives and backups in accordance with PTA Procedure for the archiving of System Data
Software & Equipment (8110-600-023) shall be completed once the change has been
completed and verified as successful by the system owners.
3. Glossary
The following terms are used in this document:
Term Definition
LLPA Long Line Public Address
OT Operational Technology
PABX Private Automatic Branch Exchange
PLC Programmable Logic Controller
PTA Public Transport Authority
RACI Responsible, Accountable, Consulted, Informed
RATs Rail Ambient Temperature SCADA
RTU Remote Terminal Unit
SCADA Supervisory Control And Data Acquisition
SVN Subversion Repository
SWMS Safe Work Method Statement
TCS Train Control System
TPS Traction Power SCADA
TTO Transperth Train Operations
VMS Video Management System
WAMS Wayside Asset Monitoring System