Test dynamic façade response to wind alarm and safe-position logic for commissioning and operations teams validating sensors, control logic, and actuators meet specification and reliably protect building envelopes during hazardous wind events.
- Proves wind sensor accuracy, thresholds, and debounce against specifications.
- Confirms control logic drives all façade zones to safe positions.
- Validates fail-safe behaviors during power or network interruptions.
- Interactive, commentable, export, QR code for field verification.
The checklist
Pre-Test Verification
- Issue permit-to-work and apply LOTO to affected panels/controllers; brief team on wind hazards and rescue plan; acceptance: signed permits and toolbox attendance uploaded; evidence: photos of LOTO tags and briefing sheet.
- Inspect representative façade units for obstructions, loose fixings, or debris using visual check and 0.5 mm feeler gauge at moving gaps; acceptance: clearances ≥ 5 mm and no fouling; evidence: photos per elevation/zone.
- Confirm anemometer calibration against handheld reference at 8–12 m/s using calibrated test fan or wind tunnel; acceptance: within ±0.5 m/s; evidence: calibration certificate, side-by-side readings, timestamped.
- Verify documented safe-position definitions per zone (angle, louvre closure, blind retraction) per approved project specifications and authority requirements; acceptance: signed matrix with elevations and unit IDs; evidence: uploaded markups.
Sensor and Threshold Validation
- Trend roof and façade-mounted anemometer points in BMS; simulate wind using signal injector or fan; acceptance: BMS value tracks sensor within ±0.5 m/s, update interval ≤ 2 s; evidence: trend export.
- Confirm wind alarm setpoint and clear setpoint per approved specifications (e.g., alarm ≥ X m/s, clear ≤ Y m/s); acceptance: matches documented values; evidence: screenshots of BMS point properties.
- Validate hysteresis/debounce: apply fluctuating wind profile; acceptance: no alarm chatter, minimum hold time per specification (recorded); evidence: annotated trend showing stable transitions.
- Verify zone mapping from each sensor to façade control groups via point-to-point testing; acceptance: only intended zones respond to simulated wind source; evidence: mapping table and BMS screenshots.
- Test sensor redundancy: isolate primary sensor and observe switchover; acceptance: secondary assumes control within ≤ 3 s, fault alarm raised; evidence: event log with timestamps.
Control Logic and BMS Integration
- Review latest approved PLC/BMS logic diagrams and version tags; acceptance: documents match deployed controller versions and date; evidence: stamped PDFs uploaded.
- Force wind alarm via BMS/PLC test flag; acceptance: global/zone wind alarm generated with timestamp, priority per specification; evidence: alarm list screenshot and CSV export.
- Measure end-to-end response time: alarm asserted to first safe-position command issued using trend logs; acceptance: ≤ 5 s unless otherwise specified; evidence: synchronized trend with markers.
- Verify mode interlocks (fire, manual override, maintenance): toggle inputs; acceptance: priority order per approved specifications, with clear annunciation; evidence: screenshots and event log.
- Confirm alarm reset logic: wind must remain below clear setpoint for hold time before auto-enable; acceptance: no premature reset; evidence: trend demonstrating hold time compliance.
Actuator Performance and Safe Position
- Select sample for motion testing: ≥ 10% of units per zone, min 10 units or all if fewer; acceptance: documented sample list covering edges/corners; evidence: test roster uploaded.
- Command selected units to safe position under wind alarm; measure travel time with stopwatch or controller timestamps; acceptance: reach defined safe position within specified time; evidence: photos before/after and time log.
- Verify position feedback (limit switch/encoder/angle): compare commanded vs actual; acceptance: within ±2° for louvres or ±10 mm for blinds; evidence: feedback trend and photo of indicators.
- Measure motor current or torque during final approach using clamp meter or controller values; acceptance: within nameplate limits and no prolonged stall; evidence: current log with unit IDs.
- Check for collisions/vibration: observe motion and measure vibration with handheld vibrometer; acceptance: no collisions, vibration < 5 mm/s RMS; evidence: video/photo and readings.
Fail-Safe and Power Scenarios
- Simulate mains power loss during wind alarm using controlled breaker open; acceptance: local controller applies defined fail-safe (move-to-safe or hold) per specifications; evidence: video and event records.
- Test UPS/backup autonomy for control system; acceptance: continuous control and logging for specified duration (record minutes); evidence: UPS runtime report and BMS trend continuity.
- Simulate network loss to façade controller (disconnect switch); acceptance: local logic enforces safe state, alarm raised centrally; evidence: controller LEDs photo and BMS communication alarm.
- Verify safe recovery on power/network restoration; acceptance: no unexpected motion, system resumes supervised control after interlocks satisfied; evidence: trend log showing orderly recovery.
Documentation and Handover
- Compile calibrated readings, screenshots, photos, and trend exports; acceptance: all artifacts tagged by zone/unit and timestamped; evidence: uploaded file index.
- Record final setpoints (alarm, clear, debounce, priorities) and any exceptions; acceptance: approved by client/consultant; evidence: signed exception list and CSV export.
- Conduct operator training on wind alarm procedure and resets; acceptance: attendance sheet signed, training materials uploaded; evidence: photos and agenda.
- Apply QR code label linking this checklist to each tested panel/zone; acceptance: code scans successfully; evidence: photo of label in situ.
Preview the printable checklist
Preview page one below. Open the image or download the PDF for all pages.
At a glance
- This checklist validates wind sensor accuracy, threshold settings, hysteresis, and zone mapping, then confirms BMS/PLC logic reliably commands all dynamic façade elements to defined safe positions within specified time and torque/current limits.
- It addresses real risk scenarios—sudden gusts, oscillating wind speeds, power or network failures—ensuring façades fail safe, alarms are time-stamped, and recoveries are controlled, preventing damage to cladding, motors, and glazing while protecting public safety.
- Interactive online checklist with tick, comment, and export features secured by QR code.
- Deliverables include calibrated readings, screenshots, trend logs, position-feedback reports, exception lists, and approvals—creating a traceable record that supports operations readiness, warranty claims, and compliance with approved project specifications and authority requirements.
How to Execute and Capture This Test
- Preparation: Confirm permits, access, and weather window. Assemble tools—handheld anemometer, signal injector, clamp meter, vibrometer, stopwatch, camera, laptop with BMS access, PPE. Verify calibration certificates and ensure rescue plan and LOTO are in place.
- Using the Interactive Checklist: Open the checklist, select project, elevation, and zones. Start interactive mode, tick steps as completed, add comments, and attach photos, screenshots, and trend exports directly from field devices.
- Using the Interactive Checklist: Capture synchronized timestamps by aligning device clocks and BMS/PLC logs. Use the built-in evidence tags to link readings and media to specific unit IDs and locations.
- Using the Interactive Checklist: At milestones (sensor validation, logic tests, motion results), generate interim PDF/Excel exports for stakeholder reviews. Use the QR link to share live status on-site without email attachments.
- Sign-Off: Review exceptions, assign actions, and retest closures. Capture digital signatures from contractor, commissioning agent, and client. Finalize the record set and archive with QR-authenticated export for O&M handover.
Why wind alarm logic must be proven under real conditions
Dynamic façades reduce solar gain and glare but can become hazardous under high winds. Proving wind alarm logic ensures sensors read accurately, alarms trigger once, and commands propagate quickly to drive units into safe positions. In practice, gusting conditions can cause alarm chatter if hysteresis and debounce are not correctly configured, leading to excessive cycling and premature wear. Thorough testing captures response time, verifies priority interlocks (fire, maintenance, manual), and confirms BMS/PLC logic aligns with approved project specifications and authority requirements. Teams should trend data during simulated wind ramps, observing the exact moment alarms assert and clear. Jobsite examples show that a 1–2 s network delay or a mis-mapped zone can leave corner units exposed, where wind pressures are highest. This checklist builds a defensible record for warranty and handover, demonstrating that every tested unit reaches its defined safe position within the specified window and without overcurrent or vibration alarms.
- Trend alarms and commands with synchronized timestamps.
- Enforce hysteresis to prevent alarm chatter.
- Prioritize interlocks per approved specifications.
- Map sensors to zones with evidence screenshots.
Defining safe positions and acceptable motion performance
Safe positions must be explicitly defined by elevation and unit type: full closure for louvres, full retraction for blinds, or a specified angle minimizing wind load. Acceptance criteria should include travel time limits, end-stop verification, and allowable torque/current at approach. Feedback devices—limit switches or encoders—provide proof that commands translate to physical positions; align these with BMS points for transparent status. Use calibrated handheld meters and controller trends to validate current draw and timing. Field crews should sample a statistically meaningful set—at least 10% per zone, including edge and corner units that experience higher loads. Excessive vibration often indicates mounting issues or binding; a simple vibrometer reading in mm/s RMS provides objective evidence. Clear photographic records of before/after positions, with unit IDs visible, strengthen traceability. By combining these methods, teams can approve performance confidently and avoid latent defects that only emerge in the first wind event.
- Define safe positions per unit type and zone.
- Verify end-stops via feedback within tight tolerances.
- Time motion and compare to specified limits.
- Measure current/torque near end-stop.
Planning for fail-safe behavior and clean recovery
Real resilience depends on how the façade behaves when things go wrong. Power interruptions or network loss should not create unsafe movements or leave units exposed. Controllers must enforce a local, deterministic fail-safe, either holding or moving to the safe position as specified. UPS provisions should keep logic alive long enough to complete a safe action and log events. Recovery is equally important: after restoration, systems should not surge into motion; instead, they should verify interlocks, wind status below clear thresholds, and then resume supervised control. Logging the switchover, UPS runtime, and communication alarms creates an auditable trail. Testing redundancy—such as sensor failover—prevents blind spots during extreme weather. These steps prove that the building envelope remains protected and operators retain situational awareness through alarms and trends, reducing the risk of panel loss, glazing damage, or injuries during unexpected outages or gusts.
- Simulate power and network loss safely.
- Confirm local controller enforces safe state.
- Verify orderly recovery before resuming motion.
- Document UPS runtime and alarms.
