Understanding your dashboard

The landing view after sign-in. One row or card per plant with its capacity, current status, and headline indicators, so you can see across the fleet which sites need attention before opening any of them. Plants you cannot access under your role or per-plant permissions are not shown.

Each plant page opens on an overview: production against the expected value from the plant’s digital twin, recent alerts, and the state of its data connections. The expected-versus-measured comparison is the backbone of most NuraVolt analytics, since deviations from expected output are what the soiling and fault models explain.

The soiling section shows the estimated soiling ratio per inverter and for the plant, a 365-day forecast of how it will evolve, and the cleaning optimiser’s recommended cleaning dates with their expected return. Every estimate carries a model version label so you can tell provisional from mature figures.

The faults section lists active and historical fault detections: what was detected, on which device, the supporting signal evidence, and the severity. From any detection you can open a ticket to hand it to the O&M workflow.

Tickets track maintenance work from detection to closure through a fixed workflow: NEW, VALIDATED, ASSIGNED, IN_PROGRESS, DONE, with WONT_FIX for detections you decide not to act on. Each ticket keeps its comments and a full status history.

The data hub is where connections live: their health, last successful poll, and field mappings, plus the wizard for onboarding new plants and sources. Settings covers the organisation profile, team and roles, MCP API keys, and billing.