Active observations
7
Sample portfolio
Solar intelligence for O&M teams
ArraySignal helps solar O&M providers separate probable equipment issues from data problems, inspect supporting evidence, and prioritize the work most likely to affect production.
ArraySignal reference experience
A sample diagnostic workflow showing probable classifications, persistence, and recommended review order.
Active observations
7
Sample portfolio
Critical review
1
Highest priority
Potential lost energy
180 MWh
Modeled estimate
Inverter 04 underperformance
Phoenix · peer deviation
Persistent production variance
Denver · 4 days
Telemetry interval gap
Raleigh · impact unknown
Fictional site names and illustrative values—not customer telemetry. These values do not represent guaranteed savings or unreleased functionality.
The operational problem
O&M teams often receive disconnected alarms and production signals without enough context to distinguish urgent generation loss from telemetry noise or normal operating behavior.
Threshold alerts can multiply without explaining persistence, peer behavior, or likely impact.
Technicians must manually assemble production, weather, inverter, and data-quality evidence.
Severity alone does not show which issue has the strongest evidence or potential energy consequence.
Workflow
Deterministic analysis organizes the signal before a technician commits time or travel to a site.
Identify persistent deviations during valid production periods.
Distinguish data-quality faults, outages, clipping, and underperformance signals.
Review peer behavior, expected output, duration, and confidence evidence.
Order inspection work by severity and modeled energy impact.
Relevant capabilities
Use deterministic rules and time-series evidence to identify probable—not confirmed—fault categories.
Compare components with their peers to surface localized production separation.
Expose missing intervals, invalid measurements, and communications conditions without inventing loss.
Use recommended inspection context to shape a more focused maintenance queue; full work-order integration is future direction.
Potential outcome
A clearer evidence trail could help O&M teams triage alarms more consistently, prepare better-informed site visits, and communicate uncertainty before action is taken.
ArraySignal surfaces probable causes and recommended inspection steps. It does not claim a field-confirmed diagnosis without confirmation data.
Frequently asked questions
No. It presents probable classifications, supporting evidence, and confidence. Field inspection, event logs, or additional measurements are still required to confirm a fault.
Nighttime zero production is excluded from outage classification. Detection rules evaluate valid production windows and relevant operating context.
No. The analytics are designed to recognize normal clipping behavior and avoid automatically labeling it as equipment failure.
Not yet. The initial MVP supports CSV telemetry and keeps vendor ingestion separate from analytics. Vendor APIs and work-order integrations are not presented as currently available.
Request demo
Request a demo to review how telemetry quality, probable fault evidence, and maintenance priority could fit your O&M process.
ArraySignal is in early access. The walkthrough uses fictional reference sites and demonstration analytics—not customer data.
A focused walkthrough
Tell us about your role, portfolio scale, monitoring platform, and primary challenge. After your request is saved, the next step will present scheduling when a provider is available.