QSRA for Airport Mega-Projects: Schedule Risk Analysis on King Salman International Airport

---

Why King Salman International Airport Needs QSRA

The King Salman International Airport project operates within constraints that make schedule risk analysis non-negotiable. The project scope includes:

A deterministic schedule—one baseline plan with no risk buffers—cannot account for these realities. QSRA provides the quantitative framework to acknowledge uncertainty, model interaction effects, and communicate confidence to stakeholders with three critical confidence levels: P50 (50th percentile, 50% probability of completion on or before date), P80 (80% confidence), and P90 (90% confidence).

For King Salman, achieving 2030 operational readiness on T1 requires not an optimistic single date, but a range: "We are 50% confident we will open by X date (P50), 80% confident by Y date (P80), and 90% confident by Z date (P90)." This transparency drives appropriate reserve allocation and stakeholder buy-in.

---

Understanding QSRA: The IQRM 7-Phase Framework

Schedule Risk Analysis: The Complete Guide provides the foundational framework. The IQRM methodology structures QSRA into seven sequential phases that build analytical rigor and ensure no risk factor is overlooked.

[IQRM 7-Phase QSRA Workflow]

Phase 1: Schedule Foundation and Validation

The analysis begins with the baseline schedule. For King Salman, this means validating that all 2,000+ activities are logically linked, durations are realistic (not padding-inflated), and interdependencies between phased terminals, airfield works, and systems integration are accurately modeled. Common errors at this stage include missing links between T1 and T2 work, overstated contractor availability, and underestimated commissioning periods for ATC systems.

The schedule must represent current project reality: which contractors are on-site, which work packages are in design versus execution, what regulatory gates are locked, and what external dependencies (government approvals, supply chain timing) are real. At King Salman, this validation typically surfaces that commissioning timelines for air traffic control systems were unrealistic without parallel runway construction completion.

Phase 2: Risk Identification and Register Build

This phase catalogs schedule risks specific to airport mega-projects. For King Salman, the risk register captures:

Phase 3: Probability and Impact Assessment

Each risk is quantified on two dimensions: probability (likelihood it will occur) and impact (days of schedule delay if it does). At King Salman, a sandstorm risk might carry 60% probability and 3-5 day impact on earthworks. A design change to terminal gate configuration carries 40% probability and 15-30 day impact on structural scheduling.

This phase also identifies risk correlation: if a design change occurs, it typically triggers both contractor rework and regulatory re-inspection. QSRA methodology captures these dependencies, preventing artificial schedule compression that assumes all risks resolve independently.

Phase 4: Schedule Risk Modeling and Simulation

This is where QSRA diverges from traditional scheduling. Rather than a single deterministic path, we build a probabilistic model. Using tools like Safran Risk integrated with Primavera P6, we assign probability distributions (not fixed durations) to high-risk activities. An earthworks activity with base duration of 60 days becomes a triangular distribution: optimistic 55 days, most likely 60 days, pessimistic 75 days, reflecting weather and site variability.

Monte Carlo simulation then runs the schedule 5,000-10,000 times, sampling from each risk distribution on each iteration. The result is not a single completion date, but a distribution of outcomes. King Salman's T1 opening date, modeled with full risk, might show:

This is not prediction failure; it is honest uncertainty communication. A 9-month window between P50 and P90 reflects the genuine variability inherent in a $33 billion, 2,000-activity schedule across 57 square kilometers and 200+ contractors.

[CDF S-Curve for King Salman Airport Project Completion]

Phase 5: Sensitivity and Criticality Analysis

Not all risks equally impact the final date. Sensitivity analysis identifies which schedule activities, when delayed, have the highest likelihood of delaying project completion. This is visualized through tornado charts: a horizontal bar chart where the longest bars represent the activities with highest schedule sensitivity.

For King Salman, Sensitivity Analysis and Tornado Charts in Schedule Risk typically reveal that runway surfacing completion dominates the sensitivity list—a 30-day delay to runway surfacing directly cascades to ATC system commissioning, taxiway opening, and ultimately operational readiness. In contrast, some terminal interior finishes show low sensitivity because they can occur in parallel with runway certification.

This phase also quantifies criticality: the percentage of Monte Carlo iterations where an activity lies on the critical path. An activity with 95% criticality must be actively managed; one with 20% criticality has more flexibility for absorbing delays.

Phase 6: Reserve and Contingency Planning

QSRA output directly informs reserve calculation. If the baseline schedule shows T1 opening in Q2 2030, but P80 analysis shows Q4 2030, the difference is the management reserve required to achieve 80% confidence. For King Salman, this might translate to 90-180 days of project-level schedule reserve, allocated strategically to critical activities based on sensitivity analysis.

Reserve is not a blanket contingency; it is surgical deployment based on quantitative analysis. High-criticality, high-sensitivity activities receive reserve; low-sensitivity activities receive less. This approach prevents over-buffering (wasting reserve on low-risk activities) and under-buffering (exposing critical risks).

Phase 7: Implementation, Monitoring, and Scenario Planning

QSRA does not end with the analysis; it becomes the scheduling discipline. As King Salman progresses, actual performance is tracked against the probabilistic baseline. If earthworks complete faster than the P50 distribution predicted, that risk category is updated. If a regulatory inspection reveals rework, the impact is quantified and re-analyzed.

This phase also includes scenario planning: "If T1 structural work slips 60 days, what is the impact to T2 start?" QSRA enables rapid re-modeling of what-if scenarios, supporting management decision-making under uncertainty.

---

[Tornado Chart of Schedule Risk Drivers for Airport Construction]

Airport-Specific Risk Factors in QSRA Modeling

Phased Terminal Delivery and Dependency Chains

King Salman's phased delivery (T1 in 2030, T2 in 2035, potential T3) creates serial dependencies. T2 cannot begin detailed design until T1 structural lessons are learned. T2 sitework cannot begin until T1 site access is relinquished. These dependencies are modeled explicitly in QSRA, with conditional risk triggers: "If T1 structural rework occurs, probability of T2 design delay increases from 30% to 60%."

Airfield Works and Runway Commissioning

Airfield works are singularly critical for airport projects. Runway preparation, taxiway construction, apron paving, and lighting systems must achieve FAA/ICAO certification before a single commercial flight. Weather impacts are severe: extreme heat affects asphalt curing, sandstorms halt earthmoving, seasonal rain (rare but possible) floods drainage systems.

QSRA models these as compound risks: runway foundation completion is "most likely 120 days; pessimistic 180 days due to weather; optimistic 100 days if equipment availability is higher than expected." Pavement certification adds another gate: "testing and re-paving, if defects found, adds 15-45 days." Monte Carlo simulation chains these together, surfacing the true distribution of runway operational readiness.

Air Traffic Control Systems Integration

ATC systems represent the interface between civil construction and operational complexity. Installing radar, communications, and automation systems requires parallel civil construction (tower building, cable ducts, power infrastructure), then integration, testing, and FAA certification. Delays in any upstream activity (electrical rough-in, concrete curing, equipment manufacturing) cascade to ATC readiness.

QSRA explicitly models this: the ATC installation task has dependencies on civil completion (tower structure, cable ducts), equipment delivery (supplier delays), and testing gates (FAA certification windows, which may be quarterly). A single supplier delay to specialized ATC hardware can shift the ATC operational date by 2-3 months.

Multi-Contractor Interface Risks

With 200+ contractors, interface risks are endemic. Mechanical contractor A must coordinate with electrical contractor B on cable trays and power distribution. Both depend on civil work by contractor C. If C delays, both A and B are delayed—but the schedule might not reflect this if interfaces are not explicitly modeled.

QSRA methodology captures this by mapping predecessor-successor relationships across contractors and adding explicit "coordination/interface buffer" activities between major handoffs. These buffers are probabilistically distributed: best case 5 days (smooth handoff), most likely 10 days, worst case 20 days (rework required).

Regulatory Compliance Gates

FAA/ICAO certification, Ministry of Transportation approval, and operational readiness inspections are external hard-stops. They cannot be crashed or paralleled; they occur in sequence. Each gate introduces schedule uncertainty: inspection scheduling might slip 2-4 weeks; rework from inspections might require 10-30 days; re-inspection might be scheduled 6 weeks later.

QSRA models these gates with probabilistic durations reflecting historical timelines from comparable airports. If certification testing fails and rework is required, the downstream date shifts by the rework duration plus the re-inspection scheduling lag.

---

Implementing QSRA at King Salman: Practical Tools and Workflows

Tool Integration: Safran Risk + Primavera P6

Primavera P6 maintains the baseline schedule: 2,000+ activities, logic links, phased delivery structure, and contractor assignments. P6 is the source of truth for schedule structure and relationships.

Safran Risk is the quantitative risk modeling engine. It integrates with P6, imports the schedule structure, and adds probabilistic distributions to activities. Safran runs Monte Carlo simulations, generates P50, P80, P90 Confidence Levels Explained, creates tornado charts, and produces S-curves showing cumulative probability of completion over time.

The workflow is iterative: baseline schedule updates in P6 flow to Safran Risk. Risk register changes (probability, impact, correlation) are updated in Safran. Monte Carlo re-runs produce updated P50/P80/P90 forecasts. Reports are shared with steering committees quarterly, with transparency on forecast changes and risk drivers.

S-Curve Visualization and Confidence Lanes

Safran Risk generates S-curves: smooth cumulative probability curves showing the likelihood of completion on any given date. King Salman's T1 opening might show:

Confidence Level	Estimated Date	Probability of Completion
P10 (Optimistic)	June 2030	10% chance of completion by this date
P50 (Most Likely)	September 2030	50% chance of completion by this date
P80 (High Confidence)	December 2030	80% chance of completion by this date
P90 (Very High Confidence)	March 2031	90% chance of completion by this date

S-curves are presented to stakeholders as confidence lanes: the area between P80 and P90 represents the "likely range"; dates outside this range are increasingly unlikely but possible. This visualization removes ambiguity from schedule forecasts and aligns stakeholder expectations with realistic timelines.

Tornado Charts and Risk Prioritization

Tornado charts rank activities by sensitivity. For King Salman's T1 opening, the top five sensitivities might be:

Activity	Sensitivity (Days of Impact per Day Delay)	Mitigation Strategy
Runway Surfacing and Certification	1.0x (1:1 impact)	Accelerate equipment procurement; parallel curing testing
T1 Structural Completion	0.95x	Front-load concrete pours; maximize crew shifts
ATC System Installation and Testing	0.85x	Early vendor engagement; parallel pre-commissioning
Baggage System Integration	0.70x	Modular design enabling phased integration
Terminal MEP Rough-In Completion	0.65x	Pre-fabrication and parallel zone work

These sensitivities directly inform where management focus and resources should concentrate. Runway surfacing, with 1.0x sensitivity, demands continuous attention and resource protection. Baggage system integration, with 0.70x sensitivity, has more flexibility for absorbing delays.

---

Risk Mitigation Strategies Informed by QSRA

---

Key Metrics and Reporting for Stakeholders

QSRA reporting to executives and government stakeholders must be clear and decision-oriented. Key metrics include:

---

Common Challenges and Lessons Learned

Challenge: Schedule Not Realistic to Begin With

Some mega-projects enter QSRA analysis with aggressive base schedules that are already optimistic. QSRA will then show extremely wide P80/P90 ranges, causing alarm. The lesson: QSRA is only as good as the baseline schedule. Before Monte Carlo simulation, invest time in schedule validation, contractor feedback, and reality checks. A realistic base schedule might be less ambitious, but QSRA analysis will be credible and actionable.

Challenge: Risk Correlation Complexity

In large schedules, risks interact: a design change triggers both rework and regulatory re-inspection. A contractor delay cascades to dependent work packages. Naive QSRA (treating all risks independently) dramatically underestimates uncertainty. The lesson: explicitly model correlations. If design change probability is 40%, and regulatory re-inspection is triggered 70% of the time when design changes occur, link these in the risk register. Safran Risk supports correlation matrices; use them.

Challenge: Reserve Depletion and Scope Creep

QSRA generates a schedule reserve aligned to P80 or P90 confidence. As the project executes, scope creep, design changes, and minor risks consume reserve faster than expected. By mid-project, P80 reserve might be consumed, and the forecast has reverted to P50 (50% confidence). The lesson: protect schedule reserve. Separate scope changes from risk absorption. If scope is genuinely added, adjust the baseline schedule; do not consume risk reserve for scope. Reserve protects against uncertainty in the approved scope.

Challenge: Stakeholder Expectation Management

When QSRA reveals that a 2030 target is only 50% likely (P50) and 80% confidence requires 2031, stakeholders may react with skepticism or denial. Resistance manifests as "just make it 2030" or "reduce scope." The lesson: frame QSRA early, before high-level commitments are made. Present P50/P80/P90 as the baseline contract target should be negotiated around P80, not P50. This aligns risk responsibility: if the owner commits to 2030 (P50), the contractor accepts 50% probability of penalty; if 2031 (P80), risk is shared more fairly.

---

Conclusion: QSRA as a Strategic Tool for King Salman and Mega-Projects

QSRA for airport mega-projects is not complexity for its own sake; it is clarity under uncertainty. King Salman International Airport's $33 billion cost, 57 square kilometer footprint, 200+ contractors, and 2030 target demand quantitative schedule risk analysis. A single-date promise ("Opening 2030") masks the reality: 50% chance, 80% chance, or 90% chance?

The IQRM 7-phase QSRA framework, implemented with Primavera P6 and Safran Risk, transforms the schedule from a guess into a probability distribution. P50/P80/P90 confidence levels replace false certainty with honest uncertainty communication. Tornado charts and sensitivity analysis focus management attention on activities that truly matter. Monte Carlo simulation captures the complexity of 2,000 interdependent activities, weather risks, contractor coordination, and regulatory gates.

For King Salman, implementing QSRA early (ideally during design/planning phases, before construction begins in earnest) enables:

Mega-airport projects like King Salman are won or lost on schedule performance. Late opening damages reputation, strands tenant revenues, and triggers contractual penalties. QSRA is the discipline that transforms schedule management from art to science, from guesswork to quantitative rigor. For Rami Salem and IQRM clients managing billion-dollar infrastructure, QSRA is the competitive advantage.

---

Frequently Asked Questions

---

Ready to Master Schedule Risk Analysis?

QSRA is a learned discipline, not an intuition. If you're managing mega-projects, you need quantitative rigor. IQRM's Quantitative Risk Analysis course trains project managers, schedulers, and controls specialists in the complete 7-phase QSRA methodology, Monte Carlo simulation, tool integration (Safran, Primavera), and stakeholder reporting.