problem with leveling

[r77]

hai.


while levelling resorses, critical path and late start-late finish are becoming wrong.

[JulieS]

Not really sure what you mean by "become wrong". Can you give more details - starting with what release of Project? Server or desktop? That is NOT Office 2013 - Project 2007? Earlier? Are you up to date with all updates? What are your leveling options? Are you delaying tasks on the critical path?

[r77]

Originally Posted by JulieS

Not really sure what you mean by "become wrong". Can you give more details - starting with what release of Project? Server or desktop? That is NOT Office 2013 - Project 2007? Earlier? Are you up to date with all updates? What are your leveling options? Are you delaying tasks on the critical path?

The problem apear in all versions. I use late start and late finish (gray lines) to show when task will becom critical. When leveling ,this gray lines are being modified automaticly and do not represente any more when task will become critical(earlier then it was suppose to be)

[JulieS]

The field [Total Slack] show the difference between Late Finish and Early Finish or between Late Start and Early Start (whichever is smaller).

I've re-created your project file using Project 2010 so let's step through this.

Before resource leveling all tasks are critical (zero total slack). This makes sense because all of the tasks assigned to Resource B (Tasks A - K) all have successors and all tasks have the same durations.

After leveling the only two tasks that are critical are tasks K (last in the tasks assigned to Resource B) and task X.

Because none of your tasks are linked past the simple one link the only tasks showing as critical are the last. You are correct that if Task A slips, it will delay task N - but Task N is not the last task in the project. If you want to see that A will Delay N (a single network path) you need to turn on the option View Multiple Critical paths.

[r77]

hai Julie.
the fact that task n slips if task a slips is normal because there is no free slack between them.
what is not normal (for example) is that task x slips if task k slips even so task k supose to have a free slack.
something dosent make sense.

[JulieS]

I agree there is a disconnect because of the leveling. Task K shows as zero Total Slack and zero Free Slack. The calculation for free and total slack does not appear to take into account the larger amount of leveling delay that has been added to task x.