Sparkplug B is an open specification that turns plain MQTT into a SCADA-ready, interoperable data protocol. Managed by the Eclipse Foundation, it defines how industrial data is structured, how devices announce themselves, and how state is managed on top of MQTT's lightweight publish/subscribe transport - making it a cornerstone of modern IIoT and unified namespace architectures.
Sparkplug B in one line: Sparkplug B is an open MQTT specification for industrial SCADA that standardizes topic namespaces, payload encoding, and session state - including birth and death certificates and report-by-exception - so edge nodes and applications can share stateful process data interoperably over an MQTT broker.
MQTT is an efficient publish/subscribe transport, but on its own it says nothing about how industrial data should be structured or how to know whether a value is currently valid. Two vendors could both use MQTT and still be unable to understand each other's topics or payloads. Sparkplug B fills that gap with three key mechanisms. It defines a standard topic namespace so every message has a predictable structure identifying the group, edge node, and device. It specifies a compact payload encoding for metrics with data types, timestamps, and quality.
Crucially, it adds stateful session management. When an edge node connects it publishes a birth certificate (NBIRTH/DBIRTH) declaring all its metrics and current values; MQTT's Last Will and Testament is registered so that if the node drops, the broker automatically publishes a death certificate (NDEATH), telling every subscriber the data is now stale. Between those, the node reports by exception - sending only changed values - which keeps bandwidth low, a real benefit over cellular links at remote wellsites.
Sparkplug B is closely tied to the unified namespace concept: a single, real-time MQTT broker acts as the central hub where every asset publishes its state and any authorized application subscribes, decoupling data producers from consumers. Instead of point-to-point polling, an edge gateway at a wellpad or compressor station publishes its metrics once, and SCADA, analytics, and historians all subscribe.
For oil and gas, this fits the reality of thousands of dispersed, bandwidth-constrained sites. Report-by-exception and efficient payloads suit cellular and satellite backhaul, while birth/death certificates give operators trustworthy knowledge of which sites are actually online. A cloud SCADA can act as a Sparkplug host application subscribing to the broker, so the same edge data feeds dashboards, alarms, and long-term history without bespoke integrations for each device type.
MQTT is the underlying publish/subscribe transport with no rules about data structure or state. Sparkplug B is a specification layered on MQTT that standardizes topic namespaces, payload encoding, and stateful session management (birth/death certificates and report-by-exception), making the data interoperable and SCADA-ready.
A birth certificate (NBIRTH/DBIRTH) is published when an edge node connects, declaring all its metrics and current values so subscribers get the full state. A death certificate (NDEATH), delivered via MQTT's Last Will and Testament, tells subscribers the node has disconnected and its data is now stale - so no one acts on outdated readings.
Sparkplug B is a common way to implement a unified namespace (UNS): an MQTT broker is the single real-time hub where every asset publishes its state and applications subscribe. Sparkplug adds the structure and state management that make that shared namespace consistent and self-describing.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.