Skip to content
Thermite SCADA
Docs · Guides

Migrating from legacy SCADA

View as Markdown

Inventory the existing system, map its functions, and agree a cutover sequence. Start with one area, compare operation during a parallel run, and establish a fallback for each step.

01 · Inventory

Catalog the legacy system.

Points & devices

Every PLC/controller, its protocol, and the point list with types, scan rates, and addresses.

Screens

Operator views and dashboards, plus which controls on them actually get used.

History

Which points are historized, at what resolution, and what downstream reports consume them.

Alarm logic

Setpoints, priorities, and how operators are notified today.

SQL touchpoints

Recipe tables, production logs, reports — anything reading or writing a database.

Users & roles

Who can see and write what, per area.

02 · Mapping

Map each item to what ships today.

Legacy item
Thermite SCADA surface
Device connections
Drivers: Modbus TCP, S7, EtherNet/IP, OPC UA, MQTT, BACnet/IP. DNP3, IEC 61850, and IEC 60870-5-104 are not integrated SCADA adapters. Confirm protocol coverage before a pilot.
Tag database / UDTs
Tag files (TOML). There are no UDT templates; organize definitions in files and folders. Your agent or a script can generate repetitive tag blocks for review.
Screens
HTML/CSS/JS screens with thermite.js live binding. Screens are rebuilt, not imported — there is no automated converter from any legacy format.
Historian
PostgreSQL-backed history with query-time aggregation, per-tag sampling and deadband.
Alarm annunciation
The alarm engine evaluates tag conditions, journals transitions, and exposes project alarm APIs. Notification pipelines support rosters, schedules, and escalation. Map existing conditions and notification rules; restart the gateway after changing alarm definitions or notification configuration.
SQL logging / recipes
Transaction groups (triggered inserts) and named queries.
Users & roles
With authentication enabled: per-project users, bindings, and role flags backed by local or gateway credential sources. LDAP/AD and SSO are not integrated.

Identify functions that need coexistence or additional integration, then agree the migration scope and sequence. Review the roadmap separately from available capabilities.

03 · Phases

Pilot → parallel → cutover → sunset.

01 · Pilot

One line or cell. Enable authentication and use project roles without can_write_tags. Rebuild one operator screen, historize the required points, and verify driver behavior and data quality.

02 · Parallel

Legacy stays authoritative. Thermite SCADA reads the same field data; compare values, history, and screen behavior side by side over real shifts.

03 · Cutover

Per area: operators move to Thermite SCADA screens. With authentication enabled, grant write permission to the required roles. Retain the area's legacy screens as the agreed fallback.

04 · Sunset

After every area cuts over and downstream reports read from the new historian, decommission legacy per site.

04 · Coexistence

Running both without crossed wires.

  • Keep Thermite SCADA read-only during pilot and parallel — no field writes until an area formally cuts over.
  • Confirm each device's session limits and polling load before adding a second client during the pilot.
  • Where both systems speak MQTT, the broker is a clean shared read path.
  • One project per area keeps cutover units independent — its screens, users, and publish lifecycle move together.
  • Keep reviewed project source and configuration templates in Git. Revert and republish project changes; restore gateway settings through their reload or restart procedure. Keep live configuration and credentials in secured recovery backups.
Next

Scope it with us.

Bring the inventory from step 01 to a technical session and we'll map it row by row, including functions that need coexistence or additional integration. Fixed-scope migration engagements are on Services.