Category: Uncategorized

Every rolling-element bearing generates characteristic vibration frequencies when a defect forms on one of its contact surfaces. These frequencies — BPFO, BPFI, BSF, and FTF — are purely geometric functions of the bearing dimensions and shaft speed. If you can read a manufacturer datasheet and know the shaft RPM, you can calculate the exact frequencies a monitoring system should look for. This article walks through each formula step by step, then applies them to a real SKF 6205 deep-groove ball bearing as a worked example.

Why Defect Frequencies Matter

Vibration analysis relies on matching spectral peaks to known mechanical sources. A bearing with a spall on its outer race produces impulses at a rate determined by how many rolling elements pass over that spall per second. That rate is the Ball Pass Frequency, Outer Race (BPFO). Without knowing the expected defect frequencies, an analyst staring at an FFT spectrum has no way to distinguish a bearing fault from a gear mesh harmonic, a belt frequency, or electrical noise.

Condition monitoring systems — from handheld analyzers to permanently installed IoT sensors — use these calculated frequencies as the foundation for automated fault detection. The system computes the expected defect frequencies from bearing geometry and shaft speed, then monitors spectral energy at those frequencies and their harmonics. When amplitude rises above a baseline threshold at BPFO, the system flags an outer race defect. This is why getting the calculation right matters: an error in the expected frequency means the system watches the wrong part of the spectrum.

The Four Bearing Defect Frequencies

All four formulas share the same geometric inputs:

• N — Number of rolling elements (balls or rollers)
• B_d — Rolling element diameter (mm)
• P_d — Pitch diameter, the diameter of the circle passing through the centers of the rolling elements (mm)
• α — Contact angle (degrees); zero for deep-groove and cylindrical roller bearings
• f_r — Shaft rotational frequency in Hz (RPM ÷ 60)

BPFO — Ball Pass Frequency, Outer Race

BPFO is the frequency of impulses generated when rolling elements pass over a defect on the stationary outer race:

BPFO = (N / 2) × f_r × (1 - (B_d / P_d) × cos α)

Because the outer race is typically stationary and the defect sits in the load zone, BPFO is usually the easiest defect frequency to detect. The impulses are consistent in amplitude because the load on each rolling element is roughly the same as it crosses the defect in the loaded region.

BPFI — Ball Pass Frequency, Inner Race

BPFI is the frequency of impulses when rolling elements pass over a defect on the rotating inner race:

BPFI = (N / 2) × f_r × (1 + (B_d / P_d) × cos α)

Note the sign difference: the inner race rotates with the shaft, so each rolling element encounters the defect more frequently than for an outer race fault. However, BPFI defects are typically harder to detect because the defect moves in and out of the load zone, causing amplitude modulation at the shaft frequency (1× RPM). This modulation produces sidebands around BPFI spaced at f_r.

BSF — Ball Spin Frequency

BSF is the rotational frequency of a rolling element about its own axis:

BSF = (P_d / (2 × B_d)) × f_r × (1 - (B_d / P_d)² × cos² α)

A defect on a rolling element strikes both the inner and outer raceways once per revolution of the element, so a ball defect typically produces a spectral peak at 2× BSF. BSF defects are the most difficult to detect because the ball rotates within the cage, and the defect orientation relative to the raceways changes constantly, producing an irregular impulse pattern.

FTF — Fundamental Train Frequency (Cage Frequency)

FTF is the rotational frequency of the bearing cage:

FTF = (f_r / 2) × (1 - (B_d / P_d) × cos α)

Note that FTF = BPFO / N. The cage rotates slower than the shaft — typically 0.35 to 0.45 times shaft speed. Cage defects are rare but dangerous; they often indicate inadequate lubrication or a cage crack that can lead to catastrophic bearing seizure. Because FTF is a sub-synchronous frequency (below shaft speed), it requires sufficient spectral resolution at the low end.

Worked Example: SKF 6205 at 1,800 RPM

The SKF 6205 is one of the most common deep-groove ball bearings in industrial use: electric motor fan ends, pump shafts, conveyor idlers. Its geometry is well documented.

Step 1: Extract Geometry from the Datasheet

From the SKF 6205 product page or any bearing catalog:

• Number of balls (N): 9
• Ball diameter (B_d): 7.938 mm (5/16 inch)
• Pitch diameter (P_d): 38.50 mm
• Contact angle (α): 0° (deep-groove, so cos 0° = 1)

Some datasheets list the bore (25 mm) and outer diameter (52 mm) but not the pitch diameter directly. In that case, P_d ≈ (bore + OD) / 2 = (25 + 52) / 2 = 38.5 mm. The ball diameter may require looking up the specific bearing series; for the 6205, the rolling element diameter is widely published as 7.938 mm.

Step 2: Calculate the Shaft Frequency

f_r = 1800 / 60 = 30 Hz

Step 3: Calculate Each Defect Frequency

BPFO:

BPFO = (9 / 2) × 30 × (1 - 7.938 / 38.50)
     = 4.5 × 30 × (1 - 0.2062)
     = 4.5 × 30 × 0.7938
     = 107.2 Hz

BPFI:

BPFI = (9 / 2) × 30 × (1 + 7.938 / 38.50)
     = 4.5 × 30 × (1 + 0.2062)
     = 4.5 × 30 × 1.2062
     = 162.8 Hz

BSF:

BSF = (38.50 / (2 × 7.938)) × 30 × (1 - (7.938 / 38.50)²)
    = 2.425 × 30 × (1 - 0.0425)
    = 2.425 × 30 × 0.9575
    = 69.7 Hz

FTF:

FTF = (30 / 2) × (1 - 7.938 / 38.50)
    = 15 × 0.7938
    = 11.9 Hz

Step 4: Verify the Relationships

As a sanity check: FTF × N should equal BPFO. Here, 11.9 × 9 = 107.1 Hz, which matches BPFO within rounding. Also, BPFI > BPFO is expected because the inner race moves with the shaft, producing a higher contact rate. And FTF should be roughly 0.35–0.45 × f_r; here 11.9 / 30 = 0.397, which falls in the expected range.

Worked Example: SKF 6312 at 1,800 RPM

The SKF 6312 is a larger deep-groove ball bearing commonly found on pump shafts, industrial blower fans, and medium-duty conveyor drives. Working through a second bearing model reinforces the calculation process and shows how geometry changes affect defect frequencies.

Step 1: Extract Geometry from the Datasheet

From the SKF 6312 product page:

• Number of balls (N): 8
• Ball diameter (B_d): 22.225 mm (7/8 inch)
• Pitch diameter (P_d): 95.0 mm
• Contact angle (α): 0° (deep-groove)

The bore is 60 mm and the OD is 130 mm, giving P_d ≈ (60 + 130) / 2 = 95 mm. Note that despite being a larger bearing than the 6205, the 6312 has fewer balls (8 vs 9) but larger ball diameter (22.2 mm vs 7.9 mm).

Step 2: Shaft Frequency

f_r = 1800 / 60 = 30 Hz

Step 3: Calculate Each Defect Frequency

First, compute the diameter ratio: B_d / P_d = 22.225 / 95.0 = 0.2339

BPFO:

BPFO = (8 / 2) × 30 × (1 - 0.2339)
     = 4 × 30 × 0.7661
     = 91.9 Hz

BPFI:

BPFI = (8 / 2) × 30 × (1 + 0.2339)
     = 4 × 30 × 1.2339
     = 148.1 Hz

BSF:

BSF = (95.0 / (2 × 22.225)) × 30 × (1 - 0.2339²)
    = 2.138 × 30 × (1 - 0.0547)
    = 2.138 × 30 × 0.9453
    = 60.6 Hz

FTF:

FTF = (30 / 2) × (1 - 0.2339)
    = 15 × 0.7661
    = 11.5 Hz

Step 4: Verify

FTF × N = 11.5 × 8 = 92.0 Hz ≈ BPFO (91.9 Hz) — confirmed. Comparing to the 6205: despite the larger bearing, BPFO is lower (91.9 Hz vs 107.2 Hz) because the 6312 has fewer rolling elements (8 vs 9). Fewer balls means fewer impulses per shaft revolution, even though each impulse carries more energy due to the higher load per rolling element.

Worked Example: SKF 6316 at 1,500 RPM

The SKF 6316 is a heavy-duty deep-groove ball bearing used on large electric motor drive ends, gearbox input shafts, and heavy industrial pumps. This example uses 1,500 RPM (a common 4-pole motor speed) to demonstrate how shaft speed scales the defect frequencies.

Step 1: Extract Geometry from the Datasheet

From the SKF 6316 product page:

• Number of balls (N): 8
• Ball diameter (B_d): 28.575 mm (1-1/8 inch)
• Pitch diameter (P_d): 125.0 mm
• Contact angle (α): 0° (deep-groove)

Bore is 80 mm, OD is 170 mm: P_d ≈ (80 + 170) / 2 = 125 mm.

Step 2: Shaft Frequency

f_r = 1500 / 60 = 25 Hz

Step 3: Calculate Each Defect Frequency

Diameter ratio: B_d / P_d = 28.575 / 125.0 = 0.2286

BPFO:

BPFO = (8 / 2) × 25 × (1 - 0.2286)
     = 4 × 25 × 0.7714
     = 77.1 Hz

BPFI:

BPFI = (8 / 2) × 25 × (1 + 0.2286)
     = 4 × 25 × 1.2286
     = 122.9 Hz

BSF:

BSF = (125.0 / (2 × 28.575)) × 25 × (1 - 0.2286²)
    = 2.187 × 25 × (1 - 0.05226)
    = 2.187 × 25 × 0.9477
    = 51.8 Hz

FTF:

FTF = (25 / 2) × (1 - 0.2286)
    = 12.5 × 0.7714
    = 9.6 Hz

Step 4: Verify

FTF × N = 9.6 × 8 = 76.8 Hz ≈ BPFO (77.1 Hz) — confirmed. At 1,500 RPM vs 1,800 RPM, all defect frequencies are proportionally lower. This is the key point about variable-speed machinery: if this motor is driven by a VFD and runs at different speeds, the defect frequencies shift proportionally, and the monitoring system must track shaft speed to keep watching the right spectral bins.

Quick Reference: Defect Frequencies Compared

Accounting for Real-World Complications

Slip

The formulas above assume pure rolling contact with no slip. In practice, rolling elements slip slightly, particularly under light load or during speed changes. Slip typically reduces the actual defect frequencies by 1–3% relative to the calculated values. This is why experienced analysts look for spectral energy in a narrow band around the calculated frequency rather than at a single bin. Monitoring systems that use automatic peak-matching algorithms typically apply a ±2–3% tolerance window.

Variable Speed

All four defect frequencies scale linearly with shaft speed. For variable-speed machinery, the monitoring system must either track the shaft speed in real time (using a tachometer or encoder) and recompute frequencies continuously, or use order tracking to normalize the spectrum against shaft speed. Without speed tracking, a defect frequency at 107 Hz at 1,800 RPM shifts to 119 Hz at 2,000 RPM — and a fixed-frequency alarm band would miss it entirely.

Harmonics and Sidebands

A real bearing defect rarely produces energy at only the fundamental defect frequency. As the defect grows, harmonics appear at 2×, 3×, and higher multiples of the defect frequency. Inner race defects produce sidebands spaced at shaft speed around BPFI. Cage defects produce modulation sidebands around BPFO and BPFI at FTF spacing. A complete analysis requires monitoring not just the four fundamental frequencies but their first several harmonics and expected sideband patterns.

Where These Calculations Feed Into Monitoring Systems

The calculated defect frequencies serve as the input to both manual and automated diagnostic workflows. In a route-based vibration program, the analyst programs these frequencies into the analyzer for each measurement point. In a permanently installed online system, the frequencies are stored in the configuration database for each monitored bearing.

Modern IoT-based bearing monitoring platforms, such as Fault Ledger, automate this process by accepting bearing part numbers and computing defect frequencies from internal geometry databases. This eliminates manual calculation errors and ensures that every alarm threshold is referenced to the correct spectral location for each specific bearing.

The quality of the monitoring depends directly on the quality of the frequency calculation. A monitoring system watching for energy at 107 Hz when the actual BPFO is 104 Hz (due to slip or an incorrect pitch diameter value) may miss early-stage defects entirely. Getting the geometry right from the datasheet is the first and most important step.

Practical Tips for Datasheet Extraction

• Always use pitch diameter, not bore or OD. The most common calculation error is using the bore diameter or outer diameter instead of the pitch diameter. P_d is the diameter of the circle through the rolling element centers.
• Contact angle matters for angular contact and tapered roller bearings. For deep-groove ball bearings and cylindrical roller bearings, α = 0. For angular contact bearings, α is typically 15°, 25°, or 40°. For tapered rollers, the effective contact angle comes from the cup and cone geometry.
• Verify with published tables. SKF, NSK, Timken, and other manufacturers publish calculated defect frequency ratios (multiples of shaft speed) for their common bearing series. Cross-reference your hand calculation against these tables to catch errors.
• Use the inner ring ball count. Some bearings (double-row designs, for example) have different ball counts per row. Use the count for the row being monitored, not the total.

Building a Frequency Database

For any facility with more than a handful of monitored bearings, maintaining a database of bearing geometries and calculated defect frequencies is essential. Each bearing point should record the bearing part number, the four geometric parameters, the operating speed (or speed range), and the resulting four defect frequencies. When bearings are replaced with a different part number, the database must be updated — a new bearing with a different ball count or pitch diameter will have different defect frequencies, and the old alarm bands will be wrong.

Some condition monitoring platforms maintain cloud-hosted bearing databases with geometry for hundreds of thousands of part numbers from major manufacturers. Fault Ledger takes this approach, enabling field engineers to select a bearing by part number and automatically populate all defect frequency calculations without manual datasheet lookups. This reduces setup time from hours to minutes per machine and eliminates transcription errors.

Summary

Calculating bearing defect frequencies from a datasheet is straightforward once you extract the four geometric parameters: number of rolling elements, ball diameter, pitch diameter, and contact angle. Combined with shaft speed, these four values yield BPFO, BPFI, BSF, and FTF — the spectral fingerprints that every vibration-based monitoring system uses to detect and diagnose bearing faults. The three worked examples above demonstrate the process across different bearing sizes and shaft speeds: the SKF 6205 at 1,800 RPM (BPFO 107.2 Hz), the SKF 6312 at 1,800 RPM (BPFO 91.9 Hz), and the SKF 6316 at 1,500 RPM (BPFO 77.1 Hz). Get these numbers right, and your monitoring system has a solid foundation for catching faults early.

The way a vibration sensor is attached to a machine determines what that sensor can actually measure. A perfectly calibrated accelerometer with a 10 kHz bandwidth delivers accurate data only if the mechanical coupling between the sensor and the machine surface faithfully transmits vibrations across the full frequency range. Mounting method is not a secondary installation detail — it is a primary measurement parameter that directly affects diagnostic capability. This article compares the three common mounting methods for bearing vibration monitoring — stud mount, magnetic mount, and adhesive mount — with specific attention to frequency response, repeatability, and suitability for permanent IoT installations.

Why Mounting Method Affects Measurement

An accelerometer measures surface acceleration by detecting the force on an internal sensing element (piezoelectric crystal or MEMS structure). For the sensor to accurately represent the vibration at the measurement point, the sensor must move in lockstep with the surface. Any compliance, looseness, or damping in the mechanical coupling between the surface and the sensor acts as a low-pass filter, attenuating high-frequency content.

The coupling between sensor and surface forms a spring-mass-damper system. The mounted resonant frequency of this system determines the usable bandwidth. Below the mounted resonance, the sensor tracks the surface faithfully. Above it, the response drops off rapidly. A stud mount produces the stiffest coupling and the highest mounted resonance. A magnet mount introduces an air gap and magnetic compliance that lowers the resonance. A thick adhesive layer adds its own compliance. The practical consequence: the same sensor on the same bearing housing can have a usable bandwidth of 6 kHz with a stud mount, 2 kHz with a magnet, or somewhere in between with adhesive, depending on the specifics.

Stud Mounting

How It Works

A flat spot is machined or ground on the bearing housing surface. A tapped hole (commonly M8 × 1.25 or 1/4-28 UNF) is drilled and tapped perpendicular to the surface. The accelerometer screws directly onto the stud, with a thin layer of silicone grease or coupling compound on the mating surfaces to fill microscopic irregularities and exclude air.

Frequency Response

Stud mounting provides the highest mounted resonant frequency — typically within 10–20% of the sensor manufacturer’s specification for the sensor’s own resonant frequency. For a sensor with a 25 kHz resonant frequency, a good stud mount preserves usable bandwidth to approximately 8–10 kHz (±3 dB). This is important for detecting high-frequency phenomena: early-stage bearing defects produce impulses with energy content extending above 5 kHz, and envelope analysis (demodulation) requires capturing this high-frequency carrier signal faithfully.

Repeatability

Stud mounting is the gold standard for repeatability. The sensor returns to exactly the same location and orientation every time it is installed. Torque specifications (typically 1.5–2 N·m for M8 studs) ensure consistent coupling stiffness. This matters for trending: if overall vibration at a bearing location is 2.1 mm/s today and 2.4 mm/s next month, you need confidence that the difference reflects a change in machine condition, not a change in sensor mounting. Stud mounting provides that confidence.

Limitations

The primary limitation is installation effort. Drilling and tapping a hole in a bearing housing requires the machine to be shut down (or at least stationary). Surface preparation must be done carefully — a non-perpendicular hole or a rough surface degrades coupling. On cast iron housings, tapping can be straightforward. On stainless steel or hardened housings, it requires proper tooling. Some facilities are reluctant to drill into equipment housings due to warranty concerns or contamination risk.

Best For

Permanent installations where maximum diagnostic capability is required. Critical machinery — turbines, large motors, compressors — where early detection of bearing defects justifies the installation cost. IoT monitoring systems designed for continuous high-frequency data capture benefit directly from stud-mounted sensors because the coupling supports the full bandwidth the sensor and data acquisition hardware can deliver. Fault Ledger recommends stud mounting for its permanently installed sensors precisely because direct coupling preserves the high-frequency content needed for both envelope analysis and forensic waveform capture.

Magnetic Mounting

How It Works

A strong rare-earth magnet (typically neodymium, NdFeB) is attached to the base of the accelerometer or integrated into a mounting pad. The magnet holds the sensor against any ferromagnetic surface — cast iron, carbon steel, or ferritic stainless steel. No surface preparation beyond cleaning is required. The sensor can be placed and removed in seconds.

Frequency Response

Magnetic mounting reduces usable bandwidth significantly. The air gap between the magnet face and the mounting surface (even with good surface contact, microscopic irregularities leave gaps), combined with the limited contact stiffness of the magnetic attraction, creates a spring-mass system with a mounted resonance typically between 2 kHz and 7 kHz, depending on the magnet pull force, sensor mass, and surface condition. For a flat-bottomed magnet on a smooth machined surface with strong pull force (20+ kg), the upper limit approaches 5–7 kHz. For a curved surface, a dirty surface, or a weaker magnet, the useful range may drop to 2 kHz or below.

This bandwidth reduction matters. BPFO for a 6205 bearing at 1,800 RPM is about 107 Hz — well within the magnetic mount range. But the impulsive energy from an early-stage spall extends to several kilohertz, and envelope analysis typically bandpass-filters in the 2–10 kHz range to isolate bearing defect impulses from lower-frequency structural vibration. If the magnetic mount rolls off above 3 kHz, the sensor cannot capture the high-frequency carrier that envelope analysis depends on, and early fault detection capability is compromised.

Repeatability

Moderate. The sensor can be placed on slightly different spots each time, at different orientations, with different surface contact quality. Studies have shown measurement variability of 2–6 dB at frequencies above 1 kHz between repeated magnetic mount placements on the same location. For route-based programs with monthly readings, this variability can obscure genuine trends — a 3 dB change may be a worsening bearing or just a different sensor placement.

Limitations

Non-ferromagnetic surfaces (aluminum housings, stainless steel 300-series, plastic or composite structures) cannot accommodate magnetic mounts. Vibration from the magnet-surface interface resonance can introduce spurious spectral energy that may be misinterpreted as a fault. In high-temperature environments, neodymium magnets lose pull force above 80–150°C (depending on grade), compromising coupling and potentially allowing the sensor to detach.

Best For

Route-based manual data collection where speed and convenience outweigh maximum diagnostic depth. Screening surveys on non-critical equipment. Temporary monitoring during commissioning or troubleshooting. Walk-around programs on large populations of similar machines where the goal is to identify which machines need further investigation, not to perform detailed diagnostics on every point.

Adhesive Mounting

How It Works

The sensor (or a thin mounting pad) is bonded to the machine surface with an adhesive. Common adhesives include cyanoacrylate (super glue), two-part epoxy, and industrial-grade acrylic adhesives. The surface must be clean, dry, and free of oil or paint. Cyanoacrylate provides a thin, stiff bond line; epoxy provides a stronger structural bond but may introduce a thicker, more compliant adhesive layer.

Frequency Response

Adhesive mounting can approach stud-mount performance if the adhesive layer is thin and stiff. Cyanoacrylate bonds, which cure to a rigid thin film, typically preserve bandwidth to 5–8 kHz — close to stud-mount performance. Thicker epoxy bonds (above 0.1 mm) introduce more compliance and reduce the mounted resonance. The key parameter is bond-line thickness: thinner is stiffer, which means higher mounted resonance and better high-frequency response.

A properly executed thin cyanoacrylate bond on a clean, flat surface provides 80–90% of stud-mount bandwidth. This makes adhesive mounting a practical alternative for permanent installations where drilling and tapping is not feasible.

Repeatability

Excellent for permanent installations — the sensor stays in exactly the same location with consistent coupling. For installations where the sensor may need to be removed and reattached (battery changes, calibration checks), repeatability depends on whether the adhesive bond can be cleanly renewed. Removing a cyanoacrylate bond typically requires acetone and scraping; re-bonding requires re-cleaning and re-curing.

Limitations

Surface preparation is critical and time-consuming. Oil, paint, rust, and surface coatings must be completely removed at the mounting point. In dirty industrial environments, maintaining a clean bond surface can be challenging. Some adhesives degrade in high temperatures or in the presence of solvents, oils, or moisture. Cyanoacrylate becomes brittle and can crack under thermal cycling. Two-part epoxies have better environmental resistance but take longer to cure. Environmental durability is the primary long-term concern for permanent outdoor or washdown installations.

Best For

Permanent installations on non-ferromagnetic surfaces where stud mounting is not possible. Lightweight sensors (MEMS accelerometers under 50 grams) where the adhesive bond can comfortably support the sensor mass under vibration loading. Situations where drilling and tapping is prohibited by facility rules or equipment warranty terms.

Frequency Response Comparison Table

The following approximate values assume a typical 50-gram industrial accelerometer with a 25 kHz sensor resonance:

• Stud mount: Usable bandwidth to 8,000–10,000 Hz. Mounted resonance 20,000–23,000 Hz.
• Thin adhesive (cyanoacrylate): Usable bandwidth to 5,000–8,000 Hz. Mounted resonance 12,000–18,000 Hz.
• Thick adhesive (epoxy, >0.2 mm): Usable bandwidth to 3,000–5,000 Hz. Mounted resonance 8,000–12,000 Hz.
• Flat magnet, good surface: Usable bandwidth to 3,000–5,000 Hz. Mounted resonance 5,000–8,000 Hz.
• Curved magnet or poor surface: Usable bandwidth to 1,500–2,500 Hz. Mounted resonance 3,000–5,000 Hz.

Implications for IoT Bearing Monitoring

Permanent IoT monitoring systems — sensors installed on a machine for months or years, reporting data continuously or on a scheduled basis — face a mounting decision at installation time that will affect every measurement for the life of the sensor. Unlike route-based programs where the analyst can switch to a stud mount for a detailed investigation, an IoT sensor delivers only what its mounting allows.

For systems designed to detect early-stage bearing defects through envelope analysis, the mounting must preserve high-frequency content — at minimum to 5 kHz, preferably to 10 kHz. This effectively rules out magnetic mounting for permanent installations and points toward stud or thin-adhesive mounting. Platforms like Fault Ledger that capture raw high-frequency waveforms for forensic analysis are particularly sensitive to mounting quality, because the forensic value of the captured data depends on faithful reproduction of the high-frequency impulse signatures that characterize specific failure modes.

For lower-criticality applications where the goal is detecting gross changes in overall vibration level — a significant imbalance, severe looseness, or a late-stage bearing failure — the mounting requirements are less stringent. Overall vibration metrics (velocity RMS in the 10–1,000 Hz range) are well within the bandwidth of any mounting method. A magnetic-mount IoT sensor can serve as an adequate screening tool for this purpose.

Practical Installation Recommendations

1. For critical bearings requiring early fault detection: Stud mount. Accept the installation cost. The diagnostic capability justifies it.
2. For permanent sensors on non-ferromagnetic surfaces: Thin cyanoacrylate adhesive on a clean, flat, prepared surface. Verify bond integrity periodically.
3. For temporary diagnostic investigations: Magnetic mount with the strongest available magnet on the cleanest available surface. Be aware of bandwidth limitations and interpret high-frequency data cautiously.
4. For large-scale screening of balance-of-plant equipment: Magnetic or adhesive mount is acceptable. The goal is detecting which machines need attention, not detailed diagnostics.
5. Always clean the surface regardless of mounting method. Oil, paint, and debris degrade coupling for all three approaches.

Conclusion

Mounting method is not a checkbox on an installation form — it is a measurement engineering decision that directly determines the frequency range, repeatability, and diagnostic value of every vibration reading the sensor produces. For bearing condition monitoring, where early defect detection depends on capturing high-frequency impulses, the coupling between sensor and surface is as important as the sensor itself. Choose stud mounting when you can, thin adhesive when you must, and magnetic mounting when convenience genuinely outweighs diagnostic depth. Whatever method you choose, understand its frequency response limitations and interpret the resulting data accordingly.

Bearing defects produce vibration signatures that are often buried beneath much stronger signals from shaft imbalance, gear meshing, and structural resonances. A raw FFT spectrum of a machine with a developing outer race spall may show no obvious peak at the expected BPFO frequency — the defect signal is simply too small relative to the dominant low-frequency vibration. Envelope analysis (also called amplitude demodulation or high-frequency resonance technique, HFRT) solves this problem by extracting the repetition rate of high-frequency impulses generated by defect impacts. It is one of the most powerful tools in bearing diagnostics, and understanding how it works is essential for anyone interpreting vibration data from bearing monitoring systems.

The Problem Envelope Analysis Solves

When a rolling element strikes a spall on a raceway, the impact produces a brief, broadband impulse — a short burst of energy spanning a wide frequency range, often from a few hundred hertz to well above 10 kHz. This impulse excites structural resonances in the bearing housing and sensor mount, producing a short burst of high-frequency ringing that decays quickly before the next rolling element arrives.

In the time domain, each impulse looks like a damped oscillation (a brief ring-down). The repetition rate of these impulses equals the bearing defect frequency — BPFO for an outer race fault, BPFI for an inner race fault, and so on. However, in a standard FFT of the raw signal, the defect frequency information is spread across a wide band of high frequencies rather than concentrated at a single low-frequency peak. The standard FFT shows energy at the structural resonance frequencies but does not clearly reveal the repetition rate. Meanwhile, the direct BPFO frequency component in the low-frequency region of the raw spectrum is often too weak to detect against the background of rotor-dynamic vibration.

Envelope analysis extracts the repetition rate from the high-frequency content, converting the periodic bursts of high-frequency energy into a clean low-frequency signal at the defect frequency.

Step-by-Step: How Envelope Analysis Works

Step 1: Acquire a Raw Time Waveform

The process starts with a high-frequency vibration measurement — a time-domain waveform sampled at a rate sufficient to capture the high-frequency structural resonance excited by the defect impacts. For most industrial bearings, this means sampling at 20 kHz or higher (supporting a Nyquist frequency of 10 kHz or above). The waveform must be long enough to contain many complete cycles of the defect frequency. For a BPFO of 107 Hz, a 1-second waveform contains approximately 107 impulse events — adequate for reliable demodulation.

Step 2: Bandpass Filter Around a Structural Resonance

The raw waveform contains energy at all frequencies: shaft speed harmonics, gear mesh, electrical noise, and the bearing defect impulses. The key step is to apply a bandpass filter that isolates a frequency band where the defect impulses dominate. This band is typically centered on a structural resonance of the bearing housing — often in the 2–10 kHz range — where the impulse energy is concentrated and the competing low-frequency vibration has little content.

Selecting the correct bandpass center frequency and bandwidth is the most critical engineering judgment in envelope analysis. A poorly chosen band may exclude the resonance where defect energy concentrates, or include interference from other sources (such as gear mesh harmonics). Experienced analysts identify the resonant response using an initial broadband spectrum and selecting the frequency region where impulsive energy is evident.

Typical bandpass settings:

• Center frequency: 2,000–10,000 Hz (depends on bearing size, housing geometry, sensor mount)
• Bandwidth: 500–5,000 Hz (narrower bands improve signal-to-noise ratio but risk excluding defect energy)
• Filter type: Butterworth or Chebyshev, 4th to 8th order

Step 3: Rectify the Filtered Signal (Full-Wave Rectification)

After bandpass filtering, the signal consists of bursts of high-frequency oscillation at the structural resonance frequency. Each burst corresponds to one defect impact. To extract the repetition rate, the next step is to take the absolute value of the filtered signal (full-wave rectification) or, equivalently, compute the analytic signal using the Hilbert transform and extract its magnitude (the envelope).

The Hilbert transform approach is standard in modern digital signal processing. Given the bandpass-filtered signal x(t), the analytic signal is:

z(t) = x(t) + j × H[x(t)]

where H[x(t)] is the Hilbert transform of x(t) and j is the imaginary unit. The envelope is the magnitude:

envelope(t) = |z(t)| = sqrt(x(t)² + H[x(t)]²)

The resulting envelope signal is a smooth, slowly varying function that traces the amplitude of the high-frequency bursts. It oscillates at the defect frequency — the repetition rate of the impulses.

Step 4: Low-Pass Filter the Envelope

The raw envelope may contain residual high-frequency content from incomplete demodulation. A low-pass filter (cutoff typically 500–1,000 Hz, well above the highest expected defect frequency) cleans up the envelope signal. This step is optional in some implementations but improves the clarity of the final envelope spectrum.

Step 5: Compute the FFT of the Envelope

The final step is to compute the FFT of the envelope signal. This envelope spectrum displays peaks at the frequencies corresponding to the repetition rates of the impulses — that is, at the bearing defect frequencies and their harmonics. A peak at BPFO with harmonics at 2× BPFO and 3× BPFO clearly indicates an outer race defect. A peak at BPFI with sidebands at ± shaft speed indicates an inner race defect.

The envelope spectrum is dramatically cleaner than the raw FFT spectrum for bearing defect identification. The dominant shaft-speed harmonics, gear mesh frequencies, and other low-frequency content have been removed by the bandpass filter in Step 2. What remains is purely the repetition pattern of the defect impacts.

Why Envelope Analysis Detects Faults Earlier

A developing bearing defect — a microscopic spall a few hundred micrometers across — produces impulses with very small energy relative to the overall machine vibration. In the raw spectrum, the BPFO component might be 40–60 dB below the dominant 1× shaft-speed peak. It is undetectable against the noise floor.

But in the high-frequency band (say, 3–8 kHz), the machine produces relatively little vibration. The defect impulses excite the structural resonance in this band and temporarily dominate the signal. The signal-to-noise ratio of the defect signature is much higher in the high-frequency band than in the low-frequency raw spectrum. By bandpass filtering into this band and demodulating, envelope analysis exploits this frequency-domain signal-to-noise advantage to reveal defects that are invisible in the raw FFT.

Practical experience shows that envelope analysis can detect bearing defects 2–6 months earlier than raw spectral analysis, depending on machine speed, load, and bearing type. For condition-based maintenance programs, this additional lead time is the difference between a planned bearing replacement during a scheduled outage and an unplanned failure that shuts down a production line.

Requirements for Effective Envelope Analysis

Sufficient Sampling Rate

The sensor and data acquisition system must capture the high-frequency content that envelope analysis depends on. If the structural resonance excited by defect impacts is at 5 kHz, the system must sample at 10 kHz or higher (Nyquist criterion), and the sensor mounting must faithfully transmit vibration at that frequency. As discussed in detail in our article on sensor mounting methods, stud mounting or thin-adhesive mounting is necessary to preserve the high-frequency bandwidth that makes envelope analysis effective.

Sensor Bandwidth

The accelerometer must have a flat frequency response extending to at least 5 kHz, preferably 10 kHz. Most industrial piezoelectric accelerometers meet this requirement easily. MEMS accelerometers vary widely — consumer-grade MEMS devices may roll off above 1–3 kHz, while industrial MEMS sensors extend to 5–10 kHz. Systems like Fault Ledger that are designed specifically for bearing diagnostics select sensors and sampling rates to ensure adequate high-frequency capture for envelope analysis, typically sampling at 25.6 kHz or higher to support demodulation bands up to 10 kHz.

Waveform Capture

Envelope analysis requires the raw time-domain waveform, not just pre-computed spectral summary data. Some low-cost IoT vibration sensors compute overall vibration level (RMS velocity) or a coarse FFT on-board and transmit only summary statistics. These cannot support envelope analysis because the high-frequency time-domain information has been discarded. Effective envelope analysis requires either on-board DSP that performs the demodulation locally or transmission of the raw waveform to a cloud or edge platform for processing.

Common Pitfalls

Wrong Bandpass Selection

If the bandpass filter is centered on a frequency where gear mesh or electrical noise dominates instead of bearing defect impulses, the envelope spectrum will show gear mesh frequency or electrical line frequency instead of defect frequencies. The analyst must identify the frequency band where defect impulse energy is concentrated — this requires examining the raw spectrum for evidence of impulsive excitation (broadband humps or raised noise floor near structural resonances).

Insufficient Spectral Resolution

The envelope spectrum must have sufficient frequency resolution to separate defect frequencies from nearby harmonics of shaft speed. For a BPFO of 107 Hz and a shaft speed of 30 Hz (3.57× shaft speed), the nearest shaft harmonic is 3× (90 Hz) or 4× (120 Hz). A frequency resolution of 1 Hz or better is adequate. But for slow-speed machinery (below 100 RPM), defect frequencies may be below 10 Hz and closely spaced, requiring resolutions of 0.1 Hz or better — which demands waveform lengths of 10 seconds or more.

Confusing Defect Frequencies with Other Sources

Not every peak in the envelope spectrum is a bearing defect. Periodic impacts from other sources — loose bolts, rubbing seals, cavitation — can produce envelope spectrum peaks. Confirmation requires matching peaks to calculated defect frequencies for the specific bearing geometry, checking for harmonics (2×, 3× the defect frequency), and looking for expected sideband patterns (shaft-speed sidebands around BPFI for inner race defects).

Envelope Analysis in IoT Monitoring Architectures

For permanently installed IoT bearing monitoring systems, envelope analysis can be implemented either at the edge (on the sensor node or gateway) or in the cloud. Edge processing reduces data transmission requirements — only the envelope spectrum or demodulated waveform needs to be sent, not the full high-frequency raw waveform. Cloud processing allows more flexible algorithm tuning and reprocessing of historical data with updated parameters.

Some architectures combine both approaches: the edge performs real-time envelope analysis for immediate alarming, while the full raw waveform is captured periodically or on trigger and uploaded for detailed cloud-based diagnostics. Fault Ledger captures and stores raw high-frequency waveforms alongside processed envelope spectra, enabling both automated fault detection and after-the-fact forensic analysis when the specific failure mode or root cause needs to be determined.

Conclusion

Envelope analysis transforms raw vibration data into bearing-specific diagnostic information by extracting the repetition rate of high-frequency defect impulses. The technique — bandpass filter, demodulate (Hilbert transform), FFT — is conceptually simple but demands careful parameter selection and adequate measurement hardware: sufficient sampling rate, sensor bandwidth, and mechanical coupling quality. When implemented correctly, it detects bearing defects months earlier than raw spectral analysis, giving maintenance teams the lead time to plan repairs rather than react to failures. For any serious bearing monitoring program, envelope analysis is not optional — it is foundational.

Rolling-element bearings fail. Even under ideal conditions, the cyclic contact stresses in a loaded bearing eventually cause subsurface fatigue cracks that propagate to the raceway surface and form spalls. But most bearings never reach their calculated fatigue life — they fail prematurely due to contamination, improper installation, inadequate lubrication, or operating conditions that exceed their design envelope. Understanding the common failure modes, their root causes, and their vibration signatures is essential for both failure prevention and accurate diagnosis when a bearing does deteriorate.

Subsurface Fatigue (Spalling)

Mechanism

Subsurface fatigue is the classical bearing failure mode — the one that the L10 life calculation describes. Repeated Hertzian contact stress between rolling elements and raceways creates a cyclic shear stress field below the surface (maximum shear stress occurs at a depth of approximately 0.5× the contact half-width, typically 0.1–0.5 mm below the surface for most industrial bearings). Over millions of stress cycles, micro-cracks nucleate at material inclusions or carbide particles and propagate parallel to the surface. When a crack network reaches the surface, a piece of material breaks away, forming a pit or spall.

The initial spall is typically small — a few hundred micrometers to a few millimeters across. It grows with continued operation as the exposed edges of the spall act as stress concentrators, accelerating crack propagation. Left unchecked, the spall expands around the raceway until the bearing produces severe vibration, elevated temperature, and eventual seizure.

Vibration Signature

Early-stage spalling produces sharp, periodic impulses as each rolling element crosses the spall. These impulses appear in the time waveform as brief, high-amplitude spikes at the bearing defect frequency (BPFO for outer race spalling, BPFI for inner race). In the frequency domain:

• Envelope spectrum shows clear peaks at BPFO (or BPFI) and harmonics (2×, 3×, 4×)
• Raw spectrum may show increased broadband energy in the 1–10 kHz range (the structural resonance band excited by the impulses)
• As the spall grows, the defect frequency harmonics increase in number and amplitude, and the time waveform shows a rising crest factor (peak/RMS ratio)
• Late-stage spalling produces a noisy, irregular waveform with elevated overall vibration velocity

Root Cause

Normal fatigue is inherent to bearing operation and is the expected end-of-life mechanism. Premature fatigue (well before L10 life) indicates excessive load, inadequate lubrication, or material quality issues. Overloading compresses the fatigue life exponentially — doubling the radial load reduces L10 life by approximately a factor of eight for ball bearings (the load-life exponent is 3).

Brinelling and False Brinelling

True Brinelling

Brinelling is permanent indentation of a raceway caused by static overload or shock loading. When a stationary bearing receives an impact force that exceeds the elastic limit of the raceway material, the rolling elements press permanent dents into the raceway. These dents are spaced at the rolling element pitch — one dent per ball position. The name comes from the similarity to a Brinell hardness test indent.

Common causes include rough handling during installation (dropping a bearing or driving it onto a shaft with hammer blows transmitted through the rolling elements), transportation vibration of heavy equipment (machinery shipped by truck or rail with the shaft locked in one position), and shock loads during operation (water hammer in pumps, sudden coupling engagement).

False Brinelling

False brinelling produces similar-looking raceway indentations but through a different mechanism: fretting corrosion from small oscillatory motion while the bearing is stationary or rotating very slowly. When a machine sits idle and is subjected to external vibration (from nearby operating equipment, for example), the rolling elements oscillate microscopically against the raceways. This micro-motion wears away the lubricant film and creates small, oxidized wear marks at each ball contact point.

False brinelling is common in standby equipment, spare pumps, transport vehicles, and any machinery that sits for extended periods in a vibrating environment.

Vibration Signature

Both true and false brinelling produce a series of evenly spaced surface irregularities on the raceway. As the shaft rotates and rolling elements traverse these dents, the vibration signature includes:

• Elevated vibration at BPFO (outer race) or BPFI (inner race) harmonics, similar to spalling but often with broader, less sharp spectral peaks
• Increased overall vibration level, particularly in the velocity range (10–1,000 Hz)
• In severe cases, audible rumbling or growling that is evident immediately upon startup
• The pattern is typically uniform around the raceway (multiple evenly spaced dents), which may produce a spectrum dominated by higher harmonics of the defect frequency rather than the fundamental

Contamination

Mechanism

Particle contamination — hard particles (sand, metal chips, scale) or soft particles (fibers, rubber fragments) entering the bearing — is the single most common cause of premature bearing failure. Industry studies consistently attribute 20–30% of all bearing failures to contamination. Particles enter through inadequate sealing, contaminated lubricant, or during installation (dirty work practices, contaminated grease in the supply chain).

Hard particles larger than the minimum oil film thickness (typically 0.2–2 μm for EHL contacts) are overrolled by the rolling elements and indent the raceways. Each indent acts as a stress concentrator that accelerates subsurface fatigue. The effect is cumulative: thousands of small dents distributed randomly across the raceways reduce the bearing fatigue life by factors of 2–10 or more, depending on contamination severity.

Vibration Signature

Contamination damage produces a distinctive vibration signature that differs from localized spalling:

• Elevated broadband vibration floor (raised noise floor across the spectrum) rather than discrete peaks at defect frequencies
• Increased high-frequency energy (acceleration domain, above 1 kHz), reflecting the many small surface irregularities
• Kurtosis of the time waveform increases as contamination worsens (more frequent impulsive events from overrolling particles and dents)
• In early stages, overall velocity may remain near baseline while high-frequency metrics (HFD, acceleration envelope RMS) rise — this is because the individual dents are too small to produce significant low-frequency vibration but collectively increase high-frequency impulsiveness
• As contamination damage progresses, the multiple dents eventually merge into larger spalls, and the signature transitions to resemble classical fatigue spalling

Distinguishing contamination-induced distributed damage from early-stage localized spalling is important for root cause analysis. Contamination suggests a sealing or lubrication supply problem; localized spalling suggests overloading, misalignment, or normal end-of-life fatigue. Vibration monitoring systems designed for forensic root cause determination, such as Fault Ledger, capture high-resolution waveform data that preserves the statistical character of the vibration (kurtosis, crest factor, and impulsive event distribution), enabling analysts to distinguish distributed contamination damage from localized defects during post-failure investigation.

Misalignment

Mechanism

Bearing misalignment occurs when the shaft axis and the bearing bore axis are not concentric (radial misalignment) or not parallel (angular misalignment). This forces the rolling elements to traverse a non-ideal load distribution, generating axial forces in bearings designed for radial loads, uneven contact stresses, and cage loading.

Common causes include imprecise shaft machining or housing boring, thermal growth that changes alignment as the machine warms from ambient to operating temperature, soft foot (uneven mounting surfaces that distort the housing when bolts are tightened), and improper shimming or coupling alignment during installation.

Vibration Signature

Misalignment produces a distinctive vibration pattern:

• Axial vibration dominance: Misaligned bearings generate significantly elevated axial (parallel to shaft) vibration relative to radial vibration. A 2:1 or greater ratio of axial to radial vibration amplitude at shaft frequency is a strong misalignment indicator.
• 2× shaft speed: Angular misalignment produces a strong 2× RPM component, often dominant over the 1× component. The once-per-revolution variation in contact conditions creates a twice-per-revolution vibration response.
• Harmonic series at shaft speed: Severe misalignment generates a series of shaft-speed harmonics (1×, 2×, 3×, 4× RPM and higher), with 2× typically dominant.
• Bearing defect frequency modulation: Misalignment alters the load distribution around the raceway, causing amplitude modulation of any existing defect signatures. This appears as sidebands around bearing defect frequencies spaced at shaft speed.

Consequences for Bearing Life

Misalignment does not cause immediate catastrophic failure, but it accelerates fatigue by creating non-uniform contact stress distribution. The most heavily loaded region of the raceway sees stresses that exceed the design basis, while other regions are under-loaded. The net effect is a reduction in fatigue life proportional to the severity of misalignment. Industry data suggests that 0.001 inch/inch of angular misalignment can reduce bearing life by 30–50%.

Other Failure Modes

Lubrication Failure

Inadequate lubrication — wrong viscosity, insufficient quantity, degraded grease, or excessive relubrication interval — is a contributing factor in an estimated 40–50% of bearing failures. Without an adequate elastohydrodynamic (EHL) lubricant film, metal-to-metal contact between rolling elements and raceways causes adhesive wear, surface distress, and accelerated fatigue. The vibration signature of lubrication-related distress includes elevated high-frequency energy (often detected with ultrasonic techniques in the 25–50 kHz range), increased bearing temperature, and eventually the onset of spalling signatures as the surface degrades.

Electrical Erosion (Fluting)

Stray electrical currents passing through bearing rolling contacts — common in variable-frequency drive (VFD) applications — cause electrical discharge machining (EDM) of the raceways. The damage appears as a pattern of closely spaced pits arranged in circumferential bands (fluting). The vibration signature includes elevated broadband energy and, as fluting progresses, peaks at BPFO and BPFI with a characteristic washboard pattern on the raceways.

Corrosion

Moisture ingress (from process leaks, washdown, condensation) causes rust and oxidation on raceway surfaces. Corroded surfaces create surface roughness that accelerates fatigue and increases vibration. The signature is similar to contamination — elevated broadband noise floor with increased high-frequency content.

Matching Failure Mode to Vibration Signature: Why It Matters

Detecting that a bearing is deteriorating is only the first step. Effective root cause analysis requires identifying which failure mode is responsible so that corrective action addresses the underlying problem, not just the symptom. Replacing a bearing that failed from contamination without fixing the seal that allowed particle ingress guarantees a repeat failure. Replacing a bearing that failed from misalignment without correcting the shaft alignment wastes the new bearing.

This is where the depth of the vibration data matters. Simple overall vibration level (a single RMS velocity number) can detect that something is wrong, but it cannot distinguish contamination from fatigue from misalignment. Frequency-domain analysis with defect frequency identification can detect and classify bearing defects. Full waveform capture with statistical analysis (kurtosis, crest factor, impulse event characterization) provides the deepest diagnostic insight.

Fault Ledger approaches this as a forensic evidence problem: by capturing and preserving high-resolution vibration waveforms throughout the bearing deterioration process, the system creates a time-stamped record of how the fault developed. This forensic record allows reliability engineers to trace a failure back to its root cause — distinguishing, for example, a contamination-initiated fatigue failure from a misalignment-initiated one — by examining the temporal progression of the vibration signature from first detection to final failure.

Conclusion

Bearing failures are not random events — they follow characteristic patterns determined by the specific failure mechanism. Fatigue produces localized spalls with periodic impulses at defect frequencies. Brinelling produces evenly spaced raceway dents from static overload or fretting. Contamination produces distributed surface damage with elevated broadband noise. Misalignment produces axial vibration dominance and strong 2× shaft-speed harmonics. Recognizing these patterns in vibration data enables both timely detection and accurate root cause identification, closing the loop between condition monitoring and reliability improvement.

Every digital vibration monitoring system converts the continuous analog signal from an accelerometer into discrete samples at a fixed rate. That rate — the sampling frequency — determines the maximum vibration frequency the system can measure. Choose too low a sampling rate and the system is physically incapable of detecting the high-frequency signatures that early-stage bearing defects produce. Choose an unnecessarily high rate and you generate massive data volumes that stress storage, bandwidth, and battery life without adding diagnostic value. This article explains the fundamental relationship between sampling rate and measurable frequency content, applies it to bearing monitoring for different machine speeds, and discusses the practical trade-offs that drive sampling rate selection in IoT sensor architectures.

The Nyquist-Shannon Sampling Theorem

The Nyquist-Shannon sampling theorem states that a continuous signal can be perfectly reconstructed from its samples if the sampling rate is at least twice the highest frequency component present in the signal. This minimum rate is called the Nyquist rate. The maximum frequency that can be represented at a given sampling rate is the Nyquist frequency, equal to half the sampling rate:

f_Nyquist = f_sample / 2

For example, a system sampling at 20,000 samples per second (20 kS/s) can represent frequencies up to 10,000 Hz. A system sampling at 1,000 S/s can represent frequencies up to only 500 Hz.

Aliasing: What Happens Below the Nyquist Rate

When a signal contains frequency content above the Nyquist frequency, those high-frequency components do not simply disappear from the digital data. They are aliased — folded back into the measurable frequency range and appear as false spectral components at incorrect frequencies. A 7,000 Hz vibration component sampled at 10 kS/s (Nyquist = 5,000 Hz) appears in the digital spectrum at 3,000 Hz (10,000 – 7,000 = 3,000 Hz). This aliased peak looks identical to a genuine 3,000 Hz signal, and there is no way to distinguish it from real content after sampling.

Aliasing is not a minor nuisance — it produces false information. An aliased bearing defect frequency could masquerade as a gear mesh harmonic, or vice versa. An aliased structural resonance could create a phantom spectral peak that triggers false alarms. To prevent aliasing, every properly designed data acquisition system includes an anti-aliasing filter — an analog low-pass filter that attenuates signal content above the Nyquist frequency before the analog-to-digital converter samples the signal.

In practice, anti-aliasing filters are not perfectly sharp. They require a transition band to roll off from passband to stopband. A practical rule is that the usable analysis bandwidth is approximately 40% of the sampling rate (80% of Nyquist). A system sampling at 20 kS/s has a Nyquist frequency of 10 kHz but a usable analysis bandwidth of approximately 8 kHz after accounting for the anti-aliasing filter roll-off.

Frequency Requirements for Bearing Monitoring

What frequencies must a bearing monitoring system capture? The answer depends on the diagnostic technique being used.

Overall Vibration Level (Velocity RMS)

The ISO 10816 / ISO 20816 standard for evaluating machine vibration severity uses velocity RMS in the 10–1,000 Hz band. A sampling rate of 2,560 S/s (usable bandwidth ~1,000 Hz) is sufficient for this metric. Most low-cost IoT vibration sensors use this approach. It detects gross mechanical problems — severe imbalance, looseness, late-stage bearing failure — but cannot detect early-stage bearing defects.

Direct Spectral Analysis of Defect Frequencies

For a bearing with defect frequencies below 500 Hz (covering most bearings on machines running below approximately 3,000 RPM), the fundamental defect frequencies fall within the 10–1,000 Hz band. A 2,560 S/s rate captures these. However, the harmonics of defect frequencies — 2× BPFO, 3× BPFO, and higher — extend higher. For a BPFO of 107 Hz, 10 harmonics extend to 1,070 Hz. Higher harmonics at 15× or 20× BPFO (1,600–2,140 Hz) become important as defect severity grows. A sampling rate of 5,120 S/s (bandwidth ~2,000 Hz) captures these higher harmonics.

Envelope Analysis

Envelope analysis (amplitude demodulation) — the most powerful tool for early bearing defect detection — operates on the high-frequency structural resonance band, typically 2,000–10,000 Hz. To capture this band, the system must sample at 25,600 S/s or higher (usable bandwidth 8,000–10,000 Hz). This is a factor of 10 higher than the rate needed for simple overall vibration monitoring.

This sampling rate requirement is the central trade-off in IoT bearing monitoring sensor design. A sensor sampling at 25.6 kS/s for 1 second generates 25,600 samples — perhaps 50 kB of data at 16-bit resolution. A sensor sampling at 2.56 kS/s generates only 2,560 samples (5 kB). The 10× difference in data volume directly affects wireless transmission time, energy consumption (and therefore battery life), cloud storage costs, and processing load.

Ultrasonic / Stress Wave Monitoring

Some advanced monitoring techniques use ultrasonic frequencies (25–100 kHz and above) to detect lubrication breakdown and very early metal-to-metal contact. These require sampling rates of 100 kS/s or more and are typically limited to wired, permanently powered systems due to the extreme data rates involved.

Sampling Rate by Machine Speed

Bearing defect frequencies are proportional to shaft speed. Higher shaft speeds produce higher defect frequencies, requiring higher sampling rates. Lower shaft speeds produce lower defect frequencies that are easier to capture but require longer waveform records (more time) to accumulate enough cycles for reliable spectral analysis.

Low-Speed Machines (60–300 RPM)

Shaft frequency: 1–5 Hz. Typical BPFO: 5–25 Hz. Envelope analysis band: 500–5,000 Hz. Minimum sampling rate for envelope analysis: 12,800 S/s. The challenge at low speed is not the sampling rate but the record length: at 5 Hz BPFO, a 1-second record contains only 5 defect cycles. Reliable spectral analysis requires 10–20 seconds of data, generating 128,000–256,000 samples per acquisition at 12.8 kS/s.

Medium-Speed Machines (300–3,600 RPM)

Shaft frequency: 5–60 Hz. Typical BPFO: 25–320 Hz. Envelope analysis band: 2,000–10,000 Hz. Minimum sampling rate for envelope analysis: 25,600 S/s. This covers the majority of industrial machinery — motors, pumps, fans, compressors. A 1-second record at 25.6 kS/s provides adequate frequency resolution (1 Hz) and sufficient defect cycles for reliable detection.

High-Speed Machines (3,600–60,000 RPM)

Shaft frequency: 60–1,000 Hz. Typical BPFO: 320–5,000 Hz. Envelope analysis band: 5,000–20,000 Hz or higher. Minimum sampling rate for envelope analysis: 51,200 S/s or higher. High-speed spindles, turbomolecular pumps, and dental handpieces push defect frequencies into the kilohertz range, requiring correspondingly high sampling rates. These applications often use specialized high-bandwidth systems rather than general-purpose IoT sensors.

The IoT Sensor Trade-Off

Battery-powered wireless vibration sensors must balance diagnostic capability against energy budget. The energy cost of a vibration measurement is dominated by two factors: the data acquisition itself (powering the sensor and ADC) and the wireless transmission of the data.

Consider a concrete example: a sensor measuring a 1-second waveform every 15 minutes, 24 hours a day.

• At 2,560 S/s: 5 kB per acquisition × 96 acquisitions/day = 480 kB/day
• At 25,600 S/s: 50 kB per acquisition × 96 acquisitions/day = 4,800 kB/day (4.8 MB/day)

The 10× data volume difference translates to approximately 10× longer transmission time and 5–8× more energy per measurement cycle (ADC power also increases with sampling rate). For a sensor running on a lithium battery with a 5-year target life, this difference can mean choosing between a AA-sized battery and a D-sized battery — or between quarterly battery changes and annual changes.

Some IoT sensor architectures address this trade-off by using adaptive sampling: the sensor normally operates at a low sampling rate (2.56 kS/s) for overall vibration monitoring and periodically switches to a high rate (25.6 kS/s) for detailed spectral and envelope analysis. This reduces the average energy consumption while preserving the ability to perform full diagnostics on a scheduled or triggered basis.

Other platforms, like Fault Ledger, prioritize high-fidelity capture for every measurement, using sampling rates of 25.6 kS/s or higher as the standard operating mode. This approach ensures that every data record supports full envelope analysis and waveform-level forensic examination, at the cost of higher per-measurement energy consumption — a trade-off justified for critical bearing applications where early detection and failure evidence quality are paramount.

Spectral Resolution and Record Length

Sampling rate determines the frequency range, but record length (the duration of the captured waveform) determines frequency resolution:

Δf = 1 / T

where T is the record length in seconds and Δf is the frequency resolution in Hz. A 1-second record provides 1 Hz resolution. A 0.1-second record provides only 10 Hz resolution — insufficient to separate a BPFO of 107 Hz from a shaft harmonic at 120 Hz.

For slow-speed bearings with closely spaced defect and shaft frequencies, high frequency resolution requires long records. A machine running at 60 RPM (1 Hz shaft frequency) with a BPFO of 3.57 Hz needs at least 0.5 Hz resolution to separate BPFO from harmonics of shaft speed (3 Hz and 4 Hz). This requires a 2-second record minimum. For reliable detection with clear spectral separation, 5–10 seconds is typical.

Total data per acquisition = sampling rate × record length × bytes per sample. At 25,600 S/s × 10 seconds × 2 bytes = 512 kB — a significant volume for a battery-powered wireless sensor.

Practical Guidelines for Sampling Rate Selection

1. If you only need overall vibration severity (ISO 20816 compliance): 2,560 S/s is sufficient. Usable bandwidth ~1,000 Hz. Lowest power, smallest data volumes.
2. If you need direct spectral analysis of defect frequencies and their harmonics: 5,120–10,240 S/s. Usable bandwidth 2,000–4,000 Hz. Moderate power and data requirements.
3. If you need envelope analysis for early defect detection: 25,600 S/s or higher. Usable bandwidth 8,000–10,000 Hz. This is the minimum for serious bearing diagnostics. Higher power and data requirements, but enables 2–6 months additional warning time before failure.
4. If you need ultrasonic monitoring for lubrication analysis: 102,400 S/s or higher. Typically limited to wired, permanently powered installations.
5. Match record length to machine speed: Ensure the record contains at least 10–15 full cycles of the lowest defect frequency of interest. For a BPFO of 10 Hz, this means at least 1–1.5 seconds.

Conclusion

Sampling rate is not a specification to gloss over when selecting a bearing vibration monitoring system. It determines the frequency ceiling of everything the system can see. Below the Nyquist frequency, the system measures faithfully. Above it, information is either lost (filtered out) or corrupted (aliased into false peaks). For bearing diagnostics, where early defect detection depends on capturing high-frequency impulse energy for envelope analysis, the required sampling rate is typically 25.6 kS/s — ten times higher than what simple overall vibration monitoring requires. Platforms built for high-frequency capture, such as Fault Ledger, make this sampling rate the default precisely because the diagnostic techniques that matter most for bearing health — envelope analysis and waveform-level forensics — depend on it. Understanding this trade-off — and choosing a sampling rate that matches your diagnostic objectives — is a fundamental step in designing an effective bearing monitoring program.

The phrase “bearing condition monitoring” covers two fundamentally different engineering objectives. Predictive monitoring aims to detect bearing deterioration early enough to schedule a repair before failure. Forensic monitoring aims to capture detailed evidence of how and why a bearing failed, producing a technical record that supports root cause analysis, warranty claims, supplier accountability, and reliability improvement programs. These two objectives overlap in their use of vibration sensors, but they diverge in architecture, data strategy, and what the data is ultimately used for. This article examines both approaches, where they complement each other, and where the differences in design philosophy lead to genuinely different system architectures.

Predictive Bearing Monitoring

Objective

The goal of predictive monitoring is actionable early warning: detect that a bearing is deteriorating, estimate remaining useful life (if possible), and alert maintenance personnel in time to schedule a repair during a planned outage. The value proposition is avoiding unplanned downtime. A bearing replacement that costs $500 in parts and labor during a scheduled shutdown might cost $50,000 or more in lost production if it triggers an unplanned outage.

Architecture

Predictive systems are optimized for detection sensitivity and alarm reliability. The typical architecture includes:

• Periodic measurement: Vibration data is acquired at regular intervals — typically every 15 minutes to every 4 hours, depending on machine criticality and bearing speed. Between measurements, the sensor sleeps to conserve power.
• On-board processing: The sensor computes summary metrics on-board: overall RMS velocity, peak acceleration, crest factor, kurtosis, and sometimes an envelope spectrum. Only these compressed results are transmitted wirelessly, reducing data volume by 100–1,000× compared to raw waveform transmission.
• Threshold-based alarms: The cloud platform compares summary metrics against pre-configured thresholds (often based on ISO 10816/20816 severity levels or machine-specific baselines). When a metric exceeds the threshold, an alarm is raised.
• Trend analysis: Historical metric values are trended over time. A rising trend in envelope spectrum amplitude at BPFO, even if still below the alarm threshold, may trigger an advisory alert.
• Machine learning models: Some advanced systems use machine learning to model normal bearing behavior and detect anomalous metric patterns that may not trigger simple threshold alarms.

Data Strategy

Predictive systems favor data reduction. The raw time-domain waveform — which might be 50 kB per measurement — is processed into a handful of scalar metrics and a compressed spectrum (perhaps 500 bytes). This enables long battery life, low wireless bandwidth consumption, and minimal cloud storage cost. The trade-off: the raw waveform is discarded after on-board processing. If a failure occurs and an engineer wants to examine the waveform characteristics leading up to it, the data does not exist.

Strengths

• Cost-effective at scale — low data volumes enable large sensor populations on shared wireless infrastructure
• Long battery life (3–5+ years in many implementations)
• Proven detection capability for medium- and late-stage bearing defects
• Well-suited for fleet monitoring across hundreds or thousands of machines

Limitations

• On-board processing discards information that may be needed for root cause analysis
• Threshold-based alarms can produce false positives (environmental changes, load variations) and false negatives (slowly developing faults that stay below threshold)
• Post-failure analysis is limited to the summary metrics that were computed and stored — the detailed vibration character is not available
• Cannot answer “why did this bearing fail?” with the same confidence as a system that preserved the full waveform record

Forensic Bearing Monitoring

Objective

Forensic monitoring aims to build a complete, time-stamped evidence record of bearing condition throughout its operational life — or at least throughout the period of deterioration. The goal is not just to detect that a bearing is failing, but to capture sufficient technical evidence to determine the failure mode, identify the root cause, assign responsibility (was it a manufacturing defect, an installation error, a lubrication failure, an overload event?), and support continuous improvement of bearing selection, installation, and maintenance practices.

This objective is particularly important in industries where bearing failures have safety, regulatory, or contractual consequences: rail transport (axlebox bearings), wind energy (main shaft and gearbox bearings), marine propulsion, mining, and critical-process manufacturing.

Architecture

Forensic systems are optimized for data completeness and evidentiary integrity. The architecture differs from predictive systems in several key ways:

• High-frequency raw waveform capture: The system captures and stores the complete time-domain waveform at high sampling rates (25.6 kS/s or higher), not just summary metrics. Every impulse, every transient, every modulation pattern is preserved.
• Time-stamped data chain: Each measurement is immutably time-stamped, creating a chronological record that can be audited. This is essential for warranty claims and regulatory submissions where the integrity of the evidence chain matters.
• Longer record lengths: Forensic analysis may require waveforms of 2–10 seconds or more to capture sufficient statistical cycles of low-frequency defect patterns and modulation effects.
• Metadata capture: Operating conditions at the time of each measurement — speed, load, temperature, process state — are recorded alongside the vibration data. This context is essential for interpreting the vibration signatures correctly. A vibration peak that appears at full load but disappears at half load tells a different story than one that is load-independent.
• Secure data storage: The captured waveforms and metadata are stored in a tamper-evident format, often with cryptographic hashing, to ensure that the evidence has not been altered after collection. This is the “ledger” concept — an immutable record of bearing condition over time.

Fault Ledger is built around this forensic architecture. The system captures high-resolution vibration waveforms at every measurement interval, stores them with full operational context and time-stamped integrity, and makes the entire evidence chain available for post-event analysis. The name reflects the core concept: a fault ledger — an auditable record of bearing condition that serves as technical evidence for failure investigation.

Data Strategy

Forensic systems favor data preservation over data reduction. The raw waveform is the primary asset — it can be reprocessed with different algorithms, different bandpass settings, different envelope parameters at any time in the future. Summary metrics are derived from the waveform and used for alarming and trending, but they supplement the raw data rather than replacing it.

This data-first approach has storage and bandwidth implications. A 1-second waveform at 25.6 kS/s generates approximately 50 kB per measurement. At 96 measurements per day, that is 4.8 MB/day per sensor — manageable for modern cloud storage but significant for wireless bandwidth, especially over LoRaWAN or other LPWAN protocols. Forensic systems may use higher-bandwidth wireless links (Wi-Fi, cellular) or edge storage with periodic batch upload to manage this data volume.

Strengths

• Supports detailed root cause analysis after a failure event
• Provides evidence for warranty claims, regulatory compliance, and supplier accountability
• Raw waveform data can be reprocessed with improved algorithms as diagnostic techniques advance
• Enables distinction between failure modes (contamination vs. fatigue vs. misalignment) that summary metrics cannot differentiate
• Creates institutional knowledge: the failure evidence record feeds back into bearing selection, installation procedures, and maintenance practices

Limitations

• Higher data volumes require more wireless bandwidth, storage, and processing resources
• Higher per-sensor cost (more capable hardware, more data infrastructure)
• May require higher power consumption, limiting battery life or requiring wired power
• The value of forensic data is only realized when someone analyzes it — the organization needs the expertise and processes to use the evidence

Where the Two Approaches Overlap

Predictive and forensic monitoring are not mutually exclusive. In fact, a forensic system inherently provides predictive capability — the same waveform data that serves as failure evidence also supports trend analysis, threshold alarming, and envelope-based early detection. The difference is that the forensic system retains the raw data while the pure predictive system discards it.

The converse is not true: a predictive system that discards raw waveforms cannot retroactively perform forensic analysis. Once the waveform is reduced to a scalar metric, the information needed for failure mode identification is gone.

Some organizations implement a hybrid approach: predictive monitoring on most machines (cost-effective fleet coverage) with forensic monitoring on critical bearings where failure consequences are severe or where root cause evidence is needed for contractual or regulatory reasons.

Choosing Between Predictive and Forensic Architectures

The right approach depends on what question you need to answer:

If the primary question is “Is this bearing failing?”

A predictive system is sufficient. On-board-processed metrics with threshold alarms and trend analysis will detect bearing deterioration with adequate lead time for maintenance planning on most industrial machinery. This is the right choice for fleet monitoring of non-critical equipment where the goal is scheduling replacements efficiently.

If the primary question is “Why did this bearing fail?”

A forensic system is necessary. Root cause analysis requires examining the vibration characteristics in detail — the statistical distribution of impulses, the modulation patterns, the frequency evolution over time. These details exist in the raw waveform, not in summary metrics. This is the right choice for critical machinery where recurring failures indicate a systemic problem, or where failure evidence has contractual, warranty, or regulatory significance.

If the primary question is “How can we prevent this failure from recurring?”

Forensic evidence feeds reliability engineering. Without evidence of how the bearing failed, the reliability engineer is guessing at root cause and corrective action. With a detailed vibration record showing the progression from first detectable anomaly to failure, the engineer can determine whether the root cause was contamination (improve sealing), misalignment (improve installation procedures), overloading (redesign the application), lubrication (change relubrication interval), or manufacturing defect (engage the bearing supplier). Fault Ledger was designed specifically to serve this reliability engineering feedback loop, providing the evidentiary record that turns bearing failures from recurring frustrations into opportunities for systematic improvement.

Architectural Differences in Practice

The following table summarizes how the two philosophies lead to different design decisions across the system:

• Sampling rate: Predictive: 2,560–10,240 S/s (sufficient for basic spectral analysis). Forensic: 25,600+ S/s (supports envelope analysis and waveform-level diagnostics).
• Data transmitted: Predictive: summary metrics (tens to hundreds of bytes). Forensic: raw waveforms (tens to hundreds of kilobytes).
• Storage per sensor-year: Predictive: 1–50 MB. Forensic: 500 MB–5 GB.
• Battery life (typical): Predictive: 3–7 years. Forensic: 1–3 years (or wired power).
• Post-failure analysis capability: Predictive: limited to stored metrics and trends. Forensic: full waveform reprocessing and failure mode classification.
• Best suited for: Predictive: fleet monitoring, non-critical equipment, maintenance scheduling. Forensic: critical machinery, root cause investigation, warranty evidence, regulatory compliance.

The Trend Toward Convergence

As edge computing capabilities improve and wireless bandwidth increases, the distinction between predictive and forensic architectures is gradually narrowing. Modern IoT sensor nodes with sufficient processing power can perform on-board envelope analysis (providing predictive detection capability) while simultaneously storing the raw waveform to local flash memory for periodic upload (preserving forensic evidence). Advances in low-power wide-area network (LPWAN) protocols and the increasing availability of industrial Wi-Fi and 5G reduce the bandwidth constraint that historically forced the choice between data reduction and data preservation.

The economic logic is also shifting. Cloud storage costs continue to decline, making the storage of raw waveforms increasingly affordable. And the cost of a single undiagnosed recurring bearing failure — repeated replacements, production losses, potential safety incidents — often exceeds the incremental cost of forensic data capture across an entire fleet of sensors.

Conclusion

Predictive and forensic bearing monitoring are not competing philosophies — they are different tools for different jobs. Predictive monitoring answers “when will this bearing need attention?” Forensic monitoring answers “why did this bearing fail, and how do we prevent it from happening again?” The choice between them — or the decision to implement both — depends on the consequences of failure, the need for root cause evidence, and the organization’s commitment to using failure data for continuous reliability improvement. As sensor and data infrastructure costs continue to decline, the case for capturing and preserving the full vibration record grows stronger. The most effective bearing monitoring programs will be those that detect faults early and explain them thoroughly.

Marine environments are among the most demanding for any electronic instrumentation. Propulsion systems, shaft bearings, auxiliary machinery, and deck equipment all operate under conditions that rapidly degrade standard industrial sensors: saltwater corrosion, continuous hull vibration, humidity cycles that condense moisture inside enclosures, limited cable routing paths, and the logistical reality that the asset may be hundreds of miles offshore when a fault occurs. Each of these factors presents a distinct engineering challenge for bearing condition monitoring.

Why Saltwater Corrosion Is a First-Order Problem

316L stainless steel — the marine-grade standard — contains 2–3% molybdenum in addition to the chromium-nickel alloy of 304 stainless. The molybdenum dramatically improves resistance to chloride pitting, which is the dominant corrosion mechanism in marine environments. Sensors housed in 304 stainless or aluminum will develop pitting corrosion within months in full saltwater spray exposure. Pitting is insidious: the exterior surface may look acceptable while the wall thickness is being consumed from within, eventually breaching the IP seal.

Connector corrosion is equally critical. Submerged or spray-exposed electrical connectors that use tin or silver plating develop galvanic corrosion at the contact interface. Gold-plated contacts over a nickel substrate are standard for long-term saltwater reliability. Any monitoring system deployed in a marine environment should have its IP rating tested under saltwater immersion, not just freshwater — IP67 and IP68 ratings are typically established with freshwater and may not indicate adequate saltwater protection.

Hull Vibration: Signal-to-Noise Challenges

Ship hulls transmit broadband vibration from propellers, engines, auxiliary machinery, and wave loading. A bearing sensor mounted on a marine propulsion gearbox is picking up not just the bearing vibration of interest but also structural resonances from the hull, interference from adjacent machinery, and low-frequency motion from sea state. This high ambient noise floor raises the minimum detectable bearing defect severity — early-stage faults that would be clearly visible on a quiet land-based machine may be buried in the noise on a vessel at sea.

Sensor placement strategy becomes critical. Rigid, direct mounting on the bearing housing (rather than on a bracket or structural member away from the bearing) maximizes signal amplitude relative to structural noise. Short, direct vibration paths from bearing to sensor are essential.

Moisture Ingress and Thermal Cycling

Marine enclosures experience daily thermal cycles as machinery heats up and cools down, combined with high ambient humidity. Each thermal cycle creates a “breathing” effect in enclosures with imperfect seals — warm air expands out during operation, and as the system cools, slightly humid external air is drawn in. Over hundreds of cycles, even trace moisture accumulates inside the enclosure, eventually condensing on electronics and causing failure.

Reliable marine sensor design addresses this in three ways: robust primary sealing (IP68 with marine-grade gaskets), dessicant material inside the enclosure to absorb residual moisture, and conformal coating on electronics to protect against condensation that does occur. Potted electronics — fully encapsulated in epoxy — offer the most reliable long-term moisture resistance but sacrifice repairability.

Cable Routing Constraints

Running signal cables from bearing sensors to a monitoring system is straightforward in a land-based industrial facility. On a vessel, cable routing through machinery spaces, bulkheads, and across hull structure is a significant integration burden. Marine classification societies (DNV, Lloyd’s, ABS) have specific requirements for cable types, routing, and protection. Signal cables near high-voltage propulsion cables require separation or shielding to prevent interference.

Wireless sensing eliminates most of these cable routing challenges. Bluetooth Low Energy (BLE) is the dominant protocol for short-range wireless sensor applications in marine environments. BLE operates in the 2.4 GHz ISM band, provides adequate range (10–30 meters in a steel machinery space with typical obstructions), and consumes low enough power for battery-operated sensors. A single BLE gateway can aggregate data from multiple sensors throughout a machinery space, requiring only a single cable run to the ship’s data network.

Remote Access and Connectivity

A vessel underway may be operating in an area with no cellular coverage for extended periods. This creates a data latency problem for condition monitoring: if a bearing begins developing a fault during a voyage, that data may not reach shore-based analysts until port call. The practical consequence is that bearing monitoring for vessels must either store sufficient local data to reconstruct fault development after the fact, or use satellite connectivity (Iridium, Starlink) for continuous uplink.

Local storage on the sensor or gateway, with periodic uplink when connectivity is available, is the most reliable architecture. The sensor should continue capturing and storing data regardless of connectivity state — communication failure should not cause data gaps in the bearing condition record.

Magnetic Mounting for Rapid Deployment

In applications where permanent mounting is impractical — routine inspection routes, temporary monitoring during sea trials, or condition assessment before a dry dock decision — magnetic mounting provides a reliable attachment method. Neodymium magnets with pull forces of 50–100 N provide adequate holding force against hull vibration on ferromagnetic surfaces. The mounting surface must be clean and flat; even a thin layer of scale or paint significantly reduces effective coupling.

A 316L stainless steel sensor shell with integrated magnets addresses both the corrosion and mounting requirements simultaneously. The metal shell provides the primary environmental protection, and direct metal-to-housing contact at the magnet face ensures the vibration signal path is rigid and well coupled.

A Practical Marine Monitoring Architecture

• 316L stainless steel sensor housing with IP68 rating tested in saltwater
• Magnetically mounted for rapid installation and removal without tools
• BLE wireless communication to a machinery space gateway
• Local flash storage on the sensor for data continuity during connectivity gaps
• LTE or satellite gateway for shore-based data access
• High-frequency vibration capture (≥20 kHz) with direct coupling to bearing housing

For applications where bearing failure triggers insurance claims or warranty disputes — common in high-value marine propulsion systems — the monitoring system must also provide tamper-evident data records. Standard monitoring systems log trending data but do not preserve the high-fidelity vibration record of the failure moment itself. Solutions like Fault Ledger address this by capturing and cryptographically sealing the raw vibration data from the failure event, providing a forensic-grade record that survives the event and remains usable in subsequent investigations.

Marine bearing monitoring is not simply a matter of waterproofing a standard industrial sensor. The combination of corrosion, moisture, noise, remote access constraints, and forensic requirements demands an integrated approach to hardware selection, sensor placement, wireless architecture, and data integrity. Treating these as separate concerns typically produces a system that fails on at least one axis within the first operating season.

As vessel operators move toward continuous rather than periodic bearing inspection, the technology exists to deliver reliable data from even the most demanding marine environments — provided the hardware and architecture are chosen with marine-specific constraints as the primary design driver, not as an afterthought. Fault Ledger’s marine bearing monitoring solution was built from the ground up with these constraints in mind.