<style>
.text-span-6 {
    background-image: linear-gradient(99deg, rgba(170, 163, 239, .5), rgba(125, 203, 207, .5));
    border-radius: 50px;
    padding-left: 15px;
    padding-right: 15px;
}

#title-text {
display: none;
}

.panelgradient {
    background-image: linear-gradient(180deg, #d5def0, whitesmoke);
    border-radius: 8px;
    flex-direction: column;
    justify-content: center;
    align-items: center;
    padding: 4rem;
    display: flex;
    position: relative;
}

</style>


<div class ="panelgradient">

<h1 style="text-align: center;">Unified Namespace <br> (Tags and UDTs)</h1>

</div>



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

Tag

A process variable representing real-time and historical data, created locally or accessed remotely.

Asset Tree

A hierarchical representation of the solution data, containing variables and DataTemplates that match sensor readings, physical equipment, setpoints, recipes, management data, and all the variables necessary to implement and operate an application.

DataTemplate (UDT)

A user-defined data structure that includes variables and references to other templates, creating a hierarchical data structure.

TagProvider Connection

Enables direct interaction with variables in remote systems without creating specific tags, enhancing data access within the Unified Namespace.

Enumeration

Defines potential values or ranges for a variable, mapping messages and colors to each state.

Runtime Database

An 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 that match 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 TagProvider Connection

It’s important to distinguish between these two concepts:


TagTagProvider Connection
Definition

Tags represent real-time and historical data variables that modules can read, write, and subscribe to.

TagProvider Connections 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. If you want to map the value of the Tag with remote system, the Module Device handles that Configuration. 

Connection settings are defined in the solution, while the data, tag names, and structures are defined in the remote system, like OPC-UA Servers, MQTT Broker or Historian system.

Usage

Tags are central to the solution configuration and when used by various modules (Datasets, Scripts, Historian, Displays) and they be accessed either path its AssetPath and the Asset() methods, or directly by its TagName. 

Eg.: Tag.Area1/LIne1/State or Asset("Area1/LIne1/State")

TagProvider Connections are linked to folders within the Unified Namespace, which are dynamically populated according the contents of the remote System. The Modules access the values exclusively by its AssetPath and the Asset() method. 

Eg.: Asset("/Area1/Line1/State")


The decision to create Tags and the Devices Module to map its data, or to use TagProvider Connections, is discussed at the page Devices Module and TagProviders.

The key concept is that there are two very distinct ways to interface with external data, each with its own limitations and benefits. According to your requirements, one approach or the other will clearly be the best way to set up. For various solutions, it is likely that your Unified Namespace will have some data in local tags, mapped to devices, and some data dynamically driven by remote systems using the TagProvider Connection.

→ See more about TagProvider Connections.

Configuring the Unified Namespace

Configuration Workflow

The Unified Namespace’s Asset Tree is where you build your data definitions. 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 “RootTags” folder for all root-level tags, improving visualization for large tag sets.

Typical configuration process:

  1. Creating DataTemplates: Define reusable tag data structures.
  2. Creating Tags and AssetFolders: Organizing your data.
  3. Creating TagProviders: Add links to folders for external data.

Editing the AssetTree

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

→ Read more about Asset Tree.

Defining DataTemplates

DataTemplates allow you to create custom data structures for reusable tag configurations, streamlining data management and improving system efficiency by defining hierarchical structures that represent assets or information models.

→ Read more about DataTemplates.

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.

→ Read more about Tags.

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

  1. Go to Unified Namespace / Enumeration.
  2. Click ‘New’ on the grid toolbar.
  3. Open the ‘Create New Enumeration’ pop-up window.
  4. Enter the name of the enumeration and click ‘OK’.
  5. Add properties to the enumeration set, such as ‘On’ and ‘Off’ with default values.

→ Read more about Enumerations.

Using TagProvider Connections

To incorporate data from TagProviders into the Asset Tree:

  1. Select or create an AssetFolder.
  2. Right-click the folder and execute the command “Link Data from TagProvider”.

The Unified Namespace / TagProvider Connections page allows reviewing the list of defined TagProviders or browsing external data contents.

→ Read more about TagProviders.

Working with the Unified Namespace

Runtime Execution

When 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, if 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 the relationships between assets, tags, and templates.
  • Use templates for reusable data structures, reducing redundancy.
  • Seamlessly integrate external data sources using 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:

Crash when using recursive data model

  • Make sure you're not using recursive Data Models - for example, a template which contains another template that contains another template etc. This may cause the system to overload and crash.

Inconsistency or Missing Data from External Systems:

  • Ensure that the external application maintains the Unified Namespace, including variable names and structure.
  • Refer to the UNS TagProviders Connections section for diagnosing connection issues.
  • For device communication drivers, the tag name will always display correctly 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 diagnostic information.
  • This applies to any external data source, such as remote SQL databases or custom scripting using external APIs.

Inconsistency or Missing Data After Importing:

  • Ensure that import files (Excel, CSV, etc.) are properly formatted with the required columns and compatible data types.

In this section: