Skip to content
Thermite SCADA
Tags & Historian

Live tags and recorded history with quality and timestamps.

Thermite SCADA carries tag values, quality, and timestamps from drivers to browser screens and APIs. Configure per-tag recording to PostgreSQL, numeric deadbands, sampling rate limits, and raw or aggregated history queries.

Hierarchical tags

Names that match how operators think.

Tags live in a project-scoped tree. Folders mirror equipment, area, or process structure. Screens and expressions reference each tag by path. You can review path changes in Git, and publish validation checks expression references.

press-line-a/
├── hydraulics/
│   ├── head_pressure         # f32 · psi · scan: fast
│   ├── reservoir_temp        # f32 · °F  · scan: slow
│   └── pump_status           # i32 · status · scan: fast
├── recipes/
│   ├── active_id             # string · scan: medium
│   └── target_pressure      # f32 · psi
├── motors/
│   ├── m1/{rpm, current, fault}
│   └── m2/{rpm, current, fault}
└── derived/
    └── cycle_efficiency      # expression tag
Tag kinds

Device, memory, and expression tags.

Device tag

Available

Bound to a configured device and address: an OPC UA node, Modbus register, S7 memory location, or MQTT topic.

Memory tag

Available

An in-memory scalar value with a declared type, held in the gateway’s runtime state.

Expression tag

Available

A read-only calculation over declared tags in the same project snapshot, recalculated when its dependencies change.

What every tag carries

Type, quality, timestamps, scan groups, units, and metadata.

Your screens receive the value and its context together.

Type

bool, i16, u16, i32, i64, f32, f64, and string.

Quality

Good, uncertain, bad, or stale. Quality travels with values into subscriptions and raw history.

Timestamp

Each tag value carries one timestamp, exposed alongside its value and quality.

Scan group

Named scan groups set polling intervals for OPC UA tags. Other devices poll at the rate set on the device.

Engineering units

Set units with eng_units and scale values with expressions.

Description

A description field documents the signal; hierarchical paths organize tags by equipment or process.

Historian

PostgreSQL history with deadbands and aggregation.

Choose which tags to record, filter numeric changes with deadbands, and limit archived sample frequency independently of polling. Query raw samples or aggregated windows.

PostgreSQL storage

Available

Opt tags into on-change recording. Stored samples retain typed values, quality, and timestamps.

Deadband filtering

Available

Absolute or percentage deadbands reduce recorded change samples for numeric tags.

Sampling rate limit

Available

Set a minimum interval between archived on-change samples independently of the live device scan rate.

Aggregations

Available

Numeric windows return average, minimum, maximum, count, first, and last values.

Bounded memory buffer

Available

Pending samples use a bounded memory buffer during database interruptions. New samples replace the oldest when the buffer fills.

JSON query API

Available

Retrieve raw samples or aggregated windows through the project HTTP API and the browser library.

Query API

Live and historical data on the same surface.

Subscribe to live tags over WebSocket and retrieve historical windows as JSON through the project HTTP API. Choose raw samples or numeric aggregation intervals. With authentication on, project roles control history reads.

See API surfaces →
# Subscribe to a live tag over the project WebSocket
ws://localhost:8432/p/cast-house/api/ws/tags
→ {"type":"subscribe","tags":["hf1/bath_temp"]}
← {"type":"update","values":{"hf1/bath_temp":{"value":1335.5,"quality":"good","timestamp":"2026-11-12T18:30:17.033921Z"}}}
← {"type":"update","values":{"hf1/bath_temp":{"value":1335.6,"quality":"good","timestamp":"2026-11-12T18:30:18.034464Z"}}}

# Thirty minutes of history in ten-minute intervals
curl 'http://localhost:8432/p/cast-house/api/history/hf1/bath_temp?start=2026-11-12T18:00:00Z&end=2026-11-12T18:30:00Z&mode=aggregated&interval=10m'
{"mode":"aggregated","tag":"hf1/bath_temp","interval_seconds":600,"count":3,"points":[
 {"interval_start":"2026-11-12T18:00:00Z","avg":1350.8680303664435,"min":1323.9000244140625,"max":1410.300048828125,"count":147,"first":1333.199951171875,"last":1409.800048828125},
 {"interval_start":"2026-11-12T18:10:00Z","avg":1360.360005457261,"min":1331.300048828125,"max":1409.800048828125,"count":170,"first":1409.300048828125,"last":1331.300048828125},
 {"interval_start":"2026-11-12T18:20:00Z","avg":1364.7602723004068,"min":1325.9000244140625,"max":1411.300048828125,"count":219,"first":1330.5999755859375,"last":1335.5}]}

Real requests to a trial gateway reading a simulated furnace controller. Line breaks added to the response. With authentication on, requests use a project session cookie, and WebSockets also need a single-use ticket.

Model your tags on a running gateway.

Bring your device list, naming conventions, and historian targets. We'll model them on the demo gateway.