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

ControlArea class diagram

Inheritance

Attributes

Name URI Cardinality and Range Inheritance Description
EnergyArea cim:ControlArea.EnergyArea 1..1 EnergyArea direct The energy area that is forecast from this control area specification.
mRID cim:IdentifiedObject.mRID 1..1 string IdentifiedObject 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.
description cim:IdentifiedObject.description 0..1 string IdentifiedObject The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy.
energyIdentCodeEic eu:IdentifiedObject.energyIdentCodeEic 0..1 string IdentifiedObject The attribute is used for an exchange of the EIC code (Energy identification Code). The length of the string is 16 characters as defined by the EIC code. For details on EIC scheme please refer to ENTSO-E web site.
name cim:IdentifiedObject.name 1..1 string IdentifiedObject The name is any free human readable and possibly non unique text naming the object.
shortName eu:IdentifiedObject.shortName 0..1 string IdentifiedObject The attribute is used for an exchange of a human readable short name with length of the string 12 characters maximum.

Format Examples

{
    "@context": {"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#", "linkml": "https://w3id.org/linkml/", "sh": "http://www.w3.org/ns/shacl#", "skos": "http://www.w3.org/2004/02/skos/core#", "dc": "http://purl.org/dc/elements/1.1/", "profcim": "http://iec.ch/TC57/ns/CIM/prof-cim#", "owl": "http://www.w3.org/2002/07/owl#", "cim": "http://iec.ch/TC57/CIM100#", "this": "http://ucaiug.org/ns/CGMES/CoreEquipment-EU/3.0#", "cims": "http://iec.ch/TC57/1999/rdf-schema-extensions-19990926#", "dct": "http://purl.org/dc/terms/", "rdfs": "http://www.w3.org/2000/01/rdf-schema#", "dcat": "http://www.w3.org/ns/dcat#", "eu": "http://iec.ch/TC57/CIM100-European#"},
    "@id": "urn:uuid:<uuid>",
    "@type": "cim:ControlArea",
    "cim:ControlArea.EnergyArea": { "@id": "urn:uuid:<uuid of EnergyArea>" },
    "cim:IdentifiedObject.mRID": "string",
    "cim:IdentifiedObject.description": "string",
    "eu:IdentifiedObject.energyIdentCodeEic": "string",
    "cim:IdentifiedObject.name": "string",
    "eu:IdentifiedObject.shortName": "string"
}

<cim:ControlArea rdf:ID="_<uuid>">
    <cim:ControlArea.EnergyArea rdf:resource="#_<uuid of EnergyArea>" />
    <cim:IdentifiedObject.mRID>string</cim:IdentifiedObject.mRID>
    <cim:IdentifiedObject.description>string</cim:IdentifiedObject.description>
    <eu:IdentifiedObject.energyIdentCodeEic>string</eu:IdentifiedObject.energyIdentCodeEic>
    <cim:IdentifiedObject.name>string</cim:IdentifiedObject.name>
    <eu:IdentifiedObject.shortName>string</eu:IdentifiedObject.shortName>
</cim:ControlArea>

{
    "EnergyArea": "<EnergyArea>",
    "mRID": "string",
    "description": "string",
    "energyIdentCodeEic": "string",
    "name": "string",
    "shortName": "string"
}

<urn:uuid:<graph-id>> {
    <urn:uuid:<uuid>>
        a cim:ControlArea ;
        cim:ControlArea.EnergyArea <urn:uuid:<uuid of EnergyArea>> ;
        cim:IdentifiedObject.mRID "string" ;
        cim:IdentifiedObject.description "string" ;
        eu:IdentifiedObject.energyIdentCodeEic "string" ;
        cim:IdentifiedObject.name "string" ;
        eu:IdentifiedObject.shortName "string" .
}

Schema Source