Prepare a controlled historical import with explicit asset IDs, timestamps, units, and validation.
Use the approved historical-import template for the active environment. The import must identify the target asset and timestamp for every row.
| Field | Requirement |
|---|---|
| ID | The exact installation or device ID that owns the measurement. |
| time | An unambiguous timestamp, preferably ISO 8601 with an offset or Z. |
| timezone | Required when the timestamp itself has no offset; use an IANA name such as Europe/Brussels. |
Supported import workflows can include fields such as:
actualPower_W;energyDelta_Wh;Use plain decimal notation without thousands separators. Do not convert watts to kilowatts or watt-hours to kilowatt-hours without also changing the field definition.
| ID | time | timezone | actualPower_W | energyDelta_Wh | temperature_C |
|---|---|---|---|---|---|
| 123 | 2026-02-01T08:00:00Z | UTC | 15000.001 | 500.2 | 25.0 |
| 123 | 2026-02-01T08:15:00Z | UTC | 14800.750 | 490.0 | 24.8 |
When the same ID and timestamp occur more than once, duplicate handling depends on the importer. Remove unintended duplicates before upload and document intentional corrections.
Back up the source file
Keep the original export unchanged. Perform cleaning or unit conversion in a separate working copy so every imported value remains traceable.