Brooke Fossey, Transportation Planner

Transcription

1 Brooke Fossey, Transportation Planner

2 The Circulator Dashboard Making Bus Performance Data Accessible, Transparent, and Effective

3 Circulator Bus

4 DASHBOARD PURPOSE AND NEED

5 Purpose Open Government Initiative on Dashboards: enable agencies, public, and stakeholders to view performance details provide information on effectiveness of government programs support decisions on investment and management of resources strengthen public trust Circulator Dashboard created to: advance government transparency and accountability facilitate data-driven decision-making improve information availability to the community engage the public on operations, routing, and safety identify areas needing improvement highlight success for replication

6 METRIC SELECTION

7 Best Practices Transportation Research Board (TRB) Guidebook for Developing Transit Performance Metrics: Avoid overwhelming with too much data. Strive for variety, but guard against superfluity. Upper limit of around 20 metrics.

8 23 Metrics Selected Ridership Total ridership Average ridership by day of week Riders per revenue hour Safety Total accidents Total injuries Accident rate (per 10,000 miles) Injury rate (per 10,000 miles) Customer Service Percent on-time under 15 minutes On-time performance (<7 min, 7-11 min, min, >15 min) Customer comments (complaints and commendations) Fleet Performance Vehicle reliability (miles between breakdowns) Vehicle availability by day of month (by vehicle length and model year) Finance Cost Revenue Subsidy Cost per rider Revenue per rider Subsidy per rider Revenue hours Revenue miles Farebox recovery Fare Media Payment type by SmarTrip card Fare media (percent of riders by payment type)

9 DASHBOARD DEVELOPMENT

10 Identify performance metrics Maintain and continually improve the Dashboard Identify type of graph for each metric Launch Dashboard publicly DESIGN PROCESS Create stored procedures in SQL server for each metric based on time parameters Test results Design user interface Gather and enter data

11 Development Process Users only need internet browser (e.g. Explorer, Firefox, or Safari) and free downloadable plug-in for Silverlight. circulatordashboard.dc.gov $5,000 2 part-time staff 6 months to create

12 Technology Visual Studio 2010 and Silverlight 4 selected for Dashboard platform DDOT s IT division s main development environment is Microsoft.NET framework C# and VB.NET are the main development languages using Visual Studio Microsoft Silverlight provides a rich user experience and allows controls and such as charts and animation

13 FUNCTIONALITY

14 Internal Data Entry Interface

15 Internal Data Entry Interface

16 Dashboard Main Page

17 Dashboard Metric Page

18 Dashboard Metric Page

19 APPLICATION

20 Link to Policy & Planning DDOT is using the Dashboard to review route performance to improve on-time performance, operational efficiency inform short-term decision-making, adjust resource allocation, and justify decisions about route planning/operations inform long-term planning efforts» 2010 DDOT Action Agenda (2-year plan): improve on-time performance to 90% of buses arriving with <11 minute headways.» 2011 DC Circulator Transit Development Plan (10-year plan): use Dashboard to set performance goals and objectives that guide the future growth of the system. Vital feedback loop linking performance, policy, and planning

21

22 LESSONS LEARNED & ONGOING IMPROVEMENTS

23 Lessons Learned 1 Technology: inexpensive vs. customizable. Silverlight free but requires download. 2 Usability: parameters vs. dynamic. Downloading format issues, Silverlight limitations. 3 Data entry: Electronic vs. hardcopy data.

24 Ongoing Improvements - Finesse download function - Add targets to all metrics - Allow copying/pasting - Pre-store some data in internal interface - Allow all routes comparisons across metrics

25