Open almost any solar portfolio review and you will find the same artefact at the centre of it: a screen full of live readings. Grid power, PV output, battery state of charge, a chart that updates every few seconds. It looks like control. It is treated as proof that the asset is being looked after. It is not. A dashboard reports the present. It does not investigate why the present looks the way it does, it does not diagnose what is wrong, and it does not act to change the outcome. Those are three separate jobs, and a screen does none of them.
This matters most to the people who own a fleet of these assets, because the gap between watching and managing scales with every site you add. One dashboard you can stare at. Forty dashboards you cannot. The question is not whether you can see the data. It is whether anyone is doing anything with it.
What a dashboard is actually for
A dashboard answers one question well: what is happening right now. That is a real and useful function. You can see that a site is online, that the battery is charging, that yesterday produced less than the day before. For a single asset, an attentive owner can sometimes infer the rest by eye.
The trouble starts when watching is mistaken for managing. Seeing that production dropped is not the same as knowing why. Seeing the battery sit at a low state of charge through the evening peak is not the same as understanding that its dispatch windows were tuned to a tariff that no longer exists. The screen shows the symptom. It is silent on the cause, and it is silent on the fix. Someone, or something, still has to close that distance.
The four jobs the screen cannot do
At Soluno the working asset lifecycle runs in four steps: investigate, then watch, then root cause, then optimise. A dashboard occupies the second of those four and stops there. The value lives in the other three.
Investigate. Before anything is watched, the asset has to be understood against what it was modelled to deliver. What load does this building actually carry, on which tariff, with what demand profile, and how does that compare to the dispatch logic it was commissioned with. A live readout assumes the question is already settled. Usually it is not.
Root cause. When a reading drifts, the screen tells you it drifted. It does not tell you whether the cause is a degraded battery, a tariff restructure, a changed load, a tripped fault code, or a dropped connection. Soluno resolves device-reported faults against a manufacturer-scoped fault catalogue rather than leaving a raw code on a screen for someone to interpret, so the anomaly is named, not just noticed.
Optimise. This is the step a dashboard structurally cannot reach, because optimisation is an action, not a view. Soluno’s optimiser solves for the least-cost battery charge and discharge plan over the next twenty five hours at thirty minute resolution, then writes that plan back to the inverter. The asset behaves differently tomorrow because of what was decided today. A screen, by definition, changes nothing it displays.
A dashboard, in other words, is the one quarter of the work that happens to be the most visible. It is easy to mistake the visible part for the whole.
Watching is not a forecast
There is a deeper limit. A dashboard is, by construction, a record of the past and the present. It cannot plan, because it has nothing to plan against. Managing an energy asset well is mostly a forecasting problem: you decide what the battery should do tonight based on what you expect demand and solar to be, and what you expect energy to cost in each window.
Soluno forecasts both sides of that equation before the day arrives. Site demand is predicted per thirty minute interval roughly a day ahead using an XGBoost model that takes temperature, time of day and scheduled site behaviour as inputs, with a residual correction that rescales the prediction against the measured-versus-predicted ratio over the previous twelve hours. Solar yield is forecast over a seventy two hour horizon from the Solcast weather service. Only with those two forecasts in hand can a dispatch plan be built in advance rather than reconstructed after the fact. A dashboard has neither forecast. It can only tell you, after the evening peak has passed, that you used the battery poorly.
Why this bites a portfolio specifically
For a single site, a diligent owner watching a screen can paper over some of the gap by reacting. Across a portfolio, reaction does not scale, and three forces make the unmanaged screen actively expensive.
- The tariff moved under every site at once. In the restructure NERSA approved on 18 February 2025, the morning peak was cut from three hours to two and the evening peak was extended from two hours to three, with weekday evening peak now running 17:00 to 20:00 in the high demand season. A battery whose discharge window was set to the old shape is now arbitraging against a tariff that no longer exists. A dashboard shows it discharging. It does not show that it is discharging into the wrong hour.
- Every battery is quietly losing capacity. Lithium capacity typically fades on the order of one to four percent per year, with warranty end-of-life thresholds generally landing somewhere between 60 and 80 percent state of health after around ten years. State of health is not a number a dashboard reads off the device. Soluno derives wear from the state-of-charge history using rainflow cycle counting against per-chemistry depth-of-discharge curves, so the dispatch plan can be re-tuned to the capacity the pack actually has, not the capacity it shipped with.
- Backup duty still has to be reserved. Load shedding has eased rather than ended: Eskom’s Winter Outlook 2026 projects no load shedding in its base case but flags a high-risk case of Stage 2 to 6 cuts during the 18 May to 12 August window if unplanned losses run high. Deciding how much capacity to hold back for resilience versus release for arbitrage is a judgement made per site, every day. A screen does not make that call.
Forty live screens do not solve any of this. They simply present forty copies of the same unanswered question.
What managing looks like in practice
The distinction is not philosophical. It changes what gets delivered. Watching produces a feeling that things are fine. Managing produces a small set of recurring disciplines applied across every asset in the fleet:
- Dispatch is re-solved continuously and written back to the asset, so charge and discharge track the current tariff rather than the commissioning-day one.
- Faults and anomalies are diagnosed to a named cause and acted on, working alongside the original installer where hardware attention is needed.
- Battery wear is tracked against the warranty curve, and the dispatch plan is adjusted to the degraded capacity envelope.
- Demand and solar are forecast ahead, so each day is planned rather than reviewed in hindsight.
- Savings are reported in rand, by comparing what the site actually paid against what it would have paid drawing the same energy entirely from the grid.
None of these are things you read off a screen. They are things a dedicated consultant, equipped with proper instrumentation, does on the asset’s behalf. The screen is one input to that work. It is not the work.
The question worth asking your provider
If you run a portfolio and your reporting is a live view that you or your team are expected to interpret, you do not have asset management. You have surveillance, and the burden of turning what is on the screen into action still sits with you. The honest test is simple: when a site drifts from plan, who notices, who diagnoses the cause, and who changes what the asset does next. If the answer to all three is “whoever happens to be looking at the dashboard”, the asset is being watched, not managed. Those are different jobs, and only one of them protects the return the fleet was financed on.
Sources and further reading
Want to know what your solar asset could save?
How Much Do I Save?