Establish priority of Changes for version 1.2 of EDI SET ERCOT advises the following Change Control items are must haves in their opinion and that they can support doing these:
1, 4, 6, 7, 8, 9, 10, 11, 15, 16, 17, 18, 19, 26.
BJ Flowers advises that #22 should also be included in the priority list for version 1.2. This puts customer information on the 814s as specified in the Change Control document. Some push back from ERCOT in that they see this as a change to Protocol via RUG which has not taken place (even though this is in the latest edition of the Ts&Cs dated 16 Nov 2000). ERCOT does not see that this one should be in the priority list. Larry is to take action on this one to determine what needs to be done.
Jill Prince advises that also need #3 as this will make the Util Rate Class and Sub Class as optional or not required. The issue is that ERCOT does not use this information and based on the present EDI design this information will be required and ERCOT would need to receive this information and do something with it or else this EDI Transaction would always be rejected by ERCOT. ERCOT advises that they agree with this one being in the priority list for version 1.2. So, #3 will be included on the Priority list for version 1.2.
Larry Shields advises that 23, related to Permits, also needs to be part of the priority list for version 1.2. ERCOT advises that they do not agree and see this as a Protocol change issue that needs to go through RUG. Larry to take action on this one to determine what needs to be done.
Larry mentioned that #s 2, 3 and 5 are not listed but that some companies need these. Jill advises that these are not Must Haves but Nice to Have.
ERCOT advises that they have been building to the following:
· 810_01 version 1.0
· 810_02 version unknown but dated 25 May (question on whether this one is truly needed as is QSE and QSE not doing EDI, ERCOT advises that they have been told to have EDI plus WEB support for this, Texas SET advises this does not exist as far as we are concerned)
· Normal 997s
· 814s version 1.1
· 867s version 1.1
· 824_02 but going to change to the one 824 (there are no longer multiple 824s)
· 820_01 version 1.0
BJ Flowers to send out information related to the 814 P transactions. There is confusion on the need for and use of these.
867_05, James (Anderson Consulting) advises that this is a “MUST HAVE”. The market will not work without this. Texas SET advises that this needs a Change Control to be issued as was not part of the original Protocols Texas SET was working from. James and Mike McCarty will work on this and submit as required. RUG says need to do this. James advises that Anderson Consulting has something already built on their end and will furnish this as part of the Change Control request so Texas SET has something to start with.
Texas SET will not have a conference call on the 22nd of Nov. The next conference call will be Thursday 30 Nov. Mike will set this up.
The next face to face meeting will be 06-07 Dec in Austin. Will work on the Priority list changes to the EDI transaction SETs on 06. On 07 will work on the Service Orders as much as possible.
Texas SET scheduling a meeting on 11-12 Dec in Austin. Sponsor and exact location TBD. This will be used to finalize as much as possible the Service Orders. Texas SET requests that the next PUC Service Order WorkShop to be sponsored by Entergy be held on 13-14 Dec in Austin after the Texas SET meeting.
END.