Resource Overallocation Part 9 – Leveling at the Resource Level (continued)

Microsoft Project provides many options for resolving overallocation at the Project, Task, Resource and Assignment levels of the Microsoft Project Data Model. In this Milestone Minute we will focus on resolving overallocation at the resource level of the data model. In upcoming Milestone Minutes we will continue to resolve overallocation through additional resource and assignment level strategies. Also, at the end of this Milestone Minute is the answer to the question asked in the Resource Overallocation – Part 8 Milestone Minute.

In the following illustration, Bradley Beck and Wendy Wheeler are overallocated as they are both assigned to Tasks A and B, and Tasks C and D during the same time period:

Resource Overallocation Leveling at the Resource Level Pic 1

To omit a resource from all leveling, from the View tab, Resource Views group, click Resource Sheet as shown in the following illustration:

Resource Overallocation Leveling at the Resource Level Pic 2

From the Format tab, Columns group, click Insert Column as shown in the following illustration:

Resource Overallocation Leveling at the Resource Level Pic 3

From the list of columns (fields) insert Can Level as shown in the following illustration:

Resource Overallocation Leveling at the Resource Level Pic 4

Change Can Level to No for the resource to be omitted from the leveling process as shown in the following illustration:

Resource Overallocation Leveling at the Resource Level Pic 5

Reapply the Gantt Chart view, and then from the Resource tab, Level group, click Level All as shown in the following illustration:

Resource Overallocation Leveling at the Resource Level Pic 6

Once Level All is selected, the overallocation is resolved as shown in the following illustrations:

Resource Overallocation Leveling at the Resource Level Pic 7

The question to consider is, “why did Microsoft Project resolve the overallocation the way it did?” The answer will be provided in the next Milestone Minute along with additional information related to the answer!

Applies To: All Current Versions of Microsoft Project.

In the previous Milestone Minute, Resource Overallocation – Part 8, we asked “why did Microsoft Project resolve the overallocation the way it did with the Standard order applied?”

Resource Overallocation Leveling at the Resource Level Pic 8

The answer: with the Standard Order applied, the first pass at leveling defaulted to ID only which means Wendy’s assignment on Task C moved first. Then, with the Standard Order applied, the second pass at leveling defaulted to amount of total slack which means Wendy’s assignment on Task B moved second. After the second move all overallocation for Wendy was resolved.

Additional information: with the Standard Order applied, the following factors are considered in the leveling process: Predecessor, Amount of Total Slack, Start Date, Priority, and Constraints.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.