Dispatch and market notices
System Management must inform market participants and network operators of impending or current situations that could have security ramifications for market participants and network operators. It does this by issuing dispatch advisories in the following situations:
- Generation shortfall/load shedding is occurring or expected.
- Conditions where committed generation running at minimum levels will exceed forecast load (over-generation).
- Any ancillary service shortfalls.
- Major facility outages (generation, transmission, major loads).
- Fuel shortages that have a wide spread impact on the market.
- Dispatch or communication system outages.
- Notification of starting or ending a high risk or emergency operating state.
A dispatch advisory includes a statement of the operating state (normal, high-risk, or emergency) during the period to which the advisory relates. These advisories include information on how market participants should respond to the situation. The Market Rules recognise that sometimes System Management has to react so quickly to a situation that it is not able to issue a dispatch advisory until after the event.
Market participants are obliged to keep System Management informed of any circumstances they become aware of that might result in System Management issuing a dispatch advisory.
AEMO must inform market participants of impending situations that could impact market outcomes. It does this by issuing market advisories in the following situations:
- Market system outages, whereby aspects of the market cannot run normally due to systems failures.
- Notification of suspension of any aspect of the market.
Market advisories include information on how market participants should respond to the situation. Note that advisories related to dispatch are called dispatch advisories, and are issued by System Management.
The information provided below aims to keep users apprised of the latest system changes, status of participant change requests, API documentation, technical bulletins, end-of-life notices, and scheduled system outages.
The table below details the release and build which is currently running in each environment. The snapshot date indicates the date at which the last snapshot of live market data was taken for the environment, as applicable.
Environment Version Snapshot date Link Live
3.21 (Build 3.21-1236-24): RCM 1.1-2098-8
https://wems.aemo.com.au Trial 3.21 (Build 3.21-1236-24): RCM 1.1-2098-8 18 May 2017 https://wems-mkt.aemo.com.au
Trial environments can simulate the operation of the WEM, but actual market outcomes may vary in these environments due to testing activities of Market Participants and AEMO, differences in software versions, and the time since the last snapshot.
3.22 (Build 3.22-1297): RCM 1.2 2146 28 September 2017 (scheduled) Link 3.21 (Build 3.21-1236-24): RCM 1.1-2098-8 13 September 2017 Link 3.21 (Build 3.21-1236-22) 3 August 2017 Link 3.19 Patch 1 (Build 3.19-1192-13) 31 May 2017 Link 3.19 (Build 3.19-1192-10) 26 April 2017 Link 3.18 (Build 3.18-1183-5) 28 September 2016 Link 3.17 (Build 3.17-1149-11) 17 August 2016 Link 3.16 (Build 3.16-1105-2) 25 May 2016 Link 3.14 (Build 3.14-1016-3) 2 March 2016 Link 3.13.1 (Build 3.13.1-981-6) 13 January 2016 Link 3.13 (Build 3.13-981-1) 29 November 2015 Link 3.12 Patch 1 (Build 3.12-913-35) 28 October 2015 Link 3.12 (Build 3.12-913-9) 23 September 2015 Link 3.11 Patch 4 (Build 3.11-374-128) 15 July 2015 Link 3.11 Patch 3 (Build 3.11-374-116) 29 April 2015 Link 3.11 Patch 2 (Build 3.11-374-93) 6 March 2015 Link 3.11 Patch 1 (Build 3.11-374-81) 19 January 2015 Link 3.11 (Build 3.11-374-63) 10 December 2014 Link 3.10 Patch 2 (Build 3.10-99-63) 8 August 2014 Link 3.10 Patch 1 (Build 3.10.1) 11 June 2014 Link
Scheduled system outages
The following lists currently scheduled and past outages for WEMS:
System outage description
- IT User Group – 3 July 2015
- IT User Group – 20 March 2015
- Austraclear Testing Enhancement 5 Briefing Session – 14 August 2015