Adding UFR Deployments to Reliability Adder Telemetry
"Explore the integration of Load Resource UFR Deployments in the Reliability Price Adder by identifying triggers, implementing modifications, and ensuring accurate capacity measurements during deployment and recovery. Learn about the telemetry requirements, deployment triggers, recall process, and recovery period for enhanced reliability. Find out how to reflect schedule changes with UFR deployments and ensure proper load recovery following recalls."
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
UFR Deployments and the Reliability Adder QMWG August 30, 2016 ERCOT Staff
Adding LR UFR Deployments to the Reliability Adder Telemetry is available for all LRs providing RRS Resource Status ONRL RRS Responsibility and RRS Schedule Net Power Consumption Low Power Consumption UFR Status Armed or Online when active Circuit Breaker Status Closed when active RRS Schedules do not change during a UFR type deployment No electronic instruction for dispatch or recall for UFR deployments currently only have a verbal instruction for the recall Ancillary Service Monitor relies on difference between RRS Responsibility and RRS Schedule to show quantity that has been deployed and as a result it does not show the amount deployed for UFR deployments To add this capacity to the Reliability Adder, we need to identify a deployment trigger, a recall trigger and a way to measure the amount of capacity that tripped on under- frequency and its recovery following the recall. None of these items are currently in our systems today. 2 PUBLIC
Possible Approach to include UFR Load Deployments in the Reliability Price Adder The following would only apply to LRs with ONRL COP status Deployment Trigger New resource specific telemetry requirement signaling relay trip Many UFRs already have this capability Cost to implement for the Providers may be significant if field visits and relay changes are required Capacity (MW) ERCOT Calculated Value Net Power Consumption (T-1 minute) Net Power Consumption (NPC) Recall Trigger Modification to the ERCOT Deployment Manger Add XML signal from the ERCOT Operator Recovery Period Back out capacity using NPC and RRS Responsibility Note: Additional emphasis should be added to require QSE s to reflect schedule changes with UFR deployments and recovery of load following recall. 3 PUBLIC
Load Resource RRS UFR Deployments Load Resource Deployment Summary 2012 to Present 2012 Duration (min) Amount of Response (MW) Date Time Type of Deployment UF Event for frequency near 59.7 Hz that caused some Load Resources to trip offline UF Event for frequency near 59.7 Hz that caused some Load Resources to trip offline 7/10/2012 20:46 14 198 7/30/2012 16:03 13 324 11/2/2012 1:41 11 882 UF Event for frequency < 59.7 Hz but of uncertain duration 2013 Duration (min) Amount of Response (MW) Date Time Type of Deployment UF Event for frequency near 59.7 Hz that caused some Load Resources to trip offline UF Event for frequency near 59.7 Hz that caused some Load Resources to trip offline UF Event for frequency near 59.7 Hz that caused some Load Resources to trip offline 1/4/2013 9:41 20 572 1/8/2013 16:40 10 974 11/1/2013 21:47 10 463 2014 Duration (min) Amount of Response (MW) Date Time Type of Deployment UF Event for frequency near 59.7 Hz that caused some Load Resources to trip offline; resulted in EEA Level 1 event. 1/18/2014 8:41 59 850 2015 Duration (min) Amount of Response (MW) Date Time Type of Deployment UF Event for frequency near 59.7 Hz that caused some Load Resources to trip offline 7/29/2015 18:16 10 22 2016 Duration (min) Amount of Response (MW) Date Time Type of Deployment UF Event for frequency near 59.7 Hz that caused some Load Resources to trip offline 5/1/2016 20:20 4 927 4 PUBLIC
