Proposals are invited for selection of System Integrator for implementation of State Wide roll- out of e-District Mission Mode Project, Odisha. Last date for submission of proposal is 26.07.2013 upto 3 PM. For details please visit the websites www.ocac.in , tenders.gov.in , http://www.odisha.gov.in. N.B.:- OCAC reserves the right to accept/ reject any/ all proposals without assigning any reason thereof. General Manager(Admn.), OCAC, Plot No.-N-1/7-D, Acharya Vihar, P.O.-RRL, Bhubaneswar-751013, Ph.-2567280/ 2567064/ 2567295 REQUEST FOR PROPOSAL Enq.No.:- OCAC-TJ-11/2012/ENQ/13015 (Technical Directorate of I.T. Deptt., Govt. of Odisha) ODISHA COMPUTER APPLICATION CENTRE EXCELLENCE IN IT SOLUTIONS
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Proposals are invited for selection of SystemIntegrator for implementation of State Wide roll-out of e-District Mission Mode Project, Odisha.Last date for submission of proposal is26.07.2013 upto 3 PM. For details please visitthe websites www.ocac.in , tenders.gov.in ,http://www.odisha.gov.in.N.B.:- OCAC reserves the right to accept/ reject any/ allproposals without assigning any reason thereof.General Manager(Admn.), OCAC, Plot No.-N-1/7-D, Acharya Vihar,P.O.-RRL, Bhubaneswar-751013, Ph.-2567280/ 2567064/ 2567295
REQUEST FOR PROPOSALEnq.No.:- OCAC-TJ-11/2012/ENQ/13015
(Technical Directorate of I.T. Deptt., Govt. of Odisha)ODISHA COMPUTER APPLICATION CENTRE
EXCELLENCE IN IT SOLUTIONS
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
1 | P a g e
REQUEST FOR PROPOSAL FOR
SELECTION OF SYSTEM INTEGRATOR FOR STATE WIDE ROLLOUT
2 SCHEDULE OF BID PROCESS ........................................................................................................................... 8
3 STRUCTURE OF THE RFP ................................................................................................................................ 9
4 BACKGROUND INFORMATION ....................................................................................................................... 9
4.1 BASIC INFORMATION ......................................................................................................................................... 9
4.3 STATE INFORMATION ....................................................................................................................................... 11
4.4 KEY INFORMATION .......................................................................................................................................... 13
4.5 ABOUT THE DEPARTMENT / OCAC..................................................................................................................... 14
5 INSTRUCTIONS TO THE BIDDERS .................................................................................................................. 15
5.2 LACK OF INFORMATION TO BIDDER ..................................................................................................................... 15
5.3 FRAUDULENT & CORRUPT PRACTICE ................................................................................................................... 16
5.4 APPLICABLE LAW ............................................................................................................................................. 16
5.9 PATENT RIGHTS .............................................................................................................................................. 17
5.10 TAXES AND DUTIES .......................................................................................................................................... 17
5.14 RESOLUTION OF DISPUTES AND ARBITRATION ....................................................................................................... 18
5.15 ACQUAINTANCE WITH LOCAL CONDITIONS ........................................................................................................... 18
5.16 LIMITATIONS OF LIABILITY ................................................................................................................................. 19
5.17 GENERAL ....................................................................................................................................................... 19
5.18 COMPLIANT PROPOSALS / COMPLETENESS OF RESPONSE ........................................................................................ 19
5.19.2 Responses to Pre-Bid Queries and Issue of Corrigendum .................................................................. 20
5.20 KEY REQUIREMENTS OF THE BID ......................................................................................................................... 20
5.20.1 Right to Terminate the Process ......................................................................................................... 20
5.21.2 Language ........................................................................................................................................... 23
5.21.3 Venue & Deadline for Submission of Proposals ................................................................................. 23
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
3 | P a g e
5.21.4 Late Bids ............................................................................................................................................ 23
5.22 EVALUATION PROCESS ..................................................................................................................................... 23
7 APPOINTMENT OF SYSTEM INTEGRATOR .................................................................................................... 42
7.1 AWARD CRITERIA ............................................................................................................................................ 42
7.2 RIGHT TO ACCEPT ANY PROPOSAL AND TO REJECT ANY OR ALL PROPOSAL(S) ............................................................. 42
7.3 NOTIFICATION OF AWARD................................................................................................................................. 42
7.4 CONTRACT FINALIZATION AND AWARD ................................................................................................................ 43
FORM 1: UNDERTAKING ON TOTAL RESPONSIBILITY ............................................................................................................ 45
FORM 2: PARTICULARS OF THE BIDDER ............................................................................................................................. 46
FORM 3: BANK GUARANTEE FOR EMD ........................................................................................................................... 47
FORM 4A: COMPLIANCE SHEET FOR PRE-QUALIFICATION PROPOSAL ..................................................................................... 49
FORM 4B: COMPLIANCE SHEET FOR TECHNICAL PROPOSAL .................................................................................................. 52
FORM 5: LETTER OF PROPOSAL ....................................................................................................................................... 55
FORM 6: PROJECT CITATION FORMAT .............................................................................................................................. 56
FORM 7: PROPOSED SOLUTION ....................................................................................................................................... 57
FORM 8: PROPOSED WORK PLAN ................................................................................................................................... 58
FORM 9: TEAM COMPOSITION........................................................................................................................................ 59
FORM 10: CURRICULUM VITAE (CV) OF KEY PERSONNEL..................................................................................................... 60
FORM 11: DEPLOYMENT OF PERSONNEL .......................................................................................................................... 62
FORM 12: DEVIATIONS ................................................................................................................................................. 63
FORM 13: MANUFACTURERS AUTHORIZATION FORM ......................................................................................................... 64
FORM 14: DECLARATION ON SOURCE CODE AND INTELLECTUAL PROPERTY RIGHTS .................................................................. 66
FORM 15: UNDERTAKING ON PATENT RIGHTS ................................................................................................................... 67
FORM 16: UNDERTAKING ON COMPLIANCE AND SIZING OF INFRASTRUCTURE .......................................................................... 68
FORM 17: UNDERTAKING ON SERVICE LEVEL COMPLIANCE .................................................................................................. 69
FORM 18: UNDERTAKING ON DELIVERABLES ..................................................................................................................... 70
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
4 | P a g e
FORM 19: UNDERTAKING ON SUPPORT TO THIRD PARTY SOLUTION ACCEPTANCE AND CERTIFICATION .......................................... 71
FORM 20: DECLARATION OF ACTIVITIES SUB-CONTRACTED ................................................................................................... 72
FORM 21: UNDERTAKING ON EXIT MANAGEMENT AND TRANSITION ...................................................................................... 73
FORM 22: DECLARATION THAT THE BIDDER HAS NOT BEEN BLACKLISTED ................................................................................. 74
FORM 1: COVERING LETTER ........................................................................................................................................... 75
FORM 2: FINANCIAL PROPOSAL....................................................................................................................................... 77
Form 2.1: Software Development Commercial Format....................................................................................... 78
Form 2.2: Integration Cost Commercial Format ................................................................................................. 79
Form 2.3: Commercial Format for Equipment’s at SDC, Bhubaneswar .............................................................. 80
Form 2.4: Commercial Format for Equipment’s at District Collectorate ............................................................. 81
Form 2.5: Commercial Format of Equipment’s at Sub-Collector office ............................................................... 82
Form 2.6: Commercial Format of Equipment’s at Tahsil offices of Odisha ......................................................... 83
Form 2.7: Commercial format of Equipment’s at Block offices of Odisha ........................................................... 84
Form 2.8: System Software Commercial Format ................................................................................................ 85
Form 2.9: Broadband Connectivity Commercial Format ..................................................................................... 86
Form 2.10: Training/Workshop Commercial Format .......................................................................................... 87
Form 2.11: Application Support & Maintenance Cost ......................................................................................... 88
Form 2.12: Commercial Formant for Technical Support Staff at SDC & District Level ........................................ 89
Form 2.13: Other Cost Commercial Format ........................................................................................................ 90
ANNEXURE III: TEMPLATE FOR PBG & CCN .............................................................................................................. 91
FORM 1: PERFORMANCE BANK GUARANTEE ..................................................................................................................... 91
FORM 2: CHANGE CONTROL NOTICE (CCN) FORMAT ......................................................................................................... 93
ANNEXURE IV: DEFINITION OF GO-LIVE......................................................................................................................... 95
3. Date of pre-bid conference 02/07/2013& 15:00 hr
4. Release of response to clarifications 11/07/2013 & 15:00 hrs
5. Bid validity period 180 days from the last date (deadline) for
submission of proposals.
6. Last date (deadline) for submission of
bids
26/07/2013 & 15:00 Hrs
7. Opening of Pre-Qualification & Technical
Bids
26/07/2013 & 17:00 Hrs
8. Technical Presentation by the Bidders “Will be intimated later
9. Place, Time and Date of opening of
Financial proposals received in response
to the RFP notice
“Will be intimated later”
10. Contact person for queries General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha Fax +91 -674-2567842
11. End-to-end project documentation and creation of manuals
T0 + 22 weeks
12. Installation & Commissioning of Hardware at District Level Offices
T0 + 16 weeks
13. Installation & Commissioning of Hardware at SDC T0 + 12 weeks
14. Onsite support covering 3 years of warranty from the date of Go-Live
T2
15. 2 years of AMC for all the H/W, N/W equipment’s, peripherals after completion of 3 years of warranty period
T2 + 2 Years
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
26 | P a g e
5.24 Terms of Payment Schedule
The following schedule would be followed for payment during the Project implementation:
S. No Milestone % of Total Fee Basis of approval
1 Approval of Final SRS 5% Minutes of meeting of the Apex Committee approving the report
2 UAT of the e-District Application by Apex Committee, deployment of necessary hardware at SDC and completion of following key activities:
- Development of connectors for SSDG
- Integration with NSDG
- Integration with AADHAAR
- Integration with Payment Gateway
- Localisation of eDistrict Application
- CSC wise Transaction reports &
calculation of fee for each SCA
- Mobile enablement of eDistrict
Application
5% Minutes of meeting of the Apex Committee approving the e-District application for all services identified in the RFP.
3 Successful District Readiness for all offices, i.e. Completion of all activities/ commissioning of all hardware & networking equipment’s in a district; i.e.
- Hardware
- Network
- Training
- Placement of Technical Manager in the
district
15% Approval of the District Collector
4 STQC Certification 5% Copy of the STQC certification
5 “Go-Live” in at least 25% Districts 10% Go-live in a district would mean 1) Using the e- District application
6 “Go-Live” in at least 50% Districts 5%
7 “Go-Live” in at least 75% Districts 5%
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
27 | P a g e
S. No Milestone % of Total Fee Basis of approval
8 “Go-Live” in 100% Districts 5% for delivery of all services 2) Completion of training 3) Deployment of identified hardware for those Districts 4) Engagement of Technical Support Staff at SDC & District Level
9 Operations and Maintenance Phase 36% To be paid quarterly (3% per quarter) for 36 months
10 Successful Exit Management 9% Minutes of meeting of the Apex Committee
Total 100%
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
28 | P a g e
5.25 Penalty
In the event the bidder is unable to meet defined milestones, a penalty of 0.5% will be charged for
each week delay from payment associated to the respective milestone, maximum limit being 10% of
the respective mile stone amount. If the delay continues beyond 20 weeks, OCAC, may terminate the
Agreement.
5.26 Service Level Agreements
5.26.1 Operation & Maintenance Support
Sl. No. SLA Terms Description
1. System Uptime Time for which user is able to access the
applications, website and other components of
the IT solution during the working hours. The
system can be down due to any of the reasons
including failure of hardware, network, system
software, application etc.
Scheduled downtime for example, backup time,
batch processing time, routine maintenance time
will not be considered while evaluating the
system uptime. However, the selected SI will be
required to schedule such downtime with prior
approval of OCAC. The selected SI will plan
scheduled downtime outside working time. In
exceptional circumstances, OCAC may allow the
SI to plan scheduled downtime in the working
hours.
2. Bugs / Issues in the
Application Software /
Hardware device / Network
Equipment
Critical bugs / issues – Bugs / issues affecting
more than one division or more than one user in
a division,
Non-critical bugs / issues – Bugs / issues
affecting at most one user in a division.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
29 | P a g e
Service
Category
Service
Level Title
/ Objective
Data Capture Measureme
nt Interval
Reportin
g Period
Hours
of
Suppor
t
Target
Servic
e
Level
Minimu
m
Service
Level
Service
Level
Dependenc
y
Increase
d Impact
Severity Weight
System
Uptime and
Performanc
e - SDC
System
uptime and
performanc
e of the
system -
SDC
No. of
recorded
hours on
server logs of
uninterrupte
d usage of the
system by
users during
working
hours
Weekly Weekly 24x7 99.9% 99% Power
Backup
Upgrades
System
Restores
To be
base
lined for
first 6
months
INR 300,000 per month for
every drop in percentage
point of uptime below 99.5 %
[The non-availability for
application service, website
measured on monthly basis
and excluding the scheduled
maintenance shutdown.
Performance of system refers
to the proper and timely
functioning of the system’s
functionalities. The
applications should be
available and performing as
per functionalities]
System
Uptime and
Performanc
e – Field
Offices
System
uptime and
performanc
e of the
system –
Field Offices
No. of
recorded
hours on
manual logs
of
uninterrupte
d usage of
each
hardware &
peripheral by
users during
working
hours
Monthly Monthly 9 x 6 >99% >99% Power
Backup
To be
base
lined for
first 6
months
INR 750 per instance of
violation for a drop in uptime
between <99% and >=98%.
Additional INR 1500 per
instance of violation for every
1% drop in percentage point
of uptime below 98%.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
30 | P a g e
Service
Category
Service
Level Title
/ Objective
Data Capture Measureme
nt Interval
Reportin
g Period
Hours
of
Suppor
t
Target
Servic
e
Level
Minimu
m
Service
Level
Service
Level
Dependenc
y
Increase
d Impact
Severity Weight
Network
Availability
Average
LAN
Network
Availability
of
each of the
designated
office
location and
the nearest
SWAN PoP.
Recording the
no. of hours
of network
outage during
working
hours.
Monthly Monthly 6 x 9 > 99% > 99% To be
base
lined for
first 6
months
INR 50,000 per month for
every drop in percentage
point of uptime below 98%
Helpdesk
Performanc
e
98% of the
calls shall be
answered
within 45
seconds.
Monthly Monthly 6 x 9 > 98% > 98% To be
base
lined for
first 6
months
INR 750 per month for every
drop in percentage point of
uptime below 98%
Helpdesk
Performanc
e
98% of the
incidents
within
helpdesk
resolution
capacity
shall be
resolved in
a cycle time
of 24 hours.
Monthly Monthly 6 x 9 > 98% > 98% To be
base
lined for
first 6
months
INR 750 per month for every
drop in percentage point of
uptime below 98%
Helpdesk
Performanc
e
90% of the
Level 1
Incidents
Monthly Monthly 6 x 9 > 98% > 98% To be
base
lined for
INR 750 per month for every
drop in percentage point of
uptime below 98%
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
31 | P a g e
Service
Category
Service
Level Title
/ Objective
Data Capture Measureme
nt Interval
Reportin
g Period
Hours
of
Suppor
t
Target
Servic
e
Level
Minimu
m
Service
Level
Service
Level
Dependenc
y
Increase
d Impact
Severity Weight
shall be
resolved
within 6
hours from
call received
/ logged
whichever
is earlier
first 6
months
Helpdesk
Performanc
e
90% of the
Level 2
Incidents
shall be
resolved
within 24
hours from
call received
/ logged
whichever
is earlier
Monthly Monthly 6 x 9 > 98% > 98% To be
base
lined for
first 6
months
INR 750 per month for every
drop in percentage point of
uptime below 98%
Helpdesk
Performanc
e
90% of the
Level 3
Incidents
shall be
resolved
within 48
hours from
call received
/ logged
whichever
is earlier
Monthly Monthly 6 x 9 > 98% > 98% To be
base
lined for
first 6
months
INR 750 per month for every
drop in percentage point of
uptime below 98%
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
32 | P a g e
6 Criteria for Evaluation
I. The overall objective of this evaluation process is to select the capable and qualified firm in
the business domain of developing and rolling out a Portal, eDistrict Application, related
hardware and other infrastructure, providing associated capacity building, training and
handholding support as well as associated managed services and who will provide a
comprehensive solution towards Supply, Installation, Integration, Commissioning,
Development, Deployment, Operation & Management of eDistrict Application and hardware
provisioning in Odisha.
II. First the Pre-Qualification Proposal will be evaluated and only those bidders who qualify
the requirements will be eligible for next set of evaluations. Technical Proposal and
Commercial Proposal of Bidders who do not meet the Pre-Qualification criteria will be
returned without opening.
III. The technical score of all the bidders would be calculated as per the criteria mentioned
below. All the bidders who achieve at least 70 marks in the technical evaluation would be
eligible for the next stage, i.e. Financial Bid opening.
IV. Proposals of Companies would be evaluated as per Technical Evaluation Criteria (Section
evidence, with respect to the above, in absence of which their proposals will be rejected
summarily at the qualification stage itself.
6.1 Pre-Qualification Criteria
Sr. No Qualification Criteria Documents/Information to be
provided in the submitted proposal
1. The responding firm / agency
a. Should have made a payment of Rs. 5000 (Rupees Five Thousands only) for the RFP document
b. Should have submitted a EMD of Rs. 80,00,000 (Rupees Eighty Lacs only)
a) Demand Draft for Rs. 5000
b) Demand Draft for Rs. 80,00,000
2. Legal Entity
Company should be registered under Companies Act, 1956
Registered with the Service Tax Authorities Should have been operating for the last
three years (FY 11-12, FY 10-11 and FY 09-10)
a) Certificate of Incorporation
b) Registration Certificate
3. The Firm / Company should be in the business as System Integrator for at least 3 years as of 31st March 2012
a) Annexure I: Form 2 Details of Responding Firm
b) Memorandum & Articles of Association
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
33 | P a g e
Sr. No Qualification Criteria Documents/Information to be
provided in the submitted proposal
c) Work orders confirming year and Area of activity
4. The responding firm shall not be under a
declaration of ineligibility for corrupt or
fraudulent practices.
Self-Declaration by the designated
official as per the format of the
responding firm or Annexure-I: Form
22
5. The Net Worth of the responding firm must be
positive as per the last audited Balance Sheet.
Chartered Accountant Certificate for
Net worth
6. The responding firm should be ISO 9000:2008
certified.
Copy of Relevant Certificate which is
valid on date of submission.
7. The responding firm should be minimum
CMMi Level 3.
Relevant certificate needs to be
attached which is valid on date of
submission.
Additional Requirement
Sl No Requirement State Category Requirements
Documents/ Information to be provided
1 Average Annual Sales Turnover generated from services related to System Integration (SI) during the last three (3) financial years (FY 11-12, FY 10-11 and FY 09-10) as per the last published balance sheets
Rs. 75 Crores or more
a) Extracts from the audited Balance sheet and Profit & Loss; OR
b) Certificate from the
statutory auditor. 2 Company experience in implementation of
integrated turnkey projects around application development as a System Integrator in India.
(Specifically each project should have components of Hardware, Networking, Helpdesk and Application related training necessarily for this project). Refer to the Important Note below for more details. Number of such Assignments of value (as specified for tiers) which have gone live in the past 5 years (FY 11-12, FY 10-11, FY 09-10 FY 08-09 and FY 07-08)
One 40 Crores Project
OR Two 20 Crores Projects OR Three 16 Crores Project
Completed Annexure I: Form 6: Details of Experience of responding firm/ Project Citation for projects supported with Work order and Proof of Go-live/ Project completion certificates from client
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
34 | P a g e
Sl No Requirement State Category Requirements
Documents/ Information to be provided
Note: Value of the project should be 40 Crores if only one project detail is given. Bidder can also provide two (2) project citations of atleast 20 Crores or Three Projects citations of atleast 16 Crores
3 The responding firm must have a minimum number of IT Staff of technically qualified personnel in the domain of systems integration, as on 31st July, 2012 on its roll.
150 Certificate from HR Department for number of technically qualified professionals employed by the company
6.2 Technical Qualification Criteria
I. Technical proposal of the bidders will be opened and evaluated who meets all the
prequalification criteria.
II. The evaluation committee will evaluate the Technical Proposals on the basis of the technical
evaluation criterion as provided below.
S. No Criteria Max Criteria/ Sub
Criteria Marks
1 Past Experience of the responding firm 30
2 Solution proposed for the e-District Project by the responding
firm
40
3 Work Plan approach and proposed methodology 10
4 Adequacy and Quality of Resources proposed for Deployment 20
Total Points 100
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
35 | P a g e
Sl
No.
Criteria/Sub
Criteria
Description Point System Max
Criteria
/ Sub
Criteria
Points
Form to
be used
1 Past Experience of the responding firm 30
a.
System Integration
projects
At least THREE
client
references for
implementation
of an integrated
turnkey project
around a)
network
solution and b)
software
development c)
Hardware
commissioning
and d) O&M
phase for
maintaining all
of the above.
Total Work order value
of three project
>INR 30 Crores = 15
points;
>INR 24 crores but less
than INR 30 crores=10
points;
>INR 18 crores but less
than INR 24 crores=5
points;
>INR 12 crores but less
than INR 18 crores
crores=2 points;
>INR 8 crores but less
than INR 12 crores =1
point; else 0
15
Annexure-
I: Form 6,
supported
by
document
ary
evidence
b.
Hardware
Products
Installation
Whether the
Firm has
delivered
hardware
products in at
least Three
projects of
similar size in
the last 3 years.
Value of hardware only
in three work order:
> INR 60 Crores = 5
points;
>INR 50 crores but
less than INR 60
crores=4 points;
>INR 40 crores but
less than INR 50
crores=3 points;
> INR 30 crores but
less than INR 40
crores=2 points;
>INR 15 crores but
5
Annexur
e-I: Form
6,
supporte
d by
documen
tary
evidence
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
36 | P a g e
Sl
No.
Criteria/Sub
Criteria
Description Point System Max
Criteria
/ Sub
Criteria
Points
Form to
be used
less than INR 30
crores=1 points;
else 0
c. Software Solutions
At least TWO
completed /
ongoing
software
development
projects each
having a
minimum value
of INR 1 crore –
for software
development
component
only). The
project should
have some or all
of the following
components :
– Portal
– Web based
Application
Engine
– Workflow
> 4 Projects – 5
points;
4 Projects - 4 points;
3 Projects - 3 points;
2 Projects - 2 points;
else 0.
5
Annexure-
I: Form 6
supported
by
document
ary
evidence
d.
Maintenance Services and Helpdesk in the State
Providing Maintenance Services / Helpdesk services in the field of IT services with a minimum
In case of any one project done for the following locations : a. covers > 22
districts – 5 points
b. covers > 14
5
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
37 | P a g e
Sl
No.
Criteria/Sub
Criteria
Description Point System Max
Criteria
/ Sub
Criteria
Points
Form to
be used
order size of INR 2 Crores in the State
districts & less than 22 districts – 3 points
c. covers > 7 & less than 14 districts – 1 points else; 0
Note :
1. For all the above, the Completion Certificate of the projects completed
in the last 3 years (as on <31/12/2012>) need to be provided (issued to
the responding firm by the respective customers)
2. The value of the projects considered in the above criterion would be
based on the Purchase Order or the LOI issued to the responding firm. In
absence of the supporting documents, the projects would not be
considered for evaluation
2 Solution proposed 40
a. Proposed solution
Requirements
addressed as
mentioned in
different parts
of the RFP and
the quality of
the solution
Evaluation Committee
will evaluate whether
all the points/
requirements
mentioned in the RFP
are addressed well and
award points
accordingly, the
important parameters
being:-
– Solution architecture
conceptualized for
this project.
– Security architecture
– Detailed plan for
using SWAN as
connectivity
– Application
15
-
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
38 | P a g e
Sl
No.
Criteria/Sub
Criteria
Description Point System Max
Criteria
/ Sub
Criteria
Points
Form to
be used
deployment and
testing Strategy
– Quality Control
Procedures
suggested by
responding firm
– Comprehensiveness
of Bill of material of
all the components
(e.g. software,
hardware, etc.) along
with their quantities
b.
Proposed
Approach and
methodology
Evaluation
Committee will
evaluate
whether the
implementation
methodology is
in line with the
requirement.
The important
parameters
being:-
- Plan for
meeting the
SLA norms.
- Redundancy
and failover
options.
- Spare
equipment
In this section, the
responding firm
should:
– Explain the
understanding of the
project requirements
– highlight the
expected support
from the State
– approach to the
services, SLA
management
methodology
– methodology for
carrying out the
activities for
expected output
– Highlight the
associated risks /
problems and plans
for mitigation and
15
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
39 | P a g e
Sl
No.
Criteria/Sub
Criteria
Description Point System Max
Criteria
/ Sub
Criteria
Points
Form to
be used
availability
plans
explain the technical
approach it would
adopt to address
them
– Explain the
methodologies the
responding firm
proposes to adopt
and highlight the
compatibility of
those methodologies
with the proposed
approach
– Planning and
Building
Infrastructure
(assessment, design,
integration /
migration of existing
Portal infrastructure)
c Training
Proposed
Training and
Change
Management
plan description
to be looked
into
The Evaluation will be
based on:
Proposed Training Schedule
– Plan to develop Training Manuals
– Areas/domains covered
– Number & Quality of personnel to be deployed for training at the site of Implementation of the Project
5
-
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
40 | P a g e
Sl
No.
Criteria/Sub
Criteria
Description Point System Max
Criteria
/ Sub
Criteria
Points
Form to
be used
d
Formation/Locatio
n of Helpdesk &
other manpower
support
Proposed
methodology of
formation of the
manpower
support team.
Operating and
Maintaining
Infrastructure
The Evaluation will be
based on
– Proposed Staff
details
– Areas/domains
covered
5 -
3 Work Plan Approach & Proposed Methodology 10
a. Project
Management
The overall
approach to be
looked into
The overall project
management approach
adopted by the
responding firm to
implement the project
to meet the timelines.
5 -
b. Detailed Work
Plan
The description
and quality of
the work plan to
be looked into.
Evaluation will be
based on the detailed
Project Plan including
day wise, week wise
activities with Work
Breakdown Structures,
Project estimates,
milestones etc.
5 Form 8
4 Resource Deployment 20
a
Quality of CV of the
resources
proposed for the
project
Quality of the
resources
proposed to
work on the
project
Qualification/relevant
certification of the
People Involved
10
Annexure
-I: Form
10
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
41 | P a g e
Sl
No.
Criteria/Sub
Criteria
Description Point System Max
Criteria
/ Sub
Criteria
Points
Form to
be used
b
Quality of District
level as Technical
e-District managers
Quality of
Technical
Support Staff to
be deployed at
the District.
Education
Qualification/ relevant
certification of the
people involved
10
Annexure
-I: Form
10
Total Points 100
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
42 | P a g e
6.3 Commercial Bid Evaluation
I. The Financial Bids of technically qualified bidders (i.e. above 70 marks) will be opened on
the prescribed date in the presence of bidder representatives.
II. Only fixed price financial bids indicating total price for all the deliverables and services
specified in this bid document will be considered.
III. The bid price will include all taxes and levies and shall be in Indian Rupees and mentioned
separately.
IV. Any conditional bid would be rejected.
V. 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 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”.
VI. If there is no price quoted for certain material or service, the bid shall be declared as
disqualified.
VII. In the event that there are 2 or more bidders having the same value in the financial bid, the
bidder securing the highest technical score will be adjudicated as the “Best responsive bid”
for award of the Project.
7 Appointment of System Integrator
7.1 Award Criteria
OCAC will award the Contract to the successful bidder whose financial proposal is the lowest and
would consider it as substantially responsive as per the process outlined above.
7.2 Right to Accept Any Proposal and To Reject Any or All Proposal(s)
OCAC 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 OCAC action.
7.3 Notification of Award
I. Prior to the expiration of the validity period, OCAC 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, OCAC,
may like to request the bidders to extend the validity period of the bid.
II. The notification of award will constitute the formation of the contract. Upon the successful
bidder's furnishing of Performance Bank Guarantee, OCAC will notify each unsuccessful
bidder and return their EMD.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
43 | P a g e
7.4 Contract Finalization and Award
I. The OCAC shall reserve the right to negotiate with the bidder(s) whose proposal has been
most responsive. On this basis the draft contract agreement would be finalized for award &
signing.
II. OCAC may also like to reduce or increase the quantity of any item in the Scope of Work
defined in the RFP. Accordingly total contract value may change on the basis of the rates
defined in the financial proposal.
7.5 Performance Guarantee
I. OCAC will require the selected bidder to provide a Performance Bank Guarantee, within 15
days from the Notification of award, for a value equivalent to 10% of the total cost of
ownership. The Performance Guarantee should be valid for a period of 6 months. The
Performance Guarantee shall be kept valid till completion of the project and Warranty
period. 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, OCAC at its discretion may cancel the
order placed on the selected bidder without giving any notice. OCAC shall invoke the
performance guarantee in case the selected Vendor fails to discharge their contractual
obligations during the period or OCAC incurs any loss due to Vendor’s negligence in
carrying out the project implementation as per the agreed terms & conditions.
7.6 Signing of Contract
After OCAC notifies the successful bidder that its proposal has been accepted, OCAC shall
enter into a contract, incorporating all clauses, pre-bid clarifications and the proposal of the
bidder between OCAC and the successful bidder.
7.7 Failure to Agree with the Terms and Conditions of the RFP
Failure of the successful Bidder to agree with the Terms and Conditions of the RFP shall
constitute sufficient grounds for the annulment of the award, in which event OCAC may
award the Contract to the next best value Bidder or call for new Bids.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
44 | P a g e
8 Annexure
Annexure I: TECHNICAL BID TEMPLATES
The bidders are expected to respond to the RFP using the forms given in this section and all
documents supporting Technical Evaluation Criteria. Technical Proposal shall comprise of following
forms:
Form 1: Undertaking on Total Responsibility
Form 2: Particulars of the Bidder
Form 3: Bank Guarantee for Earnest Money Deposit
Form 4: Compliance Sheet for Pre-Qualification Proposal
Form 5: Letter of Proposal
Form 6: Project Citation Format
Form 7: Proposed Solution
Form 8: Proposed Work Plan
Form 9: Team Composition
Form 10: Curriculum Vitae (CV) of Key Personnel
Form 11: Deployment of Personnel
Form 12: Deviations
Form 13: Manufacturers Authorisation Form
Form 14: Declaration on Source Code and Intellectual Property Rights
Form 15: Undertaking on Patent Rights
Form 16: Undertaking on Compliance and Sizing of Infrastructure
Form 17: Undertaking on Service Level Compliance
Form 18: Undertaking on Deliverables
Form 19: Undertaking on Support to Third Party Solution acceptance and certification
Form 20: Declaration of Activities sub-contracted
Form 21: Undertaking on Exit Management and Transition
Form 22: Declaration that the bidder has not been blacklisted
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
45 | P a g e
Form 1: Undertaking on Total Responsibility
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Self certificate regarding Total Responsibility
This is to certify that we undertake total responsibility for the successful and defect free operation
of the proposed Project solution, as per the requirements of the RFP for eDistrict Project.
Thanking you,
Yours faithfully
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
46 | P a g e
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
E ROC Reference No.
F Details of company registration
G Details of registration with
appropriate authorities for
service tax
H Name, Address, email, Phone
nos. and Mobile Number of
Contact Person
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
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 OCAC
Know all Men by these presents that we < > having our office at <Address> (hereinafter called "the
Bank") are bound unto the OCAC (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 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.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
48 | P a g e
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 upto <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:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
49 | P a g e
Form 4A: Compliance Sheet for Pre-Qualification Proposal
Sr.
No
Qualification
Criteria
Documents/Information
to be provided in the
submitted proposal
Compliance Reference & Page
Number
1. The responding firm /
agency
(a) Should have made
a payment of
Rs.5000(Rupees Five
Thousand only) for
the RFP document
(b) Should have
submitted a EMD of
Rs. 80,00,000
(Rupees Eighty Lacs
only)
a) Demand Draft for
Rs. 5000
b) BG/Demand Draft
for Rs. 80,00,000
Yes/No
2. Legal Entity
Company should
be registered
under Companies
Act, 1956
Registered with
the Service Tax
Authorities
Should have been
operating for the
last three years
(FY 11-12, FY 10-
11 and FY 09-10)
a) Certificate of
Incorporation
b) Registration
Certificate
Yes/No
3. The Firm / Company
should be in the
business as System
Integrator for at least
3 years as of 31st
March 2012
a) Annexure I: Form 2
Details of
Responding Firm
b) Memorandum &
Articles of
Association
c) Work orders
confirming year and
Area of activity
Yes/No
4. The responding firm
shall not be under a
Self-Declaration by the
designated official as per
Yes/No
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
50 | P a g e
Sr.
No
Qualification
Criteria
Documents/Information
to be provided in the
submitted proposal
Compliance Reference & Page
Number
declaration of
ineligibility for
corrupt or fraudulent
practices.
the format of the
responding firm or
Annexure-I: Form 22
5. The Net Worth of the
responding firm must
be positive as per the
last audited Balance
Sheet.
Chartered Accountant
Certificate for Net worth
Yes/No
6. The responding firm
should be ISO
9000:2008 certified.
Copy of Relevant
Certificate which is valid
on date of submission.
Yes/No
7. The responding firm
should be minimum
CMMi Level 3.
Relevant certificate needs
to be attached which is
valid on date of
submission.
Yes/No
8. Average Annual Sales Turnover generated from services related to System Integration (SI) during the last three (3) financial years (FY 11-12, FY 10-11 and FY 09-10) as per the last published balance sheets
Extracts from the audited Balance sheet and Profit & Loss; OR Certificate from the statutory auditor.
Yes/No
9. Company experience in implementation of integrated turnkey projects around application development as a System Integrator in India. (Specifically each project should have components of Hardware, Networking, Helpdesk and Application related training
Completed Annexure I: Form 6: Details of Experience of responding firm/ Project Citation for 3 projects supported with Work order and Proof of Go-live/ Project completion certificates from client
Yes/No
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
51 | P a g e
Sr.
No
Qualification
Criteria
Documents/Information
to be provided in the
submitted proposal
Compliance Reference & Page
Number
necessarily for this project). Refer to the Important Note below for more details. Number of such Assignments of value (as specified for tiers) which have gone live in the past 5 years (FY 11-12, FY 10-11, FY 09-10, FY 08-09 and FY 07-08) Note: Value of the project should be 40 Crores if only one project detail is given. Bidder can also provide two (2) project citations of atleast 20 Crores or Three Projects citations of atleast 16 Crores
10. The responding firm must have a minimum number of IT Staff of technically qualified personnel in the domain of systems integration, as on 31st July, 2012 on its roll.
Certificate from HR Department for number of technically qualified professionals employed by the company
Yes/No
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
52 | P a g e
Form 4B: Compliance Sheet for Technical Proposal
The Technical 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 Technical
proposal
For Technical Evaluation
S.
No.
Specific Requirements Documents Required Compliance Reference &
Page Number
1 Covering Letter for
Technical Proposal
As per Form 5 Yes / No
2 System Functionality:
Meeting the requirements
with respect to the
common functionalities
as described.
A note containing the
Mapping as per information
provided
Yes / No
3 Technology:
Demonstrated robustness
of the technology
deployed across other
installations around the
world, including
– Scalability
– Security
– Ease of
implementation
A note containing details on
a) Solution architecture
b) Security
c) System Performance
d) Supported Platform
Operating System
e) Client Hardware Operating
System
f) Database
g) System Management
h) Web Server Support
i) Application Server Support
j) Single Sign-on
k) Presentation
l) Session Management
m) Integration capabilities
n) Auditing / Reporting
features
o) Disaster recovery & back-
up
And Form 7
Yes / No
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
53 | P a g e
S.
No.
Specific Requirements Documents Required Compliance Reference &
Page Number
4 Industry Specific
Capabilities:
Past experience of the
bidder in executing
similar assignments, size
of those assignments in
the past five years.
[The definition of
“similar” should be such
that it focuses on the
areas which are
“innovative” or where the
technical feasibility is a
challenge in the context
of the project]
Completion Certificates from
the client; OR
Work Order + Self Certificate of
Completion (Certified by the
Statutory Auditor); OR
Work Order + Phase
Completion Certificate (for
ongoing projects) from the
client
Yes / No
5 Training:
Trainings proposed by
the vendor and the
amount of emphasis laid
on Training the
employees schedule
details, locations,
sessions and their
description
A note on training containing
a) Training model
b) Approach
c) Deliverables
Yes / No
7 Profile of proposed
team members:
Relevant assignment
experience / Years of
experience / Number of
Certifications in
Technology specific to
Solution proposed
Form 9,10 and 11 Yes / No
8 Project Methodology,
Support and
Documentation
Form 8 & additional
notes/document for support &
documentation
Yes / No
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
54 | P a g e
S.
No.
Specific Requirements Documents Required Compliance Reference &
Page Number
9 Tools and Assets As per
requirement specified in
Technical evaluation)
Tools and Assets which could
be leveraged for the
assignment [for e.g. Test Case
Builders, Effort Estimators,
PMU Tool, Load testing etc.,
depending on the relevance to
the Scope of work]
A note and demonstration of
the Tool/ Assets
Yes / No
10 Deviations (if any) Form 12 Yes / No
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
55 | P a g e
Form 5: Letter of Proposal
To: <Location, Date>
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Subject: Submission of the Technical bid for <Name of the Systems Implementation assignment>
Dear Sir/Madam,
We, the undersigned, offer to provide Systems Implementation solutions to the OCAC on <Name of
the Systems Implementation 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 180 days as stipulated in the RFP document.
We hereby declare that we are not insolvent, in receivership, bankrupt or being wound up, our
affairs are not being administered by a court or a judicial officer, our business activities have not
been suspended and we are not the subject of legal proceedings for any of the foregoing.
We understand you are not bound to accept any Proposal you receive.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
56 | P a g e
Form 6: Project Citation Format
Relevant IT project experience (provide no more than 5 projects in the last 5 years)
General Information
Name of the project
Client for which the project was executed
Name and contact details of the client
Project Details
Description of the project
Scope of services
Service levels being offered/ Quality of service
(QOS)
Technologies used
Outcomes of the project
Other Details
Total cost of the project
Total cost of the services provided by the
respondent
Duration of the project (no. of months, start
date, completion date, current status)
Other Relevant Information
Letter from the client to indicate the successful
completion of the projects
Copy of Work Order
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
57 | P a g e
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:
a) Solution Proposed
b) Understanding of the project (how the solution proposed is relevant to the understanding)
c) Technical Approach and Methodology
Sl.
No
Proposed Solution
(Provide the Product
Name or fill Custom
Built, in case of a new
development)
Version &
Year of
Release
OEM Feature
s &
Functio
nalities
O&M Support
(Warranty/AT
S/: as
required as
per RFP)
Reference in the
Submitted
Proposal (Please
provide page
number/section
number/ volume)
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
58 | P a g e
Form 8: Proposed Work Plan
No Activity1 Calendar Months
1 2 3 4 5 6 7 8 9 10 11 12 n
1
2
3
4
5
N
1 Indicate all main activities of the assignment, including delivery of reports (e.g.: inception,
interim, and final reports), and other benchmarks such as Purchaser approvals. For phased
assignments indicate activities, delivery of reports, and benchmarks separately for each phase.
2 Duration of activities shall be indicated in the form of a bar chart.
3 All activities should meet the 8/80 criteria i.e should at least take 8 hours and a maximum of 80
hours.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
59 | P a g e
Form 9: Team Composition
Name of Staff with
qualification and
experience
Area of
Expertise
Position
Assigned
Task
Assigned
Time
committed
for the
engagement
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
60 | P a g e
Form 10: Curriculum Vitae (CV) of Key Personnel
General Information
Name of the person
Current Designation / Job Title
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)
Key achievements and other relevant
information (if any)
Professional Certifications (if any)
Total number of years of experience
Number of years with the current company
Summary of the Professional / Domain
Experience
Number of complete life cycle
implementations carried out
The names of customers (Please provide the
relevant names)
Past assignment details (For each assignment
provide details regarding name of
organizations worked for, designation,
responsibilities, tenure)
Prior Professional Experience covering:
Organizations worked for in the past
o Organization name
o Duration and dates of entry and
exit
o Designation Location(s)
o Key responsibilities
Prior project experience
o Project name
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
61 | P a g e
o Client
o Key project features in brief
o Location of the project
o Designation
o Role
o Responsibilities and activities
o Duration of the project
Please provide only relevant projects.
Proficient in languages (Against each language
listed indicate if speak/read/write)
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
62 | P a g e
Form 11: Deployment of Personnel
No Name of Staff Staff input in Months (in the form of a bar chart)2
Total
staff
man-
months
proposed
1 2 3 4 5 6 7 8 9 10 11 12 n Total
1
2
3
N
Total
1. Professional Staff the input should be indicated individually; for Support Staff it should
be indicated by category
2 Months are counted from the start of the assignment.
Full time input Part time input
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
63 | P a g e
Form 12: Deviations
This section should contain any assumption on areas which have not been provided in the
RFP OR any changes to the existing provisions of the RFP
A - On the Terms of Reference
[Suggest and justify here any modifications or improvement to the Scope of Work you are proposing to
improve performance in carrying out the assignment (such as deleting some activity you consider
unnecessary, or adding another, or proposing a different phasing of the activities). Such suggestions
should be concise and to the point, and incorporated in your Proposal.]
B – Any other areas
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
64 | P a g e
Form 13: Manufacturers Authorization Form
(This form has to be provided by the OEMs of the products proposed)
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
OEM Authorization Letter
Dear Sir:
Ref: Your RFP Ref: [*] dated [*]
We who are established and reputable manufacturers / producers of ________________________ having
factories / development facilities at (address of factory / facility) do hereby authorize M/s
___________________ (Name and address of Agent) to submit a Bid, and sign the contract with you
against the above Bid Invitation.
We hereby extend our full guarantee and warranty for the Solution, Products and services offered
by the above firm against this Bid Invitation.
We hereby declare that we are not insolvent, in receivership, bankrupt or being wound up, our
affairs are not being administered by a court or a judicial officer, our business activities have not
been suspended and we are not the subject of legal proceedings for any of the foregoing.
We also undertake to provide any or all of the following materials, notifications, and information
pertaining to the Products manufactured or distributed by the Supplier:
a. Such Products as the Bank may opt to purchase from the Supplier, provided, that this option
shall not relieve the Supplier of any warranty obligations under the Contract; and
b. in the event of termination of production of such Products:
i. advance notification to the Bank of the pending termination, in sufficient time to
permit the Bank to procure needed requirements; and
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
65 | P a g e
ii. Following such termination, furnishing at no cost to the Bank, the blueprints, design
documents, operations manuals, standards, source codes and specifications of the
Products, if requested.
We duly authorize the said firm to act on our behalf in fulfilling all installations, Technical support
and maintenance obligations required by the contract.
Yours faithfully,
Name:
Name of Producers:
Note: This letter of authority should be on the letterhead of the manufacturer and should be signed
by a person competent and having the power of attorney to bind the manufacturer. The Bidder in
its Bid should include it.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
66 | P a g e
Form 14: Declaration on Source Code and Intellectual Property Rights
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Self-certificate regarding the source code and Intellectual property rights under this
Project
I, authorized representative of _________________________, hereby solemnly affirm to the IPR and Source
Code rights as defined in Part III of this RFP document.
In the event of any deviation from the factual information/ declaration, OCAC reserves the right to
terminate the Contract without any compensation to the System Integrator.
Thanking you,
Yours faithfully
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
67 | P a g e
Form 15: Undertaking on Patent Rights
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Undertaking on Patent Rights
1. I/We as System Integrator (SI) do hereby undertake that none of the
deliverables being provided by us is infringing on any patent or intellectual and industrial
property rights as per the applicable laws of relevant jurisdictions having requisite
competence.
2. I/We also confirm that there shall be no infringement of any patent or intellectual and
industrial property rights as per the applicable laws of relevant jurisdictions having requisite
competence, in respect of the equipments, systems or any part thereof to be supplied by us. We
shall indemnify OCAC against all cost/claims/legal claims/liabilities arising from third party
claim in this regard at any time on account of the infringement or unauthorized use of
patent or intellectual and industrial property rights of any such parties, whether such claims
arise in respect of manufacture or use. Without prejudice to the aforesaid indemnity, the
SI shall be responsible for the completion of the supplies including spares and uninterrupted
use of the equipment and/or system or any part thereof to OCAC and persons authorized by
OCAC, irrespective of the fact of claims of infringement of any or all the rights mentioned above.
3. If it is found that it does infringe on patent rights, I/We absolve OCAC of any legal
action.
Yours faithfully,
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
68 | P a g e
Form 16: Undertaking on Compliance and Sizing of Infrastructure
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Undertaking on Compliance and Sizing of Infrastructure
1. I/We as System Integrator do hereby undertake that we have proposed and sized the
hardware and all software (including perennial and enterprise wide licenses, unless
stated otherwise) based on information provided by OCAC in its RFP document and
in accordance with the service level requirements and minimum specifications
provided and assure OCAC that the sizing is for all the functionality envisaged in the
RFP document.
2. Any augmentation of the proposed solution or sizing of any of the proposed solutions
(including software and hardware) in order to meet the minimum RFP
requirements and/or the requisite service level requirements given by OCAC will
be carried out at no additional cost to OCAC during the entire period of Contract.
Yours faithfully,
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
69 | P a g e
Form 17: Undertaking on Service Level Compliance
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Undertaking on Service Level Compliance
1. I/We as System Integrator do hereby undertake that we shall monitor, maintain, and
comply with the service levels stated in the RFP to provide quality service to
OCAC.
2. However, if the proposed resources and infrastructure are found to be insufficient in
meeting the RFP and/or the service level requirements given by OCAC, then we will
augment the same without any additional cost to OCAC.
Yours faithfully,
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
70 | P a g e
Form 18: Undertaking on Deliverables
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Undertaking on Deliverables
1. I/We as System Integrator do hereby undertake that processes, deliverables/artifacts
submitted to OCAC will adhere to the quality and standards specified in this RFP.
2. We also recognize and undertake that the deliverables/artifacts shall be
presented and explained to OCAC and other key stakeholders (identified by OCAC), and also
take the responsibility to provide clarifications as requested by OCAC.
3. We agree to abide by the procedures laid down for acceptance and review of deliverables
/ artifacts by the Department as stated in this RFP or as communicated to us from time-to-time.
4. We also understand that the acceptance, approval and sign-off of the deliverables by
OCAC will be done on the advice of Department and any other agency appointed by the
Department for the same. We understand that while all efforts shall be made to accept and
convey the acceptance of each deliverable in accordance with the Project schedule, no
deliverable will be considered accepted until a specific written communication to that effect
is made by OCAC.
Yours faithfully,
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
71 | P a g e
Form 19: Undertaking on Support to Third Party Solution acceptance and certification
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Undertaking on Support to Third Party Solution Acceptance and Certification
1. I/We understand that the System (including the application and the associated IT
systems) may be assessed and certified by a 3rd party agency (to be identified by
OCAC) before the system is commissioned.
2. I/We understand that while the certification expenses will be borne by OCAC,
the responsibility to ensure successful acceptance and certification lies with the System
Integrator.
3. I/We hereby undertake that we shall do all that is required of the System
Integrator to ensure that system will meet all the conditions required for successful
acceptance and certification.
Yours faithfully,
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
72 | P a g e
Form 20: Declaration of activities sub-contracted
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Declaration on Sub-contracting
I/ We hereby declare the following list of activities which we would be sub-contracted.
S. No. Activity
1
2
3
4
I/ We would be responsible for ensuring that the sub-contracted work meets the requirements of
the Department.
Thanking you,
Yours faithfully
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
73 | P a g e
Form 21: Undertaking on Exit Management and Transition
No. Date:
To:
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Dear Sir,
Sub: Undertaking on Exit Management and Transition
I/We hereby undertake that at the time of completion of o u r engagement with the Department, either at the End of Contract or termination of Contract before planned Contract Period for any reason, we shall successfully carry out the exit management and transition of this Project to the OCAC or to an agency identified by OCAC to the satisfaction of the Department. I/We further undertake to complete the following as part of the Exit management and transition:
a. We undertake to complete the updation of all Project documents and other artefacts and handover the same to OCAC before transition.
b. We undertake to design standard operating procedures to manage system (including application and IT systems), document the same and train OCAC personnel on the same.
c. If Department decides to take over the operations and maintenance of the Project on its own or identifies or selects any other agency for providing operations & maintenance services on this Project, then we shall provide necessary handholding and transition support, which shall include but not be limited to, conducting detailed walkthrough and demonstrations for the IT Infrastructure, handing over all relevant documentation, addressing the queries/clarifications of the new agency with respect to the working / performance levels of the infrastructure, conducting Training sessions etc.
I/We also understand that the Exit management and transition will be considered complete on the basis of
approval from OCAC.
Yours faithfully,
(Signature of the Authorized signatory of the Bidding Organisation)
Name :
Designation :
Date :
Time :
Seal :
Business Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
74 | P a g e
Form 22: Declaration that the bidder has not been blacklisted
(To be submitted on the Letterhead of the responding agency)
{Place}
{Date}
To,
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Ref: RFP Notification no <xxxx> dated <dd/mm/yy>
Subject: Self Declaration of not been blacklisted in response to the RFP for Selection of
System Integrator for Statewide Roll-out of e-District MMP.
Dear Sir,
We confirm that our company, ____________, is not blacklisted in any manner whatsoever by any of
the State/UT and/or central government in India on any ground including but not limited to
indulgence in corrupt practice, fraudulent practice, coercive practice, undesirable practice or
restrictive practice.
Place:
Date:
Bidder’s Company Seal:
Authorized Signatory’s Signature:
Authorized Signatory’s Name and Designation:
Note: The Bidder shall necessarily provide a copy of ‘Power of Attorney’ authorizing the signatory
for signing the Bid on behalf of the Bidder in its Pre-Qualification Bid.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
75 | P a g e
ANNEXURE II: FINANCIAL PROPOSAL TEMPLATE
Form 1: Covering Letter
To:
<Location, Date>
General Manager, Odisha Computer Application Centre (OCAC), (Technical Directorate under IT Department, Govt. of Odisha), OCAC Building, Plot No. N-1/7D, Acharya Vihar Square, RRL Post Office, Bhubaneswar – 751 013, Odisha
Subject: Submission of the Financial bid for <Provide Name of the Implementation Assignment>
Dear Sir/Madam,
We, the undersigned, offer to provide the Implementation services for <Title of
Implementation 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 the local taxes.
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 180 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.
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. DEVIATIONS
We declare that all the services shall be performed strictly in accordance with the Tender
documents except for the variations and deviations, all of which have been detailed out
exhaustively in the following statement, irrespective of whatever has been stated to the contrary
anywhere else in our bid.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
76 | P a g e
Further we agree that additional conditions, if any, found in the Tender documents, other than
those stated in deviation schedule, shall not be given effect to.
4. TENDER PRICING
We further confirm that the prices stated in our bid are in accordance with your Instruction to
Bidders included in Tender documents.
5. QUALIFYING DATA
We confirm having submitted the information as required by you in your Instruction to Bidders.
In case you require any other further information/documentary proof in this regard before
evaluation of our Tender, we agree to furnish the same in time to your satisfaction.
6. BID PRICE
We declare that our Bid Price is for the entire scope of the work as specified in the RFP. These
prices are indicated Commercial Bid attached with our Tender as part of the Tender.
7. 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 <Form 3> 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 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,
Authorized Signature:
Name and Title of Signatory:
Name of Firm:
Address:
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
77 | P a g e
Form 2: Financial Proposal
Summary of Total Project Cost- Component Wise
Sl No. Project Expenditure Heads Reference to other tables Cost
Software Development Cost
1. Application Software
Development Form 2.1. INR 0.00
Integration Cost
2 Integration Components Form 2.2 INR 0.00
Hardware & Networking Cost
3. Hardware Form 2.3+Form 2.4+ Form 2.5 + Form 2.6 +
Form 2.7+ Form 2.8 INR 0.00
System Software
4. System Software Cost Form 2.9 INR 0.00
Connectivity
5. Broadband Connectivity Form 2.10 INR0.00
Training Cost
6. Stakeholder Training Cost Form 2.11 INR 0.00
Application Support Cost
7. Application Support Cost for
3 years after Go-Live Form 2.12 INR 0.00
Technical Support Staff
8. Technical Support Staff Form 2.13
Other Project Related Costs
9. Other Costs Form 2.14 INR 0.00
Total e-District Solution Cost INR 0.00
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
78 | P a g e
Form 2.1: Software Development Commercial Format
Module
Requirement
Analysis SRS SDD Development Testing Deployment &
Implementation
Oth
er
Co
st
To
tal
Mo
du
le C
ost
R2
Spec
ify
oth
er
reso
urc
e ty
pes
R3
Spec
ify
oth
er
reso
urc
e ty
pes
R3 R4 R 9
Spec
ify
oth
er
reso
urc
e ty
pes
R3 R 10
Spec
ify
oth
er
reso
urc
e ty
pes
R 12 R5
Spec
ify
oth
er
reso
urc
e ty
pes
R6
Spec
ify
oth
er
reso
urc
e ty
pes
Module-1
En
ter
man
m
on
ths
for
reso
urc
e ty
pe
En
ter
man
m
on
ths
for
re
sou
rce
typ
e
Module-2
***
Total Cost
Unit cost per resource should be mentioned in the below table.
Resource Type Role Unit
Rate
Resource Type Role Unit
Rate
R1 Project Manager
R7 Help Desk Resource
R2 System/Business Analyst
R8 Maintenance & Support Engineer
R3 Sr. Software Engineer
R9 Solution Architect
R4 Database Expert
R10 Developer
R5 Software Testing Expert
R11 Data Migration Specialist
R6 Implementation Engineer
R12 System Integration Tester
In order to meet the project requirements, it may be necessary to carry out modification /customization to the proposed solution. The above quoted amount shall be used if State Designated Agency wants to carry out any modification/customization activities later. The rates will be applicable for the entire duration of the contract period.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
79 | P a g e
Form 2.2: Integration Cost Commercial Format
A B C D
Software Item Cost/Unit Tax (If any) No. of Units Cost per Software item (A+B)xC
Development of Connectors for
SSDG
INR 0.00 INR 0.00
Mobile enablement of eDistrict
Application
INR 0.00 INR 0.00
Integration with NSDG INR 0.00 INR 0.00
Payment Gateway Integration INR 0.00 INR 0.00
E-Authentication with
AADHAR
INR 0.00 INR 0.00
Localisation of Application INR 0.00 INR 0.00
Total Cost for Integration INR 0.00
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume I
80 | P a g e
Form 2.3: Commercial Format for Equipment’s at SDC, Bhubaneswar
Sl
No. Item
Description
Unit Price
(P)
Tax
(t)
Total
amount/unit
T=(P+t)
Total Qty
(Q)
Total
amount
T*Q
Remarks
1 Server For Helpdesk and SLA INR 0.00 INR 0.00 INR 0.00 2 Nos. INR 0.00
2 Server for Antivirus INR 0.00 INR 0.00 INR 0.00 1 Nos. INR 0.00
2.3.1.1 System Study and Design ...................................................................................................................... 12 2.3.1.2 Preparation of Software Requirements Specifications (SRS) ................................................................. 13 2.3.1.3 Preparation of e-District Project Plan .................................................................................................... 14 2.3.1.4 Preparation of e-District Application Design Documents ...................................................................... 14 2.3.1.5 Sign off Deliverables ............................................................................................................................. 14
2.3.2 Software Development/Customization .................................................................................... 15 2.3.2.1 E-District Application ............................................................................................................................. 15 2.3.2.2 List of Services (e-District Functional Modules) ................................................................................... 15 2.3.2.3 Single-Sign On ...................................................................................................................................... 20 2.3.2.4 Support for PKI based Authentication and Authorization .................................................................... 20 2.3.2.5 Interoperability Standards .................................................................................................................... 20 2.3.3.6 Scalability ............................................................................................................................................. 20 2.3.2.7 Security ................................................................................................................................................ 21 2.3.2.8 Application Architecture ...................................................................................................................... 21 2.3.2.9 Proposed Application Architecture ...................................................................................................... 22 2.3.2.10 High Level Design (HLD) .................................................................................................................... 22 2.3.2.11 Detailed (Low Level) Design (LLD) ..................................................................................................... 22 2.3.2.12 Test Plan ............................................................................................................................................ 23 2.3.2.13 Requirement on Adherence to Standards ........................................................................................ 23 2.3.2.14 Compliance with Industry Standards ................................................................................................ 23 2.3.2.15 Specification ..................................................................................................................................... 23 2.3.2.16 Sign-off Deliverables ......................................................................................................................... 24
2.3.8.1 Sign-off Deliverables ............................................................................................................................. 27 2.3.9 Supply / Procurement of IT Infrastructure at SDC .................................................................. 28 2.3.10 Hardware Commissioning at Field Offices ............................................................................... 28
2.3.10.1 Design, Supply, Installation, Commissioning, O & M of IT Infrastructure ......................................... 28 2.3.10.2 Installation and Commissioning of IT Infrastructure ......................................................................... 29
2.3.11 Licenses ..................................................................................................................................... 29 2.3.12 Capacity Building / Training.................................................................................................... 29
2.3.16.1 Project Planning and Management .......................................................................................................... 37 2.3.16.2 Project Planning and Management .......................................................................................................... 38
2.4 SCOPE OF SERVICES - OPERATION AND MAINTENANCE PHASE .................................................................. 39 2.4.1 OVERVIEW OF POST IMPLEMENTATION SERVICES ................................................................................ 39 2.4.2 WARRANTY SUPPORT ....................................................................................................................... 40 2.4.3 ANNUAL TECHNICAL SUPPORT .......................................................................................................... 41
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
3 | P a g e
2.4.4 HELP DESK AND TROUBLE TICKET MANAGEMENT SYSTEM .................................................................... 42 2.4.5 GENERAL REQUIREMENTS ................................................................................................................. 43 2.4.6 EXIT MANAGEMENT ......................................................................................................................... 44
2.4.6.1 Purpose ................................................................................................................................................ 44 2.4.6.2 Transfer of Assets .................................................................................................................................. 44 2.4.6.3 Cooperation and Provision of Information ........................................................................................... 45 2.4.6.4 Confidential Information, Security and Data ......................................................................................... 45 2.4.6.5 Employees ............................................................................................................................................. 46 2.4.6.6 Transfer of Certain Agreements ............................................................................................................ 46 2.4.6.7 Rights of Access to Premises ................................................................................................................. 46 2.4.6.8 General Obligations of the SI................................................................................................................. 47 2.4.6.9 Exit Management Plan .......................................................................................................................... 47
3 DETAILED IMPLEMENTATION AND ROLL-OUT PLAN ................................................................... 49
4.1 OFFICE WISE REQUIREMENTS ............................................................................................................... 50 4.2 TEMPLATE FOR CAPTURING NETWORK CONNECTIVITY REQUIREMENT ...................................................... 52 4.3 FRS FOR THE PROPOSED APPLICATION .................................................................................................. 54
4.3.1 Information Dissemination Component .................................................................................. 55 4.3.2 Forms Availability Component ................................................................................................. 57 4.3.3 Application Receipt Component ............................................................................................... 59 4.3.4 Payment Component ................................................................................................................ 60 4.3.5 Application Processing Component ......................................................................................... 62 4.3.6 Verification Component ............................................................................................................ 63 4.3.7 Approval/Rejection Component (Intermediary Approver and Final Approver) .................... 64 4.3.8 Delivery Component ................................................................................................................. 66 4.3.9 Status Component ..................................................................................................................... 68 4.3.10 Monitoring Component (MIS) ....................................................................................................... 70 4.3.11 Log in Component .......................................................................................................................... 72 4.3.12 Service Specific Functionalities ..................................................................................................... 73
4.4 BILL OF MATERIAL SUMMARY ............................................................................................................... 76 4.4.1 Requirement at Field Level Offices ........................................................................................... 76 4.4.2 Requirement at SDC ................................................................................................................. 77
4.5 TECHNICAL SPECIFICATIONS ................................................................................................................. 78 4.5.1 Server for Web, Database, Application .................................................................................... 78 4.5.2 Specification for servers for Helpdesk, SLA and Antivirus ....................................................... 79
4.5.2.1 Specification of Blade chasis ................................................................................................................ 79 4.5.2.2 Specification of Servers ........................................................................................................................ 80
4.5.2 Desktop ..................................................................................................................................... 81 4.5.3 Laptops ..................................................................................................................................... 82 4.5.4 Scanner ..................................................................................................................................... 83 4.5.5 Laser Jet Printer, Scanner, Copier all in one Device ................................................................. 84 4.5.6 Laser Printers ........................................................................................................................... 86 4.5.7 UPS – 1 KVA offline UPS ........................................................................................................... 87 4.5.8 9 U Rack .................................................................................................................................... 89 4.5.9 Biometric Device ....................................................................................................................... 90 4.5.10 24 Port Managed LAN Switch ....................................................................................................... 91 4.5.11 Specification of SLA and Helpdesk Software ................................................................................. 93 4.5.12 Specification of Antivirus software ............................................................................................... 96
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
4 | P a g e
GLOSSARY OF TERMS
The definitions of various terms that have been used in this RFP are as follows:
“Request for Proposal (RFP)” means all three Volumes and its annexures and any other documents provided along with this RFP or issued during the course of the selection of bidder, seeking a set of solution(s), services(s), materials and/or any combination of them.
“Contract / Agreement / Contract Agreement / Master Service Agreement” means the Agreement to be signed between the successful bidder and OCAC, including all attachments, appendices, all documents incorporated by reference thereto together with any subsequent modifications, the RFP, the bid offer, the acceptance and all related correspondences, clarifications, presentations.
“Bidder” means any firm offering the solution(s), service(s) and /or materials as required in the RFP. The word Bidder when used in the pre-award period shall be synonymous with parties bidding against this RFP, and when used after award of the Contract shall mean the successful party with whom the agreement is signed for rendering of services for implementation of this project.
“Proposal / Bid” means the Pre-Qualification, Technical and Commercial bids submitted for this project against this RFP.
“Acceptance” means the Government’s written certification that following installation, the system(s) (or specific part thereof) has been tested and verified as complete and/or fully operational, in accordance with the acceptance test defined in the Acceptance Test Documents.
“Acceptance Test Documents” means a mutually agreed document which defines procedures for testing the functioning of the e-District system, against requirements laid down in the agreement. It should define tests to be carried out, test equipments and expected test results.
“Authorized Representative” shall mean any person/agency authorized by either of the parties.
“Contract” is used synonymously with agreement.
“Documentary evidence” means any matter expressed or described upon any substance by means of letters, figures or marks intended to be used for the recording of that matter and produced before a court.
“GoI” shall mean Government of India
“Gov./GoO/Government/Govt. of Odisha” shall mean Government of Odisha.
“Law” shall mean any Act ,notification, bye law ,rules and regulations, directive, ordinance, order or instruction having the force of law enacted or issued by the Government of India or State Government or regulatory authority or political sub-division of government agency.
“LOI” means issuing of Letter of Intent which shall constitute the intention of the Tenderer to place the purchase order with the successful bidder.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
5 | P a g e
“OCAC” stands for the Odisha Computer Application Centre, a Society registered under the
Societies Registration Act 1962, having its registered office at OCAC Building, Plot No. N-1/7-D, Acharya Vihar Square, RRL Post, Bhubaneswar, PIN. 751 013 (Technical Directorate of I.T. Department, Govt. of Odisha. The term includes its successors and assigns thereof. OCAC acts as the State Designated Agency for the project.
“OEM” means Original Equipment Manufacturer company, that is incorporated in India or abroad, who has management control over the manufacturing/production process, Quality Assurance, Procurement of Raw materials/manufacturing process inputs marketing and warranty services of the resultant products, of at least one manufacturing facility /factory where the manufacturing of equipment, related accessories, as required for the e- District, Odisha etc. is carried out.
“Party” shall mean Govt. or Bidder individually and “Parties” shall mean Govt. and Bidder collectively.
“PBC” means Pre-Bid Conference
“Rates/Prices” means prices of supply of equipment and services quoted by the Bidder in the Commercial Bid submitted by him and/or mentioned in the Contract
“RFP” means the detailed notification seeking a set of solution(s) ,service(s), materials and/or any combination of them
“Services” means the work to be performed by the Bidder pursuant to this Contract, as detailed in the Scope of Work
“Site” shall mean the location(s) for which the Contract has been issued and where the service shall be provided as per Agreement
“Tenderer” shall mean the authority issuing this Request For Proposal (RFP) and the authority under whom the e-District, Odisha is to be implemented, operated, managed etc. and this authority shall be the Odisha Computer Application Centre, acting on behalf of Govt. of Odisha as the implementing agency for the ‘e-District, Odisha project.
“Termination notice” means the written notice of termination of the Agreement issued by one party to the other in terms hereof.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
6 | P a g e
1 Implementation Framework
I. e-District project shall be implemented in a way where the districts will play a major
role. e-District shall be implemented in alignment with the NeGP principle of
“centralized planning and decentralized implementation”. State IT Department/ Nodal
Agency shall play a key role in planning and implementation of the program in
collaboration with the district.
II. The role of the DeitY, GoI focuses primarily in planning of national level roll out, issuing
guidelines, funding support to the states, monitor and support the state in
implementation of the project. States shall drive the implementation at the state/district
level. The diagram illustrating the key stakeholders and their role in implementation and
for managing the eDistrict MMP is shown below:
III. An Integrated Service Delivery Framework has been designed by DeitY in July 2012,
and communicated to all the States. It can be accessed at (URL:
http://deity.gov.in/content/e-district-guidelines). This framework envisages a
centralized architecture for each major e-Governance application at the State level. The
application software will be hosted in the State Data Centre. Integration across States
shall be enabled, through mandatory adherence to technical specifications and e-
Governance standards, besides use of the SSDG. Compliance to latest Unicode standard
(current version is 6.0) for local language content/data encoding is also mandatory. The
Integrated Framework shall be treated as part of this RFP and shall be followed with
XI. Complete mobile enablement of the e-District applications and services including all
appropriate channels such as SMS / USSD / IVRS and development of corresponding
mobile applications to the eDistrict applications and services leveraging the Mobile
Service Delivery Gateway (MSDG) and the Mobile App Store developed by DeitY
XII. Operation and Maintenance of eDistrict Application including the suggested changes
as indicated by the states for 3 years from the date of Go-Live
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
20 | P a g e
XIII. Implement / add any additional forms of State Departments as and when the depart-
ments are ready for delivering.
XIV. The Intellectual Property Rights of all the software code, data, algorithms, documenta-
tion, manuals, etc. generated as a part of implementation of this project shall solely
vest with OCAC.
XV. Detailed User and Operational Manual to be provided to each department, whose ser-
vices will be hosted on eDistrict Application.
XVI. The application should have a web interface and should publish online transaction
volume data for each service for each district & CSC.
2.3.2.3 Single-Sign On
The application should enable single-sign-on so that any user once authenticated and
authorized by system is not required to be re-authorized for completing any of the services in
the same session. For employees of the department concerned, the browser based application
accessed on the intranet, through single-sign-on mechanism, will provide access to all the
services of the departments concerned (based on their roles and responsibilities), Help module,
basic and advanced reporting etc. Similarly, for external users (citizens, etc), based on their
profile and registration, the system should enable single-sign on facility to apply for various
services, make payments, submit queries /complaints and check status of their applications.
2.3.2.4 Support for PKI based Authentication and Authorization
The solution should support PKI based Authentication and Authorization, in accordance with
IT Act 2000, using the Digital Certificates issued by the Certifying Authorities (CA) such as
MTNL or NIC. In particular, 3 factor authentication (login id & password, biometric and digital
signature) shall be implemented by the selected Bidder for officials/employees involved in
processing citizen services.
2.3.2.5 Interoperability Standards
Keeping in view the evolving needs of interoperability, especially the possibility that the
solution shall become the focal point of delivery of services, and may also involve cross-
functionality with the e-Government projects of other departments / businesses in future, the
solution should be built on Open Standards. The SI shall ensure that the application developed
should easily integrate with the existing applications of other eGovernance initiatives of the
state. Every care shall be taken to ensure that the code does not build a dependency on any
proprietary software, particularly, through the use of proprietary ‘stored procedures’ belonging
to a specific database product.
2.3.3.6 Scalability
One of the fundamental requirements of the proposed application is its scalability. The
architecture should be proven to be scalable (cater to increasing load of internal and external
users and their transactions) and capable of delivering high performance for at-least four years
from the date of deployment. In this context, it is required that the application and deployment
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
21 | P a g e
architecture should provide for Scale-Up and Scale out on the Application and Web Servers,
Database Servers and all other solution components.
2.3.2.7 Security
The systems implemented for project should be highly secure, considering that it is intended to
handle sensitive data relating to the citizens of the state. The overarching security
considerations are described below.
I. The security services used to protect the solution shall include: Identification,
Authentication, Access Control, Administration and Audit and support for industry
standard protocols.
II. The solution shall support advanced user authentication mechanisms including digital
certificates and biometric authentication.
III. Security design should provide for a well-designed identity management system,
security of physical and digital assets, data and network security, backup and recovery
and disaster recovery system.
IV. The solution should provide for maintaining an audit trail of all the transactions and
should also ensure the non-repudiation of audit trail without impacting the overall
performance of the system.
V. The overarching requirement is the need to comply with ISO 27001 standards of
security.
VI. The application design and development should comply with OWASP top 10 principles
2.3.2.8 Application Architecture
I. It has been proposed that the applications designed and developed for the departments
concerned must follow some best practice and industry standards. In order to achieve
the high level of stability and robustness of the application, the system development life
cycle must be carried out using the industry standard best practices and adopting the
security constraints for access and control rights. The various modules / application
should have a common Exception Manager to handle any kind of exception arising due
to internal/ external factors.
II. Similarly the modules of the application are to be supported by the Session and
Transaction Manager for the completeness of the request and response of the client
request. The system should have a module exclusively to record the activities/ create
the log of activities happening within the system / application to avoid any kind of
irregularities within the system by any User / Application.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
22 | P a g e
2.3.2.9 Proposed Application Architecture
A 3-tier architecture (also referred to as multi-tier or N-tier architecture) has been proposed
for the Application Solution. The entire processing should take place in n-tier architecture:
I. Front-end software (client tier): - Existing application is running as a separate portal.
Services which are available under e-District and SSDG, the e-District application
should integrate with the e-form developed under SSDG for that service and use the
standard connectors provided for this purpose by the SSDG project to connect with
the e-District application for end to end integration.
For services under e-District project which are not taken up under SSDG project, the e-form to be developed under e-District project and should use the standard connectors provided for this purpose by the SSDG project to connect with the e-District applica-tion for end to end integration. As SSDG is not operational the Bidder will take necessary action at his end to integrate the application with NSDG.
II. Application and Web Layer – Application server would be used as middle tier for var-
ious web based applications. It would take care of the necessary workflow and Web
server would be required for the interfacing with the end user. Both the web and appli-
cation server would be seamlessly integrated to provide high availability and perfor-
mance. These servers would be installed and operated in clustered configuration to en-
sure high availability and reliability.
III. Database Layer - The application will be hosted on database which will contain all the
data of the application. Since this data will be centralized and is very critical, the server
would be installed and operated in clustered configuration to ensure high availability
and reliability. The data would be physically stored on an External Fiber Channel (FC)
based Storage (SAN).
2.3.2.10 High Level Design (HLD)
SI shall complete the High Level Designing and all HLD documents of all the functionalities,
integration with existing application and external application. The SI shall prepare the HLD
and have it reviewed and approved by the OCAC. State Nodal Office will sign off on the HLD
documents based on the advice of SPMU.
2.3.2.11 Detailed (Low Level) Design (LLD)
The LLD shall interpret the approved HLD to help application development and shall include
detailed service descriptions and specifications, application logic (including “pseudo code”) and
UI design (screen design and navigation). The preparation of test cases will also be completed
during this stage. The SI shall have the design documents reviewed and approved by the state
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
23 | P a g e
Nodal Agency. State Nodal Agency will sign off on the LLD documents based on the advice of
SPMU.
2.3.2.12 Test Plan
The SI shall prepare all necessary Test Plans (including test cases), i.e., plans for Acceptance
Testing. Test cases for Initial and Final User Acceptance Testing shall be developed in
collaboration with domain experts identified at the state nodal agency. Initial and Final User
Acceptance Testing shall involve Test Case development, Unit Testing, Integration and System
Testing, Functional testing of Application, Performance testing of the Application including
measurement of all Service Levels as mentioned in this RFP and finally SI shall also carryout
Load/ Stress testing. The SI will submit the test plans and test result reports to the state nodal
agency for comprehensive verification and approval.
2.3.2.13 Requirement on Adherence to Standards
eDistrict application must be designed following open standards, and in line with overall system
requirements set out in this RFP, in order to provide for good inter-operability with multiple
platforms and avoid any technology or technology provider lock-in.
2.3.2.14 Compliance with Industry Standards
In addition to above, the proposed solution has to be based on and compliant with industry
standards (their latest versions as on date) wherever applicable. This will apply to all the
aspects of solution including but not limited to design, development, security, installation, and
testing. There are many standards that are summarized below. However the list below is just
for reference and is not to be treated as exhaustive.
I. Portal development W3C specifications
II. Information access/transfer protocols SOAP, HTTP/HTTPS
III. e-District DeitY, GoI guidelines.
IV. Photograph JPEG (minimum resolution of 640 x 480 pixels)
V. Scanned documents TIFF (Resolution of 600 X 600 dpi)
VI. Biometric framework BioAPI 2.0 (ISO/IEC 19784-1:2005)
VII. Latest HTML standards
2.3.2.15 Specification
I. Finger print scanning IAFIS specifications
II. Digital signature RSA standards
III. Document encryption PKCS specifications
IV. Information Security to be ISO 27001 compliant
V. Operational integrity & security management to be ISO 17799 compliant
VI. IT Infrastructure management ITIL / EITM specifications
VII. Service Management ISO 20000 specifications
VIII. Project Documentation IEEE/ISO specifications for documentation
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
24 | P a g e
IX. The SI shall adhere to all the standards published by the Department of
Electronics and Information Technology, Government of India.
2.3.2.16 Sign-off Deliverables
I. System Requirement Specification (SRS)
II. Functional Requirement Specification (FRS) (if, updated)
III. High Level and Low Level Design
IV. Functional and non-functional testing
V. Fully functional eDistrict Application
VI. User and Operational Manual for e-District Application
2.3.3 Obtain STQC Certification for eDistrict Application
The SI will be responsible for engaging STQC to conduct the assessment / review for the
system before “Go Live”. The SPMU shall have the right to audit and inspect all the procedures
and systems relating to the provisioning of the services. If there is any change /addition in the
application’s functionality then the SI will have to obtain the STQC Certification for the changes
/ additions. SI shall ensure the following points are duly addressed for successful completion of
STQC Certification.Successful completion of Application Audit. Application audit will include;
A. Functionality audit that will map the functionality delivered to the FRS agreed upon
during development phase.
B. Identify the nature and type of transactions being processed by the application sys-
tems.
C. Determine systematic measures implemented to control and secure access to the ap-
plication programs and data including password controls, user authentications, roles
and responsibilities, audit trails and reporting, configuration and interface controls,
etc.
D. Review of database structure including:
1. Classification of data in terms of sensitivity & levels of access 2. Security measures over database installation, password policies and user
roles and privileges
3. Access control on database objects – tables, views, triggers, synonyms, etc.
4. Database restoration and recoverability
5. Audit trails configuration and monitoring process
6. Network connections to database
E. Review of Network and Website will include:
1. Penetration and vulnerability testing
2. Security exposures to internal and external stakeholders
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
25 | P a g e
F. Definition and Implementation of Security Policies and Controls will include:
1. Define and implement backup process, including schedule, storage, archival
and decommissioning of media
2. Define physical access controls review (over DC and other critical area)
3. Define IT Change Management process, Incident Management process –
Payment against the service Payment against the dues / payments as defined under service charter of the specific service
9. The system should record and maintain all details of payment against a unique service application number
10. The system should be able to maintain all the payment records in a database and retrieve the same as and when required.
11. The system should be able to open a page with declaration on successful payment output
12. The system should able to record specific payment details on the service request form after successful payment has been made
13. The system should be such that it should allow for part payment function
14.
The system should be able to retrieve information of first part payment during the final delivery of service output for final payment as per the overall payment specified for service request
Unique application number for requested service CSC details and unique number for CSC
15. The system should be able follow the payment cycle as mentioned above for the final payment also
16. The system should be able to maintain all records of part payments as well as consolidated payment amount against the service request
17. The system should support multi-lingual interface (minimum Hindi, Oriya and English) as per localization and language
technology standards for National e-Governance plan defined in the e-District guidelines
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 62 | P a g e
4.3.5 Application Processing Component
This component deals with the processing of the application by the concerned authorities.- This component deals with the preparation of
the Case file, noting and forwarding of the same to the Approver.
5. The system should ask for unique service request number / unique application number to retrieve specific service delivery
6. The system should provide for the printable version of the service output
7. The system should be able to print the unique kiosk number, unique application number on the every service output generated
through it
8. The system should be able to print the url of the site from where the content of the service delivery could be verified
9. The system should have adequate security features built in the architecture of the system to ensure that it cannot be
manipulated
10. The system should open new page specifying error in case of incorrect digital verification
11. The system should be able to maintain the database of the all the service delivery output in a logical manner to ease the retrieval
of the same as and when required
12. The system should have a life counter to keep log of all delivery made with specific association of unique service application
number and unique CSC number
13. The system should support multi-lingual interface (minimum Hindi, Oriya and English) as per localization and language
technology standards for National e-Governance plan defined in the e-District guidelines
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 68 | P a g e
4.3.9 Status Component
This component deals with the status tracking component with which the status can be tracked by the user and the citizens for the
requested service.
S.No Functional Requirement Specifications – Status Component
1. The system should have integrated auto status tracking features embedded in the overall architecture of the system
2. The system should keep track of all the service requests from the citizens along with the respective unique application reference
id generated at the time of the application receipt
3. The system should be available in public and administrative view
4. The system should be able to keep track of the status of all the service requests with the help of the respective unique application
reference id (application id) and map the current status with the pre-defined service level against each process
5. The system should be able to detect any change in the status of a given unique application reference id
6. In case there is a change in the status of a unique application reference id , the system should update the status information in
the database
7. The system should have provisions for intimating the applicant about the current status of his/her application through SMS
and/or Email especially if there is a change in the status with respect to the final delivery of the service
8.
The system should not provide details about the internal SLAs to the applicant and only provide update about the status with
respect to the final delivery. This feature should also allow the system to update the applicant if there is any change in the service
level of the final delivery
9. System should display the link for e-district portal from where the applicant can retrieve the status information by entering the
unique application reference id
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 69 | P a g e
S.No Functional Requirement Specifications – Status Component
10. The system should also allow the applicant to retrieve update about his/her service request through the web portal by entering
the reference id in the link provided on the portal
11. System should display the number from where the applicant can retrieve the status information by sending SMS along-with the
unique application reference id
12. The system should also allow the applicant to retrieve update about his/her service request by sending a SMS containing the
unique application reference id to the e-District application
13.
The system should display an appropriate message if the system is unable to retrieve the details due to any reason like
connectivity issues, maintenance issues, etc and also provide contact details of the system administrator and alternate link (if
available)
14. The System should have Side Menu on each page so as to reflect the contents of the containing directory, making it easier to
navigate the site and locate the link for retrieving update against a given reference id
15. The system should be adequate security features built in the architecture of the system to ensure that it cannot be hacked or
manipulated
16. The system should not allow the users to edit the details of the application upon retrieving the status update against a given
reference id
17. The System should allow the end user to print the status update information if the applicant is retrieving the status through the
portal or email
18. The System should have provision for Calendar System, which displays the dates and time of schedule events on a page formatted
as a standard monthly calendar
19. The system should have additional capability to integrate and extend portals to support a vast array of mobile devices in addition
to PCs (WAP enabled)
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 70 | P a g e
S.No Functional Requirement Specifications – Status Component
20. The system should have provisions such that the System Administrator can add/remove/modify the hierarchy of the
Government officials with adequate authentication mechanism
21. If there is any modification in the hierarchy of the relevant authority against a given service (in the system), system should
automatically map the escalation levels with the new hierarchy of Government officials
22. The system should support multi-lingual interface (minimum Hindi, Oriya and English) as per localization and language
technology standards for National e-Governance plan defined in the e-District guidelines
4.3.10 Monitoring Component (MIS)
This component deals with the generation of various reports at various levels who are involved in the delivery of services under the e-
District project.
S. No. Functional Requirement Specifications – Monitoring Component
1. The Process Owner should be able to use the e-District Application to query the Departmental Databases using the name or
other details of the applicant.
2. Should allow the e-District Application to retrieve various information from the individual databases and aggregate it
3. The application should support the monitoring in both the occurrence, when an event or time driven activity is triggered.
4. Should be able to retrieve all information about the status of the application form of the citizen.
5. Should be able to automatically generate the following reports to the concerned authorities at regular time interval:-
6. Should be able to generate Service Report on a regular time interval, this report should include the no of application received, no
of application processed, no of application rejected and the no of application under process.
7. Should able to generate SLA Report on regular time interval, this report should give information related to centre wise details of
no of SLA met and centre wise details of no of SLA breached.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 71 | P a g e
S. No. Functional Requirement Specifications – Monitoring Component
8. Should be able to generate Performance Report on regular time interval, this report should give information related to centre
wise details of no of application processed against the no of application received.
9. Should be able to generate Payment Report on regular time interval, this report should give information related to centre wise
transaction, money collected and money deposited along with date and time.
10. Should be able to generate Inventory Report on regular time interval, this report should give information related to pre-printed
stationary used and issued to each centre.
11. Should be able to generate Attendance Report on regular time interval, this report should give information related to centre wise
attendance.
12. Should provide a search option to the authorized stakeholder so that he can search the information which should be sorted
according to Date, Department/Section, Service, District, Block, Sub Division, Tehasil, RI Circle etc
13. Should allow the stakeholder to review the progress report and give his comments online.
14. Should provide the facility to print and e-mail the report.
15. Should provide a printer – friendly version automatically for all pages.
16. The system should support multi-lingual interface (minimum Hindi, Oriya and English) as per localization and language
technology standards for National e-Governance plan defined in the e-District guidelines
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 72 | P a g e
4.3.11 Log in Component
S. No. Functional Requirement Specifications – Log In Component
1.
Should allow only the authentic users (Kiosk Operators, Department Officials) to login to the system through the use of:
User id and Password combination (for kiosk operators and verification officers)
Both (for Forwarders and issuing Authorities)
2. Should display the login page as the first page when the user enters the e district application.
User id & Password Combination
1. The user login and password both should be a combination of following: Alphabets (at least 1) , Special Character, Numeric
2. The user name and password should have a minimum of 8 characters each
3. Should not create duplicate user ids or passwords
4. Should not allow the user to have the same password for more than 30 days
5. Should generate alerts for password expiry from two days of actual expiry
6. Should not allow same user id and password
7. Should not allow blank spaces while setting user id or password
8. Should notify the user in case the Caps Lock is on
9. Should notify the use if Num Lock is on
10. Should generate user id based on the criteria of - Zone, district, Circle an SCA name, kiosk number
11. Should not allow a user who forgets the password to access the password retrieval mechanism
12. Should allow only the machines whose mach id is registered with the application enter the e district application
13. Should prompt the user to change the password in case of first login at the client side i.e. after imaging
14. Should give a welcome message once the user is able to successfully login to the e district application.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 73 | P a g e
S. No. Functional Requirement Specifications – Log In Component
15. Should give an error message once the user provides wrong login information and ask the user to re log in.
16. Should block the user to enter into the e-district application if he puts in wrong login info continuously thrice.
17. Should support multilingual interface (minimum Hindi, Oriya and English) as per Localization and Language Technology
Standards for National e-Governance Plan defined in e-district guidelines
4.3.12 Service Specific Functionalities
The e-District portal is envisaged to be a single point information access for all the users under the e-District project through which the
citizens can avail the specific services and get the required information of those services that are proposed to be delivered under e-District
project. This portal will provide comprehensive information about the services of District Administration, its functions and also host links to
certain specific categories of services which can be availed through the Common Service Centres (CSCs)/e-District Centres. Service Specific
functionalities comprise of functions that are specific to service categories/services and deals with the day-to-day functioning of the same.
Indicative Functional Requirement Specifications for one of the Certificate is mentioned below. SPMU shall prepare the As-Is, To-Be
Process, FRS document for the services and the same shall be handed over to the selected bidder after approval to carry out necessary task
at his end.
S. No. General Functional Requirement Specifications
1 The system should be able to display Service related page through multiple routes, Service links, Information links, District links
2 The system should be able to identify the user logging into the system using the login component.
3 The system should be able to provide information to the citizens about the relevant services both in public as well as private
domain as per the ‘Information component’
Web access to information content in public domain
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 74 | P a g e
S. No. General Functional Requirement Specifications
e-District application access to information content
4 The system should make available the latest copy of the Application Form online (24x7) as per the Form Availability component.
5 The system should be able to retrieve the service request form for a particular service
6 The system should allow the operator to fill in the online application on behalf of citizen availing the service as per the
‘application receipt’ component
7 The system should be able to generate a unique registration number during registering an applicant with the application.
8 The system should be able to identify the applicant uniquely based on this registration number for all future references.
9 The system should be able to record the payment made by the applicant against the service as per the Payment Component
10 The system should display a message regarding successful or unsuccessful completion of any transaction.
11 The system should refresh the page in case of failure in submission of service request
12 The system should be able to issue an acknowledgement receipt once the applicant is registered with the system
13 The system should be able to notify the concerned officer about the new application and this date and time must be logged
through e-District application
14 The system should allow concerned officials to view the service request only on authenticated login as per login process
15 The system should show service request to concerned Approving authority as pending for approval till it is marked for further
action
by default the system should be able to auto escalate within the service level as per the escalation matrix defined
16 The system should be able to auto generate MIS reports for the following officials as per the requirement–
District Collector, Sub Collectors/Tehasilders/BDOs, Other concerned authorities
17 The system should be able to support the status tracking as per the status tracking component
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 75 | P a g e
S. No. General Functional Requirement Specifications
18 The system should be able to support the monitoring and reporting as per the monitoring and reporting component
19 The system should be able to detect changes in status and send status updates to the citizen as per the Status Tracking
component.
20 The system should be able escalate the application as per the Auto Escalation matrix, defined, by notifying the next level of
authority and sending him a copy of the application.
21 The system should be able to maintain all records for the login sessions with date and time
22 The system should be able to provide date and time stamping for all transactions done with digital signature
23 The system should have a facility for forwarding of the application, with remarks and digital sign of the sender, to any person in
District administration registered with the System.
24 The system should support multilingual interface (minimum Oriya, Bengali, Hindi, English) from the first day of its operation, as
per Localization and Language Technology Standards for National e-Governance Plan defined in e-district guidelines.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 76 | P a g e
4.4 Bill of Material Summary
4.4.1 Requirement at Field Level Offices
Item Name Dist. Magistrate
Office
Sub
Collector
Office
Tahsildar
Office
BDO
Office
Total
Nos.
Laptop 56 51 536 266 2699
Desktop 224 102 536 532 1394
UPS 224 102 536 532 1394
Printer 140 102 536 266 1044
All in one 28 0 0 0 28
Scanner 56 102 536 266 2750
Biometric Device 280 153 1072 798 4093
Antivirus 280 153 1072 798 4093
24 Port Managed LAN
Switch
56 51 268 0 375
9 U Networking Rack 56 51 268 0 375
UTP cable CAT-6 (Box
of 305 Mtrs)
56 51 268 266 641
Jack Panel 24 Port
CAT 6
56 51 268 0 375
Information Outlet
CAT6
420 255 1340 1330 3345
Surface Mount Box
Single
420 255 1340 1330 3345
Mounting Cord 7 Ft.
CAT 6
420 255 1340 1330 3345
Mounting Cord 3 Ft.
CAT 6
420 255 1340 1330 3345
6 Core Multimode
Fiber with necessary
terminator
14000 Mtr 0 0 0 14000
Mtr
P.S.: Number of equipment’s/peripherals displayed in the above table may vary during the actual implementation in the field. In case of variance the actual requirements needs to be presented in front of the SDA. After approval, the unit price quoted by the selected vendor will be taken into consideration for payment. Also, as per requirements, the distribution of materials across the offices may also vary during the actual course of implementation.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 77 | P a g e
4.4.2 Requirement at SDC
Sl No. Item Total Qty (Q)
1 Server For Helpdesk and SLA 2 Nos.
2 Server for Antivirus 1 Nos.
3 Software for Helpdesk, SLA & Asset Management 1 Nos.
4 Antivirus Software solution 1 Nos.
5 42 U Server Rack 1 Nos.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 78 | P a g e
4.5 Technical Specifications
4.5.1 Server for Web, Database, Application
Following numbers of servers were procured during pilot implementation of eDistrict Project.
Sl.No Description of Item Quantity Make/Model
1 Web Servers 1 IBM 8204 Model E8A
2 Application Servers 1 IBM 8204 Model E8A
3 Database Servers 2 IBM 8204 Model E8A
The specifications of the existing server are as follows. The bidder has to use the existing server.
If the Bidder feels that any hardware up-gradation is required in the existing servers, then they
have to propose the same and provide commercial proposal for the same in the format given in
Network Integrated 10/100 Mbps Ethernet Adapter (RJ-45), PXE support
Key board USB 104 keys keyboard (Same make as PC) with bi-lingual keys (English and local language of the State) compliant to Enhanced Inscript Keyboard based on Unicode version 6.0 or later.
Mouse 2 button optical wheel mouse
Monitor 17” TFT Color Monitor
Interface 1 serial, 5 USB (Minimum 2 in front), 1 PS/2 Keyboard, 1 PS/2 Mouse, VGA, audio ports for Microphone & headphones in front.
OS Certification
Microsoft Windows
OS Windows 7 business Edition or higher edition preloaded
Certification For OEM:ISO 9001 and 14001. For quoted Model: FCC, UL, Energy Star 5.0, DMI
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 82 | P a g e
4.5.3 Laptops
Features Specifications Specifications Offered
Compliance Deviations if any
Make Must be specified Model Must be specified. All the rele-
vant product brochures and manuals must be submitted.
Part No. Must be specified for all the required components
Motherboard Compatible motherboard to support the processor and memory. Motherboard from the original OEM.
Memory 4 GB DDR3 SDRAM
Hard Drive 320 GB SATA
Removable drive
Integrated DVD R/W
LAN Network Integrated 10/100 Mbps Ethernet Adapter (RJ-45), PXE support
Wireless Support
Integrated 802.11 b+g 54 MBPS Wireless LAN adapter
Key board Spill-resistant keyboard (minimum 86 keys) with bi-lingual keys (English and local language of the State) compliant to Enhanced Inscript Keyboard based on Unicode version 6.0 or later.
Graphics Intel Graphics Media Accelerator X3100, with up to 384 MB shared system memory
Display 14.1" WXGA Active TFT (1280X800) & with Integrated WEB CAMERA (1.3 MP)
Interface 3 USB 2.0, 1XLine in , 1X MIC ,1XRJ11 Modem, 1XRJ45 LAN, 1X External VGA , 1X DC In
Power Universal DC Adapter
Battery 6 Cell Li Ion Battery
OS Certification
Microsoft Windows
OS Windows 7 Business Edition or higher edition preloaded
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 83 | P a g e
4.5.4 Scanner
Features Specifications
Specifications Offered
Compliance Deviations if any
Make Must be specified Model Must be specified. All the
relevant product bro-chures and manuals must be submitted.
scanner type Flatbed input modes front panel scan, copy
buttons,
speed preview speed: 10 seconds Scan speed: Photo to files: 29 secs; Text to document: 26 secs
bit depth 48-bit scaling 10 to 2000% max document size
220 x 300 mm
interface and operating system requirements
USB – compatible with USB 2.0 Windows 7 Home and Professional Edition
power Universal AC adaptor: 100 to 240 VAC (+/- 10%), 50/60 Hz (+/- 3Hz) input (according to configuration), 12 VDC, 1.25 Amp output, Energy Star™ compliant
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 84 | P a g e
4.5.5 Laser Jet Printer, Scanner, Copier all in one Device
Features Specifications
Specifications Offered
Compliance Deviations if any
Make Must be specified Model Must be specified. All the rele-
vant product brochures and manuals must be submitted.
Print speed Up to 27 ppm letter Resolution Printing: upto 1200 x
1200 dpi Copying: up to 600 x 600
dpi Scanning: up to 1200 x
1200 dpi
Printing Features
Manual duplex and book-let printing
N-up printing, Collation, Watermarks, Economic mode for toner
savings
Copying Features
1 to 99 multiple copies reduce/enlarge from 25
to 400% 2-up or 4-up allowing 2
or 4 pages to be copied onto 1 page
Contrast (light-er/darker),
resolution copy quality (draft, text, mixed)
Scanning Features
Flatbed scanner up to let-ter, A4 size;
supported file types: JPEG, TIFF, PDF, GIF, and BMP
Should be able to scan Legal Documents
Control panel
2-line LCD text display, Asian character support, 16-character display, menu and navigation
buttons, copy control buttons, cancel button
Memory 32 MB RAM Paper Handling Tray
10-sheet priority input tray,
250-sheet multipurpose input tray,
125-sheet output bin, manual two-sided print-
ing
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 85 | P a g e
Features Specifications
Specifications Offered
Compliance Deviations if any
Paper Size 76 x 127 mm (3 x 5 inch-es) to 216 x 356 mm (8.5 x 14 inches);
letter, legal, index cards, postcards; A4, A5
Interfaces Hi-Speed USB 2.0 port, Ethernet port
operating systems support Required
Windows 7 Home and Professional Edition ; Windows Vista, Linux
Power 220 to 240 volts (±10%), 50/60 Hz (±2 Hz) Input Power port with required English power chord
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 86 | P a g e
4.5.6 Laser Printers
Features Specifications
Specifications Offered
Compliance Deviations if any
Make Must be specified Model Must be specified. All the rele-
vant product brochures and manuals must be submitted.
Print speed Up to 14 ppm A4 &letter Resolution Up to 600 x 600 dpi Printing Features
Manual duplex print-ing
N-up printing, Economic mode for
toner savings
Memory 2 MB RAM Paper Handling Tray
150-sheet adjustable main input tray,
100-sheet output bin, manual two-sided
printing
Paper Size A4, A5, A6, B5, letter, legal, postcards, envelopes
Interfaces Hi-Speed USB 2.0 port, operating systems support Required
Windows 7 Home and Professional Edition ; Windows Vista, Linux
Power 220 to 240 volts (±10%), 50/60 Hz (±2 Hz) Input Power port with required English power chord
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 87 | P a g e
4.5.7 UPS – 1 KVA offline UPS
Parameter Specifications Specifications Offered
Compliance Deviations if any
Make Must be specified
Model Must be specified. All the relevant product brochures and manu-als must be submitted.
Type Line-interactive
Capacity 1 KVA
Input Voltage Range 90 – 280 V AC
Input Frequency 50 Hz +/-10%
Output Voltage 220 V +/- 10% (under line mode)
220 V +/- 5% (under battery mode)
Output Frequency 50 Hz +/- 1% (under battery mode)
Noise < 40 db at 1 m
Protection Overload, Short Circuit, Low Battery
AVR Built in Automatic Voltage Regulator (AVR)
Indicators LED indicators for AC Mains, DC, Load on Mains/Battery
Battery Type & back-up time
Batteries shall be of Sealed Maintenance Free (SMF) type The system must be capable of providing requisite battery back-up time of 60 minutes using SMF Batteries as per VAH rating below : (Minimum VAH for 60 minutes back-up = 1008 VAH) Total number of batteries offered should be clearly mentioned. Voltage of each battery offered should be clearly mentioned. Ampere-Hour rating of each battery offered should be clearly mentioned. Total Volt-Ampere-Hour rating of the Battery Bank Offered
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 88 | P a g e
Design Specifications Docu-ments of Software solutions
Design Specifications Docu-ments of Hardware solutions
User Interface Design Specifications
Integration Design Specifica-tions
Data design and migration
Development Software installation, configuration, and customization
Hardware installation and configuration
Development Unit Testing Documentation
Development Plan Updated Design Document Installed software and hard-
ware Functional modules & Portal
Solution Problem reporting
Testing System Testing Integration Testing Stress Testing Load Testing User Acceptance Test
Results
Complete Test Cases Test Plan User Acceptance Criteria Problem reporting Problem resolution testing Data Migration Testing
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 103 | P a g e
Completed Test Cases Data Migration tests Documentation
Deployment Training courses and sessions
Operations Planning User Manual Operations Manuals
Knowledge Transfer and training plan
Operations Plan Operations Policies and
Procedures
4 Selected bidder is required to describe in detail project management processes, methodologies
and procedures.
5 Describe what SDA resources will be necessary for the project to succeed.
6 Describe how SDA management will receive up-to-date reports on project status.
7 Describe the change management procedures to handle such things as “out-of-scope” requests
or changing business needs of SDA while the project is underway.
8 Describe what procedures will be used to keep the project on track, and what escalation
procedures will be employed to address any problems with project progress.
9 Describe what quality assurance processes, procedures, formal reviews, etc. will be in place.
10 Describe the proposed conflict resolution / escalation process between the Bidder and SDA to
handle project or contractual disputes.
11 Selected bidder is required to describe the proposed project structure identifying all project
individuals including project manager, business analysts, software developers, QA engineers,
hardware / network engineers, administrators, Change Management experts, and others.
12 Selected bidder shall provide a comprehensive warranty that covers all components after the
issuance of the final acceptance of e-District. The warranty should cover all materials, licenses,
services, and support for both hardware and software. Selected bidder shall administer
warranties with serial number and warranty period. Upon final acceptance of the SDA, all OEM
warranties will be transferred to the SDA at no additional charge. All warranty documentation
(whether expired or not) will be delivered to SDA at the issuance of the final acceptance
certificate
13 Selected bidder is required to provide Premium Level warranty and support through the
vendor for all hardware and software used for e-District. Selected bidder’ warranty must cover
all equipment and work activities contained in the contract against all design, manufacturing,
and environment faults until the issuance of the final acceptance. 14 Selected bidder is required to commit to the following warranty terms:
All products / components / parts shall be covered under OEM warranty up to the
Implementation Phase and AMC support shall commence after successful implemen-
tation.
The warranty shall include the repair or replacement of the products / components /
parts during the warranty period by the bidder. The replacement products / compo-
nents shall meet the related specifications without further repair or modification.
Selected bidder shall be liable for all costs including, but not limited to, the costs of
material, labour, travel, transport and living expenses associated with the collection
and return of the units covered by the warranty.
The date of manufacture or assembly of any equipment, parts or consumables, shall
not be more than six months before delivery.
Selected bidder shall state the location of his repair Centre(s) for all items not being
repaired onsite.
SDA has the right to require a replacement if the repair is deemed to be impractical.
Selected bidder ensures that replacement components shall be available for any
failed component during the warranty period.
Selected bidder shall guarantee the availability of spare parts and technical assis-
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 104 | P a g e
tance for all components (or appropriate alternatives) to ensure the equipment
would run for at least five (5) years, without major changes, at the completion of final
acceptance. Six months advance notice is required on any discontinued part(s) with a
suggestion for alternatives.
Selected bidder need to define the process & methodology in their proposal, for
achieving the response time of engineers to respond to an incident and also for re-
solving such incidents as per the SLA.
Selected bidder is required to provide additional training if the satisfaction levels/
learning does not reach 80% in evaluation/feedback from trainees, and expected to
provide additional training, if required.
The e-District application & infrastructure being provisioned by the bidder shall be
insured. The Goods supplied under the Contract shall be fully insured against loss or
damage incidental to manufacture or acquisition, transportation, storage and deliv-
ery for the entire project term.
Selected bidder is required to explain their warranty, maintenance procedures, and support
to meet the terms and requirements outlined above.
Operations Requirements 1 The selected bidder is expected to provide the following in support of e-District operations:
Selected bidder shall provide procedure documentation for all operations procedures, and SLA’s (based on ITIL best practices) for all the hardware and applications provided including backup procedures, system update procedures, security procedures, failure recovery proce-dures, upgrade procedures, remote access procedures, user manual, SOP’s etc. All such procedures and documents must be submitted for review and approval by the SDA prior to adoption. Such documentation shall be updated by the during the project term by the bidder as and when required along with the necessary approval. Selected bidder will be required to provide SDA with weekly statistics reports on the various services provided to users a mechanism as well as track and log all related statistical reports on the various delivery channels and access patterns. Selected bidder will be required to provide SDA with weekly portal performance reports showing health of system operations. Selected bidder will be required to provide SDA with Helpdesk for recording all the day to day problems and other technical incidents occur during the O&M phase. This shall also record the resolution of such incidents & problems. Selected bidder will be required to commit to Service Level Agreements (SLAs) that show,
among other metrics, appropriate escalation procedures and guarantee corrective actions
within a pre-determined time. Selected bidder is required to respond to required levels of
and user satisfaction that are equal to or higher than the SLA system requirements.
Quality Assurance & Acceptance Requirements 1 Selected bidder is required to develop and implement quality assurance processes and proce-
dures to ensure that the e-District development and operations are performed to meet the quality standards that are relevant to each area in all project phases.
2 Selected bidder is required to use various tools and techniques that can make tests run easily and the results are automatically measured. In this way, testing tools provide a more cost-effective and efficient solution than their manual counterparts. Plus, they minimize the risk of human error during testing
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 105 | P a g e
3 In order to ensure that such a QA mechanism is effective and acceptance of e-District, the fol-lowing tests are required for acceptance: Unit Testing: Basic validation of developed components by developers. Functional / Internal Integration Testing: Validation of developed components against functional requirements and design specifications. System Testing: Validation of both functional and technical requirements for the integrated Solution. This could include external integration if required or it can be separated into testing phases. UAT: User Acceptance Testing (UAT) validation of the Portal Solution and assurance that it meets both functional and technical requirements Stress and Performance Testing: Load test-ing enabling understanding of performance and behaviour of Portal Solution under large number of users and high-load conditions.
4 Selected bidder is required to describe their QA and testing approaches and procedures as well as testing tools for conducting various tests in support of the acceptance of the Portal Solution. Selected bidder is expected to follow minimum CMMi level 3 processes.
5 Furthermore, Selected bidder to describe their documentation standards e.g. Documentation description, documentation identification, content, nomenclature etc. as well. Sample docu-ments to be enclosed as part of the technical proposal.
Quality Assurance & Acceptance Requirements 1 Selected bidder is required to develop and implement quality assurance processes and proce-
dures to ensure that the e-District development and operations are performed to meet the quality standards that are relevant to each area in all project phases.
2 Selected bidder is required to use various tools and techniques that can make tests run easily and the results are automatically measured. In this way, testing tools provide a more cost-effective and efficient solution than their manual counterparts. Plus, they minimize the risk of human error during testing.
3 In order to ensure that such a QA mechanism is effective and acceptance of e-District, the following tests are required for acceptance:
Unit Testing: Basic validation of developed components by developers. Functional / Internal Integration Testing: Validation of developed components
against functional requirements and design specifications. System Testing: Validation of both functional and technical requirements for the in-
tegrated Solution. This could include external integration if required or it can be sep-arated into testing phases.
UAT: User Acceptance Testing (UAT) validation of the Portal Solution and assurance that it meets both functional and technical requirements
Stress and Performance Testing: Load testing enabling understanding of performance and behaviour of Portal Solution under large number of users and high-load condi-tions.
4 Selected bidder is required to describe their QA and testing approaches and procedures as well as testing tools for conducting various tests in support of the acceptance of the Portal Solution. Selected bidder is expected to follow minimum CMMi level 3 processes.
5 Furthermore, Selected bidder to describe their documentation standards e.g. Documenta-tion description, documentation identification, content, nomenclature etc. as well. Sample documents to be enclosed as part of the technical proposal.
RFP for Selection of System Integrator for Rollout of e-district MMP – Volume II
State-wide rollout of the eDistrict MMP 106 | P a g e