Smart Enterprise server communicates with automation control systems and IIoT via the network communication protocols. Its underlying Pharos Navigator platform supports generic solutions of connection to diverse devices avoiding specific proprietary requirements by the some manufacturers or protocols of controllers. As the result the platform meets the challenges of monitoring of both relatively small objects like buildings, offices, homes as well as large industrial systems.

The solution supports both direct communications with sensors and IoT devices as primary sources of measurements as well as with automation control systems depending on the needs. For example, there is a number of technical solutions able to read sensors by Rest API for temperature and other measurements. In this case, the platform can act as a single point of collection for all sensor readings, its processing and presentation to users for monitoring and visualization.

In case of industrial automation systems its installed sensors can be made by different manufacturers and support different protocols. In such systems the most commonly used automation solutions are the OPC servers or SCADA systems.

The Pharos Navigator platform supports communicating with sensors through open access protocols provided by these systems and their servers as well. When working with the systems positioned as the Internet of Things (IoT), its integration with Smart Enterprise server even easier. The server can access IoT devices based on support of open-source software frameworks AllJoyn and Iotivity providing access to sensor readings via Rest API.

Currently Smart Enterprise Monitor supports REST API, SOAP and SNMP. When there are the OPC XML-DA and OPC UA servers, industrial networks, the platform can work use these protocols as well.

In general the REST API is preferable since it is easy to use and is one of the most common protocols for the exchange of data via WEB. Many manufacturers of sensors, controllers and software use the protocol in various management systems, providing the possibility of access to monitoring functions through Rest API as well. For example, it can be used for control and measurements of light bulbs and street lights.

The SOAP protocol is most common in industrial systems. The use of SNMP protocol is recommended mostly for closed networks e.g. LANs due to the fact that has shortcomings in security.

The dotted block in the Picture refers to the systems which are not described here but allow access to monitoring functions via some network protocols. If the protocol is missing in the list it can be promptly implemented by the Pharos Navigator development team. Some new standards and relevant technologies which are under implementation such as IEEE 802.11ah wifi will be supported in next platform releases.

It should be taken into consideration that Pharos platform has the ability to import the stored sensor data from structured databases or files using its data import procedures.