CIM Issues #6924
Updated by Alex Anderson 24 days ago
It was agreed to keep SchedulingArea and SubSchedulingArea as the concrete classes. Specializations of FeederArea, etc. will not be added to the model in favor of an enumeration that describes the kind of SubSchedulingArea. The two classes will be added to the ControlArea package It has associations to Terminal and ConductingEquipment. The self-assc nesting and assc to Feeder to remain same as in NC package. Svein to review and edit descriptions.
The SubSchedulingArea definition will be updated as:
"An area that is a part of another scheduling area. Typically part of a Transmission System Operator (TSO) scheduling area operated by a Distributed System Operator (DSO) or a Closed Distributed System Operator (CDSO). This includes microgrid concept. A sub scheduling area can contain other sub areas. A sub scheduling area leaf will form the smallest entity of any given energy area.
The SubSchedulingArea is a persistent connectivity-based containment defined by a set of boundary Terminal objects. Each piece of ConductingEquipment can be associated with one SubSchedulingArea. The boundaries of the SubSchedulingArea are specified through the Terminals of conducting equipment forming the boundary (such as a Recloser or PowerTransformer)."
Terminal assc description: "The BoundaryTerminals association is to the near-side terminal of clearly-defined electrical boundaries forming a local power system with one or more points of common coupling. Each terminal can form the boundary of only a single SubSchedulingArea"
Cond EQ assc description: "Each piece of ConductingEquipment can be associated with one SubSchedulingArea to provide a persistent containment for connectivity and control modeling"
Descriptions for the SubSchedulingAreaKind enum same as for the original concrete specializations proposed