Creating Tags
  • 26 Sep 2023
  • 6 Minutes to read
  • PDF

Creating Tags

  • PDF

Article Summary

N3uron simplifies the process of generating robust data models that make up a single source of truth. This means that every update at the node is automatically shareable with all other applications throughout the Enterprise, reducing the potential for discrepancies and data siloing.

Tags are created in the WebUI's interface, where users can create tags manually, import a csv file containing one or more tags, or create a new template instance. It's also possible to create folders that help improve the organization of tag hierarchies in the model. 

Tags can be created manually in the Model panel. Users can create a single tag, a group, or a template instance.  

In order to create tags, all main properties must be configured:

  • Data format
  • Scaling
  • Views
  • Data Source
  • Alarms
  • History

 The following steps will explain in detail how to create a tag and configure each available option in N3uron.

  • Step 1: Go to  System-->Config-->Tags. From here, you can create a new tag in one of two ways: click on the menu button located on the left-hand side of the Model header and select New Tag, or alternatively right-click on the root folder in the Model panel and select New Tag. Either way will display a menu with the following options:
    • New Group: Allows a new folder or a template instance to be created.
    • New Tag: Allows a single tag to be created. Select this option.

Figure 1- Tag creation(1)Figure 1. Tag Creation

  • Step 2: Provide a name for the tag (in this example, Tag).

Figure 2- Tag createdFigure 2. Created Tag

  • Step 3: Now we will go over all the different properties that can be configured for Tags.

Main Parameters

Figure 3- Main ConfigurationFigure 3. Main configuration

  • Type: Configure the tag data type by clicking on the drop-down and selecting any of the following available options: 
    • Number
    • String
    • Boolean
  • Format: Select the format that will be applied to the tag in WebUI:
    • Default
    • Integer
    • Decimal Precision 1
    • Decimal Precision 2
    • Decimal Precision 3
    • String
    • Expression
      When configuring a tag, it's possible to assign virtually any visualization format by selecting <expression> from the Format dropdown menu. Within the expression field, it's necessary to specify the desired visualization format using the corresponding sprintf format.
This parameter does not change the internal format of the tag, only the way it is displayed in WebUI. Additionally, it is also stored as metadata in the tag configuration, which can be accessed from other modules such as Web Vision, Scripting, etc.
  • Deadband: A numerical value used to prevent unnecessary updates for Tags whose values change by small amounts. The suffix -u is used for absolute change in engineering units (e.g. 0.1u) whereas the suffix -% indicates percentage values (e.g. 1%).
  • Client access: Defines whether a Tag is read-only or writeable. Available options are as follows:
    • Read
    • Read & Write 
  • Persistency mode: This parameter specifies the behaviour whenever the source module, the whole service, or the system is restarted. Valid values are as follows:
    • None: Whenever the source module goes offline or at startup, the tag will take its default value and its quality will be equal to Bad-Uninitialized. 
    • Memory: The tag value and quality are maintained when its source module goes offline. However, in the event of a system restart, it will behave the same as with None
    • Disk: The tag's quality and value will be stored in the disk and will persist even in the event of a system restart.


Figure 4- Details configurationFigure 4. Details configuration


  • Details: This section includes some metadata information related to the tag. 
    • Description: Provides extra information about the tag.
    • Engineering units: The tag engineering units.
    • Default Value: Sets the default value that the tag will take after a system and/or module restart, in case it has not been configured with disk persistency.


Figure 5- Simulation configurationFigure 5. Simulation configuration

  • Simulation
    • Enabled: Enables or disables tag simulation. When Enabled, tag values are simulated instead of being provided by a source module. The simulated value corresponds to the time elapsed since midnight in milliseconds. Configuration of the rate of change for simulated values is done in the node configuration.

Assigned Views

Figure 6- Assigned Views Configuration(1)Figure 6. Assigned views configuration

  • Assigned Views: This section allows users to assign the tag to one or more Views. Views are used to restrict the information shared with other nodes through Link connections.
    • Name: Clicking on the drop-down menu button displays the available views, which need to have been previously created in the corresponding section of the Explorer panel.
  • Force Read-only: Regardless of whether the tag has been defined as writeable in the Client access section, tag access can be restricted to read-only through all views by enabling this setting. 


Figure 7- Scaling configurationFigure 7. Scaling configuration

  • Scaling: This section defines if and how the tag value will be scaled between the source and what is reported for that tag.
    • Enabled: Enables or disables the linear scaling of the tag.
    • Raw Range
      • Minimum: Start of the raw value range.
      • Maximum: End of the raw value range. 
    • Engineering Units Range
      • Minimum: Start of the scaled value range. 
      • Maximum: End of the scaled value range. 
    • Clamp Values
      • Minimum: If enabled, the values that fall below the start of the scaled value range will be adjusted to that value. 
      • Maximum: If enabled, the values that fall above the end of the scaled value range will be adjusted to that value. 

Below you can see a scaling example of a temperature sensor ranging from 0 to 100ºC with a maximum raw value equal to 32,767.

Figure 8- Probe scaling exampleFigure 8. Temperature sensor scaling example


Figure 9- Source Configuration(2)

Figure 9. Source Configuration


  • Source: Specifies how the tag determines its value.
    • Enabled: When set to No, the tag will behave like a memory tag. On the contrary, when Enabled, the source module will provide the tag's value, quality and timestamp.
    • Module Type:  Defines the type of the module used to obtain the tag's value, quality, and timestamp. If the desired module type were not available on the list displayed in the drop-down menu, it would mean that such functionality is not installed yet. 
    • Module Name: Enter the name of the moduleinstance that should have been previously created.
The configuration options of the Source section will largely depend on the selected Module Type. To find out more about this, please refer to the documentation of every particular module.


Figure 10- History Configuration(2)Figure 10. History Configuration 

  • History:
    • Enabled: Determines whether the Tag will report its history to the Tags Historian system.
    • Module name: Specifies the name of the historian module or modules, either local or remote, that will record the data. A comma-separated list of instances used must be entered. If a remote Historian instance is being used, the following pattern must be used NodeName/HistorianModule.
    • Config:
      • Mode:
        • Mode:
          • Change: Collects a record whenever the tag value changes. Only values that surpass the deadband will be stored. 
        • Deadband: The suffix -u is used for absolute change in engineering units (e.g. 0.1u) whereas the suffix -% indicates percentage values (e.g. 1%) over the current tag value.
      • Range Y: Configuration of the by-default values for the Y-axis limits in the chart.
        • Minimum: Default Y-axis minimum value in engineering units.
        • Maximum: Default Y-axis maximum value in engineering units. 
      • Chart: This allows you to configure the graph to be generated during the data history.
        • Interpolation: Defines the interpolation mode to be used to display the data in the chart. There are 2 available options:
          • Step: Value changes will be shown as discrete steps.
          • Linear: Value changes will be shown as a line.
        • Default method: Specifies the default aggregation method used for the tag in the chart:
          • First: Returns the first value in the aggregation period.
          • Last: Returns the last value in the aggregation period.
          • Minimum: Returns the minimum value in the aggregation period.
          • Maximum: Returns the maximum value in the aggregation period.
          • Average: Returns the average value in the aggregation period.
      • Rate: Normally Historian only stores records when values change. By default, an unlimited amount of time can pass between records and if the value doesn't change, a new row is never inserted into the database. By modifying these settings, it is possible to specify the maximum and minimum amount of time that can elapse between two samples. It's important to only change this property when necessary. 
        • Minimum: Minimum amount of time that must elapse before recording new data.
        • MaximumMaximum amount of time that can elapse without recording new data. 

Alarms & Events

Figure 11- Alarms & Events(1)Figure 11. Alarms & Events

  • Alarms & Events: This section is explained in detail in the following link, Alarms.

Was this article helpful?