Cumulative energy consumption. The consumption-side counterpart to energy_delivered_kwh, kept distinct so a site that both draws and exports does not net the two into a meaningless single number.
energy_kwhEach 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 |
|---|---|---|
| Fanuc | ENERGYKWH(J)ENERGYKWH_WhENERGYKWH_kWENERGY_KWH_JENERGYKWH [W]ENERGYKWH(Wh)+40 more spellings | 1.00 |
| Siemens | energieverbrauch(J)energieverbrauch(W)energieverbrauch_Whenergieverbrauch (J)energieverbrauch(Wh) | 1.00 |
| Carrier | kWhEnergyKWH | 1.00 |
| Sungrow | Daily PV generation & battery discharge | 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 | kWh |
| Accepted input units | J MWh Wh kJ kWh |
| Converted on ingest | J MWh Wh kJ → kWh |
| Physics bounds | 0.0 to 1000000000000.0 kWh |
| Measurement type | cumulative — resets are expected; a decrease is a counter reset, not a negative reading |
| Distinct source tags in the corpus | 226 |
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.
energy_delivered_kwh spindle_speed_rpm spindle_load_pct program_name part_count