|
Name |
|
|
Comment |
MR_EVENT_SCHEDULE defines the Stack version of the Acceptance Schedule and is the parent table to MR_DayOffer_Stack and MR_PerOffer_Stack. |
|
Once the offer cut off time has passed and as the schedule changes AEMO is obliged to accept MR capacity to meet the schedule in merit order according to the offers submitted. The relationship to a specific schedule, the merit order of submitted offers and accepted quantities for each trading interval are stored in the MR_Event_Schedule, MR_DayOffer_Stack and MR_PerOffer_Stack table. The MR_EVENT_SCHEDULE table determines the existence of an MR offer acceptance stack for a specific MR schedule of an MR event. The MR_EVENT_SCHEDULE table also tracks the time each stack is exercised. MR_EVENT_SCHEDULE is public and notifies the market that a new offer stack has been created. Source MR_EVENT_SCHEDULE updates are ad hoc. Volume 2 Rows per year |
|
Name |
Comment |
Value |
|
Visibility |
Data in this table is: |
Public |
|
Name |
|
MR_DATE |
|
REGIONID |
|
VERSION_DATETIME |
|
Name |
|
LASTCHANGED |
|
Name |
Data Type |
Mandatory |
Comment |
|
MR_DATE |
DATE |
X |
Mandatory Restriction imposition date |
|
REGIONID |
VARCHAR2(10) |
X |
Unique RegionID |
|
VERSION_DATETIME |
DATE |
X |
Effective Date/Time of Schedule; Allows many Stack versions |
|
DEMAND_EFFECTIVEDATE |
DATE |
|
Foreign key reference to ResDemandTrk.EffectiveDate |
|
DEMAND_OFFERDATE |
DATE |
|
Foreign key reference to ResDemandTrk.OfferDate |
|
DEMAND_VERSIONNO |
NUMBER(3,0) |
|
Foreign key reference to ResDemandTrk.VersionNo |
|
AUTHORISEDBY |
VARCHAR2(20) |
|
Authorised person confirming Offer Stack (AKA Acceptance) |
|
AUTHORISEDDATE |
DATE |
|
Date and time the Offer Stack confirmed |
|
LASTCHANGED |
DATE |
|
Date and time the record was inserted/modified |
|
|
|