Re: Start asap but with one resource when available by Trevor
Trevor
Fri Mar 14 06:10:53 CDT 2008
Since you say that the start of Task 3 depends on the Resource availability
and not on either of Task 1 and Task 2, then they should not be linked as
Predecessors.
So if there is no Predecessor links all 3 Tasks start ASAP, on day 1, Task 2
Duration is 2 days longer than Task 1 and the Duration of Task 3 doesn't
matter.
Suppose the Durations are 5, 7 and 5 days respectively.
Assign R1 to T1 and R2 to T2, then assign R1 and R2 to T3.
They will be over-allocated.
In Tools, Level Resources check "leveling can adjust individual assignments
on a task".
Then Level.
T3 gets delayed until T1 is finished, R1 starts T3, then R2 joins T3 when T2
is finished.
The Task Type and Effort Driven settings for T3 are important.
If T3 is Fixed Units (the default), then the Duration of T3 will be
increased by 2 days to 7 days so that R1 does his 40 hours in the first 5
days and R2 needs the 2 extra days to do his 40 Hours from when he joins T3
2 days after R1.
If T3 is Fixed Duration, MSP Leveling will not change the Duration but T1
will not start until umtil T2 is finished and R1 will not start work on T3
until R2 does, and they will both work the same hours on the same days.
If T3 is Fixed Work, then the Duration of T3 will be increase by 2 days to 7
days.
In all 3 cases, the Work remains 40 Hours each for R1 and R2, and the Effort
Driven setting makes no difference.
You can see this most clearly in the Task Usage View, where you can also
adjust the Work for each Resource for each day (after Leveling).
If, for example, you want to have T2 only work on the last 3 days, you can
set his Work to 0 on day 6 and 7, which would reduce the T3 Duration back to
5 days.
Trevor Rabey 0407213955 61 8 92727485 PERFECT PROJECT PLANNING
www.perfectproject.com.au
"Kay" <kay_schulz@yahoo.com> wrote in message
news:398fa6c5-4c90-4ed4-8cb7-bf91a00fc6d6@i29g2000prf.googlegroups.com...
> Hi
> I know it's possible but can't find the answer:
> Resource 1 does task 1 and it ends 19.03.2008
> Resource 2 does task 2 and it ends 21.03.2008
> Task 3 can only be started, when at least one resource is available
> and shall be done by both.
> So it should start as soon as one of the dependencies (t1 or t2) is
> available
> and r2 joins when it is ready.
> How can I handle this?
> thanks
> Kay