DESIGN PRACTICE NOTE

SIGNALLING CBI DATA SOFTWARE SUBMISSION

REQUIREMENTS
L1-NAM-INS-027 Version: 1 Effective from: 20th May 2014

Approval

Amendment Record

Approval Date Version Description

16/05/2014 1 Initial issue under MTM

Approving Manager: Chief Engineer Approval Date: 20/05/2014 Next Review Date: 20/05/2016
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 1 of 8
 DESIGN PRACTICE NOTE
SIGNALLING CBI DATA SOFTWARE SUBMISSION
REQUIREMENTS
L1-NAM-INS-027 Version: 1 Effective from: 20th May 2014

Table of Contents

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

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

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

4. Definitions and Responsibilities ................................................................................... 3

5. Background .................................................................................................................... 3

6. The Issue ........................................................................................................................ 4

7. MTM Requirements ........................................................................................................ 4

8. Related Documents........................................................................................................ 5

9. References and Legislation........................................................................................... 5

10. Appendices .................................................................................................................... 5

Appendix A: Types of Data Files for Westlock, SmartLock and SSI Interlocking ............................. 6
Appendix B: Types of Data Files for Westrace Interlocking ............................................................. 7
Appendix C: CBI Index Sheet ........................................................................................................... 8

Approving Manager: Chief Engineer Approval Date: 20/05/2014 Next Review Date: 20/05/2016
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 2 of 8
 DESIGN PRACTICE NOTE
SIGNALLING CBI DATA SOFTWARE SUBMISSION
REQUIREMENTS
L1-NAM-INS-027 Version: 1 Effective from: 20th May 2014

1. Purpose
The purpose of this practice note is to clarify the MTM requirements on submission of
Computer Based Interlocking (CBI) system data by design consultants, constructors and
contractors.

2. Scope
This document applies to the design and commissioning of new installations, renewals and
upgrades of Computer Based Interlocking system on MTM network by maintenance,
renewals and project works.

3. Abbreviations and Acronyms

AIS – As In Service
ARO – Accredited Rail Operator
CBI – Computer Based Interlocking
MTM – Metro Trains Melbourne
VRIOGS – Victorian Rail Industry Operators Group Standards

4. Definitions and Responsibilities

The following persons are to note and comply with the terms of this Design Practice Note:
Signal Designers
o To incorporate requirements into all new CBI installs, renewals or upgrades
Project Managers
o To ensure requirements are incorporated into project scope of works
Signal Maintenance
Signal Design Reviewers
Signal Design Approvers
Network Asset Managers

5. Background
The VRIOGS 012.3 Revision A stipulates in section 8.6 that “the constructor shall supply
all the hardware and software to permit the Infrastructure Manager’s representative to
undertake new signalling designs and alterations to CBI installations”. It states that the
Constructor shall provide complete documentation including manuals for Signalling Design
and Data Preparation. The same VRIOGS standard also states in section 12.8 that the
constructor shall be responsible for completing all licensing and royalty agreements for the
supply of all equipment, hardware, software and system which are provided as part of the
contract.

Approving Manager: Chief Engineer Approval Date: 20/05/2014 Next Review Date: 20/05/2016
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 3 of 8
 DESIGN PRACTICE NOTE
SIGNALLING CBI DATA SOFTWARE SUBMISSION
REQUIREMENTS
L1-NAM-INS-027 Version: 1 Effective from: 20th May 2014

In VRIOGS 012.1 Revision B, section 5.3, it has been highlighted that the “As in service”
alterations to circuit plans and application data as required to be completed after each level
of stagework, and final “As in service” plans shall be provided upon completion of
commissioning and after the test copies have been returned. It also states that the
geographic logic data shall be included in the design.

6. The Issue
There was no facility available in the DMS system to store such software, application data
and / or logic data. The constructors and CBI system installers provided the software,
application data and logic data for the particular installs as part of the design review.
However, they were not submitted in a consistent format. Neither was there a software or
data vault in the DMS, hence there was no requirement to ensure they were submitted in a
consistent format and what data files to be submitted. All software, application data and
logic data received were given to the stakeholder’s teams but were not kept in a secure
controlled vault with proper configuration control.

7. MTM Requirements
All the CBI data files in their native format are required for the data submission. They shall
be submitted together with *.pdf’s of all the source files that represent the CBI set-up and
the logic equations (e.g. Boolean logic, ladder logic, etc). Upon commissioning, all AIS CBI
data shall be stored in DMS. A CBI Index Sheet shall be created to capture and control all
CBI application data in a DMS compliant drawing in order to maintain and trace the data.
CBI index sheet shall also mention the name/revision of the data compiler for future record.

The CBI Index Sheet shall be created in the standard MicroStation VRIOGS Title Block.
CBI application data shall be stored in its relevant native format as a complete As-In
Service CBI application data package. There shall be one CBI Index Sheet per Master
Interlocking which contains all CBI data within that Interlocking.
For each CBI Index Sheet the Title Block information shall be:
a) Discipline : Signals
b) Discipline Code :G
c) Location Name : <Master Interlocking Name> (according to DMS location name in
Appendix A of the DMS standard)
d) Title 1 : CBI Index Sheet
The CBI Index Sheet shall provide a listing of all CBI data files along with compiler
name/revision for the location in a table format. The CBI Index Sheet table shall contain the
filename, description, title, revision number, file type and date for each set of CBI
application data as shown in the drawing template attached to this Design Practice Note,
Appendix C. The individual software or data file revision number has no relationship to the
Revision Number in the title block.
When submitting the CBI Index Sheet into DMS, it shall be submitted with:
Signed Interlocking Software Summary Record (e.g. WISR for Westlock, CISR for
SmartLock, CISR for SSI, GSIM Test Record for Westrace) or equivalent Validation
Record

Approving Manager: Chief Engineer Approval Date: 20/05/2014 Next Review Date: 20/05/2016
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 4 of 8
 DESIGN PRACTICE NOTE
SIGNALLING CBI DATA SOFTWARE SUBMISSION
REQUIREMENTS
L1-NAM-INS-027 Version: 1 Effective from: 20th May 2014

A complete AIS CBI application data package with all the CBI data files in their native
format (Note: The package can be in zip file.)
Readable/understandable *.pdf files format for all the source codes that represent the
CBI set-up and the logic equations (e.g. Boolean logic, ladder logic, etc)
Readable/understandable *.pdf files format of the difference list (DIFF LIST) for all the
source codes that represent the CBI set-up and the logic equations (e.g. Boolean
logic, ladder logic, etc) if the data has been amended from previous revision.
A DMS compliant drawing for each interlocking system architecture
(Note : The architecture drawing(s) of the CBI is/are to be listed on the CBI index
form. This drawing(s) entry is provided as a cross reference to a prepared DMS
compliant drawing which is entered into DMS as per the standard DMS compliant
drawing book-in process. The CBI index form should be updated to provide an area to
record the architecture drawing(s) title and DMS drawing number. Alternatively the
default will be to list this information in the "Description/Title/ID No." field on the CBI
index form.)
The CBI Index Sheet needs a field added to identify the organisation that is in control
of the CBI data
(Note: This would be the organisation who did the book-in for the current version of
the data).
The type of files to be included, but not limited to, for a Westlock, SmartLock or SSI
interlocking system is as highlighted in Appendix A.
The type of files to be included, but not limited to, for a Westrace interlocking system is as
highlighted in Appendix B.
Note : At this point of time, the ARO / DMS does not have capability to securely store the
master software. Hence, CBI provider can still maintain the control of master software files
in their server and indicate in “BLOCK LETTER” on the Index Sheet who is controlling /
maintaining the master software. Should the CBI provider be required to undertake
modifications to this data then they still have to go through the DMS Book Out / Book In
process. If any other contractor wants to access the master software, the master control
can be fully released to the second contractor through the DMS Book Out process.

8. Related Documents
VRIOGS 012.1 – Standard for Signalling Design and Documentation
VRIOGS 012.3 – Computer Based Interlocking

9. References and Legislation

Not Applicable.

10. Appendices
Appendix A: Types of Data Files for Westlock, SmartLock and SSI Interlocking
Appendix B: Types of Data Files for Westrace Interlocking
Appendix C: CBI Index Sheet

Approving Manager: Chief Engineer Approval Date: 20/05/2014 Next Review Date: 20/05/2016
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 5 of 8
 DESIGN PRACTICE NOTE
SIGNALLING CBI DATA SOFTWARE SUBMISSION
REQUIREMENTS
L1-NAM-INS-027 Version: 1 Effective from: 20th May 2014

Appendix A: Types of Data Files for Westlock, SmartLock and SSI Interlocking

Identity Files
o ACM.id = Axle Counter Identities
o BUT.id = Button Identities
o ELT.id = Elapsed Timer Identities
o FLG.id = Flag Identities (Latches / sub-routes / sub-overlaps)
o IND.id = Indication Identities
o PTS.id = Point Identities
o QST.id = Request Identities
o ROU.id = Route Identities
o SIG.id = Signal Identities
o TCS.id = Track Circuit Identities

TFM Database Listings

o IPT.tfm = TFM Input datasheet
o OPT.tfm = TFM Output datasheet

Data Files (Source Files)

o DIA.dat = Diagnostic Data Files
o SIM.dat = Simulator Data Files
o IPT.dat = Input file data
o OPT.dat = Output file data
o FOP.dat = Flag Operations file data
o MAP.dat = Map Search File data
o PFM.dat = Points Free to Move file data
o PRR = Panel Route Request file data
o Additional Simulation Files (Simulator Screens for Workstation)
o Signalman.pic1 = Signalman’s Screen View for simulation purposes
o Trackside.pic2 = Trackside Screen View for simulation purposes

Panel Data Files (Source Files)

o PBK.dat = Panel Button Indication File
o PTD.dat = Panel Track Display File
o PSD.dat = Panel Signal Display File
o PPD.dat = Panel Points Display File
o POD.dat = Panel Other Display File

Approving Manager: Chief Engineer Approval Date: 20/05/2014 Next Review Date: 20/05/2016
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 6 of 8
 DESIGN PRACTICE NOTE
SIGNALLING CBI DATA SOFTWARE SUBMISSION
REQUIREMENTS
L1-NAM-INS-027 Version: 1 Effective from: 20th May 2014

Appendix B: Types of Data Files for Westrace Interlocking

Westrace Mk II
o *.WT2 Installation file
o *.LOG Log file
o *.IFC interface file (required only when the Westrace has vital interface with other
Westraces, one *.IFC for each vital interface)
o *.ILG interface log file (required only when the Westrace has vital interface with other
Westraces, one *.ILG for each vital interface)
o *.IMG Processor A and B Image file (vital data)
o *_D.IMG Processor D image file (communications configuration)
o *.FED
o *.WIP

Westrace Mk I
o *.INS Installation file
o *.LOG Log file
o *.FED
o *.IFC interface file (required only when the Westrace has vital interface with other
Westraces or when the Westrace has non-vital interface with the S2,
one *.IFC for each vital interface)
o *.ILG interface log file (required only when the Westrace has vital interface with other
Westraces or when the Westrace has non-vital interface with the S2,
one *.ILG for each vital interface)
o *.IMG Image file – vital
o *.NCD Non vital installation file
o *.WIP
o *_NCDM.LOG Non vital Log file
o *_NCDM.IMG Non vital Image file
o *_NCDM.WIP

Approving Manager: Chief Engineer Approval Date: 20/05/2014 Next Review Date: 20/05/2016
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 7 of 8
 DESIGN PRACTICE NOTE
SIGNALLING CBI DATA SOFTWARE SUBMISSION REQUIREMENTS
L1-NAM-INS-027 Version: 1 Effective from: 20th May 2014

Appendix C: CBI Index Sheet

Approving Manager: Chief Engineer Approval Date: 20/05/2014 Next Review Date: 20/05/2016
PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 8 of 8