Production > Capacity planning > APS > Work with APS > Parallel operations and overlapping - robinfeng/beashelp GitHub Wiki

Navigation: Production > Capacity Planning > APS > Work with APS: Parallel Operations and Overlapping No contents entries on this page Contents Using overlap settings, you can delay the subsequent work sequence or start it in parallel. Unlike parallel resources, the subsequent work sequence can be moved freely.

An overlap is specified in hours – based on a 24-hour day. The specified overlap always applies to the following routing position. The overlap time is not bound to a resource calendar. This is a pure hour-based time excluding time reservations or other factors. The overlap time begins AFTER the transfer time. The next routing position cannot possess a transfer time, otherwise this will be appended to the transfer time.

Special values Value Meaning 0 No overlap -1 Parallel

0 Overlap of the following routing position or assembly if it is the last routing position.

Example: Parallel editing |----Pos 1---| |--- Pos 2---| |---- Pos 3 ---|

In this example, "-1" was entered for the overlap limit in routing position 1, whereby routing position 2 was set in parallel with routing position 1.

Example: Overlapping |---- Pos 1 ---| |--- Pos 2---| |---- Pos 3 ---|

In this example, a number > 0 was entered for the overlap limit in routing position 1

help-achtungNote: The user must take care to enter the data in such a way that the result makes sense. beas does not check the inputs for correctness. see also "Different lead times" in this chapter.

Clocking mandatory If an overlap limit is entered, the "Clocking mandatory" option is automatically deactivated. This is the only way to make it possible for the next overlapping routing position to also be reported. If "Clocking mandatory" is re-activated, the overlap limit is automatically set to 0. Important: the last operation corresponds to the last "reportable operation". If an overlap is also configured in the last operation, beas does not recognize this as the last operation. However, the automatic assembly receipt or adjustment of the backflushed material depend on this.

Scheduling Direction Overlaps can ONLY be displayed correctly in forward scheduling. In backward scheduling, scheduling is always performed as late as possible, i.e. what is the latest possible time that the preceding routing position can be started, taking the overlap into account.

hmtoggle_plus1 Example forward scheduling

In this example, the first 3 operations are parallel

|----Afo 1---| |- Afo 2-| |--- Afo 3---| |---- Afo 4 ---|

Incorrect constellation, if worked on different resources |----Afo 1---| |--- Afo 2---| |- Afo 3-| |---- Afo 4 ---|

Operation 4 starts after operation 3. If an order is split to three operations, this behavior is correct. If the order is to be kept, please make sure that operation 3 has the longest lead time, you can achieve this by entering a longer overlapping time.

hmtoggle_plus1 Example backward scheduling If parallel operations have different lead times, the operation with the shortest lead time starts latest possible, to make sure all parallel operations have the same end date.

|-- Afo 1 --| |----Afo 2---| |- Afo 3-| |--- Afo 4---| |---- Afo 5 ---|

Please consider, that lead times of parallel operations are equal or that the operation with the largest lead time is at first position.

Idle time and transit time Idle time and transit time are included into processing time. Calculation: Transit time + Processing time + Idle time Important: even if operations are executed in parallel, for transit time determination the order of operations is taken into account. hmtoggle_plus1 Example: Op 1 = Machine1 Op 2+3 = Machine 2+3, parallel Transit time machine1 = 4 hrs., Machine 2+3 = 2 hrs.

Calculation |-- Op 1--| |- 4 hrs. transit -----||- Op 2 -| |- 2 hrs. transit -||- Op3 -|

Overlapping using assemblies Assemblies can also overlap in an order-related structure. Example: |- Main assembly -| |--- Subassembly -|

Start date of the main group is normally the end date of the last routing position of the subassembly. If this last routing position has an overlap, this is also considered. Important: If an overlap is entered in the last routing position, this is no longer recognized as the "last routing position" in the backflushed posting transactions.

返回 主页