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

The problem

Every inverter OEM has a proprietary cloud portal. 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 SolarTwin solves it

• SunSpec Modbus — the de-facto solar industry standard. SolarTwin is a first-class SunSpec client with full register-map support.
• IEC 61850-7-420 — the DER information model used by utility-scale plants and substation automation. Native 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 inverters, met stations, 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.
• Irradiance & weather ingest — ECMWF, CAMS, satellite nowcasts 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. "Plant A SunSpec Modbus", "Pyranometer over Modbus RTU").
2. Tags are mapped to the canonical SolarTwin schema — once, with the SunSpec model 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 plant to the portfolio in days, not quarters.