A record of your plant data, next to your monitoring.

It collects what your portals, meters and weather sources deliver and keeps it as it arrived. It computes your KPIs from that, with the origin on every number. Your monitoring stays where it is. No migration.

Start with one report. Then it keeps 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.

What it does, in plain words

Raw kept untouched

Raw bytes are kept as they arrived. Nothing is ever overwritten.

Runs alongside

Your portals keep monitoring. Nothing changes for your teams.

Replay

Same raw data, same master data, same rules: the same numbers. You have all three, so you can recompute any number yourself.

As of a date

Both reports were right on the day they were made. You can ask what was known when.

Corrections with a ticket

A value changes only with a ticket, a reason and a name.

One machine, just for you

We run it on one machine in Germany, shared with no one else. Your data stays in your own highly available storage, so if the machine fails, nothing is lost.

We lead with solar. Wind and storage share the same data contract.

The same number, cut any way you ask.

Your rules stay the same, so a question becomes a filter: by inverter model, firmware, module type, orientation, commissioning year, or any label you keep in your project. You pick one dimension or several. Every cut adds back up to the same number.

Performance ratio by inverter model

Inverter model

The gap is 1.8 points. Together, the groups add back up to 79.8 % from the inverters, and the 0.8 points lost before the grid meter bring it to your base row of 79.0 %.

Performance ratio by module type

Module type

The gap is 2.4 points. Together, the groups add back up to 79.8 % from the inverters, and the 0.8 points lost before the grid meter bring it to your base row of 79.0 %.

Performance ratio by orientation

Orientation

The gap is 0.5 points. Together, the groups add back up to 79.8 % from the inverters, and the 0.8 points lost before the grid meter bring it to your base row of 79.0 %.

Performance ratio by commissioning year

Commissioning year

The gap is 2.5 points. Together, the groups add back up to 79.8 % from the inverters, and the 0.8 points lost before the grid meter bring it to your base row of 79.0 %.

Performance ratio by inverter model and commissioning year

Commissioned 2019
Commissioned 2023

The gap is 0.5 points for 2019 and 0.3 points for 2023. Together, the groups add back up to 79.8 % from the inverters, and the 0.8 points lost before the grid meter bring it to your base row of 79.0 %.

Availability by inverter model

Technical availability

The gap is 0.5 points. Weighted by capacity, the two models add back up to 97.7 %, your technical availability.

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

A gap can hide other differences, so add dimensions until it stops moving. Performance ratio here uses inverter readings, not the grid meter.

Missing data is named, not estimated. It shows the gap, not its cause, and we recommend no equipment. The cuts use the labels in your project: keep them there yourselves, or we add them as extra work.

Thirteen promises.

  1. 01 raw data untouched
    Raw data stays exactly as it arrived. Nothing is ever overwritten.
  2. 02 origin on every number
    Every number carries its origin: which delivery, which master-data state, which software version.
  3. 03 one format, every source
    One format for every source. Portal A, portal B, the weather model.
  4. 04 interval start, UTC
    Timestamps without debate: interval start, UTC, days in plant-local time.
  5. 05 warn, don't block
    Checks warn instead of block. A missing number is not a failure. A contradiction is.
  6. 06 corrections with a ticket
    Corrections only with a ticket, a reason and a name. They outrank the portal.
  7. 07 queryable as of a date
    Any question can be asked as of a date. The answer is a query, not archaeology.
  8. 08 provisional stays marked
    A day counts as provisional while the portal can still revise it.
  9. 09 reproducible from your data
    Reproducible: same raw data, same master data, same rules give the same numbers. You have all three, so you can recompute any number yourself.
  10. 10 dated master data
    Master data with validity dates. A meter swap is a new row, not an edit.
  11. 11 unknown values kept
    A measurement nobody recognises is kept and reported. Never dropped.
  12. 12 independent witness
    Every important number has an independent witness. The grid meter checks the inverters, the weather model checks the sensor. Two witnesses on nobody’s payroll.
  13. 13 one machine, just for you
    Runs on one machine in Germany, just for you, and we operate it. Your data stays in your own storage and you can revoke our access at any time. If the machine fails, nothing is lost.

We deliver the evidence. You make the call.

You: the verdict

  • Contracts and damages
  • Switch or stay
  • Dashboards and reports in your tools
  • Your own analytics and agents
  • Negotiating with operator and portal

Us: the evidence

  • Raw data untouched and versioned
  • A record with origin on every number
  • Checks every night that warn instead of block
  • Findings with what they cost
  • Reproducible from your data

We check the numbers. We recommend no portal, no operator and no strategy.

Send one plant, one 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 and a 30-minute walkthrough. Nothing changes in your monitoring.

Send one plant, one month