PERFORMING IMPACT ANALYSIS FOR EXTENSION OF TIME(EoT) USING PROJECT SCHEDULE

The article emphasizes on the impact analysis using project schedule, This article is continuation of my previous article Title "PREPARING CLAIM FOR EXTENSION OF TIME (EOT)" (URL:https://www.blogger.com/blogger.g?blogID=6226101373765449612#editor/target=post;postID=2758220319089207158;onPublishedMenu=publishedposts;onClosedMenu=publishedposts;postNum=0;src=postname ). 

This article elaborates on how baseline schedule is helpful to identify and refer the delay events and the associated dependencies for the impact analysis. It has already been mentioned in my previous article that the approved baseline schedule is the pre-requisite for the claim preparation. 

The data in the Figure-1 of  Article "PREPARING CLAIM FOR EXTENSION OF TIME (EOT)" can be prepared with help of project management tool. (Same Figure is referred in this article as Figure-6).
.

Steps to perform impact analysis using project schedule

The general steps are described  with the help of an example baseline schedule.as below:

1.      Open the baseline schedule file that has been approved by the Engineer

Figure 1: Baseline Schedule

2.      In the baseline schedule identify the tasks that have been delayed.

Sr.#	Activity Name	Activity ID
1	Provision of Test Servers by Engineer	P2P1005
2	Deployment on Test Server	P2P1008

Figure 2 Dependencies/Tasks that are delayed

3.      Identify the depending activities which have the predecessors mentioned in Figure 2 Dependencies/Tasks that are delayed. These activities are halted and have not been started yet.

Sr.#	Activity Name	Activity ID
1	P2P Test of Module A	P2P1010
2	P2P Test of Module B	P2P1020
3	P2P Test of Module C	P2P1030

Figure 3 Depending Activities that have been halted

4.      For each activity identified in Figure 3 perform the following:

a.       Set the primary constraint of start date to the date when dependency is resolved..

b.      Once you set the constraint, your schedule will reflect the impact of the set constraint on the overall project. The project completion date with the impact of defined constraint is updated. The below figure depicts the new Finish date to 4 Jun 18.

Figure 4 Project completion date with impact

c.    The impact of the delay in the start of the activity” P2P1010” on the overall project timelines is shown in the table below: This table have been referred in the claim to depict the impact analysis of the subject activity.

Sr.#	Activity Head	Activity ID	Start Date  (Baseline 1)	Anticipated Start Date	Project Finish Date (Baseline 1)	Impact on Project Finish Date	Variance (days)
1	Application P2P Testing	P2P1010	19 Mar 18	15 May 18	6 May 18	4 Jun 18	29

Figure 5 Delay Analysis for the impeded task P2P1010

5.    Likewise the impact of the delay of other activities can be identified as shown in the below table:

Sr.#	Activity Head	Activity ID	Start Date  (Baseline 1)	Anticipated Start Date	Project Finish Date (Baseline 1)	Impact on Project Finish Date	Variance (days)
1	Application P2P Testing	P2P1010	19 Mar 18	15 May 18	6 May 18	4 Jun 18	29
2	P2P Test of Module B	P2P1020	26 Mar 18	15 May 18	6 May 18	28 May 18	22
3	Application P2P Testing	P2P1030	2 Apr 18	15 May 18	6 May 18	21 May 18s	15

Figure 6 Delay Analysis for the impeded tasks All P2P Testing Tasks

6.      To claim the extension you may refer to the maximum date resulting in the impact analysis as shown in Figure 10, it is imperative that the extension of time claim can be set to 4 Jun 18 as being the maximum date for the project completion.