Built line by line, from your own systems.
Nothing here is inferred. Each line names the system it came from, so the control room can check a settlement period while it is still fresh and defend it if it is queried. Values fill in from your own site.
Why the machine missed its curve.
Wind speed, pitch, the availability declaration and the outage record sit in four places. The reason a machine underperformed is assembled by hand, if at all.
A turbine below its power curve is either curtailed, faulted, derated or mis-declared. Those four look identical in a monthly report. Hold the SCADA reading, the met mast data, the dispatch instruction and the maintenance record against the same machine and the distinction gets made in the settlement period it happened in, which is when it still costs nothing to make.
The step-up transformer matters more than most registers admit. A constraint at the substation limits the machine upstream of it, and unless both sit on one model that limit gets recorded as poor turbine performance.
A constraint you can point at.
The instruction exists in the control room log. The limit exists at the substation. The lost volume exists in settlement. What is usually missing is anything tying the three together while the day is still recent enough to check.
When a feeder is constrained, output falls on machines that are working correctly. Held on one record, the busbar, the breaker and the affected feeder carry the instruction that limited them, so lost generation is attributable rather than inferred at month end.
The same structure answers the question a network operator asks back: what was available, what was instructed, and what actually flowed. Each of those is a reading with a source, not a figure typed into a claim.
One availability figure, defensible.
Availability is declared, metered and settled by three groups working from three versions of the same day. Disputes are then settled by whoever kept the better spreadsheet.
The metering point is where the argument lands. Muono holds the meter reading, the instrument transformers that produced it, the availability declaration and the outage register on one record, so the figure sent to settlement carries its own derivation.
That changes what a dispute is about. Both parties look at the same meter readings and the same outage register, and the argument moves to the contract, which is where it should have been in the first place.
One site, five stages, a figure at the end.
A paid pilot on a single site, then an annual licence per site. The baseline goes in first, while nothing has changed yet. That is the figure the review argues from.
- ScopePick the site and the figure it has to defend.
- ConnectSCADA, maintenance system, and the instructions and declarations beside them.
- BaselineMeasure how the site reports today, before anything changes.
- First answersYour team asks real questions and checks the sources behind them.
- ReviewCompare against the baseline and decide whether it widens.
Put your own numbers in.
We will not publish a result we have not measured. So here is the arithmetic instead, on your figures rather than ours. Change any of them.
This is the size of your problem, not a claim about our effect on it. Muono does not generate a megawatt hour. It makes the difference between curtailed, faulted, derated and mis-declared visible in the settlement period it happened in, and the points you recover from that are yours to estimate.
Your questions, answered
- Do you connect to our SCADA and historian?
- Yes, read-only, on a schedule you set. Tags are mapped to assets once. Afterwards new readings land on the right turbine or transformer without anyone mapping them again.
- Can it handle assets we do not operate?
- Where you have the data rights. Assets you operate arrive as live readings. Others usually arrive as reports on a cycle, and the record says which it is rather than blending them.
- How does this help with settlement disputes?
- By producing the figure with its evidence at the time, not months later. A curtailment carries the instruction, the expected output and the calculation, so the dispute is about the contract rather than the arithmetic.
- Does it work across generation and network assets?
- Yes. Turbines, transformers and the export path sit on one model, which is what makes a constraint at the substation visible from the machine it limits.