RFP Vol 2 Smart Payment City Mobile App and Portal

REQUEST FOR PROPOSAL
for
Volume 2 - Scope of Work
Selection of Agency for implementation and
operations of Raipur City Smart Payment System (City
Tender
Smart Card, Mobile AppNumber: xxx
and Portal) on PPP model
Dated: xxx
Volume 2 – Scope of Work

RFP Number: 231/ RSCL/PAYMENT APP/2017-18
Date: 25th May 2017
Last date for Bid Submission: 19th June 2017
Invited by
Raipur Smart City Limited (RSCL)
Near Indoor Stadium, Opposite Budhatalab,
Raipur-492001, Chhattisgarh.
Selection of Agency for implementation and operations of Raipur City Smart Payment System (City Smart Card,
Mobile App and Portal) on PPP model
Contents
Glossary ...................................................................................... 6
1. Introduction........................................................................... 8
1.1. About Raipur Smart City Limited (RSCL) ................................................................... 8
1.2. About the project ................................................................................................................... 8
1.2.1. Vision for Raipur City Smart Card, Integrated Service Delivery Portal &
Mobile app integrated with wallet project .............................................................................. 9
2. Solution Overview .................................................................12

2.1. Raipur City Smart Payment System Overview ........................................................ 12
2.2. General description of the Project ............................................................................... 13
3. Scope of Work ...................................................................... 14
4. Detailed Requirement Specifications and scope of Common

City Payment System ................................................................. 18
4.1. Sourcing, Designing & Personalization of RAIPUR contactless SMART
Card 18
4.2. Supply/ Distribution of RAIPUR contactless SMART Cards ............................. 18
4.3. Marketing/Promotion of RAIPUR contactless SMART Card, Wallet ............ 19
4.4. Loyalty Program for RAIPUR contactless SMART Card, Wallet...................... 19
4.5. SMART Card Application and Card Data format.................................................... 19
4.6. Automatic Fare Collection (enabled for NFC payments) .................................... 20
4.7. SMART Card Application Interfaces and Integrations ........................................ 20
4.8. Smart Card Issuance .......................................................................................................... 21
4.9. Top-Up channels and service delivery points .......................................................... 22
4.10. E-Payment services for Top up .................................................................................. 22
4.11. Central Clearance House management (CCHM) ................................................ 22
4.12. Security................................................................................................................................ 22
4.13. Acceptance Testing of Agency System..................................................................... 23
4.14. Documentation................................................................................................................. 24
2
4.15. Transition Management ............................................................................................... 24

4.16. Exit management............................................................................................................. 24
4.17. Support Management including Help Desk ......................................................... 25
4.18. Provision, Deployment and supervision of personnel ..................................... 27
4.19. SLA Monitoring ................................................................................................................ 27
4.20. Training ............................................................................................................................... 29
4.21. Payment gateway ............................................................................................................. 29
5. Technical requirement ..........................................................31

5.1. Technical Specifications for mPOS / micro ATM ................................................... 31
5.2. Technical Specifications for NFC Card Reader ....................................................... 32
5.3. Functional Specifications for Tablet and smartphone based mobile
applications (Android and iOS) for Raipur citizens ......................................................... 32
5.4. Specifications for Web Portal ........................................................................................ 33
5.5. Specifications for Septic Tank Clearance .................................................................. 34
5.6. Availability ............................................................................................................................. 34
5.7. Scalability and performance........................................................................................... 35
5.8. Adaptability ........................................................................................................................... 35
5.9. User creation and administration ................................................................................ 35
5.10. Reliability and seamless integration ....................................................................... 35
5.11. Testability ........................................................................................................................... 36
5.12. Transaction security ...................................................................................................... 36
5.13. Back up ................................................................................................................................ 36
5.14. Integration of the proposed solution with Raipur City Command and
Control Centre .................................................................................................................................. 36
6. Project Implementation ....................................................... 37

6.1. Submission of Documents ............................................................................................... 37
6.2. Timeline and Phasing ........................................................................................................ 37
6.3. Testing and System Audit during Implementation of the Project ................... 40
3
Disclaimer
The information contained in this Request for Proposal document (“RFP”) whether subsequently
provided to the bidders, (“Bidder/s”) verbally or in documentary form by Raipur Smart City
Development Limited (henceforth referred to as “RSCL” in this document) or any of its
employees or advisors, is provided to Bidders on the terms and conditions set out in this Tender
document and any other terms and conditions subject to which such information is provided.
This RFP is not an agreement and is not an offer or invitation to any party. The purpose of this
RFP is to provide the Bidders or any other person with information to assist the formulation of
their financial offers (“Bid”). This RFP includes statements, which reflect various assumptions
and assessments arrived at by RSCL in relation to this scope. This Tender document does not
purport to contain all the information each Bidder may require. This Tender document may not
be appropriate for all persons, and it is not possible for the Chief Executive Officer, RSCL and
their employees or advisors to consider the objectives, technical expertise and particular needs of
each Bidder. The assumptions, assessments, statements and information contained in the Bid
documents, may not be complete, accurate, adequate or correct. Each Bidder must therefore
conduct its own analysis of the information contained in this RFP and to seek its own professional
advice from appropriate sources.
Information provided in this Tender document to the Bidder 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. RSCL accepts no responsibility for the accuracy or otherwise for
any interpretation of opinion on law expressed herein.
RSCL and their employees and advisors make no representation or warranty and shall incur no
liability to any person, including the Bidder under law, statute, rules or regulations or tort, the
principles of restitution or unjust enrichment or otherwise for any loss, cost, expense or damage
which may\ arise from or be incurred or suffered on account of anything contained in this RFP or
otherwise, including the accuracy, reliability or completeness of the RFP, and any assessment,
assumption, statement or information contained therein or deemed to form part of this RFP or
arising in any way in this Selection Process.
RSCL also 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.
RSCL may in its absolute discretion, but without being under any obligation to do so, can amend
or supplement the information in this RFP.
4
The issue of this Tender document does not imply that RSCL is bound to select a Bidder or to
appoint the Selected Bidder (as defined hereinafter), for implementation and RSCL reserves the
right to reject all or any of the Bidders or Bids without assigning any reason whatsoever.
The Bidder shall bear all its costs associated with or relating to the preparation and submission of
its Bid including but not limited to preparation, copying, postage, delivery fees, expenses
associated with any demonstrations or presentations which may be required by RSCL or any other
costs incurred in connection with or relating to its Bid. All such costs and expenses will remain
with the Bidder and RSCL shall not be liable in any manner whatsoever for the same or for any
other costs or other expenses incurred by a Bidder in preparation for submission of the Bid,
regardless of the conduct or outcome of the Selection process
5
Glossary
Terms Meaning
BOM Bill of Material
BEC Bidders Evaluation Committee
CCHS Central Clearing House System
CEO Chief Executive Officer
DD Demand Draft
EMD Earnest Money Deposit
POS Point of Sale System
GoC Government of Chhattisgarh
GPS Global Positioning System
HOD Head of Department
ICT Information and Communication Technology
IT Information Technology
ITES Information Technology Enabled Services
INR Indian Rupee
LoI Letter of Intent
NPV Net Present Value
OEM Original Equipment Manufacture
PBG Performance Bank Guarantee
PDD Proposal Due Date
PoC Proof of Concept
PQ Pre-Qualification
PSU Public Sector Undertaking
RFP Request for Proposal
PV Present Value
TAT Turn-Around-Time
FI Financial Institution
SLA Service Level Agreement
RMC Raipur Municipal Corporation
6
Terms Meaning
RSCL Raipur Smart City Limited
TQ Technical Qualification
7
1. Introduction
Smart city Mission was launched by Government of India on 25 June, 2015. Raipur city was
selected among 100 cities to be developed as smart city in India due to various achievements,
initiatives and all-inclusive approach. Accordingly Raipur city had submitted “Smart City
Proposal” (SCP) for Raipur City to Ministry of Urban Development, Government of India with
required consent of Government of Chhattisgarh and statutory authority of Raipur Municipal
Corporation.
The city of Raipur has been selected to be developed into a smart city under the fast track mode
of first phase of the Smart Cities Mission. The Smart City Proposal of Raipur includes the smart
city solutions which involve the use of technology, information and data to improve infrastructure
and services within the city of Raipur (The Smart Solutions Projects).
Presently there is no centralized system with RMC for electronic collection of payments regarding
municipal taxes and services. Tracking municipal collections and their settlement, delivery of
services and citizen feedback. Until the collection of municipal charges is digitized, payment
settlement and citizen relationship management cannot be effective.
Therefore a need was felt to have an Integrated System that can be targeted especially to those
departments that are using manual and paper based operations for processing municipal services
and payments and enable payment and delivery of services through Mobile App, Portal while
leveraging a common smart card for the city.
The Client- Raipur Smart City Limited (RSCL) now intends to select an Agency to design,
implement and operate the Raipur City Smart Card, Integrated Service Delivery Portal
& Mobile app integrated with wallet as one of the integrated smart solutions on PPP basis
which is being referred to as Raipur City Smart Payment System (RCSPS) hereafter.
1.1. About Raipur Smart City Limited (RSCL)
As per the GoI guidelines, Raipur Municipal Corporation has formed a separate Special Purpose
Vehicle (SPV) as Raipur Smart City Limited (RSCL) for the implementation of Smart Solution
Projects under the smart city mission for the city of Raipur. This SPV shall carry end to end
responsibility for vendor selection, implementation and operationalization of various smart city
projects.
1.2. About the project
The vision of the Raipur Smart City is “to facilitate creation of economically vibrant, inclusive,
efficient and sustainable urban habitats.” Its mission is to “promote cities as engines of economic
growth through improvement in the quality of urban life by facilitating creation of quality urban
8
infrastructure, with assured service levels and efficient governance to transform Raipur into a
digitally empowered society and knowledge economy.”
Raipur Smart City Limited (RSCL) plans to implement Raipur City Smart Card, Integrated Service
Delivery Portal & Mobile app integrated with wallet, with an aim to offer citizens a common
platform of payment facility which would enable them to pay for any services within the city. The
system is envisaged to bring about an enormous ease to citizens by way of paying electronically
using a smart card / wallet for all perceivable services including city transport, municipal services,
entertainment and amusement activities, parking, bill payments, utility payments, laundry, bike
sharing, challan payment etc. This System will deliver City Payment Gateway which could aid
integration of people, business and government on single platform. This will compliment
initiatives for smart services as part of the smart city initiative of RSCL.
The overarching idea of Raipur City Smart Card, Integrated Service Delivery Portal & Mobile app
integrated with wallet project is to combine all modes of payments using a single payment
instrument. Integrated payment schemes aim at facilitating integration of transport systems
along with other services thus making payment services as easy and attractive as possible. The
integration of tariffs, operators and modes is proved to have a positive impact on transport
demand and other collection services. In their electronic version, integrated card schemes could
be extended to other applications. Most experts agree that multiple services, such as for purposes
of retail or leisure or e-payment, seem to have a considerable attractiveness for the public
transport sector, as this means added value for the customers.
1.2.1. Vision for Raipur City Smart Card, Integrated Service Delivery Portal &
Mobile app integrated with wallet project
RSCL intends to implement interoperable payment ecosystem through smart fare media like
cards or mobile phones. RSCL intends to offer integrated electronic payment services to its users
by making common smart card based system available to them closely integrated with services
delivery portal and a mobile app. This common smart card would be based on the unified payment
and identification mechanism riding on the popularity of contactless card technology. It aims to
simplify the life for all residents and visitors of the city by addressing common issues such as lack
of proper change while making payments for parking, bus tickets, etc., paying for municipal
services (taxes, licenses, etc.) and high queuing times at public places to access amenities.
The initiative would offer tremendous ease and benefits to users by enabling a single instrument
powerful enough to cater to all the transit and other needs. Commuter can use the common smart
card for travelling from one place to another without getting into long queues to buy tickets
through cash. The common smart card shall act as electronic money facilitating the travel
payment and other payment needs of the users within Raipur City. It also enables access to
electronic payment infrastructure services to all strata's of society and to every nook and corner
9
of the city. It also aids in green travel initiative by enabling lesser travel by citizens for payment
services other than transport services. The Project is one of the key initiatives under the Smart
City Project of the Government of India under which Raipur has been selected as a Smart City.
The smart card should cater to all fare media types like daily, weekly, monthly passes and other
ticketing and payments to enable multimodal transport in the city. The Smart Card shall be used
as an e-Purse/Validity based product to meet commuters travelling and other payment needs. The
Smart Card can also be used in retail outlets for making payments.
Advantages of using Raipur City Smart Payment System:
1. Raipur City Smart Card, mobile app and web portal will offer independence to users paying
for services within Raipur city.
2. Raipur City Smart Card can be operated within RMC services areas or outside as well and
hence will aid faster adoption.
3. Raipur City Smart Card will offer seamless transport payment services and aid cashless travel
services for commuters enabling multimodal transport payments.
4. Since Raipur City Smart Card shall be designed with open standards data format, it can be
easily extended to other modes of transport within city like auto rickshaws, e rickshaws, taxis
etc.
5. Smart Fare Collection will permit to contribute to the overall improvement of the public
transport network level of services, image, accessibility, integration with the main aim to
facilitate and/or increase the use of public transport owing to the fact that with Raipur City
Smart Card, Commuters can experience seamless transit experience across transit eco system.
6. Raipur City Smart Cards are secured, can't be read, copied, manipulated with, counterfeited
or duplicated
7. Raipur City Smart Cards protect privacy where needed.
8. Raipur City Smart Cards are re-writable and can be recharged thousands of times
9. Raipur City Smart Card can contain digital log with location, date, time, person's stamp to
record every transaction
10. Raipur City Smart Card payment system eliminates cash from the payment systems and
reduces monetary leakage.
10
11. Selected Agency manages the entire ecosystem through its Central Clearing House System.
The entire system shall enable availability of data ( regarding citizens, service requests and
payments) in electronic form which in turn can be used for
 Automatic reconciliation and settlement
 Planning delivery of existing and upcoming services
 Make improvements or new services
 Development of smart city infrastructure for Citizen Relationship Management (CRM)
 Predict consumption with regard to supply of utilities –water, e-toilets , water
11
2. Solution Overview
2.1. Raipur City Smart Payment System Overview
The integrated view of Raipur City Smart Card, Mobile app and Portal with associated payment
infrastructure shall form the Raipur City Smart Payment System (RCSPS) which shall
enable you to have a detailed understanding of RSCL’s view on implementing city wide automated
payments system, mobile app and integrated portal. The system being proposed to be
implemented will act as a city foundation framework for integrating objectives of having one card
& wallet for all G2C and B2C services in the city including integrated transit fare management
system and other services provided by the RMC within Raipur city. The system shall also allow
the operator to leverage the common platform to deliver B2C services. The RCSPS is proposed to
be utilized for payments made by the citizens for Municipal Services, Parking services, current
City Bus Service and any other future public transit system that may be implemented within
Raipur City and other payment services required by RSCL as already mentioned in this document.
Figure 1: Conceptual Architecture of Raipur City Smart Payment System
12
2.2. General description of the Project

The objective of this project is to provide open loop smart card system, mobile app and web portal
for the purpose of payments services for RMC, payment for city bus service, parking, etc. as agreed
between the bidder and RSCL. The Bidder shall be responsible for installation of the end to end
open loop smart card based RCSPS system at the required locations.
The system security shall include, as a minimum, protection against, fraud, theft, falsification of
data, false accounting, external threats, denial of service, eavesdropping, loss or corruption of
information, masquerading (spoofing) and unauthorized access, etc. The system shall adhere to
industry recognized International and National standards and practices published.
The Bidder shall design, supply, install, test, commission and maintain the equipment hardware,
software, accessories, and interfaces required to complete the ecosystem for RCSPS as per the
project requirements.
The bidder shall design, develop and maintain the open loop smart card top-Up channels and e-
payment services. The bidder shall design, develop and be responsible for the maintenance and
management of required systems.
The bidder shall deploy system for RSCL to be able to perform day to day monitoring of the
operations and the bidder shall provision for the MIS reporting and would be responsible for
generation of MIS reports as per the requirements of the RSCL till the duration of the contract.
The bidder shall be responsible for the maintenance of the equipment hardware, software, etc.
and would be responsible for repairing and replacement in case of failures or defects as part of
the defect liability period obligation of the contract for the contract duration.
The bidder shall at all times comply with the project schedule provided by RSCL.
The Bidder shall verify by analysis, testing and system demonstrations, as required, the
operability, reliability, availability, maintainability and safety requirements stated in the
Specifications.
13
3. Scope of Work
Invest, Design, Development, procurement, supply, integration and implementation of Open

Loop EMV Compliant Common Card Payment System, Mobile Wallet, City Mobile app and Web
Portal for front end automation of G2C, G2G and G2B services covering Municipal Services and
other non-financial services.
The overall scope covers following three components:
1. Mobile App covering Non-financial application and integrated with a mobile wallet for
payments with loyalty solution
2. Portal (front end) for:
a. Citizen centric Municipal Services, general services
b. Loyalty solutions
3. Smart Card systems
The key services shall primarily cover but will not be limited to the following:
S.No. Services to be Covered
1 Municipal Services (taxes, bill, service charges etc.)
2 Public Parking – On street and Off Street (including multi-level parking) in the city
3 Utility (water) Payments
4 Multimodal transport Automatic Ticketing, Fare collection System (City bus, BRTS,
auto-rickshaw, e-rickshaw)
5 Location Based services
6 Enablement of card / wallet payment for all smart initiatives in Raipur wherever
applicable. Following shall be covered at minimum :
 Rent a Cycle scheme to be implemented in City
 Smart Parking payments
 On demand waste collection
 Pay per use laundry
 Public Transit, Parking and other VAS and Municipal Services
 Integration with City Command and Control Centre
 Bus Transit System
 Traffic Challan payment
 Transit Fare collection system integrated for BRTS, Bus and IPTs including Taxis and
Rickshaws
14
The bidder shall be responsible for successful completion / execution of the activities listed in the
following table of requirements to enable RSCL’s vision of Raipur Smart City Card, as well as
maintenance of the solution.
The following table outlines the broad areas of scope of work for bidder.
S. No. Scope of Work
Raipur Smart Card
1 Design, Manufacturing/Sourcing, Supply/Distribution, Marketing of Raipur

City Card (Mor Raipur Card)
2 Implement and maintain an interoperable SMART Card Application and Card
Data format & L2 Kernel for fare management Devices
3 Card Issuance at banks/merchant outlets and Personalization Management
Providing transaction clearing, reconciliation of accounts and money settlement

functions for all parties participating in the RMC co-branded smart card program.
4 Design, Develop and maintain Top-Up channels and e-Payment services including
service delivery points within Raipur city. In addition to the physical top up of the
Raipur smart cards from Point of Sale machines and service delivery locations within
city as per RFP, setup of web enabled online card money top-up over dedicated web
channel with payment gateways and other banking channels.
5 Design and implement a Loyalty Management and Promotional Program to encourage

increased adoption and usage of the Common Payment Card.
6 Maintenance of Central Clearance house management
7 Deployment & Maintenance of Central Smart Card Host Management
8 The Smart Card shall be branded for Smart City Raipur for all G2C services and for
payment for goods and services for B2C under the regulatory framework of the RBI
Manage the entire smart card life cycle management of open standards card
specifications, card applications, payment scheme, card account management and card
transactions.
City Mobile App, Mobile Wallet and Portal
15
1 Design, test, commission and maintain an integrated services city portal and
Raipur Smart City app which covers all citizen based services and a wide range of
non-financial services and information. This should be lite and have a smart user
experience and smooth navigation.
2 Develop suitable application for Road Transport that integrates with the Transit
Fare Collection System, Smart card payment system and finance system of RMC
including maintenance and support for the application during the contract period.
3 Develop suitable application for vehicle booking and scheduling for septage tanker
services in the city.
4 The App should also be integrated with a mobile wallet which can be white labelled
for the Raipur Smart city Mobile App. The bidder will be required to maintain the
software and interfaces required to complete the ecosystem as per the project
requirements. It will provide a complete interface with 3rd party service providers.
5 The bidder should establish top-up channels and mobile payment services. The
bidder shall design, develop and be responsible for the maintenance and
management of required systems to keep the mobile wallet functioning
6 Should be based on Open Standards and interoperable solution and integration

ready for future applications at RMC based on APIs and Web Services.
7 Mobile App, portal, wallet security shall include, as a minimum, protection against,
fraud, falsification of data, false accounting, external threats, denial of service,
eavesdropping, loss or corruption of information, masquerading (spoofing) and
unauthorized access, etc. The system shall adhere to industry recognized
International and National standards and practices published from time to time.
8 The app and portal shall provide front end for delivery of all services as mentioned
in the annexure 11.2, Vol 1.
The scope of works and services for Raipur Smart Card would include:
 Procurement, Personalization and Issuance of contactless EMV / RuPay smart cards for
ticketing and payment for goods and services outside RMC transit in line with the
Reserve Bank of India regulations/approvals.
16
 Providing transaction clearing, reconciliation of accounts and money settlement

functions for all parties participating in the Raipur smart card program.
 In addition to the physical top up of the RAIPUR smart cards from Point of Sale machines
and service delivery locations within city, setup of web and mobile app enabled online
card money top-up over dedicated web channel with payment gateways and other
banking channels.
 Provide card customer support over Phone, Internet and at bank branch level for card
issuance, renewal, refunds, customer account management and customer support with
payment gateway and authentication services as per RBI requirements.
 Manage the entire smart card life cycle management of open standards card
specifications, card applications, payment scheme, card account management and card
transactions.
 Develop suitable application for RSCL that can integrate with the Smart card payment
system and future systems of RMC including maintenance and support for the
application during the contract period.
 Smart Card should provide facility for creation of Monthly pass in Bus and Parking
services. This information should be stored in Smart Card itself and there should not be
any separate requirement of bus passes or parking stickers.
 Manage and undertake marketing and sales of RAIPUR smart cards, the RAIPUR mobile
application and interfaces through web portal with commuters, retailers/ merchants in
Raipur Region and urban agglomeration around with the objective of increasing card
penetration, mobile payment and doing e commerce transactions.
 Enable and undertake card usage over multi modal transport, retail merchant, public
utility payment, toll, petrol stations etc. with a view to make it the card of choice for
citizens and travelers in Raipur as well as to augment the non-fare box income for RMC.
 In this respect also enable installation of systems and processes at such usage points
outside RMC transit through independent arrangement directly with the respective
organizations.
 The bidder shall follow the schedules of works and supply and shall complete the sections
of the works by the key dates set out in the RFP document.
Please refer Annexure 11.2 Vol 1, for scope of services included as part of City Mobile app and Web
Portal.
17
4. Detailed Requirement Specifications and scope of Common City Payment

System
4.1. Sourcing, Designing & Personalization of RAIPUR contactless SMART Card

1. Selected agency shall source the EMV Compliant contactless Smart Card as per minimum
specifications given in the RFP and issue to the citizen after personalisation as approved by
RMC / RSCL. For select cases like tourists / people coming from
2. Selected Agency shall prepare detailed sample look and feel design specification of RAIPUR
SMART card & get it approved by RSCL before printing
3. Selected Agency or its appointed card agency should perform personalization of the card as
per approved branding & design.
4. Selected Agency shall maintain necessary hardware/software infrastructure to perform
personalization on the pre-paid smart card at Selected Agency’s owned facility.
5. Selected Agency should maintain RAIPUR Smart card & associated applications in a secure
location and comply with security guideline as per the PCI DSS guidelines
6. Characteristics of Smart Cards should be
 The smart card should be compliant with all EMV regulations and should be a dual
interface card (contactless also) capable of performing EMV and transit transactions
on the relevant terminals.
 The Smart Card to be used shall be ISO 14443/ISO18092 compliant.
 The Smart Card shall have an operating frequency of 13.56 MHz
 The dimensions of the Smart Card shall comply with ISO 7810
 The resistance of the Smart Card to mechanical stress and chemicals shall comply with
ISO 10373
4.2. Supply/ Distribution of RAIPUR contactless SMART Cards
1. Selected Agency shall set up supply/distribution points for the Smart cards from all RMC
designated locations (Ward offices / Zone offices), Banks and other private distribution
channels across the city. It should also enable the non-personalised card distribution for select
cases e.g. tourists etc. with due verification process.
2. The selected agency shall develop detailed guidelines and processes for issuance and usage of
Raipur City Smart Card.
3. The selected agency should also provide facility for personalised card sent directly to home by
leveraging logistics channels in the city without any cost to the citizen for the same.
4. Selected Agency should maintain the web based inventory management of Smart cards as
RMC locations, Agency’s branch location and Agency identified merchant locations. The same
can be enabled through centralised card hosting system.
5. Selected Agency should supply only pre-paid Smart card at distribution points in the city.
18
4.3. Marketing/Promotion of RAIPUR contactless SMART Card, Wallet

1. The Smart Card should be Open loop and should allow usage at all places, which accept
payment though cards.
2. Selected Agency should build marketing strategy to increase adoption and usage of RAIPUR
SMART Cards. The same should be reviewed and modified from time to time based on
requirements / circumstances.
3. Selected Agency should market the smart card with IEC materials through multiple channels
such as (web ads, FM, radio, TV, Posters, brochures) at its own cost.
4. Selected Agency should implement a loyalty benefit program integrated with Raipur City
Card, Mobile App & Wallet. Provide loyalty benefits for users of this card.
4.4. Loyalty Program for RAIPUR contactless SMART Card, Wallet

1. The Loyalty program associated with Raipur City Card and Mobile App / Wallet should enable
citizens to earn and accumulate loyalty points for their transactions and interactions using the
Raipur City Smart Payment System
2. Citizen should also be able to earn loyalty points at B2C merchant partners signed up to be
part of the loyalty programme.
3. Citizen should be able to redeem the loyalty points / benefits for personalized products,
discount vouchers, movie tickets, mobile recharge, electronic items, travel vouchers,
merchandise, etc. through Integrated Portal / Mobile app.
4. Citizen should also be able to redeem the loyalty benefits while performing the service
transaction to adjust the same.
5. Customers need to be given choice for redemption partly by paying through accrued points
and remaining through Cards.
6. The loyalty programme should be designed such a way that it remains dynamic and swift
allowing for changes and modifications to programme structure as per strategic and tactical
needs.
7. The loyalty program and associated benefits needs to be arrived in discussion with RSCL /
RMC and would be made applicable only after approval of RSCL/RMC from time to time.
4.5. SMART Card Application and Card Data format

1. The selected agency can leverage its smart card application & all associated software /
applications and hardware on Platform as a Service/ Software as a Service / Managed Services
model and customise the same to enable the Raipur City Smart Payment System functions
and delivery of services to promote cashless delivery of services in Raipur.
2. While working on any of these models, the agency shall not use its own brand / company logo
etc. on mobile app / portal etc. without prior permission from RSCL / RMC.
3. Provide L2 EMV Kernel for fare management devices.
4. SMART card application should conform to interoperable, open standards
19
5. Selected Agency shall define the Interoperable data format and standards of Smart Cards and
terminal interfaces for e.g. KEY and SAM management etc.
6. Selected Agency shall provide all relevant documentation, card specification and terminal
interfaces for e.g. KEY and SAM management etc.
7. Selected Agency shall provide exclusive Intellectual Property Rights (IPR) of smart card data
format and standards to RSCL/ RMC.
8. Inter-operable Data formats should allow citizen to allow the use of smart cards in any
merchant location, other transport operators joining program, the standards setup for RMC
as well as RMC operated locations.
9. Selected Agency shall design the data format and standards for terminal interface.
10. The solution should be PCI DSS (Payment Card Industry Data Security Standard) certified
and internationally accredited
11. RSCL may appoint 3rd party agency to certify the data formats.
4.6. Automatic Fare Collection (enabled for NFC payments)
The selected agency shall assess the existing fare collection system and implement the NFC
enabled fare collection system to enable multimodal transit payments in buses, taxi, e-Rickshaws,
Auto Rickshaws etc.
The selected vendor would need to create an integrated fare collection mechanism using
interoperable standards, hence the devices and media thereby has to be complementary in nature.
The end state requirement of this implementation shall be that of integrated fare management
and collection regime which will render its services to all types of transit system operated within
the city in a unified manner. In-order to meet diverse need of commuter and application, following
media types shall be offered to users for payment of fare purposes:
· Open loop EMV/RuPay with Contactless Smartcards
· Automatic Fare Collection system
· Mobile Wallet integrated with Raipur Mobile App
4.7. SMART Card Application Interfaces and Integrations

The agency must create the interface between Raipur City Smart Payment System and various
applications / systems to enable payments through Raipur City Smart Card / Mobile App /
Portal / Wallet. The agency shall also install POS systems to enable contactless payment using
cards or Mobile Wallets. All integrations of RCSPS with other systems for transaction clearance,
card host management, Automated Ticketing, etc. need to be managed by the Selected Agency.
20
Given below is the list of key RSCL / RMC systems for which the same needs to be enabled:
 Rent a Cycle scheme to be implemented in City

 Smart Parking payments
 On demand waste collection
 Pay per use laundry
 Public Transit, Parking and other VAS and Municipal Services
 Integration with City Command and Control Centre for reporting and monitoring
 Traffic Challan payment
 Transit Fare collection system / Automated Fare Collection system integrated for BRTS,
Bus and IPTs including Taxis and Rickshaws
 Integration with fare collection system :
4.8. Smart Card Issuance

1. Selected Agency shall take whole responsibility of Issuance and management of SMART cards
2. Selected Agency shall provide necessary card personalization service to RSCL based out of
Selected Agency’s owned facility.
3. Selected Agency should issue pre-paid open loop contactless SMART cards to all citizens of
Raipur as per the guidelines of Selected Agency and RBI.
4. Selected Agency should equip RMC with all the required equipment’s at RMC to enable the
functioning of smart cards
5. Selected Agency should maintain entire life cycle indicative activities of Smart card such as
 Issuance of Smart card
 Activation of Smart card
 Deactivation of Smart card
 Blocking of Smart card
 Blacklist of Smart card
 Decommission of Smart card
 Re-load / Reuse of Smart card
 Loss of Smart card
 Others etc.
6. Selected Agency should maintain dedicated helpdesk /call centre to handle calls for RAIPUR
smart card issues and grievances.
7. Selected Agency should enable web based, mobile based or any other channels to RMC
channels to apply or request for RAIPUR smart card application.
21
4.9. Top-Up channels and service delivery points

1. Selected Agency should design develop and maintain top-up channels to cater to different
channels to recharge SMART card.
2. Selected Agency should enable different channels to top up the RAIPUR SMART card i.e.
through web-based portal, mobile based app, POS machines at merchant outlet channels and
any other channels suggested by Selected Agency.
3. Citizen should be able to top up prepaid SMART card up to the monetary limits and process
as regulated by RBI or any other regulating agency.
4. Citizen should able to check balance on the pre-paid card via SMS, or web based channels, etc.
5. The Citizen should be able to adjust loyalty points / benefits for recharge of the prepaid Raipur
Smart City Card
6. Establish, the necessary interfaces required for enabling top-up channels like POS, Mobile
banking, Payment Gateway, bank branches, service delivery points etc.
7. The service delivery points (approximately 500+) shall be located at various locations across
the city and may be collocated with corner side stores like grocery stores, medical stores etc.
The purpose of providing such touch points is to ensure that all services mentioned as part of
this RFP can be availed by citizens at a walkable distance.
4.10. E-Payment services for Top up

1. Provide e-Payment gateway for transactions made through Credit/Debit/prepaid cards, net
banking, wallet, etc.
2. Provide Payment Gateway for Visa/MasterCard/Amex/RuPay. The Payment Gateway shall be
under the control of the Principal Bank.
3. Provide front-end for entry of smart cards details by bidder and additional authentication
requirements specified by payment gateway service providers.
4.11. Central Clearance House management (CCHM)
Selected Agency should leverage their own systems (hardware and software) or their authorized
partners to maintain Central Clearance house managements (CCHM) as per requirements of the
RFP. RSCL will not pay any additional charges for the maintenance of the exiting systems
leveraged by the Agency.
4.12. Security
1. The System must allow security categories to be assigned to sensitive records.
2. The Administrator should be able to determine the highest security category of any record in
any class or file by means of one simple enquiry
3. The System should support routine, scheduled, review of security categories
22
4. Users only have to log onto the System once to be allowed to access all application modules
for which he/she is authorized to access
5. Security provided at the network, application, and database levels as well as at the client level.
6. Supports standard Internet security including, but not limited to:
a. Digital Certificates
b. Various levels of encryption
c. Secure Socket Layers (SSL)
d. Secure Hypertext Transfer Protocol (HTTPS)
7. Prevent access to sensitive application data by highly privileged users. Super user should not
be able to select, insert, update or delete data from audit.
4.13. Acceptance Testing of Agency System
The objective of testing is to ensure that the entire system performs as per requirements
mentioned in RFP. The testing objectives will have the following dimensions – testing in
technical, functional and operational aspects
 Testing on Technical Aspects

 Testing on Functional Aspects
 Testing on Operational Aspects
The testing will be done at the test environment of RMC or the Selected Agency as mutually
agreed. Selected Agency shall provide requisite technical and operational support for the testing.
Specifically, Selected Agency has to take specific efforts to ensure that all Smart card based
ticketing, e-Payment transactions are done in a safe and secured manner as it is the norm for
Smart card based Fare Collection, e-Payment transactions.
The Selected Agency has to complete one round of System Integrated testing in the testing
environment before taking the solution for Use Acceptance Testing (UAT). Under this testing
the Selected Agency has to simulate all the functions including payment transactions, upload of
payment scrolls, refunds, MIS generation etc. The Methodology of Simulation and Testing has
to be part of the Technical Presentation.
The Selected Agency shall obtain the sign-off from RSCL or its nominees on testing approach
and plan. The Selected Agency shall support testing of the solution based on the approved test
plan and criteria; document the results and shall fix issues observed during testing
23
It is the responsibility of the Selected Agency to ensure that Smart Card based ticketing, e-
Payment services provided by them meet all requirements specified in the RFP. The
responsibility of testing the system is with the Selected Agency.
Selected Agency shall ensure all systems are appropriately tested in the staging area and are
applied on live instance only after such comprehensive testing.
4.14. Documentation
The Selected Agency shall prepare/update the documents including that of card design, SMART
card application design, Integration documentation, System Requirement Specification, Test
Cases & Results, Security Policy document, etc. as per acceptable standards (should not only
limited to).
The Selected Agency shall maintain log of the internal reviews of all the deliverables submitted
to RSCL. The logs shall be submitted to the RSCL or designated agency on request.
The Selected Agency shall obtain the sign-off from RSCL or its nominee for all the documents
submitted for this Project and shall make necessary changes as recommended by RSCL before
submitting the final version of the documents.
All the specifications or documentations created for the project would be owned and used by
RSCL for future rollouts with other transit operators and Selected Agency to ensure
interoperability and mitigate the risk of getting locked with any specific stakeholder.
4.15. Transition Management
Facilitate smooth transition of operations from existing system through proper understanding
of various processes and technical requirements. Deploy application services on test
environment prior to go-live.
Support testing of all the modes of SMART Card based payment/Top up, SMART Card issuance
management, Portal and Mobile app on the testing environment.
4.16. Exit management
24
The exit process would start at the beginning of the last two quarter of fifth year (i.e. from the
date of signing of the contract) in case contract not extended further. At the beginning of the last
quarter of the end of the contract period or in the event of termination of contract, the Selected
Agency is required to provide necessary handholding and transition support, which shall include
but not limited to, conducting detailed walkthrough and demos/drills for Services, project
documentation, etc., and addressing the queries/clarifications of new Agency selected by RSCL.
The incumbent Agency shall prepare proper books of accounts for all transactions and
specifically provide clear details of pending to be fund transfer.
The ownership of the data generated upon usage of the system, at any point of time during the
contract or expiry or termination of the contract, shall vest with RSCL.
During the contract period, the Selected Agency shall ensure that all the documentation
including policies, procedures, etc. are kept up to date and the same are handed over to the RSCL
during the Exit management process.
4.17. Support Management including Help Desk
During the contract period, the Selected Agency shall be completely responsible for defect
free functioning of the Services and the related software applications deployed.
The selected agency shall provide card customer support over Phone, Internet and at bank
branch level for card issuance, renewal, refunds, customer account management and
customer support with payment gateway and authentication services as per RBI
requirements.
The Selected Agency shall resolve any issues that include bug fixing, improvements in
presentation, ad hoc reports with existing data and/or functionality and others at no
additional cost during the support & contract period.
RSCL foresees the need for implementing changes during the contract period (e.g.
generation of new MIS reports, provision to upload additional formats, modify
reconciliation logic, etc.). This may also include incorporation of new modes of payment
(e.g., mobile payment, electronic, etc.) along with the current modes of payment. The
Selected Agency has to provide the above with no additional cost to RSCL.
25
26
Business Hours of the Office
The Offices of the RSCL will be operational from 9:00 AM to 9:00 PM or as notified by
RSCL. Working Days will be those as identified by RSCL. All second Saturdays, Sundays
and public holidays declared by Government of Chhattisgarh shall be non-working days.
In case of emergencies or on need basis, maintenance and support services shall be

provided by the Selected Agency before/after the normal working hours or on non-working
days. No additional costs shall be borne by RSCL for the work performed by the Selected
Agency beyond the business hours of Office.
4.18. Provision, Deployment and supervision of personnel
The Selected Agency would be required to recruit, train and deploy personnel for ensuring
compliance to SLA requirements. The personnel deployed should be appropriately trained
and should be adequate in number to meet all support, technical, functional and other
requirements of the application and processes. The personnel deployed for maintenance
and support should be regular full-time employees of the Agency.
RSCL will require the Selected Agency to meet the implementation timelines as specified
in this RFP. The Project Manager is viewed as Single point of contact (SPOC) for the
engagement, assigned to keep RSCL team abreast of all the developments and also ensure
that the SLA’s are maintained. During the contract duration, the Project Manager shall
inter alia, attend scheduled project meetings, provide directions to the Selected Agency’s
team and ensure timely resolution of faults / disruptions.
RSCL envisages active involvement of the senior resources from the Selected Agency during
the initial transition period until operations are stabilized.
4.19. SLA Monitoring
Service Levels shall be decided in consultation with the successful bidder. Service levels
agreed with the Selected Agency shall be measured by using automated tools. The SLA
reports will be monitored by the RSCL regularly. Selected Agency shall calculate the total
penalties arising due to noncompliance of the SLA on quarterly basis.
The Selected Agency shall develop an SLA Measurement and Monitoring System (SMMS)
for measuring and reporting the SLAs. All SLA measurement and calculation of penalties
shall be automated. Manual intervention for measurement of SLAs shall be after prior
approval of RSCL.
27
The Selected Agency shall ensure that proposed SMMS address all the SLA measurement
requirements and calculation of applicable penalties.
All data related to SLAs shall be made available to RSCL for audit
It would be the responsibility of the Selected Agency to generate appropriate MIS reports
both in hard and soft copies to ensure accurate capturing of the work carried out during
the month
MIS and Reporting
MIS and Reporting - – Indicative reports but not limited to below
Selected Agency should provide the following indicative report:
Payment Scrolls - The payment scroll MIS shall be available through Agency’s website
during custom specified dates, mode of payments and value of payments
 Date of Transaction
 Mode of Transaction
 Value of Transaction
 SMART Card Identity
 Name of Remitter
 Amount
 Account No (Last 4 digits in case of Credit Card / Debit Card/Prepaid card)
 Remarks as entered
MIS of Agency Statement - The Agency’s shall provide MIS view of Bank Statements
without any limitation on the period. The following shall be provided:
 Date of Realization
 Bank Transaction Remarks
 Credit Amount
 Debit Amount
 Merchant details — RMC or other merchants
 ON US/OFF US transaction indicator
28
Unique Reference No. MIS - The Agency shall provide an MIS report providing
necessary details linking collection accounts with unique reference nos. The following shall
be provided:
 Date of Realization
 Amount
 Name of Remitter
 Unique Reference no
 Bank Statement Remarks
Upload of Payment Scrolls - The Agency shall provide the details of Time and Date
of upload of payment scrolls based on duration of days as selected. The MIS report may
be in the following format.
 Scroll Details
 Date and Time of Upload
 Penalties, if applicable
MIS Dashboard - The Bank shall provide MIS dashboard displaying the following:
 Closing Balance in each Account

 Amount eligible to be withdrawn
 Status of Payment Scrolls
4.20. Training
1. Selected Agency should provide training to RMC employees on usage of Smart Card for
accepting payments for various services along with generating Challan through Online Receipt
Management System.
2. The selected agency shall also provide requisite training to new agents that chose to be added
to the service network.
3. Selected Agency should provide training material and user manuals on usage of Smart card
validator, Ticket vending machines, and Ticket Value machines.
4. Selected Agency should provide training on the Agency related MIS report and fund
reconciliation.
4.21. Payment gateway
29
Services for accepting payments through multiple digital channels and payment instruments,
processing them followed by settlement of funds over different networks – MasterCard, Visa,
RuPay /NPCI etc.
a) Enable payments initiated by citizens through the mobile and web applications
regarding –
 Municipal taxes and duties
 Public transport
 Utility payments- water meter bills
 Health Care
 Tourism
 Public convenience
 Challans and penalties
 Parking
 Public entertainment- zoos, lakes, museums and library, etc.
b) The service provider should enable the payments through following payment
channels and instruments:
Online channels:
 Online Payment Gateway for Web Portal
 Mobile Payment Gateway for Mobile Application
Payment instruments
 Debit cards
 Credit cards
 Prepaid cards/ wallets
 Net Banking
 EBPP, View and Pay, Insta Pay
 Others like IVRS, IMPS etc.
 Upcoming instruments like UPI, social media payments, AEPS, BBPS
c) Support Online payments through Web Portal
d) Mobile application payments
30
5. Technical requirement
5.1. Technical Specifications for mPOS / micro ATM

Below is the indicative specifications for mPOS machines to be installed in Buses, auto rickshaw
and Parking and other places wherever, card / wallet enabled payment gets approved by RSC.
Bidders can propose latest industry standard POS machines which are NFC compliant and comply
with all the requirements as per mentioned in the Scope of Work. Warranty and maintenance of
these POS machines would be a responsibility of the selected Agency for the entire project period
of 5 years.
S.No Parameter Minimum Technical Requirements
1 CPU 32 Bit
2 Memory 128 MB flash, 64 Mb DDR
3 Display Min 2.8 Inch LCD Color screen, resolution of 320*240
10 numeric & letter keys, 8 dedicated function keys, 1

4 Keypad
power button
5 Magnetic Card Reader Track 1/2/3 bi-directional
EMV Contact Level 1 &2
6 Certifications EMV Contactless Level 1
PCI 4.0
7 Contactless Card Reader ISO 14443 A/B, ISO 1809 2 (NFC)
8 Biometric Scanner STQC certified
9 Card Slots 2 SAMs +1 SIM
10 Printer Thermal Printer( inbuilt)
11 Battery Li-ion battery
GPRS, GSM 800/900/1800/1900 with SM and USSD

12 Communication
support
31
13 Wi-Fi Supporting 2.4G IEEC 802.11b/g/n or better
14 Peripheral Port Min 1 Micro USB, 1 port+ USB-A
15 Speaker Built in
16 Environment  Working 0℃ to 50℃
5.2. Technical Specifications for NFC Card Reader

a. Contactless Smart Card Reader
b. ISO 14443 compliant Class A and Class B card
c. CCID compliant
d. Pass CE and FCC certification / ROHS compliant
e. Built in Antenna
f. NFC Reader
g. In line with ISO/IEC 18092 (NFC Standard)
h. USB Full Speed, USB Hot Swap Support
5.3. Functional Specifications for Tablet and smartphone based mobile

applications (Android and iOS) for Raipur citizens
i. Register themselves with valid Aadhaar numbers. Mobile app should provide the
aadhaar authentication for creating the user account
j. Upload documents, pictures as required by RMC regarding various services
k. Make payments against desired services with or without login
l. Schedule appointments for doorstep collection of payments and delivery of services
m. Obtain information regarding RMC and track their service requests/transactions
n. Integrate with GIS for providing location based services through the mobile app
o. Raise queries , complaints and get them resolved
p. Provide feedback regarding services
q. Mobile app should have a Responsive UI.
r. Receive alerts and notifications
s. The mobile app shall be bi-lingual (English and Hindi)
t. The Mobile app shall be available on both Google’s Play Store and Apple’s App Store
u. Apps capturing/using personal data of the users shall require to capture user consent
at the time of installation
v. Any content or developer information shared via app store should not impersonate
other entities, brands, or work of other developers. Developers shall ensure that there
32
is no infringement on intellectual property rights of others including copyrights,

patents, trademark and other proprietary rights.
w. Apps submitted for publishing should be complete, thoroughly tested and should have
fully functional UI. The description of app functionalities should match the actual
functionalities.
x. The mobile app developed under the aegis of RSCL shall be supplemented with
relevant web services, to ensure future interoperability.
y. The mobile app developed under the aegis of RSCL shall be subject to regular audits,
in order to ensure compliance to this policy, in addition to all applicable policies at the
state or central level.
5.4. Specifications for Web Portal

a. Register themselves and login into their accounts to make service requests
b. Apply for various services and upload documents as required by RMC regarding these
services.
c. Make payments against desired services with or without login
d. Schedule appointments for doorstep collection of payments and delivery of services
e. Obtain information regarding RMC and track their service requests/transactions
f. Raise queries and complaints, and check their status
g. Provide feedback regarding services
h. Receive alerts and notifications
i. Web Portal should have a responsive interface which can be accessed through a
mobile, tablet or computers, without distortion of the User Interface.
Web Portal should also comply with below mentioned technical specifications:
# Requirement
Technical Solution Architecture Requirements
1. The Web Portal needs to be architected using robust and proven software and hardware
technologies like Service-Oriented Architecture (SOA) and open industry standards.
2. The solution architecture should be built on sound architectural principles enabling fault-
tolerance, high-performance, and scalability both on the software and hardware levels.
Software Architecture Requirements
1. Software architecture must support web services standards including XML, SOAP, UDDI and
WSDL
2. Software architecture must support appropriate load balancing for scalability and performance
3. Software architecture must support flexibility in adding functionalities or applications.
33
4. Software architecture components should utilize the high availability, clustering, and load
balancing features available in the proposed hardware architecture to increase system performance
and scalability features.
5. Software architecture must support trace logging, error notification, issue resolution and exception
handling.
Hardware Architecture Requirements
1. Hardware architecture must provide redundancy and high availability capabilities at the hardware
level; this includes servers, etc.
2. All servers and systems must be configured with no single point of failure.
3. Hardware architecture should be capable of consolidating several applications/workloads in a

number of servers as required.
4. Servers must be placed within proper security infrastructure for the Solution.
5. The technical solution architecture for Portal should be sound and complete with high
performance, redundancy, and scalability.
5.5. Specifications for Septic Tank Clearance

1. System should be able to capture the name, address, region and mobile number of the
applicant.
2. System should allow the applicant to make the online payment.
3. System should generate a unique reference number on submission of the application.
4. Applicant should be able to check the status of his application through the reference
number.
5. Applicant should be able to apply for the refund, using the reference number, in case the
Septic Tank has not been cleared due to some reasons like space not enough for the truck
to go inside, etc.
6. System should show all the applications received in a tabular format and the user should
be able to take the print of it.
7. Internal users should be able to filter out the applications based on the status.
8. Internal users should able to schedule the clearance of Septic Tanks as per the
applications received and an SMS should be delivered to the driver with the contact
details of the applicants.
9. Application should be able to send the SMS alerts to the applicant on the date and time
of clearance of his septic tank.
5.6. Availability
 The proposed solution’s design and deployment architecture should be such that services
for all the utilities mentioned in the RFP are available to users 99.99% of the times without
34
any down-time including daily, monthly or annual closings, system maintenance backups,
and while running maintenance processes.
 Additionally there should be no single point of failure at an application level, and the Lead
bidder should indicate the mitigation processes in place to mitigate single point failures if
any.
 The bidder should also plan for disaster recovery of the system without any additional cost
and must perform DR drill atleast once in 6 months. The same shall be observed by RSCL
and evaluated for performance and compliance during the tenure of contract.
5.7. Scalability and performance

 The solution should be highly scalable to support the current (500 concurrent transactions
from Raipur per day) and projected (20% year on year growth) collection- transactions’
volume across existing and upcoming channels
 The Lead bidder is responsible to arrive at the sizing independently. RSCL will not be
responsible for any assumption made by the Lead bidder with respect to the sizing.
 The Lead bidder is expected to design the solution to support high variance in frequency
as the volumes are not expected to be constant and may be subjected to variances in
customer behaviour due to year end, special offers by RSCL or any other factor.
 The solution proposed by the Lead bidder should be scalable both horizontally as well as
vertically.
5.8. Adaptability
 The system design and development should be such that the system is highly adaptable
and can be modified (code, data, logic, queries etc.), if required, to meet any change in
business needs
 The Lead bidder is expected to indicate whether the proposed solution promotes modular
programming
 The Bidder is expected to define and maintain solution components in a repository with
appropriate taxonomy and links to appropriate design / architecture document
5.9. User creation and administration

 The proposed solution should have the capability for department-wise user creation and
user management- user deletion and suspension, modification, assignment & re-
assignment of roles.
5.10. Reliability and seamless integration
35
 The system design and development should be such that the system’s behaviour under
normal and non-characteristic usage is predictable and repeatable regardless of system
load, invalid input, or availability of resources. The Lead bidder is expected to indicate the
reliability of the proposed solution components.
 The solution should also provide for the utility to seamlessly integrate with other systems
and applications, using a standard set of open APIs and Web Services.
5.11. Testability
 The system design and development should be such that the system can be thoroughly
tested for functionality, reliability, and performance.
 The selected Bidder is expected to provide test documentation that includes a test strategy,
test plan, test scenarios (used for walkthroughs), test cases, and test procedures.
5.12. Transaction security

The proposed solution should be able to carry out operations on data that has masked credentials
for e.g. credit card/debit card numbers and CVV etc.
5.13. Back up
The proposed solution should be able to store data regarding citizen registration details, service
requests, transactions, feedback, complaints and queries, business intelligence reports and
dashboards. Also, carry out daily back up of the data as specified by RSCL.
5.14. Integration of the proposed solution with Raipur City Command and
Control Centre
The proposed solution should be based on open standards and should be capable of integrating
with the future and existing applications of RMC through APIs and Web Services. Raipur Smart
City Limited
36
6. Project Implementation
The Services to be performed by the bidder shall include, but not limited to, the following:
6.1. Submission of Documents
a) The Licensee (Implementation Agency) shall provide to the Authority clear project
implementation plan and end-use requirement document and other documents specified
hereunder within the 4 weeks of LOI.
i. Project implementation Plan shall include details of the project implementation
team and benchmarks and timeline of delivery of equipment, installation of
equipment, integration and setting up of the Central Control Centre (at its own
location).
ii. Solution design and architecture document of complete RCSPS, System
Requirement specification document, Hardware and Software Documentation and
Drawing, user acceptance Test Plan and operational manual of each component of
RCSPS after studying the solution requirement as per relevant provisions of Vol 2
of RFP.
iii. Operational Documents specifying Type of Accounts required and settlement
procedures etc.
b) Each submittal specified in sub clause (a) above, should contain sufficient information to
determine that each component of the project complies with the Technical Specifications
and functional requirements specified in RFP Vol 2.
c) Licensee shall incorporate inputs and suggestions received from Authority or Authority’s
consultant in all submittals. Upon approval by the Authority and after the sign off, the
same shall form an integral part of the Licensee Agreement Approval of any such
submittals shall not absolve the Licensee from its responsibilities and obligations specified
in this Agreement.
6.2. Timeline and Phasing

a) The Authority shall issue an Order in writing, indicating the number of units of Hardware
and Software to be supplied along with the location (Project Site) within the RMC
Premises where these are to be installed.
b) Upon getting the Request Order, the Licensee shall promptly and as soon as possible
within the Lead Time specified in the Request Order, supply, install and implement
specified numbers of hardware and software at stated Project Site and commissioned the
same.
c) The Authority shall specify the Lead Time in Request Order. The Lead Time of Request
Order shall be decided in discussion with the Licensee before the Request Order is placed.
Authority’s decision in this regard shall be final but reasonable time shall be provided to
37
the Licensee. Delay or non-performance will form the basis for application of Liquidated
Damages.
d) Tentative Phasing for implementation for guidance of the Licensee is as follows. It may be
emphasized that this phasing is indicative and not binding.
Total time for implementation of the entire solution would be 6 months. Selected Agency shall
deploy the entire hardware i.e. POS machines, micro ATMs, etc. within the time as specified
below.
T0- Date of Issuance of LOI
Services Tentative Scope/ Tentative Lead Time
Approximate Sizing
Project Kick off and T0+7 days (T0 is the date of
mobilization of team signing of contract)
on the project
Solution Design and T0+15 Days
operating documents
City Civic Commissioning of Micro T0+ 60 days
Centers/ward offices ATMs in 150 City Civic
Centers/ward offices
City Bus Service Installation of POS T0+60 days
machines in 165 city buses.
And Integration with the
ticketing system.
Mobile app and Portal Payment and Informative T1=T0+90 days
(Phase 1) Services (including Study,
deployment, UAT, training
(Refer Annexure 11.2, and Go-Live)
Vol 1)
Mobile app and Portal Location Based Services and T1+90 days
(Phase 2) Integrations (including
Study, deployment, UAT,
(Refer Annexure 11.2, training and Go-Live)
Vol 1)
Smart Card Issuance Minimum 50,000 in first Start of issuance of Smart
year with 20% growth rate Cards should happen within
120 days of signing of
contract.
38
The above is a tentative/approximate schedule as envisaged at this point of time and the
Authority retains the full right to make changes / additions to this or simultaneous
implementation in more than one services. The authority shall discuss the business
requirements in detail upon signing of the contract along with timelines for adherence.
e) Licensee shall provide weekly/fortnightly/Monthly Progress Report as per the direction of
Authority.
39
6.3. Testing and System Audit during Implementation of the Project
a) Upon completing the supply, installation and commissioning of the hardware and
software quantities specified in Request Order, the Licensee shall do a test run for the
entire system, remove any shortcomings and resolve any bugs in hardware, software, and
communication network.
b) After successful test run as specified hereinabove (a), the Licensee shall inform the
Authority/ its authorized representative who shall conduct demonstration / testing of the
System installed to test their conformity to Technical Specifications and functional
requirements as per the Tests specified in the RFP, user acceptance test manual and Good
Industry Practice.
c) The system shall be checked for full functionality in an integrated environment through
test run and tests specified herein (b) above. Upon successful outcome of the Test results,
the Authority/ its authorized representative (i.e. Authority’s consultant or third party
system auditor) shall issue a Project Acceptance Certificate/Go Live Certificate (the
“Project Acceptance Certificate/Go Live Certificate”). No certificate shall be issued against
only delivery, partial installation or incomplete commissioning for quantities specified in
Request Order. Authority shall issue Request Order wise Project Acceptance
Certificate/Go Live Certificate upon successful test outcome as specified in (a) and (b)
hereinabove. The Authority shall issue Project Acceptance / Go Live Certificate separately
for each Request Order.
d) The Authority may appoint an independent consultant or third party auditor capable of
auditing IT systems envisaged as part of Project implementation. The Licensee shall be
required to provide necessary information to the third party auditor/ independent
consultant to facilitate testing and audit of hardware, software and processes related to
RCSPS during the Project Implementation.
40

RFP Vol 2 Smart Payment City Mobile App and Portal

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RFP Vol 2 Smart Payment City Mobile App and Portal

Hochgeladen von

Copyright:

Verfügbare Formate

REQUEST FOR PROPOSAL

Volume 2 – Scope of Work

2. Solution Overview .................................................................12

3. Scope of Work ...................................................................... 14

4. Detailed Requirement Specifications and scope of Common

4.15. Transition Management ............................................................................................... 24

5. Technical requirement ..........................................................31

6. Project Implementation ....................................................... 37

1.1. About Raipur Smart City Limited (RSCL)

1.2. About the project

Advantages of using Raipur City Smart Payment System:

7. Raipur City Smart Cards protect privacy where needed.

2.1. Raipur City Smart Payment System Overview

Figure 1: Conceptual Architecture of Raipur City Smart Payment System

2.2. General description of the Project

Invest, Design, Development, procurement, supply, integration and implementation of Open

S.No. Services to be Covered

1 Municipal Services (taxes, bill, service charges etc.)

3 Utility (water) Payments

5 Location Based services

S. No. Scope of Work

Raipur Smart Card

1 Design, Manufacturing/Sourcing, Supply/Distribution, Marketing of Raipur

Providing transaction clearing, reconciliation of accounts and money settlement

5 Design and implement a Loyalty Management and Promotional Program to encourage

6 Maintenance of Central Clearance house management

7 Deployment & Maintenance of Central Smart Card Host Management

6 Should be based on Open Standards and interoperable solution and integration

 Providing transaction clearing, reconciliation of accounts and money settlement

4. Detailed Requirement Specifications and scope of Common City Payment

4.1. Sourcing, Designing & Personalization of RAIPUR contactless SMART Card

4.2. Supply/ Distribution of RAIPUR contactless SMART Cards

4.3. Marketing/Promotion of RAIPUR contactless SMART Card, Wallet

4.4. Loyalty Program for RAIPUR contactless SMART Card, Wallet

4.5. SMART Card Application and Card Data format

4.6. Automatic Fare Collection (enabled for NFC payments)

4.7. SMART Card Application Interfaces and Integrations

 Rent a Cycle scheme to be implemented in City

4.8. Smart Card Issuance

4.9. Top-Up channels and service delivery points

4.10. E-Payment services for Top up

4.11. Central Clearance House management (CCHM)

4.13. Acceptance Testing of Agency System

 Testing on Technical Aspects

4.15. Transition Management

4.16. Exit management

4.17. Support Management including Help Desk

Business Hours of the Office

In case of emergencies or on need basis, maintenance and support services shall be

4.18. Provision, Deployment and supervision of personnel

4.19. SLA Monitoring

MIS and Reporting

MIS and Reporting - – Indicative reports but not limited to below

Selected Agency should provide the following indicative report:

 Closing Balance in each Account

4.21. Payment gateway

5.1. Technical Specifications for mPOS / micro ATM

S.No Parameter Minimum Technical Requirements

2 Memory 128 MB flash, 64 Mb DDR

3 Display Min 2.8 Inch LCD Color screen, resolution of 320*240

10 numeric & letter keys, 8 dedicated function keys, 1

5 Magnetic Card Reader Track 1/2/3 bi-directional

EMV Contact Level 1 &2

6 Certifications EMV Contactless Level 1