 |
|
|
 |
Products > PSOP > Documentation
Honoring Constraints
Consider the lawn mowing example project introduced in the overview.
Suppose the edging tool has been borrowed from a neighbor and has to be
returned by 11:00 am. We therefore add a finish on or before
constraint to the Edge Path
activity indicating that it must be completed by 11:00 am.
We then level using P3e's default leveling options but un-check level resource only
within activity total float
(checking this option will force the whole project to finish by 1:00,
which may not be required). P3e produces the following schedule:
which violates the finish on or before constraint we just added.
Why did this happen?
Leveling within total float in P3e means
that the project deadline must be honored. If there is no project
deadline however, this forces the project to complete as soon as
possible and this severely limits the leveler. Even if a
deadline has been
set, it may be desirable to ignore the deadline to see how much
overload can be reduced by scheduling beyond the deadline. With the P3e
leveler, however, finish on or
before and start
on or before constraints are ignored if you do not level within total float.
How can PSOP Help?
In order to emulate P3e, PSOP will also ignore finish on or
before and start
on or before constraints by default (regardless of the leveling options). If you check Enforce constraints
ignored by Primavera leveling on the Primavera Compatability tab all constraints will be honored.
We recommend using the Enforce constraints
ignored by Primavera leveling
option, but when this option is selected you should be careful not to
add unnecessary constraints to your project. For example, putting a finish on or
before constraint on a milestone
activity that marks the end of the project is unnecessary since you can specify with the leveling options when you want the project to finish. Using
such constraints will mean that PSOP can't extend your schedule.
|
|
 |
|
