What You Get
- Map risks to activities or cost elements
- WBS tree with search and bulk expand
- Undo/redo on every mapping change
Link each risk to the activities and cost elements it actually drives — the step that turns a register into a quantitative model.
Mapping is where a register becomes a model: point each risk at the activities and cost elements it actually drives, and the engine knows what to move. Walk the WBS, search by name, tick the links — undo anything.
| Id | Description | ||||||
|---|---|---|---|---|---|---|---|
| OP-100 | Offshore Platform v4.05.02 — UNDER REVIEW | ||||||
| 2 | Key Milestones/Governance Milestones | ||||||
| 2 | Governance Milestones | ||||||
| CP.3.01 | |||||||
| CP.7.01 | |||||||
| CP.5.01 | |||||||
| CP.4.01 | |||||||
| CP.6.01 | |||||||
| 1 | Other | ||||||
| CP.3.02 | |||||||
| CP.3.03 | |||||||
| CP.3.04 | |||||||
| 3 | Key Standard Milestones | ||||||
| KSM - 1.01 | |||||||
| KSM - 1.02 | |||||||
| KSM - 1.03 | |||||||
| KSM - 1.04 | |||||||
| KSM - 1.05 | |||||||
| KSM - 1.06 | |||||||
| KSM - 1.07 | |||||||
| KSM - 1.08 | |||||||
| KSM - 1.09 | |||||||
| KSM - 1.10 | |||||||
| KSM - 1.11 | |||||||
| KSM - 1.12 | |||||||
| KSM - 1.13 | |||||||
| KSM - 1.14 | |||||||
| KSM - 1.15 | |||||||
| 4 | Engineering & Procurement | ||||||
| ENG-120 | |||||||
| ENG-140 | |||||||
| PRC-330 | |||||||
| PRC-360 | |||||||
| 3 | Fabrication | ||||||
| FAB-180 | |||||||
| FAB-210 | |||||||
| FAB-260 | |||||||
| 3 | Offshore Installation | ||||||
| INST-380 | |||||||
| INST-400 | |||||||
| INST-440 |
Discrete risks are only half the model — every activity also carries duration uncertainty. Group the schedule by WBS level, give each branch a percentage band, and apply it to hundreds of activities at once instead of typing ranges one by one.
Group activities by WBS and assign duration uncertainty
| WBS Code | Name | Tasks | Group |
|---|---|---|---|
| OP-100 | Offshore Platform v4.05.02 — UNDER REVIEW | 282 |
Not every relationship is certain. Give a predecessor link or a successor branch its own probability and the engine draws it per iteration — so the logic itself varies, the critical path can move between runs, and conditional scope stops being modelled as though it always happens.
| Id | Description | Type | Prob. |
|---|---|---|---|
| FAB-260 | Load-out & sea fastening | — | |
| CP.4.01 | CP4 — Technical Solution Design Phase | — | |
| INST-380 | Transport & float-over | — |
| Id | Description | Type | Prob. |
|---|---|---|---|
| A9999 | QSRA Finish Milestone | — | |
| CP.5.01 | CP5 — Procurement Phase | — | |
| INST-440 | Ready for start-up (RFSU) | — |
Tick a box to give each relationship its own probability — the link is then drawn per iteration instead of always existing.
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