DESIGN · EXPERIMENT · UNDERSTAND
SimLab Studio
Your process. Your rules. A place to see what happens next.
From business rules to a working model
- Set a run length, arrival interval and case-value range. All times are in minutes; costs are in GBP.
- Define shared resources and their capacity. Cases wait in a first-in, first-out queue when a resource is busy.
- Add process steps and routing rules. Rules run after processing, top to bottom; the first condition whose probability check succeeds wins. Otherwise the default route applies.
- Run or step through the model. The run stops at the horizon, so unfinished cases remain visible. Compare scenarios using the same seed.
Duration is sampled uniformly between the minimum and maximum. Arrivals use an exponential interval, with the first case at time zero. Case values are sampled uniformly. Queue patience of zero means unlimited; an expired wait rejects the case. “Wait” in routing rules means accumulated queue time, and “visits” counts all steps entered. Costs measure resource time actually used, including unfinished work.
These are illustrative assumptions, not calibrated forecasts. Routes stop after 100 step visits per case. The event log retains the first 50,000 events. Save locally stores one project in this browser; export JSON for a portable copy. No account or server storage is used.
Invoice approval is ready. Edit the model or start a run.
01 / DEFINE
Business model
02 / EXPLORE
Invoice approval
A fixed seed makes the same model repeatable. Each step advances 1% of the run length.
03 / UNDERSTAND
Where work waits
| Resource | Busy / slots | Waiting | Utilisation | Cost |
|---|
Utilisation is used capacity divided by available capacity over elapsed time.
| Step | Entered | Finished | Mean wait | Timed out |
|---|
Event trail
Latest 80 recorded events · time in minutes
| Time | Case | Event | Step / detail |
|---|---|---|---|
| Run the model to follow each case through the process. | |||