Welcome! [] of Standards Webinar_… · (SPM) Section 11. Question & Answer Session. Topic 4: High-level overview of active standard development projects . Ryan Stewart, Manager of

Welcome!NERC State of Standards Webinar

Lacey Ourso, NERC Standards Developer August 27, 2015

RELIABILITY | ACCOUNTABILITY2

• Update on the Standards Program • CIP updates • Process for approving supporting documentation under Section

11 of the Standards Process Manual• High-level overview of active standard development projects • Projects currently open for comment• Updates from the Standards Information Group• Fall Standards & Compliance workshop

Topics


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.

NERC Antitrust Compliance Guidelines

Opening Remarks

Howard Gugel, Director of Standards

Topic 1: Update on the Standards Program



• Progress on FERC Directives• 2015 Trends and Expectations• Going Forward – 2016 and Beyond• Draft 2016-2018 NERC Reliability Standards Development Plan

(RSDP)

Agenda Topics


Progress on FERC Directives

Pre-2013 Directives*

Post 2012 Directives* Total

Issued prior to year-end 2012 191 Issued since year-end 2012 56 Resolved as of March 31, 2015 168 44 Remaining 23 12 35 Projected to be resolved in 2015 18 6 24 Projected remaining at year-end 2015 5 6 11


Progress on Paragraph 81 and Independent Experts’ Review Panel (IERP)


Progress on Paragraph 81 and IERP(continued)


• February (3) • May (5 planned; 3 actual)• August (4 planned; 1 actual)• November (3 planned; 7 projected plus 2 directives projects)• Early 2016 (4 planned)

Reaching Steady-State in 2015


Trend for Number of Requirements

0

100

200

300

400

500

600

2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2027

Num

ber o

f Req

uire

men

ts

Years

Continent-wide Requirements by Enforcement Date November 2014Continent-wide Requirements by Enforcement Date April 2015Regional Reliability Requirements by Board Adoption November 2014Regional Reliability Requirements by Enforcement Date April 2015


• How did we get here? 2012 stakeholder inputs

• Progress towards steady state• Project Management and Oversight Subcommittee• FERC directives

241 directives in 2013-2015 Ten directives outstanding in 2016

• Paragraph 81 and Independent Expert Review Panel 281 requirements recommended for retirement 273 addressed by 2016

o 46% retiredo 43% revisedo 11% reaffirmed

2015 Trends and Expectations


• Analysis and coordination Ahead of project kick-off Feedback loops Committees, trades, forums Risk analysis

• Consider other projects, tools, and principles Connection to technical excellence Compliance guidance

• Project planning Project Management and Oversight Subcommittee Enhanced periodic reviews

Going Forward – 2016 and Beyond


• Measured, in-depth review to improve quality and content of standards

• Look for opportunities to make standards more concise Verify content is appropriate to be included in a standard Builds on Independent Experts’ work with industry input

• Plan in development• Execution expected in Q1 2016

Topic was discussed at the May NERC Board of Trustees meetings for policy inputs

• No mandated timeline Controlled, organized rollout and execution

Enhanced Periodic Reviews


• Recognizes current trend at NERC Smaller drafting and review teams of 6-10 members Active observers Engaged industry throughout standard development process Active use of project listservs

• Essential part of standards development The ballot is an inefficient barometer of industry position Ad hoc groups have more influence early in the process Teams often more receptive to comments during early phases of

development Communication among industry, teams, NERC, and FERC

Hot Topic – Industry Outreach


• Continued open dialogue as we engage in a more measured development of standards Feedback loops Committees, trades, forums Compliance inputs and guidance Enhanced periodic reviews vs. standards development projects timing

• Feedback during outreach and development Suggested language Rationale

• NERC Standards contact Sean Cavote, Manager of Standards Development [email protected] or 404.446.9697

Hot Topic – Industry Outreach

mailto:[email protected]


• Purpose it to set forth a plan for standards development• Presented to the NERC Board and filed with applicable

governmental authorities each year• Inputs from Standards Committee, industry through a

comment period, NERC Board and Member Representatives Committee

• Draft plan incorporates planning for enhanced periodic reviews

Draft 2016-2018 Reliability Standards Development Plan


• Draft 2016–2018 RSDP sets forth a plan that involves conducting the enhanced periodic reviews as well as accomplishing other envisioned tasks by addressing: emerging risks, FERC directives, and Standards Authorization Requests (SARs).

• This plan specifically includes the Integration of Variable Generation Task Force (IVGTF) recommendations, the Essential Reliability Services Task Force (ERSTF) recommendations, communication with the Reliability Issues Steering Committee (RISC) on other emerging risks, potential FERC directives, and input from industry on the feedback loops



• Provides update on regulatory directives• Provides a 2015 progress report on all active projects• Discusses projects planned to carry over into 2016 or to begin

in 2016• Identifies what the criteria is for a standard or family of

standards are eligible to be opened for an enhanced periodic review



• Allows for feedback loops, or factors for consideration of risk Emerging Risks and Changing Technologies Event Analysis and Compliance Violation Statistics Lessons Learned and Frequently Asked Questions Measures RSAW Development and Compliance Input Regional Variances Construct of Standards



• Status Solicited to the NERC Standards Committee for comment Posted for industry comment and closed on Monday, August 17, 8pm ET Feedback will be incorporated into the draft plan and solicited for

another round of acceptance by the NERC Standards Committee Plan is to present to the NERC Board in November and then file with the

applicable governmental authorities by the end of the year

• NERC Standards contact Ryan Stewart, Manager of Standards Development [email protected] or 404-466-9712



Topic 2: CIP Standards and Compliance – Are we there yet?

Tobias Whitney, Manager of CIP Compliance


• Industry Awareness Webinars

• Clarification of Mandatory Enforcement Dates

• Training for Auditors and RSAW Development

• Pilot Exercises

• Lessons Learned and Frequently Asked Questions (Section 11)

• Implementation or Transition Period Guidance

Post-Approval Activities


Guidance Development Process

Draft and Post for Comment

Finalize and Post as Guidance

Industry Drafts/Reviews

Guidance

Post for Industry

Comment

Guidance identification and priority

FAQ identification and Priority

NERC/FERC Feedback

&Posting as a Reference Document

Identify and Prioritize1


• Advisory Groups Regional Representatives Key Industry Stakeholders Standard Drafting Team Members NERC Compliance & Enforcement Staff

• Collaboration with Industry Groups North American Transmission Forum (NATF) North American Generator Forum (NAGF) NERC Sub-Committee Leadership (PC, OC and CIPC)

Continued Stakeholder Involvement


• FERC’s Notice of Proposed Rulemaking (NOPR) – highlighted the following topics for comment: Supply chain Protecting communication links between control centers Adequacy of existing remote access controls in CIP Version 5 Protections for Transient Devices at Low Impact Clearer descriptions and definitions of Low Impact External Routable

Connectivity (LERC)

• Interpretations Patch Management Shared BES Cyber Assets & Common mode vulnerability Compliance Dates for Unplanned changes

• Standards Revisions V5 Transition Issues

Major Initiatives Related to CIP


Contact Information

• Manager of CIP Compliance, Tobias Whitney Email at [email protected] Telephone: 404-446-9674

• CIP Transition Program web pages: http://www.nerc.com/pa/CI/Pages/Transition-Program.aspx

http://www.nerc.com/pa/CI/Pages/Transition-Program-V5-Implementation-Study.aspx


http://www.nerc.com/pa/CI/Pages/Transition-Program.aspx

http://www.nerc.com/pa/CI/Pages/Transition-Program-V5-Implementation-Study.aspx

Topic 3: Process for Approving Supporting Documentation under Section 11 of the Standards Process Manual

Ryan Stewart, Manager of Standards DevelopmentShamai Elstein, Senior Counsel


• Section 11 provides a mechanism for any entity to link a supporting document to a NERC Reliability Standard.

• Supporting documents explain or facilitate implementation of Reliability Standards.

o They do not themselves contain mandatory Requirements subject to compliance review.

• Supporting documents include:o Referenceo Guidelineo Supplemento Training Materialo Procedureo White Paper

NERC Standard Processes Manual (SPM) Section 11


• Standards Committee role: Authorize the posting of all supporting references that are linked to an

approved Reliability Standard Verify the document has had stakeholder review to verify the accuracy

of the technical content SC Procedure for approving the posting of supporting references

presented by an SDT or NERC technical committee:o http://www.nerc.com/pa/Stand/Resources/Documents/SC_procedure_app

v_posting_RS_supporting_SC_endorsed_120914.pdf

• Authors role under SC procedure: Develop a supporting reference to post for an industry comment period Address comments from stakeholders, if any Develop a report that includes a response to each comment or a general

summary of all comments received


http://www.nerc.com/pa/Stand/Resources/Documents/SC_procedure_appv_posting_RS_supporting_SC_endorsed_120914.pdf


• Disclaimer for NERC Lessons Learned/FAQs under Section 11:

This document is designed to convey lessons learned. It is not intended to establish new requirements under NERC’s Reliability Standards, to modify the requirements in any existing reliability standards nor provide an Interpretation under Section 7 of the Standard Processes Manual. Additionally, there may be other legitimate ways to fulfill the obligations of the requirements that are not expressed within this supporting document. Compliance will continue to be determined based on language in the NERC Reliability Standards as they may be amended from time to time. Implementation of this lesson learned is not a substitute for compliance with requirements in NERC’s Reliability Standards.


Question & Answer Session

Topic 4: High-level overview of active standard development projects

Ryan Stewart, Manager of Standards Development


• 2007-17.4 – FERC Order No. 803 Directive (PRC-005)

• 2009-02 – Real-time Reliability Monitoring and Analysis Capabilities

• 2010-07.1 – Vegetation Management (FAC-003)

• 2010-14.2.1 – Phase 1 – Balancing Authority Reliability-based Controls (BAL-002)

• 2015-04 – Alignment of Terms

• 2015-07 – Internal Communications Capabilities (COM-001)

• 2015-08 – Emergency Operations (EOP Standards)

• 2015-09 – Establish and Communicate System Operating Limits (FAC Standards)

Agenda Topics


• In Order No. 803, FERC approved PRC-005-3, and in Paragraph 31, directed NERC to: "...develop modifications to PRC-005-3 to include supervisory devices

associated with auto-reclosing relay schemes to which the Reliability Standard applies. Further, we clarify that NERC’s proposal regarding the scope of supervisory devices is an acceptable approach to satisfy the Commission directive. Specifically, NERC proposed in its NOPR comments, and we find acceptable, that the scope of the supervisory devices to be encompassed in the Reliability Standard are those providing voltage supervision, supervisory inputs associated with selective auto-reclosing, and sync-check relays that are part of a reclosing scheme covered by PRC-005-3."

2007-17.4 – FERC Order No. 803 Directive (PRC-005)


• A revised SAR was prepared along with a proposal to address the directive

• The SAR provides background information regarding the directive

• The existing Protection System Maintenance and Testing SDT (PSMTSDT) worked to address the directive

SAR and Proposed Revisions


• The proposed solution that the PSMTSDT developed to address the directive proposes to revise the standard-specific defined terms “Automatic Reclosing” and “Component Type” Automatic Reclosing – Includes the following Components:

o Reclosing relayo Supervisory relay(s) – relays(s) that perform voltage and/or sync check

functions that enable or disable operation of the reclosing relayo Voltage and Current Sensing Devices associated with the supervisory relay(s)o Control circuitry associated with the reclosing relay or supervisory relay(s).



• The proposed solution that the PSMTSDT developed to address the directive proposes to revise the standard-specific defined terms “Automatic Reclosing” and “Component Type” Component Type:

o Any one of the five specific elements of a Protection System. o Any one of the two four specific elements of Automatic Reclosing. o Any one of the two specific elements of Sudden Pressure Relaying.



• The PSMTSDT proposes to streamline the Implementation Plan for all versions of PRC-005.

• PRC-005-2 and PRC-005-2(i) would be implemented together.• All other versions of the standard would be implemented

simultaneously with PRC-005-6. PRC-005-2(ii) PRC-005-3 PRC-005-3(i) PRC-005-3(ii) PRC-005-4 PRC-005-5

Proposed Implementation Plan


• July 30-September 16: PRC-005-6 and associated documents posted for a 45-day concurrent comment/ballot period

• September 29-October 1: PSMTSDT meeting to respond to comments and prepare documents for final ballot

• Week of October 12: Documents posted for final ballot

• November 5-6: NERC Board of Trustees meeting – Revised standard presented for adoption

• November: PRC-005-6 and Implementation Plan filed with FERC

2015 Standard Development Timeline


• Steve Crutchfield, Senior Standards Developer Email at [email protected] Telephone: 609-651-9455

• Jordan Mallory, Standards Developer Email at [email protected] Telephone: 404-446-9733

• Charles Rogers, Standard Drafting Team Chair Email at [email protected] Telephone: 517-788-0027

• Project web page:http://www.nerc.com/pa/Stand/Pages/Project_2007-17_4_PRC-005_FERC_Order_No_803_Directive.aspx

Information




http://www.nerc.com/pa/Stand/Pages/Project_2007-17_4_PRC-005_FERC_Order_No_803_Directive.aspx


• Project will develop requirements to address issues related to Real-time monitoring and analysis of the Bulk Electric System

• Formal development paused in 2011 for prioritization

• SAR Drafting Team (SAR DT) appointed in April 2015 to revise previous project SAR taking into consideration: FERC Order No. 693 directives Real-time Tools Best Practices Task Force recommendations 2011 Southwest Outage Report recommendations Proposed TOP and IRO Standards (pending FERC approval) Technical conference for stakeholder input (June 2015)

2009-02 – Real-time Reliability Monitoring and Analysis Capabilities


• SAR DT concluded that most issues and recommendations considered in original project scope have been addressed Proposed TOP and IRO Standards pending FERC approval

• Project scope going forward will address remaining issues for operator real-time situational awareness Operator indications of data and analysis quality Operator notification of monitoring and/or analysis unavailability Operating procedures to address quality or availability issues

• The standard drafting team is reviewing comments from SAR posting and developing initial draft requirements

2009-02 – Real-time Reliability Monitoring and Analysis Capabilities


• Mark Olson, Senior Standards Developer Email at [email protected] Telephone: 404-446-9760

• Sean Bodkin, Standards Developer Email at [email protected] Telephone: 202-400-3022

• Project web page:http://www.nerc.com/pa/Stand/Pages/Project-2009-02-Real-time-Reliability-Monitoring-and-Analysis-Capabilities.aspx

Information



http://www.nerc.com/pa/Stand/Pages/Project-2009-02-Real-time-Reliability-Monitoring-and-Analysis-Capabilities.aspx


• In FERC Order No. 777, the Commission directed NERC to, “conduct or contract testing to obtain empirical data and submit a report to the Commission providing the results of the testing.”

• NERC retained the Electric Power Research Institute (EPRI) to conduct testing to support appropriate Minimum Vegetation Clearance Distances (MVCDs) specified in NERC Reliability Standard FAC-003-3.

2010-07.1 – Vegetation Management (FAC-003)


• August 19, 2015 - The Standards Authorization Request was authorized for posting by the NERC Standards Committee

• September 8, 2015 - Solicitation for drafting team members ends

• September 23, 2015 - SC appoint FAC Standards Drafting Team

• October 21, 2015 - SC authorization for initial posting of FAC-003 Standard (45-day comment and ballot)

• October 22, 2015 - Post and announce FAC-003 for 45-day comment and ballot (ending Dec. 4)

• December 14, 2015 - Post for final 10-day ballot

• February 2016 - Present at February NERC Board

• February 2016 - File petition with FERC

2010-07.1 – Vegetation Management (FAC-003)




• Project web page:http://www.nerc.com/pa/Stand/Pages/Project-2010-07-1-Vegetation-Management.aspx

Information



http://www.nerc.com/pa/Stand/Pages/Project-2010-07-1-Vegetation-Management.aspx


• Purpose of Standard To balance resources and demand within defined limits in response to a

Reportable Balancing Contingency Event

• Status Completed additional ballot August 20, 2015 Received a 69.26% industry approval

• Next steps Standard drafting team meeting September 16-17, 2015 to address

comments received Posting for final ballot anticipated in late September

• Darrel Richardson, Senior Standard Developer [email protected]

Project 2010-14.2.1 - Phase 1 of BARC: BAL-002



2015-04 – Alignment of Terms

• Purpose of project Phase 1 - Align the defined terms found in the NERC Glossary of Terms

and the Rules of Procedure Phase 2 – Provide recommendations regarding other definition-related

issues in the Glossary and ROP, including enhancements to the current definition development process, to prevent misalignment in the future

• Status Initial ballot completed July 27, 2015 Industry approval for all 26 Glossary terms under revision

• Next steps Post for 10-day final ballot on September 4 Phase 2 drafting team meeting on October 19-20 in San Diego, CA


• Lacey Ourso, Standards Developer Email at [email protected] Telephone: 404-446-2581

• Project web page:http://www.nerc.com/pa/Stand/Pages/Project-2015-04-Alignment-of-Glossary-of-Terms-(NERC-Reliability-Standards-and-the-Rules-of-Procedure).aspx

Information


http://www.nerc.com/pa/Stand/Pages/Project-2015-04-Alignment-of-Glossary-of-Terms-(NERC-Reliability-Standards-and-the-Rules-of-Procedure).aspx


• In FERC Order No. 808, the Commission directed NERC to: Address “internal communications capabilities that could involve the

issuance or receipt of Operating Instructions or other communications that could have an impact on reliability.”o Address internal telecommunications or other internal communication

systems “between geographically separate control centers within the same functional entity.”

o Address internal telecommunications or other internal communication systems “between a control center and field personnel.”

o Address “[t]he adequacy of internal communications capability whenever internal communications could directly affect the reliable operation of the Bulk-Power System.”

2015-07 – Internal Communications Capabilities (COM-001)


• COM-001-3 is a modified version of COM-001-2 Proposed Requirement R12 addresses Reliability Coordinator, Balancing

Authority and Transmission Operator responsibilities. Proposed Requirement R13 addresses Distribution Provider and

Generator Operator responsibilities. Two separate requirements were necessary to address different VRFs

based on the risks associated with different functional registrations. Capabilities are not limited but encompass any medium that allows two

or more individuals to interact, consult, or exchange information as stated in the NERC Glossary of Terms.

COM-001-3


• Present to Standards Committee (SC) on September 23, 2015 for authorization to post.

• Initial 45-day comment period and 10-day ballot proposed to be posted September 2015.

• Next SDT meeting is scheduled for the week of October 26, 2015.

• If the proposed standard passes and there are no substantive revisions initial ballot, the standard will be posted for a 10-day final ballot and presented at the February 2016 NERC Board of Trustees Meeting.

Next Steps




• Project web page:http://www.nerc.com/pa/Stand/Pages/Project%202015-07_Internal_Communications_Capabilities.aspx

Information



http://www.nerc.com/pa/Stand/Pages/Project%202015-07_Internal_Communications_Capabilities.aspx


• Drafting effort a result of the EOP Emergency Operations Periodic Review

• Periodic review team proposed standard modifications

• The project will likely: EOP-004-2 – (1) Revise the standard and attachment and (2) retire

Requirement R3; EOP-005-2 – Revise the standard; EOP-006-2 – (1) Revise the standard and (2) retire Requirements Parts

R1.2, R1.3, and R1.4; and EOP-008-1 – Revise the standard.

2015-08 – Emergency Operations (EOP Standards)


• Laura Anderson, Standards Developer Email at [email protected] Telephone: 404-446-9671

• Project web page:http://www.nerc.com/pa/Stand/Pages/Project-2015-08-Emergency-Operations.aspx

Information


http://www.nerc.com/pa/Stand/Pages/Project-2015-08-Emergency-Operations.aspx


• Drafting effort a result of the FAC System Operating Limits Periodic Review

• The project will revise requirements for determining and communicating System Operating Limits (SOLs) used in the reliable planning and operation of the Bulk Electric System (BES).

2015-09 – Establish and Communicate System Operating Limits (FAC Standards)


• Propose retirement of FAC-010-3

• Clarify acceptable System performance criteria for operations time horizon

• Propose requirements to address identified reliability issues

• Revise or develop new definitions to provide clarity and alignment with how SOLs are treated

• Clarify responsibilities for establishing and communicating SOLs

• Develop revised or new requirements that facilitate transfer of necessary reliability information

Periodic Review Team Recommendations


• August 19, 2015 - The Standards Authorization Request was authorized for posting by the NERC Standards Committee

• September 2, 2015 - Solicitation for drafting team members closes

• September 23, 2015 - SC Appoint FAC SOL Standards Drafting Team

• October 2015 – SDT kickoff meeting

2015-09 – Establish and Communicate System Operating Limits (FAC Standards)


• Lacey Ourso, Standards Developer Email at [email protected] Telephone: 404-446-9733

• Mark Olson, Senior Standards Developer Email at [email protected] Telephone: 404-446-9760

• Project web page:http://www.nerc.com/pa/Stand/Pages/Project-2015-09-Establish-and-Communicate-System-Operating-Limits.aspx

Information



http://www.nerc.com/pa/Stand/Pages/Project-2015-09-Establish-and-Communicate-System-Operating-Limits.aspx

Topic 5: Projects currently open for comment

Al McMeekin, Standards Developer Scott Barfield, Standards Developer Darrel Richardson, Senior Standards Developer


• Presenters Al McMeekin - Project 2007-06 (PRC-027-1) Scott Barfield-McGinnis - Project 2007-06.2 (TOP-009-1)

• Joint effort Two separate projects addressing PRC-001-1.1(ii) PRC-027-1 is addressing Requirements R3 and R4 TOP-009-1 is addressing Requirement R1

o The reliability objectives of Requirements R2, R5, and R6 are addressed by proposed TOP/IRO standards

Goal is to achieve the complete retirement of PRC-001-1.1(ii)

Project 2007-06 & Project 2007-6.2

Project 2007-06 (PRC-027-1)


• Issues Applicability assigned to incorrect Functional Entities Lack of clarity around the term “coordinate” and the phrase “major

transmission lines”

• Reliability objective To ensure system protection is coordinated among operating entities

Current PRC-001, R3 and R4


• Requirement R1 mandates an entity establish a process for developing new and revised settings for its BES Protection Systems to operate in the intended sequence during Faults. The requirement stipulates the following attributes that must be included in the process: Provisions to review and update short-circuit models Provisions to review the developed Protection System settings Provisions to coordinate Protection System settings applied on BES

Elements that electrically join Facilities owned by separate functional entities

• Key Point: Captures reliability objectives of both Requirements R3 and R4 of PRC-

001 with minimal compliance burden

PRC-027-1


• Requirement R2 mandates an entity periodically assess the coordination of their existing Protection Systems.

• Key Points: Captures the reliability objective of Requirement R4 of PRC-001

regarding the coordination of Protection Systems on major transmission lines

Provides options for assessing coordination:o Time-based methodology – perform a Protection System Coordination

Study in a time interval not to exceed six calendar yearso Fault current-based methodology – Compare present Fault current values

to an established Fault current baseline and perform a Protection System Coordination Study when the comparison identifies a 15 percent or greater deviation in Fault current values at a bus to which the Element is connected, all in a time interval not to exceed six calendar years

PRC-027-1


• Requirement R3 mandates that an entity utilize the process established in accordance with Requirement R1

• Key Point Utilizing the process will promote consistency in developing Protection

System settings and will minimize the introduction of errors

PRC-027-1

Project 2007-06.2 (TOP-009-1)


• Issues (e.g., ambiguous phrases) As soon as possible Reduces system reliability Operating conditions that could require changes in others Protection

Systems

• Reliability objectives Operating entities have knowledge of their Protection Systems (and

RAS) and their effects Notification of relay and equipment failures and corrective actions as

soon as possible Notification of system changes “in advance” Monitoring and notification of Special Protection Systems

Current PRC-001 – Requirements R1, R2, R5 and R6


• Ensures operating entities have the requisite knowledge of Composite Protection Systems and Remedial Action Schemes (RAS), and their effects, in order to operate and maintain the reliability of the Bulk Electric System (BES) Requirements are specific to each applicable entity Requirements meeting the reliability objective to have knowledge

• Remaining reliability objectives (previous slide) are addressed by: IRO-001, IRO-005-4, IRO-008-2, IRO-010-2, and IRO-017-1 TOP-001-3, TOP-002-4, and TOP-003-3 TPL-001-4

• Improves measurability Knowledge of the functionality and effects Which Protection Systems and RAS are applicable

TOP-009-1


• Knowledge of Composite Protection System May be demonstrated through training (including the effects on the

BES), operating guides, manuals, procedures, output of operational tools (e.g., databases or analysis programs), or outcomes of analyses, monitoring, and assessments that identify the impacts on the BES

• Uses new glossary term “Composite Protection System”• Includes defined term “Remedial Action Scheme”• Aligns the reliability activity in the proper family of Reliability

Standards (i.e., TOP)• Eliminates duplicity (R2, R5, and R6) addressed by IRO, TOP,

and TPL standards

TOP-009-1 Key Points


• The complete retirement of PRC-001-1.1(ii) is contingent upon the approval of both proposed Reliability Standards PRC-027-1 and TOP-009-1

• Implementation Plan of both standards Effective date is the first day of the first calendar quarter that is twelve

(12) months after the date that the standard is approved by an applicable governmental authority…

Both plans allow sufficient time for entities to adjust their processes when transitioning to the new standard(s)

• Mapping Documents explain how reliability objectives are addressed for each of the PRC-001-1.1(ii) requirements

Collective Take-Aways


• PRC-027-1 and TOP-009-1 are posted for formal comment Comment period: July 29 – September 11, 2015 Ballot: September 2-11, 2015

• Draft RSAW for each standard is posted for feedback August 12 – September 11, 2015

• Upcoming SDT in-person meetings September 22-24, 2015 at Oncor, Ft. Worth, TX

• NERC Standards Developer Project 2007-06, [email protected], 404-446-9675 Project 2007-06.2, [email protected], 404-446-9689

Conclusion

mailto:[email protected]?subject=Project%202007-06%20(PRC-027-1)

mailto:[email protected]?subject=Project%202007-06.2%20(TOP-009-1)

Project 2010-04.1 - MOD


Standard Drafting Team

Member Organization

Mark Kuras – Chair PJM

Paul Kure RFC

Brian Glover Great River Energy

Robert Emmert CAL ISO

Barbara Doland SERC

Andrey Oks NPCC


• FERC Order No. 804, which approved reliability standard MOD-031-1 contained two directives. This project was initiated to address these directives. The directives are detailed in part below. Paragraph 18

“…Accordingly, pursuant to section 215(d)(5) of the FPA and consistent with NERC’s comments, we direct NERC to develop a modification to MOD-031-1 through the standards development process to clarify that planning coordinators and balancing authorities must provide demand and energy data upon request of a Regional Entity, as necessary to support NERC’s development of seasonal and long-term reliability assessments.”

Project 2010-04.1


Paragraph 20“…Therefore, rather than attempting to provide the clarification requested by EEI, the Commission directs NERC to consider EEI’s concern regarding the compliance obligations of an applicable entity upon receipt of a data request that seeks confidential information in the standard development process when it addresses the directive to clarify that planning coordinators and balancing authorities must provide demand and energy data upon request of a Regional Entity.”

Project 2010-04.1



• R3. The Planning Coordinator or the Balancing Authority shall provide the data listed collected under Requirement R1 Parts 1.3 through 1.5 for their area R2 to the applicable Regional Entity within 75 calendar days of receiving a request for such data, unless otherwise agreed upon by the parties.

RationaleThis requirement was modified to clarify that an entity was obligated to provide data to its RE regardless of how the data was collected.

Requirement R3


• R4. Any Applicable Entity shall, in response to a written request for the data included in parts 1.3-1.5 of Requirement R1 from a Planning Coordinator, Balancing Authority, Transmission Planner or Resource Planner with a demonstrated need for such data in order to conduct reliability assessments of the Bulk Electric System, provide or otherwise make available that data to the requesting entity. This requirement does not modify an entity’s obligation pursuant to Requirement R2 to respond to data requests issued by its Planning Coordinator or Balancing Authority pursuant to Requirement R1. Unless otherwise agreed upon, the Applicable Entity:

Requirement R4


• shall provide the requested data within 45 calendar days of the written request, subject to part 4.1 of this requirement; and

• shall not be required to provide any requested data that, if provided, would conflict with the Applicable Entity’s confidentiality, regulatory, or security requirements; and

• shall not be required to alter the format in which it maintains or uses the data.

4.1. If the Applicable Entity does not provide data requested under this requirement because (1) the requesting entity did not demonstrate a reliability need for the data; or (2) providing the data would conflict with the Applicable Entity’s confidentiality, regulatory, or security requirements, the Applicable Entity shall, within 30 calendar days of the written request, provide a written response to the requesting entity specifying the data that is not being provided and on what basis.

Requirement R4


RationaleThis requirement was modified to clarify that an entity would not be required to provide data if it would violate a confidentiality obligation. The obligation to share data under Requirement R4 does not supersede or otherwise modify any of the Applicable Entity’s existing confidentiality obligations. For instance, if an entity is prohibited from providing any of the requested data pursuant to confidentiality provisions of an Open Access Transmission Tariff or a contractual arrangement, Requirement R4 does not require the Applicable Entity to provide the data to a requesting entity. If the Applicable Entity is subject to confidentiality obligations that allow the Applicable Entity to share the data only if certain conditions are met, the Applicable Entity shall ensure that those conditions are met within the 45-day time period provided in Requirement R4.

Requirement R4


• Darrel Richardson, Senior Standard Developer [email protected] 609.613.1848

• Project page http://www.nerc.com/pa/Stand/Pages/Project-2010041-MOD031-Order-No-

804-Directives-.aspx

Information


http://www.nerc.com/pa/Stand/Pages/Project-2010041-MOD031-Order-No-804-Directives-.aspx

Project 2010-14.2.1 - Phase 2.1 BARC


Standard Drafting Team

Member OrganizationJerry Rust – Chair Northwest Power Pool

Tom Siegrist – Vice-chair Stone Mattheis Xenopoulosand Brew, PC

Doug Hils Duke Energy

Mike Potishnak Spriteland Energy representing NPCC

Gary Nolan Arizona Public Service

Howard Illian Energy Mark, Inc.

Sandip Sharma ERCOT

Philip Hart AECI

Steve Swan MISO



• R1. All generation, transmission, and load operating within an Interconnection must be included within the metered boundaries of a Balancing Authority Area. R1.1. Each Generator Operator with generation facilities operating in an

Interconnection shall ensure that those generation facilities are included within the metered boundaries of a Balancing Authority Area.

R1.2. Each Transmission Operator with transmission facilities operating in an Interconnection shall ensure that those transmission facilities are included within the metered boundaries of a Balancing Authority Area.

R1.3. Each Load-Serving Entity with load operating in an Interconnection shall ensure that those loads are included within the metered boundaries of a Balancing Authority Area.

• Correct application Being retired and moved to FAC-001-3 R5, R6 and R7 It is appropriate to make this determination at the interconnection stage.

BAL-005-0.2b R1



• R3. Each Balancing Authority shall ensure all of its Balancing Authority Area interconnection points are equipped with common megawatt-hour meters, with readings provided hourly to the control centers of Adjacent Balancing Authorities.

• Correct application Being retired from BAL-006-2 and moved to BAL-005-1 R1 and R8 BAL-005-1 is being revised to focus on the definition of “Reporting ACE”

and this move reflects that.

BAL-006-2 R3


• The Standard Drafting Team is evaluating the remaining reliability requirements associated with BAL-006-2, Inadvertent Interchange.

• The Drafting Team intends to circulate a white paper and survey to acquire industry input on their intention.

BAL-006-2 Next Steps, Industry Input



• Title is now focused on Balancing Authority control and not on a "how to accomplish through "Automatic Generation Control.

• Current BAL-005 was applicable to 4 entities - Proposed BAL-005 applicable only to a Balancing Authority.

• Existing Standard includes requirements that are either a "How to" and "Definition" - proposed Standard is Reliability Requirements. Thus reduced the Requirements from 17 to 8.

• Focused on definition of Reporting ACE and all associated definitions. Removed all associated definitions from Reporting ACE and made them stand alone definitions since they are used throughout NERC. These definitions are associated with the NERC Glossary of Terms.

BAL-005-1 Change – Reliability Focus


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

BAL-005-1 New Definitions


• R1. Each Balancing Authority shall ensure that each Tie-Line, Pseudo-Tie, and Dynamic Schedule with an Adjacent Balancing Authority is equipped with a mutually agreed-upon time synchronized common source to determine hourly megawatt-hour values.1.1. These values shall be exchanged between Adjacent Balancing Authorities.

RationaleProvides for accuracy in the measurements and calculations used in Reporting ACE, hourly inadvertent energy, and Frequency Response measurements. It specifies the need for common metering points for instantaneous and hourly integrated values for the tie line megawatt flow values between Balancing Authority Areas.

Requirement R1


• R2. The Balancing Authority shall use a scan rate of no more than six seconds in acquiring data necessary to calculate Reporting ACE.

RationaleReal-time operation of a Balancing Authority requires real-time information. A sufficient scan rate is key to an Operator’s trust in real-time information.

Requirement R2


• R3. A Balancing Authority that is unable to calculate Reporting ACE for more than 30-consecutive minutes shall notify its Reliability Coordinator within 45 minutes of the beginning of an inability to calculate Reporting ACE.

RationaleThe RC is responsible for coordinating the reliability of bulk electric systems for member BA’s. When a BA is unable to calculate its ACE for an extended period of time, this information must be communicated to the RC so that the RC has sufficient knowledge of system conditions to assess any unintended reliability consequences that may occur on the wide area.

Requirement R3


• R4. Each Balancing Authority shall use frequency metering equipment for the calculation of Reporting ACE:4.1. that is available a minimum of 99.95% for each calendar year; and,4.2. with a minimum accuracy of 0.001 Hz.

RationaleFrequency is the basic measurement for interconnection health, and a critical component for calculating Reporting ACE. Without sufficient available frequency data the BA operator will lack situational awareness and will be unable to make correct decisions when maintaining reliability.

Requirement R4


• R5. The Balancing Authority shall make available to the operator information associated with Reporting ACE including, but not limited to, quality flags indicating missing or invalid data.

RationaleSystem operators utilize Reporting ACE as a primary metric to determine operating actions or instructions. When data inputs into the ACE calculation are incorrect, the operator should be made aware through visual display.

Requirement R5


• R6. Each Balancing Authority’s system used to calculate Reporting ACE shall be available a minimum of 99.5% of each calendar year.

RationaleReporting ACE is an essential measurement of the BA’s contribution to the reliability of the Interconnection. Since Reporting ACE is a measure of the BA’s reliability performance for BAL-001, and BAL-002, it is critical that Reporting ACE be sufficiently available to assure reliability.

Requirement R6


• R7. Each Balancing Authority that is within a multiple Balancing Authority Interconnection shall implement an Operating Process to identify and mitigate errors affecting the scan-rate accuracy of data used in the calculation of Reporting ACE for each Balancing Authority Area.

RationaleWithout a process to address persistent errors in the ACE calculation, the operator can lose trust in the validity of Reporting ACE resulting in delayed or incorrect decisions regarding the reliability of the bulk electric system.

Requirement R7


• R8. Each Balancing Authority shall agree with an Adjacent Balancing Authority on a common source for respective Tie-Lines, Pseudo-Ties, and Dynamic Schedules and shall implement that common source to provide common information to both Balancing Authorities for the calculation of Reporting ACE.

RationaleProvides for accuracy in the measurement and calculations used in Reporting ACE. It specifies the need for common metering points for instantaneous values for the tie-line megawatt flow values between Balancing Authority Areas. Common data source requirements also apply to instantaneous values for pseudo-ties and dynamic schedules, and can extend to more than two Balancing Authorities that participate in allocating shares of a generation resource in supplementary regulation, for example.

Requirement R8


• Darrel Richardson, Senior Standard Developer [email protected] 609.613.1848

• Project page http://www.nerc.com/pa/Stand/Pages/Project-20101421-Phase-2--

Balancing-Authority-Reliabilitybased-Controls--BAL0051-and-BAL006.aspx

Information


http://www.nerc.com/pa/Stand/Pages/Project-20101421-Phase-2--Balancing-Authority-Reliabilitybased-Controls--BAL0051-and-BAL006.aspx

Project 2010-05.3 - Phase 3 of Protection Systems – Remedial Action Schemes (PRC-012-2)


• NERC Project 2010-05.3 Remedial Action Schemes is phase 3 of Protection Systems Phase 2 was initiated in February 2014 and culminated with the revised

definition of Remedial Action Scheme being adopted by the NERC Board of Trustees (BOT) on November 13, 2014

Phase 2 replaced the term Special Protection System with the term Remedial Action Scheme in approximately half of the forty-three (43) NERC Reliability Standards that contained the term

Phase 3 was initiated in January 2015 The SDT posted a preliminary draft of PRC-012-2 for a 21-day informal

comment period in May, 2015

Project Background


Phase 3• Address the reliability objectives associated with the six

existing Remedial Action Scheme (RAS)/Special Protection System (SPS)-related standards: PRC-012-1 Remedial Action Scheme Review Procedure PRC-013-1 Remedial Action Scheme Database PRC-014-1 Remedial Action Scheme Assessment PRC-015-1 Remedial Action Scheme Data and Documentation PRC-016-1 Remedial Action Scheme Misoperations PRC-017-1 Remedial Action Scheme Maintenance and Testing*

* The maintenance of the Protection System components associated with RAS (PRC-017-1 Remedial Action Scheme Maintenance and Testing) are already addressed in PRC-005-2. PRC-012-2 addresses the testing of the non-Protection System components associated with RAS/SPS.

Project Scope


Phase 3• Consolidate the existing RAS-related standards into one

standard – PRC-012-2 Remedial Action Schemes• Correct the applicability of the fill-in-the-blank standards • Retire the term Special Protection System from the NERC

Glossary by replacing the term with the new term Remedial Action Scheme in the remaining NERC Reliability Standards

Project Objectives


• Nine Requirements Requirements R1 – R3: RAS review and approval by Reliability

Coordinator Requirement R4: RAS planning evaluation by Transmission Planner

o Effectivenesso Coordinationo Inadvertent operationo Single Component Failure

Requirement R5: RAS operational analysis by RAS-owner Requirement R6: Corrective Action Plan (CAP) development and

submittal by RAS-owner Requirement R7: CAP implementation by RAS-owner Requirement R8: Functional testing of RAS by RAS-owner Requirement R9: RAS database upkeep by Reliability Coordinator

PRC-012-2


Reliability Coordinator Areas


• Webinar on September 10, 2015• 45-day comment and initial ballot closes October 5, 2015 • SDT meeting scheduled for October 26-30, 2015

Going Forward


• Al McMeekin, Standards Developer [email protected] 404-446-9675

• Project page http://www.nerc.com/pa/Stand/Pages/Project-2010-05_3-

Remedial-Action-Schemes_Phase-3-of-Protection-Systems.aspx

• To receive project announcements and updates, request to be added to email distribution list: SPSSDT_Plus

Information


http://www.nerc.com/pa/Stand/Pages/Project-2010-05_3-Remedial-Action-Schemes_Phase-3-of-Protection-Systems.aspx

Topic 6: Update from the Standards Information group

Barb Nutter, Manager of Standards Information


• Standard Page Updates Reference Resources

• Standards Balloting and Commenting System (SBS) Registered Ballot Body (RBB) Registration Resetting SBS Password Commenting (Surveys) – providing red-lined documents

• Support

Agenda


• Left navigation on Standards page• Reference source

Provideso Open projects by

– Standards– Project Number

o Closed projects by– Standards– Project Number

Standards and Projects Cross Reference

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


• Left navigation of Standards page

Standards and Projects Cross Reference(cont’d)

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


• Left navigation on Standards page Link also on Reliability Standards Under Development

• Reference source provides Closed projects and project pages by

o Standardso Project Number

Archived Reliability Standards Under Development

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


• Left navigation of Standards page


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




• Appendix 3D – Registered Ballot Body (RBB) Criteria• RBB requests submitted for vetting Requestor provides: Name, Entity Name, Segment, Title, Phone Number,

Email Address NERC staff may request additional information

RBB Registration

http://www.nerc.com/FilingsOrders/us/RuleOfProcedureDL/Appendix_3D_BallotBodyCriteria_20131004.pdf


• Vote belongs to the company not the individual• Current voter changes position or leaves the company

Replacement voter should register to become a voter in the same segment as the current voter

Current and/or replacement voter, or manager should email [email protected] with confirmation on voter replacement

• Current voter is a registered in current ballot pools SBS will replace current voter with the replacement voter

Voter Replacement



The easiest way to reset your password

• Select Login• Continue to next screen

Resetting Your Password


• Select ‘Reset Password’ *Password must be exactly 8

characters long, contain one upper case letter, and one numeric character.

• User name is your email address

• Confirm email address• Complete ‘verify icon’• Submit Query• Verification email will be

received

Resetting Your Password (cont’d)


• Purpose of upload document feature Provide red-lined version of any posted documents Provide supplemental information to support your response to the

question

• Upload document feature should not be used for providing comments Up to 25MB file max size Executable (*.exe) and Archive (*.zip) files are not allowed

Upload Document Feature in the Survey (commenting)


• For SBS, RBB, and voter registration questions and to provide SBS feedback, contact administrative support at [email protected] or call 404-446-2560 (Monday – Friday, 8 a.m. - 4 p.m. Eastern). Please allow 1 - 2 business days for a staff member to respond to your inquiry.

• Trouble accessing the SBS due to a forgotten password, an error message due to incorrect credentials, or system lock-out, contact NERC IT support directly at [email protected](Monday – Friday, 8 a.m. - 8 p.m. Eastern).

SBS Support




• [email protected] Submit SARs, Interpretations, etc. Requests to be added to Standard Drafting Teams Plus distribution lists Questions or feedback on

o Standard Processes Manual o Documents or links on the Standards page

Other Standards Support


Topic 7: 2015 Fall Standards & Compliance Workshop

Laura Anderson, Standards Developer


• Dates: October 20-22, 2015

• Location: Westin San Diego, 400 West Broadway, San Diego, CA 92101

• Agenda: Draft agenda posted on the NERC website

• Registration: Deadline to register is October 13, 2015 Registration for In-Person Attendance Registration for Webinar Attendance

• For information, contact Laura Anderson, Standards Developer Email: [email protected] Telephone: (404) 446-9671

Workshop Information

http://www.nerc.com/pa/Stand/Workshops/2015%20Standards%20and%20Compliance%20Fall%20Workshop%20Agenda.pdf

https://www.eventbrite.com/e/2015-standards-and-compliance-fall-workshop-in-person-only-registration-17066257636

https://www.eventbrite.com/e/2015-standards-and-compliance-fall-workshop-webinar-only-registration-17067235561


Question & Answer Session

Closing Remarks
