Skip to content

Ten plants, ten portals

The supplier's portal answers one question well — how is this plant doing — and that stops being the question you need somewhere around the third site.

17 August 2026 3 min read by Redazione NeMo

The first plant does not have a monitoring problem. It has a portal, the portal came with the hardware, it shows today’s output and thirty days of history. It works.

The second plant, if it is the same brand, joins the same portal. The third one rarely does. From there every acquisition, every repowering and every job won by a different installer adds a login.

The problem is not the number of passwords

That is the annoyance. The problem is that each portal hands the data back in its own unit, on its own time grid and inside its own boundary, and none of the three is negotiable.

One portal samples at fifteen minutes, another at five and shows you the hourly mean. One calls availability the time the inverter was powered, another the time it was powered and irradiance was above a threshold. One reports output already corrected for planned outages and does not tell you which ones.

Taken one at a time, every definition is defensible. Lined up in a spreadsheet they become a column that looks comparable and is not.

And that spreadsheet always exists. It is filled in by hand once a month from portals that round differently, and it is the only place in the company where the sites are looked at together. It is also the least reliable thing you own.

What the supplier’s portal cannot give you

This is not a criticism of the portal. It is its boundary. It was built to sell and support that hardware, and it does that job well.

Three things sit outside it by construction:

  • Comparison across brands. It does not have the other plants’ data and does not want it.
  • Quantities that do not pass through its hardware. The fiscal meter, the substation temperature probe, the gas meter, the compressed-air flow meter. Different instruments, usually different protocols.
  • History beyond its own window. Many portals keep fine-grained samples for a few months and then keep aggregates only. When you need a year-on-year comparison at the granularity that matters, the fine data is gone. Not archived elsewhere — discarded.

The last one costs the most, because you find out when you need it, and by then the only remedy is to wait another year.

What changes when you collect it yourself

The step up is not a better-looking chart. It is that the measurement stops being a by-product of the device that produced it, and becomes your data, with three properties a portal cannot guarantee:

One scale. Plants sit on the same timeline in the same unit, because the conversion happens once on the way in rather than every month by hand.

One definition. The indicator — availability, performance, specific consumption — is computed by the same formula everywhere. If the formula changes, it changes in one place, and it can be re-run over the recorded history to see what it would have said.

One history. Queryable at the granularity it was collected, for as long as you need it, without somebody else deciding when to aggregate it away.

NeMo reads the equipment you already have — inverters, meters, PLCs, probes — on the protocols they already speak, and keeps what it reads. Nothing in the field is replaced to get started, and the supplier’s portal keeps working exactly as before. It simply stops being the only place that data exists.

The feature behind it, with the steps and what comes out of it, is in dashboards and alerts.

Measuring is the part that takes time

A measured history is not something you build in a fortnight. Tell us what you have on site and we will say what it takes to read it.