OriginalThe unified namespace, explained
One broker, one topic tree, every producer and consumer decoupled. What a UNS is, what it demands, and where it goes wrong.
Industrial IoT platforms, devices, and architectures.
One broker, one topic tree, every producer and consumer decoupled. What a UNS is, what it demands, and where it goes wrong.
The topic namespace, birth certificates, and state awareness that turn MQTT from a transport into a plug-and-play OT data fabric.
From vibration sensor to work order: sensing, transport, context, models, and the analytics layer where predictions become decisions.
Three technologies that get compared as rivals but usually work as layers. What each one owns, and how to stop choosing between them.
Adapters, agents, and streams — how the open machine-tool connectivity standard works and where it fits beside OPC UA.
The three MQTT features that decide whether your telemetry is lossy, stale, or exactly-once — and when each setting is correct.
Protocol conversion, buffering, and context at the edge — the four gateway patterns that connect legacy equipment to modern platforms.
The MQTT organization homepage: protocol resources, version history, and links to brokers, clients, and the OASIS standard.
The Eclipse Sparkplug project: specification, TCK, compatible products, and working-group resources for MQTT-based OT interoperability.
MTConnect Institute: the open, read-only standard for shop-floor device data — adapters, agents, schemas, and companion specs.
HiveMQ's technical blog: MQTT features, Sparkplug, broker operations, and IIoT architecture at scale.
Opto 22's OptoBlog: edge devices, Node-RED, MQTT/Sparkplug, and practical IIoT project writeups.
HighByte: Industrial DataOps software for modeling, contextualizing, and governing data from edge to cloud.
Kepware (now part of Velotic): industrial connectivity software exposing hundreds of device protocols via OPC UA, MQTT, and more.