DE - 602
Medium Not assessed Motor on HVAC / HV-FAN-602
Medium In alert
471d3ce0 at medium priority, data as of 2026-10-19 17:18. The evidence is below: the likely faults and what changed. The alert ends when the point is back at low: when someone acknowledges it, or by itself if newer measurements no longer support the change.
Likely faults
| Fault | Likelihood | Seen on |
|---|---|---|
| Rotating looseness | 70% | stream b8753328, stream c76a18a7 |
| Bearing fault | 60% | stream b8753328, stream c76a18a7 |
| Inner race bearing damage | 50% | stream b8753328, stream c76a18a7 |
| Process related harmonics | 40% | stream b8753328, stream c76a18a7 |
| Electrical interference | 30% | stream b8753328, stream c76a18a7 |
| Beating | 20% | stream b8753328, stream c76a18a7 |
Each axis is analysed on its own; a fault seen on several shows the highest likelihood any of them reports, never a sum.
What changed
| Emerging Mode New mode 2 has been detected. |
stream 471d3ce0, stream b8753328, stream c76a18a7 | 2026-10-16 18:58 |
| Jump in Acceleration RMS (scalar) Typical level of Acceleration RMS (scalar) has increased from <<0.0:g>> to <<0.41:g>>. |
stream 471d3ce0 | 2026-10-09 10:28 |
| Jump in Envelope Peak Score Typical level of Envelope Peak Score has increased from <<0.46:g^2>> to <<0.97:g^2>>. |
stream b8753328 | 2026-09-24 18:13 |
Trends
Measurement time 2026-09-19 17:20 to 2026-10-27 13:42 (UTC). ▏went into alert · ▏back to low, cleared or as the evidence faded — from Multiviz's priority history.
Vibration level
How strongly the machine vibrates at this point. A rise here is what usually lies behind an alert: compare it with the alert marks.
Reported by the sensor itself, about every 5 min. MultiViz also computes it from each waveform (about every 14 h); the sensor's value is shown because it comes more often. The two may differ: each uses its own frequency range.
Impacting
Short, sharp impacts, as from a damaged bearing, raise crest factor and kurtosis — often before the overall level moves.
Reported by the sensor itself, about every 5 min. MultiViz also computes it from each waveform (about every 14 h); the sensor's value is shown because it comes more often. The two may differ: each uses its own frequency range.
Computed by MultiViz from each vibration measurement (waveform), about every 14 h.
Computed by MultiViz from each vibration measurement (waveform), about every 14 h.
Operating conditions
What the machine was doing. A change in speed or temperature explains many changes in vibration.
Reported by the sensor itself, about every 5 min.
Nothing recorded for this measuring point yet.
Sensor health
About the sensor, not the machine: a flat battery or a weak signal shows up as gaps in the data.
Reported by the sensor itself, about every 5 min.
Reported by the sensor itself, about every 5 min.
Acknowledge
Your verdict, recorded here and sent to Multiviz as a clear of the point: its priority drops to low and rises again only on what is detected after now. That ends the alert. It counts once Multiviz has accepted the clear.
Axes
| Axis | Priority | Latest measurement | |
|---|---|---|---|
| Stream 471d3ce0 — sets the priority | Medium | 2026-10-19 17:18 | Analysis and trends → |
| Stream b8753328 | Low | 2026-10-19 17:18 | Analysis and trends → |
| Stream c76a18a7 | Low | 2026-10-19 17:18 | Analysis and trends → |
History
Priority
Each time the point's level changed, from Multiviz's priority history (bounded by the deployment). A fall to low says how the alert ended: a clear, or the evidence faded.
| Data as of | Priority | What happened | Because of |
|---|---|---|---|
| 2026-10-19 17:18 | Medium | Went into alert | an analysis |
| 2026-10-19 17:18 | Low | — | an analysis |
Clears
Never cleared.