First-class support for the standards your fleet already speaks.

The problem

Every turbine OEM has a proprietary SCADA stack. Every third-party gateway adds latency, licensing cost, and a data-ownership question. Every "integration" you do today becomes a maintenance burden tomorrow. Operators end up locked into vendor-specific UIs because the integration cost of getting out is too high.

How WindTwin solves it

• IEC 61400-25 — the wind-industry standard for turbine-to-SCADA communication. WindTwin is a first-class IEC 61400-25 client.
• OPC UA — connect to plant historians, balance-of-plant PLCs, and substation gateways. Full PubSub and Client/Server.
• Modbus TCP / RTU — for the older controllers, met masts, and substation devices that are not going anywhere.
• MQTT (Sparkplug B) — for the edge gateways that already speak it, and for greenfield deployments where you want the protocol of the next decade.
• Weather & forecast ingest — ECMWF, GFS, DWD ICON via NetCDF / GRIB2 on a schedule.
• REST API + SignalR — every read and write available to your ERP, trading, reporting, and BI systems.
• Webhooks — for the events you want pushed (alarms, work-order changes, telemetry threshold crossings).

How it works

1. A connector instance is configured per source (e.g. "Farm A SCADA over IEC 61400-25", "Met mast over Modbus").
2. Tags are mapped to the canonical WindTwin schema — once, with the OEM’s tag dictionary as a starting point.
3. Data flows continuously; the connector reports its own health to the same dashboards your operations team uses.

What you can do with it

• Replace a per-OEM portal subscription with a single platform.
• Push live telemetry into your trading platform without an ETL pipeline you have to maintain.
• Add a new farm to the portfolio in days, not quarters.