DE - P100
Low Not assessed Pump on Water treatment / WT-PMP-100
Not in alert.
Likely faults
| Fault | Likelihood | Seen on |
|---|---|---|
| Sensor issue | 70% | stream cd9e0aa9 |
| VFD electrical noise | 60% | stream cd9e0aa9 |
| Soft foot | 30% | stream cd9e0aa9 |
| Structural looseness | 30% | stream cd9e0aa9 |
| Loose connections | 10% | stream cd9e0aa9 |
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
| Jump in Acceleration RMS (scalar) Typical level of Acceleration RMS (scalar) has increased from <<0.54:g>> to <<0.74:g>>. |
stream 16acde75 | 2026-10-15 06:46 |
| Low Frequency Change in velocity for low frequency band <<56-62:Hz>> for mode 5 has been detected. |
stream cd9e0aa9 | 2026-10-13 18:04 |
| Low Frequency Change in velocity for low frequency band <<2-8:Hz>> for mode 5 has been detected. |
stream 16acde75 | 2026-10-09 19:57 |
| Emerging Mode New mode 6 has been detected. |
stream 16acde75 | 2026-10-09 07:20 |
| Emerging Mode New mode 5 has been detected. |
stream cd9e0aa9 | 2026-10-09 07:20 |
| Jump in Acceleration RMS (scalar) Typical level of Acceleration RMS (scalar) has increased from <<0.36:g>> to <<0.55:g>>. |
stream 16acde75 | 2026-10-03 00:25 |
| Low Frequency Change in velocity for low frequency band <<56-62:Hz>> for mode 3 has been detected. |
stream cd9e0aa9 | 2026-09-26 20:51 |
Trends
Measurement time 2026-09-26 14:12 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 13 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 13 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 13 h.
Computed by MultiViz from each vibration measurement (waveform), about every 13 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.
Record a status
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. It counts once Multiviz has accepted the clear.
Axes
| Axis | Priority | Latest measurement | |
|---|---|---|---|
| Stream 16acde75 | Low | 2026-10-26 14:08 | Analysis and trends → |
| Stream 9ca9e91d | Low | 2026-10-26 14:08 | Analysis and trends → |
| Stream cd9e0aa9 | Low | 2026-10-26 14:08 | 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-26 14:08 | Low | — | an analysis |
Clears
Never cleared.