1 / 25

Move to Mandatory Wind Data Collection – View Into the Future

Move to Mandatory Wind Data Collection – View Into the Future. G. Michael Curley, Manager – GADS Service WECC VGS Meeting December 3, 2010; Salt Lake City. GADS Task Force. Talked about mandatory GADS reporting for many years.

erol
Download Presentation

Move to Mandatory Wind Data Collection – View Into the Future

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Move to Mandatory Wind Data Collection – View Into the Future G. Michael Curley, Manager – GADS Service WECC VGS Meeting December 3, 2010; Salt Lake City

  2. GADS Task Force • Talked about mandatory GADS reporting for many years. • In June 2010, the NERC Planning Committee (PC) approved a task force to determine if GADS should be mandatory and to what level. • About 77% of the installed capacity already report to GADS. • Voluntary database now. • To date, the GADSTF will recommend mandatory reporting.

  3. How Does This Affect Wind? (2 weeks ago)

  4. How Does This Affect Wind? (Today)

  5. New Wind Data Reporting Instructions

  6. Since the last presentation … • Started work in June 2006. • 88 members of the Wind Turbine Working Group • Owners/operators • ISO • PUC • Wind organizations (UWIG, AWEA)

  7. Description of WTG Hierarchy Plant (Farm or Park)  Group  Subgroup Group 1 Group 2 Group 3

  8. States of Operation

  9. What Are “Turbine-hours”? • Turbine-Hours are equal to the number of turbines in the group or sub-group times the number of Calendar Hours in the period. TH for any given condition for a given sub-group is equal to the total number of Calendar Hours that each wind turbine (WTG) in the sub-group spent in the given condition. • All of the following time/condition classifications are considered to be in turbine-hours. • For example, the number of TH for a group of 12 WTG in January (with 744 hours in January) would be 12 x 744 or 8,928 TH. • If one of those turbines were mothballed, the Period Turbine-Hours (PTH) would be 11 x 744 or 8,184 PTH with 744 Inactive Turbine-Hours.

  10. WTG Available Turbine Hours • Period Turbine-Hours – PDTH - the number of hours that turbines within the sub-group are in the active state. PDTH can vary in output reports (month, year, etc.) but for GADS reporting purposes, data is collected on the number of turbine-hours in a month. • Contact Turbine-Hours – CTH - the number of hours that turbines within the sub-group are synchronized to the system. It is the turbine-hours that the contactors are closed without regard to the grid connection. • Reserve Shutdown Turbine-Hours – RSTH - the sum of all hours that turbines within the sub-group are available to the system at a reduced capacity for economic reasons. There are no equipment problems and the turbines are ready for service. Do not include RSTH in the same equations with CTH because this would double count turbine-hours

  11. RUTH – Available and Unavailable • Resource Unavailable Turbine-Hours (RUTH) • RUTH is the number of turbine-hours the turbines within a sub-group is not producing electricity due to the wind too low or too high or was outside manufacturer’s operating specifications. For example, if 10 turbines stopped generating because of wind conditions for 3 hours each, RUTH would equal 30 turbine hours. RUTH is classified as Available Turbine-Hours for equipment calculations and Unavailable Turbine-Hours for site calculations.

  12. Time Spent in Various Unit States Calendar Hours (CalTH) Inactive Hours(ITH) Period Hours (PDTH) Inactive Reserve(IRTH) Mothballed(MBTH) Retired(RTH) Available (SATH or EATH) Unavailable (SUTH or EUTH) Contact (CTH) Reserve Shutdown (RSTH) Planned Outage (PTH) Unplanned Outage Resource Unavailable (RUTH) Forced Outage (FTH) Maintenance Outage (MTH)

  13. Proposed Survey for Data Requirements

  14. Proposed Survey for Data Requirements

  15. Proposed Survey for Data Requirements

  16. Proposed Survey for Data Requirements

  17. Proposed Survey for Data Requirements

  18. Answer to One Question …

  19. Questions?

  20. Rules of Procedure: Section 1600Overview • NERC’s authority to issue a mandatory data request in the U.S. is contained in FERC’s rules. Volume 18 C.F.R. Section 39.2(d) states: “Each user, owner or operator of the Bulk-Power System within the United States (other than Alaska and Hawaii) shall provide the Commission, the Electric Reliability Organization and the applicable Regional Entity such information as is necessary to implement section 215 of the Federal Power Act as determined by the Commission and set out in the Rules of Procedure of the Electric Reliability Organization and each applicable Regional Entity.”

  21. Rules of Procedure: Section 1600Procedure NERC Approval Committees Acting Subgroup Not Approved Submit Data Request to PC Submit Data Request to DCS Draft Data Request Data Rule In Effect Not Approved Public Comment Period FERC Comment Period Submit Data Request Post Data Request (45 Days) File Data Request (21 Days) No Appeal Collect, Respond, & Post Comments NERC Board of Trustees Affected Parties Submit Final Data Request Appeal (30 Days) Finalize Data Request Approved Not Approved

  22. Rules of Procedure: Section 1600Limitations • NERC Registered Entities • Subject to FERC Rules • Data Request does not carry the same penalties to non-U.S. entities. • However, all NERC Registered Entities, regardless of their country of origin, must comply with the NERC Rules of Procedure, and as such, are required to comply with Section 1600

  23. What If a GO Doesn’t Comply? • Possible NERC actions: • NERC may resort to a referral to FERC for only United States entities, not Canadian entities. NERC will make use of the mechanisms it has available for both U.S. and Canadian entities (notices, letters to CEO, requests to trade associations for assistance, peer pressure) to gain compliance with the NERC Rules. A failure to comply with NERC Rules could also be grounds for suspension or disqualification from membership in NERC. Whether or not NERC chooses to use that mechanism will likely depend on the facts and circumstances of the case. • NERC cannot impose penalties for a failure to comply with a data request.

  24. What If a GO Doesn’t Comply? • Possible FERC actions: • All members of NERC (US and Canadian) are bound by their membership agreement with NERC to follow NERC’s Reliability Standards and Rules of Procedure, including section 1600.   • Under section 215 of the Federal Power Act, FERC has jurisdiction over all users, owners, and operators of the bulk power system within the United States. • FERC could treat a failure by a U.S. entity to comply with an approved data request as a violation of a rule adopted under the Federal Power Act using its enforcement mechanisms in Part III of the FPA.

  25. What If a GO Doesn’t Comply? • What about Canada? • Canadian provinces who have signed agreements stating they recognize NERC’s ERO status, will be compliant with the NERC approved standards and Rules of Procedure issued by the NERC Board. • The obligation arises for the Canadian utilities if they are members of NERC. For example, if Canadian Utility “A” is a member of NERC, then it must go by the Rules of Procedure, standards, etc. If Canadian Utility “X” is not a NERC member but its providence recognizes NERC as their ERO, then Utility “X” is not under obligation to follow the rules.

More Related