Abstract:

The client for whom the claim is to be determined has furnished the following files and formats

• 5 x Microsoft Project Files (between 750 and 1000 tasks)
• 24 x PDF’s
• 35 x htm (Memos and other communications between Contractor and Developer)
• 5 x XLS (EOT and variation registers)
• 32 EOT’s Event Claims
• 30 x Team Binder Files (could be Aconex)

These files are defined below, estimating how long it will take to perform the requisite analysis to provide a solution which has been arrived at rigorously and accurately will require time.

It was determined that the delay analysis would be performed an “Impacted as-planned analysis”

This method involves introducing delay events into a logic-linked baseline programme and its recalculation using Microsoft Project programming software programme to determine the prospective impact on these events have on the predicted contract completion dates shown in the baseline programme. Before commencing upon the analysis, the analyst must be able to confirm that the sequences and durations for the works shown in the programme are reasonable, realistic and achievable and properly logically linked within Microsoft project, to deal with any risk that the baseline programme contains fundamental errors which cannot be overcome.

Technically the use of impacted as-planned is expected to be the simplest and least expensive form of delay analysis, but has material limitations, mainly because it does not consider actual progress and changes to the original planned schedule.

The use of analysis tools is used to rapidly check that the schedule produced in P6 or MSP are either compliant or not with the 14 DCMA Schedule Assessment, such as

• Deltek Acumen Fuse
• XER Schedule Toolkit
• Schedule Analysis Enterprise
• Project Tracker
• Live Project
• Schedule Analyser

A suggested time for this analysis has been based on the following premise, based on known industry expert’s opinions.  This paper explains how it is done.

Read the full article (link below)