Functional Requirements

a) Hand-held Electronic Ticketing Machines (ETMs)

i. These units shall be hand held devices which will be carried on DTC Buses by Bus crew. ETMs can also be used for sale of Tickets at Bus stops/terminals.

ii. The unit shall designed and configured to cater to all types of operations including Inter state, NCR, City and special category buses operating on flat fare structure, etc. upto 1000 tickets per single charge of batteries with technical compatibility of quick recharge. It should also display charge level of battery on the screen.

iii. Provision shall be available to download & store minimum 100 Route details each consisting of 100 stages with eight-character alphanumeric name description and five-digit rate.

iv. ETM shall be capable of handling multiple routes as per duty planned for the day.

v. ETM shall be able to print the ticket as per the specified format. Every ticket shall have a unique ticket number generated. The ticket number shall be 15 digits with the combination of ETM code, Bus Number, Date & the serial Number. Tickets

issued by the ETM(S) shall have a legible print by use of an adequate font size in order for the commuters to read the same easily.

vi. ETM shall be able to generate ticket with the minimum key strokes for easy &

effective operations. For generating a ticket other than Passes and Luggage / child tickets, the key strokes shall be preferably restricted to the punching of

• Destination code- will be punched in by the conductor

• Source/Origin code – will be changed through

• Pressing the Next button on the panel of the unit at each bus stop /source.

• Punching the Source code directly through the keys on the panel

• No of persons in a group

• No of Full tickets & No of Half tickets in a group

vii. ETMs shall be able to issue the group tickets i.e. it shall be able to accept the number of persons, number of full ticket, number of half tickets in a group and compute the fare accordingly.

viii. ETMs shall be able to issue the luggage tickets and child tickets. Following information shall be captured while issuing these types of tickets

9 Type of ticket ( Luggage, child tickets, etc) 9 Route Number

The conductor shall be able to record the following information 9 Type of Ticket

9 Category ID (Incase of child Ticket) 9 Destination ( Incase of child Ticket) 9 Fare

ix. ETMs shall have a facility to print the repeat tickets with press of only one button on the key pad. That is for the cases where two separate passengers’ source &

destination are same.

x. Ground staff at the terminal shall be utilized for issuing the tickets through the ETMs specifically configured for this activity. These tickets shall be Route

specific & not the Bus specific. Commuter is expected to board the bus with in one hour period from the time of ticket issue.

xi. ETMs shall be capable of issuing tickets on a non standard route/fallback route, incase of non-adherence to pre-fed routes due to any reasons. In this case, the ticket will only have the time stamp, ETM unit code and the fare denomination on them based on the fare stages defined.

xii. ETMs shall provide a facility to compute the refund amount as per business rules of DTC for Interstate & NCR operations.

xiii. Business rules for fare stages, fare structures, various routes, etc shall be configurable. ETMs shall have facility to compute the fare as per the fare stages defined by DTC.

xiv. At the end of every trip, ETMs shall be able to print the trip report.

xv. At the end of every duty, ETMs shall be able to print the duty summary report.

xvi. ETMs should be able to provide/print information about the number of passengers on board at any given point of time based on the ETM data. This will be useful for the enforcement officials and also to the conductor to keep track of the commuters without correct tickets or no tickets.

xvii. ETMs shall provide facility to enter the Inspector employee ID and generate inspection report with Date & Time stamp.

xviii. ETMs shall have an access control mechanism build in to facilitate authentication and authorization. Shall work with multiple operators with User Ids & passwords.

ETMs shall have capacity to store the conductor’s User ID & passwords specific to depot, for authentication & authorization.

xix. DTC wishes to capture the data regarding the travel flow patterns of the pass holders using ETMs. For this the pass holders would be required to present the pass to the conductor while traveling. The conductor shall be able to record the following pass information.

9 Ticket Classification (i.e. indicate that this is a Pass ticket).

9 Pass category ID ( i.e. Student pass or Travel as you go) 9 Destination

If free traveler then following information will be captured

9 Ticket Classification (i.e. indicate that this is a free traveler ticket).

9 Free traveler category ID ( i.e. Police or Other) 9 Destination

9 The conductor shall record the above information with minimum key strokes.

xx. ETMs shall be able to capture the information on number of daily passes sold during the duty / trip (in case DTC decides to issue daily passes manually). The conductor shall be provided with interface to enter the numbers before generating trip report. ETMs software shall compute cash collected through this operation and the same will be used during cash reconciliation at Base Station.

xxi. DTC is planning to introduce a loyalty programme on the lines of various airlines.

Therefore provision should be made to capture the personal details of the frequent travelers on DTC buses. This functionality shall be restricted to Interstate operations

xxii. DTC may engage the services of various booking agents for selling tickets on interstate routes. These agents would not be using ETMs to generate tickets.

Therefore it is imperative that some data of the passengers traveling on agents’

tickets be captured by conductor through ETMs. This data could be utilized to cross check the claims submitted by the Agents. There shall be a facility in the ETMs for the conductor to capture the tickets data issued by DTC agents on Interstate buses. ETMs shall capture the following information:

9 Agent Code 9 Source 9 Destination 9 Date & time stamp

xxiii. All the ETMs shall be docked at respective depot / Base Station at the end of the day. The ETMs shall be fed with unique code, to identify that the tickets are issued from valid ETMs and thus controls the misuse of the ETMs. This number will be randomly generated unique number and entered every day at Base Stations, before issuing the ETMs to DTC conductors.

xxiv. Data exchange facility shall be provided between ETM to PC / Desktop.

xxv. The list of minimum inputs attributes to be captured through these ETMs are:

9 Category of Buses – Cat 1(City buses, Inter state buses, NCR Buses and special buses)

9 Category of Buses – Cat 2( General, Deluxe, etc ) 9 Source

9 Destination

9 No of people for Group ticket.

9 Ticket Inspector ID and Time stamp of checking 9 Luggage charges

9 Minor Repairs & maintenance during the trip 9 Terminal fee

9 Toll taxes 9 Refund

xxvi. ETMs shall be provided with the off board charging facility in the depots.

xxvii. ETMs shall be designed keeping in view the mobility, usability and robust operations. ETM’s should be light weight which should not exceed 500 gms.

xxviii. ETMs shall be water proof, dust proof, heat resistant and shock proof.

xxix. Proper casing with a strap, for ETMs shall be provided.

b) System at Base Stations

This shall be defined as the system required at DTC depots, in which ATIS Project will be implemented, across the NCT, Delhi.

i. Base Stations shall be set up by the vendor at each of DTC’s Bus depots across the NCT of Delhi.

ii. Vendor shall provide the hardware and accessories to run the application software at the Base Stations.

iii. Vendor shall develop the application software necessary to execute the business processes expected to be performed at DTC depots.

iv. Application software at Base Stations shall have following capability.

a. DTC will provide Vendor with the duty plan sheet including routes, trips, bus numbers, conductor & driver’s ID and date & time.

b. The user interface shall be provided at the Base Station to pre- feed the necessary Information into the ETMs at the beginning of the duty based on the duty plan sheet provided by DTC. e.g. Route structure, fare stages, bus number, conductor ID, Depot ID, date, ETM ID, etc.

c. Business rules for fare stages, fare structures, various routes, etc shall be configurable.

d. The facility shall be provided to download the transactional data from the ETMs at the end of the Duty. There shall be a user interface provided to execute the data transfer operation at the Base Station.

e. There shall be a facility in the software to issue & receive the ETMs and shall be able to generate the status report.

f. Application shall have facility to capture the information regarding the tickets sold through the existing manual system incase the ETMs is not available for some unavoidable reasons.

g. Application software shall provide the cash reconciliation facility to tally the cash physically deposited at the depot / Base Station and the cash values pertaining to that particular duty sheet computed by the ATIS System.

h. Application shall keep a record of the consumables issued to the conductors along-with the ETMs.

i. The application shall provide facility to query the data and generate the customized reports as per the requirements.

j. Application shall be able to compute the applicable taxes based on transactions for different states for different routes and the tax rates stored in the masters.

k. DTC officials shall be able to access the application as per the predefined roles and responsibilities.

v. The Application software shall be able to store the transactional data received from ETMs and will be able to generate various reports. Few of the pre-defined reports are as listed below:

a. Application shall be able to create the Waybill for conductors and duty Sheets for the Drivers to be carried on board.

b. Cash collection reports, Duty wise, Bus wise, Bus category wise, conductor wise, Route wise, Denomination wise, terminal wise, consolidated report at depot level, etc.

c. Number of tickets issue Duty wise, Bus wise, Bus category wise, conductor wise, Route wise, Denomination wise, terminal wise, consolidated report at depot level, etc.

d. Report indicating travel flow patterns of pass holders, Pass category wise, Route wise, and pattern during specific period of the day, etc at base station level.

e. Consolidated report indicating travel flow pattern of commuters including pass holders.

f. Consumables reports weekly, fortnightly, monthly at depot level.

g. ETM maintenance requests status reports, including ETM ID, Date of complaint log, Description, action taken, Cost, Part changed, status of the call, call closing time, consolidated report at depot level, etc

h. Other miscellaneous reports

i. Application software shall have pre-defined reporting structure as per the hierarchical based access control.

j. Sample reports formats are described in the Appendix-4 for reference.

vi. Base Station shall be provided with the off board charging facility for the ETMs.

c) System at Central Control Station

This shall be defined as the system required at the central place for consolidation as identified by DTC.

i. Central Control Station is the central place where the main application software will be installed and all Base Stations will access the same application as per the access rights set.

ii. All the software upgrades / maintenance will be done through the central Control Station system.

iii. Central Control Station shall be set up by Vendor at one of the locations identified by DTC.

iv. Vendor shall provide all hardware and accessories to run the system at the Central Control Station.

v. Vendor shall develop the application software necessary to execute the business processes expected to be performed at Central Control Station.

vi. Application software at the Central Control Station shall have following capability.

a. Applications Software shall have a facility to define the Masters.

b. New routes shall be created in the application master and shall be mirrored at all the base stations with in 12 hours of intimation.

c. Business rules engine for fare stages, fare structures, various routes, etc shall be configurable.

d. The facility shall be provided to collate the transactional data received from Base Stations. The transaction data would be uploaded once every day for the previous day.

e. DTC officials shall be able to access the application as per the pre-defined roles and responsibilities.

f. The application shall provide facility to query the data and generate the customized reports as per the requirements.

vii. The application software shall be able to store the transactional data received from Base Stations and will be able to generate various reports. Few of the pre-defined reports are as listed below.

a. Cash collection reports, Duty wise, Bus wise, Bus category wise, conductor wise, Route wise, Denomination wise, terminal wise, depot wise, etc.

b. Number of tickets issue Duty wise, Bus wise, Bus category wise, conductor wise, Route wise, Denomination wise, terminal wise, depot wise, etc

c. Report indicating travel flow patterns of pass holders, Pass category wise, Route wise, and pattern during specific period of the day, etc at central control station level.

d. Consolidated report indicating travel flow pattern of commuters including pass holders.

e. Consumables reports weekly, fortnightly, monthly consolidated for all depots.

f. ETM Maintenance requests status reports, including ETM ID, Date of complaint log, Description, action taken, Cost, Part changed, status of the call, call closing time, depot wise, etc

g. Other miscellaneous reports as defined by DTC

h. Application software shall have a pre-defined reporting structure as per the hierarchical based access control.

2. Technical Requirements