Drive: Introduction to GADS

Last Modified on 2024-12-10 21:07:41 +0100

The Generating Availability Data System (or GADS) is a database of statistical reports from power stations in the United States and Canada.

Recognized as a valuable source of reliability information for total unit and major equipment groups, GADS is widely used by industry analysts in a variety of applications.1

GADS is maintained by the North American Electric Reliability Corporation (NERC) which requires eligible power producers to submit reports2 for:

  • Monthly Performance data on a quarterly basis.

  • Event data on a quarterly basis.

GADS is mandatory for the following renewable energy plants in the USA and Canada:

  • Wind sites with a Plant Total Installed Capacity greater than 75 MW that have been commissioned on January 1, 2005 or later.

  • PV sites with a Total Installed Wind Capacity of:

    • 100 MW or more in 2024

    • 20 MW or more in 2025.

NERC GADS Performance Calculations in Drive

Events and NERC Performance

In Drive, most NERC Performance metrics are calculated as the sum of hours in which an Asset has been in a specific state during a given period.

These states are defined by the Events recorded in Drive and the NERC Performance markers assigned to these events.

Default NERC Performance categorization per Event Code ensures that relevant events can be automatically categorized. The defaults include:

  • The markers assigned to PF Events 3 (any Event with a PF prefix, e.g., PF100) is predefined for ALL Customers (see below)

  • The markers assigned to Fault Code Events 4 are either

    • based on Power Factors' recommendations for major turbine and inverter manufacturers

    • defined by the Customer during Event Configuration.

3NERC Performance markers for PF Events cannot be changed.

4This option primarily applies to Wind Fault Codes as Power Factors strongly recommends configuring Inverter Fault Codes as Warnings – which do not have any categories associated. See the Drive Events: Warnings (User Guide) for more information.

To see how an Event Code is categorized, go to the Knowledge Base dashboard in the Manage module and view the NERC Performance column:

UG-GADSIntro_NERCPerformance.png

If the default marker does not accurately convey how an Event affects a Site’s performance, a different marker can be applied.

However, customers should read the following NERC resources before making any updates:

See Drive Events: NERC Performance Categorization for detailed instructions on how to categorize Events.

NERC Performance categorization

The tables below list all the available markers for PV and Wind sites, including which PF Events are assigned these markers by default.

PV NERC Performance markers

NERC Performance Markers

PF Events

1

Forced Outage Inverter Hours

  • PF100 Production Down

  • PF101 Inverter Down (Plant Down)

  • PF110 Production Down (Manual)

  • PF111 Inverter Down (Manual Plant Down)

2

Inactive Reserve Inverter Hours

N/A

3

Maintenance Inverter Hours

N/A

4

Mothballed Inverter Hours

N/A

5

Planned Inverter Hours

N/A

6

Reserve Shutdown Inverter Hours

  • PF520 Utility Curtailment

  • PF521 Inverter Utility Curtailment (Plant Curtailment)

  • PF530 Internal Curtailment

  • PF531 Inverter Internal Curtailment (Plant Curtailment)

7

Resource Unavailable Inverter Hours

  • PF160 Production Down (Snow)

  • PF701 Standby

8

Retired Inverter Hours

N/A

9

Service Inverter Hours

  • PF200 Production Degraded

  • PF220 Degraded - Soiling

  • PF221 Degraded - Soiling (Inverter)

  • PF225 Degraded - DC Outage

  • PF230 Degraded - Snow

  • PF231 Degraded - Snow (Inverter)

  • PF240 Degraded - Unknown

  • PF260 Production Degraded (Snow)

  • PF400 Communication Issue

Wind NERC Performance markers

NERC Performance Markers

PF Events

1

Contact

  • PF550 Turbine Deration

  • PF801 Overpower

2

Forced Turbine Hours

  • PF560 Turbine Down (Implicit)

3

Inactive Reserve

--

4

Maintenance Turbine Hours

--

5

Mothballed

--

6

OMC Forced Turbine Hours5

--

7

OMC Maintenance Turbine Hours5

--

8

OMC Pandemic (9015)5

--

9

OMC Planned Turbine Hours5

--

10

Planned Turbine Hours

--

11

Reserve Shutdown

  • PF570 Bat Curtailment

  • PF701 Standby

12

Resource Unavailable

  • PF710 Standby - No Resource

13

Retired

--

5These NERC Performance markers (“Outside Management Control”) are only relevant for reporting prior to 2024. NERC does not require reporting for these categories from January 1, 2024, so these markers should not be used.

See Drive Events: NERC Performance Categorization for detailed instructions on how to categorize Events.

GADS Performance calculations

In order to summarize the hours spent in each NERC state, Drive determines the relevant event for each timestamp. This determination is based on the NERC Performance markers of any events, and the NERC definitions:

GADS Performance Reporting

The primary result of the GADS Performance calculations is the quarterly NERC GADS Perforamnce reports. See Drive Reports: NERC Events & GADS Performance for more information.

NERC State visualizations

In addition to the reports, the NERC state of any inverters or wind turbines can be visualized via the:

Data & Trends: Historical dashboard

For Wind sites, customers can use the NERC_STATE.CALCULATED attribute to display the data for a specific reporting month for All Turbines in a Subgroup:

2409070636.png

Meanwhile for PV sites, customers can use the NERC_STATE.CALCULATED attribute to display the data for a specific reporting month for All Inverter Groups:

UG_NERC-GADS_NERCstate-PV.png

NERC_STATE.CALCULATED is visualized at the generator’s data resolution. This data can then be exported as an Excel file for further analysis.

NERC GADS Plant Events in Drive

NERC-FO Plant Events

Plant-level Events are also included in NERC specifications, starting January 2024. Criteria matching these events are replicated in Drive as NERC-FO (Forced Outage) Events.

NERC-FO Event calculations

Event Start

The NERC-FO event starts on the first timestamp where there are parallel events that are categorized as NERC Forced Outages across more than 20 MW of inverter or wind turbine capacity. This is based on the the NERC Performance marker Forced Outage Inverter Hours or Forced Turbine Hours.

  • The example below (from Chapter 5 of the NERC Data Reporting Instructions) shows a site with a Plant Total Installed Capacity of 100MW (A).

  • The event starts at 20MW (B), which is the result when the Start Plant Available Installed Capacity of 80MW is subtracted from the Plant Total Installed Capacity of 100MW.

Event Nadir

The Nadir of the NERC-FO event, i.e., the Minimum Plant Available Installed Capacity for event is determined as the largest total capacity of inverters or wind turbines with NERC Forced Outage events.

  • The example below shows an Event Nadir of 25MW (C).

Event End

The end of the NERC-FO event occurs when 95% of the capacity at that Nadir has returned to service. This is again evaluated by Drive by summing the capacity for inverters or wind turbines with NERC Forced Outage events.

  • The event ends when the capacity reaches 98.75MW (D), which is the result when the product of the Event Nadir of 25MW (C) and the Minimum Plant Available Installed Capacity is subtracted from the Plant Total Installed Capacity of 100MW (A).

Note that the 95% end criteria refers to the nadir of capacity that has been offline for NERC Forced Outage events. It is not related to 95% of the plant capacity.

UG_NERC-FO_Calculations.png

Cause Code

NERC has defined Cause Codes which indicate which equipment caused the outage. These can be attributed to any NERC-FO Event. The full lists of Cause Codes are defined by NERC:

Drive will establish an estimated Cause Code for all NERC-FO Events. This estimation is based on all parallel NERC Force Outage events at the inverters or wind turbines.

  1. The underlying events are aggregated using the System/Component categorization. See Drive Events: Categorization for System & Component for details.

  2. The System/Component with the highest cumulative energy loss (across the underlying events) is used to determine the most relevant Cause Code. The mapping between System/Component and Cause Code was established by Power Factors. Since both the System/Component and Cause Code lists were defined by NERC, there is most often a direct link.

Potential Production MWH Loss

There is a NERC-defined Potential Production MWH Loss which is calculated per event, per the NERC specifications. This is the sum of capacity lost during the period (MW Capacity loss multiplied by the duration of the event). It is shown as the green-shaded area in the example above.

Note that there is NO Drive Energy Loss Allocated (ELA) to these NERC-FO events, and they do not group with or interact with any other events in Drive.

NERC-FO Event visualizations

Events: Event Manager dashboard

In the Event Manager dashboard, customers can filter for NERC Plant Outage Events for a given reporting month at the Plant level:

UG_NERC-GADS_NERCplantOutage-PV.png

Customers can view the Event Details for any NERC-FO event to see the underlying attributes supporting the start and end times:

  • NERC_AC_CAPACITY_IN_OUTAGE.CALCULATED6

    • This is the basis for the start and end times of the event.

  • NERC_AC_CAPACITY_AVAILABLE.CALCULATED

  • NERC_NUMBER_OF_GENERATORS_IN_OUTAGE.CALCULATED

UG_NERC-FO_EventDetails.png

Data & Trends: Historical dashboard

The following attributes may also be viewed in the Data & Trends Historical dashboard at the Plant level:

  • NERC_AC_CAPACITY_IN_OUTAGE.CALCULATED6

  • NERC_AC_CAPACITY_AVAILABLE.CALCULATED

  • NERC_NUMBER_OF_GENERATORS_IN_OUTAGE.CALCULATED

UG_NERC-FO_Historical.png

6The NERC_AC_CAPACITY_IN_OUTAGE.CALCULATED attribute is the basis for the start and end time of the NERC-FO Event.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article