Sample BAS Modernization Roadmap
An example phased roadmap for modernizing a building automation system without an unnecessary rip and replace.
Example data for a fictional facility, shown to demonstrate the deliverable format. Not a real building or client.
This example plans replacement around equipment condition: repair faults, replace equipment at end of life, and retain working equipment. The roadmap divides the work into four phases, each with a useful outcome, planned around building operations.
Where the example building starts
The example building is a three-story office of 120,000 square feet, built in 1996. Three VAV air handlers, one per floor, serve 46 VAV boxes; the plant is 2 boilers and one air-cooled chiller. The automation system runs roughly 2,400 points over mixed BACnet MS/TP trunks, supervised by a 2009-era front end the manufacturer no longer supports. The field hardware is mostly healthy. The risk is concentrated at the top of the system: an unsupported front end, a database that needs verification, and trunks still using their startup configuration.
The phased plan
Each phase builds on the records and work completed before it and gives operators a usable result.
| Phase | Scope | Depends on | Outcome |
|---|---|---|---|
| 1. Assess and document | Inventory every controller, trunk, and point; verify the database against the building; export and archive backups; draw the network as it actually exists | No earlier phase. Establish the records needed to plan later work | Verified point lists and drawings, with condition-based recommendations for retaining or replacing each device |
| 2. Front-end migration | Replace the 2009-era front end with a supported supervisor; migrate the verified database of roughly 2,400 points; set per-operator accounts and a backup routine that is tested, not assumed | Phase 1. Verify the database before migrating it to the new supervisor | A supported platform on current software, with credentials, licensing, and backups in the owner's hands |
| 3. Trunk and IP migration | Correct MS/TP configuration and wiring faults; add a BACnet/IP router per trunk so the supervisor polls over IP; move controllers to IP panel by panel as age or failures justify it | Phase 2. The routers connect the trunks to the new supervisor | Work toward more responsive graphics and reliable trends, with legacy trunk replacement spread across phases |
| 4. Graphics and alarm rationalization | Rebuild operator graphics on the cleaned-up database; cut alarms to an actionable set with priorities that mean something; align schedules with occupancy; trend the points that support diagnosis | Phases 1 and 2. Build graphics on the verified database and new supervisor | Operator graphics, alarms, schedules, and trends that reflect the verified system |
Keep vs replace
- Keep the field controllers that pass the phase 1 health check. Most of them spend their lives reading sensors and driving actuators, and age alone is not a defect.
- Keep the sensors and actuators that verify against a reference. Replace the ones that lie; a sensor that reads wrong is worse than one that reads nothing.
- Keep the trunk wiring where it tests clean. RS-485 that is terminated and daisy-chained correctly does not care what year it was pulled.
- Keep the mechanical replacement decisions separate. Assess the chiller and boilers on their own condition, using the controls findings to inform replacement plans.
- Replace the front end. It is unsupported, it is the single point of failure, and it is where every other improvement lands.
- Replace the individual devices the assessment catches: failed I/O, controllers with a history of dropping off the trunk, actuators that no longer stroke.
Documentation comes first because later phases use it to price work and verify migration. The front end follows because it is the largest single risk in this example, and the network and graphics work use the new supervisor. Network work can improve graphics response and trend collection before individual controllers are replaced. Build graphics and alarms on the verified database to avoid repeated work. The plan spreads work across budget cycles and around building operations, with replacement based on condition.
Controls Retrofit & Modernization
Upgrade pneumatic controls, retrofit panels, and modernize aging BAS in planned stages.
How does this apply to your building?
Tell us about your system and we can discuss how this resource applies.