Basic work load in project server

[Peter M.]

Hello there.

What is in your opinion the best way to handle basic work load of resources
in project server? First, we set up a project with all resource names as
tasks, all assigned 10% of work to sort of simulate their estimated basic
work load of 10%.
But a problem came up with that solution. When a resource is on holiday, it
will - logically - always be overallocated and be displayed red in every
view, which harms clarity.
Now we think about setting max. units to only 90%. Is that meant to be the
best solution?

What suggestions do you have?

Thanks for your help,
Peter.

 

[Peter M.]

Sorry guys,

I'm talking about Project Server version 2007 of course, should it make a
difference.

 

[Dale Howard [MVP]]

Peter --

What you are describing is what we called an Administrative project in
Project Server 2003. In Project Server 2007, Microsoft eliminated the
Administrative project in favor of using Administrative time categories on
the My Timesheet page. However, because Microsoft removed the
Administrative projects capability does not means that we can't use
administrative-like projects if we choose to do so.

In your situation, you have two options:

1. Use the Administrative time categories on the My Timesheet page to track
non-project work.
2. Use an administrative-like project to track non-project work, as you are
currently doing.

Regarding #2, however, you have erred on one assumption. Provided that
nonworking time, such as vacation, is entered on each resources personal
calendar in the Enterprise Resource Pool, the system will automatically
reschedule overhead work around the nonworking time, and will NOT cause an
overallocation. Hope this helps.