THE DYNAMIC V APAB CALCULATOR DEMO

The video on the right provides a demonstration of the how from the source data from Primavera P6 both Dynamic and As-planned v As-built (actual) critical paths can be shown across multiple progress updates.

The APAB critical path is calculated by computer code as stated in the pages: "DYNAMIC V APAB CP REASON" and "SIMPLE DYNAMIC V APAB CALCULATION".
The Dynamic critical paths and sub-critical paths are not calculated, they are taken from the P6 database which includes "critical" and "driving" information.

Why is the APAB calculated? Because P6 cannot do an APAB critical path calculation across multiple updates.

And also:

EOT’s need to be calculated as cited by Roger Toulson QC who, in the case of John Barker Construction Ltd v London Portman Hotel Ltd, set out the following criteria that should be considered when calculating a “fair and reasonable” extension of time.

See below:

"Roger Toulson QC who, in the case of John Barker Construction Ltd v London Portman Hotel Ltd, set out the following criteria that should be considered when calculating a “fair and reasonable” extension of time:

apply the rules of the contract.
recognize the effects of constructive change.
make a logical analysis, in a methodical way, of the effect of relevant events on the contractor’s programme and
calculate objectively, rather than make an impressionist assessment of the time taken up by the relevant events."

The video above shows a delay analysis over 15 updates (inclusive of the baseline). The data is taken direct from the P6 SQL database and both a DYNAMIC and an AS-PLANNED v AS-BUILT delay analysis is provided for both. Notice the difference!!!!

From start to finish, the data from SQL is extracted then modified, formatted and the two differing delay analysis critical paths (across multiple updates) are provided in 30 MINUTES.

We call the above the : DYNAMIC versus the AS-PLANNED v AS-BUILT DELAY ANALYSIS CALCULATOR.

WE ARE WORKING ON CODE TO DO THIS EVEN FASTER and we should be able to get , for example, 86,000 relationships across 12 updates data processed for delay analysis for both dynamic and as-planned v as-built critical paths down to about 5 minutes.

Planners who use P6 will know that to download a 42,000 activity programme will probably take about 45 minutes to load up from an XER file. So going direct to the database "ONLY MAKES SENSE".

Also, the WBS is broken down to provide activity codes at all WBS levels, this means dynamic filters can be used and the Dynamic and As-planned v As-built critical paths can be analysed for any discipline, sub project(s), set of trades or just for a trade.

Likewise, another software called: "PLANNED % COMPLETE v ACTUAL % COMPLETE" will provide dynamic line graphs. Progress can then be reviewed graphically and graphs can be provided at the click of a button. The WBS (Activity Code) dynamic filter will provide a planned % v actual % graph for any discipline, sub project(s), set of trades or just for a trade also.