PLATFORM / 05 / OPERATIONS

From alert to resolution.

DYNVOLT routes severity-classified alerts directly into tickets, tickets into KPIs, and KPIs into stakeholder-ready reports. Detection is peer-relative, gated by multi-day persistence — and tickets close themselves when the fault clears.

Request a demo See reports

< 30s

Alert latency (30s polling)

70%

Peer-deviation threshold

Multi-day

Persistence before ticketing

Auto-close

When the fault clears

CLOSED-LOOP O&M

Tickets that close themselves.

When the underlying fault clears, DYNVOLT marks the ticket resolved automatically. No more dangling open tickets. No more manual reconciliation.

!
Severity classification — Critical / High / Medium / Low.
A
Auto-assignment — by site, asset class, or skill matrix.
⌬
Work orders in the field — the work-order UI is a responsive web app; crews open and close tickets with comments from any phone browser, nothing to install.
K
Work orders with asset tags — every ticket carries the string, inverter, or sensor it belongs to, so KPIs roll up per asset.

operations · alerts · tickets

DYNVOLT O&M — severity-sorted alert queue with ticket detail and resolution status

DETECTION CLASSES

Peer-relative detection. Tuned on our own plants.

A string must fall below 70% of its same-orientation peer average, persist across multiple days, and survive curtailment suppression before a ticket opens — running across 840+ monitored strings in production today. Our early threshold-based versions flooded operators with false positives — we redesigned detection peer-relative because we measure ourselves too.

PV string health

Peer-relative underperformance, soiling, expected-vs-measured current deviation, I-V degradation.

INV

Inverter faults

Trip events, derate watchdogs, communication loss, fan failures, insulation self-trips.

Grid events

Export-limit excursions, curtailment tracking, PCC monitoring.

BESS alarms

ESMU and PCS alarm decode at register level — validated against hardware as commissioning completes.

Sensor & meteo faults

EMI weather-station faults, irradiance and temperature sensor loss, stale-data watchdogs.

FAQ

Operations — frequently asked

Can't find what you're looking for? Talk to our team →

Does DYNVOLT replace my CMMS?

No — we expose a REST API and webhooks you can integrate with your CMMS (documented at developers.dynvolt.com). Tickets created from alerts carry full asset context. Pre-built connectors for specific CMMS products are on the integration roadmap, prioritised by customer demand — tell us which one you run.

How are alerts prioritized?

Detection is peer-relative rather than threshold-based — a string must fall below 70% of its same-orientation peer average, persist across multiple days, and survive curtailment suppression before a ticket opens. Severity is then classified Critical / High / Medium / Low. Ranking by revenue at risk is on our roadmap.

What detection ships out of the box?

Peer-relative string underperformance, expected-vs-measured current deviation, I-V and soiling analysis with multi-day persistence, per-inverter derating watchdogs, sensor-fault detection, and BESS alarm decode — built and tuned on our own production plants, where the real catches on record include string underperformers, inverter insulation self-trips, and failed weather sensors.

Can field techs use it on mobile?

Yes — the work-order UI is a responsive web app: crews open and close tickets with comments from any phone browser, nothing to install. A dedicated native field app is on the roadmap; the web app covers field work today.

Platform

Resources