Project Phase 2.1 BARC. September 1, 2015

Size: px

Start display at page:

Download "Project Phase 2.1 BARC. September 1, 2015"

Darren Cain
5 years ago
Views:

1 Project Phase 2.1 BARC September 1, 2015

2 Antitrust Guidelines NERC Antitrust Guidelines It is NERC s policy and practice to obey the antitrust laws and to avoid all conduct that unreasonably restrains competition. This policy requires the avoidance of any conduct that violates, or that might appear to violate, the antitrust laws. Among other things, the antitrust laws forbid any agreement between or among competitors regarding prices, availability of service, product design, terms of sale, division of markets, allocation of customers or any other activity that unreasonably restrains competition. 2

3 Disclaimers Notice of Open Meeting Participants are reminded that this webinar is public. The access number was widely distributed. Speakers on the call should keep in mind that the listening audience may include members of the press and representatives of various governmental authorities, in addition to the expected participation by industry stakeholders. Presentation Material Wording in this presentation is used for presentation purposes and may not reflect the official posted drafts of requirements or other language 3

4 Standard Drafting Team Member Jerry Rust Chair Tom Siegrist Vice-chair Doug Hils Mike Potishnak Gary Nolan Howard Illian Sandip Sharma Philip Hart Steve Swan Organization Northwest Power Pool Stone Mattheis Xenopoulos and Brew, PC Duke Energy Spriteland Energy representing NPCC Arizona Public Service Energy Mark, Inc. ERCOT AECI MISO 4

5 5

6 BAL b R1 R1. All generation, transmission, and load operating within an Interconnection must be included within the metered boundaries of a Balancing Authority Area. R1.1. Each Generator Operator with generation facilities operating in an Interconnection shall ensure that those generation facilities are included within the metered boundaries of a Balancing Authority Area. R1.2. Each Transmission Operator with transmission facilities operating in an Interconnection shall ensure that those transmission facilities are included within the metered boundaries of a Balancing Authority Area. R1.3. Each Load-Serving Entity with load operating in an Interconnection shall ensure that those loads are included within the metered boundaries of a Balancing Authority Area. Correct application Being retired and moved to FAC R5, R6 and R7 It is appropriate to make this determination at the interconnection stage. 6

7 7

8 BAL R3 R3. Each Balancing Authority shall ensure all of its Balancing Authority Area interconnection points are equipped with common megawatt-hour meters, with readings provided hourly to the control centers of Adjacent Balancing Authorities. Correct application Being retired from BAL and moved to BAL R1 and R8 BAL is being revised to focus on the definition of Reporting ACE and this move reflects that. 8

9 BAL Next Steps, Industry Input The Standard Drafting Team is evaluating the remaining reliability requirements associated with BAL-006-2, Inadvertent Interchange. The Drafting Team intends to circulate a white paper and survey to acquire industry input on their intention. 9

10 10

11 BAL b Disposition of Requirements R1 moved to new definitions of Scheduled Net Interchange & Actual Net Interchange, with new requirements in FAC-001-3, R5, R6 & R7. R2 retired under Paragraph 81. R3 retired as redundant to new R1 & new R8. R4 retired as redundant to new R1 & new R8. R5 retired as redundant to new R1 & new R8. R6 moved to Reporting ACE definition & new R3. R7 retired under Paragraph 81. R8 body moved to R2, 8.1 moved into new R3. 11

12 BAL b Disposition of Requirements R9 moved to Scheduled Net Interchange definition. R10 moved to Scheduled Net Interchange definition. R11 moved to Scheduled Net Interchange definition. R12 moved to new R1. R13 moved to new R1 & new R7. R14 moved to new R5 & new R8. R15 retired as redundant with EOP-008. R16 moved into new R5. R17 partially retired & partially moved to new R4. 12

13 13

14 BAL Change Reliability Focus Title is now focused on Balancing Authority control and not on a "how to accomplish through "Automatic Generation Control. Current BAL-005 was applicable to 4 entities - Proposed BAL- 005 applicable only to a Balancing Authority. Existing Standard includes requirements that are either a "How to" and "Definition" - proposed Standard is Reliability Requirements. Thus reduced the Requirements from 17 to 8. Focused on definition of Reporting ACE and all associated definitions. Removed all associated definitions from Reporting ACE and made them stand alone definitions since they are used throughout NERC. These definitions are associated with the NERC Glossary of Terms. 14

15 BAL New Definitions Elevating definitions within the Reporting ACE definition to stand alone definitions Actual Frequency Actual Net Interchange Scheduled Net Interchange Interchange Meter Error Automatic Time Error Correction Reporting ACE 15

16 Requirement R1 R1. Each Balancing Authority shall ensure that each Tie-Line, Pseudo-Tie, and Dynamic Schedule with an Adjacent Balancing Authority is equipped with a mutually agreed-upon time synchronized common source to determine hourly megawatthour values These values shall be exchanged between Adjacent Balancing Authorities. Rationale Provides for accuracy in the measurements and calculations used in Reporting ACE, hourly inadvertent energy, and Frequency Response measurements. It specifies the need for common metering points for instantaneous and hourly integrated values for the tie line megawatt flow values between Balancing Authority Areas. 16

17 Requirement R2 R2. The Balancing Authority shall use a scan rate of no more than six seconds in acquiring data necessary to calculate Reporting ACE. Rationale Real-time operation of a Balancing Authority requires real-time information. A sufficient scan rate is key to an Operator s trust in real-time information. 17

18 Requirement R3 R3. A Balancing Authority that is unable to calculate Reporting ACE for more than 30-consecutive minutes shall notify its Reliability Coordinator within 45 minutes of the beginning of an inability to calculate Reporting ACE. Rationale The RC is responsible for coordinating the reliability of bulk electric systems for member BA s. When a BA is unable to calculate its ACE for an extended period of time, this information must be communicated to the RC so that the RC has sufficient knowledge of system conditions to assess any unintended reliability consequences that may occur on the wide area. 18

19 Requirement R4 R4. Each Balancing Authority shall use frequency metering equipment for the calculation of Reporting ACE: 4.1. that is available a minimum of 99.95% for each calendar year; and, 4.2. with a minimum accuracy of Hz. Rationale Frequency is the basic measurement for interconnection health, and a critical component for calculating Reporting ACE. Without sufficient available frequency data the BA operator will lack situational awareness and will be unable to make correct decisions when maintaining reliability. 19

20 Requirement R5 R5. The Balancing Authority shall make available to the operator information associated with Reporting ACE including, but not limited to, quality flags indicating missing or invalid data. Rationale System operators utilize Reporting ACE as a primary metric to determine operating actions or instructions. When data inputs into the ACE calculation are incorrect, the operator should be made aware through visual display. 20

21 Requirement R6 R6. Each Balancing Authority s system used to calculate Reporting ACE shall be available a minimum of 99.5% of each calendar year. Rationale Reporting ACE is an essential measurement of the BA s contribution to the reliability of the Interconnection. Since Reporting ACE is a measure of the BA s reliability performance for BAL-001, and BAL-002, it is critical that Reporting ACE be sufficiently available to assure reliability. 21

22 Requirement R7 R7. Each Balancing Authority that is within a multiple Balancing Authority Interconnection shall implement an Operating Process to identify and mitigate errors affecting the scan-rate accuracy of data used in the calculation of Reporting ACE for each Balancing Authority Area. Rationale Without a process to address persistent errors in the ACE calculation, the operator can lose trust in the validity of Reporting ACE resulting in delayed or incorrect decisions regarding the reliability of the bulk electric system. 22

23 Requirement R8 R8. Each Balancing Authority shall agree with an Adjacent Balancing Authority on a common source for respective Tie- Lines, Pseudo-Ties, and Dynamic Schedules and shall implement that common source to provide common information to both Balancing Authorities for the calculation of Reporting ACE. Rationale Provides for accuracy in the measurement and calculations used in Reporting ACE. It specifies the need for common metering points for instantaneous values for the tie-line megawatt flow values between Balancing Authority Areas. Common data source requirements also apply to instantaneous values for pseudo-ties and dynamic schedules, and can extend to more than two Balancing Authorities that participate in allocating shares of a generation resource in supplementary regulation, for example. 23

24 Darrel Richardson Senior Standards Developer

BAL-005-1, BAL & FAC December 18, 2017

BAL-005-1, BAL & FAC December 18, 2017 BAL-005-1, BAL-006-2 & FAC-001-3 December 18, 2017 Antitrust Guidelines NERC Antitrust Guidelines It is NERC s policy and practice to obey the antitrust laws and to avoid all conduct that unreasonably