Attachment 1 Initial draft list of high level scenarios – Last Updated: September 2017 Valid Contingency Scenarios The following are valid scenarios the CPWG agreed need to be developed under the Industry Contingency Plan. Ref # Scenario Description Likelihood Impact Priority Theme Trigger(s) Action(s) Accountability (High/ Medium/ Low) (High/ Medium/ Low) S01 RoLR event occurs during Systems Cutover period (30 Nov 4 Low Low Low Market Settlements AER declares RoLR AEMO / AER – Dec) event between 30 Nov to 4 Dec S02 RoLR event occurs during the transition period prior to Low Medium will affect Medium Market Settlements AER declares RoLR AEMO / AER – commencement of Systems Cutover (22 Nov 26 Nov) preparation activities event between 22 Nov – for systems cutover to 26 Nov S03 Natural disaster or emergency event occurs during the Low Medium/High higher Medium Emergency Emergency event DNSPs – transition and cutover period (e.g. flood, bushfire, cyclone, likelihood in QLD as Management declared by system black event) cutover occurs during Government to storm/cyclone Emergency declared by season LNSP S06 The B2B e-Hub is unavailable or B2B systems fail to Low High will cause B2B Medium IT Systems AEMO announces AEMO AEMO’s – come back within the cutover timeframe transactions in the cutover failure NEM to cease for an unspecified period S07 One or more retailers systems fail to come back within the Medium Low/Medium impact Medium IT Systems Retailer(s) advise Retailer(s) send Market Notice to advise of systems Retailer – cutover timeframe will be greater if a tier 1 AEMO of cutover failure failure system retailer’s can’t Retailer(s) implements contingency measures cutover in time S08 One or more distributors systems fail to come back within the Medium Medium/High Medium IT Systems Distributor(s) advise Distributor(s) send Market Notice to advise of DNSPs cutover timeframe AEMO of cutover failure systems failure Distributor(s) implement contingency measures S09 MSATS B2M systems fail to come back within the Low High will cause B2M Medium IT Systems AEMO announces AEMO to implement contingency measures AEMO and AEMO’s – cutover timeframe transactions in the MSATS cutover failure Market Participants implement contingency NEM to cease for an measures unspecified period
Attachment 1 – Initial draft list of high level scenarios Last Updated: September 2017 Valid Contingency Scenarios The following are valid scenarios the CPWG agreed need to be developed under the Industry Contingency Plan. Ref # Scenario Description Likelihood (High/ Medium/ Low) Impact (High/ Medium/ Low) Priority Theme Trigger(s) Action(s) Accountability S01 RoLR event occurs during Systems Cutover period (30 Nov – 4 Dec) Low Low Low Market Settlements AER declares RoLR event between 30 Nov to 4 Dec AEMO / AER S02 RoLR event occurs during the transition period prior to commencement of Systems Cutover (22 Nov – 26 Nov) Low Medium – will affect preparation activities for systems cutover Medium Market Settlements AER declares RoLR event between 22 Nov to 26 Nov AEMO / AER S03 Natural disaster or emergency event occurs during the transition and cutover period (e.g. flood, bushfire, cyclone, system black event) Low Medium/High – higher likelihood in QLD as cutover occurs during to storm/cyclone season Medium Emergency Management Emergency event declared by Government Emergency declared by LNSP DNSPs S06 The B2B e-Hub is unavailable or AEMO’s B2B systems fail to come back within the cutover timeframe Low High – will cause B2B transactions in the NEM to cease for an unspecified period Medium IT Systems AEMO announces cutover failure AEMO S07 One or more retailers systems fail to come back within the cutover timeframe Medium Low/Medium – impact will be greater if a tier 1 retailer’s system can’t cutover in time Medium IT Systems Retailer(s) advise AEMO of cutover failure Retailer(s) send Market Notice to advise of systems failure Retailer(s) implements contingency measures Retailer S08 One or more distributors systems fail to come back within the cutover timeframe Medium Medium/High Medium IT Systems Distributor(s) advise AEMO of cutover failure Distributor(s) send Market Notice to advise of systems failure Distributor(s) implement contingency measures DNSPs S09 MSATS and AEMO’s B2M systems fail to come back within the cutover timeframe Low High – will cause B2M transactions in the NEM to cease for an unspecified period Medium IT Systems AEMO announces MSATS cutover failure AEMO to implement contingency measures Market Participants implement contingency measures AEMO