Skip to content
  • operations
  • telemetry correction

Correct Historical Telemetry

Correct historical telemetry values for a Weather Station device at your plant — upstream irradiance, module temperature, or air temperature — through a guided, audited workflow. Corrected values flow through all downstream calculations including performance ratio and energy loss analysis.

Before you start

Section titled “Before you start”
  • ADMIN role in SolarSENS.
  • A plant with a Weather Station device assigned to your portfolio.
  • Telemetry Correction enabled for your environment. If it doesn’t appear in your navigation, contact support.

What you can correct

Section titled “What you can correct”
ScopeDetails
Device typeWeather Station only
Telemetry keysIrradiance, Temp-PV Module, Temp-air
Date rangeUp to 6 weeks of historical data. Future dates not allowed.
UnitAs configured on the Weather Station device

Important constraints

Section titled “Important constraints”
  • One correction at a time per device. A safety hold prevents a second correction on the same device while one is active.
  • Same operator must finish the flow. Only the person who created the correction run can upload the workbook and confirm execution.
  • Baseline drift protection. If the raw telemetry changes between template download and upload, the submission is rejected. Start a new run in that case.
  • Six-week maximum. A single correction run cannot span more than six consecutive weeks.

Step 1 — Start a correction run

Section titled “Step 1 — Start a correction run”
  1. Open Telemetry Correction from the SolarSENS navigation.
  2. Select the plant and Weather Station device.
  3. Choose the telemetry keys — Irradiance, Temp-PV Module, or Temp-air.
  4. Set the date range for the correction.
  5. Review and confirm the scope.

The system validates the scope — device profile, date boundaries, and any active safety hold. The run is created in Pending status with a unique name.

Step 2 — Download and edit the workbook

Section titled “Step 2 — Download and edit the workbook”
  1. Download the XLSX workbook. It contains the current baseline telemetry for your selected scope.
  2. Edit the values in the three editable columns: Irradiance, Temp-PV Module, and Temp-air.
  3. Keep the workbook structure intact. The system will reject a workbook that has been structurally modified.

⚠️ Do not add, remove, or rename columns, rows, or sheets. The workbook must match the expected format.

Step 3 — Upload the workbook

Section titled “Step 3 — Upload the workbook”
  1. Upload the edited XLSX file.
  2. The system validates the workbook, stores it as an immutable artifact, and generates execution plans for each day in the range.

If the raw telemetry changed between download and upload (baseline drift), the system returns a conflict error. Start a new run and try again.

Step 4 — Review and confirm

Section titled “Step 4 — Review and confirm”
  1. Review the impact summary — how many data points are unchanged, changed, removed, or added.
  2. Verify the numbers match your expectation.
  3. Click Confirm to launch the correction.

Confirming creates a safety hold on the device and dispatches execution for all days in parallel. The run moves to Running status.

Step 5 — Monitor execution

Section titled “Step 5 — Monitor execution”

The execution progress view updates in real time per day:

StatusWhat it means
Backup StoredOriginal data backed up
Backup VerifiedBackup integrity confirmed
Mutation StartedApplying corrections
ThingsBoard VerifiedCorrected data verified
Dagster SuccessDownstream processing completed
CompletedAll steps successful
FailedExecution error — review and retry
Needs AttentionSome days completed, some need action
CancelledCancelled before mutation started

You can cancel a run before any day enters mutation. Once the first day starts mutating, cancellation is no longer available.

If a run enters Needs Attention, review the recovery outcome before continuing. A run can resume after its backup and recovery checks have been verified. When a correction fails after changes begin, SolarSENS restores the original telemetry before releasing the run; do not start another correction until the recovery result is confirmed.

Step 6 — Verify the results

Section titled “Step 6 — Verify the results”
  1. Confirm the run shows Completed for every day.
  2. Review the corrected values in Plant Monitoring or export them through DataHub.

History and backups

Section titled “History and backups”

The History panel shows all past correction runs. You can view by individual run or by plant.

Day-level backup artifacts are retained for 30 days after the day reaches a terminal state (Completed, Failed, or Cancelled). After that, you can delete the backup — the system removes the artifact from storage and records the action in the audit log.

Run-level audit events are append-only and immutable. They record every state transition and who performed it.

Section titled “Related pages”