Checked

Audit the KPIs your money depends on. Yourself.

And make every asset from every monitoring provider comparable.

One base row for every plant, whichever monitoring portal it runs on. Recomputed from your raw readings, with the method written next to the number.

Send one plant, one month

One plant, three numbers.

Guaranteed in the operations contract: 98 %

Pass

Source A

Availability

99.5 %

24 hours a day
inverters counted, not weighted
data gaps count as available
grid outages excluded

Fail

Source B

Availability

97.5 %

daylight hours only
weighted by capacity
data gaps count as down
nothing excluded

Pass

Source C

Availability

99.2 %

daylight hours only
contract exclusions applied
maintenance within quota excluded
data gaps left out

Not comparable

All three are called availability. None of them is wrong. Against the 98 % guaranteed in the operations contract, two pass and one fails, and a fail can mean damages. Only the contract’s own definition decides which one counts. Recomputed under this contract, it passes at 99.2 %. Over all daylight hours, the plant was available only 97.7 % of the time: the contract leaves out the grid outage and planned maintenance.

Synthetic example. The numbers are made up, the mechanics are not.

See how one plant gets three availabilities

Nobody is wrong. Nobody wrote it next to the number.

Same plant, same month, same three sources. Now performance ratio.

Layer	Source A	Source B	Source C
one set of rules	79.0 %	79.0 %	79.0 %
Energy out	+0.8	−0.4	±0.0
Sunlight	+1.6	−2.0	−0.4
Size	±0.0	−0.3	±0.0
Hours	+0.5	−0.2	−0.2
reported	81.9 %	76.1 %	78.4 %

Almost six percentage points between the three, on a KPI that decides bonuses and sales. None of it stands next to the number.

Synthetic example. The numbers are made up, the mechanics are not.

Follow the performance ratio layer by layer

Two numbers. Both right.

Technical availability

Could the equipment run?

97.7 %

daylight ≥ 50 W/m² weighted by capacity curtailed = available gaps: unknown 0.2 %, left out nothing excluded October 2026

Contractual availability

Did the contractor deliver what was signed?

99.2 %

contract OM-2024-07 daylight ≥ 50 W/m² weighted by capacity excluded: grid outage 4 h excluded: maintenance 10 h of 24 h quota gaps: unknown 0.2 %, left out October 2026

Same plant, same month, same raw data. Each number says what it is. The argument is over before it starts.

Synthetic example. The numbers are made up, the mechanics are not.

Read the seven KPI definitions

Let the portals monitor. They are good at it.

Audit

The KPIs your money depends on, recomputed by you from the raw readings. Each portal's difference is measured, and what can be explained gets a name.

Compare

One base row for every plant, whichever portal it runs on. One number that means the same thing everywhere.

Keep

Raw data stays as it arrived, in your own storage. The history stays yours when a portal goes.

We deliver the evidence. You make the call. We recommend no portal, no operator and no strategy, and we take no commission from anyone.

See it once. Then keep it running.

Step 1: the report

We do it once, on one plant.

You send one plant and one month. We recompute the KPIs and show you what we find, so you can judge the work before deciding anything else.

One plant, one month
Nothing to install
Nothing changes in your monitoring

Step 2: every plant, continuously

Then it runs all the time.

The same definitions on every plant, new data as it arrives, checks every night. We run it for you:

One machine, just for you

It runs on a machine in Germany that you share with no one else. We operate it.

Your data, in your storage

Raw data and analytics stay in your own highly available storage. You can revoke our access at any time.

Your plant changes, in your project

Your team can edit master data and see who changed what.

If the machine fails, nothing is lost. It is rebuilt from your storage and your project.

Running it continuously costs one yearly subscription, machine included. You pay your storage provider directly.

See what runs: the platform

Send one plant, one month.

You send

Portal access or a CSV export for one plant and one month
The master data: capacity, inverters, sensors
Anything that changed in the month

You get

Performance ratio and availability as a base row, with the rules written down
The difference against each reported number, with what explains it and what stays open
A method card next to every number
A 30-minute walkthrough

Nothing changes in your monitoring. No migration.

Send one plant, one month

You talk to the founder.

Philipp Wegner, fifteen years in solar monitoring and data engineering, previously on systems taking care of over 50,000 plants, currently monitoring over 500 MW. You speak directly with the person who built the platform and knows these numbers from the inside.

Philipp Wegner on LinkedIn

The KPI definition sheet.

Seven KPIs, one question each, and the five things each one has to fix. A PDF to keep next to your contracts.