Last modified: 11 April 2024
Sparse model FAQs
To ensure data volumes remain within acceptable limits, AEMO is moving to a sparse representation for Energy and FCAS Bids and Offers. This is necessary to allow us to continue meeting our Market data reporting obligations. An analysis of data by AEMO identified adopting a sparse data model, where repeated data is suppressed, can potentially result in a 95% reduction in data volumes in these reports. For details about the Sparse Model, see EMMS - Technical Specification - Data Model v5.2 - May 2023.

Public next day data.

Yes, FCAS and Energy next day only with opt-in for the sparse model for the existing data model tables. The full table data will remain the default report subscription. The sparse model is not mandatory, you can still receive the fully qualified next-day offers as the standard set of subscriptions, but we would potentially be looking to make the sparse data model the standard in a future data model release so encourage participants to begin this transition now. We're introducing the sparse model in this release for participants having specific pain points who are ready to opt-in now. AEMO would like to discuss if it makes sense to the industry to begin a transition pathway where the sparse data models become the standard way we deliver data because we understand it affects the reporting and analytics in participants' systems. If we do want to move to the sparse model as the standard delivery of next-day data, we can do that in a future release, possibly June 2024, discontinuing the fully qualified next-day reports.
We can also discuss extending the sparse model with opt-in to:
- The confidential reports.
- Energy and FCAS bid/offer submissions.

Yes, we're not removing the current next day offer reports. We are providing a new next day Energy and FCAS report version with a sparse data representation. Participants can opt into the sparse representation NEXT_DAY_OFFER report when they have modified their reporting/analytic systems to have a capability to interpret a sparse offer representation.

On the assumption that we will begin a migration to adopting a sparse data representation as the standard at a future date, our intention would be to denote the existing NEXT_DAY_OFFER reports as LEGACY and introduce new versions of these reports that have a sparse data representation. There would be no difference between these reports in terms of the reported columns. Participants would opt into the report which aligns with the capabilities of their analytic tools.

Yes, we guarantee it can be in period order.

It’s not a step we will take initially but we are considering it for the future because it might decrease the impact on participants’ systems. If AEMO were to implement this feature it would have no impact on participants who choose to continue to submit a fully qualified offer because the logic to interpret a sparse offer submission is compatible with a fully qualified offer.

The sparse concept applies equally to both the data in transit and the footprint within the local participant database. AEMO analysis indicates that moving to the sparse representation could reduce the amount of NEXT_DAY_OFFER data by up to 95%.

The PDR Loader loads the data participants are subscribed to. If a participant has opted into the sparse NEXT_DAY_OFFER report, that is what is loaded into the participant's database. The PDR Loader does not have a capability to expand a sparse offer representation to a fully qualified offer.

The PDR Loader loads the data participants are subscribed to. If a participant has opted into the sparse NEXT_DAY_OFFER report, that is what is loaded into the participant's database. The PDR Loader does not have a capability to expand a sparse offer representation to a fully qualified offer.

We are not proposing it but participants can do it themselves to reduce the size of their local data store if desired. The reason we are not proposing it is because the logic to interpret a sparse bid works equally well against a fully qualified bid. There is therefore no real requirement to have a logic cut over at a point in time when opting into the sparse offer data. For example, if you're looking at period 2 and it doesn't exist, then you would roll forward period 1 to emulate period 2. If period 2 does exist either because it is different from period 1 (sparse) or its fully qualified offer, then you would use the period 2 data already existing.

Participant suggestion: We can add that column to the database so the loader can automatically populate and verify by the start and end dates that we have 288 records for a bid.
AEMO think this suggestion has merit and have taken it on notice for consideration.

AEMO are conscious of the significant change for participants and are considering options.

AEMO are conscious of the significant change for participants and are considering options.