Beruflich Dokumente
Kultur Dokumente
Expression of Interest
Hand Held Terminals for UTS Ticketing by ETMs
(Electronic Ticketing Machines)
By:
Page 1
2014/CRIS/1034
Purpose of EoI:
Date of opening of
EOI document:
Last Date for
submission of EOI
document
Validity of EOI
response
Page 2
Index
Chapter
No.
Chapter Name
1
2
3
4
5
6
7
8
9
Introduction
Overview of UTS over ETM Project
EOI Objective
Evaluation of EOI
Eligibility criteria
Proof of Technical & Financial Soundness
Indicative Architecture of UTS over ETM System
Signing of Non Disclosure Agreement (NDA)
CRIS's Right to Accept or Reject any Technical
Proposal
10 Scope of the EOI
11 Indicative locations for field trials
12 Technical specification
Annex-I
Acronyms
Annex-II
UTS Application Functional Specifications
Annex-III
Data Synchronization Application Functional
Specifications
Annex-IV
Specification for Hand held Terminal Devices
(Performa)
Annex-V
Brief Description of POC
Annex-VI
Smartcard Reader Specification
Page no.
4
4
4
5
6
6
7
8
8
8
9
10
10
11
15
16
18
19
Page 3
1. Introduction
Unreserved Ticketing System (UTS) is the predominant ticketing system on Indian
Railways in terms of the number of passengers it serves. The application was first
Implemented in 2002 and is now operational at nearly 5700 locations over 16 Zones of
Indian Railways. During the commissioning of UTS over 'D' and 'E' category stations, it
was found that number of things adversely affecting its working mainly the network
failure due to cable cutting in remote areas. The Thin Client was the best possible
solution for link failure but its working adds some additional cost in the remote areas
i.e. cost for network equipment & channel hiring and cost for Generator set including
recurring cost of fuel. Despite of that much effort uninterrupted UTS ticketing in remote
areas is still a dream.
All the above factors warrant a cost-effective and reliable alternative ticketing system
which can be used for extending UTS over F-category stations along with Halt stations.
As solutions to all the above requirements are ETMs (Electronic Ticketing Machines).
This document is intended to describe the functional specifications and system
requirement for UTS ticketing through Electronic Ticketing Machine.
3. EOI Objective
The objective of this EOI is to find out technical solution along with Hand held
terminal suitable for implementing the UTS ticketing over F-category stations
including halt stations.
The solution providers are free to provide technical solution along with Hand
held terminal giving justification why the proposed HHT devices along with
provided solution is better in meeting above objective.
Page 4
CRIS will finalize the technical solution specification based on the response of the
EOI and may process further based on the internal assessment as well as Railway
Requirement.
4. Evaluation of EOI
The Specifications provided in this EOI document are indicative specifications. The
solution provider shall thoroughly satisfy himself that the proposed solution and hand
held terminal meet the functional requirements of this EOI.
The evaluation of EOI solution proposal will be done in three phases: Stages of Execution
Stage -1
Solution
proposal
evaluation
Stage -2
Proof of Concept
Stage -3
Field Trial
Description
In this stage all complete EOI proposals received upto
15:00 Hrs on 30 days from the date of publish of the
notification of EOI will be evaluated and acceptable
solutions will be shortlisted.
Solution providers whose solutions are found
acceptable will be required to demonstrate their
solution at a place and time chosen by CRIS. They will be
given 20 days from the date of such notification to
prepare and plan their demonstration. The solution
provider has to setup a complete solution infrastructure
as deemed necessary for proving the solution.
Acceptable solutions will be chosen based on its
performance in POC as well as other requirement as
mentioned in this document. Each solution provider
may be asked to implement and commission HHT
devices with complete solution at specified field trial
locations. The solution provider has to own up the
responsibility of supply necessary components ,
implementation, commissioning for field trial,
Integration with UTS of Indian Railway, field support
and any other support as deemed necessary for
successful trial .
Note: - The solution provider should make available the offered solution during
technical evaluation of EOI for testing and bench mark at CRIS, Chankyapuri, New Delhi.
The solution provider may need to undertake the field trial at designated six stations for
3 to 6 months. After that Railway could retain the solution for its own assessment. The
Expression of Interest for Hand held Terminal for UTS Ticketing
Page 5
solution provider may mention whether they will charge any cost for the field trial. If
they intend to charge for the same they are requested to quote the same in the following
form:
Description
Cost in (RS)
Cost in terms of per unit Hand held
terminal/Tablet
solution
with
attached/external printer which will
include all necessary supply and works
item for its commissioning.
Software/Software development cost as
per functional specifications provided in
this EOI.
CRIS will provide necessary permission, electrical power source, and application
requirement and server resource at CRIS Chankyapuri for field trials.
CRIS reserves the right to cancel this request for EOI and/or invite a fresh with or without
amendments to this request for EOI, without liability or any obligation for such request
EOI and without assigning any reason.
5. Eligibility criteria
The Final eligibility criteria will be decided by CRIS based on the chosen solution, final
specification and quantum of requirement.
Page 6
Highlights of Architecture
Whenever there is a change in the Static data of Zonal UTS server should be
synchronized to the HHT/Tablet local database.
If the previous day's data is not synchronized with the zonal server, then
ticketing is not allowed for the next day. This ensures proper accountal.
Page 7
The Application server will host the application for synchronization of data from
HHT/Tablet device to the zonal UTS server.
VPN server will authenticate and secure the connection from HHT device to HHT
application server.
10.
The scope of EOI for UTS ticketing over Hand held Terminals are as: a. Supply, Installation of HHT/ETM/TABLET
specifications provided in this EOI document.
devices
as
per
functional
Page 8
11.
In the trial phase of UTS ticketing over ETMs following stations has been selected:S No.
Station name
Division
1
2
3
4
5
6
Odela
Kotla
Mahbubnagar
Nellore-South
Tirupati West
Mukundwadi
Secunderabad
Hyderabad
Hyderabad
Vijaywada
Guntakal
Nanded
Page 9
12.
Technical specification
Detailed technical specifications parameters are given in Annexure IVkk. The Solution
Provider must submit an item wise specification of these technical specifications
parameters duly vetted by OEM.
Annexure-I
Acronyms
UTS
ETM
HHT
POC
GPRS
OEM
Page 10
Annexure-II
Input Item
Originating Station
2
3
Destination Station
Route Number
No of adults Passengers
No of child
Train type
Class code
Item Description
Originating station, by default it will be
the station issuing the ticket.
Journey Destination Station
After entering destination station code
the application should display all the
available routes for the pair of source
and destination station. The application
should allow the selection of route
among the available route; the same
should be entered in this field.
Number of adults, by default it will be 1.
Maximum number of passenger(no of
Adult + No of Child) is based on Class
code
Number of children, by default it will be
0. Maximum number of passenger(no of
Adult + No of Child) is based on Class
code
Type of the train like Mail/express (E),
ordinary (O) C-Combined, S-Superfast.
Class code, by default 2nd class.
Page 11
Ticket type
Journey date
10
Concession code
After providing all the input parameter the following information should be
displayed before confirmation and printing of UTS ticket: S No
1
2
3
4
5
Input Item
Fare
Distance
Via
Ticket Number
Print
Item Description
Ticket Fare
Distance of the journey
Route Via filed if any
UTS Ticket number
Input for confirming ticket booking
Input Item
UTS No.
Ticket No.
Fare
Cancellation
F(ULL)/P(ARTIAL)
No. of adults
No of children
Item Description
Unique UTS No.
Ticket Number, by default 0.
Fare, by default 0.
Full ticket or partial cancellation, only in
case of more than one passenger on
original ticket.
only in case of more than one passenger
on original ticket and option for partial
cancellation is selected in above option
only in case of more than one passenger
on original ticket and option for partial
cancellation is selected in above option
After providing all the input parameter the following information should be
displayed before confirmation and printing of cancelled ticket along with
remaining passenger ticket in case of partial ticket cancellation: Expression of Interest for Hand held Terminal for UTS Ticketing
Page 12
S No
1
Input Item
Originating Station
2
3
4
Destination Station
Class code
Train type
Ticket type
5
6
Journey date
Refund amount
confirm
Item Description
Originating station, by default it will be
the station issuing the ticket.
Journey Destination Station
Class code of the original ticket.
Type of the train of the original ticket.
Ticket type like J Journey, V for reverse,
A for advance of original ticket
Date of Journey of original ticket
Amount refunded after deducting
cancellation charges.
Input for taking confirmation for
cancellation of ticket
Input Item
Station Code
Terminal ID
Operator Code
Date
Shift No
Starting Stock Number
Ending Stock Number
Total Ticket Issued
Item Description
Station code of the HHT device.
Unique hand held terminal ID.
Login ID for the operator.
Login Date of the operator
Shift number of Operator
Page 13
8
9
10
Page 14
Annexure-III
Page 15
Annexure-IV
Specifications for Hand held Terminal Devices (To be filled by Solution Provider)
S
No.
1
1
2
3
4
5
6
Parameter
Form Factor
Processor
RAM memory
Data Memory
Secondary Data
Memory
(Expansion port)
Display
Battery/Battery
Bank
Key Pad(In case
of HHT without
Touch screen)
Communication
Interfaces
10
Connectivity
Support
Printer
11
Specifications
Like HHT or Tablet
12
Operating System
13
Operating
Temperature
Humidity
Terminal
Management
Status
Indications
14
15
16
17
Protocols
Page 16
18
Carry Case
19
20
Weight
Environmental
sealing
Drop Durability
Accessories
Environment,
Health and Safety
& EMI/EMC
Compliance
Comprehensive
Warranty &
Services
Lightweight
database support
Future Support
21
22
23
24
25
26
Note: The OEM should also release patches and upgrades in respect of resolving the
issues identified during trials.
Parameter
Length of Ticket paper
roll
Width of Ticket paper
Thickness of Paper
Value
15000 mm
80 mm
60 GSM
Tickets should be printed in two languages English and Hindi. There will be
approximately 200 tickets per roll.
Page 17
Annexure-V
The data of UTS ticketing should be stored locally on the HHT device.
The device should support storage of data in RDBMS form.
To provide additional security of the data, the device should support the data
storage in the encrypted format.
To avoid the loss of data, the device should allow the data storage in two
different places i.e. internal memory and external card.
In case data is not recoverable from first storage place then it should be
recovered from the other storage place.
HHT device should support the connectivity to UTS server through GPRS over
secured VPN tunnel.
HHT device should also allow the connectivity through UTS Hub (Work
Station/Network Switch).
The device should allow the data synchronization from Device database to UTS
server database at some regular interval (by scheduling) or on user selection
basis.
Page 18
Annexure-VI
Item
Description
1 Inbuilt ISO14443A Smart Card Reader/NFC to read Desfire family Cards.
Future Support for 2 SAM slots.
2 Operating distance
Up to 50 mm
5
6
7
9
Interface frequency
Modulation & Data Coding
Baud rate
Communication Standards
10 Communication Protocols
11 Crypto Support
12 Security Feature
1000(Host to Controller)
3V to 5V
Page 19
Filename:
Directory:
Template:
1034
D:\My Documents
C:\Users\RAKSHA\AppData\Roaming\Microsoft\Templates\Normal.dot
m
Title:
Subject:
Author:
cris
Keywords:
Comments:
Creation Date:
31-Oct-14 6:36:00 PM
Change Number:
2
Last Saved On:
31-Oct-14 6:36:00 PM
Last Saved By:
RAKSHA
Total Editing Time:
1 Minute
Last Printed On:
31-Oct-14 6:38:00 PM
As of Last Complete Printing
Number of Pages: 19
Number of Words: 3,912 (approx.)
Number of Characters:
22,304 (approx.)