Skip to main content
Building block image with the center block in purple representing partners

Connecting the shop floor to the UNS HighByte

Learn how industrial sites can create a single, trusted operational data layer (UNS) that provides consistent, contextualized, and governed data to all OT and IT consumers.

Overview

Architecture Hub UNS HighByte overview no text

Industrial organizations face challenges in harmonizing diverse data sources across OT and IT systems. By combining Siemens Industrial Edge for secure, local data collection and HighByte Intelligence Hub as the semantic integration layer, manufacturers can implement a Unified Namespace (UNS) that ensures data consistency, scalability, and governance across the enterprise.

Detailed architecture

Siemens Industrial Edge

  • Collects data from automation and field devices using OPC UA, MQTT, REST, Modbus, etc.
  • Performs local preprocessing: filtering, aggregation, normalization, time alignment, and lightweight edge logic where required.
  • Acts as an OT gateway with secure connectivity (TLS, certificate-based auth) into the enterprise/UNS boundary.
Architecture Hub UNS HighByte details no text

Description

HighByte Intelligence Hub as the UNS (semantic & integration layer)

  • Implements the Unified Namespace by mapping raw tags/points into canonical asset models, standardized tag names, units, and hierarchies.
  • Performs data shaping and enrichment (asset metadata, location, process context, shift/production context).
  • Publishes well-structured, schema-validated streams and enforces data contracts for downstream consumers (MQTT topics, Kafka, REST, exports).
  • Manages schema versioning, transformations, retention rules and buffering for consumers with different latency needs.

Integration & operationalization

  • Use a publish/subscribe pattern: Industrial Edge -> HighByte -> consumers (SCADA, MES, analytics, dashboards).
  • Enforce RBAC, logging, and audit trails in HighByte; secure OT/IT boundary via Industrial Edge controls (DMZ patterns).
  • Provide adapters for historical systems (historians, databases) and real-time clients (HMIs, OEE dashboards) to subscribe to UNS streams.

Values & benefits

Components