The bottom right list displays operations assigned to the currently selected route.
Use each row to change properties of the operation. Additional columns can be added by right clicking on any of the column headers selecting Field chooser.
The following is an explanation of commonly used columns:
Double click on the field and select between the resources assigned to selected operation.
Double click on the field and enter the setup time for the selected operation.
If the resource does not have a resource calendar assigned, then a duration for the operation must be entered.
The workload is either constant or variable.
A variable workload can be entered in the capacity field. The workload is automatically calculated when the route is assigned to an order and the quantity of the order is entered.
If a constant workload is preferred the value must be entered in the workload field.
Double click on the field twice and enter the capacity.
The workload is calculated automatically when the route is assigned to an order.
Double click on the field. The Edit operation window opens. Edit the overlap at the bottom of the window.
The field shows if a split has been made on operations in the route.
This field shows which operation(s) the current operation depends on. I.e. what are the previous operation(s). If an operation depends on multiple operations a comma separated list of operation numbers will be shown. It is possible to edit this field. Thus operation networks can be edited “manually” instead of using the Constraint editor.
Hints: Keep the “Constraint editor” open while editing the “Depends on” column for better overview. If editing a specific route the Gantt chart will update as soon as the
A disabled operation is not shown or used during scheduling. I.e. initially create master routes with one or more disabled operations, which a user or a script, may enable in certain situations (or vice versa).
Important: constraint lines to and from disabled operations are not drawn in the Gantt chart – i.e. they are not visible. As an example if a route contains operations A, B and C and operation B is being disabled, then operation A and C are no longer connected visually with a constraint line.
Even though constraint lines are not visible, then during scheduling they will however still be respected. Consider the following route for a production order:
If operation “D” is disabled, then during scheduling “D” is seen as having a zero duration, however operation “E” will still respect the invisible constraint lines. As a consequence the result after scheduling will look like this
I.e. invisible constraint lines are respected during scheduling and operation “E” is scheduled to start after the completion of “A”. This may not be obvious to the user, since the blue dotted constraint lines are not visible. So unless a script takes care of e.g. removing or remapping the constraints, the functionality of disabling an operation is best supported for operations being first or last in the route or running in parallel with another similar operation.