General Settings

The General Settings section ensures that the measurements generated from the data collection are named in a way, that is both unique, follows the ISA-95 standard and guarantees uniqueness in the cloud storage (Data Store).

General setting for a Tag

Naming

When creating a tag, the first thing to consider is the tag name. The tag name can be chosen arbitrarily, but must be unique within the asset and should also be descriptive for the purpose or source definition.

While data points are named in a certain standard, at the factory floor level, this naming is not necessarily what is desired in the cloud environment. Maybe data is collected from different data sources, using different naming standards. The tag naming is able to align and standardize the naming standard across multiple assets and sites.

There are 3 ways to identify a tag:

• Tag Name: Name given by the user. This name is only unique on the asset where the tag is defined, and should describe the purpose or source definition of the data point. The tag name can be changed without losing the measurements already collected.

• Hierarchical Name: The hierarchical name names the tag uniquely withing the Asset hierarchy where it is defined, by using the hierarchical location to uniquely generating a name. The name is determined from the hierarchy structure, in a ISA-95 style tag naming, where each element (area / asset) from the root node down to the asset where the tag is defined, separated by punctuations, is prefixing the tag name. For more details see ISA-95.

• Cloud Id: The cloud id is an unique identifier that is created with the tag, and never changes. Since the tag name can be changed, the cloud id ensures that data already collected still belongs to the same tag, even if its name is changed. Data stored in the cloud is always identified by cloud id.

Access

Tags can either be Read or Write, defining the direction of data (measurements).

• Read: Measurements originate from the factory floor, are read and processed at the edge device, and stored in cloud. Reading does not change data at the factory floor.

• Write: The measurements originate from other tags, and are written back to the factory floor, changing values at the site.

Read operations are always supported, but not all Data Connectors support Write operations. If the chosen Data Connector supports write operations, the tag Write option will be available.