Engineering Specification

(1)

Engineering Specification

SPM 0212

COMMUNICATIONS & CONDITION

MONITORING INFRASTRUCTURE

Version 1.1

Issued February 2012

Owner: Engineering Communications Manager, Communications & Control Systems Approved

by:

Navin Hegde

A / Communications Delivery Manager

Communications & Control Systems Authorised by: Jeff Byron Chief Engineer Telecommunications Disclaimer

This document was prepared for use on the RailCorp Network only.

RailCorp makes no warranties, express or implied, that compliance with the contents of this document shall be sufficient to ensure safe systems or work or operation. It is the document user’s sole responsibility to ensure that the copy of the document it is viewing is the current version of the document as in use by RailCorp.

RailCorp accepts no liability whatsoever in relation to the use of this document by any party, and RailCorp excludes any liability which arises in any manner by the use of this document.

Copyright

The information in this document is protected by Copyright and no part of this document may be reproduced, altered, stored or transmitted by any person without the prior consent of RailCorp.

(2)

Document control

Version Date Reviewers Summary of change

1.0 January 2012 Chris Go

Wireless Systems Manager Pat Kerrigan

Telecommunications Network Manager Llewellyn Mead

Data Networks Manager Thuan Ngo

Condition Monitoring Systems Manager

First issue

1.1 February 2012 Chris Go

Wireless Systems Manager Thuan Ngo

Condition Monitoring Systems Manager

Correction to GRN and Police Radio coverage requirement.

Correction to earthing for Condition Monitoring systems

Summary of changes from previous version

Summary of change Section

Correction to GRN and Police Radio coverage requirement. 10 Correction to earthing for Condition Monitoring systems 11.5

(3)

1 Introduction

1.1 Background

RailCorp’s Communications and Control Systems (C&CS) division owns and operates a geographically vast telecommunications and condition monitoring systems infrastructure network throughout the Sydney metropolitan area. C&CS’s telecommunications and condition monitoring infrastructure consists of multiple communications technologies including train radio systems, telephony & data networks, transmission systems, optical fibre & cable network systems, and rolling stock & infrastructure conditioning monitoring systems.

The C&CS telecommunications infrastructure supports a wide range of services critical to railway operations such as train control and signalling, emergency and driver communication, train location systems etc. C&CS infrastructure also supports a number of “on station” services such as CCTV, SPI, ticketing, station LAN.

The C&CS condition monitoring systems infrastructure provides vital alarm and trending data that help maintenance crews take corrective and preventative action for rolling stock asset and in future, infrastructure faults. Equipment used includes HBDs and AOA systems.

RailCorp is continuing to expand the railway network in Sydney and areas of New South Wales. Expansion to the network also includes the addition of new tracks or turn backs. New telecommunications and condition monitoring infrastructure required for this expansion has to interface with the existing network and needs to be compliant with C&CS technical and system requirements.

1.2 Purpose

This document is intended to detail the technical and system requirements for telecommunications and condition monitoring systems infrastructure if deployed for expansion of the rail network.

This document is not intended to provide all the necessary information required for construction or tendering purposes and thus shall only be used as a general design requirement guideline.

Applicability of the various specifications/requirements set out in this document could vary depending on the project requirements, complexity and/or location. The requirements shall therefore be assessed on a case by case basis. SME’s for respective disciplines, as listed in 0, should be consulted if in doubt.

This is a living document and is organised into infrastructure categories where the relevant RailCorp design authority responsible for each category maintains and updates that section of the document.

Sections are divided into: • General

• Facilities and DC Power • Cables

• Transmission Networks

• Emergency and Operations PABX Telephones • Data Networks

(7)

• Wireless Infrastructure • Condition Monitoring Systems

All new telecommunications infrastructure in rail corridors is to be compliant with all Australian Standards and RailCorp Standards, where this document provides specification for design it is to be used in addition to these standards.

If there is a conflict between this document and the Australian Standards or RailCorp Standards referenced in this document, then the Australian Standards and RailCorp Standards shall take precedence and the Communications Engineering Manager of C&CS Division shall be notified.

1.3 Scope and Application

The scope of this document is limited to providing C&CS’s requirements of telecommunications and condition monitoring systems infrastructure for new rail corridors and major expansions of existing rail corridors such as line duplication or quadruplication. The following is in scope:

• Telecommunications Facilities and DC Power

Including equipment rooms, equipment cabinets, and DC power supplies • Cables

Includes backbone cabling between telecommunications facilities, signalling bungalows and other telecommunications infrastructure

• Transmission Networks

Voice and Data transmission equipment and interfaces • Emergency and Operations PABX telephones

Telephone systems that are safety or operations critical and under C&CS’s Operational and Maintenance responsibility

• Data Networks

Data switched network equipment supporting networks under C&CS’s Operational and Maintenance responsibility

• Network Control Communications Systems

Including Voice Communication Systems, and Voice Recording systems for single interface communication and recording of operations telephony and radio

• Wireless infrastructure

Including train radio, yard radio, station radio, the Government Radio Network, the Police Radio Network and Public Mobile Networks

• Condition monitoring systems

Includes Bearing and Brake Temperature Detectors, Bearing Acoustic Monitors, Dragging Equipment Detectors, Angle of Attack Detectors, Wheel Impact Load Detector, In-Motion Weighbridge, Ground Borne Noise Detectors, Automatic Equipment Identification, Wayside Information Management Systems

(8)

The following is out of scope: • End user services

These are services that are supported by telecommunications and condition monitoring systems infrastructure however fall outside the scope of this document, such as Ticketing, CCTV and Passenger Information. These services may dictate requirements for telecommunications and condition monitoring systems infrastructure, however where and how they are implemented is as per the new corridor or expansion design in consultation with their stakeholders.

• IT infrastructure for general administration

This is infrastructure that does not directly support railway operations such as IT servers, desktop computers, printers and their associated networks, cables and power. These services may dictate requirements for telecommunications infrastructure; however where and how they are deployed is as per the new corridor or expansion design in consultation with their stakeholders.

RailCorp’s Information and Communication Technology division (ICT) has responsibility for operations and maintenance of administrations infrastructure. • Telephony infrastructure for general administrative communications

This includes telephones located in offices and general station facilities on desktops, which does not directly support railway operations. These services may dictate requirements for telecommunications infrastructure; however where and how they are deployed is as per the new corridor or expansion design in consultation with their stakeholders.

RailCorp’s Information and Communication Technology division (ICT) has responsibility for operations and maintenance of administrations telephony.

• Station “services” equipment rooms and on station “cable works”:

This document does not cover the technical requirements for station services equipment rooms or related cable works. These services may dictate requirements for telecommunications and condition monitoring systems infrastructure; however where and how they are deployed is as per the new corridor or expansion design in consultation with their stakeholders.

2 Definitions and abbreviations

2.1 Definitions

RailCorp’s Communications Engineering Communications Engineering in the C&CS

Division of RailCorp

Relevant Design Authority The SME Team Manager for the respective discipline, as

listed in 0

New Rail Corridors New rail corridors and major expansions of existing rail corridors

such as line duplication or quadruplication.

DTRS Digital Train Radio System. The train radio system implemented within the

RailCorp electrified area.

(9)

OCDN The C&CS IP MPLS Backbone network

C&CS ATM The C&CS ATM Backbone network being replaced by the OCDN

Administration Telephones Desktop telephony which does not directly support railway

operations. This includes telephones located in offices and general station facilities on desktops.

Administration infrastructure Infrastructure that does not directly support railway

operations such as IT servers, desktop computers, printers and their associated networks, cables and power.

Station Services Equipment Room Services rooms house end user services

infrastructure and are separate from telecommunications rooms

On Station Cable Works Cable works at stations for end user services and services

equipment rooms

2.2 Abbreviations

AC Alternating current AOA Angle Of Attack AS Australian Standards

ATM Asynchronous Transfer Mode

C&CS Communications and Control Systems CCTV Closed Circuit TV

DC Direct Current

DTRS Digital Train Radio System EIRP Effective Isotropic Radiated Power

HBD Hot Box Detector, also BBT (Bearing and Brake Temperature detector) IEEE Institute of Electrical and Electronic Engineers

IP Internet Protocol

IP Ingress Protection Rating IT Information Technology GRN Government Radio Network LAN Local Area Network

MDF Main Distribution Frame

MUX Multiplexer and De-Multiplex unit OCDN Operations Critical Data Network PABX Private Automatic Branch Exchange SDH Synchronous Digital Hierarchy

(10)

SME Subject Matter Expert SPI Station Passenger Information TDM Time Division Multiplexing WB Without Brake-Van Radio System WDM Wave Division Multiplexing

X-Ring An all ring, all talk, telephone arrangement

3 General

requirements

3.1 Design

process

Telecommunications and condition monitoring systems Infrastructure design shall follow the established design process of RailCorp. Generally for large projects such as expansions of the rail network or for new rail corridors, a design management plan is required to demonstrate how the design process being followed meets the requirements of RailCorp.

At a minimum, the design process will deliver the following:

3.1.1 Requirements

Specification

The requirements specification brings together all the design requirements and inputs sufficient for the design to proceed. The customer requirements are fully qualified and may involve the production of design specifications, such as detailed user requirements specifications, functional specification, performance specifications, and business requirements specifications. The requirements specification requires agreement or sign-off from the customer prior to proceeding further in the design.

3.1.2 Concept

Design

The concept design is intended to confirm feasibility by establishing a design solution, validating and verifying it to meet the overall objectives of the customer. This then forms the basis for a detailed design. Once again, depending on the complexity of the project, this may not be required for minor projects, but is mandatory for major projects.

For new or novel design solutions, the concept design phase is also the stage where a “prototype” could be developed and the “proof of concept” established through a series of tests and trials.

In some cases, a customer may require the design to just progress up to the concept stage. Example: For establishing feasibility or project budgeting purposes and/or to establish a business case.

The concept design is undertaken after the requirements have been developed and analysed.

The concept design may also be undertaken in the form of a document, a drawing or even a series of sketches. The following outputs are typical deliverables at the end of concept design. However, for more specialised projects, additional documentation may be required.

(11)

• Preliminary loss budgets

• Preliminary RAM (Reliability, Availability and Maintainability) analysis • Spare port and cable allocation checks

• Material and equipment availability • Software identification

• Typical Environmental limits • Typical floor plan

• Changes to power and air-conditioning loads • Concept timing diagrams

• Typical radio coverage

• Feasibility and acceptance of a new design solution. • Indentify any changes to maintenance practises required. • Prototype development report or a proof of concept report.

The concept design may also be used to determine if there is a requirement to engage other design workgroups and to provide input for the design planning such as scheduling, costs, risks and issues.

3.1.3 Detail

Design

The following outputs are typical deliverables at the end of detailed design: • Details of design for CCR purposes

• Final system level and network schematics • Detailed equipment lists and final bill of materials. • Plant & equipment to be de-commissioned (if applicable) • Rack layout and distributor diagrams

• Final port and cable allocations • Approved floor plan

• Final loss budgets

• Software and accompanying documentation

• Software development and configuration management procedures • Availability calculations/RAM

• IP addresses • Message formats • Environmental limits • Floor loads

• Heat dissipation and air-conditioning loads • Timing diagrams

• Test strategy, test and inspection plans • RATM (update)

• Hazards & risk analysis (update) • FMECA

Additionally, the following documentation shall be included as part of the detailed design documentation if appropriate:

• A Technical Maintenance Plan that includes corrective and preventative maintenance routines.

• A requirement specification for appropriate maintenance level training.

• Identification of performance criteria for maintenance contracts to be put in place, if applicable.

(12)

3.1.4 Test Strategy and Plans

The test strategy details the high level objectives to any testing required in the design, the scope of the testing and key risks, assumptions and constraints in testing. It also details at a high level, the testing methodology, types of testing to be conducted and test deliverables. The types of testing required could vary on the complexity of the design and could include FAT, SAT, Field Trials, Pilot Trials etc.

Test plans typically contain the following information: • Each test cases’ objectives

• Entry and exit criteria • Resources required • Test environment • Prep activities

• Components to be tested • Functions and features • Test cycles

• Test cases or scenarios • Acceptance criteria • Tolerances

3.1.5 RATM

All requirements in the specification(s) must be traceable to one or more design outputs via a Requirements Allocation and Traceability Matrix (RATM). The RATM is a matrix that is used to tie the design output to the original requirements. If there is a change in the design, the RATM must be revised to ensure that requirements are still met. Should a requirement not be met, there must also be an approved change in the requirements specification which will also be reflected in the concept design, risks, issues, costs and scheduling etc.

3.1.6 As Built Documentation

At the completion of the infrastructure implementation the ‘as-built documentation’ should be prepared and signed off. The final design involves the as-built documentation which becomes the documented configuration of the system and which must only be changed in the future by configuration control procedures.

3.2 Coordination

of

design

Telecommunications and condition monitoring systems infrastructure design shall be developed in consultation with and reviewed by the relevant design approval authorities within RailCorp, namely the subject matter experts with the delegated design authority within RailCorp’s Communications Engineering and the Chief Engineers office.

Where telecommunications and condition monitoring systems infrastructure requires design is to be completed by RailCorp’s Communications Engineering, it will follow the existing RailCorp design process as per document TMM P025 (version 3.0).

Generally large design and implementation projects such as expansions of existing rail or new rail corridors will require an Interface Management plan to show how the interface between the party responsible for implementation, RailCorp and Transport NSW will be managed for the coordination of design.

The external party responsible for implementation will also need to engage RailCorp’s Communications Engineering for undertaking design and implementation of interface

(13)

3.3 Acceptance testing and commissioning

Telecommunications and condition monitoring systems infrastructure shall be tested and commissioned as per existing specific infrastructure standards, specifications and procedure. Where an existing specific process does not exist, acceptance testing and commissioning will generally follow RailCorp Project Management Methodology (RPMM) and be developed in consultation with and reviewed by the relevant design authorities within RailCorp. Generally large projects such as expansions of existing or new rail corridors requires a Testing and Commissioning plan to show how the testing and commissioning requirements of RailCorp and Transport NSW will be met.

3.4 Other

obligations

Implementation shall follow established project management process of RailCorp (RPMM). Generally large projects such as expansions of existing, and new, rail corridors require the following plans to demonstrate how the requirements of RailCorp are being met:

• Installation Management Plan • OH&S Management Plan • Quality Management Plan • RAM Management Plan • Risk Management Plan • Safety Management Plan

• Through Life Support Management Plan

4 Facilities and DC Power

4.1 Telecommunications equipment rooms

4.2 Standards, Specifications and Drawings

Document

type

Document Title Document

Number

Standard Telecommunications Equipment Rooms Standard

ESM 107

Standard Communications Earthing and Surge Suppression Standard

ESM 109

Drawing Typical AC Power Supply Arrangements for Telecommunications Equipment Rooms

MET SC 0476

4.2.1 General

a) Telecommunications equipment rooms shall be provided in compliance with the standard ESM 107. All telecommunications infrastructure equipment shall be accommodated in dedicated telecommunications equipment rooms which shall have a separate access. This room need not be on the platform or within the structure of other station buildings, but shall be as closely as practicable associated with the station.

b) For interface equipment and/or new equipment, if space and power within an existing telecommunications room is available, then a design proposal shall be

(14)

provided detailing the requirements and the solution for integration. The design proposal shall include any upgrades that may be required to existing infrastructure including power supply etc to accommodate the additional infrastructure. In such cases, the final allocation and approval of the floor space and/or rack space will be by the design approval authority within RailCorp’s Communications Engineering.

c) Telecommunications equipment belonging to third party service providers such as carriers, GRN service providers, police radio equipment etc shall be accommodated in a separate communications room.

d) Other communications equipment associated with station services such as the Public Address System, Help Points, station LAN, CCTV equipment, SPI, ticketing etc will be housed in a separate dedicated “station” services equipment room. Every station will require a “station” services equipment room and this room shall have the necessary optical fibre and copper cable interconnection to the telecommunications equipment room to facilitate interconnection to the backbone network.

4.2.2 Site specific design documentation

Site specific design documentation shall be prepared for review and approval by the design approval authority within RailCorp’s Communications Engineering. The site specific design documentation shall specifically address the requirements of the standard ESM 107.

The site specific design documentation shall also include (but not limited to):

a) Room dimensions. The room size will be assessed on a site by site basis as it may vary depending on the geographic location and strategic position within the RailCorp telecommunications network.

b) AC Power supply and distribution arrangements. c) Specific surge and lighting protection.

d) Proposal for copper and optical fibre cables termination. e) General requirements for fire protection system.

f) Cable management details including cable entry points and cable tray layout. g) Air conditioning and cooling requirements.

(15)

Figure 1 - Example for Small Telecommunications Equipment Room Equipment Layout

4.3 Equipment

cabinets

4.3.1 Standards,

Specifications and Drawings

Document

type

Number

ESM 107

Standard Communications Earthing and Surge Suppression Standard

ESM 109

4.3.2 Requirements

Provide new equipment cabinet/rack to accommodate communications equipment within the telecommunications equipment rooms.

4.3.2.1 General

All new equipment cabinets to house telecommunications infrastructure shall be of “approved” makes, which are generally included in existing RailCorp supply agreements.

4.3.2.2 Type approved equipment

Where an existing supply agreement and or specification are not in place, the equipment cabinets called for in the design shall be subject to RailCorp’s type approval process.

(16)

4.3.2.3 Components

Generally equipment cabinets to house telecommunications infrastructure shall have: • 19inch mounting rails.

• Perforated front metal doors and flush mount handle. • 3 point locking system.

• Cable management system

• The option of integrated AC Power distribution.

4.3.2.4 Cabinet width

The standard cabinet width is 600mm.

800 mm wide cabinets may be required where a large amount of cabling involved makes it necessary to install cable trunking at the sides of the cabinet.

900 mm wide cabinet may be required for high density fibre enclosures.

4.3.2.5 Cabinet depth

The standard cabinet depth is 600 mm.

300 to 400 mm depth may be used for wall mount or back to back installations, for example DC Power Supplies, Transmission equipment, PABX equipment etc.

800 mm depth may be used for miscellaneous data or radio equipment that is generally not available in shallower depth.

Deeper than 800 mm depth shall only be used where there are no available suppliers of equivalent equipment that would fit within 800 mm cabinets.

4.3.2.6 Cabinet height

The standard nominal rack height shall be within 2.1 to 2.2 metres.

Where less than a full height rack is required to accommodate particular systems equipment, a full height rack shall still be provided to allow for future expansion/additions or accommodation of equipment of other systems.

4.3.2.7 Cabinet design considerations

The design for the equipment cabinet shall consider: The particular site requirements and location.

Telecommunications room equipment layout and clearance requirement as stated in RailCorp standard ESM107.

The requirements for the communications equipment that will be housed in the rack. Earthing arrangements in accordance with RailCorp standard ESM 109.

4.3.2.8 Environmental considerations

Equipment cabinets housing telecommunications infrastructure must be designed and located in to protect against detrimental effects caused by the environment. For example outdoor equipment cabinets close to the railway may be subject to hazards such as

(17)

vandalism, theft, dust contamination, flooding, earth potential rise, high temperatures and train or vehicle strike.

4.4 DC Power supplies

4.4.1 Standards,

Specifications and Drawings

Document

type

Number

ESM 107

Specification Battery Backed -48 VDC Power Supply Systems Specification

SPM 151

4.4.2 Requirements

4.4.2.1

General

-48 VDC Power supply system shall be provided within RailCorp telecommunications equipment rooms in accordance with RailCorp specification for battery backed -48 VDC power supply systems specification SPM 151 and existing supply agreements.

4.4.2.2

Type approved equipment

Where an existing supply agreement and/or specification is not in place, the power supplies offered in the design shall be reviewed/approved by the respective design approval authority within RailCorp’s Communications Engineering or subject to RailCorp’s type approval process.

4.4.2.3

Components

The new -48 VDC Power supply system shall be comprised of a combination of some or all of the following elements:

• Racking • Rectifiers • Batteries • DC/DC Converters • DC distribution module(s) • Inverters

• Remote management by way of SNMP

4.4.2.4 Performance

A minimum battery backup time of 15 hours shall be provided (assuming battery degradation will reduce backup to 12 hours after 5 years age).

Redundancy and availability of the power supply system shall comply with SPM 151 including N+1 configuration for Rectifier modules.

(18)

4.4.2.5

Documentation

4.4.2.5

Documentation

Site specific design documentation shall be submitted for review and approval by the appropriate design approval authority in RailCorp. The site specific documentation shall include (but not limited to) the following:

• Site details • Site details

• Requirement Analysis • Requirement Analysis • Proposed load calculations. • Proposed load calculations. • Equipment requirements • Equipment requirements • DC distribution arrangements. • DC distribution arrangements. • Floor loading. • Floor loading.

• Rack dimensions and floor space allocation. • Rack dimensions and floor space allocation. • Rectifiers

• Rectifiers

• Redundancy and availability • Redundancy and availability

• Reliability and availability performance including MTBF • Reliability and availability performance including MTBF

Figure 2 - Example of Small DC Power Supply System Rack Layout

Notes:

1. Rack depth may be 400mm deep or 600mm deep dependent on site layout of the Comms room. 2. The 400 deep rack will have limitations on battery sizes.

3. Wall mount DC load distribution may be used at some sites.

4. Example shown is for illustration purposes only.

(19)

5 Cables

5.1.1 Standards,

Specifications and Drawings

Document

type

Number

Standard Telecommunication Outdoor Cabling ESM 102 Standard Signalling Bungalow Telecommunications

Cabling

ESM 105

Standard Telecommunications for Traction Substations and Section Huts

ESM 106

Standard Telecommunications Equipment Rooms ESM 107 Standard Emergency Telephone Systems ESM 108 Standard Installation Requirements for Customer Cabling AS/ACIF S009. Standard Australian / New Zealand Wiring Rules AS 3000 Standard Telecommunications Installations – Integrated

Telecommunications Cabling systems for Commercial Premises

AS/NZ 3080ZA3.2

Specification Reinforced Pre-Cast Concrete Cable Pits SPM 0123 Specification Construction of Cable Route and Associated

Civil Works

SPG 705

5.1.2 Requirements

5.1.2.1 General

All new outdoor telecommunications network cables, including re-configuration of the existing outdoor cabling network will be in accordance with the Telecommunications Outdoor Cabling standard ESM 102. Cabling in tunnels is considered to be outdoor cabling.

Additional requirements to those specified in this standard also apply for special situations such as cables in tunnels, aerial cable, cables associated with high voltage installations.

5.1.2.2 Capacity

For new cables, minimum cable capacity shall be provided as per the Telecommunications Outdoor Cabling standard ESM 102.

5.1.2.3 Diversity

Diverse paths may be required to ensure the availability of telecommunications infrastructure. Types of diverse cable routes are detailed in the Telecommunications Outdoor Cabling standard ESM 102. Cable diversity requirements are generally defined in the specific telecommunications infrastructure or service that the cable supports.

(20)

5.1.2.4 Cabling in Telecommunications Equipment Rooms

All cabling inside of Telecommunications Equipment Rooms will be provided in accordance with the Telecommunications Equipment Rooms standard ESM 107.

5.1.2.5 Cabling in and leading into Traction Substations and Section Huts

All cabling inside of Traction Substations and Section Huts will be provided in accordance with the Telecommunications for Traction Substations and Section Huts standard ESM 106.

5.1.2.6 Cabling in and leading into Signal Bungalows

All cabling inside of Signal Bungalows and location cases will be provided in accordance with the Signalling Bungalow Telecommunications Cabling standard ESM 105.

5.1.2.7 Cabling Systems Works

Installation shall be carried out by communications cabling installer that is accredited with qualification relevant to the performance standards of various elements of specific cabling systems.

All works shall be supervised at all times by a ACA registered cabler who is a holder of a Open Licence with accreditation indicating completion specific endorsement courses (applicable to works undertaken) in the areas of installation, testing, commissioning and work safety practices.

5.1.2.8 Site Conditions

The cabling system provider shall carry out all required audits to fully inform themselves of the condition of the site and other issues that could be impacting on the delivery of works. This includes site conditions such as hazards that may be present at the site, crown land, heritage listing, environmentally sensitive and local council regulations.

5.1.2.9 Enabling

Enabling works may be required to remove or relocate existing Signalling and Communications services away from areas of high risk of construction risks. Installation of Combined Services Route shall be installed and commissioned prior to any decommissioning of existing cable routes in order to facilitate and operationally manage the transition of services to the new route.

5.1.2.10 Health & Safety

The proposed layout of cable site installation system and routes shall ensure that equipment, telehousing facilities and metallic components shall not be installed in areas where earth potential rise (EPR) may exceed allowable power system fault conditions as per Clause 5.1.4 of AS/ACIF S009.

5.1.2.11 Earthing

Earthing and related works shall be installed as per ESM 109 and the cabling provider shall provide:

Where specified as part of the works, a provision of Communications Earth System (CES).

(21)

Bonding of cabling system earth equipments, enclosures, pathways and earthing systems including provision of earth bar (MDF, IDF etc.) where specified as part of the works. In case of existing earthing systems, they shall be checked for compliance and upgraded as necessary to meet the current standards.

5.1.2.12 Redundant Cabling

There are large numbers of redundant cabling in the rail network and opportunity should be taken to remove this, if it is likely to impact on new cable works (where specified as part of works). Documented disposal management systems as per RailCorp guidelines shall take be complied for the disposal of redundant assets.

5.1.2.13 Combined Services Route

The combined services route is a multi disciplinary route asset used to distribute and protect cables for new installation, expansion and maintenance. Combined Services route shall be selected and designed to, comply with the minimum segregation from other services as mandated by ESM 102, SPG 705, AS/ACIF S009 and AS3000 in accordance with AS/NZ 3080ZA3.2. The construction of new cable route shall not impact or damage any existing services, where it is necessary to construct cable route in areas that has potential of having live services - communications, gas, power etc. The use of non-destructive method i.e. digging by slit-trenching or pot holing using hydro vacuum excavation -“sucker trucks” shall be used as much as possible in existing rail corridors.

5.1.2.14 Ground Level Troughing (GLT)

GLT shall only be used for short distances typically for local routes and from the cable pit to the cable entry through of the Signalling bungalow and Communications room.

6 Transmission

Networks

6.1.1 Standards,

Specifications and Drawings

Document

type

Number

Specification Synchronous Digital Hierarchy Equipment for Fibre Optical Cable

SPM 0098

Specification Channel Multiplexer Equipment STM 0097

6.1.2 Requirements

6.1.2.1 General

Transmission networks to support telecommunications are generally required to be extended to or modified to support the expansion of existing or new rail corridors. Transmission networks are required to cater for trunking of voice and data channels to efficiently utilise backbone cabling between telecommunication equipment rooms.

All new Transmission network equipment shall be provided in accordance with existing RailCorp supply agreements. Where existing supply agreements and or specifications are not in place, the Transmission network equipment offered in the design shall be subject to review and approval by the respective design authority in RailCorp’s Communications

(22)

Engineering. Alternatively, the new equipment shall be subject to RailCorp’s type approval process.

6.1.2.2 Diversity

Backbone transmission networks shall have diverse paths to ensure high availability and cable diversity (See 5.1.2.2) is used to provide diverse paths.

6.1.2.3 Synchronous Digital Hierarchy (SDH)

RailCorp has an extensive network of SDH nodes based on a protective ring topology and a consistent equipment platform. All new SDH equipment is required to fit into the wider RailCorp network and so needs to be designed and structured in consultation with RailCorp Communications Engineering subject matter experts or design authority. The SDH equipment shall comply with the Communications Engineering Specification No. SPM 0098 and be provided in accordance with existing RailCorp supply agreements.

6.1.2.4 Time Division Multiplexing (Channel MUX)

RailCorp has an extensive network of TDM equipment based on a consistent equipment platform. All new TDM equipment is required to fit into the wider RailCorp network and so needs to be designed and structured in consultation with RailCorp’s Communications Engineering. The TDM equipment shall comply with the Communications Engineering Specification No. STM 0097 and be provided in accordance with existing RailCorp supply agreements.

Some of the type of Channel Cards used by RailCorp is as follows: • 4Wire + E&M,

• 2Wire,

• Subscriber and Exchange cards for Telephones, • N x 64k Data cards,

• RS232 Data cards and • Modem Line Driver cards.

MUX systems provided for Signal SCADA data links and possibly other critical applications shall be designed with separate MUX systems providing “A” and “B” legs of any data links that require diversity.

Field equipment cabled back to the “A” and “B” MUX systems generally require diverse paths/routes and is arranged by having “A” and “B” links following opposite directions towards “A” and “B” equipment in different rooms.

6.1.2.5 Wave Division Multiplexing (WDM / CWDM / DWDM)

Generally new WDM infrastructure is best incorporated into RailCorp’s existing WDM systems and so, it shall be designed and provided by or in close consultation with RailCorp’s Communications Engineering, in accordance with RailCorp’s design process and RailCorp’s existing supply agreements.

6.1.2.6 Microwave

Where it is not feasible to provide cabling for transmission, Microwave links may be considered. All new Microwave equipment shall be provided by or in close consultation with RailCorp’s Communications Engineering, in accordance with RailCorp’s design process and RailCorp’s existing supply agreements.

(23)

6.1.2.7 Power and Location

Generally Transmission Network infrastructure is to be located in telecommunication equipment rooms in a Transmission infrastructure specific cabinet/s, specified in section 4.1 and 4.3 respectively, and powered by the telecommunications equipment room power supply specified in section 4.4.

7 Emergency and Operations PABX Telephones

Telephone Services used throughout the RailCorp Network support a variety of business needs categorised as follows:

Tunnel Emergency Telephones (Fire phones) Train Control Telephones

Signal Post Telephones (SPTs) X-ring Telephones.

Operational Telephones

Administrative/Office Telephones

7.1.1 Standards,

Specifications and Drawings

Document

type

Number

Standard Emergency Telephone Systems ESM 108 Standard Tunnels Engineering Standard ESC 340 Specification Weatherproof Telephones SPM 0082 Specification Signal Post Telephone SPM 0082

7.1.2 Requirements

7.1.2.1 Tunnel Emergency Telephones

RailCorp tunnels standard ESC 340 requires emergency telephones to be installed in new RailCorp railway tunnels using electric passenger rolling stock.

Tunnel Emergency telephone systems and supported handsets shall comply with the RailCorp Standard ESM 108.

Miscellaneous Emergency Telephones not associated with the rail tunnels shall be catered for by the Train Control Telephone Network where they are track side or associated with train running and by the Operational Telephone Network in other cases.

7.1.2.2 Train Control Telephones

Train Control telephones support the movement of rolling stock throughout the RailCorp Network. These provide direct communication between Rail Management Centres/Signal Boxes and the wider rail network.

(24)

At Major Control Centres Touch Screen based Voice Communications Systems integrated with the C&CS Train Control Telephone Network shall be used. Other Control Centres and Signal Boxes shall use integrated feature rich digital telephones.

In the wider network a combination of weather proof analogue telephones, standard analogue telephones and digital feature telephones shall provide voice communications. Telephones on the Train Control Network shall be battery backed for protection against the primary source of power being unavailable.

Telephone calls on this network shall be recorded on External Voice Recorders interfaced with the telephone network.

Refer to 7.1.2.8 for a list of locations where Train Control Telephones shall be provided.

7.1.2.3 Signal Post Telephones (SPTs)

Signal Post Telephones (SPTs) and other trackside telephones associated with signalling shall be provided at locations as shown on the Signalling Plan.

SPT equipment shall be in accordance with SPM 0082.

SPTs shall be connected to the Train Control telephone network.

7.1.2.4 X-ring Telephones

X-ring telephones shall be provided so that a Signaller can call multiple stations with a single call to convey information on “out of the ordinary” train running information such as train diversions or cancelled trains.

These telephones shall be grouped in logical arrangements that generally follow stopping patterns at stations.

X-ring telephones shall be connected to the Train Control Telephone Network as a standard office type handset that could be sourced from a C&CS store.

The arrangement for providing the X-ring functionality is normally incorporated into the VCS provided for the Signaller.

7.1.2.5 Operational Telephones

Operational telephones provide the communications to locations that support the rail network infrastructure.

Telephones on the Operational Network shall be battery backed for protection against the primary source of power being unavailable.

A combination analogue, digital and VoIP telephone handset types are supported on the RailCorp C&CS Operational Network. The phones shall be from the current schedule selected for general issue from the C&CS store.

Analogue and digital telephone utilise the cable network, where as the VoIP telephones shall be deployed over the C&CS Data Network.

(25)

7.1.2.6 Administrative/Office Telephones

Administrative/Office Telephones are used in office type environments where communications is required to support Rail business other than those mentioned above. The supported telephone types on this system include standard analogue and VoIP feature phones.

The phones connect to RailCorp ICT Administrative Telephone Network and are provided over the same ICT data network that supports the desktop personal computers.

Telephones on the Administrative/Office Telephone Network are not necessarily (or generally) battery backed.

Refer to 7.1.2.8 for a list of location where Administrative/Office Telephones are used

7.1.2.7 PABX design requirements

PABXs shall be incorporated into the wider RailCorp Emergency, Train Control and Operational Telephone networks

PABXs shall be dedicated to the purpose of the system.

PABXs shall be installed in a Telecommunications Equipment Room1 and powered from the room’s 48VDC power supply, which shall have a minimum nominal battery backup time of 12 hours.

PABX network design shall be referred to RailCorp’s Communications Engineering designers at concept design stage for direction and/or advice on networking aspects including:

a) where the PABXs are to fit into the wider network b) suitability of the model of PABX proposed

c) availability and suitability of use of existing rooms

PABX installation and configuration design shall be referred to RailCorp’s Communications Engineering designers at detail design stage for direction and/or advice on site aspects including:

a) rack location within the room and any cable tray work required b) MDF allocation for cable termination or any MDF extension required c) DC Circuit Breaker allocation or any DC Power Supply extension required d) number allocation

e) routing plans

f) trunk signalling protocols g) synchronisation plans

1

(26)

7.1.2.8 Telephone locations

The list below should be used as a guide to determine the type of telephone required at a location and the provider network. Generally more specific locations and quantities for any station shall be determined by the station working group:

Building Location Application Type Telephone Network

Railway

Tunnel Tunnel Emergency

2 Wire Analogue Weather Proof Smart Telephone Emergency Telephone Network Railway Station Station Masters Office Control Telephone,

X-ring VoIP & Analogue

C&CS Train Control Network

Supervisors Office Operational Telephone

VoIP & Digital feature phones C&CS Operational Network Booking Office Operational Telephone, facsimile

VoIP & Digital feature phones

C&CS Operational Network

Meeting, Meal,

Train Crew rooms General Purpose

Standard 2wire analogue phones C&CS Operational Network Communications Rooms Maintenance/Test Telephones

VoIP & Digital feature phones

Lift Phones Rail Network Operation

Standard 2wire analogue phones C&CS Operational Network Gate Access

Control Rail Network Operation

Standard 2wire analogue phones

Visitor Access Entry

Phones Rail Network Operation

Security Guard Rail Network Operation

Standard 2wire analogue phones C&CS Operational Network Other locations

within building Rail Network Operation

VoIP feature phone / Analogue C&CS Operational Network Public Phones External Public Network Provider Vending Machines External Public Network Provider Substation s & Section Huts High Voltage

Locations Operational Telephone VoIP feature phone

Railway

Corridor Track Side Phones Signal Post/EOL/ESML

2 Wire Analogue Weather Proof Smart Telephone

C&CS Train Control Network Signal locations cases Maintenance phones M1&M2 Standard 2wire analogue phones C&CS Operational Network

Traffic Huts Train Control

Wayside Huts Rail Network Operation VoIP feature phone Operational Network

Rail Managem ent Centre

Train Controllers

Panels Train Control

VCS & backup Digital Feature phone

Signallers Panels Train Control

Line Information

Controllers Train Control

Other locations

within building Rail Business

Analogue, Digital or VoIP feature phones

(27)

Building Location Application Type Telephone Network

Signal

Boxes Signallers Desks Train Control Digital Feature phones

Operations phone Digital Feature phones

Line Information

Controllers Train Control

Digital Feature phones, External Conference Bridge Unit

Operations phone Digital Feature phones

Other locations

within signal box Rail Network Operation

Maintenan

ce Depots Offices Rail Network Operation

Car Sheds Rail Network Operation DECT

C&CS Operational Network Emergenc y Operation

s Centres Control Room Rail Network Operation

Security

Centre Control Room Security

VCS & backup Digital Feature phone C&CS Operational Network Train Crewing

Centre Control Room Train Crew

VCS & backup Digital Feature phone C&CS Operational Network Office Building Desks

Non Critical Rail

Business VoIP feature phones

ICT

Administrative/Office Network

Meeting Rooms

Non Critical Rail

ICT

Administrative/Office Network

Offices

Non Critical Rail

ICT Administrative/Office Network facsimile VoIP Analogue Telephone Adaptor ICT Administrative/Office Network

Table 1 - Telephone Locations

8 Data

Networks

The C&CS Data Network shall provide network connectivity for data, VoIP and video applications installed along new rail corridors. The data network shall provide backbone connectivity for a number of operational and non operational train services. The critical operational services shall include DTRS, CCTV etc. The non operational business services shall include ticketing, EFTPOS, station LAN etc.

This section describes the access requirements for both the ATM Network and Operations Critical Data Network (OCDN).

The ATM Network is currently the backbone of the C&CS Data Network. The OCDN is designed to replace the ATM Network and it is anticipated that this network will be ready for general use by mid 2012. Sites and new corridors requiring access to the Data Network before July 2012 should be designed to connect to the ATM Network with

(28)

provision for migration to the OCDN. Sites and new corridors requiring access after July 2012 should be designed for connection to the OCDN.

8.1 General

Requirements

8.1.1 Standards,

Specifications and Drawings

Document

type

Number

Standard Telecommunications for Traction Substations and Section Huts

ESM 106

Supply agreement

OCDN Customer Access and Provider Access switch panel supply agreement*

WS15292

Drawing RailCorp ATM Network Core, Edge and Access Switches

MET - SC 0004

Drawing OCDN Aggregate Sections Block Diagram MET - SC 0275 Drawing OCDN Sect.04 Central to Warwick Farm

Aggregate Section Block Diagram

MET - SC 0265

Specification Element Naming Convention TMM P181 Specification Naming Convention for Switch Ports TMM P197

* Current OCDN switch panel supply agreement list to be sourced from RailCorp’s Communication Engineering when required.

8.1.2 Type approved equipment

All new Data network equipment shall be provided in accordance with existing RailCorp supply agreements. Where an existing supply agreement and or specification are not in place the data network equipment called for in the design shall be subject to RailCorp’s type approval process.

8.1.3 C&CS ManageNet

The C&CS ManageNet is a network that extends to all Simple Network Management Protocol (SNMP) compatible equipment required to be monitored by C&CS. All telecommunications equipment supplied including Ethernet switches, Transmission equipment, PABXs and Radio base stations etc shall be SNMP compatible and connected to the C&CS ManageNet.

IP Addressing for Data Network elements on ManageNet shall be allocated by C&CS.

8.1.4 Network Management and Monitoring

All data network infrastructure shall be monitored and managed in band or out-of-band by Simple Network Management Protocol (SNMP) and be integrated with ManageNet and the Rail Technology Operations Centre (RTOC) monitoring systems. Where an SNMP interface is not available this shall be provided by Remote Terminal Unit (RTU).

(29)

8.1.5 Naming

Conventions

The naming of data network elements shall conform to the convention specified in document TMM P181. The names applied to individual Ethernet switch and router ports shall conform to the convention specified in TMM P197.

Element names and port names use C&CS site codes. For each new site a request for a site code must be made to the Telecommunications Network Configuration (TNC) group within C&CS.

8.1.6 IP

Addressing

The allocation of IP addresses for VPNs on both the ATM Network and OCDN is the responsibility of C&CS.

8.1.7 Power and location

Generally data networks infrastructure is to be located in equipment rooms in data network infrastructure specific cabinet/s, specified in section 4.1 and 4.3 respectively. In telecommunications equipment rooms, the data network infrastructure shall be powered by the telecommunications equipment room power supply specified in section 4.4.

8.1.8 Commissioning

Tests

All new data services shall be tested for throughput and latency as per RFC 2544.

8.1.9 Fibre

Connectivity

All sites where data services are required shall have access to fibre. Where this is not possible, access to copper shall be provided and modems (serial data or Ethernet SHDSL) shall be installed.

8.2 ATM

Network

Requirements

The ATM network is the current backbone of the C&CS data network (refer to drawing SC 0004) and consists of a fully redundant core with diverse links to Edge nodes. Access nodes connect to the Edge nodes by single STM-1 links.

8.2.1 ATM Network VPNs

Two types of VPNs are available for connection across the ATM: • Layer 2 Point to Point or Multi-point

These VPNs may be as simple as a transparent layer 2 (Ethernet) point to point connections or a complex mesh of point to multi-point PVC’s.

• Centrally Routed

These VPNs consist of PVC’s connected to a virtual router instance on a C&CS operated core router. For redundancy the virtual router instance may be duplicated on the two core routers.

Data services for new sites and corridors will be provided as an extension of one of the existing VPN’s on the ATM Network (e.g. SPI, CCTV, Station LAN, etc). Where a completely new type of service is required then a new VPN will need to be created.

(30)

8.2.2 Access to an ATM Network VPN

Ethernet and IP data services shall access their VPN on the ATM Network either by connection directly to either:

• an ATM Edge or Access node LAN emulation interface or

• an Ethernet Access Switch (connected as described in section 8.2.3) or • SHDSL modem (connected as described in section 8.2.3)

In all cases the access interface shall be Ethernet (IEEE 802.3) RJ45. Note that exception may be made for services that for site specific reasons require a fibre connection to host equipment (e.g. High Voltage Site RTU equipment).

8.2.3 ATM Node Access Network

The ATM Network consists of approximately 100 nodes distributed across the CityRail network area. Additional ATM nodes shall not be added to the Network due to the nodes nearing end of life and the soon to commissioned OCDN. Extension of the ATM Network to new sites and corridors shall therefore be provided by Ethernet Switches.

Ethernet switches shall be installed at sites where Ethernet data services are required. These switches shall be connected by Gigabit Ethernet back to an Ethernet switch co-located with the nearest ATM node.

New access switches shall be selected from the OCDN panel supply agreement for Customer Access and Provider Access switches.

Where fibre is not available an Ethernet over SHDSL modem link shall be provided.

8.3 OCDN

Requirements

The Operations Critical Data Network (OCDN) shall replace the ATM Network as the backbone of the C&CS Data Network. The OCDN shall be extended along new rail corridors and to new sites in a manner consistent with the overall OCDN hierarchical design.

8.3.1 OCDN

Hierarchy

The Operations Critical Data Network (OCDN) hierarchy consists of four layers; the Core, Aggregation (Distribution), Provider Access (Distribution-edge) and Customer Access (OCDN Points-of-Presence).

(31)

Figure 3 - Overview of the Operations Critical Data Network (OCDN)

The core of the OCDN uses IP/MPLS standards to provide Layer 3 Multiprotocol BGP Virtual Private Networks (VPN) with virtual routers as redundant gateways to two logically separate core partitions. The distribution of the OCDN uses carrier Ethernet to make last-mile connections to the OCDN Customer Access Switch. Each customer network is provided with one or more VPNs, each with an associated Virtual LAN (VLAN), allowing hosts connected to the Rail PoPs to communicate on the VLAN and over the Layer 3 VPN (using the Virtual Routers).

The OCDN is Core and Aggregate sections are shown in drawing SC 0275. Provider Access details are shown in separate drawings, one per section. The drawing SC 0265 is an example of a section drawing.

8.3.2 OCDN VPNs – Ethernet/IP Networks

The OCDN provides logically separate VPNs for each customer network. Data services for new sites and corridors will be provided as an extension of one of the existing VPN’s on the OCDN Network (e.g. SPI, CCTV, Station LAN, etc). Where a completely new type of service is required then a new VPN will need to be created.

8.3.3 Provider

Access

Provider Access equipment is required in locations requiring access to the OCDN and shall be installed in equipment rooms with a diverse path to the rest of the OCDN distribution layer.

Provision of a Provider Access switch is the responsibility of RailCorp’s Communications Engineering. All new Provider Access equipment shall be provided in accordance with the OCDN switch specification and the existing OCDN Provider Access switch panel supply agreement.

For each site with a PA switch a single switch port shall be allocated for each customer VPN required at that site. If a customer application has multiple devices at a site then a Customer Access switch will be required (section 8.3.4).

8.3.4 Customer

Access

For a site where a customer requires more than one port to access their OCDN VPN (e.g. two or more host PCs) then a Customer Access switch shall be installed. Use of the CA switch shall be dedicated solely for that customer.

(32)

Provision of a Customer Access switch is the responsibility of the customer. All new Customer Access switches shall be provided in accordance with the OCDN switch specification or the existing OCDN

8.3.5 Interfaces

CA and PA switch interfaces shall comply with the relevant IEEE standards. Customer connection to PA switches shall be made using commercially available Ethernet transceivers at speeds of either 100Mbps or 1000Mbps over Category 5e UTP or SMOF media.

A typical arrangement for access to the OCDN is shown in the below figure.

Figure 4 - Typical OCDN Access Arrangement (CityRail Station)

8.3.6 Availability

Where a data service requires a higher than 99.9% network availability, a diverse path to the Provider Access layer is required and the Customer Access equipment must be selected from a specific subset of the OCDN switch specification and the existing OCDN Customer Access switch panel supply agreement.

Generally OCDN diverse paths are to be provided by cable diversity (See 5.1.2.3).

8.3.7 Aggregation

(Distribution)

Generally modifications or expansions of the OCDN distribution layer if required shall be designed and provided by RailCorp’s Communication Engineering, in accordance with RailCorp’s Communications Engineering design process and RailCorp’s existing supply agreements.

8.3.8 Core

Generally changes to the Core segment shall not be required however in the case that the OCDN Core is required to be modified or expanded it shall be designed and provided by RailCorp’s Communications Engineering, in accordance with RailCorp’s Communications Engineering design process and RailCorp’s existing supply agreements.

(33)

8.4 Site Specific Requirements

8.4.1 High Voltage (HV) Sites

HV sites include substations and section huts. A number of data services are required at these sites (Electrical Traction SCADA, VoIP and access to the RailCorp ICT Network) and shall be provided by installation of a C&CS Customer Access switch. These switches shall be of an industrial type designed to operate in harsh environments. At each site two separate and independently connected switches shall be installed for A and B network diversity.

For further information on the data service requirements of HV sites refer to the document Telecommunications for Traction Substations and Section Huts ESM 106

8.4.2 Stations

At each station a C&CS Provider Access (if the OCDN is available) or ATM Network Ethernet Access switch shall be installed in a 19” cabinet within the station services room. Space shall be allocated within the station services room for an OCDN rack and other racks as required for SPI, Ticketing and CCTV.

Separate Customer Access Ethernet switches shall be installed for VoIP, SPI, CCTV, Station LAN and Ticketing. Responsibility for the installation of these switches is with the application owner. Connection between these switches and the OCDN switch shall be Gigabit Ethernet over single mode optical fibre.

8.5 Serial

Data

Data devices capable of communicating directly via Ethernet/IP are preferred. Due to technological limitations or requirements some applications require the provision of serial data links. This includes applications such as Signal SCADA, ATRICS links and the legacy ticketing (AFC) network.

Serial data links shall be provided either using two/four wire serial modems, serial to optical converters or over Ethernet using serial to Ethernet converters.

8.5.1 Interfaces

Serial data links shall use standardised interfaces and protocols, i.e. RS232, RS485, RS422 and X21.

8.5.2 Real

Time

Critical Serial data

Real Time critical Serial data links shall have a round trip time less than 100ms. They shall have full redundant paths either via transmission system or copper system. A risk analysis for these services shall be provided to RailCorp’s Communications Engineering.

8.5.3 Non Real Time Critical Serial data

Non real time critical Serial data links shall have a round trip time less than 150ms.

8.5.4 Signalling

Applications

Serial data services for Signalling applications (e.g. Signal SCADA) shall not be provided over Ethernet (using Serial to Ethernet converters). They shall be provided with modems and use the SDH/PDH network as a backbone.

Engineering Specification