Weather Windows: Scheduling Component Work Around the Wind

High-wind days are lost days for rotor and yaw work. Here is how we use wind-speed history to size realistic buffers and keep component campaigns on schedule — with the approach we apply inside our own quote models.

Why wind is the schedule

On a wind farm, the resource and the hazard are the same thing. Component work sits inside a strict envelope: heavy lifts and nacelle work typically stop well before blade work does, and every OEM procedure states its own limits. When the daily average pushes past the limit, the crew stands down — and a campaign planned on calendar days quietly starts eating its own contingency.

A schedule that ignores this is not optimistic; it is wrong in a predictable way. The wind-speed history at the site already contains the answer to "how many stand-down days will we get" — you just have to ask it properly.

Use history, not hope

We start with the site's own wind-speed record — the same SCADA history the turbines generate every day, so the numbers reflect the exact met conditions at hub height, not a regional weather station 40 km away. From that record we compute, month by month, the exceedance curves: for each working threshold, what fraction of days in that month historically blew past it?

That single table changes the conversation. A 20-shift campaign starting in a month where the threshold is historically exceeded 25% of days is not a 20-shift campaign. It is a 25-shift campaign with a 5-shift problem, and everyone should know that before the contract is signed, not after the second stand-down.

Sizing buffers like a quote model

Inside our quote models for caliper and component campaigns, the buffer is computed, not guessed:

Base scope — productive shifts required by the work itself, per turbine and per crew.
Historical exceedance — stand-down probability per calendar window, from the site's own record.
Buffer shifts — exceedance applied to the base scope, rounded to whole crew-days.
Sequencing — wind-sensitive tasks front-loaded into the statistically calmer windows inside the campaign period.

The result is a price and a schedule that already contain the weather. When a stand-down day arrives, it is an expected line item, not a variation claim — which is exactly how a client relationship survives a windy month.

Sequencing work by weather sensitivity

Not all tasks are equally fragile. Paperwork, parts inspection at port, torque checks under the nacelle cover and training sessions can all run on marginal days. Heavy lifts, blade work and anything involving a crane cannot. We sequence the campaign so the weather-sensitive work claims the statistically calm windows first, and the flexible work absorbs the stand-downs. The campaign stops waiting for the weather and starts interleaving with it.

Communicating the plan

A weather-buffered plan only builds trust if the client can see it. Our schedules state the threshold, the historical exceedance behind each buffer, and the reporting cadence during execution: wind logged against plan, stand-downs explained, and recovery options (resequencing, extended shifts, crew reassignment) presented before the schedule slips, not after. Weather delays are inevitable; weather surprises are not.

Takeaways

Use the site's own hub-height wind record — not regional data — for exceedance curves.
Compute buffer shifts from historical exceedance; don't pad the schedule by feel.
Front-load wind-sensitive work into the calmest statistical windows.
Fill marginal days with flexible tasks instead of standing the crew down.
Show the client the thresholds and the maths — weather delays stop being disputes.