Fleet Normalisation & LTSA Assurance
Several SCADA schemas and several availability definitions, reduced to one governed model that holds up at the review table.
The challenge
A mixed fleet means every platform ships its own SCADA schema, its own tag names and — most consequentially — its own definition of availability. Two turbines from different OEMs cannot be ranked against each other because the numbers do not mean the same thing.
That gap is not academic. It is the reason LTSA review meetings become arguments about definitions instead of conversations about performance.
The approach
A common tag dictionary and an agreed loss taxonomy across every platform, feeding one governed model. Availability is then recomputed independently from raw SCADA and reconciled monthly against the OEM-declared figure.
The point is not to prove the OEM wrong. It is to make any difference visible and specific, so it becomes an agenda item with a number attached rather than a disagreement about method.
- Common tag dictionary mapping every platform to one vocabulary
- Agreed loss taxonomy — every lost kWh assigned to a cause
- Independent availability recomputation from raw SCADA
- Monthly reconciliation against OEM-declared figures
- Time-to-attend and time-to-restore by fault class and site
The outcome
Every platform ranked on identical definitions, and an evidence-backed position in every service review.
- One model across all OEM platforms, identical definitions
- Differences with the OEM become agenda items, not arguments
- No unexplained residual bucket in the loss waterfall
- Response analytics give evidence-backed positions on SLA
Curious what this would find in your portfolio?
A diagnostic runs across a representative slice and establishes the baseline before any build commitment.