How do you test and commission integrated smart building systems?

Integrated systems are tested in layers: each device and point, then each system on its own, then each interface between two systems, and finally complete end-to-end scenarios that cross several systems, including what happens when something fails. User acceptance by the people who will operate the building closes the sequence, alongside a plan for the tests that can only happen once the building is occupied or the season has changed. Commissioning is the wider quality process that sets the requirements those tests verify.

Three decisions make the difference between a building that is handed over and one that works. The integrated test scenarios should be written during design. One party should be clearly responsible for running integrated tests across packages. And handover should wait until the end-to-end scenarios and failure tests have passed.

Commissioning is bigger than testing

ASHRAE Guideline 0 (2019 edition) describes the commissioning process as a quality process for verifying that a facility and its systems meet the owner's project requirements. ASHRAE/IES Standard 202, most recently issued in 2024, sets out commissioning process requirements for new buildings and new systems, and ASHRAE Standard 230-2022 covers existing buildings. Commissioning starts with documented requirements and runs through design, construction, handover and early operation. Testing is one part of it: the evidence that the requirements have been met.

With integrated systems, the weak point is rarely the testing of individual systems, which each contractor carries out for its own package. It lies between the packages, where no single contractor is responsible. ASHRAE Guideline 1.1, for instance, describes validating interfaces and possible interferences between building systems as part of HVAC&R commissioning.

The test layers

The RIBA Smart Building Overlay to the Plan of Work (2024) recommends testing smart building systems in a factory environment before site installation where appropriate, and carrying out asset tagging under factory conditions where possible, coordinated with the room naming strategy. It also recommends a user acceptance period for operational applications at handover. Factory testing is worth the effort because it finds configuration and interface faults while they are cheapest to fix.

Anatomy of an integrated scenario

An integrated scenario follows a use case from trigger to outcome and states the expected result at every step. A complete one sets out the trigger and starting conditions, each system involved and what it should do, the expected timing, what each user should see, and how the scenario ends, including how alarms, tasks or overrides are cleared. It also names the evidence to be recorded, whether screenshots, logs or trend data.

Each scenario then needs its failure versions. What happens if the integration server is offline, the network link to one floor is down or a cloud service is unavailable? The answer should match the agreed degraded mode for each system.

Life-safety interfaces, such as fire alarm signals to ventilation or access control, are a special case. They are tested under the fire strategy and the relevant regulations, with the fire engineer and the approving authority, and integrated testing should include them only in the way those parties agree, without changing them.

Not starting too early

Integrated tests often fail for avoidable reasons, the commonest being that they started too soon. Entry criteria prevent this: point-to-point and system tests complete and signed off, network and security configuration in place, interface tests passed and test data available. Starting before those conditions are met wastes everyone's time and hides the root cause of defects.

Defects need a single log across all packages, each with an owner, a severity and a retest date. For a defect at an interface, both parties are recorded and one is agreed to lead the fix. Every fix is retested, along with any earlier tests it could affect.

Tests that have to wait

Some things can only be tested in use: heating in winter, cooling in summer, occupancy-based control with real occupants. These deferred tests should be listed at handover with dates and responsibilities. Monitoring-based or continuous commissioning can carry verification on into operation, but it does not replace completing the integrated tests before handover.