Scribd
Upload
291 views11 pages

ABBF Analysis in P6

As-built but for analysis for claims in P6

Uploaded by

RenoMasr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPSX, PDF, TXT or read online on Scribd
291 views11 pages

ABBF Analysis in P6

As-built but for analysis for claims in P6

Uploaded by

RenoMasr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPSX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Delay Analysis Methodology

A variance on the As-Built-But-For


Analysis using P6

Focus Planning Ltd

Disclaimer
Information contained within this presentation is for education purposes
only. How a programme or schedule is built, maintained and managed is
the responsibility of the owning organisation. Focus Planning Ltd
accepted no responsibility for changes made to programmes or
schedules which are altered as a result of reading slides contained within
this presentation. The configuration and settings of computer software
are the responsibility of the license holders and Focus Planning Ltd
accept no liability for the configuration used by the license holder.

What is As Built But-For


Analysis
As-Built But-For Analysis (for ease referred to here as ABBF) is a method of analysing
the delay on a schedule after the fact.
Long International summarise it as,
The as-built but-for analysis subtracts compensable delays from the as-built
schedule for each schedule window to determine the earliest date that the contractor
could finish its work absent compensable delays. The cumulative amount of
compensable delay calculated from all schedule windows using the as-build but-for
analysis represents the total amount of delay for which the Contractor is entitled to
recover extended field and home office overhead costs.
Richard J.Long, Andrew Avalon, Ronald J.Rider, Long International Schedule and Delay Analysis Methodologies, 2013.

What ABBF looks to answer is When would we have finished if the delay had not
occurred? And What was the impact on the actual critical path?
ABBF looks at the actual critical path rather than the planned, as the planned critical
path can change on various occasions throughout the life of the project. We will look
at how to complete this analysis in Primavera P6, this is a slight variation but to
software limitations.
Focus Planning Ltd

Step 1 The As Built


Schedule

Take a copy of the schedule (including all baselines) and open the copy in the
Activities window. Identify the activities you need to calculate delay against
(known as the Window). Ensure all activities within the window are marked
with the Actual Start and Actual Finish dates. This is the As-Built schedule. Add
two milestones called Window Start and Window Finish ,logically link as
the first and last activities in the window and mark as complete. This helps to
define the Window Period.

Focus Planning Ltd

Step 2 As Built Logic


In the copy, remove all activity relationships from the completed activities,
and rebuild the logic according to the sequence they were actually completed.
This will form the As-Built critical path.

Focus Planning Ltd

Step 3 De-progress The


Schedule
Ensure the At Complete Durations match the Original Durations for each
activity and apply the mandatory start constraint to match the start dates,
then remove the actual start and finish dates. Reschedule to the window start
data date. The schedule should be identical to the as-built one along the
critical path but the bars will be green to confirm they are not-started. Take a
new baseline called as-built.

Focus Planning Ltd

Step 3a Identify the


Critical Path

As the As-Built logic was determined in Step 2, you can now remove the
constraints holding the activities in place and re-schedule to the window start
data date. Activities on the critical path should remain the same as the as-built
dates, other activities not on the critical path may differ because there actual
start date will not be directly dictated by the predecessor, this can be
corrected using lag on the relationship but is not required as we are only
concerned with activities along the critical path. You now have a clear As-Built
critical path.

Focus Planning Ltd

Step 4a Compensable Implicit


Delays
Adjust the At Complete durations on activities which have delay included in
them that are on the critical path. For example say we know that Activity 8
includes 2 days worth of documented delays, reduce the duration by 2 days
and reschedule the plan. Take a baseline called Implicit Delay variance.

Focus Planning Ltd

Step 4b Compensable Explicit


Delays
If the schedule contains Explicit Delays (dedicated delay activities in the
schedule) then amend the logic to ignore these activities and continue on the
Critical Path. For example lets say Activity 9 was entered as Delay 2, this
activity will be ignored and the logic amended from Activity 8 to Activity 10.
Reschedule to the window start data date. Take a baseline called Explicit Delay
Variance.

Focus Planning Ltd

Step 5 Variance Reviews


Now that the As-Built critical path has been established, and all delays recorded then
removed, we can review what the Finish date for the window would have been had the
delays not occurred. First assign the following baselines;
Project Baseline = As Built Baseline from Step 3
Primary Baseline = Implicit Delay Variance from Step 4a
Secondary Baseline = Explicit Delay Variance from Step 4b
Right click the Gantt Chart, select Bars, and tick Project, Primary and Secondary Baseline
boxes to add the bars to the Gantt Chart. Also tick Baseline Milestone.
Add the following columns to the activity table to give you the results of the analysis;
BL Project Start - The As-Built Start
BL Project Finish The As-Built Finish
BL1 Start The planned start with implicit delays removed
BL 1Finish The planned finish with implicit delays removed
BL2 Start The planned start with implicit and explicit delays removed
BL2 Finish The planned finish with implicit and explicit delays removed
Variance BL Project Duration The variance between the as-build plan including all
delays and the plan excluding all delays, a positive figure indicates the number of days
the window was delayed. The variance on the last activity on the critical path is the
overall delay duration.
Focus Planning Ltd

10

Summary
So to summarise this variation on the As-Built But-For Analysis in P6
provides the project stakeholders with the following information;
The impact of implicit delays on the window finish
The impact of explicit delays on the window finish
The overall impact of all delays on the window finish
By comparing multiple baselines taken as the delay periods were
calculated we are able to see a timeline of the calculations used to
generate the claim for delays which can be issued to stakeholders as
required in a single Gantt chart, rather than separate pages of data.
Other Delay review methods including Time Impact Analysis will be
covered in future slides and a copy will be made available on the
Focus Planning Ltd website at http://www.focus-planning.com or by
contacting [email protected]
Focus Planning Ltd

11

You might also like