BMS energy modelling · comfort risk · weather-aware scenario planning

BMS What‑If Scenario Simulator

A decision-support concept for commercial buildings: test likely outcomes before changing live BMS parameters. Compare schedules, setpoints, frost protection, occupancy and weather forecast assumptions against energy impact, comfort risk and practical engineering recommendations.

  • Setpoints
  • Schedules
  • Forecast weather
  • Occupancy
  • Comfort risk
  • Energy impact

Interactive concept demo

Adjust BMS parameters and see the indicative impact.

This front-end demo does not call a live weather API or promise savings. It shows how the customer view could work once connected to approved forecast data, site meters, BMS trends and agreed calculation logic.

Indicative energy impactBaseline

Adjust the controls to compare the scenario.

Comfort riskMedium

Balanced settings normally need trend proof before rollout.

Recommended next stepTrend review

Check BMS trends, alarms and meter data before applying site-wide.

Important: outputs are indicative only. Final recommendations depend on the actual building, plant, controls strategy, calibration, occupancy, weather exposure, tariffs, meter evidence and approval from the responsible site team.

What this helps prove

Useful for energy consultants, landlords, facilities teams and BMS contractors.

Instead of arguing over whether a change might save energy or cause complaints, the simulator creates a controlled discussion around likely outcomes, risk and what evidence is still needed.

Weather-aware setpoint decisions

Compare proposed setpoint and frost changes with forecast outside temperatures from the customer’s approved API provider for the site area.

Monthly and yearly projections

Show possible cumulative effect over days, months and years while clearly marking estimates as unverified until checked against real site data.

Comfort risk visibility

Energy changes are shown with comfort and operational risk, helping avoid blunt settings that create hot/cold complaints.

Controlled approval route

Outputs can support a clear overview report, recommended test area and estimated costs before detailed engineering work is approved.

Better conversations with BMS providers

Creates a shared picture for the client, existing maintenance company and energy consultant before software changes are requested.

Safer rollout

Start with one AHU, heating circuit, VAV group or floor, then measure results before widening the strategy.

Visual mockups

Example pages that can be developed into customer demos.

These images show the direction: overview, scenario controls, recommendations, time-range comparisons and longer-term saving projections.

Legal, safe and professional wording

Built to support decisions, not make unsupported claims.

The simulator should be presented as a decision-support and engineering review tool. It should not promise guaranteed savings, claim live API integration before credentials are approved, or suggest BMS settings can be changed without site permission.

  • Use approved access methods and customer-authorised weather/API data sources.
  • Keep estimates clearly labelled until verified by meters, trends and site observations.
  • Record comfort risk, frost protection and operational constraints alongside saving opportunities.
  • Provide detailed logic and implementation steps only as part of agreed follow-on works.

What‑If Simulator FAQs

Does this page use live weather API data now?

No. This public page is a safe front-end demo. A live customer version can be configured later with approved API credentials, agreed data sources and a clear scope.

Can this replace an energy consultant report?

No. It is designed to help turn reports, BMS trends and meter data into practical control decisions. It works best alongside proper energy, building and plant evidence.

Can it be built inside Tridium/Niagara or a BMS front end?

The concept can be developed as a web-style dashboard or adapted into suitable BMS graphics depending on the customer’s platform, permissions and integration options.

Will it tell competitors exactly what to change?

The public and overview report versions should show findings, likely outcomes and estimated costs. Detailed control logic, software steps and implementation notes should be supplied only within agreed follow-on work.

Want to test a BMS change before committing to it? Send the site type, area, system platform, issue and any trend/meter data you already have.

Request a What‑If review