Unified Namespace (UNS) Module Overview
UNS provides a centralized UNS Module links: Centralized real-time data repository with hierarchical organization for all solution data.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Pillar 1: Unified Namespace (UNS)
Purpose
The Unified Namespace (UNS) is your solution's data foundation - a single source of truth for all real-time and configuration data.
What to Build
|
|
|
|---|---|---|
|
|
|
Data Explorer
The DataExplorer tool streamlines UNS creation by enabling:
- Discovery - Browse MQTT brokers, OPC servers, PLCs, and SQL databases
- Import - Create tags and templates directly from discovered structures
- Validate - Test connections before adding to production
This tool reduces manual configuration time by 50-70% when building your tag structure during the Foundation phase.
→ Learn more in the DataExplorer How-to Guide
Next Steps
- [UNS (How-to Guide)] - Step-by-step configuration
- [UNS (Reference)] - Complete technical documentation
- [P2: Process Modules] - Connect to field devices
In this section...
| Page Tree | ||
|---|---|---|
|
Key Concepts
- Tag: Process variable representing real-time and historical data, created locally or accessed remotely
- Asset Tree: Hierarchical representation of solution data containing variables and DataTemplates
- DataTemplate (UDT): User-defined data structure including variables and references to other templates
- TagProvider Service: Direct interaction with variables in remote systems
- Enumeration: Named integer values representing discrete options or states with associated messages and colors
- Runtime Database: In-memory real-time database managing Unified Namespace data during solution execution
What It Does
- Creates and manages real-time data models with tags, templates, and enumerations
- Organizes data in hierarchical Asset Tree structure with folders and templates
- Enables dynamic connectivity to external systems through TagProvider connections
- Supports advanced data types including SQL types, .NET entities, and complete DataTables
- Provides tri-dimensional dynamic arrays and type-safe reference tags
- Maintains event-driven, in-memory database for real-time data exchange
Configuration Workflow
Unified Namespace Configuration Workflow | ||
|---|---|---|
| Step | Action | Description |
| Define DataTemplates | Create reusable structures | Design custom data structures for assets |
| Build Asset Tree | Organize hierarchy | Create folders and organize data structure |
| Create Tags | Define variables | Add tags based on templates or basic types |
| Configure Enumerations | Set discrete values | Define state options with messages and colors |
| Add TagProviders | Connect external data | Link to OPC-UA, MQTT, databases, or historians |
| Map Remote Data | Link to Asset folders | Connect TagProvider data to namespace locations |
Runtime Behavior
Data Loading and Management
When solution execution starts, the Unified Namespace definition loads into the in-memory real-time database (TServer.exe process). This database enables event-driven data exchange between all solution modules.
Data Access Methods
Modules access Unified Namespace variables through two primary methods:
Direct Tag Access: Using tag names and paths
- Example:
Tag.Machine1.Temperature - Supports both local tags and nested template properties
Asset Method Access: Using the Asset() function
- Example:
Asset("/Line1/Machine1.Temperature") - Required for TagProvider connections and dynamic references
Tag vs TagProvider Connections
| Aspect | Tags | TagProvider Connections |
|---|---|---|
| Definition | Local real-time variables within solution | Direct link to external system variables |
| Creation | Created and configured locally | Defined in remote system, linked dynamically |
| Data Mapping | Devices Module handles remote mapping | No local mapping required |
| Access Method | TagName or AssetPath | AssetPath only via Asset() method |
| Use Case | Core solution data requiring local control | Dynamic external data without local overhead |
Features Highlights
Advanced Data Types
- SQL-compatible types: Full support for database data types
- .NET Framework entities: Images, JSON objects, DataTables in single tags
- Dynamic structures: Tri-dimensional arrays, lists, and collections
- Type-safe references: Dynamic tag assignments with type validation
Hierarchical Organization
- Asset folders: Logical grouping matching physical equipment
- Nested templates: Composition and inheritance support
- Reusable components: Template-based design for displays, reports, calculations
- Clear data paths: Intuitive navigation through process hierarchy
External System Integration
- Protocol support: ControlLogix, OPC-UA, MQTT SparkPlugB
- Database connectivity: SQL databases, CanaryLabs, InfluxDB, OSIsoft PI
- Remote applications: Other FrameworX solutions
- Dynamic browsing: Real-time discovery of external data structures
Real-time Performance
- Event-driven updates: Millisecond timestamp precision
- In-memory database: High-performance data access
- Publish-subscribe model: Efficient module communication
- Store-and-forward: Reliable data handling during disconnections