Question about leveling

Member for

18 years 11 months

Hello Martin,

First I would suggest ensuring that you have adequate logic ties within your projects and that you have applied a Deadline to the completion milestone for each project.  That's because MSP's default leveling heuristics give a higher score to tasks with lower Total Slack.

Next you could tinker with your leveling options, e.g. a) Level only within available slack; and b) Leveling Order - Priority, Standard.

In general, most projects are truly resource constrained, so the first option may not resolve the overallocations as much as you would like.  With the second option, you can control leveling results mainly by applying values to the Priority fields of individual tasks.  All tasks are created with a priority of 500 (i.e. Neutral) on a scale of 1000.  If two tasks are competing for the same resource, then the task with the higher priority is scheduled first, and the other task is assigned a Leveling Delay.  A task with priority of 1000 will never be assigned a Leveling Delay, but it can be delayed if its logical predecessor is delayed by leveling. 

Good luck, tom