Adding parameter containers

Name

Enter a name for the container.

The name is used in the tool configuration process and in the file structure when storing the JSON files.

Identifier (ID)

Unique identifier of the container that is generated automatically by the software and used internally for further processing. This identifier forms part of the name of the target directory at the associated endpoint.

Container description

Add optional description text. The description text is displayed under the "Containers" tab.

Data collection

Container type

Select the container type.

For a parameter container, select the "Parameter" value. The relevant fields for the parameter container are then displayed in the dialog window.

Enable container: Data container is collecting data

Activate the recording of data by the container immediately after saving the container configuration.

Update strategy

Specify the update strategy of the container:

• Triggered
• Cyclic

Update interval

Specify the update interval for cyclic data acquisition. The update interval describes the time between two successive cycles. Each cycle consists of reading and transferring data and takes about 100 ms. For example, an update interval of 5 ms results in a cyclical output interval of approx. 105 ms.

The maximum value for the update interval is 31 days.

Device groups

Assigned device groups

Select the device groups for data acquisition. All groups created under the "Groups" tab are available here.

[+] button

Create a new group and assign it to this container.

Transmission

Transmit the data packages to endpoints.

Activate or deactivate data transmission from this container to the selected endpoints.

Collect and publish all parameters separately for each device

INFORMATION: Available in stand-alone operation only.

Activate the collection and sending of parameter data for each device as an individual data package. If the option is not activated, the software collects the parameters of all devices and sends them in one data package.

Endpoints for transmitting data packages

Select one or more of the configured endpoints as the storage location for the recorded data. All entries created in the "Endpoints" menu are available here.

Templates

Use container template

Activate inheriting the entire data model from container templates. After activation, the "Included container templates" edit box for selecting the container templates is displayed.

Included container templates

Select one or more container templates to inherit the entire data model configured in them. All templates created in the "Templates" menu and templates from installed libraries are available here.

Entered parameters (INFORMATION: To save data, avoid assigning a parameter to more than one container.)

[Filter entries] button

Filter the list of entered parameters

[+ Add one] button

Add one parameter for data acquisition.

[+ Add multiple] button

Add multiple parameters simultaneously for data acquisition.

Function in the [Import parameters from JSON file] submenu

Add parameters for data acquisition by importing a JSON file or a CSV file exported from Excel, for example.

See also Parameters.

Function in the [Export parameters to JSON file] submenu

Export the currently created parameter list for data acquisition as a JSON file.

See also Parameters.

Function in the [Import parameters from template] submenu

Import parameters for data acquisition from a container template. Changes in the container template are not automatically applied to the container.

Estimates of data transfer and volume

Estimation of the collected data volume at field level (OT network) and the transferred data volume (IT network)

Metadata

Extended information about the container. This metadata is transferred within the metadata section of the data event. The scope hash depicts the entire configuration of the container or the container template in a string. After changing the configuration, the scope hash must be updated by clicking [Calculate].