BMS Points & Budget Estimator
Estimate the I/O point count and rough budget to bring a building onto one BMS.
Order-of-magnitude estimate using typical point counts per asset and a GCC per-point cost range. It excludes cabling routes, network design and vendor licensing. A puniq audit produces a costed points list.
About this tool
Before you can budget a building management system, you need a rough idea of its size. In BMS terms, size is measured in I/O points: every sensor, valve, damper, status and command that the system reads or controls. This estimator counts those points from your main assets and turns them into a planning budget.
Enter how many AHUs, FCUs and chillers you have, plus the number of floors. We apply typical per-asset point counts (an AHU is point-heavy, an FCU is light) and add a per-floor allowance for lighting and metering. The result is an order-of-magnitude I/O point count and a low-to-high budget range.
How to read the result
The headline is the estimated point count. The budget rows multiply it by a GCC per-point cost range that bundles field devices, controllers, wiring and integration labour. Use the spread, not a single figure: a clean single-vendor retrofit lands near the low end, a messy multi-vendor building with long cable runs near the high end.
Because puniq is vendor-neutral, this estimate is about scope, not a quote for any one brand. We size the open, owner-controlled system on BACnet, KNX or Modbus, then compare suppliers honestly. A puniq audit converts this into a costed points list and design.
Frequently asked
What is an I/O point, exactly?
It is a single piece of data the BMS reads or writes: a temperature reading, a valve command, a fan status, an alarm. Point count is the standard way to size and price a BMS.
How accurate is this estimate?
It is order-of-magnitude only. Real point counts depend on equipment make, control strategy and how much metering you want. Treat the range as a planning bracket, not a quote.
Why does an AHU count for so many more points than an FCU?
An AHU has many sensors and actuators (supply and return air, valves, dampers, filters, fan VFD), while an FCU typically needs just a few. That is why AHU-heavy buildings cost more per floor to control.
What does the per-point cost include?
The range bundles field devices, controllers, wiring and integration labour at GCC rates. It excludes detailed cable routing, network architecture and any vendor software licensing.
Does the budget assume a single vendor?
No. puniq is vendor-neutral, so the estimate sizes an open system on BACnet, KNX or Modbus. We then compare suppliers honestly rather than lock you to one brand.
More calculators
Ventilation & Indoor Air Quality Calculator
Calculate required fresh-air ventilation by occupancy and area to ASHRAE 62.1.
Building Intelligence Readiness Scorecard
Answer a short checklist to score how ready your building is for unified intelligence.
Vendor Lock-in Risk Assessment
Score how locked-in your building systems are and where open protocols would free you.