Skip to Content
This documentation is provided with the HEAT environment and describes this HEAT instance.

HEAT documentation

HEAT is a simulation analytics platform. Training simulators and capture tools send recorded data to HEAT. HEAT processes that data through a graph of steps that a developer defines once, then publishes the result as a dashboard. Three kinds of people work with it. Users, meaning instructors and trainees, read the dashboards. Administrators run the platform through the Control Centre. Developers decide how data is processed and what each dashboard shows.

Choose your path

Users: I want to see my sessionsAdministrators: I run a HEAT environmentDevelopers: I build data flows and dashboards
AudienceStart with
UsersSigning in, then Reading a session dashboard
AdministratorsThe Control Centre, then Deployment
DevelopersBuild your first data flow, then Node templates

How a session becomes a dashboard

Every dashboard in HEAT is the end of the same path.

  1. A developer creates a session template inside a Project. The template is a graph of named nodes that says how uploaded data is processed.
  2. Data arrives through an Ingest or the HEAT v2 API. It lands on the template’s input node and creates a Session, which is one run of the template over that batch of data.
  3. Each node in the template becomes a node instance in the session. A Runner executes the node’s node template and stores the result as a node output.
  4. A dashboard node publishes a Dimension. The dimension holds the data as channels grouped by Realm, plus a Layout that says how to draw them.
  5. The HEAT dashboard renders the layout’s widgets at /sessions/<dimensionId>.

Where things live

SurfaceWhat it is forWhere
HEAT dashboardReading session dashboards, reports and system dashboardsThe dashboard web application for your environment
Control CentreOperating the environment, including users, projects, data sources, sessions and monitoring/main and /admin on the same host (formerly Cluster Manager)
v2 APIUploading data, creating sessions and reading dashboard data from your own software/api/v2 on the same host, described in the HEAT v2 API reference
HEAT CaptureRecording data from simulators, sensors and wearables and streaming it to HEATA Windows application on the capture machine. See HEAT Capture for operators and Capture for developers for its interfaces.
This documentationConcepts, procedures and contracts for all three audiencesYou are here

New to HEAT? Read How HEAT works first, then keep the Glossary open while you work.

HEAT documentation team. Last updated 2 October 2026.

Opens your browser's print dialog. Choose "Save as PDF" as the destination.