RFP Vol I 20170720 Final

RFP for Selection of SI for Supply, Configuration of ePragati Core Platform and Services for GoAP (Volume-I)
REQUEST FOR PROPOSAL

FOR
SELECTION OF SYSTEM INTEGRATOR
for
Supply, Configuration of ePragati Core Platform and Services
IN ANDHRA PRADESH STATE
July, 2017
Andhra Pradesh Technology Services Limited (APTS)

4th Floor, B-Block, BRKR Bhavan
Tankbund Road, Hyderabad – 500 063
Volume I
Scope of Work
Page 1 of 41
Proprietary & Confidential
No part of this document can be reproduced in any form or by any means, disclosed or
distributed to any person without the prior consent of APTS except to the extent required
for submitting bid and no more.
Page 2 of 41
RFP STRUCTURE
This RFP is meant to invite proposals from interested companies capable of delivering the
services described herein. The content of this RFP has been documented as a set of three
volumes explained below:
Volume I: Functional, Technical and Operational Requirements

Volume I of the RFP intends to bring out all the details with respect to solution and other
requirements that Information Technology Electronics and Communication (ITE&C)
department deems necessary to share with the potential bidders. The information set out in
this volume has been broadly categorized as Functional, Technical, and Operational covering
multiple aspects of the requirements. The Volume I also consists of 4 (four) annexures
namely Annexure A Part (I), Annexure A Part (II), Annexure A Part (III) and Annexure A Part
(IV).
Volume II: Commercial and Bidding Terms

Volume II of the RFP details the General Terms & Conditions with respect to the bid process
management including the project implementation, financial terms, evaluation criteria and
bid submission forms to be adopted for the proposed project.
Volume III: Contractual and Legal Specifications

Volume III of the RFP details out the Draft Contract for the proposed engagement and
outlines the contractual, legal terms & conditions applicable for the proposed engagement.
This Volume is Volume I

Kindly note that all three volumes of the RFP have to be read in conjunction as there are
cross references on sections in these volumes. The selected System Integrator will be solely
responsible for any gaps in scope coverage caused by not referring to all three volumes.
Page 3 of 41
OFFICE OF THE MANAGING DIRECTOR, AP TECHNOLOGYSERVICES LIMITED

(On behalf of CHIEF EXECUTIVE OFFICER OF ePRAGATI AUTHTORITY)
News Paper Advertisement

APTS
Open Competitive Bid (OCB) - Tender Call Notice for
“Selection of System Integrator (SI) for Supply, Configuration of CORE Platform under
ePragati of GoAP”
Time schedule of various tender related events:
Bid calling date 20.07.2017
27.07.2017, 11.00 AM at Conference Hall, APSFL,
**Pre-bid conference Date, Time
3rd Floor, RTC Bus Bhavan, Vijayawada.
Last Date & time for submission of 26.07.2017, 5.00PM (No Queries will be
written queries for clarification considered beyond this date and time)
Bid Closing date and time 10.08.2017 at 02.00 pm
Bid Document Price Rs.50,000/-
1. Srinivas Prasad VSVCh, PD (ePragati)
Contact person
2. Satyanarayana PPV, i/c Manager (SDC)
pd-epragati@ap.gov.in, Mob.7331154521
Email
pvssatyanaryana.p@gov.in, Mob.9963029416
Reference No. APTS/CS/ePragati/CORE/06/2017
** Maximum 2 representatives will be permitted to attend pre-bid meeting from each firm,
who purchased Bid Document.
For further details please visit http://www.apts.gov.in/aptsTenders.aspx
Managing Director,
A.P. Technology Services Ltd., BRKR Building, 4th Floor, B-Block,
Tankbund Road, Hyderabad -500 063, India
Note: The Bid document can be purchased by submitting the document fee in the form
Demand Draft/ Banker’s cheque in favour of “The MD, APTSL” Payable at
Hyderabad.
Notice Inviting Tender (NIT)
Name of work –Supply, Configuration of ePragati Core Platform and Services
On behalf of the Government of Andhra Pradesh (“GoAP”), the Managing Director (“MD”),
Andhra Pradesh Technology Services Limited (“APTS”), Government of Andhra Pradesh,
invites eligible and competent bidders to submit their pre-qualification, technical and
financial proposal for the Project, in accordance with conditions and manner prescribed in
Page 4 of 41
this RFP and other Bidding Documents issued by the GoAP, which is available on its website
(http://www.apts.gov.in) and also on the GoAP e-procurement website
(https://tender.apeprocurement.gov.in).
The bidders, participating for the first time in the e-procurement portal on the GoAP e-
Procurement Portal, will have to complete the online registration process. Details of the pre
requirements for such registration are available on the abovementioned e-procurement
website. FAQs are available at (http://www.apeprocurement.gov.in/faqs_contractors.asp).
The MD, APTS reserves the right to reject any or all proposals without assigning any reason.
Sd/-
Managing Director, APTS
Page 5 of 41
TABLE OF CONTENTS
News Paper Advertisement .......................................................................................................... 4
List of Annexures ......................................................................................................................... 7
List of Figures............................................................................................................................... 7
List of Tables ................................................................................................................................ 7
GLOSSARY OF TERMS ................................................................................................................... 8
DISCLAIMER ............................................................................................................................... 10
PREAMBLE ................................................................................................................................. 12
1. BACKGROUND AND OBJECTIVE ......................................................................................... 13
1.1. ePragati Program Overview ..................................................................................................... 13
2. SYSTEM OVERVIEW OF EPRAGATI CORE PLATFORM ........................................................... 15
2.1. Meta-model of ePragati Core Platform ................................................................................... 15
3. PROPOSALS, PROJECT AND SCOPE OF WORK ..................................................................... 17
3.1. Proposals .................................................................................................................................. 17
3.2. Description of the Project......................................................................................................... 17
3.3. Detailed Scope of work ............................................................................................................ 18
(A) Supply of ePragati Core Platform .........................................................................................18
(B) Setting up of Zero/ Low-Code Development Platform and Core Components on the Hosting
Platform as the “ePragati Core Platform” ...................................................................................23
(C) Configuration of ePragati Core Platform ..............................................................................24
(D) Submission of a manpower rate card for the design, develop & maintenance of application
on ePragati Core Platform ...........................................................................................................29
(E) Setting up applications for provision of five services, CLGS, LMS, Integration services,
support & maintenance, design/ configure/development/ continuous improvements &
maintenance of ePragati Portal, APp Store .................................................................................30
(F) Platform Administration, Support, Operations & Maintenance ..........................................32
(G) Annual Technical Support& Updates....................................................................................33
(H) Centre of Excellence Team ...................................................................................................37
(I) Capacity Building ..................................................................................................................39
(J) Deliverables, Timelines and Payment Schedule as per Volume III of RFP ............................40
Annexure A ................................................................................................................................ 41
(End of the Volume I) ................................................................................................................. 41
Page 6 of 41
List of Annexures
Annexure A Functional and non-Functional Requirements of the ePragati Core Platform
List of Figures
Figure 1 Meta Model of ePragati Core Platform
Figure 2 Architecture of ePragati Core platform
Figure 3 Core Components of e-Pragati Core Platform
List of Tables
Table 1 List of Resources
Page 7 of 41
GLOSSARY OF TERMS
The definitions of various terms that have been used in this RFP are as follows:
 “Request for Proposal (RFP)” means the Section and its annexure and any other
documents provided along with this RFP or issued during the course of the selection of
the 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 <<System Integrator (SI)>>,
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 Financial bids submitted for
this project against this RFP.
ACRONYM Full Form

AMC Annual Maintenance Contract
API Application Programming Interface
BOM Bill of Material
COTS Commercial Off The Shelf
DC Data Centre
DR Disaster Recovery
DRC Disaster Recovery Centre
ePRS ePragati Requirements Specifications
GoAP Government of Andhra Pradesh
HOD Head of Department
HOO Head of the Office
HRMS Human Resource Management System
ICT Information and Communications Technology
INR Indian Rupee
ISO International Organization for Standardization
IT Information Technology
LAN Local Area Network
LOC Letter of Credit
MIS Management Information System
Page 8 of 41
NDA Non-Disclosure Agreement

OEM Original Equipment Manufacturer
PI Platform Integrator
RFP Request for Proposal
RTM Requirements Traceability Matrix
SI System Integrator
SLA Service Level Agreement
SMS Short Messaging Service
SOP Standard Operating Procedure
SP Service Provider
SQL Structured Query Language
SRS System Requirement Specifications
SWAN State Wide Area Network
TB Tera Byte
UAT User Acceptance Testing
UC Utilization Certificate
VPN Virtual Private Network
W&P Works & Projects
WAN Wide Area Network
XML Extensible Mark-up Language
CLGS Certificate Less Governance System
LMS License Management System
Page 9 of 41
DISCLAIMER
The information contained in this Request for Proposal document (the “RFP”) or
subsequently provided to Bidders (as defined hereinafter), whether verbally or in
documentary or any other form by or on behalf of the MD, APTS (as defined hereinafter) or
any of its employees or advisors, is provided to Bidders (as defined hereinafter) on the terms
and conditions set out in this RFP and such other terms and conditions subject to which
such information is provided.
This RFP is not an agreement and is neither an offer nor invitation by APTS to the
prospective Bidders or any other person. The purpose of this RFP is to provide interested
parties with information that may be useful to them in preparing and submitting their
Proposals (as defined hereinafter). This RFP includes statements, which reflect various
assumptions and assessments arrived at by APTS and ePragati Authority in relation to the
Project. Such assumptions, assessments and statements do not purport to contain all the
information that each Bidder may require. This RFP may not be appropriate for all persons,
and it is not possible for APTS and ePragati Authority, their respective employees or advisors
to consider the investment objectives, financial situation and particular needs of each
person who reads or uses this RFP. The assumptions, assessments, statements and
information provided in this RFP/ Bidding Documents (as defined hereinafter) may not be
complete, accurate, adequate or correct. Each Bidder should, therefore, conduct its own
investigations and analysis and should check the accuracy, adequacy, correctness, reliability
and completeness of the assumptions, assessments, statements and information contained
in this RFP and obtain independent advice from appropriate sources.
Information provided in and pursuant to this RFP to Bidders is on a wide range of matters,
some of which may depend upon interpretation of law. The information given is not
intended to be an exhaustive account of statutory requirements and should not be regarded
as a complete or authoritative statement of law. APTS, ePragati Authority and GoAP accepts
no responsibility for the accuracy or otherwise for any interpretation or opinion on law
expressed herein.
APTS, ePragati Authority and GoAP, their respective employees and advisors make no
representation or warranty and shall have no liability to any person, including any Bidder
under any law, statute, rules or regulations or tort, principles of restitution or unjust
enrichment or otherwise for any loss, damages, cost or expense which may arise from or be
incurred or suffered on account of anything contained in this RFP or otherwise, including the
accuracy, adequacy, correctness, completeness or reliability of the RFP/Bidding Documents
and/or any assessment, assumption, statement or information contained in or deemed to
form part of this RFP/Bidding Documents or arising in any way in connection with
participation in the bidding process in respect of the Project.
APTS, ePragati Authority and GoAP accepts no liability of any nature whether resulting from
negligence or otherwise howsoever caused arising from reliance of any Bidder upon the
statements contained in this RFP/Bidding Documents.
Page 10 of 41
APTS, ePragati Authority may in its absolute discretion, but without being under any
obligation to do so, update, amend or supplement the information, assessment or
assumptions contained in this RFP/Bidding Documents.
The issue of this RFP/Bidding Documents does not imply that APTS and ePragati Authority is
bound to evaluate a Bidder or to appoint the Successful Bidder, as the case may be, for the
Project and APTS and ePragati Authority reserves the right to reject all or any of the Bidders
or Proposals without assigning any reason whatsoever.
The Bidder shall bear all costs associated with or relating to the preparation and submission
of its Proposal including but not limited to preparation, copying, postage, delivery fees,
expenses associated with any demonstrations or presentations which may be required by
APTS and/or ePragati Authority or any other costs incurred in connection with or relating to
its Proposal. All such costs and expenses will be to the account of the Bidder, and APTS and
ePragati Authority shall not be liable in any manner whatsoever for the same or for any
other costs or other expenses incurred by a Bidder in connection with preparation or
submission of the Proposal, regardless of the conduct or outcome of the bidding process.
Page 11 of 41
PREAMBLE
ePragati is a long-term sustained endeavour. As aware, the Government of Andhra Pradesh,
under the aegis of the Hon’ble Chief Minister, Sri N Chandrababu Naidu Garu, has declared
the Financial Year of 2017-18 as “Year of ePragati” and subsequently passed a Cabinet
resolution and released GO.Rt.No.27 to that affect. During this period, around 24 Unique in
nature IT projects across all departments that can cater to more than 200 plus Citizen
Centric services are planned to be implemented and rolled out. To make this program a
success the following objectives must be achieved.
a. Understand Departments Businesses and its processes.

b. Transform it through Business Process Reengineering.
c. Shift this reengineered Business Process from being Government Centric to
Citizen Centric.
d. Digitise the reengineered citizen centric business process.
Government aims to deliver all its citizen related services through a single portal and
experience “ONE” Government through an integrated application, data and services
architecture as designed by J. Satyananrayana Garu, (Retd.,) IAS, IT Advisor to CM,
Government of Andhra Pradesh.
Page 12 of 41
1. BACKGROUND AND OBJECTIVE
1.1. ePragati Program Overview
(a) The Government of Andhra Pradesh (“GoAP”) has been making pioneering efforts to
develop the State of Andhra Pradesh as an innovation society of global repute, with a focus
on enhancing the quality of life of its citizens, through high-quality education and healthcare,
increased productivity in agriculture and allied activities, creation of employment by
promoting electronics and information technology, and all, by providing good governance.
(b) The vision of the State of Andhra Pradesh is “To use e-Governance as a tool to provide
integrated services to its citizens through a free flow of information, and to usher in an era of
Good Governance, to ensure transparency, efficiency, accountability, accessibility and
reliability in delivery of such services, to enhance citizen-centricity, responsiveness,
inclusiveness and citizen engagement as essential ingredients of good governance”.
(c) Towards achieving the above, the GoAP has constituted the Andhra Pradesh e-Governance
Authority as a society registered under the Andhra Pradesh Societies Registration Act, 2001
having its registered office at APIIC, Industrial Estate, Auto Nagar, Vijayawada, Andhra
Pradesh (“ePragati Authority”). ePragati Authority seeks to help GoAP realize the vision of
‘Sunrise AP 2022’ by supporting the 7 development missions launched by the GoAP in the
areas of eGovernance, Social Empowerment, Skill Development, Urban Development,
Infrastructure, Industrial Development and the Services sector.
(d) GoAP realize the vision of ‘Sunrise AP 2022’to provide integrated services to citizens through
a free flow of information, and to usher in an era of good governance, characterized by
efficiency, effectiveness, transparency, and foresight. The different dimensions of the vision
are described below:
 Departments and government agencies interoperate with ease and provide

integrated services to citizens and businesses.
 Citizens and businesses will have a seamless and smooth interface with
government. This demands to have Enterprise service bus as technology
stack with government.
 Providing common infrastructure and application services will enable one
government vision
 Faster time to market in deploying GoAP services by enabling quick
implementation of other sectoral packages. This demands to have zero/low
code platforms as technology stack with GoAP.
 Increased productivity and efficiency by providing access to single source of
truth of core data
 Readiness to create a richer portfolio of services through the ability to
compose new, complex services from simpler services that are already
available
Page 13 of 41
 Ability to create cross-Governmental services through interoperability,

service discovery, and invocation
 Increased stakeholder satisfaction through uniform user interface,
consolidated services and multiple access channels
 Leverage social, mobile, big data, cloud and internet of things technologies.
 The medium of paper will be minimized in all G2C, C2G, G2B, B2G, and G2G
interactions by listing all the services through ePragati State Portal
 GoAP and citizens will be enabled to take advantage of cutting-edge
technologies like business process/rules management tools, SMAC and IoT.
 Principles of open data, open standards and open APIs will be ingrained in
the designs of all information systems.
 ePragati Authority will ensure the right balance between information security
and privacy of personal data.
(e) GoAP proposes to realize the vision of ‘Sunrise AP 2022’ by providing integrated services to
citizens through free flow of information, integrated services through common state
ePragati portal. Further, GoAP envisions having ePragati Core Platform to enable GoAP to
develop flexible business application with fewer resources and in very less time. It also
provides GoAP with analytical capabilities while protecting the existing assets of GoAP.
Page 14 of 41
2. SYSTEM OVERVIEW OF EPRAGATI CORE PLATFORM
2.1. Meta-model of ePragati Core Platform
(a) “ePragati” is a software platform proposed to be implemented by ePragati Authority,

consisting of 72 projects spanning across all major departments and components of GoAP.
(b) The meta-model of ePragati therefore, consists of layers of applications, built around the
ePragati Core Platform (as defined hereinafter) in the manner set out below:
FIGURE 1: META MODEL OF E PRAGATI CORE PLATFORM
(c) The salient features of the meta-model of ePragati Core Platform are described below:
(i) At the heart of ePragati lies the ePragati Core Platform, which provides program-
level services, citizen related services rendered by each department, services
internal to the department, provides API interface for applications external to the
platform.
(ii) The services of the ePragati Core Platform are critical for achieving the vision of
ePragati Authority and GoAP, represented by the following goals:
 “ONE” Government
 “Citizen-centric” service delivery with a citizen-life-cycle approach. The
paradigm for service delivery “Velocity, Access & Transparency”
 Single point of entry to government services provided through ePragati Portal.
 Progress towards zero touch points in G2C services through simplification,
standardization and automation of services
 Ensure best experience “Minimum Interaction with citizen and Deliver
Maximum Outcomes”.
Page 15 of 41
 Accessibility through multiple channels.

 Integrated interface for communicating by and to the GoAP, inter /intra
departmental business functions and services.
(iii) ePragati Core Platform intends to deliver a proven and technological foundation for
digital transformation of G2C, G2B, G2G services, by enabling
departments/organizations to streamline operations, deliver consistent service, and
modernize operations without interruption.
(iv) ePragati Core Platform enables line departments of GoAP to deploy highly
automated applications without extensive configuration, which can precisely meet
evolving policy needs and real time governance requirements.
(v) ePragati Core Platform enables development of common applications which are
agnostic of the department and relate to horizontal functions of the GoAP, like
performance management, productivity tools, workflow management and core data
management, open API, messaging, user management, system administration and
security. These common applications are built centrally and used in common by all
the line departments, with appropriate configuration required by each department.
FIGURE 2: ARCHITECTURE OF E PRAGATI CORE PLATFORM
Page 16 of 41
3. PROPOSALS, PROJECT AND SCOPE OF WORK
3.1. Proposals
(a) In pursuance of the objectives of GoAP and ePragati Authority as stated in the above, APTS,
on behalf of GoAP and ePragati Authority, has issued this RFP such that interested parties
(“Bidders”) may submit their detailed proposals (“Proposals”) as per provisions of the
RFP/Bidding Documents.
(b) The Proposals would be evaluated on the basis of the evaluation criteria set out in this RFP
(volume-II) in order to identify the successful Bidder for the Project (“Successful Bidder”).
(c) The Successful Bidder shall, upon execution of the Master Services Agreement (hereinafter
defined) (the “Service Provider”), be responsible for implementation of the Project (as
defined hereinafter).
(d) APTS shall receive Proposals pursuant to this RFP in accordance with the terms set forth in
this RFP and other documents provided/ to be provided by APTS pursuant to this RFP, as
modified, altered, amended and clarified from time to time by APTS (collectively, the
“Bidding Documents”), and all Proposals shall be prepared and submitted in accordance
with such terms on or before the date specified in this RFP of this RFP for submission of the
Proposals (the “Due Date”). It is clarified that the term ‘Bidding Documents’ includes the
draft Services Agreement for the Project which shall be executed with the Successful Bidder.
The aforesaid documents and any addenda issued subsequent to this RFP will be deemed to
form part of the Bidding Documents.
3.2. Description of the Project

The ‘Project’ shall comprise of the following services to be provided by the Successful
Bidder:
A. Supply of ePragati Core Platform.

Please refer to Clause3.3 (A) of Vol-I of this RFP for details.
B. Setting up of ePragati Core Platform on the Hosting Platform (as defined hereinafter)
Please refer to Clause3.3 (B) of Vol-I of this RFP for details.
C. Configuration of ePragati Core Platform

Please refer to Clause3.3(C) of Vol-I of this RFP for details.
D. Submission of a manpower rate card for the design, configure (develop)&maintenance

of business application on ePragati Core Platform
Please refer to Clause3.3 (D) of Vol-I this RFP for details.
Page 17 of 41
E. Setting up applications for provision of five services, CLGS, LMS, Integration services,
support & maintenance, design/ configure/development/ continuous improvements &
maintenance of ePragati Portal, APp Store
Please refer to Clause3.3 (E) of Vol-I of this RFP for details.
F. Platform administration, support, operations &maintenance

Please refer to Clause3.3 (F) of Vol-I of this RFP for details.
G. Annual Technical Support & Updates

Please refer to Clause3.3 (G) of Vol-I of this RFP for details.
H. Centre of Excellence (CoE) team

Please refer to Clause3.3 (H) of Vol-I of this RFP for details.
I. Capacity Building
Please refer to Clause3.3 (I) of Vol-I of this RFP for details.
J. Deliverables, Timelines and Payment Schedule

Please refer to Clause3.3 (J) of Vol-I of this RFP for details.
3.3. Detailed Scope of work
(A) Supply of ePragati Core Platform
(1) ePragati Core Platform shall comprise of (i) Zero/ Low-Code Development Platform (as
defined hereinafter) and (ii) Core Components (as defined hereinafter):
(i) “Zero/ Low-Code Development Platform(s)”/ “Platform” means application

development platforms that enable rapid application delivery and/or creation of
applications through configuration of functions, rather than coding those functions
with minimal or no hand coding, and quick set up and deployment. Key features of
these platforms are set out below:
(a) Platform provides visual development environment with drag and drop
features to build, deploy, test and modify e-governance applications.
Consequently, application development time gets significantly reduced.
Modifications and changes in existing applications can also be done quickly
thereby, enabling departments to continuously innovate and improve
service delivery to improve citizen experience. In addition, development on
these platforms requires very minimal coding thereby reducing the need to
learn specific coding languages extensively. In some case, applications could
be developed even with zero coding knowledge.
(b) Platform would enable line departments tailor custom made applications to
suit their specific service requirements quickly and efficiently. The platform
Page 18 of 41
must have features and functionalities for development of citizen-centric

applications of line departments as well as common applications cross-
cutting across departments. The platform should be aptly configured to fulfil
all requirements of ePragati Authority in relation to applications
development.
(c) Platform should also ensure easy or one click deployment of applications
across different delivery channels (web and mobile devices). Moreover,
applications developed on these platforms must be able to seamlessly
integrate with existing systems, applications and cloud services.
(d) Speed: Application deployment required to be measured in weeks not in

months’ time.
(e) Zero/Low Code: Application build with clicks, not code, empowering
business users of GoAP to build applications.
(f) Mobile: Applications will be instantly mobile responsive and a mobile

application (iOS and android) is auto generated.
(g) Connected: Connecting/integrating applications together will be as simple as

pushing a single “connect” button.
(ii) “Core Components” means and shall include the following components:
(a) Please refer to the table below for a graphic representation of core
components of the ePragati Core Platform.
FIGURE 3: CORE C OMPONENTS OF E -PRAGATI CORE PLATFORM

(b) Channels:
Page 19 of 41
i. Mobile Applications: Mobile enablement which includes

Smartphone or Tablets or Hand Held Devices.
ii. Social Channels: Communicate and Broadcast to various social
channels
iii. IoT: Process and provide data from or to Internet of Things devices.
iv. Cloud Applications (SaaS, PaaS): Security and reliability channel for
providing and accessing cloud based solutions.
v. Partners/ Suppliers/Dealers/Distributors: Shared administrative
channel to interact with partners and suppliers.
(c) Common Services:

i. Security: Role based access, encryption of user credentials; Checks
to detect any corruption of data through processing errors or
deliberate acts/acts of sabotage.
ii. Governance: An automated communication channel for exchange of
metadata and service information between service consumers,
providers, policy decision points and additional governance tooling.
iii. Service Registry and Repository: Single source for all the services
and their dependencies.
iv. Monitoring: Administration of the Platform ranging from day to day
transactional data to health.
v. Caching: Speeds up access to data and reduces demand on an
enterprise's bandwidth.
vi. Logging/Reporting: In-Built and customised logging and reporting
frameworks.
(d) IoT Hub:

i. Device Integration & Management: Integrate with and manage
sensors and device
ii. Visual analytics: Rich analytics, filtering, correlation, aggregation
with time and location constraints.
(e) Requirements definition and management

i. Citizen eServices Planning – Plan strategy and vision through direct
capture of requirements and objectives.
ii. eServices Design and Analysis: Map the business process, create
workflows along with compliances, validations and approvals for
those workflows, roles and responsibilities, services for each
department.
iii. Rationalize and harmonize business processes across departments.
iv. Citizen touch point mapping: map and analyses citizen touch points
with departments and e-Services.
v. Enterprise Architecture: map and analyses application, data,
business and technology architecture.
(f) Cloud Integration
Page 20 of 41
i. Policy Management: Optimize policies and organizational

collaboration by centralizing policy management to maintain version
controls, code release and management, while simultaneously
federating policy creation, distribution and enforcement.
ii. PaaS Connectors: Quickly and easily configure integration between
the existing technology and PaaS applications
iii. SaaS Connectors: Quickly and easily configure integrations between
the existing technology and SaaS applications
iv. Cloud Service Provider Management: Manage cloud service
integrations using actionable analytics.
(g) API Layer

i. API Analytics: Graphically analyse the impact of changes to the APIs
and services
ii. API Gateway: Process of designing, developing, deploying versioning
and retiring APIs and services. Metrics for performance dashboards,
SLA violations, and invoicing when using APIs for monetization.
iii. API Portal: Catalogue all APIs, services, schemas, documents and
other related assets in one place, provide easy search capabilities
allow you to quickly find services for re-use.
(h) Process Integration Layer

i. Business Process Automation: Accelerate business by automating
processes, increase productivity, improve accountability and reduce
errors.
ii. Business Rules: Maintain business rules, modify business rules “on
the fly” as per real time requirements.
iii. Business Activity Monitoring (BAM): Track the performance and
effectiveness of various business processes, allowing to
continuously refine the business processes with reusability.
iv. Work Management: Ensure quality by executing optimized manual
workflows in a consistent manner
v. Business Services: Create services to support the business process
and its requirements.
(i) Application & Data Integration Layer

i. Validation: Incorporate validation checks into applications to detect
any corruption of information through processing errors or
deliberate acts.
ii. Managed File Transfer (MFT): Secure file transfers, also support
reliability and guaranteed delivery.
iii. Transformation: Capable of data transformation.
iv. Messaging: Simplify messaging with one solution from streaming
real-time data across enterprise, web and mobile channels.
v. ETL: Allow bulk data movement and transformation in a single step
without affecting performance.
Page 21 of 41
vi. Big Data integration: Integrate data to big data systems like Hadoop
and No-SQL databases.
vii. Technology Adapters: Ability to connect to a number of data
sources.
viii. Application Adapters: Ability to connect to underlying business
applications.
ix. Routing: Capable of routing information according to manually-
configured entries.
x. B2B integration: B2B integration solution enables accurate, real-
time exchange of information with partners/suppliers.
(j) Application Layer

i. Packaged application: Enable and integrate packaged application,
databases and deployed logic to execute new business processes in
real-time.
ii. Custom applications: Support integration / communication with
custom or third party applications.
iii. Legacy/ Applications: Support integration/communication with
underlying legacy applications.
(k) Data Layer

i. Data Warehouse: Centralized data repositories that integrate data
from various transactional, legacy, or external systems, applications,
and sources.
ii. Content Management: Ability to store and retrieve contents open
source document and content management. Open source content
management such as ALFRESCO
iii. Operational Data Store (ODS): Integrate data from multiple sources
for additional operations on the data.
iv. Data Lakes: Stores a vast amount of raw data in its native format
until it is needed.
(l) Data Management

i. In Memory Data Management: Distributed in-memory data
management with extremely low, predictable latency at any scale.
ii. Continuous Query: A data streams query which will evaluate
continuously over time with the continuous arrival of data streams.
iii. Data Profiling/Cleansing: Examine data availability in existing data
sources and ensure that a program operated on clean, correct and
useful data with industry standard data validations and data
standards.
iv. Data Services: Merging with and leveraging external data and
combing data from different repositories
v. Master Data Management: Support both operational and analytical
MDM, able to consolidate, federate and propagate data.
Page 22 of 41
(m) Transactional/No SQL Databases: Open source databases for Ex.: PostgreSQL or
CouchDB to manage structured and unstructured data and content. Please refer
to indicative functional and non-functional requirements of the Platform set out
in Annexure A.
(n) DevOps process mentoring & controlling tools to be proposed and used in the
platform, Patches and Version Management.
(o) SLA Monitoring & Measurement tools.
(p) Compliance Module:

i. Audit Compliance
ii. Secure by Design
iii. Single Sign-on
(2) The Successful Bidder shall deliver/supply the ePragati Core Platform for installation on the
Hosting Platform (as defined hereinafter) in a mode and manner specified by GoAP/ePragati
Authority. The Successful Bidder shall complete such deliver/supply of ePragati Core
Platform within a period of 15 days from the date of execution of the Services Agreement.
(3) The Successful Bidder shall propose readily available COTS products for all services listed as
part of the requirements for a single solution or for combination of solutions/solution for the
ePragati Core Platform.
(B) Setting up of Zero/ Low-Code Development Platform and Core Components on the
Hosting Platform as the “ePragati Core Platform”
(1) The Successful Bidder within the specified time from the date of execution of the Services
Agreement set up Zero/ Low-Code Development Platform and the Core Components on the
Hosting Platform in manner set out in table provided in Clause 3.3(A)(1)(ii)(a) of Part A of
this RFP.
(2) The setting up of the Zero/ Low-Code Development Platform shall be undertaken by the
Successful Bidder.
(3) The setting up of Zero/ Low-Code Development Platform and Core Components on the
Hosting Platform shall be undertaken in the following manner:
(i) The ePragati Core Platform involves following environments to fulfil the
requirements of systems development life cycle:
 Development
 Testing
 Pre-Production
 Production – (DC & DR)
(ii) In each environment, Service Provider needs to set up the platform to on-board
multiple departments, HoDs, Societies/corporations environment as and when on
need basis, metrics as indicated below:
Page 23 of 41
Indicative Environment to be created
Number of Departments to be configured/ integrated 33

Number of line departments – HoDs, Societies, Corporations
330
etc., to be configured/ integrated
(iii) Environments listed should be configured for design, configure (development),

integration of various business applications across various departments across GoAP.
(iv) Environments listed should support development of creation, integration and

distribution of the services for both internal and external touch points.
(v) Environments should have a code repository and automated deployment process to
enable code migration from Development environment to Production. All the above
environments should configure to the requirements of DevOps standards.
(vi) Environments should be configured/ built in such a way that each departments
should be able to develop, build/configure, test deploy and host their application
utilizing the common components that are part of/built for ePragati.
(vii) Environments should be setup in truly Cloud-based services manner in terms of all
aspects of server and system administrations and management.
(viii) All Environments should be Truly Elasticity on Demand: The ePragati Core Platform
should support on demand elastic auto scaling for the applications and ePragati Core
Platform. This configuration should be done in all environments and container based
deployment modelwithout any additional manual effort by system administration
team.
(C) Configuration of ePragati Core Platform
(1) The Successful Bidder shall, in consultation with GoAP/ePragati, configure the ePragati Core
‘Platform as a Service’. The Successful Bidder shall complete the configuration of ePragati
Core Platform within a period of 30 days from the date of execution of the Services
Agreement.
(2) The configuration of the Zero/ Low-Code Development Platform shall be undertaken by the
Service Provider in accordance with this Clause 3.3(A) (1)(ii)(a)and other applicable
provisions of the RFP.
(3) The Successful Bidder should configure the ePragati Core Platform (i) with components
which are proprietary to the OEM or (ii) with components which are proprietary to the OEM
and third party components. The ePragati Core Platform configured by the Successful Bidder
shall comply with all minimum functional and technical requirements of the ePragati Core
Platform. An extensive list of such ePragati Core Platform introduction, Architectural
Page 24 of 41
principles, functional, non-functional and technical requirements is provided in Annexure A.

Some of the key indicative features are listed below:
(i) Truly Elasticity on Demand: The ePragati Core Platform should support on demand
elastic auto scaling for the applications and ePragati Core Platform. This configure
should be done in all environments and container based deployment model.
(ii) Cloud-based services: Public or private cloud solution for cost-effective for high
volume data requirement. ePragati Core Platform should be configured to
standards of PaaS and SaaS capacities.
(iii) The data privacy: The nature of data handled through the Platform is confidential
and sensitive.
(iv) Inter-Operability: The ePragati Core Platform should be supporting the inter
department, intra department along with the data security and privacy of
independent departments.
(v) Flexibility and Agility: Quickly adopt to changing department requirements and
market dynamics;
(vi) Truly ‘Micro-Services’ based eco-system: This feature is mandated because it is a

large federated solution and scaling up the solutions are easily achieved.
(vii) Common Technology stack for ePragati Core platform to make sure to configures
as container based auto elastic scaling.
(4) The Successful Bidder shall implement a highly cost-optimized cloud-based solution, with the
following requirements:
(i) Highstandards of security and privacy shall be complied with.
(ii) There shall be strict prohibition of sharing the data with any other organization.
(iii) The application and data shall be hosted in a cloud data centre identified by GoAP
and/or ePragati Authority.
(5) The Successful Bidder shall undertake the configuration and customization of the Platform to
meet the full requirements of GoAP and/or ePragati Authority.
(6) The Successful Bidder shall prepare the SRS document, solution architecture and design
documents for the complete functionality of the ePragati Core Platform and undertake the
software supply, configuration/development/customization, testing etc.
(7) The Successful Bidder shall perform a detailed assessment of the functional and technical
requirements for the ePragati Core Platform.
Page 25 of 41
(8) The Successful Bidder shall perform detailed system requirement study, detailed high and
low level solution architecture design, solution development/ customization and solution
testing.
(9) The Successful Bidder shall submit the inception report and detailed project work plan for
the complete ePragati Core Platformproject life cycle including COTS product, procurement,
customization, &deployment, operations &maintenance and get the same approved by the
ePragati Authority.
(10) The Successful bidder should preferably follow the latest version of the IEEE Standard 830 &
1233 or equivalent for drafting the SRS and all documents.
(11) The SRS document should be accompanied with a detailed use case document of all
functions of the ePragati Core Platform application system in line with the minimum
requirements specified, and shall submit such documents in both hard and soft copy to the
ePragati Authority.
(12) The Successful Bidder shall prepare and submit a Requirements Traceability Matrix (RTM)
mapping the requirements specified.
(13) The Bidder shall present high level solution and components as part of the technical
evaluation.
(14) The architecture of the core package to be signed off or approved by the competent
authority assigned by GoAP.
(15) The Successful bidder shall conduct its testing process as per the quality assurance plan and
testing strategy (including test plan and test cases) prepared and provided by it as per
solution architecture & design stage. The objective of testing is to ensure that the entire
system in totality, including all hardware, software and human components, which are part
of this Project, perform as per the objectives laid down in this RFP.
(16) The Successful Bidder shall develop/implement a detailed security policy for the Platform
using global standards such as ISO 27001. The security policy developed by the Successful
Bidder shall be in conformity with the security policy of the GoAP.
(17) GoAP shall engage a panel of TPAs for conducting the Acceptance Testing. A detailed Testing
and Quality Assurance methodology to be followed by Successful bidder. The bidder shall
propose Testing and Quality Assurance Methodology as part of Technical proposal. The SI
has to close all the non-compliances as reported by the TPA within the stipulated timelines.
(18) The Successful Bidder shall prepare/update the documents including the following minimal
set of project documentation:
a. All Requirements, Solutions design, Architecture
b. User Manual
Page 26 of 41
c. Training Manual
d. Operations Manual
e. Maintenance Manual
f. Administrator Manual
g. Security Policy, etc.
(19) GoAP will procure/identify a cloud service provider for the infrastructure for ePragati Core
Platform. To enable the same, the Successful Bidder has to propose an appropriate
infrastructure in the Technical Proposal (“i.e. Hosting Platform”):
GoAP will indicate the location of deployment either at Interim Data Center of GoAP in the
State of Andhra Pradesh or any other data centre/ cloud resource as identified by GoAP
which meets the proposed solution requirement and SLA requirements for ePragati Core
Platform; and
(i) should support the concept of modular infrastructure requirements of
ePragati Core Platform.
(20) The Successful Bidder has to provision appropriate type and number of cells for initial data
and year on year growth. The Successful Bidder shall ensure the following:
(i) The data sizing (either usable or raw) has to be done as per requirement
definitions.
(ii) In case of additional infrastructure capacity required beyond planned year on year
growth, GoAP have to supply/ provision to address that requirement.
(iii) The Platform should support high performing optimized infrastructure (server,
storage, and network) deployment for reduced data center foot print.
(iv) The Platform should have separate environments for Development, Testing, and
production for the entire project duration.
(21) All supporting hardware like network load balancer and application load balancer, WAN
optimizer, network equipment, will be provided by the GoAP to support for implement and
working for the proposed ePragati Core Platform.
(22) The Successful Bidder shall provide and ensure all necessary support to the ePragati
Authority/ Third Party Agent (“TPA”) conducting the User Acceptance Testing (“UAT”)
including sharing necessary project documentation, source code (wherever applicable), and
systems designed & developed, testing strategy, test cases developed for the project
executable, test results etc. The Successful Bidder shall be required to facilitate this process
and it shall be incumbent upon the Successful Bidder to meet all the criteria specified in the
Bidding Documents.
(23) The Successful Bidder should prepare and submit UAT reports including:
i. Various tests performed
ii. Test results
Page 27 of 41
iii. Resolution reports for the issues identified during

testing.
(24) ePragati Core Platform after deployment in total has to be free from any security threat. The
Successful Bidder shall have to comply with any non-compliance reported by the third party
Security audit report/ certification process.
(25) In order to ensure effective completion/accomplishment of the above, the ePragati

Authority, in association with the Successful bidder, shall carry out all the necessary
operational acceptance tests including but not limited to:
i. Functionality Test
ii. Database Test
iii. Integration Testing
iv. Unit Test
v. System Test
vi. Security Compliance
vii. Stress test
viii. Performance test, etc.
(26) In order to accept the ePragati core platform, ePragati Authority must be satisfied that all of
the work has been completed and delivered to ePragati Authority’s complete satisfaction
and that all aspects of the ePragati core platform perform acceptably. The operational
acceptance of the System shall only be certified when the proposed system is installed and
configured at the sites according to the design and that all the detailed procedures of
operating them have been carried out by the Successful Bidder in the presence of the
representatives of ePragati Authority.
(27) The Successful Bidder should submit a report for obtaining ePragati Core Platform
‘OPERATIONAL ACCEPTANCE’ after the ‘Go-Live’ phase, based on the TPA (functional/
security) recommendations. The report should include following:
i. All required activities for the Platform to be delivered by the Successful
Bidderand to be accepted by the ePragati Authority
ii. All required System functionality for the Platform to be delivered by the
Successful Bidderand to be accepted by ePragati Authority
iii. All required documentation for the Platform to be prepared by the Successful
Bidderand to be accepted by ePragati Authority
iv. All required training for the Platform to be imparted by the Successful Bidderand
to be accepted by ePragati Authority
v. All identified shortcomings/defects in the Platform have to be addressed along
with remedies to ePragati Authority’s complete satisfaction
vi. All the required Project Documents (manuals, SOP, etc.) have to be submitted
and to be accepted by the ePragati Authority
Based on the above and only after being completely satisfied that at least a minimum 85
percentage of all the users of internal stakeholders have access to the Successful Bidder and
are using the Successful Bidder for the respective functional areas, the ePragati
Authorityshall issue such ‘OPERATIONAL ACCEPTANCE’ of ePragati Core Platform.
Page 28 of 41
(D) Submission of a manpower rate card for the design, develop & maintenance of
application on ePragati Core Platform
(1) The Bidder shall submit a manpower rate card to design, develop &maintenance of business
application on ePragati Core Platform. This rate card shall be submitted as part of Financial
Proposal. Further, the Successful Bidder shall design, develop, test & maintain business
applications on ePragati Core Platform for various stakeholders of ePragati including
government departments/ other governmental entities at the rates mentioned in the rate
card submitted by the Successful Bidder as part of the Financial Proposal.
(2) Various stakeholders of ePragati including government departments/ other Governmental

entities may use the identified resources, identified rates as part of this RFP on need basis or
case to case basis.
(3) On Approval of ePragati Authority including government departments/ other governmental

entities Successful bidder has to on-board resources for a defined and agreed duration.
(4) ePragati Authority including government departments/ other governmental entities reserves
rights for replacement of non-productive resources as defined in the RFP (SLA).
(5) Successful bidder shall ensure right skill, experience, quality resources on the proposed
product to be deployed for project execution. Non-quality, non-productive resources
deployment shall attract penalties.
(6) Successful bidder shall not replace resources not more than once in a calendar year for a
defined platform role. Further the resources permitted for replacement shall not be more
than 10% in given year. Any replacement of the resource shall comply with skill set defined
in Annexure. Any change/ replacement need to be consented by ePragati Authority.
(7) Successful bidder shall deploy only proposed manpower in Technical evaluations; Any
change/ replacement need to be consented by ePragati Authority.
(8) Successful bidder shall assign only one role to one resource
List of Resources
S.No. Platform role Name (Resource Category)
1 Chief Enterprise Architects
2 Solution Architects
3 Delivery Manager
4 Program Manager
5 Data Quality Expert
6 Sr. Business Analyst
Page 29 of 41
List of Resources
S.No. Platform role Name (Resource Category)
7 Senior Business Architects
8 Senior System Architects
9 Data Architects/ Tester
10 Engagement Leader/Project Manager
11 Product Owner / Departmental Project Manager (DPM)
12 Database Administrator
13 Big Data Administrator
14 Functional Tester
15 Performance/Stress/Load Tester
16 UX Designer
17 UI Developer
18 Senior Developer/ Programmer/ Integration Experts
19 Jr. Developer/ Programmer/ Integration Experts
20 Proposed Product Trainer
21 Technical Document Writer
Total
T ABLE 1 LIST OF RESOURCES
For the purposes of the above table, “Man Month” shall mean one person's working time
for a month, or the equivalent. The roles and responsibilities of each of the resource set
out in the above table are detailed in Volume II of this RFP.
For the purposes of this RFP, ‘e-governance’ projects shall mean application of information and
communication technology (ICT) for delivering government services, exchange of information,
communication transactions, integration of various stand-alone systems and services between
government-to-customer (G2C), government-to-business (G2B), government-to-government (G2G)
as well as back office processes and interactions within the entire government framework.
The Successful Bidder shall deploy Account managers’ resources at ePragati Authority office and at
no cost to ePragati authority to manage project operations, line department’s projects, resources
deployment/replacements, logistics, administrative functions, payment & bill processing, and other
contractual terms in RFP and MSA. ePragati Authority will interact only with Account managers.
(E) Setting up applications for provision of five services, CLGS, LMS, Integration
services, support & maintenance, design/ configure/development/ continuous
improvements & maintenance of ePragati Portal, APp Store
Page 30 of 41
(1) Further, as part of the configuration of the Platform, the Successful Bidder shall develop
applications for delivery of five services, CLGS, APP Store and LMS to citizens and GoAP
state ePragati Portal. The details of the applications to be developed by the Successful
Bidder are set out in Annexure A.
Integration/eHighways Services, Support & Maintenance:
(1) The Successful Bidder shall design/ configure/develop and provide continuous
improvements, support &maintenance department’s open/ closed services & APIs, API
portal and Gateway.
(2) The Successful Bidder shall provide support during the services/ APIs integration by the
line departments, internal or external stake holders.
(3) The Successful Bidder shall responsible for integration services/ API policy definition and
security policy configurations.
(4) The Successful bidder shall propose as per the RFP requirement and deploy dedicated
team CoE team at ePragati office in Vijayawada/APCRDA, Amaravati, for the
performance of obligations under this section of the RFP.
(5) Please refer to indicative functional and non-functional requirements of the Platform set
out in Annexure A.
Design/ configure/development and providing continuous improvements, support &

maintenance of ePragati Portal, APP store and other departmental applications:
(1) The Successful Bidder shall provide responsive, interactive, user friendly with a robust
graphical user interface (GUI). The Successful Bidder shall design/ configure/develop the
ePragati Portal and provide continuous improvements, support &maintenance of
ePragati Portal and APP Store.
(2) ePragati Portal and APP store shall serve as first stop to discover GoAP
services/data/information and shall serve as an information gateway to citizens &
residents, government officials, businesses and non-residents. ePragati Portal and APP
Store shall provide services for departments to develop and build new services to
citizens. It shall also have services dashboard, directory/ listing of services offered by
various departments (with extensive search), engaging citizens via. publication of topics
and posting of ideas and e-Pragati administration features.
(3) The Successful Bidder shall responsible for upgrading/ UX refreshment of the UX/UI look
and feel up to the modern trends, desired by ePragati Authority.
Page 31 of 41
The Bidder shall undertake and complete its obligations under Clause 3.3(E) of Part A of this
RFP at the rates stated by the Bidder in the manpower rate card submitted by the Bidder
under Clause 3.3(D) of Part A this RFP as part of its Financial Proposal.
The CoE will be headed by a senior executive of ePragati Authority. CoE will be primary
responsibility to architect, design, develop, test the Setting up applications for provision of
five services, CLGS, LMS, Integration services, support & maintenance, design/
configure/development/ continuous improvements & maintenance of ePragati Portal, APp
Store
(F) Platform Administration, Support, Operations & Maintenance
(1) The Successful Bidder shall be required to provide platform administration, support,
operational and maintenance services for ePragati Core Platform including, all the connected
software and integrated components.
(2) An indicative list of activities and nature of support to be provided is mentioned below:
(a) System Administration and Trouble Shooting
i. Perform ePragati Core Platform Dev, Test, Pre-Production and Production
environments on-boarding each department applications.
ii. Successful bidder is responsible for Platform administration, support and

maintenance of application developed by CoE/line departments/other
government and ensure uptime of ePragati Core Platform and applications as
per SLA’s
iii. Perform system administration tasks such as managing the user access,
creating and managing users, taking backups etc.
iv. Overall monitoring and management of ePragati Core Platform, design and
development of ePragati Portal, CLGS, LMS, APP Store, services integration,
portal services listing integration, database, data migration support and all
other services associated with these facilities to ensure service levels,
performance and availability requirements as prescribed in the Bidding
Documents.
v. Performance tuning of the system to ensure adherence to SLAs and

performance requirements as indicated in the Bidding Documents.
(b) Co-ordination with Network Administration Team

i. Coordinate with the network service providers to maintain and ensure
uptime and performance requirements of the ePragati Core Platform.
(c) Database Administration and Trouble Shooting

i. Undertake end-to-end management of database on an on-going basis to
facilitate smooth functioning and optimum utilization including regular
Page 32 of 41
database backup and periodical testing of backup data, conducting

configuration review to tune database, maintaining the necessary
documentation and managing schemes to database schema, disk space, user
roles, and storage.
ii. Perform- DBA activities of RDMS and No SQL database/Data management.
(d) Co-ordination with cloud service provider Team

i. Coordinate with the cloud service providers to maintain required
provisioning, ensure uptime and performance requirements of the ePragati
Core Platform.
ii. Generate the Infrastructure usage graphs and ensure alerts upon
thresholds to the concerned entities through an EMS tool provided by the
Cloud service provider.
iii. Failure alerts/notifications from cloud provider/ network should be taken

care by PI and required setup is to be coordinated with Network Admin
Team.
(3) The Bidder shall submit a detailed plan for the provision of the administration, support,
operations & maintenance of the Platform.
(4) Entire Platform management, SLAs management etc., must be offered through a portal.
(5) The Successful bidder shall propose and deploy solely responsible dedicated team at
ePragati Authority office for the performance of obligations under this section of the RFP.
(6) The Bidder shall to deploy sufficient and right balanced team to manage the service level
agreements as set out in the Clause 3.4 of Part A of this RFP. Further, the Bidder should
deploy minimum team at ePragati Authority office to manage functions of administration,
support, operations & maintenance.
(7) Contract period as defined in the Volume III
(G) Annual Technical Support& Updates
(1) The Successful Bidder shall ensure along with OEM to carry out the following as a part of
annual technical support:
(a) Successful Bidder and OEM shall maintain data regarding entitlement for software
upgrades, enhancements, refreshes, replacements and maintenance.
(b) If the Operating System or additional copies of Operating System are required to
be installed/ reinstalled/ de-installed, the same should be done as part of ATS.
Page 33 of 41
(c) Successful Bidder and OEM should carry out any requisite adjustments/ changes in
the configuration for implementing different versions of application software.
(d) Successful Bidder and OEM shall, from time to time, provide installation and
configuration of the updates/ upgrades/ new releases/ new versions/ patches/ bug
fixes of the ePragati Core Platform, etc., as required. Successful Bidder and OEM
should provide installation and configuration of free updates/ upgrades/ new
releases/ new versions/ patches/ bug fixes of the ePragati Core Platform and tools
to ePragati Authority, GoAP as and when released by OEM.
(e) Successful Bidder and OEM shall provide software license management and
control. Successful Bidder and OEM shall maintain data regarding entitlement for
software upgrades, enhancements, refreshes, replacements, and maintenance.
(f) Successful Bidder and OEM shall provide technical support for all the licensed
software problems and/or questions, technical guidance, defect and non-defect
related issues. Successful Bidder and OEM shall provide a single-point-of-contact
for software support and provide licensed software support including but not
limited to problem tracking, problem source identification, problem impact
(severity) determination, bypass and recovery support, problem resolution, and
management reporting.
(g) The GoAP aims to reuse the common infrastructure created under AP fibre grid,
SDC, SWAN, MeeSeva, and hence the Successful Bidder will also be required to
coordinate with fibre grid, SDC, SWAN, MeeSeva, teams to ensure that uptime and
performance requirements.
(2) Further, the Successful Bidder shall provide the following:
(a) Technical Helpdesk and trouble ticket management system

The Successful Bidder shall use the centralized helpdesk facility setup by GoAP to
provide helpdesk support for the applications provided under the Platform.
Further, the Successful Bidder will undertake the following:
i. Provide a first level of support for application and technical support at

ePragati Authority office for implementations across the State of Andhra
Pradesh where the software, hardware, and other infrastructure will be
rolled out.
ii. Provide the integrated customer support/helpdesk/ service desk by

establishing <8AM-8PM 16hrs X 7 days> support at the facility created for
reporting ePragati related issues/ problems with the software, hardware
and other infrastructure.
Page 34 of 41
iii. Successful Bidder shall provide necessary software, hardware and other
infrastructure to make fully functional customer support/helpdesk/ service
desk.
iv. ePragati Authority will provide required office space at Vijayawada/

APCRDA/Amaravati, Andhra Pradesh for the CoE and call center.
(b) Incident and Problem management

i. Service desk should address both incident management and problem
management related to the platform and operations. The application
should maintain a classification system that will distinguish the single
occurrence trouble tickets or incidents needing immediate resolution from
in-depth root cause analyses that may require longer term to resolve a
problem.
ii. The flow of events at the call centre should be:

 Event is triggered and forwarded to service desk.
 Service desk submits and updates the trouble ticket.
 Tasks expected:
 Ticket mapping and allocation: According to the severity, the
ticket should be given the priority level. Also, it should map
the ticket to the appropriate personnel for the resolution.
 Updating the status: Update the status of ticket.
 The service desk should log and escalate user interactions and
requests.
 The service desk should have an updateable knowledge base
for technical analysis and further help end-users to search
solutions for previously solved issues.
 The service desk should track the status of registered calls
with interface for call centre, using which call centre can
inform the status to users over phone.
 The service desk should provide historical report indicating
number of calls, time to resolve, status etc., for a specified
period of time.
iii. All relevant infrastructure and supporting system software required for the
deployment and operation of the help desk is to be provided by the
Successful Bidder and shall operate from CoE at the office of CEO, ePragati,
located at Vijayawada/ APCRDA/ Amaravati.
iv. All relevant infrastructure and supporting system software required for the
deployment and operation of the help desk is to be provided by the
Successful Bidder as per the specifications set out in the Bidding
Documents. The system deployed by the Successful Bidder shall comply
with Information Technology Infrastructure Library and ISO 20000 service
specifications.
Page 35 of 41
(c) Automated System Health Monitoring/ e-Transaction & SLA Monitoring Tools
i. The ePragati Authority should be able to measure and monitor the
performance in real time, the number of citizens availing services rendered
through the Platform and/or applications developed on the Platform each
day, month and year, through appropriate tools and reports.
ii. The Successful Bidder shall set up an automated system health monitoring
system which will enable the ePragati Authority to undertake the same.
Such application should have a web interface and should publish online
transaction volume data for each service of each department & district and
provide a drilled down view to the lowest level of the department.
iii. The Service Provider shall provide and measure SLAs by utilizing SLA
monitoring tools and share the data, at all times, with ePragati Authority /
GoAP. Service Provider shall configure the same to fit the SLA
measurement.
iv. The Access to Logs and the administration of the tools shall be with
ePragati authority only. The Service Provider will not have any access to
Logs.
(d) Training & Certification Management

In order to successfully address the capacity requirements of the system
management and the availability of the skilled resources over any point in time,
the Successful Bidder should prepare training plan. The training plan shall capture
training requirements of Architect, business analyst, modeller, UI developer,
developers and administrators in order to successfully handle the ePragati Core
Platform based on the roles and the responsibilities assigned to them. The
indicative training requirements are set out below:
The Successful bidder shall propose and deploy solely platform trainer responsible
dedicated team at ePragati Authority office.
Sl. Description
1 The prospective trainees shall be developers, designers, architects, business
analyst certification program etc.
2 Functions to be performed by such stakeholders shall be administrative and
support management activities.
3 Relevant case studies may be given, if necessary, as part of the training
plan.
4 Training material shall be prepared and distributed to the participants
5 Training plan shall include details like participant names, training location,
date, and time. And all necessary arrangements shall be made to enable
smooth running of sessions.
6 At the end of training sessions, assessments will have to be performed in
order to evaluate the level of understanding of the participants.
Assessments may be in the form of quiz, tests, or real-life simulation. All
necessary arrangements, including preparation of test materials,
Page 36 of 41
administering tests, and evaluating test reports must be planned and done
in advance.
7 The training should cover the processes, products and services of the
Platform.
7 The Information security and their relevance and importance to the
department data confidentiality
8 Knowledge of departmental systems, operational procedures etc.
9 System Administration training to IT Operation Management Team
The training deliverables shall include the following;

Sl. Details
1 Training Plan
2 Training Manuals, User Guides and Materials
3 Documented Evidence of Successful User Training
4 No. of Certificated professional from state of Andhra Pradesh and In-house
employees in GoAP Departments.
(H) Centre of Excellence Team
The furnished office space with plug-and play (treated power, internet) will be provided by
ePragati Authority. The Successful Bidder shall bring all required IT infrastructure for the
deployed resources and responsible for their maintenance & management including
insurance of manpower and equipment.
(1) The Successful Bidder shall establish (provide technical Manpower) Centre of Excellence
(“COE”) for developing a robust body of knowledge for executing government enterprise
architecture and technology planning, government process re-engineering, and application
development for delivery of citizen centric services by all the departments of GoAP. These
techniques, methodologies, and processes developed over time and benchmarked with
globally established practices shall be recognized as best practices of ePragati Authority.
(2) ePragati Authority envisages unique approach that separates architecture (engineering)
from implementation through setting up of Centre of Excellence. The objective of COE is to
build Government of Andhra Pradesh Enterprise Architecture as flexible, changeable, and
reusable and capable of meeting current and future e-governance needs.
(3) Overall ePragati Enterprise Architecture Governance, monitoring, Advisory support design,
development and management of ePragati Core Platform, design, development, Testing of
ePragati Portal, CLGS, LMS, portal services listing integration, database, data migration
support and all other services associated with these facilities to ensure service levels,
performance and availability requirements as prescribed in the Bidding Documents.
(4) COE shall be responsible for overall managed services, advisory services of the ePragati core
Platform.
Page 37 of 41
(5) Center of Excellence (CoE) should, at a most basic level consist of: A team of people that
promote collaboration and using best practices around a specific focus area to drive business
or customer-valued results. This team could be staffed with full-time members combination
of Successful bidder and OEM.
(6) Understanding of the Project Scope of Work & requirements of the Departments and the
State Government.
(7) Design of the overall Detailed Andhra Pradesh State Enterprise Architecture Framework
consisting of a detailed Application Portfolio by representing the Common, Group, Mission,
Cross-cutting and other applications, its functionalities, interrelationships and interactions
and preparation of the standards, protocols and interfaces required for such interactions.
(8) Conducting Stakeholder consultations, to ensure the degree of fit of the proposed
Application Architecture with the business needs of the stakeholders and the feasibility of
implementing the Target Application Architecture considering the constraints that
stakeholder organizations have in terms of resources, capabilities and preparedness for
change.
(9) CoE shall be required to diagnose faults quicker and more reliably on site.
(10) Responsibilities: CoE should serve five basic needs:

(i) Support: For their area of focus, CoE should offer support to the business lines.
This may be through services needed, or providing subject matter experts.
(ii) Guidance: Standards, methodologies, tools and knowledge repositories are
typical approaches to filling this need.
(iii) Shared Learning: Training and certifications, skill assessments, team building
and formalized roles are all ways to encourage shared learning.
(iv) Measurements: CoE should be able to demonstrate they are delivering the
valued results that justified their creation through the use of output metrics.
(v) Governance: Allocating limited resources (budgets, people etc.) across all their
possible use is an important function of CoE. They should ensure organizations
invest in the most valuable automation projects and create economies of scale
for their service offering. In addition, coordination across other corporate
interests is needed to enable the CoE to deliver value.
(11) CoE should refer to any of the support processes within an organization that complement
the line businesses; CoE should focus on processes, Project Management office, Quality
Assurance, Business Analysis, Business communications, Risk and Compliances
(12) Responsibility of Successful Bidder:

(a) To provide leadership, global best practices, architecture governance, research support ,
development Proof of Concept, common utility applications design/ development/ test/
maintain, overall ePragati program delivery responsibility, Program/ project
Page 38 of 41
management, design/development/Quality Assurance and training in connection with

implementation of the Platform and development of applications.
(b) CoE is responsible for overall ePragati Program Managed services and delivery.
(c) CoE is responsible for assignment assigned by ePragati Authority and line department
ePragati program co-ordination.
(d) To provide architecture governance support, guidance and handholding for continuously
improvement, fine-tuning and advancement of the architecture.
(e) The COE team shall be established for a period specified in the Volume-II on all working
days of GoAP comprising of following team members deployed at ePragati Authority
office:
a. Chief Enterprise Architect – 1 nos
b. Solution Architect – 2 nos
c. Sr. Business Analyst – 2 nos
d. Sr. Developer – 2 nos
e. Jr Developer – 5nos
f. Functional Tester – 1 nos
g. Performance/Stress/ Load Tester – 1nos
h. Database Tester -1 nos
i. Database Administrator -1 nos
j. UI developer – 2 nos
k. UX designer – 1 nos
l. Data Quality Expert -1 nos
m. Trainer – on Proposed Platform – 1 nos
n. Technical Document Writer -1 nos
Indicative Minimum Skill sets, Roles and Responsibilities are defined in this RFP.
(f) The Successful bidder shall setup the entire CoE team within specified timelines from the
date of LoA issued. Core team comprises Architects, Managers, Analysts, developers shall
be deployed within specified said no of days from date of LoA issued.
(g) The Successful bidder should able to scale up or down size the CoE team based on the
emerging needs of the project and technological needs of the project with as specified in
the datasheet.
(I) Capacity Building
(1) The OEM shall be required to setup and run OEM’s Certification program with top 15
colleges or as per colleges prescribed by ePragati Authority/ GoAP in the state of Andhra
Pradesh during the contract period.
(2) The OEM should run Certification Program on ePragati Core Platform components with
minimum of 500 students from overall colleges every year throughout the contract
period.
(3) The OEM should able to setup community based license of OEM platform at college to
provide training/developer labs at selected collected with no cost to ePragati Authority.
Page 39 of 41
(4) OEM shall submit an undertaking letter that OEM shall setup and run OEM’s
Certification program with top 15 colleges or as per colleges prescribed by ePragati
Authority in the state of Andhra Pradesh during the contract period.
(J) Deliverables, Timelines and Payment Schedule as per Volume III of RFP
Page 40 of 41
Annexure A
Functional and non-functional Requirements of the Platform
Refer Part 1, 2, 3 & 4 – Separate documents attached as part of this RFP.
(End of the Volume I)
Page 41 of 41

RFP Vol I 20170720 Final

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

RFP Vol I 20170720 Final

Diunggah oleh

Hak Cipta:

Format Tersedia

RFP for Selection of SI for Supply, Configuration of ePragati Core Platform and Services for GoAP (Volume-I)

REQUEST FOR PROPOSAL

IN ANDHRA PRADESH STATE

Andhra Pradesh Technology Services Limited (APTS)

Proprietary & Confidential

Volume I: Functional, Technical and Operational Requirements

Volume II: Commercial and Bidding Terms

Volume III: Contractual and Legal Specifications

This Volume is Volume I

OFFICE OF THE MANAGING DIRECTOR, AP TECHNOLOGYSERVICES LIMITED

News Paper Advertisement

For further details please visit http://www.apts.gov.in/aptsTenders.aspx

Notice Inviting Tender (NIT)

Name of work –Supply, Configuration of ePragati Core Platform and Services

 “Contract/ Agreement/ Contract Agreement/ Master Service Agreement” means the

ACRONYM Full Form

NDA Non-Disclosure Agreement

a. Understand Departments Businesses and its processes.

1. BACKGROUND AND OBJECTIVE

1.1. ePragati Program Overview

 Departments and government agencies interoperate with ease and provide

 Ability to create cross-Governmental services through interoperability,

2. SYSTEM OVERVIEW OF EPRAGATI CORE PLATFORM

2.1. Meta-model of ePragati Core Platform

(a) “ePragati” is a software platform proposed to be implemented by ePragati Authority,

FIGURE 1: META MODEL OF E PRAGATI CORE PLATFORM

 Accessibility through multiple channels.

FIGURE 2: ARCHITECTURE OF E PRAGATI CORE PLATFORM

3. PROPOSALS, PROJECT AND SCOPE OF WORK

3.2. Description of the Project

A. Supply of ePragati Core Platform.

C. Configuration of ePragati Core Platform

D. Submission of a manpower rate card for the design, configure (develop)&maintenance

Please refer to Clause3.3 (D) of Vol-I this RFP for details.

Please refer to Clause3.3 (E) of Vol-I of this RFP for details.

F. Platform administration, support, operations &maintenance

G. Annual Technical Support & Updates

H. Centre of Excellence (CoE) team

J. Deliverables, Timelines and Payment Schedule

3.3. Detailed Scope of work

(A) Supply of ePragati Core Platform

(i) “Zero/ Low-Code Development Platform(s)”/ “Platform” means application

must have features and functionalities for development of citizen-centric

(d) Speed: Application deployment required to be measured in weeks not in

(f) Mobile: Applications will be instantly mobile responsive and a mobile

(g) Connected: Connecting/integrating applications together will be as simple as

FIGURE 3: CORE C OMPONENTS OF E -PRAGATI CORE PLATFORM

i. Mobile Applications: Mobile enablement which includes

(c) Common Services:

(d) IoT Hub:

(e) Requirements definition and management

(f) Cloud Integration

i. Policy Management: Optimize policies and organizational

(g) API Layer

(h) Process Integration Layer

(i) Application & Data Integration Layer

(j) Application Layer

(k) Data Layer

(l) Data Management

(p) Compliance Module:

Indicative Environment to be created

Number of Departments to be configured/ integrated 33

(iii) Environments listed should be configured for design, configure (development),

(iv) Environments listed should support development of creation, integration and