Practical guide
Honeywell EBI: assessment and modernisation planning
Prepare inventory, backups, licences and interfaces to assess an EBI installation and its upgrade path.
Start with the installed environment when considering modernisation of Honeywell Enterprise Buildings Integrator (EBI). The manufacturer’s commercial release provides a direction; a viable path depends on versions, interfaces, tools, licences and site support conditions.
What Honeywell documents
The public EBI 2025 brochure presents integrated operations, map interface development and a point server acting as an OPC Unified Architecture (OPC UA) client. Honeywell also publishes EBI One and distinguishes evaluation of R500/R600 or older environments from connection paths for R610/R700 and EBI 2025. These references guide assessment questions; they do not establish a direct migration for every system.
Inventory before defining scope
- EBI release and revision, servers, workstations, operating system and database.
- Controllers, panels and interfaces; models, firmware, releases and used points.
- Licences, modules, software maintenance conditions and available engineering tools.
- Graphics, alarms, trends, schedules, users, permissions and operating procedures.
- Backups, validation date, network and power dependencies and fault history.
Compare options through continuity and evidence
| Option | Verify | Acceptance |
|---|---|---|
| Repair the current environment | Fault cause, support eligibility and existing constraints. | Recovered function and documented stability. |
| Upgrade the platform | Version matrix, licences, infrastructure and interfaces. | Critical function tests and available rollback. |
| Develop in stages | Coexistence, dependencies and an approved path. | Stage-level closure and validated operation. |
Prepare testing and rollback
Define critical functions: event reception and acknowledgement, point quality, trends, graphics, schedules and authorised interfaces. Validation must include connected systems and operations owners. Completing software installation does not demonstrate that the building engineering still behaves correctly.
Confirm backups, recovery, a work window and contingency before execution. Technical Assistance Centre (TAC) access, Honeywell Software Assurance (HSA), Forge functions and cloud options require verification of eligibility, validity, licences, connectivity, cybersecurity and commercial availability. A platform name does not guarantee site coverage.
A deliverable for approving intervention
BBS recommends a prioritised diagnosis, interface-specific scope, migration and rollback plan, acceptance protocol and outstanding action list. Supply, support and commercial services are confirmed for the particular installation and agreed scope.
How BBS organises the work
- Initial assessmentInventory, fault history and criticality.
- Intervention planScope, permissions, owners, contingency and acceptance.
- Execution and testingChange control and verification of authorised interfaces.
- Handover and follow-upEvidence, validated results and outstanding actions.
Sources and scope
Public reference sources checked on 5 October 2026. This BBS guide provides planning recommendations; applicable editions and requirements must be validated for each project.
LET’S TALK