Set
Meeting
Minutes
March
21-22, 2001
ERCOT Review of
Version 1.3 transactions:
867_03
·
Add BPT01 field; use
for ERCOT Polled Meter. Johnny
Robertson suggested, use “EX”, final loading configuration. The suggestion was for ERCOT to add a BPT04,
but ERCOT doesn’t think it can support that, so it is now suggesting
BPT01. Change Control 66 will be
rejected to be resubmitted as a new change control 74. Change control 74 was
approved.
·
Add REF position 60
“EO” Submitter's ID, containing BGN06 of 814_03, Change control 55. This was rejected to be resubmitted as
Change Control 76.
867_04
·
Add REF position 60
“EO” Submitter's ID, containing BGN06 of 814_03, Change control 55. This was rejected to be resubmitted as
Change Control 76.
814_03
·
ERCOT states required
move-in request in 814_03 that they will work to support it.
814_07,
814_08 and 814_11
·
Remove from Guide
rejection reason codes B04 and CCA for 814_07 and 814_08 and 814_11. ERCOT may not be able to remove these
rejection reason codes from the portal or transaction-clearing house in time
for pilot. ERCOT will add to their
tickle list.
814_12
·
ERCOT requesting
remove from gray box in BGN06 the original transaction ID from Drop to POLR
request. There was discussion about
ERCOT creating a Version 1.3a. ERCOT
will instead have an exceptions list because Version 1.3 was sent out as final
814_13
·
Clarified REF 1P MDI
so that ERCOT only can send it; ERCOT can’t validate that it can’t get from
somebody else.
814_16
·
ERCOT requesting
Change move-in request in N1 loop to required from required if. Don’t have exception logic to kick this out.
814_20
·
Bill Bojorquez says
ERCOT will not use 814_20 for move-in, move-out. Move-in’s and move-out’s are still not handled well. For 5% participating in pilot, we may very
well use the portal to do it since the volume is so small. For the 95%, we will probably send a flat
file in December.
·
On create, or
switch, multiple NM1 loops are O. K.
For remove, ERCOT is concerned that multiple NM1 loops will lead to confusion
and won’t be mapped if there are NM1 loops of differing types such as meter
voltage. There should be verbiage added
to gray box for one NM1 loop – for instance, 1 meter add and 3 removes in one
814_20 would be a problem. Four
814_20’s is not a problem. This may be
easiest to explain in a best practices section up front in the 814_20. There was discussion about David Lotspiech
to write that up in a Version 1.3a.
ERCOT will instead have an exceptions list because Version 1.3 was sent
out as final and that which everybody is supposed to comply with.
·
We added a reason
for change code to maintain premise type.
ERCOT can’t support it.
·
ERCOT needs a REF
PHC energize – de-energize flag for next version.
814_24
·
DTM 376 move out
date – moving to required.
Other Version 1.3
Review
867_03
·
QTY 02 for consumption, are all utilities reporting the same way, need to
find out. Heidi talked with all but
AEP, didn’t get consistency. Beginning,
Ending, times multiple, equals quantity, but ERCOT wants transformer losses to
be included in that number. It should
be the billable number. We provide
transformer loss factor, TXU says, so that you can calculate quantity because
it won’t match beginning, end, multiplier, without application of transformer
loss factor. Transformer loss factors
should be applied to the QTY so it is a billable amount. We should clarify in loop gray box that all
factors should be applied so that it is a billable amount.
·
TXU would like to not adjust for fast, slow or tampered meters, but to
add an additional loop to show adjustments for added flat, subtracted fast,
added slow, added tampering.
Subtractive Metering
·
This discussion is
restricted to where separate ESI IDs are assigned to subtractive and master
meters.
·
TXU, Reliant and AEP
are going to assign different ESI IDs to master and subtract meter. When there is a REP of record for both
master and subtract, no problem, but if the REP of record is different for
Masters and Subtracts, there is a problem.
Say there is a university campus and then a Jack-in-the-Box on the
campus added later, so a subtractive meter is added to the Jack-in-the-Box
load. How do we report subtractive
consumption to a REP.
·
Jill Prince is
suggesting a totalized subtractive loop, for the REP of record for the master
meter, but since there is no meter number for the subtractive loop, the word
“subtractive” would be applied in lieu of a meter number. After discussion, it was agreed that there
would always be one subtractive loop that totalized all subtractive meters to
subtract from the master meter.
·
Another wrinkle is
when the master meter is an interval meter.
The master meter would have a BO, metered gross, and PP, ERCOT net
usage, in each interval. The difference
would the subtractive value. This would
have to be calculated amount based on load profiles when the subtractive meters
are cumulative, not interval meters.
The PM loops would have to include interval subtractive data based on
load profiles or actual readings.
·
There would be a BO
master, BO subtractive, then PM master, PM subtract totaled.
·
Conference call
issues:
Ø
We need to cover
additive metering also. It will be
discussed. The 867 already supports
totalizers for additive situations.
Ø
Kim Wall discussed
having a separate code in PTD04, rather than rely on text, because a CR may
bring the text into their systems as meter number without the flag of having
this separate code in the PTD04
820
·
There is no way to reject an 820. If there is a problem, they are worked out
internally or through phone calls. This
may be addressed eventually, but not for pilot.
·
If utility sends and
867, it passes X12, ERCOT, passes on to CR, ERCOT loads into LODESTAR, and CR
rejects it (wrong ESIID, say), CR sends back an 824 through ERCOT (includes
TDSP ID so ERCOT sends it back to the right TDSP). It’s possible that ERCOT may also generate an 824 after
attempting to load to LODESTAR. Utility
will then send a cancel 867.
·
If we get an 824 rejection of an 810 or 867 - then our
next step is to send a cancel - so that we can send a corrected. Then lets say we get a 824 rejection of the
cancel 810 or cancel 867. Would the lifecycle
reference # on the second 824 be the BIG02 of the original 810 or 867 or the
BIG02 of the cancel 810 or 867.
·
Upon receiving the
824 (or two), TDSP will send an 867 cancel, 810 cancels if they had been
generated, and then new 867’s.
Municipals and Cooperatives
·
Need to put on
agenda 810_03 for Municipals and Cooperatives for 4/10 meeting. We need to review and make final a Version
1.3.
·
Change control 63 is
being re-submitted as Change Control 71.
·
Change control 62 is
being re-submitted as Change Control 72.
·
Change control 50 is
being re-submitted as Change Control 73.
·
Change control 60 is
now being re-submitted as Change Control 70.
Change
Control 55
·
Rejected and resubmitted as Change Control 76.
Change
Control 76 (was 55)
·
REF01 Position 60 of
header 867_03 and 867_04 was approved.
“EO” Submitter's ID, containing BGN06 of 814_03. Change control 55 is rejected and
resubmitted as Change Control 76. Change Control 76 has been approved for
Version 1.3.
Change Control 58 – Power Region Code – Approved for Version 1.3, and it will be implemented by ERCOT |
Add power region to the 867_01
and 867_03
ERCOT is not going to load non-ERCOT ESI ID usage into its data
aggregation system. We may receive usage data for non-ERCOT ESI Ids for switch
reads. Adding REF~SR to 867_01 and 867_03 will allow ERCOT to do validation on
the power region so that such usage is not loaded into the system.
Change Control 070 (Dave Robeson Entergy) –
Disconnect/Reconnect. – Change Control 70 Approved for Version
1.3. |
On the 650 _02 Service
Order Response (Reject or Complete Unexecutable) add the code “V005 – No Field
Action Taken-Reconnect Received” to Segment REF (Complete Unexecutable Reason).
The
TDSP receives a Disconnect for Non-Pay 650_01 Service Order Request from the
CR. Before the TDSP can dispatch
and/or work this Disconnect for Non-Pay
650_01 Service order Request, the TDSP receives a Reconnect for Non-Pay 650_01
Service Order Request from the CR. The
TDSP has not done any field work. The
TDSP would use this code to close out both 650_01 Service Order Requests
received from the CR (Disconnect for Non-Pay and Reconnect for Non-Pay). There would not be any charges associated
with this if a person was not dispatched.
If a person was dispatched, there could be potential wasted trip fee
charged.
Change
Control 74, ERCOT polled meter - Change Control 74 was approved for
Version 1.3
|
·
Add BPT01 field, use
for ERCOT Polled Meter. Johnny
Robertson suggested, use “EX”, final loading configuration. The suggestion was for ERCOT to add a BPT04,
but ERCOT doesn’t think it can support that, so it is now suggesting
BPT01. Change Control 66 will be
rejected to be resubmitted as a new change control 74.
Miscellaneous Discretionary Charges
·
These will be
invoiced at the same time as billing for consumption, so that there is one 810
per ESI ID per month, with the exception of late payment charges
· Per Customer Protection, section titled “Privacy of Customer Information” for all customers eligible for price to beat shall be included on the mass customer list – Name, billing address, rate classification, monthly usage for the most recent 12-month period, meter type, and account number or ESI ID. Maybe a csv format. Heidi to take a starter document started by Bruce White, and modify it and bring it to TX SET.
Need an N1~N1 for the 814_10 Drop to
POLR
·
Where should ERCOT receive the customer notification address in the
814_10 Drop to POLR? There is not a N1 customer notification address loop in
the transaction. ERCOT needs to enter a
change control for this. Mike McCarty agrees and shall do so.
·
If a premise is de-energized, and the TDSP sends an 867_03 to ERCOT…will
ERCOT reject the transaction? Answer – ERCOT will not reject but it could
contribute to UFE if there is usage not associated with a CR.
·
“Tax” statement from the PUC – waiting for answer from State Controller’s
Office. Cary Reed to check.
·
814_PC and PD,
pending RMS approval. Nancy Hetrick is
not questioning the need for an 814_PC and 814_PD, but she does have a question
why CRs need to do this en masse right away at beginning of pilot where the
TDSP should have all of the data. CRs
should send it for all move-ins. CRs
should do this upon move-in or vital information change for the customer. Nancy
Hetrick will bring to RMS with this understanding.
·
Overpayments – not
resolved. If, for example, Green
Mountain Power overpays TXU for an ESI ID, Green Mountain Power would never be
notified. The discussion is that the
TDSPs would notify by phone. Either the
CR can ask for a check to be cut or the CR can underpay a future charge to use
up the credit balance. TDSPs will monitor for CRs and notify after
a few months.
·
Charges not
associated with consumption after the customer has switched away – The TDSP 810
should not reference the 867. We can
change the 867 to optional, change the gray box, so that it is not required for
when the cost is not associated with an 867.
Johnny Robertson will write
change control. Add a gray box for
late payment charges or invoices not used.
·
TDSP creates 814_20
for new customer to set a new ESI ID, while construction is taking place. TDSP allows wire installs, builds customer
directly. When the customer wants a meter,
TDSP needs a CR. This is where the
814_20 comes in. But then CR will send
request to set meter in 650. CR also
sends an 814_01 to ERCOT Enrollment request, and ERCOT will reject because they
don’t have the meter information. The
best solution could probably be send an 814_04 without meter information, and
then an 814_20 ESI ID. This would
require a modification to the 814_04.
How will the TDSPs notify the CRs that a customer has
called them directly for a service order and it has been performed?
·
The issue is that the CR wants to be notified if the Customer has
requested something that involves a charge (the CR will be responsible for
paying the TDSP for that service 35 days after the TDSP invoice).
This is something TX SET
cannot do. It must go to the TX Outage
Group. We will ask the RMS group to
push this onto the Outage Group or otherwise handle as they see fit.
650_01
·
Need to replace the
“how to” page.
·
N401 and N402, add
“Must Use” for city and state.
·
Copy punctuation
note to PER – no punctuation for phone numbers.
650_02
·
Add in summary of
changes a bullet for change control –
Added two codes for REF~1P Status Reason Codes to identify no charge or charge
for no field action taken.
810_01
·
Change
“Clearinghouse” to “ERCOT”.
810_02
·
Change gray box
description, for service order billing, in BIG05, to “outstanding discretionary
charge after final bill”.
·
In IT1 B2B gray box,
change “may” to “will”.
·
In the gray box,
need to research what is the discount for TC withholding.
·
In DTM 150 and DTM
151, add in the gray box the “outstanding discretionary charges after final
bill” for service order. Not used. Clean up spacing.
·
In the gray box,
swap sentences such that the Late Payment charge invoice sentence is moved to
the beginning. Change the language
later where it says “All other charges not associated …” to state that late payment charges will be in a separate
invoice.
·
Change gray box in
REF02 of REF IK to remove “late” such that it then says “Invoice number”.
·
In the SAC04, INT
001 should be INT 003 in Notes.
·
In INT001, remove in
gray box terms and conditions statement..
Use first statement of gray box as the official title rather than use
UIG language.
·
INT003, replace UIG
with the first sentence of the gray box, remove the terms and conditions
language.
·
Change in LPC001,
gray box, remove second sentence and simply refer to “late payment charge”.
·
Reword TRN002 gray
box.
·
Change the SAC05
gray box to remove the first two sentences.
·
In Example 4 of 6,
remove ST – DTM and explain that this is only the SLN loop example.
820
·
No changes. The
820 is made final for Version 1.3.
824
·
No changes. The
824 is made final for Version 1.3.
867_03
·
REF SR needs to have
the description changed – to refer to the “Southwest Power Pool”, not
“Southwestern”.
·
Gray box, REF02,
remove after the word “transactions”.
REF02 needs to be a “must use”.
In the notes, add “required on final usage, otherwise not used”.
·
On REF 02 gray box,
change to “Original Transaction Reference Number” (not Transaction ID).
·
At ZY, Referenced
Pattern Identification, change gray box to “Adjusted Consumption Code. This consumption code is used when a meter
number is not provided to support subtractive, additive, or adjusted
consumption.” Add to the codes
“subtractive”, and “additive”. Add to
“AddedFlat” the word /Bypass” so it appears as “AddedFlat/Bypass”. Add codes 01-06 so that the codes are
numerical.
·
In the PTD BO, PL
and PM Loops, use the same verbiage as at the ZY loop.
·
Move MEA 07 note to
top of the notes gray box. It should
refer to “MEA”, not “MEA 07”.
·
Need to make a
correction in the examples – change the word “trailer” to “number of segments,
control number”.
·
Example 2, the first
MEA should be changed to 1,020 instead of 1000 or 969. In the QTY and Summary loops, it also needs
to be 1,020.
·
Example 9, BPT 01
needs to be “EX”.
·
Example 10 through
12, Take “F” out, and the word “final” in the BPT loop.
·
Examples 10 through
12, change all uses of Subtractive, Additive, etc. to number codes. Change the descriptions accordingly.
·
Change gray box in
Power Region Code from “required” to “required when ERCOT is the receiver of
the transaction, otherwise not used”. This is change control 77. It is approved for Version 1.3.
867-02
·
Review above changes
in 867_03 to see if applicable to 867_02.
867_04
·
Add “TN” code to
867_04.
·
In REF G7, Add N004,
No Ground Rod.
Open Issues List |
|
|
Date |
Issue |
Approach |
12/20 |
1) 814_28/29 – PC and PD In
our minutes of 01-02 Nov, information is provided related to potentially
continuing to develop the 814_28 and 814_29 to use for Customer
Maintenance. As reflected in the
minutes: this is for REPs that will
not handle service calls/outage notification calls. This would allow CRs to submit end use customer
information/updates to ERCOT and/or the TDSP. Is this still being considered or is this a closed issue and
the 814_28/29 dead? This is in the Ts&Cs and is expected to be
resolved for the Phase II of the ERCOT time frame. |
Pending RMS approval |
1/11 |
Overpayments: Negative values at the invoice level in the 820 are
allowed as long as the total remittance amount is still a positive deposit
amount to the bank. Other questions on over payments at an ESIID
level? Credit balance on an ESIID? Currently the implementation guide does not provide
balances in the 820 – this may be a gap that should be discussed – over payments
need to be communicated to the correct MP. |
|
1/24 |
Muni/Coop Invoice |
In progress |
1/31 |
Submit a Protocol change for Move-in Un-executeable (not
for overbooking) |
|
3/21 |
Future method to reject 820 for bad ESI-ID, bad
invoice #, etc. To be handled after
pilot. |
To be handled after pilot. |
3/21 |
“Tax” statement from the PUC – waiting for answer from
State Controller’s Office. |
Cary Reed to Check |
3/21 |
Charges
not associated with consumption after the customer has switched away – The
TDSP 810 should not reference the 867.
We can change the 867 to optional, change the gray box, so that it is
not required for when the cost is not associated with an 867. Add a gray box
for late payment charges or invoices not used. |
Johnny Robertson will write change control. |
3/21 |
TDSP
creates 814_20 for new customer to set a new ESI ID, while construction is
taking place. TDSP allows wire
installs, builds customer directly.
When the customer wants a meter, TDSP needs a CR. This is where the 814_20 comes in. But then CR will send request to set meter
in 650. CR also sends an 814_01 to
ERCOT Enrollment request, and ERCOT will reject because they don’t have the
meter information. The best solution
could probably be send an 814_04 without meter information, and then an
814_20 ESI ID. This would require a
modification to the 814_04. |
To be discussed in April Meeting. Cary Reed to write
Change Control. |
|
|
|
Items Closed
at this Meeting: |
|
|
3/21 |
Overpayments
– not resolved. If, for example,
Green Mountain Power overpays TXU for an ESI ID, Green Mountain Power would
never be notified. The discussion is
that the TDSPs would notify by phone.
Either the CR can ask for a check to be cut or the CR can underpay a
future charge to use up the credit balance. |
TDSPs will monitor for CRs and notify after a
few months. |
3/21 |
If a premise is de-energized, and the TDSP sends an
867_03 to ERCOT…will ERCOT reject the transaction? |
ERCOT will not reject but
it could contribute to UFE if there is usage not associated with a CR. |
|
|
|
Attendance:
Name |
Affiliation |
Phone |
E-Mail |
Fred
Plett |
Logica |
603-497-3907 |
Plettf@logica.com |
Jill
Popelka |
TXU |
972-679-5064 |
Jill.popelka@txu.com |
Heidi
Schrab |
Reliant |
713-207-3976 |
|
Cary
Reed |
AEP |
918-594-4026 |
Careed@aep.com |
Dave
Bynoe |
Shell |
713-241-0429 |
Rbynoe@shell.com |
Jill
Prince |
TXU |
214-875-1545 |
|
Johnny
Robertson |
TXU |
214-812-2712 |
|
Kathy
D. Scott |
Reliant
Energy |
713-945-6630 |
Kathy_D_Scott@ReliantEnergy.com |
Christine
Melovo |
New
Power |
704-502-2114 |
Christine.Melovo@us.arthurandersen.com |
Lorraine
Bucci |
Exelon |
610-676-7387 |
Lorraine.Bucci@Exeloncorp.com |
Nancy
Hetrick |
Enron |
712-366-3399 |
Nancy.Hetrick@enron.com |
Carrie
Landis |
XCEL
/ SPS |
303-571-7310 |
Carrie.Landis@Xcelenergy.com |
Susan
Neel |
Reliant |
713-207-3519 |
Susan_J_Neel@reliantenergy.com |
Darrell
Hobbs |
TXU |
214-875-2204 |
Dhobbs2@txu.com |
Kyle
Patrick |
Reliant |
713-207-3519 |
Kyle_Patrick@reliantenergy.com |
Mike
McCarty |
ERCOT |
512-248-3959 |
Mmccarty@ercot.com |
David
Lotspeich |
ERCOT |
512-248-3171 |
David.m.lotspeich@accenture.com |
Robert
Connell |
ERCOT |
512-248-3963 |
Rconnell@ercot.com |
Sharon
Polliard |
AEP |
918-594-2265 |
Spolliard@aep.com |
Dave
Robeson |
Entergy |
504-576-2571 |
Drobe90@Entergy.com |
Kim
Wall |
Green
Mountain Energy |
610-799-2740 |
Kim.Wall@greenmountain.com |
Next Change Control Conference Call – Monday,
March 26th, 2:00 CST.
Next Meeting – Dallas, April 10th and
11th, hosted by TXU. Johnny
Robertson to send out directions and location information.