All,
I currently work on a large infrastructure job and the amount of CEs is huge (some being larger than others). As a result to continue to progress the change account, the Change Manager and the team have agreed to assess time impact CEs out of chronological order to avoid getting stuck on a single CE for a while.
My question is what is the correct method of dealing with concurrent/overlapping delays.
For e.g.
There are older CEs that have been assessed at say 100d for a specific area on the job which has it’s own access and key date (these have been submitted on CEMAR with programme and quote but no assessment for months)
When assessing a later CE for e.g. a delay to access date to that same area, due to the baseline including the CEs noted above there is nil impact as they were pre construction delays moving the access date along so even with the access date change CE there is no impact. Quote and programme are submitted on this basis to keep the change account moving along.
What happens now if the client rejects the first few pre construction CEs or assesses it differently. Note ideally we would have meetings to discuss these things and know we are in the same ballpark but this is not possible and we have tried a number of times.
We have then submitted the access date CE at nil impact and if they implement it we have lost out on the difference in entitlement.
What is the best way of dealing with this? What is the best way of dealing with assessing time impact CEs in a non chronological way and ensuring that where there are 2/3 CEs that all cover the same delay we are able to get it under one of the CEs