Misty (or is it Charleen?) --
Allow me to add my thoughts to this matter. I recommend that you perform
all leveling of resource overallocations in the Resource Usage view, and
then you view the leveling results in the Leveling Gantt view. Keep in mind
that when you level a resource overallocation using the built-in leveling
tool in Microsoft Project, the software can only perform two leveling
actions:
1. Delay tasks and/or assignments on tasks.
2. Split tasks and/or assignments on tasks.
The tool cannot adjust Units on a task. This means that if the Max. Units
value for a resource is 50%, and you accidentally assign the resource at
100% Units, the software cannot resolve that overallocation, and only you
can resolve it by reducing the assignment Units to 50% or less.
Also, the built-in leveling tool uses time sensitivity in the leveling
process. When you click Tools - Level Resources, you find the sensitivity
option at the top of the dialog as the "Look for overallocations on a
_______ basis." The default setting is the Day By Day value, which means
that you can level overallocations in which the resource is assigned to more
than 8 hours in a single day time period. However, if you overallocated the
resource in a lesser time frame, such as assigning the resource to work 8
hours in a 4 hour time period, or 30 minutes in a 15 minute time period, the
tool cannot resolve the overallocation unless you change the sensitivity
setting to Hour By Hour or Minute By Minute as needed.
So, without seeing your actual project, neither Trevor nor I can determine
precisely why you cannot level the resource overallocation. Perhaps you
could give us more information about the actual overallocation and let's see
if we can help you further.
