Run the whole portfolio from one place.

One place, every plant

Each remote device sends up what it measured and what it was instructed to do. That is compared against forecast and simulated-performance data, to catch degradation or hidden faults before they surface. The system can also cross-check independent sources — inverter production figures against a smart meter reading the energy fed to the grid, or against settlement notes from sources like DAPEEP — so a bad meter, or energy lost somewhere it should not be, shows up rather than passing unnoticed.

The operations record writes itself

A curtailment instruction arrives from the grid operator. The platform opens an incident, files each change to the limit underneath it, and closes it when the limit is released. Same treatment for plant shutdowns, communication outages, an MV controller left in local, and breaker events — each one an entry with a start, an end and a duration. Nobody logs anything by hand; and where something cannot be detected automatically — a hole in the fence, say — an entry can still be added manually.

The commands that were correctly refused are on the record too. Plant in local for maintenance, a setpoint arrives anyway, the controller drops it as it should — and the drop is recorded: which command, what value, the exact time, and the mode that caused it. When someone asks why the plant did not respond on the fourteenth, that is a timestamped line instead of an argument.

And because those orders are on the record — with their limits, their durations and what the plant was producing when each one landed — the platform reports what the operator's instructions cost, per plant and per period. Most portfolios answer that question by hand, late, or not at all.

The logbook the field actually uses

Maintenance work lands in the same place as the automatic record. An entry opens, takes an assignee, moves to in-progress, and closes. Photos, reports and certificates attach to it, classified by document type, with validity dates on the ones that expire.

Who sees what

The organization tree holds companies, EPCs, departments and individual owners. Roles run from read-only viewer up to full administrator, granted per organization or per plant — and can be set to expire on a date. An O&M operator runs the portfolio; an owner sees his own plant and nothing else; an EPC keeps access through the warranty period and then it lapses on its own, without an admin having to remember. Each user works in English or Greek.

Our cloud or your rack

Hybrid edge-and-server, on purpose. Compliance and control stay on the box in the substation, where they keep working whether or not the platform is reachable — the platform is never in the path between the grid operator and your plant. The Server itself runs in our cloud or in your own rack: same build, your choice, and it can move later.