Every PLC on a factory floor speaks a different language. Siemens uses S7/PROFINET. Rockwell uses EtherNet/IP with CIP. Beckhoff uses ADS over EtherCAT. Mitsubishi uses MELSEC. Omron uses FINS. Legacy equipment still runs Modbus RTU over serial. Without a unified data architecture, connecting these machines to AI analytics, digital twins, and MES systems requires expensive custom adapters for every point-to-point connection — what the industry calls "spaghetti integration." Every new connection costs $5K-$20K in engineering, every adapter is brittle (one firmware update breaks it), and the result is a fragile web of integrations that nobody fully understands. The modern answer is the Unified Namespace: OPC-UA on the machine network because it handles the complex data structures of PLCs perfectly — self-describing, semantically rich, with metadata, units, and alarm limits — and MQTT with Sparkplug B for enterprise-wide event-driven streaming because it's lightweight, decoupled, and cloud-native. Leading PLC manufacturers including Siemens, Rockwell, Beckhoff, Schneider Electric, and ABB now embed OPC-UA servers directly into their controllers. Sparkplug B — ratified as an ISO/IEC international standard in 2023 — adds the standardized payload structure that raw MQTT lacks. We design the complete OPC-UA/MQTT data architecture for greenfield factories: protocol inventory, Unified Namespace topic tree, OPC-UA server configuration per PLC brand, MQTT broker placement with Sparkplug B payloads, edge gateway integration, and data quality management — so every machine speaks one language from commissioning day. Schedule a Demo
Spaghetti Integration vs Unified Namespace
Still running point-to-point integrations? Schedule a demo to see how a Unified Namespace eliminates spaghetti connections and lets any new application subscribe to live production data in minutes.
Protocol Inventory: OPC-UA Support by PLC Brand
| PLC Brand | Native Protocol | OPC-UA Support | Integration Method | Companion Specs |
|---|---|---|---|---|
| Siemens S7-1500 | PROFINET, S7 | Native OPC-UA server built into CPU | Direct OPC-UA connection; SiOME for modeling | PackML, Euromap, Machine Tools |
| Rockwell ControlLogix | EtherNet/IP, CIP | Via FactoryTalk Linx Gateway | FactoryTalk Gateway as OPC-UA server | PackML via Add-On Profile |
| Beckhoff TwinCAT 3 | ADS, EtherCAT | Native OPC-UA server and client in PLC | Direct integration; Nodeset Editor for companion specs | PackML, Euromap, Machine Tools |
| Schneider M580/M340 | Modbus TCP, Ethernet/IP | OPC-UA server module | EcoStruxure Machine Expert OPC-UA | PackML, OMAC |
| ABB AC500 | PROFINET, Modbus | Native OPC-UA server | Direct OPC-UA; Automation Builder configuration | Process automation companion specs |
| Mitsubishi iQ-R | MELSEC, CC-Link IE | OPC-UA server module (RD81OPC96) | Module-based OPC-UA server | Limited companion spec support |
| Omron NJ/NX | EtherNet/IP, FINS | Built-in OPC-UA server | Sysmac Studio configuration | PackML |
| Legacy (Modbus RTU/TCP) | Modbus RTU/TCP | Via gateway (Kepware, Ignition) | Software gateway with Modbus driver → OPC-UA server | N/A — manual data modeling required |
Unified Namespace Topic Tree Design
Example MQTT Topic
spBv1.0/acme_corp/DDATA/plant_chicago/machining/line_01/cnc_01
Sparkplug B payload contains: metric name, value, data type, timestamp, and quality code — all in Protocol Buffer binary format for minimal bandwidth.
ISA-95 Alignment
The topic hierarchy follows ISA-95 equipment model levels: Enterprise → Site → Area → Line → Cell → Device. This ensures the namespace scales across multi-site, multi-plant organizations without topic collisions and maps directly to MES/ERP hierarchies.
OPC-UA: The Machine Dictionary
Self-Describing Data
OPC-UA doesn't just transmit "42.5" — it transmits 42.5°C, measured at 14:32:15.625, with "Good" quality status, from "Tank_01/Temperature", with alarm limits 10°C/80°C and engineering unit metadata. This semantic richness eliminates the need for external tag databases and makes data immediately usable by any consuming application without additional context mapping. A Modbus register gives you a raw number; OPC-UA gives you a fully described measurement.
Companion Specifications
OPC Foundation companion specifications define standardized information models for specific industries and machine types: PackML for packaging machines, Euromap for injection molding, OPC-UA for Machine Tools (umati), OPC-UA for Robotics, and dozens more. When a CNC machine exposes data via its companion specification, any OPC-UA client understands it as a machine tool — not just a list of variables. Over 80 companion specifications published, with 19+ manufacturers demonstrating interoperability in OPC Foundation's multi-vendor UAFX demonstrations.
Security Built In
X.509 certificate-based authentication, 256-bit encryption (AES-256-CBC), message signing, and role-based access control — built into the protocol, not bolted on. Every OPC-UA connection is mutually authenticated: the client proves its identity to the server, and the server proves its identity to the client. No shared passwords, no plaintext transmission. In greenfield, certificate management (PKI infrastructure) is designed as part of the OT security architecture during commissioning.
OPC-UA PubSub & TSN
OPC-UA Part 14 (PubSub) extends client/server with publish/subscribe over UDP multicast, MQTT, or AMQP. Combined with TSN (Time-Sensitive Networking), OPC-UA PubSub enables deterministic real-time communication between controllers — what the OPC Foundation calls OPC-UA FX (Field eXchange). Multi-vendor UAFX demonstrations with 19+ companies (ABB, Beckhoff, Rockwell, Siemens, Schneider) have proven controller-to-controller interoperability at SPS and IIFES trade shows.
MQTT + Sparkplug B: The Enterprise Transport
Why MQTT for Factory Data
MQTT's publish/subscribe model decouples data producers from consumers — machines publish once to a broker, and any number of consumers subscribe without the producer knowing or caring who's listening. Fixed header overhead is just 2 bytes (vs OPC-UA's kilobytes of session handshake certificates). Report-by-exception means data is only sent when it changes — reducing bandwidth by 80-90% compared to polled protocols. MQTT 5.0 adds shared subscriptions, topic aliases, and enhanced QoS for industrial requirements.
Why Sparkplug B Is Required
Raw MQTT has no payload standard — every device publishes in its own format (JSON, CSV, binary, plain text). Sparkplug B adds what raw MQTT lacks: standardized topic namespace (spBv1.0/group_id/message_type/edge_node_id), typed metrics with metadata (name, value, data type, timestamp), birth/death certificates for device state awareness, Protocol Buffer encoding for compact binary payloads, and report-by-exception with sequence numbering. Ratified as an ISO/IEC international standard, Sparkplug B ensures that any Sparkplug-compatible device is immediately discoverable and interpretable by any Sparkplug-compatible application.
MQTT Broker Architecture
On-premise MQTT broker (HiveMQ, EMQX, Mosquitto, or Cirrus Link Chariot) deployed in the factory server room as the central hub of the Unified Namespace. All edge gateways publish to the broker; all consuming applications (MES, AI analytics, digital twins, dashboards) subscribe from the broker. Broker clustered for high availability (active-active or active-passive). Bridge to cloud broker (Azure Event Grid, AWS IoT Core, HiveMQ Cloud) for enterprise-level analytics with firewall-safe outbound MQTT connections only — no inbound ports opened to the factory network.
QoS Levels
MQTT provides three Quality of Service levels: QoS 0 (at-most-once, fire-and-forget — suitable for high-frequency sensor telemetry where occasional loss is acceptable), QoS 1 (at-least-once — guaranteed delivery with possible duplicates, suitable for most industrial data), and QoS 2 (exactly-once — guaranteed single delivery, suitable for commands and setpoints). Sparkplug B uses QoS 1 by default and handles deduplication via sequence numbers in the payload. QoS level per topic is configured during the greenfield data architecture design phase.
Need a Unified Namespace designed for your greenfield factory? Schedule a demo to see how OPC-UA on the machine network and MQTT/Sparkplug B on the enterprise layer create a single source of truth for every machine, sensor, and application.
Edge Gateway Architecture
Edge gateway connects to PLCs via OPC-UA client, Modbus TCP/RTU driver, EtherNet/IP driver, or proprietary protocol driver. Software platforms: Kepware (PTC), Ignition Edge (Inductive Automation), HighByte Intelligence Hub, Node-RED with OPC-UA nodes. One gateway can connect to 10-50+ PLCs simultaneously. In greenfield: gateway software and hardware specified in the automation architecture; OPC-UA server licenses specified in PLC purchase orders.
Raw PLC tags transformed into the Unified Namespace structure: mapped to ISA-95 hierarchy, assigned engineering units, tagged with data quality indicators, and time-stamped with PTP-synchronized clocks. Deadband filtering configured per tag — only values that change beyond a configurable threshold are published, reducing network traffic by 80-90%. Data transformations (scaling, unit conversion, calculated values) performed at the edge before publishing.
Transformed data published to the MQTT broker as Sparkplug B payloads. NBIRTH message on connection announces all available metrics (the "birth certificate"). NDEATH message (Last Will and Testament) notifies all subscribers if the gateway loses connection. NDATA messages contain only changed values (report-by-exception). Protocol Buffer encoding reduces payload size 3× compared to JSON. Gateway handles store-and-forward: if the broker is temporarily unreachable, data is buffered locally and published when connection resumes — no data loss.
The edge gateway acts as the IT/OT security boundary. OPC-UA connections on the OT network (certificate-authenticated, encrypted). MQTT connection to broker on the IT/DMZ network (TLS 1.3, username/password or certificate). No direct connectivity between OT PLCs and IT/cloud systems. The gateway only initiates outbound MQTT connections — no inbound firewall ports opened to the OT network. IEC 62443 zone/conduit model enforced at the gateway level.
Key Benefits & ROI
Stop Building Custom Adapters. Build a Namespace.
iFactory designs unified OPC-UA/MQTT data architectures for greenfield factories — protocol inventory, Unified Namespace design, Sparkplug B configuration, edge gateway placement, and security architecture — so every machine speaks one language from commissioning day.
Frequently Asked Questions
500 Custom Integrations or 1 Unified Namespace?
Every new application connected to your factory should take minutes, not weeks. OPC-UA + MQTT + Sparkplug B + proper architecture = subscribe and go.
