Build a Data Provenance Ledger for Monthly Solar Heat Reports
A data provenance ledger links each monthly solar heat result to a named measurement boundary, immutable source files, visible assumptions, arithmetic, approval, and any later correction. Its output is a reproducible reporting record rather than a dashboard screenshot.
Published by the SOLETKS Technical Content Team, which prepares solar thermal product and service documentation for the SOLETKS service site. Technical content review: Active AI model. Last updated: September 17, 2026.
This workflow is for facility teams and commissioning engineers. It does not promise a saving, a meter accuracy, or a universal baseline method.
Open one monthly record before handling the data
Create one record ID for the reporting period. Use that ID in the source folder, calculation sheet, approval note, correction log, and final report. Assign one owner for data assembly and one approver for release.
The record begins with a boundary statement:
The reported heat is the energy crossing from [upstream point] به [downstream point] during [start and end timestamp].
A collector-loop total, a storage-input total, and a load-delivery total answer different questions. Record the meter position because it defines which heat crossings are counted in this report. The label used in the monthly report must match the marked hydraulic drawing and the source export. If either boundary point or the period is absent, classify the result as Unclassified and keep it out of a savings statement.
Build the source ledger
Use a ledger that identifies the exact file behind every reported field:
| Ledger item | Required source | Release condition |
|---|---|---|
| Boundary | Marked hydraulic drawing and boundary statement | Upstream and downstream points use the report label |
| Meter total | Native raw export or signed register record | Opening and closing values share one unit and device identity |
| پیکربندی | Dated device snapshot | Flow, temperature, fluid, clock, and reset settings are recorded |
| Coverage | Gap and reset log | Missing intervals and resets have an explicit treatment |
| انبار | Opening and closing storage state | The storage comparison method is stated |
| Assumptions | Versioned assumptions log | Each modeled input has an owner and source |
| Arithmetic | Locked calculation sheet | Another reviewer can reproduce the displayed result |
| Approval | Signed release note | Result, status, and limitations match the final report |
Do not overwrite a raw export. Store it as received, calculate from a working copy, and record the file hash or another controlled identifier in the ledger.
Use the site’s فهرست بررسی راهاندازی تجاری سیستمهای حرارتی خورشیدی for the initial sensor map and configuration record. Use the solar thermal O&M plan for the continuing device and service history.
Preserve the measurement chain
SOLETKS commissioning guidance uses flow and temperature rise as a heat-transfer comparison. A reproducible result also needs the fluid setting and the reporting period.
آن RESOL V40 product description illustrates a pulse-flow input used with a calorimeter and configured fluid parameters. The US Department of Energy measurement and verification options explain why a measured heat total and an estimated savings result must be labeled according to their different assumptions. These references supply method context, not site-specific accuracy or savings evidence.
Record the installed instrument’s calculation chain without substituting a generic constant:
Heat total = flow × temperature difference × configured fluid property × elapsed time
The meter performs the integration under its stored configuration. The monthly record preserves that configuration, both sensor identities, the export unit, the device clock, the reset history, and the covered period.
If a setting changes during the month, split the record into intervals. Do not join incompatible configurations into one unexplained total.
Worked calculation: derive the monthly reported result
The following arithmetic demonstrates the record structure. Every value is assumed for the example and is not a site performance result.
- Opening register = 12,500 kWh thermal. Source: assumed worksheet input.
- Closing register = 13,220 kWh thermal. Source: assumed worksheet input.
- Reported boundary heat = 13,220 − 12,500 = 720 kWh thermal. Source: arithmetic from the two assumed register inputs.
- Stipulated displaced-system efficiency = 0.80. Source: assumed worksheet input.
- Estimated avoided fuel = 720 ÷ 0.80 = 900 kWh fuel input. Source: arithmetic from the assumed heat result and efficiency.
- Additional electricity = 30 kWh, reported in a separate field. Source: assumed worksheet input.
The recommendation is to release 720 kWh thermal as the meter-derived example and label 900 kWh fuel input as a modeled estimate. The latter changes when the stipulated efficiency or displacement assumption changes. Source: this decision uses only the stated assumed inputs.
Reconcile storage and unmeasured paths
Storage input and useful delivery describe different quantities when stored energy changes during the period. Keep the opening storage state, closing storage state, auxiliary heat paths, and known unmeasured paths beside the totals.
Use this reconciliation field:
Unreconciled heat = storage input − useful delivery − change in stored energy − identified auxiliary paths
Leave the remainder labeled Unreconciled until the boundary and storage records support another classification. Do not rename it “system loss” merely to close the table.
Separate source facts, calculations, and decisions
The monthly record uses three layers:
| لایه | What belongs here | Example release status |
|---|---|---|
| Source fact | Raw register, configuration, drawing, gap log | Accepted or incomplete |
| Calculation | Difference, reconciliation, or modeled conversion | Reproducible or blocked |
| تصمیم | Reported heat, modeled fuel estimate, correction, or no result | Released, qualified, or not established |
This separation keeps a valid measured total from being treated as proof of avoided fuel. It also prevents a changed tariff, efficiency, or baseline assumption from altering the source measurement.
Correct a month without rewriting history
When a source or formula changes after release, add a correction entry. Retain the original report and record:
- the affected record ID and result;
- the reason for the correction;
- the source file or assumption that changed;
- the recalculated result;
- the approver and release timestamp;
- the reports or dashboards that need the revised value.
The correction log should make both versions traceable. Replacing the old file without a change record breaks the audit trail.
Release the monthly reporting pack
The pack is ready when it contains the source ledger, raw files, marked boundary drawing, configuration snapshot, gap and reset log, calculation sheet, reconciliation note, assumptions log, final report, and approval record.
Send the intended boundary, installed meter information, sample export, reporting period, and desired reporting decision through the صفحه تماس SOLETKS. State which entries are measured, stipulated, calculated, or modeled.
Completion condition
The task is complete when another reviewer can start from the preserved source files, reproduce the arithmetic, reach the same release status, and see every later correction without replacing the original record.