String Analytics

Use String Analytics to compare strings within a plant and investigate performance differences across available analytical positions. Access depends on your role, subscriptions, and whether the plant has the required string configuration and data.

For the difference between string analysis, device health, and alarms, read Device health, alarms, and string performance.

Choose the analysis context

The example is illustrative. Use it to find the controls and see how the map, filter, timeline, and table work together.

1. Open Insights → String Analytics.
2. Select the plant and analysis type available for your investigation.
3. Review the displayed context, which can include:
   • Azimuth
   • Last Cleaned
   • Referenced Date
   • Last Updated
4. Use the position slider to move through available historical positions or select LIVE for the current position offered by the view.

Use the analysis type selector to choose the question you want to answer:

Analysis type	What it shows	Use this when
Current / Yesterday	String current from the most recent completed analytical day in the selected snapshot.	You want to spot strings with unusually low or high current before checking device status and telemetry.
Normalized Power / Yesterday	A capacity-aware production comparison for the selected result.	You want the main performance comparison across strings with different capacities.
Cleaning / Relative After Cleaning	Performance relative to the last cleaning context when that mode is available.	You want to check whether string performance changed after cleaning. This mode is shown only in the current view.

Keep the analysis type fixed when comparing results. Different analysis types answer different questions, so changing the type can change the ranking even when the plant and snapshot stay the same.

LIVE identifies the current position in String Analytics. It is not a guarantee that every underlying input is realtime or that the result was recalculated when the page opened.

Historical snapshots are available only when the plant has stored snapshots for the recent completed days shown by the slider. In a historical snapshot, String Analytics uses the current plant layout with the selected day’s stored metrics. If a string exists in the current layout but not in that snapshot, its metric can appear blank or unavailable.

Read the string table

After the context is fixed, use the map to find a pattern and the table to confirm the details.

Part of the view	How to read it
Color bands	Start with the lower-score groups, then compare them with nearby higher-score strings.
Range filter	Limit the map to the score range you want to inspect.
Snapshot timeline	Move through the available days to see whether the same string or area keeps appearing, or whether the difference looks like a one-day effect from shading, soiling, or weather.
String table	Confirm the string metadata: name or label, capacity, score, azimuth, and tilt before comparing the result with other data.

The desktop and mobile tables can show:

Field	How to use it
String	Identify the string in the selected plant context.
Cap. (kWp)	Compare strings with their configured capacity in mind.
Performance	A comparative score — rank strings within the same analysis type and position rather than reading it as an absolute measurement.
Azimuth (°)	Account for orientation before comparing strings.
Tilt (°)	Account for module tilt before comparing strings.

Do not compare the Performance field in isolation. Use it to rank strings within the same plant, analysis type, and snapshot, not as an absolute measurement. A low score is a triage signal: it helps you find strings to inspect, but it does not by itself prove a disconnected string, a hardware fault, or an energy-loss value.

When a pattern repeats across the timeline, compare the same period with device status, alarms, cleaning history, and detailed telemetry before assigning a cause.

Investigate a difference

1. Fix the plant, analysis type, reference date, and analytical position.
2. Compare strings with similar capacity, azimuth, and tilt.
3. Check Last Updated before treating the result as current.
4. Treat a blank, unavailable, or very low value as a candidate for investigation, not as proof of a measured zero.
5. Compare the result with device status, alarms, cleaning history, and detailed telemetry for the same period.
6. Confirm the pattern before assigning a physical root cause or maintenance action.

For example, a device may currently appear offline while String Analytics still shows an older analytical position. Check the timestamps instead of treating the string result as confirmation of the current device state.

When source data was incomplete

String Analytics is a readback and investigation view. Opening the page does not recalculate source data or refresh related reports.

If the result looks wrong because the source data for the day was incomplete, record the affected plant, date, analysis type, snapshot, and Last Updated time. Compare the same String Analytics context after the data has been corrected or refreshed. For the general correction model, read Data freshness and corrections.

Export analytical data

Select the CSV export action to save the currently selected analytical result. Record the plant, analysis type, reference date, position, and Last Updated context with the export so another operator can reproduce the comparison.

The string table has no energy-loss or monetary-loss columns — the Performance field cannot be converted into either.

Export inverter heatmap data

Use the inverter heatmap when you need a spreadsheet view of performance values by time bucket and device.

1. Open Insights → Heatmap.
2. Select a plant, device type, period, and date.
3. Choose Yield, Specific Yield, or Temperature, then select Generate.
4. Select the download icon labelled Export heatmap as CSV.

The export uses one row for each time bucket and device combination. Its columns are:

Column	Exported label
Time bucket	Time Bucket
Device	Device
Specific yield	S. Yield (kWh/kWp)
Yield	Yield (kWh)
Temperature	Temperature (°C)

The filename includes the selected plant, period, device type, selected date, and the export timestamp so you can identify the context later.

Related guides

• Plant Monitoring
• Cleaning Analytics
• Device health, alarms, and string performance