Proposed Standard Transaction Set
Executive Summary

The California Public Utility Commission in conjunction with the California Legislature has ruled that deregulation of the Electric Utility Industry go into effect January 1, 1998.  A new market will require new rules to govern the movement of product and the attendant customer data.  This document recommends a set of proposed transactions and the rules associated with them.  These are the proposed transactions and rules that will be used by UDC and ESP participants in the new market to communicate to one another. The transactions in this document are based upon those used in existing pilots, UIG standards and ANSI standards.  

The participants of the UDC-ESP communication sub-committee believe that the transactions should address the majority of the communication needs for the new market.  These transaction sets assume the use of a Value Added Network (VAN) to transport the data.  However, these transactions could also easily be implemented over other communication mediums, should the Internet be selected over the VAN.  It is the intention of the group to use this document as a starting point which will act as a building block for development of a consensus documents which outlines the communication standards for the new retail electric market.

The participants of the UDC-ESP communication sub-committee believe that the transactions should address the majority of the communication needs for the new market.  These transaction sets assume the use of a EDI standards to format the data.  These transactions can  easily be implemented over communication mediums including but not limited to VANs, and/or the Internet. It is the intention of the group to use this document as a starting point which will act as a building block for development of a consensus documents which outlines the communication standards for the new retail electric market using establish communications formats and protocals.  (SDGE)

Retail Settlement and Information Flows
UDC-ESP Communication Supplement
Table of Contents

BASIC UNDERSTANDINGS AND GUIDING PRINCIPLES	3
Business Transaction Set	4
Enrollment	5
Direct Access Service Request (x.12 #814 from UIG)	5
DASR Acknowledgement	6
Successful DASR Submission	6
Unsuccessful DASR SubmissionSchedule Date for Switch (x.12 #814 from UIG)	9
Customer Account Information (x.12 #814 from UIG)	9
Customer Usage Information	9
Multiple Supplier Requests	10
DISPUTE (x.12 #814 from UIG)	10
Supplier Switch	
Supplier Dispute	11
Misuse of Supplier Dispute Procedure	12
TERMINATE	12
Service Terminated by UDC	12
Service Terminated by Supplier	12
BILLING	13
Dual Billing	14
Consolidated Billing	15
SETTLEMENT	13
Dual Billing	14
Consolidated Billing	15
Maintenance Transaction	19
Customer Information	19
Immediate Outage Notification	21
Dispute Mechanism	22
Testing Requirements – Electronic Data Transactions	22
Overview of Compliance Test	23
Standard Set Test Scenarios - UDC to Supplier	23
Testing - Competitive Supplier to UDC	23
Testing - UDC to Competitive Supplier	23
Discrepancy Resolution - Repeated Testing	24
Test Completion - Commission Notification	24

BASIC UNDERSTANDINGS AND GUIDING PRINCIPLES

The transactions documented in this report were developed using the following principles:

1.	The UDCs and ESPs will have service agreements
	
2.	The UDCs will begin accepting DASRs from ESPs on November 1, 1997.  
	
3.	Using the DASR process, the UDC shall be notified whenever a customer changes its ESP. 
	
4.	All market participants and jurisdictional UDCs, are subject to the rules and/or orders issued by the Commission. 
	
5.	UDCs are not responsible for the resolution of disputes relating to competitive services.  ESPs, customers or UDCs may request the assistance of the Commission in resolving such disputes in accordance with the dispute resolution procedures prescribed in its rules.
	
6.	Customers are responsible for evaluating and securing competitive services from ESPs. A customer is not required to select a provider.  If no selection is made to the contrary, the customer will receive default service provided by its existing UDC.
7.	Customers will be switched according to tariff schedules. 
8.	If a meter change is required, the switch will become effective when the UDCs schedules the removal of the existing meter and the installation of their meter.
	
9.	Termination of ESP service shall take effect at the end of a customer’s scheduled meter read cycle as defined by the ESP-UDC service agreement.  In the event the customer does not have in place a successor ESP, the customer shall automatically receive default UDC power service.
	
10.	The electronic delivery mechanism for the transfer of electronic data among all parties including, but not limited to, ESPs, UDCs, PXs, ISOs, and Scheduling Coordinators are interconnected VANs. Other possible communication protocols which may be explored are: WENet, Internet mail using encryption, authentication, etc. or a centralized UDC maintained bulletin board.  For the purposes of this document, the electronic delivery mechanism for the transfer of electronic data among all parties includes: ESPs and UDCs interconnected but not limited to VANs. Other possible communication protocols which may be explored are:  WENet, Internet mail using encryption, authentication, etc. or a centralized UDC maintained bulletin board.  (SDGE)
	
11.	EDI and the Internet ARE NOT necessarily mutually exclusive alternatives

12.	Absent mutual agreement to the contrary, any additions or modifications to the standard data transactions and record formats specified in this document must be approved by the Commission. Absent mutual agreement to the contrary, any additions or modifications to this document and the prescribed transactions and record formats specified must be approved by the Commission.  (SDGE)
	
13.	In the dual billing and ESP consolidated billing scenarios, the ESPs have the right to bill on their own schedule. UDC will continue to bill UDC charges based on UDC meter read schedules.  (SDGE)
 
14.	The timing of the delivery of meter data, both interval and monthly, will be based upon the schedule outlined in the Retail Settlement and Information Flows and the MDCS workshop.
 
15.	The UDC will continue to be the clearinghouse for all customer selections of an ESP and related transactions as they have a relationship with every customer.  This point is still under discussion.
	
16.	The efforts of this sub-committee and the resulting document do not address flows between ESPs and Scheduling coordinators. Those communications will be outlined in commercial agreements between the ESPs and their SC.
	
17.	Similarly, the ISO transactions have been defined by another body and are not part of the scope of this group.
	
18.	Transmission of information between ESPs and UDCs will be conducted in a reliable manner.

Business Transaction Set

The following section provides a detailed description of the standard data transactions proposed for use in the market and the business rules, which will govern their use.  A list of the standard transactions is included as Appendix B.  Appendix C contains the detailed record formats that characterize each transaction.  Appendix D defines each field used in each record format. 

It should be noted that all references to Transaction Sets and the associated Appendix are incomplete and require additional work to meet the needs of all parties involved.  (SDGE)

Enrollment

ENROLL:  ENROLL
The enrollment process pertains to initial enrollment subsequent changes to other ESPs.  A more detailed enrollment process flow is included in Appendix G

The preceding diagram reflects the anticipated business results, but does not specify all procedures involved.  

Direct Access Service Request

Registered ESPs shall obtain a verifiable commitment from each customer specifying the customer’s choice of supplier for each account.  The ESP shall request that the customer be enrolled only after the customer’s selection of the ESP has been verified as provided for by law and regulation.

Such information, in control of the parties, shall be retained, or shall be capable to be regenerated, for a period not less than three(3) years. 

Once a customer’s selection of an ESP has been verified, the ESP will electronically notify the customer’s UDC of the selection. The record format for this transaction is specified in Appendix C, I.  The UDC shall process ESP enrollments in the order in which they are received at the UDC’s electronic mailbox, as determined by the receipt computer’s date and time stamp on the received transmissions. The Direct Access Service Requests (DASR) submitted by a certified renewable provider will be given priority over DASRs submitted by those ESPs without renewables certification (subject to final DAIP order of the CPUC).  The renewables priority only applies when there is a bottleneck during a given month’s processing cycle.  (SDGE) The x.12 transaction which provides the basis for the DASR is 814.  By utilizing different flags and values, the same transaction can be utilized for each of the communications identified with enrolling a Direct Access customer.

DASR Acknowledgment

Once a DASR has been submitted received (SDGE), the UDC is required to respond within 24 hours to acknowledge the receipt of the DASR.  

SDGE reserves the right to contact the customer at any time to confirm the customers intent with any change to the account.

DASR Notification

DASRs received by a UDC will be processed each business day.  All DASRs received between the last UDC processing date and the current date will be processed together and receive the same approval date.  The approval date will be used to determine the time the DASR was processed by the UDC, if it becomes necessary to determine which DASR is valid.  The approval date is not the same as the meter switch date or the customer request date.  The approval date is the date the DASR was successfully processed by the UDC.

The UDC will send an acknowledgment verifying receipt of the DASR within one (1) business day of the ESP transmittal of the DASR, barring unforeseen circumstances. The UDC will send a notice to the ESP acknowledging acceptance, rejection, or pending status of the DASR within one (1) business day, barring unforeseen circumstances.  If the UDC is investigating the DASR, the DASR is said to be pending.  Pending DASRs will become rejected DASRs after 11 business days following receipt of the DASR.

New or subsequent DASRs from the same ESP, will overwrite, and therefore nullify, pending DASRs in process at a UDC. A termination transaction received by the UDC from the same ESP will cancel a pending DASR for the same customer.

If a new or subsequent DASR from a different ESP is received by the UDC while the current DSAR is pending the UDC will reject the subsequent DASR.  The UDC will send a rejection notice to the respective ESP notifying them of the rejection and the reason for rejection.

If two DASRs are received within the same one day (SDGE) processing period (would get the same approval date) at the UDC, both will be rejected.  Consequently, a rejection notice will be sent to the respective ESPs notifying them of the rejection and the reason for rejection.

It is the recommendation of this sub-group that one enrollment DASR (supplier switch) be permitted per month. This will prevent operational problems for all parties, and ultimately reduce overall costs.

Following acceptance of a new DASR, the UDC will send a notice to the existing ESP, if any, to inform the existing ESP of the customer’s ESP change within one (1) business day following the acceptance of the new DASR. The record format for this transaction is specified Appendix C, III.

The following describes SDG&E's position on DASR acknowledgment and processing.  To the extent this process differs from the current draft, we should state these differences so it will be clear that we don't intend to follow processing methods in the draft.

DASRs received via electronic data transfer will be acknowledged as successfully transferred by the receiving computer  within 24 hours and will be given a date/time stamp by the computer for use in setting priority in the event a processing bottleneck occurs. SDG&E will process DASRs in such a manner as to provide ESPs notice of a rejected DASR within five business days.  DASRs acknowledged as received by the UDC which are not subsequently rejected in this timeframe, should be considered accepted by the ESP.  (Acceptance of a DASR is not necessarily confirmation that the ESP will become the energy provider.  This confirmation will follow further processing by the UDC).  

CPUC Decision 97-05-040 creates a monthly processing cycle for DASRs, with the 15th of each month as the close of each processing cycle.  Valid DASRs received during a given monthly processing cycle will be placed on Direct Access service (or changed to the new ESP) on the regular billing date in the following month.  Within five working days following the close of the monthly processing cycle, SDG&E will provide each  ESP with a confirmation report of all successful DASRs including account information and the start date for those accounts not requiring meter installation.  Information on the coordination of meter installations will be handled separately.  In the event the DASR is causing a switch in ESPs, both the new and current ESP will be informed of this switch in this monthly confirmation report referred to above.  This confirmation report would typically be sent on approximately the 20th of each month, and contain information about accounts that will begin service or change service providers in the following month.  SDG&E considers this to be an adequate notification timeframe from the UDC to the ESP.

In the case where multiple DASRs are received from separate ESPs during the same monthly processing cycle (which SDG&E expects to be a relatively rare occurrence) SDG&E will hold action on all DASRs related to the disputed meter.  In this situation, SDG&E will contact the customer to determine the customer's intentions.

In regard to the current procedures described in the UDC-ESP Communication document,  SDG&E objects to the assertion that UDCs will process DASRs on a daily basis.  SDG&E also objects to anything other than a monthly processing cycle as described in D. 97-05-040 for purposes of determining priority when a bottleneck occurs in the processing cycle, and for resolving disputes resulting from multiple DASRs.    

Schedule Date for Switch

Where there is no meter requirement, the acceptance transaction will contain the scheduled commencement of the service date.  Once the DASR transaction has been scheduled for switching suppliers, the receiving UDC shall electronically notify the chosen supplier of the commencement date for service, and the existing supplier, if applicable, of the termination date of service.  The record formats and data requirements for these transactions are specified in Appendix C, I and II respectively.

Customer Account Information

The release of the initial customer account information, including account number, address, contact and service specific information will be transmitted from the UDC to the ESP no later than 10 business days before the scheduled switch effective date.  This transaction will be sent upon acceptance only.  This transaction will utilize the same transaction outlined in the Account Maintenance section of this document.  Account Maintenance transactions related to the initial switch will be flagged as initial.

Customer Account information will be provided in the monthly confirmation report per CPUC decision.  (SDGE)

Customer Usage Information

Customer usage information (15-minute interval data) will be delivered to new ESPs via the MDMA server.  For the initial direct access election, the UDC will be responsible for formatting the maximum available, up to 12 months, worth of historical usage information (for the customer at the location) into the MDMA format.  This data should be posted and available on the new ESPs MDMA no later than 10 business days before the scheduled switch effective date.  The ESP will then utilize the MDMA access method for accessing its new customer’s historical usage data.

For subsequent switches, the ESP will be responsible through its MDMA to provide the succeeding ESP’s MDMA historical data (maximum available up to 12 months) in the then current standard format, within the same time frames outlined for the initial transfer. 

The UDC will be responsible for providing up to 12 months of customer usage information in the stand format as determined by the Customer Information Data Workshop. Customer Account information will be provided in the monthly confirmation report per CPUC decision.  (SDGE

Multiple Supplier Requests

Our recommendation to the Commission is the following process for addressing multiple service requests.

If a new or subsequent DASR from a different ESP is received by the UDC while a current DASR is pending, the UDC will reject the subsequent DASR.  The UDC will send a rejection notice to the respective ESP notifying them of the rejection and the reason for rejection.

If two DASRs are received within the same processing period (would get the same approval date) at the UDC, both will be rejected.  Consequently, a rejection notice will be sent to the respective ESPs notifying them of the rejection and the reason for rejection.

It is the recommendation of this sub-group that one enrollment DASR (supplier switch) be permitted per month. This will prevent operational problems for all parties, and ultimately reduce overall costs.

Customer Account information will be provided in the monthly confirmation report per CPUC decision.  (SDGE

DISPUTE

Whenever a customer elects to change its ESP, the new ESP must electronically notify UDC of the requested change.  The customer's existing ESP may, however, dispute the change. In such an event, the UDC shall observe the following rules:  

There were no examples provided of valid ESP disputes.  Two mentioned were:
•	Contract terms
•	Outstanding or delinquent balance

PG&E’s position is that the dispute needs to be resolved between the customer and the ESP or between the new and old ESPs.  PG&E does not have a protocol for disputed DASR change forms and does not want to be responsible for mediating such disputes (PGE)

SDGE restated the PGE position.  (SDGE)

Neither of these is enforceable beyond the terms of the customer contract, which should offer commercial recourse.  

Are there any justifiable disputes, which should postpone the processing of a DASR?

Supplier Dispute

To dispute a supplier change request, the existing ESP must electronically notify the UDC of its objection within two (2) business days of receiving notification from the UDC.  The record format for this transaction is specified in Appendix C, III. In the event a dispute notice is received during the two (2) business day window, the new ESP shall be notified of the dispute and the supplier change request canceled.  The record format for this transaction is specified in Appendix C, III.

Misuse of Supplier Dispute Procedure

ESPs who utilize the ESP dispute procedure described above without sufficient reason will be subject to penalty as prescribed in Commission rules.  The first ESP contract shall not be terminated, and the payments shall be accounted for in arrears.  

TERMINATE

Service Terminated by UDC

In the event a customer fails to pay the full amount billed for UDC charges  (SDGE) (UDC consolidated and dual billing scenarios), the UDC may terminate service to the customer in accordance with Commission disconnection procedures specified in its rules.  The UDC shall notify the customer's ESP electronically of the service termination within one business day from the day that the disconnection notice is issued to the customer and when disconnection occurs. The record format for this transaction is specified in Appendix C, II. 

Service Terminated by Supplier

Termination of service by an ESP shall be at will or controlled by the specific terms and conditions of the power agreement with the customer, unless otherwise amended by Commission rules and/or orders.  The ESP must notify the UDC electronically of its intent to terminate service at least ten (10) calendar days prior to the customer’s next scheduled meter read date.  The record format for this transaction is specified in Appendix C, I. ESPs must notify the customer that they have ten (10) calendar days to find another ESP before being automatically assigned to the UDCs default service.  Following the receipt of valid notification, the UDC will terminate ESP (SDGE) service to the customer upon the customer's next scheduled meter read date. Customers whose ESP’s service (SDGE) has been terminated will automatically receive UDC’s default power service in accordance with Commission rules. 

BILLING

Three billing options will be offered in the California Market. The frequency and types of flows varies greatly across the three billing options.  The most complex series of flows occurs in the case of consolidated billing regardless of whether it is being performed by the UDC or the ESP.  In both cases, there are classes of transactions which would never be transmitted between those two entities if they were developing their individual bills.  The dual billing scenario involves the simplest information flows of the three billing options. 

Three billing options will be offered in the California Market. The frequency and types of flows varies greatly across the three billing options.  The most complex series of flows occurs in the case of consolidated billing regardless of whether it is being performed by the UDC or the ESP. The dual billing scenario involves the simplest information flows of the three billing options.  (SDGE)

Dual Billing

In the dual billing scenario, UDCs and ESPs communicate upon sign up, termination and modification of customer account information.  The majority of the transactions involved with dual billing were outlined above.  The only remaining flow is between the MDMA (Meter Data Management Agent) and the ESP.  This transaction will be performed in accordance with the process outlined by MADAWG and the MDCS Workshop.  Accordingly, customer usage information will posted by the Metering Agent the MDMA server.

Interval meter data will be made available at 15 minute intervals, with all of the data available on the MDMA server by midnight of the following business day.  The record for this transaction is found in Appendix E of the MDCS Workshop Report.  This is outside the scope of this workshop and should be taken out.  (SDGE) 

The majority of the required transactions are governed by commercial agreements between market participants and will be governed by agreements between the two commercial entities. 

Consolidated Billing

In either consolidated billing scenario, the information flows become much more complex.  Under the dual billing scenario, financial transactions between the ESPs and the
for service.  Under consolidated billing, the ESP and UDC enter into a fiduciary responsibility for the other.  These transactions require immediate transmittal due to cash flow considerations.  These transactions are listed in the key shown in this diagram.

PG&E will support methods in the PG&E tariff.  PG&E will define time of use periods and price information per associated time periods.  PG&E will not support communication of non-energy charges for January 1, 1998.

Consolidated UDC Billing

Information to be used on the UDC consolidated bill from the ESP will consist of print ready lines of text.  The ESP will be responsible for calculating the dollar amount of the bill and forwarding the information to the UDC.  Use the record format in Appendix C, V.  
Each UDC will be responsible for calculating, and communicating, franchise fees and user taxes under this billing scenario. 

Each UDC will be responsible for calculating, and communicating CTC charges.  (SDGE)

There are differences between the UDCs consolidated billing strategies.  The information flow of all UDCs, however, will follow the same timing.  The MDMA will provide settlement ready meter data on the MDMA server according to the rules established by the MDCS. The ESP will transmit the billing information to the UDC within two (2) business days following the posting of the settlement ready meter data.  The UDC will transmit the status of the bill within one (1) business day upon receipt of the ESP billing information transmission.  If the billing data has not been received as established in the tariffs, the bill will be sent out without that information.

SDGE will require transmission of billing data from the ESPs no later that 6:00 pm of the second working business day.  ESPs requiring additional time can be accommodated with a service charge.  (SDGE) 

The UDCs determined a unique customer identifier is required.  A bill start and stop date and time are required.
A meter read start and stop date and time are required.
All data will be transferred at the meter level using the UDC meter identifier.  Extra pages per bill will be given according to tariff rules and restrictions, and the ESP-UDC service agreements.  Changes to billing options will be changed with effective dates given.  The bill amount, text, and bill details will be on the back pages per the tariff rules and restrictions and the ESP-UDC service agreements. A unique meter identifier will be implemented eventually, if further analysis deems implementation to be cost effective. Print font size, and font attributes will be addressed in ESP-UDC service agreements.  This subgroup determined that communications of non-energy charges, not the collection of these charges, is within the scope of this subgroup.

PG&E determined that they will not provide meter read start and stop date and times initially.  PG&E will not support the ESP sending the ESP bill amount on January 1, 1998.  They will calculate the ESP portion of the bill using the ESP supplied rate and time of usage data.  PG&E will support methods in the PG&E tariff. PG&E will not support communication of non-energy charges for January 1, 1998.

Consolidated ESP Billing

Information to be used on the ESP consolidated bill from the UDC will consist of print ready lines of text.  The UDC will be responsible for calculating the dollar amount of the bill and forwarding the information to the ESP.  Use the record format in Appendix C, V.

Each UDC will be responsible for calculating, and communicating, franchise fees and user taxes under this billing scenario.

The information flow of all UDCs, however, will follow the same timing.  The MDMA will provide settlement ready meter data on the MDMA server according to the rules established by the MDCS. The UDC will transmit the billing information to the ESP within two (2) business days following the posting of the settlement ready meter data.  The ESP will transmit the status of the bill within one (1) business day upon receipt of the UDC billing information transmission.  If the billing data has not been received as established in the tariffs, the bill will be sent out without that information.

SDGE will transmit billing information to the ESPs within (1) business day following the posting of the settlement ready meter data.  (SDGE)

The ESPs determined a unique customer identifier is required.  A bill start and stop date and time are required.
A meter read start and stop date and time are required.
All data will be transferred at the meter level using the UDC meter identifier.  Extra pages per bill will be given according to the ESP-UDC service agreements.  Changes to billing options will be changed with effective dates given. The bill amount, text, and bill details will be on the back pages per the tariff rules and restrictions and the ESP-UDC service agreements. A unique meter identifier will be implemented eventually, if further analysis deems implementation to be cost effective. Print font size, and font attributes will be addressed in ESP-UDC service agreements.  This subgroup determined that communications of non-energy charges, not the collection of these charges, is within the scope of this subgroup.

PG&E will support methods in the PG&E tariff.  PG&E will define time of use periods and price information per associated time periods.  PG&E will not support communication of non-energy charges for January 1, 1998. 

PG&E will support methods in the PG&E tariff. Refer to PGE tariffs.  (SDGE)

SETTLEMENT

There are two settlement transactions required between the ESPs and UDCs.  The first transaction describes the settlement for end use customer charges and applies only in the UDC and ESP consolidated billing scenarios.  The second transaction describes the UDC and ESP settlement for non-end use customer charges and applies to all billing scenarios.

UDC Consolidated Billing Settlement for end use customer charges

The settlement is based on end use ESP bill by meter.  The payment advice will be sent in bulk and will list individual payments in detail per the tariff rules and restrictions.  The transaction must contain ESP and UDC customer identifiers, amount paid, ESP charges, method of payment, payment identifier, and wire number.

The UDC will transmit the payment advice as per tariff rules and restrictions.  The ESP will transmit an acceptance or rejection of the payment advice (exception report) within one (1) business day of receipt of the payment advice from the UDC.

This transaction is additional to the EFT payment transaction, which is not addressed by this subgroup.

PG&E will send remittance for accounts receivable according to the tariff rules and restrictions.  PG&E will not be “settling” for ESP charges as they will be buying the receivables outright from the ESPs.

ESP Consolidated Billing Settlement for end use customer charges

The settlement is based on end use UDC bill by meter.  The payment advice will be sent in bulk and will list individual payments in detail per the tariff rules and restrictions.  The transaction must contain ESP and UDC customer identifiers, amount paid, UDC charges, method of payment, payment identifier, and wire number.

The ESP will transmit the payment advice as per tariff rules and restrictions.  The UDC will transmit an acceptance or rejection of the payment advice (exception report) within one (1) business day of receipt of the payment advice from the ESP.

This transaction is additional to the EFT payment transaction, which is not addressed by this subgroup.

UDC and ESP Settlement for non-end use customer charges

This will be sent as a separate invoice.  The invoice will contain line item details (by UDC meter number) of non-end use customer charges.  The invoice will be sent once per month.  This transaction will also be used to charge for non-performance charges.

This transaction will include charges for DASR switches.  This charge will be charged upon a successful switch, and not upon rejections.  

The transaction will contain item number, item description, date of charge, amount of charge at a minimum.  

Payment of charges will follow tariff rules and restrictions.

Maintenance Transaction

Customer Information 

The customer account maintenance transaction will be utilized in two instances, initial set up with a newly selected ESP, and for subsequent updates to account information.  

Customer Account Establishment

The initial setup with a service provider will always originate with the UDC.  Since the UDC is involved with each customer on at least a distribution basis, it is logical that the UDC be the primary holder of customer account information.  In addition, the UDC is required to be the first entity contacted in order to obtain electric service. The UDCs will establish most if not all customer accounts. 

The UDC will send an acknowledgment verifying receipt of the DASR within one (1) business day of the ESP transmittal of the DASR, barring unforeseen circumstances. The UDC will send a notice to the ESP acknowledging acceptance, rejection, or pending status of the DASR within one (1) business day, barring unforeseen circumstances.  The acceptance transaction will contain the customer’s account information.

Process will follow procedures established under the DSAR Notification.  (SDGE)  

Fields that identify special needs customers, e.g. life support, must be included with the initial exchange of customer information between the existing supplier (or UDC) and the new supplier.

Customer Account Maintenance 

Once a customer has an account with an ESP and the UDC, problems associated with distributed data are introduced. The customer could feasibly contact either party with updates to their information.  An ESP could change the equipment associated with a customer.  Both of these are examples of where information must be shared with other entities related to providing that customer with electricity.  Any changes to customer account information must be transmitted to the other parties as quickly as practical.  The ESP will send an acceptance or rejection transaction (of the changes) to the sending UDC within 2 business days.

The Customer Account Transaction will be able to be used for a single field update or for multiple field update.  An indicator will be included in the transaction in order to tell how the transaction should be applied.

In an attempt to maintain data integrity, a “last updated” field must be included with the transaction.  The receiving party can then perform a comparison with the last updated date on their own customer information system to determine the trustworthiness of the data received.  If there is a conflict between the dates, conflicting transactions should be queued for manual review.  Through the manual review process, the appropriate data can be determined.  

The UDC and ESP share equally in the responsibility of maintaining accurate customer data.  Consequently, the UDC and ESP share an equal responsibility to resolve conflicting transactions.  The UDC and ESP will contact one another in the case of data conflicts and determine ownership for the specific conflict.  The conflict owner will be responsible for contacting the customer (when required), altering the data appropriately, and sending a customer account maintenance transaction to the other interested parties as quickly as practical.  By establishing one conflict owner, the customer will only be contacted by one party, when contacting the customer is required.

The format for the customer information transaction is included in Appendix C.

Immediate Outage Notification

The ESP to UDC outage notice mechanism will be immediate.  If the ESP is the party receiving notification of an outage, the ESP will call the UDC immediately to inform them of the outage. Alternatively, if the ESP may transfer the customer immediately to the UDC phone center to directly report the outage to the UDC.  

If the UDC receives an outage notification, and the outage requires a change in equipment, the UDC will send a customer account maintenance transaction to the ESP as quickly as practical.  

Dispute Mechanism

In addition to those general transactions, pilot experiences in New Hampshire and Massachusetts indicate that the creation of an interface, not only from a systems perspective but from an organizational perspective.  These “help desk” entities need to exist within each market participant’s organization to handle inquiries from other market participant’s organizations.  The existence of a “help desk” on both sides of disputed issues would simplify discrepancy resolution.  

This “Help Desk” function would insulate each market participant from needing to intimately know the internal organization of every other participant in order to resolve issues.  Depending on the organization, the prospect of navigating a fairly sizable organization to conduct business could become a barrier to market participation.

Alternative Dispute Resolution

An independent industry reconciliation board should be appointed to impartially decide on issues, which can not be settled by market participants.  In the absence of this body, the CPUC step in to adjudicate disputes, especially where one of the entities is regulated.  

This is outside the scope of this workshop and should be eliminated from this report.  (SDGE)

Testing Requirements – Electronic Data Transactions

As part of the Commission’s registration requirements, and prior to providing power supply service to any retail customer, a supplier of competitive services must demonstrate its capability to electronically send (receive) data to (from) each UDC in whose service area it intends to offer competitive services.  The purpose of the test is to verify that the supplier is complying with the data transfer standards specified in this document and has the necessary software and hardware required to send, receive, and translate the standard transactions.

Compliance testing for competitive suppliers will be accomplished by exchanging a standard set of test transactions with each UDC. The test will utilize transactions from the standard transaction set described herein, and verification of 100% error free transmission, receipt, and translation of the data by both supplier and UDC is required.  An approved data transfer system will be used for the data exchange tests.  Prior to the effective date for retail competition, each UDC must also demonstrate its capability to send and receive the transactions specified herein without modification to format or data elements.

Overview of Compliance Test

The compliance test shall require the complete and error-free transmission, receipt, and translation of test transactions for Enroll, Dispute, Terminate, Settlement, Telemeter, and Billing as described herein.

ESPs must pass UDC compliance testing prior to processing their first set of production data.  UDCs will provide test scripts and data for interface testing and ESPs will provide evidence of successful testing. (SCE)  (SDGE)

Standard Set Test Scenarios - UDC to Supplier

The ESP shall contact UDC in whose service area it intends to do business and arrange for the exchange of test transactions. A diskette containing a standard set of test scenarios will be forwarded by the UDC to the supplier.

Testing - Competitive Supplier to UDC

The ESP will initiate the test by creating the test transaction files with its software and	post the files to the UDC’s electronic mailbox. The UDC will retrieve and translate the test transactions and verify the accuracy of the received data.

Testing - UDC to Competitive Supplier

Once the foregoing test is satisfactorily completed, the UDC will send a set of test transactions to the competitive supplier’s electronic mailbox.  The supplier will retrieve and translate the test transactions and verify the accuracy of the received data.

Discrepancy Resolution - Repeated Testing

The UDC and supplier will work to resolve any discrepancies in transmitted or received data and confirm correctness by repeating the test data exchanges described above until both parties are satisfied that consistently error free results can be accomplished.
 
Test Completion - Commission Notification

Upon successful completion of the test, the UDC shall notify the Commission in writing that the competitive supplier has satisfied the data transmission component of the registration requirements.

Appendix A
Glossary of Terms

ANSI				Acronym for the American National Standards Institute. This organization is responsible for approving and disseminating Electronic Data Interchange Standards.

ASC X12			ASC X12 represents the Accredited Standards Committee X12. It is comprised of government and industry members who create the EDI standards for submission to ANSI. (Definition of X12)?

ASCII			ASCII stands for the American Standard Code for Information Interchange, and is the uniform character set used by many computer systems so that data can be interchanged between various central and remote computers and peripheral devices.

COMMUNICATIONS
TRANSPORT PROTOCOL	The COMMUNICATIONS TRANSPORT PROTOCOL is the method used to support the exchange of protocol related information needed to ensure the efficient flow of data over a network, terminal, modem, microcomputers, workstations, concentrators, front-end processors, and host computers. Examples of such protocols are FTP, TCP/IP, NFS, and XMODEM.

EDI				EDI stands for Electronic Data Interchange. It is a term used for computer data transmission.  

ENROLL			The act of registering with a competitive Supplier for the provision of either electric power or meter reading equipment or services.

ESP	Energy Service Provider.

ISO				Independent System Operator.  

SEGMENT			A SEGMENT identifies the type of information that is included in a transaction set. There may be multiple segments in a specific order within a transaction set. A segment is assigned a usage requirement designator of Mandatory, Optional, or Conditional.

STANDARDS			STANDARDS are the technical documentation approved by ASC X12. They consist of the transaction sets, segments, data elements, code sets and the interchange control structure. Standards provide the framework for how an EDI message will be formatted for transmission.

TRANSACTION SET	A TRANSACTION SET defines the information that is relevant to a particular business transaction such as an invoice or a purchase order. It consists of a header segment, one or more  data segments in a specified order, and a trailer segment. It is the electronic equivalent of a “business document”.

TRANSMISSION LOSS	A TRANSMISSION LOSS occurs when energy is lost by transmission facilities while moving energy across the system.

UDC	Utility Distribution Company

VAN				Acronym for Value Added Network.  A network managed by a third party which is used for exchanging data in electronic format. Each participant who uses the network has an “address” for the purpose of sending and receiving files. Communications services such as electronic mailboxes and other communications services are provided for a fee to that particular participant. 

Appendix B
Open Access Transactions

Insert table to outline:
•	Business Process
•	Business Transaction
•	Flow Direction
•	Frequency
•	Timing
•	Format or transaction

LEGEND:	EESP 	=	Existing Energy Service Provider
NESP	=	New Energy Service Provider
UDC	=	Utility Distribution Company

Appendix C
Transaction Record Formats

I.	Supplier Activity Rec–rd - Supplier to Distribution Company.

This record layout reflects the records that the Suppliers will be sending to the distribution companies for supplier change, and terminations

A.	Header Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(H - Header Record)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Distribution Co. ID	Pic X(4).	Distribution Co’s Identifier
•	Transmission Date	Pic 9(8).	File Transmission Data

B.	Detail Record .......... ( Multiple Per Transmission ):

•	Record Type		Pic X.		Type of Record 
•	Supplier Acct Number	Pic X(20).	Supplier Customer Account Number
•	Disco Acct Number	Pic X(20).	DISCO Customer Account Number
•	Customer Last Name 	Pic X(4).	First 4 character of customer’s last name
•	Option Code		Pic X.		Billing Option Code
•	Supplier Rate class	Pic XXX.	Supplier rate class for Option A only
•	Supplier Pricing option	Pic 9(5)		Supplier Price Option for Option A only
•	Supplier Transaction code	Pic XX.		Supplier Transaction Code

C.	Trailer Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(T - Trailer Record)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Record Counts		Pic 9(7).	Number Detail Records TransmittedII.	

II.	Disco Activity Record - Distribution Company to Supplier.

This record layout reflects the records that the Distribution company will be sending to the Suppliers for enrollment notification, movement, and terminations.

A.	Header Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(H - Header Record)
•	Distribution Co. ID	Pic X(4).	Distribution Cos Identifier 
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Transmission Date	Pic 9(8).	File Transmission Data

B.	Detail Record .......... ( Multiple Per Transmission ):

•	Record Type		Pic X.		Type of Record 
•	Disco Acct Number	Pic X(20).	DISCO Customer Account Number
•	Customer Last Name 	Pic X(4).	First 4 character of customer’s last name
•	Supplier Acct Number	Pic X(20).	Supplier Customer Account Number
•	Option Code		Pic X.		Billing Option Code
•	Supplier Rate class	Pic XXX.	Supplier rate class for Option A only
•	Supplier Pricing option	Pic 9(5)		Supplier Price Option for Option A only
•	DisCo Transaction code	Pic XX.		DisCo Transaction Code
•	Billing Cycle	       	Pic XX.		Billing cycle assigned to account.
•	Projected Load Date	Pic 9(8).	Projected date of changed load responsibility •	Error Code		Pic 9(2).	Error Code

C.	Trailer Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(T - Trailer Record)
•	Distribution Co. ID	Pic X(4).	Distribution Co’s Identifier 
•	Record Counts		Pic 9(7).	Number Detail Records Transmitted

PG&E will require fields such as meter agent information, status information, commodity information, meter ID, load point, or template ID for DASR transactions (PGE)

III.	Dispute Transaction Record Format – Supplier to Distribution Company.

This record layout is to be used for records moving between the ESP and the UDC, or some governing body, for the purpose of initiating, acknowledging, and resolving disputes.  This transaction is used for disputing existing supplier switches.
Note:	On days that there are no dispute records to transmit, a header and a trailer record with a record count of zero will be transmitted.

A.	Header Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(H - Header Record)
•	File Type		Pic X.		Type of File
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Transmission Date	Pic 9(8).	File Transmission Data

B.	Detail Record .......... ( Multiple Per Transmission ):

•	Record Type		Pic X.		Type of Record 
•	File Type		Pic X.		Type of File 
•	Distribution Acct Number	Pic X(4).	DisCo’s Account Number
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Customer Last Name 	Pic X(4).	First 4 character of customer’s last name
•	Supplier Acct Number	Pic X(20).	Supplier Customer Account Number
•	Dispute Code		Pic X(4).	Billing Option Code
•	Activity Code		Pic XX		Activity Code 
•	Acknowledging Agncy	Pic X(4).	Acknowledging Agency Identifier 
•	Acknowledgeing Agent	Pic X(4).	Acknowledging Agent Identifier 
•	Resolving Agency	Pic X(4).	Resolving Agency Identifier 
•	Resolving Agent		Pic X(4).	Resolving Agent Identifier 
•	Dispute Details		Pic X (100).	Type of File (Explanation Verbiage)
•	Existing Supplier ID No	Pic X(20)	Dispute Supplier Acct Number

C.	Trailer Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(T - Trailer Record)
•	File Type		Pic X.		Type of File 
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Record Counts		Pic 9(7).	Number Detail Records Transmitted

IV.	Customer Maintenance Transaction:

This record layout is to be used for records moving between the ESP and the UDC for Customer data changes.

A.	Header Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(H - Header Record)
•	File Type		Pic X.		Type of File (D – Cust Data File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Bill Cycle Date		Pic 9(8).	Billing Cycle Date
•	Transmission Date	Pic 9(8).	File Transmission Date

B.	Detail Record .......... ( Multiple Per Transmission ):

•	Record Type		Pic X.		Type of Record 
•	File Type		Pic X.		Type of File (D – Cust Data File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Option Code		Pic X.		Billing Option Code
•	Activity Code		Pic X.		Activity Code 
•	Disco Acct Number	Pic X(20).	DisCo Customer Account Number
•	Supplier Acct Number	Pic X(20).	Supplier Customer Account Number
•	Meter Number		Pic X(9).	Meter number
•	Supplier Billing cycle no.	Pic XX.		Supplier Billing Cycle number
•	Service Type	.	Pic XX.		Service Type of Account
•	UDC Billing cycle no	Pic XX.		DisCo’s Billing Cycle number
•	Grid Point		Pic X(10).	Grid Point Identifier
•	Customer Type           	Pic X(4)		Relationship to Account
•	First Name              	Pic X(25)	First Name
•	Last Name		Pic X(25)	Last Name
•	Middle			Pic X		Middle Initial
•	Address Line 1		Pic X(25)	Address Information
•	Address Line 2		Pic X(25)	Additional Address Information
•	Address Line 3 		Pic X(25)	Additional Address Information
•	City			Pic X(15)	City Name
•	State			Pic X(2)		State Initials
•	Zip			Pic X(9)		Zip Code
•	Service Establish Date	Pic X(8)		Date service established
•	Service End Date	Pic 	Pic X(8)		Date service terminated
•	Phone Type	    	Pic X(2)		Phone Type
•	International Access	Pic 9(4)		International Access Code
•	Area Code		Pic 9(3)		Area Code
•	Phone Number		Pic 9(7)		Phone Number
•	Phone Extension		Pic 9(7)		Phone Extension•	
•	Phone Type		Pic X(2)		Type of phone
•	Zip			Pic X(9)		Zip Code

C.	Trailer Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(T - Trailer Record)
•	Record Date/Time	Pic X(15).	Date and Time Record Sent
•	File Type		Pic X.		Type of File (C – Bill Print File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Record Counts		Pic 9(7).	Number Detail Records Transmitted

V.	Customer Revenue Record Format: (Consolidated Billing)

This record layout is to be used for records moving between the ESP and the UDC for the consolidated billing options.
Note:	On days that there are no usage records to transmit, a header and a trailer record with a record count of zero will be transmitted.

A.	Header Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(H - Header Record)
•	File Type		Pic X.		Type of File (C – Bill Print File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Bill Cycle Date	Pic 	Pic 9(8).	Billing Cycle Date
•	Transmission Date	Pic 9(8).	File Transmission Data

B.	Detail Record .......... ( Multiple Per Transmission ):

•	Record Type		Pic X.		Type of Record 
•	File Type		Pic X.		Type of File (C – Bill Print File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Option Code		Pic X.		Billing Option Code
•	Activity Code		Pic X.		Activity Code 
•	Disco Acct Number	Pic X(20).	DisCo Customer Account Number
•	Supplier Acct Number	Pic X(20).	Supplier Customer Account Number
•	Billing cycle number	Pic XX.		Billing cycle number
•	Disco Rate Class		Pic XXX.	Distribution Company’s rate class
•	Current Read Date	Pic 9(8).	Current Read Date
•	Previous Read Date	Pic 9(8).	Previous Read Date
•	Dollar Amount		Pic S9(9)V99.	Amount for Bill Print
•	Bill Print Description	Pic X(60).	Text for Bill Print

C.	Trailer Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(T - Trailer Record)
•	File Type		Pic X.		Type of File (C – Bill Print File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Record Counts		Pic 9(7).	Number Detail Records TransmittedVI.	Customer 

Payment/Adjustment Record Format:

This record layout reflects the Supplier payments received by DisCo. These records will be transmitted to those Suppliers who use the Option A billing service. This daily transmission is to be completed by midnight of the same business day following receipt of payment at DisCo’s payment processing center, e.g., by midnight Wednesday following receipt on Monday.

This record layout also reflects the Supplier adjustments.  These records will be transmitted to DisCo Suppliers who use the Option A billing service. This daily transmission is to be completed by noon of the next business day.

A.	Header Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(H - Header Record)
•	File Type		Pic X.		Type of File–(P - Cust Payment File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Bill Cycle Date		Pic 9(8).	Billing Cycle Date
•	Transmission Date	Pic 9(8).	File Transmission Date
•	ACH Transfer Date	Pic 9(8).	ACH Transfer Date	

B.	Detail Record .......... ( Multiple Per Transmission ):

•	Record Type		Pic X.		Type of Record (D - Detail Record)
•	File Type		Pic X.		Type of File –(P - Cust Payment File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Disco Acct Number	Pic X(20).	DisCo Customer Account Number
•	Supplier Acct Number	Pic X(20).	Supplier Customer Account Number
•	Type Code		Pic XX.		Pay/Adjustment Code (See Section D)	
•	Type Description		Pic X(40).	Type Description	
•	Payment/Bill Date	Pic 9(8).	Payment Posting Date 
•	Pay/Adj Amount		Pic 9(9)v99.	Payment / Adjustment Amount
•	Filler			Pic x(10).	Filler of spaces

C.	Trailer Record .......... ( One Per Transmission ):

•	Record Type		Pic X.		Type of Record–(T - Trailer Record)
•	File Type		Pic X.		Type of File–(P - Cust Payment File)
•	Distribution Co. ID	Pic X(4).	DisCo’s Identifier (DisCo)
•	Supplier ID		Pic X(4).	Suppliers Identifier
•	Record Counts		Pic 9(7).	Number Detail Records Transmitted
•	Net Total Dollars		Pic S9(9)V99.	Total Dollars
•	Total supplier credits	Pic S9(9)V99.	Total credits
•	Total supplier debits	Pic S9(9)V99.	Total debits
•	Total ACH transfer    	Pic S9(9)V99.	Total dollars transferred
•	Total amt due         	Pic S9(9)V99.	Total amount due to DISCO

ACH Transfer Date:
This field will contain the date that the ACH transfer is expected to be deposited for the Distribution Company.

Activity Code:
This will contain a code to indicate the type of billing that was performed on the Account. Valid codes are:
0 = Normal On cycle bill
1 = Cancellation
2 = Manual Bill
3 = Final Bill
4 = Off cycle bill
5 = No bill
6 = Estimated on cycle bill
7 = Estimated off cycle bill
8 = Late read/Late booked
9 = Final for non-payment

Actual Pk KW:
This will contain the actual greatest peak measured in kilowatts during peak hours, if applicable.  Otherwise the field will contain zeroes. 

Actual Pk KVA:
This will contain the actual greatest peak measured in kilovolt-amperes during peak hours, if applicable.  Otherwise the field will contain zeroes.

Actual Ofpk KW:
This will contain the actual greatest peak measured in kilowatts during off peak hours, if applicable.  Otherwise the field will contain zeroes.

Actual Ofpk KVA:
This will contain the actual greatest peak measured in kilovolt-amperes during off peak hours, if applicable.  Otherwise the field will contain zeroes. 

Actual Shoulder KW:
This will contain the actual greatest peak measured in kilowatts during the shoulder periods, if applicable.  Otherwise the field will contain zeros.

Actual Shoulder KVA:
This will contain the actual greatest peak measured in Kilovolt-amperes during the shoulder periods, if applicable.  Otherwise the field will contain zeros.

Arrears Interest:
This field will contain any arrears interest charged on supplier arrears.  Otherwise this field will contain zeros.

Bill Cycle Date:
Date field on the header record indicating the billing date used by the UDC.  The usage records will be transmitted by midnight of this day. Format of the field is: YYYYMMDD 

Billing Cycle Number:
This is the current billing cycle for the Account assigned by the UDC. Similar to the DisCo Account number, this field may change at any time as the result of a reroute.

Billing Demand:
This field if needed will contain the demand that was used to bill the account.  This field is calculated depending on the rate.  For a cancellation this will contain the demand being canceled.  For a non demand rate this field will contain zeroes.

Note:	Currently the UDC tracks and processes usage at a component level by meter, i.e. peak, shoulder, and off peak for KW and KVA.  A determination on how the demand will be billed by Suppliers is needed in order to supply them the necessary information.
	
		Bill Print Description:
		Line item text to be printed on a Consolidated bill.

Current Bill Amount:
This will contain the total Supplier charges for the current bill.  This is an accumulation of the following Supplier charges: 
Total KWH Charges (Peak and Off peak)
Demand Charges
Customer Charge
Sales Tax
Arrears Interest

Current Peak Amount:
This will contain the total peak KWH Supplier charges.  This will contain the total KWH charges for non time of use Customers, and the total peak KWH charges for time of use Customers

Current Ofpk Amount:
This will contain the total off peak KWH Supplier charges for a time of use Customer.  Otherwise this field will contain zeros.

Customer Charge:
This field will contain any applicable supplier Customer charge.  Otherwise this field will contain zeros.

Customer Last Name:
This will contain the first four characters of the residential customer’s last name.  For a commercial industrial account this will be the first four characters of the name that is identified on the account.  This is used to ensure that the correct account is being processed.

Current Read Date:
This will contain the current read date.  This would either be the date the account was being billed to, or the date that the account was being canceled back to.  The format for the field is:  YYYYMMDD.

Demand Charges:
This field will contain the Supplier charges for the demand that was billed.  This will be dependant on the Customer’s rate.  For non demand Customers this field will contain zeroes.

DisCo Account Number:
This will contain the Account number assigned by the UDC to an Account.  If the Account number is changed due to a reroute this field would contain the new number. 

Note: This field may change at any time.

Distribution Company Transaction Codes: 

01=	Dispute notice received, stop transaction
02=	Change customer name
03=	Dispute notification too late
04=	Change cycle date
10=	Customer account in transition, unable to process
    	15=	Telemetering recorder failure
16=	Telemetering phone line failure
17=	Terminate telemetering service
18=	Terminal block installed
19=	Telemetering commission

Distribution Company  ID:
UDC’s identification abbreviation.   It will indicate the UDC for the Customer’s Account and the Company making the transmission.

		Dollar Amount:
		Calculated dollars per line item to be printed on a consolidated bill.

Error Codes:
01 =	Invalid record Type
02 =	Invalid UDC account number
03 =	Invalid Customer Name
04 =	Invalid Supplier account number 
05 =	Customer billing option not specified or invalid
06 =	Supplier rate class invalid or missing (Option A Only)
07 =	Supplier price option invalid or missing (Option A Only)
08 =	Invalid Transaction Code	

Existing Supplier ID Number: 
Existing supplier identifier for the existing supplier .  This will only be provided to a new supplier attempting to enroll a customer if the existing supplier disputes the transaction.

File Type:
Single byte indicating type of file being transmitted. Field is used on header, detail and trailer records. Valid values are: 
B = Billing file
C = Consolidated Bill Print file
D = Customer Data file
P = Payment file
U = Usage file

Net Total Dollars:
This field will contain the total of the Pay/Adj amount fields for the supplier.  This will be used to verify that the correct total was received.

Option Code: 
This will contain the billing option for the Account. The valid codes are: 	
1 = Option A
2 = Standard

Ofpk KWH:
Will contain the total off peak Kilowatt Hour Usage amount if applicable.  Otherwise the field will contain zeroes.

Payment/Adjustment Type Codes and Descriptions:
Type 01  = Payment Received from Customer
Type 02  = Transfer - Debit Adjustment
Type 03  = Transfer - Credit Adjustment
Type 04  = Bad Check - Debit Adjustment
Type 05  = Bad Check - Credit Adjustment
Type 06  = Arrears Interest - Credit Adjustment
Type 07  = Arrears Interest -Debit Adjustment
Type 08  = Flat Credit Adjustment
Type 09  = Supplier Write-Off - Supplier Changed
Type 10  = Supplier Write-Off - Account Written-Off (Account Charge-Off or Purge)
Note:	The only adjustment that comes from the Supplier will be a Type Code 08 -Flat Credit Adjustment.
Payment/Bill Date:
This is the date the payment/adjustment was processed by the UDC. The format of the field is YYYYMMDD.

Pay/Adj Amount:
This field will the payment amount or the adjusted amount.  This field is a numeric field and the amount should be processed in conjunction with the type code for debit or credits.

Peak KWH:
Will contain the total Kilowatt Hour Usage amount for non time of use customers and the total peak Kilowatt Hour Usage amount for time of use customers. 

Previous Read Date:
This will contain the last read date.  This date should be the same as the prior months new read date.  The format for the field is YYYYMMDD.

Projected Load Date:
The scheduled on-cycle meter reading date when the load will be terminated for an old supplier and be assigned to the new supplier.  Format of the field is: YYYYMMDD.
.

Rate Class:
This will contain the Customer’s UDC rate.

Record Count:
This field is on the trailer record in the variable-block file and will contain the total number of records transmitted for each record type.  It will be used to verify that the correct number of records was received.

Record Type:
Single byte indicating type of record in the variable-block file. Field is used on header, detail and trailer records. Valid values are:
H = Header record
    = Detail record descriptions
T = Trailer Record 

Sales Tax:
This field will contain the sales tax applied on the Supplier charges for commercial Accounts. For Customers exempt from sales tax this field will contain zeros.

Shoulder KWH:
Will contain the total shoulder Kilowatt Hour Usage amount if applicable.  Otherwise the field will contain zeros.

Supplier Account Number:
This will contain the Account number assigned by the Supplier to an Account. As the DisCo Account number may change at any time , Suppliers should utilize this field to identify their Customers.  If a supplier does not provide a unique account number, the DisCo account number will be substituted in this field.

Supplier Arrears:
This field will contain the total Supplier arrears amount.  Arrears interest is not included in this field.

Supplier ID:
Supplier’s identification number. This. It  will indicate the Supplier Company for the Customer’s Account and the Supplier for which the transmission is intended.

Supplier Pricing Option:
This contains a value to identify the price that the customer will be charged.  Each supplier rate class can support one or many pricing options.  This is required for the “Option A” billing option.

Supplier Rate Class:
This is a three character identifier for the supplier’s rate.  This is required for the “Option A” billing option.		

Supplier Transaction Codes:
01=	Add customer
02=	Drop customer
03=	Change (supplier price, rate, acct number, or billing option)
04=	Disputes switch
05=	Terminate telemetering service
06=	Request telemetering service
07=	Telemetering (RAPR) installed

Transmission Date:
Date field on the header record indicating date of transmission. Format of the field is:  YYYYMMDD  

Total Bill Amount:
This field will contain the total Supplier charges billed.  This is a total of:
Current Bill Amount
Supplier Arrears

Total Supplier Credits:
This field will contain the total of all the cash payments, and cash supplier credit transactions.

Total Supplier Debits:
This field will contain the total of all the cash supplier debit transactions.

Total ACH transfer:
If the Total Supplier Credits is greater than the Total Supplier Debits, this field will contain the total of the supplier dollars that are being transmitted via ACH.  Otherwise this field will contain zeros.

Total Amount due:
If the Total Supplier Debits is greater than the Total Supplier Credits, this field will contain the total amount that is owed to the UDC.  Otherwise this field will contain zeros.  	

Appendix G
Detailed Process Flows

I.	Direct Access Process Flow (includes energy flow and information flow)

II.	Detailed Enrollment Information Flow