Tutorial:

Description:

Delay analysis is one of the most critical aspects of project controls, especially for planners, schedulers, and claim analysts working with Primavera P6.
Among the several methodologies recognized by AACE International, one of the most practical and defensible approaches is the Multiple Simulation Technique, which effectively combines Windows Analysis and Time Impact Analysis (TIA) into a single, hybrid process.

This combined technique provides a realistic, evidence-based representation of project performance, it analyzes both what actually happened (observational view through Windows Analysis) and what could have happened (prospective modeling through Time Impact Analysis).
It is widely used in complex engineering, oil & gas, and infrastructure projects where transparency, consistency, and contractual defensibility are essential.

In this article, we’ll explore three practical scenarios that explain how to implement the Multiple Simulation Technique effectively inside Primavera P6:

• Scenario 1 – Windows Analysis:
  The first scenario demonstrates how to perform Windows Analysis on a monthly basis, dividing the project into analysis windows to observe real progress, track changes in the critical path, and assess delays period by period.
• Scenario 2 – Time Impact Analysis (Windows Method with Logic Override):
  The second scenario focuses on performing a Time Impact Analysis using actual dates and the Progress Override option in Primavera P6 — a method often required by clients for consistency and transparency in contractual delay assessments.
• Scenario 3 – Single Delay Impact on Entire Project:
  The third scenario explains how to handle situations where a single dominant delay event affects the entire project. It describes a simplified, quick Time Impact Analysis approach to evaluate the overall impact efficiently without conducting multiple detailed simulations.

Together, these three scenarios illustrate a complete framework for delay analysis in Primavera P6, combining forensic accuracy, AACE compliance, and practical project control insight.

Scenario 1: Windows Analysis (Observational Delay Review)

The Windows Analysis method divides the project schedule into smaller, logical time segments — usually monthly or quarterly “wThe Windows Analysis method divides the project schedule into smaller, logical time segments — usually monthly or quarterly “windows.” Each window allows the planner to observe how delays evolved, how the critical path shifted, and how progress compared to the baseline.

Step-by-Step Procedure

1. Perform the Windows Analysis Monthly

Break the project into monthly update periods to isolate and measure slippages.

2. Analyze Overall and Sectional Milestones

Assess delay impact on both overall completion and sectional milestones.

3. Evaluate Each Delay Event Separately

Analyze each delay within its window for traceable and precise cause-effect understanding.

4. Remove Out-of-Sequence Activities

Before running schedules, fix logic issues to maintain accurate results.

5. Check Activity Calendars

Ensure each activity uses the correct working calendar, especially when multiple calendars exist.

6. Organize Window Files Properly

For each window, maintain a record folder containing:

7. Save Each Baseline as a User Baseline

This allows consistent referencing and transparent audit trails.

This observational method (AACE RP 29R-03) forms the foundation for professional forensic delay analysis, ideal when detailed project updates are available.

Scenario 2: Time Impact Analysis (Windows Method with Logic Override)

The Primary Baseline is the main reference baseline that you choose for performance measurement. It is the baseline that PriIn many projects, the client or consultant specifies that the only acceptable delay analysis method is:

“Time Impact Analysis (Windows Analysis) using actual dates with Logic Override.”

This hybrid instruction means the analysis should be carried out window by window, using actual site progress and Progress Override logic in Primavera P6.

1. Where Is This Requirement Found?

This requirement often appears in the Employer’s Requirements or Special Conditions of Contract.
It’s not an AACE rule but a client-specific requirement — designed to ensure all contractors use a consistent, transparent, and verifiable method.

2. Why Time Impact Analysis (Windows Method)?

This method merges Windows Analysis (observational) and TIA (prospective) — a balanced approach endorsed by many international projects.

3. Methodology in Primavera P6

 This creates a transparent, defensible demonstration of delay impacts consistent with AACE RP 29R-03 and RP 52R-06.

4. Benefits and Risks

5. Why Clients Prefer It

This approach enforces discipline, avoids manipulation, and ensures all contractors analyze delays consistently.
Using Progress Override mirrors real site execution, not theoretical sequencing, making it a balanced but slightly client-favored method.

When the Entire Project Is Affected by a Single Delay

Sometimes, one dominant delay can affect the entire project for example, a late land handover, design approval, or long-lead material issue.
In such cases, a full window-by-window TIA may not be necessary. Instead, a quick Time Impact Analysis can efficiently determine the overall delay impact.

How to Perform a Quick TIA

1. Insert the Delay Activity After Its Related Task
   Place the delay directly after the activity it impacts.
2. Reconnect All Dependent Activities
   Re-establish logic links to ensure accurate delay propagation.
3. Run and Compare
   Reschedule to see how much the delay extends the finish date.
4. Assess Results
   The difference between pre- and post-impact schedules shows total delay duration.

Why This Works

This simple yet powerful method is ideal when:

It ensures technical accuracy while saving time — without compromising logic integrity or transparency.

CONCLUSION

Effective delay analysis is the cornerstone of fair and transparent project management. The Multiple Simulation Technique, as applied in Primavera P6, offers planners and claim analysts a balanced framework that combines accuracy, clarity, and defensibility.

This hybrid methodology — blending Windows Analysis and Time Impact Analysis (TIA) — aligns closely with AACE Recommended Practice 29R-03 and 52R-06, ensuring compliance with internationally accepted forensic scheduling standards.

Through the three scenarios described in this article, we’ve explored how this technique can be applied in real project environments:

• Scenario 1 – Windows Analysis:

This observational method breaks the project into monthly or quarterly windows to study how progress, slippages, and critical paths evolved over time. It focuses on what actually happened, allowing planners to trace the cause and effect of every delay using transparent, evidence-based data.

• Scenario 2 – Time Impact Analysis (Windows Method with Logic Override):

This scenario introduces the contractually preferred approach used by many clients — the Windows-based TIA performed with Progress Override. It combines real progress data and delay event modeling, providing a clear, defensible timeline of delay impacts. This method ensures consistency, fairness, and visibility, benefiting both the Employer and the Contractor.

• Scenario 3 – Quick TIA for a Single Global Delay:

Sometimes, one dominant delay — such as land handover, drawing approval, or design change — controls the entire project. This simplified TIA approach allows planners to model the event quickly by inserting the delay fragnet, reconnecting logic, and observing its total effect on the completion date. It is practical, efficient, and fully defensible when supported by accurate data.

Together, these three techniques represent a complete forensic toolkit for analyzing delays in Primavera P6. The Multiple Simulation Technique enables you to:

In today’s construction and EPC industries, where schedule performance often determines contractual outcomes, mastering these methods in Primavera P6 is not just a technical skill — it’s a professional advantage.

The Multiple Simulation Technique empowers planners to deliver analyses that are accurate, data-driven, and defensible — ensuring that both Employers and Contractors can reach fair conclusions based on real project behavior, not assumptions.

Whether you are preparing a claim submission, defending a delay analysis, or auditing project performance, applying this structured approach will strengthen your credibility and align your work with international best practices.

PLANNING P6 TUTORIALS

Complete Tutorial How to prepare extension of time claims | How to prepare delay analysis | #WIA_TIA

#Primavera_P6 How to do delay analysis by using Time Impact Analysis Technique | Methodology for TIA

Time and Window Impact Analysis TIA and WIA Method | Delay Analysis Techniques | #planningp6 | #WIA

How to Conduct Project Delay Analysis | Prepare Extension of Time Claim | EOT | Planning P6 | Claims

Delay Analysis Techniques | Extension of Time | EOT | Claim Management | Claim Digger | Primavera P6

PLAYLISTS