Rarf addendum information qna session
This presentation is the property of its rightful owner.
Sponsored Links
1 / 18

RARF Addendum Information / QnA Session PowerPoint PPT Presentation


  • 106 Views
  • Uploaded on
  • Presentation posted in: General

RARF Addendum Information / QnA Session. Dana Showalter January 10, 2008. Addendum Summary. Send dates: Addendum and Guide sent to Resource Entity Authorized Representatives between January 4 and January 10 If no addendum received, most likely a problem with the RARF submitted on Nov 9

Download Presentation

RARF Addendum Information / QnA Session

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Rarf addendum information qna session

RARF Addendum Information / QnA Session

Dana Showalter

January 10, 2008


Addendum summary

Addendum Summary

  • Send dates:

    • Addendum and Guide sent to Resource Entity Authorized Representatives between January 4 and January 10

    • If no addendum received, most likely a problem with the RARF submitted on Nov 9

    • Contact [email protected] with questions or to request the addendum

  • Due to ERCOT on January 31

    • Send to [email protected] or submit via TML

  • Column A

    • Only “new fields” will be read into the database

    • Any “existing” fields will continue to be read into the database off of the RARF


Important information from guide

Important Information (from Guide)

  • The purpose is to gather additional planning data for EDS 4 RARF

  • The Addendum has locked fields – these are typically information gathered from the RARF and used as reference. Corrections to these fields should be made on the RARF itself

  • All data in this addendum is unit or site specific. No CC train or CC configuration information is included nor requested

  • For both the RARF and the Addendum, the unit and site codes should not be changed, as these correlate to existing codes used in ERCOT systems

  • Pre-populated fields contain data from RARFs received prior to December 18, 2007


Important information continued

Important Information (continued)

  • Why do Resource Entities need to fill out this Addendum and correct the RARF?

    • In order to avoid manual data corrections in the database, each field (row) of the RARF and addendum are only read into the database from one form. If the field is on the RARF – it will continue to be read from the RARF. Only new fields identified on the Addendum will be read into the ERCOT database. This helps with quality control and limits manual loading of information.


Additional assets addendum why

Additional Assets Addendum – Why?


Additional assets addendum

Additional Assets Addendum

  • ERCOT Branch Data can assist with filling this out

    • Found in Operations Model Data folder on secure Operations and System Planning Website

    • http://oldercot.ercot.com/tmaps/login.cfm

  • TSP will be familiar with naming conventions and may be able to provide assistance

  • Additional questions should be directed to [email protected] who will redirect to ERCOT planning


Private use network addendum

Private Use Network Addendum

  • Should only be on Addendums for PUN Resources

  • Site and unit information requested

  • Site information includes:

    • Totals of MWs, MVARs

    • Totals of Gross Generation, Average Load, and Average Net to grid

      • Injection (positive) OR consumption (negative)

    • Load characteristics (in %, should add to 100% for MW and 100% for MVAR)

  • Unit information includes:

    • Allocating the MWs and MVARs across the units (should sum up to site totals)

    • Unit trip information


Private use network addendum site information

Private Use Network Addendum – Site Information

  • Enter totals for site (all units represented on RARF)

  • Please note that these values should be gross generation and load and only net values for specific rows.

  • A simple check would be: Net Interchange = Gross Capability – Self Serve Load


Private use network addendum site information1

Private Use Network Addendum – Site Information

  • Enter on RARF in Unit 1 column

  • If multiple tabs, enter same data on all tabs in Unit 1 column

  • Resistive MVAR load is not needed


Private use network addendum unit information

Private Use Network Addendum – Unit Information

  • Allocate site totals across units

  • Sum of allocation to equal site totals

  • Enter unit trip information as applicable


Gen and cc addendum error

Gen and CC Addendum Error

  • MW and MVAR values are swapped on Addendum only

    • Values in database correspond to values on RARF

    • No changes needed due to this mis-population as it was provided for reference only

  • To avoid in future

    • Test load with column name, which can be verified against RARF field


Gen and cc addendum

Gen and CC Addendum

  • Please ensure we get four ratings – the generator nameplate ratings in MVA, MW, and MVAR and the turbine rating in MW.

  • Please note the nameplate ratings should correspond to a nameplate power factor.

    • New: Turbine Rating (MW)

    • Renamed: Generator Name Plate Rating (MVA)

    • Corrected: label error noted in previous WebEx conversations where Rating (MVA) was used for reactive power. Please check this and correct on RARF if needed.


Gen and cc addendum1

Gen and CC Addendum

  • The two sections pictured below are omissions from the RARF.

  • The voltage connection is needed for the step up transformer and was originally requested on the Generation Data Forms.

  • As noted in previous WebEx sessions, details about the total unit auxiliary load were missing.

    • The auxiliary load characteristics should be completed on the RARF for each unit in percentage of total aux load.

    • The percentages should add up to 100%, as it is allocating the total aux load that will now associated with the generator with these new fields.


Gen and cc addendum2

Gen and CC Addendum

  • Please answer these questions and when ERCOT needs the additional forms, they will be distributed to those that are affected


Wind addendum

Wind Addendum

  • Add rating for each turbine model of a wind unit


Wind addendum1

Wind Addendum

  • The voltage connection is needed for the step up transformer and was originally requested on the Generation Data Forms

  • Please answer these questions and when ERCOT needs the additional forms, they will be distributed to those that are affected


Rarf update

RARF Update

  • To protect database integrity

    • RARFs must be submitted by Resource Entity

    • DUNs numbers of entities (submitting and owners) must align with proper entity

    • General Information tab must be complete

    • Resource Entities are being asked to clarify this information if conflicts exist

  • Additional RARF corrections may be requested as more data is applied to ERCOT Nodal Systems

    • Every attempt will be made to clearly state what needs corrected and why (i.e. if the field requires KV and 138000 is entered)

    • RARF will need to be corrected on the RE end and submitted to ERCOT to keep the database matching the currently submitted RARF (the process will be after the certified RARF)

    • Working together we can get the most complete, accurate RARF

      • Internal effort by Registration Team to encourage data is being validated by systems proactively.


Rarf update1

RARF Update

  • Scorecards will be updated with RARF data – Target Date January 18, 2008

  • TPTF Update during the January 21-23, 2008 meeting will identify upcoming dates and events

  • Combined Cycle units may have a forthcoming addendum

  • Resource Entities that have not submitted RARFs will be identified at the February, 2008 TAC meeting


  • Login