Critical Delay and Its Classifications:

Types of Delays

Schedule Delay Analysis is typically used to support EOT claims.

Numerous critical path-based delay analysis approaches are used to show the effects of delay events and then to assign blame for these delays to the accountable party. The following are the main techniques:

1. As-Planned Impacted Analysis

2. As-Built But For Analysis (Or Collapsed As-Built)

3. As Planned vs As-Built Analysis

4. Time Impact Analysis

The new SCL protocol has added 2 more delay analysis methodologies namely:

5. Time Slice Windows Analysis, and

6. Longest Path Analysis

But several variants in the above two additional methodologies but they are not commonly used

Delay Analysis Methodologies

1. Impacted As-Planned Analysis

This method involves the analysis of the Contractor’s As-Planned Programmed.

The critical path is re-analyzed to determine the impact to the As-Planned program when delay events are added to it as time-duration activities. If one occurs, the ensuing delay will serve as the foundation for an EOT claim.

Strengths & Weakness

It is easily understood.

It is appropriate for modest projects where the parties desire an expedited resolution.

Weaknesses:

It is a theoretical analysis that disregards actual development or the situation on the ground.

It is not appropriate in situations when there are many concurrent delays since it is difficult to analyze and assign responsibility for them.

2. As-Built But For Analysis (Or Collapsed As-Built)

This approach entails examining the Contractor’s As-Built Program.

The As-Built programme isolates delay events as time-duration activities. Then, these occurrences are logically eliminated, and the earlier theoretical completion date that results is contrasted with the actual completion date.

The project’s delay is the difference between the two due dates; delays are categorised based on who is to blame for them, and claims can be made as a result. To provide the correct response for EOT claims, only the delays for which the Contractor is not responsible are deleted.

Strengths & Weakness

The analysis is supported by factual information because the delays are real.

Even without a baseline or as-planned program, analysis can still be done.

Weaknesses:

It is quite challenging to implement on complicated programs.

Additional logical connections will need to be made, and this can be altered, making the analysis prone to bias.

The existence of an as-built critical path is still up for discussion, which is subjective.

3. As-Planned vs As-Built

Comparing the As-Planned and As-Built programmes is part of this strategy.

This approach, which is frequently employed in EOT claims, is based on an examination of the differences in the length of the two program. This variation is properly supported by a 'Cause & Effect' analysis that describes the delay- and disruption-causing events and their influence on the programs.

Strengths & Weakness

This analysis is ideal for straightforward programs and is simple to comprehend.

When there is doubt about the validity of baseline and/or modified programs, it is typically used.

A common-sense approach is used instead of complex software-based modelling.

Weaknesses:

This analysis required experts to utilize their practical planning or project management skills to determine the project’s critical route based on a thorough examination of the supporting documentation.

However, different experts can come to differing findings, which could spark a lot of discussions.

4. Time Impact Analysis (TIA)

With this approach, delay events are included into the As-Planned program as they happen. In order to determine how these occurrences may affect the project’s critical path and completion date in the future, the critical path is then reanalyzed.

Contrary to some other methodologies, TIA is a 'predictive' or 'prospective' method; as such, it should not be used as a 'retrospective' tool to analyze delays long after they have occurred, but rather, it should be used dynamically throughout the course of the project to predict how delay events will affect the project critical path and completion date.

Strengths & Weakness

When employed concurrently, that is, at the time the delay events occurred, they are very helpful in proving delay.

Promotes settling EOT disputes in a proactive manner as required, for instance, by various standard forms of contract.

Weaknesses:

The analysis of complicated program is tough and generally difficult.

It needed a lot of precise data, including a realistic and doable baseline or as-planned program.