MIS LOG IN

RRGRR006

Summary

Title Clarification of Descriptions and Alignment with Resource Asset Registration Forms
Next Group
Next Step
Status Approved on 10/13/2015
Effective Dates
05/08/2017

Action

Date Gov Body Action Taken Next Steps
10/13/2015 BOARD Approved
08/27/2015 TAC Recommended for Approval Revision Request Consideration
08/05/2015 ROS Recommended for Approval Revision Request Consideration
07/14/2015 RDWG Recommended for Approval Revision Request Consideration
06/16/2015 RDWG Deferred/Tabled Impact Analysis Consideration
05/12/2015 RDWG Deferred/Tabled Impact Analysis Consideration
04/21/2015 RDWG Recommended for Approval Impact Analysis Consideration

Voting Record

Date Gov Body Motion Result
10/13/2015 BOARD To approve RRGRR006 as recommended by TAC in the 8/27/15 TAC Report. Passed
08/27/2015 TAC To recommend approval of RRGRR006 as recommended by ROS in the 8/27/15 ROS Report. Passed
08/05/2015 ROS To recommend approval of RRGRR006 as recommended by RDWG in the 7/14/15 RDWG Report with a recommended priority of 2015 and rank of 1230. Passed
07/14/2015 RDWG To endorse and forward to ROS the 6/16/15 RDWG Report as revised by RDWG and the revised Impact Analysis for RRGRR006. Passed
06/16/2015 RDWG To table RRGRR006 for one month. Passed
05/12/2015 RDWG To table RRGRR006 for one month. Passed
04/21/2015 RDWG To recommend approval of RRGRR006 as revised by RDWG. Passed

Background

Status: Approved
Date Posted: Mar 20, 2015
Sponsor: Resource Data Working Group (RDWG)
Urgent: No
Sections: 2
Description: Resource Asset Registration Forms (RARFs) are submitted by every Resource Entity in the ERCOT market. The Resource Registration Glossary describes the data requested on the RARF. Market Participants have expressed concern that the description of the data requested is unclear and leads to rejection of the RARF by ERCOT. The Resource Data Working Group (RDWG) worked to clarify the description for various data needed in the RARF. This Resource Registration Glossary Revision Request (RRGRR) was developed to capture those clarifications and should not require new RARF submissions if it is approved.
Reason: Market efficiencies or enhancements

Key Documents