1. Activity A 20days FF to Activity B 2 days then reschedule changing Schedule Durations option from Contigous to Interruptible and back (found in Tools, Schedule, Options). No percentage option in P3 but you could put -10 days lag on the FF.
2. Activity C 10 days FS to Activity D 10 days and Activity E 2 days with FS between E and D. Put Zero free float constraint on E.
No a big fan of FF so I tend to use method 2 and define what needs to happen before E is required and then what can happen once it has arrived.
HTH
Member for
17 years 6 months
Member for17 years6 months
Submitted by smithie johnny on Sat, 2008-07-19 06:01
Member for
24 years 6 monthsRE: Activity cannot finish until another - zero float
Two ways to try:-
1. Activity A 20days FF to Activity B 2 days then reschedule changing Schedule Durations option from Contigous to Interruptible and back (found in Tools, Schedule, Options). No percentage option in P3 but you could put -10 days lag on the FF.
2. Activity C 10 days FS to Activity D 10 days and Activity E 2 days with FS between E and D. Put Zero free float constraint on E.
No a big fan of FF so I tend to use method 2 and define what needs to happen before E is required and then what can happen once it has arrived.
HTH
Member for
17 years 6 monthsRE: Activity cannot finish until another - zero float
Vladimir
Can you please elobrate on " no earlier than"?
Also the schedule im putting together doesnt have resource contraints just time contraints. Does this help?
Is there a way to get P3 to behave to get JIT?
Member for
24 years 9 monthsRE: Activity cannot finish until another - zero float
It is not supported if resources are limited.
All dependencies used in Primavera software are of "no earlier than" type.
The dependencies you need (JIT) are called "strong dependencies" in Spider Project software.