Productization
← Back to SOPs catalog
Keedian operations · Standard procedure

HVAC HIP Alarm Monitoring and Response — Tractor Supply.

Investigate and resolve HVAC Human Illness Prevention (HIP) temperature alarms at Tractor Supply locations within the 30-minute SLA; suppression is not permitted.

01 Detail

Trigger, action plan, and escalation criteria.

ad_hoc_client Client: Tractor Supply hvac urgent essential tier AI: hybrid SLA: 30 minutes
Value drivers
Customer experience Asset lifespan Energy savings
Preconditions
BMS email ingestion configured; alarm rule 'Temp Illness Prevention' configured at Critical Level with a 5-minute trigger and no suppression.
Human role
Building Systems Specialist acknowledges, investigates BAS data, attempts remote correction, and dispatches when temperatures stay elevated beyond ~15 minutes.
Action plan
(1) Acknowledge the alarm; confirm store number and source; begin investigation without delay (HIP alarms are Critical, never suppressed). (2) Review BAS data: current indoor temp, trend, cooling stage, equipment status, fan operation, alarm duration; classify as temporary spike, equipment failure, or sensor error. (3) Attempt remote corrective actions if BAS controls allow: lower cooling setpoint, enable cooling stage, verify fan, reset HVAC unit, confirm sensor accuracy. (4) If temperature stabilizes, continue monitoring, document actions, and close the alarm event. (5) If temperature remains elevated for ~15 minutes, create a CMMS dispatch ticket with store number, equipment ID, current temperature, and "HVAC HIP alarm – Temperature Illness Prevention event."
Escalation
(1) HVAC equipment confirmed non-operational → CMMS dispatch immediately (do not wait the 15-minute window). (2) Sensor reading suspected faulty → cross-check additional temperature points before closing alarm. (3) BAS not responding to commands → attempt remote reset, verify BAS connectivity, then dispatch if no response.
Prevention
(1) BAS connectivity health check at the start of every shift — catch comms loss before HIP fires. (2) Quarterly setpoint policy audit per site — drifted setpoints widen the gap to the HIP threshold. (3) Sensor calibration cadence per site — bad readings are a common false-positive driver.
Author
Eric Wright
Tools
BMS Email Ingestion Alarm Monitoring Platform BAS CMMS
Roles
Building Systems Specialist (BSS) Operations Supervisor Dispatch Coordinator

Purpose

Ensure HVAC Human Illness Prevention (HIP) temperature alarms are actively monitored, investigated, and resolved within the SLA. HIP alarms indicate indoor temperatures may exceed safe working conditions, creating employee safety risk and regulatory exposure.

Scope

Building Systems Specialists, Operations Supervisors, and Dispatch Coordinators within Keedian Operations responsible for monitoring BAS alarms at Tractor Supply locations.

Alarm configuration

Alarm type
HVAC HIP
Alarm rule
Temp Illness Prevention
Criticality
Critical Level
Trigger condition
Temperature condition persists for 5 minutes
Suppression
Not allowed

Procedure

Step 1 — Alarm Detection
  • Alarm received through BMS email ingestion and appears in the alarm monitoring platform.
  • Acknowledge immediately; confirm store number and alarm source; begin investigation without delay.
  • HIP alarms are Critical and Actionable — they must always be actively worked.
Step 2 — BAS Investigation
  • Verify current indoor temperature, temperature trend, cooling stage status, HVAC equipment status, fan operation, and alarm duration.
  • Classify the condition as temporary spike, HVAC equipment failure, or sensor error.
Step 3 — Attempt Remote Corrective Actions
  • Lower cooling setpoint, enable cooling stage, verify fan operation, reset HVAC unit if appropriate, confirm sensor accuracy.
  • Monitor the system to confirm temperatures return to normal.
Step 4 — Evaluate Alarm Outcome
  • Scenario A — Temperature stabilizes: continue monitoring, document actions, close the alarm event.
  • Scenario B — Temperature remains elevated: continue monitoring; confirm cooling demand active; if elevated for ~15 min, prepare a service ticket.
  • Scenario C — HVAC equipment failure: create a CMMS service ticket immediately with store number, equipment ID, current temperature, alarm type.

Quality assurance

  • Confirm temperature has returned to acceptable levels.
  • Confirm HVAC equipment is operating correctly.
  • Document all corrective actions taken.
  • Confirm dispatch issued if required.
  • Record all actions in the alarm management or CMMS system.

Troubleshooting

Sensor reading appears incorrect.
Cause — Faulty sensor or communication issue.
Solution. Verify additional temperature points; review trend history; confirm HVAC equipment operation before closing the alarm.
HVAC system not responding to commands.
Cause — Equipment failure or communication loss.
Solution. Attempt remote reset; verify BAS connectivity; create dispatch ticket if no response.
Temperature does not recover after adjustments.
Cause — Cooling-system malfunction or extreme environmental conditions.
Solution. Confirm cooling-stage operation and fan operation; dispatch a technician if temperatures stay elevated.

Documentation & reporting

  • Record alarm timestamp.
  • Record store number.
  • Record temperature readings.
  • Record BAS investigation findings.
  • Record corrective actions attempted.
  • Record dispatch status.
  • Record final resolution.

Revision history

VersionDateAuthorChanges
1.0 03/10/2026 Eric Wright Initial draft.