4 Electricity Data Model v5.5
This Release contains an updated version of the Electricity Data Model The Electricity Data Model is the definition of the interface to participants of data published by AEMO from National Electricity Market (NEM) systems. 5.5. This section describes the affected packages, tables, files, reports, and interfaces.
4.1 Data model changes summary
4.2 Package: SETTLEMENT_DATA
Results from a published Settlements See Relevant Rules or Procedures Run. The settlement data and billing run data are updated daily Energy Rules Terms between 6 am and 8 am for AEMO Australian Energy Market Operator's prudential processes. In a normal week, AEMO publishes one PRELIM, one FINAL and two REVISION runs in addition to the daily runs
4.2.1 Modified table: DAYTRACK
Comment |
DAYTRACK identifies the actual settlement run processed for each settlement day. Settlement run is in the column EXPOSTRUNNO. Generally the number of the settlement run used in the latest statement is the maximum number. |
---|---|
Visibility |
Public |
Data volume |
Low |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, EXPOSTRUNNO |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
METER_CASEID |
NUMBER(5,0) |
No |
The Metering Case Id used for the Settlement Run. For Estimate Daily Run this will be 0 |
METER_RUNTYPE |
VARCHAR2(10) |
No |
The Type of Settlement Run (ESTIMATE/PRELIM/FINAL/REVISE) |
4.2.2 New table: SET_FCAS_CLAWBACK_RUN_TRK
Comment |
This Settlements FCAS Clawback Run Track report contains the Interval Datetime for which a Clawback has occurred and included in the Settlement run. The report will be produced only if there is any Clawback Run for the Interval date time in the Settlement Date |
---|---|
Visibility |
Public |
Data volume |
Low |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, VERSIONNO, INTERVAL_DATETIME |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
SETTLEMENTDATE |
DATE |
Yes |
The Settlement Date of the Billing Week |
VERSIONNO |
NUMBER(3,0) |
Yes |
The Settlement Run No |
INTERVAL_DATETIME |
DATE |
Yes |
The Interval Datetime for which a Clawback Run has been completed. |
RUNNO |
NUMBER(3,0) |
No |
The RunNo associated with the Clawback for the above interval date time. |
CLAWBACK_DATE |
DATE |
No |
The Date time the Clawback data has been loaded into the System for processing. |
PREV_DATA_SOURCE |
VARCHAR2(20) |
No |
The Clawback Data source Used. If this interval has any Clawback already applied in past then value will be CLAWBACK , else DISPATCH. For the first Clawback processing for the Interval the Source is DISPATCH. |
LASTCHANGED |
DATE |
No |
The Last changed Date time of the record |
4.2.3 New table: SET_FCAS_CLAWBACK_UNITSOLN
Comment |
This report contains the Interval Datetime affected by the Clawback Run and the reduced MW for the FCAS Service for each affected DUID. |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, RUNNO, DUID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
INTERVAL_DATETIME |
DATE |
Yes |
The Interval Datetime for which a the Clawback Run has been completed. |
RUNNO |
NUMBER(3,0) |
Yes |
The RunNo associated with the Clawback Run for the above interval date time. |
DUID |
VARCHAR2(20) |
Yes |
The DUID for which the Reduced MW has been applied for the FCAS Service. |
LOWER1SEC |
NUMBER(18,8) |
No |
The Clawback Volume for the LOWER1SEC Service. If this service is not affected in that Clawback then retain Prev Value. |
LOWER5MIN |
NUMBER(18,8) |
No |
The Clawback Volume for the LOWER5MIN Service. If this service is not affected in that Clawback then retain Prev Value. |
LOWER60SEC |
NUMBER(18,8) |
No |
The Clawback Volume for the LOWER60SEC Service. If this service is not affected in that Clawback then retain Prev Value. |
LOWER6SEC |
NUMBER(18,8) |
No |
The Clawback Volume for the LOWER6SEC Service. If this service is not affected in that Clawback then retain Prev Value. |
RAISE1SEC |
NUMBER(18,8) |
No |
The Clawback Volume for the RAISE1SEC Service. If this service is not affected in that Clawback then retain Prev Value. |
RAISE5MIN |
NUMBER(18,8) |
No |
The Clawback Volume for the RAISE5MIN Service. If this service is not affected in that Clawback then retain Prev Value. |
RAISE60SEC |
NUMBER(18,8) |
No |
The Clawback Volume for the RAISE60SEC Service. If this service is not affected in that Clawback then retain Prev Value. |
RAISE6SEC |
NUMBER(18,8) |
No |
The Clawback Volume for the RAISE6SEC Service. If this service is not affected in that Clawback then retain Prev Value. |
LOWERREG |
NUMBER(18,8) |
No |
The Clawback Volume for the LOWERREG Service. If this service is not affected in that Clawback then retain Prev Value. |
RAISEREG |
NUMBER(18,8) |
No |
The Clawback Volume for the RAISEREG Service. If this service is not affected in that Clawback then retain Prev Value. |
LASTCHANGED |
DATE |
No |
The Last Changed Date time of the record. |
4.2.4 New table: SET_FCAS_CLAWBACK_REQ
Comment |
This report contains the Interval Datetime affected by the Clawback Run and the adjusted FCAS requirement Costs. |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, RUNNO, CONSTRAINTID, REGIONID, BIDTYPE |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
INTERVAL_DATETIME |
DATE |
Yes |
The Interval Datetime for which a the Clawback Run has been completed. |
RUNNO |
NUMBER(3,0) |
Yes |
The RunNo associated with the Clawback Run for the above interval date time. |
CONSTRAINTID |
VARCHAR2(20) |
Yes |
The FCAS Constraint ID used in the FCAS Requirements. |
REGIONID |
VARCHAR2(20) |
Yes |
The Region ID associated with each Constraint Requirements |
BIDTYPE |
VARCHAR2(10) |
Yes |
The FCAS Service - DUID offered type |
REGION_ENABLEMENT |
NUMBER(18,8) |
No |
The Overridden Regional Enablement. SUM (FCAS MW) from FCAS.Clawback_Unitsolution |
CONSTRAINT_ENABLEMENT |
NUMBER(18,8) |
No |
How much is enabled for this bid Type within the constraint. Sum(Regional_Enablement) |
REGION_BASE_COST |
NUMBER(18,8) |
No |
The Region Base Cost adjusted by the Regional Enablement Adj Ratio |
BASE_COST |
NUMBER(18,8) |
No |
The Base cost of the constraint before the regulation/contingency split. SUM(REGION_BASE_COST) |
ADJUSTED_COST |
NUMBER(18,8) |
No |
The adjusted cost of the constraint for this service, after the regulation/contingency split. This is adjusted by the Base Cost Adjustment Ratio. |
P_REGULATION |
NUMBER(18,8) |
No |
P Regulation value is not affected by Clawback. This value is copied from Original Data source (DISPATCH ) |
PREV_REGION_ENABLEMENT |
NUMBER(18,8) |
No |
The Regional Enablement before Override |
PREV_CONSTRAINT_ENABLEMENT |
NUMBER(18,8) |
No |
The Constraint Enablement before Override |
PREV_REGION_BASE_COST |
NUMBER(18,8) |
No |
The Region Base Cost before Override |
PREV_BASE_COST |
NUMBER(18,8) |
No |
The Base Cost before Override |
PREV_ADJUSTED_COST |
NUMBER(18,8) |
No |
The Adjusted Cost before override |
LASTCHANGED |
DATE |
No |
The Last Changed Date time of the record. |
4.2.5 New table: SET_FCAS_REG_AMOUNT
Comment |
This report contains the FCAS Regulation Amounts that include FPP Amounts, Used Amounts and Unused Amounts calculated using the Contribution Factors |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, VERSIONNO,UNITID,CONSTRAINTID,PERIODID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
SETTLEMENTDATE |
DATE |
Yes |
The Settlement Date of the Billing Week |
VERSIONNO |
NUMBER(3,0) |
Yes |
The Settlement Run No |
UNITID |
VARCHAR2(10) |
Yes |
The UNITID with CF factor assigned. This is a DUID or a TNI. Refer table FPP_CONTRIBUTION_FACTOR |
CONSTRAINTID |
VARCHAR2(20) |
Yes |
The FCAS Regulation Constraint ID |
PERIODID |
NUMBER(3,0) |
Yes |
The Period ID Identifier |
PARTICIPANTID |
VARCHAR2(20) |
No |
The Participant Id Identifier |
BIDTYPE |
VARCHAR2(10) |
No |
The BidType LOWERREG or RAISEREG for the Constraint ID |
FPP_AMOUNT |
NUMBER(18,8) |
No |
The FPP Amount calculated for the Constraint and UNITID using the FPP Contribution Factor |
USED_AMOUNT |
NUMBER(18,8) |
No |
The Regulation Used Recovery Amount from the eligible Units using Negative CF Value |
UNUSED_AMOUNT |
NUMBER(18,8) |
No |
The Regulation Unused Recovery Amount from Eligible Units using DCF Value |
LASTCHANGED |
DATE |
No |
The Last Changed Date time of the record. |
4.2.6 New table: SET_FCAS_REG_RESIDAMT
Comment |
This report contains the FCAS Regulation Residue Amounts that include FPP Residual Amounts, Used Residual Amounts and Unused Residual Amounts calculated using the Energy Ratio for each Requirement Region |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, VERSIONNO,PARTICIPANTID,CONSTRAINTID,PERIODID, REGIONID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
SETTLEMENTDATE |
DATE |
Yes |
The Settlement Date of the Billing Week |
VERSIONNO |
NUMBER(3,0) |
Yes |
The Settlement Run No |
PARTICIPANTID |
VARCHAR2(20) |
Yes |
The Participant Id Identifier |
CONSTRAINTID |
VARCHAR2(20) |
Yes |
The FCAS Regulation Constraint ID |
PERIODID |
NUMBER(3,0) |
Yes |
The Period ID Identifier |
REGIONID |
VARCHAR2(20) |
Yes |
The RegionId used for the residual calculation. This is the Constraint Requirement Region. |
BIDTYPE |
VARCHAR2(10) |
No |
The BidType LOWERREG or RAISEREG for the Constraint ID |
ACE_MWH |
NUMBER(18,8) |
No |
The ACE MWh value that is used for the Residual Calculation.(Excluding CPID with CF) |
ASOE_MWH |
NUMBER(18,8) |
No |
The ASOE MWh value that is used for the Residual Calculation.(Excluding CPID with CF). ASOE MWh is only used for FPP Residual. |
RESIDUAL_MWH |
NUMBER(18,8) |
No |
Sum of ABS(ACE_MWh) + ASOE_MWh. The MWh is not netted for residual calculation. This is only used for FPP Residual |
FPP_ACE_AMOUNT |
NUMBER(18,8) |
No |
The FPP ACE Amount calculated using the portion of ACE MWh value against the Total residual MWh of the requirement regions. |
FPP_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The FPP ASOE Amount calculated using the portion of ASOE MWh value against the Total residual MWh of the requirement regions. |
FPP_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
Sum of FPP_ACE_Amount + FPP_ASOE_Amount |
USED_ACE_AMOUNT |
NUMBER(18,8) |
No |
The Used Recovery ACE Amount calculated using the ACE MWh value of the requirement regions. |
USED_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Used Recovery ASOE Amount is always 0 as FCAS Regulation Residual is calculated using ACE MWh values only. |
USED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The Used Residual Amount is Same as Used_ACE_Amount |
UNUSED_ACE_AMOUNT |
NUMBER(18,8) |
No |
The Unused Recovery ACE Amount calculated using the portion of ACE MWh value against the Total residual MWh of the requirement regions. |
UNUSED_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Unused Recovery ASOE Amount is always 0 as FCAS Regulation Residual is calculated using ACE MWh values only. |
UNUSED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The Unused Residual Amount is Same as Unused_ACE_Amount |
LASTCHANGED |
DATE |
No |
The Last Changed Date time of the record. |
4.2.7 New table: SET_FCAS_REG_DEF_AMT
Comment |
This report contains the FCAS Regulation Amounts that include FPP Amounts, Used Amounts and Unused Amounts calculated using the Default Contribution Factors. This is when FPP Factors are not available for a particular interval and system used DCF in the calculation. |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, VERSIONNO,UNITID,CONSTRAINTID,PERIODID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
SETTLEMENTDATE |
DATE |
Yes |
The Settlement Date of the Billing Week |
VERSIONNO |
NUMBER(3,0) |
Yes |
The Settlement Run No |
UNITID |
VARCHAR2(10) |
Yes |
The UnitId with CF factor assigned. This is a DUID or a TNI. Refer table FPP_CONTRIBUTION_FACTOR |
CONSTRAINTID |
VARCHAR2(20) |
Yes |
The FCAS Regulation Constraint ID |
PERIODID |
NUMBER(3,0) |
Yes |
The Period ID Identifier |
PARTICIPANTID |
VARCHAR2(20) |
No |
The Participant Id Identifier |
BIDTYPE |
VARCHAR2(10) |
No |
The BidType LOWERREG or RAISEREG for the Constraint ID |
UNUSED_AMOUNT |
NUMBER(18,8) |
No |
The Regulation Unused Recovery Amount from Eligible Units using DCF Value |
LASTCHANGED |
DATE |
No |
The Last Changed Date time of the record. |
4.2.8 New table: SET_FCAS_REG_DEF_RESIDAMT
Comment |
This report contains the FCAS Regulation Residue Amounts that include FPP Residual Amounts, Used Residual Amounts and Unused Residual Amounts calculated using the Energy Ratio for each Requirement Region and the Default Residual CF |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, VERSIONNO,PARTICIPANTID,CONSTRAINTID,PERIODID, REGIONID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
SETTLEMENTDATE |
DATE |
Yes |
The Settlement Date of the Billing Week |
VERSIONNO |
NUMBER(3,0) |
Yes |
The Settlement Run No |
PARTICIPANTID |
VARCHAR2(20) |
Yes |
The Participant Id Identifier |
CONSTRAINTID |
VARCHAR2(20) |
Yes |
The FCAS Regulation Constraint ID |
PERIODID |
NUMBER(3,0) |
Yes |
The Period ID Identifier |
REGIONID |
VARCHAR2(20) |
Yes |
The RegionId used for the residual calculation. This is the Constraint Requirement Region. |
BIDTYPE |
VARCHAR2(10) |
No |
The BidType LOWERREG or RAISEREG for the Constraint ID |
ACE_MWH |
NUMBER(18,8) |
No |
The ACE MWh value that is used for the Residual Calculation.(Excluding CPID with CF) |
ASOE_MWH |
NUMBER(18,8) |
No |
The ASOE MWh value that is used for the Residual Calculation.(Excluding CPID with CF) |
RESIDUAL_MWH |
NUMBER(18,8) |
No |
Sum of ABS(ACE_MWh) + ASOE_MWh. The MWh is not netted for residual calculation. This is not used in calculation at the moment. This is only used for FPP Residual |
UNUSED_ACE_AMOUNT |
NUMBER(18,8) |
No |
The Unused Recovery ACE Amount calculated using the ACE MWh value of the requirement regions. |
UNUSED_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Unused Recovery ASOE Amount is always 0 as FCAS Reg Residual is recovered from ACE MWh Only |
UNUSED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The Unused Residual Amount is same as Unused ACE Amount. |
LASTCHANGED |
DATE |
No |
The Last Changed Date time of the record. |
4.2.9 New table: SET_FPP
Comment |
This report contains the summary of FPP Amounts for each ParticipantId in each region |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, VERSIONNO,PARTICIPANTID,REGIONID,PERIODID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
SETTLEMENTDATE |
DATE |
Yes |
The Settlement Date of the Billing Week |
VERSIONNO |
NUMBER(3,0) |
Yes |
The Settlement Run No |
PARTICIPANTID |
VARCHAR2(20) |
Yes |
The Participant Id Identifier |
REGIONID |
VARCHAR2(20) |
Yes |
The RegionId used for the residual calculation. This is the Constraint Requirement Region. |
PERIODID |
NUMBER(3,0) |
Yes |
The Period ID Identifier |
LOWERREG_AMOUNT |
NUMBER(18,8) |
No |
The LowerReg Amount from the Eligible Units. |
LOWERREG_ACE_AMOUNT |
NUMBER(18,8) |
No |
The LowerReg Amount from the ACE Portion of the Residual amount |
LOWERREG_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The LowerReg Amount from the ASOE Portion of the Residual amount |
LOWERREG_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The Lower Reg Residual Amount which is also LowerReg_ACE_Amount + LowerReg_ASOE_Amount |
RAISEREG_AMOUNT |
NUMBER(18,8) |
No |
The RaiseReg Amount from the Eligible Units. |
RAISEREG_ACE_AMOUNT |
NUMBER(18,8) |
No |
The RaiseReg Amount from the ACE Portion of the Residual amount |
RAISEREG_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The RaiseReg Amount from the ASOE Portion of the Residual amount |
RAISEREG_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The Raise Reg Residual Amount which is also RaiseReg_ACE_Amount + RaiseReg_ASOE_Amount |
LASTCHANGED |
DATE |
No |
The Last Changed Date time of the record. |
4.2.10 Modified table: SET_FCAS_REGULATION_TRK
Comment |
This report shows FCAS Regulation Service Constraint tracking for Regional FCAS Regulation recovery |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, VERSIONNO,INTERVAL_DATETIME, CONSTRAINTID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
FPP_AMOUNT |
NUMBER(18,8) |
No |
The total FPP Amount from Eligible Units for the Constraint Id |
FPP_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The total FPP Residual Amount for the Constraint Id |
USED_AMOUNT |
NUMBER(18,8) |
No |
The total Reg Used Amount from Eligible Units for the Constraint Id |
USED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The total Reg Used Residual Amount for the Constraint Id |
UNUSED_AMOUNT |
NUMBER(18,8) |
No |
The total Reg Unused Amount from Eligible Units for the Constraint Id |
UNUSED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The total Reg Unused Residual Amount for the Constraint Id |
P_REGULATION |
NUMBER(18,8) |
No |
The PRegulation Value from Constraints FCAS Requirement data |
TSFCAS |
NUMBER(18,8) |
No |
The Adjusted Cost Value from Constraints FCAS Requirement data |
RCR |
NUMBER(18,8) |
No |
The RCR Value from the FPP Inputs for the Constraint Id used to calculate FPP Amount |
USAGE_VALUE |
NUMBER(18,8) |
No |
The Usage Value from the FPP Inputs for the Constraint Id used to calculate Used Amount |
RCF |
NUMBER(18,8) |
No |
The RCF Value from the FPP Inputs for the Constraint Id used to calculate FPP Residual |
NRCF |
NUMBER(18,8) |
No |
The NRCF Value from the FPP Inputs for the Constraint Id used to calculate Used Residual Amount |
DRCF |
NUMBER(18,8) |
No |
The DRCF Value from the FPP Inputs for the Constraint Id used to calculate Unused Residual Amount |
RESIDUALTOTAL_MWH |
NUMBER(18,8) |
No |
The total residual MWh(ABS(ACE_MWh) + ASOE(MWh)) of the requirement regions. |
Modified columns
Comment Changes Only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
CMPF |
NUMBER(18,8) |
No |
Constraint Market Participant Factor. This column is NULL for Settlement Dates past FPP Rule Effective Date |
CRMPF |
NUMBER(18,8) |
No |
Constraint Residual Market Participant Factor. This column is NULL for Settlement Dates past FPP Rule Effective Date |
RECOVERY_FACTOR_CMPF |
NUMBER(18,8) |
No |
Recovery factor for CMPF based recovery. This column is NULL for Settlement Dates past FPP Rule Effective Date |
RECOVERY_FACTOR_CRMPF |
NUMBER(18,8) |
No |
Recovery factor for CRMPF based recovery. This column is NULL for Settlement Dates past FPP Rule Effective Date. |
4.2.11 Modified table: SET_FCAS_RECOVERY
Comment |
This report shows reimbursements for the Frequency Control Ancillary Services (FCAS) to be recovered from participants |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
SETTLEMENTDATE, VERSIONNO,PARTICIPANTID,REGIONID,PERIODID |
New columns
Field name |
Data type |
Primary key |
Comment |
|
---|---|---|---|---|
LOWERREG_ASOE |
NUMBER(18,8) |
No |
This column is LOWERREG_USED_ASOE + LOWERREG_UNUSED_ASOE. For Settlement dates prior to FPP Rule Effective date this column will be NULL |
|
RAISEREG_ASOE |
NUMBER(18,8) |
No |
This column is RAISEREG_USED_ASOE + RAISEREG_UNUSED_ASOE. For Settlement dates prior to FPP Rule Effective date this column will be NULL |
|
LOWERREG_USED |
NUMBER(18,8) |
No |
The LowerReg Used amount for the Participant and Region |
|
RAISEREG_USED |
NUMBER(18,8) |
No |
The RaiseReg Used amount for the Participant and Region |
|
LOWERREG_UNUSED |
NUMBER(18,8) |
No |
The LowerReg Unused amount for the Participant and Region |
|
RAISEREG_UNUSED |
NUMBER(18,8) |
No |
The RaiseReg Unused amount for the Participant and Region |
|
LOWERREG_USED_ACE |
NUMBER(18,8) |
No |
The LowerReg Used ACE Portion amount for the Participant and Region |
|
LOWERREG_USED_ASOE |
NUMBER(18,8) |
No |
The LowerReg Used ASOE Portion amount for the Participant and Region |
|
LOWERREG_USED_RESIDUAL |
NUMBER(18,8) |
No |
The LowerReg Used Residual amount for the Participant and Region (LowerReg_Used_ACE + LowerReg_Used_ASOE) |
|
RAISEREG_USED_ACE |
NUMBER(18,8) |
No |
The RaiseReg Used ACE Portion amount for the Participant and Region |
|
RAISEREG_USED_ASOE |
NUMBER(18,8) |
No |
The RaiseReg Used ASOE Portion amount for the Participant and Region |
|
RAISEREG_USED_RESIDUAL |
NUMBER(18,8) |
No |
The RaiseReg Used Residual amount for the Participant and Region RaiseReg_Used_ACE + RaiseReg_Used_ASOE |
|
LOWERREG_UNUSED_ACE |
NUMBER(18,8) |
No |
The LowerReg Unused ACE Portion amount for the Participant and Region |
|
LOWERREG_UNUSED_ASOE |
NUMBER(18,8) |
No |
The LowerReg Unused ASOE Portion amount for the Participant and Region |
|
LOWERREG_UNUSED_RESIDUAL |
NUMBER(18,8) |
No |
The LowerReg Unused Residual amount for the Participant and Region LowerReg_Unused_ACE + LowerReg_Unused_ASOE |
|
RAISEREG_UNUSED_ACE |
NUMBER(18,8) |
No |
The RaiseReg Unused ACE Portion amount for the Participant and Region |
|
RAISEREG_UNUSED_ASOE |
NUMBER(18,8) |
No |
The RaiseReg Unused ASOE Portion amount for the Participant and Region |
|
RAISEREG_UNUSED_RESIDUAL |
NUMBER(18,8) |
No |
The RaiseReg Unused Residual amount for the Participant and Region RaiseReg_Unused_ACE + RaiseReg_Unused_ASOE |
Modified columns
Comment Changes Only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
LOWERREG_RECOVERY |
NUMBER(18,8) |
No |
For Settlement Date post the IESS rule effective date the column represent the Lower Regulation FCAS MPF Recovery Amount from Customer and Generator Connection Point MPFs only. Residue Recovery Amount is not included in this amount. For Settlement Dates past FPP Rule Effective Dates this column will be NULL. |
RAISEREG_RECOVERY |
NUMBER(18,8) |
No |
For Settlement Date post the IESS rule effective date the column represent the Raise Regulation FCAS MPF Recovery Amount from Customer and Generator Connection Point MPFs only. Residue Recovery Amount is not included in this amount. For Settlement Dates past FPP Rule Effective Dates this column will be NULL. |
LOWERREG_ACE |
NUMBER(18,8) |
No |
The Lower Regulation FCAS Residue Recovery Amount using ACE MWh values excluding the MPF Connection Points. NULL value for Settlement Dates prior to the IESS rule effective date. For Settlement dates past FPP Rule Effective date this column will be LOWERREG_USED_ACE + LOWERREG_UNUSED_ACE |
RAISEREG_ACE |
NUMBER(18,8) |
No |
The Raise Regulation FCAS Residue Recovery Amount using ACE MWh values excluding the MPF Connection Points. NULL Value for Settlement Dates prior to the IESS rule effective date. For Settlement dates past FPP Rule Effective date this column will be RAISEREG_USED_ACE + RAISEREG_UNUSED_ACE |
4.2.12 Modified table: SET_NMAS_RECOVERY (comment changes heading only)
Comment |
SET_NMAS_RECOVERY sets out the NSCAS recovery data for payments other than testing This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Settlement Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
CONTRACTID |
4.2.13 Modified table: SET_NMAS_RECOVERY_RBF (comment changes heading only)
Comment |
SET_NMAS_RECOVERY_RBF publishes the RBF for NSCAS non testing payments on a half hourly basis. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Public |
Data volume |
|
Trigger |
Settlement Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
CONTRACTID |
4.2.14 Modified table: SETLSHEDPAYMENT (comment changes heading only)
Comment |
SETLSHEDPAYMENT shows specific payment details for load shed services by period. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Settlement Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
CONTRACTID |
4.2.15 Modified table: SETRPOWERPAYMENT (comment changes heading only)
Comment |
SETRPOWERPAYMENT shows specific payment details for Reactive power services by period. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Settlement Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
CONTRACTID |
4.3 Package: BILLING_RUN
Results from a published Billing Run. The settlement data and billing run data are updated daily between 6 am and 8 am for AEMO's prudential processes. In a normal week, AEMO publishes one PRELIM, one FINAL and two REVISION runs in addition to the daily runs.
Each billing run is uniquely identified by contract year, week no and bill run number.
4.3.1 New table: BILLING_FCAS_REG_AMT
Comment |
This report show the summary of the Billing run FCAS Regulation Amounts incl default amounts. |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
CONTRACTYEAR, WEEKNO,BILLRUNNO,PARTICIPANTID,UNITID,CONSTRAINTID, CONNECTIONPOINTID, REGIONID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
CONTRACTYEAR |
NUMBER(4,0) |
Yes |
The Billing Contract Year |
WEEKNO |
NUMBER(3,0) |
Yes |
The Billing WeekNo |
BILLRUNNO |
NUMBER(4,0) |
Yes |
The Billing RunNo |
PARTICIPANTID |
VARCHAR2(20) |
Yes |
The Participant Id Identifier |
UNITID |
VARCHAR2(20) |
Yes |
The UnitId for which a FPP Factor is assigned |
CONSTRAINTID |
VARCHAR2(20) |
Yes |
The FCAS Reg Constraint Id |
CONNECTIONPOINTID |
VARCHAR2(20) |
Yes |
The ConnectionPointId from Settlement Results for the UnitId |
REGIONID |
VARCHAR2(20) |
Yes |
The Region Id Identifier |
BIDTYPE |
VARCHAR2(10) |
No |
The BidType for the Constraint Id |
FPP_AMOUNT |
NUMBER(18,8) |
No |
The FPP Amount for the Participant and the Unit |
USED_AMOUNT |
NUMBER(18,8) |
No |
The FCAS Regulation Used Amount for the Participant and the Unit |
UNUSED_AMOUNT |
NUMBER(18,8) |
No |
The FCAS Regulation Unused Amount for the Participant and the Unit |
LASTCHANGED |
DATE |
No |
The Lastchanged datetime of the record. |
4.3.2 New table: BILLING_FCAS_REG_RESIDAMT
Comment |
This report show the summary of the Billing run FCAS Regulation Residual Amounts incl default amounts |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
CONTRACTYEAR, WEEKNO,BILLRUNNO,PARTICIPANTID,CONSTRAINTID,REGIONID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
CONTRACTYEAR |
NUMBER(4,0) |
Yes |
The Billing Contract Year |
WEEKNO |
NUMBER(3,0) |
Yes |
The Billing WeekNo |
BILLRUNNO |
NUMBER(4,0) |
Yes |
The Billing RunNo |
PARTICIPANTID |
VARCHAR2(20) |
Yes |
The Participant Id Identifier |
CONSTRAINTID |
VARCHAR2(20) |
Yes |
The FCAS Reg Constraint Id |
REGIONID |
VARCHAR2(20) |
Yes |
The Region Id Identifier |
BIDTYPE |
VARCHAR2(10) |
No |
The BidType for the Constraint Id |
ACE_MWH |
NUMBER(18,8) |
No |
The ACE MWh used for the Residual Calculation for the Participant |
ASOE_MWH |
NUMBER(18,8) |
No |
The ASOE MWh used for the Residual Calculation of the Participant |
RESIDUAL_MWH |
NUMBER(18,8) |
No |
Sum of ACE_MWH + ASOE_MWH |
FPP_ACE_AMOUNT |
NUMBER(18,8) |
No |
The FPP ACE Portion Amount for the Billing Week |
FPP_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The FPP ASOE Portion Amount for the Billing Week |
FPP_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The FPP Residual Amount for the Billing Week |
USED_ACE_AMOUNT |
NUMBER(18,8) |
No |
The Used ACE Portion Amount for the Billing Week |
USED_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Used ASOE Portion Amount for the Billing Week |
USED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The Used Residual Amount for the Billing Week |
UNUSED_ACE_AMOUNT |
NUMBER(18,8) |
No |
The Unused ACE Portion Amount for the Billing Week |
UNUSED_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Unused ASOE Portion Amount for the Billing Week |
UNUSED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
The Unused Residual Amount for the Billing Week |
LASTCHANGED |
DATE |
No |
The Lastchanged datetime of the record. |
4.3.3 New table: BILLING_FPP
Comment |
This report show the summary of the Billing run FPP Amounts for the week |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
CONTRACTYEAR, WEEKNO,BILLRUNNO,PARTICIPANTID,REGIONID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
CONTRACTYEAR |
NUMBER(4,0) |
Yes |
The Billing Contract Year |
WEEKNO |
NUMBER(3,0) |
Yes |
The Billing WeekNo |
BILLRUNNO |
NUMBER(4,0) |
Yes |
The Billing RunNo |
PARTICIPANTID |
VARCHAR2(20) |
Yes |
The Participant Id Identifier |
REGIONID |
VARCHAR2(20) |
Yes |
The Region Id Identifier |
LOWERREG_AMOUNT |
NUMBER(18,8) |
No |
The Lower Reg Service FPP Amount for the Participant and the Region for the Billing Week |
LOWERREG_ACE_AMOUNT |
NUMBER(18,8) |
No |
The Lower Reg Service FPP ACE Residual Amount for the Participant and the Region for the Billing Week |
LOWERREG_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Lower Reg Service FPP ASOE Residual Amount for the Participant and the Region for the Billing Week |
LOWERREG_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
Sum of LOWERREG_ACE_AMOUNT + LOWERREG_ASOE_AMOUNT |
RAISEREG_AMOUNT |
NUMBER(18,8) |
No |
The Raise Reg Service FPP Amount for the Participant and the Region for the Billing Week |
RAISEREG_ACE_AMOUNT |
NUMBER(18,8) |
No |
The Raise Reg Service FPP ACE Residual Amount for the Participant and the Region for the Billing Week |
RAISEREG_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Raise Reg Service FPP ASOE Residual Amount for the Participant and the Region for the Billing Week |
RAISEREG_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
RAISEREG_ACE_AMOUNT + RAISEREG_ASOE_AMOUNT |
LASTCHANGED |
DATE |
No |
The Lastchanged datetime of the record. |
4.3.4 Modified table: BILLINGASRECOVERY
Comment |
This report shows participant charges for Ancillary Services for the billing period. This view shows the billing amounts for Ancillary Service Recovery. |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Daily Billing Run & Posting a PRELIM/FINAL and REVISE Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
CONTRACTYEAR, WEEKNO,BILLRUNNO,PARTICIPANTID,REGIONID |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
LOWERREG_USED |
NUMBER(18,8) |
No |
The FCAS Lower Reg Service Used Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
LOWERREG_UNUSED |
NUMBER(18,8) |
No |
The FCAS Lower Reg Service Unused Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
RAISEREG_USED |
NUMBER(18,8) |
No |
The FCAS Raise Reg Service Used Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
RAISEREG_UNUSED |
NUMBER(18,8) |
No |
The FCAS Raise Reg Service Unused Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
LOWERREG_USED_ACE |
NUMBER(18,8) |
No |
The FCAS Lower Reg Service Used ACE Residual Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
LOWERREG_USED_ASOE |
NUMBER(18,8) |
No |
The FCAS Lower Reg Service Used ASOE Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
LOWERREG_USED_RESIDUAL |
NUMBER(18,8) |
No |
LOWERREG_USED_ACE + LOWERREG_USED_ASOE |
RAISEREG_USED_ACE |
NUMBER(18,8) |
No |
The FCAS Raise Reg Service Used ACE Residual Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
RAISEREG_USED_ASOE |
NUMBER(18,8) |
No |
The FCAS Raise Reg Service Used ASOE Residual Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
RAISEREG_USED_RESIDUAL |
NUMBER(18,8) |
No |
RAISEREG_USED_ACE + RAISEREG_USED_ASOE |
LOWERREG_UNUSED_ACE |
NUMBER(18,8) |
No |
The FCAS Lower Reg Service Unused ACE Residual Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
LOWERREG_UNUSED_ASOE |
NUMBER(18,8) |
No |
The FCAS Lower Reg Service Unused ASOE Residual Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
LOWERREG_UNUSED_RESIDUAL |
NUMBER(18,8) |
No |
LOWERREG_UNUSED_ACE + LOWERREG_UNUSED_ASOE |
RAISEREG_UNUSED_ACE |
NUMBER(18,8) |
No |
The FCAS Raise Reg Service Unused ACE Residual Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
RAISEREG_UNUSED_ASOE |
NUMBER(18,8) |
No |
The FCAS Raise Reg Service Unused ASOE Residual Amount for the Billing Week. This column will be NULL for Billing Week Prior to FPP Rule Effective Date |
RAISEREG_UNUSED_RESIDUAL |
NUMBER(18,8) |
No |
RAISEREG_UNUSED_ACE + RAISEREG_UNUSED_ASOE |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
LOWERREG |
NUMBER(18,8) |
No |
Post-IESS the amount in this column represent only the Lower Regulation FCAS MPF Recovery Amount from Customer and Generator Connection Point MPFs, no Residue Amounts are added to this column value. For Billing Weeks past FPP Rule Effective Date this column is not used. Always show 0. |
RAISEREG |
NUMBER(18,8) |
No |
Post-IESS the amount in this column represent only the Raise Regulation FCAS MPF Recovery Amount from Customer and Generator Connection Point MPFs, no Residue Amounts are added to this column value. For Billing Weeks past FPP Rule Effective Date this column is not used. Always show 0. |
4.3.5 Modified table: BILLING_NMAS_TST_PAYMENTS (comment changes heading only)
Comment |
BILLING_NMAS_TEST_PAYMENTS publish the NSCAS/SRAS Testing Payments data for a posted billing week. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
BILLRUNNO |
4.3.6 Modified table: BILLING_NMAS_TST_RECOVERY (comment changes heading only)
Comment |
BILLING_NMAS_TEST_RECOVERY sets out the recovery of NMAS testing payments This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
BILLRUNNO |
4.3.7 Modified table: BILLING_NMAS_TST_RECVRY_TRK (comment changes heading only)
Comment |
BILLING_NMAS_TEST_RECVRY_TRK tracks the energy data used to allocate the test payment recovery over the recovery period. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
PUBLIC |
Data volume |
|
Trigger |
Billing Run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
BILLRUNNO |
4.4 Package: DISPATCH
Results from a published Dispatch See National Electricity Rules Run
4.4.1 Modified table: DISPATCHREGIONSUM
Comment |
DISPATCHREGIONSUM sets out the 5-minute solution for each dispatch run for each region, including the Frequency Control Ancillary Services (FCAS) services provided. Additional fields are for the Raise Regulation and Lower Regulation Ancillary Services plus improvements to demand calculations. |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
DISPATCHREGIONSUM updates every 5 minutes |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
DISPATCHINTERVAL, INTERVENTION, REGIONID, RUNNO, SETTLEMENTDATE |
New columns
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
BDU_INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
Energy Storage for BDU at the start of the interval (MWh) – Region Aggregated |
DECGEN_INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
Energy storage for Daily Energy Constrained Scheduled Generating Units at the start of the interval (MWh) - Region Aggregated |
4.4.2 Modified table: DISPATCHLOAD
Comment |
DISPATCHLOAD set out the current SCADA MW and target MW for each dispatchable unit, including relevant Frequency Control Ancillary Services (FCAS) enabling targets for each five minutes and additional fields to handle the new Ancillary Services functionality. Fast Start Plant status is indicated by dispatch mode |
---|---|
Visibility |
Private, Public Next-Day |
Data volume |
Medium |
Trigger |
DISPATCHLOAD shows data for every 5 minutes for all units, even zero targets. |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
DUID, INTERVENTION, RUNNO, SETTLEMENTDATE |
Modified columns
Comment changes only
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
The energy storage at the start of this dispatch interval (MWh) |
ENERGY_STORAGE |
NUMBER(15,5) |
No |
The projected energy storage based on cleared energy and regulation FCAS dispatch (MWh) |
4.5 Package: P5MIN
Results from a published Five-Minute Predispatch Run
4.5.1 Modified table: P5MIN_REGIONSOLUTION
Comment |
The five-minute predispatch (P5Min) is a MMS system providing projected dispatch for 12 Dispatch cycles (one hour). The 5-minute Predispatch cycle runs every 5-minutes to produce a dispatch and pricing schedule to a 5-minute resolution covering the next hour, a total of twelve periods. P5MIN_REGIONSOLUTION shows the results of the regional capacity, maximum surplus reserve and maximum spare capacity evaluations for each period of the study. |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
P5MIN_REGIONSOLUTION updates every 5 minutes |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
INTERVAL_DATETIME, REGIONID, RUN_DATETIME |
New columns
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
BDU_INITIAL_ENERGY_STORAGE |
Number(15,5) |
No |
Energy Storage for BDU at the start of the interval (MWh) – Region Aggregated |
DECGEN_INITIAL_ENERGY_STORAGE |
Number(15,5) |
No |
Energy storage for Daily Energy Constrained Scheduled Generating Units at the start of the interval (MWh) - Region Aggregated |
4.5.2 Modified table: P5MIN_UNITSOLUTION
Comment |
The five-minute predispatch (P5Min) is a MMS system providing projected dispatch for 12 Dispatch cycles (one hour). The 5-minute Predispatch cycle runs every 5-minutes to produce a dispatch and pricing schedule to a 5-minute resolution covering the next hour, a total of twelve periods. P5MIN_UNITSOLUTION shows the Unit results from the capacity evaluations for each period of the study. |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
P5MIN_UNITSOLUTION updates every 5 minutes for all units, even zero targets. |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
DUID, INTERVAL_DATETIME, RUN_DATETIME |
Modified columns
Comment changes only
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
The energy storage at the start of this dispatch interval (MWh) |
ENERGY_STORAGE |
NUMBER(15,5) |
No |
The projected energy storage based on cleared energy and regulation FCAS dispatch (MWh) |
4.6 Package: PRE_DISPATCH
Results from a published 30 minutes Pre-dispatch See Relevant Rules or Procedures Run
4.6.1 Modified table: PREDISPATCHLOAD
Comment |
PREDISPATCHLOAD shows pre-dispatch targets for each dispatchable unit, including additional fields to handle the Ancillary Services functionality. No record is written where a unit is not dispatched. PREDISPATCHLOAD shows all the results for each period |
---|---|
Visibility |
Private, Public Next-Day |
Data volume |
Medium |
Trigger |
Own (confidential) data updates every thirty minutes, with whole market data for the day before available as part of next day market data. |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
DATETIME, DUID |
Modified columns
Comment changes only
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
The energy storage at the start of this dispatch interval (MWh) |
ENERGY_STORAGE |
NUMBER(15,5) |
No |
The projected energy storage based on cleared energy and regulation FCAS dispatch (MWh) |
4.6.2 Modified table: PREDISPATCHREGIONSUM
Comment |
PREDISPATCHREGIONSUM sets out the overall regional Pre-Dispatch results for base case details (excluding price). |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
PREDISPATCHREGIONSUM updates every thirty minutes. |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
DATETIME, REGIONID |
New columns
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
BDU_INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
Energy Storage for BDU at the start of the interval (MWh) – Region Aggregated |
DECGEN_INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
Energy storage for Daily Energy Constrained Scheduled Generating Units at the start of the interval (MWh) - Region Aggregated |
4.7 Package: PD7DAY
Results from a published Predispatch 7 Day Run
4.7.1 Modified table: PD7DAY_PRICESOLUTION
Comment |
PD7DAY price solution |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
PD7DAY publishes few times per day |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
RUN_DATETIME,INTERVAL_DATETIME,REGIONID,INTERVENTION |
New columns
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
BDU_INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
Energy Storage for BDU at the start of the interval (MWh) – Region Aggregated |
DECGEN_INITIAL_ENERGY_STORAGE |
NUMBER(15,5) |
No |
Energy storage for Daily Energy Constrained Scheduled Generating Units at the start of the interval (MWh) - Region Aggregated |
4.8 Package: BIDS
Energy The unit must be a generator for the service type: ‘energy’. Loads cannot bid for mandatory restrictions capacity. and Market Based 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. Offers
4.8.1 Modified table: BIDOFFERPERIOD
Comment |
BIDOFFERPERIOD shows 5-minute period-based Energy and Ancillary Service bid data.BIDOFFERPERIOD is a child table of BIDDAYOFFER |
---|---|
Visibility |
Public |
Data volume |
Large |
Trigger |
BIDOFFERPERIOD data is published whenever new bid data arrives. |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
TRADINGDATE, BIDTYPE, DUID, OFFERDATETIME, DIRECTION, PERIODID |
New columns
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
RECALL_PERIOD |
NUMBER(8,3) |
No |
The advance notice (in hours) that a Scheduled Resource requires to achieve the PASA Availability MW for this trading interval |
4.8.2 Modified table: MNSP_BIDOFFERPERIOD
Comment |
MNSP_BIDOFFERPERIOD shows availability for 5-minute periods for a specific Bid and LinkID for the given Trading Date and period. MNSP_BIDOFFERPERIOD is a child to MNSP_DAYOFFER and links to BIDOFFERFILETRK for 5MS Bids. |
---|---|
Visibility |
|
Data volume |
|
Trigger |
Generated as submissions are processed in next-day reports |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
Primary key (in order) |
LINKID,OFFERDATETIME,PERIODID,TRADINGDATE |
New columns
Field name |
Data type |
Primary Key |
Comment |
---|---|---|---|
RECALL_PERIOD |
NUMBER(8,3) |
No |
The advance notice (in hours) that a Scheduled Resource requires to achieve the PASA Availability MW for this trading interval |
4.9 Package: FPP
Results from a published Frequency Performance Payments (FPP Frequency Performance Payments) Run. The FPP calculation runs performs every trading interval Energy Rules Terms (typically 5 minutes, but different for P5MIN 5 minute pre-dispatch / PREDISPATCH) and input data feeding into the calculations. The output data from the calculations is published on that same interval. There are some tables that operate on different frequencies (e.g. P5MIN / PREDISPATCH) as well as some data becoming public the following market day. For further details please see the FPP procedure and supporting documentation.
4.9.1 Modified table: FPP_UNIT_MW
Comment |
This report delivers the curated 4 second measurement MW data for each FPP unit |
---|---|
Visibility |
Private at the completion of FPP calculation run for a closed trading interval (i.e. every 5 minutes) Public from next market day (at a time after 4am market time) |
Data volume |
Large |
Trigger |
The private report delivers at the completion of a FPP calculation run for a closed trading interval (i.e. every 5 minutes) The public report delivers the next market day (at a time after 4am market time) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, MEASUREMENT_DATETIME, FPP_UNITID, VERSIONNO |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
MW_QUALITY_FLAG |
NUMBER(5) |
NO |
MW Quality (4 second SCADA measurement Quality) Supported values are: 0 = Bad Quality -1 = Value not used as input in the FPP calculation (generally used to indicate when SCADA data was late arriving after the FPP calculation commenced) |
4.9.2 Modified table: FPP_PERFORMANCE
Comment |
This report delivers the calculated performance value for each 5 minute trading interval for each FPP unit |
---|---|
Visibility |
Private at the completion of FPP calculation run for a closed trading interval (i.e. every 5 minutes) Public from next market day (at a time after 4am market time) |
Data volume |
Medium |
Trigger |
The private report delivers at the completion of a FPP calculation run for a closed trading interval (i.e. every 5 minutes) The public report delivers the next market day (at a time after 4am market time) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME,FPP_UNITID, VERSIONNO |
Comment changes only
4.9.3 Modified table: FPP_REGION_FREQ_MEASURE
Comment |
This report delivers the curated 4 second frequency deviation and frequency measure data for each region |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
At the completion of a FPP calculation run for a closed trading interval (i.e. every 5 minutes) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, MEASUREMENT_DATETIME, REGIONID, VERSIONNO |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
HZ_QUALITY_FLAG |
NUMBER(5) |
NO |
Frequency Quality (4 second frequency deviation quality for that region) Supported values are: 0 = Bad Quality -1 = Value not used as input in the FPP calculation (generally used to indicate when SCADA data was late arriving after the FPP calculation commenced) |
4.9.4 Modified table: FPP_CONTRIBUTION_FACTOR
Comment |
This report delivers the calculated contribution factor value for each 5 minute trading interval for each constraint and FPP unit |
---|---|
Visibility |
Private at the completion of FPP calculation run for a closed trading interval (i.e. every 5 minutes) Public from next market day (at a time after 4am market time) |
Data volume |
Medium |
Trigger |
The private report will be delivered at the completion of a FPP calculation run for a closed trading interval (i.e. every 5 minutes) The public report will be delivered the next market day (at a time after 4am market time) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, CONSTRAINTID, FPP_UNITID, VERSIONNO |
Modified columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
SETTLEMENTS_UNITID |
VARCHAR2(50) |
NO |
The Settlements Unit ID (registered DUID / TNI) Note that this SETTLEMENTS_UNITID is what is sent and used by the Settlements system, and may be different from the FPP_UNITID for non-scheduled loads where the FPP_UNITID may be a descriptive key, whereas what will be sent to Settlements as the SETTLEMENTS_UNITID will be the TNI code. |
4.9.5 Modified table: FPP_FORECAST_DEFAULT_CF
Comment |
This report delivers the forecast default contribution factors (DCF) effective for a billing period (aligned to the settlement week) |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
Approval of a FPP historical default contribution factor calculation run (i.e. every week) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
FPP_UNITID, CONSTRAINTID, EFFECTIVE_START_DATETIME, EFFECTIVE_END_DATETIME, VERSIONNO |
Modified columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
SETTLEMENTS_UNITID |
VARCHAR2(50) |
NO |
The Settlements Unit ID (registered DUID / TNI) Note that this SETTLEMENTS_UNITID is what is sent and used by the Settlements system, and may be different from the FPP_UNITID for non-scheduled loads where the FPP_UNITID may be a descriptive key, whereas what will be sent to Settlements as the SETTLEMENTS_UNITID will be the TNI code. |
4.9.6 Modified table: FPP_P5_FWD_EST_COST
Comment |
This report delivers the forward estimated unit cost based on P5min runs. These high-level estimates (i.e. assuming that all is unused FCAS) will be provided for each constraint for each 5 minute pre-dispatch interval. |
---|---|
Visibility |
Private |
Data volume |
Large |
Trigger |
At the completion of a P5MIN estimation calculation run (i.e. every 5 mins) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
RUN_DATETIME, RUNNO, INTERVAL_DATETIME, CONSTRAINTID, FPP_UNITID, VERSIONNO |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
EST_UNUSED_FCAS |
NUMBER(18,8) |
NO |
Estimated unused recovery FCAS in AUD (the forward financial estimate of the recovery of unused FCAS, assuming that all is unused FCAS). This value will be either 0 (nil), or a negative value (debit) only. For details on the calculation, please see FPP procedure and supporting documentation. Please note that there may be cases where there is not yet a default contribution factor for the constraint (for example if there is a new constraint binding in p5min that has not yet bound in dispatch). In these scenarios there will be no EST_UNUSED_FCAS row sent for the constraint, as it is currently incalculable until a corresponding default contribution factor is calculated from a dispatch run with this constraint binding. |
4.9.7 Modified table: FPP_P5_FWD_EST_RESIDUALRATE
Comment |
This report delivers the forward estimated residual cost rate based on P5min runs. These high-level estimates (i.e. assuming that all is unused FCAS) will be provided for each constraint for each 5 minute pre-dispatch interval. |
---|---|
Visibility |
Public |
Data volume |
Large |
Trigger |
At the completion of a P5MIN estimation calculation run (i.e. every 5 mins) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
RUN_DATETIME, RUNNO, INTERVAL_DATETIME, CONSTRAINTID, VERSIONNO |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
EST_UNUSED_FCAS |
NUMBER(18,8) |
NO |
Estimated unused recovery FCAS in AUD/MWh (the forward financial estimate of the recovery of unused FCAS, assuming that all is unused FCAS). This value will be either 0 (nil), or a negative value (debit) only. For details on the calculation, please see FPP procedure and supporting documentation. Please note that there may be cases where there is not yet a residual default contribution factor for the constraint (for example if there is a new constraint binding in p5min that has not yet bound in dispatch). In these scenarios there will be no EST_UNUSED_FCAS row sent for the constraint, as this is currently incalculable until a corresponding residual default contribution factor is calculated from a dispatch run with this constraint binding. |
4.9.8 Modified table: FPP_PD_FWD_EST_COST
Comment |
This report delivers the forward estimated unit cost based on PREDISPATCH runs. These high-level estimates (i.e. assuming that all is unused FCAS) will be provided for each constraint for each 30 minute pre-dispatch interval. |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
At the completion of a PREDISPATCH estimation calculation run (i.e. every 30 mins) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
PREDISPATCHSEQNO, RUN_DATETIME, RUNNO, INTERVAL_DATETIME, CONSTRAINTID, FPP_UNITID, VERSIONNO |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
EST_UNUSED_FCAS |
NUMBER(18,8) |
NO |
Estimated unused recovery FCAS in AUD (the forward financial estimate of the recovery of unused FCAS, assuming that all is unused FCAS). This value will be either 0 (nil), or a negative value (debit) only. For details on the calculation, please see FPP procedure and supporting documentation. Please note that there may be cases where there is not yet a default contribution factor for the constraint (for example if there is a new constraint binding in predispatch that has not yet bound in dispatch). In these scenarios there will be no EST_UNUSED_FCAS row sent for the constraint, as it is currently incalculable until a corresponding default contribution factor is calculated from a dispatch run with this constraint binding. |
4.9.9 Modified table: FPP_PD_FWD_EST_RESIDUALRATE
Comment |
This report delivers the forward estimated residual cost rate based on PREDISPATCH runs. These high-level estimates (i.e. assuming that all is unused FCAS) will be provided for each constraint for each 30 minute pre-dispatch interval. |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
At the completion of a PREDISPATCH estimation calculation run (i.e. every 30 minutes) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
PREDISPATCHSEQNO, RUN_DATETIME, RUNNO, INTERVAL_DATETIME, CONSTRAINTID, VERSIONNO |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
EST_UNUSED_FCAS |
NUMBER(18,8) |
NO |
Estimated unused recovery FCAS in AUD/MWh (the forward financial estimate of the recovery of unused FCAS, assuming that all is unused FCAS). This value will be either 0 (nil), or a negative value (debit) only. For details on the calculation, please see FPP procedure and supporting documentation. Please note that there may be cases where there is not yet a residual default contribution factor for the constraint (for example if there is a new constraint binding in predispatch that has not yet bound in dispatch). In these scenarios there will be no EST_UNUSED_FCAS row sent for the constraint, as this is currently incalculable until a corresponding residual default contribution factor is calculated from a dispatch run with this constraint binding. |
4.9.10 Modified table: FPP_RUN
Comment |
This report delivers details of the 5-minute FPP calculation engine success failure outcome saved in FPP database |
---|---|
Visibility |
Public |
Data volume |
Low |
Trigger |
At the completion of a FPP calculation run for a closed trading interval (i.e. every 5 minutes) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, VERSIONNO |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
RUN_STATUS |
VARCHAR2(20) |
NO |
The status of FPP_RUN at the time the data model extract report was run. Typical value is Completed |
4.9.11 New table: FPP_HIST_REGION_PERFORMANCE
Comment |
This report delivers the historical region performance calculated based on a historical period and effective for a billing period (aligned to the settlement week). This calculated historical region performance calculation is an input into the constraint level residual default contribution factor (DCF) which is published in FPP_FORECAST_RESIDUAL_DCF |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
Approval of a FPP historical performance calculation run (i.e. every week) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
REGIONID, EFFECTIVE_START_DATETIME, EFFECTIVE_END_DATETIME, VERSIONNO |
New columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
REGIONID |
VARCHAR2(20) |
YES |
Region ID of the historical region performance |
EFFECTIVE_START_DATETIME |
DATE |
YES |
Effective period start date and time (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) of the effective period for this historical performance values related to the region ID. This is the billing period over which these historical performance values will be effective / applied over. This will align to the settlement week. |
EFFECTIVE_END_DATETIME |
DATE |
YES |
Effective period end date and time (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) of the effective period for this historical performance values related to the region ID. This is the billing period over which these historical performance values will be effective / applied over. This will align to the settlement week. |
VERSIONNO |
NUMBER(10) |
YES |
Version (FPP historical performance calculation run number from the FPP database) Note that due to the these historical calculations, the version numbers listed here are different to the normal FPP run number version for trading interval calculations. |
HIST_PERIOD_START_DATETIME |
DATE |
NO |
Historical period start date and time (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) of the historical period for this historical performance calculation related to the region ID. This is the historical period of trading intervals that feed into the historical performance calculation. This will align to the settlement week. |
HIST_PERIOD_END_DATETIME |
DATE |
NO |
Historical period end date and time (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) of the historical period for this historical performance calculation related to the region ID. This is the historical period of trading intervals that feed into the historical performance calculation. This will align to the settlement week. |
REG_HIST_RAISE_PERFORMANCE |
NUMBER(18,5) |
NO |
Calculated regulation historical raise performance from the historical performance period (substitute raise performance when live performance is unavailable and default raise performance used for default contribution factor calculation) - please see the NER and FPP procedure documents for further information |
REG_HIST_LOWER_PERFORMANCE |
NUMBER(18,5) |
NO |
Calculated regulation historical lower performance from the historical performance period (substitute lower performance when live performance is unavailable and default lower performance used for default contribution factor calculation) - please see the NER and FPP procedure documents for further information |
FPP_HIST_RAISE_PERFORMANCE |
NUMBER(18,5) |
NO |
Calculated FPP historical raise performance from the historical performance period (substitute raise performance calculated used for negative contribution factor calculation when live performance is unavailable) - please see the NER and FPP procedure documents for further information |
FPP_HIST_LOWER_PERFORMANCE |
NUMBER(18,5) |
NO |
Calculated FPP historical lower performance from the historical performance period (substitute lower performance calculated used for negative contribution factor calculation when live performance is unavailable) - please see the NER and FPP procedure documents for further information |
4.9.12 Modified table: FPP_USAGE
Comment |
This report delivers the calculated usage for each constraint for each 5 minute trading interval |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
At the completion of a FPP calculation run for a closed trading interval (i.e. every 5 minutes) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, CONSTRAINTID, VERSIONNO |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
USAGE_REASON_FLAG |
NUMBER(5) |
NO |
The reason flag showing the decision matrix for the usage calculation Supported values are: |
USAGE_VALUE |
NUMBER(18,8) |
NO |
Usage (calculation of the proportion of regulation FCAS that was calculated to be used) |
4.9.13 Modified table: FPP_FCAS_SUMMARY
Comment |
This report delivers a summary of FCAS requirements as used by the FPP calculation (i.e. only RAISEREG / LOWERREG bid types) |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
At the completion of a FPP calculation run for a closed trading interval (i.e. every 5 minutes) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
RUN_DATETIME, RUNNO, INTERVAL_DATETIME, CONSTRAINTID, VERSIONNO |
Modified columns
Column rename from USAGE to USAGE_VALUE as USAGE is reserved Energy Rules Terms word
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
USAGE_VALUE |
VARCHAR2(20) |
NO |
Usage (calculation of the proportion of regulation FCAS that was calculated to be used). Note that this is a join back to the FPP_USAGE table. |
4.10 Package: STPASA_SOLUTION
Results from a published Short Term PASA Projected Assessment of System Adequacy. except executable files e.g., .DLLs, .LIBs and .EXEs with the user mentioned. See National Energy Rules Run.
4.10.1 New Table: STPASA_DUIDAVAILABILITY
Comment |
This report delivers available capacity, PASA availability and given recall period for all scheduled resources. Note that for an MNSP, DUID = LINKID in the MNSP_INTERCONNECTOR table |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
Start of each STPASA run (every hour) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
RUN_DATETIME, INTERVAL_DATETIME, DUID |
New Columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
RUN_DATETIME |
DATE |
Yes |
Nominal start time of the run |
INTERVAL_DATETIME |
DATE |
Yes |
Half hour ended interval |
DUID |
VARCHAR2(20) |
Yes |
NEM Dispatchable Unit Identifier |
GENERATION_MAX_AVAILABILITY |
NUMBER (12,6) |
No |
Available Capacity for a scheduled generating unit, |
GENERATION_PASA_AVAILABILITY |
NUMBER (12,0) |
No |
PASA Availability for a scheduled generating unit, BDU (Gen side), WDR or MNSP. |
GENERATION_RECALL_PERIOD |
NUMBER (8,3) |
No |
Recall Period associated with the PASA Availability for a scheduled generating unit, BDU (Gen side), WDR or MNSP. |
LOAD_MAX_AVAILABILITY |
NUMBER (12,6) |
No |
Available Capacity for a scheduled load or BDU (Load side). |
LOAD_PASA_AVAILABILITY |
NUMBER (12,0) |
No |
PASA Availability for a scheduled load or BDU (Load side). |
LOAD_RECALL_PERIOD |
NUMBER (8,3) |
No |
Recall Period associated with the PASA Availability for a scheduled load or BDU (Load side). |
LASTCHANGED |
DATE |
No |
The Last changed Date time of the record |
4.10.2 Modified table: STPASA_REGIONSOLUTION
Comment |
STPASA_REGIONSOLUTION shows the results of the regional capacity, maximum surplus reserve and maximum spare capacity evaluations for each period of the study. |
---|---|
Visibility |
Public |
Data volume |
Large |
Trigger |
Start of each STPASA run (every hour) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, REGIONID, RUN_DATETIME, RUNTYPE |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
AGGREGATEPASAAVAILABILITY |
NUMBER(12) |
No |
Sum of PASAAVAILABILITY for all scheduled generating units and scheduled bidirectional units (Gen side) with a Recall_Period of null or <= 24 hours plus the sum of Unconstrained Intermittent Generation Forecasts (UIGF) for all semi-scheduled generating units. For the RELIABILITY_LRC and OUTAGE_LRC runs, UIGF is the POE90 forecast. For the LOR Run, UIGF is the POE50 forecast. Note that the ‘RELIABILITY_LRC’ and ‘OUTAGE_LRC’ Run Types are discontinued from 31 July 2025. |
RUNTYPE |
VARCHAR2(20) |
Yes |
Type of run. Values are RELIABILITY_LRC, OUTAGE_LRC and LOR. Note that the STPASA ‘RELIABILITY_LRC’ and ‘OUTAGE_LRC’ Run Types are discontinued from 31 July 2025, with only the ‘LOR’ Run Type reported. |
4.11 Package: PDPASA
The PDPASA package provides a 30-minute solving process to the Market systems. The current methodology for calculating reserves in the PreDispatch timeframe is determined in a post processing step using a heuristic calculation based the results and Interconnector See Relevant Rules or Procedures limits from the PreDispatch run. The calculation is a reserve assessment based on the PASA solver similar to existing ST and MT PASA Medium Term Projected Assessment of System Adequacy. A 24-month supply demand forecast, published weekly, with daily resolution. business processes. The process reflects all intra-regional See Relevant Rules or Procedures and inter-regional network constraints as an input to the process.
4.11.1 New Table: PDPASA_DUIDAVAILABILITY
Comment |
This report delivers available capacity, PASA availability and given recall period for all scheduled resources. Note that for an MNSP, DUID = LINKID in the MNSP_INTERCONNECTOR table |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
Close to or start of PDPASA run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
RUN_DATETIME, INTERVAL_DATETIME, DUID |
New Columns
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
RUN_DATETIME |
DATE |
Yes |
First half hour ended interval of the run |
INTERVAL_DATETIME |
DATE |
Yes |
Half hour ended interval |
DUID |
VARCHAR2(20) |
Yes |
NEM Dispatchable Unit Identifier |
GENERATION_MAX_AVAILABILITY |
NUMBER (12,6) |
No |
Available Capacity for a scheduled generating unit, |
GENERATION_PASA_AVAILABILITY |
NUMBER (12,0) |
No |
PASA Availability for a scheduled generating unit, BDU (Gen side), WDR or MNSP. |
GENERATION_RECALL_PERIOD |
NUMBER (8,3) |
No |
Recall Period associated with the PASA Availability for a scheduled generating unit, BDU (Gen side), WDR or MNSP. |
LOAD_MAX_AVAILABILITY |
NUMBER (12,6) |
No |
Available Capacity for a scheduled load or BDU (Load side). |
LOAD_PASA_AVAILABILITY |
NUMBER (12,0) |
No |
PASA Availability for a scheduled load or BDU (Load side). |
LOAD_RECALL_PERIOD |
NUMBER (8,3) |
No |
Recall Period associated with the PASA Availability for a scheduled load or BDU (Load side). |
LASTCHANGED |
DATE |
No |
The Last changed Date time of the record |
4.11.2 Modified table: PDPASA_REGIONSOLUTION
Comment |
The PDPASA region solution data |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
PDPASA_REGIONSOLUTION is updated each PDPASA run (i.e. half-hourly) |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, REGIONID, RUN_DATETIME, RUNTYPE |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
AGGREGATEPASAAVAILABILITY |
NUMBER(12) |
No |
Sum of PASAAVAILABILITY for all scheduled generating units and scheduled bidirectional units (Gen side) with a Recall_Period of null or <= 24 hours plus the sum of Unconstrained Intermittent Generation Forecasts (UIGF) for all semi-scheduled generating units. For the OUTAGE_LRC run, UIGF is the POE90 forecast. For the LOR Run, UIGF is the POE50 forecast. Note that the ‘OUTAGE_LRC’ Run Type is discontinued from 31 July 2025. |
RUNTYPE |
VARCHAR2(20) |
Yes |
Type of run. Values are OUTAGE_LRC and LOR. Note that the PDPASA ‘OUTAGE_LRC’ Run Type is discontinued from 31 July 2025, with only the ‘LOR’ Run Type reported. |
4.12 Package: DEMAND_FORECASTS
Regional See Relevant Rules or Procedures Demand The amount of power consumed at any time Forecasts and Intermittent Generation Energy Rules Terms forecasts.
4.12.1 Modified table: INTERMITTENT_GEN_FCST_DATA
Comment |
Stores the forecast generation (MW) for each interval within a given forecast of an intermittent generator. |
---|---|
Visibility |
Private |
Data volume |
Medium |
Trigger |
Every 30 minutes when AEMO issues a new 30-minute forecast of wind generation out to 8 days ahead |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
DUID, INTERVAL_DATETIME, RUN_DATETIME |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
POWERPOELOW |
NUMBER(9,3) |
No |
90% probability of exceedance forecast value in MW at the interval end |
POWERPOEHIGH |
NUMBER(9,3) |
No |
10% probability of exceedance forecast value in MW at the interval end |
4.12.2 Modified table: ROOFTOP_PV_FORECAST
Comment |
Regional forecasts of Rooftop Solar generation across the half-hour intervals over 8 days |
---|---|
Visibility |
Public |
Data volume |
Medium |
Trigger |
Every 30 minutes over 8 days |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
Primary key (in order) |
INTERVAL_DATETIME, REGIONID, VERSION_DATETIME |
Modified columns
Comment changes only
Field name |
Data type |
Primary key |
Comment |
---|---|---|---|
POWERPOELOW |
NUMBER(12,3) |
No |
90% probability of exceedance forecast value in MW at the interval end |
POWERPOEHIGH |
NUMBER(12,3) |
No |
10% probability of exceedance forecast value in MW at the interval end |
4.13 Package: ANCILLARY_SERVICES
4.13.1 Modified table: CONTRACTLOADSHED (comment changes to heading only)
Comment |
CONTRACTLOADSHED shows Governor contract details used in the settlement and dispatch of this service. Note: services are dispatched as 6 and 60 raise Frequency Control Ancillary Services (FCAS). Mandatory requirements and breakpoint details are not used for load shed. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Settlement run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
CONTRACTID VERSIONNO |
4.13.2 Modified table: CONTRACTREACTIVEPOWER (comment changes heading only)
Comment |
CONTRACTREACTIVEPOWER shows Reactive Power contract details used in the settlement and dispatch of this service. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Settlement run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
CONTRACTID VERSIONNO |
4.14 Package: ASOFFER
4.14.1 Modified table: OFFERLSHEDDATA (comment changes heading only)
Comment |
OFFERLSHEDDATA shows reoffers of load shed including available load shed quantity. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Settlement run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
CONTRACTID EFFECTIVEDATE PERIODID VERSIONNO |
4.14.2 Modified table: OFFERPOWERDATA (comment changes heading only)
Comment |
OFFERRPOWERDATA shows reoffers of reactive power capability and settlement measurements. This Table may also be used for NSCAS and Type 1 transitional services procured by AEMO under the ISF framework during 2025 and prior to the implementation of all system changes. During this time descriptions in these tables may not be correct. |
---|---|
Visibility |
Private |
Data volume |
|
Trigger |
Settlement run |
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReport |
Primary key (in order) |
CONTRACTID EFFECTIVEDATE PERIODID VERSIONNO |
4.15 File interface changes
Package |
File ID |
Description |
Batcher file masks |
Frequency |
Modification |
Auto-subscription |
---|---|---|---|---|---|---|
SETTLEMENT_DATA |
SETTLEMENTS |
|
*_SETTLEMENTS_*.CSV |
Daily |
Modified |
|
SETTLEMENT_DATA |
SETTLEMENTSEXT |
|
*_SETTLEMENTSEXT_*.CSV |
Daily |
New |
Yes |
BILLING_RUN |
BILLING |
|
*_BILLING_*.CSV |
Weekly |
Modified |
|
SETTLEMENT_DATA |
SETTLEMENTS_INIT |
Settlement Results from an INITIAL Run processed using the INITIAL Meter data AEMO receive. |
*_SETTLEMENTS_INIT*.CSV |
Daily |
New |
No |
BILLING_RUN |
BILLING_INIT |
Billing Results from an INITIAL Run. |
*_BILLING_INIT*.CSV |
Daily |
New |
No |
P5MIN |
P5MIN |
|
*_P5MIN_*.CSV |
5 minutes |
Modified |
|
PRE_DISPATCH |
PREDISPATCHIS |
|
*_PREDISPATCHIS_*.CSV |
30 minutes |
Modified |
|
DISPATCH |
DISPATCH |
|
*_DISPATCHIS_*.CSV |
5 minutes |
Modified |
|
BIDS |
BIDOFFERFILETRK |
|
*_BID_*.CSV |
|
Modified |
|
BIDS |
NEM_BIDS |
|
*_NEM_BIDS_*.CSV |
|
Modified |
|
BIDS |
BID_MNSP |
|
*_BID_MNSP_*.CSV |
|
Modified |
|
PD7DAY |
PD7DAY |
|
*_PD7DAY_*.CSV |
|
Modified |
|
FPP |
FPP_UNIT |
|
*_FPP_UNIT_*.CSV |
5 minutes |
Modified |
|
FPP_RUN |
|
*_FPP_RUN_*.CSV |
5 minutes |
Modified |
|
|
NEXT_DAY_FPP |
|
*_NEXT_DAY_FPP_*.CSV |
Daily |
Modified |
No |
|
NEXT_DAY_FPPMW |
|
*_NEXT_DAY_FPPMW_*.CSV |
Daily |
Modified |
No |
|
NEXT_DAY_FPPMW_2 |
|
*_NEXT_DAY_FPPMW2_*.CSV |
Daily |
New (split delivery of NEXT_DAY_FPPMW) |
No (participants that are currently subscribed to NEXT_DAY_FPPMW will be automatically subscribed to NEXT_DAY_FPPMW_2) |
|
FPP_DCF |
|
*_FPP_DCF_*.CSV |
Weekly |
Modified |
|
|
FPP_HIST_REGION_PERFORMANCE |
|
*_FPP_HIST_REGION_PERFORMANCE_*.CSV |
Weekly |
New |
Yes |
|
FPP_PRIV_P5MIN_EST |
|
*_FPP_PRIV_P5MIN_EST_*.CSV |
5 minutes |
Modified |
|
|
FPP_P5MIN_RESID_EST |
|
*_FPP_P5MIN_RESID_EST_*.CSV |
5 minutes |
Modified |
|
|
FPP_PRIV_PD_EST |
|
*_FPP_PRIV_PD_EST_*.CSV |
30 minutes |
Modified |
|
|
FPP_PD_RESID_EST |
|
*_FPP_PD_RESID_EST_*.CSV |
30 minutes |
Modified |
|
4.16 Participant interfaces changes
Package |
Data model table |
File ID |
CSV report type |
Change |
---|---|---|---|---|
SETTLEMENT_DATA |
DAYTRACK |
SETTLEMENTS |
SETTLEMENTS,DAYTRACK,7 |
Modified |
SET_FCAS_CLAWBACK_RUN_TRK |
SETTLEMENTSEXT |
SETTLEMENTS,FCAS_CLAWBACK_TRK,1 |
New |
|
SET_FCAS_CLAWBACK_UNITSOLN |
SETTLEMENTSEXT |
SETTLEMENTS,FCAS_CLAWBACK_UNITSOL,1 |
New |
|
SET_FCAS_CLAWBACK_REQ |
SETTLEMENTSEXT |
SETTLEMENTS,FCAS_CLAWBACK_REQ,1 |
New |
|
SET_FCAS_REG_AMOUNT |
SETTLEMENTSEXT |
SETTLEMENTS,FCAS_REG_AMT,1 |
New |
|
SET_FCAS_REG_RESIDAMT |
SETTLEMENTSEXT |
SETTLEMENTS,FCAS_REG_RESIDAMT,1 |
New |
|
SET_FCAS_REG_DEF_AMT |
SETTLEMENTSEXT |
SETTLEMENTS,FCAS_REG_DEF_AMT,1 |
New |
|
SET_FCAS_REG_DEF_RESIDAMT |
SETTLEMENTSEXT |
SETTLEMENTS,FCAS_REG_DEF_RESIDAMT,1 |
New |
|
SET_FPP |
SETTLEMENTSEXT |
SETTLEMENTS,FPP,1 |
New |
|
SET_FCAS_REGULATION_TRK |
SETTLEMENTS |
SETTLEMENTS,SET_FCAS_REGULATION_TRK,3 |
Modified |
|
SET_FCAS_RECOVERY |
SETTLEMENTS |
SETTLEMENTS,FCAS_RECOVERY,9 |
Modified |
|
BILLING_RUN |
BILLING_FCAS_REG_AMT |
BILLING |
BILLING, FCAS_REG_AMT, 1 |
New |
BILLING_FCAS_REG_RESIDAMT |
BILLING |
BILLING, FCAS_REG_RESIDAMT, 1 |
New |
|
BILLING_FPP |
BILLING |
BILLING, FPP, 1 |
New |
|
BILLINGASRECOVERY |
BILLING |
BILLING, ASRECOVERY,10 |
Modified |
|
P5MIN |
P5MIN_REGIONSOLUTION |
P5MIN |
P5MIN,REGIONSOLUTION,10 |
Modified |
P5MIN_UNITSOLUTION |
P5MIN |
P5MIN,UNITSOLUTION,6 |
Modified |
|
PRE_DISPATCH |
PREDISPATCHLOAD |
PREDISPATCHIS |
PREDISPATCH,UNIT_SOLUTION,4 |
Modified |
PREDISPATCHREGIONSUM |
PREDISPATCHIS |
PREDISPATCH,REGION_SOLUTION,9 |
Modified |
|
DISPATCH |
DISPATCHLOAD |
DISPATCHIS |
DISPATCH,UNIT_SOLUTION,5 |
Modified |
DISPATCHREGIONSUM |
DISPATCHIS |
DISPATCH,REGIONSUM,9 |
Modified |
|
BIDS |
BIDOFFERPERIOD |
BIDOFFERFILETRK |
BIDS,BIDOFFERPERIOD,3 |
Modified |
BIDOFFERPERIOD |
NEM_BIDS |
BIDS,BIDOFFERPERIOD,3 |
Modified |
|
MNSP_BIDOFFERPERIOD |
NEM_BIDS |
BIDS,MNSPBIDOFFERPERIOD,2 |
Modified |
|
MNSP_BIDOFFERPERIOD |
BID_MNSP |
BIDS,MNSPBIDOFFERPERIOD,2 |
Modified |
|
PD7DAY |
PD7DAY_PRICESOLUTION |
PD7DAY |
PD7DAY,PRICESOLUTION,2 |
Modified |
FPP |
FPP_CONTRIBUTION_FACTOR |
FPP_UNIT |
FPP,CONTRIBUTION_FACTOR,2 |
Modified |
FPP_CONTRIBUTION_FACTOR |
NEXT_DAY_FPP |
FPP,CONTRIBUTION_FACTOR,2 |
Modified |
|
FPP_RUN |
FPP_RUN |
FPP,FPP_RUN,2 |
Modified |
|
FPP_FORECAST_DEFAULT_CF |
FPP_DCF |
FPP,FORECAST_DEFAULT_CF,2 |
Modified |
|
FPP_HIST_REGION_PERFORMANCE |
FPP_HIST_REGION_PERFORMANCE |
FPP,FPP_HIST_REGION_PERFORMANCE,1 |
New |
|
FPP_UNIT_MW |
NEXT_DAY_FPPMW |
FPP,FPP_UNIT_MW,2 |
Modified |
|
FPP_UNIT_MW |
NEXT_DAY_FPPMW_2 |
FPP,FPP_UNIT_MW,2 |
New (split delivery of file id NEXT_DAY_FPPMW) |
|
FPP_P5_FWD_EST_COST |
FPP_PRIV_P5MIN_EST |
FPP,P5_FWD_EST_COST,2 |
Modified |
|
FPP_P5_FWD_EST_RESIDUALRATE |
FPP_P5MIN_RESID_EST |
FPP,P5_FWD_EST_RESIDUALRATE,2 |
Modified |
|
FPP_PD_FWD_EST_COST |
FPP_PRIV_PD_EST |
FPP,PD_FWD_EST_COST,2 |
Modified |
|
FPP_PD_FWD_EST_RESIDUALRATE |
FPP_PD_RESID_EST |
FPP,PD_FWD_EST_RESIDUALRATE,2 |
Modified |
|
STPASA_DUIDAVAILABILITY |
STPASA |
STPASA, DUIDAVAILABILITY, 1 |
New |
|
STPASA_REGIONSOLUTION |
STPASA |
STPASA, REGIONSOLUTION, 8 |
Modified |
|
PDPASA |
PDPASA_DUIDAVAILABILITY |
PDPASA |
PDPASA, DUIDAVAILABILITY, 1 |
New |
PDPASA_REGIONSOLUTION |
PDPASA |
PDPASA, REGIONSOLUTION, 8 |
Modified |
4.17 Discontinued reports
Data model table |
File ID |
Delivered in file |
CSV report type |
Replaced by |
---|---|---|---|---|
SETCPDATA |
SETTLEMENTS |
*_SETTLEMENTS_*.CSV |
SETTLEMENTS,CPDATA,7 |
SETTLEMENTS, SET_ENERGY_TRANSACTIONS,1 |
SETGENDATA |
SETTLEMENTS |
*_SETTLEMENTS_*.CSV |
SETTLEMENTS,GENDATA,6 |
SETTLEMENTS,SET_ENERGY_GENSET_DETAIL,1 |
SETSMALLGENDATA |
SETTLEMENTS |
*_SETTLEMENTS_*.CSV |
SETTLEMENTS,SMALLGENDATA,1 |
SETTLEMENTS,SET_ENERGY_TRANSACTIONS,1 |
SETFCASREGIONRECOVERY |
SETTLEMENTS |
*_SETTLEMENTS_*.CSV |
SETTLEMENTS,FCASREGIONRECOVERY,5 |
SETTLEMENTS,FCASREGIONRECOVERY,6 |
SET_FCAS_RECOVERY |
SETTLEMENTTS |
*_SETTLEMENTS_*.CSV |
SETTLEMENTS,FCAS_RECOVERY,7 |
SETTLEMENTS,FCAS_RECOVERY,8 |
SETINTRAREGIONRESIDUES |
SETTLEMENTS |
*_SETTLEMENTS_*.CSV |
SETTLEMENTS,INTRAREGIONRESIDUES,5 |
SETTLEMENTS,INTRAREGIONRESIDUES,6 |
SET_NMAS_RECOVERY |
SETTLEMENTS |
*_SETTLEMENTS_*.CSV |
SETTLEMENTS,NMAS_RECOVERY,2 |
SETTLEMENTS,NMAS_RECOVERY,3 |
SETMARKETFEES |
SETTLEMENTS |
*_SETTLEMENTS_*.CSV |
SETTLEMENTS,MARKETFEES,6 |
SETTLEMENTS,MARKETFEES,7 |
DISPATCH_FCAS_REQ |
DISPATCHIS_FCAS |
*_DISPATCHIS_FCAS_*.CSV |
DISPATCHIS_FCAS,DISPATCH_FCAS_REQ,3 |
DISPATCH_FCAS_REQ_RUN and Note that decommissioning of the old FCAS_REQ report will only be effective from after June 2025 |
DISPATCH_FCAS_REQ |
DISPATCHIS_FCAS_LEGACY |
*_DISPATCHIS_FCAS_*.CSV |
DISPATCHIS_FCAS_LEGACY,DISPATCH_FCAS_REQ,3 |
DISPATCH_FCAS_REQ_RUN and Note that decommissioning of the old FCAS_REQ report will only be effective from after June 2025 |
PREDISPATCH_FCAS_REQ |
PREDISPATCHIS_FCAS |
*_PREDISPATCHIS_FCAS_*.CSV |
PREDISPATCHIS_FCAS,PREDISPATCH_FCAS_REQ,2 |
PD_FCAS_REQ_RUN and Note that decommissioning of the old FCAS_REQ report will only be effective from after June 2025 |
PREDISPATCH_FCAS_REQ |
PREDISPATCHIS_FCAS_LEGACY |
*_PREDISPATCHIS_FCAS_*.CSV |
PREDISPATCHIS_FCAS_LEGACY,PREDISPATCH_FCAS_REQ,2 |
PD_FCAS_REQ_RUN and Note that decommissioning of the old FCAS_REQ report will only be effective from after June 2025 |
P5MIN_FCAS_REQUIREMENT |
P5MIN_FCAS_REQUIREMENT |
*_P5MIN_FCAS_REQUIREMENT_*.CSV |
P5MIN_FCAS_REQUIREMENT,P5MIN_FCAS_REQUIREMENT,1 |
P5MIN_FCAS_REQ_RUN Note that decommissioning of the old FCAS_REQ report will only be effective from after June 2025 |
BILLING_APC_RECOVERY |
BILLING |
*_BILLING_*.CSV |
BILLING,APC_RECOVERY,2 |
BILLING,APC_RECOVERY,3 |
BILLRESERVETRADERRECOVERY |
BILLING |
*_BILLING_*.CSV |
BILLING, RESERVETRADERECOVERY,2 |
BILLING,RESERVETRADERECOVERY,3 |
BILLINGASRECOVERY |
BILLING |
*_BILLING_*.CSV |
BILLING,ASRECOVERY,8 |
BILLING,ASRECOVERY,9 |
DISPATCHLOAD |
DISPATCHIS |
*_DISPATCHIS_*.CSV |
DISPATCHIS,UNIT_SOLUTION,4 |
DISPATCHIS,UNIT_SOLUTION,5 |
DISPATCHREGIONSUM |
DISPATCHIS |
*_DISPATCHIS_*.CSV |
DISPATCHIS,REGIONSUM,7 |
DISPATCHIS,REGIONSUM,8 |
P5MIN_REGIONSOLUTION |
P5MIN |
*_P5MIN_*.CSV |
P5MIN,REGIONSOLUTION,8 |
P5MIN,REGIONSOLUTION,9 |
P5MIN_UNITSOLUTION |
P5MIN |
*_P5MIN_*.CSV |
P5MIN,UNITSOLUTION,5 |
P5MIN,UNITSOLUTION,6 |
PREDISPATCHLOAD |
PREDISPATCHIS |
*_PREDISPATCHIS_*.CSV |
PREDISPATCHIS,UNIT_SOLUTION,3 |
PREDISPATCHIS,UNIT_SOLUTION,4 |
PREDISPATCHREGIONSUM |
PREDISPATCHIS |
*_PREDISPATCHIS_*.CSV |
PREDISPATCHIS,REGION_SOLUTION,7 |
PREDISPATCHIS,REGION_SOLUTION,8 |
BIDDAYOFFER |
BIDOFFERFILETRK |
*_BIDOFFERFILETRK_*.CSV |
BIDOFFERFILETRK,BIDDAYOFFER,2 |
BIDOFFERFILETRK,BIDDAYOFFER,3 |
STAPASA_REGIONSOLUTION |
STPASA |
*_STPASA_*.CSV |
STPASA,REGIONSOLUTION,6 |
STPASA,REGIONSOLUTION,7 |
PDPASA_REGIONSOLUTION |
PDPASA |
*_PDPASA_*.CSV |
PDPASA,REGIONSOLUTION,6 |
PDPASA,REGIONSOLUTION,7 |