ࡱ> Y =fbjbjWW 0==a-]RRRRRRRffff8f..DDDDDD?P$?3tRDDDDDt"RRDD,"""DRDRDffRRRRD"d" :&gRRDDXff" **Requirement/ IssueDiscussionPolicyAction 1. SCE HIGHThere are four phases to customer relationship Connect Update (priority; validated) Disconnect Change (Acct Maint)No Policy RequirementAction Item: Need to clarify language and terms for ALL Market Participants.2. SCE LOWAll transactions require the following: Security, Authenticity, AcknowledgmentNo Policy RequirementSecurity and authenticity may be accomplished electronically as well as paper documents.Action Item: State explicitly that electronic authorization is permitted for all actions unless prohibited by law or regulation.3. SCE HIGHDo the UDCs have any responsibility for fixing data on inbound 814No defaulting on any fieldsInfo provided by ESP is only info to be used for validation in accept or reject; no defaults; no changing. (Agreement on 1/21/99) Agreed3a Group HIGH What should the DASR Response contain?Trying to get info off Bill Statement can be challenging; so Meter Number can be a problem. In response, UDC mirrors back what was sent in. In response, UDC sends both the mirror of what was sent in as well as different data UDC has on file. In response, UDC sends data as they have on file (i.e., Name, Address, Meter #, etc); only when DASR has been accepted. (Agreement on 1/21/99) DASR response must include previous 12 months billing history including usage and billed amounts, including unbundled components (i.e. distribution, transmission, energy, CTC, taxes, etc.) Agreed4. SCE HIGHIs it a best practice to send all text (Name, Address etc.) sent in upper case?Key Fields are all numeric. Additional elements are required on a per UDC basisIn the transmission, only Upper Case for text is used. (Agreement on 1/21/99) Agreed5. SCE HIGHHow is data changed in UDC or ESP customer data baseIf the UDC is not fixing data, is the maintenance transaction the exclusive means to change data. What fields to communicate as changed is based on Acct Maintenance document.See 3a When data changes (based on Acct Maintenance list of fields) Acct Maint transaction sent to other party (UDC/ESP). (Agreement on 1/21/99)Agreed Action Item: Review list of fields in Document **Requirement/ IssueDiscussionPolicyAction 6. SCE HIGHWhat are the acceptable choices for unbundled services; Are MSP and MDMA fields required for DASR acceptanceDA Rule or UDC tariff or both Optional fields on the 814 Implementation Guide. ESPs would like flexibility in not having to specify at time of DASR, but UDCs use this info in other operation processes. Scheduling Coordinator will be included on DASRs. Requiring MSP to be specific on Connect DASR has caused problems with ESPs in scheduling Meter installations. For those who want to specify a specific MSP, then it will be identified in the MSP field on DASR. If ESP specifies MSP, then will it need to be kept updated? ESP will transmit the Billing Option, MDMA, SC and designate the MSP (and Meter Owner) as ESP or UDC or Specific Entity. (Most preferred by non-UDCs; UDCs need to assess impact to other operations.) ESP will transmit the Billing Option, MDMA, SC, and designate the Maint MSP, &; and follow-up with Acct Maint for installation MSP. ESP will transmit the Billing Option (specific), MDMA (specific), SC (specific), and designate the MSP as at least UDC or ESP. (Agreement on 2/1/99) Agreed (including MSS discussions) Action Item: UDCs to assess impact to other operations if ESPs only designate MSP as ESP or UDC on DASR. (completed) Action Item: Align Data Dictionary to new Policy. Action Item: Need to clarify what optional MSP designation means; will it still need to be maintained?7. SCE MEDDo rejected DASRs include warning messages if applicable?All rejected DASRs use the agreed upon reject code list. Reject code list is a minimum. Text description is optional, warning messages no longer sent.The ESP will receive a reject code for all rejects (that can be determined) contained in the DASR. There will be a standard list of these Reject Codes, maintained by DASR Change Control Process. (Agreement on 2/1/99)Agreed Action Item: UDCs will document their validation rules. **Requirement/ IssueDiscussionPolicyAction 8. SCE HIGHIf Account number is the primary key field, is the second key field the same across all three UDCs. Are non-key fields also being validated? What is contained in response? There is difference between validating DASR (key fields) and validating data.See Data Dictionary and Key Fields list from the work group report posted to the PUC website. ESPs need to know what the UDCs use as the secondary key. If using ZIP code, do not require Zip+4. But, ZIP code could be too loose a validation with Account Number. Some ESPs have difficulty obtaining Meter Number for enrollment. Also, certain accounts do not have meters. Want to have some assurance that Acct identified is the right one. PG&E: Primary key is Acct Number; Secondary key is Zip Code SDG&E: Primary key is Acct Number; Secondary key is Meter Number. (Sometimes difficult to get Meter Number) SCE: Primary key is Acct Number, Secondary key is Name & Address.DASRs will include all required fields; including a Primary (UDC Acct #) and Current UDC Secondary key(s) for validation. UDC Secondary key(s) are Conditional. (Agreement on 2/1/99) All three UDCs should move to zip code as secondary key. Meter numbers are more difficult for ESPs to obtain, and name and address are notoriously difficult to match perfectly especially since the service could be in a variety or persons names (husband, wife, etc.) Agreed Action Item: UDCs clearly document what are the Primary and Secondary keys they validate on. (completed) -SDG&E uses Meter Number as secondary key; SCE uses Name & Address as secondary; PG&E uses ZIP Code as secondary. Action Item: Have Meter Number as Conditional field; have Zip Code as Conditional field & Zip + 4 as optional. Republish Data Dictionary.9. SCE MEDIf the ESP does not meet the credit requirement for consolidated billing three days prior to DA switch, how does the UDC notify the ESP? Is this handled through Update or Acct Maint? Some ESP billing systems require the trigger from UDC.Update transaction will communicate relationship changes. **Requirement/ IssueDiscussionPolicyAction 10. SCE HIGHIf multiple meters (kWh & kVAR; or Multiple kWh; Totalizer/Recorder) relate to the customer account, are all related meter numbers send on the DASR NOTIFICTION ACCEPT? One DASR, one Account, One Meter was original concept.Is the Meter Installation Removal Notification more suitable to convey related meter numbers?Policy should follow procedures developed by meter installation group led by PG&E (Sue Sponsel).11. SCE LOW How is meter configuration information requested using 814?Is the 650 a consideration for this information814 should be used for request, 650 for response.12. SCERed List information (potentially dangerous customer site) will not be provided by the UDC for liability reasons.UDCs cannot provide red list information to ESPs. (Agreement on 1/21/99)Accepted13. SCE HIGHExactly what is the content of the Rate Schedule data? (Is it as identified on the customers account record, or as it appears on the bill statement?)For ESP Consolidated Billing, the rate schedule provided to the ESP for processing and billing purposes should be the rate in which the Customers bill is calculated for the UDC portion of the bill. This rate is assumed to be in the mapping for DLF and able to be referred to in the referred to in the UDC posted tariffs.The rate schedule provided by UDC will be the same as provided on the Customers Bill Statement. (Agreement on 1/21/99) The UDC must also provide the baseline designation (or baseline quantities) in the DASR response.Agreed14. SCE LOWWhat is the format for the SDP elementSDP Format should be as follows 10 followed by DOE identifier (five digits) followed by unique number assigned by UDC.Action Item: Wait for the SDP Workgroup; Need to get final details out to Rule 22. 15. SCE HIGHHas the market resolved the minimum time required to switch a customer to DAGreen Mountain ProposalWhen no meter change required, DA switch will be scheduled to occur no later than 15 calendar days from receipt of DASR to the next scheduled Meter Read. (Agreement on 1/21/99) This is unclear. Does this mean the next scheduled Meter Read no less than 15 days after the DASR is accepted? Please clarify.Agreed **Requirement/ IssueDiscussionPolicyAction 16. SCE HIGHWhat is the DASR processing priority rule for multiple DASRs received for the same processing period from more than one ESP?Refer to DA Decision, review language. What about subsequent DASR when prior DASR is still awaiting pending Meter Change? How long does this hold up subsequent DASR? If first DASR accepted in error, need to CANCEL the first, before allowing subsequent DASR to be processed and accepted. SDG&E allows new DASR to override prior one when a new monthly cycle starts (after 15th of the month). Customer has option to call in and Cancel a DASR through ESP. Should the Customer be allowed to force a Cancellation if ESP is not cooperating? Customer does receive letter when switch is accepted. First In has Priority. Subsequent DASR switch can process after the first has been accepted. Switch would take place after prior ESP-Customer agreement in effect at least 1 month (Rule 22 Tariff).A Connect DASR receiving an acceptance by UDC indicates the account has been scheduled to be switched. Reject subsequent Connect DASR, if first DASR is still Pending, for at least cases without Meter Changes. (Agreement on 2/1/99) A Connect DASR receiving an acceptance by UDC indicates the account has been scheduled to be switched. Reject subsequent Connect DASR, if first DASR is still Pending (even Meter Changes).Agreed Action Item: Continued discussion in other forums to handle the priority processing for Meter Change cases. (By March DA meetings)17. SCE HIGHInitial ACK in CMEP response (at account level) mirroring ESPs DASR is no longer necessary, replaced by EDI 997 (at file level). DASR CONNECT is responded with: Accept, Reject, Pending.In EDI, 997 will indicate acknowledgment of receipt of file; which would not be at account level. What is the date/time stamp for determining the start of the processing clock? The start will be based on when the VAN received the input EDI file. This may make it more difficult for ESPs to track individual accounts. EDI 997 (at file level) will replace the initial ACK response in CMEP (at account level) to satisfy 2-day required acknowledgment. (Agreement on 2/1/99) Agreed Action Item: ESPs need to review impact on their Account tracking. **Requirement/ IssueDiscussionPolicyAction 18. SDGE HIGHWhat is the decision requirement for new customer (new premise) and new customer to service territory? Needed for New Customer Flag.In 1999, New Customer required to be able to switch to DA within 5 days. When does 5 days start (when account number assigned)? New Construction is more difficult case to handle. For New Premise, need to have Meter Set. Contractors may want to use ESP meter installed.Five days should start from date DASR is submitted by ESP to UDC. ESP should be allowed to act as customers agent in contacting UDC to initiate distribution service (if permitted by Rule 22).Action Item: Need subgroup (UDCs and interested ESPs) to review proposals and determine what can work; including notifications, account number, meter number, etc. Action Item: UDCs will clarify how their new Account Numbers will be communicated to ESPs. 19. SCE HIGHFor a Pending DASR with meter change, is a final response sent later with the actual switch date (After Switch Response).A DASR is Accept, Rejected, or Pended based on acceptance criteria, a pending meter change is a separate issue. ESP needs to know how to closeout Pending cases. Any DASR response in Pend or Accepted with Meter Change status, requires a final DASR response. UDCs send Post-Switch Notification for all accepted Connect & Disconnect DASRs; including Meter Number, Date. (Agreement on 1/21/99)Agreed Action Item: Need to look at how to accomplish this in systems & when it can be made available. **Requirement/ IssueDiscussionPolicyAction 20. SDGE HIGHHow long is it reasonable to hold an accepted DASR that requires a meter set, if the meter change does not occur.If installation has long lead time, would not want to have process interrupted. Need process to extend time limit, in certain cases. Some want warning notification from UDCs as getting close to expiration. SDG&E needs to move forward on this as a policy. UDCs would prefer to not have to provide advanced notification; just send Disconnect notification. To extend, would ESPs need to resubmit DASR? After 3 months, an accepted DASR with Meter Change that has not been installed, a Disconnect is sent. DASR expires 180 days from time of Accepted. DASR expires 180 days from time of Accepted, with ability of ESP to extend, otherwise Disconnect.After 180 days, an accepted DASR with Meter Change that has not been installed (for an official switch), Pending status is canceled and a Disconnect is sent, with reason in transaction. Existing DASRs are grandfathered, tied to EDI implementation time. (Agreement on 2/1/99) Agreed21. PGE (see #10)Each 814 represents one DASR/ one account, can it represent zero or more than one meter if the account represents multiple meters?DASR can be for unmeter as well as metered service. The transaction set can handle multiple meters in one 814. UDC Policy determines if one DASR can be for one or more Meters.Note:Check documentation for definitions: Connect/Update (Replace) Account Maintenance/ Information Request ResponseNote:Relationships refer to MDMA, MSP, Billing Agent, etc. **Requirement/ IssueDiscussionPolicyAction 22. PGE HIGHFor UPDATE, ACCT MAINTANCE, should the DASR (request/response) identify all relationships? Or only relationships that are changing providersPer documentation these are two transactions. Requirement to know all relationships is not DA Decision requirement Acct Maint is Customer Profile type information, while Update is more Billing/Relationship type of information. On ACCT MAINT, send additional confirmation response if change applied (avoiding future resubmittals of same Acct Maint)?For UPDATE and ACCT MAINT transactions, only need to supply required fields relative to what is actually changing. The UPDATE Response will confirm those changed items (i.e., what was submitted on Update). The ACCT MAINT will only have an Accept/Reject Response, does require other party to make change. (Agreement on 2/1/99) Agreed Action Item: Need to document Update Response Data Dictionary.23. PGE HIGHFor UPDATE, should the response communicate the effective start date for each relationship (pending or current) identified in the requestPer documentation these are two transactions. Requirement to know all relationships is not DA Decision requirement. Information exchange is bi-directional. Updates to relationships still use existing Connect DASR logic? Some ESPs would like to use Requested Date to stage Connect DASRs. Will address this possibility in the future. For UPDATE, single date in submittal (Requested Date) and response (Effective Date) will apply to all identified relationships. Effective Date is based on acceptable date using existing relationship change rules (usually at next Scheduled Meter Read date). If different dates needed, send separate UPDATE transactions. (Agreement on 2/1/99) Agreed 24. PGE HIGHFor UPDATE, ACCT MAINTANCE, should the response communicate the status for each relationship identified in the requestPer documentation these are two transactions. Requirement to know all relationships is not DA Decision requirement.25. PGE HIGHUPDATE DASR will communicate changing ESP relationships and new providersPer documentation Update DASR is a replace. Requirement to know all relationships is not DA Decision requirement. More for future considerations. **Requirement/ IssueDiscussionPolicyAction 26. PGE HIGHUPDATE RESPONSE will confirm all changing relationships and their providers and one status and one start date.Per documentation, Update DASR is a replace, showing all fields. Requirement to know all relationships is not in DA Decision. Dependent on how many changes included in given UPDATE transaction. Is logic for effective date on change similar to Connect? One transaction per Update.27. PGE HIGHCONNECT DASR sets up New ESP and associated relationships, all relationships and their providers will switch together.Requirement to know all relationships is not DA Decision requirement.28. PGE HIGHCONNECT RESPONSE DASR will confirm all relationships and their providers with one status or date. The status and date are shared by all relationships.Requirement to know all relationships is not DA Decision requirement.29. PGEFor Disconnect, DISCONNECT DASR will communicate the ESP relationship/provider to disconnect.For DISCONNECT, Disconnect DASR will communicate the ESP relationship/ provider to disconnect. Meter Ownership is important information for UDC (Update DASR can be used to provide this information). If a Meter Change is required, an effective date is blank; supplied later when Meter Change takes place.Disconnect DASR applies to all relationships for that Account, except for Meter Ownership if Customer owns the meter. (Agreement on 2/1/99)Agreed30. PGE HIGHDISCONNECT RESPONSE PGE will confirm the disconnect to the ESP with a disconnect response. All relationships subcontracted to the ESP are disconnected and share the same stop date.Is there a market requirement? What are limitations on the date for Disconnect? Can ESP select a specific Disconnect Date? **Requirement/ IssueDiscussionPolicyAction 31. PGE HIGHUPDATE DASR will communicate those changing relationships and their new providers.Is there a market requirement? Need to be clear on consistent interpretation and use of codes in EDI. If same date, can send multiple changes on one Update transaction (EDI 814); otherwise would require separate Update transactions.UPDATE DASR will only be used for changing relationships - Billing Options, MSP, MDMA, Meter Owner, SC. (Agreement on 1/21/99) UPDATE should also be used for UDC rate changes (e.g. to time-of-use).Agreed32. PGE HIGHUPDATE RESPONSE will communicate changing relationships and their providers and one status or start date.Is there a market requirement? 33. PGE HIGHACCOUNT MAINTENANCE data should not be restricted to standard switching logic. Can send data that changes along with key fields.Is there a market requirement?Account Maintenance transactions will handle non-relationship changes. Required fields are determined by the requested change. (Agreement on 1/21/99)Agreed34. PGE HIGHACCOUNT MAINTENANCE RESPONSE will include Key Fields and changed data onlyIs there a market requirement?35. PGE HIGHAre Key fields sent for every transaction?Yes Should this be stated as All Required Fields sent with every transaction?All Appropriate Key Fields are sent for each transaction. (Agreement on 1/21/99)Agreed Action Item: Need clear definition of Key Fields (esp Acct Number), what is the minimum set.36. PGE LOWResend request (ESP to UDC will communicate Key Fields onlyIs there a market requirement? Future consideration.37. PGE LOWResend Response will communicate one relationship/provider and all associated dataIs there a market requirement? Future consideration.38. PGE LOWIf data is missing or incorrect a DASR is REJECTED, UDC will send Reject Code in the REF02 and further clarification in the REF03If data is missing or incorrect a DASR is REJECTED, UDC will send Reject Code in the REF02 and further clarification in the REF03. Looking for Clarification of EDI Transaction Rule.Action Item: UDCs still working on consistent Reject Codes and descriptions. ESPs welcome to participate.**Requirement/ IssueDiscussionPolicyAction 39. PGE HIGH After Switch Notification to ESP (Confirmation) is sent after switch Notification upon completion of Enrollment, confirming meter switchIs there a market requirement?40. PGE HIGHAfter Switch Notification (Confirmation) is sent after every switch to a new relationship providerIs there a market requirement? Who notifies the new ESP who was the old ESP to get Historical Usage data? ESPs may need to maintain contact information on each other. To exchange EDI data, will require some trading partner or MDMA server information sharing among ESPs.After-Switch Notification (Confirmation) is sent after every switch to a new relationship provider. On Disconnect, this will include the new ESP (Dunns #), to indicate where to send Historical Usage data. On new Connect DASR Response, let the new ESP know who was the old ESP (Dunns #), for obtaining Historical Usage data. (Agreement on 2/1/99)Agreed Action Item: ESPs need to work out how to inform each other of contact, server information, etc.41. PGE HIGH After Switch Notification (Confirmation) is sent after every switch to a new ESPIs there a market requirement?42. PGE LOWIn the 814, what REF codes should be identified in the account level LIN loop and the meter level MN1 Loop.EDI Map question.43. PGE LOWAgreed upon definitions for ESP, (OLD) ESP, Current ESP, Pending (NEW) ESP, UDC, LDC, UIG Codes and California Market codes.44. PGE HIGHAdd SDP element to list of key fields.SDP is one of Key Fields after initial response.SDP should be the primary Key Field in all transactions once SDP is available.45. PGE LOWMake sure California guide terminology is consistent with UIG46. PGE LOWRevisit required fields for Connect, Disconnect, Update, Account MaintenanceSDP should be the primary Key Field in all transactions once SDP is available. **Requirement/ IssueDiscussionPolicyAction 47. SCE HIGHWill communicate notification of turn off request when turn off is issued and every time the turn off is rescheduled or is cancelledIs there a market requirement? Is Policy dependent on size of customer? Also, if UDC not the MDMA, is advanced notification needed? What other information needs to be included? Distinction between temporary shut-off and moving out turn-off. Notification (EDI) is the key issue.48. ORA HIGHNeed to identify when kVAR metering required.Need to know if kVAR required for Billing. Also, how to handle multiple meters that include kWh & kVAR. On DASR Response, include ALL meters. How will ESPs know about totalizers and recorders? Are the Meter Specific Services forms (maybe EDI 650 in future) better suited for communicating detail meter data, instead of DASR Response?EDI 814 DASR Response will identify if account requires kVAR for Billing. DASR Response will include identification of all Meter ids on the Account. (Tentative pending UDC action item to determine feasibility on DASR Response)Action Item: UDCs to determine how they could deliver the kVAR identification. (2 weeks) Action Item: Need flag (code) in EDI 814 for identifying if kVAR needed for billing. 49. PGEES HIGHConsistency on combination of identifiers with DUNNS numberSDP should be the primary Key Field in all transactions once SDP is available. **Requirement/ IssueDiscussionPolicyAction 50. SDGE HIGHTimeline for migrating to EDI 814; including which version (4010).Policy changes will take effect when EDI implementation takes place; a packaged deal. Will there be an Operational Manual that documents the new Procedures and Policies? The EDI 814 version 4010 will be the accepted version for All at time of Implementation; no interim changes to existing EDI 814 3070 version or CMEP would be made. (Agreement on 2/1/99)Accepted Action Item: Document Calif EDI 814 mapping guide for version 4010. Action Item: DASR Consistency subteam to provide new generalized procedures & processes to Operational Manual subteam. UDCs initially posted time table (for various Quarters in 1999) to Rule 22 (in September 1998).51. SCE LOWHow to communicate Tax Exemption status?Issues on whether and what information should be communicated.This should be communicated in the DASR Response.Action Item: Resolve in separate forum.52.  DASR / Account Maintenance - Business Policies/Issues ** - Prioritization: HIGH = Consistency Needed Across Market Page -  PAGE 14 DASR / Acct Maint Consistency Group MED = Agreement between Specific UDC & ESP may be sufficient As of: 2/1/99 LOW = Not Business Policy, more Technical Issue "1INvsaS E j BD|\y|%(S/`3 """Hhy2&H5Hhy2&HHhy2&HCJHhy2&HHhy2&HHhy2&HHhy2&HHhy2&HcHdhy2&gH55CJ=")1259>?nv"#Ӕ0w$$$$$$$lLH ,s5$$$$$")1259>?nv"#KVdsbcfjoTU\]`fkl ! < & j q r               T#KVdsl$H & F$Eƀy2&() H & F$Eƀy2&() H & F$Eƀy2&() $sbcfjoTU\]`fkl !  $$$$$$lLH ,s5$ < & j q r $$$$$lLH ,s5$$ O m ]^&'$$$$$lLj6,s5$$$$$$$lLH ,s5 O m ]^&'CDgh|}\7>?yz|sta&'(/0 S/abcg     \CDgh|}\7>?yz|$$$$$$lLj.,s5$sta&'(/0ڸ$$$ !$$$$lLH ,s5$$$$$$$$$ !$$$$lLj ,p5$ S/abcgkD$$lLj ,p5$$ !$$$$lLj ,s5gkl* 3 4 8 < A """"## #1#2#_######$$ $Y$s$%%%%%%%%%%%%%j&&(()p*q*.+5+6++++++,-j.q.r............./00000*1R1S111V2W2[2_2d22333   _kl* 3 4 8 < A """"## #1#2####( $$lLj ,p5$$$$lLj ,p5$""""2####s$$%%%%%%%'')q*-++-h.j......00R1S1S23g4o444445899@;W;b;q;n=?@MB;DRD]DlDZII4KKKVKeKL0MwMxMN_OpOuOiP QSTHhy2&H5Hhy2&HHhy2&HH*5CJHhy2&H5Hhy2&H5Hhy2&H5J#$$ $Y$s$%%%%%%%%%%%%%j&p$$lLH ,s5$$$$$$$lLj ,p5$$$j&&(()p*q*.+5+6++++++,-j.q.r.. $$$$lLj ,p5$............/0 }}zww$$$$$lLH ,s5$$$$$N$$lrLj ,p5 0S111V2W2[2_2d223333h4o4p4444444 $$$$$$$$$$lLj ,p5$33h4o4p4444444455 5555556#6L6q6666 7"7#777778192999:9>9B9L99::::::::::::;:;;;<;=;>;@;C;W;b;i;q;r;v;z;;<<<n==>>>>??? ???@DBEBFB          Y4455 5555556#6L6q6666 7"7#77777$$$$$$lLH ,s5$$78192999:9>9B9L99::::::($$$lLj ,p5$$:::::::;gdddGd$$lLj ,p5$L & F$ VEƀy2&L & F$ VEƀy2&;:;;;<;=;>;@;C;W;b;i;q;r;v;z;;<<<n=D$$$lLH ,s5$$$$$$$lLj ,p5$$n==>>>>??? ???@DBEBFBMBNBSBWB\BBHCICJCKC, ߸$$$$lLj ,p5$FBMBNBSBWB\BBHCICJCKCOCSCXCC6D7D8D9D;D>DRD]DdDlDmDqDuDzDDFFFF FFFFFFFFFFFyGGGGGGG(HZIIIIIIIJ/K0K1K2K4K7KKKVK]KeKfKjKnKsKKL0MPMTMaMjMwMxMMMMMMMNNNNN"N   _KCOCSCXCC6D7D8D9D;D>DRD]DdDlDmDqDuDzDDh$$lLj ,s5$$$$$$$lLj ,p5$$$DFFFF FFFFFFFFFFFyGGGGGGG(HZII4߸ߴ$$$$lLj ,p5$IIIIIIJ/K0K1K2K4K7KKKVK]KeKfKjKnKsK h$$lLj ,s5$$$$$$$$lLj ,p5$sKKLxMMMMMMMNNNNN"N'NNN`OgOhOlOpOuOOd<$$lLj ,p5$$"N'NNN`OgOhOlOpOuOOOOOOOOOPPPiPPPP!Q"Q&Q*Q.QjQQQQQQQQR8R9R:R;R?RCRGRRSSSSSTTTT T$T(T-T.TTTTTTTTTIU\VWWW'X(X,X0X6XXXXXXXXX"Y4Y5Y6Y7Y;Y?YCYYY   `OOOOOOOOPPPiPPPP!Q"Q&Q*Q.QjQQQQQQ`$$$lLj ,p5$QQQR8R9R:R;R?RCRGRRSSSSSTTTT$$$$$$$lLj ,p5$$TTT\V'X)ZwZ"[p[u[[[[_y``aa3a>aMaMb3ddddeeEeFeGeeeeeeeeee9f=f0JmH j0JU0J5CJ5CJ Hhy2&HHhy2&H55CJ)T T$T(T-T.TTTTTTTTTIU\VWWW'X(X,X0X< $$lLj ,p5$$$$lLj ,s50X6XXXXXXXXX"Y4Y5Y6Y7Y;Y?YCYYYYYYYYY44$$lLj ,p5$$YYYYYYYY)ZVZwZxZyZzZ~ZZZZZZZZZZZ!["[O[p[q[r[s[u[x[[[[[[[[[9\T]U]V]W]_]d]]^_$`%`{`|```````aaaaaa3a>aEaMaNaRaWa\aaMb cccYcZccc3d4d8daEaMaNaRaWa\aaMb $$lLj ,s5$$$$$$$lLj ,p5$$Mb cccYcZccc3d4d8d@ABCEFGHJLMNOQRSTUWXYZ\]_`bcdeg g3FB"NYe=f?DIPV[afUnknown Chris King}/!!&F K i n  afX]/3FO$")".///+00044445588L9X9f9k9<<LLRRwS|SzY~YYYYYbStandard ConfigurationWC:\My Documents\Direct Access\DA Workshops\DASR - Acct Maint Bus Policies (1-21-99).docStandard ConfigurationVC:\My Documents\Direct Access\DA Workshops\DASR - Acct Maint Bus Policies (2-1-99).docStandard ConfigurationVC:\My Documents\Direct Access\DA Workshops\DASR - Acct Maint Bus Policies (2-1-99).docStandard ConfigurationVC:\My Documents\Direct Access\DA Workshops\DASR - Acct Maint Bus Policies (2-1-99).docStandard ConfigurationVC:\My Documents\Direct Access\DA Workshops\DASR - Acct Maint Bus Policies (2-1-99).docStandard ConfigurationVC:\My Documents\Direct Access\DA Workshops\DASR - Acct Maint Bus Policies (2-1-99).docStandard ConfigurationVC:\My Documents\Direct Access\DA Workshops\DASR - Acct Maint Bus Policies (2-1-99).doc Chris KingPC:\WINDOWS\TEMP\AutoRecovery save of DASR - Acct Maint Bus Policies (2-1-99).asd Chris KingDC:\EUDORA\Attach\DASR - Acct Maint Bus Policies (2-1-99)-cellnet.doclAN^w*@hh56>*CJOJQJo(() lAܠB@h VOJQJo(@HP DeskJet 560C PrinterLPT1:DESKJETCHP DeskJet 560C PrinterHP DeskJet 560C Printer(,,@^|HP DeskJet 560C Printer(,,@^|``4U`` ,=bp@GTimes New Roman5Symbol3& Arial"Ahy2&y2&]2F P(\0dHb Proposed ByStandard Configuration Chris KingOh+'0 ( D P \ ht| Proposed ByropStandard ConfigurationtantanNormald Chris Kingn2riMicrosoft Word 8.0i@@ N@bX@bX P՜.+,D՜.+,L px  SDGEd(Hbj  Proposed By Title 6> _PID_GUIDAN{D87196E9-C4A0-11D2-853C-0060978B9B0A}  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghjklmnopqrtuvwxyz|}~Root Entryl(@t|Cd|DE F@cX_’XF1TableJan21DASRAcctMaintBusPolicies.docJAN21D~1.DOC DASR - Acct Maint Bus Policies (1-iocDWordDocumentE4&j# CellNet Com AA report.docCELL8EEH&w 867mod.doc867MOD.DOC0ESummaryInformationZO2l9&t DASR -(s Mtg Attendees (1-21-99).docDASR-AsܩEDocumentSummaryInformation*&! EX8R.DOܩE*"2t*&! EX820.doc{ܩECompObjEX867_IU.docEX867_IU.DOCܩE2(2*&!X867_MU.DOCE"jObjectPoolE2(25& ME-EBT10.docME-EBT10._’X_’X.DOCETE;& Jan.25MeterUsageDataConferenceCallNotes.docJAN25M@25& Joint-UDC-ESP-Metering-Handbook1.d  FMicrosoft Word Document MSWordDocWord.Document.89q