Release Information

November 2026 MSUG 

The November 2026 Meeting Summaryand IDX WebSocket Event Notification demonstration are published.

Data Model 5.8 Production release

EMMS - Data Model 5.8 - Oct 2026 v3.00 is released. Data model 5.8 is now available in production. The release reports, upgrade scripts, and 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. config are available in the participant file server: \Releases\MMS Data Model\Production AEMO’s live system\v5.8.

Audience

Participants who exchange data with AEMO Australian Energy Market Operator systems, including submitting bids, receiving acknowledgements, and accessing private and next-day market data.

Participant impact

New reports

Set these reports to ACTIVE in pdrMonitor to load the data into your database:

  • BANK_GUARANTEE

  • CASH_SECURITY

Current reports

Participants subscribed to the following reports are moved to the legacy version and must subscribe to the current version to receive the new data:

  • BILLING

  • BILLING_INIT

  • BILLINGCALENDAR

  • SETTLEMENTS

  • SETTLEMENTS_EXTN

  • SETTLEMENTS_INIT

When you upgrade to the current reports the new columns are NULL until the Data Population Dates.

ST PASA Replacement tables parallel run

The new STPASA_SOLUTION and PDPASA (FNM) reports run in parallel with the current 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. and PDPASA reports from 30 November 2026 for information and familiarisation only and must not be used for financial decisions.

No auto-subscription to public files

Participants must review and manually subscribe to new public reports introduced from Data Model 5.8 onwards.

Update to INTERCONNECTEDID column

The INTERCONNECTEDID column length increases from 10 to 20 characters across all tables.

New transaction type support

The BILLING_GST_DETAIL table supports MAKEUP_AMOUNT as a valid TRANSACTION_TYPE value.

Regulation FCAS usage information table

4.5.1 New Table: DISPATCH_AGC_DATA includes the table structure only. We will communicate data population dates once available.

Data Model Manager update

Data Model Manager upgrades to v1.3.0 with security and licence agreement updates, and the upgrade is optional to implement Data Model v5.8.

Dates

Pre-production AEMO’s test system available to participants: 22 September 2026

Production: 20 October 2026

Related documents publication: 22 September 2026

Pre-production refresh: March 2027 (TBC To be confirmed)

More details

For more details, see Data Model v5.8.

Maximum Credit Limit Calculation

Audience

NEM Registered Participants Energy Rules Terms subject to AEMO's prudential requirements.

Participant impact

Review the updated Credit Limit Procedures Establishes the methodology for AEMO to determine the prudential settings for each NEM Market Participant so the prudential standard is met and monitor MCL Maximum Credit Limit values in Prudential Dashboard after revised calculation takes effect.

Background and rationale

This release updates the MCL calculation to align prudential requirements with the shortened settlement cycle. These changes include:

  • Reducing the Outstandings Limit period from 35 to 21 days

  • Using Time of Day pricing

  • Introducing calibration factors

  • Assessing credit and debit energy and reallocations separately

Dates

Production: 28 October 2026

Commencement of MCL assessments under shortened settlement cycle framework: 11 December 2026

More details

For more information on how the MCL is calculated, see the latest Credit Limit Procedures PDF available under Maximum Credit Limit.

NEM B2M and B2B archived message payloads

Audience

NEM Retail MSATS and B2B systems B2M Business-to-Market and B2B Business-to-Business. Generic term used to refer to defined business-to-business interactions between participants; excludes interactions between a participant and market systems such as MSATS. Registered Participants.

Participant impact

AEMO is proposing to reduce the archive retention period for NEM Retail B2M and B2B archived message payloads to 6 months from 13 months.

This proposed change applies to:

  • All B2M and B2B transaction groups.

  • Archived payloads accessed through FTP participant file folders, API Archive, MSATS web portal, and B2B browser.

Background and rationale

The current archive retention period is 13 months. Due to increasing archive volumes and associated storage and operational impacts, we are proposing to reduce the retention period to 6 months.

We sought feedback in industry forums regarding the current 13-month archive period and if it remains operationally necessary for participants. The feedback to move to a shorter retention period of 6 months emerged as the strongest supported position.

Dates

We will revise the 6-month archive retention period in February 2027 and advise the implementation date.

More details

For more details, download the slide pack.

AEMO Archive Message Payload Retention.pdf

Contact

nemreform@aemo.com.au

ICF017 ADWAN reporting changes - December 2026

Audience

Participants performing the Metering Data Provider Energy Rules Terms(MDP Metering Data Provider. An organisation which installs, commissions, gathers, and verifies data remotely from meters in the National Electricity Market (NEM).) or Local Network Service Provider Energy Rules Terms(LNSP) role.

Participant impact

AEMO is introducing new RM29 Active Data With Non-Active NMI Energy Rules Terms(ADWNAN) reporting queries. ADWNAN reporting is split by participant role and data quality type:

  • ADWNAN_INTERVAL_ACT - A report sent to LNSPs listing non-active NMIs with active datastreams containing interval data. This replaces the ADWAN_INTERVAL report from 6 December 2026.
  • ADWNAN_INTERVAL_SUBS - A report provided to MDPs listing non-active NMIs with active datastreams containing substituted interval data.

Background and rationale

The RM29 ADWNAN_INTERVAL report does not distinguish between actual and substituted interval data, resulting in additional investigation by LNSPs. ICF017 introduces separate reporting streams to direct actual data exceptions to LNSPs and substituted data exceptions to MDPs.

Dates

  • Pre-production: 17 November 2026
  • Production: 6 December 2026

Contact

nemreform@aemo.com.au

API URL changes - September 2026

Audience

GAS, NEM, and WEM participants.

Participant impact

The API URL Changes - September 2026 are in pre-production. Test the new 4 API changes at 4 API Changes.

Action the following:

  • Update integrations to use the new pre-production URLs.

  • Execute end-to-end connectivity and functional testing.

  • Validate:

    • Authentications and certificates.

    • API requests and response behaviours.

    • Existing business processes.

Dates

Pre-production: 17 June 2026

Production: 23 September 2026

Legacy URLs decommissioned: 1 December 2026

Contact

Contact External and internal business contacts, similar in functionality to an address book. A contact may be an internal contact within the participant organisation, or could be an external contact belonging to another market participant. apiuplift@aemo.com.au to raise any pre-production issues.

Industry Data Exchange

IDX knowledge library

Audience

Participants who use Industry Data Exchange See Relevant Rules or Procedures (IDX Industry Data Exchange) services.

Participant Impact

Assess if your current integrations will support IDX capabilities and security requirements.

Discuss IDX compatibility with your software or gateway provider, where applicable.

Review the AEMO Gateway update materials if you use AEMO Gateway software.

Background and rationale

AEMO has published the IDX Knowledge Library to provide participants with a central location for IDX learning content and demonstrations based on feedback received through MSUG Market Systems User Group. The knowledge library explains IDX capabilities, integration patterns, security requirements, operational tools, and AEMO Gateway updates.

More details

For more information on IDX Knowledge Library, see IDX Knowledge Library.

AEMO gateway software

Audience

Participants who use AEMO Gateway Software (AGS) to exchange information with AEMO.

Participant impact

Do not perform in-situ upgrades of existing installations until AEMO has completed testing and software certification.

Background and rationale

AEMO has released updated versions of pdrBatcher Software responsible for transferring files to and from AEMO's participant file server to the participant's local Data Interchange folders. It can be installed in any environment supporting Java., pdrMonitor, pdrLoader, and Certificate Helper. The release includes new features, enhancements, and defect fixes for participants using AGS across IDX/Power Quality Data, 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. services, NEM Wholesale EMMS, Gas Bulletin Board (GBB), Declared Wholesale, Declared Wholesale Gas Market (DWGM Declared Wholesale Gas Market. A Victorian gas market that allows trading on injections and withdrawals from the Declared Transmission System (DTS).), Short Term Trading Market (STTM Short Term Trading Market. A wholesale market that facilitates short-term gas trading between gas shippers and users. STTM hubs operate in Adelaide, Brisbane and Sydney.), and Gas Supply Hub Gas Trading Exchange (GSH Gas Supply Hub. An exchange for the wholesale trading of natural gas.).

More details

For more details on AEMO Gateway Software, see Industry Data Exchange – AEMO Gateway Software – August 2026.

Release notes

Data Interchange processes

Data interchange improvements and implementation instructions for pdrBatcher, pdrLoader and pdrMonitor are available in the Technical Specification Portal.

Key actions for participants

Participants performing in-situ upgrades of existing installations must upgrade pdrBatcher and pdrLoader to their latest versions before upgrading pdrMonitor to its latest version. Following this order ensures component compatibility during the upgrade process.

IDX/Power Quality Data

The following change notes are incremental upgrades to the existing AEMO Gateway Software v8.0.1 release.

Participants note the following enhancements for this release:

  • Updates to log messages and configuration descriptions to correct grammar and clarity.

  • Removes properties file documentation for unused oauth_{name}_request_scope configuration property.

  • Adds threadId as an eventing variable and included it in the MessageContextId definition to reduce the risk of message collisions and IDX 409 response errors.

  • Hides the WebSockets checkbox on the packs selection page to prevent accidental selection, as this functionality is not yet available.

Participants note the following new features for this release:

  • Adds a new pdrEncryptionKeyCycle.bat command line script. This script cycles the encryption key and updates all encrypted parameters in the properties configuration file with the updated key.

  • Adds a new API to report any messages stored in the Error folder, allowing them to be surfaced in pdrMonitor.

  • Add support for IAM role for AWS S3 access.

Participants note the following resolved defects for this release:

  • Corrects shell escaping of special characters (& < > = , ; ^) in the pdrPasswordEncrypt script.

  • Aligns the interpretation of IDX 404 response codes to detect messages that have already been consumed. This issue arises from a change to the core IDX platform response format when AEMO GW is configured with multiple parallel processing threads. AEMO GW now correctly interprets these response codes and surfaces only genuine 404 errors in the application log.

  • Ensures any IDX 429 response code (Too Many requests) causes the application to exit the current polling cycle and the thread to sleep for the Fail Wait interval period.

  • Corrects a defect that can cause filename contention when writing Performance files to the Performance folder. This issue occurs only under high throughput conditions with multiple threads, enabled API web services, and no Monitor consuming performance data.

  • Corrects a defect so the flow-control state appears immediately in Monitor at startup. This issue has no functional impact on transaction flow control in the batcher.

  • Corrects a defect, so the Windows service is also uninstalled when AEMO GW is removed using the uninstaller.

  • Corrects a defect in IDX GUI installer where previously selected business functions, such as the Windows Service, appear on the Options packs screen.

  • Adds a RENAME translator to the IDX configuration, so Monitor reports the correct filename. This change applies only when Monitor is installed and connected.

  • Prevents sensitive information associated with API requests and responses from appearing in DEBUG mode. Sensitive information may still appear in TRACE mode, as described in the pdr Participant Data Replication_log4j A Java logging facility, enabling logging at run time without modifying the application binary..xml log configuration file.

  • Enhances the pdrBatcherTransformTest script to escape special parameters passed as arguments that may be required as part of a transform definition, e.g. ‘|’.

Participants using the GUI installer for an in-situ upgrade should note that the upgrade applies standard configuration settings only. It is recommended if you use custom configurations to install the new version in a separate directory. Run the new and legacy versions side by side, so you review and reapply your custom settings. Once the new installation is operating as expected, you can remove the legacy version. Rollback is to stop the new service and restart the previous service.

The following resources are available to participants:

Participants who need assistance to configure and install AEMO Gateway Software can refer to:

NEMWeb

Audience

Participants using NEMWeb.

Participant impact

Report Management Framework Phase 2

Update any automations, scripts or integrations that reference discontinued NEMWeb report URLs. Reports will be moved to a legacy subfolder on NEMWeb, and existing automations using the old URLs will stop working. A six-month legacy access period will apply. Date to be confirmed.

Report Management Framework Phase 3

Complete migration to replacement reports before the end of the six-month legacy access period. AEMO will then permanently remove discontinued reports from NEMWeb.

More details

For more details, see EMMS - NEMWeb - December 2026.

aseXML Schemas

Audience

Business As defined in the NERL. analysts and IT staff in participant organisations.

Participant impact

Migrate from B2B aseXML schema Specification to describe the structure of an aseXML message. version r46 to B2B aseXML A standard for energy transactions in XML. A set of schemas and usage guidelines that define how data should be exchanged under FRC in the gas and electricity industries in Australia. schema version r48. For help transitioning, see Transition of aseXML.

Ensure participant systems using B2M aseXML schema r47 can receive and process the incoming IsPCP and PremisesNMI SSP Secondary Settlement Point. A metering point allowing energy flows within a customer's premises to be measured and settled separately without requiring a second physical connection to the distribution network attributes.

Background and rationale

FTA Release 2 introduces Premises Connection Point (PCP Premises Connection Point) and Secondary Settlement Point (SSP) concepts to support Flexible Trader See Relevant Rules or Procedures Model 2 (FTM2). To support these changes, updates have been made to:

  • B2B aseXML schema r48, which introduces the transaction and messaging changes required for Flexible Trading Arrangements business processes.

  • B2M aseXML schema r47, which introduces new standing data fields to support PCP and SSP relationships.

Dates

FTA Release 2: 25 October 2026

More details

For more information on implementation details, see Schema changes and release dates.