Skip to content

Manual data maintenance

Manual data maintenance handles two data-correction needs that ordinary configuration changes cannot address:

  • Reprocess historical data — recalculate or replace results when source data arrives late, or when a corrected configuration must apply retroactively.
  • Remove selected telemetry — permanently delete specific stored values that are confirmed invalid.

Removal does not repair a source or configuration problem. Fix the underlying cause separately.

If this is the situationUse this direction
Source data arrived late, or a corrected configuration must apply historicallyReprocess
A known set of stored values is invalid and must be removedRemove
The cause is still unknownInvestigate first
The scope cannot be named preciselyNarrow the scope first to the plant, devices, measurements, and period

Every request must state the following in writing:

  • The affected plant, devices, and telemetry measurements.
  • Exact local and UTC time boundaries.
  • Evidence that the current values are wrong and the expected correct result.
  • Downstream dashboards, reports, or calculations that may change.
  • The person responsible for verifying the outcome.

For removal, the scope must identify exact values rather than only a date range. If the preview of affected values is incomplete, the scope must be narrowed until the preview is complete.

Reprocessing updates historical results for the approved scope. Accepted reprocessing work is queued, and not all partitions complete at once.

After completion, the requested scope must be verified against the expected result.

Removal permanently deletes the selected stored values. It is immediate and irreversible; it does not archive values for later recovery.

After removal, verify that the selected values are absent and review affected views.

Both operations are restricted to administrators. The executable procedure, safeguards, and limitations are in the internal runbook (sign-in required).