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 |
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.
Modules access Unified Namespace variables through two primary methods:
Direct Tag Access: Using tag names and paths
Tag.Machine1.Temperature
Asset Method Access: Using the Asset() function
Asset("/Line1/Machine1.Temperature")
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 |