Name |
|
Comment |
EMSMASTER provides a description of the SCADA measurements that are associated with the SPD_ID points utilised in generic equation RHS terms |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
SPD_ID |
SPD_TYPE |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
SPD_ID |
VARCHAR(21) |
X |
ID defining data source |
SPD_TYPE |
VARCHAR(1) |
X |
ID describing type of data source |
DESCRIPTION |
VARCHAR(255) |
|
The detailed description of the SCADA point associated with the SPD_ID |
GROUPING_ID |
VARCHAR(20) |
|
The Grouping associated with the SPD ID - most often a RegionID |
LASTCHANGED |
DATE |
|
Last date and time record changed |
Name |
|
Comment |
GENCONDATA sets out the generic constraints contained within a generic constraint set invoked in PASA, predispatch and dispatch. |
GENCONDATA is a public data, and is available to all participants. Source GENCONDATA updates as constraint details are updated by AEMO. Note The following fields enable selective application of invoked constraints in the Dispatch, Predispatch, ST PASA or MT PASA processes: · DISPATCH · PREDISPATCH · STPASA · MTPASA The flag P5MIN_SCOPE_OVERRIDE indicates for each constraint whether 5MPD makes use of the default Dispatch (P5MIN_SCOPE_OVERRIDE = NULL) or Pre-dispatch (P5MIN_SCOPE_OVERRIDE = ‘PD’) style RHS definition. GENERICCONSTRAINTRHS stores generic constraint RHS definitions. Constraints without records in GENERICCONSTRAINTRHS only make use of the static RHS defined in the CONSTRAINTVALUE column in GENCONDATA . The default value for the P5MIN_SCOPE_OVERRIDE column is NULL, so constraints existing before implementing the column use the DISPATCH RHS definition by default, as was the case before the implementation of the change. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
EFFECTIVEDATE |
GENCONID |
VERSIONNO |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
EFFECTIVEDATE |
DATE |
X |
Effective date of this constraint |
VERSIONNO |
NUMBER(3,0) |
X |
Version with respect to the effective date |
GENCONID |
VARCHAR2(20) |
X |
Unique ID for the constraint |
CONSTRAINTTYPE |
VARCHAR2(2) |
|
The logical operator (=, >=, <=) |
CONSTRAINTVALUE |
NUMBER(16,6) |
|
the RHS value used if there is no dynamic RHS defined in GenericConstraintRHS |
DESCRIPTION |
VARCHAR2(256) |
|
Detail of the plant that is not in service |
STATUS |
VARCHAR2(8) |
|
Not used |
GENERICCONSTRAINTWEIGHT |
NUMBER(16,6) |
|
The constraint violation penalty factor |
AUTHORISEDDATE |
DATE |
|
Date record authorised |
AUTHORISEDBY |
VARCHAR2(15) |
|
User authorising record |
DYNAMICRHS |
NUMBER(15,5) |
|
Not used |
LASTCHANGED |
DATE |
|
Last date and time record changed |
DISPATCH |
VARCHAR2(1) |
|
Flag: constraint RHS used for Dispatch? 1-used, 0-not used |
PREDISPATCH |
VARCHAR2(1) |
|
Flag to indicate if the constraint RHS is to be used for PreDispatch, 1-used, 0-not used |
STPASA |
VARCHAR2(1) |
|
Flag to indicate if the constraint RHS is to be used for ST PASA, 1-used, 0-not used |
MTPASA |
VARCHAR2(1) |
|
Flag to indicate if the constraint RHS is to be used for MT PASA, 1-used, 0-not used |
IMPACT |
VARCHAR2(64) |
|
The device(s) that is affected by the constraint e.g. Interconnector, Generator(s) or Cutset |
SOURCE |
VARCHAR2(128) |
|
The source of the constraint formulation |
LIMITTYPE |
VARCHAR2(64) |
|
The limit type of the constraint e.g. Transient Stability, Voltage Stability |
REASON |
VARCHAR2(256) |
|
The contingency or reason for the constraint |
MODIFICATIONS |
VARCHAR2(256) |
|
Details of the changes made to this version of the constraint |
ADDITIONALNOTES |
VARCHAR2(256) |
|
Extra notes on the constraint |
P5MIN_SCOPE_OVERRIDE |
VARCHAR2(2) |
|
Extra notes on the constraint: NULL = Dispatch RHS applied in 5MPD, PD = PreDispatch RHS applied in 5MPD |
LRC |
VARCHAR2(1) |
|
Flag to indicate if PASA LRC run uses the constraint; 1-used, 0-not used |
LOR |
VARCHAR2(1) |
|
Flag to indicate if PASA LOR run uses the constraint; 1-used, 0-not used |
FORCE_SCADA |
NUMBER(1,0) |
|
Flags Constraints for which NEMDE must use "InitialMW" values instead of "WhatOfInitialMW" for Intervention Pricing runs |
Name |
|
Comment |
GENCONSET sets out generic constraint sets that are invoked and revoked, and may contain many generic constraints (GENCONDATA). |
GENCONSET is public data, and is available to all participants. Source GENCONSET updates as sets are updated by AEMO. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
EFFECTIVEDATE |
GENCONID |
GENCONSETID |
VERSIONNO |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
GENCONSETID |
VARCHAR2(20) |
X |
Unique ID for the Constraint Set |
EFFECTIVEDATE |
DATE |
X |
Date this record becomes effective |
VERSIONNO |
NUMBER(3,0) |
X |
Version no of the record for the given effective date |
GENCONID |
VARCHAR2(20) |
X |
Generic Contraint ID |
GENCONEFFDATE |
DATE |
|
Since market start in 1998 these fields have not been used and any data that has been populated in the fields should be ignored |
GENCONVERSIONNO |
NUMBER(3,0) |
|
Since market start in 1998 these fields have not been used and any data that has been populated in the fields should be ignored |
LASTCHANGED |
DATE |
|
Last date and time record changed |
Name |
|
Comment |
GENCONSETINVOKE provides details of invoked and revoked generic constraints. GENCONSETINVOKE is the key table for determining what constraints are active in dispatch, predispatch and PASA. |
GENCONSETINVOKE is public data. All participants have access to this data. Source GENCONSETINVOKE updates each time a generic constraint is invoked or revoke time is altered. Once past the time, these times cannot be altered. Note The Replica software does not handle the deletion of GENCONSETINVOKE records. To workaround this problem, the field STARTAUTHORISEDBY indicates whether a constraint set invocation is applicable. A non-null value for the STARTAUTHORISEDBY field indicates that the constraint invocation is active. Essentially inactive invocations have a null value for the STARTAUTHORISEDBY field. To remove inactive invocations from queries on the GENCONSETINVOKE table, add the following text to the where clause "and STARTAUTHORISEDBY is not null". |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
INVOCATION_ID |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
INVOCATION_ID |
NUMBER(9) |
X |
Abstract unique identifier for the record. Allows Invocations to be modified without affecting PK values |
STARTDATE |
DATE |
X |
Market date of start |
STARTPERIOD |
NUMBER(3,0) |
X |
The first dispatch interval of the invocation being the dispatch interval number starting from1 at 04:05. |
GENCONSETID |
VARCHAR2(20) |
X |
Unique generic constraint set identifier |
ENDDATE |
DATE |
|
Market date end |
ENDPERIOD |
NUMBER(3,0) |
|
Dispatch interval number end |
STARTAUTHORISEDBY |
VARCHAR2(15) |
|
User authorising invoke, indicating a constraint set invocation is applicable (i.e. non-null). A null value indicates inactive invocation. |
ENDAUTHORISEDBY |
VARCHAR2(15) |
|
user authorising revoke. |
INTERVENTION |
VARCHAR2(1) |
|
0 is not intervention, 1 is intervention and causes dispatch to solve twice. |
ASCONSTRAINTTYPE |
VARCHAR2(10) |
|
Constraint type (e.g. ancillary services). This also flags where a constraint is an interconnector or intra-region network limit. |
LASTCHANGED |
DATE |
|
Last date and time record changed |
STARTINTERVALDATETIME |
DATE |
|
The settlement date and time corresponding to the first interval to which the constraint set is to be applied. |
ENDINTERVALDATETIME |
DATE |
|
The settlement date and time corresponding to the last interval to which the constraint set is to be applied. |
SYSTEMNORMAL |
VARCHAR2(1) |
|
Flag to indicate if the constraint set is a system normal (1) or an outage set (0) |
Name |
|
Comment |
GENCONSETTRK assists in determining the correct version of a generic constraint set that has been invoked in GENCONSETINVOKE. |
GENCONSETTRK data is public to all participants. Source Ad hoc updates occur to GENCONSETTRK. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
EFFECTIVEDATE |
GENCONSETID |
VERSIONNO |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
GENCONSETID |
VARCHAR2(20) |
X |
Unique ID for the Constraint Set |
EFFECTIVEDATE |
DATE |
X |
Date this record becomes effective |
VERSIONNO |
NUMBER(3,0) |
X |
Version no of the record for the given effective date |
DESCRIPTION |
VARCHAR2(256) |
|
Description of the constraint |
AUTHORISEDBY |
VARCHAR2(15) |
|
The person who authorised the constraint set |
AUTHORISEDDATE |
DATE |
|
The date and time of authorising the constraint set |
LASTCHANGED |
DATE |
|
Last date and time record changed |
COVERAGE |
VARCHAR2(64) |
|
The region the constraint set is located in or a special grouping (e.g. CHIMERA) |
MODIFICATIONS |
VARCHAR2(256) |
|
Details of the changes made to this version of the constraint set |
SYSTEMNORMAL |
VARCHAR2(1) |
|
Not used as of 2005 End of Year Release [was Flag to indicate if the constraint set is a system normal (1) or and an outage set (0)] |
OUTAGE |
VARCHAR2(256) |
|
Detail of the plant that is not in service |
Name |
|
Comment |
GENERICCONSTRAINTRHS sets out details of generic constraint Right Hand Side (RHS) formulations for dispatch (DS), predispatch (PD) and Short Term PASA (ST). GENERICCONSTRAINTRHS also includes general expressions (EQ) used in the dispatch, predispatch and PASA time frames. |
GENERICCONSTRAINTRHS is public data, and is available to all participants. Source GENERICCONSTRAINTRHS updates whenever a new generic constraint RHS or expression is created or modified Volume Approximately 70,000 records per year Note GENERICEQUATIONRHS and GENERICEQUATIONDESC allow commonly used constraint right hand side formulations to be defined as a generic equation. Once defined, the generic equation can be referenced from any Generic constraint RHS formulation defined in GENERICCONSTRAINTRHS. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
EFFECTIVEDATE |
GENCONID |
SCOPE |
TERMID |
VERSIONNO |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
GENCONID |
VARCHAR2(20) |
X |
Generic Constraint Identifier |
EFFECTIVEDATE |
DATE |
X |
Effective date of this record |
VERSIONNO |
NUMBER(22,0) |
X |
Version no of this record for the effective date |
SCOPE |
VARCHAR2(2) |
X |
Scope of RHS term (DS, PD, ST or EQ) |
TERMID |
NUMBER(4,0) |
X |
The unique identifier for the a constraint RHS term |
GROUPID |
NUMBER(3,0) |
|
ID of super-term, if this is a sub-term |
SPD_ID |
VARCHAR2(21) |
|
ID defining data source |
SPD_TYPE |
VARCHAR2(1) |
|
ID describing type of data source |
FACTOR |
NUMBER(16,6) |
|
Multiplier applied to operator result |
OPERATION |
VARCHAR2(10) |
|
Unitary operator to apply to data value |
DEFAULTVALUE |
NUMBER(16,6) |
|
Default value if primary source given by SPD_ID and SPD_TYPE not available. |
PARAMETERTERM1 |
VARCHAR2(12) |
|
The unique identifier for the first term (logic expression) to use in a Branch term |
PARAMETERTERM2 |
VARCHAR2(12) |
|
The unique identifier for the second term (logic<=0 result) to use in a Branch term |
PARAMETERTERM3 |
VARCHAR2(12) |
|
The unique identifier for the third term (logic>0 result) to use in a Branch term |
LASTCHANGED |
DATE |
|
Last date and time record changed |
Name |
|
Comment |
GENERICEQUATIONDESC defines a generic equation identifier with a description. The formulation of the generic equation is detailed in GENERICEQUATIONRHS. |
GENERICEQUATIONDESC data is public to all participants. Source GENERICEQUATIONDESC updates when new a generic equation is created for the first time. Volume Approximately 100 records per year Note GENERICEQUATIONRHS and GENERICEQUATIONDESC allow commonly used constraint right hand side formulations to be defined as a generic equation. Once defined, the generic equation can be referenced from any Generic constraint RHS formulation defined in GENERICCONSTRAINTRHS. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
EQUATIONID |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
EQUATIONID |
VARCHAR2(20) |
X |
Generic Equation Identifier |
DESCRIPTION |
VARCHAR2(256) |
|
Generic Equation Description |
LASTCHANGED |
DATE |
|
Last date and time record changed |
IMPACT |
VARCHAR2(64) |
|
The device(s) affected by the constraint (e.g. Interconnector, Generator(s) or Cutset) |
SOURCE |
VARCHAR2(128) |
|
The source of the constraint formulation |
LIMITTYPE |
VARCHAR2(64) |
|
The limit type of the constraint e.g. Transient Stability, Voltage Stability |
REASON |
VARCHAR2(256) |
|
The contingency or reason for the constraint |
MODIFICATIONS |
VARCHAR2(256) |
|
Details of the changes made to this version of the generic equation RHS |
ADDITIONALNOTES |
VARCHAR2(256) |
|
Extra notes on the constraint |
Name |
|
Comment |
GENERICEQUATIONRHS stores the formulation of commonly used Generic Constraint Right Hand Side Equations referenced from Generic Constraint Right Hand Side definitions stored in GENERICCONSTRAINTRHS. The Generic Equation definitions are versioned and the latest effective version is applied to the dispatch process. |
GENERICEQUATIONRHS data is public to all participants. Source GENERICEQUATIONRHS updates whenever a generic equation is created or modified. Volume Approximately 1,000 records per year Note GENERICEQUATIONRHS and GENERICEQUATIONDESC allow commonly used constraint right hand side formulations to be defined as a generic equation. Once defined, the generic equation can be referenced from any Generic constraint RHS formulation defined in GENERICCONSTRAINTRHS. To reference a generic equation from a generic constraint RHS definition, specify a SPD_TYPE of ‘X’ and the SPD_ID equivalent to the EQUATIONID field in GENERICEQUATIONRHS. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
EFFECTIVEDATE |
EQUATIONID |
TERMID |
VERSIONNO |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
EQUATIONID |
VARCHAR2(20) |
X |
Generic Equation Identifier |
EFFECTIVEDATE |
DATE |
X |
Effective date of this record |
VERSIONNO |
NUMBER(3,0) |
X |
Version no of this record for the effective date |
TERMID |
NUMBER(3,0) |
X |
The unique identifier for the a equation RHS term |
GROUPID |
NUMBER(3,0) |
|
ID of super-term, if this is a sub-term |
SPD_ID |
VARCHAR2(21) |
|
ID defining data source |
SPD_TYPE |
VARCHAR2(1) |
|
ID describing type of data source |
FACTOR |
NUMBER(16,6) |
|
Multiplier applied to operator result |
OPERATION |
VARCHAR2(10) |
|
Unitary operator to apply to data value |
DEFAULTVALUE |
NUMBER(16,6) |
|
Default value if primary source given by SPD_ID and SPD_TYPE not available. |
PARAMETERTERM1 |
VARCHAR2(12) |
|
The unique identifier for the first term (logic expression) to use in a Branch term |
PARAMETERTERM2 |
VARCHAR2(12) |
|
The unique identifier for the second term (logic<=0 result) to use in a Branch term |
PARAMETERTERM3 |
VARCHAR2(12) |
|
The unique identifier for the third term (logic>0 result) to use in a Branch term |
LASTCHANGED |
DATE |
|
Last date and time record changed |
Name |
|
Comment |
SPDCONNECTIONPOINTCONSTRAINT sets out details of connections point constraints issued in dispatch, predispatch and STPASA. |
The addition of the BIDTYPE field to SPDCONNECTIONPOINTCONSTRAINT allows constraints to be applied to a dispatchable unit energy and/or Frequency Controlled Ancillary Services dispatch. SPDCONNECTIONPOINTCONSTRAINTdata is public, so is available to all participants. Source SPDCONNECTIONPOINTCONSTRAINT updates whenever new connection point constraints are created. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
BIDTYPE |
CONNECTIONPOINTID |
EFFECTIVEDATE |
GENCONID |
VERSIONNO |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
CONNECTIONPOINTID |
VARCHAR2(12) |
X |
Connection Point Identifier |
EFFECTIVEDATE |
DATE |
X |
Effective date of this record |
VERSIONNO |
NUMBER(3,0) |
X |
Version no of this record for the effective date |
GENCONID |
VARCHAR2(20) |
X |
Generic Constraint Identifier |
FACTOR |
NUMBER(16,6) |
|
Constraint factor |
LASTCHANGED |
DATE |
|
Last date and time record changed |
BIDTYPE |
VARCHAR2(12) |
X |
Bid Type Identifier; one of (RAISE6SEC, RAISE60SEC, RAISE5MIN, LOWER6SEC, LOWER60SEC, LOWER5MIN, RAISEREG, LOWERREG) |
Name |
|
Comment |
SPDINTERCONNECTORCONSTRAINT contains details on the interconnector constraint factors used in dispatch, predispatch and STPASA. The details set a LHS value. |
SPDINTERCONNECTORCONSTRAINT is public data, and is available to all participants. Source SPDINTERCONNECTORCONSTRAINT updates whenever new connection point constraints are created. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
EFFECTIVEDATE |
GENCONID |
INTERCONNECTORID |
VERSIONNO |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
INTERCONNECTORID |
VARCHAR2(10) |
X |
Interconnector Identifier |
EFFECTIVEDATE |
DATE |
X |
Effective date of this record |
VERSIONNO |
NUMBER(3,0) |
X |
Version no of this record for the effective date |
GENCONID |
VARCHAR2(20) |
X |
Generic Constraint Identifier |
FACTOR |
NUMBER(16,6) |
|
Constraint factor |
LASTCHANGED |
DATE |
|
Last date and time record changed |
Name |
|
Comment |
SPDREGIONCONSTRAINT contains details on region demand constraint factors used in dispatch. SPDREGIONCONSTRAINTsets a LHS value. |
SPDREGIONCONSTRAINT is public data, and is available to all participants. Source SPDREGIONCONSTRAINT is updated whenever AEMO creates new regional constraints. |
Name |
Comment |
Value |
Visibility |
|
Public |
Name |
BIDTYPE |
EFFECTIVEDATE |
GENCONID |
REGIONID |
VERSIONNO |
Name |
LASTCHANGED |
Name |
Data Type |
Mandatory |
Comment |
REGIONID |
VARCHAR2(10) |
X |
Region Identifier |
EFFECTIVEDATE |
DATE |
X |
Effective date of this record |
VERSIONNO |
NUMBER(3,0) |
X |
Version no of this record for the effective date |
GENCONID |
VARCHAR2(20) |
X |
Generic Constraint Identifier |
FACTOR |
NUMBER(16,6) |
|
Constraint factor; one of (-1, 1) |
LASTCHANGED |
DATE |
|
Last date and time record changed |
BIDTYPE |
VARCHAR2(10) |
X |
AS Service type - relates to the BidType table; one of (RAISE6SEC, RAISE60SEC, RAISE5MIN, LOWER6SEC, LOWER60SEC, LOWER5MIN, RAISEREG, LOWERREG) |
|
|
|