Asset Twin example

DE - Comp C

Medium Not assessed  Compressor on Cooling / CL-COMP-C

Medium In alert

5fcf8053, ef68d63d at medium priority, data as of 2026-10-27 08:34. The evidence is below: the likely faults and what changed. The alert ends when the point is back at low: when someone acknowledges it, or by itself if newer measurements no longer support the change.

Acknowledge it ↓

Likely faults

The latest analysis suggests no fault.

What changed

High Frequency
Change in acceleration for high frequency band <<4267-5267:Hz>> for mode 1 has been detected.		 stream 4aed5d89 2026-10-11 13:18
Emerging Mode
New mode 4 has been detected.		 stream 5fcf8053, stream ef68d63d 2026-10-11 13:18
Jump in Velocity RMS (scalar)
Typical level of Velocity RMS (scalar) has increased from <<1.52:mm/s>> to <<1.91:mm/s>>.		 stream ef68d63d 2026-10-09 17:01
Jump in Acceleration RMS (scalar)
Typical level of Acceleration RMS (scalar) has increased from <<0.27:g>> to <<0.34:g>>.		 stream 4aed5d89 2026-10-09 07:36
RMS Increase
An increase in RMS has been detected for mode 1 from <<0.445:g>> to <<1.031:g>>.		 stream 5fcf8053 2026-10-07 11:55
Jump in Acceleration RMS (scalar)
Typical level of Acceleration RMS (scalar) has increased from <<0.15:g>> to <<0.17:g>>.		 stream ef68d63d 2026-10-07 08:21
RMS Increase
An increase in RMS has been detected for mode 1 from <<0.316:g>> to <<0.444:g>>.		 stream 4aed5d89 2026-10-06 07:33
Jump in Envelope Peak Score
Typical level of Envelope Peak Score has increased from <<0.57:g^2>> to <<1.34:g^2>>.		 stream 5fcf8053 2026-10-06 07:33
Jump in Envelope Peak Score
Typical level of Envelope Peak Score has increased from <<0.07:g^2>> to <<0.38:g^2>>.		 stream ef68d63d 2026-10-06 07:33
Jump in Acceleration RMS (scalar)
Typical level of Acceleration RMS (scalar) has increased from <<0.1:g>> to <<0.15:g>>.		 stream ef68d63d 2026-10-06 03:11
Jump in Acceleration RMS (scalar)
Typical level of Acceleration RMS (scalar) has increased from <<0.17:g>> to <<0.39:g>>.		 stream 5fcf8053 2026-10-06 02:56
Jump in Velocity RMS (scalar)
Typical level of Velocity RMS (scalar) has increased from <<0.84:mm/s>> to <<1.52:mm/s>>.		 stream 5fcf8053 2026-10-06 00:16
Jump in Velocity RMS (scalar)
Typical level of Velocity RMS (scalar) has increased from <<0.0:mm/s>> to <<1.7:mm/s>>.		 stream ef68d63d 2026-10-02 22:16

Trends

Measurement time 2026-09-27 08:35 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 4aed5d89 0 mm/s Stream 5fcf8053 0 mm/s Stream ef68d63d 0 mm/s
0 2 4 6 8 Oct 01 Oct 08 Oct 15 Oct 22 Into alert (medium) into alert

Reported by the sensor itself, about every 5 min. MultiViz also computes it from each waveform (about every 15 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 4aed5d89 0 g Stream 5fcf8053 0 g Stream ef68d63d 0 g
0.0 0.2 0.4 0.6 Oct 08 Oct 22 Into alert (medium) into alert

Reported by the sensor itself, about every 5 min. MultiViz also computes it from each waveform (about every 15 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 4aed5d89 0 Stream 5fcf8053 0 Stream ef68d63d 0
0 2 4 6 Oct 08 Oct 22 Into alert (medium) into alert

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

Kurtosis · no unit; about 3 when nothing is impacting Stream 4aed5d89 0 Stream 5fcf8053 0 Stream ef68d63d 0
0 1 2 3 4 Oct 08 Oct 22 Into alert (medium) into alert

Computed by MultiViz from each vibration measurement (waveform), about every 15 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 10 20 30 40 Oct 08 Oct 22 Into alert (medium) into alert

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 Into alert (medium) into alert

Reported by the sensor itself, about every 5 min.

Signal strength · unit not reported latest -40
-70 -60 -50 -40 -30 Oct 08 Oct 22 Into alert (medium) into alert

Reported by the sensor itself, about every 5 min.

Acknowledge

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. That ends the alert. It counts once Multiviz has accepted the clear.


Axes

AxisPriorityLatest measurement
Stream 4aed5d89 Low 2026-10-27 08:34 Analysis and trends →
Stream 5fcf8053 — sets the priority Medium 2026-10-27 08:34 Analysis and trends →
Stream ef68d63d Medium 2026-10-27 08:34 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 08:34 Medium Went into alert an analysis

Clears

Never cleared.