Compressed-Air Predictive & Condition-Based Maintenance Engineering

COMPRESSED-AIR PREDICTIVE & CONDITION-BASED MAINTENANCE ENGINEERING

No Class 0 rental-fleet claim is permitted without current supplier/model certification and availability evidence.

Provisional new-series slug: /compressed-air-engineering/predictive-condition-based-maintenance/ | Primary CTA: Build My Compressor Condition-Monitoring Programme

Predictive maintenance is not predicting a failure date. it is detecting credible degradation early enough to make a better maintenance decision

It links failure mechanisms to measurable indicators, healthy baselines, trend quality, warning-to-action lead time, verification and maintenance response across compressors, motors, drives, cooling, lubrication, treatment, controls and distribution.

CBM does not replace manufacturer maintenance requirements or specialist diagnostics. Exact alarm limits, vibration severity, lubricant chemistry, electrical test values, dew-point limits and remaining-life claims remain equipment-, method- and specialist-specific.

1 — Failure Mechanism

CBM Foundation: link failure mechanism to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

2 — Condition Indicator

CBM Foundation: link condition indicator to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

3 — Healthy Baseline

CBM Foundation: link healthy baseline to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

4 — Operating-Context Tag

CBM Foundation: link operating-context tag to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

5 — Measurement Point

CBM Foundation: link measurement point to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

6 — Measurement Method

CBM Foundation: link measurement method to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

7 — Sampling Frequency

CBM Foundation: link sampling frequency to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

8 — Data Quality

CBM Foundation: link data quality to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

9 — Warning Threshold

CBM Foundation: link warning threshold to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

10 — Action Threshold

CBM Foundation: link action threshold to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

11 — Lead Time

CBM Foundation: link lead time to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

12 — Maintenance Response

CBM Foundation: link maintenance response to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

13 — Verification Response

CBM Foundation: link verification response to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

14 — Residual Risk

CBM Foundation: link residual risk to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

15 — Revision Control

CBM Foundation: link revision control to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

16 — Measurement Location

Vibration Monitoring: link measurement location to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

17 — Sensor Mounting

Vibration Monitoring: link sensor mounting to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

18 — Measurement Direction

Vibration Monitoring: link measurement direction to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

19 — Overall Vibration

Vibration Monitoring: link overall vibration to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

20 — Frequency Spectrum

Vibration Monitoring: link frequency spectrum to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

21 — Bearing Frequencies

Vibration Monitoring: link bearing frequencies to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

22 — Rotational Frequency

Vibration Monitoring: link rotational frequency to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

23 — Gear/Belt Signatures

Vibration Monitoring: link gear/belt signatures to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

24 — Airend Signatures

Vibration Monitoring: link airend signatures to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

25 — Motor Signatures

Vibration Monitoring: link motor signatures to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

26 — Baseline Spectrum

Vibration Monitoring: link baseline spectrum to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

27 — Load/Speed Context

Vibration Monitoring: link load/speed context to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

28 — Trend Rate

Vibration Monitoring: link trend rate to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

29 — Specialist Diagnosis

Vibration Monitoring: link specialist diagnosis to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

30 — Post-Repair Baseline

Vibration Monitoring: link post-repair baseline to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

31 — Ambient Temperature

Thermal Monitoring: link ambient temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

32 — Intake Temperature

Thermal Monitoring: link intake temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

33 — Discharge Temperature

Thermal Monitoring: link discharge temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

34 — Oil/Coolant Temperature

Thermal Monitoring: link oil/coolant temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

35 — Motor Temperature

Thermal Monitoring: link motor temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

36 — Bearing Temperature

Thermal Monitoring: link bearing temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

37 — Vsd Temperature

Thermal Monitoring: link VSD temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

38 — Cooler Approach Condition

Thermal Monitoring: link cooler approach condition to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

39 — Room Temperature

Thermal Monitoring: link room temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

40 — Hot-Air Recirculation

Thermal Monitoring: link hot-air recirculation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

41 — Cooling-Water Inlet

Thermal Monitoring: link cooling-water inlet to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

42 — Cooling-Water Outlet

Thermal Monitoring: link cooling-water outlet to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

43 — Thermal Trend

Thermal Monitoring: link thermal trend to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

44 — Thermal Imaging Boundary

Thermal Monitoring: link thermal imaging boundary to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

45 — Post-Cleaning Verification

Thermal Monitoring: link post-cleaning verification to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

46 — Sample Point

Lubricant & Fluid Condition: link sample point to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

47 — Sampling Cleanliness

Lubricant & Fluid Condition: link sampling cleanliness to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

48 — Sample Identity

Lubricant & Fluid Condition: link sample identity to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

49 — Oil Age/Hours

Lubricant & Fluid Condition: link oil age/hours to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

50 — Viscosity Boundary

Lubricant & Fluid Condition: link viscosity boundary to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

51 — Water/Moisture

Lubricant & Fluid Condition: link water/moisture to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

52 — Particle Contamination

Lubricant & Fluid Condition: link particle contamination to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

53 — Wear-Debris Interpretation

Lubricant & Fluid Condition: link wear-debris interpretation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

54 — Oxidation/Degradation

Lubricant & Fluid Condition: link oxidation/degradation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

55 — Chemistry Boundary

Lubricant & Fluid Condition: link chemistry boundary to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

56 — Additive-Depletion Boundary

Lubricant & Fluid Condition: link additive-depletion boundary to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

57 — Coolant Condition

Lubricant & Fluid Condition: link coolant condition to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

58 — Trend Comparison

Lubricant & Fluid Condition: link trend comparison to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

59 — Laboratory Interpretation

Lubricant & Fluid Condition: link laboratory interpretation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

60 — Corrective-Action Verification

Lubricant & Fluid Condition: link corrective-action verification to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

61 — Motor Current

Electrical & Motor Condition: link motor current to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

62 — Phase Balance

Electrical & Motor Condition: link phase balance to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

63 — Voltage Condition

Electrical & Motor Condition: link voltage condition to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

64 — Power-Factor Context

Electrical & Motor Condition: link power-factor context to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

65 — Input-Power Trend

Electrical & Motor Condition: link input-power trend to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

66 — Starting Behaviour

Electrical & Motor Condition: link starting behaviour to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

67 — Insulation-Test Boundary

Electrical & Motor Condition: link insulation-test boundary to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

68 — Bearing-Current Boundary

Electrical & Motor Condition: link bearing-current boundary to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

69 — Connection Temperature

Electrical & Motor Condition: link connection temperature to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

70 — Starter/Contact Condition

Electrical & Motor Condition: link starter/contact condition to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

71 — Vsd Fault History

Electrical & Motor Condition: link VSD fault history to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

72 — Vsd Cooling

Electrical & Motor Condition: link VSD cooling to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

73 — Power-Quality Boundary

Electrical & Motor Condition: link power-quality boundary to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

74 — Electrical Specialist Review

Electrical & Motor Condition: link electrical specialist review to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

75 — Post-Repair Baseline

Electrical & Motor Condition: link post-repair baseline to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

76 — Fad Trend

Airend & Package Performance: link FAD trend to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

77 — Specific-Power Trend

Airend & Package Performance: link specific-power trend to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

78 — Loaded Pressure

Airend & Package Performance: link loaded pressure to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

79 — Unloaded Power

Airend & Package Performance: link unloaded power to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

80 — Load/Unload Cycling

Airend & Package Performance: link load/unload cycling to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

81 — Vsd Operating Range

Airend & Package Performance: link VSD operating range to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

82 — Separator Differential Pressure

Airend & Package Performance: link separator differential pressure to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

83 — Oil-Filter Restriction

Airend & Package Performance: link oil-filter restriction to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

84 — Intake Restriction

Airend & Package Performance: link intake restriction to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

85 — Cooler Performance

Airend & Package Performance: link cooler performance to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

86 — Blowdown Behaviour

Airend & Package Performance: link blowdown behaviour to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

87 — Minimum-Pressure Valve

Airend & Package Performance: link minimum-pressure valve to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

88 — Internal Leakage Suspicion

Airend & Package Performance: link internal leakage suspicion to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

89 — Performance Degradation Rate

Airend & Package Performance: link performance degradation rate to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

90 — Overhaul-Trigger Review

Airend & Package Performance: link overhaul-trigger review to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

91 — Dryer Dew Point

Treatment Condition: link dryer dew point to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

92 — Dryer Pressure Drop

Treatment Condition: link dryer pressure drop to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

93 — Refrigeration Condition

Treatment Condition: link refrigeration condition to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

94 — Condenser Condition

Treatment Condition: link condenser condition to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

95 — Adsorption Cycle

Treatment Condition: link adsorption cycle to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

96 — Desiccant Performance

Treatment Condition: link desiccant performance to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

97 — Regeneration Demand

Treatment Condition: link regeneration demand to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

98 — Dryer Valve Performance

Treatment Condition: link dryer valve performance to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

99 — Filter Differential Pressure

Treatment Condition: link filter differential pressure to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

100 — Filter Contamination

Treatment Condition: link filter contamination to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

101 — Drain Operation

Treatment Condition: link drain operation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

102 — Condensate Load

Treatment Condition: link condensate load to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

103 — Receiver Drain

Treatment Condition: link receiver drain to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

104 — Quality-Instrument Health

Treatment Condition: link quality-instrument health to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

105 — Treatment Verification

Treatment Condition: link treatment verification to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

106 — Sensor Drift

Controls & Instruments: link sensor drift to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

107 — Pressure-Transducer Comparison

Controls & Instruments: link pressure-transducer comparison to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

108 — Temperature-Sensor Comparison

Controls & Instruments: link temperature-sensor comparison to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

109 — Flow-Meter Plausibility

Controls & Instruments: link flow-meter plausibility to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

110 — Dew-Point Sensor Health

Controls & Instruments: link dew-point sensor health to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

111 — Sequencer State

Controls & Instruments: link sequencer state to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

112 — Controller Alarm History

Controls & Instruments: link controller alarm history to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

113 — Configuration Drift

Controls & Instruments: link configuration drift to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

114 — Communication Errors

Controls & Instruments: link communication errors to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

115 — Time-Sync Health

Controls & Instruments: link time-sync health to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

116 — Software Context

Controls & Instruments: link software context to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

117 — Backup Freshness

Controls & Instruments: link backup freshness to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

118 — I/O Anomaly

Controls & Instruments: link I/O anomaly to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

119 — False-Alarm Pattern

Controls & Instruments: link false-alarm pattern to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

120 — Post-Change Verification

Controls & Instruments: link post-change verification to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

121 — Time-Series Trend

Analytics & Prediction: link time-series trend to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

122 — Rate Of Change

Analytics & Prediction: link rate of change to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

123 — Moving Baseline

Analytics & Prediction: link moving baseline to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

124 — Operating-State Segmentation

Analytics & Prediction: link operating-state segmentation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

125 — Load-Normalised Trend

Analytics & Prediction: link load-normalised trend to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

126 — Ambient-Normalised Trend

Analytics & Prediction: link ambient-normalised trend to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

127 — Event Correlation

Analytics & Prediction: link event correlation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

128 — Maintenance Overlay

Analytics & Prediction: link maintenance overlay to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

129 — Production Overlay

Analytics & Prediction: link production overlay to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

130 — Anomaly Detection

Analytics & Prediction: link anomaly detection to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

131 — Multivariable Pattern

Analytics & Prediction: link multivariable pattern to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

132 — False-Positive Control

Analytics & Prediction: link false-positive control to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

133 — False-Negative Control

Analytics & Prediction: link false-negative control to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

134 — Model Drift

Analytics & Prediction: link model drift to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

135 — Prediction Confidence

Analytics & Prediction: link prediction confidence to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

136 — Condition Alert

CBM Work Management: link condition alert to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

137 — Technical Triage

CBM Work Management: link technical triage to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

138 — Verification Measurement

CBM Work Management: link verification measurement to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

139 — Severity Classification

CBM Work Management: link severity classification to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

140 — Work-Order Creation

CBM Work Management: link work-order creation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

141 — Parts Readiness

CBM Work Management: link parts readiness to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

142 — Shutdown Planning

CBM Work Management: link shutdown planning to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

143 — Continued-Operation Decision

CBM Work Management: link continued-operation decision to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

144 — Temporary Monitoring

CBM Work Management: link temporary monitoring to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

145 — Specialist Escalation

CBM Work Management: link specialist escalation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

146 — Repair Execution

CBM Work Management: link repair execution to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

147 — As-Found Confirmation

CBM Work Management: link as-found confirmation to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

148 — As-Left Measurement

CBM Work Management: link as-left measurement to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

149 — Baseline Reset

CBM Work Management: link baseline reset to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

150 — Learning Feedback

CBM Work Management: link learning feedback to a credible failure mechanism and actionable maintenance decision. Record asset identity, measurement point/method, units, operating state, ambient/load context, baseline, trend, confidence, trigger, reviewer and response. Do not turn generic thresholds into equipment-specific limits without current evidence. An alert becomes useful only when it can be verified, acted upon within the available lead time and closed with as-found/as-left evidence.

151 — Premium Condition-Monitoring Register

152 — CBM Technique Selection Matrix

153 — Technical / Predictive / CBM Verification Gate

Each monitored parameter links to credible failure mechanism

Healthy baseline and repeatable method defined

Load/speed/ambient/state captured where material

Thresholds have evidence basis

OEM/specialist limits remain gated

CBM does not silently replace mandatory maintenance

Sensor/data-quality failures visible

Alerts verified before intrusive work where consequence permits

Lead time supports response

False positives/negatives reviewed

AI anomaly is not root-cause proof

No unsupported exact remaining-life claims

As-found validates diagnosis

As-left establishes new baseline

What is predictive maintenance for air compressors?

Using measured condition and operating data to identify credible deterioration early enough to plan an effective response.

What is condition-based maintenance?

Maintenance initiated or prioritised by verified equipment condition rather than only calendar time or running hours.

What should be monitored?

Depending on design and failure modes: vibration, temperatures, pressures, differential pressure, power, flow, cycling, lubricant condition, alarms and treatment performance.

Can vibration predict failure?

It can reveal some degradation, but interpretation depends on measurement point, speed/load, baseline and specialist analysis.

What can oil analysis show?

It can support assessment of contamination, fluid degradation and wear trends when sampling and interpretation are appropriate.

How is filter condition monitored?

Differential pressure can be useful where supported, interpreted at comparable flow and with instrument health considered.

What is a healthy baseline?

Controlled measurements from known acceptable operation used for later comparison.

Can AI predict exactly when a compressor will fail?

Not without a validated failure model and suitable data. AI can flag anomalies but exact remaining-life claims require strong evidence.

Does CBM replace preventive maintenance?

No. It complements RCM/PM; manufacturer, safety, statutory and hidden-function tasks can remain scheduled.

What happens after an alert?

Verify data, classify severity, determine safe margin, plan response, inspect/repair and capture as-found/as-left evidence.

Why normalise data?

Load, speed, ambient and mode can change readings without a change in equipment health.

How do you know CBM works?

Track confirmed defects, useful warning lead time, false alarms, repeat-failure reduction and post-maintenance baseline improvement.