Asset Twin example

DE - 602

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

Not in alert.

Likely faults

FaultLikelihoodSeen on
Sensor issue 70% stream 3eb7d0cb, stream 9a0e85f8, stream d08fde4a
Rotating looseness 70% stream 3eb7d0cb
Structural looseness 30% stream 3eb7d0cb, stream 9a0e85f8, stream d08fde4a
Process related harmonics 30% stream 3eb7d0cb

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

RMS Increase
An increase in RMS has been detected for mode 1 from <<0.295:g>> to <<0.583:g>>.		 stream 3eb7d0cb 2026-10-15 10:20
Jump in Velocity RMS (scalar)
Typical level of Velocity RMS (scalar) has increased from <<1.22:mm/s>> to <<2.21:mm/s>>.		 stream 9a0e85f8 2026-10-03 04:29
Jump in Velocity RMS (scalar)
Typical level of Velocity RMS (scalar) has increased from <<1.47:mm/s>> to <<2.26:mm/s>>.		 stream d08fde4a 2026-10-03 00:24
Low Frequency
Change in velocity for low frequency band <<2-8:Hz>> for mode 1 has been detected.		 stream d08fde4a 2026-09-27 12:50

Trends

Measurement time 2026-09-26 18:08 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 3eb7d0cb 0 mm/s Stream 9a0e85f8 0 mm/s Stream d08fde4a 0 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 3eb7d0cb 0 g Stream 9a0e85f8 0 g Stream d08fde4a 0 g
0.00 0.25 0.50 0.75 1.00 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 3eb7d0cb 0 Stream 9a0e85f8 0 Stream d08fde4a 0
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 3eb7d0cb 0 Stream 9a0e85f8 0 Stream d08fde4a 0
0 2 4 6 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 0 °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 -52
-70 -60 -50 -40 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 3eb7d0cb Low 2026-10-26 17:59 Analysis and trends →
Stream 9a0e85f8 Low 2026-10-26 17:59 Analysis and trends →
Stream d08fde4a Low 2026-10-26 17:59 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 17:59 Low — an analysis

Clears

Never cleared.