Originally published on 11/25/2024
This service bulletin applies to agencies that utilize Optibus and Hastus for their scheduling packages when publishing a new schedule.
What's the issue?
This is to notify Optibus and Hastus scheduling package users of an issue that prevents drivers from logging in to certain runs/blocks due to deadhead patterns containing bad schedule data.
Like other patterns, deadhead patterns need to be set up correctly for a schedule publish to be successful.
Who's affected?
Optibus and Hastus scheduling package users that are publishing a new schedule.
What do I need to do?
Review your schedule packages before exporting the files to ensure your deadhead patterns follow these rules:
- All patterns require a minimum of two unique stops; it cannot travel from Stop 1 to Stop 1.
- All patterns must be at least 60 seconds in length.
- All patterns must start and end with a timepoint.
- All timepoints should fall on an exact minute; 60 seconds, 120 seconds, 300 seconds, etc. Based on that all patterns should end on an exact minute.
How do I request assistance?
As always, if you have questions or need any assistance, please don’t hesitate to contact the Avail Customer Experience Team either by submitting a case via the AvailTec Portal or for critical or high-priority cases by calling (814) 234-3394 option 1.
Thanks for partnering with Avail. We look forward to better serving you!