About Auto Driver Break Rules

Driver breaks can be automatically inserted into run itineraries by the system based on specific rules.

Rules should be defined according to your transit site policies. Using auto driver break rules reduces the number of manual tasks that must be performed by schedulers.

After you have defined the autobreak rules, they must be associated to runs on the Detail tab in the Runs screen. The autobreak activity is shown as AB in Schedule Editor so that you can differentiate between manual and automatically created breaks. If the breaks show a status of Ignore (IG), the system is prevented from sending the information to the Mobile Data Terminal (MDT) Center.

The following conventions are applied to autobreaks:

• The Schedule Server application inserts breaks for template and live runs.
• The system automatically moves an autobreak to a different position on the run in relation to other existing events. This is an advantage over manual placement of breaks.
• Breaks inserted manually maintain their positions on a run but may be subject to a Break Run (BrR) violation if they violate the parameters (for example, exceed the maximum number of breaks) of the autobreak rule that is assigned to the run.
• Breaks are not moved to a position on the run when passengers are on board.
• The assumed geocode of the break is inherited from the event that immediately precedes it; if you remove that event, the break gets a new geocode. This means that the geocode floats. Alternatively, a fixed location can be assigned to specific autobreak rules.