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

Slides:



Advertisements
Similar presentations
NERC Reliability Readiness The Next Steps Mitch Needham NERC Readiness Evaluator September 24, 2007.
Advertisements

SYSTEM-WIDE PROCESS CONTROLS UPGRADE Detroit Water & Sewerage Department.
1 PER-005 Update Impact on Operators System Operator Conference April and May 1-3, 2012 Columbia, SC Margaret Stambach Manager, Training Services.
Goshen Area Bus Reconfiguration
NERC Lessons Learned Summary December NERC lessons learned published in December 2014 Three NERC lessons learned (LL) were published in December.
1 Disaster Recovery “Protecting City Data” Ron Bergman First Deputy Commissioner Gregory Neuhaus Assistant Commissioner THE CITY OF NEW YORK.
Information Systems Audit Program. Benefit Audit programs are necessary to perform an effective and efficient audit. Audit programs are essentially checklists.
© 2005, QEI Inc. all characteristics subject to change. For clarity purposes, some displays may be simulated. Any trademarks mentioned remain the exclusive.
DoD Information Technology Security Certification and Accreditation Process (DITSCAP) Phase III – Validation Thomas Howard Chris Pierce.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
September 2014 Lesson Learned Summary. September 2014 LLs 2 Three NERC lessons learned (LL) were published in September 2014 LL Redundant Network.
Introduction to Systems Analysis and Design
NERC Lessons Learned Summary
Workshop: The State of National Governance Relative to the International Health Regulations (2005) Ottawa, Canada, September 2006 Overview: United.
 Network Management  Network Administrators Jobs  Reasons for using Network Management Systems  Analysing Network Data  Points that must be taken.
Services Tailored Around You® Business Contingency Planning Overview July 2013.
Chapter 8.  Network Management  Organization Management  Risk Assessment & Management  Service Management  Performance Management  Problem Management.
ERCOT Compliance Audits Robert Potts Sr. Reliability Analyst March 23, 2005.
Solution Overview for NIPDEC- CDAP July 15, 2005.
PTCS Service Provider Review 0 Background RTF assumed responsibility for maintaining PTCS specifications in March 2003  Developed PTCS Service Provider.
Server Virtualization: Navy Network Operations Centers
11 SECURITY TEMPLATES AND PLANNING Chapter 7. Chapter 7: SECURITY TEMPLATES AND PLANNING2 OVERVIEW  Understand the uses of security templates  Explain.
Presentation by Paul Vine In partnership with Version Sabre and Business Continuity Planning.
IMPROUVEMENT OF COMPUTER NETWORKS SECURITY BY USING FAULT TOLERANT CLUSTERS Prof. S ERB AUREL Ph. D. Prof. PATRICIU VICTOR-VALERIU Ph. D. Military Technical.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 4 1 Chapter 4: Basics of Preventive Maintenance and Troubleshooting IT.
Peak RCCo Performance Metrics Draft –November 2013.
NERC Lessons Learned Summary April NERC lessons learned published in April 2015 Two NERC lessons learned (LL) were published in April 2015 LL
1 Availability Policy (slides from Clement Chen and Craig Lewis)
1 Texas Regional Entity 2008 Budget Update May 16, 2007.
EAS Lessons Learned Summary Lessons Learned Published in August 2014.
Troubleshooting Windows Vista Lesson 11. Skills Matrix Technology SkillObjective DomainObjective # Troubleshooting Installation and Startup Issues Troubleshoot.
Bill Lewis, Compliance Team Lead NERC Reliability Working Group May 16, 2013 Texas RE Update Talk with Texas RE April 25, 2013.
E.Soundararajan R.Baskaran & M.Sai Baba Indira Gandhi Centre for Atomic Research, Kalpakkam.
IT Essentials: PC Hardware and Software v4.0. Chapter 4 Objectives 4.1 Explain the purpose of preventive maintenance 4.2 Identify the steps of the troubleshooting.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 4 1 Chapter 4: Basics of Preventive Maintenance and Troubleshooting IT.
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.
Compliance Monitoring and Enforcement Audit Program - The Audit Process.
Chapter 12 Implementation and Maintenance
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.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Loss of EMS Events 2015 System Operator Seminar. Training Objectives 2 System Operators will be able to identify the ERO Event Analysis Process Category.
Operating Topics Part 2 Mike Oatts May 9, 2008 Transmission Customer Forum Destin, Florida Part 2 Mike Oatts May 9, 2008 Transmission Customer Forum Destin,
1 Power System Restoration. 2 Not Active 3 4 Compliance Audit Process APPA E&O Technical Conference – Atlanta April 16, 2007.
NERC Lessons Learned Summary LLs Published in December 2015.
Lead from the front Texas Nodal 1 Integrated ERCOT Readiness and Transition (IRT) TPTF – December 4 th, 2006 ERCOT Qualification.
CIIMS Update Stacen Tyskiewicz CIIMS Chair March 22, 2016.
Troubleshooting Windows Vista Lesson 11. Skills Matrix Technology SkillObjective DomainObjective # Troubleshooting Installation and Startup Issues Troubleshoot.
©2003 PJM 1 Presentation to: Maryland Public Service Commission May 16, 2003.
Blackstart Hugh Francis Southern Company Transmission Customer Forum September 22, 2006 Hugh Francis Southern Company Transmission Customer Forum September.
NERC EAS Update WECC OPEAS Meeting 01/26/2016 Rich Hydzik.
The Troubleshooting Process. Hardware Maintenance Make sure that the hardware is operating properly.  Check the condition of parts.  Repair or replace.
NERC Reliability Readiness The Next Steps
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
NERC Published Lessons Learned
EAS Lessons Learned Summary
NERC Published Lessons Learned
NERC Published Lessons Learned Summary
NERC Published Lessons Learned
Audit Plan Michelangelo Collura, Folake Stella Alabede, Felice Walden, Matthew Zimmerman.
“TOP-010-1: Data Quality, Analysis Quality, and Alarm Process Monitor”
Lessons learnt from the August trial electronic examinations
IT OPERATIONS Session 7.
Presentation transcript:

NERC Lessons Learned Summary March 2015

NERC lessons learned published in March 2015 Two NERC lessons learned (LL) were published in March2015 LL Importance of Backup Energy Management System Failover Testing after Network Device Reconfiguration LL Importance of State Estimator save Cases and Troubleshooting Guide

Importance of Backup Energy Management System Failover Testing after Network Device Reconfiguration Performing maintenance on the primary control center’s (PCC) uninterruptable power supply (UPS), all functionality of the EMS system, including the communication circuits, were successfully transferred from the PCC to the alternate control center (ACC) After maintenance was complete EMS analysts attempted to bring system functionality back to the PCC but the attempt was unsuccessful Full system restart was then performed to establish system functionality at the PCC

Importance of Backup Energy Management System Failover Testing after Network Device Reconfiguration PCC came on-line, but the ACC failed, and EMS analysts were unable to restore ACC functionality EMS functionality was lost due to communication circuits still connected to the failed ACC It should be noted that an EMS loss-of-functionality event will occur every time a full system restart is performed, and the duration of a typical event is five to eight minutes. Loss of EMS/SCADA functionality for 49 minutes during a scheduled transfer of the EMS from the alternate control center (ACC) to the primary control center (PCC)

Importance of Backup Energy Management System Failover Testing after Network Device Reconfiguration Upon subsequent investigation, it was discovered that due to a recent and extensive network device reconfiguration, one of the parameters was in error, and this resulted in the inability to restore ACC functionality via a full system restart Device configuration modifications were then performed, and the ACC was successfully restarted with functionality restored

Importance of Backup Energy Management System Failover Testing after Network Device Reconfiguration EMS maintenance and reconfiguration operations should be closely coordinated with vendors that are needed to support the changes to ensure that there are no overlaps in planned maintenance schedules Succinct and accurate communication between registered entities and vendors is essential to ensure that both parties fully understand their roles and obligations during planned maintenance operations Procedures for EMS system restart operations should be rigorously documented to ensure that the EMS can be restarted in the most rapid and secure manner

Importance of Backup Energy Management System Failover Testing after Network Device Reconfiguration Step-by-step checklist for the procedure is desirable to ensure that no steps are overlooked Entities should periodically review EMS redundancy to ensure ongoing independence between sites, including full functional failover testing. Entities should review and identify the extent of testing to be performed following significant EMS infrastructure reconfiguration.

Importance of State Estimator save Cases and Troubleshooting Guide State estimator (SE) failed to solve for 37 minutes, resulting in real- time contingency analysis (CA)also being unavailable During this event, operators had system visibility via SCADA and could still take control actions, including the ability to shed load Inter-Control Center Communications Protocol (ICCP) continued to function, providing real-time data to the RC and the other local entities in the RC’s footprint Entity confirmed with its RC that the RC’s SE and provide real-time CA

Importance of State Estimator save Cases and Troubleshooting Guide A SE should be able to automatically and frequently save cases to assist in post-event analysis. It should also automatically save non convergent cases Operators and support staff should have clear guidance and training on troubleshooting state estimator failures. An online state estimator guide for systems operators should be available to ensure consistent troubleshooting. Periodic refresher training should also be employed, including reviews of recent aborted cases. A joint review of state estimator issues with other entities should be periodically conducted to ensure applicable common solutions are implemented.

Link to Lessons Learned Directions to Lessons Learned: Go to > “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. The survey link is provided on each Lesson Learned.

Questions?