A modern Primavera Risk Analysis (Pertmaster) alternative

Primavera Risk Analysis owns deep, decades-hardened Monte Carlo — but it is end-of-life Windows desktop. CritPath AI brings AACE 132R-23 Level 4 rigor, CCPM/TOC, decision gates, and a schedule-aware AI copilot to the web.

Last updated: July 2026

Primavera Risk Analysis (PRA), still widely known by its original name Pertmaster, is the tool many project-controls analysts learned quantitative schedule risk analysis (QSRA) on. Its Monte Carlo engine is deep and battle-hardened: tornado sensitivity, criticality and cruciality indices, duration and cost risk, and AACE-style risk-driven outputs that have carried owner- and regulator-grade credibility for two decades.

It is also effectively frozen. PRA sits in Oracle's Controlled Availability program — no longer freely sold, running on a roughly 2013-era codebase, Windows-desktop only, with no AI and a UX shaped by the EPC and oil-and-gas world it was built for. If you run R&D programs — biotech IND timelines, deep-tech hardware, federally funded research — you inherit construction-shaped assumptions, an analyst-gated workflow, and a perpetual seat that typically runs $10,000+. CritPath AI is built for the opposite: the same AACE 132R-23 Level 4 rigor, but with CCPM, Theory of Constraints, decision gates, and a schedule-aware AI copilot, in a modern web app at $10/user/month.

CapabilityCritPath AIPrimavera Risk Analysis
Monte Carlo schedule riskYes — PERT-Beta, risk-event injection, criticality index, tornado sensitivity, P50/P80/P90, optional correlationYes — deep, decades-hardened engine; tornado/criticality, cost-risk, correlation (its core strength)
Critical Path Method (CPM)Yes — 4 dependency types, lag, float, near-critical analysisYes — mature CPM scheduling
CCPM / TOC / Drum-Buffer-RopeYes — critical chain, project + feeding buffers, fever chart, DBRNo — not supported
Decision gates with retroactive reschedulingYes — Go/No-Go/Pivot/Defer gates that re-cascade the scheduleNo — not supported
Schedule-aware AI copilotYes — Claude + Gemini, grounded in the live dependency graphNo — no AI (legacy desktop, ~EOL)
Modern web UX / self-serveYes — browser app, multi-tenant, collaborative, self-serve sign-upNo — Windows desktop only, analyst-gated, ~2013 codebase
AACE 132R-23 Level 4 + audit trailYes — risk-driven scheduling with an append-only audit logAACE-style QSRA, but construction-shaped and not R&D-native
Price$10/user/month (AI usage billed separately, metered)Perpetual ~$10,000+/seat plus annual maintenance (reportedly; not SaaS)

Where Primavera Risk Analysis is genuinely strong

It would be dishonest to pretend PRA is weak at its core job. Its Monte Carlo simulation has been refined for twenty years and remains a reference implementation for QSRA. It models three-point and many-parameter distributions, correlates durations, runs risk registers against the schedule, and produces tornado charts, criticality indices, and probabilistic finish dates that hold up to scrutiny in front of owners and auditors.

That maturity is real and it is earned. For EPC, oil-and-gas, and defense megaproject analysts who already live in Primavera P6, PRA's forensic depth, contract and liquidated-damages modeling, and long track record are advantages a newer tool has to respect rather than dismiss. CritPath competes on fit, modernity, and breadth of method — not by claiming PRA's engine is bad.

Where Primavera Risk Analysis falls short for R&D

The gaps are structural, not cosmetic. PRA is Windows-desktop software with no SaaS, no real-time collaboration, and no mobile access — one analyst runs it and exports a static report. Its Controlled Availability status means there is no active product roadmap and no AI of any kind. And its model of the world is construction: activities, calendars, and cost risk, with no concept of the methods R&D programs actually need.

Specifically, PRA has no Critical Chain Project Management, no Theory of Constraints or Drum-Buffer-Rope, no decision gates, and no WSJF or Cost of Delay. For a biotech program where a CMC vendor slip should re-cascade the whole plan, or a deep-tech team gating on a TRL milestone, those are the techniques that matter most — and they are exactly the ones a 2013 desktop risk tool was never designed to carry.

  • End-of-life: Controlled Availability, ~2013 codebase, no roadmap.
  • Windows desktop only — no web, no collaboration, no mobile.
  • No AI copilot, schedule-aware or otherwise.
  • No CCPM, TOC/DBR, decision gates, or WSJF/Cost of Delay.
  • Perpetual seat typically $10,000+, plus annual maintenance, analyst-gated.

What CritPath AI does instead

CritPath AI keeps the rigor and modernizes everything around it. Its Monte Carlo engine runs PERT-Beta distributions with risk-event injection, criticality index, tornado sensitivity, optional duration correlation, and P50/P80/P90 finish dates — the probabilistic core PRA users expect. On top of that it layers a full Critical Path Method (four dependency types, lag, float, near-critical analysis), CCPM with Theory of Constraints and Drum-Buffer-Rope (drum, project and feeding buffers, fever chart), decision gates with retroactive rescheduling, WSJF and Cost of Delay, and EVM.

All of it carries AACE RP 132R-23 Level 4 risk-driven scheduling with an append-only audit log, and all of it runs in a browser with multi-tenant orgs, 2FA, and XLSX/CSV import. The differentiator PRA cannot match is the AI copilot: built on Claude and Gemini and grounded in your actual dependency graph, it can tell you which task is driving your P80 slip and what a gate decision does downstream — reasoning over the real engine, not a chatbot pinned on top.

Primavera Risk Analysis vs. CritPath AI

The table below compares the two on the capabilities that decide an R&D schedule-risk purchase. Competitor figures are reseller-derived and approximate; pricing for a perpetual desktop license drifts and is quoted here for orientation only.

Which should you choose?

If you are a project-controls analyst on an EPC or defense megaproject, already standardized on Primavera P6, and you need PRA's forensic contract-and-cost-risk depth in front of an owner, the incumbent's twenty-year track record is a legitimate reason to stay. CritPath does not claim to out-forensics PRA on its home turf today.

But if you run R&D programs and want probabilistic dates plus CCPM buffers, TOC constraints, and decision gates that re-cascade the schedule — accessible to a whole program team in a browser, with an AI copilot that explains why a date moved — CritPath AI occupies a quadrant PRA cannot reach. You get AACE-grade risk-driven scheduling without a $10,000+ perpetual seat, an analyst bottleneck, or a frozen 2013 desktop product.

Frequently asked questions

Is Primavera Risk Analysis discontinued?

Effectively. Primavera Risk Analysis (Pertmaster) sits in Oracle's Controlled Availability program — it is no longer freely sold, runs on a roughly 2013-era codebase, and has no active roadmap or AI. It still works for existing analysts, but it is not being modernized.

Does CritPath AI match Primavera Risk Analysis's Monte Carlo?

CritPath runs PERT-Beta Monte Carlo with risk-event injection, criticality index, tornado sensitivity, optional duration correlation, and P50/P80/P90 dates. PRA's engine is older and deeper on forensic cost-risk and contract modeling for EPC work; CritPath matches the probabilistic schedule core R&D programs need and adds CCPM, TOC, and decision gates PRA lacks.

How much does Primavera Risk Analysis cost vs. CritPath AI?

PRA is a perpetual desktop license — reportedly around $10,000+ per seat plus roughly 22% annual maintenance, quoted via reseller. CritPath AI is $10 per user per month with every standard feature, and AI copilot usage billed separately by metered token usage.

Can CritPath AI replace Primavera Risk Analysis for AACE compliance?

CritPath ships AACE RP 132R-23 Level 4 risk-driven scheduling with an append-only audit log. That covers risk-driven QSRA rigor for R&D and federal programs. For EPC forensic contract/liquidated-damages modeling, PRA remains deeper in its lane today.

Why move from a desktop risk tool to a web app?

A desktop tool like PRA means one analyst runs the model and exports a static report. CritPath runs in the browser so a whole program team can collaborate, gates re-cascade the schedule in real time, and an AI copilot grounded in the live dependency graph explains what changed and why.

Related

See the math on your own schedule

CritPath AI is $10/user/month — real Monte Carlo, CCPM, decision gates, and a schedule-aware AI copilot. Join the waitlist for beta access.

Join the waitlist