What is the Device Attribute in Fogwing IIoT?

Attributes are parameters or data points generated by the machine or device using sensors as recognized and classified. Fogwing data processing engine uses these attribute keys to identify the data parameter and execute various data processing steps such as filtering, enrichment, routing and formulas.

What are the Types of Attributes supported by Fogwing IIoT?

Fogwing IIoT Platform supports 3 types of data attributes for different purpose.

  • Device Attribute

  • System Attribute

  • Synthetic Attribute

What is Device Attributes?

Data points sent by the device through IoT Gateway or any other controller to the Fogwing IIoT Platform for processing and storage. These device generated attributes are raw attributes stored and processed based on configuration.

What is System Attributes?

Systems attributes or variables that are preconfigured within Fogwing IIoT Platform to validate and process certain device health conditions. Example: $battery, $lati, $lang. Any device that sent these system variables as device attributes, Fogwing IIoT engine consider those device attributes as system variable to act pre-defined conditions.

What is Synthetic Attributes?

Data points that are not generated by devices however used to enrich device data to arrive meaningful value. Synthetics attributes can be used to fill default value for certain attributes (ex: power) or execute formula to arrive results.

Why attributes are important in Fogwing IIoT?

Fogwing platform handles all data processing events such as Data Integrity check, Data Rules execution, Data Simulation, Formula Execution and Data Analytics based on the attribute declaration. In Industrial applications machines send many parameters in the payload to Fogwing.However if we want to monitor specific parameter only then we need to create attributes.

What fields are to create device attribute in Fogwing IIoT?

The following fields are required to create device attribute.

Field Name

Purpose

Attribute Key

Identifier used to find attributes in payload. Must be case sensitive.

Data Types

Field data types that are expected from devices. Ex: Number, String and Boolean

Default

Default value of the key if incase of any enrichment failure.

UoM

Unit of Measure for the given key value.

Attribute name

This can be a descriptive name and will also be displayed in Analytics charts.

Analytical?

If checked, This attribute will be available in Data Analytics Studio.

Synthetic?

If checked, This attribute will become available in Formula which is a feature of Data Enrichment.

Edit Attribute Page

Note: The fields which has a * marked are mandatory fields.

What attribute data types are supported by Fogwing IIoT ?

Fogwing supports the below data types as of release 2.11:

  • String

  • Number

  • Boolean

How to hand JSON Array in Fogwing IIoT?

This feature is introduced for adding data in array format in devices attributes. It will be used to map the array data if it is present in the JSON format payload. When the device wants to send multiple values, this feature comes in handy. This option can be turned on following the below steps:

  • Select the 'Edge Devices' option from the 'Device Network'.

  • Under 'Action' click the 'edit' option. This brings to 'Edit Edge Device' page.

  • Go to the 'Attribute' tab and edit any of the attributes.

  • In the 'Edit Attribute' screen click on the '+' sign below the 'Attribute Name'.

  • It brings the screen as below.

  • Click the 'Is array' option and enter the 'Array Key Name' and the 'Attribute Position'.

  • Go to the 'Edge Simulator' and add the 'Array Key Name' in the JSON payload.

  • Click on the Simulate button.

JSON Array processing using Fogwing IIoT

What's next?

Once you have finished exploring the Device attributes in Fogwing IIoT platform you may go ahead and explore the Data Storage feature in Fogwing IIoT Platform.

Link:

For any feedback and enquires on the functionalities of the Device attributes access, write to our support team at [email protected]

Did this answer your question?