You automate processes, not devices
The most common mistake starts with the question "which controller should we buy" instead of "what do we actually want to achieve." A BMS doesn't cut costs by the mere fact of existing — it cuts them when it controls a specific process that previously ran sub-optimally. That's why the starting point isn't a manufacturer's catalogue, but an audit of how the facility really consumes energy.
In a typical warehouse, the answers to four questions determine the entire design that follows: which zones have different temperature and humidity requirements, what the real daily and weekly work rhythm is, which installations generate the highest costs — ventilation, lighting, high-bay heating, cold storage — and whether the facility has, or will have, its own energy sources that need to feed into the same system. Only from those answers does it become clear what is worth automating and where the real savings potential lies.
Choosing controllers before this audit is guesswork. And it is the most common reason a deployed BMS "does nothing" visible on the bill — it automates things that already worked well and skips the ones that actually cost money.
The communication standard is a ten-year decision, not a spec-sheet parameter
Before a manufacturer's name comes up, a far more consequential matter has to be settled: which communication protocol the system will be built on. It's a choice that binds the facility for its entire operating life, and its financial consequences surface long after deployment ends.
A system built on a closed, proprietary protocol locks the facility into one manufacturer's ecosystem. Every expansion, every service call, every change of integrator requires that same supplier's consent and price list. The maintenance tender ceases to exist — there's only one company that can do anything, and it dictates the terms. Open standards — BACnet, Modbus, KNX — reverse that dependency: devices from different manufacturers speak a common language, and expansion and service are decided by the quality of the offer, not by who holds the keys to the system.
This belongs in the contract before it's signed, not in a technical spec added after the fact. A company that proposes a closed solution isn't always acting in bad faith — sometimes it simply sells what it knows. But the consequences are borne by the facility, for the next decade.
Electrical infrastructure: cheapest at the design stage, most expensive after the fact
A BMS is not just controllers — it's also cable routes for field wiring, space and power for automation panels, and metering points placed where something actually happens. All of these share one trait: they cost a fraction of the price when planned at the detailed-design stage, and a multiple of it when they have to be retrofitted into a finished facility.
That's why electrical and automation systems should be designed together, by one team. Low-current routes run separately from power, risers with spare capacity for future metering points, automation panels with power provided for — these are decisions that are free on a drawing and mean cutting walls and rework on site. Splitting these trades between different contractors is one of the most common reasons a "simple" BMS deployment turns into costly improvisation.
Without measurements there's no automation — just control running blind
A system that doesn't measure has nothing to base decisions on. The number and placement of metering points determines whether the BMS will see where energy is being lost, or merely control blindly against a fixed schedule.
In a warehouse the minimum is energy meters split across the main loads — ventilation, lighting, heating and, where present, cold storage — because without that split there's no way to say which area drives the cost. Add to that temperature and humidity sensors placed by process zone rather than one for the whole hall, and CO2 sensors where people are present, which allow demand-controlled ventilation instead of continuous operation. A separate, critical point is contracted-power metering — indispensable wherever EV chargers or further energy-intensive equipment are planned.
The number of metering points follows from the process audit, not from a sensor price list. The audit is what says where measurement yields knowledge worth its price, and where it's merely a cost.
Energy and security: integrate from the start, don't bolt on after a year
If the warehouse has, or will have, a PV installation, battery storage or EV chargers, the BMS should see that data from day one — production, charge level, charger load — in the same system as consumption monitoring. This is where most of the money is: a system that simultaneously sees contracted power, current consumption, panel production and charger load can manage peak demand, charge the battery during off-peak tariffs and protect the facility from exceeding contracted power. Adding this integration a year after commissioning is a double cost — once for the first deployment, again for rebuilding it.
The same principle applies to security systems. If fire alarm or access control are meant to work with the BMS in event scenarios — for example shutting down ventilation and triggering smoke extraction during a fire alarm — this has to be designed from the start, not patched together from two finished, independent systems that were never meant to cooperate.
Deployment in a live facility, and the system's life after commissioning
A warehouse rarely stands still, so the automation works must be subordinated to the rhythm of its operation: installation and wiring during lower-traffic hours, commissioning zone control one at a time, testing in windows agreed with the operations team. The deployment schedule adapts to the facility's schedule, not the other way around.
But the most important part begins after handover day. A system without a defined owner on the maintenance side gradually stops being optimised — the setpoints from commissioning day stay untouched for years, even as the hall's operating conditions change. Automation that nobody monitors and tunes slowly returns to square one. That's why a complete deployment includes not only as-built documentation with the system architecture and setpoints, but also a clear answer to who watches the system, responds to alarms, and periodically corrects the setpoints as the facility lives on.
Five decisions before the first controller
Preparing a warehouse for a BMS comes down, in practice, to five decisions made before anyone touches a controller: what to automate (the process audit), on which standard (open, not closed), where to measure (metering points from the audit, not the price list), how to integrate with energy and security (from the start, not after a year), and who operates the system after commissioning. Made deliberately, they lower the deployment cost and turn automation into a tool for managing operating costs. Skipped, they yield a system that runs, lights up, and changes nothing on the bill.