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

• 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

Scope	Details
Device type	Weather Station only
Telemetry keys	Irradiance, Temp-PV Module, Temp-air
Date range	Up to 6 weeks of historical data. Future dates not allowed.
Unit	As configured on the Weather Station device

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.
• Protection against changed data. If the original readings change between downloading the workbook and uploading it, the upload 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

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.

SolarSENS checks the device, the dates, and whether a safety hold is already active. The run is created in Pending status with a unique name.

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.

Keep the workbook’s structure

Don’t add, remove, or rename columns, rows, or sheets. SolarSENS rejects a workbook that doesn’t match the downloaded format.

Step 3 — Upload the workbook

1. Upload the edited XLSX file.
2. SolarSENS checks the workbook, keeps a copy that can’t be changed, and prepares the correction for each day in the range.

If the original readings changed between download and upload, the upload is rejected. Start a new run and try again.

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 places a safety hold on the device and starts the correction for all days at once. The run moves to Running status.

Step 5 — Monitor execution

The execution progress view updates in real time per day:

Status	What it means
Backup Stored	Original data backed up
Backup Verified	Backup integrity confirmed
Mutation Started	Applying corrections
Corrections Verified	Corrected data verified
Processing Completed	Downstream processing completed
Completed	All steps successful
Failed	Execution error — review and retry
Needs Attention	Some days completed, some need action
Cancelled	Cancelled 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

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

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

Each day’s backup is kept for 30 days after the day reaches a terminal state (Completed, Failed, or Cancelled). After that, you can delete the backup. SolarSENS removes it and records the deletion in the audit log.

The run’s history can’t be edited. It records every status change and who made it.

Related pages

• Privileged Data Maintenance — broader context on data correction and repair
• How SolarSENS Processes Plant Data — how corrected data flows through downstream calculations