BAS EVALUATION CHECKLIST

When to use this evaluation: Run this evaluation any time a BAS is inherited, a retro-commissioning project begins, an EaaS or BPS/BEPS compliance engagement requires a controls baseline, or a system has been flagged for nuisance alarms, comfort complaints, or unexplained energy use.

Who should use it: Built for the controls engineer or commissioning agent leading the evaluation, but the points inventory and historian/trend pulls in Sections 1 and 3 are easiest to delegate to a BAS technician or facility engineer working in parallel with the on-site review.

Platform scope note: This checklist is platform-agnostic — it applies whether the BAS is a modern BACnet/IP system, a legacy proprietary front end, or a hybrid of both. Items are written to be answered through a combination of front-end review, trend data analysis, and direct field verification, not vendor documentation alone.

How each item is marked: Checkbox — check off once the item is confirmed in the field or verified against trend data. Status chips (✓ / REQ / N/A) — mark ✓ once confirmed, REQ if documentation has been requested but not yet received, or N/A if the item doesn't apply to this BAS.

Before evaluating logic or performance, confirm the system actually has the points and connectivity it needs — a sequence is only as good as the sensor feeding it.

• 1.Full points list obtained — physical (hardwired) and virtual (calculated/software) points, by controller✓REQN/A
• 2.Points list cross-checked against the mechanical equipment it's meant to control — flag any missing sensor or actuator✓REQN/A
• 3.Controller inventory — make, model, firmware version, and zone/system assignment for every field panel✓REQN/A
• 4.Network architecture diagram — supervisory network, field bus topology (BACnet/IP, BACnet MS/TP, Modbus, LonWorks), and gateway locations✓REQN/A
• 5.Sensor calibration records and last calibration date for critical points (OAT, supply air temp, duct static, CO2)✓REQN/A
• 6.Confirmation of which points are trended vs. simply displayed — many systems show a value without logging it✓REQN/A
• 7.Spare point capacity documented at each controller, for future ECM or retrofit tie-ins✓REQN/A
• 8.Operator workstation / front-end software version, license status, and remote access method (VPN, cloud, on-prem only)✓REQN/A
• 9.Graphics review — do floor plan and AHU graphics reflect as-built conditions, or do they show a prior configuration✓REQN/A
• 10.Backup and recovery process confirmed — where controller programming and database backups are stored, and how recently✓REQN/A

The sequence of operations is the rulebook the system is supposed to follow. This section confirms the rulebook exists, makes sense, and is actually what's running.

• 11.Written sequence of operations obtained for every major air-side and water-side system✓REQN/A
• 12.As-running control logic compared line-by-line against the written sequence — flag any deviation✓REQN/A
• 13.Occupied-mode sequence verified — supply air temp reset logic, fan control (CAV/VAV), and economizer operation✓REQN/A
• 14.Unoccupied-mode and setback sequence verified, including morning warm-up/cool-down (optimal start) logic✓REQN/A
• 15.Mode transition behavior observed in real time — occupied↔unoccupied, heating↔cooling changeover, economizer↔mechanical cooling✓REQN/A
• 16.Lockout and interlock logic confirmed — freeze-stat, low/high limit, smoke/fire, and equipment safety interlocks✓REQN/A
• 17.Staging and lead/lag logic verified for multi-unit plants (chillers, boilers, pumps, cooling towers)✓REQN/A
• 18.Demand-controlled ventilation (DCV) logic checked against CO2 setpoints, if installed✓REQN/A
• 19.Reset strategies confirmed — supply air temp reset, chilled/hot water supply temp reset, and static pressure reset✓REQN/A
• 20.Sequence documentation updated to reflect any deviations found, with engineer sign-off on the corrected version✓REQN/A

A BAS that isn't trending the right points at the right interval can't tell you anything useful after the fact — this is the evaluation's evidence base.

• 21.Trend logs confirmed active for all critical points — space temp, supply air temp, duct static, equipment status/runtime✓REQN/A
• 22.Trend sample interval appropriate to the point type (e.g., 1–5 min for fast-changing values, 15 min for slower trends)✓REQN/A
• 23.Historian storage capacity and retention period confirmed — how far back can data actually be pulled✓REQN/A
• 24.At least 30 days of trend data exported and reviewed for anomalies, short-cycling, or simultaneous heating/cooling✓REQN/A
• 25.Runtime hour-meters and start/stop counts confirmed logged for major rotating equipment (compressors, pumps, fans)✓REQN/A
• 26.Trend data cross-checked against utility interval data for at least one representative week✓REQN/A
• 27.Data export format and process confirmed — can trend data be pulled to CSV/Excel without vendor assistance✓REQN/A
• 28.Dashboard or reporting front-end reviewed for accuracy against raw trend data — confirm displayed values aren't stale or cached✓REQN/A
• 29.Gaps in trend history identified and root-caused (network outage, controller reboot, storage limit reached)✓REQN/A
• 30.M&V-grade metering identified separately from general BAS trending, if the building has IPMVP requirements✓REQN/A

An alarm system that floods operators with nuisance alerts gets ignored — the same as having no alarms at all. This section evaluates whether alarms are actually actionable.

• 31.Full alarm point list reviewed — critical, high, and informational priority tiers defined and consistently applied✓REQN/A
• 32.Alarm routing confirmed — who receives which priority tier, by what method (email, SMS, dashboard only)✓REQN/A
• 33.Nuisance alarm audit — pull 30–90 days of alarm history and flag any point generating excessive repeat alarms✓REQN/A
• 34.Alarm acknowledgment and close-out process confirmed — are alarms being actioned, or just cleared✓REQN/A
• 35.Critical alarms tested in the field (forced fault) to confirm they actually route and notify as configured✓REQN/A
• 36.Time-delay and deadband settings reviewed on alarms prone to chattering (e.g., temperature near setpoint)✓REQN/A
• 37.Fault detection and diagnostics (FDD) capability assessed — native to the BAS, third-party overlay, or absent✓REQN/A
• 38.After-hours and weekend alarm escalation path confirmed, including backup contact if primary doesn't respond✓REQN/A
• 39.Alarm log retention period confirmed and historical alarm data exportable for trend analysis✓REQN/A
• 40.Life-safety and code-related alarms (smoke, fire/life-safety interlocks) confirmed separately monitored and never suppressed✓REQN/A

Schedules and setpoints translate operational intent into equipment behavior — this is where stated occupancy and actual equipment runtime either line up or don't.

• 41.Master schedule reviewed for every zone/system — confirmed to match actual building operating hours, not a default template✓REQN/A
• 42.Holiday and exception-day schedule confirmed current for the calendar year✓REQN/A
• 43.Occupancy override process tested — after-hours override, duration limit, and automatic revert behavior✓REQN/A
• 44.Setpoints reviewed against ASHRAE 55 comfort guidance and any documented occupant complaint history✓REQN/A
• 45.Setpoint change permissions audited — who can change setpoints, and is every change logged with a timestamp/user ID✓REQN/A
• 46.Optimal start/stop parameters reviewed and tuned against actual building thermal response, not left at default✓REQN/A
• 47.Setback/setup temperature differential confirmed reasonable for unoccupied periods without risking freeze or humidity issues✓REQN/A
• 48.Schedule-vs-trend cross-check performed — does equipment runtime actually follow the programmed schedule, or run continuously✓REQN/A
• 49.Daylight saving time transition behavior confirmed correct (a surprisingly common source of schedule drift)✓REQN/A
• 50.Tenant or zone-level scheduling conflicts identified in multi-tenant buildings with submetered or leased space✓REQN/A

The BAS rarely operates in isolation anymore — this closes the loop on how it connects outward, how it reports up, and how well it's protected.

• 51.Integration points confirmed with adjacent systems — lighting controls, metering/submetering, fire/life-safety, access control✓REQN/A
• 52.ENERGY STAR Portfolio Manager or other benchmarking platform integration confirmed, if applicable✓REQN/A
• 53.API or data-export pathway documented for any third-party energy management or analytics platform in use✓REQN/A
• 54.Utility or third-party demand response (DR) program integration confirmed, including DR signal handling logic✓REQN/A
• 55.Network segmentation confirmed — BAS network isolated from general IT/business network, or risk flagged✓REQN/A
• 56.Default and shared credentials identified and flagged for remediation — front end, controllers, and remote access✓REQN/A
• 57.Remote access method reviewed for security posture (VPN vs. exposed port, multi-factor authentication status)✓REQN/A
• 58.Software and firmware patch status reviewed against vendor security advisories✓REQN/A
• 59.Standard operating reports identified — what's currently generated automatically, for whom, and how often✓REQN/A
• 60.Recommendations log compiled — prioritized list of findings from Sections 1–5, ranked by ease of fix and impact✓REQN/A