Understanding Windows Analysis for Delays and Extensions of Time (EOTs)
Laraib Fatima Dar (PMP)?
Planning Engineer at National Marine Dredging Company
In the world of project management, delays are often inevitable. Understanding how to analyze these delays effectively can significantly impact the outcome of a project, especially when it comes to claiming Extensions of Time (EOTs). One method widely used for this analysis is Windows Analysis.
What is Windows Analysis?
Windows Analysis is a technique used to evaluate delays in a project schedule. It breaks down the project timeline into specific "windows" or segments, allowing project managers to isolate and analyze delays more accurately. This method helps in determining whether the delays were caused by the contractor, the client, or other external factors.
Step 1: Define Your Time Windows
To begin, divide your project timeline into distinct windows, typically ranging from two weeks to one month. Each window will serve as a segment for detailed analysis.
Step 2: Gather Schedule Data
Collect all relevant data regarding the project schedule. This includes:
Having this information readily available is crucial for an accurate analysis.
Step 3: Analyze Each Window
For each defined window, analyze the activities and their respective statuses:
领英推荐
Step 4: Determine Responsibility for Delays
After analyzing the windows, determine who is responsible for each delay:
Step 5: Claim Extensions of Time (EOTs)
With the analysis complete, you can now prepare your EOT claim:
Conclusion
Windows Analysis is a powerful tool for managing delays and claiming Extensions of Time in project management. By systematically breaking down the project timeline into windows, collecting relevant data, and analyzing each segment, project managers can effectively assess delays and establish clear responsibility. This approach not only aids in claiming EOTs but also improves overall project control and transparency.
If you found this article helpful, feel free to share it with your network!
Senior Planning Engineer/ Manager
1 个月Just this much??? What about the concurrency analysis?? What about the baselines of each windowed program or each month impacted programs?? How to analyse and segregate the contractor delay and the client delay?? You need to explain it more in detail.. Windows time slice is just not fixing a 02 or a months window/segment and check the delay... If the event is ongoing for more than 02 months or so, there are other steps , which is to be checked and segregate each parties delay...
Project Controls| Power BI | Data Analysis |
1 个月Please bear with me on this but I have few questions. 1. What is the difference in Time Impact and Window analysis? 2. You mentioned that it identifies the delay is client or contractor, how will you distinguish if both are responsible? e.g drawings were delayed, but contractor was not ready to commence the works as per actual site condition, how will we settle that? 3. How will you assess the total impact of delay? 4. What is the basis of selecting the windows?
Project Management Specialist and Contract Engineer | PMP? | MSc ICME UK | SSYB | SFC
1 个月Insightful, but your article is silent on the topic of concurrency which comes under much debate when we try to fix the responsibility of the delays being Employer Events.
Senior Manager- Project Management
1 个月Very helpful