Asset Twin example

DE - Comp A

Low Not assessed  Motor on Cooling / CL-COMP-A

Not in alert.

Likely faults

The latest analysis suggests no fault.

What changed

No active changes.

Trends

Measurement time 2026-10-19 17:49 to 2026-10-27 13:39 (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.

Velocity RMS · mm/s Stream 8ef8bbf3 0.203 mm/s Stream a476dc11 0.305 mm/s Stream e965dcac 0.381 mm/s
0.0 0.2 0.4 0.6 Oct 20 Oct 21 Oct 22 Oct 23 Oct 24 Oct 25 Oct 26 Oct 27

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.

Acceleration RMS · g Stream 8ef8bbf3 0.017 g Stream a476dc11 0.02 g Stream e965dcac 0.02 g
0.00 0.01 0.02 0.03 Oct 20 Oct 22 Oct 24 Oct 26

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.

Crest factor · peak ÷ RMS, no unit Stream 8ef8bbf3 0 Stream a476dc11 0 Stream e965dcac 0
0 1 2 3 4 Oct 20 Oct 22 Oct 24 Oct 26

Computed by MultiViz from each vibration measurement (waveform), about every 13 h.

Kurtosis · no unit; about 3 when nothing is impacting Stream 8ef8bbf3 0 Stream a476dc11 0 Stream e965dcac 0
0 1 2 3 4 Oct 20 Oct 22 Oct 24 Oct 26

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.

Temperature · °C latest 23 °C
0 10 20 30 Oct 20 Oct 22 Oct 24 Oct 26

Reported by the sensor itself, about every 5 min.

Speed

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.

Sensor battery · % latest 100 %
90 95 100 105 110 Oct 20 Oct 22 Oct 24 Oct 26

Reported by the sensor itself, about every 5 min.

Signal strength · unit not reported latest -48
-70 -60 -50 -40 -30 Oct 20 Oct 22 Oct 24 Oct 26

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

AxisPriorityLatest measurement
Stream 8ef8bbf3 Low 2026-10-27 07:34 Analysis and trends →
Stream a476dc11 Low 2026-10-27 07:34 Analysis and trends →
Stream e965dcac Low 2026-10-27 07:34 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 ofPriorityWhat happenedBecause of
2026-10-27 07:34 Low — an analysis

Clears

Never cleared.