Agenda

Operating Committee
June 6, 2007  1 p.m. to 5 p.m.

June 7, 2007  8 a.m. to noon

Toronto Marriott Downtown Eaton Centre

525 Bay Street, Toronto, Ontario, Canada

416-597-9200

Item / Leader / Action
  1. Administration
/ Secretary
  1. Quorum

  1. Procedures

  1. Introductions

  1. Agenda
/ Chairman / Approve
  1. Consent Agenda
/ Chairman / Approve
  1. FYI  E-tag 1.8
/ Pat Doran / Discuss
  1. Committee Officer Elections
/ Secretary / Approve
  1. NERC Compliance Filing on Reliability Enhancement Programs
/ Dave Nevius / Discuss
  1. Reliability Criteria and System Limit Concepts
/ Approve
  1. Defining “Adequate Level of Reliability”
/ Chairman / Discuss
  1. Standards BAL-007 through -011
/ Raymond Vice / Discuss
  1. Time Error Monitoring and Correction
/ Terry Bilke
  1. Time Error Monitor
/ Discuss
  1. Time Error and Inadvertent Management Procedures
/ Discuss
  1. Real-time Operations SAR
/ Secretary / Discuss
  1. Demand Response
/ Dave Nevius / Discuss
  1. Reliability Coordination

  1. Reliability Coordination Information System
/ Designate and Permit
  1. Reliability Plan  SaskPower
/ Walter Omoth
Ross Wilkinson / Approve
  1. Reliability Plan  WECC
/ Approve
  1. Reliability Readiness Program
/ Richard Schneider / Discuss
  1. Next Meeting

116-390 Village Boulevard, Princeton, New Jersey 08540-5721

Phone: 609.452.8060 ▪ Fax: 609.452.9550 ▪

Operating Committee Meeting
June 67, 2007

Item 1.Administration

Item 1.aAnnouncement of Quorum

The secretary will announce whether a quorum (two-thirds of the voting members) is in place. NOTE: The committee cannot conduct business without a quorum. Please be prepared to stay for the entire meeting.

Item 1.bProcedures

The NERC Antitrust Compliance Guidelines, Operating Committee charter, and a summary of Parliamentary Procedures are attached for reference. The secretary will answer questions regarding these procedures.

Attachments

  • Antitrust Guidelines
  • Operating Committee Charter
  • Parliamentary Procedures

Item 1.cIntroduction of Members and Guests

The chairman will ask the committee members and guests to introduce themselves.

Attachment

Operating Committee roster

Item 1.dApproval of Agenda

Action

Approve meeting agenda.

Background

The chairman will review the agenda, ask for amendments, and then approval.

Item 2.Consent Agenda

The consent agenda allows the Operating Committee to approve routine items that would not normally need discussion. Any OC member may ask the chairman to remove an item from the consent agenda for formal discussion and action.

Action

Approve the attached document.

Attachment

  • Minutes of March 2122, 2007 Operating Committee meeting.

Item 3.FYI – E-tag 1.8

The Interchange Subcommittee has been working on the E-tag revisions. Subcommittee member Pat Doran from the IESO will be available to answer questions about this project.

Item 4.Committee Officer Elections

Action

Elect committee officers for July 1, 2007June 30, 2009.

The Nominating Subcommittee recommends Gayle Mayo as chair and Sam Holeman as vicechair.

Background and Procedure

Section 4 of the Operating Committee charter explains the terms, conditions, and procedures for selecting the committee’s officers. The Operating Committee uses a nominating subcommittee to provide a slate of candidates for the committee’s consideration. (Secretary’s note: Members of the nominating subcommittee are eligible for nomination.)

  1. The nominating subcommittee will present its candidate for chair.
  2. The committee chairman will then open the floor for additional nominations, and
  3. The committee will then vote on the candidates in the order they were nominated.
  4. The first candidate to garner a majority (the charter states “majority” in this instance) of the votes is elected
  5. If there is only one nominee, that person is automatically elected.

We will repeat this process for the vicechair candidate.

Item 5.NERC Compliance Filing on Reliability Enhancement Programs

Discussion Item

Dave Nevius will lead the discussion of NERC’s draft filing on reliability enhancement programs.

Attachment

“Compliance Filing on Reliability Enhancement Programs,” in response to paragraph 468 of Order No. 672

Background

The Commission requires the electric reliability organization (pursuant to Section 215 of the Federal Power Act) to make a compliance filing no later than one year from the date of certification “proposing reliability enhancement programs that would improve Bulk-Power System reliability, along with a program implementation schedule.”

In this filing (attached), NERC describes a number of programs and initiatives it has implemented or is in the process of implementing that have the objective of improving the reliability of the bulk power system.

We invite the Operating Committee to review this filing and provide comments to Dave Nevius.

Item 6.Reliability Criteria and System Limit Concepts

Action

Approve posting the Reliability Concepts documentfor industry comment. This is a follow-up to the morning’s joint meeting.

Attachments

  • Letter from Al Miller to the Planning Committee and Operating Committee, May 2, 2007
  • We will post the lastest “Reliability Criteria and Operating Limit Concepts” document in the joint OC/PC meeting agenda next week.

Background

We will start with an overview at the joint OC/PC meeting, and then provide time for each committee to discuss the reliability concepts at their own meetings.

These are very important discussions because the concepts and ideas before us will, we hope, guide drafting teams as they prepare revisions to our reliability standards in the future. These concepts are also key to the Federal Energy Regulatory Commission’s judgment of our standards as providing an “adequate level of reliability,” a term the Commission has asked NERC to define (see following agenda item).

The letter from Al Miller (attached) provides the background for the concepts document.

Item 7.Defining “Adequate Level of Reliability”

Discussion Item

This is a follow-up to the joint OC/PC meeting on this topic.

Background

In its January 18, 2007order on compliance filing, FERC directed NERC to file a plan for defining “adequate level of reliability.” The Commission will use that definition when judging the merits of NERC’s reliability standards against the requirements of Section 215 (c) of the Federal Power Act.

At this meeting, the Planning Committee and Operating Committee will discuss a draft of this definition offered by the committee officers, and review the plan for presenting the definition to the NERC Board of Trustees in February 2008 and then filing this definition with the Commission.

The Operating Committee and Planning Committee officers drafted the following definition of “adequate level of reliability” for the committees to discuss at this meeting. (The NERC staff was not involved in their deliberations.)

“An adequate level of bulk power system reliability is required to support the economy, the environment and public health and safety. Adequate reliability is a targeted level of performance, as simulated or in real-time, whereby the bulk power system has been planned with enough reserve, or operated in such manner, so as to supply the anticipated aggregate demand for electricity, including reasonable forecasting error, while operating within equipment and electric system thermal, voltage, and stability limits such that instability, uncontrolled separation, or cascading failures of the bulk power system will not occur as a result of the planned, or unplanned, loss of bulk power system facilities as described in the NERC Transmission Planning (TPL) standards. Adequate reliability also includes the capability to respond to circumstances outside the TPL standards and restore the bulk power system to normal operation to effectively mitigate the impact on public health and safety.”

Discussion Points

As the committees discuss this definition, we need to keep the following points in mind:

  1. Definition of adequate level of reliability in the context of Section 215 (c) of the Federal Power Act:

(c) CERTIFICATION—Following the issuance of a Commission rule under subsection (b)(2), any person may submit an application to the Commission for certification as the Electric Reliability Organization. The Commission may certify 1 such ERO if the Commission determines that such ERO—

(1) has the ability to develop and enforce, subject to subsection (e)(2), reliability standards that provide for an adequate level of reliability of the bulk-power system; and…. (Emphasis added)

The Commission is asking NERC to provide this definition so it can judge our standards according to this provision in the act.

  1. State savings provisions of the Act:

(i) SAVINGS PROVISIONS.—(1) The ERO shall have authority to develop and enforce compliance with reliability standards for only the bulk-power system.

(2) This section does not authorize the ERO or the Commission to order the construction of additional generation or transmission capacity or to set and enforce compliance with standards for adequacy or safety of electric facilities or services.

(3) Nothing in this section shall be construed to preempt any authority of any State to take action to ensure the safety, adequacy, and reliability of electric service within that State, as long as such action is not inconsistent with any reliability standard,…. (Emphasis added)

The savings provisions mean that NERC cannot compel any entity to construct facilities. In other words, we cannot write standards that require specific levels of generation reserves or ensure that all customer demand is served.

  1. Applicability of the definition.

The definition must be applicable to all NERC reliability standards. When we submit a standard to the board and Commission for approval, we will need to make sure that standard supports the definition of adequate level of reliability. This includes standards on planning, operations planning, and real-time operations. The Standards Committee will revise the standards process by adding a reference to this definition.

Procedure

NERC, through the PC and OC, committed to 1) develop a “straw man” definition, 2) seek industry-wide comment,3) request Commission staff’s direct participation in these technical discussions, and 4) otherwise coordinate with Commission staff at periodic intervals throughout this process to obtain input and gauge conformance to Commission expectations. Key PC/OC milestones:

  • December 31, 2007: After industry review and comment, propose a definition to the NERC Board of Trustees.
  • February 2008 Board of Trustees meeting: Present a recommendation for board approval. The definition, as approved, will be subsequently filed with the Commission and applicable regulatory authorities in Canada.

Item 8.Standards – BAL-007 through -011

Discussion Item

Raymond Vice, a member of the Balance Resources and Demand Standard Drafting Team, will solicit the Operating Committee’s thoughts and suggestions on how to proceed with these standards.

Attachments

  • Ballot ResultsBAL-007 through -011
  • Revised SAR, “Reliability-Based Control”
  • Letter – Gerry Adamski to Regional Managers – Extending the Field Test, May 17, 2007

Summary

The ballot body did not approve these standards, and the Board of Trustees would like the Operating Committee to provide its insight on the outcome of the ballot and possible next steps for this standard.

The drafting team has fully explained the concept of these standards to the Operating Committee over the past three years, focusing on the Balancing Area ACE Limit (BAAL) concepts, and then on the results of the field test.Mr. Vice, who is a member of the standard drafting team, will review the ballot results and discuss the new SAR, which the Standards Committee has already approved. The Standards Committee is also forming a new standard drafting team.

Background

Proposed standards BAL-007 through -011 were not approved (the ballot results are attached). At its May 2 meeting, the NERC Board of Trustees discussed the results of the ballot, and some board members asked for additional insight into the reasons the standard was not approved. What were the reliability arguments? Would the standard have been approved if more utilities had participated in the field trial? (See list at right.)

The standard drafting team regularly visited the Operating Committee over the past few years as the team developed and tested the standard. The field trial showed that interconnection frequency had not deteriorated, though it did exhibit frequency excursions around the time of the on-to-off peak periods that were attributed to the end of the 16-hour on-peak energy sales.

Just before the first ballot of the standard last fall, the Operating Committee provided its opinion on the merits of the standard (see following page). While the committee generally supported and recommended the standard be approved, it also pointed out two concerns: 1) The retirement of the Disturbance Control Standard at the same time the new standards became effective, and 2) the effects of the new Balancing Area ACE Limits on transmission line flow.(Several OC members suggested keeping the DCS for 18 months, or until the new BAAL standard proved to successfully deal with ACE recovery after large generation failures.)

The standard was not approved, and several ballot body members cited the retirement of the DCS as the reason for their negative vote. Others noted their concern about the effects of the BAAL standard on line flows.

The drafting team revised the implementation of the BAAL standard to keep the DCS in place, and submitted the standard for a second ballot this spring.

Analysis of Ballot Results

We can draw at least two conclusions from the ballot results:

  1. Most of the negative ballots were from ballot body members in WECC, NPCC, and FRCC. Most of them expressed their concern about the potential for transmission line overloads caused by the wider BAAL limits when the balancing authority was helping interconnection frequency, and
  1. The 14 field test participants represented about one-half of the NERC-wide load, but only a small percentage of the 214 ballot body members.

Therefore, even though the field test results have not linked transmission line overloads to the BAAL standard, sufficient ballot body members remained skeptical that this link would not materialize.

What’s Next

The Balance Resources and Demand standard drafting team has proposed a new SAR (also attached) that adds transmission line reliability to the BAAL standards. The drafting team is also actively soliciting other utilities to participate in the field trial so they can see first-hand whether the BAAL standards adversely affect transmission system loading. The Standards Committee is forming a new drafting team.

Topics to Discuss

In addition to the proposed SAR, the Operating Committee should consider these questions:

  1. Does the revised SAR address the reliability issues that the Operating Committee discussed last fall?
  2. What role does field testing playwhen balloting a standard?
  3. Does the OC have specific comments it would like to send the drafting team?

Excerpt from September 1314, 2006 OC Meeting Minutes: Opinion on BAL-007 through -011 Balance Resources and Demand

Discussion

Standard drafting team member Doug Hils presented the latest results of the field trial in which many utilities in the Eastern Interconnection have been participating.This evoked considerable discussion within the committee. Most of the comments focused on the planned retirement of standard BAL-002, also known as the Disturbance Control Standard (DCS), within 18 months of the implementation of new Balancing Area ACE Limits (BAAL) standards. Retiring the DCS effectively extends the recovery time for generation loss to 30 minutes because the BAAL standards do not distinguish generation loss from other events that result in a large area control error.

Some committee members were concerned that allowing balancing authorities more leeway in controlling their ACE when the Interconnection frequency error was low could result in more unscheduled interchange, and increased line loading. Mr. Hils noted that, so far, the field trial has not turned up this problem.

Opinion

“The Operating Committee believes BAL-007 through -011 should be approved. Eastern Interconnection frequency performance has been consistent with previous years or improved since the field trials began. The standard considers Interconnection frequency error and requires balancing authorities to take action as the frequency approaches specified high or low limits.

“The committee believes the Disturbance Control Standard should remain in effect and be eliminated only after satisfactory field trials.”

Approved by show of hands: 23 in favor and 4 opposed.

Item 9.Time Error Monitoring and Correction

Item 9.aTime Error Monitor

Discussion Item

The OC needs to discuss its expectations of the interconnection time error monitors, considering they perform this task voluntarily. Resources Subcommittee Chairman Terry Bilke will lead this discussion.

Attachments

  • Memo – Roger Harszy to Dave Whiteley
  • Letter Dave Whiteley to Roger Harszy, “Standard BAL-004, ‘Time Error Correction,’” May 11, 2007
  • NAESB Time Error Correction Business Practice

Background


Mr. Harszy’s memo requests a waiver for the Midwest Independent System Operator (MISO) from BAL-004, requirement 2, considering that MISO performs the time monitoring tasks voluntarily:

As Mr. Whiteley explained in his response, NERC cannot waive compliance with its standards. We also explained that NERC would not assess a penalty for non-compliance with requirement 2, and asked MISO to continue serving voluntarily as the interconnection’s time monitor until the Operating Committee resolved the issue.