Presentation on theme: "Reliability Software1 Reliability Software Minimum requirements & Best practices Frank Macedo - FERC Technical Conference July 14, 2004."— Presentation transcript:
Reliability Software1 Reliability Software Minimum requirements & Best practices Frank Macedo - FERC Technical Conference July 14, 2004
Reliability Software2 Blackout report findings Inadequate situational awareness by the local grid operators and Reliability Coordinators prevented effective action
Reliability Software3 Objectives What are the minimum real-time application & tool requirements for grid reliability ? What are the best available applications & tools for grid reliability ?
Reliability Software4 Functional Areas Network analysis Monitoring and visualization Real-time enablers Operations planning Transactions scheduling History & forecasting
Reliability Software5 Caveat The minimum requirements and performance indicies quoted are considered to be commercially achievable and are not intended to be regulatory requirements. Their purpose is to initiate industry discussion on what these minimum reliability capabilities ought to be.
Reliability Software6 Network Analysis Minimum Network topology processor (Detailed network & adequate external representation) State estimator (< 2 min., mismatch < 10 MVA) Real time contingency analysis (< 5 min. on 100 kV and above plus external critical facilities) Best practice Critical facility loading assessment (use of Line Outage Dist Factors) Dynamic security assessment (transient & voltage stability limits) RT thermal capability assessment (based on prevailing pre-load and ambient or dynamic field measurements) RT short-circuit assessment (based on prevailing network and generation)
Reliability Software7 Monitoring & Visualization Minimum Wide area visualization (critical facilities external to the footprint) Dynamic reactive reserve/Minimum voltage (required & actual) Remedial Action Schemes (status, trigger points & proximity) Automatic safety nets (under frequency load shedding, under voltage load shedding) Status of EMS facilities (servers, back-up systems, communications, functionality) Best Practice Dynamic Map Board driven by EMS Capability for remote access and navigation (network conditions and Contingency Analysis results) Electronic documentation (critical operating information linked to facilities on network topology)
Reliability Software8 Real-Time Enablers Minimum Intelligent alarm processing (filtering, prioritization, grouping) Block load shedding (<10 min. capability) ACE/AGC Remote back-up EMS, voice & data communications Best Practice Generation of options to return system to secure operating state
Reliability Software9 Operations Planning Minimum Outage scheduling (assess impact of outages using historical data & ac Load Flow) “Study Mode” capability (study “what-if” scenarios using a real-time snapshot of the system) Generation reserve sharing (allocation of reserves among units) Best Practice Rehearsal of next day’s operation (simulate all outages & test using contingency analysis in “study mode”)
Reliability Software10 Transactions Scheduling Minimum Interchange distribution calculator (IDC) System data exchange (SDX) updated (<15 min of outage) E-tag approval/scheduling OASIS Best Practice Automatic update of IDC Identification of full range of mitigation options for TLR
Reliability Software11 History & Forecasting Minimum Weather data (forecast high risk conditions) Load forecasts (short term & next day) Information storage & retrieval (IS&R) (reconstruction of events, proactive inspection & maintenance of critical assets) Best Practice IS&R linked to Asset Management System & Training Simulator (automatic generation of directives on equipment testing and maintenance. Scenarios for training)
Reliability Software12 Issues Network & measured data maintenance State estimator maintenance IT – Operations interactions & quality control Data sharing outside of footprint Human factors engineering Training Simulator