ࡱ> VWSTUܥhc e]-$JJJJJ$nJA{p+TEX}/V%u=g$2eUtility Industry GroupImplementationGuidelineforElectronicDataInterchangeTRANSACTION SET814General Request, Response or ConfirmationVer/Rel 004010 Summary of ChangesNovember 13, 1998Initial release.The differences between this Ver/Rel 004010 and Ver/Rel 003070 are as follows: Pos. Ref DesData Element NameAttributes 3070Attributes 4010H020BGN03373DateM DT 6/6M DT 8/8H040N10467Identification CodeX AN 2/20X AN 2/80H130ITD06446Terms Net Due DateO DT 6/6O DT 8/8D0401250Date Time Period Format QualifierDTM06 in 3070DTM05 in 4010Note: Ver 3070 provided qualifiers D6, D8, RD6, and RD8 in DTM06. Ver 4010 provides D8 and RD8 only in DTM05.D0401251Date Time PeriodDTM07 in 3070DTM06 in 4010D060AMT01522Amount Qualifier CodeM ID 1/2M ID 1/3D060AMT02782Monetary AmountM R 1/15M R 1/18D080NM10967Identification CodeA N 2/20A N 2/80In addition to the above changes, this version reflects numerous revisions reflecting the move from a "one-to-many" convention; i.e., one transaction covering many accounts, to a "one-to-one" convention; i.e., one transaction covers only one account. symbol 227 \f "Symbol" \s 10 Utility Industry Group, 1998 All Rights Reserved 814 General Request, Response or ConfirmationIntroductionThe function of the Utility Industry Group is To represent Electric, Gas, and Combination Utilities, their suppliers, their customers, and other interested parties as an Industry Action Group to the American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12, specifically in the standards-setting process, for their Electronic Data Interchange business needs. To encourage, promote, and establish conventions for the use of ASC X12 standards as the recommended method of EDI. To develop and coordinate, as required, implementation guidelines and tools to promote the growth and timely implementation of Electronic Commerce/EDI within the industry. To provide a forum for the exchange of ideas related to Electronic Commerce/EDI and its influence on the business needs of the industry. The UIG will represent the Edison Electric Institute (EEI) and its members to facilitate implementation of Electronic Commerce/EDI in the Utility Industry.PurposeThis Utility Industry Group (UIG) Implementation Guideline contains the format and establishes the data contents of the General Request, Response or Confirmation Transaction Set (814) as adopted by the UIG for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to request actions to be performed, to respond to a request for actions to be performed, or to confirm information related to actions performed for or on behalf of Customers.NotesThis Implementation Guideline was designed to address the business processes that support the supply of products or services by a third party, such as bill presentment or payment services, warranty services, or alternative energy supply. The primary processes addressed by this Transaction Set 814 are the customer request for enrollment with a third party supplier, the maintenance of customer account information, and the disenrollment from the third party supplier. The principal parties involved in this Transaction Set 814 implementation are: The end-use customer (Code 8R) The entity which provides services to the customer on behalf of another entity (Code 8S) The entity which has the primary business relationship with the customer (Code SJ) When this transaction set is used in an alternative energy supply environment, Code 8S identifies the local distribution utility (LDC or UDC) and Code SJ identifies the alternative energy service provider (ESP). 814 General Request, Response or ConfirmationBest PracticesGlobal Best PracticesUse of Text Segments The UIG recommends that the note (NTE) segment be avoided because this segment is not machine-readable. Other text segments, such as MSG and PID, may be used if their use will lead to machine processable information in subsequent applications.Use of ZZ Qualifier The use of data fields to transmit uncoded or textual information should be avoided. This practice is usually associated with the use of the ZZ qualifier as a normal course of doing business.997 - Functional Acknowledgment The purpose of the 997 is to verify receipt of a transmitted document only, not the acceptance of the document. For example, the acceptance of a purchase order (850) is accomplished through the use of the purchase order acknowledgment transaction (855).Interchange Control Number A unique and sequential interchange control number should be used on every envelope that is transmitted to a trading partner. This approach will allow the receiver to audit the interchange for any duplicate or missing transmissions.Use of Dun & Bradstreet (D-U-N-S) Number Dun & Bradstreet assigns a nine-digit identification number to every business entity. This number, known as the D-U-N-S number, should be used to identify the trading partners. A trading partner may append a four-digit suffix to the DUNS number to uniquely identify a specific location within the entity; this number is referred to as a D-U-N-S + 4 numberBanking Transactions Guidelines that outline the use of transactions relating to interactions between a sender and the sender's financial institution are available from the Bankers EDI Council and the NACHA EDI Council. Other publications that address the use of financial payment transactions include Technical Report 1 (TR1) and Technical Report 2 (TR2); both of these publications are available from DISA.Capitalization The use of all upper case (capital) letters is preferred over the use of mixed upper and lower case letters. Document-Specific Best PracticesUse of the N1 LoopIf any one entity performs more than one of the business functions provided in the N1, the loop should be repeated as necessary to identify that entity as the provider of those functions.Use of the LIN SegmentThe UIG recommends that one 814 be limited to one service account for a single commodity (electric or gas). This single service account may have more than one meter associated with it, in which case a separate LIN loop should be used for each meter. The LIN loop contains data relative to a service associated with the service account; e.g., enrollment with an ESP, sign-up for budget billing, sign-up for direct debit, etc. When Responding to a Request transaction, the best practice is to identify the LIN segments (LIN01) with the same identification sent in the Request LIN01.Use of the Detail LIN/REF Segment Three conventions for the Detail LIN/REF segment (position 030) are provided in this implementation guideline: One to convey status reason codes in response to a Request One to convey change reason codes in a Request for account maintenance One to convey account level reference information To allow for multiple rejection reasons when a Request is rejected, the UIG convention is to transmit the status reasons in the LIN/REF segment (position 030) rather than in the ASI03 element, even if there is only one rejection reason. The codes used in REF02 will be those specified for ASI03; i.e. codes from data element 641. The codes used in REF02 when the segment is used for account maintenance are maintained by the UIG. The first portion of the code identifies the segment that contains the data that has been changed; the remaining portion of the code identifies the relevant code qualifier for the data that has been changed. The changed data will appear in the appropriate element of the identified segment. For example, a REF02 code of AMT7N indicates that data in the AMT segment that is identified by the qualifier 7N (i.e., Percentage of Service Supplied) has been changed to the value now shown in AMT02. Definitions for Data Elements 128 (REF01), 306 (ASI01), and 875 (ASI02) To accommodate the identification requirements necessitated by the restructuring of the electric utility industry, the UIG has developed its own definitions for the qualifiers and codes found in data elements 128, 306, and 875.Position 130, account level acceptance or rejection of the request. It is a recommended practice to always keep the acceptance or the rejection of the request at the account level. The codes in the REF 03 are for that purpose. The codes at REF 130 are there for the sender to provide additional information about the error. To send information about the error at the meter level is optional. To reject at the meter level can lead to splitting accounts.   814 General Request, Response or Confirmation Functional Group ID=GE HeadingPos.Seg.Req.LoopNotes andNo.IDNameDes.Max. UseRepeatCommentsMust Use010STTransaction Set HeaderM1Must Use020BGNBeginning SegmentM1LOOP ID - N1>1Recomm040N1NameO1n1050N2Additional Name InformationO2060N3Address InformationO2070N4Geographic LocationO1080PERAdministrative Communications ContactO>1 DetailPos.Seg.Req.LoopNotes andNo.IDNameDes.Max. UseRepeatCommentsLOOP ID - LIN>1Must Use010LINItem IdentificationO1Must Use020ASIAction or Status IndicatorO1030REFReference IdentificationO>1Recomm040DTMDate/Time ReferenceO>1060AMTMonetary AmountO>1070PMElectronic Funds Transfer InformationO1LOOP ID - NM1>1Must Use080NM1Individual or Organizational NameO1n2090N2Additional Name InformationO2100N3Address InformationO2110N4Geographic LocationO1120PERAdministrative Communications ContactO>1130REFReference IdentificationO>1 SummaryPos.Seg.Req.LoopNotes andNo.IDNameDes.Max. UseRepeatCommentsMust Use150SETransaction Set TrailerM1 Transaction Set Notes: The N1 loop is used to identify the transaction sender and receiver. The NM1 loop is used to identify the parties associated with the individual line item (LIN), such as an individual customer in a consolidated third party Consumer Service Provider transaction. Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading: Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UseST01143Transaction Set Identifier CodeMID 3/3Code uniquely identifying a Transaction Set814General Request, Response or Confirmation Must UseST02329Transaction Set Control NumberMAN 4/9Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Segment: BGN Beginning Segment Position: 020 Loop: Level: Heading: Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of a transaction set Syntax Notes: 1 If BGN05 is present, then BGN04 is required. Semantic Notes: 1 BGN02 is the transaction set reference number. 2 BGN03 is the transaction set date. 3 BGN04 is the transaction set time. 4 BGN05 is the transaction set time qualifier. 5 BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction. Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UseBGN01353Transaction Set Purpose CodeMID 2/2Code identifying purpose of transaction set06ConfirmationConfirms receipt of the Request; action on the requested service is pending.11ResponseSignifies that the requested service will be addressed as described in this transaction.13Request14Advance NotificationCNCompletion NotificationSignifies that the requested service was completed as described in this transaction, not as identified in the original Response.Must UseBGN02127Reference IdentificationMAN 1/30Reference information as defined for a particular Transaction Set or as specified by the Reference Identification QualifierA unique transaction identification number assigned by the originator of this transaction.Must UseBGN03373DateMDT 8/8Date (CCYYMMDD)The transaction creation date.BGN04337TimeXTM 4/8Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)The transaction creation time. BGN05623Time CodeOID 2/2Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that followIdentifies the time zone applicable to the BGN04 valueATAlaska TimeCTCentral TimeETEastern TimeGMGreenwich Mean TimeHTHawaii-Aleutian TimeMTMountain TimePTPacific TimeUTUniversal Time CoordinateBGN06127Reference IdentificationOAN 1/30Reference information as defined for a particular Transaction Set or as specified by the Reference Identification QualifierIf used, refers to the BGN02 identification number of the original Request. Segment: N1 Name Position: 040 Loop: N1 Level: Heading: Usage: Recommended Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. Data Element Summary Ref. Data Des. Element Name Attributes Must UseN10198Entity Identifier CodeMID 2/3Code identifying an organizational entity, a physical location, property or an individual28SubcontractorUsed to identify the party that installs the meter.2CCo-ParticipantUsed to identify a third party who shares responsibility for payment of the customer's bill.48In-service SourceUsed to identify the party that reads the meter.55Service ManagerUsed to identify the party that manages meter data on behalf of another. Often referred to as the Meter Data Management Agent (MDMA).85Billing ProviderUsed to identify the party that will present the bill to the end use customer8RConsumer Service Provider (CSP) CustomerUsed to identify the customer associated with the service account identified in the NM1/REF segment. 8SConsumer Service Provider (CSP)Used to identify the entity that provides services to the end use customer on behalf of another. In the deregulated, alternative energy supply environment, this is the Utility 90Previous Business PartnerUsed to identify the former/departing ESP.AOAccount OfUsed to identify the former name or service address for the current end use customer. Used when the customer name or written service address has changed. Code 8R is used to qualify the new, replacement name or address.  BFBilled FromUsed to identify the party that will calculate the bill.BTBill-to-PartyUsed to identify a billing address for the customer associated with the service account identified in the NM1/REF segment.BYBuying Party (Purchaser)Used to identify a centralized management or accounts payable location responsible for the location identified by code 8R.FEMail AddressForwarding mailing address, typically used to notify another party when a customer moves.H8Servicing AgentUsed to identify the party that services and maintains the meter. Often referred to as the Meter Service Provider (MSP).OKOwnerUsed to identify the party that owns the meter.PKParty to Receive CopyUsed to identify a third party that is to receive a copy of all notices to the end use customer.RSReceiving Facility SchedulerUsed to identify the scheduling coordinator.SJService ProviderUsed to identify the entity that has the primary business relationship with the end use customer and which would otherwise be responsible for the service now being provided by the consumer service provider (Code 8S). In the deregulated, alternative energy supply environment, this is the Energy Service Provider.N10293NameXAN 1/60Free-form nameN10366Identification Code QualifierXID 1/2Code designating the system/method of code structure used for Identification Code (67)1D-U-N-S Number, Dun & Bradstreet9D-U-N-S+4, D-U-N-S Number with Four Character Suffix24Employer's Identification Number91Assigned by Seller or Seller's AgentAn identifier assigned by the Consumer Service Provider, N101=8S92Assigned by Buyer or Buyer's AgentAn identifier assigned by the Service Provider, N101=SJ or the customer, N101=8RSLStandard LicenseState registration number for Service Provider used only if the N101 = SJ.N10467Identification CodeXAN 2/80Code identifying a party or other code N10698Entity Identifier CodeOID 2/3Code identifying an organizational entity, a physical location, property or an individual.Used in addition to the N103 and N104 to identify the transaction sender and receiver when more than two parties are identified by N1 loops.40ReceiverEntity to accept transmission41SubmitterEntity transmitting transaction set Segment: N2 Additional Name Information Position: 050 Loop: N1 Level: Heading: Usage: Optional Max Use: 2 Purpose: To specify additional names or those longer than 60 characters in length Syntax Notes: Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UseN20193NameMAN 1/60Free-form nameN20293NameOAN 1/60Free-form name Segment: N3 Address Information Position: 060 Loop: N1 Level: Heading: Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UseN301166Address InformationMAN 1/55Address informationN302166Address InformationOAN 1/55Address information Segment: N4 Geographic Location Position: 070 Loop: N1 Level: Heading: Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 N402 is required only if city name (N401) is in the U.S. or Canada. Data Element Summary Ref. Data Des. Element Name Attributes N40119City NameOAN 2/30Free-form text for city nameN402156State or Province CodeOID 2/2Code (Standard State/Province) as defined by appropriate government agencyN403116Postal CodeOID 3/15Code defining international postal zone code excluding punctuation and blanks (zip code for United States)N40426Country CodeOID 2/3Code identifying the countryN405309Location QualifierXID 1/2Code identifying type of locationCOCounty/Parish and StateN406310Location IdentifierOAN 1/30Code which identifies a specific location Segment: PER Administrative Communications Contact Position: 080 Loop: N1 Level: Heading: Usage: Optional Max Use: >1 Purpose: To identify a person or office to which administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. 3 If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UsePER01366Contact Function CodeMID 2/2Code identifying the major duty or responsibility of the person or group namedICInformation ContactPER0293NameOAN 1/60Free-form namePER03365Communication Number QualifierXID 2/2Code identifying the type of communication numberEMElectronic MailFXFacsimileTETelephonePER04364Communication NumberXAN 1/80Complete communications number including country or area code when applicablePER05365Communication Number QualifierXID 2/2Code identifying the type of communication numberEMElectronic MailFXFacsimileTETelephonePER06364Communication NumberXAN 1/80Complete communications number including country or area code when applicablePER07365Communication Number QualifierXID 2/2Code identifying the type of communication numberEMElectronic MailFXFacsimileTETelephonePER08364Communication NumberXAN 1/80Complete communications number including country or area code when applicable Segment: LIN Item Identification Position: 010 Loop: LIN Level: Detail: Usage: Must Use Max Use: 1 Purpose: To specify basic item identification data Syntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required. Semantic Notes: 1 LIN01 is the line item identification Comments: Notes:A separate LIN loop is used for each meter, i.e., one LIN per meter, one meter per LIN. When responding to a Request, the best practice is to identify the LIN segment (LIN01) with the same identification sent in the Request LIN01. Note: The 3070 version of the 814 guideline allowed all services to be transmitted in one LIN segment. Finding that this was difficult, if not impossible, to manage, we recommend the use of LIN03 to identify the primary service and LIN05 to identify what is to be done to the primary service. For example, LIN*SH*EL*SH*CE\ indicates that the primary service is 'electric service' and 'customer enrollment' is the action to be done. Other examples: LIN*SH*EL*SH*HU\ requests historical usage of electric service LIN*SH*GAS*SH*MI\ requests meter information on the gas service Data Element Summary Ref. Data Des. Element Name Attributes Must UseLIN01350Assigned IdentificationOAN 1/20Alphanumeric characters assigned for differentiation within a transaction setA unique sequential number for each line item within this transaction set.Must UseLIN02235Product/Service ID QualifierMID 2/2Code identifying the type/source of the descriptive number used in Product/Service ID (234)SHService RequestedSVService RenderedMust UseLIN03234Product/Service IDMAN 1/48Identifying number for a product or serviceELElectric ServiceIndicates a customer request to obtain electric service.FOFuel Oil ServiceIndicates a customer request to obtain fuel oil service.GASGas ServiceIndicates a customer request to obtain gas service.LPLiquid Propane ServiceIndicates a customer request to obtain liquid propane gas service.STSteam ServiceIndicates a customer request to obtain steam service. SWSewage ServiceIndicates a customer request to obtain sewage service.WAWater ServiceIndicates a customer request to obtain water service.Must UseLIN04235Product/Service ID QualifierMID 2/2Code identifying the type/source of the descriptive number used in Product/Service ID (234)SHService RequestedSVService RenderedMust UseLIN05234Product/Service IDMAN 1/48Identifying number for a product or serviceAWAppliance WarrantyIndicates a customer request for warranty repair services.BBBudget BillingIndicates a customer request for a levelized billing arrangement.CECustomer EnrollmentECElectronic CreditIndicates a customer request to receive any credit due via electronic credit.EDElectronic DebitIndicates a customer request to make payment via electronic debit.EIElectronic InvoicingIndicates a customer request to be billed electronically.HUHistorical UsageIndicates an ESP request to obtain historical usage information for this customer. This information would be returned on an EDI 867.MIMeter InformationIndicates an ESP request to obtain detailed information about the existing meter. This information would be returned on an EDI 650. MRMeter ReadingIndicates a customer request to obtain meter reading services.MTMeter TestIndicates a request for the meter to be tested.MURMeter Usage ResendIndicates a request to have meter usage data resent for the specified account and meter.MUVMeter Usage ValidationIndicates a request to have meter usage data validated for the specified account and meter.RRCRetroactive Rate ChangeIndicates a customer request for a new rate to be effective retroactive to a previous billing cycle. SRSpecial Meter ReadIndicates an ESP request to obtain a special, off-cycle meter read for this customer. If the meter agent cannot provide this service, they should indicate that on the response transaction by populating REF*7G with status reason code W09.VLVolunteerIndicates a customer request to volunteer for a pilot or phase-in of deregulation. Segment: ASI Action or Status Indicator Position: 020 Loop: LIN Level: Detail: Usage: Must Use Max Use: 1 Purpose: To indicate the action to be taken with the information provided or the status of the entity described Syntax Notes: Semantic Notes: Comments: Notes:Identifies the action to be taken or the status of a requested action for the service identified in the LIN segment. Status Reason Codes are conveyed in the REF segment (position 030) rather than in the ASI03, to allow for multiple status reasons. It is a recommended practice to provide the action or status at the account level only with the option, if taken, to provide information about any errors at the meter level for accounts related to multiple meters. Data Element Summary Ref. Data Des. Element Name Attributes Must UseASI01306Action CodeMID 1/2Code indicating type of action6Receive7Request27Moved - Follow UpUsed to designate a seamless transfer of ESP when a customer moves within a Utility's service territory.A4PendedIn ProcessCCancelledFFinalTDTemporarily DenyURejectVRespondWQAcceptMust UseASI02875Maintenance Type CodeMID 3/3Code identifying the specific type of item maintenance001Change002Delete021AdditionUse when requesting or confirming a new service.022Change in Status024Cancellation or Termination025ReinstatementTo place in force again, without the usual probationary or service period.029Inquiry051Denial066Status Request101Servicer Change Segment: REF Reference Identification Position: 030 Loop: LIN Level: Detail: Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes:This convention of the REF segment is used for account level information. Data Element Summary Ref. Data Des. Element Name Attributes Must UseREF01128Reference Identification QualifierMID 2/3Code qualifying the Reference Identification06System NumberWhen a utility uses logical account numbers (those that change when a meter route is changed, etc.), the utility can assign a System Number as a permanent key for the account. The customer account number may be used for the initial Request transaction (enrollment), but the System Number will be passed to the Service Provider during confirmation and will be used for all future transactions.0BState License NumberEnergy Service Provider License or Registration number11Account NumberNon-utility trading partner assigned account number for the end use customer. In the deregulated, alternative energy supply environment, this is the Energy Service Provider-assigned account number for the end use customer. If an ESP account number is changed, this is the new ESP account number; the old ESP account number is qualified by WF12Billing AccountUtility-assigned account number for end use customer.45Old Account NumberUtilitys previous account number for the end use customer.5BSupplemental Account NumberEnergy Service Provider-assigned account number for the utility.65Total Order Cycle NumberMeter Owners Meter Reading Cycle Number7FRepeat LocationNew customer indicator. See REF02 for valid values. 9VPayment CategoryPayment OptionAJAccounts Receivable Customer AccountUtility-assigned account number for the Energy Service ProviderBFBilling Center IdentificationBilling cycle. Cycle number when the billing will be rendered.BLTBilling TypeIdentifies whether the bill is consolidated by the LDC or ESP, or whether each party will render their own bill. See REF02 for valid values.GKThird Party Reference NumberFormer/departing ESPs account number for the end use customer.H5Special ClauseRenewable Energy Provider. Indicates that renewable energy is provided for this account. See REF02 for valid values.K0Approval CodeCustomer has acknowledged responsibility for paying competitive transition charges (stranded costs). See REF02 for valid values.KWCertificationCertification Number for renewable energyNRProgress Payment NumberUsed to convey budget billing status. See REF02 for valid values.O8Original FilingUsed to indicate whether this account is a new premise within the utility's service territory. See REF02 for valid values.PCProduction CodeIdentifies the party that is to calculate the charges on the bill. See REF02 for valid values.PGProduct GroupIdentifies a public or private group that aggregates customers and contracts load on their behalf.S0Special ApprovalIndicates the extent to which the customer has authorized the release of confidential information. See REF02 for valid values.SRSales ResponsibilityService relationshipSTStore NumberAn internal reference number meaningful to the customerTNTransaction Reference NumberUsed to provide a unique identification number for the Request for this Customer. U0Consolidator's Receipt NumberEnergy Service Provider transaction number WFLocally Assigned Control NumberESPs previous account number for the end use customer.REF02127Reference IdentificationXAN 1/30Reference information as defined for a particular Transaction Set or as specified by the Reference Identification QualifierWhen REF01 is 7F, valid values for REF02 are: Y - New customer at this service address N - Existing customer at this service addressWhen REF01 is BLT, valid values for REF02 are: LDC - The Utility bills the customer ESP - The ESP bills the customer DUAL - Each party bills the customerWhen REF01 is H5, valid values for REF02 are: Y - Renewable energy is provided N - Renewable energy is not providedWhen REF01 is K0, valid values for REF02 are: Y - Acknowledgment Received N - Acknowledgment Not ReceivedWhen REF01 is NR, valid values for REF02 are: Y - This customer is on budget billing N - This customer is not on budget billingWhen REF01 is O8, valid values for REF02 are: Y - This is a new premise N - This is not a new premiseWhen REF01 is PC, valid values for REF02 are: LDC - The Utility calculates the charges on the bill ESP - The ESP calculates the charges on the bill DUAL - Each party calculates its portion of the billWhen REF01 is S0, valid values for REF02 are: 00 - Customer has released no information 01 - Customer has released Name and Address 02 - Customer has released Name, Address and Telephone Number 03 - Customer has released Name, Address and Usage 04 - Customer has released Name, Address, Telephone Number and Usage REF03352DescriptionXAN 1/80A free-form description to clarify the related data elements and their contentUsed to further describe the status reason code sent in REF02. Segment: REF Reference Identification Position: 030 Loop: LIN Level: Detail: Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes:This convention of the REF segment is used primarily to convey status reason codes in response to a Request. The status reason codes are conveyed in this segment rather than in the ASI03 to allow for multiple status reasons. Data Element Summary Ref. Data Des. Element Name Attributes Must UseREF01128Reference Identification QualifierMID 2/3Code qualifying the Reference Identification1PAccessorial Status CodeWarnings associated with an accept status notification.7GData Quality Reject ReasonReject reasons associated with a reject status notification.NUPending CasePending reasons associated with a pending status notification.REF02127Reference IdentificationXAN 1/30Reference information as defined for a particular Transaction Set or as specified by the Reference Identification QualifierThe following codes have been identified by the UIG to convey status reason codes. Other codes may be used by agreement of the trading partners when necessary.007Service terminated because of nonpayment 008Account exists but is not active 017Service terminated because the Service Provider went out of business 020Customer moved 023Cannot access the meter 027Payment DisputeA03Invalid meter address A13OtherSee explanation in REF03A75Invalid Account FormatA76Account Not FoundA77Name Specified Does Not Match AccountA78Item or Service Already Established, Cannot AddUse when a Request ASI02 was 021, AddA79Item or Service Not Established, Cannot ModifyUse when a Request ASI02 was 001, ChangeA80Item or Service Not AvailableA81Item or Service Not Available on Requested DateA82Address Specified Does Not Match AccountA83Unauthorized or Invalid ActionA84Invalid RelationshipA91Service is not offered at Customer's location A95Offer expired ABNDuplicate request received ANEAccount Not EligibleANLService Provider not licensed to provide the requested service ANVAccount Not VolunteeredAPIApplication IncompleteRequired information missing. See REF03 for details.APVAccount Previously VolunteeredB04Requested service will not be completed until outstanding payment is made B14Reason for termination is required but was not furnished B30Currently EnrolledB31Not Currently EnrolledB33Customer name is missing from the Request B38DroppedCustomer was terminated by the Service Provider for reasons other than nonpaymentB39Already DroppedBBABudget Billing AppliedBBRBudget Billing RejectedC02Customer is on credit holdCCECustomer Contract ExpiredCHACustomer changed to another Service Provider COPConclusion of Pilot ProgramD30Requested service has been declinedD50Effective date of service has been changed DIVDate InvalidEB3WithdrawnCustomer rescinded enrollment requestEBARequested incentive not found or not in effect on the requested date FRBFailed to Release BillingIncorrect billing option requestedHURHistorical Usage Not ReleasedHUUHistorical Usage UnavailableMIUMeter Information UnavailableNFINot First InNLINot Last InNMINo Meter Installed P01Processing DelayRequest received, processing will be delayedPALRequest accepted pending licensing of Service Provider SNPService Not ProvidedTHTTheftService terminated because of customer's diversion of serviceUMAUnmetered AccountUNDCannot identify Service Provider UNECannot identify LDCW05Requested rate not found or not in effect on the requested date W09Special, off-cycle meter reading cannot be performed. Meter will be read on the normal, on-cycle read date REF03352DescriptionXAN 1/80A free-form description to clarify the related data elements and their contentUsed to further describe the status reason code sent in REF02. Segment: REF Reference Identification Position: 030 Loop: LIN Level: Detail: Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes:This convention of the REF segment is used for account maintenance, to convey change reason codes. The codes used in REF02 are maintained by the UIG. The first portion of the code identifies the segment that contains the data that has been changed; the remaining portion of the code identifies the relevant code qualifier for the data that has been changed. The changed data will appear in the appropriate element of the identified segment. For example, a REF02 code of AMT7N indicates that data in the AMT segment that is identified by the qualifier 7N (i.e., Percentage of Service Supplied) has been changed to the value now shown in AMT02. Data Element Summary Ref. Data Des. Element Name Attributes Must UseREF01128Reference Identification QualifierMID 2/3Code qualifying the Reference IdentificationTDReason for ChangeREF02127Reference IdentificationXAN 1/30Reference information as defined for a particular Transaction Set or as specified by the Reference Identification QualifierAMT7NChange Percentage of Service SuppliedAMTDPChange Percentage of Service Tax ExemptAMTKCChange Capacity ObligationAMTKYChange Transmission ObligationAMTQYChange Eligible Load PercentageDTM007Change Effective DateDTM129Change Customer Contract Effective DateDTM150Change Service Period Start DateDTM151Change Service Period End DateDTM243Change Actual Complete DateDTM245Change Estimated Completion DateDTM802Change Date of ActionNM128Change Meter InstallerNM12CChange Third Party Name/AddressNM148Change Meter Reading PartyNM155Change Meter Data Management AgencyNM185Change Billing PartyNM18RChange Name or Service AddressNM1BFChange party that calculates the charges on the billNM1BTChange Bill-to Party Name/AddressNM1BYChange Centralized Management or Accounts Payable Name/AddressNM1FEChange Mailing AddressNM1H8Change party that services and maintains the meter.NM1OKChange Meter OwnerNM1PKChange Party to Receive Copy Name/AddressNM1RSChange Scheduling CoordinatorNM1SJChange Energy Service ProviderPERALChange Alternate Contact InformationPERICChange Information Contact InformationPM01Change DFI Identification NumberPM02Change Account NumberPM05Change Account Number QualifierPM06Change DFI Identification Number QualifierREF06Change System Number (Permanent Key Account Number)REF0BChange ESP's License or Registration NumberREF11Change Non-utility Trading Partner-assigned Account Number for the End Use CustomerREF12Change Utility-assigned Account Number for the End Use CustomerREF5BChange ESP-assigned Account Number for UtilityREF65Change Meter Owner's Meter Read CycleREF9VChange Payment OptionREFAJChange Utility-assigned account number for the ESPREFBFChange Billing CycleREFBLTChange Billing TypeREFD8Change Distribution Loss DesignatorREFH5Change Renewable Energy ProviderREFK0Change Approval CodeREFKWChange Certification NumberREFNRChange Budget Billing StatusREFO8Change New Premise IndicatorREFPCChange Party that Calculates the BillREFS0Change Release of Confidential Information IndicatorREFSPLChange Point at which the Customer is Connected to Transmission GridREFSRChange Service RelationshipREFSTChange Customer Reference NumberREFU0Change ESP Transaction NumberREFZWChange Congestion ZoneREF03352DescriptionXAN 1/80A free-form description to clarify the related data elements and their content Segment: DTM Date/Time Reference Position: 040 Loop: LIN Level: Detail: Usage: Recommended Max Use: >1 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM06 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM06 or DTM07 is present, then the other is required. Semantic Notes: Comments: Notes:To specify a time zone (DTM04), both DTM03 and DTM04 must be present. Therefore, if specification of a time zone is necessary, DTM06 should include only the date, not the time. Data Element Summary Ref. Data Des. Element Name Attributes Must UseDTM01374Date/Time QualifierMID 3/3Code specifying type of date or time, or both date and time007EffectiveDate upon which an addition, change, or deletion is requested to become effective (BGN01=13) or will become effective (BGN01=11).129Customer Contract EffectiveThe date/time the customer agreed to obtain service from the Service Provider.150Service Period StartDate that the service with the Service Provider will start.151Service Period EndDate that the service with the Service Provider will end.215Interruption StartDate of temporary shut-off.216Interruption EndDate of restoration from temporary shut-off.243Actual CompleteDate upon which the requested service was actually completed (BGN01 = CN).245Estimated CompletionDate upon which it is estimated that the requested service will be completed (BGN01=11).802Date of ActionDate of the request or acceptance.MRRMeter ReadingDTM03337TimeXTM 4/8Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) DTM04623Time CodeOID 2/2Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that followATAlaska TimeCTCentral TimeETEastern TimeGMGreenwich Mean TimeHTHawaii-Aleutian TimeMTMountain TimePTPacific TimeUTUniversal Time CoordinateRecDTM051250Date Time Period Format QualifierXID 2/3Code indicating the date format, time format, or date and time formatD8Date Expressed in Format CCYYMMDDDTDate and Time Expressed in Format CCYYMMDDHHMMRD8Range of Dates Expressed in Format CCYYMMDD-CCYYMMDDA range of dates expressed in the format CCYYMMDD-CCYYMMDD where CCYY is the numerical expression of the century CC and year YY, MM is the numerical expression of the month within the year, and DD is the numerical expression of the day within the year; the first occurrence of CCYYMMDD is the beginning date and the second occurrence is the ending dateRDTRange of Date and Time, Expressed in Format CCYYMMDDHHMM-CCYYMMDDHHMMA range of dates and times expressed in the format CCYYMMDDHHMM-CCYYMMDDHHMM where CCYY is the numerical expression of the century CC and year YY, MM is the numerical expression of the month within the year, DD is the numerical expression of the day within the month, HH is the numerical expression of hours in the day based on a twenty-four hour clock, and MM is the numerical expression of minutes within an hour; the first occurrence of CCYYMMDDHHMM is the starting time and the second is the ending timeRecDTM061251Date Time PeriodXAN 1/35Expression of a date, a time, or range of dates, times or dates and times Segment: AMT Monetary Amount Position: 060 Loop: LIN Level: Detail: Usage: Optional Max Use: >1 Purpose: To indicate the total monetary amount Syntax Notes: Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UseAMT01522Amount Qualifier CodeMID 1/3Code to qualify amount7NParticipating InterestThis code is used when the Energy Service Provider supplies less than 100% of the customer's load. Element AMT02 identifies the percentage of the service that is supplied.DPExemptionThis code is used when a portion of the provided service is exempt from taxation. Element AMT02 identifies the percentage of the service that is tax exempt.KCObligatedCapacity ObligationKYNot-To-Exceed-PriceTransmission ObligationLDIncrementalNumber of months over which Total kWh or Peak Demand are calculated.MAMaximum AmountPeak DemandQYQualifiedEligible Load Percentage. Percentage of the customers load that is eligible for competition.TTaxUsed when Account is 100% taxable AMT02 monetary amount would be 1.TATotal Annual SalesTotal kWhMust UseAMT02782Monetary AmountMR 1/18Monetary amountFor percentage values, the whole number "1" represents 100 percent; decimal numbers less than "1" represent percentages from 1 percent to 99 percent. Segment: PM Electronic Funds Transfer Information Position: 070 Loop: LIN Level: Detail: Usage: Optional Max Use: 1 Purpose: To supply information on the electronic funds transfer (EFT) method of payment Syntax Notes: Semantic Notes: 1 PM01 is the transit routing number of the Customer's financial institution. 2 PM02 is the Customer's account number. 3 PM03 is the authorization for electronic funds transfer indicator. A "Y" value indicates authorization has been granted to allow electronic funds transfer. If no authorization has been granted for electronic funds transfer, this segment is not sent. 4 PM04 is the authorization signature for electronic funds transfer on file indicator. A "Y" value indicates that a signature has been obtained and is on file; an "N" value indicates a signature has not been obtained. 5 PM05 qualifies the account number indicated in PM02. 6 PM06 qualifies the Depository Financial Institution (DFI) Identification Number indicated in PM01. Comments: Notes:This segment is used when electronic debit or credit service has been identified in LIN05. Data Element Summary Ref. Data Des. Element Name Attributes Must UsePM01507(DFI) Identification NumberMAN 3/12Depository Financial Institution (DFI) identification numberThe customer's Depository Financial InstitutionMust UsePM02508Account NumberMAN 1/35Account number assignedThe customer's account in the financial institution identified in PM01, to which debits or credits shall be applied.Must UsePM031073Yes/No Condition or Response CodeMID 1/1Code indicating a Yes or No condition or responseYYesIndicates that the customer has requested and authorized electronic debits or credits.Must UsePM041073Yes/No Condition or Response CodeMID 1/1Code indicating a Yes or No condition or responseNNoIndicates that a written authorization has been received by the CSP from the customer and is on file, thereby satisfying Regulation E, but an authorizing signature was not included.YYesIndicates that a written authorization, including an authorizing signature, has been received by the CSP from the customer and is on file, thereby satisfying Regulation E. PM05569Account Number QualifierOID 1/3Code indicating the type of accountDADemand DepositSGSavingsPM06506(DFI) ID Number QualifierOID 2/2Code identifying the type of identification number of Depository Financial Institution (DFI)Qualifies the customer financial institution identified in PM01.01ABA Transit Routing Number Including Check Digits (9 digits) Segment: NM1 Individual or Organizational Name Position: 080 Loop: NM1 Level: Detail: Usage: Must Use Max Use: 1 Purpose: To supply the full name of an individual or organizational entity Syntax Notes: 1 If either NM108 or NM109 is present, then the other is required. Semantic Notes: 1 NM102 qualifies NM103. Comments: Note:This segment is used to convey meter level information. Only NM101 and NM102 are required. Data Element Summary Ref. Data Des. Element Name Attributes Must UseNM10198Entity Identifier CodeMID 2/3Code identifying an organizational entity, a physical location, property or an individualMQMeter LocationMust UseNM1021065Entity Type QualifierMID 1/1Code qualifying the type of entity1PersonThe entity name is segmented into discrete elements; if sent, it is transmitted via NM103, NM104, NM105, NM106 and NM107.2Non-Person EntityThe entity name is not segmented; if sent, it is transmitted in NM103 only.3UnknownThe entity name is not segmented; if sent, it is transmitted in NM103 only.NM1031035Name Last or Organization NameOAN 1/35Individual last name or organizational nameNM1041036Name FirstOAN 1/25Individual first nameNM1051037Name MiddleOAN 1/25Individual middle name or initialNM1061038Name PrefixOAN 1/10Prefix to individual nameNM1071039Name SuffixOAN 1/10Suffix to individual nameNM10866Identification Code QualifierXID 1/2Code designating the system/method of code structure used for Identification Code (67)92Assigned by Buyer or Buyer's AgentAn identifier assigned by the Service Provider (N101=SJ)NM10967Identification CodeXAN 2/80Code identifying a party or other code Segment: N2 Additional Name Information Position: 090 Loop: NM1 Level: Detail: Usage: Optional Max Use: 2 Purpose: To specify additional names or those longer than 35 characters in length Syntax Notes: Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UseN20193NameMAN 1/60Free-form nameN20293NameOAN 1/60Free-form name Segment: N3 Address Information Position: 100 Loop: NM1 Level: Detail: Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UseN301166Address InformationMAN 1/55Address informationN302166Address InformationOAN 1/55Address information Segment: N4 Geographic Location Position: 110 Loop: NM1 Level: Detail: Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 N402 is required only if city name (N401) is in the U.S. or Canada. Data Element Summary Ref. Data Des. Element Name Attributes N40119City NameOAN 2/30Free-form text for city nameN402156State or Province CodeOID 2/2Code (Standard State/Province) as defined by appropriate government agencyN403116Postal CodeOID 3/15Code defining international postal zone code excluding punctuation and blanks (zip code for United States)N40426Country CodeOID 2/3Code identifying the countryN405309Location QualifierXID 1/2Code identifying type of locationCOCounty/Parish and StateN406310Location IdentifierOAN 1/30Code which identifies a specific location Segment: PER Administrative Communications Contact Position: 120 Loop: NM1 Level: Detail: Usage: Optional Max Use: >1 Purpose: To identify a person or office to which administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. 3 If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UsePER01366Contact Function CodeMID 2/2Code identifying the major duty or responsibility of the person or group namedALAlternate ContactPerson to be contacted when the main contact is not availableICInformation ContactPER0293NameOAN 1/60Free-form namePER03365Communication Number QualifierXID 2/2Code identifying the type of communication numberEMElectronic MailFXFacsimileHPHome Phone NumberTETelephoneWPWork Phone NumberPER04364Communication NumberXAN 1/80Complete communications number including country or area code when applicablePER05365Communication Number QualifierXID 2/2Code identifying the type of communication numberEMElectronic MailFXFacsimileHPHome Phone NumberTETelephoneWPWork Phone NumberPER06364Communication NumberXAN 1/80Complete communications number including country or area code when applicable PER07365Communication Number QualifierXID 2/2Code identifying the type of communication numberEMElectronic MailFXFacsimileHPHome Phone NumberTETelephoneWPWork Phone NumberPER08364Communication NumberXAN 1/80Complete communications number including country or area code when applicable Segment: REF Reference Identification Position: 130 Loop: NM1 Level: Detail: Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Data Element Summary Ref. Data Des. Element Name Attributes Must UseREF01128Reference Identification QualifierMID 2/3Code qualifying the Reference Identification18Plan NumberReading estimation method. The estimation rules applied to estimate values for missing data. See REF02 for valid values.46Old Meter NumberIdentifies meters being removed4LLocation-specific Services Reference NumberMeter service voltage4PAffiliation NumberMeter Constant or Meter Multiplier Billed Usage = (Ending Meter Reading - Beginning Meter Reading) X Meter Multiplier 7ECollector IdentificationMeter reading service provider7GData Quality Reject ReasonAdditional information about the error specific to the meter.91Cost ElementUsage calculation code. See REF02 for valid values.D7Coverage CodeMeter Installation Pending. See REF02 for valid values.D8Loss Report NumberDistribution loss designator or identifierGEGeographic NumberCustomer's time zone. See REF02 for valid values.IXItem NumberNumber of dials on the meterLOLoad Planning NumberLoad profileLULocation NumberIdentification number for the point where service is delivered to the customer.MGMeter NumberMeter ID Serial Number MTMeter Ticket NumberMeter TypeNHRate Card NumberIdentifies a utility rate class or tariffPLPrice List NumberPRPrice Quote NumberIdentifies a unit pricing category under a rate codePRTProduct TypeIdentifies the type of service; e.g., yard light, water heater, etc.QIQuality Inspection Area IdentifierIdentifies whether an Off-Cycle reading is or will be an actual or estimated reading.RBRate code numberIdentifies an Energy Service Provider rate classSCShipper Car Order NumberSpecial Identifier for unmetered accounts. See REF02 for valid values.SPLStandard Point Location Code (SPLC)Point at which the customer is connected to the transmission gridSUSpecial Processing CodeLife support equipment verification. See REF02 for valid values.TZTotal Cycle NumberMeter Cycle. Cycle number when the meter will be read.V9SubservicerMeter ownerVAVessel Agent NumberMeter MaintainerVEVendor Abbreviation CodeMeter Data Management Agent (MDMA)VRVendor ID NumberMeter InstallerYTReporter IdentificationAutomatic Meter Reading (AMR) device identification numberZRSupplier (Replacement)Billing/Metering Package OptionsZWAreaCongestion zone - a geographic area that requires power that exceeds the line capacity of the transmission system.REF02127Reference IdentificationXAN 1/30A13OtherSee explanation REF03.Reference information as defined for a particular Transaction Set or as specified by the Reference Identification QualifierWhen REF01 is 18, valid values for REF02 are: LDC - LDC's internal estimation method MADAWG01 - CA's Metering and Data Access Work Group methodWhen REF01 is 91, valid values for REF02 are: I - Interval L - Load ProfileWhen REF01 is D7, valid values for REF02 are: Y - Meter Installation is Pending N - Meter Installation is Not PendingWhen REF01 is GE, valid values for REF02 are: AT - Alaska Time CT - Central Time ET - Eastern Time GM - Greenwich Mean Time HT - Hawaii-Aleutian Time MT - Mountain Time PT - Pacific Time UT - Universal Time CoordinateWhen REF01 is QI valid values in REF02 are: A = Actual Read E = Estimated ReadWhen REF01 is SC, valid values for REF02 are: M - Metered U - UnmeteredWhen REF01 is SU, valid values for REF02 are: Y - Life Support Required N - Life Support Not Required I - Investigating whether Life Support is RequiredREF03352DescriptionXAN 1/80A free-form description to clarify the related data elements and their content Segment: REF Reference Identification Position: 130 Loop: NM1 Level: Detail: Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes:This convention of the REF segment is used for account maintenance, to convey meter-level change reason codes. The codes used in REF02 are maintained by the UIG. The first portion of the code identifies the segment that contains the data that has been changed; the remaining portion of the code identifies the relevant code qualifier for the data that has been changed. The changed data will appear in the appropriate element of the identified segment. For example, a REF02 code of AMT7N indicates that data in the AMT segment that is identified by the qualifier 7N (i.e., Percentage of Service Supplied) has been changed to the value now shown in AMT02. Data Element Summary Ref. Data Des. Element Name Attributes Must UseREF01128Reference Identification QualifierMID 2/3Code qualifying the Reference IdentificationTDReason for ChangeREF02127Reference IdentificationXAN 1/30Reference information as defined for a particular Transaction Set or as specified by the Reference Identification QualifierNM1MQChange Metering LocationPERALChange Alternate Contact InformationPERICChange Information Contact InformationREF18Change Reading Estimation MethodREF4LChange Meter Service VoltageREF4PChange Meter Constant/MultiplierREF7EChange Meter Reading Service ProviderREF91Change Usage Calculation CodeREFGEChange Customer Time ZoneREFIXChange Number of Dials on the MeterREFLOChange Load ProfileREFLUChange Location NumberREFMGChange Meter NumberREFMTChange Meter TypeREFNHChange Utility Rate Class or TariffREFO8Change New Premise IndicatorREFPCChange Party that Calculates the BillREFPLChange Price List NumberREFPRChange Unit Pricing Category under a Rate CodeREFPRTChange Type of ServiceREFRBChange ESP RateREFSIChange Indicator for unmetered accountsREFSUChange Special Processing CodeREFTZChange of Meter CycleREFV9Change Meter OwnerREFYGChange Meter Installer or MaintainerREFYTChange Automated Meter Reading (AMR) Device ID NumberREFZRChange Billing/Metering OptionsREF03352DescriptionXAN 1/80A free-form description to clarify the related data elements and their content Segment: SE Transaction Set Trailer Position: 150 Loop: Level: Summary: Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set. Data Element Summary Ref. Data Des. Element Name Attributes Must UseSE0196Number of Included SegmentsMN0 1/10Total number of segments included in a transaction set including ST and SE segmentsMust UseSE02329Transaction Set Control NumberMAN 4/9Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 814 symbol 183 \f "Symbol" \s 9 VERSION 003 RELEASE 070A UTILITY INDUSTRY GROUP IMPLEMENTATIONGENERAL REQUEST, RESPONSE OR CONFIRMATIONGUIDELINE FOR ELECTRONIC DATA INTERCHANGE page 2 NOVEMBER 1997 DRAFT NOVEMBER 13, 1998 814 symbol 183 \f "Symbol" \s 9 VERSION 004 RELEASE 010A UTILITY INDUSTRY GROUP IMPLEMENTATIONGENERAL REQUEST, RESPONSE OR CONFIRMATIONGUIDELINE FOR ELECTRONIC DATA INTERCHANGE A UTILITY INDUSTRY GROUP IMPLEMENTATIONVERSION 004 RELEASE 010 symbol 183 \f "Symbol" \s 9 814GUIDELINE FOR ELECTRONIC DATA INTERCHANGEGENERAL REQUEST, RESPONSE OR CONFIRMATION page 212 NOVEMBER 13, 1998 page 11 NOVEMBER 13, 1998  /=/=  !"#$23456@ABCDEFGKLMNOPQRS]^_`aefghituvxyz}~#$%c bc(c8c`cbcHUccc<cHcFc0UUcX%&'()y  ^_     !#$%(),-./KLMNc,]uDBEF*3cc0cccUUcY 68_`cde   U]cUccUccc,]Ucc0Uc(c(UY)*+,.=>?ABDSVX:;<>?@Acdefh]_T ~ 5#6#<####t$]cUcc]U]cUccUcU[t$$$$$$&A&&&&&&&&&&&&&&&&'' ''''''''' '(')'/'0'8'B'C'F'G'I'J'`'a'b'c'd'n'v'w'z'{'~''''''''''''''''''''''''''''(((^cU^cU^cUcccUUc(Uc"V^U^]UcV(((((((()(*(+(,(-(8(;(<(>(?(R(S(T(U(V(a(d(e(h(i(((((((((((((((((((((((((((((((()))#)&)()1)9):)=)>)A)B)U)V)W)X)Y)c)k)l)o)p)s)t))))))))))^cU^cU^cUcUccc\))))))))))))))))))))*********%*(*)*+*,*Q*R*S*T*U*b*o*r*t*}***************************** + + ++++++ +!+4+5+6+7+8+C+F+G+J+K+p+q+r+s+u++++ccc++++++++++++++++++++++++++++++,, , ,,, ,#,$,&,',>,?,@,A,B,L,M,c,k-l-v-y------------*.7.9.H.I.J.//!/B/_/`/h/i/m/n/q/r/////////U^Uc(U^cU^cU^cUcUcccY/////00 0 0 00,0-0.0/050700000000111 1(1,141e1r1s1t1111111 224252e2f2222 3&3'3/303536393:3V3W3X3Y3_3a3333333333334Y4\4^4`4g4j4l4n4444444#5%5-5.53545U^Uc(UUcc`457585P5Q5R5S5Z5\5555676?6@6E6F6I6J6N6O6P6Q6W6Y6k6l666666666666677777777777777785969l9o9q9s9~999999999999999999999999:::: :#:(:):,:-:E:F:G:H:UccUbH:O:Q:::;;;(;+;;;@;E;J;P;[;a;o;w;{;;;;;;;;?<N<P<Y<Z<[<D=H=================O>P>S>T>b>d>>>>>>> ????$?&?W?X?n?o???@@]@_@a@c@@@@@@@AAAAAAAABBUcU^Uc(cU`B-B.B C CCCCCC!CZC\C^C`CmCpCCCCC D DDDDDDDDD EEEEEEEEEEEEEEEFGFJFKFhFjFFFFFFFGGGGGGGGGGHHHHHHHH:H;HV?VAVCVVVYV^V_VaVbVfVgVhViVpVrVVVVVVVVVVVVVVVVVVWWWWWWWW"W'W(W+W,W@WAWBWCWJWLWWWWWWWWWWWWWXXX XXXXX(X+X-X/X8X;X@XAXDXEXYXZX[X\XcXeXXXXXUccXXXXXXXXXYY Y"Y1Y4Y6Y8YAYDYFYHYQYTYYYZY]Y^YrYsYtYuY|Y~YYYYYZZZZ$Z*Z5Z=ZAZIZuZZZZZZZZ[ [ [[[/]?]?^A^B^c^^^^^^^^^^^^^^^__R_T_\_]_b_c_f_g_______UcU^VUc(cU______``` ```#`$`)`*`-`.`@`A`B`C`J`L`z`{`}````````````a!a$a&a1a4agajamanaaaaaaaaaaabbbbb b/b1b2b3bjblbnbpb}bbbbbbbbbbbbbbbbOcPcRcTcechcjclc|c~cccUUccbccccccccccccccccc1d4d6d8dFdIddddddddddd eeee#e&ehekemeoeeeeeeeee^fafdfefwfyfzf{fggggggUgXg[g\gggigjgkggggggggghhhh0h2h3h4hhhhhhhiiiiiicUdi0i3i!j$j&j(j1j4jjjjjjjjjjjjjjjklkyk{kkkkkkkmmompmmmmmmmmmmmmmmmmmmmmnnn nnnnn)n,nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnoUcU^Uc(Uc`oo ooooooo1o2o3o4o:oACz}%(,-ACFH  qr &+3XefgUc(Ucb?ABc +,-.577:?A_bgiڜݜ.179TW]_ǝɝ UcU^Uca9<ACWZ_aŞǞ038:PSXZܟߟ +.35Y\acРӠנ٠+.35hkprCFKM{~ɢ̢cd̢ѢӢ #&,.ADIKnqvxۣޣ '*/1VY^` 25:<Y\acy|!&4:DJX`emئ٦ M\Uc(Ucb\^ghnp!#$EbcklqruvҨӨ֨بehkm٩ܩߩ369;MPĪƪʪ˪ܪުߪ #&psvx"%)*8:?@CDHIJKQSUcU^cUaSmnstwx®ĮƮѮԮ֮خ,/13@CEGSVXZsuxy~!#%SVY[?B=?BCHIMN^_`ahjŴUc(Ucb!&.Vcetvµʵ˵еѵԵյ),׶ڶܶ޶Ƿʷ:=?AOR]`bdmpθѸҸԸ׸ڸ"$&8;DFNOTUXYhijkrcUcU^Uart),]bgu{ jkpq!{}~žƾʾ˾ξϾ56egoptuxy"$,-1267XYZ[acUcU^Uc(Uc` -./068lmnpru*-.036 89;=KNPRY\`ade~),.0lnoy}3@AB AUc(UUcc`A^_ghmnpq ,-./57\]^`fiGJKMTW  !(*BCHIMNYZ[\ceUcUcU^a ./0179ISV} +-69ZwxUcU^Uc(Uc` )/:BFN{ -.2367JKLMTVmwz()*Wfhqrs!B_`aefhirstu|~Uc(cUcU^U`*+,-46 -.02ILPQTUhijkrt!&.!"etvEFUcU^Uc(Uc`FHJ[^ JKMO^acenqsu+,1256TUVW]_Ucc"$vw|} !*-/1BEJKNOcdefmo  +38@erst 4567=?noqs~UcU^Uc(Uc`~479;fhi~14RUWYsvLOQSeh*-9<>@OR:<>@QcbccbQTVXjm'*369;^a  WZ\^ilwz|~/2loqs,/4589QRUccRST[^achkZ\568klnstwx)/9?JRW_vxy'(*,=@EFIJUcU^Uc(bcU_Jbcdeln :=BDjmrt:=BD]`eg ,/46RUZ\FINPnqcUdqvx ?BGHKLWXYZac (>[\deijlm#%o]cuDBEF*3ccUcU^Uc(UcYoqrxyz{|^`#$%'()<=CDFGH\]uAEF*3PUacBEF*3PUac]cuDBEF*3ccPUcuDBEF*3PUc/  !"#$3456@ABCDH@H@@@@H@HH@H@``@H@``H#H (( R&,p@ P !$#H (( R&!p@ P !$3DEFGKLMNOPQR]^_`efgh@H@@@H@H@r``@H@r``@k@.$p@ P !$.#H (( R&!p@ P !$,p@ P !$!H (( R&htuvwxyz{|}~D`D`@H@@p@@H@@p@@H@@p@@H@@p@H#H (( R&!p@ P !$,p@ P !$#H ((~ R&$p@ P !$z  Hn@H@J@H@#H (( R&!H (( R&!p@ P !$,p@ P !$'H 4( R&!p@ P !$ @H@@H@@@@$@m#H (R&3!p@ P !$,p@ P !$#H (( R&!p@ P !$#$%&'()*yz{|}$$$*TT  @@333!p@ P !$!H (R&3,p@ P !$  !"'-1DMVWXY^_d*T @*T @*T @*T @ <3<3<3 <3E  d.!R&#"3AOPQRW**T @i*+E < d.!R& <3<3E R& <3 <3-E: < d.!R&<3W]awT @*T @*T @$3,p@ P !$ <3E  d.!R&<3<3$@$@@@@$@@`@@$@@@#H (R&#H (R&!p@ P !$3,p@ P !$!H (R&      !"#$%&@$@@@@$@@@@$@@@@$@@@@$@@@@$@@@@$@@@@$@#H (R&!p@ P !$,p@ P !$&'()*+,-.l@@@$@@@$Pli3#H7 (R&,p@ P !$,p@ P !$#H (R&!p@ P !$K n nhaaaYxx3x3x3!H (\ R& <!p@ P !$,p@ P !$#H (\ R&`x!p@ P !$ jkyrr3x3xx3!H (\ R& <!p@ P !$,p@ P !$!H (\ R&6`acde~ii!p@ P !$`!p@ P !$,p@ P !$3!H (\ R&33 h3hhx3hh$p@ P !$h!p@ P !$,p@ P !$!H (\ R& h$p@ P !$h,p@ P !$!H (\ R&!p@ P !$    )*+,wh$p@ P !$h!p@ P !$h$p@ P !$h,p@ P !$!H (\ R&=>?@ABCDSTUVx) p@ P !$h$p@ P !$h!H (\ R&!p@ P !$,p@ P !$V3!p@ P !$,p@ P !$!H (\ R&h,hp@ P !$:;<=>?@Acdef,p@ P !$!H (\ R&!p@ P !$f] 5#6#7#8#9#:#;#<#####m$fh,hp@ P !$,p@ P !$,p@ P !$!H (\ R& hx3h 3h h3hm$n$o$p$q$r$s$t$$$$$C&D&E&F&G&H&I&hh,hp@ P !$#H (\ R&) p@ P !$,p@ P !$!H (\ R&I&J&K&L&M&N&O&P&Q&R&S&T&U&V&W&X&Y&Z&[&\&^&_&`&a&3!H (\ R&) p@ P !$,p@ P !$a&b&c&d&e&f&g&h&i&j&k&l&m&n&o&p&q&r&s&t&u&v&w&x&y&z&{&|&}&~&&) p@ P !$,p@ P !$#H (\ R&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&#H (\ R&) p@ P !$,p@ P !$&&&&&&&&&&&&' '''''' ')'0'9':'C'x3`p8P?0! 333`pXG6%<3<3`% 33`p8P?0!3C'G'J'a'c'e'f'g'h'i'j'k'l'm'n'w'{''''''''''''''3333 `pXG6"#n##F$$%x3x3x3x3`p8P?0!'''''''''''''''''''''z33j`pXG6"#n##F$$% x3x3''''''''''''''(((((( ( ( ( ( (3[`pXG6"#n##F$$% 333 (((((*(,(.(/(0(1(2(3(4(5(6(7(8(<(?(S(U(W(X(Y(3333[`pXG6"#n##F$$% Y(Z([(\(](^(_(`(a(e(i((((((((((((333[`pXG6"#n##F$$% 3((((((((((((((((((((}3 `pXG6"#n##F$$%33[`pXG6"#n##F$$% (((((((((((((((((()))))) ) ) ) ) ))))) 3333`pXG6%<3<3`% ))))))$)%)&)))*)+),)-).)/)0)vnhhhhhhhx3x3x3`p8P?0!x3`p8P?0!]`pXG6"#n##F$$% 30)1):)>)B)V)X)Z)[)\)])^)_)`)a)b)~3333j`pXG6"#n##F$$% b)c)l)p)t))))))))))))))))))))))3333[`pXG6"#n##F$$% )))))))))))))))))))))))***333[`pXG6"#n##F$$% 3******* *!*"*#*$*%*)*,*R*T*V*W*X*Y*Z*[*\*]*^*3[`pXG6"#n##F$$% 333^*_*`*a*b*p*q*r*u*v*w*x*y*z*{*|*x3x3[`pXG6"#n##F$$% |*}***************3333i`pXG6"#n##F$$% ******************** ++++++3333[`pXG6"#n##F$$% +++++++++!+5+7+9+:+;+<+=+>+?+@+A+B+C+G+K+q+333[`pXG6"#n##F$$% 3q+s+v+w+x+y+z+{+|+}+~++++++++++++++++3[`pXG6"#n##F$$% 333++++++++++++++++++++zw3 `pXG6"#n##F$$%333[`pXG6"#n##F$$% ++++++++++++++++, ,,, ,$,',?,A,C,D,x3x3x3x3 3333`pXG6%<3<3`% D,E,F,G,H,I,J,K,L,M,d,e,,k-------).8.x  (3 p ( h3 4h. hp( h3 4h. hp p3p `pXG6"#n##F$$%x38.// /!/6/B/`/i/n/r/////////////0 00-0/0   oG$  %3 ' s &333 $ 3 $33  (3 p /060708000000 11+1d111 222c222222 3'30363:3W333 $ 3 $33  (3 p  p3p  %3 ' s &3W3Y3`3a3b33333333333333344Z4[4\4_4`4h4i4j4m4n444444 H$   oG$  %3 ' s &3#4444$5%5.54585Q5S5[5\5]55556676@6F6J6O6Q6X6Y6Z6j6k6l666  %  %3 ' s &3 H$   oG$366666666677777777777788495969m9n9o9r9s9999   oG$3  %  %3 ' s &33!9999999999999999999999999999:::::!:":#:):-:F:H:P:3   oG$3(P:Q:R::::;;0;?;I;Z;n;z;;;><O<D=======3 $ 3 $33!  (3 p  p3p  %3  %3 ' s &========N>O>P>S>T>b>c>d>>>>>>>>> ? ????$?%?&? H$ H$   oH$  %3 ' s &33&?W?X?Y?\?]?m?n?o?????? @@@]@^@_@b@c@@@@@@@@@AAAAA   oG$ H$   oH$3 H$ 3"AAAAAAABBB B!B,B-B.B C CCCCCC C!CZC[C\C_C`CnCoCpCCCCCC D H$3 H$   oH$3% D D DDDDDDDDDDDDDD E EEEEEEEEEEEEEEEEE H$ H$   oG$ H$3   oH$!EEEFFFGFJFKFhFiFjFFFFFFFFFGGGGGGGHHHHH  %3 ' s &3 H$   oG$   oH$ H$ 3HHHH;H=HDHEHFHHHHHHHHHHHHHHII$I%I&I)I*IOIPIQIIII H$   oG$  %3 ' s &33"IIIIIIJJJJJ%J&J'JrJsJtJyJ|JJJJJJJJJJJJJJJJ3  %3 ' s &3 H$   oG$3!JJLKMKNKKKKKKKKK L L LLLLLL@LALkLzLLLLLMM%M  (3 p  p3p H$   oG$3  %  %3%M0M1M2MGMSMqMzMMMMMMMMMMMMMMMMMMMMMM p3p  %3 ' s &333 $ 3 $33  (3 p MN!N2N>NsNNNNNNNNNNNNOOOOO%O&O'O,O0ODOFO  %3 ' s &333 $ 3 $33  (3 p  p3pFONOOOPOdOeOOOOOOOPOP`PPQQQ/Q;QYQZQ_QbQlQnQvQwQ33 $ 3 $33  (3 p  p3p  %3 ' s &3wQxQQQQQQQQQQQ RRRRR$R&R.R/R0RRRRRRRRRRRRRRRRRRS ' s &3  %3'SSS%S&S'S*S+SCSDSESJSNSbSdSlSmSnSSSSSSTTTTTU]UnUyU  (3 p  p3p3   oG$3  %3 ' s &yUzU{UUUUUUUUUUUU=V>V?VBVCVWVXVYV_VbVgViVqVrVsVVV   oG$  %3 ' s &333 $ 3 $33VVVVVVVVVVVVVVWWWWWWWWWW W!W"W(W,WAWCWKWLWMWWWW3   oG$  % ' s &33$WWWWWWWWXXXX XXXXXX)X*X+X.X/X9X:X;XAXEXZX\XdXeXfXXXXX   oG$  %3 ' s &33$XXXXXXXYYY!Y"Y2Y3Y4Y7Y8YBYCYDYGYHYRYSYTYZY^YsYuY}Y~YYYYY p3p   oG$  %3 ' s &33"YZZ#Z4Z@ZtZZZ [[[k[[]@^A^B^W^c^^^^^33 $ 3 $33 p%3h x3h<333  (3 p  p3p^^^^^^___S_T_]_c_g___________```` ```$`*`.`A`   oG$3  %  %3 ' s &3"A`C`K`L`M`y`z`{`~```````````````a a!a%a&a2a3a4ahaia  oG$ H$   oG$  %3 ' s &3 iajamanaaaaaaaaaaaaaabbbbb b/b0b1b2b3bjbkblbobpb~bbbb3 H$  oG$   oG$3$bbbbbbbbbbNcOcPcScTcfcgchckclc}c~cccccccccccccc   oG$  %3 ' s &33 H$"cccc2d3d4d7d8dGdHdIdddddddddddddd eeeee$e%e&eiejekeneoeeee H$   oG$3(eeeeeeeee_f`fafdfefwfxfyfzf{fggggggggVgWgXg[g\ggghgigjgkgg  oG$   oG$ H$3%gggggggggghhhhh0h1h2h3h4hhhhhhhhhiiiiii1i2i3i3 H$   oG$3  oG$ $3i"j#j$j'j(j2j3j4jjjjjjjjjjkkzkkkkkllnmompm3 p%<33  (3 p  p3 p p3p   oG$ H$3pmmmmmmmmmmmmmmmmmnnn n nnnnnn*n+n,n   oG$  %3 ' s &333 $ 3 $3,nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn  oG$   oG$3 H$3$nnnooo oooo2o4o;ox33 x3 3 x3x3  % 3^pqrx|$%&N]pˆ%&-.3  (3 p  p3p  %3 ' s &33  %'3QZ`dĈň݈ވ߈ H$<3   oG$  %3 ' s &333 $ 3 $33 p%89:wxy|}͉ΉωՉىz{|  %3 ' s &3  oG$ H$3   oG$3#$NOPTUwxy}~ċŋƋʋˋۋ܋݋01267=   oG$3  %(=>?XYZ^_vwx|}ŒÌ!"QRS|}~ H$3   oG$(؍ٍڍލߍ ./045JKLPQՎ֎׎ێ   oG$3*ێ܎"#;<=ABYZ[ JKLPQdefjk H$   oG$3(ÐĐŐ./045LMNRSklmqr H$3   oG$( 12378defjkxyz~ H$   oG$3( !DEFJKijkopƓǓȓ͓̓ٓړۓߓ 3 H$   oG$3( <=>BC{|}&'(,-ABCGH H$3   oG$(H  !pqrږ *W  (3 p  p3p  %  %3 ' s &3   oG$3@ABWcš  %3 ' s &33 $ 3 $33 p%33  (3 p  ,.67889:@A`abhi  %3 ' s &33   oG$$ۜܜݜ/0189UVW^_ȝ   oG$3*ȝɝ :;<BCXYZ`aƞǞ1239:Q   oG$3*QRSYZݟޟߟ ,-.45Z[\bc3   oG$*ѠҠӠؠ٠,-.45ijkqrDEFLM|}~   oG$3*ʢˢ̢ҢӢ$%&-.BCDJKopqwxܣݣ   oG$3*ݣޣ ()*01WXY_` 345;<Z[\b   oG$3*bcz{| 3CWd֦L]hop"3  (3 p  p3p  %3 ' s &3   oG$3"#$9EclrvѨҨӨרبfghl H$   oG$  %3 ' s &333 $ 3 $33 p%lmک۩ܩ456:;NOPĪŪƪʪ˪ܪݪ  oG$ H$   oG$3%ݪުߪ $%&qrswx#$%)*89:@3 H$   oG$  oG$ 3$@DIKRSTjkmntx®ŮƮҮӮԮ׮خ   oG$3  %3 ' s &33$-./23ABCFGTUVYZtuy  %3 ' s &3   oG$3$ !$%TUVZ[@AB>?CIN_aijk  %3 ' s &3 H$   oG$3!մ%Uduµ˵ѵյ   %3 ' s &333 $ 3 $33  (3 p  p3p*+,ضٶڶݶ޶ȷɷʷ H$ H$   oG$33$;<=@APQR^_`cdnopϸиѸӸԸظٸڸ !"%&9:;EFOUYi3   oG$3 H$ 3&ikstuRat hn !|} p%3  (3 p  p3p  %  %3 ' s &3}~ƾ˾Ͼ456fgpuy#$  %  %3 ' s &333 $ 3 $33$-27Y[bcd .0789klmopstu H$   oG$  %3 ' s &33"u+,-/0456 789<=LMNQRZ[\a  %3 ' s &33   oG$ H$3!ae*+,/0mn2 3 p   (3 p  p3p   oG$  %  %3 ' s &33 5A_hnq    oG$  %3 ' s &333 $ 3 $33l$ 3 p -/678[\]_`ghiHIJLMUVW3 H$   oG$  %3 ' s &3" !)*+ABCINZ\def3  %3 ' s &3&/189: H$   oG$  %3 ' s &33" GHr ,789NZx ' s &333 $ 3 $33  (3 p  p3p  %3(9Ez3 $ 3 $33  (3 p  p3p  %3 ' s &33 ,-.37KMUVWklVg !633  (3 p  p3p3  %3 ' s &36B`afisu}~+-567  %3 ' s &333 $ 3 $! ,-.12JKLQUikstu   oG$  %3 ' s &33"%duDEF  %3 ' s &333 $ 3 $33  (3 p  p3pFIJ\]^ IJKN  %3 ' s &3 H$   oG$3"NO_`adeopqtu*+,26  %3 ' s &3   oG$3$6UW^_`3   oG$  %3 ' s &3$#$%stvw}  !+   oG$33  %3 ' s &3$+,-01CDEKOdfnop *7d33  (3 p  p3p  %3 ' s &33   oG$57>?@mnors5 H$   oG$  %3 ' s &333 $ 3 $567:;ghi234STUXYtuv  oG$ H$   oG$3 H$#MNORSfgh G$ G$   oG$3 H$#+,-:;<?@PQR3 H$ H$   oG$3%:;<?@RSTWXklm  oG$ H$   oG$ H$3"()*456:;_`a H$   oG$33&  XYZ]^jklxyz}~ H$   oG$3 G$&012mnors-./59RT\]^b ' s &3   oG$ H$3$bcijk0X4Z[\ L3 x3  % \3^ \<3^  %3 H$   oG$3678dt9lmntx3 x3E333  % ^3^3(8IVwxy33 $ 3 $33 p%33  (3 p  p3p  %3 ' s &&'(+,>?@FJcemno ;<=CD   oG$  %3 ' s &33$Dklmst;<=CD^_`fg   oG$3* -./56STU[\   oG$3*GHIOPopqwx @   oG$3*@ABHLXZbcd2>\ 3 $33  (3 p  p3p  %3 ' s &33   oG$\ejm$%&Dnold& ld&333  %3 ' s &333 $opq| 3]^_`);<HZ[\]$$ $3hh3ld& ld&33hh3`33K@Normal3]a P@P Heading 12,p@ P !$Uc0"@" Heading 2b"@" Heading 3 ^0@0 Heading 4Lx"A@"Default Paragraph Font @ Footer ! @ Header !)@ Page NumbercO"Element<$O2$ Definition<c$OB$ Code Note </ ]]{ ]g%t$()+/45H:BIMQUX_cio^rNz/#p̢\SrAF~QRJqo}~DhW&  Vfm$I&a&&&C''' (Y((()0)b))*^*|**+q+++D,8./0W3469P:=&?A DEHIJ%MMFOwQSyUVWXY^A`iabceg3ipm,nnoprlvwy{}Qp=ێ HȝQݣb"lݪ@i}$ua6FN6+5bD@\o]      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKL%UnknownStandard Configuration.KM]9 " gnr9!99!!book1book2book3book4book5book6book7book8book10book11book12book13book14book15book16book17book18book19book20book21l*-8BIJfLPVmoIm^ l*-8BIJfLPVmoIm^eStandard ConfigurationKC:\My Documents\Program Office\CSS DA Interfaces\EDI 814v4 UIG (3-3-99).doc@ ATimes New Roman Symbol &ArialWingdings#h*3*3j+A#f#-814 General Request, Response or Confirmation#Implementation Guideline for TS 814Standard ConfigurationStandard Configuration  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRYaRoot Entry F }=gu=gXWordDocumentFTF+6QXFTF1XFTF+6-TKGCompObjAF+)XJGHHDCj,@SummaryInformationUlFC@F(1سFeF$ @  FMicrosoft Word Document MSWordDocWord.Document.69qOh+'0$0<P p|    .814 General Request, Response or ConfirmationA$Implementation Guideline for TS 814Standard ConfigurationF Normal.dotDocumentSummaryInformation8 ՜.+,0HP\dl t| UIG2f .814 General Request, Response or ConfirmationStandard Configuration2GMicrosoft Word for Windows 95G@F#@B2@=g@=gA#՜.+,0HP\dl t| UIG2f .814 General Request, Response or Confirmation