Using overlapping operations
You can configure the Planner to allow an operation to start before the previous operation has completed. The JS19VR.OLTYPE and JS19VR.OLVALUE fields define how the Planner calculates the start time of the overlapping operation.
During a planning run, the Planner calculates the time horizon in which to schedule an operation in the plan (the JOBPLAN.STARTDATE/ENDDATE fields). On a push-planning run, the Planner checks the previous operation's OLTYPE field for a value other than 0.
If OLTYPE is enabled, the Planner uses the rules in the OLTYPE and OLVALUE fields to calculate the number of hours after the start of the first operation to start the second operation. This calculation is based on the OLTYPE rules shown below:
| OLTYPE | Rule |
|---|---|
| 0 | No overlap |
| 1 | Start overlap window after setup and cycle time for OLVALUE items has completed |
| 2 | Start after OLVALUE percent of setup + cycle time have completed |
| 3 | Start after OLVALUE percent of cycle time has completed |
| 4 | Start after OLVALUE hours of setup + cycle time have completed |
| 5 | Start after OLVALUE hours of cycle time have completed |
The Planner moves back the second operation's horizon to reflect this overlap. It then makes further adjustments to the horizon based on the following circumstances:
-
Considers that the first operation may split across breaks for other operations (the cross-breaks rule is defined in the JS19VR.CRSBRKRL field) and makes the necessary adjustment.
-
Ensures the second operation does not end before the first operation. If the difference between the second operation's new start date/time and the first operation’s end date is greater than the total duration of the second operation, the Planner adjusts the horizon again so the second operation cannot finish before the first operation.
If you run the Scheduler after running the Planner, the Scheduler performs its overlap processing based on the same OLTYPE codes. For more information, see Chapter 2, "About the Scheduler."