Skip to content

ControlArea

A control area is a grouping of generating units and/or loads and a cutset of tie lines (as terminals) which may be used for a variety of purposes including automatic generation control, power flow solution area interchange control specification, and input to load forecasting. All generation and load within the area defined by the terminals on the border are considered in the area interchange control. Note that any number of overlapping control area specifications can be superimposed on the physical model. The following general principles apply to ControlArea: 1. The control area orientation for net interchange is positive for an import, negative for an export. 2. The control area net interchange is determined by summing flows in Terminals. The Terminals are identified by creating a set of TieFlow objects associated with a ControlArea object. Each TieFlow object identifies one Terminal. 3. In a single network model, a tie between two control areas must be modelled in both control area specifications, such that the two representations of the tie flow sum to zero. 4. The normal orientation of Terminal flow is positive for flow into the conducting equipment that owns the Terminal. (i.e. flow from a bus into a device is positive.) However, the orientation of each flow in the control area specification must align with the control area convention, i.e. import is positive. If the orientation of the Terminal flow referenced by a TieFlow is positive into the control area, then this is confirmed by setting TieFlow.positiveFlowIn flag TRUE. If not, the orientation must be reversed by setting the TieFlow.positiveFlowIn flag FALSE.

URI: cim:ControlArea
Type: Class

%%{init: {'theme':'base','themeVariables': {'lineColor': '#FF0000'}}}%%
classDiagram
    class ControlArea
    click ControlArea href "/Models/Profiles/SteadyStateHypothesis/ConcreteClasses/ControlArea/"
    style ControlArea fill:#102820,stroke:#333,stroke-width:2px,rx:10,ry:10,color:white

        PowerSystemResource <|-- ControlArea : inherits
            click PowerSystemResource href "/Models/Profiles/SteadyStateHypothesis/ConcreteClasses/PowerSystemResource/"
            style PowerSystemResource fill:#8F9779,stroke:#333,stroke-width:2px,rx:10,ry:10,color:white

        IdentifiedObject <|-- PowerSystemResource : inherits
            click IdentifiedObject href "/Models/Profiles/SteadyStateHypothesis/ConcreteClasses/IdentifiedObject/"
            style IdentifiedObject fill:#8F9779,stroke:#333,stroke-width:2px,rx:10,ry:10,color:white



        ControlArea : ControlArea.netInterchange
        ControlArea : ControlArea.pTolerance
        IdentifiedObject : IdentifiedObject.mRID

Inheritance

Attributes

Name URI Cardinality and Range Description Inheritance
netInterchange cim:ControlArea.netInterchange No cardinality available ActivePower The specified positive net interchange into the control area, i.e. positive sign means flow into the area. direct
pTolerance cim:ControlArea.pTolerance No cardinality available ActivePower Active power net interchange tolerance. The attribute shall be a positive value or zero. direct
mRID cim:IdentifiedObject.mRID No cardinality available string Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended.
For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. IdentifiedObject

Schema Source

Responsive Footer