Etihad Rail is the UAE’s national railway, a 1,200-kilometre network connecting Abu Dhabi, Dubai, Sharjah, Fujairah, and Ras Al Khaimah with freight and passenger services. Stage Two, the $11 billion backbone of the network, is under active construction with passenger services targeted for 2026. The project spans desert terrain, mountain passes through the Hajar range, and urban corridors through some of the fastest-growing cities in the world. With China Railway Construction Corporation, Samsung C&T, and Vinci leading construction packages across five geographic segments, the scheduling complexity demands more than deterministic planning. It demands quantitative schedule risk analysis.
Importing P6 schedules into Safran Risk is the critical first step in any quantitative schedule risk analysis on UAE infrastructure projects. Safran Risk reads Primavera P6 XER and XCR files, preserving the full logic network, calendars, and resource assignments so the Monte Carlo simulation runs against the actual project schedule rather than a simplified summary.
The import process is where most QSRA models fail silently. A corrupted calendar, a broken logic link, or a missing constraint in the source P6 file will propagate through every Monte Carlo iteration and produce results that look precise but are fundamentally wrong. On a programme like Etihad Rail with multiple EPC packages, each with its own P6 schedule containing thousands of activities, getting the import right is not a technical detail. It is the foundation of the entire risk analysis.
This article provides a step-by-step guide to importing P6 schedules into Safran Risk for QSRA, using Etihad Rail’s multi-package programme as the practical example throughout.
Why the P6-to-Safran-Risk Import Matters More Than You Think
The import is not just file loading. It is the first quality gate of the QSRA. Safran Risk performs a schedule health check during import that reveals issues the P6 user may never have noticed: open-ended activities without successors, negative float caused by imposed constraints overriding logic, dangling logic that creates artificial critical paths, and calendar inconsistencies between resources and activities. On Etihad Rail, where each segment contractor maintains their own P6 schedule, these issues compound across package boundaries.
IQRM’s seven-phase QSRA methodology places the schedule health check as Phase 1 precisely because a flawed schedule produces meaningless simulation results regardless of how carefully risks are identified and quantified. For the full QSRA methodology, see Schedule Risk Analysis (QSRA): Guide to Monte Carlo + Examples.
Step-by-Step: Importing a P6 Schedule into Safran Risk
Step 1: Export from Primavera P6
Export the schedule as an XER file (Primavera’s native exchange format) rather than XML. XER preserves calendar definitions, resource assignments, activity codes, and WBS hierarchy more reliably than XML export. For Etihad Rail, export each construction package separately to maintain clean package boundaries in the risk model. Ensure the export includes all activity codes that will be used for risk mapping and correlation grouping.
Step 2: Pre-Import Schedule Health Check
Before importing into Safran Risk, run a schedule quality check in P6 to identify and fix critical issues. The key metrics to verify: logic density (relationships divided by activities) should exceed 1.5, open ends should be zero, negative float activities should be reviewed and constraints relaxed where possible, and lag usage should be minimised. On a multi-segment programme like Etihad Rail, each package should meet these thresholds independently before import.
Step 3: Import into Safran Risk
In Safran Risk, create a new project and select Import from Primavera P6. Choose the XER file, map the calendar and resource definitions, and confirm the WBS structure. Safran Risk will flag any import anomalies: activities with zero duration, milestones without logic, and calendars that conflict with resource assignments. Address every flag before proceeding to risk assignment.
Step 4: Validate the Imported Schedule
After import, run a deterministic calculation in Safran Risk and compare the completion date with the P6 source. The dates should match exactly. If they diverge, the most common causes are calendar mapping errors (Safran Risk interpreting P6 calendars differently), constraint handling differences, and resource levelling settings. On Etihad Rail, IQRM found that calendar discrepancies between the P6 global calendar and activity-level calendars caused a 3-week divergence on one package that would have corrupted every simulation iteration.
| Common P6 Import Issue | Impact on QSRA | Fix |
|---|---|---|
| Open-ended activities | Simulation cannot calculate total float; activities drift unrealistically | Add successor logic to all open ends in P6 before export |
| Hard constraints overriding logic | Masks true critical path; simulation shows false confidence | Replace Mandatory/Finish On constraints with As Late As |
| Calendar mismatch | Dates diverge between P6 and Safran Risk; results unreliable | Map all P6 calendars explicitly during import; verify deterministic match |
| Excessive lags | Lags hide real work; uncertainties cannot be assigned to them | Convert lags into explicit activities that can receive risk distributions |
| Resource levelling in P6 | Safran Risk does not replicate P6 resource levelling; dates diverge | Export the levelled schedule (locked dates) or use Safran Risk’s own levelling |
Linking Multiple P6 Packages in Safran Risk
Etihad Rail’s programme comprises five geographic segments, each with its own P6 schedule. To model programme-level risk, all five schedules must be linked in Safran Risk using interface milestones. The most common interfaces on a linear railway programme are: track handover between segments, signalling system integration points, testing and commissioning dependencies that span multiple segments, and shared logistics facilities.
In Safran Risk, import each package as a separate project within a single plan file. Then create external dependencies between the interface milestones. When the simulation runs, delays in one package cascade through the interface links to downstream packages, capturing the programme-level schedule exposure that isolated package analyses miss entirely.
Programme P80 = Latest Package P80 + Interface Risk Buffer
Etihad Rail example: Individual packages show P80 at Q3 2026. Linked programme model with interface risks shows P80 at Q1 2027, a 6-month difference invisible without integration.
Best Practices for P6-to-Safran-Risk Import on UAE Mega-Projects
First, establish a schedule quality standard that all contractors must meet before their P6 files are accepted for QSRA import. On Etihad Rail, IQRM recommends a minimum logic density of 1.5, zero open ends, no more than 5 percent of activities with hard constraints, and lag usage below 10 percent of total relationships.
Second, always verify the deterministic date match between P6 and Safran Risk before assigning any risks. A mismatch means the simulation base is wrong, and no amount of careful risk modelling will fix a corrupted foundation.
Third, convert significant lags into explicit activities. A 30-day lag representing “curing time” or “authority approval” cannot receive a risk distribution in Safran Risk. Converting it to a named activity allows the analyst to assign appropriate uncertainty ranges. For how sensitivity analysis reveals which of these activities drive the most schedule risk, see Sensitivity Analysis in Schedule Risk: Tornado Charts and Risk Drivers.
Fourth, use P6 activity codes to create risk mapping groups in Safran Risk. Activity codes for discipline, location, and contractor allow the analyst to assign risk distributions to groups of similar activities efficiently rather than one activity at a time. On a 10,000-activity schedule like Etihad Rail, this reduces risk assignment from weeks to days.
Frequently Asked Questions
How do you import a P6 schedule into Safran Risk?
Export the P6 schedule as an XER file, create a new project in Safran Risk, select Import from Primavera P6, map calendars and resources, then validate by comparing the deterministic completion date in both tools. The dates must match exactly before proceeding to risk assignment.
What format should I use to export from P6 for Safran Risk?
Use XER format rather than XML. XER preserves calendar definitions, resource assignments, activity codes, and WBS hierarchy more reliably. Safran Risk reads XER and XCR files natively, maintaining the full logic network including relationships, constraints, and float calculations.
What are common P6 import errors in Safran Risk?
The most common issues are calendar mismatches causing date divergence, open-ended activities without successors, hard constraints masking the true critical path, excessive lags that cannot receive risk distributions, and resource levelling settings that produce different results in each tool.
How do you link multiple P6 schedules in Safran Risk for a programme QSRA?
Import each package as a separate project within a single Safran Risk plan file. Create external dependencies between interface milestones across packages. This allows the Monte Carlo simulation to capture how delays in one package cascade through to downstream packages, revealing the true programme-level schedule exposure.
What is Etihad Rail?
Etihad Rail is the UAE’s $11 billion national railway connecting Abu Dhabi, Dubai, Sharjah, Fujairah, and Ras Al Khaimah. The 1,200-kilometre network is being delivered in stages, with freight operations already active and passenger services targeting 2026 launch.
What schedule quality metrics should a P6 file meet before QSRA import?
IQRM recommends a minimum logic density of 1.5 (relationships divided by activities), zero open-ended activities, no more than 5 percent of activities with hard constraints, and lag usage below 10 percent of total relationships. Meeting these thresholds ensures the simulation base is analytically sound.
IQRM delivers specialist training in Safran Risk, Primavera P6, and quantitative schedule risk analysis for rail, infrastructure, and EPC mega-projects across the UAE and the GCC. Our QRM Diploma programme equips professionals with the practical skills to import, model, and interpret QSRA results on real multi-package programmes.
Learn more about the QRM Diploma →
Need help setting up QSRA on your UAE infrastructure project? IQRM provides Safran Risk model builds, P6 schedule health checks, 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.
