FRC B2B Process Flows for SA and WA Gas Markets

FRC B2B Process Flows
For the SA and WA Gas Retail Markets
Version: 3.4
Last Update: 1 July 2014
Preamble:
This document has been modified to comply as closely as possible with the jurisdictional
conditions of both the South Australian and Western Australian gas retail markets in place since
1 October 2009. The reader needs to be aware of the following changes.
(a) Several terms have been changed to a general term where possible with a market
specific definition; and
(b) in the interests of keeping new terms and acronyms to a minimum, the original word has
been italicised where possible to indicate that its definition again depends on its location.
This approach is to promote interchange-ability in these documents for the benefit of

stakeholders from both states.
The terms and there relevant definitions are as follows:
Term: South Australian Market Western Australian

Definition: Market Definition:
Market Operator AEMO REMCo
Retail Market Rules Retail Market Procedures Retail Market Rules
For more information please contact the Market Operator in your state:
AEMO REMCo
Website: http://www.aemo.com.au http://www.remco.net.au
B2B Process Flows v3.4 2

Version Release History
Version Date Author(s) Changes and Comments
0.1 30/9/03 C.Madden Initial release
0.2 16/10/03 C.Madden Working copy for Workshop
0.3 22/10/03 C.Madden Update from Workshop 17/10/03
0.4 30/10/03 C.Madden Update from Workshop 27/10/03
1.0 Minor updates
2.0 31/10/03 C.Madden Updates as per Envestra and Alinta feedback
2.1 26/11/03 C.Madden Updates from Workshop 21/11/03. Pending the addition of a
further three flows when approved.
2.2/9 19/01/04 B.Eaves Corrections to introduction and addition of REQ6B and REQ8
3.0 1/3/04 B. Eaves Addition of MIRN 1.1 – New Connection – I&C Service
Connection SA Part 1 and Part 2. Modifications to Service
Order flows in relation to interval meters.
3.1 27/4/04 B. Eaves MR9A – GIP transaction number corrected. Details of Meter
Data Notification corrected and separated for SA and WA.
MR9B – Service Order Completion Response from Step 4
removed. Note added to indicate that notification to the user is
via MDN.
MR11A – Meter Date Notification Read Reason Code
corrected.
REQ7 – Additional decision point of ‘Able to cancel Service
Order added together with steps 2 and 3.
REQ8 – Wording changed from ‘deemed’ to ‘implied’
MR7A – New flow added.
3.2 1/6/05 REMCo Update to reflect changes incorporated in V5.0 of RMR.
3.3 15/08/11 Z. Gemmell Generic documentation changes, including the addition of a
preamble for the document to be applicable in the SA and WA
gas retail markets.
3.4 1/07/14 T. Sheridan Updated to reflect the out workings of IN017/13 - Amended
relevant Service Order sections. SA only changes.

TABLE OF CONTENTS
INTRODUCTION ....................................................................................................................................................5
2. DATABASES ...............................................................................................................................................7
PROCESS FLOW: DB1: REQUESTED DB UPDATES ............................................................................................8
PROCESS FLOW: DB2: STREET SUBURB TABLE UPDATE .................................................................................9
3. MIRN..........................................................................................................................................................10
PROCESS FLOW: MIRN1: NEW CONNECTION - SERVICE CONNECTION (SA - PART 1)...............................11
PROCESS FLOW: MIRN1.1: CONNECTION REQUEST/SHIPPER – NO RETAILER (SA - PART 1) ..................12
PROCESS FLOW: MIRN1.1: CONNECTION REQUEST/SHIPPER – RETAILER ASSIGNED (SA - PART 2).......13
PROCESS FLOW: MIRN3: NEW CONNECTION (WA)......................................................................................14
PROCESS FLOW: MIRN 4A: STANDING DATA REQUEST/MIRN DISCOVERY BY MIRN..............................15
PROCESS FLOW: MIRN 4B: MIRN DISCOVERY BY ADDRESS ......................................................................16
4. METER READ ..........................................................................................................................................17
PROCESS FLOW: MR1: METER READS - FAILURE OF A COMPLETE ROUTE .................................................18
PROCESS FLOW: MR2: REQUEST FOR CHANGE TO METER READING SCHEDULE.......................................19
PROCESS FLOW: MR3: REQUEST FOR HISTORICAL DATA ............................................................................20
PROCESS FLOW: MR4A: SPECIAL METER READING RESPONSE (BASIC METERS ONLY) ..............................21
PROCESS FLOW: MR4B: DEEMED METER READING (BASIC METERS ONLY)................................................22
PROCESS FLOW: MR5: ACCOUNT CREATION .................................................................................................23
PROCESS FLOW: MR6: ANNUAL METER READING SCHEDULE .....................................................................24
PROCESS FLOW: MR7: METER SITE ACCESS/ADDRESS CHANGE FROM USER (SA) ...................................25
PROCESS FLOW: MR8: METER SITE ACCESS CHANGE FROM NO................................................................27
PROCESS FLOW: MR10: SERVICE RECOMMISSIONING BY REQUEST (WA ONLY) .......................................28
PROCESS FLOW: MR11C: DEREGISTRATION BY REQUEST (WA) .................................................................29
PROCESS FLOW: MR12: UPGRADE FROM BASIC TO INTERVAL METER (SA) ...............................................30
PROCESS FLOW: MR12: UPGRADE FROM BASIC TO INTERVAL METER (WA)..............................................31
PROCESS FLOW: MR13: GENERIC ENERGY FLOW ........................................................................................32
PROCESS FLOW: MR14: DOWNGRADE FROM INTERVAL TO BASIC FOR TARIFF D (SA) ............................33
5. REQUESTS AND SERVICE ORDERS..................................................................................................34
PROCESS FLOW: REQ1: METER DATA VERIFICATION .................................................................................35
PROCESS FLOW: REQ2: MISSING DATA READS ..............................................................................................36
PROCESS FLOW: REQ3: NOTIFICATION OF MAINS/SERVICE .......................................................................37
PROCESS FLOW: REQ4: NOTIFICATION OF DATA CHANGE ..........................................................................38
PROCESS FLOW: REQ5A: SERVICE ORDERS GENERAL (DETAILED) WA ONLY ........................................39
PROCESS FLOW: REQ5B: SERVICE ORDERS GENERAL (SA - SIMPLIFIED).................................................40
PROCESS FLOW: REQ5B: SERVICE ORDERS GENERAL (WA - SIMPLIFIED) ...............................................41
REQ5B: DET: SERVICE ORDERS TRANSACTION TABLE (SA ONLY) ...........................................................42
PROCESS FLOW: REQ6: DB INITIATED SERVICE ORDERS (SA)...................................................................43
PROCESS FLOW: REQ6B: DB VARIED SERVICE ORDERS WA ONLY...........................................................45
PROCESS FLOW: REQ7: RETAILER INITIAL REQUIRED SERVICE ORDERS CANCELLATION (SA) ............46
PROCESS FLOW: REQ7: SERVICE ORDERS CANCELLATION (WA) .............................................................47
PROCESS FLOW: REQ8: IMPLIED SERVICE RECOMMISSIONING AND (FOLLOWING TRANSFER
WITHDRAWAL) AN IMPLIED SERVICE DE-COMMISSIONING (SA) ...................................................................48
PROCESS FLOW: REQ8: IMPLIED SERVICE RE-COMMISSIONING AND (FOLLOWING TRANSFER
WITHDRAWAL) AN IMPLIED SERVICE DE-COMMISSIONING (WA) .................................................................49

1. Introduction
The Business-to-Business (B2B) process flow charts contained in this document have been
developed and updated as a working aid to assist the implementation of the South Australia
and Western Australia Gas Retail Markets (SA/WA markets). These diagrams use the
‘swimming lane’ style and show the business process flows between market participants.
Whilst the Market Operator will maintain this document on an on going basis participants are
requested to refer to the Specification Pack and relevant RMR for a detailed description of
processes. Please advise the Market Operator should you find any inconsistencies in this
document.
When reading and using this document, please note the following:
1. The process flow charts are designed to complement, but not replace, the following
source documents:
 Retail Market Rules,

 FRC B2B System Interface Definitions.
While reasonable effort has been made to ensure that these process flow charts are
consistent with the RMR and the FRC B2B System Interface Definitions, there may be
differences between the process flow charts and the source reference documents. If
there is a difference, the RMR and the FRC B2B System Interface Definitions take
precedence.
2. The process flow charts are not designed to aid the development of the B2M
requirements for the SA/WA markets. The B2M process flows are provided separately.
3. The process flow charts are designed to aid, where possible, the identification of the
necessary transactions between market participants. The following information is
provided, where known:
 Victorian Gas Market physical transaction name;

 Victorian Gas Market logical transaction name (GIP)
 Medium type eg aseXML, manual notice;
 RMR.
4. The
The drawing processused
conventions steps within
for these individual
diagrams businesses
are as follows: are indicative only and do not necessarily
identify all required process steps nor do they mandate the use of a particular process.
5. The drawing conventions used for these diagrams are as follows:
On
Process Terminator/
N.N Activity Decision Page
Inter-process Link
Ref
Process Close Process Start Wait Parallel
Mode
Decision/Data Transfer Description
aseXML Message Description  Notes
Association
6. 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 transaction.

7. The document has been divided into logical components reflecting the RMR and System
Interface Definition structures:
 Data Base and MIRN

 Meter Reading
 Requests and service orders
8. Related Documents. This document is provided as part of the Information Pack. This
document should be read in conjunction with the documents contained within the
Specification Pack as follows:
 Interface Control Document

 FRC B2B System Interface Definitions
 FRC B2M-B2B System Architecture
 FRC B2M-B2B System Specifications
 CSV Data Format Specification
Further detailed documents are provided for assistance and clarification in the Information
Pack as follows:
 Business Specification
 Consolidated Transaction List
 B2M Process Flow and Sequence Diagrams
 Glossary of Terms

2. Databases
Databases

Process Flow: DB1: Requested DB updates
PF(B2B) - DB 1: Requested DB updates
Process Step RMR Ref

1-4 61
Market Operator
5 62
1. Change 2. Produce 6 27 Notification
Y Data change
required for proposed of change
notice
MIRN or MSD amendment to Other references: decision
DB? NO database PF(B2M) - DB3
PF(B2M) - R2
Notes: Notice
The format and transport of the Data Change Notice to the <<email>>
User will vary depending on the information returned. As an
example refer to MR8. Y
4. Notify
N
Network Operator
applicant of Notice
6. Change to n/w operator,
change decision <<email>>
Notice of gas zone , meter type, base
proposed 3. DB change load or heating rate?
Notice amendment required?
Y 5. Change DB
Notice/Electronic File/
aseXML
(See note)
Current User
1A. Change 2A. Produce Notification

Y Updated details
required for proposed of change for a MIRN
MIRN or MSD amendment to decision
DB? NO database
Two business days Five business days

All participants
Project Prepared by Date

Page 1 of 1
SA/WA FRC-B2B Market Operator 17/11/03
Process Approved by Date
Requested DB updates B2B Working Group Pending

Process Flow: DB2: Street Suburb Table Update
PF(B2B) - DB 2: Street Suburb Table Update

Market Operator

1 59
Notes:
Network Operator
Extracted
1. Extract data for Street Suburb
downloading table for
all MIRNs
Current User
Website (view or download)
Complete
All users
2. View/Download Street Suburb

table table for
all MIRNs

Page 1 of 1
Street Suburb Table Update B2B Working Group Pending

3. MIRN
MIRN

Process Flow: MIRN1: New Connection - Service Connection (SA)
PF (B2B) MIRN 1: New Connection – Service Connection Request (SA)

VIC Process Ref: Diagram 100
Customer
1a. Raise 1b. Raise 9. Receive

Connection Connection Connection
Enquiry to DB Enquiry to Retailer Details
Phone
Where the Retailer has sent the
request via B2B ASExml, the
Retailer
applicable response will be provided

2. Raise
as per the Service Orders General
Connection
Process
Enquiry
GIP 310/Email Mail/Email/Fax
5. Is a Shipper
3. Contact From MIRN1.1 Part
Phone/Internet Portal Form
Customer 1.15
Required?
Yes
Distributor
No
4. Record and 7. Raise Service
8. Send
Validate Service 6. Is Retailer Connection
Connection
Connection Assigned? Request/Install
Details
Details Service Pipe
No
Yes
Go To MIRN1.1 Part Go To MIRN1.1 Part From MIRN1.1 Part

2.1b 1.1b 2.16

Process Flow: MIRN1.1: Connection Request/Shipper – No Retailer (SA - Part 1)
MIRN 1.1 Part 1 Connection Request/Shipper – No Retailer (SA)

If rejected, resolve issues VIC Process Ref: N/A
with customer and resend
Shipper Form (potentially No
amended)
Customer
5. Receive
14. Receive
Validation
11. Accept Invoice/Contract
1. Request a Outcome
Cost /
Service
Conditions?
Email Mail/Email/Fax
Yes
Phone/Email/Fax Phone/Fax/Email
Email/Fax
From MR12.1
From MIRN1.6 10. Advise Customer
of Costs / Conditions No
15. Invoice
4. Send Validation & Send Offer
Paid/Contract
Outcome Email/Fax
No Signed?
No
2. Prepare
Shipper Form Yes
Distributor
1b. Request a 7. Does the

Shipper Form 9. Assess Price & 12. Receive
Site Match
Approve Signed Offer
3. Valid Shipper Form? Go To MIRN1.7 or
Shipper Form Yes REQ6.1 as applicable
Request?
Yes
6. Review Field
13. Generate
Requirements
Invoice/Contract
and/or Visit Site 8. Complete
Shipper Form

Process Flow: MIRN1.1: Connection Request/Shipper – Retailer Assigned (SA - Part 2)
MIRN 1.1 Part 2 Connection Request/Shipper – Retailer Assigned (SA)

If rejected, resolve issues

The request for work Form is
with customer and resend
different for each DB
Shipper Form (potentially
Customer
amended)
6. Receive 12. Accept

1. Request a 15. Receive
Validation No Cost /
Service Invoice/Contract
Outcome Conditions?
Phone/Email/Fax
No
From MR12.1a or 2. Prepare

MR14.1 as applicable Shipper Form Yes 18. Is SO
Required? Yes
Email/Fax
Mail/Email/Fax
Retailer
1a. Request a Phone/Fax/Email

Phone/Fax/Email Go To REQ5B.1a
Service
Email
17. Confirm
Agreement
From MR12.2 or
Email/Fax
MR14.2 as applicable
Email
Email
11. Advise Customer

of Costs / Conditions
16. Invoice
1b. Request a 3. Prepare 5. Send Validation & Send Offer 13. Receive
Paid/Contract Yes
Shipper Form Shipper Form Outcome Signed Offer
No Signed?
No
Distributor
8. Does the Go To MIRN1.7 or

4. Valid 10. Assess Price
Site Match MR12.6 or MR14.5 as
Shipper Form & Approve
Shipper Form? No applicable
Request? Yes
From MIRN1.6 or
MR12.3 or MR14.3 as
applicable
Yes
7. Review Field
14. Generate
Requirements
9. Complete Invoice/Contract
and/or Visit Site
Shipper Form
Notes: Service Order Enquiry Code

MAP, MFX, MRT, RSR, SCR, UMS, USR

Process Flow: MIRN3: New Connection (WA)
PF(B2B): MIRN3: New Connection (WA)

4 64
Market Operator
5-6 65
6 66 New Connection To:
Confirmation PF(B2M) -
Notes: R3
Notice
For new basic meter connections, WA uses the Service Connection Request for both pipe installation and meter
connection.
At Service Order Completion the User becomes the 'Current User
The process flow does not show customer installation, inspection and commissioning
MeterFixComplete
Network Operator
4. Pipe (GIP94)
Y connection: 5. Commision delivery <<aseXML>>
- Install pipe; point:
Service 2. Send initial
3. Pipe - Assign - install/commission 6. Notify
Connection response N Meter
installed? MIRN to delivery meter participants
point ; and - gas is able to flow Data
- determine MIRN - meter reading actual Notification
ServiceOrder checksum <<aseXML>>
Request ServiceOrderResponse
(GIP 310) ServiceOrderResponse (GIP 311)
[actionType='New'] (GIP 310A) [responseType='Closure'
[JIC='SCR', 'ECO' [responseType='Initial'] <<aseXML>>
or 'CLT'] <<aseXML>>
<<aseXML>>
User
Service Connection /
1. Service Metering
Service Connection Meter Fix Complete
Connection Data
Response (Notification of
Request Registered MIRN)

Page 1 of 1
New Connection (WA) B2B Working Group Pending

Process Flow: MIRN 4A: Standing data request/MIRN discovery by MIRN
PF(B2B): MIRN 4A: Standing data request/MIRN discovery by MIRN

Market Operator
1 74
2-5 75
Notes:
Associated Discovery Flow - See MIRN 4B: MIRN Discovery by Address
Event Codes:
3603 Recipient is not responsible for the supplied MIRN
3638 MIRN is de-registered
Network Operator
NMI Standing Data Y Other 5. (SA Only)

Request 2. Is MIRN 3. MIRN 4. Provide MIRN
Additional data
within range? status? Data
to be supplied?
N Deregistered
NACK NACK
NMIStandingDataRequest NMIStandingDataRequest NMIStandingDataRequest NMIStandingDataResponse
NMIStandingDataResponse
(GIP 280) (GIP 280) (GIP 280) (GIP 281)
(GIP 284)
<<aseXML>> Event Code = 3603 Event Code = 3638 <<aseXML>>
<<aseXML>>
<<aseXML>> <<aseXML>>
MIRN Standing Data

1. Inititiate MIRN MIRN Standing Data
Negative Negative Response
discovery Response
Acknowledgement Acknowledgement - Additional Data
transaction
User

Page 1 of 1
Standing data request/MIRN discovery by
B2B Working Group Pending
MIRN

Process Flow: MIRN 4B: MIRN Discovery by Address
PF(B2B): MIRN 4B: MIRN Discovery by Address
Notes:
Market Operator
The Rules (R75-77) state that the response to a Discovery request should be immediate unless lodged on a non business day when the reply must be as if lodged
on the next business day.
Associated Discovery Flow - See MIRN 4A: Standing Data Requesyt/MIRN Discovery by MIRN Process Step RMR Ref
Event Codes: 1 74
3606 Address not found 2-4 75
3608 Address outside DB area
Note re multiple returns: If 99 MIRNs are returned for one address it should be assumed that more than 99 may exist
Network Operator
3. Single Match Single

NMI Discovery Request 2. Does Y 5. (SA Only)
or multiple match 4. Provide MIRN
(by address) address Additional data
to registered Data
exist? to be supplied?
MIRNs ?
N
Multiple Y
NACK
NMIDiscoveryRequest/ NMIDiscoveryResponse NMIDiscoveryDataResponse
NMIDiscoveryRequest NMIDiscoveryDataResponse
(GIP 280) (GIP 281) NMIStandingDataResponse
(GIP 280) (GIP 281)
<<aseXML>> Event code = 3680 (GIP 284)
Event Code = 3606 or 3608 <<aseXML>>
<<aseXML>>
1. Inititiate MIRN Message: Initial MIRN Standing Data

Negative discovery request MIRN Additional Data
discovery Response
Acknowledgement response
transaction
User
- up to 99 MIRNs

Page 1 of 1
B2B Specification Pack Market Operator 17/1/03
MIRN Discovery by Address B2B working group Pending

4. Meter Read
Meter Read

Process Flow: MR1: Meter Reads - Failure of a complete route
PF(B2B) - MR1: Meter Reads - Failure of a complete route

2-3 158(3)
Market Operator
Notes:
Network Operator
2. Is there a Y 3. Verification of
1. Read basic
total route meter reading
meter
failure? data
N
Other affected users
CSV file with

MIRN
Notification of no
<<eMail>>
read for route
Close of business
next business day

Page 1 of 1
Meter Reads - Failure of a complete route B2B Working Group Pending

Process Flow: MR2: Request for change to Meter Reading Schedule
PF(B2B) - MR2: Request for change to Meter Reading Schedule

Market Operator
1-4 145
Notes:
These requests are for individual MIRNs
Minimum notice is at least as much notice of the proposed change for a MIRN, as the
interval under the meter reading schedule between two meter readings for the MIRN. This
notice applies to request from the current user only)
Network Operator
CSVAmendScheduledReadingDay
<<Electronic File>> 4. Scheduled
1. Initiate 3. Proceeding Y
2. Consult with all meter
change to meter with schedule read (applies to
affected users
read schedule change? user request (1A)
only)
N
Notice:
Meter Route
Notice
Change
(GIP 75)
1A. Request for Notification of

Current User
change to meter failed request for Amended meter

read schedule Notice change to meter route details
read frequency
3. Review Amended meter

Affected users
proposed route details

schedule change
Minimum notice (as per above Note)

Page 1 of 1
Request for change to Meter Reading
Schedule

Process Flow: MR3: Request for historical data
PF(B2B) - MR3: Request for historical data

Market Operator

1-3 167
Notes: The rules state that historical data can be sent to a user without checking if they were the valid user based on the warrant
implicit in the initial user request.
Details of User responsibilities are in R167A
R167 refers to a notice of request withdrawal not shown in this flow.
Network Operator
Energy History Response

Request for
2. Consider if user (GIP 46)
historical metering
is current user for CSVHistoryResponseData
or meter reading 3. Send data
request period <<electronic file>>
data
(not mandatory)
Energy History
Request
(GIP 45)
<<Fax or e-mail>>
Meter reading
data daily (Basic)
Current User
1. Request Bulk data

historical meter <<electronic file>>
reading Meter reading
data daily
(Interval)
NO to provide information in 5 business days unless this is unreasonable due

to too many requests
Data is supplied on this basis for two years after which it is supplied for at least
a further 5 years in a format which is accessible within a reasonable period of
time.

Page 1 of 1
Request for historical data B2B Working Group Pending

Process Flow: MR4A: Special meter reading response (basic meters only)
PF(B2B) - MR4A: Special meter reading response (basic meters only)
To:
Process Step RMR Ref PF(B2M) -
Market Operator
1-7 147 R1.1
Notes:
Standard Service Order cancellation process applies Energy Flow for
See also MR4B: Deemed meter reading (basic meters only) Special Read
R99 - '99. Network operator may be required to undertake special meter reading for a move in' is related to this
flow and may be the subject of a separate process flow
Network Operator
2. Log Special 3. Generate

Special Read Read Request / Service Provider 5. Special
4. Read basic 6. Current 7. Send MeterDataNotification
Request Confirm request reference and Read Y Y
meter user? metering data <<aseXML>>
date is 2 days process obtained?
after lodgement request
N
SpecialReadResponse
(GIP 6)
[responseType="Closure"]
<<aseXML>>
SpecialReadRequest
Current User
SpecialReadResponse
(GIP 3)
(GIP 3A)
[actionType="New"]
[responceType="Initial"] Special Read
<<aseXML>> Energy Flow for
<<aseXML>> Request -
Special Read
No Access Advice
Requesting User
1. Nominate Day Special Read

and Generate Request
Special Read Response
Request
At least 2 business days after receipt of request

Page 1 of 1
Special meter reading response (basic
meters only)

Process Flow: MR4B: Deemed meter reading (basic meters only)
PF(B2B) - MR4B: Deemed meter reading (basic meters only)

To:
Market Operator
2-4 148
PF(B2M) -
R1.1
Notes:
Network Operator will check at approx 8 days to see if an actual read is achieved and decide if a special read Energy Flow for
should be initiated. Special Read
See also MR4A: Special meter readings (basic meters only)

Network Operator
2. Was an
3. Calculate
actual read Y MeterDataNotification
1. Read basic deemed 4. Send
achieved <<aseXML>>
meter meter read for metering data
in the 10 day period?
move in
N
Current User
To:
PF(B2B) - Energy Flow for
MR4A Special Read
Requesting User
Up to10 days between meter

read and date of move in

Page 1 of 1
Deemed meter reading (basic meters only) B2B Working Group Pending

Process Flow: MR5: Account creation
PF(B2B) - MR5: Account creation

Market Operator
1. Send transfer 1-2 103

confirmation
Notes:
Not all standing data is provided in the AccountCreationNotification for SA. This missing data is
obtained in the separate MIRN Discovery process.
Refer to R 103 (2) and (3) for details re the timing of the standing data and the basis in whcih
this is sent to incoming users for SA
Network Operator
Transfer 2. Process
confirmation transfer
confirmation
AccountCreationNotification
(GIP 12 (or 231))
<<aseXML>>
Current User
Incoming User
Account Creation
Transaction

Page 1 of 1
Account creation B2B Working Group Pending

Process Flow: MR6: Annual Meter reading schedule
PF(B2B) - MR6: Annual Meter reading schedule

1-3 144
Market Operator
Notes:
Also see PF(B2B): MR7: 'Meter Reading Schedule Amendment'
Network Operator
1. Prepare 3. Incoming
2. Send schedule
schedule user during the
to current users
(by August 31) year?
Y
Annual Meter Reading Schedule
(GIP 74)
CSV
<<Electronic File>>
Current Users
Annual Meter Reading Schedule

(GIP 74)
CSV
Annual meter <<Electronic File>>
reading schedule
Incoming User
Annual meter
reading schedule

Page 1 of 1
Annual Meter reading schedule B2B Working Group Pending

Process Flow: MR7: Meter Site Access/Address Change from User (SA)
PF(B2B) - MR7: Meter Site Access/Address Change from User (SA)

Market Operator
1-4 61
Notes:
This process is not for updating standing data.
Meter Site Access

Network Operator
Information 4. Receive and log

Change from User notice of access
details change
Meter Site Access Information Change from User/RB

(GIP 66) ACK or NACK
and / or Meter Site Access Information Change from User/RB
Supply Point Information (GIP 68)-
AmendMeterRouteDetails/ CSVAmendSiteAddressDetails
<<aseXML>>
Current User
Meter site access/

address change
2. Receive notice ACK or NACK
3. Send change of
of site access
access message
details change
1. Customer
request
Customer
changes to
access/address
information

Page 1 of 1
Meter Site Access/Address Change from
User

Process Flow: MR7A: Address Change from User (WA)
PF(B2B) - MR7A: Address Change from User (WA only)

1-4 61
Market Operator
Notes:
The process operates on the principle that the Network Operator holds the database of record for the address. The
Retailer will only update its Site Access/Address Database when it receives an update from the Network Operator.
The CSV file sent from the User will contain only a single address (to avoid problems with partial acceptance of files)
The AmendMeterRouteDetails/CSVAmendSiteAddressDetails transaction from the Network Operator contains a full
refresh of all data - not only those elements that have changed.
6. Update Network
Site Access/ Y Operator’s Site Access/
Network Operator
Address Change 4. Accept change of

Address Database and
from User Access/Address?
issue change of data
message
N
Meter Site Access Information Change from User (GIP 66) or
Supply Point Information (GIP 68) - Meter Site Access Information Change from Network Operator (GIP 76)
AmendMeterRouteDetails/ CSVAmendSiteAddressDetails Supply Point Information (GIP 69) -
NACK
<<aseXML>> AmendMeterRouteDetails/ CSVAmendSiteAddressDetails
note: contains single address only <<aseXML>>
Current User
2. Record change 3. Send change of 5. Log response Site Access/

Address Change 7. Update Current
of site access/ Site Access/ from Network User’s Site
address details Address message Operator from Network
Operator Access/Address
Database
1. Customer
request
Customer
changes to
access/address
information

Page 1 of 1
Meter Site Access/Address Change from
User B2B Working Group Pending

Process Flow: MR8: Meter Site Access Change from NO
PF(B2B) - MR8: Meter Site Access Change from NO

Market Operator
1-2 61
1-2 62
Notes:
1. Determine site
2. Send change of
Network Operator
access details
access message
have changed
Meter Site Access Information Change from NO/DB (GIP 67)

and/or
Address Information Change from NO/DB (GIP 69)
AmendMeterRouteDetails/ CSVAmendSiteAddressDetails
<<aseXML>>
Current User
Meter Site Access

Information
Change from NO

Page 1 of 1
Meter Site Access Change from NO B2B Working Group Pending

Process Flow: MR10: Service recommissioning by request (WA)
PF(B2B): MR10: Service recommissioning by request
Process Step RMR Ref Reconnection confirmation Reconnection

/ MIRN Status Update confirmation
Market Operator
1 117 notice notice To:

2 118 and PF(B2M)
3-6 119 Meter Data Notification - R5
<<aseXML>> Metering
Notes:
R120 - 124 relate to the receipt of the reconnection notice by Market Operator data
This beginning of this flow is different to a generic service order in terms of the required rejection process.
ServiceOrderRequest 2. Valid Y 5. Change MIRN

Network Operator
3. Accept request 4. Reconnect and 6. Send data to

(GIP 314: reconnection status to active
and notify user calculate actual Market Operator
Service Orders request? and notify user
for Priority C-K)
N
[actiontype='New']
[JEC='MTN' or 'SCR'] ServiceOrderResponse
<<aseXML>> ServiceOrderResponse (GIP 315)
‘NACK’ (314A - ACK) [responsetype='Closure']
(event code?) [responsetype='Initial'] <<aseXML>> Meter
<<aseXML>> Data
Notification
Service <<aseXML>>
Reconnection
Initial Complete
Current User
Service
1. Service Service
Reconnection
Reconnection Reconnection
Request -
Request Request -
Response
Response
Metering
data
R118 - If reconnection notice is not valid - immediately notify

and provide reason.
All participants
R119 - Immediate reply to valid request is required
Two business days Two business days

Page 1 o 1
Service recommissioning by request B2B Working Group Pending

Process Flow: MR11C: Deregistration by request (WA)
PF(B2B) - MR11C: Deregistration by request (WA)
Process Step RMR Ref GasMeterNotification/

MIRNStatusUpdate Removal
1-2 125
Market Operator
(GIP 158 - MIRN Status confirmation To:

2 126
Update) notice PF(B2M) -
3-6 127
<<aseXML>> R6
Notes: Metering
For WA the Meter is removed and the pipe is left. This differs from the two step SA process of meter data
removal and subsequent pipe removal.
Please refer to: MR11A and MR11B for the SA deregistration process:
Meter Data Notification
<<aseXML>>
Network Operator
5. Calculate actual,
Meter 2. Valid 3. Accept change MIRN status to 6. Send data
removal request removal Y notification and 4. Read and remove meter deregistered to Market
request? respond to user and notify user and Operator
Market Operator
N
Meter Removal Request

ServiceOrderResponse
(GIP 151) ServiceOrderResponse
‘NACK’ (GIP 151A)
[actionType='New'] (GIP 157- Meter Disconnection Complete)
(event code?) [responseType='Initial']
Various JobEnquiryCodes [responseType='Closure']
<<aseXML>>
Current User
Delivery point Delivery point

1. Lodge
removal request - removal request -
Request Meter removal
rejection response response.
Complete
Maximum of five
One business day business days
Later of two days or the date requested by User (maximum of 20 business days)

Page 3 of 3
Deregistration by request (WA) B2B Working Group Pending

Process Flow: MR12: Upgrade from basic to interval meter (SA)
MR12: Upgrade from Basic to Interval Meter (SA)

Customer
1. Request an 1a. Request an

Upgrade to Go To MIRN1.1 Upgrade to Go To MIRN1.1
Interval Meter Part1.2 Interval Meter Part2.2
from DB from Retailer
Retailer
2. Retailer
identifies need for Go To MIRN1.1 13. Receive
From REQ5B 14
Basic to Interval Part2.1a Completion Advice
Meter Upgrade
Email or
From MIRN1.1
3. Distributor Part 2.16
identifies need for Go To MIRN1.1
Email 12. Update
Basic to Interval Part 2.1b
8. Commission System And Send
Meter Upgrade
Interval Meter Completion Advice
Distributor
to Retailer
6. Confirm Receipt
of Signed
4.Confirm Receipt Acceptance
From REQ5B.9
of Service Order
9. Complete & Send 11. Receive

Data Change Notated Standing
5 Confirm
7. Install Notificaton (DCN) Data Update
From REQ6.2 Completion of
Telemetry
Field Work
Email
10. Update Meter Register

AEMO
GIP 125
to ‘Active’ Interval
<<aseXML>>
Metering & Send Standing
Email
Data Update

Process Flow: MR12: Upgrade from basic to interval meter (WA)
PF(B2B) - MR12: Upgrade from basic to interval meter

1-5 139 Metering
data
Market Operator
1-5 141
Notes:
The trigger for these flow could be at least a direct request from the user or as a result of the market operator meter upgrade process Data change To:
Refer to PF(B2M) - M4 notice PF(B2M)
The flow for the reduction of a meter from interval to basic is not shown. These actions are described in R140. - "Meter R2
After an upgrade or downgrade the NO must provide (via aseXML) the user with the meter standing data and MIRN standing data for Type" has
the delivery point before providing the metering data. changed
It was agreed that the 'ServiceOrderResponse' in this instance would not be automated as the user could provide a Meter Data Notification
service order or interface with the NO via a manual process. <<aseXML>>
Request
5. Upgrade
Basic Meter 2. Prepare
Network Operator
meter and
Upgrade qoute <<email>>
send notices
ServiceOrderR
esponse
ServiceOrder Request (GIP 125)
GIP 120 (GIP 121) (GIP 122) <<email>>
Manual process Manual process <<aseXML>>
or
Manual process
Quote for Accept Meter

1. Request
Upgrade of Quote for Upgrade
basic meter
Basic Meter Upgrade of Completed
Current User
upgrade
Basic Meter
Y Metering
3. Negotiate
4. Accept data
with
quote?
NO
Within 20 days of notice or conclusion of dispute process (managed by Market

Operator)

Page 1 of 1
Upgrade from basic to interval meter B2B Working Group Pending

Process Flow: MR13: Generic Energy Flow
PF(B2B) - MR13: Generic Energy Flow

NA
Market Operator
Other references:
As per the Interface Definitions Document:
- 4.1.2 Provision of Energy Flow Data
- Figure 4.1 Provision of Energy Flow Data Activity Diagram
Notes:
This generic flow applies where energy flow data is required to be sent from a Network Operator to the User.
The MeterDataResponse transaction will identify whether the processing was:

- Successful - all CSV records were successfully processed
Network Operator
- Partially successful - processing of some CSV records failed

- Failure - no processing of the CSV data was possible. Meter data
1. Send meter 4. Process
response
data response
Relevant Meter Data Notification (GIP) MeterDataResponse

transactions: <<aseXML>>
<<aseXML>>
9 - Energy Flow for Special Read (Not customer Relevant Meter Data Response transactions
transfer) (GIP):
13 - Energy Flow for Special Read (Customer
transfer) 2. Save and 3. Reply with
Metering data 9A - Energy Flow for Special Read (Not customer
17 - Energy Flow for Disconnection Read process metering meter data
transfer) Response,
User
41 - Energy Flow for Scheduled or Special Read data response

13A - Energy Flow for Special Read (Customer
50 - Energy Flow for Missing Reads transfer) Response
51 - Energy Flow for Estimated Read 17A - Energy Flow for Disconnection Read
53 - Energy Flow for Substituted Read Response
246 - Energy Flow Adjustment for RB Possible read reason codes provided with 41A - Energy Flow for Scheduled or Special Read
Meter Data Notification messages: Response
50A - Energy Flow for Missing Reads Response
"SRF" = Special Final Read; 51A - Energy Flow for Estimated Read Response
"SRR" = Special Reference Read; 53A - Energy Flow for Substituted Read Response
"SRA" = Special Account Investigation; 246A Energy Flow Adjustment for RB Response
"SRD" = Special Disconnection;
"SRT" = Special Transfer Read;
"SCH" = Schedule Cycle Read;
"INI" = Meter Installation Read;
"REM" = Meter Remove;
"OSO" = Other Service Order; and
"MDV" = Meter Data Verify (residual)

Page 1 of 1
Generic Energy Flow B2B Working Group Pending

Process Flow: MR14: Downgrade from Interval to Basic for Tariff D (SA)
MR14: Downgrade from Interval to Basic Meter for Tariff D (SA)

Customer
1. Request
Go To MIRN1.1
Downgrade to a
Part 2.2
Basic Meter
Retailer
2. Retailer
16. Receive
identifies need for Go To MIRN1.1 14. Receive SO
From REQ5B.9 From REQ5B.14 Downgrade
Interval to Basic Part2.1a Completion Advice
Advice
Meter Downgrade
Email
Go To MIRN1.1 5. Confirm Receipt 12. Remove 15. Advice

Part2.1b 4. Confirm Receipt From MIRN1.1
of Signed Telemetry Downgrade
of Service Order Part2.16
Acceptance Equipment Completion
Email
Distributor
3. Distributor
identifies need for
Interval to Basic 13. Update
Meter Downgrade System and set
7. Amend & 11. Receive
Meter to ‘Basic’
Resubmit DCN Standing Data
Request Confirmation
6. Prepare & Send Email
Data Change
Notification (DCN) Email
Request
No Email
Email
AEMO
8. Receive & 10. Update Meter Register

9. DCN
Validate DCN Yes to ‘Basic’ Metering & Send
Request Valid?
Request Standing Data Notice

5. Requests and Service Orders
Requests and Service Orders

Process Flow: REQ1: Meter Data Verification
PF(B2B) - REQ1: Meter Data Verification

Market Operator

To:
5 Part 4.4 PF(B2M) -
M2
Notes:
Meter Meter
Data (basic) Data (interval)
Meter
Data
Network Operator
Notification
For basic meters <<aseXML>>
<<Automated
MeterDataVerifyRequest Meter Data
Y electronic file>>
(GIP 242) Verification 4. Log and 5. System 6. Basic or
<<aseXML>> Request process request updated? Interval?
For interval meters
<<e-mail>> <<Electronic File>>
For basic meters -
MeterDataVerifyResponse Meter
(GIP 243) Data
<<aseXML>> Notification
For interval meters - <<aseXML>>
Current User
2. Billing failure 3. Request meter <<e-mail>>

identified data verification
Meter Meter
Meter Data Data (basic) Data (interval)
Verification
Response
Customer query
<<Phone, fax. email>>

Customer
1. Bill query

1 of 1
Meter Data Verification

Process Flow: REQ2: Missing data reads
PF(B2B) - REQ2: Missing data reads

Market Operator
None
Notes:
Energy Flow
Missing Reads
Network Operator
Missing meter For basic meters

reading data 2. Process MeterDataNotification
request missing data (GIP 50)
request <<aseXML>>
For interval meters
<<electronic file>>
For basic meters (and interval meters in WA)
MeterDataMissingNotification
(GIP 49)
<<aseXML>> Energy Flow
For interval meters in SA Missing Reads
<<e-mail>>
Current User
1. Request
missing meter
reading data
Customer

1 of 1
Missing data reads B2B Working Group Pending

Process Flow: REQ3: Notification of Mains/Service
PF(B2B) - REQ3: Notification of Mains/Service

Market Operator
None
Notes:
Associated process 'REQ4: Request - Notification of Data Change'
Network Operator
1. Generate
notification
FieldWorkNotification/ CSVMainsServiceRenewal
(GIP 330)
<<email>>
Current User
Notification of
mains/service
renewal
Customer

1 of 1
Notification of Mains/Service

Process Flow: REQ4: Notification of Data Change
PF(B2B) - REQ4: Notification of Data Change

Market Operator
1-2 62
2 27
Notes:
Associated process 'REQ3: Request - Notification of Mains/Service'
A data change notice may be required for Market Operator for a Gas Zone or Meter
Type change or if the delivery point is no longer in the NO's GDS
Network Operator
2. Generate notification for

change to:
1. Update MIRN/ - Heating value zone, -
MSD database transmission zone, or
distribution tariff
(BL and HR for SAustralia)
Notice
Current User
Standing Data
Change from DB/
NO
Customer

1 of 1
Notification of Data Change

Process Flow: REQ5A: Service Orders General (detailed) WA
PF(B2B) - REQ5A: Service Orders General (detailed)

None Market Operator
Market Operator
notification for any Meter

Notes: changes effecting Data
The Service Orders General is presented with all relevant service orders named (REQ5A detailed) and as a generic flow without Meter Status
service orders named (REQ5B simplified).
Two other associated service order flows are:

- A distributor initiated service order: Process Flow (B2B): REQ6: Request - DB initiated Service Orders Basic: Meter Data
- A service order cancellation flow: Process Flow (B2B): REQ7: Request - Service Orders Cancellation Notification
Meter Status Change(GIP 94)
<<aseXML>>
MIRN Status Change(GIP 158)
Interval:
Service Orders: C-K <<aseXML>>
GIP 87 - Meter Fix Request <<automated
GIP 101 - Meter Change Request electronic file>>
Network Operator
GIP 151 - Meter Removal Request

GIP 310 - Service Connection Request 3. Log Service
GIP 312 - Service Disconnection Request Y
GIP 314 - Service Orders for Priority C-K
Order and return
work request 5. Site access 6. Close service
GIP 316 - Relocate Service Request 4. Attempt service y 7. Was read
GIP 318 - Upgrade Service Size Request number available (if order request
requested taken?
GIP 320 - Upgrade Meter Size Request required) and respond
N Y
ServiceOrderResponse ServiceOrderResponse
[responseType='Initial'] ServiceOrderResponse Basic: Meter Data
[responseType='Closure' [responseType='Closure']
<<aseXML>> <<aseXML>> Notification
ServiceOrderRequest <<aseXML>> <<aseXML>>
[actionType='New']
Interval:
<<aseXML>>
Service Order response: C-K Service Order response: C-K
<<electronic file>>
Current User
GIP87A - Meter Fix Request Response Service Order response: No Access GIP 92 - Meter Fix Completed
GIP 101A - Meter Change Request Response GIP 93 - No Access to Complete Meter Fix GIP 311 - Service Connection Complete
GIP 151A - Meter Removal Request Response GIP 104 - No Access to Complete Meter GIP 313 - Service Disconnection Complete
GIP 310A - Service Connection Request Response Change GIP 317 - Relocate Service Complete
2.Current user GIP 312A - Service Disconnection Request Response GIP 154 - No Access to Complete Meter GIP 319 - Upgrade Service Size Complete Meter
GIP 314A - Service Orders for Priority C-K Response Removal
requests service GIP 321 - Upgrade Meter Size Complete Data
GIP 316A - Relocate Service Request Response
order GIP 318A - Upgrade Service Size Request Response
GIP 320A - Upgrade Meter Size RequestResponse
Additional notes:
Customer
Notes related to transfers and the Service Order process:

1. Customer
- Current User at time of closure will receive completion of service order notification (closure notification). The CU needs to know this in case the transfer fails.
requests service
- Current user will receive MDN.
- Incoming user will be charged for service.
- Incoming user will be provided with metering data when the transfer is complete via new connection notice.
- If current user is notified of a completed service order related to transfer request then current user will know to expect completed transfer notice within 3 business days.

1 of 1
Service Orders General (detailed) B2B Working Group Pending

Process Flow: REQ5B: Service Orders General (SA - simplified)
REQ5B: Service Orders General (Simplified) (SA)

Customer
Where rejected, Retailer takes

appropriate action e.g. Initiate
1. Request a new service order request and Wait for service order
Service current process ends. response ‘Closure’
15. Receive
2. Send Service 6. Receive 8. Receive Service
1a. Request a 7. Was Service Service Order
Order (SO) Acceptance/ Yes Order Response
Service Order Accepted? Response
C-K Rejection (Initial)
Up to 5 BD From (Closure)
Expected Completion of Step 10
Retailer
No
Up to 5 BD from Expected
Completion of Step 10
From MIRN1.1
Part 2.18
Go To MR12.4 or
ServiceOrderRequest MR14.4 as applicable
[actionType=’New’] ServiceOrderResponse
<<aseXML>> Transaction ServiceOrderResponse
Acknowledgment [responseType=’Closure’]
#1 [responseType=’Initial’] <<aseXML>>
<<aseXML>> <<aseXML>> #3
#2 Go To MR12.13 or
Yes MR14.14 as
3. Receive Service 9. Log Service applicable
5. Send Validation 10. Action Service
Order Request & Order & Send
Outcome Order
Validate Response
14. Upgrade or
13. Send Service No
Downgrade?
Order Response
No No
Distributor
11. Has SO 17. Does SO

been Require
4. Valid Service Completed? Yes
Yes Notification to
Order Request? AEMO?
Yes
No
18. Send
12. Was Additional 16. Does SO Type Notification to
Go To MR13.N Meter
Go To REQ6.2 Yes or Alternative No Yes Require Delivery No AEMO
Data Delivery
Work Completed? of Meter Data?
<<aseXML>>
#4
This process wasn’t reviewed as part of
IN017/13. IN027/13 has been created
AEMO
to raise awareness that when Meter

19. Action
Data Delivery process is reviewed
Notification
revisit this process flow diagram
#1, 2, 3 & 4 Refer to REQ5B Det for the transactions involved

Process Flow: REQ5B: Service Orders General (WA - simplified)
PF(B2B) - REQ5B: Service Orders General (simplified)

None
Market Operator
Market Operator
notification for any Meter
changes effecting Data
Notes:
Associated flows are: Meter Status
- REQ6: DB initiated Service Order; and
- REQ7: Service Order Cancellation
Basic: Meter Data
Meter Status Change and Notification
MIRN Status Change <<aseXML>>
(GIP 94 and GIP 158) Interval:
<<aseXML>> <<automated
electronic file>>
Network Operator
Y
3. Log Service
Service Orders : 5. Site access 6. Close service
Order and return 4. Attempt service Y 7. Was read
C-K available (if order request
work request requested taken?
required) and respond
number
N
Y
Basic: Meter Data
ServicePrderRequest ServiceOrderResponse ServiceOrderResponse ServiceOrderResponse Notification
[actiontype='New'] [actiontype='Initial'] [responseType='Closure' [responseType='Closure' <<aseXML>>
<<aseXML>> <<aseXML>> <<aseXML>> <<aseXML>> Interval:
<<electronic file>>
Current User
2.Current user Service Order No access Service Service Orders Meter

requests service response: C-K Order responses response: C-K Data
order
Customer
1. Customer
requests service

1 of 1
Service Orders General (simplified) B2B Working Group Pending

REQ5B: Det: Service Orders Transaction Table (SA)
REQ5B Det: 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
GIP 87A - Meter Fix Request Response GIP 92 - Meter Fix Completed GIP 94 - Meter Fix Notification
(JEC = MFX)
GIP 93 - No Access to Complete Meter
Fix
GIP 101 - Meter Change Request GIP 101A - Meter Change Request GIP 104 - No Access to Complete Meter
(JEC = MCH) Response Change
GIP 108 - Meter Change Completed
GIP 125 - Meter Upgrade Completed

GIP 151 - Meter Removal Request GIP 151A - Meter Removal Request GIP 154 - No Access to Complete Meter GIP 158 - MIRN Status Update
(JEC = MRM) Response Removal Notification
GIP 157 - Meter Removal Completed
GIP 310 - Service Connection Request GIP 310A - Service Connection Request
GIP 311 - Service Connection Complete
(JEC = SCR) Response
GIP 312 - Service Disconnection Request GIP 312A - Service Disconnection Request GIP 313 - Service Disconnection GIP 158 - MIRN Status Update
(JEC = SDR) Response Complete Notification
GIP 314 - Service Orders for Priority C-K GIP 314A - Service Orders for Priority C-K GIP 315 - Service Orders Completed for
(JEC = All JEC's) Response Priority A-K
GIP 316 - Relocate Service Request GIP 316A - Relocate Service Request
GIP 317 - Relocate Service Complete
(JEC = RSR) Response
GIP 318 - Upgrade Service Size Request GIP 318A - Upgrade Service Size Request GIP 319 - Upgrade Service Size
(JEC = USR) Response Complete
GIP 320 - Upgrade Meter Size Request GIP 320A - Upgrade Meter Size Request
GIP 321 - Upgrade Meter Size Complete
(JEC = UMS) Response
JEC = Job Enquiry

Process Flow: REQ6: DB initiated Service Orders (SA)
REQ 6: Distributor Initiated Service Orders (SA)

Distributor initiated work at

3. Receive &
the site requires update to
Validate Service 4. Update System
retailer/AEMO
Retailer
Order Response Data

This includes Time Expired
(C-K)
Meters
From MIRN1.1 Part ServiceOrderResponse

[responseType=Closure] Go To MR12.5
1.15
<<aseXML>>
#3
2. Send Service
1. Complete Field 5. Does SO Require
Order Response Yes
Work Notification to AEMO?
(C-K)
No
Distributor
From REQ5B.12
Go To MR13.N 6. Does SO Type 7. Send

Meter Data Yes Require Delivery of No Notification to
Delivery Meter Data? AEMO
<<aseXML>>
#4

AEMO

Data Delivery process is reviewed 8. Action
revisit this process flow diagram Notification
#3 & 4 Refer to REQ5B Det for the transactions involved

Process Flow: REQ6: DB initiated Service Orders (WA)
PF(B2B) - REQ6: DB initiated Service Orders

None
Market Operator
Market Operator
Notes: notification for any Meter
Associated flows are REQ5A: Service Order General and REQ7: Service Order Cancellation changes affecting Data
DB/NO initiated Service Order Responses: Meter Status
- SA. If a DB service order is raised and issued to a site with a MIRN then the retailer is notified via a
Service Order Response Basic: Meter Data
- WA. Not all actions will be reported back to the retailer. A Service Order Response may be sent Notification
Meter Status Change and
where a DB initiated SO affects standing data or has a customer impact. <<aseXML>>
MIRN Status Change
Interval:
(GIP 94 and GIP 158)
<<automated
<<aseXML>>
electronic file>>
Network Operator
3. Close service
1. Iniitiate Service 2. Attempt service 4. Was read
order request
Order: A - K requested taken?
and respond
Y
Basic: Meter Data

ServiceOrderResponse Notification
[responseType='Closure' <<aseXML>>
<<aseXML>> Interval:
<<electronic file>>
Current User
Service Orders Meter

response: A-K Data

1 of 1
Service Orders General (simplified) B2B Working Group Pending

Process Flow: REQ6B: DB varied Service Orders WA
PF(B2B) - REQ6B: DB varied Service Orders

None
Market Operator
Notes:
Market Operator
This flow shows the scenario in which a Network Operator/DB carries out work in the field which is in addition to, or differs from that requested Meter
notification for any
by the User. The diagram shows that the Network Operator will close the original service order and initiate an additional service order as Data
changes affecting
required. As a DB initiated service order this requires a 'Closure' response and possible provision of metering data.
Meter Status
Associated flows are REQ5B: Service Order General, REQ6A: DB initiated Service Orders and REQ7: Service Order Cancellation
DB/NO initiated Service Order Responses:
Basic: Meter Data
- SA. If a DB service order is raised and issued to a site with a MIRN then the user is notified via a Service Order Response
Meter Status Change and Notification
- WA. Not all actions will be reported back to the user. A Service Order Response will be sent where a DB initiated SO affects standing data or
MIRN Status Change <<aseXML>>
has a customer impact.
(GIP 94 and GIP 158) Interval:
<<aseXML>> <<automated
electronic file>>
Network Operator
Y
Service Orders : 3. Log Service
4. Additional or Y 5. Initiate
C-K Order and return 4. Close Service 7. Was read
alternative work additional service 6. Complete Work
work request Order taken?
required? order
number
Y
Y N
Process Ends Basic: Meter Data
ServicePrderRequest ServiceOrderResponse ServiceOrderResponse Notification
[actiontype='New'] [actiontype='Initial']
[responseType='Closure' <<aseXML>>
<<aseXML>> Interval:
<<electronic file>>
SO Closure as
Current User
per:
2.Current user Service Order PD(B2B) Service Orders Meter
requests service response: C-K REQ5B response: A-K Data
order Step 5
1. Customer
requests service
Customer

1 of 1
DB varied Service Orders B2B Working Group Pending

Process Flow: REQ7: Retailer Initiated Service Orders Cancellation (SA)
REQ 7: Retailer Initiated Service Orders Cancellation (SA)

Customer
1. Request a Same day cancellations

Service order to must also be phoned through Where cancellation is rejected
be Cancelled the original SO will continue to
be actioned
Retailer takes appropriate action
2. Send Service
1a. Request a 6. Receive 7. Was SO
Order (SO) 8. Receive Service 9. Update System
Service order to Acceptance/ Cancellation Yes
Retailer
Cancellation Order Response Data

be Cancelled Rejection Accepted?
C-K
ServiceOrderRequest
[actionType=’Cancel’] No
<<aseXML>> Transaction
#1 Acknowledgment ServiceOrderResponse
<<aseXML>> [responseType=Closure]
<<aseXML>>
#3
Up to 5 BD from Expected
Completion of Step 10
3. Receive Service
5. Send Validation
Order Cancellation
Outcome No
& Validate
12. Send Service
Distributor
Order Response
No
Yes
4. Valid Service 10. Attempt to
11. Can Initial SO
Order Cancel Yes Cancel Initial SO
be Cancelled?
Request? Request
Where cancellation is
rejected the original SO will
continue to be actioned
#1 & 3 Refer to REQ5B Det for the transactions involved

Process Flow: REQ7: Service Orders Cancellation (WA)
PF(B2B) - REQ7: Service Orders Cancellation

Market Operator
None
Notes:
Associated flows are REQ5A:Service Order General
To change a previosly submitted Service Order, a cancellation and subsequent Service Order submission is
required
Service Order
Y
Network Operator
Able to cancel
Request
Service Order?
ServiceOrderReponse
[responseType=”Closure”
<<aseXML>>
N
ServiceOrderRequest
[actiontype='Cancel'] “NACK”
<<aseXML>>
Current User
1.Current user
2. Process 3.Process
cancels service
Response Cancellation
order
Customer

1 of 1
Service Orders Cancellation B2B Working Group 14/11/03

Process Flow: REQ8: Implied service recommissioning and (following transfer withdrawal) an implied service de-commissioning (SA)
REQ8: Implied Service Recommissioning & (Following Transfer Withdrawal) an Implied Service Decommissioning (SA)
Notes:
Incoming
A transfer request by an incoming retailer is deemed as a request for the distributor to reconnect a
Retailer
Service Service
decommissioned basic metered delivery point (as per R82)
Reconnection Decommission
If the incoming retailer lodges a transfer withdrawal notice (as per R95) after the distributor has executed the
Complete Complete
reconnection but before AEMO has marked the transfer as completed, the distributor is deemed to have a
request to disconnect the delivery point.
If the transfer withdrawal notice is invalid the distributor does nothing.
ServiceOrderResponse ServiceOrderResponse
Retailer
Current
(GIP 315) Meter Data (GIP 315 SO completed for

Meter Data Priority A to K) Meter Data
[responseType=’Closure’] Notification
<<aseXML>> <<aseXML>> [responseType=’Closure’]
<<aseXML>>
Implied
Disconnection For Basic Meter:
1. Reconnect & Request from 6. Change MIRN Meter Data Notification
3. Send Data to
Obtain Meter Transfer Status to Blocked <<aseXML>>
AEMO
Read Withdrawal & Notify Retailer For Interval Meter:
Distributor
<<electronic file>>
7. Send Data to
Implied Yes
AEMO
Reconnection 2. Change MIRN
Request from 4. Valid Transfer 5. Read Meter &
Status to Active &
Transfer Withdrawal? Disconnect
Notify Retailer
Process MIRN Status Update (GIP 158) &
No
Ends For Basic Meter:
Reconnection Confirmation <<aseXML>>
GasMeterNotification/ For Interval Meter:
MIRN Status Update (REC-CON) & To <<automated electronic file>> To
Meter Data Notification Meter Data PF(B2M) PF(B2M)
<<aseXML>> – R5 Meter Data – R4
AEMO

Data Delivery process is reviewed Reconnection Disconnection
revisit this process flow diagram Confirmation Confirmation
Notice Notice

Process Flow: REQ8: Implied service re-commissioning and (following transfer withdrawal) an implied service de-commissioning (WA)
PF(B2B): REQ8: Implied service re-commissioning and (following transfer withdrawal) an implied service decommissioning
Process Step RMR Ref MIRN Status Update (GIP

Reconnection confirmation 158) and
1-8 82 for basic meter: To:
GasMeterNotification/ To:
Market Operator
4 95 Meter Meter Data Notification PF(B2M) -

MIRN Status Update (REC-CON) PF(B2M) Meter Data
Data <<aseXML>> R4
and - R5
Meter Data Notification for interval meter
<<aseXML>> <<automated electronic Disconnection
Reconnection
file>> confirmation
confirmation
notice
notice
Implied Implied
Reconnection Disconnection
2. Change MIRN
Network Operator
Request from 3. Send data to Request from

status to active 6. Change MIRN
transfer Market Operator transfer 5. Read meter 7. Send data to
and notify user Y status to blocked
withdrawal and disconnect Market Operator
and notify user
1. Reconnect and 4. Valid transfer

obtain meter read Process ends For basic meter:
withdrawal? N
Meter Data
Notification
<<aseXML>>
Meter
ServiceOrderResponse For interval meter:
ServiceOrderResponse Data
(GIP 315 Service Order <<electronic file>>
(GIP 315) Notification
completed
[responsetype='Closure'] <<aseXML>>
Current User
for priority A to K)
<<aseXML>> [responseType='Closure
Notes: <<aseXML>>
Meter
A transfer request by an incoming user is Meter Data
Data
deemed as a request for the
network operator to reconnect a
decommissioned basic metered delivery
point (as per R82).
Service If the incoming user lodges a transfer Service

Reconnection withdrawal notice (as per R95) after the Decommission
Complete network operator has executed the complete
Incoming User
reconnection, but before Market Operator has

marked the transfer as completed, the network
operator is deemed to have a request to
disconnect the delivery point.
If the transfer withdrawal notice is invalid the
network operator does nothing.

FRC B2B Process Flows for SA and WA Gas Markets

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FRC B2B Process Flows for SA and WA Gas Markets

Uploaded by

Copyright:

Available Formats

FRC B2B Process Flows

For the SA and WA Gas Retail Markets

This approach is to promote interchange-ability in these documents for the benefit of

The terms and there relevant definitions are as follows:

Term: South Australian Market Western Australian

B2B Process Flows v3.4 2

B2B Process Flows v3.4 3

B2B Process Flows v3.4 4

 Retail Market Rules,

 Victorian Gas Market physical transaction name;

5. The drawing conventions used for these diagrams are as follows:

aseXML Message Description  Notes

B2B Process Flows v3.4 5

 Data Base and MIRN

 Interface Control Document

B2B Process Flows v3.4 6

B2B Process Flows v3.4 7

PF(B2B) - DB 1: Requested DB updates

Process Step RMR Ref

1A. Change 2A. Produce Notification

Two business days Five business days

Project Prepared by Date

B2B Process Flows v3.4 8

PF(B2B) - DB 2: Street Suburb Table Update

Process Step RMR Ref

Website (view or download)

2. View/Download Street Suburb

Project Prepared by Date

B2B Process Flows v3.4 9

B2B Process Flows v3.4 10

PF (B2B) MIRN 1: New Connection – Service Connection Request (SA)

1a. Raise 1b. Raise 9. Receive

applicable response will be provided

GIP 310/Email Mail/Email/Fax

Go To MIRN1.1 Part Go To MIRN1.1 Part From MIRN1.1 Part

B2B Process Flows v3.4 11

MIRN 1.1 Part 1 Connection Request/Shipper – No Retailer (SA)

1b. Request a 7. Does the

B2B Process Flows v3.4 12

MIRN 1.1 Part 2 Connection Request/Shipper – Retailer Assigned (SA)

If rejected, resolve issues

6. Receive 12. Accept

From MR12.1a or 2. Prepare

1a. Request a Phone/Fax/Email

11. Advise Customer

8. Does the Go To MIRN1.7 or

Notes: Service Order Enquiry Code

B2B Process Flows v3.4 13

PF(B2B): MIRN3: New Connection (WA)

Process Step RMR Ref

Project Prepared by Date

B2B Process Flows v3.4 14

PF(B2B): MIRN 4A: Standing data request/MIRN discovery by MIRN

Process Step RMR Ref

NMI Standing Data Y Other 5. (SA Only)

MIRN Standing Data

Project Prepared by Date

B2B Process Flows v3.4 15

PF(B2B): MIRN 4B: MIRN Discovery by Address

3. Single Match Single

1. Inititiate MIRN Message: Initial MIRN Standing Data

Project Prepared by Date

B2B Process Flows v3.4 16