How the integration works - Industrial IoT 5.0.1.1 | BACnet | Modbus | OPC Client | SNMP Manager

Industrial IoT Plugin Guide 5.0.1.1

Applies to
Industrial IoT 5.0.1.1 | BACnet | Modbus | OPC Client | SNMP Manager
Last updated
2023-02-09
Content type
Guides > Plugin and extension guides
Language
English
Product
Industrial IoT
Version
5.0

The Industrial IoT plugin adds to Security Center the ability to communicate with devices that support IoT protocols, such as BACnet, HTTP Server, Modbus Client, MQTT Client, OPC Client, SNMP Client, and TCP Server. With this plugin, you can monitor and collect information in Security Center from these IoT devices.

Architecture diagram for Industrial IoT integration

Architecture diagram for Industrial IoT integration

Components of Industrial IoT integration

Industrial IoT plugin role
With the Industrial IoT plugin, you can create the Industrial IoT role. Through this role, Security Center can communicate with IoT devices. The plugin role can raise events and trigger alarms when data changes occur on these devices.
Config Tool
The Industrial IoT plugin must be installed on a Config Tool workstation. The Security Center administrator uses Config Tool to create and configure the plugin role.
Security Desk
The Industrial IoT plugin must be installed on all Security Desk workstations. Security Desk operators can view state changes in real time on maps. Security Desk operators can view state changes in real time on maps.
BACnet devices
Devices that use the BACnet protocol to communicate with the plugin role. When requested by the plugin role, the BACnet devices reply with their current data and states.
Modbus devices
Devices that use the Modbus-TCP protocol to communicate with the plugin role. When requested by the plugin role, the Modbus devices reply with their current data and state of their coils, discrete inputs, input registers, and holding registers.
OPC UA server
The OPC UA server connects to one or more devices. The plugin role acts as an OPC UA client on behalf of Security Center. It can then communicate with the OPC UA server to receive data and state information from the OPC Server devices.
SNMP devices
Devices that contain object identifiers (OIDs) of data points. When the plugin role polls for the current value of SNMP Objects (OIDs), the device returns its latest value. SNMP devices can also be configured to send their SNMP traps to the plugin role. You can then create traps in the plugin role to trigger rules.
HTTP Server
The plugin role can receive data from devices through an HTTP server endpoint that listens for incoming data. The plugin role server hosts the HTTP server that devices connect to, and generates the API key required for authentication when posting data. Incoming data is posted in HTTP format to a URL that is generated when you add a device to the server. Requests to post data are made through a JSON document that references the data points of a device by their JSON path.

Supported HTTP devices inherit all the features of the Industrial IoT plugin.

MQTT Client
The plugin role receives data from devices by subscribing to topics on an MQTT broker. The data is received by specifying data points with JSON paths.
TCP Server
The plugin role receives data and events from devices connected to a TCP server run by the plugin role. The TCP server must be configured to identify data and events by evaluating the payload sent by these devices against regular expressions.