Glossary for Industrial IoT - Industrial IoT 5.0.2.0 | BACnet | Modbus | OPC Client | SNMP Manager

Industrial IoT Plugin Guide 5.0.2.0

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

add-on

An add-on is a software package that adds tasks, tools, or specific configuration settings to Security Center systems.

alarm

An alarm entity describes a particular type of trouble situation that requires immediate attention and how it can be handled in Security Center. For example, an alarm can indicate which entities (usually cameras and doors) best describe the situation, who must be notified, how it must be displayed to the user, and so on.

BACnet

BACnet is a communication protocol used for building automation and control (BAC). Using the Industrial IoT plugin, you can integrate your network of BACnet devices and sensors into Security Center.

BACstac

BACstac (BACnet protocol stack) is a Windows service installed by the Industrial IoT plugin for the BACnet protocol. This service is required for the plugin to communicate with BACnet devices.

data point

A data point is a specific type of information, which can be a number, a string, or a Boolean, that has a specific value at a specific time. The Industrial IoT plugin role reads this information from a device if it uses a client protocol, or receives this information from a device if it uses a server protocol. Examples of data points include the temperature read by a thermometer, the ON or OFF position of a light switch, and the speed of a fan.

device (Industrial IoT)

In the context of Industrial IoT, a device refers to a piece of electronic equipment that can communicate with the Industrial IoT plugin role using one of the supported IoT protocols.

entity (Industrial IoT)

In the context of Industrial IoT, an entity is a virtual device used to represents a set of data points that can belong to a single or multiple devices. From a configuration perspective, you can do with entities everything you can do with devices. The only difference between devices and entities is that a device is tied to one protocol while an entity is not.

event

In the context of Security Center, an event indicates the occurrence of an activity or incident, such as access denied to a cardholder or motion detected on a camera. Events are automatically logged in Security Center. Every event has an entity as its main focus, called the event source.

event-to-action

An event-to-action links an action to an event. For example, you can configure Security Center to trigger an alarm when a door is forced open.

expansion server

An expansion server is any server machine in a Security Center system that does not host the Directory role. The purpose of the expansion server is to add to the processing power of the system.

Federation™

The Federation™ feature joins multiple, independent Genetec™ IP security systems into a single virtual system. With this feature, users on the central Security Center system can view and control entities that belong to remote systems.

Genetec Mission Control™

Genetec Mission Control™ is a collaborative decision management system that provides organizations with new levels of situational intelligence, visualization, and complete incident management capabilities. It allows security personnel to make the right decision when faced with routine tasks or unanticipated situations by ensuring a timely flow of information. To learn more about Genetec Mission Control™, refer to the Genetec™ resource center.

Industrial IoT

Industrial IoT is a building automation and control plugin. With this plugin, you can use Security Center to monitor and control devices that support one of the following IoT protocols: BACnet, HTTP Server, Modbus Client, MQTT Client, OPC Client, SNMP Client, and TCP Server.

Industrial IoT health history

The Industrial IoT health history task is an investigation task that reports on health events related to the plugin, the message queue, the protocols, and the managed devices.

Industrial IoT input activities

The Industrial IoT input activities task is an investigation task that reports on the state changes of the inputs associated to the device data points configured in the system.

Industrial IoT rule activities

The Industrial IoT rule activities task is an investigation task that reports on the execution of the Industrial IoT rules, when they were triggered, why they were triggered, and the result of their execution.

Maps

The Maps task is an operation task that heightens your situational awareness by providing the context of a map to your security monitoring and control activities.

Modbus

Modbus is a communication protocol used by electronic devices to transmit data to a computer for building automation and control. Using the Industrial IoT plugin, you can turn Security Center into a Modbus client application.

plugin

A plugin (in lowercase) is a software component that adds a specific feature to an existing program. Depending on the context, plugin can refer either to the software component itself or to the software package used to install the software component.

Plugin

Plugin (with an uppercase, in singular) is the role template that serves to create specific plugin roles.

plugin role

A plugin role adds optional features to Security Center. A plugin role is created by using the Plugin role template. By default, it is represented by an orange puzzle piece in the Roles view of the System task. Before you can create a plugin role, the software package specific to that role must be installed on your system.

Plugins

The Plugins task is an administration task that you can use to configure plugin-specific roles and related entities.

RabbitMQ

RabbitMQ is a message broker software that transmits data from external devices and systems to Security Center. The following Genetec™ software install and use RabbitMQ: Genetec Mission Control™, Sipelia™, Restricted Security Area Surveillance, and Industrial IoT.

role

A role is a software component that performs a specific job within Security Center. To execute a role, you must assign one or more servers to host it.

Service Release

A Service Release (SR) is a standalone release that includes minor functionality improvements, bug fixes, and the integration of new hardware, intrusion devices, and plugins.

Service Release (SR)

Acronym: SR

SNMP traps

SNMP traps are event messages sent by the SNMP device to the Industrial IoT plugin role.

unit

A unit is a hardware device that communicates over an IP network that can be directly controlled by a Security Center role. We distinguish four types of units in Security Center:
  • Access control units, managed by the Access Manager role
  • Video units, managed by the Archiver role
  • ALPR units, managed by the ALPR Manager role
  • Intrusion detection units, managed by the Intrusion Manager role