Adding Constraint Rules

Constraints are added as ancillary data and applied to selected sign-up periods and divisions.

Conditions rules define the set of shifts for which a constraint is valid. They are used in the construction of driver schedules.

All of the conditions that take more than one value after a singular keyword can be considered as logical OR, that is, a Boolean function, which is true only if at least one of the values match.

If the keyword is plural, then the condition is considered as logical AND, that is, Boolean function, which is true only if all of the values match.

Some condition rules allow for the opposite of the condition. In these cases, type “not_” prior to the keyword, for example, not_def.

  1. Click Ancillary > Block Optimizer Constraint Parameters.
    The Constraint Parametersscreen appears.
  2. Press F3.
    The Context dialog appears.
  3. Select the appropriate sign-up period.
  4. Click OK.
  5. Perform one of the following steps:
    • Click Data > Add New .
    • Click the Add New button: Add New button
    The Global Constraint Details dialog appears.
    Global Constraints dialog
  6. In the Abbr field, type the abbreviation for the constraint.
  7. In the Name field, type the name of the constraint.
  8. In the Constraint drop-down list, select a keyword. (For more information on the keywords, contact your Trapeze representative.)
  9. In the blank field beside the Constraint field, type or select a value that you want to apply to the selected constraint.
    For Soft constraints, the value must be a single character (any alpha character). The constraints appear as user-defined options under Miscellaneous > Miscellaneous > Options in the Block Optimizer Parameters tab as shown in the following sample graphic.
    Sample soft constraint shown as user-defined option.
  10. (If applicable) To add Condition Rules, click a field in the left column and from the drop-down list, click the keyword of the condition rule you want to apply. For example, you may want to add exceptions when a constraint does not apply.
  11. In the blank field beside the selected keyword, type an appropriate value.
  12. Click OK.

The constraints are held in a separate file and attached to run types as required. This allows for local agreements as applied to specific schedules (for example, inclusion of maximum work time on a route or not being able to mix routes).