Download pdf - Page Effective from : RDSO/ SPN/TC/99/2012 Rev. 2 1 of 35

Effective from : : 27.08.2018
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
Specification for VoIP based Train Control Communication System
VoIP BASED TRAIN CONTROL COMMUNICATION SYSTEM
/SPN/TC/99/2012
Specification No. RDSO/SPN/TC/99/2012 Revision-2

, , - 226011
TELECOM DIRECTORATE
MINISTRY OF RAILWAYS, MANAK NAGAR, LUCKNOW - 226011
Page 2 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
DOCUMENT DATA SHEET
TITLE OF DOCUMENT: SPECIFICATION FOR VOIP BASED TRAIN CONTROL COMMUNICATION SYSTEM.
AUTHOR:
APPROVED BY
THIS DOCUMENT SPECIFIES TECHNICAL SPECIFICATION FOR VOIP BASED TRAIN CONTROL COMMUNICATION SYSTEM.
Page 3 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
DOCUMENT CONTROL SHEET
RDSO/SPN/TC/99/2012 REV.0 FIRST ISSUE JULY 2012
RDSO/SPN/TC/99/2012 REV.1 FIRST REVISION DEC 2013
RDSO/SPN/TC/99/2012 REV.1 AMENDMENT NO. 1
AMENDMENT NO. 1 NOV 2016
RDSO/SPN/TC/99/2012 REV.2 SECOND REVISION AUGUST 2018
Page 4 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
I. Scope: This document covers the requirements of VoIP based train control communication system (TCCS). The purpose of the system is to provide mainly voice communication between controllers (of various control circuits) at divisional headquarters (HQ) and officials manning such control circuits at way stations/ other identified locations including Assistant Station Masters (ASM). This system also covers emergency communication from along the track through emergency communication sockets. This document does not cover the specification of underlying IP infrastructure.
II. Source: 1. Draft specification for VoIP based train control communication system is issued
by RDSO Lucknow to comply with the directive issued by Railway board vide letter number No. 2010/Tele/9(1) dated 05.10.2010.
2. This document is revised to incorporate experience/feedback of the VoIP based TCCS System trial in MAU-SHAHGANJ Section of VARANASI Division of NE Railway in the year 2017, in compliance with the directives of Railway Board vide Letter 2010/Tele/9(1)/1 Pt-1 dated 09.03.2018.
1 Introduction:
The existing train Control communication system is based on legacy analog telephony technology. It uses omnibus telephone circuits which provide communication with each train working point, thus facilitating efficient train operation. The communication arrangement should provide satisfactory and reliable communication between the controller and the various way-side stations, important signal cabins, loco sheds, yard offices etc. The Railway network is split into individual sections consisting of a number of way stations which are controlled from HQ control office. According to traffic requirements and to cater to the needs of Electric Traction area, a section may be provided with one or more Railway Control Circuits. The related definitions and various types of control circuits generally in use are given in Annexure-1 to this document. This specification intends to use standard, modern and widely proven Internet Protocol (IP) technology as a platform to provide TCCS, thus enabling use of common infrastructure for voice and data services. The specification lays down Functional and technical requirements for system elements and of the system as a whole to work as Train Control communication system (TCCS) on IP platform.
2 The VoIP based Train Control Communication System (TCCS) consists of following Components:
2.1 Servers and End Points: 2.1.1 Server/ servers cluster for Call control and conferencing, network
management, voice recording etc. to meet the requirements of this specification.
2.1.2 Controller’s console 2.1.3 Test Room Console/Equipment. 2.1.4 Gateways for providing connectivity with Railway’s Telephone Exchange
(FXO Gateway), Existing DTMF based control communication equipment
Page 5 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
(DTMF Gateway), Emergency communication circuit (Emergency Gateway), and for generating SMS alerts and sending emails (Event Notification Gateway)
2.1.5 Way side IP control telephones/Equipment for Station masters and other users of control circuit.
2.2 Underlying Network connecting Divisional HQ control office to various way side stations: The specifications for underlying network & network components i.e. switches and routers are not part of this specification.
3 General and Functional requirements:
3.1 The Typical (Indicative) schematic arrangement for “VoIP based train control
communication system (TCCS)” is given in figure 1.
Figure 1: Typical (Indicative) Schematic Arrangement for VoIP based train
control communication system (TCCS)
3.2 The purpose of Train Control communication systems (TCCS) is to provide voice communication between controller and various way stations. This system shall have the features similar to omnibus communication system. The system shall meet the requirements elaborated in the following communication scenario. (For definitions of various terms used in this specification, see annexure I)
3.2.1 Controller makes a call to way station A. Way station A answers the call and conversation starts between the controller and way station A.
Page 6 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
3.2.2 Controller makes another call to way station B, way station B responds to the call and gets added to the ongoing call between controller and station A. Controller can add more way stations to the ongoing conference call by dialing their numbers.
3.2.3 When-ever a way station makes a call to the controller, he gets added to the ongoing conference. For example, if station C dials the controller’s number, he will not get busy tone. Instead he will be added to the ongoing conference between controller and way stations.
3.2.4 If any way station, who is participant of the conference call, replaces the handset on the telephone cradle, he will be disconnected from the conference.
3.2.5 Controller should also be able to disconnect or Mute/Unmute any participant of the conference call (Desirable feature).
3.3 The TCCS shall be able to cater for more than one controller and their respective way stations. The details of various controllers are given in Annexure-1.
3.4 The TCCS shall meet the following requirements also in addition to basic requirements given in clause 3.2
3.4.1 Controller shall be able to make a group call to way stations under his jurisdiction.
3.4.2 The controller shall also get suitable visual indication on his console in addition to ring back tone, whenever the bell/buzzer at the way station control phone rings in response to the call initiated by him. The controller shall get visual indications regarding status of the call initiated by him till the time the called party responds by lifting the handset. The audio indication (ring back tone) shall be managed in such a way so as to cause minimum disturbance to the ongoing conference. Only one long beep is desired as ring back tone. The Ring back tone on the controller phone shall be configurable to ON or OFF by user (Controller).
Whenever controller initiates a new call, it shall not hamper or put on hold the ongoing call/ conference, if any, between controller and way side station/stations
3.4.3 The section Controller shall be able to call other controllers from his console and add them to ongoing conference call.
3.4.4 From way station IP control telephone, it shall be possible to call the controller by pressing a button or by dialing a code. The way station control telephone shall get connected to the ongoing conference of controller without generating any ring at controller’s end. The controller shall get a visual indication and a beep (it is desirable to disable the beep) regarding newly added way station telephone to its conference. When way station Phone calls the controller, it will generate ring if the controller’s telephone is “On Hook”. If controller’s phone is on a call, way Station Phone joins the conference call automatically.
Page 7 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
3.4.5 Way station telephones / equipment for ASMs shall have programmable hard keys to call any of the controllers pertaining to that section. Individual key shall be programmed to call a particular controller. The top key shall be programmed to call the section traffic controller.
3.4.6 The section traffic controller shall be able to give ring to the way station telephone for ASM (Assistant Station Master) even if this phone is busy in conversation or not properly restored to “On Hook” condition. The ASM’s phone shall show the caller ID of the second caller. On getting this audio visual indication, ASM would be able to take section controller’s call if he decides so.
3.4.7 The control phone at a way station for ASM shall be able to receive call from any of the controller pertaining to that section. However, the incoming call from section traffic controller to ASM’s way side telephone shall generate distinct ring tone.
3.5 The system shall provide a dedicated recording device for recording conference conversations of various controllers. It should also be possible to record direct way station to way station conversation not involving controller as per user requirement.
3.6 Emergency Control Circuit: An arrangement (gateway) shall be required for interfacing IP network and the emergency control circuit (Details in Annexure- 1). It shall be possible to reach the control office by plugging a 4 wire portable control telephone into any of the Emergency sockets. The gateways can be provided either at every way station or only at HQ depending upon the user requirement and the availability of connectivity from way station to HQ. A two way communication shall be setup between the emergency controller and the site. If any other person plugs his telephone in some other socket on the same emergency control section, he will also join the conference.
3.7 It shall be possible to join emergency conference call received on emergency control circuit, to the Section Controller’s conference if needed, in control office by Traction Power Controller/ Power Controller who normally also works as emergency controller.
3.8 The system shall provide for flexible and programmable call rules (As per user requirement). Some indicative typical call rules are;
3.8.1 HQ control phone of any control circuit shall be able to do conference with any other HQ control telephone or any telephone which is a subscriber to a railway exchange.
3.8.2 It shall be possible for any authorized subscriber of a Railway telephone exchange to call any controller by dialing a code and become part of its conference. The controller shall get a visual indication and a beep (It is desirable to disable the beep) regarding newly added subscriber to controllers ongoing conference.
3.8.3 A typical call rule matrix is given in figure 2. (This is only indicative and the requirement may change from time to time and from place to place.
Page 8 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
Therefore the call rules shall be flexible and programmable). These call rules are for the Section Controller/ other controllers/ ways stations/ Emergency controller of a particular traffic control jurisdiction only.
3.9 If certain way side stations get isolated (get disconnected from the HQ) and not able to register with either the main server block or standby/ DR server block, in that case the way side control telephone shall be able to make a call at least to way side control telephones provided on stations on either side of that particular station. e.g., if stations A, B and C got isolated then control phone at station B shall be able to call stations A and station C, whereas station A shall be able to call at least station B and station C shall be able to call at least station B with basic telephony features.
3.10 The purchaser preferably shall provide the ring path to system provider to connect the server block for providing media redundancy. In case of failure of main path the system continue to run on the ring path without any disruption of communication.
3.11 The IP based Train Control Communication System should have GUI for basic configuration. The indicative configuration matrix may be as given in Fig. 2 below;
To
From
Other way station control telephones
Subscriber of Railway exchange
Section controller’s console
Emergency Controller
Other controllers Console
Yes No Yes Yes Respective way station control phone only
Yes
Yes Yes Yes No Yes
Other way station control telephones
No No Their respective controller only
No No Yes
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
4 Technical specifications: 4.1 The various components of the VoIP based train control communication system,
while working as a system shall comply all the functional and general requirements as brought out in clause 3 of this specification, even if it requires additional hardware and software other than those mentioned in this specification. Any such additional hardware and software shall be part of the system and shall be supplied along with the system. Salient components of TCCS are as given in clause 2 of this specification.
4.2 Communication Protocol: The communication server shall support SIP 2.0 as per RFC 3261 and its extensions as per latest relevant RFCs or it shall support both SIP 2.0 and H.323 .The end points shall support either SIP or H.323 as detailed against these individual items in this specification.
4.3 The reference to IP phone in this specification shall SIP or latest platform based IP telephones unless specifically mentioned otherwise.
4.4 Any reference to ASM’s way station control telephone/Equipment shall be IP telephone. Reference to button shall be hard keys.
4.5 The equipment hardware and software shall take care of changes in system time caused by events such as leap year etc. and shall not affect system working.
4.6 There shall be uniform distribution of time for all elements (servers and end points) from a single source through NTP v 4.1.2 (RFC 1305). All the elements shall have NTP protocol support. If timing information is not available, the elements shall work with last available time and date. The timing and date information shall be retained even if the power supply to the element is cutoff.
4.7 The TCCS is expected to work continuously round the clock with high availability. Therefore all the components shall be capable of intensive 24x7 operations. Selection of components shall be based on this operating requirement.
4.8 The TCCS shall have a centralized Network management system (NMS). Test Room Console/Equipment shall be provided for centralized testing and maintenance of the system.
4.9 Security: 4.9.1 There shall be separate VLAN for TCCS system (subject to VLAN capable
switches). 4.9.2 Only authorized IP telephones will be able to register and communicate
within the system. 4.9.3 Any PC connected to second Ethernet port of the IP telephones shall not be
able to send data traffic to the voice VLAN for TCCS. 4.9.4 The performance of TCCS is dependent on configuration of end points.
Therefore the configuration shall be password protected. Any change in configuration shall be logged with date and time stamp.
4.9.5 Call server shall have following protocol support for secure configuration 4.9.5.1 SSHv2 for secure sessions. 4.9.5.2 SSLv2/v3 for secure HTTP session.
Page 10 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
4.9.6 The communication server should have secure access mechanism for legitimate users only. It shall have Syslog file for intrusion management and it shall keep records or logs regarding the following:
4.9.6.1 Connection (who is connected and at what time) 4.9.6.2 Unauthorized attempts to enter the system 4.9.6.3 History of system commands 4.9.6.4 Kernel and registration of daemons used on devices.
4.9.7 The communication server shall allow communication only with trusted hosts like IP phones, gateways, NMS stations etc.
4.9.8 IP telephones shall have anti ARP spoofing and anti ARP Cache poisoning protection features.
4.10 The configuration profile of each subscriber shall be stored at centralized place and uploaded through NMS or call server while replacing these phones. The above functionality can be provided by any other means (protocol) and in such case the vendor shall provide its details.
4.11 All the gateways and servers shall be 19 inch rack mountable. 4.12 Communication server, IP telephones, gateways and console shall provide for
voice frame marking at layer 2 as per 802.3 p / Q and at layer 3 as per ToS / DiffServ.
4.13 Fixed and dynamic assignment of the IP address support by DHCP for IP Phones shall be possible. The call control servers and gateways may use fixed addresses to avoid performance problems and service outages due to undesired addressing scheme changes.
4.14 The configuration and provisioning shall be possible only from defined network or IP, however web based performance monitoring or status view shall be permitted across the network with user authentication.
4.15 All the devices working on 230 V AC nominal supply shall work in the voltage range from 200 V AC to 240 V AC with nominal frequency of 50 Hz.
4.16 The devices working on -48 V DC shall be able to work in the range -40 V Dc to - 60 V DC.
4.17 After disconnection of power supply to any or all system components (Servers and endpoints) and its subsequent restoration, the system shall return to normal working condition without any manual intervention. The entire user specific configuration on the phone set shall be stored centrally and restored if there is a reset or power down or Preconfigured Authorized Set/ equipment with the same IP in the network is replaced with the defective set / equipment.
4.18 The vendor road map for upgrading TCCS from IPv4 to IPv6 shall be available. 4.19 Numbering scheme: The TCCS system shall support flexible numbering scheme
for support up to 8 digit numbering. For subscribers within a TCCS system for a given section, the numbering digits may vary from two to four digits. It shall be possible to have extension numbers of varying digits. The system shall support closed numbering scheme if needed.
Page 11 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
4.20 The TCCS shall have facility to generate call data reports based on caller, called party, date/time range, duration etc. The report shall include time and duration of all calls. It shall be possible to export the reports in formats like pdf or excel or word etc. It shall not be possible to alter the records.
5 Server Block for TCCS:
5.1 Server block shall consist of following minimum elements. 5.1.1 Communication server Block: Comprising all the necessary components
required for meeting call control and conferencing requirements. The Minimum Hardware requirements are as given below unless otherwise specified by the purchaser:
Sr. No.
Specification of Embedded Solution
The Server Hardware shall be of reputed brand
The Server Hardware shall be of reputed brand
ii. Hardware Hardware Shall support minimum 100 concurrent calls should be Industrial grade and suitable for 24x7 operation
Hardware Shall support minimum 100 concurrent calls should be Industrial grade and suitable for 24x7 operation
iii. Processor Intel Xeon Processor There should not be any latency in the system at full load.
Embedded (Freescale / PowerPC or equivalent) processors. There should not be any latency in the system at full load
iv. No. Of Cores 8 or more 8 or more (Combined across all processors )*
v. Frequency 2.1 GHz or higher 800 MHz or higher* for DSP based solution
vi. No. Of Processor 2 2* vii. Memory 32 GB or higher, DDR3/DDR4
SDRAM or latest The system should not add any latency when it operates at full load. Vendors should choose the right size of memory, based on the solution offered.
Minimum 2GB for embedded solutions with Digital Signal Processor The system should not add any latency when it operates at full load. Vendors should choose the right size of memory, based on the solution offered.
viii. Operating System Operating System Windows Server 2016 or Linux or latest
Operating system shall be embedded RTOS or embedded
Page 12 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
Linux or embedded CE or latest ix. LAN/Ethernet 4 x 10/100/1000Mbps ports.
Onboard/ on slot Gigabit Ethernet (RJ45) with Load Balancing and Fail over Support, IPv6 compliant
4 x 10/100/1000Mbps ports. Onboard/ on slot Gigabit Ethernet (RJ45) with Load Balancing and Fail over Support, IPv6 compliant
x. Storage Redundant storage (RAID1 or higher) of suitable capacity Minimum 1TB (For the operating system, application and other supported software packages). Server based solutions should use industrial grade SSD drives.
Embedded based systems shall have an equivalent mechanism to implement redundancy. Hot Pluggable SAS HDD, 1 TB, 7200RPM or higher Storage should be on-board for embedded solutions.
xi. RAID Controller SAS RAID Controller with RAID 0/1/5 configuration or better mechanism
SAS RAID Controller with RAID 0/1/5 configuration or better mechanism
xii. System Architecture Non-Blocking Non-Blocking xiii. Power Supply Redundant- Hot swappable
power supply. Redundant Hot-swappable power supply.
xiv. Fan Configuration Redundant Hot-swappable Fan
Redundant Hot-swappable Fan
xv. Chassis Type 19” Rack mountable with sliding rails and fittings to install into a Rack.
19” Rack mountable with sliding rails and fittings to install into a Rack.
*Embedded solution shall meet system requirement and performance at full load
5.1.2 NMS Server: The Minimum Hardware requirements are as given below
unless otherwise specified by the purchaser:
S.N. Parameter Specification i. NMS Server The NMS Server Hardware shall be of reputed brand. ii. Processor Intel Xeon Processor iii. No. of Cores 4 iv. Frequency 2.1 Ghz or higher v. Cache 8 MB vi. No. of Processors 1 vii. Memory 16 GB or higher, DDR3/DDR4 SDRAM viii. Operating System Windows Server 2016 or latest or Linux with
minimum 3 Client licenses
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
ix. LAN/ Ethernet Onboard / on slot Gigabit Ethernet ((4x1 Gbe RJ45) with Load Balancing and Fail over Support, IPv6 compliant
x. Hard Disk Drive 1TB HDD
xi. RAD Controller SAS RAID Controller with RAID 1 configuration xii. USB/PS/2 mouse &
Keyboard Required
xiii. Power Supply Redundant Hot-swappable power supply. Works on 230VAC and -48V DC simultaneously. If one fails the other takes care of system functioning without any interruption
xiv. Fan Configuration Redundant Hot-swappable Fan xv. Chassis Type 19” Rack mountable with sliding rails and fittings to
install into a Rack. 5.1.3 Voice Record Server:
The Minimum Hardware requirements are as given below unless otherwise specified by the purchaser:
S.N. Parameter Specification
i. Voice Record Server The Voice Record Server Hardware shall be of reputed brand.
ii. Processor Intel Xeon Processor iii. No. of Cores 10 iv. Frequency 2.1 Ghz v. Cache 20 MB vi. No. of Processors 2 vii. Memory 32 GB or higher, DDR3/DDR4 SDRAM
viii. Operating System Windows Server 2016 or latest or Linux with minimum 3 Client licenses
ix. LAN/ Ethernet Onboard/ on slot Gigabit Ethernet ((4x1 Gbe RJ45) with Load Balancing and Fail over Support, IPv6 compliant
x. Hard Disk Drive Hot Pluggable SAS HDD, 4TB & Minimum 7 days storage capacity, 7200RPM
xi. RAID Controller SAS RAID Controller with RAID 1 configuration
xii. USB/PS/2 mouse & Keyboard Required
xiii. Power Supply Redundant Hot-swappable power supply. Works on 230VAC and -48V DC simultaneously. If one fails the other takes care of system functioning without any interruption.
xiv. Fan Configuration Redundant Hot-swappable Fan xv. Chassis Type 19” Rack mountable with sliding rails and fittings to
install into a Rack.
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
5.1.4 Other servers required to meet the requirements of this specification
(application etc.). 5.2 Redundancy:
5.2.1 Communication server block shall be provided with 1+1 or 1:1 redundancy. The Redundant server block shall be capable of working either in Active – standby mode or in load sharing mode. However, the individual server block shall be able to take full load.
5.2.2 It shall be possible to deploy the standby server at geographically different location in different subnet.
5.2.3 During changeover, the one to one and conference calls may drop. However the subscriber shall be able to setup the one to one call quickly (within 60 second) and conference call again within 5 minutes. A suitable mechanism shall be implemented for changeover to minimize the downtime within this limit.
5.3 The hardware for these servers shall be Industrial grade from reputed vendors suitable to run 24 x 7 in an environment which may not have un-interrupted air conditioning. It shall have protected HDD’s via RAID1 scheme or better and redundant hot-pluggable PSUs.
5.4 The servers shall be 19 inch rack mountable. The server/ servers shall work on - 48V DC (working in the range -40 to -60 V DC). In case of use of 230 V AC systems, UPS of adequate capacity working on -48 V DC shall be supplied to ensure interruption free working of servers. The UPS should be preferably 19” rack mountable. -48 V DC supply shall be arranged by the purchaser.
6 Communication Server Block:
6.1 It shall be core component of the architecture and shall manage all communications of all the controls.
6.2 It shall have Hardened Operating System with inbuilt firewall allowing only necessary services. As part of hardening, the following minimum requirements shall be met:
6.2.1 Closing unnecessary Network ports and disabling Run level system services. 6.2.2 Controlling system access from servers and Networks including the use of
TCP wrapper. 6.2.3 Password management for the system (accounts access) is available by
default. 6.2.4 Unused services to be removed and listening ports numbers to be reduced. 6.2.5 There should not be any resource tool for remote file and print sharing. 6.2.6 Hard disc/ storage sharing should be restricted. 6.2.7 It should resist DoS attack. Vendor shall submit details of built in DoS attack
resistance mechanism.
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
6.3 It shall have 10/100/1000 Mbps Dual Ethernet termination capability for fault tolerant operation.
6.4 The communication server shall be able to function without any degradation of services even in the absence/fault of redundant server.
6.5 Number of control circuits is different in different divisions. The system shall support control circuits as per the requirement of the purchaser.
The system shall allow creating unlimited subscribers. However one communication server shall support minimum 100 concurrent calls.
6.6 The system shall have IP/SIP trunking to interconnect with other TCCSs. 6.7 The TCCS system consists of various types of Gateways. The communication
server block shall be able to support connectivity with all types of gateways. The exact number of gateways will be as per purchaser’s requirement subject to total ports on the gateways are less than the server capacity as per clause 6.5.
6.8 The system shall support a minimum of 100 concurrent calls in one communication server. The supplier shall give an undertaking in this regard.
6.9 The Communications Server software shall natively support Video communications along with Audio, and should support Video conference calls using additional Hardware (like MCU).
6.10 It shall support Train Control communication System implemented on a distributed IP network having Analog telephone terminated on gateways at remote locations to connect via IP network.
6.11 It shall have either auto call back feature (also known as CCBS, call completion on busy subscriber) or the called telephone shall indicate such call attempt as “missed calls”.
6.12 It should be possible to define high priority for a subscriber or group of subscriber. These subscribers will have priority when there is any resource crunch as per user requirement.
7 Voice Recording Server:
7.1 It shall record all conversations, taking place via TCCS server and involving various controllers. It shall have capability to record all conversations i.e. controller communication, way station communication, Emergency communication, two wire / four wire analog control communication, FXS/FXO user communication etc. as per user requirement.
7.2 It shall be possible to search specific recorded conversation by caller, called party, time range or date range criteria.
7.3 It shall record the conversation for at least 7 days & specified capacity of the storage device unless otherwise specified by the purchaser. For disk redundancy purpose RAID 1 or better mechanism shall be used.
7.4 Voice logger must support Alarm sending via SNMP traps or similar means to a NMS for the notification of events like recording not activated etc.
7.5 GUI shall be provided to retrieve the recordings and for playback.
Page 16 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
7.6 The desktop client PC and The Portable Maintenance Terminal for Voice record server: The recording system shall provide access of the records to the desktop client PC and The Portable Maintenance Terminal clients to provide for basic record filtering, record replay or export in the MP3 format or any other format. Necessary client software shall be supplied and loaded in the desktop client PC and the Portable Maintenance Terminal. The client PC shall also be kept inside 19 inch rack under lock and sealed condition as desired by the user. The desktop client PC and The Portable Maintenance Terminal shall be supplied from reputed brand like IBM, HP, Dell unless otherwise specified by the purchaser. The Minimum hardware configuration of the desktop client PC and the Portable Maintenance Terminal are provided in clause 8.8 and 8.9 respectively.
7.7 It shall not be possible to delete any records or to format the hard disk/ storage by conventional methods of the voice recording server.
7.8 When the capacity of main storage media is exhausted or the specified recording hours are complete, (whichever is more) there shall be automatic roll back i.e., the earliest records are overwritten with the latest record.
8 Network Management and Monitoring System :
8.1 General requirement 8.1.1 The management platform shall provide a web based monitoring of the TCCS
from any PC with an Internet browser. 8.1.2 For web based login user id and password shall be provided to restrict the
access to the authorized persons only. It shall provide role based access like read only access or read/write access.
8.1.3 The network management system shall support SNMPv2c protocol and MIB2 or latest standard Protocol / Interface as northbound interface for any Umbrella NMS (if any planned at later date).
8.2 Topology
8.2.1 The NMS shall provide a topological view of VoIP infrastructure of TCCS (gateways, IP telephones, servers and console).
8.2.2 The different icons shall correspond to different element categories. These icons must be synchronized with the alarms application in real time, and various alarms shall also be indicated on the topology diagram showing severity of alarm with different colors of icons.
8.3 VoIP monitoring and quality management The system shall provide measurement of parameters related to quality of VoIP calls.
8.3.1 The system shall generate the following reports related to quality of VoIP Calls:
8.3.1.1 The data traffic generated on the network. 8.3.1.2 Performance of the system in terms of QoS including parameters like
packet delay, jitter, Packet drop, Mean Opinion Score etc. The limits
Page 17 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
of QoS Parameters shall be within the limit of specified international standard for VoIP Network.
8.3.1.3 The capacity utilization of various component of the VoIP System. 8.3.1.4 Any other reports as necessary. 8.3.1.5 Software/platform used for report generation shall be of
internationally accepted standard.
8.4 Management of the system faults and events. 8.4.1 The system shall provide centralized fault summary information. 8.4.2 The management system shall collect and store all the events generated by
the elements, servers and by the management system itself. 8.4.3 These events shall consist of faults, alarms and other events. 8.4.4 It shall be possible to store, search and filter these events. 8.4.5 The filtering of events shall be on the criteria of element id, time range, date
range and severity. Based on the filtering, it shall be possible to generate and print the reports.
8.4.6 Notification of events: The system shall notify an event depending upon the severity level by sending an e-mail or SMS or both. It shall be possible to specify events which would require sending of email or SMS or both to a person or persons. The system shall send the SMS via e mails using SMTP protocol to an event notification gateway. Audio visual alarm shall also be provided.
8.4.7 Mobile application may be provided for maintainers to receive notification of events and maintain history of events on Mobile if required by the purchaser. The system shall have provision to notify events to user through Mobile application over mobile data network.
8.4.8 The alarms should be categorized according to the four-level of severity, and identified by different colors to facilitate direct attention to specific categories. Each Alarm must include at least:
8.4.8.1 The severity level 8.4.8.2 The managed object 8.4.8.3 The notification time and date
8.4.9 Statistics: It shall give list of all the major or minor alarms for a particular period for analysis purpose.
8.5 Configuration Management:
8.5.1 All IP telephone, consoles and other elements of the system shall be remotely provisioned/ configured automatically when powered ON. For this, minimum basic configurations for these devices shall be done before use at site.
8.5.2 The IP phones, consoles and other elements of the system shall fetch the configuration from the centralized location based on their respective MAC ID or any other unique id which could not be changed by user.
8.5.3 The provisioning system shall be able to configure remote IP phones consoles and other elements of the system by selecting type of device. The extension numbers and user privileges shall be possible to be configured from centralized location only.
Page 18 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
8.5.4 It shall provide for configuration backup and restore for individual elements of TCCS.
8.5.5 The configuration shall be possible only from defined list of network or from portable maintenance terminal.
8.6 The desktop client PC and The Portable Maintenance Terminal: Configuration
and device status monitoring shall be possible from the desktop client PC and the Portable Maintenance Terminal.
8.7 The Desktop client PC and The Portable Maintenance Terminal:
8.7.1 All above features of the network management and monitoring system shall be accessed through the desktop client PC and The Portable Maintenance Terminal.
8.7.2 The NMS shall support more than one Desktop client PC and The Portable Maintenance Terminal.
8.7.3 The Desktop client PC and The Portable Maintenance Terminal shall run the client applications of NMS for TCCSs of other sections also, so that the telecom maintainer can monitor the TCCS of various sections from one PC itself.
8.7.4 Any additional hardware/ software for the Desktop client PC and the Portable Maintenance Terminal shall be provided for satisfactory working over and above the specified requirement.
8.8 The Desktop Client PC
The desktop client PC shall perform the functions including
8.8.1 The client PC for Voice recording server as per clause 7 of the specification. 8.8.2 The desktop client PC for NMS Server as per clause 8 of the specification. 8.8.3 Any other function as per specification. 8.8.4 The minimum specification of the desktop client PC is as under.
8.8.4.1 The client PC shall be from reputed brand like IBM, HP, Dell unless otherwise specified by the purchaser
8.8.4.2 Monitor: Minimum 17 inch LCD 8.8.4.3 Processor : Intel Core i7 or better 8.8.4.4 Dual Ethernet cards 10/100/1000 Mbps 8.8.4.5 HDD: 1 TB 8.8.4.6 RAM : 6 GB 8.8.4.7 Operating System: Standard modern desktop based OS such as
Windows with latest licensed version 8.8.4.8 UPS for 30 minutes backup 8.8.4.9 DVD writer 8.8.4.10 Printer A3 size inkjet/laser or as per user requirement.
Page 19 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
8.8.4.11 Any additional hardware/ software for the desktop client PC shall be provided for satisfactory working over and above the specified requirement.
8.9 The Portable Maintenance Terminal
The portable Maintenance Terminal shall perform the functions including
8.9.1 The client PC for Voice recording server as per clause 7 of the specification. 8.9.2 The portable Maintenance Terminal for NMS Server as per clause 8 of the
specification. 8.9.3 Any other function as per specification. 8.9.4 The minimum specification of the Portable Maintenance Terminal is as under.
8.9.4.1 The Portable Maintenance Terminal shall be from reputed brand like IBM, HP, Dell unless otherwise specified by the purchaser
8.9.4.2 Monitor :Minimum 14 inch LCD/LED 8.9.4.3 Processor : Intel Core i7 or better 8.9.4.4 HDD: 1TB 8.9.4.5 RAM : 4GB 8.9.4.6 Operating System: Standard modern OS such as Windows with latest
licensed version 8.9.4.7 DVD RW 8.9.4.8 Inbuilt Speaker, 3 USB Ports, 1 Ethernet Port 10/100/1000, Wi-Fi, Built
in Camera, Bluetooth, Microphone, HDMI Port and one serial port if required by the purchaser.
9 Controller Console Equipment:
The controller Console Equipment shall be of Industrial grade. The controller Console Equipment shall be configurable as Section Controller, Emergency Controller and other controller console based on User’s requirement. The Section Control Equipment consist of Touch Screen LCD with console CPU, Speaker, Power Amplifier, Microphone, Handset, Mouse, Keyboard/Keypad for Key Dialing, soft Keys and Hot Keys for selective dialing. All these components shall be of Industrial Grade. These components can be integrated either in one customized unit or may be separate attachable components as per user requirement. The touch screen panel shall have the following minimum specification;
9.1 The Controllers console shall have an industrial grade touch screen panel having good touch sensitivity.
9.2 Minimum Touch Screen panel specification: 9.2.1 It shall have TFT liquid crystal display, minimum display, minimum size – 15.6
inch diagonal and wide screen. 9.2.2 Screen resolution shall be 1920 x 1080 9.2.3 Brightness shall be 400 cd/m2
Page 20 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
9.2.4 Contrast ratio must be 500:1 or better 9.2.5 Viewing Angle - 80 degree in all direction 9.2.6 Touch screen type shall be 5 wire resistive
9.3 The console shall have software emulated programmable buttons and custom functional fields. The size of buttons and fields shall be flexible. The functions of the button shall be programmable.
9.4 It shall be possible to send notifications in the form of messages. These messages can be prewritten messages required to be sent to predefined group. These messages could be selected and sent as email to predefined group through the IP based event notification gateway. The protocol for sending e mail to gateway shall be SMTP.
9.5 It shall have programmable buttons on touch screen for direct calling way side stations or any other pre-assigned subscriber. These buttons may be organized in layered frames (minimum 2 layers for providing total minimum 100 buttons )
9.6 The soft buttons will provide basic subscriber information like subscriber’s name, and present state of subscriber. The possible states are free, busy, outgoing call in progress and ring back tone, reachable, not reachable where such information is available for subscriber.
9.7 Soft buttons shall be provided for direct dialing of pre-defined groups of subscribers.
9.8 It shall have buttons for various subscriber services like directory services, notification service, key board, opening of various windows.
9.9 The display also shows a status row indicating date, time, user identity and availability of main network.
9.10 There shall be a conference window to show all the current participants of the conference.
9.11 There shall be a dialing window showing dialing pad. 9.12 It shall be possible to attach external keyboard/keypad and mouse to be used for
editing and for using as dial pad. 9.13 The touch screen and the keyboard for controller’s console shall be spill proof. 9.14 The console shall have phone type handset with press to talk (PTT) button also
for communication under noisy conditions or where privacy on controller side is needed. Once the handset is off-hook, audio shall automatically switch to handset. Once the handset is on-hook audio shall automatically switched to Loudspeaker.
9.15 The console shall have an embedded gooseneck Microphone or interface for an external gooseneck Microphone.
9.16 Microphone specifications: 9.16.1 The microphone shall be matched with the console to give the acceptable
performance when speaking from a distance of minimum 50cm. 9.16.2 Protection against RF disturbance from mobile phones. 9.16.3 Cardioid polar patterns. 9.16.4 Provided with status indicator with LED.
Page 21 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
9.16.5 It shall be kept on table and shall remain stable during use. 9.16.6 The microphone shall be electret condenser microphone with maximum
input 120dB sound pressure level(SPL) 9.16.7 It shall have logarithmic audio amplifier with programmable gain , ambient
noise suppression (noise gating) and compression ratio. 9.17 Speaker Specification:
9.17.1 The console shall have an embedded amplifier and loudspeaker. Alternatively loudspeaker (with left and right speaker of 10 watt each or better) with 150 Hz to 6800 Hz minimum band shall be supplied. The loudspeaker amplifier shall have with programmable gain, separately adjustable for left and right speakers.
9.17.2 Switch to loudspeaker communication is controlled either via SW controls on the touch screen or should be automatic on detecting disconnection of headset. The system shall be connected to loudspeaker by default.
9.17.3 Loudspeaker electronics shall be completely shielded for protection against electromagnetic interference.
9.17.4 Optional Central loudspeaker of amplifier shall be capable to boost lower frequencies.
9.17.5 For embedded speaker, the Console shall have LED status indicator for current speaker volume level.
9.18 Input power supply for Controller’s Console/ Equipment: 9.18.1 The Controller’s Console/Equipment shall work either on 230 V AC or on -48
V DC (Nominal). 9.18.2 In case of 230 V AC working, suitable UPS to provide atleast 1 Hour backup
for console, microphone and loud speaker shall be supplied or it shall have internal battery to provide backup of atleast 1 hour including for speaker and microphone. On disruption of mains supply to the UPS, the ongoing conference call of the controller shall not be disconnected.
9.19 Communication protocol: SIP or H.323 9.20 Codecs G 711A law, G.722 and either G.729a or iLBC. 9.21 Network protocol: TCP/IP, RTP/TRCP, HTTP, ARP/RARP, NTP. 9.22 It shall provide feature of recording on going conversation. 9.23 It shall show current time in 24 hrs. format. 9.24 It shall have features of Voice activity detection, silence suppression, comfort-
noise generation, Echo cancellation, error concealment, adaptive Jitter Compensation as applicable. It shall be possible to disable VAD and/ or silence suppression on selected end points.
9.25 It shall show call history (received calls and outgoing calls). 9.26 It shall have dual Ethernet 10/100/1000 mbps ports. 9.27 It shall provide feature of phone book (directory) search. 9.28 The console shall have minimum storage of 128 GB SSD (Solid State Disk). 9.29 It shall have industrial grade components, Ethernet redundancy, redundant
internal audio and controller interfaces.
Page 22 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
10 Test Room Console/Equipment:
10.1 Test room console shall be able to monitor, communicate & Test all the
controller’s console, way station equipment in the division for testing and maintenance purpose of VoIP TCCS system. Test room console shall be able to view all section controllers and associated ASM equipment to maintain and support.
10.2 The specification of Test room Equipment/console shall be same as Controller Console Equipment.
11 Way side IP control Telephone/Equipment:
An IP telephone with handset to be used by the ASM for communication with section controller and other controllers shall be provided. The ruggedized industrial grade IP Telephone shall be from reputed manufacturers. The specification of Way side IP control telephones/Equipment shall be as given below.
11.1 Communication protocol SIP or latest platform. 11.2 PoE as per IEEE 802.3af standard class 2 or better and 230 V AC (through
adapter). 11.3 Network protocols; TCP IP, UDP, RTP, RTCP, HTTP, ARP, RARP, NTP, ICMP. 11.4 Audio compression: G.711A law, G 722 and either G 729a or iLBC. 11.5 It shall have features of Voice activity detection, silence suppression, comfort-
11.6 Minimum 8 programmable keys for configuration for speed dialing. Dial rules shall be as per user requirements and keys shall be programmable accordingly.
11.7 Full Duplex. 11.8 Hands free operation as per User requirements. In case of hands free operation,
Internal Microphone or External Gooseneck Microphone with specification in clause No. 9.16 may be acceptable as per user requirements.
11.9 Dialpad and Redial button. 11.10 Caller ID display 11.11 Call History Received calls, outgoing calls and missed calls. 11.12 Phone Book, Volume Adjustment, phone book search. 11.13 Distinctive ring tone for calls from a specific subscriber. 11.14 Dual Ethernet ports in switch mode 10/100 Mbps auto sensing shall be provided. 11.15 It shall show current time in 24 hrs. format.
12. Specification for Gateways to be provided at HQ (HQGW):
Note: In place of separate devices only one common device having all the types/combinations of following interfaces can be supplied. If one common device is supplied, it shall have all the features mentioned for each of the interfaces. In
Page 23 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
addition it shall have Dual 10/100/1000 Mbps Ethernet ports as network interface instead of 10/100 Mbps Ethernet ports. The device shall have sufficient resources to allow simultaneous use of all the ports.
12.1 FXO gateway:
12.1.1 The gateway should be modular. This gateway is required to extend the Number from Railway Exchange to required location through VoIP server.
12.1.2 The gateway shall have 8 or 16 or 32 FXO ports as per requirement of purchaser.
12.1.3 Communication protocol: SIP 12.1.4 It shall have features of Voice activity detection, silence suppression,
comfort-noise generation, Echo cancellation, error concealment, adaptive Jitter Compensation as applicable. It shall be possible to disable VAD and/ or silence suppression on selected end points.
12.1.5 Network protocols : TCP IP, UDP, RTP, RTCP, HTTP, ARP, RARP, NTP, ICMP 12.1.6 Power supply: It shall work on nominal -48 V DC supply. 12.1.7 Network Interface: Dual 10/100/1000 Mbps Ethernet ports. 12.1.8 Codecs G.711 A-Law and either G.729a or iLBC.
12.2 DTMF Gateway:
This gateway shall be used for providing interoperability for communicating with existing DTMF waystation control Telephone and through VOIP based Controller Equipment.
12.2.1 The gateway shall be available in capacities of 4 ports for each section controller.
12.2.2 Communication protocol: SIP. 12.2.3 It shall have features of Voice activity detection, silence suppression,
comfort-noise generation, Echo cancellation, error concealment, adaptive Jitter Compensation as applicable. It shall be possible to disable VAD and/ or silence suppression on selected end points.
12.2.4 Network protocols: TCP IP, UDP, RTP, RTCP, HTTP, DHCP, NTP, ICMP. 12.2.5 Power supply: It shall work on nominal -48 V DC supply. 12.2.6 Network Interface: Dual 10/100/1000 Mbps Ethernet port. 12.2.7 Codecs G.711 A-Law and either G.729a or iLBC.
12.3 Event Notification Gateway:
12.3.1 The system alarm or events received from NMS shall be sent in the form of SMS or email or data with the help of event notification gateway. For sending SMS (from NMS, controller’s console and voice record server etc.) “Direct to Mobile SMS gateway” shall be used.
12.3.2 It shall support SMTP protocol for emails, AT command for GSM modem interface over serial port.
Page 24 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
12.3.3 The SMS, data and email shall be implemented as push notification for sending events to relevant users.
12.3.4 Android based mobile application shall be provided to the user for viewing all notification in readable formats for better management (if require by the purchaser). Since SMS is not a reliable mechanism as delivery of massages cannot be acknowledged. Hence, events shall be pushed in the form of data to the application users over mobile data network. However, GSM modem shall be provided alongwith the gateway for sending events/faults via SMS.
12.3.5 In case of SMS delivery mechanism SIM card connection shall be provided by the purchaser.
12.3.6 It shall provide GUI for user management, assigning allocation of devices/fault types to predefined users.
12.3.7 It shall be possible to interface with NMS server over standard protocol for application programmable interface (API).
13 Specification for Gateways to be provided for Emergency Communication (ECGW):
13.1 This gateway shall be provided at HQ and/or way side stations for the purpose of providing interface to emergency communication circuit working on 0.9 mm conductor diameter underground twisted pair quad cable.
13.2 This gateway shall have minimum 4 number 4 wire ports. Two ports to be used for connecting 4 wires of emergency communication circuits coming from either side of the station. At HQ only one of the port shall be used and connected to the circuit coming from the next station.
13.3 Since there is no off hook/ on hook condition on the emergency phone, the ports may be required to be active all the time. However, IP packets shall be generated only when there is actual voice communication taking place.
13.4 The gateway shall be compatible with 4/6 quad cable. The transmission characteristic of 4/6 quad cable shall be as defined in RDSO specification IRS: TC 30-05 with latest Revision and amendments.
13.5 The gateway shall be compatible with Emergency phone which shall be plugged at site. The emergency telephone shall be as per RDSO specification IRS: TC 78- 2000 with latest revision and amendments.
13.6 The gateway shall be able to work satisfactorily when the emergency telephone is plugged at any distance up to at least 10 km. The transmission parameters of the port of gateway connected to quad cable shall be specified by the vendor.
13.7 Communication protocol: SIP 13.8 It shall have features of Voice activity detection, silence suppression, comfort-
13.9 Network protocols : TCP IP, UDP, RTP, RTCP, HTTP, ARP, RARP, DHCP, NTP, ICMP 13.10 Power supply: It shall work on nominal -48 V DC supply. 13.11 Network Interface 10/100 Mbps Ethernet port autosensing.
Page 25 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
13.12 Codecs G.711 A-Law and either G.729a or iLBC.
14 Interoperability: 14.1 The subscriber of one TCCS shall be able to make normal telephony call to
subscriber of other TCCS. The system shall act as a tandem switch also to route the calls from the Railway exchange received through FXO port to TCCS systems of other sections and vice versa.
14.2 For sending SMS (from NMS, controller’s console and voice record server) “Direct to Mobile SMS gateway” shall be used. TCCS system shall follow standard protocol (SMTP) for sending emails to the event notification gateway.
14.3 The PC provided for a section as Desktop client PC for voice record server can be used as Desktop client PC for voice record servers of other section’s TCCS.
15 Environmental Tests:
15.1 Controller Console Equipment, Emergency Communication Gateway (ECGW) , Way side IP control Telephones/Equipment , DTMF Gateway & FXO Gateway shall meet following environmental parameters.
15.1.1 Operational temperature: 0°C to 50°C. 15.1.2 Operational Humidity: 10% to 95% non-condensing. 15.1.3 Storage temperature range: -5°C to 60°C.
15.2 Server elements & Event Notification Gateway shall meet following requirements:
15.2.1 Operational temperature: 0°C to 40°C. 15.2.2 Operational Humidity: 10% to 90% non-condensing.
Note: A test certificate and test report shall be furnished by the supplier. The test agency conducting the environmental tests shall be an accredited agency and details of accreditation shall be submitted by the firm to Purchaser. The details of accreditation shall be as per existing RDSO norms.
16 EMI and EMC requirement and Electrical Safety:
16.1 EMC Requirements: The servers, controller Console Equipment, Way side IP control Telephones/Equipment, Emergency Communication Gateway, DTMF Gateway, Event notification Gateway shall conform to the EMC requirements as per the following standards relevant to that particular equipment. A test certificate and test report shall be furnished by the supplier. The test agency conducting the tests shall be an accredited agency and details of accreditation shall be submitted by the firm to Purchaser. The details of accreditation shall be as per existing RDSO norms.
16.1.1 Conducted and radiated emission: As per “CISPR 22 -Limits and methods of measurement of radio disturbance characteristics of Information Technology Equipment". To comply with Class A of CISPR 22 {2006}.
16.1.2 Immunity to Electrostatic discharge: As per IEC 61000-4-2 "Testing and measurement techniques of Electrostatic discharge immunity test". For both Contact discharge and Air discharge Or equivalent CISPR 24.
Page 26 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
16.1.3 Immunity to radiated RF: As per IEC 61000-4-3 "Testing and measurement techniques-Radiated RF Electromagnetic Field Immunity test" Or equivalent CISPR 24.
16.1.4 Immunity to fast transients (burst): As per IEC 61000-4-4 "Testing and measurement techniques of electrical fast transients/burst immunity test” For both AC/DC power lines and data / telecom lines; or equivalent CISPR 24.
16.1.5 Immunity to surges: As per IEC 61000-4-5 “Testing & Measurement techniques for Surge immunity test" for both power line and telecom ports for both line to ground and line to line coupling, or equivalent CISPR 24.
16.1.6 Immunity to conducted disturbance induced by Radio frequency fields: As per IEC 61000-4-6 “Testing & measurement techniques-Immunity to conducted disturbances induced by radio- frequency fields" or equivalent CISPR 24.
Note 1: A test certificate and test report shall be furnished by the supplier. The test agency conducting the EMC tests shall be an accredited agency and details of accreditation shall be submitted by the firm to Purchaser. The details of accreditation shall be as per existing RDSO norms.
Note 2: For checking compliance with the above EMC requirements, corresponding relevant Euro Norms of the above IEC/CISPR standards are also acceptable. The details of IEC/CISPR and their corresponding Euro Norms are as follows:
IEC/CISPR IEC/CISPR
CISPR 11 EN 55011 CISPR 22 EN 55022 IEC 61000-4-2 EN 61000-4-2 IEC 61000-4-3 EN 61000-4-3 IEC 61000-4-4 EN 61000-4-4 IEC 61000-4-5 EN 61000-4-5 IEC 61000-4-6 EN 61000-4-6
16.2 Electrical Safety: The Servers, controller Console Equipment , Way side IP control telephones/Equipment, Emergency Communication Gateway, DTMF Gateway, Event notification Gateway shall conform to EN 60590 or IEC 60950 or UL 60950 or CSA60950 or equivalent IS 13252.
NOTE: A test certificate and test report shall be furnished by the supplier. The test agency conducting the Electrical Safety tests shall be an accredited agency and details of accreditation shall be submitted by the firm to Purchaser. The details of accreditation shall be as per existing RDSO norms.
17 Tests and Performance Requirements:
17.1 The System Provider shall submit detailed test reports for tests done on various equipments proposed to be used, covering the parameters as given in Functional Requirements, Technical Requirements, Environmental Requirements and EMI&EMC Requirements of this specification.
17.2 In case Purchaser so desire any other test on the equipment shall be conducted by System Provider in presence of Purchaser’s Representative to ascertain conformance.
Page 27 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
17.3 At least one equipment of each type should be tested for functional parameter by System Provider in presence of Purchaser’s Representative. The tests shall be conducted as per Test Procedure proposed by manufacturer/supplier duly reviewed and approved by Purchaser.
17.4 The equipments tested as above shall be integrated to form the complete system by System Provider to demonstrate the workability of complete integrated system as an initial demonstration.
17.5 Once the workability of system has been proved as above, installation in the field may be carried out by the System Provider in consultation with Purchaser.
17.6 System Acceptance Test: On completion of installation of Complete System in section, System Acceptance Test shall be carried out as per System Acceptance Test Procedure proposed by system provider duly reviewed and approved by Purchaser.
18 Instruction Manual, Measuring Instruments & Spares:
18.1 System Provider shall submit following documents for each Sub-System/Module as supplied by Sub-System Provider/Manufacturer alongwith each System. These documents shall be submitted in 2(two) Hard Copy and 1 (one) CD.
18.1.1 Operating Instruction Manual 18.1.2 Maintenance & Troubleshooting. 18.1.3 Technical manual including installation check list and detailed configuration
instructions. 18.2 System provider shall submit complete details of the test and measuring
equipments required for testing and servicing to the purchaser. 18.3 System provider shall submit list of the recommended spares for the system.
19 TRAINING: 19.1 Onsite training or as specified by the purchaser shall be provided to the Railway
staff which shall include complete assembly of the system through the use of various modules, integration of hardware with software and complete operation of the system.
19.2 Sets of training manual in two hard copies and two soft copies containing details of technical specifications, installation and commissioning, trouble shooting & maintenance schedule etc. or as specified by the purchaser shall be supplied along with the equipment.
20 TEST REQUIREMENTS:
20.1 Conditions of Tests:
20.1.1 Unless otherwise specified all tests shall be carried out at ambient atmospheric conditions.
20.1.2 A test certificate and test report shall be furnished by the supplier. The test agency conducting the environmental tests, EMI/EMC Test and Electrical Safety Test shall be an accredited agency and details of accreditation shall be submitted by the firm to Purchaser. The details of accreditation shall be as per existing RDSO norms.
Page 28 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
20.1.3 Inspection and testing shall be carried out to the effect that all requirements of this specification are complied with.
20.2 Type Test: 20.2.1 One complete system consisting of all type of Servers, Gateways, Section
Controller Console Equipment and Way station Control Telephone for ASM shall be subjected to following tests alongwith test applicable in the specification for the item:
20.2.1.1 Visual Inspection. 20.2.1.2 General and functional Requirement as per Clause No. 3 & Technical
Requirement as per Clause No. 4. 20.2.1.3 Environmental/Climatic Tests as per Clause No. 15. 20.2.1.4 EMI/EMC Test as per Clause No. 16. 20.2.1.5 Technical specification of the item as per respective clauses.
20.2.2 Only one complete system shall be tested for this purpose. The system shall successfully pass all the type tests for proving conformity with this specification. If any one of the equipment fails in any of the type tests, the purchaser or his nominee at his discretion, may call for another improved/modified equipment alongwith details of Corrective and preventive action taken by the supplier. The improved/modified equipment shall pass all the tests.
20.2.3 Any other tests shall be carried out as considered necessary by the inspecting authority.
20.3 Acceptance Test: 20.3.1 Visual Inspection on all the items. 20.3.2 The following shall constitute the acceptance tests which shall be carried out
by the inspecting authority for the purpose of acceptance on randomly selected 10% of items offered for inspection by the supplier from the lot (minimum 1 each type of item) offered:
20.3.3 One complete system consisting of all type of Servers, Gateways , Section Controller Console Equipment & Way station Control Telephone for ASM shall be tested for General and functional Requirement as per Clause No. 3 & Technical Requirement as per Clause No. 4. alongwith test applicable in the specification for the item.
20.3.4 Any other tests shall be carried out as considered necessary by the inspecting authority.
20.3.5 System Acceptance Test: On completion of installation of Complete System in a given section, System Acceptance Test shall be carried out as per System Acceptance Test Procedure proposed by system provider duly reviewed and approved by the Purchaser.
20.4 Routine Test /Factory Acceptance Test (FAT):
Page 29 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
20.4.1 Routine test /Factory Acceptance test (FAT) shall be conducted by Supplier/Original Equipment manufacturer (OEM) on every equipment and the test results shall be submitted to the inspection authority before inspection.
20.4.2 Firm shall submit the details of make, model and version etc. of each equipment including Software to inspection authority before inspection.
21 QUALITY ASSURANCE: 21.1 All materials & workmanship shall be of good quality. 21.2 Since the quality of the equipment bears a direct relationship to the
manufacturing process and the environment under which it is manufactured, the manufacturer shall ensure Quality Assurance Program of adequate standard.
22 MARKING & PACKING: 22.1 The following information shall be clearly marked at a suitable place on each
equipment: 22.1.1 Make and Model/Part No. of Equipment 22.1.2 Serial number of equipment
22.2 The equipment and its sub-assemblies shall be packed in suitable packing so that it can withstand bumps and jerks encountered during transportation.
23 All the provisions contained in ROSO's ISO procedures laid down in Document No. QO-D-7.1-11 dated 19.07.2016 (titled "Vendor-Changes in approved status") and subsequent versions/amendments thereof, shall be binding and applicable on the successful vendor/vendors in the contracts floated by Railways to maintain quality of products supplied to Railways.
Page 30 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
24 Ordering Information:
1 Communication Server 5 and 6 As per purchaser requirement
2 Network Management Server
5 and 8 As per purchaser requirement
3 Voice Recording Server 5 and 7 As per purchaser requirement.
4 The Portable Maintenance Terminal
8.7 & 8.9 Loaded with NMS client Software , Voice Record Client Software alongwith any other required software required to meet the specification requirement or as specified by the purchaser.
5 Desktop client PC 8.7 & 8.8 Loaded with NMS client Software, Voice Record Client Software alongwith any other required software required to meet the specification requirement or as specified by the purchaser.
6 Controller Console Equipment
9 Customized Integrated as single unit or separate attachable components as per purchaser requirement.
7 Test Room Console/ Equipment
10 Customized Integrated as single unit or separate attachable components as per purchaser requirement.
8 Way side IP Telephone/Equipment for ASM with Hands free operation as per User requirements
11 As per purchaser requirement with internal Microphone or Attachable Gooseneck Microphone.
Way side IP Telephone/Equipment for ASM without Hands free operation as per User requirements
11
10 FXO Gateway 12.1 Optional or As per
Page 31 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
SN Item Corresponding Clause
11 Emergency Communication Gateway
12 DTMF gateway 12.2 Optional or As per purchaser requirement
13 Mobile Application for event Notification
8.4.7 & 12.3.4 Optional as required by the purchaser.
Page 32 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
Annexure-1 Definitions of the terms relates to Train Control communication system (TCCS)
(Note: This annexure is for guidance purpose only)
1. Control Office: Control office/s exist in each of the Division for Controlling and
regulating train traffic over a section consisting of several Railway stations.
2. Way stations: For the purpose of train control communication system, the
following are referred to as way station
(a) Railway station
(b) Signal Cabin
(c) Loco shed
(e) Identified offices
(f) Identified residences
3. VoIP based TCCS: VoIP based Train Control Communication System is a
communication system between the control office and various way stations or
in other words it is a communication system to enable communication between
the HQ control telephone provided at control office and way station control
telephones provided at various way stations.
4. Train control communication system has different control circuits. These are
4.1 Section traffic control
4.2 Deputy traffic Control
4.5 Emergency control
4.6 Engineering control
4.8 Signal control
4.9 Telecom control
The above list is not exhaustive and other control circuits may also exists. These
circuits consist of the HQ control phone of the particular controller and way
station control telephones under control of the particular controller.
Page 33 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
In addition to above Remote control is used for remote operation of 25KV AC
traction equipments. Remote control works on SCADA principle.
5. Each control circuit is manned in control office by their respective controller/
official like section traffic controller, traction power controller etc. In this
specification section traffic controller is referred to as “section controller” and
controllers manning other control circuits are referred as “other controllers”.
Term controller refers to both section controller and other controllers.
6. On a division, there are more than one sections and each sectional traffic
control is controlled by a section controller. Each of the section controllers
communicates with a group of way stations in his jurisdiction. For other control
circuits similar arrangement exists.
7. The telephone at control office with each of the controller is called “HQ control
telephone” and the telephone at way stations is called “Way station control
telephone.” In this specification section controller’s HQ control telephone is in
the form of a console and referred to as “section controller’s console”. HQ
control phones of other controllers are referred as other controller’s phone.
Separate way station control telephone are provided for different control
circuits, e.g. the way station control phone of section traffic control, way
station control telephone for traction power control circuit etc. In this
specification, way station control phone of section traffic control is referred as
ASM’s way station control phone or ASM’s way station phone or ASM’s
control phone. The way station telephones of other control circuits are
referred as other way station control phone or other way station phone.
8. Emergency Control Circuit:
8.1 Emergency control circuit is omnibus circuit working on the underground
cable laid in most of the sections. The length of this cable can go up to
20 km or more between two adjacent way stations. The
emergency control circuit is generally a 4-Wire circuit. In normal
case, conversations on this circuit are received by Traction power
controller/ Power controller. However in case of need, Traction Power
controller/ Power controller shall be able to transfer the conversations
on section control circuit.
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
8.2 The underground cable is tapped at intervals of about 1 KM and
terminated on 6-pin socket. The control office (for a given section) can
be contacted by plugging a portable control telephone (4 wire portable
control telephone as per RDSO specification IRS TC 78/2000 with
amendment 1) into any of these sockets provided in that section.
Page 35 of 35
RDSO/ SPN/TC/99/2012 /SPN/ /99/2012
Rev. 2
ANNEXURE-2
Abbreviations
END OF DOCUMENT