Download - Traction Power SCADA Functional & Performance ......TPS Traction Power System TPSS Traction Power SCADA System TSC Track Sectioning Cabin (25kV traction) TSI Track Section Isolator

Traction Power SCADA Functional & Performance Specification - Train System

Rail Commissioner

TP2-DOC-002253


Document Number: TP2-DOC-002253 Knet No (PDF): 15851618

Version Number: 1 Knet No (Word): 14066852

Document Owner: Electrical Engineering Issue Date: 10-August-2020 UNCONTROLLED WHEN PRINTED of 33

DOCUMENT CONTROL





TABLE OF CONTENTS

1. Introduction ................................................................................................................... 5

2. Purpose ......................................................................................................................... 5

3. Scope ............................................................................................................................. 5

4. Related Documents ....................................................................................................... 5

5. References..................................................................................................................... 6

6. Acronyms ...................................................................................................................... 7

7. Definitions ..................................................................................................................... 8

8. Overview - Existing & Future Configurations............................................................ 11

8.1. Overview – Existing 25kV TPSS Configuration .................................................. 11

8.2. Overview - Future Expansion ............................................................................. 13

8.3. Future Expansion – Miscellaneous Notes .......................................................... 14

9. Traction Power SCADA Functions ............................................................................. 15

9.1. Primary Functions .............................................................................................. 15

9.2. Support Functions .............................................................................................. 15

10. Systemic Functional Requirements ........................................................................... 16

10.1. Overview............................................................................................................ 16

10.2. Equipment Interface Requirements .................................................................... 16

10.3. Data Acquisition & Processing Functional Requirements ................................... 17

10.4. RTU Functional Requirements ........................................................................... 18

10.5. Data Transmission Functional Requirements ..................................................... 19

10.6. Server Functional Requirements ........................................................................ 19

10.7. Workstation Functional Requirements ............................................................... 21

10.8. HMI Functional Requirements ............................................................................ 22

10.9. Auxiliary LV Power Supplies .............................................................................. 24

10.10. Equipment Enclosures ....................................................................................... 24

11. Operational Performance Requirements ................................................................... 25

11.1. Operational Availability Target ........................................................................... 25

11.2. Operational Reliability ........................................................................................ 25

11.3. Maintainability .................................................................................................... 26

11.4. Expandability ..................................................................................................... 26

11.5. Security ............................................................................................................. 27

11.6. Control integrity.................................................................................................. 27

11.7. Data Integrity ..................................................................................................... 27

11.8. Timing Precision ................................................................................................ 27

11.9. Response Times ................................................................................................ 27

11.10. Equipment Service Life ...................................................................................... 28





11.11. Software Service Life ......................................................................................... 28

11.12. Environmental Performance............................................................................... 28

12. General – Design Requirements ................................................................................ 30

13. General - Testing and Commissioning Requirements .............................................. 31

13.1. Factory Acceptance Testing............................................................................... 31

13.2. Site Acceptance Testing .................................................................................... 31

13.3. Commissioning Testing ...................................................................................... 32

13.4. System Integration Testing ................................................................................ 32





1. Introduction

The Department of Planning, Transport and Infrastructure (DPTI) operates and maintains the Adelaide Metropolitan Passenger Rail Network (AMPRN) under the Rail Accreditation assigned to the Rail Commissioner. This specification stipulates the minimum performance and functional requirements for traction power Supervisory Control and Data Acquisition (SCADA) system works required to remotely monitor and control the electrified portions of the rail network.

2. Purpose

This specification forms part of the engineering management system (EMS) and is intended to ensure that the traction power SCADA system (TPSS) serving the Adelaide Metropolitan train network is not subject to any risks not deemed to meet the So Far As Is Reasonably Practicable (SFAIRP) principles under Rail Safety National Law (RSNL).

3. Scope

This specification shall be applied to the design, procurement, construction, installation, testing and commissioning of all new traction power SCADA systems works to serve the AMPRN. The intended audience for this specification includes:

DPTI Rail Maintenance functional areas,

DPTI Rail Operations functional areas;

DPTI Rail Projects; and

DPTI Rail contractors to the extent specified in their contract.

The SCADA system shall be of highest reliability and based on the state-of-the art technology. It shall be capable of monitoring and controlling traction power supply from a remote location called ROC (Rail Operation Centre). The system should be capable of collecting, storing, displaying and analyzing data as stipulated in the specification

Interpretation of any technical meanings of the specifications and sorting out technical disputes regarding this specification shall be decided by Unit Manager, Electrical Engineering, whose decision shall be final and binding.

The tenderers/project proponents shall familiarize themselves with site conditions before quoting against tenders based on this specification. Conditions particular to individual sites, including availability of communication and spare channels, conditions & space at ROC, switching posts, proximity to Road/Rail, sequence in which RTUs sites will be offered by railways for taking up work, and any special conditions concerning erection and commissioning of SCADA system shall be got clarified in a pre-bid meeting to be arranged by the purchaser with the tenderers.

4. Related Documents

DOCUMENT NAME DOCUMENT NUMBER

Traction Power System Principles and Practices TP1-DOC-001097

(KNet # 11903446)

RTU Panel AR-TP-EL-SPE-00110008

(KNet # 8822511)

Marshalling Panels AR-TP-EL-SPE-00110011

(KNet # 8822515)

Guidelines for Protective Provisions Related to Electrical Earthing & Bonding for Adelaide Metro Electrified Rail Network

AR-EL-STD-0102

(KNet #4600850)





Communications Network Principles and Practices for Public Transport - Engineering Standard

PTS-AR-10-CN-SPE-00200400

(KNet # 5589254)

Hrail Traction Power SCADA System Architecture and Description TP1-DOC-003130

(KNet # 15311557)

Table 1: Reference Documents

5. References

Traction power SCADA system works shall comply with all regulations and the minimum standards listed below. Project proponents shall apply the version of the standard in force at the date of commencement of works. Project proponents may submit a waiver application to the Manager Electrical Engineering to propose the application of alternate standards for identified aspects of the works. Such waiver application shall provide justification for the departure from the listed standard. There shall be no compromise or relaxation of Australian Standards bound in regulation. Acts and Regulations

Rail Safety National Law (South Australia) Act 2012

SA Workplace Health and Safety Regulations

South Australian Electricity Act 1966

Australian Standards

AS 1000 - International system of units (SI) and its application.

AS 2067 - Substations and high voltage installations exceeding 1 kV ac

AS 3100 - Approval and Test Specification – General Requirements for Electrical Equipment

AS 3111 - Approval and test certification – miniature over-current Circuit Breakers

AS 4292.4 - Railway safety management - Signalling and telecommunications systems and equipment

AS 4312 - Atmospheric corrosivity zones in Australia

AS 60068 (set) - Environmental Testing

AS 60529 - Degrees of protection provided by enclosures (IP Code)

AS 60870 (set) - Telecontrol equipment and systems

AS 60947.2 – Low voltage switchgear and controlgear – Part 2: Circuit breakers

AS 60950.1 – Information technology equipment – Safety –General requirements

AS 61131 (set) - Programmable Controllers

AS 61508 (set) - Functional safety of electrical/electronic/programmable electronic safety-related systems

AS/CA S008 - Requirements for customer cabling products

AS/CA S009 - Installation requirements for customer cabling (Wiring Rules)

AS/NZS 11801.1 - Information technology—Generic cabling for customer premises, Part 1: General requirements

AS 11801.3 - Information technology - Generic cabling for customer premises, Part 3: Industrial premises

AS 11801.5 - Information technology - Generic cabling for customer premises, Part 5: Data centres

AS/NZS 1768 - Lightning protection

AS/NZS 2312 - Guide to the protection of structural steel against atmospheric corrosion by the use of protective coatings

AS/NZS 3000 - Electrical installations (the Australian/New Zealand Wiring Rules)

AS/NZS 3008.1.1 – Electrical installations – Selection of cables – Part 1.1: cables for alternating voltages up to and including 0.6/1kV – Typical Australian installation conditions

AS/NZS 3013 - Electrical installations – Classification of the fire and mechanical performance of wiring systems





AS/NZS 61000.6.2 -Electromagnetic Compatibility (EMC) - Part 6.2: General standards - Immunity for industrial environments

AS/NZS 61000.6.3 -electromagnetic Compatibility (EMC) - Part 6.3: Generic standards – Emission standard for residential, commercial and light-industrial environments

Telecommunications Technical Standard (Surge Protective Devices for Telecommunication Applications – AS/NZS 4117) 2015

International Standards

EN 50121 (set) - Railway Electromagnetic Compatibility

EN 50126 (set) - Railway applications - The specification and demonstration of reliability, availability, maintainability and safety (RAMS)

EN 50128 - Railway applications. Communications, signalling and processing systems. Software for railway control and protection systems.

EN 50159-1 - Safety related Communication in Closed Transmission Systems.

EN 50159-2 - Safety related Communication in Open Transmission Systems.

IEC 60870-5-104 - Telecontrol protocol

IEC 61850 (set) - Substation Automation

IEEE 1008 - Software unit testing

IEEE 1012 - Software verification and validation plans

IEEE 1059 - Guide for software verification and validation plans

IEEE 802.3 - Telecommunications and information exchange between systems – Local and metropolitan area networks

IEEE 829 - Software test documentation

ISA 99.00.01 - Security for Industrial Automation & Control Systems

ISA-18.2 - Management of Alarm Systems for the Process Industries

AS/NZS ISO/IEC 27002 - Information technology – Security techniques – Code of practice for information security management

6. Acronyms

TERM DESCRIPTION

AMPRN Adelaide Metropolitan Passenger Rail Network

BCC Backup Control Centre

CB Circuit Breaker

COM Communication Interface

CTC Central Train Control

DC Direct Current

DPTI Department of Planning Transport & Infrastructure

DMZ Demilitarised Zone

DNP Distributed Network Protocol

ECO Electrical Control Operator

ELV Extra Low Voltage

EMC Electromagnetic Compatibility

EMS Engineering Management System

EN European Norm

EST Emergency Supply Transformer

FAT Factory Acceptance Test

FOBOT Fibre Optic Breakout Tray

FS Feeder Station (25kV traction)

GPRS General Packet Radio Service

GPS Global Positioning System

GUI Graphical User Interface

HMI Human Machine Interface





TERM DESCRIPTION

HV High Voltage

IP Ingress Protection

IEC International Electrotechnical Commission

IED Intelligent Electronic Device

I/O Input/Output

ITP Inspection and Test Plan

LAN Local Area Network

LRU Line Replacement Unit

LV Low Voltage

MTBF Mean Time Between Failures

MTTR Mean Time To Repair

MTSI Motorised Track Section Isolator

NTP Network Time Protocol

OCC Operations Control Centre

OHL Overhead Line

ONRSR Office of the National Rail Safety Regulator

OS Operating System

PLC Programmable Logic Controller

RAM Reliability, Availability, Maintainability

ROC Rail Operations Centre

RSNL Rail Safety National Law

RTU Remote Terminal Unit

SAPN South Australian Power Networks

SAT Site Acceptance Test

SCADA Supervisory Control and Data Acquisition

SFAIRP So Far As Is Reasonably Practicable

SIL Safety Integrity Level

SIT System Integration Test

SMS Short Message Service

SNMP Simple Network Management Protocol

SPD Surge Protection Device

SVC Static VAr Compensator

TCU Track Coupling Unit (25kV traction)

TPS Traction Power System

TPSS Traction Power SCADA System

TSC Track Sectioning Cabin (25kV traction)

TSI Track Section Isolator

UPS Uninterruptible Power Supply

VICOS Vehicle and Infrastructure Control and Operation System

WAN Wide Area Network

Table 2: Acronyms and Abbreviations

7. Definitions

TERM DESCRIPTION

Availability The ability of a product to be in a state to perform a required function under given conditions at a given instant of time or over a given time interval assuming that the required external resources are provided (Ref EN 50126).

Complementary definitions include:

– Steady-State Availability A∞ is the limit of the instantaneous availability





TERM DESCRIPTION

function A(t) as time approaches infinity

– Inherent Availability is A∞ with Active Repair Time only (i.e. MTBF/(MTBF+MART))

- Operational Availability is A∞ with the Active Repair Time + Logistic / Administrative Delays. (i.e. MTBF/(MTBF+MTTR))

Close Two definitions are valid, depending on context:

A remote-control command to close motorised switchgear, or

A verbal command to Authorised field personnel to close an un-motorised switch using hand tools.

Feeder Station An electrical substation that converts a 3-phase 66kV bulk infeed via 2-off traction transformers to provide 2-off 25kV single-phase traction supplies to separate overheard line sections on the Adelaide rail network, using HV switchgear and auxiliary equipment to protect and switch the associated power supply arrangements.

Hand Dressed Device

A hand-operated field device depicted on a SCADA GUI that is neither remotely monitored or remotely controlled, but which operating state is ‘hand-painted’ by the ECO on the SCADA GUI to reflect the actual field status of the device.

Line Replaceable Unit

The lowest assembly or unit at which the least diagnosis and repair are carried out. An LRU can be removed and replaced on site.

Local Control A lockable switch on a circuit breaker (or motorised isolator) control panel used to disable remote control of Close and Trip (or Open) commands and enable control from the local panel only.

Master Station The centralised location from where an Electrical Control Operator utilises a Workstation and associated computer servers to remotely monitor and control a traction power network (e.g. Dry Creek Rail Operations Centre or Mile End Depot Backup Control Centre).

Maintainability Maintainability is considered on both quantitative and qualitative levels:

Quantitative Maintainability is defined as the probability that a given active maintenance action, for an item under given conditions of use, can be carried out within a stated time interval when the maintenance is performed under stated conditions and using stated procedures and resources (Ref EN 50126).

Qualitative Maintainability are states or characteristics of design and installation

that are likely to ease maintenance and increase quantitative maintainability

Mean Time Between Failure (MTBF)

MTBF, a reliability parameter, is a measure of the average time interval (hours) that will elapse before a repairable item fails (i.e. the average time a system is available and operating).

Mean Time to Failure (MTTF)

MTTF, a reliability parameter, is a measure of the average time interval (hours) to failure for a non-repairable (i.e. replaceable) element.

Mean Time to Repair (MTTR)

MTTR, a maintainability parameter, is a measure of the average time interval (hours) required to repair a failed element. It represents the total time between detection of an element failure, and completion of repair (corrective maintenance). Hence the relation: MTTR = MADT + MLDT + MART

Mean Administrative Down Time (MADT)

MADT, a maintainability parameter, is a measure of the average time interval (hours) that elapses between the occurrence of a failure and the report of the failure.

Mean Logistic Down Time (MLDT)

MLDT, a maintainability parameter, is a measure of the average time interval (hours) for a maintainer to prepare to repair a failed element (e.g. obtain spares and tools) and reach the site of the failed element.

Mean Active Repair Time (MART)

MART, a maintainability parameter, is a measure of the average time interval (hours) to repair a failed element once a maintainer is on site (i.e. includes accessing the element, diagnosing failure, repair and placing the element back into service)

Neutral Section A three-element insulated section in the overhead wiring at a Feeder Station or TSC that incorporates an earthed section between two short dead sections in





TERM DESCRIPTION

the contact wire. A neutral section prevents inadvertent connection (e.g. by pantograph-initiated arcing) of two separate overhead sections fed by separate (out-of-phase) traction transformers.

Open Three definitions are valid, depending on context:

A remote-control command to open a motorised isolator, or

A verbal command to Authorised field personnel to open an un-motorised switch using hand tools, or

The de-energised state of a switch or circuit breaker.

Outstation Any field station, such as a switching station, that contains equipment which is remotely monitored or controlled by a master station.

Reliability Ability of a functional unit to perform a required function under stated conditions for a stated period of time. [ISO 2382-9]

Remote Terminal Unit

A microprocessor-controlled electronic device that interfaces objects in the physical world to a SCADA system by transmitting telemetry data to a master system, and by using messages from the master system to control connected objects.

SCADA Server A high-reliability processor that contains a dynamic database of the state of the traction power SCADA system and the required software to maintain that database in response to changes in the status of field objects obtained from field RTU’s. Servers pass this data to the Workstations and command changes in the field objects controlled by RTU’s in response to ECO inputs.

Static VAr Compensator

Reactive power compensation equipment that uses high-power electronics and electrical components to stabilise voltage dynamically on a common 25kV busbar due to rapid load changes at the point of connection of the load. An SVC is installed at Lonsdale Feeder Station.

Switching Station A collective term to describe Feeder Stations, Track Sectioning Cabins and Track Coupling Units serving the 25kV electrified area.

Track Coupling Unit An outdoor, mast-mounted electrical installation containing HV electrical switchgear and auxiliary equipment to protect and switch a dedicated 25kV feed to a spur line or rail yard.

Track Sectioning Cabin

An electrical installation containing HV electrical switchgear and auxiliary equipment in a weatherproof building to protect and switch multiple sections of the 25kV traction overhead line system.

Track Section Isolator

An off-circuit, manually operated OHL field switch used to switch or isolate a traction overhead section.

Traction Overhead System

All fittings and equipment, as viewed from the feeding terminals of a switching station, required to supply electricity to trains and return it to the feeding substation.

Trip Two definitions are valid, depending on context:

A remote-control command to open a motorised circuit breaker, or

The independent action by a circuit breaker to interrupt an energised circuit on detection of a fault condition.

Workstation A collection of processors, screens and input devices that provide the Electrical Control Operator with the necessary system functions to remotely monitor and control the traction power network.

Table 3: Definitions





8. Overview - Existing & Future Configurations

8.1. Overview – Existing 25kV TPSS Configuration

The existing 25kV traction power SCADA system (TPSS) is configured to allow a duty Electrical Control Operator (ECO) to remotely monitor & control the switching stations serving the electrified sections of the AMPRN via remote terminal units (RTU) over redundant data networks.

The AMPRN 25kV TPSS is arranged in two levels, as follows:

Master Station Level, where the Operator remotely monitors and controls system-

wide equipment from a duty Workstation via redundant SCADA Servers located at the Dry Creek Rail Operations Control Centre (ROC) or the alternate Mile End Depot Backup Control Centre (BCC).

Switching Station Level, where RTU’s located at Lonsdale Feeder Station, Lonsdale SVC, Ascot Park Track Sectioning Cabin and Seaford Depot Track Coupling Unit provide interfaces to the field equipment that is monitored and controlled at these sites.

Communication within and between the master stations and switching stations is via dual Ethernet data links over redundant data transmission networks, as depicted below:

Figure 1 - Overview - Configuration of existing AMPRN (25kV) traction power SCADA system

The electrified portions of the AMPRN overhead line network and associated Switching stations are represented in the following semi-geographical Network views on each TPSS workstation graphic user interface (GUI).





Figure 2: 25kV Network View 1- Adelaide Railway Station to Seaford Section (left hand view)

Figure 3: 25kV Network View 2- Adelaide Railway Station to Seaford Section (right hand view)

As detailed in Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document, automated colour-coding of display icons and other graphic

display tools are applied via the SCADA human machine interface (HMI) application software to depict the operating states of all monitored and controlled equipment on the workstation GUI. Table 4 provides an overview of the colour-coding of the existing switching stations’ supply and normal feeding configuration, a key feature on the above Network views.





SWITCHING

STATION

(CHAINAGE)

SUPPLY

SUBSTATION OHL SECTIONS

[FS TRACTION TRANSFORMER]

25KV FDR / OHL

COLOUR CODE

(SCADA GUI)

Seaford Depot TCU (34km)

Lonsdale FS

- 704 (Seaford Stabling Yard)

[LND/TFf7]

BLUE

Lonsdale FS (24.5km)

Dual (redundant) SAPN 66kV bulk supplies

- 701 (Seaford UP section)

- 702 (Seaford DOWN section)

[LND/TF7]

BLUE

- 601 (Ascot Park UP section)

- 602 (Ascot Park DOWN section) [LND/TF6]

RED

Lonsdale SVC (24.5km)

NA: The Lonsdale SVC provides dynamic stability at the 25kV bus feeding traction transformers LND/TF7 & LND/TF6

NA

Ascot Park TSC (10.15km)

Lonsdale FS

- 603 (City UP section)

- 604 (City DOWN section)

- 611 (Tonsley section / Spur line)

[LND/TF6]

RED

Table 4: 25kV TPSS – Feeder Colour Coding - Adelaide Station to Seaford Section

The existing 25kV TPSS does not remotely monitor the state of hand-operated overhead line OHL track section isolators (TSI) used to switch / isolate OHL sections on the electrified 25kV network. These off-circuit TSI (see Figures 2 and 3 above) are defined as ‘hand-dressed’ devices on the Workstation GUI, and the ECO is required to obtain confirmation of the actual switch status from Authorised field personnel before manually amending the state of a specific TSI on the GUI.

8.2. Overview - Future Expansion

The ongoing electrification of the AMPRN requires expansion of the traction power SCADA system to enable remote monitoring and control of new traction power assets. DPTI prefers that any project works to extend the TPSS to new switching stations or integrate new assets (e.g. MTSI) on electrified sections should minimise modification to the existing TPSS. However, this DPTI preference does not preclude complete - or part - replacement of the existing TPSS where DPTI deems it is cost-effective to do so. Consequently, project proponents may propose to modify or replace any aspect of the existing TPSS to accommodate an extension of the rail network, or integrate new assets on electrified sections, subject to the following requirements:

Any works to extend the TPSS to new traction power assets or integrate new assets on electrified sections shall at least provide equivalent performance and functionality to the existing TPSS, as specified in Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document;

All TPSS works shall comply with the general requirements of this specification;

Project proponents must familiarize themselves with the detailed characteristics of the existing TPSS (refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document) prior to proposing any modification;

Where DPTI determines the modification proposal has merit, the project proponents may be required to submit a detailed waiver application to the Manager Electrical Engineering to support the proposal;

When required by DPTI, such detailed waiver applications shall: o Identify each aspect that is proposed to be modified;





o Specify alternate systems, subsystems and equipment, as relevant, for each aspect that is proposed to be modified;

o Demonstrate that each aspect proposed to be modified complies with the relevant portions of this specification;

o Demonstrate how each aspect proposed to be modified shall be implemented with no unplanned impacts to - or reduction in - existing train services.

The Manager Electrical Engineering may also require the project proponent to submit a cost/benefit analysis with the detailed waiver application to demonstrate the positive net value of the proposed modifications.

The Project proponents shall be responsible in providing the operator training to the ECO’s and administrator training to the relevant engineering personnel, the qualifications shall be made to suit the Australian Qualified Framework training requirements.

Since SCADA system consists of a number of sub systems like software, hardware equipment like RTU, computers and other communication interface devices, it will be the responsibility of the tenderer/ project proponents to provide successful integration & satisfactory performance of complete system.

8.3. Future Expansion – Miscellaneous Notes

Project proponents should note that the 3-off ECO Workstations at the ROC and BCC are shared workstations that allow a single duty operator to remotely monitor and control traction power assets serving both:

the electrified sections of the 25kV Adelaide Metro rail network, and

the Adelaide Metro tram network, which is electrified at 600V DC. Aside from the shared workstations (refer to Figure 4), the train and tram traction power SCADA systems are functionally independent control networks.

Figure 4 – Shared TPSS ECO Workstation at the Rail Operations Centre

Project proponents should also note that remotely controlled motor-operated track section isolators (MTSI) will be installed at key locations in future. Works to integrate new MTSI into the existing TPSS shall ensure that:

Local hardwired / electronic interlocks are provided between the MTSI and the relevant switching station 25kV circuit breakers that feed the associated





portions of the traction overhead system. That is, control integrity of MTSI shall not rely on software interlocks applied at the master station SCADA level.

Each MTSI RTU communicates with the master stations via redundant data channels on the DPTI optic fibre data transmission network.

Each MTSI installation is provided with an SAPN LV supply and an LV DC battery.

9. Traction Power SCADA Functions

9.1. Primary Functions

Traction power SCADA systems provide the means for a skilled operator to remotely monitor and control traction power networks from a computer-based workstation located at a master station within a rail control centre. Operator Functions

The AMPRN TPSS’ must provide the duty ECO the capability to:

Command the real-time switching of remote power supply and feeding arrangements at outstations where the controlled switchgear is motorised by design.

Monitor the real-time operating state and functional status of all remote electrical switchgear, traction power equipment and associated auxiliary equipment at outstations.

In real-time, remotely monitor: o The secure state of the outstations, and o The electrical supply characteristics (voltage, current, power quality) and energy

consumed on the supply and feeding arrangements at switching stations, and o Provide time synchronisation between the master station and outstations and

associated time tagging of systemic information. Process functions

The AMPRN TPSS' must provide the duty ECO and the SCADA Engineer:

An optimal human machine interface (HMI) for efficient system operation;

Optimal information logging and reporting tools to aid decision-making;

Reliable data storage and tools for detailed analysis of archived historical events;

Tools to manage and modify the TPSS configuration.

9.2. Support Functions

The above AMPRN TPSS primary functions are dependent on hardware and software systems that must provide:

A set of real-time services providing the following support functions: o Data acquisition: to acquire any digital or analogue information from the field

equipment through RTUs. o Control processing: to send commands to field equipment through RTUs. o Alarms and events management: to generate, display and sort events, prioritise

and escalate specific events as alarms, process alarm acknowledgement and manage avalanche data flow events

o Archiving: to store data and events in an historical database and allow subsequent retrieval for analysis.

o Internal Supervision: to control and monitor SCADA equipment such as servers, workstations, communications equipment and RTUs.

A set of off-line services providing the following support functions: o Playback: to replay previously recorded data and events from the historical

database to allow analysis of any operational incidents; o Reporting: to generate, edit and print various plots or reports from archived data

of daily operations.





o Simulation: to test configuration changes of the TPSS, and to emulate the TPSS environment offline to train future operators;

o Engineering utilities: to perform database administration, including configuration

of the SCADA database, edit graphical user interfaces to create f displays, dialogue boxes, etc. and set user access controls.

10. Systemic Functional Requirements

10.1. Overview

The overall TPSS architecture must have the following attributes required for a real-time environment:

ATTRIBUTE FUNCTIONS

Computer-based

Platforms for all required applications, integration and connectivity; and to meet performance requirements such as redundancy, fault-tolerance, and system loading conditions

Flexible architecture

That utilises a distributed database model to provide improved reliability and expandability, and

To support implementation of additional applications that are not constrained by the system data model, and.

Scalable platforms

To achieve performance requirements such as worst-case peak / avalanche conditions, input-to-display responses times, failover times and spare capacity

Graphical operator interfaces

That are logical and simple to use for operator interaction and for the creation or alteration of databases for system reconfiguration by SCADA engineers

Open communication protocols

That are industry-standard and independent of individual vendors

Communication systems

That provide a secure interface via data communications technology, including TCP/IP based network solutions, and

That operate predictably when field communications have failed

Common infrastructure

To provide standard functionality such as data acquisition, real-time database, alarm and event monitoring, historical data logging & archiving, reporting and user access control.

Table 5: Systemic Functional Requirements

10.2. Equipment Interface Requirements

The designer shall specify all TPSS equipment interfaces relevant to the project scope, which may include the following basic interface functions:

ITEM REQUIREMENT

Outstations - Process equipment interfaces

Electrical interface criteria to the outstation process equipment (e.g. protection relays / IED’s and hardwired connections).

Interface conditions to SCADA equipment

Power supply to the outstation process equipment

Data communications equipment (DCE)

Interface between DCE and the data transmission channels & data transmission media

Power supply to data communications equipment, if the DCE is not an integral part of any SCADA equipment.

The LAN switches, routers, LAN extenders or media converters (as required with copper or OFC medium respectively), bandwidth management hardware & software and networking wiring etc. in RCC shall be within the scope of supply of successful SCADA tenderer

Bandwidth and frequency allocations of data channels.





ITEM REQUIREMENT

Master Station Equipment

Interface between SCADA equipment and DCE

Interface between operator’s workstation and SCADA server equipment.

Power supplies to SCADA equipment.

Table 6: Typical TPSS Equipment Interfaces

Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document provided upon request for characteristic details of all interfaces

between existing TPSS equipment, which functionality and performance shall not be diminished through modification.

10.3. Data Acquisition & Processing Functional Requirements

The designer shall define all project-specific data and data quantities to be acquired and processed for remote supervision of traction power assets from the following sources:

DPTI standard “Traction Power System Principles and Practices – Train System” (TP1-DOC-001097), which specifies the minimum required controls, indications, alarms and metering associated with 25kV switching station assets.

Existing Signalling I/O Schedules for equivalent equipment at outstations and the master stations

Project-specific requirements and documentation, including drawings (e.g. single-line diagrams, schematics, fabrication drawings, etc.) and other information (e.g. equipment datasheets);

Designers may be required to specify acquisition and processing of the following information:

ITEM REQUIREMENT

Input & acquisition of monitored information

Single point information (e.g. for alarms, state information, etc.)

double point information with / without intermediate states (for circuit-breakers, isolators, etc)

integrated values for telecounting (e.g. energy values);

measured values (analogue or digital) for telemetering;

time tagging requirements;

group / common alarms derived from digital /analogue information;

System information (e.g. equipment failure alarms, etc.);

Output & presentation of information

state information

double point information with / without intermediate states

alarms, group alarms, common alarms

pulse output or persistent indication of integrated values

analogue or digital display or measured values

information logging

data storage functions

Command inputs

switching commands: single commands / double commands

set point commands: values transmitted to controlled equipment;

adjusting commands: to change state of operational equipment having more than two states;

regulating commands (analogue or digital)

select and execute commands;

command sequences;

group commands: addressed to several items of equipment

commands related to the system itself





ITEM REQUIREMENT

interrogation commands

check commands: to ensure equipment is functioning correctly

Command outputs

single commands

double commands with / without supervision of faulty states

set point commands with / without validity indication and storage

adjusting commands

command sequences

Table 7: Typical SCADA Data

The designer shall develop signalling I/O schedules to describe the data acquisition, data processing and data quantities relevant to each site. The format of signalling I/O schedules shall comply with existing templates to ensure integration with the existing TPSS.

10.4. RTU Functional Requirements

Remote terminal units shall comply with the following minimum functional requirements:

ITEM REQUIREMENT

General Shall be modular and utilise plug-in I/O modules, function modules, and communication modules

Signal I/O modules shall be hot swappable

Shall utilise high-speed CPU and communications processors

Shall be capable of pre-processing local process data

Shall include self-diagnosis and error reporting functions

Shall be capable of synchronisation by an external time signal (e.g. NTP)

Firmware Shall be the latest stable release

RTU Programming

Parameter assignment and programming shall use AS/IEC 61131-3 languages only

RTU shall have the capability to be re-programmed remotely or locally

Program & Data Storage

Shall use non-volatile memory

Data exchange Data exchange with field devices is dependent on equipment selection and configuration (Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for data exchange configurations to existing

field equipment)

The use of application protocol converters (e.g. Profibus to DNP3) is permitted, but should be minimised

Coordinate with SAPN to confirm the application data exchange

Diagnostic Interface

Shall include an external port to plug in a diagnostic/maintenance laptop

Time Synchronisation

Accurate clock Synchronization in a RTU depends on knowing the time taken to transmit a Telecontrol message to it from the central Controlling station containing the master clock time thereby permitting an allowance to be made for the transmission time during synchronisation.

Table 8: Minimum RTU Requirements

Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for detailed characteristics of the existing TPSS RTU, which

functionality and performance shall not be diminished through modification.





10.5. Data Transmission Functional Requirements

The TPSS shall communicate over data transmission networks provided by DPTI Communications. Data transmission shall comply with the following functional requirements:

ITEM REQUIREMENT

Data transmission channels

Provide redundant data channels between each RTU and the master stations

Provide redundant WAN links between duplicate SCADA servers at the ROC and BCC

Coordinate with DPTI Communications for optical fibre and transmission system points of presence at each site

Data link configuration

Communication paths & media used for data links shall at least be equivalent to that in Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document

Data link transmission speeds shall at least be equivalent to that in Knet #15311557 Hrail Traction Power SCADA System Architecture and Description document

Data transmission protocols

Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for existing data transmission protocols applied.

Data security Network switch & router ports not in use shall be locked

Failover Redundant data communications equipment shall be configured to automatically failover to the available channel

Transmission initiation mode

Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for data transmission initiation modes. Note spontaneous and cyclic data transmission (not polling) is applied on the existing AMPRN TPSS data network.

Transmission errors

The ratio of undetected data transmission errors shall not be greater than 10E-8.

Data flow conditions

The TPSS design shall prevent avalanche data flows that flood an operator with spurious alarms (e.g. on failure of data transmission)


A GPS receiver with antenna shall also be provided to synchronize the timing of the servers with that of standard satellite timing. This shall ensure that all the date/time stampings of the reports generated by the SCADA system would be accurate & hence comparable to any external report

Table 9: Minimum Data Transmission Network Requirements

10.6. Server Functional Requirements

Process and historical servers shall comply with the following functional requirements:

ITEM REQUIREMENTS

Process Servers

Shall be duplicated to meet the required availability target.

Shall be supplied with real-time, multi-tasking operating systems

Shall have the capacity to meet worst-case system failure scenarios

Shall be synchronised by external time signal (e.g. NTP)

Shall manage data acquisition from the process, control processing, events, alarms and internal supervision

Shall time-stamp process messages to millisecond precision

Shall provide seamless transfer of control from master server to standby server with no loss of data

Shall provide removable media to allow loading & storage of operating system and configuration data

Shall allow configuration data to be loaded via a data network interface

Should use solid-state hard drives for reliable operating system and process software





ITEM REQUIREMENTS

data storage

Shall either provide the historical data server functions listed below, or manage the flow of data to be archived to historical data servers

Shall interface to the Centralised Train Control (CTC) system and provide indications of the traction power supply state of each electrified track

Historical Data Servers

Shall be duplicated to ensure that no single fault causes loss of historical data

Shall include sufficient storage for a minimum 6-month period

Shall provide indications to alert the operator when the historical data storage is reaching capacity, and the data should be archived to removable media

Shall include removable media to allow permanent storage of data

Shall allow playback of stored data, including stored data on removable media

Shall allow configuration data to be loaded via a data network interface

Should use solid-state hard drives for reliable operating system, application software and historical data storage

Operating system

Shall use industry-recognised, international open standards (e.g. Microsoft, Unix) that provide a windows-based graphic user interface

Shall fully support the hardware on which it is installed

Should not be modified from the OS standard, except where a purpose-compiled version is supplied by the OS developer

Shall be the latest stable release

Shall not require software maintenance (e.g. patches and upgrades)

Application Software


Shall only be configurable using high-level, user-friendly programming languages that do not require software coding. The Software shall be general-purpose, menu driven, GUI based and fully user configurable.

Shall have facility for application engineering with necessary tools and library modules, so that it can be easily customized. It should be possible to customize the software to specific need of mimic and tabular displays, representation of various equipment and devices.

Shall be possible to create new symbols and add to this library. The online features of the application-engineering module shall allow for upgrades and modifications easily at site

SCADA software shall be capable of working on latest version of Microsoft WINDOWS operating system or open international certified.

Application software shall also include licensed copies of OS for all terminals, LAN interface software, diagnostic software, Communication system analysis software, Antivirus Software and any other software essentially required for satisfactory working of the system. This shall also include the software for RTU and / or LAN driver etc. The license fee wherever applicable of any of the above software shall be borne by the successful tenderer.

The tenderer shall be fully responsible for effective working of SCADA software and shall also provide after sales support, on chargeable basis even after expiry or warranty period as negotiated with end users

The software shall be compatible for working on IEC 60870-5-101 companion standard protocols based on IEC 60870-5-1 to 5 series of standards. It shall also support multiple channels for communication to all RTUs

The architecture of the software shall be modular and it should be possible to upgrade it to the newer versions of operating systems

The software shall give fast response to operator actions and system events. SCADA system stability should be sustained during event bursts. The software should be capable to support system working at high speed data transfer rates achievable over OFC communication networks.

The software/system performance should not degrade with the time as system is continuously up (due to generation of temporary files etc. which the software should be capable of cleaning/deleting automatically). The tenderer shall endeavour to ensure no software hanging, requiring restart of system or individual computers.





ITEM REQUIREMENTS

Software data logging functions should have flexible time and event based sampling from real time process database. All values should be registered with status/value and time stamp.

Complete SCADA application software may comprise of some commercial peripheral software therefore DPTI shall be indemnified against claims for infringements on rights of such software and only the valid licensed copies (CD/DVD’s) of complete SCADA application, commercial and peripheral software shall be supplied to the purchaser/basic user.

SCADA vendor shall provide all necessary run time utilities for successful running of the SCADA application. The utilities supplied by the Contractor along with operating system should be sufficient to independently execute the SCADA software without any problem.

The software should provide menu driven and user-friendly configuration. The configuration shall define the various devices, their attributes and the traction system specific details. The configuration of the software shall be carried out with the help of user/purchaser to cover all details/address/nodes of traction supply operation e.g. Interlocking, locked out signals, protection relays & elements, alarms with attributes, power blocks, parameter settings and display/picture screen properties etc.

The application software shall comply with DPTI’s ICT ISMF policy on information security. Although the SCADA system with dedicated network shall be kept isolated from the internet, it is the responsibility of SCADA vendor study the system vulnerabilities and build the necessary security solutions like firewalls, up to date antivirus software, no remote/e-mail/internet access, user access codes/passwords in the master station software and hardware so that any possibility of a cyber-intrusion or attacks is eliminated.

Application backup and recovery procedures shall also be well defined by SCADA vendor and end user shall be trained about the security threats and vulnerabilities involved in the systems

Device drivers Native device drivers shall be supplied


The software should have the facility to synchronize the Host computer clock through GPS. Master station servers shall be time – synchronized from the GPS receiver directly and WAN network and through to the traction site RTU’s.

Table 10: Minimum Server Requirements

Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for detailed characteristics of the existing TPSS server

configurations, which functionality and performance shall not be diminished through modification.

10.7. Workstation Functional Requirements

ECO workstation computers shall comply with the following functional requirements:

ITEM REQUIREMENT

Workstation PC’S

Shall be duplicated to meet the required availability target,

At least one of the ECO workstations shall be configurable as a Development & Training workstation

Shall be supplied with real-time, multi-tasking operating systems,

Shall be synchronised to the lead (master) process server, unless the (standby) workstation is in Development & Training mode

Shall provide seamless transfer of control from master workstation to standby workstation

Shall have the capacity to meet worst-case system failure scenarios,

Should use solid-state hard drives for reliable operating system and HMI application software data storage

Shall provide removable media to allow loading & storage of operating system and





ITEM REQUIREMENT

configuration data

The SCADA graphics should support zoom in/out facility with clutter/de-clutter function. When zooming in more details (static as well as dynamic data) on the graphics should become visible, and when zooming out the details should get hidden with only salient/important information visible

The zooming facility should not cause loss of clarity of the displayed information.

Operating system

Shall use industry-recognised, international open standards (e.g. Microsoft, Unix) that provide a windows-based graphic user interface

Shall fully support the hardware on which it is installed

Should not be modified from the OS standard, except where a purpose-compiled version is supplied by the OS developer.


Shall not require software maintenance (e.g. patches and upgrades)

Application Software

Shall be the latest stable release in line with server

Device drivers Native device drivers shall be supplied

Table 11: Minimum Workstation Requirements

Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for detailed characteristics of the existing TPSS workstation

configurations, which functionality and performance shall not be diminished through modification.

10.8. HMI Functional Requirements

The Human Machine Interface (HMI) is the means by which the ECO views the TPSS and interrogates all monitored devices and subsystems, initiates control switching, notes acknowledgment of command actions, notes and acknowledges alarms, views analogue parameter values, accesses parameter trends and prints reports of the traction power network. The HMI shall comply with the following functional requirements:

ITEM REQUIREMENT

General The workstation GUI shall be structured using windows-based utilities to be easily and quickly navigable

User Access Shall be via secure login

Shall be graded based on each user’s authority to view or operate or operate & configure the TPSS

Application software


Shall only be configurable using high-level, user-friendly programming languages that do not require software coding

Application software on a Development workstation shall allow the SCADA engineer to quickly and easily implement offline configuration changes to the SCADA database representation of the traction power supply network

Application software on a Training workstation shall allow a trainee to operate a realistic, offline simulation of the TPSS

Operator Controls

The ECO must be able to:

o Select between redundant equipment items to nominate the leading (master) and the standby equipment items;

o Confirm each remote switching command prior to the execution of the command;

o Apply a command lock (i.e. lockout) to any controllable device to prevent the execution of commands on that device until the command lock is removed by an





ITEM REQUIREMENT

operator of equivalent authority;

o Apply a message lock to any monitored or controlled device to suppress message processing for that device;

o De-couple an RTU (place out of service) for maintenance

o Operate commands and if the same could not be executed, then a message shall be displayed indicating reason(s) for it e.g.: Time out, comms loss, remote device no response etc... shall be aborted after a predefined period and shall not be in queue

o Have an option to abort a command before giving the confirmation

o See the below minimum inherent features as report status or alarms

a) Online/standby /offline state of SCADA server/communication front ends. b) State of all RTUs. c) State of printers.

d) Connection status of all the operator workstation. e) Updated/Correct state of the plant

o Have the facility for marking (Manual input) for any alarms, equipment status including manually operated isolators, measurands and limit-settings, through keyboard.

Messages All process messages shall be viewable in a chronologically sequenced message list, message lists shall be searchable and sortable

Alarm Management

Alarms shall be prioritised hierarchically based on the level of urgency

Minimise alarms for single events

Each alarm class (priority) shall be indicated by a different acoustic tone

Each alarm class shall be signalled by different graphic indications (e.g. colour-coding, fill, text, blinking effects, etc) on the GUI displays

All alarms shall be displayed in a single Alarm list view, which is chronologically sequenced

At minimum, the alarm list shall define the date, time (in milliseconds), user, device name and description associated with each alarm

Alarm lists shall be searchable and sortable

The ECO / operator is required to acknowledge each alarm

Shall have the facility for alarm acknowledgement with a single click should also be provided in addition to one by one acknowledgement

Shall have the facility for time delayed alarm operation e.g. alarm for SVC Tripped 30 min CB closing reminder

Workstation Views

At minimum the following workstation views shall be provided:

System view/s that provide an overview of the state of all master station equipment and associated communication links between all devices,

System Help view/s that provide a legend describing all possible states and associated graphic indications (e.g. icons, colour-coding, fill, text, blinking effects, etc) for all equipment states & alarms displayed in the System view

Semi-geographical Network view of the complete traction power network,

Network / Switching Station Help view/s that provide a legend describing all possible states and associated graphic indications (e.g. icons, colour-coding, fill, text, blinking effects, etc) for all equipment states & alarms displayed in the Network view and in each Switching Station view

Separate views for each Switching Station

Separate views of any specialised TPSS components

Screen Displays

Shall be customisable to allow simultaneous display of:

o Alarm list

o System view or System Help view, or Network Help view,

o Complete semi-geographical view of the traction power network, and

o Two separate switching station views.

Shall be of sufficient resolution to ensure the operator can detect state changes from a seated position at the workstation desk





ITEM REQUIREMENT

Iconography and graphic indications

Icons and graphic indications applied on the workstation GUI should conform to the existing HMI (refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document), with the following exceptions:

o Provide industry-standard icons for new equipment types specified as part of the project works (e.g. motorised trackside isolators)

o Provide unique colour-coding for each new 25kV OHL feeding arrangement, as specified in project-specific documents (e.g. minor sectioning diagram)

Reporting The HMI shall provide comprehensive reporting functions that allow the ECO or SCADA Engineer to plot, trend and/or print system data, such as measured or integrated process values, etc

Table 12: Minimum HMI Requirements

Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for detailed characteristics of the existing TPSS HMI, which

functionality and performance shall not be diminished through modification.

10.9. Auxiliary LV Power Supplies

Redundant LV power supplies are required for all TPSS equipment. The specific configuration of LV AC and LV DC supplies required to achieve redundancy is location specific, as follows:

Master Stations: refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for the compliant configuration of existing LV

power supply arrangements at the ROC and BCC, which include redundant LV AC supplies, UPS systems with a limited (30-minute) hold-up time and generator backup, and;

Switching Stations: refer to DPTI standard “Traction Power System Principles and Practices – Train System” (TP1-DOC-001097) for the redundant LV AC power supply and station battery requirements.

The LV power supply and associated earthing arrangements to TPSS equipment shall comply with AS/NZS 3000 and AS/NZS 3008.1.1 and shall incorporate surge protective devices that comply with Telecommunications Technical Standard (Surge Protective Devices for Telecommunication Applications – AS/NZS 4117) 2015. TPSS equipment shall be installed in structures that comply with AS/NZS 1768 - Lightning protection.

10.10. Equipment Enclosures

All TPSS equipment enclosures shall be robust and secured in lockable enclosures.

Refer to Knet # 15311557 Hrail Traction Power SCADA System Architecture and Description document for the security, layout & construction requirements for master

station server racks.

Refer to DPTI standard “Traction Power System Principles and Practices – Train System” (TP1-DOC-001097) for the security, layout and construction requirements of RTU Panels, Marshalling Panels and Communications Racks at switching stations.





11. Operational Performance Requirements

Traction power SCADA systems are vital to the efficient operation of the Adelaide Metropolitan train network and shall be capable of remotely operating the traction power systems continuously, 24 hours a day, 7 days a week. The AMPRN TPSS shall consist of redundant equipment or fault tolerant equipment throughout to achieve the required high availability and accommodate the operator’s physically remote location from the traction power assets being controlled & monitored. Project proponents for TPSS works shall demonstrate that the works meet or exceed the operational performance requirements specified in this section. This demonstration shall comply with the requirements in EN50126 - “Railway Applications – The Specification and Demonstration of Reliability, Availability, Maintainability and Safety (RAMS).

11.1. Operational Availability Target

The TPSS shall be available for operational use for greater than or equal to 99.95% of the time (availability class A3 per AS 60870.4). The specified availability target represents an overall system unavailability time of less than or equal to 4.5 hours per year. The TPSS is considered unavailable where any of the following conditions apply during normal service on the rail network:

Loss of any function due to a physical or logical communication failure;

Loss of any function due to equipment hardware or software failure;

Loss of any function due to equipment software upgrade. TPSS system services unavailability shall be less than or equal to 3 failure events per year. TPSS field assets at outstations may be considered available when the specific outstations are removed from service under a planned track outage, such as during a scheduled track possession. New or modified TPSS installations shall achieve the availability target by meeting all operational reliability and maintainability performance requirements.

11.2. Operational Reliability

All TPSS products and systems shall be off-the-shelf, industrial-type products and systems with proven application within railway environments. All TPSS products and systems shall be procured from internationally recognised vendors with a permanent office in Australia. Vendors shall be capable of providing ongoing technical support services from Australia for the service life of their installed products and systems. Proposed TPSS products and systems specified shall not be so mature as to be obsolete or unsupported by the vendor at the end of the required service life. Consequently, vendors shall provide the following to project proponents:

The date at which the product was released for sale.

The planned date on which the product will be withdrawn from sale.

The planned date that product support will be withdrawn, such that spares will not be available and technical support will not be provided.





Project proponents shall submit evidence of the above product / vendor requirements. All TPSS works shall apply the following operational reliability principles:

Single points of failure shall be overcome by redundancy or alternative operational procedures.

The failure of a single component shall not result in failure of the associated subsystem or the system.

The failure of any single component shall only result in the loss of the function provided by that component.

11.3. Maintainability

The following maintainability principles shall be applied in all TPSS works:

Common equipment and components shall be provided to minimise spare parts holdings;

Subsystems, consisting of multiple integrated components, shall provide self-diagnosis;

Component failures shall be indicated immediately to allow for repair or replacement;

Subsystems, consisting of multiple integrated components, shall be modular and capable of being placed back into service by the replacement of modular components;

A single technician shall be able to remove, replace and test modular components;

Spare parts lists shall be provided for each repairable component;

Recommended spare part holdings shall be derived from a RAM Demonstration, which shall specify the smallest permissible Line Replaceable Units for all equipment types.

RTU’s, servers and workstation PCs shall not require routine or planned maintenance.

Integrated fans and internal batteries are not permitted in any computing equipment (containing a CPU / microprocessor), including RTU’s, servers, workstation PC’s, protocol converters, etc.

11.4. Expandability

TPSS’ shall be designed to allow the addition of new equipment to be supervised in future, without the need to replace existing equipment.

Hardware expandability:

The addition of new equipment shall be feasible by the simple addition of cards or racks / shelves on a modular basis.

Outstation RTUs – provide a minimum 20% spare capacity for each type of I/O used at each site. Provide additional empty slots on the RTU backplane where the required spare capacity cannot be met on procured I/O cards.

Equipment enclosures – provide a minimum 20% useable space capacity within panels / racks to allow the installation of additional equipment in future.

Software expandability:

The addition of software-managed items shall be carried out by modification of parameter databases / tables.

The size of the parameter databases / tables shall not constrain the addition of new items.

Software licenses procured shall include tag counts for the required spare I/O capacity.





11.5. Security

Provide a secure TPSS data network resilient to unauthorised access and vandalism. The data network shall comply with:

Communications Network Principles and Practices for Public Transport - Engineering Standard (PTS-AR-10-CN-SPE-00200400), Section 17 – Security,

the South Australian Government’s “Information Security Management Framework (ISMF DPC/F4.1), and

AS/NZS ISO/IEC 27002 Information Technology–Security techniques–Code of practice for information security Controls, Section – Physical and environmental security”.

11.6. Control integrity

The TPSS shall not provide electrical safety functions required to mitigate the risk of harm to passengers, staff or the public from electrical faults within the electrified areas. These regulated electrical safety functions shall only be provided by:

Independently operated HV & LV electrical switchgear and associated protection devices installed at switching stations to detect and interrupt electrical faults;

Earthing & bonding provisions at switching stations, and on the wider electrified train overhead line network, to dissipate electrical faults safely.

The integrity of traction power controls shall only depend on local substation automation controllers (e.g. IEDs / protection relays) serving the primary electrical elements at each outstation. That is, the integrity of traction power controls shall not depend on the SCADA and/or data transmission network systems and subsystems. Interlocking rules for each outstation’s primary electrical elements shall only be implemented within the local substation automation controllers (e.g. IEDs / protection relays) serving that outstation. The local substation automation system (e.g. IEDs / protection relays) serving the primary electrical elements at each outstation shall ensure that no unsafe states will occur regardless of any SCADA control inputs to the local substation automation system. Remote control of the primary electrical elements at outstations (e.g. controlled motorised switchgear) shall only be initiated from the ECO workstation at the master stations.

11.7. Data Integrity

TPSS design shall incorporate data integrity levels appropriate for the intended application and comply with all relevant standards, including EN 50128.

11.8. Timing Precision

All field RTU’s shall be capable of time-stamping event data received from field equipment to a precision of ±1 millisecond.

11.9. Response Times

TPSS shall provide the following operational response times:





Term Definition Maximum

Value

RTU processing time Elapsed time for an RTU to complete a single execution of its program

100 milliseconds

Operator control action

Elapsed time between an ECO initiated control action and HMI update (subject to acknowledgement by the RTU)

1 second

ECO Workstation screen load time

Elapsed time to load the active TPSS application server local data to the ECO Workstation HMI

1 second

Spontaneous messaging time

Elapsed time between a spontaneous field condition input to an RTU and notification on the ECO Workstation HMI

3 seconds

TPSS Server changeover time

Elapsed time to transfer system control from lead Master server to standby Master server (or vice versa) with no data loss

3 seconds

Data bearer failover detection time

Elapsed time between the detection of failure of A or B communications path on any LAN or Control Bus and notification on the ECO Workstation HMI

3 seconds

System restart time Elapsed time for the TPSS to reach operational capability after a cold restart of all system components

2 minutes

Table 13: Response times

11.10. Equipment Service Life

TPSS hardware shall be fit for the intended purpose for a minimum service life, calculated from the date the equipment is commissioned into service, as follows:

EQUIPMENT SERVICE LIFE

Master Station IT equipment 7 years

All other equipment (excluding cables and cable reticulation) 15 years

Cables and cable reticulation associated with traction power SCADA Systems

30 years

Table 14: Equipment Service Life

11.11. Software Service Life

TPSS software shall be fit for the intended purpose for the service life of the equipment on which it is installed, calculated from the date the equipment enters service.

11.12. Environmental Performance

TPSS equipment shall achieve service life and reliability, availability and maintainability (RAM) requirements under the following environmental conditions:

CONDITION RANGE / COMPLIANCE

Ambient operating temperatures – Air-conditioned installation -5°C to 40°C

Ambient (shade) operating temperatures – Field installation, not air-conditioned [Note 1]

-5°C to 55°C

Storage temperatures -10°C to 60°C

Temperature shock changes ±10 °C

Relative humidity (non-condensing) 5% to 95%

Altitude 1000 metres

Solar radiation 1100 W/m2

Ground acceleration (seismic rating) [ Note 2] 0.2 g

Ingress Protection - Indoor equipment enclosures & housings [Note 3] IP 21 (per AS 60529)





CONDITION RANGE / COMPLIANCE

Ingress Protection - Outdoor equipment enclosures & housings [Note 3] IP54 (per AS 60529)

Atmospheric Corrosion - Indoor equipment [Note 4] C2 (per AS 4312 \ AS/NZS 2312.1)

Atmospheric Corrosion - Outdoor equipment [Note 4] C4 (per AS 4312 \ AS/NZS 2312.1)

Electromagnetic compatibility - Field /outstation equipment - [Note 5] EN50121 (set)

Electromagnetic Compatibility - Master Station equipment - [Note 6] AS/NZS 61000.6.2

AS/NZS 61000.6.3

Table 15: Equipment Environmental Conditions

Note 1: Air temperature in direct sunlight may be up to 15°C above shade

temperature. Note 2: Applies to As-installed equipment. Field equipment (except cables) supplied for installation shall comply with AS 60068.2 ‘Environmental testing – Tests’. Note 3: Provide heat dissipation calculations to demonstrate that internal temperature

build-up within equipment enclosures and housings does not exceed the maximum operating temperature of any enclosed equipment. Natural ventilation of the enclosure or housing is preferred. Where dedicated mechanical ventilation or air-conditioning is provided to the SCADA equipment enclosure or housing to dissipate heat, demonstrate that the dedicated mechanical ventilation or air-conditioning system meets the traction power SCADA system service life and component RAM requirements. Note 4: A lower atmospheric corrosivity category for outdoor equipment is only permitted where a durability assessment is provided to demonstrate that the specific site's proximity to the coast, local pollution environment and/or atmospheric microenvironment (e.g. air-conditioned room) complies with the proposed alternate category. Note 5: Field Equipment shall be immune to, and comply with, the relevant

electromagnetic emissions limits in EN50121-2 'Electromagnetic compatibility - Part 2: Emission of the whole railway system to the outside world'. EMC Compliance certificates are required for all equipment. Note 6: EMC Compliance certificates are required for all equipment.





12. General – Design Requirements

Detailed designs shall provide sufficient information to permit project proponents to proceed to procurement, manufacturer and construction of all aspects of the project-specific scope. Contractual documents will specify project scope and associated design deliverables, which may include the following:

ITEM REQUIREMENT

Project Plans Project-specific management plans including:

o Design and Engineering Management Plan

o Requirements Management Plan

o Safety Requirements apportionment

o Systems Engineering Management Plan

o Technical Interface Management Plan

o Verification & Validation Plan

Configuration Design Report

A design report summarising the design basis, design inputs and design outputs with respect to:

o System topology & configuration

o Equipment interfaces

o Data acquisition system design

o RTU design and configuration

o Data communication network design & settings

o Server, Workstation and Data storage design and configuration

o Detailed HMI design, etc

Other Reports

RAMS Analysis & Report, including recommended spares holdings

Testing & Commissioning Requirements

System Design & Programming

RTU configuration, customisation and programming (e.g. interlocking, isolation, propagation rules and control logic requirements applicable to traction power devices at each outstation)

Process server software configuration, customisation and programming

Historical data server software configuration, customisation and programming

HMI application software configuration, customisation and programming

Database administration, including engineering utilities

Training simulator

Signalling I/O Schedule/s

Schedules detailing all hardwired and serial/networked I/O required to control and monitor each site, formatted for compatibility with the SCADA database

Hardware Specifications

RTU specifications

Communications equipment specifications

Process server equipment specifications

Historical data server equipment specification

HMI and display client equipment specifications

Design Drawings

System topology drawings (layout and operation of the system)

Site / equipment specific detailed schematics (block diagrams, logic, wiring, earthing, etc)

Site / equipment specific detailed technical drawings

Equipment lists

Calculations Capacity calculations (e.g. equipment capacity, spare capacity, heat loading, cables, etc)

Supporting datasheets

Fabrication Drawings

Developed by manufacturers to manufacture / fabricate equipment

Table 16: Typical Design Requirements





13. General - Testing and Commissioning Requirements

The TPSS designer shall identify all testing & commissioning requirements for all equipment, subsystems and systems in the project specific TPSS design. Project proponents (e.g. contractors) shall develop a Testing & Commissioning Plan, including proposed hold points, for endorsement by the Manager Electrical Engineering prior to the manufacture or construction of any TPSS equipment or systems. The Testing and Commissioning Plan shall include the order and timing of all factory acceptance tests, site acceptance tests, commissioning testing and system integration tests, as relevant to the project. Project proponents shall notify the Manager Electrical Engineering 4 weeks in advance of each test, who may elect to attend or send a representative.

13.1. Factory Acceptance Testing

The following TPSS equipment shall undergo Factory Acceptance Testing (FAT) at the manufacturer’s premises before delivery to site:

Remote Terminal Units (RTU)

RTU panels/racks

Marshalling panels

Servers

Server panels/racks

Communication panels/racks

Project-specific Inspection and Test Plans (ITP) shall be developed to document FAT procedures for each type of equipment to be tested and must be endorsed by the designer and the Manager Electrical Engineering (or nominee) before the conduct of the relevant FAT. The manufacturer shall sign a release certificate upon successful completion of each FAT and attach a copy to the tested equipment for delivery to site.

13.2. Site Acceptance Testing

Site Acceptance Testing (SAT) shall verify the condition, layout, functionality and operation of all TPSS equipment, subsystems and systems installed at each site. Project-specific ITP shall be developed to document SAT procedures for verification testing of all site-specific equipment, subsystems and systems, and must be endorsed by the designer and the Manager Electrical Engineering (or nominee) before the conduct of the relevant SAT.

Project-specific SAT-ITP must include relevant tests to verify:

Condition and layout of all equipment;

Compliant bonding of all equipment to earth;

Integrity of power & communication cabling between local equipment (per cabling schedules and network schematics);

Auxiliary LV power supplies to local equipment (per LV single line diagrams)

RTU startup, loading of program settings/parameters and diagnostics at outstations (per design & manufacturers data)

Point-to-point testing: Local station interface and function tests of all signals between the RTU and the local traction power equipment and infrastructure process equipment (per I/O schedules).





Basic communications network within the master stations

Control system (server and workstation) startup, loading of project data and diagnostics at master stations (per design & configuration data)

Interface and function tests of all signals between master station controllers and Workstations.

Verification of all alarm classes and associated graphic indications on the HMI

The testers and project proponent shall sign a release certificate upon successful completion of each SAT and submit this to the Manager Electrical Engineering for endorsement.

13.3. Commissioning Testing

Commissioning testing shall verify the end-to-end functionality and operation of all remotely monitored and controlled field equipment at outstations from the master station. Conduct commissioning tests after completion of the construction and verification of the data transmission network between master stations and outstations (by others). TPSS commissioning shall only commence after the completion of testing of any HV equipment that is monitored and controlled (e.g. after secondary injection of HV protection). TPSS commissioning shall be completed prior to energisation of any HV equipment that is monitored and controlled. Project-specific ITP shall document commissioning test procedures for verification of end-to-end functionality, and must be endorsed by the designer and the Manager Electrical Engineering (or his nominee) before the conduct of the relevant SAT. Project-specific commissioning-ITP must include tests of all potential failure modes associated with equipment, subsystems and systems, to verify:

Testing of communications between master stations and every RTU

Time synchronisation testing between master stations and every RTU

ROC-BCC SCADA redundancy testing

End-to-end interface and function tests of all remote-control signals from the ECO workstations to all controlled switchgear at each outstation. The testers and project proponent shall sign a release certificate upon successful completion of all commissioning tests and submit this to the Manager Electrical Engineering for endorsement.

13.4. System Integration Testing

System Integration Testing shall verify the functionality and performance of the traction power SCADA system in response to the highly variable and potentially severe conditions on an operational railway. SIT shall only commence after all project-specific works (e.g. including rolling stock, if relevant) have been completed, tested and commissioned.

System Integration Tests typically include:

Testing of the stability and reliability of the traction power system and associated TPSS during operational tests of rolling stock under widely varying headway and train loading conditions, generating varying voltages, currents and harmonics throughout the traction power system.

TPSS response and recovery to stress tests / failure events induced on traction power and TPSS equipment, subsystems and systems (e.g. Short-circuit testing of





the traction power system, de-energising of a master SCADA server, RTU or communications equipment, etc.)

Electromagnetic emissions compliance testing on the railway as a whole and at traction power substations (per EN50121).

The testers and project proponent shall sign a release certificate upon successful completion of the SIT and submit this to the Manager Electrical Engineering for endorsement.

Download - Traction Power SCADA Functional & Performance ......TPS Traction Power System TPSS Traction Power SCADA System TSC Track Sectioning Cabin (25kV traction) TSI Track Section Isolator

Top Related