Terms & Concepts

Creating custom solar simulations involves key inputs that define how the PV system will be modeled to behave in the real world. To make working with the API easier, this section explains some of the more complex topics you might come across.

Energy Sites

PV Systems

The Solar Simulations API requires the client to define a PV system. This PV system is made up of modules and inverters that are wired together in specific configurations. The PV system will output power at the point of interconnection (to the electric grid or to energy storage). The Solar Simulations API models the amount of power that this PV system is outputing. The PV system components will define how the PV simulation model calculates alternating current (AC) power and AC energy from the irradiance and weather data. PV system modules output direct current (DC), which is then converted to AC by the inverter. See sections on Inverter, PV Modules and Array Configuration for more information on how these specific inputs impact the PV simulation.

System Losses/Derate

CprPVForm applies a general derate of 85% to simulation outputs to represent losses not explicitly accounted for in the Simulation tool. CprPVForm total losses are calculated using the following equation:

Total System Losses = General System Losses x Inverter Efficiency (%) x PTC Rating (kW) x Shading x Degradation

The general derate percentage, inverter efficiency, PTC rating, and shading values are PvSystems elements. To specify a general derate percentage, insert GeneralDerate_Percent=”{int value}” into the PvSystem details. A degradation factor of 0.5% per year is considered in all Clean Power Research simulations and cannot be modified.

Inverters

The inverter is a component of the PV system. Each inverter is wired to a set of PV modules and converts the DC output of the module into AC power. The PV power model used in the Solar Simulation API requires that the client pass information about the number (Count), maximum rated power (MaxPowerOutputAC_kW) and rated efficiency (EfficiencyRating_Percent) for each inverter. For a mapping of the inverter model to the necessary input ratings, see the CEC inverter list.

PV Modules

The PV module is a component of the PV system. Each PV module converts incident irradiance under the ambient weather into DC output, which the inverter then converts to AC power. The PV power model used in the Solar Simulation API requires that the client pass information about the number (Count), nameplate DC rating (NameplateDCRating_kW) and performance test conditions AC rating (PtcRating_kW) of the PV module. The client can also specify the temperature rating (PowerTemperatureCoefficient_PercentPerDegreeC) and nominal operating cell temperature (NominalOperatingCellTemperature_DegreesC) of the module, if desired. If the client leaves these two optional fields blank, the defaults are set to:

  • PowerTemperatureCoefficient_PercentPerDegreeC="0.4
  • NominalOperatingCellTemperature_DegreesC="45"

For a mapping of the inverter model to the necessary input ratings, see the CEC module list.

PTC Rating

This value reflects the expected performance of the PV module when operating in an environment with 1,000 W/m2 of solar irradiance, an air mass of 1.5, and an ambient temperature of 20°C at 10 meters above ground level with a wind speed of 1 meter per second. Additionally, the operating cell temperature is raised to 45°C in PTC tests.

PTC are considered more representative of real-world operating conditions. The CprPVForm model uses PTC rating to account for PV module performance. The module PTC rating is a PvSystems element. To specify the PTC rating, insert PtcRating_kW =”{Integer Value}” into the PvModule details.

Array Configuration

The array configuration specifies parameters about the PV system that define how the system is installed. The array configuration inputs are important to the PV simulation model as they help determine what the incident irradiance is on the plane of the PV module array, and can have a significant impact on the PV simulation accuracy. The PV power model used in the Solar Simulation API requires that the client pass information about the tilt angle from horizontal (Tilt_Degrees) and azimuth angle (Azimuth_Degrees) in which each set of PV modules is installed. For residential systems, the tilt angle often is specified by the roof pitch. The azimuth angle is a reference to the Cardinal Direction that the array of PV modules is facing. The Solar Simulations API uses 180-degrees as South reference (90-degrees is East and 270-degrees is West). The client can also specify the type of tracking system on which the PV modules are mounted (Tracking), the rotation limit of the tracker (TrackingRotationLimit_Degrees), the number of rows of modules (ModuleRowCount) and the relative module row spacing (RelativeRowSpacing). 

Tracking

The Clean Power Research simulation API supports fixed, single axis and dual axis tracking PV systems. Tracking is a PvSystems element. To specify tracking type, insert Tracking =“Fixed”, Tracking=“SingleAxis”, or Tracking=“DualAxis” into the ArrayConfiguration details.

Relative Row Spacing/Ground Coverage Ratio

Relative row spacing is the inverse of the ground coverage ratio (GCR) and can be calculated as the ratio of row-to-row pitch to array length. A lower GCR (higher relative row spacing) means wider row spacing and a higher GCR means narrower row spacing. Typical utility scale PV systems have GCRs in the range of 0.3 to 0.6. The default value of relative row spacing used in the SolarAnywhere Energy Simulations Model is 3, which is equal to a GCR of 0.3. To specify row spacing, insert RelativeRowSpacing = "{Decimal Value}” into the ArrayConfiguration details.

 

Figure 1: Relative row spacing.

 

PV Simulation

PV Simulation Tool

The Clean Power Research Solar Simulations tool is a web-based service that generates PV system production data. The tool has been designed with a modular architecture to allow user flexibility in selecting from a range of input models for weather data, shading and PV power calculations as shown in figure 1. The Solar Simulations tool supports the use of SolarAnywhere and TMY3 weather data.

Figure 1: SolarAnywhere simulation modular software architecture.

 

Shading Models

The Solar Simulations tool supports two shading and obstruction models that can be input into ShadingOptions as ShadingModel="ShadeSimulator" or ShadingModel="MonthlyPercentSolarResource".

Shade Simulator 

The shade simulator model uses information about obstructions surrounding the PV system to modify simulated output. Obstructions can be objects such as trees or adjacent buildings that shade the PV system at certain times of day.

 

Figure 1: The interaction of a shading object with a PV system.

 

Specifying obstructions for the ShadeSimuator model requires an input combination of azimuth, elevation, and opacity for each obstruction in relation to the position of the PV system. The distance and height of shadow-casting objects can be calculated using a site plan and sun path diagram or shading analysis software coupled with digital photography. The azimuths of the obstructions can be calculated directly from the site plan or sketch. The opacity or transmission factor specifies the amount of solar radiation passing through the shading objects.

The azimuths, elevations, and opacities of solar obstructions are PvSystems elements and can be specified at the time of creating an energy site using the Clean Power Research simulation API.

The shade simulator uses the azimuths, elevations, and opacities of the obstructions to generate a digital elevation model (DEM). This is an internal, three-dimensional model of the obstructions surrounding the PV system that is used to modify simulation outputs based on the time of day.

 

Figure 2: The solar obstruction profile determined using a DEM.

 

Monthly Percent Solar Resource

The MonthlyPercentSolarResource shading model is useful when details about the surrounding obstructions (buildings, trees, etc.) are unknown. This model applies monthly solar access percentage derate factors to hourly simulation outputs to account for the effect of shading on PV system production.

The solar access percentage can be calculated as the ratio of incident solar energy on the shaded PV panel to the incident solar energy on the un-obstructed PV panel.

 

Figure 3: The percentage of solar energy available at each month for the site-specific shade conditions.

 

 

Monthly solar access percentages are PvSystems elements and can be specified at the time of creating an energy site using the Clean Power Research simulation API.

Time Stamps

The simulation request time stamps indicate the start and end period for which the client wishes to return data. Time stamps are absolute and follow the ISO 8601 convention. For example, if the client wishes to request data from January 1, 2020 at 11:00 AM Pacific Standard Time to January 2, 2020 at 12:00 PM Eastern Standard Time:

  • StartTime ="2020-01-01T11:00:00-08:00"
  • EndTime="2020-01-02T12:00:00-05:00"

Time stamps are all handled as an absolute reference, so if the client wishes to request forecast data, they will need to create a time stamp for a future time from the present. Forecast data can be requested up to 90-days ahead. Short and medium term forecast models apply for forecast horizons of 1-minute up to 168-hours (7-days) into the future. Climatology models are applied starting on day 8 out to 90-days. Time stamps with a different GMT offset in the StartTime and EndTime will be synchronized in the response to the time zone of which the site location falls.

Irradiance and Weather Data

In the Simulation request, the client will specify their desired irradiance and weather data source. To see all of the available irradiance and weather data source options, view the irradiance & weather data options page.

For example, use WeatherDataSource="SolarAnywhere3_4" to request SolarAnywhere time series data with model version 3.4 as the source for the PV simulation. When requesting time series data, specify a StartTime and EndTime. Use WeatherDataSource="SolarAnywhereTGY2019" to request a typical global horizontal irradiance (GHI) year constructed using the methodology discussed at the in-depth methodology page of the SolarAnywhere website.

What’s Next?