 |
|
|
 |
Products > PSOP > Documentation
Splitting Work in
Progress
If the lawn mowing example project from the overview is updated with progress like this:

and the project is leveled using default options, Primavera P3e produces the following schedule:

Notice that the Edge Path activity is split in half.
Why did this happen?
The blue line indicates the date and time the project was last
progressed. Since things are progressing as expected, we're
halfway done with the Edge Path
task. The completed work on this task is shown in blue while
the remaining work is shown in green.
As explained in the overview,
Primavera's
default leveling priorities don't produce an optimal schedule for this
project. In addition, P3e has split the Edge Path task.
This new schedule asks us to stop edging the path and start
cutting the lawn. We are
scheduled to resume the edging task at 3:00 pm. It is often impossible,
or at least inconvenient, to split a task up in this way. The
only
way to avoid this with P3e is to add constraints
(mandatory dates) to all tasks in progress. Although we could do
this with the lawn mowing example, it would be very time consuming for
a project with hundreds of tasks.
As projects progress, things often change (tasks get longer or shorter
and the availabilities of the resources change, for example). As a
result, it is common
to
level a project after updating its progress in order to schedule the remaining
work as efficiently as possible. However, using Primavera's
default leveling options, this can cause the above unexpected behavior.
How can PSOP Help?
By default, PSOP will emulate the P3e behavior and may split activities which are in progress. However, if you select Don't split in-progress
tasks on the Primavera Compatability tab in the main window, PSOP will not split activities which are in progress.
We recommend using this option because even when activities
can be split, there is usually a cost to transfer workers, tools,
and materials from one task to another.
|
|
 |
|