|
Name |
|
|
Comment |
DISPATCHCASE_OCD shows the key data to indicate when an over-constrained dispatch (OCD) re-run actually occurred. One record per over-constrained dispatch interval. |
|
The DISPATCHCASE_OCD data is public. Source The occurrences of Over-constrained dispatch (OCD) or binding intra-regional network constraints (BNC) re-runs are ad hoc, with significant dependencies on the configuration or events in the physical power system. Potentially updated every 5 minutes. Volume Rows per day: ~2 Mb per month: <1 The estimates on the number of rows are based on a 1% occurrence rate for OCD runs. Note Due to the close dependency with the dispatch process, the OCD and BNC data models use a “CaseSolution” key table in the same manner as the DISPATCHCASESOLUTION table. |
|
Name |
|
RUNNO |
|
SETTLEMENTDATE |
|
Name |
|
LASTCHANGED |
|
Name |
Data Type |
Mandatory |
Comment |
|
SETTLEMENTDATE |
DATE |
X |
End date and time of the dispatch interval |
|
RUNNO |
NUMBER(3,0) |
X |
Dispatch run no; always 1 |
|
LASTCHANGED |
DATE |
|
Last date and time record changed |
|
|
|