MktTerminal

Subclass of IEC61970:Core:Terminal.

Type

Class

URI

cim:MktTerminal

CIM standard (perspective)

IEC62325 (Market)

Class hierarchy

Slots

Associated classes
Figure 1. Associated classes
Name Cardinality Type Description

ConductingEquipment

1

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.

InstanceSet

1

InstanceSet

Dataset containing the data objects.

Flowgate

0..1

Flowgate

n/a

TerminalConstraintTerm

0..*

TerminalConstraintTerm

n/a

BusNameMarker

0..1

BusNameMarker

The bus name marker used to name the bus (topological node).

Bushing

0..1

Bushing

n/a

Circuit

0..1

Circuit

n/a

ConnectivityNode

0..1

ConnectivityNode

The connectivity node to which this terminal connects with zero impedance.

NormalHeadFeeder

0..1

Feeder

The feeder that this terminal normally feeds. Only specified for the terminals at head of feeders.

PropertiesCIMDataObject

0..1

ChangeSetMember

The single CIM data object in the appropriate dataset context.

TopologicalNode

0..1

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.

aliasName

0..1

string

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.

connected

0..1

boolean

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.

description

0..1

string

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.

mRID

0..1

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.

name

0..1

string

The name is any free human readable and possibly non unique text naming the object.

phases

0..1

PhaseCode

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.

sequenceNumber

0..1

integer

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.

AuxiliaryEquipment

0..*

AuxiliaryEquipment

The auxiliary equipment connected to the terminal.

BranchGroupTerminal

0..*

BranchGroupTerminal

The directed branch group terminals for which this terminal is monitored.

ConverterDCSides

0..*

ACDCConverter

All converters' DC sides linked to this point of common coupling terminal.

DiagramObjects

0..*

DiagramObject

The diagram objects that are associated with the domain object.

EquipmentFaults

0..*

EquipmentFault

The equipment faults at this terminal.

HasFirstMutualCoupling

0..*

MutualCoupling

Mutual couplings associated with the branch as the first branch.

HasSecondMutualCoupling

0..*

MutualCoupling

Mutual couplings with the branch associated as the first branch.

Measurements

0..*

Measurement

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.

Names

0..*

Name

All names of this identified object.

OperationalLimitSet

0..*

OperationalLimitSet

The operational limit sets at the terminal.

PinTerminal

0..*

PinTerminal

n/a

RegulatingControl

0..*

RegulatingControl

The controls regulating this terminal.

RemoteInputSignal

0..*

RemoteInputSignal

Input signal coming from this terminal.

SvPowerFlow

0..*

SvPowerFlow

The power flow state variable associated with the terminal.

TargetingCIMDataObject

0..*

ChangeSetMember

Data objects registered.

TieFlow

0..*

TieFlow

The control area tie flows to which this terminal associates.

TransformerEnd

0..*

TransformerEnd

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

cim:IdentifiedObject.aliasName

Cardinality

0..1

Type

string

Inherited from

IdentifiedObject

AuxiliaryEquipment

The auxiliary equipment connected to the terminal.

URI

cim:Terminal.AuxiliaryEquipment

Cardinality

0..*

Type

AuxiliaryEquipment

Inherited from

Terminal

BranchGroupTerminal

The directed branch group terminals for which this terminal is monitored.

URI

cim:Terminal.BranchGroupTerminal

Cardinality

0..*

Type

BranchGroupTerminal

Inherited from

Terminal

Bushing

URI

cim:Terminal.Bushing

Cardinality

0..1

Type

Bushing

Inherited from

Terminal

BusNameMarker

The bus name marker used to name the bus (topological node).

URI

cim:ACDCTerminal.BusNameMarker

Cardinality

0..1

Type

BusNameMarker

Inherited from

ACDCTerminal

Circuit

URI

cim:Terminal.Circuit

Cardinality

0..1

Type

Circuit

Inherited from

Terminal

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

cim:Terminal.ConductingEquipment

Cardinality

1

Type

ConductingEquipment

Inherited from

Terminal

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

cim:ACDCTerminal.connected

Cardinality

0..1

Type

boolean

Inherited from

ACDCTerminal

ConnectivityNode

The connectivity node to which this terminal connects with zero impedance.

URI

cim:Terminal.ConnectivityNode

Cardinality

0..1

Type

ConnectivityNode

Inherited from

Terminal

ConverterDCSides

All converters' DC sides linked to this point of common coupling terminal.

URI

cim:Terminal.ConverterDCSides

Cardinality

0..*

Type

ACDCConverter

Inherited from

Terminal

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

cim:IdentifiedObject.description

Cardinality

0..1

Type

string

Inherited from

IdentifiedObject

DiagramObjects

The diagram objects that are associated with the domain object.

URI

cim:IdentifiedObject.DiagramObjects

Cardinality

0..*

Type

DiagramObject

Inherited from

IdentifiedObject

EquipmentFaults

The equipment faults at this terminal.

URI

cim:Terminal.EquipmentFaults

Cardinality

0..*

Type

EquipmentFault

Inherited from

Terminal

Flowgate

URI

cim:MktTerminal.Flowgate

Cardinality

0..1

Type

Flowgate

HasFirstMutualCoupling

Mutual couplings associated with the branch as the first branch.

URI

cim:Terminal.HasFirstMutualCoupling

Cardinality

0..*

Type

MutualCoupling

Inherited from

Terminal

HasSecondMutualCoupling

Mutual couplings with the branch associated as the first branch.

URI

cim:Terminal.HasSecondMutualCoupling

Cardinality

0..*

Type

MutualCoupling

Inherited from

Terminal

InstanceSet

Dataset containing the data objects.

URI

cim:IdentifiedObject.InstanceSet

Cardinality

1

Type

InstanceSet

Inherited from

IdentifiedObject

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

cim:ACDCTerminal.Measurements

Cardinality

0..*

Type

Measurement

Inherited from

ACDCTerminal

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

cim:IdentifiedObject.mRID

Cardinality

0..1

Type

string

Inherited from

IdentifiedObject

name

The name is any free human readable and possibly non unique text naming the object.

URI

cim:IdentifiedObject.name

Cardinality

0..1

Type

string

Inherited from

IdentifiedObject

Names

All names of this identified object.

URI

cim:IdentifiedObject.Names

Cardinality

0..*

Type

Name

Inherited from

IdentifiedObject

NormalHeadFeeder

The feeder that this terminal normally feeds. Only specified for the terminals at head of feeders.

URI

cim:Terminal.NormalHeadFeeder

Cardinality

0..1

Type

Feeder

Inherited from

Terminal

OperationalLimitSet

The operational limit sets at the terminal.

URI

cim:ACDCTerminal.OperationalLimitSet

Cardinality

0..*

Type

OperationalLimitSet

Inherited from

ACDCTerminal

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

cim:Terminal.phases

Cardinality

0..1

Type

PhaseCode

Inherited from

Terminal

PinTerminal

URI

cim:Terminal.PinTerminal

Cardinality

0..*

Type

PinTerminal

Inherited from

Terminal

PropertiesCIMDataObject

The single CIM data object in the appropriate dataset context.

URI

cim:IdentifiedObject.PropertiesCIMDataObject

Cardinality

0..1

Type

ChangeSetMember

Inherited from

IdentifiedObject

RegulatingControl

The controls regulating this terminal.

URI

cim:Terminal.RegulatingControl

Cardinality

0..*

Type

RegulatingControl

Inherited from

Terminal

RemoteInputSignal

Input signal coming from this terminal.

URI

cim:Terminal.RemoteInputSignal

Cardinality

0..*

Type

RemoteInputSignal

Inherited from

Terminal

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

cim:ACDCTerminal.sequenceNumber

Cardinality

0..1

Type

integer

Inherited from

ACDCTerminal

SvPowerFlow

The power flow state variable associated with the terminal.

URI

cim:Terminal.SvPowerFlow

Cardinality

0..*

Type

SvPowerFlow

Inherited from

Terminal

TargetingCIMDataObject

Data objects registered.

URI

cim:IdentifiedObject.TargetingCIMDataObject

Cardinality

0..*

Type

ChangeSetMember

Inherited from

IdentifiedObject

TerminalConstraintTerm

URI

cim:MktTerminal.TerminalConstraintTerm

Cardinality

0..*

Type

TerminalConstraintTerm

TieFlow

The control area tie flows to which this terminal associates.

URI

cim:Terminal.TieFlow

Cardinality

0..*

Type

TieFlow

Inherited from

Terminal

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

cim:Terminal.TopologicalNode

Cardinality

0..1

Type

TopologicalNode

Inherited from

Terminal

TransformerEnd

All transformer ends connected at this terminal.

URI

cim:Terminal.TransformerEnd

Cardinality

0..*

Type

TransformerEnd

Inherited from

Terminal