FPP_FORECAST_DEFAULT_CF
This report delivers the forecast default contribution factors (DCF) effective for a billing period (aligned to the settlement week).
Package
FPP
Visibility
Public
Table schema
| Column |
Official MMS Datatype |
GR-MMS Datatype |
Comment |
| FPP_UNITID |
varchar(20)  |
varchar(20) |
FPP Unit ID (registered DUID/ TNI) |
| CONSTRAINTID |
varchar(20) |
varchar(20) |
Constraint ID (binding constraint ID from FCAS data used in FPP calculations) |
| EFFECTIVE_START_DATETIME |
datetime(3) |
datetime2(0) |
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 |
datetime(3) |
datetime2(0) |
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 |
numeric(10, 0) |
smallint |
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 |
varchar(10) |
varchar(10) |
Bid type (the bid type saved in relation to constraint ID from FCAS data used in FPP calculations) |
| REGIONID |
varchar(20) |
varchar(10) |
Region ID of the frequency deviation / frequency measure |
| DEFAULT_CONTRIBUTION_FACTOR |
numeric(18, 8) |
numeric(18, 8) |
Calculated default contribution factor from the historical performance period. For further details please see the FPP procedure document. |
| DCF_REASON_FLAG |
numeric(5, 0) |
tinyint |
The reason flag showing the decision matrix for the default contribution factor (DCF) |
| DCF_ABS_NEGATIVE_PERF_TOTAL |
numeric(18, 8) |
numeric(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 |
varchar(50) |
varchar(50) |
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. |
Official MMS data model indexes
| Index name |
Index type |
Index columns (in order) |
| FPP_FORECAST_DEFAULT_CF_PK |
clustered, unique, primary key |
FPP_UNITID, CONSTRAINTID, EFFECTIVE_START_DATETIME, EFFECTIVE_END_DATETIME, VERSIONNO |
GR-MMS data model indexes
| Index name |
Index type |
Index columns (in order) |
| PK_FPP_FORECAST_DEFAULT_CF |
clustered, unique, primary key |
FPP_UNITID, CONSTRAINTID, EFFECTIVE_START_DATETIME, EFFECTIVE_END_DATETIME, VERSIONNO |
Historical-MMS data model indexes
| Index name |
Index type |
Index columns (in order) |
| PK_FPP_FORECAST_DEFAULT_CF |
clustered, unique, primary key |
FPP_UNITID, CONSTRAINTID, EFFECTIVE_START_DATETIME, EFFECTIVE_END_DATETIME, VERSIONNO |