ONGC TRIPURA POWER COMPANY LIMITED TECHNICAL SPECIFICATION FOR DATA CENTRE AND IT INFRASTRUCTURE SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE AT DELHI OFFICE AND PALATANA PLANT (This document is meant for the exclusive purpose of bidding against this specification and shall not be transferred, reproduced or otherwise used for purposes other than that for which it is specifically issued).
TECHNICAL SPECIFICATIONS FOR DATA CENTRE & IT INFRASTRUCTURE AT DELHI OFFICE & PALATANA PLANT TABLE OF CONTENT Clause No. Description Page No. 1.0 Background 3 2.0 Scope of Supply 4 3.0 Hardware Sizing for SAP 10 4.0 Design Considerations & Critical Factors Hardware for IT 12 Infrastructure 5.0 Design Considerations & Critical Factors Hardware for Data 16 Centre 6.0 Technical Specification for Blade Chassis 19 7.0 Technical Specification for Servers, Database Central 23 Instance (DB-CI) Design Considerations & RAS features 8.0 Technical Specification for Storage 50 9.0 Technical Specification for Tape Library and Tape Drive 57 10.0 Technical Specification for Tape Cartridges 60 11.0 Technical Specification for Network and Security Setup 62 12.0 Technical Specification for Load Balancers 110 13.0 Technical Specification for Racks 118 14.0 Technical Specification for Passive Work 121 15.0 Technical Specification for Scanner 133 16.0 Technical Specification for LINUX Operating System 135 17.0 Technical Specification for Backup Software 138 18.0 Technical Specification for Enterprise Management System 143 19.0 Technical Specification for Virtualization Software 166 20.0 Technical Specification for E-Mail Gateway Anti-spam & Antivirus 173 Software 21.0 Technical Specification for Data Centre Infrastructure (DELHI) 176 22.0 Technical Specification for Server Room Infrastructure 190 (PALATANA) 23.0 Technical Specification for Static / Source Transfer Switch 201 24.0 Technical Specification for Fire Proof Media Enclosure 203
1.0 BACKGROUND Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE SECTION - 1.0 SCOPE OF SUPPLY & DESIGN REQUIREMENTS 1.1 ONGC Tripura Power Company Limited (hereinafter referred as " OTPC" or "Owner"), a joint venture company promoted by Oil and Natural Gas Corporation Limited (" ONGC"), Infrastructure Leasing and Financial Services Limited (" IL&FS") and Government of Tripura, is a public limited company incorporated under the Indian Companies Act, 1956 and having its registered office at ONGC Tripura Assets, Badarghat Complex, Agartala, Tripura-799014 (India), and one of its office at 6 th Floor, IFCI Tower, 61, Nehru Place, New Delhi-110019 (India). 1.2 OTPC is setting up Data Centre and IT Infrastructure at Delhi office and Palatana plant, which is about 60 (sixty) km from the capit al city of Agartala in the State of Tripura. The setup shall cater to the ERP implementation and other IT infrastructure requirement. 1.3 The SAP ERP project is an end-to-end implementation of an IT Solution at OTPC. SAP ECC 6.0 with latest enhancement package shall be implemented with following modules: 1.3.1 SAP ERP - Finance & Costing Module 1.3.2 SAP ERP Management Accounting Module 1.3.3 SAP ERP Material Management Module 1.3.4 SAP ERP Human Resource Management Module & Payroll 1.3.5 SAP ERP Public Sector management Funds Management 1.4 Delhi and Palatana locations are currently not connected through any kind of network. The internet access for both the locations is independent. The email system is running at Delhi and Palatana users access e-mail remotely through Internet. 1.5 Existing LAN setup at Palatana is spread across different buildings in the campus. These buildings are interconnected using Wi-Fi (Building to Building). The ISP s STM link is terminated at BHEL office in administrative building. Fibre is laid from administrative block to Control and Facility Building. The outdoor access point at Control and Facility Block connects Switch Yard Control Block and Administrative Block. One Access Point is provided at Switch Yard Control Block and one at Administrative Block. Diagram Below gives a high-level representation of the present LAN setup at Palatana Technical Specifications Page 3
. 1.6 Existing Network Setup (At Delhi Office): The existing LAN at OTPC HO (Delhi) is spread across on 6th floor of IFCI Tower, Nehru place, New Delhi. CAT 6 cabling is used for networking. The entire setup is housed in 2 racks (1 for server and 1 for Voice and Data). 2.0 SCOPE OF SUPPLY The Scope of supply specified inter-alia below includes items necessary for the successful implementation of IT and Data Centre infrastructure for SAP ERP Implementation at Delhi and Palatana, Tripura. All the items offered shall be with 5 years warranty and 24 x 7 on-site support. The quantities mentioned for IT and Data Centre infrastructure are indicative and the minimum required for the implementation, contractor shall supply necessary material of all the items required Technical Specifications Page 4
for setting-up IT and Data Centre infrastructure at Delhi office and Palatana Plant as per the good design and industry practices. The basic Scope of supply covers the following in general: 2.1 IT Hardware Decription Minimum Quantity Location 2.2 Blade Chassis As Delhi 2.3 Servers 2.3.1 Blade Servers for SAP ERP 2.3.1.1 IDES Server As Delhi 2.3.1.2 Development Server 2.3.1.2.1 ERP Development Server As Delhi 2.3.1.2.2 SAP Net weaver Portal Server As Delhi 2.3.1.3 Quality and Training Server 2.3.1.3.1 ERP Quality Server As Delhi 2.3.1.3.2 SAP Net weaver Portal Server As Delhi 2.3.1.4 Production Servers 2.3.1.4.1 DB / CI (Database / Central Instance) Server As Delhi 2.3.1.4.2 Application Server As Delhi 2.3.1.5 Enterprise Portal Production Server 2.3.1.5.1 DB / CI (Database / Central Instance) Server As Delhi 2.3.1.5.2 Application Server As Delhi 2.3.1.6 SAP Solution Manager As Delhi 2.3.1.7 SAP Router As Delhi 2.3.2 Blade Servers for Backup Software As Delhi Technical Specifications Page 5
2.3.3 Blade Servers for Enterprise Management System (EMS) 2.3.4 Blade Servers for Infrastructure Setup As Delhi Delhi 2.3.4.1 Domain Controller and DNS 2 No. Delhi 2.3.4.2 DHCP Server Primary & Windows Update Service 2.3.4.3 DHCP Server Secondary & NTP Server 1 No. Delhi 1 No. Delhi 2.3.4.4 Antivirus Server 1 No. Delhi 2.3.5 Blade Servers for Anti-spam & E-Mail Gateway Antivirus 2.3.6 Blade Servers for existing production upgrade (E -Mail Migration and Setup) 2.3.7 Rack Servers for Domain Controller, DNS, DHCP, Windows Update Service and Antivirus (Minimum 2 Physical Servers) 2.3.7.1 Domain Controller + DHCP + Windows Update Service 2 No. Delhi 4 No. Delhi Palatana 2 No. Palatana 2.3.7.2 Antivirus Server 1 No. Palatana 2.4 Storage 2.4.1 Storage Area Network (SAN) 1 No. Delhi 2.4.2 Network Attached Storage (NAS) 1 No. Palatana 2.5 Tape Library / Drive 2.5.1 LTO-6 (Liner Tape Open Generation 6) Tape Library 2.5.2 LTO-6 (Liner Tape Open Generation 6) Tape Drive 1 No. Delhi 1 No. Palatana 2.6 Tape Cartridges 2.6.1 LTO-6 tape cartridges (with bar codes) 150 No. Delhi Technical Specifications Page 6
2.6.2 LTO-6 tape cartridges (with bar codes) 2.6.3 LTO-6 cleaning cartridges (with bar codes) 2.6.4 LTO-6 cleaning cartridges (with bar codes) 30 No. Palatana 20 No. Delhi 5 No. Palatana 2.7 Network 2.7.1 SAN Switch 2 No. Delhi 2.7.2 Core Switch 2 No. Delhi 2.7.3 DMZ (De-Militarized) Zone 2 No. Delhi 2.7.4 Aggregation Switch 2 No. Delhi 2.7.5 WAN (Wide Area Network) Switch 2 No. Delhi 2.7.6 48 Port LAN (Local Area Network) Switch 2 No. Delhi 2.7.7 Core Switch 2 No. Palatana 2.7.8 48 Port LAN (Local Area Network) Switch 6 No. Palatana 2.7.9 24 Port LAN (Local Area Network) Switch 2.7.10 MPLS (Multi -Protocol Label Switching) VPN Router 14 No. Palatana 2 No. Delhi 2.7.11 Internet Routers 2 No. Delhi 2.7.12 MPLS (Multi -Protocol Label Switching) VPN Router 2 No. Palatana 2.7.13 WAN (Wide Area Network) Links 1 Lot Delhi & Palatana 2.7.14 Internet Links 1 Lot Delhi & Palatana 2.8 Security Technical Specifications Page 7
2.8.1 External (Perimeter) Firewall 2 No. Delhi 2.8.2 Internal Firewall 2 No. Delhi 2.8.3 DLP (Data Lo ss Prevention) & Information security enforcement solution 1 No. Delhi 2.9 Load Balancers 2 No. Delhi 2.10 Racks 2.10.1 42U Rack (Network & Server) 1 No. Palatana 2.10.2 12U Wall Mount Network Racks 19 No. Palatana 2.11 Passive Work 2.11.1 Wall Mount Patch Panels As Delhi 2.11.2 Patch Panels for Server & Network Rack 2.11.3 Patch Panels for Wall Mount Network Racks As As Palatana Palatana 2.12 Scanner 1 No. Delhi 2.13 Software 2.13.1 LINUX Operating System (Media & Licenses) 2.13.2 Microsoft Windows Server Operating System (Media & Licenses) 2.13.3 Microsoft Windows Server Operating System (Media & Licenses) 2.13.4 Microsoft Exchange 2013 (Media & Licenses) As As As Delhi Delhi Palatana 2.13.4.1 Microsoft Exchange Server 2013 Enterprise 2013 2.13.4.2 Microsoft Exchange Server 2013 Standard 2013 2.13.4.3 Microsoft Exchange Standard CAL 2013 (User CAL) 2 No. Delhi 2 No. Delhi 100 No. Delhi Technical Specifications Page 8
2.13.4.4 Microsoft Exchange Enterprise CAL 2013 (User CAL) 2.13.4.5 SAN (Subject Alternative Name) SSL Digital Certificates 100 No. Delhi 4 No. Delhi 2.13.5 Backup Software (Media & Licenses) & Backup Agents 2.13.6 Backup Software (Media & Licenses) & Agents 2.13.7 Enterprise Management Software (Media & Licenses) 2.13.8 Virtualization Software (Media & Licenses) 2.13.9 Virtualization Software (Media & Licenses) As As As As As Delhi Palatana Delhi Delhi Palatana 2.13.10 E-Mail Gateway Anti-spam & Antivirus Software As Delhi 2.13.11 Client Access Licenses (User) for Windows Servers For 100 Users 100 Users Delhi & Palatana 2.14 Data Centre Infrastructure 2.14.1 UPS for Server Area 2 No. Delhi 2.14.2 Air Conditioning System for Server Room 2 No. Delhi 2.14.3 Access Control System 1 No. Delhi 2.14.4 Fire Detection and Alarm System 1 No. Delhi 2.14.5 Fire Suppression System 1 No. Delhi 2.14.6 CCTV Surveillance System 1 Set Delhi 2.14.7 Monitoring System 1 Set Delhi 2.14.8 Water Leakage System 1 No. Delhi 2.14.9 Rodent Repellent System 1 No. Delhi Technical Specifications Page 9
2.14.10 Civil Work As Delhi 2.14.11 Electrical Work As Delhi 2.15 Server Room Infrastructure Palatana 2.15.1 UPS for Server Area 2 No. Palatana 2.15.2 Precision Air Conditioning System for Server Room 2 No. Palatana 2.15.3 Civil Work As Palatana 2.15.4 Access Control System 1 No. Palatana 2.15.5 Electrical Work As Palatana 2.15.6 Fire Detection & Alarm System 1 No. Palatana 2.15.7 CCTV System 1 Set Palatana 2.15.8 Water Leakage Detection System 1 No. Palatana 2.15.9 Rodent Repellent System 1 No. Palatana 2.16 Static/Source Transfer Switch 1 No. Delhi 2.17 Fire Proof Media Enclosure 1 No. Delhi 2.18 Passive (Cabling) Material As Delhi & Palatana 2.18.1 CAT 6A Cabling As Delhi & Palatana 2.18.2 Fibre Cabling As Delhi & Palatana 2.18.3 Other Accessories As Delhi & Palatana 3.0 Hardware Sizing for SAP ERP Following table shows the minimum required configuration for SAP ERP environment. This is the minimum configuration as given by M/s SAP India, however supplier may provide higher configuration if required. Technical Specifications Page 10
/ recommended Configuration Users Base SAPS at 65% CPU Core Team Training Systems Additional Loading on Base SAPS Recommended SAPS RAM (GB) Disk (GB) - SAP & Oracle Software Disk (GB) Database IDES Server 10 2500 0% 2500 16 150 800 Remarks Development Systems ECC Development System 20 1500 0% 1500 16 150 400 SAP Netweaver Portal + NDWI 20 1500 0% 2500 16 150 300 Quality Servers + Training Servers ECC Quality System 20 2000 0% 2000 16 150 800 SAP Netweaver Portal 20 2000 0% 2000 16 150 300 Production Servers ECC Production System 5200 Database Server 30% 1560 75% 2730 24 150 800 Central Instance 30% 1560 75% 2730 24 150 Application Server 70% 3640 75% 6370 24 150 Enterprise Portal Production 2000 Database/CI Server 100% 2000 100% 4000 24 150 300 Application Server 100% 2000 100% 4000 24 150 around 35 ERP users HA Cluster HA Cluster SAP Solution Manager 150 2000 3000 16 150 300 Windows/Linux SAP SAP Router 8 150 High End Desktop Machine Technical Specifications Page 11
Reverse Proxy 8 150 In case of Internet scenario Total SAPS 33330 224 3300 3.1 The table provides the RAM required for application. Additional memory for overload due to Operating System and virtualization shall be provided. Also these memories are indicative only and memory shall be supplied as per the configuration guidelines provided in above table at clause 3.0. 3.2 For Development, Quality Assurance & End User Training Systems: As these systems are not business critical systems, no high availability (HA) feature is required for these. Accordingly the Database and Central Instance for each of the system in this environment shall be configured in central mode (No DB-CI Cluster). 3.3 All critical components (for production setup) shall be in HA (Highly-Available) mode to ensure business continuity. 3.4 All application servers requirement (for production setup) shall be fulfilled by providing multiple servers with minimum 13500 SAPS each to provide scalability and redundancy 3.5 For ERP, additional load shall be considered for printing, batch jobs, interfaces, extractions, custom development 3.6 All production systems SAPS rating requirement are indicated for 65% CPU Utilization. 4.0 Design Considerations and Critical Factors Hardware for IT Infrastructure 4.1 Critical Factors Following critical factors should be considered while selecting the configuration of Hardware, Software and Data Centre Components: 4.1.1 Scalable 4.1.1.1 The architecture offered must support scaling to provide continuous growth to meet changing business requirements with respect to the changing IT computing equipments. 4.1.1.2 All the power consuming components of IT Infrastructure must have scalability options to avoid over sizing & reduce the incredible wastage of power. Technical Specifications Page 12
4.1.2 Availability 4.1.2.1 There shall be multiple level redundancies in the critical components used in Data Centre to reduce the MTTR (Mean time to repair) to the minimum & to provide the maximum up-time to the Data Centre as a whole. 4.1.3 Modularity 4.1.3.1 To the extent possible, all the Components used in the Data Centre physical architecture shall be modular & hot swappable in nature, so as to minimize the human error as well as down time due to critical faults. 4.1.4 Redundancy 4.1.4.1 While designing physical infrastructure, Supplier must consider minimum N + 1 redundancy for all the critical active components. 4.1.4.2 Since OTPC is hosting business critical applications, N + 2 or N + N redundancies are to be appropriately used to achieve above 99.5 % uptime on services to business users. 4.1.5 Manageability 4.1.5.1 Ease of configuration, on-going health monitoring, and failure detection are vital to the goals of scalability, availability, and security and must be able to match the growth of the environment. 4.1.5.2 In this respect it is required to consolidate applications on minimum servers. 4.2 Design Consideration 4.2.1 Latest and proven technologies in the market shall be offered. 4.2.2 Shall not supply products which will be End of Sale (EOS) in next 24 (Twenty Four) months from the date of supply and End of Life (EOL) in next 5 (five) years from the date of taking over of the facility. Supplier shall guarantee availability of spares for a minimum period of 7 (seven) years from date of supply. 4.2.3 All the servers shall have facility to access the Internal/External DVD ROM Drive for OS, software and patch installations. In case of external DVD ROM, at least 4 DVD ROM shall be supplied per Blade Chassis. 4.2.4 Shall design the IP addressing schema for OTPC. 4.2.5 Hardware shall be supplied for 24x7 environments. Technical Specifications Page 13
4.2.6 Supply and install all necessary cables (fibre and cooper networking cable, power cables from UPS, control etc.), adaptors, power cords and any other interconnects as per the technical specification. 4.2.7 Documentation of the complete system including the following shall be submitted: 4.2.7.1 Factory / site test certificates of various equipments supplied 4.2.7.2 Original Manufacturers manuals and warranty cards 4.2.7.3 Installation certificates of all equipments, description of configuration profile as executed for different equipment 4.2.7.4 Standard OEM checklist for installation, maintenance etc, if any 4.2.7.5 Training documents 4.2.8 The supplied material shall be complete in all respect to meet the RFP requirements and infrastructure objective of SAP-ERP project. 4.2.8.1 Any item (Hardware and / or Software/Licenses) not specifically mentioned in contract and not supplied by supplier but are required for successful completion of facility as per technical specifications and performance requirement shall be supplied free of cost at the earliest, so that committed implementation schedule shall not get affected. In case the implementation schedule is affected, Liquidity charges will be applied. 4.2.8.2 In case this situation of any hardware / software/licenses found short or not quoted but required to meet the tender conditions, arises during warranty and AMC period, the supplies, installation and commissioning of the relevant hardware/ software/ License shall have to be made free of cost and completed within 8 weeks from the date of detection of such shortfall / inadequacy. 4.2.9 Shall ensure that all the devices, servers and hardware appliance supplied are rack mountable and provided with required rack mounting accessories / kit. 4.2.10 Data Centre space is limited and at premium. So supplier shall optimize on the rackspace requirement and take all other measures to fit in the IT infrastructure in available space. 4.2.11 Shall provide the technology which minimizes total power and cooling requirement for the Data Centre without compromising the performance. Technical Specifications Page 14
4.2.12 The power supplies, cables, connectors etc. for all equipment shall be suitable for Indian power specifications of voltage, frequency and phasing and matching the requirements completely. 4.2.13 Supplied material should be such that all the specified features and specifications mentioned in detailed technical specifications are complied with. 4.2.14 Material should include all other supporting material as required to ensure smooth implementation. 4.2.15 Remote Management 4.2.15.1 Facility shall have a remote management functionality to operate the server in both in in-band and out-of-band. This feature must be part of the server without need to install any additional hardware or software and any additional licensing requirements. 4.2.15.2 It shall have facility to manage the servers and get access to critical information about the health of the server from any remote location with just the help of a standard web browser. 4.2.15.3 It shall support hardware based and OS independent remote management like remote power on/off the server. It should support SSL encryption. 4.2.16 Server, Storage and Tape library shall be supplied from the same OEM. 4.3 Design Consideration specific to LAN Switches and Network Cabling 4.3.1 LAN Switches 4.3.1.1 Ethernet ports, SFPs, SFP+ and switch interconnecting cables required for connectivity on the switch shall satisfy the LAN point s requirements. 4.3.1.2 For interconnecting 2 or more floor switches, proper interconnecting cables shall be used to provide the maximum available bandwidth (minimum 1Gbps required) between switches using a single port. Link aggregation shall not be used to achieve higher bandwidth. 4.3.2 Network Cabling 4.3.2.1 UTP CAT6 cabling shall support 1Gbps connectivity. 4.3.2.2 LAN / fiber cabling shall support all types of traffic (data, voice or video). 4.3.2.3 UTP CAT6 LAN Cabling shall be able to carry power for PoE devices. 4.3.2.4 Shall use cabling standards and follow the structured cabling industry practices. Technical Specifications Page 15
4.3.2.5 Fiber termination on LIUs shall be of SC type with proper interfaces. 4.3.2.6 A minimum of 20 years cabling (LAN / fiber) product warranty by OEM sh all be ensured. 4.3.2.7 The network racks power supplies cables shall be suitable for Indian power specifications of voltage, frequency, and phasing, and match the power requirements. 4.3.2.8 All the cable interfaces, connectors, etc. are included in scope of supply. This shall include fixing of LIU, connecters, cables, and components to make the circuit operational. 4.3.2.9 Each building shall have redundant fiber connectivity to the Server room (Admin) building at plant site (Palatana, Tripura) 4.3.2.10 Uplink ports from each building shall be on fiber and shall terminate on Core Switch at Admin building at Palatana Plant Site. 4.3.2.11 To save the space on network rack at Data Centre (Delhi), external wall mount patch panel shall be supplied. It shall support minimum 250 ports including the current requirement of data and voice ports. 4.4 Virtualization: Virtualization shall be considered without compromising on performance and availability of service to OTPC s business users. Hence applications shall be consolidated on minimum physical servers using virtualization. 5.0 Design Considerations and Critical Factors Hardware for Data Centre Infrastructure 5.1 OTPC Data Centre shall be designed considering the following critical factors and requirements: 5.1.1 Minimize the capital investment as well as the operating & maintenance cost of the Data Centre. 5.1.2 Data Centre physical infrastructure must be designed with highly efficient & reliable components available in the market. 5.1.3 Power: All the components of the Data Centre must be designed to have the minimum power consumption without affecting the operations of the Data Centre. Technical Specifications Page 16
5.1.4 Scalability: Components of the Data Centre physical architecture must support scaling to provide future growth to meet future IT requirements. All the components in the Data Centre must have scalability to meet the future requirement and optimum solution at present. 5.1.5 Availability and Redundancy: While designing the Data Centre physical infrastructure Redundancy must be considered for all the active components. All the critical components used must provide redundancy level like N+N, N+1 to provide the maximum uptime to the Data Centre. 5.1.6 Security: The System Integrator must provide an end-to-end security model that protects data and the infrastructure from malicious attacks, theft, natural disasters etc. 5.1.7 Manageability: Easy of configuration, ongoing health monitoring, and failure detection are vital to the goals of scalability, availability, and security and must be able to match the growth of the environment. 5.1.8 Indoor Conditions: As per ASHARE (American Society of Heating, Refrigeration & Air-conditioning Engineers) Guidelines. 5.1.9 Blanking Panels: Supplier shall supply blanking panels to cover the vacant rack space. Technical Specifications Page 17
SECTION 2.0 DETAILED TECHNICAL SPECIFICATION AND COMPLIANCE MATRICES (I.T. AND DATA CENTRE INFRASTRUCTURE) CONTENTS SECTION - 2.1 SECTION - 2.2 SECTION - 2.3 SECTION - 2.4 SECTION - 2.5 SECTION - 2.6 SECTION - 2.7 SECTION - 2.8 SECTION - 2.9 SECTION - 2.10 SECTION - 2.11 SECTION - 2.12 SECTION - 2.13 SECTION - 2.14 SECTION - 2.15 TECHNICAL SPECIFICATION FOR BLADE CHASSIS TECHNICAL SPECIFICATION FOR SERVERS TECHNICAL SPECIFICATION FOR STORAGE TECHNICAL SPECIFICATION FOR TAPE LIBRARY / DRIVE TECHNICAL SPECIFICATION FOR TAPE CARTRIDGES TECHNICAL SPECIFICATION FOR NETWORK & SECURITY SETUP TECHNICAL SPECIFICATION FOR LOAD BALANCERS TECHNICAL SPECIFICATION FOR RACKS TECHNICAL SPECIFICATION FOR PASSIVE WORK TECHNICAL SPECIFICATION FOR SCANNER TECHNICAL SPECIFICATION FOR LINUX OS TECHNICAL SPECIFICATION FOR BACKUP SOFTWARE TECHNICAL SPECIFICATION FOR ENTERPRISE MANAGEMENT SYSTEM SOFTWARE TECHNICAL SPECIFICATION FOR VIRTUALIZATION SOFTWARE TECHNICAL SPECIFICATION FOR E-MAIL GATEWAY ANTI-SPAM & ANTIVIRUS SOFTWARE SECTION - 2.16 TECHNICAL SPECIFICATION FOR DATA CENTRE INFRASTRUCTURE (DELHI) SECTION - 2.17 SECTION - 2.18 TECHNICAL SPECIFICATION FOR SERVER ROOM (PALATANA) TECHNICAL SPECIFICATION FOR STATIC/SOURCE TRANSFER SWITCH (DELHI) SECTION - 2.19 TECHNICAL SPECIFICATION FOR FIRE PROOF MEDIA ENCLOSURE (DELHI) Technical Specifications Page 18
SECTION 2.1 TECHNICAL SPECIFICATION FOR BLADE CHASSIS 1.0 Blade Chassis Specification * Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 Form Factor 1.2 IO Modules 1.3 1.4 Ethernet IO Module Fibre Channel IO Module Max 10U Rack mounted Chassis to house at least 14 Compute Nodes. Blade chassis shall be 19 Electronic Industries Alliance standard width rack mountable and provide appropriate rack mount kit Min Four high-speed switch bays capable of supporting I/O architectures in Ethernet, Fiber Channel, FCoE and Infiniband 2 x 10gbps Ethernet switch with L2 capabilities, Vmready standards Should provide FC connectivity to all blade slots in chassis. 2 x 8 gbps FC switch and 8 Gbps SFP should be supplied along with the switch. Technical Specifications Page 19
1.5 Ethernet Module 1.6 Midplane 1.7 1.8 Power Modules Chassis Management Module The chassis should have redundant module for all fabric connectivity Chassis should have 2 hot-plug, redundant Ethernet modules with SFP ports. Should have minimum 4 numbers of active fibre uplink ports of 10Gbps and 4 numbers of active 1Gbps (copper) port each module Should have 10GB uplink from the Ethernet module which is connected to the blade chassis All Ethernet module should be VM aware. Chassis should have a highly reliable mid plane for providing connectivity of the shared resources to the compute nodes in a highly reliable manner. Redundant Platinum power modules to provide N+N or N+1 redundancy. Integrated two redundant chassis Management Modules providing IP based management of the compute nodes and vital elements like FC and Ethernet Switches. Should also provide for controlling Power, Fan management, Chassis and compute node initialization, Switch management, Resource discovery and inventory management, Resource alerts and Technical Specifications Page 20
1.9 Security 1.10 Drivers and Licenses 1.11 System Panel 1.12 Virtual DVD Support 1.13 KVM Functionality monitoring management, Chassis and compute node power management and diagnostics for elements including Chassis, I/O options and compute nodes. Should provide Secure Socket Layer (SSL) 128 bit encryption and Secure Shell (SSH) Version 2 and support VPN for secure access over internet Chassis supports both legacy-snmp and SNMPv3 interfaces. Appropriate number of licenses and drivers required for servers, networking and blade chassis LEDs on the front information panel that can be used to obtain the status of the chassis Identify, Check log and the Fault LED Should be able to support the feature of virtual DVD to individual servers from remote systems It should support remote KVM capability from an external keyboard, video monitor and mouse to all blades installed in the chassis through the management controllers. Simultaneous KVM access to a single blade KVM by multiple users but the admin user can take Read Write ownership while the other user in in read only mode Technical Specifications Page 21
1.14 1.15 Operating Temperature Range Should provide 5 years onsite comprehensive warranty & Hardware maintenance support. Chassis should support the operating temperature range between 5 C to 40 C * The blade chassis should be quoted based on optimum number of chassis requirement for the supplied number of blades. Technical Specifications Page 22
SECTION 2.2 TECHNICAL SPECIFICATION FOR SERVERS 1.0 Blade Servers for SAP ERP 1.1 IDES, Development, Quality, Solution Manager, SAP Router, Portal Servers Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1.1 Make and Model of the server 1.1.2 Form Factor Blade 1.1.3 1.1.4 1.1.5 Processor Type The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. Processors Should have minimum 2.6 GHz, 15MB L3 cache and should provide 9000. Should be 100% scalable Server RAM The server must be with the Minimum of 8 GB RAM per core, DDR3 RDIMM memory modules having same DIMM for all slots. If Vms are installed, the same can be increased Technical Specifications Page 23
1.1.6 1.1.7 1.1.8 1.1.9 1.1.10 1.1.11 1.1.12 1.1.13 1.1.14 1.1.15 Memory Protection HDD HDD Speed RAID Support for internal HDDs Ethernet Ethernet feature IO adapters FC ports OS Support and Virtualization DVD ROM as per the solution requirement. Blade should have minimum 24 DIMM slots. Advanced ECC (Chipkill/ Extended ECC/ Chipspare) with multi-bit error protection support 2 x 600GB 6G hot plug SFF SAS Internal HDD in RAID-1 15/10K RPM With Hardware or Software RAID-1 support 2 (Two) nos 10G Ethernet Ports with 4 nos vnic support per port. Should support and provide the NIC teaming / bonding All adapters should be PCI/X or PCI/E All FC ports for storage connectivity should be 8Gbps and should be provided in redundant config with multi pathing enabled. They should be provided with appropriate drivers and licenses The OS should be latest available version. The Operating systems (OS) should be 64-bit industry compliant LINUX (LINUX or Windows for Solution Manager and SAP Router) and should support both 32-bit and 64-bit applications. Should support Internal or External DVD-ROM for software Technical Specifications Page 24
1.1.16 1.1.17 1.1.18 1.1.19 Manageability Virtualization Support Should provide the facility and interfaces / cables for connecting Monitor, USB keyboard and USB mouse to the server No single point of failure for Fan Assembly and O.S. installation and patch management. Should support unified management suite that can monitor and manage all the servers 1.1.20 Power Supply with redundancy 1.1.21 1.1.22 1.1.23 1.1.24 1.1.25 Should provide LINUX OS (64- Bit Windows OS for SAP Router), licenses along with media Hardware should be compatible with SAP applications USB Ports Server should have 1 front and 2 internal USB 2.0 ports Predictive Failure Analysis Should provide 5 years onsite comprehensive warranty & Hardware maintenance Server should have feature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis Technical Specifications Page 25
support. 1.1.26 Number of Servers or partitions As per solution requirement 1.2 DB & CI and Application Instance Design Considerations and Servers 1.2.1 DB & CI Instance Specific Design Considerations 1.2.1.1 Design Considerations The DB & CI systems for each SAPS Production application module will run in a High Availability cluster on two different physical systems with adequate redundancy and with equal performance and configuration, and will have access to the same database and storage. The cluster solution must be able to provide fail-over to the other system for any failure arising due to: Hardware, Operating system, Database SAP processes in any of the two systems. Compliance (Y / N) for Design Considerations Details / Remarks / Deviations 1.2.1.2 1.2.1.3 The solution must be able to recover automatically (by restarting any stopped process automatically). In case of unrecoverable errors, the process on the failed system must be automatically restarted on the other system. This switch over should remain transparent to all the Application Servers and end-users and they should be able to continue working without re-logging into SAP. The fail over scenario mentioned in Serial number 2 item no 4, no committed transactions in SAP should be lost. Once the failed system comes up, there should be a scope of reverting back to the original configuration manually and automatically (both options) without disrupting the applications. Technical Specifications Page 26
1.2.1.4 Design Considerations An uptime of 99.5% is required for the entire solution for DB and CI. Compliance (Y / N) for Design Considerations Details / Remarks / Deviations 1.2.1.5 1.2.1.6 The database and CI servers should be configured such that there should be CPU and Memory headroom of minimum 50% allocable to any of the SAP application module (DB/CI) running on that server. System Integrator should propose the solution, with DB and CI consolidation for relevant applicable SAP modules. 1.2.2 Application Instance Specific 1.2.2.1 1.2.2.2 The total required SAPS for application servers have to be divided in to multiple servers or partitions to provide load balancing and redundancy. Each such server or partition should provide SAPS not less than 13500 If the System Integrator proposes a large server partitioned to provide the required number of Application servers, the following points are mandatory: Each partition should be able to run same or different versions of OS independently Any configuration change in one partition should not affect any other partition unless desired An error in one partition should not bring the entire system or other partitions down Each partition should be upgradeable separately and independently without affecting other partitions. 1.2.3 Other Considerations 1.2.3.1 The SAPS mentioned in hardware sizing are purely required for the SAP applications. System Integrator need propose the system considering Technical Specifications Page 27
Design Considerations additional SAPS due to OS and Virtualization overheads. The RAM mentioned in hardware sizing is purely minimum required for the SAP applications. System 1.2.3.2 Integrator need propose the system considering additional RAM for performance, OS and Virtualization overheads. The offered machine must be certified 1.2.3.3 for SAP Usage for 64-bit OS kernel. 1.2.3.4 OS should include Kerberos System Integrator needs to provide the published benchmark or OEM letter mentioning the SAPS rating 1.2.3.5 supported by the Server. The offer without competency center certificate shall not be accepted. Compliance (Y / N) for Design Considerations Details / Remarks / Deviations 1.3 Reliability, Availability and Serviceability (RAS) features required for SAP DB, CI and Application Servers RAS features described here shall be supported both by Hardware and Operating System 1.3.1 Reliability, Availability and Serviceability (RAS) RAS Type Processor RAS Advanced RAS required 1.3.2 ECC Cache 1.3.3 Memory Address Parity 1.3.4 Resilient QPI Links 1.3.5 Redundant processor to I/O hub links 1.3.6 Machine Check Architecture (MCA) QPI RAS 1.3.7 QPI protocol CRC protection 1.3.8 QPI self-healing 1.3.9 QPI clock failover 1.3.10 QPI packet retry Memory RAS 1.3.11 Chipkill /Extended ECC/ Chipspare 1.3.12 Redundant Bit Steering 1.3.13 Memory Scrubbing Compliance (Y / N) for RAS Specifications Details / Remarks Technical Specifications Page 28
Reliability, Availability and Serviceability (RAS) 1.3.14 Memory mirroring 1.3.15 Memory DIMM sparing 1.3.16 Memory Rank Sparing SMI RAS 1.3.17 SMI Protocol CRC Protection 1.3.18 SMI Lane failover 1.3.19 SMI Clock failover 1.3.20 SMI Packet retry System-wide RAS features 1.3.21 Hot-swap components (HDDs, Power supplies, fans etc.) 1.3.22 Integrated Management Module 1.3.23 Predictive Failure Analysis 1.3.24 Light Path Diagnostics 1.3.25 Dynamic System Analysis Compliance (Y / N) for RAS Specifications Details / Remarks 1.4 Blade Servers for SAP Application Instance Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specification s Proposed Capacity / Hardware ( Bidder can propose technically superior components ) Details / Remarks 1.4.1 Make and Model of Server 1.4.2 Form Factor Blade 1.4.3 Processor Type The Server should be based on Intel E7 based x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. Technical Specifications Page 29
1.4.4 1.4.5 1.4.6 1.4.7 1.4.8 1.4.9 1.4.10 1.4.11 1.4.12 Processors Server RAM Memory Protection HDD HDD Speed RAID Support for internal HDDs Ethernet Ethernet feature OS Support and Clustering Support Should have minimum 2.0 GHz, 16 MB L3 cache and should provide minimum 13500 SAPS to application instance. Should be 100% scalable The server must be with the Minimum of 8 GB RAM per core, DDR3 RDIMM memory modules having same DIMM for all slots. If Vms are installed, the same can be increased as per the solution requirement. Blade should have minimum 24 DIMM slots. Advanced ECC (Chipkill/ Extended ECC/ Chipspare), with multi-bit error protection support 2 x 600GB 6G hot plug SFF SAS Internal HDD 15/10 K RPM With Hardware or Software RAID-1 2 (Two) Ethernet Controllers each with 2 X 10G Ethernet ports with 4 Nos vnic support per port. Should support and provide the NIC teaming / bonding RHEL, SLES, VMware, Citrix XenServer, RHEV, MS-Hyper-V. The OS should be latest available version. The Operating systems (OS) should be 64-bit industry compliant LINUX and should support both 32-bit and 64-bit Technical Specifications Page 30
1.4.13 1.4.14 1.4.15 1.4.16 DVD ROM Manageability Should provide the facility and interfaces / cables for connecting Monitor, USB keyboard and USB mouse to the server No single point of failure for Fan Assembly applications. Should support Internal or External DVD-ROM for software and O.S. installation and patch management. Should support unified management suite that can monitor and manage all the servers on chassis level 1.4.17 1.4.18 Power Supply with redundancy Should provide LINUX OS, licenses along with media on chassis level 1.4.19 1.4.20 1.4.21 1.4.22 Hardware should be compatible with SAP applications Application instances should be running on separate physical servers to avoid single point of failure USB Ports Predictive Failure Analysis Offered server should have 1 front and 2 internal USB 2.0 ports Offered Server should have feature of Predictive Failure Analysis on Processors, memory, drives, in servers fans Technical Specifications Page 31
and power supplies in the chassis 1.4.23 1.4.24 Should provide 5 years onsite comprehensive warranty & Hardware maintenance support. Number of Servers or partitions As per solution requirement 1.5 Blade Servers for DB CI Instance Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specification s Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks 1.5.1 Make and Model of the servers 1.5.2 Form Factor Blade 1.5.3 The nodes of the cluster should be of same make and model 1.5.4 With reference to SAP Hardware Sizing System Integrator must ensure that required SAPS are allocated to SAP application module. At any point in time resource partitions should not run Technical Specifications Page 32
with less resources. 1.5.5 The failover partition should be capable of providing same SAPS in the event of failover 1.5.6 Each SAP instance in production system should be running in independent partitions 1.5.7 The partitions should have their own operating systems. 1.5.8 The DB and CI systems should be clustered with HA clustering technology and there should be no single point of failure in the system 1.5.9 All servers should have same x86-64 processors 1.5.10 Systems should have redundant fans 1.5.11 The systems should be provided with redundant power supplies 1.5.12 All the components including disks, power supplies, fans should be hot pluggable at chassis level at chassis level 1.5.13 Processor Type The Server should be based Intel E7 on x86-64-bit architecture to support minimum 2 processors that is latest in respective product line & server should have the Technical Specifications Page 33
capability of supporting 32-bit applications as well. 1.5.14 Processors Should have minimum 2.0 GHz, 16 MB L3 cache and should provide minimum 12500 SAPS to application instance. 1.5.15 Number of Processors 1.5.16 Processor Scalability 1.5.17 Minimum SAPS allocated for each SAP application module must be offered as per mandatory requirement in the hardware sizing, Integrator need to put appropriate buffer considering OS and other overheads. 1.5.18 Minimum Memory in each SAP application module must be offered as per mandatory requirement in the hardware sizing, Integrator need to put appropriate buffer considering OS and other overheads. As per SAPS requirement of the SAP application modules Processor should be scalable to provide 100% scalability 1.5.19 Server RAM The server must be with the Minimum of 8 GB RAM per core, DDR3 RDIMM memory modules having same DIMM for all slots. If Vms are installed, the same can be increased as per the solution requirement. Blade Technical Specifications Page 34
should have minimum 24 DIMM slots 1.5.20 Memory Protection Advanced ECC (Chipkill/ Extended ECC/ Chipspare) with multi-bit error protection support 1.5.21 Partitions Each SAP instance should run in independent virtual partitions with dedicated resources CPU/memory/IO and independent operating system 1.5.22 Any software error in one partition should not affect the other partition 1.5.23 OS in each partition should be upgradeable, without impacting the other 1.5.24 Each partition should have capability to start and shutdown independently of the other 1.5.25 Any configuration change in one partition should not impact other partition. 1.5.26 IO adapters All adapters should be PCI/X or PCI/E 1.5.27 FC ports All FC ports for storage connectivity should be 8Gbps and should be provided in redundant config with multi pathing enabled. They should be provided with appropriate drivers and licenses 1.5.28 Ethernet Adapter 2 (two) Ethernet Controller with 2 x 10G ports, The controllers should support 4 nos vnic Technical Specifications Page 35
per port. 1.5.29 All Ethernet adapters should be redundant, 10/100/1000 autosensing, should be provided with automatic failover or with link aggregation for each partition. Relevant software and licenses should be also provided 1.5.30 Internal Disks 2 x 600GB 6G hot plug SFF SAS Internal HDD in RAID-1 1.5.31 HDD Speed 15/10 K RPM 1.5.32 The OS should be mirrored for all partitions 1.5.33 Operating system Latest OS version of 64 bit Linux operating system with latest patch level. 1.5.34 OS should be capable of running 64bit SAP and 64bit Oracle database. 1.5.35 All software licenses should be provided that are offered for the solution 1.5.36 Cluster and high availability 1.5.37 Redundant heart beat paths to be provided. Paths should be physically isolated 1.5.38 Cluster solution should be OEM or SAP certified solution The systems should be made highly available using OS clustering solutions Technical Specifications Page 36
1.5.39 DVD ROM Each partition should be capable to have online access to internal/external DVD. 1.5.40 USB Ports Server should have 1 front and 2 internal USB 2.0 ports 1.5.41 Predictive Failure Analysis 1.5.42 Should provide 5 years onsite comprehensive warranty & Hardware maintenance support. Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Server should have feature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 1.5.43 Number of Servers As per solution requirement 2.0 Blade Servers for Backup Software Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks 2.1 Make and Model 2.2 Form Factor Blade 2.3 2.4 2.5 2.6 Processor Number of Processor Processor Upgrade Server RAM System Integrator to propose System Integrator to propose Upgradeable to provide 50% scalability for future expansion in storage System Integrator to propose Technical Specifications Page 37
2.7 Server RAM expansion capacity 2.8 2.9 Internal HDDs HDD Speed 2.10 Internal Storage Controller 2.11 2.12 2.13 2.14 2.15 2.16 Ethernet Ethernet feature IO Adaptors FC Ports Support for DVD- ROM (Internal/External) Redundant Power Supply Upgradeable to provide 50% scalability 2 x 600GB 6G hot plug SFF SAS Internal HDD or SAN boot in RAID-1 (additional storage capacity needs to be factored for the same) 15/10 K RPM With Hardware / software RAID-0,1 support 2 (Two) nos. 10G Ethernet Ports with 4 nos vnic support per port. Should support and provide the NIC teaming / bonding. All adapters should be PCI/X or PCI/E All FC ports for storage connectivity should be 8Gbps and should be provided in redundant config with multi pathing enabled. They should be provided with appropriate drivers and licenses 2.17 2.18 2.19 No single point of failure for Fan Assembly Operating System System Integrator needs to supply the operating system media and requisite license for the System Integrator needs to provide details Technical Specifications Page 38
environment. 2.20 2.21 2.22 2.23 USB Ports Server should have 1 front and 2 internal USB 2.0 ports Predictive Failure Analysis Should provide 5 years onsite comprehensive warranty and hardware maintenance support Number of Servers / Partitions Server should have feature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis As per solution requirement 3.0 Blade Servers for EMS (Enterprise Management System) Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks 3.1 Make and Model 3.2 Form Factor Blade 3.3 Processor Type The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. Technical Specifications Page 39
3.4 3.5 3.6 3.7 3.8 3.9 Processor Number Of Processor Processor Upgrade Server RAM Memory protection Server RAM expansion capacity As per solution requirement As per solution requirement Upgradeable to provide 50% scalability for future expansion As per solution requirement Advanced ECC with multi-bit error protection support Upgradeable to provide 100% scalability for future expansion 3.10 Internal HDDs 2 x 600GB 6G hot plug SFF SAS with RAID-1 3.11 HDD Speed 10K RPM 3.12 3.13 Internal Storage Controller For any additional hard-disk requirement as per the solution, System Integrator needs to propose the additional storage space on SAN. With Hardware/Software RAID-0,1 support 3.14 3.15 3.16 Ethernet Ethernet feature Support for DVD- ROM (Internal/External) 2(Two) nos. 10GB Ethernet ports, with 4 nos vnic support per port Should support and provide the NIC teaming / bonding. Technical Specifications Page 40
3.17 Redundant Power Supply 3.18 No single point of failure for Fan Assembly 3.19 Redundant Power Supply 3.20 Operating System As per the solution 3.21 Virtualization Support System Integrator needs to supply the operating 3.22 system media and license including virtualization licenses. USB Ports Server should have 1 3.23 front and 2 internal USB 2.0 ports Predictive Failure Analysis Server should have feature of Predictive Failure Analysis on 3.24 Processors, memory, drives, in servers fans and power supplies in the chassis Should provide 5 years onsite 3.25 comprehensive warranty and maintenance support 3.26 Number of Servers / Partitions As per requirement Technical Specifications Page 41
4.0 Blade Servers for Infrastructure Setup (Domain Controller, DNS, DHCP, NTP, Windows Update Service, Antivirus) - Delhi Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 4.1 Make and Model 4.2 Form Factor Blade 4.3 Processor Type The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. 4.4 Processor 2 * 12 Core, Should have minimum 2.7 GHz, 30MB L3 Cache 4.5 Number of Processor Two 16GB with Advanced 4.6 Error checking and Server RAM correcting (ECC) Upgradeable to 4.7 Server RAM provide 100% expansion scalability for future capacity expansion 2 x 600GB 6G hot plug 4.8 SFF Internal HDD in Internal HDDs RAID-1 4.9 HDD Speed 15/10 K RPM 4.10 Internal Storage With Hardware RAID- Controller 0,1 support 2 (Two) nos. 10G 4.11 Ethernet ports, with 4 nos vnic support per Ethernet port Technical Specifications Page 42
4.12 4.13 4.14 Ethernet feature DVD-ROM (Internal / External) Redundant Power Supply Should support and provide the NIC teaming / bonding. on chassis level 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 No single point of failure for Fan Assembly Operating System windows 2012 on chassis level System Integrator needs to propose standard /enterprise edition and 32/64 bits as per requirement. The virtualization should be offered with management component to manage virtual machines Virtualization Support System Integrator need to supply windows 2012 OS with downgrade rights. System Integrator needs to supply the operating system media and license including virtualization licenses. USB Ports Server should have 1 front and 2 internal USB 2.0 ports Predictive Failure Analysis Should provide 5 years onsite comprehensive warranty and maintenance support Server should have feature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis Technical Specifications Page 43
4.23 4.24 Domain Controller role should be running on separate physical servers in virtualized environment to avoid single point of failure Number of Servers / Virtual partitions 5 Nos 5.0 Blade Servers for Anti-Spam & E-Mail Gateway Antivirus Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( System Integrator can propose technically superior components) Details / Remarks 5.1 Make and Model 5.2 Form Factor Blade 5.3 Processor Type The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. 5.4 Processor 2 * 12 Core, Should have minimum 2.7 GHz, 30MB L3 Cache 5.5 Number of Processor Two 5.6 Server RAM 16GB with Advanced Error checking and correcting (ECC) Upgradeable to 5.7 provide 100% Server RAM scalability for future expansion capacity expansion 2 x 600GB 6G hot plug 5.8 SFF Internal HDD or Internal HDDs SAN boot in RAID-1 Technical Specifications Page 44
5.9 HDD Speed 15/10 K RPM Internal Storage With Hardware RAID- 5.10 Controller 0,1 support 2(Two) nos. 10G Ethernet ports, with 4 5.11 nos vnic support per Ethernet port Should support and 5.12 provide the NIC Ethernet feature teaming / bonding. DVD-ROM 5.13 (Internal / External) 5.14 Redundant Power Supply No single point of 5.15 failure for Fan Assembly 5.16 5.17 5.18 5.19 5.20 5.21 5.22 Operating System Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE at chassis level at chassis level System Integrator to propose the OS as per solution requirements. Virtualization Support System Integrator needs to supply the operating system media and license including virtualization licenses. USB Ports Server should have 1 front and 2 internal USB 2.0 ports Predictive Failure Server should have Analysis feature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis Should provide 5 years onsite comprehensive warranty and maintenance support Email anti-spam and antivirus serer should be running on separate physical servers in Technical Specifications Page 45
5.23 virtualized as well as non-virtualized environment to avoid single point of failure Number of Servers / Virtual partitions 2 Nos 6.0 Blade Servers for E-Mail Upgrade (Microsoft Exchange, E-Mail Migration and Setup) Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( System Integrator can propose technically superior components) Details / Remarks 6.1 Make and Model 6.2 Form Factor Blade 6.3 Processor Type The processor should be based on x86-64- bit architecture that is latest in respective product line and Shall support 32-bit applications 6.4 Processor 2 * 12 Core, Should have minimum 2.7 GHz, 30MB L3 Cache 6.5 Number of Processor Two 16 GB with Error 6.6 checking and Server RAM correcting (ECC) Upgradeable to 6.7 Server RAM provide 100% expansion scalability for future capacity expansion 6.8 2 x 600GB 6G hot plug Internal HDDs SAS in RAID-1 6.9 HDD Speed 15/10 K RPM 6.10 Internal Storage With Hardware RAID- Controller 0,1 support 6.11 Ethernet 2 (two) x 10 Gigabit Technical Specifications Page 46
Ethernet Ports with 4 nos. vnic support per port Should support and 6.12 provide the NIC Ethernet feature teaming / bonding. 6.13 I/O Sots Minimum two I/O slots 6.14 HBA Port 2 port HBA for connecting to the SAN Switch 6.15 DVD-ROM (Internal / External) 6.16 Redundant Power Supply No single point of 6.17 failure for Fan Assembly USB Ports Server should have 1 6.18 front and 2 internal USB 2.0 ports 6.19 Predictive Failure Analysis Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Server should have feature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 6.20 6.21 6.22 6.23 Operating System Windows Server 2012 System Integrator needs to supply the operating system media and license. System Integrator to supply Exchange 2013 Media, User CALs, SSL Digital Certificates (Four SAN names) Should provide 5 years onsite comprehensive warranty and maintenance support Technical Specifications Page 47
6.24 Number of Servers / Virtual Partition 4 Nos 7.0 Rack Servers for Domain Controller, DNS, DHCP, Windows Update Service and Antivirus Palatana, Tripura Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( System Integrator can propose technically superior components) Details / Remarks 7.1 Make and Model 7.2 Form Factor Rack 7.3 Processor Type The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. 7.4 Processor 2 * 6 Core, Should have minimum 2.0 GHz, 15MB L3 Cache 7.5 Number of Processor Two Upgradeable to 7.6 provide 100% Processor scalability for future Upgrade expansion 48GB with Advanced 7.7 Error checking and Server RAM correcting (ECC) 7.8 7.9 Server RAM expansion capacity Internal HDDs Upgradeable to provide 100% scalability for future expansion 6 x 600GB 6G hot plug SFF Internal HDD 7.10 HDD Speed 15/10 K RPM 7.11 Internal Storage With Hardware RAID- Technical Specifications Page 48
7.12 7.13 7.14 7.15 7.16 7.17 7.18 7.19 7.20 7.21 7.22 Controller Ethernet Ethernet feature DVD-ROM (Internal / External) Redundant Power Supply No single point of failure for Fan Assembly Operating System windows 2012 Virtualization Support System Integrator need to supply windows 2012 OS with downgrade rights. System Integrator needs to supply the operating system media and license including virtualization licenses. Should provide 5 years onsite comprehensive warranty and maintenance support Number of Servers / Virtual partitions 0,1,5 support Four Gigabit Ethernet Ports Should support and provide the NIC teaming / bonding. System Integrator needs to propose standard /enterprise edition and 32/64 bits as per requirement. 3 Nos Technical Specifications Page 49
SECTION 2.3 TECHNICAL SPECIFICATION FOR STORAGE 1.0 STORAGE AREA NETWORK (SAN) DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks Make and Model 1.1 1.2 1.3 1.4 1.5 System Integrator need to propose the number of disks for total no of IOPS as per SAPS (minimum 50% of the total SAPS excluding HA) For SAP production servers System Integrator need to provide 600 GB, 15/10 K RPM, 6Gbps SAS HDD The usable capacity for the production storage should not be less than 5 TB with RAID 1+0 and 1 TB raw SSD in RAID 5 Storage for IDES, Development & Quality Systems, Solution Manager, SAP Router Staging / disk cloning, SAP DVDs & reserve 8 TB usable disk space With RAID-5, SAS Disks System Integrator need to provide the number of disks for production storage Technical Specifications Page 50
1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 space Usable Storage for Desktop Users should not be less than 2 TB (NL-SAS Disks) in RAID 6 Highly available NAS Gateways based on Windows storage server 2012 platform for use with different applications and users roaming profiles NAS gateways should be integrated with AD Disk Speed for IDES, development & Quality, Staging/Disk Cloning & reserve, Desktop Users Disk Speed for SAP production and E- Mail Servers Disk Drive Support Cache (Memory) Storage array shall have either Cache Duplexing, Disk destaging or battery backup support to avoid any kind of data loss. Storage Expansion Hot Spare Disks RAID support for storage controllers 10K RPM 15 / 10 K RPM 300/450/900 GB hotpluggable enterprise SAS HDD, 100/200/400 GB SSD and 1/2/3 TB NL- SAS HDD System Integrator need to provide minimum 16GB cache memory to meet the performance. 50% scalability for future expansion Minimum 1 hot spare per 10 disks are required of each type Storage Array shall support standard Raid 0,1, 0+1/1+0, 5 Technical Specifications Page 51
1.17 1.18 1.19 1.20 Storage shall be offered with required licenses. Storage should have a facility of create snapshots/ pointing copies/ flash copies/ Automatic Tiering of Data. The storage array should be based on FC front-end and SAS backend with dual redundant controllers There shall be no single point of failure into the array system including Power Supplies, Cache, Cache boards, Front-end Boards, Backend Boards Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE and Raid 6 other various RAID concepts As per requirement of RFP with 10% buffer. Irrespective of OS. 1.21 Host Ports 4 Nos. per controller 1.22 Back-end Ports 4 Nos. per controller 1.23 1.24 1.25 Ports Bandwidth Load Balancing & Multi-path Operating System Support 8Gbps or higher on host port Should support Multipath and load balancing. System Integrator need to provide required software The storage array should support industry-leading Operating System platforms including: various versions of Microsoft Windows, Sun Solaris, HP-UX, IBM-AIX, and Linux. Technical Specifications Page 52
1.26 Storage Shall support all above operating systems in Clustering. 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 The Storage system should support online replacement of failed disks without interruption or rebooting the array Power Supply FAN Offered storage shall support online nondisruptive firmware upgrade for both Controller The storage system should support automatic detection of errors, error logging and notification. The storage system should support hardware based data replication to a remote sites in two geographical locations Storage Management System Integrator should provide dualcontroller arrays to avoid a single point Should provide hot plug redundant power supplies Hot-plug redundant FAN System Integrator to provide the storage management software and appropriate licenses. It should have the flexibility to allow the users to set up, enable and delete volumes Technical Specifications Page 53
1.35 1.36 of failure. Controller should be activeactive Should provide 5 years onsite comprehensive warranty and maintenance support No of SAN Storage required 1 No. 2.0 NETWORK ATTACHED STORAGE (NAS) PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 2.1 Make and Model 2.2 LDAP (Active Directory Services) Integration Functionality 2.3 The usable capacity for the storage should not be less than 3 TB with RAID - 6 2.4 Cache (Memory) System Integrator needs to provide appropriate cache memory to meet the performance 2.5 Storage Expansion 100% scalability for future expansion 2.6 Hot Spare Disks Appropriate number of disks to be provided. Technical Specifications Page 54
2.7 RAID support for storage controllers 2.8 There shall be no single point of failure into the system including Power Supplies, Cache, Cache boards, Front-end Boards, Backend Boards Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Storage Array shall support standard Raid 0,1, 0+1/1+0, 5 and Raid 6 other various RAID concepts 2.9 Ports As per solution requirement 2.10 Disk Types Support SAS, NL SAS 2.11 Protocols Supported CIFS, NFS 2.12 Operating System Support 2.13 The Storage system should support online replacement of failed disks without interruption or rebooting The storage array should support Microsoft Windows Platform. The storage shall be based on Windows Storage Server. (Primarily the storage will be used for storing OTPC users official data) 2.14 Power Supply Should provide hot plug redundant power supplies 2.15 FAN Hot-plug redundant FAN 2.16 The storage system should support automatic detection of errors, error logging and notification. 2.17 Storage Management System Integrator to provide the storage management Technical Specifications Page 55
2.18 Should provide 5 years onsite comprehensive warranty and maintenance support 2.19 No of Storage 1 No software and appropriate licenses. It should have the flexibility to allow the users to set up, enable and delete volumes Technical Specifications Page 56
SECTION 2.4 TECHNICAL SPECIFICATION FOR TAPE LIBRARY / DRIVE 1.0 LTO-6 TAPE LIBRARY DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 Make and Model 1.2 1.3 1.4 1.5 Modular Architecture to allow configuration, add capacity and increase performance as per requirement. Should have feature for accurate identification of barcoded cartridges which is important for unattended and automated backup application Calibration Capacity Should be able to do automatic calibration and therefore shall not require downtime for periodic alignment Minimum 2 (two) LTO6 FC Half Height tape drive Technical Specifications Page 57
1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 Tape Drive Scalability Scalable to 100% of the quantity offered by the System Integrator Tape Drive Speed LTO6 drive shall support 160MB/sec in Native mode and 400MB/sec in 2.5:1 Compressed mode Connectivity Tape drive shall provide FC native connectivity. Cartridge Slots Tape Library shall be offered with Minimum of 24 slots Tape Library shall have GUI Panel. Tape drive shall provide web based remote management Tape drive shall support Barcode reader Tape drive shall be supplied with software which can predict and prevent failures through early warning and shall suggest the required service action Shall be rack mountable. Shall provide Redundant Power supply Rack Mount Accessories Should provide 5 years onsite comprehensive warranty and maintenance support Number of Tape 1 Nos Library Technical Specifications Page 58
2.0 LTO-6 TAPE DRIVE PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 2.1 Make and Model Form Factor 1U Rack 2.2 Mountable 2.3 Drive Single 2.4 Architecture LTO 6 2.5 2.6 2.7 Backup Software Should provide 5 years onsite comprehensive warranty and maintenance support with rack mount accessories No of Tape Drive 1 (Data that required be backed up is of OTPC users) Technical Specifications Page 59
SECTION 2.5 TECHNICAL SPECIFICATION FOR TAPE CARTRIDGES 1.0 LTO-6 TAPE CARTRIDGES DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 1.2 1.3 1.4 1.5 LTO Generation 6 Rewritable Tape Media Should be capable of taking 2.5/6.25 TB data backup Should be compatible with Tape drive. Number of Tape Cartridge (With Bar Codes) Number of Cleaning Cartridges (With Bar Codes) 150 No, 20 No. 2.0 LTO-6 TAPE CARTRIDGES PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance Proposed Capacity / Details / Remarks Technical Specifications Page 60
(Y / N) for minimum specifications Hardware ( Bidder can propose technically superior components) 2.1 2.2 2.3 2.4 2.5 LTO Generation 6 Rewritable Tape Media Should be capable of taking 2.5/6.25 TB data backup Should be compatible with Tape drive. Number of Tape Cartridge Number of Cleaning Cartridges 30 No, 5 No. Technical Specifications Page 61
SECTION 2.6 TECHNICAL SPECIFICATION FOR NETWORK AND SECURITY SETUP 1.0 SAN SWITCH DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks Make and Model 1.1 1.2 1.3 1.4 1.5 1.6 1.7 Ports Port Type SAN Switches shall be offered with a No single point of failure configuration Port Bandwidth Aggregate Bandwidth Hot code activation 24 ports SAN Switch with at least 8 ports enabled as per RFP requirement. Should be compatible with HBA interface and interface of SAN as per solution. Offered SAN switch shall have 8Gbps ports and shall be backward compatible. 192 Gbps: 24 ports X 8 Gbps (data rate) end to end Offered SAN Switch shall support non- Bidder should access the actual requirement Technical Specifications Page 62
1.8 1.9 1.10 1.11 Management The SAN switch should have capability to interface with Host Bus Adapters (HBA) of different makes and models from multiple OEM, supporting multiple Operating System, including, but not limited to, HP-UX, IBM AIX, IBM Z/OS, Linux, Microsoft Windows, SUN Solaris, etc. Upgradability Power Supply Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE disruptive hot code activation feature. Offered SAN switch shall be manageable through Web, IP, CLI and SNMP. SAN Switch should support OS & Firmware or any software upgrade Redundant power supply 1.12 FANs Redundant FANs With two SAN switches in 1.13 redundant mode, it should provide high availability with redundant path Shall support trucking / 1.14 cascading when adding multiple switches in the same fabric Shall support 1.15 Zoning (Hardware & software) 1.16 QoS Support Support for 1.17 Bandwidth consumption traffic in real time 1.18 Diagnostics Support RASTrace Logging, Technical Specifications Page 63
1.19 1.20 1.21 The SAN switch should support all leading SAN disk arrays and tape libraries Should provide 5 years onsite comprehensive warranty and maintenance support Number of SAN Switches environmental monitoring, nondisruptive daemon restart, FCPing, FC Trace route, port mirroring 2 Nos. 2.0 SAN SWITCH TO STORAGE CABLES AND SAN SWITCH TO SERVERS CABLES DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 2.1 2.2 2.3 Length of the Cable Interface Number of Cables System Integrator need to propose Should be compatible with the SAN peripherals, serves and SAN switch interfaces System Integrator need to supply the quantity as per the solution with 25% buffer Technical Specifications Page 64
3.0 NETWORK AND SECURITY SETUP SPECIFICATIONS 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 Design Considerations System Integrator should provide Network Services for all the components, procured through this RFP, involved in application access and support at OTPC Data Centre and for OTPC LAN All network switches and Routers should be from the same OEM considering ease of manageability. Core Switches should be Chassis based / Stackable with redundant Power supply The solution should offer redundancy with no single point of failure for Aggregation Switches and Core Switches. Failure on any one Core Switch should not affect the availability of servers connection to end users. All network equipments (switches) should cater to the current requirements with 100% head room for future expansion through stacking One set of appliance based firewalls in redundant failover mode to be provisioned at Internet perimeter and Militarized zone Since the network security is an important aspect for OTPC IT landscape, Switches and Firewalls should be from different OEMs to ensure that they are not compromised at the same time All active network devices in the Data Centre under the scope of this RFP to be connected in dual homed fashion to provide redundancy All active network devices in the Data Centre under the scope of this RFP should be appliance based and rack mountable. Compliance (Y / N) for Design Considerations Details / Remarks Technical Specifications Page 65
Compliance (Y / N) for Design Considerations Design Considerations 3.10 Design Consideration specific to External Firewall The firewall shall identify applications across all ports, irrespective of protocol, encryption 3.10.1 (SSL or SSH), or evasive tactic. The application identity becomes the basis for all security policies The firewall shall identify users and not simply IP addresses. It should employ user and group information from enterprise directories for 3.10.2 visibility, policy creation, reporting and forensic investigation, regardless of user location or device type Inspect the content to protect network against known and 3.10.3 unknown threats including vulnerability exploits and malware embedded in application traffic Securely enable applications with 3.10.4 easy-to-use graphical tools that tie them together in a unified policy Combine purpose-built hardware and software to enable low-latency, 3.10.5 multi-gigabit performance with all services enabled Details / Remarks 3.1 CORE SWITCH - DELHI Feature / Specifications Minimum Specification Complianc e (Y / N) for minimum specificati ons Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks 3.1.1 Make 3.1.2 Model 3.1.3 10/100/1000Mbps Ethernet single line card / module / blade System Integrator need to propose ports as per the solution Technical Specifications Page 66
3.1.4 10 Gbps SFP+ Ports with cables Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE System Integrator need to propose ports as per the solution with 20% buffer 3.1.5 Port scalability Switch should have capability to scale min 100% of the capacity for future expansion. 3.1.6 Should be Chassis based / Stackable solution which should support minimum 4 slots/switches. 3.1.7 Should be with the latest stable software version with all updates, patches and fix ups installed 3.1.8 Should support SNMP v3 for monitoring and should be manageable using web interface 3.1.9 Virtual Switching System / Stacking with single IP Management 3.1.10 Static and Dynamic routing ( RIP v2, OSPF, RIPnG, OSPFv3, PIM, MLD etc.) protocol from day 1 3.1.11 Should provide nonblocking architecture 3.1.12 Should support basic QoS feature 3.1.13 Rack mountable, modular (slot base) / stackable architecture 3.1.14 Should provide rack mounting kit 3.1.15 Should have Internal Redundant Power Supply 3.1.16 Standard Protocols IPv6, SNMP, NTP, DCBX, DHCP etc. 3.1.17 Should provide 5 years onsite comprehensive warranty and maintenance support 3.1.18 Number of Switches 2 Nos. Technical Specifications Page 67
3.1.19 Backplane speed (IPv6) 600 Gbps 3.1.20 Throughput (IPv6) 446 Mpps 3.1.21 Certificate EAL3 Certified 3.2 DMZ SWITCH DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 3.2.1 Make and Model 3.2.2 Port Speed 10/100/1000 3.2.3 Number of UTP 24 No.s Ports/switch 3.2.4 Switch fabric speed 48 Gbps 3.2.5 Forwarding rate based on 35 Mpps 64-byte packets 3.2.6 VLANs per switch 512 3.2.7 Switch should have basic routing capabilities like static routing and RIP from day 1, upgradable to OSPF and PIM in future 3.2.8 Should be with the latest stable software version with all updates, patches and fix ups installed 3.2.9 Should support SNMP v3 for monitoring and should be manageable using web interface 3.2.10 Should support QoS 3.2.11 Should be a Layer-3 switch 3.2.11 Should provide 5 years onsite comprehensive warranty and maintenance support 3.2.12 Number of Devices 2 Nos. Technical Specifications Page 68
3.2.13 Certificate EAL3 Certified Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.3 AGGREGATION SWITCH DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specification s Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks 3.3.1 Make and Model 3.3.2 Port Speed 10/100/1000 3.3.3 Number of UTP 24 No.s Ports/switch 3.3.4 10 Gbps SFP+ Ports with cables 2 MMF SR ports 3.3.5 Should provide stacking feature from day 1 with minimum 9 switches in a stack or System Integrator can propose chassis based switch 3.3.6 Should be a Layer-3 Switch having static routing, RIP, RIPnG, OSPF, OSPFv3, PIM,MLD from day1 3.3.7 Switch fabric speed 88 Gbps 3.3.8 Forwarding rate based on 65 Mpps 64-byte packets 3.3.9 VLANs per switch 1000 3.3.10 Should provide nonblocking architecture 3.3.11 Should support basic QoS feature 3.3.12 Should be with the latest stable software version with all updates, patches and fix ups installed 3.3.13 Should support SNMP v3 for monitoring and should be manageable using web interface Technical Specifications Page 69
3.3.14 Should have Internal redundant power supply 3.3.15 Should provide 5 years onsite comprehensive warranty and maintenance support 3.3.16 Number of Switches 2 No s 3.3.17 Certificate EAL3 Certified Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.4 WAN (WIDE AREA NETWORK) SWITCH DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specification s Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks 3.4.1 Make and Model 3.4.2 Port Speed 10/100/1000 3.4.3 Number of UTP Ports/switch 3.4.4 Uplink fiber ports 1000BaseX SFP and 10/100/1000BaseT SFP (should support single and multi-mode fiber) 3.4.5 Port Scalability for fiber ports 24 No.s 2 Nos. of SFP Ports 100% scalability for future expansion 3.4.6 Switch fabric speed 52Gbps 3.4.7 Forwarding rate based on 38Mpps 64-byte packets 3.4.8 VLANs per switch 512 3.4.9 Should be with the latest stable software version with all updates, patches and fix ups installed 3.4.10 Switch should have static routing and RIP from day 1, upgradable to OSPF and PIM in future Technical Specifications Page 70
3.4.11 Should support SNMP v3 for monitoring and should be manageable using web interface 3.4.12 Should be a Layer -3 Switch 3.4.13 Should provide 5 years onsite comprehensive warranty and maintenance support 3.4.14 Number of Devices 2 No s 3.4.15 Certificate EAL3 Certified Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.5 48 PORT LAN SWITCH DELHI 1. OTPC Delhi LAN switches Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 3.5.1 Make and Model 3.5.2 Ethernet ports 48 No. (10/100/1000Mbps) 3.5.3 Uplink fiber ports 1000BaseX SFP and 2 MMF (SX) 10/100/1000BaseT SFP 1G Per Switch (should support single and multi-mode fiber) 3.5.4 Gigabit fiber port should support SFPs 3.5.5 512 VLANs or higher 3.5.6 Switch fabric speed 3.5.7 Packet Throughput based on 64byte packet size 100 Gbps or more 74Mpps or more 3.5.8 PoE on all ports 3.5.9 Rack mountable 3.5.10 Switch should support Technical Specifications Page 71
stacking 3.5.11 Switch should have static routing and RIP from day 1, upgradable to OSPF and PIM in future 3.5.12 Number of Switches 2 No. 3.5.13 Should provide 5 years onsite comprehensive warranty and maintenance support 3.5.14 Certificate EAL3 Certified Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.6 CORE SWITCH PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 3.6.1 Make and Model 3.6.2 3.6.3 3.6.4 3.6.5 Ethernet ports (10/100/1000Mbps) Fibre Ports (1000 Base X ports) Gigabit fiber port should support SFPs Stackable or Chassis based solution 3.6.6 Port Scalability 24 No. 24 No. 100% scalability for future expansion 3.6.7 1000 VLANs or higher 3.6.8 3.6.9 Should be a Layer-3 Switch Should support PoE, on 24 x 10/100/1000 Base Switch 3.6.10 Switch fabric speed 88 Gbps 3.6.11 Packet Throughput 65 Mpps Technical Specifications Page 72
based on 64byte packet size 3.6.12 Form Factor Rack Mountable Static and Dynamic 3.6.13 routing protocol (RIP v2, OSPF, RIPnG, OSPFv3, PIM, MLD) from day 1 3.6.14 Should be a L-3 Switch 3.6.15 Should provide nonblocking architecture 3.6.16 Should support basic QoS feature Should be with the latest stable software 3.6.17 version with all updates, patches and fix ups installed Should support SNMP 3.6.18 v3 for monitoring and should be manageable using web interface Should have internal 3.6.19 redundant power supply Should provide 5 years 3.6.20 onsite comprehensive warranty and maintenance support Number of Switches 2 No s 3.6.21 (24 Ethernet Ports and 24 Fibre Ports per Switch) 3.6.22 Certificate EAL3 Certified Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.7 48 PORT & 24 PORT LAN SWITCH PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 3.7.1 Make and Model Technical Specifications Page 73
3.7.2 3.7.3 3.7.4 Ethernet ports (10/100/1000Mbps) Uplink fiber ports 1000BaseX SFP (should support single and multimode fiber) Gigabit fiber port should support SFPs Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 24/48 No. 2 Per Switch 3.7.5 512 VLANs or higher 3.7.6 3.7.7 Switch Should support stacking PoE and PoE+ on all ports 3.7.8 Switch fabric speed 3.7.9 Packet Throughput based on 64byte packet size 56Gbps or more 41Mpps or more 3.7.10 Form Factor 1Rack Unit 3.7.11 Switch should have static routing and RIP from day 1, upgradable to OSPF and PIM in future 3.7.12 Rack mountable 3.7.13 Certificate EAL3 Certified 3.7.14 3.7.15 3.7.16 Number of Switches- 24 Port Number of Switches- 48 Port Should provide 5 years onsite comprehensive warranty and maintenance support 14 No. 6 No. 3.8 MPLS (MULTI-PROTOCOL LABEL SWITCHING) VPN ROUTER DELHI AND PALATANA, TRIPURA. Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks Technical Specifications Page 74
3.8.1 3.8.2 3.8.3 3.8.4 3.8.5 3.8.6 3.8.7 3.8.8 3.8.9 3.8.10 All locations should have same make and brand of router for interoperability All routers should be with the latest stable software version with all updates, patches and fix ups installed Equipment supplied under this RFP should not be EOS (End of Support) / EOL for the duration of the project (5 Years). Router should have minimum 4 x 10/100/1000 Base T Ports supporting both LAN and WAN protocols and 2 free slots for future expansion Router should have following MPLS features from day 1: L2 VPN, L3 VPN, RSVP Routers should have routing protocols of RIPv2, OSPF, BGP v4 and Multicast traffic Routers should be able to handle all types of application traffic Router should provide VPN, IPSec, NAT security, features Routers should have CoS features for providing priority to traffic Locations having dual routers should be configured with fail-over / redundancy 3.8.11 Management or System Integrator Should provide details System Integrator should provide details of product launch Technical Specifications Page 75
3.8.12 3.8.13 3.8.14 3.8.15 3.8.16 upgradation of any service of routers is the system integrator s responsibility Routers should be 19 rack mountable and should have rack mounting kit Services like VPN, upgrading of CoS should be easily manageable without changes to hardware or network links Router should support attack prevention with 3000 signature update in future. This hardware functionality should be available from day 1 Should provide 5 years onsite comprehensive warranty and maintenance support Proactive Network Management, Monitoring, IPSLA or equivalent, Maintenance, and Customer Service for devices management 3.8.17 Routing Performance Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Minimum 180 kpps 3.8.18 Certificate EAL3 Certified 3.8.19 3.8.20 MPLS Routers required at Data Centre MPLS Routers required at Palatana, Tripura 2 2 Technical Specifications Page 76
3.9 INTERNET ROUTER DELHI Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.9.1 3.9.2 3.9.3 3.9.4 3.9.5 3.9.6 3.9.7 3.9.8 3.9.9 Feature / Specifications Should have at least 4 Ethernet Ports supporting 10/100/1000 and supporting both LAN and WAN protocols Minimum of 1 Mpps of routing performance Should have L2 VPN, L3 VPN and RSVP features from day 1 Should have a modular architecture for future expansion and should have at least 4 free slots Should have internal Dual (redundant) power supply Should not be EOS / EOL for the duration of project (5 yrs) All routers should be with the latest stable software version with all updates, patches and fix ups installed Routers should have routing protocols of RIPv2, OSPF, BGP v4 and Multicast traffic Routers should be able to handle all types of application Minimum Specification Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks System Integrator should provide details System Integrator should provide details of product launch Technical Specifications Page 77
traffic Router should have 3.9.10 VPN, IPSec, NAT security features. Routers should have 3.9.11 CoS features for providing priority to traffic Routers should be 3.9.12 configured with failover / redundancy Management or upgradation of any 3.9.13 service of routers is the service provider s responsibility Routers should be 3.9.14 19 rack mountable and should have rack mounting kit Services like VPN, upgrading of CoS 3.9.15 should be easily manageable without changes to hardware. Router should support SNMP v3 for monitoring, IPSLA or 3.9.16 equivalent and should be manageable using web interface Router should support attack prevention with 3000 signature update in 3.9.17 future. This hardware functionality should be available from day 1 3.9.18 Certificate EAL3 Certified 3.9.17 3.9.18 Should provide 5 years onsite comprehensive warranty and maintenance support Number of routers required Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 2 Technical Specifications Page 78
3.10 EXTERNEL (PERIMETER) FIREWALL DELHI Feature / Specifications Minimum Specification Complian ce (Y / N) for minimum specificati ons Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks 3.10.1 Make and Model 3.10.2 Port Speed 10/100/1000 3.10.3 Port Scalability 3.10.4 Should provide High availability 100% scalability for future expansion 3.10.5 Application-layer protection Blocks attacks such as DNS cache poisoning, 3.10.6 Should be with the latest stable software version with all updates, patches and fix ups installed 3.10.7 Performance 3.10.7.1 Solution should be a Next Generation Firewall system, with capability of supporting at least 2Gbps of Application Identification Enabled Firewall throughput using 64 byte HTTP packet 3.10.7.2 The solution should support at least 1 Gbps of threat prevention throughput with all protection profiles including IPS (Intrusion Prevention System), AV (Anti-Virus), URL Technical Specifications Page 79
Filtering, antispyware & antibot enabled from day one 3.10.7.3 The solution must support at least 225,000 concurrent sessions 3.10.7.4 The solution must support at least 45,000 new session per seconds 3.10.7.5 The solution should support at least 500Mbps of IPSec VPN throughput 3.10.7.6 The solution should support at least 200 SSL VPN Tunnels 3.10.7.7 The solution, with all features turned on (IPS + AV + URL Filtering + Application Identification and Control + Data Filtering) should not fall below 50% ensuring optimum performance 3.10.7.8 For high performance with low latency the solution must provide all application level inspection as real-time stream-based and not using file-based storeand-forward techniques 3.10.7.9 For high performance with low latency the solution must provide hardware offloading of application level (L7) content processing (Anti-Virus, Anti Spyware, Vulnerability Protection, File-type filtering, Data filtering) 3.10.7.10 For high performance with low latency the solution must provide all application level inspection in a single content engine (each packet must only be inspected once even with all content inspection features Technical Specifications Page 80
enabled). 3.10.7.11 The solution must allow policy rule creation for application identification, user identification, host profile, threat prevention, content filtering, QOS and scheduling in a single rule and not at multiple locations 3.10.7.12 The solution must be able to be administered locally without additional management or logging software. 3.10.8 Hardware 3.10.8.1 The solution must support solid state drives (SSD) of at least 120Gbps 3.10.8.2 The solution must support at least 4Gb DRAM 3.10.8.3 The solution must support at least 64Mb Flash 3.10.8.4 The solution must have an operating temperature between 0-50 degree Centrigrade 3.10.8.5 The solution must support at least 8 nos. 10/100/1000 interfaces 3.10.8.6 The solution must support 4 Nos. Gigabit SFP s interfaces 3.10.8.7 The solution must support 2 10/100/1000 high availability interfaces 3.10.8.8 The solution must support 1 10/100/1000 out of band management interface 3.10.8.9 The solution must support separation of the control plane and the data plane 3.10.9 Certifications Technical Specifications Page 81
3.10.9.1 The solution must be in the Leader s quadrant in the latest Gartner Magic Quadrant for Enterprise Network Firewalls report 3.10.9.2 The solution must have achieved NSS Labs recommendation in the last 2 years 3.10.9.3 The solution vulnerability protection must have achieved NSS Labs recommendation and have a very high (in excess of 90% block rate) 3.10.10 Operation Mode 3.10.10.1 The solution must allow policy creation for application identification, user identification, threat prevention and content filtering in a single location: -Application Detection (1000+ apps) -Vulnerability Protection (Client and server side protection) -Gateway Virus Protection -Gateway Spyware Protection -Content Filtering -QoS (marking and/or traffic shaping) 3.10.10.2 The solution must be able to support Network attack detection 3.10.10.3 The solution must be able to support DoS and DDoS protection 3.10.10.4 The solution must be able to support TCP reassembly for fragmented packet protection 3.10.10.5 The solution must be able to support Brute force attack mitigation Technical Specifications Page 82
3.10.10.6 The solution must be able to support SYN cookie protection 3.10.10.7 The solution must be able to support IP spoofing protection 3.10.10.8 The solution must be able to support Malformed packet protection 3.10.10.9 The solution must support Tap mode interface configuration 3.10.10.10 The solution must support Transparent mode 3.10.10.11 The solution must support Layer 2 and Layer 3 deployments 3.10.10.12 The solution be able to support simultaneous deployment with interfaces servicing Layer 3, Layer 2 Transparent and Tap modes 3.10.10.13 The solution shall support 802.1Q VLAN tagging 3.10.10.14 The solution shall support Dual Stack IPv4 / IPv6 application control and threat inspection under: - Tap Mode - Transparent mode - Layer 2 - Layer 3 3.10.10.15 The solution shall support standards based Link aggregation (IEEE 802.3ad) to achieve higher bandwidth 3.10.10.16 The solution shall support logical Ethernet sub-interfaces tagged and untagged. 3.10.10.17 The solution must support the following routing protocols: - Static - RIP v2 Technical Specifications Page 83
- OSPF - BGP v4 3.10.10.18 The solution must have IPv6 Static Routing Support even for virtual routers 3.10.10.19 The solution must have Virtual Router capability that supports all L3 capability 3.10.10.20 The solution must support Policy Based forwarding based on: - Zone - Source or Destination Address - Source or destination port - Application (not port based) - AD/LDAP user or User Group 3.10.10.21 The solution shall support DNS proxy 3.10.10.22 The OEM should ensure that the solution should be operational for 5 years with all features / functionalities enabled on the platform 3.10.10.23 The solution shall support DHCPv4 and DHCPv6 relay 3.10.10.24 The solution must support system configuration rollback to previously saved configurations on box 3.10.10.25 The solution must support validation of policy for shadowed rules before rule application 3.10.10.26 The solution must support the ability to lock configuration while modifying it, avoiding administrator collision when there are multiple people configuring the appliance 3.10.10.27 The solution must Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 84
support the ability to view delta's between current, staged, or past configurations on the solution 3.10.11 High Availability 3.10.11.1 The solution should support full (stateful) configuration synchronization as well as session synchronization. The high availability pair can either be connected directly or over a switched or routed network 3.10.11.2 The solution must be able to support Active/Active configuration 3.10.11.3 The solution must be able to support Active/Passive HA configuration 3.10.11.4 The solution must be capable to detect device failure 3.10.11.5 The solution must be capable to detect link and path failure 3.10.11.6 The solution must be able to support encryption of HA heartbeat & control traffic 3.10.11.7 The solution must be able to support session and configuration synchronization 3.10.11.8 The solution shall synchronize the following for HA: 3.10.11.9 All sessions 3.10.11.10 Decryption Certificates 3.10.11.11 All VPN security associations 3.10.11.12 All threat and application signatures 3.10.11.13 All configuration changes Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 85
3.10.11.14 FIB tables 3.10.11.15 The solution HA shall support hitless upgrades for both major and minor code releases 3.10.12 Management & Reporting 3.10.12.1 The solution must have built in XML API for management purposes; custom logging capabilities 3.10.12.2 The solution have reporting features to generate reports using predefined reports and by using custom builder that allows to assemble a fully customized report that can be saved, exported to PDF/CSV or XML and scheduled to run and then be emailed. 3.10.12.3 Standard Reports should include: 3.10.12.4 Behavioral botnet report (Data regarding unknown applications, IRC traffic, malware sites, dynamic DNS, and newly created domains in analysed with the result displaying the list of potentially infected hosts that can be investigated as members of a botnet) 3.10.12.5 PDF Summary report (A fully customizable onepage summary report that includes data for the top 5 in each category as well as trend charts that are not available in other reports) 3.10.12.6 User Activity Report (Time Based report that shows application and web browsing activity for specific users) Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 86
3.10.12.7 The solution should support device management capabilities through an intuitive web-based interface on each device. 3.10.12.8 Command Line Interface (CLI) should be available 3.10.12.9 Shall support centralized management solution 3.10.13 Policy Based Controls Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.10.13.1 The solution shall control parameters by Security Zone, Users, IP, Application, Host Information Profile, URL Category,Schedule, QoS etc. 3.10.13.2 The solution shall be application based and not port-based and protocol based. 3.10.13.3 The solution shall support the following policy types/capabilities: 3.10.13.4 Policy-based control by port and protocol 3.10.13.5 Policy-based control by application and/or application category (non-port based) 3.10.13.6 Policy-based control by application function (posting, file transfer, desktop sharing, instant messaging, etc.) 3.10.13.7 Policy-based control by user, group or IP address 3.10.13.8 Policy-based control by country code (IN, SG, VN, USA, UK, RUS) 3.10.13.9 Per policy SSL decryption & inspection (forward or reverse proxy), including policy based on URL category. 3.10.13.10 Per policy SSH decryption & inspection 3.10.13.11 Block files by type: bat, Technical Specifications Page 87
cab, dll, exe, pif, and reg 3.10.13.12 Data filtering: Social Security Numbers, Credit Card Numbers, 3.10.13.13 Data filtering: Custom Data Patterns 3.10.13.14 QoS Policy-based traffic shaping (priority, guaranteed, maximum) 3.10.13.15 QoS Policy-based diffserv marking 3.10.13.16 Policy support of IPv6 rules/objects 3.10.13.17 Policy support of multicast rules/objects 3.10.13.18 Policy support for scheduled time of day enablement 3.10.14 Application Security Policy 3.10.14.1 The solution shall support network traffic classification which identifies applications across all ports irrespective of port/protocol/evasive tactic 3.10.14.2 The solution shall have multiple mechanisms for classifying applications 3.10.14.3 The solution shall have application and application function identification and decoding technology 3.10.14.4 The solution shall be able to handle unknown/unidentified applications e.g. alert, block or allow 3.10.14.5 The solution shall be able to create custom application signatures and categories 3.10.14.6 The solution shall include a searchable list of currently identified applications with explanation and links to external sites for further Technical Specifications Page 88
clarification 3.10.14.7 The solution shall allow updating the application database automatically or manually via the control or traffic plane 3.10.14.8 The solution shall allow dynamic updates of the application DB and not require a service restart or reboot 3.10.14.9 The solution shall warn the end-user with a customizable page when the application is blocked 3.10.14.10 The solution shall allow port-based controls to be implemented for all applications as well in the same rule 3.10.14.11 The solution shall delineate specific instances of peer2peer traffic (Bittorrent, emule, neonet, etc.) 3.10.14.12 The solution shall delineate specific instances of instant messaging (AIM, YIM, Facebook Chat, etc.) 3.10.14.13 The solution shall delineate different parts of the application such as allowing Facebook chat but blocking its filetransfer capability 3.10.14.14 The solution shall delineate specific instances of Proxies (ultrasurf, ghostsurf, freegate, etc.) 3.10.14.15 The solution shall support Voice based protocols (H.323, SIP, SCCP, MGCP etc.) 3.10.14.16 The solution shall be able to create filters to control groups of application based on category, sub category, technology, risk or Technical Specifications Page 89
characteristics ect. 3.10.14.17 The solution shall support useridentification allowing Active Directory, LDAP, RADIUS groups, or users to access a particular application, while denying others 3.10.15 URL Filtering 3.10.15.1 The solution shall support URL-Filtering 3.10.15.2 The solution shall have the database located locally on the device 3.10.15.3 The solution shall support custom URLcategorization 3.10.15.4 The solution shall support customizable block pages 3.10.15.5 The solution shall support block and continue (i.e. allowing a user to access a website which potentially violates policy by presenting them a block page with a warning with a continue option allowing them to proceed for a certain time) 3.10.15.6 The solution shall support logs populated with end user activity reports for site monitoring within the local solution 3.10.15.7 The solution shall support logs populated with end user activity reports for site monitoring within the central manager 3.10.15.8 The solution shall support URL Filtering of international languages. Please state all supported languages 3.10.15.9 The solution shall Technical Specifications Page 90
support Drive-bydownload control to prevent unintentional or malicious download of executable files. 3.10.15.10 The solution shall support URL Filtering policies by AD user, group, machines and IP address/range 3.10.16 Threat Prevention Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.10.16.1 The solution shall support Vulnerability Protection features 3.10.16.2 The solution shall support Virus and Spyware (phone home attacks) protection 3.10.16.3 The solution shall block application vulnerabilities 3.10.16.4 The solution shall block spyware and malware 3.10.16.5 The solution shall not have more than 50% degradation in the rated performance when IPS is enabled 3.10.16.6 The solution shall not have more than 50% degradation in the rated performance when Virus Protection is enabled 3.10.16.7 The solution shall not have more than 50% degradation in the rated performance when Spyware Protection is enabled 3.10.16.8 The solution shall not have more than 50% degradation in the rated performance hit when the IPS, Virus Protection and Spyware Protection is enabled 3.10.16.9 The solution shall block known network and application-layer vulnerability exploits 3.10.16.10 The solution shall block Technical Specifications Page 91
buffer overflow attacks 3.10.16.11 The solution shall block DoS/DDoS attacks 3.10.16.12 The solution shall perform stream-based Anti-Virus and not storeand-forward traffic inspection 3.10.16.13 The solution shall perform stream-based Anti-Spyware and not store-and-forward traffic inspection 3.10.16.14 The solution shall be able to perform Antivirus scans for SMB traffic 3.10.16.15 The solution shall support attack recognition for IPv6 traffic the same way it does for IPv4 3.10.16.16 The solution shall support Built in Signature and Anomaly based Vulnerability Protection Engine 3.10.16.17 The solution shall support the ability to create custom userdefined signatures 3.10.16.18 The solution shall support to exclude certain hosts from scanning of particular signatures 3.10.16.19 The solution shall support CVE cross referencing where applicable 3.10.16.20 The solution shall support granular tuning with option to configure overrides for individual signatures 3.10.16.21 The solution shall support automatic security updates directly over a secure connection (i.e. no dependency of any Technical Specifications Page 92
intermediate device) 3.10.16.22 The solution Vulnerability / Virus / Spyware protection updates shall not require reboot of the unit. 3.10.16.23 The solution shall support several prevention techniques including drop packet, tcp rst (Client, Server & both) etc. 3.10.16.24 The solution shall support response adjustment on a per signature basis. 3.10.16.25 Protocol decoder-based analysis 3.10.16.26 Protocol anomaly-based protection to detect non-rfc compliant protocol usage such as the use of overlong URI or overlong FTP login 3.10.16.27 Stateful pattern matching detects attack across more than one packet, taking into account elements such as the arrival order and sequence 3.10.16.28 Statistical anomaly detection prevents ratebased DoS flooding attacks 3.10.16.29 Heuristic-based analysis to detect anomalous packet and traffic patterns such as port scans and host sweeps 3.10.16.30 Capabilities such as blocking invalid or malformed packets, IP defragmentation and TCP reassembly for protection against evasion and obfuscation methods employed by attackers 3.10.16.31 The solution shall Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 93
support notifications via alerts, email notifications, SNMP traps and packet logs 3.10.17 Data Filtering 3.10.17.1 The solution shall support file identification by signature and not file extensions 3.10.17.2 The solution shall support identification and optionally preventing the transfer of various files (i.e. MS Office, PDF, etc.) via identified applications (i.e. P2P, IM, SMB, etc.) 3.10.17.3 The solution shall support compressed information stored in zipped format and be able to unpack and filter per policy 3.10.17.4 The solution shall be capable of identifying and optionally preventing the transfer of files containing sensitive information (i.e. credit card numbers) via regular expression 3.10.18 User Identification 3.10.18.1 The solution shall support authentication services for useridentification: 3.10.18.2 Active Directory 3.10.18.3 LDAP 3.10.18.4 edirectory 3.10.18.5 RADIUS 3.10.18.6 Kerberos 3.10.18.7 Client Certificate 3.10.18.8 The solution should support the creation of security policy based on Active Directory Users and Groups in addition Technical Specifications Page 94
to source/destination IP 3.10.18.9 The solution shall support interrogation of the host security posture using a flexible policy so that information can be used in security policy 3.10.18.10 The solution shall support useridentification in policy without installing an agent on individual endpoints 3.10.18.11 The solution shall support useridentification from Citrix and terminal services environments in policy and logs 3.10.18.12 The solution shall populate and correlate all logs with user identity (traffic, IPS, URL, data, etc.) without any additional products or modules in real-time 3.10.18.13 The solution should support role-based administrative assignment to allow specific users to have full, read-only, or no access to the functions of the firewall. Automated responses can be set up to notify specific users of specific events or incidents 3.10.19 QoS Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.10.19.1 The solution should support the ability to create QoS policy on a per rule basis: (across product line) 3.10.19.2 by source address 3.10.19.3 by destination address 3.10.19.4 by user/user group as defined by AD 3.10.19.5 by application (such as Technical Specifications Page 95
Skype, Bittorrent, YouTube, azureus) 3.10.19.6 by static or dynamic application groups (such as Instant Messaging or P2P groups) 3.10.19.7 by port 3.10.19.8 The solution shall define QoS traffic classes with: 3.10.19.9 guaranteed bandwidth 3.10.19.10 maximum bandwidth 3.10.19.11 priority queuing 3.10.19.12 The solution should support real-time prioritization of voice based protocols like H.323, SIP, SCCP, MGCP and applications like Skype 3.10.19.13 The solution should support diffserv marking of packets 3.10.19.14 The solution should support real-time bandwidth statistics of QoS classes 3.10.20 SSL/SSH Decryption 3.10.20.1 The solution shall be able to identify, decrypt and evaluate SSL traffic in an outbound connection (forwardproxy) 3.10.20.2 The solution shall be able to identify, decrypt and evaluate SSL traffic in an inbound connection 3.10.20.3 The solution shall be able to identify, decrypt and evaluate SSH / SSH Tunnel traffic in an outbound connection 3.10.20.4 The solution shall be able to identify, decrypt and evaluate SSH / SSH Tunnel traffic in an inbound connection 3.10.20.5 The solution shall support the ability to Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 96
have a SSL inspection policy differentiate between personal SSL connections i.e. banking, shopping, health and non-personal traffic 3.10.20.6 The solution shall able to decrypt in the following network modes: 3.10.20.7 Tap mode 3.10.20.8 Transparent mode 3.10.20.9 Layer 2 mode 3.10.20.10 Layer 3 mode 3.10.21 VPN 3.10.21.1 The solution shall support IPSec VPN 3.10.21.2 The solution shall support SSL VPN 3.10.21.3 The solution shall support IPSec VPN or SSL VPN without additional licensing 3.10.21.4 IPSec VPN should be integrated with the solution and support full encryption standards suites: 3.10.21.5 DES, 3DES, AES 3.10.21.6 MD5 and SHA 1 authentication 3.10.21.7 Diffie-Hellman Group 1, Group 2 and Group 5 3.10.21.8 Internet Key Exchange (IKE) algorithm 3.10.21.9 AES 128, 192 & 256 (Advanced Encryption Standard) 3.10.22 Authentication Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.10.22.1 The solution administrative module shall support the following authentication protocols: 3.10.22.2 LDAP 3.10.22.3 Radius (vendor specific attributes) Technical Specifications Page 97
3.10.22.4 Token-based solutions (i.e. Secure-ID) 3.10.22.5 Kerberos 3.10.22.6 The solution s SSL VPN shall support the following authentication protocols: 3.10.22.7 LDAP 3.10.22.8 Radius 3.10.22.9 Token-based solutions (i.e. Secure-ID) 3.10.22.10 Kerberos 3.10.22.11 Any combination of the above 3.10.23 TCP Dump / PCAP Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.10.23.1 The solution shall support packet captures based on: 3.10.23.2 Source Address 3.10.23.3 Destination Address 3.10.23.4 Applications 3.10.23.5 Unknown Applications 3.10.23.6 Port 3.10.23.7 any threat 3.10.23.8 data-filters 3.10.23.9 any combination of the above 3.10.23.10 The solution shall support PCAP downloads of specific traffic sessions from the GUI from the logging screen 3.10.24 Modern Malware Protection 3.10.24.1 The solution will have a built in protection against unknown Malware and or zero day attacks 3.10.24.2 The solution shall support sandbox behavior based inspection and protection of unknown viruses and malware 3.10.24.3 The solution shall support automated Technical Specifications Page 98
signature generation for discovered malware 3.10.24.4 The solution shall support inline control of malware infection and command/control traffic 3.10.24.5 The firewalls shall support DNS-based signatures to detect specific DNS lookups for hostnames that have been associated with malware 3.10.25 Should provide 5 years onsite comprehensive warranty and maintenance support 3.10.26 Number of Devices 2 No s Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.11 INTERNAL FIREWALL DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specificatio ns Proposed Capacity / Hardware (Bidder can propose technically superior componen ts) Details / Remarks 3.11.1 Make and Model 3.11.2 Should be rack mountable 3.11.3 12 Nos. 10/100/1000 interfaces and option for 4 fiber slots to cater future requirements. 3.11.4 1 out of band management interface 3.11.5 Minimum RAM 4GB 3.11.6 Flash 64 MB & 120GB SSD hard disk 3.11.7 Separation of data plane and management plane with dedicated hardware resources for data plane and management plane Technical Specifications Page 99
3.11.8 Next Generation Firewall system, with a capability of supporting at least 2Gbps of Application Identification Enabled Firewall throughput using 64 byte HTTP packet size,(not UDP 1518) 3.11.9 225,000 concurrent sessions & 45,000 new sessions per second. 3.11.10 static routing, RIPv2, OSPF & BGP v4 3.11.11 Ipv4 & IPv6 routing support for virtual routers 3.11.12 Should provide High availability 3.11.13 Should be with the latest stable software version with all updates, patches and fix ups installed 3.11.14 Traffic classification based on applications across all ports irrespective of port/protocol/evasive tactic 3.11.15 Application detection (at least 1000+ applications) 3.11.16 Multiple mechanisms for classifying applications including application signatures, SSH & SSL, Application decoders & heuristics 3.11.17 Handling of unknown/unidentified applications e.g. alert, block or allow 3.11.18 Protocols support IPSec, DES, 3DES, FTP, HTTP, HTTPS, IPv6 3.11.19 Inspection of HTTPS & SSH encrypted traffic 3.11.20 Support for DNS proxy & DNS sinkhole to prevent against DNS attacks 3.11.21 Policy controls based on interfaces, zones, user-id, source & destination address, applications (not ports) Technical Specifications Page 100
3.11.22 Dual stack support IPv4/IPv6 application support 3.11.23 Deployment scenarios TAP mode, vwire mode, Layer2 & Layer3 routed mode 3.11.24 Support active-active and active-standby HA configuration 3.11.25 Policy based controls by country 3.11.26 Per policy SSL decryption & inspection 3.11.27 User identification Active directory, LDAP, edirectory, Radius, Kerberos, client certificates & API s 3.11.28 Protections DOS, DDOS, IP spoofing, Brute force, Syn cookie & malformed packet protection 3.11.29 QoS features like traffic prioritization, differentiated services, committed access rate 3.11.30 QoS policy on per rule basis based on source address, destination address, user/group, application (such as bittorrent, Skype, Facebook), dynamic application group & port 3.11.31 Internal/external management system for real-time monitoring, Logging & reporting functions 3.11.32 Customize application dashboard 3.11.33 Detailed user activity report including information on applications 3.11.34 Reporting based on application, users and threats or in any combination 3.11.35 Report generation on a manual or schedule (Daily, Technical Specifications Page 101
Weekly, Monthly, etc) basis 3.11.36 XML API for management purposes; custom logging capabilities 3.11.37 Console, Telnet, SSHv2, Browser based configuration 3.11.38 SNMPv1 & v2 3.11.39 Common Criteria EAL4+ certified 3.11.40 ICSA certified 3.11.41 Gartner Magic Quadrant of Enterprise Firewall Leaders Quadrant 3.11.42 NSS Labs recommendation 3.11.43 Should provide 5 years onsite comprehensive warranty and maintenance support 3.11.44 Number of Devices 2 No s Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 3.12 DLP (DATA LOSS PREVENTION) & INFORMATION SECURITY ENFORCEMENT SOLUTION Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware (Bidder can propose technically superior components) Details / Remarks Make and Model Can be appliance 3.12.1 based or software solution 3.12.2 Must provide next generation data threat prevention and information discovery functions to protect structured, semistructured, unstructured mission critical data in the enterprise Technical Specifications Page 102
3.12.3 For software based solution, Supplier has to provide appropriate hardware keeping overall design and functional requirement under consideration and must not affect overall application performance. The proposed solution must support 100 users & scalable to 200 users. 3.12.4 solution should not require any third party proxy server (such as ICAP servers ) to provide Enforcement of Information Security 3.12.5 solution should cover both Active and passive FTP including fully correlating transferred file data with control information 3.12.6 solution Should have the ability to monitor popular IM protocols (AIM, Yahoo, MSN, IRC etc.) and properly classify tunneled IM traffic (HTTP) 3.12.7 solution should be able to interface with an institution s employee or staff directories (e.g., Active Directory, LDAP) 3.12.8 Solution must have Identity and Role Based policy capabilities that integrate with AD/LDAP/HR database. 3.12.9 solution should be capable of "Segmentation of Duty" (SoD) based Enforcement of Information Security 3.12.10 solution should enforce "Automatic Access Control" on Data and Information 3.12.11 solution must be able to Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 103
apply different policies to different employee groups 3.12.12 solution should have ability to filter out network traffic for inspection based on protocol, IP range, or email sender/recipient email 3.12.13 solution should provide encryption capabilities to protect data at risk 3.12.14 solution should have a comprehensive Information Classification methodology that would be readily deployable and does not dependent on fingerprint technology 3.12.15 solution should have Resources Qualification and experience in Information Classification 3.12.16 solution should have ability to create and manage policies that can be deployed across all components (Network and Endpoints) 3.12.17 solution MUST use automated policy mechanism 3.12.18 solution should have built-in Automated Policy Synthesis mechanism 3.12.19 solution should be able to monitor and prevent Advanced Persistent Threats (APT) 3.12.20 solution should have Built-in Ontologies on International PII and PCI-DSS capabilities and has the ability to add or customized new Ontologies to cater to specific Government or Defense requirements 3.12.21 solution should have rule or policy-based capabilities such as Technical Specifications Page 104
assigning access rights, restricting where users can store sensitive data, and so forth 3.12.22 solution should have ability to Detect based on fully customizable regular expressions 3.12.23 solution should have Ability to detect and protect confidential unstructured data based on the data categorization that has been learnt 3.12.24 solution should have Ability to detect and protect new or unseen documents, which content is similar to the data categorization which has been taught via data categorization 3.12.25 solution should have Ability to detect scanned documents, which contains sensitive data in text form 3.12.26 solution should have Ability to detect screen captures or picture formats, which contain sensitive data in text form. 3.12.27 Solution should have Ability to learn to categorize data via providing a set of sample documents to improve accuracy of detection. 3.12.28 solution should have Ability to configure and send multiple automated responses based on severity, match count, policy, etc. 3.12.29 solution should have Ability to release quarantined email from notification received. 3.12.30 On-screen/ pop-up/ e- mail notification Technical Specifications Page 105
delivered to users during a rule/ policy violation and escalation workflow to ICT Security team or immediate manager. 3.12.31 User s ability to conduct self-remediation (such as on-screen/pop-up/e-mail notification prompting user to confirm whether to continue or cancel confidential data transfer). Ability to capture justification for DLP rule/policy violation as part of logs capturing. 3.12.32 All relevant incident details on a single screen/ page to allow quick user decisionmaking and immediate action. 3.12.33 Per-user ability to customize the layout and data of the incident snapshot. 3.12.34 Ability for an incident to be correlated to other incidents by subject, sender, recipient, filename, file owner, user name, and policy. 3.12.35 solution should have ability to support realtime incident analysis 3.12.36 solution should have Integration with external directory for incident workflow assignment 3.12.37 Support for role-based access and delegated administration. 3.12.38 Integration with Active Directory or other directory 3.12.39 Ability to support automatic updates (signatures/ rules/ etc) and firmware upgrades 3.12.40 solution should have a list of pre-defined template reports Technical Specifications Page 106
3.12.41 solution should Support report customization 3.12.42 Number of device / software required 3.12.43 Should provide 5 years onsite comprehensive warranty and maintenance support 1 No s 3.13 WAN SPECIFICATIONS DELHI & PALATANA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specificatio ns Proposed Capacity / Hardware (Bidder can propose technically superior componen ts) Details / Remarks Site uptime / availability 3.13.1 for all locations 99.5%, 3.13.2 Service Provider Should provide notification alerts (email / sms / etc.) if bandwidth utilization is more than 75% for any location 3.13.3 Service Provider Should have nationwide IP Network for providing MPLS based VPN services with PoP at all the locations under consideration 3.13.4 In case of dual local loop, service provider should be different for local loop provisioning 3.13.5 Service Provider should support VoIP and Video conferencing (QoS & CoS) services 3.13.6 Dual MPLS PoP redundancy for DC 3.13.7 Service Provider should provide prior information for any link maintenance Technical Specifications Page 107
at client / Service Provider level, after seeking approvals maintenance 3.13.8 Service Provider should be able to provide real-time monitoring and hourly, daily, weekly and monthly reports in Text, HTML, PDF formats 3.13.9 Service Provider should provide Notification or alerts through email or SMS for link or equipment failure status 3.13.10 Should able to provide the service for minimum five years period compulsory 3.14 INTERNET LINKS SPECIFICATIONS DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specificatio ns Proposed Capacity / Hardware (Bidder can propose technically superior componen ts) Details / Remarks Site uptime / availability 3.14.1 99.5% 3.14.2 System Integrator to provide Minimum Public IPs at Data Center 3.14.3 Easy to upgrade bandwidth in multiples of 2Mb, without much changes in hardware 3.14.4 Internet Link Should be a premium link with 1:1 ratio (uncompressed) 3.14.5 Internet link to be provided on Ethernet 3.14.6 Service Provider should have its own international Internet gateway 3.14.7 Internet link failover from primary to backup should 15 Technical Specifications Page 108
be seamless, without manual intervention. 3.14.8 No restriction on data / file transfer from Internet 3.14.9 Should able to provide the service for minimum five years period compulsory 3.14.10 Proactive Network Management and Monitoring, Maintenance Technical Specifications Page 109
SECTION 2.7 TECHNICAL SPECIFICATION FOR LOAD BALANCERS 1.0 LOAD BALANCERS DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 Make and Model Should be appliance 1.2 based solution with high performance purpose built hardware. The appliance should have 4 GB RAM for 1.3 support for multiple load balancing features and functions Should support load 1.4 balancing features such as server load balancing, link load balancing etc. The appliance should have minimum 4 triple 1.5 speed 10/100/1000 Mbps gigabit copper ports The appliance should have 1.5 Gbps of 1.6 throughput and scalable to 2.5 Gbps without any additional hardware. Should have minimum 1.7 1M concurrent connections & scalable to 2M on same device. 1.8 Appliance should provide Technical Specifications Page 110
1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 full ipv6 support and OEM should be IPv6 gold-certified. OEM should be listed vendor for ipv6 phase-2 certification. The appliance should support layer 2 to layer 7 load balancing Extensible policies (epolicies) scripts to implement business logic on network without changes in application code. epolicy scripting should support deep packet inspection of protocol including HTTP, SOAP, Weblogic and Diameter The appliance should support server load balancing algorithms i.e. round robin, weighted round robin, least connection, Persistent IP, Hash IP, Hash Cookie, consistent hash IP, shortest response, proximity, snmp, SIP session ID, hash header etc. Should support one arm, reverse and transparent proxy mode deployment scenarios and should support nested layer7 and l4 policies. Should maintain server persistency based on source ip and destination ip, http header, url, cookie and SSL ID. The appliance should support multi-port, scripted and custom health check with content verification Should provide application & server health checks for well- Technical Specifications Page 111
1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 known protocols i.e. ARP, ICMP, TCP, DNS, RADIUS, HTTP/HTTPS, RTSP etc.. The appliance should have and/or relationship to check various dependencies for the application delivery should support layer4 and layer 7 load balancing for HTTP/HTTPS, FTP/FTPS, SIP, RTSP, RDP, TCP, TCPS and UDP protocols Should support graceful shut down of real services Should support reverse proxy functionality from Day 1 Should support SDNS functionality from Day 1 Should provide comprehensive and reliable support for high availability and N+1 clustering based on stateful session failover with Active-active & active standby unit redundancy mode. Should support USB based FFO link to synchronize configuration at boot time of HA Support for multiple communication links for realtime configuration synchronizations including HA group, gateway health check, decision rules, SSF sessions etc.. and heartbeat information Should support floating MAC address to avoid MAC table updates on the upstream routers/switches and to speed up the failover Technical Specifications Page 112
1.26 1.27 1.28 1.29 1.30 1.31 1.32 Should support for secondary communication link for backup purpose Should support floating IP address and group for statefull failover support. Appliance must have support 256 floating ip address for a floating group Should support built in failover decision/health check conditions including, CPU overheated, system memory, process health check, unit failover, group failover and reboot Should also have option to define customized rules for gateway health check - the administrator should able to define a rule to inspect the status of the link between the unit and a gateway Configuration synchronization at boot time and during run time to keep consistence configuration on both units. Should support global load balancing algorithms like global round robin (grr), VIP based weighted global round robin, global connection overflow, global least connections, IP overflow, Proximity etc., Should provide Secure online application delivery using hardware/software based high performance SSL acceleration with minimum 500Mbps of Technical Specifications Page 113
1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 SSL throughput and 5,000 ssl TPS and scalable to 7500 ssl TPS on same appliance. The appliance should support Certificate format as "OpenSSL/Apache, *.PEM", "MS IIS, *.PFX", and "Netscape, *.DB". The appliance should have additional hardware card to perform the SSL offloading / acceleration for 1024 and 2048 bit certificates. The appliance should support use of password protect Certificate/Private Key backup/restore to/from local disk or remote TFTP server, and through WebUI The appliance should support Self generates CSR (Certificate Signing Request), self-signed Certificate and private key for specified host. The appliance should support customization for SSL Error pages. The appliance should support HTTP to HTTPS location header rewrite for enhanced application delivery support The appliance should have end to end ssl support to act as a SSL Server and/or as SSL Client Should support client certificate verification, certificate bases access control, CRL's (HTTP, FTP,LDAP) and OSCP protocol Should support advance ACL's to protect against Technical Specifications Page 114
1.42 1.43 1.44 1.45 1.46 1.47 1.48 1.49 network based flooding attacks. Administrator should able to define ACL's rules based on connections per second (CPS) and concurrent connections (CC), cookie value. Should provide performance optimization using TCP connection multiplexing, TCP buffering and IEEE 802.3ad link aggregation. Should support TCP optimization options including windows scaling, timestamp & Selective Acknowledgement for enhanced TCP transmission speed. TCP optimization option configuration should be defined on per virtual service basis not globally. Appliance should provide real time Dynamic Web Content Compression to reduce server load. Should provide selective compression for Text, HTML, XML, DOC, Java Scripts, CSS, PDF, PPT, and XLS Mime types. Should provide have provision to define policy to skip compression for selected trouble URL (RegEx, Web Objects) for the specified Virtual. should provide Advanced high performance memory/packet based Web cache; fully integrated with HTTP/HTTPS Should provide support for customized cache Technical Specifications Page 115
1.50 1.51 1.52 1.53 1.54 1.55 1.56 1.57 1.58 1.59 rules including max object size, TTL objects, refresh time interval etc.. should provide detailed cache access statistics based on ip or http hosts should support cache refresh with CLI, XML- RPC input commands and "PURGE" request The appliance should support transparent, layer 7 proxy and triangular mode support The appliance should support L7 rule based application firewall to protect the internal applications within base license Appliance should have security features like reverse proxy firewall, Syn-flood and dos attack protection features from the day of installation. The appliance should have extensive report and logging with inbuilt tcpdump like tool and log collecting functionality The appliance should have SSH CLI, Direct Console, SNMP, Single Console per Cluster with inbuilt reporting. Should support XML-RPC for integration with 3rd party management and monitoring The appliance should provide detailed logs and graphs for real time and time based statistics Appliance must support multiple configuration files with 2 bootable partitions for better availability and easy Technical Specifications Page 116
1.60 1.61 1.62 upgrade / fallback. The system should support led warning and system log alert for failure of any of the power and CPU issues Should provide 5 years onsite comprehensive warranty and maintenance support Number of Load Balancers 2 No s Technical Specifications Page 117
SECTION 2.8 TECHNICAL SPECIFICATION FOR RACKS 1.0 42U RACK (NETWORK & SERVER) PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 Make and Model 1.2 Mounting space of 42U 1.3 Depth 1000mm 1.4 1.5 1.6 1.7 1.8 1.9 Width - Should accommodate 19 inch devices and devices in the solution Four vertical posts for rack mounting of equipment utilizing 4 posts Should be able to open the rack from all 4 sides (along with front/back doors) Should have adequate ventilation to provide air flow Redundant Rack PDUs / Power strips Each rack should have redundant PDUs / power strips Technical Specifications Page 118
1.10 Sufficient cage nuts for installation of equipments in the Rack Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Should have front 1.11 and back door opening along with Lock and Key Sufficient clearance 1.12 between side panel and posts Sufficient clearance 1.13 between front door and vertical mounting posts 1.14 Perforated front / back doors and roof Should provide 5 years onsite 1.15 comprehensive warranty and maintenance support 1.16 Blanking Panels 1.17 No. of Racks (42U) 1 (One) 2.0 12U WALL MOUNT NETWORK RACK PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 2.1 Make and Model 2.2 2.3 2.4 Mounting space of 12U Wall Mount Accessories Width - Should accommodate 19 inch devices and devices offered in the solution 2.5 Should be able to Technical Specifications Page 119
2.6 2.7 2.8 open the rack from all 3 sides Should have adequate ventilation to provide air flow Redundant Rack PDUs / Power strips Sufficient cage nuts for installation of equipments in the Rack Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 2.9 With Lock and Key 2.10 2.11 2.12 Sufficient clearance between side panel and posts Should provide 5 years onsite comprehensive warranty and maintenance support No. of Server Racks (12U) 19 (Nineteen) Technical Specifications Page 120
SECTION 2.9 TECHNICAL SPECIFICATION FOR PASSIVE WORK 1.0 WALL MOUNT PATCH PANEL DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 Make 1.2 Wall Mount Patch Panel 1.3 TIA/EIA Category: 6 1.4 1.5 1.6 1.7 1.8 1.9 1.10 minimum 250 ports, Interface RJ45 Support 10/100/1000Mbps Printed colour coding to make the termination easy Should be capable of handling data, voice, and video Modular, moulded plastic modules should be UL rated Should have a clear label holder Should have a cable handler to avoid stress from the hanging cable bundle 2.0 PATCH PANEL (NETWORK & SERVER RACK) PALATANA, TRIPURA Technical Specifications Page 121
Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 2.1 Make 2.2 Rack Mountable, 1 RU size panel 2.3 TIA/EIA Category: 6 2.4 24 Ports, Interface RJ45 2.5 2.6 2.7 2.8 2.9 2.10 Support 10/100/1000Mbps Printed colour coding to make the termination easy Should be capable of handling data, voice, and video Modular, PCB based, moulded plastic modules should be UL rated Should have a clear label holder Should have a cable handler to avoid stress from the hanging cable bundle 3.0 PATCH PANEL FOR WALL MOUNT NETWORK RACK PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 3.1 Make 3.2 Rack Mountable, 1 RU size panel Technical Specifications Page 122
3.3 TIA/EIA Category: 6 3.4 24 Ports, Interface RJ45 3.5 3.6 3.7 3.8 3.9 3.10 Support 10/100/1000Mbps Printed colour coding to make the termination easy Should be capable of handling data, voice, and video Modular, PCB based, moulded plastic modules should be UL rated Should have a clear label holder Should have a cable handler to avoid stress from the hanging cable bundle at rear 4.0 50μ, 6/12-core Multi mode OM3 distribution LSZH cable as per ISO/IEC-11801 PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 4.1 Make 4.2 4.3 4.4 Fiber Optic Cable, ISO/IEC-11801-OM3 50/125μ, OM3 Indoor Tight buffered Int/Ext type as per IEC 60332-3, IEC 61034, IEC 60754 Shall be 50μ, 6/12-core Multi mode OM3 distribution cable as per ISO/IEC-11801 Shall be able to meet Gigabit & 10 Gigabit Ethernet performance up to 300 meters requirement specified by Technical Specifications Page 123
4.5 4.6 4.7 4.8 4.9 IEEE 802.3z (1000 Base- X) & IEEE 802.3ae (10G Base-X) Shall be suitable for using in the building shaft Shall be a distribution cable with tight buffered construction Shall have aramid yarns (Kevlar) inside to add strength to the cable Tensile load should be 1000 Newton or higher and crush resistance should be 2000 Newton or higher Fiber cable shall be RoHS Compliant. 5.0 Fiber optic OM3 LIU, fully loaded with pigtails, couplers, sleeves and splice trays 6/12/24 fiber PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 5.1 Make 5.2 5.3 5.4 Fiber Optic LC style fully loaded Patch Panel (FOPP), 19" Rack Mount with 6/12/24 nos. of OM3 50/125μ Pigtails. Shall have 6/12/24 nos. of ISO/IEC-11801-OM3 Pigtails with LC Type Connectors Shall have all accessories including coupler plates preloaded with duplex LC couplers (OM3), pigtails for terminating fibers on Technical Specifications Page 124
5.5 5.6 5.7 5.8 5.9 the FOPP Shall be Front Patching Type, 1U high and rack mountable on standard 19 rack with mounting arrangements Shall be supplied with fusion splicing sleeves for termination of fiber Shall be slide-out type drawer enclosure for Easy access to splicing tray, Easy access to back side of the connector and have labels for better identification Shall have all necessary accessories for fiber management inside such as Fiber guides, radius controls & secure tie downs within the FOPP LIU shall be RoHS Compliant. 6.0 LC- LC duplex OM3 Multimode LSZH patch cords PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 6.1 Make 6.2 6.3 6.4 Fiber Optic Patch Cable (LC-LC), 3 Mtrs. Long, ISO/IEC-11801-OM3 50μ Duplex, LSZH All patch cords shall conform to EIA/TIA- 568C.3 and ISO/IEC- 11801 Shall be Duplex Multi Mode Fiber Optic Patch Cords OM3 50μ Technical Specifications Page 125
6.5 6.6 6.7 6.8 6.9 Shall support network line speeds up to 10 Gbps. Shall have LC Connector jacks at both the ends All patch cords shall be factory terminated and packed. Shall be Low-Smoke & Zero-Halogen and RoHS compliant LIU shall be RoHS Compliant. 7.0 9μ, 6/12-core Single mode OS2 Indoor/Outdoor rated LSZH cable as per ISO/IEC- 11801 PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 7.1 Make 7.2 7.3 7.4 7.5 7.6 7.7 Fiber Optic Cable, ISO/IEC-11801-OS2 9/125μ, Indoor/Outdoor, IEC 60332-3, IEC 61034-2, IEC 60754-2 Shall be 9μ, 6/12 -core Single mode OS2 metallic armored cable. Shall be able to meet Gigabit & 10 Gigabit Ethernet performance requirement specified by IEEE 802.3 Shall be suitable for using in the building shaft and outdoor laying Optical Fibers should be in multitube/unitube type of cables Shall be certified third party labs for IEC Technical Specifications Page 126
7.8 7.9 60332-3 for flame retardant, IEC 61034-2 for smoke density and RoHS compliant Tensile load should be 2700 Newton or higher and crush resistance should be 3000 Newton or higher Shall have water blocked construction to prevent water absorption and consequent damages 8.0 Fiber optic OS2 LIU, fully loaded with pigtails, couplers, sleeves and splice trays 6/12/24 fiber PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 8.1 Make 8.2 8.3 8.4 8.5 Fiber Optic LC style fully loaded Patch Panel (FOPP), 19" Rack Mount with 6/12/24 nos. of OS2 9/125μ Pigtails. Shall have 6/12/24 nos. of ISO/IEC-11801-OS2 Pigtails with LC Type Connectors Shall have all accessories including coupler plates preloaded with duplex LC couplers (OS2), pigtails for terminating fibers on the FOPP Shall be Front Patching Type, 1U high and rack mountable on standard 19 rack with mounting arrangements Technical Specifications Page 127
8.6 8.7 8.8 8.9 Shall be supplied with fusion splicing sleeves for termination of fiber Shall be slide-out type drawer enclosure for Easy access to splicing tray, Easy access to back side of the connector and have labels for better identification Shall have all necessary accessories for fiber management inside such as Fiber guides, radius controls & secure tie downs within the FOPP LIU shall be RoHS Compliant. 9.0 LC- LC duplex OS2 Single mode LSZH patch cords PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 9.1 Make 9.2 9.3 9.4 9.5 9.6 Fiber Optic Patch Cable (LC-LC), 3 Mtrs. Long, ISO/IEC-11801-OS2 9μ Duplex, LSZH All patch cords shall conform to EIA/TIA- 568C.3 and ISO/IEC- 11801 Shall be Duplex Single Mode Fiber Optic Patch Cords OS2 9μ Shall support network line speeds up to 10 Gbps. Shall have LC Connector jacks at both the ends Technical Specifications Page 128
9.7 9.8 9.9 All patch cords shall be factory terminated and packed. Shall be Low-Smoke & Zero-Halogen and RoHS compliant LIU shall be RoHS Compliant. 10.0 Category 6 Unshielded Twisted Pair LSZH Cable PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 10.1 Make 10.2 10.3 10.4 10.5 10.6 10.7 UTP Cable, TIA-568C.2, Category-6, LSZH (305 Mtrs./1000 feet per Box) Shall be of 4 twisted pairs of 23 AWG solid conductors & support network line speeds up to 1 GBps. Shall be 4-pair Unshielded twisted pair with a cross filler, meeting Category 6 tested to 500 MHz or more as per TIA-568C.2. Support 10/100/1000Mbps Cable should be tested till 500 MHz or more from independent laboratories like ETL for 4 connections. Submission of this report is mandatory Should be capable of handling data, voice, video & meet the Technical Specifications Page 129
10.8 10.9 10.10 applications ATM, ISDN etc. Shall have the length printed on the outer jacket of after every meter. Shall be fire retardant, Low smoke zero halogen as per IEC 60332, IEC 61034-2 and IEC 60754-2 respectively Shall be supplied in Reel of 305 Meters/ 1000 feet packed in Boxes 11.0 Category 6 Unshielded Twisted Pair LSZH Cable PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 11.1 Make 11.2 11.3 11.4 11.5 11.6 Cat 6 UTP Patch Cable, TIA-568C Category-6, LSZH and shall be available is 1/2/3 meters or 4/7/10 feet All patch cords shall conform to Category 6 & conductor shall be stranded 24 AWG or better Shall support network line speeds up to 1 Gbps Shall have RJ-45 connectors with transparent plugs at both the ends All patch cords shall be factory crimped and ETL verified (Report Technical Specifications Page 130
11.7 11.8 required). Patch cords shall support applications such as 155 Mbps ATM, token ring & VOIP. Patch cord shall be made of Low Smoke Zero Halogen and RoHS compliant 12.0 Category 6 UTP PCB based Jack PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 12.1 Make 12.2 12.3 12.4 12.5 PCB based Information Outlet (I/O) RJ45, TIA- 568C Category-6, Termination of Catergory-6 UTP Cable, UL listed (Certificate required) Shall conform to Category-6 as per the EIA/TIA-568C.2 and support network line speeds up to 1 Gbps Shall have RJ-45 type connector with strain relief bend limiting boot for securing IDC contacts from external forces Shall Snap into standard faceplates, surfacemount boxes, consolidation point boxes, and Modular Panels Technical Specifications Page 131
12.6 12.7 Shall be certified by independent labs like ETL/GHMT for compliance to EIA/TIA- 568C.2. (Report ) Shall have minimum 20- Year Extended Product Warranty and system warranty for all the passive products Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 12.8 Shall be RoHS Compliant 13.0 British style shuttered Faceplate PALATANA, TRIPURA Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 13.1 Make 13.2 13.3 13.4 13.5 13.6 Shall be Single Port (RJ45) square plate, dimension as per commercially available modular office furniture Shall have spring shuttered front access for preventing ingress of dust Shall be supplied with Gang Box of the same size by System Integrator or OEM Shall have Write on labels in transparent plastic window along with the plate Shall be able to support variety of jacks UTP and STP Information outlets Technical Specifications Page 132
SECTION 2.10 TECHNICAL SPECIFICATION FOR NETWORK SCANNER 1.0 NETWORK SCANNER DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 2.1 Make 2.2 Scanner type Flatbed, ADF 2.3 Optical Sensor Colour CCD 2.4 Scan Option B&W, Color 2.5 2.6 Scan resolution, optical Duty cycle (daily) Minimum 600 dpi x 600 dpi B/W and Color Minimum duty cycle: 500 pages daily 2.7 Bit depth Minimum 24-bit 2.8 2.9 Multifeed detection Scan size (flatbed) 2.10 Media Support 2.11 Scan file format 2.12 2.13 2.14 Automatic document feeder capacity Automatic document feeder scan speed Scanning options (ADF) Yes, length 215 x 297 mm Minimum Paper (plain, inkjet, photo), envelopes, cards (index, greeting), 3-D objects PDF, searchable PDF, JPG, BMP, TIFF, compressed TIFF, TXT, HTML, RTF, FPX, PNG, PCX, GIF 100 sheets 20 ppm 20 ipm Minimum One-Side, Two-sided (Automatic Duplex) Technical Specifications Page 133
2.15 Scan size (ADF) 216 x 356 mm Minimum 2.16 2.17 Connectivity Option Operating System Support Ethernet, Hi-Speed USB 2.0 Microsoft Windows XP/Vista/7/8 (Home/Professional/Professional x64) 2.18 Warranty 5 Years On-Site OEM 2.19 Number of scanner required 1 Technical Specifications Page 134
SECTION 2.11 TECHNICAL SPECIFICATION FOR LINUX OPERATING SYSTEM 1.0 LINUX OPERATING SYSTEM 1.1 1.2 1.3 Parameter O.S. (Operating System) Specifications Compliance (Y / N) for OS Specifications Details / Remarks All the servers offered for SAP application and Database deployment should be licensed version of LINUX based and the O.S. specifications are as follows: The operating system should support multiple hardware architectures i.e. X86, X86_64, etc. which will allow to have a scalable platform with improved quality. The operating system (including all variants) should have been certified on hardware from leading system vendors. Operating system should also include upgrades, updates and web & telephonic support from OS vendor. OS should have predictive product roadmap The product should have Product Life Cycle of 10 years Should have FIPS-140 Validation government security standard used for accrediting cryptographic modules The source code of the OS should be freely available from the OEM The enterprise grade OS should support the essential network services like Directory Features Services(LDAP V3), DNS, DHCP, Radius, Web Server, Application Server, Cluster Services (High Availability and Fail Over Support), Load Balancer, with virtualization support. OS must support NFS IPV6, multi queue network drivers Must support RAID 5 to RAID 6 restripe kernel Dynamic power adjustment to PCIe Technical Specifications Page 135
1.4 Parameter O.S. (Operating System) Specifications & SATA via Aspm/alpm Should have minimum of 2.6.32 kernel and POSIX compliant Tickles Kernel and APCI 4.0 Infiniband and RDS support Support of large files and file systems on a single host using XFS OS should support Fibre Channel over Ethernet (FCoE) The OS should have processor, CPU, I/O controller & Network ceiling enforcement (Cgroups) Should support mandatory access control for file system, processes & users The OS should support of Security Enhanced features and be capable of managing public key infrastructure (PKI) Indict languages (Unicode) support within OS Should support System Security Services Daemon which manages communication with centralised identity and authentication stores, predictable caching for network accounts, handle multiple domains of user data and authentication Should support Advanced RAS (Reliability, Availability and Serviceability features: I. Physical Memory hot add II. Memory demand and patrol scrubbing (also known as HW Poison) III. Advanced Error Reporting IV. (AER) for PCIe Devices CPU logical on-lining / offlining (Detailed RAS features required are described at the end of this section) Should support Security features like Mandatory Access Control for OS level security hardening Should have Identity Management server for features like SSO, auditing, logging & should also Compliance (Y / N) for OS Specifications Details / Remarks Technical Specifications Page 136
1.5 1.7 1.8 Parameter High Availability Cluster File System Network Load Balancer O.S. (Operating System) Specifications have graphical admin control OS should have certification for business application like SAP where features like: I. Support for high performance, like SAP Business applications in both physical and virtual environments II. Optimised code to ensure that SAP products provide many fold performance improvements III. SAP problem resolution by IOS vendor OS should support High Availability (HA) of applications in its environment HA should support data integrity when one cluster node takes over control of a service from another cluster node. The faulty node is stopped using a method called fencing that prevents data corruption HA module should be also able to support virtual machines (VMs) & application inside the VM Should support cluster file system for application in its environment Cluster file system should be able to access common storage devices across network for multiple read / write operations Cluster file system should be portable operating system interface for UNIX (POSIX) compliant file system Each member of the cluster thus has direct access to the same storage device and all cluster nodes access the same set of files Should support network load balancer functionality Compliance (Y / N) for OS Specifications Details / Remarks Technical Specifications Page 137
SECTION 2.12 TECHNICAL SPECIFICATION FOR BACKUP SOFTWARE 1.0 BACKUP SOFTWARE - DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 1.2 1.3 1.4 1.5 1.6 Software Name and Version Number The Backup Solution should be available on various OS platforms such as Windows, UNIX and Linux platforms. Backup solution shall support industry leading cluster solution such as MSCS, MC Service Guard, Veritas Cluster etc. Backup solution shall have same GUI across heterogeneous platform to ensure easy administration. The backup solution shall have inbuilt Java/ Web Based GUI for centralised management of backup domain. The backup solution should allow System Integrator to provide details Technical Specifications Page 138
1.7 1.8 1.9 1.10 1.11 creation of additional backup copies, run concurrently with primary backup, within the same Library or over the network to another tape library/standalone drive of different format medium (e.g. Ultrium to SDLT etc..) to allow easy vaulting operation The backup solution should support demultiplexing/tape copy and staging of data cartridge to another set of cartridge for selective set of data for faster restores operation to client/servers. The backup solution should allow creating tape clone facility after the backup process. The Backup Solution should have in-built calendar based scheduling system and supports Clustering the Backup Server and Media Server on Windows and Linux. The solution should also supports Disk staging. System Integrator need to provide the online licenses and agents for Production setup, existing applications and development setup as per the requirement of this Technical Specifications Page 139
1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 RFP System Integrator to provide the licenses and agents to take the backup of the OS mentioned in the RFP with 10% additional licenses The Backup Solution should have in-built media management and supports cross platform Device & Media sharing in SAN environment. It provides a centralised scratch pool thus ensuring backups never fail for media Backup Software shall support Synthetic backup / Virtual full backups so that Full backup can be constructed directly from the disk based incremental backups. Backup Software is able to rebuild the Backup Database/Catalog from tapes in the event of catalog loss/corruption. The Backup Software shall offer OPEN File Support for windows. The backup solution shall provide granularity of single file restore. Backup Solution shall be able to copy data across firewall. Backup Solution shall support backup & restore over LAN Technical Specifications Page 140
1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 The Backup Solution has certified Hot- Online backup solution for different type of Databases such as Oracle, MS SQL, Sybase, Exchange etc. The backup solution shall support granular recovery of Virtual Partitions, Exchange Server etc. The backup software should give the option to allow de-duplication to be done either on the application server or on backup server or at the target device The backup solution should support searching data using either structured and unstructured information The backup software should support contextual search based on meaning The backup software should be IPv6 compliant The backup solution must support at least AES 256-bit encryption capabilities. The backup solution shall be configured in such a fashion that no extra license for client and media servers is required while moving from LAN to SAN based backup. The backup solution shall be configured Technical Specifications Page 141
1.29 1.30 with adequate client and media licenses for LAN based backup. The backup solution must not require separate licensing when upgrading from a lower end server (1-2 CPU based) to higher end server (4-and above CPU based server). System Integrator need to supply the required backup agents and licenses for all the servers as per application requirements and solution offered by System Integrator. Technical Specifications Page 142
SECTION 2.13 TECHNICAL SPECIFICATION FOR ENTERPRISE MANAGEMENT SYSTEM (EMS) SOFTWARE 1.0 EMS SOFTWARE- DELHI 1.1 NETWORK MANAGEMENT Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1.1 Software Name and Version Number 1.1.2 Number of devices/nodes to be managed Minimum 1000 nodes / devices 1.1.3 System Integrator need to supply the media and licenses. 1.1.4 The Network management System (NMS) shall be able to monitor and manage the Network devices like Routers, switches, Wireless equipments and other SNMP based devices. 1.1.5 Must provide a web based user interface across the managed components. 1.1.6 Should have 100% scalability without major architectural changes 1.1.7 Should support nearly Technical Specifications Page 143
continuous discovery process. 1.1.8 NMS must provide functionality to discover network devices 1.1.9 Should have the capability to produce customizable add hoc reports. 1.1.10 Automatic discovery of IP devices on the network. 1.1.11 NMS should detect the SNMP compliant network devices on the network and manage them. 1.1.12 Ability to present graphical view of the LAN and WAN network. 1.1.13 NMS should provide the capability to role based view the network topology. 1.1.14 Should provide the ability to define user roles and node / interface grouping features. 1.1.15 It should offer fault management for analysis and alert of incoming and provide capability to alert of the events, fault should be colour-coded on the GUI based on severity. 1.1.16 It must filter, correlate & process, the events that are created daily from network devices 1.1.17 The NMS should provide very powerful event correlation engine, which should be rulesbased and work in conjunction with event management system. It should assist in root cause determination and help prevent flooding of non-relevant console messages Technical Specifications Page 144
1.1.18 Root Cause Analysis Report should be available for the faults. 1.1.19 NMS shall be able to provide secured windows based consoles as well as secured webbased consoles. 1.1.20 The NMS system should support distributed hierarchical architecture. 1.1.21 The system shall support discriminated polling, whereby certain critical interface of routers or switches may be polled more frequently that others. 1.1.22 NMS architecture should be open standard, distributed, scalable, and should support integration with third party tools. 1.1.23 NMS should support ODBC Compliant database 1.1.24 NMS should support monitoring / managing of SNMP v1, SNMPv2C and SNMPv3 based devices. 1.1.25 The product should have web browser interface with user name and Password Authentication. It should be possible to view topology maps, events, reports etc. in full graphical format using standard web browser that support Java interfaces. 1.1.26 The NMS should provide information regarding capacity utilization and error statistics for WAN links. 1.1.27 The NMS should trigger automated and operator- initiated Technical Specifications Page 145
responses and actions based on incoming events / traps. 1.1.28 Should be able to generate and provide web-based reports. 1.1.29 It should be possible to be able to be export data in various formats, for use in capacity planning, statistical analysis, and spreadsheet applications. 1.1.30 Should provide reports on different performance parameters based on real time/near real time and historical reporting. 1.1.31 The system must provide capability to store the collected data in a repository based on an RDBMS. 1.2 SERVER MANAGEMENT Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.2.1 1.2.2 Software Name and Version Number Number of servers to be managed 1.2.3 System Integrator need to propose and supply System Integrator to propose as per the solution and requirement mentioned in the RFP. Technical Specifications Page 146
the licenses to manage the number of servers as per solution and RFP requirement and additional 10% buffer. 1.2.4 This module is primarily used to ensure that the performance of heterogeneous servers and operating systems are being monitored through agent based / agent less on a 24 X 7 basis. The module should have capability that in case of any problem, suitable preventive and corrective actions can be initiated. 1.2.5 It should ensure the availability of the system resources and service independent of the machine location, collect performance data for capacity planning and alert generation of potential problems. 1.2.6 The module should have capability to generate problem summary for a day to show the systems which generated maximum number of exceptions during the previous day along with details on resource utilization, including but not limited to, run queue, CPU utilization, memory utilization, swap utilization, page outs per second and number of processes, exception details and grade of service for these systems. 1.2.7 The module should have capability to provide online and historical graphs and reports of Technical Specifications Page 147
system health. It should provide for a web-based health console display that includes robust and flexible graphing capabilities for multiple metrics simultaneously, provides comparative and trending analysis. 1.2.8 ESM should be able to run OS flavours such as Windows, HP-UX, IBM AIX, Sun Solaris, Red Hat Enterprise Linux, Suse Linux Enterprise Server, Debian Linux 1.2.9 Service discovery 1.2.10 Should provide comprehensive event management, proactive performance monitoring, automated alerting, reporting and graphing for operating systems, middleware and applications. 1.2.11 Should a web browser interface that can be accessed from anywhere using industry-standard web browsers. 1.2.12 Each operator should be provided with a specific user role based view, restricting what they see and what they can do within the managed environment. 1.2.13 Integrated scheduled and operational maintenance modes for managed systems to prevent operations staff from seeing false alarms during authorized outages 1.2.14 Flexible architectures including support for high availability cluster architectures (Microsoft Cluster Server) and disaster tolerant Technical Specifications Page 148
distributed architectures with multiple Management servers (failover, competence centers, etc.) 1.2.15 Should use intelligent filtering, duplicate suppression and correlation, the agents manage by exception only forwarding actionable events to the Management server. 1.2.16 Should support for monitoring Data Centre technologies such as virtualization and clusters 1.2.17 Auditing and logging of operator activities 1.2.18 Accelerate root cause analysis through advanced analytics and problem resolution 1.2.19 ESM must filter, correlate, process, and respond to the thousands of events that are created daily from systems, databases, and applications. 1.2.20 ESM must provide a centralized point of control that offers operations staff close and efficient control of events happening across the managed systems, creating a "mission control" centre for the distributed environment. 1.2.21 ESM must include very powerful event management and correlation services technology, providing correlation capabilities on the intelligent agents in addition to the central manager station 1.2.22 Secured communication between Management Technical Specifications Page 149
server and Managed nodes 1.2.23 ESM must support the backup server concept, which enables switching management responsibility from one management centre to another in case of system failure. This eliminates single points of failure in the management system. 1.2.24 ESM should notify through alerts, events, email alerts, SMS etc 1.2.25 Automated policy deployment with detailed, intelligent monitoring 1.2.26 Predefined policies that include event log, service monitoring, metric collection, thresholds, alarms with meaningful message text, instruction text, operator / automatic actions / linked graphs, duplicate message suppression 1.2.27 Predefined graphs/reports 1.2.28 Predefined tools (for troubleshooting) 1.2.29 Web Application Servers 1.2.30 Out of the box reporting templates available for performance and availability of managed servers 1.2.31 Should provide reports that can prove IT service quality levels, such as application response times and server resource consumption 1.2.32 Reports should be accessible via web browser 1.2.33 Reports can be Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 150
scheduled to publish automatically or they can be produced on demand 1.2.34 Reports can be applied to all systems, to a group of systems, to a customer group of systems, or to a single system. 1.2.35 Should be possible to send reports via email from the GUI 1.2.36 Automated report generation and publishing 1.3 DESKTOP MANAGEMENT Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks Software Name and 1.3.1 Version Number Software should maintain minimum 200 1.3.2 desktops which could spread across multiple locations. 1.3.3 The solution should support maintains the status of the desktop with respect to software installed and OS, patch levels as per organization policy. 1.3.4 The solution should include inventory management (hardware and software inventory), software management Technical Specifications Page 151
(push and pull), patch management, usage management and OS management. 1.3.5 The software should have a single agent which is capable of inventory as well as software management (software pull / push) and including patch management. 1.3.6 The software should be capable of bandwidth throttling and other features which use the network efficiently. Please describe the features your software offers for efficient usage of network bandwidth. 1.3.7 The software should support MS SQL Server 1.3.8 Solution should support multiple levels of administrative delegation. The system should be able to define multiple levels of administrative domains and regions so that each administrator is assigned certain resources for which they are responsible for managing the application from the business perspective. 1.3.9 The solution should support a distributed architecture with centralized or distributed management capabilities. 1.3.10 The Software should support multi-tiered architecture as well as bandwidth optimization techniques to optimize the WAN usage and for faster deployment of software. Technical Specifications Page 152
1.3.11 The agents required for the solution should be deployed on all the desktops to be monitored 1.3.12 It should provide out-ofthe-box reporting capabilities for general reporting requirements in the form of printable table views, graphical views, explorer-type views, and list views. 1.3.13 The solution should combine advanced hardware and software scanning technology with efficient and open database design, and provide comprehensive information needed to manage IT assets 1.3.14 The software should have capability to discover software and hardware inventory across all computing devices enterprise-wide and have accurate, upto-date IT asset information to more effectively meet IT project planning, auditing, compliance reporting and configuration management needs. 1.3.15 The software should collect hardware and software inventory across multiple platforms. It should have the capability to collect information from every desktops and notebooks. 1.3.16 It should have the capability to be able to discover the hardware and the software configurations of elements, including but Technical Specifications Page 153
not limited to, Processor type, Memory, Hard Disk, I/O ports, I/O cards, Operating System, etc. 1.3.17 It should integrate with help desks and other system management tools for seamless operations and CMDB updates. 1.3.18 It should support policybased model that allows IT administrators to efficiently and concisely define entitlements, controlling the deployment of software and content to PCs, authorized users and subscribers. 1.3.19 The software should ensure that subsequent changes to policies and entitlements cause software and content to be automatically installed, changed or deinstalled for all affected users and PCs. 1.3.20 The agents should store a local copy of the inventory for comparison on next scan and send only the differential data on inventory scan. 1.3.21 The module should have capability to track software usage throughout the Microsoft windows environment so as to effectively manage the risk of unauthorized usage or under-licensing of software. 1.3.22 The software should be effective, reliable and scalable for software delivery and distribution, particularly for patch distribution and management. Technical Specifications Page 154
1.3.23 It should provide increased flexibility to define and initiate the update by push or pull interfaces and should support Multicast distribution. 1.3.24 It should provide facility to increase efficiency of network bandwidth usage by using intelligent network conserving capabilities 1.3.25 The software should accelerate deployment and automate the maintenance of applications and content, personalized for individual end users or groups as prescribed by policies. 1.3.26 The software should automatically prepare an application package and ensure deployment compliance 1.3.27 The software should have capabilities to target individual PCs, workgroups or entire populations of PCs for deployment and maintenance of software and content according to policies. 1.3.28 The module should have capability to track the software that is deployed on a PC 1.3.29 It should have the capability to automatically repair damaged software on any managed desktop. 1.3.30 Any and all software on the managed desktops should be automatically discovered and reported. It should be able to capture inventory information from various Technical Specifications Page 155
sources on the desktop including Add/Remove programs, WBEM, Registry, etc. 1.3.31 Inventory reports should be available to be viewed over the Web and should be able to be extracted in various formats. 1.3.32 It should be able to collect WBEM information which provides a vast repository of inventory. It should be capable of using multiple collection techniques for full file, path and registry information scanning. 1.3.33 Application Management 1.3.34 The software maintenance should be policy-based and not list-and-script i.e. The software configuration on the managed desktops and servers should be maintained automatically based on policies set in the central configuration server or Active Directory server. 1.3.35 It should allow integration with Active Directory server such that changes to policies in the AD are automatically reflected and enforced in the configuration management software as well. 1.3.36 The solution should provide capability of enabling deployment of applications along with all the pre-requisites. 1.3.37 It should have a built-in reporting system that provides extensive reports of hardware and Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 156
software inventory. 1.3.38 It should allow you to group and sort the resulted based on more than one field. 1.3.39 It should have the provision to summaries the report in terms of spread of various values like I3-4 machines, I5-6 machines etc. or give a total count of machines in the report 1.3.40 The administrator should have the flexibility to scheduling each and every module independently viz. hardware, software, template inventory, reporting etc. 1.3.41 Configuration Management components should be designed for flexibility during deployment and ongoing operations. They could all be installed on one server or the components can be distributed across various servers. Virtually any component could be put almost anywhere in the network. Each component should be designed to have minimal impact on the computers on which it resides. 1.3.42 Patch Management 1.3.43 The Patch Management module should manage the entire lifecycle of patches, hot-fixes, updates and service packs from automatic discovery, download and collection, through testing, conflict analysis, and vulnerability Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 157
assessment, to policybased targeting and deployment and ongoing management to ensure that patches stay applied as prescribed by policy. 1.3.44 The patch management module should be able to deliver updates on the test computers to check conflicts 1.3.45 The Patch management module should be able to automatically download patches from the vendor support site, automatically package the patches and deploy the patches based on policy defined. 1.3.46 The Patch Management software should automatically ensure the maintenance of all the deployed patches. I.e. if a certain patch is deleted or de-installed from any desktop by the user, it should automatically be repaired / re-installed without the intervention of the Administrator. 1.3.47 The Patch Management module should support automatic download and deployment of patches for MS Windows platforms 1.4 MANAGEMENT AND MONITORING OF VIRTUALIZED SERVERS Feature / Specifications Minimum Specification Compliance Proposed Capacity / Details / Remarks Technical Specifications Page 158
(Y / N) for minimum specifications Hardware ( Bidder can propose technically superior components) The Solution should be able to monitor User Virtual Resources 1.4.1 independent of the platform & solution/service they are running The Solution should be able to monitor key performance 1.4.2 characteristics of the virtual resource (OS, RDBMS, Memory, Storage, Network etc.) 1.4.3 The Solution should have the mechanism to store the historical data for problem diagnosis, trend and analysis 1.4.4 Solution should monitor near real time performance of critical devices like bandwidth \ cpu utilization using management console 1.4.5 The proposed server monitoring solution should detect threshold violations in real-time, sending an alert to the administrator or group of them. 1.4.6 The monitoring tool should support database Performance agents for Performance reporting of standard RDBMs. 1.4.7 The proposed solution should be able to proactively monitor all real user transactions. 1.4.8 Real time end User response monitoring & application Performance Technical Specifications Page 159
diagnostic should be tightly integrated out of the box without a need To perform extensive customizations. 1.4.9 The proposed solution should allow access to performance data both using a Graphical user interface (GUI) and over the web (web based access) and provide ability to monitor performance of applications up to the method level of execution (Java/.Net method) 24x7 in production environments with negligible impact on monitored application. 1.4.10 The proposed tool should be able To monitor various operating system parameters such as processors, memory, files, processes, file systems, etc. where applicable, using light footprint agents on the servers To be monitored. 1.4.11 The proposed tool should support operating system monitoring for various platforms including Windows, UNIX and Linux. 1.4.12 The proposed solution should be able to proactively monitor all real user transactions; detect failed transactions and help diagnosis of problems that affect user experience and prevent completion of critical business processes 1.4.13 The proposed solution must be able To provide Technical Specifications Page 160
Analysis of all problems and find Root-cause for problems showing the problematic areas within the application infrastructure 1.4.14 The solution should provide Heterogeneous Virtualization Management from One Console. 1.4.15 The solution should have the capability to manage SNMP version 1, 2 & 3 devices in High availability mode 1.4.16 The solution should allow administrator to graphically represent creating own dashboards with multiple components. 1.4.17 The solution should have network port level granularity 1.4.18 The solution should be able to integrate with other solution to raise tickets and for automotive\remediate actions 1.4.19 The solutions should have Virtualization support for virtual machines running on Microsoft Hyper-V, Citrix Zen Servers and VMware ESX. 1.4.20 The solution should provide Administrator Console as a central work area for performing resource tuning. Resource settings can be changed on virtual machines without interrupting workloads and virtual machines can be migrated from one host to another to optimize physical resources. Technical Specifications Page 161
1.4.21 The solution should have capability to integrate with patch management for intelligent patching of the hosts. 1.4.22 The solution should provide capability to integrate with leading management tools to enable interoperability across the datacenter. 1.4.23 The proposed helpdesk solution must provide flexibility of logging, viewing, updating and closing incident manually. 1.4.24 The proposed helpdesk solution must support ITIL processes like request Management, problem Management, configuration Management and change order Management with outof-the-box templates for various ITIL Service support processes. 1.4.25 Each escalation policy must allow easy definition on multiple escalation levels and notification to different personnel via window GUI/console. 1.4.26 The proposed helpdesk solution must support tracking of SLA (Service level agreements) for call requests within the help desk. 1.4.27 It should support remote Management for end- User & allow analysts To do the desktop sharing for any system located anywhere, just connected To internet. 1.4.28 The Solution should provide a Knowledge base to store history of Technical Specifications Page 162
useful incident resolution 1.4.29 The Solution should have capabilities to create workflows to automate common admin challenges 1.4.30 The Solution should offer usage report by tenant, by region, or by Virtual Machine reporting usage of memory consumption, CPU consumption, disk consumption, Network & Disk IO 1.4.31 The Solution should be able to send the reports through e-mail to predefined user with pre-defined interval 1.4.32 The user must be able to generate reports from the long term database based on specific thresholds defined by the user where the threshold can be compared to rate, utilization or volume of every monitored interface as a filter for inclusion in the report. 1.4.33 The overview page must include an email function that provides a GUI driven method for emailing the page in PDF format as well as for scheduling the email of this page at regular intervals without user intervention to one or more recipients. 1.5 SERVICE DESK Technical Specifications Page 163
Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks Software Name and 1.5.1 Version Number Update & close jobs / 1.5.2 tickets 1.5.3 Place jobs / tickets on Hold 1.5.4 Ticket auditing facility should provide by the Service Desk tool. (Will give a history of the ticket) 1.5.5 Transfer & assign the jobs tickets to other location help desk person 1.5.6 Assign priorities to Jobs / Tickets. (This should assign as per the seniority & aggraded SLA model) 1.5.7 Specify & track target job completion status based on various factors as, Dates, Priority etc. 1.5.8 Services desk tool should have capability to categories the jobs as per the structure of a problem ex: Server related problem should assign to hardware team 1.5.9 Service desk should have a SLA mapping / monitoring & tracking feature. (When a ticket is raised, Target Helpdesk calculates the most relevant service level agreement according to the contact and any asset identified). 1.5.10 Service desk should record time duration spent on each ticket Technical Specifications Page 164
1.5.11 Service desk should be able to provide role base access to users 1.5.12 Service desk module should have its own database (CMDB) which will incorporate as Knowledge base search (Kind of FAQ s for L1 person) 1.5.13 Service desk tool has to have inbuilt Escalation Matrix which help for the notification purpose to operators & users about their tickets 1.5.14 The tool should maintain Asset Information 1.5.15 The tool should have a facility to link files (error, log files) to help desk tickets. 1.5.16 License provided Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 1.6 The Enterprise Management System should provide a robust reporting system with all the standard reports and User can define their own reports and dashboards without having any additional cost implication to OTPC. OTPC shall not have any commercial implication for any kind of customizations and developments required to develop the customized reports as per the requirement of OTPC. Technical Specifications Page 165
SECTION 2.14 TECHNICAL SPECIFICATION FOR VIRTUALIZATION SOFTWARE (DELHI & PALATANA) 1.0 VIRTUALIZATION SOFTWARE Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 Software Name and Version Number 1.2 Number of physical CPUs per license. 1.3 Number of Managed Unlimited Operating System Environment per license 1.4 Anti-virus / Anti-malware protection 1.5 Database server licenses for management databases 1.6 Support for enterprise operations monitoring and management of hosts, guest VMs, and application workloads running within VMs from day 1 1.7 Support for private cloud management capabilities 1.8 Web based management console 1.9 Logical processors per 320 host 1.10 Physical RAM per host 4 TB 1 Software that supports more than 1 CPU per license may be preferred Technical Specifications Page 166
1.11 Active VMs per host 512 1.12 Virtual CPUs per VM 64 1.13 Host adjust virtual CPU resources to VM 1.14 Virtual RAM per VM 1 TB 1.15 Hot-add virtual RAM to VM 1.16 Dynamic Memory Management 1.17 Guest NUMA (Non- Uniform Memory Access) support 1.18 Physical hosts per 32 cluster 1.19 VMs per cluster 4000 1.20 Virtual Machine 32 snapshots 1.21 Integrated application load balancing for scaling-out application tiers 1.22 Bare metal deployment of new Hypervisor hosts and clusters 1.23 Virtualization of USB devices 1.24 Virtualization of serial ports 1.25 Boot from flash 1.26 Boot from SAN 1.27 Live migration of running VMs 1.28 Live migration of running VMs without shared storage between hosts 1.29 Highly available VMs 1.30 Failover Prioritization of Highly Available VMs 1.31 Affinity rules for highly available VMs 1.32 Cluster aware updating for orchestrated patch management of hosts 1.33 Guest OS application monitoring for highly available VMs 1.34 VM guest clustering via shared virtual hard disk Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 167
files 1.35 Intelligent placement of new VM workloads 1.36 Automated load balancing of VM workloads across hosts 1.37 Power optimization of hosts when load balancing VMs 1.38 Backup of VMs and Applications 1.39 Site-to-site asynchronous VM replication 1.40 Virtual SCSI hard disks 60 per VM 1.41 Virtual Hard disk size 62 1.42 Boot VM from virtual SCSI disks 1.43 Hot add virtual SCSI VM storage for running VMs 1.44 Hot-Expand virtual SCSI hard disks for running VMs 1.45 Storage QoS 1.46 Virtual Fibre Channels to VMs 1.47 Live migration of virtual storage for running VMs 1.48 Flash based read cache 1.49 Storage Via iscsi, NFS, Fibre Channel and SMB 3.0 1.50 Storage Multipathing 1.51 VM storage provisioning based on storage classification 1.52 Dynamically balance and re-balance load based on demands 1.53 Distributed switches across hosts 1.54 NIC Teaming 1.55 Private VLANs (PVLAN) 1.56 Virtual port ACLs 1.57 Trunk mode to VMs 1.58 Port monitoring Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 168
1.59 Port mirroring 1.60 Dynamic Virtual Machine queue 1.61 Single Root IO Virtualization (SR-IOV) 1.62 Virtual Receive Side Scaling (Virtual RSS) 1.63 Network Quality of Service 1.64 Network virtualization / Software Defined Networking (SDN) 1.65 The Virtualization software should be based on hypervisor technology which sits directly on top of Hardware (Bare Metal) 1.66 The Solution should be able to run various operating systems like windows client, windows server, linux. 1.67 The Solution should have the capability for creating Virtual Machines templates to provision new servers 1.68 The Solution should continuously monitor utilization across Virtual Machines and should intelligently allocate available resources among the Virtual Machines 1.69 The Solution should allow for taking snapshots of the Virtual Machines to be able to revert back to an older state, if required 1.70 The Solution should be able to dynamically allocate and balance computing capacity across collections of hardware resources of one physical box aggregated into one unified resource pool Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 169
1.71 The Solution should provide support for cluster services between Virtual Machines 1.72 The Solution should deliver above listed Hypervisor capabilities using standard server infrastructure from at least HP, DELL, IBM, Cisco and Oracle 1.73 The Solution should allow Virtual Machines consume RAM dynamically in such a way that if some of the VMs in Physical machine are not utilizing the RAM, this RAM can be utilized by some other VM in the same physical machine which has a requirement 1.74 The Solution should be able to use power saving features like, in case of off-peak hours, if not all servers are required to be powered on, the solution should shut down to save power. There also need to be reporting associated with this capability. 1.75 The Cloud Automation framework should provide capability for Role based Access for performing specific tasks 1.76 The Solution should have the ability to develop highly customized workflows and easy user interface. 1.77 The Orchestration Solution should be open and interoperable and has rich integration capabilities that support interfaces from command line interface and web services Technical Specifications Page 170
1.78 The Solution should be capable of extending entire functionality to virtual environment utilizing existing components of SDC such as Enterprise Management System (EMS) 1.79 The Solution should provide support for cluster services between Virtual Machines 1.80 The Solution should have the capability for moving Virtual Machines from Primary site to the Secondary site. 1.81 The Solution must offer Identity, Authentication and Role based access to User Departments Infrastructure - Machines (Virtual or Physical), 1.82 The Solution must offer Policy based administration by putting User Departments Machines (Virtual or Physical) in logical groups and apply relevant policies 1.83 The Solution should have the ability to not just enforce policies but also track and report non-conformance to access 1.84 The Solution should automate provisioning of new and changes to existing infrastructure (Virtual, Physical, Application or Common Services) with approvals 1.85 The Solution should have capabilities to create workflows to automate common admin challenges 1.86 The Solution should Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 171
have the ability to develop highly customized workflows and easy user interface. Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 172
SECTION 2.15 TECHNICAL SPECIFICATION FOR E-MAIL GATEWAY ANTI-SPAM & ANTIVIRUS SOFTWARE 1.0 E-MAIL GATEWAY ANTI-SPAM & ANTIVIRUS SOFTWARE 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 Feature / Specifications Software Make and Version Should provide gateway level antis-spam and email antivirus feature Should protect the messaging system from the spam and phishing Antivirus engine should blocks malware and spyware attacks Should be compatible with leading messaging systems Should scan the emails for the virus and clean the same or take appropriate actions Should scan emails and attachments Email Gateway security for Inbound and Outbound email Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks Technical Specifications Page 173
based threats such as spam, viruses, bounce attack prevention, zero day attacks, sender authentication etc The solution should have 1.9 aliasing and masquerading functionality The solution should drop invalid recipients 1.10 from a given message and prevent against Directory Harvest Attacks The solution should provide 1.11 visibility to administrators in to the email delivery queue The solution should have an 1.12 extensive array of millions of decoy email addresses (honey pots) The solution should support 1.13 mechanism to block the bounce attacks The solution should provide protection against 1.14 mail bomb attacks by specifying maximum size and scanning depth levels 1.15 Support detect phishing attacks Should have web 1.16 based management console 1.17 System Integrator Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 174
1.18 1.19 needs to propose and supply the licenses for protecting 100 mailboxes. System Integrator need to propose and configure the Anti-spam and antivirus solution to avoid the single point of failure System Integrator needs to supply the software media. Technical Specifications Page 175
SECTION 2.16 TECHNICAL SPECIFICATION FOR DATA CENTRE INFRASTRUCTURE - DELHI 1.0 INTEGRATED RACK WITH UPS, PRECISION AC, CCTV SYSTEM AND MONITORING SOLUTION Feature / Specifications 1.1 Intelligent integrated / inbuilt infrastructure 1.2 Infrastructure shall be flexible, adaptable, controllable 1.3 Integrated / inbuilt infrastructure shall have redundant components and concurrently maintainable 1.4 Integrated infrastructure shall include internal redundant or backup PDU of type IEC19/13 1.5 Integrated infrastructure shall include redundant precision air conditioning 1.6 Integrated infrastructure shall include fire detection and alarm system 1.7 Integrated infrastructure shall include Water Leak detection system 1.8 Integrated infrastructure shall include temperature & humidity sensor Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Equipment ( Bidder can propose technically superior components) Details / Remarks Technical Specifications Page 176
1.9 Integrated infrastructure shall include motion sensor 1.10 Integrated infrastructure shall include redundant UPS in N+1 topology 1.11 Integrated infrastructure shall have foot print approximately 1600 mm x 1000 mm x 2000 mm (W x D x H), shall have minimum 50 U usable space 1.12 Integrated infrastructure shall provide cold aisle & hot aisle 1.13 Cabinet shall be fire rated 1.14 Cabinet shall have insulation, remote management and single point of service features 1.15 Monitoring System with capability for E- mail alerts 1.16 Integrated infrastructure shall have provision to add an extra rack in future 1.17 UPS (Uninterrupted Power Supply) System 1.17.1 2 X 10 KVA rack mount UPS 1.17.2 UPS Frame Size 30 KVA 1.17.3 Power Factor 0.9 1.17.4 Efficiency More than 94% 1.17.5 Backup Time on full 60 Minutes load 1.17.6 UPS should be mounted inside the cabinet only 1.17.7 Battery Bank should be place outside the cabinet 1.17.8 Battery bank connection using Nyvin cables and providing safety Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 177
barriers for all busbars and cable connection leads on battery bank 1.17.9 Batteries SMF Batteries 1.17.10 Input Dual Input ( Mains + Bypass Input) Bypass may be disabled 1.17.11 Input Voltage 415 V ± 15%, 3 Phase, 4 wire 1.17.12 Input Frequency 50-60 Hz +/- 5 Hz ( auto sensing ) 1.17.13 Output voltage 415 V ±1%, 3 Phase, 4 wire 1.17.14 Output Frequency 50 Hz ±1% for all condition of inputs 1.17.15 Output Wave form Pure sine wave 1.17.16 Output Voltage Less than 3% Distortion 1.17.17 DC Ripple Less than 1.5% 1.17.18 DC Voltage +/- 1% Regulation 1.17.19 Crest Factor Designed to handle unbalanced and 100% non-linear loads 1.17.20 Overload Capacity/rating 125% for 5 minutes, 150% for 60 seconds 1.17.21 On line Transfer Time Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Zero ( line fails or recovers ) 1.17.22 UPS fault Transfer Time < 4 ms ( Auto by pass activation or recovers ) 1.17.23 Bypass Automatic internal 1.17.24 Surge Protection Against Transient Voltage Surge 1.17.25 Rectifier 3 Phase, IGBT based rectifier. 1.17.26 Communication & Management: Web/SNMP/Telnet management, Pre- Installed Smart Slot Cards 1.17.27 Static Bypass. Option of disables shall be provided 1.17.28 Operating 0 to 40 C Temperature 1.17.29 Relative humidity 0 95% 1.17.30 Noise level at full load Less than 65dBA at 1mtr distance 1.17.31 Neutral at output side as well. Technical Specifications Page 178
1.17.32 Metering & Alarm Display on Front LCD Panel. 1.17.33 Alarm Messages Input- abnormal, voltage; Battery- low, over voltage, discharging, breaker open/trip; Outputunder/over voltage, overload, over temp; Bypass-voltage abnormal, frequency abnormal. 1.17.34 UPS Output distribution breakers 1.17.35 Double Conversion & IGBT technology 1.17.36 Full IGBT rectifier / Battery Charger 1.17.37 IGBT based Inverter 1.17.38 Power Distribution Panels 1.17.39 Remote Emergency Power off 1.17.40 Facility for remote viewing 1.17.41 Upgrade of the system hardware and associated other software during warranty period should be supplied free of charge Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Minimum 2 no. of 100A, 4P, MCB and 2 no. of 40A, 4P MCBs shall be required 1.18 Precision Air-Conditioning (AC) System 1.18.1 Redundant cooling unit in at least N+1 configuration to cater load of maximum 10 KVA 1.18.2 Rack mounted 7 KW DX type Precision cooling system with 5 Star rating 1.18.3 7KW redundant Precision cooling with digital scroll compressors 1.18.4 Designed to operate 24X7 1.18.5 Temperature Control Technical Specifications Page 179
1.18.6 Filtration 1.18.7 Cooling unit should be rack mounted only 1.18.8 Cold air shall be supplied to the cold aisle containment and the hot air shall be taken from the hot aisle containment of the integrated cabinet 1.19 Monitoring Solution 1.19.1 Monitoring Functional Unit shall support following functions: 1.19.2 Status of equipment, environment, temperature, humidity, UPS and Cooling system 1.19.3 Send control commands and setting equipment parameter 1.19.4 Dynamic alarm system 1.19.5 Historical alarms and logs 1.19.6 The unit shall be 19 1U rack mountable 1.19.7 One 10/100 Ethernet port 1.19.8 2 RJ 45 relay ports 1.19.9 Temperature, humidity sensor port 1.19.10 USB Ports 1.19.11 Sensor Ports 1.19.12 Serial Ports 1.19.13 GUI 1.19.14 Reporting Feature 1.19.15 SNMP V2, V3 1.20 Management Software Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 1.20.1 The solution should support UPS, Cooling, Rack Power Distribution, Utility Power Distribution, Switching Power Supply, Door Access Controller 1.20.2 Power Consumption Details Technical Specifications Page 180
1.20.3 Serial Temp & Hum Sensor 1.21 Blanking Panels 1.22 UPS & PAC should be from same OEM and should be rack mount 1.23 Should Provide 5 years onsite comprehensive warranty & maintenance support on 24X7 basis for all the components (UPS & Battery Bank, PAC, Monitoring, Management software) 1.24 Rodent Repellent System 1.25 42 U Rack 2 Nos. 1.26 UPS 2 Nos. 1.27 PAC 2 Nos. 1.28 Monitoring System 1 Lot 1.29 Rodent Repellent 1 Nos. System 1.30 Management Software 1 Nos. 2.0 CIVIL WORK Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Feature / Specifications 2.1 Demolition / Dismantling work Minimum Specification and Quantity Demolition / Dismantling Work including carefully stacking (at customer storing area) of useful materials & disposing off the unserviceable material out of the premises to the nearest municipal dump) etc. complete as per customer direction. Compliance (Y / N) for minimum specifications Proposed Capacity / Equipment ( Bidder can propose technically superior components) Details / Remarks Selected System Integrator will have to make good without any extra payment any damage done during Execution. The Technical Specifications Page 181
System Integrator s are requested in their own interest to inspect the site to assess the nature and quantum of work. 2.2 False flooring work For flooring for the area as per the server room layout (tentative). Access floor systems with a maximum finished floor height of 300 mm from the existing floor level in the Server room. The raised floor shall be provided with Raised Access Flooring system with access floor panel of size (600 x 600) mm and shall be of steel welded construction. The floor panels should be finished with antistatic high pressure laminate with point load 360 kg and uniform distribution load (UDL) 1080 kg/sqm. It should have a suitable pedestal assembly to provide a means of leveling and locking at a selected height. Suction Equipment for lifting tiles (Access Floor Systems Lifting Tools) to be provided as required. Steps also shall be provided for the server room. 2.3 False ceiling work Metal false ceiling system of size 600 x 600 x 5mm laid on Grid System Integrator has to visit the site before to understan d the site condition and actual quantity required before bidding Technical Specifications Page 182
system (Micro lock edge) with 15mm thick T- section (White) having main runner 1200mm x 600mm, cross Tee at suitable height. And having noise reduction co-efficient of 0.5, light reflection over 70%, Relative Humidity 99%, fire performance class 0 /class1. With standard perforation of 2.5 mm dia (16% open space) and fleece with NRC of 0.70 & CAC 36 to be laid on grid system should be provided in the server room 2.4 Gypsum partition work 100mm of Fire rated gypsum partition between UPS and Server room 2.5 Fire rated door High quality galvanized steel and having fire rating up to 2 hours (conforming to BS 476 part 22 and IS 3614 part 2 standards). The doors to be suitable for openings of sizes 4 x7. The main access door shall of two pane type, one pane to be bolted and the other with automatic door closer and locking 2.6 False ceiling works at Toilet area for Cooling unit s outdoor location Re structure / Modification of the existing false ceiling to be done to install the outdoor units of cooling equipment on the ceiling of the toilet If required the modificati on of toilet area false ceiling shall be carried out as per the requireme nts of the outdoor units of the Technical Specifications Page 183
2.7 Any other civil works Any Miscellaneous works to complete the job, which may include closing of wall cut outs with proper sealants, cleaning works etc., Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE cooling equipment as per OEM recommen dation 3.0 ACCESS CONTROL SYSTEM (For one number of door of the server room) Feature / Specifications Minimum Specification 3.1 Reader Controller Compliance (Y / N) for minimum specifications Proposed Capacity / Equipment ( Bidder can propose technically superior components) Details / Remarks 3.2 Access Control Software 3.3 Proximity Card Reader With in-built Self-test & Diagnostic, read range 10-12cm from the front surface and suitable for indoor mounting and. A multi-colour LED on the front surface of the reader with an audio beep tone to indicate that the card has been read. 3.4 Proximity Card Interchangeable, Compatible with all readers, Sequentially numbered passive device without internal battery /any other memory powering /supporting device (such as capacitors, etc.). 3.5 Door Lock with in-built door status sensor Electromagnetic type, suitable for 600 Lbs load Technical Specifications Page 184
with power supply unit. 3.6 Cables PVC insulated Copper armoured FRLS cable as required 3.7 Provide 5years onsite. comprehensive warranty+amc for complete system 3.8 Make & Model 3.9 Reader Controller 1 No. 3.10 Power supply with inbuilt 1 No. battery 30 minutes backup and charger for Controller 3.11 Proximity Card Reader 1 No. 3.12 Proximity Cards with 10 Nos. prints detail of company & card holder 3.13 Electromagnetic Door 01 Nos Lock suitable for 600Lbs load with inbuilt door contact sensor 3.14 Egress Switch 01 No. 3.15 Access Control Software 01 Set. Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 4.0 ELECTRICAL WORK 4.1 4.2 Feature / Specifications UPS Input UPS Output DB for Server room Minimum Specification UPS input shall be taken from the spare feeder of the existing Raw power panel at UPS room. The breaker and cables shall be designed for the total rating of the UPS frame rating Quantity - 02 Nos. of 4Way HSPN DB Each DB shall be with the following specs: Incomer: From UPS Compliance (Y / N) for minimum specifications Proposed Capacity / Equipment ( Bidder can propose technically superior components) Details / Remarks Technical Specifications Page 185
4.3 4.4 4.5 4.6 4.7 4.8 4.9 Raw power for supporting systems Cables Laying & Clamping, Glanding & Termination Earthing Work Lighting Providing & Fixing Cable Trays Other Miscellaneous works Provide 5years onsite comprehensive warranty+amc for complete work Outgoing: To Racks (Industrial sockets) Incomer: 40A, TPN, MCB Output: 12 x 20A SP MCBs Raw power for the cooling shall be taken from the existing Raw power panel / DB in UPS room. Suitable rated FRLS cables shall be installed as per below minimum specs: UPS Input : PVC, CU Cables of 1C / 4C; UPS Output: PVC, CU Cables of 1C / 4C; Rack Input: 3C x CU PVC Cables; Raw power cabling: 4C x Al, XLPE Cables; Wirings: using CU wires. The work shall include all clamping, making gland hole/tapping glanding, inhibiting compound filling, epoxy cable jointing, crimping, and connecting. Installation of required earthing conductors for the equipment and Server room area Suitable lighting with LED light fixtures shall be installed to provide minimum of 500lux inside the server room Suitable size of Perforated cable trays shall be installed for the cables with supports and complete accessories Any other works required to complete the job. Technical Specifications Page 186
5.0 FIRE SUPRESSION SYSTEM Feature / Specifications Minimum Specification 5.1 System The system discharge time shall be 10 seconds or less, in accordance with NFPA Standard 2001. The suppression sub-system shall provide high-speed release of Fire Protection Fluid based on the concept of total flooding fire protection for enclosed areas. Compliance (Y / N) for minimum specifications Proposed Capacity / Equipmen t ( Bidder can propose technicall y superior compone nts) Details / Remarks The installation and commissioning of Fire Suppression system NOVEC1230 should be carried out by authorized/cert ified vendor of the principal manufacturer. 5.2 System Cylinder & Valve Assembly Seamless Cylinder, UL listed and approved by Chief Controller of Explosives, Government of India. Welded cylinders will not be acceptable. 5.3 Fire Suppression Agent NOVEC 1230 5.4 Gas Release Panel Microprocessor Based with Auto/Manual Selector Switch and inbuilt battery 30 minutes backup with charger The System Integrator should produce a NOC from the CCOE, Government of India for the storage containers against the cylinder identification nos. punched on them. The Fire Suppression System shall be integrated with Fire Alarm Technical Specifications Page 187
5.5 Fire Suppression piping Seamless Sch 40 ASTM 106 gr B piping with fitting suitable for 3000psi, rigid supports with angles, 2 coats of Zinc primer & 3 coats of P.O. red paint, 5.6 Cables PVC insulated Copper armoured FRLS cable. 5.7 Fire Suppression Novec Storage Tank of required capacity & valve assembly, CCOE approved, With all required complete accessories 5.8 Provide 5 years onsite comprehensive warranty+amc for complete system 5.9 Make & Model Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE detection system with provision for both pre-alarm and automatic agent release. 1 Lot For Server Room. System Integrator should visit the site and understand the available space. 6.0 CCTV SYSTEM Feature / Specifications Minimum Specification 6.1 Camera CE approved /UL listed, Fixed lens type, minimum 0.5 Lux, BNC connection Colour Dome type Camera, coupled with motion sensor, suitable for indoor application 10-50 c and relative humidity 10- Compliance (Y / N) for minimum specifications Proposed Capacity / Equipmen t (Bidder can propose technicall y superior componen ts) Details / Remarks Technical Specifications Page 188
90%. 6.2 Power Supply for 230V AC, 50 HZ supply Camera 6.3 Digital Video Recorder Recording for 30 days 6.4 Video Signal Cable 6.5 Provide 5 years onsite. comprehensive warranty +AMC for complete system 6.6 Make & Model 6.7 1/3 CCD 12mm Lens, 1No Colour Dome Camera 6.8 Digital Video Recorder 01 No. Technical Specifications Page 189
SECTION 2.17 TECHNICAL SPECIFICATION FOR SERVER ROOM PALATANA, TRIPURA 1.0 UPS (PARALLEL REDUNDENT) Feature / Specifications 1.1 Input Dual Input Minimum Specification and Quantity Compliance (Y / N) for minimum specifications Proposed Capacity / Equipment (Bidder can propose technically superior components) Details / Remarks 1.2 Input Voltage 415 V ± 15%, 3 Phase, 4 wire 1.3 Input Frequency 50-60 Hz +/- 5 Hz ( auto sensing ) 1.4 Output voltage 230 V ±1%, 1 Phase, 1.5 Output Frequency 50 Hz ±1% for all condition of inputs 1.6 Output Wave form Pure sine wave 1.7 Output Voltage Less than 3% Distortion 1.8 DC Ripple Less than 1.5% 1.9 DC Voltage Regulation +/- 2% 1.10 Crest Factor Designed to handle unbalanced and nonlinear loads 1.11 Overload Capacity/rating. 1.12 Output Power Factor 0.8 to unity Support 1.13 Technology Double conversion Technology with built in battery charger 1.14 On line Transfer. 1.15 UPS fault Transfer Time Auto by pass activation or recovers Technical Specifications Page 190
1.16 Overall Efficiency 84%( At Full load) 82%( At half load) 1.17 Bypass Automatic internal 1.18 Battery Sealed maintenance free with 60 minutes backup for Full load. 1.19 Communication & Management: Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE for BMS interface. 1.20 Static Bypass. 1.21 Generator supply Compatibility The UPS should be generator supply compatible 1.22 Operating Temperature 0 to 40 C 1.23 Relative humidity 0 95% 1.24 Noise level at full load Less than 65dBA 1.25 UPS Cabinet Floor mounted with MS frame base Panel, Key lockable door. 1.26 Redundancy Parallel redundant with common Battery 1.27 Maintenance Bypass Switch 1.28 Power Status Bypass voltage ok, Load on bypass, Load on inverter LED indication on Mimic display. 1.29 Provide 5 years onsite. comprehensive warranty + AMC for the system 1.30 Make & Model. 1.31 UPS (2 x 10KVA) in Parallel mode (with paralleling kit) with common 60 minutes SMF battery backup, 1.32 Supply, Termination of UPS to Battery Cable 2 Nos. As Technical Specifications Page 191
2.0 PRECISION AC SYSTEM Feature / Specifications Minimum Specification and Quantity 2.1 Make and Model Compliance (Y / N) for minimum specifications Proposed Capacity / Equipment (Bidder can propose technically superior components) Details / Remarks 2.2 Redundant cooling unit in at least N+1 configuration 2.3 3 KW Precision cooling system 2.4 5 Star Rating 2.5 3 KW redundant Precision cooling with digital scroll compressors 2.6 Designed to operate 24X7 2.7 Temperature Control 2.8 Load sharing 2.9 Filtration 2.10 Outdoor Unit 2.11 Distance between Outdoor Unit and Precision cooling system 2.12 Provide 5 years onsite comprehensive warranty + AMC for the system 30 MTR Technical Specifications Page 192
3.0 CIVIL WORK Feature / Specifications 3.1 Demolition / Dismantling work Minimum Specification and Quantity Demolition / Dismantling Work including carefully stacking (at customer storing area) of useful materials & disposing off the unserviceable material out of the premises to the nearest municipal dump) etc. complete as per customer direction. Compliance (Y / N) for minimum specification s Proposed Capacity / Equipment (Bidder can propose technically superior component s) Details / Remarks Selected System Integrator will have to make good without any extra payment any damage done during Execution. The System Integrator s are requested in their own interest to inspect the site to assess the nature and quantum of work. 3.2 False flooring work For flooring for the area as per the server room layout (tentative). Access floor systems with a maximum finished floor height of 1200 mm from the existing floor level in the Server room. The raised floor shall be provided with Raised Access Flooring system with access floor panel of size (600 x 600) mm and shall be of steel welded construction. The floor panels should be finished with System Integrator has to visit the site before to understand the site condition and actual quantity required before bidding Technical Specifications Page 193
antistatic high pressure laminate with point load 360 kg and uniform distribution load (UDL) 1080 kg/sqm. It should have a suitable pedestal assembly to provide a means of leveling and locking at a selected height. Suction Equipment for lifting tiles (Access Floor Systems Lifting Tools) to be provided as required. Steps also shall be provided for the server room. 3.3 False ceiling work Metal false ceiling system of size 600 x 600 x 5mm laid on Grid system (Micro lock edge) with 15mm thick T- section (White) having main runner 1200mm x 600mm, cross Tee at suitable height. And having noise reduction co-efficient of 0.5, light reflection over 70%, Relative Humidity 99%, fire performance class 0 /class1. With standard perforation of 2.5 mm dia (16% open space) and fleece with NRC of 0.70 & CAC 36 to be laid on grid system should be provided in the server room 3.4 Fire rated door High quality galvanized steel and having fire rating up to 2 hours (conforming to BS 476 part 22 and IS 3614 part 2 standards). The doors to be suitable for openings of sizes 4 x7. The main access door shall of two pane type, one pane to be bolted and the other with automatic door closer Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 194
and locking 3.5 Gypsum partition work 100mm of Fire rated gypsum partition between UPS and Server room 3.6 Any other civil works Any Miscellaneous works to complete the job, which may include closing of wall cut outs with proper sealants, cleaning works etc., 4.0 ACCESS CONTROL SYSTEM (For one number of door of the server room) Feature / Specifications Minimum Specification 4.1 Reader Controller Compliance (Y / N) for minimum specification s Proposed Capacity / Equipment (Bidder can propose technically superior component s) Details / Remarks 4.2 Access Control Software 4.3 Proximity Card Reader With in-built Self-test & Diagnostic, read range 10-12cm from the front surface and suitable for indoor mounting and. A multi-colour LED on the front surface of the reader with an audio beep tone to indicate that the card has been read. 4.4 Proximity Card Interchangeable, Compatible with all readers, Sequentially numbered passive device without internal battery /any other memory powering /supporting device (such as capacitors, etc.). 4.5 Door Lock with in-built Electromagnetic type, Technical Specifications Page 195
door status sensor suitable for 600 Lbs load with power supply unit. 4.6 Cables 4.7 Provide 5years onsite. comprehensive warranty+amc for complete system 4.8 Make & Model 4.9 Reader Controller 1 No. 4.10 Power supply for 1 No. Controller 4.11 Proximity Card Reader 1 No. 4.12 Proximity Cards with 10 Nos. prints detail of company & card holder 4.13 Electromagnetic Door 01 Nos Lock suitable for 600Lbs load with in-built door contact sensor 4.14 Egress Switch 01 No. 4.15 Access Control Software 01 Set. Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 5.0 ELECTRICAL WORK 5.1 5.2 Feature / Specifications UPS Input Cables Laying & Clamping, Glanding & Termination Minimum Specification UPS input shall be taken from the spare feeder of the existing Raw power panel (shall be identified at site) Suitable rated FRLS cables shall be installed as per below minimum specs: UPS Input : PVC, CU Cables of 1C / 4C; UPS Output: PVC, CU Cables of 1C / 4C; Rack Input: 3C x CU PVC Cables; Raw power cabling: 4C x Compliance (Y / N) for minimum specification s Proposed Capacity / Equipment (Bidder can propose technically superior component s) Details / Remarks Technical Specifications Page 196
5.3 5.4 5.5 5.6 5.7 Earthing Work Lighting Providing & Fixing Cable Trays Other Miscellaneous works Provide 5years onsite comprehensive warranty+amc for complete work Al, XLPE Cables; Wirings: using CU wires. The work shall include all clamping, making gland hole/tapping glanding, inhibiting compound filling, epoxy cable jointing, crimping, and connecting. Installation of required earthing conductors for the equipment and Server room area Suitable lighting with LED light fixtures shall be installed to provide minimum of 500lux inside the server room Suitable size of Perforated cable trays shall be installed for the cables with supports and complete accessories Any other works required to complete the job. 6.0 FIRE DETECTION AND ALARM SYSTEM 6.1 System Feature / Specifications Minimum Specification All equipment should be in compliance with specifications laid out in the National Fire Protection Associations Document, NFPA 75: Protection of Compliance (Y / N) for minimum specification s Proposed Capacity / Equipment (Bidder can propose technically superior component s) Details / Remarks Technical Specifications Page 197
Electronic/Data Processing Equipment. 6.2 Detectors Analog Addressable Optical smoke detector 6.3 Electronic Hooter Addressable, Sound levels range from 75dBA to 100dBA and multi tone facility. 6.4 High Sensitivity Smoke Detection System Panel Aspiration unit working on Laser Based Detection Technology with Pre-Alarm, Alarm, Fire and Fault relays. 6.5 Provide 5years onsite comprehensive warranty+amc for complete system. 6.6 Make & Model 6.7 Main Fire Alarm Panel 1 No. 6.8 Optical Smoke Detectors 2 Nos. 6.9 Electronic Hooter 1 Nos. 6.10 Electronic Hooter cum strobe 1 Nos. Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 7.0 CCTV SYSTEM Feature / Specifications Minimum Specification 7.1 Camera CE approved /UL listed, Fixed lens type, minimum 0.5 Lux, BNC connection Colour Dome type Camera, coupled with motion sensor, suitable for indoor application 10-50 c and relative humidity 10-90%. 7.2 Power Supply for 230V AC, 50 HZ supply Camera 7.3 Digital Video Recorder with 30 days Compliance (Y / N) for minimum specification s Proposed Capacity / Equipment (Bidder can propose technically superior componen ts) Details / Remarks Technical Specifications Page 198
recording 7.4 Video Signal Cable 7.5 Provide 5 years onsite. comprehensive warranty +AMC for complete system 7.6 Make & Model 7.7 1/3 CCD 12mm Lens, 1No Colour Dome Camera 7.8 Digital Video Recorder 01 No. Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 8.0 WATER LEACKAGE DETECTION SYSTEM Feature / Specifications 8.1 Water leakage detection system Minimum Specification Compliance (Y / N) for minimum specification s Proposed Capacity / Equipment (Bidder can propose technically superior componen ts) Details / Remarks 8.2 Provide 5 years onsite. comprehensive warranty+amc for complete system 8.3 Make & Model 8.4 WLD system with complete accessories 1Set 9.0 RODENT REPELLENT SYSTEM Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specification s Proposed Capacity / Equipment (Bidder can propose technically superior componen ts) Details / Remarks Technical Specifications Page 199
9.1 Rodent Repellent System 9.2 Provide 5 years onsite. comprehensive warranty+amc for complete system 9.3 Make & Model 9.4 Rodent Repellent system with complete accessories 1Set Technical Specifications Page 200
SECTION 2.18 TECHNICAL SPECIFICATION FOR STATIC/SOURCE TRANSFER SWITCH 1.0 STATIC/SOURCE TRANSFER SWITCH - DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 Make 1.2 1.3 1.4 Rack mount with dual input power source Input Source Output Ports 2 Power Input source for UPS Redundancy 12 C13 type ports 1.5 Nominal Current 16 Amp 1.6 Input Voltage 208 V /230 V 1.7 Out Voltage 208 V /230 V Compatibility Any On-Line 1.8 Double Conversion UPS 1.9 Input Port Type Indian Type Input Source 2 Power Input 1.10 source for UPS Redundancy Auto switchover Auto switchover 1.11 to any available UPS 1.12 Output Port Type IEC-C13 1.13 Standards Compliance UL/cUL, CE, TUV, IEC 50091-1, IEC 50022/B, IEC 1000-4 Technical Specifications Page 201
1.14 Operating Environment -5 to 45 C 1.15 Operating Relative 5 to 95% Humidity Monitoring Feature In-built Digital 1.16 Information Display. 1.17 Overload Alert Alarm/Indication Overload Protection Distribute load 1.18 during over load 1.19 Warranty 5 Years On-Site 1.20 Number of STS Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE 1 Technical Specifications Page 202
SECTION 2.19 TECHNICAL SPECIFICATION FOR FIRE PROOF MEDIA ENCLOSURE 1.0 FIRE PROOF MEDIA ENCLOSURE - DELHI Feature / Specifications Minimum Specification Compliance (Y / N) for minimum specifications Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks 1.1 Make 1.2 Size 90 Litre Minimum 1.3 Lock Type Dual Locking feature Safety Feature Fire, Water, Humidity, 1.4 Magnetic, Temperature & dust proof. 1.5 Fire Rating 2-hour at 1000 C 1.6 Standard UL 125 Rated Drawer /Shelves Type Design for Data 1.7 drives (e.g. LTO Tape, CD/DVD Media) Internal Temperature 30 C after exposure to 1.8 high temperature For 2 hour 1.9 Shelves Types Adjustable Number of Shelves To be proposed 1.10 by manufacturer as per requirement. 1.11 Locking feature 2 IO-lever high Technical Specifications Page 203
security cylindrical / Electronic lock 1.12 Warranty 5 Years on site Project: SETTING-UP DATA CENTRE AND IT INFRASTRUCTURE Technical Specifications Page 204