How to use the scheduling module

The basic approach

Run the algorithm via “Update schedule”.

Outperform Planning considers three time windows, potentially different per resource: ERP, scheduling, and planning window. All three windows span over an integer number of days which can be 0 for the first two windows. The planning window covers all days of the supply horizon after the end of the scheduling horizon. All three windows are considered consecutively, i.e., the day after the last day of a window is the start day of the next window. “Today” is the first day covered by the time windows, usually part of the ERP window.

The report “Resources” allows to set the window lengths by resource; it also shows up to which date the schedule was created in the latest run.

The scheduling algorithm uses all transactional inputs only related to the scheduling window, i.e., it ignores production proposals in the ERP window as well as planning window, irrespective of their source. If the scheduling window spans beyond the date the schedule was created last time, i.e., there is a time frame inside the scheduling window yet without a schedule, the next run of the algorithm will incorporate the consolidated production plan of that time frame as input.

The algorithm schedules the input only inside the scheduling window observing the constraints and objectives activated.

This process results in an initial schedule for the further refinement.

Use the UI to refine the schedule:

1. Use the reports “Schedule” and “Gantt chart” to manually move, remove, create and split batches.
2. Batches that couldn’t be allocated end up in the parking lot. You can unpark, i.e. allocate and schedule, them from there manually.
3. The menu option “Recalculate” moves batches on the selected day and resource such that they are executed back-to-back.

Set the batch status and repeat, if necessary

After moving a batch in the UI, you can set its status to “User allocated”, “User scheduled” or “User” by fixing its resource, its start time or both, respectively. When running “Update schedule” again, the algorithm is no longer allowed to change the fixed value(s).

Export

Tba, esp. ERP code and batch code connection

Implementation hints

Earliest start and latest end

ERP planned productions

The values for earliest start/latest end of ERP planned productions are set in query id="FC435E86-59E6-4F0D-934A-3253CCA8BAD1", name="Scheduling/Algorithms/Firm planned activities" in the two patterns "actual_earliest_start" and "actual_latest_end"

By default, these two patterns are filled by acnsupply.earliest_start_datetime and acnsupply.latest_end_datetime, respectively, but these columns are not filled in standard integrated’s integration, because their values are highly custom.

You essentially have two options:

1. fill these values in an sp_after_import_acn procedure and continue to use the standard version of the query or
2. modify the patterns mentioned above to your liking.

Batches created from the consolidated plan

The values for earliest start/latest end of production batches created from consolidation are set in query id=" 7399BE25-5D34-4528-92EC-9671EBC52C66",(more precisely in the underlying template id="0E0C75CB-3795-47DB-B388-B10F82C75BEB"), name="Scheduling/Algorithms/Consolidated activities" in the two patterns "actual_earliest_start" and "actual_latest_end"

By default, the former is null and the latter is the start of the first day of the first bucket after the bucket the batch was planned according to the consolidation. Here the only option for manipulation is option #2 from above.

Batches already scheduled

During the creation of a batch from ERP or consolidated the earliest start and latest end data as defined above is stored inside the batch and reused in all following runs of the algorithm.