Skip to main content
Architecture of the Future

Unified Namespace Platform
for Industrial IoT

A unified namespace gives every team and system a single, consistent way to understand factory data. Proxus helps you replace scattered tag lists and fragile point-to-point connections with a live, hierarchical model of sites, lines, equipment, and metrics.

Proxus UNS Explorer - Real-time hierarchical view of industrial data

The Reality: Spaghetti Integration The Solution: Unified Namespace

Watch how UNS transforms point-to-point chaos into a real-time data fabric.

UNS Single Source
Hover to pause

What is a Unified Namespace?

A Unified Namespace (UNS) is a single, well-structured topic hierarchy where all operational data lives: events, metrics, states, alarms. Instead of every system talking directly to every other system, each one:

  • Publishes what it knows to the UNS once
  • Subscribes to what it needs from the UNS when required

This eliminates point-to-point integrations, breaks data silos, and gives IT and OT teams a shared, real-time view of the factory. In Proxus, the UNS is not a slide in a presentation – it is the core runtime architecture.

From Spaghetti to Single Source of Truth

  • Publish once, consume everywhere
    Devices, SCADA, MES, ERP and analytics all connect to the same hub.
  • Security by design
    Edge Gateways initiate outbound connections; no inbound PLC ports.
  • Real-time, event-driven
    MQTT + High-Performance Message Bus ensure low-latency streams with guaranteed delivery.

Structured Data, Not Chaos

Proxus supports the ISA-95 standard hierarchy. This ensures that any application, AI model, or human knows exactly where to find data without asking the original integrator.

  • Self-aware Data Topics
  • Sparkplug B Payload Compression
  • Automatic Birth/Death Certificates
// Topic Structure Example
Enterprise (Proxus_Global)
Site (Istanbul_Factory)
Area (Assembly_Line_1)
Robot_Arm_04
metrics/Temperature
metrics/Status
metrics/OEE

How Proxus Implements UNS

Proxus is built from the ground up around the UNS concept. Instead of bolting MQTT on top of a legacy platform, Proxus uses an actor-based architecture where every major component speaks the same language.

  • Edge Gateways
    Stateless Gateways collect data from PLCs and fieldbuses, normalise tags and publish them into the UNS. If connectivity drops, the internal backbone buffers every event.
  • Central UNS Broker
    A highly-available MQTT broker becomes the Single Source of Truth for all plants, sites and applications.
  • Central Data Pipeline & Storage
    On the central server, the data pipeline consumes UNS streams and persists telemetry to PostgreSQL and ClickHouse without impacting the broker.
  • UNS Tree & Dashboards
    The UNS Tree Monitor and Blazor dashboards read from a high-performance in-memory cache, not directly from PLCs, ensuring real-time UI without extra load on the plant network.

End-to-End Data Flow

Devices
Edge Gateway
UNS (MQTT)
Rules & Functions
DB & Analytics
Dashboards & AI

All of this is configured from a single place: the Proxus central server. Gateways remain stateless and can be redeployed or replaced without losing their role in the UNS.

Why UNS with Proxus?

Whether you are modernizing a single line or rolling out across multiple plants, a Unified Namespace dramatically reduces integration cost and accelerates digital projects.

1. Real-Time Visibility

Operators, maintenance and management all see the same live data set: OEE, alarms, energy metrics and more – without building yet another custom dashboard per system.

2. Lower Integration Cost

New applications (MES, CMMS, AI platforms) subscribe to existing topics instead of requiring new point-to-point connectors. Projects move from months to weeks.

3. Future-Proof Data Model

A clean, ISA-95-aligned topic structure means AI, digital twins and analytics teams can explore data without constantly touching production systems.

Ready to make UNS your Single Source of Truth?

Learn how Proxus implements UNS in real factories and how you can roll it out step by step – from a single line to a multi-site architecture.

Read the UNS Architecture Guide Deep Dive: Architect's Guide to UNS