Asset Twin example

DE - 601

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

Not in alert.

Likely faults

FaultLikelihoodSeen on
Sensor issue 70% stream d6efb9c5
Structural looseness 30% stream d6efb9c5

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 d5e3d1e4 2026-10-06 14:56
Jump in Envelope Peak Score
Typical level of Envelope Peak Score has increased from <<0.1:g^2>> to <<0.19:g^2>>.		 stream 7552eeec 2026-10-03 16:11
Jump in Velocity RMS (scalar)
Typical level of Velocity RMS (scalar) has increased from <<1.45:mm/s>> to <<3.1:mm/s>>.		 stream d6efb9c5 2026-10-03 08:43

Trends

Measurement time 2026-09-27 12:07 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 7552eeec 0 mm/s Stream d5e3d1e4 0 mm/s Stream d6efb9c5 0 mm/s
0 1 2 3 4 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 7552eeec 0 g Stream d5e3d1e4 0 g Stream d6efb9c5 0 g
0.0 0.2 0.4 0.6 0.8 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 7552eeec 0 Stream d5e3d1e4 0 Stream d6efb9c5 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 7552eeec 0 Stream d5e3d1e4 0 Stream d6efb9c5 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 -39
-50 -45 -40 -35 -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 7552eeec Low 2026-10-27 12:06 Analysis and trends →
Stream d5e3d1e4 Low 2026-10-27 12:06 Analysis and trends →
Stream d6efb9c5 Low 2026-10-27 12:06 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-27 12:06 Low — an analysis

Clears

Never cleared.