nerc highlights and minute…translate this page%pdf-1.6 %âãÏÓ 11087 0 obj >stream xÚ¤zm Ü...

116-390 Village Blvd. Princeton, NJ 08540

609.452.8060 | www.nerc.com

Agenda Operating Committee March 12, 2008 | 1–5 p.m. March 13, 2008 | 8 a.m.–noon The Westin City Center 650 North Pearl Street Dallas, Texas 75201 214-979-9000

Item Leader Action

1. Administration Secretary

a. Quorum

b. Procedures

c. Introduction of Members and Guests

d. Agenda Chairman Approve

2. Consent Agenda Chairman Approve

a. Minutes of December 12−13, 2007 meeting

b. State/Municipal Utility Representative

3. FYI

a. NERC Board of Trustees Vice Chairman

b. Operating Committee Work Plan Vice Chairman

c. NERC Board Technology Committee Stan Johnson

d. Operating Committee Appointments Chairman

i. OC/PC Subgroup Nomination Form Chairman

ii. Reliability Fundamentals Working Group Chairman

iii. Integration of Variable Generation Task Force Warren Frost

iv. Reliability Metrics Working Group Jason Shaver

continue…

Operating Committee Meeting Agenda March 12–13, 2008 2

4. Operating Committee Charter Revisions Chairman Approve. Follow-up

from the joint meeting.

5. Critical Infrastructure Protection Stan Johnson

a. NERC Situation Awareness Tool Status Report

b. North American SynchroPhasor Initiative Follow-up from joint meeting

c. National Response Framework Information

6. Reliability Readiness Program

a. Reliability Readiness Program Work Plan Kevin Conway Discussion.

b. Role of the Operating Committee Chairman Discussion

7. Functional Model Working Group Steve Crutchfield Follow-up from joint meeting

8. Organization Registration and Certification Lucius Burris Discussion

9. Reliability-based Control Standard Drafting Team Doug Hils Discussion

10. Training John Taylor Endorse Personnel Subcommittee’s training model

11. Education and Certification Programs Martin Sidor Discussion

12. Events Analysis Bob Cummings Discussion

13. NERC/NAESB Coordination Andy Rodriquez Discussion

a. TLR Procedure

b. ATC/AFC and CBM/TRM Revisions

c. Balancing Authority Controls

14. Real-time Tools Best Practices Task Force Jack Kerr Approve

15. Interchange Subcommittee John Ciza Discussion

a. TSIN Registry

b. Eastern Interconnection Interchange Tool

16. Resources Subcommittee Terry Bilke

a. Time Monitor Reference Document Approve

b. Access to Performance Data Information

c. FERC Request for Access to Inadvertent Data Discussion

17. Operating Reliability Subcommittee

a. Flowgate Administration Reference Document David Zwergel Approve

18. Next meeting – June 4–5, 2008 (Tentatively Toronto, Ontario)

Secretary


Item 1. Administration

Item 1.a Announcement 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.b Procedures 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.c Introduction of Members and Guests The chairman will ask the committee members and guests to introduce themselves.

Attachment Operating Committee roster

Item 1.d Approval of Agenda Action

Approve meeting agenda.

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


609.452.8060 | www.nerc.com

1

Antitrust Compliance Guidelines

I. General 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. It is the responsibility of every NERC participant and employee who may in any way affect NERC’s compliance with the antitrust laws to carry out this commitment. Antitrust laws are complex and subject to court interpretation that can vary over time and from one court to another. The purpose of these guidelines is to alert NERC participants and employees to potential antitrust problems and to set forth policies to be followed with respect to activities that may involve antitrust considerations. In some instances, the NERC policy contained in these guidelines is stricter than the applicable antitrust laws. Any NERC participant or employee who is uncertain about the legal ramifications of a particular course of conduct or who has doubts or concerns about whether NERC’s antitrust compliance policy is implicated in any situation should consult NERC’s General Counsel immediately.

II. Prohibited Activities Participants in NERC activities (including those of its committees and subgroups) should refrain from the following when acting in their capacity as participants in NERC activities (e.g., at NERC meetings, conference calls and in informal discussions):

• Discussions involving pricing information, especially margin (profit) and internal cost information and participants’ expectations as to their future prices or internal costs.

• Discussions of a participant’s marketing strategies.

• Discussions regarding how customers and geographical areas are to be divided among competitors.

Attachment 1b

Antitrust Compliance Guidelines 2

• Discussions concerning the exclusion of competitors from markets.

• Discussions concerning boycotting or group refusals to deal with competitors, vendors or suppliers.

• Any other matters that do not clearly fall within these guidelines should be reviewed with NERC’s General Counsel before being discussed.

III. Activities That Are Permitted From time to time decisions or actions of NERC (including those of its committees and subgroups) may have a negative impact on particular entities and thus in that sense adversely impact competition. Decisions and actions by NERC (including its committees and subgroups) should only be undertaken for the purpose of promoting and maintaining the reliability and adequacy of the bulk power system. If you do not have a legitimate purpose consistent with this objective for discussing a matter, please refrain from discussing the matter during NERC meetings and in other NERC-related communications. You should also ensure that NERC procedures, including those set forth in NERC’s Certificate of Incorporation, Bylaws, and Rules of Procedure are followed in conducting NERC business. In addition, all discussions in NERC meetings and other NERC-related communications should be within the scope of the mandate for or assignment to the particular NERC committee or subgroup, as well as within the scope of the published agenda for the meeting. No decisions should be made nor any actions taken in NERC activities for the purpose of giving an industry participant or group of participants a competitive advantage over other participants. In particular, decisions with respect to setting, revising, or assessing compliance with NERC reliability standards should not be influenced by anti-competitive motivations. Subject to the foregoing restrictions, participants in NERC activities may discuss:

• Reliability matters relating to the bulk power system, including operation and planning matters such as establishing or revising reliability standards, special operating procedures, operating transfer capabilities, and plans for new facilities.

• Matters relating to the impact of reliability standards for the bulk power system on electricity markets, and the impact of electricity market operations on the reliability of the bulk power system.

• Proposed filings or other communications with state or federal regulatory authorities or other governmental entities.

• Matters relating to the internal governance, management and operation of NERC, such as nominations for vacant committee positions, budgeting and assessments, and employment matters; and procedural matters such as planning and scheduling meetings.

Operating Committee Charter

Approved by the Board of Trustees: May 2, 2007

Operating Committee Charter 1

Attachment 1b

Table of Contents

Purpose...................................................................................................................4 Section 1. Functions ............................................................................................4

1. General forum. ........................................................................................... 4 2. Advice and recommendations........................................................................ 4 3. Support to the Reliability Readiness Program. ................................................. 4 4. Support for other programs. ......................................................................... 5 5. Approve the following documents and procedures:........................................... 5 6. Opinions and interpretations. ........................................................................ 5

Section 2. Membership ........................................................................................5 1. Goals ........................................................................................................ 5 2. Expectations............................................................................................... 5 3. Representation. .......................................................................................... 6 4. Selection.................................................................................................... 6 5. Terms. ...................................................................................................... 7 6. Resignations, Vacancies, and Nonparticipation................................................. 7 7. Proxies. ..................................................................................................... 7

Section 3. Meetings .............................................................................................7 1. Quorum. .................................................................................................... 7 2. Voting. ...................................................................................................... 7 3. Antitrust Guidelines. .................................................................................... 7 4. Open Meetings............................................................................................ 7 5. Confidential Sessions. .................................................................................. 8

Section 4. Officers ...............................................................................................8 1. Terms and conditions................................................................................... 8 2. Selection.................................................................................................... 8

Section 5. Subcommittees ...................................................................................9 1. Appointing subgroups. ................................................................................. 9 2. Nominating subcommittee. ........................................................................... 9

Section 6. Executive Committee...........................................................................9 1. Authorization.............................................................................................. 9 2. Membership. .............................................................................................. 9 3. Election Process. ......................................................................................... 9 4. Terms. ...................................................................................................... 9

Appendix 1 – Committee Members ........................................................................10


Appendix 2 – Meeting Procedures .........................................................................12 Section 1. Voting Procedures for Motions ..........................................................12 Section 2. Minutes .............................................................................................12 Section 3. Minority Opinions ..............................................................................12 Section 4. Personal Statements .........................................................................12


Purpose

The Operating Committee’s mission is to provide the ERO (stakeholders, board of trustees, and staff) with the collective and diverse opinions from the experts in interconnected systems operation to help the industry arrive at informed decisions.

Section 1. Functions

1. General forum.� Provides a general forum for aggregating ideas and interests regarding the operations of the interconnected bulk power systems in North America.

2. Advice and recommendations.� Provides NERC (stakeholders, Board of Trustees, and staff) with advice, recommendations, and the collective and diverse opinions on matters related to interconnected operations to help the industry arrive at informed decisions.

3. Support to the Reliability Readiness Program. �Provide technical support, guidance, and advice to NERC’s Reliability Readiness Program (see also NERC Rules of Procedure, Section 700, “Reliability Readiness Evaluation and Improvement program, and Appendix 7, “Reliability Readiness Evaluation and Improvement Program Procedure.”)

a. General

• Develop criteria for measuring program success, and review the program against those criteria.

• Recommend actions to other NERC programs (standards, compliance, assessments, training, etc.) based on lessons learned and trends from readiness evaluations and examples of excellence

b. Readiness Evaluations

• Review readiness evaluations for trends and recommend new or different types of evaluations or changes in processes or metrics, including:

o Readiness criteria

o Guidelines for reporting and disclosure, and

o Guidelines for consistency and relevancy of evaluations:

Between comparable entities, and

Through time

• Provide guidance to the readiness evaluations process

c. Examples of Excellence

• Review and discuss the examples of excellence for lessons learned

• Support information exchange within the industry on examples of excellence


4. Support for other programs.� Provide technical advice and subject matter expert support to each of the NERC program areas, and serve as a forum to integrate the outputs of each NERC program area.

a. Standards.

• Provide opinions. Provide the committee’s majority and minority opinions to the industry on NERC’s standards as those standards are drafted, posted for ballot, and presented to the board of trustees for implementation.

• Help prioritize standards. Help the Standards Committee prioritize those standards that are in the drafting queue.

b. Compliance. Review quarterly and annual compliance reports for trends and suggest new or different types of compliance monitoring based on a technical review of system performance trends or as a result of compliance investigations.

c. Reliability assessments and performance analysis. Review reliability assessments and recommend topics that need additional investigation. These include:

• Future adequacy

• Event analysis

• Benchmarking

d. Personnel training and certification. Recommend to the Personnel Certification Governance Committee the types of operating personnel that should be certified.

e. Situation awareness. Review and recommend control, monitoring, and visualization tools for system operators.

5. Approve the following documents and procedures:

a. Reliability Coordinator plans.

b. Market operations plans that are a part of the Reliability Coordinator plans.

c. Field test procedures, and the commencement and end of field tests to make sure those tests are “safe and effective.”

d. NERC Reliability Functional Model.

6. Opinions and interpretations.� Provide technical opinions at the industry stakeholders’ request on operating reliability concepts, philosophies, and standards.

Section 2. Membership

1. Goals� The Operating Committee provides for balanced decision making by bringing together a wide diversity of opinions from industry experts with outstanding technical knowledge and experience in the area of interconnected systems operation reliability.

� Operating Committee voting members are expected to: 2. Expectations.

a. Bring subject matter expertise to the Operating Committee


b. Be responsible for operating reliability within their organization

c. Attend and participate in all Operating Committee meetings

d. Express their own opinions, as well as the opinions of the sector they represent, at committee meetings

e. Discuss and debate interests rather than positions

f. Complete committee assignments

3. Representation.� See Appendix 1, “Committee Members”

a. Committee members may, but need not be, NERC members.

b. To ensure adequate Canadian representation, the membership to the committee may be increased so that the number of Canadian voting members is equal to the percentage of the net energy for load (NEL) of Canada to the total NEL of the United States and Canada, times the total number of voting members on the committee, rounded to the next whole number.

4. Selection.� NERC sector members will annually elect voting committee members in committee sectors corresponding to their NERC sector under an election process that is open, inclusive, and fair. The selection process will be completed in time for the secretary to send the committee membership list to the board for its approval at the board’s August meeting so that new committee members may be seated at the September meeting.

a. The Regional Reliability Organizations may, at their option, appoint their voting committee members.

b. Un-nominated voting member positions will remain vacant until the next annual election, or until the committee secretary receives a nomination for that position, whichever occurs first.

c. Members may not represent more than one committee sector.

d. A particular organization may not have more than one member on the committee.

e. If additional Canadian members are added, no more than one additional Canadian voting member shall be selected from a sector unless this limitation precludes the addition of the number of additional Canadian voting representatives required by Section 3.3.b. In this case, no more than two additional Canadian voting members may be selected from the same sector.

f. The secretary will monitor the committee selection process to insure that membership specifications are met.


5. Terms.� Members’ terms are staggered, with one-half of the members' terms expiring each year. Except for the initial selection, a member’s term is two years and will commence on the first September meeting following the member’s selection pursuant to Section 2.4 and continue until the September meeting two years later. Members may be re-elected for subsequent terms.

6. Resignations, Vacancies, and Nonparticipation

a. Members who resign will be replaced for the time remaining in the member’s term. Members will be replaced pursuant to Section 2.4, officers will be replaced pursuant to Section 4, and executive committee members will be replaced pursuant to Section 6.

b. The secretary will submit the new member’s name to the board for approval at the board’s next regular meeting.

c. The committee may approve the new member on an interim basis at the committee’s next meeting.

d. The committee chair will contact any member who has missed two consecutive meetings (even if the member has sent a proxy) to 1) seek a commitment to actively participate or 2) ask the member to resign from the committee.

7. Proxies.� A member of the committee may give a proxy only to a person who is a member registered in the same sector. Each voting member of the committee shall have one vote on any matter coming before the committee that requires a vote.

Section 3. Meetings

See Appendix 2, “Meeting Procedures” Unless stated otherwise, the Operating Committee will follow Roberts Rules of Order, Newly Revised.

1. Quorum.� The quorum necessary for the transaction of business (i.e., formal actions) at meetings of the Committee is two-thirds of the voting members currently on the committee roster (i.e., does not count vacancies). The committee may engage in discussions without a quorum present.

2. Voting.� Actions by members of the Committee shall be approved upon receipt of the affirmative vote of 2/3 of the voting members of the Committee present and voting, in person or by proxy, at any meeting at which a quorum is present. The chairman and vice-chairman may vote. Additional voting guidelines are in Appendix 2.

3. Antitrust Guidelines.� All persons attending or otherwise participating in the Committee meeting shall act in accordance with NERC’s Antitrust Compliance Guidelines at all times during the meeting. A copy of the NERC antitrust statement shall be included with each meeting agenda.

4. Open Meetings.� NERC committee meetings shall be open to the public, except as noted below under Confidential Sessions. Although meetings are open, only voting members may offer and act on motions.


5. Confidential Sessions.� The chair of a committee may limit attendance at a meeting or portion of a meeting, based on confidentiality of the information to be disclosed at the meeting. Such limitations should be applied sparingly and on a non-discriminatory basis as needed to protect information that is sensitive to one or more parties. A preference, where possible, is to avoid the disclosure of sensitive or confidential information so that meetings may remain open at all times. Confidentiality agreements may also be applied as necessary to protect sensitive information.

Section 4. Officers

1. Terms and conditions.� At its June meeting the Committee shall select a chairman and vice chairman from among its voting members by majority vote of the members of the Committee to serve during the period July 1 through June 30 of the following two years, provided that:

a. The newly selected chairman and vice chairman shall not be representatives of the same sector.

b. The chairman and vice chairman, upon assuming such positions, shall cease to act as representatives of the sectors that elected them as representatives to the Committee and shall thereafter be responsible for acting in the best interests of the members as a whole.

c. The secretary will submit the elected officers to the chairman of the board for approval.

2. Selection.� The Committee selects officers using the following process. The chairman is selected first, followed by the vice-chairman.

1. The nominating subcommittee will present its recommended candidate.

2. The chairman opens the floor for nominations.

3. After hearing no further nominations, the chairman closes the nominating process.

4. The Committee will then vote on the candidate recommended by the nominating subcommittee, followed by the candidates nominated from the floor in the order in which they were nominated. The first candidate to garner the majority of the Committee’s votes will be selected.

5. If the Committee nominates one person, that person is automatically selected as the next chairman.

6. If the Committee nominates two or more persons, and none receive a majority of the Committee’s votes, then the secretary will distribute paper ballots for the members to mark their preference.

7. The secretary will collect the ballots. If the Committee nominates three or more candidates, then the winner will be selected using the Instant Runoff Process. (Explained in Roberts Rules of Order)


Section 5. Subcommittees

1. Appointing subgroups.� The Operating Committee may appoint technical subcommittees, task forces, and working groups as needed.

2. Nominating subcommittee.� At the first regular meeting following the selection of a new committee chairman, the chairman will nominate, for the committee’s approval, a slate of five committee members from different sectors to serve as a nominating subcommittee. The subcommittee will:

a. Recommend candidates for the committee’s chairman and vice chairman, and

b. Recommend candidates for the executive committee’s four “at large” members.

Section 6. Executive Committee

1. Authorization.� The executive committee is authorized to act between regular meetings of its parent committee. However, the executive committees may not reverse its parent committee’s decisions.

2. Membership.� The Committee will elect an executive committee of six members, all from different sectors, as follows:

• Chairman

• Vice-chairman

• Four at-large members from different sectors nominated by the nominating subcommittee.

3. Election Process.

• The Nominating Subcommittee will present its slate of candidates for the four “at large” members.

• The chairman opens the floor for additional nominations.

• If the Committee members nominate additional candidates, then the secretary will distribute paper ballots for the members to list their top four candidates.

• The four candidates who receive the most votes will be elected, provided that no two candidates may be from the same sector.

4. Terms.� The executive committee will be replaced every two years, with the chair and vice chair replaced at a June meeting and the at-large members replaced at a September meeting..


Appendix 1 – Committee Members

Definition Members Name

Voting Members

1. Investor-owned utility This sector includes any investor-owned entity with substantial business interest in ownership and/or operation in any of the asset categories of generation, transmission, or distribution. This sector also includes organizations that represent the interests of such entities.

2

2. State/municipal utility This sector includes any entity owned by or subject to the governmental authority of a state or municipality, that is engaged in the generation, delivery, and/or sale of electric power to end-use customers primarily within the political boundaries of the state or municipality; and any entity, whose members are municipalities, formed under state law for the purpose of generating, transmitting, or purchasing electricity for sale at wholesale to their members. This sector also includes organizations that represent the interests of such entities.

2

3. Cooperative utility This sector includes any non-governmental entity that is incorporated under the laws of the state in which it operates, is owned by and provides electric service to end-use customers at cost, and is governed by a board of directors that is elected by the membership of the entity; and any non-governmental entity owned by and which provides generation and/or transmission service to such entities. This sector also includes organizations that represent the interests of such entities.

2

4. Federal or provincial utility/Federal Power Marketing Administration

This sector includes any U.S. federal, Canadian provincial, or Mexican entity that owns and/or operates electric facilities in any of the asset categories of generation, transmission, or distribution; or that functions as a power marketer or power marketing administrator. This sector also includes organizations that represent the interests of such entities. One member will be a U.S. federal entity and one will be a Canadian provincial entity.

2

5. Transmission dependent utility This sector includes any entity with a regulatory, contractual, or other legal obligation to serve wholesale aggregators or customers or end-use customers and that depends primarily on the transmission systems of third parties to provide this service. This sector also includes organizations that represent the interests of such entities.

2

6. Merchant electricity generator This sector includes any entity that owns or operates an electricity generating facility that is not included in an investor-owned utility’s rate base and that does not otherwise fall within any of sectors (i) through (v). This sector includes but is not limited to cogenerators, small power producers, and all other non-utility electricity producers such as exempt wholesale generators who sell electricity at wholesale. This sector also includes organizations that represent the interests of such entities.

2

7. Electricity marketer This sector includes any entity that is engaged in the activity of buying and selling of wholesale electric power in North America on a physical or financial basis. This sector also includes organizations that represent the interests of such entities.

2


Definition Members Name

Voting Members

8. Large end-use electricity customer

This sector includes any entity in North America with at least one service delivery taken at 50 kV or higher (radial supply or facilities dedicated to serve customers) that is not purchased for resale; and any single end-use customer with an average aggregated service load (not purchased for resale) of at least 50,000 MWh annually, excluding cogeneration or other back feed to the serving utility. This sector also includes organizations that represent the interests of such entities.

2

9. Small end-use electricity customer

This sector includes any person or entity within North America that takes service below 50 kV; and any single end-use customer with an average aggregated service load (not purchased for resale) of less than 50,000 MWh annually, excluding cogeneration or other back feed to the serving utility. This sector also includes organizations (including state consumer advocates) that represent the interests of such entities.

2

10. Independent system operator/regional transmission organization

This sector includes any entity authorized by the Commission to function as an independent transmission system operator, a regional transmission organization, or a similar organization; comparable entities in Canada and Mexico; and the Electric Reliability Council of Texas or its successor. This sector also includes organizations that represent the interests of such entities.

2

11. Regional reliability organization

This sector includes any regional reliability organization as defined in Article I, Section 1, of the Bylaws of the corporation.

2

12. State government (See Government representatives below) 2

Officers Chair and Vice Chair 2

Total Voting Members 26

Non-Voting Members1

0 This sector includes any federal, state, or provincial government department or agency in North America having a regulatory and/or policy interest in wholesale electricity. Entities with regulatory oversight over the Corporation or any regional entity, including U.S., Canadian, and Mexican federal agencies and any provincial entity in Canada having statutory oversight over the Corporation or a regional entity with respect to the approval and/or enforcement of reliability standards, may be nonvoting members of this sector.

Government representatives

United States federal government 2

Canadian federal government 1

Provincial government 1

Regional reliability organizations The remaining RROs that are not RRO sector voting members. 6

Secretary The committee secretary will be seated at the committee table 1

Subcommittee Chairs The chairs of the subcommittees will be seated at the committee table.

1 Industry associations and organizations and other government agencies in the U.S. and Canada may attend meetings as non-voting observers.


Appendix 2 – Meeting Procedures

Section 1. Voting Procedures for Motions

1. The default procedure is a voice vote.

2. If the chairman believes the voice vote is not conclusive, he may call for a show of hands.

3. The chairman will not specifically ask those who are abstaining to identify themselves when voting by voice or a show of hands.

4. The committee may conduct a roll-call vote in those situations that need a record of each member's vote.

• The committee must approve conducting a roll call vote for the motion.

• The secretary will call each member's name.

• Members answer "yes," "no," or "present" if they wish to abstain from voting.

Section 2. Minutes

1. Meeting minutes are a record of what the committee did, not what its members said.

2. Minutes should list discussion points where appropriate, but should usually not attribute comments to individuals. It is acceptable to cite the chairman's directions, summaries, and assignments.

3. Do not list the person who seconds a motion.

4. Do not record (or even ask for) abstentions.

Section 3. Minority Opinions

All Committees members are afforded the opportunity to provide alternative views on an issue. The meeting minutes will provide an exhibit to record minority opinions. The chairman shall report both the majority and any minority views in presenting results to the Board of Trustees.

Section 4. Personal Statements

The minutes will also provide an exhibit to record personal statements.


Parliamentary Procedures Based on Robert’s Rules of Order, Newly Revised, 10th Edition, plus “Organization and Procedures Manual for the NERC Standing Committees”

Motions Unless noted otherwise, all procedures require a “second” to enable discussion.

When you want to… Procedure Debatable Comments Raise an issue for discussion

Move Yes The main action that begins a debate.

Revise a Motion currently under discussion

Amend Yes Takes precedence over discussion of main motion. Motions to amend an amendment are allowed, but not any further. The amendment must be germane to the main motion, and can not reverse the intent of the main motion.

Reconsider a Motion already approved

Reconsider Yes Allowed only by member who voted on the prevailing side of the original motion.

End debate Call for the Question or End Debate

Yes If the Chair senses that the committee is ready to vote, he may say “if there are no objections, we will now vote on the Motion.” Otherwise, this motion is debatable and subject to 2/3 majority approval.

Record each member’s vote on a Motion

Request a Roll Call Vote

No Takes precedence over main motion. No debate allowed, but the members must approve by 2/3 majority.

Postpone discussion until later in the meeting

Lay on the Table Yes Takes precedence over main motion. Used only to postpone discussion until later in the meeting.

Postpone discussion until a future date

Postpone until Yes Takes precedence over main motion. Debatable only regarding the date (and time) at which to bring the Motion back for further discussion.

Remove the motion for any further consideration

Postpone indefinitely

Yes Takes precedence over main motion. Debate can extend to the discussion of the main motion. If approved, it effectively “kills” the motion. Useful for disposing of a badly chosen motion that can not be adopted or rejected without undesirable consequences.

Request a review of procedure

Point of order No Second not required. The Chair or secretary shall review the parliamentary procedure used during the discussion of the Motion.

Notes on Motions Seconds. A Motion must have a second to ensure that at least two members wish to discuss the issue. The “seconder” is not recorded in the minutes. Neither are motions that do not receive a second.

Announcement by the Chair. The Chair should announce the Motion before debate begins. This ensures that the wording is understood by the membership. Once the Motion is announced and seconded, the Committee “owns” the motion, and must deal with it according to parliamentary procedure.

Attachment 1b

Voting Voting Method When Used How Recorded in Minutes Unanimous Consent When the Chair senses that the Committee

is substantially in agreement, and the Motion needed little or no debate. No actual vote is taken.

The minutes show “by unanimous consent.”

Vote by Voice The standard practice. The minutes show Approved or Not Approved (or Failed).

Vote by Show of Hands (tally) To record the number of votes on each side when an issue has engendered substantial debate or appears to be divisive. Also used when a Voice Vote is inconclusive. (The Chair should ask for a Vote by Show of Hands when requested by a member).

The minutes show both vote totals, and then Approved or Not Approved (or Failed).

Vote by Roll Call To record each member’s vote. Each member is called upon by the Secretary,, and the member indicates either “Yes,” “No,” or “Present” if abstaining.

The minutes will include the list of members, how each voted or abstained, and the vote totals. Those members for which a “Yes,” “No,” or “Present” is not shown are considered absent for the vote.

Notes on Voting (Recommendations from DMB, not necessarily Mr. Robert)

Abstentions. When a member abstains, he is not voting on the Motion, and his abstention is not counted in determining the results of the vote. The Chair should not ask for a tally of those who abstained.

Determining the results. The results of the vote (other than Unanimous Consent) are determined by dividing the votes in favor by the total votes cast. Abstentions are not counted in the vote and shall not be assumed to be on either side.

“Unanimous Approval.” Can only be determined by a Roll Call vote because the other methods do not determine whether every member attending the meeting was actually present when the vote was taken, or whether there were abstentions.

Majorities. Robert’s Rules use a simple majority (one more than half) as the default for most motions. NERC uses 2/3 majority for all motions.

Operating Committee Roster March 12–13, 2008 Meeting

Chairman Gayle Mayo

Executive Vice President and Chief Operating Officer

Indiana Municipal Power Agency 11610 N. College Avenue Carmel, Indiana 46032

(317) 575-3867 (317) 575-3372 Fx [email protected]

Vice Chairman J.S. Holeman

Manager, System Operating Center

Duke Energy 526 South Church Street EC02B Charlotte, North Carolina 28202

(704) 382-0011 (704) 382-6938 Fx jsholeman@ duke-energy.com

Secretary Larry J. Kezele

Manager of Reliability Support Services

North American Electric Reliability Corporation 116-390 Village Boulevard Princeton, New Jersey 08540-5721

(609) 452-8060 (609) 452-9550 Fx larry.kezele@ nerc.net

Investor Owned Utility

C. Martin Mennes Vice President, Transmission & Substations

Florida Power & Light Co. 9200 West Flagler Street Room 6301 Miami, Florida 33174

(305) 552-4138 (305) 228-5116 Fx marty_mennes@ fpl.com

Investor Owned Utility

Thomas R. Stuchlik Executive Director Transmission Operations

Westar Energy 818 South Kansas Ave P.O. Box 889 Topeka, Kansas 66601

(785) 575-6046 (785) 575-1798 Fx Tom.Stuchlik@ westarenergy.com

State/Municipal To Be Named

State/Municipal Blaine R. Dinwiddie

Division Manager Omaha Public Power District 4325 Jones Plaza Omaha, Nebraska 68105

(402) 552-5970 (402) 552-5679 Fx bdinwiddie@ oppd.com

Cooperative Mark E. Fidrych

Reliability Compliance Administrator

Tri-State G & T Association Inc. 1100 W. 116th Avenue Loveland, Colorado 80234

(303) 452-6111 (303) 548-5287 Fx mfidrych@ tristategt.org

Cooperative Alan H. Wilkinson

Operations Reliability Administrator

Southwest Transmission Cooperative, Inc. P.O. Box 2195 Benson, Arizona 85602

(520) 586-5315 (520) 586-5279 Fx awilkinson@ swtransco.coop

Federal/Provincial Julien Gagnon

Manager, System Control Scheduling

Hydro-Quebec TransEnergie Complexe Desjardins Est 9ieme C.P. 10000 Montreal, Quebec J3V 5Z2

(514) 289-2211 ext.4372 (514) 289-2969 Fx gagnon.julien@ hydro.qc.ca

Federal/Provincial Tom Irvine

Manager, Grid Operations Hydro One Networks, Inc. 49 Sarjeant Drive Barrie, Ontario L4R-5G6

(705) 792-3004 (705) 792-3012 Fx tom.irvine@ hydroone.com

Federal/Provincial Lorne Midford

Manager, System Performance Dept.

Manitoba Hydro P.O. Box 815 Winnipeg, Manitoba R3C 2P4

(204) 487-5426 (204) 487-5496 Fx lemidford@ hydro.mb.ca

Attachment 1c

2

Federal/Provincial Darren Buck

Power Systems Operations Manager

Western Area Power Administration 114 Parkshore Drive Folsom, California 95630


Transmission Dependent Utility

Dennis Florom Manager, Energy and Environmental Operations

Lincoln Electric System 1040 O St. P.O.Box 80869 Lincoln, Nebraska 68501-0869


Transmission Dependent Utility

Raymond Phillips Manager System Operations

Alabama Municipal Electric Authority 804 South Perry Street Montgomery, Alabama 36103


Merchant Electricity Generator

Ralph Honeycutt, PE Director, Transmission Analysis and Operations

SUEZ Energy Marketing NA, Inc. 1990 Post Oak Boulevard Suite 1900 Houston, Texas 77056

(713) 636-1282 (713) 636-1800 Fx ralph.honeycutt@ suezenergyna.com

Merchant Electricity Generator

James T. Thompson Vice President

Constellation Energy 500 Dallas St. Suite 3015 Houston, Texas 77002

(713) 332-2901 (443) 213-3674 Fx jt.thompson@ constellation.com

Electricity Marketer Matt E. Greek

Vice President - Gas Plant Operations

Reliant 1000 Main Street, #1662 Houston, Texas 77002

(713) 497-7560 (713) 497-9280 Fx mgreek@ reliant.com

Electricity Marketer Stephen McCullough

Director - Transmission and Operations

Exelon Corporation 300 Exelon Way Kennett Square, Pennsylvania 19348

(610) 765-6710 (610) 765-7710 Fx stephen.mccullough@ exeloncorp.com

Large End-use Electricity Customer

John A. Anderson President and CEO

Electricity Consumers Resource Council 1333 H Street, N.W. 8th Floor, West Tower Washington, D.C. 20005

(202) 682-1390 (202) 289-6370 Fx janderson@ elcon.org

Large End-use Electricity Customer

Thomas Gianneschi Regulatory Affairs

Alcoa, Inc. 900 South Gay Street 12th Floor Knoxville, Tennessee 37902

(865) 594-4988 (865) 291-8507 Fx tom.gianneschi@ alcoa.com

Small End-use Electricity Customer

To Be Named

ISO/RTO Tom Bowe

Executive Director Reliability Integration

PJM Interconnection, L.L.C. 955 Jefferson Avenue Valley Forge Corporate Center Norristown, Pennsylvania 19403-2497


ISO/RTO Warren Frost

Vice President Operations & Reliability

Alberta Electric System Operator 2500, 330 - 5 Avenue SW Calgary, Alberta T2P 0L4

(403) 539-2515 (403) 539-2612 Fx warren.frost@ aeso.ca

3

ISO/RTO James G. McIntosh Director of Grid Operations

California ISO 151 Blue Ravine Road Folsom, California 95630

(916) 351-2101 (916) 351-2453 Fx jmcintosh@ caiso.com

RRO-ERCOT Kent Saathoff

Vice President of System Operations

Electric Reliability Council of Texas, Inc. 2705 West Lake Drive Taylor, Texas 76574

(512) 248-6560 (512) 248-6560 Fx ksaathoff@ ercot.com

RRO-FRCC Ronald L. Donahey

Managing Director, Grid Operations

Tampa Electric Co. P.O. Box 111 Tampa, Florida 33601-0111

(813) 623-5120 (813) 630-6299 Fx rldonahey@ tecoenergy.com

RRO-MRO Lawrence R. Larson

Manager, Delivery Operations Otter Tail Power Company 215 South Cascade Street Fergus Falls, Minnesota 56538-0496

(218) 739-8572 (218) 739-8625 Fx llarson@ otpco.com

RRO-NPCC Derek R. Cowbourne

Chief Operating Officer Independent Electricity System Operator Station A Box 4474 Toronto, Ontario M5W 4E5

(905) 855-6211 (905) 403-6932 Fx derek.cowbourne@ ieso.ca

RRO-RFC Jacquie Smith

320 Springside Dr. Suite 300 Akron, Ohio 44333

(330) 247-3067 (303) 456-3648 Fx jacquie.smith@ rfirst.org

RRO-SERC Jim Griffith

Manager of System Operations Southern Company Services, Inc. P.O. Box 2625 Birmingham, Alabama 35202-2625

(205) 257-6892 (205) 257-6663 Fx jsgriffi@ southernco.com

RRO-SPP Peter Kuebeck

Manager Transmission Operations

Oklahoma Gas and Electric Co. 321 N. Harvey Oklahoma City, Oklahoma 73101


RRO-WECC John R. Powell

System Operations Manager Platte River Power Authority 2000 East Horsetooth Rd. Fort Collins, Colorado 80525


State Government Steve F. Ghadiri

Transmission Systems Engineer California Electricity Oversight Board 770 "L" Street Suite 1250 Sacramento, California 95814

(916) 322-8690 (916) 322-8591 Fx sghadiri@ eob.ca.gov

State Government Howard A. Tarler

Chief, Bulk Transmission Systems Operations and Planning

New York State Department of Public Service 3 Empire State Plaza Albany, New York 12223

(518) 486-2483 (518) 473-2420 Fx howard_tarler@ dps.state.ny.us

U.S. Federal (Non-voting)

To Be Named

U.S. Federal (Non-voting)

To Be Named

Canadian Federal (Non-voting)

To Be Named

4

Provincial (Non-voting)

Mark Lamothe Specialiste en Regulation Economique

Quebec Energy Board 800 Place Victoria 2nd Floor, CP 001 Montreal, Quebec H4Z 1A2

(514) 873-2452 (514) 873-3037 Fx mark.lamothe@ regie-energie.qc.ca


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.

Item 2.a Minutes of December 12–13, 2007 Meeting Action Approve the attached document

Attachment Minutes of December 12−13, 2007 Operating Committee meeting

Item 2.b State/Municipal Utility Representative The secretary will announce the ballot results to elect a representative for the State/Municipal Utility sector. The elected representative will fill the unexpired term of Mr. Kevin Conway, who resigned.

Action Approve

Operating Committee Meeting December 12−13, 2007

Minutes

Convene

A regular meeting of the NERC Operating Committee (OC) was held on December 12−13, 2007, in Orlando, Florida. The meeting notice, agenda, and attendance list are affixed as Exhibits A, B, and C, respectively; and individual statements and minority opinions as Exhibits D and E, respectively. The meeting presentations are posted in a separate file at http://www.nerc.com/~filez/ocmin.html.

Operating Committee chair Gayle Mayo convened the meeting at 1 p.m.

Secretary Don Benjamin announced that a quorum was present.

Antitrust Compliance

The secretary referred the committee to the NERC Antitrust Compliance Guidelines included in the meeting agenda.

FYI

The secretary reviewed the recently approved NERC Strategic Plan for 2008–2013.

Chair Mayo highlighted the October 23, 2007 Board of Trustees’ Technology Committee meeting, and its guidelines for supporting NERC system operator “tools.” (Refer to the Operating Committee’s discussion in its September 12–13, 2007 meeting minutes, “Operator ‘Tools’ for Balancing Authorities.”)

Meeting Highlights The Operating Committee:

1. Approved Version 1.0.0 of the Reliability Concepts document. This is an “open source” document that will be continuously updated.

2. Tasked the Operating Reliability Subcommittee with performing a “gap” analysis on all standards that refer to SOL and IROL, and prepare the necessary standards authorization requests.

3. Approved the definition of “Adequate Level of Reliability.”

4. Tasked the Resources Subcommittee with preparing a concepts “chapter” on load-generating balancing.

5. Approved the scope of the “Integration of Variable Generation Task Force.” Will ask the PC to consider focusing on wind generation.

6. Reviewed the developing Situation Awareness Tool.

7. Approved process for approving NERC operating tools, along with a resolution explaining these tools are for system operators, and that the OC “…will work with federal, state, and provincial agencies to find the means to provide them the information they need.”

8. Approved the committee’s three-year work plan.

9. Approved SaskPower’s reliability coordination plan.

10. Reviewed the scope of NERC’s new Metrics Working Group and three proposed metrics indices.

Minutes of September 12–13, 2007 Operating Committee meeting

After minor revision (see screenshot at right from page 6, “August 4, 2007 Disturbance”), the committee approved the minutes of its September 12–13, 2007 meeting.

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

Phone: 609.452.8060 ▪ Fax: 609.452.9550 ▪ www.nerc.com

Attachment 2a

http://www.nerc.com/

Operating Committee Meeting December 12-13, 2007

Reliability Readiness Program

Chair Mayo reported that she and vice chair Sam Holeman will discuss with the NERC staff the Operating Committee’s expectations as the program committee.

Situation Awareness Tool

Stan Johnson and Scott Mix (managers of Situation Awareness and Infrastructure Security) explained the purpose of the Situation Awareness Tool.

The committee’s lengthy discussion included:

• The intended recipients of this information (Regions, reliability coordinators, NERC staff).

• Federal, provincial, and state regulatory agencies’ interest in this information.

o Concern that regulatory agency requests will interfere with system operator responsibilities, or

o Lead to compliance assumptions.

• Data link problems that need to be solved.

Chair Mayo asked Mr. Johnson to keep the Operating Committee informed about the progress of this information system.

Definition of “Adequate Level of Reliability”

Chair Mayo introduced this item and asked the committee to discuss the draft definition with the goal of approving it at this meeting. She noted a change in the introduction section (as shown at right) that the OC and Planning Committee (PC) officers were contemplating, regarding whether the definition would be filed with the Federal Energy Regulatory Commission.

Larry Larson moved to approve the definition.

The committee’s discussion centered on whether, or how, NERC would “file” the definition with FERC (e.g., formal filing or information filing). Chair Mayo explained that the FERC staff did not expect NERC to formally file the definition as a separate document, but rather as part of NERC’s work plan that includes performance metrics and standards development.

2


The committee then approved Mr. Larson’s motion.

Tom Gianneschi and John Anderson submitted a minority opinion, included in Exhibit E. The NERC staff will submit the definition along with minority opinions, all public comments, and OC and PC officers’ (and NERC staff’s) responses to those comments, to the Board of Trustees.

Reliability Concepts Document

Operating Limits Definition Task Force chair Al Miller presented a brief recap of the document at the joint meeting with the Planning Committee that morning. He reported the Planning Committee approved the document, and he was now asking the OC to do the same.

Derek Cowbourne moved to approve Version 1.0.0 of the Reliability Concepts Document, approve the scope of the Reliability Criteria Working Group, and dismiss the Operating Limits Definition Task Force.

In the discussion that followed, vice chair Sam Holeman thanked the task force for a job well done. He said the document sets an important foundation and approach that will help both operators and planners.

The committee then approved Mr. Cowbourne’s motion.

Chair Mayo presented Mr. Miller with a plaque expressing the Operating Committee’s appreciation for his contributions to the industry’s understanding of reliability concepts.

(Secretary’s note: the draft posted had several mechanical errors left over from a previous draft. The corrected document is posted as Version 1.0.1.)

“Gap” Analysis

Chair Mayo asked the Operating Reliability Subcommittee to review all the NERC standards that reference system operating limit and interconnection reliability operating limit, and, based on the Reliability Concepts Document, prepare a report on which standards need to be revised, added, or removed. Operations

& PlanningReliabilityConcepts

OperatingLimits

TrainingModeling ProtectionCIP Balancing

Reliability ConceptsDocuments Structure

The chapters are related to eachother as well as the ReliabilityConcepts document. Blue boxesdenote chapters that have beendrafted. Others are possibilities.

PowerSupply

Chapters

Additional Chapters

Chair Mayo asked the Resources Subcommittee to write a comprehensive chapter on load-generation balancing. That chapter would be instrumental in developing the concepts and recommendations on integrating variable generation (see next item).

Integrating Variable

3


Generation Task Force

The committee then discussed forming, jointly with the Planning Committee, a task force to study and recommend actions for reliably integrating variable generation into the interconnection. (The concepts chapter on load-generation balancing would be a very important pre- or co-requisite.)

Derek Cowbourne moved to approve the scope, but limit its focus to wind generation (and change the task force’s name accordingly).

In its discussion of the motion, the committee agreed it was a critical subject, and asked Jim McIntosh and Warren Frost to present their report on wind generation experiences in California and Alberta to the NERC Board of Trustees. That report, which Messrs. McIntosh and Frost presented at the joint OC/PC/CIPC meeting, described the challenges of operating generation whose availability may have no relationship to normal daily demand patterns.

The committee decided to table Mr. Cowbourne’s motion until the next day so we could determine the Planning Committee’s reaction to limiting the working group’s scope to wind generation.

The following day, the secretary returned Mr. Cowbourne’s motion to the table. The Planning Committee’s decision was not available, so the OC approved the motion by unanimous consent, and asked the Executive Committee to bring the OC’s recommended scope changes to the Planning Committee officers.

Midwest ISO Balancing Authority Plan

David Zwergel explained MISO’s plan for becoming a balancing authority area for its “footprint.” (Presentation 1.) (See presentation excerpts at right).

James Uhrin provided an update on MISO’s certification as a balancing authority. (Presentation 2.) The committee asked Messrs. Zwergel and Uhrin several questions regarding the balancing authority tasks, the role MISO would play, and the role its members would continue.

(Secretary’s note: this was not an action item because the OC had already approved MISO’s balancing authority implementation plan at an earlier meeting.)

Training Model

The secretary reviewed the Personnel Subcommittee’s draft framework for a training model that utilities could use to help them implement effective training programs for their personnel.

4


John Taylor, who chairs the Personnel Subcommittee, was not able to attend this meeting, and the committee asked that he provide more detail about this model at the next OC meeting.

Events Analysis

Bob Cummings reviewed four topics (Presentation 3.) :

1. September 18 MRO separation

2. NERC Alerts (see graphic at right)

3. Lessons Learned − Emerging and Ongoing Trends

4. Events Under Analysis and Review

Operating Committee Work Plan

The secretary reviewed the proposed Operating Committee work plan for 2008–2011, and the committee made several revisions during the review. The final version is affixed as Exhibit F.

Access Permission for NERC Operator Tools

Operating Reliability Subcommittee chair Jim Castle reviewed the protocols the subcommittee was recommending the Operating Committee approve. These protocols explain how NERC approves access to a number of online system operator tools:

1. Central Repository for Security Events (CRC)

2. Reliability Coordinator Information System (RCIS)

3. Factors Viewer (NFV)

4. System Data Exchange (SDX)

5. Interchange Distribution Calculator (IDC)

6. Tag Dump Reader

7. Interregional Security Network (ISN) Data Files

8. NERCNet

9. Book of Flowgates

10. Resource Adequacy

The Operating Committee discussed at length the provision for providing regulatory authorities access to these operator tools, focusing in particular on the RCIS and Resource Adequacy (Balancing) tools:

5


“Upon the advice of the RCWG and ORS, Federal and State agencies (e.g., FERC, DHS) may be granted RCIS read-only access as approved by the Operating Committee.”

Some committee members believed it was more efficient to directly provide regulatory authorities the information they were seeking. Others noted that any utility or RTO/ISO was free to provide whatever information it wanted to regulators. And others expressed concern that these tools were intended for system operators’ use, and the information they convey was not appropriate to provide to regulators.

Derek Cowbourne then moved the following resolution:

WHEREAS the NERC Reliability Tools are for operating the system,

THEREFORE, the Operating Committee resolves to work with federal, state, and provincial agencies to find the means to provide them the information they need.

(Secretary’s note: This final wording was the result of the committee’s on-screen editing after the initial resolution was offered.)

Mr. Cowbourne’s motion included adding this resolution to the introduction section of the protocols document, and removing the references to granting access to federal and state agencies. The marked-up and final documents are affixed as Exhibits G and H.

SaskPower Reliability Coordination Plan

Jim Castle recapped the steps for approving the SaskPower reliability coordination plan.

Larry Larson then moved that “the OC accepts the ORS assessment of the SaskPower Pre-Operational Review and grants final approval of the SaskPower Reliability Plan including access to the associated NERC reliability tools necessary to perform Reliability Coordinator Functions beginning January 3, 2008.”

The committee approved Mr. Larson’s motion. SaskPower’s reliability coordination plan will be posted on NERC’s Web site at http://www.nerc.com/~filez/reliaplans.html.

Metrics

Jessica Bian, NERC’s manager of benchmarking, reviewed the three key indices that Ms. Bian described at the joint OC/PC/CIPC meeting (see slide at right).

The committee discussed each of these, bringing the following points to the table:

• Whether the indices were proposals from the NERC staff, or had already been decided. (They are proposed.)

• The need for direct OC involvement in the new

6

http://www.nerc.com/%7Efilez/reliaplans.html


Metrics Working Group the PC was forming.

• Whether the OC and PC would determine an “Adequate Level of Reliability” based on these metrics.

The OC generally agreed that it wanted to be represented on the metrics group the Planning Committee was establishing, and possibly change the scope of the working group to report to both the OC and PC. The committee asked to review the final scope before it is approved.

Procedure for Approving Guidelines

This was a follow-up to the straw man presented at the joint OC/PC/CIPC meeting. The OC and PC executive committees will work together on these guidelines.

Adjourn

There being no further business before the Operating Committee, chair Mayo adjourned the meeting on Thursday, December 14, 2008 at 11:30 p.m.

7

Angie Nicastro

From: Rocio Wong [[email protected]]Sent: Monday, October 22, 2007 12:26 PMTo: [email protected]; [email protected]; [email protected]; [email protected]: [email protected]: ANNOUNCEMENT: North American Electric Reliability Corporation (NERC) - Standing Committees' Meetings

December 11-14, 2007

Page 1 of 1

12/17/2007

This email was sent to the nercroster List Serve --- TO: CRITICAL INFRASTRUCTURE PROTECTION COMMITTEE

OPERATING COMMITTEE PLANNING COMMITTEE STANDARDS COMMITTEE REGIONAL ENTITY MANAGEMENT GROUP NERC ROSTER

Dear Members: I have attached the December 11-14, 2007 Critical Infrastructure Protection, Operating, Planning, and Standards Committees’ meetings announcement and Web site registration link. You can register online at the following Web sites: http://www.nerc.com/committees/ http://www.nerc.net/meetings/ You MUST respond by NOVEMBER 15, 2007. Only online registrations will be accepted. Please let me know if you have any questions regarding the registration process. Sincerely, Rocio Wong Meeting Planner North American Electric Reliability Corporation (NERC) 116-390 Village Blvd. Princeton, NJ 08540 Phone: 609-452-8060 Fax: 609-452-9550 [email protected] --- You are currently subscribed to nercroster as: [email protected] To unsubscribe send a blank email to [email protected]

Exhibit A

August 7, 2007

TO: CRITICAL INFRASTRUCTURE PROTECTION COMMITTEE NERC ROSTER Ladies and Gentlemen: I have listed the September 27– 28, 2007 Critical Infrastructure Protection Committee meeting logistics and registration link below. The meeting will be held at the Cervantes Convention Center at America’s Center, 701 Convention Plaza, St. Louis, MO. Hotel accommodations have been set at the Drury Inn & Suites Convention Center (not at Union St.), 711 North Broadway, St. Louis MO (phone: 314-231-8100).

You can click on the “registration” link to register for the meetings or you can register online at the following Web sites: http://www.nerc.com/committees/ or http://www.nerc.net/meetings/

You MUST respond by September 12, 2006. EVERYONE must register online.

Date & Time Group Staff City Registration

Link 9/27/2007: 8:00 AM - 5:00 PM

9/28/2007: 8:00 AM - 12:00 PM

CIPC Stan Johnson St. Louis Register

Accommodation logistics: • Room rate: $85.99 single/double occupancy. • Room block: Nights of September 26 – 27, 2007. • Hotel cut-off date: September 12, 2007 — NOTE: After the cut-off date, the hotel will release this block of rooms and only

accept reservations on a space available basis at the prevailing room rate. • Check-in: 4 p.m., Check-out: noon • Lambert International Airport: Is about 20 to 30 minutes from the hotel. • Trans-express shuttle service to the hotel is about $16 one way and approximately $26 round trip. • Dress code: Business casual.

When making your hotel reservation, please be sure to mention the “NERC/North American Electric Reliability Corporation” meeting to get the preferred rate and to ensure your reservation is credited to the NERC room block. The hotel may charge NERC a penalty if the total rooms blocked for this event are not picked up. Also, if you use a travel agency for your travel plans, please make sure the agency mentions NERC.

Please let me know if you have any questions regarding the registration process. Sincerely,

Rocio Wong Rocio Wong Meeting Planner

Rocio E. Wong Meeting Planner

http://www.nerc.com/committees/

http://www.nerc.net/meetings/

http://www.nerc.net/meetingregistrations/default.aspx?meetingdate=9/27/2007&meetingtype=CIPC

Agenda Operating Committee

December 12, 2007 ⎯ 1 to 5 p.m. December 13, 2007 ⎯ 8 a.m. to noon

Buena Vista Palace Hotel

1900 Buena Vista Drive, Lake Buena Vista, Florida Item Leader Action

1. Administration Secretary

a. Quorum

b. Procedures

c. New Members

d. Introductions

e. Agenda Chairman Approve

2. Consent Agenda Chairman Approve

a. Minutes of September 12−13, 2007 meeting

3. FYI

a. NERC Strategic Plan Secretary

b. NERC Board Technology Committee Chairman

4. Reliability Readiness Program Jim Castle Discuss

5. NERC Situation Awareness Tool Scott Mix Follow-up from joint meeting.

6. Definition of Adequate Level of Reliability Chairman Approve. Follow-up from joint meeting.

7. Reliability Concepts Document and Related “Chapters”

a. Reliability Concepts Document Al Miller Approve Version 1.0.0.

b. Standards “Gap” Analysis for SOL an IROL

Chairman Assign to Operating Reliability Subcommittee.

c. Chapter: Load-Generation Balancing Assign to Resources Subcommittee.

d. Chapter: Variable Generation Assign to joint OC/PC task force.

8. Training John Taylor Endorse Personnel Subcommittee’s training model.

9. Events Analysis Bob Cummings Discuss

10. Operating Committee Work Plan Chairman Approve

11. Time Error Monitor Procedures Approve developing Time Monitor Procedure.

12. Metrics Jessica Bian Discuss

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

Phone: 609.452.8060 ▪ Fax: 609.452.9550 ▪ www.nerc.com

Continued…

Exhibit B

Operating Committee Meeting December 12−13, 2007

Item Leader Action

13. Operator “Tools” Access Jim Castle Approve

14. Reliability Plans

a. SaskPower Pre-Operations Evaluation Jim Castle Approve

b. MISO Balancing Authority Plan David Zwergel and Jim Uhrin

Discuss

15. Next meetings Secretary

ATTENDEES Operating Committee Meeting

December 12–13, 2007 OFFICERS

Chairman Gayle Mayo Vice Chairman Sam Holeman Secretary and Staff Coordinator Donald M. Benjamin

MEMBERS

VOTING MEMBERS Investor-Owned Marty Mennes Utility State/Municipal Blaine Dinwiddle Cooperative Alan Wilkinson Mark Fidrych Federal/Provincial Tom Irvine Lorne Midford Transmission Raymond Phillips Dependent Utility Merchant Electricity Ralph Honeycutt Generator Electricity Marketer Tom Bradish (for Matt Greek) Stephen McCullough Large End-Use John Anderson Customer Thomas Gianneschi ISO/RTO Tom Bowe Warren Frost Jim McIntosh

VOTING MEMBERS (contd) ERCOT Ken Saathoff FRCC Ron Donahey MRO Larry Larson NPCC Derek Cowbourne RFC Jacqueline Smith SERC Jim Griffith SPP Peter Kuebeck WECC John Powell State Government Howard Tarler

Exhibit C

ATTENDEES — Operating Committee Meeting (cont) December 12–13, 2007

2.

REGIONAL ENTITY MANAGEMENT GROUP Edward Schwerdt (NPCC) Louise McCarren (WECC) NERC STAFF Bob Cummings Larry Kezele Tom Vandervort Ronald Niebo Angie Nicastro Julia Souder Stanley Johnson Scott Mix Jessica Bian OC SUBGROUP CHAIRMEN OR VICE CHAIRMEN Terry Bilke Chair, Resources Subcommittee James Castle Chair, Operating Reliability Subcommittee David Zwergel Chair, Reliability Coordinator Working Group Al Miller Chair, Operating Limit Definitions Task Force GUESTS Bill Addington Intellibind Sheldon Berg Midwest Reliability Organization Jack Bernhardsen Pacific Northwest Security Coordinator, Inc Steve Beuning Xcel Energy Peter Brandien ISO New England Larry Bugh ReliabilityFirst Corporation Mary Cain Federal Energy Regulatory Commission Roman Carter Southern Company John Ciza Southern Company Generation Julian Cox National Grid James Dalrymple Tennessee Valley Authority Terri Eaton Xcel Energy Ron Falsetti IESO Will Franklin Entergy Elizabeth Howell ITC Holdings Tony Jankowski We Energies Joe Krupar (retired) Florida Municipal Power Authority Pedro Modia Florida Power & Light Allen Mosher American Public Power Association Jerry Mosier Northeast Power Coordinating Council Steve Rueckert Western Electricity Coordinating Council Jason Shaver American Transmission Eric Senkowicz Florida Reliability Coordinating Council John Troha SERC Relliability Corporation Jim Uhrin ReliabilityFirst Corporation Dale Zahn Intellibind

Individual Statements Operating Committee Meeting December 12-13, 2007

There were none.

Exhibit D

Minority Opinions Operating Committee Meeting December 12–13, 2007

MEMORANDUM

Date: December 17, 2007

To: Don Benjamin, OC Secretary

From: Tom Gianneschi, Alcoa, Large End-use Representative OC John Anderson, ELCON, Large End-use Representative OC

Subject: Cost Effectiveness in the Definition of “Adequate Level of Reliability”

The definition of “Adequate Level of Reliability” was discussed and approved at the December 2007 meetings of NERC’s Planning Committee and Operating Committee (PC & OC). Representatives of both Small End-use and Large End-use Consumers expressed significant concern both in comments filed on the definition when it was posted as well as at the December meetings of the PC and the OC that the definition does not mention any measure of “cost effectiveness.” Consumers believe strongly that this omission should be corrected before the definition receives its final approval.

Consumers emphasize that the very broad, high-level definition includes terms such as: “acceptable limits”, “performs acceptably”, is “protected from unacceptable damage”, and includes “reasonably expected unscheduled outages.” Obviously, there are multiple ways to comply with these characteristics, some more expensive than others. End-use consumers, those that pay the bills, expect that the procedures actually implemented achieve the adequate level of reliability at least cost.

Thus, the end-use consumer representatives of the PC and OC strongly recommend that the introductory sentence to the definition of Adequate Level of Reliability be amended to state:

“The Bulk-Power System (“System”) will achieve an adequate level of reliability when it implements the following characteristics at least cost:”

Additional language must be added to the definition to further define the extent of cost control considerations the standards process should include. We will supply this language in our Minority Opinion to be filed in January.

Exhibit E

Operating Committee Three-Year Plan 2008 − 2010

Task When Description

1. Concepts Documents and Procedures

a. Reliability Concepts Document

By January 30, 2008 Core team. Core team in place with process for maintaining the document.

b. Integration of variable generation

2008-09 Resources Subcommittee. Write concepts chapter on balancing load and generation.

OC and PC. Develop joint team to develop concepts chapter on variable generation.

c. Training Concepts July 2008 Personnel Subcommittee. Develop personnel training model for the industry.

d. Voltage and Reactive concepts

2008-09 Operating Committee. Consider developing concepts chapters on voltage and reactive power.

e. Time Monitor Procedures

March 2008 Resources Subcommittee and RCWG. Develop committee procedure for selecting and monitoring Time Monitors. (See Dec 12-13, 2007 OC agenda for details)

2. SOL and IROL By May 1, 2008 Operating Reliability Subcommittee and Reliability Coordinator Working Group. Perform “gap” analysis and develop SARs for all standards that currently deal with SOL and IROL.

Includes analysis of IROL reports.

The ORS should bring philosophical issues to the Operating Committee at each OC meeting until this project is complete.


December (?) 2008 Operating Reliability Subcommittee. Continue to work with the OC and NERC staff to improve the effectiveness of this program.

4. Operator Tools 2008 Operating Committee. Foster new technology solutions and will lead the development of new reliability tools where new technology and tools are necessary to improve reliability. (NERC Strategic Plan).

5. Metrics 2008-10 Operating Committee. Participate with the Planning Committee in developing performance metrics.

6. Event analysis Every meeting NERC staff. Report from Bob Cummings on conclusions and recommendations from latest studies.

7. Other Items

a. BPS v. BES Why are these different? (Reliability Concepts document uses “Interconnection” and explains why.)

b. OC Role in Standards development

Establish more effective relationship between OC and standards work plan.

Exhibit F

Vetting Criteria for Granting Access to NERC Reliability Tools

Introduction At the direction of the Operating Committee, the Operating Reliability Subcommittee developed the following criteria for use by NERC staff in granting access to NERC web-based reliability tools. These reliability tools are used by reliability coordinators, balancing authorities, transmission operators, and, in some instances, purchasing-selling entities, and are under the purview of the Operating Reliability Subcommittee, the Resources Subcommittee, or one of their respective working groups or task forces.

Providing Information to Federal, State, or Provincial Agencies Whereas the NERC reliability tools are for operating the system,

The OC resolves to work with federal, state, or provincial agencies to find the means to provide them with the information they need.

Dispute Resolutions Disputes related to a request for access to one of the NERC reliability tools (e.g., denial of access to CRC) should be directed to [email protected]. If the dispute cannot be resolved by NERC staff, NERC staff shall consult with the Operating Committee Executive Committee.

Contents Introduction .....................................................................................................................1 Contents..........................................................................................................................1 NERC Reliability Tools........................................................................................................2 Central Repository for Security Events (CRC) ........................................................................2 Reliability Coordinator Information System (RCIS) .................................................................3 Factors Viewer (NFV).........................................................................................................4 System Data Exchange (SDX).............................................................................................4 Interchange Distribution Calculator (IDC) .............................................................................5 Tag Dump Reader .............................................................................................................6 Interregional Security Network (ISN) Data Files.....................................................................7 NERCNet .........................................................................................................................8 Book of Flowgates (BoF) ....................................................................................................8 Resource Adequacy ...........................................................................................................9

For Operating Committee Approval

Formatted: Heading 2

Formatted: Heading 2

Deleted:

Deleted: subcommittee

Deleted: having oversight responsibility of the reliability tool in dispute

Exhibit G


Approved by the Operating Reliability Subcommittee – November 14, 2007

- 2 -

NERC Reliability Tools The NERC reliability tools addressed in this procedure include:






6. Tag Dump Reader


8. NERCNet



A description of the function and purpose of each reliability tool is provided followed by the vetting criteria for granting access.

Central Repository for Security Events (CRC) Description — CRC is a limited-access website that provides transmission system curtailment information to transmission customers in accordance with FERC Order 605, at the request of the Market Interface Committee in August 2000. Many transmission providers use the site to comply with Order 605, with references or direct links to the CRC site from their OASIS sites.

Approval Criteria — CRC access is granted to requester’s from:

1. Entities listed in Transmission Services Information Network (TSIN), (e.g., purchasing-selling entities, balancing authorities, and reliability coordinators)

2. Federal and State agencies (e.g., FERC, DHS)

3. Other organizations, provided the organization signs the NERC Policy on Availability of Secured Electricity Sector Data

CRC Oversight — Under the general guidance of the IDC Working Group, NERC staff approves CRC access requests in accordance with the above criteria.

CRC Registration Link — https://www.nerc.net/applicationbroker/

CRC Website Address — https://crc.nerc.net/



- 3 -

Reliability Coordinator Information System (RCIS) Description — The RCIS is a real-time web-based messaging system that connects all reliability coordinators and many balancing authorities and transmission operators. RCIS allows reliability coordinators to share emergency alerts and other real-time operational information. RCIS also displays information related to ACE, frequency, and generator and transmission outages.

Approval Criteria

1. RCIS access is granted to employees of Recipient Parties1 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for RCIS access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. Reliability coordinators shall be granted RCIS read/write access 4. Balancing authorities and transmission operators shall be granted

RCIS read-only access

5. Regional Entities shall be granted RCIS read-only access

6.

RCIS Access Control — The Reliability Coordinator Working Group will annually review the list of RCIS users.

RCIS Oversight — Under the general guidance of the Reliability Coordinator Working Group, NERC staff approves RCIS access requests in accordance with the above criteria.

RCIS Registration Link — https://www.nerc.net/applicationbroker/

RCIS Website Address — https://rcis.nerc.net/

1 Recipient Party. A signatory to this ORD Agreement that (i) is directly responsible for the immediate, real-time operations of the bulk electric system, or (ii) uses operating reliability data for analyzing system performance, standards compliance, and producing value-added information for use by operating entities, and that receives operating reliability data, directly from a disclosing party or by means of data-sharing systems maintained by NERC. The term includes NERC.

Deleted: reliability organizations

Deleted: Upon the advice of the RCWG and ORS, Federal and State agencies (e.g., FERC, DHS) may be granted RCIS read-only access as approved by the Operating Committee



- 4 -

Factors Viewer (NFV) Description — NFV is a vendor hosted limited-access website that provides transmission system curtailment information, generation shift factors, and transfer distribution factors.

Approval Criteria — NFV access is granted to any requestor that has an active NERC CRC account.

NFV Oversight — Under the general guidance of the IDC Working Group, NERC staff approves NFV access requests in accordance with the above criteria.

NFV Registration Link — http://nfv.nerc.mcgware.com/

NFV Website Address — http://nfv.nerc.mcgware.com/

System Data Exchange (SDX) Description — SDX is a vendor hosted system that allows for the exchange of electric system data between balancing authorities, transmission operators, and reliability coordinators. The SDX is used to exchange information related to generation and transmission outages, system load, and generation reserve data. Data from the SDX is used within the Interchange Distribution Calculator and the RCIS, and by various operating entities to update calculations of available transfer capability.

Approval Criteria

1. SDX access is granted to employees of Recipient Parties2 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for SDX access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. SDX access is granted to:

a. Reliability coordinators




- 5 -

b. Balancing authorities

c. Transmission operators

SDX Access Control — The SDX Self-Directed Work Team will annually review the current list of SDX users.

SDX Oversight — Under the general guidance of the IDC Working Group and its SDX Self-Directed Work Team, NERC staff approves SDX access requests in accordance with the above criteria.

SDX Registration Link — https://sdx.nerc.mcgware.com/MainMenu.aspx

SDX Website Address — https://sdx.nerc.mcgware.com/MainMenu.aspx

Interchange Distribution Calculator (IDC) Description — IDC is a vendor hosted system used primarily as the implementation tool for the NERC Transmission Loading Relief Procedure (TLR). Each NERC reliability coordinator in the Eastern Interconnection has the option of invoking the NERC TLR procedure or other agreed-upon local procedures to relieve transmission network congestion.

Approval Criteria

1. IDC access is granted to employees of Recipient Parties3 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for IDC access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. IDC access is granted to:

a. Reliability coordinators in the Eastern Interconnection






- 6 -

IDC Access Control — The IDC Working Group will annually review the current list of IDC users.

IDC Oversight — Under the general guidance of the IDC Working Group, NERC staff approves IDC access requests in accordance with the above criteria.

IDC Registration — Reliability coordinators, balancing authorities, and transmission operators are granted IDC access upon implementation of an IDC Working Group approved IDC change order.

IDC Website Address — http://www.oatiidc.com/

Tag Dump Reader Description — The Tag Dump Reader is an EPRI developed application used by reliability coordinators, balancing authorities, and transmission operators to read and analyze NERC tag dump files.

Approval Criteria

1. Tag Dump Reader access is granted to employees of Recipient Parties4 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for Tag Dump Reader access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. Tag Dump Reader access is granted to:




4. Access to the Tag Dump Reader and associated tag dump files is available to RCIS users through RCIS.

Tag Dump Reader Oversight — Under the general guidance of the IDC Working Group, NERC staff approves Tag Dump Reader access requests in accordance with the above criteria.

4 Ibid.



- 7 -


Tag Dump Reader Website Address — https://www.nerc.net/tags/

Interregional Security Network (ISN) Data Files Description —ISN Data Files are submitted by NERCNet node operators and contain the data definitions of all available Intercontrol Center Communications Protocol (ICCP) data points.

Approval Criteria

1. ISN Data Files access is granted to employees of Recipient Parties5 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for ISN Data Files access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. ISN Data Files access is granted to:




4. ISN Data Files Access Control — The Data Exchange Working Group will annually review the current list of ISN Data File users.

ISN Data Files Oversight — Under the general guidance of the Data Exchange Working Group, NERC staff approves ISN Data Files access requests in accordance with the above criteria.

ISN Data Files Registration Link — https://www.nerc.net/applicationbroker/

ISN Data Files Website Address — https://www.nerc.net/datastore/isndata




- 8 -

NERCNet Description — NERCNet (sometimes called the ISN) is a private frame relay network used by reliability coordinators, balancing authorities, and transmission operators for the timely exchange of operating data and information. As a private Intranet, NERCNet is also capable of handling additional applications between participants.

Approval Criteria — NERCNet access is granted to Recipient Parties6 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html

Additional NERCNet User Related Information

1. NERCNet User Organizations are subject to compliance with NERC reliability standard COM-001-1 (Telecommunications) and Attachment 1 – COM-001— NERCnet Security Policy.

2. NERCNet data recipients are subject to compliance with NERC reliability standard TOP-005-1 (Operational Reliability Information).

NERCNet Oversight — Under the general guidance of the Telecommunications Working Group, NERC staff approves NERCNet access requests in accordance with the above criteria.

Book of Flowgates (BoF) Description — The NERC Glossary of Terms defines a flowgate as a designated point on the transmission system through which the Interchange Distribution Calculator calculates the power flow from interchange transactions. The Book of Flowgates is an Excel spreadsheet database which documents all flowgates. Approval Criteria — BoF access is automatically granted to all users having an active NERC CRC account.

BoF Oversight — By default, NERC staff approves access to the BoF when approving NERC CRC access requests.


BoF Website Address — https://www.nerc.net/dfwg/bof/




- 9 -

Resource Adequacy Description — Reliability coordinators, balancing authorities, and transmission operators use the Resource Adequacy application (sometimes called ACE-Frequency) to monitor one-minute area control error (ACE) and interconnection frequency. In addition the application alerts system operators when abnormal frequency excursions occur. Such monitoring allows better compliance with NERC reliability standards and facilitates the investigation of system disturbances which result in frequency excursions.

Approval Criteria

1. Resource Adequacy access is granted to employees of Recipient Parties7 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for Resource Adequacy access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. Resource Adequacy access is granted to:




4.

Resource Adequacy Access Control — The Resources Subcommittee will annually review the current list of Resource Adequacy users.

Resource Adequacy Oversight — Under the general guidance of the Resources Subcommittee, NERC staff approves Resource Adequacy access requests in accordance with the above criteria.

Resource Adequacy Registration Link — https://www.nerc.net/applicationbroker/


Deleted: NERC staff will review and approve access requests to Resource Adequacy from Federal and State agencies (e.g., FERC, DHS)

1


Approved by the Operating Committee: December 13, 2007

Introduction At the direction of the Operating Committee, the Operating Reliability Subcommittee developed the following criteria for use by NERC staff in granting access to NERC web-based reliability tools. These reliability tools are used by reliability coordinators, balancing authorities, transmission operators, and, in some instances, purchasing-selling entities, and are under the purview of the Operating Reliability Subcommittee, the Resources Subcommittee, or one of their respective working groups or task forces.

Providing Information to Federal, State, or Provincial Agencies Whereas the NERC reliability tools are for operating the system, the Operating Committee resolves to work with federal, state, or provincial agencies to find the means to provide them with the information they need1.

Dispute Resolutions Disputes related to a request for access to one of the NERC reliability tools (e.g., denial of access to CRC) should be directed to [email protected]. If the dispute cannot be resolved by NERC staff, NERC staff shall consult with the Operating Committee Executive Committee.

1 The Operating Committee approved this wording in the form of a resolution at the committee’s December 13, 2007 meeting.

Exhibit H


2

Contents Introduction .....................................................................................................................1 Contents..........................................................................................................................2 NERC Reliability Tools........................................................................................................3 Central Repository for Security Events (CRC) ........................................................................3 Reliability Coordinator Information System (RCIS) .................................................................4 Factors Viewer (NFV).........................................................................................................4 System Data Exchange (SDX).............................................................................................5 Interchange Distribution Calculator (IDC) .............................................................................6 Tag Dump Reader .............................................................................................................7 Interregional Security Network (ISN) Data Files.....................................................................8 NERCNet .........................................................................................................................8 Book of Flowgates (BoF) ....................................................................................................9 Resource Adequacy ...........................................................................................................9


3

NERC Reliability Tools The NERC reliability tools addressed in this procedure include:






6. Tag Dump Reader


8. NERCNet



A description of the function and purpose of each reliability tool is provided followed by the vetting criteria for granting access.

Central Repository for Security Events (CRC) Description — CRC is a limited-access website that provides transmission system curtailment information to transmission customers in accordance with FERC Order 605, at the request of the Market Interface Committee in August 2000. Many transmission providers use the site to comply with Order 605, with references or direct links to the CRC site from their OASIS sites.

Approval Criteria — CRC access is granted to requester’s from:

1. Entities listed in Transmission Services Information Network (TSIN), (e.g., purchasing-selling entities, balancing authorities, and reliability coordinators)

2. Federal and State agencies (e.g., FERC, DHS)

3. Other organizations, provided the organization signs the NERC Policy on Availability of Secured Electricity Sector Data

CRC Oversight — Under the general guidance of the IDC Working Group, NERC staff approves CRC access requests in accordance with the above criteria.


CRC Website Address — https://crc.nerc.net/


4

Reliability Coordinator Information System (RCIS) Description — The RCIS is a real-time web-based messaging system that connects all reliability coordinators and many balancing authorities and transmission operators. RCIS allows reliability coordinators to share emergency alerts and other real-time operational information. RCIS also displays information related to ACE, frequency, and generator and transmission outages.

Approval Criteria

1. RCIS access is granted to employees of Recipient Parties2 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for RCIS access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. Reliability coordinators shall be granted RCIS read/write access 4. Balancing authorities and transmission operators shall be granted

RCIS read-only access

5. Regional Entities shall be granted RCIS read-only access

RCIS Access Control — The Reliability Coordinator Working Group will annually review the list of RCIS users.

RCIS Oversight — Under the general guidance of the Reliability Coordinator Working Group, NERC staff approves RCIS access requests in accordance with the above criteria.


RCIS Website Address — https://rcis.nerc.net/

Factors Viewer (NFV) Description — NFV is a vendor hosted limited-access website that provides transmission system curtailment information, generation shift factors, and transfer distribution factors.



5

Approval Criteria — NFV access is granted to any requestor that has an active NERC CRC account.

NFV Oversight — Under the general guidance of the IDC Working Group, NERC staff approves NFV access requests in accordance with the above criteria.

NFV Registration Link — http://nfv.nerc.mcgware.com/

NFV Website Address — http://nfv.nerc.mcgware.com/

System Data Exchange (SDX) Description — SDX is a vendor hosted system that allows for the exchange of electric system data between balancing authorities, transmission operators, and reliability coordinators. The SDX is used to exchange information related to generation and transmission outages, system load, and generation reserve data. Data from the SDX is used within the Interchange Distribution Calculator and the RCIS, and by various operating entities to update calculations of available transfer capability.

Approval Criteria

1. SDX access is granted to employees of Recipient Parties3 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for SDX access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. SDX access is granted to:




SDX Access Control — The SDX Self-Directed Work Team will annually review the current list of SDX users.



6

SDX Oversight — Under the general guidance of the IDC Working Group and its SDX Self-Directed Work Team, NERC staff approves SDX access requests in accordance with the above criteria.

SDX Registration Link — https://sdx.nerc.mcgware.com/MainMenu.aspx

SDX Website Address — https://sdx.nerc.mcgware.com/MainMenu.aspx

Interchange Distribution Calculator (IDC) Description — IDC is a vendor hosted system used primarily as the implementation tool for the NERC Transmission Loading Relief Procedure (TLR). Each NERC reliability coordinator in the Eastern Interconnection has the option of invoking the NERC TLR procedure or other agreed-upon local procedures to relieve transmission network congestion.

Approval Criteria

1. IDC access is granted to employees of Recipient Parties4 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for IDC access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. IDC access is granted to:

a. Reliability coordinators in the Eastern Interconnection



IDC Access Control — The IDC Working Group will annually review the current list of IDC users.

IDC Oversight — Under the general guidance of the IDC Working Group, NERC staff approves IDC access requests in accordance with the above criteria.



7

IDC Registration — Reliability coordinators, balancing authorities, and transmission operators are granted IDC access upon implementation of an IDC Working Group approved IDC change order.

IDC Website Address — http://www.oatiidc.com/

Tag Dump Reader Description — The Tag Dump Reader is an EPRI developed application used by reliability coordinators, balancing authorities, and transmission operators to read and analyze NERC tag dump files.

Approval Criteria

1. Tag Dump Reader access is granted to employees of Recipient Parties5 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for Tag Dump Reader access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. Tag Dump Reader access is granted to:




4. Access to the Tag Dump Reader and associated tag dump files is available to RCIS users through RCIS.

Tag Dump Reader Oversight — Under the general guidance of the IDC Working Group, NERC staff approves Tag Dump Reader access requests in accordance with the above criteria.


Tag Dump Reader Website Address — https://www.nerc.net/tags/

5 Ibid.


8

Interregional Security Network (ISN) Data Files Description —ISN Data Files are submitted by NERCNet node operators and contain the data definitions of all available Intercontrol Center Communications Protocol (ICCP) data points.

Approval Criteria

1. ISN Data Files access is granted to employees of Recipient Parties6 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for ISN Data Files access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. ISN Data Files access is granted to:




4. ISN Data Files Access Control — The Data Exchange Working Group will annually review the current list of ISN Data File users.

ISN Data Files Oversight — Under the general guidance of the Data Exchange Working Group, NERC staff approves ISN Data Files access requests in accordance with the above criteria.

ISN Data Files Registration Link — https://www.nerc.net/applicationbroker/

ISN Data Files Website Address — https://www.nerc.net/datastore/isndata

NERCNet Description — NERCNet (sometimes called the ISN) is a private frame relay network used by reliability coordinators, balancing authorities, and transmission operators for the timely exchange of operating data and information. As a private



9

Intranet, NERCNet is also capable of handling additional applications between participants.

Approval Criteria — NERCNet access is granted to Recipient Parties7 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html

Additional NERCNet User Related Information

1. NERCNet User Organizations are subject to compliance with NERC reliability standard COM-001-1 (Telecommunications) and Attachment 1 – COM-001— NERCnet Security Policy.

2. NERCNet data recipients are subject to compliance with NERC reliability standard TOP-005-1 (Operational Reliability Information).

NERCNet Oversight — Under the general guidance of the Telecommunications Working Group, NERC staff approves NERCNet access requests in accordance with the above criteria.

Book of Flowgates (BoF) Description — The NERC Glossary of Terms defines a flowgate as a designated point on the transmission system through which the Interchange Distribution Calculator calculates the power flow from interchange transactions. The Book of Flowgates is an Excel spreadsheet database which documents all flowgates. Approval Criteria — BoF access is automatically granted to all users having an active NERC CRC account.

BoF Oversight — By default, NERC staff approves access to the BoF when approving NERC CRC access requests.


BoF Website Address — https://www.nerc.net/dfwg/bof/

Resource Adequacy Description — Reliability coordinators, balancing authorities, and transmission operators use the Resource Adequacy application (sometimes called ACE-Frequency) to monitor one-minute area control error (ACE) and interconnection frequency. In addition the application alerts system operators when abnormal



10

frequency excursions occur. Such monitoring allows better compliance with NERC reliability standards and facilitates the investigation of system disturbances which result in frequency excursions.

Approval Criteria

1. Resource Adequacy access is granted to employees of Recipient Parties8 that have signed the NERC Operating Reliability Data Confidentiality Agreement. The confidentiality agreement is available at http://www.nerc.com/~filez/NERC_ORD.html.

2. Requests for Resource Adequacy access are reviewed with the requester’s manager to verify that the requester is responsible for real-time operating reliability, as that term is used in the NERC Operating Reliability Data Confidentiality Agreement, and is eligible for access to operating reliability data.

3. Resource Adequacy access is granted to:




Resource Adequacy Access Control — The Resources Subcommittee will annually review the current list of Resource Adequacy users.

Resource Adequacy Oversight — Under the general guidance of the Resources Subcommittee, NERC staff approves Resource Adequacy access requests in accordance with the above criteria.

Resource Adequacy Registration Link — https://www.nerc.net/applicationbroker/



Item 3. FYI These items are for the committee’s information. The committee is free to raise any of these items for discussion.

Item 3.a NERC Board of Trustees Vice Chairman Holeman will provide an overview of the February 12, 2008 Board of Trustees meeting.

Item 3.b Operating Committee Work Plan Vice Chairman Holeman will review the Operating Committee’s work plan. Attachment Operating Committee Work Plan

Item 3.c NERC Board of Trustees Technology Committee Stan Johnson, secretary of the NERC Board of Trustees Technology Committee, will review highlights from the Technology Committee’s February 11, 2008 meeting.

Item 3.d Operating Committee Appointments

Item 3.d.i. OC/PC Subgroup Nomination Form The officers of the Operating and Planning Committees developed a subgroup nomination form to facilitate the creation of task forces and working groups. Attachment OC/PC Subgroup Nomination Form

Item 3.d.ii. Reliability Fundamentals Working Group The chairman will review the purpose and scope of the Reliability Fundamentals Working Group. Attachment Scope – Reliability Fundamentals Working Group

Item 3.d.iii. Integrating Variable Generation Task Force Mr. Warren Frost, chairman of the Integrating Variable Generation Task Force, will provide an overview of task force activities.

Attachment Integrating Variable Generation Task Force Roster

Item 3.d.iv. Reliability Metrics Working Group Mr. Jason Shaver, chairman of the Reliability Metrics Working Group, will provide an overview of working group activities.

Attachment Reliability Metrics Working Group Roster

Operating Committee Three-Year Plan 2008 − 2010

Task When Description

1. Concepts Documents and Procedures

a. Reliability Concepts Document

By January 30, 2008 Core team. Core team in place with process for maintaining the document.

b. Integration of variable generation

2008-09 Resources Subcommittee. Write concepts chapter on balancing load and generation.

OC and PC. Develop joint team to develop concepts chapter on variable generation.

c. Training Concepts July 2008 Personnel Subcommittee. Develop personnel training model for the industry.

d. Voltage and Reactive concepts

2008-09 Operating Committee. Consider developing concepts chapters on voltage and reactive power.

e. Time Monitor Procedures

March 2008 Resources Subcommittee and RCWG. Develop committee procedure for selecting and monitoring Time Monitors. (See Dec 12-13, 2007 OC agenda for details)

2. SOL and IROL By May 1, 2008 Operating Reliability Subcommittee and Reliability Coordinator Working Group. Perform “gap” analysis and develop SARs for all standards that currently deal with SOL and IROL.

Includes analysis of IROL reports.

The ORS should bring philosophical issues to the Operating Committee at each OC meeting until this project is complete.


December (?) 2008 Operating Reliability Subcommittee. Continue to work with the OC and NERC staff to improve the effectiveness of this program.

4. Operator Tools 2008 Operating Committee. Foster new technology solutions and will lead the development of new reliability tools where new technology and tools are necessary to improve reliability. (NERC Strategic Plan).

5. Metrics 2008-10 Operating Committee. Participate with the Planning Committee in developing performance metrics.

6. Event analysis Every meeting NERC staff. Report from Bob Cummings on conclusions and recommendations from latest studies.

7. Other Items

a. BPS v. BES Why are these different? (Reliability Concepts document uses “Interconnection” and explains why.)

b. OC Role in Standards development

Establish more effective relationship between OC and standards work plan.

Attachment 3b

116-390 Village Blvd. Princeton, NJ 08540 609.452.8060 | www.nerc.com

Self-Nomination and Recommendation Form For OC and PC Subgroup Member

OC Subgroup Yes PC Subgroup Yes Joint OC/OC Subgroup Yes

Name of the Subgroup Information about you, serving as reference

(Please skip this section and go to #7 if you are self-nominating)

1. Name Your first and last name.

2. E-mail Address Your E-mail address.

3. Phone Number Your phone number.

4. Employer Who you work for or represent.

5. OC/PC Member Are you an OC or PC member? Yes No

6. NERC Membership Sector, if applicable

If your employer is a NERC member, select their NERC membership sector. If not, select “Not a NERC member.”

-Select-

Information about you for self-nomination or the person you are recommending

7. Name Nominee’s name.

8. E-mail Address Nominee’s e-mail address.

9. Title Nominee’s business title.

10. Employer Who the nominee works for or represents.

11. Mailing Address Nominee’s business address.

12. Phone Nominee’s business phone number.

13. Fax Nominee’s business fax number.

14. OC/PC Member Is the nominee an OC or PC member? Yes No

The nominee is willing to: a. Bring subject matter expertise to the

subgroup. b. Attend and participate in all

subgroup meetings. c. Express their opinions as well as the

opinions of the sector/sub-sector they represent at subgroup meetings.

d. Discuss and debate interests rather than positions.

e. Complete subgroup assignments.

Yes 15. Willingness to serve

The nominee has read the subgroup scope. Yes

Attachment 3d.i

-2-

16. Job Description

Explanation of the nominee’s responsibilities and technical qualifications in sufficient details.

17. Reasons for joining the subgroup

Explanation of why the nominee wants to join the subgroup.

18. Additional Information

Additional information about the nominee that would help the committee chair(s) decide to appoint this person.

How to Submit this Form E-mail this form as an attachment to the appropriate committee chair(s) and copy (CC) to committee secretary(ies).

For subgroup within

E-mail to committee chair(s) Copy to committee secretary(ies)

OC Gayle Mayo, [email protected] Larry Kezele, [email protected] PC Scott Helyer, [email protected] John Seelke, [email protected]

Joint OC/PC [email protected]; [email protected] [email protected]; [email protected]


609.452.8060 | www.nerc.com

Reliability Fundamentals Working Group

Purpose

Oversee the maintenance the Reliability Concepts document and assigned chapters and provide subject matter expertise to standard drafting teams and NERC committees and subcommittees as requested.

Scope of Working Group

1. Manage an “open source” process through a web site or means that serves as the common point of contact for industry stakeholders wishing to propose additions and enhancements to the Reliability Concepts document and associated chapters.

2. Maintain a published project list of items under development to and their status to allow the industry to monitor progress of, and to allow feedback on current initiatives.

3. Review revisions to the Reliability Concepts document proposed by others through the open source process.

4. Resolve issues raised by the industry stakeholders. 5. Present revisions to the Reliability Concepts document to the NERC standing committees for

discussion and any necessary approvals. 6. Support NERC committees, subcommittees, working groups, task forces and standards

drafting teams by answering questions about the Reliability Concepts document within their area of expertise.

7. Consult with other subcommittees, working groups and task forces to seek additional expertise as required.

8. Work on items assigned by the Operating or Planning Committee. Reporting

The Reliability Fundamentals Working Group reports to the Operating and Planning Committees. Membership Qualifications

Core Team Members must be:

1. “Passionate” about the subject, 2. Willing to commit their time for the good of the industry, 3. Pay attention to detail, and 4. Be good team players.

Attachment 3d.ii

Reliability Fundamentals Working Group

Approved by the OC and PC at their respective December 12–13, 2007 meetings. 2

The Reliability Fundamentals Working Group may request assistance from other subcommittees, working groups and task forces as necessary to accomplish the working group’s scope.

Integrating Variable Generation Task Force

Chairman Warren Frost

Vice President Operations & Reliability

Alberta Electric System Operator 2500, 330 - 5 Avenue SW Calgary, Alberta T2P 0L4

(403) 539-2515 (403) 539-2612 Fx warren.frost@ aeso.ca

Daniel Brooks

Manager, Power Delivery System Studies

Electric Power Research Institute 942 Corridor Park Blvd. Knoxville, Tennessee 37932


Lisa Dangelmaier

Operations Superintendent Hawaii Electric Light Company 54 Halekauila Street P.O. Box 1027 Hilo, Hawaii 96721

(808) 969-0427 (808) 896-8132 Fx lisa.dangelmaier@ helcohi.com

Abraham Ellis

Transmission Operations Public Service Company of New Mexico 414 Silver SE Albuquerque, New Mexico 87102


David Jacobson

Interconnection & Grid Supply Planning Engineer

Manitoba Hydro 12-1146 Waverly Street P.O. Box 815 Winnepeg, Manitoba R3C 2P4

(204) 474-3765 (204) 477-4606 Fx dajacobson@ hydro.mb.ca

Yuriy Kazachkov

Principal Consultant Siemens Power Transmission & Distribution 1482 Erie Boulevard Schenectady, New York 12305

(518) 395-5132 (518) 346-2777 Fx yuriy.kazachkov@ siemens.com

Warren Lasher

Manager, System Assessment Electric Reliability Council of Texas, Inc. 2705 West Lake Drive Taylor, Texas 76574

(512) 248-6379 (512) 248-4235 Fx wlasher@ ercot.com

Michael McMullen

Director, West Regional Operations

Midwest ISO, Inc. 1125 Energy Park Drive St. Paul, Minnesota 55108

(651) 632-8404 (612) 632-8417 Fx mmcmullen@ midwestiso.org

Michael Milligan

Consultant National Renewable Energy Laboratory NWTC 1617 Cole Boulevard Golden, Colorado 80401

(303) 384-6927 (303) 384-6901 Fx michael_milligan@ nrel.gov

Thomas M. Moleski

Senior Analyst PJM Interconnection, L.L.C. 955 Jefferson Avenue Norristown, Pennsylvania 19403-2497


Bradley M. Nickell, PE, MBA

Technology Manager - Wind Systems Integration

U.S. Department of Energy 1000 Independence Avenue, SW Washington, D.C. 20585

(202) 586-8508 brad.nickell@ ee.doe.gov

John R. Norden

Manager, Renewable Resource Integration

ISO New England, Inc. One Sullivan Road Holyoke, Massachusetts 01040-2841

(413) 537-7699 (413) 535-4343 Fx jnorden@ iso-ne.com

Attachment 3d.iii

Dale Osborn Transmission Technical Director

Midwest ISO, Inc. 1125 Energy Park Drive St. Paul, Minnesota 55108

(651) 632-8417 dosborn@ midwestiso.org

Sophie Paquette

Transmission Planning Engineer Hydro-Quebec TransEnergie Complexe Desjardins, Tower East 10th Floor P.O. Box 10000 Montreal, Quebec H5B 1H7

(514) 289-2211 Ext. 2796 (514) 289-4459 Fx paquette.sophie@ hydro.qc.ca

Subbaiah Pasupulati

Director of Technical Studies Oak Creek Energy Systems, Inc. 14633 Willow Springs Road Mojave, California 93501

(909) 241-9197 (661) 822-5991 Fx subbaiah@ oakcreekenergy.com

Pouyan Pourbeik

Technical Executive EPRI 942 Corridor Park Boulevard Knoxville, Tennessee 37932

(919) 806-8126 ppourbeik@ epri.com

David C. Schooley

Sr. Engineer Commonwealth Edison Co. 1N301 Swift Road Lombard, Illinois 60148

(630) 691-4466 david.schooley@ exeloncorp.com

Dariush Shirmohammadi

Consultant Oak Creek Energy Systems, Inc. 10208 Cielo Drive Beverly Hills, California 90210

(310) 858-1174 (310) 858-8274 Fx dariush@ shirconsultants.com

J. Charles Smith

Executive Director Utility Wind Integration Group 2004 Lakebreeze Way Reston, Virginia 20191

(703) 860-5160 (703) 860-1544 Fx jcharlessmith@ comcast.net

Juan R. Villar

Director Transmission Northeast Region

FPL Energy 700 Universe Boulevard Juno Beach, Florida 33408

(561) 694-3472 (561) 304-5161 Fx juan_r_villar@ fpl.com

Edward P. Weber

Transmission System Planning Manager

Western Area Power Administration P.O. Box 35800 Billings, Montana 59107-5800


Robert Zavadil

Vice President EnerNex Corp 170C Market Place Boulevard Knoxville, Tennessee 37922

(865) 691-5540 Ext. 149 (865) 691-5046 Fx [email protected]

NERC Staff Larry J. Kezele

Manager of Reliability Support Services


(609) 452-8060 (609) 452-9550 Fx larry.kezele@ nerc.net

NERC Staff Mark G. Lauby

Manager of Reliability Assessments


(609) 452-8060 (609) 452-9550 Fx mark.lauby@ nerc.net

NERC Staff Thomas Vandervort

Reliability Assessment & Performance Analysis Coordinator


(609) 452-8060 (609) 452-9550 Fx tom.vandervort@ nerc.net

Reliability Metrics Working Group

Chairman Jason Shaver

Reliability Standards and Performance Manager

American Transmission Company, LLC N19 W23993 Ridgeway Pkwy. W. Waukesha, Wisconsin 53187-0047

(262) 506-6885 jshaver@ atcllc.com

Secretary Jessica J Bian

Manager of Benchmarking North American Electric Reliability Corporation 116-390 Village Boulevard Princeton, New Jersey 08540

(609) 452-8060 (609) 452-9550 Fx jessica.bian@ nerc.net

William O. Adams

System Operations Manager Georgia Power Company 241 Ralph McGill Boulevard NE Bin #10024 Atlanta, Georgia 30308-3374

(404) 506-1160 (404) 506-2049 Fx woadams@ southernco.com

Scott Benner

Senior Engineer, Performance Compliance

PJM Interconnection, L.L.C. 955 Jefferson Avenue Valley Forge Corporate Center Norristown, Pennsylvania 19403-2497


Stuart Brindley

Manager-Training & Emergency Preparedness

Independent Electricity System Operator Station A Box 4474 Toronto, Ontario M5W 4E5

(905) 855-6108 (905) 855-6471 Fx stuart.brindley@ ieso.ca

Gary Bullock

Manager, Merchant Transmission Planning & Analysis

Tennessee Valley Authority 1101 Market Street MR 2B Chattanooga, Tennessee 37402-2801

(423) 751-8402 (423) 751-7462 Fx gcbullock@ tva.gov

Brian C. Furumasu

NERC Compliance Officer Bonneville Power Administration P.O. Box 3621 Portland, Oregon 97208-3621

(503) 230-7681 (503) 230-3862 Fx bcfurumasu@ bpa.gov

David Anthony McRee

Senior Engineer Duke Energy 526 S. Church Street Charlotte, North Carolina 28202

(704) 382-9841 (704) 382-6938 Fx damcree@ duke-energy.com

Howard A. Tarler

Chief, Bulk Transmission Systems Operations and Planning

New York State Department of Public Service 3 Empire State Plaza Albany, New York 12223

(518) 486-2483 (518) 473-2420 Fx howard_tarler@ dps.state.ny.us

Chad Thompson

Senior Operations Engineer/Analyst Operations Planning

Electric Reliability Council of Texas, Inc. 2705 West Lake Drive Taylor, Texas 76574

(512) 248-6508 (512) 248-3055 Fx cthompson@ ercot.com

Observer Albert M. DiCaprio

Strategist PJM Interconnection, L.L.C. 955 Jefferson Avenue Valley Forge Corporate Center Norristown, Pennsylvania 19403-2497


Attachment 3d.iv

Observer Alireza Ghassemian, Ph.D, EE Electrical Engineer

Federal Energy Regulatory Commission 888 First Street NE Room 91-05 Washington, D.C. 20426

(202) 502-8634 (202) 219-2836 Fx alireza.ghassemian@ ferc.gov

Observer Fred Huang

Operations Engineer/Analyst II Electric Reliability Council of Texas, Inc. 2705 West Lake Drive Taylor, Texas 76574


NERC IT Staff Member

Paul J. Baratelli Information Technology - Web Developer/Programmer


(609) 452-8060 (609) 452-9550 Fx paul.baratelli@ nerc.net

NERC IT Observer Brian Nolan

Manager of Information Technology and Projects


(609) 452-8060 (609) 452-9550 Fx Brian.Nolan@ nerc.net


Item 4. Operating Committee Charter Revisions Action

Approve.

This is a follow-up from the joint OC/PC meeting item.

Attachment Operating Committee Charter (red-line)

Operating Committee Charter (clean)

Background At its October 23, 2007 meeting, the Board of Trustees asked NERC staff to develop the common elements of an appropriate guidelines development process and work to have the committees develop guidelines in accordance with those common elements. The officers of the Compliance and Certification Committee (CCC), the Critical Infrastructure Protection Committee (CIPC), the Operating Committee (OC), the Planning Committee (PC), and the Standards Committee (SC) agreed upon a common process to be followed by NERC’s technical committees (CIPC, OC, and PC). Appendix 4 in the attached draft red-line OC charter contains this process.

The following table delineates all changes in the attached draft redline charter:

Change Language changed Reason

Section 2.2 Advice and Recommendations.

Added: “Issue reliability guidelines in accordance with the process described in Appendix 4.”

Section 2 lists the OC’s functions, and issuing reliability guidelines is an added function.

Section 3.4.d under “Selection”

Modified item d. of the membership selection requirements: “A particular organization, including its affiliates, may not have more than one member on the committee.”

Clarified that affiliated organizations are considered as one organization for membership purposes.


Change Language changed Reason

Section 3.7 Proxies

Modified this section as follows: “A member of the committee may give a proxy only to a person who is a member registered in not affiliated with the same sectororganization as another committee member. This provision is consistent with Section 3.4.d. Each voting member of the committee shall have one vote on any matter coming before the committee that requires a vote.”

Committee members need not be NERC members, so they do not necessarily have a sector. The existing language is therefore improper on this point and was stricken. However, just as two members cannot be from the same organization, neither can a member and a proxy. Therefore, this language was added.

Appendix 3 Added an entire new Appendix 3 that contains the OC’s approval process for reliability guidelines.

Added to comply with the NERC Board of Trustees request as discussed above.


609.452.8060 | www.nerc.com

Operating Committee Charter Draft February 29, 2008 Approved by the Board of Trustees: May 2, 2007

Attachment 4


Table of Contents

Purpose............................................................................................................................................ 4

Section 1. Functions................................................................................................................. 4

1. General forum. 4 2. Advice and recommendations. 4 3. Support to the Reliability Readiness Program. 4 4. Support for other programs. 5 5. Approve the following documents and procedures: 5 6. Opinions and interpretations. 5

Section 2. Membership ............................................................................................................ 6

1. Goals 6 2. Expectations. 6 3. Representation. 6 4. Selection. 6 5. Terms. 7 6. Resignations, Vacancies, and Nonparticipation 7 7. Proxies. 7

Section 3. Meetings.................................................................................................................. 7

1. Quorum. 7 2. Voting. 7 3. Antitrust Guidelines. 8 4. Open Meetings. 8 5. Confidential Sessions. 8

Section 4. Officers ................................................................................................................... 8

1. Terms and conditions. 8 2. Selection. 8

Section 5. Subcommittees........................................................................................................ 9

1. Appointing subgroups. 9 2. Nominating subcommittee. 9

Section 6. Executive Committee.............................................................................................. 9

1. Authorization. 9 2. Membership. 9 3. Election Process. 9 4. Terms. 10

Appendix 1 – Committee Members.............................................................................................. 11

Appendix 2 – Meeting Procedures................................................................................................ 13

Section 1. Voting Procedures for Motions............................................................................. 13

Formatted: Indent: Left: 0"

Deleted: 5

Deleted: 5

Deleted: 5

Deleted: 7

Deleted: 7

Deleted: 9

Deleted: 10

Deleted: 12

Deleted: 12


Section 2. Minutes ................................................................................................................. 13

Section 3. Minority Opinions................................................................................................. 13

Section 4. Personal Statements .............................................................................................. 13

Appendix 3 – Reliability Guidelines Approval Process

Deleted: 12

Deleted: 12

Deleted: 12


Purpose



1. General forum. Provides a general forum for aggregating ideas and interests regarding the operations of the interconnected bulk power systems in North America.

2. Advice and recommendations. Provides NERC (stakeholders, Board of Trustees, and staff) with advice, recommendations, and the collective and diverse opinions on matters related to interconnected operations to help the industry arrive at informed decisions. Issue reliability guidelines in accordance with the process described in Appendix 3.

3. Support to the Reliability Readiness Program. Provide technical support, guidance, and advice to NERC’s Reliability Readiness Program (see also NERC Rules of Procedure, Section 700, “Reliability Readiness Evaluation and Improvement program, and Appendix 7, “Reliability Readiness Evaluation and Improvement Program Procedure.”)

a. General









Through time






4. Support for other programs. Provide technical advice and subject matter expert support to each of the NERC program areas, and serve as a forum to integrate the outputs of each NERC program area.

a. Standards.





• Future adequacy

• Event analysis

• Benchmarking



5. Approve the following documents and procedures: a. Reliability Coordinator plans.




6. Opinions and interpretations. Provide technical opinions at the industry stakeholders’ request on operating reliability concepts, philosophies, and standards.



1. Goals The Operating Committee provides for balanced decision making by bringing together a wide diversity of opinions from industry experts with outstanding technical knowledge and experience in the area of interconnected systems operation reliability.

2. Expectations. Operating Committee voting members are expected to: a. Bring subject matter expertise to the Operating Committee






3. Representation. See Appendix 1, “Committee Members”



4. Selection. NERC sector members will annually elect voting committee members in committee sectors corresponding to their NERC sector under an election process that is open, inclusive, and fair. The selection process will be completed in time for the secretary to send the committee membership list to the board for its approval at the board’s August meeting so that new committee members may be seated at the September meeting.




d. A particular organization, including its affiliates, may not have more than one member on the committee.

e. If additional Canadian members are added, no more than one additional Canadian voting member shall be selected from a sector unless this limitation


precludes the addition of the number of additional Canadian voting representatives required by Section 3.3.b. In this case, no more than two additional Canadian voting members may be selected from the same sector.


5. Terms. Members’ terms are staggered, with one-half of the members' terms expiring each year. Except for the initial selection, a member’s term is two years and will commence on the first September meeting following the member’s selection pursuant to Section 2.4 and continue until the September meeting two years later. Members may be re-elected for subsequent terms.

6. Resignations, Vacancies, and Nonparticipation a. Members who resign will be replaced for the time remaining in the member’s

term. Members will be replaced pursuant to Section 2.4, officers will be replaced pursuant to Section 4, and executive committee members will be replaced pursuant to Section 6.




7. Proxies. A member of the committee may give a proxy only to a person who is not affiliated with the same organization as another committee member. This provision is consistent with Section 3.4.d. Each voting member of the committee shall have one vote on any matter coming before the committee that requires a vote.

Section 3. Meetings


1. Quorum. The quorum necessary for the transaction of business (i.e., formal actions) at meetings of the Committee is two-thirds of the voting members currently on the committee roster (i.e., does not count vacancies). The committee may engage in discussions without a quorum present.

2. Voting. Actions by members of the Committee shall be approved upon receipt of the affirmative vote of 2/3 of the voting members of the Committee present and voting, in person or by proxy, at any meeting at which a quorum is present. The

Deleted: a member registered in

Deleted: sector


chairman and vice-chairman may vote. Additional voting guidelines are in Appendix 2.

3. Antitrust Guidelines. All persons attending or otherwise participating in the Committee meeting shall act in accordance with NERC’s Antitrust Compliance Guidelines at all times during the meeting. A copy of the NERC antitrust statement shall be included with each meeting agenda.

4. Open Meetings. NERC committee meetings shall be open to the public, except as noted below under Confidential Sessions. Although meetings are open, only voting members may offer and act on motions.

5. Confidential Sessions. The chair of a committee may limit attendance at a meeting or portion of a meeting, based on confidentiality of the information to be disclosed at the meeting. Such limitations should be applied sparingly and on a non-discriminatory basis as needed to protect information that is sensitive to one or more parties. A preference, where possible, is to avoid the disclosure of sensitive or confidential information so that meetings may remain open at all times. Confidentiality agreements may also be applied as necessary to protect sensitive information.

Section 4. Officers

1. Terms and conditions. At its June meeting the Committee shall select a chairman and vice chairman from among its voting members by majority vote of the members of the Committee to serve during the period July 1 through June 30 of the following two years, provided that:




2. Selection. The Committee selects officers using the following process. The chairman is selected first, followed by the vice-chairman.










1. Appointing subgroups. The Operating Committee may appoint technical subcommittees, task forces, and working groups as needed.

2. Nominating subcommittee. At the first regular meeting following the selection of a new committee chairman, the chairman will nominate, for the committee’s approval, a slate of five committee members from different sectors to serve as a nominating subcommittee. The subcommittee will:




1. Authorization. The executive committee is authorized to act between regular meetings of its parent committee. However, the executive committees may not reverse its parent committee’s decisions.

2. Membership. The Committee will elect an executive committee of six members, all from different sectors, as follows:

• Chairman

• Vice-chairman


3. Election Process.The Nominating Subcommittee will present its slate of candidates for the four “at large” members.





4. Terms. The executive committee will be replaced every two years, with the chair and vice chair replaced at a June meeting and the at-large members replaced at a September meeting.


AAppppeennddiixx 11 –– CCoommmmiitttteeee MMeemmbbeerrss Name Definition Members

Voting Members


2


2


2



2


2


2


2


Name Definition Members

Voting Members

8. Large end-use electricity customer This sector includes any entity in North America with at least one service delivery taken at 50 kV or higher (radial supply or facilities dedicated to serve customers) that is not purchased for resale; and any single end-use customer with an average aggregated service load (not purchased for resale) of at least 50,000 MWh annually, excluding cogeneration or other back feed to the serving utility. This sector also includes organizations that represent the interests of such entities.

2

9. Small end-use electricity customer This sector includes any person or entity within North America that takes service below 50 kV; and any single end-use customer with an average aggregated service load (not purchased for resale) of less than 50,000 MWh annually, excluding cogeneration or other back feed to the serving utility. This sector also includes organizations (including state consumer advocates) that represent the interests of such entities.

2



2

11. Regional reliability organization This sector includes any regional reliability organization as defined in Article I, Section 1, of the Bylaws of the corporation.

2




Non-Voting Members1

This sector includes any federal, state, or provincial government department or agency in North America having a regulatory and/or policy interest in wholesale electricity. Entities with regulatory oversight over the Corporation or any regional entity, including U.S., Canadian, and Mexican federal agencies and any provincial entity in Canada having statutory oversight over the Corporation or a regional entity with respect to the approval and/or enforcement of reliability standards, may be nonvoting members of this sector.

0










AAppppeennddiixx 22 –– MMeeeettiinngg PPrroocceedduurreess Section 1. Voting Procedures for Motions








Section 2. Minutes










AAppppeennddiixx 33 –– RReelliiaabbiilliittyy GGuuiiddeelliinneess AApppprroovvaall PPrroocceessss 1. Reliability Guidelines

Reliability guidelines are documents that suggest approaches or behavior in a given technical area for the purpose of improving reliability. Reliability guidelines are not binding norms or mandatory requirements. Reliability guidelines may be adopted by a responsible entity in accordance with its own facts and circumstances.2

2. Approval of Reliability Guidelines Because reliability guidelines contain suggestions that may result in actions by responsible entities, those suggestions must be thoroughly vetted before a new or updated guideline receives approval by a technical committee. The process described below will be followed by the Operating Committee:

a. New/updated draft guideline approved. The Operating Committee approves release of a new or updated draft guideline developed by one of its subgroups or the committee as a whole.

b. Post draft guideline for industry comment. The draft guideline is posted for industry-wide comment for forty-five (45) days. If the draft guideline is an update, a redline version against the previous version must also be posted.

c. Post industry comments and responses. After the public comment period, the Operating Committee posts the comments received as well as its responses to the comments. The committee may delegate the preparation of responses to a committee subgroup.

d. New/updated guideline approval and posting. A new or updated guideline which considers the comments received, is approved by the sponsoring technical committee and posted on the NERC Web site. Updates must include a revision history and a redline version against the previous version.

e. Guideline updates. After posting a new or updated guideline, the Operating Committee will continue to accept comments from the industry via a Web-based forum where commenters may post their comments.

i. Each quarter, the Operating Committee will review the comments received. At any time, the Operating Committee may decide to update the guideline based on the comments received or on changes in the industry that necessitate an update.

ii. Updating an existing guideline will require that a draft updated guideline be approved by the Operating Committee in step “a” and

2 Standards Committee authorization is required for a reliability guideline to become a supporting document that is posted with or referenced from a NERC Reliability Standard. See Appendix 3A in the NERC’s Rules of Procedure under “Supporting Documents.”

Formatted: Bullets and Numbering




proceed to steps “b” and “c” until it is approved by the Operating Committee in step “d.”

OOppeerraattiinngg CCoommmmiitttteeee CChhaarrtteerr

February 13, 2008

Attachment 4


2

TTaabbllee ooff CCoonntteennttss Purpose............................................................................................................................................ 3

Section 1. Functions................................................................................................................. 3

Section 2. Membership ............................................................................................................ 4

Section 3. Meetings.................................................................................................................. 6

Section 4. Officers ................................................................................................................... 7

Section 5. Subcommittees........................................................................................................ 8

Section 6. Executive Committee.............................................................................................. 8

Appendix 1 – Committee Members................................................................................................ 9

Appendix 2 – Meeting Procedures................................................................................................ 11

Section 1. Voting Procedures for Motions............................................................................. 11

Section 2. Minutes ................................................................................................................. 11

Section 3. Minority Opinions................................................................................................. 11

Section 4. Personal Statements .............................................................................................. 11

Appendix 3 – Reliability Guidelines Approval Process ............................................................... 12


3

Purpose



1. General forum. Provides a general forum for aggregating ideas and interests regarding the operations of the interconnected bulk power systems in North America.

2. Advice and recommendations. Provides NERC (stakeholders, Board of Trustees, and staff) with advice, recommendations, and the collective and diverse opinions on matters related to interconnected operations to help the industry arrive at informed decisions. Issue reliability guidelines in accordance with the process described in Appendix 3.

3. Support to the Reliability Readiness Program. Provide technical support, guidance, and advice to NERC’s Reliability Readiness Program (see also NERC Rules of Procedure, Section 700, “Reliability Readiness Evaluation and Improvement program, and Appendix 7, “Reliability Readiness Evaluation and Improvement Program Procedure.”)

a. General









Through time






4

4. Support for other programs. Provide technical advice and subject matter expert support to each of the NERC program areas, and serve as a forum to integrate the outputs of each NERC program area.

a. Standards.





• Future adequacy

• Event analysis

• Benchmarking



5. Approve the following documents and procedures: a. Reliability Coordinator plans.




6. Opinions and interpretations. Provide technical opinions at the industry stakeholders’ request on operating reliability concepts, philosophies, and standards.


1. Goals The Operating Committee provides for balanced decision making by bringing together a wide diversity of opinions from industry experts with outstanding technical knowledge and experience in the area of interconnected systems operation reliability.

2. Expectations. Operating Committee voting members are expected to: a. Bring subject matter expertise to the Operating Committee



5





3. Representation. See Appendix 1, “Committee Members”



4. Selection. NERC sector members will annually elect voting committee members in committee sectors corresponding to their NERC sector under an election process that is open, inclusive, and fair. The selection process will be completed in time for the secretary to send the committee membership list to the board for its approval at the board’s August meeting so that new committee members may be seated at the September meeting.




d. A particular organization, including its affiliates, may not have more than one member on the committee.

e. If additional Canadian members are added, no more than one additional Canadian voting member shall be selected from a sector unless this limitation precludes the addition of the number of additional Canadian voting representatives required by Section 3.3.b. In this case, no more than two additional Canadian voting members may be selected from the same sector.



6

5. Terms. Members’ terms are staggered, with one-half of the members' terms expiring each year. Except for the initial selection, a member’s term is two years and will commence on the first September meeting following the member’s selection pursuant to Section 2.4 and continue until the September meeting two years later. Members may be re-elected for subsequent terms.

6. Resignations, Vacancies, and Nonparticipation a. Members who resign will be replaced for the time remaining in the member’s term.

Members will be replaced pursuant to Section 2.4, officers will be replaced pursuant to Section 4, and executive committee members will be replaced pursuant to Section 6.




7. Proxies. A member of the committee may give a proxy only to a person who is not affiliated with the same organization as another committee member. This provision is consistent with Section 3.4.d. Each voting member of the committee shall have one vote on any matter coming before the committee that requires a vote.

Section 3. Meetings


1. Quorum. The quorum necessary for the transaction of business (i.e., formal actions) at meetings of the Committee is two-thirds of the voting members currently on the committee roster (i.e., does not count vacancies). The committee may engage in discussions without a quorum present.

2. Voting. Actions by members of the Committee shall be approved upon receipt of the affirmative vote of 2/3 of the voting members of the Committee present and voting, in person or by proxy, at any meeting at which a quorum is present. The chairman and vice-chairman may vote. Additional voting guidelines are in Appendix 2.

3. Antitrust Guidelines. All persons attending or otherwise participating in the Committee meeting shall act in accordance with NERC’s Antitrust Compliance Guidelines at all times during the meeting. A copy of the NERC antitrust statement shall be included with each meeting agenda.

4. Open Meetings. NERC committee meetings shall be open to the public, except as noted below under Confidential Sessions. Although meetings are open, only voting members may offer and act on motions.


7

5. Confidential Sessions. The chair of a committee may limit attendance at a meeting or portion of a meeting, based on confidentiality of the information to be disclosed at the meeting. Such limitations should be applied sparingly and on a non-discriminatory basis as needed to protect information that is sensitive to one or more parties. A preference, where possible, is to avoid the disclosure of sensitive or confidential information so that meetings may remain open at all times. Confidentiality agreements may also be applied as necessary to protect sensitive information.

Section 4. Officers

1. Terms and conditions. At its June meeting the Committee shall select a chairman and vice chairman from among its voting members by majority vote of the members of the Committee to serve during the period July 1 through June 30 of the following two years, provided that:




2. Selection. The Committee selects officers using the following process. The chairman is selected first, followed by the vice-chairman.









8


1. Appointing subgroups. The Operating Committee may appoint technical subcommittees, task forces, and working groups as needed.

2. Nominating subcommittee. At the first regular meeting following the selection of a new committee chairman, the chairman will nominate, for the committee’s approval, a slate of five committee members from different sectors to serve as a nominating subcommittee. The subcommittee will:




1. Authorization. The executive committee is authorized to act between regular meetings of its parent committee. However, the executive committees may not reverse its parent committee’s decisions.

2. Membership. The Committee will elect an executive committee of six members, all from different sectors, as follows:

• Chairman

• Vice-chairman


3. Election Process.The Nominating Subcommittee will present its slate of candidates for the four “at large” members.




4. Terms. The executive committee will be replaced every two years, with the chair and vice chair replaced at a June meeting and the at-large members replaced at a September meeting.


9

AAppppeennddiixx 11 –– CCoommmmiitttteeee MMeemmbbeerrss Name Definition Members

Voting Members


2


2


2



2


2


2


2


10

Name Definition Members

Voting Members

8. Large end-use electricity customer

This sector includes any entity in North America with at least one service delivery taken at 50 kV or higher (radial supply or facilities dedicated to serve customers) that is not purchased for resale; and any single end-use customer with an average aggregated service load (not purchased for resale) of at least 50,000 MWh annually, excluding cogeneration or other back feed to the serving utility. This sector also includes organizations that represent the interests of such entities.

2

9. Small end-use electricity customer

This sector includes any person or entity within North America that takes service below 50 kV; and any single end-use customer with an average aggregated service load (not purchased for resale) of less than 50,000 MWh annually, excluding cogeneration or other back feed to the serving utility. This sector also includes organizations (including state consumer advocates) that represent the interests of such entities.

2



2

11. Regional reliability organization This sector includes any regional reliability organization as defined in Article I, Section 1, of the Bylaws of the corporation.

2




Non-Voting Members1

This sector includes any federal, state, or provincial government department or agency in North America having a regulatory and/or policy interest in wholesale electricity. Entities with regulatory oversight over the Corporation or any regional entity, including U.S., Canadian, and Mexican federal agencies and any provincial entity in Canada having statutory oversight over the Corporation or a regional entity with respect to the approval and/or enforcement of reliability standards, may be nonvoting members of this sector.

0










11

AAppppeennddiixx 22 –– MMeeeettiinngg PPrroocceedduurreess Section 1. Voting Procedures for Motions








Section 2. Minutes










12

AAppppeennddiixx 33 –– RReelliiaabbiilliittyy GGuuiiddeelliinneess AApppprroovvaall PPrroocceessss 1. Reliability Guidelines

Reliability guidelines are documents that suggest approaches or behavior in a given technical area for the purpose of improving reliability. Reliability guidelines are not binding norms or mandatory requirements. Reliability guidelines may be adopted by a responsible entity in accordance with its own facts and circumstances.2

2. Approval of Reliability Guidelines Because reliability guidelines contain suggestions that may result in actions by responsible entities, those suggestions must be thoroughly vetted before a new or updated guideline receives approval by a technical committee. The process described below will be followed by the Operating Committee:

a. New/updated draft guideline approved. The Operating Committee approves release of a new or updated draft guideline developed by one of its subgroups or the committee as a whole.

b. Post draft guideline for industry comment. The draft guideline is posted for industry-wide comment for forty-five (45) days. If the draft guideline is an update, a redline version against the previous version must also be posted.

c. Post industry comments and responses. After the public comment period, the Operating Committee posts the comments received as well as its responses to the comments. The committee may delegate the preparation of responses to a committee subgroup.

d. New/updated guideline approval and posting. A new or updated guideline which considers the comments received, is approved by the sponsoring technical committee and posted on the NERC Web site. Updates must include a revision history and a redline version against the previous version.

e. Guideline updates. After posting a new or updated guideline, the Operating Committee will continue to accept comments from the industry via a Web-based forum where commenters may post their comments.

i. Each quarter, the Operating Committee will review the comments received. At any time, the Operating Committee may decide to update the guideline based on the comments received or on changes in the industry that necessitate an update.

ii. Updating an existing guideline will require that a draft updated guideline be approved by the Operating Committee in step “a” and proceed to steps “b” and “c” until it is approved by the Operating Committee in step “d.”

2 Standards Committee authorization is required for a reliability guideline to become a supporting document that is posted with or referenced from a NERC Reliability Standard. See Appendix 3A in the NERC’s Rules of Procedure under “Supporting Documents.”


Item 5. Critical Infrastructure Protection Stan Johnson, manager of Situation Awareness and Infrastructure Security, will lead a discussion of the following topics.

Item 5.a NERC Situation Awareness Tool At the December 2008 Operating Committee meeting, Stan Johnson and Scott Mix (managers of Situation Awareness and Infrastructure Security) explained the purpose of the Situation Awareness Tool. Mr. Johnson will provide a status report.

Item 5.b North American SynchroPhasor Initiative This is a follow-up from the joint OC/PC meeting item.


Item 5.c National Response Framework Mr. Johnson will review the highlights of the Department of Homeland Security’s National Response Framework.

Purpose: The National Response Framework presents the guiding principles that enable all response partners to prepare for and provide a unified national response to disasters and emergencies ⎯ from the smallest incident to the largest catastrophe. The Framework establishes a comprehensive, national, all-hazards approach to domestic incident response.

Additional information is available at http://www.fema.gov/emergency/nrf/aboutNRF.htm.

http://www.fema.gov/emergency/nrf/aboutNRF.htm


Item 6. Reliability Readiness Program

Item 6.a Reliability Readiness Program Work Plan Kevin Conway, reliability readiness evaluator, will provide an overview of the Reliability Readiness Program Work Plan.

Item 6.b Role of the Operating Committee Chairman Mayo will lead a discussion of the role of the Operating Committee in the Reliability Readiness Program.

Background (Excerpt of the Operating Committee charter)

3. Support to the Reliability Readiness Program. Provide technical support, guidance, and advice to NERC’s Reliability Readiness Program (see also NERC Rules of Procedure, Section 700, “Reliability Readiness Evaluation and Improvement program, and Appendix 7, “Reliability Readiness Evaluation and Improvement Program Procedure”).

a. General • Develop criteria for measuring program success, and

review the program against those criteria. • Recommend actions to other NERC programs (standards,

compliance, assessments, training, etc.) based on lessons learned and trends from readiness evaluations and examples of excellence

b. Readiness Evaluations • Review readiness evaluations for trends and recommend

new or different types of evaluations or changes in processes or metrics, including:

Readiness criteria Guidelines for reporting and disclosure, and Guidelines for consistency and relevancy of

evaluations: • Between comparable entities, and • Through time

• Provide guidance to the readiness evaluations process c. Examples of Excellence




Item 7. Functional Model Working Group Action

Discussion. (Follow-up from the joint meeting)

Steve Crutchfield, standards development coordinator, will respond to committee questions related the development of version 4 of the Functional Model.


Item 8. Organization Registration and Certification Discussion

Lucius Burris, chairman of the Organization Registration and Certification Subcommittee (ORCS), will provide an overview of its efforts to develop registration and certification requirements for balancing authorities, transmission operators, and reliability coordinators. The timeline for developing revised rule of procedure 500 is reflected in the following table.

Organizational Certification Process Project Development Timeline

September 12, 2007 Joint Compliance and Certification Committee (CCC) & Standards Committee (SC) meeting, translate interim standards into a process/procedure: ● Transmission Operator Certification Standards (ORG

001-008) ● Balancing Authority Certification Standards (ORG 009-

018) ● Reliability Coordinator Certification Standards (ORG

020-027) ● Appointed a subcommittee to perform this task (ORCS) ● Held first ORCS meeting September 13 to establish

schedule

October 9 & 10, 2007

2nd ORCS meeting ● Developed 1st draft of RoP 500, Appendix 5, &

questionnaires ● Made forms & questionnaires separate from Appendix 5 ● Revised schedule & process flow diagram

October 25, 2007 Submit solicitation for informal comments ● Web site developed to communicate changes ● NERC members, roster, & coordinators ● Regional compliance managers

December 11–13, 2007

Meet in Orlando ● Review stakeholder comments ● Incorporate comments and develop first rough draft ● Lucius to provide CCC update on December 13

January 23 & 24, 2008

Meet in Salt Lake City ● Review revised certification process and develop draft for

NERC compliance vice president (VP) ● Provide draft and comment resolution report


January 28, 2008 Provide NERC VP the draft for review and comment February 4 , 2008 Provide CCC package for review February 14 , 2008 ORCS chair to present draft to CCC for review and approval

to place draft on the NERC Web site for 45-day public comments (with the ORCS)

February 22 , 2008 Place draft on NERC Web site for public comments per NERC bylaws Article XI section 2

March 18 &19, 2008 Meet in conjunction with the CCC meeting in Salt Lake City ● Review public comments to date ● Revise certification process based on comments ● ORCS chair to provide CCC update on project

April 7, 2008 45-day public comment due date April 15 & 16, 2008 ORCS to meet in Atlanta

● Review and incorporate all substantive public comments ● Develop package for NERC vice presidentfor board

presentation April 28, 2008 Provide final package and draft of RoP 500 and its appendix

for CCC approval to present to the Board of Trustees (Provide package 1 week earlier for review)

May 12, 2008 Present the final draft package to the board for approval (Provide package 1 week earlier for review)


Item 9. Reliability-based Control Standard Drafting Team Discussion

Doug Hils, chairman of the Reliability-based Control Standard Drafting Team, will provide a status report of this standard development effort.

Background (Summary of Purpose/Industry Need) This project includes expanding on the work already done in developing the draft BAL-007 through BAL-011 by adding requirements to address the following concerns:

• To support corrective action by the balancing authority when excessive Area Control Error (ACE) (as determined by this standard) may be contributing to or causing action to be taken to correct an SOL/IROL problem.

• To prevent interconnection frequency excursions of short duration attributed to the ramping of on- and off-peak interchange transactions.

• To support timely transmission congestion relief by requiring corrective load/generation management by the balancing authority(ies) within a defined time frame when participating in transmission loading relief procedures.

• To address the directives of FERC Order 693.

• To ensure that when finalized the standards associated with this project conform to the latest versions of NERC’s Reliability Standards Development Procedure, the Sanction Guidelines of the North American Electric Reliability Corporation, and the ERO Rules of Procedure.

Additionally, the frequency model used to establish the frequency-based limits will be reviewed to see if additional enhancements are necessary.

Small groups of balancing authorities were brought under the generation control criteria of the draft Standard BAL-007 beginning in July 2005. Under the Proof-of-Concept Field Trial (“Field Trial”), each balancing authority balances resources and demand, and takes corrective action as needed, so that its clock-minute ACE does not exceed its clock-minute Balancing Authority ACE Limit (“BAAL”) for more than 30 consecutive clock-minutes.


Item 10. Personnel Training Action

Endorse the Personnel Subcommittee’s plan for developing a learning model for system personnel. John Taylor, chairman of the Personnel Subcommittee, will lead this discussion.

Attachment “A Learning Model for System Personnel”

Background

The Personnel Subcommittee comprises experts in operator and personnel training, and can play an important service role by providing a “learning model” for the industry to use. The model would provide a helpful guide for personnel trainers within the utilities, and a valuable reference for third-party training providers.

The subcommittee can effectively serve as the core team of experts to develop this model using the “open source” process that solicits industry comment and encourages dialog through Internet forums and the like.

A Learning Model for System Personnel

Concept Establish a sustainable learning model for system personnel that provides needed information and instruction dynamically assembled on demand from a pool of content types. Through the development of knowledge maps based on performance requirements and personnel competency profiles, the goal is to build a performance support system around the constantly changing competency profile of each learner. The stages leading up to this performance support model would include needs assessment role identification, performance gap analysis, and competency‐based action learning experiences. Once the content is established, the delivery system will be learner focused by delivering just‐in‐time performance support linking a learning context to job performance. Knowledge is filtered to deliver the information system personnel need when they need it.

Phase One - Operations and Program Requirements Gathering • Establish competency requirements by function according to the Functional Model for all

system personnel that impact reliability of the bulk electrical system.

• Establish performance metrics requirements.

• Establish learning assessment requirements.

• Establish minimum requirements for a training program – number of hours, minimum, essential components of training, certification requirements, etc.

• Establish a training program accreditation process.

Phase Two - Support Requirements Gathering • Establish requirements for system personnel performance support capability that integrates

performance metrics with knowledge bases, situational filtering, and individual learning profiles.

• Establish knowledge capture process to incorporate lessons learned and situational awareness into the knowledge base in real time.

• Repeat phase one for other system personnel.

Phase Three - Design and Develop Dynamic Model • Establish situational knowledge push requirements for system personnel based on real‐time

operating conditions. Knowledge push means that the performance support system proactively notifies the employee of conditions in real time and contingency scenarios that require employee action to maintain system reliability by presenting dynamically arranged instruction for taking the action required by the situation. The performance support system would include only instruction beyond what the employee already knows, per their competency profile, to successfully accomplish the task. Once completed, the new competency of the employee is added to their competency profile.

• Repeat phase two for other system personnel.

Attachment 10

Phase Four – Design and Develop Dynamic Model for Other System Personnel Repeat phase three for other system personnel.


Item 11. Education and Certification Programs Action

Martin Sidor, director of training, education and personnel certification, will lead a discussion on the 2008 activities of the System Operator Certification Program and the Continuing Education Program. Mid-year changes in the certification examinations and what it will mean to test-takers will be presented.

Also to be discussed are the increased use of continuing education activities to maintain certification and the project to develop more stringent criteria for training providers to become “NERC-approved providers.”


Item 12. Events Analysis Action

Discussion.

Bob Cummings will bring the committee up-to-date on the latest “lessons learned” from the analyses NERC is conducting.


Item 13. NERC/NAESB Coordination Action

Discussion.

Andy Rodriquez, manager of business practice coordination, will summarize recent activities related to the development of NERC rReliability sstandards and NAESB business practices in the following topical areas. Mr. Rodriquez works within the Standards Development group in NERC’s Washington, D.C. office. He is responsible for ensuring close coordination between the reliability activities of NERC and the commercial needs of NAESB.

Item 13.a TLR Procedure The NERC TLR reliability standard IRO-006-4 was approved by the Board of Trustees on October 23, 2007. IRO-006-4 splits the Eastern Interconnection TLR procedure into NAESB business practices and NERC Reliability Standards. NERC filed IRO-006-4 with FERC on December 21, 2007.

The TLR standard drafting team posted the Joint NERC/NAESB System Operator’s Transmission Loading Relief (TLR) Reference Manual on February 8, 2008 for a 45-day comment period.

Item 13.b ATC/AFC and CBM/TRM Revisions The ATC/AFC and CBM/TRM standards were posted for a 30-day pre-ballot review on February 1, 2008. The standard drafting team is proposing revisions to the following reliability standards:

MOD-001 — Available Transfer Capability — An “umbrella” standard that requires the selection of a methodology, the updating of values, and the sharing of procedures and data.

MOD-004 — Capacity Benefit Margin — A standard that describes the requesting, calculation, and use of CBM

MOD-008 — Transmission Reliability Margin — A standard that describes the calculation and use of TRM

MOD-028 — Area Interchange Methodology — A standard that describes the calculation of TTC and ATC, as performed primarily in the Eastern Interconnection

MOD-029 — Rated System Path Methodology — A standard that describes the calculation of TTC and ATC, as performed primarily in the Western Interconnection

MOD-030 — Flowgate Methodology — A standard that describes the calculation of TFC and AFC, as well as the conversion of those values to TTC and ATC

Item 13.c Balancing Authority Controls The Balancing Authority Controls Standard Drafting Team will be reviewing the following standards:

• BAL-002 - Disturbance Control Performance


• BAL-004 – Time Error Correction • BAL-005 – Automatic Generation Control • BAL-006 - Inadvertent Interchange

The purpose of this set of four standards is to ensure that balancing authorities take actions to maintain interconnection frequency with each balancing authority contributing its fair share to frequency control and without burdening transmission facilities with excessive imbalances of load and generation.

The standard authorization request is intended to address the following:

• FERC Final Rule “Mandatory Reliability Standards for the Bulk-Power System, FERC Order 693” on the NERC standards BAL-002, 004, 005, and 006.

• To specify the Time Error Correction, special Area Control Error cases, and Inadvertent Interchange reliability requirements/business practices with NERC and NAESB collaborative participation.

• To incorporate the necessary content, structure, and language to comply with the NERC standards process.


Item 14. Real-time Tools Best Practices Task Force Action

Approve.

Jack Kerr, chairman of the Real-time Tools Best Practices Task Force, will provide an overview of the final report. The report is posted at http://www.nerc.com/~filez/rtbptf.html.

Background The purpose of the Real-time Tools Best Practices Task Force is to identify the best practices currently employed for tools used for building and maintaining real-time network models, performing state estimation and real-time contingency analysis, and maintaining situational awareness in accordance with NERC Operating Standards. An interim goal of the task force will be to develop guidelines for minimally acceptable capabilities for these critical reliability tools. The ultimate goal of the task force will be to recommend specific requirements for inclusion in new reliability standards for state-of-the-art real-time network modeling and network analysis and monitoring tools.

Secretary’s Note: While the report is approximately 500 pages, I would urge you to download and review the Executive Summary, the Introduction, and Chapter 6 (Next Steps). These sections of the report will give a very good overview of this project.

http://www.nerc.com/%7Efilez/rtbptf.html


Item 15. Interchange Subcommittee Action

Discussion.

John Ciza, a member of the Interchange Subcommittee, will provide an overview of efforts to develop a new TSIN registry and of a project to create an Eastern Interconnection Interchange Tool.

Item 15.a TSIN Registry NAESB requested that the Joint Interchange Scheduling Working Group (JISWG) perform a technical review of the NERC Transmission System Information Networks (TSIN) Registry. Since the last revision of the functional specification for a new TSIN registry occurred in May 2006, NAESB requested that JISWG review the specification for accuracy and to incorporate language that reflects the transition of the registry from NERC to NAESB.

The JISWG continues its review of the TSIN (now call Electric Industry Registry) registry functional specification.

Item 15.b Eastern Interconnection Interchange Tool The Interchange Subcommittee formed the Eastern Interconnection Interchange Tool Task Force to analyze the feasibility of creating a tool similar to the WECC Interchange Tool (WIT) in the Eastern Interconnection. The task force analysis will address WIT-like functionality, funding, central control, hosting site, and tool management.


Item 16. Resources Subcommittee Terry Bilke, chairman of the Resources Subcommittee, will provide an overview of the following topics:

Item 16.a Time Monitor Reference Document Action

Approve.

At the committee’s request, the Resources Subcommittee, with input from the Reliability Coordinator Working Group and the Operating Reliability Subcommittee, prepared the Time Monitor Reference Document.

Attachment Time Monitor Reference Document

Item 16.b Access to Performance Data In accordance with its charter, the Resources Subcommittee is charged with reviewing “balancing authorities’ control performance on a periodic basis.” However, the data required to perform this review (i.e., CPS1 and CPS2 data) are deemed to be compliance data and, therefore, subject to non-disclosure agreement requirements. The Resources Subcommittee remains at an impasse in being granted access to the data.

Item 16.c FERC Request for Access to Inadvertent Data Chairman Bilke will review a request made by FERC for access to inadvertent data.


609.452.8060 | www.nerc.com

Time Monitoring Reference Document

Introduction This procedure outlines responsibilities of reliability coordinators serving as time monitors in the North American interconnections. Changes to this reference document will be at the direction of the NERC Operating Committee (OC) with the participation of the NERC Resources Subcommittee (RS) and the Operating Reliability Subcommittee (ORS). This document applies to current and future frequency or time related procedural responsibilities assigned to the time monitor in NERC standards or NAESB business practices. Designation of Time Monitor There will be one time monitor within each interconnection. NERC ORS will nominate a time monitor for each interconnection. The ORS will present the nomination to the NERC OC for acceptance. The NERC OC will forward the nomination to the NERC Board of Trustees for approval. The term of each time monitor shall be three (3) years. The time monitor term shall be automatically renewed unless requested otherwise by providing a minimum of six (6) months notice to the NERC ORS. Should an existing time monitor no longer be willing or able to fulfill its responsibilities, the NERC Operating Committee will direct the NERC ORS to nominate a replacement and communicate the transition plan. If a time monitor fails to fulfill its responsibilities, the NERC ORS will work with the time monitor to resolve the problem. The NERC ORS will submit a report to the NERC OC either identifying corrective measures taken or provide a recommendation for a new time monitor. The NERC RS will report to the NERC OC and ORS any frequency or time error issues that may have been caused or aggravated by the time monitor or time error correction (TEC) practices. Responsibilities of the Time Monitor The time monitor will start and stop time error corrections as outlined in NERC standards and NAESB business practices. The time monitor will terminate any TEC believed to be negatively impacting reliability. Requests for termination may come from any transmission operator or balancing authority operator to its respective reliability coordinator, who will notify the respective Interconnection’s time monitor.

Attachment 16a

Time Monitoring Reference Document 2

The time monitor will provide accumulated time error following each TEC or at least monthly to the BAs within its interconnection. References Links to each time monitor’s local procedures to meet this procedure will be posted at the NERC RS Web site (http://www.nerc.com/~filez/rs.html). Interconnection Time Monitors Each interconnection has identified the following reliability coordinator as its time monitor:

1. ERCOT Interconnection – ERCOT reliability coordinator 2. Québec Interconnection – Hydro-Québec TransÉnergie reliability coordinator 3. Eastern Interconnection – Midwest ISO reliability coordinator 4. WECC Interconnection – California Mexico reliability coordinator


Item 17. Operating Reliability Subcommittee David Zwergel, chairman of the Operating Reliability Subcommittee, will provide an overview of the following topics:

Item 17.a Flowgate Administration Reference Document Action

Approve.

The Distribution Factor Working Group drafted version 4 of the Flowgate Administration Reference Document. Changes in version 4 address 1) usage of temporary flowgates and 2) elimination of commercial flowgates.

Attachments Flowgate Administration Reference Document – version 3 (red-line)

Flowgate Administration Reference Document – version 4 (clean)

Version 4 - 1 - Approved by Operating Committee: March 13, 2008

Flowgate Administration Reference Document Version 4

Reference Document Subsections A. General B. Guidelines for Permanent Flowgates C. Flowgate Administration

A. General

Purpose The Flowgate Administration Reference Document explains how RELIABILITY COORDINATORS can add, modify, and remove flowgates from the Interchange Distribution Calculator (IDC). The procedures that follow in this document:

• Ensure that Reliability Coordinators have the flowgate data they need to manage system reliability.

• Ensure that market participants receive timely information about flowgate changes they need to assess impacts on Interchange Transactions.

• Address administrative authorities, criteria, and processes for: o Adding and deleting “permanent” Reliability Flowgates. o Modifying Reliability Flowgates in the Book of Flowgates. o Defining “temporary” Reliability Flowgates. o Expiring “temporary” Reliability Flowgates. o Adding “temporary” Reliability Flowgates to the Book of Flowgates. o Modifying Informational Flowgates.

Terms Flowgate. A single transmission element, or group of transmission elements, intended to model MW flow impact relating to transmission limitations and transmission service usage. Within the IDC, Transfer Distribution Factors (see PTDFs and OTDFs as defined below) are calculated to approximate MW flow impact on the flowgate caused by point-to-point power transfers.

Flowgate Categories:

Temporary Flowgate. A flowgate created by a RELIABILITY COORDINATOR within the IDC to monitor or mitigate a Constraint for which a PERMANENT FLOWGATE has not been identified. TEMPORARY FLOWGATES expire either at the time of the next model update, by default, or on the End Date and Time entered in the IDC, not to exceed ninety days, by the RELIABILITY COORDINATOR who created the TEMPORARY FLOWATE.

Permanent Flowgate. A flowgate approved by the Reliability Coordinator Working Group and listed in the Book of Flowgates. PERMANENT FLOWGATES remain in the IDC unless removed from the Book of Flowgates and deleted from the IDC.

Formatted: Small caps

Formatted: Not Small caps

Deleted: 3

Deleted: when each new IDC base case is updated. IDC base cases are normally updated on a monthly basis

Deleted: 3

Deleted: September 14, 2005

Attachment 17a

Flowgate Administration Reference Document


Flowgate Types: A flowgate may be classified as one or more of the following types

Informational Flowgate Type: A flowgate the RELIABILITY COORDINATOR can establish for monitoring purposes only. An INFORMATIONAL FLOWGATE does not qualify for Transmission Loading Relief (TLR) usage and should be reviewed periodically.

Reliability PTDF Flowgate Type: A RELIABILITY PTDF FLOWGATE is represented by the PTDF of its defined transmission element(s). The defined transmission element(s) can be the monitored element(s) or the contingent element(s). This type of flowgate qualifies for TLR usage under NERC reliability standard IRO-006, “Reliability Coordination — Transmission Loading Relief.”

Reliability OTDF Flowgate Type: A RELIABILITY OTDF FLOWGATE is another type of Reliability Flowgate. It is represented by the OTDF on the Monitored Element(s) with the simulated outage of the critical contingency. This type of flowgate also qualifies for TLR usage under NERC reliability standard IRO-006.

Commercial Flowgate Type: COMMERCIAL FLOWGATES contain transmission elements on which transmission service has been or is expected to be sold. Some RELIABILITY COORDINATORS and Transmission Providers use COMMERCIAL FLOWGATES in ATC calculations. A COMMERCIAL FLOWGATE status alone does not qualify for TLR usage. RELIABILITY COORDINATORS and Distribution Factor Working Group (DFWG) are not responsible for approving, modeling, and maintaining COMMERCIAL FLOWGATES and therefore the administrative process described in this document does not apply to COMMERCIAL FLOWGATES.

Benchmark Flowgate Type: A Benchmark Flowgate is a type identified by the DFWG for internal use by the Interchange Distribution Calculator (IDC) as a quality assurance measure. It is used in monitoring differences in calculated Transfer Distribution Factors (TDFs) by the IDC. A separate column in the Book of Flowgates (Flowgates page) identifies Benchmark Flowgates.

Responsibilities and Authorities The Operating Reliability Subcommittee (ORS) is responsible for:

• Reviewing all changes to the Book of Flowgates at each of its regularly scheduled meetings.

• Resolving disputes resulting from the implementation of Section B, “Guidelines for Permanent Flowgates,” or Section C, “Flowgate Administration,” in this reference document.

The Reliability Coordinator Working Group (RCWG) is responsible for:

• Authorizing all changes to the Book of Flowgates on a monthly basis.

• Providing semi-annual reports on flowgate changes to the ORS.

Individual RELIABILITY COORDINATORS are responsible for:

• Authorizing the use of TEMPORARY FLOWGATES.

• Modeling TEMPORARY FLOWGATES within the IDC.

• Recommending conversion of TEMPORARY FLOWGATES to PERMANENT FLOWGATES.

Formatted: Strikethrough

Deleted: -0

Deleted: -0

Deleted: 3




• Reviewing and updating periodically its PERMANENT FLOWGATES.

• Authorizing the removal of PERMANENT FLOWGATES.

The Distribution Factor Working Group (DFWG) is responsible for:

• Performing the on-going function of administering the Book of Flowgates under the direction of the RCWG. Administration includes but is not limited to the following:

1. Tracking the relationship between TEMPORARY FLOWGATES and PERMANENT FLOWGATES for historical purposes.

2. Reviewing flowgate data, including the transmission element(s), which define PERMANENT FLOWGATES.

3. Reviewing flowgate data, including the transmission element(s), which define TEMPORARY FLOWGATES used for TLR greater than TLR Level 1.

• Authorizing Book of Flowgates changes that can be unanimously agreed upon. If the DFWG cannot unanimously agree, or if they see reasons for RCWG discussions, then the DFWG will forward the flowgate review to the RCWG with its recommendations.

• Provide quarterly updates to the RCWG on Book of Flowgates changes highlighting key changes in PERMANENT FLOWGATES.

• Modeling the basic set of permanent Book of Flowgates changes as approved by RCWG.

• Maintaining and being the “owner” of the Book of Flowgates.

• Developing a posted flowgate review process for evaluating flowgates.

The NERC staff is responsible for:

• Posting the basic set of flowgates on the NERC web site, and posting IDC messages regarding flowgate changes and TEMPORARY FLOWGATE additions. IDC message posting is expected to be an automated process.

Deleted: 3




B. Guidelines for Permanent Flowgates A PERMANENT FLOWGATE must meet at least one of the following five requirements to be in the Book of Flowgates:

1. A TLR has been called on the flowgate at least once during the past two years.

2. A TLR greater than TLR Level 1 has been called on the TEMPORARY FLOWGATE at least once during the past two years and the TEMPORARY FLOWGATE was created multiple times during the past two years.

3. The flow on the flowgate has exceeded a reasonably high percentage (i.e. 90%) of its applicable rating or INTERCONNECTED RELIABILITY OPERATING LIMIT (IROL) at least once during the past three years.

4. The flow on the flowgate is expected to exceed a reasonably high percentage (i.e. 90%) of its applicable rating or IROL in the coming year.

5. The DFWG or RCWG has determined that the flowgate should remain in the Book of Flowgates, or the RELIABILITY COORDINATOR recommends and presents the rationale to the RCWG that a flowgate be included or retained in the Book of Flowgates.

PERMANENT FLOWGATES will not be removed from the Book of Flowgates or the IDC database unless requested by the responsible RELIABILITY COORDINATOR.

Deleted: 3




C. Flowgate Administration

The Flowgate Administration process is shown in the flowchart below.

Deleted: 3


DFWG or RCreview BoF

Need tocreate ormodify

PermanentFG Created in

IDC

DFWGReview

RCWGReview

By Reliability Coordinator

Temporary FG created in

IDC

By DFWG

DFWGApprove?

InformRCWG

Update BoF and post DFWG records revision Notify IDC provider Notify RC via IDC

No

RCWGApprove?

Yes

RC provides additional

information

No

Inform DFWG by DFWG FG

process

ORS:Reviews changes to BoFResolves disputes

Yes



Permanent Flowgates 1. The ORS has final approval for the basic set of flowgates taking into account recommendations

from the RCWG and DFWG.

2. The DFWG assists in preparing information for RCWG review and maintains records showing when flowgate decisions were made.

3. The responsible RELIABILITY COORDINATOR or its DFWG representative authorizes changes to PERMANENT FLOWGATES through submittal to the DFWG.

4. The DFWG will either unanimously approve flowgates or forward flowgates to the RCWG with recommendations.

5. After the flowgate’s approval, the DFWG and IDC service provider will model the flowgate changes.

6. NERC staff will post the basic set of flowgates with a link provided via the NERC web site at crc.nerc.com.

Temporary Flowgates 1. RELIABILITY COORDINATORS, along with the Transmission Providers they represent, will

determine the need for TEMPORARY FLOWGATES. TEMPORARY FLOWGATES can be created directly within the IDC and may become available for potential TLR use within 20 minutes to one hour after they are entered into the IDC. TEMPORARY FLOWGATES can be deleted at any time and expire on the End Date and Time, not to exceed ninety days, entered in the IDC by the RELIABILITY COORDINATOR who created the TEMPORARY FLOWGATE . If no End Date and Time is entered for the TEMPORARY FLOWGATE, it will expire when the IDC base case is updated.

2. Information regarding TEMPORARY FLOWGATE additions, modifications, or deletions is communicated to RELIABILITY COORDINATORS via the IDC service provider. Whenever a flowgate is added, deleted, or changed, the IDC service provider will send a message to the DFWG with a copy to a NERC listserver. NERC staff will publicly post the message on the NERC crc.nerc.com web page. Permanent Book of Flowgates changes will be posted separately.

3. TEMPORARY FLOWGATES will expire either at the time of the next model update, by default, or on the End Date and Time entered in the IDC, not to exceed ninety days, by the RELIABILITY COORDINATOR who created the TEMPORARY FLOWATE.. IDC base cases are normally updated on a monthly basis. The IDC model updating process schedule will be posted on the NERC web site as it becomes known.

4. TEMPORARY FLOWGATES, which are used for TLR greater that Level 1, should go through a DFWG review. Individual RELIABILITY COORDINATORS may recommend converting a TEMPORARY FLOWGATE into a PERMANENT FLOWGATE by following Step 3 in the PERMANENT FLOWGATES section above.

Informational Flowgates 1. RELIABILITY COORDINATORS may establish an INFORMATIONAL FLOWGATE to help them

monitor power flows over certain interfaces.




Deleted: ,

Deleted: they

Deleted: automatically

Deleted: when each new IDC base case is updated

Deleted: automatically

Deleted: when a new IDC base case is updated

Deleted: 3




2. The RELIABILITY COORDINATOR establishing the INFORMATIONAL FLOWGATE will review the flowgate periodically, and remove the flowgate if no longer needed.

3. INFORMATIONAL FLOWGATES are included in the Book of Flowgates that is posted on the NERC web site.

4. INFORMATIONAL FLOWGATES may be converted to Reliability Flowgates by going through the formal recommendation process.

DFWG Flowgate Review RELIABILITY COORDINATORS may request the DFWG to review and revise the list of PERMANENT FLOWGATES in accordance with the guidelines detailed in Section B. A standardized approach should be used for reviewing all flowgates. The Book of Flowgates will be kept up to date so that it is consistent with the latest IDC base case. The DFWG will generally not review TEMPORARY FLOWGATES unless:

• They are used for a TLR greater than Level 1.

• A flowgate is repeatedly created as a Temporary Flowgate.

• A request is made to convert a Temporary Flowgate to a Permanent Flowgate.

INFORMATIONAL FLOWGATES are not to be used for TLR. The review for INFORMATIONAL FLOWGATES may differ from that of a Reliability Flowgate. DFWG review of Reliability Flowgates for thermal purposes may differ from the review of Reliability Flowgates used for voltage or dynamic stability purposes.

Flowgate review may require the responsible RELIABILITY COORDINATOR to provide additional flowgate detail as determined by the DFWG.

Deleted: 3



609.452.8060 | www.nerc.com

Flowgate Administration Reference Document (Version 4)

Reference Document Subsections A. General B. Guidelines for Permanent Flowgates C. Flowgate Administration

AA.. GGeenneerraall Purpose The Flowgate Administration Reference Document explains how RELIABILITY COORDINATORS can add, modify, and remove flowgates from the Interchange Distribution Calculator (IDC). The procedures that follow in this document:

• Ensure that Reliability Coordinators have the flowgate data they need to manage system reliability.

• Ensure that market participants receive timely information about flowgate changes they need to assess impacts on Interchange Transactions.

• Address administrative authorities, criteria, and processes for: o Adding and deleting “permanent” Reliability Flowgates. o Modifying Reliability Flowgates in the Book of Flowgates. o Defining “temporary” Reliability Flowgates. o Expiring “temporary” Reliability Flowgates. o Adding “temporary” Reliability Flowgates to the Book of Flowgates. o Modifying Informational Flowgates.

Terms Flowgate. A single transmission element, or group of transmission elements, intended to model MW flow impact relating to transmission limitations and transmission service usage. Within the IDC, Transfer Distribution Factors (see PTDFs and OTDFs as defined below) are calculated to approximate MW flow impact on the flowgate caused by point-to-point power transfers. Flowgate Categories:

Temporary Flowgate. A flowgate created by a RELIABILITY COORDINATOR within the IDC to monitor or mitigate a Constraint for which a PERMANENT FLOWGATE has not been

Attachment 17a



identified. TEMPORARY FLOWGATES expire either at the time of the next model update, by default, or on the End Date and Time entered in the IDC, not to exceed ninety days, by the RELIABILITY COORDINATOR who created the TEMPORARY FLOWATE. Permanent Flowgate. A flowgate approved by the Reliability Coordinator Working Group and listed in the Book of Flowgates. PERMANENT FLOWGATES remain in the IDC unless removed from the Book of Flowgates and deleted from the IDC.

Flowgate Types: A flowgate may be classified as one or more of the following types

Informational Flowgate Type: A flowgate the RELIABILITY COORDINATOR can establish for monitoring purposes only. An INFORMATIONAL FLOWGATE does not qualify for Transmission Loading Relief (TLR) usage and should be reviewed periodically. Reliability PTDF Flowgate Type: A RELIABILITY PTDF FLOWGATE is represented by the PTDF of its defined transmission element(s). The defined transmission element(s) can be the monitored element(s) or the contingent element(s). This type of flowgate qualifies for TLR usage under NERC reliability standard IRO-006, “Reliability Coordination — Transmission Loading Relief.” Reliability OTDF Flowgate Type: A RELIABILITY OTDF FLOWGATE is another type of Reliability Flowgate. It is represented by the OTDF on the Monitored Element(s) with the simulated outage of the critical contingency. This type of flowgate also qualifies for TLR usage under NERC reliability standard IRO-006. Benchmark Flowgate Type: A Benchmark Flowgate is a type identified by the DFWG for internal use by the Interchange Distribution Calculator (IDC) as a quality assurance measure. It is used in monitoring differences in calculated Transfer Distribution Factors (TDFs) by the IDC. A separate column in the Book of Flowgates (Flowgates page) identifies Benchmark Flowgates.

Responsibilities and Authorities The Operating Reliability Subcommittee (ORS) is responsible for:

• Reviewing all changes to the Book of Flowgates at each of its regularly scheduled meetings.

• Resolving disputes resulting from the implementation of Section B, “Guidelines for Permanent Flowgates,” or Section C, “Flowgate Administration,” in this reference document.

The Reliability Coordinator Working Group (RCWG) is responsible for:

• Authorizing all changes to the Book of Flowgates on a monthly basis.

• Providing semi-annual reports on flowgate changes to the ORS.



Individual RELIABILITY COORDINATORS are responsible for:

• Authorizing the use of TEMPORARY FLOWGATES.

• Modeling TEMPORARY FLOWGATES within the IDC.

• Recommending conversion of TEMPORARY FLOWGATES to PERMANENT FLOWGATES.

• Reviewing and updating periodically its PERMANENT FLOWGATES.

• Authorizing the removal of PERMANENT FLOWGATES.

The Distribution Factor Working Group (DFWG) is responsible for:

• Performing the on-going function of administering the Book of Flowgates under the direction of the RCWG. Administration includes but is not limited to the following:

1. Tracking the relationship between TEMPORARY FLOWGATES and PERMANENT FLOWGATES for historical purposes.

2. Reviewing flowgate data, including the transmission element(s), which define PERMANENT FLOWGATES.

3. Reviewing flowgate data, including the transmission element(s), which define TEMPORARY FLOWGATES used for TLR greater than TLR Level 1.

• Authorizing Book of Flowgates changes that can be unanimously agreed upon. If the DFWG cannot unanimously agree, or if they see reasons for RCWG discussions, then the DFWG will forward the flowgate review to the RCWG with its recommendations.

• Provide quarterly updates to the RCWG on Book of Flowgates changes highlighting key changes in PERMANENT FLOWGATES.

• Modeling the basic set of permanent Book of Flowgates changes as approved by RCWG.

• Maintaining and being the “owner” of the Book of Flowgates.

• Developing a posted flowgate review process for evaluating flowgates.

The NERC staff is responsible for:

• Posting the basic set of flowgates on the NERC web site, and posting IDC messages regarding flowgate changes and TEMPORARY FLOWGATE additions. IDC message posting is expected to be an automated process.



BB.. GGuuiiddeelliinneess ffoorr PPeerrmmaanneenntt FFlloowwggaatteess A PERMANENT FLOWGATE must meet at least one of the following five requirements to be in the Book of Flowgates:

1. A TLR has been called on the flowgate at least once during the past two years.

2. A TLR greater than TLR Level 1 has been called on the TEMPORARY FLOWGATE at least once during the past two years and the TEMPORARY FLOWGATE was created multiple times during the past two years.

3. The flow on the flowgate has exceeded a reasonably high percentage (i.e. 90%) of its applicable rating or INTERCONNECTED RELIABILITY OPERATING LIMIT (IROL) at least once during the past three years.

4. The flow on the flowgate is expected to exceed a reasonably high percentage (i.e. 90%) of its applicable rating or IROL in the coming year.

5. The DFWG or RCWG has determined that the flowgate should remain in the Book of Flowgates, or the RELIABILITY COORDINATOR recommends and presents the rationale to the RCWG that a flowgate be included or retained in the Book of Flowgates.

PERMANENT FLOWGATES will not be removed from the Book of Flowgates or the IDC database unless requested by the responsible RELIABILITY COORDINATOR.



CC.. FFlloowwggaattee AAddmmiinniissttrraattiioonn The Flowgate Administration process is shown in the flowchart below.

DFWG or RCreview BoF

Need tocreate ormodify

PermanentFG Created in

IDC

DFWGReview

RCWGReview

By Reliability Coordinator

Temporary FG created in

IDC

By DFWG

DFWGApprove?

InformRCWG

Update BoF and postDFWG records revisionNotify IDC providerNotify RC via IDC

No

RCWGApprove?

Yes

RC providesadditional

information

No

Inform DFWG by DFWG FG

process

ORS:Reviews changes to BoFResolves disputes

Yes



Permanent Flowgates 1. The ORS has final approval for the basic set of flowgates taking into account

recommendations from the RCWG and DFWG.

2. The DFWG assists in preparing information for RCWG review and maintains records showing when flowgate decisions were made.

3. The responsible RELIABILITY COORDINATOR or its DFWG representative authorizes changes to PERMANENT FLOWGATES through submittal to the DFWG.

4. The DFWG will either unanimously approve flowgates or forward flowgates to the RCWG with recommendations.

5. After the flowgate’s approval, the DFWG and IDC service provider will model the flowgate changes.

6. NERC staff will post the basic set of flowgates with a link provided via the NERC web site at crc.nerc.com.

Temporary Flowgates 1. RELIABILITY COORDINATORS, along with the Transmission Providers they represent, will

determine the need for TEMPORARY FLOWGATES. TEMPORARY FLOWGATES can be created directly within the IDC and may become available for potential TLR use within 20 minutes to one hour after they are entered into the IDC. TEMPORARY FLOWGATES can be deleted at any time and expire on the End Date and Time, not to exceed ninety days, entered in the IDC by the RELIABILITY COORDINATOR who created the TEMPORARY FLOWGATE . If no End Date and Time is entered for the TEMPORARY FLOWGATE, it will expire when the IDC base case is updated.

2. Information regarding TEMPORARY FLOWGATE additions, modifications, or deletions is communicated to RELIABILITY COORDINATORS via the IDC service provider. Whenever a flowgate is added, deleted, or changed, the IDC service provider will send a message to the DFWG with a copy to a NERC listserver. NERC staff will publicly post the message on the NERC crc.nerc.com web page. Permanent Book of Flowgates changes will be posted separately.

3. TEMPORARY FLOWGATES will expire either at the time of the next model update, by default, or on the End Date and Time entered in the IDC, not to exceed ninety days, by the RELIABILITY COORDINATOR who created the TEMPORARY FLOWATE.. IDC base cases are normally updated on a monthly basis. The IDC model updating process schedule will be posted on the NERC web site as it becomes known.

4. TEMPORARY FLOWGATES, which are used for TLR greater that Level 1, should go through a DFWG review. Individual RELIABILITY COORDINATORS may recommend converting a TEMPORARY FLOWGATE into a PERMANENT FLOWGATE by following Step 3 in the PERMANENT FLOWGATES section above.



Informational Flowgates 1. RELIABILITY COORDINATORS may establish an INFORMATIONAL FLOWGATE to help them

monitor power flows over certain interfaces.

2. The RELIABILITY COORDINATOR establishing the INFORMATIONAL FLOWGATE will review the flowgate periodically, and remove the flowgate if no longer needed.

3. INFORMATIONAL FLOWGATES are included in the Book of Flowgates that is posted on the NERC web site.

4. INFORMATIONAL FLOWGATES may be converted to Reliability Flowgates by going through the formal recommendation process.

DFWG Flowgate Review RELIABILITY COORDINATORS may request the DFWG to review and revise the list of PERMANENT FLOWGATES in accordance with the guidelines detailed in Section B. A standardized approach should be used for reviewing all flowgates. The Book of Flowgates will be kept up to date so that it is consistent with the latest IDC base case. The DFWG will generally not review TEMPORARY FLOWGATES unless:

• They are used for a TLR greater than Level 1.

• A flowgate is repeatedly created as a Temporary Flowgate.

• A request is made to convert a Temporary Flowgate to a Permanent Flowgate.

INFORMATIONAL FLOWGATES are not to be used for TLR. The review for INFORMATIONAL FLOWGATES may differ from that of a Reliability Flowgate. DFWG review of Reliability Flowgates for thermal purposes may differ from the review of Reliability Flowgates used for voltage or dynamic stability purposes. Flowgate review may require the responsible RELIABILITY COORDINATOR to provide additional flowgate detail as determined by the DFWG.


Item 18. Next Meetings OC Meetings in 2008

June 4, 2008

June 5, 2008

1 p.m. – 5 p.m.

8 a.m. – 12 p.m.

Toronto (Location subject to change)

September 10, 2008

September 11, 2008

1 p.m. – 5 p.m.

8 a.m. – 12 p.m.

Portland or Seattle

December 3, 2008

December 4, 2008

1 p.m. – 5 p.m.

8 a.m. – 12 p.m.

Orlando (Location subject to change)