1 / 9

RARF Feedback process to RE’s from ERCOT

RARF Feedback process to RE’s from ERCOT. Art Deller. RARF Processing. Responsibilities: Per Protocol 3.7, Resource Parameters and 3.10, Network Operations Modeling and Telemetry – the Resource Entity is responsible for registering Resource Parameters with ERCOT. RARF Processing.

julian-barlow
Download Presentation

RARF Feedback process to RE’s from ERCOT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RARF Feedback process to RE’s from ERCOT Art Deller Resource Integration, Registration and Modeling Workshop

  2. RARF Processing Responsibilities: Per Protocol 3.7, Resource Parameters and 3.10, Network Operations Modeling and Telemetry – • the Resource Entity is responsible for registering Resource Parameters with ERCOT. NATF

  3. RARF Processing • Two methods to submit • Through Internet MIS as Service Request (Preferred) • Through ERCOT Legal (mpappl@ercot.com, and cc: resourcereg@ercot.com) • Submitted by Authorized Representative (or backup Authorized Representative) of the Resource Entity • RARF forms and Guide located on ERCOT.com (http://www.ercot.com/services/rq/re/) • Must be on current version (currently 4.8) as .xls

  4. RARF Processing • ERCOT Processing • Registration receives RARF and performs initial screening • Registration runs programmed business rules, derived from downstream system owners, to ensure compliance with defined business rules and completeness of data • If passed, Registration communicates next Model Load Date to RE submitting request, based on Section 3.10.1, Timeline for Network Operations Model Changes

  5. RARF Processing • ERCOT Processing (cont) • Model load date available on website (http://www.ercot.com/gridinfo/transmission/opsys-change-schedule) • Registration uploads RARF to data base of record and notifies Network Modeling Group (NMG) • NMG reviews RARF for accuracy and ability to model • NMG may have additional questions

  6. RARF Processing

  7. RARF Processing • Exception Process exists • If the Resource entity needs the change implemented earlier than the next normal model load date, they must request an interim update • Must submit an additional details and justification for interim update (New Form: Request for Interim Network Model Update) • NMG, via Registration, will communicate the earliest available date • Can manage changes of certain parameters through Market Manager, and/or Outage Scheduler

  8. RARF Changes Changes to RARF • New look – Unit data runs horizontal • New data elements (Governor parameters, Performance Limits, Cooling source, Gas fuel interface, • Splitting the RARF into different forms by technology type • Process remains the same. NATF

  9. Questions QUESTIONS?

More Related