Results and comparison

Results are collected while the simulation runs. The Results tab reads from the top down: run state, four headline numbers, actions, then detail sections. Every run is also saved in your Run archive, and the Run comparison table puts several runs side by side.

What the Results tab shows

At the top of the tab, a switch chooses between Current run (the simulation you are running) and Run archive (runs saved earlier, see Run archive). Before the first run the current view offers a Run button instead of zeros. Once data exists:

1. Run state: Run in progress, Run finished or Paused, the simulated clock and, with a duration, a progress bar.
2. Headline KPIs (see below).
3. Actions: Export (.zip), JSON, PDF and Compare.
4. Sections: Mission times and Bottlenecks open, Fleet usage, Timeline and Events collapsed.

Headline KPIs

A growing queue with high utilisation means the fleet cannot keep up. A short queue with low utilisation means the fleet is oversized for the demand.

Detail sections

Mission times

Bottlenecks

Total traffic waiting time, the number of managed stops, then a ranking of the five paths with the most waiting (hover for stops and occupancy) and of stations with waits at access or queues. This is the first place to look when throughput is lower than expected.

Fleet usage

One bar per AGV splits its time into Loaded transport, Empty travel, Loading / unloading, Return, Waiting for traffic, Charging and Idle, with utilisation, missions and kilometres. With batteries enabled, charge levels are shown too.

Timeline

Three charts, one measure each, sampled every simulated minute: throughput (trailing-hour average), queued orders and AGVs waiting for traffic. Hover a chart to read the value at a given time. Charts appear after two simulated minutes.

Events and gridlock

Events lists what happened: assignments, completions, waits, returns and warnings. If every AGV with a mission has been waiting on the others for more than a minute, a Possible gridlock alert appears at the top of the results.

Heatmaps

The Heatmap selector in the canvas toolbar colours the layout with the collected data:

A single-hue ramp and line width encode the value; a legend shows the scale. Hover a path or a cell to read its value. The image button in the view controls downloads the current view as a PNG, including the heatmap and its legend, ready for a report.

Exporting results

Export (.zip) downloads an archive with:

• results.json: format agv-simulation-results version 1, including the scenario used;
• CSV tables: summary, missions, vehicles, stations, segments, wait_hotspots and timeline.

Column names are stable English identifiers such as throughput_per_hour or lead_time_p95_s, so spreadsheets and scripts keep working across versions. Files include a byte-order mark; the separator and decimal mark follow the interface language: ; and comma in Italian, , and point in English. JSON downloads only the JSON document, with the complete data.

PDF report

PDF creates a formatted report of the run, ready to share, in the language of the interface. It works for the current run and for any run reopened from the archive, and contains:

1. Cover and operational overview: run name, project, date, simulated duration and status; missions completed, average throughput, fleet utilisation and orders queued; demand and deliveries, fleet, timing and traffic figures, with a short reading of the results.
2. Run trends: throughput (trailing-hour average) and orders queued over time.
3. Fleet detail: one row per AGV with missions, utilisation, distance, battery and the breakdown of its time.
4. Paths and stations: the paths and stations with the most waiting.
5. Latest completed missions, with a short guide to reading the report.

The PDF is a summary: long tables show only their first rows and say how many were left out. For every record use Export (.zip) or JSON.

Run archive

The studio keeps every run you make, so you can reopen its results later, from this or another device, without having exported anything.

When a run is archived

• When it reaches its duration: it is saved as completed.
• When its results are about to be cleared, by Reset, by starting a new Run or by a scenario change that restarts the simulation: the results produced so far are saved as stopped.
• Pause does not create a copy, because you can resume the same run. A run that never advanced beyond time zero is not saved.

Each run gets a name made of the project name, the date and time, and its state, for example Warehouse A · 23/09/2026, 14:05:12 · completed.

Browsing and reopening runs

1. Open the archive. In Simulate›Results, click Run archive at the top of the tab. The counter shows how many runs are saved.
2. Find a run. The newest runs come first; each row shows name, date, state and completed missions. Type in the search box to filter by run or project name; Refresh reloads the list.
3. Open it. Click a run: its full results appear below, marked Archived run · completed or Archived run · stopped, with the same KPIs and sections as the current run, except the event list. Archived runs cannot be added to the comparison table.
4. Download it. Export (.zip), JSON and PDF work on the archived run as well.
5. Go back. Current run returns to the simulation in progress.

To delete the selected run, press Delete and confirm. Deletion is permanent.

Where runs are stored

Runs are stored on the server in your private space, encrypted, separately from your projects and linked to your account: after signing in you find them on any device. The .sim project never contains them.

If a run cannot be saved right away (for example the connection dropped), it waits in a queue in your browser and a notice shows Runs awaiting save with two actions: Retry sends it again, Run archive opens the archive. The studio also retries automatically when you reopen it. Until the server confirms the save, the run is not visible from other devices. If the browser cannot store the queue, a warning appears and the pending copy lives only in the current tab: do not close it before retrying.

Run comparison

Every run that reaches its duration is added automatically to Run comparison in the bottom dock and announced once. To add a run you stopped by hand, press Compare in Results.

Each row shows the run's inputs (fleet, order interval or Diagram when Plant logic is on, speed, mission priority, AGV selection, battery), its duration and its metrics: completed, throughput, lead time, P95, utilisation, maximum queue and traffic waiting.

• Changed inputs are highlighted, so you can see at a glance what differs between runs.
• The best value of each measure is marked with ▲, only when runs really differ. Utilisation is not ranked, because higher is not always better.
• Runs that had a possible gridlock are flagged.
• Remove deletes a row, Clear empties the table, Export CSV downloads it.

The comparison keeps up to 12 runs and lasts for the browser session; it is not part of the project file.