Negative Float

Hi Muir,

There is a big chance the schedule was constraint using "must be finish" dates.

Charlie

Thanks Charlie,

In my research on other sites/forums today I came across a similar sentiment & am now in the process of reviewing all constraints. This seems to be doing the trick. Thank you for confirming that I’m on the right track. Your help & your time are appreciated.

Alan

Dear Alan,

You probably have figured this one out already.

Must finish contraints are the root cause of this in my experience. In particular, at a project level in Primavera (P3e) you may place a project ’must finish by’ contraint. This will impact everything as soon as you start progressing your plan.

Another cause of this is when you have "loose logic". Your plan should input/output logic links except for the 1st and last activity! Loose logic causes havoc with your float calculations. However, it mainly gives you huge float values on certain activities as opposed to -ve float.

Cheers
Neil.

Cheers Neil,

You were right on both counts. I appreciate your time & help with this problem.

Thanks,

Alan

Late start or finish constraints can also cause negative float when the activity logic and durations push past this date.

Negative float = early dates > late dates