Background
NERC requires event detail reporting beginning in 2024 to identify forced outages across wind and solar plants that impact the grid. Currently, the GADS threshold for an event start is 20 MW. NERC defines an event end as 95% of the maximum plant total installed capacity that was unavailable at any point during the forced outage has been returned to service, and less than 20 MW of plant capacity is in a forced outage.
Bazefield greatly eases the Event Detail Reporting process by tracking plantwide events using domain points and alarms. The alarms drive allocations that store the event type, contributing operating condition, cause code - system, and cause code - description. All of this data is used in the 'GADS Export' application for Event Reporting. More detail on the process used to generate event allocations from Turbine/Inverter allocation is in the article GADS Event Script Model.
While users do not need to configure event reporting, it is still important to know where exactly in the portal the data is sourced from. This article tabulates each of the fields contained in a GADS Event Report in the context of the Bazefield Portal.
GADS Event Report
Table 1: Mapping GADS DRI Event Detail Record fields to the Bazefield Portal
| Field Name | GADS DRI Description | Bazefield Portal Location | |
| 1 | Entity ID | Enterthe NERC Compliance Registry ID number (NCR ID) or voluntary reporting ID assigned by NERC of the organization that operates the Wind/Solar plant. | Object Attribute on Wind/Solar Farm, key entityID |
| 2 | Plant ID | Enterthe Plant ID assigned by the GADS Wind/Solar reporting application. | Object Attribute on Wind/Solar Farm, key plantID |
| 3 | Event ID | Enter a unique identification forthe event. | This field is left blank by the export report. The user must enter an Event ID for each plant event. |
| 4 | Time Zone | Enter the Time Zone in which data are reported for the plant. This time zone will be used to convert Event Start and EndDate/TimestoUTC. | Object Attribute on Wind/Solar Farm, key timeZone |
| 5 | Event Start Date/Time | Enter the Event Start time (mm/dd/yyyy HH:MM) (24-hour clock format) | Power Plant Controller object, point name 'Event-GADSForcedDerate.Start'. This point is written to via API, with a Script Model 'PowerPlantController GADS Script', and should be 1 when the total capacity in a forced outage category at a site is >=20MW' |
| 6 | Event End Date/Time | Enter the Event End time (mm/dd/yyyy HH:MM) (24-hour clock format) | Power Plant Controller object, point name 'Event-GADSForcedDerate.End'. This point is written to via API, with a Script Model 'PowerPlantController GADS Script', and should be 1 when the total capacity in a forced outage category at a site is <20MW |
| 7 | Event Type | Enter the type of Event. | Allocation Type, name Event Type. The default for an event is 'Forced Outage'. This must be manually updated if the event is of another type. |
| 8 | Cause Code | Enter the cause for the outage. | Linked Allocation Types, names Cause Code - System & Subsystem and Cause Code - Description. The default for an event is 'Uncategorized: Please Choose'. This must be manually updated for each event. |
| 9 | Contributing Operating Condition | Enter the underlying environment related to the outage. Refer to Table 5.3 below for a list of Contributing Operating Conditions, descriptions, and examples. | Allocation Type, name Contributing Operating Condition. The default for an event is No Contributing Condition. This must be manually updated of the event has a Contributing Operating Condition. |
| 10 | Description | Provide text description of the circumstancesthat caused the event. | This field will pull the most recent comment from an event allocation, which should describe the event cause. |
| 11 | Potential MWh Production Loss | Enter the number of Potential MWh of Production loss during the duration of the event. See the Potential Production MWh Loss section below for a description of this field. | Allocation Property, Lost Production. Uses the Power Plant Controller point 'MaxCapacityForced'. This point is written to via API, with a Script Model 'PowerPlantController GADS Script', and sums the total capacity in a forced outage category at a site. |