Skip to content
Thermite SCADA
Solution · Reporting

Reports are scripts you own.

Thermite SCADA has no report designer to learn. A report is a script on your server that reads history, live values, and alarm records from the gateway and produces the output you want. Run it on a schedule, or start it from a tag change or an alarm.

Included in one platform license
  • Reports are scripts
    A report is a script on your server. Write it in Python, SQL, shell, or whatever suits the job, and keep it under version control with the rest of your work.
  • History to read
    Query raw or aggregated tag history over HTTP, or read the PostgreSQL history database directly. Live tag values and alarm records are there too.
  • Run on a schedule
    Schedule a script with cron or your operating system's scheduler: end of shift, end of day, end of month.
  • Run on an event
    Start a report when a tag changes or an alarm is raised. A script can watch a tag over WebSocket, and an alarm notification can call an HTTP address you choose.
  • Production records
    Transaction groups write production values to PostgreSQL tables when a tag changes, ready for a report to read.
redundancy included · no module uplift
What you get

What you can build with Thermite SCADA.

Reports are scripts

A report is a script on your server. Write it in Python, SQL, shell, or whatever suits the job, and keep it under version control with the rest of your work.

History to read

Query raw or aggregated tag history over HTTP, or read the PostgreSQL history database directly. Live tag values and alarm records are there too.

Run on a schedule

Schedule a script with cron or your operating system's scheduler: end of shift, end of day, end of month.

Run on an event

Start a report when a tag changes or an alarm is raised. A script can watch a tag over WebSocket, and an alarm notification can call an HTTP address you choose.

Production records

Transaction groups write production values to PostgreSQL tables when a tag changes, ready for a report to read.

Any output

A PDF, a spreadsheet, an email, a row in another system. The script decides, so the report looks the way its readers need.

A report from a real run

Describe the report. Get a script that writes it.

We asked an agent for an hourly furnace report on a gateway reading a simulated holding furnace. It wrote the script, ran it for the last complete hour, and gave us the cron line.

Agent session

You I want an hourly report for HF-1, as a text file a supervisor can read and a CSV with the same numbers. Ten-minute rows: minimum, average and maximum bath temperature, the lowest level, and minutes the charging door was open. Under the table, the alarms raised in the hour and the number of charges. One script, no package installs.

Read AI-GUIDE.md then the tag and site reference pages in docs/

Fetch /p/cast-house/api/history/hf1/bath_temp?start=2026-11-12T18:00:00Z&end=2026-11-12T19:00:00Z&mode=raw recorded samples for the hour, each with its quality

Read site/logs/alarms.jsonl active and return-to-normal lines for hf1/bath_temp:hi and hf1/level:lo

Agent History comes over HTTP. The alarm interface shows current state, not past activations, so alarm times and trip values come from the alarm journal.

Write scripts/hf1_hourly.py 389 lines, Python standard library only

Run python3 scripts/hf1_hourly.py Saved reports/hourly/hf1_2026-11-12T18-00-00Z.txt and .csv

Agent The report for 13:00 to 14:00 is saved: 9 alarms raised, all returned to normal, and 5 charges. The numbers match the gateway’s own aggregates. To run it five minutes past every hour: 5 * * * * /usr/bin/python3 /opt/thermite-demo/scripts/hf1_hourly.py

Illustrative walkthrough of a session we ran, shortened. The furnace is a simulator; the script, the report and its figures are from the run.
reports/hourly/hf1_2026-11-12T18-00-00Z.txt
HF-1 HOLDING FURNACE - HOURLY REPORT
Hour: 2026-11-12T13:00:00.000-05:00 to 2026-11-12T14:00:00.000-05:00 (America/New_York; end excluded)
UTC: 2026-11-12T18:00:00Z to 2026-11-12T19:00:00Z
Journal read at: 2026-11-12T14:07:15.374-05:00

Time         Bath min F  Bath avg F  Bath max F  Low level %  Door open min
-----------  ----------  ----------  ----------  -----------  -------------
13:00-13:10      1323.9      1350.9      1410.3         36.8          1.833
13:10-13:20      1331.3      1360.4      1409.8         38.8          0.116
13:20-13:30      1325.9      1364.8      1411.3         43.8          1.717
13:30-13:40      1326.4      1366.3      1416.3         37.0          1.833
13:40-13:50      1324.0      1352.2      1405.4         36.3          1.833
13:50-14:00      1328.8      1355.9      1401.4         39.3          0.616
The top of the report the script wrote. Under the table it lists the nine alarms raised in the hour, with the time each went active, how long it stayed active, and the value that tripped it, and counts five charges.
Why Thermite SCADA for this

How it fits your work.

No framework to fit into

You are not limited to what a built-in report designer can describe. If a script can compute it, you can report it.

Your agent writes it

Describe the report you want. Your agent writes the script against the gateway's interfaces, runs it, and shows you the result to check.

Versioned query definitions

Named SQL queries live in project TOML files. Review changes alongside tag mappings and transaction definitions in Git.

Go deeper

Related Thermite SCADA documentation.

Bring a report you already rely on.

We'll show you how it becomes a script on a Thermite SCADA server, and what it reads from the gateway.