|
Name |
|
|
Comment |
This report delivers the weighted 4 second frequency measure data for each constraint |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
MEASUREMENT_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
MEASUREMENT_DATETIME |
DATE |
X |
Date and time of the SCADA data (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
FM_RAISE_HZ |
NUMBER(18,8) |
|
Calculated 4 second Frequency Measure in Hz for that constraint from the FPP database. Frequency Measure data is split across these two raise and lower columns in the following ways: >0 = Allocated to the FM_RAISE_HZ column <0 = Allocated to the FM_LOWER_HZ column 0 = To fill any gaps where the alternative column is not applicable (or no deviation from 50 Hz) |
|
FM_LOWER_HZ |
NUMBER(18,8) |
|
Calculated 4 second Frequency Measure in Hz for that constraint from the FPP database. Frequency Measure data is split across these two raise and lower columns in the following ways: >0 = Allocated to the FM_RAISE_HZ column <0 = Allocated to the FM_LOWER_HZ column 0 = To fill any gaps where the alternative column is not applicable (or no deviation from 50 Hz) |
|
USED_IN_RCR_FLAG |
NUMBER(5) |
|
Flag to indicate the result of the Frequency Measure alignment check between Mainland and Tasmania for global constraints. Supported values are: 0 = Not used in RCR calculation as the signs for the frequency measures between Mainland and Tasmania do not align 1 = Used in the RCR calculation as the signs for the frequency measures between Mainland and Tasmania do align in the case of global constraints. For non-global constraints this flag is set to 1 |
|
CORRELATION_FLAG |
NUMBER(5) |
|
Flag to indicate the result of the Frequency Measure correlation check between regions in the same constraint. Supported values are: 0 = Frequency measures in this constraint are not correlated (e.g. system separation between two regions) 1 = Frequency measures in this constraint are correlated |
|
Name |
|
|
Comment |
This report delivers the calculated contribution factor value for each 5 minute trading interval for each constraint and FPP unit |
|
Name |
Comment |
Value |
|
Visibility |
|
Private & Public Next-Day |
|
Name |
|
CONSTRAINTID |
|
FPP_UNITID |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
FPP_UNITID |
VARCHAR2(20) |
X |
FPP Unit ID (registered DUID/ TNI) |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
CONTRIBUTION_FACTOR |
NUMBER(18,8) |
|
Contribution Factor (the calculated contribution factor for the FPP unit and constraint ID for that trading interval) - for further details please see the FPP procedure document |
|
NEGATIVE_CONTRIBUTION_FACTOR |
NUMBER(18,8) |
|
Negative Contribution Factor (the calculated negative contribution factor for the FPP unit and constraint ID for that trading interval) - for further details please see the FPP procedure document |
|
DEFAULT_CONTRIBUTION_FACTOR |
NUMBER(18,8) |
|
The Default Contribution Factor (the calculated default contribution factor based on historical performance for the FPP unit and constraint ID for that trading interval) that is effective for this trading interval, which joins back to FPP_FORECAST_DEFAULT_CF - for further details please see the FPP procedure document |
|
CF_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the contribution factor (CF) Supported values are: 0 = CF is calculated based on good input data 1 = CF is 0 because it is not primary in the group 2 = CF is not for the DUID but for the whole group 4 = CF is calculated based on substitute performance 8 = CF is 0 because FM is unreliable. 16 = CF is 0 because more than 50 percent input is bad or not available. |
|
CF_ABS_POSITIVE_PERF_TOTAL |
NUMBER(18,8) |
|
The sum of absolute positive performance in MWHz for the combination of constraint / bid type (raise or lower). This is used as the denominator in normalising contribution factors (CF) where a units performance is positive. For further details please see the FPP procedure document. >0 = Performance was calculated for the units NULL = Performance for the units was unavailable |
|
CF_ABS_NEGATIVE_PERF_TOTAL |
NUMBER(18,8) |
|
The sum of absolute negative performance in MWHz for the combination of constraint / bid type (raise or lower). This is used as the denominator in normalising contribution factors (CF) where a units performance is negative. For further details please see the FPP procedure document. >0 = Performance was calculated for the units NULL = Performance for the units was unavailable |
|
NCF_ABS_NEGATIVE_PERF_TOTAL |
NUMBER(18,8) |
|
The sum of absolute negative performance in MWHz for the combination of constraint / bid type (raise or lower). This is used as the denominator in normalising negative contribution factors (NCF). For further details please see the FPP procedure document. >0 = Performance was calculated for the units NULL = Performance for the units was unavailable 0 = When NCF is zero (i.e. CF is positive), then this total will be represented as zero |
|
PARTICIPANTID |
VARCHAR2(20) |
|
Participant ID |
|
SETTLEMENTS_UNITID |
VARCHAR2(20) |
|
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. |
|
Name |
|
|
Comment |
This report delivers the estimated cost for each FPP unit for each constraint for each 5 minute trading interval |
|
Name |
Comment |
Value |
|
Visibility |
|
Private |
|
Name |
|
CONSTRAINTID |
|
FPP_UNITID |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
FPP_UNITID |
VARCHAR2(20) |
X |
FPP Unit ID (registered DUID / TNI) |
|
VERSIONNO |
NUMBER(10) |
X |
The version number. In most cases this version will be the FPP run number from the FPP database, however there are some cases (like a new pricing run of the constraint FCAS processor received by the FPP system) where the version number listed here will be the financial estimate run number from the FPP database (this number is a different sequence from the FPP run number because there is no recalculation of performance or contribution, just changes to pricing / p regulation hence only the financial estimation is performed). |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RELEVANT_REGIONS |
VARCHAR2(200) |
|
Relevant regions (a comma separated list of the relevant regions for the constraint from FCAS data) |
|
FPP |
NUMBER(18,8) |
|
FPP in AUD (the financial estimate of frequency performance payment calculated for the constraint / bid type / unit). This value can be either positive (credit) or negative (debit). For details on the calculation, please see FPP procedure and supporting documentation. |
|
USED_FCAS |
NUMBER(18,8) |
|
Used recovery FCAS in AUD (the financial estimate of the recovery of used FCAS calculated for the constraint / bid type / unit). 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. |
|
UNUSED_FCAS |
NUMBER(18,8) |
|
Unused recovery FCAS in AUD (the financial estimate of the recovery of unused FCAS calculated for the constraint / bid type / unit). 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. |
|
PARTICIPANTID |
VARCHAR2(20) |
|
Participant ID |
|
Name |
|
|
Comment |
This report delivers the estimated performance cost rate for each constraint for each 5 minute trading interval |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(10) |
X |
The version number. In most cases this version will be the FPP run number from the FPP database, however there are some cases (like a new pricing run of the constraint FCAS processor received by the FPP system) where the version number listed here will be the financial estimate run number from the FPP database (this number is a different sequence from the FPP run number because there is no recalculation of performance or contribution, just changes to pricing / p regulation hence only the financial estimation is performed). |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RELEVANT_REGIONS |
VARCHAR2(200) |
|
Relevant regions (a comma separated list of the relevant regions for the constraint from FCAS data) |
|
FPP_PAYMENT_RATE |
NUMBER(18,8) |
|
The payment rate for FPP in AUD / MWHz (the denominator used is the sum of positive performance for the constraint calculated by contribution factor calculation). This value will be either 0 (nil), or a positive value (credit) only. For details on the calculation, please see FPP procedure and supporting documentation. |
|
FPP_RECOVERY_RATE |
NUMBER(18,8) |
|
The recovery rate for FPP in AUD / MWHz (the denominator used is the absolute sum of negative performance for the constraint calculated by the contribution factor calculation). 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. |
|
USED_FCAS_RATE |
NUMBER(18,8) |
|
The rate for used FCAS in AUD / MWHz (the denominator used is the absolute sum of negative performance for the constraint calculated by the negative contribution factor calculation). 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. |
|
UNUSED_FCAS_RATE |
NUMBER(18,8) |
|
The rate for unused FCAS in AUD / MWHz (the denominator used is the absolute sum of negative performance for the constraint calculated by the default contribution factor calculation). 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. |
|
Name |
|
|
Comment |
This report delivers the estimated residual cost rate for each constraint for each 5 minute trading interval |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(10) |
X |
The version number. In most cases this version will be the FPP run number from the FPP database, however there are some cases (like a new pricing run of the constraint FCAS processor received by the FPP system) where the version number listed here will be the financial estimate run number from the FPP database (this number is a different sequence from the FPP run number because there is no recalculation of performance or contribution, just changes to pricing / p regulation hence only the financial estimation is performed). |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RELEVANT_REGIONS |
VARCHAR2(200) |
|
Relevant regions (a comma separated list of the relevant regions for the constraint from FCAS data) |
|
FPP |
NUMBER(18,8) |
|
FPP in AUD/MWh (the financial estimate of frequency performance payment calculated). This value can be either positive (credit) or negative (debit). For details on the calculation, please see FPP procedure and supporting documentation. |
|
USED_FCAS |
NUMBER(18,8) |
|
Used recovery FCAS in AUD/MWh (the financial estimate of the recovery of used FCAS calculated). 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. |
|
UNUSED_FCAS |
NUMBER(18,8) |
|
Unused recovery FCAS in AUD/MWh (the financial estimate of the recovery of unused FCAS calculated). 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. |
|
Name |
|
|
Comment |
This report delivers a summary of FCAS requirements as used by the FPP calculation (i.e. only RAISEREG / LOWERREG bid types) |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
RUN_DATETIME |
|
RUNNO |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
RUN_DATETIME |
DATE |
X |
The run date and time of the dispatch case that was the trigger for the constraint FCAS processor execution |
|
RUNNO |
NUMBER(5) |
X |
The dispatch case run number that was the trigger for the constraint FCAS processor execution |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(10) |
X |
The version number. In most cases this version will be the FPP run number from the FPP database, however there are some cases (like a new pricing run of the constraint FCAS processor received by the FPP system) where the version number listed here will be the financial estimate run number from the FPP database (this number is a different sequence from the FPP run number because there is no recalculation of performance or contribution, just changes to pricing / p regulation hence only the financial estimation is performed). |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations, i.e. RAISEREG or LOWERREG) |
|
RELEVANT_REGIONS |
VARCHAR2(200) |
|
Relevant regions (a comma separated list of the relevant regions for the constraint from FCAS data) |
|
REGULATION_MW |
NUMBER(18,8) |
|
Enabled regulation MW used in the FPP calculation (from FPP database) |
|
CONSTRAINT_MARGINAL_VALUE |
NUMBER(18,8) |
|
Marginal value in AUD/MW per hour related to the constraint (from FCAS data used for FPP calculations) |
|
P_REGULATION |
NUMBER(18,8) |
|
P regulation value in AUD/MW per hour related to the constraint (from FCAS data used for FPP calculations also known as adjusted marginal value) |
|
BASE_COST |
NUMBER(18,8) |
|
Base cost in AUD related to the constraint (from FCAS data used for FPP calculations) |
|
TSFCAS |
NUMBER(18,8) |
|
TSFCAS in AUD related to the constraint (FCAS recovery amount related to the constraint also known as adjusted cost) |
|
TOTAL_FPP |
NUMBER(18,8) |
|
Total amount of FPP in AUD changing hands related to the constraint (note that this is not the sum of FPP) |
|
RCR |
NUMBER(18,5) |
|
RCR MW (the calculated requirement for corrective response from FPP database). Note that this is a join back to the FPP_RCR table. |
|
USAGE |
NUMBER(18,8) |
|
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. |
|
Name |
|
|
Comment |
This report delivers the forecast default contribution factors (DCF) effective for a billing period (aligned to the settlement week) |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
EFFECTIVE_END_DATETIME |
|
EFFECTIVE_START_DATETIME |
|
FPP_UNITID |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
FPP_UNITID |
VARCHAR2(20) |
X |
FPP Unit ID (registered DUID/ TNI) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
EFFECTIVE_START_DATETIME |
DATE |
X |
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 default contribution factor related to the combination of FPP unit ID / constraint. This is the billing period over which these default contribution factors will be effective / applied. In most cases this will align to the settlement week, however there are some cases (like a new constraint) where the effective start date will be prorated to align with the change. |
|
EFFECTIVE_END_DATETIME |
DATE |
X |
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 default contribution factor related to the combination of FPP unit ID / constraint. This is the billing period over which these default contribution factors will be effective / applied. Effective end date will align with the end of a settlement week. |
|
VERSIONNO |
NUMBER(10) |
X |
The version number. In most cases this version will be the historical performance calculation run number from the FPP database (which is different from the FPP run number), however there are some cases (like a new constraint) where the version number listed here will be the FPP run number from the FPP database (this will be where the effective start date time will be prorated to align with the detection of this change). |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
REGIONID |
VARCHAR2(20) |
|
Region ID of the frequency deviation / frequency measure |
|
DEFAULT_CONTRIBUTION_FACTOR |
NUMBER(18,8) |
|
Calculated default contribution factor from the historical performance period. For further details please see the FPP procedure document. |
|
DCF_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the default contribution factor (DCF) |
|
DCF_ABS_NEGATIVE_PERF_TOTAL |
NUMBER(18,8) |
|
The sum of absolute negative performance in MWHz for the combination of constraint (raise or lower). This is used as the denominator in normalising default contribution factors (DCF) as the historical performance is always negative for DCF. For further details please see the FPP procedure document. >0 = Performance was calculated for the units NULL = Performance for the units was unavailable |
|
SETTLEMENTS_UNITID |
VARCHAR2(20) |
|
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. |
|
Name |
|
|
Comment |
This report delivers the forecast residual default contribution factors (DCF) effective for a billing period (aligned to the settlement week) |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
EFFECTIVE_END_DATETIME |
|
EFFECTIVE_START_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
EFFECTIVE_START_DATETIME |
DATE |
X |
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 residual default contribution factor related to the constraint. This is the billing period over which these default contribution factors will be effective / applied. In most cases this will align to the settlement week, however there are some cases (like a new constraint) where the effective start date will be prorated to align with the change. |
|
EFFECTIVE_END_DATETIME |
DATE |
X |
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 residual default contribution factor related to the constraint. This is the billing period over which these default contribution factors will be effective / applied. Effective end date will align with the end of a settlement week. |
|
VERSIONNO |
NUMBER(10) |
X |
The version number. In most cases this version will be the historical performance calculation run number from the FPP database (which is different from the FPP run number), however there are some cases (like a new constraint) where the version number listed here will be the FPP run number from the FPP database (this will be where the effective start date time will be prorated to align with the detection of this change). |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RESIDUAL_DCF |
NUMBER(18,8) |
|
Calculated residual default contribution factor from the historical performance period. For further details please see the FPP procedure document. |
|
RESIDUAL_DCF_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the residual default contribution factor (DCF) |
|
DCF_ABS_NEGATIVE_PERF_TOTAL |
NUMBER(18,8) |
|
The sum of absolute negative performance in MWHz for the combination of constraint (raise or lower). This is used as the denominator in normalising default contribution factors (DCF). For further details please see the FPP procedure document. >0 = Performance was calculated for the units NULL = Performance for the units was unavailable |
|
Name |
|
|
Comment |
This report delivers the historical performance calculated based on a historical period and effective for a billing period (aligned to the settlement week) |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
EFFECTIVE_END_DATETIME |
|
EFFECTIVE_START_DATETIME |
|
FPP_UNITID |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
FPP_UNITID |
VARCHAR2(20) |
X |
FPP Unit ID (registered DUID/ TNI) |
|
EFFECTIVE_START_DATETIME |
DATE |
X |
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 FPP unit 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 |
X |
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 FPP unit 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) |
X |
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 |
|
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 FPP unit 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 |
|
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 FPP unit 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) |
|
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) |
|
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) |
|
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) |
|
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 |
|
Name |
|
|
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. |
|
Name |
Comment |
Value |
|
Visibility |
|
Private |
|
Name |
|
CONSTRAINTID |
|
FPP_UNITID |
|
INTERVAL_DATETIME |
|
RUN_DATETIME |
|
RUNNO |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
RUN_DATETIME |
DATE |
X |
The run date and time of the 5 minute predispatch case that was the trigger for the constraint FCAS processor execution (as the FCAS requirement data is the basis of these forward estimates) |
|
RUNNO |
NUMBER(5) |
X |
The 5 minute predispatch case run number that was the trigger for the constraint FCAS processor execution (as the FCAS requirement data is the basis for these forward estimates) |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
FPP_UNITID |
VARCHAR2(20) |
X |
FPP Unit ID (registered DUID / TNI) |
|
VERSIONNO |
NUMBER(5) |
X |
The version number of the effective default contribution factor for the unit / constraint combination taken from the FPP_FORECAST_DEFAULT_CF table |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RELEVANT_REGIONS |
VARCHAR2(200) |
|
Relevant regions (a comma separated list of the relevant regions for the constraint from FCAS data) |
|
EST_UNUSED_FCAS |
NUMBER(18,8) |
|
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. |
|
PARTICIPANTID |
VARCHAR2(20) |
|
Participant ID |
|
Name |
|
|
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. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
RUN_DATETIME |
|
RUNNO |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
RUN_DATETIME |
DATE |
X |
The run date and time of the 5 minute predispatch case that was the trigger for the constraint FCAS processor execution (as the FCAS requirement data is the basis of these forward estimates) |
|
RUNNO |
NUMBER(5) |
X |
The 5 minute predispatch case run number that was the trigger for the constraint FCAS processor execution (as the FCAS requirement data is the basis for these forward estimates) |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(5) |
X |
The version number of the effective default contribution factor for the unit / constraint combination taken from the FPP_FORECAST_DEFAULT_CF table |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RELEVANT_REGIONS |
VARCHAR2(200) |
|
Relevant regions (a comma separated list of the relevant regions for the constraint from FCAS data) |
|
EST_UNUSED_FCAS |
NUMBER(18,8) |
|
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. |
|
Name |
|
|
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. |
|
Name |
Comment |
Value |
|
Visibility |
|
Private |
|
Name |
|
CONSTRAINTID |
|
FPP_UNITID |
|
INTERVAL_DATETIME |
|
PREDISPATCHSEQNO |
|
RUN_DATETIME |
|
RUNNO |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
X |
Predispatch sequence number for the 30 minute predispatch case that triggers the constraint FCAS processor run |
|
RUN_DATETIME |
DATE |
X |
The run date and time of the 30 minute predispatch case that was the trigger for the constraint FCAS processor execution (as the FCAS requirement data is the basis of these forward estimates) |
|
RUNNO |
NUMBER(5) |
X |
The 30 minute predispatch case run number that was the trigger for the constraint FCAS processor execution (as the FCAS requirement data is the basis for these forward estimates) |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the 30 minute predispatch interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
FPP_UNITID |
VARCHAR2(20) |
X |
FPP Unit ID (registered DUID / TNI) |
|
VERSIONNO |
NUMBER(5) |
X |
The version number of the effective default contribution factor for the unit / constraint combination taken from the FPP_FORECAST_DEFAULT_CF table |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RELEVANT_REGIONS |
VARCHAR2(200) |
|
Relevant regions (a comma separated list of the relevant regions for the constraint from FCAS data) |
|
EST_UNUSED_FCAS |
NUMBER(18,8) |
|
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. |
|
PARTICIPANTID |
VARCHAR2(20) |
|
Participant ID |
|
Name |
|
|
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. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
PREDISPATCHSEQNO |
|
RUN_DATETIME |
|
RUNNO |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
X |
Predispatch sequence number for the 30 minute predispatch case that triggers the constraint FCAS processor run |
|
RUN_DATETIME |
DATE |
X |
The run date and time of the 30 minute predispatch case that was the trigger for the constraint FCAS processor execution (as the FCAS requirement data is the basis of these forward estimates) |
|
RUNNO |
NUMBER(5) |
X |
The 30 minute predispatch case run number that was the trigger for the constraint FCAS processor execution (as the FCAS requirement data is the basis for these forward estimates) |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the 30 minute predispatch interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(5) |
X |
The version number of the effective default contribution factor for the unit / constraint combination taken from the FPP_FORECAST_DEFAULT_CF table |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RELEVANT_REGIONS |
VARCHAR2(200) |
|
Relevant regions (a comma separated list of the relevant regions for the constraint from FCAS data) |
|
EST_UNUSED_FCAS |
NUMBER(18,8) |
|
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. |
|
Name |
|
|
Comment |
This report delivers the calculated performance value for each 5 minute trading interval for each FPP unit |
|
Name |
Comment |
Value |
|
Visibility |
|
Private & Public Next-Day |
|
Name |
|
FPP_UNITID |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
FPP_UNITID |
VARCHAR2(20) |
X |
FPP Unit ID (registered DUID/ TNI) |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
RAISE_PERFORMANCE |
NUMBER(18,5) |
|
Raise performance value in MWHz units (calculated by FPP for that trading interval taken from FPP database) |
|
RAISE_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the raise performance value Supported values are: 0 = Performance is calculated based on good input data 1 = Performance is Null as unit is a Non Primary DUID in the group 2 = Performance against the Primary DUID representing the group 4 = Performance is Null as Input data is bad or unavailable 8 = Performance is Null as FM is unreliable 12 = Performance is Null as Input data is bad or unavailable and FM is unreliable 6 = Performance against the Primary DUID representing the group is Null as Input data is bad or unavailable 10 = Performance against the Primary DUID representing the group is Null as FM is unreliable 14 = Performance against the Primary DUID representing the group is Null as Input data is bad or unavailable and FM is unreliable |
|
LOWER_PERFORMANCE |
NUMBER(18,5) |
|
Lower performance value in MWHz units (calculated by FPP for that trading interval taken from FPP database) |
|
LOWER_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the lower performance value Supported values are: 0 = Performance is calculated based on good input data 1 = Performance is Null as unit is a Non Primary DUID in the group 2 = Performance against the Primary DUID representing the group 4 = Performance is Null as Input data is bad or unavailable 8 = Performance is Null as FM is unreliable 12 = Performance is Null as Input data is bad or unavailable and FM is unreliable 6 = Performance against the Primary DUID representing the group is Null as Input data is bad or unavailable 10 = Performance against the Primary DUID representing the group is Null as FM is unreliable 14 = Performance against the Primary DUID representing the group is Null as Input data is bad or unavailable and FM is unreliable |
|
PARTICIPANTID |
VARCHAR2(20) |
|
Participant ID |
|
Name |
|
|
Comment |
This report delivers the calculated RCR for each constraint for each 5 minute trading interval |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RCR |
NUMBER(18,5) |
|
RCR (the calculated requirement for corrective response from FPP database) |
|
RCR_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the requirement for corrective response (RCR) calculation Supported values are: 0 = RCR is calculated based on good input data 1 = RCR is 0 as FM is unreliable 2 = RCR is 0 as the percentage of units with unavailable input or bad data is greater than the threshold percentage |
|
Name |
|
|
Comment |
This report delivers the curated 4 second frequency deviation and frequency measure data for each region |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
INTERVAL_DATETIME |
|
MEASUREMENT_DATETIME |
|
REGIONID |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
MEASUREMENT_DATETIME |
DATE |
X |
Date and time of the SCADA data (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
REGIONID |
VARCHAR2(20) |
X |
Region ID of the frequency deviation / frequency measure |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
FREQ_DEVIATION_HZ |
NUMBER(18,8) |
|
Frequency Deviation (4 second frequency deviation in Hz for that region) |
|
HZ_QUALITY_FLAG |
NUMBER(5) |
|
Frequency Quality (4 second frequency deviation quality for that region) Supported values are: 0 = Bad Quality 1 = Good Quality 2 = Suspect Quality |
|
FREQ_MEASURE_HZ |
NUMBER(18,8) |
|
Calculated 4 second Frequency Measure for that region from FPP database |
|
FM_ALIGNMENT_FLAG |
NUMBER(5) |
|
Alignment Flag (4 second frequency deviation is aligned with 4 second frequency measure for that region) Supported values are: 0 = Misaligned 1 = Aligned |
|
Name |
|
|
Comment |
This report delivers the calculated residual contribution factor value for each 5 minute trading interval for each constraint |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
RESIDUAL_CF |
NUMBER(18,8) |
|
Residual Contribution Factor (the calculated residual contribution factor for the constraint ID for that trading interval) - for further details please see the FPP procedure document |
|
NEGATIVE_RESIDUAL_CF |
NUMBER(18,8) |
|
Negative Residual Contribution Factor (the calculated negative residual contribution factor for the constraint ID for that trading interval) - for further details please see the FPP procedure document |
|
RESIDUAL_DCF |
NUMBER(18,8) |
|
The Residual Default Contribution Factor (the calculated residual default contribution factor based on historical performance for the constraint ID for that trading interval) that is effective for this trading interval, which joins back to FPP_FORECAST_RESIDUAL_DCF - for further details please see the FPP procedure document |
|
RESIDUAL_CF_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the residual contribution factor (CF) Supported values are: 0 = CF is calculated based on good input data 8 = CF is 0 because FM is unreliable. 16 = CF is 0 because more than 50 percent input is bad or not available. |
|
CF_ABS_POSITIVE_PERF_TOTAL |
NUMBER(18,8) |
|
The sum of absolute positive performance in MWHz for the combination of constraint / bid type (raise or lower). This is used as the denominator in normalising contribution factors (CF) where a units performance is positive. For further details please see the FPP procedure document. >0 = Performance was calculated for the units NULL = Performance for the units was unavailable |
|
CF_ABS_NEGATIVE_PERF_TOTAL |
NUMBER(18,8) |
|
The sum of absolute negative performance in MWHz for the combination of constraint / bid type (raise or lower). This is used as the denominator in normalising contribution factors (CF) where a units performance is negative. For further details please see the FPP procedure document. >0 = Performance was calculated for the units NULL = Performance for the units was unavailable |
|
NCF_ABS_NEGATIVE_PERF_TOTAL |
NUMBER(18,8) |
|
The sum of absolute negative performance in MWHz for the combination of constraint / bid type (raise or lower). This is used as the denominator in normalising negative contribution factors (NCF). For further details please see the FPP procedure document. >0 = Performance was calculated for the units NULL = Performance for the units was unavailable 0 = When NCF is zero (i.e. CF is positive), then this total will be represented as zero |
|
Name |
|
|
Comment |
This report delivers the calculated residual performance value for each 5 minute trading interval |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
INTERVAL_DATETIME |
|
REGIONID |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
REGIONID |
VARCHAR2(20) |
X |
Region ID of the residual performance |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
RAISE_PERFORMANCE |
NUMBER(18,5) |
|
Raise performance value in MWHz units (calculated by FPP for that trading interval taken from FPP database) |
|
RAISE_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the raise performance value Supported values are: 0 = Performance is calculated based on good input data 4 = Performance is Null as Input data is bad or unavailable 8 = Performance is Null as FM is unreliable 12 = Performance is Null as Input data is bad or unavailable and FM is unreliable |
|
LOWER_PERFORMANCE |
NUMBER(18,5) |
|
Lower performance value in MWHz units (calculated by FPP for that trading interval taken from FPP database) |
|
LOWER_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the lower performance value Supported values are: 0 = Performance is calculated based on good input data 4 = Performance is Null as Input data is bad or unavailable 8 = Performance is Null as FM is unreliable 12 = Performance is Null as Input data is bad or unavailable and FM is unreliable |
|
Name |
|
|
Comment |
This report delivers details of the 5-minute FPP calculation engine success failure outcome saved in FPP database |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
FPPRUN_DATETIME |
DATE |
|
Completion time of the FPP calculation run (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
RUN_STATUS |
VARCHAR2(20) |
|
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
AUTHORISED_DATETIME |
DATE |
|
Date and time of the authorisation of this FPP calculation run (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) - Note may be delayed in cases of ex-post calculation runs |
|
Name |
|
|
Comment |
This report delivers the curated 4 second measurement MW data for each FPP unit |
|
Name |
Comment |
Value |
|
Visibility |
|
Private & Public Next-Day |
|
Name |
|
FPP_UNITID |
|
INTERVAL_DATETIME |
|
MEASUREMENT_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
MEASUREMENT_DATETIME |
DATE |
X |
Date and time of the SCADA data (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
FPP_UNITID |
VARCHAR2(20) |
X |
FPP Unit ID (registered DUID/TNI) |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
MEASURED_MW |
NUMBER(18,8) |
|
Measured MW (4 second SCADA measurement in MW) |
|
MW_QUALITY_FLAG |
NUMBER(5) |
|
MW Quality (4 second SCADA measurement Quality) Supported values are: 0 = Bad Quality 1 = Good Quality 2 = Suspect Quality |
|
SCHEDULED_MW |
NUMBER(18,5) |
|
Scheduled MW (reference trajectory value from FPP calculation process) |
|
DEVIATION_MW |
NUMBER(18,5) |
|
Unit Deviation (output of the FPP calculation process) |
|
PARTICIPANTID |
VARCHAR2(20) |
|
Participant ID |
|
Name |
|
|
Comment |
This report delivers the calculated usage for each constraint for each 5 minute trading interval |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
VERSIONNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
INTERVAL_DATETIME |
DATE |
X |
Date and time of the trading interval (DD/MM/YYYY HH24:MI:SS) fixed to the UTC+10 time zone (NEM time) |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
|
VERSIONNO |
NUMBER(5) |
X |
Version (FPP run number from the FPP database) |
|
BIDTYPE |
VARCHAR2(10) |
|
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
|
REGULATION_MW |
NUMBER(18,8) |
|
Enabled regulation MW used in the FPP calculation (from FPP database) |
|
USED_MW |
NUMBER(18,8) |
|
Maximum used regulation MW value (quantity of regulation FCAS that was calculated to be used in MW) |
|
USAGE |
NUMBER(18,8) |
|
Usage (calculation of the proportion of regulation FCAS that was calculated to be used) |
|
USAGE_REASON_FLAG |
NUMBER(5) |
|
The reason flag showing the decision matrix for the requirement for corrective response (RCR) calculation Supported values are: 0 = Usage is calculated based on good input data 1 = Usage is 0 as FM is unreliable 2 = Usage is 0 as the percentage of units with unavailable input or bad data is greater than the threshold percentage |
|
|
|