Availability factor is the headline number that tells an owner how much of the time their generating equipment was actually ready to produce. It is deliberately separate from how much energy the plant made, because a plant can sit idle for reasons that have nothing to do with the equipment being broken, and a warranty needs to draw a fair line around what the manufacturer is responsible for. This guide defines availability factor, distinguishes the time-based and energy-based ways of measuring it, explains the contractual version that carves out grid and force-majeure hours, and shows how SCADA state codes turn raw operating status into an availability figure.
Availability factor in one line: Plant availability factor is the fraction of a period during which a plant, or a turbine or inverter within it, was ready and able to generate, whether or not it actually did. It can be measured on a time basis, counting the share of hours the equipment was available, or on an energy basis under standards like IEC 61400-26, weighting by the energy that could have been produced. Contractual availability further excludes hours lost to grid outages, force majeure, and other causes outside the operator's control, which is why it is the headline KPI in equipment warranties.
The simplest way to measure availability is by time: over a given period, what fraction of the hours was the equipment able to run? If a turbine was healthy and ready for ninety-eight of every hundred hours, its time-based availability is ninety-eight percent, regardless of whether the wind actually blew during those hours. Time-based availability is easy to compute and to reason about, which is why it has long been the default, but it treats every hour as equally valuable even though an hour of strong wind is worth far more than an hour of calm.
Energy-based availability corrects that blind spot by weighting each period of downtime by the energy that would have been produced during it. Under this view, being unavailable for two hours of a windy afternoon counts far more heavily than being unavailable for two hours of a still night, because the first lost real generation and the second lost almost none. The IEC 61400-26 family of standards formalises this approach for wind, providing a consistent framework for classifying operating time and for expressing availability in energy terms, so that owners and manufacturers can argue about performance using a common definition rather than each side's convenient one.
The two measures can diverge sharply, and which one a contract uses has real money attached. A turbine that always seems to break down in high wind will look far worse on an energy basis than on a time basis, and rightly so, because those failures cost the most. Owners generally prefer energy-based availability because it aligns the manufacturer's incentive with actual production, while the extra complexity is the price of that fairness, since estimating the energy that would have been produced during downtime requires modelling the wind and the would-be power curve.
Neither raw time-based nor raw energy-based availability is quite what a warranty guarantees, because a manufacturer cannot fairly be held responsible for downtime it did not cause. If the grid goes down and the plant is ordered off, if a storm exceeds design conditions, or if the owner's own actions take a unit offline, the equipment was arguably still ready to work. Contractual availability, the figure written into a service agreement, therefore starts from measured availability and adds back the hours lost to agreed exclusions such as grid outages, force majeure, scheduled maintenance windows, and owner-caused stops. The result is a number that reflects only the availability the service provider is accountable for.
Getting to that number depends on downtime allocation: for every interval a unit was not available, someone must decide whose fault it was. A component failure inside the turbine belongs to the OEM or service provider. A grid disconnection belongs to the network. A decision by the owner to hold a unit offline belongs to the owner. A lightning strike or an extreme storm belongs to force majeure. This allocation is where availability disputes are usually won or lost, because the same downtime hour counts against the guarantee or does not depending purely on which bucket it lands in, and the categorisation must be defensible if the owner later claims against the warranty.
Because so much money rests on the categorisation, the allocation cannot be a matter of opinion after the fact; it has to be traceable to what the equipment and the grid were actually doing at the time. That is why availability accounting leans on recorded status data rather than memory, so that when a claim is challenged, the operator can point to the timestamped record showing that a given outage was a grid trip and not an equipment fault, or the reverse.
Every modern turbine and inverter continuously reports its operating state to the SCADA system as a status or fault code: running normally, waiting for wind or sun, stopped by a fault, stopped for maintenance, curtailed by an external command, and so on. Computing availability is fundamentally the job of sorting all of that recorded time into two piles, available and unavailable, and then applying the exclusions. A unit waiting for wind is available; a unit stopped by its own fault is unavailable and belongs to the OEM; a unit held down by a grid command is unavailable but excluded from the contractual figure. The state codes are the raw evidence, and the mapping of codes to categories is the heart of an availability calculation.
This is precisely the kind of work a monitoring platform automates. Rather than an engineer manually reconstructing why each unit was down, the platform ingests the continuous stream of state codes, applies an agreed rulebook that maps each code to available, OEM-caused, owner-caused, grid, or force majeure, and rolls the result up into time-based and energy-based availability across the fleet. Because the underlying timestamped records are retained, any figure can be drilled back down to the specific outages that produced it, which is what makes the number defensible in a warranty conversation rather than merely plausible.
It is worth keeping availability distinct from the other headline KPI, performance ratio or the equivalent measure of how efficiently the equipment converted available resource into energy. Availability answers whether the equipment was ready; performance answers how well it worked when it ran. A plant can be almost perfectly available yet underperform because of soiling, degradation, or miscalibration, and it can perform beautifully in the hours it runs yet score poorly on availability because it keeps tripping offline. Owners track both, because a high number on one cannot rescue a low number on the other, and a cloud SCADA platform that gathers state and production data together lets a team watch the two side by side across a whole fleet.
Availability measures the share of time or energy for which the equipment was ready to run, regardless of whether the resource was there. Capacity factor measures the energy actually produced against what the plant could have produced at full nameplate for the whole period, so it folds in the wind or sun resource, curtailment, and downtime together. A plant can have very high availability yet a modest capacity factor simply because the wind was light or the sun was low.
IEC 61400-26 is the wind-industry standard family that defines how to classify a turbine's operating time and how to express availability, including on an energy basis. It gives owners and manufacturers a common framework for categorising available and unavailable time and for allocating downtime, so that availability guarantees are measured consistently rather than by each party's own definition. Using it reduces disputes because both sides compute the number the same way.
A service warranty typically guarantees only the availability the provider is responsible for, so downtime caused by grid outages, force majeure, or the owner is excluded from the guaranteed figure. Allocating each outage to the right cause therefore decides whether a given lost hour counts against the guarantee or not. Because that decision has direct financial consequences, the allocation must be traceable to the recorded status data at the time of the outage.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.