'/%3e%3c/mask%3e%3c/defs%3e%3cellipse%20cx='259'%20cy='244'%20rx='204'%20ry='196'%20fill='url(%23uns-abstract-halo)'/%3e%3crect%20x='24'%20y='32'%20width='470'%20height='424'%20fill='url(%23uns-abstract-dots)'%20mask='url(%23uns-abstract-mask)'%20opacity='.32'/%3e%3cg%20stroke='%23CBC2DE'%20stroke-width='1.15'%20stroke-linecap='round'%20opacity='.62'%3e%3cpath%20d='M259%20244C215%20244%20218%20174%20166%20174M259%20244C215%20244%20218%20314%20166%20314M259%20244C303%20244%20300%20174%20352%20174M259%20244C303%20244%20300%20314%20352%20314'/%3e%3cpath%20d='M166%20174C119%20174%20120%20110%2068%20110M166%20174C119%20174%20120%20220%2068%20220M166%20314C119%20314%20120%20268%2068%20268M166%20314C119%20314%20120%20378%2068%20378'/%3e%3cpath%20d='M352%20174C399%20174%20398%20110%20450%20110M352%20174C399%20174%20398%20220%20450%20220M352%20314C399%20314%20398%20268%20450%20268M352%20314C399%20314%20398%20378%20450%20378'/%3e%3c/g%3e%3cg%20fill='white'%20stroke='%23C8BDDC'%20stroke-width='1.15'%20opacity='.68'%3e%3ccircle%20cx='166'%20cy='174'%20r='6'/%3e%3ccircle%20cx='166'%20cy='314'%20r='6'/%3e%3ccircle%20cx='352'%20cy='174'%20r='6'/%3e%3ccircle%20cx='352'%20cy='314'%20r='6'/%3e%3c/g%3e%3cg%20fill='white'%20stroke='%23D6CEE4'%20stroke-width='1'%20opacity='.75'%3e%3ccircle%20cx='68'%20cy='110'%20r='3.5'/%3e%3ccircle%20cx='68'%20cy='220'%20r='3.5'/%3e%3ccircle%20cx='68'%20cy='268'%20r='3.5'/%3e%3ccircle%20cx='68'%20cy='378'%20r='3.5'/%3e%3ccircle%20cx='450'%20cy='110'%20r='3.5'/%3e%3ccircle%20cx='450'%20cy='220'%20r='3.5'/%3e%3ccircle%20cx='450'%20cy='268'%20r='3.5'/%3e%3ccircle%20cx='450'%20cy='378'%20r='3.5'/%3e%3c/g%3e%3ccircle%20cx='259'%20cy='244'%20r='30'%20stroke='%23DCD3EC'%20stroke-width='1'%20opacity='.45'/%3e%3ccircle%20cx='259'%20cy='244'%20r='13'%20fill='%23FAF8FE'%20stroke='%23C5B6DD'%20stroke-width='1.2'%20opacity='.8'/%3e%3ccircle%20cx='259'%20cy='244'%20r='3.5'%20fill='%23B9A7D9'%20opacity='.55'/%3e%3c/svg%3e)
'/%3e%3c/mask%3e%3c/defs%3e%3cellipse%20cx='259'%20cy='244'%20rx='204'%20ry='196'%20fill='url(%23uns-abstract-halo)'/%3e%3crect%20x='24'%20y='32'%20width='470'%20height='424'%20fill='url(%23uns-abstract-dots)'%20mask='url(%23uns-abstract-mask)'%20opacity='.32'/%3e%3cg%20stroke='%23514766'%20stroke-width='1.15'%20stroke-linecap='round'%20opacity='.62'%3e%3cpath%20d='M259%20244C215%20244%20218%20174%20166%20174M259%20244C215%20244%20218%20314%20166%20314M259%20244C303%20244%20300%20174%20352%20174M259%20244C303%20244%20300%20314%20352%20314'/%3e%3cpath%20d='M166%20174C119%20174%20120%20110%2068%20110M166%20174C119%20174%20120%20220%2068%20220M166%20314C119%20314%20120%20268%2068%20268M166%20314C119%20314%20120%20378%2068%20378'/%3e%3cpath%20d='M352%20174C399%20174%20398%20110%20450%20110M352%20174C399%20174%20398%20220%20450%20220M352%20314C399%20314%20398%20268%20450%20268M352%20314C399%20314%20398%20378%20450%20378'/%3e%3c/g%3e%3cg%20fill='%23151515'%20stroke='%235A4E72'%20stroke-width='1.15'%20opacity='.68'%3e%3ccircle%20cx='166'%20cy='174'%20r='6'/%3e%3ccircle%20cx='166'%20cy='314'%20r='6'/%3e%3ccircle%20cx='352'%20cy='174'%20r='6'/%3e%3ccircle%20cx='352'%20cy='314'%20r='6'/%3e%3c/g%3e%3cg%20fill='%23151515'%20stroke='%234F4563'%20stroke-width='1'%20opacity='.75'%3e%3ccircle%20cx='68'%20cy='110'%20r='3.5'/%3e%3ccircle%20cx='68'%20cy='220'%20r='3.5'/%3e%3ccircle%20cx='68'%20cy='268'%20r='3.5'/%3e%3ccircle%20cx='68'%20cy='378'%20r='3.5'/%3e%3ccircle%20cx='450'%20cy='110'%20r='3.5'/%3e%3ccircle%20cx='450'%20cy='220'%20r='3.5'/%3e%3ccircle%20cx='450'%20cy='268'%20r='3.5'/%3e%3ccircle%20cx='450'%20cy='378'%20r='3.5'/%3e%3c/g%3e%3ccircle%20cx='259'%20cy='244'%20r='30'%20stroke='%234F4563'%20stroke-width='1'%20opacity='.45'/%3e%3ccircle%20cx='259'%20cy='244'%20r='13'%20fill='%231B1824'%20stroke='%235E5080'%20stroke-width='1.2'%20opacity='.8'/%3e%3ccircle%20cx='259'%20cy='244'%20r='3.5'%20fill='%238573C8'%20opacity='.55'/%3e%3c/svg%3e)
Connect data across systems
Publish data to a shared namespace so multiple applications can consume it without separate source connections.
UNIFIED NAMESPACE
Unified namespace for industrial IoT
Contextualize industrial data so it’s easier for AI agents to use. Connect equipment, apps, and agents through a shared MQTT backbone powered by EMQX.
Overview
What is a unified namespace?
A unified namespace (UNS) organizes industrial data around a shared naming structure and agreed data models. Applications access that data through a common messaging hub.
Acme/Detroit/Assembly/Line01/Cell02/Press07/Temperature Temperature
72.4 °C- Asset
- Press07
- Time (UTC)
Benefits
Why adopt a unified namespace?
Reduce integration work and make operational data easier to find, share, and use.
Bring OT and IT together
Make equipment events available to business applications using a common naming structure and data context.
Support live operations
Deliver events as they occur to applications for monitoring, maintenance, and operational analysis.
Architecture
Building UNS architecture with EMQX
Factory Site A
EMQX Neuron
PLC
SCADA
Historian
Factory Site B
EMQX Neuron
Sensors
CNC Machine
Edge Devices
EMQX Enterprise
MQTT Pub/Sub
Topic Namespace
Rule Engine
Data Integration
Business Systems
ERP
MES
Historian
Analytics & AI
Big Data
AI/ML
AI agents
BI Dashboard
Cloud & Storage
Data Lake
Time Series DB
Cloud Platform
1. Connect equipment
Use gateways such as EMQX Neuron to collect PLC and sensor data, translate industrial protocols, and publish MQTT messages.
2. Route shared data
Use EMQX as the messaging hub. Route messages through shared topics and apply rules where data needs filtering or transformation.
3. Connect apps and agents
Connect MES, ERP, analytics, and AI agents to the data they need through MQTT subscriptions or supported integrations.
Capabilities
Why EMQX is the UNS foundation
Build your UNS on a scalable, reliable MQTT platform, connecting devices, apps, and agents from edge to cloud.
Scalable clustering
Expand broker capacity as the number of connected assets, sites, and applications grows.
Cluster deployment guideHigh availability
Use a broker cluster to reduce the impact of node failures and support planned maintenance.
Cluster architecture guideControlled data access
Use TLS, certificate authentication, and topic permissions to protect connections and restrict publishing and subscribing.
Client authorization guideData integration
Configure rules and supported connectors to route shared data to databases, messaging systems, and cloud services.
Data integration guideMQTT 5.0 support
Use features such as message expiry and user properties to manage message lifetimes and carry application metadata.
MQTT feature guideDecoupled applications
Add consumers without changing each producer, using shared topic and payload contracts.
Publish/subscribe guidePlan your unified namespace
Agree on data conventions, connect equipment, and introduce applications in manageable stages.
- 1
Define the UNS Hierarchy
Agree on topic names, payloads, units, timestamps, and ownership. Map the hierarchy to your sites, lines, and equipment.
- 2
Deploy EMQX & Edge Gateways
Deploy EMQX as the messaging hub. Connect industrial equipment through supported edge gateways and drivers, then verify data collection.
- 3
Configure Data Flow & Rules
Publish data to the agreed topics. Use rules to filter, transform, and route messages to the applications that need them.
- 4
Connect & Secure Applications
Connect apps and AI agents to relevant topics. Set client and topic permissions, then test data quality and failure recovery.
Products
Products for your unified namespace
Combine industrial connectivity, local messaging, and a central MQTT broker.
EMQX Neuron
Collect equipment data through supported industrial drivers and publish it over MQTT or Sparkplug B.
Explore NeuronEMQX Edge
Run local MQTT messaging at the edge and bridge selected topics to a central broker.
Explore EMQX EdgeEMQX Enterprise
Run a self-managed MQTT cluster as the central messaging hub for your unified namespace.
Explore EnterpriseResources
Explore EMQX for unified namespace
FAQ
Frequently asked questions
A UNS is an architecture pattern for organizing and sharing industrial data. It combines a consistent topic hierarchy, agreed payload models, and a messaging hub so authorized systems can find and consume relevant data.
EMQX provides the MQTT messaging hub, with clustering, access controls, rules, and data integration. Your team defines the namespace hierarchy, data models, and ownership conventions.
The equipment layer collects and converts OT data. The hub layer routes MQTT messages and applies configured rules. The application layer consumes data through subscriptions or integrations for monitoring, analysis, and business workflows.
Start with a focused use case and an agreed topic and payload model. Define names, units, timestamps, and ownership before connecting more equipment and applications.
Use TLS for connections, authenticate clients, and authorize which topics each client may publish to or subscribe to. Review access as applications and sites are added.
Yes. Use an industrial gateway such as EMQX Neuron to collect data through supported device protocols. Map that data into your agreed topics and payloads before publishing to EMQX.
Build your unified namespace with EMQX
Plan your namespace, equipment connectivity, and application integrations with our team.