8000 Metropolis (Building E), Suite 100
Austin, TX 78744
168
Agenda
1
Texas SET Meeting
Antitrust Admonition
Reviewed -- no questions
Introductions
See Official Roster
Approval of the Draft January 26, 2006 Meeting Notes:
Approved with no updates
RMS Update -- includes comments from RMS Leadership
A meeting was held with RMS leadership and Working Group/Task Force leaderships.
RMS leadership has asked that the Working Groups and Task Forces begin to use the Event Summary Document for meeting notes.
Meeting notes from RMS Working Groups and Task Forces will be included as supporting material for RMS going forward.
Kathy Scott
9:00 AM
2
Mass Transition
TX SET Mass Transition Meeting Update (02/27/06 and 02/27/06 Meetings)
The Mass Transition Team revised the long term PRR language and short term RMGRR language.
ERCOT will take information back from the meeting and work to gather information for Cost Benefit Analysis(CBA) for both Customer Information Repository(CIR) updates directly to ERCOT and CIR updates directly to Designated 3rd Party Vendor, also CBA will include usage of CSV.file and 814_PC TX SET transaction .
TX SET Mass Transition Sub-Team Discussion (02/08/06 and 02/21/06 Meetings)
Proposed Mass Transition Concept
Checklist Changes Required
Business Requirements Document
Implementation Guide Revision
Reviewed checklist and assigned for review -- see checklist for assignments
Timeframe: Will review any available guide revisions at the March TX SET meeting.
Johnny Robertson provided the following codes for standardization:
‘TS’(Transfer Status) code has been identified as the code for Mass Transition Indicator.
Reject Code of 017 can be used for Mass Transition. States: (Service terminated because of CR Default
This item will be discussed by TX SET following the final approval of Mass Transition Retail Market Guide Revisions (RMGRR for Section 7.11)
Visio Flow Processes
Reviewed Updated Visio Flows
Protocol Revisions: Protocol Revisions Deferred
Chapter 15 -- Customer Registration
Chapter 19 -- Texas Standard Electronic Transaction
Chapter 24 -- Retail Point to Point Communications
Others? Example: Chapter 2 -- Definitions and Acronyms?
Plan of Attack to Accomplish All Mass Transition Deliverables?
TX SET leadership assigned TX SET members in attendance the SET Implementation Guides that required review and propose changes based upon the high level design discussed by TX SET over the past 2 weeks for the Mass Transition Project.
Open Discussion, Action Items or Issues
Kathy Scott
9:30 AM
Lunch
12:00 PM
3
Discuss ONLY if time permits following Mass Transition Discussion
TX SET Procedures Document
Reviewed Procedures and made changes where necessary. This document will be submitted to RMS for approval at the April meeting. See meeting ‘Key Documents’ Approved TX SET Procedures Document
Reviewed Timeline for Establishing TX SET Release.
Market Coordination Team Roles and Responsibilities Document
Reviewed and made changes where necessary.
RMGRR necessary so that the Roles and Responsibilities will be added to the Retail Market Guide. Kathy Scott will submit to the RMGChangeControl@ercot.com listserv.
2:00 PM
4
4. Additional Agenda Items -- Katherine Meiners
Clarification of dates in 867_04s. The guide shows it possible to have multiple DTM~140s in an 867_04 for an ESI ID with multiple meters. In addition, those dates can be different from each other. Is there any reason why these dates should be allowed to be different? If the dates are different, which date should ERCOT use as the Start Date for the order that this transaction is completing?
Bill Reily will look into the specific example and bring back to TX SET with more details.
o TX SET will need to correct the example in the guide 2 of 5 found on page 19 of the 867_04 Implementation Guide.
SIR 10559 -- Currently ERCOT is inconsistently validating on the number of digits in a zip code. Should ERCOT be failing zip codes that are between 5 and 9 digits? Or allowing them to pass TX SET Validations?
o Service address zip codes should only be 5 or 9. Anything else will be rejected by ERCOT
o ERCOT will implement this validation.
SIR 10528 - Backdating Transactions -- ERCOT Systems don’t recognize some very old dates as dates and will not reject for backdated. ERCOT would like to know what date should be used to put in validation such as not allowing anything prior to 01/01/1999. Specifically 814_04s and 814_20s.
o There is no reason either of these transactions should come in with a date prior to 01/01/1999 so using this date is fine.
