request for proposal (rfp) selection of system integrator ...€¦ · ibef - rfp for selection...

Request For Proposal (RFP)

Selection of System Integrator for Brand India

portal, Mobile Solution, and content

management services

for

India Brand Equity Foundation (IBEF)

Tender no.: DM/05/01/2016

Date of Issue: 05/01/2016

Issued by:

India Brand Equity Foundation,

Apparel House, 5th Floor,

# 519-22, Sector 44,

Gurgaon - 122003, Haryana

IBEF - RFP for selection System Integrator to develop, maintain portal and mobile solutions

Ver 0.f of 73

Glossary

1. IBEF India Brand Equity Foundation

2. ATS Annual Technical Support

3. CVC Central Vigilance Commission

4. CSP Cloud Service Provider

5. EMD Earnest Money Deposit

6. LoI Letter of Intent

7. MSA Master Services Agreement

8. PBG Performance Bank Guarantee

9. RFP Request for Proposal

10. SLA Service Level Agreement

11. SP Service Provider

12. IA Implementation Agency


Ver 0.f of 73

Terms and Legends used in this document

Symbol / Terms

Meaning

<< >> Text to be filled in by the bidder in response to this document

India Brand Equity

Foundation (IBEF)

The India Brand Equity Foundation (IBEF), the “owner” of the project

under which this RFP document is being issued

Bidder / System

Integrator/Vendor

Any firm offering the solution, service(s) and /or materials as required in

the RFP.


Ver 0.f of 73

Table of Contents

1 Important Information ................................................................................................................. 5

2 Request for Proposal – Selection of System Integrator ............................................................. 6

2.1 Fact Sheet ................................................................................................................................ 6

2.2 Request for Proposal ............................................................................................................... 8

2.3 Structure of the RFP ................................................................................................................ 8

2.4 Background Information ......................................................................................................... 8

2.5 Instructions to the Bidders .................................................................................................... 11

2.6 Criteria for Evaluation .......................................................................................................... 16

2.7 Appointment of Portal/Website Service Provider ................................................................ 22

2.8 Scope of Work ...................................................................................................................... 24

2.9 Testing and User Acceptance Test (UAT) ............................................................................ 35

2.10 Key Personnel ....................................................................................................................... 36

2.11 Provisioning of client infrastructure and cloud services ....................................................... 37

2.12 Operation and Maintenance post Implementation Services .................................................. 41

2.13 Service Level Agreement ................................................................................................ 45

2.14 Project Timelines and Deliverables ...................................................................................... 49

2.15 Payment Terms & Schedule .................................................................................................. 52

2.16 GO-LIVE and Acceptance Criterion ..................................................................................... 52

2.17 Exit management & Transition ............................................................................................. 53

2.18 Fraud and Corrupt Practices .................................................................................................. 54

2.19 Conflict of Interest ................................................................................................................ 55

Appendix I: Pre-Qualification & Technical Bid Templates ............................................................. 57

Appendix II: Forms for Technical Proposal ..................................................................................... 62

Appendix III: Forms for the Financial Proposal ............................................................................... 69


Ver 0.f of 73

1 Important Information

S. No. Particular Details

1. Start date of issuance of RFP document 5th Jan 2016

2. Pre-Bid Conference 19th Jan 2016

3. Last date for Submission of Pre-Bid Queries 12th Jan 2016

4. Issue of Clarifications on Pre-Bid Queries 22nd

Jan 2016

5. Last date and time for Bid Submission 8th Feb 2016, 17:00 hours

6. Date and time of opening of Pre-Qualification bids 9th Feb 2016, 15:00 hours

7. Date and time for opening of Technical bids 11th Feb 2016, 15:00 hours

8. Date and time of Presentation by the bidders 16th Feb 2016, 11:00 hours

9. Date and time for opening of Commercial bids Will be informed later


Ver 0.f of 73

2 Request for Proposal – Selection of System Integrator

2.1 Fact Sheet

Clause Reference Topic

Section 2.7.1 The method of selection is: QCBS(Quality and Cost based Selection)

Section 2.5.4.4 RFP can be

Downloaded from www.ibef.org

Section 2.5.4.5 Earnest Money Deposit of amount 20,000,00 (Twenty lakh) by

Demand Draft in favor of “India Brand Equity Foundation” and

payable at “New Delhi” from any of the nationalized Scheduled

Commercial Bank

OR

Bank Guarantee as mentioned in Appendix I- Form 3

EMD should remain valid for 45 days after the Bid Validity period.

In case EMD is submitted by the bidder through Demand Draft, a new

Demand Draft shall have to be submitted by the bidder to commensurate with

the validity of EMD with the ‘bid validity period plus 45 days’. The new

Demand Draft shall be submitted at-least fifteen IBEF working days before the

expiry date of the original Demand Draft.

The bidders are required to submit the EMD at the following address :

Deputy CEO

India Brand Equity Foundation

Apparel House, 5th Floor, # 519-22

Sector 44, Gurgaon - 122003

Haryana

India

Section 2.5.4.5 Earnest Money Deposit Refund

EMD of all unsuccessful bidders would be refunded by IBEF within 30 days

of the bidder being notified as being unsuccessful.

Section 2.5.3 A pre-Bid meeting will be held at India Brand Equity Foundation (IBEF),

Apparel House, 5th Floor, # 519-22, Sector 44, Gurgaon - 122003,

Haryana.

on the date and time as mentioned in section 1 :

The name, address, and telephone numbers of the Nodal Officer is:

Deputy CEO



http://www.ibef.org/


Ver 0.f of 73

Clause Reference Topic


Haryana

India

All the queries should be received on or before the last date of Submission of

Queries as mentioned in section 1, through email.

Section 2.5.5.2

Proposals should be submitted in English language

Section 2.6.3 Taxes: As applicable

Section 2.5.7.2 Bid validity Period

Proposals must remain valid for 180 days after the last date of Proposal

Submission as mentioned in section 1.

Section 2.5.5 Submission of Proposals

Bidders must submit

An original and two additional copies of each proposal along with one

copy of non-editable CD for Prequalification & Technical Proposal.

The CD must be signed by the Bidder using a Permanent Marker.

One original copy of the Commercial Proposal

Section 2.5.5 The proposal submission address is:

Deputy CEO




Haryana

India

Section 2.5.5 Proposals must be submitted no later than the last date and time of Proposal

Submission as mentioned in section 1 Any submission later than this date and

time shall not be accepted.

Section 2.4.1 Contract Period

Any contract that may result from this project will be issued for Three years

(“the Term”) extendable by another Two years

Section 2.7.5 Validity of Performance Bank Guarantee

Performance Bank Guarantee must remain valid for 60 days after completion

of Contract Period

Value of PBG:

PBG value shall be 10% of the total order value.

Section 2.8 Support of these languages English, German, Arabic, Mandarin, Russian,

French, Japanese and any other language as decided by IBEF. Provision for

adding other languages in future.


Ver 0.f of 73

2.2 Request for Proposal

Sealed tenders are invited from eligible, reputed, qualified System Integrators with sound technical

and financial capabilities for providing but not limited to portal development and maintenance, mobile

solutions, content management services as detailed out in the Scope of Work under Section 2.8 of this

RFP Document. This invitation to bid is open to all Bidders meeting the minimum eligibility criteria

as mentioned in this RFP Document.

2.3 Structure of the RFP

This Request for Proposal (RFP) document for the project of “Selection of System Integrator for

Brand India portal, Mobile Solution and content management services for IBEF” comprise of the

following.

i. Instructions on the Bid process for the purpose of responding to this RFP. This broadly covers:

a. General instructions for bidding process

b. Bid evaluation process including the parameters for Pre-qualification, Technical

evaluation and commercial evaluation to facilitate IBEF in determining bidder’s

suitability as the implementation partner

c. Payment schedule

d. Commercial bid and other formats

ii. Functional and Technical Requirements of the project. The contents of the document broadly

cover the following areas:

a. About the project and its objectives

b. Scope of work for the Implementation Partner

c. Functional and Technical requirements

d. Project Schedule

e. Service levels for the implementation agency (IA)

The bidder is expected to respond to the requirements as completely and in as much relevant

detail as possible, and focus on demonstrating bidder’s suitability to become the implementation

agency for IBEF.

The bidders are expected to examine all instructions, forms, terms, Project requirements and other

information in the RFP documents. Failure to furnish all information required as mentioned in the

RFP documents or submission of a proposal not substantially responsive to the RFP documents in

every respect will be at the Bidder's risk and may result in rejection of the proposal.

2.4 Background Information

2.4.1 Basic Information

a) IBEF invites responses (“Tenders”) to this Request for Proposal (“RFP”) from eligible

Service Providers/Agencies (“Bidders”) for providing portal development and maintenance,


Ver 0.f of 73

mobile solutions, content management services as described in Section 2.8 of this RFP, Scope

of Work.

b) Any contract that may result from this procurement competition will be issued for a term as

mentioned in the Fact Sheet.

c) Proposals must be received not later than time and date and at the venue mentioned in the

Fact Sheet. Proposals that are received late WILL NOT be considered in this procurement

process.

2.4.2 Introduction

a. About IBEF

India Brand Equity Foundation (IBEF) is a trust established by the Department of Commerce,

Ministry of Commerce and Industry, Government of India. IBEF's primary objective is to

promote and create international awareness of the Made in India label in markets overseas and to

facilitate dissemination of knowledge of Indian products and services. Towards this objective,

IBEF works closely with stakeholders across government and industry.

India, today, is well established as a credible business partner, preferred investment destination,

rapidly growing market and provider of quality services and manufactured products; and, stands

on the threshold years of unprecedented growth.

IBEF works with a network of stakeholders - domestic and international - to promote Brand

India.

More information about IBEF can be obtained from the web site: www.ibef.org

b. About the Brand India website/portal

IBEF intends to Design, Develop and Maintain a mega B2B portal. The objective of the portal is

to create a positive perception of Indian products and services in markets abroad and to project

India as a reliable supplier of quality goods and services. The portal needs to engage with

domestic and global audiences. A Mobile App also needs to be developed for this portal. IBEF

intends to make it a flagship portal of international repute for promoting made in India goods and

services. This portal will act as a platform for various Indian manufacturers and MSMEs to

promote and sell their products and services.

Key areas for consideration and features to be implemented are as mentioned below (details of

any other considerations and sub-features within the below core considerations and features to be

discussed during requirements phase):

User Experience

o Organized Navigation

o Search mechanism

o Responsiveness to the search queries

Content Management System

o Content Design and Regulation

o Content Search

o Content Revision and Management

Feedback and Grievance system

o User Feedback mechanism

o Information Sharing (blogs, forum etc.)

o Grievance system

Infrastructure Hosting Services



Ver 0.f of 73

o Hosting Portal

o Hosting Mobile Solutions

o End to End hosting

In this regard, IBEF announces a tender detailed in this document.

c. Leveraging the cloud capability

IBEF proposes to leverage cloud service offerings for the IBEF Mega portal solution. The

Service Provider should leverage Infrastructure-as-a-Service (IaaS) and if available and meets the

RFP requirements, offerings from Cloud Service Provider (CSP) for deploying the IBEF web

portal solution. For the system software that is not procured as a service from the Cloud Service

Provider, the Service Provider shall procure the same along with the ATS (Annual Technical

Support) from the OEM as per the requirements in the RFP.

The compute & storage requirements may be scaled (up or down) over the period of the contract

in line with the transaction load to meet the SLA requirements. The application shall be

architected and designed to leverage the cloud characteristics such as rapid elasticity and handle

transient and hardware failures without downtime.

In addition to the production environment, Service provider shall also provision for the

development, test, and training environments on the cloud infrastructure. The testing of the

integrated solution should be carried on the test environment that is a miniature of the production

environment.

The Cloud Service provider and the service offerings of the Cloud Service Provider used for the

IBEF project shall meet the requirements detailed under Annexure I of this RFP.

2.4.3 Key Information

a. Objective of the portal

IBEF is planning to have mega portal in addition to mobile application to serve its stakeholders,

both internal and external. The main objective of this project is to promote Indian products and

services across the globe. The portal will act as a one stop shop for major Indian products and

services to the world.

This mega portal shall provide services briefed in para 2.4.2b of this document and detailed in

section 2.8, Scope of Work.

b. Stakeholder Details

Following important stakeholders have been identified:

Indian Manufacturers/Exporters

MSMEs(medium and Small Medium) Enterprises

Importers from foreign countries

Various departments of the Government of India


Ver 0.f of 73

2.5 Instructions to the Bidders

2.5.1 General

a) While every effort has been made to provide comprehensive and accurate background

information and requirements and specifications, Bidders must form their own conclusions

about the solution needed to meet the requirements.

b) All information supplied by Bidders shall be treated as contractually binding on the Bidders,

on successful award of the assignment by the IBEF on the basis of this RFP.

c) No commitment of any kind, contractual or otherwise shall exist unless and until a formal

written contract has been executed by or on behalf of the IBEF. Any notification of preferred

bidder status by the IBEF shall not give rise to any enforceable rights by the Bidder. The

IBEF may cancel this public procurement at any time prior to a formal written contract being

executed by or on behalf of the IBEF.

d) This RFP supersedes and replaces any previous public documentation & communications

from IBEF, and Bidders should place no reliance on such communications.

2.5.2 Compliant Proposals / Completeness of Response

a) Bidders are advised to study all instructions, forms, terms, requirements and other information

in the RFP documents carefully. Submission of the bid shall be deemed to have been done

after careful study and examination of the RFP document with full understanding of its

implications.

b) Failure to comply with the requirements of this paragraph may render the Proposal non-

compliant and the Proposal may be rejected. Bidders must:

i. Include all documentation specified in this RFP;

ii. Follow the format of this RFP and respond to each element in the order as set out in

this RFP

iii. Comply with all requirements as set out within this RFP.

2.5.3 Pre-Bid Meeting & Clarifications

2.5.3.1 Pre-bid Conference

a. IBEF may hold a pre-bid meeting with prospective bidders. Refer Fact Sheet for details.

b. The Bidders will have to ensure that their queries for Pre-Bid meeting should reach the

designated officer on or before the Date mentioned in the Fact Sheet.

c. The queries should necessarily be submitted in the following format:


Ver 0.f of 73

S. No. RFP Document

Reference(s) (Section &

Page Number(s))

Content of RFP

requiring

Clarification(s)

Points of clarification

1.

2.

3.

4.

5.

6.

IBEF shall not be responsible for ensuring that the bidders’ queries have been received by them.

Any requests for clarifications post the indicated date and time may not be entertained by the

IBEF. The replies to the queries shall be published on IBEF website (www.ibef.org).

2.5.3.2 Responses to Pre-Bid Queries and Issue of Corrigendum

a. The Nodal Officer notified by the IBEF will endeavour to provide timely response to all

queries. However, IBEF makes no representation or warranty as to the completeness or

accuracy of any response made in good faith, nor does IBEF undertake to answer all the

queries that have been posed by the bidders.

b. At any time prior to the last date for receipt of bids, IBEF may, for any reason, whether at its

own initiative or in response to a clarification requested by a prospective Bidder, modify the

RFP Document by a corrigendum.

The Corrigendum (if any) & clarifications to the queries from all bidders will be posted on the

www.ibef.org and emailed to all participants of the pre-bid conference.

c. Any such corrigendum shall be deemed to be incorporated into this RFP.

d. In order to provide prospective Bidders reasonable time for taking the corrigendum into

account, IBEF may, at its discretion, extend the last date for the receipt of Proposals.

2.5.4 Key Requirements of the Bid

2.5.4.1 Consortium

Consortium shall not be permitted to bid.

2.5.4.2 Sub-contracting

The selected Vendor will undertake to implement the mega brand India portal and its related

components as mentioned in this RFP for IBEF and will not outsource or subcontract any or all

of the services being offered to IBEF to any company or to a company fully / partly owned by the

Vendor, without the written consent of the IBEF.

Only Infrastructure hosting services can be sub-contracted, if required.

2.5.4.3 Right to Terminate the Process

a. IBEF may terminate the RFP process at any time and without assigning any reason. IBEF

makes no commitments, express or implied, that this process will result in a business

transaction with anyone.




Ver 0.f of 73

b. This RFP does not constitute an offer by IBEF. The bidder's participation in this process may

result IBEF selecting the bidder to engage towards execution of the contract.

2.5.4.4 RFP Document

The bidder can download the RFP document from the website provided in the Fact sheet.

2.5.4.5 Earnest Money Deposit (EMD)

a. Bidders (except those who are registered with the Central Purchase Organization or National

Small Industries Corporation (NSIC)) shall submit along with their Bids, EMD of said

amount as mentioned in the Fact sheet.

b. EMD of all unsuccessful bidders would be refunded by IBEF as mentioned in the Fact sheet.

c. The EMD, for the amount mentioned above, of successful bidder would be returned upon

submission of Performance Bank Guarantee as per the format provided in Appendix III.

d. The EMD amount is interest free and will be refunded to the unsuccessful bidders without any

accrued interest on it.

e. The bid / proposal submitted without EMD, mentioned above, will summarily be rejected.

f. The EMD may be forfeited:

If a bidder withdraws its bid during the period of bid validity.

In case of a successful bidder, if the bidder fails to sign the contract in accordance

with this RFP and within specified time.

2.5.4.6 Submission of Proposals

a. The bidders should submit their responses as per the format given in this RFP in the manner

mentioned in the Fact sheet.

b. The Response to Pre-Qualification criterion, Technical Proposal and Commercial Proposal

should be covered in separate sealed envelopes super-scribing “Pre-Qualification Proposal”,

"Technical Proposal" and “Commercial Proposal” respectively. Each copy of each bid should

also be marked as "Original" OR "Copy" as the case may be. All pages should be numbered

as “Page # of n”.

c. The documents to be submitted as part of the Pre-Qualification & Technical proposals are

stated in Appendix I: Pre-Qualification & Technical Bid Templates.

d. The documents to be submitted as part of the financial proposal are stated in Appendix II:

Financial Proposal Template.

e. Please note that prices should not be indicated directly or indirectly in the Pre-Qualification

Proposal or Technical Proposal but should only be indicated in the Commercial Proposal.

f. The three envelopes containing copies of Pre-qualification Proposal, Technical Proposal and

Commercial Proposal should be put in another single sealed envelope clearly marked << RFP

Reference Number>> and the wordings “DO NOT OPEN BEFORE” <<Date and Time as

mentioned in the Fact sheet>>.

g. The outer envelope thus prepared should also indicate clearly the name, address, telephone

number, E-mail ID and fax number of the bidder to enable the Bid to be returned unopened in

case it is declared "Late".

h. All the pages of the proposal must be sequentially numbered and must contain the list of

contents with page numbers. Any deficiency in the documentation may result in the rejection

of the Bid.


Ver 0.f of 73

i. The original proposal/bid shall be prepared in indelible ink. It shall contain no interlineations

or overwriting, except as necessary to correct errors made by the bidder itself. Any such

corrections must be initialed by the person (or persons) who sign(s) the proposals.

j. All pages of the bid including the duplicate copies, shall be initialed and stamped by the

person or persons who sign the bid.

k. In case of any discrepancy observed by IBEF in the contents of the submitted original paper

bid documents with respective copies, the information furnished on original paper bid

document will prevail over others.

l. Bidder must ensure that the information furnished by him in respective CDs is identical to

that submitted by him in the original paper bid document. In case of any discrepancy observed

by IBEF in the contents of the CDs and original paper bid documents, the information

furnished on original paper bid document will prevail over the soft copy.

m. All pages of the bid shall be initialed and stamped by the person or persons who are

authorized to sign the bid.

2.5.4.7 Authentication of Bids

A Proposal should be accompanied by a power-of-attorney in the name of the signatory of the

proposal.

2.5.5 Preparation and Submission of Proposal

2.5.5.1 Proposal Preparation Costs

The bidder shall be responsible for all costs incurred in connection with participation in the

RFP 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 IBEF to facilitate the evaluation

process, and in negotiating a definitive contract or all such activities related to the bid process.

IBEF will in no case be responsible or liable for those costs, regardless of the conduct or

outcome of the bidding process.

2.5.5.2 Language

The Proposal should be filled by the Bidder in the language as mentioned in the Fact sheet. If

any supporting documents submitted are in any language other than English, translation of the

same in English language is to be duly attested by the Bidders. For purposes of interpretation

of the Proposal, the translation in the language as mentioned in the Fact sheet shall govern.

2.5.5.3 Venue & Deadline for Submission of Proposals

Proposals, in its complete form in all respects as specified in the RFP, must be submitted to

IBEF as mentioned in the Fact sheet.


Ver 0.f of 73

2.5.5.4 Late Bids

a. Bids received after the due date and the specified time (including the extended period if any)

for any reason whatsoever, shall not be entertained and shall be returned unopened by Speed-

post only.

b. The bids submitted by telex/telegram/fax/e-mail etc. shall not be considered. No

correspondence will be entertained on this matter.

c. IBEF shall not be responsible for any postal delay or non-receipt/ non-delivery of the

documents. No further correspondence on the subject will be entertained.

d. IBEF reserves the right to modify and amend any of the above-stipulated condition/criterion

depending upon project priorities vis-à-vis urgent commitments.

2.5.6 Deviations

The bidder may not provide any deviation / non-compliance to the contents of the RFP

document. Any deviation /non-compliance may lead to rejection.

2.5.7 Evaluation Process

a. A Proposal Evaluation Committee shall be formed to evaluate the responses of the bidders

b. The Proposal Evaluation Committee shall evaluate the responses to the RFP and all

supporting documents / documentary evidence. Inability to submit requisite supporting

documents / documentary evidence, may lead to rejection.

c. The decision of the Proposal Evaluation Committee in the evaluation of responses to the RFP

shall be final. No correspondence will be entertained outside the process of negotiation/

discussion with the Committee.

d. The Proposal Evaluation Committee may ask for meetings with the Bidders to seek

clarifications on their proposals if the committee desires and feels the need for it.

e. The Proposal Evaluation Committee reserves the right to reject any or all proposals on the

basis of any deviations.

f. Each of the responses shall be evaluated as per the criterions and requirements specified in

this RFP.

2.5.7.1 Tender Opening

The submitted tenders will be opened by the proposal evaluation committee, in the presence

of such of those Bidders or their representatives who may like to be present at the time of

opening. The date of opening shall normally be as per the Fact sheet. However any change in

the date shall be mentioned on the IBEF website only.

The representatives of the bidders should be advised to carry the identity card or a letter of

authority from the tendering firms to identify their bonafides for attending the opening of the

proposal, besides personal photo id.

2.5.7.2 Tender Validity

The offer submitted by the Bidders should be valid for minimum period of for the period

mentioned in the Fact sheet.


Ver 0.f of 73

IBEF may at its discretion extend the bid’s validity period. Extension of validity period by the

Bidder should be unconditional and irrevocable. The EMD provided shall also be suitably

extended by the bidder. A bidder acceding to the request will neither be required nor be

permitted to modify its Bid. A bidder may refuse the request (to extend the validity period)

without forfeiting its EMD. In any case, the EMD of the bidders shall be returned after

completion of the process.

2.5.7.3 Tender Evaluation

a. Initial Bid scrutiny will be held and incomplete details as given below will be treated as

non-responsive, if Proposals :

Are not submitted in the format as specified in the RFP document

Received without the Letter of Authorization (Power of Attorney)

Are found with suppression of details

With incomplete information, subjective, conditional offers and partial offers

submitted

Submitted without the documents requested in the RFP document

Have non-compliance of any of the clauses stipulated in the RFP

With lesser validity period

Without EMD

b. All responsive Bids will be considered for further processing as below.

A list of responsive bidders shall be prepared, who comply with all the terms and

conditions of the tender. All eligible bids will be considered for further evaluation by a

Committee according to the Evaluation process defined in this RFP document. The

decision of the Committee will be final in this regard. Financial bids of successful bidders

shall be opened on a date which shall be specified on IBEF website. Interested bidders

may attend if they so desire.

2.6 Criteria for Evaluation

2.6.1 Pre-Qualification Criteria

Bidders who meet the below given eligibility requirements would be considered as qualified to move

to the next stage.

S.

No.

Basic

Requirement

Specific Requirements Documents Required

1. Power of

Attorney

Individual signing the documents in connection with

the Bid must be certified to do so

Power of Attorney in the

name of the Authorized

signatory

2. Particulars of the

Bidders

Details of the bidder as per format provided in the

RFP

Form 2

3. Office Location Bidder should have an office in NCR Delhi Copy of a proof in this regard

in the form of Municipality

Registration/ Labour

Department registration

4. Earnest Money EMD is required to protect IBEF against the risk of Original EMD


Ver 0.f of 73

S.

No.

Basic

Requirement


Deposit Bidder's conduct

5. Legal Entity The Bidder should be a company registered under

Indian Companies Act 1956.

Registered with the Indian Service Tax Authorities.

Should have been operating for the last five years as

on 30-09-2015 in India.

1) Certificate of

Incorporation

2) Registration Certificate

3) Memorandum and Articles

of Association or Filings to

the Stock Exchanges

4) PAN

5) Service tax registration

certificate

6. Turnover Bidder’s Annual Sales Turnover (global / India

based) should be at least INR 25 Crore for each of

the last three financial years as on March 31, 2015.

Certificate from the statutory

auditor

7. Profitability Company should be profitable during each of the last

three financial years (as per the last

published/audited Balance sheets).


auditor

8. Net worth Company’s Net Worth should be at least 10 Cr. as

on March 31, 2015.


auditor

9. Portal/Web

development

experience

The Bidder shall have proven experience of

developing, operating and maintaining at least Five

(5) portal/Web solutions in last 3 years based on

COTS (Commercially off the shelf) solution

pertaining to aggregation services as a “System

Integrator” with value of each project at least 50

Lacs and at least one project with value 1 Crore.

The bidder should have successfully done these

executions for Business to Business (B2B),

Government to Business (G2B), Government to

Citizen (G2C) or Business to Consumer (B2C). The

portal/Web should have been developed for

client/partner only.

“System Integrator” role shall necessarily

include at least 3 of the following in one assignment

(one mandatory of Portal Development &

Maintenance and two others optional of (b), (c), (d)

below)

a. Portal/Website Development & Maintenance

b. Content Management Services

c. IT Infrastructure hosting services

d. Mobile solution development

Completion Certificates from

the client;

OR

Purchase / Work Order +

Phase Completion Certificate

from the client

OR

Citations that include letter

from the client or contract

agreements

10. Manpower The bidder should have at least 100 IT professionals

on its rolls as on the date of submission.

A Self Certified letter by the

Authorized Signatory which

should be HR head or

Company Secretary

11. Blacklisting The bidder should not be currently blacklisted or

banned by any Government / Government

Department/ PSU for corrupt or fraudulent practices

or non-delivery or non-performance as of submission

of their bid.

A Self Certified letter by the

Authorized Signatory

12. Certification The Bidder should be having the following Copy of certification which


Ver 0.f of 73

S.

No.

Basic

Requirement


certifications

a) CMMi Level 3 or above Certification

b) ISO/IEC 27001 for Infrastructure Hosting

services,

should be valid at the time of

Bid Submission

In case of subcontracting of

Hosting services certificate

should be provided from the

Subcontracting organization.

2.6.2 Technical Scoring Model

Bidders who meet the pre-qualifications requirements would be considered as qualified to

move to the next stage - Technical scoring. Bidders will either get the assigned mark on

fulfilling a criteria or will get zero (no mark) if a criteria is not met.

It is expected that the Bidders shall provide solutions be highly scalable and support the future

requirements of the project. In this regards, solutions/products accredited by leading

agencies shall be preferred.


Ver 0.f of 73

No Evaluation Criterion

(Figures in brackets indicate the maximum score)

Max score

1 Previous Project Experience

(Weightage will be given for project references where

the bidder has implemented solutions in the cited

projects that match the proposed solution for Brand India

Portal)

25

1.A Previous project experience in Implementation of portal

on a COTS based solution architecture for providing e-

commerce or aggregator website services to citizens/

businesses – features comprising of product catalogue

services, comprehensive search mechanism, multi

lingual support, rich media content support, workflow

engine, online payment facilities, DMS, user registration

system, user feedback and review system.

1. Product catalogue services (1)

2. Search mechanism (1)

3. Multi lingual support (1)

15

(5) Projects with (3) marks

each

1.B The project should have been used to deliver average

50,000 financial or non-financial transactions monthly

and also capable of handling at least 1000 concurrent

users.

Transactions: 5 Marks

Concurrent Users: 5 marks

10

Transactions

>=2 Lac : 5 Marks

>= 1 Lac: 3 Marks

>=50K : 1 Marks

Users

>=3000 : 5 Marks

>=2000: 3 Marks

>= 1000 : 1 Mark

<1000 : 0 Mark

2. Proposed Solution 30

Underlying Solution (Response will be evaluated on

Openness, Flexibility, Maintainability, Configurability,

Reusability that will lead to reduced cycle time of

change and first time right):

i. Overall Design & Architecture of the Proposed

Solution that meets the requirements specified in

the RFP (5)

ii. Underlying Solution components ( Website

design, Workflow Engine, Rule Engine,


Ver 0.f of 73

Payment Solution, Search mechanism, Content

management solution, DMS …) catering to

IBEF portal requirements as indicated in the

RFP (5)

(An indicative list of functional and technical

requirements is given in RFP. However the SP may

propose the solution components based on the solution

design proposed to meet IBEF portal requirements.

Service Provider should propose COTS based solution to

meet IBEF portal requirements.)

iii. Design and layout of the proposed portal

pertaining to ease of product search, portal

navigation, categorization of products &

services etc. (4)

iv. Methodology and approach for updating the

content on the portal (4)

v. Details of the cloud offerings( Deployment

Architecture, Underlying calculations justifying

the sizing, Adequate provision for Year on Year

Requirements) to meet the requirements

specified in Annexure pertaining to cloud

services (4)

vi. Quality of resources proposed for this project

(Level of skills, qualifications & Experience)

(5)

vii. Mobile application solution capability (3)

3 Demonstration of the similar projects 20

Vendor needs to show the following capabilities in the

already implemented systems for other clients on the live

working system either at the client site or through remote

connection

i. Design of the web/portal system-5

ii. Responsiveness of the portal to user queries, search

capability, page loading etc. -3

iii. User registration system-3

iv. Ease of Content creation and updation-4

v. Ease of navigation across the web portal-2

vi. Grievance and redressal mechanism-2

vii. Mobile application -1

20


Ver 0.f of 73

4 Technical Presentation 25

i. Walk-through of the proposal in the presentation

(5)

ii. Detailed explanation of overall project plan (10)

Project Plan, including Resource planning,

allocation and Loading

Proposed Status Reporting mechanism

Governance structure

iii. Clarity of understanding of the project and

risks(5)

iv. Proposed Operations and Maintenance Services

methodology and Tools (EMS solution, Project

management Tool, issue tracker, Configuration

management tool) (5)

Total 100

Bidders, whose bids are responsive, who score at least 70% in the defined technical scoring

mechanism would be considered technically qualified. Price Bids of such technically qualified bidders

alone shall further be opened.

2.6.3 Commercial Bid Evaluation

a. Only fixed price financial bids indicating total price for all the deliverables and services

specified in this bid document will be considered.

b. This Fixed Annual Fee will cover costs/expenses of the design, development, maintenance

and hosting of Brand India B2B portal by Agency for undertaking work as detailed in the

Scope of Work.

c. Fixed Annual Fee, to be quoted year-wise for three years, from the date of issue of work

order, along with the total for three years, as given below:

1. 1st year: Rs.--------

2. 2nd year: Rs.--------

3. 3rd year: Rs.--------

4. Total for 3 years: Rs.--------

This break-up of cost will not be considered for financial evaluation.

d. The bid price will exclude all taxes and levies and shall be in Indian Rupees and mentioned

separately. Service Tax though needs to be mentioned separately. Service Tax shall be paid

extra based on the prevailing rates and submission of proof of payment.

e. The evaluation of bids shall be done after excluding the Service Tax.

f. Any conditional bid would be rejected.

Errors & Rectification: Arithmetical errors will be rectified on the following basis: “If there

is a discrepancy between the unit price and the total price that is obtained by multiplying the


Ver 0.f of 73

unit price and quantity, the unit price shall prevail and the total price shall be corrected. If

there is a discrepancy between words and figures, the amount in words will prevail”

2.7 Appointment of Portal/Website Service Provider

2.7.1 Award Criteria

The selection of Implementation Agency would be done under Quality and Cost Based

Selection (QCBS) method and procedures.

A composite score shall be calculated for those bidders whose bids are found to be in

order.

The weightage for the composite evaluation is as described below:

a. Technical – 70%

b. Commercial/Financial – 30%

For Quality and Cost based Evaluation (QCBS), the following formula will be used for

evaluation of the bids.

B = 0.7 * Tn + 0.3 * (Cmin/Cb X 100)

Where

Bn = overall score of bidder under consideration

Tn = Technical score for the bidder under consideration

Cb = Commercial Bid of the bidder under consideration

Cmin = Lowest Commercial Bid among the financial proposals under consideration

The bidder achieving the highest overall score will be termed the successful bidder for

awarding the work order. In case of a tie where two or more bidders achieve the same

highest overall score, the bidder with the higher technical score will be considered first

for awarding the work order.

The bid price will exclude all taxes and levies and shall be in Indian Rupees and

mentioned separately.

Any conditional bid would be rejected.

Errors & Rectification: If there is a discrepancy between words and figures, the amount

in words will prevail.

2.7.2 Right to Accept Any Proposal and To Reject Any or All Proposal(s)

IBEF reserves the right to accept or reject any proposal, and to annul the tendering process /

Public procurement process and reject all proposals at any time prior to award of contract,

without thereby incurring any liability to the affected bidder or bidders or any obligation to

inform the affected bidder or bidders of the grounds for IBEF action.


Ver 0.f of 73

2.7.3 Notification of Award

Prior to the expiration of the validity period, IBEF will notify the successful bidder in writing or

by fax or email, that its proposal has been accepted. In case the tendering process / public

procurement process has not been completed within the stipulated period, IBEF may like to

request the bidders to extend the validity period of the bid.

The notification of award will constitute the formation of the contract. Upon the successful

bidder's furnishing of Performance Bank Guarantee, IBEF will notify each unsuccessful bidder

and return their EMD.

2.7.4 Contract Finalization and Award

After the successful bidding and verification IBEF shall draft the contract agreement to be signed

and awarded to the selected bidder.

2.7.5 Performance Guarantee

The IBEF will require the selected bidder to provide a Performance Bank Guarantee, within

specified time period from the Notification of award, for a value equivalent to the specified

amount of the total cost of ownership as mentioned in the Fact sheet. The Performance Guarantee

shall be kept valid till completion of the project and warranty period and shall be refunded

without interest after successful completion of the project. In case of due extension of the

Contract, the validity period of the Performance Bank Guarantee shall be extended by the vendor.

The Performance Guarantee shall contain a claim period of three months from the last date of

validity. The selected bidder shall be responsible for extending the validity date and claim period

of the Performance Guarantee as and when it is due on account of non-completion of the project

and warranty period. In case the selected bidder fails to submit performance guarantee within the

time stipulated, the IBEF at its discretion may cancel the order placed on the selected bidder

without giving any notice. IBEF shall invoke the performance guarantee in case the selected

vendor fails to discharge their contractual obligations during the period or IBEF incurs any loss

due to vendor’s negligence in carrying out the project implementation as per the agreed terms &

conditions.

2.7.6 Signing of Contract

After the IBEF notifies the successful bidder that its proposal has been accepted, IBEF shall enter

into a contract, incorporating all clauses, pre-bid clarifications and the proposal of the bidder

between IBEF and the successful bidder.

2.7.7 Failure to Agree with the Terms and Conditions of the RFP

Failure of the successful bidder to agree with the Draft Legal Agreement and Terms &

Conditions of the RFP shall constitute sufficient grounds for the annulment of the award, in

which event IBEF may award the contract to the next best value bidder or call for new proposals

from the interested bidders.

In such a case, the IBEF shall invoke the PBG of the most responsive bidder.


Ver 0.f of 73

2.8 Scope of Work

Broad Scope of Work

The successful bidder is fully responsible for the following broad categories of work for IBEF portal

1. Website design and development (for desktop and Mobile platform)

2. Content management system

3. Infrastructure services

4. Mobile Application Development

5. Social Media Integration

Detailed Scope of Work

These are MINIMUM indicative requirements and the bidder is required to fully comprehend and

develop the solution best suited to meet the requirements of the RFP. The detailed scope of work is as

given below and is applicable for the Contract Period.

1. Website design and development (for Desktop and Mobile platform)

Functional Requirements

Intuitive and easy

to Navigate

The design should be visually appealing, have a unified look and feel and

provide easy navigation throughout. As most users are interested in the product

catalogues, this should be the central component of the website.

It should provide Layered-navigation filters to help customers quickly narrow

their product options and pinpoint exactly what they’re looking for on the

category page.

Web design

Website should be developed utilizing modern web design and standards,

compatible with all the modern browsers (Mozilla, Firefox, Safari, Chrome,

Internet Explorer, Opera etc.) while providing graceful degradation for older

browsers. Website URLs should predominantly be clean URLs. This design

should be mobile device friendly and should support all the predominant mobile

platform such as Android, iOS, Windows Mobile with proper rendering.

Search

mechanism

Website should have a simple and standardized search with a text-box able to

search site-wide, such as a Google custom search.

Search should be able to capture items based on category, type products, cost,

source of origin, discount etc..

Sub-searches should also be available based upon various filters.

Search should include but not limited to the following search types

Native In-site search

Predictive Search

Type ahead search with product display

Multi-lingual

support

The portal (desktop and mobile version) should support at-least these languages

with provision to add more languages in future whenever required


Ver 0.f of 73

English, German, Arabic, Mandarin, Russian, French, Japanese.

Rich Media

Content

Website should support rich media content such as videos, high resolution

pictures, animations etc. for product information, product manuals, product

promotions, product brochures etc.

Document

Management

System

Provides effective and secured means of storage, retrieval and management of

attachments submitted by the IBEF users (buyers, sellers or IBEF users).

Workflow Engine Provides the automatic management and execution of all system processes and

would facilitate flow of information, task and events.

Multi-platform

support

The website should be developed as Responsive website supported on across

major hardware platforms such as PC, Mobile, PDAs etc. The website should

automatically render a mobile view when opened on a mobile device. Only

single URL should be used for the website for all the platforms.

User registration

System

Provide a registration system that enables different access levels for different

users (Buyers, Sellers, admin etc.).

Account status will be linked to the kind of user

Account registration will be required for access to community features

such as blogs, discussion, chat etc.

Guest users should also be able to access all the functionality of the

website

Login should also be supported via different social media platform IDs

such as Twitter, Facebook, Google, Yahoo etc.

Product

Information

Management

The following minimum functionalities should be supported in terms of product

information catalogue with scope of addition after discussion during

requirement gathering phase of project implementation

Product Configuration

Product catalog based on Manufactures

Product catalog based on Categories

Single Product

Product with options

Collection Products

Bundles

Personalized products

Product Attributes

SKU (Stock Keeping Unit)

Inventory

Brand

Imagery

Video

Rates & Review

Questions & Answers

Short description, long description

Product Comparison

Custom Attributes

…..

Product Pricing


Ver 0.f of 73

Cost

On Sale

Tier Pricing

Contract Pricing

……

Product Taxes

Tax category Management

…..

Currencies

Multi-currency

Custom Exchange Calculations

…….

Inventory management

SKU-level inventory

……

Promotions and

Merchandising

Promotion management

Unique Promo Code

One-time Use Promo

One-per-customer Promo

One-per-shipping-address Promo

Inclusion/Exclusion by Customer Tier Group (Customer Segmentation,

Country etc.)

Inclusion/Exclusion by Sub Category

Inclusion/Exclusion by Affiliate Source ( Email, Social)

Begins On/Expires On Promo

Flash Promo (Valid for first X # of uses, for example)

Auto-Triggering

……

Promotion Types

By Manufacturers/Brand

By Category (Percentage)

By Sub-category (Percentage)

Stock Number Specific

…….

Merchandising

Cross sell

Upsell

Bundled Products

Shop by

Frequently Purchased Products

Previously Viewed

Recommended Products

People Who Bought This Bought That

Low Inventory

Back orders


Ver 0.f of 73

……..

User Management Super User

The super admin should be able to manage the overall content of the

website and also should have the option to edit/ delete contents.

The super administrator should be able to create users as per the

requirement and assign necessary permissions to update/delete/modify

the portal/website content.

General User Information

Unique User ID

Buyer and seller profiles

Customized sections for Buyers and Sellers with relevant functionalities

User Fields

Multiple Addresses

Contact Information

Manage catalog request

…….

Members Area

Manage my account

Order History

View Wishlist

Subscription Management

Share Wishlist on Social Media

Reset Password

…….

Personalization

User should be able to personalize the landing page based on the

products/services of their interest

Personalized content based on digital analytics based on various

parameters such as user needs, order history, user profiling, search and

browsing preferences, location etc.

Option to add custom landing pages with rich content

Analytics &

Reporting

The reporting should be comprehensive enough to analyze any trend or analysis

based on various parameters available. The below list of reporting parameters is

indicative and can be modified during actual requirement analysis. These are

minimum indicative requirements. All the reports should be easily customizable

for different parameters.

Website Analytics

No. of unique visitors

Products searched/viewed

Location of visitors

Access to third party websites

Bounce rate

…….

Order reports

Customize

Daily Trends


Ver 0.f of 73

Country wise Orders

Monthly Comparison

New Buyers

Repeat Purchases

Sales Trends

Shipping Latency

Status

Subscriptions

Top Customers

Transaction History

……..

Product Reports

Back-Ordered Products

Cost Trend Analysis

Cross-sell/Up-sell Performance

Inventory on Hand

Inventory Sell Through

Products Most Viewed

Products By Sub-Category

Top Categories

Top Sub-Categories

Traffic reports

404/Detailed Traffic

By Location

Keywords Analysis

SEO

Source

Summary

Top Product Views

Trends

User Reports

Credit/Refund Report

Sales by User

Top sellers

Scheduled Reports

Upsell/Cross-Sell

Top Customers

User Feedback &

Review

mechanism

A complete grievance redress system should be built to cater to following

functionalities

User should be able to register and escalate complain

User should be able to provide feedback about product, delivery

services, seller, packaging etc. online, via email.

Online customer center to take care of all the complaints via Live chat,

or emails

Auto escalation mechanism


Ver 0.f of 73

FAQs

Ability to add reviews by customers for different products and services

System should be able to redirect the query to relevant stakeholder and

to IBEF automatically

Social Media integration to share reviews

Discussion forum support

Integrated tools to send review invitations via email and social media

User should be able to upload pictures or videos of the products as part

of feedback and complaint mechanism

Link to Merchant

website

This website should provide link to seller’s website and other website promoted

by Export promotion councils wherever information is provided. The website

can be provisioned to open within the brand India portal or can be opened

separately.

Performance The portal opening response time should be within 2-3 secs.

As the number of users can’t be assessed at this point of time but portal

should be able to handle at-least 2 lacs users per month with a

growth rate of 30% on YOY basis.

The number of concurrent users can be anywhere between 2-3K, but

portal should be able to handle the future requirement also in terms of

concurrent users as this number may increase significantly once the

website is promoted in various countries.

Vendor needs to build a scalable system keeping in view the dynamic

nature of the website.

General SI will be responsible for purchasing the Domain name in consultation

with IBEF.

Functionality of ‘Send a business query’ and ‘Invite Quote’

Functionality of “Minimum Order Quantity”

Related business query/request for a quote should automatically go to

relevant sellers

Functionality of ‘zoom in/zoom out’ while browsing through product

listings

Portal will need to have all the functionalities of an E-Commerce portal

except payment gateway (the portal will not have payment gateway

initially)

Portal should be SEO friendly

IBEF will need to have access to all functionalities in order to

add/remove/block the product listings as well as buyers/sellers/visitors

etc.

Portal must be secure from virus attacks, malware and hackers etc.

Past Go-Live, with every significant change to the Mobile web solution,

the solution provider must ensure its correct rendering on these devices.

For purposes of UAT, the solution provider shall ensure that the

solution is properly rendered on the device platforms mentioned in this

RFP. However, the solution provider shall ensure that the solution

works well on the latest version/device of the said device platforms


Ver 0.f of 73

throughout the entire project period

Technical Requirements

Bidder should understand that these are minimum indicative requirements and bidder is expected to

provide the best suitable technological specifications in its technical solution.

Web Development

Standards

The portal/website (mobile website and desktop website) should be developed

with the latest technology, using up-to-date and well established development

tools and software. The development approach should conform to the best

practices in the web site development and maintenance industry. Generally it

should ensure the following:

Adherence to commonly accepted standards and practices,

including W3C and GIGW compliance for both desktop and mobile

website

Obtain the mandatory “Safe-to-Host” certifications

Mobile website should be compliant to the latest versions of W3C

recommendation on ‘Mobile Web Best Practices’ and ‘Mobile Web

Initiative’

Development using latest website design technologies

Acceptability on all current user technology platforms; browsers,

operating systems, client systems

Technology The Web site should be developed using industry standard

configurable, extensible COTS solution along with content

management software and web analytics on all Operating System.

Must support both 64-bit and 32-bit architecture on server side

The portal should be developed based on AJAX, Flash Technologies

etc. to have a better user experience and faster response time.

Use of Web Application Framework, Web Content Management

System supported by a database, to deliver the site contents.

The portal should have automated deployment scripts for managing

applications, pages and other portal artifacts to reduce manual

intervention.

The website must be designed for continuous operation 24 hours a day,

7 days a week with express maintenance windows clearly defined

User interface Portal should support the page level and portal level configurable look-

and-feel

Portal should provide the consistent interface rendering across multiple

channels such as mobile, desktops, tablets etc. without the need to

segregate the development for each channel.

Portal should support dynamic menus driven by personalization and

complex business rules

Ability to persist user's session, including current location in portal,

across browser sessions

User should be able to customize the landing page layout as per his/her


Ver 0.f of 73

interest

Security &

Compliance

The vendor will provide for the following security features

Tools for monitoring web site security Protection against defacement,

hacking

Design should incorporate security features to protect the site from

Session Hijacking, SQL injection, Cross scripting, Denial of Service

etc.

Portal system should maintain a secure Password policy

Portal system should be secured by using Intrusion detection system

(IDS) and Intrusion prevention system (IPS) at network level.

Attain security certification for the new website from STQC or NIC,

CERT-IN through their empaneled vendors.

Website Hosting Website should be hosted in a Hosting Center in India. Further, at any given

point of time, all data generated through the Portal should reside in India.

Capacity and

Scalability

Portal should be able to scale as per the below parameters and on “as-per-

requirement” basis

Scaling of products

Scaling of SKUs

Scaling of customers

Peak transaction volume

Concurrent users

…………….

Payment Gateway It is envisaged that payment gateway would be integrated to the

website/portal during phase-II. But vendor should make sure that the

portal is developed initially in such a way to integrate the payment

gateway at later stage without any downtime for the website.

Integration should be smooth enough to avoid user observance.

COTS Product Requirements

The solution should be available Commercially Off-The-Shelf (COTS). The software application

should be readily deployable with or without configuration to suit the customer’s specific process

requirements and does not involve developing the application from scratch. COTS software shall be

implementable or deployable and maintainable by any other competent agency other than the

manufacturer or agency which has developed the COTS software. Proposed COTS software solution

shall also be available with complete transparency including operation manuals, help documents and

source code for the customized application.

Proposed COTS solution should comply with following essential criteria:

Bidder should have successfully implemented the proposed COTS product in any Public or

private sector organization before bidding for this project.

There should be at least 2 Public or private entities in India or outside who are using the

proposed COTS product for last 3 years.

The COTS OEM should have support & development centers in India having at least 100

developers/product support team.

The COTS Product should have been implemented and maintained by at least 2 System

Integrators in India.


Ver 0.f of 73

The COTS Solution should be platform independent, should support all major Operating

System and should support industry standard database management systems.

2. Content management system

IBEF will be responsible for creating content in terms of product list, product description, product

videos etc. The bidder is expected to deploy easy to use content creation and management tool.

Vendor will need to update, upload and publish content given/approved by IBEF. IBEF will need to

have access to CMS in order to update, upload and publish content if required.

Functional Requirements

Rich Media

Content

Website/portal should support content in form of text, video, animation,

product manuals, product images etc.

Content scheduling

for deployment

System should be able to provide the following functionalities

Version Control

Push or schedule content from staging site to production site

User Access control Provision to add/modify new/existing user in system

Ability to assign necessary privileges as per the user access policy to

different users

Ability to access profiles in system and assign the same to user

Wish List and gift

registry

Permanent Shopping List

Gift Registry

Gift Wrapping

Deliver On Specified Date

Share List Via Email or Social

Gift Certificates (optional)

Search Site search capability

Type ahead search with product display

Administrative Control of Product Data Fields Used in Search

Administration and

management

Comprehensive Content Management System

Responsive Design Support

Mobile Design Support

CMS Permission Levels

Ease of Use for Non-Technical Users

HTML/CSS(Cascading Style Sheets)/JavaScript Access for Technical

Users

Ability to manage Meta Content at all levels

Version control tool(s) for content management

Content

Capabilities

Unlimited Categories

Unlimited Subcategories

Data Driven Classification/Attributes(Filtering)

Shop by Brand

Unique Category Pages

Unique Subcategory Pages


Ver 0.f of 73

Unique Brand Pages

Unique Product Listing Pages

Unique Product Detail Pages

Featured Content Site wide

Featured Content Page Specific

Automated Cross-sell/Upsell based on purchase behavior

Automated Cross-sell/Upsell based on views

Built-in rates and reviews

Auto image sizing

Alternate images

Built-in image zooming

Social Networking

Social Connect

Social Login

Social Sharing

Built-in blog functionality

Built-in forum capabilities

Built-in Q&A

SEO capabilities SEO should be a built-in capability and based on the following contents of the

website

Product Descriptions

Product Images

Videos

Product Manuals

Customer Reviews

Product Ratings

Blogs

Landing Pages

Natural Language URLs

Page and Section Titles and Tags

Meta Content at Every Level

Alt tags on images and graphics

Preservation of content based on customer searches, to auto generate

content and relevant search results

Technical Requirements

Multi-site

management

To allow content across multiple sites to be easily managed through a single

interface. Contents / files / multimedia content can be shared across all the

websites.

Content

management

Built-in workflow support for content management (creation,

approval, updation, publication etc.)

Easy to use content creation and management tool for non-technical

business users


Ver 0.f of 73

Should have ability to manage content metadata via portal

Access Control Access control tied to portal access Control

Ability to manage content, such as availability, on/off times,

accessibility based on security or authorization rules.

Store shared images, videos, files and data in one location for easy

access. Create user and role-level access to individual directories.

3. Mobile Application Development

Native mobile application shall be developed for the following platforms: Apple App Store and

Android Market, Windows Mobile.

Applications must be strictly hosted at their official platform sites, i.e., at Apple App Store, Android

Market, to ensure credibility and trust for a user.

The scope of work broadly covers design, development, testing, and hosting at platform including

approval by platform owner & updates. The application needs to be updated as per the changes in

corresponding website application till the contract period validity. Mobile application needs to be

abreast with the changes in website. The applications shall be provided free of cost at the respective

platform portal perpetually and shall be clearly marked as the official apps for Brand India portal and

should be optimized for the platform it is being run on.

The username and password credentials under which these applications are submitted to the

corresponding platforms shall be exclusive for IBEF and property of IBEF; the solution provider must

submit the credentials to IBEF on-demand and on termination/completion of the work. The mobile

applications should be built on object oriented programming and open standards.

The solution provider shall share the complete information about the Native apps, as available on the

platform accounts (download statistics, email addresses of users etc.), with IBEF as part of the

quarterly summarized SLA compliance and activities report. Additionally, the solution provider shall

make the same information available in softcopy on ad-hoc request basis (at-most once per month).

The solution provider shall conduct the UAT of Mobile web using the native/default browser and at

the native/ default screen resolution. It should be noted that the procurement and ownership of these

devices for UAT or other testing purposes shall be solely solution provider’s responsibility.

Note:

a) The UAT for mobile apps and Mobile websites shall be carried out by IBEF; however SI shall

provide the testing environment and test cases and assume the overall responsibility of conducting

UAT.

b) The Mobile App shall be delivered in English Language to begin with. It shall be expanded to

cover other languages (for which web portal is available)

c) Analytics shall also be provided for both Mobile Apps and Mobile websites

4. Infrastructure Services

The selected bidder shall be responsible for hosting the Brand India B2B Portal, Mobile Website and

Mobile App for IBEF. The hosting would be done on the cloud environment servers in India only and


Ver 0.f of 73

bidder would be responsible for arranging all the necessary software, hardware, licenses etc. for

hosting the portal, mobile website and mobile App.

The proposed Hosting solution should be centralized on ASP (Application Service Provider)

ALL Hosted Solution Model

Hosting must be done in India only.

The proposed portal solution should maintain the SLA’s define and specified in this

document.

5. Social Media Integration

I. Option for creation and maintenance of multiple blogs and/or newsgroups

II. Ability to use current interactive and social networking mediums such as Facebook, Twitter, and

RSS feeds, as well as flexibility to add these types of features in the future

III. Create reviews quickly and easily. Assign indexing terms to improve SEO and enable topic

categorization.

2.9 Testing and user acceptance Test (UAT)

i. The IA shall be responsible for making all necessary arrangements for testing (unit, functional,

integration, and user acceptance) including the preparation of test data, scripts where necessary

and deployment of the same. The test data shall be comprehensive and address all scenarios

identified in the test cases. The IA shall create test reports from testing activities and submit to

IBEF on request.

ii. IA will be responsible for testing of each unit of the functional modules separately before

integrating them. After successful unit testing of all components, the IA shall conduct full-

fledged integration testing, system testing, functional testing, performance testing (including load

and stress), scalability testing and security testing in accordance with the approved Test Plans.

Integration testing shall cover both cross-functional integration points, as well as end-to-end

processes. This would also include development of exhaustive testing scenarios and test scripts.

Functional testing will be led by the IA’s domain experts and the IA shall also ensure full

participation of IBEF’s domain experts during this exercise. IA shall ensure a clear delineation of

testing and development/implementation environments for enabling efficient monitoring and

timely closure of bugs and defects.

iii. IA shall develop comprehensive test plans and test scripts for conducting application testing for

its functionality, performance, scalability, security etc. . The test data shall be comprehensive and

address all scenarios identified in the test cases. The SP shall create test reports from testing

activities and submit to IBEF on request.

iv. IA shall conduct the load tests with an objective to determine the response times of various time

critical transactions and business processes and ensure that they are within documented

expectations (or Service Level Agreements - SLAs). IA shall conduct the stress tests with an


Ver 0.f of 73

objective to determine the system’s behavior when its resources are limited and to check whether

the behavior is well within the defined parameters.

v. Load, scalability and Stress Testing would be conducted prior to submitting the application for

User Acceptance Test (UAT), once the System Integration Testing has been conducted

successfully. The IA should use suitable simulation tools in accordance with the agreed test

procedures keeping in view IBEF’s projected future load of transactional users as proposed by

The IA and agreed by IBEF.

vi. Test Plans for UAT would be prepared / updated by the IA in collaboration with the IBEF. The

IA shall conduct the UAT in the cloud environment; The IA will plan all aspects of UAT

(including the preparation of test data) and obtain required assistance from IBEF to ensure its

success. IBEF will identify the users for different modules or services who would be carrying out

the UAT. The IA would make the necessary changes to the application to ensure that the

application successfully goes through UAT.

vii. Further any changes to the application suite during the operations and maintenance phase will be

released to production only after successful regression testing, including automated testing where

necessary, of the application. The regression test plans shall be provided in advance to IBEF for

approval.

2.10 Key Personnel

Staffing shall consist of, at a minimum, the following categories:

1) Project Manager

The profile of the Project Manager should be as follows:

Minimum Educational Qualification

a) B.E. /B.Tech/MCA with MBA/M.Tech/M.E. or equivalent

Desired Skills & Experience

a) Overall experience of 10 years in System Integration

b) Proven experience in handing large team of over 20 people

c) At least 4 years of work experience of working on project (s) involving Portal Development.

d) Knowledge in latest trends, technology and process related to new Portal development and

management

e) Should have experience in interpreting and monitoring of SLAs at various levels

f) Should have ability to lead, motivate and direct the team to achieve the business objectives.

2) UI designer (Portal) and (Mobile)


a) B.E. /B.Tech/MCA or equivalent


a) Front end Technologies: In-depth knowledge of HTML5 and CSS3, and at least JavaScript.

b) Conceptual understanding of User Interface Design and the Design Process.


Ver 0.f of 73

c) Excellent time-management, multi-tasking, and communication skills.

d) Capable of juggling multiple projects and related complexities at the same time.

Desired Experience

e) A minimum of 5 years of formal industry/professional experience as a web/mobile designer.

f) Good eye for aesthetics: layout, grid systems, color theory and typography.

g) Strong understanding of mobile platforms, particularly iOS, Android and Windows Phone.

h) Understanding of the limitations of web and mobile, with approaches/ideas to flex those

boundaries.

i) Candidate must absolutely be in sync with recent design standards and trends.

3) Portal Developer


a) B.E. /B.Tech/MCA or equivalent


a) 7 years of work experience in Portal Development and Maintenance

b) Ability to interface with customers on the architecture and design aspects of the project

c) Experience on the use of portal development best practices, tools and technologies.

d) Ability to identify the Co-existence and Interoperability Requirements

4) Performance Expert


a) B.E. /B.Tech/MC or equivalent


a) Experience to Identify performance, reliability, security & integration bottlenecks and suggest

recommendations

b) Experience on the portal development best practices, tools and technologies related to

performance.

c) Experience in SLA based delivery based on performance metrics

5) SME- e-commerce Portal Development


b) B.E. /B.Tech./MCA or equivalent


a) At least 10 years of work experience in Portal Development and Maintenance in India

b) Well conversant with latest trends, technologies and features on portal development

(preferably in the e-commerce sector)

2.11 Provisioning of client infrastructure and cloud services

Client Infrastructure

1. The System Integrator shall setup and maintain the required software and the infrastructure

for Portal’s staging environment, testing, content management support from IBEF and

training activities within IBEF premises (for 5 users at least); and for any other activities that

may be carried out of IBEF premises such as issue management (Issue Tracker), product

repository (content management tool), etc. For this the bidder is required to supply at least 5

desktops and 5 UPS with minimum configuration as mentioned below:


Ver 0.f of 73

Minimum Desktop Configuration

CPU Intel or AMD

Operating System latest version of Microsoft windows

Enterprise application including word, excel, power point, anti-virus, firewall

No of Cores Minimum 2

CPU Speed Minimum 2.33 GHz or higher

Chipset Compatible to supplied CPU

Cache Memory Minimum 2 MB L2 or higher

FSB Minimum 800 MHz or Higher

Memory 2 GB DDR2 RAM Min. 667MHz Upgradable up to 4GB

HDD 250 GB SATA 7200rpm HDD

Monitor Min. 17" Colour SVGA Non -Interlaced TFT Monitor (with TCO‟03

Certification)

Keyboard Min. 104 Keys OEM Mechanical Key Board or TVSE Gold or

equivalent

Mouse Two Button Optical Scroll Mouse

Optical Drive Internal DVD-RW Drive

Cabinet Micro-ATX/ Desktop

Ports Min. 6 USB (2 In front), 1 Serial, 1 Parallel, PS/2 (For Keyboard &

Mouse)

2. Any other software required for operation and maintenance

3. The SP shall have to do the required site preparation that includes civil works and electrical

cabling for the systems to be installed at these offices

4. Ensuring that the supplied equipment supports the intended system hardware, operating

system and other software. Any problems encountered in the installation of the

hardware/software because of hardware/software incompatibility shall be the responsibility of

the IA.

5. All the systems shall be supported by UPS in case of power failure

Cloud Services

i. The SP shall be responsible for provisioning of the necessary underlying software, infrastructure,

and data center services for deployment of the IBEF portal solution. The infrastructure required

for hosting the IBEF solution shall be provisioned as IaaS from a cloud service provider. Where

applicable & available with the cloud service provider, the SP may also leverage the required

system software (along with the necessary ATS as per the requirements of the RFP) as a service.

ii. For all other system software that is not procured as a service from the Cloud Service Provider,

the SP shall procure, implement and maintain the same along with the ATS from the OEM as per

the requirements in the RFP. For such system software,

a. Supply tools, accessories and documentation. Tools and accessories shall be part of the

offered solution.


Ver 0.f of 73

b. Procure and Supply the Annual Technical Support from the product OEMs for the contract

period as covered in the O&M support scope.

c. Product Documentation to include hard copies and soft copies (sets of two numbers) to be

supplied along with the product licenses and associated software solution and shall include

but not limited to the following:-

1. Technical manuals.

2. Installation guides.

3. User manuals.

4. System administrator manuals.

5. Toolkit guides and Troubleshooting guides.

d. All documents mentioned above or any other standard documentation for the products will

be included in the cost of the license.

e. SP shall Procure and Supply user licenses (if required) for transaction, technical and

system administration for the offered product.

iii. The SP shall be completely responsible for the sourcing, installation, commissioning, testing and

certification of the necessary software licenses and infrastructure required to deploy the Solution

on the Cloud offering at the Primary Data Centre and the Disaster Recovery Centre (DRC). SP

shall ensure that support and maintenance, performance and up-time levels are compliant with

SLAs.

iv. Service Provider shall be responsible for adequately sizing the necessary compute, memory, and

storage required, building the redundancy into the architecture (including storage), and load

balancing to meet the service levels mentioned in the RFP. While the initial sizing &

provisioning of the underlying infrastructure (including the system software available as service)

may be carried out for the first year; subsequently, it is expected that the Service Provider based

on the growth in the user load (peak and non-peak periods; year-on-year increase) will scale up

or scale down the compute, memory, and storage requirements to support the scalability and

performance requirements of the solution and meet the SLAs. SP is expected to carry out the

capacity planning in advance to identify & provision, where necessary, the additional capacity to

meet the user growth and / or the peak load requirements to support the scalability and

performance requirements of the solution. There should not be any constraints on the services

(ex, limit on sessions, blocking the non-critical services,..) during the Peak Period. SP shall

ensure that effective Remote Management features exist in solution so that issues can be

addressed by the SI in a timely and effective manner. All technical specifications, documentation

generated during design, installation and commissioning phase shall be provided to the IBEF.

v. The public facing services shall be deployed in a zone (DMZ) different from the application

services. The Database nodes (RDBMS) should be in a separate zone with higher security layer.

vi. In addition to the production environment in the Primary DC, the Service Provider should setup

the development, test (30% of the production environment) and training (10% of the production

environment) environments on the cloud at the Primary Data Center Facility. The environments

should be a miniature of the production environment. The environments should be a secluded

environment in a different VLAN than the production environment and setup such that users of

the environments are in separate networks.

vii. In addition to the Primary DC, SP is responsible for Disaster Recovery Center Services so as to

ensure continuity of operations in the event of failure of primary data center and meet the

RPO(Recovery Point Objective) and RTO(Recovery Time Objective) requirements. RPO should

be less than or equal to 2 hours and RTO shall be less than or equal to 4 hours. The key

transaction data shall have RPO of 15 minutes. However, during the change from DC to DRC or

vice-versa (regular planned changes), there should not be any data loss. There shall be


Ver 0.f of 73

asynchronous replication of data between Primary DC and DRDC and SP shall be responsible for

sizing and providing the DC-DR replication link so as to meet the RTO and the RPO

requirements.

viii. The Primary DC and the DRC should be in different seismic zones. The disaster recovery site

shall have the similar environment (physical & IT), processes, and controls (security,..) as that of

the primary data centre. During normal operations, the Primary Data Center will serve the

requests. The Disaster Recovery Site will not be performing any work but will remain on

standby. During this period, the compute environment for the application in DR shall be available

but with minimum possible compute resources required for a functional DR as per the solution

offered. The application environment shall be installed and ready for use. DR Database Storage

shall be replicated on an ongoing basis and shall be available in full (100% of the PDC) as per

designed RTO/RPO and replication strategy. The storage should be 100% of the capacity of the

Primary Data centre site.

ix. In the event of a site failover or switchover, DR site will take over the active role, and all

requests will be routed through that site. Application data and application states will be replicated

between data centers so that when an outage occurs, failover to the surviving data center can be

accomplished within the specified RTO. This is the period during which the Compute

environment for the application shall be equivalent to DC. The installed application instance and

the database shall be usable and the same SLAs as DC shall be provided. The use of this Full

Compute DR environment can be for specific periods during a year for the purposes of DC

failure or DR Drills or DC maintenance. The Database and storage shall be of full capacity and

the licenses and security shall be for full infrastructure. The bandwidth at the DR shall be scaled

to the level of Data center. Internal and external users of IBEF should be routed seamlessly from

DC site to DR site. SI shall conduct DR trail for two days at the interval of every six months of

operation wherein the Primary DC has to be deactivated and complete operations shall be carried

out from the DR Site. However, during the change from DC to DRC or vice-versa (regular

planned changes), there should not be any data loss. SP shall clearly define the procedure for

announcing DR based on the proposed DR solution. SP shall also clearly specify the situations in

which disaster shall be announced along with the implications of disaster and the time frame

required for migrating to DR. SI shall plan all the activities to be carried out during the Disaster

Trial and issue a notice to the IBEF at least two weeks before such trial.

x. Expected data size is approximately 2 TB for the first year. Data is expected to grow at the rate

of 30% per year. The data size is indicative. SP shall carry out actual assessment at the time of

project implementation.

Detailed requirements with respect to the offerings of the cloud service provider are provided under

Annexure I.

Enterprise Monitoring System

IA shall design, procure & implement the necessary modules of the Enterprise Monitoring System

including any additional tools required for measuring and monitoring each of the Service Levels

prescribed in this RFP. The EMS shall at a minimum provide the service level management,

reporting, End-User Response Time Monitoring, Application Transaction Performance Monitoring


Ver 0.f of 73

System, and network management features. It is expected that the infrastructure management &

monitoring reports would be provided by the CSP.

The EMS implemented by IA shall be audited by an agency nominated by IBEF. The SP shall

provide complete access to the SLA Reporting System including the manner in which the

configuration of the system has been done, SRS and system manuals. Full access should be provided

to generate reports from the systems for IBEF officials or its nominees. IA shall design the system to

provide an independent and real-time access to the SLA Monitoring System, any generated logs, or

the underlying components such as databases, servers to IBEF or its nominated agency.

2.12 Operation and Maintenance post Implementation Services

IA shall be fully responsible for operations and maintenance of the Brand India portal system, hosting

center and disaster recovery center, and any other component or facility being established by IA as

part of this project for a period of 3 years from the go-live date.

The service provider will get a 3 month SLA holiday, i.e., there will not be any SLA related penalties

for the 1st quarter payment. However, the Service Provider has to monitor and report on the

applicable SLAs to IBEF during this period. The SP shall help IBEF users to correct any errors

incurred while generating monthly and quarterly reports or any other errors. The SP shall update the

user manuals and configuration manuals if required.

The following sections detail the O&M requirements:

1. Web Application Management

The IA is responsible for the maintenance of the IBEF portal solution so as to meet the desired service

levels. The services will include activities such as:

a. During the support period, IA shall be completely responsible for the defect free functioning of

the application software and shall resolve any issues including bug fixing, improvements in

presentation and/or functionality and others within a duration agreed between IBEF and the IA

in relation to such a work.

b. IA shall provide the latest updates, patches/fixes, version upgrades relevant for the solution

components.

c. IA shall be responsible for software version management and software documentation

management reflecting current features and functionality of the solution.

d. Carry out any minor enhancements/modifications to the application that are incidental to proper

and complete working of the application

e. Tuning of application, databases, third party software’s and any other components provided as

part of the solution to optimize the performance

f. SP shall provide patches to the licensed software including the operating system,

databases and other applications.

g. Update and maintain all project documents

h. End user support in case of technical difficulties in use of the software, answering

procedural questions, providing recovery and backup information, and any other

requirement that may be incidental/ancillary to the complete usage of the application


Ver 0.f of 73

i. User ID and group management services.

j. Maintain access controls to protect and limit access to the authorized End Users of the

Application

k. Administrative support for user registration, creating and maintaining user profiles,

granting user access and authorization, providing ongoing user password support,

announcing and providing networking services for users and providing administrative

support for directory and e-mail servers

l. Release Management for the interim releases of the application

m. Routine functional changes that include user and access management, creating new

report formats, and configuration of reports. Some of the indicative changes include:

1. Introduction of new forms, new workflows or modification in existing

workflow for existing services

2. Addition or modification of validations in e-forms(if any)

3. Modifications (addition of new fields, removal of fields, modification of

levels of approval, processing logic, approval logic, addition of attachment

requirement etc.) to e-forms

4. Configuration changes to improve the performance & efficiency of the

system

n. Changes in application or development of application modules for strategic control &

monitoring of system for ministry or appointed body like PMU (Program Monitoring/

Management Unit)

2. Annual Technical Support (ATS) for all the licensed software

As part of the ATS services for all the licensed software, SP shall provide:

i. The SP shall provide ATS for all the licensed software during the contract period.

ii. The ATS should be valid for a period of at least one year at the time of expiry of the contract.

However, with respect to the validity for a period of at least one year at the time of expiry of

the contract, the bidders are only required to ensure that such a support is available but are not

required to cost for the same in their commercials.

iii. SP shall maintain data regarding entitlement for software upgrades, enhancements, refreshes,

replacements and maintenance.

iv. If the Operating System or additional copies of Operating System are required to be installed /

reinstalled / de-installed, the same should be done as part of ATS.

v. SP should carry out any requisite adjustments / changes in the configuration for implementing

different versions of Application Software.

vi. Updates/Upgrades/New releases/New versions. The SP shall provide from time to time the

Updates/Upgrades/New releases/New versions of the software and operating systems as

required. The SP should provide free upgrades, updates & patches of the software and tools as

and when released by OEM at no extra cost to IBEF. The SP will implement from time to

time the Updates/Upgrades/New releases/New versions of the software and operating systems

as required after necessary approvals from IBEF about the same

vii. SP shall provide and apply regular patches to the licensed software including the software,

operating system, databases and other applications.

viii. Software License Management. The SP shall provide for software license management and

control. SP shall maintain data regarding entitlement for software upgrades, enhancements,

refreshes, replacements, and maintenance. SP should perform periodic audits to measure

license compliance against the number of valid End User software licenses consistent with the

terms and conditions of site license agreements, volume purchase agreements, and other


Ver 0.f of 73

mutually agreed upon licensed software terms and conditions and report to State on any

exceptions to SP terms and conditions, to the extent such exceptions are discovered.

ix. SP shall provide complete manufacturer’s technical support for all the licensed software

problems and/or questions, technical guidance, defect and non-defect related issues. SP shall

provide a single-point-of-contact for software support and provide licensed software support

including but not limited to problem tracking, problem source identification, problem impact

(severity) determination, bypass and recovery support, problem resolution, and management

reporting.

x. The manufacturer’s technical support shall at a minimum include online technical support and

telephone support during the IBEF’s business hours (Business hours of IBEF will be from

0830 hours to 2030 hours on all days (Mon-Sun)) with access for IBEF and SP to the

manufacturer’s technical support staff to provide a maximum of 4 hour response turnaround

time. There should not be any limits on the number of incidents reported to the manufacturer.

IBEF shall have access to the online support and tools provided by the manufacturer. IBEF

shall also have 24x7 access to a variety of technical resources including the manufacturer’s

knowledge base with complete collections of technical articles.

xi. Software Distribution. SP shall formulate a distribution plan prior to rollout and

distribute/install the licensed and tested software as per the plan

xii. The ATS Services will cover, all product upgrades, modifications, and enhancements

xiii. The SP shall undertake regular preventive maintenance of the licensed software

3. Infrastructure Management Services

a) This includes the design of an appropriate System Administration policy with precise

definition of duties and adequate segregation of responsibilities and obtaining the approval for

the same from IBEF. System Administration includes the following activities:

Overall management and administration of infrastructure solution including servers,

networking & security components, storage solution and others.

Performance tuning of the system as may be needed to enhance system’s performance

and comply with SLA requirements on a continuous basis.

Security management including monitoring security and intrusions into the system.

Monitor and track server and network performance and take corrective actions to

optimize the performance on a daily basis.

Escalation and coordination with other vendors for problem resolution wherever

required.

System administration tasks such as managing the access control system, creating and

managing users and other related work.

Data storage management activities including regular backup, restore and archival

activities.

Support to system users with respect to attending to their requests for assistance in

usage and management of the application.

b) The IA undertakes to ensure that regular back-ups of data are taken and maintained safely.

c) The IA shall maintain the adequate stocks of spares to meet the requirements.

d) Whenever a component has to be replaced because of technical, functional, manufacturing or

any other problem, it shall be replaced with a component of the same make and configuration.

In case the component of same make and configuration is not available, the replacement shall

confirm to open standards and shall be of a higher configuration.

e) Other important activities shall include but not limited to:

Daily maintenance of system configuration

Implementation of system security features


Ver 0.f of 73

Overall security of the network

Day-to-day disk space management

Tracking the servers’ performance and taking remedial and preventive actions in case

of problems

Proper upkeep of storage media for taking backups

4. Continuous Improvement/Enhancement

The system needs to be continually upgraded to meet the industry standards in respect of

websites/portals, content management systems, search engine capabilities, information management,

analytics, networks and security. IA shall be also responsible for improvements/modifications to be

able to take advantage of improvements expected in the future in the online transaction/retail system.

5. Warranty Support Services

IA shall provide comprehensive warranty for all IT and non-IT infrastructure, provided as part of the

project, for a period of 3 years from the Go-live date.

As part of the warranty/AMC services SP shall provide:

i. AMC for hardware should be valid for a period of at least one year at the time of expiry of the

contract. In case any of the hardware is reaching end of life and the SP is not able to procure

the AMC services, such hardware shall be replaced with the then current infrastructure to

meet the above requirement.

ii. SP shall provide a comprehensive warranty and on-site free service warranty for all the new

hardware procured as part of this RFP

iii. SP shall provide OEM warranty (minimum 1 year) and comprehensive AMC support (after

the expiry of warranty) for the entire contract period. The comprehensive AMC should

include provision and replacement of all spares and parts, free of cost during the entire period.

iv. Where such a support for any component(s) is not available or ends during the contract

period, the component(s) shall be replaced with latest available component(s) in the market

with similar or better specifications at least 3 months before the end of support period.

v. SP shall provide the comprehensive manufacturer's warranty in respect of proper design,

quality and workmanship of all hardware, equipment, accessories etc. covered by the RFP. SP

must warrant all hardware, equipment, accessories, spare parts, software etc. procured and

implemented as per this RFP against any manufacturing defects during the warranty period.

vi. SP shall provide the performance warranty in respect of performance of the installed

hardware and software to meet the performance requirements and service levels in the RFP.

vii. During the warranty/AMC period SP shall maintain the systems and repair / replace at the

installed site, at no charge to IBEF, all defective components that are brought to the SP's

notice.

viii. The SP shall as far as possible repair the equipment at site.

ix. In case any hard disk drive of any client machine is replaced during warranty / AMC the

unserviceable HDD will be property of IBEF and will not be returned to SP. Warranty/AMC

should not become void, if IBEF buys, any other supplemental hardware from a third party

and installs it within these machines under intimation to the SP. However, the warranty will

not apply to such supplemental hardware items installed.

x. SP shall carry out Preventive Maintenance (PM), including cleaning of interior and exterior,

of all hardware and testing for virus, if any, and should maintain proper records at each site

for such PM. Failure to carry out such PM will be a breach of warranty/AMC and the

warranty/AMC period will be extended by the period of delay in PM. PM envisages all


Ver 0.f of 73

activities require to be undertaken for good upkeep of hardware. It also includes the end user

equipment or client side infrastructure.

xi. SP shall monitor warranties/AMCs to check adherence to preventive and repair maintenance

terms and conditions.

xii. SP shall ensure that the warranty/AMC complies with the agreed Technical Standards,

Security Requirements, Operating Procedures, and Recovery Procedures.

xiii. SP shall have to stock and provide adequate onsite and offsite spare parts and spare

component to ensure that the uptime commitment as per SLA is met.

xiv. Any component that is reported to be down on a given date should be either fully repaired or

replaced by temporary substitute (of equivalent configuration) within the time frame indicated

in the Service Level Agreement (SLA).

xv. SP shall develop and maintain an inventory database to include the registered hardware

warranties/AMCs

6. Support to Testing & Certification by a Third Party or any other Agency appointed by

IBEF

IA shall provide necessary support to the Third Party Audit Agency or any other agency/ group

appointed by IBEF for acceptance testing and certification of IA’s deliverables. This includes

providing access to the necessary systems, documentation etc. to the audit agency.

The IA needs to address the gaps identified in Audit & Certification process.

2.13 Service Level Agreement

Service Level Agreement (SLA) defines the terms of the Successful bidder's responsibility in ensuring

the timely delivery of the deliverables and provisioning of all required services while monitoring the

performance of the same to effectively comply with the performance levels for the duration of the

contract based on the agreed Performance Indicators as detailed in the Agreement. This section

defines various Service Level Indicators which will be considered by IBEF in the Service Level

Agreement with Successful bidder. The services provided by the successful bidder shall be reviewed

by IBEF to ensure the effectiveness of the SLA.

The following measurements and targets shall be used to track and report performance on a regular

basis. The targets shown in the following table are applicable for the Contract Period. Please note that

the Successful Bidder should provide comprehensive, end-to-end service to maintain the hardware

and software components, including replacement of the equipment in case of physical damage. No

reason shall be entertained (unless those mentioned in Force Majeure) in case of non-availability of

required services and appropriate penalty shall be levied.

2.13.1 SLA Monitoring System

The SLA Monitoring function is important because the payments to the vendor shall be linked to a

measurement of the SLA parameters defined in this RFP. In this context, the SLA Monitoring system

should:


Ver 0.f of 73

a) Be integrated with the application software component of portal software that measures

performance of system against the following SLA parameters:

Response times of Portal (desktop, mobile etc.)

Transaction handling capacity of application server in terms of number of concurrent connects

Uptime of Portal (desktop, mobile etc.)

Meantime for restoration of Portal

b) Compile the performance statistics from all the IT systems involved and compare it with the SLA

metrics laid down in this RFP or as mutually agreed between the IBEF and the vendor

c) Be under the control of the IBEF, so as to ensure that it is in a trusted environment.

d) Be subject to random third party audit to vouchsafe its accuracy, reliability and integrity.

The performance indicators shall be tracked using Analytics & Reporting module of the

website/portal.

IBEF shall issue a quarterly SLA Satisfaction Certificate on adherence/non-adherence to SLA

parameters and penalty deductions if any. The application of these penalties shall begin after 3 months

of go-live of the website. The overall penalty of all SLAs shall be levied up to a maximum of 20% of

monthly bill amount. However, if the maximum penalty limit is reached continuously for Four (4)

billing cycles then the cap may be removed by the IBEF and actual penalty may be charged.

Technical Service Level Requirements

a. Portal Uptime/Availability

Objective To ensure that not more than 0.5% of time portal is unavailable to the user

Definition The amount of time services from the portal were available to the users. It

excludes any and every form of downtime which might prevent a user to access

the website

Data Capture Measured over a leased circuit or equivalent at 1 Mbps bandwidth over a period

of one month.

Measurement interval Daily

Reporting period Quarterly

Calculation of availability:

{[Scheduled Operation Time – (Scheduled Maintenance Time + Customer introduced

Outage + Downtime Due to Force Majeure)] / Scheduled Operation Time} *100 %

Scheduled Maintenance Time should not be more than one hour per month and client should be

informed at least 48 hours in advance and subsequent approval / acceptance should be taken from

customer.

Service Level

Sl. No System availability value for month Penalty

1. >= 99.5% Nil

2. >= 99% but < 99.5% 10% of monthly billed amount

3. >= 99.5% but < 99% 20% of monthly bill amount

b. Infrastructure Performance


Ver 0.f of 73

Objective To ensure that system is maintained and managed at optimum level without

degrading the performance.

Definition This is measured as: CPU processing power, memory, storage, network, internet

bandwidth and monitoring of the services

Data capture CPU/IO/Memory utilization of the servers


Reporting period Quarterly

Each occurrence where the peak CPU IO/Memory utilization of any server crosses 70% and stays

above 70% for time more than 30 minutes will be treated as one (1) instance

Service Level

Sl. No. Number of instances occurred

monthly

Penalty

1 >0 & <=3 10% of monthly bill value

2 >3 20% of monthly bill value

c. Portal Response Time in providing informational services

Objective This SLA is to ensure that website is responsive to the user activity.

Definition This is measured as the response time of the webpages of the portal.

Data capture Response time measurement using broadband as well as dial up connection.

Audit conducted by third part administrators based on sample and also

random audit process


Reporting period Monthly

Service Level

Sl. No. Response time Penalty

1 <=3 sec Nil

2 >3 sec<=5 sec 10% of monthly bill value

2 >5 sec<=7sec 15% of monthly bill value

3 >7Sec<=10sec 20% of monthly bill value

d. Content Management SLAs

i. Content upload to Portal for all languages

S.No. Activity Service Level Severity

1. Content once approved by the IBEF

should be uploaded to the portal.

3 Business hours High

ii. Content Removal

S.No. Activity Service Level Severity

1. Objectionable content removable 1 Business Hour High

2. Content removal-Others 8 Business hours Medium


Ver 0.f of 73

Following penalties will be levied on the basis of non-achievement of SLA.

S.No. Type of instance Penalty

(Delay of every hour would attract a penalty per hour as per the

following)

1. Content Upload Penalty = 2 X Per hour Penalty (Per hour penalty is INR 1000)

2. Content Removal Severity= High

Penalty = 2 X Per hour Penalty (Per hour penalty is INR 1000)

Severity= Medium

Penalty = 1 X Per hour Penalty (Per hour penalty is INR 1000)

Operational Service Level Requirements

Scope of work

Bug fixes, minor changes/enhancements

Minor enhancements (the usual run-of-the-mill enhancements and not the ones identified as part

of Continuous Improvement).

Change request management based on feedback from the users/ IBEF.

Routine functional changes related to content management

Updating and maintenance of all project documents

Severity Level

The severity level of a service call is defined by the extent of impact the problem has on the overall

portal solution performance.

S1: Business can't Work - Issue in which significant portion of business is non-operational and failure

to fix the issue have significant impact on the ability of user’s to perform business transactions.

S2: Application is not down but there is an issue affecting small number of users or customers.

Acceptable work around is available.

S3: Application is not down but some operational/non-operational issues with no immediate impact

but needs to be fixed to avoid service degradation in near future.

S3: Functionality enhancement and/or support for modifications or maintenance of source code,

training documentation or user documentation

Priority level

The priority level of a service call is defined by the priority in which the calls would be handled in

case of queuing.

P1- High Priority: Total failure of critical systems, services, applications or underlying hardware,

Hosting center failure, Network failure, External attack on network

Immediate investigation and status reports.

P2- Medium Priority: Partial failure of critical systems, services, applications or underlying hardware

failure in standard operating procedures, Non-critical hardware defect, Operating system failure of

backup system,

Hourly reporting of investigations.

P3- Low Priority: Partial failure of non-critical services or applications, Standard operating

procedures, Routine password changes, Errors in hosted content


Ver 0.f of 73

Report of initial investigations within four hours

Indicative response time to resolve reported problem

Severity/Priority P1 P2 P3

S1 2Hrs 4Hrs 6Hrs

S2 4Hrs 6Hrs 8Hrs

S3 6Hrs 8Hrs 10Hrs

S4 8Hrs 10Hrs 12Hrs

Failing to achieve the above service level will be considered as one instance. Following penalties will

be levied on the basis of number of instances occurring in a Month.

The IA shall provide service as per the following standards –

Following penalties will be levied on the basis of non-achievement of SLA.

S.No. Priority Type Penalty

(Delay of every hour would attract a penalty per hour as per the

following)

1. P1 Penalty = 3 X Per hour Penalty (Per hour penalty is INR 1000)



2.14 Project Timelines and Deliverables The overall implementation of the Brand India portal has been envisaged to be of 32 weeks. The IA

needs to adhere to the timelines as specified in the table below:

2.14.1 Milestones and Timelines

S.No. Milestones Time for completion

Design, Development, Testing and Implementation of web portal application

Priority

Type

Performance baseline

P1 All calls resolved within specified response time

P2 At least 99.5 % calls resolved within specified

response time

P3 At least 98 % calls resolved within specified

response time


Ver 0.f of 73

1. Requirements Study T+4 Weeks

2. Preparation and submission of System Requirement

Specification (SRS)

T+10 Weeks

3. Review & Sign-off on SRS T+11 Weeks

4. Mobile Website prototype T+19 Weeks

5. Mobile Application Prototype T+19 Weeks

6. Design, Development, Testing of web (Desktop, mobile)

portal

T+28 Weeks

7. Design, Development, Testing of Mobile Application T+28 Weeks

8. Portal (Desktop, mobile) Development & Hosting T+29 Weeks

9. Development of System User Manual & Technical Manual T+30 Weeks

10. Acceptance Testing & Certification of IBEF or third party

agency nominated by IBEF

T+31 Weeks

Providing Hosting center and DR center services

11. Departmental approval of Hosting Center, BCP/DR Center T+8 Weeks

12. Providing Hosting services T+20 Weeks

13. Providing Disaster Recovery (DS) services T+28 Weeks

Capacity Building

14. Development of Training Plan & Curriculum T+28 Weeks

15. Development of Training Material T+28 Weeks

16. Training to identified key stake holders T+28 Weeks

Help Desk

17. Preparation of FAQ document T+28 Weeks

18. Operationalization of Help Desk T+30 Weeks

Go-Live

19. Final launch of all the three applications

Desktop, mobile website and Mobile application

T+ 32 Weeks

“G”

Support & Maintenance

20. Overall portal and help center maintenance and support G+3 Years

2.14.2 Project Deliverables

The IA has to deliver the following deliverables to IBEF as part of an assurance to fulfil the

obligations under the SLA. The table given below may not be exhaustive and IA is responsible to

provide all those deliverables which may be specified in this RFP but not listed here and those agreed

by IA in response to any request from the IBEF. The timelines for producing each of these

deliverables will be in line and closely linked with the overall project timeline as indicated in above

section. Any conflict with respect to project and/or deliverable timelines will have to be resolved by

IA in consultation with IBEF and/or its designated agencies and approved by the IBEF. Thereafter the

approved timelines will have to be adhered to by IA, unless specified otherwise.

It is to be noted that upon completion of Go-live, IA is required to submit all the updated system

design documents, specifications, source code, application deployment files, user manuals,

administration manuals and all other applicable deliverables listed below.

Project Deliverables

Stage Activities Deliverables Timelines


Ver 0.f of 73

Kick-off Initial Stakeholder Meetings to

define the way forward for the

project

Inception Document: This would

include the:

The understanding of the IA

of the project.

Work Breakdown Structure

Detailed Project Schedule

and deliverables etc.

After award

of contract

Requirement

Analysis

Define Functional

Requirements

Requirements management

Prototyping

Documentation

Functional Requirement

Specification Document.

Software Requirements and

Specifications Document

T+10

Weeks

Design Detailed Software Solution

Architecture design

Detailed Hardware Solution

Architecture Design

Data Schema design

User Interface Design

Integration & Interfaces

Design

Prototyping design

Validation

Documentation

Design Specifications

Documents of Software

solutions

Design Specifications

Documents of Hardware

solutions

User Interface Design

Specifications

Integration Design

Specifications

Between

T+15

Weeks to

T+17

Weeks

Development Software installation,

configuration, and

customization

Hardware installation and

configuration

Development

Unit Testing

Documentation

Development Plan

Updated Design Document

Installed software and

hardware

Functional modules & Portal

Solution

Between

T+26 weeks

to T+27

weeks

Testing System Testing

Integration Testing

Stress Testing

User Acceptance Test Results

Completed Test Cases

Documentation

Complete Test Cases

Test Plan

User Acceptance Criteria

Problem reporting

Problem resolution testing

Between

T+27 weeks

to T+28

weeks

Implementation Documentation

Operations Planning

System User Manual &

Technical Manual

Knowledge Transfer and

training plan

Training Manual

Operations Plan

Operations Policies and

Between

T+30 weeks

to T+31

weeks


Ver 0.f of 73

Procedures

Go Live Report

Helpdesk Helpdesk operations.

Preparation of FAQs.

Report on establishment of

Helpdesk infrastructure

outlining details of Help

desk infrastructure deployed,

Helpdesk staff / contact

details, Helpdesk service

delivery processes etc.

FAQs.

T+28 weeks

Operation &

Maintenance

Operation & maintenance of

the entire system

Delivery of services.

Periodic SLA performance

reports

Periodic progress reports

After Go-

Live

2.15 Payment Terms & Schedule

IA will be required to finance all the expenses, capital and operational, related to their scope of work

in this project.

Design and Development payment

S.No. Milestone Payment

1. Mobile Application and Website prototype 10% of total cost

2. Final Launch of Web portal, Mobile portal, and Mobile

Application

10% of total cost

Total 20% of total cost

Operation and maintenance cost

S.No. Milestone Payment

1. Portal, application maintenance 80% of remaining payment

from Portal Development fee

with EQI for 12 quarters

(Contract period) after adjusting

penalty if any

* Service Tax would be paid as per prevalent rates at the time of Invoicing.

2.16 GO-LIVE and Acceptance Criterion

IBEF or its nominated agency will carry out User Acceptance Test, System Acceptance Test and /or

Certification to ensure that the implementation meets all the requirements including but not limited to

processes, standards, specifications, and performance as detailed in the RFP.

The IA is required to achieve “Go-live” status of the Brand India portal within the timelines specified

in section above. The “go-live” date is defined as the date when the IA has completed the following:


Ver 0.f of 73

This will be carried out after the release to the production (in case of application) or

commissioning (in case of client side infrastructure).

Service Provider shall submit a self-certificate to IBEF detailing out how all the requirements

targeted are met prior to the release to the production.

IBEF will review the details, conduct the necessary tests, and may request any clarifications.

Service Provider shall clarify with additional details to the satisfaction of IBEF and fix any

open items that are discovered during the tests / audits conducted by IBEF to the satisfaction

of IBEF. The same has to be approved by IBEF.

Released in production environment (in case of application) or deployed at the sites (in case

of infrastructure) and systems should be running for a continuous period of 2 weeks with no

Priority Level – 1 (Critical) or Priority Level – 2 (High) or Priority Level – 3 (Medium)

incidents reported.

All the services are enabled (as agreed upon with IBEF during the implementation phase) and

users including the external and internal IBEF users are able to successfully carry out the

business transactions on the brand India portal system.

The IT and Non IT infrastructure has been established as per the requirements and certified by

IBEF or its nominated quality agency.

The Brand India portal for Mobile, desktop platform and mobile application have been

designed, developed and tested for compliance to requirements including security certification

by a third party agency.

All the milestones have been achieved as specified in the Milestones section and timelines

and deliverables have been delivered as mentioned in this RFP.

Once “Certificate of System Acceptance” is provided to Service Provider by IBEF, it

will consider Go-Live of the Brand India portal solution.

2.17 Exit management & Transition

i. At the end of the contract period or upon termination of contract, if any other agency is

identified or selected by IBEF for providing O&M Services for IBEF portal system and IT

Infrastructure, the SP is required to provide necessary handholding and transition support to

the complete satisfaction of IBEF

ii. The ownership of the data generated upon usage of the system, at any point of time during the

contract or expiry or termination of the contract, shall rest absolutely with IBEF.

iii. During the exit/transition management process, it is the responsibility of the SP to address and

rectify the problems identified with the IBEF portal system and related IT infrastructure

including replacements of defunct hardware, cabling/re-cabling, installation/reinstallation of

the system software etc. The SP shall ensure that the infrastructure (both software and

hardware) are handed over to IBEF in a complete operational condition to the satisfaction of

IBEF. In case SP is unable to address such issues, IBEF may levy penalty or invoke the

Performance Bank Guarantee.

iv. During the contract period, the SP shall ensure that all the documentation including policies,

procedures, asset registers, configuration documents, Sign-off document, Maintenance


Ver 0.f of 73

Manuals, Administration Manual, Security Manual , Applications and Web Portal Training

Manual and others (if any) as per acceptable standards, Systems Manual Detailing the data

structure, table, forms and report structures., Installation and maintenance manual for the

servers and other hardware Trouble Shooting Guide / Handbook for helpdesk which

describes the various trouble shooting methods etc. are kept up to date and all such

documentation is handed over to IBEF during the exit management process.

2.18 Fraud and Corrupt Practices

a. The Bidders and their respective officers, employees, agents and advisers shall observe the

highest standard of ethics during the Selection Process. Notwithstanding anything to the

contrary contained in this RFP, the IBEF shall reject a Proposal without being liable in any

manner whatsoever to the Bidder, if it determines that the Bidder has, directly or indirectly or

through an agent, engaged in corrupt practice, fraudulent practice, coercive practice,

undesirable practice or restrictive practice (collectively the “Prohibited Practices”) in the

Selection Process. In such an event, the IBEF shall, without prejudice to its any other rights or

remedies, forfeit and appropriate the Bid Security or Performance Security, as the case may

be, as mutually agreed genuine pre-estimated compensation and damages payable to the IBEF

for, inter alia, time, cost and effort of the IBEF, in regard to the RFP, including consideration

and evaluation of such Bidder’s Proposal.

b. Without prejudice to the rights of the IBEF under Clause above and the rights and remedies

which the IBEF may have under the LOI or the Agreement, if an Bidder or Service Provider,

as the case may be, is found by the IBEF to have directly or indirectly or through an agent,

engaged or indulged in any corrupt practice, fraudulent practice, coercive practice,

undesirable practice or restrictive practice during the Selection Process, or after the issue of

the LOI or the execution of the Agreement, such Bidder or Service Provider shall not be

eligible to participate in any tender or RFP issued by the IBEF during a period of 2 (two)

years from the date such Bidder or Service Provider, as the case may be, is found by the IBEF

to have directly or through an agent, engaged or indulged in any corrupt practice, fraudulent

practice, coercive practice, undesirable practice or restrictive practice, as the case may be.

c. For the purposes of this Section, the following terms shall have the meaning hereinafter

respectively assigned to them:

i. “corrupt practice” means (i) the offering, giving, receiving, or soliciting, directly or

indirectly, of anything of value to influence the action of any person connected with

the Selection Process (for avoidance of doubt, offering of employment to or

employing or engaging in any manner whatsoever, directly or indirectly, any official

of the IBEF who is or has been associated in any manner, directly or indirectly with

the Selection Process or the LOI or has dealt with matters concerning the Agreement

or arising there from, before or after the execution thereof, at any time prior to the

expiry of one year from the date such official resigns or retires from or otherwise

ceases to be in the service of the IBEF, shall be deemed to constitute influencing the

actions of a person connected with the Selection Process); or (ii) save as provided

herein, engaging in any manner whatsoever, whether during the Selection Process or

after the issue of the LOA or after the execution of the Agreement, as the case may

be, any person in respect of any matter relating to the Project or the LOA or the


Ver 0.f of 73

Agreement, who at any time has been or is a legal, financial or technical consultant/

adviser of the IBEF in relation to any matter concerning the Project;

ii. “fraudulent practice” means a misrepresentation or omission of facts or disclosure of

incomplete facts or presenting incorrect information in order to influence the

Selection Process;

iii. “coercive practice” means impairing or harming or threatening to impair or harm,

directly or indirectly, any persons or property to influence any person’s participation

or action in the Selection Process;

iv. “undesirable practice” means (i) establishing contact with any person connected with

or employed or engaged by IBEF with the objective of canvassing, lobbying or in any

manner influencing or attempting to influence the Selection Process; or (ii) having a

Conflict of Interest; and

v. “restrictive practice” means forming a cartel or arriving at any understanding or

arrangement among Bidders with the objective of restricting or manipulating a full

and fair competition in the Selection Process

2.19 Conflict of Interest

a. A bidder shall not have a conflict of interest that may affect the Selection Process or the

Solution delivery (the “Conflict of Interest”). Any Bidder found to have a Conflict of

Interest shall be disqualified. In the event of disqualification, the IBEF shall forfeit and

appropriate the EMD, if available, as mutually agreed genuine pre-estimated compensation

and damages payable to the IBEF for, inter alia, the time, cost and effort of the IBEF

including consideration of such Bidder’s Proposal, without prejudice to any other right or

remedy that may be available to the IBEF hereunder or otherwise.

b. The IBEF requires that the Service Provider provides solutions which at all times hold the

IBEF’s interests paramount, avoid conflicts with other assignments or its own interests, and

act without any consideration for future work. The Service Provider shall not accept or

engage in any assignment that would be in conflict with its prior or current obligations to

other clients, or that may place it in a position of not being able to carry out the assignment in

the best interests of the IBEF.

c. Without limiting the generality of the above, an Bidder shall be deemed to have a Conflict of

Interest affecting the Selection Process, if:

i. the Bidder and any other Bidder have common controlling shareholders or other

ownership interest; provided that this disqualification shall not apply in cases where

the direct or indirect shareholding or ownership interest of an Bidder (or any

shareholder thereof having a shareholding of more than 5 per cent of the paid up and

subscribed share capital of such Bidder in the other Bidder is less than 5% (five per

cent) of the subscribed and paid up equity share capital thereof. For the purposes of

this Clause, indirect shareholding held through one or more intermediate persons shall

be computed as follows:


Ver 0.f of 73

− where any intermediary controlled by a person through management control

or otherwise, the entire shareholding held by such controlled intermediary

in any other person (the “Subject Person”) shall be taken into account for

computing the shareholding of such controlling person in the Subject

Person; where a person does not exercise control over an intermediary,

which has shareholding in the Subject Person, the computation of indirect

shareholding of such person in the Subject Person shall be undertaken on

− a proportionate basis; provided, however, that no such shareholding shall be

reckoned under this Sub-clause if the shareholding of such person in the

intermediary is less than 26% (twenty six per cent) of the subscribed and

paid up equity shareholding of such intermediary; or

ii. a constituent of such Bidder is also a constituent of another Bidder; or

iii. such Bidder receives or has received any direct or indirect subsidy or grant from any

other Bidder; or

iv. such Bidder has the same legal representative for purposes of this Application as any

other Bidder; or

v. such Bidder has a relationship with another Bidder, directly or through common third

parties, that puts them in a position to have access to each other’s’ information about,

or to influence the Application of either or each of the other Bidder; or

vi. there is a conflict among this and other solution assignments of the Bidder (including

its personnel and other members, if any) and any subsidiaries or entities controlled by

such Bidder or having common controlling shareholders. The duties of the Service

Provider will depend on the circumstances of each case. While providing portal and

mobile solution services and related solutions to the IBEF for this particular

assignment, the service provider shall not take up any assignment that by its nature

will result in conflict with the present assignment; or

vii. A firm hired to provide System Integration/Turnkey solutions for the implementation

of a project, will be disqualified from subsequently providing goods or works or

services related to the same project;

d. An Bidder eventually appointed to implement portal and application services for this Project

shall be disqualified from subsequently providing goods or works or services related to the

construction and operation of the same Project and any breach of this obligation shall be

construed as Conflict of Interest; provided that the restriction herein shall not apply after a

period of 12 months from the completion of this assignment; provided further that this

restriction shall not apply to software solutions delivered to the IBEF in continuation of this

systems implementation or to any subsequent systems implementation executed for the IBEF

in accordance with the rules of the IBEF.


Ver 0.f of 73

Appendix I: Pre-Qualification & Technical Bid Templates

The bidders are expected to respond to the RFP using the forms given in this section and all

documents supporting Pre-Qualification / Technical Evaluation Criteria.

Forms to be used in Pre-Qualification Proposal

Form 1: Compliance Sheet for Pre-qualification Proposal

Form 2: Particulars of the Bidder

Form 3: Bank Guarantee for Earnest Money Deposit

Form 4: Financial Details of the Organization

Form 5: Details of CMMi Certification

Forms to be used in Technical Proposal

Form 1: Letter of Proposal

Form 2: Experience in implementing portal solution

Form 3: project experience in implementation of an IT Application

Form 4: Technical BOM for Cloud Services (Form 1A, 1B, 1C, 1D)

Form 5: Network Connectivity Detail

Form 6: Personnel Profiles

Form 7: Proposed Solution


Ver 0.f of 73

Form 1: Compliance Sheet for Pre-qualification Proposal

The pre-qualification proposal should comprise of the following basic requirements. The documents

mentioned in this compliance sheet along with this form, needs to be a part of the Pre-Qualification

proposal.

S.

No.

Basic Requirement Documents Required Provided Reference

Page Number

1. Power of Attorney Power of Attorney in the name of the

Authorized signatory

2. Particulars of the Bidders Form 2

3. Earnest Money Deposit Original EMD

4. Office Location Copy of a proof in this regard in the form

of Municipality Registration/ Labour

Department registration

5. Legal Entity 1) Certificate of Incorporation

2) Registration Certificate

3) Memorandum and Articles of

Association or Filings to the Stock

Exchanges

4) PAN

5) Service tax registration certificate

6. Turnover Extracts from the Audited Balance Sheet

and Profit and Loss Account

OR

Certificate from the statutory auditor

7. Nature of Work Turnover Completion Certificates from the client;

OR

Purchase / Work Order + Phase

Completion Certificate from the client

OR

Citations that include letter from the client

or contract agreements

8. Net Worth Certificate from the statutory auditor

9. Portal/Web development

experience

Completion Certificates from the client;

OR

Purchase / Work Order + Self Certificate

of Completion (Certified by the Statutory

Auditor); OR

Purchase / Work Order + Phase

Completion Certificate from the client

10. Manpower A Self Certified letter by the Authorized

Signatory which should be HR head or

Company Secretary

11. Certifications

Copy of valid certifications

12. Blacklisting A Self Certified letter by the Authorized

Signatory


Ver 0.f of 73

Form 2: Particulars of the Bidder

SI No. Information Sought Details to be Furnished

A Name and address of the bidding

Company

B Incorporation status of the firm

(public limited / private limited,

etc.)

C Year of Establishment

D Date of registration and

registration No.

E ROC Reference No.

F Details of company registration

G Details of registration with

appropriate authorities for service

tax

H Details of registration with

appropriate authorities for Sales

tax/VAT

I Name, Address, email, Phone nos.

and Mobile Number of Contact

Person

Form 3: Bank Guarantee for Earnest Money Deposit

To,

Deputy CEO, IBEF


Apparel House, 5th Floor, # 519-22,


Haryana,

India

Whereas <<Name of the bidder>> (hereinafter called 'the Bidder') has submitted the bid for

Submission of RFP # <<RFP Number>> dated <<Date>> for <<Name of the assignment>>

(hereinafter called "the Bid") to the India Brand Equity Foundation (IBEF).

Know all Men by these presents that we << >> having our office at <<Address>> (hereinafter called

"the Bank") are bound unto the <<IBEF>> (hereinafter called "the Purchaser") in the sum of Rs.

<<Amount in figures>> (Rupees <<Amount in words>> only) for which payment well and truly to be


Ver 0.f of 73

made to the said Purchaser, the Bank binds itself, its successors and assigns by these presents. Sealed

with the Common Seal of the said Bank this <<Date>>

The conditions of this obligation are:

1. If the Bidder having its bid withdrawn during the period of bid validity specified by the Bidder on

the Bid Form; or

2. If the Bidder, having been notified of the acceptance of its bid by the Purchaser during the period

of validity of bid

(a) Withdraws his participation from the bid during the period of validity of bid document; or

(b) Fails or refuses to participate in the subsequent Tender process after having been short

listed;

We undertake to pay to the Purchaser up to the above amount upon receipt of its first written demand,

without the Purchaser having to substantiate its demand, provided that in its demand the Purchaser

will note that the amount claimed by it is due to it owing to the occurrence of one or both of the two

conditions, specifying the occurred condition or conditions.

This guarantee will remain in force up to <<insert date>> and including <<extra time over and above

mandated in the RFP>> from the last date of submission and any demand in respect thereof should

reach the Bank not later than the above date.

NOTHWITHSTANDING ANYTHING CONTAINED HEREIN:

I. Our liability under this Bank Guarantee shall not exceed Rs. <<Amount in figures>> (Rupees

<<Amount in words>> only)

II. This Bank Guarantee shall be valid up to <<insert date>>)

III. It is condition of our liability for payment of the guaranteed amount or any part thereof arising

under this Bank Guarantee that we receive a valid written claim or demand for payment under

this Bank Guarantee on or before <<insert date>>) failing which our liability under the

guarantee will automatically cease.

(Authorized Signatory of the Bank)

Seal:

Date:


Ver 0.f of 73

Form 4: Financial Details of the Organization

Financial Information

FY 2012-13 FY 2013-14 FY 2014-15

Revenue (in INR crores)

Profit Before Tax (in INR crores)

Revenue from IT services and system

integration services (in INR crores)

Other Relevant Information

Mandatory Supporting Documents:

a. Auditor Certified financial statements for the last three financial years; 2014-15, 2013-14 and

2012-13 .For companies whose closure of the financial year is not March, then such

companies shall submit the statements for the years 2013-14, 2012-13, and 2011-12.

(Please include only the sections on P&L, revenue and the assets, not the entire balance

sheet.).

b. Certification by the company auditors supporting the above information

Form 5: Details of CMMi Certification

CMMi Assessment Details

Level of CMMi Assessment

Date of Assessment

Validity of the Assessment

Name of the Assessing company and their

contact details

Units / Locations Assessed

Mandatory Supporting Documents

Proof of Certification

In case of bidders where the CMMi certification is under renewal, the bidders shall provide the

details of the previous CMMi certification and the current assessment details for consideration in

the RFP process


Ver 0.f of 73

Forms for Technical Proposal

Technical Proposal Form 1: Letter of Proposal

To:

<Location, Date>

Deputy CEO, IBEF




Haryana,

India

Subject: Submission of the Technical bid for <Name of the assignment>

Dear Sir/Madam,

We, the undersigned, offer to undertake the assignment of design, development and maintenance of an

Brand India B2B portal for IBEF on <Name of the engagement> with your Request for Proposal

dated <insert date> and our Proposal. We are hereby submitting our Proposal, which includes this

Technical bid and the Financial Bid sealed in a separate envelope.

We hereby declare that all the information and statements made in this Technical bid are true and

accept that any misinterpretation contained in it may lead to our disqualification.

We undertake, if our Proposal is accepted, to initiate the Implementation services related to the

assignment not later than the date indicated in Fact Sheet.

We agree to abide by all the terms and conditions of the RFP document. We would hold the terms of

our bid valid for < > days as stipulated in the RFP document.

We understand you are not bound to accept any Proposal you receive.

Yours sincerely,

Authorized Signature [In full and initials]:

Name and Title of Signatory:

Name of Firm:

Address:

Location: _____________________________________Date: ___________________________

Technical Proposal Form 2: Experience in implementing portal solution


Ver 0.f of 73

Previous Project experience - Transactional Web Portals for providing online

aggregator services to Citizens/Businesses)

General Information

Name of the project

Client for which the project was executed

Name and contact details of the client

Project Details

Project Name & Description of the

project

Role of the SP

Scope of work

Outcomes of the project

Underlying Solution Components of the

Project (portal solutions in providing e-

commerce related/ product catalogue

services to citizens/ businesses – features

comprising of product catalogue services,

comprehensive search mechanism, multi

lingual support, rich media content

support, workflow engine, online

payment facilities, DMS, user registration

system, user feedback and review system

Details of Solution Components

Portal Product catalogue

/Workflow/DMS/CMS/ /Online Payment

Solution...

Give details for each of the components

Number of end-users by type of users

Services offered

Technology Stack (including COTs

components used)


Ver 0.f of 73

Architecture (n-tier/ other, DC, apps,

security etc.)

Service levels being offered/ Quality of

service (QOS)

Critical SLA

Other Details

Total cost of the project

Total cost of the services provided by the

Bidder

Duration of the project (no. of months,

start date, completion date, current

status)


a) Letter from the client to indicate the successful completion of the projects

Other Relevant Information

(The bidders may provide additional details as required to meet the technical criteria)


Scanned/Photo copies of Purchase Orders & Completion Certificates. Email references

will not be accepted.

The project should have gone live in the last 5 financial years (2010-2015).

Project Capability Demonstration

Please provide complete details regarding the scope of the project to indicate the relevance

to the requested technical evaluation criterion.

Technical Proposal Form 3: project experience in implementation of an IT Application

Previous Project experience - Experience in Implementation of IT Projects(Web

Application) in e-commerce sector

General Information

Name of the project

Client for which the project was executed

Name and contact details of the client

Project Details


Ver 0.f of 73

Project Name & Description of the project

Role of the SP

Scope of work

Duration

Outcomes of the project

Project Components should be an IT

Application (web application not a static

website) in the e-commerce sector or in

aggregator services .

Solution Details

Functions/Modules implemented

Number of Users for each module

Number of daily financial and non-financial

transactions

Technology Stack (including COTs

components used)

Architecture (n-tier/ other, security etc.)

Years in Operation

Current Status

Other Details

Total cost of the project

Total cost of the services provided by the

Bidder

Duration of the project (no. of months, start

date, completion date, current status)


a) Scanned/Photo copies of Purchase Orders & Completion Certificates. Email references will

not be accepted.

b) Provide one citation. The project should have gone live in the last 5 financial years (2010-

2015).

Project Capability Demonstration

Please provide complete details regarding the scope of the project to indicate the relevance to the

requested technical evaluation criterion.

Technical Proposal Form 4: Technical BOM for Cloud Services (Form 1A, 1B, 1C, 1D)

(The bidder shall submit one form each for Development (1A), Testing (1B), Training (1C), and

Production Environments (1D) respectively (Year on Year sizing to cater for the requirements ) )

Component Unit of Measurement Year1 Year2 Year3

Compute

In case of proposing VMs of

different configuration,

include individual line items

providing the VM


Ver 0.f of 73

configuration (type of VM,

number of virtual CPUs /

cores, Speed, memory, disk

space/storage,)

Memory

Storage

In case of proposing Storage

of different configuration,

include individual line items

providing the Storage

configuration details

Platform (System software)

As a service (if any)

Include individual line items

as required for each of the

System Software

Technical Proposal Form 5: Network Connectivity Detail

Sr. No. Location Bandwidth factored

i. Data Center

ii. Insert Items as required

iii. Disaster Recovery Center

iv. Insert Items as required

v. IBEF Office

vi. Insert Items as required

Technical Proposal Form 6: Personnel Profiles

Summary of Profiles of the resources proposed for the project.

Role Name of the Proposed Resource

Solution Architect

Project Manager –Applications/ Software

Project Manager – IT Infrastructure including

Cloud Expertise

Domain Expert

Format for the Profiles

Name of the person

Current Designation / Job Title


Ver 0.f of 73

Current job responsibilities

Proposed Role in the Project

Proposed Responsibilities in the Project

Academic Qualifications:

Degree

Academic institution graduated from

Year of graduation

Specialization (if any)

Professional Certifications (if any)

Total number of years of experience

Experience in similar Projects as proposed in RFP

(Provide the details of the projects such as project name, customer

name, key project features, duration of the project, and status of the

project)

Relevant Experience as per the Role in the current project

(Provide the details of the projects such as project name, customer

name, key project features, duration of the project, and status of the

project)

A separate undertaking with the format as below with all the names of the proposed profiles should be

provided.

Certification

I, the undersigned, certify that to the best of my knowledge and belief, the proposed CVs correctly

describes the qualifications and experience of the respective resource. I understand that any willful

misstatement described herein may lead to disqualification of the bid.

Names of the proposed profiles:

1.

2.

3.

…..

…..

Signature:

Date:

[Signature of authorized representative] Day/Month/Year

Full name of authorized representative:

Technical Proposal Form 7: Proposed Solution

Technical approach, methodology and work plan are key components of the Technical Proposal. You

are suggested to present Approach and Methodology divided into the following sections:


Ver 0.f of 73

a) Solution Proposed

b) Understanding of the project (how the solution proposed is relevant to the understanding)

c) Technical Approach and Methodology.

d) Feasibility parameters for the proposed solution in respect of understanding of IBEF

requirements


Ver 0.f of 73

Appendix II: Forms for the Financial Proposal

Form to be used in Financial Proposal

Form 1: Financial Proposal

Form 2: Template for PBG

Form 1: Financial Proposal Letter

To:

<Location, Date>

Deputy CEO, IBEF




Haryana,

India

Subject: Submission of the Financial bid for <Provide Name of the Assignment>

Dear Sir/Madam,

We, the undersigned, offer to the assignment of design, development and maintenance of an

Brand India B2B portal for IBEF <<Title of Services>> in accordance with your Request for Proposal

dated <<Date>> and our Proposal (Technical and Financial Proposals). Our attached Financial

Proposal is for the sum of <<Amount in words and figures>>. This amount is inclusive of all taxes &

levies except service tax.

Fixed Annual Fee

1st year :Rs.--------

2nd year :Rs.--------

3rd year :Rs.--------

Total for 3 years: Rs.--------

* Excluding service tax. Service tax shall be paid (extra) as per applicable rates at the time of Invoice

generation.

1. PRICE AND VALIDITY

All the prices mentioned in our Tender are in accordance with the terms as specified in the

RFP documents. All the prices and other terms and conditions of this Bid are valid for a

period of <days> calendar days from the date of opening of the Bid.

We hereby confirm that our prices include all taxes. However, all the taxes are quoted

separately under relevant sections.


Ver 0.f of 73

We understand that the actual payment would be made as per the existing indirect tax rates

during the time of payment.

2. UNIT RATES

We have indicated in the relevant forms 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. TENDER PRICING

We further confirm that the prices stated in our bid are in accordance with your Instruction to

Bidders included in Tender documents.

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

5. BID PRICE

We declare that our Bid Price is for the entire scope of the work as specified in the RFP document.

These prices are indicated Commercial Bid attached with our Tender as part of the Tender.

6. PERFORMANCE BANK GUARANTEE

We hereby declare that in case the contract is awarded .to us, we shall submit the Performance Bank

Guarantee as specified in the <Appendix III> of this RFP document.

Our Financial Proposal shall be binding upon us subject to the modifications resulting from Contract

negotiations, up to expiration of the validity period of the Proposal, i.e., [Date].

We understand you are not bound to accept any Proposal you receive.

We declare that all the services shall be performed strictly in accordance with the Tender documents.

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.

Thanking you,

We remain,

Yours sincerely,


Ver 0.f of 73

Authorized Signature:

Name and Title of Signatory:

Name of Firm:

Address:


Ver 0.f of 73

Form 2: Template for PBG

PERFORMANCE SECURITY:

Deputy CEO, IBEF




Haryana,

India

Whereas, <<name of the supplier and address>> (hereinafter called “the bidder”) has undertaken, in

pursuance of contract no. <Insert Contract No.> dated. <Date> to provide of design, development and

maintenance of Brand India B2B portal for IBEF <<name of the assignment>> to the India Brand

Equity Foundation (hereinafter called “the beneficiary”)

And whereas it has been stipulated by in the said contract that the bidder shall furnish you with a bank

guarantee by a recognized bank for the sum specified therein as security for compliance with its

obligations in accordance with the contract;

And whereas we, <Name of Bank> a banking company incorporated and having its head /registered

office at <Address of Registered Office> and having one of its office at <Address of Local Office>

have agreed to give the supplier such a bank guarantee.

Now, therefore, we hereby affirm that we are guarantors and responsible to you, on behalf of the

supplier, up to a total of Rs.<Insert Value> (Rupees <Insert Value in Words> only) and we

undertake to pay you, upon your first written demand declaring the supplier to be in default under the

contract and without cavil or argument, any sum or sums within the limits of Rs. <Insert Value>

(Rupees <Insert Value in Words> only) as aforesaid, without your needing to prove or to show

grounds or reasons for your demand or the sum specified therein.

We hereby waive the necessity of your demanding the said debt from the bidder before presenting us

with the demand.

We further agree that no change or addition to or other modification of the terms of the contract to be

performed there under or of any of the contract documents which may be made between you and the

Bidder shall in any way release us from any liability under this guarantee and we hereby waive notice

of any such change, addition or modification.

This Guarantee shall be valid until <<Insert Date>>)

Notwithstanding anything contained herein:


Ver 0.f of 73

I. Our liability under this bank guarantee shall not exceed Rs. <Insert Value> (Rupees <Insert

Value in Words> only).

II. This bank guarantee shall be valid up to <Insert Expiry Date>)

III. It is condition of our liability for payment of the guaranteed amount or any part thereof arising

under this bank guarantee that we receive a valid written claim or demand for payment under

this bank guarantee on or before <Insert Expiry Date>) failing which our liability under the

guarantee will automatically cease.