It could also be that the network logic is incomplete. If you have a series of activities forming a path that is not somehow anchored at the end, either by the project completion or by a constraint (Finish No Later Than), and your analysis is not based on longest path, then the total float for that path will always be zero. This is due to the backward pass originating at the end of that path, the same point that the forward pass ends, so the lates will always equal the earlies and total float =0. But that is only one possible explanation.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Fri, 2012-03-02 13:04
If you compare Early vs Early or Late versus Late you will record slippage but not float consumption. Use Baseline Late Dates minus Current Early Dates for float consumption, a simple formula or Global Change shall do it. An alternate way is to compare float values between Baseline and Current.
If your current job is ahead of schedule your float consumption shall be negative (depending on your comparison settings Baseline minus Current or Current minus Baseline), you have created float available for your benefit and for those who want to take it away from you.... LOL
Regards,
Rafael
Member for
24 years 1 month
Member for24 years1 month
Submitted by Daniel Limson on Fri, 2012-03-02 11:08
Granting the the programme logic is correct, the Variance Report should tell you what activities have slipped against your baseline programme and how much time (total float) you still have before impacting the project completion date. If you are saying that you have now TF=0, it simply means that these activities are now critical and should be completed on time otherwise these activities are already delaying the project completion. I would suggest to filter all these activities and discuss it with the construction team so that mitigation measures or work around can be plan ahead to avoid delaying the proejct completion.
Member for
13 years 9 monthsIt could also be that the
It could also be that the network logic is incomplete. If you have a series of activities forming a path that is not somehow anchored at the end, either by the project completion or by a constraint (Finish No Later Than), and your analysis is not based on longest path, then the total float for that path will always be zero. This is due to the backward pass originating at the end of that path, the same point that the forward pass ends, so the lates will always equal the earlies and total float =0. But that is only one possible explanation.
Member for
21 years 8 monthsIf you compare Early vs Early
If you compare Early vs Early or Late versus Late you will record slippage but not float consumption. Use Baseline Late Dates minus Current Early Dates for float consumption, a simple formula or Global Change shall do it. An alternate way is to compare float values between Baseline and Current.
If your current job is ahead of schedule your float consumption shall be negative (depending on your comparison settings Baseline minus Current or Current minus Baseline), you have created float available for your benefit and for those who want to take it away from you.... LOL
Regards,
Rafael
Member for
24 years 1 monthHi Raul,Granting the the
Hi Raul,
Granting the the programme logic is correct, the Variance Report should tell you what activities have slipped against your baseline programme and how much time (total float) you still have before impacting the project completion date. If you are saying that you have now TF=0, it simply means that these activities are now critical and should be completed on time otherwise these activities are already delaying the project completion. I would suggest to filter all these activities and discuss it with the construction team so that mitigation measures or work around can be plan ahead to avoid delaying the proejct completion.
Best regards,
Daniel