MktTerminal
Subclass of IEC61970:Core:Terminal.
Type |
Class |
---|---|
URI |
|
CIM standard (perspective) |
IEC62325 (Market) |
Slots
Name | Cardinality | Type | Description |
---|---|---|---|
1 |
The conducting equipment of the terminal. Conducting equipment have terminals that may be connected to other conducting equipment terminals via connectivity nodes or topological nodes. |
||
1 |
Dataset containing the data objects. |
||
0..1 |
n/a |
||
0..* |
n/a |
||
0..1 |
The bus name marker used to name the bus (topological node). |
||
0..1 |
n/a |
||
0..1 |
n/a |
||
0..1 |
The connectivity node to which this terminal connects with zero impedance. |
||
0..1 |
The feeder that this terminal normally feeds. Only specified for the terminals at head of feeders. |
||
0..1 |
The single CIM data object in the appropriate dataset context. |
||
0..1 |
The topological node associated with the terminal. This can be used as an alternative to the connectivity node path to topological node, thus making it unnecessary to model connectivity nodes in some cases. Note that the if connectivity nodes are in the model, this association would probably not be used as an input specification. |
||
0..1 |
The aliasName is free text human readable name of the object alternative to IdentifiedObject.name. It may be non unique and may not correlate to a naming hierarchy. The attribute aliasName is retained because of backwards compatibility between CIM relases. It is however recommended to replace aliasName with the Name class as aliasName is planned for retirement at a future time. |
||
0..1 |
The connected status is related to a bus-branch model and the topological node to terminal relation. True implies the terminal is connected to the related topological node and false implies it is not. In a bus-branch model, the connected status is used to tell if equipment is disconnected without having to change the connectivity described by the topological node to terminal relation. A valid case is that conducting equipment can be connected in one end and open in the other. In particular for an AC line segment, where the reactive line charging can be significant, this is a relevant case. |
||
0..1 |
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. |
||
0..1 |
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. |
||
0..1 |
The name is any free human readable and possibly non unique text naming the object. |
||
0..1 |
Represents the normal network phasing condition. If the attribute is missing, three phases (ABC) shall be assumed, except for terminals of grounding classes (specializations of EarthFaultCompensator, GroundDisconnector, and Ground) which will be assumed to be N. Therefore, phase code ABCN is explicitly declared when needed, e.g. for star point grounding equipment. The phase code on terminals connecting same ConnectivityNode or same TopologicalNode as well as for equipment between two terminals shall be consistent. |
||
0..1 |
The orientation of the terminal connections for a multiple terminal conducting equipment. The sequence numbering starts with 1 and additional terminals should follow in increasing order. The first terminal is the "starting point" for a two terminal branch. |
||
0..* |
The auxiliary equipment connected to the terminal. |
||
0..* |
The directed branch group terminals for which this terminal is monitored. |
||
0..* |
All converters' DC sides linked to this point of common coupling terminal. |
||
0..* |
The diagram objects that are associated with the domain object. |
||
0..* |
The equipment faults at this terminal. |
||
0..* |
Mutual couplings associated with the branch as the first branch. |
||
0..* |
Mutual couplings with the branch associated as the first branch. |
||
0..* |
Measurements associated with this terminal defining where the measurement is placed in the network topology. It may be used, for instance, to capture the sensor position, such as a voltage transformer (PT) at a busbar or a current transformer (CT) at the bar between a breaker and an isolator. |
||
0..* |
All names of this identified object. |
||
0..* |
The operational limit sets at the terminal. |
||
0..* |
n/a |
||
0..* |
The controls regulating this terminal. |
||
0..* |
Input signal coming from this terminal. |
||
0..* |
The power flow state variable associated with the terminal. |
||
0..* |
Data objects registered. |
||
0..* |
The control area tie flows to which this terminal associates. |
||
0..* |
All transformer ends connected at this terminal. |
aliasName
The aliasName is free text human readable name of the object alternative to IdentifiedObject.name. It may be non unique and may not correlate to a naming hierarchy. The attribute aliasName is retained because of backwards compatibility between CIM relases. It is however recommended to replace aliasName with the Name class as aliasName is planned for retirement at a future time.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
AuxiliaryEquipment
The auxiliary equipment connected to the terminal.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
BranchGroupTerminal
The directed branch group terminals for which this terminal is monitored.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
BusNameMarker
The bus name marker used to name the bus (topological node).
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
ConductingEquipment
The conducting equipment of the terminal. Conducting equipment have terminals that may be connected to other conducting equipment terminals via connectivity nodes or topological nodes.
URI |
|
---|---|
Cardinality |
1 |
Type |
|
Inherited from |
connected
The connected status is related to a bus-branch model and the topological node to terminal relation. True implies the terminal is connected to the related topological node and false implies it is not. In a bus-branch model, the connected status is used to tell if equipment is disconnected without having to change the connectivity described by the topological node to terminal relation. A valid case is that conducting equipment can be connected in one end and open in the other. In particular for an AC line segment, where the reactive line charging can be significant, this is a relevant case.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
ConnectivityNode
The connectivity node to which this terminal connects with zero impedance.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
ConverterDCSides
All converters' DC sides linked to this point of common coupling terminal.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
description
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.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
DiagramObjects
The diagram objects that are associated with the domain object.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
EquipmentFaults
The equipment faults at this terminal.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
HasFirstMutualCoupling
Mutual couplings associated with the branch as the first branch.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
HasSecondMutualCoupling
Mutual couplings with the branch associated as the first branch.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
InstanceSet
Dataset containing the data objects.
URI |
|
---|---|
Cardinality |
1 |
Type |
|
Inherited from |
Measurements
Measurements associated with this terminal defining where the measurement is placed in the network topology. It may be used, for instance, to capture the sensor position, such as a voltage transformer (PT) at a busbar or a current transformer (CT) at the bar between a breaker and an isolator.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
mRID
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.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
name
The name is any free human readable and possibly non unique text naming the object.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
Names
All names of this identified object.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
NormalHeadFeeder
The feeder that this terminal normally feeds. Only specified for the terminals at head of feeders.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
OperationalLimitSet
The operational limit sets at the terminal.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
phases
Represents the normal network phasing condition. If the attribute is missing, three phases (ABC) shall be assumed, except for terminals of grounding classes (specializations of EarthFaultCompensator, GroundDisconnector, and Ground) which will be assumed to be N. Therefore, phase code ABCN is explicitly declared when needed, e.g. for star point grounding equipment. The phase code on terminals connecting same ConnectivityNode or same TopologicalNode as well as for equipment between two terminals shall be consistent.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
PropertiesCIMDataObject
The single CIM data object in the appropriate dataset context.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
RegulatingControl
The controls regulating this terminal.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
RemoteInputSignal
Input signal coming from this terminal.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
sequenceNumber
The orientation of the terminal connections for a multiple terminal conducting equipment. The sequence numbering starts with 1 and additional terminals should follow in increasing order. The first terminal is the "starting point" for a two terminal branch.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |
SvPowerFlow
The power flow state variable associated with the terminal.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
TargetingCIMDataObject
Data objects registered.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
TieFlow
The control area tie flows to which this terminal associates.
URI |
|
---|---|
Cardinality |
0..* |
Type |
|
Inherited from |
TopologicalNode
The topological node associated with the terminal. This can be used as an alternative to the connectivity node path to topological node, thus making it unnecessary to model connectivity nodes in some cases. Note that the if connectivity nodes are in the model, this association would probably not be used as an input specification.
URI |
|
---|---|
Cardinality |
0..1 |
Type |
|
Inherited from |