Comparison · Structured data · Sourced
Honeywell EBI versus Johnson Controls Metasys
These two are not the same kind of product, and the difference matters more than any feature list. Honeywell Enterprise Buildings Integrator is a multi-discipline head-end: HVAC, fire and life safety including smoke control and public address, security, video and energy run as EBI Manager modules rather than bridged systems, on a fault-tolerant distributed architecture of independent nodes. Metasys is a building automation suite: tiered server software, ADS, ADX and OAS, over NAE, SNE and SNC network engines, with Release 14.0 current. EBI enumerates no controller line of its own; Metasys sells the controllers and the servers together.
This comparison is strongly limited by available evidence on the Honeywell side. Honeywell publishes no EBI datasheet, specification sheet or documentation portal, the buildings site is regionally gated, several canonical EBI URLs return 404, and the R500 BACnet PICS fetched without an extractable text layer. Metasys publishes open, versioned, deep-linkable documentation with server capacities and licence tiers. So almost every direct comparison below has one verified side and one unverified side. Read it alongside the narrative overview at Siemens vs Schneider vs Honeywell vs Johnson Controls.
Last reviewed 7 November 2026
The products
Honeywell Enterprise Buildings Integrator (EBI)
Honeywell
Honeywell multi-discipline building head-end that runs HVAC, fire and life safety, security, video and energy from one operator platform. Current release R610. Quote only, delivered through Honeywell and its partners.
Full profileMetasys
Johnson Controls
Johnson Controls building automation system built from tiered server software (ADS, ADX, OAS) over NAE, SNE and SNC network engines. Release 14.0 is current and the technical documentation is fully public.
Full profileThe main differences
Integration beyond HVAC
This is the clearest real difference. EBI treats fire and life safety, security, video and energy as native platform modules, which is a genuinely different design from integrating them as third-party systems. If your project needs smoke control and public address on the same operator platform as HVAC and access, that is what EBI is for. Metasys published scope is building automation plus Fault Detection and Triage as a licensed server feature; nothing opened positions it as a fire and life-safety platform. On cross-discipline work also see BMS integration with fire, access control and CCTV.
Protocols, verified against unverified
- Metasys: BACnet/IP, BACnet/SC and LonWorks, plus vendor application notes for Modbus, KNX, M-Bus and OPC UA client. MQTT is not named in any document opened, so unverified.
- EBI: BACnet confirmed, with BACnet Secure Connect and KBOB BACnet compliance added in R610, and OPC confirmed with OPC UA history in R610. Modbus, KNX, MQTT and SNMP are not named on any page that resolved, so they could not be verified from published sources.
- Writing that EBI lacks Modbus would be wrong. The correct statement is that Honeywell publishes nothing on it, so it must be confirmed in writing.
Scale and edge controller management
Metasys gives numbers: ADX up to 1,000 network engines and 100 concurrent users with a split web and database configuration, ADS up to 14 engines, OAS BACnet device management up to 200 devices, and each engine family has a vendor commissioning guide. EBI gives architecture instead of numbers: independent nodes that share information so a campus does not depend on one server, single building through campus to global operations, building-to-building over web services. No EBI capacity figure of any kind could be found. For edge controller lifecycle work, Metasys is the documented option here; EBI is the head-end above someone else controllers.
Security and licensing posture
EBI states built-in cybersecurity monitoring and updates, a Policy Enforcer, a Software Update Service and Windows OS compliance, and R610 adds BACnet Secure Connect and OPC UA history. Metasys security is itemised but chargeable: FIPS 140-2 Level 1 and ADFS two-factor authentication are add-on licences and BACnet/SC is licensed per server. Metasys add-on licensing is pervasive and includes historical archival and five years of UI history, and the RESTful API is unavailable on MVE sites. Neither vendor publishes a price. Honeywell names subscription and hosted licensing options and routes to a sales form; Johnson Controls publishes the SKU and tier structure without figures. Both are integrator-delivered.
Side by side
| Attribute | Honeywell Enterprise Buildings Integrator (EBI) | Metasys |
|---|---|---|
| Vendor | Honeywell | Johnson Controls |
| Primary use | BMS supervisory software | Building automation suite |
| Deployment | Cloud, On-premises | On-premises |
| Organisation size | Enterprise | Medium, Enterprise |
| Licensing model | Commercial | Commercial |
| Free version | No | No |
| Trial | Not verified | Not verified |
| Published price | Contact vendor for pricing | Contact vendor for pricing |
| Product status | Active | Active |
| Capabilities | ||
| Third-party system integration | Yes Stated to work with a wide range of third-party equipment and software. source | Yes RESTful Metasys API plus a Monitoring and Commanding API for bidirectional integration. The API is available only on non-MVE sites. source |
| Multi-building and enterprise scale | Yes Single building, campus or global operations; building to building over Web Services. source | Yes ADX supports up to 1,000 network engines, 100 concurrent users and a split web and database configuration. source |
| Edge controller management | Not verified EBI is the head-end; no controller or edge product line is enumerated under it. | Yes NAE, NAE85 and LCS85, SNE and SNC network engines, each with a vendor commissioning guide. ADS up to 14 engines, ADX up to 1,000. source |
| Remote and browser access | Yes HTML5 browser, EasyMobile smartphone and tablet clients plus cloud connectivity. source | Yes Metasys UI browser client on every server tier, plus Remote Notifications. source |
| Cybersecurity features | Yes Built-in cybersecurity monitoring and updates, Policy Enforcer, Software Update Service, Windows OS compliance. source | Yes FIPS 140-2 Level 1 and ADFS two-factor authentication, both add-on licences; BACnet/SC licensed per server; secure user access and authorisation. source |
| Historical data and archiving | Yes Narrow basis: OPC UA history in R610. No long-term archive feature stated. source | Yes Manual, scheduled or automatic archival, but requires the Historical Data add-on licence, and five years of history in the UI is a further separate licence. source |
| Dashboards and graphics | Yes Healthy Buildings dashboards, risk alarms page and floor plan views. source | Yes Dashboards and widgets listed as a feature topic, with dynamic user graphics. source |
| Energy metering | Yes Energy Manager module, Attune Advisory Services and Automated Demand Response Gateway. source | Yes Meter data acquisition via M-Bus application note LIT-12013149 and Modbus. Note that the packaged Energy Essentials application is listed as discontinued from Release 12.0. source |
| Trending and logging | Yes The BACnet Testing Laboratories listing for EBI R600, tested February 2020, certifies the Trending BIBBs T-VMT-A, T-ATR-A, T-VMMV-A, T-AMVR-A, T-V-A, T-AVM-A and T-A-A, plus Scheduling BIBBs. Certifier-published and for R600 rather than the current R610, and the scope is BACnet trending specifically. source | Yes Long-term trend data storage for performance analysis. source |
| Alarm management | Yes Alarm Management named as a platform feature with automated workflow routing. source | Yes Event messages routed to operators for fault diagnosis with an audit trail; Remote Notifications feature. source |
| HVAC control | Yes Building Manager module covers building and energy management. source | Yes Network engines are the supervisory controllers for HVAC field devices; Fault Detection and Triage is a licensed server feature. source |
| MQTT support | Not verified MQTT is not named on any Honeywell EBI page that resolved. | Not verified No Johnson Controls document opened names MQTT. |
| OPC UA support | Yes OPC listed among supported open systems; OPC UA history added in R610. source | Yes Vendor application note LIT-12013545, OPC UA Client vendor integration. Client role specifically. source |
| KNX support | Not verified KNX is not named on any Honeywell EBI page that resolved. | Yes Vendor application note LIT-12013148 for KNX vendor integration. source |
| Modbus support | Not verified Modbus is not named on any Honeywell EBI page that resolved. | Yes Vendor application note LIT-12013150, Network Engine and Server Commissioning for Modbus Vendor Integration. source |
| BACnet support | Yes BACnet AWS listed among supported open systems; R610 adds BACnet Secure Connect and KBOB BACnet compliance. source | Yes OAS does direct BACnet device management over BACnet/IP and BACnet/SC, MS/TP via router, max 200 devices. BACnet/SC is a per-server licence. source |
| Last reviewed | 7 November 2026 | 7 November 2026 |
| Profile | View profile | View profile |
Not verified means the capability has not been checked for that product. It does not mean the product lacks it. Blank cells and unverified rows are never counted as a "no".
Strengths and limitations
Drawn from each product's own profile, where every item is labelled a verified fact or an editorial judgement.
Honeywell Enterprise Buildings Integrator (EBI)
Read the full assessmentMetasys
Read the full assessmentWhich to choose
Choose EBI when the requirement is one operator platform across fire, life safety, security, video, energy and HVAC, and when a distributed node architecture that survives a server loss is worth more than published numbers. Accept that you are buying on trust and on a written specification you negotiate, because the public evidence base is thin to the point of being unusable for scoring.
Choose Metasys when the estate is HVAC-led and multi-site, when you want to size and licence against published engine and user ceilings, and when your IT organisation can own Windows and SQL Server. Then budget deliberately for the add-ons, because historical archival, FIPS, two-factor authentication, BACnet/SC and fault detection are each separately licensed, and settle the MVE versus REST API fork during design rather than after.
Neither should be evaluated on vendor material alone. Both are quote only and the software licence is a small part of a cost dominated by engineering, controllers and field devices.
Frequently asked questions
No. The Honeywell side is thin. Honeywell publishes no EBI datasheet or documentation portal, the buildings site is regionally gated with 404s on canonical URLs, and no capacity figure could be found. The Metasys side rests on open, versioned vendor documentation.
EBI, on published evidence. Fire and life safety including smoke control and public address, security and video are EBI Manager modules on the platform itself. Nothing opened positions Metasys as a fire and life-safety platform.
Metasys is the only one with published figures: ADX up to 1,000 network engines and 100 concurrent users. EBI claims campus and global operations with a distributed node architecture but publishes no capacity numbers at all, so the two cannot be compared numerically.
EBI pages state cloud connectivity and hosted licensing options. For Metasys, no cloud-hosted offering could be confirmed from the documentation opened, so treat it as on premises unless Johnson Controls confirms otherwise.
Related comparisons
- Automated Logic WebCTRL versus Johnson Controls Metasys
- Schneider EcoStruxure Building Operation versus Johnson Controls Metasys
- Honeywell EBI versus Siemens Desigo CC
Sources and review basis
Attribute values come from each product's structured profile rather than being written into this page, so a correction made once appears everywhere. This comparison was last reviewed on 7 November 2026. Assessment of this category is documentation-based, not hands-on testing of every product.
- Enterprise Buildings Integrator (EBI), UK page accessed 7 November 2026
- Metasys ADS and ADX Product Bulletin, Features and Benefits accessed 7 November 2026
Disclosure
Alongside advisory work I also build a CMMS and CAFM platform, so I have a commercial interest in enterprise software generally. No vendor here has paid for inclusion, placement or wording, and there are no reseller or affiliate arrangements.
Deciding between these?
Independent help scoring them against your actual requirement rather than a feature list, and designing the integration work that follows. No reseller arrangements.
Book a conversationWant a different pairing? Build your own comparison from any products in the directory.