Upload
others
View
10
Download
0
Embed Size (px)
Citation preview
PARTICIPANT BUILD PACK 1
PROCESS FLOW DIAGRAMS VER 3.3
TABLE OF TRANSACTIONS VER 3.2
PREPARED BY: MARKET DEVELOPMENT
DOCUMENT REF: 305196
VERSION: 3.4
DATE: 01 JULY 2014
FINAL :
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 2 of 51
Document Approval and Acceptance
AEMO Approval This document has been prepared by:
NAME: DANNY MCGOWAN
Position: Principal Regulatory Analyst
Signature: Date:
This document has been reviewed and conforms with the authorised changes to the Gas Interface Protocol:
NAME: PETER ALBERTS
Position: Senior Manager, Gas Retail Market Development
Signature: Date:
This document has been reviewed and conforms to AEMO’s regulatory obligations:
NAME: TERRY GRIMWADE
Position: Executive General Manager, Market Development
Signature: Date:
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 3 of 51
Version History
VERSION. DATE AUTHOR(S) CHANGES AND COMMENTS
3.0 01/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 email.
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 email.
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 email.
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 [email protected]
3.1 30/07/12 S. Macri IN011/12 (NECF Changes)
Changes for Customer Classification
3.2 01/02/13 J. Luu IN029/12 Pilot Program BAU Process
3.3 01/01/14 D. McGowan IN004/12 – Redundant Provision and minor GIP and Spec Pack changes
3.4 01/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
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 4 of 51
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.
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 5 of 51
Contents
1 Process Flow Diagrams ................................................................................... 7
1.1 DIAGRAM 1.0 – SPECIAL METER READS ............................................................... 2
1.2 DIAGRAM 1.1 – SPECIAL METER READS CANCELLATION ................................... 3
1.3 DIAGRAM 2.0 – BM DATA COLLECTION AND DELIVERY (PAGE 1) ...................... 4
1.4 DIAGRAM 2.0 – BM DATA COLLECTION AND DELIVERY (PAGE 2) ...................... 5
1.5 DIAGRAM 2.7 – BASIC METER CUSTOMISATION BILL ESTIMATION ................... 6
1.6 DIAGRAM 4.0 – BASIC METER ROUTE AND SITE INFORMATION ........................ 7
1.7 DIAGRAM 4.1 – BASIC METER ROUTE AND SITE INFORMATION ........................ 8
1.8 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 1) ................................................ 9
1.9 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 2) .............................................. 10
1.10 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 3) .............................................. 11
1.11 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 4) .............................................. 12
1.12 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 5) .............................................. 12
1.13 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 6) .............................................. 14
14
1.14 DIAGRAM 9.1 – BM DAILY CONSUMPTION ESTIMATION .................................... 15
1.15 DIAGRAM 10.0 – DATA CHANGE ........................................................................... 16
1.16 DIAGRAM 11.0 – BASIC METER PROFILER (BMP) ............................................... 17
1.17 DIAGRAM 12.0 – MIRN REQUEST ......................................................................... 18
1.18 DIAGRAM 13.0 – CUSTOMER REQUEST TO RETAILER ...................................... 19
2 RETAILER OF LAST RESORT PROCESS FLOWS .......................................20
2.1 DIAGRAM 13.1 – PRE-ROLR EVENT – MONTHLY TRANSFER OF CUSTOMER DATA TO AEMO ................................................................................................................ 20
2.2 DIAGRAM 13.2 – CATS PROCESSING – CANCELLED AND ACCELERATED CUSTOMER TRANSFERS ...................................................................................... 21
2.3 DIAGRAM 13.2A – CATS PROCESSING – ACCELERATED CUSTOMER TRANSFERS (‘MOVE INS’) ............................................................................................................ 22
2.4 DIAGRAM 13.3 – NON-CATS / CUSTOMER DATA EXCHANGE AND DATA GENERATION ......................................................................................................... 23
2.5 DIAGRAM 13.4 – FRB GENERATED CUSTOMER LISTS FOR ROLR ................... 24
2.6 DIAGRAM 13.5 – WHOLESALE PROCESS ............................................................ 25
2.7 DIAGRAM 13.6 – ROLR COMMUNICATIONS ......................................................... 26
2.8 DIAGRAM 13.7 – PROVISION OF ESTIMATE TRANSFER READS AND SUBSEQUENT ADJUSTMENT ......................................................................................................... 27
2.9 DIAGRAM 13.8 – SERVICE ORDERS IN FLIGHT ................................................... 28
3 PROCESS FLOW DIAGRAMS .......................................................................29
3.1 DIAGRAM 99.1 – MAINS RENEWAL ....................................................................... 29
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 6 of 51
3.2 DIAGRAM 99.2 – NETWORK BILLING .................................................................... 30
3.3 DIAGRAM 99.4 – MIRN STANDING DATA UPDATE ............................................... 31
3.4 DIAGRAM 99.5 – METERED SUPPLY POINT COUNT UPDATE ............................ 32
4 CUSTOMER CLASSIFICATION .....................................................................33
4.1 DIAGRAM 99.6 – METER FIX .................................................................................. 33
4.2 DIAGRAM 99.7 – TRANSFER (IN SITU / MOVE – IN) ............................................. 34
4.3 DIAGRAM 99.8 – MOVE IN (NO CHANGE IN RETAILER) ...................................... 35
4.4 DIAGRAM 99.9 – CUSTOMER REQUEST TO RETAILER ...................................... 36
5 SERVICE ORDER PROCESS FLOWS ..........................................................37
5.1 The drawing conventions used for these diagrams: .................................................. 37
5.2 Diagram 100: Service Orders General (Simplified) ................................................... 38
5.3 Diagram 101: Retailer Initiated Service Orders Cancellation .................................... 39
5.4 Diagram 102: Distributor Initiated Service Orders ..................................................... 40
5.5 Diagram 103: Shipper Process ................................................................................. 41
5.6 Diagram 104: Meter Fix Request .............................................................................. 42
5.7 Diagram 105: Upgrade from Basic to Interval Meter ................................................. 43
5.8 Diagram 106 : Downgrade from Interval to Basic Meter For tariff D .......................... 44
5.9 Diagram 107: Service Order Transaction Table ........................................................ 45
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 7 of 51
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.
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 2 of 51
1.1 DIAGRAM 1.0 – SPECIAL METER READS
Customer
Retail Business
(New or Existing FRO)
AEMO
Distribution
Business
BMDM
MBMR
1.1 Requests
special read
1.2 Requires special
read
1.11 Close Special
Read Request and
adv ise RB
1.3 Nominate date and
generate special read
request 1.17 Will l Retailer
carry out special
read?
1.8 Issues request to
contractor for debt
collection or
disconnection
1.4 Log request and
forward to Meter Reading
Contractor
1.18 Attend site:
Access available
1.10 Record reason for no
access and adv ise DB1.5 Record reading and if
requested disconnect
1.6 Perform basic
high/low v alidation 1.7 Send read data to
BMDM
1.19 Was meter
disconnected?
1.9.1 Update MIRN and Meter
Data database with
disconnection status
1.14 Send New FRO
Meter index, date and
site data
1.15 Transfer Request?
1.9 If debt un paid
disconnect and read
meter. Forward meter
read and disconnection
flag to DB
1.13 Update New
FRO CIS
10.0 Data Change - 10.4
[No]
1.16 Receiv e Transfer
Completion
Notification
6.0 Customer Transfer
Page 4 - 6.4.12
1.20 Return Work
Order Number
1.21 Log Work Order
Number
6.0 Customer Transfer -
6.1.19
2.0 Basic Meter Data
Collection and Delivery -
2.6
1.20 Was it Special
Final Read ?
1.21 Perform Estimation
SpecialReadRequest
«aseXML»
[Yes]
[No]
[Yes]
[No]
AccountCreationNotification
«aseXML»
[Yes]
SpecialReadResponse
«aseXML»
[Yes]
[Yes][No]
MeterReadInputNotification
«aseXML»
SpecialReadResponse
«aseXML»
CATSNotification
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 3 of 51
1.2 DIAGRAM 1.1 – SPECIAL METER READS CANCELLATION
1.22 Special Read
no longer required
Nominate
date and
generate
Special
Read
Request
1.23 Raise Special
Read Cancellation
request
1.24 Log Special
Read Cancellation
Close
Special
Read
Request
and
adv ise RB
Distributor
Retailer
SpecialReadRequest
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 4 of 51
1.3 DIAGRAM 2.0 – BM DATA COLLECTION AND DELIVERY (PAGE 1)
2.2 Load reading route
schedules into PDEs
2.17 Card Read
2.16 Call Centre
Read
2.3 Follow route schedule
and key reads into PDEs
2.4 Perform basic
high/low v alidation,
update site info as
required
2.1 Download reading
route schedule and
v lidation parameters to
meter reading contractor
2.5 Upload read data
2.8 Subtract prev ious
index read from current
index read
Retail
Business
Customer
2.1a Calculate v alidation
parameters
A (to page 2)
AEMO
Distribution
Business
BMDM
MBMR
4.0 Basic Meter Route and Site
Information - 4.2
5.1 Basic Meter Fix -
5.1.12
1.0 Special Meter
Reads - 1.9.1, 1.19 &
1.21
2.7 Obtain estimated index
data as required via
process 2.7 Basic Meter
Customer Bill Estimation
2.6 Store and v alidate data
Page 1
1.0 Special Meter Reads -
1.15
5.5 Basic Meter
Removal - 5.5.11 &
5.5.13 99.3 Service
Orders - 99.3.9
2.30 Able to
read meter?
2.31 Leav e card
5.2 Basic Meter
Change - 5.2.9
5.3 Basic Meter
Upgrade to
Interval - 5.3.10
«Phone»
«Mail» MeterReadInputNotification
«aseXML»
[Yes][No]
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 5 of 51
1.4 DIAGRAM 2.0 – BM DATA COLLECTION AND DELIVERY (PAGE 2)
2.9 Conv ert imp to
metric
2.10 Apply PCF
2.12 Prov ide Energy and/or flow data and or index readings
2.15 Calculate
bill/DUoS
2.13 Bill end
customers
Metric Data ?
2.11 Apply
av erage heating
v alue
2.22 Process Energy
Data Response
11.0 Basic Meter Profiler
(BMP) - 11.1
10.0 Data Change - 10.59.1 BM Daily Consumption
Estimation
A (from page 1)
2.23 Sav e
energy data
2.24 Process
energy data
2.25 Return
Meter Data
Response
2.26 Request
Energy History
2.27 Sav e
Energy History
data
Retail
Business
Customer
AEMO
Distribution
Business
BMDM
MBMR
Page 2
2.28 Identify any
missing energy
data
2.29 Request
missing energy
data
11.0 Basic Meter
Profiler (BMP) - 11.15
MeterDataMissingNotification
«aseXML (CSV)»
MeterDataMissingNotification
«aseXML»MeterDataNotification (2nd tier)
«aseXML (CSV)»
MeterDataNotification
«aseXML (CSV)»MeterDataHistoryResponse
(CSV)»
[No]
[Yes]
MeterDataResponse
«aseXML»
MeterDataResponse
«aseXML»Request Gas History Data
«fax or e-mail»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 6 of 51
1.5 DIAGRAM 2.7 – BASIC METER CUSTOMISATION BILL ESTIMATION
MBMR
BMDM
Distribution
Business
AEMO
Customer
Retail
Business
2.7.4 Prov ide
Customer
Characterisation
2.7.5 Prov ide EDD2.7.6 Prov ide av e. daily
flow. weighted Heating
Values
consumption
history >1yr?
2.7.1 Determine av e
BL & av e TSF from
Customer
Characterisation 2.7.2 Estimate Daily
Consumed Energy using
BL & TSF
2.7.3 Conv ert
Estimated Consumed
Energy to flow
2.0 Basic Meter Data
Collection and Delivery
- 2.62.0 Basic Meter
Data Collection
and Delivery - 2.8
AmendMeterRouteDetails
«aseXML (CSV)»
«MIBB»«MIBB»
[No]
[Yes]
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 7 of 51
1.6 DIAGRAM 4.0 – BASIC METER ROUTE AND SITE INFORMATION
MBMR
BMDM
Distribution
Business
AEMO
Customer
Retail
Business
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)
4.3 Consultation on
Route/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
3.4 Update Meter Data
Database
3.3 Receiv es and acknowledges change to Site Information
4.1 Analyse and
optimise routes4.2 Update/Create route
schedules based on
outputs
3.5 Meter Reading Serv ice
Prov ider requests changes to
site Information (eg - Access to
Meter, Address details)
5.1 Basic Meter Fix -
5.1.12
4.4 Record route
changes
4.5 Record annual
meter read schedule
5.3 Basic Meter Upgrade
to Interval - 5.3.10
2.0 Basic Meter Data
Collection and Delivery - 2.1
«Phone, fax, e-mail»
AmendMeterRouteDetails
«aseXML»
AmendMeterRouteDetails
«aseXML»
AmendMeterRouteDetails
«E-mail (CSV)»
Annual meter read schedule
«E-mail (CSV), web»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 8 of 51
1.7 DIAGRAM 4.1 – BASIC METER ROUTE AND SITE INFORMATION
Distribution
Business
Customer
Retail
Business
3.1c Customer
request change to
contact details
3.1d Customer request
mov e in and prov ides
contact Details
3.2c Retailer
records details
and issues request
to update contact
details
3.3 Reciev es and
acknowledges change
to customer contact
details
3.6 Update Customer
contact Database
«<aseXMLCSV>»
AmendCustomerDetails
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 9 of 51
1.8 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 1)
6.1.13 Prov ide
Implicit Informed
Consent
6.1.1 Submit Transfer
Request to CATS
6.1.6 Initiate
Transfer
Transaction
6.1.7 Request
Standing Data
6.1.9 Notify Affected
Parties
6.1.8 Deliv er
Standing Data
6.1.12 Put on Notice to
Deliv er Energy for This
Site in the Allowable
Period
6.1.10 Receiv e
Notice of Transfer
6.1.11 Receiv e
Notice of Transfer
Customer
AEMO
Current FRO
TPO
Distributor
6.1.17 Receiv e
Standing Data
6.1.18 Process
Response to Standing
Data
6.1.5 Notify New
Retailer
6.1.16 Process Response to
Transfer Request
End Process
A (to page 2)
Page 1
1.0 Special Meter Reads - 1.2
New FRO
12.0 MIRN
Request
End Process
I (to page 4)
6.1.19 Is it re
Retrospective Transfer
& no reading for that
date?
6.6.1 Receiv e
Problem Notice
6.1.20 Generate
Problem Notice
NACK
Further processing as per
problem notice handling,
refer to Page 6
6.1.21 Is it
move-in transfer ?
B (to page 3)
D (to page 4)[No]
[Yes]
[If Special Read is required]
CATSChangeRequest
«aseXML»
CATSChangeResponse
«aseXML»
CATSChangeResponse
«aseXML»
CATSDataRequest
«aseXML»
CATSNotification
«aseXML»
«manual process»
CATSNotification
«aseXML»
CATSChangeRequest
«aseXML»
[No]
NACK [Yes]
«aseXML»
CATSChangeAlert
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 10 of 51
1.9 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 2)
6.2.2 Enter
Objection in CATS
6.2.3 Validate
Objection
6.2.5 Notify
Objecting Party6.2.6 Register
Objection
Customer
New FRO
AEMO
Current FRO
TPO
Distributor
6.2.7 Process
Objection
Response
A (from page 1)
C (to page 3)
6.3.1 Notify
Affected
Participants
6.3.2 Consider
Valid Objection
6.3.5 Receiv e
Notice of
Objection
6.2.1 Object ?
B (to page 3)
G (to page 3)
Page 2
[No]
[Yes]
CATSObjectionResponse
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSObjectionRequest
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 11 of 51
1.10 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 3)
6.3.19 Receiv e
Notice of Objection
Withdrawal6.3.10 Liase/Notify
with Customer
6.3.12 Receiv e
Cancelled Txf
Notice
6.3.8 Clear
Objection
6.3.11 Monitor
Objection Period
6.3.9 Any Objections?6.3.13 Cancel
Transfer Request
End Process
End Process
6.3.14 Receiv e
Cancelled Txf
Notice
6.3.15 Receiv e
Cancelled Txf
Notice6.3.20 Receiv e
Notice of Objection
Withdrawal
6.3.18 Receiv e
Notice of Objection
Withdrawal
6.3.17 Remov e from
the Transfer Queue to
Deliv er Energy
6.3.16 Receiv e
Cancelled Txf
Notice
Customer
New FRO
AEMO
Current FRO
TPO
Distributor
C (from page 2)
6.3.7 Resolv e
ObjectionD (to page 4)
B (from page 2)
G (from page 2)
6.3.21 Receiv e
Notice of
Objection
Withdrawal
Page 3
H (from page 5)
6.3.22 Send
Cancelled Txf
Notice
6.3.23 Send
Notice of
Objection
Withdrawal CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»CATSNotification
«aseXML»
CATSNotification
«aseXML»
[objection period expired]
CATSObjectionWithdrawal
«aseXML»
[Yes]
[No]
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 12 of 51
1.11 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 4)
1.12
6.4.14 Receiv e
Status Update
6.4.1 Set Transfer
Status to Pending
6.4.16 Receiv e
Status Update
6.4.15 Receiv e
Status Update
6.4.2 Wait For
Final Read Data
6.4.3 Load Actual
Meter Read Data6.4.5 Is Read an Actual Read?
6.4.6 Is Read
Date OK for
Transfer?
6.4.9 Update CIS
End Process
End Process
End Process
End Process
End Process
6.4.7 Update
Status to
Completed
6.4.8 Notify
Affected
Participants
6.4.10 Issue
Final Bill
6.4.11 Update
DUoS/TUoS Billing
6.4.12 Update
Data Access
Controls
6.4.13 Update
Meter Register
Customer
New FRO
AEMO
Current FRO
TPO
Distributor
D (from page 3)
E (from page 5)
F (to page 5)
Page 4
6.4.17 Has
Standing Data
been provided ?
6.4.17 Send Status
Change Notice
1.0 Special
Meter Reads -
1.16
11.0 Basic Meter
Profiler (BMP) - 11.21
I (from page 1)
[No]
[Yes]
[No]
[Yes][Yes]
[Yes]
[No]
[No]
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
D (from page 1 and 3)
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 13 of 51
DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 5)
6.5.1 Exception
Processing
6.5.4 New
Transfer Date
or Cancel?
6.5.17 Receiv e
Transfer
Cancellation
Notice
End Process
End Process
End Process
6.5.2 Notify Late
Meter Read 6.5.6 Set Transfer
Status to Cancelled
6.5.7 Notify Affected
Participants
6.5.8 Update
Status with new
Transfer Date
6.5.10 Notify
Affected
Participants
6.5.19 Receiv e
Transfer
Cancellation
Notice
6.5.18 Receiv e
Transfer
Cancellation
Notice
6.5.11 Receiv e
Notice
6.5.12 Receiv e
Notice
6.5.3 Notify New
Retailer Of final
Read Failure
Customer
New FRO
AEMO
Current FRO
TPO
Distributor
F (from page 4)
6.5.15 Receiv e
Notice of Read
Failure
6.5.16 Receiv e
Notice of Read
Failure
E (to page 4)
CATSChangeWithdrawal
Page 5
6.5.14 Has
read fail notice
been issued ?
H (to page 3)
CATSChangeRequest
6.5.20 Process
Response
AEMOwill automatically cancel the Transfer Request
if a New Transfer Date or a Cancellation is not
received within 10 business days.
6.5.21 Is it re
Retrospective
Transfer
H (to page 3)
[Cancel]
«aseXML»
[New transfer date]
«aseXML»
CATSDataRequest
«aseXML»
CATSDataRequest
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSNotification
«aseXML»
CATSChangeResponse
«aseXML»
CATSDataRequest
«aseXML»
[No]
[Yes]
[No]
[Yes]
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 14 of 51
1.13 DIAGRAM 6.0 – CUSTOMER TRANSFER (PAGE 6)
6.6.1 Receiv e
Problem Notice
6.6.2 Pass Problem
Notice to New
Retailer
6.6.5 Generate
Problem Notice
6.6.3 Generate
Problem Notice
Customer
New FRO
AEMO
Current FRO
TPO
Distributor
Page 6
6.6.4 Generate
Problem Notice
CATSChangeAlert
«aseXML»
CATSChangeAlert
«aseXML»
«manual process»
CATSChangeAlert
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 15 of 51
1.14 DIAGRAM 9.1 – BM DAILY CONSUMPTION ESTIMATION
Customer
Retail Business
AEMO
Distribution
Business
BMDM
MBMR
11.0 Basic Meter Profiler (BMP)9.1.1 Consumed
Energy Available ?
9.1.2 Estimate Daily
Consumed Energy using
BL & TSF
9.1.3 Prov ide BL & TSF
11.0 Basic Meter Profiler
(BMP)
See also diagram 11.0 BMP
(11.16 -> 11.17)
This diagram is for AEMO internal use only.
Not to be used for participant design
[No]
[Yes]
NMIStandingDataUpdateNotification
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 16 of 51
1.15 DIAGRAM 10.0 – DATA CHANGE
Retail
Business
Customer
AEMO
Distribution
Business
BMDM
MBMR
10.1 Customer
complaint re bill
10.2 Consider
complaint - data
problem?
10.3 Request data quality confirmation and
prov ide clarifiying Information (where
applicable)
10.6 Manage customer /
complaint
10.4 Initiate Special
Read
10.8 Alternative
re-estimate or special
read required?
10.7 Carry out
alternativ e
re-estimation
10.5 Inform RB of
re-estimation or special
read result
1.0 Special Meter Reads -
1.4
2.0 Basic Meter Data
Collection and
Delivery - 2.12
[Yes] [No]
MeterDataVerifyRequest
«aseXML»
[Special Read] [Alternative re-estimate]
[If new energy data is to be
supplied]
MeterDataVerifyResponse
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 17 of 51
1.16 DIAGRAM 11.0 – BASIC METER PROFILER (BMP)
Retail
Business
Customer
AEMO
Distribution
Business
BMDM
MBMR
11.11 Calculate EDD
Values
11.12 Generate
v alues/site without
reading
11.5 Aggregate
Energy Readings by
RB by DB
11.6 Apply Profile to
Aggregated Energy
11.4 Apply UAFG
Benchmark
11.7 Profile
Preparation (PPS)
11.8 Settlements
Process
11.9 MIBB
11.17 Update Meter
Register with BL and
TSF
11.21 Meter Data
Store
Meter Data Store
11.16 Deliv er BL and
TSF by Site
11.14 Monitor Energy
Data
11.15 Request
Missing Energy Data
11.2 Are all
MIRNs present ?
11.18 Send Response
to BL and TSF by Site
Update
11.20 Process Response
to BL and TSF by Site
Update
11.1 Validate Data
6.0 Customer
Transfer - 6.4.3
2.0 Basic Meter Data
Collection and Delivery
- 2.12
2.0 Basic Meter Data
Collection and Delivery
- 2.22
MeterDataResponse
«aseXML»
NMIStandingDataUpdateResponse
«aseXML»
MeterDataNotification (2nd tier)
«aseXML»
NMIStandingDataUpdateNotification
«aseXML»
[No]
[Yes]
MeterDataMissingNotification
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 18 of 51
1.17 DIAGRAM 12.0 – MIRN REQUEST
Retail
Business
Customer
AEMO
Distribution
Business
BMDM
MBMR
12.2 Prov ide Explicit
Informed Consent,
MIRN or Address
12.12 Contact DB
for Details
12.13 Manage Query
on Failed Searches
12.9 Can RB resolve?
12.3 Initiate MIRN
Discov ery Transaction
12.5 Single match on
Address/MIRN?
12.6 Prov ide MIRN Data12.7 Prov ide Additional
MIRN Data
12.8 Use Data
NMIDiscoveryRequest/
NMIStandingDataRequest
12.14 Return error
NMIDiscoveryResponse/
NMIStandingDataResponse
MIDiscoveryResponse/
NMIStandingDataResponseNMIDiscoveryResponse/
NMIStandingDataResponse
«Phone, fax, e-mail»
[No][Yes]
«aseXML»
[Yes][No] [If additional data to be supplied]
«aseXML» «aseXML»«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 19 of 51
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
Ret
aile
r
(Not
FR
O)
Ret
aile
r
(Not
FR
O)
AE
MO
AE
MO
FRO
FRO
Dis
tribu
tor
Dis
tribu
tor
Cus
tom
erC
usto
mer 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 email for
“Identify FRO”.
4. Helpdesk logs
call and searches
meter register for
current FRO.
5. AEMO Pass
customer details to
FRO and closes call.
6. FRO contact
customer and
collects SO
details.
7. Customer
happy.
End.
8. Organise
Service Order (if
required).
9. Receive Service
order request and
complete.
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 20 of 51
2 RETAILER OF LAST RESORT PROCESS FLOWS
2.1 DIAGRAM 13.1 – PRE-ROLR EVENT – MONTHLY TRANSFER OF CUSTOMER DATA TO AEMO
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 21 of 51
2.2 DIAGRAM 13.2 – CATS PROCESSING – CANCELLED AND ACCELERATED CUSTOMER TRANSFERS
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 22 of 51
2.3 DIAGRAM 13.2A – CATS PROCESSING – ACCELERATED CUSTOMER TRANSFERS (‘MOVE INS’)
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 23 of 51
2.4 DIAGRAM 13.3 – NON-CATS / CUSTOMER DATA EXCHANGE AND DATA GENERATION
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 24 of 51
2.5 DIAGRAM 13.4 – FRB GENERATED CUSTOMER LISTS FOR ROLR
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 25 of 51
2.6 DIAGRAM 13.5 – WHOLESALE PROCESS
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 26 of 51
2.7 DIAGRAM 13.6 – ROLR COMMUNICATIONS
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 27 of 51
2.8 DIAGRAM 13.7 – PROVISION OF ESTIMATE TRANSFER READS AND SUBSEQUENT ADJUSTMENT
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 28 of 51
2.9 DIAGRAM 13.8 – SERVICE ORDERS IN FLIGHT
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 29 of 51
3 PROCESS FLOW DIAGRAMS
3.1 DIAGRAM 99.1 – MAINS RENEWAL
99.1.1 Identify
maintenance work
requirement
99.1.2 Identify
impacted MIRNs
99.1.3 Notify Retailer
of impacted MIRNs
99.1.4 Record
impacted MIRNs
Distributor
Retailer
99.1.5 Notify impacted
customers as required
FieldWorkNotification
«E-mail (CSV)»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 30 of 51
3.2 DIAGRAM 99.2 – NETWORK BILLING
99.2.1 Collate
Network DUoS
Billng Details data
99.2.2 Record
Network DUoS
Billing Details
data
Distributor
Retailer
99.2.3 Issue a
Dispute
99.2.4 Rev iew
Network DUoS
Billing Details and
Propose a
Resolution
99.2.5 Rev iew
Proposed
Dispute
Resolution
99.2.6 Record
Payment Details
«aseXML (CSV)»
NetworkDUoSBill ingNotification
[disagreement with
bill ing details]
«aseXML (CSV)»
NetworkDUoSBill ingNotification
«aseXML (CSV)»
NetworkDUoSBill ingNotification
«aseXML (CSV)»
NetworkDUoSBill ingNotification
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 31 of 51
3.3 DIAGRAM 99.4 – MIRN STANDING DATA UPDATE
99.4.1 Update
MIRN Standing
Data
99.4.2 Notify
Retailer of
change
99.4.3 Update
MIRN Standing
Data
Distributor
Retailer
«e-mail»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 32 of 51
3.4 DIAGRAM 99.5 – METERED SUPPLY POINT COUNT UPDATE
99.5.2 Update Metered
Supply Points Count
99.5.1 Prov iding
Metered Supply Points
Count
AEMO
Distributor
MeteredSupplyPointsCountUpdate
«aseXML»
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 33 of 51
4 CUSTOMER CLASSIFICATION
4.1 DIAGRAM 99.6 – METER FIX
Customer Classification
AEM
OR
etai
ler
Dis
trib
uto
r
AGREED - Transfer (Insitu/MoveIn)
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
Generate Account Creation
Notification
Send Notifiction transfer Complete
Receive Completion and update system
Receive Completion and ACN and
update system(s)
Generate Amend Route/Site Address Details Transaction
Has the primary use of the property changed?
End
No
Yes
Receive Amend Route/Site Address Details transaction
and update system(s)
Receive transaction with Customer Classification
Code
Generate Amend Route/
Site Address Details
Transaction
Where CCC is “BUS” Update
Customer Threshold Code (‘LOW’, ‘MED’,
‘HIGH’
Send update
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 34 of 51
4.2 DIAGRAM 99.7 – TRANSFER (IN SITU / MOVE – IN)
Customer Classification
AEM
OR
etai
ler
Dis
trib
uto
r
AGREED - Transfer (Insitu/MoveIn)
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
Generate Account Creation
Notification
Send Notifiction transfer Complete
Receive Completion and update system
Receive Completion and ACN and
update system(s)
Generate Amend Route/Site Address Details Transaction
Has the primary use of the property changed?
End
No
Yes
Receive Amend Route/Site Address Details transaction
and update system(s)
Receive transaction with Customer Classification
Code
Generate Amend Route/
Site Address Details
Transaction
Where CCC is “BUS” Update
Customer Threshold Code (‘LOW’, ‘MED’,
‘HIGH’
Send update
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 35 of 51
4.3 DIAGRAM 99.8 – MOVE IN (NO CHANGE IN RETAILER)
Customer Classification
Ret
aile
rD
istr
ibu
tor
AGREED - Move In (Same Retailer)
Receive Customer request for Move-in on property already
with the Retailer
Generate Amend Route/Site Address Details Transaction
Has the primary use of the property changed?
End
No
Yes
Receive transaction with updated
Customer Classification Code
Generate Amend Route/Site Address Details Transaction
Receive Amend Route/Site Address Details transaction
and update system(s)
Where CCC is “BUS” Update
Customer Threshold Code (‘LOW’, ‘MED’,
‘HIGH’
Send update
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 36 of 51
4.4 DIAGRAM 99.9 – CUSTOMER REQUEST TO RETAILER
Customer Classification
Ret
aile
rD
istr
ibu
tor
AGREED - Request from Customer to RB
Receive Customer request
Generate Amend Route/Site Address Details Transaction
Has the primary use of the property changed?
End
No
Yes
Receive transaction with updated
Customer Classification Code
Generate Amend Route/Site Address Details Transaction
Receive Amend Route/Site Address Details transaction
and update system(s)
Where CCC is “BUS” Update
Customer Threshold Code (‘LOW’, ‘MED’,
‘HIGH’
Send update
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 37 of 51
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 ActivityProcess Terminator/
Inter-process LinkDecision
Process Close
On
Page
Ref
Process Start
Decision/Data Transfer Description
Wait
Notes
Parallel
Mode
Association
aseXML Message Description
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 38 of 51
5.2 Diagram 100: Service Orders General (Simplified)
SA Process Ref: PF (B2B) REQ5B/MIRN 1
Diagram 100: Service Orders General (Simplified)
AE
MO
Dis
trib
uto
rR
eta
iler
Cu
sto
me
r
ServiceOrderRequest
[actionType=’New’]
<<aseXML>>
#1
<<aseXML>>
#4
YesYes
No
Transaction
Acknowledgment
<<aseXML>>
ServiceOrderResponse
[responseType=’Initial’]
<<aseXML>>
#2
Yes
No
ServiceOrderResponse
[responseType=’Closure’]
<<aseXML>>
#3
YesNoYes
Where rejected, Retailer takes
appropriate action e.g. Initiate
new service order request and
current process ends.Wait for service order
response ‘Closure’
Yes
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
No
No
No
19. Action
Notification
11. Has SO
been
Completed?
16. Does SO Type
Require Delivery
of Meter Data?
2. Send Service
Order (SO)
C-K
Go To 102.2
12. Was Additional
or Alternative
Work Completed?
Go To 2.0 Meter
Data Delivery
9. Log Service
Order & Send
Response
6. Receive
Acceptance/
Rejection
1. Request a
Service
18. Send
Notification to
AEMO
8. Receive Service
Order Response
(Initial)
5. Send Validation
Outcome
7. Was Service
Order Accepted?
15. Receive
Service Order
Response
(Closure)Up to 5 BD From
Expected Completion of Step 10
10. Action Service
Order
4. Valid Service
Order Request?
13. Send Service
Order Response
3. Receive Service
Order Request &
Validate
1a. Request a
Service
17. Does SO
Require
Notification to
AEMO?
From 103.15 or
104.6 or 104.8 as
applicable
Up to 5 BD from Expected
Completion of Step 10
#1, 2, 3 & 4 Refer to Diagram 107 for the transactions involved
Go To 105.18 or
106.14 as
applicable
14. Upgrade or
Downgrade?
Yes
No
From 103.14
Go To 105.4 or
106.4 as
applicable
If required by
service requested
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 39 of 51
5.3 Diagram 101: Retailer Initiated Service Orders Cancellation
SA Process Ref: PF (B2B) REQ 7
Diagram 101: Retailer Initiated Service Orders CancellationD
istr
ibu
tor
Re
taile
rC
usto
me
r
ServiceOrderRequest
[actionType=’Cancel’]
<<aseXML>>
#1
Yes
No
Transaction
Acknowledgment
<<aseXML>>ServiceOrderResponse
[responseType=Closure]
<<aseXML>>
#3
Yes
2. Send Service
Order (SO)
Cancellation
C-K
1a. Request a
Service order to
be Cancelled
3. Receive Service
Order Cancellation
& Validate
4. Valid Service
Order Cancel
Request?
1. Request a
Service order to
be Cancelled
9. Update System
Data
8. Receive Service
Order Response
12. Send Service
Order Response
6. Receive
Acceptance/
Rejection
5. Send Validation
Outcome
11. Can Initial SO
be Cancelled?
No
Yes
Same day cancellations
must also be phoned through
Where cancellation is
rejected the original SO will
continue to be actioned
No
7. Was SO
Cancellation
Accepted?
Where cancellation is rejected
the original SO will continue to
be actioned
Retailer takes appropriate action
10. Attempt to
Cancel Initial SO
Request
Up to 5 BD from Expected
Completion of Step 10
#1 & 3 Refer to Diagram 107 Table for the transactions involved
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 40 of 51
5.4 Diagram 102: Distributor Initiated Service Orders
SA Process Ref: PF (B2B) REQ 6
Diagram 102: Distributor Initiated Service OrdersA
EM
OD
istr
ibu
tor
Re
taile
r
<<aseXML>>
#4
Yes
No
No
ServiceOrderResponse
[responseType=Closure]
<<aseXML>>
#3
Distributor initiated work at
the site requires update to
retailer/AEMO
This includes Time Expired
Meters
8. Action
Notification
3. Receive &
Validate Service
Order Response
(C-K)
2. Send Service
Order Response
(C-K)
4. Update System
Data
#3 & 4 Refer to Diagram 107 Table for the transactions involved
Go To 2.0 Meter
Data Delivery
From 100.12
7. Send
Notification to
AEMO
5. Does SO Require
Notification to AEMO?
6. Does SO Type
Require Delivery of
Meter Data?
1. Complete Field
Work
Yes
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
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 41 of 51
5.5 Diagram 103: Shipper Process
SA Process Ref: MIRN1.1 Part 2
Diagram 103: Shipper ProcessD
istr
ibu
tor
Re
taile
rC
usto
me
r
Phone
No
Yes
Yes
Phone/Fax/Email
No
Yes
Email/Fax
Email/Fax
If rejected, resolve issues
with customer and resend
Shipper Form (potentially
amended)
The request for work Form is
different for each DB
Tariff V requires response
within 10 business days from
request received otherwise
date agreed by the customer
No
Go To 100.1a
14. Receive
Signed Shipper
Acceptance
11. Advise Customer
of Costs / Conditions
& Send Offer
13. Receive
Signed Agreement
5. Send Validation
Outcome
12. Accept
Cost /
Conditions?
7. Review Field
Requirements
and/or Visit Site
6. Receive
Validation
Outcome
1. Request a
Service
4. Valid
Shipper
Request?
3. Receive &
Validate Shipper
Form
8. Does the
Site Match
Shipper Form?
10. Receive
Shipper Response
9. Complete
Shipper
Evaluation Form &
Send Response
2. Prepare
Shipper Form
Notes: Service Order Enquiry Code
MAP, MFX, MRT, RSR, SCR, UMS,
USR
15.Is SO Required
for the Service by
the Applicable
DB?
Yes
1a. Request a
Service
1b. Request a
Shipper
From 104.3 or
105.1 or 106.1 as
applicable
From 105.2 or
106.2 as applicable
From 105.3 or
106.3 as
applicable
Go To 104.7 or 105.5
or 106.5 or 100.9 as
applicable
No
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 42 of 51
5.6 Diagram 104: Meter Fix Request
SA Process Ref: NA
Diagram 104: Meter Fix RequestR
eta
iler
Cu
sto
me
r
1. Request Meter Fix
as Service & Fitting
Lines Completed
2.Simple Meter
Type
Installation?
4. Request
Customer to
Provide CoC &
PLN
5. Customer
Quotes CoC &
PLN
6. Valid CoC &
PLN?Go To 100.1a
7. Request Customer
to Provide Start Work
Notice No & PLN
8. Customer
Quotes Start Work
Notice No & PLN
Yes
No
No Yes
3.Is a Shipper
form required?No
Go To 103.2Yes From 103.14
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 43 of 51
5.7 Diagram 105: Upgrade from Basic to Interval Meter
SA Process Ref: PF (B2B) MR12
Diagram 105: Upgrade from Basic to Interval MeterA
EM
OD
istr
ibu
tor
Re
taile
rC
usto
me
r
GIP 126
No
Yes
Email GIP 126
EmailEmail
GIP 126
Email or
ServiceOrderResponse
7. Prepare & Send
Meter Registration
(MR) Application12. Receive
Notated MR
Application
11. Update Meter Register
to ‘Pending’ Interval
Metering & Send Notated
MR Application
18. Receive
Completion Advice
16. Receive
Notated MIP
Notice
8. Amend &
Resubmit MR
Application
17. Update
System Send
Completion Advice
to Retailer
9. Receive &
Validate MR
Application
14. Complete & Send
Meter Installation
Parameter (MIP)
Notice
5. Confirm Receipt
of Signed
Acceptance
10. MR
Application
Valid?
1. Request
Upgrade to
Interval Meter
From 103.14
15. Update Meter Register
to ‘Active’ Interval
Metering & Send Notated
MIP Notice
Go To 103.2
3. Distributor
identifies need for
Basic to Interval
Meter Upgrade
13. Commission
Interval Meter in
Association with
MDP
6. Install Data
Logger and/or
Comms
4.Confirm Receipt
of Service Order
From 100.9
If required by service
requested
Go To 103.1b
2. Retailer
identifies need for
Basic to Interval
Meter Upgrade
Go To 103.1a
From 100.14
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 44 of 51
5.8 Diagram 106 : Downgrade from Interval to Basic Meter For tariff D
SA Process Ref: PF (B2B) MR14
Diagram 106 : Downgrade from Interval to Basic Meter For tariff DA
EM
OD
istr
ibu
tor
Re
taile
rC
usto
me
r
GIP 134
No
Yes
GIP 134
ServiceOrderResponse
9. MIP Valid?
14. Receive SO
Completion Advice
Go To 103.2
2. Retailer
identifies need for
Interval to Basic
Meter Downgrade
11. Receive
Notated MIP
Go To 103.1a
13. Remove Data
Logger and/or
Comms
10. Update Meter Register
to ‘Basic’ Metering & Send
Notated MIP
Go To 103.1b
3. Distributor
identifies need for
Interval to Basic
Meter Downgrade
6. Prepare & Send
Meter Installation
Parameter change
Notice (MIP)
From 100.9
5. Confirm Receipt
of Signed
Acceptance
From 100.14
12. Update
System and set
Meter to ‘Basic’
7. Amend &
Resubmit MIP
From 103.14
8. Receive &
Validate MIP
4. Confirm Receipt
of Service Order
1. Request
Downgrade to a
Basic Meter
PARTICIPANT BUILD PACK 1 - PROCESS FLOW DIAGRAMS
Doc Ref: 305196 ver 3.4 01 JULY 2014 Page 45 of 51
5.9 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 87A - Meter Fix Request Response GIP 92 - Meter Fix Completed GIP 94 - Meter Fix Notification
GIP 93 - No Access to Complete Meter
FixGIP 101 - Meter Change Request
(JEC = MCH)
GIP 101A - Meter Change Request
Response
GIP 104 - No Access to Complete Meter
Change
GIP 108 - Meter Change Completed
GIP 125 - Meter Upgrade Completed
GIP 151 - Meter Removal Request
(JEC = MRM)
GIP 151A - Meter Removal Request
Response
GIP 154 - No Access to Complete Meter
Removal
GIP 158 - MIRN Status Update
Notification
GIP 157 - Meter Removal Completed
GIP 310 - Service Connection Request
(JEC = SCR)
GIP 310A - Service Connection Request
ResponseGIP 311 - Service Connection Complete
GIP 312 - Service Disconnection Request
(JEC = SDR)
GIP 312A - Service Disconnection Request
Response
GIP 313 - Service Disconnection
Complete
GIP 158 - MIRN Status Update
NotificationGIP 314 - Service Orders for Priority C-K
(JEC = All JEC's)
GIP 314A - Service Orders for Priority C-K
Response
GIP 315 - Service Orders Completed for
Priority A-KGIP 316 - Relocate Service Request
(JEC = RSR)
GIP 316A - Relocate Service Request
ResponseGIP 317 - Relocate Service Complete
GIP 318 - Upgrade Service Size Request
(JEC = USR)
GIP 318A - Upgrade Service Size Request
Response
GIP 319 - Upgrade Service Size
CompleteGIP 320 - Upgrade Meter Size Request
(JEC = UMS)
GIP 320A - Upgrade Meter Size Request
ResponseGIP 321 - Upgrade Meter Size Complete
JEC = Job Enquiry
Diagram 107: Service Order Transaction Table