{"type": "object", "properties": {"SETTLEMENTDATE": {"type": "string", "examples": ["2026/01/20 00:05:00"], "format": "date-time", "description": "End date and time of the dispatch interval\nWARNING: Despite what the name suggests, this is a datetime, not a date."}, "RUNNO": {"type": "string", "enum": [1], "description": "Dispatch run no; always 1"}, "LASTCHANGED": {"type": "string", "examples": ["2026/01/20 00:05:00"], "format": "date-time", "description": "Last date and time record changed"}}, "required": ["SETTLEMENTDATE", "RUNNO"], "description": "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.\nThe DISPATCHCASE_OCD data is public.\n\nSource\n\nThe occurrences of Over-constrained dispatch (OCD) or binding\nintra-regional network constraints (BNC) re-runs are ad hoc, with\nsignificant dependencies on the configuration or events in the physical\npower system. Potentially updated every 5 minutes.\n\nVolume\n\nRows per day: ~2\n\nMb per month: \\<1\n\nThe estimates on the number of rows are based on a 1% occurrence rate\nfor OCD runs.\n\nNote\n\nDue to the close dependency with the dispatch process, the OCD and BNC\ndata models use a \u201cCaseSolution\u201d key table in the same manner as the\nDISPATCHCASESOLUTION table."}