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'.
-
Xnode "tieLineSubstationEnd" is realized by Name.name with a NameType=tieLineSubstationEnd. The naming convention (up to 32 chars): Substation name (From end) “-” Substation name (To end). Example: Albertirsa-Zakhidnoukrainska
-
Xnode "borderName" is realized by Name.name with a NameType.name="borderName". The naming convention (fixed 5 chars): ISO country code (From end) “-” ISO country code (To end). Example: HU-UA. In case of more than one TSO in the country or a tie-line between two regions within a TSO area the ISO code From and the ISO code To is the same. Example: DE-DE.
-
Xnode "tieLineTSOName" is realized by Name.name with a NameType.name = "tieLineTSOName". The naming convention (up to 32 chars): TSO name (From end) “-” TSO name (To end). Example: Mavir-Ukrenergo
-
all XNode names are required for boundary MAS : name, energyIdentCodeEIC, borderName, tieLineSubstationEnd, tieLineTSOName
-
Xnode "energyIdentCodeEIC" is realized by Name.name with a NameType.name = "energyIdentCodeEIC".
|
name |
1..1 |
|
||
|---|---|---|---|---|
|
IdentifiedObject |
1..1 |
|
||
|
NameType |
1..1 |
|
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".
|
BaseVoltage |
1..1 |
|
|---|
|
name |
1..1 |
see IdentifiedObject |
|---|
|
baseURI |
1..1 |
FixedValue=http://iec.ch/TC57/61970-456/TopologyBoundary/1 |
|
|
|---|---|---|---|---|
|
date |
1..1 |
FixedValue=2011-06-20 |
|
|
|
URI |
1..1 |
FixedValue=http://www.entsoe.eu/profile/TopologyBoundary/Edition2_v3 |
|
|
|
version |
1..1 |
DefaultValue=Entsoe_TopologyBoundary_Edition2.v3 |
|
This is a root class to provide common identification for all classes needing identification and naming attributes
-
IdentifiedObject.name naming convention - it is up to 12 chars Xnode code agreed between the two parties responsible for the tie-line
|
name |
1..1 |
|
|---|
This is the IEC 61970 CIM version number assigned to this UML model.
|
date |
0..1 |
FixedValue=2011-07-07 |
|
|
|---|---|---|---|---|
|
version |
0..1 |
FixedValue=IEC61970CIM15v31 |
|
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.
-