9
Commercial Operations Subcommittee Update to TAC November 5, 2009

Commercial Operations Subcommittee Update to TAC November 5, 2009

Embed Size (px)

Citation preview

Page 1: Commercial Operations Subcommittee Update to TAC November 5, 2009

Commercial Operations Subcommittee

Update to TAC

November 5, 2009

Page 2: Commercial Operations Subcommittee Update to TAC November 5, 2009

Voting Item from Oct 13Voting Item from Oct 13thth COPS Meeting COPS Meeting

LPGRR035, LPGRR035, URGENTURGENT, Addition of Time Of Use , Addition of Time Of Use Schedules (TOUS) to Profiles with Interval Data Schedules (TOUS) to Profiles with Interval Data Recorder (IDR) Meter Data Type Codes for Recorder (IDR) Meter Data Type Codes for Advanced MetersAdvanced Meters– REPs still need the TOU data on the 867_03s for their TOUS REPs still need the TOU data on the 867_03s for their TOUS

Customers, even after ERCOT begins settling on the 15-minute Customers, even after ERCOT begins settling on the 15-minute interval data for AMS meters. PUC Final Order requires REPS interval data for AMS meters. PUC Final Order requires REPS to continue to support their existing TOUS functionality.to continue to support their existing TOUS functionality.

– IAIAMinor cost impact to be managed under the operations and Minor cost impact to be managed under the operations and management (O&M) budgets of the affected departmentsmanagement (O&M) budgets of the affected departmentsSystem impact due to update to Lodestar table to include System impact due to update to Lodestar table to include Profile IDs that allow TOUS for AMS meters. No code Profile IDs that allow TOUS for AMS meters. No code changes are necessary. changes are necessary.

– Effective Date:Effective Date:BOD Approval 11/17/2009BOD Approval 11/17/2009Required 150 day notice will end around 4/17/2010Required 150 day notice will end around 4/17/2010

Page 3: Commercial Operations Subcommittee Update to TAC November 5, 2009

Highlights of Oct 13Highlights of Oct 13thth COPS Meeting COPS Meeting

CCWGCCWGCOPMGRR015, Section 8, ERCOT Settlement and COPMGRR015, Section 8, ERCOT Settlement and Invoice ProcessInvoice ProcessCOPMGRR016, Update to Section 12, Renewable COPMGRR016, Update to Section 12, Renewable Energy Credits, align with PRR808Energy Credits, align with PRR808– Both are currently in 20 day comment periodBoth are currently in 20 day comment period

ERCOT.com Satisfaction Survey ResultsERCOT.com Satisfaction Survey Results– 89 Users Participated in Survey, 57% Operations89 Users Participated in Survey, 57% Operations– Improvements that can be implemented nowImprovements that can be implemented now

Google search appliance Google search appliance Advanced search featureAdvanced search featureiCal feature added by end of yeariCal feature added by end of yearRSS feeds by end of yearRSS feeds by end of yearRedesign of meeting calendar layoutRedesign of meeting calendar layout

– Other improvements will be implemented by SCR755 which is Other improvements will be implemented by SCR755 which is tabled at COPStabled at COPS

Page 4: Commercial Operations Subcommittee Update to TAC November 5, 2009

Highlights of Oct 13Highlights of Oct 13thth COPS Meeting COPS Meeting

PWGPWGLPGRR035, Addition of Time Of Use Schedules LPGRR035, Addition of Time Of Use Schedules (TOUS) to Profiles with Interval Data Recorder (TOUS) to Profiles with Interval Data Recorder (IDR) Meter Data Type Codes for Advanced (IDR) Meter Data Type Codes for Advanced MetersMeters

150 day notice required after BOD approval150 day notice required after BOD approvalRecommended approval to TACRecommended approval to TAC

– COPS 10/13COPS 10/13– TAC 11/05TAC 11/05– BOD 11/17BOD 11/17– 150 notice ends around 4/17/2010150 notice ends around 4/17/2010

Discussing if Annual Validation 2010 is needed Discussing if Annual Validation 2010 is needed due to AMSdue to AMSEd Echols is new Vice ChairEd Echols is new Vice Chair

Page 5: Commercial Operations Subcommittee Update to TAC November 5, 2009

Highlights of Oct 13Highlights of Oct 13thth COPS Meeting COPS Meeting

PWGPWG

Page 6: Commercial Operations Subcommittee Update to TAC November 5, 2009

Highlights of Oct 13Highlights of Oct 13thth COPS Meeting COPS Meeting

SEWGSEWGReport and Extract issues continue to decline, Report and Extract issues continue to decline, issues with completeness or erroneous data in issues with completeness or erroneous data in extracts have not appeared in some timeextracts have not appeared in some time

Investigating combining the Investigating combining the Retail and Retail and Wholesale SLAs for reports/extractsWholesale SLAs for reports/extracts

Page 7: Commercial Operations Subcommittee Update to TAC November 5, 2009

Highlights of Oct 13Highlights of Oct 13thth COPS Meeting COPS Meeting

NOI DRG TFContinue work to move threshold for the DG data submission requirement to 1MW and apply this to all DG, not just DRG

Drafting various language changes– PRR, NPRR, RMG section 7.14

Defining reporting requirements

Next Meeting - October 14th after RMS

Page 8: Commercial Operations Subcommittee Update to TAC November 5, 2009

Highlights of Oct 13Highlights of Oct 13thth COPS Meeting COPS Meeting

Nodal RTM Settlement TimelineNodal settlement schedule will advance the capture of Nodal settlement schedule will advance the capture of generation and load data for use in settlements by 1 daygeneration and load data for use in settlements by 1 day– Generation: Operating Day + 7Generation: Operating Day + 7– Load: Operating Day + 7Load: Operating Day + 7

Why the change?Why the change?– Increased number of Operating Days to be processed in the Increased number of Operating Days to be processed in the

settlement system on a daily basis and to be verified by settlement system on a daily basis and to be verified by business on business daysbusiness on business days

– Need to minimize the risk of a back-out / rerun on all other Need to minimize the risk of a back-out / rerun on all other settlement jobssettlement jobs

– Need to reduce risk of posting statements and invoices late Need to reduce risk of posting statements and invoices late when verification identifies errors and a back-out/rerun is when verification identifies errors and a back-out/rerun is necessarynecessary

Page 9: Commercial Operations Subcommittee Update to TAC November 5, 2009

Questions ?Questions ?