Hrail Traction Power SCADA System Architecture and Description … · 2021. 2. 3. · Hrail...

Hrail Traction Power SCADA System Architecture and Description – Train

Rail Commissioner

TP1-DOC-003130

Hrail Traction Power SCADA System Architecture and Description

Document Number: TP1-DOC-003130 Knet No (PDF): 15855578

Version Number: 1 Knet No (Word): 15311557

Document Owner: Electrical Engineering Issue Date: 10-August-2020 UNCONTROLLED WHEN PRINTED Page 2 of 72

DOCUMENT CONTROL





TABLE OF CONTENTS

1. Introduction .................................................................................................................. 6

2. Configuration Overview ............................................................................................... 6

3. Equipment Configuration – Master Stations .............................................................. 6

3.1. ROC Workstations .............................................................................................. 7

3.2. BCC Workstation ................................................................................................ 7

3.3. ROC SCADA Servers & SCADA LAN ................................................................. 7

3.4. BCC SCADA Servers & SCADA LAN ................................................................. 9

3.5. Master Stations - SCADA Server Components ................................................... 9

3.6. Master Stations - PLC Components .................................................................. 10

3.7. Master Stations – Network Equipment Components ......................................... 11

3.8. Master Stations – TPSS Network Characteristics ............................................. 13

3.8.1. LAN Redundancy ................................................................................. 13

3.8.2. WAN Redundancy ............................................................................... 14

3.8.3. Security ............................................................................................... 14

3.9. Master Stations – Power Supply & Earthing ...................................................... 15

4. Equipment Configuration – Data Transmission System ......................................... 16

4.1. Overview of DPTI Rail Communications Network ............................................. 16

4.1.1. Terrestrial Optic Fibre Network ............................................................ 17

4.1.2. OPGW Optic Fibre Network ................................................................. 17

4.2. TPSS Data Transmission Network .................................................................... 18

4.3. TPSS Network – IP Addressing ........................................................................ 18

4.4. Addressing - Traction Power ASDU Allocation .................................................. 20

4.5. Voice over IP Telephones ................................................................................. 21

5. Equipment Configuration – Switching Stations ....................................................... 22

5.1. Control System Overview.................................................................................. 22

5.2. Controllable Equipment ..................................................................................... 22

5.3. Control System Configurations.......................................................................... 24

5.3.1. Lonsdale FS –Control & Monitoring System ......................................... 24

5.3.1. Ascot Park TSC –Control & Monitoring System ................................... 25

5.3.1. Seaford TCU –Control & Monitoring System ........................................ 26

5.4. RTU Specifications ........................................................................................... 27

5.5. Building Services I/O ......................................................................................... 28

5.6. LV Supplies I/O ................................................................................................. 29

5.7. Signalling I/O Schedules ................................................................................... 29

6. TPSS Software System - Overview ........................................................................... 31

6.1. Project Editor .................................................................................................... 31

6.2. Control Sequence Editor ................................................................................... 32





6.3. Training Application .......................................................................................... 32

6.4. Applying New Project Data ............................................................................... 33

6.5. Telecontrol (SCADA) Interfaces ........................................................................ 33

6.6. Overview of Runtime System Software ............................................................. 33

6.6.1. Operator Interface Functions ............................................................... 34

6.6.2. Data / Process Management Functions ............................................... 35

6.6.3. Specialised Functions .......................................................................... 36

6.7. Archiving Functions........................................................................................... 37

7. TPSS Runtime System Implementation .................................................................... 38

7.1. Overview of Operator HMI ................................................................................ 38

7.2. SYSTEM Views ................................................................................................ 38

7.3. NETWORK Views ............................................................................................. 39

7.3.1. OHL/Track Sections ............................................................................. 39

7.3.2. Track Section Isolators ........................................................................ 42

7.4. Switching Station Views .................................................................................... 42

7.4.1. Switching Command Functions ............................................................ 42

7.4.2. Other Management Functions .............................................................. 44

7.5. User Access Rights........................................................................................... 46

7.6. Lists .................................................................................................................. 46

7.6.1. Logbook ............................................................................................... 46

7.6.2. Alarms ................................................................................................. 48

7.6.3. Operator Notes .................................................................................... 48

7.6.4. State List.............................................................................................. 49

7.7. Plotting Analogue Values .................................................................................. 49

8. Historical Data Storage .............................................................................................. 49

8.1. Short-term Data Storage on Master Servers ..................................................... 49

8.2. Longer term Storage & Evaluation .................................................................... 50

9. Detailed HMI Views .................................................................................................... 52

9.1. Background Colours ......................................................................................... 52

9.2. Alphanumeric Characters.................................................................................. 52

9.3. Application & Indicator Tool Bars ...................................................................... 52

9.4. Lists .................................................................................................................. 52

9.4.1. Logbook (Messages) ........................................................................... 53

9.4.2. Warning List (Alarms) .......................................................................... 53

9.4.3. State List (Control deviation) ................................................................ 54

9.4.4. Notice list (Notes) ................................................................................ 54

9.5. “SYSTEM” View ................................................................................................ 55

9.6. “SYSTEM_HELP” View ..................................................................................... 56





9.6.1. Servers and RTU – State Descriptions & Colour Coding ...................... 57

9.6.2. CTC Interface via Local PLC 1 ............................................................. 58

9.7. “NETWORK” View ............................................................................................ 58

9.8. “NETWORK_HELP” View ................................................................................. 61

9.8.1. Depiction of Traction Power Equipment ............................................... 62

9.9. “LND_FS” View ................................................................................................. 67

9.10. “LND_BS” View ................................................................................................. 68

9.11. “ASP_TSC” View .............................................................................................. 69

9.12. “SFD_TCU” View .............................................................................................. 70

9.13. “SMS” and “BCC UPS Status” Views ................................................................ 71

10. References .................................................................................................................. 72





1. Introduction

This Addendum describes the characteristics of the existing Adelaide Metropolitan Passenger Rail Network (AMPRN) 25kV traction power SCADA system (TPSS), which was commissioned into service under the ‘Adelaide Rail Revitalisation - Electrification’ project in 2014. Addendum A is structured as follows:

Sections 16 to 18 provide the hardware context, describing the equipment installed and associated configurations, stepping top-down from the master station Level through the data transmission network to the Switching station Level.

Sections 19 to 22 provide the software context, describing the application software, the specific control and indication considerations for the AMPRN 25kV traction power network and the operator HMI.

Section 23 lists reference documentation for further reading.

2. Configuration Overview

The AMPRN 25kV TPSS is arranged in two levels interconnected by data networks:

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 (FS),

Lonsdale SVC, Ascot Park Track Sectioning Cabin (TSC) and Seaford Depot Track Coupling Unit (TCU) 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 A1 - Overview - Configuration of existing AMPRN (25kV) traction power SCADA system

3. Equipment Configuration – Master Stations





The 25kV TPSS utilises a Siemens Vehicle and Infrastructure Control and Operation System (VICOS) Rail SCADA (RSC) software system and associated hardware to provide an operator interface and systemic process functionality to remotely control and monitor the 25kV traction power network from the Workstations located at the ROC and BCC. The VICOS RSC application operates on multiple SCADA Server and Workstation PC’s running either Microsoft Windows Server 2008 or Microsoft Windows 7 operating systems. The traction power SCADA systems at the ROC and the BCC operate as independent Control Systems, with the ROC typically being the lead control system.

3.1. ROC Workstations

The duty Electrical Control Operator (ECO) at the ROC monitors and controls the 25kV traction power system via the ECO Workstation located in the ECC room. A second HotStandby Workstation is installed adjacent to the ECO Workstation, and provides identical functionality, but is currently used primarily for system development & training. Table A1 lists the main components of the two ROC Workstations, excluding the operator’s desk, chair and file storage arrangements.

COMPONENT ECO WORKSTATION HOTSTANDBY WORKSTATION

PC Type 21" Rack PC 21" Rack PC

Operating System Windows 7 Windows 7

CPU Intel Dual core i5-2400 Intel Dual core i5-2400

Main Memory DDR3 2GB DDR3 2GB

Hard disk 500GB 500GB

DVD-ROM Yes Yes

User Interface 5 x 23” LCD monitors (PCI), keyboard (PS/2), mouse (PS/2)

5 x 23” LCD monitors (PCI), keyboard (PS/2), mouse (PS/2)

LAN (Ethernet) 2 x RJ45 ports 2 x RJ45 ports

VICOS RSC Dongle Yes (USB internal) Yes (USB internal)

Table A1 - ROC Workstation components

3.2. BCC Workstation

The alternate ECO Workstation located in the Mile End Level 1 BCC Control room is configured identically to the ROC Workstations and permits engineering oversight of the traction power SCADA system from Mile End. Should the primary ECO Workstation at the ROC fail, the alternate ECO Workstation at the BCC can be used to monitor and control the traction power network.

3.3. ROC SCADA Servers & SCADA LAN

The SCADA Server Cabinet located in the Dry Creek ROC Server room G.11 at the ROC contains the main components of the TPSS, listed in Table A2, which are interconnected to form a SCADA LAN, shown in Figure A2.

COMPONENT FUNCTION

Master Server 1 The Master Server is the primary component of the traction power SCADA System. Master Server 1 at the ROC manages the monitoring & control process, for example by immediately archiving all messages, measured values, metered values,





COMPONENT FUNCTION

comments, announcements, notes and system messages in the message archive, measured-value archive and metered-value archive respectively.

Process Server 1 Process Server1 at the ROC provides an interface to all Switching station RTUs using SCADA protocol IEC 60870-5-104. The field data collected is transferred to Master Server 1 for further processing.

Archive Server 1 Archive Server 1 provides for longer term data storage and evaluation. The data exported from the circular buffer of Master Server 1 is stored (automatically or manually) in a database on Archive Server 1.

Local PLC 1 A local PLC (connected to the Master Server 1 via RS 232) provides the Central Train Control (CTC) system operators with indications of the traction power supply state of each electrified track (via digital outputs).

Ethernet Switches 1 & 2 Two Ethernet switches provide the communication interface for all TPSS equipment at the ROC. The switches are redundantly configured to form a dual SCADA LAN, with a bandwidth of 100Mbps.

Routers 1-4 Routers 1 to 4 provide redundant interfaces between the ROC SCADA LAN and the data transmission network. Two routers interface to the 100Mbps WAN interconnecting the ROC and BCC, while the other two routers interface to the 10Mbps WAN serving the switching stations.

Router 5 (cRSP) Router 5 (a cRSP router) provides the Manufacturer with a facility to remotely access the TPSS through a secure interface. Following an access request to the DPTI Authorised Person/system administrator, the router is first physically connected and thereafter logically connected to the State Government corporate network via a firewall and thence to the internet to allow remote access from specific IP addresses on the manufacturer's network.

Router 6 Router 6 provides the capability to interface to a future ROC NTP (SNTP) Server (i.e. Master Clock) via a firewall, for centralised time synchronisation of the TPSS equipment. Currently, the Dry Creek Communication Network switches TS1 and TS2 provide NTP signals to TPSS Ethernet Switches 1 & 2, which provide NTP synchronisation to the TPSS servers.

GPRS Router A GPRS Router connected to Ethernet Switch 2 only, provides a facility to broadcast SMS notifications to personnel over a mobile network.

Server Cabinet User Interface

A keyboard, mouse and display are provided to operate the Master / Process / Archive Servers in the Cabinet. The devices are connected using a Keyboard, Video and Mouse (KVM) switch.

Table A2 – Components in ROC SCADA Server Cabinet

The ROC Server cabinet components are redundantly connected for reliability as per Figure A2.





Figure A2 – Redundant configuration of ROC Server Cabinet components

3.4. BCC SCADA Servers & SCADA LAN

The standby SCADA Servers and SCADA LAN, installed in a dedicated SCADA Server Cabinet at the BCC, are identically configured to that at the ROC (refer to Table A2 and Figure A2 above), except that:

Local PLC 2 at the BCC monitors the state of the BCC UPS, and does not have a serial (RS232) interface to the Master Server 2, and thus does not communicate with the Central Train Control (CTC) system

No GPRS Router is provided at the BCC for SMS notifications to personnel

The equipment naming conventions differ at the BCC, as follows:

ROC SCADA SERVER CABINET COMPONENT BCC SCADA SERVER CABINET EQUIVALENT

Master / Process/ Archive Server 1 (typically lead)

Master / Process/ Archive Server 2 (typically standby)

Local PLC 1 Local PLC 2

Ethernet Switches 1 & 2 Ethernet Switches 3 & 4

Routers 1, 2, 3, 4 Routers 7, 8, 9, 10

Router 5 (cRSP) Router 11 (cRSP)

Router 6 Router 12 Table A3 –SCADA Server Cabinet equipment naming convention

3.5. Master Stations - SCADA Server Components

The main components of each of the SCADA Servers at the ROC - and the duplicate SCADA Servers at the BCC - are listed in Table A4.

Component Master Server 1 / 2 Process Server 1 / 2 Archive Server 1 / 2

PC Type (Product)

19" Rack Industrial PC (Simatic IPC547D)



Operating System

Windows Server 2008 Windows 7 Windows 7

CPU Intel Dual core i5-2400 Intel Dual core i5-2400 Intel Dual core i5-2400

Main Memory DDR3 2GB DDR3 2GB DDR3 2GB





Component Master Server 1 / 2 Process Server 1 / 2 Archive Server 1 / 2

Hard disk 500GB 500GB 500GB

DVD-ROM Yes Yes Yes

User Interface Common LCD monitor, keyboard, mouse, interfaced via KVM switch (Model MINIMUX4-RM, Manufacturer Guntermann & Drunck),

LAN (Ethernet) 2 ports (RJ45) 2 ports (RJ45) 2 ports (RJ45)

VICOS RSC Dongle

Yes (USB internal) Yes (USB internal) No

Table A4 – SCADA Master, Process and Archive Server Components

3.6. Master Stations - PLC Components

The main components of the PLC’s at the ROC and BCC are listed in Table A5.

Component PLC 1 (ROC) PLC 2 (BCC)

Product Simatic S7-300 RTU Simatic S7-300 RTU

Program Software (function block diagrams)

Step7 Step7

CPU CPU315-2 PN/DP CPU315-2 PN/DP

Communication Processor (Ethernet to Process Server 1 or 2))

CP 343-1 CP 343-1

Communication Processor (Serial to Master Server 1 only)

CP 341 -

Digital Output module (hardwired - 32 outputs at 24V DC)

SM332 SM332

Digital Input module (hardwired - 32 inputs at 24V DC)

SM321 SM321

Power Supply SITOP PSU100L SITOP PSU100L

Table A5 – PLC Components

Local PLC 1 at the ROC only collects the power supply status of all 25kV overhead line/track sections from the Master Server 1 via an RS232 serial interface (CP-341 processor), and communicates these supply states via hardwired connections from the SM332 digital output module to the Central Train Control (CTC) System (see Figure A3). Local PLC 2 at the BCC only monitors the TPSS UPS at the BCC. Both Master station PLC’s are configured as IEC 60870-5-104 Remote Terminal Units (RTU) in the VICOS RSC Project Editor. The supply status of all electrified overhead line sections is provided to the CTC System, including:

Section 601 (Ascot Park Up section)

Section 602 (Ascot Park Down section)

Section 603 (City Up section)

Section 604 (City Down section)

Section 611 (Tonsley section)

Section 701 (Seaford Up section)

Section 702 (Seaford Down section)

Section 704 (Seaford stabling yard)





Figure A3 – PLC 1 (ROC / OCC) Interface to CTC System

3.7. Master Stations – Network Equipment Components

Basic specifications for the network switches and routers installed in the SCADA Server Cabinets at the ROC and BCC, which provide communication interfaces to all TPSS equipment, are listed in Table A6 and Table A7.

Item Network Switches

Manufacturer Cisco

Model C2960S-24TS-L

Basic Technical Specification

Operating temperature: 0 to 45ºC

Operating relative humidity (non-condensing)

10 to 85%

Configuration -24 x Ethernet 10/100/1000 ports - 4 x Gigabit Ethernet SFP ports

Voltage, Current, Frequency, Power

- (auto-ranging) 100 to 240 VAC - 1 to 0.5 A - 50 to 60 Hz - 0.09 kW





Item Network Switches

Availability and Scalability - N master redundancy allows each stack member to serve as a master, providing high reliability for forwarding - Equal-cost routing for load balancing and redundancy. - Uplink bandwidth can be upgraded by adding a 10 Gigabit Ethernet version to a wiring-closet stack and replacing the Gigabit Ethernet uplinks with 10 Gigabit Ethernet without having to change fibre pairs.

Performance Inter-VLAN IP routing for full Layer 3 routing between 2 or more VLANs.

Network Security - IEEE 802.1x with VLAN assignment allows a dynamic VLAN assignment for a specific user regardless of where the user is connected. - Cisco security VLAN ACLs on all VLANs prevent unauthorised data flows from being bridged within VLANs.

Manageability - Up to 1005 VLANs per switch or stack - Up to 128 spanning-tree instances per switch

Configurable maximum transmission unit (MTU)

- MTU of up to 1546 bytes for bridging and routing on Fast Ethernet ports. - MTU of up to 9000 bytes with a maximum Ethernet frame size of 9018 bytes (jumbo frames) for bridging on Gigabit Ethernet ports.

Table A6 – Network Switches –Basic Specification

Item Routers

Manufacturer Cisco

Model 892-K9

Basic Technical Specification



10 to 85%

Configuration - LAN switch: 8 x Ethernet 10/100 Mbps ports - WAN: 1 x Gigabit Ethernet port, 1 x Fast Ethernet port

Voltage, Current, Frequency, Power

- (Universal) 100 to 240 VAC - 0.6 to 0.26 A - 50 to 60 Hz - 0.06kW

Availability - Redundant WAN connections for failover protection and load balancing -Dynamic failover protocols such as Virtual Router Redundancy Protocol (VRRP; RFC 2338), Hot Standby Router Protocol (HSRP), and Multigroup HSRP (MHSRP) - Dial in backup with external modem through a virtual auxiliary port

Performance The router can run multiple services simultaneously with no performance degradation

Network Security - Firewall with advanced application and control - Site-to-site remote access and dynamic VPN services: IP Security (IPSec) VPN's, Group Encrypted Transport VPN (GET VPN] with onboard acceleration and Secure Sockets Layer [SSLVPN]

Table A7 – SCADA Routers – Basic Specification





Figure A4 depicts the configuration of the ROC SCADA network switches and routers. The configuration of the BCC SCADA network is similar, except for the different equipment naming conventions (see Table A3), and the lack of a GPRS Router.

Figure A4 – ROC Network Equipment Configuration

3.8. Master Stations – TPSS Network Characteristics

The traction power SCADA communications networks are configured for redundancy and security as follows:

3.8.1. LAN Redundancy

The two network switches at the ROC (and separately at the BCC) are arranged to form a dual SCADA LAN with a bandwidth of 100Mbps at each site.

Communication between the SCADA LAN network switches is via ether-channels. The two physical ports on each switch are joined into a single virtual port, which provides a higher bandwidth during normal operation. In the event of a fault on one port/cable the minimum bandwidth of the remaining switch port is available.

Every Workstation and Server has a dual-LAN interface (RJ45 ports & Ethernet cables) to the switched network.

Every dual-LAN interface is configured in teaming mode, with the “Switch-Fault-Tolerance” feature enabled allowing the LAN-interface to automatically switch over to the other interface in the event of a fault.





Redundancy towards the data transmission networks (Wide Area Networks) is provided by hot-standby-routers.

All TPSS equipment is time synchronised using the standard network time protocol (NTP/SNTP). o At present, the communications network switches TS1 and TS2

at Dry Creek provide the time source for the TPSS. o However, the existing TPSS configuration makes provision for

time synchronisation from local dedicated NTP Servers (Master Clocks) to be installed at the ROC & BCC in future.

In the unlikely event of a failure of the time source, the Master Server's internal clock will provide a time synchronisation signal to the other servers & workstations and to the RTU via the data transmission system.

3.8.2. WAN Redundancy

Two Wide Area Networks (WAN) are configured for SCADA communications over the DPTI data transmission networks, namely:

The ‘Control Centre Bridge’ WAN o Routers 3&4 (ROC) and 9&10 (BCC) interface to the Control

Centre Bridge WAN, which connects the ROC to the BCC over the DPTI data transmission network using Transparent Ethernet (e.g. transport of HSRP, STP, RSTP, MSTP, VLAN’s, etc data) at 100Mbps

o Routers 3&4 and 9&10 are configured as hot-standby-router pairs, and the WAN-Ports of the router-pairs are thus visible to each other within the WAN.

o One of the two local routers at each site (e.g. Router 3 at ROC and Router 7 at BCC) is the nominal master router, from which all traffic is transmitted towards the WAN. Should the connection to the master-router be disturbed, traffic is automatically switched over to the standby-router. During this change-over-period the communication between ROC and BCC may be disturbed for a few packages.

The ‘Switching Station WAN’ o Routers 1&2 (ROC) and 7&8 (BCC) interface to the Switching

station WAN, which connects the ROC & BCC to the field switching stations over the DPTI data transmission network using Transparent Ethernet (e.g. transport of OSPF, HSRP, STP, RSTP, MSTP, VLAN’s, etc data) at 10Mbps

o The IEC 60870-5-104 protocol is used for communication between the Master stations and Switching stations over the Ethernet TCP/IP data transmission network.

Refer to Section 17 and Section 18 below for redundancy on the data transmission network and at the switching station interfaces.

3.8.3. Security

All SCADA communications network and process control equipment (switches, routers, servers) at the ROC / BCC are installed in lockable Server Cabinets inside locked rooms (keycard access) within secure facilities.

Switch & router ports not in use are turned off, and “port security” is activated within the network components.





All SCADA LAN interfaces are via router including the connections to the two data transmission networks, the (normally disconnected) links to the Government Network and the provisions to connect to future Master Clocks at the ROC and BCC. If the dedicated local Master Clocks are provided at the ROC & BCC in future, firewalls will be installed between the SCADA LAN and proposed Master Clocks to protect time synchronisation data exchange with the Master Server.

Firewalls provided between the cRSP router and the State Government corporate network at ROC / BCC permit secure remote access for maintenance by the manufacturer. o Note that the cables between the cRSP routers and the State

Government corporate network are normally disconnected to comply with the DPTI ICT Information security management framework system (ISMS).

o To gain access, the manufacturer must request a DPTI Authorised person/system administrator to connect and enable the connection to the relevant cRSP router. Thereafter a technician can access the Master/Process/Archive Servers from a defined set of IP addresses on the manufacturer’s corporate network via a DMZ (Demilitarized Zone) and VPN (Virtual Private Network). After establishing a VPN-tunnel, the technician connects to the Servers using the Windows Remote Desktop application.

o All connections are monitored and logged, and the system can be configured to send an SMS to specific DPTI personnel to notify when a technician remotely accesses the SCADA Servers.

3.9. Master Stations – Power Supply & Earthing

An Uninterruptible Power Supply (UPS) at each Master station site serves all traction power SCADA system equipment at that site. The power supply from the relevant ROC/ BCC LV Main Switchboards to each TPSS UPS’ are classed as essential supplies. Note that both the ROC & BCC LV Main Switchboards are supplied by alternate SAPN in-feeds and are backed up by onsite standby diesel generator (with a start time of 4 minutes). The UPS to the ROC TPSS equipment is provided and managed by the DPTI Signal and Train Control team. However, a dedicated TPSS UPS is provided at the BCC, and has the following basic specification:

Item Routers

Manufacturer Schneider Electric

Model APC Smart UPS RT 5000VA

Output

Topology Double-conversion online

Nominal output voltage 230 VAC

Efficiency at full load Up to 92%

Output frequency (sync to mains) 50 / 60Hz (± 3Hz, user adjustable)

Output power capacity 3500W

Output connections 8 x IEC 320 C13, 2 x IEC 320 C19

Input





Item Routers

Nominal input voltage 230 VAC

Input frequency 45 - 65 Hz (autosensing)

Input connections 3 wire (Active, Neutral, Earth)

Bypass Automatic & Manual (built-in)

Battery

Battery type Maintenance-free, lead-acid battery with suspended electrolyte; leak proof; hot-swappable

Battery pack SURT 192XLBP APC Smart-UPS RT 192V battery pack

No. battery packs (per UPS) 1

Battery runtime estimate at half-load

71 minutes

Battery runtime estimate at full load

30 minutes

Typical recharge time 2.5 hours

Communications & management

Interface ports RJ45 10/100 Base T, RJ45 serial, SmartSlot

Pre-installed SmartSlot card AP9631

Emergency Power off Yes

Control Panel LED's

Physical

UPS cabinet (Netshelter SX 24U) Height: 24 RU, Width: 19" (H1198xW600xD1070)

UPS Height: 3RU, Width: 19"

Battery Pack Height: 3RU, Width: 19"

Automatic transfer switch Height: 1RU, Width: 19"

Table A8 – BCC UPS – Basic Specification

Two UPS-supplied 230VAC (50Hz) terminals are provided inside each SCADA Server Cabinet at the ROC and BCC. The SCADA Server cabinets are bonded to the local structure earth via G/Y cabling from earthing studs (M12) in the server cabinet. Separate 230VAC UPS supplies are provided to each Workstation. The workstation equipment is earthed through the protective earth (PE) conductor of the power supply sockets.

4. Equipment Configuration – Data Transmission System

4.1. Overview of DPTI Rail Communications Network

The DPTI rail communications network is a private network that consists of 2 independent network classes:

The Signalling Fibre Optic Transmission System (SFOTS), which is dedicated to the rail signalling system (including the Train Control System), and

The General Fibre Optic Transmission System (GFOTS), which serves all other rail systems including traction power SCADA, Passenger Information and CCTV.

On the electrified portions of the AMPRN, both network classes use common fibre optic communication bearers, connected in a ‘bridged’ ring formation, which consists of two geographically diverse segments between the ROC and field equipment, namely:





A terrestrial fibre optic network and

An OPGW (optical ground wire) fibre optic network, reticulated on SA Power Network infrastructure.

Copper communications bearers are used on non-electrified portions of the AMPRN.

Figure A5 – DPTI Communications Network – Backbone Overview

4.1.1. Terrestrial Optic Fibre Network

The terrestrial fibre optic network consists of 24-core single mode optic fibres, divided into 4 tubes containing 6 fibres each. The allocation of tubes is as follows:

Tube Tube Colour Rail Network External System Interface Allocation

1 Blue SFOTS Signalling

2 Orange GFOTS Belair Line, Spare

3 Green GFOTS Passenger information / CCTV

4 Brown GFOTS Traction Power SCADA and VOIP

Table A9 –DPTI Communications – Terrestrial Fibre – Tube Allocations

Tube 4 of the terrestrial fibre is only spliced at traction sites, where dedicated traction routers are installed within control rooms to interface to the local equipment.

4.1.2. OPGW Optic Fibre Network

The diverse OPGW fibre optic network consists of two tubes, with 12 optic fibres each. The traction power and VoIP communications utilise 6 fibres in Tube 2, as shown in Figure A6 below.





Figure A6 – DPTI Communications Network – OPGW Tube and Fibre Allocations

4.2. TPSS Data Transmission Network

The Traction SCADA network is designed in a dual bus configuration, with the ‘A’ bus using the terrestrial fibre as the communication bearer and the ‘B’ bus using specific cores on the OPGW as the communication bearer. Two routers at each traction power site interface to the GFOTS network, one for the terrestrial fibre interface, and the other for the OPGW interface. Each Router is configured with a VLAN ‘3’ address, effectively providing a ‘Layer 2’ network under the OSI model. The VLAN ID’s and names used in all traction power SCADA switch/router configurations on the GFOTS network are listed in Table A10.

VLAN ID VLAN Name Description

1 Traction_ROC Traction - ROC

3 Traction_RTU Traction - RTU

4 Traction_Interconnect Traction – ROC & BCC

5 Traction_BCC Traction – BCC/TCF

Table A10 – TPSS Communications – VLAN Description

4.3. TPSS Network – IP Addressing

The IP addresses assigned to each of the TPSS network components are listed below.

Equipment Site IP Address Subnet Mask Standard Gateway

Master Server 1 ROC 192.168.1.1 255.255.255.0 192.168.1.253

Process Server 1 ROC 192.168.1.2 255.255.255.0 192.168.1.253

Archive Server 1 ROC 192.168.1.3 255.255.255.0 192.168.1.253

ECO Workstation ROC 192.168.1.4 255.255.255.0 192.168.1.253

HotStandby Workstation

ROC 192.168.1.5 255.255.255.0 192.168.1.253

Mimic Workstation ROC 192.168.1.6 255.255.255.0 192.168.1.253

Printer 1 ROC 192.168.1.20 255.255.255.0 192.168.1.253





Equipment Site IP Address Subnet Mask Standard Gateway

Local PLC 1 ROC 192.168.1.151 192.168.1.152

255.255.255.0 192.168.1.253

Network Switch 1 ROC 192.168.1.201 255.255.255.0 192.168.1.253

Network Switch 2 ROC 192.168.1.202 255.255.255.0 192.168.1.253

Master Server 2 BCC 192.168.5.1 255.255.255.0 192.168.5.253

Process Server 2 BCC 192.168.5.2 255.255.255.0 192.168.5.253

Archive Server 2 BCC 192.168.5.3 255.255.255.0 192.168.5.253

ECO Workstation BCC 192.168.5.4 255.255.255.0 192.168.5.253

Printer 2 BCC 192.168.5.20 255.255.255.0 192.168.5.253

Local PLC 2 BCC 192.168.5.151 192.168.5.152

255.255.255.0 192.168.5.253

Network Switch 3 BCC 192.168.5.201 255.255.255.0 192.168.5.253

Network Switch 4 BCC 192.168.5.202 255.255.255.0 192.168.5.253

Table A11 – TPSS – ROC & BCC - IP Addressing (excluding routers)

The IP addresses of the Traction Power SCADA Routers are listed below.

Equipment Sub-component IP Address Subnet Mask

Router 1 - ROC-side (virtual IP) - ROC-side - WAN-side

192.168.1.254 192.168.1.220 192.168.3.220

255.255.255.0

Router 2 - ROC-side (virtual IP) - ROC-side - WAN-side

192.168.1.254 192.168.1.221 192.168.3.221

255.255.255.0

Router 3 - ROC-side (virtual IP) - ROC-side - WAN-side (virtual IP) - WAN-side

192.168.1.253 192.168.1.222 192.168.4.1 192.168.4.11

255.255.255.0

Router 4 - ROC-side (virtual IP) - ROC-side - WAN-side (virtual IP) - WAN-side

192.168.1.253 192.168.1.223 192.168.4.1 192.168.4.12

255.255.255.0

Router 5 - ROC-side - WAN-side

192.168.1.252 (ON REQUEST)

255.255.255.0 (ON REQUEST)

Router 6 - ROC-side - WAN-side

FUTURE FUTURE

GPRS Router

- ROC-side 192.168.1.250 255.255.255.0

Router 7 - BCC-side (virtual IP) - BCC-side - WAN-side

192.168.5.254 192.168.5.220 192.168.3.222

255.255.255.0

Router 8 - BCC-side (virtual IP) - BCC-side - WAN-side

192.168.5.254 192.168.5.221 192.168.3.223

255.255.255.0

Router 9 - BCC-side (virtual IP) - BCC-side - WAN-side (virtual IP) - WAN-side

192.168.5.253 192.168.5.222 192.168.4.2 192.168.4.13

255.255.255.0





Equipment Sub-component IP Address Subnet Mask

Router 10 - BCC-side (virtual IP) - BCC-side - WAN-side (virtual IP) - WAN-side

192.168.5.253 192.168.5.223 192.168.4.2 192.168.4.14

255.255.255.0

Router 11 - BCC-side - WAN-side

192.168.5.252 (ON REQUEST)

255.255.255.0 (ON REQUEST)

Router 12 - BCC-side - WAN-side

FUTURE FUTURE

Table A12 – TPSS – ROC & BCC Routers - IP Addressing

The IP addresses of the TPSS RTU’s (except the ROC & BCC PLC’s, which are provided above) are listed in the table below, which includes numerous spare addresses for future extension / expansion.

Equipment IP Address Subnet Mask

Lonsdale FS RTU 192.168.3.1 192.168.3.2

255.255.255.0

Spares / Reserve 192.168.3.5 to 192.168.3.20

-

Ascot Park TSC RTU 192.168.3.21 192.168.3.22

255.255.255.0


-

Seaford TCU RTU 192.168.3.36 192.168.3.37

255.255.255.0


-

Lonsdale SVC RTU 192.168.3.85 192.168.3.86

255.255.255.0

Table A13 – TPSS – Switching Station RTU’s - IP Addressing

IP addresses reserved for maintenance and service devices are listed below.

Site IP Address Subnet Mask Standard Gateway

Maintenance - ROC

192.168.1.100 192.168.1.101 192.168.1.102 192.168.1.103 192.168.1.104

255.255.255.0 192.168.1.253

Maintenance - BCC

192.168.5.100 192.168.5.101 192.168.5.102 192.168.5.103 192.168.5.104

255.255.255.0 192.168.5.253

Switching Stations

192.168.3.100 192.168.3.101 192.168.3.102 192.168.3.103 192.168.3.104

255.255.255.0 -

Table A14 – TPSS – Switching Station RTU’s - IP Addressing

4.4. Addressing - Traction Power ASDU Allocation





The IEC-60870-5-104 addresses of all RTU’s, including spare addresses reserved for future extension, are listed in the table below.

Site - Equipment ASDU Address

Lonsdale FS RTU 1

Lonsdale SVC RTU 3

Spares / reserves 4 to 20

Ascot Park TSC RTU 21


Seaford TCU RTU 36


ROC - Local PLC 1 101

BCC - Local PLC 2 102

Table A15 – TPSS RTU’s - IEC-60870-4-104 addresses

4.5. Voice over IP Telephones

The DPTI Voice over IP (VoIP) telephone system has interface points at each traction power site for the connection of site telephones. The VoIP system relies only on the terrestrial fibre (‘A’ pathway) for communications and has separate network hardware for all sites except at the ROC. There is no redundancy in the VoIP network, which does not use the OPGW as a diverse return path. The VoIP network consists of a single VLAN, which is independent of the traction power SCADA network.





5. Equipment Configuration – Switching Stations

5.1. Control System Overview

The Switching station control systems are hierarchical systems for the control of substation equipment at various independent levels, classed as follows:

Level 0: Mechanical control of switchgear, for example: o Mechanical control of motorised 66kV and 25kV circuit breakers and

disconnectors (using racks/handles) is reserved for emergency operation only.

o Mechanical control of un-motorised 25kV disconnectors / earth switches is required to achieve specific supply states. [Note: manual switching of 25kV disconnectors and earth switches is in infrequent as traction power supply states are typically only amended for maintenance, either at the switching station or for track possessions.]

Level 1: Local control of switchgear, for example: o Local control of 25kV circuit breakers using push buttons on the 25kV

switchgear LV panels in the 25kV Switch room at Lonsdale FS, or o Local control of 66kV switches using key switch arrangements on the

LV panels (Lonsdale FS Control & Protection room only), or o Local control of motorised 66kV circuit breakers and disconnectors

using the Siprotec protection interfaces (Lonsdale FS Control & Protection room only)

o Local control of all other auxiliary devices and substation building services

Level 2: Station Level control, for example, by plugging a diagnostic laptop

into the industrial ‘Box-PC’ (provided for maintenance at Lonsdale FS only) within the RTU rack in the Control and Protection room.

Level 3: Remote Control of motorised switchgear, and monitoring of all other substation equipment, which is the normal practice.

Note that the failure of a Switching station RTU will not affect the ongoing operation of the Switching station itself.

5.2. Controllable Equipment

Most equipment at the Switching stations is only monitored. The only Switching station equipment that can be controlled – either locally, or remotely by the ECO at the ROC/BCC - are those HV circuit breakers and disconnectors that are motorised. The table below lists all motorised switchgear and associated protection relays at each switching station. It is recommended that this table be read with the relevant site single line diagrams.

Lonsdale FS Primary Equipment Protection (Secondary) Equipment

2x 66kV Incomer Circuit Breakers (8DN8)

Each with Siprotec 4 Relays - Main: 1x 7SJ647 - Cable Protn: by SAPN - Bus Diff: 1x 7UT635 - Power Quality: Simeas P600

2x 66kV Transformer (66/25kV 15MVA) Feeder Circuit Breakers (ASG25)

Each with Siprotec 4 - Transf (oil temp/pressure/level, winding temp) - Main: 1x 7UT635 - Backup: 1x 7SJ647





Lonsdale FS

1x SVC Transformer (66/7.5kV 20MVA) Feeder Circuit Breaker (ASG25)

Siprotec 4 - Transf (oil temp/pressure/level, winding temp) - Main: 1x 7UT633 - Backup: 1x 7SJ647

2x 25kV Incoming Circuit Breaker (ASG25)

Each Siprotec 4 - Main: 1x 7SJ645

1x25kV Bus Section Circuit Breaker (with Isolator) (ASG25)

Siprotec 4 (1x 7SJ64) - Main: 1x 7SJ645

4x 25kV OH Line Feeder Circuit Breakers (ASG25)

Each Siprotec 4 - Main 1x 7ST612 - Backup: 1x 7SJ802

Ascot Park TSC

Primary Equipment Protection (Secondary) Equipment

1x25kV Bus Section Circuit Breaker (with Isolator) (ASG25)

Siprotec 4 (1x 7SJ64) - Main: 1x 7SJ645

5x 25kV OH Line Feeder Circuit Breakers (ASG25)

Each Siprotec 4 - Main 1x 7ST612 - Backup: 1x 7SJ802

Seaford TCU

Primary Equipment Protection (Secondary) Equipment

1x 25kV Line Feeder Circuit Breaker

Each Siprotec 4 - Main: 1x 7SJ802

Table A16 – Switching Stations – Controllable Devices





5.3. Control System Configurations

5.3.1. Lonsdale FS –Control & Monitoring System

The Lonsdale FS control system is distributed across the site. All signals, however, are concentrated in the Control & Protection Room, as shown in Figure A7:

Figure A7 – Lonsdale FS – Control System Configuration

The main components of the Lonsdale FS control system within the Control & Protection Room include:

Communications Rack – provides the interface to the DPTI data transmission network (terrestrial fibre ‘Path A’ and OPGW ‘Path B’) via a FOBOT;

RTU Marshalling Panel (UX03) o A Prolinx Gateway in the RTU Communications Marshalling

Cubicle transmits a subset of 66kV switchgear data to the SAPN Control and Monitoring System via a DNP3.0 protocol serial link for monitoring purposes only. The data includes 66kV switchgear indications, warnings, trip signals, information about auxiliary system and measurement values;

o A Simatic ET200M collates all Building Services signals and LV AC / DC auxiliary signals from the 66kV Switchroom, 25kV switchroom and the Control and Protection Room, interfacing to the S7-400 PLC via PROFIBUS.

RTU Rack (UW01): o Two RUGGEDCOM RX1512 Ethernet Switches/routers

provide the WAN interface between the Lonsdale FS RTU and the FOBOT;

o A Simatic S7-400 RTU and associated modules, which interfaces to the two RUGGEDCOM network switches and to





all 66kV & 25kV protection panels and Building Services via PROFIBUS interfaces;

o An industrial “Box-PC”, which provides the Station Level diagnostic interface (including diagnostic HMI), accessed by a maintainer’s laptop

SVC Marshalling Cubicle (UX04) o The SVC Marshalling Cubicle collates all hard-wired I/O from

the SVC field devices. o A protocol converter installed in the SVC Terminal

Marshalling Cubicle converts all serial IO signals from the SVC controller into the IEC 60870-5-104 format. The protocol converter interfaces directly to the DPTI communications network via dual Ethernet ports.

Terminal Marshalling Panel (UX01) o Collates all hard-wired I/O from field devices, except for SVC

field devices and Building Services

5.3.1. Ascot Park TSC –Control & Monitoring System

The Ascot Park TSC control system, located in the Control & Protection Area, is arranged as shown in Figure A8 below:

Figure A8 – Ascot Park TSC – Control System Configuration





The main components of the Ascot Park TSC control system include:

Communications Rack – provides the interface to the DPTI data

transmission network (terrestrial fibre ‘Path A’ and OPGW ‘Path B’) via a FOBOT;

RTU Marshalling Cubicle (UX03): o Two RUGGEDCOM RX1512 Ethernet Switches/routers

provide the WAN interface between the Ascot Park TSC RTU and the FOBOT;

o A Simatic ET200M collates all Building Services signals and LV AC / DC auxiliary signals from the 66kV Switchroom, 25kV switchroom and the Control and Protection Room, interfacing to the S7-400 PLC via PROFIBUS.

RTU Rack (UW01) o A Simatic S7-400 RTU and associated modules, which

(among other functions) interfaces to the two RUGGEDCOM network switches via Ethernet ports, and to all 25kV protection panels via a PROFIBUS interface.

5.3.1. Seaford TCU –Control & Monitoring System

The Seaford TCU control system, located in a ground-mounted cabinet, is arranged as shown in Figure A9 below:

Figure A9 – Seaford TCU – Control System Configuration





The main components of the Seaford TCU control system include:

Communications Rack – provides the interface to the DPTI data

transmission network (terrestrial fibre ‘Path A’ and OPGW ‘Path B’) via a FOBOT;

RTU Rack (UW01): o Two RUGGEDCOM RX1512 Ethernet Switches/routers

provide the WAN interface between the Seaford TCU RTU and the FOBOT;

o A Simatic S7-300 collates I/O from the 25kV switchgear, the associated protection relay and the LV AC / DC auxiliary signals

5.4. RTU Specifications

The RTU’s at each Switching station are configured as listed below.

RTU Lonsdale FS Ascot Park TSC Seaford TCU

RTU Equipment Location

Control & protection Room at LND_FS

Control & Protection Room at ASP_TSC

Ground-mounted Cabinet

Product Simatic S7-400 RTU

Simatic S7-400 RTU

Simatic S7-300 RTU

IP Rating IP20 IP20 IP20

Operating temperature:

0 to 60ºC 0 to 60ºC 0 to 60ºC

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

Program Software Step7 Step7 Step7

CPU CPU 414-3 PN/DP CPU 414-3 PN/DP CPU315-2 PN/DP

Communication Processor (Ethernet - 2 x RJ45 ports)

CP 443-1 CP 443-1 CP343-1

DO module (hardwired, 32 outputs at 24V DC)

SM422 SM422 SM332

DI module (hardwired, 32 inputs at 24V DC)

SM421 SM421 SM321

Profibus extension module

CP443-5 NA NA

Table A17 – Switching Station RTU – Basic Specification

Note on SVC Controller Interface As noted above, a protocol converter, installed in the SVC Marshalling Cubicle in the Lonsdale FS ‘Control & Protection Room’ (see Figure A7), is used to convert serial IO signals from the SVC controller into the IEC 60870-5-104 format. The protocol converter interfaces directly to the DPTI communications network via dual Ethernet ports, and has the following base specification.





Item Protocol Converter

PC Type 19" Rack Industrial PC

Manufacturer IPComm

Model IPC191V3 (Linux OS)



5% to 90%

Power Supply Fanless, 24 V DC, Power consumption: max. 50 W

Mainboard - VIA Eden processor 600 MHz CPU - Max 1 GB DDRRAM - EIDE hard disk and flash disk drive interface

Serial Interfaces - Up to sixteen serial RS232 ports (DB9 male connectors) - 50 bps to 921.6Kbps transmission speed - 16KV ESD Protection

Ethernet Interfaces - 2 x Ethernet 10/100 Mbps BaseT (RJ45)

Table A18 – Lonsdale SVC – Protocol Converter – Basic Specification

5.5. Building Services I/O

The building services monitored at each Switching station site room are listed below.

Building Service

LN

D - S

AP

N

Bld

g

LN

D - 6

6kV

Bld

g

LN

D - 2

5kV

Bld

g

LN

D - C

ntrl &

P

rotn

Bld

g

LN

D - S

VC

Co

nta

iner

AS

P - T

Sc B

ldg

SF

D - T

CU

Cab

inet

Smoke Detector Alarm X X X X X X

Intruder Alarm X X X X X X X

Building / SVC container / TCU cabinet in Attendance

X X X X X X X

SVC Container / TCU Cabinet Door open

X X

Ventilation Fans Alarm X X

Air conditioner 1 X X X X

Air conditioner 2 X X X

Room Humidity - Sensor 1 % X X X X

Room Humidity - Sensor 2 % X X

Room Temperature - Sensor 1 X X X X

Room Temperature - Sensor 2 X X

SVC Cubicle Over-temperature X

RTU Panel temperature Warning X X

RTU Panel temperature Alarm X X

SVC Converter Room Door 1 key locked

X

SVC Converter Room Door 2 key locked

X

SVC Yard key locked X

Table A19 – Switching Stations – Monitored Building Services





Note that the I/O associated with the 2-off oil-water separators at the Lonsdale FS, which separately serve the two traction transformers and the SVC transformer, are excluded from the above table. The monitored signals for each oil-water separator include:

Oil-water separator fail

Sump high level

Oil tank high level, and

Transfer pump fail

5.6. LV Supplies I/O

The LV AC auxiliary signals monitored at each Switching station site are listed below.

LV AC Auxiliary Services LND ASP SFD

LV AC DB in local X X X

Supply 1 On (SAPN) X X X

Supply 1 Fail (SAPN) X X X

Supply 1 MCB trip X X

Preferred feed selector X X X

Supply 2 On (LND = SVC/GEN; Other sites = EST) X X X

Supply 2 Fail (LND = SVC/GEN; Other sites = EST) X X X

Supply 2 MCB trip X X

SVC Aux selected X

Generator selected X

Power conditioner fault X

MCB trip isolation transformer (SAPN) X

MCB trip for SVC X

MCB trip for 66kV switchboard X



Table A20 – Switching Stations – LV AC Auxiliary signals

The LV DC auxiliary signals monitored at each Switching station site are tabled below.

LV DC Auxiliary Services LND LND

SVC 1

LND SVC

2

ASP SFD

Rectifier fail X X X X X

AC fail X X X X X

Battery charger /controller failure X X X X X

CB Open X X X X X

Battery earth fault X X X X X

Battery temperature X X X X X

Low DC volts X X X X X

High DC volts X X X X X

Table A21 – Switching Stations – LV DC Auxiliary signals

5.7. Signalling I/O Schedules





The signalling I/O schedules for each traction power site comprehensively define all required process data at all levels including at:

The diagnostic HMI at the site (Lonsdale only)

The RTU (Profibus) Interface, and

The SCADA System HMI at the ROC/BCC The schedules, listed below for reference, are extensive and available on request.

Site Signalling I/O Schedule

ROC PTS-AR-TP-SK-LST-02970002

BCC PTS-AR-TP-SK-LST-02970003

Lonsdale FS PTS-AR-TP-SK-LST-02970005

Lonsdale SVC PTS-AR-TP-SK-LST-02970006

Ascot Park TSC PTS-AR-TP-SK-LST-02970004

Seaford TCU PTS-AR-TP-SK-LST-02970007

Table A22 – List of Signalling I/O Schedules

The signalling I/O schedules fields / columns are grouped by:

Equipment identifiers (Plant section identifier and Device identifier)

Signal text descriptions (e.g. “Opened” - circuit breaker open status indication)

Signal classifications, including o IEC signal type, such as SP [Single Point], DP [Double Point], SC

[Single Command], DC [Double Command], ME [Measured value] o Signal Class, such as CO [Command], OI [Operation Indication], WI

[Warning Indication], FI [Fault Indication], TI [Protection trip indication], SI [Signal], and MV [Measured value]

o Signal groups

Signal descriptors pertinent to the Lonsdale FS local diagnostic HMI (Box-PC) only (e.g. Indication, Operation, Sound, Event, Event number, Event Priority, Event Class, Event Type and Event Text),

Signal descriptors used for the RTU SCADA Interface, including: o RTU receive/transmit bits; o Signal types (command messages, single point messages, double point

messages and measured values) and associated class (command message, general message, warning message, fault message, trip message);

o Signal range (In the IEC 60870-5-104 protocol, a maximum 16 bits [two bytes] are used to represent an analogue value. If one bit is used for the algebraic sign, the maximum possible signal range for the analogue value is 0 32768. The signal range thus represents the bit value range associated with a specific analogue value transmitted from the RTU to the SCADA Control system via the IEC 60870-5-104 protocol, e. g. “0 32768” or “0 500” or “-10 +10”, etc).

o Rated range (the actual min / max range that an analogue value represents for a given signal, e.g. a signal range of say 0 14000 may be used to represent measured values derived from a feeder current transducer, where the feeder has an actual rated range of say 0 Amps to 1400.0Amps)

o IEC object number (The IEC 60870-5-104 telegram address of the signal, which is a unique identifier for each signal. The IEC Object No. is structured in 3 Fields, each with 8-Bit values)

The equivalent Signal descriptors used for the SCADA System HMI at the ROC/BCC (refer to Table A31 in Section 20 for these information fields).





Note on Digital I/O States The AMPRN signal database design follows the “normally open” concept for all single-pole indications. That is, the telegram bit is set to “1” (high) in the event of device fault/failure. Under normal operational conditions the telegram bit is “0” (low). For double-pole indications (e.g.to denote the switching state of a circuit breaker/switch) the 2 telegram bits are defined as follows:

“00” (0) = Undefined status

“01” (1) = Opened status

“10” (2) = Closed status

“11” (3) = Disturbed status

6. TPSS Software System - Overview

The 25kV TPSS utilises the Siemens Vehicle and Infrastructure Control and Operation System (VICOS) Rail SCADA (RSC) software system and associated hardware to provide an operator interface and systemic process functions to remotely monitor and control the 25kV traction power network from the Workstations at the ROC and BCC. The VICOS RSC applications run on Microsoft Windows OS platforms that provide:

A known user-environment operated using a keyboard, mouse and monitor which permits multi-tasking, window management and multi-screening capabilities, etc,

Stable hardware drivers, plug & play device recognition, etc., and

The capability to exchange data with other railway systems and/or integrate different IT systems on multi-functional terminals via standardised interfaces.

Specifically, the VICOS RSC applications operate on SCADA Server and Workstation PC’s running either:

Microsoft Windows Server 2008 – Master Servers 1 & 2 only; or

Microsoft Windows 7 - Process Servers 1 & 2, Archive Servers 1 & 2 and all Workstations.

The object-oriented VICOS RSC system architecture allows for modular configuration and distribution of system functions. The main VICOS RSC software applications include:

The VICOS RSC Project Editor & Control Sequence Editor, which are development applications installed on the HotStandby Workstation,

A Training application, installed on the HotStandby Workstation,

The Runtime System, installed on Master Servers 1 & 2, Process Servers 1 & 2, and the ECO Workstations at the ROC & BCC,

The VICOS RSC EVA archiving application installed on Archive Servers 1 & 2.

6.1. Project Editor

The VICOS RSC Project Editor on the HotStandby workstation at the ROC is used to configure the TPSS. The Project Editor’s functions allow a SCADA Engineer to:

Import device plans (e.g. control centre equipment schematics, overhead line sectioning diagrams and site single line diagrams), to use a basis for the development of HMI;

Use graphical tools to configure the entire system as ‘project diagrams’ (i.e. HMI views) that depict interconnections of all static or dynamic computing / communications / electrical network devices (objects) using symbols from an extendable system library.





o Note that the graphic interconnection of computing / communications / electrical devices (objects) in the Project Editor completely defines the system topology, and no coding is required.

Allocate protocol types (e.g. SNMP and IEC 60870-5-104) and assign (address) telegrams to each network device.

Define the process status of each network device under different conditions using colours, line widths, shading & other attributes (e.g. crossed out letters or symbols).

Set validation methods for network devices and operations (e.g. warning messages / operator guidance to be displayed in fault / information windows)

Output project data in the form of "txt" files, Microsoft Excel files, or printouts, etc.

6.2. Control Sequence Editor

The Control Sequence Editor application on the HotStandby workstation provides tools to develop control sequences to automate routine or complex switching operations. The SCADA Engineer develops control sequences by linking device symbols and applying operators, analogous to the development of a flow chart. Once defined, control sequences can be copied and organised in groups. The VICOS RSC System library provides the following generic control sequence operators:

Start - Identifies the start of a control sequence in the log

End - Identifies the end of a control sequence in the log

Stop - Stop the control sequence (e.g. due to a fault condition) and output a message

Delay – Set a delay in the control sequence (in seconds)

Operation o Select the device to be controlled and the sub-status to be controlled o Select if steps are to be acknowledged o Select control confirmation, if any o Set number of repetitions if (first) attempt is unsuccessful o Select command inhibit check, if any

Condition o Check the required condition to execute the next step, or o Check multiple (tabulated) decision elements to execute the next step o Abort in the case of an incorrect result

Branching o Check required conditions to execute branching, or o Check multiple (tabulated) elements for a branching decision o Branch the control sequence, depending on the result

6.3. Training Application

The Training application is a simulation program run on the HotStandby Workstation. It operates in parallel to the Runtime System using actual process data but is disconnected from the active Runtime System control process. The Training application has much of the functionality of the Runtime System (detailed in Sections 20 to 22 below) and allows operator training under realistic conditions.





6.4. Applying New Project Data

After configuration using the Editors, new project data is transferred from the HotStandby Workstation to a new Runtime System data directory (“LZSDATEN” directory) on the two lead/standby Master Servers. The SCADA Engineer can only upload new project data to the Runtime System using the process leading Master Server, typically Master Server 1 at the ROC. After the SCADA Engineer selects the new project data, and confirms selection, the new project data is transferred to all servers and workstations and the system shuts down & restarts with the new runtime data. Multiple different Runtime System data configurations can be applied (e.g. for commissioning and testing). Playback of older Runtime System data is also feasible, but historical data may be lost due to differences in Runtime System configurations.

6.5. Telecontrol (SCADA) Interfaces

Telecontrol interfaces (TCI) provides a connection between the control system and the process. The TCI collects process data from field devices (e.g. switching station RTU’s, or ROC/BCC PLC’s) and converts the data for further processing in the distributed VICOS RSC system.

The main functions of the telecontrol interfaces are to:

Control interrogation of field equipment

Compare old/new process data values, and

Manage the current process image

Two types of telecontrol interface (TCI) are configured in the AMPRN TPSS:

TCI for TCP/IP-based telecontrol protocols – this function is provided by

Process Servers 1 & 2 at the ROC and BCC respectively. The Process Servers exchange data with field devices using the IEC 60870-5-104 telecontrol protocol via LAN/WAN interfaces.

TCI for serial telecontrol protocols - this function is provided only by

Master Server 1 at the ROC. The Master Server 1 contains a VICOS RSC TCI server to interface to the Local PLC 1 (Simatic S7 400) serial interface module, which updates the Central Control System with the electrified state of all overhead line/track sections for the Adelaide Station to Seaford sections.

6.6. Overview of Runtime System Software

The VICOS RSC runtime application provides various generic software functions that are configured to form a specific operator interface. These generic functions are broadly classed as:

Operator Interface Functions

Data / Process Management Functions, or

Specialised Functions This functionality is introduced in tabular format below to provide context for the specific AMPRN TPSS Runtime configuration described in Sections 20 to 22.





6.6.1. Operator Interface Functions

Function Description

HMI The operator HMI includes all application toolbars, project diagrams (inclusive of all network electrical & communications components), graphic selection buttons and lists necessary to operate the system.

Access Rights User Access Rights specify the control system functions that can be accessed by each operator and are set by an Administrator (e.g. SCADA Engineer).

Lists Lists are windows that display operational events (i.e. messages) in text form, with up to 100,000 entries. All lists are navigable (e.g. via scroll bars), and can be filtered using date/time range, Switching Station identifier, Feeder identifier, Element identifier, Acknowledgement flags, etc.

Alarms A message (operational event) becomes an alarm when the message enters a status defined by one of the user-configurable alarm classes. Alarms are signalled to the operator through multiple mechanisms such as alarm tones, alarm messages in the operating window and flashing components on the HMI display (e.g. window, line, button or icon).

Operator Notes Note functions allow an operator to transfer information to other users (e.g. next duty shift operator) in various forms, such as: - An operator announcement entered in the logbook - An operator comment inserted in the various list types - An operator note attached to a switching element on the HMI display

Curve (Plot) Windows Measured data values can be graphically displayed in curve (plot) windows. The operator can display up to 6 plots simultaneously in one curve window by dragging and dropping values from the project diagrams. Archived values can also be displayed for comparison using forward and back buttons. The operator can set curve resolution to 1 second, 1 minute, 10 minutes, 1 hour or 1 day. Curves can be printed on the system printer.

Control Sequence Window

The operator accesses control sequence functions defined by the SCADA Engineer via the “CS” button in the operating window. The control sequence window allows the operator to: - Display all activated control sequences and their status - Preview control sequences (e.g. view the control sequence as a structured flowchart, zooming in/out) - Display the next step and associated messages - Start / continue step-by-step execution or termination of a control sequence - Skip current step, or interrupt the control sequence (as limited by the operator’s user access rights)

(Software) Interlocks Topological interlocking functions are software interlocks that automatically draw the operator's attention to incompatible network statuses during switching. Topological interlocks can be configured to check (incompatible) phase status, short-circuit / earth fault prevention. Note that a software interlock programmed by the SCADA Engineer using the Project Editor cannot be bypassed by the operator. Non-programmed software interlocking conditions can be bypassed by the operator, but the operator’s skip action is recorded in the logbook.

Table A23 – VICOS RSC Software – Overview of Operator Interface Functions





6.6.2. Data / Process Management Functions


Message Processing The preparation of system and process messages for display to the operator on the HMI. After processing, message information is shown in the project diagrams via configured symbols using colour changes, flashing and/or acoustic signals. Messages are time-stamped on arrival at the Process Server, unless time-stamped at the field source, using IEC 104 telegrams. VICOS RSC uses the following messages types: - System messages - Process indications - System-internal derived messages

System Messages Those Messages associated with - System operations (e.g.: login) - Computer (operating status / process status) - TeleControl (SCADA) Interface (operating status / TCI status / channel status) - Remote terminal unit (operating status / RTU error messages) - Control sequences (start / end / particular events within the sequence) - SMS mobile phone (operating status / provider messages) - Timeout

Process Messages (Indications)

Process messages from field devices, including - Single-point indications (1-bit) (rising / falling), - Double-point indications (2-bit) (on / off / disturbed / undefined), or - Fleeting indications (1-bit) (rising) from field devices Note that Process indications are either 'Requested' indications, 'Spontaneous' indications or 'Command acknowledgement' indications.

System-Internally Derived Messages

Those messages generated by configured system-software elements, such as Message combiners (binary logic), Meters (operating cycle counters), Warnings (e.g. violation of configured limits), and from special devices such as: Automatic Fault Localisation (AFL)

Process Management Management processes that: - Control operation of network components (e.g. select network component, open pop-up menu, issue command, issue Control Confirmation, etc), - Monitor Command Execution - Block other operations on a specific network component (e.g. while an active Command is executed) - Perform operational interlock (e.g. block disallowed operations) - Perform topological interlocks (e.g. warn operator of an impermissible network states)

Organisational Operations Internal processing operators in the control system (e.g. Command inhibit, Message inhibit, Notes defining control deviations, Single acknowledgement of the selected network component, Display of statuses of the positioned network component) Note that 'Markers' are associated with organisational operations and are displayed in the project diagrams via configurable icons.

Control Sequences A logical summary of controls and organisational operations for a unit which can be selected at any time. Control sequences can relate to several switching stations and can be organized in control sequence groups. Control sequences can be operator-initiated or automated (event or time controlled)

Event Scheduler Used to automatically schedule events, such as starting a control sequence, or exporting lists (e.g. daily archiving of historical data).






Remote Terminal Units Remote terminal units for controlling and monitoring the field process at switching stations. Note that the system permits: - RTU Data decoupling (no incoming process data will be processed) - RTU Device decoupling (communication to the RTU is disconnected)

Table A24 – VICOS RSC Software – Overview of Data Processing Functions

Other miscellaneous data processing functions, include:

Set Point Value Settings - Functionality to define set point values (e.g. limit values) to monitor / control an aspect of system behaviour based on a defined set point.

Metered-Value Processing - Preparation and display of metered process values (e.g. counters) in a format that suits the operator, including displaying values as numerical values in text boxes, bars or in curve windows. Note that ‘Meters’ are user-specified software devices to count (cyclic) events on devices in the system.

Measured-Value Processing - Preparation and display of measured process values (i.e. analogue values) in a format that suits the operator, including displaying numerical values in text boxes, bars or in curve windows. Measured value functionality is highly configurable.

Calculation functions - Mathematical manipulation of numerical values for display in a format to suit the operator.

Message Combiner functions -Logical manipulation & display of messages using binary operators (“NOT”, “AND”, “OR”)

6.6.3. Specialised Functions


Automatic Fault Location (AFL)

Specialised substation test equipment can be used to identify the specific location of overhead line short circuits on long rail lines to allow a rapid maintenance response to faults. Where such 'automatic fault location' test devices are installed at substations, the TPSS control system can be configured to automatically isolate the affected overhead line section, and (if appropriate field equipment is also installed) automatically switch around faults.

Connection to Rail Control Centre

The TP SCADA control system collects a large quantity of data that is useful to rail control centres (e.g. the energised state of each overhead line/track section), which data can be transferred to the control centre via standard interfaces.

Maintenance and Repair System

The TP SCADA control system can be configured to store equipment usage data, (e.g. operating cycles / duration, limit values and alarm messages), which can be transferred to asset maintenance systems via standardised interfaces.

Alarms via SMS The TP SCADA control system can be configured to automatically filter key alarms and forward these via mobile phone SMS to nominated personnel.

SNMP Communication Vicos RSC communicates with other local I/O devices via SNMPv1. This protocol is suitable for universal use, e.g. to connect to facilities not equipped with RTU such as ticket machines, escalators, elevators, information displays, etc.

Mimic Boards via Simatic S7 Mimic boards can be controlled via Vicos RSC using conventional Simatic S7 PLCs.





Export / Import of System Data

All data captured or generated by the Vicos RSC control system can be exported and integrated into Microsoft Excel documents. Conversely, Microsoft Excel data that is appropriately formatted in a specific data structure, can be imported into the Vicos RSC Project Editor.

Switching Preview Function The switching preview function enables the viewing of sub-statuses in the runtime system before the actual control operations are carried out. This means that switches can be switched to the corresponding position, and the resulting impact on the system can be modelled. The runtime system continues to operate in the background and is not affected by the preview function. On completion of the preview, the settings can be applied or discarded.

Local Operation A local operation function can be configured to enable a workstation, which is normally just a terminal, to become an independent master in specific operational circumstances.

Local Controller A Local Controller function ensures that, during work in a substation, the substation devices can only be operated (switched) by specific users. The function sets the control authorisations for individual devices. The status of the Local Controller can be switched over manually (by selecting the device) or via a process message.

Table A25 – VICOS RSC Software – Overview of Specialised Functions

6.7. Archiving Functions

The VICOS RSC EVA application installed on the Archive Servers provides various archiving and data analysis capabilities

Hrail Traction Power SCADA System Architecture and Description … · 2021. 2. 3. · Hrail...

Documents

Transcript of Hrail Traction Power SCADA System Architecture and Description … · 2021. 2. 3. · Hrail...