BACnet, Modbus, MQTT: connect the portfolio without replacing everything
Useful collection starts by accepting protocols already in place. Octowise aggregates BACnet, Modbus, MQTT, OPC-UA, APIs, and Enedis in one repository.
Octowise Team
Managers inherit BMS platforms, communicating meters, supplier APIs, and historical spreadsheets. Replacing everything is neither fundable nor desirable. Octowise aggregates BACnet, Modbus, KNX, MQTT, OPC-UA, LoRaWAN, APIs, Enedis, databases, and Excel imports in one repository, and monitors each source’s health.
Accept what is already there
A high school does not have the same BMS as a headquarters; a district-heating network does not expose the same protocol as a Linky meter. A useful platform starts with connectors, not a controller-replacement project. Octowise’s architecture is protocol-agnostic: each protocol is a data source with its collection cycle and status.
New connectors can be added. What matters is that the building, equipment, and analyses do not need to know the underlying protocol.
- BMS and controllers: BACnet, Modbus, KNX, OPC-UA.
- IoT and messaging: MQTT, LoRaWAN.
- Meters and suppliers: Enedis, APIs.
- IT and history: databases, Excel imports.
One source, one cycle, one status
Collection is not a global on/off. Each source has its frequency, errors, and voluntary pauses. A source in BMS maintenance is not the same as a never-synced source or an expired API key.
That grain lets you assign the fix: the BMS integrator, the energy supplier, IT. Without per-source status, everyone sees “the building stopped reporting” and nobody acts.
Data continuity
A network outage or a planned BMS shutdown should not create an unexplained gap in the curves. Automatic recovery and availability history distinguish a one-off incident from connectivity drift.
That is a prerequisite for seasonal signatures: training a model on outage windows means learning silence as if it were zero consumption.
Expose afterwards, don’t copy
Once collected, data stays in Octowise and is exposed via API, OData, and MCP. You avoid the classic pattern: extract to a parallel data lake, then no longer know which system is the portfolio system of record.
The Protocols & sources page details the catalogue; the business point sits elsewhere: one repository to monitor, alert, declare, and invest.