There are many ways to expand and compress a work order along the timeline.
Priority
Priority can influence transit time and utilization.
Transit Time
|--- Transfer time --| |-- Plan time --| |--- Idle time ---|
You can specify the % of transit time to be considered.
For example, if you input 50%, the transit time is compressed to 50% and the lead time reduced accordingly.
Utilization
You can use the utilization to specify the % to which an order can be dispatched to a resource.
Example 1.
Resource has 8 hours / day and consists of one machine. No other time reservations. 10 hours are to be dispatched, utilization is set to 100% (default).
Day 1 Day 2 |--------| |--------|
Order |********| |**------|
The order is dispatched for 2 days here.
At 150% utilization this would look as follows:
Day 1 Day 2 |--------| |--------|
Order |**********| |--------|
In this case, simply more is dispatched on day 1 than is available. An overload up to 150% would occur here. The shift definition for the resource is adapted here order-specifically: Instead of 8 hours, the program then assumes 8 * 150% = 12 hours, i.e. from 6am to 6pm instead of 8am to 4pm.
Example 2: Expansion
Utilization at 50%
Day 1 Day 2 |--------| |--------|
Order |--****--| |--****--|
For the calculation of this order, the shift definition is changed here to 12 - (8 : 2) = 8am to 12 + (8 : 2) = 4pm Therefore, only 4 hours are available per day and the throughput is expanded accordingly.
|
Expansion / compression by resource allocation
The priority always refers to the overall production order. If only one operation should be expanded, the "Resource Allocation" option is available. This value can be specified in % or number of machines/persons per resource.
Example 1:
1 machine on the resource, 8 hrs/day, work sequence with 10 hours, default resource allocation
Day 1 Day 2 |--------| |--------|
Order |********| |**------|
Changing the resource allocation to 200%
Day 1 Day 2 |--------| |--------|
Order |xxxxx---| |--------|
The shift definition is not changed here; each x corresponds to 200% utilization This results in an overall utilization of 200% in the first 5 hours. The throughput time is reduced accordingly.
It is reduced to 50% for expansion
Day 1 Day 2 Day 3 |--------| |--------| |--------|
Order |oooooooo| |oooooooo| |oooo----|
The shift definition is not changed here; each o corresponds to just 50%. Another position can thereby be dispatched in parallel to this position.
Example 2:
2 positions with 10 hours each, 1x with 50% resource allocation and 1x 100%
Day 1 Day 2 Day 3 |--------| |--------| |--------|
Order1 |oooooooo| |oooooooo| |oooo----|
Order2 |******--| |****----|
Order 2 is dispatched to 75% in the first day, but to 100% at 6 hours. Reason: Beas always calculates: daily capacity minus allocated time (8*25% = 2 hrs, 6 free hours remain) On the second day the remaining 4 hours are scheduled to 100%.
Note: Expansion and compression is not possible in Detailed planning. The program switches automatically to calculation method Exploit full capacity. |
See
Resource - Planning - Planned capacity