Page History

Key Concepts

and Terms

The purpose of the Unified Namespace is to provide a unified and organized data framework.

The key data modeling concepts to organize a Unified Namespace include:

Asset Tree

The Asset Tree is a hierarchical representation of the physical equipment in the production environment. It leverages a group of tags that effectively capture and reflect the real-time state of the equipment. This organized structure enhances data modeling and provides context for tags by establishing a common definition for a set of variables by creating tags based on through data templates (UDTs). Additionally, the Assets Asset Tree folders support categorizing and organizing tags and assets within the Unified Namespace, facilitating easier navigation and data comprehension.

Tags

A Tag tag represents real-time and historical data variables that modules can read, write, and subscribe to. Tags are Local can be local (created within the solution) or Remote remote (dynamically accessed via ExternalTags Sources connectivity). Additional metadata, known as Tag Attributes tag attributes (e.g., last update time, quality status, description), are automatically generated upon tag creation. Modules utilize tags in different various ways:

• Devices

• Module: Maps tag values to field equipment like PLC registers.

• Datasets

• Module: Links tags to SQL database tables and queries.

• Scripts

• Module: Performs analytics and calculations using tags.

• Historian

• Module: Creates a time-series archive of tag values.

• Displays Module: Enables operator displays to independently show values corresponding to tags, regardless of their data source.

Data Templates (UDT)

Data templates are user-defined data structures known as , or UDTs (User Data Types). That data structure , are user-defined data structures that can include variables of any type and references to other templates, creating a hierarchical data structure. When creating Tags tags based on Templatestemplates, each variable in the template is referred to as a Propertyproperty. An example of a data template is a simple PID information template with the properties such as ProcessValue, Setpoint, and ControlValue.

Enumerations

Enumerations define a series of potential values or ranges of values for a variable, mapping to messages and colors in to each state. When connecting with connected to a Tagtag, the enumeration value of the enumeration enhances data interpretation, providing context to the different states the variable can assume.

External TagProviders

The External TagProviders enable direct interaction with variables in remote systems, bypassing the need to create specific tags in the solution. It establishes They establish connections with tags tag sources, which can be set up in a table or directly in the assets, enhancing the versatility of data access and exploration in within the Unified Namespace.

Runtime Database

The runtime database is an in-memory real-time database that stores and manages the Unified Namespace data during the execution of a solution. It provides an event-driven data exchange of the values of tags and assets between various modules, like such as alarms and displays. The runtime database is implemented by implemented by the TServer.exe process, which ensures ensuring efficient and reliable data management.

Understanding the Unified Namespace 

Module Highlights

• Real-time Elements: The system has a built-in real- time, event driven, in-memory database, that manages the tags, assets and events in the application. 

• Real-time Tag Types: A typical HMI-SCADA system has only basic tag types, such as numeric and messages. As the system also targets IT and MES systems, it goes far beyond, supporting real- time entities that match all the SQL types and many .NET Framework entities, including Images and a complete DataTable in a single real-time tag.  

• Dynamic Arrays and References: The system offers built-in support for tri-dimensional dynamic arrays, lists and type-safe reference tags with dynamic assignments, creating reusable components on displays, symbols, reports, calculation and at any part of your solution.  

Configuring the Unified Namespace 

Configuration Workflow

The User Interface to build your models can be found Solution Designer tools, under the section Unified Namespace.

From that centralized interface, you can create or import Tag definition, organize the hierarchy and monitor the current values of your variables. 

When you start a new Solution, there already two folders pre-defined in the model.

• The "BaseTags" folder is where all new Tags are created by default.

• The "ExternalTags" folder is where all new External TagProviders connections are added by default. 

The typical process on creating the model is:

1. Creating Data Templates for Assets

2. Creating and Organizing Tags and Folders. Optionally you can use dynamic Tag definition from external data sources using the External TagProviders features. 

Typically the values of Tags will be read from physical Devices, like PLC's or field devices, or used in Displays, Scripts and other modules. But those configurations are executed in each module and not in the data model.

Defining Data Templates

Data Templates provide a way to create custom data structures that allow you to define reusable Tag configurations. They can be used to create hierarchical structures representing assets or information models, streamlining data management and improving system efficiency. For example, a template could be created for a specific type of equipment, with tags for its operational parameters and status information. 

Go to Data Templates for more information.

Asset Tree

The typical action when configuration the asset tree are:

• Create a new folder: Folders allow you to organize, group and create hierarchies for your assets. Click the new Asset Folder icon to create one or right click the Asset Tree.
• Create new Tags: After selecting a folder, use the New Tag toolbar button or right-click menu, to create a new tag inside that folder.
• Move Tags to selected folders: Just drag tags from the BaseTags folder — or other location — to the desired placement level at the tree.
• Insert Remote Assets: If there is a ExternalTags connection defined, you can insert specific assets from the external system in the asset tree.

For more information on the Asset Tree, visit Assets Tree.

The maximum number of tags that can be included in a solution, based on the Product Model of the license, follows the formula below: (ProductModel * 20) + 5000 = maximum number of tags allowed in the solution

Tags

Tag Objects represent real-time variables and their associated historical data within the Unified Namespace, managing and editing these objects ensures seamless integration with other modules and systems.

To learn more about aspects of managing Tags within the Unified Namespace, including Creating Tag Objects, Modifying Tag Objects, Deleting Tag Objects, Importing/Exporting Tag Objects, and using built-in tools for searching, filtering, and bulk-editing to optimize the management process, visit: Tags.

Enumerations

Enumerations are sets of named integer values used to represent discrete options or states. They can help improve code readability and reduce errors by assigning meaningful names to integer values. An example of an enumeration could be a set of named states for a pump, such as "Off", "On", and "Fault", with corresponding integer values of 0, 1, and 2.

To create and set up a new Enumeration, navigate to Unified Namespace → Enumeration. Then, click 'New' on the Grid toolbar to open the 'Create New Enumeration' pop-up window. Enter the name of the Enumeration and click 'Ok' to create a new one. Following this, add the properties of the Enumeration set. You can add On and Off options, set the default value to each one, for example, '1' for 'On' and '0' for 'Off', and customize any enumeration properties, such as ActiveColor and InactiveColor, and several other available properties.

Visit Enumerations for more information.

External TagProviders

The External TagProviders is a tool that allows you to access Data Models definitions from external systems, using those variables and structures in any module directly, without having to create any local definition of Tags inside your solution.

This feature is available for:

• InfluxDB

• MQTT SparkPlugB

• AB Rockwell - ControlLogix/CompactLogix Devices

• OPC UA 

• CanaryLabs

• Server to Server communication

• GE Proficy Historian

• SQLDatabase

For more information, visit External TagProviders.

Working with the Unified Namespace

Woking with the module

The User Interface to build your The user interface for building models can be found in the Solution Designer tools , under the section Unified Namespace section. From that this centralized interface, you can create or import Tag definitiontag definitions, organize the hierarchy, and monitor the current variable values of your variables.   When you start starting a new Solutionsolution, there already two folders pre-defined in the model.are predefined:

• BaseTags Folder: Where all new tags The "BaseTags" folder is where all new Tags are created by default.
• The "ExternalTags" folder is where ExternalTags Folder: Where all new External TagProviders connections are added by default. 

The typical process on creating the model is:

Typical Process for Creating the Model

1. Create data templates for assets.
2. Create and organize tags and folders. Optionally, use dynamic tag definitions

3. Creating Data Templates for Assets

4. Creating and Organizing Tags and Folders. Optionally you can use dynamic Tag definition from external data sources using the External TagProviders features. 
5. Typically

1. , tag values are read from physical

1. devices, like

1. PLCs or field devices, or used in

1. displays, scripts,

1. and other modules.

1. These configurations are executed in each module

1. , not in the data model.

Runtime Execution Execution

When you start the solution execution of your solutionstarts, the Unified Namespace definition in is loaded into a an in-memory Real-Time Database. The .NET process in the computer implementing that is named TServer.exe

Executable Process, ports, Diagram, data flow

During the execution the Realtime Database, or just called Runtime, provides an real-time database, implemented by the TServer.exe process. During execution, the real-time database provides event-driven data exchange of the values of Tags and Assets tag and asset values between various modules, like Alarms alarms and Displays.The chapter Runtime Environment has detailed displays. Detailed information on all aspects and process in place when running the solution.processes during runtime can be found in the chapter "Runtime Environment."

Accessing Assets

in Scripts and Expressions

Integration with Other Modules

The The platform's various modules of the platform, like Alarms and Displays, can easily access any variable from the Unified Namespace by using its full name or path.   For example, to access a tag when creating a an operator Displaydisplay, use "Tag." to access the available tags. A tag called Temperature from a data template named Machine 1 would have the full path: Tag.Line.Machine1.Temperature. The information on the Unified Namespace This information is also accessible to other application, applications using the built-in MQTT broker , or its native ability to act as an OPC Server. For detailed information, please refer to the corresponding sections within the document and on the pages OPC Server and Client Tools and MQTT Tools.

Third-party applications can also access that data using Integration APIs.

RemoteAssets methods

RemoteAssets Methods

RemoteAssets methods allow interaction RemoteAssets methods provide means to interact with assets remotely. They allow you provide functions to map and unmap entire assets , and refresh readings of the registered elements. :

RegisterElementToTag: This method allows you to map Maps an entire RemoteAsset to a Tag. It requires that you create a Template tag, requiring a template with the same structure as your the asset. 
@Client.RegisterElementToTag(string assetName, string tagName, [bool readOnly=false]) 

RefreshRemoteTags: Performs a new reading on the registered elements. 
@Client.RefreshRemoteTags() 

UnregisterElementToTag: Removes the RemoteAsset from the registered list. 
@Client.UnregisterElementToTag(string assetName)

UnregisterAllAssets: Removes All all RemoteAssets from the registered list. 
@Client.UnregisterAllAssets()

Advanced Unified Namespace Topics

Runtime Attributes

The Tag has attributes and methods that can be used in .NET scripts, and other system modules. The Unified Namespace Runtime Attributes page lists all options available.

Troubleshooting and Best Practices

Troubleshooting and Common #Issues

Some common issues that may arise while working with the Unified Namespace include:

#Inconsistency or missing data from external systems:

When using ExternalTags Sources, our software is dependent on ensure the external application to provide and maintain that section of provides and maintains the Unified Namespace, including the variables variable names and its structure.

Refer to the External TagProviders section of the manual on how to diagnose connections with external systems. for diagnosing connections.

When mapping Tags to Device Communication drivers, the Tag Definition is the Solution, so the Tag name will always show property in the Unified Namespace, but its value in depending on the connection with the remote device.

Refer the Devices, Field Communication section on the documentation for information on setup and diagnose connections with field devices. 

This concept applies to any external data source being used by the system, like remote SQL database or custom scripting using external APIs.

#Inconsistency or missing data after importing:

Ensure that the import files (Excel, CSV, or any other supported formatformats) are properly formatted and follow the guidelines mentioned in the documentation. Check if the , with required columns are present, and verify that the compatible data types and values are compatible with the destination tables.

#Performance issues

Here are some key areas to review when improving performance: 

#Target Solution

Analyze the structure and organization of your solutions. A well-organized solution with efficiently structured hierarchies can significantly improve system performance. 

#Driver Communication

• Target Solution: Structure and organize solutions efficiently to improve performance.
• Driver Communication: Use the Monitor Page

• and Runtime Diagnostics to monitor

#Displays

Busy and information overloaded displays can hinder system performance and make the solution more difficult to navigate for the user. Ensure that your screens have only the information they need to operate. 

#Optimization and Grouping

Only use tags that are necessary for your application. Excessive and unnecessary tags can create additional overhead that can hamper performance. Group tags logically based on functionality or the device they are associated with. This not only improves readability but also enhances system efficiency. 

#Reuse Assets

Try to reuse assets where possible. If two components use the same type of asset, consider using one asset and replicating it where needed. 

#Modular Templates

• driver communication.
• Displays: Avoid overloading displays with excessive information.
• Optimization and Grouping: Use only necessary tags, group them logically, and reuse assets when possible.
• Modular Templates: Design modular templates to reduce redundancy and streamline management.

Best Practices and #Recommendations

To get the most out of the Unified Namespace, follow these best practices:

#Organization of the data structure

• Organize tags into a clear hierarchy , using with folders and templates , to make it easier for users to find and understand the information they needfor easier navigation and understanding.
• Plan your data structure structures carefully, considering the relationships between assets, tags, and templates.
• Leverage Use templates to create for reusable data structures, reducing redundancy and streamlining data management. Create standard templates for common tasks. This not only saves time but also ensures consistency across your solution. 
• Integrate external data sources seamlessly using ExternalTags SourcesUse ExternalTags Sources to integrate external data sources, ensuring a seamless exchange of information between systems.
• Use a consistent naming convention conventions for your tags . It can make your solution easier to navigate and troubleshoot. to simplify navigation and troubleshooting.

#Status Monitoring 

Commonly used Tag Properties

Property

Type

Description

Value

Tag Type

Last Value of the Tag

Quality

Integer

Data Quality field, according OPC standards:

0: bad quality
64: undefined quality
192: good quality

Timestamp

DateTimeOffset

• Add to your solution specific Displays displays and Scripts scripts to regularly monitor and report the system performance , as well as the and connection status with the external data sourcesregularly. 
• Implement alarm conditions when critical connections are lost.

Unified Namespace Runtime Attributes

The Tag has attributes and methods that can be used in .NET scripts, and other system modules. 

This section describes only some commonly used properties.

• for critical connection losses.

In this section: