A Practical Map of the BMS Software Landscape

At the bottom are controllers doing the immediate work. Above them is software for engineering and supervising the system. Above that, increasingly, are analytics and operations platforms trying to make the data useful across a building or portfolio.

The layers overlap, and most suppliers now cover more than one. But they are not interchangeable. A fault-detection platform is not a replacement for a controller. A polished portfolio dashboard does not remove the need for a well-engineered BMS. An open supervisor does not automatically make every device beneath it easy to replace.

That distinction is a useful place to start.

Layer one: control that has to keep working

The controller layer runs pumps, valves, fans, boilers, heat pumps, air-handling units and room systems. It reads sensors, applies sequences and sends outputs. This is where Trend, Delta, Schneider Electric, Honeywell, Johnson Controls and many other established controls manufacturers have built deep product ecosystems.

The important feature of this layer is not its dashboard. It is that the building still needs to operate when a browser is closed or a cloud service is unavailable. Fast loops, interlocks and fallback states belong close to the plant.

Different ecosystems have different strengths: controller ranges, engineering tools, approved partner networks, application libraries and long-term support. A fair comparison needs to consider the whole lifecycle, not just whether two controllers both speak BACnet.

Layer two: supervision and integration

The supervisor is the place where an operator usually sees graphics, alarms, trends, schedules and device networks.

Tridium describes Niagara as software infrastructure for connecting operational data across devices and systems. It is widely used as a multi-vendor integration layer, with a control engine, histories, schedules, alarms and presentation tools. The fact that Trend IQVISION is built on Niagara 4 shows why the market cannot be divided neatly into independent brands.

Other vendors provide their own integrated supervisor environments. Delta enteliWEB combines facility management, engineering, dashboards and energy functions. Schneider Electric's EcoStruxure Building Operation integrates its control range with third-party systems and standard protocols. Johnson Controls Metasys brings HVAC, lighting, security and fire systems into one platform. Honeywell's portfolio spans building controls, Niagara and cloud services such as Remote Building Manager.

These systems are sometimes dismissed as legacy software. That is too simple. They contain decades of hard-won controls capability and can be entirely appropriate for the job. The more useful question is whether the delivered system is understandable, supportable and open enough for the owner's future needs.

Layer three: analytics and building operations

A newer group of products generally sits above, rather than instead of, the BMS.

Clockworks Analytics focuses on fault detection and diagnostics: analysing existing building data, identifying high-impact issues and giving the operator a likely cause and recommended action. KODE OS presents a broader building operating layer, connecting BMS, IoT and business systems across portfolios. Facilio combines connected-building data with CMMS and facilities workflows, linking assets, maintenance, vendors and work orders.

These products address a real limitation of many head-ends: a BMS can expose thousands of values without helping a small operations team decide what deserves attention first. The trade-off is that an analytics layer is only as good as its connectivity, point mapping, equipment model and operational follow-through.

An impressive fault list that no one owns is still an impressive fault list.

There is no useful universal ranking

A hospital, a school, a residential development and a multi-site retail estate need different things. The strongest buying questions cut across brands:

What continues to run locally if the supervisor, internet connection or cloud platform fails? Who can edit the control logic, and what tools, licences and training do they need? Can the owner export trends, alarms, asset data and configuration in usable formats? How are third-party devices integrated, and which functions are lost at that boundary? Does the system explain equipment behaviour, or mainly display points and alarms? How does an identified issue become assigned work, a recorded intervention and a verified result? What will an upgrade, change of maintainer or addition of another building involve?

The answers matter more than the number of logos on an integration slide.

Where Automatry fits

Automatry works across several of these environments as a controls contractor. That means designing, programming and commissioning established BMS platforms as well as building software around them.

Automatry Edge sits in the operations layer. It connects to the existing BMS, structures live building data and helps engineers and operators investigate what is happening. It complements the underlying control system and extends the value of working controllers.

That is our view of where the market is heading: strong local control, better access to the data it produces, and software that helps people close the gap between an alarm and a useful action.