See your fleet the way it actually behaves.

The problem

Most wind operations run on 10-minute SCADA averages. By the time a vendor portal aggregates and the on-call refreshes a dashboard, the gust that tripped a turbine — or the vibration spike that preceded a gearbox alarm — is buried in a five-point moving average. Performance engineers spend their days reconstructing what "probably" happened from coarse data.

How WindTwin solves it

• Live dashboards for rotor RPM, generator temperature (stator and bearing), gearbox vibration (RMS and spectral), pitch angle, active power (kW), and wind speed/direction — out of the box.
• Sub-second updates via SignalR. When a turbine controller publishes, the screen reflects it within a heartbeat. No 10-minute lag, no page refresh.
• OEM-normalised tags so a Vestas Online tag and the equivalent Siemens Gamesa tag show up on the same dashboard panel with consistent units and ranges.
• Per-turbine telemetry schemas — every reading is typed, unit-aware, and bounded by thresholds you configure once per model.
• Time-series history retained at full resolution — no down-sampling that silently drops the transient you cared about.
• Compare windows — overlay the last 24 hours against the same conditions last week, or any custom interval.

How it works

1. Your turbine controller or SCADA gateway publishes telemetry over IEC 61400-25, OPC UA, Modbus TCP, or MQTT (we bridge any of them).
2. WindTwin parses, normalises against the turbine model schema, and writes to the time-series store.
3. Every connected client — operator dashboard, mobile, integrated control system — sees the change in under a second.

What you can do with it

• Catch a vibration transient as it happens, not in next month's CMS report.
• Validate a power-curve deviation against the live wind and pitch state instead of guessing from 10-minute means.
• Hand new operators a single source of truth on day one — across every farm in the portfolio.