4 Electricity Data Model v5.6
This Release contains an updated version of the Electricity/Gas Data Model The definition of the interface to participants of data published by AEMO for gas or electricity. A database conforming to the Data Model can contain a local copy of all current participant-specific data recorded in the main database. The Data Model includes database tables, indexes, and primary keys. 5.6. This section describes the affected packages, tables, files, reports, and interfaces.
4.1 Data model changes summary
4.2 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.2.1 Modified table: BIDPEROFFER_D
|
Comment |
BIDPEROFFER_D shows the public summary of the energy and FCAS offers applicable in the Dispatch for the intervals identified. BIDPEROFFER_D is the child to BIDDAYOFFER_D. |
|
Visibility |
Public |
|
Data volume |
Large |
|
Trigger |
Updates daily shortly after 4am. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVREPORTS |
|
Primry key (in order) |
BIDTYPE, DIRECTION, DUID, INTERVAL_DATETIME, SETTLEMENTDATE |
|
Project |
ST PASA Procedure and Recall Period |
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.3 Package: DEMAND_FORECASTS
Regional See Relevant Rules or Procedures Demand The amount of power consumed at any time Forecasts, Intermittent Generator A person who owns, operates or controls a generating unit forecasts and Rooftop PV A system comprising 1 or more photovoltaic (PV) panels installed on a residential or commercial rooftop, converting sunlight to electricity. The capacity of these systems is less than 100 kilowatts (kW) forecasts.
4.3.1 Modified table: INTERMITTENT_GEN_FCST (comment changes heading only)
|
Comment |
Identifying record for a given forecast of an intermittent generation. This table is the version table for the INTERMITTENT_GEN_FCST_DATA table which stores the individual forecast values. AEMO plans to remove this table in a Data Model version release after 5.6. |
|
Visibility |
Private |
|
Data volume |
Medium |
|
Trigger |
INTERMITTENT_GEN_FCST_DATA updates every 30 minutes when AEMO issues a new 30-minute forecast of intermittent generation out to 8 days ahead. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
DUID, RUN_DATETIME |
|
Project |
Operational Forecasting |
4.3.2 Modified table: INTERMITTENT_GEN_FCST_DATA (comment changes heading only)
|
Comment |
Stores the forecast generation (MW) for each interval within a given forecast of an intermittent generator. AEMO plans to remove this table in a Data Model version release after 5.6. |
|
Visibility |
Private |
|
Data volume |
Medium |
|
Trigger |
INTERMITTENT_GEN_FCST_DATA updates 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 |
|
Project |
Operational Forecasting |
4.3.3 New table: INTERMITTENT_GEN_FCST_RUN
|
Comment |
Contains forecast runs for intermittent wind and solar units, with a 30-minute resolution over the week-ahead PD/STPASA timeframe. This is the parent table to the child table INTERMITTENT_GEN_FCST_PRED, which contains the corresponding forecast predictions over the full horizon. |
|
Visibility |
Private, Public Next-Day |
|
Data volume |
Medium |
|
Trigger |
Every 30 minutes when a new intermittent generator forecast is available, covering the 8 days ahead horizon with 30-minute resolution. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
FORECAST_RUN_DATETIME, DUID, OFFERDATETIME, PROVIDERID, FORECAST_PRIORITY |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
FORECAST_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime in downstream processes, unless a forecast run is missed, in this case the previous run is used. |
|
DUID |
VARCHAR2(20) |
YES |
Dispatchable unit identifier for which this forecast applies. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this forecast submission was loaded. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Forecast provider identifier |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
YES |
Priority of forecast run, higher number is used in preference to lower number for the same provider. |
|
PROVIDER_TIMESTAMP |
DATE |
NO |
Datetime when the provider created the forecast. |
|
REMARKS |
VARCHAR2(300) |
NO |
Comments relating to the forecast run. This column is not made available to the public. |
|
MODEL_USED |
VARCHAR2(30) |
NO |
Metadata describing the model used to produce the forecast run. This column is not made available to the public. |
|
SUPPRESSED_PROVIDER |
NUMBER(1,0) |
NO |
Flag indicating if the forecast run was suppressed by the provider when submitted. Suppressed forecasts are not used by downstream systems. Suppressed = 1, Unsuppressed = 0. |
|
TRANSACTION_ID |
VARCHAR2(100) |
NO |
Transaction identifier for receiving the forecast run |
|
LASTCHANGED |
DATE |
NO |
Datetime when the forecast run was written into AEMO's database. |
4.3.4 New table: INTERMITTENT_GEN_FCST_PRED
|
Comment |
Contains forecast predictions for intermittent wind and solar units, with a 30-minute resolution over the week-ahead PD/STPASA timeframe. This is the child table of the parent table INTERMITTENT_GEN_FCST_RUN, which contains the corresponding forecast runs. |
|
Visibility |
Private, Public Next-Day |
|
Data volume |
Large |
|
Trigger |
Every 30 minutes when a new intermittent generator forecast is available, covering the 8 days ahead horizon with 30-minute resolution. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
FORECAST_RUN_DATETIME, DUID, OFFERDATETIME, PROVIDERID, FORECAST_PRIORITY, INTERVAL_DATETIME, FORECAST_TYPE |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
|
FORECAST_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime in downstream processes, unless a forecast run is missed, in this case the previous run is used. |
|
|
DUID |
VARCHAR2(20) |
YES |
Dispatchable unit identifier for which this forecast applies. |
|
|
OFFERDATETIME |
DATE |
YES |
Datetime when this forecast submission was loaded. |
|
|
PROVIDERID |
VARCHAR2(20) |
YES |
Forecast provider identifier |
|
|
FORECAST_PRIORITY |
NUMBER(10,0) |
YES |
Priority of forecast run, higher number is used in preference to lower number for the same provider. |
|
|
INTERVAL_DATETIME |
DATE |
YES |
Datetime (interval-ending) for the period that this forecast applies to, within the current forecast_run_datetime. |
|
|
FORECAST_TYPE |
VARCHAR2(20) |
YES |
Type of forecast, for example, POE_10, POE_50, POE_90, MEAN and so on. |
|
|
FORECAST_VALUE |
NUMBER(18,8) |
NO |
Forecast value in MW. |
|
4.3.5 New table: INTERMITTENT_GEN_FCST_P5_RUN
|
Comment |
Contains forecast runs for intermittent wind and solar units, with a 5-minute resolution over the hour-ahead P5MIN timeframe. This is the parent table to the child table INTERMITTENT_GEN_FCST_P5_PRED, which contains the corresponding forecast predictions over the full horizon. |
|
Visibility |
Private, Public Next-Day |
|
Data volume |
Medium |
|
Trigger |
Every 5 minutes when a new intermittent generator forecast is available, covering the 2 hours ahead horizon with 5-minute resolution. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
FORECAST_RUN_DATETIME, DUID, OFFERDATETIME, PROVIDERID, FORECAST_PRIORITY |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
FORECAST_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime in downstream processes, unless a forecast run is missed, in this case the previous run is used. |
|
DUID |
VARCHAR2(20) |
YES |
Dispatchable unit identifier for which this forecast applies. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this forecast submission was loaded. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Forecast provider identifier |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
YES |
Priority of forecast run, higher number is used in preference to lower number for the same provider. |
|
PROVIDER_TIMESTAMP |
DATE |
NO |
Datetime when the provider created the forecast. |
|
REMARKS |
VARCHAR2(300) |
NO |
Comments relating to the forecast run. This column is not made available to the public. |
|
MODEL_USED |
VARCHAR2(30) |
NO |
Metadata describing the model used to produce the forecast run. This column is not made available to the public. |
|
SUPPRESSED_PROVIDER |
NUMBER(1,0) |
NO |
Flag indicating if the forecast run was suppressed by the provider when submitted. Suppressed forecasts are not used by downstream systems. Suppressed = 1, Unsuppressed = 0. |
|
TRANSACTION_ID |
VARCHAR2(100) |
NO |
Transaction identifier for receiving the forecast run. |
|
LASTCHANGED |
DATE |
NO |
Datetime when the forecast run was written into AEMO's database. |
4.3.6 New table: INTERMITTENT_GEN_FCST_P5_PRED
|
Comment |
Contains forecast predictions for intermittent wind and solar units, with a 5-minute resolution over the hour-ahead P5MIN timeframe. This is the child table of the parent table INTERMITTENT_GEN_FCST_P5_RUN, which contains the corresponding forecast runs. |
|
Visibility |
Private, Public Next-Day |
|
Data volume |
Large |
|
Trigger |
Every 5 minutes when a new intermittent generator forecast is available, covering the 2 hours ahead horizon with 5-minute resolution. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
FORECAST_RUN_DATETIME, DUID, OFFERDATETIME, PROVIDERID, FORECAST_PRIORITY, INTERVAL_DATETIME, FORECAST_TYPE |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
FORECAST_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime in downstream processes, unless a forecast run is missed, in this case the previous run is used. |
|
DUID |
VARCHAR2(20) |
YES |
Dispatchable unit identifier for which this forecast applies. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this forecast submission was loaded. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Forecast provider identifier |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
YES |
Priority of forecast run, higher number is used in preference to lower number for the same provider. |
|
INTERVAL_DATETIME |
DATE |
YES |
Datetime (interval-ending) for the period that this forecast applies to, within the current forecast_run_datetime. |
|
FORECAST_TYPE |
VARCHAR2(20) |
YES |
Type of forecast, for example, POE_10, POE_50, POE_90, MEAN and so on. |
|
FORECAST_VALUE |
NUMBER(18,8) |
NO |
Forecast value in MW. |
4.3.7 Modified table: INTERMITTENT_P5_PRED (comment changes heading only)
|
Comment |
Unconstrained Intermittent Generation Forecasts (UIGF) for 5-Minute Pre-dispatch. AEMO plans to remove this table in a Data Model version release after 5.6. |
|
Visibility |
Private |
|
Data volume |
Large |
|
Trigger |
Not applicable |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
DUID, FORECAST_PRIORITY, INTERVAL_DATETIME, OFFERDATETIME, ORIGIN, RUN_DATETIME |
|
Project |
Operational Forecasting |
4.3.8 Modified table: INTERMITTENT_P5_RUN (comment changes heading only)
|
Comment |
Unconstrained Intermittent Generation Forecasts (UIGF) for 5-Minute Pre-dispatch. AEMO plans to remove this table in a Data Model version release after 5.6. |
|
Visibility |
Private |
|
Data volume |
Medium |
|
Trigger |
Not applicable |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
DUID, FORECAST_PRIORITY, OFFERDATETIME, ORIGIN, RUN_DATETIME |
|
Project |
Operational Forecasting |
4.3.9 New table: ROOFTOP_PV_FCST_RUN
Participant facing
|
Comment |
Contains forecast runs for rooftop PV areas, with a 30-minute resolution over the week-ahead PD/STPASA timeframe. This is the parent table to the child table ROOFTOP_PV_FCST_PRED, which contains the corresponding forecast predictions over the full horizon. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Every 30 minutes when a new rooftop PV forecast is available, covering the 8 days ahead horizon with 30-minute resolution. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
FORECAST_RUN_DATETIME, AREAID, OFFERDATETIME, PROVIDERID, FORECAST_PRIORITY |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
FORECAST_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime in downstream processes, unless a forecast run is missed, in this case the previous run is used. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier, aligning with the load forecasting areas. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this forecast submission was loaded. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Forecast provider identifier, for example, AEMO, PROVIDER_A and so on. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
YES |
Priority of forecast run, higher number is used in preference to lower number for the same provider. |
|
PROVIDER_TIMESTAMP |
DATE |
NO |
Datetime when the provider created the forecast. |
|
REMARKS |
VARCHAR2(300) |
NO |
Comments relating to the forecast run. |
|
MODEL_USED |
VARCHAR2(30) |
NO |
Metadata describing the model used to produce the forecast run. |
|
SUPPRESSED_PROVIDER |
NUMBER(1,0) |
NO |
Flag indicating if the forecast run was suppressed by the provider when submitted. Suppressed forecasts are not used by downstream systems. Suppressed = 1, Unsuppressed = 0. |
|
INSTALLED_CAPACITY |
NUMBER(18,8) |
NO |
Installed rooftop PV capacity that was used for the forecast run, in MW. |
|
LASTCHANGED |
DATE |
NO |
Datetime when the forecast run was written into AEMO's database. |
4.3.10 New table: ROOFTOP_PV_FCST_PRED
Participant facing
|
Comment |
Contains forecast predictions for rooftop PV areas, with a 30-minute resolution over the week-ahead PD/STPASA timeframe. This is the child table of the parent table ROOFTOP_PV_FCST_RUN, which contains the corresponding forecast runs. |
|
Visibility |
PUBLIC |
|
Data volume |
Large |
|
Trigger |
Every 30 minutes when a new rooftop PV forecast is available, covering the 8 days ahead horizon with 30-minute resolution. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
FORECAST_RUN_DATETIME, AREAID, OFFERDATETIME, PROVIDERID, FORECAST_PRIORITY, INTERVAL_DATETIME, FORECAST_TYPE |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
FORECAST_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime in downstream processes, unless a forecast run is missed, in this case the previous run is used. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier, aligning with the load forecasting areas. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this forecast submission was loaded. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Forecast provider identifier, for example, AEMO, PROVIDER_A and so on. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
YES |
Priority of forecast run, higher number is used in preference to lower number for the same provider. |
|
INTERVAL_DATETIME |
DATE |
YES |
Datetime (interval-ending) for the period that this forecast applies to, within the current forecast_run_datetime. |
|
FORECAST_TYPE |
VARCHAR2(20) |
YES |
Type of forecast, for example, POE_10, POE_50, POE_90, MEAN and so on. |
|
FORECAST_VALUE |
NUMBER(18,8) |
NO |
Forecast value in MW. |
4.3.11 New table: ROOFTOP_PV_FCST_P5_RUN
Participant facing
|
Comment |
Contains forecast runs for rooftop PV areas, with a 5-minute resolution over the hour-ahead DS/P5MIN timeframe. This is the parent table to the child table ROOFTOP_PV_FCST_P5_PRED, which contains the corresponding forecast predictions over the full horizon. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Every 5 minutes when a new rooftop PV forecast is available, covering the 2 hours ahead horizon with 5-minute resolution. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
FORECAST_RUN_DATETIME, AREAID, OFFERDATETIME, PROVIDERID, FORECAST_PRIORITY |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
FORECAST_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime in downstream processes, unless a forecast run is missed, in this case the previous run is used. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier, aligning with the load forecasting areas. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this forecast submission was loaded. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Forecast provider identifier, for example, AEMO, PROVIDER_A and so on. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
YES |
Priority of forecast run, higher number is used in preference to lower number for the same provider. |
|
PROVIDER_TIMESTAMP |
DATE |
NO |
Datetime when the provider created the forecast. |
|
REMARKS |
VARCHAR2(300) |
NO |
Comments relating to the forecast run. |
|
MODEL_USED |
VARCHAR2(30) |
NO |
Metadata describing the model used to produce the forecast run. |
|
SUPPRESSED_PROVIDER |
NUMBER(1,0) |
NO |
Flag indicating if the forecast run was suppressed by the provider when submitted. Suppressed forecasts are not used by downstream systems. Suppressed = 1, Unsuppressed = 0. |
|
INSTALLED_CAPACITY |
NUMBER(18,8) |
NO |
Installed rooftop PV capacity that was used for the forecast run, in MW. |
|
LASTCHANGED |
DATE |
NO |
Datetime when the forecast run was written into AEMO's database. |
4.3.12 New table: ROOFTOP_PV_FCST_P5_PRED
Participant facing
|
Comment |
Contains forecast predictions for rooftop PV areas, with a 5-minute resolution over the hour-ahead DS/P5MIN timeframe. This is the child table of the parent table ROOFTOP_PV_FCST_P5_RUN, which contains the corresponding forecast runs. |
|
Visibility |
PUBLIC |
|
Data volume |
Large |
|
Trigger |
Every 5 minutes when a new rooftop PV forecast is available, covering the 2 hours ahead horizon with 5-minute resolution. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
FORECAST_RUN_DATETIME, AREAID, OFFERDATETIME, PROVIDERID, FORECAST_PRIORITY, INTERVAL_DATETIME, FORECAST_TYPE |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
FORECAST_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime in downstream processes, unless a forecast run is missed in which case the previous run is used. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier, aligning with the load forecasting areas. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this forecast submission was loaded. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Forecast provider identifier, for example, AEMO, PROVIDER_A and so on. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
YES |
Priority of forecast run, higher number is used in preference to lower number for the same provider. |
|
INTERVAL_DATETIME |
DATE |
YES |
Datetime (interval-ending) for the period that this forecast applies to, within the current forecast_run_datetime. |
|
FORECAST_TYPE |
VARCHAR2(20) |
YES |
Type of forecast, for example, POE_10, POE_50, POE_90, MEAN and so on. |
|
FORECAST_VALUE |
NUMBER(18,8) |
NO |
Forecast value in MW. |
4.3.13 Modified table: ROOFTOP_PV_ACTUAL (comment changes heading only)
|
Comment |
Estimate of regional Rooftop Solar actual generation for each half-hour interval in a day. AEMO plans to remove this table in a Data Model version release after 5.6. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Not applicable |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
INTERVAL_DATETIME, REGIONID, TYPE |
|
Project |
Operational Forecasting |
4.3.14 New table: ROOFTOP_PV_ACTUAL_RUN
Participant facing
|
Comment |
Contains prediction runs for rooftop PV area estimated actuals, with a 5-minute and 30-minute resolution for different estimate types. This is the parent table to the child table ROOFTOP_PV_ACTUAL_PRED, which contains the corresponding actual predictions. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Every 5 or 30 minutes when a new rooftop PV estimated actual is available, covering the most recent 5 or 30-minute interval that is available. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
PREDICTION_RUN_DATETIME, INTERVAL_DURATION, AREAID, OFFERDATETIME, ESTIMATE_TYPE, PROVIDERID, PREDICTION_PRIORITY |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
PREDICTION_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) from which this prediction run is valid. |
|
INTERVAL_DURATION |
NUMBER(3,0) |
YES |
Duration of each interval (in minutes) for this prediction, for example, 5 or 30. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier, aligning with the load forecasting areas. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this prediction submission was loaded. |
|
ESTIMATE_TYPE |
VARCHAR2(20) |
YES |
Type of Rooftop PV estimate, for example, MEASURED, SATELLITE and so on. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Provider identifier, for example, AEMO, PROVIDER_A and so on. |
|
PREDICTION_PRIORITY |
NUMBER(10,0) |
YES |
Priority of prediction run, higher number is used in preference to lower number for the same provider. |
|
PROVIDER_TIMESTAMP |
DATE |
NO |
Datetime when the provider created the forecast. |
|
REMARKS |
VARCHAR2(300) |
NO |
Comments relating to the prediction run. |
|
MODEL_USED |
VARCHAR2(30) |
NO |
Metadata describing the model used to produce the prediction run. |
|
SUPPRESSED_PROVIDER |
NUMBER(1,0) |
NO |
Flag indicating if the prediction run was suppressed by the provider when submitted. Suppressed predictions are not used by downstream forecasting systems. Suppressed = 1, Unsuppressed = 0. |
|
INSTALLED_CAPACITY |
NUMBER(18,8) |
NO |
Installed rooftop PV capacity used for the prediction run, in MW. |
|
LASTCHANGED |
DATE |
NO |
Datetime when the prediction run was written into AEMO's database. |
4.3.15 New table: ROOFTOP_PV_ACTUAL_PRED
Participant facing
|
Comment |
Contains predictions for rooftop PV area estimated actuals, with a 5-minute and 30-minute resolution for different estimate types. This is the child table of the parent table ROOFTOP_PV_ACTUAL_RUN, which contains the corresponding actual prediction runs. |
|
Visibility |
Public |
|
Data volume |
Large |
|
Trigger |
Every 5 or 30 minutes when a new rooftop PV estimated actual is available, covering the most recent 5 or 30-minute interval that is available. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
PREDICTION_RUN_DATETIME, INTERVAL_DURATION, AREAID, OFFERDATETIME, ESTIMATE_TYPE, PROVIDERID, PREDICTION_PRIORITY, INTERVAL_DATETIME |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
PREDICTION_RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) from which this prediction run is valid. |
|
INTERVAL_DURATION |
NUMBER(3,0) |
YES |
Duration of each interval (in minutes) for this prediction, for example, 5 or 30. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier, aligning with the load forecasting areas. |
|
OFFERDATETIME |
DATE |
YES |
Datetime when this prediction submission was loaded. |
|
ESTIMATE_TYPE |
VARCHAR2(20) |
YES |
Type of Rooftop PV estimate, for example, MEASURED, SATELLITE and so on. |
|
PROVIDERID |
VARCHAR2(20) |
YES |
Provider identifier, for example, AEMO, PROVIDER_A and so on. |
|
PREDICTION_PRIORITY |
NUMBER(10,0) |
YES |
Priority of prediction run, higher number is used in preference to lower number for the same provider. |
|
INTERVAL_DATETIME |
DATE |
YES |
Date and Time the forecast applies (dispatch interval ending). |
|
PREDICTION_VALUE |
NUMBER(18,8) |
NO |
Prediction value in MW. |
|
PREDICTION_QUALITY |
NUMBER(2,0) |
NO |
Prediction quality. Higher number represents better quality. |
4.3.16 Modified table: ROOFTOP_PV_FORECAST (comment changes heading only)
|
Comment |
Regional forecasts of Rooftop Solar generation across the half-hour intervals over 8 days. AEMO plans to remove this table in a Data Model version release after 5.6. |
|
Visibility |
Public |
|
Data volume |
Large |
|
Trigger |
Not applicable |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
INTERVAL_DATETIME, REGIONID, VERSION_DATETIME |
|
Project |
Operational Forecasting |
4.4 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.4.1 Modified table: DAYTRACK (comment changes only)
|
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 |
DAYTRACK is populated by the posting of a billing run. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
EXPOSTRUNNO, SETTLEMENTDATE |
|
Project |
Improving Security Frameworks |
Modified columns (comment changes only)
|
Field name |
Data type |
Primary key |
Comment |
|
EXANTERUNSTATUS |
VARCHAR2(15) |
NO |
This is to determine whether the Settlement Run is a valid run or not. |
|
EXPOSTRUNSTATUS |
VARCHAR2(15) |
NO |
Estimate for DAILY/INITIAL and Actual for PRELIM/FINAL and REVISE. |
4.4.2 New table: SET_NMAS_MANUAL_PAYMENT
|
Comment |
This report contains the NMAS Manual TI Payments that are uploaded by the Settlement Business Team. Amounts in this table are not calculated by the Settlement System. |
|
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, CONTRACTID, DUID, SERVICETYPE, PAYMENTTYPE, PERIODID |
|
Project |
Improving Security Frameworks |
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 Contract Participant Id. |
|
CONTRACTID |
VARCHAR2(20) |
Yes |
The NMAS System Security Contract ID. |
|
DUID |
VARCHAR2(20) |
Yes |
The DUID associated with the Contract Payment. |
|
SERVICETYPE |
VARCHAR2(40) |
Yes |
The NMAS System Security Service Types (INERTIA, SYSTEM STRENGTH, TYPE1, TYPE2 and so on). |
|
PAYMENTTYPE |
VARCHAR2(20) |
Yes |
The Payment Type associated with the Service like Availability, Usage, Enablement, Energy Revenue, Test, ADHOC and so on. |
|
PERIODID |
NUMBER(3,0) |
Yes |
The Settlement Period Id (1-288). |
|
REGIONID |
VARCHAR2(10) |
No |
The Contract Region Id. |
|
PAYMENTAMOUNT |
NUMBER(18,8) |
No |
The NMAS Contract Manual Payment for the Payment Type. |
|
LASTCHANGED |
DATE |
No |
The last changed date time of the record. |
4.4.3 Modified table: SET_FCAS_REG_RESIDAMT (comment changes only)
|
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 |
|
Project |
Frequency Performance Payments |
Modified columns (comment changes only)
|
Field name |
Data type |
Primary key |
Comment |
|
ASOE_MWH |
NUMBER(18,8) |
No |
The ASOE MWh value that is used for the FCAS 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. |
|
USED_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Used Recovery ASOE Amount calculated using the portion of ASOE MWh value against the Total residual MWh of the requirement regions. |
|
USED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
Sum of USED_ACE_AMOUNT + USED_ASOE_AMOUNT. |
|
UNUSED_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Unused Recovery ASOE Amount calculated using the portion of ASOE MWh value against the Total residual MWh of the requirement regions. |
|
UNUSED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
Sum of UNUSED_ACE_AMOUNT + UNUSED_ASOE_AMOUNT. |
4.4.4 Modified table: SET_FCAS_REG_DEF_RESIDAMT (comment changes only)
|
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 |
|
Project |
Frequency Performance Payments |
Modified columns (comment changes only)
|
Field name |
Data type |
Primary key |
Comment |
|
RESIDUAL_MWH |
NUMBER(18,8) |
No |
Sum of ABS(ACE_MWh) + ASOE_MWh. The MWh is not netted for residual calculation. |
|
UNUSED_ASOE_AMOUNT |
NUMBER(18,8) |
No |
The Unused Recovery ASOE Amount calculated using the ASOE MWh value of the requirement regions. |
|
UNUSED_RESIDUAL_AMOUNT |
NUMBER(18,8) |
No |
Sum of UNUSED_ACE_AMOUNT + UNUSED_ASOE_AMOUNT. |
4.5 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.5.1 New table: BILLING_NMAS_MANUAL_PAYMENT
|
Comment |
This report contains the NMAS Manual Weekly Payments that are uploaded by the Settlement Business Team. Amounts in this table are not calculated by the Settlement System. |
|
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, CONTRACTID, DUID, SERVICETYPE, PAYMENTTYPE |
|
Project |
Improving Security Frameworks |
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 Contract Participant Id. |
|
CONTRACTID |
VARCHAR2(20) |
Yes |
The NMAS System Security Contract ID. |
|
DUID |
VARCHAR2(20) |
Yes |
The DUID associated with the Contract Payment. |
|
SERVICETYPE |
VARCHAR2(40) |
Yes |
The NMAS System Security Service Types (INERTIA, SYSTEM STRENGTH, TYPE1, TYPE2 and so on). |
|
PAYMENTTYPE |
VARCHAR2(20) |
Yes |
The Payment Type associated with the Service like Availability, Usage, Enablement, Energy Revenue, Test, ADHOC and so on. |
|
REGIONID |
VARCHAR2(10) |
No |
The Contract Region Id. |
|
PAYMENTAMOUNT |
NUMBER(18,8) |
No |
The NMAS Contract Manual Payment for the Payment Type. |
|
LASTCHANGED |
DATE |
No |
The last changed date time of the record. |
4.5.2 New table: BILLING_NMAS_MANUAL_RECOVERY
|
Comment |
This report shows the summary of the Billing NMAS Recovery Amounts. This table will have recovery data for manual payments for System Security Services. |
|
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, CONTRACTID, SERVICETYPE, PAYMENTTYPE, REGIONID |
|
Project |
Improving Security Frameworks |
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 Contract Participant Id. |
|
CONTRACTID |
VARCHAR2(20) |
Yes |
The NMAS System Security Contract ID. |
|
SERVICETYPE |
VARCHAR2(40) |
Yes |
The NMAS System Security Service Types (INERTIA, SYSTEM STRENGTH, TYPE1, TYPE2 and so on). |
|
PAYMENTTYPE |
VARCHAR2(20) |
Yes |
The Payment Type associated with the Service like Availability, Usage, Enablement, Energy Revenue, Test, ADHOC and so on. |
|
REGIONID |
VARCHAR2(10) |
Yes |
Region Identifier |
|
PAYMENTAMOUNT |
NUMBER(18,8) |
No |
The NMAS Contract Manual Payment for the Payment Type. |
|
RECOVERYSTARTDATETIME |
DATE |
No |
The Recovery Start Date and Time for the Payment Calculation. |
|
RECOVERYENDDATETIME |
DATE |
No |
The Recovery End Date and Time for the Payment Calculation. |
|
RECOVERYAMOUNT_ACE |
NUMBER(18,8) |
No |
Recovery Amount on ACE portion ($). |
|
RECOVERYAMOUNT_ASOE |
NUMBER(18,8) |
No |
Recovery Amount on ASOE portion ($). |
|
PARTICIPANT_ACE_MWH |
NUMBER(18,8) |
No |
Participant Consumed Energy in MWh. |
|
PARTICIPANT_ASOE_MWH |
NUMBER(18,8) |
No |
Participant Sent Out Energy in MWh. |
|
REGION_ACE_MWH |
NUMBER(18,8) |
No |
Region Consumed Energy in MWh. |
|
REGION_ASOE_MWH |
NUMBER(18,8) |
No |
Region Sent Out Energy in MWh. |
|
LASTCHANGED |
DATE |
No |
The last changed date time of the record. |
4.6 Package: DISPATCH
Results from a published Dispatch See National Electricity Rules Run.
4.6.1 New table: DISPATCH_ROOFTOP_PV_FCST_TRK
|
Comment |
Uniquely tracks which Rooftop PV forecast run (from ROOFTOP_PV_FCST_P5_RUN) was used for the Area in which Dispatch run. |
|
Visibility |
PUBLIC |
|
Data volume |
Medium |
|
Trigger |
Every 5 minutes when a new dispatch run is published. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
RUN_DATETIME, AREAID |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) of the Dispatch run. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier aligning with the load forecasting areas, tracks to ROOFTOP_PV_FCST_P5_RUN.AREAID. |
|
FORECAST_RUN_DATETIME |
DATE |
NO |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime, unless a forecast run is missed, in this case the previous run is used. Tracks to ROOFTOP_PV_FCST_P5_RUN.FORECAST_RUN_DATETIME. |
|
PROVIDERID |
VARCHAR2(20) |
NO |
Provider identifier of the forecast run used for the DS run, tracks to ROOFTOP_PV_FCST_P5_RUN.PROVIDERID. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
NO |
Priority of the forecast run used for the DS run, tracks to ROOFTOP_PV_FCST_P5_RUN.FORECAST_PRIORITY. |
|
OFFERDATETIME |
DATE |
NO |
Submission datetime of the forecast run used for the DS run, tracks to ROOFTOP_PV_FCST_P5_RUN.OFFERDATETIME. |
4.6.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 |
|
Project |
Inverter Management System |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
ELEMENT_CAP |
NUMBER(5,0) |
NO |
Cap on the number of turbines or inverters at a DUID. |
4.7 Package: P5MIN
Results from a published Five-Minute Pre-dispatch See Relevant Rules or Procedures Run.
4.7.1 New table: P5MIN_INTERMITTENT_FCST_TRK
|
Comment |
Uniquely tracks which Intermittent Generation forecast run (from INTERMITTENT_GEN_FCST_P5_RUN) was used for the DUID in which 5-Minute Pre-dispatch run. |
|
Visibility |
Private, Public Next-Day |
|
Data volume |
Medium |
|
Trigger |
Every 5 minutes when a new 5-Minute Pre-dispatch run is published. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
RUN_DATETIME, DUID |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) of the 5-Minute Pre-dispatch run. |
|
DUID |
VARCHAR2(20) |
YES |
Dispatchable unit identifier, tracks to INTERMITTENT_GEN_FCST_P5_RUN.DUID. |
|
FORECAST_RUN_DATETIME |
DATE |
NO |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime, unless a forecast run is missed in which case the previous run is used. Tracks to INTERMITTENT_GEN_FCST_P5_RUN.FORECAST_RUN_DATETIME. |
|
PROVIDERID |
VARCHAR2(20) |
NO |
Provider of the forecast run used for the 5MPD run, tracks to INTERMITTENT_GEN_FCST_P5_RUN.PROVIDERID. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
NO |
Priority of the forecast run used for the 5MPD run, tracks to INTERMITTENT_GEN_FCST_P5_RUN.FORECAST_PRIORITY. |
|
OFFERDATETIME |
DATE |
NO |
Submission datetime of the forecast run used for the 5MPD run, tracks to INTERMITTENT_GEN_FCST_P5_RUN.OFFERDATETIME. |
4.7.2 New table: P5MIN_ROOFTOP_PV_FCST_TRK
|
Comment |
Uniquely tracks which Rooftop PV forecast run (from ROOFTOP_PV_FCST_P5_RUN) was used for the Area in which 5-Minute Pre-dispatch run. |
|
Visibility |
PUBLIC |
|
Data volume |
Medium |
|
Trigger |
Every 5 minutes when a new 5-Minute Pre-dispatch run is published. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
RUN_DATETIME, AREAID |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
RUN_DATETIME |
DATE |
YES |
Datetime (interval ending) of the 5-Minute Pre-dispatch run. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier aligning with the load forecasting areas, tracks to ROOFTOP_PV_FCST_P5_RUN.AREAID. |
|
FORECAST_RUN_DATETIME |
DATE |
NO |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime, unless a forecast run is missed, in this case the previous run is used. Tracks to ROOFTOP_PV_FCST_P5_RUN.FORECAST_RUN_DATETIME. |
|
PROVIDERID |
VARCHAR2(20) |
NO |
Provider identifier of the forecast run used for the DS run, tracks to ROOFTOP_PV_FCST_P5_RUN.PROVIDERID. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
NO |
Priority of the forecast run used for the DS run, tracks to ROOFTOP_PV_FCST_P5_RUN.FORECAST_PRIORITY. |
|
OFFERDATETIME |
DATE |
NO |
Submission datetime of the forecast run used for the DS run, tracks to ROOFTOP_PV_FCST_P5_RUN.OFFERDATETIME. |
4.7.3 Modified table: P5MIN_UNITSOLUTION
|
Comment |
The five-minute pre-dispatch (P5Min) is a MMS system providing projected dispatch for 12 Dispatch cycles (one hour). The 5-minute pre-dispatch 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 |
|
Project |
Inverter Management System |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
ELEMENT_CAP |
NUMBER(5,0) |
NO |
Cap on the number of turbines or inverters at a DUID. |
4.8 Package: PRE_DISPATCH
Results from a published 30-minute Pre-dispatch Energy Rules Terms Run.
4.8.1 New table: PD_INTERMITTENT_FCST_TRK
|
Comment |
Uniquely tracks which Intermittent Generation forecast run (from INTERMITTENT_GEN_FCST_RUN) was used for the DUID in which Pre-dispatch run. |
|
Visibility |
Private, Public Next-Day |
|
Data volume |
Medium |
|
Trigger |
Every 30 minutes when a new Pre-dispatch run is published. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
PREDISPATCHSEQNO, DUID |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
YES |
Unique identifier of Pre-dispatch run in the form YYYYMMDDPP with 01 at 04:30. |
|
DUID |
VARCHAR2(20) |
YES |
Dispatchable unit identifier, tracks to INTERMITTENT_GEN_FCST_RUN.DUID. |
|
FORECAST_RUN_DATETIME |
DATE |
NO |
Datetime (interval ending) when this forecast run is valid. It aligns with run_datetime, unless a forecast run is missed, in this case the previous run is used. Tracks to INTERMITTENT_GEN_FCST_RUN.FORECAST_RUN_DATETIME. |
|
PROVIDERID |
VARCHAR2(20) |
NO |
Provider of the forecast run used for the PD run, tracks to INTERMITTENT_GEN_FCST_RUN.PROVIDERID. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
NO |
Priority of the forecast run used for the PD run, tracks to INTERMITTENT_GEN_FCST_RUN.FORECAST_PRIORITY. |
|
OFFERDATETIME |
DATE |
NO |
Submission datetime of the forecast run used for the PD run, tracks to INTERMITTENT_GEN_FCST_RUN.OFFERDATETIME. |
4.8.2 New table: PD_ROOFTOP_PV_FCST_TRK
|
Comment |
Uniquely tracks which Rooftop PV forecast run (from ROOFTOP_PV_FCST_RUN) was used for the Area in which Pre-dispatch run. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Every 30 minutes when a new Pre-dispatch run is published. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
PREDISPATCHSEQNO, AREAID |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
YES |
Unique identifier of Pre-dispatch run in the form YYYYMMDDPP with 01 at 04:30. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier aligning with the load forecasting areas, tracks to ROOFTOP_PV_FCST_RUN.AREAID. |
|
FORECAST_RUN_DATETIME |
DATE |
NO |
Datetime (interval ending) when the forecast run is valid. It would align with run_datetime, unless a forecast run is missed, in this case the previous run will be used. Tracks to ROOFTOP_PV_FCST_RUN.FORECAST_RUN_DATETIME. |
|
PROVIDERID |
VARCHAR2(20) |
NO |
Provider identifier of the forecast run used for the PD run, tracks to ROOFTOP_PV_FCST_RUN.PROVIDERID. |
|
FORECAST_PRIORITY |
NUMBER(10,0) |
NO |
Priority of the forecast run used for the PD run, tracks to ROOFTOP_PV_FCST_RUN.FORECAST_PRIORITY. |
|
OFFERDATETIME |
DATE |
NO |
Submission datetime of the forecast run used for the PD run, tracks to ROOFTOP_PV_FCST_RUN.OFFERDATETIME. |
4.8.3 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 |
|
Project |
Inverter Management System |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
ELEMENT_CAP |
NUMBER(5,0) |
NO |
Cap on the number of turbines or inverters at a DUID. |
4.9 Package: MARKET_CONFIG
Standing data for the market.
4.9.1 New table: AREA
|
Comment |
Table containing static metadata for the Areas, which are sub-regions used in load forecasting and rooftop PV forecasting. The latest metadata can be obtained for each AreaID using the most recent EffectiveDate and then VersionNo. If an AreaID is not mapped to an active RegionID in the corresponding REGION_AREA table, then that AreaID can be considered inactive. |
|
Visibility |
Public |
|
Data volume |
Small |
|
Trigger |
Ad hoc when Areas are updated or added. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
AREAID, EFFECTIVEDATE, VERSIONNO |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier |
|
EFFECTIVEDATE |
DATE |
YES |
Calendar date from when this record set is effective. |
|
VERSIONNO |
NUMBER(3,0) |
YES |
Version number for the same effectivedate. |
|
AREA_NAME |
VARCHAR2(20) |
NO |
Area name |
|
AREA_DESCRIPTION |
VARCHAR2(200) |
NO |
Area description |
|
LASTCHANGED |
DATE |
NO |
Last date and time record changed. |
4.9.2 New table: REGION_AREA
|
Comment |
Table containing static metadata for mapping the Areas to Regions. The latest mapping can be obtained for each RegionID using the most recent EffectiveDate and then VersionNo. |
|
Visibility |
Public |
|
Data volume |
Small |
|
Trigger |
Ad hoc when Area-Region mappings are updated or added. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
REGIONID, EFFECTIVEDATE, VERSIONNO, AREAID |
|
Project |
Operational Forecasting |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
REGIONID |
VARCHAR2(10) |
YES |
Region identifier |
|
EFFECTIVEDATE |
DATE |
YES |
Calendar date from when this record set is effective. |
|
VERSIONNO |
NUMBER(3,0) |
YES |
Version number for the same effectivedate. |
|
AREAID |
VARCHAR2(10) |
YES |
Area identifier |
|
LASTCHANGED |
DATE |
NO |
Last date and time record changed. |
4.10 New Package: SYSTEM_SECURITY_MANAGEMENT
Package for ISF Improving Security Frameworks. A project that builds on existing tools and frameworks within the power system to enhance system security procurement frameworks (Improving Security Frameworks) for Electricity Power System Security procurement (not related to IT security)
4.10.1 New table: SSM_CONTRACT_UNIT_AVAIL
Participant facing
|
Comment |
The variable parameters associated to the Unit within an SSM Contract, allowing changes to the base contract values due to unit availabilities (e.g Maintenance, Outages). |
|
Visibility |
Private |
|
Data volume |
Medium |
|
Trigger |
On change of the Contract Availability. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
CONTRACT_ID, DUID, INTERVAL_DATETIME, VERSION_DATETIME |
|
Project |
Improving Security Frameworks (ISF) Phase 1 (Dec 2025 rule change) |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
CONTRACT_ID |
VARCHAR2(20) |
Yes |
Unique Contract Identifier |
|
DUID |
VARCHAR2(20) |
Yes |
Dispatchable Unit Identifier |
|
INTERVAL_DATETIME |
DATE |
Yes |
The starting Dispatch Interval for the availability change. This will be the active availability until the next INTERVAL_DATETIME record for this Contract and DUID. |
|
VERSION_DATETIME |
DATE |
Yes |
Effective Date and Time of this record. |
|
AVAILABLE |
NUMBER(1,0) |
No |
Indicates if DUID is available for the INTERVAL_DATETIME (1 = True, 0 = False). |
|
UNIT_COUNT |
NUMBER(4,0) |
No |
Number of sub-units within a DUID that are available for enablement. |
|
ACTIVATION_LEAD_TIME |
NUMBER(6,0) |
No |
The expected maximum lead time for the system security service to be enabled from a non-operational state in minutes. |
|
MIN_DISPATCH_MW |
NUMBER(18,8) |
No |
Minimum Dispatch Target required for DUID to enable the contract. |
|
MIN_ENABLEMENT_DURATION |
NUMBER(6,0) |
No |
Minimum duration a unit must be active to enable the contract in minutes. |
|
LASTCHANGED |
DATE |
No |
Last time record was changed |
4.10.2 New table: SSM_INSTRUCTION
Participant facing
|
Comment |
An enablement of an SSM Contract that instructs a Dispatchable Unit is to provide a System Security Service. |
|
Visibility |
Private |
|
Data volume |
Medium |
|
Trigger |
On enablement of a contract to provide System Security Services. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
INSTRUCTION_ID, VERSION_DATETIME |
|
Project |
Improving Security Frameworks (ISF) Phase 1 (Dec 2025 rule change) |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
INSTRUCTION_ID |
VARCHAR2(20) |
Yes |
Unique Instruction Identifier. |
|
VERSION_DATETIME |
DATE |
Yes |
Effective Date and Time of this record. |
|
INITIAL_INSTRUCTION_ID |
VARCHAR2(20) |
No |
Unique transaction identifier of initiating transaction if instruction related to an amendment or cancellation. |
|
DUID_PARTICIPANTID |
VARCHAR2(10) |
No |
Primary recipient (SSM Service Provider) of enablement instruction. |
|
CONTRACT_ID |
VARCHAR2(20) |
No |
Unique Contract Identifier used to create enablement. |
|
TNSP_PARTICIPANTID |
VARCHAR2(10) |
No |
Participant ID of TNSP if contract procurer is TNSP. |
|
DUID |
VARCHAR2(20) |
No |
Dispatchable Unit Identifier |
|
UNIT_COUNT |
NUMBER(4,0) |
No |
Number of sub-units within a DUID that are required for enablement. Value of zero means cancellation of instruction. |
|
EQUIPMENT_TYPE |
VARCHAR2(40) |
No |
Dispatchable Unit resource (for example, GENERATOR, LOAD, BIDIRECTIONAL, SYNCHRONOUS CONDENSER). |
|
SERVICE_TYPE |
VARCHAR2(40) |
No |
Requested Service to provide (System strength – combination, System strength – coefficient, NSCAS – voltage control, NSCAS, Inertia, Transitional service – type 1 MSL, Transitional service – type 1, Transitional service – type 2). |
|
MIN_DISPATCH_MW |
NUMBER(18,8) |
No |
Minimum Dispatch Target required for DUID to enable the contract. Value of zero means cancellation of instruction. |
|
START_INTERVAL_DATETIME |
DATE |
No |
The first Dispatch Interval of the enablement. |
|
END_INTERVAL_DATETIME |
DATE |
No |
The last Dispatch Interval of the enablement. |
|
LASTCHANGED |
DATE |
No |
Last time record was changed. |
4.10.3 New table: SSM_SCHEDULE
Participant facing
|
Comment |
Scheduled SSM contract enablement's. |
|
Visibility |
Private |
|
Data volume |
Medium |
|
Trigger |
Timed trigger once per day for previous day. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
INSTRUCTION_ID |
|
Project |
Improving Security Frameworks (ISF) Phase 1 (Dec 2025 rule change) |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
INSTRUCTION_ID |
VARCHAR2(20) |
Yes |
Unique Instruction Identifier |
|
CONTRACT_ID |
VARCHAR2(20) |
No |
Unique Contract Identifier used to create enablement. |
|
DUID_PARTICIPANTID |
VARCHAR2(10) |
No |
Primary recipient (SSM Service Provider) |
|
TNSP_PARTICIPANTID |
VARCHAR2(10) |
No |
Participant ID of TNSP if contract procurer is TNSP. |
|
DUID |
VARCHAR2(20) |
No |
Dispatchable Unit Identifier |
|
UNIT_COUNT |
NUMBER(4,0) |
No |
Number of sub-units within a DUID that are required for enablement. |
|
EQUIPMENT_TYPE |
VARCHAR2(40) |
No |
Dispatchable Unit resource (for example, GENERATOR, LOAD, BIDIRECTIONAL, SYNCHRONOUS CONDENSER). |
|
SERVICE_TYPE |
VARCHAR2(40) |
No |
Requested Service to provide (System strength – combination, System strength – coefficient, NSCAS – voltage control, NSCAS, Inertia, Transitional service – type 1 MSL, Transitional service – type 1, Transitional service – type 2). |
|
MIN_DISPATCH_MW |
NUMBER(18,8) |
No |
Minimum Dispatch Target required for DUID to enable the contract. |
|
START_INTERVAL_DATETIME |
DATE |
No |
The first Dispatch Interval of the enablement. |
|
END_INTERVAL_DATETIME |
DATE |
No |
The last Dispatch Interval of the enablement. |
|
LASTCHANGED |
DATE |
No |
Last time record was changed. |
4.10.4 New table: SSM_SCHEDULED_AVAILABILITY
Participant facing
|
Comment |
Scheduled SSM availability |
|
Visibility |
Private |
|
Data volume |
Medium |
|
Trigger |
Timed trigger once per week for the previous week. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
CONTRACT_ID, DUID, AVAILABLE_START_INTERVAL |
|
Project |
Improving Security Frameworks (ISF) Phase 1 (Dec 2025 rule change) |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
CONTRACT_ID |
VARCHAR2(20) |
Yes |
Unique Contract Identifier |
|
DUID |
VARCHAR2(20) |
Yes |
Dispatchable Unit Identifier |
|
AVAILABLE_START_INTERVAL |
DATE |
Yes |
The first Dispatch Interval the unit is available. |
|
AVAILABLE_END_INTERVAL |
DATE |
No |
The last Dispatch Interval the unit is available. |
|
TNSP_PARTICIPANTID |
VARCHAR2(10) |
No |
TNSP Participant ID |
|
LASTCHANGED |
DATE |
No |
Last time record was changed. |
4.10.5 New table: SSM_ENABLEMENT_PERIOD
Participant facing
|
Comment |
SSM Contract Enablement Periods |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Timed trigger once per day for previous day. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
INSTRUCTION_ID, DUID, ENABLEMENT_START_INTERVAL |
|
Project |
Improving Security Frameworks (ISF) Phase 1 (Dec 2025 rule change) |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
INSTRUCTION_ID |
VARCHAR2(20) |
Yes |
Unique Instruction Identifier |
|
DUID |
VARCHAR2(20) |
Yes |
Dispatchable Unit Identifier |
|
ENABLEMENT_START_INTERVAL |
DATE |
Yes |
The first Dispatch Interval the unit is enabled for SSM Services. |
|
ENABLEMENT_END_INTERVAL |
DATE |
No |
The last Dispatch Interval the unit is enabled for SSM Services. |
|
ENABLEMENT_REASON |
VARCHAR2(40) |
No |
Reason for the enablement. |
|
LASTCHANGED |
DATE |
No |
Last time record was changed. |
4.10.6 New table: SSM_ENABLEMENT_COSTS
Participant facing
|
Comment |
SSM Contract Enablement Costs for NEM |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Timed trigger once per day for previous day. |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
END_TRADINGDATE, ENABLEMENT_REASON |
|
Project |
Improving Security Frameworks (ISF) Phase 1 (Dec 2025 rule change) |
New columns
|
Field name |
Data type |
Primary key |
Comment |
|
END_TRADINGDATE |
DATE |
Yes |
Trading Date of the end of the enablement. |
|
ENABLEMENT_REASON |
VARCHAR2(40) |
Yes |
Primary Service type associated. |
|
ESTIMATED_COSTS |
NUMBER(18,8) |
No |
Cost estimation for the service type. |
|
LASTCHANGED |
DATE |
No |
Last time record was changed. |
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 Projected Assessment of System Adequacy. except executable files e.g., .DLLs, .LIBs and .EXEs with the user mentioned. See National Energy Rules 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 Modified table: PDPASA_DUIDAVAILABILITY (comment changes only)
|
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 |
|
Project |
ST PASA Procedure and Recall Period |
Modified columns (comment changes only)
Comment changes only
|
Field name |
Data type |
Primary key |
Comment |
|
RUN_DATETIME |
DATE |
Yes |
PDPASA run, identified by the first half hour ended interval of the run. |
|
LASTCHANGED |
DATE |
No |
Report Creation Date Time. |
4.11.2 Modified table: PDPASA_REGIONSOLUTION (comment changes only)
|
Comment |
The PDPASA region solution data. Note that the OUTAGE_LRC Run Type is no longer reported from 31 July 2025. |
|
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 |
|
Project |
ST PASA Procedure and Recall Period |
Modified columns
Comment changes only
|
Field name |
Data type |
Primary key |
Comment |
|
RUN_DATETIME |
DATE |
Yes |
Unique Timestamp Identifier for this run, identified by the first half hour ended interval of the run. |
|
RESERVEREQ |
NUMBER(12,2) |
No |
Reserve Requirement (MW). This field is not populated after 30 July 2025. |
|
CAPACITYREQ |
NUMBER(12,2) |
No |
Demand + Reserve requirements (MW). This field is not populated after 30 July 2025. |
|
ENERGYREQDEMAND50 |
NUMBER(12,2) |
No |
Sum of: (Region Demand50)/Period (sum by trading day, entered in first period of trading day, GWh). |
|
UNCONSTRAINEDCAPACITY |
NUMBER(12,0) |
No |
Aggregate generation + WDR capacity from Non-Energy Constrained plant subjected to restrictions due to network constraints. |
|
CONSTRAINEDCAPACITY |
NUMBER(12,0) |
No |
Aggregate generation + WDR capacity from Energy Constrained plant subjected to restrictions due to network constraints. |
|
NETINTERCHANGEUNDERSCARCITY |
NUMBER(12,2) |
No |
Net export (MW) out of this region in the LOR evaluation. Export if > 0, Import if < 0. This value is the same as LORNETINTERCHANGEUNDERSCARCITY. |
|
SURPLUSCAPACITY |
NUMBER(12,2) |
No |
Regional surplus capacity (MW), +/- values indicate surplus/deficit capacity respectively. This value reflects Regional LOR reserve. |
|
SURPLUSRESERVE |
NUMBER(12,2) |
No |
Regional surplus reserve (MW). This value also reflects Regional LOR reserve. Note: For LOR runs, RESERVEREQ requirement input is not used. |
|
RESERVECONDITION |
NUMBER(1,0) |
No |
Regional reserve condition from LRC run. This field is not populated after 30 July 2025. |
|
MAXSURPLUSRESERVE |
NUMBER(12,2) |
No |
Maximum Surplus Reserve (MW) evaluated for this region from LRC runs. This field is no longer populated. |
|
MAXSPARECAPACITY |
NUMBER(12,2) |
No |
Maximum Spare Capacity (MW) evaluated for this region. Calculated for each region in turn. This value reflects Regional LOR reserve. |
|
LASTCHANGED |
DATE |
No |
Date time this record was created. |
|
AGGREGATEPASAAVAILABILITY |
NUMBER(12,0) |
No |
Sum of PASAAVAILABILITY for all scheduled generating units and scheduled bidirectional units (Gen side) with a Recall_Period <= 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. |
|
MSRNETINTERCHANGEUNDERSCARCITY |
NUMBER(12,2) |
No |
Net interconnector flow from the region for this interval from the MSR assessment. This field is no longer populated. |
|
SEMISCHEDULEDCAPACITY |
NUMBER(12,2) |
No |
Constrained generation forecast (MW) for semi-scheduled units for the region. For OUTAGE_LRC run and LOR run, semi-scheduled generation is constrained by both System Normal and Outage constraints. All run types (OUTAGE_LRC, LOR) incorporate MAXAVAIL limits. |
|
LCR2 |
NUMBER(16,6) |
No |
Two Largest Credible Risks. MW value for highest two credible contingencies. |
|
SS_SOLAR_UIGF |
NUMBER(12,2) |
No |
Unconstrained Intermittent Generation Forecast for solar for the region. For OUTAGE_LRC run, this is the POE90 forecast (determined by LRCUIGFOption in CaseSolution). For LOR run, this is the POE50 forecast. |
|
SS_WIND_UIGF |
NUMBER(12,2) |
No |
Unconstrained Intermittent Generation Forecast for wind for the region. For OUTAGE_LRC run, this is the POE90 forecast (determined by LRCUIGFOption in CaseSolution). For LOR run, this is the POE50 forecast. |
|
SS_SOLAR_CAPACITY |
NUMBER(12,2) |
No |
Constrained generation forecast for solar for the region. For OUTAGE_LRC run and LOR run. solar generation is constrained by both System Normal and Outage constraints. All run types (OUTAGE_LRC, LOR) incorporate MAXAVAIL limits. |
|
SS_WIND_CAPACITY |
NUMBER(12,2) |
No |
Constrained generation forecast for wind for the region. For OUTAGE_LRC run and LOR run, wind generation is constrained by both System Normal and Outage constraints. All run types (OUTAGE_LRC, LOR) incorporate MAXAVAIL limits. |
|
SS_SOLAR_CLEARED |
NUMBER(12,2) |
No |
Constrained generation forecast (MW) for solar for the region. For OUTAGE_LRC run and LOR run, solar generation is constrained by both System Normal and Outage constraints. All run types (OUTAGE_LRC, LOR) incorporate MAXAVAIL limits. This value is the same as SS_SOLAR_CAPACITY. |
|
SS_WIND_CLEARED |
NUMBER(12,2) |
No |
Constrained generation forecast (MW) for wind for the region. For OUTAGE_LRC run and LOR run, wind generation is constrained by both System Normal and Outage constraints. All run types (OUTAGE_LRC, LOR) incorporate MAXAVAIL limits. This value is the same as SS_WIND_CAPACITY. |
4.11.3 Modified table: PDPASA_CONSTRAINTSOLUTION (comment changes only)
|
Comment |
PDPASA_CONSTRAINTSOLUTION shows binding and violated constraint results from the capacity evaluation, including the RHS value. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Updated each PDPASA run (i.e. half-hourly). |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
RUN_DATETIME |
|
Project |
ST PASA Procedure and Recall Period |
Modified columns
Comment changes only
|
Field name |
Data type |
Primary key |
Comment |
|
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.11.4 Modified table: PDPASA_INTERCONNECTORSOLN (comment changes only)
|
Comment |
PDPASA_INTERCONNECTORSOLN shows the results of the capacity evaluation for Interconnectors, including the calculated limits for the interval. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Updated each PDPASA run (i.e. half-hourly). |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
INTERCONNECTORID,INTERVAL_DATETIME,RUN_DATETIME,RUNTYPE,STUDYREGIONID |
|
Project |
ST PASA Procedure and Recall Period |
Modified columns
Comment changes only
|
Field name |
Data type |
Primary key |
Comment |
|
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: STPASA
Results from a published Short Term PASA Run.
4.12.1 Modified table: STPASA_DUIDAVAILABILITY (comment changes only)
|
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 |
|
Project |
ST PASA Procedure and Recall Period |
Modified columns
Comment changes only
|
Field name |
Data type |
Primary key |
Comment |
|
RUN_DATETIME |
DATE |
Yes |
STPASA run, identified by the nominal start time of the run. |
|
LASTCHANGED |
DATE |
No |
Report Creation Date Time. |
4.12.2 Modified table: STPASA_REGIONSOLUTION (comment changes only)
|
Comment |
STPASA_REGIONSOLUTION shows the results of the regional capacity, maximum surplus reserve and maximum spare capacity evaluations for each period of the study. Note that the RELIABILITY_LRC and OUTAGE_LRC Run Types are no longer reported from 31 July 2025. |
|
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) |
INTERVAL_DATETIME, REGIONID, RUN_DATETIME, RUNTYPE |
|
Project |
ST PASA Procedure and Recall Period |
Modified columns
Comment changes only
|
Field name |
Data type |
Primary key |
Comment |
|
RUN_DATETIME |
DATE |
Yes |
Unique Timestamp Identifier for this run, identified by the nominal start time of the run. |
|
INTERVAL_DATETIME |
DATE |
Yes |
End date time of the interval. |
|
DEMAND10 |
NUMBER(12,2) |
No |
10% Probability of Exceedance demand forecast. |
|
DEMAND50 |
NUMBER(12,2) |
No |
50% Probability of Exceedance demand forecast. |
|
DEMAND90 |
NUMBER(12,2) |
No |
90% Probability of Exceedance demand forecast. |
|
RESERVEREQ |
NUMBER(12,2) |
No |
Reserve Requirement (MW). This field is not populated after 30 July 2025. |
|
CAPACITYREQ |
NUMBER(12,2) |
No |
Demand + Reserve requirements (MW). This field is not populated after 30 July 2025. |
|
ENERGYREQDEMAND50 |
NUMBER(12,2) |
No |
Sum of: (Region Demand50)/Period (sum by trading day, entered in first period of trading day, GWh). |
|
UNCONSTRAINEDCAPACITY |
NUMBER(12,0) |
No |
Aggregate generation + WDR capacity from Non-Energy Constrained plant subjected to restrictions due to network constraints. |
|
CONSTRAINEDCAPACITY |
NUMBER(12,0) |
No |
Aggregate generation + WDR capacity from Energy Constrained plant subjected to restrictions due to network constraints. |
|
NETINTERCHANGEUNDERSCARCITY |
NUMBER(12,2) |
No |
Net export (MW) out of this region in the LOR evaluation. Export if > 0, Import if < 0. This value is the same as LORNETINTERCHANGEUNDERSCARCITY. |
|
SURPLUSCAPACITY |
NUMBER(12,2) |
No |
Regional surplus capacity (MW), +/- values indicate surplus/deficit capacity respectively. This value reflects Regional LOR reserve. |
|
SURPLUSRESERVE |
NUMBER(12,2) |
No |
Regional surplus reserve (MW). This value also reflects Regional LOR reserve. Note: For LOR runs, RESERVEREQ requirement input is not used. |
|
RESERVECONDITION |
NUMBER(1,0) |
No |
Regional reserve condition from LRC run. This field is not populated after 30 July 2025. |
|
MAXSURPLUSRESERVE |
NUMBER(12,2) |
No |
Maximum Surplus Reserve (MW) evaluated for this region from LRC runs. This field is no longer populated. |
|
MAXSPARECAPACITY |
NUMBER(12,2) |
No |
Maximum Spare Capacity (MW) evaluated for this region. Calculated for each region in turn. This value reflects Regional LOR reserve. |
|
LASTCHANGED |
DATE |
No |
Date time this record was created. |
|
AGGREGATEPASAAVAILABILITY |
NUMBER(12,0) |
No |
Sum of PASAAVAILABILITY for all scheduled generating units and scheduled bidirectional units (Gen side) with a Recall_Period <= 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. |
|
MSRNETINTERCHANGEUNDERSCARCITY |
NUMBER(12,2) |
No |
Net interconnector flow from the region for this interval from the MSR assessment. This field is no longer populated. |
|
SEMISCHEDULEDCAPACITY |
NUMBER(12,2) |
No |
Constrained generation forecast (MW) for semi-scheduled units for the region. For RELIABILITY_LRC run, semi-scheduled generation is constrained only by System Normal constraints. For OUTAGE_LRC run and LOR run, semi-scheduled generation is constrained by both System Normal and Outage constraints. All three run types (RELIABILITY_LRC, OUTAGE_LRC, LOR) incorporate MAXAVAIL limits. |
|
LOR_SEMISCHEDULEDCAPACITY |
NUMBER(12,2) |
No |
Constrained generation forecast for semi-scheduled units for the region for the LOR run. Semi-scheduled generation is constrained by both System Normal and Outage constraints, and incorporate MAXAVAIL limits. |
|
LCR2 |
NUMBER(16,6) |
No |
Two Largest Credible Risks. MW value for highest two credible contingencies. |
|
SS_SOLAR_CLEARED |
NUMBER(12,2) |
No |
Constrained generation forecast (MW) for solar for the region. For RELIABILITY_LRC run, solar generation is constrained only by System Normal constraints. For OUTAGE_LRC run and LOR run, solar generation is constrained by both System Normal and Outage constraints. All three run types (RELIABILITY_LRC, OUTAGE_LRC, LOR) incorporate MAXAVAIL limits. |
|
SS_WIND_CLEARED |
NUMBER(12,2) |
No |
Constrained generation forecast (MW) for wind for the region. For RELIABILITY_LRC run, wind generation is constrained only by System Normal constraints. For OUTAGE_LRC run and LOR run, wind generation is constrained by both System Normal and Outage constraints. All three run types (RELIABILITY_LRC, OUTAGE_LRC, LOR) incorporate MAXAVAIL limits. |
4.12.3 Modified table: STPASA_CONSTRAINTSOLUTION (comment changes only)
|
Comment |
STPASA_CONSTRAINTSOLUTION shows binding and violated constraint results from the capacity evaluation, including the RHS value. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Updated each STPASA run (i.e. every 2 hours). |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
CONSTRAINTID, INTERVAL_DATETIME, RUN_DATETIME, RUNTYPE, STUDYREGIONID |
|
Project |
ST PASA Procedure and Recall Period |
Modified columns
Comment only changes
|
Field name |
Data type |
Primary key |
Comment |
|
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.12.4 Modified table: STPASA_INTERCONNECTORSOLN (comment changes only)
|
Comment |
STPASA_INTERCONNECTORSOLN shows the results of the capacity evaluation for Interconnectors, including the calculated limits for the interval. |
|
Visibility |
Public |
|
Data volume |
Medium |
|
Trigger |
Updated each STPASA run (i.e. every 2 hours). |
|
Participant file share location |
<#INTRFACE>\<#PARTICIPANTID>\IMPORT\REPORTS\CSVReports |
|
Primary key (in order) |
INTERCONNECTORID,INTERVAL_DATETIME,RUN_DATETIME,RUNTYPE,STUDYREGIONID |
|
Project |
ST PASA Procedure and Recall Period |
Modified columns
Comment only changes
|
Field name |
Data type |
Primary key |
Comment |
|
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.13 File interface changes
|
Package |
File ID |
Description |
Batcher file masks |
Frequency |
Change |
Auto-subscription |
|
DEMAND_FORECASTS |
INTERMITTENT_GEN_FCST |
Real-time private forecasts for intermittent wind and solar units (30-min PD/STPASA timeframe) |
*_INTERMITTENT_GEN_FCST_*.CSV |
30 min |
Modified |
No |
|
NEXT_DAY_INTERMITTENT_GEN_FCST |
Next day public forecasts for intermittent wind and solar units (30-min PD/STPASA timeframe) |
PUBLIC_NEXT_DAY_INTERMITTENT_GEN_FCST_*.CSV |
Daily |
New |
No |
|
|
INTERMITTENT_GEN_FCST_P5 |
Real-time private forecasts for intermittent wind and solar units (5-min P5MIN timeframe) |
*_INTERMITTENT_GEN_FCST_P5_*.CSV |
5 min |
New |
Yes |
|
|
NEXT_DAY_INTERMITTENT_GEN_FCST_P5 |
Next day public forecasts for intermittent wind and solar units (5-min P5MIN timeframe) |
PUBLIC_NEXT_DAY_INTERMITTENT_GEN_FCST_P5_*.CSV |
Daily |
New |
No |
|
|
ROOFTOP_PV_FCST |
Real-time public forecasts for rooftop PV Areas (30-min PD/STPASA timeframe) |
PUBLIC_ROOFTOP_PV_FCST_*.CSV |
30 min |
New |
Yes |
|
|
ROOFTOP_PV_FCST_P5 |
Real-time public forecasts for rooftop PV Areas (5-min DS/P5MIN timeframe) |
PUBLIC_ROOFTOP_PV_FCST_P5_*.CSV |
5 min |
New |
Yes |
|
|
ROOFTOP_PV_ACTL |
Real-time public estimated actuals for rooftop PV Areas (5-min and 30-min resolution) |
PUBLIC_ROOFTOP_PV_ACTL_*.CSV |
5 and 30 min |
New |
Yes |
|
|
DISPATCH |
DS_ROOFTOP_PV_FCST_TRK |
Real-time tracking of which Rooftop PV forecast run was used for the Area in the corresponding Dispatch run. |
PUBLIC_ROOFTOP_PV_FCST_DS_TRK_*.CSV |
5 min |
New |
Yes |
|
DISPATCHIS |
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. |
*DISPATCHIS*.CSV |
5 min |
New |
No |
|
|
NEXT_DAY_DISPATCH |
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. |
*NEXT_DAY_DISPATCH*.CSV |
5 min |
New |
No |
|
|
P5MIN |
P5_INTERMITTENT_GEN_FCST_TRK |
Real-time tracking of which Intermittent Generation forecast run was used for the DUID in the corresponding 5-min Pre-dispatch run. |
*_INTERMITTENT_GEN_FCST_P5_TRK_*.CSV |
5 min |
New |
Yes |
|
P5_ROOFTOP_PV_FCST_TRK |
Real-time tracking of which Rooftop PV forecast run was used for the Area in the corresponding 5-min Pre-dispatch run. |
PUBLIC_ROOFTOP_PV_FCST_P5_TRK_*.CSV |
5 min |
New |
Yes |
|
|
P5MIN |
The five-minute pre-dispatch (P5Min) is a MMS system providing projected dispatch for 12 Dispatch cycles (one hour). The 5-minute pre-dispatch 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. |
*P5MIN*.CSV |
5 min |
New |
No |
|
|
PRE_DISPATCH |
PD_INTERMITTENT_GEN_FCST_TRK |
Real-time tracking of which Intermittent Generation forecast run was used for the DUID in the corresponding Pre-dispatch run. |
*_INTERMITTENT_GEN_FCST_PD_TRK_*.CSV |
30 min |
New |
Yes |
|
PD_ROOFTOP_PV_FCST_TRK |
Real-time tracking of which Rooftop PV forecast run was used for the Area in the corresponding Pre-dispatch run. |
PUBLIC_ROOFTOP_PV_FCST_PD_TRK_*.CSV |
30 min |
New |
Yes |
|
|
NEXT_DAY_PREDISPATCH_D |
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. |
*NEXT_DAY_PREDISPATCH_D*.CSV |
30 min |
New |
No |
|
|
PREDISPATCHIS |
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. |
*PREDISPATCHIS*.CSV |
30 min |
New |
No |
|
|
MARKET_CONFIG |
AREA |
Static metadata for the Areas (sub-regions used in load forecasting and rooftop PV forecasting) |
PUBLIC_AREA_*.CSV |
Ad hoc |
New |
Yes |
|
REGION_AREA |
Static metadata for mapping the Areas (sub-regions) to Regions |
PUBLIC_REGION_AREA_*.CSV |
Ad hoc |
New |
Yes |
|
|
SYSTEM_SECURITY_MANAGEMENT |
SSM_CONTACT_UNIT_AVAIL |
|
|
|
New |
Yes |
|
SSM_INSTRUCTION |
|
|
|
New |
Yes |
|
|
SSM_DAILY_SCHEDULE |
|
|
|
New |
Yes |
|
|
SSM_AVAILABILITY |
|
|
|
New |
Yes |
|
|
SSM_ENABLEMENT_PERIOD |
|
|
|
New |
Yes |
|
|
SSM_ENABLEMENT_COSTS |
|
|
|
New |
Yes |
4.14 Participant interfaces changes
|
Package |
Data model table |
File ID |
CSV report type |
Change |
|
DEMAND_FORECASTS |
INTERMITTENT_GEN_FCST_RUN |
INTERMITTENT_GEN_FCST |
INTERMITTENT_GEN,FORECAST,1 |
New |
|
INTERMITTENT_GEN_FCST_RUN |
NEXT_DAY_INTERMITTENT_GEN_FCST |
INTERMITTENT_GEN,FORECAST,1 |
New |
|
|
INTERMITTENT_GEN_FCST_PRED |
INTERMITTENT_GEN_FCST |
INTERMITTENT_GEN_FCST_PRED,1 |
New |
|
|
INTERMITTENT_GEN_FCST_PRED |
NEXT_DAY_INTERMITTENT_GEN_FCST |
INTERMITTENT_GEN_FCST_PRED,1 |
New |
|
|
INTERMITTENT_GEN_FCST_P5_RUN |
INTERMITTENT_GEN_FCST_P5 |
INTERMITTENT_GEN_FCST_P5_RUN,1 |
New |
|
|
INTERMITTENT_GEN_FCST_P5_RUN |
NEXT_DAY_INTERMITTENT_GEN_FCST_P5 |
INTERMITTENT_GEN_FCST_P5_RUN,1 |
New |
|
|
INTERMITTENT_GEN_FCST_P5_PRED |
INTERMITTENT_GEN_FCST_P5 |
INTERMITTENT_GEN_FCST_P5_PRED,1 |
New |
|
|
INTERMITTENT_GEN_FCST_P5_PRED |
NEXT_DAY_INTERMITTENT_GEN_FCST_P5 |
INTERMITTENT_GEN_FCST_P5_PRED,1 |
New |
|
|
ROOFTOP_PV_FCST_RUN |
ROOFTOP_PV_FCST |
ROOFTOP,FORECAST,1 |
New |
|
|
ROOFTOP_PV_FCST_PRED |
ROOFTOP_PV_FCST |
ROOFTOP,FORECAST,1 |
New |
|
|
ROOFTOP_PV_FCST_P5_RUN |
ROOFTOP_PV_FCST_P5 |
ROOFTOP,FORECAST,1 |
New |
|
|
ROOFTOP_PV_FCST_P5_PRED |
ROOFTOP_PV_FCST_P5 |
ROOFTOP,FORECAST,1 |
New |
|
|
ROOFTOP_PV_ACTUAL_RUN |
ROOFTOP_PV_ACTL |
ROOFTOP,ACTUAL1 |
New |
|
|
ROOFTOP_PV_ACTUAL_PRED |
ROOFTOP_PV_ACTL |
ROOFTOP,ACTUAL,1 |
New |
|
|
SETTLEMENT_DATA |
SET_NMAS_MANUAL_PAYMENT |
SETTLEMENTS_EXTN |
SETTLEMENTS,NMAS_MANUAL_PAYMENT,1 |
New |
|
BILLING_RUN |
BILLING_NMAS_MANUAL_PAYMENT |
BILLING |
BILLING,NMAS_MANUAL_PAYMENT,1 |
New |
|
BILLING_NMAS_MANUAL_RECOVERY |
BILLING |
BILLING,NMAS_MANUAL_RECOVERY,1 |
New |
|
|
DISPATCH |
DISPATCH_ROOFTOP_PV_FCST_TRK |
DS_ROOFTOP_PV_FCST_TRK |
DISPATCH,ROOFTOP_PV,1 |
New |
|
DISPATCHLOAD |
DISPATCHIS |
DISPATCH,UNIT_SOLUTION,6 |
Modified |
|
|
DISPATCHLOAD |
NEXT_DAY_DISPATCH |
DISPATCH,UNIT_SOLUTION,6 |
Modified |
|
|
P5MIN |
P5MIN_INTERMITTENT_FCST_TRK |
P5_INTERMITTENT_GEN_FCST_TRK |
P5MIN,INTERMITTENT_GEN,1 |
New |
|
P5MIN_INTERMITTENT_FCST_TRK |
NEXT_DAY_INTERMITTENT_GEN_FCST_P5 |
P5MIN,INTERMITTENT_GEN,1 |
New |
|
|
P5MIN_ROOFTOP_PV_FCST_TRK |
P5_ROOFTOP_PV_FCST_TRK |
P5MIN,ROOFTOP_PV,1 |
New |
|
|
P5MIN_UNITSOLUTION |
P5MIN |
P5MIN,UNITSOLUTION,7 |
Modified |
|
|
PRE-DISPATCH |
PD_INTERMITTENT_FCST_TRK |
PD_INTERMITTENT_GEN_FCST_TRK |
PREDISPATCH,INTERMITTENT_GEN,1 |
New |
|
PD_INTERMITTENT_FCST_TRK |
NEXT_DAY_INTERMITTENT_GEN_FCST |
PREDISPATCH,INTERMITTENT_GEN,1 |
New |
|
|
PD_ROOFTOP_PV_FCST_TRK |
PD_ROOFTOP_PV_FCST_TRK |
PREDISPATCH,ROOFTOP_PV,1 |
New |
|
|
PREDISPATCHLOAD |
NEXT_DAY_PREDISPATCH_D |
PREDISPATCH,UNIT_SOLUTION,5 |
Modified |
|
|
PREDISPATCHLOAD |
PREDISPATCHIS |
PREDISPATCH,UNIT_SOLUTION,5 |
Modified |
|
|
MARKET_CONFIG |
AREA |
AREA |
MARKET_CONFIG,AREA,1 |
New |
|
REGION_AREA |
REGION_AREA |
MARKET_CONFIG,REGION_AREA,1 |
New |
|
|
SYSTEM_SECURITY_MANAGEMENT |
SSM_CONTRACT_UNIT_AVAIL |
SSM_CONTRACT_UNIT_AVAIL |
SSM,CONTRACT_UNIT_AVAIL,1 |
New |
|
SSM_INSTRUCTION |
SSM_INSTRUCTION |
SSM,INSTRUCTION,1 |
New |
|
|
SSM_SCHEDULE |
NEXT_DAY_DAILY_SCHEDULE |
SSM,SCHEDULE,1 |
New |
|
|
SSM_SCHEDULED_AVAILABILITY |
NEXT_DAY_SCHEDULED_AVAILABILITY |
SSM,SCHEDULED_AVAILABILITY,1 |
New |
|
|
SSM_ENABLEMENT_PERIOD |
NEXT_DAY_ENABLEMENT_PERIOD |
SSM,ENABLEMENT_PERIOD,1 |
New |
|
|
SSM_ENABLEMENT_COSTS |
NEXT_DAY_ENABLEMENT_COSTS |
SSM,ENABLEMENT_COSTS,1 |
New |
4.15 Discontinued reports
|
Data model table |
File ID |
Delivered in file |
CSV report type |
Replaced by |
Reason |
|
BILLING_DIRECTION_RECONCILIATN |
BILLING, BILLING_LEGACY |
|
|
|
Moved to HISTORICAL package. |
|
BILLINGCPDATA |
BILLING |
|
|
BILLING_ENERGY_TRANSACTIONS |
Moved to HISTORICAL package. Table comments updated to reflect this change. |
|
BILLINGGENDATA |
BILLING |
|
|
BILLING_ENERGY_GENSET_DETAIL |
Moved to HISTORICAL package. Table comments updated to reflect this change. |
|
DISPATCHLOAD |
NEXT_DAY_DISPATCH |
*_NEXT_DAY_DISPATCH_*.CSV |
DISPATCH |
NEXT_DAY_DISPATCH, DISPATCHLOAD,6 |
Modified table |
|
DISPATCHREGIONSUM |
DISPATCHIS |
*_DISPATCHIS_*.CSV
|
DISPATCH |
DISPATCHIS, DISPATCHREGIONSUM,10 |
Modified table |
|
P5MIN_REGIONSOLUTION |
P5MIN |
*_P5MIN_*.CSV |
P5MIN |
P5MIN, P5MIN_REGIONSOLUTION, 11 |
Modified table |
|
PREDISPATCHLOAD |
NEXT_DAY_PREDISPATCH_D |
*_NEXT_DAY_PREDISPATCH_D_*.CSV |
PREDISPATCH |
NEXT_DAY_PREDISPATCH_D, PREDISPATCHLOAD,5 |
Modified table |
|
PREDISPATCHREGIONSUM |
PREDISPATCHIS |
*_PREDISPATCHIS_*.CSV
|
PREDISPATCH |
PREDISPATCHIS, DISPATCHREGIONSUM,10 |
Modified table |
|
RESERVE |
RESERVETRK |
|
|
|
Moved to HISTORICAL package. |
|
SET_RUN_PARAMETER |
SETTLEMENTS |
|
|
|
Moved to HISTORICAL package. |
|
SETCPDATA |
SETTLEMENTS |
|
|
SET_ENERGY_TRANSACTIONS and SET_ENERGY_GENSET_DETAIL |
Moved to HISTORICAL package. Table comments updated to reflect this change. |
|
SETGENDATA |
SETTLEMENTS |
|
|
SET_ENERGY_TRANSACTIONS and SET_ENERGY_GENSET_DETAIL |
Moved to HISTORICAL package. Table comments updated to reflect this change. |
|
SETSMALLGENDATA |
SETTLEMENTS |
|
|
SET_ENERGY_TRANSACTIONS and SET_ENERGY_GENSET_DETAIL |
Moved to HISTORICAL package. Table comments updated to reflect this change. |
|
SETCPDATAREGION |
SETTLEMENTS |
|
|
SET_ENERGY_REGION_SUMMARY |
Moved to HISTORICAL package. Table comments updated to reflect this change. |
|
SETGENDATAREGION |
SETTLEMENTS |
|
|
SET_ENERGY_REGION_SUMMARY |
Moved to HISTORICAL package. Table comments updated to reflect this change. |
4.16 Non-functional changes
-
Table 1 Table 1 MMS Data Model 5.6 non-functional changes
|
MMS Data Model table |
Change detail |
|
None |
|