Optimus Power requirements and integration points

Optimus Power ingests data in two ways

  • Pull model – data is getting pulled from the existing endpoint (HTTP API or database)
  • Push model – data is getting pushed by a service running on a BMS operator workstation or by a client

High-level integration provides flexibility in underlying BMS provider support as it is possible to actively integrate it with most of the existing ones on the market. Standard protocols like BACnet, KNX, Zigbee and LonWorks will be supported in the near future as the integration with BMS providers progresses.

Input data has to satisfy some minimal requirements listed below:

  • Indoor (air) temperature measurements collected at least hourly or more often
  • Energy consumed by heating/cooling appliances collected at least hourly
  • Static metadata about the building (square meters, number of rooms, number of HVAC appliances, solar orientation, etc.)

Optimus Power + BMS

The standard specification from BMS solutions like Cisco, Honeywell, Schneider Electric or Johnson Controls, provides the following definitions:

  • Stand-alone DDC controllers – DDC control system with one or many controllers not connected to each other
  • Network DDC systems – two or more DDC controllers that are connected by a communication network without a permanent operator
  • BMS – contains at least one permanent operator connected to multiple DDC controllers via the communication network
  • Direct digital control (DDC) controllers enable remote or automated control of a device or process. When DDC controllers are connected together they can share data and be controlled through a data bus. The protocol can be proprietary or open and most of the providers support one or many of the open protocols like BACnet, LonWorks, KNX and IP protocol for IoT enabled devices.