Total AC reactive power, signed. Separated from active power because a single generic Power tag on a meter is ambiguous between kW, kVA and kVAR, and the three are not interchangeable in any downstream calculation.
Total AC reactive power. Signed.
reactive_power_kvarEach of these is a real tag as the device or controller emits it, taken from the Forge mapping corpus. This is the table that does not exist anywhere else — the reason cross-vendor telemetry is hard is visible in a single column.
| OEM / profile | Raw tag as the device emits it | Confidence |
|---|---|---|
| Schneider | Q_TotalkVAR_TotTotal_kVARkVAR_TotalReactivePower | 1.00 |
| Fronius | VARReactivePower | 1.00 |
| SunSpec 101 | VARReactivePower | 1.00 |
| SunSpec 103 | VARReactivePower | 1.00 |
| SolarEdge (inverter) | I_AC_VAR | 1.00 |
| SolarEdge (meter) | M_AC_VAR | 1.00 |
| SunSpec 201/202 | VAR | 1.00 |
| SunSpec 203/204 | VAR | 1.00 |
| Sungrow | Reactive power | 1.00 |
Every row above is an exact match — a deterministic pack entry or a confirmed corpus mapping — so all of them carry confidence 1.00. That is not a rounding: these are the two exact-match layers, and a tag that resolves here never reaches the embedding or LLM layers. Mappings resolved by the LLM layer do carry sub-1.0 confidence, but those are per-tenant and are not published here.
The canonical field is not just a name. It is a contract about units, sign convention and plausible range, enforced on the way in and re-checked at read time.
| SI / canonical unit | kVAR |
| Accepted input units | MVAR kVAR var |
| Converted on ingest | MVAR var → kVAR |
| Physics bounds | -100000.0 to 100000.0 kVAR |
| Measurement type | instantaneous |
No mapping table to maintain, and no per-vendor branch in your code. The same request shape works for every OEM in the table above.
Read alongside this one.
spindle_speed_rpm spindle_load_pct program_name part_count feed_rate