Impacted As-Planned Delay Analysis : Using Primavera P6 to see combined / consolidated effect from some or all delay events

Analyzing Combined Delay Events in Primavera P6 Without Creating Multiple Projects

In a typical delay analysis scenario, suppose a project experiences five distinct delay events. If we want to analyze the combined impact of Delay Event 1 and Delay Event 2, we traditionally create a new project that includes only those two events. Then, to analyze Delay Event 1 and Delay Event 3 together, we create yet another project. This process continues, and we may end up managing over 20 separate project files.

Now imagine that the baseline schedule requires a minor correction—such as adding a single relationship. That change would need to be applied to all 20+ project files individually. Clearly, this is inefficient and time-consuming.

This article introduces a more efficient approach: using Primavera P6’s Multi-Project Scheduling feature to analyze the combined effects of delay events—without creating dozens of separate projects.

Step-by-Step: Using Multi-Project Scheduling for Delay Analysis

Let’s assume we have a baseline schedule, as shown in the image below:

We represent each of the five delay events in separate project files:

Viewing the Impact of a Single Delay Event

To analyze the effect of Delay Event 1:

1. Open the Baseline project and the Delay Event 1 project.
2. Press F9 to schedule.
3. In the Schedule Options dialog, check the box:
   “Ignore relationships to and from other projects.”

After scheduling, you’ll see the impact of Delay Event 1 on the baseline.

Result: Extension of Time (EOT) = 15 days

Repeat the same steps for Delay Event 2:

• Open Baseline and Delay Event 2
• Press F9
• View the result:
  EOT = 10 days

Viewing the Combined Impact of Multiple Delay Events

To analyze the combined effect of Delay Event 1 and Delay Event 2:

1. Open Baseline, Delay Event 1, and Delay Event 2
2. Press F9 to schedule

Result: EOT = 25 days

You can repeat this process to analyze any combination of delay events—without duplicating projects. Simply open the relevant delay event files alongside the baseline and schedule them together.

We can also see the combined effect of all delay events: