Unified Namespace (UNS)

The UNS eliminates data silos by providing one canonical location for every piece of industrial data. Rather than duplicating a temperature reading in an MES, a historian, and a dashboard, the value exists once in the namespace.

• Tag resolution maps a logical asset name to its current value
• Consumers always read from the authoritative source
• Eliminates reconciliation errors between systems
• Example: Enterprise/SiteA/Line3/Press1/Temperature resolves to a single, current value regardless of which application requests it

The UNS organizes data according to the ISA-95 equipment hierarchy, creating an intuitive, browsable namespace that mirrors the physical factory.

• Enterprise → Site → Area → Line → Cell → Equipment
• Structure provides semantic context without external lookups
• Enables hierarchical aggregation and drill-down analytics
• Example: Aggregating OEE from all cells within a line requires only navigating up one level in the namespace

Producers and consumers never communicate directly. Instead, they interact through a message broker using a publish-subscribe pattern, typically implemented with MQTT Sparkplug or OPC UA PubSub.

• Producers publish data without knowledge of consumers
• Consumers subscribe to topics without knowing the producer
• Enables plug-and-play interoperability
• Adding a new analytics dashboard requires zero changes to PLC code
• Systems can be upgraded or replaced independently

Data is transmitted only when a value changes beyond a defined deadband threshold, not on a fixed polling cycle. This dramatically reduces network load while ensuring timely delivery of meaningful changes.

• A temperature reading at steady state generates zero network traffic
• A sudden spike is transmitted immediately
• Typical deadband: ±0.5% of span or ±1°C
• Reduces bandwidth consumption by 90% or more compared to cyclic polling
• Critical for scaling to thousands of tags across a factory

Unlike raw MQTT, a UNS built on Sparkplug maintains awareness of device state and session continuity. Each participant reports a Birth Certificate on connection and a Death Certificate on disconnection.

• Birth Certificate: publishes all tag values and metadata on connection
• Death Certificate: notifies all subscribers of graceful or ungraceful disconnection
• Enables store-and-forward for disconnected edge devices
• Consumers always know if data is stale due to a disconnected producer
• Critical for mission-critical industrial applications

A true UNS is built on open, non-proprietary standards to avoid vendor lock-in and ensure long-term interoperability across heterogeneous equipment.

• MQTT: OASIS standard for lightweight pub/sub messaging
• Sparkplug: Eclipse Tahu specification for industrial MQTT payloads
• OPC UA: IEC 62541 standard for industrial interoperability
• Any compliant client can participate regardless of vendor
• Protects against obsolescence and enables best-of-breed component selection

The process of translating a logical asset name into its current real-time value and metadata by navigating the UNS topic tree. For example, a query for Site3.PackagingLine.Filler.Pressure resolves to:

• Value: 2.31 bar
• Timestamp: 2024-01-15T14:23:01.001Z
• Data Type: Float32
• Engineering Units: bar
• Quality: Good Tag resolution abstracts the physical connection details, allowing applications to request data by asset context rather than by IP address or register number.

The process of attaching machine-readable meaning to raw UNS data points by linking them to formal ontologies. This transforms a tag like Temp_247 into a semantically rich entity:

• isA: TemperatureSensor
• measures: CoolantTemperature
• belongsTo: CNC_Machine_05
• hasUnit: Celsius Semantic annotation enables automated reasoning, cross-site data discovery, and self-service analytics where users can query for 'all coolant temperatures across all CNC machines' without knowing specific tag names.

A formal agreement between a data producer and its consumers that defines the schema, semantics, and quality guarantees of data published into the UNS. A contract specifies:

• Schema: Field names, data types, and structure
• Semantics: Business meaning of each field
• Quality SLAs: Completeness, freshness, and accuracy thresholds
• Versioning: Compatibility rules for schema evolution Data contracts prevent downstream breakage when producers change their payloads, ensuring the UNS remains a trustworthy single source of truth.