MQTT Sparkplug B IIoT: The Industrial Standard Your Plant Needs in 2025

Why MQTT Sparkplug B IIoT Is Reshaping Industrial Data Exchange

If you work in industrial automation, you have probably heard the buzz around MQTT Sparkplug B IIoT in the last couple of years. What started as a specification developed by Cirrus Link Solutions and later donated to the Eclipse Foundation has now become one of the most referenced standards in Industry 4.0 conversations — and for very good reason. As plants grow more connected and data-hungry, the need for a unified, efficient, and interoperable protocol to move industrial data from the shop floor to cloud platforms, SCADA systems, MES, and AI engines has never been greater. This article provides a technical deep-dive into the Sparkplug B specification, explains why it is becoming the de facto standard for IIoT data exchange, and shows how you can implement it in your facility without writing a single line of custom code.

The Problem With Raw MQTT in Industrial Environments

MQTT (Message Queuing Telemetry Transport) is a lightweight publish/subscribe messaging protocol originally designed for low-bandwidth, high-latency networks. It is widely used in IoT applications and has found its way into industrial environments because of its simplicity and efficiency. However, raw MQTT has a significant limitation when used at scale in industrial settings: it provides no standardization for payload format, topic structure, or device state management.

Think about a large plant with Siemens S7-1500 PLCs on the production lines, Rockwell Automation ControlLogix controllers in the packaging area, Schneider Electric Modicon PLCs managing utilities, and ABB drives and controllers scattered throughout the facility. Each of these devices, when connected via raw MQTT, can publish data in completely different formats — some in plain text, some in JSON, some in proprietary binary structures. There is no agreed-upon way to know which devices are online, which tags have changed, or even what engineering units a value represents. Integrating all of this data into a SCADA, a BI dashboard, or an ML/AI platform becomes an expensive, time-consuming custom development exercise.

This is precisely the problem that MQTT Sparkplug B IIoT was designed to solve. You can learn more about the base MQTT protocol at mqtt.org, the official home of the MQTT standard.

What Is Sparkplug B? A Technical Overview

Sparkplug B is an open, royalty-free specification that defines how MQTT should be used in industrial and IIoT environments. It was standardized under the Eclipse Tahu project and addresses three core deficiencies of raw MQTT for industrial use:

• Defined topic namespace: Sparkplug B defines a strict topic hierarchy — spBv1.0/[Group_ID]/[Message_Type]/[Edge_Node_ID]/[Device_ID] — so every device on the network publishes and subscribes to predictable, structured topics. This makes discovery, routing, and filtering straightforward without manual configuration.
• Standardized payload encoding: All Sparkplug B messages use Google Protocol Buffers (Protobuf) for payload serialization. This binary format is compact, fast to serialize and deserialize, and strongly typed — meaning every data value carries its name, data type, timestamp, and engineering unit metadata.
• State management and birth/death certificates: One of the most powerful features of Sparkplug B is its concept of NBIRTH (Node Birth), DBIRTH (Device Birth), NDEATH (Node Death), and DDEATH (Device Death) messages. These messages allow any application consuming data to know exactly which edge nodes and devices are online, what tags they publish, and when they go offline — enabling true session awareness across the entire IIoT network.

MQTT Sparkplug B IIoT: Key Concepts Every Engineer Should Know

Understanding the architecture of MQTT Sparkplug B IIoT requires familiarity with three main roles defined by the specification:

• Edge of Network (EoN) Node: The software component that sits at the edge — typically an IIoT gateway — and communicates with field devices such as PLCs, drives, sensors, and meters. It is responsible for publishing Birth Certificates and data messages to the MQTT broker.
• MQTT Broker: The central message hub. Any standard MQTT broker — such as HiveMQ, EMQX, Mosquitto, or cloud-hosted brokers like AWS IoT Core — can handle Sparkplug B traffic. The broker does not need to understand Sparkplug B; it simply routes messages according to the defined topic namespace.
• Primary Application (SCADA Host): The consuming application — whether a SCADA system, MES, historian, or AI platform — that subscribes to Sparkplug topics and processes the data. In Sparkplug B, the Primary Application also publishes its own STATE message so edge nodes can confirm connectivity to the host.

This three-tier architecture creates a clean separation between data acquisition at the edge, transport via the broker, and consumption by enterprise applications — which is exactly what modern IT/OT convergence demands.

Why Sparkplug B Is Becoming the De Facto Standard in 2025

Several converging factors are driving the rapid adoption of MQTT Sparkplug B IIoT across industries ranging from discrete manufacturing to oil and gas, water utilities, and building automation:

• Vendor neutrality: Because Sparkplug B is an open specification managed by the Eclipse Foundation, it is not tied to any single vendor ecosystem. A Siemens PLC, a Rockwell controller, a Schneider sensor, and an ABB drive can all coexist on the same Sparkplug B network without proprietary middleware.
• Report by Exception (RBE): Sparkplug B mandates that edge nodes only publish data when a value actually changes (Report by Exception). This dramatically reduces network bandwidth consumption and broker load compared to polling-based protocols or raw MQTT implementations that publish on a fixed schedule regardless of value changes.
• Self-describing payloads: Because every Sparkplug B DDATA message carries full tag metadata — name, data type, engineering unit, timestamp — consuming applications do not need to maintain a separate tag database or schema file. The data describes itself, which accelerates integration with BI platforms, ML/AI pipelines, and cloud digital twin applications.
• Cloud and edge convergence: All major cloud IIoT platforms — AWS IoT Core, Azure IoT Hub, Google Cloud IoT — support MQTT natively, and Sparkplug B sits cleanly on top of them. This makes Sparkplug B the natural bridge between the operational technology (OT) floor and the information technology (IT) cloud.
• Growing ecosystem: An increasing number of SCADA vendors, historian platforms, and IIoT middleware providers have added native Sparkplug B support, making interoperability easier than ever. The OPC Foundation and Eclipse Foundation have also been collaborating on ensuring that OPC UA and Sparkplug B can work together in unified architectures.

Real-World Use Cases: From Siemens to ABB

Let us look at how MQTT Sparkplug B IIoT works in practice across real industrial scenarios.

In a Siemens S7-1500 environment, an IIoT gateway reads PLC tags via the S7 native protocol or OPC UA and republishes them as Sparkplug B DDATA messages to a central MQTT broker. The SCADA team gets a self-describing data stream with timestamps and engineering units without having to configure a tag database in the SCADA server. If the gateway loses connectivity, its built-in Store and Forward capability ensures no data is lost, and when reconnection is established, it retransmits buffered values in sequence.

In a mixed Rockwell Automation and Schneider Electric plant, where ControlLogix controllers handle discrete manufacturing and Modicon PLCs manage power distribution, a unified Sparkplug B layer above both environments means the MES system subscribes to a single broker and receives normalized data from both PLC families — same topic structure, same payload format, same timestamp resolution — regardless of the underlying communication differences.

In an ABB drive monitoring application, energy consumption data from ABB ACS series drives is published via Sparkplug B to an AI/ML platform analyzing anomalies and predicting maintenance needs. Because Sparkplug B payloads include quality flags and timestamps natively, the ML model receives clean, time-stamped data without preprocessing pipelines.

Implementing MQTT Sparkplug B IIoT Without Custom Development

The technical elegance of Sparkplug B is clear. But how do you actually implement MQTT Sparkplug B IIoT in a production plant without a team of software developers and months of integration work?

This is where the choice of IIoT gateway software becomes critical. Many automation teams attempt to implement Sparkplug B by writing custom Edge of Network node software — a time-consuming and maintenance-heavy approach that requires expertise in Protobuf encoding, MQTT session management, and Sparkplug B state machine logic. For most operations teams, this is not a viable option.

The alternative is to use a purpose-built IIoT gateway platform that natively supports Sparkplug B as a built-in output module — one that handles all the Birth Certificate management, Protobuf serialization, Report by Exception logic, and reconnection behavior automatically, while connecting to your existing PLCs, sensors, and systems through standard industrial protocols.

How vNode Solves This

vNode Automation delivers a complete, production-ready implementation of MQTT Sparkplug B IIoT through its dedicated Sparkplug B Module — no custom development, no Protobuf coding, no manual state machine management required.

Here is how vNode addresses every challenge discussed in this article:

• Native Sparkplug B output: vNode’s Sparkplug B Module acts as a fully compliant Edge of Network node. It automatically generates NBIRTH, DBIRTH, NDEATH, DDEATH, and DDATA messages according to the specification, handles reconnection and Birth Certificate retransmission, and manages the Primary Application STATE handshake — all out of the box.
• Universal protocol support for data acquisition: vNode connects to Siemens S7 PLCs (300/400/1200/1500), Rockwell EtherNet/IP controllers, Schneider Modbus devices, ABB VIP AC controllers, OPC UA and OPC DA servers, DNP3, BACnet, REST APIs, and many more — all configured through a browser-based interface with no programming required. Whatever your shop floor looks like, vNode reads it and delivers it as clean Sparkplug B data.
• Store and Forward: vNode’s MQTT module includes built-in Store and Forward capability, ensuring zero data loss during network disruptions. Buffered Sparkplug B messages are retransmitted in correct time order when connectivity is restored — critical for historian and AI/ML applications that depend on complete, time-accurate datasets.
• Unlimited tags, no per-tag licensing: Unlike many gateway solutions that charge per tag — which can make Sparkplug B deployments expensive at scale — vNode has no tag-based licensing. You can publish thousands of data points from your Siemens, Rockwell, Schneider, and ABB devices without worrying about licensing costs growing with your data model.
• Plug and Play deployment: vNode runs on Windows, Linux, and ARM embedded systems. Configuration is done entirely through a remote web interface. A new Sparkplug B edge node can be operational in minutes, not days.
• Redundancy built in: vNode’s Redundancy Module provides automatic Primary and Backup node failover, ensuring your Sparkplug B edge layer is as resilient as your SCADA infrastructure.

Whether you are deploying a greenfield IIoT architecture or retrofitting an existing plant to feed a modern SCADA, MES, or AI platform, vNode gives you a direct, standards-compliant path to MQTT Sparkplug B IIoT without the complexity and cost of custom software development.

Ready to bring Sparkplug B to your plant floor? Explore the full vNode platform at https://vnodeautomation.com/new-version-1-22/ or browse the technical documentation at usermanual.vnodeautomation.com. If you would like to discuss your specific connectivity requirements, contact the vNode team — our engineers are ready to help you design the right architecture for your facility.