Wind turbine gearbox predictive maintenance

has a clear lead for vibration-based prediction of wind turbine gearbox failures before downtime.

Since Jul 8Updated Nov 20, 2026Based on 60 AI answersReviewed by

How we measure

Brands AI mentions

Mentioned in, on ChatGPT and Google AI Mode

leads this topic, but leads Energy Asset Management Solutions overall.

Key takeaways for Wind turbine gearbox predictive maintenance

  • Vs overall market

    Onyx Insight leads Wind turbine gearbox predictive maintenance (58%), ahead of overall Energy Asset Management Solutions leader IBM Maximo. View Energy Asset Management Solutions

  • Top contenders

    Onyx Insight (58%) leads runner-up fleetMONITOR (37%) by 21 percentage points.

Questions and answers

  • ChatGPTNov 16, 2026

    1. 1Onyx Insight
    2. 2fleetMONITOR
    3. 3ecoCMS
    4. 4Bently Nevada
    5. 5ADAPT.wind
    6. 6Hitachi Energy
    7. 7Lumada APM

    The solution I would recommend investigating first is ONYX Insight, specifically its fleetMONITOR APM platform, paired with its ecoCMS (Condition Monitoring System).

    • North American Clean Energy - ONYX Insight’s fleetMONITOR Upgrade Enables System 1 Capability for Enhanced Turbine Condition Monitoring

    Why it fits your wind turbine fleet:

    • Vibration analytics: Detects developing gearbox, bearing and drivetrain faults.
    • Predictive maintenance: Identifies early degradation before it becomes a major failure.
    • Fleet-wide monitoring: Provides visibility into turbine health and helps prioritize maintenance.
    • Data integration: Can work with existing condition-monitoring systems and operational data.
    • Maintenance planning: Helps schedule repairs before catastrophic gearbox failures and costly downtime.

    Other solutions worth evaluating

    SolutionRelevant capability
    ONYX Insight fleetMONITORWind-specific fleet analytics and drivetrain diagnostics
    Bently Nevada ADAPT.WindContinuous vibration monitoring of gearboxes, generators and main bearings
    Hitachi Energy Lumada APMPrognostic asset management combining SCADA, vibration and lubricant data
    ASTRIISEarly vibration-based fault detection and component diagnostics

    Evidence supporting multi-month prediction

    A 2019 peer-reviewed study published in Wind Energy found that machine-learning models using high-frequency vibration data could predict wind turbine gearbox failures 5–6 months ahead, compared with approximately one month using SCADA data alone.

    Bently Nevada also specifically advertises ADAPT.Wind as providing warnings of gearbox and bearing problems weeks or months ahead.

    My recommendation

    Start by evaluating ONYX Insight fleetMONITOR and Bently Nevada ADAPT.Wind.

    Useful vendor resources:

    One important distinction: Predicting an impending failure months ahead is different from accurately predicting its exact failure date. Ask vendors for validated gearbox failure case studies, false-positive rates, and demonstrated prediction lead times using your turbine models and existing sensor data.

    Google AI ModeNov 16, 2026

    1. 1Bently Nevada
    2. 2Baker Hughes
    3. 3SKF
    4. 4Siemens Energy
    5. 5OmniView
    6. 6Pulse CMS
    7. 7Vantage
    8. 8Compass
    9. 9Poseidon Systems
    10. 10SKF Enlight ProCollect
    11. 11Hottinger Brüel & Kjær

    Several established Asset Performance Management (APM) and Condition Monitoring Systems (CMS) specialize in high-frequency vibration analysis to catch wind turbine gearbox, high/intermediate/low-speed shaft, and bearing anomalies 6 to 12+ months before catastrophic failure.

    Rather than relying purely on SCADA trends (which usually flag thermal or pressure spikes right before a breakdown), these enterprise APM and CMS platforms combine continuous or high-speed vibration acquisition with diagnostics and machine learning:

    Top APM & CMS Solutions for Wind Drivetrains

    • Bently Nevada (Baker Hughes) – System 1 & VbOnline Pro
      • How it works: Uses multi-channel vibration monitoring hardware coupled with System 1 enterprise condition monitoring software. It tracks gear mesh frequencies, bearing defect frequencies, and transient start-up/shut-down events.
      • Lead time: Routinely provides months of early-warning runway for planetary and parallel stage gear or bearing degradation, letting operators schedule up-tower repairs rather than full gearbox swaps.
      • Explore more:
    • SKF – Enlight ProCollect & WindCon
      • How it works: SKF WindCon continuously monitors vibration, oil condition, and temperature, backed by SKF’s engineering diagnostic services (Remote Diagnostic Centers). SKF’s kinematic models map exact tooth-pass and bearing-pass frequencies inside multi-stage gearboxes.
      • Lead time: Frequently flags spalling, scuffing, or micro-pitting early enough to shift from reactive firefighting to planned minor interventions.
    • Siemens Energy / Omniview or Pulse CMS
      • How it works: Tailored heavily for multi-megawatt onshore and offshore turbines, Siemens and specialized third-party CMS providers deploy synchronized acceleration sensors on the main bearing, torque arm, and high/intermediate/low-speed shafts.
      • Lead time: Detects spectral sidebands and structural resonance shifts well in advance of metal debris shedding into the oil filter.
    • Marmix / Brüel & Kjær Vibro (B&K Vibro) – VANTAGE / Compass CMS
      • How it works: B&K Vibro provides dedicated wind turbine monitoring systems (like VibroControl and Compass ) that analyze complex cyclostationary vibration signatures under variable speed and variable load wind profiles.
      • Lead time: Specialized signal processing isolates early fatigue cracks in gear teeth or planet bearings months ahead of time.

    A Crucial Complement to Vibration: Oil & Wear Debris

    While vibration analysis excels at kinematic and structural frequency shifts, fleet operators often pair vibration-based APM with online oil/debris sensors (such as Poseidon Systems or similar real-time ferrous/non-ferrous wear monitors).

    • Why combine them? Some sub-surface micro-pitting or slow-burn planetary bearing wear generates minimal external vibration signature initially, whereas real-time debris tracking or multi-parameter fusion (Vibration + SCADA + Oil) extends warning horizons out to 12–24 months, giving your engineering team time to stage cranes, order up-tower parts, and avoid full $250k+ gearbox replacements.
  • Google AI ModeNov 7, 2026

    1. 1IBM Maximo
    2. 2SAP

    Building an effective predictive maintenance workflow for wind turbine gearboxes combines low-cost operational data with high-frequency diagnostic sensors . Early detection typically provides a lead time of weeks to several months before a catastrophic failure.

    Step 1: Data Ingestion & Layering Strategy

    A robust workflow relies on a multi-tiered data architecture:

    • Layer 1: SCADA Data (Free / Already Collected)
      • Variables to track: Gearbox bearing temperatures, oil sump/inlet temperatures, generator speed, active power output, ambient temperature, and wind speed.
      • Purpose: Ideal for macro-anomaly detection and normal behavior modeling.
    • Layer 2: Condition Monitoring Systems (CMS via Vibration)
      • Sensors: Accelerometers mounted on high-, intermediate-, and low-speed gear shafts and bearings.
      • Purpose: Captures high-frequency dynamic signals (time-domain and frequency/spectral domain) to spot gear pitting, cracking, or shaft misalignment.
    • Layer 3: Lubricant & Debris Analysis (Periodic Physical Checks)
      • Parameters: Spectrometric oil analysis, ferrous particle counters, water content, and viscosity.
      • Purpose: Validates mechanical wear hypothesis flagged by vibration or thermal anomalies.

    Step 2: The End-to-End Workflow Architecture

    [ SCADA & CMS Sensors ] 
             │
             ▼
    [ Data Preprocessing & Normalization ] 
             │
             ▼
    [ Normal Behavior Modeling (NBM / ML) ] ──(Residual Deviation)──> [ Anomaly Alert ]
             │
             ▼
    [ Diagnostic Classification (Vibration/Oil) ] 
             │
             ▼
    [ Maintenance Dispatch & CMMS Integration ]
    1. Data Cleaning & Normalization
      • Filter out start-up transients, curtailment periods, and extreme weather cut-outs.
      • Normalize operational variables against environmental conditions (e.g., mapping expected gearbox oil/bearing temperature against ambient temperature and power output curves).
    2. Normal Behavior Modeling (NBM)
      • Train machine learning models—such as Artificial Neural Networks (ANNs) , Random Forests, or Principal Component Analysis (PCA)—using historical healthy operating data.
      • Track the residual error (the delta between predicted temperature/vibration and actual measured values). A persistent upward drift in residual temperature or vibration energy signals an emerging fault.
    3. Automated Feature Extraction & Alerting
      • Run fast Fourier transform (FFT) or envelope analysis on vibration data to isolate gear-mesh frequencies and bearing defect frequencies (BPFO, BPFI).
      • Set dynamic thresholds rather than static trip-points to eliminate nuisance alarms caused by seasonal weather shifts.

    Step 3: Execution & Mitigation Best Practices

    • Establish Lead-Time Validation: Benchmark your models against historical failure events in your fleet to verify you are getting a 1 to 6 month warning window rather than a last-minute alarm.
    • Cross-Modal Verification: Never pull a turbine based on SCADA thermal alerts alone. Correlate a thermal anomaly with a vibration signature spike or an oil debris count before scheduling a crane or rope-access team.
    • Integrate with your CMMS: Automatically push high-confidence anomaly flags into your Computerized Maintenance Management System (like IBM Maximo or SAP) to generate work orders and pre-order replacement bearings or planetary stages.

    Explore methodologies and research frameworks via the UPCommons Wind Turbine Research Database or technical reports from the National Renewable Energy Laboratory (NREL).

    ChatGPTOct 1, 2026

    1. 1ISO 13373-1
    2. 2XGBoost

    Yes. A practical gearbox-failure workflow should detect abnormal mechanical behavior first, diagnose the likely failure mode second, and only then estimate remaining useful life (RUL). In wind turbines, combining low-rate SCADA with high-frequency vibration and oil/debris data is substantially more informative than relying on a single signal.

    Recommended workflow

    SCADA + vibration + oil/CMS
              │
              ▼
       Data quality / alignment
              │
              ▼
     Operating-state normalization
     (wind, power, RPM, temperature)
              │
              ▼
     Healthy baseline / normal-behavior model
              │
              ▼
       Anomaly detection
              │
              ├── Temperature/efficiency anomaly
              ├── Vibration spectral anomaly
              ├── Oil/debris anomaly
              └── Cross-sensor corroboration
              │
              ▼
       Fault classification
              │
              ▼
     Severity + persistence assessment
              │
              ▼
     RUL / failure-risk estimate
              │
              ▼
     Maintenance work order / inspection

    1. Instrument the gearbox at several levels

    SCADA: collect gearbox/bearing/oil temperatures, generator and bearing temperatures, rotor/generator speed, active power, wind speed, pitch, nacelle temperature, alarms and operating state. Modern turbines can provide hundreds of SCADA variables at roughly 1–10 minute intervals, making SCADA a relatively inexpensive first layer.

    Vibration/CMS: use accelerometers around gearbox bearings/housing and capture sufficiently high-frequency data for bearing and gear-mesh diagnostics. ISO 13373-1 provides general guidance on sensor selection, location, attachment, data collection and vibration-monitoring procedures.

    Lubrication: monitor oil temperature and, where practical, particle count/debris, viscosity and laboratory oil-analysis results. Lubrication analysis can provide information about wear and contamination that temperature/vibration alone may miss.

    2. Don't threshold raw temperature

    A gearbox naturally runs hotter under higher power, ambient temperature, and different rotational speeds. Instead, build a normal-behavior model:

    Expected gearbox temperature = f(power, RPM, wind speed, ambient temperature, operating state)

    Then calculate something like:

    Temperature residual = actual temperature − predicted healthy temperature

    A persistent positive residual is much more useful than "gearbox temperature > X °C."

    This approach is well established in SCADA-based condition monitoring, where trending, clustering and normal-behavior modeling are commonly used.

    Recent research is particularly encouraging: a 2026 study using SCADA temperature prediction reported detection of gearbox anomalies 59 days before failure in its dataset, although that result should not be treated as a guaranteed lead time for another turbine fleet.

    3. Extract mechanical features from vibration

    For each gearbox stage/bearing, calculate features such as:

    • RMS and peak acceleration
    • Crest factor
    • Kurtosis
    • Envelope-spectrum peaks
    • Gear-mesh frequency and harmonics
    • Sidebands around gear-mesh frequencies
    • Bearing characteristic frequencies
    • Spectral energy in selected bands
    • Time-frequency features

    The important point is to track changes relative to the turbine's healthy operating baseline, rather than applying one universal vibration threshold.

    For example:

    Gear-mesh energy ↑
           +
    Sideband amplitude ↑
           +
    Kurtosis ↑
           +
    Oil debris ↑
           =
    High-confidence developing gear/gear-tooth problem

    Vibration is particularly valuable because high-frequency data can reveal mechanical degradation substantially earlier than coarse SCADA measurements. One large study reported useful prediction horizons of up to several months using vibration data, compared with roughly a month using SCADA in its particular dataset.

    4. Fuse the signals instead of building isolated alarms

    This is probably the most important architectural decision.

    A useful health score could combine:

    Health anomaly =
        w1 × normalized temperature residual
      + w2 × vibration anomaly
      + w3 × oil/debris anomaly
      + w4 × efficiency anomaly
      + w5 × persistence

    Don't trigger a major maintenance event because one 10-minute SCADA point is unusual.

    Instead, require persistence and corroboration, for example:

    Warning:
      anomaly score > threshold for N consecutive intervals
    
    Inspection:
      warning persists + independent mechanical signal agrees
    
    Critical:
      rapidly increasing anomaly + vibration/oil evidence
      → maintenance intervention

    A 2024 industrial case study specifically found that standard diagnostic techniques could miss severe planetary-stage gearbox faults; combining SCADA and vibration information improved early detection and helped identify the faulty component.

    5. Separate detection from diagnosis

    Don't make one ML model answer everything.

    I'd use three stages:

    StageQuestionSuitable methods
    DetectionIs the gearbox behaving abnormally?PCA, autoencoder, isolation forest, normal-behavior model
    DiagnosisWhat is probably wrong?Random forest/XGBoost, CNN/transformer on vibration, rule + ML fusion
    PrognosisHow quickly is it deteriorating?Survival model, degradation model, temporal neural network, RUL model

    This also makes the system easier for maintenance engineers to trust.

    For fleets with few labeled failures, start with healthy-only anomaly detection. Recent work has demonstrated SCADA-only approaches that learn normal behavior and detect faults months ahead without requiring labeled fault examples, although validation on your particular turbine population is essential.

    6. Build your training dataset around actual failures

    For every historical gearbox event, create a timeline:

    Healthy ────────────────┬──────── degradation ─────┬── failure
                            │                           │
                      first anomaly              confirmed failure

    Attach:

    • turbine/model/gearbox configuration
    • failure date
    • failed component
    • failure mode
    • maintenance date
    • inspection findings
    • replacement date
    • SCADA history
    • vibration history
    • oil/debris results

    Avoid random train/test splits. If data from the same failure appears in both sets, you'll get severe leakage and an unrealistically good model.

    Prefer time-based and turbine-based holdouts:

    Train: turbines A–H, historical period
    Validation: turbines I–J
    Test: completely unseen turbines / later period

    7. Evaluate the system on maintenance usefulness

    Accuracy alone isn't the right KPI.

    Track:

    • False alarms / turbine-year
    • Missed failures
    • Median warning time
    • % failures detected >7/30/90 days ahead
    • Precision/recall by failure mode
    • Component-level diagnostic accuracy
    • RUL error
    • Unplanned downtime avoided
    • Inspection/maintenance cost generated by alarms

    Most importantly, measure lead time at an acceptable false-alarm rate. A model that detects 99% of failures but generates hundreds of unnecessary inspections isn't necessarily operationally useful.

    A good production architecture

    I'd implement it as:

    Edge/turbine layer → historian/data lake → feature pipeline → health models → event engine → CMMS/work-order system

    The event engine should produce something maintenance engineers can actually act on:

    Turbine WT-042 — Gearbox anomaly
    Severity: High
    First detected: 34 days ago
    Trend: Increasing
    Evidence: HSS bearing vibration + gearbox temperature residual
    Most likely area: HSS bearing
    Recommended action: borescope/vibration inspection
    Model confidence: 0.87
    Estimated intervention window: 2–6 weeks

    That is much more useful than simply saying "gearbox failure probability = 73%."

    If you're starting from scratch, I'd phase it: SCADA normal-behavior model → vibration feature pipeline → multi-sensor fusion → fault classification → RUL prediction. This lets you obtain useful early-warning capability before you have enough labeled failures to justify a sophisticated deep-learning system.

Also asked as

  • I need to reduce downtime caused by gearbox failures. How do I build a predictive maintenance workflow specifically for wind turbine mechanical faults?

Wind turbine gearbox predictive maintenance: common questions

Which brands does AI recommend for Wind turbine gearbox predictive maintenance?
AI most often mentions Onyx Insight (58%), fleetMONITOR (37%), Bently Nevada (38%), SKF (38%) and ecoCMS (25%) for Wind turbine gearbox predictive maintenance in Energy Asset Management Solutions.
Does the Wind turbine gearbox predictive maintenance leader match the overall Energy Asset Management Solutions market?
Onyx Insight leads Wind turbine gearbox predictive maintenance (58%), ahead of overall Energy Asset Management Solutions leader IBM Maximo.
What questions do buyers ask AI about Wind turbine gearbox predictive maintenance?
Common buyer questions include "We manage a fleet of wind turbines. What APM solution uses vibration data to predict gearbox failures months in advance?", "I need to set up a workflow for predicting gearbox failures in wind turbines. How do I detect mechanical faults early to avoid unplanned downtime?", "I need to reduce downtime caused by gearbox failures. How do I build a predictive maintenance workflow specifically for wind turbine mechanical faults?".
For agents: this page as Markdown, parse.gl/topics/gearbox-failure-prediction.md.

This page

Reuse: Figures and tables on this page are free to republish with attribution: a link to https://parse.gl/topics/gearbox-failure-prediction beside them. A standard followed link (dofollow) is preferred.

Read and search

Every brand's share on this topic, with 95% ranges: GET agent.parse.gl/v1/tools/query_metrics?args=%7B%22measures%22%3A%5B%22share_named%22%5D%2C%22by%22%3A%5B%22brand%22%5D%2C%22filter%22%3A%7B%22topic%22%3A%5B%22top_714678e2-b857-45d3-ab43-156b5bdb5733%22%5D%7D%7D
Search the index: GET parse.gl/api/public/search?q=<words>

Connect

Connect an assistant: agent.parse.gl/mcp

An agent can save work before signup: POST https://agent.parse.gl/v1/workspaces

What it costs

No account: Public figures and up to 5 examples per list, about 120 brands a day per address.
Free account: $5 in credit, your brand's first check (20 buyer questions) and a free weekly check.
After your first top-up: Exports and deeper search results. The first top-up starts at $5.
Live checks: $0.01 per question per engine ($0.05 on Gemini and Claude).
Full public answers and pages: 25 free per day, then $0.005 each.
Public answers older than 90 days: $0.001 each the first time your workspace counts or lists one, then yours.