Remaining Late

negative float

Hannes,

Many in order to avoid negative float computations that override traditional CPM computations for backward pass resort to temporarily eliminate all finish constraints, including job must finish date.

I do not use negative float to follow project logic, as a matter of fact I believe the application of finish constraints by most software, if not all, is wrong.

Because it is error prone to get back all constraints, I would suggest you to make a copy of your job and then in this copy delete the constraints.

For a recovery schedule you most probably will be in need to temporarily delete finish constraints, depending on software recovery of constraints can be tricky.

Also understand that under a resource constrained job, negative float computations are wrong, even if your software is capable of displaying resource critical float, negative float is kind of meaningless.

Best regards,
Rafael

Dear Hannes,

What do you mean by remaining late?

The Data Date is the date through which the project status and progress were last determined. And the Remaining Duration is the difference between the Data Date and the Schedule activity finsih date; which is the time required to complete the activity.

What exactly is the error that you are getting?

With kind regards,

Samer

Do you have level of effort activities with resource assignments?

There is a known bug in P6 where LOE’s that are in progress have the late start date set equal to the actual start date. This causes remaining late work to show up before the data date on histograms.

An easy way to check is to filter out the LOE’s and see if the display looks right.

Ian


http://www.emerald-associates.com

Seems like not always Negative Float is bad.

http://www.arcadis-us-pmcm.com/assets/files/PinnacleOne_Criticality_What_Do_Courts_Say.pdf

Another Court Accepts the Negative Float Theory of Criticality !!!

INCREDIBLE .......COURTS ARE "SMARTER"/"OR AS DUMB" AS THE FOOLS THAT CREATED NEGATIVE FLOAT... LOVE THIS ONE.

Hi Rafael

Thanks for that link - it makes the UK jurisdiction on concurrency relatively straightforward.

Best regards

Mike Testro

What happened:

as I hardly use constraints I do not often have negative float. But the answers seemed to be good, so I checked my schedule. I found a negative float of 60 days!!!. Now I looked for the reason and found two strange FS-linked activities - The successor had started, the predecessor was still in future. This created my negative float. After deleting this link, everything was ok.

Thank you for some good replies.