Tags

General

Tags belong to devices which in turn belong to one or more workspaces. Therefore assignment of tags to workspaces happens on the device level.

A tag can have various entities like events, rules and formulas. More on this later.

It's important to know that changing a tag name could change/interrupt the receiving of new data since device data packets are processed to tags via their name. So when you want to provide more details on the tag, use the description field.

Creation

Tags can't be created by users. Instead they are automatically created from device data.

In case you want a derived value like an average or sum, you could use an aggregate for that. An aggregates creates a tag for the configured computation like an average.

Please refer to this page to read more about aggregates.

Type

Every tag can be of one type. Types can be seen as a category. Some examples of types are;

• Average flow

• Temperature

• Flow rate

• Flow totalized

• Temperature

• Humidity

• Wind speed

More types can be added by users with sufficient rights via the library as shown below. Types will in the near future be used to present tag data like min, max, color etc.

Formulas

A tag can have one or more mathematical formulas that will be executed on every incoming datapoint.

For example we have a formula of + 10 and a datapoint is received of 5, the datapoint stored in the database will then be 15.

Please refer to this page for more details about formulas.

Rules

A tag can have one or more rules.

Rules are business logic like for example creation of alarms at certain thresholds / setpoints. Rules are created in a workspace and afterwards

Please refer to this page for more details about formulas.

State

A tag can have one state. This state is normally 'normal', but if something happens this state could change. The following are the possible states;

• Normal

• Warning

• Danger

• Failure