IEEE 762 Service Hours Vs Period Hours: Definitions, Formulas, and NERC GADS Application

A single miscoded event can turn a strong availability number into an audit finding. The most common cause is confusion about which hour category an event belongs to and which denominator a metric requires. The distinction between Institute of Electrical and Electronics Engineers (IEEE) 762 service hours and period hours sits at the center of that confusion, and getting it wrong distorts every reliability index you submit to North American Electric Reliability Corporation (NERC).

Under IEEE 762, Service Hours are the hours a unit was synchronized to the system. Period Hours are the total hours in the reporting period during which the unit was in the active state, the denominator for factors like availability and service. Most conventional factors and rates in NERC GADS (Generator Availability Data System) reporting generally trace back to one of these two numbers, and confusing them produces figures that do not reconcile against benchmarks or survive a regional entity review.

What is the difference between service hours and period hours

Period Hours is greater than or equal to Service Hours, and Service Hours is a subset of it. IEEE 762, formally titled “Definitions for Use in Reporting Electric Generating Unit Reliability, Availability and Productivity,” establishes both. NERC GADS Appendix F names the standard directly: “The basis for these relationships is IEEE Standard No. 762 ‘Definitions for Use in Reporting Electric Generating Unit Reliability, Availability and Productivity.’”

Period Hours (PH) is the number of hours in the reporting period that the unit was in the active state. NERC GADS defines it as the sum of Available Hours and Unavailable Hours. In practice, for a unit that exists for the full period, Period Hours equals the total clock time: 720 hours in a 30-day month, 8,760 in a standard year. It is the denominator that answers “out of all the time that passed, how much of it did the unit spend in a given state?”

Service Hours (SH) is the sum of all hours the unit was synchronized to the system. Operationally, NERC GADS calls it the “sum of hours synchronized to system.” Service Hours is a subset of Available Hours, which is itself a subset of Period Hours. A unit accrues Service Hours only when it is electrically connected. Every hour a unit spends offline, whether for an outage or because the market did not call for its output, counts toward Period Hours but not toward Service Hours. Hours spent in Reserve Shutdown, where the unit is available but not dispatched, count within Available Hours, not Service Hours.

The definitions have shifted across the editions in this comparison. IEEE 762-1987 framed both terms as unit states. IEEE 762-2006 reframed Service Hours around electrical connection and Period Hours around total clock time. IEEE published IEEE 762-2023 on August 15, 2023; the 2023 edition superseded the 2006 edition and extended the framework to variable energy resources.

How period hours break down into service hours

Period Hours splits into two branches, and Service Hours sits at the end of one of them. The master accounting equation is straightforward: Period Hours equals Available Hours plus Unavailable Hours. Available Hours then decompose further, and Service Hours is the portion during which the unit was synchronized to the system.

The full hierarchy maps as follows:

Service Hours represents the subset of Period Hours that remains after the accounting hierarchy assigns outage hours to Unavailable Hours and available-but-not-generating hours to non-service available states. That second assignment is where most reporting errors originate.

Available hours and unavailable hours

Available Hours measure the time a unit could have generated, whether or not it did. NERC GADS Appendix F defines Available Hours as Service Hours plus Reserve Shutdown Hours plus Pumping Hours plus Synchronous Condensing Hours. A combustion turbine sitting ready but undispatched on a mild spring day accrues Available Hours without accruing Service Hours. That gap is normal for peaking units.

Unavailable Hours measure the time the unit could not have generated at all. Appendix F defines them as the sum of Planned Outage Hours, Forced Outage Hours, and Maintenance Outage Hours, including any outage extensions. Every hour in this branch is an hour the unit was physically or administratively incapable of serving load.

The path from Period Hours to Service Hours runs through two branches. Outage hours accrue to the Unavailable branch. Reserve shutdown hours sit in the Available branch but do not count as Service. Both distinctions matter, and they behave differently in the formulas.

Outage state classifications

Outage hours accrue to the Unavailable branch, and Service Hours is what remains of Period Hours after both outage hours and available-but-not-generating hours are removed. NERC GADS classifies forced outages into three urgency tiers plus startup failures, and separates planned from maintenance outages by how far in advance operators scheduled the work.

The forced outage classifications turn on how quickly the unit must come offline:

• U1, immediate: An outage requiring immediate removal of the unit from service, another outage state, or a reserve shutdown state. It typically results from automatic control system trips or operator-initiated manual trips, but can also occur while the unit is offline.
• U2, delayed: An outage that does not require immediate removal but requires the unit to come offline within six hours. It can only occur while the unit is in service.
• U3, postponed: An outage that can be postponed beyond six hours but requires removal before the end of the next weekend (Sunday at 2400 or before Sunday turns into Monday). It can only occur while the unit is in service.

Startup Failure (SF) covers a unit unable to synchronize within a specified period or aborting startup for repairs. NERC GADS includes SF in Forced Outage Hours. IEEE 762 does not count SF in its forced outage totals, one of the specific points where the GADS implementation departs from the base standard.

Operators schedule Planned Outages well in advance with a predetermined duration and scope. Operators defer Maintenance Outages beyond the end of the next weekend but must take them before the next planned outage. Both, along with their extensions (PE and ME), sit in the Unavailable branch and never appear in Service Hours.

Reserve shutdown hours

Reserve Shutdown is the single most common source of confusion in the service-versus-period distinction. A reserve shutdown event is one where the unit is available for load but is not synchronized due to lack of demand. NERC GADS describes it as sometimes being called an economy outage or economy shutdown. The unit is available for load, but the market did not dispatch it.

Reserve Shutdown Hours enter Available Hours and stay outside Service Hours. This is why a peaking gas turbine can post a Service Factor of 6 percent and an Availability Factor of 88 percent in the same reporting period. The unit was available almost all the time and dispatched almost none of it. If you treat reserve shutdown hours as if they reduce availability, or fold equipment problems into a reserve shutdown event, you distort both numbers.

The governing rule is explicit: if a unit is shut down due to any equipment-related problem, report a forced, maintenance, or planned outage, whether or not the system needed the unit. Do not report a Reserve Shutdown. A shutdown driven by equipment is never a reserve shutdown, even when demand was low at the same moment.

Service factor vs availability factor: two formulas, two questions

Service Factor and Availability Factor share the same denominator and ask different questions. Both divide by Period Hours. The numerators diverge: one counts synchronized time, the other counts available time.

Service Factor measures how much of the period the unit spent generating:

SF = Service Hours / Period Hours × 100%

Availability Factor measures how much of the period the unit was capable of generating:

AF = AH / PH × 100%

Service Factor answers a dispatch question: what fraction of the time was this unit running and putting power on the grid? A high Service Factor indicates a baseload unit that runs nearly continuously. A low one indicates a peaker that runs only when called.

Availability Factor answers a readiness question: what fraction of the time could this unit have run if the system had needed it? It strips out the dispatch decision and isolates the unit’s condition and readiness. The gap between AF and SF for any unit is largely the reserve shutdown time, the hours the unit was ready but not called.

For the 2018-2022 period, NERC GADS Statistical Brochure 4 reports coal units at a 64.13 percent Service Factor and 81.13 percent Availability Factor, while gas turbines fifty megawatts and larger split 6.63 percent against 88.51 percent.

When to use service hours vs period hours as the denominator

The choice of denominator follows a single NERC GADS principle: factors use Period Hours, rates use Service Hours. NERC GADS Training Module 11 states it directly: “Factors in NERC GADS are generally based on Period Hours (PH) because they indicate performance over the entire period, whereas rates are generally based on Service Hours (SH) because they indicate performance during the time the unit was running.”

A factor tells you how the unit performed across all the time that passed, dispatched or not. Availability Factor, Service Factor, Forced Outage Factor, and Equivalent Availability Factor all divide by Period Hours. A rate tells you how the unit performed during the hours it was running or was needed. Forced Outage Rate and the equivalent forced outage rates divide by a service-based denominator because they condition the answer on demand.

Misapplying this principle produces figures that will not match benchmarks. Compute EFORd with Period Hours in the denominator instead of the service-based demand denominator, and the number you submit will not be comparable to the industry values a regional entity uses for reference.

How NERC GADS implements these definitions

NERC GADS Appendix F operationalizes the IEEE 762 hour definitions into the exact equations that produce mandatory reliability indexes. Mandatory reporting applies to generators of twenty megawatts and larger in North America, a threshold in effect since January 1, 2013.

Reporting runs on a quarterly cycle. You submit event and performance data to Open Access Technology International (OATI) through the webE-GADS data collection system within forty-five days after the end of every calendar quarter. Service Hours and Period Hours enter through the 05 Performance Data file, Section D, which holds thirteen fields reporting sums of hours for the unit’s states during the month, and the roll-up produces Available Hours, Unavailable Hours, and finally Period Hours as their sum.

EFORd and demand-period weighting

EFORd weights forced outage hours by demand periods, and Appendix F builds its denominator from Service Hours rather than Period Hours. The formula is:

EFORd = (FOHd + EFDHd) / (SH + FOHd) × 100%

The EFORd denominator uses Service Hours. The denominator is restricted to hours during which the unit was either in service or would have been in service during demand periods (SH + FOHd), which conditions the entire rate on demand. FOHd is forced outage hours adjusted for demand periods, calculated as the demand factor f multiplied by forced outage hours. EFDHd is equivalent forced derated hours adjusted the same way. Reserve shutdown hours do not sit in the EFORd denominator at all.

Service Hours enter EFORd through three inputs:

• Denominator: SH forms the demand-time base in SH + FOHd.
• Demand factor f: Average demand time D equals Service Hours divided by the number of actual unit starts.
• fp fallback: When reporters submit no reserve shutdown events, GADS calculates fp as Service Hours divided by Available Hours.

That relationship between SH and AH shapes the EFORd you report.

Outside management control (OMC) reclassification

GADS software performs OMC reclassification as a computational step. Reporters should not change the submitted event data. NERC GADS is emphatic that every cause code, including OMC codes, must be reported; the OMC calculations then show the events without the forced outage. You must not exclude a forced outage or downgrade it when the cause was outside the operator’s control, such as a lightning strike or a fuel supplier’s force majeure.

GADS produces a parallel set of “without OMC” statistics, prefixed with X, such as XEFORd. When GADS removes OMC events for these X-series figures, it adds the hours back to Available Hours, not to Service Hours. NERC Appendix K notes: “we are increasing available hours and not service hours even though we are reducing outage hours.” Because fp equals Service Hours divided by Available Hours, removing OMC events increases the denominator and shrinks the demand-weighted numerator terms. Report every cause code, including OMC codes, and let the software carve out the OMC-adjusted view.

Weighted vs unweighted pooling methods

Fleet statistics can be pooled two ways, and the choice changes whether a large unit and a small unit count equally. Unweighted, or time-based, pooling treats all units as equal in outage impact, so results reflect time alone. Weighted, or capacity-based, pooling incorporates Net Maximum Capacity so that larger units carry proportionally more influence on the fleet number.

The weighting rule is easy to get wrong. You do not take each unit’s EFOR, multiply by its Net Maximum Capacity, sum, and divide by the summed capacities. NERC GADS requires that each term in the equation be multiplied by the unit’s Net Maximum Capacity first, then all products summed across the fleet. Net Maximum Capacity is gross maximum capacity less station service, and it also weights capacity-based indexes such as Equivalent Availability Factor. Net Dependable Capacity is the net level the unit can sustain given ambient conditions, and the gap between the two drives Equivalent Seasonal Derated Hours.

Worked calculation example: one unit, one month

Assign hours to each state category, and the two denominators become concrete. Consider one unit over a 30-day month, giving 720 Period Hours. During the month the unit was synchronized and generating for 500 hours, sat in reserve shutdown for 150 hours because demand was low, and was on a forced outage for 70 hours.

The hours assign as follows:

Service Factor divides Service Hours by Period Hours (500 / 720 × 100% = 69.4%), and Availability Factor divides Available Hours by Period Hours (650 / 720 × 100% = 90.3%). The 21-point gap between the two is almost entirely the 150 reserve shutdown hours.

EFORd uses the service-based denominator, where FOHd = f × FOH. Ignoring deratings for simplicity and treating FOHd as the full 70 forced outage hours, EFORd approaches 70 / (500 + 70) × 100% = 12.3%. The 150 reserve shutdown hours play no part here.

Common reporting errors and how to avoid them

Most GADS findings start with hour classification errors, especially reserve shutdown and OMC treatment. Derating-hour omissions create the same structural problem. Each error moves hours into the wrong branch of the hierarchy and distorts a specific index.

The recurring errors follow a pattern:

• Coding an equipment-related shutdown as reserve shutdown: This removes equipment-caused hours from the Forced Outage Hours numerator and produces an artificially optimistic EFORd.
• Recording an invalid RS-to-U2 transition: Reserve shutdown is an offline state and a U2 delayed forced outage can only occur from an online state, so a direct transition between them is invalid and will fail validation.
• Excluding OMC events instead of reporting them: OMC events must be reported as forced, maintenance, or planned outages, with the OMC cause code attached. The software generates the without-OMC view. Suppressing the event at entry corrupts both the standard and the X-series statistics.
• Omitting forced deratings during a legitimate reserve shutdown: Failing to report derates that occur during reserve shutdown understates Equivalent Forced Derated Hours during Reserve Shutdown, which flows into EFORd through the fp factor.

These errors happen at data capture and classification, and they surface months later as self-reports or audit findings. The structural fix is to catch the miscoding at the point of entry rather than during audit assembly. PowerGADS connects to your PI historian and SCADA systems to capture unit events directly and runs more than 200 built-in validations against the Appendix F rules as events are recorded. It maintains a full audit trail so your team catches a reserve shutdown that should have been a forced outage before submission. Most teams are live in under four weeks.

Related concepts

The service-versus-period framework changes shape for variable energy resources, and IEEE 762-2023 is where that change enters the standard. IEEE 762-2023 adds Expected Generation, the energy a unit could have produced given measured ambient conditions, and uses it as the denominator in generation-based indexes such as the Forced Outage Generation Rate.

Two adjacent measures round out the picture: commercial availability, which weights availability by the unit’s contractual or market obligations rather than clock time, and critical period indexes, which isolate reliability during the highest-demand hours when unavailability costs the most.

FAQ

What is the exact difference between Service Hours and Period Hours under IEEE 762? Service Hours are the hours a unit was synchronized to the system, while Period Hours are the total hours in the reporting period that the unit was in the active state. Period Hours equals Available Hours plus Unavailable Hours, and Service Hours is a subset of Available Hours.

How does Reserve Shutdown fit into the hour accounting? Reserve Shutdown Hours count as Available Hours but not as Service Hours, because the unit is available for load but not synchronized. This is why availability can be high while the Service Factor is low, and an equipment-related shutdown is never a reserve shutdown even during low demand.

How does NERC GADS implement the IEEE 762 definitions? NERC GADS Appendix F converts the IEEE 762 hour definitions into the equations that produce mandatory reliability indexes. Units of twenty megawatts and larger report through the webE-GADS system within forty-five days of each calendar quarter.

When should I use each denominator? Use Period Hours for factors such as Availability Factor and Service Factor, which measure performance across the entire period. Use Service Hours for rates such as Forced Outage Rate and EFORd, which measure performance during the time the unit was running or needed.

How do outage hours fit between Period Hours and Service Hours? Outage hours, including forced, planned, and maintenance outages plus extensions, do not reduce Period Hours itself. They sit in Unavailable Hours, so those Period Hours do not qualify as Available Hours or Service Hours. Reserve shutdown and other available-but-not-generating hours then reduce Available Hours down to Service Hours, and what remains is synchronized, generating time.

How does EFORd use Service Hours and Period Hours? EFORd uses Service Hours in its denominator: (FOHd + EFDHd) divided by (SH + FOHd), times 100 percent, because it measures forced unavailability conditioned on demand. Service Hours also enters the demand factor and, when no reserve shutdown events are reported, the partial factor fp equal to Service Hours divided by Available Hours.