AutomatedBuildings.com is pleased to welcome IOTech Systems as our newest sponsor. IOTech builds an open, vendor-neutral software platform for the edge of building networks, the layer where BACnet controllers, proprietary BMS front ends, and cloud analytics tools all have to agree on what the data means.
If you have wrestled with a multi-vendor portfolio where every building speaks a slightly different dialect, IOTech’s approach is worth knowing.
Who is IOTech?
IOTech’s software collects data from industrial devices and sensors, normalizes it into a consistent format, runs local analytics or AI inference on it in real time, and makes it available to whatever needs it next: a local control loop, a cloud platform, or a fault-detection model.
The platform is built on EdgeX Foundry, the Linux Foundation’s open-source edge data framework, and IOTech is a leading contributor to that project. That means the platform’s core is an open, community-developed standard rather than a single vendor’s proprietary format, which is exactly the kind of foundation a fragmented industry like building automation needs.
IOTech’s stated customers and partners include CBRE, Shell, Schneider Electric, Eaton, Danfoss, Johnson Controls, Verizon, Microsoft, Intel, and Accenture, alongside academic and utility deployments, a footprint well beyond building automation alone.
The Product Lineup
Edge Central is IOTech’s flagship open edge data platform. It handles device connectivity, data processing, alarm management, historian services, and cloud streaming in one modular package, with full edge management included. It runs on any hardware, OS, or processor, the practical meaning of vendor-neutral in a portfolio with mixed-vintage equipment.
Edge Connect is the leaner, real-time counterpart, built for time-critical and resource-constrained environments. Written in C for a small footprint and low latency, it is used as an embedded OT connectivity layer by industrial OEMs, supporting BACnet, Modbus, and OPC UA among others, and normalizing everything into a standard OPC UA data layer.
Edge Manager handles scale. Past a handful of buildings, someone has to provision, configure, monitor, and update every node and application across every site. Edge Manager does that from a single controller, on-premise or cloud, built for the resource and connectivity limits of edge devices rather than assuming Kubernetes-style infrastructure everywhere.
Why This Matters for Building Automation
IOTech’s building automation practice maps directly onto problems this audience knows well. High-performance BACnet discovery and polling with no per-point licensing limits removes a familiar cost and scaling constraint. Multi-protocol standardization addresses portfolios running several BMS vendors side by side with no shared language between them. IOTech also cites Honeywell ecosystem and major cloud integration, plus AI-based auto-tagging against Project Haystack conventions to speed up commissioning, usually one of the slowest parts of any integration project.
The company frames its value in three steps: connect data from any vendor into one source of truth, model it with semantic tagging so disparate equipment becomes AI-ready, and act on it with real-time local control while streaming normalized data upstream. It is a plain description of what most of this industry is already trying to build.
IOTech also points to a real deployment: a large global property company that unified BMS data across a multi-vendor portfolio, connecting every protocol and site without ripping out existing systems, reporting fewer breakdowns meaningfully through proactive diagnostics and faster, template-based rollout in place of custom integration at every building.
A Fitting Addition to This Community
AutomatedBuildings.com has spent decades covering the industry’s push toward genuine interoperability, so a sponsor whose core product is an open, standards-based edge layer aimed at that exact problem is a natural fit. We are glad to have IOTech Systems join us, and we encourage you to explore their platform directly.
===
