Man Loading

[Robert E Jones III]

The resource pool here is unique to say the least.
Since Project Server 2003 and EPK are installed and used the company still
struggles with Man loading.
I have suggested using Resource Calendars as a means to so show non working
times for staff, but that went through one ear and out the other.
In a meeting this week someone suggested using the % availability as a means
to resolve the allocation issues.

Example Joe is allocated to work 50% of his time on Project X and 50% of his
time on Project Z and not used anywhere else.

So I guess we are saying when a resource is loaded onto a project the
availability is loaded at 50% for each project for that resource?
I have never seen it done this way?

 

[Gary L. Chefetz [MVP]]

Robert:

Don't you think it makes more sense to assign a resource at 50% to each
project, rather than 100% to each project? It certainly gets you closer to
reality. 40% to each might even get you closer.

 

[Rob]

The issue I have is not doing the % allocation injuction with the Resource
Calendars. The way it is setup now is that M-F 9-5 everyday [including
company holidays] is not marked with any days off. Thats what I have never
seen before not the % availability sorry I wasn't clear on that.

--
Rob Jones
Project Consultant
REJ Company

 

[Gary L. Chefetz [MVP]]

Rob:

You should difinitely put the company calendars in the standard calendar.
Beyond that, resource away time is very difficult to manage. It's the "hot
potato" of managing the system. You can check our website for a tool that
helps with this if you're interested.

The issue I have is not doing the % allocation injuction with the Resource
Calendars. The way it is setup now is that M-F 9-5 everyday [including
company holidays] is not marked with any days off. Thats what I have never
seen before not the % availability sorry I wasn't clear on that.

--
Rob Jones
Project Consultant
REJ Company

Robert:

Don't you think it makes more sense to assign a resource at 50% to each
project, rather than 100% to each project? It certainly gets you closer
to
reality. 40% to each might even get you closer.

 

[Rob]

Any [tool] help you have would be great.
The vacations and training [since they are weeks at a time] is something
that is a must for PM's. Communication here is lacking and the thought of not
knowing months in advance when someone is out for a week or 2 is asking for
trouble.
--

Rob:

You should difinitely put the company calendars in the standard calendar.
Beyond that, resource away time is very difficult to manage. It's the "hot
potato" of managing the system. You can check our website for a tool that
helps with this if you're interested.

The issue I have is not doing the % allocation injuction with the Resource
Calendars. The way it is setup now is that M-F 9-5 everyday [including
company holidays] is not marked with any days off. Thats what I have never
seen before not the % availability sorry I wasn't clear on that.

--
Rob Jones
Project Consultant
REJ Company

Robert:

Don't you think it makes more sense to assign a resource at 50% to each
project, rather than 100% to each project? It certainly gets you closer
to
reality. 40% to each might even get you closer.




The resource pool here is unique to say the least.
Since Project Server 2003 and EPK are installed and used the company
still
struggles with Man loading.
I have suggested using Resource Calendars as a means to so show non
working
times for staff, but that went through one ear and out the other.
In a meeting this week someone suggested using the % availability as a
means
to resolve the allocation issues.

Example Joe is allocated to work 50% of his time on Project X and 50%
of
his
time on Project Z and not used anywhere else.

So I guess we are saying when a resource is loaded onto a project the
availability is loaded at 50% for each project for that resource?
I have never seen it done this way?