Integrated cost‑loaded schedule risk. Ours to run.
QSCRA is a complete alternative to Safran for combined schedule + cost risk. It ships only when the internal Monte Carlo engine clears the validation milestones we publish below.
One model. Both axes. One audit trail.
Cost-loaded schedule risk modelling is hard because the cost dimension and the schedule dimension move together. Today most teams run two models, two tools, two audit chains — then reconcile by hand. QSCRA models them together — one set of iterations, one joint outturn.
- Single integrated model — schedule risk drives cost via resource loading; cost risk drives schedule via funding gates.
- Same audit chain as QSRA + QCRA — replay, sign-off, defensibility carry through.
- Same export formats — Excel, Weblink HTML, PDF, PPTX. Briefings address joint outturn, not two separate tables.
- Safran-benchmarked — we benchmark every Monte Carlo scheme against Safran and share the per-scheme comparison under NDA before release.
Defensibility before speed.
Replacing Safran is a serious claim. We won't make it until the maths is validated, the test suite is exhaustive, and we can show the regulator how every number was produced. The engine/qscra/ placeholder lives in the active codebase. Real code lands when V2.0 is ready to be defensible.
The validation milestones that gate V2.0.
We won't ship a Safran replacement on a "trust us" basis. Before QSCRA leaves the placeholder package, we have to clear the bar on each of the following — publicly, on benchmark schemes, with the variance band stated. We benchmark every Monte Carlo scheme against Safran and share the per-scheme comparison under NDA. Parity validation is ongoing; we publish the benchmark register to procurement teams on request.
- Schedule‑side parity — P50, P80 and P90 finish dates benchmarked against Safran across our benchmark suite, with the comparison shared under NDA.
- Cost‑side parity (post‑QCRA) — P50, P80 and P90 outturn benchmarked against Safran on the cost‑loaded benchmark scheme, with the comparison shared under NDA.
- Joint outturn convergence inside 10,000 runs, without auto‑extending silently. Convergence diagnostic plotted on every run.
- Audit‑replay determinism — byte‑identical re‑run on every benchmark scheme, on every supported platform, across at least three released versions.
- At least one external reviewer (academic or industry) signs off the methodology pack before V2.0 ships to a client.
Each milestone has a target date in the internal V2.0 plan. We'll share that plan under NDA with serious procurement teams. We won't publish a release date we aren't confident in.
Plan QSCRA into your three‑year horizon.
The roadmap is published so you can plan around it. If a combined schedule + cost view sits in your three‑year plan, ask us where we are against the milestones above. We'll show you.