Blog

Bat shutdowns in wind power forecasts: modelling operational availability

Illustrative image.

Wind availability is not the same as permission to generate. A turbine may have sufficient wind yet be required to stop or reduce output to protect wildlife. A useful power forecast therefore distinguishes the energy the weather could support from the feed-in expected under the site's operating restrictions. The original 2017 article described two German wind-farm examples with different bat-protection schedules. Their thresholds were site-specific examples, not a universal rule for turbines today.

Translate an operating restriction into data

Obtain the actual permit conditions and operating instructions from the asset owner. A shutdown rule may depend on season, time relative to sunset or sunrise, wind speed, temperature and the turbines affected. Those details should be represented explicitly. Avoid substituting a generic night-time reduction for a more precise rule. Record the source of the instruction, its effective date and who can authorise updates.

Keep time and asset scope consistent

Sunrise and sunset depend on location and date. Local-time rules also need careful conversion when daylight-saving changes occur. A restriction affecting some turbines should not automatically remove the entire wind farm. When forecasts are delivered at portfolio level, aggregate the restricted and unrestricted assets consistently. Validate boundary intervals around the start and end of each restriction.

Separate potential output from expected feed-in

Potential production describes what the available wind resource could produce without the restriction. Expected feed-in incorporates known operating constraints. Keeping both quantities distinct can support schedule preparation and later analysis. A measured zero during a required shutdown should not automatically teach a weather-to-power model that the wind was absent. Availability and shutdown flags help interpret the measurement correctly.

Evaluate the rule implementation

Compare the forecast against the same measurement boundary and operating definition. Review intervals when the rule applied, when its triggering weather was close to a threshold, and when the real control behaviour differed from the planned rule. Record changes rather than blending several permit versions into one history. A reliable forecast cannot replace compliance monitoring or the operator's responsibility to follow the applicable conditions.

Prepare a practical handover

Before adding a wind farm, provide asset identifiers, the affected turbines, location, restriction calendar and the authoritative operating rule. Agree how planned restrictions and actual shutdowns reach the forecast provider, and how quickly changes need to be reflected in the scheduling workflow. This turns a nature-protection condition into an auditable forecasting input while preserving the distinction between an energy estimate and an operational instruction.

Check the boundary cases

Test the restriction immediately before and after the seasonal boundary, at sunset and sunrise, and when predicted conditions lie near a threshold. Compare the implemented rule with the approved instruction. Where the control system uses measured conditions rather than forecast conditions, explain that distinction: the forecast describes expected operation, while the actual control decision may change as measurements arrive. It is possible for the model to implement a rule correctly and still differ from feed-in because the triggering weather was forecast imperfectly.

Maintain a reviewable history

Keep the original schedule and every revision, rather than overwriting a single current field. During evaluation, apply the version effective for the interval being assessed. If actual shutdown records are unavailable, state that limitation before interpreting the errors. A recurring low-output pattern can prompt investigation, but it should not be converted into an invented permit rule. Agreement between the asset owner, forecasting team and scheduling user is especially useful when restrictions affect only part of a site. That shared history supports both the forecast and an honest explanation of its limits.

Get in touch

Put your forecasts to the test

Describe your assets, decision horizon and available measurements. Discuss the scope of a forecast evaluation with our team.

Discuss a backtest