Honeywell Enterprise Buildings Integrator (EBI)

Enterprise Buildings Integrator (EBI) is Honeywell head-end supervisory software, marketed as enabled by the Honeywell Forge platform, with R610 named as the current release on the vendor product page. It is not a controller line. EBI is the server tier that sits above Honeywell and third-party controllers and subsystems, and Honeywell describes it as an agnostic solution to total integration and an open, scalable solution that works with a wide range of third-party equipment and software.

Architecturally it is a distributed server platform built from independent nodes that share information and provide fault tolerance, so a campus is not dependent on a single server. Above that sits an Enterprise Model, alarm management, and operator clients in three forms: an HTML5 browser client, the EasyMobile smartphone client, and a full-featured tablet client. Platform services named on the vendor page include Policy Enforcer, a Software Update Service and Windows OS compliance.

What distinguishes EBI from most BMS head-ends is that the disciplines are plug-in Manager modules on the same platform rather than bridged systems: Building Manager for HVAC and building management, LifeSafety Manager for fire detection, smoke control and public address, Security Manager for access control, Digital Video Manager for video, and Energy Manager with Attune Advisory Services and an Automated Demand Response Gateway. One operator console, one alarm queue, and workflow automation that alerts the right people and triggers procedures.

Open protocol support, on the current page, is narrower on paper than several competitors. Honeywell names BACnet (including a BACnet AWS profile and, new in R610, BACnet Secure Connect and KBOB BACnet compliance), OPC and OPC UA history, LonWorks, ONVIF for video and Enterprise Web Services. Modbus, KNX, MQTT and SNMP are not named anywhere on the pages that resolve, so a buyer who needs those should get written confirmation rather than assume them. Building-to-building federation is done over Web Services, and a zoomable interactive map covers portfolio navigation.

Cybersecurity is described with named tooling rather than a generic claim: built-in cybersecurity monitoring and updates, Policy Enforcer, the Software Update Service, Windows OS compliance and GDPR privacy protection. Deployment is offered either on premises or cloud-based, with subscription and hosted licensing options, and cloud connectivity is positioned as supporting management from multiple locations.

Platform requirements are published, though only on some regional pages: the Spanish and Malaysian EBI 600 pages state Microsoft Windows Server 2019, Windows 10 and Microsoft SQL Server 2019 compliance, and the pages note point descriptions of up to 64 characters with UTF-8 tag names. BACnet conformance is independently verifiable: the BACnet Testing Laboratories listing for EBI R600, tested February 2020, certifies it as a BACnet Advanced Operator Workstation over BACnet/IP and lists the Trending, Scheduling and Device Management BIBBs, which is the only public confirmation that EBI does trending at all.

The honest weak point is the diligence surface. No Honeywell-authored specification and technical data sheet for R600 or R610 is publicly reachable. Searching found only BACnet protocol implementation conformance statements for older releases, a legacy undated architecture poster, and a 2021 marketing brochure that contains no protocols, capacities or specifications at all. The Honeywell Forge API Marketplace page is marked discontinued, gates its documents behind sign-in and does not mention EBI, and the Forge developer portal is a JavaScript application that serves no readable public documentation. So no point counts, node counts or client limits are published anywhere reachable. The site is also regionally gated: several canonical EBI URLs return 404 while the UK, Spanish and Malaysian paths resolve and carry slightly different feature detail, so even the marketing content differs by country.

Who it fits. Large, regulated and mission-critical estates where fire, security, video and HVAC must share one operator console, one alarm queue and one enterprise model. The verticals Honeywell names match that: airports, data centres, healthcare, government and military, justice and corrections, education, hospitality, retail, industrial and smart cities. It is also the natural head-end where the Honeywell stack is already specified, because Building Manager, LifeSafety Manager, Security Manager, Digital Video Manager and Energy Manager are first-party modules rather than integrations.

Who it does not fit. Small and mid-size single buildings. There is no small-business positioning, no trial, no download and no price; the only commercial path is a Honeywell sales enquiry. Buyers who need a published protocol matrix, published capacity figures or self-service documentation before shortlisting will find nothing to work with. Estates built mainly on Modbus, KNX or MQTT field devices should treat support as unverified rather than assume Honeywell breadth.

Typical use. Campus or multi-site command and control with life-safety integration, delivered by Honeywell or an authorised partner, federated building to building over Web Services, with operators on browser, tablet and phone clients.