{"type": "object", "properties": {"INTERVENTION": {"type": "boolean", "description": "Manual intervention flag"}, "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"}, "CASESUBTYPE": {"type": "string", "description": "always BNC"}, "LASTCHANGED": {"type": "string", "examples": ["2026/01/20 00:05:00"], "format": "date-time", "description": "Last date and time record changed"}, "NONPHYSICALLOSSES": {"type": "integer", "maximum": 127, "minimum": -128, "description": "Non-Physical Losses algorithm invoked occurred during this run"}, "SOLUTIONSTATUS": {"type": "integer", "maximum": 127, "minimum": -128, "description": "If non-zero indicated one of the following conditions:\n* 1 = Supply Scarcity, Excess generation or constraint violations\n* X = Model failure"}, "SPDVERSION": {"type": "number", "description": "Current version of SPD"}, "STARTPERIOD": {"type": "string", "description": "Period identifier of first interval of the case (yyyymmddppp)"}, "TOTAL5MINVIOLATION": {"type": "number", "description": "Total of 5 minute ancillary service region violations"}, "TOTAL6SECVIOLATION": {"type": "number", "description": "Total of 6 second ancillary service region violations"}, "TOTAL60SECVIOLATION": {"type": "number", "description": "Total of 60 second ancillary service region violations"}, "TOTALAREAGENVIOLATION": {"type": "number", "description": "Total Region Demand violations"}, "TOTALASPROFILEVIOLATION": {"type": "number", "description": "Total of ancillary service trader profile violations"}, "TOTALENERGYCONSTRVIOLATION": {"type": "number"}, "TOTALENERGYOFFERVIOLATION": {"type": "number", "description": "Total of unit summated offer band violations"}, "TOTALFASTSTARTVIOLATION": {"type": "number", "description": "Total of fast start trader profile violations"}, "TOTALGENERICVIOLATION": {"type": "number", "description": "Total generic constraint violations"}, "TOTALINTERCONNECTORVIOLATION": {"type": "number", "description": "Total interconnector violations"}, "TOTALOBJECTIVE": {"type": "number", "description": "The Objective function from the LP"}, "TOTALRAMPRATEVIOLATION": {"type": "number", "description": "Total ramp rate violations"}, "TOTALREGVIOLATION": {"type": "number", "description": "Total of Regulation ancillary service region violations"}, "TOTALUNITMWCAPACITYVIOLATION": {"type": "number", "description": "Total unit capacity violations"}}, "required": ["INTERVENTION", "SETTLEMENTDATE", "RUNNO"], "description": "DISPATCHCASESOLUTION_BNC was discontinued on 30 September 2009. Prior: DISPATCHCASESOLUTION_BNC is the key data to indicate when a binding intra-regional network constraints (BNC) re-run actually occurred.\nDISPATCHCASESOLUTION_BNC was discontinued on 30 September 2009.\n\nIn accordance with the \"Arrangements for Managing Risks Associated with\nTransmission Network Congestion\" set of rule changes the Dispatch\nBinding Network Constraints re-run was discontinued on September 30,\n2009.\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: ~72\n\nMb per month: 25% of DISPATCHCASESOLUTION\n\nThe estimates on the number of rows are based on a 25% occurrence rate\nfor BNC 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\nDISPATCHCASESOLUTION."}