By Marc Taccolini, CEO & Founder, Tatsoft

Your First Step to Unified Namespace Starts at the Edge

The promise of an enterprise-wide Unified Namespace, a single source of truth for all industrial data, has captured the industry’s imagination. Walker Reynolds’ vision of breaking down data silos resonates deeply. Yet for many organizations, implementing an enterprise UNS feels like a massive IT project with unclear ROI and daunting complexity.

Consistent with the vision Aim high, start simple, scale without limits, the pragmatic path is to start with Local UNS nodes where operations happen, then federate upward. This approach delivers immediate value while building toward the enterprise vision.

Understanding the Two-Layer Model

Enterprise UNS: The Corporate Vision

The Enterprise UNS represents the ultimate goal—a corporate-wide nervous system where all data flows freely between systems. It’s the “single pane of glass” promise, typically implemented through:

• Central MQTT brokers (often cloud-hosted)
• Standardized topic structures across divisions
• IT-managed infrastructure
• Top-down governance models

Local UNS: Where Operations Live

A Local (or Solution-Level) UNS operates at the factory floor, production line, or facility level. It provides:

• Real-time operational data management
• Direct connection to equipment and processes
• Operations-owned and managed
• Immediate problem-solving capability

The Power of Starting Local

Every FrameworX installation functions as a complete UNS node for its operational area. This isn’t a limited subset—it’s a fully-capable UNS implementation that:

1. Organizes local data following ISA-95 or custom hierarchies
2. Connects directly to PLCs, sensors, and local systems
3. Operates independently ensuring production continuity
4. Publishes selectively to enterprise systems when ready

Building the Federation

Local UNS nodes naturally federate into enterprise systems. The architecture supports different roles at each level:

This layered approach means each operational level has the right-sized solution: EdgeConnect originates data from equipment, MachineHMI provides local operator interfaces, and Enterprise orchestrates facility-wide or multi-site operations. Each maintains its local namespace while participating in the larger structure.

Edge-First Architecture

[Equipment] → [Local UNS] → [Optional: Enterprise UNS]
| | |
[Local HMI] [Local Apps] [Corporate Systems]

Each local node:

• Maintains operational autonomy
• Publishes what’s relevant upstream
• Consumes enterprise data as needed
• Continues operating if enterprise fails

Selective Publishing

Not all data belongs in the enterprise. Local nodes intelligently filter:

• Publish up: KPIs, alarms, production counts
• Keep local: High-frequency sensor data, intermediate calculations
• On-demand: Historical data when requested

From Theory to Practice: UNS in 10 Minutes

• With FrameworX EdgeConnect (under $1,000), you can deploy your first UNS node today:
• Step 1: Install EdgeConnect on industrial PC or router
• Step 2: Connect to your PLCs/sensors
• Step 3: Auto-generate ISA-95 structure
• Step 4: Enable MQTT broker with one checkbox
• Step 5: Start collecting and contextualizing data

This solves immediate problems:

• Operators get unified data access
• Maintenance sees all equipment status
• Quality tracks production parameters
• All without waiting for enterprise IT

Real Implementation Examples

Scenario 1: Single Production Line

• Local UNS: FrameworX managing one line’s equipment
• Value: Unified operator view, local optimization
• Enterprise connection: Publishes OEE and production counts

Scenario 2: Multi-Site Corporation

• Local UNS: FrameworX at each facility
• Value: Site autonomy with standardization
• Enterprise connection: Regional brokers aggregate to corporate

Scenario 3: OEM Machine Builder

• Local UNS: FrameworX embedded in each machine
• Value: Self-contained machine intelligence
• Enterprise connection: Customer’s choice of integration

Why Local-First Succeeds

Immediate ROI

• Solve today’s problems without waiting
• Prove value before scaling
• Build expertise incrementally

Operations Ownership

• IT doesn’t become bottleneck
• Changes happen at operational speed
• Domain experts maintain control

Resilience by Design

• Production continues if enterprise fails
• No single point of failure
• Gradual migration reduces risk

Technical Advantages of FrameworX Local UNS

Native Implementation

• UNS is built-in, not bolted on
• Every tag automatically part of namespace
• No separate publishing layer needed

Protocol Flexibility

• MQTT Sparkplug B (one checkbox)
• OPC UA Server (one checkbox)
• REST APIs
• Custom protocols via scripting

Dynamic Extension

• Connect to external databases as UNS folders
• Bridge to other UNS implementations
• Extend without reconfiguration

The Path Forward

Starting with Local UNS nodes isn’t settling for less—it’s building a stronger foundation. Consider this progression:

Month 1: First local node solving real problem Month 3: Multiple nodes, local integration Month 6: Regional aggregation, enterprise pilots Year 1: Selective enterprise integration Ongoing: Continuous expansion as value proven

Conclusion: Global UNS Needs Strong Local Foundations

The future of industrial data does start with a Unified Namespace, but that namespace doesn’t have to start at the enterprise level. By deploying Local UNS nodes where operations happen, organizations can:

• Deliver immediate operational value
• Build toward enterprise vision pragmatically
• Maintain operational resilience
• Prove ROI incrementally

Every FrameworX installation is a future-ready UNS node. Whether it remains local or becomes part of a global namespace, the value starts immediately.