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. Motivation Vision Execution Results Response Lessons

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

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

6. Motivation Vision Execution Results Response Lessons

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

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

9. Motivation Vision Execution Results Response Lessons

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. Today’s trains (per GTFS) Alert will clear after selected train scheduled to reach destination Text generated as you make selections Alert GUI

12. Recurring alerts Details and URL

13. Developer output & outreach

14. Motivation Vision Execution Results Response Lessons

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

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

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

18. Motivation Vision Execution Results Response Lessons

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

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

24. Motivation Vision Execution Results Response Lessons

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

26. 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

27. Thank you Dave Barker, Manager of Operations Technology, dbarker@mbta.com Visit realtime.mbta.com for more. Acronym Reference - APIApplication Programming Interface - CSVComma-Separated Value - GTFSGeneral Transit Feed Specification - GUIGraphical User Interface - JSONJavaScript Object Notification - MBTAMass. Bay Transportation Authority - RSSReally Simple Syndication - SMSShort Message Service - XMLeXtensible Markup Language