Hi All,
In a detailed contractual programme where we have around 40,000 No. of activities with proper weekly updates and around 600 Engineer's Instructions / Site Instructions;
If the programme logic is not altered after a point and it is not reflecting the actual site conditions due to changes/instructions not being reflected into the programme, what is the best way to put an EOT Claim while we reach to the end of the project?
Looking at the delay event register, maybe 250 No. of these changes, delays from the employer are critical. There is also serious amount of mitigations measures taken by the Contractor in various areas of the job (and not measured properly) and obviously there are a lot of out of sequence work compared to the Contract Programme logic.
Considering all of these, I cannot settle in my head about how to do the proper analysis.
1. Looking at the period of changes and delays; I should be having at least 10 to 12 windows (presumably monthly),
2. Each window will be having serious amount of delay events with their fragnets,
3. Eventhough the programme is having a great detail; some parts of the programme are not having sufficient detail to reflect the actual conditions and the impact of the changes due to complexity of the horizontal project. This will require huge amount of logic changes in each windows' original updated programme to reflect the facts and will require linking the fragnet activities with a proper logic.
So, this is a huge task and with having all the information it would require at least 2-3 months in my opinion.
Is there any simpler way to do this analysis? For instance, can we make a final as-built programme with all the changes and final sequence and logic to compare with the baseline? If we do that, how we will be able to identify the concurency?
I am confused :)
Thanks already to those who will reply.