Asset Twin example

DE - 501

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

Not in alert.

Likely faults

FaultLikelihoodSeen on
Rotating looseness 70% stream 2f1a63c4
VFD electrical noise 60% stream 2f1a63c4, stream 773d4419
Process related harmonics 30% stream 2f1a63c4
Soft foot 30% stream 2f1a63c4, stream 773d4419
Loose connections 10% stream 2f1a63c4, stream 773d4419

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.521:g>> to <<1.083:g>>.		 stream 2f1a63c4 2026-10-22 06:56
Jump in Envelope Peak Score
Typical level of Envelope Peak Score has increased from <<0.48:g^2>> to <<0.71:g^2>>.		 stream 2f1a63c4 2026-10-10 22:53
Low Frequency
Change in velocity for low frequency band <<2-8:Hz>> for mode 6 has been detected.		 stream 773d4419 2026-10-06 06:21
Low Frequency
Change in velocity for low frequency band <<2-8:Hz>> for mode 2 has been detected.		 stream 773d4419 2026-10-03 16:24

Trends

Measurement time 2026-09-26 20:32 to 2026-10-27 13:43 (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 2f1a63c4 1.55 mm/s Stream 773d4419 1.63 mm/s Stream 8bfd4774 1.32 mm/s
0 2 4 6 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.5 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 2f1a63c4 0.545 g Stream 773d4419 0.404 g Stream 8bfd4774 0.496 g
0.0 0.5 1.0 1.5 Oct 08 Oct 22

Reported by the sensor itself, about every 5 min. MultiViz also computes it from each waveform (about every 13.5 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 2f1a63c4 3.63 Stream 773d4419 3.56 Stream 8bfd4774 3.68
0 2 4 6 Oct 08 Oct 22

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

Kurtosis · no unit; about 3 when nothing is impacting Stream 2f1a63c4 2.67 Stream 773d4419 2.91 Stream 8bfd4774 3.09
0 1 2 3 4 Oct 08 Oct 22

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

Operating conditions

What the machine was doing. A change in speed or temperature explains many changes in vibration.

Temperature · °C latest 32 °C
0 10 20 30 40 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 -39
-70 -60 -50 -40 -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 2f1a63c4 Low 2026-10-26 20:31 Analysis and trends →
Stream 773d4419 Low 2026-10-26 20:31 Analysis and trends →
Stream 8bfd4774 Not analysed — 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 20:31 Low — an analysis

Clears

Never cleared.