3 Participant Impact
Participants wanting to receive the new and updated 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. information in their 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. environments must upgrade to the latest version of the Data Model 5.5.
3.1 Electricity data model v5.5
Participants wanting to receive the new Reports must upgrade to EMMS Data Model v5.5 .
3.2 Data population dates
3.2.1 ST PASA Procedure and Recall Period
Pre-production AEMO’s test system available to participants: Wednesday 21 May 2025
Production AEMO’s live system: Thursday 31 July 2025
Please note that 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 changes to add bid Recall Period The advance notice (in hours) that a scheduled resource will require to achieve the PASA Availability MW for this trading interval. are implemented on 1 July 2025. However, the change to the PDPASA and STPASA reports and the new PDPASA_AVAILABILITY and STPASA_AVAILABILITY reports will be implemented on 31 July 2025. We will notify participants before 1 July 2025 that any bids submitted without the Recall Period The 288 periods from 4:30 am to 4:00 am. attribute will default to 24000.
3.2.2 ERI
Pre-production: Wednesday 21 May 2025
Production: Tuesday 1 July 2025
3.2.3 FPP Settlements
Pre-production: 2 February 2025
Production: 8 June 2025
File Interface Changes
Please note the new files in File interface changes, SETTLEMENTS_INIT and BILLING_INITIAL.
The INITIAL files capture a snapshot of participants’ current outstanding amounts for Settlements See Relevant Rules or Procedures and Billing. Participants use these files to view their Current The participant can receive files compliant to the current aseXML version. Outstanding, displayed in the Prudential Dashboard. The system populates these files at midnight.
The SETTLEMENTS_INIT and BILLING_INITIAL files follow the same table structure as SETTLEMENTS and BILLING files. These files are optional and will not be auto subscribed. Participants who wish to receive these files must manually subscribe.
FCAS Requirement Table Changes
Please note updates in Discontinued Reports.
The FCAS Frequency Controlled Ancillary Services. A service that balances, over short intervals (shorter than the dispatch interval), the power supplied by generating units and the power consumed by loads. requirement tables have changed in preparation for the FPP Frequency Performance Payments rule change commencing 8th June 2025 in production. Participants must move usage of FCAS requirement data from the old FCAS requirement tables to the new FCAS requirement tables published as part of Data Model v5.4. This was made available in production on 9 December 2024.
|
Old Table Name |
Old File ID |
New Table Names |
New File ID |
|---|---|---|---|
|
DISPATCH_FCAS_REQ |
DISPATCHIS_FCAS |
DISPATCH_FCAS_REQ_RUN DISPATCH_FCAS_REQ_CONSTRAINT |
DISPATCHFCST |
|
PREDISPATCH_FCAS_REQ |
PREDISPATCHIS_FCAS |
PD_FCAS_REQ_RUN PD_FCAS_REQ_CONSTRAINT |
PREDISPATCHFCST |
|
P5MIN_FCAS_REQUIREMENT |
P5MIN_FCAS_REQUIREMENT |
P5MIN_FCAS_REQ_RUN P5MIN_FCAS_REQ_CONSTRAINT |
P5MINFCST |
In the Data Model v5.5 release, Settlements will be performed on the new dispatch Energy Rules Terms FCAS requirement tables. We will no longer maintain the old FCAS tables after 28 March 2025 in pre-production and 8 June 2025 in production.
3.3 Data subscription
3.3.1 Auto-subscription
Existing participants are auto-subscribed to any new files when they upgrade to the latest data model version. New file names to be advised.
3.3.2 Legacy files
On the Release Dates, AEMO Australian Energy Market Operator moves participants subscribed to existing files to the Legacy version. After you have upgraded to v5.5, subscribe to the current files in Data Subscription. For help, see Subscribe to Files.
3.4 Data Model Manager
Data Model v5.5 introduces a new feature embedding 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. mapping configuration as a resource within the Data Model package file. You require Data Model Manager v1.2 to apply this update, as earlier versions do not support this capability.
This enhancement allows the Data Model Manager to apply the configuration directly to the PDR_* tables as part of the upgrade process. It ensures environments not permanently connected to an AEMO system still receive the necessary updates, preventing missing configurations.
You must apply the pdrLoader mapping configuration manually using existing methodologies, if the PDR_* tables are not present or if your system is not connected to AEMO market systems.
Based on the pdrLoader mapping:
- If the configuration is already loaded, the Data Model Manager skips this step.
- If the configuration is partially loaded, the Data Model Manager fills in any missing data.