Supported OEMs
ODS-E currently ships transform support for 16 OEM ecosystems across solar, BESS, wind, and SCADA historian sources.
Solar Inverters
| OEM |
Typical Input |
Notes |
| Huawei FusionSolar |
CSV/API export |
Common in utility/commercial PV fleets |
| Enphase Envoy |
JSON API payload |
Microinverter-heavy portfolios |
| Solarman Logger |
CSV/API export |
Logger-centric deployments |
| SolarEdge |
CSV/API export |
Site-level telemetry and status streams |
| Fronius |
CSV/API export |
Inverter/device-level export formats |
| Switch Energy |
API/flat export |
Integration depends on deployment profile |
| SMA |
API/flat export |
Structured status and production feeds |
| FIMER Aurora Vision |
API export |
Legacy/modern payload variants may differ |
| SolisCloud |
API export |
Cloud telemetry with OEM-specific status mappings |
| SolaX Cloud |
API export |
Requires vendor-specific field mapping |
| Higeco |
JSON API export |
Cloud SCADA platform (docAPI), normalized contract input |
Battery Energy Storage (BESS)
| OEM |
Source Key |
Typical Input |
Notes |
| Sungrow PowerTitan |
sungrow_bess |
JSON (iSolarCloud) |
Charge/discharge, cell-level telemetry, dispatch mode |
| BYD BatteryBox |
byd_bess |
CSV (BMS export) |
Cell voltage/temperature, cycle count, SoC/SoH |
Wind Turbines
| OEM |
Source Key |
Typical Input |
Notes |
| Vestas |
vestas |
CSV (Vestas Online) |
Wind speed, rotor RPM, blade pitch, nacelle direction, turbine state codes |
| Siemens Gamesa |
siemens_gamesa |
CSV (Diagnostic System) |
Nacelle/met mast wind speed fallback, availability status mapping |
| Nordex |
nordex |
CSV (Nordex Control) |
Turbine status string mapping, wind speed, rotor RPM |
SCADA Historian
| OEM |
Source Key |
Typical Input |
Notes |
| Terraco |
terraco |
JSON (REST API) or CSV (export) |
Auto-detects input format, {AssetName}.{TagName} pattern mapping, state code mapping |
Compatibility Notes
- Input schema quality varies by OEM and account configuration.
- Historical exports may differ from live API responses.
- Some connectors may require additional mapping for edge deployments.
Recommended Rollout Sequence
- Start with one OEM and validate output.
- Add second/third OEMs using the same downstream contract.
- Track transform regressions when OEM providers change their APIs.
