70 likes | 174 Views
Texas Nodal EMS Forced Outage Detection Business Requirements Document Carlos Gonzalez-Perez – August 21 st , 2006. Document Contents. Proposed System Scope As is and To be Sub processes Assumptions and Dependencies Definitions and Acronyms Functional Requirements Supplementary Requirements
E N D
Texas NodalEMS Forced Outage DetectionBusiness Requirements DocumentCarlos Gonzalez-Perez – August 21st, 2006 http://nodal.ercot.com 1
Document Contents • Proposed System Scope • As is and To be Sub processes • Assumptions and Dependencies • Definitions and Acronyms • Functional Requirements • Supplementary Requirements • Sub-Process Coverage • Protocols Coverage • FOD Activity Map http://nodal.ercot.com 2
Scope, Business Sub Processes and Assumptions • Proposed System Scope • FOD is a new application to detect and alarm unplanned status changes in transmission elements and generation resources • Business Processes impacted: • Operations Support Engineering • Outage Coordination • Business Sub process • The FOD function is not currently in place. NO As-If Process • No To-be Sub process generated for FOD • Assumptions: • The Network Real Time Operational Model used in the real time sequence is available to FOD. • Outage Scheduler (OS) DB is populated with up-to-date planned schedules • Telemetered Resource Status the same as in COPs • SCADA manual overrides will be available to FOD http://nodal.ercot.com 3
Activity Diagram for Forced Outage Detection http://nodal.ercot.com 4
Functional Requirements • FOD-FR1: Forced Output Input • Real Time Telemetry, OS and COP with resource status • FOD-FR2: Force Outage Cycle • The application will execute periodically. Period to be configurable • FOD-FR3: State Change Alarm • Detect and alarm for unplanned status change of Breaker/switch, Status for Resources, Transmission Lines, Transformers and Load disconnection • FOD-FR4: Forced Outage Detection • Detect change in status • Check for the outage in the OS. • Discrepancies of more than xx minutes indicate Forced Outage • Alarm/Display of forced outages • COPS used to distinguish between forced resource outage or shutting down generation • FOD-FR5: Resource Status Deviation • Checking conflicts in the resource status against COPS, OS, and Resource Status from SCADA. • FOD-FR6: Force Outage Display. According to outage type and other custom filtering • FOD-FR7: Forced Outage Continued Alarming. Alarm is generated when the Forced Outage is detected and not corrected in the OS after 2 hours. The alarm is persistent every 15 minutes • FOD-FR8: Forced Outage and QSE Performance Reporting Input. FOD outputs need to be archived for audit and reporting purposes. http://nodal.ercot.com 5
Supplementary Requirements • FOD-SR1: No degradation of Performance. • Automatic re-starting • FOD shall finish processing before the end of each cycle • FOD-SR2: Interfaces • SCADA • Outage Scheduler • COP • FOD-SR2: User Interface • Special displays will be generated for FOD http://nodal.ercot.com 6
Protocol Coverage http://nodal.ercot.com 7