What EN 15232 / ISO 52120 building automation classes actually mean for your project

If you have specified a building management system in Europe in the last decade, someone has quoted a control efficiency class at you — usually Class B, usually in a sales document, usually without saying what it would take to actually achieve it. This is a short, practical explanation of what those classes are and where projects lose them.

Where the classes come from

The framework began as EN 15232, Energy performance of buildings — Impact of building automation, controls and building management. It has since been carried into the international series as ISO 52120-1, published in Europe as EN ISO 52120-1. If you see both numbers cited on the same project, they are describing the same idea; the ISO edition is the one to work from now.

The standard does something quite specific. It takes the individual control functions in a building — how the heating is zoned, whether the ventilation responds to demand, whether the lighting knows if anyone is in the room — and sorts them into four building automation and control (BAC) efficiency classes:

• Class D — non-energy-efficient controls. Systems that would not be built new today.
• Class C — standard controls. This is the reference case: the baseline everything else is measured against.
• Class B — advanced controls, with some room-level and technical building management functions.
• Class A — high energy performance controls, with demand-driven operation and full technical building management.

The functions are listed by domain — heating, cooling, ventilation and air conditioning, domestic hot water, lighting, blind control — plus a separate group for technical building management: the monitoring, reporting and fault-detection layer that sits above the plant.

The part most projects get wrong

Your class is set by the weakest relevant function, not by the best one on the schedule. A building with sophisticated demand-controlled ventilation and no lighting control is not a Class A building. The standard is a floor, applied function by function, and the marketing tends to describe the ceiling.

The second trap is more expensive. The standard describes functions that are implemented and operating. A project can install every function required for Class A, hand over, and operate at Class C for the next fifteen years, because:

• the reset schedules were disabled during the first winter to settle a complaint;
• the occupancy sensors were commissioned to a hold time long enough to never expire in practice;
• the demand-controlled ventilation runs on a fixed schedule because the CO₂ sensors drifted and nobody recalibrated them;
• the technical building management layer was delivered, licensed, and never logged into.

None of that shows up in a handover certificate. All of it shows up in the energy bill.

The efficiency factors, and how far to trust them

The standard also offers a simplified method: tabulated BAC efficiency factors that let you estimate the energy impact of moving between classes, differentiated by building type — offices, schools, hospitals, hotels and so on. They are a genuinely useful early-stage tool for arguing that a control upgrade deserves budget.

They are not a calculation of your building. The factors are derived from reference cases, and the spread between building types is wide. Use them to justify looking properly; do not use them as the saving you commit to in a business case. Where the number matters — where someone is making a capital decision on it — the detailed hourly method, or a calibrated model of the actual building, is what you want.

What we do with this on a project

Three things, in order:

1. Set the target class before tender, function by function. Not "Class B" as a headline, but the specific list of functions in each domain that the class requires. That list belongs in the specification, where an integrator has to price it.
2. Write the sequences that deliver those functions. A class is a claim about behaviour. Behaviour lives in the sequence of operation, which is why we treat that document as a design deliverable rather than something the commissioning engineer improvises.
3. Test each function at handover, and again a season later. Functional testing against the written sequence is the only evidence that the class you paid for is the class you have. The seasonal revisit catches everything that was never exercised in the month the building happened to be handed over.

The short version

The classes are a useful common language for specifying how much control a building should have. They are not a certificate, and they are not self-enforcing. What determines your operating class is which functions are still doing their job in year three — which makes the specification and the commissioning far more important than the letter on the datasheet.