Inserting an Operation and Closing Gaps
You use this finite scheduling mode for interactive planning with the detailed scheduling planning board or resource planning table if you want to create a gap-free schedule for a resource.
You can only use this scheduling mode for single-activity resources that are to be finitely scheduled. For more information about finite and infinite scheduling modes and resources, see Finite and Infinite Scheduling.
Do not use this scheduling mode in combination with the scheduling submode Plan dependent operations according to scheduling mode
, since the planning problems will then become too complex and could lead to performance problems.
If you set this scheduling mode, the system attempts to insert the operation finitely at the desired date/time (see Insert Operation). The system then tries to close all gaps in the resource schedule in the planning direction. The system does not change the sequence of the operations on the resources.
The system starts with the first gap in the planning direction, and then attempts to close the next gap, and so on. It cancels this process if it cannot move an operation, for example, because relationships to other operations can otherwise not be adhered to.
It is necessary to differentiate between the following cases:
Using the Scheduling Mode Without Block Planning
You can only implement this scheduling mode with a forwards planning direction. The system tries to close the gaps in the resource schedule up to the end of the planning period, if they are in the planning direction. The system begins by closing the gaps on the earlier of the following dates/times:
Original operation date/time
New operation date/time
Using the Scheduling Mode with Block Planning
You can implement this scheduling mode with a forward and backward planning direction. The system tries to close all the gaps that are in the planning direction of the resource schedule, up to the beginning or end of a relevant block. The system begins by closing the gaps for the forward scheduling or backward scheduling on the earlier or later of the following dates/times:
Original operation date/time
New operation date/time
The system does not close the following gaps:
A gap caused by changes to an order, for example, through changes the order quantity or deletion of an order
A gap caused by the deallocation of an operation
Note
Depending on the complexity of the scenario and the planning environment, the system is not always able to schedule the operation and close existing gaps even when the scheduling mode Insert and close gaps
is used.
Single-activity Resources