Tender Reference No: F 4.3 (162)/RISL/Tech/2014/6250 dated 19/09/2014

Request for Proposal (RFP) Document for

Selecting Agency for Setting up and Maintenance Support of Cloud Solution in Rajasthan State Data Centre (RSDC)

Tender Reference No: F 4.3 (162)/RISL/Tech/2014/6250 dated 19/09/2014

Procuring Authority Managing Director,

RISL, First Floor, C-Block, Yojana Bhawan, Tilak Marg, C-Scheme, Jaipur-302005 (Rajasthan)

Date & Time of Pre-bid meeting 30-09-14 at 11:00 AM

Last Date & Time of Submission of Bid 13-10-14 at 03:00 PM

Date & Time of Opening of Technical Bid 13-10-14 at 05:00 PM

Bidding Document Fee: Rs. 1000 only (Rupees One Thousand only)

Name of the Bidding Company/ Firm: Contact Person (Authorised Bid Signatory): Correspondence Address:

Mobile No. Telephone

& Fax Nos.: Website & E-Mail:

RajCOMP Info Services Limited (RISL)

First Floor, Yojana Bhawan, C-Block, Tilak Marg, C-Scheme, Jaipur-302005 (Raj.) Phone: 0141- 5103902 Fax: 0141-2228701

Table of Contents

Sr. No Type Page Number

1 INVITATION FOR BID (IFB) & NOTICE INVITING BID (NIB) 8 2 PROJECT PROFILE & BACKGROUND INFORMATION 11

3 ELIGIBILITY CRITERIA 14

4 SCOPE OF WORK, DELIVERABLES & TIMELINES 17

5 INSTRUCTION TO BIDDERS (ITB) 28

6 GENERAL TERMS AND CONDITIONS OF TENDER & CONTRACT 49 7 SPECIAL TERMS AND CONDITIONS OF TENDER & CONTRACT 62

Annexure

1 ANNEXURE-1: BILL OF MATERIAL (BoM) 75

2 ANNEXURE-2: FUNCTIONAL REQUIREMENT SPECIFICATIONS 76

3 ANNEXURE-3: PRE-BID QUERIES FORMAT 90

4 ANNEXURE-4: BIDDER’S AUTHORIZATION CERTIFICATE 91

5 ANNEXURE-5: SELF-DECLARATION 92

6 ANNEXURE-6: CERTIFICATE OF CONFORMITY/ NO DEVIATION 93

7 ANNEXURE-7: DECLARATION BY BIDDER 94

8 ANNEXURE-8: MANUFACTURER’S AUTHORIZATION FORM (MAF) 95 9 ANNEXURE-9: UNDERTAKING ON AUTHENTICITY OF

COMPUTER EQUIPMENTS

96

10 ANNEXURE-10: COMPONENTS OFFERED – BOM 97

11 ANNEXURE-11: FINANCIAL BID COVER LETTER & FORMAT 98

12 ANNEXURE-12: BANK GUARANTEE FORMAT 103

13 ANNEXURE-13: DRAFT AGREEMENT FORMAT 105

14 ANNEXURE-14: MEMORANDUM OF APPEAL UNDER THE RTPP ACT, 2012

108 15 ANNEXURE-15: FORMS FOR FILING THE TECHNICAL BID 109

ABBREVIATIONS & DEFINITIONS

Act The Rajasthan Transparency in Public Procurement Act, 2012 (Act No. 21 of 2012) and Rules thereto

Authorised Signatory The bidder’s representative/ officer vested (explicitly, implicitly, or through conduct) with the powers to commit the authorizing organization to a binding agreement. Also called signing officer/ authority having the Power of Attorney (PoA) from the competent authority of the respective Bidding firm.

AAA Authentication, Authorization and Accounting

ACL Access Control List

ARP Address Resolution Protocol

AQP Agreed Quarterly Payment

BG Bank Guarantee

BGP Border Gateway Protocol

Bid A formal offer made in pursuance of an invitation by a procuring entity and includes any tender, proposal or quotation

Bid Security A security provided to the procuring entity by a bidder for securing the fulfilment of any obligation in terms of the provisions of the bidding documents. Bidder Any person/ firm/ agency/ company/ contractor/ supplier/ vendor participating

in the procurement/ bidding process with the procurement entity

Bidding Document

Documents issued by the procuring entity, including any amendments thereto, that set out the terms and conditions of the given procurement and includes the invitation to bid

BoM Bill of Material

CMC Contract Monitoring Committee

Competent Authority An authority or officer to whom the relevant administrative or financial powers have been delegated for taking decision in a matter relating to procurement. MD, RISL in this bidding document.

Contract/ Procurement Contract

A contract entered into between the procuring entity and a successful bidder concerning the subject matter of procurement

Contract/ Project Period

The project period would be 3 years from date of Final acceptance of the Cloud Enablement components by the State

COTS Commercial Off The Shelf Software

CPU Central processing Unit

Day A calendar day as per GoR/ GoI.

DCO Data centre Operator

DCCO Data Centre Cloud Operator

DeitY, GoI Department of Electronics and Information Technology, Government of India

DMZ Demilitarized Zone

DNS Domain Name Server

DoIT&C Department of Information Technology and Communications, Government of

Rajasthan.

EMS Enterprise Management System

FC Fiber Channel

FCIP Fiber Channel over IP

FTP File Transfer Protocol

FAT Final Acceptance Test

G2B Government to Business

G2C Government to Citizen

GBIC Giga Bit interface

Gbps Gigabits per second

GE Gigabit Ethernet

GHz GigaHertz

GUI Graphical User Interface

H/W Hardware

HDD Hard disk drive

HIPS Host Intrusion Prevention System

HTML Hypertext Markup Language

ETDC Electronic Testing & Development Center

FOR/ FOB Free on Board or Freight on Board

GoI/ GoR Govt. of India/ Govt. of Rajasthan

Goods

All articles, material, commodities, electricity, livestock, furniture, fixtures, raw material, spares, instruments, software, machinery, equipment, industrial plant, vehicles, aircraft, ships, railway rolling stock and any other category of goods, whether in solid, liquid or gaseous form, purchased or otherwise acquired for the use of a procuring entity as well as services or works incidental to the supply of the goods if the value of services or works or both does not exceed that of the goods themselves

I/O Input Output

ICT Information and Communication Technology. IDS Intrusion Detection System

IEEE International electrical and electronics engineers

IFB

Invitation for Bids (A document published by the procuring entity inviting bids relating to the subject matter of procurement and any amendment thereto and includes notice inviting bid and request for proposal)

INR Indian Rupee

IP Internet Protocol

IPS Intrusion prevention System ISI Indian Standards Institution

ISO International Organisation for Standardisation

IT Information Technology

ITIL Information Technology Infrastructure Library

ITB Instruction to Bidders

Kbps Kilobits per second

L2 Layer2

LACP Link Aggregation Protocol

LAN Local Area Network

LD Liquidated Damages

LoI Letter of Intent

LUN Logical Unit Number

MAC Media Access protocol

Mbps Megabits per second

NAT Network Address Translation

NCB A bidding process in which qualified bidders only from within India are allowed to participate

NeGP National e-Governance Plan of Government of India, Department of

Information Technology (DIT), Ministry of Communications and Information Technology (MCIT), New Delhi.

NIB Notice Inviting Bid

NOC Network Operation Center

Notification A notification published in the Official Gazette

OEM Original Equipment Manufacturer

OFC Optical fiber Channel

OS Operating System

PAN Permanent Account Number

PBG Performance Bank Guarantee

PC Procurement/ Purchase Committee

PQ Pre-Qualification

Procurement Process

The process of procurement extending from the issue of invitation to bid till the award of the procurement contract or cancellation of the procurement process, as the case may be

Procurement/ Public Procurement

The acquisition by purchase, lease, license or otherwise of works, goods or services, including award of Public Private Partnership projects, by a procuring entity whether directly or through an agency with which a contract for procurement services is entered into, but does not include any acquisition without consideration, and “procure” or “procured” shall be construed accordingly

Project Site Wherever applicable, means the designated place or places.

PSD/ SD Performance Security Deposit/ Security Deposit

Purchaser/ Tendering Authority/ Procuring Entity

Person or entity that is a recipient of a good or service provided by a seller (bidder) under a purchase order or contract of sale. Also called buyer. RISL in this RFP document.

QoS Quality of Service

RajSWAN/ RSWAN Rajasthan State Wide Area Network

RDBMS Relational database management system

RISL RajCOMP Info Services Limited

RSDC Rajasthan State Data Centre, New IT Building, Jaipur

RVAT Rajasthan Value Added Tax

S/W Software

SAN Storage Area Network

SAS Small Form Factor Pluggable

Services

Any subject matter of procurement other than goods or works and includes physical, maintenance, professional, intellectual, consultancy and advisory services or any service classified or declared as such by a procuring entity and does not include appointment of any person made by any procuring entity

SLA

Service Level Agreement is a negotiated agreement between two parties wherein one is the customer and the other is the service provider. It is a a service contract where the level of service is formally defined. In practice, the term SLA is sometimes used to refer to the contracted delivery time (of the service) or performance.

SNMP Simple Network Management Protocol

SI System Integrator

SSDG State Services Delivery Gateway

State Government Government of Rajasthan (GoR)

State Public

Procurement Portal http://sppp.raj.nic.in

STQC Standardisation Testing and Quality Certification, Govt. of India

Subject Matter of

Procurement Any item of procurement whether in the form of goods, services or works

TB Terra Byte

TIN Tax Identification Number

TPA Third Party Auditors

VAT/ CenVAT Value Added Tax/ Central VAT

VLAN Virtual Local Area Network

VPN Virtual private network

WAN Wide Area Network

2. PROJECT PROFILE & BACKGROUND INFORMATION

2.1. Under the National e-Governance Plan (NeGP), it is envisioned to “make all Government services accessible to the common man in his locality, through common service delivery outlets and ensure efficiency, transparency & reliability of such services at affordable costs to realize the basic needs of the common man”.

2.2. In order to make this vision a reality, the Government of India (GoI) recognized the potential of Information and Communication Technology (ICT) for rapid and all round development in general and transforming governance in particular. Initially there were islands of ICT initiatives at the National, State, district, and even block level. The learning’s by way of both the challenges and opportunities faced during the development and implementation of such initiatives contributed to refining the overall eGovernance strategy. One of the key learning’s that emerged was an urgent need to develop the core and other supporting infrastructure for sustaining e- Governance initiatives across the country.

2.3. The National e-Governance Plan (NeGP) has identified multiple mission mode projects along with various e-Governance initiatives at the State level to provide increased number of services electronically. The State Data Centers are being implemented to provide common IT infrastructure to host these planned e-Governance initiatives / applications. State Data Centers are one of the three infrastructure pillars structured by the NeGP to facilitate web-enabled Anytime, Anywhere access. State Data Centers are conceptualized with the objective of providing a common enabling infrastructure to the States to cater to their e-governance applications hosting requirements of the entire state governments and its departments. State Data Centre has been identified as one of the core infrastructure components to consolidate services, applications and infrastructure to provide efficient electronic delivery of G2G, G2C and G2B services. It will enable various State departments to host their services/applications on a common infrastructure leading to ease of integration and efficient management, ensuring that computing resources and the support connectivity infrastructure (SWAN/NICNET) is adequately and optimally used.

2.4. The State Data Centres (SDC) being established in the States/ UTs shall provide better operations & management control; minimize overall cost of Data Management, IT Management and Deployment through use of common infrastructure, which broadly includes:

i. Compute Infrastructure: To cater to the needs of application hosting at the State, an initial compute infrastructure consisting of web, application and database servers with different flavors of OS & database software’s has been provisioned in the SDC.

ii. Storage Infrastructure: Centralized storage with flexible and secure configuration shall be available in the SDC including backup facilities. The same shall be leveraged by different line departments for their data storage requirements in shared manner. Currently, the states have adequately provisioned for 5 years storage requirement.

iii. Network and Security Infrastructure: Core network infrastructure that is a requirement of every Data Centre has been provided for every SDC and has been designed with sufficient capacity to meet the basic needs of the State Data Center.

2.5. Substantial progress has been made in the SDC project. 21 SDCs have been operationalized and it is expected that most of the SDCs shall be operational by end of 2014. SDCs have been equipped with infrastructure which will enable State /UT departments with seamless, highly reliable/robust, shared and secured infrastructure with scalable capacity.

2.6. However, for a project of this nature it is prudent to assess the need for integrating latest but matured technology advancements to make them future proof for optimal utilization, Better Management and Monitoring.

2.7. To address issues typically faced by different departments at the State, such as long IT infrastructure procurement cycles, underutilization of resources, need for dynamic Scalability, appropriate disaster recovery of applications and data and for simplifying IT infrastructure provisioning & availability to line departments to cloud based service delivery in accelerated manner, to start with, it would be required to leverage the benefits of Cloud enabled services in State Data Centre.

2.8. It is in this context, that the SDC components have been analyzed with respect to following areas: Cloud Enablement

 Server Virtualization  Self Service provisioning

 Automation, Orchestration and Monitoring

2.9. After having analyzed the infrastructure at present provisioned in the SDC’s and technology advancements DeitY has thus initiated the process for implementing a Cloud based Service Delivery Model in each SDC, so that the SDC IT Infrastructure can be shared amongst multiple departments. Thus making the SDC as a Private Cloud operated for State and to be managed by a third party.

2.10. Following are the important characteristics of a well-managed cloud based service delivery model: i. On-demand self-service

- Line Departments can unilaterally provision computing capabilities ii. Broad network access

- Capabilities are available over the network - Accessed through standard mechanisms iii. Resource pooling

- Computing resources are pooled to serve multiple Line Departments - Location independence

iv. Rapid elasticity

- Capabilities can be rapidly and elastically provisioned

- Create a cascading effect of improved efficiency in increasing the number of services to be offered by various departments due to on demand availability of infrastructure. Departments can concentrate on their core competencies of providing related services and rely on the SDAs to deliver the required infrastructure.

v. Measured service

- Resource usage can be monitored, controlled, and report

- Create an IT governance mechanism within States as they leverage common / shared Platforms to speed up the process of service delivery.

2.11. This document is a Request for Proposal (RFP) for Bidders to quote for Setting up and Maintenance Support of Cloud Solution in Rajasthan State Data Centres (RSDC). The successful Bidder shall do the supply, installation, configuration, testing, training and support and do FAT as per the specifications and the specified scope of work

2.12. Post FAT completion, the Operations & Maintenance would be done by the selected SI for a period of 3 years from the date of final acceptance of the cloud enablement components by the state.

2.13. O & M Project period: The project period for O&M, post the FAT Completion, would be in line with five years of SDC Operational period. For the RSDC, the project period would be 3 years from date of Final acceptance of the Cloud Enablement components by the State.

2.14. For all purposes in the document, the term “Data Centre Cloud Operator (DCCO)” will be referred to as the entity responsible for the Operations & Maintenance of the SDC Cloud environment for the entire project period.

3. PRE-QUALIFICATION/ ELIGIBILITY CRITERIA

1) The Bidder must possess the requisite experience, strength and capabilities in providing the services necessary to meet the requirements as described in the RFP document. Keeping in view the complexity & volume of the work involved, the following criteria are prescribed as Pre-Qualification Criteria for Bidder interested in undertaking the project. The Bidder must also possess the Technical know-how and the Financial wherewithal that would be required to successfully provide the Cloud Solution and required support services sought by the State. The Bids must be complete in all respect and shall cover the entire scope of work as stipulated in the tender document. The invitation to Bid is open to all Bidders who qualify the eligibility criteria as given below:

S. No.

Basic Requirement

Specific Requirements Documents Required

1. Legal Entity The bidder should be a Proprietorship firm duly registered either under the Rajasthan Shops & Commercial Establishments Act, 1958 or any other Act of State/ Union, as applicable for dealing in the subject matter of procurement

(Note: A self-certified declaration regarding the non-applicability of registration to any Act should be submitted by the bidder)

OR

A company registered under Indian Companies Act, 1956

OR

A partnership firm registered under Indian Partnership Act, 1932

Copy of valid Registration Certificates In case of company-Copy of certificate of incorporation 2. Tax registration and clearance

The bidder should have a registered number of

i. VAT/ CST where his business is located ii. Service Tax

iii. Income Tax / Pan number.

The bidder should have cleared his VAT/ CST dues up to 31-Mar-2014 to the Government.

Copies of relevant certificates of registration VAT/ CST clearance certificate from the Commercial Taxes Officer of the Circle concerned

3. Financial: Turnover from IT/ ITeS

Average Turnover of the bidder from IT/ ITeS during last three financial years, i.e., from 2011-2012, 2012-2013, and 2013-2014 shall be at least INR 10 Crores

CA Certificate with CA’s Registration Number/ Seal

4. Financial: Net Worth

The Bidder shall have positive net worth as on 31st March 2014.

CA Certificate with CA’s Registration Number/ Seal

5. Operations of the firm

Bidder should be in operation for at least 5 years as on 31.03.2014 and shall have their registered offices in India.

Copy of Work Order before 31.03.2009 in IT/ITeS services

31-03-S. No.

Basic Requirement

Specific Requirements Documents Required

Capability - Experience

installation, commissioning and annual maintenance services for IT Infrastructure projects and shall have been in the business for a period exceeding three years as on 31.03.2014

2011 confirming year and area of activity

7. Technical Capability- Certification

The Bidder must have ISO 9001:2000 certification

Valid Copy of the Certification

8. Technical Capability- Manpower

a) The Bidder must have on its roll at least 100 Technically qualified professionals with combination in the following fields (system integration, Virtualization and experience in implementing the Cloud Solution) as on 31.03.2014

Certificate from Bidder’s HR Department for the number of Technically qualified professionals employed by the company 9. Technical Capability- Cloud Imple-mentation

The Bidder must have implemented/ commissioned at least one Cloud Implementation in Data Centre in India as on 31.03.2014

(Cloud Implementation for providing Cloud based services in their own Data Centre or on to the customer Data Centre shall be considered)

(a) Work Orders confirming year and area of activity (b) Valid Work Order and

Certificate from the Client in case implementation/ commissioning in Client Data Centre OR

(a) Declaration from the Company Secretary confirming the Cloud Implementation in their own Data Centre for providing services to the customers (b) Client certificate

confirming the cloud services they are getting from the Bidders Data Centre 10. Mandatory

Undertaking

Bidder should: -

a) not be insolvent, in receivership, bankrupt or being wound up, not have its affairs administered by a court or a judicial officer, not have its business activities suspended and must not be the subject of legal proceedings for any of the foregoing reasons;

b) not have, and their directors and officers not have, been convicted of any criminal offence related to their professional conduct or the making of false

A Self Certified letter as per Annexure-5: Self-Declaration

S. No.

Basic Requirement

Specific Requirements Documents Required

statements or misrepresentations as to their qualifications to enter into a procurement contract within a period of three years preceding the commencement of the procurement process, or not have been otherwise disqualified pursuant to debarment proceedings;

c) not have a conflict of interest in the procurement in question as specified in the bidding document.

d) comply with the code of integrity as specified in the bidding document. 11. Conflict of

Interest

The Bidder shall provide an undertaking that they or their allied agencies/ Subsidiaries are not working as a Consultant / TPA in the SDC in the State where the Bidder is bidding

Declaration in this regard by the authorized signatory of the Bidder 12. _MAF The Bidder shall submit valid letter from all

the OEMs confirming the following:  Authorization for Bidder

 Undertake that the support including patches, updates and upgrades for the quoted products shall be available for the entire project period.

Manufacturers

Authorization (MAF) for products as indicated in the Annexure-1 Bill of material

13. Consortium The Bids shall be submitted by only the Bidder; no consortium is allowed in this Bid

Declaration in this regard needs to be submitted

2) In addition to the provisions regarding the qualifications of the bidders as set out in (1) above: - a. the procuring entity shall disqualify a bidder as per the provisions under “Clause: Exclusion/

Disqualification of bids in Section-5: ITB”; and

b. the procuring entity may require a bidder, who was pre-qualified, to demonstrate its qualifications again in accordance with the same criteria used to pre-qualify such bidder. The procuring entity shall disqualify any bidder that fails to demonstrate its qualifications again, if requested to do so. The procuring entity shall promptly notify each bidder requested to demonstrate its qualifications again as to whether or not the bidder has done so to the satisfaction of the procuring entity.

4.

SCOPE OF WORK, DELIVERABLES & TIMELINES

RSDC has been equipped with infrastructure which enables State with seamless, highly reliable/robust, shared and secured infrastructure with scalable capacity. For better and optimal utilization of the compute infrastructure and utilizing the same infrastructure amongst multiple applications, adoption of Cloud technology components in RSDC is required. This technology will also drive consolidation of IT resources resulting in power savings which will be a significant step towards adopting green technologies.

To address issues typically faced by different departments at the State, such as long IT infrastructure procurement cycles, underutilization of resources, need for dynamic Scalability, appropriate disaster recovery of applications and data, and for simplifying IT infrastructure provisioning & availability to the line departments, cloud based service delivery is needed to be leveraged in the RSDC.

These Cloud solution requirements would include all the necessary components/ modules which are necessary to provide Infrastructure as a service to various line departments within the State as a Private Cloud to start with and have the capability of moving gradually to other delivery models like Platform-as-a-Service and Software-as-a-service.

After having analyzed the infrastructure presently provisioned in the RSDC and technology advancements required to make it Cloud enabled, following have been considered:

1. Cloud Enablement Infrastructure

a. Server Virtualization Software with required security capabilities b. Cloud Enablement components

i. Self Service provisioning ii. Automation & Orchestration iii. Capacity Management iv. Life Cycle Management

v. Catalogue and directory Maintenance vi. Monitoring and Reporting

vii. Helpdesk

The following are steps for Cloud Implementation:

 Help foster a Private cloud based environment on limited set of servers to begin with while retaining traditional Data Centre hosting models. This will enable the State to get exposure/confidence in building various levels of services that can be broadly classified into following categories:

a. Infrastructure as a Service (IaaS) b. Platform as a Service (PaaS) c. Software as a Service (SaaS)

 The services can be initiated with basic Compute Services (CPU, RAM, Storage, OS, and database) to the departments on demand basis along with a test and development environment. Once state develop confidence/maturity in operating cloud enabled environment, gradual migration of existing infrastructure and applications can happen on cloud.

While the Cloud solution is focused primarily on Infrastructure-as-a-Service, other services such as Platform-as-a-Service (PaaS), Software-as-a-Service (SaaS) to be deployed by the State, are complementary and/or deployed on top of the basic Infrastructure-as-a-Service (IaaS) services and would be based on the maturity of the State. The current scope of work is to ensure a capable environment for future SaaS and PaaS implementation. Services complimentary to IaaS such as PaaS and SaaS would be taken up in the future through third party tools.

The solution shall be capable of enabling automatic scale-up and scale-down of services hosted in the cloud based on user demand or other factors, shall ease infrastructure management, shall be agnostic to the underlying hardware, storage, network, operating system, and hypervisor . The solution needs to provide the ability for end customers to automatically provision the services via a Web Portal, provide metering and billing to provide service assurance for maintenance & operations activities performed by State teams. Detailed user level or user group level auditing, monitoring, metering, accounting, quota and show-back information is essential for building a platform. Detailed FRS is given in Annexure 2. The State is looking for a solution approach and architecture based design principles from market leading cloud solution providers in providing a low-cost solution enabled through factors such as using commodity hardware and efficient operations to ensure a cost-effective, scalable, efficient e-Governance platform. The architecture needs to be scalable to meet future demand and provide sufficient levels of security and interoperability so that customers (internal and external) are comfortable having critical infrastructure hosted in a safe environment.

4.1.1.

The minimum specified scope of work to be undertaken by the Selected SI for supply, installation, Commissioning, testing, Training, knowledge transfer and Support for SDC Cloud Enablement Infrastructure is mentioned below:

a) Finalize the deployment architecture/layout with the State Designated Agency/ State Implementation Agency

b) Procurement, supply, installation & commissioning of all the components & sub components including all necessary software as per the proposed solution. The Bidder has to ensure that the solution shall work as desired and the Bidder is also responsible to supply and install any other components that is inadvertently missed out but required for the overall solution to work, without adding any line item in the Bill of Material at no additional cost to the purchaser.

c) Active directory is required to be setup/configured and to be integrated with proposed virtualization manager and proposed cloud solution by bidder.

d) The Bidder shall be responsible for ensuring implementation of the proposed solution with existing infrastructure and solutions present in the RSDC and optimal functioning of all the components post installation. This implementation shall comply with all the functionalities stated in the Functional Requirement Specifications (FRS) and conform to the agreed deployment/implementation architecture. It shall be noted that any customization / API development that is carried out by the Bidder for such implementation will have to be supported (error correction, patch management) for the same duration of support applicable for the overall solution. The Bidder shall ensure that the Cloud solution is able to permit utilization of the existing security device like, firewall, IPS such that entire functionality of these devices can be used to monitor security features and provide alerts, alarms, reports, proactive actions on virtual environment similar to those provided in physical environment. For any further queries, the Bidder can also post queries in the pre-Bid meeting. The bidder has to ensure that all the components listed below shall work with the virtual machines as they were working with the existing infrastructure:

S. No.

Existing SDC Module

Make & Model Sub-Modules

1. IPS/ IDS, Firewall

₁₎

_{Radware defence pro 3020}

S. No.

Existing SDC Module

Make & Model Sub-Modules

2. SAN Storage Management Software / Controller

Make Type Model

Description

Disk

Type

No of

Hard

Disk

Raw

Capa

-city

IBM

2145 8A4

Storage SAN Volume Controller with 1U UPS

IBM

1818 51A

FC

15K

208 60

TB

IBM

2805 MC4

IBM

2145 8A4

Make Type Model

Descr-iption

Disk

Type

No of

Hard

Disk

Raw

Capa-city

HP

3PAR T400

HP 3PAR

T400

SSD

32 6.4

TB

HP

3PAR T400

FC 15K

160 48

TB

HP

3PAR T400

7.5K NL

32 64

TB

_{IBM Tivoli Storage Manager Suit}

for

Unified

Recovery

Terabyte(1-100) License – 25

licences.

4. Antivirus , HIPS

_Symantec

_protection

_Suite

Enterprise Edition 3 available

licenses :- 50

Quantity/ Number 5. Racks (Available in

Number)

39 6. Power per Rack

available

7KV 7. SAN Switch Ports

Available

Cisco SAN SWITCH =26 HP SAN SWITCH=46 8. L2 Switch Network

Ports available

136 available out of 336 9. Structured cabling

per Rack available

12 port per rack 10. CA tool

11. Active Directory/ LDAP server

e) The State will appoint a 3-4 member specialized team from the DCO’s (RSDC-O&M) team, Composite Team and State SIA/DIT to be associated with the Selected Bidder team so that

full hand holding of the entire solution shall be done from the beginning, up to FAT completion and subsequent O&M period.

f) The necessary server, operating system, database and any other required Licenses for Cloud Solution etc shall be provisioned by the SI on its own and cost of the same would be built-in in the cost of the proposed Solution. No separate line item(s) shall be entertained. The solution would be required to cater to the entire Data Centre infrastructure for which limited licenses for Cloud Management would be procured as part of this RFP. Licenses for Cloud Management of additional infrastructure, as applicable, would be procured in the future.

g) Comprehensive training during the implementation phase shall be the key to successful Operations and Maintenance; hence the Bidder is required to undertake robust training for at least 10 representatives from the State, Composite Team and DCO. The training documents, including Operating Manuals, Standard Operating Procedures (SOP) for the proposed Cloud solution shall be prepared and shared by the bidder with the State. The successful Bidder is free to propose the training plan. However at a minimum, the plan shall include the following:

SDC Cloud Enablement Training Schedule

S. No. Training Description

A IT Training

1. Overview of Components Installed 2. Server Virtualization

3. Adherence and Compliance

4. Overview of Migration from stand-alone Applications to the Virtualized Environment 5. Overview of Cloud Management and Monitoring Modules

6. Services that can be leveraged through SDC Private Cloud 7. Service Provisioning Portal, Orchestration, Automation etc.

8. Customization of Service Catalogue and Directory to able to add more services

B SLA

1. Overview of SLA Monitoring & Management

C Others

1. Overview of Service Provisioning, security adherence etc. 2. Do's and Don’ts

3. Any other points/topics (for e.g., Open Format, Interoperability, consolidation, virtualization etc.)

The above plan is only indicative; the final training plan shall be finalized between the SI and the State.

h) A training workshop needs to be arranged by the Bidder for hands-on training. This workshop shall be for 2 weeks and will be delivered by people certified in Cloud and Virtualization

i) 1 week training would be prior to the FAT and 1 week after the FAT completion

j) The RISL, prior to the initiation of the O&M phase, shall undertake a detailed Final Acceptance Test (FAT) process, which will include:

 Component wise Acceptance  Overall Solution Acceptance

k) It is mandated that cloud OEM representatives shall verify for satisfactory deployment of their components by the selected SI. Cost for the same shall be inbuilt as part of the bid and no extra payment / billing request shall be entertained in this regard during the project period.

l) FAT completion would only be considered after at least one application identified by the State has been put on the proposed cloud environment after testing all the solution capabilities as part of the FAT parameters. The state will inform the identified application to the selected bidder only.

Prior to deployment of the solution, the Bidder shall convey to the State all the requirements to be fulfilled by the State for ensuring smooth operations. The Bidder shall ensure that the planned downtime is during non-peak hours and on weekends, so that the downtime has minimum effect on the existing operations of RSDC.

m) The successful Bidder shall ensure that the project documents are maintained as per existing State policies.

n) During the entire project period, the successful Bidder shall comply with the SLAs provided under this RFP

o) All complaints shall be logged in the proposed Cloud Help Desk and the data shall be used to comply with the SLA compliance

p) The call and escalation that would be for the support period shall be properly recorded in the proposed Cloud helpdesk system

q)

r) The prices would be discovered in two parts:

 CAPEX (which shall include the Supply, Installation , Testing, Training and FAT)

 OPEX (This shall include the O&M, support and subscription cost for the period of the project, as mentioned in the RFP)

4.1.2.

The scope of work for the Operations Phase is categorized below: 4.1.2.1. Basic Services

i. Facilitate hosting of departmental applications on Cloud and in Virtualized Environment at the RSDC:

o Provision of Virtual Machines based on the requirement of the user department. o Maintaining catalogue and templates in the self service provisioning portal o Ensuring Connectivity of servers to the LAN and SAN Storage

o Ensuring required configuration for maintaining virtual IP and switch where the virtual machines do the communication

ii. SI shall maintain records of the maintenance of the cloud solution and shall maintain a logbook on-site that may be inspected by the State at any time.

iii. Server Monitoring, Administration & Management Services iv. Backup & Restore Services of Virtual Machines

v. Preventive Maintenance Services vi. Corrective Maintenance Services vii. MIS Reports

4.1.2.2. Help Desk Services

The help desk service will serve as a single point of contact for all incidents and service requests at the RSDC. The service will provide a Single Point of Contact (SPOC) and also escalation / closure of incidents for the user departments whose infrastructure is hosted at the data center. The activities related to Cloud shall include the following:

i. Solution should comprise of a completely automated system of raising issues on a portal through web / intranet, call logging, ticket generation, sending alerts on email and escalation to the cloud administrators and end users

ii. Provide Help Desk facility during agreed service period window for reporting user department incidents / issues / problems related with cloud solution.

iii. Provide necessary channels for reporting issues to the help desk.

iv. The Help desk shall log user calls related to Cloud Solution and assign an incident/ call ID number. Severity shall be assigned to each call as per the SLAs.

v. Creation of knowledge base on frequently asked questions to assist user departments in resolving basic issues themselves

vi. Track each incident / call to resolution vii. Provide feedback to callers.

viii. Analyze the call statistics

ix. Creation of knowledge base on frequently asked questions to aid users.

x. Continuous monitoring of the cloud solution at the RSDC to ensure availability as per agreed SLAs.

xi. Escalate the calls, to the appropriate levels, if necessary as per the escalation matrix agreed between the SI and the user department. The escalation matrix shall be developed by the SI in discussion with the SIA.

xii. Coordinate with respective vendors for closure of calls.

xiii. All complaints shall be logged in the proposed Cloud Help Desk and the data shall be used to comply with the SLA compliance

xiv. The call and escalation that would be for the support period shall be properly recorded in the proposed Cloud helpdesk system

xv. During the entire project period, the successful Bidder shall comply with the SLAs provided under this RFP

xvi. Analyze the incident / call statistics and provide monthly reports including but not limited to:

o Type of incidents / calls logged o Incidents / calls resolved o Incidents / calls open

Further, it is clarified that the existing helpdesk solution in the RSDC would be used ONLY for ticketing, call logging, and all processes related to recording of raising issues & issue resolutions, and knowledge/problem management. One helpdesk analyst license from the existing helpdesk solution would be provided to the selected bidder. However, all other helpdesk functionalities mentioned in the RFP (such as management & monitoring, reporting, issue diagnosis & resolution, etc) would have to be catered by the selected bidder from its own proposed Cloud solution.

4.1.2.3. Server Monitoring, Administration

The bidder shall ensure following activities on servers provided for deployment of cloud solution in RSDC.

The activities shall include:

i. Configuration of server parameters, operating systems administration and tuning. ii. Operating system administration, including but not limited to management of users,

processes, resource contention, preventive maintenance and management of updates & patches to ensure that the system is properly updated.

iii. Re-installation in the event of system crash/failures.

iv. 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.

v. Event log analysis generated in all the sub systems including but not limited to servers, operating systems, applications, etc. Ensuring that the logs are backed up and truncated at regular intervals.

vi. Periodic health check of the systems, troubleshooting problems, analyzing and implementing rectification measures.

vii. Ensuring the upkeep of existing systems that would be reused and also incorporate necessary changes for new applications if any during the tenure of the contract. viii. Identification, diagnosis and resolution of problem areas pertaining to the RSDC Cloud

Solution and application and maintenance of assured SLA levels.

ix. Prepare, Design, implement and maintain standard operating procedures for maintenance of the Cloud infrastructure based on the State’s policies.

4.1.2.4. Backup and Restore Services

The SI shall be using the existing backup solution, policies and procedures that is available at RSDC. The activities shall include, but not limited to:

 Backup of operating system, Virtual Machines and application as per stipulated policies at the RSDC.

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

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

4.1.2.5. MIS Reports

SI shall submit the reports on a regular basis in a mutually decided format. The SI shall workout the formats for the MIS reports and get these approved by the State within a month of being awarded the contract. The following is only an indicative list of MIS reports that may be submitted to the State:

a. Daily reports

o Summary of issues / complaints logged at the Help Desk

o Summary of resolved, unresolved and escalated issues / complaints

o Summary of resolved, unresolved and escalated issues / complaints to vendors. o Log of backup and restoration undertaken.

b. Weekly Reports

o Summary of systems rebooted.

o Summary of issues / complaints logged with the OEMs.

o Summary of changes undertaken in the Data Centre including major changes like configuration changes, patch upgrades, etc. and minor changes like log truncation, volume expansion, user creation, user password reset, etc.

o Hypervisor patch update status of all servers including the Virtual Machines running on in

c. Monthly reports

o Component wise server as well as Virtual machines availability and resource utilization

o Consolidated SLA / (non)- conformance report. o Summary of component wise uptime.

o Log of preventive / scheduled maintenance undertaken o Log of break-fix maintenance undertaken

o All relevant reports required for calculation of SLAs d. Quarterly Reports

o Consolidated component-wise availability and resource utilization. o All relevant reports required for calculation of SLAs

The MIS reports shall be in-line with the SLAs and the same shall be scrutinized by the TPA. Note: The Selected bidder will also provide any other report requested by the SIA/TPA

4.1.3.

i. The Cloud SI shall supply to the State, 5 (five) days after the signing of the contract or effective date of commencement of works/services or kick-off meeting whichever is earlier, an organization chart showing the proposed organization/manpower to be established by the SI for execution of the work/facilities including the identities and Curriculum-Vitae of the key personnel to be deployed. The SI shall promptly inform the State in writing of any revision or alteration of such organization charts

ii. The SI shall be responsible for the deployment, transportation, accommodation and other requirements of all its employees required for the execution of the work and for all costs/charges in connection thereof. The bidder has to estimate the number of manpower required for meeting out the SLA and RFP requirement as per cloud solution proposed by the SI (minimum one manpower/shift for the entire project period considering 3 shifts in a day shall be deployed by the bidder). Seating space for the manpower would be provided by the purchaser.

iii. The SI shall provide and deploy manpower on the site for carrying out the work, only those manpower resources who are skilled and experienced in their respective trades and who are competent to execute or manage/supervise the work in a proper and timely manner iv. The State’s Representative may at any time object to and require the SI to remove

forthwith from the site a supervisor or any other authorized representative or employee of the SI or any person(s) deployed by SI, if in the opinion of the State’s Representative the person in question has mis-conducted himself or his deployment is otherwise considered undesirable by the State’s Representative the SI shall forthwith remove and shall not again deploy the person in question of the work site without the written consent of the State’s Representative

v. The State’s Representative may at any time request the SI to remove from the work / Site the Implementation Agency’s supervisor or any other authorized representative including any employee of the SI or any person(s) deployed by SI for professional incompetence or negligence or for being deployed for work for which he is not suited. The SI shall consider the representative’s request and may accede to or disregard it. The State’s Representative having made a request as aforesaid in the case of any person which the SI has disregarded, may in the case of the same person at any time but on a different occasion and for a different instance of one of the reasons referred to above in this Clause object to and require the SI to remove that person from deployment on the work which the SI shall then forthwith do and shall not again deploy any person so objected to on the work or on the sort of work in question (as the case may be) without the written consent of the State’s Representative

vi. The State’s Representative shall state to the SI in writing his reasons for any request or requirement pursuant to this clause

vii. The SI shall maintain backup personnel and shall promptly provide replacement of every person removed pursuant to this section with an equally competent substitute from the pool of backup personnel

viii. In case of change in its team composition owing to attrition the SI shall ensure a reasonable amount of time-overlap in activities to ensure proper knowledge transfer and handover/takeover of documents and other relevant materials between the outgoing and the new member. The exiting team member shall be replaced with an equally competent substitute from the pool of backup personnel

4.2. Project Deliverables, Milestones & Time Schedule S. No. Project Activity/ Scope of Work Activity Deliverables

(Reports/ Docs./ Infra.)

Timelines 1. Team Mobilization, Preparation of Project Plan, Kick-off meeting etc. and Completion of activities mentioned in section 4.1.1 of the scope of work Detailed Project Plan, kick-off meeting and Final Acceptance Testing of deployed solution

 Detailed Project Plan  Minutes of Meeting

7 days from the date of issue of work order/ LOI

 Organization chart showing the proposed organization/ manpower including the identities and Curriculum-Vitae of the key personnel to be deployed

 5 (five) days after the signing of the contract or  effective date of commencement of works/services or  kick-off meeting whichever is earlier amongst the above  Delivery reports for all

software  Installation and

Commissioning reports of components and solution  FAT document (including

Plan, procedures, and report)  Standard Operating

Procedures (SOP)  Exit Management Plan  SLA Measurement

Methodology  Training material  Training completion

certificate from user

99 days from the date of issue of work order/LOI or 84 days from the signing of contract, whichever is earlier 2. Completion of scope of work of section 4.1.2 of the scope of work Operation and Maintenance  Basic Services (As per section 4.1.2.1)

 Date wise detailed and MIS reports of corrective maintenance services provided during the quarter  Backup and recovery

services of virtual machines- Exception report along with related logs

Within 15 days from the end of respective quarter

 Help Desk Services (As per section

 Detailed SLA compliance report and logs

S. No. Project Activity/ Scope of Work Activity Deliverables

(Reports/ Docs./ Infra.)

Timelines 4.1.2.2)  Server Monitoring, Administration (As per section 4.1.2.3)

 Server Administration and management services:

o Updates/upgrades, patches history report o Server uptime report

along with logs  Backup and

restore services (As per section 4.1.2.4)

 Exception report along with related logs

 MIS reports (As per section 4.1.2.5)

 Reports submission chart for all reports as mentioned in SoW and additional reports as desired by the purchaser

Note: DCCO has to provide all the reports and deliverables mentioned above and provide any additional reports as required by purchaser.

4.3. Roles and Responsibilities

The roles of the stakeholders shall change over a period of time as the project will evolve from design to implementation and enter the operations phase. With this background, stakeholders’ responsibilities and illustrative organizational structure for the design & implementation phase and operational phase is given below:

STATE State Implementation Agency and/ or Composite Team Cloud SI System Integrator/ Bidder

DCO Data Centre Operator

TPA Third Party Auditor

A- Advise C- Coordinate I- Implement

The table below summarizes the Roles and Responsibilities of stakeholders involved in the project: Table 1: Summary of Roles and Responsibilities of stakeholders

S. No. Activity Stakeholder State / CT Cloud SI DCO

1 Supply, Installation and Commissioning

1.1 Finalize Deployment Architecture with SIA C I 1.2 Cloud SI to finalize requirements (Downtime

requirements)

S. No. Activity Stakeholder State / CT Cloud SI DCO 1.3 Cloud SI to submit a plan for the following:

 Project Implementation,

 Training and Knowledge Transfer Plan

C I C

Preparation and submission of Standard Operating Procedures (SOP)

C I

1.4 State to sign off on submitted Plans and give go-ahead to Cloud SI for Installation

I C

1.5 Supply, Installation and commissioning of Cloud Solution such as Server Virtualization, Cloud Management and monitoring tools and other IT components required at the Rajasthan State Data Centre as specified in the Functional requirements, and / or suggested by the Cloud SI

C I

1.6 State to sign off on Deployment Architecture after taking compliance from Cloud SI for required uptime SLAs

I C

1.7 All SW, Licenses shall be verified as per the BoM submitted by the Cloud SI as part of the Bid

I C

1.8 State to specify one application to be put in virtualized environment

I C C

2 Testing

2.1 Acceptance Test Plan customization by Cloud SI and submission to State for approval (Focus to be on Performance, Resilience and Quality of solution)

I I C

2.2 Provide SW and Licenses required for testing installed Cloud Solution

I

3 Final Acceptance Test

3.1 Cloud SI to demonstrate all the services / features / functionalities as mentioned in the FRS and defined in the Scope of Work and subsequently in the agreement, as part of the FAT

C I C

3.2 State to verify the functionalities and sign-off on FAT completion

I C C

4 Training

4.1 State to identify the representatives from CT, DCO, User Department, SeMT and SIA

I 4.2 Training to be provided by the Bidder as per the

training requirements mentioned in the RFP

C I C

5 Operations and Maintenance

5.1 Support for all the components (upgrades, updates, call, escalation, response time , resolution time )

C I C

5.2 Maintaining the helpdesk for Cloud components I C 5.3 Support during the Operations phase for any error

correction or version Updations

I C

5.4 Provisioning of new VM deletion, Updations, P to V Conversion etc.

5. INSTRUCTION TO BIDDERS (ITB)

1)

a) The sale of bidding documents shall be commenced from the date of publication of Notice Inviting Bids (NIB) and shall be stopped one day prior to the date of opening of Bid. The complete bidding document shall also be placed on the State Public Procurement Portal and e-Procurement portal. The prospective bidders shall be permitted to download the bidding document from the websites and pay its price while submitting the Bid to the procuring entity.

b) The bidding documents shall be made available to any prospective bidder who pays the price for it in cash or by bank demand draft, banker's cheque.

c) Bidding documents purchased by Principal of any concern may be used by its authorised sole selling agents/ marketing agents/ distributors/ sub-distributors and authorised dealers or vice versa.

2)

a) Any prospective bidder may, in writing, seek clarifications from the procuring entity in respect of the bidding documents.

b) A pre-bid conference is also scheduled by the procuring entity as per the details mentioned in the NIB and to clarify doubts of potential bidders in respect of the procurement and the records of such conference shall be intimated to all bidders and where applicable, shall be published on the respective websites.

c) The period within which the bidders may seek clarifications under (a) above and the period within which the procuring entity shall respond to such requests for clarifications shall be as under: -

a. Last date of submitting clarifications requests by the bidder: as per NIB b. Response to clarifications by procuring entity: as per NIB

d) The minutes and response, if any, shall be provided promptly to all bidders to which the procuring entity provided the bidding documents, so as to enable those bidders to take minutes into account in preparing their bids, and shall be published on the respective websites.

3)

a) At any time, prior to the deadline for submission of Bids, the procuring entity may for any reason, whether on its own initiative or as a result of a request for clarification by a bidder, modify the bidding documents by issuing an addendum in accordance with the provisions below.

b) In case, any modification is made to the bidding document or any clarification is issued which materially affects the terms contained in the bidding document, the procuring entity shall publish such modification or clarification in the same manner as the publication of the initial bidding document.

c) In case, a clarification or modification is issued to the bidding document, the procuring entity may, prior to the last date for submission of Bids, extend such time limit in order to allow the bidders sufficient time to take into account the clarification or modification, as the case may be, while submitting their Bids.

d) Any bidder, who has submitted his Bid in response to the original invitation, shall have the opportunity to modify or re-submit it, as the case may be, within the period of time originally

allotted or such extended time as may be allowed for submission of Bids, when changes are made to the bidding document by the procuring entity:

Provided that the Bid last submitted or the Bid as modified by the bidder shall be considered for evaluation.

4)

a) Bids submitted by the bidders shall remain valid during the period specified in the NIB/ bidding document. A Bid valid for a shorter period shall be rejected by the procuring entity as non-responsive Bid.

b) Prior to the expiry of the period of validity of Bids, the procuring entity, in exceptional circumstances, may request the bidders to extend the bid validity period for an additional specified period of time. A bidder may refuse the request and such refusal shall be treated as withdrawal of Bid and in such circumstances bid security shall not be forfeited.

c) Bidders that agree to an extension of the period of validity of their Bids shall extend or get extended the period of validity of bid securities submitted by them or submit new bid securities to cover the extended period of validity of their bids. A bidder whose bid security is not extended, or that has not submitted a new bid security, is considered to have refused the request to extend the period of validity of its Bid.

5)

a) Bidders must submit their bids online at e-Procurement portal i.e. http://eproc.rajasthan.gov.in. b) All the documents uploaded should be digitally signed with the DSC of authorized signatory. c) A Single stage-Two part/ cover system shall be followed for the Bid: -

a. Technical Bid, including fee details, eligibility & technical documents b. Financial Bid

d) The technical bid shall consist of the following documents: -

S. No. Documents Type Document Format

Fee Details

1. Bidding document Fee (Tender Fee) Proof of submission (PDF)

2. RISL Processing Fee (e-Procurement) Instrument/ Proof of submission (PDF)

3. Bid Security Instrument/ Proof of submission (PDF)

Eligibility Documents 4. Bidder’s Authorisation Certificate along with

copy of PoA/ Board resolution stating that Auth. Signatory can sign the bid/ contract on behalf of the firm.

As per Annexure-4 (PDF)

5. All the documents mentioned in the “Eligibility

Criteria”, in support of the eligibility As per the format mentioned against the respective eligibility criteria clause (PDF)

Technical Documents

6. Certificate of Conformity/ No Deviation As per Annexure-6 (PDF) 7. Declaration by Bidders As per Annexure-7 (PDF)

8. Manufacturer’s Authorisation Form (MAF) As per Annexure8 (Indicative Format) (PDF) for the items given in Annexure-1 (BoQ)

S. No. Documents Type Document Format 9. Undertaking on Authenticity of Comp. Equip. As per Annexure-9 (PDF) 10. Components Offered + Functional

Requirement Specifications compliance sheet for all items only on OEM Letter Head

As per Annexure-10 (PDF)

11. All the documents mentioned in the clause “Technical Evaluation criteria” of “Evaluation & Tabulation of Technical Bids” given in Section-5 (Instruction to bidders)

As per the format mentioned against the respective evaluation criteria.

12. Technical Solution and Technical Forms As per Annexure-15 (Forms for filling the technical Bid)

b) Financial bid shall include the following documents: -

S. No. Documents Type Document Format

1. Financial Bid – Cover Letter On bidder’s letter head duly signed by authorized signatory as per Annexure-11 (PDF)

2. Financial Bid - Format As per BoQ (.XLS) format available on e-Procurement portal c) The bidder should ensure that all the required documents, as mentioned in this bidding

document, are submitted along with the Bid and in the prescribed format only. Non-submission of the required documents or submission of the documents in a different format/ contents may lead to the rejections of the Bid submitted by the bidder.

6)

a) The Bidder shall bear all costs associated with the preparation and submission of its Bid, and the procuring entity shall not be responsible or liable for those costs, regardless of the conduct or outcome of the bidding process.

b) The Bid, as well as all correspondence and documents relating to the Bid exchanged by the Bidder and the procuring entity, shall be written only in English Language. Supporting documents and printed literature that are part of the Bid may be in another language provided they are accompanied by an accurate translation of the relevant passages in English/ Hindi language, in which case, for purposes of interpretation of the Bid, such translation shall govern.

7)

Alternative/ Multiple Bids shall not be considered at all. Also, the bidder shall not quote for multiple brands/ make/ models but only one in the technical Bid and should also mention the details of the quoted make/ model in the “Annexure-10: Components Offered”.

8)

Every bidder, if not exempted, participating in the procurement process will be required to furnish the bid security as specified in the NIB.

a) In lieu of bid security, a bid securing declaration shall be taken from Departments of the State Government, Undertakings, Corporations, Autonomous bodies, Registered Societies and Cooperative Societies which are owned or controlled or managed by the State Government and Government Undertakings of the Central Government.

b) Bid security instrument or a bid securing declaration shall necessarily accompany the technical bid.

c) Bid security of a bidder lying with the procuring entity in respect of other bids awaiting decision shall not be adjusted towards bid security for the fresh bids. The bid security originally deposited may, however, be taken into consideration in case bids are re-invited.

d) The bid security may be given in the form of a banker’s cheque or demand draft of a scheduled bank or deposited through eGRAS. The bid security must remain valid thirty days beyond the original or extended validity period of the bid.

e) The issuer of the bid security and the confirmer, if any, of the bid security, as well as the form and terms of the bid security, must be acceptable to the procuring entity.

f) Prior to presenting a submission, a bidder may request the procuring entity to confirm the acceptability of proposed issuer of a bid security or of a proposed confirmer, if required. The procuring entity shall respond promptly to such a request.

g) The bid security of unsuccessful bidders shall be refunded soon after final acceptance of successful bid and signing of Agreement and submitting performance security.

h) The Bid security taken from a bidder shall be forfeited, including the interest, if any, in the following cases, namely: -

a. when the bidder withdraws or modifies its bid after opening of bids;

b. when the bidder does not execute the agreement, if any, after placement of supply/ work order within the specified period;

c. when the bidder fails to commence the supply of the goods or service or execute work as per supply/ work order within the time specified;

d. when the bidder does not deposit the performance security within specified period after the supply/ work order is placed; and

e. if the bidder breaches any provision of code of integrity, prescribed for bidders, specified in the bidding document.

i) Notice will be given to the bidder with reasonable time before bid security deposited is forfeited. j) No interest shall be payable on the bid security.

k) In case of the successful bidder, the amount of bid security may be adjusted in arriving at the amount of the Performance Security, or refunded if the successful bidder furnishes the full amount of performance security.

l) The procuring entity shall promptly return the bid security after the earliest of the following events, namely:-

a. the expiry of validity of bid security;

b. the execution of agreement for procurement and performance security is furnished by the successful bidder;

c. the cancellation of the procurement process; or

d. the withdrawal of bid prior to the deadline for presenting bids, unless the bidding documents stipulate that no such withdrawal is permitted.