Building automation system upgrades and migration

Building automation systems age faster than the mechanical equipment they control. A chiller or air handler may run for 25 years or more, but controllers, workstations and software often become unsupported in 10 to 20 years. Replacement parts disappear, the original programmer retires, the front end runs on an obsolete operating system, and the building owner is left with a system that works until it does not.

A well-planned upgrade fixes these problems and creates an opportunity to improve sequences, energy performance and data access. This guide covers how to assess an existing system, choose a migration strategy, and specify and deliver the work.

Signs that an upgrade is needed

• The manufacturer has discontinued the controllers or software, and spare parts are scarce
• The front-end workstation runs an unsupported operating system or software version
• Only one contractor can service the system because of proprietary tools or licensing
• Operators cannot get useful trends, alarms or graphics
• Controllers fail frequently or communication is unreliable
• Sequences are outdated and do not include resets, setback or demand control required by current energy codes
• The system has known cybersecurity weaknesses and cannot be patched

Assess before you design

A thorough assessment avoids surprises and lets the owner budget accurately.

1. Inventory the system. List every controller, its model, firmware, location, network and the equipment it serves. Record the point count by type.
2. Review sequences. Compare as-built documentation with what is actually programmed. Undocumented changes are common.
3. Check field devices. Sensors, actuators, valves and dampers may be reusable or may be part of the problem. Test a representative sample.
4. Evaluate networks. Document wiring types, trunk layouts, IT network connections and remote access.
5. Interview operators. Find out what works, what does not, and what information they lack.
6. Identify integrations. Lighting, meters, fire alarm interfaces, lab controls, generators, chillers with their own controls, and third-party equipment.

Migration strategies

Many owners combine strategies: replace the front end first to gain visibility and a common platform, then replace field controllers in phases aligned with equipment renewals and capital budgets. See planning equipment replacement and capital budgets.

Wiring and field devices

Reusing existing field wiring can reduce cost, but only if wiring is documented, in good condition and compatible. Some manufacturers offer replacement controllers designed to fit legacy terminal layouts, which simplifies cutover. Sensors and actuators are inexpensive relative to labour and are often worth replacing at the same time.

Specifying an open, serviceable system

The specification is the owner's best tool for avoiding future lock-in.

• Protocol: require native BACnet at all levels, with BTL-listed devices. See BACnet basics for building owners.
• Ownership of software and files: require turnover of programming tools, licences, passwords, editable program files, graphics and database backups.
• Standards: define point naming conventions, graphic standards, alarm priorities and trend requirements, ideally consistent across the owner's portfolio.
• Sequences: provide updated sequences of operation, referencing ASHRAE Guideline 36 where appropriate. See writing clear sequences of operation.
• Cybersecurity: require unique credentials, role-based access, encrypted remote access, secure configuration and patching procedures, coordinated with the owner's IT group.
• Documentation and training: as-built drawings, network diagrams, points lists, O&M manuals and hands-on operator training.
• Warranty and support: define response times and software update provisions.

Phasing and cutover

Cutover is where upgrades go wrong. Good practice includes:

1. Developing a detailed cutover plan for each system, with the sequence of work, expected downtime and fallback.
2. Scheduling work in mild weather and outside critical periods, especially for heating plants in winter and cooling plants in summer.
3. Pre-programming and bench-testing controllers before installation.
4. Performing point-to-point checks immediately after each controller is installed.
5. Keeping temporary manual control or the legacy system available until the new system is proven.
6. Coordinating with tenants and occupants about any shutdowns.

Critical facilities, such as hospitals, labs and data centres, need particularly careful phasing, often with temporary controls or redundant equipment kept online throughout.

Commissioning the new system

Every point, sequence, alarm and trend should be verified, not just the systems that were problematic. Functional testing should confirm that sequences match the specification, that interlocks and life safety interfaces work, and that graphics display correct values. Trends collected for several weeks after completion reveal tuning issues and logic errors. Our control system verification work focuses on exactly this step.

Budgeting and procurement

Upgrade costs depend mainly on point count, the amount of field device replacement, and how much after-hours work is needed for cutover. Owners should ask for pricing broken down by system or phase so scope can be adjusted without re-tendering. Where the existing contractor holds proprietary tools, competitive tendering of an open replacement system often pays for the effort of preparing a full specification.

Using the upgrade to improve performance

An upgrade is the cheapest time to add features that save energy and improve operations:

• Supply air temperature and static pressure reset
• Demand-controlled ventilation
• Optimal start and setback
• Chilled water, hot water and condenser water resets
• Metering and energy dashboards
• Fault detection and diagnostics

These measures can make an upgrade eligible for utility incentives in some provinces; check current programs before finalizing scope.

Key takeaways

• BAS components often become unsupported long before mechanical equipment wears out.
• Start with a detailed assessment of controllers, sequences, field devices, networks and integrations.
• Choose a migration strategy, from front-end replacement to full replacement, that fits budget and risk.
• Specify native BACnet, owner access to tools and files, naming standards and cybersecurity requirements.
• Plan cutover carefully, commission thoroughly, and use the upgrade to add energy-saving sequences.