Baseline schedule lost its validity for that reason the client asked to create a recovery plan which takes place of the baseline. Once the recovery approved, it must be used as a new baseline because it drops past issues (concurrent delays, contractor caused delays etc.)
Hi Kathy
I disagree with your opinion that the recovery schedule should be used for the baseline in delay analysis.
It may just be a target programme set by the contractor to avoid LAD's.
Ahmed tells us that both the programmes end on the same date which means that the logic and/or task durations are different.
In any case any form of impact on a critical path will give theoretical results and should be avoided.
Best regards
Mike Testro
Member for
7 years 6 months
Member for7 years6 months
Submitted by Kathy Castle on Thu, 2018-04-19 15:31
If your recovery schedule is approved by the client officially, you should use this one. Because the recovery is the latest one which includes all the changes and the delays in the past. If you need to make a forensic schedule delay analysis, I recommend you to read this methods https://www.projectcubicle.com/forensic-schedule-delay-analysis/
Hi Ahmed.
Which one are you using to monitor current progress?
A "recovery schedule" indicates that there are already delays on the project.
If you add delays caused by change orders to a programme already delayed by the contractor then you are giving him the benefit of his own delays.
This is always a problem when impacting delay events on a theoretical critical path which may be different in the two programmes.
If you use a Projected As Built method then the inherent problem is solved.
You can download the method from my website www.expertdelayanalysis.com for £35.00
Best regards
Mike Testro
Member for
7 years 6 monthsMike,Baseline schedule lost
Mike,
Baseline schedule lost its validity for that reason the client asked to create a recovery plan which takes place of the baseline. Once the recovery approved, it must be used as a new baseline because it drops past issues (concurrent delays, contractor caused delays etc.)
Member for
19 years 10 monthsHi Kathy I disagree with your
Hi Kathy
I disagree with your opinion that the recovery schedule should be used for the baseline in delay analysis.
It may just be a target programme set by the contractor to avoid LAD's.
Ahmed tells us that both the programmes end on the same date which means that the logic and/or task durations are different.
In any case any form of impact on a critical path will give theoretical results and should be avoided.
Best regards
Mike Testro
Member for
7 years 6 monthsHi Ahmad,If your recovery
Hi Ahmad,
If your recovery schedule is approved by the client officially, you should use this one. Because the recovery is the latest one which includes all the changes and the delays in the past. If you need to make a forensic schedule delay analysis, I recommend you to read this methods https://www.projectcubicle.com/forensic-schedule-delay-analysis/
Member for
19 years 10 monthsHi Ahmed. Which one are you
Hi Ahmed.
Which one are you using to monitor current progress?
A "recovery schedule" indicates that there are already delays on the project.
If you add delays caused by change orders to a programme already delayed by the contractor then you are giving him the benefit of his own delays.
This is always a problem when impacting delay events on a theoretical critical path which may be different in the two programmes.
If you use a Projected As Built method then the inherent problem is solved.
You can download the method from my website www.expertdelayanalysis.com for £35.00
Best regards
Mike Testro