1 / 27

MBTA-realtime

Learn about the integration of MBTA realtime predictions and alerts into a GTFS-based platform in this T3 Open Data webinar from December 2013. Discover the motivation, vision, execution, results, and lessons learned from this project.

sidneym
Télécharger la présentation

MBTA-realtime

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MBTA-realtime Integrating predictions and alerts into one GTFS-based platform T3 Open Data Webinar, December 2013 Dave Barker, dbarker@mbta.com Manager of Operations Technology, MBTA

  2. MotivationVisionExecutionResultsResponseLessons

  3. The MBTA: • Serves 175 member cities and towns • Carries 1.3 million passengers each weekday • Operates heavy rail, light rail, commuter rail, bus, ferry, and paratransit • Extensive data sharing: GTFS, realtime, more Image credit: walkingbostonian.blogspot.com

  4. 2009-2012: Rapid development led to numerous feeds GTFS GTFS API Bus (NextBus) GTFS-realtime Bus (RealTimeBus) csv/json/xml Commuter rail csv/json Heavy rail 2.0 csv/json/xml Heavy rail 1.0 RSS Alerts 1.0

  5. 50+ Applications • Variety • Customer choice • Innovation • Mostly one subject each • Little integration • Contradictory information

  6. MotivationVisionExecutionResultsResponseLessons

  7. The MBTA-realtime vision Bus locations NextBus API (NextBus) Limited GTFS GTFS GTFS New MBTA-realtime software Com.rail predictions GTFS-realtime Subway predictions API (XML, JSON) Elevator status RSS (alerts only) Alerts thru GUI

  8. Phase I, June 2013 Bus locations NextBus API (NextBus) Limited GTFS GTFS GTFS (schedule only) New MBTA-realtime software Com.rail predictions GTFS-realtime Subway predictions API (XML, JSON) Elevator status RSS (alerts only) Alerts thru GUI

  9. MotivationVisionExecutionResultsResponseLessons

  10. Technical details • Designed and written by IBI Group for MBTA • C# application with Microsoft SQL Server back-end on two Amazon cloud servers • Based around foundation of GTFS data • Alert GUI • XML / JSON API, GTFS-realtime, RSS • Website, subscription service

  11. Alert GUI Today’s trains (per GTFS) Alert will clear after selected train scheduled to reach destination Text generated as you make selections

  12. Recurring alerts Details and URL

  13. Developer output & outreach

  14. MotivationVisionExecutionResultsResponseLessons

  15. MBTA to Customers (SMS, email, website)

  16. Developers to customers (web, apps, notification) Google Transit BOSRoadify

  17. Developers to customers (web, apps, notification) Embark ProximiT

  18. MotivationVisionExecutionResultsResponseLessons

  19. Customers #1 Complaint #2 Complaint I want fewer alerts! I want more alerts!

  20. Customers • Positive • - 30,000 subscribers • - Alert detail & precision • - Web page design • Negative • - Consistency • - SMS delays • Subscriber options

  21. Internal users Positive - Simple alerts are easy - Having accurate lists of trips, stops - Ability to review user actions Negative - Complex alerts are hard - Many audiences to consider at once(Alerts vs. website, email vs. SMS…) - Some repetitive actions

  22. Developers Positive - 100+ have registered to develop (!) - 30 of 65 polled “Plan to release app” - Alerts integrated quickly into some of the most popular apps Negative - RSS feed “good enough” for many - Many holding off until phase II (real-time) - No “T-Alert service killer” app yet

  23. MotivationVisionExecutionResultsResponseLessons

  24. Lessons • GTFS base successful • Development method worked well • Developer encouragement • Real-time information more fun for developers than alerts • The advantage of third parties

  25. Next steps • Real-time integration for subway, commuter rail • Twitter integration • Steps to reduce message volume and improve formatting • Encourage further development • Leverage the API ourselves

  26. Thank you Visit realtime.mbta.com for more. Acronym Reference - API Application Programming Interface - CSV Comma-Separated Value - GTFS General Transit Feed Specification - GUI Graphical User Interface - JSON JavaScript Object Notification - MBTA Mass. Bay Transportation Authority - RSS Really Simple Syndication - SMS Short Message Service - XML eXtensible Markup Language Dave Barker, Manager of Operations Technology, dbarker@mbta.com

More Related