Process Map overview
Process Map lets you model any workflow as a directed graph of nodes, then simulate how work flows through it using discrete-event simulation.
What it does
You place nodes on a canvas — a Start node where work arrives, Task nodes where work is processed, Queue nodes where work waits, and an End node. You connect them with edges, configure service time distributions, optionally assign resources, and run a simulation. The engine reports throughput, cycle time, queue depth, resource utilization, and more.
Who it's for
Any process with variability: support ticket flows, manufacturing lines, hospital intake, document approvals. If you want to know "what's the bottleneck?" or "what happens if I add a second person to step 3?", Process Map answers it.
Key concepts
| Concept | Description |
|---|---|
| Node | A step in the process. Can be a task, queue, start, or end. |
| Connection | A directed edge between nodes. Can carry a probability weight (probabilistic routing) or a conditional expression (conditional routing). |
| Distribution | The probability distribution used to sample service times or arrival intervals. |
| Resource | A shared constraint (e.g. a person or machine) that limits concurrency across nodes. |
| Scenario | A saved snapshot of the full graph plus its configuration. |
| Simulation run | One execution of the DES engine over a scenario. |
Next steps
- Node types — learn what each node type does
- Connections — routing modes and edge weights
- Simulation — distributions, resources, and result metrics
- Scenarios — saving, loading, and sharing your work