nerc highlights and minutes/…translate this page%pdf-1.6 %âãÏÓ 1168 0 obj > endobj 1278 0...

Agenda Standards Committee Meeting December 6, 2017 | 10:00 a.m. to 3:00 p.m. Eastern Dial-in: 1-415-655-0002 | Access Code: 857 944 441 | Meeting Password: 120617 Click here for: WebEx Access Introduction and Chair’s Remarks NERC Antitrust Compliance Guidelines and Public Announcement* Agenda Items

1. Review December 6 Agenda ― (Approve) (B. Murphy) (1 minute)

2. Consent Agenda ― (Approve) (B. Murphy) (1 minute)

a. October 18, 2017 Standards Committee Meeting Minutes* ― (Approve)

b. Standards Committee Executive Committee Election* ― (Approve)

c. Standards Committee Annual Accomplishments* ― (Approve)

3. Upcoming Standards Projects or Issues ― (Update)

a. Three-Month Outlook* (H. Gugel; B. Murphy) (10 minutes)

4. Projects Under Development ― (Review)

a. Project Tracking Spreadsheet (C. Yeung) (5 minutes)

b. Projected Posting Schedule (H. Gugel) (5 minutes)

5. Project 2017-02 Modifications to Personnel Performance, Training, and Qualifications Standards* ― (Accept) (S. Kim) (10 minutes)

6. Consultants on Standards Drafting Teams* ― (Authorize) (B. Murphy) (10 minutes)

7. 2018-2020 Standards Committee Strategic Plan* ― (Approve) (A. Gallo) (10 minutes)

8. Definition Development Procedure* ― (Approve) (B. Li) (10 minutes)

9. Standard Drafting Team Scope* ― (Approve) (B. Li) (10 minutes)

10. Functional Model Advisory Group Scope-of-Work* ― (Approve) (J. Cyrulewski; B. Murphy) (10 minutes)

11. Subcommittee Reports and Updates

https://nerc.webex.com/nerc/onstage/g.php?MTID=e419cc7a720f1c338a723e235fc4a8064

https://nerc.webex.com/nerc/j.php?MTID=m0900beb27538f0faf87834e50bb70a64

http://www.nerc.com/comm/SC/Project%20Management%20and%20Oversight%20Subcommittee%20DL/Project%20Tracking%20Spreadsheet.xlsx

http://www.nerc.com/pa/Stand/Documents/Projected_Posting_Schedule.pdf

Agenda - Standards Committee Meeting | December 6, 2017 2

a. Project Management and Oversight Subcommittee ― (Update) (C. Yeung) (5 minutes)

b. Process Subcommittee* ― (Update) (B. Li) (5 minutes)

12. Legal Update and Upcoming Standards Filings* ― (Review) (S. Elstein) (5 minutes)

13. Informational Items ― (Enclosed)

a. Standards Committee Expectations*

b. 2017 Meeting Dates and Locations*

c. 2017 Standards Committee Roster*

d. Highlights of Parliamentary Procedure*

14. Adjournment

*Background materials included.

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.

• Discussions concerning the exclusion of competitors from markets.

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

NERC Antitrust Compliance Guidelines 2

• 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.

Public Announcements

REMINDER FOR USE AT BEGINNING OF MEETINGS AND CONFERENCE CALLS THAT HAVE BEENPUBLICLY NOTICED AND ARE OPEN TO THE PUBLIC

For face-to-face meeting, with dial-in capability:Participants are reminded that this meeting is public. Notice of the meeting was posted on the NERCwebsite and widely distributed. The notice included the number for dial-in participation. Participantsshould keep in mind that the audience may include members of the press and representatives ofvarious governmental authorities, in addition to the expected participation by industry stakeholders.

Minutes Standards Committee Conference Call October 18, 2017 | 1:00 to 4:00 p.m. Eastern B. Murphy, chair, called the meeting of the Standards Committee (SC or the Committee) to order on October 18, 2017, at 1:00 p.m. Eastern. After the roll call by C. Larson, secretary, meeting quorum was declared. The SC member attendance and proxy sheet is attached hereto as Attachment 1. NERC Antitrust Compliance Guidelines and Public Announcement Committee Secretary called attention to the NERC Antitrust Compliance Guidelines and the public meeting notice. He asked that any questions regarding the NERC Antitrust Compliance Guidelines be directed to NERC’s General Counsel, Charles Berardesco. Introduction and Chair’s Remarks B. Murphy welcomed the Committee and guests. H. Gugel announced S. Noess’ new role at NERC and that S. Cavote has left NERC.

Review October 18, 2017 Agenda (agenda item 1) Approved by unanimous consent with agenda item #10 being struck.

Consent Agenda (agenda item 2) Motion to adopt September 7, 2017 Standards Committee Meeting Minutes

Approved by unanimous consent. Motion to endorse minor corrective changes to the 2018-2020 Reliability Standards Development Plan (RSDP).

Approved by unanimous consent. Upcoming Standards Projects or Issues (agenda item 3) S. Noess provided highlights of the Three-Month Outlook. There were no questions from members or observers. Projects Under Development (agenda item 4) C. Yeung reviewed the Project Tracking Spreadsheet. Based on the current project schedule, G. Zito raised a concern about the timing of some ballot and comment periods, including periodic reviews, and asked that Project Management and Oversight Subcommittee coordinate with the teams to ensure there was efficient posting of projects.

S. Noess reviewed the (Projected Posting Schedule.

Agenda Item 2a Standards Committee December 6, 2017

http://www.nerc.com/comm/SC/_layouts/xlviewer.aspx?id=/comm/SC/Project%20Management%20and%20Oversight%20Subcommittee%20DL/Project%20Tracking%20Spreadsheet.xlsx&Source=http%3A%2F%2Fwww%2Eqa%2Enerc%2Ecom%2Fcomm%2FSC%2FProject%2520Management%2520and%2520Oversi




http://www.nerc.com/pa/Stand/Documents/Projected_Posting_Schedule.pdf

Minutes - Standards Committee Conference Call | October 18, 2017 2

Standard Authorization Request for BAL-003-1.1 (agenda item 5) S. Bodkin made a motion to accept the action item as written; R. Crissman seconded. R. Blohm asked a clarifying question about the Standard Authorization Request (SAR) and associated drafting team, which B. Murphy explained. The motion was as follows:

Authorize:

1. The posting of BAL-003-1.1 Standard Authorization Request (SAR), and assign the SAR to Project 2017-01 Modifications to BAL-003-1.1; and 2. The SAR drafting team, nominated to address the NERC Resource Subcommittee SAR on BAL-003-1.1, to review comments received from this posting and develop one combined SAR that would be reviewed and authorized to be posted by the SC.

The Committee approved the motion with no objections or abstentions.

Project 2017-01 Modifications to BAL-003-1.1 (agenda item 6) G. Zito made a motion to accept the action item as written; R. Crissman seconded. D. Kiguel recommended making it visually easier to compare the list of candidates versus nominees. B. Murphy committed to D. Kiguel to work with NERC staff to ensure uniform format on the presentation of candidates, consistent with past practices. B. Hampton stated that depending upon the content and proposed applicability of the combined SAR, the SC might consider augmenting the standard drafting team (SDT) with additional expertise associated with generation at a future date. The motion was as follows:

Appoint Project 2017-01 BAL-003-1.1 Standard Authorization Request drafting team, as recommended by NERC staff. The Committee approved the motion with no objections and R. Blohm abstaining. The following SAR drafting team members were appointed:

• David Lemmons, chair, Ethos Energy Group

• Rich Hydzik, vice chair, Avista

• Thomas V. Pruitt, Duke Energy

• Greg Park, Northwest Power Pool

• Danielle Croop, PJM Interconnection

• Terry Bilke, MISO

• Daniel Baker, Southwest Power Pool


• Sandip Sharma, ERCOT

Project 2017-06 Modifications to BAL-002-2 (agenda item 7) S. Rueckert made a motion to accept the action item as written; B. Hampton seconded. The motion was as follows:

Appoint Project 2017-06 BAL-002-2 Standard Authorization Request (SAR) drafting team, as recommended by NERC staff. The Committee approved the motion with no objections and R. Blohm abstaining. The following SAR drafting team members were appointed:

• Jerry Rust, chair, Northwest Power Pool

• Glenn Stephens, vice chair, Santee Cooper

• Gerry Beckerle, Ameren

• Natika Mago, Electric Reliability Council of Texas

• Mark Prosperi-Porta, BC Hydro

• Lonnie L Lindekugel, Southwest Power Pool

• David Kimmel, PJM Interconnection

• Sean Erickson, WAPA

Project 2017-07 Standards Alignment with Registration (agenda item 8) C. Gowder made a motion to accept the action item while adding Candidate #6 as vice chair and adding Candidate #7; S. Bodkin seconded. SC members discussed the involvement and precedent of having consultants as SDT members. B. Hampton suggested discussing this topic in more depth at the December SC Meeting. B. Murphy committed to work with NERC staff on the one-pager for the December SC meeting so that the SC could discuss the role of consultants in Standards development process. The motion was as follows:

Appoint Project 2017-07 Standards Alignment with Registration Standard Authorization Request (SAR) drafting team, as recommended by NERC staff. The Committee approved the amended motion with L. Lee, R. Crissman, R. Blohm, D. Kiguel, and G. Zito objecting. The following SAR drafting team members were appointed:

• Stephen D. Wendling, chair, American Transmission Company

• Mark Atkins, vice chair, AESI


• Betty J. Deans, CLECO Corporate Holdings LLC

• Janelle Marriott Gill, Tri-State Generation and Transmission Association, Inc.

• Shannon V. Mickens, Southwest Power Pool

• Leslie Williams, ERCOT

• Jill Loewer, Utility Services, Inc.

Project 2013-03 Geomagnetic Disturbance Mitigation (agenda item 9) G. Zito made a motion to accept the action item as written; A. Gallo seconded. The motion was as follows:

Determine that the proposed modifications to the Implementation Plan for Reliability Standard TPL-007-2 do not constitute “substantive” revisions within the scope of Section 4.14 of the Standard Processes Manual (Appendix 3A of the NERC Rules of Procedure (“ROP”)).

The Committee approved the motion with no objections or abstentions.

Project 2016-04 Modifications to PRC-025-1 (agenda item 10) Per the consent agenda, this agenda item was struck. Quality Review Process (agenda item 11) S. Kim shared the Quality Review Process with the SC members. B. Murphy highlighted that industry can participate as Quality Review volunteers via the website. R. Crissman suggested soliciting for Quality Review volunteers at Regional Workshops and S. Bodkin suggested adding a similar note to the Standards Bulletin. Subcommittee Reports and Updates (agenda item 12)

Project Management and Oversight Subcommittee C. Yeung provided an update of Project Management and Oversight Subcommittee activities. There were no comments or questions from the SC or observers.

Process Subcommittee B. Li provided an update of Standards Committee Process Subcommittee work activities. R. Crissman noted the Standards Committee Process Subcommittee officer nominations will open soon.

Legal Update (agenda item 15) S. Elstein provided the legal update regarding recent and upcoming standards filings.


Informational Items (agenda item 16) R. Crissman asked about a brief update regarding the Standards Efficiency Review. H. Gugel stated the team has been formed and had drafted an initial scope of work. B. Murphy committed to work with NERC staff to add the Standards Efficiency Review as a standing item at future SC meetings. Adjournment B. Murphy thanked the Committee members and observers, and adjourned the meeting at 2:18 p.m. Eastern.

Attachment 1

Segment and Term Representative Organization Proxy Present (Member or

Proxy)

Chair 2016‐17

Brian Murphy Senior

NextEra Energy, Inc. Yes

Vice‐Chair 2016‐17

Michelle D’Antuono

Occidental Energy Ventures, LLC Yes

Segment 1‐2016‐17 Laura Lee Manager of ERO Support and Event Analysis, System Operations

Duke Energy Yes

Segment 1‐2017‐18 Sean Bodkin NERC Compliance Policy Manager

Dominion Resources Services, Inc.

Yes

Segment 2‐2016‐17 Ben Li Consultant

Independent Electric System Operator

Yes

Segment 2‐2017‐18 Charles Yeung Executive Director Interregional Affairs

Southwest Power Pool Yes

Segment 3‐2016‐17 VACANT


Segment 4‐2016‐17 Chris Gowder Regulatory Compliance Specialist

Florida Municipal Power Agency Yes

Segment 4‐2017‐18 Barry Lawson Associate Director,

National Rural Electric Cooperative Association

Yes

Segment 5‐2016‐17 Randy Crissman Vice President – Technical

New York Power Authority Yes

Segment 5‐2017‐18 Amy Casuscelli Sr. Reliability Standards Analyst

Xcel Energy Yes

Standards Committee Attendance – October 18, 2017

Segment and Term Representative Organization Proxy Present (Member or

Proxy)

Segment 6‐2016‐17 Andrew Gallo Director, Reliability Compliance

City of Austin dba Austin Energy

Yes

Segment 6‐2017‐18 Brenda Hampton Regulatory Policy

Vistra Energy – Luminant Energy Company LLC

Yes

Segment 7‐2016‐17 Frank McElvain Senior Manager, Consulting

Siemens Power Technologies International

No


Segment 8‐2016‐17 Robert Blohm Managing Director

Keen Resources Ltd. Yes

Segment 8‐2017‐18 David Kiguel Independent Yes

Segment 9‐2016‐17 Alexander Vedvik Senior Electrical Engineer

Public Service Commission of Wisconsin

Yes

Segment 9‐2017‐18 Michael Marchand Senior Policy Analyst

Arkansas Public Service Commission

Yes

Segment 10‐2016‐17 Guy Zito Assistant Vice President of Standards

Northeast Power Coordinating Council

Yes

Segment 10‐2017‐18 Steven Rueckert Director of Standards

Western Electricity Coordinating Council

Yes

Standards Committee Attendance – October 18, 2017

Agenda Item 2b Standards Committee December 6, 2017

Standard Committee Executive Committee Elections

Action Approve the following approach to elect the three at‐large Standards Committee Executive Committee (SCEC) members: The secretary of the Standards Committee (SC) shall request, via email, no later than December 12, 2017, that any member of the 2017 SC who is interested in running for one of the three 2018 at‐large SCEC seats contact the SC secretary no later than January 4, 2018 and provide a brief, written statement on his or her interest in serving on the SCEC. The SC secretary shall provide the SC with the list of nominees and their statements by January 5, 2018. The SCEC at‐large election, including any run‐offs, will be conducted in the following manner:

At the start of the January 17, 2018 SC conference call, the SC secretary will request that SC members vote within the first hour of the call via email or other specified electronic means. If a run‐off election is needed, the SC secretary will notify the SC during the call and request that SC members provide their votes via email or other specified electronic means. Results, including vote totals, will be announced before the meeting is adjourned and included in the SC meeting minutes.

Each SC member may cast a vote for up to three of the SCEC nominees. The three nominees with the highest number of votes and a simple majority of the SC members’ votes will be elected as at‐large members of the SCEC. The SC chair and vice chair have the right to vote in the election. If necessary, run‐off elections will be conducted until three nominees have each received a simple majority vote of SC members.

Background Pursuant to Section 7 of the SC Charter, the Committee shall have an Executive Committee that consists of five members, including the Committee officers and three at‐large members, elected by the SC. The three at‐large members cannot represent the same industry segments that the Committee officers previously represented, nor can two of the at‐large members be from the same segment. The Executive Committee will be elected annually at the January SC meeting. The SC used the above process for the 2017 SCEC elections.

Agenda Item 2c Standards Committee December 6, 2017

2017 Standards Committee Accomplishments

Action Endorse the following Standards Committee Executive Committee (SCEC) determination on the Standards Committee (SC) 2017 accomplishments:

• Implementation of Periodic Review? (task 1) – Yes

• Standards Grading for 2017? (task 2) – Yes

• Draft policy on Guidelines and Technical Basis? (task 3) – Yes

• Standards Committee Process Subcommittee completion of all on-going tasks? (task 4) – No, tasks to continue in 2018

• Conduct a review of 2017-2019 Strategic Work Plan? (task 5) – Yes, as of Dec 6, 2017

• SCEC evaluate the need for additional reforms or enhancements to the SC Charter? (task 5) – Yes

Background The 2017-2019 Standards Committee Strategic Plan required that the SC “develop metrics and a self-evaluation process to assess its annual accomplishments.” The Action Item requires the SCEC to review each of the annual required tasks and provide the results of whether the SC accomplished each of the required tasks at the December 2017 meeting. Consistent with the review of the Strategic Plan at the end of 2016, the SCEC used a binary self-evaluation process to assess the SC 2017 accomplishments and present for SC endorsement in its December 2017 meeting, the results. The SCEC agreed on the above evaluations.

Three-Month Outlook

Brian Murphy, SC Chair, NextEra Energy Resources, LLCHoward Gugel, Senior Director of Standards and Education, NERCStandards Committee November 27, 2017

Agenda Item 3aStandards CommitteeDecember 6, 2017

RELIABILITY | ACCOUNTABILITY2

• December None

• January None

• February None

Authorize Nomination Solicitations


• December Project 2017-02 Modifications to Personnel Performance, Training, and

Qualifications Standards (PER-003, PER-004)

• January None

• February None

Authorize Team Appointments


• December Project 2017-02 Modifications to Personnel Performance, Training, and

Qualifications Standards (PER-003, PER-004)

• January None

• February Project 2017-06 Modifications to BAL-002-2

Accept/Authorize SAR Postings


• December None

• January Project 2017-02 Modifications to Personnel Performance, Training, and

Qualifications Standards (PER-003, PER-004) Project 2017-04 Periodic Review of Interchange Scheduling and

Coordination Standards (INT-004, INT-006, INT-009, INT-010)

• February None

Authorize Initial Postings


• October Letter Order approving revisions to VRFs for BAL-002-2 Letter Order approving regional Reliability Standard BAL-502-RF-03 Letter Order approving regional Reliability Standard PRC-006-SERC-02 Order No. 830 on Geomagnetic Disturbance Research Work Plan NOPR to approve Reliability Standard CIP-003-7

• November NOPR to approve Reliability Standards PRC-027-1 and PER-006-1

FERC Orders and NOPRs


• Standards Efficiency Review (SER) Advisory Group of industry leaders met multiple times to create a scope and approach document

• Nominations for three SER Working Teams open until November 30, cross-section of skills and backgrounds

• Working Teams will be finalized shortly to begin work on identifying recommendations for retirement or modification

Standards Efficiency Review

Agenda Item 5 Standards Committee December 6, 2017

Project 2017-02 Modifications to Personnel Performance, Training, and

Qualifications Standards Action Accept the PER-003-1 and PER-004-2 Standard Authorization Request (SAR) for final posting. Appoint the Project 2017-02 SAR drafting team (SAR DT) as the standard drafting team for the standard development process. Background In September 2016 the Project 2016-EPR-01 PER Enhanced PRT began their review of the Personnel Performance, Training, and Qualifications (PER) standards. The project reviewed Reliability Standards PER-001-0.2, PER-003-1, and PER-004-2. As part of its review, the PRT referenced the following background documents: 1) the currently-enforceable PER-001-0.2, PER-003-1, and PER-004-2 standards; 2) outstanding issues and directives pertaining to the aforementioned standards; 3) the Independent Experts Report; and 4) Paragraph 81 criteria. On June 21, 2017, the SAR DT posted their SAR addressing the aforementioned standards. The SAR DT did not review standard PER-001-0.2 as it was approved to be retired through a different project. The SAR DT reviewed the comments received from the posting and decided to not make any modifications to the SAR. The industry significantly supported the SAR.

Standard Authorization Request Form

NERC welcomes suggestions to improve the reliability of the bulk power system through improved Reliability Standards. Please use this form to submit your request to propose a new or a revision to a NERC Reliability Standard.

Request to propose a new or a revision to a Reliability Standard

Title of Proposed Standard: PER-003-1 Operating Personnel Credentials and PER-004-2 Reliability

Coordination — Staffing

Date Submitted: March 20, 2017

SAR Requester Information

Name: Patti Metro

Organization: Chair - Project 2016-EPR-01 PER

Telephone: (703) 907-5817 Email: [email protected]

SAR Type (Check as many as applicable)

New Standard

Revision to Existing Standard

Withdrawal of Existing Standard

Urgent Action

SAR Information

Industry Need (What is the industry problem this request is trying to solve?):

Need to add clarity to PER-003-1 that explains that the NERC certifications identified in this standard are described in the NERC System Operator Certification Program.

The requirements of PER-004-2 are duplicative with requirements in several other standards that explain in detail the staffing requirements of personnel conducting the Reliability Coordinator function.

When completed, please email this form to:

[email protected]

Agenda Item 5(i) Standards Committee December 6, 2017

http://www.nerc.com/files/PER-003-1.pdf

http://www.nerc.com/pa/Stand/Reliability%20Standards/PER-004-2.pdf

http://www.nerc.com/pa/Stand/Reliability%20Standards/PER-004-2.pdf

mailto:[email protected]

Standard Authorization Request Form 2

SAR Information

Purpose or Goal (How does this request propose to address the problem described above?):

The Project 2016-EPR-01 PER Team recommends that a clarifying footnote be added to PER-003-1 to ensure that stakeholders (now and in the future) understand (i) the connection between the Standard and the Program Manual; and (ii) that the certifications referenced under PER-003-1 are those under the NERC System Operator Certification Program.

The Project 2016-EPR-01 PER Team recommends that PER-004-2 be retired.

Identify the Objectives of the proposed standard’s requirements (What specific reliability deliverables are required to achieve the goal?):

N/A

Brief Description (Provide a paragraph that describes the scope of this standard action.)

The Project 2016-EPR-01 PER team recommends that a clarifying footnote be added to PER-003-1 Requirement R1, R2 and R3 to ensure that stakeholders (now and in the future) understand (i) the connection between the Standard and the Program Manual; and (ii) that the certifications referenced under PER-003-1 are those under the NERC System Operator Certification Program.

The PER-004-2 standard falls within Paragraph 81 Criterion B7, because all of its requirements are redundant with requirements in other FERC-approved reliability standards that are in effect or soon to be effective. It is not necessary or efficient to maintain such duplicative requirements. Specifically, PER-004-2’s requirements are duplicated in standards:

• PER-003-1, R1 • PER-005-2, R2 and R3 • IRO-002-4, R3 and R4 • EOP-004-2, R2 • IRO-008-2, R1, R2, and R4 • IRO-009-2, R1 – R4 • IRO-010-2, R1 – R3 • IRO-014-3, generally • IRO-018-1, R1-R3


SAR Information

Detailed Description (Provide a description of the proposed project with sufficient details for the standard drafting team to execute the SAR. Also provide a justification for the development or revision of the standard, including an assessment of the reliability and market interface impacts of implementing or not implementing the standard action.)

The Project 2016-EPR-01 PER Team recommends that a clarifying footnote be added to PER-003-1 Requirements R1, R2 and R3 to ensure that stakeholders (now and in the future) understand the connection between the Standard and the Program Manual. The PRT suggests for consideration the following language be used for the footnote “The certifications referenced under PER-003-1 are those under the NERC System Operator Certification Program.”

Concerning PER-004-2, the standards is duplicative and all requirements are covered in other reliability standards. Specifically, PER-003-1 R1 states that each Reliability Coordinator shall staff its Real-time operating positions with System Operators who have obtained and maintained a valid NERC Reliability Operator certificate. PER-005-2 R1 states that each Reliability Coordinator shall design, develop, and deliver training to its System Operators based on a list of Bulk Electric System (BES) company specific Real-time reliability-related tasks. Additionally, PER-005-2 R3 states that Reliability Coordinators have to verify that their personnel are capable of performing each of those tasks.

Moreover, in PER-004-2 R1, 24 hours per day, and seven days a week requirements are addressed by several NERC Reliability Standards and Requirements. These requirements cannot be accomplished without an entity having a 24/7 operation. IRO-002-4 R4 (enforceable 4/1/2017) requires that, “Each Reliability Coordinator shall have monitoring systems that provide information utilized by the Reliability Coordinator’s operating personnel…” In addition, IRO-002-4 R3 states that, “Each Reliability Coordinator shall monitor Facilities, the status of Special Protection Systems, and non-BES facilities identified as necessary by the Reliability Coordinator, within its Reliability Coordinator Area and neighboring Reliability Coordinator Areas to identify any System Operating Limit exceedances and to determine any Interconnection Reliability Operating Limit exceedances within its Reliability Coordination Area.” EOP-004-2 covers continuous observation through its reporting timeframes to meet OE-417 for Loss of Monitoring. Additional coverage is ensured through IRO 008-2 R2, “Each Reliability Coordinator shall have a coordinated Operating Plan(s) for next-day operations to address …(SOL) and (IROL) exceedances…” and R4 states, “Each Reliability Coordinator shall ensure that a Real-time Assessment is performed at least once every 30 minutes.” Reinforcing the structure of the 24 hours per day, and seven days per week requirement is carried out by IRO-010-2 R1, requiring that Reliability Coordinator’s maintain documented specifications for the data to perform Operational Planning analyses, Real-time monitoring, and Real-time Assessments. Real-time is defined as, “Present time as opposed to future times,” while Real-time Assessment is defined as “An examination of existing and expected system


SAR Information

conditions, conducted by collecting and reviewing immediately available data.” Using these definitions in the Reliability Standards further confirms that PER-004-2 Requirement 1 is duplicative and non-essential as its content is covered in multiple Reliability Standards.

PER-004-2 Requirement R2 is duplicated in numerous Reliability Standards justifying the need for retirement of this requirement. As described below, the Standards and requirements of IRO-002-4, IRO-008-2, IRO-009-2, IRO-010-2, IRO-014-3, and IRO-018-1 adequately ensure that protocols are in place to allow the Reliability Coordinator operating personnel to have the best available information at all times.

IRO-002-4, R3 states that the Reliability Coordinator shall monitor Facilities and work with neighboring Reliability Coordinator areas to identify SOL and IROL exceedances within its area. In order to ensure compliance with this Standard and Requirement, particular attention must be placed on SOLs, IROLs, and inter-tie facility limits.

IRO-008-2 ensures that the Reliability Coordinator performs analyses and assessments to prevent instability, uncontrolled separation, or cascading. R1, R2, and R4 of this Standard specifically require that an Operational Planning Analysis is performed to:

• assess whether the planned operations for the next-day will exceed SOLs and IROLs within its Wide Area,

• ensure that coordinated plans are developed for the next-day operations to address these exceedances, and

• execute Real-time Assessments at least once every 30 minutes.

To maintain compliance with the IRO-008-2 Standard, the Reliability Coordinator must place particular attention on SOLs and IROLs.

IRO-009-2 builds on IRO-008-2 by ensuring prompt action to prevent or mitigate instances where IROLs are exceeded. Through the Requirements of this Standard, assurances are made that the Reliability Coordinator has one or more Operating Processes, Procedures, or Plans that identify actions to take, or actions to direct others to take, to mitigate the magnitude and duration of an IROL exceedance identified in their Assessments.

IRO-010-2 provides data specifications that affords the Reliability Coordinator the specific data necessary to perform its Operational Planning Analyses, Real-time monitoring, Real-time Assessments


SAR Information

and ensures that a protocol exists to resolve any data conflicts. This Standard ensures that the Reliability Coordinator has the best available information at all times to maintain compliance.

IRO-014-3 ensures that each Reliability Coordinator’s operations are coordinated so that they will not adversely impact other Reliability Coordinator Areas and preserve the reliability benefits of interconnected operations. This Standard again builds on the coordination of the Operational Analyses and Real-time Assessments which requires the Reliability Coordinator to have the best available information at all times to maintain compliance.

IRO-018-1 established three requirements for Real-time monitoring and analysis capabilities to support reliable operations. Real-time monitoring involves observing operating status and operating values in Real-time to ensure awareness of system conditions. Through this Standard, processes and procedures are established for evaluating the quality of Real-time data and to provide assurance that any action taken addresses any data quality issues so that Real-time monitoring and Real-time Assessments performed by the Reliability Coordinator contains the best available information at all times.

Reliability Functions

The Standard will Apply to the Following Functions (Check each one that applies.)

Reliability Coordinator Responsible for the real-time operating reliability of its Reliability Coordinator Area in coordination with its neighboring Reliability Coordinator’s wide area view.

Balancing Authority Integrates resource plans ahead of time, and maintains load-interchange-resource balance within a Balancing Authority Area and supports Interconnection frequency in real time.

Interchange Authority Ensures communication of interchange transactions for reliability evaluation purposes and coordinates implementation of valid and balanced interchange schedules between Balancing Authority Areas.

Planning Coordinator Assesses the longer-term reliability of its Planning Coordinator Area.

Resource Planner Develops a one year plan for the resource adequacy of its specific loads within a Planning Coordinator area.


Reliability Functions

Transmission Planner Develops a one year plan for the reliability of the interconnected Bulk Electric System within its portion of the Planning Coordinator area.

Transmission Service Provider

Administers the transmission tariff and provides transmission services under applicable transmission service agreements (e.g., the pro forma tariff).

Transmission Owner Owns and maintains transmission facilities.

Transmission Operator

Ensures the real-time operating reliability of the transmission assets within a Transmission Operator Area.

Distribution Provider Delivers electrical energy to the end-use customer.

Generator Owner Owns and maintains generation facilities.

Generator Operator Operates generation unit(s) to provide real and reactive power.

Purchasing-Selling Entity

Purchases or sells energy, capacity, and necessary reliability-related services as required.

Market Operator Interface point for reliability functions with commercial functions.

Load-Serving Entity Secures energy and transmission service (and reliability-related services) to serve the end-use customer.

Reliability and Market Interface Principles

Applicable Reliability Principles (Check all that apply).

1. Interconnected bulk power systems shall be planned and operated in a coordinated manner to perform reliably under normal and abnormal conditions as defined in the NERC Standards.

2. The frequency and voltage of interconnected bulk power systems shall be controlled within defined limits through the balancing of real and reactive power supply and demand.

3. Information necessary for the planning and operation of interconnected bulk power systems

shall be made available to those entities responsible for planning and operating the systems reliably.

4. Plans for emergency operation and system restoration of interconnected bulk power systems shall be developed, coordinated, maintained and implemented.

5. Facilities for communication, monitoring and control shall be provided, used and maintained for the reliability of interconnected bulk power systems.


Reliability and Market Interface Principles

6. Personnel responsible for planning and operating interconnected bulk power systems shall be trained, qualified, and have the responsibility and authority to implement actions.

7. The security of the interconnected bulk power systems shall be assessed, monitored and maintained on a wide area basis.

8. Bulk power systems shall be protected from malicious physical or cyber attacks.

Does the proposed Standard comply with all of the following Market Interface Principles?

Enter

(yes/no)

1. A reliability standard shall not give any market participant an unfair competitive advantage.

YES

2. A reliability standard shall neither mandate nor prohibit any specific market structure.

YES

3. A reliability standard shall not preclude market solutions to achieving compliance with that standard.

YES

4. A reliability standard shall not require the public disclosure of commercially sensitive information. All market participants shall have equal opportunity to access commercially non-sensitive information that is required for compliance with reliability standards.

YES

Related Standards

Standard No. Explanation

Related SARs

SAR ID Explanation

N/A


Related SARs

Regional Variances

Region Explanation

ERCOT N/A

FRCC N/A

MRO N/A

NPCC N/A

RFC N/A

SERC N/A

SPP N/A

WECC N/A

Version History

Version Date Owner Change Tracking 1 June 3, 2013 Revised

1 August 29, 2014 Standards Information Staff Updated template

PER-003-2 – Operating Personnel Credentials

Draft PER-003-2 December 2017 Page 1 of 8

Standard Development Timeline

This section is maintained by the drafting team during the development of the standard and will be removed when the standard is adopted by the NERC Board of Trustees (Board). Description of Current Draft This is the first posting of the revised draft standard.

Completed Actions Date

Standards Committee approved Standard Authorization Request (SAR) for posting

June 2017

SAR posted for comment June 21, 2017 through July 24, 2017

Anticipated Actions Date

45-day formal comment period with ballot December 2017 – January 2017

10-day final ballot February 2017

Board adoption May 2017

Agenda Item 5(ii) Standards Committee December 6, 2017



A. Introduction 1. Title: Operating Personnel Credentials

2. Number: PER-003-1

3. Purpose: To ensure that System Operators performing the reliability-related tasks of the Reliability Coordinator, Balancing Authority and Transmission Operator are certified through the NERC System Operator Certification Program when filling a Real-time operating position responsible for control of the Bulk Electric System.

4. Applicability:

4.1. Functional Entities:

4.1.1. Reliability Coordinator

4.1.2. Transmission Operator

4.1.3. Balancing Authority

5. Effective Date: See Implementation Plan for standard PER-003-2.

B. Requirements and Measures R1. Each Reliability Coordinator shall staff its Real-time operating positions performing

Reliability Coordinator reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining a valid NERC Reliability Operator certificate (1)(2): [Risk Factor: High][Time Horizon: Real-time Operations]

1.1. Areas of Competency

1.1.1. Resource and demand balancing

1.1.2. Transmission operations

1.1.3. Emergency preparedness and operations

1.1.4. System operations

1.1.5. Protection and control

1.1.6. Voltage and reactive

1 Non-NERC certified personnel performing any reliability-related task of a real-time operating position must be under the direct supervision of a NERC Certified System Operator stationed at that operating position; the NERC Certified System Operator at that operating position has ultimate responsibility for the performance of the reliability-related tasks. 2 The NERC certificates referenced in this standard pertain to those certificates identified in the NERC System Operator Certification Program Manual.



1.1.7. Interchange scheduling and coordination

1.1.8. Interconnection reliability operations and coordination

M1. Each Reliability Coordinator shall have the following evidence to show that it staffed its Real-time operating positions performing reliability-related tasks with System Operators who have demonstrated the applicable minimum competency by obtaining and maintaining the appropriate, valid NERC certificate:

M1.1 A list of Real-time operating positions.

M1.2 A list of System Operators assigned to its Real-time operating positions.

M1.3 A copy of each of its System Operator’s NERC certificate or NERC certificate number with expiration date which demonstrates compliance with the applicable Areas of Competency.

M1.4 Work schedules, work logs, or other equivalent evidence showing which System Operators were assigned to work in Real-time operating positions.

R2. Each Transmission Operator shall staff its Real-time operating positions performing

Transmission Operator reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining one of the following valid NERC certificates (1)(2): [Risk Factor: High][Time Horizon: Real-time Operations]:







2.2. Certificates

• Reliability Operator

• Balancing, Interchange and Transmission Operator

• Transmission Operator




M2. Each Transmission Operator shall have the following evidence to show that it staffed its Real-time operating positions performing reliability-related tasks with System Operators who have demonstrated the applicable minimum competency by obtaining and maintaining the appropriate, valid NERC certificate:





R3. Each Balancing Authority shall staff its Real-time operating positions performing

Balancing Authority reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining one of the following valid NERC certificates (1)(2): [Risk Factor: High][Time Horizon: Real-time Operations]:


3.1.1. Resources and demand balancing




3.2. Certificates



• Balancing and Interchange Operator

M3. Each Balancing Authority shall have the following evidence to show that it staffed its Real-time operating positions performing reliability-related tasks with System Operators who have demonstrated the applicable minimum competency by obtaining and maintaining the appropriate, valid NERC certificate:








C. Compliance

1. Compliance Monitoring Process

1.1. Compliance Enforcement Authority: “Compliance Enforcement Authority” means NERC or the Regional Entity, or any entity as otherwise designated by an Applicable Governmental Authority, in their respective roles of monitoring and/or enforcing compliance with mandatory and enforceable Reliability Standards in their respective jurisdictions.

1.2. Evidence Retention: The following evidence retention period(s) identify the period of time an entity is required to retain specific evidence to demonstrate compliance. For instances where the evidence retention period specified below is shorter than the time since the last audit, the Compliance Enforcement Authority may ask an entity to provide other evidence to show that it was compliant for the full-time period since the last audit.

The applicable entity shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of time as part of an investigation.

• Each Reliability Coordinator, Transmission Operator and Balancing Authority shall keep data or evidence for three years or since its last compliance audit, whichever time frame is the greatest.

1.3. Compliance Monitoring and Enforcement Program As defined in the NERC Rules of Procedure, “Compliance Monitoring and Enforcement Program” refers to the identification of the processes that will be used to evaluate data or information for the purpose of assessing performance or outcomes with the associated Reliability Standard.



Violation Severity Levels

R # Violation Severity Levels

Lower VSL Moderate VSL High VSL Severe VSL

R1. N/A N/A N/A The Reliability Coordinator failed to staff each Real-time operating position performing Reliability Coordinator reliability-related tasks with a System Operator having a valid NERC certificate as defined in Requirement R1.

R2. N/A N/A N/A The Transmission Operator failed to staff each Real-time operating position performing Transmission Operator reliability-related tasks with a System Operator having a valid NERC certificate as defined in Requirement R2, Part 2.2.

R3. N/A N/A N/A The Balancing Authority failed to staff each Real-time operating position performing Balancing Authority reliability-related tasks with a System Operator having a valid NERC certificate as defined in Requirement R3, Part 3.2.

D. Regional Variances

None.



E. Associated Documents Implementation Plan – Add link



Version History

Version Date Action Change Tracking

0 April 1, 2005 Effective Date New

1 February 17, 2011

Complete revision under Project 2007-04 Revision

1 February 17, 2011

Adopted by Board of Trustees

1 September 15, 2011

FERC Order issued by FERC approving PER-003-1 (effective date of the Order is September 15, 2011)

2 TBD Added footnote to requirements Revision

2 TBD Adopted by Board of Trustees


Draft PER-003-21 DecemberNovember 2017 Page 1 of 8

Standard Development Timeline

This section is maintained by the drafting team during the development of the standard and will be removed when the standard is adopted by the NERC Board of Trustees (Board). Description of Current Draft This is the first posting of the revised draft standard.

Completed Actions Date

Standards Committee approved Standard Authorization Request (SAR) for posting

June 2017

SAR posted for comment June 21, 2017 through July 24, 2017

Anticipated Actions Date

45-day formal comment period with ballot December 2017 – January 2017

10-day final ballot February 2017

Board adoption May 2017

Agenda Item 5(iii) Standards Committee December 6, 2017



A. Introduction 1. Title: Operating Personnel Credentials

2. Number: PER-003-1

3. Purpose: To ensure that System Operators performing the reliability-related tasks of the Reliability Coordinator, Balancing Authority and Transmission Operator are certified through the NERC System Operator Certification Program when filling a Real-time operating position responsible for control of the Bulk Electric System.

4. Applicability:

4.1. Functional Entities:

4.1.1. Reliability Coordinator

4.1.2. Transmission Operator

4.1.3. Balancing Authority

5. Effective Date: See Implementation Plan for standard PER-003-2.In those jurisdictions where regulatory approval is required, this standard shall become effective the first calendar day of the first calendar quarter twelve months after applicable regulatory approval. In those jurisdictions where no regulatory approval is required, this standard shall become effective the first calendar day of the first calendar quarter twelve months after Board of Trustees adoption.

B. Requirements and Measures

R1. Each Reliability Coordinator shall staff its Real-time operating positions performing

Reliability Coordinator reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining a valid NERC Reliability Operator certificate (1)(2 ): [Risk Factor: High][Time Horizon: Real-time Operations]


1.1.1. Resource and demand balancing










1.1.8. Interconnection reliability operations and coordination

M1. Each Reliability Coordinator shall have the following evidence to show that it staffed its Real-time operating positions performing reliability-related tasks with System Operators who have demonstrated the applicable minimum competency by obtaining and maintaining the appropriate, valid NERC certificate:





R2. Each Transmission Operator shall staff its Real-time operating positions performing

Transmission Operator reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining one of the following valid NERC certificates (1)(2): [Risk Factor: High][Time Horizon: Real-time Operations]:







2.2. Certificates







M2. Each Transmission Operator shall have the following evidence to show that it staffed its Real-time operating positions performing reliability-related tasks with System Operators who have demonstrated the applicable minimum competency by obtaining and maintaining the appropriate, valid NERC certificate:





R3. Each Balancing Authority shall staff its Real-time operating positions performing

Balancing Authority reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining one of the following valid NERC certificates (1)(2): [Risk Factor: High][Time Horizon: Real-time Operations]:


3.1.1. Resources and demand balancing




3.2. Certificates



• Balancing and Interchange Operator




M3. Each Balancing Authority shall have the following evidence to show that it staffed its Real-time operating positions performing reliability-related tasks with System Operators who have demonstrated the applicable minimum competency by obtaining and maintaining the appropriate, valid NERC certificate:





C. Compliance

1. Compliance Monitoring Process

1.1. Compliance Enforcement Authority: “Compliance Enforcement Authority” means NERC or the Regional Entity, or any entity as otherwise designated by an Applicable Governmental Authority, in their respective roles of monitoring and/or enforcing compliance with mandatory and enforceable Reliability Standards in their respective jurisdictions.

1.2. Evidence Retention: The following evidence retention period(s) identify the period of time an entity is required to retain specific evidence to demonstrate compliance. For instances where the evidence retention period specified below is shorter than the time since the last audit, the Compliance Enforcement Authority may ask an entity to provide other evidence to show that it was compliant for the full-time period since the last audit.

The applicable entity shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of time as part of an investigation.

• Each Reliability Coordinator, Transmission Operator and Balancing Authority shall keep data or evidence for three years or since its last compliance audit, whichever time frame is the greatest.

1.3. Compliance Monitoring and Enforcement Program As defined in the NERC Rules of Procedure, “Compliance Monitoring and Enforcement Program” refers to the identification of the processes that will be used to evaluate data or information for the purpose of assessing performance or outcomes with the associated Reliability Standard.



Violation Severity Levels

R # Violation Severity Levels

Lower VSL Moderate VSL High VSL Severe VSL

R1. N/A N/A N/A The Reliability Coordinator failed to staff each Real-time operating position performing Reliability Coordinator reliability-related tasks with a System Operator having a valid NERC certificate as defined in Requirement R1.

R2. N/A N/A N/A The Transmission Operator failed to staff each Real-time operating position performing Transmission Operator reliability-related tasks with a System Operator having a valid NERC certificate as defined in Requirement R2, Part 2.2.

R3. N/A N/A N/A The Balancing Authority failed to staff each Real-time operating position performing Balancing Authority reliability-related tasks with a System Operator having a valid NERC certificate as defined in Requirement R3, Part 3.2.

D. Regional Variances

None.



E. Associated Documents Implementation Plan – Add link



Version History

Version Date Action Change Tracking

0 April 1, 2005 Effective Date New

1 February 17, 2011

Complete revision under Project 2007-04 Revision

1 February 17, 2011

Adopted by Board of Trustees

1 September 15, 2011

FERC Order issued by FERC approving PER-003-1 (effective date of the Order is September 15, 2011)

2 TBD Added footnote to requirements Revision

2 TBD Adopted by Board of Trustees

Implementation Plan Project 2017-02 Operating Personnel Credentials Requested Approvals • PER-003-2 Operating Personnel Credentials Requested Retirements • PER-003-1 Operating Personnel Credentials

• PER-004-2 Reliability Coordination - Staffing Applicable Entities • Reliability Coordinator


• Balancing Authority

Effective Date The effective date for proposed Reliability Standard PER-003-2 is provided below: Where approval by an applicable governmental authority is required, Reliability Standard PER-003-2 shall become effective the first day of the first calendar quarter that is six (6) calendar months after the effective date of the applicable governmental authority’s order approving the standards and terms, or as otherwise provided for by the applicable governmental authority. Where approval by an applicable governmental authority is not required, Reliability Standard PER-003-2 shall become effective on the first day of the first calendar quarter that is six (6) calendar months after the date the standards and terms are adopted by the NERC Board of Trustees, or as otherwise provided for in that jurisdiction. Retirement Date Current NERC Reliability Standards The existing standards PER-003-1 and PER-004-2 shall be retired immediately prior to the effective date of the proposed PER-003-2 standard.

Agenda Item 5(iv) Standards Committee December 6, 2017


Consultants on Standard Drafting Teams

Action Endorse approach for the Standards Committee Executive Committee (SCEC) to work with NERC staff to develop guidelines on the appointment of consultants to Standard Authorization Request and standard drafting teams, and provide the guidelines for Standards Committee endorsement at the March 2018 Standards Committee meeting. Background Standards Committee members have requested to discuss and develop guidance on the appointment of consultants to Standard Authorization Request and standard drafting teams.


Standards Committee 2018-2020 Strategic Work Plan

Action Approve the Standards Committee (SC) 2018-2020 Strategic Work Plan.

Background The draft SC 2018-2020 Strategic Work Plan was provided for comment to the SC and NERC staff from November 15 to November 24, 2017. Based on the comments submitted, a draft plan is attached. Once approved, the plan will be presented to the NERC Board of Trustees for endorsement.

2018-2020 Standards Committee Strategic Work Plan Introduction The 2018-2020 Standards Committee (SC) Strategic Work Plan (Plan) focuses Reliability Standards development activities on: (1) addressing Federal Energy Regulatory Commission (FERC) directives; (2) continuing Periodic Reviews (PRs); and (3) addressing emerging risks using input from the Reliability Issues Steering Committee (RISC). The SC will continue: (i) providing oversight for Reliability Standards grading activities evaluating Reliability Standards for quality and content; and (ii) prioritizing Reliability Standards development activities. Emerging Risks Through input by a NERC technical committee, the RISC, or a governmental authority (such as FERC), the SC develops new or revised Reliability Standards, as appropriate. Vision, Mission and Guiding Principles Vision A comprehensive body of Reliability Standards collectively helping achieve an adequate level of reliability and promote reliable operation of the North American bulk power system. Mission For the SC to effectively manage and oversee development of a comprehensive set of Reliability Standards aligned with NERC’s strategic goals through open and inclusive processes and procedures. Guiding Principles

• Consistent with the 2017-2019 Reliability Standards Development Plan (RSDP), this Plan recognizes the transition of a Reliability Standard development process addressing a small number of FERC directives, PRs, and emerging risks. The details of the goals and objectives for 2017-2019 appear in the RSDP.

• SC continues to promote and implement a collaborative working environment with other NERC Standing Committees, NERC Standards staff, stakeholders, and standard drafting teams.

• SC continues to execute the Reliability Standards development process for effective and efficient use of NERC and industry resources.

• SC continues to promote and take a leadership role on consensus-building activities.


2018-2020 Standards Strategic Word Plan 2

Work Plan Task No. 1 – Periodic Reviews

• Project Management and Oversight Subcommittee and NERC staff work together to prioritize and schedule 2017 PRs for SC endorsement. Project Management and Oversight Subcommittee will use the 2016 PR Standing Team’s grading of Reliability Standards in that prioritization/scheduling by the end of February 2018.

Task No. 2 – Standards Grading

• NERC staff and the SC chair or delegate (acting in the capacity of Standing Team facilitator) will start the 2018 Reliability Standards grading as soon as practicable to provide time to conduct and comment on the grading. NERC staff will present Reliability Standard grades to the SC as an attachment to the RSDP and ask the SC to endorse the process adopted for the grading of Standards.1

• To be completed by June 2018 if possible, but no later than the end of August 2018 to coordinate

with the development of the 2019-2021 RSDP. Task No. 3 – Guidelines and Technical Basis

• The Technical Rationale Advisory Group (TRAG) will draft a project plan and, if necessary, draft revisions to the NERC Standard Processes Manual (SPM). Technical Rationale documents are developed as a technically sound basis to promote an understanding of a Reliability Standard’s requirements. Technical Rationale documents will not serve as Compliance Monitoring and Enforcement Program (CMEP) Implementation Guidance. The TRAG will provide a draft project plan and, if necessary, revisions to the SPM for SC endorsement by March 2018.

Task No. 4 – Standards Committee Process Subcommittee

• NERC staff and the Standards Committee Process Subcommittee will endeavor to complete all on-going projects and seek SC endorsement, with a priority on changes to Sections 6, 7, and 11 of the SPM by December 2018. This target for completion does not apply to new tasks added in 2018.

Task No. 5 – Fourth Quarter Review of SC 2018-2020 Strategic Work Plan

• The SC will conduct a review of this Plan and provide changes for 2019-2021 to the SC for endorsement.

• The SC Executive Committee (SCEC) shall evaluate the need for additional revisions to the SC Charter and provide proposed changes (if any) to the SC for endorsement by the end of December 2018.

1 The SC endorsed the process for the grading of Standards at its 2016 March meeting.

2018-2020 Standards Strategic Word Plan 3

Task No. 6 – Standards Efficiency Review

• The SC will support the evaluation of NERC Reliability Standards to identify potential efficiencies through retirement or modification of particular requirements. This project seeks to identify potential candidate requirements that are not necessary to maintain an adequate level of reliability and could reduce regulatory obligation.


Standards Committee Resource Document Definition Development Procedure

Action Approve retiring the Standards Committee’s Definition Development Procedure document as all of its content is adequately represented in other NERC documents. Background In 2016, the Standards Committee approved a Resource Document Matrix developed by the Standards Committee Process Subcommittee (SCPS). The Matrix provides information about each resource document that is developed and maintained by the Standards Committee, the most recent revised date of each document, suggested review frequency, ownership, and the party responsible for the periodic review and updating of each document

In accordance with the proposed review schedule, and consistent with the SCPS charter, the SCPS has completed a review of the Definition Development Procedure document. The review results suggest that:

• All relevant and consequential content in the Definition Development Procedure is adequately represented in the Standard Processes Manual and Standards Drafting Team Reference Manual.

• The Request for the Development of a Definition form in the Definition Development Procedure document is redundant to the SAR request form.

• There are references in the procedure that do not replicate the Standard Processes Manual, but are not activities that are occurring or add value to the process.

• The document referenced in the industry resource section of the NERC website contains NERC staff administrative tasks that are not relevant to industry in a procedure document; as such, the reference to this document can be removed.

Summary In brief, the SCPS recommends retiring the Definition Development Procedure document with no further action taken on any content contained in the document.


Standards Committee Resource Document Standard Drafting Team Scope

Action Approve the attached revised Standard Drafting Team Scope document. Background In 2016, the Standards Committee approved a Resource Document Matrix developed by the Standards Committee Process Subcommittee (SCPS). The Matrix provides information about each resource document that is developed and maintained by the Standards Committee, the most recent revised date of each document, suggested review frequency, ownership, and the party responsible for the periodic review and updating of each document.

In accordance with the proposed review schedule, and consistent with the SCPS charter, the SCPS has completed a review of the Standard Drafting Team Scope document. The review results indicate that the document is still applicable, but some minor changes need to be made to achieve consistency with terms defined in the NERC Glossary and other NERC documents. Summary In brief, the SCPS recommends approving the attached Standard Drafting Team Scope document for use until the next review cycle.

Standard Drafting Team Scope December 6, 2017 1

Standard Drafting Team Scope Purpose The purpose of a standard drafting team (SDT) is to develop a standards-related product as directed by the Standards Committee (SC). The product that is developed is typically a new or revised Reliability Standard, but could also be a definition, a reference document, a set of Violation Risk Factors, a set of Violation Severity levels, or the team could be appointed to assist an author in refining a Standard Authorization Request (SAR). While the Standard Processes Manual indicates that SARs limited to addressing a regulatory directive or implementing revisions that have had some vetting in the industry will be posted without a formal comment period, the process does allow any interested person to submit a SAR at any time. If a SAR is submitted and proposes a new standard, then the SC will appoint a standard drafting team to work with the staff to help industry reach consensus on the reliability-related need for the new or revised Reliability Standard, and the scope of that new or revised Reliability Standard. If an SDT is assigned to work on a SAR, the SDT will:

• Assist in the development or refinement of a SAR with the SAR’s author;

• Participate in industry forums to help build industry consensus on the SAR;

• Consider and respond to comments and attempt to resolve objections;

• Identify and consider potential regional variances to be incorporated in the proposed new or revised standard;

• Provide advice on the decision to continue with the development of a SAR; and

• Report progress to the SC. If the SC appoints a SDT to work on a SAR and that SAR is authorized to move forward to develop a new or revised standard, then the same SDT appointed to refine the SAR will also work on the development of the associated new or revised standard. Each SDT develops the technical language of a new or revised Reliability Standard. Each Reliability Standard must be technically correct, must be within the scope of the associated SAR, must meet the criteria identified for regulatory approval, and must reflect the comments submitted by electricity industry participants so that the standard is based on the consensus of the electric industry. Standard drafting teams may also develop, or request to have developed, documents to support Reliability Standards. The SDT will:



• Participate in industry forums to help build industry consensus on the standard;

• Gather informal feedback on preliminary draft documents;

• Post information gathered through informal processes, along with a summary of how the information is used;

• Consider and respond to posted comments;

• Develop an implementation plan for the standard;

• Assist in the determination of the need for field testing;

• Determine when a Reliability Standard is ready for balloting;

• Submit the standard to standards staff for a quality review;

• Take any actions directed by the SC to resolve deficiencies, including revising the standard and submitting a request for a supplemental SAR;

• Identify and consider regional variances to be incorporated into the standard(s);

• Consider and respond to observations of Quality Review teams;

• Report progress to the SC;

• Assist in developing documentation used to obtain governmental approval of the standard(s); and

• Review related rule makings and orders and make recommendations (to the SC and NERC staff) on the acceptability of content in order to permit NERC to make a timely response.

Each SDT stays in place until the later of the following occurs:

• The SAR is rejected or withdrawn.

• The SC approves withdrawal of the standard authorization request upon a request from the SDT.

• The standard is rejected by the ballot pool.

• The standard is adopted by the NERC Board of Trustees (Board) and approved by all governmental authorities that have approval processes.

Under certain circumstances, the SC may disband an SDT even though none of the above have occurred. This may be necessary, for example, if the SC determines it is necessary to curtail work on a project or if an SDT has not been successful in meeting its responsibilities as identified in the Standard Processes Manual. The SC, at the recommendation of the Director of Standards, will officially dissolve the SDT once the conditions above have been met. Reporting


SDTs report to the SC. Each SDT works closely with the NERC staff and the SC. Timing of Standard Drafting Team Formation The SC may appoint a standard drafting team in advance of authorizing the posting of the SAR for the associated project. This allows the leadership of the team to work with the standards staff, the SC, and members of the drafting team in developing a project schedule that works with the work schedules of all those involved and also attempts to meet the project schedule proposed in the latest version of the Reliability Standards Development Plan. Drafting Team Appointments The SC will normally use a public nomination process to populate standard drafting teams. The SC may use another method that results in a team that collectively has the necessary technical expertise and work process skills to meet the objectives of the project. In some situations, an ad hoc team may already be in place with the requisite expertise, competencies, and diversity of views that are necessary to refine the SAR and develop the standard, and additional members may not be needed. In most cases, when an SDT is to be appointed, NERC staff will post a notice on the NERC website, requesting that interested parties complete and submit an SDT nomination form. The Director of Standards will review the list of candidates and forward all nominations along with a recommended slate of nominees to the SC. The recommended slate of nominees will include a recommendation for a chair and a vice chair. The size of the SDT should depend in large part on the scope and complexity of the work that will be assigned to it. Simple, non-controversial changes to a single standard benefit from the efficiencies gained through consideration by a smaller SDT (such as five to seven members). Complex projects that entail changes to multiple standards or development of a controversial, complicated new standard could benefit from a larger team with the capacity to work in subteams, broad subject-matter diversity and depth of knowledge, and the necessary industry outreach. If a project is anticipated to require a greater time commitment, the number of SDT members need to be sufficient to provide continuity as competing demands on members’ time fluctuate. The SC has the responsibility and authority to make the final determination on appointment to SDTs and shall consider each candidate’s technical experience in the specific issue being addressed as well as the ability to work effectively in a group situation. In making appointments, the SC shall consider the following qualifications:

• Verifiable requisite subject matter expertise;

• Representation from as many NERC Regions as possible, with particular consideration given to including each Region with an identified Regional variance. This may consist of any or all of the following;

http://www.nerc.com/pa/Stand/Resources/Documents/Standards_Drafting_Team_Nomination_Form.docx


Technical knowledge of regional criteria (Regional staff and/or NERC staff may verify regional participation, references provided by the candidate in the nomination form, or verify knowledge by other means.)

Operational experience in the region

Asset ownership in the region

• Representation from each Interconnection;

• Representation from any pertinent NERC Standing Committee(s);

• Representation from each of the functional entities expected to have compliance obligations in the proposed standard;

• Representation from Canada and the United States;

• Representation from as many impacted industry segments as possible;

• Prior standard development experience and the number of drafting teams the candidate already represents; and

• Regulatory, legal, and/or compliance expertise. If more than one candidate provides a similar set of qualifications and diversity, preference shall be given to appointing the candidate who:

• Is an employee or agent of an entity in the Registered Ballot Body;

• Has experience, or is familiar with, NERC standards drafting (though not mandatory so as not to limit participation of new members);

• Has proven experience working in a team environment (NERC staff may verify past experience and active participation/performance in NERC or Regional committees, working groups, or task forces).

If the initial pool of nominations does not provide the mix of candidates needed to ensure that there is sufficient technical expertise with diverse views to represent the industry’s viewpoints, additional nominations may be solicited. The SAR author is not a voting member of the SDT unless appointed by the SC. Membership Changes The SC approves all changes to drafting team membership. If a drafting team member cannot complete work on an SDT, that member shall notify the SDT chair and Standards Developer. The Standards Developer shall report the vacancy to the SC with a recommendation on whether to fill the vacancy. Although an SDT’s member organization may offer a replacement for an individual assigned to the team, this choice and change in appointment will not be automatic. The new appointment will be based, in part, on the SDT’s continued need as identified by the chair and the Standards Developer.


When determining whether to appoint drafting team replacements, the SC shall consider the following:

• Whether there is a candidate who has the requisite subject matter expertise and has been an active observer, already receiving drafting team material;

• Whether a candidate has similar expertise as the individual being replaced;

• Whether there are qualified candidates who submitted a formal application for a position on the team but were not appointed; and

• Whether the project schedule includes sufficient work to warrant adding a new drafting team member.

The SC may direct staff to post a request for additional nominations, opening the nomination process to all interested parties. The Standards Developer and chair will keep the SC apprised of the need to make changes to the membership (additions, replacements, dismissals, etc.) to keep an efficient and effective team. If an SDT member does not actively participate in the team activities, NERC staff shall contact the individual to verify his/her degree of commitment and time availability to the work of the team. If the SDT member cannot demonstrate the necessary dedication to developing the standard and devoting the necessary time to the work of the team, the Director of Standards may recommend to the SC the removal of the person in question from the SDT. In those instances when an SDT member may be participating in a way that makes progress difficult by obstructing the work of the team, the SDT chair or the Standards Developer shall first discuss the issue with the individual, and should the issue continue, recommend dismissal of the individual from the SDT to the Director of Standards. The SC may accept or reject a recommendation for dismissal of an SDT member. SDT Chair When making appointments, the SC shall identify a team member to serve as the chair. The SDT chair shall be chosen with due consideration given to the following:

• Level of experience for the proposed standard relative to the other members of the team;

• Level of experience in NERC drafting standards;

• Level of experience as a chair or leading a group;

• Demonstrated ability to work in a group; and

• Potential ability and commitment to remain active on the team until the estimated time of completion.


The SC shall also consider, with input from the selected SDT chair and the coordinator, identifying a vice chair, based on the size of the SDT and the complexity of the standard development or revision. The chair and the NERC Standards Developer are responsible for leading the drafting team in a fair and impartial manner. The chair and Standards Developer report team progress to the SC. Standards Developer The Standards Developer shall be a member of the NERC staff appointed by the Director of Standards, and shall be an impartial, non-voting member of the team. The Standards Developer has overall responsibility for the appearance of team documents submitted for posting, balloting and adoption, records meeting proceedings, and prepares, distributes and posts meeting notes, supports and facilitates SDT activities, and is an impartial, non-voting member of the team, committed to assist in the development of the standard without undue influence on the outcome. The Standards Developer is also responsible for ensuring that the drafting team adheres to the integrity of the standards process. Technical Writer The standards staff may provide an individual to support the team with technical writing expertise, in addition to the Standards Developer. The Technical Writer serves as an advisor to the drafting team and does not have voting rights. In developing the standard, the drafting team members assigned by the SC shall have final authority over the technical details of the standard, while the technical writer shall provide assistance to the drafting team in assuring that the final draft of the standard meets the quality attributes identified in NERC’s Benchmarks for Excellent Standards. This decision authority also applies when the standard drafting team receives legal and/or compliance inputs during standard drafting. Meeting Procedures Open Meetings Meetings of SDTs shall be open to all interested parties. Meeting notices and agendas shall be publicly posted on the NERC website at least five business days prior to the meeting. Notices shall describe the purpose of meetings and shall identify a readily available source for further information. All who wish to attend an SDT meeting must pre-register via the NERC Calendar web page to ensure that there are sufficient resources to accommodate guests and SDT members. http://www.nerc.com/pa/Stand/Pages/Calendar.aspx An observer is any industry individual who wishes to attend a SDT meeting. A guest is a subject matter expert that the SDT may decide to invite to one or more of the SDT meetings to respond to the team’s questions. Invitations to guests shall be extended by the chair or the Standards Developer. The SDT chair is responsible for conducting the meetings in a responsible, timely and efficient manner. The chair may limit the participation of guests and observers to ensure that the SDT accomplishes its

http://www.nerc.com/pa/Stand/Pages/Calendar.aspx


assigned tasks or to permit discussions pertaining to Critical Energy Infrastructure Information (CEII), Cyber Security, or other “sensitive” issues. Such decisions shall be documented in meeting notes. Meeting notes shall be posted no more than five business days following each meeting. Quorum A quorum requires two-thirds of the voting members of the SDT be in attendance participating. Voting While the SDT members are encouraged to arrive at decisions through consensus, on the rare occasions when this is not possible, team members assigned by the SC have the right to vote. Voting may take place during formal meetings or may take place through electronic means. Approval of any action of a SDT through a vote requires a two-thirds majority of the SDT member votes cast. Guests and observers shall not have the right to vote unless an informal straw poll is taken at the request of or by the SDT Chair. Proxies Proxies are not allowed. Schedule When a drafting team begins its work, either in refining a SAR or in developing or revising a proposed standard, the drafting team shall develop a project schedule. If information has been made available about a project’s anticipated schedule prior to drafting team member selection, the drafting team should revise this schedule as necessary, considering the complexity of the project, any regulatory time constraints and the project’s priority. As the project progresses, the drafting team has the responsibility to adhere to the schedule if possible, to provide predictability to the industry and regulators. If this proves impossible, the chair and the coordinator shall update the schedule. The chair and the Standards Developer shall report progress and any schedule adjustments to the SC. Expectations of Members, Guests, and Observers It is expected that all members, guests, and observers attending drafting team meetings adhere to the NERC Reliability Standard Development Procedure. Members and observers are expected to participate in a courteous and professional manner. Each SDT is expected to develop excellent, technically correct standards that provide for bulk power system reliability. The SDT is also expected to address any regulatory directive included in the SAR for the particular project assigned to it. The SDT can address the directive by adopting the technical approach that the regulatory body has specified in the directive or it can propose an alternate, equally effective and efficient approach that affirmatively responds to the concern or goal underlying the directive. The SDT is obligated to document an adequate technical analysis supporting any alternate proposal for use by the industry ballot body, the SC, NERC staff, the Board, and the regulatory body in assessing the alternative. List Server Use


NERC staff will assign each SDT a unique list server. The list server allows drafting team members, and any others on that list, to simultaneously send a message to all members of the SDT. NERC staff will also assign an expanded (SDT-plus) list server to include other interested individuals who are not members of the team (observers, guests, etc.). The drafting team should use the “plus” list as the primary communication tool. The “team only” list should only be used when sensitive information is discussed. The use of an SDT list server is limited to exchange of email relative to the development of the associated SAR, standard, or standards. The use of an SDT list server for any other reason, such as for the exchange of personal information or for the distribution of commercial information, is prohibited. Repeated use of list servers for non-drafting team business may result in the member or observer being removed from the list server.

Version History

Version Date Owner Change Tracking 0 July 13, 2011 NERC (Standards

Committee Endorser)

1 May 16, 2014 NERC (Standards Committee Endorser)

Updated Nomination Form link and template

2 December 6, 2017 NERC (Standards Committee Endorser)

Periodic review with conforming changes incorporated.

1

Standard Drafting Team Scope Purpose The purpose of a standard drafting team (SDT) is to develop a standards-related product as directed by the Standards Committee (SC). The product that is developed is typically a new or revised reliability Reliability standardStandard, but could also be a definition, a reference document, a set of Violation Risk Factors, a set of Violation Severity levels, or the team could be appointed to assist an author in refining a Standard Authorization Request (SAR).

While the Standard Processes Manual indicates that SARs limited to addressing a regulatory directive or implementing revisions that have had some vetting in the industry will be posted without a formal comment period, the process does allow any interested person to submit a SAR at any time. If a SAR is submitted and proposes a new standard, then the SC will appoint a standard drafting team to work with the staff to help industry reach consensus on the reliability-related need for the new or revised reliability Reliability standardStandard, and the scope of that new or revised reliability Reliability standardStandard.

If an SDT is assigned to work on a SAR, the SDT will: • Assist in the development or refinement of a SAR with the SAR’s author • Participate in industry forums to help build industry consensus on the SAR • Consider and respond to comments and attempt to resolve objections • Identify and consider potential regional variances to be incorporated in the proposed new or

revised standard• Provide advice on the decision to continue with the development of a SAR • Report progress to the Standards Committee (SC)

If the Standards CommitteeSC appoints a SDT to work on a SAR and that SAR is authorized to move forward to develop a new or revised standard, then the same SDT appointed to refine the SAR will also work on the development of the associated new or revised standard.

Each SDT develops the technical language of a new or revised reliability Reliability standardStandard. Each reliability Reliability standard Standard must be technically correct, must be within the scope of the associated SAR, must meet the criteria identified for regulatory approval, and must reflect the comments submitted by electricity industry participants so that the standard is based on the consensus of the electric industry. Standard drafting teams may also develop, or request to have developed, documents to support reliability Reliability standardsStandards.

The SDT will: • Participate in industry forums to help build industry consensus on the standard. • Gather informal feedback on preliminary draft documents.

Agenda Item 9(ii) Standards Committee December 6, 2017

2

Formatted: Font: (Default) Arial, 8.5 pt, Font color: Black

Formatted: Indent: Left: 0", Right: 0.01"

• Post information gathered through informal processes, along with a summary of how the information is used

• Consider and respond to posted comments. • Develop an implementation plan for the standard. • Assist in the determination of the need for field testing. • Determine when a reliability Reliability standard Standard is ready for balloting. • Submit the standard to standards staff for a quality review. • Take any actions directed by the Standards CommitteeSC to resolve deficiencies, including

revising the standard and submitting a request for a supplemental SAR • Identify and consider regional variances to be incorporated into the standard(s). • Consider and respond to observations of Quality Review teams. • Report progress to the Standards Committee (SCSC). • Assist in developing documentation used to obtain governmental approval of the standard(s) • Review related rule makings and orders and make recommendations (to the SC and NERC staff) on the acceptability of content in order to permit NERC to make a timely response.

Each SDT stays in place until the later of the following occurs:

• The SAR is rejected or withdrawn • The SC approves withdrawal of the standard authorization request upon a request from the SDT • The standard is rejected by the ballot pool • The standard is adopted by the NERC Board of Trustees (Board); and approved by all governmental

authorities that have approval processes.

Under certain circumstances, the SC may disband an SDT even though none of the above have occurred. This may be necessary, for example, if the SC determines it is necessary to curtail work on a project or if an SDT has not been successful in meeting its responsibilities as identified in the Standard Processes Manual. The SC, at the recommendation of the Director of Standards, will officially dissolve the SDT once the conditions above have been met. Reporting SDTs report to the SC. Each SDT works closely with the NERC staff and the SC. Timing of Standard Drafting Team Formation The SC may appoint a standard drafting team in advance of authorizing the posting of the SAR for the associated project. This allows the leadership of the team to work with the standards staff, the SC, and members of the drafting team in developing a project schedule that works with the work schedules of all those involved and also attempts to meet the project schedule proposed in the latest version of the Reliability Standards Development Plan.

Public

Standard Drafting Team Scope May 16, 2014December 6, 2017 3


Formatted: Centered


Drafting Team Appointments The Standards CommitteeSC will normally use a public nomination process to populate standard drafting teams. The SC may use another method that results in a team that collectively has the necessary technical expertise and work process skills to meet the objectives of the project. In some situations, an ad hoc team may already be in place with the requisite expertise, competencies, and diversity of views that are necessary to refine the SAR and develop the standard and additional members may not be needed. In most cases, when an SDT is to be appointed, NERC staff will post a notice on the NERC website, requesting that interested parties complete and submit an SDT nomination form. The Director of Standards Development will review the list of candidates and forward all nominations along with a recommended slate of nominees to the SC. The recommended slate of nominees will include a recommendation for a chair and a vice chair. The size of the SDT should depend in large part on the scope and complexity of the work that will be assigned to it. Simple, non-controversial changes to a single standard benefit from the efficiencies gained through consideration by a smaller SDT (such as five to seven members). Complex projects that entail changes to multiple standards or development of a controversial, complicated new standard could benefit from a larger team with the capacity to work in subteams, broad subject-matter diversity and depth of knowledge, and the necessary industry outreach. If a project is anticipated to require a greater time commitment, the number of SDT members needs to be sufficient to provide continuity as competing demands on members’ time fluctuate. The SC has the responsibility and authority to make the final determination on appointment to SDTs and shall consider each candidate’s technical experience in the specific issue being addressed as well as the ability to work effectively in a group situation. In making appointments, the SC shall consider the following qualifications:

• Verifiable requisite subject matter expertise; • Representation from as many NERC Regions as possible, with particular consideration given to

including each Region with an identified Regional variance. This may consist of any or all of the following;

o Technical knowledge of regional criteria (Regional staff and/or NERC staff may verify regional participation, references provided by the candidate in the nomination form, or verify knowledge by other means.)

o Operational experience in the region o Asset ownership in the region

• Representation from each Interconnection; • Representation from any pertinent NERC Standing Committee(s);

Field Code Changed

http://www.nerc.com/pa/Stand/Resources/Documents/Standards_Drafting_Team_Nomination_Form.docx

4



• Representation from each of the functional entities expected to have compliance obligations in the proposed standard;

• Representation from Canada and the United States; • Representation from as many impacted industry segments as possible; • Prior standard development experience and the number of drafting teams the candidate already

represents; and • Regulatory, legal and/or compliance expertise.

If more than one candidate provides a similar set of qualifications and diversity, preference shall be given to appointing the candidate who:

• Is an employee or agent of an entity in the Registered Ballot Body; • Has experience, or is familiar with, NERC standards drafting (though not mandatory so as not to

limit participation of new members); • Has proven experience working in a team environment (NERC staff may verify past experience and

active participation/performance in NERC or Regional committees, working groups or task forces). If the initial pool of nominations does not provide the mix of candidates needed to ensure that there is sufficient technical expertise with diverse views to represent the industry’s viewpoints, additional nominations may be solicited. The SAR author is not a voting member of the SDT unless appointed by the SC. Membership Changes The SC approves all changes to drafting team membership. If a drafting team member cannot complete work on an SDT, that member shall notify the SDT chair and coordinator Standards Developer. The coordinator Standards Developer shall report the vacancy to the SC with a recommendation on whether to fill the vacancy. Although an SDT’s member organization may offer a replacement for an individual assigned to the team, this choice and change in appointment will not be automatic. The new appointment will be based, in part, on the SDT’s continued need as identified by the chair and the coordinatorStandards Developer. When determining whether to appoint drafting team replacements, the SC shall consider the following:

• Whether there is a candidate who has the requisite subject matter expertise and has been an active observer, already receiving drafting team material.

• Whether a candidate has similar expertise as the individual being replaced. • Whether there are qualified candidates who submitted a formal application for a position on the

team but were not appointed. • Whether the project schedule includes sufficient work to warrant adding a new drafting team

member.

Public



Formatted: Centered


The SC may direct staff to post a request for additional nominations, opening the nomination process to all interested parties. The coordinator Standards Developer and chair will keep the SC apprised of the need to make changes to the membership (additions, replacements, dismissals, etc.) to keep an efficient and effective team. If an SDT member does not actively participate in the team activities, NERC staff shall contact the individual to verify his/her degree of commitment and time availability to the work of the team. If the SDT member cannot demonstrate the necessary dedication to developing the standard and devoting the necessary time to the work of the team, the Director of Standards Development may recommend to the SC the removal of the person in question from the SDT. In those instances when an SDT member may be participating in a way that makes progress difficult by obstructing the work of the team, the SDT chair or the coordinator Standards Developer shall first discuss the issue with the individual and should the issue continue, recommend dismissal of the individual from the SDT to the Director of Standards. The SC may accept or reject a recommendation for dismissal of an SDT member. SDT Chair When making appointments, the SC shall identify a team member to serve as the chair. The SDT chair shall be chosen with due consideration given to the following:

• Level of experience for the proposed standard relative to the other members of the team. • Level of experience in NERC drafting standards. • Level of experience as a chair or leading a group. • Demonstrated ability to work in a group. • Potential ability and commitment to remain active on the team until the estimated time of

completion. The SC shall also consider, with input from the selected SDT chair and the coordinator, identifying a vice-chair, based on the size of the SDT and the complexity of the standard development or revision. The chair and the NERC coordinator Standards Developer are responsible for leading the drafting team in a fair and impartial manner. The chair and coordinator Standards Developer report team progress to the SC. CoordinatorStandards Developer The coordinator Standards Developer shall be a member of the NERC staff appointed by the Director of Standards Development, and shall be an impartial, non-voting member of the team. The coordinator Standards Developer has overall responsibility for the appearance of team documents submitted for posting, balloting and adoption, records meeting proceedings, and prepares, distributes and posts

6



meeting notes, supports and facilitates SDT activities, and is an impartial, non-voting member of the team, committed to assist in the development the standard without undue influence on the outcome. The coordinator Standards Developer is also responsible for ensuring that the drafting team adheres to the integrity of the standards process. Technical Writer The standards staff may provide an individual to support the team with technical writing expertise, in addition to the coordinatorStandards Developer. The Technical Writer serves as an advisor to the drafting team and does not have voting rights. In developing the standard, the drafting team members assigned by the Standards CommitteeSC shall have final authority over the technical details of the standard, while the technical writer shall provide assistance to the drafting team in assuring that the final draft of the standard meets the quality attributes identified in NERC’s Benchmarks for Excellent Standards. This decision authority also applies when the standard drafting team receives legal and/or compliance inputs during standard drafting. Meeting Procedures Open Meetings Meetings of SDTs shall be open to all interested parties. Meeting notices and agendas shall be publicly posted on the NERC website at least five business days prior to the meeting. Notices shall describe the purpose of meetings and shall identify a readily available source for further information. All who wish to attend an SDT meeting must pre-register via the NERC Meetings Calendar web page to ensure that there are sufficient resources to accommodate guests and SDT members. http://www.nerc.net/meetings/ http://www.nerc.com/pa/Stand/Pages/Calendar.aspx An observer is any industry individual who wishes to attend a SDT meeting. A guest is a subject matter expert that the SDT may decide to invite to one or more of the SDT meetings to respond to the team’s questions. Invitations to guests shall be extended by the chair or the coordinatorStandards Developer. The SDT chair is responsible for conducting the meetings in a responsible, timely and efficient manner. The chair may limit the participation of guests and observers to ensure that the SDT accomplishes its assigned tasks or to permit discussions pertaining to Critical Energy Infrastructure Information (CEII), Cyber Security or other “sensitive” issues. Such decisions shall be documented in meeting notes. Meeting notes shall be posted no more than five business days following each meeting. Quorum A quorum requires two-thirds of the voting members of the SDT be in attendance participating. Voting While the SDT members are encouraged to arrive at decisions through consensus, on the rare occasions when this is not possible, team members assigned by the SC have the right to vote. Voting may take place

http://www.nerc.com/pa/Stand/Pages/Calendar.aspx

Public



Formatted: Centered


during formal meetings or may take place through electronic means. Approval of any action of a SDT through a vote requires a two thirds majority of the SDT member votes cast. Guests and observers shall not have the right to vote unless an informal straw poll is taken at the request of or by the SDT Chair. Proxies Proxies are not allowed. Schedule When a drafting team begins its work, either in refining a SAR or in developing or revising a proposed standard, the drafting team shall develop a project schedule. If information has been made available about a project’s anticipated schedule prior to drafting team member selection, the drafting team should revise this schedule as necessary, considering the complexity of the project, any regulatory time constraints and the project’s priority. As the project progresses, the drafting team has the responsibility to adhere to the schedule if possible, to provide predictability to the industry and regulators. If this proves impossible, the chair and the coordinator shall update the schedule. The chair and the coordinator Standards Developer shall report progress and any schedule adjustments to the Standards CommitteeSC. Expectations of Members, Guests and Observers It is expected that all members, guests and observers attending drafting team meetings adhere to the NERC Reliability Standard Development Procedure. Members and observers are expected to participate in a courteous and professional manner. Each SDT is expected to develop excellent, technically correct standards that provide for bulk power system reliability. The SDT is also expected to address any regulatory directive included in the SAR for the particular project assigned to it. The SDT can address the directive by adopting the technical approach that the regulatory body has specified in the directive or it can propose an alternate, equally effective and efficient approach that affirmatively responds to the concern or goal underlying the directive. The SDT is obligated to document an adequate technical analysis supporting any alternate proposal for use by the industry ballot body, the Standards CommitteeSC, NERC staff, the NERC Board of TrusteesbBoard and the regulatory body in assessing the alternative. List Server Use NERC staff will assign each SDT a unique list server. The list server allows drafting team members, and any others on that list, to simultaneously send a message to all members of the SDT. NERC staff will also assign an expanded (SDT-plus) list server to include other interested individuals who are not members of the team (Observers, Guests, etc.). The drafting team should use the “plus” list as the primary communication tool. The “team only” list should only be used when sensitive information is discussed. The use of an SDT list server is limited to exchange of e-mail relative to the development of the associated SAR, standard or standards. The use of an SDT list server for any other reason, such as for the exchange of personal information or for the distribution of commercial information, is prohibited. Repeated use of

8



list servers for non-drafting team business may result in the member or observer being removed from the list server.

Version History

Version Date Owner Change Tracking 01 July 13, 2011 NERC (Standards

Committee Endorser)

1 May 16, 2014 NERC (Standards Committee Endorser)

Updated Nomination Form link and template

2 February December 6X, 2017

NERC (Standards Committee Endorser)

Periodic review by Standards Committee Process Subcommitteewith conforming and associated changes incorporated.


NERC Functional Model Advisory Group

Scope-of-work

Action Endorse proposed scope-of-work for NERC Functional Model (FM) Advisory Group (FMAG) for 2018.

Background At the July 20, 2016 Standards Committee (SC) meeting, the SC authorized the FMAG to post a revised version of the FM and Functional Model Technical Document (FMTD) reflecting numerous changes to various NERC Reliability Standards, Rules of Procedure (including Appendices), and the Glossary of Terms since the last update of the FM and FMTD. As per the FMAG Scope Document, the FMAG reviewed all functions and made changes in the FM and FMTD “to ensure the model correctly reflects the industry today and evaluates and incorporates new and emergent reliability-related tasks.” The comment period concluded on September 7, 2016 and resulted in a range of comments and recommendations.

The FMAG supports revisions which, at a minimum, address definitions and terms. However, the FMAG performed significant work reviewing functions, especially the planning functions, to bring the model up-to-date. Thus, the FMAG proposes a scope-of-work with two parts and consistent with recommendations made to the Standards Oversight and Technology Committee.

Scope of Work Task 1: Basic Improvement Version 5.1

Continue refining definitions and terms in the FM with all definition and term refinements endorsed by the applicable technical committee (i.e., Operating Committee (OP), Planning Committee (PC), and Critical Infrastructure Protection Committee (CIPC)). Thereafter, the FMAG and NERC staff will provide the proposed refinements to the SC for endorsement and posting for industry comment for no less than 30 days. After industry comment, if NERC receives suggested changes to the proposed definition and term refinements, they shall submit the changes to the applicable technical committee for endorsement prior to bringing them to the SC for endorsement. The FMAG expects to bring its work product to the SC for endorsement in the first or second quarter of 2018.

Task 2: Seek industry consensus on additional revisions to the FM or FMTD

The FMAG identified areas in the FM and FMTD needing updating. The FMAG recognizes NERC needs industry support and consensuses for any changes to the FM. The FMAG proposes providing the applicable context for possible changes and polling the industry on the following question(s) in January 2018, to be included in the comment form for Task 1:

• Does your company see a need for changes to the FM or FMTD at this time beyond those proposed in Task 1?

If yes, specifically identify the changes to the FM or FMTD you recommend and the technical basis for each change.

NERC staff and FMAG leadership shall conduct at least one webinar to present the content and polling questions. Industry representatives shall have no less than 30 days to respond to the polling questions. NERC staff and the FMAG shall present the results of the polling to the OC, PC, and CIPC for input and endorsement of any proposed changes. NERC staff and the FMAG shall present to the SC for endorsement the FMAG’s Scope of Work. The Scope of Work shall only include changes requested by a majority of industry representatives and endorsed by the OC, PC, or CIPC, as applicable.

SCPS Work Plan Activities Document — November 21, 2017

Agenda Item 11b Standards Committee

December 6, 2017

Standards Committee Process Subcommittee Work Plan (SC Endorsed Project Scopes)

Task

General Scope of Task

Task Initiated

Target Completion

Status/Remarks

1. Revisions to NERC Standard Processes Manual (SPM)

a. Section 6: Processes for Conducting Field Tests and Collecting and Analyzing Data

b. Section 7: Process for Developing an Interpretation

c. Section 11.0: Process for Approving Supporting Documents

Team Lead: Pete Heidrich Ben Li Jennifer Flandermeyer Steve Rueckert Chris Gowder Sean Bodkin Linn Oelker Guy Zito (consulting) Lauren Perotti (NERC Legal) Sean Cavote (NERC)

a. Develop and propose recommendations to the SC for revisions and/or modifications to the SC Charter Section 10 and Section 6 of the Standard Processes Manual (SPM), which will address the coordination and oversight involvements of the NERC technical committees.

b. Develop and propose recommendations to the SC for revisions and/or modifications to the Interpretation Process in Section 7 of the SPM which will improve the effectiveness and efficiency of (i) validation of a request for Interpretation (RFI), and (ii) development of an interpretation of an approved Reliability Standard or individual Requirement(s) within an approved Reliability Standard.

c. Develop and propose recommendations to the SC for revisions and/or modifications to the Technical Document Approval Process in Section 11 of the SPM.

July 2015

March 2017 (delayed to early 2018)

Comments received from the first posting of the revised SPM are being reviewed, and responses to be drafted. A verbal report to the SC regarding next steps was been provided at the June 14 SC meeting. Ballot Name: NERC Standard Processes Manual Sections 2.1, 3.7, 6, 7, 8 & 11 IN 1 OT Voting Start Date: 4/24/2017 12:01:00 AM Voting End Date: 5/3/2017 8:00:00 PM Ballot Type: OT Ballot Activity: IN Ballot Series: 1 Total # Votes: 140 Total Ballot Pool: 179 Quorum: 78.21 Weighted Segment Value: 64.72 SCPS is finalizing response to comments and conforming changes to the SPM.

SCPS Work Plan Activities Document— November 21, 2017


Task


Task Initiated

Target Completion

Status/Remarks

2. Review/Revise Periodic Review Assessment Template

Team Lead: Ruida Shu Jennifer Flandermeyer Laura Anderson Sean Bodkin

Review the current version of the periodic review template and revise it as appropriate

May 2017 September 2017, delayed to early 2018

Scope approved by the SC on June 14. SCPS will review and develop a final draft at its December 2017 meeting, in preparation for presentation to the SC for approval at an early 2018 SC meeting.



Task


Task Initiated

Target Completion

Status/Remarks

3. Standing task to review/revise resource documents

Documents to be updated in next 6 months: i. Standard Drafting Team

Scope; Sub-Team: - John Hagen (lead) - Jennifer Flandermeyer - Monica Bales

ii. NERC Glossary of Terms Used in Reliability Standards Definition Development Procedure; Sub-Team: - Chris Scanlon (lead) - John Hagen - Jennifer Flandermeyer

iii. Reliability Standard Quality Review Form Sub-Team Ed Skiba (Lead) Sean Bodkin Soo-in Kim

iv. Three documents are slated for retirement and one is being revised as part of the SPM revisions project: see email for list to insert.

Per the resource document matrix and periodic update process approved by the SC, review the current version of all resource documents and update them as necessary.

Mar 2017 June 2017 TBD

Dec 2017 Dec 2017 Mar 2018

Submitted for SC approval at December 6, 2017 meeting. Submitted for SC approval at December 6, 2017 meeting. Sub-team formed. Plan to have an initial draft by the December SCPS meeting. Documents to be retired after SPM is revised (cont’d): - Approving a Field Test

Associated with a Reliability Standard;



Task


Task Initiated

Target Completion

Status/Remarks

3. Standing task to review/revise resource documents (cont’d)

Documents to be retired after SPM is revised (cont’d): - Procedure document:

Approving the Posting of Reliability Standard Supporting References;

- Procedure document: Processing Requests for an Interpretation;

Document to be updated in conjunction with SPM changes: - Guideline document:

Guidelines for Interpretation Drafting Teams.


NERC Legal and Regulatory Update

October 2017 – November 2017

NERC FILINGS TO FERC SUBMITTED SINCE LAST SC UPDATE

FERC Docket No. Filing Description FERC Submittal

Date

RM18-1-000

Petition for Approval of Proposed revisions to Appendix 3d to the Rules of Procedure NERC submitted proposed revisions to Appendix 3D (Registered Ballot Body Criteria) of the NERC Rules of Procedure. The purpose of the proposed revisions is to help ensure that the votes of Independent System Operators and Regional Transmission Organizations are appropriately represented in Segment 2 of NERC’s Registered Ballot Body for voting on NERC Reliability Standards.

11/21/2017

RM18-1-000

Comments of NERC in Response to Grid Reliability and Resilience Pricing NOPR NERC submitted comments in response to the Department of Energy's proposed rule and the Commission's request for comments on grid reliability and resilience pricing.

10/23/2017

RR17-6-000

Motion of NERC for Leave to Answer joint Comments of AESO, CAISO, IESO and PJM NERC submitted a motion to answer the joint comments of the Alberta Electric System Operator, the California Independent System Operator Corporation, the Independent Electricity System Operator, ISO New England, Inc., and PJM Interconnection, LLC.

10/17/2017

FERC ISSUANCES SINCE LAST SC UPDATE

FERC Docket No. Issuance Description FERC Issuance

Date

RD17-6-000

Letter Order Approving revisions to VRFs for BAL-002-2 FERC issued a letter order approving revisions to the violation risk factors for Requirements R1 and R2 of Reliability Standard BAL-002-2 (Disturbance Control Standard-Contingency Reserve for Recovery from a Balancing Contingency Event).

10/2/2017

RD17-8-000

Letter Order Approving regional Reliability Standard BAL-502-RF-03 FERC issued an order approving regional Reliability Standard BAL-502-RF-03 (Planning Resource Adequacy Analysis, Assessment and Documentation).

10/16/2017

RD17-9-000 Letter Order Approving regional Reliability Standard PRC-006-SERC-02 10/16/2017

http://www.nerc.com/FilingsOrders/us/NERC%20Filings%20to%20FERC%20DL/Petition%20for%20Approval%20of%20Proposed%20Revisions%20to%20Appendix%203D%20to%20the%20Rules%20of%20Procedure.pdf

http://www.nerc.com/FilingsOrders/us/NERC%20Filings%20to%20FERC%20DL/Petition%20for%20Approval%20of%20Proposed%20Revisions%20to%20Appendix%203D%20to%20the%20Rules%20of%20Procedure.pdf

http://www.nerc.com/FilingsOrders/us/NERC%20Filings%20to%20FERC%20DL/Comments%20of%20NERC%20re%20Proposed%20Grid%20Reliability%20and%20Resilience%20Pricing.pdf

http://www.nerc.com/FilingsOrders/us/NERC%20Filings%20to%20FERC%20DL/Comments%20of%20NERC%20re%20Proposed%20Grid%20Reliability%20and%20Resilience%20Pricing.pdf

http://www.nerc.com/FilingsOrders/us/NERC%20Filings%20to%20FERC%20DL/Motion%20for%20Leave%20re%20NERC%20ROP%20revisions%20Joint%20Comments.pdf

http://www.nerc.com/FilingsOrders/us/NERC%20Filings%20to%20FERC%20DL/Motion%20for%20Leave%20re%20NERC%20ROP%20revisions%20Joint%20Comments.pdf

http://www.nerc.com/FilingsOrders/us/FERCOrdersRules/Delegated%20Letter%20Order%20Approving%20revisions%20to%20VRF%20for%20BAL-002-2.pdf

http://www.nerc.com/FilingsOrders/us/FERCOrdersRules/Delegated%20Letter%20Order%20Approving%20BAL-502-RF-03.pdf

http://www.nerc.com/FilingsOrders/us/FERCOrdersRules/Delegated%20Letter%20Order%20Approving%20PRC-006-SERC-02.pdf

2

UPCOMING FILING DATES

FERC Docket No. Filing Description Projected Filing

Date

RM17-11-000 Comments in response to NOPR are due on December 26, 2017.

FERC issues a letter order approving regional Reliability Standard PRC-006-SERC-02 (Automatic Underfrequency Load Shedding (UFLS) Requirements).

RM17-11-000

Notice of Proposed Rulemaking Proposing to Approve Reliability Standard CIP-003-7 FERC issued a notice of proposed rulemaking proposing to approve (i) Reliability Standard CIP-003-7 (Cyber Security - Security Management Controls); (ii) revised definitions of Removable Media and Transient Cyber Asset to be included in the NERC Glossary; (iii) the associated VRFs and VSLs; (iv) the associated Implementation Plan; and (v) the retirement of currently-effective Reliability Standard CIP-003-6 and the NERC Glossary definitions of Low Impact External Connectivity and Low Impact BEC Cyber System Electronic Access Point. Comments in response to NOPR are due by 12/26/2017.

10/19/2017

RR17-5-000

Letter Order Approving WECC SDP manual Revisions FERC issued a letter order accepting NERC's petition to approve the Western Coordinating Council ("WECC") Regional Entity Standards Development Process Manual.

10/27/2017

RM16-22-000

Notice of Proposed Rulemaking Proposing to Approve reliability Standards PRC-027-1 and PER-006-1 FERC issued a notice of proposed rulemaking proposing to approve (i) Reliability Standards PRC-027-1 (Coordination of Protection Systems for Performance During Faults) and PER-006-1 (Specific Training for Personnel); (ii) new and revised definitions of Protection System Coordination Study, Operational Planning Analysis and Real-time Assessment; (iii) the associated VRFs/VSLs and Implementation Plans; and (iv) the retirement of currently-effective Reliability Standard PRC-001-1(ii). NOPR published on 11/22/2017, comment deadline is Jan. 22, 2018.

11/16/2017

http://www.nerc.com/FilingsOrders/us/FERCOrdersRules/E-1_NOPR%20on%20CIP-003-7_10192017.pdf

http://www.nerc.com/FilingsOrders/us/FERCOrdersRules/E-1_NOPR%20on%20CIP-003-7_10192017.pdf

http://www.nerc.com/FilingsOrders/us/FERCOrdersRules/Delegated%20Order%20Approving%20WECC%20RSDP_RR17-5.pdf

http://www.nerc.com/FilingsOrders/us/FERCOrdersRules/Order%20on%20CMEP.pdf

http://www.nerc.com/FilingsOrders/us/FERCOrdersRules/Order%20on%20CMEP.pdf

Standards Committee Expectations Approved by Standards Committee January 12, 2012

Background Standards Committee (SC) members are elected by members of their segment of the Registered Ballot Body, to help the SC fulfill its purpose. According to the Standards Committee Charter, the SC’s purpose is:

In compliance with the NERC Reliability Standards Development Procedure, the Standards Committee manages the NERC standards development process for the North American-wide reliability standards with the support of the NERC staff to achieve broad bulk power system reliability goals for the industry. The Standards Committee protects the integrity and credibility of the standards development process.

The purpose of this document is to outline the key considerations that each member of the SC must make in fulfilling his or her duties. Each member is accountable to the members of the Segment that elected them, other members of the SC, and the NERC Board of Trustees for carrying out their responsibilities in accordance with this document.

Expectations of Standards Committee Members

1. SC Members represent their segment, not their organization or personal views. Each member isexpected to identify and use mechanisms for being in contact with members of the segment inorder to maintain a current perspective of the views, concerns, and input from that segment. NERCcan provide mechanisms to support communications if an SC member requests such assistance.

2. SC Members base their decisions on what is best for reliability and must consider not only what isbest for their segment, but also what is in the best interest of the broader industry and reliability.

3. SC Members should make every effort to attend scheduled meetings, and when not available arerequired to identify and brief a proxy from the same segment. Standards Committee businesscannot be conducted in the absence of a quorum, and it is essential that each Standards Committeemake a commitment to being present.

4. SC Members should not leverage or attempt to leverage their position on the SC to influence theoutcome of standards projects.

5. The role of the Standards Committee is to manage the standards process and the quality of theoutput, not the technical content of standards.

Agenda Item 12a Standards Committee December 6, 2017

http://www.nerc.com/comm/SC/Documents/SC%20approved%20Item_7-Att_2_SC_Charter-SC_Approved_January_16_2013_Revised_11_26_13_clean.pdf

Agenda Item 12b Standards Committee December 6, 2017

Standards Committee Meeting Dates and Locations for 2017

The time for face-to-face meetings is based on the ‘local’ time zone. The time specified for all conference calls is based on Eastern Time.

• January 18, 2017 Conference Call (1:00 - 4:00 p.m.)

• March 15, 2017 WECC (10:00 a.m. – 3:00 p.m.)

• April 19, 2017 Conference Call (1:00 - 4:00 p.m.)

• June 14, 2017 Atlanta (10:00 a.m. – 3:00 p.m.)

• July 19, 2017 Conference Call (1:00 - 4:00 p.m.)

• September 7, 2017 MRO (10:00 a.m. – 3:00 p.m.)

• October 18, 2017 Conference Call (1:00 - 4:00 p.m.)

• December 6, 2017 Atlanta (10:00 a.m. – 3:00 p.m.)

This schedule was designed so that the SCPS SC subcommittee face-to-face meetings will occur the day before and the PMOS SC Subcommittee will occur face-to-face the mornings of the SC meetings from 8:00 a.m. – 9:45 a.m. Scheduling of subcommittee face-to-face meetings is handled by the chairs of the subcommittees in consultation with the subcommittees’ members and NERC staff.

Standards Committee 2017 Segment Representatives

Segment and Term Representative Organization

Chair 2016‐17

Brian Murphy Senior Attorney

NextEra Energy, Inc.

Vice‐Chair 2016‐17

Michelle D’Antuono Manager, Energy

Occidental Energy Ventures, LLC

Segment 1‐2016‐17 Laura Lee Manager of ERO Support and Event Analysis, System Operations

Duke Energy

Segment 1‐2017‐18 Sean Bodkin NERC Compliance Policy Manager

Dominion Resources Services, Inc.

Segment 2‐2016‐17 Ben Li Consultant

Independent Electric System Operator

Segment 2‐2017‐18 Charles Yeung Executive Director Interregional Affairs

Southwest Power Pool

Segment 3‐2016‐17 Scott Miller Manager Regulatory Policy

MEAG Power

Segment 3‐2017‐18 John Bussman Manager, Reliability Compliance

Associated Electric Cooperative, Inc.

Segment 4‐2016‐17 Chris Gowder Regulatory Compliance Manager

Florida Municipal Power Agency

Segment 4‐2017‐18 Barry Lawson Associate Director, Power Delivery and Reliability

National Rural Electric Cooperative Association

Segment 5‐2016‐17 Randy Crissman Vice President – Technical Compliance

New York Power Authority

Segment 5‐2017‐18 Amy Casuscelli Sr. Reliability Standards Analyst

Xcel Energy

Agenda Item 12c Standards Committee December 6, 2017

Segment 6‐2016‐17 Andrew Gallo Director, Reliability Compliance

City of Austin dba Austin Energy

Segment 6‐2017‐18 Brenda Hampton Regulatory Policy

Energy Future Holdings – Luminant Energy Company LLC

Segment 7‐2016‐17 Frank McElvain Senior Manager, Consulting

Siemens Power Technologies International

Segment 7‐2017‐18 vacant

Segment 8‐2016‐17 Robert Blohm, Managing Director

Keen Resources Ltd.

Segment 8‐2017‐18 David Kiguel Independent

Segment 9‐2016‐17 Alexander Vedvik Senior Electrical Engineer

Public Service Commission of Wisconsin

Segment 9‐2017‐18 Michael Marchand Senior Policy Analyst

Arkansas Pubic Service Commission

Segment 10‐2016‐17 Guy Zito Assistant Vice President of Standards

Northeast Power Coordinating Council

Segment 10‐2017‐18 Steve Rueckert Director of Standards

Western Electricity Coordinating Council

Standards Committee 2017 Roster

Parliamentary Procedures

Agenda Item 12d Standards Committee December 6, 2017

Based on Robert’s Rules of Order, Newly Revised, 11th 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 cannot 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

No 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.” The vote is subject to a 2/3 majority approval. Also, any member may call the question. This motion is not debatable. The vote is subject to a 2/3 vote.

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.

- 1 -

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.

- 2 -

Voting Voting Method When Used How Recorded in Minutes Unanimous Consent The standard practice.

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.

- 3 -