Avail is designed to support fixed route service. Fixed route service, by definition, is a digitized, predictable schedule which transit vehicles follow, servicing scheduled stop locations with scheduled departure times. Passengers rely on fixed route service for their travel needs: Example: "I catch the bus to go to work at 7:15 am Monday - Friday. I love that I always know the departure times for 3rd & Main St. on myStop, so I can plan my travel needs easily."
How Does a Fixed Route Schedule Work?
Vehicles are installed with GPS, so we know location and time as the vehicle traverses its schedule. The digital schedule includes designated roads and stop locations that are based on latitude and longitude. When vehicles arrive and depart stops, the system records vehicle activity. When vehicles deviate from their scheduled roads/stops, the vehicle is considered 'off route'.
Below is an example of a vehicle's 'breadcrumb trail', generated via the Replay Tool, which is located in Geographic Tools:
Deviated Fixed Route Service Types:
Best Practice: Avail recommends that agencies always use fixed route service to best serve passengers and for robust reporting metrics, however, agencies often ask how the Avail system supports deviated fixed route service. The definition of deviated fixed route varies, and can include:
- on-demand service
- off-route request stops
- off route request pickups
- other special un-scheduled service
There are workarounds in the Avail system when an agency determines that deviated fixed route service is necessary. Please note that deviated service will affect your reporting metrics. Below are a few options:
Service Options and Effects:
The first option is to schedule the most frequent path of travel as if it were fixed. When the vehicle follows that most-frequent path, no action is needed (the system works normally). When the vehicle deviates, you will see the following effects:
- The driver will see the MDT showing off-route
- Depending on the deviation and next stop, the driver may need to manually announce, manually flip the headsign, and/or manually select a trip
- Dispatch and passengers will see the vehicle as off-route (dispatch map, myStop applications)
- The agency must enter an adjustment for the deviation in order for NTD actual miles and hours to be correct for your reporting needs
- Various reports can be affected: depending on the type of deviation used:
- Your 'Schedule Health' report, which identifies scheduled but missed stops, timepoints and/or trips) could be broken
- Your 'OTP' reports (on time performance, which is based on scheduled timepoint departures) could be impacted negatively
- Your 'Running Times' report, which is used for schedule improvement, would have less value (since some timed segments (stop to stop distances) would show normal operation and some would show missed/deviations)
The second option is to leave a portion of service unscheduled (e.g. not included in the digitized schedule data software) and perform the service as-needed. This has all of the same results as the above option with the following additions:
- The agency must create an adjustment for the service performed (since there is no “normal” fallback plan)
- Passenger information will not indicate that service is available in that area/time since it is not included in the digital schedule
- Any miles/ hours will be included but undefined in your reporting metrics since the service is not included in the digital schedule
The third option is to create a Special Event. To create a Special Event, an agency must submit a request in the Avail Customer Portal.
- With a Special Event, the driver is given a special run ID to log into. The vehicle headsign can be set automatically and dispatch sees the vehicle information/location on the dispatch map, as with any other vehicle logged into revenue service
- However, since there is no schedule data there are not “next stops” or other driver prompts on the MDT
- Special event service does not display on your myStop applications/passenger information and is not available for trip planning
- Fare entries, if used, are manually added for Special Service in DataPoint. Vehicle operators often use tally sheets to document fares. Fare collection information should be handed off to whomever manages exceptions processing/DataPoint System Adjustments to add the fare entries. Need information about manual fare entries? Click here to review the process.
- The agency is required to enter adjustments in DataPoint for each Special Event performed in order for your NTD S10 reporting metrics to be correct.
On your myStop application used by your ridership base, it will negatively impact real-time departure estimations and therefore will impact rider satisfaction.
Best Practice is to include all known service in your digitized scheduling package as 'Fixed Route' service, where possible; to ensure schedule visibility for rider satisfaction, and to capture better reporting metrics for your agency reporting needs.