A building rarely runs one vendor’s equipment. It runs whatever was installed over twenty years: BACnet controllers from one era, Modbus meters from another, a LonWorks legacy wing, and increasingly cloud and IoT systems that expect MQTT. Building automation integration is the work of making all of it one coherent system.
Protocols We Integrate
- BACnet — IP and MS/TP, with proper object mapping rather than raw point dumps.
- Modbus — TCP and RTU, with the register scaling and byte-order care that decides whether values are correct or merely plausible.
- LonWorks — legacy estates that still run critical plant.
- MQTT — edge, IoT and cloud-bound telemetry.
- SNMP and oBIX — network equipment and enterprise interoperability.
- Project Haystack tagging — so the data means something to software, not just to the person who mapped it.
Where Integrations Go Wrong
Almost never at the protocol level. They go wrong in the details: a Modbus register scaled incorrectly so a reading looks reasonable and is wrong, a naming convention nobody documented, points mapped without units, or a structure that made sense to the integrator and to nobody since.
We integrate to a convention, document it, and tag the data so analytics and any future AI layer can actually use it. The argument for that groundwork is set out in BACnet vs Modbus and Project Haystack and semantic tagging.
If the network itself is misbehaving — duplicate device IDs, broadcast storms, timeouts — our sister practice covers BACnet and OT network diagnostics.
Tell us what equipment needs to come together and we will scope the integration properly.
Related services
- Niagara Framework Development — Back to the full Niagara Framework development overview.
- Platforms — Protocols and platforms we integrate.