Navi Mumbai Metro Line 1

AnTaCs
Request for Change of Requirement-Automatic Fare Collection and Smart Card system

City and Industrial Development

Corporation of Maharashtra Limited
(CIDCO)
AnTaCs Navi Mumbai Metro Rail Project
Line - 1
Contract: Design, Manufacture, Supply, Installation, Testing,
Commissioning of complete metro rail system on turnkey basis including
Spares, Training of Operation and Maintenance Personnel, handover to the
Authority of the whole equipment necessary to comply with the Authority’s
requirements comprising of Rolling Stock including Driving Simulator;
Signalling & Train Control; Communication System; Power Supply,
Traction & SCADA; Track Works (ballastless for the main line and for the
depot); Automatic Fare Collection and Depot Equipment for Navi Mumbai
Metro Line 1 (NMML1 – elevated route about 11.0 km long and at grade in
depot along with the approach lines to the depot) and Rail Systems’
maintenance for three years.
C. A. No. 02/CIDCO/RP/SE (TP-III) /2012-13
Contractor:

AnTaCs Consortium
(Consortium of Ansaldo STS SpA., Tata Projects Limited and
CSR Zhuzhou Electric Locomotive Co., Ltd.)
SLV Complex, AVS Compound, No.35,
80 Feet Road, 4th Block, Koramangala,
Bangalore - 560 034.
Karnataka, India.

Document Title:
REQUEST FOR CHANGE OF REQUIREMENT
(Reliability target)

Initial Submission 21.03.2019

Nazareth
Pradeep Sawant Abhinav Kumar
Guerrero

Author Approver: Authoriser

Description of Revision Date

Document Number Request For Change of Requirement

Page 1 of 8
Revision 00
 Navi Mumbai Metro Line 1
AnTaCs
Request for Change of Requirement-Automatic Fare Collection and Smart Card system

Document Number Request For Change of Requirement

Page 2 of 8
Revision 00
 Navi Mumbai Metro Line 1
AnTaCs
Request for Change of Requirement-Automatic Fare Collection and Smart Card system

Revision
Rev. Date Author Reviewer Approver Authorizer
Description

Juan
Nazareth Pradeep Abhinav
00 2019/03/21 Manuel First Release
Guerrero Sawant Kumar
Armenteros

TRACEABILITY OF THE REVISIONS

Revision
Rev. Date Author Approver Authorizer
Description

Document Number Request For Change of Requirement

Page 3 of 8
Revision 00
 Navi Mumbai Metro Line 1
AnTaCs
Request for Change of Requirement-Automatic Fare Collection and Smart Card system

INDEX
1. INTRODUCTION .................................................................................................. 5
1.1 DEFINITIONS, ACRONYMS AND ABBREVIATIONS .................................................................... 5
2. DESCRIPTION ..................................................................................................... 5
2.1 PROPOSAL ......................................................................................................................... 5
3. TECHNICAL REASON ......................................................................................... 6
3.1 MCBF CALCULATION ......................................................................................................... 6
3.2 TVM, TIM AND POST ........................................................................................................ 7
3.3 AG .................................................................................................................................... 8
4. CONCLUSION...................................................................................................... 8
5. SOURCES ............................................................................................................ 8

Document Number Request For Change of Requirement

Page 4 of 8
Revision 00
 Navi Mumbai Metro Line 1
AnTaCs
Request for Change of Requirement-Automatic Fare Collection and Smart
Card system

1. INTRODUCTION

The purpose of this document is to justify the non-compliance with the

requirement 2.12.1.2 of the technical specification [1].

1.1 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

AG Automatic Gate

MCBF Mean Cycle Between Failures

MTBF Mean Time Between Failure
POST Point Of Sales Terminal
TIM Ticket Issuing Machine

TVM Ticket Vending Machine

2. DESCRIPTION

The requirement under evaluation is the following:

“2.12.1. The achieved level of reliability for the system, shall ensure a MCBF of:
a. 900,000 cycles, to be demonstrated at the completion of six (06)
months after commencement of Revenue Service.
b. 1,200,000 cycles, to be demonstrated at the completion of eighteen
(18) months after commencement of Revenue Service.
A cycle is defined as one issue from a TIM/TVM/POST or one entry into
the paid area or one exit from the paid area.”

2.1 PROPOSAL
In order to allocate suitable values that respond to the current state-of-the-art of
the ticketing subsystem/components placed on the market, the requirement
2.12.1.1 should be re-evaluated and updated accordingly (please see section 3).

The change proposal is as following:

2.12.1.1 The achieved level of reliability for the Automatic Fare Collection
subsystems/components shall ensure a MCBF of:
a. TIM/TVM: 25.000 cycles, to be demonstrated at the completion of eighteen
(18) months after commencement of Revenue Service.
b. POST: 40.000 cycles, to be demonstrated at the completion of eighteen
(18) months after commencement of Revenue Service.
Document Number Request For Change of Requirement
Page 5 of 8
Revision 00
 Navi Mumbai Metro Line 1
AnTaCs
Request for Change of Requirement-Automatic Fare Collection and Smart
Card system
c. AG: 50.000 cycles, to be demonstrated at the completion of eighteen (18)
months after commencement of Revenue Service.
A cycle is defined as one issue from a TIM/TVM/POST or one entry into
the paid area or one exit from the paid area.

3. TECHNICAL REASON

According to cycle definition, requirement 2.12.1.1, the MCBF applies to the

following subsystems:
 Token Vending Machine (TVM/TIM)[2]
 Point Of Sales Terminal (POST[3]
 Automatic Gates (AG)[4]

For the TVM/TIM and POST a cycle is defined as one issue and for the AG as
one entry to the paid area or one exit from the paid area.

It is important to note, the reliability parameter “MCBF” is based on the

subsystem/component cycles, which in turn respond to its specific functionality.
Therefore, the MCBF must be allocated at component/subsystem level
performing the same functionality to be consistent.

3.1 MCBF CALCULATION

Mean Cycles Between Failures (MCBF) is the average of number of cycles
between chargeable failures. Non-chargeable failures will be identified as:
 Non-relevant failures
 Relevant failures caused by a condition previously not specified as being
the responsibility of a given organizational entity.
A non-relevant failure is a malfunction caused by a condition external to the
equipment under test, which is neither a functional, environmental, nor a test
requirement and is not expected to be encountered during normal and correct
operation of the equipment in revenue service. Non-relevant failures shall include
the following but not limited to:
 Accident or mishandling
 Failure of test facility or test instrumentation
 Equipment failures caused by externally applied overstress conditions
excluding the approved specification requirements.
 Operating adjustments nor made in accordance with equipment operating
and maintenance manuals
 Dependent failures occurring with the independent failure that caused
them
 Failures of expendable items beyond the defined replacement time of the
item

Document Number Request For Change of Requirement

Page 6 of 8
Revision 00
 Navi Mumbai Metro Line 1
AnTaCs
Request for Change of Requirement-Automatic Fare Collection and Smart
Card system

Failures of expendable items beyond the defined replacement time of the
item
 Failures caused by incorrect operating, maintenance or repair procedure
 Failures due to components not supplied by the System Integrator
MCBF is expressed as:

𝑇𝑜𝑡𝑎𝑙 𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝐶𝑦𝑐𝑙𝑒𝑠

𝑀𝐶𝐵𝐹 =
𝐶ℎ𝑎𝑟𝑔𝑒𝑎𝑏𝑙𝑒 𝐹𝑎𝑖𝑙𝑢𝑟𝑒𝑠

To calculate a MCBF at system level, it is necessary to calculate an equivalent

MCBF through the MTBF figures.

𝑀𝐶𝐵𝐹𝑒𝑞𝑢𝑖𝑣 = 𝑀𝑇𝐵𝐹 𝑥 𝐶𝑦𝑐𝑙𝑒𝑠/ℎ𝑜𝑢𝑟

Mean Time Between Failures (MTBF) is the average of time between chargeable
failures. MTBF is expressed as:
𝑂𝑝𝑒𝑟𝑎𝑡𝑖𝑛𝑔 𝑇𝑖𝑚𝑒
𝑀𝑇𝐵𝐹 =
𝐶ℎ𝑎𝑟𝑔𝑒𝑎𝑏𝑙𝑒 𝐹𝑎𝑖𝑙𝑢𝑟𝑒𝑠

To perform MTBF figures based on components that make up the system:

1
𝑀𝑇𝐵𝐹 =
1
∑𝑖
𝑀𝑇𝐵𝐹𝑖

Where 𝑀𝑇𝐵𝐹𝑖 is the MTBF of the i components of the system.

Therefore, each component impacts on the final MTBF (in consequence, affects
the MCBF figures), and the result is always lower than the value of each element
individually.

3.2 TVM, TIM AND POST

TVM/TIM and POST accepted credit/debit card payments. Based on Indra return
of experience from previous projects1, the table below shows the achievable
MCBF for some components of the TVM, TIM and POST:
Component Model1 MCBF
Manual reader Verifone UX 500,000 insertions
PinPad Verifone UX 2,000,000 pulsations2
Remarks:
1 Please note, the manufacturer/model of the components has

been included as reference.

2 A cycle of the PinPad is composed by 5 pulsations; it means

the MCBF for this component is 400,000 cycles.

1 AFC Riyadh, AFC Malasya and AFC Thessaloniki projects

Document Number Request For Change of Requirement
Page 7 of 8
Revision 00
 Navi Mumbai Metro Line 1
AnTaCs
Request for Change of Requirement-Automatic Fare Collection and Smart
Card system
According to the achievable values presented in table above, the Manual reader
and the PinPad individually does not reach the target included in requirement
2.12.1.1 for the TVM/TIM and POST susbsytems and therefore the addition of
the rest of LRUs conforming the TVM/TIM and POST in the calculation, will
contribute in decreasing the MCBF at sub-system level.

3.3 AG
In regards to the Automatic Gates, based on Indra return of experience from
previous projects, the achievable MCBF for the entrance control module is
1,000,000 cycles and therefore the addition of the rest of LRUs conforming the
AG in the calculation, will contribute in decreasing the MCBF at sub-system level.

4. CONCLUSION

As explained in section 3, the reliability targets included in the requirement

2.12.1.1 are not achievable with the current state-of-the-art of the ticketing
system.
In Chapter 2.1 a requirement is proposed based on Indra return of experience
and in accordance with the current state-of-the-art of the ticketing system.

5. SOURCES

[1] Automatic Fare Collection System Employer’s Requirements – Technical

Specifications Navi Mumbai Metro Rail Project Line – 1
[2] NMML1-AFC-8-B-0012 – TVM Detail Design
[3] NMML1-AFC-8-B-0013 – POST Detail Design
[4] NMML1-AFC-8-B-0019 – AG Detail Design

Document Number Request For Change of Requirement

Page 8 of 8
Revision 00