Rtm/Dam Code/Mode/Base

RTM Commercial Operating Day Extract (CODE)/Market Operating Day Extract (MODE)/BASE

•For each approved RTM operating day settlement:

–Post a single file for each operating day (therefore, multiple file postings a day) for:

•Consolidated CERTIFIED interval data for Load, Generation and Settlements & Billing data called ‘RTM Consolidated Operating Day Extract’ (CODE)

•Consolidated SECURE market interval data for Load, Generation and Settlements & Billing data called ‘RTM Market Operating Day Extract’ (MODE)

–CODE/MODE - Order of file postings of operating days is irrelevant

•For CODE/MODE, create a separate extract for base tables that will include an ‘Initial’ to provide the full record set and a ‘Daily’ for the incremental changes called ‘BASE’.

•Produce ‘Initial BASE’ one time per month and an incremental as changes are made. If changes are made impacting the day the ‘Initial BASE’ file would be posted, also post the incremental file for those that are not re-loading the tables each month.

•File naming convention for CODE/MODE to include ‘RTM’, the operating day, settlement run type (Initial, Final, True-Up, Resettlement) and channel <like statements>, which should also map back to the naming convention in the settlements calendar.

•Data content in MODE, CODE, and BASE should include all data necessary to perform a shadow settlement to the settlement statement.

•Recorder field will be broken up into meaningful fields

•OPEN QUESTION (to be answered at COPS on 10/9): Should the tables be lumped together, as they are today, or broken apart, the way ERCOT will for Nodal (such as RUC, DAM, RTM, etc.)

•Interval data Header/Data/Status tables will remain separate

SETTLEMENT CALENDAR Extract

•Use naming convention for settlement type as used in the Settlement Statement, Consolidated Operating Day Extract and Market Operating Day Extract

•One available posting of the calendar with the most current data should be posted; when data is updated, previous calendar should be overwritten.

•DDL to include: Operating Day, Run Date, Run Type, Channel, Settlement Statement posting date, Invoice posting Date, Payment due date (pay in), Payment Process Date (pay out), Dispute Date Deadline, Last Updated Date

•One record per operating day, run type, channel – unique key

•Invoice date will be populated on each record

•CRR monthly and CRR annually – no invoice date will be initially populated in the calendar

•For NP 9.1.2(2), need to have a notice sent, as well as the calendar update

Certified Dispute Extract

•Intent of extract: CERTIFIED extract to provide QSEs and CRRs current status of all disputes that are not closed or withdrawn, and all disputes closed or withdrawn within the last 120 days

•No triggering event

Secure Dispute Extract

•DAM and RTM statements report on same report

•DAILY SECURE Summary by charge type with cumulative total by operating day and status and resolution and count of disputes and market type (DAM, RTM)

–Filter by:

•Resolution - granted, granted with exception, null

•Status – not started, open, adr

•Resolution - Denied, granted, granted with exception, null

•Status - not started, open, closed, withdrawn, ADR

–If submitted in 10 days of statement, then must be resolved in 10 days

–If submitted outside of 10 days, then have until True-Up to resolve

•For granted & granted with exception, these will ‘roll off’ once the status changes to ‘CLOSED’ or ‘Withdrawn’

•ERCOT will determine in the design process the best way to report on multiple operating days

•Most current report will always be available

Other Requirements

•For CODE, MODE, BASE, Dispute Extracts, Settlement Calendar, Settlement Input Data Extract, DAM Settlements & Billing Extract provide output option for csv or xml output

•File naming convention for DAM Settlements & Billing Extract to include ‘DAM’, the operating day, settlement run type (Initial, Final, True-Up, Resettlement) and channel <like statements>, which should also map back to the naming convention in the settlements calendar.

•Continue providing Default Profile ESIID, Load Counts and Load Volumes reports with Nodal implementation; to be included in COPS Market Guide in data aggregation section

•Provide an option for csv or xml for all new COMS scheduled extracts.

•Extracts include:

•Dispute Extract

•RTM Consolidated Operating Day Extract

•DAM Settlements & Billing Extract

•Settlements Calendar Extract

•Settlement Input Data Extracts