Is a Unified Namespace just an MQTT broker?

No. MQTT is the most common transport, but the UNS is the agreed topic structure, payload conventions, and governance on top of the broker. Two plants can run identical brokers and only one of them has a UNS.

Do I need ISA-95 to build a UNS?

Not strictly, but most teams borrow the ISA-95 equipment hierarchy (enterprise / site / area / line / cell) for the topic tree because operators, MES, and ERP already think in those terms. What matters is that one documented convention exists and is enforced.

Does a UNS replace my historian or MES?

No. The UNS is the real-time exchange layer. Historians keep long-term storage and MES keeps execution logic; both become publishers and subscribers on the namespace instead of one-off integration endpoints.

Unified Namespace

A UNS is not just MQTT. It is governed operational meaning in motion.

A Unified Namespace is an event-driven information space where systems publish and consume contextualized industrial data through a shared structure. Producers and consumers connect once to the namespace instead of to each other, so it becomes the single, current picture of the operation.

Visual Model

Topic structure plus semantic context plus governance.

enterprise/site/area

Business and plant hierarchy that consumers can understand.

line/cell/asset

Asset and process location of the event or state.

state/event/metric

Current operational meaning, not just raw tags.

quality/context

Payload conventions, data quality, ownership, and lifecycle rules.

Broker

The broker can move messages, but it does not define the business meaning by itself.

Model

The namespace needs hierarchy, semantics, payload conventions, state definitions, and ownership.

Governance

Security, lifecycle, access control, lineage, and stewardship keep the namespace trustworthy.

The UNS should unify information, not flatten security.

It does not replace Purdue segmentation, industrial DMZ patterns, zones, conduits, identity, certificates, access control, or write-path restrictions. It connects business-facing information while respecting operational risk.

Field Notes

How UNS attempts actually fail.

Flat or device-oriented topic trees (PLC and tag names) that force every consumer to know the wiring instead of the business structure.
Publishing raw tag values with no units, quality, or timestamps — moving data is not the same as publishing information.
No owner for the convention, so every team invents its own branch and the namespace fragments within months.
Big-bang scope. Model one line end to end, prove a consumer on it, then expand.

Go deeper: ISA-95 supplies the hierarchy vocabulary most topic trees borrow, Sparkplug B standardizes the MQTT payloads and session state underneath, contextualization keeps the published values meaningful, and the Minimum Technical Requirements gate the technology choices. You can check a draft topic convention with the free UNS convention checker.