ConnectivityNode

Core

Connectivity nodes are points where terminals of conducting equipment are connected together with zero impedance.

Native Members

TopologicalNode	0..1	TopologicalNode	Several ConnectivityNode(s) may combine together to form a single TopologicalNode, depending on the current state of the network.

Name

Core

The Name class provides the means to define any number of human readable names for an object. A name is not to be used for defining inter-object relationships. For inter-object relationships instead use the object identification 'mRID'.

-
When associated NameType.name = "energyIdentCodeEIC", Name.name is used to hold the EIC code (formerly generated by ETSO; now it is under ENTSO-E authority). In this case, the Name.name is optional in the profile to support specifying this only where appropriate

-
When associated NameType.name = "description", Name.name is used to hold the description of the class. In this case, it is a free text 256 characters (example: new configuration long term only). By agreement the first 8 characters of 256 available characters contain the Node code string as defined by UCTE DEF (version 2: 2007.05.01). This is valid some of the ENTSO-E Regional Groups which used UCTE DEF.

Native Members

name	0..1	String		Any free text that name the object.
NameType	1..1	NameType	Type of this name.
IdentifiedObject	1..1	IdentifiedObject	Identified object that this name designates.

Terminal

Core

An electrical connection point to a piece of conducting equipment. Terminals are connected at physical connection points called "connectivity nodes".

Native Members

connected	0..1	Boolean		The connected status is related to a bus-branch model and the TopologicalNode-Terminal relation. True implies the Terminal is connected to the related TopologicalNode 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 TopologicalNode-Terminal relation. A valid case is that ConductingEquipment can be connected in one end and open in the other. In particular for an ACLineSegment where the charging can be significant this is a relevant case.
TopologicalNode	1..1	TopologicalNode	The terminals associated with the topological node. This can be used as an alternative to the connectivity node path to terminal, thus making it unneccesary to model connedtivity nodes in some cases. Note that the if connectivity nodes are in the model, this association would proably not be used.

TopologicalNode

Topology

For a detailed substation model a TopologicalNode is a set of connectivity nodes that, in the current network state, are connected together through any type of closed switches, including jumpers. Topological nodes changes as the current network state changes (i.e., switches, breakers, etc. change state).
For a planning model switch statuses are not used to form TopologicalNodes. Instead they are manually created or deleted in a model builder tool. TopologialNodes maintained this way are also called "busses".

-
Naming convention : TopologicalNode must be under a VoltageLevel

-
The attribute name is a node code or a node number which must be unique within the substation or voltage level (2 characters max)

Native Members

BaseVoltage	1..1	BaseVoltage	The base voltage of the topologocial node.
ConnectivityNodeContainer	1..1	ConnectivityNodeContainer	The connectivity node container to which the toplogical node belongs.

Inherited Members

Inheritance pass: ->IdentifiedObject

name	1..1	String		see IdentifiedObject

BaseVoltage

Core

Defines a system base voltage which is referenced.

-
BaseVoltage is an abstract class. It is used here to generate the TopologicalNode.BaseVoltage association that is a pointer to BaseVoltage concrete class in the Equipment Profile

Native Members

ConnectivityNodeContainer

Core

A base class for all objects that may contain ConnectivityNodes or TopologicalNodes.

-
ConnectivityodeContainer is an abstract class. It is used here to generate the TopologicalNode.ConnectivityNodeContainer association that is a pointer to ConnectivityNodeContainer concrete subclasses in the Equipment Profile

Native Members

EntsoeTopologyProfileVersion

EntsoeTopologyProfile

Profile version details

-
EntsoeTopologyProfileVersion is an abstract class that is not exchanged. It holds all information on Topology profile version

Native Members

baseURI	1..1	String	DefaultValue=http://iec.ch/TC57/61970-456/Topology/2	Profile URI used in the Model Exchange header. It uniquely identifies the Profile and its version. It matches URI used for CPSM.
date	1..1	Date	FixedValue=2011-07-16	Profile creation date Form is YYYY-MM-DD for example for January 5, 2009 it is 2009-01-05.
URI	1..1	String	FixedValue=http://www.entsoe.eu/profile/Topology/Edition2_v19	Entso-E profile URI
version	1..1	String	FixedValue=Entsoe_Topology_Edition2_v19	Profile version

IdentifiedObject

Core

This is a root class to provide common identification for all classes needing identification and naming attributes

-
IdentifiedObject.name for topology is a two characters string

-
The attribute “name” inherited by many classes from the abstract class IdentifiedObject is not required to be unique. Software developers should not count on this to link the power system model.

Native Members

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

IEC61970CIMVersion

EntsoeTopologyProfile

This is the IEC 61970 CIM version number assigned to this UML model file.

-
IEC61970Version is an abstract class that is not exchanged. It holds all information on the CIMVersion the topology profile version is based on

-
The CIM base URI is "http://iec.ch/TC57/2010/CIM-schema-cim15#"

Native Members

date	0..1	Date	FixedValue=2011-07-07	Form is YYYY-MM-DD for example for January 5, 2009 it is 2009-01-05.
version	0..1	String	FixedValue=IEC61970CIM15v31	Form is IEC61970CIMXXvYY where XX is the major CIM package version and the YY is the minor version. For ecample IEC61970CIM13v18.

NameType

Core

Type of name. Possible values for attribute 'name' are implementation dependent but standard profiles may specify types. An enterprise may have multiple IT systems each having its own local name for the same object, e.g. a planning system may have different names from an EMS. An object may also have different names within the same IT system, e.g. localName and aliasName as defined in CIM version 14. Their definitions from CIM14 are
The localName is a human readable name of the object. It is only used with objects organized in a naming hierarchy. localName: A free text name local to a node in a naming hierarchy similar to a file directory structure. A power system related naming hierarchy may be: Substation, VoltageLevel, Equipment etc. Children of the same parent in such a hierarchy have names that typically are unique among them.
aliasName: A free text alternate name typically used in tabular reports where the column width is limited.

-
NameType.name could have two values "description" or "energyIdentCodeEIC". This gives the meaning of associated Name.name

Native Members