String-level degradation is the most expensive performance loss at utility-scale solar plants — not because the damage is severe per string, but because it compounds silently across hundreds of strings for months before anyone investigates why output is falling short of forecast. A single underperforming string represents a fraction of a percent of plant output. Three hundred underperforming strings across a 100 MW facility represent a 15–25% revenue gap that no SCADA threshold alarm ever surfaces because each individual string stays just below the alert threshold. OxMaint's solar analytics platform tracks string-level performance deviation against irradiance-corrected baselines continuously, calculates the cumulative revenue impact of degraded strings across your entire portfolio, and generates the maintenance work orders that stop the silent revenue leak — before your next quarterly review confirms it on paper.
Why SCADA Thresholds Miss String Performance Problems
SCADA alarm thresholds are set at failure levels — they trigger when something breaks, not when it degrades. A string producing 18% below weather-normalized baseline is not a failed string; it is a string with a dirty combiner connection, a micro-cracked cell cluster, or a developing bypass diode fault. It will never cross the SCADA alarm threshold. It will produce at 82% of expected output for the next two years and your SCADA dashboard will show it as green.
Track String Performance Where Your SCADA Dashboard Stops
OxMaint benchmarks every string against irradiance-corrected baselines, quantifies degradation in revenue terms, and generates maintenance work orders when deviation exceeds threshold — automatically, continuously, across your entire portfolio.
OxMaint String Analytics: What Gets Tracked and How
String Performance Reports Your O&M Team and Asset Managers Both Need
Frequently Asked Questions
How does OxMaint differentiate genuine string degradation from weather-related output variation?
OxMaint applies weather normalization to every string baseline — correcting for measured irradiance, ambient temperature, and the plant's soiling rate model before comparing actual output to expected output. This isolates genuine equipment underperformance from the weather variability that masks performance ratio calculations on overcast or high-temperature days. Start a free trial to see weather-normalized deviation tracking applied to your plant's string data from the first week of connection.
Can OxMaint analytics support warranty claims for underperforming modules?
Yes. OxMaint tracks degradation rate per string section against the manufacturer's annual degradation guarantee — typically 0.5% per year. When a string's measured degradation rate exceeds the warranted rate, OxMaint generates a flagged report with the irradiance-corrected output trend, deviation magnitude, and cumulative energy loss calculation formatted for warranty claim submission. Complete maintenance records are linked to each string's asset profile to support the claim. Book a demo to see the warranty flagging workflow in action.
How does OxMaint handle string analytics across a multi-site portfolio?
OxMaint's portfolio analytics dashboard aggregates performance ratio, string fault count, and degradation rate across all sites on a single screen — with drill-through from portfolio view to individual string performance in the same workflow. Asset managers can identify which sites have the highest revenue impact from string degradation and prioritize maintenance interventions by financial return, not by alert count.
What data sources does OxMaint require to run string performance analytics?
String-level DC voltage and current data from combiner boxes or string-level monitoring hardware, irradiance and temperature from on-site weather stations, and inverter AC output are the minimum inputs for performance analytics. Most utility-scale plants already have these data sources available via SCADA or the plant monitoring platform. OxMaint connects via Modbus, SunSpec, or REST API without requiring additional hardware. Thermographic inspection results and historical cleaning records can be imported to enhance root cause classification.
How does OxMaint's string analytics translate performance deviation into maintenance priorities?
OxMaint ranks underperforming strings by revenue impact — calculated as the deviation from weather-normalized expected output multiplied by operating hours and energy price. The maintenance work order queue is sorted by estimated revenue recovery per repair event, so technicians address the strings where intervention will have the largest financial return first. This prioritization replaces manual fault log review and eliminates the guesswork from O&M resource allocation across a large string count.
Stop Letting String Degradation Drain Your Plant's Revenue Silently
OxMaint tracks string performance, quantifies revenue impact, and generates maintenance priorities automatically — across every string in your portfolio, every day. Most plants see their first actionable string deviation report within the first week of connection.
