Decision point
When optimization should come before replacement
If the BAS can expose stable telemetry, accept approved setpoint writes, and retain local safeties, optimization can usually test the savings case faster than a replacement project. The first job is to understand the current point map, sequence limits, and operator constraints.
- Use existing trends and writable points before specifying a new controls stack.
- Keep the incumbent BAS interface during the proof period.
- Let measured savings decide whether replacement is still justified.
Replacement fit
When BAS replacement is the real answer
Optimization cannot rescue a controls platform that is physically failing, cyber-unacceptable, unsupported, or too opaque to provide the data and write path required for supervisory control.
- Replace when critical controllers, networks, or workstations are unreliable.
- Modernize when the owner needs a new enterprise controls standard across a portfolio.
- Treat optimization as a later layer if the site lacks basic visibility or safe write permissions.
Combined path
Use optimization evidence to scope the retrofit
The strongest path is often sequential: optimize what can be optimized now, document which constraints block deeper savings, then use that evidence to target the controls retrofit rather than buying a broad replacement on assumptions.
- Identify which points, sequences, and network limits actually block savings.
- Prioritize retrofit scope around measured energy opportunity.
- Avoid replacing working controls that can remain local safety and fallback layers.