MQTT Sparkplug B: The Protocol That Will Retire Your OPC Server
OPC UA is robust but heavy. Here is why Sparkplug B is the real standard for massive scale and the Unified Namespace.
Hassle-free automation?
Checklist: 10 Steps to Digitize Your Plant
Avoid costly implementation errors
The scaling problem with OPC UA #
OPC UA (Unified Architecture) is excellent. It is secure, semantic and standard. But it has one fatal flaw in the age of big data: it works on a client-server (request-response) model.
Imagine 1,000 sensors. With OPC UA your SCADA has to constantly ask each one: "any new data?". That generates brutal network traffic and couples the systems together. If the SCADA goes down, nobody sees anything.
Move beyond restrictive licensing
See why iGromi OS is a modern alternative to legacy SCADA and MES systems.
The New Standard: Edge AI
The industry no longer buys expensive per-tag licences or depends on slow clouds. Modern plants process data locally at < 5ms with full autonomy, even with no internet.
View Architecture MatrixEnter MQTT: report by exception #
MQTT works on publish/subscribe. Sensors (publishers) only send data when SOMETHING CHANGES. If temperature is steady, the network stays silent. This cuts bandwidth consumption by as much as 95%.
So what is MQTT missing? Context. (This is where Sparkplug B comes in) #
Plain MQTT is payload-agnostic. You can send JSON, XML or a photo of a cat. The subscriber has no idea what "45.2" means. Temperature? Pressure? Speed?
Sparkplug B is a specification built ON TOP of MQTT that defines:
- A standard topic structure:
spBv1.0/Group/Node/Device. - Efficient encoding: It uses Google Protobufs instead of text JSON, compressing the payload further.
- State management: The concept of a birth certificate and a death certificate. When a device connects, it sends its full definition. When it disconnects abruptly (power cut), the broker tells everyone "device X has died", thanks to the Last Will and Testament (LWT) message.
Unified Namespace (UNS) architecture #
With Sparkplug B we build an architecture where the MQTT broker is the centre of the universe. The ERP subscribes to production data. The MES publishes work orders. The PLC publishes machine states.
All decoupled. You can restart the ERP and the plant keeps producing and publishing. It is the definitive architecture for resilience.
