Advanced Schedule Options

Advanced schedule options like resource allocation priorities and scheduling bucket specifications drive algorithmic decisions during schedule generation.

Configure Advanced Schedule Options

1. Select the resource allocation priority type, based on which the solver assigns work order operations to alternate resources.

   • If you select Earliest completion time, work order operations are assigned to resources that allow them to be completed relatively sooner.

   • If you select Changeover and idle time aware, work order operations are assigned to resources such that changeover and idle time is minimized locally.

2. Specify whether to use scheduling buckets.

   If the Use scheduling buckets setting is enabled, the schedule horizon is divided into buckets, and the scheduling bucket starts from the anchor date and time. If you enable this setting, you must also specify the scheduling bucket size.

   Note:

   To use buckets and the horizon extension is dynamic, your bucket must align with the fixed time fence, in that the end of the fixed time fence must match the bucket limit.

3. Specify whether to use accelerated dispatching.

   If the Use accelerated dispatching setting is enabled, the solver uses a simplified algorithm for faster dispatching, used in scheduling models where only one production stage is constrained and many work orders with same need-by dates have to be sequenced. This simplified algorithm might lead to lower overall solution quality in schedules with alternate resources or multiple production stages due to the trade-offs made to increase performance.

4. Specify whether to respect firm work orders within the fixed time fence.

   If the Respect firm work orders setting is enabled, the application schedules firm work order operations such that their assigned start dates will be respected throughout the fixed time fence. Production Scheduling might move firm work orders outside the fixed time fence to respect constraints.

5. Specify the duration of a scheduling bucket.

6. Select whether to prebuild relaxed upstream resources.

   If you enable this setting, operations on a relaxed upstream resource will be scheduled regardless of when operations on a constrained downstream resource are scheduled to begin. This means upstream operations can complete well in advance of when downstream operations begin. If you don't enable this option, upstream operations will be scheduled to complete just as downstream operations begin, or to their need-by date or need-by override if that happens to be earlier.

7. Specify a prebuild maximum duration.

   It's the number of days in advance of the Need-by Date, that a work order can be scheduled for. This duration determines the bucket to use for scheduling work orders that run on resources with a user-defined attribute sequence.

   Note:

   The prebuild maximum duration is considered only when scheduling buckets are used.

8. Select whether to use the anchor date as the horizon start date.

   If you enable this setting, the schedule horizon is no longer calculated from your local date and time but from the anchor date and time, making it constant. Then, the schedule data isn't affected by any differences between the anchor date and time and your current date and time. The past-due windows for both supplies and demands also stay constant with respect to the schedule horizon dates.

9. Specify the repair behavior you want to apply during manual scheduling.
   • If you select the Multistage checkbox, then the repair reschedules all work order operations in the work definition. This repair behavior minimizes the work order's make span but can lead to overlap of upstream and downstream operations with other work order operations. Multistage repair works well in scheduling models in which only the manufacturing stage on which you performed manual scheduling changes is constrained.
   • If you select the Single-stage checkbox, then the repair reschedules only work order operations that were modified during manual scheduling. This repair behavior is preferred if the work order has upstream or downstream operations that run on constrained resources. In some cases, the upstream or downstream operations are rescheduled to ensure start-after-end precedence constraints within the work order.
10. Select whether to prioritize the work order need-by date over the demand requested date.
    • If Prioritize work order need-by date over demand requested date is selected, Oracle Production Scheduling uses the work order need-by date for scheduling, even if a work order is reserved for a sales order. This can be helpful because the work order need-by dates already reflect strategic planning decisions made by Oracle Global Order Promising and Oracle Fusion Cloud Supply Chain Planning.
    • If Prioritize work order need-by date over demand requested date isn't selected, Production Scheduling prioritizes the pegged demand requested date over the work order need-by date.
11. Specify if the minimum transfer quantity maintained on work definitions should be used for schedule calculation.
    • If the Consider minimum transfer quantity for schedule calculation checkbox is selected, then the minimum transfer quantity, if defined on the work definition, is considered for schedule calculation.
    • If the Consider minimum transfer quantity for schedule calculation checkbox isn't selected, then the minimum transfer quantity won't be considered for schedule calculation.

Changeovers

1. Specify if changeovers should be inserted between operations with same attribute values.
   • If the Insert changeovers between work orders with same attribute values checkbox is selected, changeovers are inserted between different work orders even if their operation attribute values are the same.
   • If the Insert changeovers between work orders with same attribute values checkbox isn’t selected, then changeovers will only be inserted if the operation attribute values are different.
2. Specify if resource calendar and maintenance downtime during changeovers must be respected.
   • If Respect resource calendar during changeovers is selected, resource downtimes and maintenance are considered while performing production changeovers such as setups and cleanups.
   • If Respect resource calendar during changeovers isn't selected, production changeovers might be scheduled during resource downtimes and maintenance.
3. Specify the number of days in Look Ahead Window in Days. It's the number of days that Production Scheduling scans into the future to identify operations with the same attribute value specified in the resource parameter, Grouping Attribute for Changeover Reduction, to schedule them adjacently and reduce changeovers. This only applies when the user-defined attribute sequence functionality isn't used.

For more information on minimum transfer quantity, see the topic titled Minimum Transfer Quantity.