What Safran Risk is used for
- QSRA: confidence finish dates and schedule contingency.
- QCRA and integrated analysis: cost loaded onto the schedule, so time-driven costs grow when the schedule slips.
- Joint Confidence Level: the probability of meeting cost and schedule targets together.
- Pre- and post-mitigation runs: the value of each mitigation in weeks and money.
Features practitioners rely on
| Feature | Why it matters |
|---|
| Risk register linked to the schedule | Each risk is mapped to the activities it affects, with probability and impact ranges |
| Correlation | Stops the model treating related activities as independent and understating risk |
| Calendar and weather risk | Models seasonal limits such as GCC summer working restrictions or marine weather windows |
| Probabilistic branching | Represents outcomes such as a failed test leading to rework |
| Criticality and sensitivity outputs | Shows which paths and risks drive the finish date |
Safran Risk and Primavera Risk Analysis
Primavera Risk Analysis (formerly Pertmaster) was the standard QSRA tool for many years, and many models still run in it. Teams choosing a tool today often pick Safran Risk for its integrated cost and schedule handling and its correlation features. The method is the same in both; the quality of the schedule and the inputs matters more than the tool.
A typical QSRA workflow in Safran Risk
Import and check
Import the P6 XER, then fix logic, constraints and open ends.
Apply uncertainty
Add three-point duration ranges and calendar risk.
Map risks
Link register risks to activities and set correlation.
Simulate and report
Run the simulation, read the S-curve and tornado, and test mitigations.
Common mistakes
- Learning the buttons, not the method. A clean-looking model on a weak schedule still gives the wrong P80.
- Skipping correlation. The default of independent activities narrows the S-curve.
- Importing without a health check. Constraints and lags carried over from P6 distort the results.
Related terms
