Data Field Services

Home · LDUX and SCADA

What SCADA is

SCADA (Supervisory Control and Data Acquisition) monitors and operates remote equipment — sensors, pumps, valves, facility systems — through field controllers, telemetry, a server or historian, and an operator HMI. Safety interlocks and hard control stay in OT (PLC/DCS), not in a browser.

Layer map

SCADA Role LDUX mapping
Field devices / RTUs / PLCs Sense and actuate Outside LDUX. Real plant / OT hardware.
Telemetry Tags, alarms, setpoints (OPC-UA, MQTT, Modbus, …) Adjacent data. Custom integrations and reporting sit beside the feed.
Server / historian Collect, store, trend App store only: OPFS ldux.db, edge KV/D1 — not a process historian.
HMI Operator screens Native web components — the human surface.
Engineering / config Who may change screens and recipes LDUX editor + sign-off — only attested publishes go live.
Audit / provenance Who changed what, when Signed objects — hash of layout, tokens, and HTML plus agent and org.
Secure compute boundary Logic that must not be casually tampered with TEE / WASM — sign and verify outside ordinary page script.

What maps cleanly

What must stay outside LDUX

Setpoints that move physical plant, safety interlocks, real-time control loops, and air-gapped OT networks stay in SCADA, DCS, and PLC. LDUX can describe, display, and attest information workflows next to those systems — it does not supervise pumps or breakers.

North star

SCADA’s HMI + config + audit ideas map to native web components + signed publish + TEE/WASM verify. SCADA’s control and safety do not.

For Data Field Services, that means SCADA-adjacent consulting: reporting, field-to-office integration, and attested operator views for oil & gas and data centers — without claiming to be a control system.