NARGP Industry Transition Cutover and Controlled ... · NSW/ACT GAS RETAIL MARKET PROJECT – INDUSTRY TRANSITION, CUTOVER AND CONTROLLED PRODUCTION START PLAN Page | 2 DOCUMENT HISTORY

Page | 1

NSW/ACT RETAIL GAS PROJECT (NARGP) – INDUSTRY TRANSITION, CUTOVER AND CONTROLLED PRODUCTION START PLAN

PREPARED BY: Kerry Galloway / Danny McGowan

DOCUMENT REF:

VERSION: V4.0

DATE: 8th March 2016

FINAL

NSW/ACT GAS RETAIL MARKET PROJECT – INDUSTRY TRANSITION, CUTOVER AND CONTROLLED PRODUCTION START PLAN

Page | 2

DOCUMENT HISTORY

Version Date By Notes

1.0 03/07/15 Kerry Galloway/Tim Sheridan

Initial draft

2.0 5/08/15 Kerry Galloway/Danny McGowan

First round feedback


TCWG accepted Transition Plan version.


(i) Inclusion of Wagga Wagga and Tamworth Transition Plan (Attachment C);

(ii) minor changes to Attachment B Part B section 1 and 3;

(iii) minor changes to Attachment E;

(iv) Inclusion of Attachment D.

5.0


Page | 3

Contents

1.1 Intended Audience ............................................................................................................. 7

1 Introduction ...................................................................................................... 9

1.1 Scope ......................................................................................................................... 9

1.2 Background ................................................................................................................ 9

1.3 Purpose of this Document. ......................................................................................... 9

1.4 Updates to this Document. ....................................................................................... 10

2 Governance and Communication ....................................................................11

2.1 Governance.............................................................................................................. 11

2.2 Reporting and communication .................................................................................. 11

3 Approach to develop the Industry Transition, Cutover and Controlled Production Start (CPS) plans ............................................................................................12

3.1 Principles ................................................................................................................. 12

3.2 Key assumption ........................................................................................................ 12

3.3 Timeframe to develop the Industry Transition Plan ................................................... 12

3.4 Approach to develop the Industry Transition Plan .................................................... 13

3.5 Timeframe to develop the Industry Cutover Plan ...................................................... 13

3.6 Approach to develop the Industry Cutover Plan ........................................................ 13

3.7 Timeframe to develop the Controlled Production Start (CPS) Plan ........................... 14

3.8 Approach to develop the Industry Controlled Production Start (CPS) Plan ............... 14

4 Application of the Industry Transition, Cutover and Controlled Production Start (CPS) Plans ....................................................................................................15

5 Key activities and timeline ...............................................................................16

5.1 Readiness planning .................................................................................................. 16

5.2 Transition, cutover and CPS period .......................................................................... 17

5.2.1 Jemena Outage window ............................................................................................................ 17 5.2.2 AEMO Outage window .............................................................................................................. 18 5.2.3 AGN/APA Outage window ........................................................................................................ 18

Attachment A - Guiding principles to complete the transition and cutover plan. ..........19

Attachment B – Industry Plans for transitioning off existing NSWACT function matrix – Jemena Networks ...........................................................................................20

Part 1 - Business to Business (B2B) interactions between User and Network Operators or vice versa. .......................................................................................................20

Section 1 –Critical Gas incidents ............................................................................................ 21

Sub Section A - Critical gas incidents not currently logged in GASS Application by the Users 21

Sub Section B - Critical gas incidents currently logged in GASS Application by the Users ..... 23


Page | 4

Section 2 – Other GASS Application functions ....................................................................... 25

Sub Section A - Retail Services – Request for Service (mnemonic Transaction Code AGILSERV). ................................................................................................................................. 25

Sub Section B – New Connection (mnemonic Transaction Code CONADD, RFSENQ, CONREL, RFSOFFER, CONCAN) ........................................................................................... 31

Sub Section C – Delivery Point Identify (DPI) Enquiry and claim Unclaimed Supply Points (mnemonic Transaction Codes DPIINFO, DPIENQ, DPIFIND, UNCENQ) ............... 37

Sub Section F - Network Tariff Charge Calculation (mnemonic Transaction Code NTCHCALC)42

Sub Section G - Network-Related Enquiries (mnemonic Transaction Code NCOMPADD) ..... 43

Section 3 – Meter Reading functions. ..................................................................................... 58

Section 4 – Network Billing functions ..................................................................................... 61

Section 5 – Contract admin billing system (CABS) ................................................................. 63

Part 2 - Business to Market Operator (B2M) interactions between User and Market Operator, Network Operators and Market Operator or vice versa. ..................65

Section 1 – Delivery Point Registry Transactions (DPRT) ..................................................... 65

Sub Section A - Delivery Point – New and Deactivation ......................................................... 65

Sub Section B – Change of User and Meter Read Request ................................................... 69

Sub Section C – Standing Data .............................................................................................. 73

Sub Section D – Deliver Point Register Information ............................................................... 74

Sub Section E – Correction Transaction ................................................................................ 76

Section 2 – Estimation Reconciliation and Forecasting Transactions (ERFT) ....................... 79

Sub Section A – Gas wholesale quantities and meter readings.............................................. 79

Sub Section B – Wholesale Estimation Results ..................................................................... 83

Sub Section C – Reports from AEMO to Users ...................................................................... 87

Section 3 – Imbalance And Incentives Transactions (IAIT) ................................................... 88

Section 4 - RoLR.................................................................................................................... 93

Part 3 – Miscellaneous transitional function that do not fall with the framework of Parts 1 or 2. .....................................................................................................................94

Section 1 – Retention of Gass+ historical information – requirements, format, how far back, etc94

Section 2 – Planned Gas Network Interruptions ..................................................................... 95

Section 3 – New Participant Registration ............................................................................... 96

Attachment C – Industry Plans for transitioning off existing NSWACT function matrix – AGNL/APA Networks ......................................................................................98

Section 1 Wagga Wagga and Tamworth network sections ..................................................... 98

Section 2 Tamworth network section ...................................................................................... 99

Section 3 Wagga Wagga network section ............................................................................ 100

Attachment D – Industry Cutover Plan .......................................................................106

1. Document Purpose .......................................................................................106


Page | 5

2. Management, Decision Making (incl. escalation), Reporting, & Communications plan ...............................................................................................................106

2.1 Introduction ...................................................................................................106

2.2 Control/management framework and responsibilities ....................................106

2.3 Representatives ............................................................................................107

2.4 Cutover dependencies ..................................................................................107

2.5 Decision making (responsibilities, process incl. escalation process). ............107

2.6 Industry Schedule .........................................................................................107

2.7 Communications ...........................................................................................107

2.7.1 Communications Processes: .........................................................................108

2.8 Reporting ......................................................................................................108

3. Cut-over Activities .........................................................................................109

3.1 Certification ...................................................................................................109

3.2 Initial Connectivity Testing (ICT) ...................................................................109

3.2.1 Intent of ICT ..................................................................................................109

3.2.2 ICT process ...................................................................................................110

3.2.3 Pre-requisites for ICT ....................................................................................110

i. Initial Connectivity Testing activities .................................................................................. 110

3.3 Test of System Changes ...............................................................................111

3.3.1 Pre-requisites for Production Verification Testing .........................................111

3.3.2 Production Verification Test Execution ..........................................................111

4. Cutover Timetable (Industry schedule) and Responsibilities .........................113

5. Teleconferencing Details and Industry Contacts ...........................................115

6. Post Go-live...................................................................................................119

6.1 Controlled ramping-up period ........................................................................119

6.2 Post go-live monitoring ..................................................................................119

6.2.1 Initial post go-live Production Transaction Monitoring ...................................119

6.2.2 Initial post go-live Issues/Defects Resolution ................................................121


Page | 6

6.2.3 Timing ...........................................................................................................122

6.2.4 Criteria to assess whether to close out daily post “go live” monitoring ..........122

6.3 Closure of Post go-live monitoring ................................................................122

Attachment E – Plan for monitoring Transition activities progress in the lead up to cutover. ......................................................................................................................125

Attachment F – Industry Controlled Production Start (CPS) Plan ..............................128


Page | 7

1.1 Intended Audience

Role Description

NARGP Consultative Forum

(NARGP-CF)

It is important for the NARGP-CF and this category of readers to oversee the transition and cutover planning and activities

Transition and Cutover Working Group (TCWG)

It is important for this category of readers to drive the transition and cutover planning. Participants working within this team require an understanding of transition and cutover activities, and will be required to make decisions on the approach, processes and timeframes within the transition period.

Participant industry operational teams Participant operational teams undertaking transition and cutover activities. This audience needs to have an understanding of the management approach in order to effectively plan and execute activities for transition and cutover and subsequently report on issues and progress.

1.2 References

Item Document Name Link

1 NARGP Market Readiness Approach v7.1 TBC

2 NARGP Certification Plan v4.2 TBC

3 NARGP Industry Test Plan v2.1 TBC

4 AEMO decision notice published on 11 June 2015 or any subsequent decision notices published by AEMO

AEMO website

5 Retail Market Procedures (NSW/ACT) AEMO website

6 Gas Interface Protocol (GIP) (NSW/ACT)1 AEMO website

7 Retail Market Procedures (SA)2 AEMO website

1.3 Terms

Term Definition

Gas Day Term used in the Retail Mark Procedures (NSW/ACT) - A period of 24 consecutive hours beginning at 6:30 am

1.4 Acronyms

Acronym Description

AGNL Australian Gas Networks Limited

APA Australian Pipeline Assets

B2B Business to Business

B2M Business to Market

CATS Consumer Administration and Transfer Solution

CPS Controlled Production Start

FRC Full Retail Contestability

GRMBS Gas Retail Market Business Systems

ITCCPS Industry Transition Cutover Controlled Production Start

MIBB Market Information Bulletin Board

M2B Market to Business

1 This document includes a section that explains the applicability of Build Packs by network section 2 The Retail Market Procedures for South Australia are taken to apply to Network Operators in respect of the Wagga Wagga and Tamworth network sections


Page | 8

Acronym Description

NARGP-CF NSW/ACT Gas Retail Project Consultative Forum

NOW Network Operator

SCU Self-Contracting User

STTM Short Term Trading Market

TCWG Transition and Cutover Working Group

WWT Wagga Wagga Tamworth


Page | 9

1 Introduction

This document outlines the transition and cutover approach and plans for the implementation of the NSW/ACT Gas Retail Market Project (NARGP) which is targeted to ‘go-live’ on Monday 2 May 2016 on the assumption that regulatory relief for all participants allows production verification testing to occur in a period before market start.

1.1 Scope

This Industry Transition, Cutover and Controlled Production Start (CPS) Plan prescribes all necessary pre- and post-implementation activities that will allow AEMO, Network Operators (which includes all networks owned and operated by Jemena and AGNL/APA) and Users to transition from current market arrangements and obligations to the future arrangements and obligations defined in the notice of AEMO decision published on 11 June 2015 or any other subsequent AEMO decision notices that are published after that date.

These notices contain the amendments to the NSW/ACT Retail Market Procedures (RMP) and Gas Interface Protocol (GIP) that take effect on 2 May 2016. All the regulatory obligation that are set out in the RMP and GIP are considered “in scope3”.

1.2 Background

In February 2014, Jemena (on behalf of Jemena Gas Networks (NSW) Ltd and ActewAGL Distribution) announced the replacement of their current retail gas systems and supporting IT infrastructure by November 2015.

The purpose of the NARGP is to harmonise (where possible) the business-to-business (B2B) and business-to-market (B2M) transactions with the NSW/ACT retail gas market, consistent with arrangements currently used in VIC, QLD and SA.

On 27 February 2015, AEMO published its decision approving the proposed changes to NSW/ACT Retail Market Procedures (RMP) and the Gas Interface Protocol (GIP) as per IN006/14. On 11 June 2015, AEMO published its decision approving changes to the NSW/ACT RMP and GIP for the Wagga Wagga and Tamworth networks as per IN004/15. These RMP and GIP changes were developed by AEMO in consultation with industry participants over multiple workshops that had commenced in March 2014.

1.3 Purpose of this Document.

The purpose of this document is to define the industry agreed scope, approach, process, responsibilities and schedule with respect to the following NARGP transition and cutover activities that has implication for AEMO, NWO and Users4. The document will outline:

Key activities and timeline

Governance, decision making (including escalation), reporting, and communications

Cutover steps, (e.g. connectivity test, data migration), data reconciliation

Transition approach and timeline:

o Ramp up, ramp down and freeze periods

o Management of inflight transactions, including meter reads, transfers and service orders

Cutover process and timelines:

3 For the avoidance of doubt “bi-lateral” arrangements for the Jemena Portal between Network Operator and Participants are considered out of scope. 4 Users includes Retailers and Self-Contracting Users


Page | 10

o Risk management and contingency planning

o Technical verification

o Production verification testing

o Reporting and monitoring

o Issues escalation and decision-making processes

Initial post ‘go-live’ monitoring

Transition to business-as-usual (BAU):

o Heightened support

o Procedure changes

Other elements of the transition and cutover period which are not covered by this document are:

Participants’ business readiness. This is covered within User, Network Operator and AEMO internal plans and only has visibility via the requirements of the NARGP Market Readiness Report.

1.4 Updates to this Document.

It should be noted that this document will evolve over time. At various stages, AEMO will publish updated versions and place these versions under change control. The change control process for this document will operate in a similar manner to the way in which NARGP has managed changes to the RMP and the GIP. It will involve maintaining a change register of proposed changes and the TCWG will periodically review that register and either approve or reject the changes by consensus. Any proposed changes that are contentious will be referred to the NARGP-CF for ratification.

The timings as to when AEMO will publish the updated versions are prescribed in sections 3.2 and 3.5 of this document.


Page | 11

2 Governance and Communication

2.1 Governance

In July 2015, the Transition Cutover Working Group (TCWG) was established. The purpose of the TCWG is to provide a platform whereby AEMO and all registered Participants can actively participate in the development of the Industry Transition, Cutover and Controlled Production Start (CPS) plan.

Transition and cutover steps will be executed by individual Participants working in accordance with the Industry Transition, Cutover and Controlled Production Start (CPS) Plan. These Participants will be individually pro-active in participating at agreed levels as follows:

providing initial input to the industry plans

reporting completion of activities / milestones in accordance with the industry plans

identifying and escalating issues

attending meetings as required to resolve issues that may arise

Issues will be initiated and managed on a participant by participant basis unless escalated to the TCWG to manage the issue on an industry basis. The TCWG will either make industrywide decisions relating to transition and cutover, or agree to escalate the issue/decision to the NARGP-CF.

2.2 Reporting and communication

The objective is to facilitate an industry wide view of participant status during the transition and cutover process.

At the first level, communications will occur directly between participants in specific activities or transactions. These communications will be instigated by project staff within each business on as as-required basis to ensure readiness for the particular interaction.

Second level communications will be initiated by participants raising industry issues for decision to the TCWG

Third level is via the organised and scheduled TCWG meetings


Page | 12

3 Approach to develop the Industry Transition, Cutover and Controlled Production Start (CPS) plans

3.1 Principles

In September 2015, the TCWG agreed on the following key principles in assessing the appropriateness of any approach to transitioning from the existing to the new market arrangements. These are in priority order:

1. AEMO and all Participants must ensure that there is an orderly market start by defining an agreed ramp-up process that avoids an excessive volume of transactions in the period immediately after go-live.

2. AEMO and all Participants must fulfil all regulatory and compliance obligations, noting that exemptions may be required for specific regulatory obligations pertaining to AEMO Procedures. Participants must also fulfil any all other compliance obligations, contractual or otherwise noting that exemptions may be required;

3. Any transitional arrangements must be practical and cost efficient;

4. All reasonable endeavours must be used to minimise disruption to customers, Participants and AEMO;

5. All transactions/messages must begin and end under same rules/systems to the extent possible;

6. Wherever possible and it is practicable to do so minimise in flight transactions as at transition date;

7. All transactions handled during and after the transition period that are business to market operator in nature must reconcilable between AEMO and participants;

8. Minimise operation of old and new systems in parallel;

9. The industry cutover approach must be based on a ‘fix-on-fail/roll-forward’ approach in which AEMO and all Participants will commit to cutting over to new systems and processes and will avoid rollback by addressing any problems as and when they arise; and

10. Cut-over can commence once AEMO and all Participants have met all required readiness criteria. If retailers have system readiness issues, they must implement contingency (e.g. manual) arrangements in their organisations and notify AEMO/NWO so that they can meet their obligations after go-live without impacting other participants.

These principles were the foundation to develop the “Guiding principles to develop the transition plan” document which was agreed in early October 2015.

Attachment A contains the agreed “Guiding principles to develop the transition plan” document

3.2 Key assumption

1. Industry will focus additional efforts to completing/reconciling outstanding B2B and B2M transactions prior to the shutdown period with the goal of minimising in-flight transactions at Cutover

2. Participants will use reasonable endeavours to define detailed transition interim and reconciliation processes and reports by end January 2016

3.3 Timeframe to develop the Industry Transition Plan

For the Jemena networks the timeframes to develop the Industry Transition Plan were set out in the “Guiding principles to develop the transition plan” document (see Attachment “A”).


Page | 13

This documented included a table that set out the October/November 2015 meeting schedule along a set of targeted outcomes. The last of those meeting noted that by mid November 2015 100% of B2B and B2M transaction transition plans would be well defined. To ensure that the 2 May 2016 ‘go-live’ date isn’t jeopardised, the TCWG agreed that the Industry Transition Plan for the Jemena networks must be signed-off and placed under change control by mid December 2015.

In terms of the timeframes to develop the Industry Transition Plan for the AGNL/APA networks, in consultation with Participants who operate in the WWT area it was agreed to hold at least three meetings, the first to be held in mid-January 2016 and the last mid-February 2016. To ensure that the 2 May 2016 ‘go-live’ date isn’t jeopardised, the TCWG agreed that the Industry Transition Plan for the AGNL/APA networks must be sign-off and placed under change control by late February 2016.

3.4 Approach to develop the Industry Transition Plan

The development of the Industry Transition Plan will take into account the outage timelines set out in section 5.2(Transition and cutover period) of this document.

The documents to be used as a baseline to develop the Industry Transition Plan are those that best describe the B2B and B2M interaction. For the Jemena networks, the TCWG agreed that the Interface Control Document (ICD) and Jemena’s Retail GASS training guide would be used as the baseline to develop Industry Transition Plan.

For the AGNL/APA networks, the ICD would again be used as the baseline to develop the Industry Transition Plan. Whether any further documents are required will be a topic of discussion in mid-January 2016.

Monitoring progress on Transition Plan progress is set out in Attachment E.

3.5 Timeframe to develop the Industry Cutover Plan

In order to ensure that the 2 May 2016 ‘go-live’ date isn’t jeopardised the TCWG agreed that the Industry Cutover Plan must be:

Prepared by end-January 2016 with cutover approach and draft timing.

Finalised and signed-off and placed under change control by mid-March 2016.

Unlike the development of separate transition for each network operator, the development of the Industry Cutover Plan will be a joint effort involving both Jemena and AGNL/APA networks.

The TCWG has agreed to hold at least three meeting, with the first commencing in mid-December 2015 and the last in mid-March 2016.

3.6 Approach to develop the Industry Cutover Plan

At a TCWG workshop held on 13 November 2015, AEMO circulated a document titled “Release And Cutover Working Group - Implementation Plan”. This document related to the implementation of version R29 of the schema (for VIC, QLD and SA markets) and was prepared by industry back in 2012. It described the major cutover events and timelines as to when such events need to be completed. AEMO proposed that the TCWG should use this document as a template to develop the NARGP Industry Cutover Plan. The TCWG agreed with this approach.

Subject to APA/AGNL endorsing the above approach AEMO will use the Release And Cutover Working Group - Implementation Plan” document as the baseline to develop the NARGP Industry Cutover Plan.

The development of the Industry Cutover Plan will take into account the outage timelines set out in the section 5.2 (Transition and cutover period) of this document.

When developed and agreed by the TCWG, the Industry Cutover Plan will form part of Attachment D.


Page | 14

3.7 Timeframe to develop the Controlled Production Start (CPS) Plan

In order to ensure that the 2 May 2016 ‘go-live’ date isn’t jeopardised the TCWG agreed that the Industry Controlled Production Start (CPS) Plan must be signed-off and placed under change control by the end of February 2016.

Unlike the development of separate transition for each network operator, the development of the CPS Plan will be a joint effort involving both Jemena and AGNL/APA networks.

3.8 Approach to develop the Industry Controlled Production Start (CPS) Plan

At the time of preparing this version of this document the approach to develop the Industry CPS plan has been defined. This will be a topic of future TCWG discussions.

When developed and agreed by the TCWG, the Industry Controlled Production Start Plan will form part of Attachment F.


Page | 15

4 Application of the Industry Transition, Cutover and Controlled Production Start (CPS) Plans

AEMO, Network Operators and Users must comply with, and are bound by, the GIP in respect to the provision of information, giving of notice, delivery of notices or documents and making of requests, and the receipt of information, notices, documents or requests, as contemplated by the RMPs. The development of the Industry Transition, Cutover and Controlled Production Start (CPS) Plan alone does not alter those obligations.

Once the Industry Transition Plans are agreed, AEMO, on behalf of Participants, will use the information contained in the plans as drafting instructions to seek relief from the regulatory artefacts that AEMO administers. AEMO legal will be engaged in this process which will kick-off in mid-December 2015. In mid-January 2016 AEMO will advise Participants on what approach AEMO will take in respect to maintaining compliance with the artefacts that AEMO administers.

If AEMO deems that the approach to be taken will require amendments to the existing RMP by including a new section within the existing RMP to document the transitional arrangement, any such amendments will form part of a new consultation process. The timing of this consultation process needs to coincide with the go/no go decision in mid-March 2016.

In terms of other regulatory artefacts not administered by AEMO, or any “bi-lateral” contractual arrangements between Network Operators and Users, it will be the responsibility of those parties to facilitate a program of work to seek compliance relief from those arrangements where applicable.


Page | 16

5 Key activities and timeline

This section details the key planning activities in the lead up to ‘go-live’ as well as the specific activities over the transition, cutover and CPS period.

5.1 Readiness planning

Date Activity Who Complete

17 July 2015 NARGP workshop - walk-through the first draft of the NARGP ITCCPS Plan.

All

24 July 2015 Window closes for participants

to provide feedback to first draft of the NARGP ITCCPS plan. All feedback to [email protected]

Participants

5 August 2015 Circulate second draft of the NARGP ITCCPS plan.

AEMO

12 August 2015

For Jemena networks the first of several TCWG meeting kick-off to develop the Transition Plan

All

6 October 2015

Guiding principles to complete the transition and cutover plan signed off

(Attachment A)

All

19 November 2015 Issue third draft of the NARGP ITCCPS plan.

AEMO

Late November 2015 The call for nomination to be added to the TCWG to help develop the Cutover Plan issued

AEMO

4 December 2015 Window closes for participants to provide feedback to third draft of the NARGP ITCCPS plan. All feedback to [email protected]

All

Mid-December 2015 Industry Transition Plan for Jemena networks signed off (Attachment B).

Updated version of the NARGP Industry Transaction and Cut over Plan published.

All

AEMO

Mid-January 2016

For AGNL/APA networks the first of several TCWG meetings kick-off to develop the Transition Plan

All

End-January 2016 Industry Cutover Plan (Attachment D) approach and draft timing signed off and agreed

Updated version of the NARGP ITCCPS plan published

All

AEMO

mailto:[email protected]



Page | 17

Date Activity Who Complete

Mid-February 2016 Industry Transition Plan for AGNL/APA networks signed off (Attachment C)

Updated version of the NARGP ITCCPS plan published.

All

AEMO

End-February Controlled Production Start (CPS) Plan (Attachment F) signed off and agreed

Updated version of the NARGP Industry Transaction and Cutover Plan published

All

AEMO

Mid-March 2016 Industry Cutover Plan signed off (Attachment D)

Updated version of the NARGP ITCCPS plan published

All

AEMO

15 March 2016 Industry ‘go-live’ decision All

2 May 2016 Controlled Production Start (CPS) Plan (Attachment F) is updated with actual stockpile numbers

Updated version of the NARGP Industry Transaction and Cutover Plan published

All

5.2 Transition, cutover and CPS period

The proposed ‘‘go-live’’ date for the NARGP is 2 May 2016. In order to develop the Transition and Cutover plans, the Market Operator and the Network Operator must nominate their respective outage windows.

5.2.1 Jemena Outage window

For a 06:30 ‘go-live’ date of Monday 2 May 2016, Jemena will have a staged transition. These stages include the following:

Stage 1 from 17:00 on Friday 22 April 2016:

(i) fully remove GASS online access from Users (retain access to the CABS facility to manage Forecasts and Nominations in the Canberra network); and

(ii) stop processing inbound B2B transactions from Users.


Page | 18

Stage 2 from 17:00 on Wednesday 27 April 2016:

(i) stop sending outbound B2B response transactions to Users; and

(ii) stop processing inbound/outbound B2M transactions (excluding wholesale market transactions and CABS facility to manage Forecasts and Nominations).

Stage 3 from 15:00 on Sunday 1 May 2016:

(i) access to CABS facility to manage Forecasts and Nominations unavailable; and

(ii) stop processing inbound/outbound wholesale market B2M transactions.

5.2.2 AEMO Outage window

For a 06:30 ‘go-live’ date of Monday 2 May 2016, AEMO will from 18:00 on Friday 29 April 2016

(iii) fully remove the interface features for its retail systems; and

(iv) partially maintain interface features for its wholesale systems to enable AEMO and Participants to fulfil its regulatory obligations except the reports referred to attachment B (Industry Plans for transitioning off existing NSWACT function matrix) Part 2 Sub Ref # 2C.1 which would normally be sent to Users on the Sunday 1 May 2016 between the hours 20:00 and 21:00 inclusive. Instead these reports will be issued sometime between 06:30 and 12:00 on Monday 2 May 2016 under the arrangement prescribed in PBP5.

5.2.3 AGN/APA Outage window

For the Tamworth network section, the same outage window described in section 5.2.1 applies.

For the Wagga Wagga network section, the following applies:

For a 06:30 ‘go-live’ date of Monday 2 May 2016, AGN will from:

(i) 17:00 on Friday 22 April 2016 stop processing inbound B2B transactions from Users and stop processing inbound B2M transfers from Users.

(ii) 17:00 on Wednesday 27 April 2016 stop sending outbound B2B response transactions to Users.

(iii) Continue sending outbound B2M transactions (ERFT) as per business as usual


Page | 19

Attachment A - Guiding principles to complete the transition and cutover plan.

Guiding principles

to develop the transition plan v 1.1.pdf


Page | 20

Attachment B – Industry Plans for transitioning off existing NSWACT function matrix – Jemena Networks

Part 1 - Business to Business (B2B) interactions between User and Network Operators or vice versa.

In the case of Service Order transactions, the following shows Job Enquiry Codes and whether they are categorises as either a “high”, “medium” or “low” priority for the purposes of transition planning:

High (A+B) Medium (carry on During Shutdown )

Low (on hold During Shutdown )

Not used

CSL EBD EBS EFB EMG EMT EOT ESE EST EXP FAP FAT FHS FMN FMT FSV

MST MTE MTN RML SNG RSD SPN MDM SBS AML DFC

MTJ UEF DSD OTH MCH MDO MRM MAP MRC RSR SDR USR UMS MHA MRT

MRR MRF MRG MBO


Page | 21

Section 1 –Critical Gas incidents

Sub Section A - Critical gas incidents not currently logged in GASS Application by the Users

Parent Process

Sub Ref #, Sub Process -

Brief description of

the current process

Cross ref notes to GIP transactions

Details of any existing regulatory or contract obligation that govern this process

Priority and estimated number of transactions

Initial transition plan expectations

Pre-Shutdown activities

During Shutdown activities

Post go-live activities (Rules and Procedures apply)

Other Notes, including any “In flight” arrangements

1 A. Gas incidents which have caused or have the potential to cause injuries and/or major equipment damage.

1A.1 Information from customers must be made available to the Network Operator immediately and with urgency and without further evaluation by the Retailer of the customer’s information. Call transfer to JGN’s emergency line – 131909 or Smell of Gas - gas leak is inside the house In certain circumstances Users may log this into GASS using the codes 101, 102 and 105.

Only Response Transaction – T315 Job Enquiry codes are: CSL Critical Supply Loss (eg Hospital Equipment); EBD Escape Bad; EFB Police and/or Fire Brigade, ESE Street Excavations, EXP Explosion, FAP Fire Appliance, FAT, Fatalities, FHS Fire House, FMN Fire Main, FMT Fire Meter, FSV Fire Service;

Access arrangements – bilateral agreements AER requirements NSW/ACT safety regulator Network code – NSW / ACT government (overlap with NERR & NERL)

High (This is a subset of the A&B priority classification. The total A&B for the equivalent period in 2015 is 1373)

AEMO – doesn’t directly interact with this process therefore not impacted. AEMO does however receive the energy data if the meter is read or a gas meter notification if the meter is turned off.

AEMO – AEMO – . AEMO – Note will also require MDN if appropriate

Users - Existing process call transfer to JGN’s emergency line – 131909 and/or enter into GASS

Users - Ensure that customer service staff is well trained on the revised emergency procedures noting that it is a change from current procedures. COB 22 April 2016 Commence raising all emergency service orders with the Jemena

Users- COB 22 April 2016- Retailers will phone through all emergency calls during the cutover period using the revised procedures.

Users- Transfer all calls to NWO emergency line – 131909. This becomes BAU 02 May forward - Process responses sent as a result of the DB initiated service orders if required


Page | 22

emergency response centre and cease use of GASS and other interfaces

Network Operator: - GASS will not be available post go-live

Network Operator - Notify all Users in advance to revert to call process for cutover and post go-live 20 Feb 2016 - Define, and agree with retailers, the process which will commence at COB on 22nd April 2016 for retailers to follow for directly raising all emergency calls with the Jemena emergency desk. Note: this process is the future BAU process. 20 April 2016 - Notify all retailers that they should commence raising all emergency service orders with the Jemena emergency desk and cease using from COB 22 April 2016

Network Operator - COB 22 April – 01 May 2016 - Jemena will process all high-priority service orders using manual processes during the outage but will not provide any routine responses to retailers on the progress of these service orders during the cutover period

Network Operator - 02 May forward - After go-live Jemena will raise DB initiated service orders in the SAP system for all of the service orders raised during the cutover period and issue responses to retailers When providing these responses, Jemena will give priority to the responses that include changed meter information (new meter information).

Priority given to any that have had a meter impact – users need to know on day 1 of new arrangements (2 May)


Page | 23

Sub Section B - Critical gas incidents currently logged in GASS Application by the Users

Parent Process

Sub Ref #, Sub Process - Brief

description of the current process









1 B. Smell of Gas Process

1B.1 If the gas leak is at the meter: Initiate a Service Order - Enter the work code 105 - ESCAPE-METER. This service order will be raised in GASS and completed within 7 calendar days. If the gas leak is in the front yard: Initiate a Service Order - Enter the work code 102 - ESCAPE - CONSUMER SERVICE .If the gas leak is 0n footpath / road: Initiate a Service Order - Enter the work code 101 - ESCAPE AT COMPANY MAIN/SERVICE.

Only Response Transaction – T315 Job Enquiry codes are: EMT Escape Meter – User, EBS - Escape Bad in Street. EMG - Emergency EOT - Escape Other EST – Escape in Street User do not enter this enquire code as this is a Priority A or B so the call is diverted to the Network Operator directly.

Access arrangements – bilateral agreements AER requirements NSW /ACT Safety Regulatory Network code – NSW/ACT government (overlap with NERR & NERL)

High (A&B) This is a subset of the A&B priority classification. The total A&B for the equivalent period in 2015 is 1373)

AEMO – doesn’t directly interact with this process therefore not impacted. AEMO does however receive the energy data if the meter is read or a gas meter notification if the meter is turned off. . .

AEMO – AEMO – AEMO – Note will also require MDN if appropriate

Users - Existing process enter into GASS will cease. Retailers will transition to call process

Users - 1 April 2016 Ensure that customer service staff is well trained on the revised emergency procedures noting that it is a change from current procedures. COB 22 April 2016 Commence raising all emergency service orders with the Jemena emergency response centre and cease use of GASS and other interfaces

User- 23 April 2016- Retailers will phone through all emergency calls during the cutover period using the revised procedures.

User- Transfer all calls to NWO emergency line – 131909. This becomes BAU 02 May forward - Process responses sent as a result of the DB initiated service orders if required


Page | 24

Network Operator - GASS will not be available post go-live

Network Operator - Notify all Users in advance to change to call process for cutover and post go-live 20 Feb 2016 - Define, and agree with retailers, the process which will commence at COB on 22nd April 2016 for retailers to follow for directly raising all emergency calls with the Jemena emergency desk. Note: this process is the future BAU process. 20 April 2016 - Notify all retailers that they should commence raising all emergency service orders with the Jemena emergency desk and cease using from COB 22 April 2016

Network Operator - 23 April – 01 May 2016 - Jemena will process all high-priority service orders using manual processes during the outage but will not provide any routine responses to retailers on the progress of these service orders during the cutover period

Network Operator - 02 May forward - After go-live Jemena will raise DB initiated service orders in the SAP system for all of the service orders raised during the cutover period and issue responses to retailers When providing these responses, Jemena will give priority to the responses that include changed meter information (new meter information).


Page | 25

Section 2 – Other GASS Application functions

Sub Section A - Retail Services – Request for Service (mnemonic Transaction Code AGILSERV).

Parent Process



the current process









2A.Supply Problem Process

2A.1.If the consumer has poor supply; Initiate a Service Order and enter the work code: 202 - POOR SUPPLY for service on the same day or the next working day. Note - If the consumer’ property (Commercial) has no supply same process used.

T314,T315 SBS - Bad Supply Priority C service order Job Enquiry codes are: MST – Meter Stolen MTE – Meter Turn on / Cut-off in error MTN – Meter Turn-on RML – Remove Locks/Plugs to Meter for Debit SNG – No Gas RSD – Reconnect Service in Street after payment SPN – Practically no gas MDM – Meter Damaged SBS – Bad Supply MTJ – Meter Tap Jammed MDO – Meter Defective Operation Ordinary.

Access arrangements – bilateral agreements AER requirements (NSW/ACT Safety Regulatory Network code – NSW/ACT government (overlap with NERR & NERL) In the case of Disconnections or Reconnections current RMP Section 10 (This links to Part 2, 1A.3)

Medium (>B). The total in this category for the equivalent period in 2015 is 696)

AEMO – doesn’t directly interact with this process therefore not impacted. AEMO does however receive the energy data if the meter is read.

AEMO –. AEMO –. AEMO – Note will also require MDN if appropriate

Users - Job raised in GASS

Users - By end January Retailers will work with Jemena to define detailed requirements for the interim process (for example, a mock-up of a form or systems extract) contact details, reconciliation process, tagging process, etc.) By end February 2016. Retailers will work with Jemena to agree on the definition and development of the interim process.

Users – COB 6pm 22 April – 1 May 2016 Retailers will use the interim process to send through medium priority service orders during the cutover period. 23 April – 1 May 2016 A daily reconciliation process will operate to provide retailers with the status of the service orders.

Users – 02 May – 05 May Retailers will re-raise those service orders that were created or converted to manual process during the cutover period using the interim process. Retailers will re-raise the service orders using B2B. These service orders will be ‘tagged’ (potentially using the special instructions field) to differentiate

Note Retailers and AEMO require information regarding changes to metering attributes (e.g. meter number, status,) For Retailers via B2B SO response, plus associated MDN as appropriate, For AEMO via B2M GasMeterNotification/ MIRNStatusUpdate.


Page | 26

MFX (unclaimed)

By end March 2016 Retailers and Jemena will test the interim process defined above. COB 6pm 22 April 2016 Retailers will adopt the manual/interim process for medium priority Service Orders.

them from new service orders. Retailers will re-raise the service orders based on the agree priorities. 02 May → All new Service orders to be raised via B2B

Network Operator: -

Network Operator - By end January Jemena will work with retailers to define detailed requirements for the interim process (for example, a mock-up of a form or systems extract) contact details, reconciliation process, tagging process, etc.) By end February 2016. Jemena will define and develop an interim process for processing medium priority service orders during the cutover period. This process will be agreed with

Network Operator - COB 6pm 22 April – 1 May 2016 Jemena will use the interim process to receive medium priority service orders during the cutover period. COB 6pm 22 April – 1 May 2016 Jemena will operate a daily reconciliation process to provide retailers with the status of the service orders. 22 April 2016 Jemena will capture any medium priority Service Orders

Network Operator – 02 – 09 May 2016 Jemena to reconcile Retailer-initiated Service Orders raised for items actions during the Cutover period 02 – 09 May 2016 Finalise reconciliation of offline work completions and provide individual reports to Retailers with details of the service orders that need to be re-raised. 02 – 09 May 2016

Manual form potentially using drop down boxes – and/or system extract. Note needs to include the data needed to enter these post go-live (service order response). Form/system extract should consider using service order request transaction format.


Page | 27

the retailers. The process will include an approach for re-entering of service orders after go-live that allows the re-raised service orders to be reconciled with those raised using the interim process (potentially using the special comments field). The interim process could be a manual form, an electronic form (using drop down boxes) and/or a systems extract. Note: the form should as far as possible include all necessary data for the re-entry of the service order after go-live (and could use the service order transaction format). By end March 2016 Jemena and retailers will test the interim process defined above. By End February 2016 Jemena will agree an approach with

not closed out prior to cutover - and incorporate into manual process. Jemena will continue to process these service orders.

Process re-raised service orders and provides response transactions to retailers and AEMO as required.


Page | 28

retailers for prioritising the service orders that are re-raised after go-live. 22 April 2016 Prior to go-live, Jemena will provide an updated list of unclaimed sites so that retailers can raise MFX Service Orders for unclaimed sites using the interim process during the cutover period (without needing to access GASS+). COB 6pm 22 April 2016 Jemena will adopt the manual/interim process for medium priority Service Orders.

2A. Temporary disconnection Permanent disconnection and meter removal And other metering functions of a low priority nature

2A.2. Retailer to nominate an accredited service provider other than the Network Operator, to perform the services for a temporary disconnection

T314,T315 SNG - No Gas Priority C Job Enquiry codes are: UEF – Upstream Equipment Fault DSD – Disconnect

Access arrangements – bilateral agreements AER requirements NSW?ACT Safety Regulatory Network code – NSW/ACT government

Low (> B) The total in this category for the equivalent period in 2015 is 1256)

AEMO – doesn’t directly interact with this process therefore not impacted. AEMO does however receive the energy data if the meter is read . or a gas meter notification if the meter is turned off. .

AEMO – AEMO. AEMO – Note will also require MDN if appropriate


Page | 29

and reconnection. The Retailer is obliged to notify the Network Operator of the following: 1. Intent to undertake the services with at least 24 hours notice of the service being performed. 2. Notification after 2 days of the work being carried out Select - Retailer Intentional Reconnection or Retailer Intentional Disconnect

Service in Street for Debt OTH - Other MCH – Meter Change MAP – Meter Alter Position MRC – Interval Meter Remove RSR – Relocate Service Only Request SDR – Service Disconnection Request USR – Upgrade Service Request UMS – Upgrade Meter Size Request DFC – Dissatisfied Customer MHA – Meter High Account MRT – Meter Retake and Test AML – Attach Lock/Plug to Meter for Debt Note – MRR (Meter Refix and Relight), MRF (Meter Refix) , MRG (Meter Refix and Relight), MBO (Meter Pre-Pay Broken) not used

(overlap with NERR & NERL) Current RMP RMP section 10 – meter turn off


Users - By end Feb 2016 – Jemena and Retailers will agree a process which will include an approach for re-entering of service orders after go-live which allows the re-raised service orders to be reconciled with those previously cancelled. Jemena and Retailers will agree an approach with retailers for prioritising the service orders that are re-raised after go-live. By end March 2016 Jemena and retailers will test the process for re-raising service orders defined above. Up to 22 April 2016 BAU

Users - 23 April – 1 May 2016 Retailers will not raise any low priority service orders during the cutover period unless exceptional circumstances

Users - 2 May → Retailers will re-raise the service orders that were cancelled prior to Cutover. These service order requests will be issued via the new B2B processes. The service orders will be ‘tagged’ to show that they had been previously raised and cancelled.

Network Operator: -

Network Operator - SDR only - stop sending the DE file to Users on 22 April (link to 2B.4)

Network Operator - 26 April 2016 As a first step in the cutover process, Jemena will

Network Operator – 2 May → Jemena will accept the re-raised service orders and

Cutover dress rehearsal – test process for re-entering in flight SOs and tagging


Page | 30

22 April 2016 For SDR and MRM service orders, Jemena will stop sending the DE file to retailers on 22 April. For SCR and MFX service orders, Jemena will stop sending the NC file to retailers on 22 April By End February Jemena and Retailers will define and agree a process which will include an approach for re-entering of service orders after go-live which allows the re-raised service orders to be reconciled with those previously cancelled. By end February Jemena and Retailers will agree an approach with retailers for prioritising the service orders that are re-raised after go-live. By End March 2016 Jemena and retailers will test the process defined above.

cancel all open service orders in GASS *New connections work will continue for field activities – working to required dates. A Manual process will be used for data capture, tracking and reconciliation 26 April – 1 May 2016 Jemena will provide each retailer with a file with details of all cancelled service orders.

reconcile them with the previously cancelled service orders so that they can be completed within SLAs.


Page | 31

Sub Section B – New Connection (mnemonic Transaction Code CONADD, RFSENQ, CONREL, RFSOFFER, CONCAN)

Parent Process

Sub Ref #, Sub Process

- Brief description

of the current process









2B.New Connection

2B.1.Mains Evaluation Required - Check is required prior to proceeding with new connection. This check determines if gas is available. Standard Connections (Quotable site conditions) - do not satisfy one or more of the Basic connection criteria New Connection - Peak Load >320 MJ / Hour - a mains evaluation will be conducted to determine if

Quote – some quotes will be migrated to SAP – open (with an offer and not yet accepted will be migrated, others will not. (accepted quotes have moved to SO)

Access arrangements – bilateral agreements AER requirements NSW/ACT Safety Regulatory Network code – NSW/ACT government (overlap with NERR & NERL) RMP Section 9

AEMO – AEMO currently doesn’t interact with this process therefore not impacted.

AEMO – AEMO –. AEMO –.

Users - Users - 30 November 2015 & 15 February 2016 Receive reports on open quotes. Perform clean-up activities for Retailer owned items in GASS for aged items. (Reports to be sent Nov 2015 and Feb 2016) 22 April 2016 Stop raising new requests for new quotes in GASS

Users - 23 April – 1 May 2016 Interim processes used during Cutover (as agreed and communicated) in exceptional circumstances. 23 April – 1 May 2016 Capture and hold requests for quote.

Users - 2 May 2016 → For any converted quotes or quotes manually raised during the cutover period, Retailer to submit Service Order Request with New Offer #. Interim process required for Jemena on converted data to process as quote number will not exist in Portal (validation process) 2 May 2016 → Re-raise those Requests for Quote via Gas Distribution Portal


Page | 32

the existing infrastructure can handle the additional load Lodging a Request for Service – Commercial and Industrial Consumers Note1: See also part 1 Section 2 - 2G.25 Note2: For AEMO see also Part2 Section 1 (DPRT)

that were cancelled using agreed ‘tagging’ process so that dates can be recaptured. 2 May 2016 → New requests to be raised via the Gas Distribution Portal Note: If a retailer does not require a quote for their specified service, they may request this service via B2B without visiting the Gas Distribution Services Portal to obtain a quote ‘Offer Number’. This would be the case for a ‘Basic’ connection, where no quote is required.

Network Operator -

Network Operator - 30 November 2015 Provide an extract report for all Open quote items. Analyse and provide options to Retailers on management of Aged/Open items.

Network Operator - 26 April Cancel all requests for quotations (RFS) where the quote has not been issued and provide reports to retailers. 23 April – 1 May 2016

Network Operator – 2 to 5 May 2016 Process backlog for any provided quotes during Cutover period 2 May 2016 Report to be provided to Retailers to reconcile GASS quote ID with the new SAP quote ID for all converted

Cutover dress rehearsal – test process for re-entering open quotes (and SO with RFS) Need to be able to accept new connections with quotes raised in GASS Can extract/report of open quotes be mapped/transformed to Portal inputs


Page | 33

15 February 2016 Provide updated extract report for all Open quote items. Analyse and provide options to Retailers on management of open items. By End February Interim process for Cutover period (to be used only for ‘urgent’ quotes to be defined and communicated to Retailers. By End February Agree a process with retailers for re-raising (via Gas Distribution Portal) those Requests for Quotes (RFS) that were open prior to cutover with no offer issued (subsequently cancelled) to maintain SLA’s By End February 2016 Create interim process (for use post Go-Live) for Retailers and Developers to accept

Interim processes used for urgent quotes during Cutover (as agreed and communicated) 26 April – 1 May 2016 Migrate all open quotes (issued and accepted) to new SAP system

Open/Accepted quotes. Preferably this report would provide data that can be easily mapped to the data input fields in the Portal. 2 May 2016 Process re-raised Requests for Quote (from Portal) and reconcile with those cancelled so that dates can be maintained.


Page | 34

converted quotes/offers

2B.2.Basic Connections - peak load less than 320 MJ/hour Meter removals Note1: See also Part 1 Section 2G.25. Note2: For AEMO see also Part2 Section 1 (DPRT)

T310, T311 and T87, T92 SCR Service Connection Request; MFX Meter Fix MRM Meter removal

Access arrangements – bilateral agreements AER requirements NSW/ACT Safety Regulator Network code – NSW government (overlap with NERR & NERL) RMP Section 9


AEMO – AEMO – AEMO –

AEMO is involved – receive DPI update – MFX notification- (links to B2M)

Users -

Users - BAU until COB 22 April – enter into GASS By End February Agree format for re-entering and tagging inflight SOs Also need manual process for emergency ones by end February

Users - Only critical, emergency raised over cutover via manual process Capture and store details from customers

Users - Re-raise SOs from Report in date order, tagged as pre-cutover so dates can be recovered Raise captured ones post go-live as per BAU

Network Operator: -

Network Operator - Cancel open SO on 22 April, prepare report of open SO send to Retailers and continue undertaking work via manual process By End February Agree

Network Operator - Continue field activities – working to required dates Manual process - manual data capture, tracking and reconciliation

Network Operator – Accept SO and match it to manual report so can complete within SLAs. In the case of were a New Connection (NC) is raised in GASS prior to shut down and it also is completed prior to

Cutover dress rehearsal – test process for re-entering in flight SOs and tagging It is desirable that the report of open SO be in previous and new SORD (T87) format.


Page | 35

format of report of open SOs. Agree format for re-entering and tagging inflight SOs Also need manual process for emergency ones by end February Stop sending the new connection (NC) file to Users on 22 April

shut down and the NC is sent via the existing NC file to Retailer, but the Retailer failed to provide the update to the GRMBS prior to the shut down resulting in a “orphaned NC” the NWO is to reconcile NC sent to RBs against DPRTNotifyNew DeliveryPoint transaction received from AEMO (see Part 2, 1A.2) and if NC sent to the Retailers doesn’t have a corresponding DPRTNotify NewDeliveryPoint transaction, then the NWO is to send AEMO a Meter Fix notification.

2B.3.Lodging a Request for Meter only Note See also Part 1 Section 2 - 2G.25 Note2: For AEMO see also Part2

T314, T315

MFX (unclaimed/additional)

Access arrangements – bilateral agreements AER requirements NSW/ACT safety regulatory )

Same as medium

AEMO – doesn’t directly interact with this process therefore not impacted. AEMO does however receive the energy data if the meter is read.

AEMO –data if the meter is read.

AEMO – AEMO – Note will also require MDN if appropriate


Page | 36

Section 1 (DPRT)

Network code – NSW government (overlap with NERR & NERL) RMP Section 9


Users - Review and accept manual process by end February Stop entering medium priority SO on COB 22 April and commence manual process thereafter Inflight medium: any medium priority SO not closed out prior to cutover – 22 April – manual update and close out

Users – Manual process - manual data capture, tracking and reconciliation

Users – Reconciliation Retailers re-raise with tag

Note Retailers and AEMO require information regarding changes to metering attributes (eg meter number, status,) via B2B SO response, plus associated MDN as appropriate.

Network Operator: -

Network Operator - Develop manual process by end February, including form/system extract, contact details, reconciliation process – in consultation with Users Inflight medium: any medium priority SO not closed out prior to shutdown – COB 22 April - (“stragglers”), and continue to process and incorporate into manual process

Network Operator - Manual process - manual data capture, tracking and reconciliation

Network Operator – Provide manual report to Users of list of Service Orders that Jemena performed manually during the outage.

Manual form potentially using drop down boxes – and/or system extract. Note needs to include the data needed to enter these post go-live (service order response). It is desirable to that the form/system extract should consider using service order request transaction format.


Page | 37

Sub Section C – Delivery Point Identify (DPI) Enquiry and claim Unclaimed Supply Points (mnemonic Transaction Codes DPIINFO, DPIENQ, DPIFIND, UNCENQ)

Parent Process

Sub Ref # Sub Process

- Brief description










2C DPI Discovery All the DPI codes above

2C.1 (i) Network operator to provide DPI full listing to AEMO, (ii) AEMO to provide DPI full listings to users and (iii) Use of DPI full listings

T280 MIRN discovery

RMP Section 17 Access arrangements – bilateral agreements Network code – NSW/ACT government (overlap with NERR & NERL)

AEMO – AEMO – Post off-cycle DPI full listing on 22 April into each retailers’ folder

AEMO – AEMO – Generate and publish MIRN complete listing (T299) 2 May

Users – BAU until 22 April, no access to GASS+ after 22 April

Users – BAU until 22 April

Users – Default to DPI listing

Users -

Network Operator: -

Network Operator – Generate an off-cycle DPI full-listing on 21 April

Network Operator –

Network Operator – Generate and publish MIRN complete listing (T299) 2 May Refer to Part 2 – move-in transfers (see 1B.5), will be large volumes of MIRN discovery

2C Unclaimed Supply Points

2C.2 Ability for User to claim unclaimed site

AEMO – . AEMO – AEMO – AEMO –


Page | 38

UNCENQ Users -

Users - BAU until 15 April,

Users - Use unclaimed DPI list

Users -

Network Operator: -

Network Operator - Cleanse of unclaimed sites to match GASS with field Generate unclaimed DPI list by 22 April and send to Users

Network Operator -

Network Operator -

Sub Section D – Retail Service – Meter Reading Request (mnemonic Transaction Code READSERV)

Parent Process


- Brief description










2D. Metering Services

2D.1 Special meter read - consumer transfer,

T3,T6 SRF

Access arrangements – bilateral agreements

Medium AEMO – AEMO currently doesn’t interact with this process therefore not impacted.



Page | 39

52G – SPECIAL METER READ Special meter read - consumer final bill 52G – SPECIAL METER READ

Network code – NSW government (overlap with NERR & NERL) RMP Section 5.1

Users - Users - By end February develop and agree standard format in consultation with NWO See PBP5 extract of current file format

Extract form PBP5 -

Special Read Request.docx

BAU until COB 22 April

Users – Commencing COB 22 April generate system extract of new special reads captured in systems and provide to Jemena. This can be generated every few hours or daily – (Includes RB ref #) Emailed to NWO

Users - Receiving actual reads in MDN closes off the special read request in system. Receiving estimated read will initiate a work item requiring CSR to follow up as per BAU Re-raise special reads that have not been attempted? Do we need this if Jemena are maintaining their SLAs?

Refer to medium SO – except not re-raising if can do system extract

Network Operator: -

Network Operator - Continue to receive and schedule works in as per BAU

Network Operator - Continue field work maintaining SLA Receiving extract from Retailers and schedule work accordingly Provide Retailers daily report of completed and not completed special reads In Flights:

Get extract from Gass of open SRFs in the same standard format agreed with the Retailers. Reads completed

Network Operator – . Provide actual reads in MDN for completed special reads and estimated for not completed special reads due to no access. The MDN will have the RB reference number matching what has been provided manually to Jemena and what has been raised in GASS pre Jemena outage. Provide Retailers a report of special reads requiring to be re-raised (jobs not attempted). In Flights:

Process extract in

Refer to medium SO Reads completed after COB 22 April – new charging applies


Page | 40

prior to COB 22 April – current charging applies

new system.

MDNs generated as BAU.

2D.2 Special meter read - intermediate read 52G – SPECIAL METER READ

T3,T6 SRA, SRT, SRR

Access arrangements – bilateral agreements Network code – NSW government (overlap with NERR & NERL)

Low AEMO – AEMO currently doesn’t interact with this process therefore not impacted.

AEMO –. AEMO – AEMO –

Users - Users - BAU until COB 22 April – enter into GASS Managing customer expectations and do not raise with dates during Jemena outage By End February Agree format for re-entering and tagging inflight special reads

Users - Only urgent special reads raised over cutover via manual process Capture and store details from customers

Users - Re-raise special reads that are in-flight from Report in date order, tagged as pre-cutover so dates can be recovered Raise captured ones post go-live as per BAU

Network Operator: -

Network Operator - Cancel open special reads on 27 April, prepare report of open special reads send to Retailers and continue undertaking work via manual process for exceptions By End February Agree format for re-entering and tagging inflight special reads

Network Operator - Only continue field activities – for exceptions Manual process - manual data capture, tracking and reconciliation

Network Operator – Re-raise special reads that were completed over the shutdown period as DB-initiated Accept special reads and match it to manual report so can complete within SLAs

Cutover dress rehearsal – test process for re-entering in flight SOs and tagging


Page | 41

NWO Also need manual process for urgent ones by end February Develop priority list for when these get re-raised NWO to focus additional efforts to completing/reconciling outstanding SRR/SRT/SRA prior to shutdown minimising in-flights


Page | 42

Sub Section E - Maintain Site Contact Details (mnemonic Transaction Code RGENMOD)

Parent Process


- Brief description










2E - Maintain Site Contact Details

2E.1 Triggered by customer –

T70 - CDN Access arrangements – bilateral agreements Network code – NSW/ACT government (overlap with NERR & NERL) AER


AEMO – AEMO – AEMO – AEMO currently doesn’t interact with this process therefore not impacted.

Users - Users – BAU until COB 22 April

Users – Manually record (store and hold)

Users – Use new B2B process to send items that were manually recorded during the Cutover period

Network Operator: - Network Operator -

Network Operator -

Network Operator -

Sub Section F - Network Tariff Charge Calculation (mnemonic Transaction Code NTCHCALC)

Parent Process


- Brief description











Page | 43

2F - Network Tariff Charge Calculation

2F.1 No equivalent process in new RMP and GIP

TBC AEMO – AEMO currently doesn’t interact with this process therefore not impacted.

AEMO – AEMO – AEMO –.

Users - Users – BAU to COB 22 April

Users – Stop

Users -

Network Operator: - Network Operator -

Network Operator -

Network Operator -

Sub Section G - Network-Related Enquiries (mnemonic Transaction Code NCOMPADD)

Parent Process


- Brief description of

the current process

Cross ref notes to GIP

transactions








2G. Add a Network Enquiry

2G.1 ACCESS -Access Enq/ Difficulties

T66,T67 Accepted existing B2B Transaction – AmendMeterRoute/AmendSiteAccess

Access arrangements – bilateral agreements Network code – NSW/ACT government (overlap with NERR & NERL) AER

Low – Number of transaction raised in the period 1/7/14-30/6/15 -344



Users - Users - BAU till COB 22nd April

Users Capture and stockpile Raise Stockpiled Orders

Users Raise captured ones post go-live as per BAU-


Page | 44

Network Operator: - ?

Network Operator – BAU till 22nd April

Network Operator – Record details and hold over till 2nd May

Network Operator – BAU

2G.2.ADDRESS -Address Details

T68,T69 Existing B2B Transaction – AmendSiteAddress. Hard copy of council notification also requested by Jemena and received via fax/ email usually. Same process used in other jurisdictions.

Access arrangements – bilateral agreement Network code – NSW/ACT government (overlap with NERR & NERL) AER

Low – Number of transaction raised in the period 1/7/14-30/6/15 1060






Network Operator: -




2G.3 BILLING -Concerns regarding network billing charges issues by Jemena

T351,T352 Network DUoS Billing Details (Dispute Notification)


High – Number of transaction raised in the period 1/7/14-30/6/15 182







Page | 45

Network Operator: -

Network Operator – BAU till COB 22nd April



2G.4 CFACTOR Common Factor Enq – concerns regarding the common factor calculated for centralised hot water systems in a block of units

No GIP transaction.


Number of transaction raised in the period 1/7/14-30/6/15 - 43




Users Email Details – Ref ROCL (The new BAU Process)

Users

Network Operator: -

Network Operator – BAU till COB 22nd April Capture items that are in flight so that they are not lost.

Network Operator – Process e-mail (The new BAU Process)


2G.5 COMPLIMENT - Compliment

No new transaction to be created as these can be provided via email.

Access arrangements – bilateral agreements Network code – NSW/ACT government (overlap with NERR & NERL)

Low – Number of transaction raised in the period 1/7/14-30/6/15 - 5





Users


Page | 46

AER





2G.6 CONBEHAV Contractor’s behaviour – complaint about a contractor’s behaviour.

T314,T315 DFC SO to be used ServiceOrderRequest








Network Operator: -




2G.7. CONSDATA Consumption data History

T45 Retailer can provide this information or under NECF customer can be directed to distributor to provide this as current retailer would not have historical da ta when the site was with previous retailer. In other




AEMO –. AEMO – AEMO –.



Users -

Network Operator: -





Page | 47

jurisdictions usually major commercial customers only request history data. Jemena to provide volumes of these requests as low volumes may not warrant a new transaction to be developed. EK: 18/yr

Capture items that are in flight so that they are not lost.

2G.8.CONTINFO - Plumbers & Cust Contact Details







Users -

Network Operator: -




2G.9 CSDATA - Change of Standing Data

T66,T67 Current issues with standing data in NSW-ACT: connection dates, initiation dates, daily/ monthly read site. Not an issue in other jurisdictions.





Users - Users - BAU till 22nd April

Users Capture and stockpile



Page | 48

Need to check what unique elements of standing data are covered. List of standing data required from Jemena. Use Amend Meter Route SO for such queries. AmendSiteAddress 40/yr. Currently used to request change in billing cycle (Q to M, M to Q).

AER

Raise Stockpiled Orders

Network Operator: -




2G10 DAMAGE Inlet Service damage – has been identified/ suspected that customer inlet service has been damaged.

T314,T315

Access arrangements – bilateral agreements Network code – NSW government (overlap with NERR & NERL) AER

Medium – Number of transaction raised in the period 1/7/14-30/6/15 - 58



Users - See Service Order transition plan (low)

Network Operator: -

See Service Order transition plan (low)

2G.11 DATECONN- Date of Connection

. There were 1921 DATECONN diaries raised by retailer from 1 January – 31 December 2013. This figure does not contain data on responses






Users Phone Details – Ref ROCL (The new BAU Process)

Users


Page | 49

provided by network operator, only pertains to requests raised by retailer. Jemena requests new job code for this diary code. Proposal is to utilise conceptual Portal to manage interaction (note Portal go-live date is 2 May 2016)

AER



Network Operator – Process phone (The new BAU Process)


2G.12 DPIENQ DPI Enq Process

T280,T281 Jemena highighted an issue faced with NSW-ACT Lost Gas Customer process. B2BWG agreed to use the DPI Discovery process currently in place. To be included in MIRN Discovery.





Users - Users – See MIRN Discovery transition plan

Users - Users -

Network Operator: -

Network Operator – See MIRN Discovery transition plan

Network Operator -

Network Operator -

2G.13 GOVTTST Government Meter Test – a meter test is required following extensive investigations performed by the retailer.

T314,T315 Maps to MRT – meter retake and test. Note: Jemena does not test meters on site. Jemena sends meter off to lab. Network must adhere to NSW





Users - Users – Ref to Service Order transition plan (low)?

Users - Users -


Page | 50

Department of Fair Trading regulatory requirements for testing. ServiceOrderRequest

AER

Network Operator: -

Network Operator – Ref to Service Order transition plan (low) Field work to continue.

Network Operator -

Network Operator -

2G.15 MAINEXTN - Mains Extension Enq – all man extension enquiries including when customer wants to know where the main extension is coming from.

Usually retailer diaries raised under RFSOFFER which had 870 queries raised in 2013. Proposal is to utilise conceptual Portal to manage interaction


Low – Number of transaction raised in the period 1/7/14-30/6/15- 1




Users Phone Details – Ref ROCL (The new BAU Process)

Users

Network Operator: -


Network Operator – Process phone (The new BAU Process)


2G.16 – MDLALIGN. MDL Reported out of Alignment

T242, T243 Existing B2B Transaction (subset) – MeterDataVerify to be used, as retailers are not aware if a Meter Data Logger is installed at site.




AEMO –. AEMO – AEMO –.

Users - Users – Ref to Service Order transition plan (low)

Users

Users

Network Operator: -

Network Operator – Ref to Service Order transition plan (low)




Page | 51

Field work to continue.

2G.17 - METER - Meter detail problems – enquiries related to the meter specific to the device

850/yr. Currently used to report issue with the meter. Suggest the following is used: T314/T315 ServiceOrderRequest with JEC = MDM/MDO





Users - Users – See Service Order transition plan (Medium)

Users - Users -

Network Operator: -

Users – See Service Order transition plan (Medium)

Network Operator -

Network Operator -

2G.18. METERNR Meter Not Registering

T243, T246 Existing B2B Transaction (subset) – MeterDataVerify to be used.





Users - Users – See Service Order transition plan (Medium)

Users - Users -


Page | 52

AER

Network Operator: -

Users – See Service Order transition plan (Medium)

Network Operator -

Network Operator -

2G.19. METERLOC. Meter Location Issues

T66,T67 Existing B2B Transaction – AmendMeterRoute to be used 60/yr. Currently used for request to change the meter location. In NSW, customer is to book a standby and in ACT, call through to the make appointment for a site visit – phone number of AAR website.


Low – Number of transaction raised in the period 1/7/14-30/6/15 – 59




Users - Users -

Network Operator: -


Network Operator -

Network Operator -

2G.20. READER. Personal Behaviour

T314,T315 DFC Service Order to be used


Low – Number of transaction raised in the period 1/7/14-30/6/15 – 259




Users - Users -

Network Operator: -


Network Operator -

Network Operator -


Page | 53

2G.21. READING. Data Quality

T243, T246 Existing B2B Transaction (subset) – MeterDataVerify and MissingMeterDataNotification to be used


Low – Number of transaction raised in the period 1/7/14-30/6/15 – 21,379 .: 2010 – 628 2011 – 3029 2012 – 7208 2013 – 11280 2014 – 18185 2015 – 23272 Volumes for missing meter reads vs verify meter reads not currently provided




Users - BAU until COB 22 April – enter into GASS Agree format for re-entering and tagging inflight READING. Data Quality by the end of February

Users - Capture and store details from customers

Users - Re-raise READING. Data Quality (MDV) from Report in date order, tagged as pre-cutover so dates can be recovered Raise captured ones post go-live as per BAU

Network Operator: -

Network Operator - Cancel open READING. Data Quality issues on 22 April, prepare report of open READING. Data Quality send to Retailers and continue undertaking work via manual process for exceptions Agree format for re-entering and tagging inflight READING. Data Quality by the end of February Develop priority list for when

Network Operator - Only continue

Network Operator – Accept MDV . Data Quality (MDV) and match it to manual report so can complete within SLAs


Page | 54

these get re-raised Heightened focus on rapid closure of MDN/MDV from March onwards

2G.22. RFSOFENQ RFS Offer Enq – any queries regarding the offer on the RFS including when a customer enquires about RTA road traffic control changes or when an offer will be made or re-offered.

Proposal is to utilise conceptual Portal to manage interaction

Access arrangements – bilateral agreements Network code – NSW government (overlap with NERR & NERL) AER





Users Phone / Email Details – Ref ROCL (The new BAU Process)

Users

Network Operator: Network Operator – BAU till COB 22nd April

Network Operator – Process phone / email (The new BAU Process)


2G.23. RSTRTN - Restoration problem – there has been a restoration issue identified at a site.

T314,T315 This refers to restoration of site conditions e.g. footpath as opposed to the gas supply. DFC (Dissatisfied customer) SO to be used.





Users - User - See Service Order transition plan (low)

Users - Users -


Page | 55

AER

Network Operator: -

Network Operator - See Service Order transition plan (low)

Network Operator -

Network Operator -

2G 24. RUSHHWB Rush or hot Water Breakdown Issues

Proposal is to utilise conceptual Portal to manage interaction For basic connection, send through SCR/MFX with Connection Type = H.





Users - Users - See Service Order transition plan (High)

Users - Users -

Network Operator: -

Users - See Service Order transition plan (High)

Network Operator -

Network Operator -

2G.25. SITECOND- Site Specific condition information/queries from customer to network – i.e information that may affect the way the contractor performs the network connection.

Proposal is to utilise conceptual Portal to manage interaction A consumer wants to pass on information about site conditions to the contractor such as if site is clean, and clear or any specific information that may affect the way the contractor performs the





Users - Users - BAU till 22nd April

Users Phone Details – Ref ROCL

Users New Process

Network Operator: -


Network Operator – Process phone

Network Operator – New Process


Page | 56

network connection.

2G.26. SNMIS Serial Number Mismatch – a customer identifies that the meter serial number being charged does not match the serial number on the meter that is supplying gas at the site.

Crossed Meter Template (GIP Trans 354 and 355). EK: T242/T243 MeterDataVerifyRequest/Response with InvestigateCode = Cross Meter and the associated Cross Meter Investigation Template (email)


Low – Number of transaction raised in the period 1/7/14-30/6/15 -1217



Users - Users – New process from COB 22 April 2016

Users - BAU

Users – BAU

Network Operator: -

Network Operator – New process from COB 22 April 2016 In flights moved onto new form Provides report of in-flights to Users

Network Operator - In flights moved onto new form

Network Operator - BAU

2G.27. SOENQ - Service Order Enq


N/A Low Number of transaction raised in the period 1/7/14-30/6/15 1847





Users

Users -

Network Operator: -




Network Operator: -


Page | 57

2G.28. SPNT - Supply Point Issues


Low Number of transaction raised in the period 1/7/14-30/6/15-3





Users

Network Operator: -




2G.29 - SUPNEWNo Supply after Network Connection was completed.


Low Number of transaction raised in the period 1/7/14-30/6/15– 2





Users

Network Operator: -





Page | 58

2G. 30. SUPADD -Supply Address Enq – an enquiry regarding the supply address including adding an address in the system or changing the address on the RFS.



Low - Number of transaction raised in the period 1/7/14-30/6/15 - 9





Users

Network Operator: -




Section 3 – Meter Reading functions.

These are meter reading interactions that are not described in GASS Application guideline. They are the daily and non-daily scheduled meter reading that the Jemena send to Users.

Parent Process



the current process









3. Provision of scheduled meter read

3.1 Basic Meters (TCCH)

T41 Access arrangements – bilateral agreements Network code – NSW/ACT government (overlap with NERR & NERL) AER

AEMO – AEMO – increased volume of reads ahead of 23 April

AEMO – AEMO –

Users -

Users - Adjust NSRD in January bills – managing customer notifications

User-

User-

Risks: the ongoing meter reading issues are unresolved – large volume of estimates


Page | 59

Reference service agreements

2. If go-live date shifts (mitigation – retain the compression) Have a go/no-go decision point in January pre notifying customers

Network Operator – Jemena Meter Reading Cutover Plan.

Jemena Meter

Reading Cutover Plan presentation for NARGP.pdf

AGL questions –

Key dates – Friday 22 April Last day of meter reading Monday 25 April Anzac Day Tuesday 26 April Final clean-up of meter reading data (unprocessed/skips) by 12pm Monday 2 May Meter reading operations resumes with download and issue of routes Tuesday 3 May Scheduled meter reading commences

Network Operator - Optimisation of route to meet new regulatory environment Advance reading of sites so there is no reading of sites over cutover period By mid December provide additional report with sites impacted NSRD and updated DPI listing (additional report by route type eg monthly, quarterly) In March need update for DPI listing and additional report for monthly sites impacted post go-live Data from Friday 22 reads to be provided 26/04/2016–

Network Operator - No scheduled reads from gas day 26 April to gas day 2 May 2016 (inclusive)

Network Operator - Monthly routes will be rescheduled back to 4 week cycle In July reschedule quarterly reads back to quarterly schedule

Risks:


Page | 60

3.2 Interval Meters (IM)

Access arrangements – bilateral agreements Network code – NSW/ACT government (overlap with NERR & NERL) AER Reference service agreements

AEMO – N/A AEMO – N/A

AEMO – N/A AEMO – N/A

Users -

Users - Process files from Jemena

User- Will receive Network Bill and IM file on 27 April

User- Process backlog files from Jemena


Network Operator - Provide Network Bill and IM file to Retailers for gas days 1st April – 26th April (up to 6:30am 27th April) on 27th April 2016 in non-B2B format as per BAU

Network Operator - Will send Network Bill and IM file on 27 April

Network Operator - Provide Network Bill and MDN files (one file per gas day) to Retailers for gas days 27th April – 1st May (up to 6:30am) by the 6th of May 2016 BAU from the 2nd May 2016 daily MDN files


Page | 61

Section 4 – Network Billing functions

These are network billing interactions that are not described in GASS Application guideline that Jemena sends to Users.

Parent Process

Sub Ref#, Sub Process -


the current process









4 Network billing

4.1. Billing disputes

T351 and T352 Access arrangements – bilateral agreement Reference service agreements



Users -

Users - Focus on closing open billing disputes (from now). Also focus on investigations that could lead to a billing dispute eg cross meter). (from now). Heightened focus on rapid closure of disputes for the bills from March onwards

User- No disputes raised over cutover unless material

User- Disputes for data from 1st April to 26th April will be via manual process and will be resolved Disputes for data from 27th April onwards will use the new B2B Process Adjustments (cancel/rebill) will be reflected in Retailers BAU Network Bill

Network Operator -

Network Operator - Focus on closing open billing disputes (from now).

Network Operator -

Network Operator -


Page | 62

Also focus on investigations that could lead to a billing dispute eg cross meter). (from now). Heightened focus on rapid closure of disputes for the bills from March onwards

4.2 Invoicing .

T331, T332 and T334

Access arrangements – bilateral agreement Reference service agreements



Users -

Users - Advise business of off-cycle bill

User-

User-

Network Operator -

Network Operator - One-off special bill – 27 April with due date as per normal arrangement One-off bill will include excluded service charges

Network Operator - No network billing

Network Operator - Issue bill 1st week of June

10 May bill effectively came out on 27 April, next bill is 1st week of June (will include manual work over cutover)


Page | 63

Section 5 – Contract admin billing system (CABS)

Parent Process

Sub Ref #, Sub Process - Brief description of

the current process









5 Contract admin billing system

5.1 Users Daily Nominations. Users Access the NWO. Nominations by Users Confirmed Nominations to Shipper/PO .

Reference Service Agreement (RSA)



Users - BAU – Nominations provided per current SLAs.

Users - BAU – Nominations provided per current SLAs. .

User-

User-

Network Operator -

Network Operator -

Network Operator - Potential outages window (6pm 1st May – 6am 2 May).

Network Operator -

5.2 HWU file (specific to AGL)

N/A AEMO –. AEMO – AEMO. AEMO –.

Users – As this is a specific AGL and Jemena arrangement, the transition plans for this process are

Users -

User-

User-


Page | 64

between AGL and Jemena.

Network Operator - As this is a specific AGL and Jemena arrangement, the transition plans for this process are between AGL and Jemena.

Network Operator -

Network Operator -

Network Operator -


Page | 65

Part 2 - Business to Market Operator (B2M) interactions between User and Market Operator, Network Operators and Market Operator or vice versa.

Section 1 – Delivery Point Registry Transactions (DPRT)

Sub Section A - Delivery Point – New and Deactivation

Parent Process

Sub Ref #, Sub Process - Brief description of the current process









1A Delivery Point – New and deactivation

1A.1 User Initiates New Delivery Point Transaction and send to AEMO DPRTInitNewDeliveryPoint Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction

The process will be done by the NWO instead of the User – See GIP T94)

RMP Section 9

Med AEMO – AEMO –

AEMO – Cancel inflights on 29 April. These are “in progress” The normal cancellation transaction notice will not be sent because the volumes can jeopardise the ability to be operative on the new systems at 06:30 on 2 May. Instead a report of DPI cancelled

AEMO –


Page | 66

due to the NARGP migration will be issued on 30 April between the hours 09:00 to 12:00 to the NWO and the Users who raised initiated the new DPI

Users -

Users - BAU until COB 22 April

User-

User- Reconcile report from AEMO Pre-Shutdown with report from NWO post cutover


Network Operator – BAU up to COB 22 April, then stop sending the NC file and SO Response to Users Receive and process all cancellations before GASS shutdown on 27 April

Network Operator –.

Network Operator – Use report from AEMO to trigger and send MFX notifications to AEMO Generate by User a report of MFX notifications to AEMO

1A.2 Notification to NWO of New Delivery Point Transaction from AEMO DPRTNotifyNewDeliveryPoint

No equivalent process in new RMP and GIP

RMP Section 9

AEMO – AEMO –

AEMO – See 1A.1

AEMO –


Page | 67

Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction

Users -


User-



Network Operator – BAU up to COB 22 April, then stop sending the NC file and SO Response to Users Receive and process all cancellations before GASS shutdown on 27 April


Network Operator – Use report from AEMO to trigger and send MFX notifications to AEMO Generate by User a report of MFX notifications to AEMO

1A.3 – User initiation of Deactivation of Delivery Point Transaction to AEMO DPRTInitDeact Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction


RMP section 10

AEMO – AEMO –

AEMO – See 1A.1

AEMO –

Users -

Users - BAU until 22 April

User-



Network Operator – BAU up to COB 22 April, then stop sending the DE file and


Network Operator – Use report from AEMO to trigger and send MIRN status update to AEMO


Page | 68

SO Response to Users Receive and process all cancellations before GASS shutdown on 27 April

Generate by User a report of MIRN status update to AEMO

1A.4 Notification to NWO of Deactivation of Delivery Point Transaction from AEMO DPRTNotifyDeactivationOfDeliveryPoint Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction


RMP section 10

Medium AEMO – AEMO –

AEMO – See 1A.1

AEMO –

Users -

Users - BAU until 22 April

User-



Network Operator – BAU up to COB 22 April, then stop sending the DE file and SO Response to Users Receive and process all cancellations before GASS shutdown on 27 April


Network Operator – Use report from AEMO to trigger and send MIRN status update to AEMO Generate by User a report of MIRN status update to AEMO


Page | 69

Sub Section B – Change of User and Meter Read Request

Parent Process

Sub Process - Brief description of the current process



Priority Initial transition plan expectations





1B Change of User

1B.1 User initiation of Change of User Transaction sent to AEMO DPRTInitChangeOfUser (in-situ) Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction

T170, T187, T191, T196, T205, T222, T227

RMP Section 6

Med AEMO – AEMO – By End February Devise plan to stagger re-raising of cancelled transfers (in-situ 15k) – move-ins first as priority, then oldest first – by planned completion date (BAU + additional load), aim to clear backlogs within 2 weeks

AEMO – – Cancel inflights on 29 April. These are COU processes that are “in progress” The normal cancellation transaction notice will not be sent because the volumes can jeopardise the ability to be operative on the new systems at 06:30 on 2 May. Instead a report of DPI cancelled due to the NARGP migration will be issued on 30 April between the hours 09:00 to 12:00 to the NWO and the Users who

AEMO – In the case of a Transfer that is an Interval metered site and the requested date of the transfer is between 29th Arp 2016 to 1st May 2016 inclusive process the “Manifest Data Error request e-mail.

Need to ensure proper analysis on volumes and ramp-up is undertaken.


Page | 70

raised the COU.

Users -

Users - BAU with the following additional step for a Transfer that is an Interval metered site and the requested date of the transfer is between 29th Arp 2016 to 1st May 2016 inclusive. For Transfers that fall into this category, an e-mail containing a subject heading “Interval site transfer schedule for 29th Arp 2016 to 1st May 2016 for MIRN <insert MIRN #> is to be sent to [email protected]. The content of the e-mail is to a request a “Manifest Data Error under Chap 12 and this e-mail need to include the date of transfer.

User- BAU until 29 April noting the step in previous column.

User- Reconcile User’s system with AEMO’s report Re-raise cancelled transfers from AEMO report – staggered due to volumes


Network Operator – BAU To continue to provide the TCCH until 26 April



1B.2 Notification from AEMO of Change of User Transaction to Network Operator DPRTNotifyChangeOfUserToNWO

T185 T187, T191, T196, T205, T222, T227

RMP Section 6

AEMO – See 1B.1

AEMO – See 1B.1 and 1B.5

AEMO – See 1B.1

AEMO – See 1B.1

See 1B.1 and 1B.5



Page | 71


Users - See 1B.1

Users - See 1B.1

User- See 1B.1

User- See 1B.1

Network Operator – See 1B.1


Network Operator –. See 1B.1


1B.3 – Notification from AEMO of Change of User Transaction to Current User DPRTNotifyChangeOfUserToUser Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction

T184 T187, T191, T196, T205, T222, T227

RMP Section 6

AEMO – See 1B.1

AEMO – See 1B.1 AEMO – See 1B.1

AEMO – See 1B.1

See 1B.1

Users - See 1B.1

Users - See 1B.1

User- See 1B.1

User- See 1B.1





1B.4 AEMO request for move-in meter reading from NWO READREQ

T181 T187, T191, T196, T205, T222, T227

RMP Section 6

AEMO – See 1B.1

AEMO – See 1B.1 AEMO – See 1B.1

AEMO – See 1B.1

See 1B.1


Page | 72

DPRTMeterReadingRequest Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction

Users - See 1B.1

Users - See 1B.1

User- See 1B.1

User- See 1B.1





1B Change of User

1B.5 User initiation of Change of User Transaction sent to AEMO DPRTInitChangeOfUser (move in) Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction

T 170 T187, T191, T196, T205, T222, T227

RMP Section 6

Med

AEMO – AEMO – From when Jemena’s system goes down (23 April), AEMO to send daily file between 09:00 to 11:00 of move-in transfers to NWO to determine if reconnection is required (approx. 49 needed turn ons last year) And see 1B.1

AEMO – See 1B.1

AEMO – See 1B.1

Cancellation notices will be issue however from 23rd April won’t reach NWO system Action on all – analysis on volumes and ramp-up,

Users -

Users - BAU

User- BAU until 29 April

User- Reconcile User’s system with AEMO’s report Re-raise cancelled transfers from AEMO report – staggered due to volumes When re-raise move-in transfers will also raise


Page | 73

MIRN discovery, special read request and MTN if required, as per new BAU


Network Operator – BAU To continue to provide the TCCH until 26 April Build a widget to read AEMO’s daily file of move ins and to find out if reconnection is required

Network Operator –. Check list of move-ins and find out if reconnection is required Do field work and manually capture

Network Operator – Update systems with work done over cutover (meters reconnected etc) Check re-raised transfers for duplicated MTN

Sub Section C – Standing Data

Parent Proces

s


Cross ref notes to

GIP transaction

s








1C Standing Data

1C.1 User initiation of Change of

Standing Data Transaction to AEMO

INTCOSD DPRTInitChangeOfStandingData


RMP Section 8

AEMO – AEMO – Cancel inflights 29 April, create report and sent to Retailers

AEMO – AEMO –


Page | 74


Users -

Users – BAU until COB 22 April

User- Stockpile

User- Any held over, advise NWO of the details




Network Operator – NWO to send GasMeterNotification/MIRNStatusUpdate

1C.2 Notification of Change of Standing Data Transaction form AEMO to NWO NETOP Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction


RMP Section 8

AEMO – See 1C.1

AEMO – See IC.1

AEMO – See IC.1

AEMO – See IC.1

Users - See IC.1

Users - See IC.1

User- See IC.1

User- See IC.1

Network Operator – See IC.1


Network Operator –. See IC.1


Sub Section D – Deliver Point Register Information

Parent Process



Details of any existing

Priority and estimated




Post go-live activities (Rules and

Other Notes, including any


Page | 75

regulatory or contract obligation that govern this process

number of transactions

Procedures apply)

“In flight” arrangements

1D Standing Data

1D.1 User or NWO Delivery Point Information Request sent to AEMO REQINFO DPRTInformationRequest Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction


RMP Section 16

AEMO – AEMO – There are unlikely to be any of these. Any raised will be actioned and will be closed out and responded too before 18:00 on Friday 29th Apr

AEMO – AEMO –

Network Operator -

Network Operator - BAU until COB 22 April

Network Operator - Stockpile

Network Operator -

Users -


User- Stockpile

User-

1D.2 Delivery Point Information Response from AEMO to NWO or User DPINFO DPRTInformationResponse


RMP Section 16

AEMO – See 1D.1

AEMO – See 1D.1

AEMO – See 1D.1

AEMO – See 1D.1

Network Operator - See 1D.1

Network Operator -

Network Operator -

Network Operator -


Page | 76


Users - See 1D.1

Users - See 1D.1

User- See 1D.1

User- See 1D.1

Sub Section E – Correction Transaction

Parent Process










1E Correction Transaction

1E.1 User sends Initiation of Correction Transaction to AEMO NITCORR DPRTInitCorrection Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction

Only applicable for transfers – T2135

RMP Section 11

AEMO – AEMO – AEMO – Cancel inflights on 29 April. These are Error Correction processes that are “in progress” The normal cancellation transaction notice will not be sent consistent with 1B.1 Instead a report of DPI cancelled due to the NARGP

AEMO –


Page | 77

migration will be issued on 30 April between the hours 09:00 to 12:00 to the NWO and the Users who raised the Error Correction

Users -

Users - BAU until COB 22 April, then stop

User- Stockpile

User-





1E.2 AEMO sends Notification of Correction Transaction. to User and NWO NOTFCORR DPRTNotifyCorrection Note: For this process Participants and AEMO have the ability to raise the transaction listed below as part of this process. These therefore form part the transition plan for this process. DPRTObjection DPRTNotificationOfObjection DPRTWithdrawalOfObjection DPRTNotifyWithdrawalOfObjection DPRTNotifyPermittedTransaction DPRTNotifyCompletedTransaction DPRTCancellationOfTransaction DPRTNotifyCancellationOfTransaction

AEMO – See 1E.1

AEMO – See 1E.1

AEMO – See 1E.1

AEMO – See 1E.1

Users - See 1E.1

Users - See 1E.1

User- See 1E.1

User- See 1E.1

Network Operator – See 1E.1


Network Operator –. See 1E.1



Page | 78


Page | 79

Section 2 – Estimation Reconciliation and Forecasting Transactions (ERFT)

The ICD list the following ERFT transactions and because they are internal with AEMO systems are out of scope of industry transition plans. The transactions are: ERFTDailyReportToSTTM, ERFTWeeklyReportToSTTM,

ERFTPreMonthlyReportToSTTM, ERFTFinMonthlyReportToSTTM, ERFTRevMonthlyReportToSTTM

Sub Section A – Gas wholesale quantities and meter readings

Parent Process










2A

2A.1 Total Quantity of Gas Injected From NWO to AEMO All Network Receipt Points within each Network Section are to be provided ERFTTotalGasInjected TOTGAS.

T2000

RMP Section 31.2 & 33.1

AEMO – Keep ERF system running which includes generating reports and posting them via the normal means. Any outage period to be kept to a minimum which will take into account periods when the system needs to be available.

AEMO – BAU

AEMO – BAU

AEMO –

Users -

Users -

User-

User-


Page | 80

Network Operator – Keep system running which includes generating out bound transaction for AEMO as per the prescribed timeframe set out in the RMP. Any outage period to be kept to a minimum which will take into account periods when the system needs to be available


Network Operator –. BAU


2A.2 Linepack and Unaccounted For Gas – From NWO to AEMO ERFTLinepackAndUnaccountedForGas

T2005

RMP Section 31.2 & 33.1

AEMO – As per Part 2, 2A.1



AEMO –

Users -

Users -

User-

User-

Network Operator – As per Part 2, 2A.1


Network Operator –. As per Part 2, 2A.1



Page | 81

2A.3 Participant’s Change in Linepack and Unaccounted for Gas. NWO to AEMO. ERFTParticipantCLPandUAG PARCLPUAG

T2020 RMP Section 31.2 & 33.1

Medium AEMO – As per Part 2, 2A.1



AEMO –

Users -

Users -

User-

User-





2A.4 Matched Allocations data. NWO to AEMO. ERFTMatchedAllocationsData

T2025 RMP Section 33.1

Medium AEMO – As per Part 2, 2A.1



AEMO –

Users -

Users -

User-

User-





2A.5 – Meter Readings. From NWO to AEMO ERFTMeterReadings METREAD HWU (NWO to AGL)

T2117 RMP Section 21



As per Part 2, 2A.1 [Note - new systems functionality to be operational from 2nd May that will check all reads and



Page | 82

perform adjustment to the previous read date (eg – add one calendar day to the date) where that previous read is a calendar date prior to the 2nd May.]

Users -

Users -

User-

Users -



Network Operator –. As per Part 2, 2A.1 N


2A.6 Daily Meter Readings sent from AEMO to User ERFTMeterReadingToUser


Medium AEMO – As per Part 2, 2A.1. No transition plan required as it is BAU till 2 May

AEMO – As per Part 2, 2A.1 No transition plan required as it is BAU till 2 May


AEMO – Retain the file created on 1 May and place on the FTP server for 1 week.

Users – No transition plan required as it is BAU till 2 May

Users - No transition plan required as it is BAU till 2 May

User- No transition plan required as it is BAU till 2 May

User-






Page | 83

2A.7 Daily Meter Readings from AEMO to User for non STTM. ERFTMeterReadingToUserNonSTTM

T2165 RMP Section 21

Medium AEMO – As per 2A.6

AEMO – As per 2A.6


AEMO –

Users – As per 2A.6


User- As per 2A.6

User-





Sub Section B – Wholesale Estimation Results

Parent Process










2B

2B.1 T Estimation Results from AEMO to User ESTREUSR

T2180

RMP Section 32.1




AEMO –


Page | 84

ERFTEstimationResultsToUser Users – As per 2A.6


User- As per 2A.6

User-





2B.2 Revised Estimation Results from AEMO to USER REVRESUSR ERFTRevisedEstimationResultsToUser

T2185

RMP Section 32.1




AEMO –



User- As per 2A.6

User-





2B.3 – Estimation Results from AEMO to Network Operator ERFTEstimationResultsToNWO ESTRESNWO


AEMO – No transition plan required as it is BAU till 2 May



AEMO –

Users -

Users -

User-

User-


Page | 85

Network Operator – By end February 2016 in consultation with the AEMO , develop process to receive and input files from AEMO via alter method BAU till 22 April




2B.4 Revised Estimation Results AEMO to Network Operator REVRESNWO ERFTRevisedEstimationResultsToNWO


Medium AEMO – No transition plan required as it is BAU till 2 May



AEMO –

Users -

Users -

User-

User-

Network Operator – By endFebruary 2016 in consultation with the AEMO , develop process to receive and input files from AEMO via alter method BAU till COB 22 April





Page | 86

2B.5 Reconciliation Results AEMO to Network Operator RECRES ERFTReconciliationResults Only ACT


Medium AEMO – No transition plan required as it is BAU till 2 May



AEMO –

Users -

Users -

User-

User-

Network Operator – By end February 2016 in consultation with the AEMO , develop process to receive and input files from AEMO via alter method BAU till COB 22 April





Page | 87

Sub Section C – Reports from AEMO to Users

Parent Proces

s


Cross ref notes to

GIP transaction

s





During Shutdown activities Post go-live activities (Rules and Procedures apply)


2C

2C.1 ERFT Reports from AEMO to Users: ERFTDailyReportToUser ERFTWeeklyReportToUser ERFTPreMonthlyReportToUser ERFTFinMonthlyReportToUser ERFTRevMonthlyReportToUser ERFTChangeOfStandingDataReport ERFTDailyNSLReport ERFTApportionmentPercentageReport ERFTCustomerChurnReport ERFTBasicConsumptionReport ERFTTotalGasInjectedReport DLYRESUSR WKYRESUSR MTHPREUSR MTHFINUSR MTHREVUSR DLYCOSDREP DLYNSLREP DLYAPREP DLYCHURN MTHBCSCON DLYTOTGAS

T2210, T2215, T2220, T2225, T2230 T2170, T2205, T2195, T2175, T2155, T2200

ICD Appendix A



AEMO – As per 2A.6 expect for the following reports ERFTChangeOfStandingDataReport ERFTDailyNSLReport; ERFTApportionmentPercentageReport ERFTTotalGasInjectedReport. These reports are normally issued on the 20:00 to 21:00 on Sunday 1 May 2016. Instead they will be issued on the Monday 2 May 2016 between the hours of 06:30 to 12:00.

AEMO – Reports posted MIBB



User- As per 2A.6

User- Access reports from MIBB



Network Operator –. Network Operator –

2C.2 Forecasting Data From AEMO to Users ERFTForecastingData

T2190

RMP Section 26.1




AEMO –


Page | 88

FCAST



User- As per 2A.6

User-



Network Operator –. Network Operator –

Section 3 – Imbalance And Incentives Transactions (IAIT)

Parent Process










3A

3A.1 Notification of Daily Imbalance from NWO to AEMO IAITNotificationOfDailyImbalance For ACT

T2030

RMP Section 30.1

AEMO – Keep ERF system running which includes generating reports and posting them via the normal means. Any outage period to be kept to a minimum which will take into account periods when the

AEMO – BAU

AEMO – BAU

AEMO –


Page | 89

system needs to be available.

Users -

Users -

User-

User-

Network Operator – Keep system running which includes generating out bound transaction for AEMO as per the prescribed timeframe set out in the RMP. Any outage period to be kept to a minimum which will take into account periods when the system needs to be available




3A.2 Notification of Revised Imbalance From AEMo to Users IAITRevisedImbalance

T2280

RMP Section 30.1

AEMO – As per Part 2, 3A.1. No transition plan required as it is BAU till 2 May



AEMO – Retain the file created on 1 May and place on the FTP server for 1 week.


Page | 90

Users – No transition plan required as it is BAU till 2 May

Users - No transition plan required as it is BAU till 2 May

User- No transition plan required as it is BAU till 2 May

User-





3A.3 Imbalance Trade from Users to AEMO IAITImbalanceTrade


Medium AEMO –

AEMO – BAU till 22 Apr

AEMO – No processing from 22 Apr to 2 May

AEMO – Process stockpiled transaction

Note – Very low volumes. zero transaction in 2014, 2 transition in 2015

Users -

Users - BAU till 22 Apr

Users - Stockpile from 22 Apr to 2 May

User- Sumit Stockpiled trades 2 May





3A.4 Notification of Matched Imbalance Trade / Notification of Expired Imbalance Trade - From AEMO to Users

T2285, T2290 RMP Section 30.1

Medium AEMO – As per Part 2 3A.1

AEMO – As per Part 2 3A.1


AEMO –


Page | 91

IAITNotificationOfMatchedImbalanceTrade IAITNotificationOfExpiredImbalanceTrade

Users - As per Part 2 3A.2



User-





3A.5 Request for Participant Imbalance Amount. From User to AEMO IAITRequestParticipantImbalanceAmount





AEMO –




User-





3A.6 Notification of Participant Imbalance Amount From AEMO to Users IAITNotifyParticipantImbalanceAmount


Medium AEMO – As per Part 2 3A.1



AEMO –


Page | 92




User-






Page | 93

Section 4 - RoLR

Parent Process

Sub Ref # Sub Process - Brief description of the current process









4 Retailer of Last Resort

4.1 Customer and Site Details (Monthly)


Low AEMO – AEMO – BAU

AEMO – BAU AEMO – BAU

Users -

Users - BAU

User- BAU

User- BAU


Network Operator

Network Operator


4 4.2 ROLR Event T905 – T1070

RMP Section 5.4

Low AEMO –

AEMO – From mid-April to 2 May to mitigate the risk of a RoLR event occurring heighten prudential checks undertaken.

AEMO – BAU

AEMO – BAU

Users –

Users - From mid-April if requested by AEMO top up securities accordingly.

User- BAU

User- BAU


Page | 94



Network Operator –.BAU

Network Operator –BAU

Part 3 – Miscellaneous transitional function that do not fall with the framework of Parts 1 or 2.

Section 1 – Retention of Gass+ historical information – requirements, format, how far back, etc

Parent Process











1 1.1 Online access to GASS

AEMO – AEMO – AEMO – AEMO –

Users –

Users - Develop requirements for Jemena system extract (GASS+ history) late January Review mock up system extract by mid March

User-

User-


Page | 95


Network Operator – Develop requirements for Jemena system extract (GASS+ history) late January Provide mock up system extract early March for User review Provide system extract to Users (agree timing by early April. Extract will be delivered by 22

April) Extract must be provided inclusive of all transactions up until COB 22 April



Section 2 – Planned Gas Network Interruptions

Parent Process











1 2.1 Planned interruptions (daily/as req)

T330

AEMO – AEMO – AEMO – AEMO –


Page | 96

Users –

Users -

User-

User-


Network Operator – Jemena to notify Users of planned interruptions prior to system outage.



Section 3 – New Participant Registration

Parent Process











1 3.1 New Participant Registration

AEMO – AEMO – In mid-January issue internal advice to AEMO registration team to prevent Participants wherever possibility nominating entrée into the NSW/ACT Gas Retail Market for the period 1 April to 1 June

AEMO – No new Participant activation from 22nd April to 2 May inclusive

AEMO –


Page | 97

Users –

Users -

User-

User-






Page | 98

Attachment C – Industry Plans for transitioning off existing NSWACT function matrix – AGNL/APA Networks

The following is the Industry Transition Plan for the Wagga Wagga and Tamworth network sections.

Section 1 Wagga Wagga and Tamworth network sections

In relation to both the Wagga Wagga and Tamworth network sections, the following changes apply to the whole of Attachment B.

Change Type Part Section Sub Ref# Process Column Details

Deletion Part 1 Section 2, Sub Section B 2B.3 MeterFix (unclaimed/additional) All Not applicable to WWT

Deletion Part 1 Section 2, Sub Section C 2C.2 Unclaimed supply point All Not applicable to WWT

Deletion Part 1 Section 2, Sub Section F 2F.1 Network Tariff Change Calculation All Not applicable to WWT

Deletion Part 1 Section 2, Sub Section G 2G.4 Common Factor enq. All Not applicable to WWT

Deletion Part 1 Section 5 5.1 and 5.2 Contract admin billing system All Not applicable to WWT

Deletion Part 2 Section 2, Sub Section A 2A.3 ERFTParticipantCLPandUAG All Not applicable to WWT

Deletion Part 2 Section 2, Sub Section A 2A.4 ERFTMatchedAllocationsData All Not applicable to WWT

Deletion Part 2 Section 2, Sub Section B 2B.3 ERFTEstimationResultsToNWO All Not applicable to WWT

Deletion Part 2 Section 2, Sub Section B 2B.4 ERFTRevisedEstimationResultsToNWO All Not applicable to WWT

Deletion Part 2 Section 2, Sub Section B 2B.5 ERFTReconciliationResults All Not applicable to WWT

Deletion Part 2 Section 3 All Imbalance and Incentives Transactions (IAIT)

All Not applicable to WWT

Modification Part 1 Section 2, Sub Section A 2A.1 Retail services - medium priority GIP transaction column

Remove unclaimed MFX from list of Service Orders

Deletion Part 1 Section 2, Sub Section D 2D.2 Special meter read - intermediate read (SRA)

All Not applicable in WWT.


Page | 99


Modification Part 1 Section 3 3.2 Provision of meter reads (interval meters)

Network Operator Provide network bill from gas days 27 April to 31 May in June

Modification Part 1 Section 3 3.2 Provision of meter reads (interval meters)

Network Operator BAU from 2 May 2016 (not a MDN)

Section 2 Tamworth network section

In relation to Tamworth network section the whole of Attachment B applies, noting the following changes in addition to those shown in Section 1.


Modification Part 1 Section 1, Sub Section A 1A.1 Critical gas incidents Users

From COB 22 April, phone APA: 1800 427 532 - Post go-live routed to Envestra – Wagga Wagga (AGNL).

Modification Part 1 Section 1, Sub Section B 1B.1 Critical gas incidents Users

From COB 22 April, phone APA: 1800 427 532 - Post go-live routed to Envestra – Wagga Wagga (AGNL).

Modification Part 1 Section 2, Sub Section A 2A.1 Retail services - medium priority Users Send to APA instead of JGN from COB 22 April

Modification Part 1 Section 2, Sub Section A 2A.2 Retail services - low priority Users Send to APA instead of JGN from COB 22 April

Modification Part 1 Section 2, Sub Section B 2B.2 SCR, MFX, MRM User

Stockpile SCR, Raise MFX and MRM if required over the shutdown period - to AGN not Jemena

Modification Part 1 Section 4 4.2 Invoicing Network Operator APA to issue Tamworth bill in June (not JGN)


Page | 100

Section 3 Wagga Wagga network section

In relation to Wagg Wagga network section the whole of Attachment B applies, noting the following changes in addition to those shown in Section 1.


Deletion Part 3 Section 1 All Access to GASS historical information All Not applicable to WW

Modification All All All All All Replace Jemena (JGN) with AGN

Modification All All All All All Replace GASS with NSW Metering System

Modification Part 1 Section 1, Sub Section A 1A.1 Critical gas incidents Users Phone APA: 1800 427 532, remove initial training step (as this is BAU)

Modification Part 1 Section 1, Sub Section B 1B.1 Critical gas incidents Users Phone APA: 1800 427 532, remove initial training step (as this is BAU)

Modification Part 1 Section 1, Sub Section A 2A.1 Supply Problem Users

Stockpile & if critical raise via BAU ie ring NRC, perform field work & raise as DB SO post go-live

Modification Part 1 Section 1, Sub Section A 2A.2 Temp Disconnection Users

Stockpile & if critical raise via BAU ie ring NRC, perform field work & raise as DB SO post go-live

Modification Part 1 Section 2, Sub Section B 2B.1 New Connection Quotes Users

BAU until COB 22 April.

For quotes not yet performed - Retailers to re-submit request via B2B after 0630 on 2 May

For quotes performed but not yet accepted - Retailers to re-submit request via B2B after 0630 on 2 May with comment “quote accepted”

For quotes performed and accepted, Retailers will receive list of cancelled WOs and will re-submit via B2b after 0630 on 2 May with comment “quote accepted”


Page | 101


Modification Part 1 Section 2, Sub Section B 2B.1 New Connection Quotes Network Operator


For quotes not yet performed, AGNL will advise User to re-submit after 0630 am 2 May. AGNL will perform quote within original SLAs.

For quotes accepted by customer. AGNL will cancel WO and send Retailers a report of closed WOs

Modification Part 1 Section 2 Sub Section 2B.2 .Basic Connection Network Operator Cancel open SO on 24 April i.e. not 22 April

Modification Part 1 Section 2, Sub Section D 2D.1 SRF Users

BAU until COB 22 April. Submit via email post 22 COB April for SRFs to be performed before Wednesday 4 May (due to 2 business day notice period).

Post go-live receive B2B MDN

Modification Part 1 Section 2, Sub Section D 2D.1 SRF Network Operator

BAU until COB 22 April. From COB 22 April, receive emailed requests for SRFs and undertake field work.

Between 2 May and 4 May enter the reading into the system and supply reading details via a B2N MDN

Modification Part 1 Section 2, Sub Section D 2D.2 SRA, SRT, SRR User


For Special Reference Reads (SRR) follow process in Part 1, 2D.1.

For other special reads – stockpile and submit post 6:30 am 2 May.

Modification Part 1 Section 2, Sub Section D 2D.2 SRA, SRT, SRR Network Operator


For Special Reference Reads (SRR) follow process in Part 1, 2D.1.

For other special reads – No activity over the shutdown period.


Page | 102


Modification Part 1 Section 2, Sub Section G 2G All All Users

Follow normal BAU process until COB 22 April. Stockpile from COB 22 April, unless urgent. Urgent to be emailed until COB 27 April and then stockpiled

Modification Part 1 Section 3 3.1 Provision of meter reads (basic meters) Network Operator

Provide meter read schedules by end January and meter type size codes by 31 March

Note that AGNL will be reading meters on 2 May in Wagga Wagga.

Modification Part 1 Section 3 3.2 Provision of meter reads (interval meters) Network Operator

Daily interval meter file delivery - BAU

BAU until COB Sunday 1 May, new format as at Monday 2 May

Provide Network Bill Retailers for gas days 1st April – 26th April (up to 6:30am 27th April) on 28 April 2016 in non-B2B format as per BAU

Modification Part 1 Section 4 4.2 Invoicing Network Operator Pre shutdown: Network bill will be provided on 28 April

Modification Part 2 Section 1, Sub Section A 1A.1 Delivery Point initiation Network Operator Replace NC with Closure report and stop sending Closure report on 27 April

Modification Part 2 Section 1, Sub Section A 1A.3 Delivery Point deactivation Network Operator Replace DE with closure report, and stop sending Closure Report on 27 April

Modification Part 2 Section 1, Sub Section B 1B.1 Change of user (in-situ) User BAU until COB 22 April, stockpile and re-raise

Modification Part 2 Section 1, Sub Section B 1B.1 Change of user (in-situ) Network operator BAU until COB 22 April

Modification Part 2 Section 1, Sub Section B 1B.5 Change of user (move in) User

BAU until COB 22 April, then check DPR extract - if meter not commissioned then email requesting meter turn on (as per ROCL)

Modification Part 2 Section 2, Sub Section A 2A.1 ERFTTotalGasInjected Network Operator BAU

Modification Part 2 Section 2, Sub Section A 2A.2 ERFTLinepackAndUnaccountedForGas Network Operator BAU

Modification Part 2 Section 2, Sub Section A 2A.5 ERFTMeterReadings Network Operator BAU

Modification Part 2 Section 2, Sub Section A 2A.6 ERFTMeterReadingToUser Network Operator BAU


Page | 103


Page | 104


Page | 105


Page | 106

Attachment D – Industry Cutover Plan

1. Document Purpose

The purpose of this document is provide collective agreed guidance for industry participants and AEMO, for the NARGP cutover period, with respect to the following cutover issues:

Cross-Industry Management, Decision Making (incl. Escalation), Reporting, & Communications

Go/no-go readiness criteria – identify the risks and requirements for contingency plans and/or dress rehearsal

Establishing a timeline of activities

Production Verification Test

Initial post go-live monitoring The cutover period is defined as 18:00 on Friday 29 April 2016 to 06:30 on Monday 2 May 2016 (AEST) inclusive.

For each of these cutover activities, this document will generally provide guidance within the following categories:

what is a collective industry requirement that must be adhered to by all participants

what is a User, Network Operator and AEMO responsibility but requires visibility at industry level

Other elements of the cutover period which are not covered by this document are:

Cross business data migration for AGNL owned Tamworth network, that has been historically operated by Jemena. This activity is already planned and managed by Jemena and AGNL as a discrete activity within the cutover period. The guidelines within this document need to be consistent with that plan (vide Section 4).

2. Management, Decision Making (incl. escalation), Reporting, & Communications plan

2.1 Introduction

This section outlines responsibilities for:

Control/management (framework and responsibilities)

Decision making (responsibilities, process incl. escalation process)

Reporting (Status, Readiness, Fix on Fail decisions)

Communications tools (& responsibilities) to support the above.

2.2 Control/management framework and responsibilities

Cutover will be planned by the TCWG:

TCWG representation is both a Cutover Manager, and a Business representative from each participant, and representation from AEMO

The TCWG meets on a regular basis to plan cutover and issue management on a case by case basis.

Industry cutover will be executed by individual businesses working in accordance with the timeframes set out in section 4. These participants will be individually pro-active in participating at agreed levels as follows:


Page | 107

providing initial input to the industry schedule,

reporting completion of activities / milestones;

identifying & escalating issues,

attending meetings as required to resolve issues that may arise Issues will be initiated and managed on a participant by participant basis unless escalated to the TCWG to manage the issue on an industry basis. The TCWG will either make industry wide decisions relating to cutover, or agree to escalate the issue/decision to the NARGP-CF.

2.3 Representatives

Participants should identify representatives within their organisation for the cutover activities and ensure they are clearly identified within the Industry Contact List (see section 7).

2.4 Cutover dependencies

The pre-requisites to invoke this Cutover plan are:

(i) AEMO has published the effective date for version 15.0 of the Retail Market Procedures (Procedures) and version 2 of the Gas Interface Protocol (GIP);

(ii) the Cutover Timetable (Industry schedule) and Responsibilities set out in section 4 are complete and agreed by the TCWG; and

(iii) the teleconferencing details and Industry Contacts details set out in section 5 are complete and agreed by the TCWG.

2.5 Decision making (responsibilities, process incl. escalation process).

Participants will escalate issues that require resolution at industry level to the TCWG. Issues that require resolution at the industry level are those that may jeopardise the ability of AEMO and other Participants interacting under the version 15 of the Procedures and version 2 of the GIP that take effect 6:30 am on the 2 May 2016. Participants are to notify the chair of the TCWG (by telephone / email) who will arrange a meeting to suit the circumstances (e.g. face to face, telephone hook-up, email notification).

The TCWG makes decisions relating to the resolution of issues that have been escalated within constraints established by regulatory mandates (Procedures etc.). There are many scenarios where the TCWG will simply agree a course of action for execution by all or some Participants. In other scenarios, the TCWG could make recommendations to the NARGP-CF, requesting a decision.

Significant decisions in relation to extraordinary unforeseen events will be escalated via individual Participant CEOs.

2.6 Industry Schedule

The industry cutover schedule is set out in section 4 and is maintained by AEMO.

2.7 Communications

The objective of communications is to ensure that AEMO and all Participants are able to communicate with each other whilst, at the same time, being able to keep other players in the cutover informed of progress and issues that have arisen that may have an impact on them.


Page | 108

2.7.1 Communications Processes:

These communications will be instigated by project staff within each business on an as-required basis to ensure readiness for the particular interaction. Method is appropriate to the situation, i.e. telephone or email as the preferred methods, with escalation points to individual Project Managers in the event escalation is required using 24 X 7 escalation procedures detailed in this cutover plan.

Second level communications will be initiated by Project Managers raising industry issues for decision by the TCWG / NARGP-CF as required.

Third level communications will be initiated by TCWG / NARGP-CF reps raising key issues to individual CEOs (or a nominated representative) or a CEOs' meeting for consideration. It is expected that level 3 communications will relate only to extraordinary events / decisions that may put the cutover plan at extreme risk. It is also expected that these events are highly unlikely to occur.

2.8 Reporting

The objective is to facilitate an industry wide view of participant status and readiness for cutover

Pre-agreed reporting timeframes, methods, and tools are used. Two key areas are:

‘Readiness reporting. In the lead up to the go-live decision, reporting of market readiness takes place via the NARGP Market Readiness Report which details each participants’, and the overall industry, progress towards a number of key milestones as detailed in the NARGP Market Readiness Approach. This reporting takes place on a monthly basis, with reports submitted to the NARGP inbox no less than 7 business days in advance of each month’s NARGP-CF meeting. The consolidated readiness report is discussed at each meeting and a collective decision made regarding industry status/readiness and any issues/recommendations requiring escalation and/or endorsement.

Each Business Day during the overall period 22 April 2016 - 29 April 2016, AEMO will facilitate a teleconference call commencing at 09:30. All Participants are to attend these sessions and advise the status/readiness to invoke the cutover process that commences at 18:00 on Friday 29 April. It should be noted that Monday 25 April 2016 is not a Business Day because of ANZAC day therefore no teleconference will take place this day. At the conclusion of each teleconference but no later than 16:00 hrs, a status report will be issued that describes AEMO and each Participants progress against invoking the cutover process that commences 18:00 on Friday 29 April. The report will also note any key issues that AEMO or Participants may have incurred that would potentially put the cutover “at risk”. This would include what initiative is in place to mitigate the risk.

The reporting periods may extend beyond the periods indicated, by mutual agreement by the TCWG. Meetings management will be maintained by AEMO. See section 4 for further details.


Page | 109

3. Cut-over Activities

This section details the following cutover activities:

Connectivity testing

Production verification testing

Reporting and monitoring For each of these transition and cutover activities, this document will generally provide guidance within the following categories:

what is a collective industry requirement that must be adhered to by all participants

what is a User/Network Operator bilateral responsibility (including initial data loads) but requires visibility at industry level

what is a Network Operator/AEMO bilateral responsibility (including initial data loads) but requires visibility at industry level

Participants will be responsible for developing their own cutover plan such that it is compatible with the overall Industry Cutover plan set out in section 3 and 4 of this document.

3.1 Certification

The following information on certification is provided in this document for contextual purposes only. As described in clause 1.3.4 of the Retail Market Procedures (RMP) AEMO and each Retailer and Network Operator must be certified as compliant by AEMO prior to using the FRC HUB for transactions specified in the Gas Interface Protocol. The Gas FRC Business to Business connectivity Testing and System Certification document published on AEMO website provides further information the criteria when Participants need to certify and the steps to achieve certification.

For NARGP, as per the NARGP Certification Plan, the formal certification window, for all participants except APA/AGNL, runs from 7 March to 25 March 2016, with 3 allocated slots of 5 days for each Participant. A re-certification window will run for one-week after the completion of the Market Trial on 25 March 2016, until 1 April 2016, to allow for re-certification if required. APA/AGNL will certify in the two week period from 13 April to 27 April 2016.

3.2 Initial Connectivity Testing (ICT)

3.2.1 Intent of ICT

Certification is undertaken against the pre-production Hub responders. In terms of Panel 1 (connectivity) certification, this validates:

That the protocol and messaging conforms to the required ebXML standard as adopted for Gas Hub messaging, including reliable delivery handling.

Connectivity against the pre-production environment FBS or FBSTEST responders only. The intent of the initial connectivity testing phase is to validate connectivity, noting that:

Connectivity can only be demonstrated against production environment trading partner gateways explicitly and individually.

With the Hub on webmethods 7.x or higher, each relevant trading partner combination has to be configured as a separate trading partner agreement (TPA) at the Hub and also within each partner gateway (sender or receiver) running on webMethods 7.x or higher.

Confirming network or ebxml message level connectivity (using a Message Service Handler Ping/Pong exchange as referenced in the PBP3 system architecture document and eb messaging specification document) with the Hub alone is not sufficient to guarantee a gateway’s full end to end exchange with another partner will be successful.


Page | 110

Being able to verify as many partner combinations as possible well in advance of the cutover weekend will mitigate the risk of connectivity issues delaying PVT, as connectivity issues can be time consuming to fix.

3.2.2 ICT process

AEMO and Participants will use their best endeavours to have their production Gateways configured available for connectivity testing by Friday 15th April which is two weeks prior to cutover period.

In the period from Monday 18th April to Friday 22nd April inclusive, Retailers/Network Operators/AEMO are to perform basic connectivity checks to confirm:

that each participant has connectivity to the FRC B2B Hub;

that each participant has connectivity through the FRC B2B Hub to each of the other participants gateways they must communicate with (trading partners). That is (i) AEMO can exchange ebXML messages with every Retailer and Network Operator, (ii) every Retailer can connect to AEMO and to every Network Operator, and (iii) every Network Operator can connect to AEMO and to every Retailer. This may be done using Message Service Handler Ping/Pong exchange (referred to as ebXML ping/pong).

All participants (including AEMO) with ebXML connectivity and MIBB account access will take an active role in the Initial Connectivity Testing activities.

The role of the AEMO hub is to ensure non repudiated delivery of correctly addressed transactions.

By Monday 7th March, AEMO will e-mail TCWG reps requesting the period (a period between Monday 18th April to Friday 22nd April inclusive) in which their organisation will make available their production Gateways for ICT. If AEMO doesn’t receive a response to this request AEMO will assume that the Retailers or Network Operators will not be taking part in the ICT.

By Tuesday 15th March, AEMO will e-mail the TCWG reps a list of what organisation are taking part in the ICT and the period their production gateways will be available for ICT.

3.2.3 Pre-requisites for ICT

The following activities must be completed and reported before Initial Connectivity Testing

activities5:

AEMO production hub must be live.

User/Network Operator/AEMO Participant gateways must be live.

Participant MIBB Accounts set up

AEMO/Network Operators/Users have fulfilled their certification obligation as set in clause 1.3.4 of the Retail Market Procedures (NSW/ACT) that will take effect on 2 May 2016 and that they have received advice from AEMO advising that certification was successful.

i. Initial Connectivity Testing activities

User/Network Operator/AEMO Participant B2B interfaces are ready in the Production environment (i.e. all components have been migrated, the B2B interface setup has been confirmed in Production, any appropriate shakedown activities have been conducted, staging tables have been confirmed as clear etc.)

5 I-e-: internal participant technical start-up activities will naturally occur before this


Page | 111

Participants confirm connectivity to the MIBB.

Participants to establish network connectivity to the production MIBB for their NSW/ACT retail gas systems and users. This should include via both FTP and HTTP.

All relevant MIBB accounts required for normal market use after go live (user or batch system) to be established and access validated. i.e. read access to all private subfolders for that participant’s accounts, and write access to the Upload folders for selected accounts. Network operators should also have additional access for at least one account to write to the complete_mirn_listing folder.

3.3 Test of System Changes

Production Verification Testing is defined as a limited and controlled set of production transactions between participants (including AEMO), to provide added confidence that production systems are in fact fully ready. Production Verification Testing occurs prior to full production loads being placed on participant systems.

Productive verification tests will be defined by the TCWG.

3.3.1 Pre-requisites for Production Verification Testing

The pre-requisites for Production Verification Testing (PVT) are:

AEMO and all Retailers and all Network Operators systems have completed certification and have received advice from AEMO that their systems have successfully passed certification.

The AEMO and all NWO, and all User wishing to commence PVT have deployed and successfully tested all their required system changes for NARGP.

For a given User/Network Operator pair, initial connectivity testing must have progressed to a stage where both gateways are live and connected to the AEMO hub, and both Partners have a backend system capable of generating a Production Verification transaction. PVT is “live data”

3.3.2 Production Verification Test Execution

In order to validate a successful cut-over of the NARGP changes a Production Verification Test will take place.

For the purposes of PVT, during the PVT period the Retail Market Procedures (NSW AND ACT) (version 15) apply to the provision, delivery or receipt of information, notices, documents, requests and reports.

The PVT period is part of the transition period to allow for production verification testing prior to the transition time. Transition period and transition time are defined in the Procedures v.14.1 (Part H – Transitional Provisions).

The PVT period will be determined by AEMO and specified in the notice of the transition period published by AEMO on the AEMO website.

a) Each Retailer will send each Network Operator a transaction

The type of transactions will comprise but not limited to:

MIRN Discovery Request (T280)

Amend Customer Contact Details (T70)


Page | 112

Service Order Request (T314)

Meter Data Verify Request (T242)

Only one transaction per transaction type is to be sent

b) Each Retailer will send AEMO a transaction


Customer Transfer (T170)


c) Each Network Operator will send each retailer a transaction


MIRN Discovery Response (T281) (note – in response to the one sent above)

Meter Site Access Information Change (T67)

Service Order Response (T315) (note – DB initiated service order)

Meter Reads (T41)


d) Each Network Operator will send AEMO a transaction


Meter Read (T42)


e) AEMO will send each Network Operator and each retailer a transaction.


Notice of Transfer (T183, T184 and T185) Transitional Provision final stage consultation Only one transaction per transaction type is to be sent

f) All transactions will be acknowledged with BOTH an ebXML acknowledgement and an aseXML transaction acknowledgement as appropriate.

The above transaction will be “live” market transactions. Participants will pre-identify the transaction that will be provided to the Retailer / Network Operator. These will be sent to AEMO ([email protected]) before 5pm Tuesday 26 April 2016. AEMO will collate this information and provide to the participants before 5pm Friday 29 April 2016.

Note – In the case of CATSNotification, for confidentiality reasons AEMO will not include MIRN to the Retailer who is to receive this notice.

.

During the PVT window (15:00 – 19:00 on Sunday 1st May 2016):

AEMO will be available to assist where participants have issues that arise.

All participants would be holding back all transactions other than those that are included in the test.



Page | 113

4. Cutover Timetable (Industry schedule) and Responsibilities

Step Event Market Time/EST Responsible Party

1. Using the template in appendix A, participants to provide AEMO ([email protected]) their transaction list for PVT.

Tuesday 26/04/16

Before 17:00 AEST

All Participants

2. Send transaction list to participants detailing transactions they are expecting to receive

Friday 29/04/16

Before 17:00 AEST

AEMO

3. Cease generating and sending outbound transactions

Batch jobs completed before this time

Invoke the use of the processes described in the NARGP Industry Transaction and Cut-over Plan (Attachment B).

Friday 29/04/16

18:00 AEST

All Participants

4. Clear both incoming and outgoing failures from the GRMBS FTP Inbox Outbox

All transactions processed

Friday 29/04/16

Before 20:00 AEST

All Participants

5. Via Teleconference:

Confirm all gateways are cleared of transactions

Confirm that gateways can be brought down at this time

Confirm readiness to continue onto next Cut-over step

Friday 29/04/16

20:00 AEST

All Participants


Confirm readiness to commence Cut-over (for those who are implementing on Sunday).

Report Cut-over progress (for those implementing on Friday, Saturday or Sunday).

Sunday 1/05/16

09:00 AEST

All Participants

7. Perform basic connectivity checks (i.e. ebXML Ping/Pong

Sunday 1/05/16

10:00 – 12:00 AEST

All Participants



Page | 114

test6) noted in section 4 to re-confirm connection to FRC Hub.

Ensure Systems ready to commence PVT (ie NARGP systems are online)


Participants to provide an update on Cut-over progress

Confirm readiness for 15:00 PVT on track

Sunday 1/05/16

11:30 AEST

All Participants

9. Internal troubleshooting period allowed to validate gateways are operational

Re-establish connectivity to FRC Hub

Sunday 1/05/16

12:00 – 14:00 AEST

All Participants


Confirm readiness to start Production Verification Testing

Sunday 1/05/16

14:30 AEST

All Participants

11. Conduct PVT as outlined in section 3.3.2 above.

Sunday 1/05/16

15:00 – 19:00 AEST. [Note – The above date and time is a guide. As prescribed in section 3.3.2 PVT period will be determined by AEMO and specified in the notice of the transition period published by AEMO on the AEMO website]

All Participants


Provide feedback on Production Verification Testing

Determine success of cutover

Sunday 1/05/16

19:30 AEST

All Participants

13. Systems in Production

All transactions sent with R34 schema

Transactions commence as per the Controlled Production Start plan.

Monday 2/05/16

Post 06:30 AEST

All Participants

14. Via Teleconference: Monday 2/05/16 All Participants

6 Ebxml Ping/Pong testing requires AEMO and all NWO's to ping/pong all Retailers and all Retailers to ping/pong AEMO and all NWOs. EbXML Ping/pong refers to a Message Service Handler Ping/Pong exchange as referenced in the PBP3 system architecture document.


Page | 115

Refer to section 6: post-go-live 09:30 AEST

5. Teleconferencing Details and Industry Contacts

As detailed in this Cut-over plan, there will be a number of teleconferences to manage and monitor participant progress. The details of the teleconference are as follows:

Teleconference Chair: TBA

+61 2 8884 5050 - NSW

+61 7 3347 3030 - QLD

+61 8 8201 7363 - SA

+61 3 9609 8989 - VIC

1300 654 386 - WA, ACT, NT

Passcode: TBA

This passcode will remain the same for all teleconferences held during the cutover period

Name Organisation Email Phone

TBA (AEMO) Chair Person

Market Operator

TBA (Primary) AEMO FBS Admin

TBA (Secondary) AEMO FBS Admin

TBA (Primary) AEMO

TBA (Secondary) AEMO

TBA (Primary) AEMO / CGI

TBA (Secondary) AEMO / CGI

Network Operators

TBA (Primary) Jemena Gas Networks (NSW) Ltd

TBA (Secondary) Jemena Gas Networks (NSW) Ltd

TBA (Primary) ActewAGL Distribution Ltd


Page | 116


TBA (Secondary) ActewAGL Distribution Ltd

TBA (Primary) Australian Gas Networks (NSW) Pty Limited

TBA (Secondary) Australian Gas Networks (NSW) Pty Limited

TBA (Primary) Central Ranges Pipeline Pty Limited

TBA (Secondary) Central Ranges Pipeline Pty Limited

Retailers

TBA (Primary) AGL Energy Sales & Marketing Limited

TBA (Secondary) AGL Energy Sales & Marketing Limited

TBA (Primary) Origin Energy LPG Limited

TBA (Secondary) Origin Energy LPG Limited

TBA (Primary) Origin Energy LPG Limited No. 2

TBA (Secondary) Origin Energy LPG Limited No. 2

TBA (Primary) EnergyAustralia Pty Ltd

TBA (Secondary) EnergyAustralia Pty Ltd

TBA (Primary) EnergyAustralia Pty Ltd No. 2

TBA (Secondary) EnergyAustralia Pty Ltd No. 2

TBA (Primary) Red Energy Pty Limited


Page | 117


TBA (Secondary) Red Energy Pty Limited

TBA (Primary) Lumo Energy (NSW) Pty Ltd

TBA (Secondary) Lumo Energy (NSW) Pty Ltd

TBA (Primary) Covau Pty Limited

TBA (Secondary) Covau Pty Limited

TBA (Primary) M2Energy Pty Ltd (T/As Dodo Power & Gas)

TBA (Secondary) M2Energy Pty Ltd (T/As Dodo Power & Gas)

TBA (Primary) GOEnergy Pty Ltd

TBA (Secondary) GOEnergy Pty Ltd

Self-Contracting Users

TBA (Primary) Visy Paper

TBA (Secondary) Visy Paper

TBA (Primary) Visy Pulp and Paper Pty Ltd

TBA (Secondary) Visy Pulp and Paper Pty Ltd

TBA (Primary) BlueScope Steel Limited

TBA (Secondary) BlueScope Steel Limited

TBA (Primary) OneSteel Manufacturing Pty Limited

TBA (Secondary) OneSteel Manufacturing Pty Limited

TBA (Primary) Qenos Pty Ltd


Page | 118


TBA (Secondary) Qenos Pty Ltd

TBA (Primary) Snowy Hydro Limited

TBA (Secondary) Snowy Hydro Limited


Page | 119

6. Post Go-live

To mitigate risk of the FRC Hub being flooded with transactions built up during the cutover period, from 15:00 AEST on Sunday 1 May all participants with the capability to, will (i) manage business processes to avoid flooding and/or (ii) limit the amount of transactions sent through their gateway to the FRC Hub. Attachment F of the Industry Transition, Cutover and Controlled Production Start (CPS) Plan document sets out the agreed maximum transaction through put that covers “business as usual” and the stockpiled transaction accrued over the outage period.

On the morning of Monday 2 May, all participants will monitor their backend systems and gateways to ensure successful Cut-over. A meeting will be held at 09:30 AEST to determine the success or otherwise of the Cut-over across the industry. Corrective action will be decided on issues and defects identified based upon their severity and market impact.

For the remainder of that week (Tuesday 3rd May to Friday 6th May inclusive) additional teleconference will be held at 15:00 each day.

6.1 Controlled ramping-up period

Any required controls during the ramping up period will be defined by the TCWG. The scope of the controlled ramp up covers “Business as Usual” transactions and the processing of the transactions with held over or re-raised as set out in the Attachment F of the Industry Transition, Cutover and Controlled Production Start (CPS) Plan.

6.2 Post go-live monitoring

This is the increased level of technical and business transaction monitoring, in place for a short post go-live period (with the length of this period to be defined by the TCWG). Participants may provide this support either via an extended cutover model (cutover tail), or via their business-as-usual production support infrastructure.

6.2.1 Initial post go-live Production Transaction Monitoring

Immediately post Go-Live monitoring of transactions will be required by all participants to ensure the new FRC systems are working correctly. Due to the highly integrated nature of the systems, it is likely that problems will be encountered that will require cooperation between market participants to resolve them.

The following level of transaction monitoring would be desirable to help assess the correct operation of systems.

Daily volumes of transactions processed through the hub (timing to be agreed).

Post Go-live monitoring will also include “health check points” for a typical gas day. The timeframes and the process referred to within the new Procedures was used as basis of the “health check points”.

Daily Health Check Point Report for gas day for – 2nd May 2016

Time period (AEST) Process and time Parties involved Actual time process occurred and was it successful

06:30 – 09:30 Total Quantity of Gas Injected, Linepack and Unaccounted For Gas received by 08:30

NWO to AEMO


Page | 120

Provision of Energy Data (daily metered delivery points on STTM) received

by 09:30

NWO to AEMO

11:00 Teleconference review check point

09:30 – 12:30 Estimation Results received by 10:00

AEMO to NWO

Revised Estimation Results received by 10:30

AEMO to NWO

STTM Daily Distribution System Allocation Data received by 10:30

AEMO to Users

Provision of Energy Data (daily metered delivery points on non-STTM)

received by 12:00

NWO to AEMO

STTM Daily Distribution System Allocation Data to Users

Customer Churn Data Report by 12:00

AEMO to Users


12:30 – 15:30 Heating values for the gas received by 13.30

NWO sends to AEMO

STTM Weekly Distribution System Allocation Data received by 14:00

AEMO to User

Daily Meter Readings (STTM) received by 14:00

AEMO to Users

Apportionment Percentage Report by 14:00

AEMO to Users


15:30 – 18:30 Heating values for the gas published by 17.00

AEMO send to MIBB

Provision of Energy Data (non-daily metered delivery points on STTM) received

by 17:00

NWO to AEMO

Estimation Results received by 17:00

AEMO to Users


Page | 121

Estimation Results received by 17:00

AEMO to NWO

Daily Meter Readings (Non-STTM) received by 17:30

AEMO to Users


18:30 – 21:30 Forecasting Data received by 19:00

AEMO to Users

Change of Standing Data Report by 20:00

AEMO to Users

NSL Daily Report by 20:30 AEMO to Users

Apportionment Percentage Report by 21:00

AEMO to Users

Total Gas Injected Report by 21:00

AEMO to Users

21:30 – 00:30

00:30 – 03:30 Request for move-in meter reading received by 00:30

AEMO to NWO

03:30 – 06:30

By 12 noon on the next gas day, AEMO will e-mail the daily health check report to the NARGP-CF and NARGP-TCWG. The issuing of this report will cease when two consecutive reports reveal no delays or issues.

6.2.2 Initial post go-live Issues/Defects Resolution

Due to the highly integrated nature of the systems the types of defects are likely to be widespread. These include Transaction failure (eg: aseXML format issues), Back-end application failure, Gateway configuration issues, HUB connectivity etc.

For an initial period it has been suggested that any defects that potentially impact participants should be visible to industry.


Page | 122

As defects in production systems are identified, they should be assessed for impact on other industry participants, and where a possible industry impact is identified, they should be communicated to other market participants immediately.

Communication of defects will allow the following to occur:

Participants will be able to make allowances for defective functionality in other participants’ software by reducing the flow of transactions or reverting to manual transactions.

Participants will be able to assess their own systems to determine if they are affected by the same defect

Participants will be able to avoid re-keying of failed transactions, or data integrity in their systems by early awareness of impacting defects

Participants will have the opportunity to communicate the impact on their own systems and business and set the priority of defects accordingly.

Lodging of Defects:

Any issue or defect that is found post go live is to be reported as per the Cutover Communications Plan.

Defects should be presented with sufficient details to allow an impact assessment by other participants. TCWG will prepare a defect template.

Participants are requested to maintain progress on posted defects.

6.2.3 Timing

It is anticipated that daily transactional monitoring and defect reviews will be required for the first weeks after Go-Live as noted above. At that point, an agreement should be reached as to the frequency and degree of monitoring and reporting that will be required by Participants on an ongoing basis.

6.2.4 Criteria to assess whether to close out daily post “go live” monitoring

Post go live daily monitoring is schedule to finish on Friday the 6th May. This is conditional that:

AEMO and all Participants are operating on productions systems that are compliant with the Procedures;

There are no “open” defect flagged as a “show stopper”;

On at least two occasions, the “health check point” report, reported no delays or issues; and

A NARGP-CF meeting has been schedule prior to the 31st May to review open issues.

Failure of any of the above conditions will result in the post “go live” monitoring continuing beyond Friday 6th May unless otherwise agreed with NARGP-CF.

6.3 Closure of Post go-live monitoring

It is anticipated that Post go-live monitoring will close on 31st May 2016. A final meeting of the NARGP-CF would be held to review any open issues and decide whether the issue is material


Page | 123

enough that remain open and determine the next step for the issue to be resolve which may include adding the issue to the Gas Retail Market Issue/Change Register for the Gas Retail Consultative Forum (GRCF) to consider.


Page | 124

Appendix A – PVT Transaction list template

Sample -


Page | 125

Attachment E – Plan for monitoring Transition activities progress in the lead up to cutover.

Item Date Activity Category Reference

1 30 November Jemena provide report on open SO, RFS and open network diaries to Retailers

Data cleanse – SO, quotes and network diaries

Part 1 Section 2 Sub Section A, 2A.1 Section 2, Sub Section B, 2B.1

2 By mid December

By mid December provide additional report with sites impacted Next Schedule Read Date (NSRD) and updated DPI listing (additional report by route type eg monthly, quarterly)

Optimisation of route to meet new regulatory environment. Advance reading of sites so there is no reading of sites over cutover period

Part 1 Section 3 Sub Section 3.1

11 January Implementation Progress meeting #1

3 By end Jan Retailers and Jemena to define detailed requirements for interim manual process (form/system extract, contact details, reconciliation process, tagging process etc.)

Medium priority SO – interim manual process Low priority SO – interim manual process Quotes –interim manual process

Part 1 Section 2 Sub Section A, 2A.1 Section 2, Sub Section A, 2A.2 Section 2, Sub Section B, 2B.1

1 February Implementation Progress meeting #2

4 15 February Jemena to provide updated extract report for all Open quote, diaries and SO items. Analyse and provide options to Retailers on management of open items.

Data cleanse - Quotes

Part 1 Section 2, Sub Section B, 2B.1

18 February Implementation Progress meeting #3

5 20 Feb Jemena and Retailers define and agree on the process which will commence on 22 April for emergency calls

High priority SO Part1 Section 1, Sub Section 1.A.1, and 1.B.1

6 By End Feb Jemena and Retailers to agree on approach for re-raising SO after go-live - approach for re-raising so that they can be reconciled - approach for prioritising (CPS)

Medium priority SO Low priority SO

Part 1 Section 2 Sub Section A, 2A.1 Section 2, Sub Section A, 2A.2 Section 2, Sub


Page | 126


7 By End Feb Create interim process (for use post Go-Live) for Retailers and Builders/Developers to accept converted quotes/offers

Quotes Part 1 Section 2, Sub Section B, 2B.1

8 By End Feb Interim process for Cutover period (to be used only for ‘urgent’ quotes to be agreed )

Quotes Part 1 Section 2, Sub Section B, 2B.1

9 By End Feb Agree a process for re-raising (via Gas Distribution Portal) those Requests for Quotes (RFS) that were open prior to cutover with no offer issued (subsequently cancelled) to maintain SLA’s

Quotes re-raising Part 1 Section 2, Sub Section B, 2B.1

10 By End Feb By end February develop and agree standard format in consultation with NWO for special reads:

- Tagging - Volumes (CPS)

Special reads Part 1 Section 2, Sub Section D, 2D.1

11 By End Feb Agree format for re-entering and tagging inflight READING. Data Quality by the end of February - VMDs

Reading data quality

Part 1 Section 2, Sub Section G, 2G.21

12 By End Feb By end February 2016, AEMO and NWO, develop process to receive and input files from NWO and AEMO via alternate method

ERFT files Part 2 Section 2, Sub Section, 2, 2A.1 – 2A.5, 2A.6

7 March Implementation Progress meeting #4

13 15 March Jemena to provide report on open SO, RFS and open network diaries to Retailers

Data cleanse – SO, quotes and network diaries

Part 1 Section 2 Sub Section A, 2A.1 Section 2, Sub Section B, 2B.1

14 March In March need update for DPI listing and additional report for monthly sites impacted post go-live

Optimisation of route to meet new regulatory environment. Advance reading of sites so there is no reading of sites over cutover period

Part 1 Section 3 Sub Section 3.1

22 March Implementation Progress meeting #5


Page | 127


15 By End March Retailers and Jemena to test the interim manual process for SO and quotes

Medium priority SO – interim manual process Low priority SO – interim manual process Quotes –interim manual process

Part 1 Section 2 Sub Section A, 2A.1 Section 2, Sub Section A, 2A.2 Section 2, Sub Section B, 2B.1

4 April Implementation Progress meeting #6




Page | 128

Attachment F – Industry Controlled Production Start (CPS) Plan

This section of the document will be updated as part of the process to develop the Controlled Production Start (CPS) Plan

Documents

NARGP Industry Transition Cutover and Controlled ... · NSW/ACT GAS RETAIL MARKET PROJECT – INDUSTRY TRANSITION, CUTOVER AND CONTROLLED PRODUCTION START PLAN Page | 2 DOCUMENT HISTORY