myRide: A Real-Time Information System for the Carnegie Mellon University Shuttle


Published on
myRide is a real-time transit information system for the Carnegie Mellon University Shuttle. It was built by Heinz College graduate students in the fall of 2009. The pilot will end in December 2009, but the website ( will remain up as we work to make myRide a permanent system at Carnegie Mellon.

Published in: Education, Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

myRide: A Real-Time Information System for the Carnegie Mellon University Shuttle

  1. 1. a a real-time pilot for the CMU Shuttle<br />Daiying Chen DAVId LevinsonAddam Hall KAREN MESKOLisa Hall EI EI MIN THUNolan Leavitt SUDHEER SOMESHWARA<br />Fall 2009 <br />Heinz College, Carnegie Mellon University<br />
  2. 2. Agenda<br />History<br />Planning<br />Implementation<br />Results<br />Going Forward<br />
  3. 3. Stakeholders<br /><ul><li>Stakeholders</li></ul>Starting Problem<br />Advancing knowledge within CMU community, in line with Traffic21<br />Benefiting area residents and commuters<br />Make significant and substantial contributions to public policy and non-profit management<br />
  4. 4. Our Changing World<br />
  5. 5. Our Solution: Real-Time Information<br />Real-Time Transportation Information<br />Cutting-edge technology<br />Novel solution to reliability problems<br />Many benefits<br />To riders<br />To transit providers<br />To community<br />
  6. 6. Agenda<br />History<br />Planning<br />Implementation<br />Results<br />Going Forward<br />
  7. 7. Deliverables<br />Port Authority Technical Capabilities Report<br />Public Transit Ridership Surveys<br />myRide website -<br />Funding Request for permanent system<br />Future coursework plans <br />Android Phone GPS tracking application<br />Google Transit Feed Specification compliant database<br />Mobile Webpage <br />Project Document Report <br />
  8. 8. Benchmarking<br />University of Michigan<br />TransLoc<br />~60-bus fleet covers 10 routes<br />~Magic Bus was designed by students<br />~Maintained by staff and students<br />~Funded by Transportation Dept.<br />~Newer company based in Raleigh<br />~Provides services for 15 schools, including Princeton, Auburn, and Yale<br />
  9. 9. Internal CMU Ridership Survey<br />Goal: identify the most effective and desired<br />dissemination methods for the CMU shuttle<br />Small, N= 51<br />Conducted in person at CMU Shuttle stops and on the Shuttle.<br />Time frame: Weekdays at various times in mid-October.<br />
  10. 10. CMU Ridership Survey Takeaways<br />Shuttle riders do have issues with the timeliness of service.<br />A wide range of people use the shuttle.<br />Shuttle riders have very high levels of access to Internet and Text plans.<br />iPhones would not be the most effective way to reach the largest number of people.<br />Focus on a webpage that can be viewed on mobile devices.<br />
  11. 11. Pittsburgh Community Survey<br />Goal: Measure attitudes and perceptions in regards to public transit and technology. <br />Key factors we wanted to measure:<br />Ridership habits<br />Factors affecting demand elasticity for public transit<br />Access to information dissemination methods<br />Receptiveness to various real-time services<br />Perceived value of a real-time system<br />The questions posed to respondents were modeled after a series of questions used in a 2006 study by the FTA in estimating benefits of a real-time system.<br />Source: Real-time Bus Arrival Systems Return on Investment Study. Federal Transit Administration, 2006.<br />
  12. 12. Pittsburgh Community Survey Methodology<br />Our survey was limited in breadth and depth by a limited time<br />frame and limited resources. The sample size is not intended to be a<br />random sampling of Allegheny County residents; instead, it attempts<br />to measure riders and advocates in the Oakland-Downtown<br />corridor. <br />N=148<br />Survey conducted in-person and online<br />31% Random sample of pedestrians and bus riders in the Oakland corridor and downtown<br />35% Students, faculty and professionals in the Higher Education field<br />34% Developmental, cultural and transportation advocacy groups<br />
  13. 13. Pittsburgh Community SurveyPreferred Delivery Methods<br />Access to method:<br />97.1%<br />90.1%<br />72.8%<br />21.3%<br />
  14. 14. Pittsburgh Community SurveyPerceived Value<br />
  15. 15. Pittsburgh Community SurveyPerceived Value<br />
  16. 16. Pittsburgh Community Survey Takeaways<br />When compared with other metro regions, the Oakland-Downtown corridor has:<br />The FTA estimated that a system widereal-time system would increase ridership by 6%-8%.<br />Source: Real-time Bus Arrival Systems Return on Investment Study. Federal Transit Administration, 2006.<br />
  17. 17. Scope Framework<br />Transmitting Real-time Bus Location Part<br />Bus with GPS <br />Send GPS data to Web server<br />G-phone & T-mobile<br />Web Application<br />Web server<br />Mobile Web<br />Riders<br />Map Plug In<br />Estimated Time Module<br />Location Retrieval Module<br />Accessing Real-time BUS Location Part<br />GTFS Data Schema<br />
  18. 18. Use Case Diagram<br />myRide System<br />Add new Alert for riders<br />Start auto-GPS transmission for any Route<br />Add another Admin user<br />Transport Admin<br />Stop auto-GPS transmission for any Route<br />View myRide on their Mobile Phone<br />View Current Bus location on the map<br />Driver<br />View estimated arrival time for their bus stop<br />Change the Route <br />View full schedule for each route<br />Rider<br />General User<br />Use Twitter to follow, share the updates <br />
  19. 19. Agenda<br />History<br />Planning<br />Implementation<br />Results<br />Going Forward<br />
  20. 20. Logistics<br />
  21. 21. Graphic Design<br />
  22. 22. Graphic Design<br /><br />
  23. 23. Marketing Roll-out<br />
  24. 24. Demo:<br />
  25. 25. Highlighted tables are GTFS-compliant schema<br />Improve scalability and future enhancement with Google<br />GTFS-Compliant Database Schema<br />
  26. 26. Data Source Challenges<br />Bus stop information not available<br />Collected bus stop information<br />Obtained GPS longitude/latitude from Google Maps<br />Collaborated with drivers to get accurate schedule<br />Route and schedule data population<br />3 Routes<br />23 Stops<br />78 Trips<br />1140 records of Stop-times<br />
  27. 27. Route Stops Population Data<br />
  28. 28. Runs as background service on Google Android Phones<br />Transmits GPS data every 5 seconds<br />Easy to use for different routes<br />User-friendly User Interface (UI) for Shuttle Drivers<br />GPS Transmission<br />
  29. 29. GPS Transmission Challenges<br />Get GPS<br />Learning curve of Android Platform<br />GPS providers <br />Network vs. GPS satellite provider <br />Adjusting GPS transmission interval <br />1 minute or 50 seconds or 5 seconds<br />Performance vs. Accuracy<br />Deployment to real phone <br />Versions crisis<br />GPS background service challenge<br />Reliability of hidden service<br />Does phone screen lock stop our application?<br />Transmit to Web Server<br />Background Service<br />
  30. 30. Main Web Interface<br />
  31. 31. Challenges Behind the Scene<br />Geographic Information System<br />Calculating distance by Vincenty’s formula with ellipsoidal model of earth<br />Accuracy within 0.5mm[1]<br />Route distances vs. straight-line distance<br />Mapping raw GPS to nearest bus stop<br />Geocoding with Google Map<br />Reverse Geocoding<br />Encoded Geopolyline mapping<br />Ajax and timer for updating real-time<br />Cross-Browser Compatibility<br />[1] Source:<br />
  32. 32. Challenges: Estimated Time Prediction<br />Inaccurate schedule stop times<br />Exponentially Weighted Moving Average<br />Problem with frequent stop times <br />Kalman-Filter Prediction Algorithms[1]<br />Consider dwelling times<br />Various Scenarios <br />Select stop time<br />Schedule time<br />Last trip<br />[1] Source: Prediction Models of Bus Arrival and Departure Times, University of Toronto<br />
  33. 33. Challenges: Estimated Time Prediction<br />Is Schedule running?<br />No<br />Display Not Running Now<br />Yes<br />Display Location without Time<br />Get Latest GPS data<br />Yes<br />Last Trip of the day and passed by?<br />Is GPS data outdated?<br />Yes<br />Get Next Schedule Time<br />Yes<br />No<br />No speed? Or Morewood is in between?<br />No<br />Get the distance and speed to selected stop<br />Predict time <br />
  34. 34. Mobile Phone Interface<br />
  35. 35. Challenges<br />Display and bandwidth limitations<br />Layout changes for mobile<br />Decrease page load time<br />Request redirection<br />Device detection<br />Users<br />Request<br />
  36. 36. Transport Admin Interface<br />
  37. 37. User Location Detection<br />Detecting nearest stop based on user’s current location<br />Google Gears – Geolocation API<br />
  38. 38. Agenda<br />History<br />Planning<br />Implementation<br />Results<br />Going Forward<br />
  39. 39. Test Cases<br />
  40. 40. Test Reports<br />Test for Route AB – by Ei Ei Min Thu 11/08/09<br />Procedure: attached the phone on bus window without interaction. Phone is charged with laptop on.<br />
  41. 41. Web Counter<br />Thanksgiving Holiday<br />
  42. 42. Accomplishments<br />Android deployment<br />GIS (Geographic Information Systems) Challenges<br />Estimating bus arrival time<br />Mobile Compatibility<br />
  43. 43. Agenda<br />History<br />Planning<br />Implementation<br />Results<br />Going Forward<br />
  44. 44. Next Steps: Future Enhancements<br /><ul><li>Enhance System Admin module to update the Route and the stop times on the UI
  45. 45. Improve the Estimated Time algorithm
  46. 46. Incorporate the CMU Escort and PTC Shuttle Route
  47. 47. Add advertisements and school announcements on the website</li></li></ul><li>Next Steps<br />Continue the Pilot <br />Install more robust hardware<br />Create an iPhone application<br />Devise traffic monitoring system based on sensor and server capabilities<br />Pursue funding opportunities<br />Advertisements<br />University Funding<br />Traffic21<br />
  48. 48. Acknowledgements<br />Robert Hampshire (team advisor)<br /> (donation of G1 Phones)<br />CMU Shuttle: Lt. Gary Scheimer, Jim Heverly, Jim McNeil, Colton Brown, James Collins, & Jason Brown<br />Hillman Foundation <br />Ramayya Krishnan, Rick Stafford, Dave Roger, Steve Bland, and Joe Hughes (advisory board)<br />Gary Franko (design and printing support)<br />
  49. 49. Contact Information<br />Addam Hall (project manager):<br />EiEi Min Thu (IT manager):<br />Robert Hampshire (advisor):<br />