Annexure 7.4 Technical Specification Ver 6.0

8/6/2019 Annexure 7.4 Technical Specification Ver 6.0

1/101

FCS EGOVERNANCE PROJECT -RFP-ANNEXURE 7.4(TECHNICAL SPECIFICATIONS)

RFP for appointment of Vendor for Distribution Mechanism for PDS 44

A. R E Q U I R E M E N T S

1.1 REQUIREMENTS TO BE MET BY TH E SYSTEM

The generalized requirements for the new systems to be implemented, but not limited to, can be summarized as follows:

The application system should primarily work in centralized architecture. However, essential data should be replicated at the central server. The system should allow both interactive and the batch work modes depending on the type of modules. The application design and

construction should take into account the network infrastructure availability, as per the proposed solution by the bidder. Incorporation of Multi-tier architecture in the centralized solution. Development and Integration of portal & new system with existing and upcoming FCS applications and systems. Ensuring quality in all the activities carried out during the development/ customization, documentation, testing, implementation,

maintenance etc. of the system. The bidder would also be required to provide FCS with approach for quality related activities. The bidderMUST provide the quality records related to deliverables of the project e.g. review reports, defect density, effort and schedule slippage etc.

Taking care of the configuration management i.e. version control of all the deliverables, where applicable. Considering that most of the documents of FCS are in Hindi, the application system MUST cater to the Hindi language requirements of

FCS and as per existing policies and procedures. The fields of application system can be bilingual (both English and Hindi) depending uponthe design of the application system. Where it is not possible due to technical reasons to have Hindi User Interface, the bidder MUSTpropose an alternative means of converting English text to Hindi and vice-versa, so that appropriate reports can be generated for use by thedepartment.


2/101


RFP for appointment of Vendor for Distribution Mechanism for PDS45

OVERVIEW OF PROPOSED SOLUT ION

Proposed Solution

The proposed portal architecture for FCS shall comprise of the following components:

1) Database Servers2) Application Servers3) Portal Engine4) Load balancing Routers (Hardware)5) MI S and Other applications Servers

The details of the above mentioned components are provided in the subsequent sections of this document.

T E C H N I C AL SPE CI F I CA T I O N S

2.0 TECHNICAL REQUIREMENTS

2.0.1 Language Support: All information technologies must provide support for the English and/ or Hindi language .Specifically; all displaytechnologies and software must support the ISO character set and perform sorting. The application system MUST be UnicodeCompliant.

2.0.2 Dates: All information technologies MUST properly display, calculate, and transmit date data, including, but not restricted to 21st-Century date data. .

2.0.3 Electrical Power: All active (powered) equipment must operate on voltage range and frequency range, 220v +/ - 20v, 50Hz +/ - 2Hz.All active equipment must include power plugs standard in India.

2.0.4 Environmental: Unless otherwise specified, all equipment must operate in environments of . 10-45 degree centigrade, 20-90 percentrelative humidity, and 0-40 grams per cubic meter of dust.

2.0.5 Safety:2.0.5.1 Unless otherwise specified, all equipment must operate at noise levels no greater than 55 decibels.


3/101


RFP for appointment of Vendor for Distribution Mechanism for PDS46

2.0.5.2 All electronic equipment that emits electromagnetic energy must be certified as meeting, US FCC- class B and UL or equivalent,emission standards.

2.1 DATA CENTER (DC)AT H EAD OFFICE & DISASTER RECOVERYSITE (DR)

2.1.1 Data Center (DC) At Head Office:

The vendor has to supply, install, configure and maintain the systems at the same location at the data center and disaster recovery site as decidedby the FCS. FCS will provide the space, ac power & backup (generator only), physical security, f ire detection and control and vendor need toprovide racks, security, bandwidth, networking & networking equipments (firewall, router, etc) & remote access. It would be the vendorsresponsibility to meet the SLA requirements as defined in this RFP.

The proposed FCSoverall data center architecture appears as shown in the following diagram on next page.


4/101


5/101



WAN Links will terminate on core router and it will configure for failover via HSRP (Hot Stand by routing Protocol or GLBP (Gateway LoadBalancing Protocol). Two Firewalls configured in HA (High Availability) mode, which could act as web SSL, IPS, VPN and firewall unit .Firewall will be connected to core switches. The core switches will be running HSRP to eliminate single point of failure. The switches that areused for connectivity to the servers will be configured in transparent mode to introduce a level of security and isolate them from the user

segment. The users will connect to an access switch as shown. All uplinks from user segment and the server access switch to the core switcheswill be a fiber Gigabit connection. All servers will be placed under server farm for centralized access and maintenance. Internal LAN would besegregated through different VLAN or subnet.

Wide-Area Network

WAN Router for Data Center

FunctionThe WAN router is responsible for connecting Primary Data center with the DR site.

The interface offered in the equipment should match with the interface provided by service provider.

Router Architecturei. Architecture should be based on high speed CPU with high port densitiesii. Router should be single box configuration and modular so that the for the flexibility to use appropriate choice of interfaces as and when

requirediii. Router shall have minimum two spare interface slots after accommodating required interfaces, for future expandability.iv. Router should support standard interfaces such as E3, Ch-E3, Ch-E1, 1000BaseSX, 1000Base LX, 1000Base TX, ISDN PRI, Fast

Ethernet and Gigabit Ethernet. Router should support these interfaces at the time of bidding.v. Router should be capable of functioning as the Customer Premise Equipment (CPE) for MPLS VPN networks.

Router Hardwarei. Should be compact rack mountable chassisii. Health LED for all modules to indicate operational status of the moduleiii. The router must support the flash file system to easily store and load multiple images.iv. Router must have minimum of 256MB expandable to 512 MB flash memory.v. Should ensure storage of multiple router software images.vi. Router must have minimum of 1GB DRAM.vii. Extensive debugging capabilities to assist in hardware problem resolution


6/101



High Availabilityi. Redundant AC Power Supply Unitii. Capability to support redundant CPU / routing engine for High Availabilityiii. Hot swappable control and individual I nterface Modules/ Online Insertion and removal of individual interface cards / modulesiv. Support for Virtual router redundancy protocol (VRRP) (RFC 3768) or equivalentv. Router software must have on line reconfiguration facilities to ensure that the changes made to its configuration take place with

immediate effectvi. Link aggregation using LACP as per IEEE 802.3advii. It must be possible to fast boot the router to ensure that software updating can be done with minimum network down time.viii. High Mean Time Between Failure values should be available to ensure long life of router hardware.ix. Configuration changes should be done without rebooting the router or modules.

Router Performancei. Shall support dual CPU configuration with distributed forwardingii. State-full switch-over so that forwarding performance of the router shall not be impacted due to one CPU failure.iii. Shall have performance enhancement through hardware based acceleration of IP Services like GRE tunneling or equivalent I EEE

standard, ACLs, IPSEC VPNs, Firewall , NAT or equivalent.iv. Shall support multiple physical WAN links into single logical interfaces, to increase bandwidth.v. Shall support load balancing across multiple unequal WAN links to the same destination network.vi. Shall have packet forwarding rate of 2 Mpps @ 64 byte packets per second or more on single chassis.vii. Shall have 2 Gbps back plane or higher.

Router I nterface Requirementi. E3 2 Nosii. Ch-E1 2 Nosiii. E1 2 Nosiv. 10/ 100/ 1000 Mbps Ethernet Port 2 Nosv. ISDN PRI (Can be Internal or External) 2 Nos

Router Protocoli. RIPv1 (RFC 1058)ii. RIPv2 (RFC 2453)iii. OSPF v2 (RFC 2328)iv. BGP v4 (RFC 1771)

Quality of Service (QoS)


7/101



i. Traffic Condit ioning: A class-based scheduling/ queuing mechanism that provides configurable minimum bandwidth allocation toeach class for assigning priority to critical traffic.

ii. RSVP: Resource Reservation Protocol (RSVP) as per RFC 2205iii. Policy Routing support: It shall be possible to affect the normal routing process for specific mission critical traffic through specified

alternate routes in the network.iv. The router should be able to recognize applications, including Web-based and other difficult-to-classify protocols that use dynamic

TCP/ UDP port assignments. When an application is recognized and classif ied by router, a network can invoke services for thatspecific application.

v. Support for Per VLAN QoS

Debug, Alarms & Diagnosticsi. Support for monitoring of traffic flows for network planning and security purposes.ii. Display of input and output error stats on all interfaces.iii. Display of Dynamic Arp table.iv. Display of physical layer line status signals like DCD, DSR, DTR, RTS, CTS on all serial interfaces.

v. Trace-route, Ping and extended Ping.vi. Should have extensive support for SLA monitoring for metrics like delay, latency, jitter and packet loss.

Managementi. The router should be manageable from any open management systemo.ii. Shall have support for Web based/ GUI based management, FTP/ TFTP, CLI , Telnet and SNMP/ SNMPv3 and RMON.iii. Shall support Secure Shell.iv. Shall support out of band management through Console and external modem for remote management.v. The router shall support Network Time Protocol (NTP) (RFC 1305).

Securityi. IPSEC with 3DES/ AES encryptionii. GRE Tunneling or equivalentiii. IPSEC (Site-to-Site) and Remote Access.iv. MD-5 route authentication for RIP, OSPF, IS-IS and BGPv. SSHv2.vi. Logs (access and service).vii. Access Control Lists (ACL) / IP Access list to limit Telnet and SNMP access to router.viii. AAA support using Radius and/ or TACACS.ix. NTP with authentication features.


8/101



x. CHAP authentication for P-to-P links.xi. DoS/ DDoSprotection.

Internet Router for Data Center

Function

The Internet router at Data Center is responsible for providing connection to the Internet Service Provider. Two routers load balanced in HighAvailability configuration provide internet connectivity.The interface offered in the equipment should match with the interface provided by service provider.

Router Architecturei. Architecture should be based on high speed CPU.ii. Router should be single box configuration and modular so that the for the flexibility to use appropriate choice of interfaces as and when

requirediii. Router shall have minimum one spare interface slots after accommodating required interfaces, for future expandability.iv. Router should support standard interfaces such as E1, Fast Ethernet and Gigabit Ethernet. Router should support these interfaces at the

time of bidding.

Router Hardwarei. Should be compact rack mountable chassisii. Health LED for all modules to indicate operational status of the moduleiii. The router must support the flash file system to easily store and load multiple images.iv. Router must have minimum of 128MB expandable to 256 MB flash memory.v. Should ensure storage of multiple router software images.vi. Router must have minimum of 512 DRAM.vii. Extensive debugging capabilities to assist in hardware problem resolution

High Availabilityi. Redundant AC Power Supply Unitii. Hot swappable control and individual I nterface Modules/ Online Insertion and removal of individual interface cards / modulesiii. Support for Virtual router redundancy protocol (VRRP) (RFC 3768) or equivalentiv. Router software must have on line reconfiguration facilities to ensure that the changes made to its configuration take place with

immediate effectv. Link aggregation using LACP as per IEEE 802.3advi. It must be possible to fast boot the router to ensure that software updating can be done with minimum network down time.vii. High Mean Time Between Failure values should be available to ensure long life of router hardware.


9/101


10/101



i. The router should be manageable from any open Management system platform.ii. Shall have support for Web based/ GUI based management, FTP/ TFTP, CLI , Telnet and SNMP/ SNMPv3 and RMON.iii. Shall support Secure Shell.iv. Shall support out of band management through Console and external modem for remote management.v. The router shall support Network Time Protocol (NTP) (RFC 1305).

Securityi. IPSEC with 3DES/ AES encryptionii. GRE Tunneling or equivalentiii. IPSEC (Site-to-Site) and Remote Access.iv. MD-5 route authentication for RIP, OSPF, IS-IS and BGPv. SSHv2.vi. Logs (access and service).vii. Access Control Lists (ACL) / IP Access list to limit Telnet and SNMP access to router.viii. AAA support using Radius and/ or TACACS.ix. NTP with authentication features.

x. CHAP authentication for P-to-P links.xi. DoS/ DDoSprotection.

Local Area Network(S):

Core Switch for Data Site

FunctionCore switch at the Primary Data Center acts as Core/ Distribution layer and provides aggregation of server farm and user access switches. Itprovides multilayered, high speed scalable and fault tolerant connectivity to various access layers.

PerformanceThe suggested core switch should have features as under:

i. High back plane speed (30 GBPS or more)ii. The forwarding rate should be 20 Mbps or more.

High Availabilityi. Redundant Power Supplies


11/101



ii. Hot swappable control and individual I nterface Modules/ Online Insertion and removal of individual interface cards / modules.iii. Switching engine: The switch should have capability to support redundant Control Modules. The switching & routing performance

claimed on the chassis should not degrade with failure of switching/ routing engine module.iv. The switch should support server load balancing internally or with third party boxes / products.v. Shall support Non-Stop forwarding with State-full Switch Over, allows packet forwarding to continue until route re-convergence is

complete.

vi. Shall support multiple storage of multiple images and configurationsvii. Shall support link aggregation using LACP (IEEE 802.3ad).viii. On power up the platform should use built-in system monitoring & diagnostics before going online to detect failure of hardware.ix. Switch should support 10 G ports.x. Switch Port requirement:

10/ 100/ 1000 Mbps port 48 Nos 1000 Base SX port 16 Nos

Layer 2 Featuresi. Layer 2 switch ports

ii. IEEE 802.1Q VLAN encapsulationiii. Support for VLANs.iv. Dynamic Trunking Protocol (DTP) or equivalent.v. VLAN Trunking Protocol or equivalent.vi. Multiple Spanning Tree (802.1s)vii. Rapid Spanning Tree Protocol (802.1w)viii. Port Trunking technology across line cards

Layer 3 Featuresi. Hot Standby Routing Protocol (HSRP)/ VRRP (RFC 3768) or equivalentii. IPv6 support in hardwareiii. Static IP routing.iv. IP routing protocols

OSPF v2 (RFC 2328) RIP v1 (RFC 1058) and v2 (RFC 2453) BGP v4 (RFC 1771)

v. Internet Control Message Protocol (ICMP) supportvi. ICMP Router Discovery Protocol

Standards


12/101


13/101



iv. Support for VLANsv. Spanning tree/ Rapid Spanning Tree supportvi. Per VLAN Spanning Tree or equivalent supportvii. The switch must support Dynamic VLAN Registrationviii. Dynamic Trunking Protocol or equivalent.ix. VLAN Trunking Protocol or equivalent

x. Must have support for SNMP/ SNMPv3/ RMONxi. Prioritization supportxii. SNMP, Telnet and SSH v2 supportxiii. Web-based and CLI managementxiv. Additional features: Advanced QoS, Rate limitingxv. Standard and extended IP security router ACLs to define security policies on routed interfaces for control-plane and data-plane traff ic.

Security Devices

Firewall with SSL VPN Gateway, content security and URL filtering and for Data Center

FunctionThe Firewall at the Primary Data Center is responsible for acting as a Gateway Protection to defend FCS network from virus, phishing,spamming, worms and other malicious traffic. Also Firewall is responsible to act as a SSL VPN Gateway.

Firewall Architecture with featuresi. Architecture should be based on high speed CPU with high port densitiesii. Firewall should be modular so as to have flexibility to use appropriate choice of interfaces and security modules as and when required.iii. Firewall should support interfaces such as Fast Ethernet and Gigabit Ethernet.iv. Firewall should be capable of functioning as SSL VPN Gateway.v. Firewall should have either an integrated module with Anti-spam/ Spamblocker or separate content filtering appliance with Anti

spam/ Spamblocker that removes unsolicited e-mail and other malicious content before it hits the mail server or any other servers.vi. Firewall should have either an integrated Intrusion Prevention Service module or should be integrated with a separate Network Intrusion

Prevention appliance to protect FCS network from any intrusion/ malicious content at the main gateway.vii. Firewall should either have a content-based inspection module or separate content-based inspection appliance for inspecting web, e-mail

and ftp content for virus, phishing, spamming, worms and other malicious content.viii. Firewall should either have a content-based inspection module or separate content-based inspection appliance for inspecting web, e-mail

and ftp content for virus, phishing, spamming, worms and other malicious content.


14/101



ix. Firewall should either a URL filtering capabilities or a separate URL filtering appliance to block malicious sites that FCS does not wanttheir employees to access. URL Filtering should have capability to filter URL traffic according to predefined categories such as adult ormature content, games, phishing, movies/ songs, chat or instant messaging or gambling and any other pirated software downloadingsites.

x. SSL VPN functionality with authentication using Dual Factor Authentication with support for SSO / RADIUS/ LDAP/ Microsoft ADserver or any other directory server.

Firewall Hardwarei. Should be compact rack mountable chassisii. Health LED for all modules to indicate operational status of the module.iii. The Firewall must support the flash file system to easily store and load multipleimages.iv. Firewall must have minimum of 256MB expandable to 512 MB flash memory.v. Firewall must have minimum of 1GB DRAM.vi. Extensive debugging capabilities to assist in hardware problem resolution.

High Availability

i. Redundant AC Power Supply Unitii. Two firewall units with support for High Availability (Active and Active failover) with Internet Service provider (ISP) failoverprotection.

iii. Hot swappable security Modules/ Online Insert ion and removal of security modules.iv. Firewall software must have on line reconfiguration facilities to ensure that the changes made to its configuration take place with

immediate effect.v. It must be possible to fast boot the firewall to ensure that software updating can be done with minimum network down time.vi. High Mean Time between Failure values should be available to ensure long life of Firewall hardware.vii. Configuration changes should be done without rebooting the firewall or its modules.

Firewall Performancei. Firewall throughput 700 Mbps to 1 Gbpsii. Maximum firewall connections 400,000 to 500,000iii. 3DES/ AES IPSec support with 500 Mbps throughput.iv. Firewall with Antivirus/ Anti-Spam integration should support 3000 concurrent users.v. Firewall as SSL VPN Gateway should support 3000 concurrent SSL VPN sessions.vi. URL and content filtering for 600-700 concurrent users.vii. Shall have 2 Gbps back plane or higher

Firewall Interface Requirement


15/101



i. Gigabit Ethernet 4 Nosii. Fast Ethernet 2 Nos

Routing Protocoli. RIPv1 (RFC 1058)ii. RIPv2 (RFC 2453)

iii. OSPF v2 (RFC 2328)

Quality of Service (QoS)i. Traffic Condit ioning: A class-based scheduling/ queuing mechanism that provides configurable minimum bandwidth allocation to each

class for assigning priority to critical traffic.ii. The firewall should be able to recognize applications, including Web-based and other difficult-to-classify protocols that use dynamic

TCP/ UDP port assignments. When an application is recognized and classified by firewall, a network can invoke services for that specif icapplication.

iii. Support for Per VLAN QoS

Debug, Alarms & Diagnosticsi. Support for monitoring of traffic flows for network planning and security purposesii. Display of input and output error stats on all interfaces.iii. Display of Dynamic NAT/ Arp tableiv. Trace-route, Ping and extended Pingv. Should have extensive support for SLA monitoring for metrics like delay, latency, jitter and packet loss

Management

i. The Firewall should be manageable from any open management system .ii. Shall have support for secure web based/ GUI based management, CLI, Telnet/ SSH and SNMP/ SNMPv3 and RMON.iii. Shall support out of band management through Console portiv. The firewall shall support Network Time Protocol (NTP) (RFC 1305)

Other Securi tyi. IPSEC with 3DES/ AES encryptionii. IPSEC (Site-to-Site ) and Remote Accessiii. MD-5 route authentication for RIP and OSPFiv. SSHv2v. Logs (access and service)vi. Access Control Lists (ACL) / IP Access list to limit Telnet and SNMP access to f irewall


16/101



vii. AAA support using Radius and/ or TACACSviii. NTP with authentication features

2.1.2 Remote Di saster Recovery (DR) Site:

The DR database must be in sync and be mirror image of the database at FCS Datacenter at any given point of time and be online. There should

be redundancy at network components level and security appliances level. The bidder has to propose the solution for the same includingminimum number of servers & other hardware from given specifications in this document. However the bidder may propose the optimalsolution for meeting this requirement.


17/101




18/101



Proposed DR Architecture

2.2 COMPUTINGH ARDWARE REQUIREMENTS

The indicativeminimumconfigurations for the servers, storage unit and tape library unit, etc is provided later

The specifications are indicative and the bidder MUST fine-tune to upgrade the specifications and the numbers as per requirements of thesystem proposed.

The bidder MUST also propose the specifications of any additional servers that will be required for the system. The bidder MUST provide thearchitecture of the solution, which it is proposing.

2.2.1 Server Requirement:

To run the FCS application successfully on the network, Web Server, Application Server, Database Server, etc will be required. Some otherservers like MI S, Antivirus, and EMS Server etc will be required for their different purposes. The detailed specif ication of each server is given in

this document.

Application, Web & Portal Server

Application would be required as middle tier for various web based applications. Application server would take care of the necessary workflowand Web and Portal server would be required for the interfacing with the end user / department user. All of these servers would be seamlesslyintegrated to provide high availabili ty and performance. It would be required to cluster these Servers to ensure high availability and reliability

Database Server

The FCS application will be hosted on a centralized common database which will contain all the data of the application. Since this data iscentralized and is very critical, it would be required to cluster this Server to ensure high availability and reliability. The data would be physicallystored on an External FC based Storage (SAN). These will be RISC/ EPIC based servers.

Management Server


19/101



The management server would help in administration of distributed systems at the server farm. The management server would help in efficientand reliable administration of all the distributed computing devices. It would provide Inventory Management, Fault Management andPerformance Management and Patch management and it would monitor the availability of Services. EMS will be installed on this system.

Backup Server

A backup server would be required for installation of backup software which will take care of backup activity.

Anti virus & Anti -Spam ServerA separate server for Anti Virus and Anti Spam would be required to keep the other servers and application secure from the attack of virus,Trojans and spam. This will also act as a centralized system for updating the virus definitions on the systems across FCS offices.

2.2.2 Backup, External Storage (SAN) & Tape Library & Restoration

A SAN (Storage Area Network) will be required for storage of data from all the locations. This will act as central repository for data, documentsand records. The specif ication for SAN is given in subsequent Section. Backup is an important aspect of recovering the lost data due to any loss.A Tape Library is proposed for taking the regular backup of centralized storage (SAN).

The FCS setup would be configured with SAN for external storage of data for faster access and would be implemented on RAID 1+0 forredundancy and high availability. The Database cluster connects to SAN through a redundant f iber switch to ensure no single point of failure.Tape Library would also be deployed for auto backup, which would have automated robot to place the tapes for backup. The detail specificationof each server is given in This document.

The backup solution should address the following

Assuring that the production servers data is available in an offline storage device, and can be restored as and when required.

The backup of the production systems to be performed in an LAN free manner for the Database Server, a LAN based backup for otherAPP and WEB Servers.

Online full and incremental backups for the main database

To ensure a policy driven data-protection through scheduled backup and recovery.

Replication of complete backup data to a remote site, so that in case of any disaster at the Server Farm, the backup may be recovered fromthe remote site.


20/101



Single, centralized management for data protection and disaster recovery.

Backup of operating system, database and application as per stipulated policies at the Server Farm.

Monitoring and enhancement of the performance of scheduled backups, schedule regular testing of backups and ensure adherence torelated retention policies.

Ensuring prompt execution of on-demand backups of volumes, files and database applications whenever required by User Departments orin case of upgrades and configuration changes to the system.

Real-time monitoring, log maintenance and reporting of backup status on a regular basis. Prompt problem resolution in case of failures inthe backup processes.

Media management including, but not limited to, tagging, cross-referencing, storing, logging, testing, and vaulting in fire proof cabinets.

Physical security of the media stored in cabinets.

Ongoing support for file and volume restoration requests at the Server Farm.

All proposed hardware MUST be of proven technology and be current / recent in the Supplier's product line. Equipment MUST not beobsolete and MUST be fully supported by the product supplier.

The bidder is expected to analyze the processes for the offices, geographic locations, and network in order to determine the best hardware andsystems requirements.

Proposed Server Configuration to Support World Class Systems and Data Sharing

The specifications of servers, provided by the bidder should include following characteristics:

Scalability- The configuration proposed is expected to have adequate upgrade capability in terms of processors, memory, disk storage, etc. Thisshould be achievable with minimum disruptions to processes and Users with minimum additional investment.

Reliability- FCS will consider installation of equipment manufactured by reputed companies committed to product improvement and newproduct development.

Security- The equipment should have good security features, both physical (lockable, etc.) and operational (security/ administration systems).

Backup- The bidder should also recommend and provide an appropriate archiving system i.e. tape cartridge library or optical backup equipmentor better alternative to be installed at the server sites. In the event of serious failure, the backed up dataMUST be restored in the quickestpossible time to ensure continuity.


21/101



Open Systems Standards - The hardware MUST be such that FCS will not have restrictions on software application solutions interactingacross Servers & client platforms.

The specification of the servers should be designed to ensure high availability of servers (clustering) at the central site. The servers should beconfigured in such a way that there is no single point of failure. This means that RAID technology may be used and configured as a multi-storage system cluster. The bidder is to ensure the high availability for these servers (clustering) also. The option of having clustered servers is toallow for redundancy and load sharing for both database management and applications.

The bidder has to provide and install associated computing hardware apart from the servers, required for the installation, operation,management and administration of the solution provided e.g. hardware for Hindi User Interface.

Note:The bidder will be responsible for the compatibility requirements.

2.2.3 Desktops (with UPS), Printers

The bidder has to provide all necessary desktops, printers along with UPS(3hrs backup) for desktops. The specifications of the same are givenin this document.


22/101



2.3 NETWORK AND COMMUNICATIONSSPECIFICATIONS

FCS Datacenter will have all critical applications and servers deployed at FCS Bhopal. All services shall be web based so that HO and fieldoffices users are able to access it through internet.

Figure: Proposed Network architecture of FCSDatacenter

2.3.1 Local Area Network(s):

2.3.1.1 Equipment and software:


23/101



The bidder has to establish the LAN in various offices of FCS including integration with existing LAN. The list of offices with LANrequirement is provided in this document. The list shows the minimum requirement of FCS. The bidder has to conduct the site survey of FCSoffices and propose the optimal solution.

2.3.1.2 Cabling:

Vendor is required to do cabling in Data Centre and LAN cabling in various offices as needed till final equipment (desktop, printer, etc.).

Vendor shall ensure existing LAN is integrated with the respective hardware setup envisaged.

Vendor needs to provide all necessary cabling at Datacenter & various offices for Routers, Switches, RAS, Servers, etc.

Vendor should provide structured WAN cabling from distribution box of Connectivity Provider till final equipment.

Vendor shall also provide necessary electrical cabling for the required infrastructure.

2.3.2 Wide-Area Network

All FCS offices will be connected to the centralized datacenter through internet. All critical offices (regional offices) will have redundant WANlinks for application access in case of failure of the primary link. WAN connection at each location would terminate at router or firewall withserial port for wan termination. In this centralized architecture framework, all major application or services will be deployed at centralizeddatacenter. The proposed WAN diagram is depicted below; the specifications of Networking Equipments are given in This document. The listof offices with WAN requirement is provided in Annexure B. The list shows the minimum requirement of FCS. The bidder has to conduct thesite survey of FCS offices and propose the optimal solution.

2.3.3 Network Securi ty Considerations

Overall network environment has to follow a well-defined security policy. The framework needs to ensure the information availability, integrity,

and confidentiality of FCS infrastructure and data. The security policy should be comprehensive and shall address the security needs of thenetwork and the Network Operations for the Servers kept at Data Centre and for the end-users in various offices.Following are the key recommendations to secure the FCS network:

IT Security is very crucial since IT has become a key tool for the business. The overall security has to be achieved based on the ITSecurity policies of the Government of India. The vendor shall ensure that the policy guidelines are followed in the daily activities.


24/101



The security services shall be delivered, and that the technologies implemented, in conjunction with a set of best practices guidelines, andindustry standards. The technology solution should comply with BS7799/ ISO27001standard or any other standard adopted as a policyby the Government of India.

Appropriate security components/ devices shall be selected to protect FCS network and assets from any security threats and intrusionactivities from the unknown, un-trusted networks Internet and any third party connectivity, which can affect its business operations.

The FCS network shall have firewall in High Availability and integrated with Gateway Antivirus/ Intrusion Prevention Service with anti-spyware/ Spam Blocker to ensure network protection f rom security threats, e.g. viruses, worms, bots, spyware, phishing,Trojans, web-based exploits and other malicious threats. All such security threats can be stopped at the FCS gateway before it reaches inside itsnetwork.

The Network shall have Web/ URL filtering for creating lists of trusted web sites, or blacklist specific URLs or IP addresses. Blocksmalicious sites to keep network protected from risky web content such as spyware, adware and phishing sites.

The Network shall have SSL VPN gateway functionality to be included in the firewall to ensure secure remote access connectivity to

applications and resources inside FCSnetwork.

Security I nfrastructure should provide comprehensive identification, authentication, authorization/ access control, administration, andaudit mechanism in the Hardware and network with relevant technologies, best practices, guidelines, and standards. The security servicesused to protect the information infrastructure shall include:

Identification Process of distinguishing individual users Authentication Process of verifying the identity of a user. Authorization and Access Control Process of establishing and enforcing user rights and privileges. Administration Process of managing, and maintaining infrastructure. Audit Process of monitoring above mentioned processes, to make sure that suitable security has been established andmaintained.

A security audit shall be done for the FCS APPLICATI ONS after the completion of implementation phase and regularly during theOperations and Maintenance phases on annual basis, to assess whether appropriate security procedures are being followed.

Methods of mitigating a security breach from within the intranet or extranet should be addressed by the security policy. The biddershould design appropriate network solution so that a security breach/ virus do not spread throughout the network if originating at theend-user level.


25/101



The Network shall have Anti-Virus corporate edition to protect desktops/ laptops from viruses, Trojans, network worms, spyware androot kits.

The Network shall have ISP Failover Protection either by firewall in high availability or using link load balancer.

Mission crit ical servers such as application and database server shall have Host-based Intrusion Prevention System to stop well-known

attacks, new, unknown attacks and encrypted-tunnel based attacks that target the application/ database servers. This will reduce the riskof downtime caused by malware, spyware and other malicious content and helps to keep your critical application up and running.

Security administration activities shall include the following

Monitoring of various security devices such as firewall, intrusion detection, content filtering and blocking, virus protection, andvulnerability protection through implementation of proper patches and rules

Ensuring that patches / workarounds for identif ied vulnerabilities are patched / blocked immediately

Responding to security breaches or other security incidents and coordinate with respective OEM in case of a new threat is observed toensure that workaround / patch is made available for the same.

Monitor the Anti-Virus tool installed on daily basis and ensure that the latest patches are updated in all the systems.

Alert users on new virus breakouts based on the info received from the IT industry.

Monitoring the efficiency and effectiveness of the Anti-Virus and updating the Anti-Virus signatures on the server and the clientsperiodically.

Firewall integrated with SSL VPN Gateway

In the proposed setup, if users need to access FCS corporate network from the internet, to ensure ease of manageabil ity and uniform securitycontrols, it is recommended to configure all existing web-based incoming access through an SSL VPN gateway.SSL VPN (Web VPN) allows secure access to the corporate network from any location. The remote client/ PC needs only an SSL enabled webbrowser to access http or https enabled web servers on the corporate LAN. Access is also available to browse for Windows files with theCommon Internet File System (CIFS).


26/101



SSL VPN on firewall should have following features:

Firewall with SSL VPN should support following authentication mechanisms for secure remote-access

Popular authentication services e.g. Microsoft Active Directory, Lightweight RADI US, Directory Access Protocol (LDAP), andRSA SecurID.

Single sign-on support


27/101



HTTPS to access internal web servers of FCSnetwork


28/101


29/101


30/101


31/101



2.4 SOFTWARE SPECIFICATIONS

2.4.1 System Software and System-Management Utilities:

The bidder MUST provide the associated system software and system management utilities including clustering software for the hardwareprovided.

2.4.1.2Processing unit type 1 (Higher End Servers):

The operating system on server should be preferably UNIX. The operating system on desktops will be Windows. Bidder MUST also providethe associated system software and system management utilities.

2.4.1.3Processing unit type 2 (Lower End Servers):

The operating system on server should be Linux/ Windows. The operating system on desktops will be Windows. Bidder MUST also provide theassociated system software and system management utilities.

2.4.1.4System Upgrade:The support infrastructure layer software (operating system, database management system and software tools intended to support applicationsystems) should be easily upgradeable when required.

2.4.2 Enterprise Management System (EMS) :

EMS need to be deployed at the servers kept at FCSData Centre to perform the following functions:

Measure the performance

Manage and monitor the Servers (e.g. Database, Application, Backup and Anti-Virus etc.)

Manage non-functional requirements of FCS applicationsManage connectivity speed and Network components (including Routers, Switches, links, etc.)

EMS should help in pro-actively diagnosing and support in resolution of any technical hindrance for smoother operations. In addition to faultdetection, these tools should be capable enough in providing reports for:

Server Statistics

Server Performance

Alerts from Virus Attack


32/101


33/101



2.4.5 Database Software and Development Tools:

The bidder MUST procure and install database software. The bidder MUST also provide the user-friendly tools with GUI features to interactwith Database.

2.4.6 Business Application Software:

The proposed modules in the application have been identified. However, the modules to be deployed in FCS may or may not have samemodular demarcation; but it should certainly cater to all the functionalities identified in Scope and FRS of the RFP.

The application software components should be simple to use. The total set of software components MUST be uniform in their User interface,being consistent in their use and meaning of keystrokes and sequences and in their visual presentations to the User. The User interface should begraphical (i.e. GUI) in nature.

The indicative list of operational functionality, the application MUST provide is as follows:

The application MUST be multi-userHelp facility through use of Function keys

Prompt facility in searching for the correct code for coded parameters

Ability to discard all data when the transaction is incomplete (Should not save)

Ability to carry forward data from a previous screen

An audit trail for all transactions

Procedures for data exchange with interfaced applications

Must have the facility for Edit

During the implementation and commissioning, circumstances may arise when some of the functions (applications) at site have beencomputerized and some are still manual. The bidder MUST state how the proposed applications will function in this interim period and howthe applications will cater for circumstances where a site that is computerized or manual will communicate with other computerized or manualsites

FCS G P RFP A 7 4 (T )


34/101



2.5 SYSTEM MANAGEMENT ,ADMIN ISTRATI ON, AND SECURIT Y SPECIFI CATI ONS

2.5.0 General Requirements:

In addition to the management, administration, and security requirements specif ied in each sections covering the various hardware and softwarecomponents of the System, the System must also provide for the following management, administration, and security features at the overallsystem level.

System installation procedures should be self explanatory, menu driven and should require minimum user interaction. A detail on-line help forinstallation should also be provided. Installation procedure should set all the required system parameters for successful installation of the system.The bidder should take into account ease of deployment for while proposing a solution.

The Bidder shall preferably follow best practices of BS7799 Certif ication or equivalent for security.

2.5.1 Facili ty M anagement and Administration

The Facility Management operations shall include the following tasks

Configuration of server parameters, operating systems administration and tuning

Operating system administration, including but not limited to management of users, processes, resource contention, preventive maintenanceand management of upgrades including migration to higher versions and patches to ensure that the system is properly updated.

Re-installation in the event of system crash/ failures

Maintenance of a log of the performance monitoring of servers including but not limited to monitoring CPU, disk space, memory utilization,I/ O utilization, etc.

Event log analysis generated in all the sub systems including but not limited to servers, operating systems, databases, applications, securitydevices, messaging, etc.

Ensuring that the logs are backed up and truncated at regular intervals

Periodic health check of the systems, troubleshooting problems, analyzing and implementing rectification measure

Ensuring the upkeep of existing systems that would be reused and also incorporate necessary changes for new applications if any during thetenure of the contract

FCS G P RFP A 7 4 (T )


35/101



Troubleshooting issues in the infrastructure, network and application to determine the areas where fixes are required and ensuring resolutionof the same.

Identification, diagnosis and resolution of problem areas pertaining to the Server farm infrastructure and application and maintenance ofassured SLA levels.

Implementation and maintenance of standard operating procedures for maintenance of the infrastructure.

Management of the user names, roles and passwords of all the relevant subsystems, including, but not limited to servers, applications,devices, etc.

System administration activit ies shall include the following tasks but not limited to the following -

Configuring and apportioning storage space

Management and integration of databases

Implementing security on the Internet / Intranet

Setting up of firewalls and authorization systems

Performing periodic backup and archiving of data and automating reporting tasks

Executing hardware and software updates when necessary.

The Facil it y management activit ies shall also include the following configuration management processes to track IT assets

Providing Information on the IT infrastructure

o To all other processes

o IT Management

Enabling control of the infrastructure by monitoring and maintaining information on

o All the resources that need to deliver services

o Status and history of Configuration Items (CI) or I T Assets and their relationship with other IT Assets

2.5.2 Storage and Database Administration

The vendor shall administer the databases which have been setup in the server farm and provide a repository of information for BusinessCritical applications. Database Administration involves data backups & restores and monitoring the database server.

FCS EGOVERNANCE PROJECT RFP ANNEXURE 7 4 (TECHNICAL SPECIFICATIONS)


36/101



Storage and Database administration activities shall include the following

Installation and configuration of the storage system.

Management of storage environment to maintain performance at desired optimum levels.

Development of storage management policy, configuration and management of disk array, SAN fabric / switches, tape library, etc.

Configuration of SAN whenever a new application is hosted at the server farm. This shall include activities such as management of storagespace, volume, RAID configuration, zone, security, business continuity volumes, NAS, performance, etc.

End-to-end management of database on continuous basis to ensure smooth functioning of the same

Management of any changes to database schema, disk space, storage, user roles

Review of Code of Conduct and configuration to improve performance of the application or to resolve bottlenecks if any.

Performance monitoring and Databases on a regular basis including, preventive maintenance of the database as required.

Applying patches and database upgrades as and when required with minimal downtime.

Regular backups for all databases in accordance with the backup and archive policies and conduct recovery whenever required withappropriate permissions.

Use of DBA tools related to performing database creation, maintenance, and database monitoring tasks

2.5.3 Network Monitoring and Administration

Network Monitoring and administration activities shall include the following

Monitoring and administering the LAN up to the integration points with WAN.

Creation and modification of LANs, assignment of ports to appropriate applications and segmentation of traffic.

Coordination with vendor for break fixes maintenance of the LAN cabling.

2.5.4 Backup and restore

The backup and restore functions will comprise of the following activities Backup of operating system, database and application as per stipulated policies at the Server Farm.

Monitoring and enhancement of the performance of scheduled backups, schedule regular testing of backups and ensure adherence torelated retention policies.



37/101



Ensuring prompt execution of on-demand backups of volumes, files and database applications whenever required by User Departments orin case of upgrades and configuration changes to the system.

Real-time monitoring, log maintenance and reporting of backup status on a regular basis. Prompt problem resolution in case of failures inthe backup processes.

Media management including, but not limited to, tagging, cross-referencing, storing, logging, testing, and vaulting in fire proof cabinets.

Physical security of the media stored in cabinets.

Ongoing support for file and volume restoration requests at the Server Farm.

2.5.5 Server Management

The vendor shall perform all system administration tasks like server management and operating system administration, user management, devicemanagement etc. The vendor shall ensure high availability of System resources to the users and to maximize the uptime of the system bydiagnosing, detecting and rectifying the faults in time.

The Server Administration for any platform will comprise of the following activities Start ing/ Shutdown servers or services at Server Farm

Monitoring performance of server resources (CPU Usage, Memory, disks)

Monitoring access logs and application logs

Purging of files and logs

Taking data backup and restoration

Applying service packs, fixes, updates and security patches

Providing helpdesk related administrative support

The minimum qualification of the person will be degree / equivalent with 2 years relevant experience

Server Management operations will comprise of the following

Monitoring of software licenses and identification of software license procurement or up-gradation

Providing and maintaining user access controls creation, modification or deletion of access/ authentication and administrative rights onservers as per defined access policy.

Maintaining data access security



38/101



Deployment, Monitoring and updating of Anti-virus software on servers

Coordinating with Anti-virus service provider for support for virus attacks and resolution.

2.5.6 Change Management

As the organization goes through changes IT infrastructure will also change from time to time to meet the changing needs of the businesses.

Proper change management will ensure that approved changes are implemented efficiently and with acceptable risk to the existing and to thenew IT Services with minimal impact on the operations of FCS. Change management would include the following tasks

Change management has to be approved by the authorized officials of FCS

Tracking the changes in hard / soft conf igurations, changes to applications, changes to policies, applying of upgrades / updates / patches,etc.

Plan for changes to be made - draw up a task list, decide on responsibilities, coordinate with all the affected parties, establish and maintaincommunication between parties to identify and mitigate risks, manage the schedule, execute the change, ensure and manage the portchange tests and documentation.

2.5.7 Technical management and troubleshooting:

The bidder MUST provide a detailed plan for technical management and troubleshooting.

Recovery and auto-roll back of data: There should also be re-scheduling capabilities for automatic retries and restart logic (e.g. batchprocessing)

Audit trails and logs maintenance capabilities

The bidders will provide the backup frequency and recovery plan. The application system should also support the replication of the

centralized system to the disaster recovery site, as and when the site comes up. A combination of full (on Tape Media) and incremental(Day-time) backups should be employed to ensure disaster tolerance. The bidder MUST provide the backup and recovery plan.

The bidder MUST provide an Industry Standard BCP/ Disaster Recovery plan.

2.5.8 User and usage administrati on:

The bidder MUST clearly state the access controls, for on-line PCs applications connected to the centralized server, which ensures that:

FCS EGOVERNANCE PROJECT - RFP - ANNEXURE 7 4 (TECHNICAL SPECIFICATIONS)


39/101



Only authorized personnel are allowed to access the system; access being restricted via the use of user names/ identif ications andassociated password.

Access to each application is restricted to specified authorized users

The user in the application system is logged off automatically if the user is idle for morethan a specif ied and variable period, to preventaccess to the system, applications etc. by unauthorized third parties when a terminal is left unattended.

2.6 SERVICE SPECIFICATIONS

2.6.1 System I ntegration:

The application and systems have been identified based on the existing structure of FCS and its existing IT applications.The bidder is required to design the system in such a way so as to provide fully integrated system with functionalities, at the minimum, asmentioned inthe FRS in this RFP. It is expected that the application system will cater to the workflow requirements, wherever necessary.

The system will be developed and implemented as a turnkey project, and thus bidder will also have to perform the role of systems integrator.

The bidder MUST provide for integrating the existing/ proposed systems with the solution provided. The bidder will coordinate and provide allnecessary support to any vendor whenever needed during the execution of this assignment. Bidders MUST also specify the infrastructurerequirements, if any, for the successful execution of the assignment.

2.6.2 Infrastructure Service requirements:

Software Updates:

An important requirement of the FCS project is to update the system software, patch installation etc. This services is not only limited to systemsoftware but also includes all the software required to run the system successfully.

2.6.3 Training and Training Materials:

2.6.3.1 User Training:

The indicative training needs, but not limited to, depending on the role of user of the systems, is as follows:



40/101



End users:

o Application usageo Intraneto Basic Computer Training.o Training on Basic Hardware & Network Problems and their solutions.o Defect logging systemo Etc.

Helpdesk:

o Application usageo Intraneto Defect logging systemo Defect tracking and resolutiono Troubleshootingo Etc.

2.6.3.2 Technical:

Technical training will ensure that the FCS staff is well trained to manage the system in long run. The indicative training need, depending on therole of personnel or technical groups:

Application System support group:

o Installation of application systemo Parameter tuningo Application design, logic and usageo Configuration Managemento Performance tuning of applicationso Client server architectureo Structured system development methodologyo Language used for codingo Etc.

Database Administration Group:



41/101

FCS EGOVERNANCE PROJECT RFP ANNEXURE 7.4(TECHNICAL SPECIFICATIONS)


o Database installationo Security maintenanceo Parameter tuningo Creating and maintaining the database objectso Performance tuningo Database designo

Backup/ recovery/ restart procedureso System start-up/ shutdown procedureso Client/ Server architectureo Database administrationo Data Conversion, Migration and Validation and their tools, if any

Operations and Facilities Management group:

o Server managemento System administrationo System operations and maintenance

o Backup and recovery managemento Security maintenanceo Installation of hardware and softwareo Etc.

Network Administration Group:

o Network installationo Network performance tuningo Network configuration managemento Network configuration backup and restoration

o Network architecture and zoningo Network administrationo Network monitoring

Security Administration Group:

o Security devices installationo Security configuration managemento Secure network architecture

FCS EGOVERNANCE PROJECT - RFP - ANNEXURE 7.4 (TECHNICAL SPECIFICATIONS)


42/101



o Monitoring security logso Installation of security patcheso Applying AV signatures updates

2.6.3.3 Management:

The management training will include project management, operation of the new system and functions of the new system. The indicativetraining needs are as follows:

Application usage

MI S Report analysis

Query Generation

Defect Prevention

Quality Management System

Etc.

The Final training plan will be prepared by the selected vendor in consultation with FCS. FCS will assess the quality, relevance andcomprehensiveness of the training materials/ tools.

2.6.4 Technical Support:

2.6.4.1 Warranty Service:

The bidder MUST warrant that all the deliverables provided under this bid will be free from defects in design, materials and workmanship forthe warranty period. If any issues remain outstanding at the end of the warranty period, the warranty period will be extended unti l FCS issatisfied with the resolution of the issues.

The bidder MUST identify a Warranty Manager who will be the primary point of contact for FCS during the warranty period and who willhave the authority to take any action necessary to resolve any warranty related issues.

Throughout the acceptance and warranty period the bidder MUST provide, but not limited to the following:

FCS EGOVERNANCE PROJECT - RFP - ANNEXURE 7.4 (TECHNICAL SPECIFICATIONS)


43/101



Provide resources at strategic location at various sites of FCS

Provide resources that are on call to support the developed application for 24 X 7.

Provide onsite or on call resources as required by FCS for other special situations.

The bidder MUST provide reporting strategy plan in the bid. This plan should include the actions that the bidder will take, on daily basis(if needed), to resolve all the identified problems.

2.6.4.2User support / Hot line:

The bidder MUST nominate staff at Bhopal for their permanent support centre at FCS. The support centre will be responsible for, but notlimited to the following:

Performing effective maintenance during and after the warranty period.

Acting as a help desk to provide operational support.

Coordinating with other vendors, if required, for the resolution of the reported problems.

2.6.4.3Maintenance services:

The bidder will provide comprehensive maintenance service for these systems after the warranty has ended. The AMC period will be for 2 years,on expiry of warranty for initial 3 years from the Go-Live date.

The maintenance service will include, but not limited to:

Equipment maintenance, such as repairs, changes, modifications etc.

Application system maintenance such as changes, modifications, bug fixing etcAll Software maintenance such as upgrades, reinstallations

Provide resources that are on call to support the developed application for 24 X 7.

Provide onsite or on call resources as required by FCS for other special situations.

The bidder MUST provide reporting strategy plan in the bid. This plan should include the actions that the bidder will take, on daily basis(if needed), to resolve all the identified problems etc.



44/101

( )


2.7 DOCUMENTATION REQUIREMENTS

2.7.1 End-User documents:

Documentation will be supplied and maintained by the bidder during different stages of the project. The ownership of all documents, suppliedby the bidder, will be with FCS. The electronic copies will be supplied with all the documents and manuals, required for operating and

configuring the hardware and software at the user specific environment. The documents have to be provided in English and Hindi and MUST include at least:

User Documentation including user guide and procedures manuals for hardware and software

Software installation guide including the configuration of the database etc

User will have the rights to duplicate the hardcopy and soft copy for the documents created by the bidder without any financial and legalimplications.

Note: At least 2 soft copies (in CD) and three hard copies of all the documents to be provided by the bidder.

2.7.2 Technical Documents:

The bidder shall supply operation and maintenance manuals together with the drawings of goods and equipments. These shall be in such detailsas to enable FCS to operate, maintain, adjust and repair the parts of the works as stated in the specifications. The manuals and drawings, for allsupplied equipments, shall be in English and/ or Hindi and in soft and/ or hard copy and equal to the number of supplied equipments.

Indicative list of documents, not l imited to, that wil l be supplied and maintained by the bidder during different stages of the project are:

System Manual for Server, Storage & other hardware.

Operating System ManualDatabase Manual

Application System Requirement Specification (SRS)/ Application Customization Requirements Specif ication (CRS)

Application Integration Requirements

Gap Analysis Document (if applicable)

Plan for digitization and data entry



45/101

( )


Application Software Design Document (SDD)

Coding standard guidelines

Trouble Shooting document

Installation Manual

Operational Procedures ManualAcceptance Test Plan

Acceptance Test Specifications

Detailed Network diagram which includes both LAN and WAN

Secure Network architecture diagram

Documented configuration of all network devices e.g. routers, switches etc.

Documented configuration of all security devices e.g. firewall, IDS/ IPS etc.

Other relevant technical documentation etc.

Any updates to the documents MUST be made available to FCS to support any changes to requirements, design, etc. All deliverables preparedby the bidder for this assignment and submitted to FCS will be final after the approval provided by FCS.

2.8 OTHER NON-ITGOODS

2.8.1 Power Supply and Backup

UPS Requirement

Power should be supplied from dual redundant parallel UPS with input and output isolation transformers. The electrical system should bedesigned to incorporate 100% spare capacity in-order to provide for adequate redundancy for continuous and uninterrupted Power Supply.Power redundancy should be available up to the rack level i.e. from two power sources.

The UPS should be located at close proximity to the server room to limit the neutral to earth potential to fewer than 2 volts, which is essentialfor the clean power requirements for servers. Minimum 3hrs battery back-up is required.

The tentative scope of equipments & items under this head of works includes the following:



46/101


Copper power cabling from Main LT panel to the UPS, UPS output to UPS distribution panel, UPS distribution panel to PDU and toserver racks.

UPS input, output & distribution panel.

T E ST I N G & Q A RE Q U I R E M E N T S

3.1 INSPECTIONS

3.1.1 Factory Inspections:

Bidder shall provide the factory inspection report for quality assurance as per prevailing industry standards and practices for each type of item.The goods will be accepted only after verifying the factory inspection report by FCS.

3.1.2 Inspections following delivery:

FCS will conduct a thorough physical inspection of all the products delivered to ensure that they arrive at the sites in good condition and arefree from physical damage including but not limited to crushed or broken equipments, missing seals, opened packages and incompleteshipments. FCS reserves the right to return the products to the bidder at the bidders expense.

Physical inspection of hardware will also include physical checking, unpacking and counting of the delivered equipment by FCS staff in presenceof the bidder. This equipment will only be acceptable as correct when each received item corresponds with the checklist that will be prepared bythe bidder prior to shipment. Any shortfalls in terms of number of items received may render the delivered equipments incomplete.

.

3.2 PRE-COMMI SSION IN G TESTS


47/101



48/101


The bidder MUST indicate how one will demonstrate to FCS that all applications installed in the system have been tested.

3.3 OPERATIONAL ACCEPTAN CE TESTS

3.3.0 FCS (with the assistance of the bidder) will perform the following tests on the System and its Subsystems following Installation todetermine whether the System and the Subsystems meet all the requirements mandated for Operational Acceptance.

3.3.1 Testing Methodology/ Techniques

Please refer section 3.2.0 for testing methodology/ techniques.Successful completion of the contract will be gauged through a series of formal acceptance tests performed on all aspects of the system/ subsystems as mentioned in 3.3.1.

Database TestVerify complete and correct installation of Database Management System

Data Integrity Testing

Data Sampling

Database Back-up & Recovery Testing

Query Testing

Database Connection Test (Determine if the database server will be able to sustain the expected number of connections) etc.

Functionality TestTest that the functional requirements specified in all the modules are met.

All functions MUST be tested when user provide inputs with correct and incorrect inputsTesting of Formats etc.

Unit TestEach module or Component should to be fully tested independently before integration etc.

System Test



49/101


All specified functionality should exist. This testing verifies the as-built program's functionality and performance with respect to therequirements for the software product.

All System functions that are accessed through menus should be tested

Defect test: Test software defects before implementation

House Keeping functions like archiving

Easy to use: Graphical user interface as per requirement specification

Server, Storage system etc. shutdown and power up test

System backup and restoration test etc.

Security TestIT audit of application from External auditors.

Real Time Security monitoring.

Reviewing and Evaluating the Security Controls etc.

SecurityAttempt to break the password

Time out facility on dormant menu/ screen. To continue using the open screens the user MUST re-login.

Reviewing and Evaluating the Security Controls etc.

Stress TestFinding errors that will show themselves under certain combinations of events or data values

Heavy repeating of certain actions or inputs

Time Test To determine if individual business transactions run to completion in a reasonable amount of time

etc.

Reliability TestingTesting the system for prolonged use at varying levels, or, possibly, constant value at peak level etc.



50/101


Performance TestingTesting to probe the system against prescribed timing etc.

Consistency TestingTest the consistency of data and results across the applications etc.

Recovery TestingTesting the response of the system to failures of all sorts including but not limited to power failure etc.

Audit TrailTracking crit ical transactions

Logging all critical errors etc.

Multi-User CapabilityTest that the application system can support several users etc.

Help Information TestingTesting for help information that will be verified for detail and presentation etc.

Limit TestingTest as to how the system reacts to data which is maximal or minimal in the sense of attaining limit

The system will be tested beyond the limits specified to verify whether sufficient margins have been built in etc.

Volume TestTest to submit the system to large volumes of data etc.

System I ntegration TestTesting Components and Component Integration

Testing System Interfaces



51/101


After each system has been fully integrated to create a larger system, each module or sub-system MUST have a defined interface which willbe used to call another program component

Parameter interface: Data and function references are passed from one component to another.

Procedure interface: One sub-system encapsulates a set of procedure which is called by other sub-system

Message passing interface: One sub-system request a service from another sub-system.

Validation (Completeness)

Robustness Testing

Testing for 24x7 availability

Error Detection & Recovery Testing

Measuring response time, throughput and availability

Monitoring Resource Utilization

Data Conversion

Compatibi li ty and Configuration TestingOperating System and Data Base Compatibility

Hardware and Network Compatibility

Checking Compliance with Standards

Test the compatibility of data to the higher version, as and when applicable

Storage TestingTesting to detect instances when the system exceed the specified limits (e.g. processing or supplying large volume of data) etc.

Installation TestingThe ease of installation will be checked

Where installation counts are applicable, the number of installations specified will be tested. The system will be checked for a highernumber of installations than specified, also to uninstalled to check if the installation count is reduced


52/101



53/101


The acceptance tests shall demonstrate that the bidder has met each and every requirement specified within the contract and has delivered aneffective operational system.

Complete System Acceptance (UAT)

At the end of the System Acceptance period, FCSwill acknowledge complete system acceptance in writing to the bidder upon completion of thefollowing:

All required activities as defined in the bid document including all changes agreed by FCSand delivered by the bidder and accepted by FCS

All required system functionality as defined in the bid document including all changes agreed by FCS and delivered by the bidder andaccepted by FCS

All required documentation as defined in this bid document including all changes agreed by FCS and delivered by the bidder and acceptedby FCS

All required training as defined in this bid document including all changes agreed by FCSand delivered by the bidder and accepted by FCS

All identified shortcomings/ defects in the systems have been addressed to complete satisfaction of FCS

The bidder MUST agree to above criteria for complete system acceptance and further agree that:

In order to accept the system, FCSMUST be satisfied that all of the work has been completed and delivered to complete satisfaction of FCSand that all aspects of the system perform acceptably. The functional/ logical acceptance of the system will only be certified when the proposedsystem is installed and configured at the sites according to the design and that all the detailed proceduresof operating them have been carriedout by the bidder in the presence of FCSstaff

NOTE: The acceptance test of the application system will be conducted with the live/ actual data.



54/101


HARDWARE SPECIFICATIONS& PH YSICAL REQUIREMENTS(DC)

Following are the minimum indicative specifications for each component at DC.T he infr astructur e required at D R would be repli ca of D C wi thout highavailability.

1. Web Server (Blade Server):

Make And Model To be specified by the vendorProcessor 2.5Ghz or higher latest generation x86 based processor` Up to 2 Nos. ProcessorsCache Maximum cache available with the processorExpansion Slots Minimum 2 PCI-E I/ O Expansion SlotsMain Memory Capacity(Scalability)

Scalable to 64 GB fully buffered DDR2 memory

Main Memory 16 GB fully buffered DDR2RAS Features Hot Pluggable Disk Drives

Redundant Power SupplyRedundant hot swappable fansError Correction and Parity CheckingRAID 0 and 1 Support

Hard Disks 2 Nos. Hot-swap 146 GB SAS/ SCSI Disk Drives.RAID Integrated RAID offering Striping, Mirroring (RAID 0, 1)Network Interface Card Minimum 2Nos. 10/ 100/ 1000 Mbps Ethernet ports

USB Minimum 1 USB 2.0 ports or a facility for connecting USB devicesOperating System Windows/ LinuxSupport 3 year Onsite Warranty with Parts exchange/ replacement, Same

Business Day Response basis, regular working hours/ days



55/101


2. Application Server (Blade Server)

Make And Model To be specified by the vendorProcessor 2.5Ghz or higher latest generation x86 based processor

` Up to 2 Nos. ProcessorsCache Maximum cache available with the processorExpansion Slots Minimum 2 PCI-E I/ O Expansion SlotsMain Memory Capacity(Scalability)



Redundant Power SupplyRedundant hot swappable fansError Correction and Parity Checking

RAID 0 and 1 SupportHard Disks 2 Nos. Hot-swap 146 GB SAS/ SCSI Disk Drives.RAID Integrated RAID offering Striping, Mirroring (RAID 0, 1)Network Interface Card Minimum 2Nos. 10/ 100/ 1000 Mbps Ethernet portsUSB Minimum 1 USB 2.0 ports or a facility for connecting USB devicesOperating System Windows/ LinuxSupport 3 year Onsite Warranty with Parts exchange/ replacement, Same

Business Day Response basis, regular working hours/ days



56/101


3. Database Server -

Make And Model To be specified by the vendorProcessor RISC/ EPIC based 64-bit processor latest generation

processorNo of Processors Minimum 4 Processors scalable to 8 processorsCache Maximum as available with the processorExpansion Slots Minimum 4 PCI-E I/ O Expansion Slots supporting a mix of

4 lane and 8 lane PCI-E SlotsMain Memory Capacity (Scalability) Scalable to 64 GB fully buffered DDR2 memoryMain Memory 32 GB fully buffered DDR2RAS Features Hot Pluggable Disk Drives

Redundant Power SupplyRedundant hot swappable fans

Error Correction and Parity CheckingRAID 0 and 1 SupportHard Disks 4 Nos. Hot-swap 146 GB SAS/ SCSI Disk Drives.Hard Disk Scalability 8 hot swap SAS/ SCSI HDDRAID Integrated on-board RAID offering Striping, Mirroring

(RAID 0, 1)Optical Drive Internal DVD DriveNetwork Interface Card Minimum 4 Nos. 10/ 100/ 1000 Mbps Ethernet ports

Support for 10Gbps TechnologyHBA 2 x 4 Gb Dual port Fiber Channel HBAs (should be

compatible with SAN Infrastructure)Serial One DB-9 portUSB Minimum 2 USB 2.0 ports or provision to connect with USB

devicesPower Supply Dual Redundant Hot-Swappable Power Supplies

Operating SystemEnterprise class Unix operating system for 64-bit RISC/EPIC processor

Design standard and Safety standard Service Processor providing: DMTF CLP-based CLI overSSH, Web-based GUI over HTTPS/ HTTP, IPMI 2.0, SNMP



57/101


V1, v2c and v3, remote graphical access over Ethernet andremote storage over Ethernet

Support 3 year Onsite Warranty with Partsexchange/ replacement,Same Business Day Response basis,regular working hours/ days

4. Portal Server (Blade Server)

Make And Model To be specif ied by the vendorProcessor 2.5Ghz or higher latest generation x86 based processor` Up to 2 Nos. ProcessorsCache Maximum cache available with the processorExpansion Slots Minimum 2 PCI-E I/ O Expansion SlotsMain Memory Capacity(Scalability)


Main Memory 16 GB fully buffered DDR2

RAS Features Hot Pluggable Disk DrivesRedundant Power SupplyRedundant hot swappable fansError Correction and Parity CheckingRAID 0 and 1 Support

Hard Disks 2 Nos. Hot-swap 146 GB SAS/ SCSI Disk Drives.RAID Integrated RAID offering Striping, Mirroring (RAID 0, 1)Network Interface Card Minimum 2Nos. 10/ 100/ 1000 Mbps Ethernet portsUSB Minimum 1 USB 2.0 ports or a facility for connecting USB devicesOperating System Windows/ Linux

Support 3 year Onsite Warranty with Parts exchange/ replacement, SameBusiness Day Response basis, regular working hours/ days



58/101


5. Test & Development Server (Blade Server)

Make And Model To be specified by the vendorProcessor 2.5Ghz or higher latest generation x86 based processor` Up to 2 Nos. Processors

Cache Maximum cache available with the processorExpansion Slots Minimum 2 PCI-E I/ O Expansion SlotsMain Memory Capacity(Scalability)



Redundant Power SupplyRedundant hot swappable fansError Correction and Parity CheckingRAID 0 and 1 Support

Hard Disks 2 Nos. Hot-swap 146 GB SAS/ SCSI Disk Drives.RAID Integrated RAID offering Striping, Mirroring (RAID 0, 1)Network Interface Card Minimum 2Nos. 10/ 100/ 1000 Mbps Ethernet portsUSB Minimum 1 USB 2.0 ports or a facility for connecting USB devicesOperating Syste