ENGINEERING IN PERU · INTERNATIONAL ENQUIRIES

PLATFORMS · SUPERVISION AND INTEGRATION

Honeywell EBI 2025: building integration.

Recover, integrate and modernize building supervision.

HONEYWELL EBI 2025

Your building, in context.

Supervise automation, fire, access and video through an architecture defined for your operations.

Engineering and coordination in Peru · ES / EN enquiries

Honeywell EBI · manufacturer context image
Honeywell EBI · manufacturer context image

EBI · CLSS HORIZON · ONYXWORKS

Operating needs and the panel family define the path

Compare Honeywell XLS + EBI for integrated operations and NOTIFIER + CLSS Horizon for graphical fire monitoring. Identify the installed system, authorized functions and continuity requirements before modernizing.

01 · HONEYWELL XLS + EBI

Integrated operations

Assess fire, access, HVAC and video in an operating platform, including the option of redundant servers. The native fire path presented here is XLS and requires validation of models, interfaces, releases and licenses.

02 · NOTIFIER + CLSS HORIZON

Graphical fire monitoring

Assess event location on floor plans, history and operator follow-up on a compatible NOTIFIER installation. Horizon offers LAN and Cloud modes; the reviewed LAN guide specifies ONYX/INSPIRE and NOTI-FIRE-NET.

Keep XLS-NET and NOTI-FIRE-NET as separate networks. Appendix A of manual 54013:C8 requires same-brand products on a network. A shared NCM/HS-NCM reference does not allow mixing XLS and NOTIFIER.

  1. Honeywell XLS / XLS-NET → approved interface → EBIFire integration with building operations; verify model, firmware, interface, release and licenses.
  2. NOTIFIER ONYX/INSPIRE / NOTI-FIRE-NET → CLSS Gateway → Horizon LANLocal path described by the May 2025 LAN guide. Horizon Cloud requires its own architecture and connectivity validation.

Comparison of two specific applications. It does not limit all EBI capabilities to XLS or imply that NOTIFIER has no other integration or availability options. Reference diagram, not an approved client topology.

Example: fire alarm + video

A fire detection and alarm event received by EBI through an authorized interface can trigger a sequence with Digital Video Manager (DVM):

  1. Display: show live video in Station from the camera associated with the area or point.
  2. Record: trigger recording and link it to the event for review.
  3. Aim, where applicable: move a compatible pan-tilt-zoom (PTZ) camera to a configured preset. A fixed camera retains its view.

Engineering validation: check event-camera mapping, compatible equipment and interfaces, releases, licenses, operator rights, time stamps and recording availability. Test the sequence under an authorized protocol to support the operator; fire protection logic retains its approved function.

Function documented in DVM Overview and Planning Guide R2025, p. 21, and EBI 2025 Overview, p. 35. This is not a test performed at a client installation. Explore Honeywell DVM →

1. EBI 2025: integration, XLS and documented changes

Enterprise Buildings Integrator (EBI) connects subsystems through specific interfaces and licenses. For fire applications, the Life Safety Manager option supports assessing XLS-family monitoring; actual scope depends on the panel, release and approved engineering.

As a documented reference, XLS3000 datasheet 74-4034-16 (14 September 2022, p. 4) describes Q7055C1034 for connecting XLS-NET or a standalone XLS3000 to EBI. This does not establish current availability or support across every EBI 2025 or XLS4000 release; verify the specific architecture and components.

The June 2025 public brochure highlights geospatial maps, a point interface acting as an OPC UA client —OPC Unified Architecture—, BACnet/BACstac updates, DVM and Command and Control Suite integration and Energy Manager web reports. It lists Windows 11, Windows Server 2022/2025 and SQL Server 2022; confirm the permitted combination against the installed release matrix.

BBS engineering criterion: an open interface requires mapping objects, units, data quality, permissions and loss-of-link behavior. It does not itself establish a life safety function or universal compatibility across manufacturers.

2. Horizon LAN and Cloud: differences that affect the project

Connected Life Safety Services (CLSS) Horizon provides graphical fire-event visualization. Manufacturer sources distinguish LAN-Connected and Cloud-Connected. The published 2024 comparison describes monitoring and control for LAN and monitoring for Cloud; confirm these functional boundaries against the release and configuration offered.

  • LAN: the May 2025 application guide uses the CLSS Gateway HON-CGW-MBB over Ethernet and documents NOTIFIER/NOTI-FIRE-NET, ONYX and INSPIRE under specific conditions. This architecture requires static IP addressing and excludes DHCP, NAT and HTTP proxy. It distinguishes gateway and workstation licenses.
  • Cloud: assess cloud transport, connectivity and services. The comparison includes third-party panels through CLSS Pathway; verify protocol, communicator and actual event detail. A Contact ID event should not be assumed equivalent to native-interface detail.

CLSS is not equivalent to Horizon. XLS4000 datasheet HON-62112:B (25 September 2025, pp. 1 and 6) documents CLSS platform connectivity and HON-CGW-MBB. That shared reference does not establish a Horizon configuration for XLS. Obtain compatibility documentation for the specific mode and release.

Datasheet HON-62125 E describes floor plans, event priorities, user profiles, history and graphics import. This does not establish transfer of every existing function or UL-listed control. For Peru, the proposal must confirm commercial availability, lifecycle, licensing, support and current operating-system requirements. Regional product listings require manufacturer validation before committing supply.

3. ONYXWorks and UL: function, operating mode and interface

Identify the family before migrating. NOTIFIER bulletin M23.2 from 2023 describes an ONYXWorks case using NFN-GW-EM-3 toward Horizon LAN. XLS-GW-EM-3 is listed in the XLS3000 datasheet as an XLS-NET gateway: these are different references and that path cannot be extrapolated to XLS.

The ONYXWorks name alone does not identify the complete installed architecture: XLS4000 datasheet HON-62112:B describes Fire System Manager with an ONYXWorks graphical interface. Verify the actual family, workstation, gateways and functions used.

Before retiring ONYXWorks, inventory graphics, events, commands, NetLogic, audio and optional functions where actually implemented. Map each function to a proposed replacement and test evidence.

The 2022 UL document LS10050-051NF-E:K distinguishes PRU (Proprietary Receiving Unit) and PPCU (Protected Premises Control Unit). It includes a decisive restriction: Ethernet communication to the life safety network is listed for monitoring only. Control functions described for another operating mode do not remove this restriction.

This is a revision-specific reference, not blanket certification of any current ONYXWorks, EBI or Horizon installation. Obtain the applicable current listing for the model, software, function, gateway, interface and topology. A historical commercial migration offer does not establish a valid migration path today.

4. Redundancy: demonstrate end-to-end continuity

EBI’s technical architecture includes two identically configured servers with primary-server arbitration. Assess server redundancy separately from gateways, switches, links, workstations, power and the uninterruptible power supply (UPS).

  • Lost server or link: verify failure detection, transfer, pending events and operational limits.
  • Single dependency: identify any shared interface, switch, power or service that could interrupt both paths.
  • Recovery: verify reconnection, consistent states, event records and authorized return to service.

Agree acceptable timings and scenarios before testing. Do not promise interruption-free operation or induce failures in an occupied facility without a contingency and authorized work window.

5. Cause-and-effect matrix: acceptance evidence

A cause-and-effect matrix relates a condition to its intended responses. Identify where each logic function resides and how its physical outcome will be verified. A color change on a screen does not demonstrate field actuation.

  • Detection and notification: event origin, classification, location, signaling and the engineered response.
  • Ventilation and smoke: authorized interface, sequence, feedback and loss-of-communication behavior.
  • Access and egress: affected doors and interfaces, permissions and approved evacuation-route behavior.
  • Monitoring: time stamps, permitted acknowledgment, records, link failure and recovery; video where included in scope.

For buildings, campuses, plants and mining facilities in Peru, check project documentation, authority requirements and the applicable code edition. Building integration does not replace process safety instrumented systems. Protocols may require a registered professional engineer’s signature as agreed for the scope.

6. EBI One and Cognition: assess the evolution separately

Honeywell publishes an evolution toward EBI One with on-premise artificial intelligence, queries over alarms and history and Alarm Assist. Verify these capabilities as a distinct offer, release and license; they do not automatically apply to an EBI 2025 installation.

BBS proposed application: first establish inventory, data quality, useful history, event classification and cybersecurity controls. Then assess a pilot with permissions, metrics and human review. Prioritizing or grouping operational events must never be confused with inhibiting life safety alarms.

What a BBS assessment should deliver

Initial diagnosis with inventory and criticality → Intervention plan with scope, contingency and rollback → Execution and testing under change control → Closure and follow-up with evidence and acceptance.

Start with the site, panel models, ONYXWorks or EBI release, gateways, licenses, required functions, available backups and operating restrictions. Exchange drawings, configurations and credentials through an agreed private channel.

Commercial selection and design require project-specific confirmation. Stock, prices, support eligibility and service availability in Peru have not been verified here.

A platform for connected operations

Geospatial maps

Locate systems and events within the context of the facility.

OPC UA client

The 2025 edition adds a point-server interface acting as an OPC Unified Architecture client.

Alarms and workflows

Organise events and operator actions around approved roles and interfaces.

Video and incidents

Assess integration with DVM and Command and Control Suite.

Energy Manager

Assess web-based energy reporting against your monitoring objectives.

2025 platform

Check operating systems, database and workstations against the release matrix.

Hosting options

Compare on-premises deployment and hosted options subject to eligibility.

Operational security

Define permissions, communication protection and administration responsibilities.

From event to action

Define what the operator needs to see, which actions are permitted and what evidence should remain. Integration is designed around those scenarios.

EBISUPERVISION & INTEGRATION

Conceptual BBS diagram. Select a family to explore it. Interfaces and licences require project validation.

From information to a defined scope

BBS reviews inventory, versions, licences, interfaces and backups to define the intervention with site operations.

  1. Initial assessment

    Inventory, failure history, versions, licences and backups. Findings ranked by criticality.

  2. Intervention plan

    Scope, permissions, responsibilities, operating window and contingency agreed with site operations.

  3. Execution and testing

    Work under change control. Verify authorised interfaces against agreed acceptance criteria.

  4. Closeout and follow-up

    Evidence, open items and recommendations. Results reviewed with the client.

Functions and compatibility are validated against model, firmware, architecture, licensing and available engineering. The proposal defines the work window, contingency, tests and acceptance evidence.

References for your decision

Let’s define your next step.

Tell us the country, site, installed system and expected outcome.

FUNCTIONS AND BOUNDARIES

From local systems to supervision

  1. Building systems

    Each system retains its local controls and function.

  2. Project interfaces

    Explicitly enabled states, events and commands; models, versions and licences must be checked.

  3. EBI supervision

    Operational views, event management and coordination of the integrated systems.

BBS functional diagram, not a software screenshot or an installed architecture. Interfaces require project validation. Supervision does not replace the local fire-system safety logic.

BBS TECHNICAL GUIDANCE

Guidance for planning your project

Explore all guides →

BBS

What are you looking for?

Examples: