Rafael is correct - non work days are claimable if a prior delay moves the task over a non work period.
I have known this to be many months if a delay puts the work over an embargo period in the contract.
Remember as well that the delay period is expressed in calendar days so if you have put in a task bar to represent the delay period make sure that it has a 24/7 calendar and the duration column shows elapsed of calendar days.
Best regards
Mike T.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Wed, 2012-02-29 01:36
It depends on the change of finish dates of your job, on the impact. If due to weather conditions the one day lost to rain on Monday delayed the job to finish instead of next Saturday to finish next Monday you got delayed by 2 calendar days. If the Monday was a holiday then finish of job is delayed to next Tuesday you got delayed by 3 calendar days.
What if there is a resource conflict and the delay is even more?
Some people ask Float, is it real? .. and they are right. Many software cannot handle float under resource leveling, cannot handle float under multiple constraints but can figure out the correct finish date. Also negative float creates a lot of issues. Float have been prostituted by those who insist on basing the analysis using float instead of observing the effect.
By no means I pretend to say float has no value, correct float shall be displayed always but the impact is better determined by running the model.
Member for
19 years 10 monthsHi Carlos Rafael is correct -
Hi Carlos
Rafael is correct - non work days are claimable if a prior delay moves the task over a non work period.
I have known this to be many months if a delay puts the work over an embargo period in the contract.
Remember as well that the delay period is expressed in calendar days so if you have put in a task bar to represent the delay period make sure that it has a 24/7 calendar and the duration column shows elapsed of calendar days.
Best regards
Mike T.
Member for
21 years 8 monthsIt depends on the change of
It depends on the change of finish dates of your job, on the impact. If due to weather conditions the one day lost to rain on Monday delayed the job to finish instead of next Saturday to finish next Monday you got delayed by 2 calendar days. If the Monday was a holiday then finish of job is delayed to next Tuesday you got delayed by 3 calendar days.
What if there is a resource conflict and the delay is even more?
Some people ask Float, is it real? .. and they are right. Many software cannot handle float under resource leveling, cannot handle float under multiple constraints but can figure out the correct finish date. Also negative float creates a lot of issues. Float have been prostituted by those who insist on basing the analysis using float instead of observing the effect.
By no means I pretend to say float has no value, correct float shall be displayed always but the impact is better determined by running the model.