Where calculated results appear
SolarSENS presents current observations, analytical results, and prepared reporting data in different views. Two labels can look related without representing the same grain, period, or refresh state.
Before comparing values, align the plant or portfolio, date boundary, displayed grain, unit, and last-updated context.
Quick view map
Section titled “Quick view map”| View | Use it for | Displayed grain | Key labels and units | Presentation behavior | Read next |
|---|---|---|---|---|---|
| Operation Overview | Fleet status and portfolio performance comparison | Near-current status; Day Performance uses 30-minute display points; Month uses daily results | PR, PR Corrected, Actual Yield/Budget, and Availability in %; Specific Yield in kWh/kWp; energy in kWh where shown | Monthly PR and availability use their accumulated inputs, not a simple average of displayed daily percentages | Portfolio and Operation Overview, Performance ratio calculation, and Availability and energy-loss attribution |
| Plant views | Inspect plant power, energy, weather, status, and devices | Near-current and historical; chart grain depends on the selected view and range | Power in kW; energy in kWh; irradiance in W/m²; irradiation in Wh/m² | A chart can reverse export visually to show direction. This does not establish the stored sign of every grid-power value | Plant Monitoring and Metering, consumption, and grid flow |
| Insights → Overview | Compare the energy bridge across a plant or portfolio | Month or Year, with the available monthly or quarterly partition | Visible estimated loss categories: Irradiation, Overspill, Unavailability, and Soiling; energy in kWh and optional percentages | Percentages can use Budget Yield or Potential Generation as the denominator. Variance and Meter to Inverter are bridge stages, not additional attributed-loss formulas | Availability and loss analysis |
| Alarm Analytics | Investigate alarm duration, recurrence, attributed impact, and computation limits | Alarm/event rows and selected reporting scope; attributed loss is prepared from matched five-minute analytical intervals | Energy Loss in kWh and Remarks | An unavailable loss can appear as 0; interpret Energy Loss and Remarks together | Alarm Analytics and Device health, alarms, and string performance |
| String Analytics | Compare strings in the current-view position or a historical analytical snapshot | Current-view position or selected historical snapshot | String, capacity in kWp, Performance, Azimuth, Tilt, and Last Updated context | Compare strings within the same plant and snapshot; a zero can reflect a missing observation rather than a measured zero | String Analytics |
| Cleaning Analytics | Review soiling trends, cleaning history, suggestions, weather context, and estimated loss | Weekly model and trend context; daily loss can feed period summaries | Relative and soiling performance, trend/status, cleaning context, and estimated loss | Trend and suggested-cleaning results do not feed the daily loss estimate; check the displayed unit before comparing loss values | Cleaning Analytics and Cleaning and soiling analytics |
| Reports | Prepare, save, download, or review operational records | Report-specific daily, monthly, or selected period | Labels and units follow the selected report definition | Report preparation can lag analytical processing. A successful report does not prove every upstream input was complete | Reports and Data freshness and corrections |
| Public API boundary | Supply source data to processing and expose supported processed or freshness outputs downstream | Request-specific aggregation and time window | Output-specific; measurement timestamps are separate from response time | Confirm an output is a supported integration point before building on it | How SolarSENS processes plant data and Data freshness and corrections |
This guide describes the Public API only as a processing boundary. It does not define endpoints, authentication, payloads, access tiers, or an integration contract.
Current versus analytical results
Section titled “Current versus analytical results”Operation Overview and Plant views can show recent status, power, telemetry, and current-day estimates before the corresponding daily analytical result has been processed. A current value is useful for active operations; a daily or monthly value is better suited to a period comparison.
The display can use a different grain from the calculation. For example, Day Performance requests 30-minute display points even when upstream calculations use five-minute intervals. Analytical values can also change after late data or reprocessing.
See How SolarSENS processes plant data for the processing layers and Data freshness and corrections for the timestamps to compare.
Analytical views
Section titled “Analytical views”- Insights compares four currently visible estimated loss categories. Do not treat Variance as a confirmed cause.
- Alarm Analytics pairs attributed Energy Loss with Remarks. A displayed zero needs the remark and event context.
- String Analytics compares string-level snapshots. Check the selected position and Last Updated context before treating it as current confirmation.
- Cleaning Analytics combines weekly model context with cleaning and weather information; daily soiling loss is a separate downstream estimate.
Use each view to answer its own question. A status, alarm, string result, and loss estimate can support the same investigation without proving one another.
Reports and downstream access
Section titled “Reports and downstream access”Reports prepare selected indicators for an operational record. Their generation status and preparation time are separate from measurement, analytical calculation, and browser refresh time.
The Public API can participate both before and after calculation, but it is not a substitute for the view-specific interpretation guides above. When comparing an external result with a screen, first align the plant, period, aggregation, unit, and measurement timestamp.
Before comparing two values
Section titled “Before comparing two values”- Confirm the same portfolio, plant, and device population.
- Align the plant-local date and selected period.
- Confirm the displayed grain: recent, 30-minute, daily, weekly, monthly, or report-specific.
- Match the indicator variant and unit.
- Check required telemetry and configuration coverage.
- Compare measurement, calculation, publication, report, or Last Updated context where available.
- Treat page reload or API response time as retrieval time, not proof that upstream processing completed.