Outage Event Reporting. Module 04 - GADS Data Reporting Workshops

Transcription

1 Outage Event Reporting Module 04 - GADS Data Reporting Workshops

2 Why Collect Event Records? Track problems at the plant for Your use Use by others Provide Proof of unit outages for interested parties such as Independent System Operators (ISOs), Public Utility Commissions (PUCs), consumers groups Histories of equipment for lessons learned Planning with data for determining length and depth of next/future outages. 2

3 Event Identification Required fields: Utility (Company) Code o Three character alpha-numeric code identifying the reporting organization o Assigned by OATI for NERC Unit Code o Three-digit code identifying the unit reported o Code distinguishes one unit from another in an utility o Code also sets the unit type in the GADS database Combination of the utility and unit codes uniquely identifies units! 3

4 Event Identification (cont.) Required fields: Year: the year the event occurred Event Number: unique number for each event o One event number per outage/derating o Need not be sequential Events that continue through multiple months keep the originally assigned number Events start when they start and end when they end events that continue through multiple months should be tracked as one long event and not ended/re-started each month 4

5 One Event for One Outage Event 1 Event 1 Event 1 Month 1 Month 2 Month 3 Event 1 5

6 Quick Quiz Some generators report a new event record for the same event if it goes from one month to the next or goes from one quarter to the next. What are the advantages of such actions to the GADS statistics? 6

7 Answer None! Disadvantages: Distorts the frequency calculation of outages Increases the work load of the reporter Increases the chances of errors in performance and event records o Hours of outage o Cause codes and event types 7

8 GADS is a DYNAMIC System Make as many changes as you need to, as many times as you need to, whenever you find errors in your data. GADS is in the business of historical performance reporting and we need accurate data. 8

9 Event Identification (cont.) Report Revision Code Shows changes to the event record (voluntary) o Original Reports (0) o Additions or corrections (1, 2, 9) o Report all records to a performance report Even if just one record is revised Why? PH = FOH + MOH + POH + RSH + SH + Sync + Cond Event Type Describes the event experienced by the unit (required) o Inactive o Active 9

10 Active Unit States 10

11 Inactive Unit States 11

12 Unit States Inactive (cont.) Inactive From IEEE 762, o Deactivated shutdown is the State in which a unit is unavailable for service for an extended period of time for reasons not related to the equipment. IEEE and GADS interpret this as o Inactive Reserve, o Mothballed, or o Retired 12

13 Unit States Inactive (cont.) Inactive Reserve (IR) A unit is unavailable for service but can be brought back into service after some repairs in a relatively short duration of time o Typically measured in days Excludes idle units due to a failure and dispatch did not call for operation Unit must be on Reserve Shutdown (RS) a minimum of 60 days before moving to IR status These events use Cause Code 0002 (three zeros plus 2) 13

14 Unit States Inactive (cont.) Mothballed (MB) A unit is o Unavailable for service but can be brought back into service after some repairs with appropriate amount of notification, typically in weeks or months o Not operable or is not capable of operation at a moments notice must be on a forced, maintenance or planned outage and remain on that outage for at least 60 days before it is moved to the MB state Use Cause Code 9991 for these events. 14

15 Unit States Inactive (cont.) Retired (RU) A unit is unavailable for service and is not expected to return to service in the future RU should be the last event for the remainder of the year o Up through December 31 at 2400 o The unit must not be reported to GADS in future submittals These events use Cause Code

16 NERC Compliance Units in IR or MB will not be included in fleet unit reporting statistics like Equivalent Availability Factors (EAF) or Equivalent Forced Outage Rate Demand (EFORd) because no period hours are being reported on them HOWEVER, unit-level compliance MAY still be open for NERC auditing under the NERC Reliability Standards Examples include Critical Infrastructure Protection (CIP), Emergency Preparedness and Operations (EOP), and Protection and Control (PRC) WECC requires compliance with their standards Check with your Region for rules 16

17 Unit States Active Active 17

18 Event Identification (cont.) Event Type (required choices) Two-character code describes the event o Outage, derating, reserve shutdown, or non-curtailing Event Types Outages PO Planned PE Planned Extension MO Maintenance ME Maintenance Extension SF Startup Failure U1 Forced - Immediate U2 Forced - Delayed Deratings PD Planned DP Planned Extension D4 Maintenance DM Maintenance Extension D1 Forced - Immediate D2 Forced - Delayed D3 Forced - Postponed U3 Forced Postponed RS Reserve Shutdown NC Non-curtailing 18

19 Unit States Active (cont.) What is an outage? An outage o Starts when the unit is either desynchronized (breakers open) from the grid or when it moves from one unit state to another o Ends when the unit is synchronized (breakers are closed) to the grid or moves to another unit state o In moving from one outage to the next, the time (month, day, hour, minute) must be exactly the same for the end of the previous outage and the start of the next! 19

20 Outage Types Timing starts WHEN THE PROBLEM IS DETECTED! Forced Outages (four types) Maintenance Outage (one type plus extension) Planned outage (one type plus extension) Outages Forced Maintenance Planned Before the end of next weekend (U3) 6 hours (U2) Now or very soon (U1) Can t start (SF) After the end of next weekend (MO/ME) Planned Well in Advance (PO/PE) 20

21 From the Unit State Diagram Unplanned Forced + Maintenance + Planned Active 21

22 From the Unit State Diagram Scheduled Forced + Maintenance + Planned Active 22

23 Unit States Active (cont.) Scheduled-type Outages Planned Outage (PO) o Outage planned Well in Advance Annual unit overhaul o Predetermined duration o Can slide PO if approved by ISO, Power Pool or dispatch Maintenance (MO) o Deferred beyond the end of the next weekend but before the next planned event (Sunday 2400 hours) Definition applies if an outage occurs before Friday at 2400 hours If the outage occurs after Friday at 2400 hours and before Sunday at 2400 hours, MO will only apply if the outage can be delayed passed the next, not current, weekend If the outage can not be deferred, the outage is a forced event 23

24 Unit States Active (cont.) Scheduled-type Outages Planned Extension (PE) o Continuation of a planned outage Maintenance Extension (ME) o Continuation of a maintenance outage 24

25 Unit States Active (cont.) Extensions are valid if All work during PO and MO events are determined in advance The work is within the original scope of work When unexpected problems or conditions are discovered during the outage and the result is a longer outage time o Do not use PE or ME PE or ME starts at the same time (month/day/hour/minute) that the PO or MO ended 25

26 PE or ME on January 1 at 00:00 Edit program checks to make sure an extension (PE or ME) is preceded by a PO or MO event Create a PO or MO event for one minute before the PE or ME Start of Event: End of Event:

27 Forced Outages (FO) U1 An immediate Unplanned (Forced) Outage Requires o Removal of a unit from service, another Outage State, or a Reserve Shutdown state o Cause code amplification code ONLY IF the U1 is preceded by the unit being in service (generating power) T1: Tripped/shutdown grid separation, automatic T2: Tripped/shutdown grid separation, manual 84: Unknown investigation underway Warning: Amplification code 84 is ignored until the end of the year so don t forget to change it as soon as you know the correct code! Required 27

28 Unit States Active (cont.) U1 An immediate Unplanned (Forced) Outage o If U1 is not a trip but the result of a change of state Example: from planned outage to U1 o Then the amplification code can be any appropriate amplification code if the reporter chooses to report amplification codes In-service (generating power) U1 Outage Amp code required = T1 (automatic) or T2 (manual) PO, MO, U1, etc. U1 Outage No amp code required 28

29 Unit States Active (cont.) Forced Outages Types Delayed (U2) o Does not required immediate removal from service o Requires removal within six (6) hours o Outage type only occurs when unit is in service Postponed (U3) o Does not required immediate removal from service o Outage is postponed beyond six (6) hours o Requires removal from service before the end of the next weekend o Outage type only occurs if the unit is in service Startup Failure (SF) o Unable to synchronize within a specified period of time or abort startup for repairs o Startup procedure ends when the breakers are closed 29

30 Is That Really a U1 Outage? Of the 42,762 FO events in 2016, 84.5% are U1 outages (36,130 events) 9.4 % are SF outages (4,032 events) 4.0 % are U2 outages (1,706 events) 2.1 % is U3 outages (894 events) With U1, amp cause codes are needed! If a boiler leak is detected and the unit remains in service for 2-4 more hours before starting to shut down for repairs then the boiler tube leak is a U2 event, not a U1. A U1 is an immediate event. 30

31 Event Description: River Glenn #1 is a 700 MW unit. On January 3 at 4:30 a.m., River Glenn #1 tripped off line due to high turbine vibration. The cause was the failure of an LP turbine bearing (Cause Code 4240). The unit synchronized on January 8 at 5:00 p.m Example #1 Simple Outage Capacity (MW) Forced Outage Cause Code Jan 3-Jan 4-Jan 5-Jan 6-Jan 7-Jan 8-Jan 9-Jan 31

32 32