Project scheduled unavailable resource

[deluth]

I'm currently using MSP2003. I have different resources available at
different times, I set this is the Resource Sheet (General Tab). I then set
all the tasks and assigned it to the resources accordingly. When I level the
resources, Project complained that the unavailable resources were
overallocated. Of course they're overallocated, they're not available to
work yet. Why is Project scheduling them when they're not available? Do I
need to do something special to specify their unavailability?

 

[Jan De Messemaeker]

Hi,

As I said before, the Why questions beat me, I can't read the developers'
minds.
Fact is yes, unavailable in that sense sets availability to zero but does
not shift tasks until you do leveling.
I'm afraid that if you want tasks to react immediately to absences you have
to enter them as non working time.
HTH

 

[JulieS]

Hi Deluth,

If your resources are not available until dates you specified through
modifying their max. units (General Tab on the Resource Information dialog
box), Project will not automatically shift the work to when they are
available. However, leveling should solve the problem and delay the tasks
until the resource is available as long as you allow the Leveling to delay
tasks on the critical path. (Remove the check from "Level only within
available slack" in the Resource Leveling dialog box.)
The only other option is to modify the resource's calendar (the Working time
tab on the Resource Information dialog box) by marking the dates they are not
available as non-working time. Then Project will shift the tasks to time
defined as working time in their calendar. (They may still appear as
overallocated if you assign them to multiple tasks.)

Hope this helps. Let us know how you get along.
Julie