Results

​

Overview

Every simulation run produces a dataset of events that you can replay in the Modeler and analyze with Dexter. The Modeler holds the run’s replay, summary, and event log. Old Results links open the selected model and run there. For a dashboard, start from the Simulation results module template and connect it to your run, or ask Dexter to build a view for the questions you want to answer. Templates start with sample data unless you connect your own. To compare configurations or read the spread across repeated seeds, ask Dexter to compare runs or replicate one.

​

KPIs

A KPI is a SQL query that returns one row with a single value column, plus a required format type that tells the UI how to render it. There is no separate “text KPI” type — a status-style label is just a category-formatted KPI. The palette has ten colors (blue, orange, green, red, purple, yellow, cyan, brown, gray, lime), but four of them carry a documented semantic meaning: red for higher-is-worse (defects, downtime), green for higher-is-better (yield, throughput), gray for context or baseline, blue for neutral. The rest are neutral palette options. An optional unit suffix renders alongside the value.

​

Authoring and inspecting KPIs

Describe the metric to Dexter, including the run, units, and what counts toward it. Dexter can query the results dataset, explain the calculation, and present the result in a module or report.

​

Charts

Ask Dexter for the comparison or pattern you want to see, such as output over time, resource utilization, waiting time, or the spread of cycle times. It can build a chart from the run’s data or adapt the Simulation results app template. Charts and KPIs live in the app that presents them. Ask Dexter to update that app’s queries and query the run you want to analyze again when the calculation changes. A new simulation does not automatically refresh an app’s saved analysis.

​

Per-chart actions

Controls belong to the app that displays the chart. Ask Dexter to explain its calculation or change the view, or use the app’s Annotate control to point to what you mean. For a downloadable artifact, request a report.

​

Querying Simulation Data

KPIs and charts aren’t preconfigured dashboards: they’re SQL queries against the event tables the simulation engine writes for every run. Any question the event data supports is a query away — and Dexter writes those queries when you describe the metric you want. Every event table carries a timestamp (float, simulation seconds) and a global event_seq (strictly increasing across all event tables).

​

Event tables

One row per event; all carry timestamp and event_seq.

​

Context tables

No timestamp / event_seq — static context you join against.

​

The Run Page

Open the model in the Modeler and use View latest to open its newest run available for replay. To review an earlier run, ask Dexter for its link; opening a link to a specific run keeps that run selected. Use the Modeler to inspect the replay and summary, and use a module or Dexter conversation for KPI and chart analysis.

​

Simulation Event Log

The Modeler’s event trace shows what happened during the selected run. Use it to inspect entity movements and process activity, validate routing decisions, or confirm that scheduled actions fired when expected. Ask Dexter to query the run’s event tables when you need a filtered table or a deeper explanation.

​

Exporting Results

Ask Dexter for a report, and name the model, run, metrics, and format you need. For an Excel export, say which event tables or summaries to include; for a PDF, describe the charts and explanation you want to share.