Skip to content
Process simulation software

Software that computes your process instead of drawing it

FlowVisual is a desktop process simulator for macOS and Windows. You build a flow from six blocks, enter volumes, capacities and durations as ranges, and run it as a Monte Carlo stress test. Out comes the constraint, the lead time as a P10–P90 band, and what a change is worth in money.

PlatformmacOS 12+ · Windows 10/11
First number~30 minutes
PrerequisitesNone
DataStays local
In short

Process simulation software runs a modelled flow hundreds of times with randomly drawn arrivals and processing times, then reports where cases pile up. It answers four questions a spreadsheet cannot: which step limits throughput, how long a case takes in the bad cases, where the constraint moves once you fix it, and what a change is worth in money. FlowVisual is the lean version of that. Six building blocks, first defensible run in about 30 minutes, everything local on your machine, with no account and no event log.

Building blocks

6

Start, step, decision, merge, abort, end. No notation to learn.

Results as

P10–P90

Every figure for time and money arrives as a band, never as a single value.

Utilisation

Peak day

Reported for the P90 day, not the monthly average where every problem disappears.

Views

4

Model, department, IT, management. One model, four audiences.

01Purpose

Four questions that actually require simulation

Everything else can be answered more cheaply. If none of these four is your question, you do not need simulation software. A product page should be allowed to say so.

1. Which step limits throughput? Not the one people complain about loudest, and not the one that takes longest. The constraint is the step with the highest utilisation ρ = demand ÷ capacity. At 85 % utilisation a case already waits 5.7× its own processing time; at 95 % it waits 19×. The arithmetic is here.

2. How long does it take in the bad cases? An average answers no commitment. Promise "three days" because the median is three days and you break the promise half the time. What matters is the P90, the value nine out of ten cases stay below.

3. Where does the constraint move once I fix it? This is where spreadsheet business cases fall apart. While review runs at 114 % utilisation, the approval behind it looks relaxed. It barely receives anything. Fix review, and approval takes the full volume. The saving that was in the spreadsheet never arrives.

4. What is a change worth in money? Not "faster", but a number with provenance: staff cost per case, cost of waiting, cost of rework, before against after, with a range.

02Positioning

Four categories of software, four purposes

Tools that appear on the same results page solve different problems. Most bad purchases happen not when picking within a category, but when picking the category.

Drawing toolBPM suiteSimulation labFlowVisual
ExamplesVisio, Lucidchart, draw.ioSignavio, ARIS, Bizagi, CamundaArena, Simul8, AnyLogic, FlexSim—
Core purposeDocumentGovern, executeDesign, optimiseDecide, prove, document
Enginenonemodule, edition-dependentvery strongfocused
Time to resultminutesweeks to monthsweekshours
Typical outputdiagramprocess archive, running appstatistics reportbefore/after in money, process manual
Falls apart atany numeric questionone detailed questiontime pressuredesign depth

Where the other categories fit: production lines, warehouses, emergency departments and terminals are designed in a simulation lab, with transport logic, setup matrices and experiment designs. Approval workflows across hundreds of processes and execution in a process engine belong in a BPM suite.

The full comparison, including the limits of each category, is in the article Process simulation software: four categories.

03Method

How the numbers are produced

No percentage uplift on an average. Discrete-event simulation with Monte Carlo repetition, the same principle the labs use, restricted to what is necessary.

Cases arrive one at a time. Not 120 a day as a flat number, but drawn from a distribution with variation, peak probability and peak factor. The damage happens on the five worst days of the quarter, not in the mean.

Every step has capacity and a processing range. Capacity either as people × hours per day, or as a flat takt where a machine sets the limit. Processing from–to, not as a point value. The spread is the actual information, because it is what creates the queue.

The run is repeated hundreds of times. Each repetition draws fresh random values. The distribution of results becomes the band: P10, P50, P90. Why a single number is useless here is covered in Understanding P10, P50 and P90.

Coupling is part of the calculation. A step never sees more cases than the slowest step ahead of it lets through. That is exactly why the constraint moves once you fix it, and exactly what no spreadsheet can do.

Utilisation  ρ  =  demand ÷ capacity
Waiting time Wq ≈  ρ/(1−ρ)  ×  (ca² + cs²)/2  ×  te

The second line is the approximation every simulation result can be checked against. If simulation deviates strongly from it, the difference sits in the coupling or in the calendar. That belongs in the explanation, not swept aside.

04Positioning

Where other tools fit

FlowVisual computes and documents administrative and service processes, from a single workflow to the whole company with org chart, systems and process landscape. Three jobs belong to other classes of tool.

  • Process mining for the past. FlowVisual reads no event logs; you enter volumes and durations. To learn from an event log what happened yesterday, use a mining tool. What happens once step 3 is automated, FlowVisual computes.
  • BPMN 2.0 for a process engine. FlowVisual works with six building blocks and produces the flow diagram, the process manual and RACI itself. It does not export BPMN 2.0 XML. See BPMN simulation.
  • Factory design. Transport logic, setup matrices, experiment designs and shift models with handover rules belong in a simulation lab.
05Getting started

From nothing to the first defensible number

About 30 minutes, no training, no account. The order is always the same.

  1. Open a template instead of starting empty. Via Browse templates in the onboarding sheet or File → Templates…. Order handling, quotation, invoice approval, complaints, onboarding and IT ticket ship with the app. Thirty seconds to see what a finished model looks like, which saves you from building your own too finely.
  2. Draw the flow. Start, steps in real sequence, decisions only where a case genuinely branches, an abort for everything that leaves the process.
  3. Enter volumes, durations and costs. Daily volume with variation, per step capacity and processing from–to, plus role, system and hourly rate. Compute a fully loaded rate: gross salary × 1.5 to 1.8, divided by roughly 1,500 productive hours.
  4. Watch before you compute. Does it really work like this? Those two minutes with the department save the argument about the result.
  5. Run the stress test. The button sits in the page header of the Processes area, next to Prove and Export. The top bar is your constraint; one click opens that step in the Details panel.
  6. Capture before, change exactly one lever, prove. FlowVisual also captures the before state by itself at your first change. Prove in the page header puts before and after side by side. Change one lever per run, and it is clear which one worked.
  7. Export. Proposal (PDF) for the decision maker, documentation (PDF) for traceability, plus the process manual, work packages, workshop minutes and the data as CSV or JSON.

All seven steps are free; the PDFs then carry a trial mark. Pro adds PDFs without a watermark, your letterhead, Word, Visio (.vsdx) and draw.io/SVG. The long version with checklists and the five expensive mistakes is in the guide.

At a glance
Method
Discrete-event simulation with Monte Carlo repetition
Output
Throughput, lead time, queue and cost per step, as P10–P50–P90
Modelling
Six building blocks, no notation, no scripting language; Visio files (.vsdx) can be imported
Operation
Desktop, macOS 12+ and Windows 10/11. No cloud, no account, no sign-up
Data
Stays on the device. No event log required, no system integration
Cost
Modelling, stress testing, comparing variants, saving and PDF with a trial mark are free for good; Pro for PDF without watermark, letterhead, Word, Visio, draw.io/SVG and the team project folder
Learning curve
First defensible number in about 30 minutes, no statistics background needed

Frequently asked

What exactly is process simulation software?

Software that runs a modelled flow many times with randomly drawn arrivals and processing times, then reports where cases pile up. The difference from a spreadsheet is the queue: Excel adds processing times, simulation represents the fact that cases wait when a step is busy. In administrative processes waiting is typically the larger part of lead time.

Do I need an event log or a system integration?

No. FlowVisual computes an assumption, not a log. You enter volumes, capacities and durations as ranges. Estimates are allowed as long as they stay visible as assumptions. If you have an event log and want to measure the past, you need process mining instead; the two answer different questions.

Do I need a statistics background?

No. Distribution choice, warm-up period and replication count are your responsibility in simulation labs, not here. You enter ranges and get ranges back. For laying out a production line with transport logic and experiment designs, a simulation lab is built for the job.

How many steps does a meaningful model need?

Five to ten is almost always enough. The constraint rarely hides in the detail; it sits where utilisation is highest, and that is just as visible in a coarse model as in a fine one. Finer modelling pays off only when you want to quantify the effect of a specific change at a specific step.

Does the simulation run in the cloud?

No. FlowVisual is a desktop application for macOS 12+ and Windows 10/11 and processes process data exclusively on the device. There is no account and no sign-up. For processes touching staff, customer or contract data, that regularly removes an approval step a cloud tool would require.

FlowVisual

Run the numbers on your own process

Download it, open a template, enter your figures, run the stress test. Modelling, stress testing and saving cost nothing, and your data never leaves the machine.

Guide: seven steps to the number