Getting started / WORKED EXAMPLE
Service queue
See why a shared service desk develops a queue.
Free to open, edit and save a file. Pro to run your changes. Opening a project asks before replacing your current space.
Why does a shared service desk develop a queue?
- Who uses it
- New simulation users · queue tutorial
- How it can create value
- Learn how arrivals and processing capacity create waits before modeling a real operation. This small numeric exercise is not an investment case.
- Bring your site data
- Arrival intervals, service time and number of stations. Add measured demand, a service target and option costs for a business study.
01 / SETUP
A model you can inspect.
A shared resource serves deterministic arrivals. Change station count, service time and arrival spacing to inspect contention.
Change one thing
Compare 1 and 2 stations with the same 12 jobs.
Read the consequence
Average wait, maximum queue and station utilization.
View the starting inputs
- Stations
- 2
- Jobs
- 12
- Arrival interval (s)
- 5
- Service time (s)
- 12
Agent counts, routes and resource definitions are also saved in the project JSON.
02 / ACTUAL ENGINE OUTPUT
A reproducible starting result.
One run, seed 0. Observation window 3 minutes.
| Scenario | Completed | Mean wait | Mean cycle | Blocked |
|---|---|---|---|---|
| Original scenario | 12 | 5s | 17s | 0 |
Waiting averages cover arrived jobs, including unfinished waits; cycle averages cover completed jobs only. These are synthetic calculations, not measured store performance, revenue or a safety assessment.
Engine, status and output notes
process-des-2.2.0. Status: Original scenario: completed. “Completed” is the engine run status; check the blocked column for unreachable jobs.
- No engine warnings.
Engine inputs and saved comparisons stay with the downloaded project. Any limited trace affects playback details, not aggregate metrics.
03 / MAKE IT YOURS
Plan in 2D. Inspect in 3D. Keep the whole project.
- Open and adjust. Switch between 2D and 3D; edit a part, a floor or an input. Both views describe the same model.
- Connect your agent for free. Sign in, choose Connect AI and connect Codex or Claude Code. Ask it to inspect the example, edit the layout and check a route.
- Save a checkpoint. Export → Project JSON, or ask the agent to export the complete project. Import it later to restore floors, scenarios, saved comparisons and the selected view.
- Compare with Pro. Run an edited scenario or compare frozen options under the same demand. Pro also adds built-in AI and manual cloud saving.