In-house Energy Germany Company newsroom

EnBW

Predictive Maintenance

EnBW needed to move beyond reactive, manual analysis of massive wind-turbine telemetry so it could detect faults and anomalies early across a heterogeneous fleet before they caused expensive failures or downtime.

450 wind turbines are monitored with the aid of AI
Each turbine contains up to 1,500 sensors
Every ten minutes, each wind turbine sends its operating data
hundreds of thousands of values per minute

Reported impact

Business outcome

EnBW detects turbine faults and anomalies earlier, can reduce output before a complete failure occurs, cuts maintenance and failure costs, and improves the availability of renewable-energy generation.

  • Cost Reduction
  • Risk Reduction

Solution

EnBW built an in-house AI and machine-learning workflow for condition and structural health monitoring across its onshore wind fleet. Each turbine contributes operating telemetry from up to 1,500 sensors, with readings such as bearing temperature, gear-oil temperature, generator speed, wind speed, rotational speed and output arriving continuously, and core operating data sent every ten minutes. EnBW correlates these measurements with environmental and operating parameters, then feeds them into thousands of specialized models that learn normal behavior for specific turbine types, components and site conditions. When a model detects deviation from the learned baseline, the system alerts specialists, who review the abnormal pattern with engineers and technical experts, estimate severity and decide whether to dispatch service teams. If a serious failure is imminent, the team can proactively restrict turbine output to protect damaged parts, buying time for maintenance while improving availability and reducing repair cost.

Data flow

Telemetry from wind-turbine sensors and anemometers flows into EnBW's monitoring environment, where operating and environmental parameters are correlated and used to train and run specialized machine-learning models. Deviations from normal behavior trigger alerts for specialists, engineers and technical experts, who validate the issue and, if needed, send service teams or reduce turbine output to protect equipment.

Solution architecture

0 products mentioned

Architecture clues

  • Models are specialized by turbine type, component set, location and environmental conditions rather than using one general model.
  • New wind turbines must pass through a full annual cycle before models can account for seasonal fluctuations reliably.
  • Specialists can restrict turbine output remotely when models indicate imminent failure.
  • Telemetry includes bearing temperature, gear-oil temperature, generator speed, outside temperature, wind speed, rotational speed and output.
  • The team can access elastic compute capacity equivalent to hundreds or thousands of machines for model calculation.

Evidence from the source

"By doing so, they are already saving EnBW around ten million euros per year."
"Every ten minutes, each wind turbine sends its operating data."
"If, for example, they detect that a serious fault is imminent and there is risk of a complete system failure, they restrict the wind turbine’s output."
"The EnBW team currently monitors 450 wind turbines with the aid of AI."
"The pair are working with artificial intelligence (AI) to subdue the data storm and thus enable them to detect faults and anomalies in the turbines at an early stage."
"We feed the model with these values – and it then learns the dependencies between the individual measured parameters. This is how the model simulates a certain normal behavior."
Transparency Evidence & methodology 75/100 reference value · 90% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth15/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence90%
  • Source authority25/25
    The deployment is described by the adopting organization or a government source.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity6/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. EnBW

    EnBW customer story

    First-party
    https://www.enbw.com/company/topics/wind-power/using-ai-for-wind-power.html
    Source type
    Customer-published story
    Published
    Oct 25, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.