Every system has its own connection
MES, ERP, historian and analytics each poll the PLCs. Each new consumer means another point-to-point link to build and maintain.
UltraMQ is an MQTT broker for factories. It brings PLC and SCADA data into one real-time namespace, runs in Europe or on your own servers, air-gapped if required, and feeds MES, ERP and AI from the same source.
enterprise/
└─ site-frankfurt/
├─ line-3/
│ ├─ press-07/temp
│ └─ robot-2/torque
└─ line-4/
└─ oven-1/statusILLUSTRATIVE — REAL BENCHMARKS PENDINGMES, ERP, historian and analytics each poll the PLCs. Each new consumer means another point-to-point link to build and maintain.
Many plants run on-prem or air-gapped. A cloud-only broker is not an option, and approvals for new cloud services take months.
Production runs 24/7. The broker in the middle has to stay up through updates, network faults and node failures.
A proprietary hub becomes a dependency for every line. Teams want an open standard they can move away from if they have to.
Publish once, subscribe anywhere. Machines, lines and sites share one topic tree that MES, ERP, historians and AI read from. [Unified Namespace reference designs to confirm]
Run UltraMQ on your own servers, without a connection to our cloud. [Offline licensing and update bundles to confirm]
Keep a broker at the edge of each site and forward selected topics to a central or cloud broker. [Bridge feature details to confirm]
If you prefer us to run it: managed clusters in EU regions, operated by a European company. [EU entity and regions to confirm]
Clients speak plain MQTT, so devices, gateways and software stay portable. [Supported MQTT versions and protocol list to confirm]
Rules filter and transform data in flight, and agents can send commands back to machines with the right permissions. [Rule engine and permission model to confirm]
Values in [brackets] are not confirmed yet.
PLCs and sensors publish over MQTT, directly or through an edge gateway that translates fieldbus protocols.
PUBLISH
enterprise/site-frankfurt/
line-3/press-07/tempTopics follow your ISA-95 hierarchy: enterprise, site, area, line, cell. Everyone finds data in the same place.
enterprise/site/
area/line/cell/tagEach site keeps its own broker. Selected topics are forwarded to a central or cloud broker when the network allows.
BRIDGE
site-frankfurt → central
[to confirm]MES, ERP, historian, dashboards and AI subscribe to what they need. Adding a consumer does not touch the PLCs.
SUBSCRIBE
enterprise/+/line-3/#| Role | Their question | What we work through with you |
|---|---|---|
| OT engineer | Will it work with our machines? | Your devices and protocols, topic structure, a pilot on one line |
| Industrial IT architect | Does it fit our architecture? | Edge, site and central brokers, high availability, the namespace design |
| Head of OT / plant manager | What does it cost and who supports it? | Pricing per connection, support terms [support tiers to confirm] |
| Security and procurement | Can we approve it? | Hosting location, data flows, security documentation [certifications to confirm] |
A Unified Namespace is an architecture pattern: one event-driven hub, usually an MQTT broker, holds the current state of the operation, organised by the ISA-95 hierarchy. Systems publish to it and subscribe from it instead of connecting to each other.
Yes. UltraMQ can run on your own servers and in air-gapped plants. Offline licensing and update bundles are [to confirm].
Devices and gateways that speak MQTT connect directly. Native support for protocols such as OPC UA, Modbus TCP, Siemens S7 or IEC 60870-5-104 is [to confirm]; until then, an edge gateway that translates them to MQTT is the common pattern.
We only list certifications we hold. [Certifications to confirm.] Ask us for the current security documentation.
In the managed version, in EU regions operated by a European company [regions to confirm]. You can also run it in your own cloud account or on your own servers.
Tell us what you want to connect, where it has to run and what the data should feed. We reply by email.