Siemens vs Schneider vs Honeywell vs Johnson Controls BMS

Every BMS tender I am asked to review eventually produces the same question from the client side: which of the big four is best? It is the wrong question, but an understandable one, because those four names dominate the specification language of large commercial and institutional buildings. All four are serious engineering organisations with decades of controls heritage, all capable of running a complex building well, and all capable of leaving you with an unloved, half-commissioned system that operators route around. What separates the good outcome from the bad one is usually not the logo on the panel. It is who designed the points list, who commissioned the sequences, and who is contracted to look after it for fifteen years. This comparison takes each vendor seriously, gives each a real Considerations section, then explains why the local integrator and the maintenance contract matter more than the brand.

The message up front: all four vendors can deliver a competent building management system. The variance between two installations of the same brand, in the same city, is routinely larger than the variance between the four brands. So specify openness deliberately, evaluate the proposed integrator as hard as you evaluate the product, and treat the service agreement as part of the purchase rather than an afterthought. For the underlying concepts, start with the complete BMS guide and the BAS explainer.

A naming warning, please read it: product family names in building automation are re-branded more often than in almost any other category I work in. Platforms get renamed during reorganisations, sub-brands get folded into umbrella brands, and regional naming sometimes differs from global naming. Everything below describes how each family has been marketed and how it is generally positioned, not a guarantee of the current commercial name, module list or licence structure. Verify current naming, protocol support and lifecycle status with the vendor or their local office before writing it into a specification.

1. The shape of the market, and why BMS comparisons behave differently

Comparing BMS vendors is not like comparing CMMS or CAFM products. In building automation you buy a layered system: field devices and sensors at the bottom, programmable controllers in the middle, a supervisory and graphics layer above, and increasingly an analytics or cloud layer on top. Each layer can come from a different source. The controllers may carry the vendor badge while the valves, actuators, meters and drives come from a dozen other manufacturers, and the whole thing is assembled, programmed and commissioned by a contractor who may or may not be the vendor's own service branch. That has three consequences for any comparison exercise.

• The delivery channel is part of the product. The same vendor product line, installed by two different contractors, produces genuinely different buildings. One gives you clear graphics, documented sequences and a clean points list. The other gives you a system that alarms constantly and is left in manual override within a year.
• Openness is a specification outcome, not a brand attribute. All four vendors support open protocols. Whether your system ends up open depends on how the specification was written, which layers were left proprietary, and whether you insisted on receiving the source programming and licences. See BMS specification clauses for the language that does the work here.
• Lifecycle horizon is long. Controls hardware routinely stays in service fifteen to twenty-five years, well beyond the commercial life of the product generation. Obsolescence handling therefore matters more than the current feature list. All four have made buyers migrate, and all four will again.

2. Vendor marketing games to watch for

Before the individual sections, the claims that come up in nearly every BMS pitch and what to ask in response.

3. Siemens

Siemens approaches building automation the way it approaches industrial automation: as an engineering discipline with a strong emphasis on structured programming, documentation and standards conformance. Its building control portfolio has been marketed for many years under the Desigo name, covering field controllers and the supervisory layer, alongside a broader smart-buildings and digital-services positioning at the enterprise end. In the buildings I have seen, Siemens tends to be chosen by technically confident clients with in-house engineering capability, often in healthcare, pharmaceutical, laboratory, higher education and transport infrastructure, where documentation rigour and validation matter as much as day-to-day usability.

Strengths: strong standards and conformance culture, which shows up in clean BACnet implementations and disciplined controller engineering; deep HVAC sequence capability for complex plant, including the critical-environment cases (operating theatres, cleanrooms, containment labs) where pressure cascade and airflow control cannot be approximated; engineering documentation is generally among the better sets handed over in this category; credible fire, security and building control portfolio under one corporate roof, which helps when a single accountable party across life-safety and comfort systems is genuinely required; strong presence in Europe and the Middle East with established local engineering offices in most major markets.

Considerations: the engineering-led culture cuts both ways, and Siemens systems can feel heavier to configure and change than the lighter-touch alternatives, which discourages the small continuous improvements a building needs; operator graphics have historically been functional rather than pleasant, and while this has improved, I would still demand to see the actual delivered front end from a recent local project rather than the demonstration environment; the portfolio breadth means the commercial conversation can involve several Siemens business units with different pricing and support models, and buyers need to force clarity on exactly which entity owns the delivery and the warranty; engineering tooling and training are specialised, so the pool of local contractors genuinely competent on the current generation is often smaller than for the more channel-heavy vendors, which weakens your competitive position at service renewal; positioning at the small and medium building end is less convincing than at the complex-plant end.

Best suited for: complex and critical HVAC environments (hospitals, laboratories, pharmaceutical and semiconductor facilities); clients with in-house controls engineering capability who will use the depth; transport, utility and campus infrastructure with long asset horizons and formal documentation requirements; organisations that want fire, security and building control from a single accountable corporate group and have the governance to manage a multi-business-unit relationship.

4. Schneider Electric

Schneider Electric comes at buildings from the electrical distribution and energy management side, and that origin is visible in the product positioning. Its building and energy portfolio has been marketed under the EcoStruxure umbrella, with EcoStruxure Building as the building-automation branch, and the group has grown by acquisition over a long period, which means the portfolio contains several controls lineages rather than one. Schneider is also the strongest of the four on the electrical side of the building: metering, power quality, switchgear monitoring and energy reporting sit naturally in the same conversation as HVAC control, which is a real advantage when energy performance is the driving requirement.

Strengths: best natural fit where electrical distribution, metering and HVAC control need to be seen together, because the power side is core business rather than an add-on; genuinely strong energy and sustainability reporting positioning, which matters when the building has external reporting obligations; broad and mature channel of independent systems integrators in most markets, which gives buyers real competitive tension at both tender and renewal; comfortable across a wide building size range, from single mid-size commercial buildings up to multi-site portfolios; open-protocol positioning is generally well established, and the group has long-standing involvement with the open supervisory framework layer discussed below.

Considerations: the acquisition history is the central caveat, because the portfolio has carried more than one controls lineage and buyers must establish precisely which product line is being proposed, whether it is the strategic line going forward, and what the migration path is if it is not; the EcoStruxure umbrella covers a very wide range of offerings, and the name alone tells you almost nothing about which specific controllers, supervisory software and subscriptions are in scope, so insist on a component-level schedule rather than a brand-level proposal; because much delivery runs through independent integrators, quality varies more across the channel than with vendors who self-deliver more work, which makes integrator due diligence non-negotiable; some analytics and cloud capability sits behind separate subscriptions, and the total five-year cost can be materially different from the headline installation figure.

Best suited for: buildings where energy performance and electrical monitoring are first-order requirements rather than secondary; portfolios that want one commercial relationship across power distribution and building control; buyers who value a wide independent integrator channel and the price tension it creates; organisations with existing Schneider electrical infrastructure where the integration story is real rather than theoretical.

5. Honeywell

Honeywell has one of the longest controls heritages of the four and an unusually broad footprint, from residential thermostats through commercial HVAC controls to large building supervisory platforms and life-safety systems. Its building supervisory offerings have been marketed under several names over the years, and the group also owns Tridium, whose Niagara framework is the vendor-neutral integration layer covered in its own section below. That ownership gives Honeywell a distinctive position: it sells both branded building automation and the open framework that many of its competitors' integrators build on.

Strengths: enormous installed base and a very wide product range, so there is usually a Honeywell answer at every scale from a small retail unit to an airport; strong life-safety and fire heritage alongside building control, which is valuable where those systems must be coordinated; ownership of Tridium and the Niagara framework means an unusually credible open-integration story when it is deliberately specified that way; deep field device and sensor range, which simplifies sourcing and spares; very broad contractor and integrator population in most markets, which generally means competitive service pricing and easier contractor replacement.

Considerations: breadth is also the biggest weakness, because the portfolio contains multiple overlapping control lineages accumulated over decades and product naming has changed repeatedly, so establishing what is current and strategic takes real effort; upgrade paths between older and newer Honeywell generations have not always been graceful, and I have seen sites where the practical answer was replacement of the supervisory layer rather than migration; because so much is delivered through a large and varied channel, the quality distribution of Honeywell installations is wide, and a weak local branch or dealer will undo the product's strengths; the coexistence of branded Honeywell automation and vendor-neutral Niagara can make commercial conversations ambiguous, and buyers should ask directly which they are being sold and what the licensing implications are; some analytics and remote-service capability is subscription-based and site connectivity dependent.

Best suited for: large mixed estates that need a single supplier able to cover many building types and sizes; sites where fire and life safety coordination with building control is a design requirement; buyers who want an open Niagara-based supervisory approach from a large corporate supplier; existing Honeywell estates where field device and controller standardisation already has real operational value.

6. Johnson Controls

Johnson Controls is the most purely buildings-focused of the four. Its building automation platform has been marketed for many years under the Metasys name, and the wider group includes major HVAC equipment and fire and security brands, which means it can supply chillers, controls, fire detection and security under one corporate umbrella. In practice that equipment adjacency is the distinctive argument: when the chiller plant, the controls and the service contract come from the same group, the finger-pointing that normally follows a plant performance dispute has fewer places to go.

Strengths: strongest alignment between HVAC equipment and controls of the four, which genuinely reduces interface risk on chiller plant and central plant optimisation; Metasys has a long track record as a supervisory platform and a large trained operator population, so finding staff who already know the front end is easier than average; operator experience and graphics have generally been a relative strength, and the platform is usually rated approachable by facilities teams rather than only by engineers; extensive direct service organisation in many markets, so there is a well-defined route to accountable support; broad portfolio across fire, security and building control for buyers who want consolidated accountability.

Considerations: the strong direct-service model reduces competitive tension at renewal, and I have seen sites where the practical difficulty of moving service away from the original supplier became the dominant cost issue over a decade; equipment and controls bundling is convenient but tends to concentrate commercial dependency on one group, so price benchmarking needs deliberate effort; there have been generational transitions in the controller and supervisory lines over the platform's long life, and some older estates carry legacy segments with limited forward path, so an existing-site assessment must establish exactly which generation is installed before any upgrade budget is credible; some advanced features and integrations have historically depended on specific licence tiers, and buyers should map feature to licence line by line; open-protocol support is present and well established, but as with all four, what you actually receive depends on how hard the specification pushed on engineering tool access and programming handover.

Best suited for: buildings where central HVAC plant is the dominant technical risk and equipment plus controls alignment has real value; facilities teams who will operate the system themselves and need an approachable front end; organisations that prefer a single accountable direct-service relationship over a competitive integrator market; multi-system consolidation where fire, security and building control under one group is a governance requirement.

7. Tridium Niagara: the layer that changes the lock-in conversation

Any honest four-way BMS comparison has to introduce a fifth name. Tridium produces the Niagara framework, a vendor-neutral supervisory and integration platform that sits above field controllers and normalises devices from many manufacturers into one model with common graphics, scheduling, alarming and history. Tridium is owned by Honeywell, but Niagara is licensed widely, and a large population of independent integrators plus several vendors' own branded products build on it. That is exactly why the question "is this product Niagara-based?" belongs in every BMS tender. It matters to a buyer for three reasons.

• It decouples the supervisory layer from the controller brand. You can keep the Niagara head end and change controller vendor at the next refresh of a plant room, or run mixed-vendor controllers across a campus behind one consistent operator interface. That is the single most effective structural defence against supervisory-layer lock-in.
• It broadens the competitive field for service. A Niagara station can, in principle, be maintained by any competent Niagara integrator. In practice this depends on how the station was built, whether the engineering was documented, and whether licences and credentials were properly transferred, but the ceiling is far higher than with a closed platform.
• It is a well-understood integration target. When you later need building data in a CAFM, CMMS or analytics platform, a Niagara layer usually gives a cleaner, better-documented starting point than a proprietary head end. The BMS to CAFM integration reference architecture covers what that interface should look like.

8. The systems-integrator and channel question

This is the section a vendor-sponsored comparison would shorten, and it is the one that most affects outcomes. The party who designs the points list, writes the controller logic, builds the graphics, commissions the sequences and then services the system is usually not the vendor's corporate entity. It is a local branch, a franchised dealer, an authorised integrator, or an independent integrator on an open framework. Their competence determines whether the system you paid for exists in any meaningful sense. There are three delivery models across these four vendors, each with a different risk profile.

• Vendor direct delivery and service. Clear accountability and usually consistent engineering standards, but weak competitive tension at renewal and a genuine risk of price drift over a decade.
• Authorised dealer or franchised branch. Wider geographic coverage and more price competition, but quality depends heavily on the specific firm, and vendor accountability for a dealer's poor commissioning is often thinner than buyers assume.
• Independent integrator on an open framework. Best long-term flexibility and strongest renewal position, but it puts the whole quality burden on your selection process and your specification, because there is no corporate standards department behind the work.

The questions I would ask any proposed integrator, regardless of the badge on the proposal, are deliberately unglamorous:

1. Name the individual engineers who will program and commission this project, and give me their current certifications on the exact product generation being proposed. Not the firm's certifications, the individuals'.
2. Show me two comparable buildings you commissioned in this city in the last three years, and let me speak to the facilities manager at each without you present.
3. Show me a sample points list, a sample sequence of operation and a sample as-built graphics set from a completed project, so I can judge your documentation standard before I buy it. See points lists and field devices for what good looks like.
4. Which engineering software licences, tool versions, passwords and source programs will be handed to the building owner at practical completion, and in whose name are the licences registered?
5. If we replaced you in year four, what specifically would the next contractor be unable to do, and why?
6. Who answers the phone at 02:00 when the chiller plant trips, what is the contracted response time, and is that person in this country?

A vendor whose local integrator answers those six questions well is a better buy than a technically superior vendor whose integrator cannot. I apply that rule without hesitation.

9. Graphics, operator experience and analytics

Operator experience is where BMS evaluations most often go wrong, because the environment shown at tender stage is almost never what gets delivered. Vendor demonstration graphics are built by specialists with unlimited time on an idealised plant. Your graphics will be built by a project engineer under commercial pressure in the final weeks of a programme. That gap is the single most common reason a technically sound system ends up unused. What to evaluate instead of the demo:

• A delivered graphics set from a local project of comparable complexity. Ask how many clicks it takes to get from the home page to a specific AHU's supply air temperature setpoint. Three is acceptable. Six means operators will stop using it.
• Alarm design, not alarm capability. Every platform can raise alarms. Ask to see the alarm list from a live comparable site. If it runs to hundreds of standing alarms, the platform is not the problem but the delivery practice is, and you are about to buy that practice.
• Trend and history usability. Can an operator build a multi-point trend across two plant items without engineering-level access? If not, fault diagnosis will always require a contractor visit.
• Mobile and remote access reality. Ask what works on a phone in a plant room with poor signal, and what the cybersecurity posture of remote access is. The BMS cybersecurity guide covers the exposure that remote access introduces.

On analytics and energy capability, all four have credible offerings and all four market them heavily. The positioning differs: Schneider leans hardest on energy and electrical performance, Johnson Controls on central plant optimisation, Siemens on engineering rigour and critical environments, Honeywell on breadth plus the Niagara openness angle. But the analytics layer is rarely the binding constraint. Fault detection tools generate findings; findings only become savings when somebody is contractually obliged and able to act on them. I have seen more value from a good commissioning re-visit and a corrected schedule than from an analytics subscription nobody had time to read. The BMS energy optimisation and FDD guide sets out how to make that accountability explicit.

10. Lifecycle and obsolescence: the history that matters

Controls hardware outlives product generations. A controller installed today will plausibly still be running when its product line has been superseded twice, and the supervisory software will hit operating system and database dependency limits long before the field hardware wears out. Every one of these four has, over their long histories, ended sales and support for controller generations and required customers to migrate. That is the nature of a business with twenty-year field assets and five-year technology cycles. How gracefully each transition was handled varies more by product line and region than by vendor, so do not try to pick the vendor with the best obsolescence record. You cannot verify it reliably and it will not predict your own experience. Extract commitments you can act on instead:

• Ask for the published end-of-sale and end-of-support policy for the exact controller and supervisory versions proposed, in writing, with dates where they exist.
• Ask what the previous generation's migration looked like on a comparable local site: was it a firmware and software upgrade, a panel-level replacement, or a full rip-out? Ask to speak to that client.
• Establish which operating system and database versions the supervisory layer depends on, and who is responsible for patching them. This is frequently the first thing to become unsupportable.
• Require that the building owner holds the engineering licences and source programs, so a future migration can be competitively tendered.
• Budget for a supervisory-layer refresh at roughly the ten-year mark as a planned capital item, not a surprise. Treating it as planned is what keeps the estate from drifting into an unsupported state. The BMS maintenance and lifecycle guide covers how to structure that plan.

11. Four-way comparison

Deliberately qualitative. Any table that scored these vendors numerically would be inventing precision that does not exist, and the numbers would be out of date within a product cycle.

Read the last row as the most useful one. Each vendor's principal risk is structural rather than technical, and each is manageable if you know about it before you sign.

12. How to actually choose

The process I would run, in order:

1. Write the requirement before you look at any vendor. Building type, plant complexity, criticality, in-house operator capability, integration needs, reporting obligations, and the honest maintenance budget you will actually sustain. See how to evaluate BMS software and platforms.
2. Specify openness explicitly. Protocol requirements at each layer, engineering tool and licence ownership, source program handover, documentation deliverables, and a clause that lets another contractor take over. Language in BMS specification clauses.
3. Shortlist two or three vendors on fit, not reputation. Use the decision table below as the starting filter.
4. Evaluate the proposed integrator with equal weight to the product. The six questions in section eight. If the integrator fails, reject the bid regardless of the badge.
5. Price the fifteen-year service and lifecycle cost, not the installation. Include service agreement escalation, licence and subscription renewals, and a planned supervisory refresh.
6. Make commissioning and witnessed sequence testing a payment milestone. Retention released against demonstrated sequences, not against energisation. This one clause changes outcomes more than any vendor choice on this page. If you are running a formal process, the discipline in how to write an RFP transfers directly.

13. Where this framework does not help you

14. The idea to walk away with

The four vendors in this comparison are not interchangeable, and the differences described above are real. But they are second-order differences. The first-order variables in whether your building management system delivers are these: whether the points list matched the plant, whether the sequences were witnessed and proven before payment, whether the documentation and licences ended up in the owner's hands, whether there is a funded and capable person operating the system, and whether the service contract obliges somebody to respond and improve rather than merely to attend.

None of those five are determined by the vendor. All five are determined by your specification, your integrator selection and your maintenance contract. So if you must have a default position: choose the vendor whose best local integrator you trust most, insist on a Niagara-based or otherwise genuinely open supervisory layer with owner-held licences, and put half the energy you were going to spend on feature comparison into the commissioning and service clauses instead. That combination has produced better buildings, in my experience, than any amount of vendor scoring.

15. Final thoughts

Building automation is an unusual market because the product is genuinely good across all four major suppliers while the outcomes are genuinely inconsistent, and that gap is explained almost entirely by delivery practice. A well-specified, well-commissioned, well-documented and well-maintained system from any of these four will serve a building for twenty years. A poorly commissioned one from any of them will be in override by the second summer.

So use the comparison above to narrow the field honestly, then shift your attention. Interrogate the integrator. Own your licences. Witness your sequences. Fund your operator. The badge on the panel door will be the least consequential decision on the project, and recognising that early is the most valuable thing a buyer here can do.

Disclaimer: this article is general buyer-oriented analysis based on publicly available vendor positioning and practitioner experience at the time of writing. It is not a paid review. No vendor named here has had editorial input or a commercial relationship with this publication. Product family names, module structures, protocol support, licensing models and lifecycle status in building automation change frequently and vary by region. Verify all current naming and capability directly with each vendor, and conduct your own due diligence before any procurement decision.

Related reading: BMS complete guide, BAS explained, evaluating BMS platforms, points lists & field devices, specification clauses, maintenance & lifecycle, BMS cybersecurity, energy optimisation & FDD, BMS to CAFM integration.