An assessment of your own fleet,
on the history you already hold.

Tell us the sites, the turbine models, and roughly how much history is available. The assessment runs on exported SCADA data, so nothing is installed and operations are not interrupted.

  • Your own fleet, not a demonstration datasetThe assessment is performed on SCADA history from the sites you nominate, over a period you choose.
  • Underperformance identified per turbineEach machine is measured against comparable units operating in the same conditions, and the gap is quantified.
  • Developing faults, with the evidence attachedComponent degradation visible in the record before an alarm was raised, with the signals that moved and the window they moved in.
  • Annual energy and revenue on every findingEach result carries what recovering it is worth over a year, which is what allows work to be sequenced by return.

Onshore fleets, offshore portfolios, and mixed-manufacturer sites are all assessed on the same basis.

Request a demo

We respond within one business day.

Measured against a period whose outcome you already know.

A demonstration on our own sample data establishes very little, because we selected it. An assessment is worth running on your history, over a period in which the operations team already knows which machines caused trouble, so that the comparison has a control.

Two things are being measured. Whether the findings correspond to events already known to the team, which establishes that the models are reading the fleet correctly. And what the findings nobody knew about are worth, which is the product itself.

Nothing is installed to do this. The assessment runs on exported SCADA history, so it can be completed before any decision about deployment is taken.

How each turbine is modeled against its own conditions

What the first thirty days involve.

An assessment runs on your own historical data, over a period the operations team already has views about, because the only convincing result is one that can be checked against a known outcome.

  1. Transfer the operating history

    Standard SCADA exports for the sites in scope. No installation, no site visit, and no interruption to operations.

  2. Each turbine is modeled against its own conditions

    The models build a per-machine expectation from matched wind conditions, then measure actual output against it across the full period.

  3. Findings are delivered ranked and quantified

    Each finding names the turbine, the probable cause, the evidence behind it, and the annual energy and revenue at stake.

  4. Verify against known events

    The team already knows what happened on some of those machines. That overlap is the control, and it establishes how far to trust the remainder of the list.