NERC Published Lessons Learned

Slides:

Advertisements

Similar presentations

NAESB Coordinate Interchange Standard, Version 1 / 0

Advertisements

Governor Droop Criteria

1. Four LLs were published in February Transmission Relaying – Undesired Blocking 2.Lack of Separation for Critical Control Power Supply Leads.

PER Update & Compliance Lessons Learned

NERC Lessons Learned Summary December NERC lessons learned published in December 2014 Three NERC lessons learned (LL) were published in December.

EAS Lessons Learned Summary Lessons Learned Published in May 2014.

System Operator Conference NERC Standards Review for: Simulator Drill Orientation 2014 System Operator Conferences Charlotte NC & Franklin TN SERC/SOS.

CIP Version 5 Update OC Meeting November 7, 2013.

Managing the Information Technology Resource Jerry N. Luftman

MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.

Electricity Markets Overview Lo-Cal seminar, 09/21/2010.

7.2 System Development Life Cycle (SDLC)

NERC BAL Frequency Response Reliability Standard

September 2014 Lesson Learned Summary. September 2014 LLs 2 Three NERC lessons learned (LL) were published in September 2014 LL Redundant Network.

NERC Lessons Learned Summary March NERC lessons learned published in March 2015 Two NERC lessons learned (LL) were published in March2015 LL

NERC Lessons Learned Summary

System Implementation

E.R.P.S University of Palestine. Risks in an ERP environment : The use of ERP systems clearly introduces additional risks into the system environment.

Averting Disaster - Grid Reliability Issues and Standards National Energy Restructuring Conference April 1, 2004 Washington, DC.

Module 10 Session 10.4 Visual 1 Module 10 Organizing Procurement Session 10.4 Procurement of Services: Use of Consultants and Developing Terms of Reference.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.

NERC Lessons Learned Summary April NERC lessons learned published in April 2015 Two NERC lessons learned (LL) were published in April 2015 LL

SPP.org 1. EMS Users Group – CIP Standards The Compliance Audits Are Coming… Are You Ready?

Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.

Committee of Sponsoring Organizations of The Treadway Commission Formed in 1985 to sponsor the National Commission on Fraudulent Financial Reporting “Internal.

EAS Lessons Learned Summary Lessons Learned Published in August 2014.

Status Report for Critical Infrastructure Protection Advisory Group

Project System Protection Coordination Requirement revisions to PRC (ii) Texas Reliability Entity NERC Standards Reliability Subcommittee.

Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.

1Texas Nodal Market Trials Update. 2Texas Nodal Full System Market and Reliability Test 24-Hour Test Observations Duration of Test for Week of 8/ Hour.

1 Compliance Update May Control Performance Highlights  NERC CPS1 Performance Performance further declined in March  March performance comparison.

NERC Lessons Learned Summary February NERC lessons learned published in February 2015 Two NERC lessons learned (LL) were published in February 2015.

EAS Lessons Learned Summary Lessons Learned Published in June 2014.

2013 Wind Conference. Congestion Management & Communication Processes CJ Brown.

Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.

NERC Lessons Learned Summary LLs Published in September 2015.

Implementing Multiagency Coordination IS-701.A – February 2010 Visual 4.1 Unit 4: Implementing Multiagency Coordination.

NERC Lessons Learned Summary LLs Published in December 2015.

NPRRs NPRR649 Lost Opportunity Payments for HDL Manual Overrides. This Nodal Protocol Revision Request (NPRR) proposes two options for a lost opportunity.

RA workshop presentation Karl Meeusen, Ph.D. Senior Advisor – Infrastructure Policy CPUC Resource Adequacy Workshop February 18, 2016.

 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,

NERC Published Lessons Learned Summary

Introduction to CAST Technical Support

NERC Published Lessons Learned

NERC Published Lessons Learned Summary

NERC Lessons Learned Summary

NERC Published Lessons Learned

System Design, Implementation and Review

Current FRRS Language & Explanation of Posted Data

Phase Angle Limitations

EAS Lessons Learned Summary

NERC Published Lessons Learned

NERC Published Lessons Learned Summary

Overview of New Control Room Desk

NERC Published Lessons Learned Summary

Reasons for Auditing There are many reasons for auditing. Some examples of these reasons might be: Requested by the IRB Committee Requested by an IRB.

Western Electricity Coordinating Council

Lecture 6. Information systems

NERC Published Lessons Learned

IS442 Information Systems Engineering

Bomgar Remote support software

Automatic Generation Control (AGC)

Module 4 Smart Grid Implementation Issues

NERC OC Update Greg Park, NWPP (In place of Rich Hydzik)

Sixth Meeting of the Statistical Commission for Africa

Analytical Method Validation PAI Readiness / Certification

SRWG Chair Report March 2015 WECC HQ

NERC OC Update Greg Park, NWPP (In place of Rich Hydzik)

NERC Congestion Management

Energy Storage Roadmap & Flexibility Roadmap Information Session

Presentation transcript:

NERC Published Lessons Learned April 2017

NERC Lessons Learned One Lessons Learned (LL) was published in April 2017 LL20170401 Dispatched Reduction in Generation Output Causes Frequency Deviation

Dispatch Causes Frequency Deviation - Details Inadequate data definition resulted in transfer of incomplete data to security-constrained economic dispatch unit commitment software This resulted in undesirable unit commitment outputs from the BA’s dispatch software SOs attempted to intervene, however, some dispatch instructions could not be blocked or overridden There was a large reduction in generation output that caused the BA’s ACE and system frequency to deviate for almost 20 minutes

Dispatch Causes Frequency Deviation

Dispatch Causes Frequency Deviation

Dispatch Causes Frequency Deviation – Corrective Actions Resolve the data transfer design that led to the data inconsistency in the unit commitment software Improve existing automated controls to block dispatches that exceed certain criteria Improve SO manual intervention capabilities Entity developed additional manual controls for SOs and support personnel until software and automation improvements can be implemented SOs involved in the event developed lessons learned training for SOs and support personnel

Dispatch Causes Frequency Deviation – Lessons Automated & manual controls for dispatch software should be reviewed, tested, and SOs trained in its use periodically under various conditions SO and/or GOPs should be able to intervene to override automated dispatch signals BAs should review ramp rates of fast-ramping resources and determine the ramping that can be absorbed at steady state SOs & support staff should have guidance & training on troubleshooting security-constrained economic dispatch software issues

Lessons Learned Survey Link NERC’s goal with publishing lessons learned is to provide industry with technical and understandable information that assists them with maintaining the reliability of the bulk power system NERC requests that industry provide input on lessons learned by taking the short survey. A link is provided in the PDF version of each Lesson Learned

Hassan Hamdar hhamdar@frcc.com