Certra Sign in
Monte Carlo schedule risk analysis

A finish date you can defend.

Certra runs thousands of simulations over your project schedule and turns duration uncertainty and risk events into probabilities — P10, P50, P80 dates, the activities that drive them, and a report your board can read.

Self-hosted · accounts are created by your administrator
10,000
iterations per run
P10 · P50 · P80
finish dates with confidence
5
schedule formats imported natively
9
result views, one workspace
01 · Why probabilistic

A schedule is a forecast. Treat it like one.

Every deterministic plan compresses thousands of possible outcomes into a single date — and hides how likely that date actually is. Certra makes the probability explicit before you commit to it.

The deterministic plan

One date, unknown odds

The CPM finish is one path through the network with every estimate taken at face value. How much confidence does it carry? The plan cannot say.

The same plan in Certra

Every date, with its odds

Simulation turns the same network into a distribution: the deterministic date turns out to be P28 — and the date worth committing to is P80.

02 · How it works

One deterministic date in, a distribution out.

The workspace follows the analysis itself — three sections, in the order a risk engineer works.

01 · INPUT

Import the schedule

Bring the project in from Primavera, Microsoft Project, Safran or Excel. Define three-point duration uncertainty and a register of discrete risk events with probability and impact.

02 · ANALYSIS

Run the simulation

Thousands of iterations sample every duration and risk, re-run the critical-path method each time, and build the full distribution of finish dates — Monte Carlo or Latin Hypercube sampling.

03 · OUTPUT

Read the results

S-curves, tornado, criticality, probabilistic Gantt and percentile tables — plus an executive summary you can edit and export for the steering committee.

03 · The analysis

Not just a date — the reasons behind it.

Find the schedule's real drivers

The tornado ranks every activity and risk event by how much of the finish spread it explains. Mitigation effort goes where the schedule is won or lost — not where the loudest stakeholder points.

  • Duration sensitivity and risk-event impact, ranked
  • Δ days each driver adds at your confidence level

Watch the critical path move

The deterministic plan has one critical path; across 10,000 iterations it shifts. Criticality shows how often each activity really sits on it — drawn onto a probabilistic Gantt of the whole schedule.

  • Criticality index across all iterations
  • Near-critical work exposed before it bites

Interrogate the run in plain language

The AI analyst answers with the numbers of the current simulation and explores what-if scenarios — mitigate a risk, crash an activity — while the charts follow the scenario being discussed.

  • Answers cite the run's own figures
  • What-if scenarios re-simulated on the spot
Tornado — drivers of the finish date Δ days at P80
Jacket fabrication+21d
Weather — winter towing+16d
HV cable delivery+13d
Piling vessel availability+9d
Commissioning & grid tests+7d
Criticality — share of iterations on the critical path probabilistic gantt
Detailed design12%
Jacket fabrication84%
Foundations & piling61%
Turbine delivery22%
Offshore installation77%
HV cable pull-in58%
Commissioning45%
Grid acceptance91%
AI Analyst grounded in this run
Why did P80 move 12 days after the re-run?
The new risk SR-07 · grid-connection consent fires in 31% of iterations and lands on the critical path in most of them, moving P80 from 433d to 445d. Mitigating it to 15% would bring P80 back to 436d.
scenario: SR-07 mitigated — charts follow
04 · The instrument

Built for planners who read numbers all day.

Dense, flat, keyboard-friendly, every figure in tabular mono — an instrument, not a dashboard.

S-curves & percentiles

Cumulative probability of completion against the deterministic date, with P10–P90 marked and the contingency each confidence level implies.

Risk events register

Discrete risks with probability and impact, mapped to the activities they hit — simulated alongside duration uncertainty, not instead of it.

Full activity table

Per-activity percentiles, float and criticality — sortable, searchable, and consistent with every chart on screen.

Run history

Every simulation is snapshotted: compare runs as the schedule and the risk register evolve from month to month.

Reports that leave the room

A full Excel results workbook and a board-ready PowerPoint deck, generated from the run — no screenshots, no retyping.

Executive summary

A drafted, editable summary of the run in plain language — the page you hand to the steering committee.

05 · Interoperability

Your schedule, in its native format.

No conversion step: Certra reads the files your planning tools already produce.

.xerPrimavera P6
.xmlPrimavera P6 XML
.xmlMicrosoft Project
.spxSafran
.xlsxExcel workbook
06 · Deployment

Runs on your infrastructure.

Certra is self-hosted: schedules and results stay on your servers, and access is governed by your administrators.

See your schedule as a distribution.

Sign in with the account your administrator created for you.

Sign in to the platform