TX SET Meeting
December 6-7, 2000
Strategy for review of
change control incorporation in the guidelines
Change Control Issues
Review of all questions
sent to Larry since the last meeting
Service order workshop
request and inclusion in the 650
Request to review data
flows for the pilot
ERCOT comment:
“MP companies have
informed ERCOT that the TX SET team is misaligned with market intent and must
be better managed”
·
ERCOT did not reveal
who the MPs that have expressed this concern
·
TX SET would like ERCOT
to provide examples and a - SET needs
some specific examples of how to remedy the “problem”
·
Larry will send a
written response to Mike and ERCOT.
If RUG, PIWG, TAC, and
PUC rules or the ERCOT Board has a change then SET will include it in the
transaction and ERCOT will include those changes.
Ex.
Customer contact info included in Ts&Cs but not included in
Protocols. It is difficult to “know’
what gets included, if it is in one rulemaking but not protocols, then it must
go through the ERCOT protocols review process to be included in protocols..
“Processes were developed
by MPs and must be followed, no exceptions”
We will make sure that
change controls apply to Protocols will be included in the
“Mike is the
communication agent for all MPs , there are MPs that do not participate in this
group (SET), however he has to answer to all, he must raise and communicate
issues that do not follow the process.
Take care of it in SET first and if no resolution is reached, Mike is
responsible for raising the issue to ERCOT”
Update on MRS
Presentation – Posting of Scenarios to website:
Bill will not post the
information to the website, but will be transmitted to the TPT and the
registered respondents, wants to post the location for the next meeting on the
webiste.
--------------<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>-------------
PIWG Update:
For concurrent
processing, the transactions will not be supported by ERCOT or needed to be
supported by the TDSPs until 1/1/02.
Per Protocols 15.1.3.3
ERCOT is supposed to compare dates of the Drop to POLR and the switch, the
switch will be cancelled if the switch date is after the Drop date. If the switch date is sooner, the POLR will
have to be held until we are sure that the switch will go through.
15.1.3.3 TDSPs will need
to support concurrent processing beginning 1/1/02.
Change controls that
affect concurrent processing can be delayed until
·
The problem is that
the TDSP will not know if it is a Drop to POLR. So if the TDSP gets two “switches” it will hold them, schedule
both and return the responses to ERCOT, then ERCOT will compare dates and send
an 814_08 with the original transaction reference number of the transaction
that will be cancelled.
Change Controls that
will be included:
Everything that is
included in the version 1.2 of the implementation guide release will be
included in ERCOT’s build for Pilot
PIWG Change Controls:
The following change
controls must be implemented by Pilot date:
SET Change Controls 2, 3, 4
(updated), 6, 34, 35 AND the PIWG Item number 185 and 196.
SET Change Controls #4 (has been updated):
Standard interconnection
point has been changed to “station ID”, on the 814_20 the field name will be
added. Approved by SET.
Change control #6:
Premise type indicator –
approved by SET.
Change control #34:
Add fields of Customer
Service Address in the 814_04 and 814_05 gray box “required for accept
response”.
Change control #35:
Add fields for
distribution loss factor codes (DLF code) in the 814_04 and 814_05 and 814_20
(add possible values for the 814_20).
Possible values for this REF~AQ are T, A, B, C, D, E.
PIWG #185 – ESI ID information included on SET
814_04;
15.1.1.7
·
ESI ID
·
Service Address
·
Rate Class and
Sub-class, if applicable
·
Life Support Status
·
Load Profile Type
·
Scheduled meter read
date
·
Meter Type,
identification number, number of dials and role for each meter at the ES ID, if
ESI ID is metered
·
For un-metered ESI
Ids, number and description of each un-metered device
·
Distribution Loss
Factor code
·
Station ID
15.1.2.5
“Upon receipt of a
registration notification request, the TDSP shall provide to ERCOT ESI ID
information including;
·
ESI ID
·
Service Address
·
Rate Class and
Sub-class, if applicable
·
Life Support Status
·
Load Profile Type
·
Scheduled meter read
date
·
Meter Type,
identification number, number of dials and role for each meter at the ES ID, if
ESI ID is metered
·
For un-metered ESI
Ids, number and description of each un-metered device
·
Distribution Loss
Factor code
·
Station ID
·
Premise Type
(residential, non-residential – is this really 2 or 3 categories??)
15.1.4.5
“Upon receipt of a
registration notification request, the TDSP shall provide to ERCOT ESI ID
information including;
·
ESI ID
·
Service Address
·
Rate Class and
Sub-class, if applicable
·
Life Support Status
·
Load Profile Type
·
Scheduled meter read
date
·
Meter Type,
identification number, number of dials and role for each meter at the ES ID, if
ESI ID is metered
·
For un-metered ESI
Ids, number and description of each un-metered device
·
Distribution Loss
Factor code
·
Station ID
·
Premise Type
(residential and non-residential – is this really 2 or 3 categories??)
--------------<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>-------------
Change Control Issues:
Change Control
#1 – agreed to on the
phone, required DTM.
The DTM is required on
the 814_03 - - description in the gray box to ‘first available switch date”
Change Control
#2 - Add un-metered
service type in the 814_04, 814_05,and 814_20.
PIWG has added this to the list for version 1.2
814_04, 814_05 – REF
segment can repeat as many times as necessary (COO4: REF~QQ number of devices
of this type)
814_20 – for maintenance
only, add code in the REF~TD, REFPRT for “number of un-metered devices has
changed”. Current inventory should be
sent when the number of un-metered devices changes.
Change Control #3 – 814_20 Utility rate class and sub-class. This
will be “not used when create ESI ID opt-in” until David gets back to us – will
it be shown in the Portal? This will
not be viewable on the Portal if you are not the Current REP for that ESI
ID.
Change Control #4 – According to PIWG, this has been changed. Change the description used in REF03 for
standard Interconnection Point (SPL), the REF03 should indicate the Station ID
(Sub-station ID) in the 814_04, 814_05
and 814_20.
Change Control #5 – Rejection reason codes to be made consistent with
Protocols
Change Control #6 – For Drop to POLR determining if the customer is
large commercial and small commercial /residential customers.
Premise Types: Residential, Small Non-residential, Large
Non-commercial
Change Control #7 – for drop to POLR and Move-out there needs to be
a validation that the submitting REP is the Current REP of record. – The codes can be added, but the codes
need to be made.
814_11 and 25: Add A84
invalid relationship– gray box “REP does not have a valid relationship with the
customer to perform this action” – ex.
Current REPs cannot request switches to themselves, cannot request a
drop if you are not the Current REP”
814_11: NFI has been added. Gray box “If drop date is after switch date
or equal to the switch date”
814_25: NFI has been
added. For blocked by pending request – Currently using “Not first In” – AC is
currently testing this, so we will leave it. Add Gray box to clarify “if the
current REP submits a second move-out request the second request will be
rejected as “not first in’”
814_ 17: Already has NFI
for a reject response.
824_02 - EPS issue.
Change Control #8 – Withdrawn
Change Control #9 – Modify the 814_20, in the NM1 loop, REF~TD –
remove the required REF04 in the compound for a REF~TD.
David is rewording the
change control to clarify the concurrent process. Bullet point 1 and 2 will be
removed.
814_05: Add a new rejection code in REF~7G for
NFI. Gray box “used when the drop date is sooner than the switch date”
814_10: Allows for a special read.
814_11: Add new rejection code in REF~7G for
NFI. Gray box “If drop date is after
switch date or equal to the switch date”
814_12: Currently AC can’t do a special read for
Drop to POLR. The rule says that a REP
can drop out of cycle. Changes that
need to be made in order for the current REP to be aware of the actual date
that the customer will be dropped.
814_12: ERCOT can be the submitter of the request
(RA to Current REP)
814_12: Add a new REF02 code (TD~DTM151) to the
existing REF~TD
814_12: Add a new DTM~151 (gray box “required if
changing the scheduled drop to POLR date…”) to support the drop to POLR
814_12: Title change to “Date Change Request”
814_13: Title change to “Date Change Response”
Add an un-metered code to
the 867_04 – previously approved.
PTD04 and PTD05 use will
be changed to “Dependent”
Add gray boxes to the MEA
and QTY to say “not used if ESI ID is un-metered services”
Change Control #12 - Withdrawn
Change control should be
modified to include 867_02 as well.
Change Control #14 – 810_02 late payment charge - on hold.
Modify change control to
change BGN07 to BGN08 for the implementation guide number in the header
(because there is no 12 code available in BGN07).
AC suggests that the
Sending CR not use the BGN08, then ERCOT will receive the transaction and
figure out which transaction this is and will assign the appropriate IG
number. ERCOT will not validate the
BGN07 field on incoming transactions, but they will assign it on transactions
that are being sent from ERCOT. This is
approved by SET for the 814s.
Add a gray box for the
BGN07 saying that it will be “used to readily identify the type of transaction
that is being processed”
For the 867s we will not
an additional data element to identify which transaction it is, this will be
determined by interrogating BPT. (no changes to the 867s for this purpose).
867_01 and 867_03 time of
use codes need to be added for the PTD~PP loop, the DTM for service period
start and end need to have hour and minute.
Add the PTD~SU for
non-interval summarized, for 867_03. Approved and included in version 1.2.
Change control needs to
be updated to include the 814_20, and to change the 814_15 to read 814_14.
Time of use, multiple
peaks for 867. Currently we have
on-peak, mid-peak, and off-peak. AC has
mocked a code for super-on-peak (super-peak does not exist in UIG codes) for
its internal systems.
Add Codes in the REF~IX
and 4P in the 814s. Add the codes in
the MEA07 for the 867s. Leave mid-peak intermediate
(43) (used for shoulder), on-peak (42), off-peak (41), and totalizer (51) codes
as are currently included in the IG.
Add “summer super
on-peak” code (71) and add a gray box to explain that it is used for super
peak.
867_01, 867_02, 867_03,
867_04, 814_04, 814_05, 814_14, 814_20 need to be updated to include the new
codes (above).
Change Control #19 - Withdrawn
Change Control #21 - SIC codes – sent to regulatory
Change Control #22 - Customer contact info on switches and move-ins –
implementation date TBD.
Change Control #23 - Permit flag – raised to TAC
Change Control #24 - Pending
Change Control #25 - Pending
Change Control #26 – Remove the SW, MVI and MVO secondary service
codes in the LIN09 Product Service ID.
814_01, 814_02, 814_03, 814_04, 814_05 need explanation in the gray
boxes in the LIN to indicate that these codes cannot be used together, they are
mutually exclusive.
Change Control #27 – Proposed 867_05 for TDSPs that submit loss
factors on a daily basis.
Change Control #28 – Withdrawn
Change Control #29 – Withdrawn
Change Control #30 – Withdrawn
Change Control #31 – Rejected
Change Control #32 – Rate Class full for the Pilot response. –
Pending PIC meeting.
Change control #33:
Add rejection reasons for
the TED02 for (TED~848) “Incorrect
meter role for ID type” and “Incorrect TOU Periods” fields in the 867s and the
824. – This is not a PIWG issue, companies need to send comments asap.
--------------<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>-------------
Other Issues:
814_24: Change title to
Move out request
814_25: Change title to
Move out response
814_06 (drop due to
switch request) – is TDSP included on this IG? – DAVID?
814_08 (cancel switch
request) – DTM~150 should be removed, gray box was struck, do we need the date
here or not? The gray box has been
added again, however DAVID will follow up on this.
814_10: (Current REP to
RA) DTM~150 should be removed. There is no pending change control on this, but
the idea is approved by SET and an official change control will be submitted
for the 814_08, 814_10.
Meter set that cannot
be performed on a Move-in Request:
If an ESI ID has been
established and a TDSP receives a move-in on that premise (it knows that a
meter needs to be set), the appropriate responses are sent, the field person
goes out to the premise and finds incorrect wiring (or some unsafe condition)
and the service person will leave a note on the door asking the Customer to
call their REP. The TDSP needs a way to
“close” this when the meter info cannot be sent back on the 814_04 in the
prescribed 2 day turn-around.
Suggested solution:
The codes should be added
to include a code on the 814_04 to indicate that the requests cannot be
completed yet.
For this situation this
would cause the metering info to be “Dependent” on the 814_04.
The 867_04 would provide
completion of the move-in.
AC Change Request –
life cycle tracking number:
On a number of 814s we
have left out the BGN06 (refers to the BGN02 or the initiating transaction
identifier), it needs to be added as “Dependent” use. Add to 814_18, 814_20,
814_24, 814_26 – AC has already implemented this in its build for ERCOTs
system. David will write up the change
control, but it will be added to the 1.2 version.
--------------<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>-------------
Transactions Review:
814_01 – Switch Request
changes that have been
made that should not be included in version 1.2:
DAVID will report
these. Inclusion on the Customer name
on this IG?
810_02 – TDSP Invoice
Addition of the B2B loop.
Add a code in SAC04
(BAS03) for “Point of Delivery”.
We need to have a change
control written up to reflect that once the TDSPs have one consolidated list
then the codes will be added to the 810_02 later (after Pilot).
Each IT1 needs to have
the DTM segments (150 and 151).
In the SAC04 add gray
boxes for the late fees (DSC001 and LPC001) will be gray boxed to indicate that
they will only be used in the B2B loop.
Change gray box to
indicate that the Account loop is “required.”
867_05 Distribution Loss Factor Report – Strawman
developed by ERCOT
TDSP to ERCOT which will
deliver the96 intervals for the 5 loss factor types.
QTY~DD - Loss factor must
be greater than zero and less than one.
How to handle daylight
savings time – should be in the metering section of Protocols??
Approved.
Pilot transactions:
SET has agreed to merge
“P1 with P3” and merge “P2 and P4,” one request and one response.
Service
Order Discussion:
Service Order approach and the agenda for
next Monday and Tuesday.
Types
of Service Order Requests:
650_01 – Requests and Updates to Original
Request |
650_02 – Reject or Completion Response |
1.
Disconnect for
Non-pay *the POLR is
the only party that can request this · Original
Request · Update or
Change Original · Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
2.
Disconnect for
customer Requested Clearance · Original
Request · Update or
Change Original · Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
3.
Reconnect for
Non-Pay · Original
Request · Update or
Change Original ·
Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
4.
Reconnect for
Customer Requested clearance · Original
Request · Update or
Change Original ·
Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
5.
Technical/Environmental · Original
Request · Update or
Change Original ·
Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
6.
Re-read
Request · Original
Request · Update or
Change Original · Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
7.
Meter Exchange
Request · Original
Request · Update or
Change Original · Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
8.
Lighting
Request (streetlights) · Original
Request · Update or
Change Original · Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
9.
Facilities
Investigation Request · Original
Request · Update or
Change Original · Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
10.
Meter
Maintenance Request · Original
Request · Update or
Change Original · Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
11.
Special
out-of-cycle Read Request · Original
Request · Update or
Change Original · Cancel |
· Reject · Completed
unexecuteable · Completed as
requested |
650_01 Service Order Request (original,
change or cancel)
650_02 Response (Reject, Complete as
requested, Complete unexecuteable)
·
Is there a transaction needed to change an existing
service order request? No, make this
part of the 650_01.
·
Diana will compile all of the TDSP codes.
·
A “reconnect request” would cancel a pending “disconnect
for non-pay.”
·
Unresolved Issue: How will the TDSP cancel a
Service Order? Can the TDSP
update/change the status of and existing service order request?
Action items:
·
Put together the Service Order matrices
·
Complete the code list
·
Do a compare to see similarities and then standardize
(reason codes,
·
Look at Priority codes, Action codes, Reason codes for
street lighting and guard lighting, Reason codes for disconnect.
·
Develop a recommendation on any unresolved issues.
·
Created the matrix of codes for the standardized list of
TDSP action and reason codes.
Other
·
On a move-in when the premise is de-energized, the TDSP
will send the 867_04 because there is not enough info to send an 867_03. This is an exception.
·
Protocols update:
Remove
the second 824 and should be titled “Application Advice” referenced in the
Protocols Ch. 19.
IG
cover pages have been updated and need to be reflected in the Protocols Ch. 19.
814_18
description needs to be changed – “from ERCOT to the Current CSA CR to ERCOT” –
should be “Current CSA CR to ERCOT”
·
For kVA and kVAR
being dependent on each other, SET cannot make this determination, this issue
should be referred to James Cohea to find out if ERCOT will send both to the
TDSP on EPS.
·
867_03 in the QTY
loop add a PID segment to indicate the “reason that the reading was estimated”
– this is in Ts&Cs currently, not updated in Protocols yet. AEP will submit the change control.
·
The 867_03 will
allow for noting estimated read/consumption at the interval level.
·
Removal of the DTM 150 for service period start in
the 814-10 - done
·
Status on the
actual/estimated in the QTY02 – done
Pilot reference in
Protocols:
·
Clarification of
section 19 of the protocols for the P1 transaction Currently the protocols are
defined as originating from the REP and ERCOT as the destination (BGN08 will
have PA for the Pilot Request, PB for the Pilot Response).
·
CRs can begin
sending the Pilot transactions as early as Feb 15th – not April 16th.
Reference number in
the 820:
·
Is the unique
cross-reference number to link the 867 – BPT02, 810 – BIG05 and 820 really
needed? – No, a change control will be submitted (to change the REF in the RMR
loop – if the REF is marked “Must Use” a change control will need to be
submitted) by Johnny to remove the reference number in the 820.
Recommendations
Document:
·
Clean up
recommendations in the assumption #2 – “all transactions will be done at the
ESI ID level”. This should have a
disclaimer or clarification with the exception of the 820, which is not on the
ESI ID level.
Customer Protection
Rule has been Adopted with significant changes:
·
Postcards will go
out but ERCOT will not automatically stop a slam.
·
Recission period (3
days) is overlapping the postcard review period.
·
Customer can switch
on an estimated read – wouldn’t have to be on a meter read, special reads can
be estimated.
·
SET Meeting for
Service Orders – Dec 11-12 in Houston. Monday, Tuesday 8:30-5:00
·
Service Order
Meeting (Technical Workshop) – Dec 13-14 in Houston. Wednesday 10:00-7:00, Thursday ????
·
January 10-12,
Wednesday @1:00, Thurs 8:30-5:00, Friday 8:30-12:30 hosted by Entergy in
Austin. Location to be determined.
Attachments:
Meeting Minutes 12/6-7/00
Attendees:
Diana
Rehfeldt TNMP Anette Morton AEP
Debbie
McKeever TXU Rohni Patel Reliant
Jill
Prince TXU Heidi
Schrab Reliant
BJ
Flowers TXU Jeanette
Harris Reliant
Mike
McCarty ERCOT Cary Reed AEP
Dave
Robeson Entergy Johnny Robertson TXU
Susan
Neel Reliant Sharon
Polliard AEP
Shirley
White US Power
Solutions Fred Plett Logica
Terry
Roberts Entergy Richard Powajbo Entergy
Kim
Wall Green
Mountain Nancy Hetrick Enron
Bryn
Owen Energy
Services Group Rob Boye AEP
Malcolm,
Wrench Logica David
Lotspeich AC