> For the complete documentation index, see [llms.txt](https://docs.net2grid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.net2grid.com/net2grid-energy-ai-cloud-interface-specifications/daily-consumer-intelligence/output/solar-production-metrics.md). # Solar Production Metrics ## Solar Production Metrics The **Solar Production Metrics Report** provides a detailed view of an installation’s **daily solar energy production**. The report answers questions such as: > “How much energy did the solar panels produce during the day and how efficiently did they operate?” The report is generated whenever new measurement data is uploaded. *** ### Key Characteristics * **Per-day production estimation**\ The report provides solar production metrics for a specific reporting day. * **Production & efficiency insights**\ Includes key indicators such as: * total daily production * hourly production * peak production * overproduction percentage * efficiency metrics * **Inverter-agnostic approach**\ No direct inverter integration is required. * **NET2GRID EnergyAI® estimation**\ Production values are estimated using disaggregation algorithms. *** ### Understanding the Data The report provides the following key metrics: * **Daily Production**\ Total estimated solar energy production for the day (kWh) * **Per Hour Production**\ Per-hour estimated solar energy production for the day (kWh) * **Overproduction Percentage**\ Percentage of time during which solar production exceeded consumption * **Peak Production Value**\ Maximum active power recorded during the day (W) * **Peak Production Timestamp**\ Time at which peak production occurred * **Efficiency (Monthly / Annual)**\ Relative performance of the installation compared to its historical best production *** ### Report Generation Logic * The report is generated whenever new measurement data is uploaded * If measurements are received for a past day, the system regenerates the report for that specific reporting day This ensures that the report always reflects the latest available data. *** ### Requirements The Solar Production Metrics Report is generated only if: * Measurement data is available for the reporting day * Electricity **returned to the grid** (CSR) measurements have been uploaded for the installation *** ## Technical Specifications ### Storage Location The Solar Production Metrics reports are generated under the S3 export bucket using the following format: `s3://{exportBucket}/{labelpartner}/reports/{installationIdentifier}/{serviceType}/solar-production-metrics/{filename}` #### Path Parameters * **exportBucket**: the name of the AWS S3 bucket that contains the reports * **labelpartner**: the identifier of the label partner * **installationIdentifier**: the external installation identifier provided during provisioning * **serviceType**: SM (low-resolution measurement data) #### Filename Format `{internalInstallationIdentifier}_{reportDate}_solar_production_metrics.json` Where: * **internalInstallationIdentifier**: the internal installation identifier used in NET2GRID EnergyAI® * **reportDate**: the date in `YYYYMMDD` format for which the report was generated *** ### Report Format The report is provided in **JSON format**. #### Main Fields | Field | Type | Description | | ---------------------- | ------ | ---------------------------------------------------------------------- | | date | string | The reporting date in `YYYYMMDD` format. | | error | string | Error code returned for the report. | | timestamp | long | UNIX timestamp (milliseconds) indicating when the report was produced. | | version | string | Service version, e.g. `2.3`. | | solarProductionMetrics | object | Object containing solar production metrics. | *** #### SolarProductionMetrics Object | Field | Type | Description | | ------------------------ | ------------ | ------------------------------------------------------------------------ | | dailyProduction | double | Total estimated solar production for the day, in kWh. | | peakTime | long | Timestamp of peak solar production (UNIX seconds). | | peakValue | integer | Peak active power value (W). | | overproductionPercentage | double | Percentage of time during which production exceeded consumption. | | efficiencyAnnual | double | (Optional) Efficiency compared to best annual production. | | efficiencyMonth | double | (Optional) Efficiency compared to best monthly production. | | perHour | double array | 24-length array containing hourly solar production (kWh), in local time. | *** **Notes** * `timestamp` is expressed in **milliseconds** * `peakTime` is expressed in **seconds** * All timestamps refer to the installation’s local timezone *** ### Example Report File A report may be generated in a location such as: `s3://s3-export-ABC/labelpartnerB/reports/installationX/SM/solar-production-metrics/abc123456_20230519_solar_production_metrics.json` Example contents: ```json { "date": "20230519", "error": "null", "timestamp": 1684777690568, "version": "2.3", "solarProductionMetrics": { "dailyProduction": 16.543, "peakTime": 1684496700, "peakValue": 2902, "overproductionPercentage": 57.323, "efficiencyAnnual": 0.689, "efficiencyMonth": 0.755, "perHour": [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.073, 0.022, 0.025, 0.604, 2.54, 2.8, 2.545, 1.91, 2.447, 2.023, 1.167, 0.314, 0.06, 0.002, 0.0, 0.0, 0.0, 0.0 ] } } ``` *** ### Notification Mechanism A message is published when a report is generated. Queue: `solar_production_metrics_{labelpartner}` #### Message Format ```json { "bucket": "s3-export-customerA", "filename": "/labelpartnerB/reports/installationX/SM/solar-production-metrics/abc123456_20230519_solar_production_metrics.json" } ``` Routing key: `{installationIdentifier}.solar_production_metrics` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.net2grid.com/net2grid-energy-ai-cloud-interface-specifications/daily-consumer-intelligence/output/solar-production-metrics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.