The On-Time Performance (OTP) product gives insights into your transit system’s historical schedule adherence. By understanding where vehicles are scheduled to be versus where they actually are throughout their trips, Swiftly accurately identifies when and where vehicles are early, late, and on time. In the OTP product, you can view overall schedule adherence performance over a particular date range or narrow in on a particular route to understand where routes become problematic - at specific stops, during certain time windows, or both - so that you can make informed decisions about how to triage and resolve schedule and planning issues.
Note: Swiftly looks at stop departures for the on-time performance product.
The Basics
Summary Overview: You can view the overall on-time performance across all stops and routes for your transit system. Also, you can view changes and trends to your on-time performance over the past 6 months. The Data Completeness chart in On-Time Performance helps put performance data in context. While the On-Time Performance summary chart shows the percentage of observed stops that were on time, late, or early, the Data Completeness chart shows how that fits into the full picture of your scheduled service.
Filters: In the On-Time Performance product, you can look at data for your whole system, or hone in on a specific route's performance. You can also look at performance for a single day or over a longer date range. You can exclude dates that may impact on-time performance (snow days, events that disrupt service, etc.). Lastly, you can adjust on-time performance parameters--these changes will persist in other products during the current dashboard session, but any setting changes will reset when you log in again.
Stop Handling: Swiftly supports stop-level OTP configurations as a way to reflect what is happening in the real world. For example, we know there are stops (such as on commuter routes, or the last stop of a trip) where it may not make sense to penalize early arrivals. As stop-handling is typically done at the agency level, in order to change these parameters, please contact support@goswift.ly.
Swiftly can handle last stop performance in three ways: (1) including last stop arrivals in performance reporting normally, (2) including them but treating early arrivals as on-time, or (3) simply excluding last stops from the data sample entirely.
Swiftly can handle drop-off only stops in three ways: (1) including drop-off only stop arrivals in performance reporting normally, (2) including them but treating early arrivals as on-time, or (3) simply excluding drop-off only stops from the data sample entirely. Drop-off only handling needs to be configured in GTFS in the stop_times.txt file using pickup_type=1 (no pickups). Stops denoted as drop-off only will flow through to Swiftly. Please contact support@goswift.ly if you could use assistance setting this up.
Routes Overview: You can view on-time performance for all routes or specific routes. If you select a single route, you can view OTP by stop, by time of day, by severity (histogram), or at the granular schedule level. Need to quickly see OTP for a specific group of routes in the dashboard? Learn more about accessing route groups.
Own your data: When you use Swiftly, we help process and display your data in ways that help isolate problems, but at the end of the day, the underlying data is always yours. You can easily export the underlying data we use to generate charts in our dashboard to CSV so you can merge with other data sets or run your own analyses.
Take On-Time Performance Beyond the Basics
Swiftly Customer use Cases:
- Speeding Up Transit and Project Timelines at Santa Clara VTA
- How Juneau Is Wooing Cruise Ship Passengers with a Transit Rebrand
- Swiftly Restores Transit Calm on the Oregon Coast
Customer Community Training Webinars:
Comments
Article is closed for comments.