Technology

MQTT integration: brokers, topic design and Sparkplug B

We publish machine and PLC data over MQTT in an orderly topic structure, so MES, ERP, historian and cloud systems subscribe to the same data.

Let's talk about your project → What we deliver

Our clients

Siemens
Anadolu Isuzu
BSH
Tofaş
Toyotetsu
Martur
Turkcell
Vodafone
Doğadan
Pakmaya
Bross
Abdi İbrahim
Nobel İlaç
Plastimak
Dalgıç Kalıp
Barbaros Motor
Magneti Marelli
Rözmaş
Sanel

MQTT is a lightweight messaging protocol where data is distributed through a broker on a publish-subscribe model. A source publishes to a topic, every system that needs the data subscribes to it, and sources and consumers never connect to each other directly.

In a plant, MQTT's value is collecting data once and serving it to many consumers instead of opening a new connection to the PLC for every new system. That is the basis of a Unified Namespace (UNS). It only works if the topic hierarchy, payload format, QoS levels and access rights are designed up front.

VOLSOFT collects data from PLCs, CNCs and other devices with Proxus and publishes it over MQTT. We build the topic tree on an ISA-95 hierarchy, choose between JSON and Sparkplug B based on the consuming systems, and set up broker access with the IT team.

What we deliver

MQTT integration

Topic hierarchy

Topics follow an enterprise, site, area, line and machine structure with the same rules at every site, so a consumer can follow one line or a whole plant the same way.
JSON or Sparkplug B

Proxus publishes JSON by default and can publish Sparkplug B 3.0 instead, with BIRTH and DATA messages, typed metrics and rebirth support. We recommend Sparkplug B when systems from several vendors must interoperate.
Built-in or existing broker

Every Proxus edge gateway includes a built-in MQTT broker that publishes the Unified Namespace as topics. If the plant already runs a broker, we publish to it as well.
QoS and message rate

We decide which data is published at which QoS level and how often, based on what each consumer needs, and avoid flooding the broker with unchanged values.
Security and access

Broker access is limited per user and per topic, and connections are protected with TLS. The OT-to-IT crossing is designed to the IT team's rules.

How a project runs

From discovery to live, step by step

01
Consumer needs

We identify which systems will use the data and which format they expect, JSON or Sparkplug B.
02
Topics and data model

We design the topic tree on an ISA-95 hierarchy and the payload: value, timestamp, quality and unit.
03
Broker and security

With IT we settle the built-in or existing broker, users, topic permissions and TLS configuration.
04
Publish and verify

We start publishing and verify end to end that consuming systems subscribe and receive the data correctly.

Built on Proxus

Proxus uses MQTT three ways: the built-in broker on each edge gateway publishes the UNS as JSON or Sparkplug B 3.0 topics, devices can publish their own values to it, and outbound MQTT or Sparkplug B targets send data to your existing broker.

Proxus is the industrial data platform built by the VOLSOFT team.

Proxus MQTT and Sparkplug B ↗

Frequently asked questions

Common questions

What is MQTT used for in manufacturing?

MQTT is a lightweight publish-subscribe protocol that distributes data through a broker. In a plant it lets machine data be collected once and served to MES, ERP, historian and cloud systems at the same time.

What is an MQTT broker?

A broker is the server that receives messages from publishers and forwards them to clients subscribed to the topic. Sources and consumers only connect to the broker. Every Proxus edge gateway includes one.

What does MQTT QoS mean?

QoS (Quality of Service) sets the delivery guarantee: QoS 0 is at most once, QoS 1 at least once, QoS 2 exactly once. Higher levels add assurance and also add network and broker load.

When should we use Sparkplug B?

Sparkplug B is an Eclipse specification that defines topics, typed metrics and session state with BIRTH and DEATH messages on top of MQTT. It fits when systems from several vendors must interoperate; when you control both ends, a documented JSON schema is often enough.

How does MQTT relate to a Unified Namespace?

A Unified Namespace publishes plant data in one orderly hierarchy, usually on an MQTT broker. MQTT is the transport; the topic hierarchy is the data model.