Industrial MQTT topic design: names, payloads and data contracts
Design a stable telemetry namespace with identity, timestamps, units, quality and schema ownership before connecting dashboards and consumers.
Industrial data contract
An owned agreement about a signal’s identity, datatype, units, timestamps, quality and consumer behavior.
Transport protocols move data; the contract makes its meaning and failure handling explicit. Include schema revision and migration rules, plus behavior for stale, duplicate, bad-quality and incompatible data. Keep credentials in approved secret storage. Use the contract worksheet with the connectivity learning path.
See also: Information model · Source timestamp · Topic namespace
Use the concept: Industrial data connectivity: from register to consumer · Industrial data contract template
In depth
Historian sampling and deadband: budget storage without losing events
Estimate raw historian volume, distinguish acquisition from storage filtering, and validate compression against the signals and events that matter.
Single-pair Ethernet and APL: two wires to the field instrument
How Single-Pair Ethernet and Ethernet-APL bring power and 10 Mbit/s Ethernet to hazardous-area field devices — and what changes in process design.