Cost · Budgeting
Building Automation Cost: What Drives the Number
Understand the cost packages, scope factors and budgeting approach for building automation without relying on invented price figures.
Quick answer
Building automation cost is driven by the number and type of points, the systems integrated, the engineering and commissioning effort, and the condition of the building. A reliable budget comes from a point schedule, an integration matrix and a defined scope of responsibilities, not from a price per square metre alone.
Cost follows scope, not a price list
There is no meaningful universal price for building automation. Two buildings of the same size can differ by a large factor because one integrates six systems with a clear point schedule and the other integrates twelve systems in an occupied building with incomplete drawings. A useful cost conversation therefore begins with scope: what is controlled, what is monitored, what is integrated and who is responsible for each interface. Once those boundaries are explicit, the packages below can be sized and compared. A lump sum without a scope statement is not a price; it is a placeholder. The same rule applies to rates quoted per square metre or per point without a definition.
The packages that make up the number
Most projects can be broken into engineering and design, controllers and I/O hardware, field devices and actuators, integration hardware and licences, installation labour, commissioning and training, and ongoing support. Field devices are often supplied by the mechanical or electrical contractor, while controllers and integration sit with the automation supplier; the split changes the total and the risk. Ask each bidder to state what is included and excluded at every interface. The most expensive line item is frequently the one nobody priced: retesting after another trade's change, or integrating a system whose vendor did not enable the promised interface. A complete cost model names those risks before the tender.
Scope factors that move the number
Point density, protocol mix, redundancy, physical distribution, access conditions and programme all move cost. A project with many small panels across a large site costs more to wire, commission and maintain than a concentrated plant room with the same point count. A retrofit in an occupied building costs more than a new-build with clean containment. High-availability requirements add controllers, networks and engineering. A compressed programme adds shifts and coordination. None of these factors has a fixed multiplier; each should be described in the scope and priced by the bidder rather than assumed. The same applies to the split between supply-only and installed packages, which can make one bid look cheaper while the project total is unchanged.
How to budget without a quotation
Start with a point schedule and an integration matrix, even if both are preliminary. Group points by type and by panel, list the systems and protocols, and write the sequences the building must run. Ask for a budget range with the assumptions stated, then test how the number changes when scope is reduced or phased. Carry a contingency that reflects design maturity, and keep commissioning as a separate allowance so it is not squeezed by hardware savings. Compare bids on the same scope, not on the same headline total. The aim is a defensible budget that can survive a value-engineering review, not the lowest number that can be written on a page. Document the assumptions so the budget can be re-run when the design changes.
Cost packages in a building automation project
7 rows| Cost package | What it covers | Main driver |
|---|---|---|
| Engineering and design | Architecture, point schedule, sequences, graphics design | Scope clarity and number of integrated systems |
| Controllers and I/O | Controllers, I/O modules, panels, power supplies | Point count, point type and panel distribution |
| Field devices | Sensors, valves, actuators, meters | Specification level and who supplies them |
| Integration and gateways | Protocol gateways, licences, interface engineering | Number of third-party systems and interface condition |
| Installation | Cabling, containment, termination, panel mounting | Building condition, access and labour market |
| Commissioning and training | Point checks, sequence tests, documentation, operator training | Integration depth and evidence requirements |
| Support and spares | Warranty, remote support, spare parts | Service level and criticality of the building |
Project images
3 images
Frequently asked
01Can you give a price per square metre?
A rate per square metre is only a rough early check. It cannot reflect point density, system mix, integration or building condition, so it should not be used as a budget without a scope.
02Is the lowest bid the lowest cost?
Rarely. A low bid may exclude integration, training, spares or commissioning. Compare inclusions and lifecycle cost, not the headline total.
03What reduces cost most?
A clear scope, an early point schedule, standard sequences and a realistic programme. Changes after tender usually cost more than design effort before it.
04Does retrofitting cost more than new build?
Generally yes, because access, unknown conditions, occupied operation and retesting add work. The difference should be assessed in the survey, not assumed.
05Are software licences included?
Ask explicitly. Some platforms include licences in the controller price, others charge per point, per user or per site. Confirm transfer rights at handover.
06How much contingency should we carry?
It should reflect design maturity and site risk. A preliminary budget needs more contingency than a tender-stage estimate with a verified point schedule.
Next step
Bring us the building.
Tell us the building type, systems in scope and the outcome you need. We will map the shortest path to a working system.