Unifying IT & OT with a HMI or Headless HMI
When we move from the Single Factory, or the Single Farm, to
Large-Scale, Distributed Industrial Applications, a common concern
voiced by many IT Administrators is that infrastructure costs and
overhead will skyrocket. They fear they won’t be able to keep up
with the influx of new devices being added to the network or
aggregate data from multiple locations simultaneously. Are such
concerns warranted? Or can MQTT actually make life easier, not only
for Operations, but also for Information Technology teams?
Before deploying new technologies and rolling out new
infrastructure, IT Admins need assurances. Their jobs depend on
their ability to monitor networks and scale out infrastructure. They
also need to know that data moving through the network is secure,
and that it can be backed up adequately in the case of an outage or
Put your mind at ease. The Maple Solution with MQTT on one of our
HMIs or headless HMIs checksall the boxes:
Traffic sent between Edge Nodes, MQTT Brokers, SCADA systems,
and the Cloud can all be encrypted using Transport Layer
Security (TLS 1.2) and device certificates.
The Publish/Subscribe model of MQTT means that no additional
security compromises need to be made as far as opening network
ports or allowing incoming connections.
In short, data is encrypted end-to-end and no changes need to be
made to network firewall configurations.
MQTT is an inherently fault-tolerant, and latency-tolerant,
Device resource utilization (CPU, Network, and RAM usage) is
minimal, while messages can be delivered on a “best-effort”
If a device falls offline, Quality of Service and Data Retention
policies ensure that messages are delivered the next time the
device is online.
STANDARDIZED DATA FORMATS:
Because MQTT data is sent in an open-standard JSON file format,
all process variable tags and metadata are natively consumable
This makes it easy to integrate the data that devices send over
MQTT into existing IT processes.
Data can be stored in SQL databases, visualized using SCADA
historian software, or kept in Document Stores (also known as
MQTT allows for what is called “Decoupled” Infrastructure. Put
simply, this means that an MQTT Broker or SCADA System can go
offline, and it doesn’t stop you from doing business.
Example MQTT Network Layout
A resilient, distributed architecture with MQTT can be comprised of:
Any number of edge nodes and sensors at different locations,
publishing data to MQTT Topics
Maple Systems HMIs and headless HMIs actas MQTT Brokers,
subscribing to Topics relating to Edge Nodes, publishing data
into central repositories, SCADA systems, and MES systems, etc.
Where any two or more MQTT Brokers subscribe to the same set of
topics from Edge Nodes, redundancy is achieved. Even if one MQTT
Broker goes offline, a Single Source of Truth is maintained for
all Tags and Process Variables.
Learn more about our HMIs and headless HMIs Contact us with any
⇐ Back To IIoT Solutions
Please Sign in or Register to continue reading this article.