Table: GENCONDATA

GENCONDATA

Name

GENCONDATA

Comment

GENCONDATA sets out the generic constraints contained within a generic constraint set invoked in PASA, predispatch and dispatch.
Fields enable selective application of invoked constraints in the Dispatch, Predispatch, ST PASA or MT PASA processes.


Description

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.


Notes

Name

Comment

Value

Visibility

Data in this table is:

Public


Primary Key Columns

Name

EFFECTIVEDATE

GENCONID

VERSIONNO


Index Columns

Name

LASTCHANGED


Content

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