This document presents an initial design proposal for a real-time tum-tum tracking system. It outlines problems with the current lack of tum-tum schedule and location information. The proposed system would use GPS or RFID to track tum-tums in real-time, storing data on a central server. Users could then access estimated tum-tum arrival times and locations through SMS, a web interface, or mobile app. The document compares GPS and RFID tracking methods and concludes with an overview of the system design.

1. Presentations 2 Initial design
presentation
By:
Aditya Gupta 09005017
Ashish Yadav 09005018
Pallav Dhobley 09005012
Vikas

2.  Problems encountered and Our focus
 Flow chart and Overview
 Real time tracking of tum-tums
 Central server
 User-access
 Comparison and Conclusion

3.  From the contextual enquiries, we had made
the following observations
 Information about tum-tums not available readily
 No idea when a tum-tum is going to come, what
route is it going to follow
 Can get info from the tum-tum office, but no
runtime information (i.e when a tum-tum is
actually needed)

4.  We plan on designing a centralized
information system
 System for real time tracking of tum-tums
 GPS; RF-ID
 Centralized server to store information
 External or Gymkhana server
 User-end system to access information
 SMS, Web, Mobile app

5.  Problems encountered and Our focus
 Basic design and Flow chart
 Real time tracking of tum-tums
 Central server
 User-access
 Comparison and Conclusion

6.  Tracking of tum-tums at bus stops.
 Information to be transmitted to server
 Server keeps track of all buses running at a
time
 User can query the server for tum-tums
nearby their locations
 Server optimizes results as per user’s start
and end destination.

7. Gymkhana
Server
BUS 1
BUS 2
BUS 3
USER 1
USER 2
USER 3
GPS
NFC
+ SMS
WEB
MOBILE
APP
SMSTIME-
TABLE

8. Its Kresit
to H4, lets
walk!
Lets take
an Auto !
NO lets try this SMS
service for tracking
tum-tums

9.  Problems encountered and Our focus
 Flow chart and Overview
 Real time tracking of tum-tums
 Central server
 User-access
 Comparison and Conclusion

10.  We plan to track tum-tums
 Naïve way:
 Tum-tum timetable can be created
 Start time, Expected end time
 Start location, End location
 Estimation of time taken from one stop to
another
 During peak hours
 During normal hours
 Night hours
 This information can be used to predict the
approximate position of the tum-tums

11.  Near Field communication:
 A RFID tag to be placed in every tum-tum with a
specific identifier.
 RFID scanners to be placed at every bus stop
 Any bus crossing the stop is detected at the stop
and is recognised using the identifier
 The data has to be transmit to the central server.
 Can be achieved by sending an automated SMS
via GSM
 Currently used in some Air conditioners

12.  Global Positioning System:
 A GPS tracking device can be placed in every
tum-tum.
 GPS determines the current location of a tum-
tum using GPS satelites
 The recorded location is transmitted to a central
server using a cellular (GPRS or SMS), radio,
or satellite modem embedded in the unit

13.  Problems encountered and Our focus
 Flow chart and Overview
 Real time tracking of tum-tums
 Central server
 User-access
 Comparison and Conclusion

14.  Keeps track of all the buses.
 GPS
 RFID information
 Maintains information of the following:
 Bus routes
 Bus stops
 Estimated transit time between stops.
 Start time of bus when it leaves its stationay
place.

15.  Whenever a query of type ‘<stop1 stop2>’ is
sent to it
 Scans the database to determine buses currently
near location1
 Selects those buses which will go towards
location 2
 Calculates the approximate time required for the
next two tum-tums to arrive at location 1
 Responds to the sender with the information
 <Bus route, ETA>; <Bus route, ETA>

16.  Suppose a query of type ‘<stop1> buses’ is
sent
 Scans the database to find the tum-tums about
to cross the bus-stop
 Responds to the user with information about next
2 tum-tums
 <Bus-route, ETA>; <Bus-route, ETA>

17.  Problems encountered and Our focus
 Flow chart and Overview
 Real time tracking of tum-tums
 Central server
 User-access
 Comparison and Conclusion

18.  A user generally wants to know
 Buses from one bus-stop to other
 Buses crossing a given bus-stop
 A user can make use of the information via
the following methods :
 Short Messaging Service
 A user can send an SMS in either of these formats
 between <stop1> <stop2>
 crossing <stop>
 An additional parameter <time> can also be
allowed to find tum-tums at a specified time
 The server responds with info about the next 2
tum-tums corresponding to the query

19.  Web Interface
 Provide a web based portal to access information
about the tum-tums
 Real Time tracking on a Map can also be
implemented
 RailRadar
 Mobile Application
 Develop an app which can support the web based
functions

20.  Problems encountered and Our focus
 Flow chart and Overview
 Real time tracking of tum-tums
 Central server
 User-access
 Comparison and Conclusion

21. NFC Tracking GPS Tracking
 Cheaper than GPS
 Reader is around
Rs.1500/- ; tags cost
around Rs.45/- each*
 Less reliable
 Vulnerable to rain
 Bare-
bones, communication
to the server has to be
implemented
additionally
 Expensive
 Approx Rs. 10,000 for
each device
 More reliable; accurate
positioning
 Placed inside the tum-
tum; rain issues minimal
 Communication features
are embedded with
most tracking devices
* http://www.sunrom.com/rfid-tags-reader/rfid-reader?sunid=6ace32c53dcb8a24140d09aae23f07f9