TECHNICAL REQUIREMENTS VOICE COMMUNICATION CONTROL SYSTEM 1. SCOPE OF WORK 1.

1 The tender scope includes Supply, Installation, Testing, Training & Commissioning of the IP based Voice Communication and Control System (VCCS) for IGI Airport Delhi. 1.2 The successful bidder/Contractor shall carry out installation of entire H/W, assets interface, S/W and laying of cabling in this tender for VCCS system which may be centralized or distributed in architecture, interfaced to all offered operator positions at defined locations, local/remote leased/non leased E1/E3/MPLS/IP trunk lines, local/remote Analog/IP radio/telephone interfaces, laying and interfacing to non leased ATS Network infrastructure, RCMMS at IGIA airport Delhi. 1.3 Contractor shall also carry out and assist AAI in testing, integration, training & commissioning on the complete offered system against this tender after carrying out successful Site Acceptance Testing (SAT). 1.4 The contractor shall provide the following trainings : On Job Training on Operation of VCCS equipment On Job Training on Maintenance of VCCS equipment Detailed Module level training on System Administration/System Configuration functions/System Recovery at its factory premises. On the job training on as built system layout/supervisory functions. 1.5 The communication media (cable) length as appropriate for installation of complete VCCS shall be brought out in the tender by the bidder/contractor. 1.6 Power requirements for the VCCS equipment and its components shall be furnished by the bidder/contractor. 1.7 Bidder/Contractor shall furnish the list of test equipments required for upkeep and maintenance of the complete VCCS with all types of CWP and H/W, S/W interfaces. 1.8 AAI will not provide any Inter building communication media between the buildings where VCCS along with operator positions is to be installed. This shall include provision of the redundant IP backbone for VCCS system. However, Tenderer shall furnish details of such communication media requirement. 1.9 Contractor shall be responsible for interfacing the VCCS equipment on this IP backbone using the appropriate fire retardant structured shielded cabling and L2/L3 switches. Redundancy shall be maintained in all the network connections/components. 2. SYSTEM DESCRIPTION 2.1 The VCCS shall be designed on open system architecture philosophy and use standardized open standards/RFC based IP Technology. 2.2 It shall minimum meet latest current valid WG67 ED136-139 or equivalent standards to meet aviation specific ATS requirements. 2.3 The VCCS may have a decentralized and distributed architecture with no single point of failure. 2.4 The system shall have sufficient inbuilt H/W & S/W components/modules to isolate individual failures from affecting overall performance of other VCCS functionalities. 2.5 Each VCCS module/component shall be an intelligent end-point that has a valid copy of the overall VCCS communication dial-plan / its own configuration during normal operations so that on failure of one module/component system functional performance is not degraded. 2.6 The H/W & S/W components for processing of audio from radio assets and CWP shall not/never share the same processing H/W & S/W due to its criticality in ATS operation except at the CWP analog accessories and ATS network components/cables etc... 2.7 The H/W & S/W components for processing of audio from telephony/intercom communication can share the same processing H/W & S/W. 2.8 Voice, Control and data shall use the same IP based ATS network. 2.9 The VCCS shall be able to connect both VoIP and legacy radios, telephony networks/assets. 2.10 Media gateways for converting VoIP audio & signaling to and for connection to legacy analog radios & legacy telephony networks/assets (incl. related signaling) and vice versa shall be used to increase efficiency, ease administration / maintenance efforts & decrease component number count,. 2.11 Within the VCCS/ATS network common IP protocols to transport voice and signaling over the ATS network shall be used. 2.12 The VCCS shall take its system time from a NTP time server over the IP network preferably using NTP v4 RFC 5905 2.13 The VCCS shall provide and extend SIP based IP-PABX functionalities within the ATS network for replacing or extending or working along with the legacy private automatic branch exchanges (PABX). 2.14 All VCCS components shall run on preferably open GNU based operating system.

i) ii) iii) iv)

3.2

3.4

Voice aggregation methods shall be offered & used for low bandwidth connection consumption to VoIP radio/other interfaced assets, where bandwidth on the transport network is limited. 2.16 The VCCS functionality shall be fully compliant to EUROCAE ED137-B Volume 1-4 or equivalent standards. 2.17 The offered system/architecture shall be deployed and operational since minimum 02 years, preferably in an airport ATS environment. 3. DESCRIPTION OF SYSTEM REQUIREMENT 3.1 SCALABILITY The offered VCCS shall be a scalable system that shall allow 50% addition or deletion of assets at a later time by inserting/with drawl of modules to interface Controller Working Position (CWP)s, IP/analog phones, leased/non leased analog /IP telephony networks and local/remote radio sites, IP/Analog radio interfaces without need for replacing the existing ATS network infrastructure and installed system/ equipment. 3.1.1 VCCS core shall be designed for Maximum, any instant capacity to handle airground and ground-ground communication from 500 CWPs with all assets. 3.1.2 Migration to ATS systems with VoIP/Analog assets & all-Analog/IP ATS infrastructure shall not need replacement of installed CWPs, Servers VCCS equipment and ATS network components. REDUNDANCY 3.2.1 1:1 redundancy for all critical equipment sub-systems shall be provided to ensure high system availability. 3.2.2 Critical components/equipment subsystems of the VCCS shall be considered as all network components and servers except NTP server. 3.2.3 The functional capability and capacity provided by the main and standby components/equipment subsystems shall be identical. 3.2.4 Failure of one network switching component/link part of dual redundant ATS network shall not affect the VCCS functionality and the ongoing calls i.e. there shall be No audio interruption and no need of reestablishment of connection within the ATS network connected assets. 3.2.5 Servers shall have redundant hot swappable storage disks to prevent any data transaction loss and enable recovery from operational online system. 3.2.6 In case the inbuilt VCCS management system is down or not reachable, the VCCS shall continue to function in the current online assets & state with no disruption to any existing calls. 3.2.7 All system sub components, like CWPs, servers and media gateways, shall have dual network interfaces to ensure redundant connection to the redundant IP ATS network. 3.2.8 Failure of one network interface in all system sub components shall trigger an automatic switch to the second network interface with all asset/communication functionality available within no more than 200 msec from the instant of interface failure. 3.2.9 Switchover between the redundant network interfaces for all system sub components shall not cause ongoing calls connections ATS network connected assets to be dropped. 3.2.10 All VCCS components (CWPs, media gateways, servers, LAN components) shall be fitted with dual power supply of 2 x auto-ranging AC inputs and 2 x DC inputs (24/48Vdc) 3.2.11 All media gateway interface cards shall be modular, hot swappable for easy, hot and direct replacement. 3.2.12 The VCCS core shall support geographical redundancy. 3.2.13 One or more subset of VCCS components shall be possible to be installed at separate geographical locations without affecting the overall VCCS functionality/ availability. 3.2.14 VCCS shall support distances of 1 km and more between the different locations of a geographically distributed VCCS system/ ATS network connected assets sites. 3.3 VOICE DELAYS 3.3.1 VCCS audio/control processing H/W & S/W modules shall not introduce a voice/PTT delay larger than 50 msec between the PTT device (headset/handset/microphone/foot switch PTT) at the CWP and the input interface at the distributed radio site/networked asset in 95% of the cases for VoIP and analog radios/assets. 3.3.2 VCCS audio/control processing H/W & S/W modules shall not introduce a voice/Squelch delay larger than 50 msec between the receiving radio squelch break/networked asset output interface and the CWP audio output devices in 95% of the cases for VoIP and analog radios/assets. RADIO 3.4.1 VCCS shall allow ATS controllers to receive and transmit voice over the assigned and selected radio frequencies over the ATS network. 3.4.2 VCCS Radio interface shall fully comply ED137B Volume 1 "Radio" for radios interface 2.15
Page 2 of 29

3.4.3

Concentrator device shall be provided to aggregate the VoIP traffic from all CWPs to VoIP radios, which support only a limited number of SIP sessions as per ED137B, at the VCCS core site so that only one SIP connection to the radio is established.

3.5

3.6

RADIO FREQUENCY OPERATIONS 3.5.1 Radio frequency shall be assigned by authorized system administrator in configurable GUI at the TED/CWP touch screen, as one/more buttons for the controller to maintain watch, monitor, couple and operate main/standby and fall back radios/frequencies/assets connected over the ATS network. 3.5.2 Each frequency/radio asset assigned by system administrator shall give possiblility to be selected in the following ways: a) Rx mode only (receive/monitor mode) with or without Best Signal Selection (BSS) b) Tx mode only (transmit mode) with or without radio/frequency aggregation c) Rx/Tx mode only (traffic mode) with or without BSS/radio/frequency aggregation d) Deselected mode (nothing is received or transmitted) e) Simplex/Duplex Frequency Coupling 3.5.3 The selection/operation of a radio frequency button at one CWP shall not influence the frequency selection/operation done at other CWPs (except for PTT locked) that have the same frequency assigned. 3.5.4 The CWP shall allow the controller to select all frequencies in different pages in any of the available operational modes. RADIO CHANNEL OPERATIONS 3.6.1 The VCCS system shall allow all physical analog/VoIP receivers, transmitters and transceivers sites that operate on the same radio frequency to be grouped into one logical element called "frequency". 3.6.2 Each individual radio transmitter, receiver and transceiver shall be displayed at the CWP as a radio channel that is part of the logical radio frequency 3.6.3 Each logical radio frequency can contain up to 12 radio channels (transmitters/receivers/transceivers) that can be analog or VoIP radios or a mixture of both. 3.6.4 Each radio channel part of a radio frequency can be selected in the following ways: a)Rx mode only (receive) with or without Best Signal Selection (BSS) b)Tx mode only (transmit) with or without radio/ frequency aggregation c)Rx/Tx mode (receive and transmit) with or without BSS/radio/frequency aggregation d) Deselected mode (nothing is received or transmitted) e) Simplex/Duplex Frequency Coupling 3.6.5 The selection of active receiving and transmitting radio channels of a radio frequency at one CWP shall not influence the selection made at other CWPs that have the same frequency assigned. 3.6.6 To cover extended geographical areas for monitoring a radio frequency, VCCS shall allow the controller to select multiple same frequency radio channels in Tx & Rx mode with & without BSS function. 3.6.7 If frequencies in climax mode are authorized by system administrator, then maximum of configurable transmitter/ Receiver/ transceiver channel per one radio frequency shall be active in transmit or traffic mode at a CWP at a time. 3.6.8 If Climax functionality is configured for a frequency by System Administrator then multiple transmitters and transceivers shall be selectable for that frequency at any CWP that has the frequency assigned. 3.6.9 When the controller selects a radio frequency in monitoring mode (Rx), then VCCS shall configure itself radio calls toward all receiver/transceiver radio channels selected as active for this frequency at the commanding CWP only and shall not effect selection at other CWPs. 3.6.10 When the controller selects a radio frequency in transmit mode (Tx), the VCCS shall configure itself radio calls toward all transmitter/transceiver radio channels selected as active for this frequency at the commanding CWP only and shall not effect selection at other CWPs. 3.6.11 The CWP shall clearly indicate to the controller whether selection of a radio frequency is made. 3.6.12 The CWP shall clearly indicate to the controller whether selection of a radio frequency/channel has failed. 3.7 RADIO TRANSMISSION 3.7.1 Each CWP shall allow for multi-frequency transmit operations/ frequency aggregation. 3.7.2 The controller shall be able to select multiple frequencies in transmit or traffic mode. 3.7.3 The controller's voice shall be transmitted to radios only during PTT activation. 3.7.4 At PTT activation, the controller's voice shall be transmitted on all frequencies selected in Tx or traffic mode.
Page 3 of 29

4.3

The source of the PTT shall be indicated clearly at the CWP GUI, at each PTT activation. 3.7.6 The source of PTT activation shall be indicated as one of the following: a) headset/handset/microphone ID b) footswitch PTT c) GUI activated PTT 3.7.7 The controller shall receive a graphical feedback at the CWP GUI of the success or failure of his/her transmission (e.g. failure due to concurrent PTT from another CWP). 3.7.8 A PTT timeout timer shall be configurable from 3-300 seconds to avoid faulty continuous PTT activation. 3.7.9 When PTT is being continuously active for periods longer than the PTT timeout timer, the CWP shall be able to forcefully interrupt the active PTT. 3.8 RADIO RECEPTION 3.8.1 Each CWP shall allow for multi-frequency receive operations. The controller shall be able to select multiple frequencies in receive mode. 3.8.2 The voice received from all the frequencies selected in receives or traffic mode shall be presented to the controller. 3.8.3 Squelch shall be visually indicated on all the frequencies selected in receive or traffic mode that have an active radio reception. 3.8.4 Received radio voice shall be presented to one or more of the audio output devices depending on the CWP audio settings: a)left and/or right earpiece of the stereo headsets b)handsets/mono headsets c)any of the loudspeakers 3.8.5 The controller shall be able to configure each radio frequency to be heard in any of the available audio output devices at the CWP independently from the settings on other CWPs. 4 RADIO FUNCTIONS 4.1 BSS 4.1.1 The controller shall be able to select in CWP TED (Rx) or traffic (Rx/Tx) mode multiple radio channels that are part of the same frequency. As a result of such a selection, the controllers shall be presented with only one voice stream voted as being of the best quality by the BSS function, if enabled. 4.1.2 BSS function shall not introduce its own voice delay larger than 250 ms. 4.1.3 BSS shall be possible to apply for up to 16 radio channels of the same radio frequency. 4.1.4 The BSS function shall be possible to be activated and deactivated by each CWP individually. 4.1.5 The BSS activation at each CWP shall be independent from other CWPs. 4.1.6 BSS shall be automatically activated by the CWP for frequencies with more than one receiver/transceiver selected in receive or traffic mode. 4.1.7 Activation of the BSS function on a radio frequency at a CWP shall be visually indicated on the radio frequency button of the CWP GUI. 4.1.8 A BSS algorithm shall be preferably be based on the comparison of the actual voice quality deduced from the spectral richness of the voice signal received and RSSI signal quality parameter received from different radios/ sites. 4.1.9 It shall be possible to configure different BSS algorithm is to be used for each multichannel frequency: RSSI or BSS based on voice quality by system administrators. 4.1.10 VCCS shall support the BSS function for all mixed analog and VoIP radios, selecting the best voice reception regardless of the radio type and BSS algorithm selected. 4.2 AUTOMATIC TRANSMITTER SELECTION 4.2.1 The VCCS shall provide an Automatic Transmitter Selection function. When this function is activated, the radio transmission from a CWP is sent to be aired to the transmitter which is paired with the receiver voted as best by the BSS function at the CWP. 4.2.2 The controller shall have the following modes available: a) Manual Selection of Receivers and Transmitters (BSS inhibited); b) BSS /Receiver Voting (the best transmitter will be selected manually and BSS selects the best receiver); c) Transmitter Follows Best Receiver (BSS selects the best receiver; the transmitter automatically follows the best receiver). 4.2.3 It shall be possible for the controller to override the Automatic Transmitter Selection function result and manually select another transmitter. SIMULTANEOUS TRANSMISSION DETECTION 4.3.1 VCCS shall be able to read information provided by the radio about the simultaneous transmissions that occurs on the radio channel. 3.7.5
Page 4 of 29

4.4

4.5 4.5.1 4.5.2 4.5.3 4.5.4 4.5.5 4.5.6 4.5.7 4.5.8 4.5.9 4.5.10 4.5.11 4.6

VCCS shall visually inform the controller by means of the CWP GUI of a simultaneous transmission that occurred on a radio channel. 4.3.3 There shall be provisions employed in VCCS to avoid occurrence of simultaneous transmissions on radio channels within the ATS network at same or different PTT priority. RADIO SIDE TONE 4.4.1 Radio side tone shall be configurable for the complete VCCS as follows: a) No side tone b) locally generated side tone c) true remote side tone 4.4.2 To avoid audio loops generated by the controller's voice entering the loudspeakers and then back to the microphone, the CWP shall not present the received radio voice (including true radio side tone) to the loudspeakers in the case when CWP is currently transmitting on this frequency. 4.4.3 Local side tone shall never be presented at the loudspeakers as to not generate audio loops. FREQUENCY CROSS COUPLING It shall be possible for the controller to activate the frequency Cross-Coupling function at the CWP. Frequencies shall be possible to be placed in a Cross-Coupled group causing automatic retransmission of the signal received on one of these frequencies to all other cross coupled radio frequencies. A Cross-Coupled group shall be possible to contain both Simplex mode and Duplex mode frequencies. Duplex mode shall be the default mode to couple a radio frequency. Audio received from a frequency in duplex Cross Coupling shall be retransmitted to all other frequencies in the same Cross-Coupled Group. Only one frequency can be retransmitted at one time for each Cross-Coupled Group. Audio received from a frequency in simplex Cross Coupling shall not be re-transmitted to other frequencies in the same Cross-Coupled group. Simplex group members shall only receive audio from the controller or from duplex Cross Coupled frequencies. The controller shall be able to choose the coupling mode (duplex or simplex) for each frequency. VCCS shall allow multiple cross coupling groups to be created inside the VCCS. VCCS shall allow only one cross coupling group to be created at each CWP. VCCS shall allow up to 8 cross coupling members in each cross coupling group. 4.3.2 PRIORITY RADIO OPERATIONS 4.6.1 The VCCS shall support the emergency radio call features as described in ED137B Volume 1. 4.6.2 In case a radio has a limit of active VCCS-to-radio connections, VCCS shall offer the possibility to gain prioritized access to congested radios by placing emergency radio calls from CWPs. 4.6.3 The emergency radio frequency selection (selection of emergency Rx or/and emergency Tx) shall interrupt an existing connection of lower priority at each called radio and establish the requested radio call. 4.6.4 For multi-channel frequencies, when the controller selects a frequency in Rx or Tx emergency mode, the VCCS shall automatically place the necessary number of emergency radio calls towards the configured and active radio channels. 4.6.5 The CWP shall visually indicate the radio frequencies that have been selected using the emergency function at the CWP. 4.6.6 The VCCS shall offer the possibility to the controller to place an urgent or emergency radio transmission even if another controller is currently transmitting on the same frequency. 4.6.7 VCCS shall support differentiated PTT Priority. Three PTT priorities shall be available at the CWP (from lower to higher): a)normal PTT b)priority PTT c)emergency PTT 4.6.8 In the event of simultaneous PTTs, the controller with the highest PTT priority shall seize the transmitter even if it was already in use by another controller with a lower PTT priority. 4.6.9 The priority of the PTT at one CWP shall be set by the controller by activating/deactivating the "Emergency" or Priority functions at the CWP GUI. CWP OPERATIONAL MODES CWP shall support the following operational modes: one or multiple controller operations with no special operational mode multiple controllers in trainer/trainee mode multiple controllers in split mode
Page 5 of 29

4.7 i) ii) iii)

4.8

4.9

4.10

4.12

4.13 4.13.1 4.13.2 4.13.3 4.14

i. ii. iii.

ONE OR MULTIPLE CONTROLLER OPERATIONS 4.8.1 The audio shall be presented to all available headsets/handsets in the same way. 4.8.2 At PTT activation, the controller's voice shall be taken from the headset that activated the PTT first. TRAINER/TRAINEE MODE 4.9.1 VCCS shall support Trainer/Trainee operations at CWPs. 4.9.2 The Trainer/Trainee operational mode shall be possible to activate independently for each CWP from the CWP GUI. 4.9.3 At PTT activation, the trainer's voice shall take precedence over the trainee's. If the trainer activates PTT, his/her voice shall be transmitted to the radio, even if the trainee was transmitting at the same time. 4.9.4 All trainers and trainees at a CWP shall hear each other's transmissions at the headsets regardless of the radio side tone settings configured in the VCCS. 4.9.5 Up to two trainers and two trainees shall be possible to operate at a CWP. SPLIT MODE 4.10.1 VCCS shall support independent split operations for radio and telephony at the same CWP. 4.10.2 The Split operational mode shall be possible to activate independently for each CWP from the CWP GUI. 4.10.3 During split mode operations, a controller shall be able to operate the radio communication while the other operates the telephony communication. Each of the controllers shall only hear the radio and respectively the telephony communication. 4.11 CLIMAX (CARRIER OFFSET) OPERATIONS 4.11.1 VCCS shall support Climax Operations (off-set carrier) to provide extended radio coverage. 4.11.2 For frequencies configured with the climax functionality, multiple transmitters (transmitting radio channels) shall be selectable by the controller to be used at the same time. 4.11.3 For frequencies configured with the climax functionality VCCS shall be able to transmit voice over several same-frequency transmitter channels simultaneously. REMOTE RADIO CONTROL 4.12.1 VCCS shall offer radio control and monitoring possibilities for a range of VoIP and analog radios 4.12.2 If authorized, ATS controllers shall be able to monitor from the CWP the operational state of the radio/asset (normal operation/ warning/ error) 4.12.3 It shall be possible for ATS controllers to change the radio frequencies remotely from the CWP for the supported radios/assets, if authorized. 4.12.4 If authorized, the CWP shall present a list of available frequencies/assets that are available for selection and from which the controller can choose to activate remotely. AIR-GROUND CONFERENCE VCCS shall support activation/deactivation and configuration of A/G conference feature by System administrator. If need arises, VCCS shall support Air/Ground conferences. As a result of an air-ground conference, one or multiple ground stations can listen to the transmission of one or multiple radio frequencies. RADIO INTERFACES 4.14.1 The VCCS shall be able to connect to local/remote VoIP and analogue radios. 4.14.2 VCCS shall use the ED137B Volume 1 "Radio" standard to ensure voice communication with VoIP radios via the IP ATS network. 4.14.3 VoIP radios shall be connected directly to the VCCS IP interface without additional IPto-analog media conversion. 4.14.4 Radio gateways shall be used to connect VCCS to analog radios via the E&M/phantom keying interface. 4.14.5 VCCS shall support in-band and out of band DTMF PTT and Squelch signaling at analog radio interfaces. 4.14.6 VCCS shall have available the possibility to set the type of each E&M interface for inband and out of band signaling. 4.14.7 For radios that do not generate a Squelch signal, VCCS shall detect reception independently. The decision of signal presence shall be based on a signal strength analysis. 4.14.8 The signal strength threshold for voice detection shall be configurable per radio channel. 4.14.9 Radio gateways shall be able to support the following signaling: Type I 2 wires for supervisor signaling: E, M Type II 4 wires for supervision signaling: E, M, SB and SG Type III 4 wires for supervision signaling: E, M, SB and SG
Page 6 of 29

iv. v.

5.1 5.2 5.3

5.3.3

5.3.4

Type IV 4 wires for supervision signaling: E, M, SB and SG Type V 2 wires for supervisor signaling: E, M 4.14.10 Failure of one interface card in a radio gateway shall not lead to failure of other radio interface cards. 5 TELEPHONY The telephony operations and functions provided by the VCCS shall be compliant with the ED137B Volume 2 "Telephone" and Volume 3 "European Legacy Telephone Interworking" standards. The VCCS shall permit all CWPs and telephony VCCS users to place and receive telephony calls. TELEPHONY CALL 5.3.1 CALL INITITATION: 5.3.1.1 INDIRECT ACCESS CALL IDA CALL Each CWP shall allow the operator to initiate calls to a preset ground destination (or predefined group of destinations by dialing its number manually on a dial pad. 5.3.1.2 DIRECT ACCESS CALL -DA CALL Each CWP shall provide the capability of displaying and using at minimum 40 DAkeys. DA-calls shall be placed by pressing the DA-button of the target ground destination and waiting for the call answer at the destination. 5.3.1.3 INSTANTANEOUS ACCESS CALL - IA CALL Each CWP shall provide the capability of displaying and using IA-keys. IA-calls shall be placed by pressing the IA-button of the target ground destination. The targeted CWP shall not need to accept the call first, voice shall be directly connected to the position and added to the communications already taking place. 5.3.2 CALL ACCEPTANCE 5.3.2.1 It shall be possible to accept an incoming telephony call by pressing the corresponding key in the incoming call queue. 5.3.2.2 It shall be possible to accept an incoming telephony call by pressing the corresponding DA key in the telephony buttons area. 5.3.2.3 IA calls shall be connected without the destination performing any acceptance action. 5.3.2.4 All incoming telephony calls (except IA calls) shall appear in the call queue identified with the called ID and name (if available) of the calling party 5.3.2.5 Each incoming call in the call queue shall display the time spent by the call in the call queue. CALL RELEASE 5.3.3.1 The Call Release (Call END) function shall enable the operator to terminate active telephony calls. 5.3.3.2 In order to release an active or an outgoing call that is still ringing at the called destination, the END button or the corresponding DA key shall be pressed TELEPHONY FUNCTIONS 5.3.4.1 VCCS PTT use shall be configurable for one of the following: a) PTT used only for Radio calls b) PTT used for both radio and telephony calls 5.3.4.2 CALL HOLD/MUSIC ON HOLD a) By means of the Call Hold function the operator shall be able to cut off an active telephony call without having to release it so that he can continue the call at a later moment. b) The VCCS shall permit the operator to temporarily withdraw from an active G/G connection by pressing the Hold button. c) After placing a call on hold, the operator shall be free to place or answer A/G calls and other G/G calls as if no G/G call was active. d) The user placed on hold shall receive Music on Hold e) Possible to hold both telephony and conference calls exception for IA (Instantaneous Calls). It should not be possible to put IA calls on hold at all. 5.3.4.3 CALL FORWARD a) The call forward function shall enable a controller to re-route all incoming telephony calls to another CWP or telephony destination b) The controller shall be presented with a visual indication of the fact that call forward is active at the CWP as well as the destination of the forwarding. c) A CWP with call forward activated shall be able to place telephony calls and operate radio communication 5.3.4.4 CALL TRANSFER This function shall enable any call made or received at a CWP to be manually redirected to another CWP or telephony destination. 5.3.4.5 PRIORITY CALL
Page 7 of 29

5.3.5

a) The VCCS shall support the priority telephony call feature as described in ED137B Volume 2. b) The VCCS shall uses 3 levels of telephony call priority: 5.3.4.5.b a)normal call (low priority) 5.3.4.5.b b) priority call 5.3.4.5.b c) emergency call (highest priority) c) For any telephony call initiated at a CWP (except IA call) it shall be possible to attach a priority level. d) The controller shall be able to set the priority level of the call prior to initiating it. e) Incoming priority calls at a CWP shall be presented in a distinctive manner in the call queue so that the controller receiving the call takes notice of an important call. 5.3.4.6 CONFERENCE a) The conference function shall enable a controller to interconnect a number of CWPs and/or lines of varying types, allowing full speech facilities between all connected parties. b) The VCCS shall support progressive conferences. The controller shall be able to progressively add participants to a conference he/she initiated. c) The VCCS shall support preset conferences. The controller shall be able to initiate a preset conference call by selecting a programmed dial number or function key. 5.3.4.7 PROGRESSIVE CONFERENCE a) Each position shall be able to initiate up to three progressive conferences from the CWP. b) The initiator and/or participants of the conference shall be able to temporarily leave the conference without ending it. c) The VCCS shall allow the conference initiator to terminate the whole conference permanently d) Any internal or external line and phone (CWP, SIP phone, analog phone, PABX phone) shall be possible to be added to the progressive conference. 5.3.4.8 FORKING GROUP a) VCCS shall support Call Forking functionality that allows a call to be directed to multiple destinations placed in the same Forking group. b) A call directed to a Forking group shall be displayed as an incoming call at all the terminals that are part of the Forking group. c) As soon as the call is accepted at one terminal, the call shall disappear from the call queue of all the other CWPs or VCCS telephony users d) Any type of telephony call (except IA call) shall be possible to be initiated toward a Forking group. e) VCCS shall allow a number of up to 100 Forking groups to be defined in the VCCS Management System. f) VCCS shall support 100 members in each defined Forking group. 5.3.4.9 HUNTING GROUP a) The VCCS shall support the call hunting functionality whereby members (CWP roles, VCCS telephony users) defined as part of a Hunt group can be called according to their priority in the group. b) A hunting group shall be called using the hunt group target number uniquely defined in VCCS Management System. c) When a hunt group target number is called, the system shall hunt through the group of members starting with the highest priority down to the lowest until it finds a destination that answers the call. d) Any type of telephony call (except IA) shall be possible to be addressed to a hunting group. e) VCCS shall allow a number of up to 100 Hunting groups to be defined in the VCCS Management System. f) VCCS shall support 20 members in each defined hunting group. 5.3.4.10 OTHER FACILITIES: a) LAST NUMBER REDIAL: Any last telephony destination that has been previously called shall be possible to be recalled by using the "Redial" function. b) CALL PICKUP GROUPS: i) The VCCS shall support call pickup facility which enables a user to answer a call that is in the alerting phase (ringing) at another user's terminal in the Pickup group. ii) Pickup groups shall be defined by the system administrator at the VCCS Management System. TELEPHONY INTERFACES
Page 8 of 29

5.3.5.1 5.3.5.2 5.3.5.3 5.3.5.4 5.3.5.5 5.3.5.6 5.3.5.7 5.3.5.8 5.3.5.9 5.3.5.10

i) ii) iii) iv) v) vi) vii) viii) ix) x) xi) xii) xiii) xiv)

6 6.1.1.1 6.1.1.2 Basic Call Call Hold/Music on Hold Call Forward Voicemail Call Transfer Meet Me Conference Call Waiting Call Hunting Call Forking Call Pickup Do Not Disturb(DND) Anonymous Call Rejection Calling Line Identification Presentation(CLIP) Calling Line Identification Restriction(CLIR) 6.1.1.3 The VCCS telephony users shall be able to place and receive calls using CWP TED and external SIP phones. 6.1.1.4 The VCCS telephony users shall be able to place and receive VCCS internal G/G calls and external calls on both IP and legacy networks 6.1.1.5 Configuration and management of the VCCS telephony users shall be performed from the System administrator on VCCS Management System connected in ATS Network. 7 CONTROLLER WORKING POSITIONS (CWP) 7.1 AUDIO ACCESSORIES 7.1.1 Each CWP shall allow for connection and use of up to four headsets/handsets/microphones and four loudspeakers. Any subset of these audio devices shall also be supported. 7.1.2 The headset/handset/microphone connectors and volume adjustment knobs shall be placed on audio modules separate from the CWP body and shall be possible to be installed in the controller's desk. 7.1.3 The audio modules shall be connected to the CWP unit via a interfaces with protection mechanism against accidental disconnection. 7.1.4 The audio module for connecting headsets/handsets/microphones shall have its audio connectors on the front panel easily accessible by the controller for frequent connection and disconnection of headsets. 7.1.5 The headset/handset plug connectors shall provide optical aid that helps the controller to properly align plug and socket at the audio panel. 7.1.6 The audio module for connecting loudspeakers shall have its audio connectors at the back panel for protection. 7.1.7 The presence of correctly connected headset/handset/microphone shall be visually indicated at the audio module as well as at the CWP GUI. 7.1.8 The connectors for headset/handset/microphone shall be fitted with a protection mechanism against accidental disconnection.

VCCS shall use the ED137B Volume 2 "Telephone" standard to ensure voice communication with VoIP networks and telephony destinations over the IP network. Calls toward VoIP networks and terminals shall not need an additional IP-to-analog media conversion. VCCS shall use the ED137B Volume 3 "European Legacy Telephone Interworking" standard to ensure voice communication with legacy telephony networks and terminals. The VCCS shall ensure telephony call placement and answer over the FXO and FXS interfaces. The VCCS shall ensure telephony call placement and answer over the MFC-R2 interfaces. The VCCS shall ensure telephony call placement and answer over the LB interfaces. The VCCS shall ensure telephony call placement and answer over the E&M interfaces. The VCCS shall ensure telephony call placement and answer over the ISDN PRI and BRI interfaces. Telephony gateways with modular interface cards shall be used. Failure of one interface card shall not lead to failure of other interface cards. It shall be possible to use different types of telephony interfaces in the same telephony gateway. IP-PABX VCCS shall offer IP PABX functionalities for VCCS telephone users. VCCS shall support the following telephony functions for the VCCS telephony users:

Page 9 of 29

7.2

i) ii) iii) iv) v)

The audio volume for headsets/handsets and loudspeakers shall be individually adjustable both from the CWP GUI and from the physical knob at the front panel of the audio modules. 7.1.10 For stereo headsets, the audio module shall allow for independent left and right audio channel volume adjustment. 7.1.11 The result of the audio volume adjustment using the physical knob at the audio module shall be visually displayed at the CWP GUI in real time. 7.1.12 Loudspeakers shall have a visual indication on the front panel of the audio module that indicates active radio reception HARDWARE REQUIREMENTS 7.2.1 The CWP unit shall preferably be not larger than 1HU and shall use very small foot print. 7.2.2 CWP shall be connected to the VCCS ATS IP infrastructure via two fully redundant Ethernet interfaces. 7.2.3 In case one of the network connections fails, this shall not cause the CWP to drop established calls or interrupt its operation as long as at least one network connection is functional. 7.2.4 All connectors that link the essential components to the CWP processing unit shall be fitted with mechanisms that prevent accidental disconnection: i. touch screen (CWP TED) ii. network connection iii. voice accessories iv. All PTT devices v. Dual AC/DC power supplies 7.2.5 CWP shall be fitted with a PTT interface for connecting a foot-switch PTT. 7.2.6 The CWP shall have at least one free standard interfaces for connection of additional peripherals (mouse or keyboard) for maintenance or enhanced operations. 7.2.7 CWP shall have a serial RS-232 interface for maintenance purposes. 7.2.8 VCCS CWP shall provide the possibility to control the brightness and/or contrast of the CWP touch screens by a dedicated control: mechanical button/knob or soft key at the touch screen. 7.2.9 Changes of brightness and/or contrast shall take place in steps. 7.3 CWP HMI REQUIREMENTS 7.3.1 The CWP shall have touch screen-based graphical user interface. 7.3.2 The CWP GUI shall display telephony, radio and additional function resources for the ATS controller's use. 7.3.3 The actual layout of the CWP GUI shall be configurable and easy to change by the system administrator. 7.3.4 There shall be a CWP GUI Designer tool for configuring the CWP display layout by means of simple actions like drag and drop, color selection and real time resizing of elements. 7.3.5 Different CWPs shall be possible to have different GUI layouts depending on their operational roles. 7.3.6 The CWP GUI shall contain the following main operational areas: i) radio frequency and functions area ii) telephony buttons and functions, call queue area iii) CWP functions area iv) additional applications area 7.3.7 The CWP GUI shall be structured in one main and many secondary sub-windows that allow for less important information to be placed in sub-menus. 7.3.8 The events related to call control shall be presented at the CWP GUI with a maximum delay of 40 ms from the moment they are established at the CWP. 7.3.9 The events related to call control shall be transmitted by the CWP GUI to the call control software with a maximum delay of 10 ms from the moment the controller selected/unselected a telephony or radio button. 7.3.10 Changes to call states shall be presented at the CWP GUI by means of changing color, size or other parameter of the telephony and radio buttons. 7.4 CWP GUI DESIGNER 7.4.1 VCCS shall provide a web-based graphical GUI designer tool to customize and edit the actual GUI layout for the CWPs. 7.4.2 The GUI designer shall allow the administrator to: design a new GUI edit an existing GUI delete an existing GUI test a new GUI/edited GUI store different GUIs without bringing them into operation
Page 10 of 29

7.1.9

vi) vii)

7.5.2

7.5.3

7.5.4

assign different GUIs to different roles bring a new GUI into operation, also during the related role is active 7.4.3 The scope of the GUI designer shall cover: i) define/edit/delete radio, telephony and functional buttons and text areas ii) integration of icons and images with free positioning on buttons or on the screen iii) free positioning of all buttons and fields iv) define areas on the screen 7.4.4 The GUI designer shall support the following features in order to allow the designer to work quick and efficient. i) Drag-and-Drop of GUI elements ii) Resize of GUI elements by means of simple stretching/ compression iii) Change element properties and immediately assess the visual result 7.4.5 The GUI layout prepared with VCCS GUI designer shall allow a deployment of the GUI at different screen sizes. 7.5 CWP FUNCTIONS 7.5.1 AUDIO CONTROLS 7.5.1.1 CWP shall offer audio routing features. 7.5.1.2 Telephony and intercom audio shall be presented to the following output devices: 1. headsets, 2. loudspeaker/s 7.5.1.3 Radio audio shall be routed to the following audio outputs according to the configuration per each frequency: 1. at the left and/or right audio channel of the headsets, 2. at any combination of the loudspeakers. 7.5.1.4 "Telephony to speaker" function shall be available to route all telephony audio to the speakers instead of the headsets. 7.5.1.5 "Mute Buzzer" function shall be available to stops the incoming telephony calls from generating a sound alarm. In such a case, only a visual indication of the incoming call shall be presented to the controller. 7.5.1.6 Audio volume control shall be available for each audio output device independently. 7.5.1.7 Audio volume adjustment shall be available from the audio module plug panel and from a "Audio Settings" menu at the CWP GUI. 7.5.1.8 Audio volume shall be presented at the CWP GUI as progressive bars displaying the actual audio level compared to the maximum level available. 7.5.1.9 For stereo headsets independent audio volume adjustment for the right and left audio channel shall be available. 7.5.1.10 For stereo headsets, a binding function shall be available that allows simultaneous volume adjustment for the right and left audio channel. 7.5.1.11 Protection against zero audio level settings shall be available for headsets/handsets and loudspeakers. Once activated at the VCCS Management System, this feature shall not allow the controller to set to zero the audio output volume for certain audio devices. SHORT TERM RECORDING 7.5.2.1 The CWP shall have a short term recording playback function that allows the controller to hear communications that took place at the CWP in the immediate past. 7.5.2.2 The recorded time shall be the last 60 minutes of communication. 7.5.2.3 Telephony and radio audio shall be recorded and played back separately. 7.5.2.4 The short term recording playback menu shall present a list of past recordings that can be selected by means of the touch screen and played back to the controller. 7.5.2.5 Each short term recording file shall be named, dated and indicate the duration of the recording. POSITION MONITORING 7.5.3.1 The VCCS shall support the Position Monitoring function as described in ED137B Volume 2 "Telephone". 7.5.3.2 By means of the Position Monitoring function an operator shall be able to choose to monitor either G/G audio, A/G audio or the sum of G/G and A/G audio from the monitored CWP. 7.5.3.3 Position Monitoring mode shall be activated by pressing a "Position Monitor" functions button followed by the identification of the destination to monitor. 7.5.3.4 The controller shall be able to select the type of position monitoring (for A/G, G/G or summed audio) prior to starting the actual monitoring session. DIAL PAD 7.5.4.1 The Dial Pad function shall allow a controller to enter a complete address of the telephony destination on a telephone dialing keypad, in order to cause a call attempt to be made to the supplied address.
Page 11 of 29

7.5.5

7.5.6

7.5.7

7.5.9

7.5.10

The dial pad shall contain digits 0 to 9, # and * defined in the classic telephone dial pad format. The digits shall be sent out when the "Call" button is selected. 7.5.4.3 The dial pad shall automatically close at the activation of the "Call" button. 7.5.4.4 The dial pad shall have a display area for the dialed number to be presented. 7.5.4.5 The dial pad shall have a "Delete" button to correct erroneous entries. TELEPHONE DIRECTORY 7.5.5.1 The Directory (Address Book) shall allow the controller to find and call telephony contacts based on their name/label. 7.5.5.2 The Directory shall be defined as a tree-like structured address book and shall present the name and the call number of a contact. 7.5.5.3 It shall be possible to initiate calls directly from the Directory. 7.5.5.4 It shall be possible to have up to five telephone numbers to call for each contact in the Directory. The controller shall be able to initiate a telephone call to any of the displayed numbers. 7.5.5.5 The contacts in the Address Book shall be added/deleted/edited by the administrator at the VCCS Management System. 7.5.5.6 It shall be possible to configure groups of contacts in the Directory. 7.5.5.7 It shall be possible to configure several Directories with distinct contents. The VCCS administrator shall be able to configure per CWP and per groups of CWPs which directory will be used. CALL HISTORY 7.5.6.1 A call history list shall be available at each CWP. 7.5.6.2 The call history list shall present the recent telephony calls (outgoing, incoming and missed calls) and allow redialing these destinations. 7.5.6.3 The call history list shall present the following call details: i) type of call (outgoing, incoming or missed call) ii) name/number /CLI of the B party, iii) date and time of the call. VIDEO MONITORING 7.5.7.1 It shall be possible to present at the CWP GUI the video stream received from IP cameras, if configured by system administrator. 7.5.7.2 If configured, a "video" menu shall be available at CWPs that allows the controller to select a video stream from a list of up to 20 IP cameras connected over ATS network. 7.5.7.3 If a camera is selected for viewing at a CWP then same cameras shall also be available for monitoring at different CWPs at the same time. 7.5.8 INPUT/OUTPUT DEVICE MANAGEMENT 7.5.8.1 The VCCS CWP shall be able to monitor and control switching input/output devices over USB/standard interface and IP, if configured by system administrator. 7.5.8.2 The controller shall be able to monitor the state of a list of switching input/output/BMS devices by means of the CWP HMI, if configured by system administrator. 7.5.8.3 The controller shall be able to control the state of a list of switching input/output devices /BMS by means of the CWP HMI, if configured by system administrator. TEXT MESSAGE DISTRIBUTION 7.5.9.1 The VCCS shall support distributing text messages, if configured by system administrator, from connected PC workstation to groups of CWP over ATS network. 7.5.9.2 If configured by system administrator, on receiving a new text message feed, the CWP shall present it to the controller via the HMI. 7.5.9.3 The text message distribution technology shall support font formatting: size, color, boldness of text. LOGIN/LOGOUT 7.5.10.1 VCCS shall support work activation/deactivation and CWP Login procedures by System Administrators. 7.5.10.2 If deactivated then CWP shall allow work without the need for controllers to login at the CWP. 7.5.10.3 If activated then CWP shall allow work with the need for controllers to login at the CWP. 7.5.10.4 If activated so, controllers shall login at the CWP before starting the operations using a username and a password allotted by System Administrators or AAI Enterprise ERP system. 7.5.10.5 If configured with the login feature, the login page shall display an alphanumeric keyboard on the CWP GUI that shall be used to type the username and password. 7.5.10.6 If configured with the login feature, the password field shall not display directly the keys written into it. 7.5.11 STATUS INDICATION

7.5.4.2

Page 12 of 29

7.5.11.1

7.5.12

The CWP shall constantly monitor the status of its redundant network connections to the VCCS network. In case of network interface failures, the controller shall be visually notified by use of HMI. 7.5.11.2 The CWP shall constantly monitor its connection to the VCCS Management System database. In case of connection failure, the controller shall be visually notified by use of HMI. 7.5.11.3 The CWP shall constantly monitor if there is a new configuration available for use at the CWP. CWP MAINTENANCE FEATURES 7.5.12.1 CWP shall have a calibration function that can be easily used by the controllers or by technical personnel to calibrate the touch screen in case of need. 7.5.12.2 CWP shall support a cleaning function that deactivates the touch screen for a configurable period of time so that the cleaning actions do not trigger undesired touch activations. During this time, all the voice and active conversations shall go on undisturbed, but the touch screen shall not accept inputs. 8 CONFIGURATION MANAGEMENT 8.1 SCOPE OF THE VCCS MANAGEMENT SYSTEM 8.1.1 The administrator shall be able to configure at minimum the following VCCS parameters at the VCCS Management System: i) routing management ii) VCCS telephony users management iii) operational setting iv) monitoring and supervision v) system control vi) configuration backup vii) GUI designer 8.2 VCCS MANAGEMENT SYSTEM ACCESS 8.2.1 VCCS Management System shall be a web based application, accessible from any host fitted with a web browser. 8.2.2 Access to VCCS Management System shall be protected by use of individual usernames and passwords. 8.2.3 Multiple user access at VCCS Management System shall be supported. 8.2.4 It shall be possible to predefine a list of valid IP addresses that are allowed to connect to VCCS Management System. Connection attempts from other hosts shall be ignored. 8.2.5 Remote access to VCCS Management System shall be possible through an engineered VPN. 8.3 CONFIGURATION DISTRIBUTION AND UPDATE 8.3.1 The VCCS shall support configuration and distribution of the new configuration to all relevant equipment during operation time. 8.3.2 Changes concerning the operational layout shall need explicit acceptance by the controller at the CWP before taking action. CWP shall inform the controller of a new set of operational configuration available (buttons, resources). 8.3.3 Changes regarding system functionality (call routing parameters, equipment configuration and other system settings) shall take action immediately at all the affected VCCS components without additional actions. These updates shall not affect the ongoing calls. 8.3.4 VCCS Management System shall allow detailed configuration up to card and port structure of equipment well as equipment settings necessary to integrate it in the overall VCCS. 8.3.5 VCCS Management System shall allow control of software updates to its components individually or in groups of equipment. 8.3.6 VCCS Management System shall allow import/export of VCCS relevant files to/from VCCS equipment. 8.4 MONITORING AND SUPERVISION 8.4.1 VCCS equipment malfunctions shall be monitored and displayed at the VCCS Management System 8.4.2 All monitoring information regarding the VCCS components shall be clearly separated in two categories: Events and Alarms. 8.4.3 "Events" shall be considered changes in VCCS components' states that do not threaten VCCS functionality and which happen under normal operations. 8.4.4 "Alarms" shall be considered changes in VCCS components' functionalities that threaten or limit the normal operations of the VCCS. 8.4.5 VCCS shall display system alarms together with the corresponding severity level. 8.4.6 The number of severity levels used to monitor the VCCS shall be configurable. 8.4.7 Each VCCS alarms type shall be possible to be attached with a corresponding severity level.
Page 13 of 29

8.4.8

i) ii) iii)

All VCCS alarms and events shall be dated using the system time synchronized via NTP. 8.4.9 A clear indication for each event/alarm shall present it has been acknowledged by the administrator or not. 8.4.10 Appearance of a new alarm shall generate an audio notification at the administrator workstation. 8.4.11 Following methods shall be used to obtain equipment and event information: i) direct and active notifications generated by the VCCS components and inserted into the VCCS Management System's database. ii) continuous monitoring from the Management System of software and hardware state of VCCS components. iii) SNMP messages from the VCCS components 8.4.12 Monitoring of the VCCS components shall be available via SNMPv2 and SNMPv3 8.4.13 Following VCCS components shall be possible to monitor using SNMP: i) CWPs, ii) Media gateways iii) IP network switching components iv) Management, Database, Radio, Telephony and Media Servers 8.5 CONFIGURATION BACKUP 8.5.1 VCCS Management System shall support configuration backup. All VC Management System configuration data shall be saved in files that can be stored and later retrieved. 8.5.2 The VC Management System shall support restoring a full VCCS configuration from a previously stored configuration file. 8.5.3 VCCS shall have the possibility to manage multiple stored configurations. 8.6 OPERATIONAL CONFIGURATION 8.6.1 The operational configuration of CWPs shall be done at the VCCS Management System. 8.6.2 The operational configuration of each CWP shall be assigned by the VCCS Management System on a per role basis. 8.6.3 A role shall be considered a VCCS entity that comprises all resources and information needed by a controller to operate an ATC segment. 8.6.4 Each role shall be assigns with a set of A/G and/or G/G buttons as configured at the VCCS Management System. 8.6.5 Besides any VCCS internal addressing, each role shall have its own MFC id number for external contact. 8.6.6 The same A/G and G/G resources (DA keys, radio buttons) shall be possible to assign to several roles at the same time. 8.6.7 Each CWP shall display a GUI layout as configured for the active role at the CWP. 8.6.8 The VCCS shall offer the possibility to configure different operational layouts of the CWP GUI for each individual role, for groups of roles or one common layout for all roles in the VCCS. 8.6.9 The changes to the operational configuration of a role shall be sent to the corresponding CWP immediately, but shall take action only after the controller working with the role has accepted the reconfiguration 9 VOICE/DATA/CONTROL RECORDING 9.1 The VCCS shall support recoding as described in ED-137B Volume 4 "Recording". 9.2 It shall be possible to record (digital certificate signed, if provisioned by AAI) voice/control/data generated from Analog/IP end systems/ assets connected to a redundant IP based local/remote ATS network at one location in IGI Airport Delhi. 9.3 This recorder shall be basically a Network Attached Storage technology based bulk recorder (COTS) configured to store 60 calendar days from 1500 (voice/control/data) assets information from IP based ATS network. 9.4 Intelligence from the following voice/control/data sources shall be recorded in separate physical/logical recording channels: Audio to and from all CWPs, Audio to and from legacy radios and telephony networks, Audio to and from VoIP radios and VoIP telephony terminals and networks. 9.5 Recording/Replay application on RCMMS shall allow to search, locate, start, replay, pause, restart listen locally, route over the network & export a physical/logical live/recorded (digital certificate signed, if provisioned by AAI) voice/control/data information from one or any group of any 1500 physical/logical channels from this recorder on to any role un assigned CWP position and /or Administrative laptop. 9.6 NETWORK ATTACHED STORAGE RECORDING DEVICE 9.6.1 NAS recorder device shall be used to record audio/video/control/data streams over dual redundant ATS IP based network, based on the configuration assigned by administrator.
Page 14 of 29

9.6.2 9.6.3 9.6.4 9.6.5 9.6.6 9.6.7 9.6.8 9.6.9 9.6.10 9.6.11 9.6.12 9.6.13 a) b) c) d) e) f) g) h)

Record-Replay application enabled on CWP by system administrator within the ATS network shall be able to access the recorded video streams, if authorized and approved by system administrators. The NAS recorder device shall support simultaneous play back and recording at full duplex operation. NAS recorder device shall provide a high quality recording storage and play back of recorded data. NAS recorder device shall support integration with ATS IP based network to provide centralized management from all management servers and RCMMS operating on latest Windows/Linux /Unix OS. NAS recorder device shall support of local/centralized user management with security procedures/level to control and authenticate its configuration & use. The legal recorder shall extend to provide & notify multiple alarms using audio/visual indications and reporting module. This shall use administrative ruggedized Laptop for local display & acknowledgement of alarms & messages from reporting module. It shall be able to notify alarms and reporting module messages to system administrators using RCMMS over the ATS network which can record and replay events in ATS network at all VCCS/Radio site. The reporting module message shall be able to play & send the specified pre recorded audio/visual alarm messages at RCMMS upon the activation of specified alarm. The alarm management system in RCMMS shall keep ongoing audit trail and save alarm in database for different periods of time, of all alarm and operators related operations in a separated database for later analysis. If the alarm is acknowledged by one of its recipient at local administrative laptop or RCMMS, then it shall disappear from other user screens also i.e. alarm stack for the complete system shall be common. These NAS recorder device shall have the following minimum features and specifications: Controller Onboard Cache with 4GB IOPS Storage HDDrive 15K rpm or more HDD support Host Interface RAID Support Network Transport Protocols Network File Protocols Controllers in Active-Active fail over mode with no single point of failure Mirrored SAS HDD of 450 GB or 600 GB in RAID 6 External/Internal USB/SATA & SAS At least four Gigabit Ethernet (IP) ports and four FC ports RAID levels 0,1, 1+0, 5, 6/DP SNMP, DHCP, DNS for network management. TCP/IP for communication and NTP for timing synchronization CIFS, NFS, HTTP/HTTPS, FTP, iSCSI, FCP and any other Protocols required by recording, replay, management application manufacturer as per its System Design. Compatible and Interoperable with Latest versions of MS Windows or Linux or Unix OS Hot pluggable 1+1 Redundant Power Supply Inbuilt GUI/CLI & Web Based administration management software on a appropriate recording administrative ruggedized Laptop with 15 monitor (shall be supplied along with this recorder) 19 Spare USB 2.0 slots to connect external USB device for backup and spare SAS/SATA Slots to be provided for connecting SAS/SATA HDD (for Back Up). 50% of minimum usable space configured for 60 calendar days 1500 voice/control/data logical/physical channels

i) j) k)

Operating System (OS) Power supply Storage Management Software

l) m)

Rack mountable Spare Slots

n)

Backup Slot populated with SAS HDD

9.7

9.8 10 POWER DISTRIBUTION PANEL (PDP)

Bidders/Contractors must provide an OEM authorization confirming the compliance to above technical specifications, along with the OEM authorization letter

Page 15 of 29

10.1 10.2 10.3 11 11.1

11.2 11.3

11.4 a. b. c. d. e. f. g. h. i. j. k. l. m. n. o. p. q. r.

s.

t.

u.

The 03 class C power distribution panel with class C Automatic Transfer Switch and Transient surge protection shall be provided to meet the power distribution to entire system from centralized/distributed UPS. This power distribution panel shall provide sufficient MCBs and power loops with Class C protection, ratings with independent fuses for entire offered equipment system distribution of VCCS, CWPs, Recorders and RCMMS elements. It shall extend independent circuits/loops one MCB for each loop with class C Automatic Transfer Switch and Transient surge protection and one mains control switch with class B Automatic Transfer Switch and Transient surge protection. The PDP shall also have changeover switch with class B Automatic Transfer Switch and Transient surge protection for bypassing the UPS with other sources of supply. Qty 03 2 X 40 KVA PARALLEL REDUNDANT CONFIGURATIONS UPS Qty 03 nos 2x40 KVA Floor Mounted On-Line UPS (Three Phase AC Input & single/3ph Phase AC Output) with input & output Isolation Transformer and Individual SMF Battery Bank (65AH or higher) to provide 60 minutes Battery back-up in load sharing mode shall be offered along with this requirement. There shall be nothing common between input & output connections/leads from each UPS. RS 232 Serial Port & RJ45 SNMP port with Software for remote control and monitoring of each UPS each battery banks and each isolation transformer using SNMP protocols over ATS network shall be supplied along with all accessories, options and one set of hard and soft copy of documentation. UPS PARTICULAR SPECIFICATIONS: UPS shall be free from all workmanship defects, sharp edges, nicks, scratches, burs, etc. All fasteners shall be fixed properly. The offered UPS shall be complete with all parts and all parts shall be functional. Enclosures shall conform to protection requirement of IP2L1 to IS13947 (part 1)/1993 (reaffirmed 1998). Mains By-pass facility shall be provided for maintenance of UPS. UPS rectifier shall supply minimum 1.5 times DC power for operating the UPS on full load and full battery bank boost charging current at the same time. Switching device shall be IGBT & shall employing modular PWM technology for graceful degradation in performance. Switching frequency shall be above 20 KHz. KW rating of the UPS shall be 0.70 times the KVA rating. Input: 3ph 300-450V AC, 50 3%Hz Output: 230V +/-1% (with alternative setting for 220VAC 1%) 50 0.5Hz phase or 3ph 440VAC 0.5%, 501Hz. Voltage regulation from no load to full load shall be within 1%. UPS shall have facility for operation in synchronous mode in which output frequency shall be same as that of mains frequency. Total harmonics distortion at output: 3% maximum for UPS on resistive load, if total input harmonics are less than or equal to 10%. Efficiency (at rated output voltage and frequency): Overall efficiency (minimum): 90% UPS power factor at rated load: better than 0.9 lagging. Over load: UPS shall withstand 50% overload for 10 minutes and 100% over load for one minute. Protections: Following protection shall be provided in UPS: i) Input / Output Over voltage ii) Output short circuit iii) Output overload. iv) Under voltage protection at battery terminal. v) Output Over shoot and under shoot shall not be greater than 4% of rated voltage for duration of 40msec. (maximum) Indicators and meters: Following indicators shall be provided:i) Mains presence. ii) Battery charging and discharging iii) Output overload iv) Low battery voltage. Digital meter shall be provided for monitoring the following preferable parameters in UPS: i) Input AC voltage. ii) Output AC Voltage, current and frequency iii) Battery voltage and current. BATTERY BANK: i) UPS shall be supplied with SMF VRLA battery only.
Page 16 of 29

11.5

Bidders shall offer 65AH or higher battery capacity SMF VRLA batteries only. Bidders shall declare normal operating battery voltage, number of batteries of in each bank, make and model of batteries offered with each UPS. iv) Offered Batteries for UPS shall be of the following makes only:- EXIDE, PANASONIC, AMAR RAJA, GLOBAL, ROCKET, YUASA, AMRON, RITAR makes DULY TYPE TESTED to JIS C 8702 standards. v. The UPS shall be complete with separate Trolley based protective enclosure for each battery bank and the firms shall connect these battery banks with each UPS to commission the same. w. Pre-dispatch Testing requirement for UPS: Following shall constitute pre-dispatch test and at least one sample shall be tested for each ratings at maximum backup time. Predispatch testing shall be conducted at the premises of the manufacturer in presence of an officer deputed by AAI: i) Visual examination of offered UPS. ii) Verification of output power, frequency, voltage regulation, efficiency, total harmonics distortion. iii) Verification of overshoot, undershoot limits and protection circuits. iv) Verification for insulation resistance, leakage current high voltage. v) Insulation resistance should not be less than 100 mega ohms vi) Verification of battery makes & capacity VAH. x. It shall be housed in rugged enclosure made of M.S sheet 1.2 mm (minimum) thick, aesthetically finished, duly pre-treated and powder coated. y. UPS shall be provided with SNMP RJ45 Ethernet for remote control monitoring & interfacing to computer hardware/software for data exchange of electrical parameters of UPS like input/output/rectifier/charger voltage, current frequency, UPS status, mode of operation etc. over ATS network. z. Bidders/Contractors must provide an OEM authorization confirming the compliance to above technical specifications, along with the OEM authorization letter ii) iii)

Page 17 of 29

1.

2.

3.

4.

SPECIFICATIONS/REQUIREMENTS OF VHF AMS BAND IP TRANSMITTERS, RECEIVERS AND RCMMS GENERAL SPECIFICATIONS 1.1. The offered VHF IP Radios/RCMMS/equipment/system by bidders shall work as Ground based Radios in VHF AMS band of 118-137 Mhz (Transmitter, Receiver with all accessories). 1.2. This Radios/RCMMS/equipment/system shall be compact, fully solid state, highly reliable and shall use latest state of the art technology. 1.3. This Radios/RCMMS/equipment/system design shall be such that it uses the most optimum rack space and all the components/modules/sub-modules/line replaceable units shall be selected by bidder in consistent with the philosophy/requirements of long term trouble free operation with highest degree of stability, reliability and maintainability. 1.4. All this offered Radios/RCMMS/equipment/system shall be according to CE/uL/cUL certified to fulfill the standards for electrical safety and electromagnetic compatibility 1.5. This offered Radios/RCMMS/equipment/system shall be designed for continuous operation/use (24/7 and 365 days a year). 1.6. The design life of this offered Radios/RCMMS/equipment/system shall be a minimum of 10 years. 1.7. The design life shall be achievable through normal and regular maintenance and without major dismantling or overhauling etc. of this offered Radios/RCMMS/equipment/system. 1.8. All types of spares and spare modules shall be made available by the bidder during life time of the Radios/RCMMS/equipment/system for maintenance, repair and up keep of the offered Radios/RCMMS/equipment/system. 1.9. Safety and protection of all personnel during normal operation and maintenance or during malfunctioning of any Radios/RCMMS/equipment/system shall be ensured as an integrated feature of design, manufacture and installation of the offered Radios/RCMMS/equipment/system. 1.10. Sufficient & adequate protection shall be included/inbuilt in offered Radios/RCMMS/equipment/system for ensuring safety of personnel from any possible hazards, including EMI radiation, high voltages etc. 1.11. The bidder shall furnish the details of EMI and Safety Standards met by its offered Radios/RCMMS/equipment/system and built in safety features. 1.12. The Radios/RCMMS/equipment/system shall be constructed on a modular basis, using plug-in type modules. Preferably, all plug in units and modules shall fit in suitable slots and shall be easily removable for maintenance & cleaning of the Radios/RCMMS/equipment/system. MAINS POWER SUPPLY 2.1. All Radios/RCMMS/equipment/system shall operate with an AC power source of 230 VAC, -10% @ 47 to 60Hz. 2.2. The Radios/RCMMS/equipment/system shall also have a DC power input facility as backup when AC Mains is not available. RELIABILITY 3.1. The Radios/RCMMS/equipment/system design shall employ the most suitable engineering techniques, materials and components and rigorous inspection during manufacturing to ensure a very high MTBF (Mean Time Between Failure) of Radios/equipment/system. ENVIRONMENTAL CONDITIONS 4.1. The Radios/RCMMS/equipment/system shall operate without any deviation in quality or degradation of system performance and all the parameter detailed in these specifications shall be guaranteed over the following environmental conditions : 4.1.1. Temperature: in line with EN60068-2-1, EN 60068-2-2 Operating: -10 C to +40 C Storage: -30 C to +70 C 4.1.2. Relative Humidity: 95% up to 40 C in line with EN60068-2-30

Page 18 of 29

PART 5. IP BASED VHF TRANSMITTER GROUND STATION S.NO. SPECIFICATIONS 5.1 RF Power Output: nominal 50 Watts +/-1dB in 50 unbalanced dummy load. Adjustable 5 to 50Watt in steps of 1 to 5 W. 5.2 Load Impedance: 50 ohms unbalanced 5.3 Duty Cycle:100% up to 80% of maximum operating temperature and 90% up to maximum operating temperature 5.4 Frequency Band: 118MHz to 136.975MHz (Voice Mode & VDL mode 2 operation) 5.5 Frequency Stability: < 0.3 ppm for duty cycle in Para 5.3 at 50 W RF power output 5.6 Frequency Error: < 1.5 ppm in 10years life cycle of equipment 5.7 Channel Spacing: at least 8.33 KHz. & 25 KHz 5.8 Audio interface: Voice over IP (VoIP) in line with in line with EUROCAE ED137B part1, standard conventional audio interface (600 balanced, -30 dBm to +10 dBm) to work with 2W/4W E&M signaling and Phantom key signaling. 5.9 Adjacent Channel Emissions: A: For AM Mode: i) 70dB for 25 KHz channel spacing ii) 60dB for 8.33KHz channel spacing B: For VDL Mode 2: in line with ETSI EN 301841-1, ICAO annex 10, volume III, chapter 6 i) 1st adjacent channel, BW = 25 kHz: in line with ICAO annex 10, volume III, chapter 6, == < 0 dBm ii) 1st adjacent channel, BW = 16 kHz: in line with ETSI EN 301841-1 == < 18 dBm iii) 2nd adjacent channel: < -28dBm iv) 4th adjacent channel: < -38 dBm 5.11.1 Spurious Emission: in line with ETSI EN 300676-1 ; f > 1 MHz: < -93 dBc 5.11 Modulation Mode: A3E for 8.33 KHz & 25 KHz. Channel Spacing and D8PSK for VDL Mode 2: 5.12 Modulation Depth: configurable between 30 % and 95 %, in steps, limited at 95 % 5.13 Audio Band width: 350-2500 Hz for channel spacing of 8.33 KHz & 300-3400 Hz for channel spacing 25 KHz. 5.14 Amplitude Modulation Distortion: <5% in line with ETSI EN 300676-1 5.15 Broadband noise for Voice at 300 kHz from carrier, in line with ETSI EN 300676-1, < 140 dBc (1 Hz) (at full output power) VDL2 at 800 kHz from carrier, < 144 dBc (1 Hz) (at full output power) 5.16 VDL Mode 2 Symbol Rate: 10500 symbols/sec ; Tolerance < +50 ppm; in line with ETSI EN 301841-1, 5.17 Digital audio interface: i) voice over IP (VoIP): in line with EUROCAE ED137B, part 1 ii) Session control: SIP in line with EUROCAE ED137B part1 iii) Audio stream: RTP in line with EUROCAE ED137B part1 iv) Audio codec: in line with ITU-T G.711 5.18 RF Power Attack time (Voice) in line with ETSI EN 300676-1 < 10ms 5.19 RF Power Release Time (voice) in line with ETSI EN 300676-1 < 10ms 5.20 Protection: Inbuilt for i) High VSWR, open / short circuit of the load ii) Protection against over temperature operation. 5.21 Load Mismatch: In built capability to operate at VSWR of 2:1 without power reduction and performance degradation. 5.22 At High VSWR up to 2:1: Power output shall remain within +/-1 dB of rated value. 5.23 Operation on Battery: nominal Battery operation at 24/28VDC. (Automatic Switch Over from AC to DC in case of Mains Power Supply failure and vice versa) 5.24 Controls, indications:The transmitter shall have the following minimum controls, indications and connectors: i) a visual indication for transmitter switch on ii) a visual indication for carrier transmission
Page 19 of 29

5.25 5.26 5.27 5.28 5.29

iii) Switch for AC/DC Power on/off iv) Front panel LCD Display to display various system parameters such as a) frequency/channel of operation b) O/P Transmitted power c) modulation depth level d) VSWR e) Results of continuous Built in test results (BITE) f) Failure of Transmitter modules/line replaceable units/accessories. v) Provision for programming various Transmitter parameters from front panel such as frequency/channel, power, modulation vi) Mode selector for 25 KHz, 8.33 KHz, AM, VDL Mode-2 operation. vii) Microphone jack viii) Conventional 600 audio interface for use with E & M signaling or phantom keying. ix) Data interfaces for VDL Mode-2 x) Remote control interface and operations : Ethernet IP xi) VoIP Interface as per EUROCAE ED137B part 1 xii) RF Output Connector xiii) USB/console port for maintenance PTT Timeout configurable between 3 sec and 300 sec & deactivated Type of equipment 19 Rack Mounting or 19/2, 1 to 3HU. EMI / EMC Standards: EMI/EMC standards as per ETSI EN 301489-1/22 and EN55022 class B Safety Standards: EN60950 or equivalent. Remote control monitoring and management interface (RCMMS) & operations: Should support Ethernet IP i) VoIP operation in line with EUROCAE ED137B, part 1 from RCMMS ii) Provide full operational control of the transmitter to RCMMS from local/ remote location over ATS network. iii) Support changing of transmitter operational parameters such as frequency, power etc from RCMMS iv) Provide monitoring of the transmitter parameters from the RCMMS

Page 20 of 29

PART 6. IP BASED VHF RECEIVER GROUND STATION S.NO. SPECIFICATIONS 6.1 Frequency Band:118MHz to 136.975MHz (Voice Mode & VDL mode 2 operation) 6.2 Channel Spacing: minimum 8.33 KHz & 25 KHz. 6.3 Modulation Mode: A3E at 8.33 KHz & 25 KHz Channel Spacing and D8PSK for VDL Mode 2 6.4 Frequency Stability: +1 ppm for operating temperature range 6.5 Receiver Protection: No permanent damage when subjected to in band signal up to +30 dBm @50 6.6 Signal dynamic: 98 dBm to +10 dBm and VDL2 for BER < 103 in line with ETSI EN301841-1, 6.7 Receiver Sensitivity (Voice Mode): -101 dBm 6.8 Receiver Selectivity: At 25 KHz. Channel spacing: 11 kHz/6 dB, 25 kHz/80 dB. At 8.33 KHz. Channel spacing: 3.5 kHz/6 dB, 25 kHz/80 dB, 6.9 Spurious Signal Rejection : >80 dB 6.10 Image Rejection: >100 dB 6.11 Adjacent Channel Rejection: at 25 kHz spacing: > 75dB & at 8.33kHz spacing: > 65 dB 6.12 Co-channel interference: VDL2 for BER = 103 < 20 dB; in line with ETSI EN 301841-1, 6.13 Conducted Spurious Emission: Better than 57 dBm 6.14 Digital audio interface: voice over IP (VoIP): in line with EUROCAE ED137B, part 1, Session control: SIP in line with EUROCAE ED137B part1 Audio stream: RTP in line with EUROCAE ED137B part1 Audio codec: in line with ITU-T G.711 6.15 Squelch: -107 to -70 dbm adjustable 6.16 Desensitization at f > 1 MHz; in line with ETSI EN 300676-1: > 95dB 6.17 Audio Frequency Response: 350-2500 Hz for channel spacing of 8.33 KHz & 300-3400 Hz for channel spacing of 25 KHz. 6.18 Audio Line Output:600 ohms, adjustable 30 dBm to +10 dBm. 6.19 Audio Distortion at Receiver Output <2% at 30% Modulation Depth 6.20 Audio Noise (S+N)/N better than 50 dB. 6.21 Controls & Indications: The receiver shall have the following minimum controls, indications and connectors: i) a visual indication for receiver switched on/off ii) a visual indication for squelch lifting (SQL). iii) Front panel LCD Display to display of various operational system parameters. iv) Provision to programme various Receiver Parameters such as Frequency/Channel/squelch/audio level v) Mode selection for 25 KHz, 8.33 KHz, AM, VDL Mode-2 operation. vi) RCMMS and operations: Ethernet IP vii) Headphone jack connector viii) Data interfaces for VDL Mode-2, ix) VoIP Interface as per EUROCAE ED137B part 1 x) RF Input Connector xi) USB/console port for maintenance 6.22 Operation on battery: Battery operation 24/28VDC (Automatic Switch Over from AC to DC in case of AC failure and vice versa) 6.23 Equipment Size 19 Rack Mounting Type or 19/2 or 19/4 1 to 3HU. 6.24 EMI/EMC Standards: as per ETSI EN 301489-1/22 and EN55022 class B 6.25 Safety Standards: EN60950 or equivalent. 6.26 Max. RF Input signal >+30dbm 6.27 RCMMS and operations: Support Ethernet IP i) Provide full control of the receiver from remote/local RCMMS location ii) Monitoring of the receiver parameters from RCMMS. iii) VoIP operation as per EUROCAE ED137B, part 1 from RCMMS iv) Allow changing of receiver parameters such as frequency etc from RCMMS.
Page 21 of 29

Part 7. 7.1

REMOTE CONTROL MONITORING AND MANAGEMENT SYSTEM (RCMMS) Qty 03 nos of Desktop based Remote Control Monitoring and Management System (RCMMS) and Qty 03 nos of ruggedized portable laptop based RCMMS shall be supplied as a part of complete RCMMS system for use over the AAI owned/leased ATS network. All the Remote Control Monitoring and Management Systems (RCMMS) offered against compliance to this shall be build on same make/model H/W & S/W and offer similar functionalities over the entire ATS network. One desktop based RCMMS each complete in its capability/functionality shall be supplied, installed, tested, commissioned (SITC) in each TWR, ACC, TBB building at IGIA Airport for maintenance/operational supervisors/personnel remote monitoring, control and management of entire VHF & VCCS/assets installation at all sites connected through ATS network. Each ruggedized portable laptop based RCMMS each complete in its capability/functionality shall be supplied in ready to use status over ATS Network environment for maintenance supervisors/personnel. Each RCMMS offered shall not be dependent in any way on any other RCMMS in the network for its complete functionality and its connectivity or disconnection of the each RCMMS shall be transparent to other RCMMS and ATS VCCS/VHF operator. Each RCMMS shall have capability to completely configure, control, manage, interrupt, manage (local/remote) VCCS System Components/connectivity interfaces along with connected various assets. RCMMS shall interfaces for Connection to may or may not compliant EUROCAE ED137B, part 1 network/interface i.e. interfaces to connect audio/control connection over E1/E3 or MPLS or IP based Ethernet network. Assets connected to VCCS can be similar/dissimilar makes analog/digital Radios, one or more service provider provisioned 2W/4W CB/E&M/V.35/PBX/EPABX/VoIP/TDM /MPLS etc local/trunk lines. RCMMS software shall use open RFC standards like SNMP protocol & shall be built using completely ruggedized portable commercial of the shelf (COTS) H/W & S/W components. RCMMS shall facilitate/allow complete monitoring & control of the connected each assets/system components in the ATS network environment. RCMMS shall use the ATS network environment sharing data and voice & shall not require any additional hardware for its functions of monitoring and controlling of the local/remote sites. RCMMS core H/W & S/W shall be designed to have sufficient H/W & S/W for system redundancy & shall be capable to perform for 24/7 & 365 days continuous functions without depending on other in built redundancy in ATS network/components. RCMMS software shall allow hierarchal login based login procedures and shall be SNMP based for configuring, control & monitoring using centralized authentication control over connected ATS Network. RCMMS shall allow overall status reports be sent to higher-levels of monitoring/ management system components via SNMP over connected ATS Network. The RCMMS system shall provide/display a complete situational overview of the ATS network system/assets through monitoring of all connected SNMP-capable devices. The RCMMS shall display/present system components layout be shown in tree view & map view. The tree/map view shall show the location, asset label and basic configuration/status of each component. These tree/map views shall allow capturing of detailed status of individual network connected components. Detailed view of each individual network connected components shall be quickly and easily selectable and manageable.

7.2 7.3

7.4 7.5

7.6 7.7 7.8 7.9 7.10 7.11 7.12

7.13 7.14 7.15 7.16 7.17 7.18 7.19

Page 22 of 29

7.20 7.21 7.22

7.23

7.24 7.25

7.26

7.27

7.28

7.29 7.30 7.31

7.32

7.33 7.34

RCMMS shall also allow few detailed/overview system parameters data recording/capturing (recording on open standards) for specific statistical analysis using third party applications/ applications provided by system provider. The RCMMS shall enable/allow operational/maintenance system administrators & maintenance personnel of ATS network/system to configure, monitor and control connected components from multiple distributed locations in ATS network. RCMMS shall allow sending of cost-effective quick ( IP unicast or multicast /SNMP) corrective messages in response to error conditions and shall provide the ability to set operational parameters and one touch configuration messages to each network element/ assets throughout the connected ATS network. The RCMMS software system shall be easy configurable and expandable by +50% or more without need of additional H/W, S/W or licenses and shall use Open RFC standards based IP protocols over ATS network/components/assets connected. The RCMMS should be capable of operating over any IP network and shall require no protocol/interface conversions for the IP assets/devices that support the SNMP based monitoring. The local connectivity within the TWR, TBB, ACC building or within local/remote radio sites having connectivity distance less than 05 KM shall be IP based and shall be supplied, laid, tested and commissioned by the vendor and shall form part of the ATS network. Ducts & Pits if any required shall be provisioned by AAI. IP Connectivity between the RCMMS locations and network assets sites where the IP radios, VCCS components and the SNMP supported devices such as Ethernet switches shall be via IP network built for Airports Authority of India (AAI) by the vendor through switches/routers/firewall/IDS etc to be supplied by vendor based on IP address/ label scheme provided by AAI system administrators. Leased TDM/MPLS Connectivity to remote radio sites and network elements shall be provided by AAI through Indian Telecommunication Service Provider with ground based networks (latency of 60-100ms or less) or satellite based networks (latency 600 ms) having E1/E3 or MPLS links. AAI shall make its best effort to obtain and provision best of the network connectivity available in India. The vendor shall also be responsible to supply, install, test and commission Network Time service in the ATS network i.e. NTP based time shall be available at each local & remote radio/VCCS/RCMMS sites part of the ATS network and same shall be used by AAI for its other display uses and purposes. The system time on the RCMMS shall be synchronized with the central/distributed time provisioning system by means of the NTP service/protocol. The RCMMS shall be capable of assigning various user levels authentication for accessing the labeling, renaming, monitoring, configuration and control of the devices/assets connected to the ATS network. The RCMMS system shall store all system events for the IP assets being monitored in a database. In addition to error messages and warnings, information such as user login or logout is also to be stored. This information is to be displayed in different tabular report form and shall the reports shall allow filtering according to various criteria set by the system administrator such as time frame, message type, and message code or radio name. It shall maintain the history of an individual asset or the entire system activities/status can be tracked at any time within 30 days. The RCMMS shall stores the incoming status messages from the radios in a database and can export them for external analysis. AAI can use this data for carrying out further detailed analysis to understand network behavior over a period of time, frequency of errors, usage of assets etc.. using standard DTP/Office S/W. The RCMMS shall enable detailed/comprehensive configuration, management, monitoring and control of various IP radio functionalities and the monitoring of the VCCS components and other SNMP supported devices. RCMMS shall allow radio parameters be easily set and/or changed in order to adapt the radio system to current/future operational needs by maintenance system administrators.
Page 23 of 29

7.35

In addition to monitoring, the radios shall also be managed by RCMMS system administrators without any interruption of the normal ATS monitoring/operation activities in progress by the ATS operational personnels. 7.36 RCMMS shall allow detailed/comprehensive monitoring of radios/assets and their operational parameters. All GUI shall be easy-to-use graphical user interface & shall provide an overview of the entire radio system as well as information regarding the status of each individual radio. 7.37 Information about each radio shall be displayed on the screen with specific colors to indicate the status of the link and the radio itself. The user-friendly interface shall make it easy to navigate between a complete network wide overview of the system and detailed information about each individual radio, including its parameters and status. 7.38 The following basic radio fundamental monitoring functions shall be available at all RCMMS positions in addition to configuration, control, management of assets over ATS network at all sites: i) display of radio's current overall state: ok, warning, error ii) display of status of current continuous built-in test (CBIT)/BITE, iii) display radio voltage, temperature iv) display of current local/remote link state v) display of current Go/NoGo state of each asset vi) display of current active/inactive state vii) display of current Transmitted power measurements viii) display of current VSWR measurement ix) display of current receiver levels setting x) Status (read-only) xi) display of current modulation measurement parameters xii) status of activation/deactivation of test tone xiii) display of internal event log list xiv) erasure of internal event log list xv) display and activation of preset page number xvi) display and setting of frequency xvii) display of modulation xviii) display and setting of channel spacing xix) display and setting of TX offset xx) display and setting of TX power xxi) display and setting of RX squelch xxii) activation/deactivation of radio and display of current setting xxiii) display of measured temperatures xxiv) display of measured voltages xxv) Measured values xxvi) display of measured audio levels xxvii) display of radio type xxviii) display of radio serial number xxix) display of installed radio options xxx) display of radio inventory xxxi) display if radio is configured for single-channel operation xxxii) display of list of configured blocked frequencies within radio xxxiii) display of configured installation information (user-defined text) xxxiv) display of configured location information (user-defined text) xxxv) display and setting of current date and time xxxvi) User rights management should be provided to allow the access rights to various users. xxxvii) Database support for event log and query facility for analysis. 7.39 RCMMS shall be capable of monitoring all relevant assets/components connected over the ATS network. The following details to be made available to RCMMS user: i) the overall state of each VCCS module/sub-modules/Line replaceable units ii) CPU load iii) Network bandwidth /traffic iv) Each parallel load sharing UPS complete status/control
Page 24 of 29

v) Recorder complete status/control RCMMS HARDWARE SPECIFICATIONS: Bidders must provide OEM MAF & authorization confirming the compliance to minimum or higher of each specification, for each named type of H/W along with the OEM authorization letter. 7.40.1 NTP SERVER: GPS/GLONASS satellite supported L1/L2/L5 freq band RACK MOUNTED dual ported NTP SERVER to maintain and display IP based NTP time across the ATS network shall be SITC by the supplier. NTP server shall act as a master clock with accuracy less than 20 ns in the network to which other clients shall interconnect over the network using NTP client software on Windows XP/7 or Linux OS and synchronize periodically. It shall take input from GPS/GLONASS satellites using externally mounted antenna and give outputs of NTP on dual IP 10/100 Base T IPv4/IPv6 Ethernet port, RS 485 port/ RS232 port and 1 PPS signal for dependent systems synchronization. It shall provide diagnostic and status ports/indications for Automatic/manual intervention. 7.40.2 RUGGEDIZED PORTABLE RCMMS: x86 BASED RUGGED TABLET OR RUGGED LAPTOP: 01 Numbers shall be SITC. Rugged Hardware shall be of Light weight, wireless, x86 based convertible powerful note book meeting MIL-STD-810G or IP 65 Standards. If it is laptop then it shall be convertible to tablet on fly. Hardware display screen shall be direct sun light readable/ viewable. Hardware casing shall be Full Magnesium Alloy Case with Hand Strap. Its HDD shall be Shock-proof mounted Flex-connect with Quick-release; It shall provide option for Bluetooth v2.1 + EDR (Class 1, ) Wi-Fi 802.11a/b/g/n, 3G or 4G Mobile Broadband. It shall be minimum based on Intel Core i5/i7 Processor or AMD equivalent or higher processor with 2 to 3.2 GHz Turbo Boost, Cache 3MB or more, 4GB DDR3-1333 RAM, 250 GB reinforced HDD, Flexible Input from Touch screen or dual touch (touch screen and digitizer models), Integrated stylus holder, 82-key with dedicated Windows key & Pressure-sensitive touchpad with scrolling support, Expansion slots like PC card type II, SD card (SDXC), Express Card/54 & Docking connector Dedicated 100-pin, External Interface like VGA D-sub 15-pin, Headphones/speaker Mini-jack stereo, Microphone/line in Mini-jack stereo, Serial D-sub 9-pin, External antenna connection (x 2) 50 ohm coaxial, USB 2.0 (x 2) 4-pin, IEEE 1394a (FireWire) 4-pin, 10/100/1000 Ethernet RJ-45 & 56K Modem RJ-11, Power supply of Lithium ion battery pack, Battery operation: 7 to 9 hours, full Battery charging time: 3.5 hours, AC Adapter: AC 100V-240V 50/60Hz, auto sensing/switching, Worldwide power supply type, and display of 10.1" XGA sunlight-viewable LED 1024 x 768 (touch screen or optional dual touch), Transflective Plus and CircuLumin technology AR, AG & circular polarizer, video controller, max. 1557MB shared VRAM with 32-bit, external video support up to 1280 x 1024 at 16.7 million colors and Concealed mode.. OPERATING SYSTEM: - latest x86 Windows or Linux or Unix & Antivirus: Lifetime free upgradable Antivirus for lifetime of system. Application HMI Password Controlled Software, All OS/Application/DBMS/Antivirus etc licenses shall be perpetual local machine licensed based, installable alongside the operating system. 7.40.3 DESKTOP BASED RCMMS shall be of the most recent computer technology and shall be inbuilt with following minimum requirements to meet DESKTOP RCMMS COTS requirements a) Minimum 64 bits high performance, RISC/CISC architecture, fully installed Two Quad Core Intel/AMD CPU operating at 2 GHz or more with 2x4MB Cache or more b) 1333MHz FSB with 08 GB of DDR-III RAM or more/better expandable up to 32 GB c) Motherboard: Latest Intel Chipset OEM Motherboard d) Chassis Type: Desktop/Rack type 7.40
Page 25 of 29

7.40.4

i)

ii)

iii)

SAS 10K RPM hot swappable Hard Disk in RAID 5 configuration having usable space of 500 GB or more. f) NIC - Four numbers of Gigabit Ethernet ports. (10/100/1000 Mbps) g) Free at least 2 x PCI express I/O slots. h) DVD RW Drive i) Hot Swappable dual redundant power supply. j) Inbuilt cooling system. k) If required, Rack mounts with rapid rail. l) USB optical Mouse with scroll /Keyboard m) 4 nos USB 2.0 or higher Ports and other Ports as required. n) Standard and HDMI/DVI-D video port connected to 21 or higher 16:9 LCD/LED lit intelligent monitors. o) Additional Other PCB/Modules hardware as per system design requirements. p) OS: UNIX/LINUX Enterprise /Windows Server latest version with 24X7 (Premium) support. q) Lifetime free upgradable Antivirus for lifetime of system r) Latest open RDBMS. s) The requirements stated above are bare minimum requirements. If the system performance and capabilities stated in this tender document requires a higher/ better hardware or any other module/component than the same shall be offered by bidder. 24 PORT LAYER 3 CORE SWITCHES : Layer 3 Switch shall meet the following minimum specifications:GENERAL FEATURES a) The switch shall be of Chassis type. b) Chassis shall have IPV4 and IPV6 in hardware. c) Chassis shall have minimum of 6 payload slots d) Chassis shall have Inbuilt minimum 18 copper ports of 10/100/1000 Mbps & 06 Fiber ports of 1Gbps e) Switch chassis shall be loaded with dual redundant active-active core CPU f) Minimum Switch Switching Fabric 600Gbps or more. g) Switch forwarding rate 340Mpps or higher h) Switch shall support Wire-speed multicasting for IPv4 & IPv6 traffic i) Support minimum 16K MAC addresses j) Support minimum 2 or 4K layer 2 multicast entries k) Support minimum 1K layer 3 IPv4 multicast entries l) Support minimum 4K VLANs m) Mean Time Between Failures: operation 5years on 365/24/7 or more n) Dual hot swappable PSUs with 1 + 1 redundancy o) Hot-swappable modules p) Hot swappable fan modules q) Switches shall support graceful restart for OSPF/BGP/IS-IS & in service software upgrade. RELIABILITY a) Mean Time Between Failures: operation 5years 365/24/7 or more b) Dual hot swappable PSUs with 1 + 1 redundancy c) Hot-swappable modules d) Hot swappable fan modules e) Switches shall support graceful restart for OSPF/BGP/IS-IS & in service software upgrade IEEE STANDARDS a) IGMPv3, Internet Group Management Protocol v2 (IGMPv2), PIMSM, OSPFv2 or equivalent b) IEEE 801v VLAN classification by protocol & port or equivalent e)
Page 26 of 29

iv)

v)

vi)

vii)

viii)

ix)

x)

xi)

IEEE 803ac VLAN tagging or equivalent RADIUS or equivalent RADIUS Accounting or equivalent RADIUS Attributes for Tunnel Protocol Support or equivalent IEEE 801p Priority Tagging or equivalent DiffServ Precedence for 8 queues/port or equivalent DiffServ Architecture or equivalent IEEE 802.d Spanning Tree Protocol (STP) - MAC Bridges or equivalent k) IEEE 801.1s Multiple Spanning Tree Protocol (MSTP) or equivalent l) IEEE 801t - 2001 801D maintenance or equivalent m) IEEE 801w - 2001 Rapid Spanning Tree Protocol (RSTP) or equivalent ROUTING a) Advanced routing protocol like IS-IS, RIPing, OSPFv3, BGPv4+, VRRPv3 b) Minimum 5K RIP routes c) Minimum 15K OSPF routes d) Minimum BGP routes e) Minimum 5K RIPng routes f) IPv6 routing option g) Minimum 4096 VLANs SECURITY a) 801x support b) Dynamic VLANs c) NAC or equivalent d) IDS protection like TAD or DoS or Equivalent e) BPDU Protection f) STP Root Guard g) RADIUS server QUALITY OF SERVICE a) Policy based QoS features b) Highly configurable traffic classification c) Mixed scheduling, to support complex traffic queuing requirements d) QoS queues per port e) Two-rate three-contrasting colors bandwidth metering, with burst sizes of 64 Kbps MANAGEMENT a) GUI b) Out of band 10/100/1000 Ethernet management port and console management port c) SSH and SNMPv3 for secure management d) Local RADIUS database and RADIUS Authentication ELECTRICAL APPROVALS AND COMPLIANCES a) EMC: EN55022 class A, FCC class A, VCCI class A b) Immunity: EN55024, EN61000-3-levels 2 (Harmonics), and 3 (Flicker) SAFETY a) Standards: UL60950-1, b) Certification: UL, cUL, TUV c) Restrictions on Hazardous Substances (RoHS) Compliance POWER CHARACTERISTICS a) AC Voltage: 100 to 240V (+/-10% auto ranging) b) Frequency: 47 to 63Hz c) Dual Redundant power supply (1+1 PSU) POWER CONSUMPTION: 1400W or less ; Voltage input 100- 240VAC, 47 to 63 Hz (auto ranging) ENVIRONMENTAL SPECIFICATIONS Operating Temperature Range: 0C to 50C c) d) e) f) g) h) i) j)
Page 27 of 29

a) b) c)
a) b) c) d) e) f)

a) b) c)

a) b) c) d) e)

a) b) c) d) e) f) a) b) c) d) e) f) g) a) b) c) d) e) f) g) h) i)

24 PORT LAYER 2 POE MANAGED SWITCHES PORT DENSITY a) 24-port POE 10/100/1000 Mbps and with minimum four SFP combo ports, one console port and separate stacking port. b) Uplink populated with four numbers of single modes fiber ports to connect to L3 core switches. c) Wire speed non blocking architecture & Wire-speed multicasting for IPv4 and IPv6 traffic d) Across Stack Link Aggregation ii) POWER OVER ETHERNET Provides standards based 802.3af Power over Ethernet to all 10/100/1000 ports, auto-negotiating & auto-cross Support for minimum 8, class 2 Powered devices at 7.3 watts iii) PERFORMANCE 64MB RAM 2048 or more VLAN ID 8,000 or more MAC address 45 Mpps or better forwarding rate Port Mirroring Stacking up to 5 L2 Switches iv) INTERFACE SUPPORT 10/100/1000-TX RJ-45 100-FX, 1000-SX/ LX/ ZX, 1000-LX SFP slot RJ45 or RS232 DB9 pin or male port or console port v) MANAGEMENT a) Industry Standard CLI b) Web Interface c) Secure encrypted WEB and CLI management with SSH v2 and SSL d) SNMP v3 vi) GENERAL FEATURES Single IP address Stack management Across Stack Link Aggregation VLAN configuration Port Mirroring Trunking across stack vii) QUALITY OF SERVICES 4 or more Priorities assigned to all queues 802.1p for Layer 2 QoS DSCP (Diffserv) for Layer 3 QoS 802.1p to DSCP remarking traffic Traffic prioritization using 802.1p, ToS, DSCP fields Strict Scheduling and Weighted Round Robin viii) SECURITY Guest or Private VLAN or equivalent SSHv2 for Telnet management SSLv3 for WEB management TACACS RADIUS Authentication IEEE 802.1x Port-based network access control Broadcast Storm Control ix) GENERAL STANDARDS or equivalent 802.1d Bridging 802.3x BackPressure/ Flow Control Redundancy Standards 802.1D Spanning Tree Protocol 802.1W Rapid Spanning Tree 802.1s Multiple Spanning Tree 802.3ad LACP Link Aggregation Static port trunk IGMP snooping v3 7.40.5 i)
Page 28 of 29

a) b) c) d) e) f)

a) b) c) d) e) f)

x) VLANs IEEE 802.1Q VLAN Tagging Up to 256 VLANs Port-based VLANs MAC-based VLANs Private VLANs GARP VLAN Registration Protocol (GVRP) xi) POWER CHARACTERISTICS Voltage input 100- 240VAC, 47 to 63 Hz (auto ranging) xii) ELECTRICAL/ MECHANICAL APPROVALS or equivalent Safety UL 1950 (UL/cUL), EN60950 (TUV) EMI FCC Class A, EN55022 Class A, VCCI Class A, C-Tick, EN61000-3-2, EN61000-3-3 Immunity EN55024 RoHS compliant xiii) ENVIRONMENTAL SPECIFICATIONS Operating Temperature Range: 0C to 50C S. No.
1) 2) 3) 4) 5)

ESTIMATED RCMMS H/W ITEMS ITEM DESCRIPTION NTP SERVER WITH ACCESSORIES PORTABLE RCMMS WITH ACCESSORIES DESKTOP RCMMS WITH ACCESSORIES LAYER 2 24 PORT POE MANAGED SWITCHES WITH ACCESSORIES LAYER 3 24 PORT CORE SWITCHES WITH ACCESSORIES

QTY 01 NO. 03 NO. 03 NO. 24 NO. 08 NO.

REFERENCE PARA

Page 29 of 29