What is a unified namespace and why does it matter?
A unified namespace (UNS) is a single logical data layer, built on an MQTT broker, where every device, system and application in a factory publishes and subscribes to operational data through one central point. It replaces hundreds of point-to-point integrations with one hub-and-spoke topology. Walker Reynolds (Independent MES) documented the architecture in 2020. In a plant with 40 PLCs and 8 enterprise systems, a UNS reduces integration lines from over 1,500 to 40, cuts integration maintenance cost by an estimated 70 percent, and halves the time to connect a new data consumer.
Why point-to-point integration breaks down
In a traditional plant, each system talks directly to the ones it needs: the MES calls the PLC, the ERP calls the MES, the historian calls the PLC, the quality system calls the MES. With n systems, you can have up to n times (n minus 1) divided by 2 integration pairs. For 10 systems, that is 45 pairs. Each pair uses a different protocol, runs on a different schedule and breaks in a different way.
When an integration breaks, the system that depends on it fails silently or generates bad data. Debugging requires knowing which pair broke, which requires someone to know that the pair exists. In practice, in a plant with 50 integrations, nobody has a complete map.
How a unified namespace solves this
In a UNS, every data producer publishes to a topic on a central MQTT broker (HiveMQ, EMQX, Mosquitto, or AWS IoT Core). Every data consumer subscribes to the topics it needs. The PLC does not know who is consuming its data. The MES does not know where the data comes from. Adding a new consumer means adding a subscriber, not a new integration.
The topic hierarchy (enterprise / site / area / line / machine / tag) mirrors the ISA-95 model. Data is self-describing: each message carries the tag name, value, quality and timestamp. No integration documentation is needed because the topic path is the documentation.
When a UNS is and is not the right choice
A UNS is the right choice for a plant that expects to add more data consumers over time: new analytics tools, new AI models, new reporting dashboards. It pays back within 18 months in integration maintenance savings for plants with more than 15 connected systems.
A UNS is not the right choice for a single-vendor, tightly coupled system where the vendor controls all integrations. SAP Manufacturing Integration and Intelligence (SAP MII) and similar monoliths handle integration internally. Adding a UNS on top of a monolith adds complexity without benefit.
Related questions
Ajinkya Technologies has designed and deployed unified namespace architectures on EMQX and HiveMQ for steel, aluminium and automotive plants in India. Contact hello@ajinkyatechnologies.in for an IIoT architecture review.
Reviewed by Amey Kadle, Founder, Ajinkya Technologies. Last reviewed: 2026-09-08.