FrankM -- Resource contention and stacking of hours (overallocatio

[Frank M]

What is the best way to handle resource leveling within the MS Project Server
2003 environment when ...

1. Administrative tasks (vacation, sick, etc.) under separate
'administrative project' allocates time on a day that project work has
already been allocated. Results in gross overallocation for that day. I've
heard about a 'plug-in' tool called 'TimeAway' by MSProjectExperts that I'm
thinking will address this issue by tracking administrative time by 'cup
empty' rather than 'cup full' approach. Project managers do not have access
to the enterprise resource pool in our environment --- only the administrator.

2. One or more projects have contention for the same resource on the same
day resulting in gross overallocation.

I know about leveling within the MS Project Professional 2003 application
.... but is this the best approach within the server environment, and if so,
using 'Automatic' or 'Manual'? I've heard that 'automatic leveling' can
produce some really unexpected results and so I'm hesitant to use this
approach.

Any ideas or suggestions? How does everyone else handle these scenarios?
Any feedback on the product 'TimeAway' for the administrative time issue?

Thanks!

 

[Dale Howard [MVP]]

FrankM --

If you are interested in our TimeAway application, please note that the
software saves each resource's nonworking time instance (such as vacation)
as nonworking time on the resource's personal calendar in the Enterprise
Resource Pool. This allows Project Server to automatically reschedule
planned work around each nonworking time instance.

The only way to level in your situation is to open each project in which a
resource is overallocated, to set a Priority number for each project
(Project

 

[Dale Howard [MVP]]

FrankM --

If you are interested in our TimeAway application, please note that TimeAway
saves each resource's nonworking time instance (such as vacation) as
nonworking time on the resource's personal calendar in the Enterprise
Resource Pool. This allows Project Server to automatically reschedule
planned work around each nonworking time instance. This will eliminate some
of your leveling needs.

The only way to level in your situation is to open each project in which a
resource is overallocated, to set a Priority number for each project
(Project - Project Information), and then to level each resource
individually in the Resource Usage view. This can be a very trying process,
and you should level each resource individually so that you can maintain
control over the process. Just a thought. Hope this helps.