DE - Comp C
Low Not assessed Motor on Cooling / CL-COMP-C
Not in alert.
Likely faults
| Fault | Likelihood | Seen on |
|---|---|---|
| Rotating looseness | 70% | stream 9fde0072 |
| Process related harmonics | 30% | stream 9fde0072 |
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 Envelope Peak Score Typical level of Envelope Peak Score has increased from <<0.26:g^2>> to <<0.53:g^2>>. |
stream 9fde0072 | 2026-10-15 12:19 |
| Jump in Envelope Peak Score Typical level of Envelope Peak Score has increased from <<0.49:g^2>> to <<0.7:g^2>>. |
stream 2ed44210 | 2026-10-14 22:17 |
| Jump in Envelope Peak Score Typical level of Envelope Peak Score has increased from <<0.17:g^2>> to <<0.25:g^2>>. |
stream 8c9123c4 | 2026-10-10 23:44 |
| Jump in Acceleration RMS (scalar) Typical level of Acceleration RMS (scalar) has increased from <<0.41:g>> to <<0.65:g>>. |
stream 9fde0072 | 2026-10-08 12:46 |
| Jump in Velocity RMS (scalar) Typical level of Velocity RMS (scalar) has increased from <<1.57:mm/s>> to <<2.16:mm/s>>. |
stream 9fde0072 | 2026-10-03 05:46 |
| Jump in Velocity RMS (scalar) Typical level of Velocity RMS (scalar) has increased from <<0.38:mm/s>> to <<1.57:mm/s>>. |
stream 9fde0072 | 2026-10-02 17:41 |
Trends
Measurement time 2026-09-27 09:41 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 47 min); 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 47 min); 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 47 min.
Computed by MultiViz from each vibration measurement (waveform), about every 47 min.
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 2ed44210 | Low | 2026-10-27 09:37 | Analysis and trends → |
| Stream 8c9123c4 | Low | 2026-10-27 09:37 | Analysis and trends → |
| Stream 9fde0072 | Low | 2026-10-27 09:37 | 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-27 09:37 | Low | — | an analysis |
Clears
Never cleared.