1 / 6

EAS Lessons Learned Summary

EAS Lessons Learned Summary. Lessons Learned Published in August 2014. August 2014 Lessons Learned. Two NERC lessons learned (LL) were published in August 2014 LL20140801 - Load-Shedding Plans for Localized Events

venus
Download Presentation

EAS Lessons Learned Summary

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EAS Lessons Learned Summary Lessons Learned Published in August 2014

  2. August 2014 Lessons Learned Two NERC lessons learned (LL) were published in August 2014 LL20140801 - Load-Shedding Plans for Localized Events LL20140802 - Loss of EMS Monitoring and Control Functionality for More Than 30 Minutes

  3. Load-Shedding Plans for Localized Events • Fire protection system on the 345/115 kV transformer activated isolating the transformer • Separation resulted in a loss of voltage support from 345 kV systems to 115 kV systems in the area • Reduction in voltage (86%) led to loss of 360 MW coal unit • SO placed all Caps in-service and increased reactive on gens • Additional gens couldn’t start-up due to low voltage • No load-shedding plan to solve a local area voltage issue • SOs should have flexible load shedding plans to local area issues • SOs should have continual training and guidance on load shedding plans

  4. Loss of EMS Monitoring and Control Functionality for More Than 30 Minutes • System failure triggered by insufficient amount of disc storage space for the Oracle recovery log area • No Oracle services terminated as a result • Oracle saves all changes/updates in “redo logs” as backup • No storage space in recovery log area led to storage on EMS server • Oracle connection was lost and the back-up and alternate EMS servers were notified to failover • Failover timed-out on initiating functional primary EMS server • Caused server to be brought down (failure-detection strategy) • Other servers not acting as primary since the failover timed-out • Set high alarm priority to Relational Database Management System (RDBMS) going online and offline

  5. 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’sgoal 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.

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

More Related