Test dynamic façade BMS integration and alarm reporting for commissioning teams verifying BACnet points, interlocks, and notifications, ensuring safe, compliant, and documented performance before occupancy and ongoing operations.
- Verify BACnet point mapping, priorities, units, and timestamps end-to-end
- Prove wind, rain, and fire interlocks transition façades to safe states
- Validate alarm texts, severities, escalation, and operator acknowledgment flow
- Interactive, commentable, export-ready checklist secured by QR code
The checklist
Pre-Test Documentation & Configuration
- Confirm the façade integration scope, approved points, and controller readiness.
- Validate the approved points list against current BMS database; note object types, units, and priorities; acceptance: 100% match; evidence: marked-up list signed by controls lead.
- Check façade controller firmware and application versions using vendor tool; acceptance: versions match approved submittals; evidence: screenshots and version report.
- Confirm BACnet device instance IDs, object names, and units are unique and per naming convention; tool: BACnet browser; evidence: CSV export; acceptance: no duplicates, correct SI units.
- Verify NTP time sync on BMS and façade controllers; tool: NTP query or SNTP status; acceptance: offset ≤ 2 s; evidence: time-sync screenshots.
- Review safe-state sequences for wind, rain, and fire inputs per approved project specifications and authority requirements; acceptance: documented logic approved; evidence: signed sequence markup.
Network & Protocol Verification
- Check physical connectivity (IP or RS-485) and terminations; tool: cable tester and photos; acceptance: continuity OK, polarity correct, shield grounded per design; evidence: photos and tester report.
- Verify IP reachability: ping façade controller for 200 packets; acceptance: packet loss < 1%, latency stable; evidence: ping summary screenshot.
- Validate BACnet read/write on representative analog and binary points including priority array; tool: BACnet browser; acceptance: read/write OK, present-value updates within 2 s; evidence: browser screenshots.
- Confirm MSTP baud, addressing, and token passing (if used); tool: protocol analyzer; acceptance: no retries > 2% over 5 min; evidence: trace capture.
- Check BBMD/foreign device settings for cross-subnet routing; tool: Wireshark Who-Is/I-Am; acceptance: devices discoverable across subnets; evidence: packet trace.
- Review cybersecurity controls: unique credentials, role-based access; acceptance: least-privilege enforced; evidence: access matrix and screenshot of roles.
Point-to-Point Functional Tests
- Command a sample façade zone to 0%, 25%, 50%, 75%, 100%; acceptance: feedback within ±5% of command within 30 s; evidence: trend plot and photos.
- Test local/remote handoff: switch local panel to manual; acceptance: BMS shows ‘local’ status and blocks write; evidence: screenshots and photo of panel state.
- Verify sun sensor scaling: simulate 0–100 klx using calibrator or input override; acceptance: BMS displays within ±2% of set value; evidence: browser screenshot.
- Validate wind interlock: inject 15 m/s equivalent signal; acceptance: façades move to safe position within 30 s and latch until below threshold for 120 s; evidence: video or trend.
- Validate rain interlock: wet-contact simulation; acceptance: façades transition to safe within 60 s and auto-clear after dry 120 s; evidence: event log and photo.
- Fire alarm interface: trigger supervised input; acceptance: façades go to defined state, BMS point read-only, category ‘Life Safety’; evidence: alarm screenshot; note: per approved project specifications and authority requirements.
- Priority array behavior: apply BMS override at priority 8 then release; acceptance: feedback follows override, returns to schedule within 60 s; evidence: audit log and trend.
Alarm Logic & Notification Tests
- Simulate actuator stall: command change with no movement; acceptance: ‘Actuator Stuck’ alarm within 60 s, correct severity and text; evidence: alarm snapshot.
- Simulate comms loss: disconnect segment for 2 min; acceptance: ‘Communication Fault’ alarm, auto-restore logged; evidence: event list and Wireshark trace.
- Validate alarm acknowledgment: operator must enter comment; acceptance: ack time-stamped, user recorded; evidence: acknowledgment report export.
- Escalation test: leave alarm unacknowledged for 10 min; acceptance: email/SMS to supervisor and duty phone received; evidence: message headers/screenshots.
- Event Enrollment: confirm Off-Normal/To-Normal events, limits, deadbands; acceptance: correct priorities and states; evidence: event configuration export.
- Nuisance filtering: enable 3 s debounce on binary inputs; acceptance: no alarm chattering during simulated contact bounce; evidence: trend comparison.
Trending, Reporting & Handover
- Enable trend logs: position, wind speed, sun level, overrides at 60 s; acceptance: buffer ≥ 7 days; evidence: CSV export and storage path.
- Verify timestamps: cross-check façade and BMS log entries; acceptance: drift < 2 s; evidence: synchronized event pair screenshots.
- Compile commissioning report: include pass/fail table, defects log, photos, traces; acceptance: sign-offs from contractor, integrator, and client.
- Operator training: demonstrate alarm acknowledgment, override release, and safe-state resets; acceptance: attendance sheet with names and roles.
- Archive backups of controller apps, BMS database, and final point list in CDE; acceptance: retrievable with QR-linked as-built reference.
Preview the printable checklist
Preview page one below. Open the image or download the PDF for all pages.
At a glance
- De-risks handover by proving end-to-end BACnet communications, correct units, accurate command/feedback, and stable priority handling. Confirms safe-state logic for wind, rain, and fire inputs and documents acceptance evidence, including screenshots, network traces, and trends for future maintenance and audits.
- Builds reliable alarm reporting by validating event enrollment, severities, texts, acknowledgment requirements, and timed escalation to supervisors. Reduces nuisance through debouncing and deadbands, and ensures operators see clear alarm summaries, timestamps, and zone-level context for rapid response and root-cause analysis.
- Ensures data integrity with time synchronization under 2 s drift, 7-day minimum trend buffers, and CSV exports for analytics. Consolidates commissioning artifacts—approved points list, configuration backups, and sign-offs—within a common data environment linked to project as-builts.
- Interactive online checklist with tick, comment, and export features secured by QR code.
How to Use This Interactive Checklist
- Preparation: Gather approved points list, network analyzer, BACnet browser, vendor tools, NTP access, calibrated sensor simulators, PPE, and permits. Confirm mechanical installation and power are signed off, and ensure stakeholder availability for witnessing and acknowledgments.
- Using the Interactive Checklist: Start interactive mode, assign zones to team members, tick each item as executed, attach photos, screenshots, and traces, and record measured values, tolerances, and outcomes directly in comments.
- Export and Distribute: Generate a timestamped PDF/Excel export with embedded photos and attachments, and share with contractor, integrator, and client for daily review, defect tracking, and closeout planning.
- Sign-Off and Archive: Collect digital signatures from responsible parties, store backups and evidence in the common data environment, and secure authenticity with a QR-linked record for future audits.
Commissioning Boundaries and Prerequisites
This checklist targets dynamic façade devices—motorized shades, blinds, and louvers—integrated to a building management system via BACnet. It assumes mechanical installation, power, and structural verifications are complete and approved. The emphasis is on database accuracy, time synchronization, and correct interpretation of sequences of operation for safe-state transitions. Teams verify unique device instances, clear naming, SI units, and consistent priority arrays, ensuring commands and feedback align. Network health is proven with physical inspection, IP reachability, and, where applicable, MS/TP token stability. By resolving configuration drift, mismatched units, and duplicate addresses upfront, field time is minimized and nuisance defects are avoided. Acceptance hinges on documented evidence: screenshots, protocol traces, photos of panels, and signed markups. Life-safety interfaces, including fire alarm signals, are validated strictly per approved project specifications and authority requirements to avoid unsafe behavior and handover delays.
- Installation and power checks completed beforehand
- Unique IDs, names, and SI units confirmed
- Time synchronization offset within 2 seconds
- Physical and protocol connectivity verified
- Evidence captured and signed off
Functional Integration and Interlocks
Reliable façade automation depends on accurate command/feedback, robust interlocks, and orderly priorities. Representative zones are driven through 0–100% while verifying feedback within ±5% and response times under 30 s. Local/remote handoff must clearly block BMS writes to prevent conflicts. Environmental inputs are simulated: sun level scaling across 0–100 kilolux, wind speeds that enforce immediate safe positioning, and rain signals that initiate protective states with a sensible auto-clear delay to avoid chatter. Fire alarm integration is confirmed so façades move to the designated position, and BMS points become read-only where mandated. Priority arrays are exercised to ensure operator overrides do not persist, returning control to schedules gracefully. Each test captures trends and photographs for traceability, building a defensible commissioning record.
- Command to feedback within ±5 percent
- Wind and rain drive safe states promptly
- Fire inputs handled per approvals
- Overrides return to schedules cleanly
Alarm Reporting, Escalation, and Evidence
Alarms protect operations only when they are accurate, timely, and actionable. Event enrollment is checked for Off-Normal and To-Normal transitions, with deadbands and limits tuned to reduce noise. Clear alarm texts, severities, and categories help operators triage quickly. Acknowledgment must capture user, time, and comment, while escalation sends notifications to the right roles if alarms remain unaddressed. Communication loss, sensor faults, and actuator stalls are simulated to confirm consistent behavior and auto-recovery logs. Trend buffers and CSV exports secure the evidence required for analytics and warranty. Finally, an alarm summary dashboard presents counts by zone and priority with near-real-time refresh, ensuring issues are visible and auditable.
- Texts, severities, and categories standardized
- Acknowledgment requires time, user, comment
- Escalation reaches duty contacts reliably
- Deadbands and debounce reduce nuisance alarms
- Dashboard refresh within ten seconds