Level resource and Load summary resource assignment


×

×רז

Hi all
We are using project server 2007 SP1
I checked the Load summary resource assignment check box and did level
resource on specific resource.
I see that the resource has been scheduled to start working in the far future.
The resource is not allocate to other projects and did not submit future
timesheets.
I also know that this resource did not use plan administrative time.

What could be the reason for this schedule behavior?
 
Ad

Advertisements

D

Dale Howard [MVP]

×רז --

First of all, I would recommend that you deselect the "Load Summary Resource
Assignments" option before you attempt to level overallocated resources.
Doing so will allow you to focus your leveling process on only the projects
you open. If you have a resource that is overallocated across multiple
projects, you will need to open each of those projects. Also, open the
project in which you leveled the resource overallocation and clear the
leveling using Tools - Level Resources - Clear Leveling. You need to remove
the leveling before you go any further.

The behavior you describe can happen if you attempt to level resource
overallocations in the Gantt Chart view, because you lose control of the
leveling process. My company recommends that you level in the Resource
Usage view, one resource at a time, beginning with your key or most critical
resource. In the Resource Usage view, select the resource in question and
click Tools - Level Resources. In the Resource Leveling dialog, deselect
the "Clear leveling values before leveling" option, as this will allow you
to level one resource at a time. Click the Level Now button, choose the
"Selected resources" option in the Level Now dialog, and then click OK. The
system will attempt to resolve your resource overallocation by either
delaying one or more tasks to which the resource is assigned, or by
splitting one or more tasks to which the resource is assigned.

There's no guarantee that the system can ever level your resource
overallocations the way that you wish, and there are some overallocations
that the system cannot even touch. For example, a resource's Max Units
value is set at 50% in the Enterprise Resource Pool, and you accidentally
assign the resource at 100% Units on the task. Because the leveling tool
does not touch the Units field ever, it cannot resolve this overallocation.

To see the results of leveling, click Window - New Window. In the New
Window dialog, select the Leveling Gantt view and then click OK. In the
Leveling Gantt view, green bars represent the pre-leveling schedule of tasks
to which the overallocated resource is assigned, and blue bars represent the
post-leveling schedule. If you see a brown underscore in front of a blue
Gantt bar, that is the Leveling Delay the tool applied to the task to
resolve the overallocation. You should see the amount of the Leveling Delay
in the Leveling Delay column.

Why don't you try leveling using this methodology and let us know the
results. Hope this helps.
 
×

×רז

Dale,

Thanks for your rapid replay,
I totally agree with you and at the initial planning phase we also deselect
the "Load Summary Resource Assignments".
We do not level at the Gantt chart view; we are doing it from the resource
sheet, one resource at a time.

I would like to focus on the Load Summary Resource Assignments schedule
mechanism.
When I am doing level resource, with selected Load Summary Resource
Assignments".
I would like to understand what the project mechanism, is taking on
consideration?
I think that this feature is very powerful in a multi projects environment.
I see that in some cases, the resource has been scheduled to start working
in the far future.
The resource is not allocate to other projects and did not submit future
timesheets nor using plan administrative time.
I will appreciate your help in this matter
 
D

Dale Howard [MVP]

×רז --

You are wrong about the "Load Summary Resource Assignments" option being
useful during leveling. It is NOT useful, and is frankly quite troublesome.
Here's why: for some strange reason, Project Server 2007 assumes that
projects you do not have open have a higher Priority number that those that
youcurrently have open. This makes no sense whatsoever, and throws off your
leveling immensely. This is why I recommend that you deselect the open when
you want to level overallocations, and then open each project containing
resources that are overallocated across multiple projects. This way you can
set Priority numbers for each project (Project - Project Information) and
level successfully across multiple projects.

Hope this helps.
 
×

×רז

Dale,
Thanks again,
I understand what you are saying but
If I will not check the Load Summary Resource Assignments check box, the
project will not take in consideration the plan administrative time (vacation
etc for example)
How can I overcome this issue?
Regards
Erez
 
Ad

Advertisements

A

Alain

Hi ×רז,

I have exactly the same issue as you. When I level my project some tasks are
scheduled to start in the far future although this resource has a lot of
available capacity in the near future.
If you have found any solution, please advice.

Thanks.

Alain.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top