Building controls can influence heating, cooling, ventilation, lighting and operating schedules. After installation, a screen that displays values is not proof that sensors, sequences and equipment behave as intended. Verification should compare the agreed design with real operation, involve the people who use the building and document any settings that remain to be corrected. For related ownership and operational context, see the hotel-owner perspective, hotel operations, and Feathers Hospitality’s management approach.
System changes and performance tests should be carried out by qualified professionals. For ownership and operations context, see the hotel-owner perspective, hotel operations, and Feathers Hospitality’s management approach.
At a glance
- Agree functional tests before installation is considered complete.
- Test sensors, schedules, alarms and affected equipment together.
- Record baseline, settings, defects and owner for each correction.
Define the expected sequence of operation
Write what the system should do in ordinary schedules, occupied and unoccupied periods, overrides and faults. Include which zones and equipment are affected and what signals trigger each action. A clear sequence helps the owner distinguish a software issue from an upstream equipment or sensor problem.
Have the design and operations teams agree the sequence before testing. If the project changes during installation, update the document and record who approved the change. Do not rely on informal descriptions such as “the system will optimize the building” without a testable outcome.
Check the installed points and naming
Compare the control interface with the point list, equipment and actual areas served. Confirm that sensors show plausible values, labels match the room or plant and alarms reach the intended operator. A control point mapped to the wrong zone can produce apparently normal data while the equipment responds elsewhere.
Check a sample on site with a competent technician. Confirm calibration and installation details through appropriate technical procedures. Keep configuration files and point schedules under version control so a later change can be understood and reversed by authorized staff.
Test schedules and overrides in context
Run the agreed occupied and unoccupied schedules and verify that equipment starts and stops as intended. Test temporary overrides and confirm they expire or return to the approved schedule. A forgotten manual setting can keep a system in an inefficient mode long after the technician has left.
Test different days or operating patterns where relevant, and coordinate with hotel operations so comfort and service are not disrupted. Record start time, observed response and any exception. Avoid changing live settings without approval and a plan to restore the prior condition.
Verify alarms and failure responses
Simulate agreed faults safely and check that alarms identify the right equipment, location and response. Confirm where alerts appear, who receives them and whether escalation works outside normal hours. An alarm that remains only on a screen nobody monitors does not support timely action.
Do not deliberately create unsafe conditions or disable protective functions to test a control. Let qualified technicians plan and supervise simulations. Record which tests were completed, which could not be run and what evidence remains outstanding.
Measure performance against a usable baseline
Collect comparable data before and after the change where available: schedules, setpoints, runtime, consumption and comfort complaints. Record weather, occupancy and service changes that affect results. A short sample may confirm a control function but may not support a long-term energy-saving claim.
Use the same meter boundaries and time periods for comparison. Explain missing points and estimated values. European Commission guidance on building energy performance provides policy context, but it does not validate the performance of this specific hotel installation.
Hand over knowledge and close defects
Provide current diagrams, schedules, credentials through an approved secure process, manuals, training and a defect list with owners and dates. Operations staff should know which settings they may change and how to escalate unusual readings. Keep technical access limited to authorized personnel.
After corrections, retest the affected sequence rather than accepting a vendor note alone. Assign an owner to review trends after the hotel has used the system in normal operation. Close the project only when documentation, training and outstanding responsibilities are understood.
Frequently asked questions
How long should performance be monitored after commissioning?
Agree the period with the project team based on the system, season and operating patterns. A brief functional test and a seasonal performance review answer different questions.
Can an energy reduction be promised after installing controls?
Only with a defined baseline, boundaries and operating assumptions. Report measured results with context and avoid attributing every change to the control system.