PARTICIPANT BUILD PACK 1 PROCESS FLOW DIAGRAMS VER 3.3 TABLE OF TRANSACTIONS VER 3.2 DOCUMENT REF: VERSION: 3.4 DATE: 01 JULY 2014 FINAL :

Transcription

1 PARTICIPANT BUILD PACK 1 PROCESS FLOW DIAGRAMS VER 3.3 TABLE OF TRANSACTIONS VER 3.2 PREPARED BY: DOCUMENT REF: VERSION: 3.4 MARKET DEVELOPMENT DATE: 01 JULY 2014 FINAL :

2 Document Approval and Acceptance AEMO Approval This document has been prepared by: NAME: Position: Signature: DANNY MCGOWAN Principal Regulatory Analyst Date: This document has been reviewed and conforms with the authorised changes to the Gas Interface Protocol: NAME: Position: Signature: PETER ALBERTS Senior Manager, Gas Retail Market Development Date: This document has been reviewed and conforms to AEMO s regulatory obligations: NAME: Position: Signature: TERRY GRIMWADE Executive General Manager, Market Development Date: Doc Ref: ver JULY 2014 Page 2 of 51

3 Version History VERSION. DATE AUTHOR(S) CHANGES AND COMMENTS /07/10 S. Monaco Ensure document complies with AEMO standard. Replace references to MSOR with relevant NGR & RMP references. Update terminology to correspond with current usage and definitions. Update acronyms to the current vernacular. Update images Add References to Predecessors Diagram 2.0 Remove process flows 2.18, 2.19 and 2.21 which related to an asexml transaction interface between RB and DB for confirming current FRO. This asexml transaction does not exist. Diagram 2.0 Process flow 2.12 to 2.27 which relates to an asexml transaction called Meterdatahistory, which is not operational in asexml. It is however operational as an . Diagram 4.0 Remove the information bubble that made reference to reviewing Meter Route schedule being considered as an asexml. This transaction continues to be made available via . Diagram 5.4 Remove the information bubble that made reference to reviewing Meter Time Expired notice being considered as an asexml. This transaction continues to be made available via . Diagram 13.1, 13.2A, 13.3 and 13.7 yellow change marks as agreed in IN003/09 (CR96 Minor RoLR Documentation Changes) have been included. A copy of the IN003/09 GMI is available from grcf@aemo.com.au /07/12 S. Macri IN011/12 (NECF Changes) Changes for Customer Classification /02/13 J. Luu IN029/12 Pilot Program BAU Process /01/14 D. McGowan IN004/12 Redundant Provision and minor GIP and Spec Pack changes /07/14 D. McGowan IN017/13 Gas Road Map. Service Orders Review. Remove diagrams 5.1 to 5.5, 99.3 and 99.4 and add new Process Flows diagrams 100 to 107 Doc Ref: ver JULY 2014 Page 3 of 51

4 Executive Summary The Table of Transactions version 3.0 contains: Table of Transactions, Table of Elements, List of Job Enquiry Codes, Address Elements and MIRN and Meter states. Note: The Table of Transactions is a separate document and is not included in the electronic version of this document. References to Predecessors To reflect the governance changes implemented on 1 July 2009, this document has been amended to remove references to the Victorian Energy Networks Corporation (VENCorp) and replace such references with Australian Energy Market Operator (AEMO). Where any content inadvertently refers to VENCorp it should be read as referring to AEMO. It should be noted that participant ID VENCORP remains as the participant ID for AEMO as the gas market operator in Victoria and Queensland. Doc Ref: ver JULY 2014 Page 4 of 51

5 Contents 1 Process Flow Diagrams DIAGRAM 1.0 SPECIAL METER READS DIAGRAM 1.1 SPECIAL METER READS CANCELLATION DIAGRAM 2.0 BM DATA COLLECTION AND DELIVERY (PAGE 1) DIAGRAM 2.0 BM DATA COLLECTION AND DELIVERY (PAGE 2) DIAGRAM 2.7 BASIC METER CUSTOMISATION BILL ESTIMATION DIAGRAM 4.0 BASIC METER ROUTE AND SITE INFORMATION DIAGRAM 4.1 BASIC METER ROUTE AND SITE INFORMATION DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 1) DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 2) DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 3) DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 4) DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 5) DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 6) DIAGRAM 9.1 BM DAILY CONSUMPTION ESTIMATION DIAGRAM 10.0 DATA CHANGE DIAGRAM 11.0 BASIC METER PROFILER (BMP) DIAGRAM 12.0 MIRN REQUEST DIAGRAM 13.0 CUSTOMER REQUEST TO RETAILER RETAILER OF LAST RESORT PROCESS FLOWS DIAGRAM 13.1 PRE-ROLR EVENT MONTHLY TRANSFER OF CUSTOMER DATA TO AEMO DIAGRAM 13.2 CATS PROCESSING CANCELLED AND ACCELERATED CUSTOMER TRANSFERS DIAGRAM 13.2A CATS PROCESSING ACCELERATED CUSTOMER TRANSFERS ( MOVE INS ) DIAGRAM 13.3 NON-CATS / CUSTOMER DATA EXCHANGE AND DATA GENERATION DIAGRAM 13.4 FRB GENERATED CUSTOMER LISTS FOR ROLR DIAGRAM 13.5 WHOLESALE PROCESS DIAGRAM 13.6 ROLR COMMUNICATIONS DIAGRAM 13.7 PROVISION OF ESTIMATE TRANSFER READS AND SUBSEQUENT ADJUSTMENT DIAGRAM 13.8 SERVICE ORDERS IN FLIGHT PROCESS FLOW DIAGRAMS DIAGRAM 99.1 MAINS RENEWAL Doc Ref: ver JULY 2014 Page 5 of 51

6 3.2 DIAGRAM 99.2 NETWORK BILLING DIAGRAM 99.4 MIRN STANDING DATA UPDATE DIAGRAM 99.5 METERED SUPPLY POINT COUNT UPDATE CUSTOMER CLASSIFICATION DIAGRAM 99.6 METER FIX DIAGRAM 99.7 TRANSFER (IN SITU / MOVE IN) DIAGRAM 99.8 MOVE IN (NO CHANGE IN RETAILER) DIAGRAM 99.9 CUSTOMER REQUEST TO RETAILER SERVICE ORDER PROCESS FLOWS The drawing conventions used for these diagrams: Diagram 100: Service Orders General (Simplified) Diagram 101: Retailer Initiated Service Orders Cancellation Diagram 102: Distributor Initiated Service Orders Diagram 103: Shipper Process Diagram 104: Meter Fix Request Diagram 105: Upgrade from Basic to Interval Meter Diagram 106 : Downgrade from Interval to Basic Meter For tariff D Diagram 107: Service Order Transaction Table Doc Ref: ver JULY 2014 Page 6 of 51

7 1 Process Flow Diagrams 1. These flow charts were developed as a working aid to development of the Retail Market Procedures (Victoria) and the Participant Build Packs for the purpose of identifying the necessary transactions between Retailers, Distributors and AEMO. Whilst reasonable effort has been made to ensure that these flow charts are updated and consistent with the Retail Market Procedures (Victoria) and the Participant Build Packs, there may be differences between the flow charts and the Retail Market Procedures (Victoria) and the Participant Build Packs. Where there is a difference, the Retail Market Procedures (Victoria) and the Participant Build Packs take precedence. 2. The process steps within individual business are indicative only and do not necessarily identify all required process steps nor do they mandate the use of a particular process. 3. The drawing conventions used for these diagrams are as follows: a. Multiple flow arrows exiting from a process step indicate two or more independent process flows that occur following the step. If a flow is conditional, that condition will be noted on the flow arrow. b. Alternative flows are indicated by a decision box containing a question. Conditions based on answers to the question on the flows exiting these boxes will be noted on the flow arrows. c. A fork synch bar indicates two unconditional parallel processes that will rejoin at some point with a join synch bar. A join indicates that all processes must be completed before moving on. 4. Flow arrows that cross swim lanes to connect to a start or end identifier are used to ease diagram production and do not indicate a B2B transaction. Doc Ref: ver JULY 2014 Page 7 of 51

8 1.1 DIAGRAM 1.0 SPECIAL METER READS Customer 1.1 Requests special read Retail Business (New or Existing FRO) 1.2 Requires special read 1.3 Nominate date and generate special read request 1.17 Willl Retailer carry out special read? [Yes] 1.8 Issues request to contractor for debt collection or disconnection 1.9 If debt un paid disconnect and read meter. Forward meter read and disconnection flag to DB 6.0 Customer Transfer Log Work Order Number [No] 1.13 Update New FRO CIS AEMO SpecialReadResponse SpecialReadResponse SpecialReadRequest MeterReadInputNotification 6.0 Customer Transfer Page CATSNotification AccountCreationNotification Distribution Business 1.11 Close Special Read Request and advise RB 1.20 Return Work Order Number 1.4 Log request and forward to Meter Reading Contractor 10.0 Data Change [Yes] Update MIRN and Meter Data database with disconnection status 1.16 Receive Transfer Completion Notification 1.14 Send New FRO Meter index, date and site data [Yes] BMDM 1.19 Was meter disconnected? [No] 2.0 Basic Meter Data Collection and Delivery Transfer Request? MBMR 1.10 Record reason for no access and advise DB [No] 1.20 Was it Special Final Read? [No] 1.18 Attend site: Access available [Yes] 1.5 Record reading and if requested disconnect 1.6 Perform basic high/low validation 1.7 Send read data to BMDM [Yes] 1.21 Perform Estimation Doc Ref: ver JULY 2014 Page 2 of 51

9 1.2 DIAGRAM 1.1 SPECIAL METER READS CANCELLATION Retailer 1.22 Special Read no longer required Nominate date and generate Special Read Request 1.23 Raise Special Read Cancellation request Distributor SpecialReadRequest 1.24 Log Special Read Cancellation Close Special Read Request and adv ise RB Doc Ref: ver JULY 2014 Page 3 of 51

10 1.3 DIAGRAM 2.0 BM DATA COLLECTION AND DELIVERY (PAGE 1) Customer Page Card Read Retail Business «Phone» 2.16 Call Centre Read AEMO «Mail» MeterReadInputNotification Distribution Business 2.1a Calculate validation parameters 5.1 Basic Meter Fix Basic Meter Removal & Service Orders Basic Meter Change Basic Meter Upgrade to Interval BMDM 2.1 Download reading route schedule and vlidation parameters to meter reading contractor 4.0 Basic Meter Route and Site Information Store and validate data 2.7 Obtain estimated index data as required via process 2.7 Basic Meter Customer Bill Estimation 2.8 Subtract prev ious index read from current index read A (to page 2) 1.0 Special Meter Reads MBMR 2.2 Load reading route schedules into PDEs 2.3 Follow route schedule and key reads into PDEs 1.0 Special Meter Reads , 1.19 & Upload read data 2.31 Leave card [No] 2.30 Able to read meter? [Yes] 2.4 Perform basic high/low validation, update site info as required Doc Ref: ver JULY 2014 Page 4 of 51

11 1.4 DIAGRAM 2.0 BM DATA COLLECTION AND DELIVERY (PAGE 2) Customer Page 2 Retail Business 2.13 Bill end customers 2.28 Identify any missing energy data 2.24 Process energy data 2.29 Request missing energy data 2.26 Request Energy History 2.25 Return Meter Data Response 2.23 Save energy data 2.27 Save Energy History data AEMO 11.0 Basic Meter Profiler (BMP) Basic Meter Profiler (BMP) Distribution Business MeterDataMissingNotification MeterDataNotification (2nd tier) «asexml (CSV)» MeterDataResponse MeterDataResponse MeterDataMissingNotification Request Gas History Data «asexml (CSV)» «fax or » MeterDataNotification MeterDataHistoryResponse «asexml (CSV)» « (CSV)» 2.15 Calculate bill/duos BMDM 2.22 Process Energy Data Response Metric Data? [Yes] 2.10 Apply PCF A (from page 1) [No] 2.9 Conv ert imp to metric 2.11 Apply average heating v alue 2.12 Provide Energy and/or flow data and or index readings MBMR 9.1 BM Daily Consumption Estimation 10.0 Data Change Doc Ref: ver JULY 2014 Page 5 of 51

12 1.5 DIAGRAM 2.7 BASIC METER CUSTOMISATION BILL ESTIMATION Customer Retail Business Provide Customer Characterisation AEMO Provide EDD Provide ave. daily flow. weighted Heating Values Distribution Business AmendMeterRouteDetails «asexml (CSV)» «MIBB» «MIBB» BMDM 2.0 Basic Meter Data Collection and Delivery consumption history >1yr? [No] Determine ave BL & av e TSF from Customer Characterisation [Yes] Estimate Daily Consumed Energy using BL & TSF Conv ert Estimated Consumed Energy to flow 2.0 Basic Meter Data Collection and Delivery MBMR Doc Ref: ver JULY 2014 Page 6 of 51

13 1.6 DIAGRAM 4.0 BASIC METER ROUTE AND SITE INFORMATION Customer 3.1(a) Customer Requests changes to address information (eg - Lot number to Hse Number) 3.1(b) Customer Requests changes to site Information (eg - Access to Meter) Retail Business 4.3 Consultation on Route/Route Changes 4.5 Record annual meter read schedule 4.4 Record route changes 3.2(a) Retailer records and issues request to update address information 3.2(b) Retailer records and issues request to update Site Information AEMO AmendMeterRouteDetails « (CSV)» AmendMeterRouteDetails AmendMeterRouteDetails Annual meter read schedule «Phone, fax, » « (CSV), web» Distribution Business 5.3 Basic Meter Upgrade to Interval Update Meter Data Database 3.3 Receives and acknowledges change to Site Information BMDM 5.1 Basic Meter Fix Analyse and optimise routes 4.2 Update/Create route schedules based on outputs 2.0 Basic Meter Data Collection and Delivery MBMR 3.5 Meter Reading Service Provider requests changes to site Information (eg - Access to Meter, Address details) Doc Ref: ver JULY 2014 Page 7 of 51

14 1.7 DIAGRAM 4.1 BASIC METER ROUTE AND SITE INFORMATION Customer 3.1c Customer request change to contact details 3.1d Customer request mov e in and prov ides contact Details Retail Business 3.2c Retailer records details and issues request to update contact details Distribution Business AmendCustomerDetails «<asexmlcsv>» 3.6 Update Customer contact Database 3.3 Reciev es and acknow ledges change to customer contact details Doc Ref: ver JULY 2014 Page 8 of 51

15 1.8 DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 1) Customer Provide Implicit Informed Consent Further processing as per problem notice handling, refer to Page 6 Page 1 New FRO 12.0 MIRN Request Submit Transfer Request to CATS Process Response to Transfer Request [If Special Read is required] 1.0 Special Meter Reads Receive Problem Notice AEMO CATSChangeRequest Initiate Transfer Transaction CATSChangeResponse Notify New Retailer Request Standing Data Receive Standing Data I (to page 4) Notify Affected Parties CATSNotification Is it move-in transfer? [No] [Yes] D (to page 4) B (to page 3) CATSChangeAlert Generate Problem Notice Current FRO CATSChangeRequest «manual process» Receive Notice of Transfer A (to page 2) TPO CATSDataRequest CATSChangeResponse Receive Notice of Transfer NACK CATSNotification End Process NACK [Yes] Distributor Deliver Standing Data Process Response to Standing Data Is it re Retrospective Transfer & no reading for that date? [No] Put on Notice to Deliver Energy for This Site in the Allowable Period End Process Doc Ref: ver JULY 2014 Page 9 of 51

16 1.9 DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 2) Customer Page 2 New FRO Consider Valid Objection CATSNotification AEMO B (to page 3) Validate Objection Register Objection Notify Objecting Party Notify Affected Participants C (to page 3) [No] CATSObjectionRequest CATSObjectionResponse Current FRO Object? [Yes] Enter Objection in CATS Process Objection Response G (to page 3) A (from page 1) CATSNotification TPO Distributor Receive Notice of Objection Doc Ref: ver JULY 2014 Page 10 of 51

17 1.10 DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 3) Customer Page 3 New FRO B (from page 2) Receive Notice of Objection Withdrawal H (from page 5) Receive Cancelled Txf Notice Liase/Notify with Customer CATSNotification CATSNotification AEMO Current FRO C (from page 2) G (from page 2) Resolve Objection Monitor Objection Period Clear Objection CATSObjectionWithdrawal CATSNotification [objection period expired] Send Notice of Objection Withdrawal CATSNotification Receive Notice of Objection Withdrawal Any Objections? [Yes] [No] D (to page 4) Cancel Transfer Request Send Cancelled Txf Notice CATSNotification CATSNotification Receive Cancelled Txf Notice End Process TPO Receive Notice of Objection Withdrawal Receive Cancelled Txf Notice End Process Distributor Receive Notice of Objection Withdrawal Receive Cancelled Txf Notice Remove from the Transfer Queue to Deliver Energy Doc Ref: ver JULY 2014 Page 11 of 51

18 1.11 DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 4) Customer 1.12 Page 4 New FRO Receive Status Update Update CIS E (from page 5) End Process AEMO D (from page 3) Set Transfer Status to Pending CATSNotification Send Status Change Notice Wait For Final Read Data Load Actual Meter Read Data Is Read an Actual [Yes] Read? Is Read Date OK for Transfer? I (from page 1) [Yes] [Yes] Has Standing Data been provided? [Yes] Update Status to Completed CATSNotification Notify Affected Participants Update Meter Register End Process D (from page 1 and 3) Current FRO CATSNotification Receive Status Update 11.0 Basic Meter Profiler (BMP) [No] [No] [No] [No] F (to page 5) CATSNotification Issue Final Bill End Process TPO CATSNotification CATSNotification Update DUoS/TUoS Billing End Process Distributor Receive Status Update Update Data Access Controls 1.0 Special Meter Reads End Process Doc Ref: ver JULY 2014 Page 12 of 51

19 Customer DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 5) AEMOwill automatically cancel the Transfer Request if a New Transfer Date or a Cancellation is not received within 10 business days. Page 5 New FRO AEMO F (from page 4) Current FRO Is it re Retrospective Transfer [Yes] H (to page 3) [No] [Yes] Has read fail notice been issued? H (to page 3) [No] Notify Late Meter Read CATSDataRequest Receive Notice of Read Failure Exception Processing CATSDataRequest Notify New Retailer Of final Read Failure New Transfer Date or Cancel? [Cancel] CATSChangeWithdrawal Set Transfer Status to Cancelled Receive Transfer Cancellation Notice CATSNotification Notify Affected Participants CATSNotification Receive Transfer Cancellation Notice End Process CATSChangeRequest [New transfer date] Update Status with new Transfer Date End Process Process Response CATSChangeResponse Receive Notice Notify Affected Participants CATSNotification E (to page 4) TPO CATSDataRequest CATSNotification CATSNotification Distributor Receive Notice of Read Failure Receive Transfer Cancellation Notice End Process Receive Notice Doc Ref: ver JULY 2014 Page 13 of 51

20 1.13 DIAGRAM 6.0 CUSTOMER TRANSFER (PAGE 6) Customer Page 6 New FRO Receiv e Problem Notice AEMO CATSChangeAlert Pass Problem CATSChangeAlert Notice to New Retailer CATSChangeAlert Current FRO «manual process» Generate Problem Notice TPO Generate Problem Notice Distributor Generate Problem Notice Doc Ref: ver JULY 2014 Page 14 of 51

21 1.14 DIAGRAM 9.1 BM DAILY CONSUMPTION ESTIMATION Customer This diagram is for AEMO internal use only. Not to be used for participant design Retail Business AEMO [Yes] 11.0 Basic Meter Profiler (BMP) 11.0 Basic Meter Profiler (BMP) Consumed Energy Available? [No] Estimate Daily Consumed Energy using BL & TSF NMIStandingDataUpdateNotification Distribution Business See also diagram 11.0 BMP ( > 11.17) Prov ide BL & TSF BMDM MBMR Doc Ref: ver JULY 2014 Page 15 of 51

22 1.15 DIAGRAM 10.0 DATA CHANGE Customer 10.1 Customer complaint re bill Retail Business [Yes] 10.2 Consider complaint - data problem? [No] 10.3 Request data quality confirmation and provide clarifiying Information (where applicable) 10.6 Manage customer / complaint AEMO Distribution Business MeterDataVerifyRequest MeterDataVerifyResponse BMDM [Special Read] 10.4 Initiate Special Read 10.8 Alternative re-estimate or special read required? [Alternative re-estimate] 10.7 Carry out alternativ e re-estimation 10.5 Inform RB of re-estimation or special read result [If new energy data is to be supplied] 2.0 Basic Meter Data Collection and Delivery MBMR 1.0 Special Meter Reads Doc Ref: ver JULY 2014 Page 16 of 51

23 1.16 DIAGRAM 11.0 BASIC METER PROFILER (BMP) Customer Retail Business AEMO Generate values/site without reading Meter Data Store 11.4 Apply UAFG Benchmark 11.9 MIBB Calculate EDD Values Monitor Energy Data 6.0 Customer Transfer Aggregate Energy Readings by RB by DB 11.8 Settlements Process [Yes] Update Meter Register with BL and TSF Send Response to BL and TSF by Site Update 11.2 Are all MIRNs present? 11.6 Apply Profile to Aggregated Energy Meter Data Store NMIStandingDataUpdateNotification NMIStandingDataUpdateResponse Request Missing Energy Data [No] 11.1 Validate Data 11.7 Profile Preparation (PPS) Distribution Business Deliver BL and TSF by Site Process Response to BL and TSF by Site Update MeterDataResponse MeterDataNotification (2nd tier) BMDM MeterDataMissingNotification 2.0 Basic Meter Data Collection and Delivery Basic Meter Data Collection and Delivery MBMR Doc Ref: ver JULY 2014 Page 17 of 51

24 1.17 DIAGRAM 12.0 MIRN REQUEST Customer 12.2 Provide Explicit Informed Consent, MIRN or Address Retail Business 12.3 Initiate MIRN Discov ery Transaction 12.8 Use Data Contact DB for Details [No] 12.9 Can RB resolve? [Yes] AEMO NMIDiscoveryResponse/ NMIStandingDataResponse NMIDiscoveryRequest/ NMIStandingDataRequest NMIDiscoveryResponse/ NMIStandingDataResponse MIDiscoveryResponse/ NMIStandingDataResponse «Phone, fax, » Distribution Business Manage Query on Failed Searches Return error [No] 12.5 Single match on Address/MIRN? [Yes] 12.6 Prov ide MIRN Data [If additional data to be supplied] 12.7 Provide Additional MIRN Data BMDM MBMR Doc Ref: ver JULY 2014 Page 18 of 51

25 1.18 DIAGRAM 13.0 CUSTOMER REQUEST TO RETAILER Identifying a Gas Customer s Current Retailer (Meter and/or up stand removed) Business Day 1 Day 3 Day 8 Retailer Retailer Distributor Distributor FRO FRO AEMO AEMO (Not (Not FRO) FRO) Customer Customer 1. Customer calls a RB who is not the FRO to arrange SO. 2. Receives call from customer. Advises customer they are not the RB for that address. Take customer's details. No SO details are taken. 3. RB B2B Contact (Primary/Secondary) send AEMO Helpdesk for Identify FRO. 4. Helpdesk logs call and searches meter register for current FRO. 5. AEMO Pass customer details to FRO and closes call. 7. Customer happy. End. 6. FRO contact customer and collects SO details. 8. Organise Service Order (if required). 9. Receive Service order request and complete. Doc Ref: ver JULY 2014 Page 19 of 51

26 2 RETAILER OF LAST RESORT PROCESS FLOWS 2.1 DIAGRAM 13.1 PRE-ROLR EVENT MONTHLY TRANSFER OF CUSTOMER DATA TO AEMO Doc Ref: ver JULY 2014 Page 20 of 51

27 2.2 DIAGRAM 13.2 CATS PROCESSING CANCELLED AND ACCELERATED CUSTOMER TRANSFERS Doc Ref: ver JULY 2014 Page 21 of 51

28 2.3 DIAGRAM 13.2A CATS PROCESSING ACCELERATED CUSTOMER TRANSFERS ( MOVE INS ) Doc Ref: ver JULY 2014 Page 22 of 51

29 2.4 DIAGRAM 13.3 NON-CATS / CUSTOMER DATA EXCHANGE AND DATA GENERATION Doc Ref: ver JULY 2014 Page 23 of 51

30 2.5 DIAGRAM 13.4 FRB GENERATED CUSTOMER LISTS FOR ROLR Doc Ref: ver JULY 2014 Page 24 of 51

31 2.6 DIAGRAM 13.5 WHOLESALE PROCESS Doc Ref: ver JULY 2014 Page 25 of 51

32 2.7 DIAGRAM 13.6 ROLR COMMUNICATIONS Doc Ref: ver JULY 2014 Page 26 of 51

33 2.8 DIAGRAM 13.7 PROVISION OF ESTIMATE TRANSFER READS AND SUBSEQUENT ADJUSTMENT Doc Ref: ver JULY 2014 Page 27 of 51

34 2.9 DIAGRAM 13.8 SERVICE ORDERS IN FLIGHT Doc Ref: ver JULY 2014 Page 28 of 51

35 3 PROCESS FLOW DIAGRAMS 3.1 DIAGRAM 99.1 MAINS RENEWAL Retailer Record impacted MIRNs FieldWorkNotification « (CSV)» Distributor Notify Retailer of impacted MIRNs Identify maintenance w ork requirement Identify impacted MIRNs Notify impacted customers as required Doc Ref: ver JULY 2014 Page 29 of 51

36 3.2 DIAGRAM 99.2 NETWORK BILLING Retailer Record Network DUoS Billing Details data NetworkDUoSBillingNotification «asexml (CSV)» Distributor Collate Network DUoS Billng Details data [disagreement with billing details] Issue a Dispute NetworkDUoSBillingNotification «asexml (CSV)» Rev iew Network DUoS Billing Details and Propose a Resolution Rev iew Proposed Dispute Resolution NetworkDUoSBillingNotification «asexml (CSV)» NetworkDUoSBillingNotification «asexml (CSV)» Record Payment Details Doc Ref: ver JULY 2014 Page 30 of 51

37 3.3 DIAGRAM 99.4 MIRN STANDING DATA UPDATE Retailer Update MIRN Standing Data Distributor « » Update MIRN Standing Data Notify Retailer of change Doc Ref: ver JULY 2014 Page 31 of 51

38 3.4 DIAGRAM 99.5 METERED SUPPLY POINT COUNT UPDATE AEMO Update Metered Supply Points Count Distributor MeteredSupplyPointsCountUpdate Prov iding Metered Supply Points Count Doc Ref: ver JULY 2014 Page 32 of 51

39 4 CUSTOMER CLASSIFICATION 4.1 DIAGRAM 99.6 METER FIX Customer Classification AGREED - Transfer (Insitu/MoveIn) AEMO Distributor Retailer Request MIRN Discovery/Standing Data Validate request and send MIRN Discovery Response Receive MIRN Discovery Responsse and update system(s) Raise Transfer Request Receive transfer and Issue market notifications Receive Completion and ACN and update system(s) Generate Account Creation Notification Receive Completion and update system Send Notifiction transfer Complete Has the primary use of the property changed? No End Yes Generate Amend Route/Site Address Details Transaction Receive transaction with Customer Classification Code Where CCC is BUS Update Customer Threshold Code ( LOW, MED, HIGH Send update Receive Amend Route/Site Address Details transaction and update system(s) Generate Amend Route/ Site Address Details Transaction Doc Ref: ver JULY 2014 Page 33 of 51

40 4.2 DIAGRAM 99.7 TRANSFER (IN SITU / MOVE IN) Customer Classification AGREED - Transfer (Insitu/MoveIn) AEMO Distributor Retailer Request MIRN Discovery/Standing Data Validate request and send MIRN Discovery Response Receive MIRN Discovery Responsse and update system(s) Raise Transfer Request Receive transfer and Issue market notifications Receive Completion and ACN and update system(s) Generate Account Creation Notification Receive Completion and update system Send Notifiction transfer Complete Has the primary use of the property changed? No End Yes Generate Amend Route/Site Address Details Transaction Receive transaction with Customer Classification Code Where CCC is BUS Update Customer Threshold Code ( LOW, MED, HIGH Send update Receive Amend Route/Site Address Details transaction and update system(s) Generate Amend Route/ Site Address Details Transaction Doc Ref: ver JULY 2014 Page 34 of 51

41 4.3 DIAGRAM 99.8 MOVE IN (NO CHANGE IN RETAILER) Customer Classification AGREED - Move In (Same Retailer) Retailer Receive Customer request for Move-in on property already with the Retailer Has the primary use of the property changed? No Yes Generate Amend Route/Site Address Details Transaction Receive Amend Route/Site Address Details transaction and update system(s) End Receive transaction with updated Customer Classification Code Distributor Where CCC is BUS Update Customer Threshold Code ( LOW, MED, HIGH Send update Generate Amend Route/Site Address Details Transaction Doc Ref: ver JULY 2014 Page 35 of 51

42 4.4 DIAGRAM 99.9 CUSTOMER REQUEST TO RETAILER Customer Classification AGREED - Request from Customer to RB Retailer Receive Customer request Has the primary use of the property changed? No Yes Generate Amend Route/Site Address Details Transaction Receive Amend Route/Site Address Details transaction and update system(s) End Receive transaction with updated Customer Classification Code Distributor Where CCC is BUS Update Customer Threshold Code ( LOW, MED, HIGH Send update Generate Amend Route/Site Address Details Transaction Doc Ref: ver JULY 2014 Page 36 of 51

43 5 SERVICE ORDER PROCESS FLOWS 5.1 The drawing conventions used for these diagrams: The drawing conventions used for these diagrams are as follows: N.N Activity Decision Decision/Data Transfer Description Process Terminator/ Inter-process Link On Page Ref Process Close Process Start Wait Parallel Mode asexml Message Description Association Notes Doc Ref: ver JULY 2014 Page 37 of 51

44 5.2 Diagram 100: Service Orders General (Simplified) Diagram 100: Service Orders General (Simplified) SA Process Ref: PF (B2B) REQ5B/MIRN 1 AEMO Distributor Retailer Customer From or or as applicable 1a. Request a Service 3. Receive Service Order Request & Validate 1. Request a Service ServiceOrderRequest [actiontype= New ] <<asexml>> #1 No 4. Valid Service Order Request? Go To Yes Where rejected, Retailer takes appropriate action e.g. Initiate new service order request and current process ends. 2. Send Service Order (SO) C-K 5. Send Validation Outcome Yes Transaction Acknowledgment <<asexml>> 9. Log Service Order & Send Response 12. Was Additional or Alternative Work Completed? 6. Receive Acceptance/ Rejection From No 10. Action Service Order 7. Was Service Order Accepted? No This process wasn t reviewed as part of IN017/13. IN027/13 has been created to raise awareness that when Meter Data Delivery process is reviewed revisit this process flow diagram Yes If required by service requested ServiceOrderResponse [responsetype= Initial ] <<asexml>> #2 Go To or as applicable 11. Has SO been Completed? Yes Go To 2.0 Meter Data Delivery 8. Receive Service Order Response (Initial) No Yes Wait for service order response Closure Up to 5 BD From Expected Completion of Step Send Service Order Response Up to 5 BD from Expected Completion of Step Does SO Type Require Delivery of Meter Data? ServiceOrderResponse [responsetype= Closure ] <<asexml>> Go To or #3 Yes as applicable No 14. Upgrade or Downgrade? 17. Does SO Require Notification to AEMO? No 15. Receive Service Order Response (Closure) No Yes 18. Send Notification to AEMO <<asexml>> #4 19. Action Notification #1, 2, 3 & 4 Refer to Diagram 107 for the transactions involved Doc Ref: ver JULY 2014 Page 38 of 51

45 5.3 Diagram 101: Retailer Initiated Service Orders Cancellation Diagram 101: Retailer Initiated Service Orders Cancellation SA Process Ref: PF (B2B) REQ 7 Distributor Retailer Customer 3. Receive Service Order Cancellation & Validate 1. Request a Service order to be Cancelled 1a. Request a Service order to be Cancelled ServiceOrderRequest [actiontype= Cancel ] <<asexml>> #1 No 4. Valid Service Order Cancel Request? 5. Send Validation Outcome 2. Send Service Order (SO) Cancellation C-K Yes Transaction Acknowledgment <<asexml>> Same day cancellations must also be phoned through 10. Attempt to Cancel Initial SO Request 6. Receive Acceptance/ Rejection No 7. Was SO Cancellation Accepted? 11. Can Initial SO be Cancelled? No Yes Yes Where cancellation is rejected the original SO will continue to be actioned Retailer takes appropriate action 8. Receive Service Order Response ServiceOrderResponse [responsetype=closure] <<asexml>> #3 12. Send Service Order Response 9. Update System Data Up to 5 BD from Expected Completion of Step 10 Where cancellation is rejected the original SO will continue to be actioned #1 & 3 Refer to Diagram 107 Table for the transactions involved Doc Ref: ver JULY 2014 Page 39 of 51

46 5.4 Diagram 102: Distributor Initiated Service Orders Diagram 102: Distributor Initiated Service Orders SA Process Ref: PF (B2B) REQ 6 AEMO Distributor Retailer Distributor initiated work at the site requires update to retailer/aemo This includes Time Expired Meters From Complete Field Work 3. Receive & Validate Service Order Response (C-K) ServiceOrderResponse [responsetype=closure] <<asexml>> #3 2. Send Service Order Response (C-K) This process wasn t reviewed as part of IN017/13. IN027/13 has been created to raise awareness that when Meter Data Delivery process is reviewed revisit this process flow diagram Go To 2.0 Meter Data Delivery 4. Update System Data Yes 5. Does SO Require Notification to AEMO? 6. Does SO Type Require Delivery of Meter Data? No No Yes 7. Send Notification to AEMO <<asexml>> #4 8. Action Notification #3 & 4 Refer to Diagram 107 Table for the transactions involved Doc Ref: ver JULY 2014 Page 40 of 51

47 5.5 Diagram 103: Shipper Process Diagram 103: Shipper Process SA Process Ref: MIRN1.1 Part 2 Distributor Retailer Customer From or or as applicable 1a. Request a Service From or as applicable 1. Request a Service Phone 2. Prepare Shipper Form 1b. Request a Shipper From or as applicable The request for work Form is different for each DB 6. Receive Validation Outcome 3. Receive & Validate Shipper Form If rejected, resolve issues with customer and resend Shipper Form (potentially amended) Phone/Fax/ 11. Advise Customer of Costs / Conditions & Send Offer 10. Receive Shipper Response 5. Send Validation Outcome No 4. Valid Shipper Request? No Yes 12. Accept Cost / Conditions? Yes /Fax 13. Receive Signed Agreement 8. Does the Site Match Shipper Form? 7. Review Field Requirements and/or Visit Site No Yes 15.Is SO Required for the Service by the Applicable DB? No Tariff V requires response within 10 business days from request received otherwise date agreed by the customer Yes /Fax 9. Complete Shipper Evaluation Form & Send Response Go To 100.1a 14. Receive Signed Shipper Acceptance Go To or or or as applicable Notes: Service Order Enquiry Code MAP, MFX, MRT, RSR, SCR, UMS, USR Doc Ref: ver JULY 2014 Page 41 of 51

48 5.6 Diagram 104: Meter Fix Request Diagram 104: Meter Fix Request SA Process Ref: NA Retailer Customer 1. Request Meter Fix as Service & Fitting Lines Completed 2.Simple Meter Type Installation? No Yes 3.Is a Shipper form required? 5. Customer Quotes CoC & PLN 4. Request Customer to Provide CoC & PLN No No 6. Valid CoC & PLN? Yes Go To 100.1a 7. Request Customer to Provide Start Work Notice No & PLN 8. Customer Quotes Start Work Notice No & PLN Yes Go To From Doc Ref: ver JULY 2014 Page 42 of 51

49 5.7 Diagram 105: Upgrade from Basic to Interval Meter Diagram 105: Upgrade from Basic to Interval Meter SA Process Ref: PF (B2B) MR12 AEMO Distributor Retailer Customer Go To 103.1b 3. Distributor identifies need for Basic to Interval Meter Upgrade 1. Request Upgrade to Interval Meter 2. Retailer identifies need for Basic to Interval Meter Upgrade 4.Confirm Receipt of Service Order 6. Install Data Logger and/or Comms GIP 126 Go To Go To 103.1a 9. Receive & Validate MR Application 7. Prepare & Send Meter Registration (MR) Application GIP 126 From Confirm Receipt of Signed Acceptance 10. MR Application Valid? If required by service requested From Amend & Resubmit MR Application No Yes 13. Commission Interval Meter in Association with MDP 12. Receive Notated MR Application GIP Update Meter Register to Pending Interval Metering & Send Notated MR Application From Complete & Send Meter Installation Parameter (MIP) Notice 18. Receive Completion Advice or ServiceOrderResponse 17. Update System Send Completion Advice to Retailer 16. Receive Notated MIP Notice 15. Update Meter Register to Active Interval Metering & Send Notated MIP Notice Doc Ref: ver JULY 2014 Page 43 of 51

50 5.8 Diagram 106 : Downgrade from Interval to Basic Meter For tariff D Diagram 106 : Downgrade from Interval to Basic Meter For tariff D SA Process Ref: PF (B2B) MR14 AEMO Distributor Retailer Customer Go To 103.1b 3. Distributor identifies need for Interval to Basic Meter Downgrade 1. Request Downgrade to a Basic Meter 2. Retailer identifies need for Interval to Basic Meter Downgrade 4. Confirm Receipt of Service Order 6. Prepare & Send Meter Installation Parameter change Notice (MIP) GIP 134 Go To Go To 103.1a GIP Receive & Validate MIP 5. Confirm Receipt of Signed Acceptance From Amend & Resubmit MIP No 9. MIP Valid? From Yes From Update System and set Meter to Basic 11. Receive Notated MIP 10. Update Meter Register to Basic Metering & Send Notated MIP 14. Receive SO Completion Advice ServiceOrderResponse 13. Remove Data Logger and/or Comms Doc Ref: ver JULY 2014 Page 44 of 51

51 5.9 Diagram 107: Service Order Transaction Table Diagram 107: Service Order Transaction Table #1 Service Orders Request C-K #2 Service Order Response C-K (Initial) #3 Service Order Response C-K (Final) #4 Status Change Response GIP 87 - Meter Fix Request (JEC = MFX) GIP Meter Change Request (JEC = MCH) GIP 87A - Meter Fix Request Response GIP 92 - Meter Fix Completed GIP 94 - Meter Fix Notification GIP 101A - Meter Change Request Response GIP 93 - No Access to Complete Meter Fix GIP No Access to Complete Meter Change GIP Meter Change Completed GIP Meter Upgrade Completed GIP Meter Removal Request (JEC = MRM) GIP 151A - Meter Removal Request Response GIP No Access to Complete Meter Removal GIP MIRN Status Update Notification GIP Meter Removal Completed GIP Service Connection Request (JEC = SCR) GIP Service Disconnection Request (JEC = SDR) GIP Service Orders for Priority C-K (JEC = All JEC's) GIP Relocate Service Request (JEC = RSR) GIP Upgrade Service Size Request (JEC = USR) GIP Upgrade Meter Size Request (JEC = UMS) GIP 310A - Service Connection Request Response GIP 312A - Service Disconnection Request Response GIP 314A - Service Orders for Priority C-K Response GIP 316A - Relocate Service Request Response GIP 318A - Upgrade Service Size Request Response GIP 320A - Upgrade Meter Size Request Response GIP Service Connection Complete GIP Service Disconnection Complete GIP Service Orders Completed for Priority A-K GIP Relocate Service Complete GIP Upgrade Service Size Complete GIP Upgrade Meter Size Complete GIP MIRN Status Update Notification JEC = Job Enquiry Doc Ref: ver JULY 2014 Page 45 of 51