Manual data maintenance
Manual data maintenance covers two operations that ordinary configuration changes cannot handle:
- Reprocess historical data — recalculate or replace results when source data arrives late or a corrected configuration needs to apply retroactively.
- Remove selected telemetry — permanently delete specific stored values that are confirmed invalid.
Removal is not a substitute for fixing a source or configuration problem.
Choose the direction
Section titled “Choose the direction”| Situation | Direction |
|---|---|
| Source data arrived late, or a corrected configuration must apply historically | Reprocess |
| A known set of stored values is invalid and must be removed | Remove |
| The cause is still unknown | Investigate first |
| The scope cannot be named precisely | Narrow down plant, devices, measurements, and period first |
Scope requirements
Section titled “Scope requirements”Every request needs, in writing:
- Affected plant, devices, and telemetry measurements
- Exact local and UTC time boundaries
- Evidence that current values are wrong and the expected correct result
- Downstream dashboards, reports, or calculations that may change
- Person responsible for verifying the outcome
For removal, scope must be against exact values, not a date range. If a preview of affected values is incomplete, narrow the scope until it is complete.
How each operation finishes
Section titled “How each operation finishes”- Reprocessing — accepted as queued work. Not all partitions complete at once. Verify each requested scope against the expected result.
- Removal — immediate and irreversible. Verify the selected values are absent and review affected views.
Who performs these
Section titled “Who performs these”Both operations are restricted to administrators. The executable procedure with safeguards and limitations is in the internal runbook (sign-in required).