Page History

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.

External

TagProvider Connection

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

Enumeration

Defines

Enumeration

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 matching 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:

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 → Namespace’s Asset Tree is is where you build your data definitiondefinitions. 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 Solutionsolution, the Asset Tree has includes a built-in folder "Base Tags" to keep all tags from the Root level (tags not associated with an AssetFolder), That allows a better visualization of your Asset Tree when there is large number of tags“RootTags” folder for all root-level tags, improving visualization for large tag sets.

Typical configuration process:

1. Creating Data TemplatesDataTemplates: Define reusable tag data structures.
2. Creating Tags and AssetFolders, organizing : Organizing your data.
3. Creating TagProviders and adding links in the folders to its : Add links to folders for external data.

Editing the

AssetTree

• Create a new folder: Folders allow you to organize, group and create hierarchies for your assets. Click Organize and group assets using the new Asset Folder icon to create one Image Added or right-click the Asset Treemenu from the Root or parent node.
• Create new Tags: After selecting Select a folder , and use the   New Tag   toolbar Image Added 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 — Drag tags to the desired placement level at the treefolder.
• Create TagProviders: If using that feature, create TagProvides with toolbar icon (. ), or right click or with the menu option File / New / Use the toolbar icon New TagProvider Image Added or the menu command File > New > TagProvider Connection.
• Insert Link Remote Assets:select any folder, rightData: Right-click a folder and use the context menu Add command "Link to Data from TagProvider, so you can insert specific data from the external system", or use the toolbar iconImage Added.

→ Read more about Assets Asset Tree.

Data Templates

Defining DataTemplates

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

→ Read more about Data Templates.

Configuring the Asset Tree

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

→ Read more about Assets Tree.

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.

Managing Tags Allows You To:

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.

• Create, Modify and Delete Tag Objects. 
• Import and Export 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 used to represent representing discrete options or states. By assigning meaningful names to integer values, you will improve , improving code readability and reduce reducing errors.   An example of this is a set of named states for a pump, such as "Off", "On", and "Fault", with corresponding integer values of For example, a pump’s states like “Off”, “On”, and “Fault” with values 0, 1, and 2.

To Create Enumerations

1. Go

1. to Unified Namespace

1. / Enumeration.
2. Click

1. ‘New’ on the

1. grid toolbar.
2. Open the

1. ‘Create New

1. Enumeration’ pop-up window.
2. Enter the

1. name of the

1. enumeration and click ‘OK’.
2. Add

1. properties to the enumeration set, such as

1. ‘On’ and ‘Off’ with default values.

→ Read more about Enumerations.

External TagProviders

The External TagProviders is a tool that allows you to access Data Models definitions from external systems.  You can also access 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

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 → Read more about External TagProviders.

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. During execution, the This real-time database provides enables event-driven data exchange of tag and asset values between various modules, like such as alarms and displays. → "Runtime (Solution Execution)."

Accessing Assets in Scripts and Expressions

The platform's various modules, 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" “Tag” to access available tags. A tag property called Temperature “Temperature” from a data template tag named Machine 1 “Machine1” would have the full path: Tag.Line.Machine1.Temperature 

This information is also accessible to other applications using the built-in MQTT broker or its native ability to act as an OPC Server.

RemoteAssets Methods

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

RegisterElementToTag: Maps an entire RemoteAsset to a tag, requiring a template with the same structure as 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)

.

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"UnregisterAllAssets: Removes all RemoteAssets from the registered list.
@Client.UnregisterAllAssets()

Anchor
BestPractices BestPractices

Best Practices and Troubleshooting

Best Practices and Recommendations

To get maximize the most out 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.
• Integrate Seamlessly integrate external data sources seamlessly using ExternalTags SourcesTagProviders.
• 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 regularly.
• 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

• .

Performance issues

Here are some key areas to review when improving performance: 

• Target Solution: Structure and organize solutions efficiently to improve performance.
• Driver Communication: Use the Monitor Page and Runtime Diagnostics to monitor 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.

In this section: