P1:Unified Namespace (Concept) is the first pillar on the Four Pillars methodology, it provides a centralized real-time data repository with hierarchical organization for all solution data. As the first pillar in the Four-Pillar methodology, it creates a standardized method for accessing and managing tags, assets, and external data sources.

In this page:


Unified Namespace → Tutorial | Concept | How-to Guide |  ISA-95 | Reference


Key Concepts

ConceptDescriptionExample
TagProcess variable representing real-time and historical dataTank01.Level, Pump01.Status
Asset TreeHierarchical representation of solution data/Plant/Area1/Line1/Equipment
UserType (UDT)Reusable data structure with variables and referencesMotor template with Speed, Current, Status
TagProvider ServicesDirect interaction with variables in remote systemsOPC UA server, MQTT broker connections
EnumerationNamed integer values with messages and colors0=Stopped, 1=Running, 2=Fault
Runtime DatabaseIn-memory real-time database managing UNS dataTServer.exe process


What the UNS Does

The Unified Namespace serves as your solution's data backbone:

Data OrganizationSystem Integration
  • Creates real-time data models with tags and templates
  • Organizes data in hierarchical Asset Tree structure
  • Maintains relationships between equipment and data
  • Provides intuitive navigation through process hierarchy
  • Enables dynamic connectivity to external systems
  • Supports advanced data types including SQL datasets and JSON objects
  • Provides type-safe references and up to  tri-dimensional arrays
  • Maintains event-driven, in-memory database



Configuration Workflow

StepActionTool (Designer UI)Tools
1. Define UserTypesCreate reusable structuresUNS → UserTypesTemplate Editor
2. Build Asset TreeOrganize hierarchyUNS → Asset TreeAsset Browser
3. Create TagsDefine variablesUNS → TagsTag Editor, DataExplorer
4. Configure EnumerationsSet discrete valuesUNS → EnumerationsEnumeration Editor
5. Add TagProvider ServicesConnect external dataUNS → TagProvider ServicesTagProvider Services
6. Map Remote DataLink to Asset foldersUNS → Asset TreeAsset Mapping


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


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 with millisecond precision.

Data Access Methods

Modules access Unified Namespace variables through two primary methods:

Direct Tag Access (Local Tags)Asset Method Access: Using the Asset() function

Using tag names

  • Example: Tag.Machine1.Temperature
  • Supports both local tags and nested UserType properties

When connecting the tag with the field device

  • Use the Devices Module to map the Tag to a DevicePoint
  • If the protocol has TagDiscovery, you can use the DataLink field
    • In this case only the TagProvider services must be enabled
  • Example: Asset("/Line1/Machine1.Temperature")
  • Local Tags can be also use this syntax

TagProvider TagDiscovery Service

  • If the protocol supports TagDiscovery (OPC UA, MQTT, ..)
    • Dynamic Tags can created in runtime as a Asset("path") is used. 
    • see  more at ->


Features Highlights

Advanced Data Types

  • SQL-compatible types - Full database data type support
  • .NET entities - Images, JSON, DataTables in single tags
  • Dynamic structures - Tri-dimensional arrays, lists, collections
  • Type-safe references - Dynamic tag assignments with validation

Hierarchical Organization

  • Asset folders - Logical grouping matching equipment
  • Nested templates - Composition and inheritance support
  • Reusable components - Template-based design patterns
  • Clear data paths - Intuitive navigation through hierarchy

External System Integration

  • Protocol support - ControlLogix, OPC-UA, MQTT SparkPlugB
  • Database connectivity - SQL, CanaryLabs, InfluxDB, OSIsoft PI
  • Remote applications - Other FrameworX solutions
  • Dynamic browsing - Real-time discovery of 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 handling during disconnections


Common Implementation Patterns

ISA-95 Model Implementation


evelAsset StructureTypical Tags
Enterprise/CompanyKPIs, Financial metrics
Site/Company/Site1Production totals, Energy usage
Area/Company/Site1/Area1Area production, Quality metrics
Line/Company/Site1/Area1/Line1Line speed, Product counts
Cell/Company/Site1/Area1/Line1/Cell1Equipment status, Process values

Naming Convention Best Practices


Standard Format: [Area]_[Equipment]_[Component]_[Signal]

Examples:
WTP_PUMP01_MOTOR_RUNNING
WTP_PUMP01_MOTOR_SPEED_SP
WTP_TANK01_LEVEL_PV
BLDG_HVAC_AHU01_TEMP_SP

if using UDT SP is BLDG_HVAC_AHU01_TEMP.SP


Standard Format: [Area]/[Equipment]/[Component][Signal].[Attribute]

Examples:
WTP/PUMP01/MOTOR/RUNNING
WTP/PUMP01/MOTOR/SPEED.SP
WTP/TANK01/LEVEL.PV
BLDG/HVAC/AHU01/TEMP.SP

Standard Format: [Area]/[Equipment]/[ComponentUDT].[Signal]

Examples:
WTP/PUMP01/MOTOR.RUNNING
WTP/PUMP01/MOTOR.SPEED.SP
WTP/TANK01/LEVEL.PV
BLDG/HVAC/AHU01.TEMP.SP

Development Efficiency Tools

  • Bulk operations - Import/export via Excel, CSV
  • Search and filter - Quick tag location and editing
  • Template library - Reusable component repository
  • Cross-reference - Find tag usage across modules
  • Version tracking - Built-in change management


  • Rename any Tag , anytime - Without losing configuration integrity and runtime online updates. 
  • Cross-reference Tag usage - on-the-fly update, information is always instantly available


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...