I appreciate your reply. Do you have a sample report that u can share to me as a guideline. If you have kindly email it to denmark_zb@yahoo.com. Thank you very much.
Regards,
Den
Member for
17 years 7 months
Member for17 years7 months
Submitted by Mark Bandong on Thu, 2008-04-24 22:35
I appreciate your reply. Do you have a sample report that u can share to me as a guideline. If you have kindly email it to denmark_zb@yahoo.com. Thank you very much.
It depends upon which method u have chosen for analysis of EOT. Impact as-planned, as-planned V/s as-built, as-built but-for, collapsed as-built, time impact or window slice method.
It is necessary to focus the analysis on key areas of delay to avoid unnecessary expense. This makes the method iterative. It is not usually sufficient to simply compare the as-built programme to the planned programme without verifying the planned programme. It is necessary instead to prepare a construction logic which explains the sequence of events and reasons for the actions taken and the delay caused.
Also, you can highlight the events (By adding summary bars) in three ways:
- Delayed Events (Delay by client which cannot be mitigated)
- Mitigated Events (Delay by client but mitigated by contractor)
- Planned Events (New activities or variations)
The content of ur layout will change depending upon the method of analysis used. Apart from ur P3 programs and contract clauses, u may add the letters, ERIs / PMIs or RFIs to substatiate your claim, as that will be a key part of your notices sent regarding delays.
Member for
17 years 7 monthsRE: sample substantiation report
Dear ravi
Thanks Ravi
I appreciate your reply. Do you have a sample report that u can share to me as a guideline. If you have kindly email it to denmark_zb@yahoo.com. Thank you very much.
Regards,
Den
Member for
17 years 7 monthsRE: sample substantiation report
Thanks Ravi,
I appreciate your reply. Do you have a sample report that u can share to me as a guideline. If you have kindly email it to denmark_zb@yahoo.com. Thank you very much.
Regards,
Den
Member for
18 years 5 monthsRE: sample substantiation report
Hi,
It depends upon which method u have chosen for analysis of EOT. Impact as-planned, as-planned V/s as-built, as-built but-for, collapsed as-built, time impact or window slice method.
It is necessary to focus the analysis on key areas of delay to avoid unnecessary expense. This makes the method iterative. It is not usually sufficient to simply compare the as-built programme to the planned programme without verifying the planned programme. It is necessary instead to prepare a construction logic which explains the sequence of events and reasons for the actions taken and the delay caused.
Also, you can highlight the events (By adding summary bars) in three ways:
- Delayed Events (Delay by client which cannot be mitigated)
- Mitigated Events (Delay by client but mitigated by contractor)
- Planned Events (New activities or variations)
The content of ur layout will change depending upon the method of analysis used. Apart from ur P3 programs and contract clauses, u may add the letters, ERIs / PMIs or RFIs to substatiate your claim, as that will be a key part of your notices sent regarding delays.
Cheers,
Ravi