Asset Twin example

DE - 501

Low Not assessed  Fan on HVAC / HV-FAN-501

Not in alert.

Likely faults

The latest analysis suggests no fault.

What changed

High Frequency
Change in acceleration for high frequency band <<4145-5145:Hz>> for mode 2 has been detected.		 stream c81f8474 2026-10-26 03:48
Low Frequency
Change in velocity for low frequency band <<56-62:Hz>> for mode 5 has been detected.		 stream 4b7adcd9 2026-10-05 23:51
RMS Increase
An increase in RMS has been detected for mode 1 from <<0.373:g>> to <<0.762:g>>.		 stream 1110d1af 2026-09-27 04:15
RMS Increase
An increase in RMS has been detected for mode 1 from <<0.382:g>> to <<0.475:g>>.		 stream 4b7adcd9 2026-09-27 04:15

Trends

Measurement time 2026-09-26 16:38 to 2026-10-27 13:40 (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 1110d1af 0.914 mm/s Stream 4b7adcd9 1.02 mm/s Stream c81f8474 0.61 mm/s
0 1 2 3 Oct 01 Oct 08 Oct 15 Oct 22

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 1110d1af 0.272 g Stream 4b7adcd9 0.288 g Stream c81f8474 0.182 g
0.0 0.2 0.4 0.6 Oct 08 Oct 22

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 1110d1af 3.67 Stream 4b7adcd9 3.39 Stream c81f8474 3.69
0 2 4 6 Oct 08 Oct 22

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

Kurtosis · no unit; about 3 when nothing is impacting Stream 1110d1af 2.74 Stream 4b7adcd9 3 Stream c81f8474 3.19
0 1 2 3 4 Oct 08 Oct 22

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 41 °C
0 20 40 60 Oct 08 Oct 22

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 08 Oct 22

Reported by the sensor itself, about every 5 min.

Signal strength · unit not reported latest -37
-40 -38 -36 -34 -32 -30 Oct 08 Oct 22

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 1110d1af Low 2026-10-26 16:33 Analysis and trends →
Stream 4b7adcd9 Low 2026-10-26 16:33 Analysis and trends →
Stream c81f8474 Low 2026-10-26 16:33 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-26 16:33 Low — an analysis

Clears

Never cleared.