← Back to SOPs catalog
Keedian operations · Standard procedure
Pump-down does not reach setpoint.
A pump-down request fails to reach its configured Pump Down Setpt within Pump Down Delay. An incomplete pump-down leaves refrigerant where it should not be and risks liquid return and compressor damage on the next start.
01 Detail
Trigger, action plan, and escalation criteria.
optimization_metric
refrigeration
high
managed tier
AI: hybrid
- Related metric
refrigeration_rack_pump_down_performance
- Trigger
pump-down request does not reach Pump Down Setpt within Pump Down Delay (request/state and suction evidence confirmed)
- Value drivers
-
Asset lifespan
Operational continuity
Energy savings
- Preconditions
- Rack controller exposes a pump-down request/state plus suction pressure and timestamps; Pump Down Setpt / Pump Down Delay commissioned per rack. Setpoint/delay alone do not activate the alarm — a request/state and suction timeline are required.
- Human role
- Primary when a dispatch is required; AI confirms the sequence evidence and correlates.
- Action plan
-
(1) Confirm a real pump-down request/state occurred and that suction did not reach Pump Down Setpt within Pump Down Delay.
(2) Rule out an evidence gap (missing request/state or suction data) before scoring.
(3) Correlate valve/compressor behavior for a controllable cause and attempt a remote correction where exposed.
(4) If a mechanical cause (valve, leak-back) is implied, dispatch the refrigeration vendor with the sequence evidence.
- Escalation
-
(1) Incomplete pump-down paired with compressor start behavior indicating liquid return → asset-protection dispatch within SLA.
(2) Recurring incompletes on the same rack → valve/controls review candidate.
- Prevention
-
(1) Require a pump-down request/state and suction timeline as activation evidence so the alarm is never inferred from setpoint/delay alone.
(2) Review valve seating and pump-down configuration per rack on recurring incompletes.