Release Information

Data Model 5.7

The Electricity Data Model 5.7 v1.01 is released.

NEMWeb

Release dates

For more information, see NEMWeb - 21 April 2026

 

MSUG Action Items

Updates to the MSUG Market Systems User Group action items

  • Inclusion of the 7-day pre-dispatch data is in testing.

  • LastChanged field in FPP tables and reports in progress.

For details, see MSUG Action Items.

IDX Knowledge Library

Based on feedback for Industry Data Exchange See Relevant Rules or Procedures learning content in MSUG, we have published the IDX Knowledge Library in the Technical Specification Portal.

 

The overview of the Basic Power Quality Data API is now available.

aseXML Schemas

Schema changes and release dates

Release dates

  • Pre-production: Tuesday 14 April 2026
  • Production: Thursday 14 May 2026

Portfolio Management System

The release dates for Portfolio Management System are updated.

Release dates

  • Pre-production: Wednesday 25 February 2026
  • Production: Thursday 19 March 2026

For more information, see EMMS - Portfolio Management System - March 2026

Data Model 5.6

Discontinued reports

In Electricity Data Model v5.6, the following tables are moved into HISTORICAL package:

  • BILLING_DIRECTION_RECONCILIATN
  • BILLINGCPDATA
  • BILLINGGENDATA
  • RESERVE
  • SET_RUN_PARAMETER
  • SETCPDATA
  • SETGENDATA
  • SETSMALLGENDATA
  • SETCPDATAREGION
  • SETGENDATAREGION

Participant interfaces changes

There was an error in the report version of the CSV Report A data report that loads into a data model table. Identified by its type, subtype, and version. For example: BILLING,BILLINGASPAYMENTS,2 Type in Participant Interfaces Changes. The latest Data Model The definition of the interface to participants of data published by AEMO for gas or electricity. A database conforming to the Data Model can contain a local copy of all current participant-specific data recorded in the main database. The Data Model includes database tables, indexes, and primary keys. v5.6 publish Energy Rules Terms corrects this.

Package

 

Data model table

 

File ID

 

CSV report type

Old

New

DISPATCH

DISPATCHLOAD

DISPATCHIS

DISPATCH,UNIT_SOLUTION,5

DISPATCH,UNIT_SOLUTION,6

 

DISPATCHLOAD

NEXT_DAY_DISPATCH

DISPATCH,UNIT_SOLUTION,5

DISPATCH,UNIT_SOLUTION,6

P5MIN

P5MIN_UNITSOLUTION

P5MIN

P5MIN,UNITSOLUTION,6

P5MIN,UNITSOLUTION,7

PRE-DISPATCH

PREDISPATCHLOAD

NEXT_DAY_PREDISPATCH_D

PREDISPATCH,UNIT_SOLUTION,4

PREDISPATCH,UNIT_SOLUTION,5

 

PREDISPATCHLOAD

PREDISPATCHIS

PREDISPATCH,UNIT_SOLUTION,4

PREDISPATCH,UNIT_SOLUTION,5

Production issue

There is a known issue in Production where the PARTICIPANT_REGISTRATION data does not load for PARTICIPANTCATEGORY table. The pdrLoader Software responsible for loading files to and from participant's local Data Interchange folders to the participant's DBMS. It can be installed in any environment supporting Java. fails after 10 attempts. AEMO Australian Energy Market Operator will publish an updated category to fix the issue and notify participants.

NEM Report Updates

On 14 August, AEMO sent a notice about the NEM reports for PDPASA DUIDAVAILABILITY and PDPASA REGIONSOLUTION tables were missing data for Interval Period over which interval energy data is recorded by the metering installation that corresponds to a TI or submultiples of a TI._DateTimes between 00:00 and 04:00 inclusive on the first trading day Energy Rules Terms, for PDPASA runs between 00:00 and 04:00 inclusive.

These updates are now available in production from 10:30 PD Pre-dispatch run onwards.

Updating Short Term PASA Rule - NEM Production system changes

AEMO has deployed all core changes to the ST PASA Short Term Projected Assessment of System Adequacy. A daily load forecast that shows expected demand two to seven days ahead of time. Procedure and Recall Period The advance notice (in hours) that a scheduled resource will require to achieve the PASA Availability MW for this trading interval. initiative in production.

Participants should ensure the bid PASA Availability PASA Availability  For a scheduled generating unit, scheduled bidirectional unit, scheduled load or scheduled network service in a given period, its available physical plant capability (taking ambient weather conditions into account) and any additional physical plant capability that can be made available during that period within a given recall period in accordance with the reliability standard implementation guidelines and its associated bid Recall Period The 288 periods from 4:30 am to 4:00 am. reflect the ST PASA Projected Assessment of System Adequacy. except executable files e.g., .DLLs, .LIBs and .EXEs with the user mentioned. See National Energy Rules Procedures from 31 July 2025. The Bidding system changes to add the new Recall Period were implemented in Production on 1 July 2025.

As part of the ST PASA Procedures consultation, the PD PASA and ST PASA LRC reports are discontinued, as these not used for operational decision Energy Rules Terms making.

Participants using the Data Interchange A set of cooperating applications used to replicate data between AEMO's energy market systems and a participant's DBMS conforming to the MMS Data Model. should subscribe to the latest file IDs using Data Subscription A web application in the Markets Portal used to subscribe to Data Interchange files and to obtain the latest MMS Data Model. These files are typically csv files containing public data and participant’s private data. AEMO recommends participant use of the Data Interchange suite of products, supplied by AEMO, to automate receiving and storage of the files to their systems. AEMO provides working sample software for FTP access (Participant Batcher) to MarketNet and working sample software for Data Interchange. in the Markets Portal Web applications for registered participants only. Requires access to MarketNet..

NEM report changes

  • Adds new PDPASA_DUIDAVAILABILITY and STPASA Short-term Projected Assessment of System Adequacy. 30 minute resolution, seven days ahead. A daily load forecast showing expected demand two to seven days ahead of time._DUIDAVAILABILITY report files:
    • For every PDPASA and STPASA run, publish Max Avail, PASA Avail and Recall Period for each half-hour for all scheduled resources
  • Updates following reports in existing Next Day Bid See Relevant Rules or Procedures files, to include the new Recall Period:
    • BIDMOVE_BIDPEROFFER_D_COMPLETE (file: PUBLIC_BIDMOVE_COMPLETE)
    • NEXTDAY_BIDOFFERPERIOD_ENERGY_SPARSE (file: PUBLIC_NEXT_DAY_OFFER_ENERGY_SPARSE)
    • NEXTDAY_MNSP_BIDOFFERPERIOD (file: NEXT_DAY_OFFER_ENERGY_SPARSE)
    • NEXTDAY_BIDPEROFFER_FCAS_SPARSE (file: PUBLIC_NEXT_DAY_OFFER_FCAS_SPARSE)
  • Updates following reports in the existing PDPASA and STPASA files:
    • PDPASA_REGIONSOLUTION
    • Updated calculation of AGGREGATEPASAAVAILABILITY, to reflect PASA Availability with a Recall Period ≤ 24 hours
    • Removed OUTAGE_LRC run type
    • PDPASA_INTERCONNECTORSOLN
    • Removed OUTAGE_LRC run type
    • PDPASA_CONSTRAINTSOLUTION
    • Removed OUTAGE_LRC run type
    • STPASA_REGIONSOLUTION
    • Updated calculation of AGGREGATEPASAAVAILABILITY, to reflect PASA Availability with a Recall Period ≤ 24 hours
    • Removed RELIABILITY_LRC, OUTAGE_LRC run types
    • STPASA_INTERCONNECTORSOLN
    • Removed RELIABILITY_LRC, OUTAGE_LRC run types
    • STPASA_CONSTRAINTSOLUTION
    • Removed RELIABILITY_LRC, OUTAGE_LRC run types

Sparse Data Filter Configuration Example

Sparse data filter configuration example included in Sparse Data Model.