190 likes | 204 Views
Updated Analysis of Non-Spin Deployments and RUC. John Dumas Director Wholesale Market Operations. Outline of Presentation. July 13 & July 18 : Results of SCED Re-Run: LSL=0, LDL recalculated for different “floor” scenarios August 8, 2011: Non-Spin Deployment
E N D
Updated Analysis of Non-Spin Deployments and RUC John Dumas Director Wholesale Market Operations Reliability Deployments Task Force Meeting
Outline of Presentation • July 13 & July 18 : Results of SCED Re-Run: LSL=0, LDL recalculated for different “floor” scenarios • August 8, 2011: Non-Spin Deployment • Summary of August 8 Non-Spin Deployment • Discussion of Adjusting Non-Spin Deployment and Recall • Discussion of Adjusting RUC Approach Reliability Deployments Task Force Meeting
July 13 & July 18 : Results of SCED Re-Run: LSL=0, LDL recalculated for different “floor” scenarios Reliability Deployments Task Force Meeting
August 8, 2011: Non-Spin Deployment • All Non-Spin deployed at 14:56 in the amount of 1540.70 MW • Continued All Non-Spin deployment at 17:02 in the amount of 1626.74 MW • All Non-Spin recalled at 18:41 • @14:56, of the total 1540.7 MW of Non-Spin Responsibility, 1103 MW Non-Spin ALREADY available to SCED from Online QSGR. • Between 14:52 and 15:56 - PRC went below 2500. • Between 17:00 and 18:00 PRC went below 2500. • Between 14:25 and 17:30 the Avail_CAP_30MIN went below 1000 MW (negative for some 5 minute intervals) and SHDL-GTBD went below 200 after 16:10 (29.11 MW @16:52) • Load Forecast for HE 15 = 64464 MW • Load Forecast for HE 16 = 66355 MW • Load Forecast for HE 17 = 67195 MW • Load Forecast for HE 18 = 66668 MW Reliability Deployments Task Force Meeting
August 8, 2011: Non-Spin Deployment • Telem Non-Spin Responsibility @14:55=1540 • Telem Non-Spin Responsibility @15:25=1657 • Telem Non-Spin Responsibility @17:00=1627 • @14:55 System_Lambda=$725.83 • @15:25System_Lambda=$60.13 • Load increase from 14:55 to 15:25 = 564.9 MW • LSL injection from OFFNS resources from 14:55 to 15:25 = • 0 (“OFFNS” QSGR) + 101 (“OFFNS” Non-QSGR) = 101 MW Reliability Deployments Task Force Meeting
August 8, 2011: Non-Spin Deployment (continued) • Note 1: All are telemetry values at 14:55 (before Non-Spin Deployment) • Note 2: The total HSL from “OFF” Generation Resources that came online = 206 MW Reliability Deployments Task Force Meeting
August 8, 2011: Non-Spin Deployment (continued) Reliability Deployments Task Force Meeting
August 8, 2011: Non-Spin Deployment (continued) OFFNS Non-QSGR resources carrying Non-Spin: Aggregated EOC from LSL to HSL Reliability Deployments Task Force Meeting
August 8, 2011: Non-Spin Deployment (continued) Online Non-QSGR resources carrying Non-Spin: Aggregated EOC from HASL to HASL+Non-Spin Reliability Deployments Task Force Meeting
Summary of August 8 Non-Spin Deployment • Price is $725.83 just before Non-Spin Deployment • Note all QSGR are online. • Price reduction 30 minutes after Non-Spin deployed is due to additional EOC available to SCED at low price. Reliability Deployments Task Force Meeting
August 8: Results of SCED Re-Run for different “floor” scenarios Reliability Deployments Task Force Meeting
Current Non-Spin Deployment based on “HDL-GTBD” • If SHDL – GTBD <= 200 AND Avail_Cap30Min < 1000 MW; >>>> deploy HALF of Non-Spin. (Partial deployment of Non-Spin) • If SHDL – GTBD <= 200 AND Avail_Cap30Min < 500 MW; >>>> deploy ALL Non-Spin. (Full deployment of Non-Spin) Avail_Cap30Min = SHASL – GTBD – 30MinLoadRamp 30MinLoadRamp=( NextHourLoadForecast – CurrentHourLoadForecast)/2 Reliability Deployments Task Force Meeting
Illustrative Example of Revision to Deployment Based on “HDL-GTBD” (Section 3.4 of RT Desk Operating Procedure ) • If SHDL – GTBD <= 400 AND Avail_Cap30Min < 1000 MW; Then deploy all of On-Line Non-Spin [Starts earlier with On-Line only] • If SHDL – GTBD <= 200 AND Avail_Cap30Min < 1000 MW; Then deploy HALF of Off-Line Non-Spin. (Partial deployment of Off-Line Non-Spin) • If SHDL – GTBD <= 200 AND Avail_Cap30Min < 500 MW; Then deploy ALL Non-Spin. (Full deployment of Non-Spin) Avail_Cap30Min = SHASL – GTBD – 30MinLoadRamp 30MinLoadRamp=( NextHourLoadForecast – CurrentHourLoadForecast)/2 Reliability Deployments Task Force Meeting
Additionally Current Non-Spin Deployment based on “PRC” • If Physical Responsive Capability (PRC) < 2500 MW – deploy enough to recover PRC to 2500 (Partial deployment of Non-Spin) • If Physical Responsive Capability (PRC) < 2300 MW – deploy ALL Non-Spin. (Full deployment of Non-Spin) • Physical Responsive Capability = S Min (Max ((HSL – TelemMW), 0.0), 0.2*HSL) for online units + RRS from Load Resources Reliability Deployments Task Force Meeting
Illustrative Example on Revision to Deployment Based on “PRC” (Section 5.2 of RT Desk Operating Procedure) • If Physical Responsive Capability (PRC) < 2700 MW; Then deploy all On-Line Non-Spin (Partial deployment of Non-Spin) • If Physical Responsive Capability (PRC) < 2500 MW; Then deploy enough Off-Line Non-Spin to recover PRC to 2500 (Partial deployment of Non-Spin) • If Physical Responsive Capability (PRC) < 2300 MW; Then deploy ALL Non-Spin. (Full deployment of Non-Spin) • Physical Responsive Capability = S Min (Max ((HSL – TelemMW), 0.0), 0.2*HSL) for online units + RRS from Load Resources Reliability Deployments Task Force Meeting
Current Recall Procedure (No suggested changes at this time) • If (HDL-GEN) ≥ 500 MW, Avail_CAP_30Min ≥ 1000, AND PRC is ≥ 3000 MW; • Then recall half of Non-Spin. • If (HDL-GEN) ≥ 1000 MW, Avail_CAP_30Min ≥ 1000, AND PRC is ≥ 3000 MW • Then recall all Non-Spin. Reliability Deployments Task Force Meeting
Possible Revisions to Non-Spin Deployment and Recall Procedure Several possible revisions to the Non-Spin deployment and recall procedures have been discussed. For some revisions, in addition to procedure changes that need to be approved by TAC, there would need to be changes to the ERCOT systems in order to have deployments and recalls that discriminate between On-Line Non-Spin and Off-Line Non-Spin Resources. At least several months would be needed to implement the needed display changes and software changes. Reliability Deployments Task Force Meeting
Adjustments to the RUC Process RUC is used to ensure ERCOT System reliability and to ensure that enough Resources Capacity, in addition to Ancillary Service capacity, is committed in the right locations to reliably serve the forecasted Load on the ERCOT system. Bias already subtracted from the Load Forecast. (Average 1259 MW across peak hours in August) Any adjustment would need to be studied and take into consideration the way the Quick Starts are represented in COP. Protocol changes are likely required. Reliability Deployments Task Force Meeting
Last Slide QUESTIONS Reliability Deployments Task Force Meeting