The Impacted As-Planned method measures the impact of the delays on the as-planned schedule. The delays are formulated as activities and added to the as-planned schedule showing the effect of each delay and demonstrating how the project is being delayed. The amount of delay equals the difference in completion dates between the schedules before and after the impacts.
We have an As-Planned schedule.
We will insert Delay event into our schedule.
Enter Duration of the delay. Then Assign the right successor (which activity the delay will affect).
For example Duration of the “Design Changes” delay is 14 days. And it will affect “House Walls” activity.
Use Activity constraint to identify when the delay happen.
After insert all of Owner delay, running F9 and we will have the final result.
The total Extension of Time is 161 – 112 = 49 days
Have you considered filtering to the longest path, deleting the Total Float column, and adding a Variance BL1 Finish Date Column to your Gantt chart? That would focus on the important metrics and eliminate the need to perform any math.
LikeLike
Hi David,
I don’t know that method. Is it a certified method for Delay analysis?
It’s would be great if you can share an example or an article explaining in more detail about it.
LikeLike
The method explained by Doduykhuong is that of a simple case, with the assumption that the baseline schedule is fully logic driven and all the relationships are true under all conditions. But this is not the situation in most EoT cases. Further, the As Planned As Impacted method is not accepted by many current legal entities. For more complex programmes, you have to resort to As Progressed As impacted method, where, each delay event is to be incorporated in the programme updated for progress upto the start of the delay event. It is also necessary that any illogical relationships among the future activities are corrected as and when noticed and contractor should carry out mitigation adjustments, if the contract calls for such measures by the contractor.
LikeLike
Don’t you use a predecessor for the delay events?
LikeLike