L1-CHE-INS-012 CBI To CIS (Pride) Telemetry Interface

DESIGN PRACTICE NOTE
CBI TO CIS (PRIDE) TELEMETRY INTERFACE

L1-CHE-INS-012 Version: 1 Effective from: 18th November 2015
Approval
Amendment Record
Approval Date Version Description

18/11/2015 1 Initial Issue
Approving Manager: Chief Engineer Approval Date: 18/11/2015 Next Review Date: 18/11/2017
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 1 of 11
Table of Contents
1. Purpose........................................................................................................................ 3
2. Scope ........................................................................................................................... 3
3. Abbreviations and Acronyms ..................................................................................... 3
4. Definitions.................................................................................................................... 4
5. Background / History .................................................................................................. 4
6. General Architecture Description............................................................................... 4
7. Requirements .............................................................................................................. 5
7.1 Communications Protocol ............................................................................................. 5

7.2 Modbus Bitmap Design Guideline ................................................................................. 6
7.3 Availability ..................................................................................................................... 9
7.4 Location and Arrangement of Equipment ..................................................................... 9
7.5 Power Supply ................................................................................................................ 9
7.6 Network Security ........................................................................................................... 9
7.7 Network Design ............................................................................................................. 9
7.8 IP Addressing and Port Allocations ............................................................................. 10
7.9 Health Monitoring ........................................................................................................ 10
7.10 Documentation ............................................................................................................ 10
8. References and Legislation ...................................................................................... 10
9. Appendix A – TCMS Indicated Regions ................................................................... 11
1. Purpose
The purpose of this document is to present Metro’s requirements for the provision of an
‘OCS Telemetry Interface’ used to provide real time (state of the railway) signalling
indication data from Computer Based Interlocking (CBI) assets.
The nature, arrangement and modes of operation of the OCS Telemetry Interface are
described including high level system interconnectivity, interface availability, redundancy,
monitoring capability, maintainability, network security and documentation requirements.
This document is not intended to describe the CBI operation or signalling design but rather
to detail the interface requirements to the signalling system from an OCS perspective.
2. Scope
This Design Practice Note applies to all projects providing new or upgrading existing CBI
signalling instances. This interface is only applicable to non-TCMS indicated regions and
does not include legacy telemetry systems such as the railmaster network. Refer to
Appendix A for TCMS indicated regions.
3. Abbreviations and Acronyms

ACL Access Control List
ARO Accredited Rail Operator
CBI Computer Based Interlocking
CER Communications Equipment Room
CIS Customer Information System (formerly known as PRIDE)
DPN Design Practice Note
FEP Front End Processor
MTM Metro Trains Melbourne
OCS Operational Control Systems
PRIDE Passenger Real-time Information Dissemination Equipment now referred to
as ‘CIS’
SER Signalling Equipment Room
TCMS Train Control & Monitoring System
TCS Train Control System
TDS Train Describer System (JZA 715)
VRIOGS Victorian Rail Industry Operators Group Standards
4. Definitions
For the purpose of this DPN the following terms are defined as followed:
CBI-CIS Telemetry Interface – the interface point defining the physical demarcation point
(active network equipment) between signalling and OCS networks. The primary function of
the active network equipment is to restrict access to each respective network.
5. Background / History
This DPN was developed to standardise the architecture of CBI-CIS Telemetry Interfaces
given the different CBI installations provided by signalling contractors. The need arose to
standardise the interface due to a number of existing interfaces being identified as
exhibiting unacceptable reliability, availability and providing inadequate monitoring
capability. Much of the equipment is outdated with obsolescence issues and does not meet
MTM’s growing need to achieve higher availability and maintainability targets.
The communication protocol utilised to date between respective existing CBI-CIS Telemetry
Interfaces is loosely titled the “PRIDE protocol” and is not supported by all present day
signalling contractors. Further improving the architecture and bringing it up to modern day
standards, the communication protocol will move towards Modbus TCP/IP.
6. General Architecture Description

The general CBI-CIS Telemetry Interface arrangement can be seen in Figure 1 below. The
signalling system shall provide dual network connections either directly to the respective
CBI interface or via routers connected to the local signalling network.
Fibre shall be used to connect the two respective systems to provide optical and electrical
isolation in the event of a lighting strike or other fault condition.
SIGNALLING INSTALLATION OCS INSTALLATION

( SER ) ( CER )
FIBRE OCS FIREWALL

SWITCH #1
TO RESPECTIVE #1
INTERLOCKING VIA OCS Network
CBIs
SWITCH #2 FIBRE OCS FIREWALL
#2
DEMARCATION
POINT
Figure 1– General CBI-CIS Telemetry Interface
7. Requirements
7.1 Communications Protocol

The CBI-CIS Telemetry Interface shall be designed to utilise Modbus TCP/IP to align with
industry standards. Where a signalling contractor cannot natively support Modbus TCP/IP
directly from a CBI interface or signalling router, a waiver and proposed architecture is to be
submitted to MTM for approval.
For the purposes of the MODBUS interface the Signalling System shall be the slave
(TCP/IP server) and the OCS system shall be the master (TCP/IP client).
Each instance of the signalling interface system shall be duplicated and therefore available
on two separate IP addresses associated with two separate systems.
Each signalling interlocking presented on each interface may have an individual MODBUS
IP interface port. The default MODBUS IP port is 502, if required other port numbers shall
be selected by the contractor to provide interface points for each interlocking.
If the contractors interface will not be providing individual port numbers for each
interlocking, then it must be possible to open simultaneous TCP/IP connections (initiated on
the same port number) to access the interlocking data.
Interlocking A on port 502 Interface 1 (eg 192.168.101.10)

Interlocking A Interlocking B on port 502
Interlocking C on port 502
Interlocking B
Interlocking C
Interlocking A on port 502
Interlocking B on port 502
Interlocking C on port 502 Interface 2 (eg 192.168.101.20)
Figure 2: Example CBI/OCS Interface Logical Arrangement
This interface will provide indications only. There is no capability to apply any controls to
the signalling system. The state of signalling objects shall be provided through Modbus
function code 0x02 – Discrete Inputs or function code 0x04 Read Input Registers.
The state of each interlocking and interface shall be made available as part of the list of
indications. This will allow the receiving system to interpret the data concerning each
interlocking as a single unit. All indications for a single interlocking will be read as a single
Modbus poll.
The response time shall not exceed 1.0 second 95% of the time with no instance to exceed
1.5 seconds. Sub-second response times are desirable. The OCS system will poll the
interface as soon as the previous poll has completed, but will not exceed an inter poll
period of 0.5 seconds.
7.2 Modbus Bitmap Design Guideline

The following tables provide a description of the recommended signalling indication and
format of the Modbus frame to be provided to CIS based on a sub-set of indications
currently used by TCMS. These indications have been consolidated to align with other OCS
systems most notably Picview.
Per Interlocking Frame layout
Starting Number Number of Content

Register of 16-bit Indications
Address Registers
0 16 128 Track Indications (8 per register)
16 16 32 Point/Gate/Derailer Indications (2 per register)
32 32 64 Signal Indications (2 per register)
64 16 256 Route Indications (16 per register)
80 10 Miscellaneous Indications (16 per register)
90 4 System Health Indications (16 per register)
94 Total registers per interlocking
Track Indications
2 bits per track indication, 16 track indications per register.

Where bit is not present or cannot be derived, mark as “spare”.
Bit Mask Bit State Meaning for OCS
0 Track is not clear. Usually means a train is present,
x1 but can also indicate track circuit/system failure.
1 Track is proven clear.
0 Track is not blocked / sleeved
1x
1 Track is blocked / sleeved
Point/Derailers/Gates Indications
8 bits per point indication, 2 point indications per register.

xxxxxxx1 1 Point lie is corresponded normal. (controlled and detected)
xxxxxx1x 1 Point lie is corresponded reverse. (controlled and detected)
0 Point is free to move.
xxxxx1xx
1 Point is locked.
0 Point is in hand operation mode.
xxxx1xxx
1 Point is in motor operation mode
0 Point is not blocked / sleeved.
xxx1xxxx
1 Point is blocked / sleeved
xx1xxxxx 1 Lever in Normal.
x1xxxxxx 1 Lever in Centre.
1xxxxxxx 1 Lever in Reverse.
Signal Indications
8 bits per signal indication, 2 signal indications per register.

Where bit is not present or cannot be calculated mark as “spare”.
xxxxxxx1 1 Stop Aspect Inc. train stop / TPWS proving.
xxxxxx1x 1 Low speed aspect.
xxxxx1xx 1 Proceed Aspect. Also known as “Clear’.
xxxx1xxx 1 Approach locking timer active. Also known as “Time
Release”.
xxx1xxxx 1 Signal in fleeting mode.
xx1xxxxx 1 Approach clearing.
Common route set.
x1xxxxxx 1
True if any route is set from this signal.
0 Signal is not blocked / sleeved
1xxxxxxx
1 Signal is blocked / sleeved.
Route Indications
1 bit per route indication, 16 route indication per register.

Where bit is not present or cannot be calculated mark as “spare”.
Route is set. The interlocking has accepted a
request to set the route.
1 This type of indication may not be available from all
1 interlocking systems (see route set in Signal
indications).
0 Route is not set.
Miscellaneous Indications
1 bit per miscellaneous indication, 16 route indication per register.

Below is a list of miscellaneous indications as a guide, miscellaneous indications shall be
developed as part of a site specific instance and documented in the ICD.
- Power Alarms
- ELD Alarms
- UPS Alarms
- Stopper / Express Indications
- Ground Frame / Release indications
- Approach Tracks (dark territory boundary)
- Level Crossings – Booms Up / Booms Down / Test Switch / Booms Down Too Long
- Ped Gates Alarms
- Tilt Alarms
- Signal Lamp Proving Alarms
System Health Indications
2 bits per status indication, 8 status indication per register.

Heartbeat for signalling system front end. Bit pulses
at frequency less than polling rate.
x1 0/1
For an expected 1 second poll rate this bit will cycle at
0.5 Hz.
Interlocking not updating. Indicated that the signalling
0 system front end is not connected to a live
1x interlocking.
Interlocking is running. Indicates that the signalling
1
system front end is connected to a live interlocking.
7.3 Availability
The CBI-CIS Telemetry Interface shall be designed and implemented to achieve the same
availability as the type approved FEP used in the proposed system architecture.
7.4 Location and Arrangement of Equipment

The signalling network shall allow for two (2) OM3 MMOF (typically) network connections
between signalling and OCS networks to minimise single points of failure. Where fibre is
not supported on the signalling side, a media converter shall be used upon approval from
MTM. The installation shall adhere to VRIOGS 013.3 Generic ICT Communications
Pathways Specification & MSST060000-01 Communications Links for Signalling
Where the Signalling and OCS installations are located beyond the capabilities of multi-
mode fibre, single-mode fibre shall be utilised.
Signal Equipment Room (SER)
1. Dual network connections
2. Fibre patch panel (1-2RU) in same equipment rack as active network equipment
3. Fibre trunking and cable management to provide necessary fibre tail support
4. Media converter if required
Communications Equipment Room (CER)
1. Fibre patch panel (1-2RU) in same equipment rack as active network equipment
2. Fibre trunking and cable management to provide necessary fibre tail support
3. Security Network Firewalls
Where OCS communication equipment and signalling equipment share the same signalling
power supply in the signal equipment room, dual copper UTP connections may be used in
lieu of fibre between the signalling equipment and the OCS equipment. Copper patch
panels and structured copper cabling would therefore be used.
7.5 Power Supply

All equipment that forms part of the CBI-CIS Telemetry Interface shall adhere to VRIOGS
013.1 standards when installed in a CER. Otherwise, when installed in an SER the
installation shall adhere to VRIOGS 012.1 standards.
7.6 Network Security

The signalling and security networks shall be partitioned via the deployment of a pair of
firewalls. Routing rules and ACL’s will be configured to prevent unauthorised network
activity. Authorized traffic will be explicitly allowed with other traffic being blocked by
default.
The signalling contractor shall ensure that the performance of the signalling system cannot
be degraded in any way by the operation of the OCS system. This includes OCS network
outages, excessive polling and/or unexpected traffic.
7.7 Network Design

A formal network design suitable for peer review shall be prepared and submitted by the
signalling contractor to MTM to ensure compatibility between signalling and OCS networks.
7.8 IP Addressing and Port Allocations

The signalling contractor and MTM shall co-ordinate to determine an IP addressing scheme
to establish networking connectivity.
The signalling and security networks shall occupy discrete subnets to prevent routing
conflicts.
7.9 Health Monitoring

The signalling system shall make available health reporting bits to indicate significant
events that will result in the loss of train indications to CIS, which include the loss of
communications and fault conditions.
7.10 Documentation
The Signalling Contractor shall develop and submit to MTM for approval a CBI-CIS
Telemetry Interface ICD that will detail all relevant Modbus communications and system
parameters. MTM will provide feedback and work with the Signalling Contractor to achieve
a consistent interface setup across the Melbourne Metropolitan Rail Network.
Signalling Arrangement Plans (SAPs) and system bit lists shall also be provided to MTM at
the beginning of the CBI-CIS Telemetry Interface development phase.
8. References and Legislation

No. Document Title Document No. Version
1. Signalling CBI VRIOGS 012.3 A
2. Communications Links For Signalling MSST060000-01 1
Design Practice Note – Signal Equipment L1-CHE-INS-006 1
3. Rooms Electrical Supply and Earthing System
Design
4. Modbus Application Protocol Specification, V1.1b3
Modbus Messaging on TCP/IP Implementation V1.0b
5. Guide
VRIOGS – 013.1 Communications Equipment VRIOGS 013.1 A
6. Room Brief
VRIOGS – 013.3 Generic ICT Communications VRIOGS 013.3 A
7. Pathways Specification
VRIOGS - 012.1 Standard for Signalling VRIOGS 012.1 B
8. Design and Documentation
9. Appendix A – TCMS Indicated Regions

L1-CHE-INS-012 CBI To CIS (Pride) Telemetry Interface

Uploaded by

Copyright:

Available Formats

L1-CHE-INS-012 CBI To CIS (Pride) Telemetry Interface

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

L1-CHE-INS-012 CBI To CIS (Pride) Telemetry Interface

Uploaded by

Copyright:

Available Formats

DESIGN PRACTICE NOTE

CBI TO CIS (PRIDE) TELEMETRY INTERFACE

Approval Date Version Description

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

5. Background / History .................................................................................................. 4

6. General Architecture Description............................................................................... 4

7.1 Communications Protocol ............................................................................................. 5

8. References and Legislation ...................................................................................... 10

9. Appendix A – TCMS Indicated Regions ................................................................... 11

3. Abbreviations and Acronyms

6. General Architecture Description

SIGNALLING INSTALLATION OCS INSTALLATION

FIBRE OCS FIREWALL

Figure 1– General CBI-CIS Telemetry Interface

7.1 Communications Protocol

Interlocking A on port 502 Interface 1 (eg 192.168.101.10)

Figure 2: Example CBI/OCS Interface Logical Arrangement

7.2 Modbus Bitmap Design Guideline

Starting Number Number of Content

2 bits per track indication, 16 track indications per register.

8 bits per point indication, 2 point indications per register.

8 bits per signal indication, 2 signal indications per register.

1 bit per route indication, 16 route indication per register.

1 bit per miscellaneous indication, 16 route indication per register.

2 bits per status indication, 8 status indication per register.

7.4 Location and Arrangement of Equipment

7.5 Power Supply

7.6 Network Security

7.7 Network Design

7.8 IP Addressing and Port Allocations

7.9 Health Monitoring

8. References and Legislation

9. Appendix A – TCMS Indicated Regions

You might also like