Connect directly from your PLC or HMI
Instead of configuring another hardware device, you simply:
- 1Create a generic MQTT configuration in DCC
- 2Load the resulting certificates onto your PLC or HMI
- 3Map tags to a simple JSON MQTT payload
- 4Publish the payload directly to DCC
No extra infrastructure, additional gateway management or separate configuration tool.
Secure by design - without compromising OT security
Connecting directly from a PLC or HMI to DCC over MQTT does not inherently compromise security or conflict with modern cybersecurity frameworks such as NIS2. In many architectures, the device establishes only an outbound encrypted MQTT connection to the cloud.
- No inbound ports need to be opened
- No direct remote access to the PLC is required
- No VPN tunnel into the machine network is necessary
- Operational machine control remains separate from cloud-based monitoring and analytics
- Modern MQTT supports TLS encryption, authentication and certificates, and controlled outbound communication policies
Secure cloud connectivity and NIS2 compliance are about implementing connectivity correctly - not avoiding connectivity.
Why not OPC UA?
OPC UA and MQTT are often presented as alternatives, but many industrial architectures use both.
OPC UA can provide structured access to PLC and machine data inside the local OT environment, while MQTT transports selected information efficiently to cloud platforms such as Inuatek DCC.
MQTT can also carry structured industrial data using conventions such as Sparkplug B, or act as the transport for OPC UA PubSub.