Asset Twin example

DE - 402

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

Not in alert.

Likely faults

FaultLikelihoodSeen on
VFD electrical noise 60% stream 1126bcee
Soft foot 30% stream 1126bcee
Loose connections 10% stream 1126bcee

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

Emerging Mode
New mode 2 has been detected.		 stream dcc3491f 2026-10-24 06:04
Emerging Mode
New mode 3 has been detected.		 stream ac962754 2026-10-22 21:22

Trends

Measurement time 2026-09-26 20:13 to 2026-10-27 13:41 (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 1126bcee 1.7 mm/s Stream ac962754 1.14 mm/s Stream dcc3491f 1.47 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 14.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 1126bcee 0.418 g Stream ac962754 0.305 g Stream dcc3491f 0.476 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 14.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 1126bcee 3.36 Stream ac962754 3.86 Stream dcc3491f 3.54
2 3 4 5 Oct 08 Oct 22

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

Kurtosis · no unit; about 3 when nothing is impacting Stream 1126bcee 2.99 Stream ac962754 3.19 Stream dcc3491f 2.83
1.5 2.0 2.5 3.0 3.5 Oct 08 Oct 22

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

Operating conditions

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

Temperature · °C latest 29 °C
20 25 30 35 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 -41
-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 1126bcee Low 2026-10-26 20:08 Analysis and trends →
Stream ac962754 Low 2026-10-26 20:08 Analysis and trends →
Stream dcc3491f Low 2026-10-26 20:08 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:08 Low — an analysis

Clears

Never cleared.