# Wind turbine vibration thresholds: $4,200 truck roll vs 14 downtime — dispatch or defer

Chase Pierce · November 15, 2026

> Dispatch or defer on wind turbine vibration alarms? Compare the $4,200 truck roll against downtime costs to cut expenses and avoid false alarms.

Immediate dispatch on any single-channel alarm maximizes short-term availability because every alert prompts a physical inspection. In practice, it delivers the worst cost-per-confirmed-finding of the three options. Single-cutoff strategies are dominated when signals near a boundary carry high uncertainty: acting on every crossing expends resources on events that do not warrant intervention. Verify this on your own fleet by comparing last quarter's single-channel dispatches against how many found a confirmed fault.

Deferring everything to the next scheduled service visit sits at the opposite extreme. It is the cheapest option on a per-event basis because it eliminates unscheduled mobilizations, but it treats deferral cost as if it were zero. In reality, the cost of deferral is the downtime exposure you accept by leaving a fault to progress. For contained bearing or gearbox wear, that exposure can convert a manageable repair into an unplanned outage with broader secondary consequences, eroding the apparent savings of waiting.

The explicit winner is conditional dispatch on sustained multi-channel trends, with immediate dispatch reserved for coupled-channel escalation. This strategy filters out transient, isolated signals before committing a crew, concentrates truck rolls on alarms that exhibit corroborated persistence, and escalates without delay when multiple mechanical channels deteriorate together. By aligning dispatch decisions with the balance of mobilization cost and deferral exposure, conditional dispatch preserves availability where it matters while avoiding the systematic waste of single-channel responses and the hidden liabilities of blanket deferral.

![Immediate dispatch on any single-channel alarm maximizes short-term — Wind turbine vibration thresholds](https://static.mm-ais.com/article-images-ai/wind-turbine-vibration-thresholds-4-200-ai-4167c17a.jpg)

## The Numbers That Move the Decision

The dispatch decision starts with a clear cost anchor: a truck roll to check a vibration alarm carries an all-in planning cost of about $4,200. That figure should cover technician travel hours, any crane or lift-adjacent access required to inspect the drivetrain, and the opportunity cost of pulling that crew from scheduled work. Because labor rates, site access, and fleet logistics vary, treat $4,200 as a planning anchor rather than a universal rate. Verify your own figure by dividing last quarter’s reactive-dispatch spend by the number of reactive dispatches; if your verified cost differs, substitute it everywhere in the comparison.

The deferral side is the exposure you accept by waiting. A practical planning window is 14 hours of downtime. To estimate that exposure, multiply 14 hours by your turbine’s hourly revenue loss, calculated as expected output during those hours multiplied by the applicable energy price or contract rate. This yields the direct downtime cost of deferral. Any credible risk of secondary damage is additive to that downtime cost, not a substitute for it.

These two quantities define a break-even failure-probability delta formula, used here as a method rather than measured fleet data. Let *Ctruck* be your verified truck-roll cost, *Cdown* be the 14-hour downtime exposure, *Csecondary* be the estimated cost of secondary damage if the condition worsens, and *Δp* be the increase in probability of that secondary damage caused by waiting. The expected cost of deferral is *Cdown + (Δp × Csecondary)*. Dispatch is justified on cost grounds when this expected cost exceeds *Ctruck*.

Solving for the break-even point gives *Δpbreak-even = (Ctruck − Cdown) / Csecondary*, provided *Cdown* is less than *Ctruck*. If your 14-hour downtime exposure already equals or exceeds $4,200, deferral fails the cost test before secondary-damage risk is considered. If downtime exposure is lower, the formula shows how large the added damage probability must be to justify the roll. For example, using the $4,200 anchor, a $1,400 downtime exposure leaves $2,800 ($4,200 − $1,400) to be offset by risk; closing that gap requires a Δp of 0.28 against a $10,000 secondary-damage estimate, or 0.14 against a $20,000 estimate.

Run this arithmetic before committing a crew: confirm your verified truck-roll cost, calculate the 14-hour revenue exposure for the specific turbine and conditions, and test whether plausible secondary-damage costs and probability deltas clear the break-even threshold. This keeps the dispatch decision tied to quantified exposure rather than alarm magnitude alone.

![The Numbers That Move the Decision — Wind turbine vibration thresholds](https://static.mm-ais.com/article-images-ai/wind-turbine-vibration-thresholds-4-200-ai-44c30666.jpg)

## What This Evidence Cannot Tell You

The trend-confirmation rule is a decision structure, not a substitute for equipment-specific limits. The evidence available for this guide contains no wind-turbine-specific vibration thresholds, so it cannot supply the millimeters-per-second values that separate normal operation from alarm or trip states. Before applying any dispatch logic, verify the applicable ISO 10816 or ISO 20816 vibration zone boundaries and the OEM alarm bands against your turbine’s OEM manual. Treat those documented limits as the authoritative baseline; this guide only defines when a confirmed signal justifies the cost of a truck roll.

That boundary matters most when a failure develops faster than the confirmation window can observe. Fast-developing failure modes—such as a sudden gearbox tooth fracture or loose bolts—can move from apparently normal readings to a critical condition inside a single 10-minute SCADA interval. In these cases, waiting for a sustained, multi-interval trend offers no protection, and the trend-confirmation rule breaks. OEM hard-alarm or hard-trip thresholds must override the deferral logic and trigger an immediate response, regardless of whether a multi-interval pattern has formed.

The rule still wins when degradation unfolds gradually enough for consecutive intervals to reveal a consistent direction. Progressive bearing wear, imbalance growth, and misalignment drift typically produce the kind of sustained, corroborated signal that distinguishes a developing fault from transient noise. In those conditions, confirming persistence before dispatch remains the appropriate way to weigh secondary-damage risk against the cost of mobilizing a crew.

| Failure development | Example modes | Trend-confirmation rule | Required response |
| --- | --- | --- | --- |
| Fast (within one 10-minute interval) | Sudden gearbox tooth fracture, loose bolts | Breaks; confirmation window cannot detect the escalation in time | Follow OEM hard-alarm or hard-trip limits and dispatch or secure the turbine immediately |
| Gradual (across multiple intervals) | Progressive bearing wear, imbalance growth, misalignment drift | Wins; sustained evidence can separate a developing fault from noise | Apply the three-check order before committing to a truck roll |

Use this distinction as a pre-dispatch gate: if the alarm reflects an OEM-defined hard limit or a failure mode capable of step-change escalation, do not wait for trend confirmation. If it does not, the confirmation structure remains the defensible basis for deciding whether the expected cost of deferral exceeds the cost of dispatch.

![What This Evidence Cannot Tell You — Wind turbine vibration thresholds](https://static.mm-ais.com/article-images-pixabay/wind-turbine-vibration-thresholds-4-200-54f7885a.jpg)

## The $4,200 Question

Consider an illustrative method using a $4,200 truck-roll cost as the dispatch threshold. A gearbox high-speed-shaft vibration channel trends from 4.2 to 5.1 mm/s RMS over four consecutive 10-minute SCADA intervals, while the generator drive-end channel remains flat. If the asset carries 14 hours of downtime exposure at a computed $900 per hour revenue loss, the deferral exposure is 14 × $900 = $12,600. The decision turns on whether the evidence shows that this exposure is likely enough to justify spending $4,200 now.

**Checkpoint 1 — trend confirmation:** The signal rises in four consecutive intervals (4.2, 4.5, 4.8, 5.1 mm/s RMS), clearing a sustained rise of at least 0.2 mm/s each interval. This passes a quantification bar rather than a detection-only blip; as Koji’s 2026 discussion of detection versus quantification limits notes, quantifying a pattern typically requires roughly four times the sample needed to detect it. A sustained four-interval trend provides the minimum basis to treat the alarm as a measurable condition instead of noise.

**Checkpoint 2 — coupling:** With only one channel moving and the generator drive-end channel flat, there is no corroborating mechanical signature across components. The absence of coupling limits the inferred increase in failure probability from deferral: the risk is confined to a developing single-channel trend, not an escalating multi-component event. **Checkpoint 3 — mechanical corroboration:** Before dispatch, confirm whether available mechanical indicators (such as temperature or lubrication-related signals) move in the same direction. If they do not, the case for immediate intervention remains weaker even when vibration is rising.

| Decision error | What happens | Cost consequence |
| --- | --- | --- |
| Wrong to dispatch | Truck rolls on a trend that stabilizes or proves non-critical within the exposure window. | $4,200 spent without avoiding material downtime or secondary damage. |
| Wrong to defer | Condition progresses into a forced outage during the exposure window. | $12,600 revenue loss, plus any unquantified secondary damage from continued operation. |

In this worked example, Checkpoint 1 supports actionability, but Checkpoints 2 and 3 determine urgency. When the trend is sustained yet uncoupled and mechanically uncorroborated, the expected cost of deferral may not yet exceed $4,200; when coupling or corroboration appears, the $12,600 exposure quickly dominates the dispatch cost.

![The ,200 Question — Wind turbine vibration thresholds](https://static.mm-ais.com/article-images-pixabay/wind-turbine-vibration-thresholds-4-200-30b85b00.jpg)

## Worked Example: Run the Numbers

Illustration only, not a field record: one turbine, one drivetrain vibration alarm, no second mechanical channel escalation, and the alarm present in two consecutive 10-minute SCADA intervals. The exact inputs are scenario = single-channel sustained alarm; intervals = 2 × 10 minutes = 20 minutes; dispatch benchmark = ~$4,200; decision owner = maintenance planner; date = none assigned. Downtime cost per hour and secondary-damage probability are left as variables because they are site-specific.

For this illustration, the winner is defer unless the 20-minute sustained alarm has an expected deferral cost above ~$4,200. The break-even trigger is expected downtime cost plus probability-weighted secondary damage greater than ~$4,200; in the downtime-only case over the full 14-hour window, that is a total downtime exposure above $4,200 — equivalently, an hourly revenue loss above $300, since $4,200 ÷ 14 hours = $300 per hour.

Sensitivity check: if the alarm clears before the second interval, the sustained duration is 10 minutes, or 1/6 hour, and the downtime-only break-even rate becomes $4,200 ÷ (1/6) = $25,200 per hour.

No dispatch decision should be taken from the benchmark alone: the ~$4,200 figure is a comparison point, while the site-specific downtime cost and damage probability determine whether this example's 20-minute alarm crosses it.

![Worked Example: Run the Numbers — Wind turbine vibration thresholds](https://static.mm-ais.com/article-images-pixabay/wind-turbine-vibration-thresholds-4-200-6a1e0e31.jpg)

## Five Rules for Dispatch or Defer

Apply these five rules only after the three pre-dispatch checks are complete. They are the final gate: each rule states the condition, the action, and why the cost comparison changes.

## Frequently Asked Questions

**Which dispatch option has the worst cost-per-confirmed-finding in practice?**

Immediate dispatch on any single-channel alarm delivers the worst cost-per-confirmed-finding of the three options.

**How can a fleet verify that single-channel dispatches are inefficient?**

Compare last quarter's single-channel dispatches against how many found a confirmed fault.

**What risk does deferring contained bearing or gearbox wear create?**

That exposure can convert a manageable repair into an unplanned outage with broader secondary consequences.

**What does conditional dispatch filter out before committing a crew?**

It filters out transient, isolated signals before committing a crew.

**What alarms does conditional dispatch concentrate truck rolls on?**

It concentrates truck rolls on alarms that exhibit corroborated persistence.

**What is immediate dispatch reserved for under the winning strategy?**

Immediate dispatch is reserved for coupled-channel escalation.

## Quick answers

| What is the main drawback of immediate dispatch on any single-channel alarm? | It delivers the worst cost-per-confirmed-finding of the three options because acting on every crossing expends resources on events that do not warrant intervention. |
| --- | --- |
| How can a fleet verify the effectiveness of single-channel dispatches? | By comparing last quarter's single-channel dispatches against how many found a confirmed fault. |
| What is the risk of deferring all alarms to the next scheduled service visit? | It treats deferral cost as if it were zero, and for contained bearing or gearbox wear, that exposure can convert a manageable repair into an unplanned outage with broader secondary consequences. |
| Which dispatch strategy is identified as the explicit winner? | Conditional dispatch on sustained multi-channel trends, with immediate dispatch reserved for coupled-channel escalation. |
| How does conditional dispatch on sustained multi-channel trends improve maintenance decisions? | It filters out transient, isolated signals before committing a crew, concentrates truck rolls on alarms that exhibit corroborated persistence, and escalates without delay when multiple mechanical channels escalate. |

Also worth reading: **AI dispatch scheduling: 40% downtime cut vs manual vs AI vs 2026**: [AI dispatch scheduling: 40% downtime](https://technician.dev/blog/ai-dispatch-scheduling-40-downtime-cut-vs-manual-vs-ai-vs-2026.php) · **Reducing unnecessary truck rolls with IoT and AI diagnostics**: [Reducing unnecessary truck rolls with](https://technician.dev/blog/reducing-unnecessary-truck-rolls-with-iot-and-ai-diagnostics.php) · **Work order closeout with voice: 18 to 3-4.2 minutes, dispatch or skip**: [Work order closeout with voice:](https://technician.dev/blog/work-order-closeout-with-voice-18-to-3-42-minutes-dispatch-or-skip.php)

### Related reading

- [AI dispatch scheduling: 40% downtime cut vs manual vs AI vs 2026](https://technician.dev/blog/ai-dispatch-scheduling-40-downtime-cut-vs-manual-vs-ai-vs-2026.php)
- [First Time Fix Rate: $19 Match vs $250 Repeat Truck Roll](https://technician.dev/blog/first-time-fix-rate-19-match-vs-250-repeat-truck-roll.php)
- [Remote Diagnostics: Evaluating the 40% Truck Roll Reduction Claim](https://technician.dev/blog/remote-diagnostics-evaluating-the-40-truck-roll-reduction-claim.php)
- [Stochastic Dispatch vs. Static Zones: A Verify-Before-You-Commit Guide](https://technician.dev/blog/stochastic-dispatch-vs-static-zones-a-verify-before-you-commit-guide.php)
- [AI Dispatch Decision Framework: Stochastic vs. Deterministic Scheduling — 12 FTF Points vs. 87% On-Time Target](https://technician.dev/blog/ai-dispatch-decision-framework-stochastic-vs-deterministic-scheduling-12-ftf-points-vs-87-on-time-target.php)
- [Reassign or hold: computing a per-dispatch technician break-even](https://technician.dev/blog/reassign-or-hold-computing-a-per-dispatch-technician-break-even.php)

### Latest

- [Stochastic Dispatch vs. Static Zones: A Verify-Before-You-Commit Guide](https://technician.dev/blog/stochastic-dispatch-vs-static-zones-a-verify-before-you-commit-guide.php)
- [AI Dispatch Decision Framework: Stochastic vs. Deterministic Scheduling — 12...](https://technician.dev/blog/ai-dispatch-decision-framework-stochastic-vs-deterministic-scheduling-12-ftf-points-vs-87-on-time-target.php)
- [AI dispatch scheduling: 40% downtime cut vs manual vs AI vs 2026](https://technician.dev/blog/ai-dispatch-scheduling-40-downtime-cut-vs-manual-vs-ai-vs-2026.php)

Canonical: https://technician.dev/blog/wind-turbine-vibration-thresholds-4200-truck-roll-vs-14-downtime-dispatch-or-defer.php
Markdown: https://technician.dev/blog/wind-turbine-vibration-thresholds-4200-truck-roll-vs-14-downtime-dispatch-or-defer.php/index.md
