Device and Tag Metadata Use Case

17 min

When configuring DeviceHub devices and tags, you have the option of adding metadata, which allows you to define key-value pair data for the device output payload. The metadata can then be used to find, use, and reuse particular instances of data.

Some examples where using metadata would be beneficial include the following:

Device category metadata organizes devices.
Tag type metadata organizes tag categories.
Plant Floor ID metadata organizes different areas of a production site.
Location metadata organizes devices and plants across multiple worldwide sites.

Use Case

For this use case, you will use device and tag metadata to organize your data using the following parameters:

The country and city the device is located in. In a real-life scenario, you may be using multiple Belden Horizon Data Operations instances across different locations that are managed by Belden Horizon Data Manager.
The location (wing area) of the devices within each plant.
The category for each tag.

You will create four devices, with two tags each, totaling eight tags.

Step 1: Connect Devices

You will first connect all relevant devices in DeviceHub.

To connect devices:

Navigate to DeviceHub. The Devices pane opens.
Click the Connect a Device box. The Connect Device dialog box appears.
Connect a Device box
Click the Device Type drop-down list and select Simulator.
Click the Driver Name drop-down list, and select Generator.

Configure the following four devices.

Device 1

Name: PLC_1
Meta Data: Select checkbox.
Key/Value pair 1
- Key: Country
- Value: US
Key/Value pair 2
- Key: City
- Value: Chicago
Key/Value pair 3:
- Key: Device_Location
- Value: South_Wing
Enable Alias Topics: To view the topic with an alias name instead of in raw format, select this checkbox. For Belden Horizon Data Operations version 3.5.2 and later, it is selected by default. Learn more about Alias Topics.

Device 2

Name: PLC_2
Meta Data: Select checkbox.
Key/Value pair 1
- Key: Country
- Value: US
Key/Value pair 2
- Key: City
- Value: Chicago
Key/Value pair 3
- Key: Device_Location
- Value: East_Wing
Enable Alias Topics: To view the topic with an alias name instead of in raw format, select this checkbox. For Belden Horizon Data Operations version 3.5.2 and later, it is selected by default. Learn more about Alias Topics.

Device 3

Name: PLC_3
Meta Data: Select checkbox.
Key/Value pair 1
- Key: Country
- Value: US
Key/Value pair 2
- Key: City
- Value: Cleveland
Key/Value pair 3
- Key: Device_Location
- Value: North_Wing
Enable Alias Topics: To view the topic with an alias name instead of in raw format, select this checkbox. For Belden Horizon Data Operations version 3.5.2 and later, it is selected by default. Learn more about Alias Topics.

Device 4

Name: PLC_4
Meta Data: Select checkbox.
Key/Value pair 1
- Key: Country
- Value: Canada
Key/Value pair 2
- Key: City
- Value: Toronto
Key/Value pair 3
- Key: Device_Location
- Value: North_Wing
Enable Alias Topics: To view the topic with an alias name instead of in raw format, select this checkbox. For Belden Horizon Data Operations version 3.5.2 and later, it is selected by default. Learn more about Alias Topics.

Step 2: Add Tags

You can now add tags to the devices you created. For this use case, the tags will be used to capture air pressure and temperature values, and each device can have multiple tags for each measurement.

To add tags:

Navigate to DeviceHub > Tags.
From the Tags pane, click Add Tag, and then select Add Tag. The Add Tag dialog box appears.
The Add Tag icon
Click the Select a Device field, and then select the first device to add tags to.

Add the following eight tags.

PLC_1

Tag 1

Name: S - Random value generator
Value Type: int64
Polling Interval: Enter 5. This is the time interval in seconds that the tag will be polled for data.
Tag Name: Temperature_1
Meta Data: Select checkbox.
Key/Value pair
- Key: Category
- Value: Temp

Tag 2

Name: S - Random value generator
Value Type: int64
Polling Interval: Enter 5. This is the time interval in seconds that the tag will be polled for data.
Tag Name: Temperature_2
Meta Data: Select checkbox.
Key/Value pair
- Key: Category
- Value: Temp

PLC_2

Tag 1

Name: S - Random value generator
Value Type: int64
Polling Interval: Enter 5. This is the time interval in seconds that the tag will be polled for data.
Tag Name: Temperature_1
Meta Data: Select checkbox.
Key/Value pair
- Key: Category
- Value: Temp

Tag 2

Name: S - Random value generator
Value Type: int64
Polling Interval: Enter 5. This is the time interval in seconds that the tag will be polled for data.
Tag Name: Air_Pressure_1
Meta Data: Select checkbox.
Key/Value pair
- Key: Category
- Value: Pressure

PLC_3

Tag 1

Name: S - Random value generator
Value Type: int64
Polling Interval: Enter 5. This is the time interval in seconds that the tag will be polled for data.
Tag Name: Air_Pressure_1
Meta Data: Select checkbox.
Key/Value pair
- Key: Category
- Value: Pressure

Tag 2

Name: S - Random value generator
Value Type: int64
Polling Interval: Enter 5. This is the time interval in seconds that the tag will be polled for data.
Tag Name: Air_Pressure_2
Meta Data: Select checkbox.
Key/Value pair
- Key: Category
- Value: Pressure

PLC_4

Tag 1

Name: S - Random value generator
Value Type: int64
Polling Interval: Enter 5. This is the time interval in seconds that the tag will be polled for data.
Tag Name: Air_Pressure_1
Meta Data: Select checkbox.
Key/Value pair
- Key: Category
- Value: Pressure

Tag 2

Name: S - Random value generator
Value Type: int64
Polling Interval: Enter 5. This is the time interval in seconds that the tag will be polled for data.
Tag Name: Temperature_1
Meta Data: Select checkbox.
Key/Value pair
- Key: Category
- Value: Temp

Step 3: View Data

You can now view the data from the devices and tags in Belden Horizon Data Operations through the Flows Manager.

View Data in Flows Manager

Navigate to DeviceHub. The Devices pane opens.
For the PLC_1 device tile, open the menu and copy the device topic name. Store the topic name somewhere for use later. The ">" indicates a wildcard character, so the topic name applies to all tags for the device.
Device topic name
Copy and store the device topic names for all other devices.
Navigate to Flows Manager.
For a Flows Manager, click the Go To Flow Definition icon. The Flow canvas opens in a new browser tab.
Go To Flow Definition icon
On the Flow canvas, drag four DataHub Subscribe nodes and four debug nodes onto the canvas. Then, connect the nodes.
Flow canvas nodes
Double-click the first DataHub subscribe node. The Edit DataHub Subscribe node dialog box appears.
- In the Topic field, paste the wildcard topic name for the device copied in step 2.
- If needed, configure the Datahub Subscribe connection. See the Configure Connector Nodes section to learn more.
- In the Name field, enter PLC_1.
- Click Done.
Continue configuring the other three DataHub Subscribe nodes for the other devices.
Four DataHub Subscribe nodes configured
Click Deploy.
Expand the message window beneath the flow to view debug messages.
The message window
Click the Debug icon.
The Debug icon
Make sure the four debug nodes are activated.
Activate buttons
View the data in the debug window. The payload below shows data from each tag in each of the four devices. The device and tag metadata is included at the end of each payload item.

Payload from four devices

View Payload Data

Review the payload data from the debug window for each DeviceHub device.

{
  "success": true,
  "datatype": "int64",
  "timestamp": 1683901824688,
  "registerId": "7425F365-9D97-4B6C-BB01-DCCAFC04F383",
  "value": 1,
  "deviceID": "C9C3F3DF-954F-4233-834C-4B381741357C",
  "tagName": "Temperature_1",
  "deviceName": "PLC_1",
  "description": "",
  "metadata": {
    "Device_Location": "South_Wing",
    "City": "Chicago",
    "Country": "US",
    "Category": "Temp"
  }
}