Unified Namespace
(Tags and UDTs)
Introduction to the Unified Namespace
The Unified Namespace provides a centralized data repository and a standardized method for organizing and accessing data from various sources. This concept streamlines data management, enhances system interoperability, and simplifies the development of applications that utilize data from multiple sources.
On this page:
Key Concepts and Terms
Asset Tree
A hierarchical representation of the solution data, containing variables and data templates matching sensor reading physical equipments, setpoints, recipes, management data, and all the variables necessary to implement and operate an application.
Data Template (UDT)
User-defined data structure that includes variables and references to other templates, creating a hierarchical data structure.
External TagProvider
Enable direct interaction with variables in remote systems without creating specific tags, enhancing data access within the Unified Namespace.
Tag
Process variable representing real-time and historical data, created locally or accessed remotely.
Enumeration
Define potential values or ranges for a variable, mapping messages and colors to each state.
Runtime Database
In-memory real-time database for Unified Namespace data, ensuring efficient data management during solution execution.
Understanding the Unified Namespace
Module Features
Real-time Elements: The system includes a built-in, real-time, event-driven, in-memory database that manages tags, assets, and events within the application
Real-time Tag Types: Unlike typical HMI-SCADA systems with basic tag types, this platform supports advanced real-time entities matching all SQL types and many .NET Framework entities, including JSON objects and complete DataTables in a single real-time tag.
Dynamic Arrays and References: The system supports tri-dimensional dynamic arrays, lists, and type-safe reference tags with dynamic assignments, creating reusable components for displays, symbols, reports, calculations, and other solution parts.
Tags vs External TagProviders
It’s important to distinguish between these two concepts:
| Tag | External TagProvider | |
|---|---|---|
| Definition | Tags represent real-time and historical data variables that modules can read, write, and subscribe to. | External TagProviders enable direct interaction with variables in remote systems, bypassing the need to create specific tags within the solution. |
| Creation | Tags are created locally within the solution. | Connection settings are defined in the solution, while the data, tag names, and structures are defined in the remote system. |
| Usage | Tags are central to the solution configuration and are used by various modules (Devices, Datasets, Scripts, Historian, Displays). | External TagProviders facilitate the use of remote data directly within the solution, supporting protocols like OPC UA, MQTT, and various historian systems. |
Configuring the Unified Namespace
Configuration Workflow
The Unified Namespace’s Asset Tree is where you build your data definition. From this central point, you can create or import tags, organize the hierarchy, and monitor the current values of your variables.
When you start a new solution, the Asset Tree includes a built-in “Base Tags” folder for all root-level tags, improving visualization for large tag sets.
Typical configuration process:
- Creating Data Templates: Define reusable tag data structures.
- Creating Tags and AssetFolders: Organizing your data.
- Creating TagProviders: Add links to folders for external data.
Editing the Assets Tree
- Create a new folder: Organize and group assets using the new Asset Folder icon
or right-click menu from the Root or parent node. - Create new Tags: Select a folder and use the New Tag toolbar
button or right-click menu. - Move Tags: Drag tags to the desired folder.
- Create TagProviders: Use the toolbar icon New TagProvider
or the menu command File > New > TagProvider Connection. - Link Remote Data: Right-click a folder and use the context menu command "Link Data from TagProvider", or use the toolbar icon
.
Defining Data Templates
Data Templates allow you to create custom data structures for reusable tag configurations, streamlining data management and improving system efficiency by defining hierarchical structures representing assets or information models.
→ Read more about Data Templates.
Defining Tags
The page Unified Namespace → Tags allows you to:
Create, modify, and delete tag objects.
Use built-in tools for search and filtering.
Bulk-edit.
Defining Enumerations
Enumerations are sets of named integer values representing discrete options or states, improving code readability and reducing errors. For example, a pump’s states like “Off”, “On”, and “Fault” with values 0, 1, and 2.
To Create Enumerations
- Go to Unified Namespace → Enumeration.
- Click ‘New’ on the grid toolbar.
- Open the ‘Create New Enumeration’ pop-up window.
- Enter the name of the enumeration and click ‘OK’.
- Add properties to the enumeration set, such as ‘On’ and ‘Off’ with default values.
→ Read more about Enumerations.
Using External TagProviders
To incorporate data from TagProviders into the Asset Tree:
- Select or create an AssetFolder.
- Right-click the folder and execute the command “Insert Link to TagProvider”.
The Unified Namespace → External TagProviders page allows reviewing the list of defined TagProviders or browsing external data contents.
Working with the Unified Namespace
Runtime Execution
When the solution execution starts, the Unified Namespace definition is loaded into an in-memory real-time database, implemented by the TServer.exe process. This real-time database enables event-driven data exchange of tag and asset values between various modules, such as alarms and displays.
Accessing Assets in Scripts and Expressions
Modules like Alarms and Displays can access any variable from the Unified Namespace using its full name or path. For example, to access a tag when creating an operator display, use “Tag” to access available tags. A property called “Temperature” from a template Tag named “Machine1” would have the full path: Tag.Machine1.Temperature.
You can also access values using the Asset() method syntax. For, example you place the tag defined in the previous example inside a folder called Line1 the path for that value would be:
Asset ("/Line1/Machine1.Temperature")
Best Practices and Troubleshooting
Best Practices and Recommendations
To maximize the benefits of the Unified Namespace, follow these best practices:
Organization of the Data Structure
- Organize tags into a clear hierarchy with folders and templates for easier navigation and understanding.
- Plan data structures carefully, considering relationships between assets, tags, and templates.
- Use templates for reusable data structures, reducing redundancy.
- Seamlessly integrate external data sources using External TagProviders.
- Use consistent naming conventions for tags to simplify navigation and troubleshooting.
Status Monitoring
- Add specific displays and scripts to regularly monitor system performance and connection status.
- Implement alarm conditions for critical connection losses.
Common Issues and Solutions
Some common issues while working with the Unified Namespace include:
Inconsistency or Missing Data from External Systems:
- Ensure the external application maintains the Unified Namespace, including variable names and structure.
- Refer to the UNS External TagProviders section for diagnosing connections.
- For device communication drivers, the tag name will always show properly in the Unified Namespace, but its value depends on the connection with the remote device.
- Refer to the Devices (Field Communication) section in the documentation for setup and diagnosis information.
- This applies to any external data source, like remote SQL databases or custom scripting using external APIs.
Inconsistency or Missing Data After Importing:
- Ensure import files (Excel, CSV, etc.) are properly formatted with required columns and compatible data types.
In this section: