Scenario Logic
Model behaviour a fixed network cannot show: probabilistic links and branches, rules that fire on conditions in each iteration, and a scripted layer run in a sandbox.
How It Works
Link and Branch
On Mappings, give a link a probability, or branch the network between alternatives.
Write a Rule
When a risk occurs, an activity runs long, lands on the critical path or passes a date, set a duration, force or suppress a risk, move a start, turn off a branch or set a cost.
Pick When It Runs
Rules run before the CPM pass, after it, or after costs.
Preview
Preview the rule before you save it.
Or Script It
Write the logic as a script instead. It runs in a sandbox in every iteration.
Details
What You Get
- Probabilistic linking and branching, plus a scripted scenario layer run in a sandbox.
- A rule can fire on every iteration or with a probability.
- Conditions combine with all or any.
- Graphic and Script views of the same logic.
Limits and Conditions
- Float, critical path and date conditions work only in rules that run after the CPM pass.
- Previewing a rule needs an analyst seat.
Related Features
- QRA Engine
Schedule and CPM
Edit the project schedule in the browser with a grid and a Gantt chart, reschedule on our servers, and use the same network in every simulation iteration.
- QRA Engine
Risk Mapping and Risk Types
Map each risk to the activities and cost elements it would hit, choose how its impact applies, and model risk types a register alone cannot hold.
- QRA Engine
Monte Carlo Simulation
Run the project’s schedule, risks and costs through a Monte Carlo simulation on our servers, and read the P80 for the finish date and the cost.