Solar intelligence for O&M teams

Turn solar performance anomalies into a focused investigation queue.

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.

  • Surface probable faults with explainable evidence
  • Keep communications gaps separate from confirmed outages
  • Prioritize investigation before dispatching field work
O&M investigation view
Sample data

ArraySignal reference experience

Prioritized issue queue

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

Priority signalStatus / impact

Inverter 04 underperformance

Phoenix · peer deviation

Critical

Persistent production variance

Denver · 4 days

Investigate

Telemetry interval gap

Raleigh · impact unknown

Data issue

Fictional site names and illustrative values—not customer telemetry. These values do not represent guaranteed savings or unreleased functionality.

The operational problem

Alert volume does not tell technicians where to look first.

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.

01

Noisy alert streams

Threshold alerts can multiply without explaining persistence, peer behavior, or likely impact.

02

Slow fault investigation

Technicians must manually assemble production, weather, inverter, and data-quality evidence.

03

Unclear maintenance priority

Severity alone does not show which issue has the strongest evidence or potential energy consequence.

Workflow

Move from deviation to evidence-backed inspection.

Deterministic analysis organizes the signal before a technician commits time or travel to a site.

  1. 01

    Detect

    Identify persistent deviations during valid production periods.

  2. 02

    Separate

    Distinguish data-quality faults, outages, clipping, and underperformance signals.

  3. 03

    Investigate

    Review peer behavior, expected output, duration, and confidence evidence.

  4. 04

    Prioritize

    Order inspection work by severity and modeled energy impact.

Relevant capabilities

The product capabilities that matter most to O&M Providers.

Demonstrated

Explainable fault detection

Use deterministic rules and time-series evidence to identify probable—not confirmed—fault categories.

Demonstrated

Inverter relative performance

Compare components with their peers to surface localized production separation.

Demonstrated

Data-quality diagnostics

Expose missing intervals, invalid measurements, and communications conditions without inventing loss.

Product direction

Maintenance prioritization

Use recommended inspection context to shape a more focused maintenance queue; full work-order integration is future direction.

Potential outcome

Spend less investigation time on noise and more on supported operating issues.

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.

  • More consistent remote triage
  • Better-prepared technician investigations
  • Clear separation of telemetry and production faults

ArraySignal surfaces probable causes and recommended inspection steps. It does not claim a field-confirmed diagnosis without confirmation data.

Frequently asked questions

Questions from O&M Providers.

Does ArraySignal automatically confirm equipment faults?

No. It presents probable classifications, supporting evidence, and confidence. Field inspection, event logs, or additional measurements are still required to confirm a fault.

How does it handle nighttime zero production?

Nighttime zero production is excluded from outage classification. Detection rules evaluate valid production windows and relevant operating context.

Will normal inverter clipping be treated as a failure?

No. The analytics are designed to recognize normal clipping behavior and avoid automatically labeling it as equipment failure.

Does the MVP connect directly to every monitoring vendor or CMMS?

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

Bring a real investigation workflow to an ArraySignal walkthrough.

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

Start with a few portfolio details.

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.

  • Takes about two minutes
  • Preserves your original campaign attribution
  • No promotional-email opt-in required
Book a Demo