The Inferrix IoT platform provides an ‘Integrated Single Console’ to ‘Monitor & Control’ all the disparate asset classes in your environment. The Inferrix IoT platform is protocol agnostic and has been designed to co-relate across asset classes and take automated decisions as per business rules relevant to the situation.
Silo’ed management has been inhibiting enterprises from maximizing the potential to optimize operations costs and deliver better customer service.
There are a wide gamut of business applications that we address with the Inferrix IoT Platform, ranging from simple Sensor based monitoring to Complex control of machines / business process and integration with 3rd party applications.
Data Source is source from which to collect the information and Data points are the parameters in the data source. This module basically collects the status, health and performance information from the device hosting a data source. In this module, the user can set threshold for the different points based on which we can generate events.
Multiple protocols can receive data from any device for which there is a protocol driver. Currently supported protocols include - a. BACnet I/P & MS/TP b. Modbus (ASCII, RTU, TCP, and UDP) c. MBUS d. SNMP and SNMP Traps e. SQL f. HTTP (Receiver, Retriever and Image) g. Meta Points h. Inferrix Sensors (Wirepas) i. Inferrix Server Agents (Server Monitoring like Window, Linux, Solaris) j. ASCII File and Serial
Event manager is responsible for raising an event or alarm, for the Data points being monitored, as well as for System or Audit related aspects. The alarms or event can be in one of the following states, which can be defined by the user or the system defaults can be used- a. Information b. Warning c. Urgent d. Critical e. Emergency It also has sub-module called Compound Event Generator to correlate between the different events to generate a new event.
It is used to publish data to any other instance of Inferrix, especially in a distributed (hub-spoke) architecture to form a Manager of Managers. It has following two methods of publishing - a. HTTP/HTTPS b. TCP Persistent
Used to put a particular device or data source into the maintenance mode for specified time period, so that we do not generate any false positive alerts for the device that might be under the maintenance.
A drag and drop graphical presentation of the environment being monitored by Inferrix.
This helps users define standard configurations for collection of datapoints, especially in term of their Database logging properties, text renders, purging properties or thresholding, which then can be applied to multiple data points of similar kind.
Meta points allow for powerful combinations of point values as well as historical point information to correlate information across asset classes.
Users can make custom scripts/rules on the data points value to control or set data points and data sources.
User permissions are defined by system administrators, and all communications with the IoT platform is secured with 256 bit SSL (Secure Socket Layer), ensuring the privacy of information.
Any events that occur, either system or user defined, can be handled arbitrarily using user-defined event handlers. These handlers can send emails / SMS notifications to defined mailing/user lists.
Inferrix IoT Platform supports restAPI with token-based authentication. We have exposed services/endpoint, which can be used by third party applications to access the data collected by the Inferrix IoT platform. The RestAPI is available on both the gateway and the IoT platform. The API has been extensively documented for the users to understand and 3rd parties can get an access to the sample outputs for testing purpose.
Changes to all information processing objects cause audit events to be raised, including new objects, changes, and deletions. These events pass through the event management system so that all users can independently acknowledge the event.