Unified Namespace: The Single Source of Truth for Your Factory

Imagine you are running a factory. Did the raw material arrive and get received? The answer is somewhere — maybe in the PLC’s memory. How many hours did the machine run? It’s logged in the machine’s log file. Did the work order start today? Check the ERP. What is the operator doing right now? Text them on WhatsApp.

The information exists, but it’s scattered everywhere. The manager wants to make a decision: “Will this order ship on time?” To answer, they open three different systems, check an Excel sheet, and phone the operator. Thirty minutes later, they have an answer.

This is a contradiction in the Industry 4.0 era. Hardware is internet-enabled. Data streams down from satellites. Yet inside a factory, collecting and consolidating data still requires manual work.

Here is an idea to solve this problem: Unified Namespace (UNS).

What Is Unified Namespace?

Unified Namespace is an architecture that binds all data sources in a factory — PLCs, machines, sensors, software systems — into one central tree of information.

Think of it like a file system. On your computer, documents are in /home/user/documents/. Music is in /home/user/music/. Photos are in /home/user/photos/. One place; information accessible from anywhere.

UNS applies the same idea to a factory. All data sources are published into a central namespace.

For example:

• /factory/machine-1/status — Is Machine 1 running?
• /factory/machine-1/temperature — What is the temperature right now?
• /factory/order-12345/start-time — At what time did work order 12345 start?
• /factory/operator-ali/assigned-job — What work order is assigned to Ali?

Every system publishes to this shared space in real-time. Everyone reads from the same source.

Why Unified Namespace?

What is the alternative? Each system owns its data. Connections are opened, APIs are built, integrations are soldered together. One system pulls data from the machine PLC, sends it to the ERP, notifies the MES. Each link is separate; each data transformation is distinct.

The problem is, this network is complicated and slow.

The machine finishes production, but the ERP hasn’t been notified yet. The MES screen shows “pending.” But the machine says “complete.” Which is true? The data comes from the original source — the machine PLC — yet the ERP is still holding stale information.

With UNS, it’s different. The machine PLC updates the /factory/machine-1/production-complete field. Everyone sees this. The ERP reads it. The MES reads it. All interfaces display it. Everyone is reading from the same fact. No contradiction.

Data Producer vs Data Consumer

The beauty of UNS is that it separates data production from consumption. The machine produces the status field. The ERP reads it; it does not write. The historian records it, but the machine owns the status field.

This clarifies responsibility. “If the status is wrong, check the machine software, not the ERP,” someone can say. Who is responsible? The machine. Why did it report incorrectly? Fix the code.

What Do You Gain?

1. No lag: When a machine finishes production, the entire system knows instantly. Planning, management, the operator — everyone learns at the same time.

2. Less wrong information: Instead of each system interpreting data its own way, all read from the original source. No mistranslation.

3. New tools integrate easily: Want to add a new system? Connect it to the central namespace, read what you need. No need to modify old systems.

4. Audit and accountability: Who changed what, and when? In UNS, it is all logged. When you ask “Why did this status change?” the log has the answer.

How Does It Work in Practice?

United Manufacturing Hub (UMH) is the name of the open-source project that operationalizes UNS. Here is the architecture:

• Data producers: PLCs, sensors, software systems — publish data to UNS (typically over MQTT).
• Central tree: A Kafka or MQTT broker (UMH commonly uses this).
• Data consumers: MES, ERP, BI tools, real-time dashboards — read from the central tree.
• Historian: All changes are recorded; you can query them later for analysis.

Common Objections

1. “All data in one place?” — Concern: privacy, scale. Answer: the central location can be on-premises or at an edge gateway. Data stays on your network.

2. “What are standard data fields?” — Every factory speaks differently. Standardization is the first step; UMH helps here. MQTT and JSON are foundational; communities extend from there.

3. “My old machine won’t output data.” — Write an adapter. If the machine cannot emit data, install a sensor; the sensor publishes to the central namespace.

The Takeaway

A factory runs on data. But if data is scattered, so is control. UNS gathers data and publishes it to one common space. Everyone reads from the same truth. Speed increases, errors decrease, decision-making becomes faster.

Tools like United Manufacturing Hub have engineered this architecture; starting today is no longer about technology — it is about discipline.