BPMN describes the flow. Simulation needs four more inputs
A BPMN diagram says which steps exist, who performs them and where the flow branches. It cannot be computed: arrival rate, spread, capacity and calendar are not part of the notation. This page covers which BPMN tools actually simulate, what their simulation does, and when you do not need the notation for the number at all.
BPMN 2.0 is a notation for the flow, not a computational model. A simulation needs four inputs that appear in no BPMN diagram: how many cases arrive, how much processing durations vary, how much capacity each role has, and which calendar applies. Tools such as Bizagi Modeler, Signavio, ARIS, Trisotech and Cardanit add these in their own dialogues, partly through the WfMC extension BPSim, partly proprietary, depending on product and edition. If you need BPMN 2.0 for a process engine or a mandate, model in BPMN. If you need the number and a process manual, skipping the notation is faster.
What BPMN contains and what it does not
The distinction is not pedantry. It explains why an imported diagram cannot be computed at the press of a button, whichever tool opens it.
What BPMN 2.0 describes: activities, events, gateways, sequence flows, pools and lanes, messages, sub-processes. In other words the structure of the flow. Complete, standardised, exchangeable between tools.
What BPMN 2.0 does not describe: behaviour under load. Four inputs are missing:
| Input | Example | Why it decides the result |
|---|---|---|
| Arrival process | 120 cases/day, peak day 180 | Without volume there is no utilisation and therefore no constraint |
| Spread of durations | processing 5–15 min instead of "10 min" | Queues come from variation, not from averages |
| Capacity per role | 3 people × 7 productive hours | Determines whether a step runs above or below 100 % |
| Calendar and cost | Mon–Fri 08:00–17:00, €53/h fully loaded | Turns waiting time into a number in money |
The WfMC extension BPSim (Business Process Simulation Interchange Standard) exists precisely for this: it attaches those parameters (arrivals, distributions, resources, costs, scenarios) to a BPMN file as a separate section. In practice its adoption is limited; most tools store simulation parameters in their own fields, which is why switching tools rarely saves you from re-entering the numbers.
The consequence for your project: importing a BPMN diagram saves you the structure, not the data. And the data is the work.
Which BPMN tools actually compute
"Simulation ✓" on a comparison page covers everything from "colours in boxes" to "discrete-event simulator". This ranking is by computational depth, not vendor size. It is a starting point for your own check, not a replacement for it.
| Tool | Kind of simulation | Note |
|---|---|---|
| Bizagi Modeler | Staged: process validation, time, resource and calendar analysis | The best-known entry point; modelling is freely usable, simulation scope depends on edition |
| SAP Signavio | Simulation module inside the suite | Its strength is the process archive and governance; simulation is one component |
| Software AG ARIS | Simulation module, historically deep | Sensible when ARIS is already in operation |
| Trisotech, Cardanit | Browser-based process simulation, close to BPMN | Smaller vendors, often more direct to operate |
| Camunda | No simulation | An execution engine: it runs real cases through the process, not simulated ones. Frequently confused |
| bpmn.io / bpmn-js | No simulation | A library for drawing and embedding, no engine |
| Simulation labs (Arena, Simul8, AnyLogic) | Very strong, BPMN usually only as an import | Compute deeper than any BPM suite, but the notation is not the model there |
Three questions to ask any vendor before committing:
- Is simulation included in this edition, or in a more expensive one?
- Does it represent queues in front of busy steps, or does it merely add processing times along the paths?
- Do I get a result as a range (P10–P90) or as a single number?
Question 2 is where the category splits. A tool that sums path durations calls its result "lead time" but means processing time. In administrative processes the difference is rarely smaller than a factor of three.
The sequence that works in practice
Not either/or. BPMN and the computational model serve different purposes.
The BPMN diagram is for systems and mandates that require BPMN: execution in a process engine, exchange as BPMN 2.0 XML, standards that demand exactly this notation.
The FlowVisual model is for decisions and operations: is this automation worth it, does the process survive double the volume, where do we add half a position. The same model produces the process manual with RACI, deputies, approvals and controls. It stays current because every change to the flow changes the manual with it.
The usual sequence:
- Capture the flow coarsely: five to ten steps, not thirty. The constraint almost never sits in the detail. Existing Visio processes are imported instead of redrawn.
- Enter volumes, ranges, capacities and rates. That is the work BPMN does not save you.
- Compute, capture before, change one lever, prove.
- Justify the decision with the result and output the process manual from the same model.
- Where a process engine or a mandate requires BPMN 2.0, also keep the flow in a BPMN tool.
Why coarse: a diagram for a process engine often has thirty activities; a computable model needs ten. Every additional activity costs five input fields without changing the result.
Why FlowVisual works with six building blocks
Six building blocks instead of a notation, on purpose.
FlowVisual knows start, step, decision, merge, abort and end. No pool, no lane, no message event, no notation validation.
Where BPMN stays: if a process engine, an exchange format or a mandate explicitly requires BPMN 2.0, keep the flow in a BPMN tool as well. FlowVisual does not export BPMN XML. It produces the process manual with flow, RACI, deputies, approvals and controls itself.
What that buys: in the workshop the department argues about the process instead of about the notation. A model stands in ten minutes rather than two hours. And every input field that exists is one that changes the result: volume, range, capacity, role, system, rate.
The rule of thumb:
- You need BPMN 2.0 as notation or XML, for a process engine or a mandate → BPMN tool.
- You need a number a decision maker will sign and a process manual that stays current → FlowVisual.
- You need both → both, each for its purpose.
The longer version of this comparison is in the article BPMN tool with simulation.
- Notation
- Six building blocks instead of BPMN 2.0; no BPMN XML export
- Import
- Visio (.vsdx) free. No BPMN XML: the structure is redrawn in ten minutes, and the data would have to be entered either way
- Engine
- Discrete-event simulation with queues in front of busy steps, Monte Carlo repetition
- Result
- Throughput, lead time, utilisation and cost as P10–P50–P90
- Recommendation
- FlowVisual for the decision and the process manual, a BPMN tool where BPMN 2.0 is required
Frequently asked
Can a BPMN diagram be simulated directly?
Not without additional inputs. BPMN describes the structure of the flow, not behaviour under load. Before any run you must supply arrival rate, spread of processing durations, capacity per role and calendar. Tools with a simulation module ask for these in their own dialogues; the standard extension for exchanging them is BPSim, which is not implemented everywhere.
What is BPSim?
The Business Process Simulation Interchange Standard from the WfMC. It attaches simulation parameters (arrivals, distributions, resources, costs, scenarios) to a BPMN file as a separate section so they become exchangeable between tools. The idea is right; adoption is limited, which means switching tools in practice usually means re-entering the numbers.
Is Camunda a simulation tool?
No, and this is one of the most common confusions. Camunda is an execution engine: it runs real cases through a BPMN process and measures what happens. Simulation computes a process that does not exist yet, for example after a planned automation. Both are useful, but they answer different questions.
How many activities should a simulation model have?
Five to ten. A documentation-grade BPMN diagram often has thirty or more, which is harmful for computation because every extra activity demands input fields without changing the result. The constraint is the step with the highest utilisation, and that is just as visible in a coarse model as in a fine one.
Does FlowVisual support BPMN?
No. FlowVisual works with six building blocks and no notation validation, and it does not export BPMN XML. It produces the flow diagram, the process manual and RACI itself. Where a process engine or a mandate requires BPMN 2.0, a BPMN tool comes in addition. The benefit of six building blocks is speed: a computable model stands in ten minutes, and in the workshop people argue about the process rather than the notation.
The number first, the diagram afterwards
Build the flow coarsely from six blocks, enter volumes and ranges, and let it run. The process manual with RACI comes from the same model.
Guide: seven steps to the number- Comparison
BPMN with simulation: what the notation can compute and what it cannot
“Our BPMN tool does simulation” means anything from a plausibility check to a full discrete-event engine, depending on the product. Five questions that tell the difference in ten minutes.
Read - Comparison
Simulating a process in Visio: why it does not work and what to do instead
“Simulate a process in Visio” is one of the most common searches in the process field. The answer is no. What is more interesting is what somebody searching that way actually needs.
Read - Comparison
Process simulation software: four categories, four purposes
“Which tool should I buy?” is the wrong question. Software for business processes falls into four categories with four different purposes. Most bad purchases happen because someone bought from the wrong category.
Read