The whole point of an 'as-is' method is that you leave the data 'as-is', to avoid any allegation of manipulation etc.
The main As-Is methodology I use is in the production of 'float map'. This uses only as-built data programme data, taken directly from the Contractor's files.
Essentially its just an abstract of monthly total float values, which you can sort / filter to illlustrate as-built critical path changes, etc.
Of course if there are discrepencies in as-built data, these will need to be addressed.
In practical terms, its also neccassary to adjust total float values to accomodate different calenders etc, and you'll be scratching your head with a way to show driving/sub-critical tasks so it can get pretty complicated. However the underlying data being unchanges is the key.
I've got a fairly good system, which can quickly identify the as-built critical path, subject to further scrutiny.
Cheers,
Alan
Member for
22 years 5 months
Member for22 years5 months
Submitted by Stephen Hepburn on Tue, 2014-01-21 06:49
Member for
12 years 1 monthStephen,The whole point of an
Stephen,
The whole point of an 'as-is' method is that you leave the data 'as-is', to avoid any allegation of manipulation etc.
The main As-Is methodology I use is in the production of 'float map'. This uses only as-built data programme data, taken directly from the Contractor's files.
Essentially its just an abstract of monthly total float values, which you can sort / filter to illlustrate as-built critical path changes, etc.
Of course if there are discrepencies in as-built data, these will need to be addressed.
In practical terms, its also neccassary to adjust total float values to accomodate different calenders etc, and you'll be scratching your head with a way to show driving/sub-critical tasks so it can get pretty complicated. However the underlying data being unchanges is the key.
I've got a fairly good system, which can quickly identify the as-built critical path, subject to further scrutiny.
Cheers,
Alan
Member for
22 years 5 monthsMike,In what way would this
Mike,
In what way would this methodology have validity. Do you mean in sub contract form, the process is used to quickly identify the impact and delay.?
Member for
19 years 10 monthsHi StephenAccording to Mr
Hi Stephen
According to Mr Chris Carson there are at least 18 different delay analysis methods.
What you have described seems to be an As Planned v As Built variant.
This could be valid in a sub-contract EoT but otherwise useless.
Best regards
Mike Testro