Hard Constraints
Hard constraints set the conditions that must be satisfied for a run or an event to be created or applied.
The following table explains the Hard Constraints.
| Hard Constraint | Constraint | Description |
|---|---|---|
| Exclude | exc | Do not create any runs that match the current conditions. |
| Exclude portion | Exc in Shift | Do not create portions (pieces) that match the current conditions. |
| Maximum of | max [value] | Set a maximum number of runs that match the current conditions equal to [value] or a percentage [value%]. |
| Minimum of | min [value] | Set a minimum number of runs that match the current conditions equal to [value] or a percentage [value%]. |
| Minimum average minutes worked | Mwk [value] | Increase the minutes worked as much as possible to meet the typed
minimum average. Note: This rule should be avoided because the algorithm will pad runs
with “spare” to attain the minimum required value (This “spare” will not be visible
in Blockbuster.) |
| Maximum average minutes worked | mwk [value] | The average (minutes worked divided by number of
runs)
will not exceed this value. Note: Additional
runs
may be required to meet this maximum average. |
| Set the maximum number of vehicles in garage | vmax [value] | The maximum number of vehicles that you do not want to exceed. |
| Set the minimum number of vehicles in garage | vmin [value] | The maximum number of vehicles that you do not want to exceed |
|
Set a maximum vehicle number or staff cars by vclass in garage |
vcap [value] | The maximum number by vehicle class or staff cars that you do not want to exceed. |
|
Set a maximum vehicle number at a place (node) |
pcap [value] |
The maximum number of vehicles that you do not want to exceed at a PLACE. |