The Optional layover feature is not commonly used. It’s a special type of layover where the operator will drive the vehicle away from a trip change stop location earlier than the scheduled next trip departure time because they are not permitted to remain at the trip change stop location for the entire time between their arrival time and the next trip departure time.
In this situation, the vehicle operator will drive the vehicle to an alternate layover location and wait. When the optional layover is complete, the driver returns to the trip change stop, performs any passenger services, and then departs on time at the start of the next trip.
Drivers should not depart early at the start. If they do, the trip will be marked early and negatively impact the on-time performance metric of the agency.
If configured for Optional Layover, the myAvail system operates seamlessly through the layover and trip change events:
- Trip information is updated correctly for the MDT, headsign, and farebox.
- Stop announcements play at the correct locations.
- Passenger counting is collected and reported correctly.
When Optional Layover is enabled in the myAvail system, only trip changes with a large enough scheduled gap (layover or make-up time in the trip as scheduled) are eligible.
The workflow graphic below illustrates each use case for vehicle operators:
Green: The “pros” for the action selected. Good habits for your vehicle operators and the expected transit data will be captured
Yellow: These are up to the agency to decide if they are okay with this operationally.
Orange/Red: The “cons” for the action selected. This could result in operator headache or transit data loss. This is not the end of the world or a showstopper, just an impact to be aware of.
Vehicle Operator SOP: Vehicle Operator SOP 021: Perform Revenue Service