TIA in P6

8/9/2019 TIA in P6

http://slidepdf.com/reader/full/tia-in-p6 1/14

Delay Analysis Methodology

Time Impact Analysis©Focus Planning Ltd

8/9/2019 TIA in P6


DisclaimerInformation contained within this presentation is for education purposesonly. How a programme or schedule is built maintained and managed isthe responsibility of the owning organisation. Focus Planning Ltdaccepted no responsibility for changes made to programmes or

schedules which are altered as a result of reading slides contained withinthis presentation. !he con"guration and settings of computer softwareare the responsibility of the license holders and Focus Planning Ltdaccept no liability for the con"guration used by the license holder.

8/9/2019 TIA in P6


#hat is !ime ImpactAnalysis$

!ime Impact Analysis is a method of calculating the delay to a pro%ectbased on the delay to pro%ect completion and was de&eloped byMD'(ystemsLtd. It is normally associated with being a best practicemethod for assessing a single delay on the critical path of a pro%ectschedule that is in progress.

!he analysis loo)s to compare the schedule pre*delay to the schedulewith the delay included. It loo)s to calculate the duration &ariancebetween the two schedules to pro&ide the contractor with a basis forestimating the delay impact.

!ime Impact Analysis is best used to calculate delays loo)ing forwardrather than bac) other methods such as As*+uilt +ut*For ,A++F- canbe more accurate for calculating retrospecti&e delay. ,(eehttp//www.slideshare.net/Adam0arnham/delay*analysis*methodology*asbuilt*butfor*&ariation*in*p1 -

©Focus Planning Ltd 2

http://www.slideshare.net/AdamGarnham/delay-analysis-methodology-asbuilt-butfor-variation-in-p6




8/9/2019 TIA in P6


Process (teps

In order to successfully identify the delay the following stepsshould be followed3


1 2 3 4 5

6 7 8 9

8/9/2019 TIA in P6


(tep 5 Determine the +aseline

(chedule

!he "rst step in completing a !IA is todetermine the correct baseline schedule to %udge the delay against. Most construction

contracts will contain clauses relating to the6agreed7 or 6con"rmed7 baseline although thisis often an implied rather than regimented

factor. #hate&er contract mechanics are in

place the 'ontractor should loo) to determinethe correct baseline to use for the analysis andto re&iew the baseline to ensure it isreasonable for the pro%ect.


8/9/2019 TIA in P6


(tep 9 Determine As*+uilt data

source

!his would normally be the updatedschedule but again contractually it isimportant to agree what schedule &ersion to

use. 'ontracts such as :;' determine theschedule as the 6Accepted Programme7. !hemechanics of which schedule to use will bedetermined usually by the contract in place.

<nce this has been agreed assign thebaseline from (tep 5 to this pro%ect in P1.


8/9/2019 TIA in P6


8/9/2019 TIA in P6


(tep 4 Model delay using fragnetAt this stage we will loo) to model the delay according to the logicand duration decided by the pro%ect team. !his is the basis for theclaim. !o do this create a copy of the schedule and enter thedelay as a new acti&ity/s and logically lin) to the successors on

the critical path according to the build process. Do not rescheduleyet @ the purpose of the fragnet at this stage is to con"rm the

delay logic and relationship to the current programme foracceptance.

©Focus Planning Ltd

8/9/2019 TIA in P6


(tep 4 Model delay using fragnet

<nce the fragnet has been entered and con"rmed by theplanner this will need communicating to the pro%ect team toallow them to comment on the logic and placement of thedelay. <nce all are in agreement and acceptance with thefragnet detail this will need to be )ept aside ready for (tep 8.

©Focus Planning Ltd B

8/9/2019 TIA in P6


(tep 8 Merge fragnet with current

schedule:ow the fragnet has been accepted by the pro%ect team it will needincorporating in to the current schedule.

0oing bac) to the current schedule ta)e a new baseline to record the

dates per*fragnet. !his baseline is for records purposes and does notneed assigning at this stage.

:ow using the accepted fragnet enter the delay acti&ities in to the

current programme with the logic as agreed and lin) to the eCected

successors in the schedule.

:ow reduce the delay acti&ities durations to ero days and re*

schedule the pro%ect. !he Pro%ect 'ompletion date should still remainthe same as the new acti&ities ha&e ero duration. As we assigned thebaseline in (tep 9 you can chec) this is the case by adding the

baseline bars in the 0antt 'hart or by adding the Variance – BL Project

Finish Date column to the acti&ity table ,&alue should be ero-

©Focus Planning Ltd 5E

8/9/2019 TIA in P6


(tep 1 pdate Delay Durations

:ow the fragnet has been entered it is time to enter the delaydurations against the delay acti&ities.

!o do this enter the duration against the acti&ities in the originalduration "eld this should then be mirrored in the remaining and atcompletion duration "elds.

Ge*schedule and you will see the bars from the fragnet increase andthe remaining acti&ities push out mo&ing the pro%ect completion date.


8/9/2019 TIA in P6


8/9/2019 TIA in P6


(tep ;nter Delay Actuals

!he "nal step is to enter the Delay actual dates. If this is a calculationof an upcoming delay there will be no actual dates on the delayacti&ities and the results from (tep ? should be communicated.

If this is an ongoing delay the actual delay start date should comefrom the last schedule update. In order to enter these you will need

to assess when the successor to the delay becomes critical. As youwill remember from 'ritical Path Analysis the acti&ity becomes criticalat the late start date so the delay start date will be the successororiginal late start date 5day. Mar) this date as the delay start dateand reschedule.

For more information on 'ritical Path Analysis see3http//www.slideshare.net/Adam0arnham/guide*to*the*critical*path*and*critical*path*analysis


http://www.slideshare.net/AdamGarnham/guide-to-the-critical-path-and-critical-path-analysis




8/9/2019 TIA in P6


(tep B 'ommunicate the !IA

:ow you can communicate the completed !IA to the pro%ect andcommercial teams ready for a cost analysis process to ta)e place.

As well as displaying the 0antt 'hart the following columns can alsobe helpful in communicating the delays3

BL Project Start @ the original planned start date for acti&itiesBL Project inis! @ the original planned "nish date for acti&itiesStart @ the new start date with the delay includedinis! @ the new "nish date with the delay includedAct"al Start @ the actual start date with the delay includedAct"al inis! @ the actual "nish date with the delay included

#ariance $ BL Project inis! %ate @ the &ariance in Finish datesbetween the original planned "nish and the delay included "nish.


TIA in P6

Documents

Transcript of TIA in P6