EAS Lessons Learned Summary

Slides:



Advertisements
Similar presentations
Summary of Second Draft of the NERC Standard PRC Disturbance Monitoring and Reporting JSIS Meeting August 10, 2010 Salt Lake City, UT.
Advertisements

1. Four LLs were published in February Transmission Relaying – Undesired Blocking 2.Lack of Separation for Critical Control Power Supply Leads.
Revised Event Analysis Process Event Analysis Subcommittee (EAS) Process Update Team (EUT) Hassan Hamdar – FRCC Reliability Engineer, EAS Vice-Chair FRCC.
1 PER-005 Update Impact on Operators System Operator Conference April and May 1-3, 2012 Columbia, SC Margaret Stambach Manager, Training Services.
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.
1. 11/26/2012: NERC Board of Trustees adopted CIP v5 CIP thru CIP CIP and CIP Version 5 Filing FERC requested filing by 3/31/2013.
Lesson 11-Virtual Private Networks. Overview Define Virtual Private Networks (VPNs). Deploy User VPNs. Deploy Site VPNs. Understand standard VPN techniques.
September 2014 Lesson Learned Summary. September 2014 LLs 2 Three NERC lessons learned (LL) were published in September 2014 LL Redundant Network.
MCDST : Supporting Users and Troubleshooting a Microsoft Windows XP Operating System Chapter 5: User Environment and Multiple Languages.
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
5 Copyright © 2008, Oracle. All rights reserved. Configuring the Oracle Network Environment.
5 Copyright © 2007, Oracle. All rights reserved. Configuring the Oracle Network Environment.
11 Copyright © 2005, Oracle. All rights reserved. Configuring the Oracle Network Environment.
Current Job Components Information Technology Department Network Systems Administration Telecommunications Database Design and Administration.
11 Copyright © 2005, Oracle. All rights reserved. Configuring the Oracle Network Environment.
APS Dual Site ECC Primary Site Shutdown/Restart CIPC Confidentiality: Public Release.
David N. Wozei Systems Administrator, IT Auditor.
NERC Lessons Learned Summary April NERC lessons learned published in April 2015 Two NERC lessons learned (LL) were published in April 2015 LL
Monitoring EMS Infrastructure Ann Moore San Diego Gas & Electric September 13, 2004 EMS Users Group Meeting-St. Louis.
EAS Lessons Learned Summary Lessons Learned Published in August 2014.
6 Copyright © 2009, Oracle. All rights reserved. Configuring the Oracle Network Environment.
Bill Lewis, Compliance Team Lead NERC Reliability Working Group May 16, 2013 Texas RE Update Talk with Texas RE April 25, 2013.
© Property of ERCOT /06/20041 Overview of SPS in ERCOT February 5, 2004.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—1-1 Planning Routing Services Creating an Implementation Plan and Documenting the Implementation.
NERC Lessons Learned Summary February NERC lessons learned published in February 2015 Two NERC lessons learned (LL) were published in February 2015.
11 CLUSTERING AND AVAILABILITY Chapter 11. Chapter 11: CLUSTERING AND AVAILABILITY2 OVERVIEW  Describe the clustering capabilities of Microsoft Windows.
EAS Lessons Learned Summary Lessons Learned Published in June 2014.
Lesson 12: Configuring Remote Management
Loss of EMS Events 2015 System Operator Seminar. Training Objectives 2 System Operators will be able to identify the ERO Event Analysis Process Category.
NERC Lessons Learned Summary LLs Published in September 2015.
NERC Lessons Learned Summary LLs Published in December 2015.
1 Compliance Update April Control Performance Highlights  NERC CPS1 Performance Performance further declined in March  March performance comparison.
MCSA Windows Server 2012 Pass Upgrading Your Skills to MCSA Windows Server 2012 Exam By The Help Of Exams4Sure Get Complete File From
Summary Event Analysis Subcommittee – LL Update NERC OC Meeting - June 2014.
NERC EAS Update WECC OPEAS Meeting 01/26/2016 Rich Hydzik.
Cyber Security of SCADA Systems Testbed Development May1013 Group Members: Ben Kregel Justin Fitzpatrick Michael Higdon Rafi Adnan Adviser: Dr. Manimaran.
MOPC Meeting Oct , 2016 Little Rock, AR
NERC Published Lessons Learned Summary
NERC Published Lessons Learned
NERC Published Lessons Learned Summary
NERC Published Lessons Learned
NERC Lessons Learned Summary
NERC Published Lessons Learned
“FRCC RESTORATION PLAN (BLACKOUT & BLACK START)” - TRAINING -
Black Start Overview.
Phase Angle Limitations
Summary Rich Bauer, Senior Reliability Engineer
NERC Published Lessons Learned
NERC Published Lessons Learned
NERC Published Lessons Learned Summary
Direct Attached Storage and Introduction to SCSI
NERC Published Lessons Learned Summary
How SCADA Systems Work?.
PRC Implementation Plan and Summary of Devices
NERC Published Lessons Learned
MONITORING MICROSOFT WINDOWS SERVER 2003
NAT , Device Discovery Chapter 9 , chapter 10.
Removal of Fraser RAS from RAS Databse
NERC CIP Implementation – Lessons Learned and Path Forward
Peter Erning, PSP-T11, Power Gen 2010
“TOP-010-1: Data Quality, Analysis Quality, and Alarm Process Monitor”
Primary Site Shutdown/Restart
Power System Protective Relaying-Part One
New features, more applications with PQube 3 Power Analyzers
Removal of Fraser RAS from RAS Databse
Distance Relay Specification
Long Island Interconnection Working Group Meeting August 22, 2019
Presentation transcript:

EAS Lessons Learned Summary Lessons Learned Published in June 2014

June 2014 Lessons Learned Three NERC lessons learned (LL) were published in June 2014 LL20140601 - Generation Relaying - Underfrequency Protection Coordination LL20140602 - Generation Relaying - Overexcitation LL20140603 - Verify That Actions Called for in Operating Guides Can Be Implemented Within Required Time Frames LL20140604 - Loss of SCADA Due to Memory Resources Being Fully Utilized

Generation Relaying - Overexcitation New microprocessor relay added to generator’s protection system. Included Volts/HZ function to protect for overexcitation Engineer duplicated existing Volts/HZ setting in new relay Existing Volts/HZ relay was a definite time characteristic and the new relay Volts/HZ element was an inverse time characteristic **Settings needed to be different During testing the unit tripped on Volts/HZ before the units overexcitation limiter actuated and below actual capability of unit LL: Do not assume new elements can be set with the same settings as the existing relays LL: When setting overexcitation elements, trip function needs to be coordinated with units excitation limiter

Generation Relaying – Auxiliary Equipment Underfrequency Protection Coordination Unit auxiliary (aux) equipment protection contained underfrequency tripping This underfrequency protection tripped the aux equipment during a system disturbance The aux equipment tripping resulted in the generator tripping (due to loss of boiler / turbine) It was determined that the aux equipment underfrequency protection was not needed and was disabled LL: Critical plant aux equipment protection should be reviewed to ensure it does not unnecessarily cause a generator trip during system disturbances

Included the TOP turning off auto reclosing on circuit breaker Verify Actions in Operating Guides Can Be Implemented Within Required Time Frames Operating Guides contained time requirements that did not consider the ability of Operating Personnel to complete task Required that actions be taken within 30 minutes to protect local generation Included the TOP turning off auto reclosing on circuit breaker Required dispatching personnel to the substation TOP was informed TO personnel would take longer than 30 minutes to reach the substation LL: Review procedures to verify documented actions can be accomplished within the specified time LL: When developing operating plans (etc.), must consider real- time requirements and involve all stakeholders or parties that have actions in the plans

Loss of SCADA Due to Memory Resources Being Fully Utilized Loss of EMS due to memory resources (MR) on primary server being overworked by SSH sessions from another SCADA host SSH session repeatedly initiated commands Discrepancy in EMS file host-naming convention caused the MR to exceed maximum capacity Some protocols used in communication front-end processors did not support the Network Address Translation used in failover Host names on the host file were corrected and tested. Configuration settings modified - front-end processor at backup used in the event the primary fails LL: SCADA host resources to include monitoring and alarming of crucial events and server resources for SA Secure Shell (SSH) memory resources (MR)

Links to Lessons Learned Link to Lessons Learned Directions to Lessons Learned: Go to www.NERC.com > “Program Areas & Departments” tab > “Reliability Risk Management” (left side menu) > “Event Analysis” (left side menu) > “Lessons Learned” (left side menu) 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.

Questions For more information please email: Nerc.LessonsLearned@nerc.net