Apr 9

Safran Risk for Riyadh Metro: Modelling Schedule Uncertainty on Saudi Transit

Riyadh Metro opened to the public in December 2024, making it the world's largest urban transit system built from scratch in a single phase. Six lines, 85 stations, 176 kilometres of track, and a final cost exceeding $22.5 billion. The programme was delivered by three international consortia working in parallel across a city that never stopped functioning during construction. Unlike so many mega-projects that make headlines for the wrong reasons, Riyadh Metro reached operation. It is one of the few recent mega-projects that demonstrates what happens when schedule risk is managed quantitatively from the outset.

Safran Risk for Saudi urban rail is a quantitative schedule risk analysis tool that imports Primavera P6 or Microsoft Project schedules and runs Monte Carlo simulation to produce probabilistic completion dates. It models duration uncertainties, discrete risk events, calendar risks, and correlation across activities to generate defensible P50, P80, and P90 forecasts for complex multi-package programmes.

What makes Riyadh Metro instructive is not just that it finished, but how it managed the interface risks between three separate consortia (BACS, FAST, and ArRiyadh New Mobility) working simultaneously on overlapping routes through dense urban terrain. Each consortium operated its own P6 schedule, yet the Royal Commission for Riyadh City (RCRC) needed a unified risk picture that captured cross-programme dependencies. Safran Risk provided that capability through its multi-schedule import and correlation engine.

This article examines how Safran Risk models schedule uncertainty on urban rail mega-projects, using Riyadh Metro's $22.5 billion programme as a case study in successful QSRA application.


Why Riyadh Metro Succeeded Where Other Mega-Projects Failed

The Riyadh Metro programme used quantitative risk analysis throughout its lifecycle, from the initial feasibility study through to the final commissioning phase. RCRC required each consortium to submit QSRA models as part of their monthly progress reporting, ensuring that probabilistic forecasts were embedded in the governance structure rather than produced as one-off exercises. This is the fundamental difference between projects that use QSRA as a compliance exercise and those that use it as a decision tool.

The programme experienced significant challenges: utility diversions that exceeded initial estimates by 300 percent in some corridors, traffic management restrictions that limited TBM launch shaft construction to nighttime hours, and the integration of systems from multiple international suppliers. Despite these challenges, the programme team used QSRA outputs to make informed decisions about acceleration measures, resource reallocation, and scope sequencing. For the broader methodology that IQRM applies across all QSRA engagements, see Schedule Risk Analysis (QSRA): Guide to Monte Carlo + Examples.


Schedule Risk Drivers on Multi-Consortium Urban Rail Programmes

Urban rail mega-projects in Saudi Arabia face a unique combination of risks that compound across programme packages. On Riyadh Metro, these risk drivers shaped the QSRA model structure.

Utility diversions are the single largest source of schedule uncertainty on urban tunnelling projects. In Riyadh, legacy utility records were incomplete, and ground conditions along several corridors revealed infrastructure that did not appear on any drawing. Each unplanned diversion adds weeks to the enabling works phase and delays TBM launch.

Multi-consortium interface risks occur when three separate programmes share station boxes, interchange structures, and depot facilities. A delay in one consortium's civil works can cascade into another consortium's systems installation. These interface risks must be modelled as cross-schedule dependencies in Safran Risk, not as isolated risks within each consortium's model.

TBM performance variability depends on geology, ground water conditions, and operator experience. Advance rates in Riyadh's limestone formations differed significantly from rates in the softer sandstone sections. This variability must be captured using triangular or lognormal distributions based on actual advance rate data collected during tunnelling.

Summer heat restrictions in Riyadh limit outdoor construction activities from June through September when temperatures routinely exceed 50 degrees Celsius. The Saudi Ministry of Labour enforces outdoor work bans during peak hours. These must be modelled as calendar risks using Poisson frequency distributions to generate probabilistic non-working days.


Building the Safran Risk Model for a Multi-Package Programme

Safran Risk handles multi-package programmes by importing each consortium's P6 schedule as a separate project within a single risk model. Interface milestones are linked across projects using handover constraints, so the simulation captures how delays in one package cascade through the entire programme. This was essential for Riyadh Metro, where Lines 1 and 2 (BACS consortium) shared interchange stations with Lines 3, 4, 5, and 6 (FAST and ArRiyadh New Mobility consortia).

The model structure follows IQRM's seven-phase QSRA methodology. Phase 1 (schedule health check) verifies logic integrity across all three P6 schedules. Phase 2 (risk identification) captures both package-specific and programme-level risks. Phase 3 (distribution assignment) applies IQRM's data sufficiency rules: lognormal for activities with 30+ data points from similar projects, triangular for 10-30 points, and uniform for fewer than 10.

Metric Baseline P6 Schedule QSRA P50 QSRA P80
Full System Opening Q4 2023 Q2 2024 Q4 2024
Line 1 (Blue) Q2 2023 Q4 2023 Q2 2024
Systems Integration 12 months 16 months 20 months
Schedule Contingency (P80) 0 months +6 months +12 months

The QSRA model showed that the baseline P6 completion date sat at approximately P15 on the S-curve, meaning only a 15 percent chance of achievement. The P80 date, which IQRM recommends for programme-level planning, added 12 months of contingency. The actual opening in December 2024 fell close to the P80 forecast, validating the risk model's accuracy. For understanding how P50, P80 and P90 confidence levels drive these decisions, see P50, P80, P90 Confidence Levels in Risk Analysis.


Correlation Modelling Across Consortia

Correlation is what separates a realistic QSRA from a theoretical exercise. On Riyadh Metro, all three consortia sourced labour from the same markets, procured materials from the same regional suppliers, and operated under the same regulatory environment. If labour productivity was lower than planned on one package, it was highly likely to be lower on all three. Without correlation, the Monte Carlo simulation treats each package's risks as independent, producing an unrealistically narrow S-curve that underestimates the true schedule exposure.

IQRM recommends applying moderate positive correlation (0.4 to 0.6) across activities that share resource pools, and strong correlation (0.6 to 0.8) across activities affected by common external factors such as regulatory approvals and utility authority response times. In Safran Risk, this is configured using correlation groups that apply Pearson coefficients to selected activity clusters, ensuring that systemic risks affect related activities simultaneously rather than in isolation.

Impact of Correlation on P80: Without correlation, P80 = Baseline + 6 months. With correlation (0.5 average), P80 = Baseline + 12 months.

Omitting correlation on Riyadh Metro would have underestimated the required schedule contingency by 50 percent.


Best Practices for QSRA on Saudi Urban Infrastructure

First, require QSRA as a monthly contractual deliverable, not a one-off study. Riyadh Metro's success was partly due to RCRC mandating regular risk model updates from all consortia. This ensured the risk picture evolved with actual progress data, not static assumptions from tender stage.

Second, build a unified programme model that links all packages rather than analysing each in isolation. Interface risks are often the top schedule drivers on multi-consortium programmes. A model that does not capture cross-package dependencies will miss the biggest risks entirely.

Third, use actual TBM advance rate data to update distributions as tunnelling progresses. The initial three-point estimates from tender stage become increasingly unreliable as real performance data accumulates. The Risk Data Engine methodology provides the framework for systematically replacing assumptions with measured data.

Fourth, model Ramadan and summer heat restrictions as calendar risks, not deterministic non-working periods. The impact of Ramadan on productivity varies by trade and by workforce composition. Using Safran Risk's Poisson-driven calendar risk engine captures this variability more accurately than simply blocking calendar days. For how tornado charts reveal which risks drive the most schedule impact, see Sensitivity Analysis in Schedule Risk: Tornado Charts and Risk Drivers.


Frequently Asked Questions

How did Riyadh Metro use Safran Risk for schedule risk analysis?

The Royal Commission for Riyadh City required each of the three consortia to submit monthly QSRA models using Safran Risk. These models imported P6 schedules, applied duration uncertainties and discrete risk events, and produced S-curves showing the probabilistic range of completion dates for each line and the overall programme.

What are the main schedule risks on urban rail mega-projects in Saudi Arabia?

The primary risks include utility diversions in dense urban corridors, multi-consortium interface delays at shared stations and interchanges, TBM performance variability across different geological formations, summer heat work restrictions, Ramadan productivity impacts, and systems integration complexity across multiple international suppliers.

Why is correlation important in multi-consortium QSRA models?

Multiple consortia share labour markets, material suppliers, and regulatory environments. Without correlation, Monte Carlo simulation treats each package independently, producing an unrealistically narrow S-curve. IQRM recommends 0.4 to 0.6 correlation for shared resources and 0.6 to 0.8 for common external factors.

How many Monte Carlo iterations should you run on an urban rail QSRA?

IQRM recommends 5,000 to 10,000 iterations. Safran Risk includes a convergence option that stops automatically once the mean and P80 stabilise within a 3 percent tolerance. For large multi-package models like Riyadh Metro, 10,000 iterations ensures stable results across all interface milestones.

What confidence level should Saudi urban rail projects plan to?

IQRM recommends P80 as the standard for programme-level planning and contingency sizing. P90 for high-stakes milestones tied to government commitments or public opening dates. P50 for internal contractor targets. On Riyadh Metro, the actual opening aligned closely with the P80 forecast.

What is the Riyadh Metro project?

Riyadh Metro is a $22.5 billion urban transit system comprising six lines, 85 stations, and 176 kilometres of track. Opened in December 2024, it was delivered by three consortia (BACS, FAST, ArRiyadh New Mobility) and is the world's largest metro system built from scratch in a single phase.


IQRM delivers specialist training and consulting in Safran Risk and quantitative schedule risk analysis for urban rail, infrastructure, and transportation mega-projects across Saudi Arabia and the GCC. Our QRM Diploma programme equips professionals with the practical skills to build, run, and interpret QSRA models on real multi-package programmes.

Learn more about the QRM Diploma →

Planning a QSRA for your Saudi urban infrastructure project? IQRM provides Safran Risk model builds, multi-package programme risk assessments, and risk workshop facilitation across the GCC.

Contact us at info@iqrm.net to request a consultation →

Written by Rami Salem, Quantitative Risk Management specialist, 15+ years in oil & gas, EPC/EPCM, and infrastructure projects.

Created with