Forum Discussion
Start to Finish Relationship - earliest start when connecting to two predecessors
Hi
I have a scenario. Three tasks
Task A - Technical documentation (preparation of it)
Taks B - Project Stage Finish For Technical documetation so A have to finish before B
Task B have Constraint Type - Must Finish On
Task B - can change its Start/Finish date
Task C - Physical Works Start - Start of works for which Technical Doc. from task A is needed
so A have to finish before C
Task C - will move as in reality, it will also depend upon other "tings" in project which can and will change
Task A is most "submissive" task
It always have to be finished before Start of B and C (sorry to all Documentation designers out there)
How to create proper connection between a/m taks that always will move finish of Task A before start of B and C independent of where B and C will be moved ?
I've tried to use Start to Finish, but it works only if I connect one task
Below a screen shoot form my MSP
I'm sorry for Polish ... but can't switch it to English (entire Office suite will .. but not MSP.. )
RZ = SF
Typ Ograniczenia -> Constraint Type
Jak najwcześniej -> As Soon As Possible
Musi zakończyć się -> Must Finish On
Rozpocznij nie wcześniej niż -> Start No Earlier Than
Rozpoczęcie -> START
Zakończenie -> Finish
Poprzedniki -> Predecessors
Następniki -> Successors
Example 1 and 1A - works.... but it A is connected to only one task (A or B)
Example 2 - I've connected A to B and C, but A is moved beyond B
Example - same problem as above but in this scenario I've moved C before B
but A... stick itself for task furthrer in future
I know that I can create connection like belowe
Using "Standard" connection between A and B
and in the moment when situation as above will happen (A will move past B), MPS will "Scream" at me with a message that he can't finish task A
but that is not a solution for me.
1 Reply
If Task C is on the critical path (Has 0 days float/total slack) you should be able to link both Task A and B to Task C using the default FInish-Start relationship type, and set the Constraint Type to "As Late As Possible" for both Task A and B. This will move them as late as they can occur without pushing back the start of Task C. However, If Task C has float/slack, doing this will push Task C as late as possible as well. Alternatively, you can set a deadline for Task C (by double clicking on the Task) and linking A and B to C as described above. If Task A, B, or C falls behind schedule, the dates will still get pushed beyond the deadline, but you will have negative float to alert you of the problem. I'm fairly new to Project, so I hope I understood your question correctly and hope this helps.
