On-Time Performance in Live Map

Follow

A vehicle’s on-time performance (or schedule adherence) in the Live Map product is calculated as the vehicle’s expected time at a given point along a route vs the actual time. A vehicle’s on-time performance (or schedule adherence) in the Live Map product is determined by comparing the current time with the expected time for the vehicle to be at its current location according to the schedule.  Swiftly calculates this expected time by taking into account factors beyond the schedule, like historical data on how long it has taken vehicles to go from stop to stop. A vehicle’s “on-time performance” color on the Live Map is determined by on-time performance parameters that are specific to your agency. For example, your on-time performance standards could be 1 minute early / 4 minutes late – meaning that vehicles are considered "on-time" if they are less than 1 minute early and less than 4 minutes late, according to the schedule. 

This differs from on-time performance calculations displayed in the On-Time Performance product, which are based on the observed departure times from the stops or timepoints as compared to the schedule.

 

How does Swiftly make these specific predictions for "adherence"?

The Swiftly platform considers a combination of factors to generate the vehicle’s schedule adherence in the Live Map, which includes:

  • historical data on how long it has taken vehicles to go from stop to stop (travel times)
  • current conditions, such as speed and current location
  • A vehicle's schedule adherence at the most recently departed stop

These factors allow Swiftly to create very accurate predictions of when vehicles will arrive at forthcoming stops, and then calculate the current schedule adherence.

Stop Times v.s. Timepoints

All schedule adherence calculations will display the vehicle’s expected arrival time to the next stop unless the vehicle’s next stop is an operational timepoint.  If a vehicle's next stop with a scheduled time in GTFS is an operational timepoint that has distinct scheduled arrival and departure times, the expected time for the vehicle's current location takes this difference into account.  Swiftly references the scheduled arrival for early vehicles and scheduled departure for late vehicles.  If the next stop is designated as an operational timepoint in the GTFS, the system will assume the vehicle will wait there until its scheduled departure time. 

 

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.