Wind Plants

You can register wind plants in Mirox and manage them as first-class resources alongside your solar and battery sites. Turbine monitoring, turbine alarms with notifications, curtailment settlement and outage reporting to the direct marketer are live; deeper wind performance analysis is being built out next.

What You Can Do Today

A wind plant is a full Mirox park resource. Once you create a park of type wind, everything the platform offers around organizing and governing a site applies:

• Portfolio organization — group wind plants into portfolios alongside other plant types.
• Resource hierarchy and access — assign roles per park, share plants across organizations through cooperations, and keep one consistent permission model for every site.
• Plant records — maintain contacts, comments, site documents, and a site outline image per plant.
• Connectivity and remote access — reach on-site infrastructure through the VPN and Browser Proxy, and inspect the local network with the Local Network Inspector.

Curtailment Settlement (Redispatch 2.0)

The first wind-specific analysis is live: when the grid operator orders your plant down, Mirox detects the curtailment and reconstructs the compensable lost energy (Ausfallarbeit) per turbine and quarter-hour under the BilAReM rules — the same legal engine that settles solar plants.

What You Configure

• Settlement method — one of the three legal methods, chosen per plant in the market configuration.
• Hub height — per turbine, so the weather service's wind profile can be extrapolated to the rotor.
• Reference turbine — per turbine, where a machine's own anemometer is not usable and a neighbouring turbine should stand in for it.

Both turbine fields live in the turbine drawer; see Configure Wind Turbines.

The Three Methods

• Spitz Wind — the certified power curve at the turbine's own nacelle wind speed.
• Spitz Wind light — the certified power curve at a reference wind speed: an assigned reference turbine, or the weather service at hub height.
• Pauschal Wind — the turbine's own feed-in in the last unrestricted quarter-hour before the curtailment, held flat.

Unavailability and the Direct Marketer

A wind plant has an Unavailability page: everything that makes a turbine unavailable to the grid or to your direct marketer, and what the marketer has received of it. Open in Mirox — pick your wind plant from your plants and choose Unavailability. The register works per reportable unit: on a wind plant these are the turbines, which is why this section says "turbine"; for other plant types, once they are enabled, the unit is the plant itself. Every (i) icon on the page leads here — this section is the full explanation.

The page is laid out like the production page. The date range picker at the top right sets the period of the Overview and Curtailment tabs. Four key figures sit above the tabs: Planned hours ahead (with the number of outages declared), Ongoing outages (with the turbines affected), Turbines not identified (how many of them the marketer can identify) and Pending at the marketer (with the number of failed reports). Below them, four tabs:

• Overview — the availability timeline of the selected period, one row per turbine, with three lanes: outages you planned, outages reported by alarm and outages found at the marketer; the plant's grid-operator and marketer curtailments sit on a row of their own, Plant (curtailment). Click a bar for the details. The Report outage or curtailment button sits above the timeline.
• Register — the outage register: every planned, alarm-reported and marketer-found outage from 30 days ago to a year ahead, with its origin, reason, available power and the marketer state of every turbine (Pending, Reported, Failed, Not sent, Withdrawal pending, Withdrawn, Removed at the marketer). Report outage or curtailment declares a new one; a row can be edited, withdrawn or — after a failed report — sent once more with Report again. A grid-operator or marketer row also carries Settlement, which opens its settlement under the Curtailment tab. Filter by turbine, origin, reason and marketer state; withdrawn outages stay hidden until you show them.
• Curtailment — the plant's curtailment events with their detection and settlement details, the same view as on the production page of a solar plant. The Report outage or curtailment button is the way to enter a curtailment here, too. A curtailment that belongs to a register entry is edited or withdrawn in the register, not in the curtailment dialog.
• Direct marketer — the marketer the plant reports through, the turbine identification table, Sync now, and Reported live by alarm: the alarm rules that report this plant's outages the moment they fire.

Reporting an Outage or a Curtailment

One dialog, Report outage or curtailment, covers both the planned outage and the manual curtailment entry on this page. It asks for the turbines (all by default), begin and end in plant time, the reason, the available power — Full stop or Reduced to … kW per turbine, never more than the turbine's rated power — and a comment. An outage starts at its begin and ends just before its end, in quarter hours: 06:00 to 18:00 covers the quarter hours from 06:00 through 17:45. The reasons are the four reasons of the BWE outage interface, and the reason decides what Mirox does with the entry:

Before you save, the dialog tells you what will happen: Will be reported to … for N turbines — or, without a linked marketer, No direct marketer linked — recorded for the settlement only — and either Counts the turbines as unavailable in the settlement or Also recorded as a curtailment and settled for compensation. Two rules apply to Grid operator and Direct marketer: the entry must lie inside one delivery month — report it in two parts at the month edge — and, as the BWE rule shown in the dialog says, if it cannot be told whether the grid operator or the direct marketer curtailed, report neither. A grid or marketer entry appears under the Curtailment tab with its settlement figures, reached from its register row via Settlement; it is edited or withdrawn in the register.

How Reporting Works

Mirox reports the plant's outages to your direct marketer through the BWE outage interface. The plant's agent does the reporting: it sends a new or changed declaration within seconds and reads the register back from the marketer every 15 minutes. A report is never changed at the marketer — a change is reported anew and the latest report wins; the register shows what the marketer has accepted for each turbine, and an outage's details list every report made to the marketer.

• An outage that was entered at the marketer in another way appears in the register as Found at the marketer.
• An outage Mirox reported that the marketer no longer holds is flagged Removed at the marketer; Report again sends it once more.
• A report that did not get through is shown as Failed, with the number of attempts; Report again queues it for the marketer again.
• Sync now on the Direct marketer tab makes the plant report and read back within moments instead of waiting for the 15-minute cycle.

The marketer identifies a turbine by its manufacturer and serial number — or by the plant key the marketer assigned. The serial number is set in the turbine's settings, see Configure Wind Turbines; the manufacturer comes from the turbine's datasheet. A turbine the marketer cannot identify is not reported — the other turbines are — and the Turbine identification table on the Direct marketer tab shows each turbine's status:

The key figure Turbines not identified counts these cases.

Reported Live by Alarm

A turbine alarm needs no planned entry. An Alert Manager rule that watches the turbines one by one and has your direct marketer among its receivers reports the alarm to the marketer the moment it fires — this many hours ahead, extended every pass while the alarm lasts — and cuts the outage back to the real end when the alarm resolves. The rule's Report outages setting carries the reason (Maintenance, Administrative order, Grid operator or Direct marketer) and whether the turbine is reported as a full stop or with the power it still delivers. These rows appear in the register as Reported by alarm, with the rule and the alert, and cannot be edited.

The Reported live by alarm card on the Direct marketer tab lists the rules that report this plant's outages — rule, reason, the hours reported ahead, the power reported (Full stop (0 kW) or The power still delivered) and whether it reaches the marketer — a rule that reports to its own receivers only is listed too; a switched-off rule carries the badge Inactive. A rule on the plant total never appears here: only rules judged per turbine are reported. Set up live reporting opens the Alert Manager with the system template Turbine not operational → outage report to the direct marketer already targeting this plant; Alert Manager opens your rules. Planned outages and alarm outages go to the same direct marketer — the one linked to the plant.

The Marketer Connection

The connections to your marketers' outage web services live under Organization ▸ Direct marketers Open in Mirox — wind plants report their turbine outages through these web services; each plant picks its marketer on its Unavailability page. Every connection is created together with a receiver of the same name in the Alert Manager — see Direct marketer. A connection has a name, the protocol (today the BWE outage interface — Request another protocol tells us which standard your marketer uses), the web service address, the sign-in (token) address, the user name and password the marketer issued, an optional Client ID (only if the marketer requires one), the hours ahead an outage is reported and renewed (2 by default, 1 to 48) and the switch Active — plants report through this connection; switched off, reporting pauses for every plant on the connection and for its receiver. The password is stored encrypted and never shown again. Test sign-in signs in and shows how many plants the marketer has assigned to your account; it never reports an outage. The list shows each connection's health — Not tested yet, Working, Last call failed, Switched off — plus its linked plants and the plants at the marketer. A wind plant is linked to one connection on its Direct marketer tab, and several plants can report through the same connection. A connection cannot be removed while a plant still reports through it; removing it also removes its receiver in the Alert Manager; each row's … menu offers Edit, Test sign-in, Receiver in the Alert Manager and Delete.

What It Means for the Settlement

An outage with the reason Maintenance or Administrative order is not a curtailment. A turbine in maintenance during a grid measure was not available to be called on, so no compensation can be claimed for it in that time: Mirox lowers the turbine's availability in the curtailment settlement and claims no lost energy for it while the outage lasts. An entry with the reason Grid operator or Direct marketer is a curtailment: it is reported to the marketer and recorded as a grid or marketer curtailment, and the settlement calculates its compensation like for any detected or manually entered measure — its figures are under the Curtailment tab. Like a manual curtailment entry, an entry can be reported, changed or withdrawn until the settlement deadline of its month — the end of the 4th working day of the following month. A withdrawn entry stays in the register as withdrawn, its reports are deleted at the marketer and the settlement no longer takes it into account.

Who May Do What

Everyone who can see the plant sees the page, its register and the marketer the plant reports through. Reporting, editing and withdrawing outages and curtailments, linking the plant to a marketer and Sync now are reserved for the plant's technical roles, Operator and Technical Manager — the same roles that enter curtailments by hand. The marketer connections under Organization ▸ Direct marketers are created, changed and tested by Admins and Moderators; every member can see which connections exist. Alarm rules that report live, and the direct-marketer receivers they use, are created by Admins and Moderators in the Alert Manager — Set up live reporting is shown to them.

Turbine Monitoring

The Turbines page of a wind plant shows the turbines from their own 10-minute SCADA data:

• Key figures — current power, energy and lost energy over the last 24 hours, average wind speed, turbines producing, availability and utilization.
• Graphs — power over the day, energy per turbine, the measured power curve against the turbine's characteristic curve, and a wind rose.
• Turbine table and drawer — every turbine with model, serial number and last reading. The drawer holds its settings (hub height, reference turbine) and its alarm list: the turbine controller's own active and withdrawn alarms, with code and text.

On the Monitor page each wind plant shows how many turbines are healthy, stopped by a fault or not communicating.

Production Forecast and Expected Power

Every wind plant gets a 5-day production forecast built from the wind at hub height, the air density at the rotor and each turbine's datasheet power curve. It appears on the Forecast page, on the Turbines page as a forecast lane with the 5-day strip (you can page up to four days ahead), and in the forecast places of the monitor, the dashboard and the mobile app.

The same model run on the actual weather gives an expected power for the past, about six hours behind real time. Charts show it next to the possible power your turbine controllers report — one reference from the nacelle's own wind measurement, one from the weather.

• Hub height matters — set it per turbine in the turbine drawer (Configure Wind Turbines); without one, 120 m is assumed.
• A power curve is required — a turbine is forecast only when its datasheet has a power curve; turbines without one are left out of the plant total.
• All visible turbines count as available — the forecast shows what the plant can produce, not what outages or curtailments will leave of it.

How the forecast is computed is explained in Forecasts — Wind plants.

Turbine Alarms and Notifications

Mirox notifies on the judged state of a turbine, not on each raw code of its controller:

• Stopped by a fault — the turbine reports a fault or protection stop. The event opens on the first 10-minute row; the plant's single "components down" notification (High) follows after two consecutive rows, about 20 minutes.
• Not communicating — one turbine's data stops while the others still deliver: an event after 30 minutes, the plant notification after 3 hours (12 hours after a service visit or a commanded stop).
• Safety alarm (Critical) — fire, smoke or an arc in the converter or switchgear. Sent with the first row that carries it, also during a service visit.

Stops that are not faults — a remote pause, bat, shadow-flicker, ice or noise curtailment, a stop ordered by the direct marketer or the grid operator, a pause pressed on the turbine's keyboard or a service stop — are recorded as status: they open no event and never notify. The controller's own alarm code travels with each event as detail, and plain controller warnings stay on the turbine's alarm list without notifying.

The thresholds, why they are what they are, and how they compare with solar and battery storage are explained in Alarm Levels — Wind turbines.

Still Planned

• Production analysis — underperformance detection that holds measured output against the expected power from the weather.
• Loss attribution — distinguishing real production loss from weather and communication gaps; curtailment is already separated out by the settlement engine.

Related Features

• Plant Catalog Overview — the plant types Mirox supports and how they fit together
• Solar Plants — the fully supported plant type today, with live monitoring and analysis
• Alarm Levels — turbine alarms, their levels and timing
• Alert Manager — Direct marketer — report turbine alarms to your direct marketer automatically
• Battery Storage — battery energy storage plants in Mirox
• Forecasts — the 5-day wind production forecast
• Digital Twin — the automated analysis engine (solar PV today, plus wind curtailment settlement)
• Resources — how organizations, portfolios, and parks are structured