Unexpected Cold
An Unexpected Cold condition means a trap that should have steam running has gone cold. It does not automatically indicate a failed trap — it can also mean a process upstream was taken offline, a valve was closed, or a planned shutdown was not declared in Insights before it started.
How Detection Works
The platform monitors steam state transitions in real time. When a trap transitions from steam-on to steam-off, the analytics service evaluates whether that transition is unexpected based on the trap's operation type, the current date, and account-level settings.
When a transition is classified as unexpected, the platform:
- Updates the trap's condition to Unexpected Cold Condition
- Opens an Unexpected Cold event record with the timestamp of the transition
- Sends email alerts to users subscribed to the
steam trap unexpected coldnotification type
Eligibility Rules
Not all steam-off transitions trigger an Unexpected Cold event. The following rules determine whether a detection is created or suppressed:
| Condition | Result |
|---|---|
| Trap operation type is Continuous | Detection fires whenever steam goes off |
| Trap operation type is Seasonal, steam-off time falls inside the configured season window | Detection fires |
| Trap operation type is Seasonal, steam-off time falls outside the configured season window | Detection suppressed — off-season cold is expected |
| Trap operation type is Intermittent | Detection always suppressed — cycling is by design |
| Steam Shutdown flag is active on the account | Detection suppressed for all traps on the account, regardless of operation type |
| Trap is already in Unexpected Cold Condition state | No duplicate event is created |
| An open Unexpected Cold event already exists on the trap | No duplicate event is created |
See Operation Types for guidance on choosing the right type per trap, and Trap Configuration for how to set the Steam Shutdown flag.
Responding to an Unexpected Cold Event
When you see an Unexpected Cold event or receive an alert, work through these steps in order:
-
Determine whether the shutdown was intentional. Check whether a valve was closed, a process was stopped, or maintenance was in progress. If steam was taken offline deliberately but no shutdown was declared in Insights, the alert is a false positive — clear it and consider setting the Steam Shutdown flag before your next planned outage.
-
Check for upstream causes. If multiple traps in the same zone or header go cold simultaneously, the problem is almost certainly upstream — a supply valve, a boiler, or a section of the main line rather than the individual traps themselves.
-
Inspect the trap if steam should be running. A trap that has failed closed or a condensate drain that is blocked will produce the same reading as a process shutdown. Inspect the trap physically and record your finding as a Ground Truth measurement so the sensor data has a confirmed explanation attached to it.
-
Resolve the notification. Once you have determined the cause and taken action, resolve the event in Insights so the trap's condition updates and the alert closes.
How an Unexpected Cold Event Closes
Unexpected Cold events close in two ways:
- Automatically — when the platform detects that steam has turned back on, it sets an end timestamp on the open event. The trap's condition returns to its normal assessed state.
- Manually — you can resolve the event in Insights without waiting for steam to return, for example after confirming the shutdown was intentional or after physically repairing the trap.
The event record is retained with both start and end timestamps for audit and reporting purposes regardless of how it was closed.
Related
- Operation Types — continuous, seasonal, and intermittent behavior explained
- Trap Configuration — how to set operation type and Steam Shutdown