1 / 47

EMS Users Group Meeting March 13, 2000

NERC Policy 10, draft 3 Proposed Standards and Measurements for the Building Blocks of Interconnection Reliability. EMS Users Group Meeting March 13, 2000. Stephen P. Hoffman, ComEd. What is an IOS?. required to achieve one (or more) reliability objectives:

hawa
Download Presentation

EMS Users Group Meeting March 13, 2000

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. NERC Policy 10, draft 3 Proposed Standards and Measurements for the Building Blocks of Interconnection Reliability EMS Users Group Meeting March 13, 2000 Stephen P. Hoffman, ComEd

  2. What is an IOS? • required to achieve one (or more) reliability objectives: • generation/load balance (continuous and post contingency) • transmission security • emergency preparedness • measurable • higher cost or effort. • separable & distinct • usually provided by generators

  3. Interconnected Operations Services • Balance Supply and Demand • Continuous • Regulation • Load Following • Post Contingency • Frequency Response • Spinning Reserve • Non-Spinning Reserve • Transmission Security • Reactive Power Supply from Generators • Emergency Preparedness • System Black Start Capability Deployment Period Seconds Minutes Hour

  4. Where We’ve Been • IOSWG Report Issued March, 1997 • Decision to convert IOSWG report to Policy 10 by EC/OC April 1997 • IOSITF formed September 1997 • Policy 10 R1 posted April, 1998 • Policy 10 R2 posted December, 1998 • Policy 10 Adopted as White Paper, July 1999 • Policy 10 R3 posted December, 1999

  5. Where We’re Going*** • IOSITF to issue responses to public comments • IOSITF submits draft 3.1 for NERC OC approval and MIC concurrence in March 13-15, 2000 • NERC Board Approval - May 2000 • Assign subcommittee to resolve solutions to 7 non-technical issues in implementation of Policy 10. • Compliance Templates (Metrics) for Policy 10 to be posted summer 2000 • Effective date of Operating Policy 10 and associated compliance templates in their entirety January 2002 *** Future plans subject to change!

  6. Seven non-technical issues 1. Distinction between NERC IOS and FERC Ancillary Services 2. Allow implementation of Policy 10 in a manner that adheres to reliability principles yet accommodates differences in emerging market structures. 3. Prepare to file Operating Policy 10 with FERC. 4. Determine the necessary requirements for independence of the Operating Authority from commercial interests. 5. Determine the applicability of Operating Policy 10, in particular, how the Policy applies to traditional, vertically integrated utilities. 6. Recognize the potential interactions of Policy 10 with Policies 1-9. 7. Coordinate remaining steps to enact Operating Policy 10.

  7. IOS “White Paper” • Approved by the NERC SC in July 1999 • Contains IOS Standards • Defines IOS • Describes obligation of Suppliers and Operating Authorities • Defines IOS Resource certification • Contains IOS Metrics • Describes measurement of delivery • Proposes method for determining adequate delivery

  8. Need for Policy 10 • Lack of standards will result in inconsistent practices, which may undermine reliability. • Assists industry restructuring initiatives: • Corporate realignment or functional unbundling • Divestiture • Operational Unbundling • Evolving markets • Operating Authorities (OA’s) may no longer own nor have inherent “rights” to resources that supply IOS • Nothing is free. Formal agreements/protocols will replace informal arrangements.

  9. Ancillary Services Relative to IOS • Ancillary services: • are driven by regulatory objectives (open, non- discriminatory transmission access, equitable cost recovery) • provide a means to recover costs (i.e. collect revenues) • IOS: • constitute “building blocks” (physical capabilities) needed to support reliability • have always existed, and will always exist under some name • are combined and deployed to provide ancillary services • Accommodate local/regional needs

  10. Operating Authorities’ Obligations • Determine and publish IOS requirements*** • quantity • response times (if applicable) • location (if applicable) • metering & telecommunication requirements • Tx service requirements • process for arrangement, provision and deployment • *** Use inclusive, open process to establish regional/local requirements

  11. Operating Authorities’ Obligations • Arrange for and deploy IOS to meet reliability obligations • Adapt and modify requirements in response to system conditions • Monitor supplier’s performance

  12. Suppliers’ Obligations • Deliver stated capabilities • Certify resources as required • Provide and maintain required metering & telecommunication facilities • Provide information needed to verify performance • Notify Operating Authority of changes in capability

  13. IOS and Ancillary Service Comparison Assembly Process Raw Materials Policy 10 Reliability Control Functions Finished Product Reliable Transmission Service • Transmission • Customers: • Loads • Generators • IOS Suppliers Operating Authority: System Control and Integration Functions IOS Suppliers: Generators and Controllable Loads • Regulation • Load Following • Contingency Reserves • Frequency Response • Spinning • Non-Spinning • Reactive Power Supply from Generation Sources • Unit Black Start • Scheduling Sys. Control & Dispatch • Reactive Supply & VC from GS • Regulation and Frequency Response • Operating Reserve- Spin • Operating Reserve- Supplemental • Energy Imbalance

  14. Power variations • Consists of changes in: • Load • Generation • Interchange

  15. Load, Generation, and Interchange over two days

  16. Transition to definitions • Any of the IOS/Ancillary terms just divide this real variability into different categories. Frequency Response Regulation Load Following Contingency Reserves - Spinning & Supplemental Dispatchable Units Energy market

  17. IOS Quantity relationships • Definitions and associated rules determine how much is needed for each bucket. • Total amount is the same, so rules just shift amounts from one bucket to another. • Examples: • generation scheduling method impacts the amount of Regulation needed. • Capacity bought with rights to dispatch serves any Load Following need. • 16 hour energy schedule increases variability that must be corrected with another resource.

  18. IOS Measurements • Lots of details & possibilities • Is there a single number to “measure” one service? • Some measurement objectives are tied to desired financial terms. • frequency of CR deployment • variability of Regulation schedule • Measure capability shortfalls? • Some measurement objectives measure whether reliability was maintained • did the resource follow the request?

  19. Real Energy Demand - Supply Balance Process

  20. Supplier Control Error • Any dispatch request can be expressed as a variable schedule. • SCE = actual - scheduled • Need to measure SCE average and “variability” • IOS are used to correct for SCE • a resource can both supply, and consume, IOS • schedule respects stated (agreed to) resource capabilities • If a resource is providing several products, the purchasing entities need to agree how to divide the single delivery error.

  21. IOS Resource Measurements Stated Capabilities Observed Capabilities Variable Schedule SCE IOS actual output Schedule parameters indicate “how much” of the stated capabilities were dispatched. Power output, Range, and Ramp rate shortfalls from stated re-set events Regulation - Range, Ramp rate, acceleration Could also indicate delivery error Indicates delivery error Defined once per contract period Defined many times per contract period Useful for financial purposes Useful for reliability and financial purposes

  22. Regulation and Load Following • Stated capabilities • Capacity • Maneuverability • Ramp Rate • Acceleration • Signal Update (Regulation = automatic;Load Following = automatic or manual)

  23. Reg & LF Schedule Pt+1 = Pt + Rt * dt + 1/2 * Jt * dt2 Rt+1 = Rt + Jt * dt Subject to: Pmin < Pt < Pmax Rmin < Rt < Rmax Jmin < Jt < Jmax

  24. Regulation and Load Following as seen by the Supplier Unit Providing Regulation or Load Following Two Units Following Control Instructions From the Operating Authority Max. Load On Control Manual Control Control Setpoint Capacity Maneuverability Energy Automatic Control MW Min. Load On Control Time

  25. Reg & LF Criteria- several options • [StDev{|SCEsampled|}hour] < slimit • Where: SCEsampled = Supplier Control Error at the sampled rate (e.g., every minute). • Meet this limit 90% of the periods in each month • The Operating Authority would select the numerical value of slimit. • Avg[ACE1 * SCE1]hour < SCEACElimit , and • Avg{|SCE1|}hour< SCElimit • Where: SCE1 = one-clock minute average of the SCE.

  26. Contingency Reserves - Spinning and Supplemental • Stated Capabilities • Capacity • Maintain reserved capability at all times • Load reserved capacity within (10-X) minutes • Maneuverability • Responsive to Operating Authority Control Signals • Synchronized (spinning and frequency responsive) • Maintain an Operable Governor (frequency responsive) • Agree on the dispatch time “X”

  27. Contingency Reserve Schedule & Criteria TDCS

  28. Frequency Response • Frequency Response Capabilities • Capacity • Maneuverability • Frequency Response Characteristic

  29. Frequency ResponseSchedule and Criteria • Frequency Response Characteristic • SCE > 0% of the requested MW amount during disturbance recovery.

  30. Bulk Transmission Security(Reactive Power Supply from Generation Sources) • Continuous • Reactive Power Supply to follow voltage schedules • Event Response • Reactive reserves activated by an automatic voltage regulator (AVR) in response to a sudden voltage change. Rated Power Factor MVar Potential Reactive Reserves Reactive Supply for Voltage Schedule Support MW

  31. Reactive Power Supply • Reactive supply capabilities • Reactive Capacity (both leading and lagging) • Maintain reserved reactive capability at all times • Maneuverability • Responsive to Control Signals • Respond to voltage schedule updates • Maintain an operating Automatic Voltage Regulator (AVR) • Criteria • Error is maintained less than an Operating Authority specified band • AVR status is maintained

  32. Black Start • Black Start Capabilities • Capability to start a self-starting unit within a time specified. • Capability of picking up external load within a specified time. • Stated MW capacity and energy capability of the System Black Start Capability unit or units. • Frequency response and voltage control capability. • Certification tests, and actual performance during an event.

  33. IOS Measurement Impacts • Additional control center (EMS?) capabilities will be needed to: • calculate IOS performance, and • track variables tied to IOS financial settlement. • In general, will need to track requests in future, whereas present practice largely tracks actual output • Will need to track intra-hour performance

  34. Certification • Demonstrates ability to perform a service • Inverse relationship between ability to measure and certification difficulty • Important for Reliability & market design • Provides customers assurance they are paying for a real product • De-certification???

  35. Certification - Regulation • Mutually agree on 60 minute test period • Confirm time via phone circuits • Operating Authority • sends raise & lower signals • signals remain unchanged for at least 1 minute • signals respect agreed-upon resource limits • record 1 minute average of schedule and actual output • Certifying entity • performs correlation coefficient test • issues certification

  36. Certification - Load Following • Mutually agree on 60 minute test period • Confirm time via phone circuits • Operating Authority • sends raise & lower signals • signals remain unchanged for the pre-determined minimum time between load changes • sends at least 15 load change requests • signals respect agreed-upon resource limits • record 1 minute average of schedule and actual output • Certifying entity • performs correlation coefficient test • issues certification

  37. Certification - Contingency Reserves • Mutually agree on 8 hour test window • Confirm time window via phone circuits • Operating Authority • selects actual time of test within the 8 hours (surprise test) • request that resource provide its declared amount of Contingency Reserves • record 1 minute average of schedule and actual output • record from 1 minute before notification until 19 minutes past TDCS - X • Certifying entity • ensures that actual is between 100% and Y% of CR amount • issues certification

  38. Certification - Reactive Supply • Based on Planning Standards • IOS Resource • performs AVR tests as described in NERC Planning Standards 2B M4 & 2B M6. • Verifies and maintains its stated reactive capacity, as described in NERC Planning Standards 2B M3. • Certifying entity • verifies completion of all test criteria • issues certification

  39. Certification - Frequency Response • Mutually agree on test period • IOS Resource • record output changes in response to a test frequency signal, or • test that portion of the governor system that can be tested if real power cannot be modified. • Certifying entity • verifies completion of all test criteria • issues certification

  40. Certification - System Black Start Capability • Composed of five parts: • control communication path • primary and alternate voice circuits • Basic Starting Test • Line Energizing Test • Load Carrying Test • Many comments were received that some of the last two tests were too difficult to perform.

  41. Basic Starting Test • Mutually agree on a one week test window • Operating Authority • selects actual time of test within the week (surprise test) • isolates IOS Resource from the power system • request that resource start within the agreed-upon time • ensure that the resource remains frequency and voltage stable for 30 minutes

  42. Line Energizing Test • Isolate sufficient transmission as called for in black start plan • Conduct a Basic Starting Test • monitor frequency & voltage at both ends of line while energized by resource • ensure that the resource remains frequency and voltage stable for 30 minutes

  43. Load Carrying Test • Conduct a Basic Starting Test • Conduct a Line Energizing Test • Pick up sufficient load at the remote end of the line • ensure that the resource and load remains frequency and voltage stable for 30 minutes

  44. Black Start Certification • Certification is issued upon: • control communication performance • test primary and alternate voice circuits • One year Basic Starting Test • Three years Line Energizing Test • Six years Load Carrying Test • Provisions for revocation of certification

  45. Practical exampleContingency Reserves • Three Ancillary Service supply options: • purchase from CA, • purchase from third party, or • self provision • OA(CA) just needs to dispatch resource • Which resources/suppliers form the pool of eligible suppliers for Contingency Reserves? • Which resources/suppliers can actually be dispatched by the reserve sharing system? • Certification helps to answer these questions.

  46. Conclusion • Many of the concepts described in Policy 10 must be implemented, in some manner, as long as the electric industry continues on the path to deregulation

More Related