MSUG Action Items

Sparse data filter configuration example

Participants requested an example of the sparse data filter configuration.

Insert and Delete feature in pdrloader

A query was raised about the implementation of the insert and delete feature in 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.. The feature has been implemented but is yet to be trialed. A participant has offered to engage in beta testing.

FPP Design - Participants noted a LastChanged field would be beneficial in Data Model for data management and handling retrospective changes made by AEMO

The designs will be reviewed and changes will be made if necessary.

Include the FCAS requirement in the 7-day pre-dispatch data.

The action item has been reopened and the request is currently pending a business decision.

Update from the Electricity Market Monitoring team:

Updating the 7DAYPD report is dependent on an internal dispatch Energy Rules Terms uplift project running until the end of December 2026 and confirmation AEMO Australian Energy Market Operator can again publish Energy Rules Terms the full 7 days. Once we have this confirmation we can look at updating the report.

A DUDETAILSUMMARY table refresh results in duplicate records

For details about the issue and a workaround, see DUDETAILSUMMARY table refresh issue resulting in duplicate records

Some participants mentioned they are still seeing duplicates in the table. Investigation is under way.

Publishing sub-regional data

We are seeking participant feedback to include sub-regional data in the data model and evaluate the feasibility of publishing this data in future releases.

The new tables will be introduced in the next data model update (v5.6), expected in November 2025. Until then, the sub-regional data can be found in Nemweb and the Data Interchange as non-data model reports.

Modification of sub-regional actual rooftop PV data in the ROOFTOP_PV_ACTUAL report

We are seeking participant feedback about a proposal to stop publishing the sub-regional actual rooftop PV data as you can identify it where the REGIONID field is equal to the following: QLDC, QLDN, QLDS, TASN, TASS.

We will present this proposed change in the next MSUG 2 April 2025, where participants can provide feedback.

The proposed change was presented to participants in the December 2024 Intermittent Generator Forum.

Proposed changes presented at MSUG 2 April 2025.

Data Model - Noting changes to Settlement data tables impacted by IESS

Awaiting confirmation before finalising the update

The Data Model 5.5 release will include changes to settlement data tables impacted by the FPP rule change. From 8 June 2025 onwards, settlements will be performed on the new dispatch FCAS requirements tables, and the old FCAS tables will no longer be maintained. Participants must transition to using the new FCAS requirement tables by this date.

See 3 Participant Impact

Data Model - Amend primary key on Demand operational forecast table

If there is broad support for the change from participants, AEMO will consider implementing the change

We will not change the primary key definition at this time. However, participants are encourage to modify the primary key themselves by adding a column, such as LOAD_DATE, to retain historical forecast data.

Distribution loss factor data is only available in the DUDETAILSUMMARY table. Can AEMO provide the source for this data so participants are not dependent on this table?

If participants are interested and see the value, provide Feedback by 13 November 2024 so we can consider it as a future service

The WA market data has become a lot more complex with the new reformed WEM market starting last October.

Explore the possibility of fetching and loading WEM data into a data model similar to EMMS.

Obtain feedback from other participants and AEMO to investigate and publish a concept paper on how this could work.

If participants are interested and see the value, provide Feedback by 13 November 2024 so we can consider it as a future service

Positive: 4

Negative: 0

AEMO has begun internal discussion with the WA Market Solutions team around the proposal. Depending on this discussion and presenting the same proposal in the WA Market Forum, and wider interest from all relevant stakeholders, AEMO can make a determination on this item.

For dispatchable or available generation in Dispatch Regions, can we assume all fields referring to different aggregate quantities for Generation or Load include the BDU components?

Can we get this information documented in technical specifications or Data Model documentation?

If participants are interested and see the value, provide Feedback by 13 November 2024 so we can consider it as a future service

AEMO has an action to determine the right level of clarity on the data model and that is reflected in updated comments.

Is AEMO planning to update the comments in the PASA tables?

If participants are interested and see the value, provide Feedback by 13 November 2024 so we can consider it as a future service

Participants must provide specific feedback about what kind of information they are looking for.

Does AEMO have a plan to fill in some of the gaps with registration data, for example, the DUALLOC?

If participants are interested and see the value, provide Feedback by 13 November 2024 so we can consider it as a future service

AEMO publishes data through a centrally maintained Data Model for the NEM, GBB, and DWGM, Is there an intention to do the same for the WEM?

Currently, we have no formal plans, but if participants are interested and see the value, provide Feedback by 13 November 2024 so we can consider it as a future service

Awaiting participant responses.

Is AEMO providing a script to back populate the Sparse Data Model with historical Bid Offer Period data?

Currently, we are not planning that but there are 2 approaches we can consider:

• One approach is to set the PERIODITTO field equal to the PERIODID field for all the historical data ensuring participants have a consistent representation, although this is inefficient storage

• A more comprehensive approach is to collapse the historic data into a sparse model, to realise the storage benefits

Please provide Feedback by 13 November 2024

Positive: 3

Negative: 0