EOI/DMRC/Open Loop Ticketing 01 DELHI METRO RAIL ......2021/01/19 · outlets/parking etc.) in...

EOI/DMRC/Open Loop Ticketing 01

of 60

NOTICE OF INVITATION

DELHI METRO RAIL CORPORATION LIMITED

Our Ref: Date:

TO FROM

________________________________ MANAGING DIRECTOR,

________________________________ Delhi Metro Rail Corporation Ltd..

________________________________ Metro Bhawan,

_________________________________ Barakhamba Road,

_________________________________ Fire Brigade Lane,

_________________________________ New Delhi – 110001


EXPRESSION OF INTEREST FOR IMPLEMENTATION OF EMV AND

RUPAY BASED OPEN LOOP TICKETING IN DMRC INCLUDING

COMPREHENSIVE MAINTENANCE OF AFC SYSTEM OF PHASE I, II,

AND III STATIONS




of 60


Delhi Metro Rail Corporation Ltd., (DMRC) invites Expressions of Interest (EOI) for

implementation of QR Code, EMV enabled Account Bases Ticketing (Master/VISA), and

RUPAY based Open Loop Ticketing in DMRC including Comprehensive Maintenance of AFC

system of Phase I, II and III stations of supplied equipment’s/parts.

This document is an Expression of Interest (EOI) published by Delhi Metro Rail Corporation

Ltd., to solicit and examine the response of the Financial Institutions/Banks along with

firms/companies/entities that are capable of upgrading the AFC System and provide

Comprehensive Onsite Maintenance of supplied equipment’s/parts as per the details

mentioned in this document.

The current document is, therefore, published to explore the response from perspective

bidders. The timelines and the quantity of units mentioned in this document are subject

to change and shall be firmed up while the Technical and Commercial Bids i.e. Request

for Proposal (RFP) are called for by DMRC at a later date.

Some of the conditions are briefly mentioned in this document. These are subject to

change based on the review of the response received.

The Documents describing the Scope of Work and the Terms and Conditions for the EOI

are enclosed with this Notice of Invitation.

EOI Documents comprise of

Notice of Invitation

Instructions to Applicants

The Evaluation and Determination of Responsiveness of EOI and subsequently RFP

submission shall solely be carried out by DMRC.

The EOIs for this Contract will be considered only from those companies, corporation,

partnerships, consortia and joint ventures that pass the initial Eligibility based on

submissions with the EOI. Only such eligible applicants will be allowed to participate in

the next stage of the project, i.e. RFP (Request for proposal).


of 60

KEY DETAILS

Expected Completion period of the work 11.5 years (including years for supply and commissioning of QR Code , EMV (Account Based Ticketing (Master, VISA & Rupay)& Rupay Based System and 5 years of Comprehensive Onsite Maintenance).

EOI documents release date 19/01/2021 For further information on this regard bidders are advised to contact DMRC on 011-23415831

Cost of EOI documents NIL (All documents uploaded on DMRC website – www.delhimetrorail.com

Last date of Seeking clarification 01/02/2021 (Queries from applicants after due date shall not be acknowledged)

Pre-EOI Meeting 02/02/2021

Last date of issuing DMRC’s response to queries

05/02/2021

Date and time of submission of EOIs 11/02/2021 up to 15:00 Hrs

Date and time of opening of EOIs 12/02/2021 at 15:30 Hrs

Authority and place for submission of EOIs and seeking clarifications

General Manager (Telecom) 6th Floor, ‘B’ Wing, Metro Bhawan, Barakhamba Road, New Delhi-110001

Please note carefully the requirements for submitting EOIs, and the date and time for submittal.

Late or delayed EOIs will not be accepted.

http://www.delhimetrorail.com/


of 60


EXPRESSION OF INTEREST FOR IMPLEMENTATION OF EMV AND

RUPAY BASED OPEN LOOP TICKETING IN DMRC INCLUDING

COMPREHENSIVE MAINTENANCE OF AFC SYSTEM OF PHASE I, II,

AND III STATIONS


of 60

Table of Contents

No. Item Page No.

A. Introduction

A1. Definitions

A2. General Description of Work

A3 Eligible Applicants

B. EOI Documents

B1. Content of EOI Documents

B2. Clarification of EOI Documents

B3. Amendment of EOI Documents

C. Preparation of EOI Documents

C1 EOI Bid Submission Documents

C2 Pre EOI Meeting

D Submission of Bids

E. EOI Opening and Evaluation

F Annexure I EOI Proforma

G. Annexure II Form of Certificate

H. Annexure III Bid Data Sheet (BDS)

I. Appendix I No. of AFC Equipments and technology

J Appendix II Design Parameters

K Appendix III Brief scope of work


of 60

INSTRUCTION TO APPLICANTS

A. INTRODUCTION

A1. Introduction and Definition

(i) Delhi Metro Rail Corporation (DMRC) Limited invites proposals from the bidders

for implementation of QR Code, EMV enabled Account Bases Ticketing

(Master/VISA),and Rupay based Open Loop Ticketing (National Common Mobility

Card) extendable to feeder buses, parking services and other services in Delhi and

Comprehensive Onsite Maintenance of Automatic Fare Collection System for Ph-

I, Ph-II & Ph-III of Delhi Metro of supplied equipment’s/parts.

(ii) In this request for Expression of Interest, the words and expressions shall have the

meanings assigned to them, except where the context requires otherwise. Words

indicating persons or parties include corporations and other entities except where

the context requires otherwise.

(iii) Throughout these Bidding Documents:

a. The term “in writing” means communicated in written form and delivered

against receipt;

b. Except where the context requires otherwise, words indicating the singular

also include the plural and words indicating the plural also include the singular;

and

c. “Applicant/Lessor” means the JV/SPV/Consortium submitting the EOI.

d. “Commencement Date” means the date of Letter of Acceptance.

e. “Contract Period” means the total contract duration of 10 years from

commencement date during which the Consortium shall be responsible to

execute the Project.

f. “Day” means calendar day.

g. “Engineer” means any person nominated or appointed from time to time by

DMRC to act as the Engineer for purposes of the contract and notified as such

in writing to the Applicant.

h. “Fare Box Revenue” means the revenue generated by DMRC through fare

collection from its metro.

i. “FI” means “Financial Institution or Acquirer Bank” that can be a Bank in India

which is approved by Reserve Bank of India.

j. “Lessee” means DELHI METRO RAIL CORPORATION LIMITED (DMRC), its

legal successors and assignees.

k. “Lessor” means the applicant whose proposal has been finally accepted by the Lessee and the legal successors in title to such person, but not (except with the consent of the Lessee) any assignee of such person.


of 60

l. “Operator” means the lessee.

m. “Project” means

a. Upgrade the Automated Fare Collection System of Delhi Metro Rail

Corporation Limited to enable the QR Code, EMV (Account Bases

Ticketing) and Rupay based open loop ticketing following the NCMC

standard model as specified by MoHUA for interoperability with other

operators by use of non-proprietary standards so that the interface is

scalable to other networks (transit operator/retail outlets/parking etc.)

in Delhi/NCR; and

b. Execute the Comprehensive maintenance of supplied

equipment’s/parts including the Back Office.

n. “Royalty” means premium paid by service provider to DMRC to get rights to

issue EMV and Rupay Cards to commuters at metro stations and facilitate

existing DMRC AFC system for new services. NCMC/EMV cards issued by Other

bank cards also accepted at entry and exit. Service provider will keep this

royalty amount and need not pay to DMRC.

o. “RFP” means Request for Proposal.

A2. General Description of Work

A2.1 General Information:

(i) The Delhi Metro is a metro system service in Delhi and its satellite cities of

Faridabad, Gurgaon, Noida and Ghaziabad in National Capital Region in India.

Delhi Metro Rail Corporation Limited (DMRC) with a total length of 314

kilometers serving 245 stations (excluding 6 on Airport Express Line).

(ii) In FY 19-20, the metro had an average daily ridership of 2.86 million passengers,

and served 100 crore riders in total during the year.

(iii) DMRC has implemented AFC for Phase I, II and III system. Phase I, II and III consists

of 9 lines with 245 stations:

S.No. Line No. Section No. of Stations

1. Line-1 Saheed Sthal (New Bus Adda)-Rithala 29

2. Line-2 Samaypur Badli-Huda City Centre 37

3. Line-3 Noida Electronic City-Dwarka Sec.21 49

4. Line-4 Laxmi Nagar-Vaishali 7

5. Line-5 Inderlok –Brigadier Hoshiyar Singh 23

6. Line-6 Kashmiri Gate- Raja Nahar singh 34

7 Line-7 Majlis Park to Shiv Vihar 38

8 Line-8 Botanical Garden to Janak Puri West 25

9 Line-9 Dwarka to Najafgarh 3


of 60

(iv) The details of stations, AFC Equipment’s and existing technology are placed at

Appendix-I.

A2.2 Up-gradation of AFC System

(i) In order to upgrade the ticketing technology, DMRC envisages to upgrade the

existing Automatic Fare Collection System to enable the QR Code, EMV (Account

Bases Ticketing) and Rupay based open loop ticketing following the NCMC

standard model as specified by MoHUA (Ministry of Housing and Urban Affairs)

for interoperability with other operators by use of non-proprietary standards so

that the interface is scalable to other networks (transit operator/retail

outlets/parking etc.) in Delhi/NCR.

(ii) Ministry of Housing and Urban Affairs has laid down the Smart NCMC standard

model specifications. Following the NCMC standard model, the common Mobility

card will enable seamless travel by different metros and other transport systems

across the country besides retail shopping and purchases.

(iii) The existing AFC technology and infrastructure (Hardware and software including

Back office and external interfaces) needs to be updated accordingly.

(iv) The proposed Business Model shall have a Consortium of a Financial Institution, a

AFC Solution provider and/or a third member. The Financial Institution and AFC

Solution provider is the mandatory member of the consortium.

(v) The Financial Institution shall be responsible for Issuance of EMV/Rupay Dual

Interface smart cards and other fare media and related logistics, including

marketing, customer contact center support on card transactions and Fraud

Management Setup of online card top-up/renewal, customer account

management and customer support with payment gateway and authentication

services as per RBI requirements, settle Fare Revenues with DMRC and other

Public Transit system revenues with respective operators.

(vi) The AFC Solution Provider shall be responsible for upgrading the Station level

Equipments to support EMV and RuPay NCMC, QR and NFC Based ticketing,

Integration of clearing house and smart Card host system of FI, integration of

DMRC mobile application with AFC system and provide the Comprehensive Onsite

Maintenance of supplied equipment’s/parts including the Back Office. Details

scope of work at Appendix-III

(vii) The Key Dates for delivery and commissioning will be detailed out in the RFP

Document.


of 60

A2.3 Functional and Performance Based specifications

(i) The Applicant shall be responsible for operation of both existing and new AFC

system.

(ii) The Performance requirements of each system shall be met in accordance to

Design Parameters placed at Appendix-II.

A2.4 Contract Period

(i) The Contract Period will be 11.5 Years (including 5 years of operation and

maintenance) from Commencement date.

(ii) The Contractor will be responsible to meet the specified performance criteria in

the RFP Document

A2.5 Applicant Liability

(i) The Consortium/JV would be liable for all services as per the scope of work to be

detailed out in the RFP document.

(ii) The AFC Solution provider would be jointly liable for all scope of services

pertaining to the Supply, Installation, Commissioning, Up-gradation and

Maintenance of supplied equipment’s/parts of AFC system at all locations and

related services.

A2.6 DMRC Liability

(i) The account ownership for the float of DMRC CSC amount shall remain with DMRC

A2.7 Operating Expenses

(i) The complete cost of Up-gradation, Operation and Maintenance of supplied AFC

Equipment’s/parts shall be borne by the JV/Consortium.

(ii) The personnel required for staffing the Customer Care Counters/Excess Fare

Offices at DMRC stations shall be provided by DMRC and shall be adequately

trained by the JV/Consortium on the required ticketing operations.

A2.8 Comprehensive Maintenance and Up-gradation of AFC Equipment’s

(i) The maintenance and upkeep of the supplied AFC Equipment’s/ parts and

facilities, over the entire contract period shall be responsibility of the

JV/Consortium.

(ii) It is expected that the Contractor shall assess the condition of the AFC Equipments

at the time of submission of RFP.


of 60

A2.9 Performance Criteria

(i) The Contractor would be responsible for meeting the laid down Performance

Criteria, which shall be detailed in RFP.

(ii) The Contractor shall carry out Integrated Testing and Commissioning of EMV and

Rupay based ticketing, QR and NFC functionality on the system in coordination

with the Engineer. He shall also carry out all interface tests with the FI Host.

(iii) The Scope of Work for the JV/Consortium shall be detailed in the RFP document.

A2.10 Handback and/or termination

There shall be provision for the handback of AFC equipments/Parts or for the early

termination of the lease, or both. For example, in the case of lease containing an early

termination provision, the value to the lessee of the early termination provision will be

reflected in the leas terms.

The details shall be provided in RFP document.

A3 Eligible Applicants

(i) EOIs for this Contract will be considered only from those consortia and joint

ventures that pass the initial Eligibility criteria based on submissions with the EOI.

Only such eligible applicants will be allowed to participate in the next stage of the

project, i.e. RFP.

(ii) Each Applicant (each member of joint venture or consortium) or any associate is

required to confirm and declare with his EOI that no agent, middleman or any

intermediary has been, or will be, engaged to provide any services, or any other

item or work related to the award and performance of this Contract. They will

have to further confirm and declare in the submittal that no agency commission

or any payment which may be construed as an agency commission has been, or

will be paid and that the quoted prices will not include any such amount. If the

Employer subsequently finds to the contrary, the Employer reserves the right to

declare the Applicant as non compliant, and declare any Contract if already

awarded to the Applicant to be null and void. Canvassing or offer of an advantage

or any other inducement by any person with a view to influencing acceptance of

an EOI will be an offence under laws of India. Such action will result in the rejection

of the EOI in addition to other punitive measures.

(iii) There are no restrictions on the country of origin of equipment, materials, and

services to be provided under the Contract. However, all the up-gradation of

equipment, materials and services shall be to the satisfaction of the Employer’s

Engineer. The information regarding all the Equipment, materials and services


of 60

included in the Applicant’s Proposals and incorporated into the Contract

Document shall not, in any event, be construed as a submission to the Engineer

under the Contract.

A3.1 Initial Eligibility Criteria

The applicants will be evaluated on the eligibility criteria provided below table. When

responding to the eligibility criteria, applicants should demonstrate their capabilities, by

providing material based on their experience, past performance, their personnel,

equipment and financial resources.

S.No. Criteria for all members Yes No.

1. Has the Applicant ( any member) abandoned any work in the last ten (10) years?

2. Has the Applicant (any member) suffered bankruptcy/ insolvency in the last ten (10) years?

3. Has the Applicant (any member) been debarred by the Government of India/any State Government in India/Central or State Government undertaking as on the due date of submission of bid? (Bidder to furnish a specific undertaking to this effect).

4. Has the Applicant certified that no agent/middleman has been or will be engaged or any agency commission been or will be paid?

Eligibility Criteria for (Financial Institution or Acquirer Bank)

S.No. Criteria Documentary Evidence Yes/No.

5. The Acquirer Bank should be a Bank in India which is approved by Reserve Bank of India.

Certified copy of RBI

6. The Acquirer Bank should have the details of GST Registration and PAN

Copies of relevant certificate.


of 60

7. Acquirer Bank should have the experience of handling channels of payment gateways (web, mobile etc.), processing NEFT/RTGS, IMPS,ATMs, IVR, SMS etc.

Self-certification or copy of relevant and valid PO/WO/LOA/Contract Agreement issued till the date of bid submission, along with completion certificates issued by the client or company secretary/CFO/Auditor of the Acquirer Bank member, covering the requirement.

8. Deleted

9. Applicant should have the experience of developing and commissioning EMV based smart card system

-DO -

10. Acquirer Bank should have the experience of executing projects with loyalty program design or management of retail customer base

Self-certification or copy of relevant and valid PO / WO/LOA/Contract Agreement issued till the date of bid submission, along with completion certificates issued by the client or company secretary/CFO/Auditor of the FI member, covering the requirements.

11. Acquirer Bank should have the experience in providing corporate banking services:

-DO -


of 60

Eligibility Criteria for AFC Solution Provider

12. AFC Solution Provider should constitute under Companies Act of the country, which it belongs to. In case of Foreign Company, incorporation documents other than English language should be accompanied by the notarized translation to English language only.

Certified copy of incorporation.

13. AFC Solution Provider as part of consortium should have experience of working on EMV contactless cards.

Copy of relevant and valid PO/WO/LOA/Contract Agreement issued till the date of Bid Submission along with the completion certificates issued by the client or Company Secretary/CFO/Auditor of the Consortium member covering the requirements. Self-certification from Consortium’s member/CFO/Auditor is also applicable.

14. AFC provider should carry out one of the following projects in the last 7 years in a Metro/LRT/Mono Rail System:- a) Must have completed ONE work of

Contactless Smart Card based AFC System of minimum value equal to INR 100 crore at 31.12.2020 price level or One work of contactless smart card based AFC System for minimum 20 stations OR

b) Must have completed Two works of similar nature of Contactless Smart Card Based AFC System of

Copy of relevant and valid PO/WO/LOA/Contract Agreement issued till the date of Bid Submission along with the completion certificates issued by the client or Company Secretary/CFO/Auditor of the Consortium member covering the requirements. Self-certification from Consortium’s


of 60

each costing minimum INR 62.5 crore at 31.12.2020 price level OR Each of these 2 work of Contactless Smart Card based AFC system for minimum 12 stations OR

c) Must have completed THREE works of similar nature of Contactless smart card based AFC system of each costing minimum INR 50Crores at 31.12.2020 price level OR each of three work at minimum 10 stations.

member/CFO/Auditor is also applicable.

15 Average Annual financial turnover during the last 5 financial years (as applicable in the country or origin), should be at least INR 100 Crore.

Audited balance sheet or CA certificate to be provided.

Note:

1. A “YES” answer to any question 1,2,3 and 4 will disqualify the Applicant.

2. A “NO” answer to any question 5 to 15 will disqualify the Applicant.

3. In the Consortium, each individual member must qualify individually in the ‘Eligibility of

Applicants – Question at Serial No.1,2,3 and 4.

4. Sr.No.5 -11 is applicable for Acquirer Bank only and Sr.No.12-15 are applicable for AFC

Provider only.

5. Change in the composition of a Consortium may be permitted by DMRC prior to submission

of RFP Documents subject to meeting the qualifying requirements of EOI, DMRC, at the

specific written request of the qualified consortium/JV, may agree for change of any

partner(s) at post EOI stage except that change of the Technology partner (member of the

consortium/JV responsible for providing AFC Solution and provided as options for the role

of AFC Provider) would not be permissible.

A3.2 One EOI per Applicant

Each Applicant shall submit only one EOI. If an Applicant submits an EOI in his own name

and at the same time participates and submits an EOI as a member of a consortium/joint

venture, both applicants will be disqualified. However, a propulsion system supplier can

participate either as a member of any JV/Consortium bidding for this EOI or as a sub

vendor to other Applicants.


of 60

A3.3 Applicant Conditions

Prime bidder, as part of its technical proposal, is allowed to propose up to 3 (three)

entities as options for the role of AFC provider in the consortium subject to following

conditions:

(i) Each of entities proposed as option for the role of AFC Provider consortium

member shall meet the requirements of RFP and bid submission requirement

including relevant bidding forms.

(ii) Prime Bidder is required to include all relevant details of each entity option as per

the bidding forms that will be detailed out in the RFP.

A4 Payment to the Employer/Contractor

(i) The payment terms shall be detailed in the RFP Document and shall be based on

the Fare Box Revenue and Non Fare Box Revenue Collection, through Open Loop

Ticketing.

(ii) The Percentage sharing of Fare Box Revenue to be paid by the Employer and the

percentage of Non-fare Box Revenue share to be paid by the Consortium shall be

fixed and detailed out in the RFP Document.

(iii) The Contractor shall also pay Yearly Royalty to DMRC which shall be detailed in

RFP Document.

A5 Site Visits

(i) The Applicant is advised to visit existing and proposed DMRC Stations and examine

the Equipment’s and facilities available, site and surroundings and obtain for

himself on his own responsibility all information that may be necessary for

preparing the EOI for the proposed works.

(ii) The costs of visiting the Site shall be borne by the Applicant. It shall be deemed

that the Applicant has undertaken a visit to the site of Works and is aware of the

site conditions prior to the submission of the EOI.

(iii) The Applicant and any of his personnel will be granted permission by the Employer

to enter upon his premises and lands for the purpose of such inspection but only

upon the express condition that the Applicant, and his personnel, will release and

indemnify the DMRC and his personnel from and against all liability in respect

thereof and will be responsible for death or personal injury, loss of or damage to

property and any other loss, damage, costs and expenses incurred as a result of

the inspection.


of 60

A6 Indigenization

i. For Indigenization (Preference to Make in India), the Applicants have to comply with

the Public Procurement Order, 2017 issued by Ministry of Commerce and Industry,

Department of Industrial Policy and updated Order No. P-45021/2/2017-PP(BE-II) dated

04.06.2020 issued by DPIIT.

ii. However, the minimum Local Content shall ordinarily be 50 %. The ‘Local Content’

means the amount of value added in India, which shall unless otherwise prescribed

by the Nodal Ministry, be the total value of item procured (excluding net domestic

indirect taxes) minus the value of imported content in the item (including all custom

duties ) as a proportion of the total value, in percent.

B. EOI Documents

B1 Contents of EOI Documents

(i) The EOI Documents, as listed below, have been prepared for the purpose of

inviting EOIs for implementation of EMV and RuPay based Open Loop Ticketing &

Comprehensive Onsite Maintenance of supplied equipment’s/parts for Ph-I, II and

III stations of DMRC and as more particularly described in these documents:

a. Notice of Invitation to EOI (NIE).

b. Instruction to Applicants (ITA).

c. Bid Data Sheet (BDS) (Refer Annexure-III).

(ii) The Applicant is expected to examine carefully the contents of all the above

documents. Failure to comply with the requirements of EOI Submittal will be at

the Applicant’s own risk. EOIs that are not substantially responsive to the

requirements of the EOI Documents will be rejected.

(iii) The Applicant shall not make or cause to be made any alteration, erasure or

obliteration to the text of the EOI Documents.

B2 Clarification of EOI Documents

B2.1 The Applicant shall check the ages of all documents against page numbers given in indexes

and summaries and, in the event of discovery of any discrepany, the Applicant shall inform

in writing to the office of General Manager/ Telecom forthwith for clarification.

B2.2 Should the Applicant for any reason whatsoever, be in doubt about the meaning of

anything contained in the Invitation to EOI or EOI Documents, the Applicant shall seek


of 60

clarification from the Engineer, not later than the “last date of seeking clarification” given

in the Bid Data Sheet.

B2.3 DMRC will respond in writing, to any request for clarification received in writing from

Applicants prior to deadline for such clarification or modification in the Bid Data Sheet.

B2.4 The response to queries of the prospective applicants shall be uploaded on the DMRC

Website, without identifying the source of clarifications.

B2.5 No further clarification questions will be accepted after the “last date of seeking

clarifications”.

B2.6 Except for any such written clarification by the office of GM/Tele which is expressly stated

to be by way of an addendum to the documents referred to in paragraph B1 above and/or

for any other document issued by DMRC which is similarly described, no written or verbal

communication representation or explanation by any employee of the DMRC or the

Engineer shall be taken to bind.

B3 Amendment of EOI Documents

Applicants are advised that further instructions to Applicants and addenda to the EOI

Documents may be issued during the EOI period. The provisions in any such addenda shall

take priority over the Invitation to EOI and EOI Documents previously issued. Applicants

shall confirm receipt of such documents and list them in the EOI submittal.

C. PREPARATION OF EOI

C1 EOI Bid Submission Documents

C1.1 EOI Pro-Forma

The Applicant shall submit the specified EOI Proforma, duly filled in.

The Applicant shall provide EOI index (Table of Contents) in his EOI. The EOI Index should

indicate where within the EOI, the Applicant has included his responses/comments to the

EOI requirements and conditions elaborated in these EOI documents. (Refer EOI Pro-

forma in Annexure-I)

EOIs and all accompanying documents shall be in English. In case any accompanying

printed literature is in other languages, it shall be accompanied by an English translation

duly certified by a registered translator. The English version shall prevail in matters of

interpretation.


of 60

C1.2 Applicant Details

State the structure of the applicant’s organization, i.e. Joint Venture or Consortium.

C1.3 Leader of JV/Consortium

C1.4 MOU for JV/Consortium: The Applicant shall submit the following additional information

to meet the initial eligibility criteria for eligibility.

a. A Memorandum of Understanding/Consortium Agreement, comprising of all the

members, shall be provided.

b. Lead member of the consortium or Joint Venture to be in-charge (Leader), and this

authorization shall be covered in the Power of Attorney signed by the legally

authorized signatories of all members of consortium or joint venture. Any member of

consortium or joint venture be the Prime and lead Member of the Consortium;

c. Details of the intended percentage participation given by each member shall be

provide and reconfirmed and expanded with complete details of the proposed

division of responsibilities and corporation relationships among the individual

members.

d. The lead partner, FI and the AFC Service provider must have minimum 26% individual

participation. Partners have less than 26% participation will be termed as non-

substantial partners which mean their financial soundness and work experience shall

not be considered for Evaluation.

e. The partner in charge (Leader) shall be authorized to incur liabilities, receive payments (if provided for in MOU/Consortium Agreement) and receive instructions for and on behalf of any or all partners of the Joint Venture/Consortium.

f. All partners of the joint venture/consortium shall be jointly and severally responsible for the execution of the Contract in accordance with the Contract terms.

g. The Applicant shall submit with his EOI full details of his ownership and control or, if the Applicant is a partnership, joint venture or consortium, full details of ownership and control of each member thereof.

h. Indian Applicants, or Indian members of partnership, joint venture or consortium shall submit, a certified copy of the last 3 years (including the latest Financial Year) income tax return, duly acknowledged by Income Tax department. In case the Indian member of a partnership, joint venture or consortium is a wholly owned 100% subsidiary of their foreign partner in the said joint venture or consortium and this Indian company has been formed less than 3 years ago, the certified copy of the latest Financial Year income tax return (applicable only if company was formed more than a year ago), duly acknowledged by Income Tax department shall be submitted.


of 60

C1.5 Power of Attorney for each member and for leader, as applicable

The Applicants to qualify for award of Contract shall submit a written power of attorney bearing specimen signatures of the authorized signatories of the EOI to commit each member of the partnership, consortium or joint venture. In case of Foreign Partners, Power of Attorney(s) and Board Resolution/Commercial Register confirming authority on the persons issuing the Power of Attorney for such actions, shall be submitted duly notarized by the notary public of country of origin and should be stamped by Embassy/High Commission. Applicants from Member Countries of Hague convention may submit all these documents with “Apostille” stamp instead of Embassy.

C1.6 Documents supporting Initial Eligibility Criteria

Documents in support of checklist provided in Initial Eligibility Criteria, Clauses A3 and A3.1 of this ITA.

C1.7 Financing structure

In order to have a sustainable and technically & financially sound proposal. DMRC shall propose a suitable financial structure for the Applicant in detailed RFP Document.

C1.8 Guarantees and Warranties

The Applicant shall submit full details of the identity of the proposed parties who would respectively provide or issue:

(a) The Performance Security

(b) The Revenue Security

(c) Parent company undertakings

(d) Parent company Guarantees

If the Applicant comprises a consortium or joint venture, a parent company of each member of participant will be required to execute the Undertakings and Guarantees referred to in sub-paragraphs (c) and (d) above.

C1.9 EOI documents (including amendments) duly signed by each member. A form of certificate confirming careful examination of all the contents of EOI documents including EOI addenda and signing of all pages of the Applicant’s proposal shall be furnished along with the EOI proposal. It should be submitted by each constituent member in case of Joint Venture or Consortium, as per Annexure-II.

C2 Pre-EOI Meeting

C2.1 The prospective Applicants or their official representatives are invited to attend a pre-EOI meeting, which will be held on the date, time and location indicated in Bid Data Sheet.

C2.2 The purpose of the meeting will be to clarify issues and to answer questions on any matter that may be raised with respect to this EOI at that stage.

C2.3 The Applicants are requested to submit any questions in writing or by email, to reach DMRC before or during the meeting.


of 60

C2.4 Minutes of the meeting, including the text of the questions raised and the responses given, will be transmitted without delay to by mail to all such Applicants, who either attend the Pre-EOI meeting or intimate in writing that they would like to receive the clarifications. Any modification of the EOI documents listed in paragraph B1 which may become necessary as a result of the pre-EOI meeting shall be made by the DMRC exclusively through the issue of an Addendum pursuant to paragraph B3 and not through the minutes of the pre-EOI meeting.

C2.5 Non attendance at the Pre-EOI meeting will not be a cause for disqualification of an Applicant.

D. Submission of EOIs

D1 Submission Address and Date

All documents corresponding to “Initial Eligibility” shall be annexed in a separate folder, which shall be a part of the EOI. All the envelopes shall be addressed to the DMRC at the following address:

To,

The Managing Director,

Delhi Metro Rail Corporation,

Metro Bhawan, Barakhamba Road,

New Delhi-110001

EOIs must be received at the address specified above, not later than the date and time noted in Bid Data Sheet.

D2 Sealing and Marking of EOI

D2.1 The Applicant shall seal the Original and each copy of the EOI in separate envelopes, duly marking the envelopes as “Original”, “copy 1” and “Copy 2”.

D2.2 If the envelope is not sealed and marked as above DMRC will assume no responsibility for the misplacement or premature opening of the EOI.

D3 Late or Delayed EOIs

D3.1 EOIs must be received by the GM/Telecom, at the address specified above, not later than the date and time noted in Bid Data Sheet. If the due date is declared to be a public holiday due to unforeseen reasons, the EOIs shall be submitted and opened at the same time on the next working day. DMRC may, at its discretion, extend the deadline for submission of EOIs by issuing an amendment in accordance with paragraph B3, in which case all rights and obligations of DMRC and the Applicant previously subject to the original deadline will thereafter be subject to the deadline as extended.

D3.2 Any EOI received by the Engineer after the deadline for submission of EOIs stipulated above will be returned unopened to the Applicant.


of 60

E. EOI Opening and Evaluation

E1 EOI Opening

The EOI will be opened at time and date as specified in Bid Data Sheet in the Office of DMRC, Metro Bhawan, New Delhi. The Applicants are allowed to be present at the time of opening.

DMRC shall prepare a record of the opening that shall include, as a minimum: the name of the Applicant. The Applicants’ representatives who are present shall be requested to sign the record. The omission of an Applicant’s signature on the record shall not invalidate the contents and effect of the record. A copy of the record shall be distributed to all Applicants.

E2 Clarification of EOIs from Applicants

To assist in the examination, evaluation and comparison of EOIs, DMRC may, at his discretion, ask any Applicant for clarification of his EOI. The request for clarification and the response shall be in writing or by facsimile, but no change in the substance of the EOI shall be sought, offered or permitted. DMRC may call for a meeting with the Applicants in this regard. The minutes of the meeting, if held, with any applicant shall be recorded and acknowledgement obtained from the concerned applicant.

E3 Determination of Responsiveness

E3.1 DMRC will determine whether each EOI:

(i) Has been properly signed; and

(ii) Meets the Initial Eligibility Criteria – DMRC will evaluate the eligibility and acceptability based on initial Eligibility criteria indicated in these documents.

A ‘NO’ answer to any of the above item will disqualify the EOI.

E4 Intimation of Evaluation of EOI

E4.1 RFP document shall be issued to only such applicants, who qualify based on E3.1 above.

E4.2 Applicants may note that pursuant to their qualification in the ‘Initial Eligibility Criteria’. In case the Applicant (applies to each individual member in case of a Joint Venture/Consortium) is debarred/blacklisted by Government of India/State Government/Government Undertaking after the due date of submission of EOI but before the evaluation of RFP document to be issued separately. They shall inform the same to DMRC in writing within 5 working days of issue of such debarment, failing which it will be considered that the applicant has willfully concealed the information and the applicant shall be solely responsible for all implications that may arise in accordance with the conditions of this EOI. Any such debarment will result in disqualification of the Applicant and the RFP document of such Applicant shall be returned unopened.


of 60

F. ANNEXURE-I

EOI Pro-Forma

PRO-FORMA LETTER OF APPLICATION (on Firm’s Letter Head)

The Managing Director, Delhi Metro Rail Corporation Ltd., Metro Bhawan, Barakhamba Road, New Delhi-110001 India

( Applicant to provide date and reference) APPLICATION FOR INITIAL ELIGIBILITY

Dear Sir, We hereby make application for Initial Eligibility as an applicant for the implementation of EMV Based Open Loop Ticketing & Maintenance of supplied equipment’s/parts for Ph-I, II and II stations of DMRC. In support of the application we submit herewith one original and two copies of the required documents. This application is submitted on behalf of a joint venture/consortium (applicant to delete as appropriate) comprising ____________________________________( Applicant to state the names of each member) _________________________and of which___________( Applicant to insert name of leading member of joint venture/consortium) has agreed to act as leader. Each member has prepared a statement of participation in relation to this application and these are contained in the next Section herewith.

Yours faithfully,

________________(Signature) Name of Signatory___________________ Capacity of signatory_________________

Name and address of the leader of the Consortium


of 60

PRO-FORMA LETTER OF PARTICIPATION FROM EACH MEMBER OF A JOINT VENTURE/CONSORTIUM

(On Letter Head of each Firm)

The Managing Director, Delhi Metro Rail Corporation Ltd., Metro Bhawan, Barakhamba Road, New Delhi-110001 India

( Applicant to provide date and reference) APPLICATION FOR INITIAL ELIGIBILITY

Dear Sir, We wish to confirm that our company/firm (delete as appropriate) has formed/intends (delete as appropriate) to form a Joint Venture/Consortium with _____________________( Member o insert names of all other members of the group) for purposes associated with this EOI. (Members who are not the lead member of the Joint Venture/Consortium should add the following paragraph). The Joint Venture/Consortium is led by (member to insert name of lead member) whom we hereby authorize to act on our behalf for the purposes of applying for initial Eligibility. (The lead member of the Joint Venture/Consortium should add the following paragraph) In this joint Venture/Consortium we act as leader and, for the purposes of applying for Initial Eligibility, represent the group. In the event of our Joint Venture/Consortium being invited to tender for this EOI, we agree to be jointly (with other members of our Joint Venture/Consortium) and severally liable to the Delhi Mero Rail Corporation Ltd. (DMRC), its successors and assigns for all obligations, l duties and responsibilities arising from or imposed by any contract subsequently entered into between the DMRC and our Joint Venture/Consortium.

Yours faithfully,

________________(Signature) (Name of Signatory)___________________ (Capacity of signatory)_________________


of 60

G. ANNEXURE-II

FORM OF CERTIFICATE

FORM OF CERTIFICATE CONFIRMING CAREFUL EXAMINATION OF ALL THE CONTENTS OF EOI DOCUMENTS AND SIGNING OF ALL PAGES OF

APPLICANT’S PROPOSAL This is to certify that we M/s. _____________________________(Name of the company) have

carefully examined all the contents of the EOI documents including EOI Addenda (if any) and all

the pages of our proposal have been signed and stamped (by each constituent member in case

of a Joint Venture or Consortium).

SIGNATURE OF APPLICANT

*To be submitted by each constituent member.


of 60

H. ANNEXURE-III

Bid Data Sheet (BDS)

1. The name of the Project. EOI/DMRC/Open Loop Ticketing 01

2. Employer is Delhi Metro Rail Corporation (DMRC)

3. The name of the EOI is The identification number of the EOI is

Expressions of Interest for Implementation of EMV and Rupay based Open Loop Ticketing in DMRC including Comprehensive maintenance of supplied equipment’s/parts of Ph.I, II and III stations. EOI/DMRC/Open Loop Ticketing 01

4. Expected Completion period of the work

11.5 years

5. EOI Documents release date

6. Cost of EOI Documents NIL (all documents uploaded on DMRC website- www.delhimetrorail.com)

7. For clarification purposes only, the Purchaser’s address is

Attention: GM/Telecom 6th Floor, B Wing, Metro Bhawan, Barakhamba Road, New Delhi-110001

8. Last date for seeking clarification 01/02/2021

9. Pre-EOI Meeting 02/02/2021

10. Last date of issuing DMRC’s response to queries.

05/02/2021

11. The language of the Bid is English

12. Representation by an Agent Not allowed

13. In addition to the original Bid, the number of copies is

Two

14. The written confirmation of Authorization to sign on behalf of the Bidder shall consist of

Power of Attorney for each member and for leader, as applicable.

15. The identification of this bidding process is

Superscription on each package of the bid 1. EOI Pro-forma:

“EOI Pro-Forma: EOI/DMRC/Open Loop Ticketing 01

2. Initial Eligibility Criteria (Original + 2 copies)

3. OUTER PACKAGE: 3.1 ORIGINAL comprising of S.No.1 & 2

shall be sealed in an outer envelope

http://www.delhimetrorail.com/


of 60

and marked as “BID: EOI/DMRC/Open Loop Ticketing 01 – ORIGINAL”.

3.2 Copies of the initial Eligibility criteria shall be sealed in outer envelopes and market as “BID: EOI/DMRC/Open Loop Ticketing 01-Copy 1” and “BID: EOI/DMRC/Open Loop Ticketing 01-copy 2”.

16. For bid submission purposes only, the Purchaser’s address is:

Attention: GM/Telecom 6th Floor, B Wing, Metro Bhawan, Barakhamba Road, New Delhi-110001

17. The deadline for bid submission is: Date:11/02/2021 Time: up to 15:00 Hrs

18. Date and time for opening of EOIs Date:12.02.2021 Time: at 15:30 Hrs


of 60

I. APPENDIX –II Number of AFC Equipments and Technology Equipment specification as installed in existing DMRC AFC System:- List of Stations (Samsung Make):-

RED LINE (SAMSUNG)

1. Shahadara Elevated

2. Seelampur Elevated

3. Welcome Elevated

4. Shastri Park Elevated

YELLOW LINE (Samsung)

1. Sultanpur Elevated

2. Ghitorni Elevated

3. ArjanGarh Elevated

4. Guru Dronacharya Elevated

5. HUDA City Centre Elevated

BLUE LINE (SAMSUNG)

1. Pragati Maidan Elevated

2. Barakhambha Road Underground

3. RK Ashram Elevated

4. Jhandewalan Elevated

5. Rajendra Place Elevated

6. Laxmi Nagar Elevated

7. Nirman Vihar Elevated

8. Karkardooma Elevated

GREEN LINE (SAMSUNG)

1. Inderlok Elevated

2. Ashok Park Main Elevated

3. Satguru Ram Singh Marg Elevated

4. Punjab Bagh East Elevated

5. Shivaji Park Elevated

6. Madipur Elevated

7. Paschim Vihar East Elevated

8. Paschim Vihar West Elevated

9. Peera Garhi Elevated

10. Udyog Nagar Elevated


of 60

11. Surajmal Stadium Elevated

12. Nangloi Elevated

13. Nangloi Railway Station Elevated

14. Rajdhani Park Elevated

15. Mundka Elevated

VIOLETE LINE (SAMSUNG)

1. Central Secretariat Underground

2. Khan Market Underground

3. Jawaharlal Nehru Stadium Underground

4. Jangpura Underground

5. Lajpat Nagar Elevated

6. Moolchand Elevated

7. Kailash Colony Elevated

8. Nehru Place Elevated

9. Kalkaji Mandir Elevated

10. Govind Puri Elevated

11. Okhla Elevated

12. Jasola Apollo Elevated

13. Sarita Vihar Elevated

14. Mohan Estate Elevated

15. Tughlakabad Elevated

16. Badarpur Elevated

Equipment Specifications:

S.No.

Equipment Type Technology Make

1. Gate CST (Type A & C) Mifare Ultralight (64 bytes) Samsung

Sony Felica RCS 890 (512 bytes)

CSC (Type A & C) Mifare Desfire (4 KB)

Sony Felica RCS 833 (1 KB)

2. TOM CST (Type A & C) Mifare Ultralight (64 bytes) Samsung





of 60

List of Stations (Thales Make-1):-

RED LINE (THALES)

1. Kashmere Gate Elevated

2. Tis Hazari Elevated

3. Pul Bangash Elevated

4. Pratap Nagar Elevated

5. Shastri Nagar Elevated

6. Inder Lok Elevated

7. Kanhaiya Nagar Elevated

8. Keshav Puram Elevated

9. Netaji Subash Place Elevated

10. Kohat Enclave Elevated

11. Pitam Pura Elevated

12. Rohini East Elevated

13. Rohini West Elevated

14. Rithala Elevated

YELLOW LINE (THALES)

1. Samaypur Badli Elevated

2. Rohini Sector 18 Elevated

3. Haiderpur Elevated

4. Jahangirpuri Elevated

5. Adarsh Nagar Elevated

6. Azadpur Elevated

7. Model Town Elevated

8. GTB Nagar Underground

9. Vishwavidyalaya Underground

10. Vidhan Sabha Underground

11. Civil Lines Underground

12. Kashmere Gate Underground

13. Chandhni Chowk Underground

14. Chawri Bazar Underground

15. New Delhi Underground

16. Rajiv Chowk Underground

17. Patel Chowk Underground

18. Central Secretariat Underground

19. Udyog Bhawan Underground

20. Lok Kalyan Marg Underground

21. Jorbagh Underground


of 60

22. INA Underground

23. AIIMS Underground

24. Green Park Underground

25. Hauz Khas Underground

26. Malviya Nagar Underground

27. Saket Underground

28. Qutab Minar Elevated

29. Chhattarpur Elevated

30. Sikandarpur Elevated

31. MG Road Elevated

32. IFFCO Chowk Elevated

BLUE LINE (THALES)

1. Noida City Centre Elevated

2. Golf Course Elevated

3. Botanical Garden Elevated

4. Noida Sect 18 Elevated



7. New Ashok Nagar Elevated

8. Mayur Vihar Ext Elevated

9. Mayur Vihar-I Elevated

10. Akshardham Elevated

11. Yamuna Bank Elevated

12. Mandi House Underground

13. Barakhamba Road Underground

14. Rajiv Chowk Underground

15. Karol Bagh Elevated

16. Patel Nagar Elevated

17. Shadipur Elevated

18. Kirti Nagar Elevated

19. Moti Nagar Elevated

20. Ramesh Nagar Elevated

21. Rajouri Garden Elevated

22. Tagore Garden Elevated

23. Subash Nagar Elevated

24. Tilak Nagar Elevated

25. Janak Puri East Elevated

26. Janak Puri West Elevated

27. Uttam Nagar East Elevated

28. Uttam Nagar West Elevated

29. Nawada Elevated


of 60

30. Dwaraka Mor Elevated

31. Dwarka Elevated

32. Dwarka Sector - 14 Elevated








40. Vaishali Elevated

41. Kaushambi Elevated

42. Anand Vihar Elevated

43. Preet Vihar Elevated

VIOLET LINE (THALES)

1. ITO Underground

2. Mandi House Underground

3. Janpath Underground

4. Sarai Elevated

5. NHPC Chowk Elevated

6. Mewla Maharajpur Elevated

7. Sector 28 Elevated

8. Badkhal Mor Elevated

9. Faridabad Old Elevated

10. Neelam Chowk Ajronda Elevated

11. Bata Chowk Elevated

12. Escorts Mujesar Elevated


S.No.


1. Gate CST (Type A & C) Mifare Ultralight (64 bytes) Thales V3





of 60

List of Stations (Thales Make-2):-

BLUE LINE (THALES)

1. Dwarka Elevated

2. Nangli Elevated

3. Saraspur Elevated

GREEN LINE (THALES)

1. Mundka Industrial Area (MIA) Elevated

2. Ghevra Metro Station Elevated

3. Tikri Kalan Elevated

4. Tikri Border Elevated

5. Modern Industrial Estate (MIE) Elevated

6. Bus Stand Elevated

7. Bahadurgarh City Park Elevated

VIOLLET LINE (THALES)

1. Kashmere Gate Underground

2. Lal Qila Underground

3. Jama Masjid Underground

4. Delhi Gate Underground

5. NCB Colony Elevated

6. Ballabhgarh Elevated

PINK LINE (THALES)

1. Mukundpur At Grade

2. Majilis Park Elevated

3. Azadpur Underground

4. Shalimar Bagh Underground

5. Netaji Subhash Place Underground

6. Shakurpur Elevated

7. Punjabi Bagh West Elevated

8. ESI Hospital Elevated

9. Rajouri Garden Elevated

10. Maya Puri Elevated

11. Naraina Vihar Underground

12. Delhi Cantt Elevated

13. South Campus Elevated

14. Moti Bagh Elevated

15. Bhikaji Cama Place Underground

16. Sarojini Nagar Underground


of 60

17. INA Underground

18. South Extension Underground

19. Lajpat Nagar Underground

20. Vinobapuri Underground

21. Ashram Underground

22 Hazrat Nizamuddin Underground

23 Mayur Vihar – 1 Elevated

24 Mayur Vihar Pocket 1 Elevated

25 Trilok Puri Elevated

26 Vinod Nagar East Elevated

27 Vinod Nagar Elevated

28 IP Extension Elevated

29 Anand Vihar Elevated

30 Karkarduma Elevated

31 Krishna Nagar Elevated

32 East Azad Nagar Elevated

33 Welcome Elevated

34 Jaffrabad Elevated

35 Maujpur Elevated

36 Gokulpuri Elevated

37 Johri Enclave Elevated

38 Shiv Vihar Elevated

MEGENTA LINE (THALES)

1. Janakpuri West Underground

2. Dabri Mor Underground

3. Dashrath Puri Underground

4. Palam Underground

5. Sadar Bazaar Elevated

6. Indira Gandhi International Airport T-1D Underground

7. Shankar Vihar Elevated

8. Vasant Vihar Underground

9. Munirka Underground

10. R.K.Puram Underground

11. IIT Underground

12. Hauz Khas Underground

13. Panchsheel Underground

14. Chirag Delhi Underground

15. Greater Kailash –II Underground

16. Nehru Enclave Underground

17. Kalkaji Mandir Underground

18. Okhla Phase-III Elevated


of 60

19. Sukhdev Vihar Elevated

20. Jamia Milia Islamia Elevated

21. Okhla Vihar Elevated

22 Jasola Vihar Elevated

23 Kalindi Kunj Elevated

24 Okhla Bird Sanctuary Elevated

25 Botanical Garden Elevated


S.No.


1. Gate CST (Type A & NFC) Mifare Ultralight (64 bytes)/My-D Move (Infineon). Type A Token compliant to ISO 14443.

Recto/Verso (Thales V4)

CSC (Type A & NFC) Mifare Desfire (minimum 4 KB)

EV1 ISO/IEC 14443 and ISO 18092 or equivalent

2. TOM CST (Type A & NFC) Mifare Ultralight (64 bytes)/My-D Move (Infineon). Type A Token compliant to ISO 14443.

Recto/Verso (Thales V4)



List of Stations (Indra Make):-

RED LINE (INDRA)

1. Sahid Nagar Elevated

2. Raj Bagh Elevated

3. Rajendra Nagar Elevated

4. Shyam Park Elevated

5. Mohan Nagar Elevated

6. Arthala Elevated

7. Hindon River Elevated

8. New Bus Adda Elevated


of 60

BLUE LINE (INDRA)

1. Noida34 Elevated

2. Noida 52 Elevated




6. Electronic City Elevated


S.No. Equipment Type Technology Make


G46 (INDRA)




G46 (INDRA)




1. Gate CST (Type A & C) Mifare Ultralight (64 bytes) Line 06:

Central Secretariat to Badarpur

Line 05:

Inderlok to Mundka

Line 02:

Qutub Minar to Huda City Center




2. TOM CST (Type A & C) Mifare Ultralight (64 bytes)





of 60


1. Gate CST (Type A ) Mifare Ultralight (64 bytes)

Line 02:

Samaypur Badli to Haiderpur

Line 06: ITO to Janpath and Sarai to Escort Mujesar




2. TOM CST (Type A & C) Mifare Ultralight (64 bytes)






Line 03 ext:

Dwarka to Saraspur

Line 05: MIA to Bahadurgarh City park

Line 06: NCB-Ballabhgarh Heritage Line:

Kashmere Gate to Delhi Gate

Line 07:

Mukundpur







of 60



Line 01:

Rajbagh to New Bus Adda

Line 03:

Noida 34 to Electronic City






J. APPENDIX-II

Function/Performance Mobile based NFC ticketing

QR code based Ticketing

Contactless EMV Smart Card

Minimum Operating Lifetime with Data Retention in Memory

05 years As per expiry for one time usage

5 years

Recyclable No No No

Recharge-Purchase Tickets or Increase ‘Pay As You Go’

Yes N/A Yes

Auto Top-up ‘Add Value’ Via Arrangement with Debit or Credit Card Provider

Yes N/A Yes – details to be agreed with Employer

Maximum time to complete a transaction

500 m Sec 600 m Sec 500m Sec


of 60

K. APPENDIX-III

Scope of Work

Upgradation of DMRC Line 1 to Line 9 AFC system for implementation of Open Loop EMV NCMC Card Based for Rupay, QR Code Ticketing and Account Based Ticketing

Delhi Metro currently operates metro rail services in Delhi and NCR region with more than 250 working station Equipment supplied by three vendor). Closed loop tokens & smart cards along are currently used as ticket fare media by commuters to travel on this line. This document explains the detailed Scope of Work that DMRC is planning for implementation: -

1. Upgradation Supply & Service for Implementation of Open Loop EMV NCMC Card Based for RuPay/Maser/Visa, QR Code and Account base ticketing at equipment’s (Gate/Customer Care and POS details at Annexure A)

2. Upgradation & Commissioning of current Gate and new POST/CUC and station computer Central Computer (Hardware & Software)

Abbreviations:-

POST-Point of Sale Terminal CC-Customer Care NCMC –National Common Mobility Card ABT - Account Based Ticketing FI- Financial Institutions i.e. Payment Switch Bank –Acquire Bank for Transaction Upgradation of DMRC Line 1 to Line 9 AFC system for implementation of Open Loop EMV NCMC Card Based for Rupay, QR Code Ticketing and Account Based Ticketing

Brief Scope of Work for Implementation of Open Loop EMV NCMC Card Based for Rupay, QR Code Ticketing and Account Based Ticketing that includes but not limited to following: -

Supply and Services : -

1. Upgradation/supply of DMRC Line 1 to Line 9 AFC system certified Readers and passenger information display for AFC equipment’s / server that supports close loop card, Open Loop EMV NCMC for Card based Rupay, Master & Visa & Account based Ticketing (Master & Visa)

2. Supply of all required network accessories like Network switches, cables etc required for working for Open Loop EMV NCMC Card Based for Rupay/Master/Visa,QR Code ,QR Code ticketing and Account based Ticketing Implementation as well existing close loop card.

4. Upgradation of station server for working of Open Loop EMV NCMC Card Based for Rupay/Master/Visa,QR Code ,QR Code ticketing and Account based Ticketing as well as close loop card Implementation.


of 60

5. Supply of new Central Computer system (CC) for working of Open Loop EMV NCMC Card Based for Rupay/Master/Visa,QR Code ,QR Code ticketing and Account based Ticketing as well as close loop card Implementation. 6. Every Line have one central computer for handling of transaction and equipment parameters and all reports related to Line and supervision of line. 7. One Bank Office for all for settlement between all Line Central computer as well as all external operator and banks. Back Office also able to handle all interface of QR-Code Ticketing ,NCMC ,Account Based Ticketing (brief description in Annexure A) 6. Complete Software Designing, Development & Upgrade for supporting Open Loop EMV NCMC Card Based for Rupay/Master/Visa , QR Code Ticketing and Account based Ticketing as per their guidelines ( NCMC guideline define by MOUOA) and also compatible with existing close loop card.

7. Complete Software Designing. Development & Up gradation of existing AFC Back office means station computer and other central computer of all vendors.

8. Complete setup of Servers (Station Computer as well as Central Computer).

9. Complete Software Designing, Development& Upgrade of existing Network as per banking standards for all settlement like report to bank as well as other service provider like Bus ( DTC, DIMTS, Feeder ), Parking.

10. Complete Interface with FI and Bank switches.

11. All required Certifications to be taken for commercial operations for working of Open Loop EMV NCMC Card Based for Rupay/Master/Visa,QR Code ,QR Code ticketing and Account based Ticketing. 12. All Hardware and software modification required in current AFC equipment (Gate, POST, Station Computer, Central Computer).

13. Complete Interface with current AFC system at all levels like AFC Gate, Network, Database, AFC Back office.

14 Complete interface development at all level means in future AFC of other supplier can be integrated with the new system means standard interface shall be provided for the integration for future AFC provided.

15. Interface document shall be provide for the interface for new AFC provider for seamlessly working of Open Loop EMV NCMC Card Based for Rupay/Master/Visa,QR Code ,QR Code ticketing and Account based Ticketing as well as Banking switch. 15. Installation & Commissioning of complete system.

16. End to end testing of complete system with all relevant parties e.g. FI, Bank, DMRC, NPCI,Master,Visa, PCI DSS and other required for commercial operations.


of 60

17. Account based ticketing will be implemented in such a manner that whenever DMRC want to enable/disable this functionality same can be done immediately

General Technical Specifications:-

1. Automatic fare Collection system shall, as far as possible, operate using open non-propriety, industry standards and shall be highly reliable, scalable, secure and customer friendly facility. 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 and maintained by organizations such as EMVco, PCIDSS, IEC, ISO, CEN, EN, NPCI and ISI etc. as applicable.

2. The intention is to make the systems interoperable with other Public Transport Organizations in Delhi like DTC DIMTS and, RMGL, the AFC system shall integrate and synchronize seamlessly with a collection of multiple systems, like the inter-site transmission network, master clock system, power supply system, main earthling facilities, cable routing facilities, fault monitoring system.

3. Contractor shall employ system for Delhi Metro to able to perform day to day monitoring of the ticketing operations and shall provision for the MIS reporting and would be responsible for generation of MIS report, Bank settlement report as per the requirements of the Delhi Metro e same was discuss during Design Phase.

4. Contractor shall do all interface which are required for final AFC System which able to handle QR Code /Open Loop Card (Rupay/Master/Visa)/Existing DMRC Card/Account Based Ticketing.

5. Contractor shall verify by analysis, testing and system demonstrations, as required the operability, reliability availability maintainability and safety requirements.

6. It also includes supply, installation and commissioning of all the networking equipment’s and cables for station LAN central computer system LAN and for the connectivity with the communication backbone (Station to station connectivity) provided by Telecom (DMRC).

7. Delhi Metro seeks an Solution with following points: a. Adherence to international and national standards and practices for the industry.

(Published and maintained by organizations such as EMC, ISO, CEN, and ISI etc.) b. Interoperability – To ensure that Delhi Metro Airport Line will be able to participate in

an open loop Smart Card market including other transit systems. 8. The proposed solution (hardware and software) will ensure:


of 60

a. Contractor- independent delivery of modules/ equipment as far as possible. Use of Standard Commercial off the shelf products and software, encouraging use of non-proprietary items.

b. Proven hardware platform. 9. The system needs to be flexible and configurable designed to allow future adaptation in

a multi operator environment and government policies. 10. The attainment of the reliability availability maintainability and safety requirements of

the system will be verified by analysis testing and system demonstrations as required in the specifications.

11. The scope of supply shall include all necessary hardware/ equipment, software, accessories, materials, documentation and facilities necessary to meet all requirements of the AFC system for the required stations.

12. Issuance infrastructure- this shall comprise of setting up the issuance infrastructure at the POST/CUC which will be used to issue the pre-personalized EMV NCMC and DMRC Smart Card.

13. Fare media Acceptance Infrastructure - This shall comprise of EMV contactless readers to read process ticketing media (Open Loop Card, Existing DMRC Smart Card, QR Code and Account Based Ticketing) . This infrastructure shall be made available at the Automatic Gates POST, CUC etc.

14. Local Area Network (LAN) – This shall comprise of networking of the systems including but not limited to ticked vending machines automated gates ticket office machines workstations and all network equipment’s necessary for operations. The WAN connectivity shall be provided by Delhi Metro Airport line means stations to stations fibre connectivity.

15. Station computer – Station computer shall be the station level AFC management application responsible for monitoring station level equipment generating station level reports sending control command from AFC BackOffice system.

16. Complete station level networking works and network equipment like switches routers including Ethernet / OFC cable ties conduits legends terminations other accessories power supply distribution panels power/ control cable and all fixing and termination accessories. However, the control router / switch shall be equipped to support all stations.

17. Interface to the central back-office system based AFC system and station AFC equipment and infrastructure.

18. Scope of software supply shall as a minimum but not restricted to include all software required for the AFC system including. - a. Development /Customization of AFC application software. b. Application programming interface (API) software. c. Simulator software. d. Antivirus software. e. Network security etc.


of 60

19. Contractor shall supply to Delhi Metro all software solution relevant to all of the AFC equipment for staff to carry out successful ticketing operations.

20. Contractor shall provide detailed interface specification for following interfaces (API’s, DLL’s documentation) a. Smart card to smart card reader b. QR code to QR code reader c. Smart card reader, smart card, QR code reader to AFC equipment. d. AFC equipment (Gate, POST) to Central computer /Back office e. Smart card Host to Central Back Office f. Various external interfaces (Mobile Application, Web site if any)

21. The operation features of the system shall be fully parameterized to provide flexibility for modification of operational parameters/ conditions. Such changes shall be done at the central AFC Back office system and downloaded to the equipment to be effective at a future date. There should be provision to transfer EOD parameter (business rule as well other parameter required for running the system) to one station / few stations / all stations from central AFC Back office system. An acknowledgement from the equipment should be sent to central AFC Back office system automatically for the acceptance and validation of new EOD parameters (Business rule as well other parameter required for running the system)

22. Blacklist shall be sent automatically and frequency of sending blacklist parameter should be configurable and a report of card is required which give the information about all blacklisted card which come in the system after doing blacklisting.

23. Power & Control Cable

To be of suitable specification. Contractor to propose as per requirement. Cables shall be ISI mark or similar international rating. Fire retardant, Low smoke, low halogen for elevated stations and for underground stations as Zero halogen. The halogen content shall not be more than 0.5% for underground cables. Cables shall comply with latest version of British, IEC, ASTM, ITU standard. Proven in Underground Environment, for underground stations. Data Cable: All data cable to be utilized in underground stations to be low smoke zero Halogen (<0.5% Halogen)

Detailed scope of work for implementation of Open Loop EMV NCMC card based RuPay card, QR code and Account based ticketing that includes but not limited to following:

1. Acceptance of Open loop EMC NCMC card based Rupay card having store value & QR code and Account based ticketing at Gate and Ticket Office Machine :-

i. Design, Develop & Upgrade Kernel & Firmware of Gate Reader’s for acceptance of Open Loop EMV NCMC card based RuPay card, QR code and Account based ticketing


of 60

ii. Design Develop & Upgrade interface between gate EMV reader and already installed AFC Backup office for data storage, equipment configuration and other existing features.

iii. Design, Develop & upgrade interface between gate EMV reader and FI /Bank switch for acquiring of transaction happen on AFC gate.

iv. All required certifications to be taken from Rupay (NPCI)/Master/Visa for operation. Cost of these certificates to be taken care by tenderer.

2. Issuance & Top up of Open Loop EMV NCMC card based RuPay card, QR code and Account based ticketing and existing close loop card. a. Develop & Upgrade Ticket office Machine (TOM) software already installed for close loop card Issuance, Top up and Penalty of Store Value . b. Develop & Upgrade interface between POST and already installed AFC Backup office for data Storage, equipment configurations and other existing features. d. Develop & Upgrade interface between POS and FI/Bank switch for acquiring of transactions happen on Ticket Office Machine. e. Develop & Upgrade interface between Ticket Office Machine for managing all functions of the cards using the POST interface and user access control modules. f. Commuters will be able to pay in:- 1. Cash 2. Scanning of QR Code 3. Debit, Credit & Prepaid Cards 4. Wallet 5. Online payment 5. Any other Payment mode All payment mode data need to be captured & validated from AFC for issuance & top up of EMV cards. 3. AFC Back-office System:- a. Contractor will provide the end to end back-office AFC software platform to manage the

open loop system as well as close loop card , QR code Account based ticketing . b. Develop & Upgrade AFC Back-office as per Card based NCMC ,EMV, Account based ticketing

specification & requirements. c. Develop & Upgrade AFC Back-office (Database, Backend, Functions, etc) as per Delhi Metro

Business Rules. d. Develop & Upgrade interface between AFC Back-office & FI/Bank switch as per Card based

Rupay Specification & requirements. e. Back-office System of AFC will provide functionalities for:- Implementing Delhi Metro business rules in line with EMV standards Transaction

Management system, Reconciliation and settlements management Information System (MIS)

g. A brief description of scope also at Annexure A. 4. Network Connectivity & Server Set up:


of 60

a. Contractor will design, configure & install the network communication architecture to enable card based Rupay, Account Based Ticketing and QR Ticketing in such a way so that existing card also work. b. Contractor will collaborate with Delhi Metro to finalize the server set up design to house the back office AFC system. c. Upgrade all hardware, network and hosting setup for Card based Rupay in line with the payment industry regulations and guideline right from station equipment to AFC Back-office & FI/Bank Switch/System. 5. Interfacing with FI and Bank:- a. Develop and implement interfaces to integrate with FI and Bank acquiring switch system and settlement as defined by FI. b. Integration with F1 and Bank in all respect in line with EMV based Card , QR Code as well Account based ticketing.

6. Operations Support-

a. Field support- Contractor has to provide field support engineers to support any issues faced in the open loop AFC set up and QR Code.

b. Monitoring Support- Contractor has to provide monitoring of AFC system components from a Delhi Metro Centralised dashboard.

c. Bugs Resolution- Contractor has to evolve any type of bug faced during operations.

7. Other/Common Requirement:- a. Develop & Upgrade AFC software in line with the banking specifications that shall be

shared for enabling open loop in line with industry standards and regulatory guidelines. b. Ensure all required certifications from station level AFC equipment till the Central OCC. c. PCI DSS compliance or certification to be taken at all levels till the Central OCC. d. Mobile based NFC acceptance is also enabled at the gates using Host Card Emulation

(HCE), Secure Element etc. e. Delhi Metro Rail business rule implementation. f. DLP for 2 years that includes Hardware & Software Maintenance & Support services. g. Maintenance that includes Hardware & Software Maintenance & Support services for 5

years post DLP.

Part 2 – Supply & Commissioning of current Gate and new POST/CUC and station computer Central Computer (Hardware & Software) Brief Scope of work for Re-engineering of Current GATE ECU (Hardware & Software) includes but not limited to following:- Supply:- Supply of all required accessories like Network switches, cables, etc required for current Gate and new POST/CUC, Station Computer & central computer.


of 60

Services:-

1. All activities (hardware & software) required to be done for Current Gate/POST ,Station computer and central computer.

2. Finally one software for all type of Media (EMV/Existing Card/QR code/Account Based Ticketing).

Detailed scope of work for current GATE/POST/CUC (Hardware & Software) includes but not limited to following:-

1. Contractor will develop new firmware & software for current AFC Gate/POST/CUC 2. Contractor will develop a software for station computer for each station and Line wise

central computer means every line shall have one central computer and one super central computer that make all settlement corresponding connected line wise Central Computer so revenue can be settle among all lines as well as other service like BUS ,Parking etc as define in Appendix B .

3. Contractor will undertake the following approach for this project:- a. For Hardware interfaces to the gate/POS/CUC same as it is now. b. For Software development Gate/Post/CUC software for controlling all sub

components functionally. Gate/ POST/CUC software for controlling all Gate sub components required for debugging for maintenance, controlling of sensors, many more.

5. Gate/ POST/CUC software to be integrated with Station Computer & Backend Server application for viewing alarms, status, etc.

6. Contractor will first demonstrate the functionalities of the Gate/ POST/CUC in Delhi Metro Software development Centre. Post successful POC & this project to be undertaken for actual deployment on live Stations equipments.

7. Gate/ POST/CUC Software need to be developed as per AFC system requirement of Delhi Metro .

8. Station Computer and Central Computer Software need to be developed as per AFC

system requirement and full fill all requirement of Business Rule means all Gate and Fare mode management. Central Computer should have a capability to handle 512 station fare matrix.

9. All MMI shall be developed at station computer as well Central Computer to manage all operation and maintainer requirement of system.

10. DLP for 2 years that includes Hardware & Software Maintenance & Support services which is supplied in this contract.

11. Maintenance that includes Hardware & Software Maintenance & Support services for 5 years post DLP.


of 60

Proposed Flow of Open Loop Card Transactions Rupay Card based and Account Based Ticketing :-

Contractor has to submit the complete design for approval for complete process flow. Proposed transaction flow for Rupay Card based Open Loop Card and Account Based Ticketing Transactions along with existing card transaction and QR code includes but not limited to following:-

1. Entry Gate:-

a. The Upgraded AFC equipment will accept the open loop card transactions means all type of transaction of for Rupay Card based Open Loop Card, QR Code, Account Based Ticketing and existing DMRC smart Card.

b. The AFC equipment would validate the Bank Card based on Delhi Metro Business rules (minimum. balance on the card, blacklist status from the card, etc) as per EMV Guidelines & NCMC Rupay rules.

c. Once the card is validated, the flap on the gate opens allowing the user to enter the station.

d. The AFC equipment then sends encrypted card data to the Payment switch through a secure channel.

e. The reader would also send the tokenized (non- secured) transaction information to the AFC system as DMRC close loop card and QR data.

2. Exit Gate: a. Similarly, at the exit gate, When the passenger taps the card, the terminal would perform

the following high-level tasks: Read the Card entry information, calculate the fare, and update the balance. Blacklist check based on feedback from the Payment switch, if required.

b. Once the transaction is complete, the gate flap opens, and the passenger is allowed to exit.

3. Terminal - Acquirer Switch / Host

a. Open loop readers on the gate will send financial transaction advice request to switch host in required ISO 8583 format.

b. Open loop readers will receive financial transaction advice response from switch host.

4. Acquirer – Rupay – Issuer Bank a. Acquirer switch sends the required formatted ISO 8583 message to Rupay (NPCI). b. Payment scheme forwards the transaction advice request to respective Issuer bank. c. Issuer bank updates host global balance. d. Issuer bank responds to advice request to Payment Scheme. e. Payment scheme sends the response to acquirer switch. f. The Acquirer switch would then send the transaction information back through the Delhi

Metro Airport Line network down to all the gate readers on a secure channel.


of 60

5. All Transaction of Gate/POST/CUC shall go to Centre computer via station computer as well as Card transaction will be send to CCHS for card settlement.

Proposed Interface between AFC System & FI for all cases:-

Contractor has to submit the complete design for approval for complete process flow. Proposed interface between AFC & FI for Open Loop Card Transactions Rupay Card based /Account Based ticketing system includes but not limited to following:-

1. AFC Back-office will interface with FI Acquirer system for the following:- a. For authorization of sales & usage transactions. b. Clearance and settlements of transactions at EOD operations c. To download Card parameters, Acquirer Terminal configuration parameters, Certificates,

Keys, Card range parameters and Issuer Card parameters d. EMV prepaid card balance synchronization with Issuers through Acquirer / Payment

Scheme e. Acquirer connection integration parameters as defined by the acquirer FI f. Should have secure connections with Acquiring system as defined by the Acquirer on the

handshake and transaction data. g. FI Acquirer will clear & settle the revenue with Delhi Airport Line directly.

2. Bank Interface: - The banking interfaces will be required for enabling top-up channels like POST/CUC, Existing POS and others. The banking interfaces will also be used for customer service.

3. AFC Back-office will request Acquirer for clearing and settlement in End of Day Job. 4. Acquirer Bank:- The backend system will interface with acquirer through NMC Transaction

Settlement System for following:- a. Clearing & Settlement b. Deferred Authorization c. Balance query on card d. EMV Parameter e. Card Business Rule f. Risk Management

5. Issuer Bank: The backend system will interface with issuer through FI Acquiring system a. Card Balance Enquiry, Reload & Issuance


of 60

Annexure B BILL of Quantity

Sr, No

Item Unit Amount Quantity Total Amount

1. Project Management ( Design Document submission ,Technical solution of system)

1 1

2 Interface with existing System (Interface document with existing AFC equipments

1 1

3 Interface with CCHS ( interface document for transaction)

1 1

4. Interface with Bank (All interface document / format for interface with bank has to submit)

1 1

5 Interface with payment switch (All transaction format or documents required for Switch payment)

1 1

6 Upgradation of AFC Gate all part that make full requirement as per sope of work (Hardware/Software design document for Gate interface to make Gate compatible with new display for Open Loop Card ,QR Code and Account Based Ticketing)

1 2887

7 Upgradation Of POST/CUC as per scope of work ( Hardware /Software Design document for NCMC/EMV/QR Code/Account Based Ticketing)

1 1184

8 Supply of Station Computer as per scope of work ( Hardware /Software Design document)

1 246

9 Supply of Central Computer as per scope of work (Hardware /Software Design document)

1 9

10 Back Office 1 1

11 5 Years AMC 1

Total time for DLP and 5 years AMC will be 7 years and same can be extended in future for 2 years

. DLP will be completed with the completion of DLP period of OCC. AMC of all parts supplied in

the scope remaining with DMRC.

DMRC will give MDR per transaction on NCMC card to Bank as per NPCI circular same will be

updated as per NPCI/Govt. Of India/RBI guideline


of 60

Performance Requirements for Central Computer/Back Office system

(i). Availability 99.9%

(ii). CC able to handle transactions per day 5 million

(iii). Transactions in peak hour 1 million

(iv). Fare table configuration 512 stations

(v). System spare capacity at the time of taking over Over 50%

(vi). Connect a maximum of station computers (configurable, not to be limited by any parameter)

125

(vii). Handle a maximum of station equipments 3000

(viii). Total CC system rebuild (reinstallation of AFC application and database restore from tape) This does

not include the time required to install OS and other

system programme

within 4 Hr.

(ix). On-line data 30 day

(x). Off-line data 6 months

(xi). Data on tape 36 months

(xii). Daily database and system backup on backup server and tape

1 Hr

(xiii). Data restore Tape to backup server 1 Hr

(xiv). Backup server to system 1 Hr

(xv). Transaction update interval at CC

(xvi). AR update interval

5 min.

15 min.

(xvii). Time for completion of all end of business day tasks. within 4 Hr.


of 60

Introduction

General requirements for a back-office Central System (CS) that supports a legacy Card-based Automated Fare Collection (AFC) solution as well as requirements to support future National Common Mobility Card (NCMC) ,Pay-As-You-Go (PAYG) ticketing (Mobile Ticketing),QR Ticketing and Account-based AFC. While requirements for some core components are common across the above solutions: Some of points cover in the back office solutions are as below: 1. Media Types – Card-based solutions rely solely on “closed” contactless smartcards/smart

tokens (long-life and short-use/single journey) with a proprietary card format that stores the customers travel instruments such as purses/products; account-based solutions can use a variety of ISO-14443 compliant media types including contactless smartcards, open-payment bank cards, NFC-enabled phones, etc. (“Tokens”) which do not store any travel instruments or other data but simply presents a unique ID that identifies a user with a back-office account where travel instruments are stored.

2. Online versus Offline – Card-based solutions are designed so that devices can operate in an offline mode (i.e. no requirement for continuous or “online” communications to the Central System). In account-based solutions, devices are required to be online in order to perform realtime or semi-realtime authorization against the card account. (Note, performance requirements for authorization of Tokens in account-based systems is a balance between transaction processing speed at the AFC device versus financial risk and there are several mechanisms available to mitigate these risks).

3. Fare Processing – In card-based solutions, fare processing and business rules are performed by the devices whereas in account-based solutions, they are performed within the back-office. Inherently card-based systems require fare tables and other business-rule related configuration data to be distributed to all devices whereas in account-based systems, these tables only need to exist within the back-office. Fare rules in account-based solutions offer greater capabilities and flexibility such as journey reconstruction, best fare/fare capping, etc.

4. Card Accounts – Card-based solutions require a copy or “image” of the smartcard data to be stored in a back-office account which is updated by transactions generated on devices when the card is used for fare payment or add-value; specific fraud detection mechanisms (e.g Transaction Sequence Numbers/Counters) are required to be implemented to mitigate against fraudulent activity such as duplicate cards and unauthorized card data manipulation as well as for missing/late transaction processing. In account-based systems, an account also exists in the back-office to store the travel instruments, this being the only place where they are stored and represents the single source of truth.

5. Action List Processing – Card-based solutions rely on action lists that are sent to devices in the field to support autoload functionality. These lists support customers adding value via websites or Customer Service Centres and subsequently are used to update the customer’s physical card at a specified location; lists are distributed to devices on a scheduled basis and


of 60

there can be a delay between the customer add-value process and the data representing the value being available to write to a presented card. Action-lists are not required in account-based solutions as add-value is written directly to the card account in the back-office (via open API’s).

6. Refunds/Replacements – In card-based systems there may be a temporal mismatch between the value of travel instruments stored on the card versus the back-office card account. This has implications for example when refunds/replacements are requested and therefore online enquiries from customer service devices to the back-office are required to interrogate the back-office account to identify any outstanding top-ups, usage transactions, and current purse/pass values. For account-based systems the back-office account represents the real-time single source of truth which simplifies refund processing.

7. Pay-As-You-Go (PAYG) – This is a form of account-based ticketing where customers can use their open payment instrument (i.e. EMV-compliant bank card or NFC enabled phone with mobile wallet containing a payment instrument) to pay for transit journeys directly from their bank account. Transactions generated within the system are sent to the back-office for initial authorization and then aggregated and settled with the issuer. If transactions are not successfully authorized (e.g. insufficient funds, etc.) then the card number is added to a hotlist that is sent to all devices to block future transactions until the card is removed from the list.

8. National Common Mobility Card (NCMC) – NCMC is an application that resides on pan-India open-payments “RuPay” cards which are based on EMV specifications. The NCMC solution is governed by specifications published by the National Payments Corporation of India (NCPI) and covers card, device/terminal and back-office requirements. Central System Common Requirements

This section outlines the requirements for the Central System that are common to both card-based and account-based systems.

General Requirements

1. The Central System (CS) shall support a closed loop card-based solution as well as an account-based solution in the future; fare transaction processing and business rules processing shall be performed locally in the AFC devices for card-based cards and centrally in the back-office for account-based cards.

2. The system shall use proven technologies, software and systems and be fundamentally designed to incorporate new and emerging open fare payment technologies such as Pay-As-You-Go (PAYG) with EMV-compliant bank cards, National Common Mobility Cards (NCMC), payment applications on mobile phones, etc.

3. The system shall be PCI compliant and meet relevant local and international standards for the protection of payment card information as well Personally Identifiable Information (PII).


of 60

4. The system shall be designed around open architecture principles to allow future expansion through the use of open standards and published interfaces that avoid constraints resulting from proprietary technology.

5. The system shall utilize Commercial Off-The-Shelf (COTS) products where available.

Back Office Architecture

1. The back-office shall be designed using open architecture principles with open API’s being available to allow for interoperability with equipment/systems from different vendors.

2. The back-office platform shall be cloud-hosted and support flexible scaling-up and scaling-down, in order to handle changing transaction volumes and different operational environments.

3. The system shall be designed with a High-Availability architecture that offers maximum protection against data loss and system failure. The system shall provide >99.9% availability.

4. The system design shall ensure complete recovery from the loss of any system components at any point during operation.

5. All data shall be protected against loss or failure at a given cloud location or availability zone. The solution shall be equipped with the appropriate hardware, software, and procedures to provide redundancy and meet all performance requirements. Load balancing, automated failover, and data mirroring between multiple sites shall be provided as necessary.

6. A disaster recovery plan shall be developed that describes data backup and recovery and ensures minimal data loss in the event of a catastrophic event or system failure. The disaster recovery plan shall contain detailed procedures to be followed to restore the system to full operation following a disaster or failover event.

System Security

1. The back-office system hosting environment shall be compliant to ISO 27001 and 27002 Information Security standards

2. The system shall be compliant with all applicable Payment Card Industry (PCI) Payment Card Application (PCA) standards and with all Agency, state, and local policies for the handling of Personally Identifiable Information (PII).

3. All equipment that captures, stores, transmits, or processes bank card data shall be certified as compliant with all applicable PCI-PCA standards.

4. The storage and transmission of bank card data and PII data shall be in a tokenised or encrypted form whenever possible.

5. Connections between devices and the back-office shall use at a minimum Transport Layer Security (TLS 1.2) with strong encryption. All data sent via the internet shall be TLS 1.2 encrypted using the HTTPS protocol.

6. The back-office system/network shall be protected using firewalls.


of 60

7. Access Control shall be implemented to restrict physical and logical access to system components that contain PII and/or financial data, in accordance with PCI standards.

8. Logical access to all systems shall require two-factor authentication and be centrally managed using an industry standard user authentication and access control platform.

Financial Management Subsystem

1. A Financial Management subsystem shall be provided that supports the full auditing of all system financial activity, including reconciliation of all system accounts, and end-to-end tracking of revenue as it is generated and settled.

2. The system shall support financial clearing, settlement and automated reconciliation business functions.

3. The financial management facility shall maintain a record of transactions and financial operations, provide an audit trail and ensure the transparency of all financial transactions in accordance with federal Accounting Standards.

4. A COTS reporting package shall be provided that is capable of generating reports covering revenue management, accounts receivable, financial settlement and reconciliation.

5. The financial management subsystem shall allow for integration with the Agency’s enterprise accounting systems.

Payment Processing

1. The system shall incorporate a PCI-certified payment application to integrate with the Agency selected merchant acquirer.

2. The payment application shall support the following payment types:

a. Credit

b. Debit

c. Mobile wallets

d. Direct Debit ACH

e. In-app mobile payments from Google Pay and Apple Pay

3. The payment application shall provide the following:

a. Authorization and settlement of EMV, contactless EMV, eCom and MOTO (Mail Order Telephone Order) credit / debit card transactions

b. Ability to maintain linkage of electronic primary account numbers to the associated funding primary account number (dPAN and fPAN in Apple Pay terminology)

c. Provide a secure payment page that can be embedded in a customer’s website

d. Flexibility to split payment across multiple forms of payment


of 60

4. The payment application shall include an EMV compliant tokenisation service that supports a variety of different Acquirers and Bank Interfaces.

Central Clearing House (CCH)

1. The CCH shall perform clearing functions on all financial transactions using a configurable rules-based engine that caters for rules to be added or modified as business requirements change.

2. As a minimum, the CCH shall support financial transactions associated with the following:

a. sales transactions (cash sales, credit / debit, and PAYG)

b. transactions from vending/reload devices and fare payment devices

c. invoices (retailers and transit benefit employers)

d. adjustments, refunds, and replacements transactions

3. Summarised transaction categories shall be fully auditable with full end-to-end tracing of revenue and expenses back to supporting transaction reports

4. Exceptions to automated processing shall be flagged, reported and made available in a graphical user interface, where they can be analysed, marked as resolved, or sent for reprocessing.

5. The CCH shall be capable of configuring the following parameters and rules:

a. fees and commissions,

b. revenue apportionment rules,

c. settlement rules,

d. funds transfer rules,

e. the mapping of transaction types to General Ledger accounts.

Operational Parameters Management (OPM)

1. The system shall be implemented for 512 Metro stations and 64 fare zones.

2. The system shall include a management tool to support configuration and distribution of operational parameters, system settings, device settings, user interface resource files and device software binaries by authorized users.

3. The OPM tool shall support the configuration and distribution of all device parameters, hotlists, fare tables and other device tables as required by the system. The frequency of list updates shall be configurable and include current and future activation dates.

4. The OPM tool shall perform checks to ensure a consistent/valid set of tables is available for download to devices.


of 60

5. The OPM tool shall create a manifest of parameter files for distribution and then manage and monitor the publication of files to devices and identify devices with failed downloads. The manifest shall contain only those files that have changed in version (i.e. the system shall not require all files to be downloaded every time).

6. The OPM tool shall support publishing of operational parameters and files to a single device, multiple devices, groups of devices and all devices.

7. The OPM tool shall support the download of new software/firmware versions for devices with support for current and future activation dates.

8. The OPM workflow shall include the ability for an authorized user to provide approval for the updated configuration prior to the publishing of files to the devices.

9. The OPM tool shall support the automatic distribution of hotlists and autoload actionlists (which are special types of parameter files) without requiring approval by an authorized user.

10. The OPM tool shall log user sessions to be able to provide a history of changes, versions and distributions made by an authorized user for audit purposes.

11. The OPM tool shall support the real-time issuance of device commands system-wide and by device type, location, and individual device, using the device management API. Examples of commands include:

a. Device Entry-only mode

b. Device Exit-only mode

c. Device bidirectional mode

d. Device in-service mode

e. Device out-of-service mode

f. Open all gates mode

g. Emergency mode

12. Commands shall utilise an appropriate command protocol based on industry standards, such as SNMP, or equivalent.

13. The OPM tool shall be able to generate reports detailing current and historic parameter configuration versions, software revisions, publishing history and exception reports for failed downloads.

Device Asset Management

1. The system shall include device asset management tool that provides basic asset and life cycle management.

2. The device asset management tool shall be a COTS tool that stores device information such as

a. device type, location, software version, service history, and device status


of 60

b. configuration item by manufacturer,

c. configuration item types,

d. asset information for a specific vendor.

3. The device asset management tool shall be able to report on asset retirements for the current week, month, and year.

4. The device asset management tool shall allow authorized users to manually create, update or view device details; device details shall also be updated automatically (dependent on the type of detail) based on received events/records as reported by devices.

Monitoring

General Requirements

1. The system shall include a web-based monitoring tool that enables the central monitoring of all devices and system components.

2. The monitoring tool shall be accessible remotely using any modern desktop, mobile web browser or mobile application.

3. The monitoring tool shall provide access to all monitoring functions via a configurable dashboard using colour, graphics and text.

4. The monitoring dashboard shall include a system map and list that can be drilled-down into by location to view the status of system components.

5. The monitoring tool shall provide for manual (by authorized users) and automatic (by device events) updates when devices or systems are added and removed.

Device and Equipment Monitoring

1. The monitoring tool shall provide real-time performance and status monitoring for all devices, back-office systems, and network nodes.

2. The monitoring tool shall display device attributes, including but not limited to device type, device ID, location, status, events, and alarms.

3. Device status reported by the monitoring management tool shall include operational status (e.g., in service, degraded mode, out of service, or no communications), maintenance alarms associated with individual device modules, and revenue alerts (e.g., vault near-full/full and low stock/out of stock).

4. The monitoring tool shall monitor and display in real-time the status of all back-office systems, applications, databases, and processes.

5. Devices or systems that are not reporting status for any reason shall be easily identifiable, and the last known status and history shall be available.


of 60

6. The monitoring tool shall automatically generate alerts via email and text message. The triggers, frequency, thresholds and cancellations of alerts shall be configurable.

Key Management Facility

1. The system shall include a proven data security and key management facility, capable of managing separate device keys and security tokens to encrypt and confirm transaction authenticity.

Key Types

1. The key management facility shall support the following key types:

a. EMV Key sets including RSA Public Keys (an asymmetric public key used by card acceptance devices to verify EMV card authenticity against the Issuer's private key), EMV Data Authentication Public Key (an asymmetric public key used by card acceptance devices to authenticate EMV bankcard data), EMV Digest Key (a symmetric key/salt used to create a unique one-way hash for EMV bankcards),

b. Token Keys (master and diversified key set for secure smartcard data read and write access).

c. Closed-loop card-based keys sets (keys required for secure smartcard data read and write access)

d. MAC Key (a symmetric key/salt used to create a unique one-way hash to verify a message is valid and has come from a known and trusted source).

e. NCMC keys for OSA (Operator Service Area) areas of the card

Key Management

1. The key management facility shall incorporate a Hardware Security Module (HSM) for the secure and tamper-proof storage of keys

2. The key management application shall be used in conjunction with the HSM to perform security key management, secure credit / debit card encryption, and decryption.

3. The key management application shall encrypt and store credit / debit cards into the Token vault in a PA-DSS-compliant manner.

4. The key management application shall allow authorized users to view and generate new keys through a secure User Interface.

5. Keys generated by the key management application shall be wrapped in a certificate and digitally-signed for secure distribution to devices using secure messaging protocols.

6. All keys shall be stored on devices in tamper-proof Secure Application Modules (SAMs) or in PCI-approved secure environments

7. The Key Management should be dynamic


of 60

Message Authentication

1. All individual transactions or message bundles containing one or more transactions shall incorporate a Message Authentication Codes (MAC) to confirm message authenticity.

Access Control

1. The system shall include Role Based Access Control to configure authorized users to access system components and applications

2. Authorized users shall access systems and applications using their user name and password for authentication as a minimum

3. The system shall support configurable password validity durations and enforced password changes

4. Administrators and super-users shall log-in using two-factor authentication

5. The Access Control sub-system shall allow the configuration of individual user profiles and user groups

6. The Access Control sub-system shall be based on industry-standards such as LDAP (Lightweight Directory Access Protocol) and Active Directory to allow users/groups to be centrally managed.

7. The system shall incorporate Single Sign-On (SSO) capabilities

8. The system shall keep a record of all current and historic users along with allocated profiles over time.

Reporting Facility

Reporting General

1. The system shall include a Reporting Facility that interfaces with the local Operational Data Store, Data warehouses, and other systems as necessary, for the generation of pre-defined and custom reports.

2. Data for reporting shall be retained for a minimum of 24 months online and 60 months offline.

3. The Reporting Facility shall support scheduled and ad-hoc reporting

4. The Reporting Facility shall allow authorized users to design and save new report templates that can be shared across users

5. The Reporting Facility shall include, but not limited to, the following reports:

a. Ridership reports

b. Sales reports

c. Revenue reports

d. Deferred revenue reports


of 60

e. Financial settlement reports

f. Maintenance reports

g. Device and system performance reports

h. Customer service reports

i. Exception reports

j. Fraud detection reports

k. Device errors and alerts

l. Service planning reports

m. System and device availability reports.

6. Reports shall be able to be run and viewed through a web interface, as well as exported in several formats, including but not limited to PDF, MS Excel, CSV, and plain ASCII text.

7. The Reporting Facility shall allow all reports to be configured to run on a scheduled basis and automatically delivered to one or multiple email addresses.

8. The Reporting Facility shall support big data analytics and web-based dashboards using a COTS business intelligence tool.

9. The Reporting Facility shall provide a web interface supported by all modern desktop and mobile browsers, including but not limited to Internet Explorer, Firefox, Safari, Chrome, and Opera.

10. Access to the Reporting Facility shall be password-controlled. The ability to create and run reports shall be configurable by user type. User accounts shall be set up with custom access levels that define which reports can be viewed, and what data can be queried for custom reports.

Device Management API

1. The Device Management API shall be provided that supports the real-time reporting of device events and alarms, and the distribution of new software, configuration parameters and hotlist updates as required and will be utilised by all devices deployed within the system, including but not limited to Ticket Vending Machines, Validators, Driver Control Units, Ticket Office Terminals, Mobile Fare Inspection/Validation Device Application and Mobile Sales Devices.

2. The Device Management API shall support the passing of data between the devices and the monitoring management tool to enable the monitoring of device/system performance and issuance of commands in real-time.


of 60

Year wise Lease Amount to be Paid to lessor by DMRC

Sr. No Year Lease Amount to be Paid By DMRC

(including taxes)

1. Jan 2022-Dec 2022 Work to be completed

2. Jan 2023-Dec 2023

3. Jan 2024-Dec 2024

4. Jan 2022-Dec 2025

5. Jan 2022-Dec 2026

6. Jan 2022-Dec 2027

7. Jan 2022-Dec 2028

8. Jan 2022-Dec 2029

9. Jan 2022-Dec 2030

10. Jan 2022-Dec 2031

11. Jan 2022-Dec 2032

12. Jan 2022-Dec 2033

Royalty amount on account to get rights to issue EMV and Rupay Cards to commuters at metro

stations and facilitate existing DMRC AFC system for new services is to be kept by Lessor for the

contract period.

*****END OF DOCUMENT*****

EOI/DMRC/Open Loop Ticketing 01 DELHI METRO RAIL ......2021/01/19 · outlets/parking etc.) in...

Documents

Transcript of EOI/DMRC/Open Loop Ticketing 01 DELHI METRO RAIL ......2021/01/19 · outlets/parking etc.) in...