Leveling problem.

[Manis]

People,
Need help with leveling.
I have a test project.
1 resource with a max unit of 80%
4 tasks
1. Pre-work - 8 hrs - fixed work - with the only available resource at 80%
(default).
2. meeting - 13 days - fixed duration - with the resource at 100%.
3. post-work - 16 hrs - fixed work - resource at 80%
4. post-work meeting - 25 days - fixed duration - resource at 100%

The above is all I have in the plan. When I try to level (day by day, entire
project on standard leveling order, leveling can adjust individual
assignment, can create split), project says it cannot level.

All I have is 1 resource and 4 tasks! Why won't it level such a simple
project? I have been able to work around. But, I need to understand why
leveling will not work for the above scenario.

I can send my MPP file. Let me know.

Thank you!

 

[Jan De Messemaeker]

Hi,

Allleveling does is postpone taks that cause tasks when they are
simultaneous with other tasks.
Leveling DOES NOT, NEVER EVER, change assignment units.
So even a "project" with one task will give the "cannot level" message when
the assignment units exceed the maximum units.
OTOH I have seen good results of leveling of thousands of asignments... as
long as you do not introduce the impossible.

Hope this helps,

 

[Manis]

Jan,
Thank you for the reply. I'm not expecting Project to do anything other than
postpone taks. But if you try the example given below, it does not do
anything. All I want is to understand why it won't do it.
It's just 4 tasks and there's no dependency. I can introduce dependency and
work around the problem (There are other ways too). But, I'd like to
understand why Project won't level this simple project.

I would think leveling 4 tasks with just 1 resource should not be an
impossible scenario!

Thanks!

 

[Manis]

Jan,
I think I replied too quickly without completely understanding what you are
saying. Sorry about that!

From your reply, I understand that the problem is because the resource has a
max assignment of 80%, but some tasks have 100%.
The work around would be to have everyone at 100% and instead reduce all
working days to 80% of standard hours.

Thank you again!

 

[Jan De Messemaeker]

Hi,

Sorry if I wasn't clear enough.
Once Project discovers an impossibility (and 100% assignment unist versus
80% mas units IS an impossibility for leveling) it "gives up" that day for
that resource.
So in your example it does noithing.
HTH

 

[Steve House]

Postponing a task means slipping it back in the schedule so it's not
occuring at the same time another conflicting task is occuring. But it
slips as a unit - if the duration is 2 weeks and it is postponed, it remains
a two week duration task but is started sometime later than originally
scheduled. There's no way to slip that 13 day task where the resource is
assigned at 100% and have the resource assignment drop to 80%. For the 100%
you've assigned to drop down to the 80% you've said is that maximum it's
possible for this resource to work, you have to either lengthen the duration
or reduce the number of man-hours of work the task requires. But leveling
doesn't do that for you, you have to resolve it yourself because only you
know which of those two options would be appropriate.