List of packages

Name

Code

Use Parent Namespace

CONFIGURATION

CONFIGURATION

X

ANCILLARY_SERVICES

ANCILLARY_SERVICES

X

ASOFFER

ASOFFER

X

BIDS

BIDS

X

BILLING_CONFIG

BILLING_CONFIG

X

BILLING_RUN

BILLING_RUN

X

DEMAND_FORECASTS

DEMAND_FORECASTS

X

DISPATCH

DISPATCH

X

FORCE_MAJEURE

FORCE_MAJEURE

X

GD_INSTRUCT

GD_INSTRUCT

X

GENERIC_CONSTRAINT

GENERIC_CONSTRAINT

X

IRAUCTION

IRAUCTION

X

MARKET_CONFIG

MARKET_CONFIG

X

MARKET_NOTICE

MARKET_NOTICE

X

METER_DATA

METER_DATA

X

MTPASA

MTPASA

X

P5MIN

P5MIN

X

PARTICIPANT_REGISTRATION

PARTICIPANT_REGISTRATION

X

PRE_DISPATCH

PRE_DISPATCH

X

RESERVE_DATA

RESERVE_DATA

X

SETTLEMENT_CONFIG

SETTLEMENT_CONFIG

X

SETTLEMENT_DATA

SETTLEMENT_DATA

X

STPASA_SOLUTION

STPASA_SOLUTION

X

TRADING_DATA

TRADING_DATA

X

HISTORICAL TABLES

HISTORICAL_TABLES

X

PDPASA

PDPASA

X

PRUDENTIALS

PRUDENTIALS

X

MCC_DISPATCH

MCC_DISPATCH

X

NETWORK

NETWORK

X

VOLTAGE_INSTRUCTIONS

VOLTAGE_INSTRUCTIONS

X


Description of the model MMS Data Model v5.1 Oracle

Background

The MMS Data Model is the definition of the interface to participants of data published by AEMO from the NEM system. A database conforming to the MMS Data Model can contain a local copy of all current participant-specific data recorded in the main NEM production database. The target databases have been called such names as the Participant Database, the Participant InfoServer and the Replica Database.

The MMS Data Model includes database tables, indexes and primary keys. The model is currently exposed as a physical model, so is different in presentation for each RDBMS. However, the same logical model underlies all the physical models published by AEMO.

The MMS Data Model is the target model for products transferring data from AEMO to each participant. Current product supplied by AEMO for data transfer is Participant Data Replication (PDR), with some support for the superseded Parser.

Compatibility of the transfer products with the MMS Data Model is the responsibility of those products and their configuration. AEMO’s intention is to supply the data transfer products pre-configured to deliver data consistent with the MMS Data Model, noting differences where they occur (e.g. for historical reasons).

Entity Diagrams

The entity diagrams show the key columns. Relationships have now been included in many cases.

Note:

The National Electricity Market registration classification of Yarwun Power Station Unit 1 (dispatchable unit ID: YARWUN_1) is market non-scheduled generating unit. However, it is a condition of the registration of this unit that the Registered Participant complies with some of the obligations of a Scheduled Generator. This unit is dispatched as a scheduled generating unit with respect to its dispatch offers, targets and generation outputs. Accordingly, information about YARWUN_1 is reported as scheduled generating unit information.


Notes

Each table description has a Note providing some information relevant to the table.


Visibility

Visibility refers to the nature of confidentiality of data in the table. Each table has one of the following entries, each described here.


Private: meaning the data is confidential to the Participant (e.g. BILLINGFEES).

Public: meaning all Participants have access to the data (e.g. DISPATCHPRICE).

Private, Public Next-Day: meaning the data is confidential until available for public release at beginning of next day (i.e. 4am) (e.g. BIDDAYOFFER).

Private & Public: meaning some items are private and some are public (e.g. MARKETNOTICES).