Raptor Maps

The Raptor Maps Knowledge Hub

Welcome to the Raptor Maps knowledge hub. You'll find guides and documentation to help you start working with Raptor Maps as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Calculating impact of anomalies and power factors

The Findings table of the Raptor Maps report provides insight into the impact of anomalies on solar site power production:

For each anomaly type, the table calculates the estimated impact by multiplying the number of modules affected, the peak power of the solar module at STC (Standard Test Conditions), and a power factor ranging from 0 to 1 specific to the anomaly.

  • Each cell anomaly impacts the power of the associated module, so for each cell anomaly, there is associated impact on the module, represented by the number of modules affected.

  • The peak power of the solar module at STC takes into account the specific module installed at the site, as the standard output of a module (in watts) varies by manufacturer and model.

  • The power factor serves to reflect that, for example, a string outage will have much greater impact on overall power production than a cell outage.

To review or adjust the power factor default values, click on the down arrow to the right of your username, then click on the cogwheel.

Note: This action requires administrator privileges.

From the page that displays, click on the tags icon on the left:

A page displays the default power factor for each anomaly:

If, in your experience, anomaly types have higher or lower impact on affected power, adjust the power factor to more accurately estimated impact.

Note. If you are managing solar inspections for multiple clients, any adjustments you make to Power Factors will change the affected power calculations associated with the Findings table for all new and existing reports.

Updated 7 months ago

Calculating impact of anomalies and power factors

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.