Primary Events

The value in the Event Start and Event End fields identify the way in which an event contributes to the NERC GADS Event Report 07 or NERC GADS Performance Report 05. This topic describes how these fields contribute to the reports in various scenarios.

Scenario 1: Event start and end date are known

In this scenario, the Event Start field contains the actual date when the event started and the End Date field contains the actual date when the event ended. The actual date can be a date of the past or current date. The following will be true in this scenario:

• The Start Date is Estimated? check box must be cleared.
• The End Date is Estimated? check box must be cleared.
• The NERC GADS Event Report 07 includes the event.
• The NERC GADS Performance Report 05 includes the effect on performance due to this event.

Scenario 2: Start date is known but event end date is unknown

In this scenario, the Event Start field contains the actual date when the event started, but the End Date field contains no value to indicate when the event might end. The actual date can be a past date or the current date. The following will be true in this scenario:

• The Start Date is Estimated? check box must be cleared.
• The End Date is Estimated? check box must be cleared.
• The NERC GADS Event Report 07 includes the event with no value in the Event End field.
• The NERC GADS Performance Report 05 includes the event with the end of month as the value in the Event End field. The report also includes the effect on performance due to this event.

Scenario 3: Start date is known but event end date is estimated

In this scenario, the Event Start field contains the actual date when the event started but the End Date field contains an estimated date in future when the event might end. The actual date can be a past date or the current date. The following will be true in this scenario:

• The Start Date is Estimated? check box must be cleared.
• The End Date is Estimated? check box must be selected.
• The NERC GADS Event Report 07 includes the event with no value in the Event End field.
• The NERC GADS Performance Report 05 includes the event with no value in the Event End field. The report also includes the effect on performance due to this event.

Scenario 4: Start and End date of an event are estimated

In this scenario, the Event Start field contains the estimated date in future when the event will start and the End Date field contains an estimated date in future when the event might end. The following will be true in this scenario:

• The Start Date is Estimated? check box must be selected.
• The End Date is Estimated? check box must be selected.
• The NERC GADS Event Report 07 does not include the event.
• The NERC GADS Performance Report 05 does not include the event.

Some types of events have only one possible cause. In Events where the value in Capacity Event Type field identifies a single-cause event, the Cause Code System, Cause code Component, and Cause Code fields will be disabled and populated automatically with the appropriate cause code. The following table lists these Capacity Event Type values and their corresponding Cause Code values.

This topic describes the event types that are defined for a GAA Unit that reports to NERC and a GAA Unit that reports to CEA.

Event Types for a GAA Unit that Reports to NERC

Each Primary and Contributing Event can be either in Inactive State or Active state. Each Primary or Contributing Event must be classified using a value in the Capacity Event Type field.

• Inactive State: Indicates the state in which a unit is unavailable for service for an extended period of time for reasons not related to the equipment. There are three types of events in an Inactive state:

  • IR (Inactive Reserve): The unit could not generate power but can do so after some repairs. You can create this event only as a Related Event to a Reserve Shutdown Event when the duration of the event is more than 60 days.
  • MB (Mothballed): The unit could not generate power but can do so after some repairs with an appropriate notification period. You can create this event only as a Related Event to an Outage Event when the duration of the event is more than 60 days.
  • RU (Retired): The unit could not generate power and will never do so in the future.

• Active State: Indicates the state in which a unit is available to generate power. There are four types of events in an Active state:

  • Outage Events: The unit could generate no power during the event. If a Primary Event or Contributing Event contains one of the following values in the Capacity Event Type field, it is considered an outage event:
    • U1 (Unplanned (forced) Outage - Immediate)
    • U2 (Unplanned (forced) Outage - Delayed)
    • U3 (Unplanned (forced) Outage - Postponed)
    • MO (Maintenance Outage)
    • PO (Planned Outage)
    • ME (Maintenance Outage Extension): This event type will be available only when you create a Related Event.
    • PE (Planned Outage Extension): This event type will be available only when you create a Related Event.
    • SF (Startup Failure): This event type will be available only when you create a Related Event.
  • Derate Events: The unit could produce power during the event, but at a reduced capacity. If a Primary Event or Contributing Event contains one of the following values in the Capacity Event Type field, it is considered a derate event:
    • D1 (Unplanned (forced) Derating - Immediate)
    • D2 (Unplanned (forced) Derating - Delayed)
    • D3 (Unplanned (forced) Derating - Postponed)
    • D4 (Maintenance Derating)
    • DM (Maintenance Derating Extension): This event type will be available only when you create a Related Event.
    • PD (Planned Derating)
    • DP (Planned Derating Extension): This event type will be available only when you create a Related Event.

  • Reserve Shutdown Events: The unit can produce power during the event, but is generating no power due to lack of demand. You must not report a Reserve Shutdown. If a Primary Event or Contributing Event contains the following value in the Capacity Event Type field, it is considered an Reserve Shutdown event:

    • RS (Reserve Shutdown)

  • Non-Curtailing Events: The unit could produce power during the event, although an equipment or a major component was removed for maintenance, testing, or other purposes. If a Primary Event or Contributing Event contains the following value in the Capacity Event Type field, it is considered an Non-Curtailing event:

    • NC (Noncurtailing Event)

Event Types for a GAA Unit that Reports to CEA

Each Primary Event can be either in Commercial Service State or Not in Commercial Service state. Each Primary Event must be classified using a value in the Capacity Event Type field.

• Not in Commercial Service State: Indicates the state in which a unit is unavailable for commercial service for an extended period of time, to perform repairs that will improve the performance of the unit and extend the life of the plant. The following are the events types that are associated with a unit in the Not in Commercial Service state:

  • 30-1 (Not-in-Commercial Service (NICS) (Decommissioned))

  • 30-2 (Not-in-Commercial Service (NICS) (Mothballed))

  • 30-3 (Not-in-Commercial Service (NICS) (Refurbishment))

  • 30-4 (Not-in-Commercial Service (NICS) (Deferred))

• Commercial Service State: Indicates the state in which a unit is available for commercial service. The following are the event types that can be associated with a unit in the Commercial Service state:

  • 11-1 (Operating (O) in a Synchronous Condenser Mode)
  • 11-2 (Operating (O) in Spin no Load Mode)
  • 12 (Operating under a Forced Derating (OFD))
  • 12-1 (Operating under a Forced Derating (OFD) (Synchronous Condenser))
  • 12-2 (Operating under a Forced Derating (OFD) (Spin No Load))
  • 13 (Operating under a Scheduled Derating (OSD))
  • 13-1 (Operating under a Scheduled Derating (SD) (Synchronous Condenser))
  • 13-2 (Operating under a Scheduled Derating (SD) Spin no Load)
  • 14 (Available but not Operating (ABNO))
  • 14-1 (Available but not Operating (ABNO) (Synchronous Condenser))
  • 14-2 (Available but not Operating (ABNO) (Spin No Load))
  • 15 (Available but not Operating (Forced Derating) (ABNO-FD))
  • 15-1 (Available but not Operating (Forced Derating) (ABNO-FD) (Synchronous Condenser))
  • 15-2 (Available but not Operating (Forced Derating) (ABNO-FD) (Spin No Load))
  • 16 (Available but not Operating (Scheduled Derating) (ABNO-SD))
  • 16-1 (Available but not Operating (Scheduled Derating) (ABNO-SD) (Synchronous Condenser))
  • 16-2 (Available but not Operating (Scheduled Derating) (ABNO-SD) (Spin no Load))
  • 21-1 (Forced Outage (FO) (Sudden Forced Outage))
  • 21-2 (Forced Outage (FO) (Immediately Deferrable Forced Outage))
  • 21-3 (Forced Outage (FO) (Deferrable Forced Outage))
  • 21-4 (Forced Outage (FO) (Starting Failure Outage))
  • 22 (Forced Extension of Maintenance Outage (FEMO))
  • 23 (Forced Extension of Planned Outage (FEPO))
  • 24 (Maintenance Outage (MO))
  • 25 (Planned Outage (PO))

The Entity ID field in all Events is generated automatically, but the fields that are used to generate the values are different for Primary Events and Contributing Events.

• The value in the Entity ID field for each Primary Event is unique to all Primary Events that are linked to a given Generation Unit. The Entity ID in Primary Events is generated automatically using the following format:

  <Event ID> ~ <Cause Code Description> ~ <Capacity Event Type>

  ...where:

  • <Event ID> is the value in the Event ID field.
  • <Cause Code Description> is the value in the Cause Code field.

  • <Capacity Event Type> is the value in the Capacity Event Type field.

    The value in the Event ID field in Primary Events is generated using the following format:

    <Unit ID> ~ <Reporting Year> ~ <Event Number>

    ...where:

    • <Unit ID> is the value in the Unit ID field.
    • <Reporting Year> is the value in the Reporting Year field.
    • <Event Number> is the value in the Event Number field. If the value in the Event Number field is fewer than four digits, zeros will be added in front of the value so that the event number in the Event ID field will be four digits.

• The value in the Entity ID field in Contributing Events identifies the Primary Event to which the Contributing Event is linked. The values in the Entity ID field in all Contributing Events that are linked to a given Primary Event will match one another. The Entity ID in Contributing Events is generated using the following format:

  <Primary Incident ID> ~ <Capacity Event Type> <Cause Code>

  ...where:

  • <Primary Incident ID> is the value in the Primary Incident ID field.
  • <Capacity Event Type> is the value in the Capacity Event Type field.

The Primary Incident ID field is populated automatically with the value in the Event ID field in the Primary Event for which the Contributing Event exists. The value in the Primary Incident ID field for all Contributing Events will match the value in the Event ID field in the Primary Event to which they are linked.

For example, suppose the following diagram.

The Entity ID of the first Primary Event begins with GAA Unit ~ 2016 ~ 0001. You can identify the Contributing Event that is linked to this Primary Event because its Entity ID also begins with GAA Unit ~ 2016 ~ 0001.

The Entity ID of the second Primary Event begins with GAA Unit ~ 2016 ~ 0002. This event is linked to two Contributing Events, both of which begin with GAA Unit ~ 2016 ~ 0002, which allows you to determine that both Contributing Events are linked to the second Primary Event.