Transcript Document
RTD DENVER AND RIDECHECK PLUS Jonathan Wade Manager, Service Development Support Regional Transpiration District, Denver, CO October 16, 2014, Houston, TX STARTING POINT (~2003) APCs on… • 54 buses • 18 light rail vehicles INITIAL OBJECTIVES • Base routes and schedules on real, quantitative data to constantly monitor to improve the customer experience • Use best available database and consolidate data wherever logical • Constant and continuous incremental upgrades to data and systems • Easy-to-use for Service Planners/Schedulers/Analysts • A vendor with whom we could establish a partnership CURRENT SYSTEM STATUS (~2014) RTD Collection Staff 6 Service Monitors Laptops (ridechecks/pointchecks) 43 Street & LRT Supervisors Laptops (pointchecks) (Trapeze & TIES) (Hastus and TIES) Init Automated Passenger Counting System 2 Station Starters Desktop (pointchecks) 56 Commuter Rail (Future 2016) 42 LRT Cars 347 Buses (of ~ 1000) APCs (ridechecks) All with APCs (ridechecks) (of ~ 178) APCs (ridechecks) Ridecheck Plus CAD/AVL System LRT Factoring Survey Validation APC Validation Technician Schedule Adherence Data (INIT data 2013, ACS data pre-2013) Toad for Ad Hoc Reporting Bus and LRT Schedule Data & Bus Vehicle Assignments Commuter Rail Schedules & Vehicle Assignments Automated Analysis and Reporting Google Earth Ridership Maps TriTapt and On-Time Performance Schedule Adherence Reports Ridership Analysis Reports Ridership Analysis Maps IMPROVING THE CUSTOMER EXPERIENCE Scope of GIS and Schedule Data Changes • 3 Major run boards year (usually in August, January and May) • 30 to 50 revisions to each run board after voting • Minor changes: footnotes, running time changes • Major changes: rerouting, modifying operator run • 50-75 Special Services each year (scheduled in Trapeze) • Examples: Broncos Ride (football), Rockies Ride (baseball), etc. • About 1100 Special Service orders per year (scheduled in TIES) Bus stops defined Time points Trapeze scheduling CONSTANTLY MONITOR TO IMPROVE THE CUSTOMER EXPERIENCE Routing defined Bus stops defined TriTapt ontime performance analysis Other schedule data TIES DB for error checking, production and data collection INIT CAD/AVL /APC data collection Ridecheck Plus ridership analysis and reporting Can we improve the customer experience ? PERSUASIVE PRESENTATIONS OF DATA • • • The data is complete • Stop data • Ridership data The data is accurate • Passes all validation processes • Updated frequently The data is readily available • Uses know where and how to access the data quickly BENEFITS OF APPROACH • • • • Credibility, better decision making All stakeholders within RTD are working with the same data Reporting tool uses a variety of data sources Customers and operations benefit from accurate, timely schedule and GIS data FUTURE TASKS • Implementation of protected transfers and alternate pattern concepts (nearly complete) • Incorporate Special Services data into Ridecheck Plus (in progress) • Interface to a new scheduling software system (2015-2016) • Integration connected trips using fare media data (???)