本页未翻译。您正在浏览的是英文版本。
For saving project sites in Prospect you just need to follow these simple steps:
In order to obtain PV electricity yield estimate and overview of system losses, it is required to add a PV configuration to your project. The first step is to select a system type.
Once the preferred system type is selected, you have several options:
As a final step, for applying changes click on the button Save and calculate PV electricity.
There are two ways of putting the info of the system size in Prospect:
Both values are related in Prospect with a reference ratio of 6468 m² of modules area for 1MWp installed capacity. This is equivalent to a PV module efficiency of 15,46% on standard conditions.
Please note the area of installed modules does not represent the total ground area covered by the PV field, which will be larger due to spacing between rows.
One of the inputs for PV project setting in Prospect is the relative row spacing, which is defined by the ratio of distance between the neighboring PV table legs and PV table width (see below picture).
It was established that row spacing must be planned in order to limit shading of a module row on another. The row spacing can have an impact not only on the irradiation falling on the panels, but also create shading effects that can result in yield losses.
Example: x2=2000 [mm] x3=5000 [mm], Relative Row Spacing = 5000/2000 = 2.5
Figure: Calculation of relative row spacing value (= x3/x2).
Prospect app offers the following system types:
By default, a DC/AC ratio of approx 1.2 is used in simulations done in Prospect. There are small nuances depending on the configuration that are chosen, but this varies very little. The DC/AC ratio depends on the module type, inverter type, installation size, etc.
The current target was to set it close to 1.2 to avoid inverter clipping. We are planning to implement a feature to allow users to adjust this ratio.
Soiling loss of 3% is used as default value in the PV system configuration. Currently, it is only a suggestion and you can edit it. Instead of using a single annual input you can also consider specific values for each month.
We are planning to add this parameter later into our maps and database, thus it will be tailored to site specific conditions.