Fault detection and tickets
How fault alerts become work orders your team can execute and audit.
NuraVolt classifies inverter and string anomalies into faults, and every fault can open an O&M ticket. Tickets move through a validation workflow: NEW, then VALIDATED, ASSIGNED, IN_PROGRESS and DONE, with comments, history and revenue impact estimates attached. AI narration can draft the ticket summary; a person approves it.
From anomaly to ticket
- Detection: rule-based and model-based checks flag underperformance, thermal anomalies and failures.
- Interpretation: each alert carries an explanation and an estimated energy and revenue impact.
- Ticketing: alerts open tickets, or your team creates them by hand. Every ticket keeps its trigger and history.
The ticket workflow
| Status | Meaning |
|---|---|
| NEW | Created, awaiting review. |
| VALIDATED | A person confirmed the issue is real. |
| ASSIGNED | A technician or crew owns it. |
| IN_PROGRESS | Work started on site. |
| DONE | Resolved and closed. |
Validation is deliberate: nothing is dispatched purely on a model score. Priorities weigh estimated revenue impact so the most expensive faults surface first.
Frequently asked questions
See also
See this on your own plants
NuraVolt turns your SCADA and BMS data into early fault detection, degradation-aware BESS analytics, and audit-ready reporting. A fixed-scope audit shows you what we’d find on your portfolio.