Engine / Scenarios

Scenarios

Model the behaviour a spreadsheet cannot: cascades, mutually exclusive risks and conditional responses — as visual rules or as script, dry-run before you commit.

Engine / Scenarios

Model What Actually Happens, Not What Fits a Spreadsheet.

Real projects have behaviour: one delay cascades into the next, two risks cannot both occur, a team outsources when a date slips. Build that as visual rules or write it as script — the same engine runs either. Dry-run before you commit.

3 rules · 2 active
WHEN·Risk
AND IFActivity
CHANCEWith probability%
THEN+=//d
WHEN·Risk
AND IFRisk
CHANCEWith probability%
THENSet Riskoccurred =
WHEN·Activity
CHANCEWith probability%
THEN+=//€k
References valid2 active rules

Toggle a rule and hit Re-run — the dry-run samples 1,000 iterations and reports the finish shift the enabled rules add.

scenarios / rule typeslive
01Probabilistic cascades — one risk triggers the next
02Mutually exclusive risks that cannot both occur
03Conditional responses driven by dates or critical path
04Probabilistic linking and branching logic
05Non-existence rules that suppress a risk entirely
06Rules phased before or after schedule and cost analysis
07Graphic builder and script view over one engine
08Dry-run preview before the rule reaches a real run
01 / At a Glance

What You Get

  • Visual rule builder and equivalent script
  • Cascades, exclusivity and conditional responses
  • Dry-run preview of the finish shift before committing
02 / Next Step

See It on Your Own Project.

Start your Demo and run your first Monte Carlo analysis on your own schedule, or talk to sales and we will take you through it on a sample project. No card needed.

Talk to Sales