Asset Twin example

NDE - P200

Low Not assessed  Motor on Water treatment / WT-PMP-200

Not in alert.

Likely faults

FaultLikelihoodSeen on
VFD electrical noise 60% stream 409e5b0b
Inner race bearing damage 50% stream 9ef6e1d3
Soft foot 30% stream 409e5b0b
Electrical interference 30% stream 9ef6e1d3
Beating 20% stream 9ef6e1d3
Loose connections 10% stream 409e5b0b

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

No active changes.

Trends

Measurement time 2026-09-26 18:13 to 2026-10-27 13:42 (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 409e5b0b 2.26 mm/s Stream 72a675ed 3.43 mm/s Stream 9ef6e1d3 2.62 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 12.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 409e5b0b 0.724 g Stream 72a675ed 0.683 g Stream 9ef6e1d3 0.722 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 12.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 409e5b0b 3.39 Stream 72a675ed 3.77 Stream 9ef6e1d3 3.61
0 2 4 6 Oct 08 Oct 22

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

Kurtosis · no unit; about 3 when nothing is impacting Stream 409e5b0b 2.93 Stream 72a675ed 2.94 Stream 9ef6e1d3 2.85
0 1 2 3 4 Oct 08 Oct 22

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

Operating conditions

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

Temperature · °C latest 24 °C
0 10 20 30 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 -23
-32.5 -30.0 -27.5 -25.0 -22.5 -20.0 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 409e5b0b Low 2026-10-26 18:09 Analysis and trends →
Stream 72a675ed Low 2026-10-26 18:09 Analysis and trends →
Stream 9ef6e1d3 Low 2026-10-26 18:09 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 18:09 Low — an analysis

Clears

Never cleared.