rfp for cloud enablement

TENDER DOCUMENT

For Appointment of an Agency for Setting up and Maintenance

Support of Cloud Enablement Infrastructure In

Tripura State Data Centre Tender No. F.7(3)/TSCA/SDC/2013

03rd April 2013

Tripura State Computerization Agency (TSCA) (A society of Directorate of Information Technology, Government of Tripura)

ITI Road, Indranagar Agartala, Tripura - 799 006

RFP for TSDC Cloud Enablement

Tripura State Computerization Agency 2

Important Dates and Information

Bid Reference F. 7(3)/TSCA/SDC/2013

Publication details The tender form can be seen and downloaded from the website http://www.tripuratenders.gov.in and also hyperlinked from Directorate of IT website at http:/ittripura.gov.in and the Central Public Procurement Portal at http://eprocure.gov.in . The stated Tender is in e-Tender mode with built-in e-Bid and their online evaluation and can only be accessed through http://www.tripuratenders.gov.in.

Date Of Commencement Of Bid 03rd April 2013

Last Date for sending Pre-Bid query 20th April 2013, 4 PM

Pre Bid Conference Date and Time 25th April 2013, 11 AM

Last Date And Time For Receipt Of Bids 15th May 2013, 11 AM

Date & Time Of Opening Of Prequalification Bids and Technical Bids

15th May 2013, 11:30 AM

Date & Time Of Opening Of Technical Presentation

27th May 2013, 11 AM

Date & Time Of Opening Of Commercial Bids

31th May 2013, 11 AM

Address For Communication / Pre-Bid / Submission/ Opening of Technical & Commercial Bid

MEMBER SECRETARY

TRIPURA STATE COMPUTERIZATION SOCIETY(A SOCIETY UNDER DIRECTORATE OF INFORMATION TECHNOLOGY, GOVT. OF TRIPURA); ITI ROAD; INDRANAGAR; AGARTALA -799006

Contact Person Shri. Uttam Podder, Sr.Informatics Officer

Contact email [email protected]

Contact Phone no 0381-2355751

Fax 0381-2355751

http://www.tripuratenders.gov.in/�

http://www.tsecl.nic.in/�

http://eprocure.gov.in/�


mailto:[email protected]�



Table of Contents 1. Executive Summary ........................................................................................................................... 6 2. Instruction to SIs................................................................................................................................ 8

2.1 Definitions .................................................................................................................................. 8 2.2 Eligibility Criteria of SIs.......................................................................................................... 11 2.3 Tender Fees............................................................................................................................... 12 2.4 Proposal Preparation Cost ...................................................................................................... 12 2.5 RFP Document ......................................................................................................................... 12 2.6 Clarification on RFP Document and Pre Bid Conference .................................................. 13 2.7 Amendment to RFP Document .............................................................................................. 13 2.8 Language of BID....................................................................................................................... 13 2.9 Period of Validity of Bids ........................................................................................................ 13 2.10 Submission of the Bids ............................................................................................................ 14 2.11 Opening of Bids ........................................................................................................................ 15 2.12 Evaluation Criteria................................................................................................................... 15 2.13 Bid Currency ............................................................................................................................. 16 2.14 Bid Security............................................................................................................................... 17 2.15 Forfeiture of EMD/ Bid Security ........................................................................................... 17 2.16 Award of Contract .................................................................................................................... 17 2.17 Performance Security .............................................................................................................. 17 2.18 Contacting TSCA ...................................................................................................................... 18 2.19 Right to Accept Bids and to reject any or all Bids ............................................................... 18 2.20 Lack of Information to SI........................................................................................................ 18 2.21 Fraudulent & Corrupt Practice............................................................................................... 18

3. General Conditions .......................................................................................................................... 19 3.1 Conditions Precedent .............................................................................................................. 19

3.1.1 Commencement of the Agreement .................................................................................... 19

3.1.2 Obligations to satisfy the Conditions Precedent .......................................................... 19

3.1.3 Notice of fulfillment of the Conditions Precedent ....................................................... 19

3.1.4 Non-fulfillment of Conditions Precedent...................................................................... 19

3.2 Contract Obligations................................................................................................................ 19 3.3 Application................................................................................................................................ 19 3.4 Governing Language................................................................................................................ 19 3.5 Applicable Law ......................................................................................................................... 20 3.6 Sub-Contracts ........................................................................................................................... 20 3.7 Change orders........................................................................................................................... 20



3.8 Notice......................................................................................................................................... 20 3.9 Patent Rights ............................................................................................................................ 20 3.10 Taxes and Duties ...................................................................................................................... 20 3.11 Operation and Maintenance................................................................................................... 20 3.12 Force Majeure........................................................................................................................... 20

3.12.1 Force Majeure Exclusions ............................................................................................... 21

3.12.2 Procedure for Calling Force Majeure............................................................................. 21

3.12.3 Procedure for Claiming Relief ........................................................................................ 22

3.12.4 Extensions due to Force Majeure................................................................................... 22

3.12.5 Termination as a result of Exceptional Event .............................................................. 22

3.13 Handing Over ........................................................................................................................... 23 3.14 Termination .............................................................................................................................. 23 3.15 Resolution of Disputes and Arbitration ................................................................................ 23 3.16 Acquaintance with local conditions....................................................................................... 24 3.17 Statutory and Regulatory Approvals ..................................................................................... 24 3.18 Confidentiality .......................................................................................................................... 24 3.19 Limitation of Liability ............................................................................................................. 24 3.20 Failure to Agree with the Terms and Conditions of the RFP ............................................. 24 3.21 Indemnification........................................................................................................................ 24 3.22 Control and Possession ........................................................................................................... 25 3.23 Replacement: ............................................................................................................................ 25 3.24 Books & Records ...................................................................................................................... 26 3.25 Amendment to the Agreement ............................................................................................... 26 3.26 Use of Agreement Documents and Information.................................................................. 26 3.27 Exit Management ..................................................................................................................... 27

4. Special Conditions............................................................................................................................ 29 4.1 SI’s Responsibility.................................................................................................................... 29 4.2 Tests ........................................................................................................................................... 29

4.2.1 Partial Acceptance Test ................................................................................................... 29

4.2.2 Test Run............................................................................................................................. 29

4.2.3 Final Acceptance Test ...................................................................................................... 29

4.3 Payment Terms ........................................................................................................................ 30 5. Scope of Work:.................................................................................................................................. 31

5.1 Supply, Installation, Commissioning, Testing, Training and Knowledge transfer for TSDC Cloud Enablement Infrastructure........................................................................................... 32



5.2 Operation and Maintenance for SDC Cloud Enablement .................................................. 35 6. Roles and Responsibility (RACI Matrix)....................................................................................... 36 7. Service Level Agreement ................................................................................................................. 38

7.1 Definitions ................................................................................................................................ 38 7.2 Service Levels ........................................................................................................................... 39

7.2.1 Implementation service levels ........................................................................................ 40

7.2.2 IT Infrastructure Support Service Levels...................................................................... 42

7.2.3 Software Support Service Levels .................................................................................... 44

7.2.4 Support Service Levels..................................................................................................... 46

7.3 Penalties .................................................................................................................................... 48 8. Functional Requirement Specification.......................................................................................... 49

8.1 Cloud Enablement General Requirements........................................................................... 49 8.2 FRS for Cloud enablement...................................................................................................... 51 8.3 Specification for Blade Enclosure/Chassis ................................................................................ 60 8.4 Specification for Blade Server ................................................................................................ 62 8.5 Specification for SAN Storage ................................................................................................ 63 8.6 Specification for SAN Switch (for connectivity with SAN Storage) .................................. 65

9. Bill of Materials ................................................................................................................................ 66 10. Annexure ....................................................................................................................................... 68 Annexure I: SI Profile .............................................................................................................................. 68 Annexure II: SI’s Experience .................................................................................................................. 70 Annexure III: Format for Financial Information ................................................................................ 71 Annexure IV: Format for Performance Bank Guarantee.................................................................... 72 Annexure V: Format for Providing Citations ....................................................................................... 74 Annexure VI: Format for Queries .......................................................................................................... 75 Annexure VII: Technical Bid letter ........................................................................................................ 76 Annexure VIII: Technical Evaluation Criteria ..................................................................................... 78 Annexure IX: Statement of Deviation from Technical Specification ................................................ 84 Annexure X: Format of Curriculum Vitae for Proposed Manpower ................................................. 85 Annexure XI: Un-Priced Bills of Materials ........................................................................................... 86 Annexure XII: Commercial Bid Letter .................................................................................................. 89 Annexure XIII: Summary of Cost Components ................................................................................... 91 Annexure XIV: Breakdown of Cost Components................................................................................. 92 Annexure XV: Existing Infrastructure of TSDC................................................................................... 97 Annexure XVI: Abbreviations ................................................................................................................ 99



1. Executive Summary Under the National eGovernance 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”.

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.

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 Centre has been implemented to provide common IT infrastructure to host these planned e-Governance initiatives / applications. State Data Centre 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.

The State Data Centre (SDC) established in the State has provided 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 has been provisioned in the SDC.

ii. Storage Infrastructure: Centralized storage with flexible and secure configuration is available in the SDC including backup facilities. The same shall be leveraged by different line departments for their data storage requirements in shared manner.



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

SDC have been equipped with infrastructure which will enable State departments with seamless, highly reliable/robust, shared and secured infrastructure with scalable capacity. 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.

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 SDC. After having analyzed the infrastructure at present provisioned in the SDC and technology advancements, the process for implementing a Cloud based Service Delivery Model in SDC has been initiated, so that the SDC IT Infrastructure can be shared amongst multiple departments. Thus making the SDC as a Private Cloud operated for State.

The proposed Cloud solution should be capable of providing Infrastructure as a service. It should possess the following capabilities:

• Self Provisioning and catalogue • Migration of VMs within and across enclosures • Automation, Orchestration, Monitoring and self service portal (Internal Use) • Planning and optimization

While we are moving towards Cloud based service approach, it is also very much essential that the security requirements are addressed adequately. The solution should be capable of enabling automatic scale-up and scale-down of services hosted in the cloud based on user demand or other factors, should ease Infrastructure Management, Application Management and should be able to consolidate resources, should be agnostic to the underlying hardware, storage, network, operating system, and hypervisor, should be interoperable across multiple enclosures. Following are the important characteristics of a well-managed cloud based service delivery model. The proposed cloud solution should possess the following capabilities:

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 State Designated Agency (SDA) to deliver the required infrastructure.

v. Measured service - Resource usage can be monitored, controlled, and reported. - Create an IT governance mechanism within State as it leverage common /

shared Platforms to speed up the process of service delivery. vi. Service catalog

vii. Service Delivery and Capacity planning and management.

This document is a Request for Proposal (RFP) for Bidders to quote for the Supply, Installation, Configuration, Testing, Training and Seamless steady-state Support of components for Cloud Enablement in Tripura State Data Centre (TSDC). The successful Bidder shall do the design, supply, installation, configuration, testing, Training and provide steady-state Support and do FAT as per the specifications and the minimum specified Scope of Work to be undertaken by the successful Bidder.

2. Instruction to SIs

SI’s is advised to study this RFP document carefully before participating. It shall be deemed that submission of bid by the SI has been done after their careful study and examination of the RFP with full understanding to its implications. Any lack of information shall not in any way relieve the SI of his responsibility to fulfill his obligations under the Bid.

2.1 Definitions

In this document, the following terms shall have following respective meanings:-

“Acceptance” means the Government’s written certification that following installation, the system(s) (or specific part thereof) has been tested and verified as complete and/or fully operational, in accordance with the acceptance test defined in the Acceptance Test Documents.

“Acceptance Test Documents” means a mutually agreed document which defines procedures for testing the functioning of the solution, against requirements laid down in the agreement. It should define tests to be carried out, test equipment and expected test results.

“Agreement” means the Agreement to be signed by the Successful SI and Tripura State Computerisation Agency.



“Authorized Representative” shall mean any person/agency authorized by either of the parties.

“Affiliate” shall mean any holding company or subsidiary company as a party of the Agreement or any company, which is subsidiary of such a holding company. The expressions "holding company" and “subsidiary company” shall have the meaning specified in Section - 4 of the Companies Act 1956 (as amended from time to time).

“Contract” is used synonymously with agreement.

“Corrupt Practice” means the offering, giving, receiving or soliciting of anything of value or influence the action of a public official in the process of Contract execution

“Documentary evidence” means any matter expressed or described upon any substance by means of letters, figures or marks intended to be used for the recording of that matter and produced before a court.

“Default Notice” shall mean the written notice of Default of the Agreement issued by one Party to the other in terms hereof.

“Final Acceptance Test (FAT)” means the acceptance testing for Cloud Enablement of SDC covered under the scope of work and the issues rectified at partial acceptance test.

“Fraudulent Practice” means a misrepresentation of facts in order to influence a procurement process or the execution of a Contract and includes collusive practice among SIs (prior to or after Bid submission) designed to establish Bid prices at artificial non-competitive levels and to deprive TSCA and /or GoT of the benefits of free and open competition.

“Good Industry Practice” shall mean the exercise of that degree of skill, diligence and prudence which would reasonably and ordinarily be expected from a reasonably skilled and experienced SI engaged in the same type of undertaking under the same or similar circumstances.

“Gov./GoT/Government/Govt. of Tripura” shall mean Government of Tripura.

“Implementation Period” shall mean the period from the date of signing of the Agreement and up to the issuance of Final Acceptance Certificate of Cloud Enablement for TSDC

“SI” means any firm offering the solution(s), service(s) and/ or materials required in the RFP. The word SI, when used in the pre-award period shall be synonymous with SI, and when used after intimation of successful SI shall mean the successful SI, also called “System Integrator”.

“Law” shall mean any Act ,notification, bye law ,rules and regulations, directive, ordinance, order or instruction having the force of law enacted or issued by the Government of India or State Government Tripura or regulatory authority or political sub-division of government agency.

“LOI” means Letter of Intent which shall constitute the intention of the Tenderer to place the purchase order with the successful SI.



“Partial Acceptance Test (PAT)” means the provisional acceptance testing of all equipment (hardware & software) and their services covered under the scope of work.

“Party” shall mean TSCA or SI individually and “Parties” shall mean TSCA and SI collectively.

“PBC” means Pre-Bid Conference

“Performance” means accomplishment of the project in terms of Standards, Quality, SLA for implementation, maintenance and support.

“Period of Agreement" means Implementation period as defined plus 3 years for AMC (including warranty period) from the date of final acceptance.

“Rates/Prices” means prices of supply of equipment and services quoted by the SI in the Commercial Bid submitted by him and/or mentioned in the Contract

“RFP” means the detailed notification seeking a set of solution(s), service(s), materials and/or any combination of them.

“Services” means the work to be performed by the SI pursuant to this RFP, as detailed in the Scope of Work

“Site” shall mean the location(s) for which the RFP has been issued and where the service shall be provided as per Agreement

“System Integrator” shall mean the selected SI.

“Termination notice” means the written notice of termination of the Agreement issued by one party to the other in terms hereof.

“TSWAN” means Tripura State Wide Area Network

“TSDC” means Tripura State Data Center

“TSCA” means Tripura State Computerisation Agency



2.2 Eligibility Criteria of SIs

The following are the conditions, which are to be necessarily fulfilled, to be eligible for technical evaluation of the proposed solution. Only those interested SIs who satisfy the following eligibility criteria should respond to this RFP:

SI’s General Qualifications

a) An Individual organization shall submit the Bid. Consortium is not allowed.

b) The SI should be an established Information Technology company and IT System Integrator in India and should have been in the business for a period exceeding ten years

as on 31st

March 2013. (Certificate of Incorporation should be provided)

c) The SI shall not be under a declaration of ineligibility for corrupt or fraudulent practices or blacklisted with any of the Central / State Government/Government agencies/ PSUs/ World Bank etc.

d) The SI shall have company registration certificate registered under the Company’s Act 1956, valid sales tax registration certificate, valid Service tax registration certificate and Permanent Account Number (PAN) issued by income Tax department. (Copy of each registration certificate should be provided).

The SI shall meet the following criteria for eligibility:

1. SI must be having a registered office with legal presence in India and with a minimum average annual turnover of INR 200 Crores (Rupees Two hundred Crores) from IT business for the preceding 3 financial years ended with 31st March 2012 (as per the Audited Balance Sheets and Income statements).

2. The SI must have implemented/ commissioned at least 2 (two) Cloud Implementation in Data Centre (Govt./PSU/Private sector) in India (upto 31-Mar-2013).

3. The SI should have experience of working with Government for any two e-Governance project of value not less than Rs 2 Crore each during the last three years (upto 31-Mar-2013).

4. In order to enable Govt. to assess the authenticity of the above, the SI shall provide relevant and necessary documentary evidence in relation to the previous similar contracts executed by the SI. e.g. Copies of the Work Order and its timely completion certificates, customer satisfaction certificate etc. Govt. reserves the right to verify, if it so desires, the correctness of documentary evidence furnished by the SI.

5. GoT further reserves the right to verify the successful operation and performance of qualifying projects and SI shall arrange permission for the same.

6. The SI should either have local presence in Tripura or agree to setup local office within one month of award of contract.



7. The SI will have the responsibility of all kind of maintenance and support of equipment, software etc. specified in this project for a period of three years after successful implementation.

8. The SI should be ISO 20000 and ISO 27001 certified.

NOTE: Please submit all the documentary evidence in support of the above conditions as the eligibility criteria.

2.3 Tender Fees

A non-refundable payment of Rs. 10,000.00 (Rupees Ten Thousand only) by demand draft from any nationalized /scheduled commercial bank having branch at Agartala drawn in favour of “Member Secretary, Tripura State Computerization Agency” payable at Agartala to be made as Tender fees. The original draft should reach the office of Member Secretary, Tripura State Computerisation Agency prior to the opening of the Tender. The Scanned copy (PDF version at 150 dpi) of draft should be uploaded in the specific folder as mentioned in the RFP document. If the scanned copy is not uploaded although the original draft is submitted or vice versa the bid is liable to get rejected.

2.4 Proposal Preparation Cost

The SI is responsible for all costs incurred in connection with participation in this process, including, but not limited to, costs incurred in conduct of informative and other diligence activities, participation in meetings/discussions/presentations, preparation of proposal, in providing any additional information required by TSCA, GoT to facilitate the evaluation process, and in negotiating a definitive Service Agreement or all such activities related to the bid process. This RFP does not commit TSCA to award a contract. Further, no reimbursable cost may be incurred in anticipation of award.

2.5 RFP Document

Interested SI’s shall have to register themselves in the e-Procurement website at http://www.tripuratenders.gov.in for participating in the e-Tender and require at least a Class-II Digital Signature Certificates.

Interested SI’s shall have to get equipped for e-Tendering. SI’s may also take assistance from the toll free 24x7 Help Desk advertised in Central Public Procurement Portal.

SI’s may also view the entire Bid Opening process online, on the e-Tendering Software.

SI is expected to examine all instructions, forms, terms, specifications, and other information in the RFP document. Failure to furnish all information required by the RFP document or to submit a Bid not substantially responsive to the RFP document in every respect will be at SI’s risk and may result in the rejection of its Bid.

Tempering with any format will attract disqualification from the process.




2.6 Clarification on RFP Document and Pre Bid Conference

The SI’s or its official representatives (maximum two members) is invited to attend a pre-bid meeting to be held on the date mentioned in the important dates section at the Office of Member Secretary, TSCA, Indranagar, Agartala. The purpose of the meeting will be to clarify issues and to address clarifications sought by the SIs in this context. The SI is requested to submit their Request for Clarifications through email only to reach the Member Secretary, TSCA, GoT by the date specified under important date section before the pre bid meeting. The responses for the clarifications sought by any SI will be distributed to all the SIs.

However, it is not binding on TSCA to hold a pre-bid meeting or restrict itself to holding only one such meeting. If it feels, that the clarifications sought by the SIs do not warrant a pre-bid meeting, it can cancel the meeting and send the replies to the SIs by email.

2.7 Amendment to RFP Document

Any modifications in the bidding documents, which may become necessary as a result of the pre-bid meeting, shall be made by TSCA exclusively through the issue of a corrigendum. The decision of TSCA on the need for any modification shall be final and binding on all.

The amendment(s) will be published in the e-Tender portal at http://www.tripuratenders.gov.in. Registered SIs shall be notified of the related Corrigendum(s) by e-mail. However, TSCA shall bear no responsibility or liability arising out of non-receipt of the same in time or otherwise. Prospective Bidders are requested to visit the site frequently to check whether there is any related Corrigendum or not.

In order to afford prospective bidders reasonable time to take the Corrigendum into account in preparing their bids, TSCA may, at its discretion, extend the deadline for submission of bids.

Such Corrigendum, Clarifications etc. shall be binding on the Bidders and shall be given due consideration by them while they submit their bids.

2.8 Language of BID

The bid prepared by the SI, as well as all correspondence and documents relating to the Bid exchanged between the SI and the TSCA shall be in English. Supporting documents and printed literature furnished by the SI may be in another language provided they are accompanied by an accurate translation by approved translator of the relevant pages in English. For the purposes of interpretation of the bid, the translation shall govern. Information supplied in another language without proper translation shall be rejected.

2.9 Period of Validity of Bids

The bid shall remain valid for 180 days from the date of Technical Bid Opening being specified. SI should ensure that in all circumstances, its Bid fulfills the validity condition. Any bid valid for a shorter period shall be rejected as non- responsive.

In exceptional circumstances, TSCA may solicit SIs consent to an extension of the period of validity. The request and the responses thereto shall be made in writing or by Fax. Bid Security




shall also be suitably extended. SI granting the request is neither required nor permitted to modify the bid.

2.10 Submission of the Bids

The Bid shall be submitted in 4 (Four) parts, post registration in the http://www.tripuratenders.gov.in, as under:

PART-I: Tender Fees and EMD. IS is expected to scan the relevant drafts into PDF format (in 150 dpi scan resolution)

Documents to be uploaded in My Space:

Where documents shall be uploaded in “My Space” of SI

Sl. Documents required to upload

“My Space” Category “My Space” Sub Category

1 PAN Card Tax related documents PAN card

2 VAT Registration Certificate

Tax related documents VAT registration certificate

3 Audited Balance sheets

Financial Details Balance Sheets

4 Relevant Experience Experience/ mfg. capacity Detailed Experience of Supplies/Works/Services of the Bidder

5 Certificate of incorporation, Blacklisting Clause undertaking, Undertaking for Opening of Office or Local Office address

Misc. document Any other document

PART-II: Pre-Qualification Documents. Digitally sign Tender Document - to be downloaded. The Tender document shall be downloaded by the Bidder, digitally sign and uploaded the same for submission of “Pre- Qualification “during actual bidding session, which will be regarded as equivalent to signing all pages of the Tender Document.

All documents to be submitted for Pre-qualification as per section 2.2 are free-format, except “SI’s Profile as per Annexure I and SI’s experience as per Annexure II” in this RFP.

For all the free-format documents, Bidder is expected to scan the relevant documents into PDF format (in 150 dpi scan resolution).




For “SI’s Profile and experience”, Bidder shall take a printout of the stated format, fill in data, sign and stamp the document before scanning the same in PDF format and finally saving the same and uploading.

PART-III: TECHNICAL BID complete technical details, solution, data sheet, and detail technical specification for the item offered. Technical Bid will be considered for evaluation for those SIs who have cleared the Part-II.

PART-IV: Financial Bid as per the template. Any tempering with financial bid will be liable to cancellation of the bid. N.B: One Hard copy of Prequalification documents and Technical Solution with all Technical details, data sheets with detail technical specification and one copy of Financial Bid(as per Annexure-XIII & XIV) in an envelope superscribed as “Commercial Bid-Do not open before Commercial Bid opening date and time” all sealed in separate envelopes enclosed in a larger envelope duly sealed and marked as Response to Request for Proposal (RFP) with title and reference number, and a statement "To be opened by addressee only” the name and address of the Bidder to be submitted to Member Secretary, Tripura State Computerisation Agency, Indranagar, Agartala-799006 by 15th May 2013.

2.11 Opening of Bids

TSCA will open bids at time mentioned at important Information sheet. SI’s representatives (Maximum 2) may also attend the opening at TSCA or also attend the same via e-procurement software. Technical Bid will be considered for those SIs whose bids shall meet all the eligibility criteria mentioned in the Pre-qualification documents.

2.12 Evaluation Criteria

Part 1 (Bid Security) Bidder’s who have submitted the valid Tender fees and EMD shall be considered for further evaluation.

Part 2 (Pre-Qualification criteria) The Evaluation Committee would evaluate the Pre-qualification. SIs should be ready to give any clarification asked by the evaluation committee. The SIs fulfilling all the conditions mentioned in the pre-qualification will be considered for Technical Bid opening.

Opening and Evaluation of Technical Bids

The Evaluation Committee would evaluate the technical bids. IS should be ready to give the presentation on their proposed solution and the queries raised by the evaluation committee in front of the Evaluation Committee at a date, time and location determined by TSCA. They are expected to reply to all the queries from the Evaluation Committee during the presentation. The presentation would be part of technical evaluation process.



TSCA may also undertake oral clarifications with the SIs. The primary function of clarifications in the evaluation process is to clarify ambiguities and uncertainties arising out of the evaluation of the bid documents.

In order to facilitate the Technical Bid evaluation, the technical criteria laid down along with the assigned weights have been presented in (Annexure). The marking scheme presented is an indication of the relative importance of the evaluation criteria.

SI’s securing a minimum of 70% marks in the technical evaluation will only be considered for further financial bid evaluation. Bids which don’t secure the minimum specified technical score will be considered technically non-responsive and hence debarred from being considered for Commercial evaluation. Scores of technically qualified SIs shall be weighed prorate on a scale of 60 and shall be carried forward for evaluation together with the scores of Commercial evaluation.

Opening and Evaluation of Commercial Bids After evaluating the Technical Bids, TSCA shall notify the SIs who’s Technical Bids were considered acceptable to TSCA, indicating the date, time and place for opening of the Commercial Bids. SI’s representative (maximum 2) may attend the commercial bid opening at TSCA, Agartala.

Scores of the Commercial evaluation would be weighed prorate on a scale of 100 with the IA with the lowest commercial quote getting 100. These commercial scores would then be added up with the score of the technical evaluation and the SI getting the maximum total score out of 100 would be considered as the successful SI (i.e. L1 SI) and called for negotiations, if required. Formula for Final Bid Evaluation is

Bm= 0.6 (TM) + 0.4 (Fn) Fn= (Fmin/ Fb)*100

Where

Bm is total marks of the SI in consideration TM is Technical Marks of the SI in consideration Fn is Normalized financial score of the SI in consideration Fb is Evaluated Cost of SI under consideration Fmin is Minimum evaluated cost of any SI

TSCA reserves the right to negotiate with the SI whose proposal has been ranked first on the basis of best value.

2.13 Bid Currency

Prices for services offered shall be quoted in Indian National Rupees only.



2.14 Bid Security

1. All SIs shall furnish, as part of its Bid, an Earnest Money Deposit (EMD) amounting to Rs.10, 00,000 (Rs. Ten Lakhs Only). Bids without this EMD will be rejected.

2. The EMD shall be in Indian Rupees and shall be in the form of Demand Draft, issued by any Nationalized/Scheduled Commercial bank in India, having a branch at Agartala drawn in favour of “Member Secretary, Tripura State Computerization Agency” payable at Agartala. Such negotiable instrument should be valid for at least sixty (60) days beyond the validity of the Bid.

3. Unsuccessful SI's EMD will be discharged or returned within sixty (60) days after the expiration of the period of Bid validity prescribed.

4. The successful SI's EMD will be discharged upon the SI signing the Contract Agreement, and furnishing the Performance Security.

2.15 Forfeiture of EMD/ Bid Security

The EMD/ Bid security may be forfeited either in full or in part, at the discretion of TSCA, on account of one or more of the following reasons:

1. The SI fails to co-operate in the Bid evaluation process 2. If the bid or its submission is not in conformity with the instruction mentioned herein 3. If the SI violates any of the provisions of the terms and conditions of the tender 4. In the case of a successful SI fails to (a) accept award of work, (b) sign the Contract

Agreement with TSCA, after acceptance of communication on placement of award, (c) furnish performance security, (d) fails to sign the Contract Agreement in time, (e) or the SI violates any of such important conditions of this tender document or indulges in any such activities as would jeopardize the interest of TSCA in timely finalization of this tender. The decision of TSCA regarding forfeiture of bid security shall be final and shall not be called upon question under any circumstances. A default in such a case may involve black-listing of the SI by TSCA.

2.16 Award of Contract TSCA will award the contract to successful SI whose bid has been determined to be responsive and has been determined to be most competitive

2.17 Performance Security Within 14 (Fourteen) days of Notification of “Award of the Work” the company shall furnish Performance Security to TSCA @ 10% of the total value of quoted bid by way of irrevocable and unconditional Bank Guarantee in favor of TSCA, payable at Agartala for a period to be specified in the award of work. This Bank Guarantee should be of duration of 48 months. Depending on the project going online the Bank guarantee may have to be extended from the date of “Go live”. The proceeds of the Performance Security shall be payable to TSCA as compensation for any loss resulting from the Company’s failure to fulfill its obligations under the terms and conditions of the Work Order. The Performance Security regarding commencement of job / task will be discharged by TSCA and returned to the company not later than 30 (Thirty) days following the date of completion of



the company’s performance, related obligations under the terms & conditions of the Work Order. Failure of the successful SI to comply with the requirements specified in this Section shall constitute sufficient ground for the annulment of the notification and forfeiture of the bid security in part or full.

2.18 Contacting TSCA 1. SI shall not approach TSCA officers beyond office hour and/ or outside TSCA office

premises, from the time of the Bid opening to the time of finalization of successful SI. 2. Any effort by a SI to influence TSCA officers in the decisions on Bid evaluation, Bid

comparison or finalization may result in rejection of the SI's offer. If the SI wishes to bring additional information to the notice of the TSCA, it should do so in writing.

2.19 Right to Accept Bids and to reject any or all Bids 1. Prior to expiration of the period of Bid validity, TSCA will notify the successful SI in writing

that its Bid has been accepted. 2. Within 7 days of receipt of such intimation, the successful SI shall give its acceptance to the

TSCA 3. Upon furnishing of Performance Security and acceptance by successful SI, TSCA will

promptly notify all unsuccessful SIs and will discharge their Bid security 4. Effort will be made by the TSCA to sign an agreement with the successful SI within 15 days. 5. TSCA will have the right to accept bid and to reject any or all bids.

2.20 Lack of Information to SI The SI shall be deemed to have carefully examined RFP document to his entire satisfaction. Any lack of information shall not in any way relieve the SI of his responsibility to fulfill his obligation under the bid.

2.21 Fraudulent & Corrupt Practice “Fraudulent Practice” means a misrepresentation of facts in order to influence a procurement process or the execution of the project and includes collusive practice among SIs (prior to or after Bid submission) designed to establish Bid prices at artificial non-competitive levels and to deprive the GoT of the benefits of free and open competition. “Corrupt Practice” means the offering, giving, receiving or soliciting of anything of value, pressurizing to influence the action of a public official in the process of project execution. GoT will reject a proposal for award if it determines that the SI recommended for award has engaged in corrupt or fraudulent practices in competing for, or in executing, the project.



3. General Conditions

3.1 Conditions Precedent

3.1.1 Commencement of the Agreement

The successful SI shall obtain the required clearances within 20 days of issuance of LoI. Agreement shall be signed only after the clearances are obtained:

The successful SI shall have received all clearances, approvals and permits including any environmental approvals. The successful SI shall also be responsible for obtaining the clearances on behalf of and in the name of TSCA, those clearances which are the responsibility of GoT /TSCA. The clearances, approvals and permits are specified in the RFP. TSCA and /or GoT will provide all necessary support to the successful SI to obtain clearances, approvals and permits including environmental approvals. All the timelines will be counted from the date of signing the Agreement. Hence signing of Agreement cannot be altered / deferred. TSCA will help in receiving different clearances but obtaining clearances is the responsibility of the SI.

3.1.2 Obligations to satisfy the Conditions Precedent

The successful SI and TSCA shall use all reasonable endeavors to satisfy the Conditions Precedent that falls within the scope of its respective responsibility.

3.1.3 Notice of fulfillment of the Conditions Precedent

Upon the date on which the successful SI becomes aware that any of the Conditions Precedent has been satisfied in full, it shall promptly give notice thereof to TSCA together with full details of the circumstances constituting such satisfaction and documentary evidence thereof.

3.1.4 Non-fulfillment of Conditions Precedent

If the Conditions Precedent set out here in above are not satisfied in full within 20 days of issuance of LoI, TSCA shall have the right to terminate/ cancel the LoI without any liability on TSCA and /or GOT. However, the Implementation Guarantee provided by the successful SI will be encashed by TSCA/GoT if the delay is ascribed to the successful SI.

3.2 Contract Obligations

Once a contract is confirmed and signed, the terms and conditions contained therein shall take precedence over the SI’s bid and all previous correspondence.

3.3 Application

These general conditions shall apply to the extent that they are not superseded by provisions of other parts of the bid document.

3.4 Governing Language

The Contract shall be written in English language. All correspondence and other documents pertaining to the Contract, which are exchanged by the parties, shall be written in the same language.



3.5 Applicable Law

The Contract shall be interpreted in accordance with the laws of the Union of India and State of Tripura.

3.6 Sub-Contracts

The SI cannot assign anyone in whole or in parts, its obligations to perform under the Contract.

3.7 Change orders

TSCA may at any time, give written order to the SI to make changes for additional functionalities specifically required, but not falling within the general scope of the current RFP/Contract. If any such change causes an increase in the cost of, or the time required for, the SI’s performance of any provisions under the Contract, the SI should notify TSCA in terms of the cost and person month efforts required for executing the change requests, TSCA will examine the efforts estimate & agreed efforts will be compensated in terms of person month charges.

3.8 Notice

1. Any notice given by one party to the other pursuant to this contract shall be sent to the other party in writing or by telex, email, or facsimile to the other party’s address, and confirmed in writing by the other party.

2. A notice shall be effective when delivered or tendered to other party whichever is earlier.

3.9 Patent Rights

The SI shall indemnify the Tenderer against all third party claims of infringement of patent, trademark or industrial design and intellectual property rights arising from the use of equipment and services or any part thereof.

3.10 Taxes and Duties

Sales Tax/ Service Tax/VAT/Work Contracts Tax/ Octroi and other statutory levies shall be paid by SI as applicable. TSCA shall pay any increase in duties, taxes and surcharges and other charges on account of any revision, enactment during the period of validity of the Bids and also during the contract period. In case of any decrease in duties, taxes and surcharges and other charges, IA should refund the same to TSCA. The decision of TSCA in this regard will be final and binding and no disputes in this regard will be entertained.

3.11 Operation and Maintenance

The SI shall support the State for the periods of 3 years for the maintenance of the infrastructure after formal go live. The SI will respond to any issue raised by the state or notified by the authorize person.

3.12 Force Majeure

1. For the purpose of this Article, Force “Majeure” means any cause, which is beyond the control of the SI or GoT as the case may be, which such party could not foresee or with a reasonable amount of diligence could not have foreseen, and which substantially affect the performance of the Contract, such as:-

- War / hostilities



- Riot or civil commotion / Political Unrest

- Earth Quake, Flood, Fire, Tempest, Epidemics, Lightning or other natural physical Disaster, Quarantine restricts and Freight embargoes

- Restrictions imposed by the Government or other statutory bodies, which is beyond the control of the SI, which prevent or delay the execution of the order by the SI.

2. If a Force Majeure situation arises, the SI is required to promptly notify TSCA in writing of such condition and the cause thereof within a period of three (3) days from the date of happening of such an event requiring invocation of this force majeure article. Unless otherwise directed by TSCA in writing, the SI will continue to perform its obligations under this supply order as far as is reasonably practical and shall seek all reasonable alternative means for performances of this order.

3.12.1 Force Majeure Exclusions

Force Majeure shall not include the following event(s) and/or circumstances, except to the extent that they are consequences of an event of Force Majeure :

(a) Unavailability, late delivery, or changes in cost of the Cloud Enablement of TSDC, machinery, equipment, materials, spare parts.

(b) delay in the performance of SI or their agents. (c) non-performance resulting from normal wear and tear of the materials and

equipment; and (d) non-performance caused by, or connected with, the Affected Partys:

(i) negligent or intentional acts, errors or omissions; and/or

(ii) failure to comply with an Indian law or Indian Directive; and/or

(iii) breach of, or default under the Agreement.

3.12.2 Procedure for Calling Force Majeure

The Affected Party shall notify to the other Party in writing of the occurrence of the Force Majeure as soon as reasonably practicable, and in any event within 3 (three) days after the Affected Party came to know or ought reasonably to have known, of its occurrence and that the Force Majeure would be likely to have a material impact on the performance of its obligations under the Agreement.

Any notice pursuant this clause shall include full particulars of:

(i) the nature of each Force Majeure Event which is the subject of any claim for relief under the Agreement;

(ii) the effect which such Force Majeure Event is having or is likely to have on the Affected Party’s performance of its obligations under the Agreement;

(iii) the measures which the Affected Party is taking, or proposes to take, to alleviate the impact of the Force Majeure Event and restore the performance of its obligations under the Agreement which are affected; and

(iv) any other information relevant to the Affected Party’s claim.



3.12.3 Procedure for Claiming Relief

(i) Where an Affected Party claims relief on account of Force Majeure Event then, the rights and obligations of both Parties under the Agreement shall be suspended to the extent that they are affected by such Force Majeure Events.

(ii) In an Event of Force Majeure :

(a) the Affected Party shall use its best efforts to minimise the effects of

Force Majeure and remedy any inability to perform due to Force Majeure;

(b) the Affected Party shall provide weekly written reports to the other Party regarding its progress in overcoming the adverse effects of the Force Majeure event;

(c) the Affected Party shall, as soon as reasonably practicable after claiming such relief, provide the other Party with written notice containing such information as may be reasonably required to justify the claim for relief due to Force Majeure;

(d) the Affected Party shall claim in respect of physical loss or damage resulting from the event constituting Force Majeure which are available from Insurances pursuant to any Insurance maintained by the Affected Party and ensure such claims are made as soon as is reasonably possible and that the proceeds of any such Insurance claims are applied to remedy the effects of the event constituting Force Majeure as soon as is reasonably possible; and

(e) the Affected Party shall, at its own cost, take all steps reasonably required to restore its ability to perform its obligations under the Agreement as soon as possible, including the re-commissioning of any affected part of the Cloud Enablement of SDC.

(iii) When the Affected Party is able to resume performance of its obligations under the Agreement, it shall promptly give the other Party written notice to that effect. In no event shall the suspension of performance be of greater scope and of longer duration than is necessitated by Force Majeure.

3.12.4 Extensions due to Force Majeure Neither Party shall be responsible or liable for, or deemed to be in breach of the Agreement because of any failure or delay in complying with its obligations under the Agreement, due solely to one or more events of Force Majeure, and the periods allowed for the performance by the Parties of such obligation(s) shall be extended on a day-for-day basis from the date of the event of Force Majeure provided that no relief shall be granted to the Affected Party to the extent that such failure or delay would have nevertheless been experienced by that Party had such Force Majeure event not occurred.

3.12.5 Termination as a result of Exceptional Event Notwithstanding anything contained herein, in case the period of Force Majeure lasts for more than 3 (three) months from the occurrence of the event of force majeure, whether such force majeure event occurs before or after commissioning of the Project, either party shall have the right to terminate the Agreement by a written notice of 15 (fifteen) days to the other party.



The IA shall give notice to the TSCA of: (i) the cessation of the event or circumstance of Force Majeure being

claimed; and (ii) the cessation of the effects of the event or circumstance of Force Majeure

being claimed on the enjoyment by such Party of its rights or the performance of its obligations pursuant to the Agreement, as soon as possible after becoming aware thereof.

3.13 Handing Over 1. At the end of the services period of 3 years, TSCA may exercise its option to renew the

contract with the existing SI or may invite fresh bids for subsequent maintenance or extension.

2. If handover is required to TSCA or any other SI other than the implementing SI, at the end of the existing contract or otherwise, the implementing SI would be responsible for handing over the complete know-how documentation records/software logs and all such relevant items that may be necessary for the transition process.

3.14 Termination 1. Termination for Default: If the SI fails to carry out the award / work order in terms of this

document within the stipulated period or any extension thereof, as may be allowed by TSCA, without any valid reasons acceptable to TSCA, TSCA may terminate the contract after giving one month notice, and the decision of TSCA on the matter shall be final and binding on the SI. Upon termination of the contract, TSCA shall be at liberty to get the work done at the risk and expense of the SI through any other agency, and to recover from the SI compensation or damages.

2. Termination for Insolvency: TSCA can terminate the contract if the SI becomes bankrupt and/or losses the desired state of insolvency with a notice of 15 days. TSCA, in such cases of termination, will not be responsible for any loss or financial damage to the SI resulted due to the termination. The Government will also, in such cases have the right to recover any pending dues by invoking the performance bank guarantee or any such instrument available with the Government. In this event, termination will be without compensation to the SI, provided that such termination shall not prejudice or affect any right of action or remedy which has accrued or will accrue thereafter to TSCA. In exercise of the exclusive charge upon the assets of the SI, TSCA shall be entitled to take over the assets of the SI.

3. Force Majeure Termination: In case the period of Force Majeure lasts for more than 3 (three) months from the occurrence of the event of force majeure, whether such force majeure event occurs before or after commissioning of the Project, either party shall have the right to terminate the Agreement by a written notice of 15 (fifteen) days to the other party. In the event of such termination, TSCA will take over all equipment (without any liability) necessary for the proper and normal operation of the project.

3.15 Resolution of Disputes and Arbitration 1. TSCA and the selected SI shall make every effort to resolve amicably by direct informal

negotiation any disagreement or dispute arising between them under or in connection with the Contract.

2. If, after thirty (30) days from the commencement of such informal negotiations, State and the selected SI have been unable to amicably resolve dispute, either party may require that the dispute be referred for resolution to the formal mechanisms, which may include, but are



not restricted to, conciliation mediated by a third party acceptable to both, or in accordance with the Arbitration and Conciliation Act, 1996.

3. All Arbitration proceedings shall be held at Agartala, Tripura, and the language of the arbitration proceedings and that of all documents and communications between the parties shall be in English.

3.16 Acquaintance with local conditions 1. The SI is expected to fully get acquainted with the local conditions and factors, which would

have any effect on the performance of the contract and /or the cost. 2. The SI is expected to know all conditions and factors, which may have any effect on the

execution of the contract after issue of Letter of Intent/Award as described in the bidding documents. The Tenderer shall not entertain any request for clarification from the SI regarding such local conditions.

3. It is the SI’s responsibility that such factors have properly been investigated and considered while submitting the bid proposals and no claim whatsoever including those for financial adjustment to the contract awarded under the bidding documents will be entertained by the Tenderer. Neither any change in the time schedule of the contract nor any financial adjustments arising thereof shall be permitted by the Tenderer on account of failure of the SI to know the local laws / conditions.

3.17 Statutory and Regulatory Approvals The SI shall be responsible for obtaining approvals for any statutory and regulatory requirements from any of the authorities. Further, the SI shall be responsible to get required documentation completed for obtaining such approvals from time to time.

3.18 Confidentiality Any information pertaining to GoT /TSCA or any other agency involved in the project, matters concerning GoT/TSCA that comes to the knowledge of the SI in connection with this contract, will be deemed to be confidential and the SI will be fully responsible, for the same being kept confidential and held in trust, as also for all consequences of its concerned personnel failing to observe the same. The SI shall ensure due secrecy of information and data that is not intended for public distribution.

3.19 Limitation of Liability The liability of the TSCA or SI for its obligations under the Contract shall in no case exceed the total value of the Contract.

3.20 Failure to Agree with the Terms and Conditions of the RFP Failure of the successful SI to agree with the Terms and Conditions of the RFP shall constitute sufficient grounds for the annulment of the award, in which event TSCA may award the Contract to the next best value SI or call for new Bids.

3.21 Indemnification (1) The SI shall indemnify TSCA and hold it harmless from all losses, claims, causes of action, damages, liabilities, fines, penalties and expenses of all kinds (including legal expenses, court



fees and professional advisory service expenses) arising from or out of any adverse claims of any and all persons related to the execution of services as mentioned in the RFP. Notwithstanding anything expressed or implied in the Agreement to the contrary:-

(i) Neither Party shall be liable to the other Party in Agreement, tort, warranty, strict liability or any other legal theory in respect of any cost, expense, loss or damage of an indirect, consequential, incidental, punitive or exemplary nature suffered by the other including but not limited to loss of use of property, Agreement, production, maintenance charges or goodwill or cost of business interruption or increased costs of working howsoever arising including but not limited to the default or sole or concurrent negligence of a Party and whether or not foreseeable at the date of the Agreement.

(ii) Such indemnity shall not extend to any loss, death or injury or any expenses relating thereto to the extent that it was caused by any act or omission of either party or the failure of either party to take reasonable steps in mitigation thereof.

(iii) Such indemnity shall not be applicable to any loss, damage, cost or expense in respect of, and to the extent that either party is compensated pursuant to the terms of any other agreement or under any policy of insurance.

For the purpose of this clause:-

(1) The SI shall include its directors, employees, agents, Affiliates and sub-contractors.

Properties and Facilities -

The SI shall assume full responsibility and liability for the maintenance and operation of the equipments, properties and facilities supplied and installed by SI under this project and shall indemnify and hold TSCA harmless from all liability and expense on account of any and all damages, claims or actions, including injury to and death of persons, arising from any act, accident or omission in connection with or arising out of the installation, presence, maintenance and operation of such properties and facilities.

3.22 Control and Possession

The SI shall be deemed to be in control and possession of the equipment necessary for the proper and normal operation of the Cloud Enablement of SDC.

3.23 Replacement: The SI is required to replace, maintain & repair any equipment under this project getting damage or become non- functional.



3.24 Books & Records SI shall maintain adequate books and records in connection with Contract and shall make them available for inspection and audit by TSCA during the terms of Contract until expiry of the performance guarantee.

3.25 Amendment to the Agreement Amendments to the Agreement may be made by mutual agreement by both the Parties. No variation in or modification in the terms of the Agreement shall be made except by written amendment signed by both the parties. All alterations and changes in the Agreement shall take into account prevailing rules, regulations and laws.

3.26 Use of Agreement Documents and Information The SI shall not without prior written consent from TSCA disclose the Agreement or any provision thereof or any specification, plans, drawings, pattern, samples or information furnished by or on behalf of TSCA in connection therewith to any person other than the person employed by the SI in the performance of the Agreement. Disclosure to any such employee shall be made in confidence and shall extend only so far as may be necessary for such performance. The SI shall not without prior written consent of TSCA make use of any document or information made available for the project except for purposes of performing the Agreement. All project related documents issued by TSCA other than the Agreement itself shall remain the property of TSCA and Originals and all copies shall be returned to TSCA on completion of the SI's performance under the Agreement, if so required by the TSCA



3.27 Exit Management

1. Upon completion of the contract period or upon termination of the agreement for any reasons, the IA shall comply with the following: a) notify to TSCA forthwith the particulars of all Project Assets; b) deliver forthwith actual or constructive possession of the Cloud Enablement of SDC

Project free and clear of all Encumbrances and execute such deeds, writings and documents as may be required by the TSCA / State Govt. for fully and effectively divesting the SI of all of the rights, title and interest of the SI in the Cloud Enablement Project;

c) comply with the Divestment Requirements set out in the RFP except in case if Termination of this Agreement

d) pay all transfer costs and stamp duty applicable on hand back of project assets except in case the Project is being transferred due to State Govt. of Default, Indirect Political Event, Political Event or expiry of Concession period, where State Govt. shall be responsible for transfer costs and stamp duty, if any.

2. Subject to clause 1 of exit management, upon completion of the contract period or upon termination of the agreement, the SI shall comply and conform to the following Divestment Requirements in respect of the Cloud Enablement Project: a) all Project Assets including the hardware, software, documentation and any other

infrastructure shall have been renewed and cured of all defects and deficiencies as necessary so that the Cloud Enablement Project is compliant with the Specifications and Standards set forth in the RFP, Agreement and any other amendments made during the contract period;

b) the SI delivers relevant records and reports pertaining to the Cloud Enablement Project and its design, engineering, operation, and maintenance including all operation and maintenance records and manuals pertaining thereto and complete as on the Divestment Date;

c) the SI executes such deeds of conveyance, documents and other writings as the State Govt. may reasonably require to convey, divest and assign all the rights, title and interest of the SI in the Cloud Enablement Project free from all Encumbrances absolutely and free of any charge or tax unto the State Govt. or its Nominee; and

d) the SI complies with all other requirements as may be prescribed under Applicable Laws to complete the divestment and assignment of all the rights, title and interest of the SI in the Cloud Enablement Project free from all Encumbrances absolutely and free of any charge or tax to State Govt. or its nominee.

3. Not earlier than 3 (three) months before the expiry of the contract Period but not later than 30 (thirty) days before such expiry, or in the event of earlier Termination of the contract, immediately upon but not later than 15 (fifteen) days from the date of issue of Termination Notice, the Independent Consultant or authorized person as nominated by the TSCA shall verify, in the presence of a representative of the SI, compliance by the SI with the Divestment Requirements set forth in the RFP in relation to the Cloud Enablement Project and, if required, cause RFP for Cloud Enablement of SDC appropriate tests to be carried out



at the Divestment Requirements are found by either Party, it shall notify the other of the same and the SI shall rectify the same at its cost.

4. Upon the SI conforming to all Divestment Requirements and handing over actual or constructive possession of the Project to State Govt. or a person nominated by State Govt. in this regard, State Govt. shall issue a certificate substantially in the form set forth in earlier Section, which will have the effect of constituting evidence of divestment of all rights, title and lien in the Cloud Enablement Project by the SI and their vesting in Cloud Enablement Project pursuant hereto. Issue of such certificate shall not be unreasonably withheld by State Government. The divestment of all rights, title and lien in the Cloud Enablement Project shall be deemed to be complete on the date when all the Divestment requirements have been fulfilled or the Certificate has been issued, whichever is earlier, it being expressly agreed that any defect or deficiency in any Divestment Requirement shall not in any manner be construed or interpreted as restricting the exercise of any rights by State Government or its nominee on or in respect of the Cloud Enablement Project on the footing as if all Divestment Requirements have been complied with by the Concessionaire.



4. Special Conditions

The following clauses shall supplement the Instructions to SIs and General Conditions of Contract.

4.1 SI’s Responsibility The SI shall implement the project strictly as per the plan approved by TSCA. The implementation plan will take into consideration the following:

• The SI shall provide details of equipment (including Architecture/Version/ Make/Build used, and Technical Specifications) that will be incorporated in Cloud Enablement of SDC.

• Implementation plan will be finalised during the period in which approvals & clearances will be taken.

• The SI shall provide the necessary technical support, Manuals/Publications like Standard Operating Procedure (SOP) and other Documentary information to TSCA/GoT and its user organizations in implementing Cloud Enablement of SDC.

4.2 Tests The Tests concern all the equipment, systems and sub-systems supplied against this tender.

4.2.1 Partial Acceptance Test Once the system is installed and operating, it shall be tested by the SI and witnessed by TSCA. The Test shall be carried out as per the detailed test procedure supplied by SI and approved by the TSCA. Once the Tests successfully performed, the temporary acceptance of the system will be given. Only then the system will be ready for “Test Run”.

4.2.2 Test Run This Test aims at keeping the complete system in operation for a period of 10 days continuously. In case of failure, the Tests will be re-started till the system operates without failure for 10 days continuously. TSCA shall have the right to reject the complete system or part thereof in the event(s) of the acceptance Tests failing in two attempts. The “Test Run” shall be carried out after the commissioning of complete system. Various observations and test results obtained during the various tests shall be documented and produced in the form of a report by the SI. If malfunctions or failure of a unit or sub-system repeats, the Test shall be terminated and SI shall replace the necessary components and assemblies to correct the deficiencies. Thereafter, the Test shall commence all over again from the start as mentioned above. If after this one replacement, the unit or sub-system still fails to meet the specifications, the SI shall replace the complete unit or sub-system with the one that meets the requirements, and restart the Test all over again. All cost for repair/replacement of defective unit/ component/system/sub-system shall be borne by the SI.

4.2.3 Final Acceptance Test After the successful test run of the complete system for 10 days, a Final Acceptance Test Certificate (FAT) shall be issued by the TSCA to the SI. The date on which Final FAT certificate is issued shall be deemed to be the date of successful commissioning of the Cloud Enablement of TSDC.



4.3 Payment Terms The payment for implementation of Cloud Enablement of SDC will be as follows:

a. CAPEX Payment Schedule

S. No Payment Schedule Fee Payable Remarks

1. Delivery of all the Components

(Hardware + Software)

30% of CAPEX On successful acceptance of the BOM by the competent authority of the STATE

2. Installation, commissioning, Integration of all equipments and Successful Final Acceptance Test (FAT) and Training of State representatives and officials for the deployed solution

60% of CAPEX On Successful signoff by the competent authority

3. Balance 10% will be amortized for the period of 3 years of the project and shall be paid to the SI in equivalent yearly.

b. OPEX Payment Schedule • There are 2 (two) types of OPEX:

a. AMC cost for Hardware and Support & Subscription cost for Software and Licenses.

b. Service Support for all the calls escalated by the onsite service support Team. • The total amount of the OPEX shall be paid in equivalent annually to the SI and will

be calculated based on the period of the project, considering status of SLA achieved/breached as explained at Section 7 of this Document.

On receipt of such invoice after verification, TSCA shall release the amount to the SI. The currency of payment shall be Indian Rupees. If there is any deficiency in the performance of contractual obligations on the part of the SI, the SI shall be liable for imposition of appropriate penalties as specified in the RFP and TSCA shall be entitled to deduct such penalties at source while making payment to the SI for the services provided as mentioned & forfeit the guarantee submitted.



5. Scope of Work:

State Data Centre has been equipped with infrastructure which will enable State departments 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 across all SDCs 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 SDC.

These Cloud solution requirements would include all the necessary components/ modules which are necessary to provide Infrastructure as a service (IaaS) to various line departments within the State as a (Private Cloud) to start with and have the capability of moving gradually for Platform-as-a-service (PaaS) and Software-as-a-service (SaaS).

After having analyzed the infrastructure presently provisioned in the SDCs and technology advancements required to make them Cloud enabled, following have been considered. Cloud solution should possess the following capabilities:

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

i. Self Service portal, Catalogue and directory Maintenance ii. Automation and Orchestration

iii. Common resource pool iv. Service provisioning and Service delivery v. Capacity Planning and Management and optimization

vi. Life Cycle Management vii. Monitoring and Reporting Solutions

viii. Migration of VMs within and across enclosures While we are moving towards Cloud based service approach, it is also very much essential that the security requirements are addressed adequately. The solution should be capable of enabling automatic scale-up and scale-down of services hosted in the cloud based on user demand or other factors, should ease Infrastructure Management, Application Management and should be able to consolidate resources, should be agnostic to the underlying hardware, storage, network, operating system, and hypervisor, should be interoperable across multiple enclosures.

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.

The selected System Integrator (SI) shall study the requirements of the project and existing systems. The SI shall Supply, Installation, Commissioning, Testing, Training and knowledge transfer for Cloud Enablement Infrastructure of TSDC. Subsequently it has to support for 3 (three) years from “go live” or successful completion of FAT. The solution should first test run of the identified application from the existing application of TSDC as pilot basis. Once stabilized and accepted by the TSCA, SI shall migrate the other application identified by the TSCA into Cloud Environment. The broad scopes of work are mentioned below:

For implementation of Cloud solution SI would use the Blade Enclosure being supplied through this RFP. SI has to cover Cloud enablement in 2 more Blade Enclosure already existing in TSDC.

5.1 Supply, Installation, Commissioning, Testing, Training and Knowledge transfer for TSDC Cloud Enablement Infrastructure

a) The Bidder shall provide the detailed design document of the architecture of the proposed Cloud Solution and 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 hardware & software as per the proposed solution. The Bidder has to ensure that the solution should work as desired by TSCA (tuned and customized to suit TSCA’s technical-needs) 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.

c) The Bidder shall be responsible for ensuring implementation of the proposed solution with existing infrastructure, solutions present in the SDC and optimal functioning of all the components post installation. The implementation shall be carried out in accordance to the existing SDC Policies, ISO 20000 & ISO 27001 standard policies. This implementation should comply with all the functionalities stated in the Functional Requirement Specifications (FRS) (Section VI) and conform to the agreed deployment/implementation architecture. It should 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, etc.) for the same duration of support applicable for the overall solution. The Bidder should ensure that the Cloud solution should be 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 components listed in Annexure XV - Existing SDC Infrastructure should work with the virtual machines for cloud environment.



d) The Bidder should provide the documentation on the proposed cloud solution include, detailed of

• Installation and Configuration Manuals

• Operation and Troubleshooting Manuals

• FAQs & Self-Supporting Manuals based on Knowledge-Base

e) The State will appoint a representative to be associated with the Selected Bidder team so that full hand holding of the entire solution should be done from the beginning, to ensure complete and smooth knowledge transfer.

f) The necessary server, operating system, database, Application-Software/Plugins and any other required Licenses and Certification of the hardware for Cloud Solution etc. would be provisioned by SI on its own and cost of the same would be built-in the solution proposed as per proposed Solution. No separate line items would be mentioned for these items in the BOM.

g) Coordination with all the project stakeholders to ensure that all Data Centre activities are carried out in a timely manner.

h) Coordination with vendors and OEMs to ensure that time and equipment dependencies are optimally managed

i) The detailed vendors database shall be maintained like contact person, telephone nos., escalation matrix, response time and resolution time commitments etc.

j) Comprehensive training during the transition phase shall be the key to successful Operations and Maintenance hence, the Bidder is required to undertake robust training. The successful Bidder is free to propose the training plan. However at a minimum, the plan should include the following:

SDC Cloud Enablement Training Schedule

S. No. Training Description A IT Training

1. Overview of Components Installed

2. Server Virtualization Configurations put in Use

3. Adherence and Compliance Standards

4. Overview of Migration from stand-alone Applications to the Virtualized Environment

5. Overview of Cloud Management and Monitoring Modules, Thresholds, KPIs

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



SDC Cloud Enablement Training Schedule

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 and program shall be finalized between the SI and the State. a) A training workshop needs to be arranged by the Bidder for hands-on training for the

selected groups of person by the State. This workshop shall be for 3 (Three) weeks and will be delivered by people certified in Cloud and Virtualization. 1 (One) week training would be prior to the Test Run and 2 (Two) week after the Test Run.

b) All the training material will be provided by the Bidder. Training material should include the presentation used for training and also the relevant documents covering all the topics

c) The State, prior to take over the O&M phase, shall undertake a detailed Acceptance Test process, which will include:

• Component wise Acceptance • Overall Solution Acceptance

d) It is the mandate that cloud OEM representative will certify for satisfactory deployment of their components. Representatives from the OEM shall also be present during the Final Acceptance Tests.

e) FAT completion would only be considered if at least one or more application from the SDC has been put on Cloud Environment and tested under various workloads for successful demonstration of capabilities.

f) 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. This Document of Pre-Requisites may include: i. Rack Space requirements in the available racks ii. Power requirements to ensure Uninterrupted Services iii. Passive component requirements iv. Planned downtime requirements, if any v. Structural Requirements or Ventilation/Exhaust or such vi. Connectivity Requirements

(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 SDC)

g) The successful Bidder shall ensure that the project documents are maintained as per ISO 9001-2008, ISO 20000-2011 & ISO 27000-2005 requirements.

h) The solution should be properly integrated with the existing Helpdesk services of the SDC.

i) The Bidder shall ensure that the products quoted are not “end of life as on Bid Submission date. If in case the support for the product quoted has been stopped/ withdrawn till the time of delivery of equipment, the same will be changed with the



superior product at no extra cost. The support including spares, patches, upgrades for the quoted products shall be available for the entire period of the Project

j) The prices would be discovered in two parts: • CAPEX - This shall include the Supply, Installation, Configuration, Testing, Training

and FAT.

• OPEX – This shall include the product (Hardware & Software) support and necessary subscription / licensing renewals cost for the 3 (three) years period after the successful commissioning & FAT. TSDC team will provide services support during this 3 years and SI has to train them to make them capable to do so and SI has to certify the team for that. SI has to provide service support if any service support call get escalated to them by onsite service support team for 3 years after FAT.

Integration

This shall be a black-box testing role primarily to ensure that the application to be deployed

does not disrupt the Cloud Environment and affect other SDC infrastructure in terms of

performance and security. The technical tasks to be carried out shall be as follows:

• Functional Testing: Ensuring that the application functionality is adequately on the

cloud environment. The functional testing of application will necessarily be minimal as

this is a core responsibility for SI,

• Performance Testing: Ensuring that the application meets expressed performance

requirements of the cloud environment by using performance test tools and performance

monitoring tools.

• Security Testing: Testing for exploitable application security weaknesses that undermine

the application security or the security of the infrastructure.

5.2 Operation and Maintenance for SDC Cloud Enablement

After the successful completion of supply, installation, commissioning, testing, training and

knowledge transfer, a team identified by the TSCA will provide 24x7 operation and maintenance

support for the period of 3 (three) years from the date of go-live or successful completion of

FAT.

SI shall provide support to the onsite teams, support shall be for 24x7 till the end of the project.

The escalated calls will be approximate 15 calls a month.

The support will include, but not limited to, troubleshooting & addressing the functionality,

availability, performance, security and other issues escalated by the onsite team. It will also

support on the time of upgrades of applications as requested. The detailed scope of work for

support will be aligned with the Section 7 – Service Level Agreements.



6. Roles and Responsibility (RACI Matrix) 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- Advice C- Coordinate I- Implement The table below summarizes the Roles and Responsibilities of stakeholders involved in the project:

Stakeholder S. No. Activity 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)

C I C

1.3

Cloud SI to submit a plan for the following: • Project Implementation, • Training and Knowledge Transfer Plan • Downtime time etc.

C I C

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 IT Infrastructure components (HW and SW) (active and passive) such as Server Virtualization, Cloud Management and monitoring tools and other IT components required at the 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



Stakeholder S. No. Activity State /

CT Cloud

SI DCO

1.7 All equipment (HW, 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, HW, 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 SIA, CT, DCO or other

I

4.2

Training to be provided by the Bidder’s resources who are OEM certified to the officials of State people to be identified by the State covering Implementation, day to day operations & management and other aspects or as decided by the State Government. (As per the training plan approved by the State)

C I C

5 Operation 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 C C I

5.3 Support during the Operations phase for any error correction or version Updations

C I C

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

I C



7. Service Level Agreement

The purpose of this Service Level Agreement (hereinafter referred to as SLA) is to clearly define the levels of service which shall be expected from the Cloud Solution provider (hereinafter referred to as SI) towards the State during the implementation and its subsequent support for the project period of 3 years

7.1 Definitions For the purpose of this SLA, the definitions and terms as specified in the contract along with the following terms shall have the meanings set forth below:

1. “Incident” refers to any event / abnormalities in the functioning of the Cloud Enablement components in State Data Centre / specified services that may lead to disruption in normal operations of the Cloud based services

2. “Support" shall mean the 24x7 supports which shall handle patch updates, upgrades Fault Reporting, Trouble Ticketing, and resolution of related enquiries during this contract. Interactive remote diagnostic support shall also be there, allowing technical support engineers to troubleshoot an incident securely through a browser-based remote control feature.

3. Availability shall mean the time for which the services offered are available for conducting operations from the equipment / solution hosted on Cloud.

4. Scheduled Maintenance Time / Scheduled downtime shall mean the time that the System is not in service due to a scheduled work. Scheduled maintenance time is planned downtime with the prior permission of the designated SDC operator.

5. Scheduled operation time means the scheduled operating hours of the System for the month. All scheduled maintenance time on the system would be deducted from the total operation time for the month to give the scheduled operation time. The total operation time for the systems and applications hosted on cloud will be 24x7x365. Downtime means accumulated time during which the System is totally inoperable within the Scheduled Operation Time but outside the scheduled maintenance time.

6. Subsystem Downtime shall mean the downtime observed in major components of the cloud infrastructure. E.g. in Cloud Network or Virtualization Layer or Storage, Virtual Operating Systems etc. will be the major components in cloud solution. The amount (%) that the sub-system contributes to the mission of the Total System Total System Downtime shall be defined as the sum of the downtimes of each functional sub-system in as much as that sub-system contributes to the mission of the Total System. The average downtime of the all subsystems will be calculated by following formula:

Subsystem Downtime= (Downtime Subsystem A + Downtime Subsystem B + Downtime Subsystem N) / Total Subsystems.

7. “Response time” is defined as the time between receipt of the incidence and a support start time for working on the incidence

8. “Resolution Time” shall mean the time taken (after the incident has been reported to the SI), in resolving (diagnosing, troubleshooting and fixing) or escalating (to the second



level or to respective Vendors, getting the confirmatory details about the same from the Vendor and conveying the same to the State), the services related troubles during the first level escalation. The resolution time shall vary based on the severity of the incident. The severity parameters have been defined below:

The severity would be as follows:

a. Critical: In case 1 or more than 1 physical servers are down threatening business continuity (VMs on the physical server are not accessible and not working and Multiple Clients are affected) which is attributable to the Cloud Solution implemented by the SI and an immediate workaround is not possible, it shall be considered as a Critical incident. Or Incidents whose resolution shall require additional investment in components or time or shall involve coordination with OEMs. These incidents shall impact the overall functioning of the TSDC.

b. High: Incidents, whose resolution shall require replacement of hardware or software parts, requiring significant interruption in working of that individual component. For example, installation of operating system, replacement of switch etc.

c. Medium: In case an essential functionality of the Cloud solution becomes unavailable in the Live SDC environment which is not actually hampering the live services of the Cloud but may impact the services if not attended immediately will be termed as medium.

d. Low: The incidents would be termed as low, which does not have any significant impact on the Cloud service delivery (little or no impact on business entity).

i. Delay of less than 1 Hour in provisioning of Virtual Machine

ii. A minor problem or question that does not affect the software function,

iii. An error in software product Documentation that has no significant effect

on operations; or

iv. A suggestion for new features or software product enhancement.

7.2 Service Levels

This SLA document provides for minimum level of services required as per contractual obligations based on performance indicators and measurements thereof. The SI shall ensure provisioning of all required services, while monitoring the performance of the same, to effectively comply with the performance levels mentioned below. The services provided by the SI shall be reviewed by TSCA that shall:

• Regularly check performance of the SI against this SLA. • Discuss escalated problems, new issues and matters still outstanding for resolution. • Review of statistics related to rectification of outstanding faults and agreed changes.

• Obtain suggestions for changes to improve the service levels.



The SLAs have been segregated in the following categories:

1. Implementation Service Levels

2. IT Infrastructure Service Levels

3. Cloud Services Levels

The targets shown in the following tables are mapped with the requirements specified for Cloud Enablement components for Tripura State Data Centre, as a part of support for the Cloud infrastructure; it is the responsibility of the SI to maintain the same SLAs with the OEM for their support and maintenance which can be extended to the State.

7.2.1 Implementation service levels

The service levels indicators and the target performance levels to be maintained by the SI during the Implementation of Cloud Enablement for TSDC. The target performance metrics as outlined in the table below:

Table 1: Implementation Service Levels

S. No.

Service Category

Service Level Target Penalty

1.

Supply, Installation and Commissioning

12 weeks from the date of signing of contract. FAT has to be completed successfully within 12 weeks from the signing of contract by SI

Penalties will be applicable after 12 weeks, if the implementation work is still not completed. (Work completion shall be considered after successful completion of FAT, as well as submission of all documents, and submission of all applicable reports as mentioned in the Contract before FAT completion) A penalty of 2% per week subject to a maximum of 10%. Penalty percentage as mentioned will be computed on the final value of contract between State and SI.

2. Training

3 (Three) weeks from the completion of Supply, Installation and Commissioning (1 (One) week before Test Run and 2 (TWO) week after Test Run)

Penalties will be applicable after 3 weeks from the completion of Supply, Installation, Commissioning and Test Run. A penalty of 1% per week to a maximum of 5%. Penalty percentage as mentioned will be computed on the final value of contract between State and SI.



System Integration Services include the following:

• Feasibility Check

• Team Mobilization for the commencement of the work

• Before the initialization of the work a complete schedule will be provided by the SI to the State in the form of a Project Plan.

• Weekly track report would be given to the State (with Milestones achieved and Weekly Project Status Report) by end of every week for acknowledgement and review

• Delivery of all the Equipment and Software on time which are part of Scope of Work

• Installation & Commissioning of all the components

• Installation report needs to be checked and passed by the State

• All the documents, manuals & CDs need to be made available to the State

• Licenses, Service Support documents will be checked and cleared by the State

• Component-wise installation, commissioning & testing schedule should be made available to the State, by which periodic tracking of all the components can be done

• Quality control document for installation and commissioning should be prepared by SI and verified by the State <before / after installation completion / kickoff>

• Complete Load testing of all the equipments as per the equipment Data Sheet would be done by SI in presence of appointed concerned authority of the State

• Final Acceptance Test (FAT) of the Cloud Enablement components as a whole which will also include running at least 1 application in the cloud environment at the SDC

• Training schedule to be submitted two weeks prior to the start of Training and approved by the State

• System Integration services may also include any scripting, adapters required for integration of the solution

• Handover of the solution to the State, operating and maintaining it for a period of 2 months from the date of O&M start date as declared by the State

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



7.2.2 IT Infrastructure Support Service Levels

The following outlines the service level indicators and the target performance levels to be maintained by the SI during the contract period for 3 years of support. The target performance metrics as outlined in the table below:

Table 2: IT infrastructure related Service Levels

S.

No.

Measurement Service

Level Target

Penalty

1.

Server &

Storage

Hardware

Availability

99.5%

After reporting of the issue, SI should respond to the call within 30 min’s, if the SI fails to respond 0.1% of the annually payment (excluding payment for service support) for every 30 min’s to the maximum of 2 hrs.

After the responding to the call, the issue or problem shall resolve within 2 hrs. If the issue or problem is not resolve SI has to be onsite within 24 hrs and resolve the issue at the earliest to complied with the availability target of 99.5%

As per availability target, 43.8hrs of down time is acceptable yearly for any server and storage hardware or any other hardware supplied through this RFP. For any particular hardware faces down time beyond 43.8hrs yearly for such down time penalty will be imposed 0.5% per hrs of the annually payment (excluding payment for service support).

Maximum annually penalty related to server and storage hardware availability would be 10% of the annually payment (excluding payment for service support).

The above SLA is on the Servers and other equipments which are procured through this

RFP.

Note: - For the Components which are in Redundant mode or High Availability Mode or in Cluster, if one of the redundant components goes down and the services required form that particular set of components are still working/ not hampered, than the SI shall be given 24Hrs time to rectify the components, if it is still not rectified within 24Hrs, the SLA as defined above will come into existence. If in between 24hrs the other component goes down, and the entire services required from that components are not available, the penalties as defined in the table above will come into existence from that particular point.



IT Infrastructure Services includes the following:

Server Availability

Network Availability

Link to the storage components

Intranet Connectivity

Hypervisor Availability

Operating System Availability

Response time

Remote Support (Online or Phone support)

Any component that is reported to be faulty / non-functional should be either fully repaired or replaced (of equivalent configuration) within the time frame agreed upon in the Service Level Agreement (SLA).

Diagnostic report should be made available to State as and when required.

Management of changes to Storage schema, disk space, storage, user roles.

Performance monitoring and tuning of the Hypervisor and OS on a regular basis

Management of update or patch update as and when required with minimal downtime.



7.2.3 Software Support Service Levels

The following outlines the service level indicators and the target performance levels to be maintained by the SI during the contract period for 3 years of O&M. The target performance metrics as outlined in the table below:

Table 3: Cloud Services related Service Levels

S.

No.

Measurement Service Level

Target

Penalty

2.

Uptime of

Virtual

Software

99.5%

After reporting of the issue, SI should

respond to the call within 30 min’s, if the SI

fails to respond 0.1% of the annually

payment (excluding payment for service

support) for every 30 min’s to the maximum

of 2 hrs.

After the responding to the call, the issue or

problem shall resolve within 2 hrs. If the

issue or problem is not resolve SI has to be

onsite within 24 hrs and resolve the issue at

the earliest to complied with the availability

target of 99.5%

As per availability target, 43.8hrs of down

time is acceptable yearly for any Virtual

Software. For any particular software faces

down time beyond 43.8hrs yearly for such

down time penalty will be imposed 0.5% per

hrs of the annually payment (excluding

payment for service support).

Maximum annually penalty related to such

software availability would be 10% of the

annually payment (excluding payment for

service support).



S.

No.

Measurement Service Level

Target

Penalty

3.

Uptime of

Cloud Solution

including the

individual

Cloud Solution

Modules as

specified in the

FRS and are

mentioned

below

99.5%

After reporting of the issue, SI should

respond to the call within 30 min’s, if the SI

fails to respond 0.1% of the annually

payment (excluding payment for service

support) for every 30 min’s to the maximum

of 2 hrs.

After the responding to the call, the issue or

problem shall resolve within 2 hrs. If the

issue or problem is not resolve SI has to be

onsite within 24 hrs and resolve the issue at

the earliest to complied with the availability

target of 99.5%

As per availability target, 43.8hrs of down

time is acceptable yearly for Cloud Solution

Software. If the Cloud Solution Software

faces the down time beyond 43.8hrs yearly,

for such down time penalty will be imposed

0.5% per hrs. of the annually payment

(excluding payment for service support).

Maximum annually penalty related to Cloud

Solution Software availability would be 10%

of the annually payment (excluding payment

for service support).

Note: - For the Components which are in Redundant mode or High Availability Mode or in Cluster, if one of the redundant components goes down and the services required form that particular set of components are still working/ not hampered, than the SI shall be given 24Hrs time to rectify the components, if it is still not rectified within 24Hrs, the SLA as defined above will come into existence. If in between 24hrs the other component goes down, and the entire services required from that components are not available, the penalties as defined in the table above will come into existence from that particular point.



Cloud Services includes the following:

Provisioning and de-provisioning of Virtual Machines

Ensuring Integrity of Infrastructure deployed on Cloud (Preventive measures for safeguarding from unauthorized hackers)

Maintaining the uptime of virtual Machine, which will also include the migration of virtual machine from one physical server to another based on the increased requirement of resources or due to the downtime of physical server

Management and maintenance of Cloud Solution Modules

Performance monitoring and tuning of the OS and Virtual Machines on a periodic basis including, preventive maintenance of the VMs as required.

Add or modify administration and delegation of selected Virtual Machines or Services

7.2.4 Support Service Levels

S. No.

Measurement Service

Level

Target

Penalty

4.

Service support

for the calls

escalated by the

onsite service

support team.

100% of the calls to be resolve within 2 hrs for each call.

Each calls escalated by the onsite support team should be respond within 30 mins. If the SI fail to respond within 30 mins 0.1% of the yearly payment for this purpose for every 30 mins, to the maximum capping of 2 hrs. Penalty will be imposed for all unresolved calls (within target time, 2hrs) as mention below.

Down time beyond 2 hrs target time for each call would be 0.1% per hrs of the yearly payment for this purpose.

Maximum annually penalty related to services support would be 20% of the annually payment for service support.

All the escalated calls reports should be submitted to TSCA for every month by 5th of next month with proper RCA, if SI fails to submit, additional 0.5% of such yearly payment a month.



Service support includes the following: • All the service shall be supported 24x7 • All the escalated calls shall be attended within the specified time period. • Monthly escalation report should be sent or shared to TSCA. If required it should also be

available as and when required by the TSCA including but not limited to: o Type of incidents / calls logged

o Incidents / calls resolved

o Incidents / calls open

• All the calls shall be treated as critical and resolution shall be made available as soon as possible, after the call has been escalated by the onsite support team.

• SI support team shall support online or phone support for any escalated call. • SI team should visit onsite as and when required. • Onsite team shall provide all the required information related to the escalated calls. • Coordinate with respective vendors for closure of calls.



SLA Compliance Review Process • The SI has to submit all the reports pertaining to SLA Review process within 2 weeks after

the end of every half yearly period. • All the reports must be made available to State, as and when the report is generated or as

and when asked by the competent authority.

• SLA may be revised if required with mutually acceptable terms between SI and the TSCA.

7.3 Penalties

• The total deduction should not exceed 20% of the total project cost as discovered through the tender

• Two consecutive yearly deductions of more than 20% of the applicable fee on account of any reasons will be deemed to be an event of default and termination

• It is the right of the State to bring any external resource at any time for SLA review • No Carry forward of any penalties of SLA calculations can be done from any of the

preceding period.

Accuracy of grievance logging by SI The objective is to measure the accuracy with which SI register State user complaints. The complaints that have been captured incorrectly by the Call Center operators of the SI make it difficult to resolve the same. State would like to ensure that no more than 5% of complaints are incorrectly captured. The complaints that are marked with a wrong tag shall be used to calculate the percentage of incorrect complaints lodged by the SI (which would be termed as call not closed).



8. Functional Requirement Specification

8.1 Cloud Enablement General Requirements

S. No. Cloud Enablement Requirements

i. Solution should support cloud services to be delivered on both X86 (Intel, AMD) and RISC/

EPIC based servers as and when required.

ii. The Solution should be capable of allowing applications to self-service compute, network and

storage infrastructures automatically based on workload demand.

iii. The Solution should be capable of decoupling applications and application infrastructure

configurations in portable containers called images

iv.

The tool should provide image library, where Software and server images can be maintained.

Facilities should be there to import new server templates to the library and registering, so as

to use the same for provisioning the new virtual and physical servers.

v. Unified infrastructure management software should provide unified physical and virtual

machine management from single console.

vi. The Solution should be able to isolate and allow secure authenticated access to infrastructure

services

vii. The Solution should be capable of orchestrating compute and storage resource placements

based on flexible policies to maximize hardware utilization.

viii. Infrastructure as a service solution to be offered. It should deliver services using multiple

hypervisors including Unix based hypervisors and physical servers.

ix.

The Solution should be able to abstract compute, network, and storage resources for the

application and user self-service regardless of hypervisor, server, network and storage

hardware.

x.

The Solution should be capable of supporting multi-tenancy to run cloud services (compute,

network, and storage) for multiple consumers on a single platform while dynamically and

automatically managing the isolation of virtual and physical machines into secure pools. This

functionality should be exposed via API

xi. The solution must provide API reference, So as to aid in integrating with third party system.

xii. The Solution should be able to provide workload migration, orchestration, interoperability

between private and public clouds (like auto-scaling, cloud-bursting)

xiii. The Solution must support standards-based REST/SOAP/Equivalent interfaces

xiv. The Solutions should be deployable on a wide variety of open source and proprietary host

Operating Systems

xv. The Solution should support open format

xvi. The solution should also be able to restrict usage of each tenant to defined values, else it

would lead to control over-consumption and under consumption of resources



xvii.

Software console shall provide a single view of all virtual machines, allow Monitoring of

system availability and performance and automated notifications with email alerts. Software

console shall provide reports for performance and utilization of physical servers, Virtual

Machines & hypervisors. It shall co-exist and integrate with leading systems management

vendors.

xviii.

Management software should provide real-time utilization & trend analysis for CPU, Memory,

Network, disk and power (for physical servers only) for physical server and virtual machine. It

should able to integrate 3 blade enclosures.

xix. Software should provide forecast analysis for future workloads based on previous server

(physical or virtual) utilization history.

xx.

Infrastructure management software console shall provide the Manageability of the complete

inventory of virtual machines, and physical servers with greater visibility into object

relationships.

xxi. It should provide seamless migration from physical to virtual, virtual to physical and virtual to

virtual servers.

xxii.

Software should provide ability to create solution templates (solution may includes physical

servers, virtual machine, storage, network, OS etc ) which can be automatically deployed

multiple times based on subscription. A Single template should support multiple

virtualization technologies & physical servers.

xxiii.

It should provide self service portal through which users can subscribe for their suitable

virtual machine / solution template. Users should be able to define for the period for which

they would like to subscribe for the virtual machine / solution.

xxiv. Management software should also include necessary workflow for subscription, approval and

provisioning of solution.

xxv. Management solution should enable to deliver Infrastructure as a service with complete

lifecycle management.

xxvi.

Proposed hardware platform should offer state-less compute nodes & ability to move

workloads among the farm of servers across enclosures offered. Virtual Server profiles should

move across enclosures offered in the blade server section.

xxvii.

Proposed hardware platform should help to reduce datacenter network cables, expensive

network/FC ports, provide better power, cooling & rack space utilization. To reduce network

cables & switch port counts. It should able to integrate and manage virtual MAC and WWN

numbers for better and tight integration prospective.

xxviii. To ensure future-proofing infrastructure & considering future bandwidth requirements,

proposed server blades and enclosures must have a cost effective upgrade path.

xxix. Solution should be capable to allocate bandwidth based on application requirement & to avoid

over provisioning of network resources.



xxx. Solution should have capability to integrate with the network slices/ports mentioned in the

enclosure specification and should able to integrate with variable configurable speeds.

xxxi. The software should have the capability to create virtual machines with required number of

vCPUs.

xxxii.

The cloud solution should tightly integrate with FC and iSCSI SAN Solution provided in the

storage section to leverage high performance shared storage for greater manageability,

flexibility and availability of cloud services.

8.2 FRS for Cloud enablement

Server Virtualization Functional Capabilities Compliance

1 Hypervisor

i.

The Virtualization software should be based on hypervisor technology which

sits directly on top of Hardware (Bare Metal).

The vendor should offer suitable management software.

ii.

The Solution should be able to run various operating systems like windows client, windows server, Linux (at least RedHat, SUSE, Ubuntu, Debian, FreeBSD, Oracle Enterprise Linux & CentOS), solarisx86, Novell NetWare and any other open source.

iii. The Solution should have the capability for creating Virtual Machines

templates to provision new servers

iv.

The Solution should continuously monitor utilization across Virtual Machines

and should intelligently allocate available resources among the Virtual

Machines

v. The Virtualized Machines should be able to boot from iSCSI, FCoE and fiber

channel SAN

vi. The Virtualized Infrastructure should be able to consume Storage across

various protocols like DAS, NAS , SAN. It should support thin provisioning.

vii. The Solution should allow for taking snapshots of the Virtual Machines to be

able to revert back to an older state, if required

viii.

The Solution should be able to dynamically allocate and balance computing

capacity across collections of hardware resources of one physical box

aggregated into one unified resource pool

ix.

The Solution should cater for the fact that if one server fails all the resources

running on that server shall be able to migrate to another set of virtual servers

as available

x. The Solution should provide support for cluster services between Virtual

Machines



xi.

The Solution should provide patch management capabilities such that it should

be able to update patches on its own hypervisor and update guest operating

system through the existing EMS

xii.

The Solution should provide the monitoring, prioritizing and reserving

capabilities for storage, processor, network, memory so as to ensure that the

most important Virtual Machines get adequate resources even in the times of

congestion.

xiii. The Solution should support Live Migration of Virtual Machine from one host

(Physical Server) to another

xiv. The Solution should deliver above listed Hypervisor capabilities using standard

server infrastructure

xv.

The Solution should provide security on the hypervisor, as well as guest VMs. It

should provide the ability to apply security to virtual machines and security

policies that can follow the machines as they move in the cloud.

xvi.

The Solution should provide policy-based configuration management to ensure

compliance across all aspects of the datacenter infrastructure, including virtual

and physical resources.

xvii.

The solution should have the ability to live migrate VM files from one storage

array to another without no VM downtime. Support this migration from one

storage protocol to another (ex. FC, iSCSI, NFS, DAS).

xviii.

The solution should have the ability to manage virtual switches, can span an

entire clusters VM mobility aware & should support features NetFlow and Port

mirror and protocols Link Layer Discovery Protocol (LLDP) and Cisco

Discovery Protocol (CDP).

xix.

The solution should provide network traffic-management controls to allow

flexible partitioning of physical NIC bandwidth between different network-

traffic types and allow user-defined network resource pools, enabling multi-

tenancy deployment, and to bridge virtual and physical infrastructure QoS with

per resource pool 802.1 tagging.

xx.

The solution should provide an integrated back-up solution in addition to

support for a centralized backup proxy to offload backup from virtualization

host.

xxi.

The Management software should have integrated Physical Host and Virtual

Machine performance monitoring including CPU, Memory, Disk, Network,

Power, Storage Adapter, Storage Path, Cluster services, Virtual machine data

stores.



xxii. The management software console shall provide reports for performance and

utilization of Virtual Machines.

xxiii.

The management software console shall provide Interactive topology maps to

visualize the relationships between physical servers, virtual machines,

networks and storage.

xxiv.

The management software should allow reliable and non disruptive migrations

for Physical/ Virtual machines running Windows and Linux operating systems

to virtual environment.

xxv. The management software should generate automated notifications and alerts,

and can trigger automated workflows to remedy and pre-empt problems.

xxvi.

The management software should have provision to capture the blueprint of a

known, validated configuration - including networking, storage and security

settings – and deploy it to many hosts, simplifying setup for automated host

configuration and compliance monitoring.

xxvii.

The solution should include DR functionality management that must be

integrated with the rest of the virtualization management, with functionality to

automate testing and executing of DR plans (to reduce RTOs) without

disrupting production environment.

xxviii. The Solution should also provide solution to address replication between

heterogeneous storage arrays across sites.

xxix.

The Solution should be able to discover and display virtual machines protected

by storage replication using integration adapters certified by storage vendors.

Support for iSCSI, FibreChannel, and NFS-based store replication.

xxx.

The Solution should support Real time visibility and status reports into Step-

By-Step DR execution plans along with Granular controls in the DR workflow

editor. It should Control access to recovery plans with granular role-based

access controls.

xxxi.

The Solution should have the ability to extend recovery plans with custom

scripts like it should be able to reconfigure virtual machines’ IP addresses to

match network configuration at failover site.

2 Compute

i. The Software should have the capability to create Virtual Machines with

required number of vCPUs

ii.

The Solution should allow Virtual Machines consume RAM dynamically in such

a way that if some of the VMs in Physical machine are not utilizing the RAM,

this RAM can be utilized by some other VM in the same physical machine



which has a requirement

iii.

The Solution should be able to use power saving features like, in case of off-

peak hours, if not all servers are required to be powered on, the solution

should shut down to save power

3 Storage

i.

The Solution should also integrate with FC, FCoE and iSCSI SAN and

infrastructure from leading Vendors so as to leverage high performance shared

storage to centralize Virtual Machine file storage for greater manageability,

flexibility and availability

ii. The Proposed Storage Solution should have the ability to thin provision and

thin reclaim disks to avoid allocating all storage space upfront.

iii. The Solution should support migration of the live Virtual Machine files from

one storage array to another storage

iv. The Solution should deliver above listed capabilities using standard storage

infrastructure

4 Network

i.

The Solution should allow configuring each Virtual Machine with one or more

virtual NICs. Each of those network interfaces can have its own IP address and

even its own MAC address

ii. The Solution should allow for creating virtual switches that connect virtual

machines

iii. The Solution should support configurations of 802.1 q VLANs which are

compatible with standard VLAN implementations from other vendors

iv. Solution should take advantage of NIC Teaming Capabilities

v. The Solution should deliver above listed all network capabilities using standard

network infrastructure

vi. The Solution should have the feature for moving Virtual Machines from

Primary site to the Secondary site.

1 Security Capabilities

i. The Solution should offer Automated and Approval based Upgrades for Virtual

and Physical Machines/Servers delivered through cloud infrastructure

ii. The Solution should be able to provide existing Host Firewall protection for the

virtual machine.

iii.

The Solution must offer Identity, Authentication and Role based access to User

Departments Infrastructure - Machines (Virtual or Physical), Application or

Common Services



iv.

The Solution must offer Policy based administration by putting User

Departments Machines (Virtual or Physical) in logical groups and apply

relevant policies.

v. The Solution should have the ability to not just enforce policies but also track

and report non-conformance

vi. The Solution should generate reports on non-conformance and escalation for

privileged access by unauthorized roles/ identities

vii. The Solution should support VLAN isolation by supporting multiple networks

per resource pool

viii. The Solution should support secure communication between cloud framework

and all target systems

ix. The Solution must offer ability to Copy, convert, or migrate an image (P2V,

V2V, V2P).

x.

The Solution must offer ability to utilize existing Intrusion detection System /

Intrusion Protection system to seamlessly extend into Virtualization

environment

1 Service Portal Capabilities

i. The Solution should provide a simple to use intuitive Web portal for SDC Cloud

Administrator and User Departments.

ii. The Solution should have self-service capabilities to allow Users Departments

to log service requests - in SDC

iii.

The Solution should be able to offer choice of various Service offering on

multiple hypervisors (such as XEN/KVM , Hyper-V, VMware) with an option to

select multi operating systems such as Windows 2003, 2008, RHEL / SUSE

Linux, etc., VLAN , Storage and quickly compute associated price for the same

as well as shows the deduction for overall Tenant approved infrastructure

Quota.

iv.

The Solution should offer Service catalog listing availability of Cloud

infrastructure like Virtual Machines, Physical Machines, Applications ,

Common Services offered by State Private cloud. Software console shall

provide a single view of all type of virtual and physical machines for monitoring

of system availability performance and automated notifications with email

alerts.

v.

The Solution should provide comprehensive service catalog with capabilities

for service design and lifecycle management, a web-based self-service portal for

users to order and manage services



vi.

The solution should provide an on-boarding mechanism for the new tenants (

Department) on the cloud infrastructure that automatically creates the tenant,

the tenant administrators, allocates specific resources for the tenant like

storage pools, server pools, S/W packages, network pools (including VLANs,

DNS, IP address spaces, etc...)

vii. The Solution should offer Registration, Signup , Forgot Password and other

standard pages (Profile, Billing or Contact information)

viii. The Solution should enforce password policies and allow to personalize the

look & feel and logo on the user-interface panels

ix.

The Solution should be able to offer choice of various hardware profiles,

custom hardware profile, Selection of operating systems, VLAN, Storage.

Solution should have capability to integrate with the network slices/ports

mentioned in the enclosure specification and should able to integrate with

variable configurable speeds and resources available in the enclosure.

x.

The Solution should automate provisioning of new and changes to existing

infrastructure (Virtual, Physical, Application or Common Services) with

approvals

xi. The Solution should allow creation of library hosting various Operating System

that can be selected while creating new virtual and physical servers

xii.

The Solution should track ownership and utilization of virtual machines,

Physical machines, and common services. Solution should have capability to

allocate bandwidth based on application requirement & to avoid over

provisioning of network resources. .

xiii.

The Solution must provide the capability to support the following Service

Request Types or reasons for contact:

Provisioning of Commuting Infrastructure - Virtual, Physical or OS

xiv.

The Solution should allow for implementing workflows for provisioning,

deployment, decommissioning all virtual and physical assets in the cloud

datacenter

xv.

The Solution should allow easy inventory tracking all the physical & virtual

assets in the Private Cloud. The software solution should provide life-cycle

management for physical and virtual servers

xvi. The Solution should employ Role Level Access Control with the ability to

central manage Roles and Identities in an LDAP based Identity Store

xvii. The Solution should have the ability to manage Virtual Assets across the major

multiple virtualization platforms (Microsoft, VMware, Xen/KVM, UNIX VM)



xix.

The Solution should be able to dynamically allocate and balance computing

capacity across collections of hardware resources aggregated into one unified

resource pool with optional control over movement of virtual machines like

restricting VMs to run on selected physical hosts.

xx.

The Solution should have Show-Back (to check the usage patterns and

reporting for the user department) and the same solution should have the

capability of Charge-Back

xxi.

The Solution should offer usage report by tenant, by region, or by virtual and

by physical server machine reporting usage of memory consumption, CPU

consumption, disk consumption

xxii.

The solution should allow the users to schedule a service creation request in a

future date/time; the solution should check if a request scheduled for a future

time can be fulfilled and reject the request in case of projected resources

shortage or accept the request and reserve the resources for that request,

xxiii. The Solution should have web based interface for administration

xxv. The Solution should have the ability generate customize report as well as the

native ability to export to common formats

xxvi.

Whenever the Charge Back mechanism is enabled, the Solution must satisfy the

following requirements:

• The Solution should support different cost models like allocated or

reserved cost per virtual machine. It should also allow tracking usage of

resources

• The Solution should have the ability to charge differently for different level

of services

• The Solution should support cost calculation of shared/ multi-tenant

application

xxvii.

The Solution should provide service catalog with capabilities for service

offering design and lifecycle management, a self-service portal for users to

order and manage services

2 User Department Requirement

i.

The User Departments should be able to view Department’s infrastructure as

Services e.g. : group his servers by- application servers, All web servers, all DB

servers etc

ii.

The User Departments should be able to select between a managed

infrastructure or an unmanaged infrastructure. (e.g. who will manage the

Patched Updations on virtual and physical machines)



iii. The Solution should allow User Departments to delegate user services to others

on their team

vi. The Solution should allow selecting various Operating System

3 SDC Private Cloud Administrator Requirement

i.

Administrators should be able to automatically scale and/or manage resources

unilaterally for tenant services without manual intervention as and when

required by the SLA requirements of the service

ii. The Cloud Automation framework should provide capability for Roll based

Access for performing specific tasks

iii.

Private Cloud Administrators should be able to easily configure, deploy, and

manage multiple hypervisor and physical infrastructure including x86 and

RISC/EPIC services through a highly intuitive service-centric interface, while

using a library of standard templates

iv.

Private Cloud Administrators should be easily be able to take resources offline

and online. They should have a capability to manage existing servers and

storage of SDC also.

v.

Private Cloud Administrators/Application Owners should be able to create,

manage, services using a web-based interface that presents a customized view

of resources based on your role in the organization

4 Capacity Management

i. The Solution should be able to determine how many more physical and virtual

machines can fit the environment

ii. The Solution should identify idle, underutilized capacity to provide inputs to

the capacity management function such that informed decisions can be taken

iii. The Solution should support to identify and determine optimum sizing and

placement of virtual and physical machines

iv. The Solution should provide forecast reports demonstrating forecasted

utilization of the entire solution

v. The Solution should support all of the following modeling scenarios: Physical

to Virtual, Virtual to Virtual, Virtual to Physical,

vi.

The Solution should provide a mechanism to automatically assess high

volumes of workloads and determines optimal placement on virtual machines

across the enterprise’s shared resource pools. The cloud solution should tightly

integrate with FC SAN Solution provided in the storage section to leverage high

performance shared storage for greater manageability, flexibility and

availability of cloud services. Also it should able to integrate with the offered

storage and virtualization solution offered.



vii.

The Solution should be able to utilize existing investment in tools/

Functionality and extend these to physical and virtual environment as well,

which are available from leading vendors

Automation, Orchestration and Monitoring Compliance

1 Process Automation

i. The Solution should demonstrate a way to comprehensively model cloud datacenter process end to end across multiple Vendors software and hardware thus enforcing Operational Best Practices and Procedures

2 Integration Capabilities

i. The Orchestration Solution should be open and interoperable and has rich integration capabilities that support interfaces from command line interface and web services

ii.

The Solution should provide resource-level operations across compute resources (IBM, Cisco, HP, Dell, Oracle and/or other hardware), hypervisors (VMware, Xen/KVM, Hyper-V), storage resources (EMC, Netapp, IBM,HP,Oracle), and network resources (3Com, Cisco, Juniper). It should support provisioning for multiple platforms including Windows, Linux, & ESX, HyperV on x86 (32 and 64 bit) and UNIX on RISC/EPIC environment.

iv. The Solution should provide capability for orchestrating tasks across systems for consistent, documented, compliant activity

v. The Solution should possess capabilities to extent resource & cloud fabric management onto other Private Clouds or public cloud

vi. The Solution should be able to move identified workloads to another private cloud or public cloud

vii. The Solution should be able to audit and monitor execution of processes and report on violations against the same

viii The various participating HW & SW components in the Data Center process as modeled by the solution should be easily manageable by this Orchestration layer

ix. The Solution should provide a set of adapters that should be able to utilize existing infrastructure elements and IT service management tools to provide smooth, precise orchestration of automated processes

x The Solution should be able to accelerate adequate utilization of subsystems (not limited to but including) the backup solution, the service manager/helpdesk module, the operations modules, the virtual asset provisioning modules etc

3 Monitoring Capabilities

i The Solution should be able to monitor User Department Virtual Resources independent of the platform & solution/service they are running

ii. The Solution should be able to monitor key performance characteristics of the virtual resource (Processes, OS, Memory, Storage, Network etc.)

iii. The Solution should give User Department ability to select performance counters and duration for which they want to view the performance data

iv. The Solution should have the mechanism to store the historical data for problem diagnosis, trend and analysis



v. The Service level dashboard provided with the Solution should have a web based interface

vi. The Solution should be able to send the reports through e-mail and also SMS to predefined user with pre-defined interval

viii. The Solution should be able provide integration with the existing helpdesk system for incidents in SDC

8.3 Specification for Blade Enclosure/Chassis

S. No. Specifications Compliance

i. Single blade Chassis/enclosure should accommodate minimum 12 blade

servers

ii.

Support heterogeneous environment: AMD, Intel CPU blades, RISC/EPIC

blades must be in same chassis with scope to run Windows Server, Red Hat

Linux, Suse Linux / 64 Bit UNIX or other standard open source OS.

iii. Chassis should have a highly reliable mid plane for providing connectivity of the shared resources to the compute nodes in a highly reliable manner.

iv.

Each enclosure should be configured with redundant Ethernet modules with

10Gbps downlink ports and 4 no. 10 Gbps and 2 no. 1 Gbps uplink ports per

module, up-linkable to the data centre switch. Shall be capable of supporting

up to 4 physical slices per 10Gbps server communication port, within the

server Blade. Each of the tailoring slices shall be capable of tailoring the

network with their own dedicated, customized bandwidth per 10Gbps

downlink connection, with customizable speeds from 100Mbps to 10Gbps

v.

The Blade enclosure should be configured with redundant fiber channel

module which should support downlink ports to all the blades and 6 No of 8

Gbps uplink ports to consolidate the FC uplinks to upstream SAN switches.

This module should also provide virtual WWN to the servers in order to

assign the servers rapidly.

vi. Hot swap and redundant cooling unit and all fans should be fully populated.

vii. The blade chassis should have at least 8 I/O Modules.

viii.

The enclosure should be populated fully with power supplies of the highest

capacity available with the vendor. Power supplies should support N+N as

well as N+1 redundancy configuration, where N is greater than 1

ix.

Power Management Features like ;

• To cap the power of individual server or a group.

• Intelligently assign power to the appropriate server in the pool based




on policy settings.

• To generate comprehensive power reports.

• To show the actual power usage and thermal measurements data of

servers.

x.

The blade chassis should be configured with cables, connectors and

accessories required to connect the Power distribution units to the power

supplies.

xi. Should support Hot Pluggable & fully Redundant Management Modules.

xii.

The blade chassis should be configured with Hot swap IP based KVM Switch

for Management or KVM Management should be integrated in Remote

Management Controller

xiii. Should support combination housing of Ethernet, FC, IB interconnect fabrics

offering Hot Pluggable & Redundancy as feature.

xiv. Warranty 5 years 24x7 support directly from the OEM.

xv.

Must have the ability to map the remote media to the server. Also must have the ability to transfer files from the user’s desktop/laptop folders to the remote server with only the network connectivity. Must have the capability of capturing and deploying OS images.

xvi. Must have the ability to automatically trigger events and alerts based on performance issues or thresholds set.



8.4 Specification for Blade Server


i. The make of Blade server should match the enclosure specification.

ii.

Minimum 2 processor with 8 Cores & minimum 2.4 GHz with min 16MB L3

cache per processor

iii. Memory (RAM): Min. 128 GB scalable to 256 GB

iv.

64bit OS support: Virtualization Software / Microsoft® Windows Server

Data Centre Edition / Red Hat® Enterprise Linux 5 & 4 AS / SUSE® Linux

Enterprise Server 9 /Unix or other standard open source OS.

v.

Processor should be latest series/generation for the server model being

quoted

vi. RAID controller with RAID 0, 1.

vii. HDD: 2 x 400 GB SSD hot swappable system disk.

viii.

2 x 10GbE network ports with support for iSCSI/FCoE protocols based on

future datacenter needs. Each 10 GbE should be able to partition as

minimum 4 partitions.

Should be Supplied with 1 No of FC HBA card with Dual Port 8Gbps Fiber

Channel.

In addition to the above dedicated Remote Management should be done/

All the blades in the chassis should be remotely managed through Chassis.

ix.

Minimum of 2 PCI expansions/Mezzanine expansions.

Bus slots should support for Dual/Quad Gigabit, Dual 10Gbps and Dual

port 4x QDR Infiniband options for increased bandwidth and additional

network port requirements.

x.

Security: Power-on password / admin password / unattended boot /

selectable boot

xi.

The server should come with systems management software to provide

update management, configuration management, patch management and

virtualization management. The software should be able to Cap data based

on the report.

xii.

All the necessary tools & tackles, cables/ connectors for Ethernet/

Fibre/USB/ Power etc. required for making the system operational shall be

provided by the bidder.

xiii. Server is certified with FCC and CE compliance specifications.



8.5 Specification for SAN Storage


i. Rack Mountable, Mountable in standard rack

ii.

SAN Controller should be True Enterprise Class Storage system as per Industry standards and should be configured in NO Single point of failure including Array Controllers card, Cache Memory, FAN, Power Supply etc. and complying with below mentioned Enterprise class specifications.

iii.

The Storage system should be configured with at least 32 GB of usable Cache or Higher and should support scalability up to minimum 64 GB usable Cache. Only write cache is to be mirrored and cache should be managed dynamically between read and write operations. The cache should be DRAM based or equivalent technology and should be usable cache.

iv. Minimum 8 x 8 Gbps Fiber Channel host ports and it should be scalable to at least 24 FC host ports. 2 x 1 Gbps iSCSI Host interface scalable to 10 Gbps.

v.

The enterprise storage should have highly reliable and performance efficient drives connectivity and should offer minimum 16 numbers of 6Gbps or 8Gbps backend ports/lanes. The same should be scalable to 24 Number of 6Gbps or 8Gbps backend ports/lanes

vi. RAID levels should support 0, 0+1, 1, 5 and 6.

vii.

The Storage array should support intermix disk capacity 900GB or higher SFF/LFF SAS/SATA/FC drives on RAID 5. Should be able to create large size LUNs. Minimum One hot spare to be configured for every 30 spindles for each type of disk configured in the proposed storage system. The storage system should be scalable up to 400 drives with different drive combinations. The storage should be offered with thin provisioning and thin reclaim feature and the storage should be tightly integrated with the cloud.

viii. The Storage system should be 40TB Usable with RAID 5.

ix.

The Storage system should have the storage based data replication and it should support for incremental replication over SAN and WAN for proposed storage systems. It should be possible to implement a 3-way DR solution using the proposed storages for achieving zero data loss.

x.

Management software should be configured to manage the proposed SAN storage system from a common screen for all activities like RAID creation, LUN creation, Presentation, Snapshot, replication, etc. This S/W should find the root cause and diagnose the problem.

xi. The storage array should have synchronous and asynchronous replication simultaneously for the LUNs on the proposed SAN and storage Sub systems leveraging the enterprise class capabilities.

xii. The storage array must have complete cache protection mechanism either by destaging data to disk/flash or providing complete cache data protection with battery backup for up-to 72 hours or more.




xiii. The storage array should support virtualization for zero disk layout can be used with thin provisioning and thin re-claim.

xiv. The storage array should offer native IP based replication, if the Storage array requires FCIP routers, the same should be offered in High availability configuration.

xv. The storage array should support Operating System Platforms & Clustering including: Windows Server (Enterprise Edition), Sun Solaris, Linux, VMware, Hyper V, HP-UX and IBM-AIX.

xvi. Storage should support non-disruptive online firmware upgrade for Controllers and disk drives.

xvii. The storage should provide automatic rerouting of I/O traffic from the host in case of primary path failure.

xviii. Should support hot-swappable physical drive RAID array expansion with the addition of extra hard disks.

xix. Should be able to support clustered and individual servers at the same time.

xx. Should support hardware based data replication at the array controller level across all standard models with the proposed model.

xxi. Vendor should also configure required software to offer common interface for storage performance monitoring and management for proposed SAN storage system

xxii. Should have “snapshots” of the stored data to other logical drive for backup purposes and license to be provided for proposed capacity.

xxiii. The Storage should support authentication security control, by user and role in order to avoid unauthorized service access.

xxiv. Warranty 5 years 24x7 support directly from the OEM.

xxv. The bidder has to provide the complete part number wise Bill of Material which will be cross verified with the OEM.

xxvi. Should provision for LUN masking, fibre zoning and SAN security.



8.6 Specification for SAN Switch (for connectivity with SAN Storage)


i. Rack Mountable in standard rack

ii. SAN Switch solution should be highly available with no single point of

failure.

iii.

Switch shall support minimum 32 ports x 4Gbps FC ports or higher with

all port licenses. Additional 4 uplink ports of 8 Gbps FC ports should be

provided. It should be upgradeable to 72 FC ports in the same chassis.

iv.

The SAN switch should have capability to interface with HBA of different

makes and model from multiple OEM, supporting multiple Operating

Systems, including, but not limited to HP-UX, IBM AIX, Linux, MS-

Window, Sun Solaris etc. The SAN switch should support all leading SAN

disk array and tape libraries including, but not limited to, EMC, Hitachi,

HP, IBM, Sun, NetApp etc.

v. Management S/W to provide topology view of switches, HBA Cards,

Storage and SAN Fabric should be offered.

vi. Support for web based management and configuration for remote

administration

vii. Switch should have dual hot swappable power supply.

viii. Switch should support non-disruptive Micro code/Firmware upgrade

ix. All required accessories and cables, etc. as applicable to meet the above

specification and hence the proposed solution.

x. Should support proactive fault detection and alerting capability to avoid any hotspots in the fabric.

xi. Switch shall support diagnostics features such as port mirroring, Syslog, Online system health, Port-level statistics etc

xii.

Should support features such as Quality of Service (QoS) to help optimize application performance in consolidated, virtual environments. It should be possible to define high, medium and low priority QOS settings to expedite high priority traffic.

xiii. Should support Port security and Port Zoning. It should support NP-IV. Should support Secure Shell (SSH) (SSL) and encryptions.



9. Bill of Materials

The Bidder shall procure the material and equipment with integration and passive components requirement based on the table 1 and table 2 for the Cloud Enablement of Tripura State Data Centre. Any component which is required and is not specified in the given table should be specified in the table given in the Section XIII - Commercial Bid as Other Components.

Table: 1

S. No. Components Quantity

1. Cloud Management Software with all required modules (for 3 enclosure)

as defined in FRS and SOW. 1

2. Blade Chassis /Enclosure 1

3. Blade Server 4

4. Linux Enterprise Edition (Latest Version) Operating System 1

5. Windows Server Data Centre Edition (Latest version) Operating System 1

6. Virtualization S/W (hypervisor) for Servers (2 Hypervisor for each

Server) with licenses 8

7. Cisco MDS 9134 8-Port 4Gb Port Activation Upgrade License (for

existing SAN switch) 2

Table: 2

S. No. Components Quantity 8. Blade Server 8

9. Additional licenses for Virtualization S/W (hypervisor) for Servers 16

10. SAN Storage Box 1

11. SAN Switch for connectivity to the SAN Storage 2

12. Cisco MDS 9124e 12-port Upgrade LTU for existing HP blade system +

4 SFP and 4 cables for connectivity 4

13. HP Virtual Connect Flex-10/10D Module for existing HP BladeSystem

(With 10 No of 1 Gig external ports) 4

14. HP Virtual Connect 8Gb 24-Port Fibre Channel Module for existing HP

BladeSystem (With 8 No of 8 Gig FC Ports) 4

15. HP LTO4 Ultrium 1.6TB read/write Data Cartridge (C7974A) including

tape label 100

16. MS Office 2013Home Edition 2

Please note that all components/Licenses purchase shall be with the name of TSCA from the day one.



There should not be any hidden costs on Licensing/ Feature addition-Enablement / Integration with other existing SDC Components. Hence, it shall recommend obtaining perpetual/unlimited License for all solutions supplied by Bidder. This will eliminate the need for buying additional licenses as and when hardware up gradation or VM up gradation is carried out in the future. All equipment procured for the cloud solution should have OEM support for at least 5 years from the date of installation.



10. Annexure

Annexure I: SI Profile RFP No: F. 7(3)/TSCA/SDC/2013 Name of the Project: Cloud Enablement of Tripura State Data Centre (TSDC)

1. Name of the Firm 2. Registered Office address

Telephone Number Fax Number e-mail

3. Correspondence/ contact address 4. Details of Contact person

(Name, designation, address etc.) Telephone Number Fax Number e-mail

5. Is the firm a registered company? If yes, submit documentary proof.

Year and Place of the establishment of the company

6. Former name of the company, if any. 7. Is the firm

a Government/ Public Sector Undertaking? a propriety firm?

a partnership firm (if yes, give partnership deed)? a limited company or limited corporation? a member of a group of companies (if yes, give name and address, and description of other companies)?

a subsidiary of a large corporation (if yes give the name and address of the parent organisation) If the company is subsidiary, state what involvement if any, will the parent company have in the project.?

8. Is the firm registered with sales tax department? If yes, submit valid sales tax registration certificate.

9. Is the firm registered for service tax with Central Excise Department (Service Tax Cell)? If yes, submit valid service tax registration certificate.

10. Is the firm registered under Labour Laws Contract Act? If yes, submit valid registration certificate.

11. Attach the organizational chart showing the structure of the organization including the names of the directors and the position of the officers. Total number of employees

12. Number of years of experience:



13. Are you registered with any Government/ Department/ Public Sector Undertaking (if yes, give details)

14. How many years has your organization been in business under your present name? What were your fields when you established your organization? When did you add new fields (if any)?

15. What type best describes your firm? (documentary proof to be submitted)

• Manufacturer • Supplier • System Integrator • Consultant • IA (pl. specify details) • Software Developer • Total solution provider (design, supply, integration,

O&M) • IT Company

16. Number of Offices / Project Locations 17. Do you have a local representation /office in Agartala? If

so, please give the address and the details of staff, infrastructure etc in the office and no. of years of operation of the local office

18. Please give details of key technical and administrative staff who will be involved in this project, their role in the project, their qualifications & experience and the certification attained from network product SI. (documentary proof to be submitted)

19. Does your organization have ISO 9001 and ISO 27001 certificates? If so, attach copies of the certificates. State details, if certified by bodies, other than that stated.

20. List the major clients with whom your organization has been/ is currently associated.

21. Were you ever required to suspend a project for a period of more than three months continuously after you started? If so, give the names of project and reasons for the same.

22. Have you in any capacity not completed any work awarded to you? (If so, give the name of project and reason for not completing the work)

23. In how many projects you were imposed penalties for delay? Please give details.

24. The SI shall disclose details pertaining to all contingent liabilities, claims, disputes, matters in appeal & in court and any pending litigation against the SI .If nil, an undertaking from the SI mentioning the same.

25. Whether your organisation has Bank’s certificate of solvency. If yes, submit documentary proof.

26. Have you ever been denied tendering facilities by any Government/ Department/ Public sector Undertaking? (Give details)



Annexure II: SI’s Experience

S. No. Item Details

General Information

1 Customer Name/ Government Department

2 Name of the Contact Person and Contact details for the project

Brief Description of scope of Project

Size of the project

3 Contract Value of the project (in crores)

4 Capital Expenditure involved (by the govt./ client)

5 Total cost of the services provided (by the Bidder)

Project Details 6 Name of the project

7 Start Date/End Date

8 Current Status (work in progress, completed)

9 Contract Tenure

10 Type of Project

11 Solution architecture employed & core Components

12 Scope of Service Delivery System

13 Tools Deployment



Annexure III: Format for Financial Information RFP No.F. 7(3)/TSCA/SDC/2013 Name of the Project: Cloud Enablement of TSDC

Turn Over (Rs Crore) Name of the

SI

09-10 10-11 11-12

Note:

1. Submit the audited financial statement/ audited annual report of the last three (above mentioned) financial years.



Annexure IV: Format for Performance Bank Guarantee (To be stamped in accordance with Stamp Act) Ref: Bank Guarantee No. Date: To Member Secretary, Tripura State Computerization Agency ITI Road, Indranagar; Agartala Dear Sir, WHEREAS ........................... (Name of SI) hereinafter called "the SI" has undertaken, in pursuance of Contract dated ... 2013 (hereinafter referred to as “the Contract") to implement the Cloud Enablement of TSDC for the Tripura State Computerization Agency (TSCA), Government of Tripura ("GoT"). AND WHEREAS it has been stipulated in the said Contract that the SI shall furnish a Bank Guarantee ("the Guarantee") from a Nationalized bank for the project/performance of the Cloud Enablement of TSDC as per the agreement WHEREAS we ("the Bank", which expression shall be deemed to include it successors and permitted assigns) have agreed to give the Tripura State Computerization Agency (TSCA), Government of Tripura ("GoT") the Guarantee: THEREFORE the Bank hereby agrees and affirms as follows:

1. The Bank hereby irrevocably and unconditionally guarantees the payment of Rs.___________ (being 10% of the sum of order value) to TSCA, GoT under the terms of their Agreement dated ____ on account of full or partial non-performance / non- implementation and/ or delayed and/ or defective performance / implementation. Provided, however, that the maximum liability of the Bank towards TSCA, GoT under this Guarantee shall not, under any circumstances, exceed in aggregate.

2. In pursuance of this Guarantee, the Bank shall, immediately upon the receipt of a written notice from TSCA, GoT stating full or partial non-implementation and/ or delayed and or defective implementation, which shall not be called in question, in that behalf and without delay/demur or set off, pay to TSCA, GoT any and all sums demanded by TSCA, GoT under the said demand notice, subject to the maximum limits specified in Clause 1 above. A notice from TSCA, GoT to the Bank shall be sent by Registered Post (Acknowledgement Due) at the following address: Attention Mr………………………. .

3. This Guarantee shall come into effect immediately upon execution and shall remain in force for a period of 12 months from the date of its execution. However, the Guarantee shall, not less than 30 days, prior to its expiry, be extended by the Bank for a further period of 12 months. The Bank shall extend the Guarantee annually in the manner herein before provided for a period of four years from the date of issue of this Guarantee.

4. The liability of the Bank under the terms of this Guarantee shall not, in any manner whatsoever, be modified, discharged, or otherwise affected by:



a. any change or amendment to the terms and conditions of the Contract or the execution of any further Agreements.

b. any breach or non-compliance by the SI with any of the terms and conditions of any Agreements/credit arrangement, present or future, between SI and the Bank.

5. The BANK also agrees that TSCA, GoT at its option shall be entitled to enforce this Guarantee against the Bank as a Principal Debtor, in the first instance without proceeding against SI and not withstanding any security or other guarantee that TSCA, GoT may have in relation to the SI’s liabilities.

6. The BANK shall not be released of its obligations under these presents by reason of any act of omission or commission on the part of TSCA, GoT or any other indulgence shown by TSCA, GoT or by any other matter or thing whatsoever which under law would, but for this provision, have the effect of relieving the BANK.

7. This Guarantee shall be governed by the laws of India and only the courts of Agartala, Tripura shall have exclusive jurisdiction in the adjudication of any dispute which may arise hereunder.

Dated this the ………………. Day of ……………………..2012 Witness (Signature) (Signature) (Name) (Name) Bank Rubber Stamp (Official Address) Designation with Bank Stamp Plus Attorney as per Power of Attorney No. Dated:



Annexure V: Format for Providing Citations Sl. No.

Item

Guidelines

Attachment Ref.No. for details

1. Name of the Project

2.

Client Details

Name; Contact person’s Name & No.

3.

Domain/Sector

Please specify the domain such as which department etc.

4.

No. of Locations

Please Specify Number of locations for implementation

5.

Scope of Work

Provide Scope of Work; highlight Key Result Areas expected and achieved

6.

Contract Value

Provide particulars on Contract Value assigned to each major phase and milestone

7.

Complete Project Duration

Provide particulars on the total time taken for the completion of project including time details on various activities

The Citations should be given in the above format. A separate copy of this format should be used for each citation.



Annexure VI: Format for Queries SI’s requiring specific points of clarification may communicate with TSCA, GoT during the specific period using the following format. RFP No.F. 7(3)/TSCA/SDC/2013 Name of Project: Cloud Enablement of TSDC Name of the SI- Contact Address of the SI-

Sl No. Section No. Page No Query

Signature: Name of the Authorized signatory: Company seal: Note: All the queries should be sent in this format to: [email protected]. No other format is acceptable apart from this format.



Annexure VII: Technical Bid letter To, Member Secretary Tripura State Computerisation Agency ITI Road, Indranagar Agartala – 799006, Tripura

Sir,

Subject: Appointment of an Agency for Supply, Installation, Commissioning, Training and Testing and Maintenance services for Cloud Enablement components for Tripura State Data Centre

Reference: Tender No: F.7(3)/TSCA/SDC/2013 Dated <dd/mm/yyyy>

We, the undersigned Bidders, having read and examined in detail all the Tender documents do hereby propose to provide the services as specified in the Tender document number F. 7(3)/TSCA/SDC/2013 Dated <dd/mm/yyyy> along with the following:

1. Earnest Money Deposit (EMD)

We have provided an EMD of Rs. 10, 00, 000/- (Rupees ten Lacs only) along with this bid response. This EMD is liable to be forfeited in accordance with the provisions of - General Conditions of the Contract.

2. Deviations

We declare that all the services shall be performed strictly in accordance with the Tender documents except for the variations, assumptions and deviations, all of which have been detailed out exhaustively in the following statements, irrespective of whatever has been stated to the contrary anywhere else in our Tender:

• Statement of Deviations from Tender Terms and Conditions is as specified in General Terms and Conditions

Further we agree that additional conditions or assumptions, if any, found in the Tender documents other than those stated in deviation schedule shall not be given effect to.

3. Contract Performance Guarantee Bond

We hereby declare that in case the contract is awarded to us, we shall submit the Contract Performance Guarantee Bond in the form prescribed in the RFP.



4. Bid Validity Period

We agree to abide by this Bid for a period of 180 days after the date fixed for Bid opening or for any further period for which Bid validity has been extended and it shall remain binding upon us and Bid may be accepted at any time before the expiration of that period.

We hereby declare that our Bid is made in good faith, without collusion or fraud and the information contained in the Bid is true and correct to the best of our knowledge and belief.

We understand that our Bid is binding on us and that you are not bound to accept a Bid you receive.

Thanking you,

Yours faithfully,

(Signature of the Bidder)

Printed Name

Designation

Seal

Date:

Business Address: N.B: This letter should be scanned (PDF format) at a resolution of 150 dps and uploaded in the specific folder mentioned.



Annexure VIII: Technical Evaluation Criteria

Sl No.

Criteria/Sub Criteria

Description

Point System

Max Criteria/ Sub Criteria Points

Section No. and Page No. in the IAs Proposal/ Reference (schedule tobe filled)

1

Past Experience of the SI

30

a.

Experience of working in DC Projects in India

Bidder’s experience in setting-up IT infrastructure in Data Centres in India, quantified in terms of number of projects will be evaluated. Setting-up IT infrastructure in Data Centres would mean where the Bidder has procured, installed and commissioned IT Infrastructure (Hardware and Software) in Data centre. Only Project Cost greater than Rs. 5 Cr and set up as per the contract in the last 3 financial years will be considered.

>=5 Projects = 10 points; 4 Projects = 8 points; 3 Projects = 6 points; 2 Projects = 4 points; 1 Project = 2 points ; else 0

10

Schedule A

b.

Experience in commissioning Cloud Solution in DC in India

Bidder’s experience in commissioning Cloud Solution in India, quantified in terms of number of projects will be evaluated. Setting-up IT infrastructure would mean where the Bidder has procured, installed and commissioned Cloud Infrastructure (Hardware and Software). Only Project Cost greater than Rs. 2 Cr and set up as per the contract in the last 3 financial years will be considered.

>=5 Projects = 10 points; 4 Projects = 8 points; 3 Projects = 6 points; 2 Projects = 4 points; 1 Project = 2 points; else 0

10 Schedule B

c. Experience of working with Government for

All completed ICT infrastructure project

>=5 Projects = 10 points; 4 Projects = 8 points;



Sl No.


Description

Point System



any sort of ICT infrastructure project in India

for Govt. (each having a minimum value of 2 crore) for the last three years to be looked at

3 Projects = 6 points; 2 Projects = 4 points; 1 Project = 2 points; else 0

10 Schedule C

2 Financial Strength of the SI 10

a.

Turnover figure for Last three Years

Average Turnover of theBidder from IndianOperations for the lastthree financial year ending31st March 2012

Qualifying turnover should beat least Rs.200 crores > Rs 300 Cr = 10 > Rs 200 Cr ≤ Rs 300 Cr = 5

10

Schedule D

3 Technical Solution , Specification, Technical presentation for the Solution by the SI

40

a.

For each BOM component as specified, the Bidder will provide the compliance status, value addition provided and impact of value addition (considered as positive impact). If there is no positive value addition the Bidder would get 70% of the marks attributed to that component. (Note: The overall marks shall be restricted to the maximum allowed under that component head irrespective of the positive impact)

20

Schedule E

b.

Proposed approach and Methodology

Description of the overall implementation methodology for implementing the Solution

Evaluation Committee will evaluate whether the implementation methodology is in line with the requirement. The important parameters being:- Server Virtualization, Cloud Enablement, Security Mechanism, Plan for meeting the SLA, etc.

5



Sl No.


Description

Point System



c. Technical Specification

Comparison between Technical Specification and offered Specification

1 marks to be reduced for each deviation

5

d.

Technical Presentation

Technical presentation to be looked into

The SI’s clarity of the total scope of work, approach and methodology, the solution and network architecture etc. Weightage of the technical presentation shall be on the following:- Proposed solution and its compliance with RFP SOW, Deployment plan , Architecture, Clarifications to the queries raised by the Technical Evaluation Committee

10

4 Resource a. The Bidder must have on its roll at least 20 Technically qualified professionals in virtualization, cloud implementation, as on Bid submission date.

> 20 = 5; 15 - 20 =3; 10 - 15 = 2; <10 =1;

5

Manpower at TSDC to be deployed b. The Resources deployed

by the SI for CloudEnablement Implementation at theTSDC

2 Resources with OEMcertification for VirtualizationImplementation= 2.5 2 Resources with OEMcertification for CloudImplementation= 2.5 (The OEM certification should be from that OEM whose product has been quoted in this Bid)

5

5 Certifications 10

a. ISO 20000 Valid 20000 certification to be looked at

ISO 20000 = 5 marks Else = 0

5

b. ISO 27001 Valid 27001 certification to be looked at

ISO 27001 = 5 marks Else = 0

5

Total Points 100



Schedule A- Bidders Experience in setting-up IT infrastructure in Data Centres

Criteria

S. No.

Name of Client

Project Cost

Year of Execution

Details of testimonial attached

1 2 3 4

Bidder’s experience in setting-up IT infrastructure in Data Centres in India, quantified in terms of number of projects will be evaluated. Setting-up IT infrastructure in Data Centres would mean where the Bidder has procured, installed and commissioned IT Infrastructure (Hardware and Software) in Data centre. Only Project Cost greater than Rs. 5 Cr and set up as per the contract in the last 3 financial years will be considered. >=5 Projects = 10 points; 4 Projects = 8 points; 3 Projects = 6 points; 2 Projects = 4 points; 1 Project = 2 points; else 0

5

Note: Testimonials would include Copy of work order/ Contract / Client certificate Schedule B- Bidders Experience In Cloud Solution

Criteria

S. No.

Name of Client

Project Cost

Year of Execution


1 2 3 4

Bidder’s experience in commissioning Cloud Solution in India, quantified in terms of number of projects will be evaluated. Setting-up IT infrastructure would mean where the Bidder has procured, installed and commissioned Cloud Infrastructure (Hardware and Software). Only Project Cost greater than Rs. 2 Cr and set up as per the contract in the last 3 financial years will be considered. >=5 Projects = 10 points; 4 Projects = 8 points; 3 Projects = 6 points; 2 Projects = 4 points; 1 Project = 2 points; else 0

5

Note: Testimonials would include Copy of work order/ Contract / Client certificate



Schedule C- Experience of working with Government for any sort of ICT infrastructure project in India

Criteria

S. No.

Name of Client

Project Cost

Year of Execution


1 2 3 4

All completed ICT infrastructure project for Govt. (with each having a minimum value of 2 crore) for the last three years to be looked at. >=5 Projects = 10 points; 4 Projects = 8 points; 3 Projects = 6 points; 2 Projects = 4 points; 1 Project = 2 points; else 0

5

Note: Testimonials would include Copy of work order/ Contract / Client certificate Schedule D- Average Turnover

Criteria

Turnover for the Financial year 2011 – 2012

Turnover for the Financial year 2010– 2011

Turnover for the Financial year 2009 – 2010

Average Turnover (Rs.)

Indicate the page number where balance sheets are provided

Average Turnover of the Bidder from Indian Operations for the last three financial year ending 31st March 2012. Qualifying turnover should be at least Rs.200 crores > Rs 300 Cr = 10 > Rs 200 Cr ≤ Rs 300 Cr = 5



Schedule E- Specification Compliance

Specification

Total Marks

Compliance with RFP specifications (Yes/No)

Value addition provided (Yes/No)

Impact of value addition on (Performance /Scalability/ Availability)

Final Score

Components 70% of Total Marks 30% of Total Marks Positive Impact Total 20 Marks

70% of Total Marks

30% of Total Marks

Positive Impact

Final Marks

Server Virtualization 3 Cloud enablement including: - Self Service Provisioning, Catalog, Directory Maintenance, Automation, Orchestration, Common Resource Pool, Service provisioning & Service Delivery, Capacity Planning and Management, Optimization, Life cycle management, Monitoring & Reporting solution, Migration of VMs within and across enclosure.

5

Security provisioning 3 Blade Enclosure 3 Blade Server 3 SAN System 3



Annexure IX: Statement of Deviation from Technical Specification To Member Secretary, Tripura State Computerization Agency ITI Road, Indranagar; Agartala Reference. RFP No.F. 7(3)/TSCA/SDC/2013 Dated………………. Dear Sir, Following are the deviations and variations from the Technical Specifications of tendered items. These deviations and variations are exhaustive. Except these deviations and variations, the entire work shall be performed as per your specifications and documents.

Sl. No.

Section No. & Page No.

Deviation in the Bid

Brief Reason

1.

2.

3.



Annexure X: Format of Curriculum Vitae for Proposed Manpower (Use the Format given below for each individual) Sl.No. Category Details

1. Proposed Position

2. Name

3 Current Designation

4

Educational Background/ Training/ Certifications

5. Tasks proposed to be assigned

6. Areas of Expertise

7.

Summary of Professional/ Domain Experience

8.

Period of Association with the organization

9.

Number and Details of relevant project experience

10. Any other Information



Annexure XI: Un-Priced Bills of Materials Sl. No.

Item Description Item Code Make Model Quantity/No. of years for

AMC

1 2 3 4 5 6 1 Cloud Management

Software with all required modules as defined in FRS and SOW • Virtual Machine Management • Security Capabilities • Self Service Provisioning • Process Automation • Capacity Management • Orchestration • Monitoring • Migration of VMs within and across enclosures • Etc (for 3 enclosure) (The cost of the solution should also include required hardware, Software, Licenses that are required to make the solution fully functional)

item1

2 Support and subscription for Cloud Management Software

item2

3 Blade Chassis /Enclosure item3 4 AMC for Blade Chassis

/Enclosure item4

5 Blade Server item5 6 AMC for Blade Server item6 7 Linux Enterprise Edition

(Latest Version) Operating System

item7

8 Support & Subscription for Linux Enterprise Edition

item8

9 Windows Server Data Centre Edition (Latest version) Operating System

item9

10 Support & Subscription item10



Sl. No.


AMC

Windows Server Data Centre Edition

11 Virtualization S/W (hypervisor) for Servers (2 Hypervisor for each Server) with licenses

item11

12 Support & Subscription for Virtualization S/W (hypervisor)

item12

13 Cisco MDS 9134 8-Port 4Gb Port Activation Upgrade License (for existing SAN switch)

item13

14 SAN Storage Box item14 15 AMC for SAN Storage Box item15 16 SAN Switch for

connectivity to the SAN Storage

Item16

17 AMC SAN Switch Item17 18 Cisco MDS 9124e 12-port

Upgrade LTU for existing HP blade system + 4 SFP and 4 cables for connectivity

Item18

19 HP Virtual Connect Flex-10/10D Module for existing HP Blade System (With 10 No of 1 Gig external ports)

Item19

20 AMC for HP Virtual Connect Flex-10/10D Module

item20

21 HP Virtual Connect 8Gb 24-Port Fibre Channel Module for existing HP BladeSystem (With 8 No of 8 Gig FC Ports)

item21

22 AMC for AMC for HP Virtual Connect 8Gb 24-Port Fibre Channel Module

item22



Sl. No.


AMC

23 HP LTO4 Ultrium 1.6TB read/write Data Cartridge (C7974A) including tape label

item23

24 MS Office 2013Home Edition

item24

25 Cloud enablement of TSDC infrastructure, with the help of equipments, HW, SW, etc supplied, installed, configured under the SOW of this RFP

item25

26 Training Cost Item26 27 Onsite operating and

maintaining the cloud solution for a period of 2 months from O&M start date

Item27

28 Service support for the calls escalated by the onsite TSCA service support team.

Item28

29 Any other item proposed Item29 30 Any other item proposed item30 31 Any other item proposed item31 32 Any other item proposed item32 33 Any other item proposed item33 34 Any other item proposed item34

N.B: Please don’t change the item code as it will be referred with the Commercial bid



Annexure XII: Commercial Bid Letter To, Member Secretary Tripura State Computerisation Agency ITI Road, Indranagar Agartala – 799006, Tripura

Sir,

Subject: Appointment of an Agency for Supply, Installation, Commissioning, Training and Testing and Maintenance services for Cloud Enablement components for Tripura State Data Centre

Reference: Tender No: F. 7(3)/TSCA/SDC/2013 Dated <dd/mm/yyyy>

We, the undersigned Bidder, having read and examined in detail all the Tender documents in respect of Appointment of an Agency for Supply, Installation, Commissioning, Training and Testing and Maintenance services for Cloud Enablement components for Tripura State Data Centre do hereby propose to provide services as specified in the Tender documents number F. 7(3)/TSCA/SDC/2013 Dated <dd/mm/yyyy> 1. Price And Validity • All the prices mentioned in our Tender are in accordance with the terms as specified in the

Tender documents. All the prices and other terms and conditions of this Tender are valid for a period of 180 calendar days from the date of opening of the Tenders.

• We hereby confirm that our Tender prices include all taxes. However, all the taxes are quoted separately under relevant sections.

• We have studied the clause relating to Indian Income Tax and hereby declare that if any income tax, surcharge on Income Tax, Professional and any other corporate Tax in altercated under the law, we shall pay the same in accordance with clause 3.10 Taxes and Duties of this RFP.

2. Unit Rates We have indicated in the relevant schedules enclosed the unit rates for the purpose of on account of payment as well as for price adjustment in case of any increase to / decrease from the scope of work under the contract. 3. Deviations We declare that all the services shall be performed strictly in accordance with the Tender documents except for the variations and deviations, all of which have been detailed out exhaustively in the following statement, irrespective of whatever has been stated to the contrary anywhere else in our Bid.



Further we agree that additional conditions, if any, found in the Tender documents, other than those stated in deviation schedule, shall not be given effect to. 4. Tender Pricing We further confirm that the prices stated in our Bid are in accordance with your Instruction to Bidders included in Tender documents. 5. Qualifying Data We confirm having submitted the information as required by you in your Instruction to Bidders. In case you require any other further information/documentary proof in this regard before evaluation of our Tender, we agree to furnish the same in time to your satisfaction. 6. Bid Price We declare that our Bid Price is for the entire scope of the work as specified in the Schedule of Requirements and Tender documents. These prices are indicated in Format 2 of Section XIII attached with our Tender as part of the Tender. 7. Contract Performance Guarantee Bond We hereby declare that in case the contract is awarded to us, we shall submit the Contract Performance Guarantee Bond in the form prescribed in Section XIII, Annexure II- Proforma and as per General Conditions of Contract. We hereby declare that our Tender is made in good faith, without collusion or fraud and the information contained in the Tender is true and correct to the best of our knowledge and belief. We understand that our Tender is binding on us and that you are not bound to accept a Tender you receive. We confirm that no Technical deviations are attached here with this commercial offer.

Thanking you,

Yours faithfully,

(Signature of the Bidder)

Printed Name

Designation

Seal

Date:

Business Address:

Witness Address: N.B: This letter should be scanned (PDF format) at a resolution of 150 dps and uploaded in the specific folder mentioned.



Annexure XIII: Summary of Cost Components

N.B: Bidders are instructed to follow the Annexure-XIII and XIV while preparing and uploading the BOQ in e-Procurement application. Bidders have to quote in the e-Procurement application as per the format provided there. However, they may provide information as per the format given in Annexure-XIII and XIV in the hard copy of Financial Bid (in case any discrepancy between BOQ format of e-Procurement application and formats provided here under, BOQ format of e-Procurement application will prevail). All unit rates indicated in the schedules shall be inclusive not limited to supply, installation, duties, transport, packing and transit insurance charges etc. Taxes should be indicated under the relevant column in the schedules.

Summary Component vise Cost Table

Sl No

Item Reference CAPEX (1)

OPEX (2)

Total Price (1+2)

Total Price in words

1

Cloud Enablement Infrastructure (table 1)

CAPEX= C1+C3+C4;

OPEX= O1+O3

2 Additional BOM (table 2)

CAPEX=C2;OPEX=O2



Annexure XIV: Breakdown of Cost Components

1. Bidder should provide all prices as per the prescribed format. Bidder should not leave any field blank. In case the field is not applicable, Bidder must indicate “0” (Zero) in all such fields. 2. All the prices (even for taxes) are to be entered in Indian Rupees ONLY (% values are not allowed) 3. It is mandatory to provide breakup of all Taxes, Duties and Levies wherever applicable and/or payable. 4. TSCA reserves the right to ask the Bidder to submit proof of payment against any of the taxes, duties, levies indicated. 5. TSCA shall take into account all Taxes, Duties & Levies for the purpose of Evaluation 6. The Bidder needs to account for all Out of Pocket expenses due to Boarding, Lodging and other related items.

The Unit Rate as mentioned in the following formats shall be used for the purpose of ‘Change Order’ for respective items, if any. However, based on the market trends, TSCA retains the right to negotiate this rate for future requirements.

Cloud Enablement Infrastructure CAPEX (C1) : Cost of items in table 1 of BOM

Sl No Components

Unit Rate (1)

Taxes (2)

Quantity (3)

Total Price (4)=(1+2)x3

1

Cloud Management Software with the functionality as defined in FRS & SOW:

• Virtual Machine Management • Security Capabilities • Self Service Provisioning • Process Automation • Capacity Management • Orchestration • Monitoring • Migration of VMs within and

across enclosures • Etc

(The cost of the solution should also include required hardware, Software, Licenses that are required to make the solution fully functional)

1

2 Blade Chassis 1

3 Blade Servers 4



4 Linux Enterprise Edition (Latest Version) Operating System

1

5 Windows Server Data Centre Edition (Latest version) Operating System

1

6 Virtualization S/W (hypervisor) for Servers (2 Hypervisor for each Server)

8

7 Cisco MDS 9134 8-Port 4Gb Port Activation Upgrade License (for existing SAN switch)

2

Total

CAPEX (C2) : Cost of items in table 2 of BOM Sl No Components

Unit Rate (1)

Taxes (2)

Quantity (3)

Total Price (4)=(1+2)x3

8 Blade Servers 8

9 Virtualization S/W (hypervisor) for Servers

16

10 SAN Storage Box 1

11 SAN Switch for connectivity to the SAN Storage

2

12 Cisco MDS 9124e 12-port Upgrade LTU for existing HP blade system + 4 SFP and 4 cables for connectivity

4

13 HP Virtual Connect Flex-10/10D Module for existing HP BladeSystem (With 10 No of 1 Gig external ports)

4

14

HP Virtual Connect 8Gb 24-Port Fibre Channel Module for existing HP BladeSystem (With 8 No of 8 Gig FC Ports)

4

15 HP LTO4 Ultrium 1.6TB read/write Data Cartridge (C7974A) with Tape label

100

16 MS office Home Edition 2 Total



CAPEX (C3) : Cost for Cloud enablement

Sl component Cost Taxes Total

1. Cloud enablement of TSDC infrastructure, with the help of equipments, HW, SW, etc supplied, installed, configured under the SOW of this RFP.

CAPEX (C4) : Cost for training

Sl component Cost Taxes Total

1. 3 weeks training on cloud to a team selected by TSCA

OPEX (O1) for CAPEX (C1)

First Year Second Year Third Year Sl Operational Support

Cost Taxes

Total Cost Taxes

Total Cost Taxes

Total

1. AMC cost for Hardware

2.

Support and subscription Cost for Software and Licenses

Total Total Total

Total cost for 3 (three) years:

OPEX (O2) for CAPEX (C2)


Cost Taxes

Total Cost Taxes

Total Cost Taxes

Total


Total Total Total




OPEX (O3)


Cost Taxes

Total Cost Taxes

Total Cost Taxes

Total

4.

Onsite operating and maintaining the cloud solution for a period of 2 months from O&M start date.

NA NA NA NA NA NA

5.

Service support for the calls escalated by the onsite TSCA service support team.

Total Total Total


Note: This Operational Support per year shall be for all the components / items / infrastructure under this RFP / Contract including the Support personnel deployed during the implementation for the project. This cost shall also include the implementation, integration requirement for making the cloud enablement solution operational. OPEX (O4): Breakup for OPEX items


UnitRate

Taxes

Total UnitRate

Taxes

Total UnitRate

Taxes

Total


1.1 Blade Chasis

1.2 Blade Server

1.3 SAN Storage Box

1.4 SAN Switch

2. Support and b i i



subscription Cost for Software and Licenses

2.1

Cloud Management Software

2.2 Virtualization S/W (hypervisor)

2.3

Linux Enterprise Edition (Latest Version) OS

2.4

Windows Server Data Centre Edition (Latest version) OS



Annexure XV: Existing Infrastructure of TSDC Sl No

Existing SDC Module

Make & Model Sub-Modules

Unicenter Network & Systems Management version 11.x - Managed Resources

CA Insight for Distributed Database

CA Spectrum Network Fault Manager Foundation Suite for Windows CA Spectrum Network Fault Manager Report Manager. CA eHealth Network Performance Manager Starter Suite CA eHealth Service Availability

CA IT Client Manager

CA Patch Management

1

EMS (Performance Monitoring) CAL licenses

CA Unicenter

CA Service Desk Manager Full License

IPS/IDS – Cisco IPS 4270

2 IPS/ IDS, Firewall Firewall – Fortigate 3016B (External FW) and Cisco ASA 5580 (Internal FW)

3

SAN Storage Management Software / Controller

HP EVA Command View 8.1 and HP Storage Management Utility

4 Backup Solution HP Data Protector Antivirus – CA Threat Manager

5 Antivirus , HIPS HIPS – IBM Proventia

Quantity/ Number

6 Racks (Available in Number)

24 Nos

7 Power per Rack available

5 KVA

8 SAN Switch Ports Available

Total 24 Licensed Ports out of 32 physical ports (All licensed ports are consumed)

9 L2 Switch Network Ports available

6 L2 Switch(48 Ports)-All Consumed



Sl No

Existing SDC Module

Make & Model Sub-Modules

10 Structured cabling per Rack available

Available

The Bidder is advised to prepare their integration and passive components requirement based on the table above. Any component which is required and is not specified in the BoM of this RFP should be specified in the table given in the Financial Bid as Other Components.



Annexure XVI: Abbreviations AAA Authentication, Authorization and Accounting ACL Access Control List ARP Address resolution protocol BGP border gateway protocol BOQ Bill of Quantity CPU Central Processing Unit DCO Data Centre Operator DHCP Dynamic Host Configuration Protocol DMZ De-Militarized Zone DNS Domain Name Server 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 G2G Government to Government GBIC Giga Bit interface Gbps Gigabits per second GE Gigabit Ethernet GHz Giga Hertz GoT Government of Tripura GUI Graphical User Interface H/W Hardware HDD Hard Disk Drive HIPS Host Intrusion Prevention System HTML Hypertext Markup Language I/O Input/ Output IDS Intrusion Detection System IP Internet Protocol IEEE International electrical and electronics engineers IPS Intrusion Prevention System IT Information Technology ITIL Information Technology Infrastructure Library Kbps Kilobits per second L2 Layer 2 LACP Link Aggregation Control Protocol LAN Local Area Network LFF Large Form Factor LUNs Logical unit number



MAC Media Access Control Mbps Megabits per second NAT Network Address Translation NOC Network Operation and Control OEM Original Equipment Manufacturer OFC Optical Fiber Channel OS Operating System QoS Quality of Service QGR Quarterly Guaranteed Revenue RAM Ran Access Memory RDBMS Relational Database Management System S/W Software SAN Storage Area Network SAS Secure Attention Sequence SeMT State e-Governance Mission Team SFP Small Form Factor Pluggable SLA Service Level Agreement SLL Small Form Factor SNMP Small Network Management Protocol SIA State Implementing Agency SI System Integrator TB Tera Byte TCP Transmission Control Protocol TPA Third Party Audit TSCA Tripura State Computerisation Agency TSWAN Tripura State Wide Area Network VLAN Virtual Local Area Network VPN Virtual Private Network WAN Wide Area Network XML Extensible Markup Language

rfp for cloud enablement

Documents

earnest money deposit

includes collusive practice

variable configurable speeds

existing hp bladesystem

port upgrade ltu

tsdc cloud enablement

unified resource pool

calling force majeure