Getting started / WORKED EXAMPLE
Transport
Understand loading, travel and a shared transport fleet.
Free to open, edit and save a file. Pro to run your changes. Opening a project asks before replacing your current space.
How do loading and return trips occupy a shared mover?
- Who uses it
- New simulation users · transport tutorial
- How it can create value
- Learn to include the complete transport cycle before comparing fleet sizes. Distances are supplied inputs; use a spatial example to evaluate an actual layout.
- Bring your site data
- Job arrivals, loading/unloading time, travel distance and speed. A purchase decision also needs device costs and a measured site trial.
01 / SETUP
A model you can inspect.
Jobs reserve a mover, load, travel out and back, then return it. Straight-line coordinates are explicit inputs and ignore scene obstacles.
Change one thing
Compare 1 and 2 movers at the same travel distance.
Read the consequence
Job completion time and mover wait. Distances are inputs; walls do not affect this example.
View the starting inputs
- Movers
- 2
- Jobs
- 6
- Arrival interval (s)
- 12
- Distance (m)
- 10
- Speed (m/s)
- 1
- Load time (s)
- 4
- Unload time (s)
- 4
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 5 minutes.
| Scenario | Completed | Mean wait | Mean cycle | Blocked |
|---|---|---|---|---|
| Original scenario | 6 | 4s | 32s | 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.