The CCA Handbook. Chapter 5 Setting Up Electronic Communications & Compliance Testing. Version 2.0 May 1, 2015

Transcription

1 The Handbook Chapter 5 Setting Up Electronic Communications & Compliance Testing Version 2.0 May 1, 2015

2 Coordinating the provision of Community Choice Aggregation () services will require that and Community Choice Aggregators (s) follow a clear and consistent set of communication protocols. In addition to the communication necessary between and a, should a acquire a Direct Access (DA) customer, communication with the existing Electric Service Provider (ESP) is also necessary. For the most part, will use the California Retail Market protocols and electronic communication methods that were implemented in support of DA for exchanging transactions with a. There are new transactions exclusive to such as Mass Enrollment files. This chapter will provide the required information associated with establishing electronic communications, following protocols, and performing compliance testing. This chapter includes: Information on communicating with electronically Information on electronic interface testing for s The Community Choice Aggregation Interface Specifications, Communications Methods, and Protocol Specifications document which was modeled after the Retail Settlement Information Flow (RSIF) workshop on DA Communicating with intends to carry out the majority of communications and data exchanges to and from s using standard transaction formats within an EDI environment. After the mass enrollment process, s will be required to communicate customer switches to and from using EDI. Additionally, intends to communicate key transactions, such as updates to meter owner or unique customer identifier, billing, and payments, via EDI Establishing EDI with s interested in establishing EDI capability with should begin by contacting the Electronic Communications Coordinator (ECC). The ECC will function as the liaison between the and s Corporate Information Technology Group. Specifically, the ECC will assist s in understanding the requirements and protocols associated with establishing EDI communications with, assist as necessary in completing the Trading Partner Profile (TPP) agreement, and compile the necessary electronic transmission control information for EDI communications. The ECC can be contacted between the business hours of 7am 4pm (PST) at (626) intends to use standard EDI transactions developed and maintained by the Accredited Standards Committee X12 (ASC X12). This Committee and its standard transaction formats are sanctioned and approved by the American National Standards Institute (ANSI). ASC X12 transactions have been adopted for EDI by the Utility Industry Group (UIG), an industry action group working in the interest of electric and combination utilities, ESP s, end-use customers, and suppliers to improve the methods of exchanging business information through EDI. Specifically, intends to use UIG Southern California Edison Company Chapter 5, Page 1

3 Implementation Guidelines for the following ASC X12 transaction sets to communicate key data in the process: General Request, Response, or Confirmation Transaction Set, version/release After the initial mass enrollment process, s will be required to submit individual Community Choice Aggregation Service Requests (SRs) to enroll a customer in and/or return a customer to bundled service through EDI using Transaction Set 814 version The 814 will also be used by to acknowledge receipt of the SR, and to send SR confirmation or rejection notices to the. will use the UIG guideline for Transaction Set 814 version 4010 for all EDI SR requests and responses. s are also required to be capable of sending and receiving Update SR notifications to change the meter owner or the unique customer identifier. The UIG mapping guide may be found on the UIG web site at Prior to submitting a SR, all s will need to successfully meet certain compliance requirements for EDI Transaction Set 814 version Testing will include both inbound SRs and outbound messaging in a controlled testing environment. Compliance testing will test end-to-end processes between s and. s compliance testing timeframe for Transaction Set 814 will be established by IT at the time your request is received. Additional SR compliance testing information can be obtained from s ECC between the business hours of 7am 4pm (PST) at (626) In addition, has established EDI capability to conduct other key transactions. plans to use the following billing related transaction sets to conduct these: UDC Consolidated Billing 810 Invoice Transaction Set, version/release 3070 & 824 Application Advice Transaction Set, version/release It is expected that s will transmit inbound bill-ready data electronically to by utilizing Transaction Set 810 version A is required to use a Value-Added Network (VAN) and will need to establish a mailbox on a VAN of their choice. This VAN must be fully capable of storing and forwarding ASC X12 transactions. Information about a s VAN can be communicated through the EDI TPP agreement included in this handbook. currently uses nubridges as their VAN provider. will use the UIG guideline for Transaction Set 810 version 3070 for all inbound bill-ready data. The UIG mapping guide may be found on the UIG web site at Transaction Set 824 version 3070, will be sent by to the as a response to the inbound bill-ready data transmitted by the to via EDI Transaction Set 810. The 824 transaction indicates an Acceptance or Rejection, and the error code and Southern California Edison Company Chapter 5, Page 2

4 description of what field(s) of the account data is incorrect. The 824 mapping guide is the official UIG 824 guide, version 3070, and meets ANSI X12 standards, but is no longer posted for viewing or downloading on the UIG web site. will use the 824 Application Advice version 3070 for all outbound bill-ready data responses. The 824 Application Advice version 3070 mapping guide may be found at the following link: 1E512FA2084B/0/ESPHandbook824ApplicationAdvicev3070.pdf Prior to transmitting inbound bill-ready data and receiving outbound responses, all s will need to successfully meet certain compliance requirements for EDI Transaction Set 810 & 824 version Testing will include both inbound transmissions and outbound responses in a controlled testing environment. Although it is not required, s have the option of participating in practice testing prior to initiating compliance testing. Both practice testing and compliance testing will test end-to-end processes between s and. The following timeline has been established (in business days) with regards to EDI Transaction Set 810 & 824 version 3070 compliance testing. s compliance testing timeframe for Transaction Set 810 & 824 will be established by IT at the time your request is received. Additional compliance testing information can be obtained from s ECC between the business hours of 7am 4pm (PST) at (626) Payment Order/Remittance Advice Transaction Set, version/release At this time, it is expected that will use Transaction Set 820 version 3030 to communicate to the both remittance data to post payments to individual customer accounts and banking instructions to move the funds electronically. s will receive payments from either: a) via EFT/EDI (an electronic funds transfer with electronic data interchange remittance information) or b) via Paper/EDI (a check with electronic data interchange remittance information) depending on the s preference. A Value-Added Bank (VAB) will serve as the financial intermediary between s and. s are required to complete an EFT Agreement form (if selected) and also must have an EDI Trading Partner Agreement on file with. The 820 mapping guide is the official UIG 820 guide, version 3030, and meets ANSI X12 standards, but is no longer posted for viewing or downloading on the UIG web site. will use the 820 Payment Order/Remittance Advice version 3030 for all payments made and remittance advices sent. The 820 Payment Order/Remittance Advice version 3030 mapping guide may be found at the following link: Product Transfer and Resale Report Transaction Set, version/release Southern California Edison Company Chapter 5, Page 3

5 has implemented the use of Internet based EDI using Transaction Set 867 version 4010 to post routine monthly usage and historical usage data to the Meter Data Management Agent (MDMA) server for the to retrieve. To utilize EDI via the Internet, the must have EDI-INT compatible software. The 867 mapping guide is the official UIG 867 guide, version 4010, and meets ANSI X12 standards. will use the UIG guideline for Transaction Set 867 version 4010 for all monthly and historical usage data. The UIG mapping guide may be found on the UIG web site at: Meter Data Management Agent (MDMA) will act in all cases as the customer s MDMA. s will be required to download meter usage data from a designated server ( in order to calculate charges. s will be provided with a User ID and Password to logon to s MDMA server. Additional MDMA server information can be obtained from s ECC between the business hours of 7am 4pm (PST) at (626) Additional Information on Electronic Data Interchange As stated above, intends to utilize transaction set guidelines for EDI established by the UIG. These guidelines provide a standardized methodology to conduct business in an EDI environment. Consistent with UIG guidelines, uses Dun & Bradstreet (D&B) numbers as mailbox identifiers among the VANs to identify itself and its partners in the EDI exchange process. For more information about UIG guidelines, visit the UIG website at has developed mapping guides to assist s in conducting transactions through EDI. s should note that the guides define the format for various transactions; will not customize formats for individual trading partners. These mapping guides will be available by request from the ECC and through s website at Mapping guide information can be obtained from s ECC between the business hours of 7am 4pm (PST) by calling (626) Testing Electronic Communications 5.4.A. System Testing Establishing the information system infrastructure necessary to implement on schedule represents a significant challenge for both s and. 5.4.B. Establishment Testing As described above, has conducted system testing in order to ensure the functionality of s electronic infrastructure for. In addition to this system testing, provides testing procedures designed to assist Southern California Edison Company Chapter 5, Page 4

6 s in establishing electronic communications with for the first time. As a first step, a is required to submit certain background information described in the Fulfill Establishment Requirements step of the process. The ECC may contact a to ensure that all the required information was correctly submitted. s Interface Protocols As part of establishing and maintaining services, s will need to follow unique protocols as they communicate data through EDI. In order to assist s in following these protocols, has developed the Community Choice Aggregation System Interface Specification: Communication Methods and Protocol Specifications, a document that describes the data interfaces necessary to properly transfer information between and the. This guide breaks down key transactions into 14 key logical messages, and provides information on the interfacing entities, requirements on the type of interface, required characteristics of data element groupings, and other data. s Community Choice Aggregation Interface Specifications: Communication Methods and Protocol Specifications 5.A. Introduction 5.A.1. Introduction The Public Utilities Commission in Paragraph 7(c.) of its Second Interim Order for Direct Access in Decision D , required the Utility Distribution Companies to hold a Retail Settlement and Information Flow workshop. This workshop, held July 7, 1997, was responsible for informing the electrical industry stakeholders of the requirements needed for retail settlement and information flow. has used this as a model for informing s of the requirements necessary. In this document, will describe the data transfer protocol and system interfaces which will encompass all data transfers. 5.A.2. Purpose This document specifies the data interfaces needed to properly transfer information between and the. To properly establish the correct interface protocol between and s, has identified 14 key logical messages. The key messages will signify information flow from either (1) to the, (2) the to or (3) both ways. Later in this document, added clarification will be asserted for each of the 14 areas separately. Each area will be broken down into interfacing entities, requirements on the type of interface, required characteristics of data element groupings, required characteristics of communication methods that the interfacing entities must use for the interface, required characteristics of protocols the interfacing entities must use for the Southern California Edison Company Chapter 5, Page 5

7 interface, and other required characteristics that further clarify the / interface. 5.B. Referenced Documents 1. Retail Settlement and Information Flow Workshop Report. 2. Metering and Data Communications Standards (MDCS) Workshop Report, dated 7/16/ Customer Information Database Workshop Report. Southern California Edison Company Chapter 5, Page 6

8 5.C. Interface Context Diagrams Historic Customer Usage [D.1] SR [D.3] SR Acknowledgment [D.3] SR Confirmation [D.3] Former ESP Mass Enrollment Data File [D.2] Opt-Out Notifications [D.2] Confidential Customer Information [D.1] Non-Energy Billing [D.4] Non-Energy Billing Payment [D.4] Distribution Loss Factor [D.10] MADEN Request [D.11] MADEN Response [D.11] Account Maintenance Notifications [D.6] Bill (Ready) Data [D.7] Bill Data Acknowledgments & Confirmations [D.7] Payments/Adjustments/Return Receivables [D.8] Load Profiles [D.9] Meter Usage Data - Settlement Files [D.12] Support Help Desk [D.13] Compliance Testing [D.14] Monthly Meter Usage Data [D.5] Historic Customer Usage [D.1] MDMA SERVER* Monthly Meter Usage Data [D.5] Historic Customer Usage [D.1] *Depicts retrieval of information from Server 5.D. Interface Requirement Descriptions Southern California Edison Company Chapter 5, Page 7

9 1. Confidential Customer Information will provide information to s to enable them to investigate, pursue, or implement Community Choice Aggregation. This information will be provided subject to a nondisclosure agreement and an affidavit from the mayor or chief administrative officer of a city or county attesting that the city or county is investigating or pursuing status as a. Please refer to Chapter 4 for the requisite forms. Historical Customer Usage will provide 12 months of historical customer usage information for each customer that is enrolled in. This information will be posted electronically in EDI format to the MDMA server. Information released as a result of the Mass Customer Enrollment process, or an individual SR submission, will be posted by and must be retrieved by the. s acquiring a Direct Access customer should be aware that they are entitled to receive 12 months of historical consumption data from the existing ESP, not. 2. Mass Enrollment Data For customers who will be switching to, will provide a list of individual customer specific information to s. The mass enrollment data file will be sent to the and will contain each customer s name, address, and switch date among other things. Opt-Out Notifications will exclude customers from the mass enrollment who have opted-out. 3. Community Choice Aggregation Service Requests (SRs) The SR is the central processing record exchanged between the and for individual customer switches following mass enrollment. The SR will be sent electronically using an EDI format and will contain all of the information required to initiate a customer switch to and/or termination from. SR acknowledgments will respond to the within two (2) business days of successful and unsuccessful SR submissions. Unsuccessful SRs will be rejected and returned to the with information regarding any errors or omissions, and will need to be resubmitted in order to be reprocessed. SR processing confirmation This will be the process used by to notify s of the switch date for individual customer switches that occur outside of the mass enrollment process. will provide a SR confirmation notification to the within two (2) business days of an accepted SR. 4. Non Energy Bill will bill the on a monthly basis for all service fees will send a hard copy bill statement and a flat file containing a line by line detailed accounting of the charges to the via . Upon request, a hard-copy statement will be provided to the via U. S. Mail. Southern California Edison Company Chapter 5, Page 8

10 Non Energy Bill Payment s can pay their non-energy bill using traditional bill payment methods i.e., check sent by U.S. Mail along with a hard copy bill stub or through a variety of electronic methods. currently offers the following electronic payment options: - online via the Internet website using the Online Payment, - automatically through your bank account using Direct Payment 5. Meter Usage Data Monthly customer meter usage data will be posted by to the MDMA server on or about the end-use customer s scheduled meter read date. Information will be posted in an EDI format and must be retrieved from the server by the. 6. Account Maintenance When a or changes account specific information, e.g., name change, mailing address change, etc., notification should be given to the other party. will communicate these types of changes via Billing Data Exchange offers bill-ready consolidated billing to s. A shall retrieve the meter usage data from the MDMA server, calculate its own charges, taxes, or other fees, and submit its charges in bill-ready form via EDI to s van by 12 PM on the second business day following the service account s usage file posting on the MDMA server. Bill Data Acknowledgments and Confirmations will respond to the within one (1) business day of both successful and unsuccessful bill data submissions. Unsuccessful bill data transactions will be rejected and the will be notified of any errors or omissions. will provide the end-use Customer s Account Number in the confirmation notification. 8. Payment/Adjustments/Uncollectible Charges offers three methods for paying bills to s: online payment through direct pay (automatic debit to bank account monthly) and; check via U.S. Mail. When processing EDI/EFT transactions will send remittance data for each customer account and amount paid in an EDI format to a VAB and use EFT for transferring funds to the. also utilizes an EDI/check process. must be able to reconcile bills and make appropriate adjustments on a monthly basis. This can include but is not limited to incorrect reads, returning uncollected charges to the, processing returned checks, etc. 9. Load Profiles will assign and communicate load profile identifiers for service accounts without interval data recording meters to the. The is responsible for applying load profiles to their settlement data. 10. Distribution Loss Factors will communicate distribution loss factors to s through a daily posting to s website. The is responsible for applying distribution loss factors to their settlement data. Southern California Edison Company Chapter 5, Page 9

11 For additional information on the DLF data file format, please refer to the Distribution Loss Factors web page on s web site at Meter and Data Exception Notification (MADEN) Occasionally, is unable to retrieve usage data for a particular customer account due to access problems and/or other issues. will communicate these exceptions to a via Settlement Meter Usage Data s will send an with meter usage data settlement files submitted to the ISO for each trade day. 13. Support Desk Interactions has established a toll free hotline (800) and address SVCS@.com for s to pose operational questions such as providing the status of Community Choice Aggregation Service Requests. 14. Compliance Testing s must pass s compliance testing prior to sending their first set of production data. will provide test data for interface testing and s will provide evidence of successful testing. Southern California Edison Company Chapter 5, Page 10

12 5.D.1. Confidential Customer Information This interface allows the requesting and release of, confidential customer information subject to receipt of a nondisclosure agreement and an affidavit from the mayor or chief administrative officer of a city or county attesting that the city or county is investigating or pursuing status as a. Non-Disclosure Agreement Affidavit from Mayor/Chief Administrative Officer Confidential Customer Information 5.D.2. Mass Enrollment Opt-Out Requests Historic Customer Usage This interface describes the communication of customer requests to optout of, data and information necessary for the effective mass enrollment of customers in, and how the will receive 12 months of historic customer usage. Opt-Out Requests Access Server/ Retrieve Information MDMA Server Historic Customer Usage Mass Enrollment Data File Required Characteristics of Communication Methods for the Interface The historic usage data will be posted to the MDMA server in EDI format. posts 12 months of historic usage for the to retrieve. To utilize EDI transactions, the must have EDI-INT compatible software. Required Characteristics of Protocols for the Interface The method for the transmission must be EDI. The Transaction Set 867 version 4010 Product Transfer and Resale Report is appropriate. Other Required Characteristics for the Interface Transaction Set 867, and EDI Trading Partner Profile (TPP) Southern California Edison Company Chapter 5, Page 11

13 5.D.3. Community Choice Aggregation Service Request (SR) SR Acknowledgment SR Processing Confirmation This interface describes the SR (customer elections to and/or from ) process. It describes the data exchanges and messages necessary for the effective communication of customer information to complete the transition from one provider (,, or ESP) to another. Connect SR Disconnect SR SR Acknowledgements SR Acknowledgements Former ESP SR Processing Confirmation SR Processing Confirmation Historic Customer Usage Required Characteristics of Communication Methods for the Interface will receive EDI transmissions through a VAN for Transaction Set 814 version Required Characteristics of Protocols for the Interface will support the following protocols: EDI Transaction Set 814 version 4010 General Request, Response, or Confirmation. Other Required Characteristics for the Interface EDI Trading Partner Agreement EDI Trading Partner Profile(s) Southern California Edison Company Chapter 5, Page 12

14 5.D.4. Non Energy Billing and Payment This interface describes the billing and payment exchange between and the for CPUC-approved service fees. Non-Energy Bill for Fees Payment from for Services Rendered The following option will be used for bill presentation to the : 1) Bill Statement with attachment (spreadsheet of detailed charges). A number of methods for paying bills are available to the : 1) Online Payment (through 2) Direct Pay (Automatic Debit to Bank Account Monthly) 3) Check via US Mail Required Characteristics of Communication Methods for the Interface None Required Characteristics of Protocols for the Interface If EDI is used for payment, the protocol is the Transaction Set 820 version 3030 Remittance Advice. See Implementation Guide for current requirements. Other Required Characteristics for the Interface None Southern California Edison Company Chapter 5, Page 13

15 5.D.5. MDMA Usage/Meter Reads This interface describes the monthly meter usage exchange between and s MDMA server, as well as between the and s MDMA server. Access Server/ Retrieve Information MDMA Server Monthly Meter Usage Data Required Characteristics of Communication Methods for the Interface Internet based EDI. posts monthly usage data to the MDMA Server for the to retrieve. To utilize EDI via the Internet, the must have EDI-INT compatible software. Required Characteristics of Protocols for the Interface The method for the transmission is EDI Transaction Set 867 version 4010 Product Transfer and Resale Report. Other Required Characteristics for the Interface Transaction Set 867, EDI Trading Partner Profile. Southern California Edison Company Chapter 5, Page 14

16 5.D.6. Account Maintenance This interface provides messaging for the mutual exchange of data related to a specific customer s service account. Account Maintenance Message Required Characteristics of Communication This notification will be provided by using . s should notify s Services group of any account maintenance changes via or by phone. The address is SVCS@sce.com. This notification of Account Maintenance changes could include any, some, or all of the following: service account number; name; mailing address; phone number; fax number; address; rate change; meter access change; and any authorized persons added to an account. Required Characteristics of Protocols will support the following protocols: 1) Internet 2) EDI Transaction Set 814 version 4010 General Request, Response, or Confirmation. Other Required Characteristics If EDI, Trading Partner Agreement. Southern California Edison Company Chapter 5, Page 15

17 5.D.7, 8. Consolidated Billing & Customer Payment Data Interchange This interface provides the exchange of bill-ready data from the to for consolidation. Additionally, it reflects the interface of customer payments, adjustments, and/or uncollected receivables being returned from to the. Bill-Ready Data Customer Payment Data/EFT Adjustments Returned Receivables Consolidated Billing Data Interchange Information is exchanged via EDI, except for the returned receivable listings, which are sent via . Customer Payment Data Interchange Information is exchanged via EDI, money is transferred through Automated Clearinghouse/Electronic Funds Transfer (ACH/EFT). Required Characteristics of Communication Methods for the Interface Use of Value Added Network and Value Added Bank. Required Characteristics of Protocols for the Interface Transaction Set 810 version 4010 Invoice and transaction Set 820 version 3030 Remittance Advice. See Implementation Guide for current requirements. Other Required Characteristics for the Interface EDI Trading Partner Agreement, Electronic Funds Transfer Payments Agreement, 810 and 820 Trading Partner Profiles. Southern California Edison Company Chapter 5, Page 16

18 5.D.9. Load Profiles Each day a load profile for each of the identified rate classes will be available over the Internet on the website. Load Profile Information Internet Server Load Profile Information No. Data Element Name Type Size Notes Required/ Optional 1 Message Preamble Required 2 Load Profile ID CHAR 8 Rate class Required 3 Profile Date DATE MM/DD/YYYY Required 4 Hour 1 Value kwh DECIMAL Required 5 Hour 2 Value kwh DECIMAL Required 6 Hour 3 Value kwh DECIMAL Required 7 Hour 4 Value kwh DECIMAL Required 8 Hour 5 Value kwh DECIMAL Required 9 Hour 6 Value kwh DECIMAL Required 10 Hour 7 Value kwh DECIMAL Required 11 Hour 8 Value kwh DECIMAL Required 12 Hour 9 Value kwh DECIMAL Required 13 Hour 10 Value kwh DECIMAL Required 14 Hour 11 Value kwh DECIMAL Required 15 Hour 12 Value kwh DECIMAL Required 16 Hour 13 Value kwh DECIMAL Required 17 Hour 14 Value kwh DECIMAL Required 18 Hour 15 Value kwh DECIMAL Required 19 Hour 16 Value kwh DECIMAL Required 20 Hour 17 Value kwh DECIMAL Required 21 Hour 18 Value kwh DECIMAL Required 22 Hour 19 Value kwh DECIMAL Required 23 Hour 20 Value kwh DECIMAL Required 24 Hour 21 Value kwh DECIMAL Required 25 Hour 22 Value kwh DECIMAL Required 26 Hour 23 Value kwh DECIMAL Required 27 Hour 24 Value kwh DECIMAL Required Required Characteristics of Communication Methods for the Interface Internet Access. Southern California Edison Company Chapter 5, Page 17

19 5.D.10. Distribution Loss Factors Each day a distribution loss factor will be available on the Internet at the website. Distribution Loss Factors Internet Server Distribution Loss Factor No. Data Element Name Type Size Notes Required/ Optional 1 Message Preamble Required 2 UDC ID CHAR 4 Required 3 UDC DUNS INTEGER 9 Required 4 Loss Factor Date DATE 8 YYYYMMDD Required date of actual or subject date of estimated 5 Record Type CHAR 1 A = actual Required F = forecast 6 Hour INTEGER Required 7 Subtransmission DLF DECIMAL Required percentage with 5.34% shown as Primary Voltage DLF DECIMAL Required percentage with 5.34% shown as Secondary Voltage DLF DECIMAL Required percentage with 5.34% shown as Distribution Loss Designator INTEGER 5 Required Required Characteristics of Communication Methods for the Interface Internet Access. Required Characteristics of Protocols for the Interface None. Other Required Characteristics for the Interface None. Southern California Edison Company Chapter 5, Page 18

20 5.D.11. Meter and Data Exception Notification (MADEN) This interface provides the with notification of a potential or actual problem obtaining a meter read, with a metering device, or issue related to a metering device. Meter and Data Exception Noitfication Internet Server Meter and Data Exception Notification (MADEN) This information will be exchanged via . Required Characteristics of Communication Methods for the Interface Internet/ . Required Characteristics of Protocols for the Interface None. Other Required Characteristics for the Interface None. Southern California Edison Company Chapter 5, Page 19

21 5.D.12. Settlement Meter Usage Data The s will provide with meter usage data settlement files that are to be submitted to the ISO for each trade day. Settlement Data Settlement Data This information will be exchanged an secure MFT server when/if necessary. Required Characteristics of Communication Methods for the Interface Internet Required Characteristics of Protocols for the Interface None. Other Required Characteristics for the Interface None. Southern California Edison Company Chapter 5, Page 20

22 5.D.13. Support Desk Interactions This interface is a Customer Service function with a different set of interactions specific to a relationship. Inquiry or Service Request Responses Required Characteristics of Communication Methods for the Interface Phone, . Required Characteristics of Protocols for the Interface Internet/ . Other Required Characteristics for the Interface None. Southern California Edison Company Chapter 5, Page 21

23 5.D.14. Compliance Testing Compliance testing is required before a can implement within the service territory. will provide a test plan, test procedures, and sample test data. Required Characteristics of Communication Methods for the Interface EDI. Required Characteristics of Protocols for the Interface Mentioned in other sections. Other Required Characteristics for the Interface None. Notes proposes a standard Entity ID. This would be a standard four (4) character ID much like the standard ticker symbols, airline codes, airport codes, etc. will assign a Ticker symbol for every. Southern California Edison Company Chapter 5, Page 22