Resource leveling weirdness

[Gershon Shamay]

In Project Standard 2002, I do a resource leveling as follows:
One resource has overlapping tasks, all of the ASAP
Leveling calculations: Manual, look for overallocation week by week, clear
leveling values before leveling
Date range: Level <from> <to>
Resolving overallocations: all checkboxes clear
Level now - selected resources [there's only one resource I'm looking at]

Result: most tasks are sequenced logically; the last 6 or 7 tasks are
scheduled concurrently at the same date, at the END of the date range, as
though they are scheduled ALAP instead of their ASAP designation. If my <to>
date is 5 years from now, these tasks will move to that date !!

Any explanation why this happens ?

 

[Jan De Messemaeker]

Hi Gershon,

Isn't the resource availability contoured?
This happens when a resource is no longer available after a certain date.
Mind you in your case it will also happen if a second resource on these
tasks is no longer available since you unchecked the possibility to handle
individual assignments individually.
HTH



--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/index.htm
32-495-300 620

In Project Standard 2002, I do a resource leveling as follows:
One resource has overlapping tasks, all of the ASAP
Leveling calculations: Manual, look for overallocation week by week, clear
leveling values before leveling
Date range: Level <from> <to>
Resolving overallocations: all checkboxes clear
Level now - selected resources [there's only one resource I'm looking at]

Result: most tasks are sequenced logically; the last 6 or 7 tasks are
scheduled concurrently at the same date, at the END of the date range, as
though they are scheduled ALAP instead of their ASAP designation. If my