EcoStruxure Building Operation versus Johnson Controls Metasys

Protocols

Metasys documents third-party integration at both server and network-engine level, with named vendor application notes: Modbus via LIT-12013150, KNX via LIT-12013148, OPC UA client via LIT-12013545 and M-Bus metering via LIT-12013149, alongside BACnet/IP, BACnet/SC and LonWorks. OAS does direct BACnet device management over BACnet/IP and BACnet/SC with MS/TP via a router, up to 200 devices. Schneider names BACnet, LonWorks, Modbus, web services and MQTT on its own page, which is the broader headline list and the only one in this pair naming MQTT. The inverse gaps: MQTT is not named in any Johnson Controls document opened, and KNX and OPC are not named on any Schneider page that could be opened. Both are unverified, not absent.

Published scale

• Metasys publishes portfolio-scale headroom in numbers: ADX supports up to 1,000 network engines and 100 concurrent users with a split web and database configuration, and ADS up to 14 engines. Server tier is chosen by concurrent-user count against published SKUs.
• Schneider publishes no point counts, server-tier limits or concurrent-user ceilings on any reachable page. Portfolio capability is stated qualitatively as dashboards from device to portfolio level.
• Point counts as distinct from engine and user counts are not published by Johnson Controls either, so neither vendor gives you a point ceiling.

Licensing posture and hidden cost

This is where Metasys transparency cuts against it. Published documentation makes visible how much is an add-on: historical data archival, five years of history in the UI, FIPS 140-2 Level 1, ADFS two-factor authentication, BACnet/SC, Fault Detection and Triage and MVE are each licensed separately. There is also a hard constraint worth knowing early, because it is a genuine architectural fork: the RESTful Metasys API is available only on non-MVE sites, so a validated regulated environment and a BI integration configuration are mutually exclusive. Metasys also carries a hard Windows and SQL Server dependency across all server tiers, which is licence cost and patching burden before any BMS value appears. Schneider publishes no licence structure at all, so the equivalent add-on list may exist and simply be invisible. Both are specified, supplied and commissioned through integrators, and the software is a line item inside an engineering-dominated project cost.

Scope and security

Schneider reaches further beyond HVAC on published evidence, into power, microgrids, renewables, EV charging and metered energy, with Brick Schema semantic tagging, and states the most specific cybersecurity posture in the category: secure development lifecycle, BACnet SC certificate management, installation-free secure web clients. Metasys security is concrete but mostly chargeable, namely FIPS 140-2 Level 1 and ADFS two-factor authentication as add-on licences and BACnet/SC licensed per server. See BMS cybersecurity for connected buildings.