 |
|
|
 |
Products > PSOP > Documentation
Handling Unavoidable Overload
In some situations overload simply can not be avoided. For example, the lawn project example introduced in the overview
has the following optimal schedule:
If we specify a project deadline of 3:00 pm it will be
impossible to complete the project by that deadline without the Cut Lawn and Edge Path activities
overlapping. Primavera P3e produces the following schedule for this project:
The above schedule has two hours of overload (the father resource is
overloaded by one unit between 8:00 and 10:00 am) although it is
possible to cut that overload in half while still meeting the deadline.
Why did this happen?
Unavoidable overload can occur for several reasons. It may
be that a single task all by itself causes overload. For
example, a task may require four welders when there are only three on
staff. Overload can also be unavoidable due to constraints,
relationships, and deadlines.
In the example above our deadline and the activity relationships made
it impossible to produce a schedule with no overload. If a task
cannot be placed
without introducing overload the P3e leveler will place the task
at its early start even when there is another time that results in less overload.
Note that it is possible that P3e will produce a schedule with overload, even when a schedule without overload exists (more information...). In these situations as well, P3e will place activities at their early starts rather than trying to minimize over-allocation.
How can PSOP Help?
When
overload cannot be avoided, PSOP still attempts to minimize it. Thus PSOP
produces the following schedule for the above example:
which has only one hour of overload instead of the two hours of
overload in the P3e schedule. For large projects with some unavoidable
overload, this can lead to significant improvements.
|
|
 |
|
