exocorriges.com · web viewtechnical requirements. supply and installation of at least 500...

National Hydromet Modernization Project-2Bidding Documents # NHMP2/A.1.aSection VI. Technical Requirements

Technical Requirements

Supply and Installation of at least 500 Teraflops supercomputer for the Main Computer Center of the RHM (including modernization of the engineering

infrastructure)

Moscow, 2015

2


Section VI. Technical Requirements (Including Implementation Schedule)

Table of Contents LIST OF DRAWINGS........................................................................................................5

LIST OF TABLES...............................................................................................................5

0. A. GENERAL.....................................................................................................................60.1. Customer..............................................................................................................................60.1.1. Managing Organization of the Project..............................................................................................60.1.2. Legal Purchaser................................................................................................................................60.1.3. Consignee.........................................................................................................................................60.2. Main Tasks of the RHM......................................................................................................60.3. Expected Results..................................................................................................................60.4. Terms and Abbreviations.....................................................................................................8

1. B. BUSINESS FUNCTIONS AND FUNCTIONAL REQUIREMENTS.......................151.1. Current Situation................................................................................................................151.2. Architecture of the Existing Information System..............................................................171.3. System Requirements........................................................................................................221.4. Project Sites.......................................................................................................................231.4.1. Categories of Requirements............................................................................................................24

2. C. TECHNICAL SPECIFICATIONS..............................................................................252.1. General Requirements.......................................................................................................252.1.1. Requirements for Goods and Services............................................................................................252.1.2. Language Support...........................................................................................................................252.1.3. Dates...............................................................................................................................................252.1.4. Power Consumption........................................................................................................................252.1.5. Operating Environment..................................................................................................................262.1.6. Certification Requirements.............................................................................................................262.1.7. Requirements for Physical Parameters of the Complex.................................................................272.1.8. Requirements for Security and Technical Compatibility...............................................................272.1.9. Methodic Support Requirements....................................................................................................282.2. Hardware of the Computer Complex and Other Equipment.............................................292.2.1. General Requirements....................................................................................................................292.2.2. Supercomputer #1...........................................................................................................................292.2.3. Supercomputer (R)..........................................................................................................................342.2.4. Data Management System..............................................................................................................352.2.5. Operational System Servers............................................................................................................382.2.6. The Monitoring and Control System Server...................................................................................402.2.7. Resource Access Control Server....................................................................................................402.2.8. Virtualization Platform...................................................................................................................412.2.9. Standard Server Configurations......................................................................................................412.3. Local-Area Network..........................................................................................................422.3.1. General Requirements....................................................................................................................422.3.2. LAN Architecture...........................................................................................................................432.3.3. General Requirements for Switches...............................................................................................442.3.4. Switch #1 – Core Level..................................................................................................................442.3.5. Switch #2 – Access Level...............................................................................................................452.3.6. Switch #3 – Access level................................................................................................................452.3.7. Information Security System..........................................................................................................45

3


2.3.8. LAN Control and Monitoring System............................................................................................482.3.9. LAN Security Policies Management System.................................................................................492.4. Software.............................................................................................................................492.4.1. General Requirements....................................................................................................................492.4.2. System Software Tools and System Control Tools of the Supercomputer....................................492.4.3. Set of Software Tools for Control of Backup Copying and Data Recovery..................................502.4.4. Set of Software Tools for Control of Hierarchic Data Storage......................................................502.4.5. SW of the Monitoring and Control System of the Computer Complex.........................................502.4.6. SW of the Batch Job Processing System........................................................................................512.4.7. Resource Access Control Software................................................................................................522.4.8. Application Development and Debug Tools..................................................................................522.4.9. Optimization and Development Software for Work Stations.........................................................532.4.10. Virtualization Platform Software....................................................................................................532.4.11. Software of Virtual Machines.........................................................................................................542.4.12. System of Infrastructure Services...................................................................................................552.4.13. Workstation Management System..................................................................................................582.5. Life-Support System..........................................................................................................602.5.1. Structured Cable System (SCS)......................................................................................................612.5.2. Uninterruptible Power Supply System...........................................................................................612.5.3. Conditioning and Ventilation System of Service Rooms (CVSSR)...............................................622.5.4. Automatic Gas Fire-Extinguishing System....................................................................................662.5.5. Automatic Fire Alarm System........................................................................................................682.6. Service Specifications........................................................................................................692.6.1. General Requirements....................................................................................................................692.6.2. Work Scope....................................................................................................................................702.6.3. Mounting and Installation...............................................................................................................712.6.4. Training...........................................................................................................................................722.6.5. Warranty Services...........................................................................................................................752.6.6. Technical Support...........................................................................................................................762.7. Documentation Requirements...........................................................................................772.8. Responsibilities of the Consignee......................................................................................78

3. D. TESTING AND QUALITY EVALUATION.............................................................793.1. Preliminary Evaluation of the Technical Solution of the Computer Complex..................793.1.1. General Requirements....................................................................................................................793.1.2. Evaluation of the Maximal Achieved Performance of the Supercomputer in the Linpack Test....803.1.3. Communications Network Testing.................................................................................................803.1.4. Total Performance Testing of the Computer System.....................................................................813.1.5. Total Performance Testing of the ODP Server...............................................................................813.1.6. Performance Testing of the File System.........................................................................................813.1.7. Performance Evaluation of the Supercomputer in Consignee’s Jobs.............................................813.2. Post-Qualification of the Proposed Technical Solution....................................................823.3. Preliminary Testing...........................................................................................................823.3.1. Testing Preparation.........................................................................................................................823.3.2. Testing............................................................................................................................................823.4. Operational Acceptance.....................................................................................................833.5. Acceptance Testing............................................................................................................843.5.1. Testing Preparation.........................................................................................................................843.5.2. Testing............................................................................................................................................84

4. Е. REQUIREMENTS FOR THE BID..............................................................................854.1. General Requirements.......................................................................................................854.2. Preliminary Contract Plan.................................................................................................85

5. F. FLOOR PLANS FOR LOCATION OF COMPUTER COMPLEXES.......................91

4


6. G. Equipment Location Tables.......................................................................................100

LIST OF DRAWINGS

Figure 1-1. Block diagram of computer complexes in the WMC in Moscow and in RSMC in Novosibirsk and Khabarovsk.........................................................................................................18Figure 5-1. Plan of Floor 2 with the rooms of the existing computer complex in the WMC in Moscow.........................................................................................................................................92Figure 5-2. Plan of Floor 4 with the rooms of the Computer Complex in the WMC in Moscow.93Figure 5-3. Floor plan with the rooms of engineering equipment of the Computer Complex in the WMC in Moscow..........................................................................................................................94Figure 5-4. Plan of the administrative and production floor in the WMC in Moscow.................95Figure 5-5. Floor plan with the rooms of the computer complex in the RSMC in Khabarovsk.. .96Figure 5-6. Equipment layout scheme in the rooms of the computer complex in the RSMC in Khabarovsk....................................................................................................................................97Figure 5-7. Floor plan with the rooms of the computer complex in the RSMC in Novosibirsk...98Figure 5-8. Equipment layout scheme in the rooms of the computer complex in the RSMC in Novosibirsk....................................................................................................................................99

LIST OF TABLES

Table 1-1. Information System Configuration..............................................................................19Table 1-2. List of Project Sites......................................................................................................23Table 4-1. Preliminary Contract Plan............................................................................................88Table 6-1. Equipment Location for the WMC in Moscow (the MCC of the RHM)...................101Table 6-2. Equipment Location for the RSMC in Novosibirsk...................................................128Table 6-3. Equipment Location for the RSMC in Khabarovsk...................................................129

5


0. A. GENERAL

0.1. Customer The Customer shall comprise three constituent legal entities who determine their relations

by agreements, departmental acts and any other documents as described below: the Legal Purchaser, the managing organization of the Project, and the Consignees of equipment.

0.1.1. Managing Organization of the ProjectThe managing organization of the project shall be the Federal Service for

Hydrometeorology and Environmental Monitoring (RHM) whose interests are rendered in these Technical Requirements that is the main superintendent of the budgetary funds and the Beneficiary of the NHMP-2.

0.1.2. Legal PurchaserThe Legal Purchaser (hereinafter, “Purchaser”) shall be the Foundation “Bureau of

Economic Analysis” (BEA).

0.1.3. ConsigneeThe Consignee shall be the RHM institutions appointed by the RHM order on the

acceptance procedures of Goods under the Contract on whose balance-sheets property acquired under the Project shall be registered after it is transferred from the RHM in the established order, as listed in paragraph 1.4.

0.2. Main Tasks of the RHMThe main objectives of the activities of the Federal Service for Hydrometeorology and

Environmental Monitoring are to ensure protection of vital interests of individuals, the society and the state against dangerous hydrometeorological events, climate change (hydrometeorological security) and to satisfy the needs of the population, government authorities and economic sectors for hydrometeorological information.

To achieve the above-mentioned objectives, the RHM shall ensure operation of hydrometeorological observation points, a collection and distribution system of primary hydrometeorological data, development and provision of information about actual and forecasted environmental conditions to government authorities, industries of the economy and the general public, including emergency information about dangerous weather events in the territory of the Russian Federation;

0.3. Expected ResultsThe purpose of the works is to build up computer capacities significantly for developing

scientific-methodical support of calculations and achieving spatial, time and quality characteristics of hydrometeorological products in line with advanced global achievements, and

6


for solving evaluation tasks of climate changes as established by the Strategy in Hydrometeorology and Related Areas.

The following activities are planned under this Bidding:Supply the Supercomputer with the performance of at least 1 PFlops to the Main Computer Center of the RHM, with related activities for modernization of the engineering infrastructure, required works for developing the scientific and mathematical capacities, and staff training; Replace computer clusters in Centers for Hydrometeorology and Environmental Monitoring in Novosibirsk and Khabarovsk that perform the functions of Regional Specialized Meteorological Centers of the WMO (FSBI “West-Siberian UGMS”, FSBI “Far-East UGMS”) to support operational task solving;Build a monitoring and diagnostic system of the technical condition of the supercomputer and computer clusters in Centers for Hydrometeorology and Environmental Monitoring in Novosibirsk and Khabarovsk;Organize remote access to the computer resources for RHM organizations, including the FSBI “GGO named after Voeikov”.

The procurement “Supply and installation of at least 500 Teraflops supercomputer for the Main Computer Center of the RHM (including modernization of the engineering infrastructure)” shall be implemented as part of the National Hydromet Modernization Project-2 and in accordance with the Procurement Plan set out at the address: http://www.beafnd.org/projects/detail.php?id=177

7

http://www.beafnd.org/projects/detail.php?id=177


0.4. Terms and Abbreviations

Term Explanation

AGFE Automatic Gas Fire Extinguishing

AFA Automatic Fire Alarm

Hardware partition

A component of a computer device that can operate as an independent system. A hardware partition can be managed by an image of an operating system different from the main part, and enables performance of all its functions, including a possibility of power turning on/off and restarting the system without affecting any other parts of the main system.

AWS Automated work station

ASC Authorized Service Center

Basic cloak rate Cloak rate of the electronic component operation without using any acceleration modes (e.g., TurboBurst for the processor)

Disk array A consolidated disk system under control of one or several controllers.

VM Virtual machine

WMO World Meteorological Organization

DCN Departmental communication network of the RHM

Supercomputer Set of computer nodes integrated for joint work by means of high-performance data transmission environment.

CC See “Computer Complex”

VC Videoconferencing

Computer Complex

Totality of hardware and software facilities designed for performing the functions of a modernized center and satisfying the technical requirements (specifications) of this assignment. It includes the Supercomputer, the Data Management System, the Monitoring and Control System, and the Local-Area Network to be supplied under this Bidding.

Computer node A multi-processor device with common sharable memory. All the processors of the computer node designed for computations are identical and have a direct access to all the physical memory of the node. One image of the operating system operates in the node.

GGO Main Geophysical Observatory

MDB Main distribution board

DS Directory Service

SSPTM Set of Spare Parts, Tools and Materials

8


Identity Identity of components: identical components shall have the same size, internal organization, operation rate, and the same part number of the Manufacturer

Information System (IS)

The Information System that is the subject of this Bidding shall include all the components offered for supply, and integration thereof.

UPS Uninterruptible power supply

IT Information technologies

Cluster, fault-tolerant cluster

Totality of identical servers grouped together for joint work by means of data transmission environment that acts as a single device for external users.

LAN Local-area network

CMR Computer machine room

WMC World Meteorological Center in Moscow (organizations performing processing of operational hydrometeorological information: the Hydrometeorological Center of Russia, the MCC of the RHM and the Main Air-Meteorological Center (Aviamettelecom)

FW Firewall

HDD Hard disk drive

RW Research work

R&D Research and development work

Common disk space

Nominal summarized volume of disk space before formatting and including into a RAID configuration

ODP Operational data processing

OS Operating system

BNSS Basic Network Service Subsystem

Peak performance Performance of the element calculated using its basic cloak rate

VP Virtualization Platform

SW Software

UCS Unified Communications Subsystem

Hardware-software complex

Totality of clusters, peripheral equipment, and software

Manufacturer Producing company of hardware and/or software facilities that fabricates and supports products as of the current date

Processor See “Processor core”

Processor core Central computer module of a computer node that is indivisible in terms of the operating system and subject to the condition that processor logical threading mechanisms (such as Hyper-threading, Simultaneous multithreading, etc.) are not used

SWT Software tools

9


EIR Electric Installation Regulations

RCC Regional Computer Center

RSMC Regional Specialized Meteorological Center

UEPSS See UPSS

UPSS Uninterruptible Power Supply System

GPSS Guarantied Power Supply System

SCS Structured Cable System

MCS Monitoring and Control System

Spam Undesirable / unauthorized electronic message dissemination

Data Management System, DMS

An independent component made of disk data storage systems, including archiving, backup copying, and hierarchic storage servers, as well as auxiliary service servers (e.g., input/output), if necessary, and software for data management and an interface with the Supercomputer.

Life-Support System

It includes the following systems: conditioning of service rooms, uninterruptible power supply, automatic gas fire extinguishing, and automatic fire alarm.

SCS Weak-Current Structured Cable System

CVSSR Conditioning and Ventilation System of Service Rooms

TSS Technical Support Service

DBMS Database Management System

WSMS Workstation Management System

Cloak rate See “Basic cloak rate”

Theoretical peak performance

See “Peak performance”

Node See “Computer node”

API Application Program Interface

BLAS Basic Linear Algebra Subprograms — set of main linear algebra functions

BLACS Basic Linear Algebra Communication Subprograms — set of main linear algebra communication functions

BMC Baseboard management controller

CPU Central Processor Unit (central processor / processor)

DHCP Dynamic Host Configuration Protocol

DNS Domain Name System

EUROBAT Association of European Automotive and Industrial Battery Manufacturers

Flops Floating-point operations per second

10


FC Fibre Channel — common name for a group of serial data transmission protocols used in data storage networks

GB Gigabyte (230 bytes)

GBph Gigabyte per hour

GBps Gigabyte per second

Gbit Gigabit (230 bits)

Gbps Gigabit per second

GFlops Gigaflop or 109 floating-point operations per second

HTML HyperText Markup Language

HTTP HyperText Transfer Protocol

IEEE Institute of Electrical and Electronics Engineers – an international organization issuing standards; also standards issued by it

Infiniband High-rate commuted serial bus used for both internal (intra-system) and intersystem connections. Infiniband uses a bidirectional serial bus. Basic rate: 2.5 Gbps in each of the directions; ports are used that are made of groups of 1x, 4x and 12x basic bidirectional buses (lanes). Modes: Single Data Rate (SDR) – work with the basic rate;Double Data Rate (DDR) – the bit rate is equal to the double basic rate;Quad Data Rate (QDR) – the bit rate is equal to the quadruple basic rate; Fourteen Data Rate (FDR) – basic rate of 1x bus 14.0625 Gbps.Enhanced Data Rate (EDR) – rate of 1x = 25.78125 Gbps; 4x = about 100 Gbps.

IPMI Intelligent platform management interface

iSCSI Small Computer System Interface over IP – protocol based on TCP/IP and is designed for establishing interaction and managing data storage systems, servers and clients

IRU Individual Rack Unit

KB Kilobyte (210 bytes)

Kbit Kilobit (210 bites)

LAN Local-Area Network

LDAP Lightweight Directory Access Protocol

LAPACK Linear Algebra Package

LINPACK Software package for analyzing and solving linear algebra equation systems and for solving tasks with own values. The package is used as a test package for evaluating performance of computer systems.

Linux Multi-user operating system Linux (SUSE Linux Enterprise Server x86_64)

LVM Logical Volume Manager

MACMAC address

Media Access Control – protocol for managing access to environmentPhysical address is a unique identifier of a device in TCP/IP networks

11


MB Megabyte (220 bytes)

MBps Megabyte per second

Mbit Megabit (220 bits)

Mbps Megabit per second

Mpps Megapackages per second

MFlops Megaflops or one million (106) floating-point (64 bits) operations per second

GFlops Gigaflops or one billion (109) floating-point (64 bits) operations per second

TFlops Teraflops or one trillion (1012) floating-point (64 bits) operations per second

PFlops Petaflops or (1015) floating-point (64 bits) operations per second

MPI Message Passing Interface — a standardized mechanism of the inter-node interface for executing parallelized software tools in a message exchange model.

NAS Network Attached Storage – network device for data storage

NTP Network Time Protocol – network protocol for synchronizing the internal clock

OpenMP Software interface (API) for programming computers with sharable memory (SMP/NUMA).

OSI Open System Interconnection – a standard interaction model of open systems

PE Programming Environment

PC Personal Computer

PB Petabyte

PDU Power Distribution Unit

QoS Quality of Service – quality and class of provided data transmission services

RAM Random-access memory

RAID Redundant Array of Independent Disks

SAN Storage Area Network

ScaLAPACK Scalable LAPACK – a parallel version of the mathematic library LAPACK

SAS Serial Attached SCSI

SCSI Small Computer Systems Interface – a standard for high-rate parallel interface

SLA Service Level Agreement

SNMP Simple Network Management Protocol included into the protocol stack TCP/IP

TCP Transmission Control Protocol – the main protocol in TCP/IP computer networks

TB Terabyte (240 bytes)

TFlops Teraflops or 1012 floating-point operations per second

Telnet Virtual terminal protocol included into the TCP/IP pack

U Unit — height unit of mounting cabinets equal to 44.45 mm

12


UPS Uninterruptible Power Supply

VLAN Virtual Local-Area Network

VPN Virtual Private Network

WAN World Area Network

WWW World Wide Web

13


1. B. BUSINESS FUNCTIONS AND FUNCTIONAL REQUIREMENTS

1.1. Current SituationThe FSBI “Russian Hydrometeorological Center”, the FSBI MCC and the FSBI

“Aviamettelecom” of the RHM ensure operation of the comprehensive technology of hydrometeorological information receipt, processing and distribution; and their technological integration supports the functions of the WMC of the World Meteorological Organization in Moscow. FSBI MCC supports the part of the common technology that is based on usage of high-performance computer complexes.

At the regional level, technologies requiring resources of high-performance computer complexes for regional tasks are operated in Novosibirsk and Khabarovsk.

Under Project-1, a computer complex was installed and is now operated in the FSBI “GGO named after A.I. Voeikov” for climate research purposes, with computer resources similar to the complexes in Novosibirsk and Khabarovsk RSMC.

The practical operation of high-performance computer complexes integrated into the information-telecommunication structure has confirmed that RHM organizations have sufficient experience in operating computer complexes of both vector and scalar types, and have acquired skills of remote operability monitoring and malfunction diagnostics of IT structures.

At present, the below technologies are operational in the WMC in Moscow:

Short-Term Forecast and Data Assimilation

For short-term forecasting (less than 3 days), forecasting technologies have been commissioned based on mesoscale models COSMO-RU with a pitch of 7 and 2.2 km, WRF with a pitch of 4 km, and an assimilation technology of meteorological observation data, including satellite data, of the 3D-VAR class. In accordance with RHM R&D plans, significant research and technological works are being performed to improve the mentioned and other models and technologies.

Global Mid-Term Forecast

The main global model is the semi-Lagrange PLAV model. At present, the operational version of the model has quite rough resolution of about 70 km at 28 vertical levels (grid size 400х251х28). Computation input is less than 8 processor-hours per one session. At present, the RHM carries out fine-tuning and designer’s testing of a new version of the PLAV model with the resolution of about 20 km in medium latitudes of the northern hemisphere, as part of its R&D efforts. The grid size is 1600х866х51; and it takes about 2000 processor-hours in at least 450 processors to calculate a 10-day forecast without violating the established schedule of forecasting product readiness.

The WMC in Moscow carries out operational activities with the Т169L31 global spectral model with the resolution of about 70 km. The model takes about 30 processor-hours in at least 32 processors to calculate a mid-term forecast.

The spectral model of the Russian Hydrometeorological Center is based on solving a standard system of hydrothermal dynamic equations for baroclinic atmosphere recorded in the sigma coordinate system, namely the following equations: movement, hydrostatic, continuity, heat inflow, moisture transfer, as well as diagnostic ratios (relations) for vertical components of

14


the wind velocity in p- and coordinate systems. The forecasting variables in the model are: temperature, velocity vortex and divergence, and surface air pressure.

The equation system is solved with the help of the spectral net-point method. In doing so, the main variables of the model are approximated in truncated convergent series based on orthogonal functions determined for the whole solution area. Effects of physical processes of the sub-grid scale are calculated in the grid environment. The model uses the so-called Gauss grid that is regular in the longitude and slightly irregular in the latitude. The semi-implicit scheme is used for time integrating.

Monthly and Seasonal Forecasts

For monthly forecasts, the WMC in Moscow still uses spectral model T40L15 that does not require too much computation effort; however, as part of its R&D activities the RHM works at applying a version of the global semi-Lagrange model PLAV with the resolution of 1.4х1.1 degrees and 28 levels on the vertical to calculate monthly forecasts. That version of the atmosphere model PLAV is used in operational activities for calculating ensemble seasonal forecasts. To calculate an ensemble, 160 processor-hours in 40 processors are required; it is done in pauses between operational sessions of short-term and mid-term weather forecasting. Any improvements in the seasonal forecasting model require re-calculation of a set of historic forecasts over 30 years, which takes as much as 4800 processor-hours for every starting date (at least once a month). At present, a seasonal weather forecast is being optimized with the help of a joint atmosphere and ocean model.

Chemical Weather Models

In 2008, the RHM of Russia started works on quantitative forecasting of the air quality level in cooperation with the Nizhny-Novgorod Institute of Applied Physics of the Russian Academy of Sciences. The works are oriented towards use of separate models of the atmosphere and the chemical-transport model.The atmosphere model WRF ARW was developed by the National Center for Atmosphere Research of the USA (NCAR) in cooperation with a number of other scientific organizations of the USA. It is based on elastic non-hydrostatic equations; with several parameter versions correlated with groups of small sub-grid processes. The used version is 3.1.1 distributed since August, 2009 in the site: http://www.wrf-model.org.

The chemical-transport model (XTM) CHIMERE was developed in the National Center of Scientific Research of France and is designed for recovery and forecasting of concentrations of chemical compounds and aerosols. Version V200709D is in use, developed in September, 2009, with 2 blocks of gas-phased reactions: MELCHIOR 1 (~80 substances, >300 reactions) and MELCHIOR 2 (44 substances, 116 reactions). Aerosols are divided into 8 grades by size. Site: http://www.lmd.polytechnique.fr/chimere.

In CHIMERE calculations, nested grids are used: an external grid with the resolution 1х1 and a nested one with the resolution 0.1 (latitude) х 0.2 (longitude). The boundary conditions in CHIMERE calculations are: calculated climate concentrations in the external area and calculation results in the external grid in the internal area.

It takes at present about 240 processor-hours to calculate chemical weather.

Initial data for global models are prepared with the help of the objective analysis unit that relies on the three-dimension analysis of variance on the basis of external fields of the first-order

15

http://www.wrf-model.org/


approximation. The existing version of the objective analysis consumes quite few resources: less than 10 processor-hours.

In 2009-2013, the computer capacities of the high-performance computer complexes supplied under Project-1 (SGI Altix 4700, SGI Altix ICE-8200, RSC “Tornado” and those implemented outside Project-1 (SGIICE-X and SGIUV – these clusters were used to deploy the operational meteorological support scheme of the Sochi Olympic Games in 2014) are fully exhausted. Operational tasks take quite a significant part of the computer resources of the complexes. This brings about serious limitations on use of the resources for research works related to development and testing of promising observation data assimilation models.

Experiments held by RHM specialists demonstrated that at present, tasks solved at the high-performance complexes are quite demanding to random access memory per processor core (3-4 GB per processor core). For this reason, use of accelerators (graphical accelerators NVIDIA, co-processors Intel Xeon Phi) is a problem.

As the experience of practical usage demonstrated in 2010-2014, the technologies that can be now developed by RHM institutions due to the results of Project-1, are rather demanding not just in terms of computation resources but also in relation to disk memory sizes. First of all, it is connected with a sharp increase (several-fold) in the output forecasting data volumes due to a higher detail level (3 km instead of 75 km) and periodicity. For analysis, generalized assessments and research works purposes, it is required to store the output data for a certain period of time (at least several months).

1.2. Architecture of the Existing Information SystemIn 2009, high-performance computer complexes were installed in the WMC in Moscow

and in RSMC in Novosibirsk and Khabarovsk; in 2011-2013, computer capacities of the complexes were built up.

The complex structure includes the following main components (Figure 1-1):

16


Figure 1-1. Standard block diagram of computer complexes in the WMC in Moscow and in RSMC in Novosibirsk and Khabarovsk

The Supercomputer performs the functions of operational and research computations and resource support of research efforts. Tasks are differentiated according to technological schemes of each of the centers where it is installed. The complete system set includes a system console of access organization to all the system nodes for engineering staff.

The Data Management System includes the following:Disk Data Storage System supporting data storage on magnetic hard disk drives and providing resources for the input/output subsystems of the Supercomputers, database servers and operational systems; Tape Data Storage System made of an automated tape library; Servers of the Data Management System including archiving, backup copying and hierarchic data storage servers.

Servers of the operational system and databases include computing servers, local servers for operational purposes, including servers for exchange of operational data, servers of RHM information systems, file servers supporting file and transaction data exchange for LAN clients.

17


General-purpose servers support operation of basic network services, such as DHCP, NTP, local DNS, and mail service.

User work stations for operational and research purposes include personal computers and visualization stations of operational and non-operational staff.

The local-area network integrates all the components of the information system. Communication with the existing LAN is by means of two Ethernet 10/100/1000 Base-T interfaces. To ensure smooth operation, monitoring and control of network equipment is implemented.

The Supercomputers perform the functions of operational and research computations and resource support of research efforts. Tasks are differentiated according to technological schemes of each of the centers where it is installed. The complete system set includes a system console of access organization to all the system nodes for engineering staff.

Table 1-1 presents the main characteristics of the installed Computer Complexes.

Table 1-1. Information System Configuration

RHM Center

Pick Performanc

e TFlops (1012)

Supercomputer Type

Quantity of CPU/

CPU in a Node

RAM TB(1012) / GB

per core

Manufacturer

(Company / Country)

Disk Subsystem TB(1012)

WMC

Moscow

11SGI

Altix 47001664 / 128

6.6/4SGI (USA)

180TB=60TBSGI IS4000+120TB SGI IS10000

16SGI Altix

ICE82001408/8 2.8/2 SGI (USA)

35RSC

”Tornado”1152/12 4.608/4

RSC

(Russia)300TBIBM Storwize V7000, IBM System Storage UDS3700

14 SGI ICE-X 720/20 2.304/3.2 SGI (USA)

2SGI

UV 200096/96 1.024/10.6 SGI (USA)

RSMC

Novosibirsk0.7

G-Scale

S4700104 / 104 0.2 Kraftway

(Russia)12.3TB SGI IS4000

RSMC

Khabarovsk0.7

G-Scale

S4700104 / 104 0.2 Kraftway

(Russia)12.3TB SGI IS4000

Cluster (Supercomputer #C1) SGI Altix 4700 with the peak performance 11 TFlops is built on 832 dual-core processors Intel Itanium 9140М with the random-access memory 6.6 TB (1664 processor cores, 4 GB per core). The Supercomputer is a system with shared memory,

18


scalable to 1024 cores in the frameworks of the single operating system image. The architecture SGI NUMAflex ensures the best values (in performed tests) of the bandwidth and latency. The interaction bus SGI NUMALink ensures high-rate interaction between system processors. As of today, the Supercomputer is logically divided into partitions/nodes (13 nodes): 1 partition = 1 computer rack. In each partition, there are 32 virtual computer nods: 4 cores + 16 GB random-access memory. Two virtual nodes are reserved for system processes (8 cores + 32 GB memory). Each hardware partition has system hard disks SAS with useful size 300 GB with mirroring and high-rate access to the Disk Storage System via parallel file system SGI CXFS. The cluster is operated by the operating system SLES 11SP1 (ia64).

Cluster (Supercomputer #C2) SGI Altix ICE8200 with the peak performance 16 TFlops is built on 352 four-core processors Intel Quad Core Xeon e5440 with the random-access memory 2.8TB (1408 processor cores, 2 GB per core). The Supercomputer is a widely-spread type of blade systems, with 64-bit architecture EM64T/AMD64. The Supercomputer consists of 3 computer racks, each: 4 IRU (Individual Rack Unit — blade chassis), 15 computer blades, 8 cores and 16 GB random-access memory in each blade. The Infiniband DDR technology is used as the interaction bus. The cluster uses the diskless operation principle: an image of the operating system is rolled out in the random-access memory. The common file system is built on the basis of the NFS over Infiniband technology. The cluster is operated by the operating system SLES 10SP2 (x86_64).

Cluster (Supercomputer #C3) RSC “Tornado” with the peak performance 35 TFlops is built on 192 eight-core processors Intel E5-2690 with the random-access memory 6.1 TB (1536 processor cores, 4 GB per core). The Supercomputer has 64-bit architecture EM64T/AMD64. The Infiniband QDR technology is used as the interaction bus. The common file system is built on the basis of the NFS technology for connections to the file system of SGI clusters and parallel file system GPFS for direct connection of cluster nodes to disk arrays. The cluster is operated by the operating system SLES 11SP2 (x86_64).

Cluster (Supercomputer #C4) SGI ICE-X with the peak performance 14 TFlops is built on 72 ten-core processors Intel E5-2670v2 with the random-access memory 2.3 TB (720 processor cores, 3.2 GB per core). The Supercomputer has 64-bit architecture EM64T/AMD64. The Infiniband FDR technology is used as the interaction bus, with Enhanced Hypercube IB Interconnect Topology. The common file system is built on the basis of the NFS technology for connections to the file system of SGI clusters and parallel file system GPFS for direct connection of cluster nodes to disk arrays. The cluster is operated by the operating system SLES 11SP3 (x86_64).

Supercomputer #C5 SGI UV2000 with the peak performance 2 TFlops is a system with global common random-access memory built on 16 six-core processors Intel E5-4617 with the random-access memory 1 TB (96 processor core, 10 GB per core). The Supercomputer has 64-bit architecture EM64T/AMD64. The common file system is built on the basis of the NFS technology for connections to the file system of SGI clusters and parallel file system GPFS for direct connection of the Supercomputer to disk arrays. The Supercomputer is operated by the operating system SLES 11SP3 (x86_64).

The disk subsystem with the total size 180 TB has a hierarchic structure: 60TB SGI InfiniteStorage 4000 system (Disk Data Storage System #C1) and 120TB SGI InfiniteStorage 10000 (Disk Data Storage System #C2). The storage-area network (SAN) solution is based on two switches Brocade SilkWorm® 48000 (48K) and file system SGI CXFS, that is a parallel file system to direct the data flow via the SAN. CXFS ensures connection of all the technological servers and nodes of Supercomputer #C1 with the Disk Data Storage System #C1. The file system works together with SGI DMF (hierarchic storage management system SGI Hierarchical Storage Management) that ensures data migration between disk subsystems.

19


Supercomputer #C2 is connected to the parallel file system by means of direct fault-tolerant connection to metadata servers (SGI Altix 450).

Disk Data Storage System #C3 is built on the basis of disk arrays 14 TB IBM Storwize V7000, 300 TB IBM System Storage UDS3700. The Data Storage Network solution is implemented on the basis of two installed FC switches Express IBM System Storage SAN24B-4 with a connection to switches SW 48K and to file system GPFS that is a parallel file system. GPFS ensures connection of all the required technological servers and nodes of Supercomputer #C3 with Disk Data Storage System #C3. Data migration between the disk subsystems is also performed by GPFS tools.

To ensure operation and management of components of the computer infrastructure, the Microsoft Windows Directory Service and associated general system services, such as: infrastructure of the common directory on the basis of Microsoft Active Directory, basic network services DHCP, DNS, and NTP. Microsoft Exchange is used as a mail server service; and Microsoft Lync is used as unified communications.

The LAN is built on the following basis:Core level: switches Cisco 6509;Distribution level: switches Cisco 4948 with connection to the core level switches at the rate of 10 Gbps via a fiberoptic communication channel; Backup level of the server factory: switches Cisco 4948 with connection to the core level switches at the rate of 1 Gbps via a fiberoptic communication channel or UTP connection;Access level: switches Cisco 2960 and Cisco 3650 with connection to the core level and/or distribution level switches at the rate of 1 Gbps via a fiberoptic communication channel or UTP connection.

The security system of the network architecture is based on firewalls Cisco ASA of series 5500 and access servers Cisco ACS.

The LAN control system is implemented using Cisco LMS integrated solution (element manager of active equipment) and HP OpenView NNMi (enterprise manager of equipment). Analysis of network traffic is carried out using Adventnet NetFlow Analyzer Professional. Monitoring of crucial vulnerabilities of information-network resources is supported by scanner PositiveTechnologies XSpider Professional Edition.

The Microsoft System Center is used for control purposes of workstations based on operating systems Windows Server and SLES.

To organize count, the Altair PBS Pro centralized system for batch processing of jobs is used in the computer complexes.

Operational and research count processes are performed in the above-mentioned computer systems.

In specialized regional centers in Novosibirsk and Khabarovsk, the pick performance of the Supercomputer G-Scale S4700 manufactured by ZAO “Kraftway Corporation PLC” on the basis of 52 Intel Itanium 9140 processors is 0.7 TFlops. The capacity of the disk storage for the centers in Novosibirsk and Khabarovsk is 12.3 TB on the basis of SGI InfiniteStorage 4000 equipment.

At present, the resources of the complexes are fully exhausted. Operational tasks take quite a significant share of the computer resources of the complexes; it brings about serious limitations in research works for developing and testing promising models and observation data assimilation systems.

20


1.3. System RequirementsIt is required to make up and supply information systems for the WMC in Moscow, and

RSMC in Novosibirsk and Khabarovsk, with the main task of the systems to enhance the quality of output forecasting products.

The information computer system to be supplied under the Contract shall have the following parameters:Performance sufficient for basic operational calculations within periods determined by technological reasons;Reserve of computer capacities for performing research and development tasks in accordance with the Strategy in Hydrometeorology and Related Areas;Data storage resources ensuring accumulation of results with the aim of supporting operational activities, supporting research works and quality control procedures of forecast calculations; Network infrastructure integrating individual technological elements of the computer facility, with a channel (throughput) capacity that is in balance with the Supercomputer performance; Set of technological servers supporting monitoring, management, security, workload distribution and other service functions; Network infrastructure supporting local and remote access to information resources of the complex and access to corporate and global networks;Set of system software and general and specialized libraries sufficient for implementing technological tasks;Engineering systems to ensure operability and security of technological equipment.

The set of operational technologies of digital analysis and forecast of meteorological fields that is currently in operation includes the following elements:

Subsystems for receipt, operational monitoring, primary processing of observation data and of products of foreign meteorological centers;Subsystems for quality control of observation data and objective analysis of meteorological fields;Regional finite-difference atmosphere model;Global spectral atmosphere model;Technologies for maintaining operational databases, the quality control system, graphic product presentation and remote access of users to information and computation resources of the WMC in Moscow via the Internet.

In order to minimize operating expenses and secure investments make in the already built computer infrastructure (including that during Project-1), modernization of high-performance computer complexes for the WMC in Moscow and the RSMC in Novosibirsk and Khabarovsk shall be on the basis of scalar computer complexes of unified architecture in the unified Linux environment.

Modernization of the high-performance complexes for the RSMC in Novosibirsk and Khabarovsk will be implemented by means of replacing the existing clusters, but preserving the engineering infrastructure..

1.4. Project SitesTable 1-2 presents addresses of Project Sites.

Table 1-2. List of Project Sites

21


№ Project Site Address1 FSBI “MCC of the RHM” Building 1, house 11, Bolshoy Predtechensky

Side-Street, Moscow, 1232422 FSBI “West-Siberian UGMS” 30, Sovetskaya st., Novosibirsk, 630099

3 FSBI “Far-East UGMS” 18, Lenina st., Khabarovsk, 680673

The Computer Complex in the WMC in Moscow will be located in the building of the MCC.

The building was erected in 1964 using the technology of load-bearing framework for industrial purposes. The interaxal distance between columns is 6x6 meters. The maximal permissible area for equipment location (full area of the 1st floor) is 645 m2. Floors between storeys: concrete slabs, with the load-bearing capacity not more than 600 kg/m2. The ceiling height between floors is 4.8 m. Window size 3x3, looking to the South-East. There is a cargo elevator in the building, with the capacity 4 t; cabin size: 3х2.8х2.5 m. There are the main and emergency entrances/exits in the building, central heating, cold and hot running water, and centralized ventilation.

Figure 5-2 presents a floor plan with the location of the existing computer complex. Room #5 is designated to locate the main computer equipment (Figure 5-3).

The computer complex of the RSMC in Novosibirsk (FSBI “West-Siberian UGMS”) is located in the building of the Computer Department. It was erected in 1964. It is a 2-floor rectangular building, 48×24 m, without a basement. The height of the 1st floor is 4.2 and 5.4m, the height of the 2nd floor is 5.0m. The total area of the building is 2304 m2 (1st and 2nd floors).

The construction solution of the Computer Department building includes load-bearing external walls, an internal ferroconcrete frame and beam ferroconcrete ceilings. The column grid is 6x6 m, series ИИ-60, 61, 62, 63 edition 1 and series ИИ-64 edition 1, 2 of the Catalogue of the Novosibirsk Economic Council, 1961.

The external walls are made of ceramic bricks (640 mm thick) with an external series of horizontal belts of single lime-and-sand bricks. The foundations of the columns are ferroconcrete monolith piles; the foundations of the walls are continuous, made of concrete blocks of precast ferroconcrete slabs. Ceilings: ribbed slabs of two types: 1190×350×5660 mm and 490×350×5660 mm, with designed useful load up to 8kPa. Covering: ribbed slabs on precast ferroconcrete lean-to beams, series ПК-01-115. Windows: double-glass (single casement), with wooden casing, frames and sashes. The foundations are based on dusty sand, with middle density, low humidity, and estimated resistance of 0.2MP.

The computer complex is located in Room # 222 (45) (Figure 5-8, Figure 5-9) of the regional computer center. The room is in the 2nd floor. The operator service is located in Room #46. The external wall of the building is not a façade.

The computer complex of the RSMC in Khabarovsk (FSBI “Far-East UGMS”) is located in the block of Computer Department. The block was erected in 1965. It is a rectangular building, 48×24m, with a basement. The height of the basement, the 1st and 2nd floors is 3.6, 4.0 and 5.5 m, respectively. The total area of the building is 3409.4 m2 (basement, floors 1 and 2).

The construction solution of the Computer Department building includes load-bearing external brick walls and an internal ferroconcrete frame. Column grid: 4×6m. Foundations: monolith ferroconcrete piers under columns; concrete blocks under external and internal walls (series ИИ-03). Walls: full ceramic bricks and concrete blocks. Precast monolith ferroconcrete floors and covering (series ИИ-64, issue 1, 2) are designed for a normative useful load of 4kPa

22


and 8kPa (in computer rooms). Windows: dual pane windows with single casing and wooden casings, sashes and frames; glass sandwiches on the 2nd storey. Rolled-strip, combined, ventilated roof, with external unarranged water run-off. Floors: linoleum, ceramic and PVC tiles.

The computer complex is located in Room 220 (45) (Figure 5-6, Figure 5-7) of the regional computer center. The room is in the second floor. The external wall of the building is a façade wall.

1.4.1. Categories of RequirementsCertain requirements established for supercomputer complexes in the WMC in Moscow

and in the RSMC in Novosibirsk and Khabarovsk, differ: 1. (M) – for the WMC in Moscow;2. (R) – for the regional centers.

23


2. C. TECHNICAL SPECIFICATIONSAll the requirements set out in this section shall be mandatory, unless explicitly stated

otherwise.

2.1. General Requirements

2.1.1. Requirements for Goods and Services1. All functions described here in Section C “Technical Specifications” shall be implemented.

The term “option” used in the Technical Requirements shall mean availability of a function, but not a possibility of implementing it.

2. Any equipment and software pieces required to implement the functions as set out in Section C “Technical Requirements” shall be provided for (including those not explicitly stated in the “Technical Requirements”).

3. All the equipment and its components, as well as materials used shall be new and have a Manufacturer’s trademark on the package.

4. All the software shall be stable working latest English versions. Versions with Russian localization shall be supplied (if available).

5. Equipment and software shall have been tested in the Manufacturer’s factories.6. According to the Contract, all the offered models shall have been in the market for at least 3

months by the Bid submission date.

2.1.2. Language SupportAll the supplied hardware and software (if applicable) shall support Cyrillic operations in

data input – output, processing and transmission at the application level.

2.1.3. DatesAll the supplied software (if applicable) shall present, compute and transmit dates,

including dates of the 18th – 22nd centuries.

2.1.4. Power ConsumptionAll the equipment supplied shall satisfy the following power supply characteristics

(unless specific requirements are set forth): Voltage: one-phase 220 V or three-phase 380 V with permissible variations from -15% to

+10%; Frequency 50 Hz +/- 1 Hz; All the active equipment shall have cables and accessories to be connected to electric

sockets 220 V under the CEE 7 Standard (GOST R 51322.1-99 or IEC 60884-1-94) with grounding (connection of active equipment directly to 220 V or 380 V distribution boards is allowed);

The total consumed capacity of the Computer Complex and the Life-Support System shall not exceed:

24


1200 kVAThe Bidder shall include information about power consumption of the offered equipment

pieces of the Computer Complex and the Life-Support System into its Bid;If the real power consumption (to be measured during tests as per paragraphs 3.1.2, 3.3.2,

3.5.2) exceeds the power consumption value declared in the Bid, the Supplier shall be liable to make monthly payments of the interest on the expense amount of the electric power consumed by the complex during the period of Warranty #1, based on the tariffs effective as of the payment date according to the following formula:

(Ca – Cd)/Cd * tariff as of the payment date, where:Cd – consumption declared in the Bid;Ca – Actual consumption in tests.

Cases of equipment parts, installation cabinets and racks on which the equipment is to be mounted shall have radial connections to contacts of the protective grounding network;

The Bidder shall submit documentary confirmation of the battery design life to be equal to 10 years according to the EUROBAT classification, from the Manufacturer of the Uninterruptible Power Supply #1. The warranty obligations related to the mentioned batteries shall be as per paragraph 2.6.5 Warranty #3.

2.1.5. Operating EnvironmentOperating conditions and maintenance types and periods of technical facilities of the

complex shall be ensured to meet the requirements for their operation, maintenance, repairs and storage as per the Manufacturer’s documents.

Unless any specific requirements are set forth, all the equipment pieces shall operate at least under the following conditions of the environment in rooms where the equipment of this Bidding is to be located:1. Temperature: from +10 ºC to +40 ºC;2. Relative humidity: from 20 % to 80 %, without condensation;3. The electric field level inside service rooms with IT equipment and machine rooms of the

Computer Complex shall not exceed the values mentioned in GOST 16325-88;4. The allowed vibration level in service rooms and in computer machine rooms shall not

exceed the amplitude of 0.1 mm and the frequency of 25 Hz; 5. The dust content of the air of service rooms and computer machine rooms shall not exceed:

up to 0.75 mg/m3.

2.1.6. Certification Requirements1. The Supplier shall submit copies of conformity certificates or conformity declarations of

the Customs Union for all the offered equipment at the delivery stage to confirm compliance of the offered equipment with technical regulations of the Customs Union or Unified Requirements of the Customs Union.

2. The Bidder shall submit documentary evidence that it has quality certificates ISO 9001 or similar ones.

3. The Bidder shall submit documentary evidence that the Manufacturer of the offered hardware has quality certificates ISO 9001 or similar ones.

4. All the electric equipment shall be certified in accordance with the requirements of GOST R 50839-95 or an equivalent standard.

25


5. The type of gas fire extinguishing substance of the AGFES shall be certified for use in the territory of the Russian Federation.

6. The Bidder or its subcontractor shall have all the required licenses for works related to preparation of the computer complex premises and installation of the Life-Support System (including construction works).

7. By the delivery date, the Supplier shall have submitted a full set of permitting documents for import into the Russian Federation (if import is necessary) and for further operation of the offered equipment. The set of documents shall be presented to the Purchaser before equipment supply from abroad.

8. The Bidder shall submit a documentary confirmation of the possibility of installation of the supplied equipment in the premises without any need to make changes to the load-bearing structures of the building, from an authorized organization. The documents shall be submitted before equipment dispatch.

2.1.7. Requirements for Physical Parameters of the Complex1. The equipment of the Computer Complex shall be located in mounting cabinets (19 or 24

inches, not more than 1700 mm deep).2. The design of mounting cabinets shall enable access to the equipment from the front and

from the rear. 3. IT equipment pieces shall be in cases enabling mounting into standard mounting cabinets and

having standard fixing elements for mounting into such cabinets.4. IF the applied technical solution implies use of any equipment not designed for installation

into standard 19”cabinets, such equipment shall be monoblocks in tower cases with a built-in ventilation and temperature control system.

5. The height of the mounting cabinets shall not exceed 42 U and 2.5 meters;6. The total room space required for locating the equipment shall not exceed:

(М) – 150 m2;Additional room space shall be allocated for the UPSS, as mentioned herein.

7. The load on the floor plates shall not exceed:(М) – 600 kg/m2;

2.1.8. Requirements for Security and Technical Compatibility1. All the hardware-software tools of the Computer Complex shall comply with at least the

following normative documents (among other things): GOST R MEC 60950-2002 in part of compliance of hardware-software tools of the Computer Complex with the security requirements;GOST R 51318.22-99, GOST R 51317.6.3-99 in part of electromagnetic compatibility of the hardware-software tools; GOST 26329-84 in part of permissible noise levels of the hardware-software tools. 2. The Bidder shall submit documentary evidence of compatibility of all the structural

components of the Computer Complex (hardware pieces and software) in the form of public compatibility lists or a letter of guaranty from the Manufacturer of the offered hardware or software tools.

3. The Bidder shall submit a written recommendation of joint use of computer nodes, the Data Management System, and the basic software of the Computer Complex (including the Operating System, the parallel file system, the Batch Job Processing System and compilers,

26


Application Development and Debug Tools, and the Monitoring and Control System) from the Manufacturer of the Supercomputer.

4. The Bidder shall submit legally valid letters of authorization from the Manufacturers for information technologies (except for technologies produced by the Bidder), all the active (requiring power supply) equipment and software.

2.1.9. Methodic Support RequirementsThe methodic support of the modernization process shall be determined by the following

set of standards and guidance documents describing the process of information system building:GOST 34.602-89 “Information technology. Set of standards for automated systems. Terms of reference for building an automated system”; GOST 34.601-90 “Information technology. Set of standards for automated systems. Automated systems. Building stages”;

When performing premises preparation works for locating the equipment of the Computer Complex, the following documents shall be observed: GOST R 12.2.142-99 “Cooling systems with cooling capacity over 3.0 kW. Safety requirements”; GOST 12.1.012-2004 “System of standards for labor safety. Vibration safety. General requirements”;Fire Safety Rules 01-03, SNiP 41-01, SNiP 21-01, Fire Safety Norms 88-01, SNiP 31-03 Set of Rules 5.13130.2009 approved and brought into effect by Order of the Emergency Ministry of Russia.

27


2.2. Hardware of the Computer Complex and Other Equipment

2.2.1. General RequirementsAll the hardware pieces supplied under this Bidding shall meet at least the following

requirements:1. All functions described in paragraph 2.2 shall be implemented;2. To implement the functions mentioned in paragraph 2.2, all the required hardware and

software pieces (including those not explicitly mentioned in the Technical Requirements) shall be provided for,

3. All the hardware pieces of the Computer Complex shall have built-in remote control hardware features enabling configuration, halt, start and/or re-start of the system or its individual elements by means of a secure interface from the monitoring and control network. The monitoring and control network shall be supplied and installed together with the rest of the equipment of the Computer Complex;

4. All the CVSSR and UPSS hardware pieces shall have built-in remote control hardware features enabling configuration and monitoring of the system or its individual elements by means of an interface from the monitoring and control network. All the CVSSR and UPSS hardware pieces shall include all the required equipment and infrastructure to be integrated into the monitoring and control network;

5. The Computer Complex shall meet the requirement of maximal readiness. The “maximal readiness” is understood herein in the following meaning: in case of a failure of any of the system nodes or components (hard- and software) the system shall automatically detect the failure and take measures for self-recovery and re-configuration. User processes interrupted by such a node failure need not be recovered automatically. No loss of data integrity of the parallel file system is allowed;

6. In case of a failure of any node/nodes of the Supercomputer or any part of the communication network MPI or any part of the disk sub-system, the remaining nodes of the Supercomputer shall automatically retain access to all the data stored in the Disk Data Storage Systems;

7. Maintenance engineers carrying out diagnostic or repair works in any of the sub-systems shall have a possibility of performing their work without interrupting the main operational functions and causing performance decrease of the Supercomputer by more than 25%.

2.2.2. Supercomputer #1The Supercomputer is a set of computer nodes integrated with the help of a high-

performance interaction mechanism (network for MPI communications/interconnections).

The Supercomputer shall meet at least the following requirements:The total peak performance achieved in the Linpack test of the Supercomputer shall be not less than the following value under the methodology used to measure the parameter in TOP500.org (Rpeak value):1.2 PFlops;The maximal performance achieved in the Linpack test of the Supercomputer shall be not less than the following value under the methodology used to measure the parameter in TOP500.org (Rmax value):

28


0.9 PFlops;The Supercomputer shall support execution of applications written with the use of MPI libraries version 3.0;All the computer nodes shall be identical;The computer nodes shall have the form factor of blade servers and shall be installed into a common chassis. Not more than 4 computer nodes may be installed into one blade; not more than 12 computer nodes may be installed into one chassis; The Supercomputer shall have a liquid cooling system to meet the following requirements:

Cooling with inflammable and chemically active substances is not allowed; No direct contact is allowed of the cooling liquid with electronic components of the computer nodes; Efficient cooling (without using chillers) shall be used while the environment air temperature remains below28oC; components of computer nodes shall operate without any performance decrease; Protection against unintended leakage of the liquid shall be designed in case of stopping or disconnecting elements of the Computer Complex. Blade servers shall be connected and disconnected without stopping any other blade server;The theoretical peak performance of a computer node shall not be less than:

1 TFlops;Each node shall include random access memory with support of sharpness control algorithms and single-bit mistake correction with the following characteristics:

Cloak rate at least 2400 MHz and the sizeat least 4 GB per processor;Memory modules shall be installed so that to use all the accessible channels evenly for maximal performance; All the memory modules in a computer node shall be identical;

Each node shall have hard system solid-state disk drives SSD with the size 200 GB.Diskless configuration is allowed; if so, all the required equipment shall be provided for in order to support work in the fault-tolerant mode for organizing OS loading to computer nodes;For computer nodes, execution of the following operations initiated from any control node of the system shall be implemented:

Set of operations compatible with the IPMI protocol, version 2.0 or a later one;Selective hardware reset of any node or group of nodes;Selective power supply connection/disconnection of any node or group of nodes (power

cycle); Reading of the node status testing result code (Power-On Self Test, POST); Update of the BIOS code in one and all nodes of the Supercomputer simultaneously; Reading of the value of the instant power consumption of the node, processor chips; Setup of limitations of the node power consumption: after setup of the maximal limit, the

node shall decrease its power consumption level down to the established limit; Reading of the temperature or thermal reserve value for each processor chip;

Supercomputer nodes shall have a catastrophe-prevention function: the node shall disconnect itself fully independently when the temperature value gets outside the established operating temperature range as established by the Manufacturer for such nodes;Each processor of the computer node shall be an original 64-bit scalar processor. All the processors in the node shall be identical;

29


The architecture of the command set of the processor shall be compatible with x86-64 with vector extensions;The cache memory size of each processor chip shall be at least 25 MB;The theoretical peak performance of one processor shall be at least 35 GFlops;Each node shall have access to Disk Data Storage System #2 via the parallel file system. The performance of Disk Storage System #2 (in test as per paragraph 3.1.5) shall be at least as set out in the test accompanying documents; Each node shall have a MPI interface; and the Supercomputer shall have an MPI communication network with characteristics not less than in the test accompanying documents and measured in tests as per paragraph 3.1.3;The MPI communication network shall support integration of at least all computer nodes into a single high-performance network. The network topology shall ensure full utilization of the bandwidth from all connected computer nodes, i.e. each element (e.g. switch) in the topology shall have the same or better performance as to the network, than the sum of performance values of connected nodes. The topology shall be the same for the whole Supercomputer; The transportation network shall support integration of all the computer nodes for access to Disk Storage Systems;Simultaneous work of the communication network and transportation network shall be supported via separate interfaces. The topologies of the communication and transportation networks shall be identical;The high-performance communications and transportation networks shall support channel capacity of each link at the level at least 80 Gbps; The quantity of root switches in each of the high-performance networks (if any in the topology) shall be at least 2; Communications between nodes (power supply, interconnections, LAN) in a chassis shall be implemented without cables. When using central root interconnect switch directors, it is allowed to use direct cable connections;The communications network shall be built on a scheme without a single point of failure to ensure integration of channel capacities of interfaces or, in case of failure, an automatic switching mechanism between interfaces of computer nodes;The dedicated monitoring and control network of the Supercomputer shall be implemented on a scheme without a single point of failure with a rate at least 1Gbps;The duration of the Supercomputer switch from the working mode to the power-off status shall not exceed 15 minutes. The duration of the Supercomputer switch from the power-off status to the working mode shall not exceed 20 minutes;A single failure of a power supply unit and/or an active cooling component shall cause no node failure;The cooling system of Supercomputer nodes shall ensure reliability and accessibility:Computer nodes shall not include any elements with mechanic parts moving in the process of operation, such as hard disks, fans, etc.;Any single failure of a cooling element shall not cause failure of any node of a group of blade servers;Any regular maintenance works of elements of the Supercomputer cooling system shall be without stopping the computer nodes;The performance time of the test to be provided by the Consignee on the basis of the global spectral model (paragraph 3.1.7.1) for the minimal configuration required for testing (paragraph 3.1.1) shall not exceed the values stated in the test accompanying documents;

30


The performance time of the tests to be provided by the Consignee on the basis of the finite-difference model SLM (paragraph 3.1.7.2) for the minimal configuration required for testing (paragraph 3.1.1), shall not exceed the values stated in the test accompanying documents;The performance time of the tests on the COSMO model (paragraph 3.1.7.3) for the minimal configuration required for testing (paragraph 3.1.1), shall not exceed the values stated in the test accompanying documents.

2.2.2.1. System Console #1 of the SupercomputerThe Supercomputer shall be supplied together with one System Console #1 (cluster) that

shall meet at least the following requirements:1. The System Console #1 of the Supercomputer shall support performance of console

functions for the Supercomputer and all the server equipment of the Computer Complex and include all the equipment pieces required to do it;

2. The equipment control functions before the operation system boot shall be supported (including work with BIOS, power-off status, OS crash);

3. It shall be designed for rack mounting;4. It shall have a pre-installed OS of the Supercomputer with a distribution optical disk;5. DVD disk drive;6. Connection to the LAN to organize remote access;7. TFT monitor, active matrix, diagonal screen size at least17" designed for 1U.

2.2.2.2. System Console #2System Console #2 shall duplicate the functions of System Console #1 of the

Supercomputer, be located outside the Computer Complex premises, and include System Unit #1 and Monitor #1.

System Unit #1 shall meet at least the following requirements:1. 1 (one) 64-bit processor chip;2. Peak performance of each processor chip shall be 30 GFlops;3. Random-access memory 8 GB;4. 1(one) hard disk drive SAS 10k, size 600 GB or 2(two) hard disk drives SATA, size 1 TB

each, with mirroring;5. 1 combined CD/DVD drive;6. 1 network adapter – integrated RJ-45, Ethernet 10/100/1000 Base-Т;7. 2 free USB 2.0 ports;8. 1 serial port;9. Standard keyboard 101 key Rus/ Lat10. Optical mouse with a scroll-wheel and a mouse pad;11. Pre-installed OS shall be the OS of the Supercomputer with an installation disk.

Monitor#1 shall meet at least the following requirements:1. Type: color, active matrix TFT;2. Diagonal screen size 20";3. Pixel size not more than 0.26 mm;

31


4. Contrast 700:1;5. Brightness 300 cd/m2;6. Resolution 1600x1200, 60 Hz;7. Maximal permissible quantity of bad pixels – as per class II in the ISO 13406-2 standard;8. Built-in power supply;9. Emission and ecological security standard TCO-03;10. Monitor #1 shall be compatible with System Unit #1;11. Monitor #1 shall be supplied with interface cables.

2.2.2.3. FRONT-END System of the SupercomputerThe System shall meet at least the following requirements:

The System is organized to ensure a single point of entry for users, to organize broadcasting environment, etc. 1. The System shall be organized in the following way:

(M) – as a cluster without a single point of failure to be based on the configuration of Server #1 (paragraph 2.2.9.1)

(R) – on the basis of the configuration of Server #1 (paragraph 2.2.9.1);2. The Operating System shall be the OS of the Supercomputer;3. Job start in the Supercomputer shall be organized via the Batch Job Processing System;4. It is not allowed to implement other services and systems in the hardware platform of this

system.

2.2.2.4. Batch Job Processing SystemThe System shall meet at least the following requirements:

1. The System shall be organized to support controlled job start in Computer Complex resources;

2. The System shall be organized as a cluster without a single point of failure to be based on the configuration of Server #2 (paragraph 2.2.9.2);

3. The service of the batch job processing system shall also be backed up;4. It is not allowed to implement other services and systems in the hardware platform of this

system.

2.2.2.5. License Management SystemThe License Management System shall meet at least the following requirements:

1. The System shall be organized to support centralized license management of the software installed in Computer Complex resources;

2. The System shall be organized as a cluster without a single point of failure to be based on the configuration of Server #2 (paragraph 2.2.9.2);

3. The pre-installed operating system shall be identical to the OS of the Supercomputer.

2.2.3. Supercomputer (R)The Supercomputer is a set of computer nodes integrated with the help of a high-

performance interaction mechanism (network for MPI communications/interconnections).

The Supercomputer shall meet at least the following requirements:

32


1. The total peak performance of the Supercomputer in the Linpack test shall be not less than the following value under the methodology used to measure the parameter in TOP500.org (Rpeak value):

75 TFlops;2. The maximal performance achieved in the Linpack test of the Supercomputer shall be formed

under the methodology used to measure the parameter in TOP500.org (Rmax value)55 TFlops.

The Supercomputer shall support execution of applications written using MPI libraries of the version 3.0;

3. All the computer nodes shall be identical;4. The computer nodes shall have the form factor of blade servers and shall be installed in

groups into a common chassis. Communications (interconnections, LAN) inside the chassis shall be implemented without cables. Not more than 2 computer nodes may be installed into one blade.

5. The computer nodes shall be outfitted with air cooling elements only. It is allowed to offer nodes with liquid cooling (similar to those in paragraph 2.2.2) – if so, it is required to preserve all engineering infrastructure, including the cooling and power supply systems for operability support in the fault-tolerant version;

6. The theoretical peak performance of one computer node shall be at least:1 TFlops;

7. Each node shall include random access memory with support of sharpness control algorithms and single-bit mistake correction, with at least the following characteristics:

Frequency at least 2400 MHz;Size at least4 GB per processor;Memory nodes shall be installed so that to use evenly all the available channels

for maximal performance;All memory modules in a computer node shall be identical;

8. Each node shall have hard system solid-state disk drives SSD with payload volume 200 GB.Diskless configuration is allowed; if so, all the required equipment shall be provided for to support work in the fault-tolerant mode for organizing OS loading;9. For computer nodes, execution of the following operations initiated from any control node of

the system shall be implemented:Set of operations compatible with the IPMI protocol, version 2.0 or a later one;Selective hardware reset of any node or group of nodes;Selective power supply connection/disconnection of any node or group of nodes (power

cycle);Reading of the value of the instant power consumption of the node, processor chips;Setup of limitations of the node power consumption: after setup of the maximal limit, the node shall decrease its power consumption level down to the established limit;Reading of the temperature or thermal reserve value for each processor chip;10. Each processor of the computer node shall be an original 64-bit scalar processor. All the

processors in the node shall be identical;11. The architecture of the command set of the processor shall be compatible with x86-64, with

vector extensions;12. The cache memory size of each processor chip shall be at least 25 MB;13. The theoretical peak performance of one processor shall be at least 35 GFlops;

33


14. Each node shall have access to Disk Storage System #1 via the parallel file system;15. Each node shall include a MPI interface; and the Supercomputer shall have an MPI

communication network;16. The MPI communication network shall support integration of at least all computer nodes into

a single high-performance network. The network topology shall ensure full utilization of the bandwidth from all connected computer nodes, i.e. each element (e.g. switch) in the topology shall have the same or better performance as to the network, than the sum of performance values of connected nodes. The topology shall be the same for the whole Supercomputer;

17. The communication networks shall support channel capacity of each link at the level at least 50 Gbps;

18. The quantity of root switches in the communication network (if available in the topology) shall be at least 2;

19. Communications between nodes (power supply, interconnections, LAN) in a chassis shall be implemented without cables. When using central root interconnect switch directors, it is allowed to use direct cable connections;

20. The communication network shall be implemented without a single point of failure;21. The monitoring and control network of the Supercomputer shall be implemented on a scheme

without a single point of failure with the rate at least 1 Gbps;22. The duration of the Supercomputer switch from the working mode to the power-off status

shall not exceed 15 minutes. The duration of the Supercomputer switch from the power-off status to the working mode shall not exceed 20 minutes;

23. A single failure of a power supply unit and/or a cooling component shall cause no node failure;

24. The Supercomputer (R) and Supercomputer #1 shall be of the same model series; 25. The performance time of the tests to be provided by the Consignee on the basis of the finite-

difference model SLM (paragraph 3.1.7.2) for the minimal configuration required for testing (paragraph 3.1.1), shall not exceed the values stated in the test accompanying documents;

26. The performance time of the tests on the COSMO model (paragraph 3.1.7.3) for the minimal configuration required for testing (paragraph 3.1.1), shall not exceed the values stated in the test accompanying documents.

2.2.4. Data Management SystemThe Data Management System shall include the Disk Data Storage System (paragraph

2.2.4.1), Disk Data Storage System #2 (paragraph 2.2.4.2), servers of the Data Management System (paragraph 2.2.4.3), including the Server for Data Access from LAN.

The equipment of the Data Management System shall meet at least the following requirements:1. All the nodes of the Supercomputer, the FRONT-END system of the Supercomputer, the Job

Batch Processing System, servers of the Data Management System, servers of the Operating System shall have access to data located in the Disk Data Storage System and shall have fault-tolerant access to Disk Data Storage System #2 via the parallel file system;

2. Servers and workstations within the LAN shall have network access to the data of the parallel file system;

3. Only the client part (parts) of the parallel file system shall be installed in the Supercomputer;4. Access management to data via the parallel file system shall be with the help of additional (in

relation to the Supercomputer) equipment, with a fault-tolerant file system organized;

34


5. The Data Management System shall support automatic file migration between storage levels, including data of the parallel file system;

6. A centralized backup copying system shall be implemented to support backup copying of system disks of all servers of the Computer Complex, part or all servers of the Information System to the Disk Data Storage System;

7. All the components of the Data Management System shall be controlled from a remote console located within the LAN.

2.2.4.1. Disk Data Storage System #1Disk Data Storage System #1 shall meet at least the following requirements:

1. The total disk space without reserve disks shall be:(M) – 320 TB;(R) – 200 TB;

2. The data shall be protected using the distribution technology of check sums between all disks used for metadata storage;

3. Single failures of system hardware components shall not cause any system stop and interruption of access to the data;

4. The Disk Data Storage System shall have external interfaces: SAS, FC 8 Gbps or Infiniband FDR;

5. The channel capacity of the disk array of the Disk Data Storage System shall be at least: (M) – 6 GBps;(R) – 2 GBps;

Disk arrays for the WMC and RSMC shall be of the same model series;6. The Disk Data Storage System shall be built on SAS or NL-SAS disks;7. One chassis of the disk array shall comprise at least 60 disks;8. All the disks designed for data storage shall be identical and have the same model number,

size and rotation rate; 9. The Disk Data Storage System shall support parallel access to data from the Supercomputer,

the servers of the Data Management System, servers of the Operating System and network access of clients located within the LAN;

10. The architecture of the Disk Data Storage System and the disk arrays shall have no single point of failure, support replacement of equipment pieces and maintenance without stopping the data access service;

11. As its parts, the Disk Data Storage System shall include reserve disks operated in the hot-swap mode, with the total size at least 10% of the total disk size. The disks shall not be included in any active disk group (e.g. in RAID configurations), but shall be automatically connected to active disk groups in case of failure of a group disk;

12. The Disk Data Storage System shall support hardware data protection against media failures;13. The Virtualization Platform shall have direct access to the Disk Data Storage System; 14. The Disk Data Storage System shall support access from the side of servers and workstations

operated by the Windows or Linux operating system via the LAN using the NFS, CIFS and FTP protocols;

15. Authorization shall be designed using the LDAP protocol in access to data located in the Disk Data Storage System;

16. The Disk Data Storage System may be configured as one of the levels of the Hierarchic Data Storage System.

35


2.2.4.2. Disk Data Storage System #2The Disk Data Storage System #2 shall meet at least the following requirements:

1. Formatted disk space without reserve disks shall be at least: 2.5 PB;

2. The data shall be protected using the distribution technology of check sums between all disks used for metadata storage;

3. Single failures of system hardware components shall not cause any system stop and interruption of access to the data;

4. Disk Data Storage System #2 shall support external interfaces Infiniband FDR;5. The channel capacity of Disk Data Storage System #2 shall be at least:

55 GBps;6. Disk Data Storage System #2 shall be built on disks of the SAS family;7. All the disks designed for data storage shall be identical and have the same model number,

size and rotation rate;8. Disk Data Storage System #2 shall support parallel access to data from the Supercomputer,

servers of the Data Management System, servers of the Operating System and network access of clients located within the LAN;

9. Disk Data Storage System #2 shall support performance of the file system as required for the Supercomputer in paragraph 2.2.2, to be confirmed in tests;

10. The architecture of Disk Data Storage System #2 and the disk arrays shall have no single point of failure, support replacement of equipment pieces and maintenance without stopping the data access service;

11. The Disk Data Storage System shall have a possibility of creating, extending, changing parameters of and deleting logical volumes in the operating mode;

12. The Disk Data Storage System shall include reserve disk capacity operated in the hot-swap mode, with the total size at least 10% of the total disk size. The capacity shall not be used for data storage, but shall be automatically used to recover fault-tolerance of the array in case of failure of a disk;

13. Disk Data Storage System #2 shall support data protection against simultaneous loss of at least two media pieces in a group;

14. Disk Data Storage System # 2 shall provide an access possibility to data for the Supercomputer;

15. Disk Data Storage System #2 shall support access from the side of servers and workstations operated by the Windows or Linux OS via the LAN using the NFS, CIFS and FTP protocols;

16. Authorization shall be designed using the LDAP protocol in access to the data located in the Disk Data Storage System.

2.2.4.3. Servers of the Data Management System

2.2.4.3.1. Archiving and Backup Copying Server

The Server shall meet at least the following requirements:1. The functionality of the Archiving and Backup Copying Server shall support backup data

copying /recovery from dedicated servers of the Information System to the Disk Data Storage System;

2. The Server shall be implemented as a cluster without a single point of failure based on the configuration of Server #1 (paragraph 2.2.9.1);

36


3. The requirements for software tools for data copying/recovery are set out in paragraph 2.4.3;4. The Server shall have access to the parallel file system without using the LAN.

2.2.4.3.2. Hierarchic Data Storage Server

The Server shall meet at least the following requirements:1. The functionality of the Hierarchic Data Storage Server shall support operation of the parallel

file system and data migration between Disk Data Storage Systems in accordance with the prescribed policy;

2. The Server shall be implemented as a cluster without a single point of failure, based on the configuration of Server #1 (paragraph 2.2.9.1);

3. The requirements for software tools are set out in paragraph 2.4.43;4. The Server shall have access to the parallel file system without using the LAN.

2.2.4.3.3. Server for Data Access from LAN

The Server shall meet at least the following requirements:1. The functionality of the Server shall support the functions set out in paragraph 2.2.4.1;2. The Server shall be implemented as a cluster without a single point of failure to be based on

the configuration of Server #1 (paragraph 2.2.9.1); 3. The Server shall have access to the parallel file system without using the LAN;4. Control shall be designed from System Console #1 (paragraph 2.2.2.1);5. It shall have fault-tolerant connection to the LAN with a rate at least 10 Gbps;6. It is not allowed to implement any other services or systems in the hardware platform of the

mentioned system.

2.2.5. Operational System ServersThe functionality of the Servers of the Operational System shall support management of

meteorological databases, data pre-processing and post-processing, management of operational tasks and exchange tasks of operational data.

2.2.5.1. Operational Product Generating ServerThe Server shall meet at least the following requirements:

1. The Server shall be implemented as a cluster without a single point of failure to be based on the configuration of Server #3 (paragraph 2.2.9.3);

2. The Server shall have access to Disk Storage Systems, including access to the parallel file system without using the LAN;

3. The operating system shall be that of the Supercomputer;4. It is not allowed to implement any other services or systems in the hardware platform of the

mentioned system.

2.2.5.2. Operational Data Processing ServerThe Server shall meet at least the following requirements:

1. The Server shall be a computer system with global common random-access memory; 2. The total peak performance of the Server in the Linpack test shall be calculated in the

method used to measure the value in the TOP500.org (Rpeak value):9 TFlops;

37


3. Each processor shall be an original 64-bit scalar processor;4. The architecture of the command set shall be compatible with x86-64, with vector

extensions;5. The size of the cache memory of each processor chip shall be at least 15 MB;6. The random access memory shall be 4 TB, with the automated error correction technology

ECC (random-access memory cards shall be at least 16 GB each);7. 4 (four) hard disk drives SSD, each at least 160 GB, with hardware mirroring;8. 2 (two) adapters Gigabit Ethernet;9. 4 graphic adapters with the memory size at least 2 GB GDDR5, with two DVI interfaces;10. Connection to Disk Data Storage System #2 shall be without using the LAN, including

connection to parallel file systems;11. The Server shall be connected to the System Console;12. Direct connection of 2 work stations shall be designed (at a distance up to 30 m). Each

work station shall be outfitted with a monitor 30”, a keyboard, and a mouse; 13. The operating system (the single image of the operating system) shall be as the OS of the

Supercomputer;14. Chassis to locate components in the blade form factor;15. The chassis shall be located in the server rack;16. It is not allowed to implement any other services or systems in the hardware platform of

the mentioned system;17. The results of total performance tests (paragraph 3.1.5) for full configuration of the server

shall not be worse than the values stated in the documents accompanying testing.

2.2.5.3. Work Group Server # 1The Server shall meet at least the following requirements:

1. The Server shall be implemented as a cluster without a single point of failure to be based on the configuration of Server #1 (paragraph 2.2.9.1);

2. The cluster shall be connected to System Console #1 (paragraph 2.2.2.1);3. The cluster shall have an independent data storage system built on disks SAS 10k, with a size

at least 10 TB, with hardware RAID5 and a 10% set of reserve disks operated in the hot-swap replacement mode;

4. The Server shall have access to the parallel file system without using the LAN;5. Application Development and Debug Tools (paragraph 2.4.88) shall be proposed for the

mentioned cluster;6. The operating system shall be the OS of the Supercomputer;7. It is not allowed to implement any other services or systems in the hardware platform of the

mentioned system.

2.2.5.4. Work Group Server #2The Server shall meet at least the following requirements.

The main components of the server platform shall meet at least the following minimal requirements:1. The Server shall be implemented on the basis of the configuration of Server #1 (paragraph

2.2.9.1);2. Operating System:

38


Windows Server x64 Edition, with a license for 250 users;3. The Server shall have access to the parallel file system without using the LAN. It is allowed

to replace the mentioned functionality with a data storage system built on disks SAS 10k, with a size at least 10 TB, with hardware RAID5 and a 10% set of reserve disks operated in the hot-swap replacement mode;

4. It is not allowed to implement any other services or systems in the hardware platform of the mentioned system.

2.2.5.5. Technological Segment Server The Server shall meet at least the following requirements:

1. The Server shall be implemented on the basis of the configuration of Server #1 (п.2.2.9.1);2. The Server shall have access to the parallel file system without using the LAN. It is allowed

to replace the mentioned functionality with a data storage system built on disks SAS 10k, with a size at least 10 TB, with hardware RAID5 and a 10% set of reserve disks operated in the hot-swap replacement mode;

3. The operating system shall be Linux;4. It is not allowed to implement any other services or systems in the hardware platform of the

mentioned system.

2.2.6. The Monitoring and Control System ServerThe Server shall meet at least the following requirements:

1. The functionality of the Server shall support control and monitoring of the Computer Complex and the Life-Support System;

5. The Server shall be implemented as a cluster without a single point of failure to be based on the configuration of Server #1 (п.2.2.9.1);

6. The software requirements are set out in paragraph 2.4.5.

2.2.7. Resource Access Control ServerThe Server shall meet at least the following requirements:

1. The functionality of the Server shall support centralized assigning, distribution and execution control of general access rules to computer and information resources of the system;

2. The hardware implementation shall be based on the configuration of Server #1 (paragraph 2.2.9.1), with fault-tolerant backup organized;

3. The software requirements are set out in paragraph 2.4.7; 4. It is not allowed to implement any other services or systems in the hardware platform of the

mentioned system.

2.2.8. Virtualization PlatformThe Virtualization Platform (VP) is a set of server nodes, DSS and communication

facilities designed to build a unified fault-tolerant cluster for starting virtual servers.

The VP shall meet at least the following requirements:1. The server part of the VP shall be implemented in hardware facilities with characteristics

identical to the server facilities of Supercomputer #1 (paragraph 2.2.2);

39


2. After all the workload as provided for by these Terms of Reference is placed in the VP, at least 50% of the hardware resources (processors, memory) shall remain vacant for the purpose of extended use of the Consignee’s VP;

3. The VP shall remain fully operable if up to 50% of its hardware resources (servers) become inoperable in full;

4. The total number of server nodes shall be at least 36 (thirty six);5. The hardware of the VP shall be managed Supercomputer by means of the Monitoring and

Control System of the Supercomputer;6. The communication and transport networks of the VP and Supercomputer #1 shall be

separated physically;7. The transport network of server nodes of the VP shall be used for access to Disk Data

Storage System #1 to support non-stop migration function between VP nodes for interserver interaction in the VP and for internet traffic exchange of virtual machines with the Consignee’s LAN;

8. An interface shall be designed between the communication and transport nets of the VP and the Consignee’s LAN at the level L2 of the OSI model by means of at least two connections at a rate at least 10 Gbps each.1.

2.2.9. Standard Server Configurations

2.2.9.1. Server #1The Server shall meet at least the following requirements:

1. 2 (two) processor chips; 2. Each processor shall be an original 64-bit processor identical to the processor of the

Supercomputer;3. Random-access memory 256 GB, with a rate at least 2400 MHz, with the error correction

technology ECC;4. 2 (two) HDD SAS 10k, each 600 GB, with hardware mirroring;5. 2 (two) adapters Ethernet 10/100/1000 Base-T;6. No requirements are set out for the cooling system type;7. Redundant fans, hot-swappable;8. Redundant power supply units, hot-swappable;9. The Server shall be connected to System Console #1 (paragraph 2.2.2.1);10. The operating system shall be as the Supercomputer OS;11. For locating in a mounting cabinet.


1 2 (two) processor chips;2 Each processor shall be an original 64-bit processor identical to the processor of the

Supercomputer;3 Random-access memory 128 GB, with a rate at least 2400 MHz, with the error correction

technology ECC;4 2 (two) HDD SAS 10k, each 600 GB, with hardware mirroring;

40


5 2 (two) adapters Ethernet 10/100/1000 Base-T;6 No requirements are set out for the cooling system type;7 Redundant fans, hot-swappable;8 Redundant power supply units, hot-swappable;9 The Server shall be connected to System Console #1 (paragraph 2.2.2.1);10 The operating system shall be as the Supercomputer OS;11 For locating in a mounting cabinet.


1 2 (two) processor chips;2 Each processor shall be an original 64-bit processor identical to the processor of the

Supercomputer;3 Random-access memory 512 GB, with a rate at least 2400 MHz, with the error correction

technology ECC;4 2 (two) HDD SAS 10k, each 600 GB, with hardware mirroring;5 2 (two) adapters Ethernet 10/100/1000 Base-T;6 Redundant fans, hot-swappable;7 Redundant power supply units, hot-swappable;8 It shall be connected to the Disk Data Storage System without using the LAN, including

connection to the parallel/shared file system;9 The Server shall be connected to System Console #1 (paragraph 2.2.2.1);10 The operating system shall be as the Supercomputer OS;11 For locating in a mounting cabinet.

2.3. Local-Area Network

2.3.1. General Requirements1. It is required to build a Local-Area Network, including a Structured Cable System in rooms

where the Computer Complex will be located. 2. It is required to ensure connection to the existing Consignee’s LAN via four channels with

the channel capacity 10 Gbps.3. Active LAN equipment shall be fully compatible with the Cisco Systems equipment

underlying the existing Consignee’s corporate network. A related compatibility confirmation shall be issued by Cisco Systems.

4. It is required to ensure all-round interaction with network protocols and technologies of the existing LAN.

5. It is required to use new technological principles (models) for building network infrastructures:

Use distributed integration of physical channels into one logical channel;Ensure a virtualization possibility (dividing a physical switch into virtual routers with independent switching/routing tables, etc.);Ensure a possibility of using virtual external boards (extenders).6. It is required to ensure integration with the RHM DCN via existing communication channels.

41


7. It is required to install standby power supply units and redundant ventilator modules into the existing switches of the Consignee’s core.

8. It is required to install additional firewall and security modules into the existing switches of the Consignee’s core.

9. It is required to install up-to-date IOS versions into the existing switches of the Consignee’s core.

10. Build a unified technological infrastructure of distributed software-hardware facilities of the System of Infrastructure Services and ensure complete network connectivity of the three automation Sites in accordance with paragraph 1.4.

11. Structure the LAN by subsystem/level of data transmission – LAN traffic, information security, and network environment management and control.

12. Crossing equipment of the cable system and LAN active equipment shall be located in mounting cabinets. After the SCS is located in the mounting cabinets, free space shall be available (at least 30%).

13. After all the connections are organized in switches, free ports and transceivers shall be available (at least 30%) of each connection type/rate.

14. A detailed description of required active network pieces is set out below.15. The Bid shall include all the equipment and materials required for installing the mentioned

LAN. 16. The Bidder shall develop a detailed scheme of the proposed LAN infrastructure depicting all

the required connections and include it into its Bid.17. All the functions described in paragraph 2.3 shall be implemented.18. All the equipment and software (including pieces not explicitly mentioned in the Technical

Requirements) required to implement the functions as per paragraph 2.3 shall be provided for.

2.3.2. LAN Architecture The following LAN architecture shall be designed, with regard to all the building

principles, design, protocols and technologies of the existing network infrastructure:The levels of the core, distribution, access and server farm may be combined in a single device;The core level shall be fully backed up;Core switches shall be located in different floors of the building;

The LAN topology shall include the following levels: Core/distribution level – 2 central modular L3 switches; The core level shall be connected to the existing LAN with four trunk multimode lines at

a rate at least 10 Gbps. To organize communication lines, it is required to design appropriate transceivers in the existing equipment;

The access level shall have a required quantity of access switches connected to the LAN core with 2 trunk connections at a rate at least 10 Gbps. Such switches shall be cards of core switches.

It is required to ensure connection of DMS servers, operating system servers, the server of the monitoring and control system directly to core switches via external cards at the rates 1Gbps and 10Gbps.

42


2.3.3. General Requirements for Switches1. The IP protocol shall be supported at all the levels of the local-area network, as well as the

following protocols:Remote access, control and monitoring protocols: Telnet, SSH, HTTP, HTTPS, SNMP (Simple Network Management Protocol), RMON (Remote Monitoring), ICMP (Internet Control Message Protocol);Technological protocols: DNS, NTP, DHCP (Dynamic Host Configuration Protocol);Authentication protocols: TACACS+ (Terminal Access Controller Access Control System), RADIUS (Remote Authentication in Dial-In User Service), 802.1x.2. It is required to ensure standby power supply units in each data transmission component of

the LAN.3. It is required to ensure compatibility with the control and management systems operated by

the Consignee. A compatibility confirmation shall be issued by the Manufacturer of the equipment.

2.3.4. Switch #1 – Core LevelSwitches #1 (LAN core level) shall meet at least the following requirements:

1. Support required throughput capacity of the channels to the access level at least 10 Gbps;2. Ensure channel backup to connect the access level;3. Ensure a required quantity of the SFP+ transceivers to connect the access level, connect to

the existing data transmission network and to organize inter-switch interaction;4. Meet the following scalability requirements: at least 2 (two) available free slots to increase

the number of connections of access/extension level switches to the existing network;5. Have modular architecture, not more than 2U high;6. Have an unblocked switching matrix at a rate at least 1920 Gbps;7. Have a traffic switching and routing functions at a rate at least 160 Gbps;8. Support routing protocols: OSPF, RIP, IS-IS, BGPv4, EIGRP;9. Support the FCoE technology and enable installation of Fiber Channel adapters in any port of

the switch;10. Have at least 8 SFP+ transceivers 8Gbps Fiber Channel;11. Have a function of establishing a distributed aggregated channel between switches;12. Have a function of utilizing individual physical devices as additional switching cards.

2.3.5. Switch #2 – Access LevelSwitch #2 (access level) shall meet at least the following requirements:

1. Have at least 48 ports 1 Gbps for connecting server equipment;2. Have at least 4 (four) SFP+ slots in each access switch;3. Have at least 2 transceivers 10 Gbps;4. Support integration with the core switch as a virtual module;5. Height not more than 1U;6. Support air blow-out to the hot zone.

2.3.6. Switch #3 – Access levelSwitch #3 (access level) shall meet at least the following requirements:

43


1. Have at least 32 SFP+ slots in each access switch;2. Have at least 10 transceivers 10 Gbps for connecting server equipment;3. Have at least 8 (eight) SFP+ slots in each access switch for communicating with core

switches;4. Have at least 2 transceivers 10 Gbps for communicating with core switches;5. Support integration with the core switch as a virtual module;6. Height not more than 1U;7. Support air blow-out to the hot zone.

2.3.7. Information Security System LAN information security solutions shall meet at least the following requirements.

2.3.7.1. Architecture1. The information security architecture shall imply a multi-level protection model of the basic

infrastructure of the IP network.2. It is required to use up-to-date protection tools against unauthorized access.3. It is required to ensure firewalls and create protected segments (DMZ) on the basis of

hardware facilities as per paragraph 2.3.7.3, namely: Utilize a cluster solution in Active/Active mode; Ensure the Statefull Failover functionality; Use equipment with standby power supply units; Enable virtualization (division into virtual FW), with at least 5 (five) virtual FW available; Create several security zones with different access levels.

4. Ensure secure access to information resources by means of utilizing security policies and delimiting security zones.

5. Ensure use of smart network mechanisms protecting access to data. 6. Ensure secure inter-network interaction using the VPN technology.7. Use security analysis tools of the network infrastructure.8. Use tools for detecting and preventing intrusions. 9. Ensure backup of the existing system of centralized authentication, authorization and audit

for ensuring centralized organization of network identification and streamlining user control in the hardware with a possibility of simultaneous work with 500 devices on the basis of software-hardware facilities as per paragraph 2.3.7.5.

10. Develop methods and ways of protecting interfaces of hardware facilities of the LAN infrastructure, interfaces with external and related systems and with the Internet using new-generation information security technologies.

11. Develop control and monitoring methods using information security tools, namely: Use a unified management system of security rules to control all the FW and intrusion

detection and prevention tools; Implement a centralized solution (the equipment shall be located at the Consignee’s

premises) to control the distributed security infrastructure; Ensure universal remote access to LAN information resources, RHM DCN nodes, namely:

Implement the functionality of the VPN concentrator to terminate protected connections with users via the Internet; Ensure the performance of the VPN concentrator at least 400 Mbps.

44


2.3.7.2. Developing Policies of the Multi-Level LAN Security Strategy1. Take into account requirements of guidance documents, provisions, regulations and

instructions on LAN and DCN information security.2. Formulate tasks to ensure information security and develop tools to solve the tasks.3. Take into account specific features of the network infrastructure.4. Develop user authentication procedures on the basis of the RADIUS/TACACS+ protocols.5. Develop rules for delimiting user access to the network information resources on the basis of

security policies and access lists in FW.

2.3.7.3. Firewall #1Firewall #1 is designed to form a protected fault-tolerant access node to information

resources, protect segments of the local-area network (LAN) against unauthorized access and destructive actions of offenders (protection of LAN segments, protection of information interaction via RHM communication channels and via the Internet).

Firewall #1 shall meet at least the following requirements:1. Random-access memory at least 12 GB;2. Flash-memory size at least 8 GB;3. Built-in ports: at least 8 ports 10/100/1000 Mbps;4. Control ports: at least one port 10/100/1000 Mbps;5. Available tool for detecting and preventing intrusions with performance at least 900 Mbps.Software:6. Cisco Adaptive Security Appliance Software;7. Cisco Adaptive Security Device Manager;8. Support operation in the modes: Active/Standby and Active/Active;9. Support services: SSL and IPSec VPN;10. Compatibility with the existing control system of the Consignee (CiscoWorks, including all

the functionality of the management and control system);Performance:11. Maximal channel (throughput) capacity: at least 1.5 Gbps;12. Maximal quantity of supported simultaneous connections: at least 750000;13. Maximal quantity of Site-to-Site and Remote Access VPN sessions: at least 2500;14. Maximal quantity of SSL VPN sessions: at least 2500;15. Maximal channel capacity 3DES VPN: at least 400 Mbps.

2.3.7.4. Firewall #2Firewall #2 is designed to delimit access between the Supercomputer zone and the

existing network. Firewall #2 shall meet at least the following requirements:1. It shall be built-in into the existing switches Cisco Catalyst 6500;Software:2. Cisco Adaptive Security Appliance Software;3. Cisco Adaptive Security Device Manager;4. Support operation in the modes: Active/Standby and Active/Active;5. Compatibility with the existing control system of the Consignee (CiscoWorks, including all

the functionality of the management and control system);

45


Performance:6. Maximal channel (throughput) capacity: at least 16 Gbps;7. Maximal quantity of supported simultaneous connections: at least 10000000;8. Maximal quantity of establishing new connections: at least 300000 per second;9. Maximal quantity of virtual subnets (VLAN): at least 1000;10. At least 5 (five) virtual FW available;11. Maximal quantity of entries in access lists: at least 2000000.

2.3.7.5. Centralized Authentication, Authorization and Audit System #1The System shall meet at least the following requirements:

1. Be made of the following components: policy administration point (PAP) and policy decision points (PDP);

2. Support AAA protocols: RADIUS and TACACS+;3. Support authentication protocols: PAP, MS-CHAP, Extensible Authentication Protocol

(EAP)-MD5, Protected EAP (PEAP), EAP-Flexible Authentication via Secure Tunneling (FAST), and EAP-Transport Layer Security (TLS);

4. Support integration with Windows Active Directory and LDAP;5. Maintain audit logs of user actions (including attempts to violate security policies);6. Support information collection for systems that account for consumption of network

resources (traffic);7. Support the SSL protocol for controlling web interface;8. Enable information storage about accounting and audit in the CSV format for convenient

import to the billing systems;9. Support extendable user attributes: Vendor Specific Attributes (VSA);10. Enable access on the basis of policies to be determined by the administrator, with access

delimitation by device, time, and authentication protocol;11. Enable control and management of all settings via a web interface;12. Support flexible control and delimitation of authority and functions of administrators on the

basis of role models;13. Be compatible with the Consignee’s existing control system (CiscoWorks, including all the

functionality of the management and control system);14. Form factor: the system shall be mountable in to a rack, not more than 1 RU;15. The system shall have the following input/output ports: 1 serial port, 4 USB 2.0, VGA

Video;16. The system shall have at least 4 interfaces RJ-45 10/100/1000 Mbps;17. Random-access memory at least 16 GB.

2.3.8. LAN Control and Monitoring System The Control and Monitoring System shall meet at least the below requirements.It is required to do the following:

1. Implement centralized control and monitoring of all the devices operated in the network, including the existing equipment;

2. Implement centralized control and monitoring of active equipment on the basis of an element manager control system;

46


3. Implement centralized control and monitoring of equipment on the basis of an enterprise manager control system;

4. Ensure simultaneous control and monitoring of at least 150 devices; 5. Ensure control and configuration of technical facilities;6. Ensure control and status display of technical facilities;7. Ensure operational detection and localization of emergency and failure situations;8. Implement tools to collect statistic data;9. Ensure compatibility with control systems from various Manufacturers and with Consignee’s

existing systems; 10. Develop control methods of information flows;11. Ensure that the subsystem has a complete set of integrated applications for control from the

network administrator’s work station: Develop a graphic interface and visual graphic presentation of the network topology,

including active network equipment and channel infrastructure; Ensure control of network operability from the network control station; Ensure access control of any user station to LAN ports from the central console; Ensure automatic detection of devices in the network; Ensure monitoring of the workload of data transmission channels, utilization intensity of

work stations, servers, and network information resources; Ensure issue of warnings about near critical events in accordance with adjustable filters

and thresholds; Provide tools for collecting statistic data about flows and data in the network; Provide tools for analyzing and decoding protocols; Provide a flexible mechanism for generating reports; Ensure notifying in case of detecting emergency and failure situations; Implement logging of administrators’ activities and active network equipment operation; Implement tools and methods for creating filters to support control of data flows; Ensure a possibility of distributed, remote control and management of the LAN

infrastructure.

2.3.9. LAN Security Policies Management System The system of centralized security policies management shall meet at least the below

requirements.It is required to implement a centralized security policies management system with the

following characteristics:1. Support all the devices manufactured by Cisco that ensure network security, including the

existing equipment;2. A powerful and friendly control mechanism of objects and rules;3. Ensure a possibility of analyzing compliance of the existing access lists with the required

security rules; 4. Ensure a possibility of system messages from Cisco ASA/ASASM/FWSM devices;5. Ensure a possibility of generating reports about passed traffic;6. Ensure a possibility of adding new signatures to intrusion prevention devices;7. Ensure a possibility of setting VPN connections.

47


2.4. Software

2.4.1. General Requirements1. All SW shall be compatible with the related equipment. 2. The following list of software shall be supplied:Software distribution version on an optical disk (CD or DVD);SW shall be supplied with a compete set of documents; at least one electronic and one paper copy are required;Required licenses and registration data for legal SW use in related equipment.

3. All the licenses shall be drawn out to the Consignees and intended for operation at the actual installation addresses (paragraph 1.4);

4. All the licenses for the supplied software shall be permanent;5. All the functions set out in paragraph 2.4 shall be implemented. The implementation shall be

supported with appropriated hardware pieces;6. All the equipment and software shall be provided for (including pieces not explicitly

mentioned in the Technical Requirements) that is required to implement the functions as per paragraph 2.4.

2.4.2. System Software Tools and System Control Tools of the Supercomputer

The system software tools and system control tools of the Supercomputer shall meet at least the following requirements:1. The operating system shall be a 64-bit industrial multi-user OS SuSE Linux Enterprise

Server for all the Supercomputer nodes and be supported by the Manufacturer of the Supercomputer;

2. The software tools of the Supercomputer shall support parallel access of each computer node to the Disk Data Storage System #2;

3. The parallel file system shall support at least the following functions:Minimal scalability:

Up to 4000 clients;Size: 10 PB;

Control and monitoring functions;Quotas for users/groups;4. Software tools shall be provided for centralized management of access rights and

authorizations. The Supercomputer shall execute only authorized tasks on behalf of a user via the batch job processing system;

5. A system of batch job processing shall be provided (the service shall be backed up in a fault-tolerant cluster). The software requirements are set out in paragraph 2.4.6.

2.4.3. Set of Software Tools for Control of Backup Copying and Data Recovery

The set of software tools for control of backup copying and data recovery shall support at least the following:

1. Unified interface integrating technologies of creating local data copies in disks;

48


2. Automatic backup copying of selected files and file system data using various backup copying policies (at least full and incremental copying);Backup copying in the operational mode;

3. Manual recovery of files and file systems from backup copies, with selection options of recovered data by saving time;

4. Backup copying of catalogues/files of the parallel file system;5. Backup copying of data of Disk Data Storage Systems without using the LAN.

2.4.4. Set of Software Tools for Control of Hierarchic Data Storage The set of software tools for control of hierarchic data storage shall meet at least the

following characteristics:1. File migration: automated or following a user’s / administrator’s command;2. All servers of hierarchic data storage shall be utilized simultaneously for input/output

operations of the parallel file system for even workload distribution; 3. Multi-level migration shall be performed, namely, a possibility of using disk space as an

interim level, and network migration;4. Automatic migration by the criteria of: creation/circulation time (age), file size, user

group, and disk space fill level; 5. Automatic migration shall be performed by the following criteria:

File type;Creation/circulation time (age);File size;User group and disk space fill level.

2.4.5. SW of the Monitoring and Control System of the Computer Complex The Bidder shall propose SW of the Monitoring and Control System integrated for the

Supercomputer and the Data Management System.1. The system shall support functions: remote switch on, switch off, console, software

installation, etc. The software shall be recommended by the Manufacturer of the equipment for monitoring and control and shall support the following: Monitoring and control of the proposed equipment and the Supercomputer; Graphic and command user interface to be a single monitoring and control point of the

systems; Possibility of selecting a metric for monitoring of hardware facilities and software for

each node of the systems (at least 100); Console functions ensuring complete remote control, including: switch on, switch off,

screen transmission in the console mode (e.g.: blue error screen in MS Windows, system crash in Linux) via IPMI and other interfaces;

Selection of report versions from sets for error messages and possible corrective actions; Adjustable style for presenting the operability status of a system under control

(dashboard); Simultaneous preparation/fill (provisioning) of set images of system software to minimize

preparation time of computer complexes for work; Individual control of image versions, OS cores, installed distribution versions, programs

and file systems; Complete control of power consumption by server, group of servers/nodes, and the

Supercomputer;

49


Centralized presentation and analysis of memory errors; Management of updates of the BMC, BIOS from a single point; Role distribution in the monitoring/control system for groups and users;

2. Control of Supercomputer systems:Compatibility with the batch job processing system;Control of the Supercomputer and server equipment in the command and graphic modes, including: Equipment control functions before the operating system loading shall be supported (work with BIOS and BMC, power-off status, OS crash, information about the status of hardware facilities). The hardware shall support the mentioned functions; Control of communication equipment; Control of Disk Storage Systems, including software and hardware configuration; Power switching on and off in servers of the system;Transfer of the Computer Complex to the “power-off” mode upon a signal from the UPS, CVSSR and AGFES (with/without a confirmation by the administrator);Configuration of system hardware resources and system start or restart.3. Software tools shall operate in the System Console #1 and System Console #2, be accessible

within the LAN in the graphic mode; 4. Software tools shall provide a graphic interface to the user.

2.4.6. SW of the Batch Job Processing System A system of batch job processing shall be provided (with the service backed up in a fault-

tolerant cluster) to implement the following functions:Provide a graphic interface to the user;Start parallel jobs (MPI, OpenMP);Built-in tools for manual and automatic optimization of queues of parallel jobs;Guaranteed provision of computer resources for any job in the queue;Prioritization of jobs;Workload distribution between nodes based on the workload intensity of a resource;Job start out of a queue based on the job dependency criterion;Simultaneous stop/start of the active job in all the nodes;Start of jobs from the queue with prior file loading and automatic reset/migration of files after the job is completed;Automating re-queuing of jobs selected for control purposes or all failed jobs;Prioritization of jobs dependent on power consumption requirements;Output of statistic data on power consumption for performed tasks;Output of analytical information on use of computer resources for performed tasks;Compatibility with the existing batch job processing system, including use of the existing licenses.

2.4.7. Resource Access Control SoftwareThe access control software shall support the following:

1. Tools for authorized access to file information and support of standard file rights in Linux owner/group/world;

2. User passwords shall be stored in a specialized place so that access to them is given to only privileged users or processes;

3. Centralized logging tools of user log-in to the system;

50


4. Report generation tools from security logs;5. Determined and implemented unified set of delimitation and control rules of access to

computer and information resources of the system;6. Determining individual rights and authority of each user to use corporate resources;7. Authentication of users and network devices;8. Support of various authentication systems: routine protocols of OS of the Microsoft

Windows family, LDAP, LDAP over SSL, using digital certificates, including those with the help of smart cards;

9. Support of user access to information system resources via single sign-on authentication mechanisms.

2.4.8. Application Development and Debug ToolsThe Bidder shall propose the following software tools for the Linux OS to work in the

supplied Supercomputer:1. Compilers:CompilerC++; CompilerFortran; 2. Libraries and software models:Library Math Kernel Library (MKL); Library TBB;Library IPP;3. Parallel programming libraries:Library MPI; 4. Performance analyzer Trace Analyzer and Collector;5. Performance analyzer VTune Amplifier for OS Linux ;6. Debugger Inspector;7. The products listed in points 1-6 are included into the product Intel Cluster Studio XE; 8. Licenses for the products as per points 1-6 shall support simultaneous work of 5 users;9. Graphical tools for developing, profiling and debugging parallel programs in the C, C++ and

FORTRAN languages for at least 4 users. Debugger TotalView to debug parallel programs shall be offered (with a 1-year warranty from the Manufacturer for the mentioned product);

Licenses for program profiling and debugging shall support:Work of at least one user in up to 64 processors inclusive; and at least 4 users

shall simultaneously have a possibility of working in 16 processors10. The libraries shall be available for users and integrated in the programming environment

(PE). The functions of the libraries shall be called from users’ programs written in various programming languages as mentioned in point 1.

2.4.9. Optimization and Development Software for Work StationsSW tools shall be provided with functionality analogous to that mentioned in paragraph

2.4.88 (1-6) for installation in 10 personal computers of the x86_64 architecture operated by OS Linux.

51

http://www.intel.com/cd/software/products/emea/rus/vtune/343476.htm


2.4.10. Virtualization Platform SoftwareThe SW of the Virtualization Platform shall meet at least the following requirements:

1. It shall be supplied with licenses sufficient for use of all the supplied virtualization servers as hardware virtualization tools;

2. Supplied licenses for the SW of the VP shall enable placement of an unlimited number of virtual machines within this VP without any additional costs;

3. The VP shall have the following virtualization objects:Processor and random-access memory;Data Storage System;Computer network of the Ethernet standard.4. The control tools of the VP shall have the following:Graphical administrator and user interface;Command administrator interface;Software interface (API);Enable complete management (creating, deleting, status changing) of VP objects.5. The options and list of services that can be managed by a VP user shall include the

following:Creating and deleting virtual networks and virtual switches;Creating, deleting, changing assigned resources, stopping and starting virtual servers;Creating, deleting, and increasing the size of virtual volumes;Connecting and disconnecting virtual volumes;Creating and deleting virtual volume images;Creating and deleting virtual server templates.6. A possibility shall be designed of integrating the physical network of the Ethernet standard

with the virtual VP switch.7. The VP shall enable start of virtual servers of the x86_64 architecture.8. The VP shall automatically de-allocate occupied resources, under certain conditions.9. The VP shall have a built-in system to account for utilized resources.The accounting system shall enable report generation on any time period;The accounting system shall have a possibility of creating quoting rules and assigning them to a VP user.10. The virtualization platform shall:Re-start virtual servers in case of failure of the physical server where such virtual servers operated;Have the availability level at least 99% (without taking into account failures caused by power supply, conditioning, etc.);Have a possibility of creating volumes of different performance levels;Have a possibility of changing the performance category of volumes for an operating period;Enable adding data storages during operation;Enable integration of data storage systems of various Manufacturers;Enable creation of replicated volumes within the Virtualization Platform.

11. Interface requirementsThe VP control interface shall:

Have intuitive user interaction tools;Have a possibility of connecting to the graphic console of a virtual server via a web interface.

A possibility shall be designed of remote work with the control interface via the Internet.

52


A possibility shall be designed of creating virtual work stations.Access to virtual work stations shall be designed via a web browser, software client or with the help of the thin client.The VP shall maintain statistic records about the workload on processors, consumed memory, and utilized disk and network resources.The VP shall have a possibility of locating files of a certain size.A control system of access to located objects shall be designed.Access to the storage of VP objects shall be via the HTTP, HTTPS protocols.

12. Information security requirementsVP virtual networks shall be delimited at the second level of the OSI model.A possibility shall be designed of access management to virtual networks via the protocols: TCP, UDP, ICMP, GRE, ESP, AH via ports and IP networks. Access to software interfaces shall be protected with the SSL protocol.Each request shall be signed with a cryptographically resistant algorithm.VP software interfaces shall be accessible via the HTTP protocol.The VP shall enable assigning an external IP address to any virtual server.The VP shall have a firewall as its part. The VP firewall shall enable adding or deleting access rules to virtual networks. Each rule shall include a network from which access is allowed, an access protocol and a port, if possible.

2.4.11. Software of Virtual MachinesTo roll out specialized Consignee’s tasks in the VP environment, it is required to supply the following SW (in addition to the SW required to roll out the VP, SIS, and WSMS):

1. Microsoft Windows Server – 36 pieces;2. Microsoft System Center Standard Edition with the quality sufficient for 36 virtual

virtualization nodes on the basis of two-processor servers;3. OS SLES – 10 pieces;4. PositiveTechnologies XSpider 7.7 Professional Edition 256 IP addresses (1С network

2.4.12. System of Infrastructure ServicesThe System of Infrastructure Services (SIS) shall meet at least the following

requirements: 1. The SIS shall be located on the basis of the VP;;

2. It shall enable migration of existing components of the Consignee’s SIS to the newly built infrastructure; ;

3. To prevent disruption of any of the designed services used in the SIS operation, redundancy of services (DS, BNSS, UCS, mail subsystem) and technical facilities that are crucial for normal operation of the SIS, shall be designed;

4. Distributed SIS components shall be interconnected: Via the channels of the DCN of the RHM with the channel capacity at least 1 Mbps; Via Internet channels with the channel capacity at least 10 Mbps.

53


The TCP/IP protocol shall be used as the main transportation protocol of the mentioned information networks;.

5. When building the SIS and its parts, interaction shall be organized between existing Consignee’s directory services, mail systems and corresponding parts of the SIS to be built; migration of the services shall be organized to the SIS to be built without any interruptions in the services;

6. Information about failures in the work of the services and their components included into the SIS shall be entered into OS system logs and specialized control and diagnostic applications, stating the values of the main operation parameters of the services and their components as of the denial of service moment. Notifications about critically important events in the system status shall be duplicated via e-mail to the addresses of system administrators;

7. The SIS to be developed shall support logical delimitation of access rights to reading and changing information stored in the SIS at the level of UDS objects;

8. The developed SIS shall ensure protection against unauthorized access and destructive external impact;

9. SIS components of all levels shall interact using standardized procedures and protocols;10. SIS service names and TCP/IP server addresses shall be unique to the extent of the whole

existing RHM infrastructure. Agreement of names and addresses with the Consignee shall be at the Contract performance stage;

11. At the SIS design stage, uniform rules and methods shall be developed for identifying/marking objects in the SIS for all the Sites.

2.4.12.1. SIS Structure1. The SIS structure shall be built on the hierarchic principle to support centralized control of

information resources. 2. It shall enable delegation of administrative powers related to management of SIS services to

Consignee’s administrators to the extent sufficient for them to execute their professional duties, with control retained at higher hierarchy levels.

3. The SIS shall include:1) Universal Directory Service (UDS) subsystem;2) Basic network service subsystem (BNSS);3) Mail subsystem;4) United communications subsystem (UCS).4. The universal directory service shall be designed for use in Consignee’s information systems

as a unified storage of data about all the objects and components included into the information system.

5. The basic network service subsystem shall be designed for automated assignment of IP addresses to work stations for establishing correlation between digital IP addresses and text names of domain records, and for time synchronizing.

6. The mail subsystem shall be designed for information exchange between Consignee’s employees and/or external correspondents by e-mail.

7. The UCS shall be designed for organizing information exchange between Consignee’s employees by means of exchanging instant messages, availability information, holding audio, video and web conferences and shared work with applications.

54


2.4.12.2. UDS SubsystemThe UDS shall meet at least the following requirements:

1. The UDS shall support a possibility of managing account records of users and work stations in the directory;

2. The UDS shall support a possibility of centralized management and delegation of administrative powers to administrators of Consignee’s subdivisions;

3. The UDS shall support a possibility of reliable authentication of users and control of access rights to directory objects;

4. The UDS shall support distributed storage of directory data;5. The UDS shall support storage in Consignee’s DS distributed servers of a range of

accounting data of SIS objects that would be enough for autonomous work with network resources when no communication channel is available;

6. .7. The UDS shall support navigation and search in the universal directory.

2.4.12.3. Basic Network Service Subsystem The basic network service subsystem shall meet at least the following requirements:

The DNS domain name resolution service shall be the main service for resolution of computer names in the SIS. The DNS shall enable SIS operability if a DNS server or a communication channel (Internet channels, DCN channel) fail; The DHCP service shall act as the dynamic IP address allocation service. The list of objects to be operated by the DHCP service shall be determined at the design stage; The NTP service shall be used and the time service for the whole organization. The NTP service shall be synchronized with an external time source in the Internet.

2.4.12.4. Mail SubsystemThe Mail Subsystem shall meet at least the following requirements:

The mail subsystem shall support a possibility of creating mail boxes for 350 users; The mail subsystem shall support access of users to their mail boxes from the Consignee’s local-area network, the RHM DCN, and from the Internet;The mail subsystem shall support delivery of mail messages to the given address (addresses) both inside and outside the mail organization; The mail subsystem shall support a possibility of creating a unified hierarchic address book in the frameworks of the RHM LAN and DCN;The mail subsystem shall support an access possibility of all users of the mail subsystem to the address book;The mail subsystem shall support a possibility of working with the calendar, including shared work for several users;The mail subsystem shall provide a possibility of establishing quotas to limit the size of mail boxes;The mail subsystem shall support a possibility of centralized management and delegation of administrative functions to the administrators of Consignee’s subdivisions;The mail subsystem shall be identical to the existing Consignee’s system;The mail subsystem shall support all-round protection against harmful virus programs and unauthorized group mailing (spam);It shall support archiving of the mail system to external information media;The mail subsystem shall be integrated with the UCS;

55


The mail subsystem shall be integrated with the e-mail system of the RHM DCN. A description of the e-mail subsystem of the RHM DCN will be submitted to the Supplier at the Contract performance stage.

2.4.12.5. United Communications SubsystemThe united communications subsystem shall meet at least the following requirements:

The UCS shall support operation for 200 users; The UCS shall support search for users in a unified address book;A UCS user shall have a possibility of forming an own contact list of UCS users; A UCS user shall have a possibility of getting information about accessibility of other UCS users;A UCS user shall have a possibility of setting own accessibility status;Some UCS user accessibility statuses shall be established automatically;A UCS user shall have a possibility of exchanging instant messages with other UCS users; A UCS user shall have a possibility of organizing and participating in instant message exchange conferences with other UCS users (with 2 or more participants);A UCS user shall have a possibility of organizing and participating in joint desktop or open application viewing conferences (with two or more users). The organizer shall have a possibility of control transfer (cursor control and keyboard typing) to other participants in the conference;A UCS user shall have a possibility of answering an incoming call with an instant message; A UCS user shall have a possibility of organizing and participating in videoconferences with other UCS users (with two or more participants);A UCS user who hosts a conference shall have a possibility of adding and deleting one or more participants in the conference;UCS users who participate in a conference shall have a possibility of viewing the image from the camera of the active (speaking) participant in the conference;UCS users who participate in a conference shall have a possibility of turning off his/her microphone for the other participants not to hear him/her;UCS users who participate in a conference shall have a possibility of turning off his/her video image for the other participants not to see him/her;

The UCS shall be integrated with the mail system. The UCS shall be integrated with the RHM DCN, the subsystem of departmental IP telephoning and the public telephone network

2.4.13. Workstation Management SystemThe Workstation Management System shall meet at least the following requirements:

1. The Workstation Management System (WSMS) shall support centralized monitoring of the composition and parameters of the software, updates of the software and automated performance of routine works with the software installed in work stations in the LAN. The minimal quantity of work stations to be connected to the WSMS in parallel shall be 350;

2. The WSMS shall be implemented on the basis of the VP;3. The WSMS shall include the following functional subsystems:Hardware inventorying;Software inventorying;Software roll-out;Updates roll-out;OS image roll-out;Configurations control;Remote control.

56


4. All parts of the WSMS shall be connected between each other by means of information networks using the existing computer networks;

5. WSMS diagnostics shall be by means of tools and event logs of the operating system to be built into the installed software;

6. The WSMS to be developed shall support logical delimitation of access rights to reading and changing information stored in the SIS at the level of UDS objects;

7. The names of servers and TCP/IP addresses shall be unique to the extent of the whole existing infrastructure.

2.4.13.1. Hardware Inventorying SubsystemThe hardware inventorying subsystem shall meet at least the following requirements:

1. The subsystem shall carry out automatic inventorying of hardware of workstations and servers;

2. Inventory of hardware of work stations and servers shall present data about the following:CDROM reading devices;Monitor;Hard disks;Mother board;Processor;Video adapter;Random-access memory;Network adapters;Services;3. The subsystem shall support a possibility of viewing the data of hardware inventory of

individual work stations and servers using built-in tools;4. The subsystem shall support a possibility of getting reports about the results of hardware

inventorying of work stations and servers.

2.4.13.2. Software Inventorying SubsystemThe software inventorying subsystem shall meet at least the following requirements:

1. The subsystem shall carry out automatic inventorying of the software installed in work stations and servers. Inventory of the software of work stations and servers shall present information about the names, locations and versions of executed files stored in hard disks of work stations and servers;

2. The subsystem shall support a possibility of viewing data of software inventory of individual work stations and servers using built-in tools;

3. The subsystem shall support a possibility of getting reports about the results of software inventorying of work stations and servers.

2.4.13.3. Software Roll-Out Subsystem The software roll-out subsystem shall meet at least the following requirements:

1. The subsystem shall support a possibility of creating software batches;2. The subsystem shall support a possibility of creating computer collections;3. The subsystem shall support a possibility of creating assignment of software for collections;

57


4. The subsystem shall support a possibility of controlling the installation time of software batches;

5. The subsystem shall support a possibility of automatic installation of the software assigned by the System administrator into work stations;

6. The subsystem shall support a possibility of getting reports about the results of software installation;

7. When starting the assigned software in a user’s work station, the notification panel shall display a notification icon about the software installation.

2.4.13.4. Update Roll-Out SubsystemThe update roll-out subsystem shall meet at least the following requirements:

1. The subsystem shall support a possibility of setting periods for updates from the Internet;2. The subsystem shall automatically update the list of updates for the following classification

categories:Updates;Critical updates;Drives;Functional batches;Security updates;Update batches;Tools;Cumulative update batches.3. The subsystem shall automatically update the list of updates for the following available

product localizations:English;Russia;4. The subsystem shall support a possibility of update testing in a test group of computers;5. The subsystem shall support a possibility of controlling the update installation time;6. The subsystem shall support a possibility of automatic centralized installation of software

updates in work stations;7. The subsystem shall support a possibility of getting reports about the results of update

installation;8. When starting an update in a user’s work station, the notification panel shall display a

notification icon about the update installation.

2.4.13.5. OS Image Roll-Out SubsystemThe OS image roll-out subsystem shall meet at least the following requirements:

1. The subsystem shall support a possibility of creating images of operating systems of work stations;

2. The subsystem shall support a possibility of rolling out prepared images of operating systems into target work stations via the network using PXE;

3. The subsystem shall support a possibility of rolling out prepared images of operating systems into target work stations via the network using removable media.

2.4.13.6. Configuration Control SubsystemThe configuration control subsystem shall meet at least the following requirements:

58


1. The subsystem shall support a possibility of creating master configurations;2. The subsystem shall support a possibility of comparing current configurations with the

master configuration using built-in reports;3. The subsystem shall support a possibility of using prior created configuration batches.

2.4.13.7. Remote Control SubsystemThe remote control subsystem shall meet at least the following requirements:

1. The subsystem shall support a possibility of remote control of work stations;2. When using remote access to work station, connection to the console shall be performed only

if allowed by the user;3. For security reasons, remote access to work stations shall be allowed for authorized

administrators only, with an option of viewing and managing the remote work station.4. The subsystem shall be

2.5. Life-Support System 1. All the functions described in paragraph 2.5 shall be implemented.2. All the equipment and software (including that not explicitly mentioned in the Technical

Requirements) required to implement the functions mentioned in paragraph 2.5 shall be provided for.

3. The life-support system shall be outfitted with electricity meters with a possibility of remote monitoring per consumption area (UPSS as a whole, Supercomputer, Data Storage System, server equipment, CVSSR as a whole, CVSSR for the computer machine room, RSS, CVSSR for UPSS and RSS, etc.). The areas for accounting shall be proposed by the Supplier and agreed with the Consignee.

2.5.1. Structured Cable System (SCS)The Structured Cable System shall meet at least the following requirements:

1. The SCS is built to integrate elements of the supplied information system and connections to elements of the existing information system;

2. The fill of cable ducts and cable trays shall not exceed 50%;3. The SCS shall satisfy category 6 of standards for cable systems: EIA/TIA-568В, EIA/TIA-

568А;4. The Cable System shall comply with the European EMC Directive 89/336/EEC in

accordance with standard EN55022 (Class A и Class B); 5. The optical component shall be made of optic cable MM of the OM4 class;6. All the system components shall meet the general requirements for operating and service

safety of electronic and communication equipment in accordance with GOST R 50571.2-94.

59


2.5.2. Uninterruptible Power Supply System

2.5.2.1. General RequirementsThe Uninterruptible Power Supply System shall be implemented for the Computer

Complex located in Room #1 (Figure 5-3). The UPSS is located in Room #7 (Figure 5-4).

The Uninterruptible Power Supply System shall meet at least the following requirements:1. The proposed uninterruptible power supply system shall support operation of the Computer

Complex for 5 minutes plus the time required for a routine halt of the Computer Complex. The Bidder shall carry out assessment calculations to illustrate that the proposed UPSS configuration meets this requirement and has a 15% reserve of power, and include them into the Bid;

2. The Uninterruptible Power Supply System shall be built on the basis of Uninterruptible Power Supplies #1 (paragraph 2.5.2.2) and have a redundancy level at least N+1. A failure of any component/module shall not bring about a failure of the UPSS as a whole or a transfer to consumption from an unprotected power supply;

3. The UPSS#1 shall support staff notifying in case of emergencies occurring in it;4. The UPSS#1 shall support a possibility of operational (without switching off UPSS #1)

replacement of the main elements of the UPSS #1 directly in the installation site of the system without involving ASC specialists and without equipment disconnection;

5. The Bidder shall include information about the price of the UPSS and installation works into its Bid;

6. The UPSS#1 shall be located in the basement.

2.5.2.2. Uninterruptible Power Supply #1 (UPS #1)UPS #1 shall meet at least the following requirements:

1. The UPS shall be built on the principle of double conversion – on-line VFI device (Voltage and Frequency Independent, IEC620040-3 classification);

2. The UPS shall enable installation of a VRLA (Valve Regulated Lead Acid) battery from independent vendors;

3. Input voltage: 3-phase, 380/220 V;4. The range of input voltage without switching to the battery: at least 340 and not more than

460 V;5. The output voltage of the system shall support power supply of all the offered equipment

pieces;6. The design factor of output power shall be at least 0.9;7. Maximal permissible output voltage deviations:

±1% at static workload;±3% at dynamic workload (application or removal of 100% load);

8. Maximal permissible deviations of the frequency of the output voltage: ±1 Hz;9. Non-linear distortion factor of the output voltage:

Not more than 1.5% at linear workload;Not more than 3% at non-linear workload;

10. System overloading capacity:150% during 1 minute in the normal work mode from the input mains and

when working from the battery;125% during 10 minutes;

60


11. The UPS shall be outfitted with a device for smooth growth of the current consumed from the network when switching from the battery to the mains;

12. All the UPS shall be outfitted with remote monitoring (via the LAN) devices using the SNPM protocol;

13. All the UPS shall include software for monitoring and control;14. The UPS set shall include batteries to be located in special cabinets/shelves;15. If direct current is required to supply the Supercomputer, installation of an inverter shall be

provided for;16. The inverter shall be built on the scheme with backup at least N+1;17. The inverter may operate in the UPS mode; in such case, the power of the UPS#1 may be

reduced by the inverter power;18. The inverter and its storage batteries shall meet all the requirements established for the

UPSS.

2.5.3. Conditioning and Ventilation System of Service Rooms (CVSSR)The CVSSR shall be implemented to support operation of the Computer Complex.

2.5.3.1. General RequirementsThe CVSSR shall meet at least the following requirements:

1. The CVSSR shall ensure efficient removal of excessive heat and create environment as prescribed by the Manufacturers of utilized equipment pieces and by effective normative documents in the computer machine room, in the UPSS room, and in the room of the refrigeration supply system (RSS);

2. Calculation of the heat emission power shall be made in accordance to SNiP 41-01-2003 “Heating, ventilation and air conditioning”, with regard to total heat emission of technical facilities, electric engineering equipment, electric illumination, radiant heat flow, heat flows from construction structures, service staff and the ventilation system of related rooms;

3. Noise protection shall be implemented with regard to: SNiP 23-03-2003 (2004) “Protection against noise”, GOST 12.1.003-83 “System of standards for labor safety. Noise. General safety requirements”;

If the rated parameters of SNiP 41-01-2003 “Heating, ventilation and air conditioning”, SNiP 23-03-2003 (2004) “Protection against noise”, GOST 12.1.003-83 “System of standards for labor safety. Noise. General safety requirements” are exceeded because of technical characteristics of installed technical facilities, organizational measures shall be taken.

4. The CVSSR shall support uninterrupted (all year round, 24 hours a day, including the starting and halting modes) operation of the Computer Complex (365х7х24) at the external temperature range:

from -40 ºС to +40 ºС;5. The CVSSR shall retain operability when the load is changed from 100% to 25% of the

maximal load; 6. The CVSSR shall be implemented on the backup scheme at least N+1 of all the active

components. The function of even resource wear-out of all active components shall be implemented;

61


7. In case of emergency disconnection, autonomous operation of the CVSSR shall be supported calculated as 5 minutes of maximal workload plus the time required for routine halt of the Computer Complex;

8. Control of CVSSR active equipment shall be performed by its monitoring and supervision system (MSS);

9. The CVSSR (all its main elements) shall be outfitted with routine remote monitoring/control features of the BACnet protocol;

10. All the CVSSR large-unit equipment pieces (chillers, fan-coils, conditioners) shall be outfitted with remote monitoring features of the SNMP protocol;

11. All the main CVSSR nodes and components shall be easily accessible for pre-commissioning, routine maintenance and preventive works. The system shall be repairable with a possible halt of the Computer Complex for a period up to 1.5 hours according to the Technical Requirements;

12. All the CVSSR equipment pieces shall be grounded;13. Non-specific requirements for the CVSSR shall be in accordance with Instruction СН-512-78

“Instructions on designing building and premises for electronic computer machines” and requirements of the Manufacturer of the proposed CVSSR;

14. The Bidder shall include information about the price of the CVSSR and installation works into its Bid.

2.5.3.2. CVSSR of the Computer Machine RoomThe CVSSR of the Computer Machine Room shall meet at least the following requirements:1. It is required to design operation of a heat flow removal system of the combined type in the

machine computer room: direct water cooling of the most energy-intensive equipment and air cooling of the rest of the equipment. The direct water cooling of the Computer Complex shall use technological cooled water to be supplied to the machine room from the refrigeration supply system;

2. It is required to outfit the water contour (contours) with a water filling and automatic replenishment system with a required purification level.;

3. The requirements for the composition and quality of the supplied water shall be determined by the Manufacturer of the supplied equipment; but the mechanical admixture parameter shall not be worse than 200 m;

4. It is required to include a water preparation station into the CVSSR of the machine room that shall be based on reverse osmose, with required inhibitors added in the work process, and ensure antibacterial protection measures;

5. All the water supply equipment to/from the machine room shall be manufactured without ferrous metals;

6. It is required to design water collection facilities in places of pipelines in case of local leakage;

7. Air-cooled racks layout shall form a system delimiting hot and cold corridors; the air input into the racks shall meet the following temperature and humidity characteristics:

Temperature: 18-24 ºСHumidity: 40-60 %; 8. The air temperature in the machine room at the distance at least 1 m from the rack shall not

exceed 26 ºС all year round, at any operation mode of the equipment and given climate parameters;

62


9. Forced-exhaust ventilation shall be designed for all the rooms of the Computer Complex (Rooms #1, 5), production rooms of Floor 4 of the Consignee’s building (Figure 5-3) and administrative-production rooms of Floor 5 (Figure 5-5), with regard to the following: Service staff shall spend short periods of time in Rooms # 1, 5 of the Computer Complex

for routine works and repairs (up to 5 people); In other rooms, staff members shall stay on a permanent basis; When calculating the air exchange, the figures of temperature, relative humidity and air

movement speed shall be determined based on effective norms, with regard to the category of such works: easy Iа;

Equipment with reduced noise levels shall be used. The noise shall not exceed 55 dB in the maximal production mode at design conditions.

10. The existing forced-exhaust ventilation equipment is located in Room # 17 (Figure 5-5).11. Excessive pressure shall be generated in the Computer Complex room of not less than 1.5

mm/water column;12. The CVSSR shall ensure air filtering level from dust not less than G4.

2.5.3.3. Refrigeration Supply SystemThe RSS shall meet at least the following requirements:1. In rooms allocated for RSS equipment, refrigerating machines shall be installed with cooling

capacity sufficient to remove heat flows from the machine room, UPSS and RSS and with a required capacity reserve;

2. Coolers located outside the building are in the zone of residential development. Equipment shall be used with reduced noise levels;

3. Hybrid coolers of the liquid shall be used. The noise from the cooler shall not exceed 55 dB in the maximal production mode at design conditions;

4. The place to be occupied by external units shall be limited to 2.4x6.5 m and 4x8 m, including service and maintenance zones. The second area may be expanded up to 4x14 m at the expense of the drainage of one of the operated external units of the existing system. The Bid shall include any related dismounting works and organization of uninterrupted operation of the existing system;

5. All the equipment that may be located inside the building (pumping equipment, chillers, cold accumulating tanks, water preparation system, etc.), except external heat-exhaust units and cooled equipment proper shall be located in the basement;

6. It is required to design a possibility of filling and emptying all contours of the refrigeration supply system;

7. It is required to install sewage traps for water drain in places where refrigerating equipment is installed;

8. Rooms for location of refrigerating machines shall be outfitted with an emergency ventilation system.

2.5.3.4. CVSSR for UPSS and RSSThe CVSSR for UPSS and RSS shall meet at least the following requirements:1. The CVSSR shall ensure parameters in UPSS and RSS rooms that meet the requirements of

the Manufacturers of the installed equipment on the condition of workload change from 100% to 25% of the maximal workload.

2.5.3.5. Air ConditionersThe air conditioners shall meet at least the following requirements:

63


1. All the conditioners shall be for industrial purposes.2. All the conditioners shall have an option of smooth performance adjustment of fans and of

cooling capacity by means of changing performance of spiral compressors. It is not allowed to use inverter-control compressors.

3. Each conditioner included into the CVSSR shall be outfitted with standard Manufacturer’s function of automatic restart, i.e. in case of sudden power disconnection and further connection the conditioner shall automatically resume operation in the previous mode, independent of the disconnection period.

4. The conditioner shall have a self-diagnostic function to ensure detection of at least the following malfunctions: Ventilator engine malfunctions; Filter clogging; Malfunctions of temperature and humidity sensors; Inter-unit communication errors; Water leakage.

5. Each conditioner shall have a connection to an external regular touch-screen display at least 10” at a distance up to 200 m, to be installed near the operator’s work station inside the building.

6. All the conditioners in the CVSSR shall be integrated with control chains of conditioner operation for automatic control of all conditioners and monitoring of their operation status and parameters.

2.5.3.6. Monitoring and Supervision System of the CVSSR (MSS of the CVSSR) The MSS of the CVSSR shall meet at least the following requirements:1. The MSS of the CVSSR shall ensure control and efficient management of all the

technological parameters of the CVSSR to support operability of the Computer Complex. 2. The MSS of the CVSSR shall be integrated into the unified MSS of engineering systems of

the Computer Complex.3. The MSS of the CVSSR shall operate in the following modes:

a) Automatic mode: fully automatic maintenance of operation modes established by CVSSR technological parameters and control of equipment operation modes, including the starting mode of CVSSR equipment from any initial status;

b) Automated mode: control of CVSSR technological parameters by the operator from the AWS;

c) Manual mode: manual control of individual nodes and mechanisms.

4. To support the mentioned operation modes, all the CVSSR active equipment shall be outfitted with Manufacturer’s controllers with network interfaces.

5. All the rooms controlled by the MSS of the CVSSR shall be outfitted (as necessary) with temperature, humidity and leakage sensors.

6. All the controllers of CVSSR equipment, sensors inside rooms and temperature and humidity sensors of outside air shall be integrated into a unified technological network to have output to the operator’s AWS of the MSS of the CVSSR.

7. The AWS of the operator of the MSS of the CVSSR shall ensure an intuitive graphic interface for convenient and quick control of the status of CVSSR equipment and for management in the form of mnemonic schemes, event logs, and trend logs.

64


8. The MSS of the CVSSR shall support issue of warning and emergency signals to both operator’s AWS and to the monitoring and supervision system of the information system.

9. The MSS of the CVSSR shall ensure even mean time to failure of CVSSR in the automatic mode.

10. The MSS of the CVSSR shall ensure flexible response to failures of individual CVSSR nodes.

11. Solutions related to the MSS of the CVSSR shall include required redundancy and backup of active elements and discrete channels that, if lost, can cause critical CVSSR failures.

2.5.4. Automatic Gas Fire-Extinguishing System

2.5.4.1. General RequirementsThe Automatic Gas Fire-Extinguishing System (AGFES) shall be built for rooms of the

Computer Complex (Rooms # 1, 5 (Figure 5-3), Room #7 (Figure 5-4)) and shall meet at least the following requirements:1. Technical solutions taken when building the AGFES shall comply with effective norms and

regulations;2. AGFES equipment shall use standard electric links, interfaces, technologies and data

transmission protocols; 3. AGFES technical facilities subject to mandatory certification as per effective laws of the

Russian Federation, shall have required certificates;4. The AGFES shall perform the following functions:

Automatically detect fire in fire-hazardous premises and smoke in staff evacuation routes; Support automatic and remote control of technological fire-extinguishing equipment; Control operation parameters of technological equipment and issue notices about fire-

extinguishing progress; Control and manage smoke removal; Control and manage fire cut-off valves; Form fire signals to switch off ventilation systems; Issue fire notices to switch on the staff warning system; Control the “closed” status of fire doors; Carry out diagnostics of AGFES technical facilities and form a signal in case of

malfunctions as unreadiness for operation;

5. The AGFES shall support the following: Receive signals from multi-sensor fire detectors; Process the signal in accordance to the fire-defense algorithms; Issue signals to manage technological fire-extinguishing equipment; Issue signals to service staff to ensure timely evacuation; Issue signals to manage engineering systems of rooms protected by the AGFES; Supply gas fire-extinguisher in order to create its fire-extinguishing concentration;

6. A 100% reserve of fire-extinguisher shall be available at the site;7. Equipment power supply:

AGFES technical facilities shall be of category 1 of electric power collectors in terms of power supply reliability as per EIR (Sections 6 and 7) and SNiP 3.05.06-85 “Electrotechnical devices”;

It is required to design power supply for ensuring equipment operation for at least 24 hours in the standby mode and 1 hour in the fire mode;

65


According to GOST R 50969-96 electric equipment, metal hoses and pipelines of installations shall be grounded;

The resistance of the grounding device used to ground electric equipment shall be not more than 4 Ohms.The chain of grounding and zero conductors shall have no disconnection applications and

fuses. Connection of grounding and zero conductors to parts of electric equipment shall be by means of welding or bolts;8. It is required to design smoke, fire-extinguisher and fire products removal from the premises

after operation of AGFE installations: With a mobile gas-removal unit;

or Stationary smoke-removal system with lower air intake;

9. The AGFES shall include the following: Fire detectors (signals); Warning alarms (announcers); Fire-extinguishing modules; Pipeline wiring; Fire alarm station to control technological equipment;

10. Technical support:a) When building the fire alarm system, it is required to use multi-sensor detectors;b) Design a data collection and processing system (concentrating equipment, AGFE stations); All the AGFE stations shall be designed with 100% hot standby; Standby shall be implemented in the hardware of each module included into a station. The

modules included into stations shall have two controllers in their cards: the main and the standby ones. Switching to the standby part shall be automatic in case of main part failure;

AGFE stubs that connect concentrating equipment shall have loop structure; AGFE stubs that connect detecting equipment shall have loop structure; A control possibility shall be designed of the clogging level and operation time of

detectors.

2.5.5. Automatic Fire Alarm System The Automatic Fire Alarm System (AFAS) shall be built for rooms of the Computer

Complex and shall meet at least the following requirements:1. The AFAS shall support very early fire or smoke detection in the protected premises to

ensure reaction time for the staff before the AGFES start; 9. The AFAS is designed to ensure the following:

Day and night control of the situation in the premises to prevent fire; Very early detection of facts of emerging fire and smoke in the protected premises; Transmission of fire notification to the rooms where staff on duty is present day and night

(fire alarm post of the building); Transmission of command signals to fire-protection systems and the access control and

management system;10. The AFAS shall include the following:

Detection tools (detectors); Data collection and processing equipment (concentrating equipment, automatic fire alarm

stations); Notification tools about the status of signalization stubs (indicators, alarm controls).

66


11. Equipment and system compliance with effective normative acts: Technical solutions in AFAS building shall be in compliance with effective norms and

regulations; AFAS equipment shall use standard electric connections, interfaces, technologies and

data transmission protocols; AFAS technical facilities subject to mandatory certification under the effective law of the

Russian Federation shall have related certificates;5. It is required to outfit the Computer Complex rooms with the AFAS;6. AFAS equipment shall support the following:

Day and night control of the situation in the rooms to prevent fire; Detection of inflammation and smoke content in the rooms; Event log maintenance, with a print-out option; Transmission of the fire notification to the rooms where staff on duty is present day and

night; Transmission of commands to unlock doors in evacuation routes; Intellectual analysis of the condition of fire detectors and issue of recommendations about

maintenance time; Hot replacement of detectors without stopping the whole system; Fault-tolerance in case of failure of fire station controller components.

7. The Automatic Fire Alarm System shall be started automatically or in a remote method when fire occurs;

8. In case of fire, a signal shall be formed to switch off the ventilation and conditioning systems in the protected rooms and a signal to switch on audible warnings;

9. When building the fire alarm system aspiration detectors shall be used to ensure early fire detection with high reliability;

10. AFAS technical facilities shall be of category 1 of electric power collectors in terms of power supply reliability as per EIR (Sections 6 and 7). Power supply (alternating current 220 V) and the grounding bus for AFAS equipment power supply shall be designed from the uninterruptible power supply distribution board;

11. It is required to design power supply for ensuring equipment operation for at least 24 hours in the standby mode and 1 hour in the fire mode;

12. The data collection and processing system (concentrating equipment, AFAS stations) shall ensure the following:

All the AGFE stations shall be designed with 100% hot standby. Standby shall be implemented in the hardware of each module included into a station. The modules included into stations shall have two controllers in their cards: the main and the standby ones. Switching to the standby part shall be automatic in case of main part failure;

AGFE stubs that connect concentrating equipment shall have loop structure;AGFE stubs that connect detecting equipment shall have loop structure;A control possibility shall be designed of the clogging level and operation time of detectors;

13. Values of the equivalent of acoustic noise generated by AFAS equipment shall comply with GOST 21552-84 “Computer equipment. General technical requirements, acceptance, testing methods, marking, packing, transportation and storage”, but not exceed the following values:

50 dB – when technological equipment and computer equipment work without a printing device;

60 dB – when the same works with a printing device;14. AFAS mounting:

67


The equipment, switching panels and connecting cable lines shall be protected against unauthorized unsealing and connections;

AFAS mounting shall follow GD 78.145-93; AFAS shall support uninterrupted day and night operation mode, with regard to

maintenance time; AFAS units and modules shall be mutually replaceable with analogous units from the

SSPTM without any or minimal additional setup; A possibility of operational repairs shall be designed by means of replacing failing nodes

and devices with similar ones from the SSPTM; Supply of a required quantity of devices and nodes shall be provided for as part of the

SSPTM for operational repairs, but at least 10% of AFAS equipment.

2.6. Service Specifications

2.6.1. General Requirements1. All the Services listed in this section shall be rendered at Project Sites as per paragraph 1.4

without any additional costs of the Customer;2. Equipment mounting, assembly and installation (paragraph 2.2) shall be performed in

accordance with the equipment location tables at Sites (Section G. Equipment LocationTables);

3. Installation and setup of system and application software (paragraph 2.4) shall be performed in accordance with the equipment location tables (Section G. Equipment Location Tables);

4. All installation works shall be performed by certified specialists of Manufacturers’ service centers.

2.6.2. Work ScopeThe Bid shall include all the work scope to organize delivery, installation, pre-

commissioning, commissioning and further operability support of the Information System during the Warranty Period.

The work scope shall include the following, among other things:1. Prepare and receive permitting documents, including agreements with supervisory authorities

for performance of works related to preparing Computer Complex rooms and installing the Life-Support System, attestation of parts of the Life-Support System with supervisory authorities upon completion of installation works, if prescribed by effective normative documents;

2. Preparatory works:o Prepare rooms for locating the Computer Complex, including works for organizing distributed load on the floors and commissioning life-support systems;o When locating the Computer Complex in Room 14 of Floor 4 (Figure 5-3), works shall be planned for integrating earlier located equipment – such as the IT equipment rack (communications) and the situation center equipment control rack. If it is impossible to integrate them into the layout scheme, it is required to provide for re-location of the mentioned equipment without operability interruption;o Test and recover operability of the existing life-support systems that must be involved in technological connections of the Computer Complex;

68


o The UPSS shall be located in place of the existing system. It is required to plan all the dismounting works of the existing systems and installation works of the new system, including cable replacement from the input automatic circuit breakers located in the MDB (QF2,QF41 800a);o Supply equipment and materials; o Mount the SCS for connecting supplied equipment, including cable ducts with accessories, cables and sockets with accessories within the location area of the Computer Complex and connections with the existing computer complex; o Install local power distribution boards or modernize the existing ones (if necessary) to connect the Computer Complex;o Modernize parts of the false floor to meet the requirements of the supplied equipment;o Lay required electric and grounding cables within the area of the Computer Complex, installing required power equipment; if necessary, install additional local power distribution boards; o Lift and locate equipment of the Computer Complex, including active LAN equipment; o Perform mounting works;o Make changes to the operating documents;o Mount equipment and connect interface cables and power supply;o Clean the rooms after work completion;

3. Mounting and installation:o Perform pre-commissioning works;o Carry out preliminary off-line and comprehensive tests;o Develop operating documents;o Carry out operational acceptance;o Carry out acceptance testing;o Commission.

4. Train Consignee’s staff;5. Provide maintenance in accordance with the warranty obligations and technical support terms

and conditions;6. Ensure certification of the FSBI “RHM MCC” as an Authorized Service Center of the

Manufacturer of the Supercomputer for possible independent support of the hardware facilities by it;

7. The work scope related to points 2-5 is listed in paragraphs 2.6.3 – 2.6.6.

2.6.3. Mounting and InstallationThe scope of works shall include the following, among other things:

1. Set up active network equipment (basic settings): Set up VLAN, LUN and zonal configuration of the SAN (if applicable); Set up ports; Perform specialized settings; Set up routing; Set up firewall features.

2. Install and set up supplied system and application software:

69


Install the operating system; Perform basic settings of the operating system; Install and perform basic settings of application software features; Perform specialized settings of system and application software tools, including

the communications network MPI; Install and set up software features of the Data Management System (set for

controlling backup copying, software control tools of hierarchic data storage);3. Install and set up access equipment and software to Disk Data Storage Systems, including the

parallel file system;4. Install and set up application software, set up the system as a whole;5. Integrate the supplied equipment and the existing system of the Consignee’s system of

computer facilities, including all the required licenses; 6. Install and set up software tools, set up the information security system;7. Install and set up software of the Monitoring and Control System;8. Install and set up equipment and software tools of work stations;9. Carry out off-line testing in Consignee’s tests and modernize (replace), if necessary, system

software (firmware, BIOS);10. Develop operating documents (technical and user documents) for operational acceptance of

the supplied equipment. See paragraph “Documentation Requirements”;11. Carry out preliminary testing, operational acceptance and acceptance testing in compliance

with the requirements of Section D. TESTING AND QUALITY EVALUATION.

2.6.4. Training

2.6.4.1. General RequirementsAs part of equipment preparation, the Supplier shall train Consignee’s staff. The training

shall meet the following requirements:1. The training shall be delivered in a training center or at the Site (at the Supplier’s discretion)

after the software and hardware is installed; 2. The training shall be delivered by trainers certified by the Manufacturer to deliver the

courses;3. The training shall include a course of theory and practical exercises, with duration of each of

the training courses at least 40 class periods (45 minutes each). Upon training completion, the trainees shall get certificates of the training center confirming completion of the training course in the subject;

4. Documents confirming completion of the training course shall permit independent activities for installing and setting up supplied SW and carrying out hardware repairs related to replacement of faulty nodes;

5. If training is delivered in a training center, the total number of trainees in a group shall not exceed 12 (twelve) people;

6. If training is delivered in a training center, the cost of training shall include accommodation costs of trainees in the training location and travel from the Site to the training location and back;

7. In all the delivered training courses, trainees shall be provided with required training materials in the Russian language. The training shall be delivered in Russian. Costs of translation services (if necessary) shall be included into the Bid price.

70


At least the following authorized training courses shall be mandatory.

2.6.4.2. Training #1 – Hardware Maintenance of the Computer ComplexIt is required to organize an authorized training course /courses in maintenance of the

hardware of the Supercomputer, servers of the Data Management System, the Monitoring and Control System, etc. The course shall include the following sections:1. Supercomputer architecture overview;2. Induction to inter-node connection technologies (hardware implementation of the

communication network MPI), implementation specific features of the Supercomputer;3. Diagnostics of hardware facilities, work with built-in software;4. Replacement of faulty nodes;5. Control of Supercomputer configurations;6. Integration and setup of the operating system.

The number of trainees shall be 5 people.

2.6.4.3. Training #2 – Administration of Disk Data Storage SystemsIt is required to organize an authorized training course in administration of Disk Data

Storage Systems. The course shall include the following sections:1. Induction into the architecture of data storage networks, specific features of the given

implementation;2. Installation, setup and administration of disk arrays;3. Specific features of utilizing external disk arrays with various operating systems (OS of the

Supercomputer, Windows Server);4. Diagnostics of hardware, work with built-in software of external disk arrays; 5. Replacement of faulty nodes.


2.6.4.4. Training #3 – Hardware Maintenance of Life-Support Systems of the Computer Complex

It is required to organize an authorized training course /courses in maintenance of the hardware of the Life-Support System of the Computer Complex (Uninterruptible Power Supply System, Conditioning System, Automatic Gas Fire-Extinguishing System, Automatic Fire Alarm System). The course shall include the following sections:1. Overview of the solution and equipment architecture;2. Diagnostics of hardware, work with built-in software;3. Replacement of faulty nodes;4. Control of equipment configurations;5. Integration into a complex.

The number of trainees shall be 4 people in each type of the systems.

2.6.4.5. Training #4 – Training in System Software Tools and System Management Tools

It is required to organize authorized training courses in maintenance of the following basic areas:

71


2.6.4.5.1. Administration and Diagnostics of Systems and Networks of the Supercomputer Operating System

The course shall include the following sections:1. System start and stop;2. OS installation and setup;3. Control of users, devices, file system and swapping environment;4. Planning of task execution;5. Start and configuration of network services and special implementation features in the

Supercomputer OS;6. Installation, configuration and control of software tools of the shared file system.

2.6.4.5.2. Operation of the Software Set of the Data Management SystemThe course shall include the following sections:

1. Overview of solutions, specific implementation features;2. Installation, configuration and control of the software control set of backup copying and data

recovery;3. Installation, configuration and control of the software control set of hierarchic data storage.

2.6.4.5.3. Operation of the Monitoring and Control SystemThe course shall include the following sections:

1. Overview of solutions, induction to the control architecture, specific implementation features;

2. Use of monitoring tools, application of graphic presentation features;3. Induction to the control architecture of servers and applications;4. Setup of user interfaces;5. Setup of data collection functions and threshold parameter values;6. Interaction of the control server with software agents installed in controlled servers,

collection of data about operation of servers and applications, and of console messages;7. Setup of presentation functions of service statuses;8. Installation, configuration and control of the Monitoring and Control System;9. Operator’s / administrator’s work with the Monitoring and Control System.

2.6.4.5.4. Operation of the Batch Job Processing SystemThe course for administrators shall include the following sections:

1. Work basics with the Supercomputer OS;2. Start of parallel jobs (MPI,OpenMP);3. Work with graphic user interface;4. Installation, configuration and administration of the Batch Job Processing System.

The number of trainees shall be 4 people in each of the areas.

2.6.4.6. Training #5 – Administration of LAN SwitchesIt is required to organize an authorized training course in administration of LAN switches.

The course shall include the following sections:1. Installation, configuration and control of hardware facilities;

72


2. Diagnostics of hardware, work with built-in software;3. Replacement of faulty nodes;4. Routing organization and configuration of static virtual local-area networks (VLAN);5. Setup of multi-level switching;6. Support of fault-tolerant routing;7. Implementation of security policies in the switched network;8. Updates of configurations and system SW.


2.6.4.7. Training #6 – LAN Control and MonitoringIt is required to organize authorized training courses in the following areas:

2.6.4.7.1. Element Manager of Active Equipment

The course shall include the following sections:1. Operation principles of control systems;2. SNMP protocol;3. Control of equipment and SW configurations;4. Work with the network map;5. Information collection about device parameters (audit);6. Event registration and administrator warning system;7. Network testing;8. SW setup of the control system.

The training shall include a course of theory and practical exercises.


2.6.4.7.2. Enterprise Manager of Equipment

The course shall include the following sections:12. Monitoring principles of interogenic equipment;2. Network map plotting;3. Event logging;4. Monitoring of device parameters;5. SW setup.

The training shall include a course of theory and practical exercises.


2.6.5. Warranty ServicesThe warranty services shall imply operability support of equipment and software of the

supplied Information System. The following shall be performed as such works:

1. Regular diagnostics of hardware and detection of malfunctions, operability recovery of hardware (including firmware) in case of failure;

2. Recovery of functionality and integrity of system SW in case of failure or malfunction of hardware.

73


All the hardware and software shall have at least the following support levels:1. Warranty #1 — at least 5 years of Manufacturer’s warranty services for the equipment of the

Supercomputer, the Data Management System, the Monitoring and Control System, all server equipment, and VP equipment (unless stipulated otherwise);

2. Warranty #2 — at least 5 years of warranty services for LAN equipment (including equipment of LAN security policies control and of the information security system);

3. Warranty #3 — at least 5 years of warranty services for the Life-Support System;4. Warranty #4 — at least 20 years of warranty services for the SCS;5. Warranties #1, #2 shall include updates of the relevant SW (update/upgrade firmware, BIOS,

IOS, etc.);6. The Bidder shall guarantee that the idle time of the Computer Complex (installed SW and

equipment) caused by malfunctions will not be more than 72 hours a year and not more than 12 hours running during the warranty period.

All the software shall have at least the following support:7. Warranty #5 — at least 5 years of standard Manufacturers’ service support for all the

supplied software (unless stipulated otherwise);8. The software warranty shall include a quality guaranty of the software media and software

updates;9. All the works shall be agreed with the Consignee and shall be performed without disrupting

the operational technological cycle.

The result of the warranty services shall be support of fail-proof operation of the Information System.

2.6.6. Technical SupportThe technical support shall ensure a set of technical and organizational activities for

uninterrupted operation, setting and modernization of the hardware part, system and application SW supplied under the Contract.1. All the technical support shall be provided by the established Technical Support Service on

the basis of an Authorized Service Center (ASC). The ASC shall be authorized by the Manufacturer of the related equipment. The Bidder shall submit authorization documents as part of its Bid.

2. The Technical Support Service shall be established for the following two areas: Technical support of computer equipment; Technical support of life-support systems.

3. The TSS shall ensure timely updates of firmware of the supplied equipment, updates of all the software under the Contract in accordance with the upgrades and patches issued by the related Manufacturer.

4. The TSS shall be outfitted with a set of required diagnostic tools and SSPTM.5. Support of mathematical libraries and compilers shall be provided as part of technical

support of the Supercomputer. This type of support shall be performed by the TSS of the ASC.

As part of the mentioned support, timely installation of new software versions, updates and patches, and testing in Consignee’s tasks shall be ensured, with regard to the uninterrupted technological process.

74


6. All the replacement equipment and spare parts shall be manufactured or certified by the original Manufacturer and have the same or better characteristics.

7. The Supplier shall ensure warranty and maintenance services of supplied products (including SSPTM and consumables) during the warranty period without any additional costs of the Purchaser and the Consignee. The types and periodicity of maintenance of hardware facilities shall be in compliance with the operating, maintenance and repair requirements set out in the Manufacturer’s documents.

8. ASC shall provide a hot line on warranty service issues (contact phone, fax, and e-mail address) to receive requests from Consignees for warranty services. The contact phone and fax shall be in the cities where the modernized Sites are located or a free telephone line shall be organized (e.g. using the 800 code).

9. For Warranties #1, #2, #3 the ASC shall receive Consignees’ requests 24 hours a day. For Warranties #4 and #5 the ASC shall receive requests on working days from 9:00 to 18:00 Moscow time. All the requests shall be entered into the Request Log, with the request name, date and time of application.

10. Supplier’s staff shall analyze the condition of the Computer Complex following a Consignee’s request via the hot line during a visit to the site where the Computer Complex is located:

(M) – within 3 hours;

(R) – on the following working day

after the registration (in a centralized way through the FSBI MCC of the RHM). 11. The ASC staff shall speak fluent Russian.12. Hardware warranty services (Warranties #1, #2 and #3) shall be performed according to

service programs that shall ensure at least the following:1. When available Computer Complex resources (performance or available disk space) are

reduced by not more than 20%, the Supplier shall recover resource availability within not more than 7 days after the request receipt;

2. When available Computer Complex resources (performance or available disk space) are reduced by more than 20%, the Supplier shall recover resource availability (to 80%) within not more than 3 days, and follow point 1 of this paragraph further on.

13. The Supplier shall provide consultations on optimization of application SW in the supplied Computer Complex to the Consignee within at least one year after the acceptance testing date.

14. If the warranty repairs period is more than the operability recovery limits, the Supplier shall ensure operability over the period by means of providing equivalent equipment.

15. The overall duration of warranty repairs shall not exceed 60 working days.16. Warranty services shall be rendered at the Site where the equipment is located. If equipment

transportation is required to the Supplier’s ASC and back, it shall be performed by the Supplier at its own account.

17. Within 2 years, the Supplier shall provide consulting assistance to the Consignee on issues related to resource management of the Complex and optimization and setup of application software for not more than eight hours a week. Such assistance shall be rendered in the Russian language.

18. A description of technical support programs and contact data of the hot line (contact phone, fax, and e-mail) shall be included into the Bid.

75


19. To meet reliability requirements, a set of spare parts, tools, accessories and consumables shall be established to be located at the Site where the Computer Complex is installed. The list of consumables shall support a half-year reserve in accordance with the hardware Manufacturers’ requirements for operating conditions.

2.7. Documentation RequirementsAs part of its services, the Supplier shall develop and submit to the Consignee the

following range of technical documents (contractor’s and operating documents) in compliance with the following effective normative documents:1. The Supplier shall prepare at least the following set of contractor’s and operating documents

under GOST 34.201-89, GOST 34.003-90, GD 50-682-89, GD 50-680-88, in the Russian language and submit it on paper and in an electronic format (at least one copy of each):

List of operating documents; Testing programs and methods; Information System certificate under Guidance Document (GD) 50-34.698-90, issued by

the State Committee for Standardization of the Russian Federation; User manual for installation, administration and recovery; Block diagram with a description of the set of technical facilities; Functional diagram with and designation and interaction description of various

components; Equipment layout in the Computer Complex rooms; Equipment layout in racks; Hard- and software specifications of the Information System; Requirements for operating staff with regard to 24-hour operation mode of the Complex,

including structural, quantity and qualification characteristics;2. The contractor’s and operating documents for life-support systems and the SCS, including a

combined plan of engineering networks;3. For each type of hardware and software supplied by the Supplier, the Supplier shall submit 1

(one) set of Manufacturer’s technical documents on paper and in an electronic format; 4. No photocopies of documents on paper are allowed.5. The draft list as per points 1-2 shall be prior developed by the Supplier and agreed with the

Consignee.

2.8. Responsibilities of the ConsigneeThe Consignee shall provide the following: 1. Access of Supplier’s staff to the Site and provide a possibility of locating, using and storing

Supplier’s technological equipment for start-up and fine-tuning;2. Access to power supply at the MDB;3. Connection possibility to the existing LAN in accordance with the Technical Requirements; 4. All the required information about location of water supply points according to the

specifications of the building where the equipment will be located in order to prepare the computer room for external water supply;

5. SW submission for testing purposes (paragraph 3.1.7 (1, 2)), excluding standard tools of operating systems and libraries.

76


3. D. TESTING AND QUALITY EVALUATION1. The Bidder shall attach to its Bid results of equipment tests proposed by the Consignee and

performed in a location determined by the Bidder.2. If it is impossible to get such results in a system as required for testing (paragraph 3.1.1), the

Bidder may extrapolated real results received in an available installation to the configuration required by the Consignee for preliminary evaluation of the technical solution. E.g. if the Bidder has no installation with the processor cloak rate as in the offered configuration, it is allowed at the Bid submission stage to carry out tests in an installation with processors with an available cloak rate and to extrapolate the results to the configuration planned for supply.

3. The testing results, methods and extrapolation results (if applicable) shall be included into the Bid as an integral part.

4. Declared test results shall be transferred to the contract requirements. Future Suppliers shall be liable for non-achievement of the declared values.

5. If awarded the Contract, the Bidder shall confirm or exceed the declared results during tests after equipment installation at the Site. If the supplied equipment is unable to demonstrate the results as quoted in the Bid, the Supplier shall add any equipment required to achieve all the declared characteristics and preliminary testing results without any additional costs of the Purchaser. The system modified in the mentioned way to achieve the declared parameters shall meet all the supply requirements and conditions included into the Technical Requirements.

6. In case of significant deviations of the results of the final tests at the Site from the declared characteristics and from preliminary testing results, the Purchaser shall be entitled to reject the proposed solution as non-responsive to the bidding requirements. In such case, the Bidder’s expenses shall not be reimbursed, any funds paid to the Bidder shall be returned, and penalties payable by the Bidder to the Purchaser shall not be less than 20% of the Contract price.

3.1. Preliminary Evaluation of the Technical Solution of the Computer Complex

3.1.1. General RequirementsThe performance evaluation shall be held with the aim of finding the most efficient

technical solution for the Computer Complex. 1. The testing shall be performed by the Bidder at part of the Information System offered for

supply. The Bidder may assess parameters of the complete system. The Bidder shall submit a detailed description of the tested equipment and the extrapolation method (if any) in its Bid.

2. The testing shall be held at fixed conditions – i.e. the Bidder shall not change any parameters of the operating system, the parallel file system, the environment, etc. when performing all the testing elements. The configuration of the parameters shall be at the Bidders discretion.

3. The principle of the highest packing density at processors shall be complied with during the testing. Any deviations from the principle shall be mentioned. In any case, the Bidder shall specify which of the processors remained idle.

4. The testing results submitted together with the Bid shall include the following: Description of the technical characteristics of the hardware configuration and

architecture of the installation where the testing was performed;

77


Description of the operating environment and system environment (operating system, installed system SW, such as compilers, debuggers, optimized libraries, etc.);

Description of the parallel environment (MPI, OpenMP, optimized parallel libraries);

Texts of programs and command files used in testing; Compilation procedures, including the parameters of the compiler and the loader; Input data used for testing and start parameters; Resource distribution for the job (processors, processor numbers, quantity of

processors, utilization of their internal devices, utilization of local and external memories, etc.);

Resulting files; Results of performance tests;

5. It is allowed to use test results of similar systems for extrapolation, with a description of the differences and an explanation of the extrapolation methods;

6. The hardware configuration used by the Bidder for testing purposes, shall include mandatory interconnections (inter-node, inter-rack connections) if it is part of the Bid. The interconnection topologies that are used in testing and offered for supply shall be identical;

7. The minimal peak performance of the configuration of the system part offered for evaluation shall be at least:

150 TFlops;8. The Consignee shall submit tests for performance evaluation as described in paragraph 3.1.7;9. Based on the testing results, a documentary confirmation shall be submitted of

responsiveness of the Computer Complex characteristics to the requirements of section 2.2;10. The Purchaser may reject a Bid that includes knowingly false information.

3.1.2. Evaluation of the Maximal Achieved Performance of the Supercomputer in the Linpack Test

1. The maximal achieved performance shall be measured in the Linpack test (Rmax value), TOP500 methodology.

2. If only part of the configuration offered for supply is used in testing (paragraph 3.1.1, point 1), extrapolation results to the whole system shall be submitted.

3.1.3. Communications Network Testing The test shall rely on basic primitives of the MPI library.It shall be measured in the HPCC method (http://icl.cs.utk.edu/hpcc/).

3.1.3.1. Performance Testing1. The test is designed to get characteristics of the aggregate channel capacity between nodes.2. A description of the testing procedure shall be submitted in an accompanying file.3. Results of performance tests shall be submitted as result files and a table of values.

3.1.3.2. Latency Testing1. The test is designed to get latency characteristics.2. A description of the testing procedure shall be submitted in an accompanying file.3. Results of tests shall be submitted as result files and a table of values.

78


3.1.4. Total Performance Testing of the Computer System1. The performance shall be measured in the SPEC MPI test, methodology: spec.org;2. A description of the testing procedure shall be submitted in an accompanying file.3. Results of performance tests shall be submitted as result files and a table of values.

3.1.5. Total Performance Testing of the ODP Server

1. Performance #1 shall be measure in the SPEC OMP2012 test, methodology: http://www.spec.org/omp2012.

2. A description of the testing procedure shall be submitted in an accompanying file.3. Results of performance tests shall be submitted as result files and a table of values.4. Performance #2 shall be measured in the EPCC OpenMP test, methodology:

http://www2.epcc.ed.ac.uk/computing/research_activities/openmpbench/openmp_index.html. 5. A description of the testing procedure shall be submitted in an accompanying file.6. Results of performance tests shall be submitted as result files and a table of values.

3.1.6. Performance Testing of the File System1. The performance shall be measured using the methodology: iozone.org; 2. A description of the testing procedure shall be submitted in an accompanying file.3. Results of performance tests shall be submitted as result files and a table of values.

3.1.6.1. Reading/Writing Testing from Any Node to One File (One Flow)

3.1.6.2. Parallel Reading/Writing Testing from Any Single Node to Different Files

3.1.6.3. Parallel Writing Testing from Processors of Different Nodes

3.1.7. Performance Evaluation of the Supercomputer in Consignee’s Jobs1. The Bidder shall submit testing results of RHM applied jobs. For this aim, required source

codes and test data sets, instructions on compilation and startup, use of system environment variables, and accuracy check procedures of resulting data shall be submitted to the Bidder.

2. Job testing shall be performed with input data sets. The compliance of the count results shall be tested in a Consignee’s procedure. For optimization purposes for the platform, it is allowed to use any keys and non-specialized machine-dependent library functions. To achieve compatibility of various library function standards it is allowed to correct files with original texts in which library calls are made for supporting such calls.

3. For code optimization purposes, it is not allowed to make any changes in job implementation texts (excluding those mentioned above) and solution algorithms or to use lower-level programming languages, unless explicitly specified otherwise in the test description.

4. When additional libraries are used for optimization purposes the libraries shall be included into the Bid.

5. Initial texts used to get the results shall be submitted to the Client. Any changes in the initial texts shall be documented and explained. The Bidder shall not claim intellectual property of the performed modifications of the text of Consignee’s jobs.

79


6. If the above-mentioned text modification conditions are violated, the Consignee shall be entitled to reject proposed changes in terms of their acceptability for its purposes. In such case the testing results shall be recognized non-responsive to the Bidding requirements.

3.1.7.1. Global Spectral Model 1. The initial text with a set of data required for testing shall be submitted by the Consignee. A

description of the testing procedure and instructive materials shall be submitted in the accompanying file.

2. Results of performance tests shall be submitted as result files and a table of values.

3.1.7.2. Global Finite-Difference Model (SLM)1. The initial text with a set of data required for testing shall be submitted by the Consignee. A


2. Results of performance tests shall be submitted as result files and a table of values

3.1.7.3. COSMO Model1. The initial text with a set of data required for testing shall be submitted by the Consignee. A


2. Results of performance tests shall be submitted as result files and a table of values.

3.2. Post-Qualification of the Proposed Technical SolutionThe Consignee shall retain the right to check the submitted results either being present at

the Supplier’s testing site or in a remote method. Such decision shall be taken during Bid evaluation.

The Consignee shall retain the right to check the submitted results in full in the testing site of the Supplier/Manufacturer or in a remote method before the dispatch of the complex to be supplied.

3.3. Preliminary Testing

3.3.1. Testing PreparationThe Supplier shall ensure checks of completeness of the hardware and software,

documentation, and appearance, and check for any mechanical damage immediately after the delivery and unpacking.

3.3.2. TestingThe Supplier shall perform preliminary testing to check infrastructure readiness for the

acceptance testing. The Supplier shall develop the Program and Methodology of Preliminary Testing and agree it with the Consignee before commencing equipment delivery to the Site. The contents of the Program shall be in keeping with the recommendations of GD 50-34.698-90 and GOST 34.603-92. The Testing Program shall include at least the following:

Checks of completeness of sets, appearance and equipment specifications; Off-line testing of individual infrastructure elements;

80


Off-line testing of infrastructure sub-system; Comprehensive testing of the Information System as a whole.

The committee shall include representatives of both the Consignee and the Supplier. Testing results shall be registered in minutes.

The following documents shall be drawn out for off-line testing: Stand-alone Testing Program and Methodology.

As a result of off-line testing, the following documents shall be drawn out: Minutes of off-line testing; Action plan to resolve comments based on the results of the off-line tests.

The following documents shall be drawn out for comprehensive testing: Comprehensive Testing Program and Methodology; Completion statement of mounting and adjustment works; Operating documents.

As a result of comprehensive testing, the following documents shall be drawn out: Minutes of comprehensive testing, to be approved by the Supplier and the Consignee; Action plan to resolve comments based on the results of the comprehensive tests; Statement of Operational Acceptance of the Information System.

3.4. Operational AcceptanceAt the Operational Acceptance stage, qualitative and quantitative characteristics of the

Information System shall be determined, as well as staff readiness for the IS operation. If necessary, the Supplier shall adjust the documents following Consignee’s comments.

Operational Acceptance shall follow the Testing Program and Methodology at the Operational Acceptance Stage to be prior developed by the Supplier and agreed with the Consignee. It shall set out conditions and order of operation of parts of the Information System as a whole, duration of the Operational Acceptance and system characteristics to be tested. The contents of the Program shall follow the recommendations of GD 50-34.698-90 and GOST 34.603-92.

The duration of the Operational Acceptance shall be at least 15 calendar days.

The following documents shall be submitted for the Operational Acceptance: Testing Program and Methodology at the Operational Acceptance Stage; Operating documents; Order by an authorized Consignee’s representative to carry out Operational Acceptance

of the IS.

During the Operational Acceptance period, a work log shall be kept to register IS operation duration, failures and malfunctions. Any changes to the working and operating documents during the Operational Acceptance period shall be made without issuing a change notification.

Based on the results of the Operational Acceptance, the Consignee shall draw out and approve a statement on operational acceptance completion and on admission of the Information System to Acceptance Testing.

81


3.5. Acceptance Testing

3.5.1. Testing PreparationThe aim of the acceptance testing is to confirm declared characteristics of supplied

equipment.

The Supplier shall develop the Acceptance Testing Program and Methodology and agree it with the Purchaser. The contents of the Program shall correspond to the recommendations of GD 50-34.698-90 and GOST 34.603-92.

The Program shall include at least the following: Tests of the Information System as described in paragraph 3.3.2; Checks of completeness of sets and quality of technical documents; Check of user readiness for system operation.

3.5.2. Testing 1. The Acceptance Testing of the technological infrastructure shall be performed in accordance

with the Program and Methodology mentioned in paragraph 3.5.1.2. The Acceptance Testing of the technological infrastructure shall be performed by the

Supplier and the Consignee together.3. Upon system installation, multiple tests shall be carried out for compliance with the

requirements of paragraph 2.2, including the following: Performance testing of the Supercomputer in the configuration that was used for

testing at the Bid preparation stage (paragraphs 3.1.2 - 3.1.7), including tests of the MPI communications network, the parallel file system, as well as Consignee’s application tests;

Performance testing of the Supercomputer in its complete configuration; Performance testing (Rmax value) of the Supercomputer in the Linpack test using

the TOP500 method; The Consignee shall be entitled to test any technical requirement declared in its

Bid in any set of interconnecting nodes/switches to form the minimal testing configuration.

4. The testing duration shall be at least 30 calendar days;5. During the testing period the Supplier shall demonstrate uninterrupted operation of the

Complex in accordance with the requirements set forth in the Technical Support Section. The idle time of the Computer Complex shall not exceed 3 hours and 2 hours running;

6. If the requirement for uninterrupted operation is violated the testing shall be terminated and a related statement shall be drawn out. The Supplier shall take measures to eliminate the exposed non-conformities. After the defects/discrepancies in the solution implementation are eliminated the testing shall be repeated. In case of a repeated violation of the reliability requirements a decision shall be taken whether further testing is expedient.

82


4. Е. Requirements for the Bid

4.1. General Requirements1. The Bidder shall include a detailed description of the proposed solution and its scheme in

accordance with GD 50-34.698-90 in the Russian language, including: Block diagram with a description of hardware solution parts; Functional diagram to list components and describe interaction between them; Equipment layout in rooms; Equipment layout in mounting cabinets; Specifications of proposed software and hardware, with Manufacturers’ names and

product codes; Calculations of power supply, cooling (liquid/air cooling), and weight and size

characteristics for the computer equipment and the Data Storage System. The parameters shall be stated as calculated per rack and in total. The declared data shall be confirmed by the Manufacturers;

2. The Bid shall include a scheme to depict all cable connections with a relevant table to list such connections;

3. The Bid shall include all materials mentioned in these Technical Requirements as mandatory for the Bid;

4. The Bidder shall submit and justify information about required qualifications and number of engineering-technical staff for operation and maintenance of the Computer Complexes (for each Project Site);

5. The Bid shall include calculations of operating expenses (including maintenance) to cover operation of the Computer Complexes for 10 years of their normal operation (for each Project Site). The calculations of the operating expenses shall include estimates of spare part replacement costs, with regard to spare parts price growth with time, and obsolescence or phase-out factors, among other things;

6. The Bid shall include a filled-in Technical Responsiveness Checklist (its form is presented in Table 4-3.

4.2. Preliminary Contract Plan

1. The Bidder shall submit a Preliminary Contract Plan as an integral part of its Bid. 2. The Preliminary Contract Plan shall include sections covering the following aspects:

(a) Project organization and implementation plan;(b) Supply and installation plan;(c) Training plan;(d) Testing and acceptance testing plan;(e) Service plan;(f) Schedule of resources, tasks and dates.

3. Section (а) shall set out a mandatory list of the project team, with specified roles for the whole Contract period.

83


The staff list shall include at least 2 specialists in each of the Project implementation areas (it is allowed to combine positions); replacements are allowed only upon agreement with the Consignee with a specialist with similar or better confirmed qualifications.4. The proposed Supply and Installation Plan (b) is set out in Table 4-:

The Supply Plan sets out preferable installation and acceptance dates of systems; The following deviations from the supply and acceptance dates shall be acceptable for the

Purchaser: (i) If ahead of the schedule – 6 (six) weeks; (ii)If behind the schedule – 4 (four) week.

In its Bid, the Bidders shall state specific deadlines (in weeks) not to be outside the established limits and to be stated in the final Contract for determining the check-point of the acceptance testing.

Bids with deadlines exceeding the above-mentioned limits, shall be rejected. Interests for adjusting the Bid with the aim of earlier or later completion of installation

and acceptance works as compared to the mentioned dates shall not be applicable. The proposed Supply and Installation Plan shall be submitted in the form as in Table 4-3.

5. Sections (с) – (e) shall be executed with regard to the requirements herein.

84


Table 4-3 Technical Responsiveness Checklist Form

#

Paragraph number as per the Technical Requirements

Man

dato

ry (M

)

Tech

nica

l evi

denc

e to

con

firm

res

pons

iven

ess

Cro

ss-r

efer

ence

s to

conf

irm

ing

info

rmat

ion

in th

e Te

chni

cal P

ropo

sal

Res

pons

ive

/ Non

-res

pons

ive

85


Table 4-2. Preliminary Contract Plan

# Subsystem / ItemNumber as per the Technical Requirements

Site Code Commencement Completion

1 Preparation, agreement and approval of the Contract Plan W1 W2

2Development and acquisition of permitting documents, including agreements with supervisory authorities

2.6.2. (1) W1 W10

3

Development and agreement of the set of documents for supply of Supercomputer equipment, SW and life-support systems (including documents for equipment export, customs import clearing, compliance certificates, etc.)

W1 W10

4 Performance of preparatory works 2.6.2. (2) W10 W15

5 Supply and mounting of life-support systems of the Supercomputer W12 W20

6 Equipment supply to the Site W20 W227 Equipment mounting W21 W268 Software supply W25 W269 Software installation W26 W27

10Certification of the FSBI MCC of the RHM as the ASC of the Manufacturer of the Supercomputer

2.6.2 (6) W25 W30

11 Training 2.6.4 W27 W3412 Preliminary Testing 3.3 W14 W28

86


13 Attestation of systems upon installation completion (as applicable) W22 W28

14 Operational Acceptance 3.4 W28 W3015 Changes to the documents 2.7 W31 W3216 Acceptance Testing 3.5 W33 W3817 Technical Support 2.6.6 W39 W29918 Warranty Services 2.6.5 W39 W299

87


Table 4-4 Preliminary Contract Plan Form

#

Subs

yste

m /

Item

Con

figur

atio

n ta

ble

#

Proj

ect S

ite /

Cod

e

Del

iver

y (t

o be

stat

ed b

y th

e B

idde

r in

the

Prel

imin

ary

Con

tract

Pla

n)

Inst

alla

tion

(in w

eeks

afte

r the

C

ontra

ct E

ffec

tive

Dat

e)

Serv

ice

Com

men

cem

ent (

in w

eeks

af

ter t

he C

ontra

ct E

ffec

tive

Dat

e)

Serv

ice

Com

plet

ion

(in w

eek

afte

r th

e C

ontra

ct E

ffec

tive

Dat

e)

Liqu

idat

ed D

amag

es (Y

es /

No)

88


5. F. Floor Plans for Location of Computer Complexes

89


Figure 5-2. Plan of Floor 2 with the rooms of the existing computer complex in the WMC in Moscow

90


Figure 5-3. Plan of Floor 4 with the rooms of the Computer Complex in the WMC in Moscow

91


BASEMENT

Figure 5-4. Floor plan with the rooms of engineering equipment of the Computer Complex in the WMC in Moscow

92


Figure 5-5. Plan of the administrative and production floor in the WMC in Moscow

93


Figure 5-6. Floor plan with the rooms of the computer complex in the RSMC in Khabarovsk

94


Figure 5-7. Equipment layout scheme in the rooms of the computer complex in the RSMC in Khabarovsk

95


Figure 5-8. Floor plan with the rooms of the computer complex in the RSMC in Novosibirsk

96


Figure 5-9. Equipment layout scheme in the rooms of the computer complex in the RSMC in Novosibirsk

97


6. G. Equipment Location Tables

98


Table 6-5. Equipment Location for the WMC in Moscow (the MCC of the RHM)

№ Description

Paragraph

number as per

the Technic

al Specifica

tions

Comments

Quantity in room / Room #

Total

1

Floor 4

5

Floor 4 6Floor 2

10

Floor 1

Hardware of the Computer Complex and OtherEquipment 2.2 1

Supercomputer 2.2.2 1 1System Console #1 of the Supercomputer 2.2.2.1 Cluster 1 1System Console #2 2.2.2.2 1FRONT-END System of the 2.2.2.3 Cluster 1 1Batch Job Processing System 2.2.2.4 Cluster 1 1License Management System 2.2.2.5 Cluster 1Data Management System 2.2.4Disk Data Storage System 2.2.4.1 1 1Disk Data Storage System #2 2.2.4.2 1 1Servers of the Data Management System 2.2.4.3Archiving and Backup Copying Server 2.2.4.3.1 Cluster 1 1Hierarchic Data Storage Server 2.2.4.3.2 Cluster 1 1Server for Data Access from LAN 2.2.4.3.3 Cluster 1 1Operational System Servers 2.2.5Operational Product Generating Server 2.2.5.1 Cluster 1Operational Data Processing Server 2.2.5.2 1 1Work Group Server # 1 2.2.5.3 Cluster 1 1Work Group Server #2 2.2.5.4 1 1Technological Segment Server 2.2.5.5The Monitoring and Control System Server 2.2.6 Cluster 1Resource Access Control Server 2.2.7 1 1Virtualization Platform 2.2.8 Set 1 1Local-Area Network 2.3Switch #1 – Core Level 2.3.4 1 1 1 1 2 1 2 2

99


№ Description

Paragraph

number as per

the Technic

al

Comments


Total1

Floor 4

5

Floor 4

6Floor 2

10

Floor 1

Switch #2 – Access Level 2.3.5

To be distributed across floors *) The quantity is to be determined in accordance with the Technical Requirements

1 1 *)

Switch #3 – Access level 2.3.6

To be distributed across floors *) The quantity is to be determined in accordance with the Technical Requirements

*)

Information Security SystemFirewall #1 2.3.7.3 1 1 1 4 2Firewall #2 2.3.7.4 1 1Centralized Authentication, Authorization and AuditSystem #1

2.3.7.5 1 1 2

LAN Control and Monitoring System 2.3.8 1LAN Security Policies Management System 2.3.9 1Software 2.4System Software Tools and System Control Tools of theSupercomputer 2.4.2 1 1

Set of Software Tools for Control of Backup Copying and DataRecovery 2.4.3 1 1

Set of Software Tools for Control of Hierarchic Data Storage 2.4.4 1 1SW of the Monitoring and Control System of the ComputerComplex 2.4.5 1 1

SW of the Batch Job Processing System 2.4.6 1 1Resource Access Control Software 2.4.7 1

100


№ Description

Paragraph

number as per

the Technic

al

Comments


Total1

Floor 4

5

Floor 4

6Floor 2

10

Floor 1

Application Development and Debug Tools 2.4.88 1 1

Optimization and Development Software for Work Stations 2.4.9

To be distributed in work stations of SW

developers (may have no connection to the

LAN)

10

Virtualization Platform SWError:Reference sourcenot found

1

1

Software Tools of Virtual Machines 2.4.11 1 1

Error: Reference source not found

Error:Reference sourcenot found

1

1

Error: Reference source not found

Error:Reference sourcenot found

1

1

Life-Support System 2.5

Structured Cable System (SCS) 2.5.1To be distributed across floors 1

Uninterruptible Power Supply System 2.5.2 1 1Conditioning and Ventilation System of Service Rooms(CVSSR) 2.5.3 1 1

Automatic Gas Fire-Extinguishing System 2.5.4 1Automatic Fire Alarm System 2.5.5 1

101


Table 6-6. Equipment Location for the RSMC in Novosibirsk

№ Description

Paragraph

number as per

the Technic

al Specifica

tions

Comments

Quantity in room / Room # Total222

Floor 2

Hardware of the Computer Complex and OtherEquipment 2.2

Supercomputer (R) 2.2.2 1 1System Console #1 of the Supercomputer 2.2.2.1 1 1FRONT-END System of the 2.2.2.3 1 1Data Management System 2.2.4Disk Data Storage System 2.2.4.1 1 1

Software 2.4System Software Tools and System Control Tools of theSupercomputer 2.4.2 1

SW of the Monitoring and Control System of the ComputerComplex 2.4.5 1

SW of the Batch Job Processing System 2.4.6 1

102


Table 6-7. Equipment Location for the RSMC in Khabarovsk

№ Description

Paragraph

Number as per

the Technic

al Specifica

tions

Comments

Quantity in room / Room # Total220

Floor 2

Hardware of the Computer Complex and OtherEquipment 2.2

Supercomputer (R) 2.2.2 1 1System Console #1 2.2.2.1 1 1FRONT-END System of the 2.2.2.3 1 1Data Management System 2.2.4Disk Data Storage System 2.2.4.1 1 1

Software 2.4System Software Tools and System Control Tools of theSupercomputer 2.4.2 1

SW of the Monitoring and Control System of the ComputerComplex 2.4.5 1

SW of the Batch Job Processing System 2.4.6 1

103