Identifying and Managing BAS Overrides

Problem

Overrides are left active from troubleshooting and no one remembers them. Months later, someone asks why the thermostat isn't responding, and you discover a "temporary" override still locked in.

Root Cause

Lack of process for tracking and documenting manual overrides; operators don't understand they're bypassing automation.

Solution

1. Document Every Manual Override

Create a simple log (spreadsheet or notepad):

Date   | Override Point        | Override Value | Reason  | Tech | Expected Duration | Cleared?
11/24  | Conference Room VAV   | 100% Open      | Testing | John | 1 hour           | No ❌

2. Set Automatic Time Limits

• If your BAS supports it, set overrides to auto-revert after 4 hours or 24 hours
• Example: In Niagara, wire a scheduled action to release overrides daily at 6 AM
• Prevents "temporary" from becoming permanent

3. Daily Override Audit

• Each morning, check for active overrides
• If found, verify it's still needed
• If not, release it immediately
• Flag any overrides that should have been released

4. Color-Code Override Status

• In graphics, show overridden points in orange or red (make it obvious)
• Include a label: "Manual Override Active – Contact John"

5. Email Notification on Override Release

• Set up system to email tech when override is released
• Confirms it happened and when
• Creates audit trail

Example Override Safety Logic (Niagara)

IF override_active == true AND current_time > (override_start_time + 24_hours)
    THEN release_override()