|
Name |
|
|
Comment |
The constraint level FCAS cost / price details for constraint FCAS processor runs. This enhanced output table format is established for the constraint FCAS processor release required for the Frequency Performance Payments (FPP) release. This enhanced output is hierarchical in nature, with the parent *_FCAS_REQ_RUN table holding the details about the triggering case run and time, and the child *_FCAS_REQ_CONSTRAINT table holding the constraint level details of FCAS costs / prices. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
BIDTYPE |
|
CONSTRAINTID |
|
INTERVAL_DATETIME |
|
PREDISPATCHSEQNO |
|
REGIONID |
|
RUN_DATETIME |
|
RUNNO |
|
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 triggers the constraint FCAS processor run |
|
RUNNO |
NUMBER(5) |
X |
The 30 minute predispatch case run number that has triggers the constraint FCAS processor run |
|
INTERVAL_DATETIME |
DATE |
X |
The 30 minute interval date and time of the 30 minute predispatch interval that was processed by the constraint FCAS processor |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
ConstraintID join to table GenConData |
|
REGIONID |
VARCHAR2(20) |
X |
Region identifier |
|
BIDTYPE |
VARCHAR2(10) |
X |
DUID offered type |
|
LHS |
NUMBER(15,5) |
|
Constraints summed LHS - aggregate LHS Solution values from the physical run from the PREDISPATCHCONSTRAINT table |
|
RHS |
NUMBER(15,5) |
|
Constraints RHS value used in the solution - may be either dynamic (calculated) or static from the physical run from the PREDISPATCHCONSTRAINT table |
|
MARGINALVALUE |
NUMBER(15,5) |
|
Shadow price of constraint from the PREDISPATCHCONSTRAINT table from the physical run. |
|
RRP |
NUMBER(15,5) |
|
Bid type prices for the region coming from the pricing run of the PREDISPATCHREGIONSUM table |
|
REGIONAL_ENABLEMENT |
NUMBER(15,5) |
|
The dispatched MW for the bid type inside the region from the physical run of the PREDISPATCHREGIONSUM table |
|
CONSTRAINT_ENABLEMENT |
NUMBER(15,5) |
|
MW enabled for this bid type within the constraint |
|
REGION_BASE_COST |
NUMBER(18,8) |
|
The regional payment allocated to the constraint for the interval pro-rated based on marginal value ratios over the binding constraints for that service in that region (this is an intermediate calculation to get to the base cost) |
|
BASE_COST |
NUMBER(18,8) |
|
The base cost of the constraint, before the regulation/contingency split |
|
ADJUSTED_COST |
NUMBER(18,8) |
|
The adjusted cost of the constraint for this service, after the regulation/contingency split |
|
P_REGULATION |
NUMBER(18,8) |
|
The adjusted marginal value of the constraint for FPP recovery (blank for constraints without REG terms) |
|
Name |
|
|
Comment |
The constraint FCAS processor run details. This enhanced output table format is established for the constraint FCAS processor release required for the Frequency Performance Payments (FPP) release. This enhanced output is hierarchical in nature, with the parent *_FCAS_REQ_RUN table holding the details about the triggering case run and time, and the child *_FCAS_REQ_CONSTRAINT table holding the constraint level details of FCAS costs / prices. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
PREDISPATCHSEQNO |
|
RUN_DATETIME |
|
RUNNO |
|
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 triggers the constraint FCAS processor run |
|
RUNNO |
NUMBER(5) |
X |
The 30 minute predispatch case run number that has triggers the constraint FCAS processor run |
|
LASTCHANGED |
DATE |
|
The last time the constraint FCAS processor was executed for this case run time. |
|
Name |
|
|
Comment |
PREDISPATCH_FCAS_REQ shows Predispatch Constraint tracking for Regional FCAS Requirements. |
|
Source PREDISPATCH_FCAS_REQ updates with each pre-dispatch run (half hourly) Volume Approximately 2,000 rows per day. Note The PERIODID columns in tables PREDISPATCHCONSTRAINT and PREDISPATCH_FCAS_REQ have no consistent relationship with the other PERIODID values in the other tables in the PRE-DISPATCH package (such as PREDISPATCHPRICE). AEMO and many Participants appreciate the data model is inconsistent, but the cost of changing existing systems has been judged as being unjustifiable. An additional field DATETIME was added to allow joins between these data sets. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
BIDTYPE |
|
DATETIME |
|
GENCONID |
|
REGIONID |
|
Name |
|
LASTCHANGED |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
|
PreDispatch Sequence number |
|
RUNNO |
NUMBER(3,0) |
|
Case Run number |
|
INTERVENTION |
NUMBER(2,0) |
|
Intervention Flag |
|
PERIODID |
VARCHAR2(20) |
|
Unique period identifier, in the format yyyymmddpp. The period (pp) is 01 to 48, with 01 corresponding to the half-hour ending at 04:30am. |
|
GENCONID |
VARCHAR2(20) |
X |
Generic Constraint ID - Join to table GenConData |
|
REGIONID |
VARCHAR2(10) |
X |
Region ID |
|
BIDTYPE |
VARCHAR2(10) |
X |
Bid Type Identifier |
|
GENCONEFFECTIVEDATE |
DATE |
|
Generic Constraint EffectiveDate - Join to table GenConData |
|
GENCONVERSIONNO |
NUMBER(3,0) |
|
Generic Constraint Version number - Join to table GenConData |
|
MARGINALVALUE |
NUMBER(16,6) |
|
Marginal Value of generic constraint |
|
DATETIME |
DATE |
X |
Date and Time of trading interval |
|
LASTCHANGED |
DATE |
|
Last date and time record changed |
|
BASE_COST |
NUMBER(18,8) |
|
The base cost of the constraint for this service, before the regulation/contingency split |
|
ADJUSTED_COST |
NUMBER(18,8) |
|
The adjusted cost of the constraint for this service, before the regulation/contingency split |
|
ESTIMATED_CMPF |
NUMBER(18,8) |
|
An estimated value for the constraint CMPF, based on dispatched data |
|
ESTIMATED_CRMPF |
NUMBER(18,8) |
|
An estimated value for the constraint CRMPF, based on dispatched data |
|
RECOVERY_FACTOR_CMPF |
NUMBER(18,8) |
|
Estimated recovery factor for CMPF based recovery |
|
RECOVERY_FACTOR_CRMPF |
NUMBER(18,8) |
|
Estimated recovery factor for CRMPF based recovery |
|
Name |
|
|
Comment |
Sets out local pricing offsets associated with each DUID connection point for each dispatch period |
|
Name |
Comment |
Value |
|
Visibility |
|
Private & Public Next-Day |
|
Name |
|
DATETIME |
|
DUID |
|
Name |
|
DATETIME |
|
DUID |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
X |
Unique identifier of predispatch run in the form YYYYMMDDPP with 01 at 04:30 |
|
DATETIME |
DATE |
X |
The unique identifier for the interval within this study |
|
DUID |
VARCHAR2(20) |
X |
Dispatchable unit identifier |
|
PERIODID |
VARCHAR2(20) |
|
A period count, starting from 1 for each predispatch run. Use DATETIME to determine half hour period |
|
LOCAL_PRICE_ADJUSTMENT |
NUMBER(10, 2) |
|
Aggregate Constraint contribution cost of this unit: Sum(MarginalValue x Factor) for all relevant Constraints |
|
LOCALLY_CONSTRAINED |
NUMBER(1,0) |
|
Key for Local_Price_Adjustment: 2 = at least one Outage Constraint; 1 = at least 1 System Normal Constraint (and no Outage Constraint); 0 = No System Normal or Outage Constraints |
|
LASTCHANGED |
DATE |
|
Last date and time record changed |
|
Name |
|
|
Comment |
PREDISPATCH_MNSPBIDTRK shows the MNSP bid tracking, including the bid version used in each predispatch run for each MNSP Interconnector Link. PREDISPATCH_MNSPBIDTRK shows the audit trail of the bid used for each predispatch run. |
|
Source Own (confidential) data updates every predispatch run. All bids are available to all participants as part of next day market data. Volume 1, 700, 000 per year |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
LINKID |
|
PERIODID |
|
PREDISPATCHSEQNO |
|
Name |
|
LASTCHANGED |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
X |
Predispatch run identifier |
|
LINKID |
VARCHAR2(10) |
X |
Identifier for each of the two MNSP Interconnector Links. Each link pertains to the direction from and to. |
|
PERIODID |
VARCHAR2(20) |
X |
Trading Interval number |
|
PARTICIPANTID |
VARCHAR2(10) |
|
Participant Identifier |
|
SETTLEMENTDATE |
DATE |
|
Market Date from which bid is active |
|
OFFERDATE |
TIMESTAMP(3) |
|
Time this bid was processed and loaded |
|
VERSIONNO |
NUMBER(3,0) |
|
Version No. for given offer date and settlement date used |
|
DATETIME |
DATE |
|
Period expressed as Date/Time |
|
LASTCHANGED |
DATE |
|
Record creation timestamp |
|
Name |
|
|
Comment |
PREDISPATCH Blocked Constraints lists any constraints that were blocked in a Predispatch run. If no constraints are blocked, there will be no rows for that predispatch run. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
CONSTRAINTID |
|
PREDISPATCHSEQNO |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
X |
Unique identifier of predispatch run in the form YYYYMMDDPP with 01 at 04:30 |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Generic Constraint identifier (synonymous with GenConID) |
|
Name |
|
|
Comment |
PREDISPATCHCASESOLUTION provides information relating to the complete predispatch run. The fields provide an overview of the dispatch run results allowing immediate identification of conditions such as energy or FCAS deficiencies. |
|
PREDISPATCHCASESOLUTION data is public, so is available to all participants. Source PREDISPATCHCASESOLUTION updates every half-hour. Volume Approximately 48 records per day. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
PREDISPATCHSEQNO |
|
RUNNO |
|
Name |
|
LASTCHANGED |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
X |
Unique identifier of predispatch run in the form YYYYMMDDPP with 01 at 04:30 |
|
RUNNO |
NUMBER(3,0) |
X |
Predispatch run no, normally 1. |
|
SOLUTIONSTATUS |
NUMBER(2,0) |
|
If non-zero indicated one of the following conditions: 1 = Supply Scarcity, Excess generation or constraint violations, -X = Model failure |
|
SPDVERSION |
VARCHAR2(20) |
|
Current version of SPD |
|
NONPHYSICALLOSSES |
NUMBER(1,0) |
|
Non-Physical Losses algorithm invoked during this run |
|
TOTALOBJECTIVE |
NUMBER(27,10) |
|
The Objective function from the LP |
|
TOTALAREAGENVIOLATION |
NUMBER(15,5) |
|
Total Region Demand violations |
|
TOTALINTERCONNECTORVIOLATION |
NUMBER(15,5) |
|
Total interconnector violations |
|
TOTALGENERICVIOLATION |
NUMBER(15,5) |
|
Total generic constraint violations |
|
TOTALRAMPRATEVIOLATION |
NUMBER(15,5) |
|
Total ramp rate violations |
|
TOTALUNITMWCAPACITYVIOLATION |
NUMBER(15,5) |
|
Total unit capacity violations |
|
TOTAL5MINVIOLATION |
NUMBER(15,5) |
|
Total of 5 minute ancillary service region violations |
|
TOTALREGVIOLATION |
NUMBER(15,5) |
|
Total of Regulation ancillary service region violations |
|
TOTAL6SECVIOLATION |
NUMBER(15,5) |
|
Total of 6 second ancillary service region violations |
|
TOTAL60SECVIOLATION |
NUMBER(15,5) |
|
Total of 60 second ancillary service region violations |
|
TOTALASPROFILEVIOLATION |
NUMBER(15,5) |
|
Total of ancillary service trader profile violations |
|
TOTALENERGYCONSTRVIOLATION |
NUMBER(15,5) |
|
Total of Energy Constrained unit offer violations. |
|
TOTALENERGYOFFERVIOLATION |
NUMBER(15,5) |
|
Total of unit summated offer band violations |
|
LASTCHANGED |
DATE |
|
Last date and time record changed |
|
INTERVENTION |
NUMBER(2,0) |
|
Flag to indicate if this Pre-Dispatch case includes an intervention pricing run: 0 = case does not include an intervention pricing run, 1 = case does include an intervention pricing run. This field has a default value of 0 and is not nullable |
|
Name |
|
|
Comment |
PREDISPATCHCONSTRAINT sets out constraints that are binding in each predispatch run and interconnector constraints (whether binding or not). Only binding and interconnector constraints are reported. Binding contracts have marginal value greater than $0. Interconnector constraints are listed so RHS values can be reported for ST PASA. |
|
PREDISPATCHCONSTRAINT data is confidential on the day of creation, and public to all participants after the end of the market day. Source PREDISPATCHCONSTRAINT updates with every thirty-minute predispatch run. Note The PERIODID columns in tables PREDISPATCHCONSTRAINT and PREDISPATCH_FCAS_REQ have no consistent relationship with the other PERIODID values in the other tables in the PRE-DISPATCH package (such as PREDISPATCHPRICE). AEMO and many Participants appreciate the data model is inconsistent, but the cost of changing existing systems has been judged as being unjustifiable. An additional field DATETIME was added to allow joins between these data sets. |
|
Name |
Comment |
Value |
|
Visibility |
|
Private & Public Next-Day |
|
Name |
|
CONSTRAINTID |
|
DATETIME |
|
Name |
|
PREDISPATCHSEQNO |
|
Name |
|
LASTCHANGED |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
|
Unique identifier of predispatch run in the form YYYYMMDDPP with 01 at 04:30 |
|
RUNNO |
NUMBER(3,0) |
|
SPD Predispatch run no, typically 1. It increments if the case is re-run. |
|
CONSTRAINTID |
VARCHAR2(20) |
X |
Generic constraint identifier |
|
PERIODID |
VARCHAR2(20) |
|
Unique period identifier, in the format yyyymmddpp. The period (pp) is 01 to 48, with 01 corresponding to the half-hour ending at 04:30am. |
|
INTERVENTION |
NUMBER(2,0) |
|
Flag to indicate if this result set was sourced from the pricing run (INTERVENTION=0) or the physical run (INTERVENTION=1). In the event that there is not intervention in the market, both pricing and physical runs correspond to INTERVENTION=0 |
|
RHS |
NUMBER(15,5) |
|
RHS value used. |
|
MARGINALVALUE |
NUMBER(15,5) |
|
Marginal value of violated constraint |
|
VIOLATIONDEGREE |
NUMBER(15,5) |
|
Degree of constraint violation |
|
LASTCHANGED |
DATE |
|
Last date and time record changed |
|
DATETIME |
DATE |
X |
Period date and time |
|
DUID |
VARCHAR2(20) |
|
DUID to which the Constraint is confidential. Null denotes non-confidential |
|
GENCONID_EFFECTIVEDATE |
DATE |
|
Effective date of the Generic Constraint (ConstraintID). This field is used to track the version of this generic constraint applied in this dispatch interval |
|
GENCONID_VERSIONNO |
NUMBER(22,0) |
|
Version number of the Generic Constraint (ConstraintID). This field is used to track the version of this generic constraint applied in this dispatch interval |
|
LHS |
number(15,5) |
|
Aggregation of the constraints LHS term solution values |
|
Name |
|
|
Comment |
PREDISPATCHINTERCONNECTORRES records Interconnector flows and losses for the periods calculated in each predispatch run. Only binding and interconnector constraints are reported. |
|
Source PREDISPATCHINTERCONNECTORRES updates with every thirty-minute predispatch run. Note MW losses can be negative depending on the flow. The definition of direction of flow for an interconnector is that positive flow starts from the FROMREGION in INTERCONNECTOR. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
DATETIME |
|
INTERCONNECTORID |
|
Name |
|
PREDISPATCHSEQNO |
|
Name |
|
LASTCHANGED |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
|
Unique identifier of predispatch run in the form YYYYMMDDPP with 01 at 04:30 |
|
RUNNO |
NUMBER(3,0) |
|
SPD Predispatch run no, typically 1. It increments if the case is re-run. |
|
INTERCONNECTORID |
VARCHAR2(10) |
X |
Interconnector identifier |
|
PERIODID |
VARCHAR2(20) |
|
PERIODID is just a period count, starting from 1 for each predispatch run. Use DATETIME to determine half hour period. |
|
INTERVENTION |
NUMBER(2,0) |
|
Flag to indicate if this result set was sourced from the pricing run (INTERVENTION=0) or the physical run (INTERVENTION=1). In the event that there is not intervention in the market, both pricing and physical runs correspond to INTERVENTION=0 |
|
METEREDMWFLOW |
NUMBER(15,5) |
|
Metered MW Flow from EMS. For periods subsequent to the first period of a Pre-Dispatch run, this value represents the cleared target for the previous period of that Pre-Dispatch run. |
|
MWFLOW |
NUMBER(15,5) |
|
Calculated MW Flow |
|
MWLOSSES |
NUMBER(15,5) |
|
Calculated MW Losses |
|
MARGINALVALUE |
NUMBER(15,5) |
|
$ Marginal value of interconnector constraint from SPD |
|
VIOLATIONDEGREE |
NUMBER(15,5) |
|
Degree of violation of interconnector constraint in MW |
|
LASTCHANGED |
DATE |
|
Last changed. |
|
DATETIME |
DATE |
X |
Period date and time |
|
EXPORTLIMIT |
NUMBER(15,5) |
|
Calculated export limit. |
|
IMPORTLIMIT |
NUMBER(15,5) |
|
Calculated import limit. |
|
MARGINALLOSS |
NUMBER(15,5) |
|
Marginal loss factor. Use this to adjust bids between reports. |
|
EXPORTGENCONID |
VARCHAR2(20) |
|
Generic Constraint setting the export limit |
|
IMPORTGENCONID |
VARCHAR2(20) |
|
Generic Constraint setting the import limit |
|
FCASEXPORTLIMIT |
NUMBER(15,5) |
|
Calculated export limit applying to energy + FCAS. |
|
FCASIMPORTLIMIT |
NUMBER(15,5) |
|
Calculated import limit applying to energy + FCAS. |
|
LOCAL_PRICE_ADJUSTMENT_EXPORT |
NUMBER(10,2) |
|
Aggregate Constraint contribution cost of this Interconnector: Sum(MarginalValue x Factor) for all relevant Constraints, for Export (Factor >= 0) |
|
LOCALLY_CONSTRAINED_EXPORT |
NUMBER(1,0) |
|
Key for Local_Price_Adjustment_Export: 2 = at least one Outage Constraint; 1 = at least 1 System Normal Constraint (and no Outage Constraint); 0 = No System Normal or Outage Constraints |
|
LOCAL_PRICE_ADJUSTMENT_IMPORT |
NUMBER(10,2) |
|
Aggregate Constraint contribution cost of this Interconnector: Sum(MarginalValue x Factor) for all relevant Constraints, for Import (Factor >= 0) |
|
LOCALLY_CONSTRAINED_IMPORT |
NUMBER(1,0) |
|
Key for Local_Price_Adjustment_Import: 2 = at least one Outage Constraint; 1 = at least 1 System Normal Constraint (and no Outage Constraint); 0 = No System Normal or Outage Constraints |
|
Name |
|
|
Comment |
PREDISPATCHINTERSENSITIVITIES sets out the sensitivity flows for each interconnector by period. |
|
Name |
Comment |
Value |
|
Visibility |
|
Public |
|
Name |
|
DATETIME |
|
INTERCONNECTORID |
|
Name |
|
LASTCHANGED |
|
Name |
Data Type |
Mandatory |
Comment |
|
PREDISPATCHSEQNO |
VARCHAR2(20) |
|
Unique identifier of predispatch run in the form YYYYMMDDPP with 01 at 04:30 |
|
RUNNO |
NUMBER(3,0) |
|
LP Solver Predispatch run no, typically 1. It increments if the case is re-run. |
|
INTERCONNECTORID |
VARCHAR2(10) |
X |
Unique interconnector identifier |
|
PERIODID |
VARCHAR2(20) |
|
PERIODID is just a period count, starting from 1 for each predispatch run. Use DATETIME to determine half hour period. |
|
INTERVENTION |
NUMBER(2,0) |
|
Flag to indicate if this result set was sourced from the pricing run (INTERVENTION=0) or the physical run (INTERVENTION=1). In the event that there is not intervention in the market, both pricing and physical runs correspond to INTERVENTION=0 |
|
DATETIME |
DATE |
X |
Period date and time |
|
INTERVENTION_ACTIVE |
NUMBER(1,0) |
|
Flag to indicate if the sensitivity run contains an active intervention constraint: 0 = No, 1 = Yes |
|
MWFLOW1 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 1 |
|
MWFLOW2 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 2 |
|
MWFLOW3 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 3 |
|
MWFLOW4 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 4 |
|
MWFLOW5 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 5 |
|
MWFLOW6 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 6 |
|
MWFLOW7 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 7 |
|
MWFLOW8 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 8 |
|
MWFLOW9 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 9 |
|
MWFLOW10 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 10 |
|
MWFLOW11 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 11 |
|
MWFLOW12 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 12 |
|
MWFLOW13 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 13 |
|
MWFLOW14 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 14 |
|
MWFLOW15 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 15 |
|
MWFLOW16 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 16 |
|
MWFLOW17 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 17 |
|
MWFLOW18 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 18 |
|
MWFLOW19 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 19 |
|
MWFLOW20 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 20 |
|
MWFLOW21 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 21 |
|
MWFLOW22 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 22 |
|
MWFLOW23 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 23 |
|
MWFLOW24 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 24 |
|
MWFLOW25 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 25 |
|
MWFLOW26 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 26 |
|
MWFLOW27 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 27 |
|
MWFLOW28 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 28 |
|
MWFLOW29 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 29 |
|
MWFLOW30 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 30 |
|
MWFLOW31 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 31 |
|
MWFLOW32 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 32 |
|
MWFLOW33 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 33 |
|
MWFLOW34 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 34 |
|
MWFLOW35 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 35 |
|
MWFLOW36 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 36 |
|
MWFLOW37 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 37 |
|
MWFLOW38 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 38 |
|
MWFLOW39 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 39 |
|
MWFLOW40 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 40 |
|
MWFLOW41 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 41 |
|
MWFLOW42 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 42 |
|
MWFLOW43 |
NUMBER(15,5) |
|
MW flow for given Interconnector for scenario 43 |
|
|
|