package jssp/icb/2.3.2. telecommunication infrastructure … · 2020. 3. 21. · judicial system...

Judicial System Support Project

BIDDING DOCUMENTS # JSSP/ICB/2.3.2

Section VI “Technical Requirements (including Implementation Schedule)” 169

Package JSSP/ICB/2.3.2.

Telecommunication Infrastructure Development

In the Area of Departmental Telephone Network, Stage 1

Section VI. Technical requirements (including Implementation Schedule)

A. GENERAL INFORMATION ................................................................................... 172

A.1. Subject of this Contract ...................................................................................... 172

A.2. Payer ................................................................................................................. 172

A.3. Client ................................................................................................................. 172

A.4. Consignee .......................................................................................................... 172

A.5. Expected results ................................................................................................. 172

A.6. Primary objectives of the Client ......................................................................... 173

A.7. List of acronyms ................................................................................................ 173

B. FUNCTIONAL REQUIREMENTS .......................................................................... 176

B.1. Current Status .................................................................................................... 176

B.2. Main responsibilities of the Supplier .................................................................. 176

B.3. Main responsibilities of the Client ...................................................................... 176

B.4. General requirements to the DTN upgrade ......................................................... 177

C. TECHNICAL SPECIFICATIONS ............................................................................ 178

C.1. General requirements ......................................................................................... 178

C.1.1. Certification requirements ........................................................................... 178

C.1.2. Configuration requirements ........................................................................ 178

C.1.3. Requirements to unification and compatibility ............................................ 179

C.1.4. Requirements to the project team ................................................................ 179

C.2. Requirements to DTN upgrade kits .................................................................... 179

C.3. Requirements to PBX upgrade kits..................................................................... 180

C.3.1. Requirements to PBX upgrade kits #1-4, #7-8, #10, #12-16, #18, #21-32, #34-39, #42, #44, #46, #49-52, #54-56, #58, #61-68, #70, #72-74, #77-78, 82, #86-87, #92, #99

180

C.3.2. Requirements to PBX upgrade kits #5-6, #9, #11, #17, #19, #40-41, #45, #47-

48, #53, #57, #59-60, #71, #75-76, #89, #95 .................................................................... 180

C.4. Requirements to PBX upgrade kits #5-6, #9, #11, #17, #19, #40-41, #45, #47-48, #53, #57, #59-60, #71, #75-76, #89, #95 ............................................................................. 181

C.4.1. Technical requirements to the RL PBX ....................................................... 181




C.4.2. Requirements to the LL media gateways ..................................................... 183

C.4.3. Requirements to terminal devices ............................................................... 184

C.4.4. Requirements to telecommunications cabinets ............................................ 186

C.5. Requirements to the session border controller kit ............................................... 186

C.5.1. Requirements to SBC #1 ............................................................................. 187



C.6. Requirements to ACAS ...................................................................................... 188

C.6.1. Requirements to ACAS #1 .......................................................................... 189

C.6.2. Requirements to ACAS #2 .......................................................................... 190

C.7. Requirements to Installations #1-4 ..................................................................... 191

C.7.1. Installation #1 ............................................................................................. 191

C.7.2. Installation #2 ............................................................................................. 192

C.7.3. Installation #3 ............................................................................................. 193

C.7.4. Installation #4 ............................................................................................. 193

C.8. Requirements to the Detailed Design Documentation ......................................... 194

C.8.1. General requirements .................................................................................. 194

C.8.2. Requirements to Detailed Design Documentation #1 .................................. 194



D. TIME LINES AND SCOPE OF QUALITY ASSURANCE ...................................... 196

E. TESTING AND QUALITY ASSESSMENT ............................................................ 197

E.1. Quality control on delivery ................................................................................ 197

E.1.1. Check on delivery ....................................................................................... 197

E.2. Acceptance testing ............................................................................................. 197

E.2.1. Preparing for testing ................................................................................... 197

E.2.2. Acceptance testing for Installations #1-3 ..................................................... 198

E.2.3. Acceptance testing for Installation #4 ......................................................... 199

E.2.4. Consolidated Services Acceptance Certificate for Installations #1-4 ........... 199

F. IMPLEMENTATION PLAN .................................................................................... 200

F.1. Implementation schedule ................................................................................... 200

F.2. List of supplied goods ........................................................................................ 200

F.3. List of Services .................................................................................................. 203

G. TECHNICAL PROPOSAL FORMAT REQUIREMENTS ....................................... 205

G.1. Description of information technologies, materials, and other products and services 205




G.2. General requirements ......................................................................................... 205

G.3. Formats requirements......................................................................................... 205

G.4. Clarifications for each position of the Technical Requirements .......................... 206

G.5. Tentative Project Plan ........................................................................................ 206

H. TECHNICAL COMPLIANCE SHEET..................................................................... 207

H.1. Technical compliance sheet ............................................................................... 207

APPENDIX A. DESCRIPTION OF THE CURRENT INFRASTRUCTURE .................. 208

H.2. Solution architecture .......................................................................................... 208

H.3. Basic principles of DTN functioning .................................................................. 209

H.4. Description of the current DTN infrastructure .................................................... 210

H.4.1. Description of the Alcatel-Lucent OmniPCX Enterprise based technical solution for the FC PBX .................................................................................................. 210

H.4.2. Functional characteristics of the technical solution of FC PBX ................... 211

H.4.3. Description of the Alcatel-Lucent OmniPCX Enterprise based technical solution for the RL PBX .................................................................................................. 211

H.4.4. Functional characteristics of the technical solution at the regional level ...... 212

H.4.5. RL PBX of production other than Alcatel-Lucent ....................................... 212

H.4.6. Description of the Alcatel-Lucent OmniPCX Enterprise based technical

solution for the LL media gateways ................................................................................. 212

H.4.7. Functional characteristics of the technical solution at the local level ........... 213

H.4.8. Operated terminal devices ........................................................................... 213

APPENDIX B. PLACES OF DELIVERY OF DTN UPGRADE KITS ............................ 300

APPENDIX C. DTN UPGRADE KITS INSTALLATION SITES ................................... 305

APPENDIX D. REQUIREMENTS TO PBX UPGRADE KITS ....................................... 321




A. GENERAL INFORMATION

A.1. Subject of this Contract

The purpose of this contract is to develop departmental telephone network of the FBS of Rus-

sia by supplying DTN upgrade kits #1-19, #21-32, #34-42, #44-68, #70-78, #82, #86-87, #89,

#92, #95, #99 1, and to provide Installation services #1 -4.

A.2. Payer

The Payer is the Non-commercial Foundation for Enterprise Restructuring and Financial Insti-

tutions Development performing the functions of the Project Implementation Unit of the Judicial

System Support Project acting in the interests of the Client.

A.3. Client

The Client is the Federal Bailiffs Service, a federal executive body of the Russian Federation.

A.4. Consignee

The Consignee is the Central and Territorial Offices of the FBS of Russia, where the equip-

ment procured under the Project will be carried on the balance. The addresses of the Consignees

are given in APPENDIX B. PLACES OF DELIVERY OF DTN UPGRADE KITS.

A.5. Expected results

It is expected that development of the departmental telephone network of the FBS of Russia

will result in the following changes in the performance of the FBS of Russia:

increased availability of information on public services provided by the FBS of Russia;

improved provision of information on public services (functions) provided by the FBS of Russia, including addresses, phones, working schedules of the FBS of Russia, its territorial

offices and structural units;

reduced time and financial costs of citizens and organizations required to obtain public services through awareness raising and speeding up the documents preparation process;

informing about the procedure for providing public services, including dates, requirements to the necessary documents, as well as the public servants, higher authorities

responsible for provision of public services;

organization of a convenient channel of telephone communication for citizens and organization to request information;

informing citizens and organizations about the procedure of challenging the actions (inaction) of the Agency’s officials when providing public services;

increasing efficiency and quality of communication between the agencies of the federal, regional and local levels;

reduction of costs of long-distance calls related to the interaction of geographically distributed structural units through the use of a private telecommunications network.

1 Here and elsewhere, the numbering of the DTN upgrade kits corresponds to the numbering of the Russian re-

gions as established in the registry of regional car codes of the State Traffic Safety Inspectorate.




A.6. Primary objectives of the Client

The Federal Bailiffs Service is a federal executive body (Project Participant) that performs

functions to support the established order of courts’ operation, enforcement of judicial acts, acts

of other bodies and officials, as well as law enforcement and control and supervisory functions

within the assigned area of activity.

Primary objectives of the FBS of Russia are as follows:

ensure the established order of operation of the Constitutional Court of the Russian Federation, the Supreme Court of the Russian Federation, courts of general jurisdiction and

arbitration courts;

organize enforcement of judicial acts of the courts of general jurisdiction and arbitration courts, as well as acts of other bodies stipulated by Russian laws on enforcement proceedings;

enforce the criminal procedure laws under the cases referred to the jurisdiction of the Federal Bailiffs Service by the Russian criminal procedure laws;

manage the regional offices of the FBS of Russia;

maintain the public registry;

perform the federal state control (oversight) of the activities of legal entities (included in the State Register) whose main activity is related to the past due debt recovery.

A.7. List of acronyms

Acro-

nyms

Definition Explanation

AA Automated Attendant

ABC-F Alcatel-Lucent Business Com-

munication Networking protocol

A networking protocol with extended functional

capabilities

ACT Alcatel-Lucent Crystal Tech-

nology

A technology for combining station boards based

on the “fully connected” principle through a 2

Mbit/s channel

AD Active Directory A corporate directory

ARS Automatic Route Selection Automatic call routing

CAC Call Admission Control

CDR Call Detail Record A detailed record of a phone call

CIFS Common Internet File System A shared file system for data exchange in the net-

work

DDoS Distributed Denial of Service Distributed denial of service

DECT Digital Enhanced Cordless Tel-

ecommunication Cordless technology at 18801900 MHz

DoS Denial of Service

DSP Digital signal processor

DTMF Dual-Tone Multi-Frequency A dual-tone multi-frequency analog signal

EDSS European Digital Subscriber

Signalling A telephony signalling protocol

ETSI European Telecommunications

Standards Institute

FTP File Transfer Protocol




Acro-

nyms


FXO Foreign eXchange Office An analog interface of subscriber devices of tele-

phone stations

FXS Foreign Exchange Sta-

tion/Subscriber

A voice interface or port, emulating the PBX ex-

pansion interface

GAP Generic Access Profile A set of mandatory requirements for compliance

with the DECT standard

HTTP HyperText Transfer Protocol

HTTPS HyperText Transfer Protocol

Secure

An HTTP protocol extension to support encryption

for improved security

IDS Intrusion Detection System

IEEE Institute of Electrical and Elec-

tronics Engineers

IP Internet Protocol A routable TCP/IP network protocol

ISDN Integrated System Digital Net-

work

IVR Interactive Voice Response An interactive voice menu

LAN Local Area Network A local computer network

LDAP Lightweight Directory Access

Protocol An AD access protocol

LLDP-

MED

Link Layer Discovery Protocol-

Media Endpoint Discovery A data link level protocol

PBX Private Branch eXchange A corporate communication system

PCS Passive Communication Server A local backup server

QoS Quality of Service

QSIG Q-Point Signalling System A symmetric signalling protocol for private tele-

phone networks

RFC Request for Comments Technical specifications and recommendations

SBC Session Border Controller

SD Secure Digital A flash memory card format

SFTP Secured File Transfer Protocol

SIP Session Initiation Protocol A sessions initiation protocol for IP telephony

SMB Server Message Block A server message block protocol

SNMP Simple Network Management

Protocol A network management protocol

SSH Secure Shell A secure command line access protocol

SysLog System log

TCP Transmission Control Protocol

TDM Time Division Multiplexing

Telnet Teletype network A command line access protocol

TFTP Trivial File Transfer Protocol A file transfer protocol

UDP User Datagram Protocol

USB Universal Serial Bus A serial data transfer interface

VLAN Virtual Local Area Network A group of devices which can communicate with

each other directly on the link layer




Acro-

nyms


VoIP Voice over IP A technology of voice transmission over IP net-

work

XML eXtensible Markup Language

ANI Automatic Number Identifier

ACAS Automated Call Accounting

System

DTN Departmental Telephone Net-

work

GOST State Standard

ATS Additional Types of Services

UPS Uninterruptible Power Supply

WS Work Sites (APPENDIX C)

LL Local Level

SBC Session Border Controller

RL Regional Level

SanPiN Sanitary Norms and Regulations

SNiP Construction Norms and Regu-

lations

TA Telephone Apparatus

ToR Terms of Reference

PTN Public Telephone Network

PBX Private Branch eXchange

OFBS Office of the Federal Bailiffs

Service

FD Federal District

FBS Federal Bailiffs Service

FC Federal Center

http://www.tehdoc.ru/sanitary.htm




B. FUNCTIONAL REQUIREMENTS

B.1. Current Status

The current system of the Departmental Telephone Network (DTM) of the FBS of Russia en-

sures comprehensive telephone communications of the staff with both wire and wireless (DECT)

telephone sets, and also provides for the possibility to use advanced IP services and applications.

The DTN architecture is based on modern technologies and generally accepted open system

concepts, which allow easy modification and scaling of this solution, both in terms of quantity

and quality, while preserving the invested capital. The departmental telephone network of the

FBS of Russia is based on a network of interrelated private branch exchanges (PBX) providing

for reliable and effective communication. The DTN of the FBS of Russia is based on three lev-

els:

the level of the Federal Center (FC) - PBX located in the Administrative Offices of the FBS of Russia in Moscow (Central Office), Nizhny Novgorod, St. Petersburg, Rostov-

on-Don, Ekaterinburg, Novosibirsk, and Khabarovsk;

regional level (RL) - PBX located in the Administrative Offices of the FBS of Russia in the regional capitals in line with the accepted administrative division of Russia;

local level (LL) - Bailiffs Departments in the region population centers in line with the generally accepted regional division of Russia.

The routing of calls in the DTN enables making long-distance calls to any federal city num-

bers not on the call initiator’s node but as close to the location of the dialed landline number as

possible. This reduces the cost of long-distance communications as the caller and dialed landline

phone number are actually located (from the point of view of the public telephone network)

within one tariff zone.

The detailed description of the current DTN infrastructure of the PTS is given in APPENDIX

A.

B.2. Main responsibilities of the Supplier

The main responsibilities of the Supplier include the following:

Deliver DTN upgrade kits #1 -19, #21-32, #34-42, #44-#70, 68-78, #82, #86-87, #89, #92, #95, #99, consistent with the functional requirements of this section and technical

requirements of section C for the sites referred to in APPENDIX B (hereinafter, Sites of

Delivery);

Provide Installation Services #1-4 pursuant to the requirements of section C.7 at the Work Sites mentioned in APPENDIX C (hereinafter, Work Sites);

Prepare detailed design documentation pursuant to the requirements of section C.8;

Provide warranty service pursuant to the requirements of section D;

Carry out acceptance testing pursuant to the requirements of section E.2.

B.3. Main responsibilities of the Client

The main responsibilities of the Client include the following:

Ensure that the Supplier has administrative access to the upgraded equipment and organ-ize physical access of the Supplier’s staff to the Work Site during the time of Installations

#1 -4.




Hand over the equipment to the Supplier to perform Installations #1 -4.

Provide information on changes in the addresses of places of delivery of DTN upgrade kits (as specified in APPENDIX B) and DTN upgrade kits installation sites (as specified

in APPENDIX C) within 2 (two) business days from the date of change in the addresses

of each site.

B.4. General requirements to the DTN upgrade

1) DTN upgrade kits #1 -19, #21-32, #34-42, #44-#70, 68-78, #82, #86-87, #89, #92, #95, #99 should be compatible with the upgraded equipment and improve its functionality by integrat-

ing into the existing technical infrastructure of the departmental telephone network of the

FBS of Russia.

2) The departmental telephone network of the FBS of Russia should be based on the current tel-ecommunications infrastructure of the FBS of Russia.

3) The DTN upgrade kits should be supplied with free new software versions (in accordance with the new version release schedule and the manufacturer’s license agreement) and up-

dates, patches for error handling during 24 months.

4) The process of DTN upgrading should ensure integration with the existing PBX at the FC and RL while maintaining the current level of the DTN functionality.

5) The DTN should operate under a single numbering plan supporting seven-digit subscriber numbers in line with the DTN Numbering Plan of the FBS of Russia provided by the Client.

6) The DTN of the FBS of Russia should be a single network of the VoIP-based package of equipment.

7) The DTN upgrade should be based on the three standard levels of equipment:

Federal Center (FC);

Regional Level (RL);

Local Level (RL);

8) The current fully-meshed topology of the DTN should be kept between all FC PBX and tele-phone sub-networks subject to the availability of appropriate communication channels pro-

vided by the Client.

9) Interaction between any two PBX of the DNT of the FBS of Russia via communication channels should not depend on the availability of any other PBX of the departmental network

(or their telecommunication nodes).

10) The upgrade should result in the creation of a centralized automated call accounting sys-tem.

11) The upgrade should result in a possibility to route calls to DEF numbers through SIP trunks.




C. TECHNICAL SPECIFICATIONS

C.1. General requirements

1) All equipment and each unit supplied under these requirements shall:

be supplied in the manufacturer’s packaging appropriate to the nature of the equipment and the method of its transportation, protecting the equipment against damage and loss of

presentation during its delivery, with the reference tape and control sheet for each cargo

space;

be factory-assembled, have a trademark, not be restored and not assembled from second-hand parts, be made no earlier than in 2018.

by its functional features (consumer properties), qualitative characteristics and complete-ness, conform to the technical requirements of the Client specified in these requirements

or exceed them, which should be supported by technical documentation of the equipment

manufacturer;

be serially produced for at least 6 (six) months prior to the bidding;

have technical documentation established by the manufacturer of this equipment, as well as certificates of quality, compliance and other documents established by Russian laws

for this type of equipment;

2) All supplied equipment should be stationary and intended for connection to an electrical dis-tribution network with the following characteristics:

voltage – 220 V/230 V;

frequency – 50 Hz.

3) The list of equipment defined below can be extended by the Supplier with additional soft-ware or hardware components if this is necessary to meet the Technical Requirements.

C.1.1. Certification requirements

1) For all delivered PBX, the Supplier shall provide a certificate of conformity of the public tel-ecommunication networks used as departmental private branch exchange based on the circuit

switching and packet switching technology to the Rules of Applying Departmental Private

Branch Exchanges approved by Order of the Ministry of Information Technology and Com-

munications of the Russian Federation # 51 of April 29, 2008, as amended by Order of the

Ministry of Information Technology and Communications of the Russian Federation # 93 of

April 23, 2013.

2) For all delivered DECT base station, the Supplier shall provide a declaration of conformity with the Rules of Applying Terminal Equipment Performing the Functions of Switching Sys-

tems, approved by Order of the Ministry of Information Technology and Communications of

the Russian Federation # 113 of August 24, 2006.

C.1.2. Configuration requirements

1) The Supplier shall ensure that the proposed hardware and software is operational and shall include all components necessary to ensure this requirement into the scope of delivery.

2) All active hardware should be provided with cable connections to perform commissioning and operation.




3) DTN upgrade kits, where applicable, shall be supplied with electric cables to connect to the Schuko type sockets.

4) DTN upgrade kits #1-19, #21-32, #34-42, #44-68, #70-78, #82, #86-87, #89, #92, #95, #99 shall be supplied with all the necessary consumables for passive switching.

5) DTN upgrade kits #1-19, #21-32, #34-42, #44-68, #70-78, #82, #86-87, #89, #92, #95, #99 shall be supplied with all necessary mounting materials, including telecommunication cabi-

nets for RL PBX and LL media gateways according to APPENDIX D if the existing tele-

communication cabinets at the installation sites do not have sufficient space to accommodate

the equipment.

C.1.3. Requirements to unification and compatibility

1) PBX upgrade kits #1-19, #21-32, #34-42, #44-68, #70-78, #82, #86-87, #89, #92, #95, #99 (APPENDIX D) should be compatible with the equipment available at the FBS (APPENDIX

A, Table 13) subject to maintaining the current functionality and implementation of the func-

tional requirements of these Terms of Reference. It is permitted to replace the existing

equipment (APPENDIX A, Table 13) subject to implementation of the functional require-

ments of these Technical Requirements.

2) The RL PBX (para. C.2), LL media gateways (para. C.4.2) and TA #1 -4 (para. C.4.3) shall be of the same manufacturer.

C.1.4. Requirements to the project team

1) The Supplier shall have a qualified project team capable of providing all the services speci-fied in the Technical Requirements. The project team members shall have relevant certifi-

cates issued by the manufacturers of the equipment specified below.

2) The minimum number of the Supplier’s specialists certified by the manufacturer of the sup-plied DTN upgrade kits #1 -19, #21-32, #34-42, #44-#70, 68-78, #82, #86-87, #89, #92, #95,

#99 shall be as follows:

─ Alcatel-Lucent System Expert or similar expert certificate from another manufacturer in the case of complete replacement of the existing PBX – 2 specialists;

─ Alcatel-Lucent Field Engineer or similar professional certificate from another manu-facturer in the case of complete replacement of the PBX – 2 specialists;

3) All specialists proposed in the bid must be available to provide services during the contract execution.

C.2. Requirements to DTN upgrade kits

1) DTN upgrade kits #1 -19 PTS, #21-32, #34-42, #44-#70, 68-78, #82, #86-87, #89, #92, #95, #99 shall ensure expansion of the existing functionality of the existing DTN.

2) The contents of DTN upgrade kits #1 -19, #21-32, #34-42, #44-#70, 68-78, #82, #86-87, #89, #92, #95, #99 for each Delivery Site is specified in REQUIREMENTS TO PBX UPGRADE

KITS.

3) DTN upgrade kits #2, #16, #24, #34, #36, #52, #54, #55, #59, #61, #63, #66, #74, #77, #78, #99 shall consist of:




1 PBX upgrade kit;

1 SBC kit;

1 ACAS kit.

4) DTN upgrade kits #1, #3-4, #7-8, #10, #12-15, #18, #21-23, #25-32, #35, #37-39, #42, #44, #46, #49-51, #56, #58, #62, #64-65, #67-68, #70, #72-73, #82, #86-87, #92 shall consist of:

1 PBX upgrade kit;

1 ACAS kit.

5) DTN upgrade kits #8, #82, #92 shall consist of:

1 ACAS kit.

C.3. Requirements to PBX upgrade kits

C.3.1. Requirements to PBX upgrade kits #1-4, #7-8, #10, #12-16, #18, #21-32, #34-39, #42, #44, #46, #49-52, #54-56, #58, #61-68, #70, #72-74, #77-78, 82, #86-

87, #92, #99

1) PBX upgrade kits can be implemented through enhancement of the existing PBX or through their complete replacement.

2) In the case of enhancement or total replacement of the existing PBX, the functional charac-teristics of the existing equipment (para. A2-A3, APPENDIX A) that will not be replaced by

the Supplier, and all current interfaces between PBX of the FC level and Regional Level

should be fully preserved.

3) In the case of total replacement of the existing PBX, the PBX upgrade kits should include the necessary network infrastructure equipment (servers, media gateways, UPS, telecommunica-

tion cabinets, etc.) and TA in the amount not less than that indicated in Tables 1-3 APPEN-

DIX A and ensure registration and service capability of telephone terminals.

4) PBX upgrade kits #1-4, #7-8, #10, #12-16, #18, #21-32, #34-39, #42, #44, #46, #49-52, #54-56, #58, #61-68, #70, #72-74, #77-78, #82, #86-87, #92, #99 shall include ТА#3 including

activation keys to ensure their operation in the amount pursuant to REQUIREMENTS TO

PBX UPGRADE KITS.

C.3.2. Requirements to PBX upgrade kits #5-6, #9, #11, #17, #19, #40-41, #45, #47-48, #53, #57, #59-60, #71, #75-76, #89, #95

1) PBX upgrade kits should include the necessary network infrastructure equipment (servers, media gateways, UPS, telecommunication cabinets, etc.), and TA including activation keys

to ensure efficiency of the equipment package pursuant to APPENDIX D.

2) PBX upgrade kits #5 -6, #9, #11, #17, #19, #40-41, #45, #47-48, #53, #57, #59 -60, #71, #75-76, #89, #95 shall include:

RL PBX – 1 set

media gateways # 1-6 (hereinafter, the LL Media Gateways) – in the quantity pursuant to APPENDIX D;

terminal devices (TA #1 -4) – in the quantity pursuant to APPENDIX D;

telecommunication cabinets – in the quantity pursuant to APPENDIX D.




C.4. Requirements to PBX upgrade kits #5-6, #9, #11, #17, #19, #40-41, #45, #47-48, #53, #57, #59-60, #71, #75-76, #89, #95

C.4.1. Technical requirements to the RL PBX

1) The RL PBX shall include the following systems:

call management system;

DECT communications system;

RL PBX management system;

2) Subscriber capacity RL PBX should have scaling capacity of up to 15 000 and more sub-scribers.

3) RL PBX should be modular with uniform structural elements and standardized modules to connect subscribers, lines and host software.

4) RL PBX should enable use of telephones of different modifications (including IP telephone terminals and software based telephones), analogue telephones and fax machines, SIP termi-

nals.

5) RL PBX should support the Session Initiation Protocol (SIP).

6) RL PBX should support the operation of the DECT system.

7) RL PBX should support marking of IP packets to ensure functioning of the quality of service (QoS) mechanisms in the network, and also support CAC (Call Admission Control).

8) RL PBX should support connection to the PTN through analogue and digital interfaces: E1 ISDN PRI (EDSS-1), 2-wire analog trunks.

9) RL PBX shall have built-in voice response/auto attendant with a possibility to create a multi-level access to subscribers.

10) The RL PBX call management components shall ensure control of distributed media gate-ways.

11) Media gateways should be an integral part of the RL PBX.

12) The central processor device of the RL PBX shall be based on the Intel server platform rec-ommended by the solution manufacturer and accommodated structurally in a 19" rack.

13) The central processor device of the RL PBX shall ensure a fault-tolerant active-active opera-tion mode.

14) The equipment of the RL PBX shall support at least 1 hour of continuous work in the event of power failure.

15) All installed software of the RL PBX shall be of the most relevant (last) version at the time of DTN upgrade kits.

16) The Supplier shall deliver the RL PBX to the sites pursuant to APPENDIX B in the quantity and in line with the specification as stated in APPENDIX D.

C.4.1.1. Technical requirements to the calls management system

1) The call management system of the RL PBX shall support the following subscriber telephony services:




a unified numbering plan supporting a 7-digit internal subscriber number;

presentation of the number and name of the calling person on IP phones in Russian;

call hold/return;

redirecting a call to another subscriber;

conditional and unconditional call forwarding;

organization of conference calls;

call parking;

return call if the subscriber is busy or unavailable;

alerting on the second incoming call;

call intrusion;

call interception (pickup);

list of missed calls to IP phones;

speed dialing using abbreviated notation;

searching for the number and organizing a call by name (including Cyrillic characters) from a built-in keyboard for IP phones that support this functionality;

supporting security features (PIN-code to call a certain number, access to connectors, etc.);

supporting Cyrillic characters on the IP phone menu;

Russian interface on all IP phones including Russians voice prompts for ease of use of telephone sets and services;

a multiline service on the telephone set supporting the number of lines equal to the num-ber of function keys on IP phones;

organizing a conference call with at least 29 subscribers simultaneously.

C.4.1.2. Technical requirements to the DECT communications system of RL PBX

1) The DECT communications system of RL PBX should support:

connection of DECT terminals as fully-featured terminals of RL PBX;

RL PBX integration with the full circuit management at DECT terminals, single number-ing plan and delivery of subscriber’s number and name.

at least 11 simultaneous conversations per one DECT base station;

redirect calls on DECT telephone sets;

seamless (without interrupting the connection and deterioration in the communication quality) switching of DECT terminals between base stations during conversation – hand-

over;

wireless (without using specialized devices for subscriber terminals connection) updates of microcodes of DECT telephone sets;

roaming of DECT terminals in the RL-LL-segment;

centralized data backup and recovery for microcellular DECT subscribers;

use of a centralized corporate phone book.

C.4.1.3. Technical requirements to the PBX control system

1) The control system shall constitute a single centralized management, administration and monitoring system regardless of the number of units and the total port capacity of the RL

PBX with a single operator work station based on the software of the control server manufac-

turer.




2) The RL PBX control system shall ensure management of all elements of the RL-LL segment.

3) The RL PBX control system shall enable single centralized collection of statistics and moni-toring of alarms from all outstations of the PBX port capacity allowing the operator to regis-

ter alarms and load voice IP channels of the backhaul network.

C.4.2. Requirements to the LL media gateways

1) LL media gateways should ensure the following subscriber telephony services:

a unified numbering plan supporting a 7-digit internal subscriber number;

presentation of the number and name of the calling person on IP phones in Russian;

call hold/return;

redirecting a call to another subscriber;

conditional and unconditional call forwarding;

organization of conference calls;

call parking;

return call if the subscriber is busy or unavailable;

alerting on the second incoming call;

call intrusion;

call interception (pickup);

list of missed calls to IP phones;

speed dialing using abbreviated notation;

searching for the number and organizing a call by name (including Cyrillic characters) from a built-in keyboard for IP phones that support this functionality;

supporting security features (PIN-code to call a certain number, access to connectors, etc.);

supporting Cyrillic characters on the IP phone menu;

Russian interface on all IP phones including Russians voice prompts for ease of use of telephone sets and services;

a multiline service on the telephone set supporting the number of lines equal to the num-ber of function keys on IP phones.

2) The equipment of the LL media gateway should support at least 30 days of continuous work in the event of failure of the signal channel of communication with the central processor unit.

3) The equipment of the LL media gateway should support at least 1 hour of continuous work in the event of power failure.

4) The Supplier shall deliver media gateways #1-6 to the Site of Delivery pursuant to APPEN-DIX B with a breakdown by types and quantity pursuant to REQUIREMENTS TO PBX

UPGRADE KITS

C.4.2.1. Requirements to media gateway #1

1) Media gateway #1 should meet the following requirements:

availability of interfaces to connect to the PTN through eight analog trunks;

supporting continuous operation of subscribers of the LL segment in the event of failure of the signal channel with the central processor unit;






availability of interfaces to connect to the PTN through 12 analog trunks;


















C.4.3. Requirements to terminal devices

C.4.3.1. Requirements to ТА #1

1) TA #1 should meet the following requirements:

support of the SIPv2 communication protocol;

supported audio codecs: G.711a, G.711μ, G.729AB, G722;

availability of a color 3.5 inches or more LCD with a resolution of at least 240 x 320 pix-el;

Russian language support of the phone menu;

possibility to dial subscribers by name;

presence of functional keys: volume up and down, speakerphone, mute key, call release, redial;

availability of at least programmable keys with LED indication;

possibility to connect expansion modules with at least 50 programmable keys in total;

possibility to program at least 68 speed dial entries;

LLDP-MED support;




a built-in switch with at least two Ethernet 10/100/1000 Base-T interfaces with a possibil-ity of ports partitioning in VLAN;

support of Power over Ethernet (IEEE 802.3a);

power supply unit included;

possibility of a headset connection.




support of audiocodecs: G.711a, G.711μ, G.729AB, G.722;

availability of a 2.8 inches or more LCD with a resolution of at least 64x128 pixel;



functional keys: volume up and down, speakerphone, mute key, call release, redial;

availability of at least programmable keys with LED indication;

possibility to connect expansion modules with at least 50 programmable keys in total;

possibility to program at least 68 speed dial entries;

LLDP-MED support;

a built-in switch with at least two Ethernet 10/100/1000 Base-T interfaces with a possibil-ity of ports partitioning in VLAN;







support at least two SIP accounts;

support of audiocodecs G.711a, G.711μ, G.729AB, G.722;



functional keys: volume up and down, speakerphone, mute key, redial;

LLDP-MED support;

a built-in switch with at least two Ethernet 10/100 Base-T interfaces with a possibility of ports partitioning in VLAN;






support of the GAP protocol;



possibility of a headset connection;

support of the wireless firmware program update;




missed call/voice mail receipt indication;

vibro call support;

talk time - 17 hours and more;

standby time - 160 hours and more;

charger included.

C.4.4. Requirements to telecommunications cabinets

C.4.4.1. Requirements to telecommunications cabinet #1

1) Telecommunications cabinet #1 should meet the following requirements:

compliance with industry standard EIA-310-E;

width at least 600 mm;

depth at least 800 mm;

height at least 2065 mm;

load capacity at least 830 kg.

C.4.4.2. Requirements to telecommunications cabinet #2

1) Telecommunications cabinet #2 shall meet the following requirements:

compliance with industry standard EIA-310-E.

width at least 600 mm;

depth at least 800 mm;

height at least 1405 mm;

load capacity at least 730 kg.

C.5. Requirements to the session border controller kit

1) The session border controller kit for each Delivery Site includes the types and quantity of the session border controller (SBC #1-3) as indicated in REQUIREMENTS TO PBX UP-

GRADE KITS.

2) SBC #1-3 shall support SIP trunk connection based on UDP and TCP transport protocols.

3) SBC #1 -3 shall be able to convert between the RTP and SRTP protocols.

4) SBC #1 -3 shall support the following audio codecs: G.711, G.723.1, G.726, G.729, G.722.

5) SBC #1 -3 shall support the SIP message manipulation:

add title;

delete title;

changing title and/or title parameter;

manipulation of messages based on regular expressions;

title manipulation depending on the type of message (Request/Response);

manipulation of titles depending on the method of communication;

relocation of the parameter values from one title to another;

use of variables to relocate values from one message to another.

6) SBC #1-3 shall support filtering (qualification) of messages based on:

IP address;

type of transport protocol;




inbound SIP interface;

value of a particular parameter set based on regular expressions.

7) SBC #1 -3 shall support registration of up to 1 500 users;

8) SBC #1 -3 shall support SIPRec.

9) SBC #1 -3 shall support echo compensation.

10) SBC #1 -3 shall ensure routing based on:

A-number;

B-number;

source IP address;

LDAP data;

external routing information file.

11) SBC #1 -3 shall ensure control of the HTTP/HTTPS protocol, console port, remote access SSH/Telnet protocols, SNMP protocol.

12) SBC #1 -3 shall ensure access control:

by IP addresses;

based on local account: login/password;

based on the RADIUS protocol

by LDAP.

13) SBC #1-3 shall ensure calls reporting and recording (Call Detail Record - CDR);

14) SBC #1-3 shall ensure collection and viewing of accounting information locally and through a web interface.

15) SBC #1-3 shall ensure collection of accounting information using the SysLog Protocol.

16) SBC #1-3 shall ensure filtering of the collected reports.

17) SBC #1-3 shall support IDS (Intrusion Detection System) to protect from DoS/DDoS (Denial of Service/Distributed Denial of Service) attacks.

18) SBC #1-3 shall support RestAPI to control the rules of SBC routing from an external source.

19) The structural elements of SBC #1-3 shall be designed for mounting in a standard 19"rack, the height of the structural elements shall not be more than 1U.

20) SBC #1-3 shall be powered from a 220V/5060Hz AC network.

21) SBC #1-3 shall have at least 2 pairs of 100/1000 Base-T Ethernet ports operating in an ac-tive/standby mode for physical separation between LAN and WAN.

C.5.1. Requirements to SBC #1

1) SBC #1 shall support processing of at least 50 SIP sessions.








C.6. Requirements to ACAS

1) The set of an automated calls accounting system (ACAS) for each Delivery Site includes the ACAS #1-2 with a breakdown by types and quantity according to REQUIREMENTS TO

PBX UPGRADE KITS.

2) The ACAS is a hardware and software package ensuring a centralized charging for telecom-munication services consumed by the Client based on the geographically distributed network

- FC/RL PBX.

3) The ACAS should be capable to provide automated calls analytics in the following modes:

visualization in the form of graphs and/or diagrams;

downloaded analytical reports.

4) Calls statistics should be collected through a module for collection and storage of calls statis-tics individually for each PBX.

5) The ACAS shall contain the following mechanisms of CDR processing:

PBX prefix assignment;

substitution in the phone numbers for their normalization.

6) The subscriber base, the numbering capacity and tariffs in the ACAS should have the follow-ing capabilities:

maintaining a centralized base of subscribers;

using time-based and unlimited tariffs for all types of connections (copper pair, E1 stream, SIP);

rating based on directions;

rating based on the time zones of PBX installation sites;

charging for additional types of services;

charging for fee-based information services (09 009, etc.);

maintenance of the database of the numbering capacity;

adding supplementary lines to the subscriber’s number;

assigning multiple phone numbers to the subscriber, including ranges;

establishment of tariffs with the required number of chargeable areas, manually and au-tomatically (import of tariffs).

7) The ACAS shall support collection of calls statistics from the PBX (individually for each of the PBX) in the following modes:

active mode: TCP socket in standby mode (IP, RS232) or Telnet connection.

passive mode: TCP socket in standby mode for connections (IP, RS232);

collection from remote network drives: by FTP, SFTP, SMB, CIFS protocols.

8) The ACAS shall be able to import tariffs received from the operator (in an approved format).

9) The ACAS shall support an unlimited number of tariff plans, including packages and numer-ous types of discount plans;

10) The ACAS shall support the functionality of tariff export.




11) The ACAS shall support the functionality of verifying the volume of services rendered and detailed reports.

12) The ACAS shall have a certificate of conformity to the “Rules of Application of Automated Calculation Systems” approved order of the Ministry of Information Technology and Com-

munications of the Russian Federation of July 02, 2007 for communication network as an au-

tomated system of settlements up to a hundred thousand subscribers.

13) The ACAS shall support a hierarchical organizational structure with a single billing account.

14) The ACAS shall support data archiving.

15) The ACAS shall support multiple billing of call detail records (CDR).

16) The ACAS shall have a web interface for management.

17) The ACAS shall be able to download reports in PDF or CSV formats.

18) The ACAS shall support identification of subscribers by telephone numbers, by the trunk group numbers, by combination of the phone number and the trunk group, and by IP address-

es of software switches.

19) The ACAS shall support automatic generation of reports and their distribution by email.

20) The ACAS shall support the system of differentiation of user access rights.

21) The ACAS shall support processing of calls of at least 50,000 internal subscribers.

22) Computing systems ACAS#1 and ACAS #2 have equally acceptable to the Client methods to confirm the required performance of the proposed models base on the

SPECint_rate_base2006 test:

confirmation at www.spec.org;

the proposed server model has the same or a larger number of processors of the same type (with the same trademark) with the same or greater operating frequency, with the

same or greater volume of cash memory and FSB (if any) with the same or greater fre-

quency as the processors installed in the server model that has a performance confirma-

tion www.spec.org.

C.6.1. Requirements to ACAS #1

1) ACAS #1 shall represent a hardware and software package consisting of two servers, each of which shall conform to the following set of requirements:

shall be built on the basis of processors with the 86-64 architecture;

shall be equipped with at least two processors (with 10 or more cores for each processor) with the total productivity of least 967 units as per the SPECint_rate_base2006 test;

shall be equipped with at least 32 GB RAM with a maximum operating frequency of 2550MHz and more, and expandable up to not less than 384GB without replacement of

the installed modules;

shall have at least 24 slots for RAM modules installation;

shall have at least 4 Gigabit Ethernet network interfaces (1000 Base-T);

shall have at least 2 expansion slots PCI-E 3.0, supporting installation of PCI Express adapters with external interfaces;

shall be equipped with a SAS RAID controller that does not occupy the PCI-E slots, which support the installation of PCI-E adapters with external interfaces and meets, as a

http://www.spec.org/http://www.spec.org/




minimum, the following set of requirements:

i. shall support, inter alia, the following RAID levels: 0, 1, 5, 6, 10;

ii. shall have at least 2 GB of cache memory;

iii. the controller’s cache memory shall be protected from power failures (in this case the cache content should be uploaded to the solid-state media);

shall be equipped with at least three 2.5” solid state (SSD) SAS drives with an unformat-ted capacity of not less than 400 GB each and producer-declared durability (TBW) of at

least two PB;

shall have at least 4 external USB ports, two of which should be located on the front side of the server, at least one USB port from the number located on the front side of the serv-

er shall conform to the USB 3.0 standard;

shall have at least one video port (DB-15);

shall have a dedicated service processor for monitoring and control with a possibility of remote server, power control, access to the server logs, remote access to server’s graph-

ical console;

shall have a dedicated network port for interaction with the service processor;

shall have a function (via Ethernet) of remote connection to the server through the service processor of virtual CD/DVD drives, USB and disk images;

shall have the function of remote interception of both textual and graphical console of the server: screen, keyboard and mouse, both at the stage of server load and operating system

functioning;

shall occupy not more than one mounting unit (1RU);

shall be equipped with a cable handler that enables the server to be removed from the mounting rack without disabling of the connected interface cables and power cables (val-

ue cannot be changed);

shall be supplied with backed-up fans and backed-up replaceable power supplies without interrupting the server operations;

the power supplies shall comply with the 80 PLUS Platinum standard and have a capacity of at least 750 W;

shall have a system of forecasting the server component failures of (processors, memory, hard drives, SSD drives, power supplies, fans);

2) ACAS #1 shall represent a central hub of the system.

3) ACAS #1 shall have a centralized system of monitoring the status of ACAS #1 and ACAS #2.

4) ACAS #1 shall process the call data (CDR) of the locally connected CA PBX in real-time and store it in the local database.

5) ACAS #1 shall rate the call data based on the uploaded scale of rates and save the rating re-sult in the local database.

6) ACAS #1 shall aggregate the call data collected by ACAS #1 kits in the local database.

7) ACAS #1 shall process and rate data on all calls of DTN subscribers.

C.6.2. Requirements to ACAS #2

1) ACAS #2 is a hardware and software package with the following characteristics:




is equipped with at least one x86-64 processors with at least four cores and the total productivity of least 154 units as per the SPECint_rate_base2006 test;

has the random access memory of least 4 GB, with the frequency of at least 2133 MHz;

has at least 2 slots for RAM installation;

has at least one solid state drive (SSD) with the storage capacity of at least 128 GB;

has at least one network interface Ethernet 1000 Base-T;

has at least four 3.x USB ports.

has an external power supply of at least 65W;

2) ACAS #2 shall autonomously perform the following functions in the case of a break in communication between ACAS #1 and ACAS #2:

automatic collection of call statistics;

storage of call statistics;

local call billing;

local call analytics;

3) ACAS #2 shall process the call data (CDR) of the locally connected RL PBX in real-time and store it in the local database.

4) ACAS #2 shall rate the call data based on the uploaded scale of rates and save the rating re-sult in the local database.

5) Upon request of ACAS #1, ACAS #2 shall send information on the rated calls in the local database.

6) ACAS #2 shall maintain local copies of call data before and after rating in the case of failure of communication with the ACAS #1 and automatically upload a local copy of the rated data

if connection is restored.

C.7. Requirements to Installations #1-4

C.7.1. Installation #1

1) The purpose of carrying out installation #1 is to extend functionality of the existing set of equipment of DTN kits (DESCRIPTION OF THE CURRENT INFRASTRUCTURE).

2) Installation #1 is performed at the respective Work site, as indicated in APPENDIX C DTN UPGRADE KITS

3) Installation #1 shall include:

PBX upgrade kit activation;

organization of interaction with the SBC;

installation of the SBC kit;

switching of the SBC kit;

connection of the SBC kit to the power source;

configuring of the SBC kit;

configuring a LAN site in order to ensure interoperability of the SBC with the operator;

configuring the information security system of the site in order to ensure interoperability of the SBC with the operator;

configuring the telephone system in order to ensure interoperability of the SBC with the operator;




configuring of the ACAS kit for receiving data of the local PBX.

4) During installation, the Supplier shall ensure:

continuous operation of all DTN PBX except for the PBX at the Work Site;

the time of the PBX subscribers’ service interruption at the Work Site should not exceed 10 minutes.

5) Based on the results of Installation #1, a package of Detailed Design Documentation #2 is agreed upon for DTN upgrade kits #2, #16, #24, #34, #36, #52, #54, #55, #61, #63, #66, #74,

#77, #78 and a package of Detailed Design Documentation #3 is prepared for DTN upgrade

kits #1, #3 -7, # 9-15, #17 -19, #21 -23, #25-32, #35, #37-#44, 42-51, #53, #56-58, #60, #62,

#64-#67, 65-68, 73-#70, #75-#86, 76-87, #89, #95.

6) After Installation #1 the Supplier runs Acceptance Testing for Installation #1 (E.2.2) with participation of the Consignee.


1) The purpose of carrying out installation #2 is to expand telephone sub-networks by adding new RL PBX.


3) Installation #2 shall include:

installation of the PBX upgrade kit, except for telephone sets;

switching the PBX upgrade kit, except for telephone sets;

marking of completed connections;

connection of the PBX upgrade kit to the power source, except for telephone sets;

installation of the PBX upgrade kit;

configuring of the PBX upgrade kit;

integration of the PBX upgrade kit into DTN;

organization of interfaces with the standby circuit at the inter-regional level;



switching of the SBS kit;





installation of the ACAS kit;

switching of the ACAS kit;

connection of the ACAS kit to the power source;


4) During installation, the Supplier shall ensure seamless operation of all PBX of the DTN ex-cept of the PBX at the work site.




5) Based on the results of Installation #2, a package of Detailed Design Documentation #1 is agreed upon including the results of Installation #3 of the respective DTN upgrade kit.

6) After Installation #2-3 the Supplier runs Acceptance Testing for Installation #2-3 (E.2.2) with participation of the Consignee.


1) The purpose of carrying out installation #3 is to expand telephone sub-networks by adding new LL media gateways.


3) Installation #3 should include:

receiving from the Consignee of a media gateway set #1 -6 and telecommunications cab-inet #2 at the respective Site of Delivery and their transportation to the respective Work

Site pursuant to APPENDIX C;

installation of an LL media gateway;

switching of an LL media gateway;

marking of completed connections;

connection of the LL media gateway to the power source;

configuring of the LL media gateway;

integration of the LL media gateway with the RL PBX.

4) During installation, the Supplier shall ensure seamless operation of the RL PBX.


1) The purpose of carrying out Installation #4 is to extend functionality of the existing set of equipment of DTN kits (see description at DESCRIPTION OF THE CURRENT INFRA-

STRUCTURE).


3) Installation #4 should include:

PBX upgrade kit activation;



switching of the SBC kit;

connection of the SBC kit to the power source;






4) During installation, the Supplier shall ensure:




continuous operation of all DTN PBX except for the PBX at the work site;

the time of the PBX subscribers’ service interruption at the work site should not exceed 10 minutes.

5) Based on the results of Installation #4, Detailed Design Documentation Package # 2 is agreed upon.

6) After Installation #4 the Supplier runs Acceptance Testing for Installation #4 (E.2.3) with participation of the Consignee.

C.8. Requirements to the Detailed Design Documentation

C.8.1. General requirements

1) The Supplier shall prepare Detailed Design Documentation #1-3 for DTN upgrade kit (APPENDIX D) and have it approved by the Client.

2) Detailed Design Documentation #1-3 shall be prepared in Russian.

3) Detailed Design Documentation #1-3 shall be prepared in accordance with the main provi-sions of GOST 34.

4) Detailed Design Documentation #1-3 shall be submitted to the Client on electronic media (CD/DVD) in an editable format.

C.8.2. Requirements to Detailed Design Documentation #1

1) Detailed Design Documentation #1 shall be prepared for DTN upgrade kits #5 -6, #9, #11, #17, #19, #40-41, #45, #47-48, #53, #57, #59 -60, #71, #75-76, #89, and #95 and contain de-

sign solutions for implementing PBX upgrade kits #5 -6, #9, #11, #17, #19, #40-41, #45,

#47-48, #53, #57, #59 -60, #71, #75-76, #89, #95, SBC #2, ACAS # 2 pursuant to APPEN-

DIX D. Detailed Design Documentation #1, as a minimum, shall include the following com-

ponents:

statement of technical working design;

explanatory note;

description of the hardware kit;

structural scheme of communications;

physical scheme of communications;

logical scheme of communications;

statement of equipment and materials;

administrator’s manual;

user manual.


2) Detailed Design Documentation #2 shall be prepared for DTN upgrade kits #2, #16, #24, #34, #36, #52, #54, #55, #61, #63, #66, #74, #77, #78, and #99 and contain design solutions

for implementing SBC #1-3 kit and ACAS #1-2 pursuant to APPENDIX D. Detailed Design

Documentation #2, as a minimum, shall include the following components:





general system description;


physical scheme of communications;

logical scheme of communications;



user manual.


3) Detailed Design Documentation #3 shall be prepared for DTN upgrade kits #1, #3-4, #7-8, #10, #12-15, #18, #21-23, #25-32, #35, #37-39, #42, #44, #46, #49-51, #56, #58, #62, #64-

65, #67-68, #70, #72-73, #82, #86-87, #92 and contain design solutions for implementing

ACAS #2 kit pursuant to APPENDIX D. Detailed Design Documentation #3, as a minimum,

shall include the following components:


general system description;




user manual.




D. TIME LINES AND SCOPE OF QUALITY ASSURANCE

1) The guarantee period is the time period during which the Supplier guarantees consistency of the equipment characteristics with its passport data (technical documentation), continu-

ous operation of the equipment, reliability of its operation, maintaining the required prop-

erties and suitability of the equipment for use;

2) For all supplied equipment the Supplier shall provide a guarantee, which will operate from the date of the equipment delivery to the Site of Delivery and for 60 months or more from

the date of signing the final Acceptance Certificate by the Client.

3) Regarding the scope of the quality assurance, the Supplier shall guarantee that it, at its own expense, without any reimbursement of costs from the Client or Payer, shall:

within not more than 45 (ten) working days, replace or repair the defective equipment if the failure was not caused by a violation of operating conditions of the equipment regu-

lated by its manufacturer. Upon failure of the supplied equipment or its components, the

Client (or contractor providing equipment maintenance) shall inform the Supplier in writ-

ing or by e-mail of such failure. The Supplier shall, within not more than 4 (four) work-

ing days, explore the situation and coordinate with the Client further joint actions to re-

place or repair the faulty equipment.

Fix within not more than 10 (ten) working days faults in the operation of the supplied equipment and the detailed design documentation during the warranty period for the ser-

vices related to commissioning and development (updating) the detailed design documen-

tation if they result from the Supplier’s mistakes made during the provision of services

under this document.




E. TESTING AND QUALITY ASSESSMENT

E.1. Quality control on delivery

E.1.1. Check on delivery

1) Acceptance of the delivered Goods shall be performed by the Consignee at the Place of De-livery.

2) During the Goods acceptance, the Consignee verifies the integrity of the reference tape and completeness according to the goods-related and/or delivery-related documents and the con-

trol sheet provided by the Supplier.

3) If during the Goods acceptance it was identified that the reference tape was broken and cer-tain Goods are missing as per the goods-related and/or delivery-related documents and the

control sheet provided by the Supplier, the Consignee shall present a reasoned refusal from

the Goods acceptance and establish a time period for the Supplier to remove the identified

defects.

4) The Supplier shall, not later than the scheduled date, at its own expense without additional charges to the Payer or Client, remove these defects. The deadline for the Supplier to remove

the identified defects is not included in the Goods acceptance period by the Consignee.

5) If the Consignee has no comments to the Goods acceptance, the Consignee shall within 3 (three) working days sign 4 (four) copies of goods-related (delivery-related) documents for

the Supplier:

1 (one) copy of goods-related (delivery-related) documents signed by the Consignee and Supplier shall be retained by the Supplier;

3 (three) copies of goods-related (delivery-related) documents signed by the Consignee and Supplier shall be handed over by the Consignee to the Supplier for submission to the

Buyer, 2 (two) of which the Supplier shall submit to the Buyer.

6) The completion date of the Goods delivery shall be the date of signing the goods-related (de-livery-related) documents by the Consignee.

7) Prior to signing the goods-related (delivery-related) documents by the Consignee, the Suppli-er assumes full liability for the Goods against all types of risk of loss or damage.

8) After the Consignee has signed the goods-related (delivery-related) documents, the Consign-ee assumes full liability for the Goods against all types of risk of loss or damage.

E.2. Acceptance testing

E.2.1. Preparing for testing

1) For Installations #1, #2-3, #4, the Supplier shall develop Acceptance Testing Program and Methods (Testing Program) and coordinate them with the Client prior to the acceptance test-

ing. The content of the Testing Program should be designed based on the requirements of the

existing standards GOST 34. 603-92.

2) For Installation #1, the Testing Program shall include, as a minimum:

verification of conformity of the supplied hardware and software to the technical re-




quirements using internal tests of hardware manufacturers;

verification of completeness and quality of the documentation supplied with the hardware and software;

verification of completeness and quality of the Detailed Design Documentation;

testing of the DTN upgrade kits for compliance with the functional requirements (Section B) and technical requirements (Section C) of these Technical Requirements;

testing of the SBC kits for compliance with the functional requirements (Section B) and technical requirements (Section C) of these Technical Requirements;

testing of the ACAS kits for compliance with the functional requirements (Section B) and technical requirements (Section C) of these Technical Requirements;

3) For Installation #2 and Installation #3 a joint Testing Program is drawn up, which shall in-clude, as a minimum:

verification of conformity of the supplied hardware and software to the technical re-quirements using internal tests of hardware manufacturers;


verification of completeness and quality of the Detailed Design Documentation;




4) For Installation #4, the Testing Program shall include, as a minimum:

verification of conformity of the supplied hardware and software to the contract require-ments using internal tests of hardware manufacturers;





E.2.2. Acceptance testing for Installations #1-3

1) The duration of acceptance testing should be no more than 3 (three) business days.

2) Acceptance testing for Installations #1-3 is carried out with participation of the Consignee and Supplier.

3) Acceptance testing for Installations #1-3 is carried out to assess compliance of the delivered DTN upgrade kits with the technical requirements and their readiness for continued opera-

tion.




4) Subject to the positive results of acceptance testing for Installations #1 -3, the Consignee and Supplier sign an acceptance testing report and approve a respective package of detailed de-

sign documentation.

5) If the results are negative, remarks in the Acceptance Testing Report are made and the timing of their elimination is agreed.

6) After the remarks have been eliminated the acceptance testing is carried out again pursuant to the procedure specified above.

E.2.3. Acceptance testing for Installation #4

1) The duration of acceptance testing should be no more than 3 (three) business days.

2) Acceptance testing for Installation #4 is carried out with participation of the Client and Sup-plier.

3) Acceptance testing for Installations #4 is carried out to assess compliance of the delivered DTN upgrade kits with the technical requirements and their readiness for continued opera-

tion.

4) Subject to the positive results of acceptance testing for Installation #4, the Client and Suppli-er sign an acceptance testing report and approve a respective package of detailed design doc-

umentation.

5) If the results are negative, remarks in the Acceptance Testing Report are made and the timing of their elimination is agreed.

6) After the remarks have been eliminated the acceptance testing is carried out again pursuant to the procedure specified above .

E.2.4. Consolidated Services Acceptance Certificate for Installations #1-4

7) По результатам подписания протоколов for Installations #1 -4, , the Client and Supplier sign within 5 business days a Consolidated Services Acceptance Certificate for Installations

#1-4.




F. IMPLEMENTATION PLAN

F.1. Implementation schedule

# Stage Tender doc-

umentation

section

Term/duration

of the stage

from the date

of the contract

Documents based on the

stage outcome

Ground

s for

penalty

1 Delivery C, APPEN-

DIX B Weeks 1 to 17

Delivery related docu-

ments yes

2 Installation C.7, E.2 Weeks 1 to

37

Acceptance testing re-

ports, packages of agreed and

approved detailed de-

sign documentation #1-3, Consolidated Installa-

tion Services Acceptance Certificate

yes

3 Acceptance testing E.2.2 Weeks 34 to 37 Acceptance testing report System commissioning

certificate yes

F.2. List of supplied goods

#

Name of the kit (the

structure of the respec-

tive kit is given in AP-

PENDIX D)

Technical re-

quirements (Sec-

tion of the Ten-

der Documenta-

tion)

Place of delivery Quantity

1 Upgrade Kit DTN #1

C Office of the FBS of Russia in the

Republic of Adygea 1

2 Upgrade kit DTN #2


Republic of Bashkortostan 1



Republic of Buryatia 1



Republic of Altai 1



Republic of Dagestan 1



Republic of Ingushetia 1



Kabardino-Balkar Republic 1



Republic of Kalmykia 1



Karachay-Cherkess Republic 1




#




PENDIX D)

Technical re-

quirements (Sec-

tion of the Ten-

der Documenta-

tion)




Republic of Karelia 1



Republic of Komi 1



Republic of Mari El 1



Republic of Mordovia 1



Republic of Sakha (Yakutia) 1



Republic of North Ossetia-Alania 1



Republic of Tatarstan 1



Republic of Tyva 1



Udmurt Republic 1



Republic of Khakassia 1



Chuvash Republic 1


C Office of the FBS of Russia in

Altai Krai 1



Krasnodar Krai 1



Krasnoyarsk Krai 1



Primorsky Krai 1



Stavropol Krai 1



Khabarovsk Krai and Jewish Au-

tonomous Oblast

1



Amur Oblast 1



Arkhangelsk Oblast and Nenets

Autonomous Okrug

1



Astrakhan Oblast 1



Belgorod Oblast 1



Bryansk Oblast 1



Volgograd Oblast 1



Vologda Oblast 1



Voronezh Oblast 1




#




PENDIX D)

Technical re-

quirements (Sec-

tion of the Ten-

der Documenta-

tion)


35