Metasys

Metasys is Johnson Controls building automation system, and the one product in this category whose technical documentation is genuinely open. The software tier is the Metasys Server family: the Application and Data Server (ADS), the Extended Application and Data Server (ADX), the lighter Open Application Server (OAS) and ADS-Lite, with the Metasys UI and the legacy Site Management Portal as clients and the System Configuration Tool (SCT) as the engineering tool. The hardware tier is the NAE, NAE85 and LCS85, SNE and SNC network engines plus field controllers. Release 14.0 is the current product bulletin, revised December 2024, with 13.0.50 and 12.0.50 branches also published.

The tier choice is the commercial decision and Johnson Controls publishes the numbers. ADS suits a single building: up to five concurrent users, up to fourteen network engines, Windows desktop or VM with SQL Server Express. ADX is the estate product: 10, 25, 50 or 100 concurrent users by licence, up to 1,000 network engines subject to server hardware, Windows Server with full SQL Server, and it is the only tier that gets Advanced Reporting, the Export Utility, a split web and database configuration and Metasys for Validated Environments. OAS is the lighter server that uniquely does direct BACnet device management, BACnet/IP and BACnet/SC natively and MS/TP through a router, to a maximum of 200 devices, in OASMIN and OASSTD variants.

Third-party integration is documented per protocol rather than claimed. Johnson Controls publishes commissioning application notes for Modbus, M-Bus, KNX and OPC UA client integration at both network-engine and server level, alongside BACnet/IP, BACnet/SC, LonWorks, legacy Johnson Controls N2 trunks, N1 migration, SA Bus and a generic integration object. That makes it unusual: a vendor-published KNX commissioning note and a vendor-published OPC UA client note at server level are rare in this market. Data egress is well served too, through a documented RESTful Metasys API that pulls raw historical and site data for tools such as Power BI and Tableau, plus a Monitoring and Commanding API for bidirectional third-party control. One constraint is stated outright: the API is available only on non-MVE sites, so the validated environment configuration and the BI integration configuration are mutually exclusive.

The honest counterweight is pervasive add-on licensing. Historical data archival, five years of history visible in the UI, FIPS 140-2 Level 1, ADFS two-factor authentication, BACnet/SC per server, Fault Detection and Triage, and MVE are each separately licensed. Several of those, history retention and transport security in particular, are things buyers assume are included. There is also a hard Windows and SQL Server dependency, which is licence cost, patching burden and an IT ownership question before any BMS value appears. The packaged energy application, Energy Essentials, is listed as discontinued from Release 12.0, although M-Bus and Modbus meter data acquisition remain. Finally, the 13.0.50 server comparison marks Site Management Portal as upgrade sites only against Metasys UI, so older sites face a front-end migration for operators.

Who it fits. Johnson Controls states the range itself: Metasys is highly scalable, serving everything from small office buildings to massive, multi-site campuses, and it names complex facilities such as data centres, hospitals and universities, along with operators facing strict compliance and reporting requirements. The vendor also claims it is trusted in more than 54,000 locations worldwide. In practice it suits mid-size to very large estates, especially brownfield Johnson Controls sites with legacy N2 trunks to absorb, and mixed-vendor plant where Modbus, M-Bus, KNX or OPC UA devices need documented integration paths. Regulated industries have a defined route through Metasys for Validated Environments on the ADX tier, with FIPS 140-2 Level 1 and ADFS two-factor authentication as options. Organisations that want BMS data in Power BI or Tableau get a documented API for it. And for any buyer who values diligence, the open versioned documentation portal is a real advantage: capacity tables, licence tiers and SKUs are all public.

Who it does not fit. Small buildings with no IT function, because of the Windows and SQL Server dependency, and buyers who need predictable total cost, because so many expected capabilities are add-on licences. Validated-environment sites cannot also use the REST API. Anyone wanting a cloud-hosted BMS should note that no Johnson Controls document read describes a hosted Metasys offering, only VM hosting, which permits self-managed infrastructure as a service.

Typical use. Campus and multi-building estates delivered by a Johnson Controls branch or an authorised controls contractor, with SCT as the engineering tool, an ADX server tier sized by concurrent users, and historisation into SQL Server. Budget the add-ons at quote stage, especially historical data retention and BACnet/SC.