business i ntelligence development at winnipeg transit
play

Business I ntelligence Development at Winnipeg Transit Bill Menzies - PowerPoint PPT Presentation

I TS Canada Webinar February 28, 2013 Business I ntelligence Development at Winnipeg Transit Bill Menzies Senior Transit Planner, Dillon Consulting Limited Manager of Service Development, Winnipeg Transit (formerly) Transit Service Management


  1. I TS Canada Webinar February 28, 2013 Business I ntelligence Development at Winnipeg Transit Bill Menzies Senior Transit Planner, Dillon Consulting Limited Manager of Service Development, Winnipeg Transit (formerly)

  2. Transit Service Management Decision Information Service Action Plan Service Consolidation Delivery Data Analysis 3

  3. Data Consolidation for Analysis TSAS Database GI S Geography Network, Schedule, Schedule Cost Files (SAS) Service Costs Transit Cost Model Bus Run Fleet Assignment NETData Files (SAS) Dispatch MMI S Contact On-TRAC Operations APC Files APC Utilization (DB2) 4

  4. Transit Network Definition • Booking • Route • Route Direction • Trip Pattern (Leg) • Segment • Defined by contiguous timing points • Common stop sequence • Bus Stop • Service Access/Egress • Timing Point • Transfer Point • Relief Point 6

  5. Utilization: APC System • Automatic Passenger Counting System • Boardings/Alightings by Stop • Loads Between Stops • Arrival/Departure/Dwell Times at Stops and Timing Points • Actual Running Times Between Timing Points • Service Delays • 183 buses equipped (33% of fleet) • 28 x 40’ High Floor (New Flyer D40) • 150 x 40’ Low Floor (New Flyer D40LF) • 5 x 30’ Low Floor (New Flyer D30LF) • 3 service lines at 2 garages equipped 10

  6. Data Consolidation • Goal is to consolidate key data from different systems to support analysis, planning, and management of transit service • What’s needed: • Data interfaces for major applications • Software that can read a variety of database formats • End user programming skills • Internal computer network for data access • Intranet site for report publication 14

  7. The TSAS Warehouse APC Diagnostic Reports Network & Schedule Service Trip Samples Database Supply Reports Utilization Dispatch Reports Bus/Run Assignments Trip Sample Passenger Database Programs Status Count Reports SAS Trip Productivity Service Evaluation APC Reports Run Sample BusStops Status Schedule Database Adherence Run Times Reports Run Time Service Trip Recovery Data Files for Cost Status HASTUS-ATP Database 15

  8. Performance Metrics

  9. System-Based Metrics • Dispatch • Schedule Adherence • % of scheduled service • % of departures within actually operated window: • 1 min early to 3 min late • % of designated service operated by designated • Measured only at stops with buses boardings • Low Floor Routes • Weighted by boardings • Downtown Spirit Routes • Bike Rack Routes • BRT Routes • System Ridership • Average Daily Boardings by: • APC Data Recovery • Booking Type • % of APC-operated trips for • Schedule Type which data successfully • Year recovered 18

  10. Route-Based Metrics • Schedule Adherence • Trip Productivity • % of departures within • Average Boardings window: • Boardings/Bus Hour • 1 min early to 3 min late • Maximum Load/Seated • Weighted by boardings Capacity • % of Seat-Kms used • Running Times/Speed • Average pgr trip length • Mean, Standard Deviation • Service Frequency • Crowding • Scheduled Headway vs. • At trip maximum load point, Demand – Based Headway % of passengers: • at each route’s maximum • Seated load point • Standing (comfortable) • By schedule type, time • Standing (uncomfortable) period, and route direction 19

  11. Stop-Based Metrics • Passenger Activity • Schedule Adherence • Ons/Offs/Load by: • % of departures within • Booking window: • Schedule Type • 1 min early to 3 min late • Time Period • Weighted by each • Route passenger trip’s boardings 20

  12. Service Evaluation - Supply 40 seats 0 Min 1000 m 1000 m 1000 m 1000 m 1000 m 45 Min Bus Hours = 0.75 Bus Kms = 5 Seat-Kms = (40 seats * 1,000 m)/ 1,000 m) * 5 = 200 21

  13. Service Evaluation - Demand 40 seats 45 25 20 15 17 2 8 3 0 30 22 2 0 15 5 0 5 0 Min 1000 m 1000 m 1000 m 1000 m 1000 m 45 Min Ons = 52 Offs = 52 Max Load = 45 Pgr-Kms = ( (5* 1000)+ (20* 1000)+ (25* 1000)+ (45* 1000)+ (15* 1000) ) / 1000 = 110 22

  14. Service Evaluation - Metrics 40 seats 45 25 20 15 17 2 8 3 0 30 22 2 0 15 5 0 5 0 Min 1000 m 1000 m 1000 m 1000 m 1000 m 45 Min Boardings/ Bus Hour = 52/ 0.75 = 69 Boardings/ Bus Km = 52/ 5 = 10.4 Pgr-Kms/ Bus Kms = 110/ 5 = 22 (Average Load) Pgr-Kms/ Seat Kms = 110/ 200 = 55% (Load Factor) Pgr-Kms/ Boardings = 110/ 52 = 2.12 (Avge Pgr Trip Length) 23

  15. Service Evaluation - Metrics • Balanced Scorecard • Route Peer Comparison Performance Measures • Routes compared • • Boardings/Bus Hour within category: • Boardings/Bus Km • Downtown Main Line • Average Load • Express • Load Factor • Crosstown • Complete Route • Neighbourhood Feeder • Peak Direction • Downtown Spirit • Average Trip Length • DART Cost Measures • • Variable Cost/Boarding • Full Cost/Boarding • Variable Cost/Bus Hour • Full Cost/Bus Hour 24

  16. Service Evaluation - Example Daily Category Daily Costs Performance Cost Schedule Service Measures Measures and Route Operated Demand 25

  17. I nformation Delivery

  18. What, How, For Whom? • On-Line Reports • Generated daily at 05:00 • Designed for quick reference by all staff • Detailed Paper Reports • ~ 30 standard reports generated on demand for planning/scheduling purposes • Evaluation Reports • Generated at end of each booking to track system ridership, route productivity, demand-based headways, service costs • Restricted circulation • Data Extraction for Input to Other Applications • Observed run time data for HASTUS-ATP analysis • Spatial data for GIS analysis 27

  19. On-Line Reports 28

  20. System Schedule Adherence 29

  21. Route Reports 30

  22. Stop Reports 31

  23. GI S – Load Profile 34

  24. Next Steps • Integrate data from new ITS deployments into TSAS: • Automatic Vehicle Location System (2010) • Generates second-by-second log file of each bus’s operation each day • Electronic Passenger Information Systems (2011) • Trip planner, IVR, mobile, and SMS apps generate travel pattern data • Fare Collection System (2013) • Generates spatially-referenced fare payment and transfer data • Develop management dashboard of key operational and performance measures 35

  25. Thank You!

Recommend


More recommend