Page History

HTML

<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 Tags<UDTs)</h1>

</div>

Introduction to the Unified Namespace

Image Added

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, improves enhances system interoperability, and simplifies the development of applications that utilize data from multiple sources.

Image Added

On this page:

Table of Contents

maxLevel	3
minLevel	2
style	none

Key Concepts and Terms

Info

icon	false
title	Info Box

TermDefinitionAsset TreeThe Asset Tree is a hierarchical representation of the physical equipment in the production environment

Asset Trees leverage 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 through data templates (UDT's). Additionally, the Asset Tree folders support categorizing and organizing tags and assets within the Unified Namespace, facilitating easier navigation and data comprehension.

Panel

bgColor	#ffffff

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 through data templates (UDT's). Additionally, the Asset Tree folders support categorizing and organizing tags and assets within the Unified Namespace, facilitating easier navigation and data comprehension.

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 data templates that match sensor readings, physical equipment, setpoints, recipes, management data, and all the variables necessary to implement and operate an application.

Data Template (UDT)

A user-defined data structure that includes variables

Panel

bgColor	#ffffff

Data Templates (UDT)

Data templates, or UDT's (User Data Types), 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 based on templates, each variable in the template is referred to as a property. An example of a data template is a simple PID information template with properties such as ProcessValue, Setpoint, and ControlValue. Panel

bgColor	#ffffff

External TagProviders

External TagProviders enable

.

TagProvider Connection

Enables direct interaction with variables in remote systems

, bypassing the need to create specific tags in the solution. They establish connections with tag sources, which can be set up in a table or directly in the assets, enhancing the versatility of data access and exploration

without creating specific tags, enhancing data access within the Unified Namespace.

Panel

bgColor	#ffffff

Enumerations

Enumerations define a series of

Enumeration

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

When connected to a tag, the enumeration value enhances data interpretation, providing context to the different states the variable can assume. PanelbgColor#ffffff

Runtime Database

The runtime database is an

An in-memory real-time database

that stores and manages

for 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

,

such as alarms and displays. The runtime database is implemented by the TServer.exe process,

ensuring efficient

and reliable

data management during solution execution.

Understanding the Unified Namespace

Module

Highlights

Features

Real-time Elements: The system has The system includes a built-in, real-time, event-driven, in-memory database , that manages the tags, assets, and events in within the application.
Real-time Tag Types: A Unlike typical HMI-SCADA system has only systems with basic tag types, such as numeric and messages. As the system also targets IT and MES systems, it goes far beyond, supporting this platform supports advanced real-time entities that match all the SQL types and many .NET Framework entities, including Images JSON objects and a complete DataTable DataTables in a single real-time tag.
Dynamic Arrays and References: The system offers built-in support for supports tri-dimensional dynamic arrays, lists, and type-safe reference tags with dynamic assignments, creating reusable components on for displays, symbols, reports, calculation and at any part of your solution. calculations, and other solution parts.

Tags vs TagProvider Connection

It’s important to distinguish between these two concepts:

Tag

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

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 AssetTree

Create a new folder: Organize and group assets using the new Asset Folder icon Image Added or right-click menu from the Root or parent node.
Create new Tags: Select a folder and use the New Tag toolbar Image Added button or right-click menu.
Move Tags: Drag tags to the desired folder.
Create TagProviders: Use the toolbar icon New TagProvider Image Added 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 iconImage Added.

→ Read more about Asset Tree .

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 that represent 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.

→ Read more about Tags .

Defining

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:

Creating Data Templates for Assets
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.