Profile Documentation

r0PerR	1..1	Simple_Float		The ratio of zero sequence resistance to positive sequence resistance.
sShortCircuit	1..1	ApparentPower		The short circuit apparent power drawn at this node when faulted.
x0PerX	1..1	Simple_Float		The ratio of zero sequence reactance per positive sequence reactance.
xPerR	1..1	Simple_Float		Ratio of positive sequence reactance per postive sequence resistance.
TopologicalNode	1..1	TopologicalNode	The topological node associated with the short circuit state.

inService	1..1	Boolean		The in service status as a result of topology processing.
ConductingEquipment	1..1	ConductingEquipment	The conducting equipment associated with the status state.

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'.

-
TopologicalIsland does not use description. But description could be used by the tools to exchange specific information needed by the tools. (Name.name is the text of the description with a NameType.name="description")

Native Members

name	1..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.

SvInjection

StateVariables

Injection state variable. Used for addressing situations where the exchanged models have a Kirchof's law mismatch at a bus. This includes exchange of partial models with boundary flows and state estimator solutions with residual mismatch.

-
SvInjection represents the flow through the TieLine at X-Node (boundary files). Parameters of SvInjection classes are set to zero when State Variables file covers multiple MAS and if a tie-line is connected. It is not necessary that the SvInjection is set to zero at the time of the import. Additional functions should be made available for users to cover all necessary use cases when dealing with TSO MAS and Boundary MAS.

Native Members

pNetInjection	1..1	ActivePower		The active power injected into the bus at this location. Positive sign means injection into the bus.
qNetInjection	0..1	ReactivePower		The reactive power injected into the bus at this location. Positive sign means injection into the bus.
TopologicalNode	1..1	TopologicalNode	The topological node associated with the state injection.

SvPowerFlow

StateVariables

State variable for power flow. Load convention is used for flow direction. This means flow out from the TopologicalNode into the equipment is positive.

Native Members

p	1..1	ActivePower		The active power flow. Load sign convention is used, i.e. positive sign means flow out from a node.
q	1..1	ReactivePower		The reactive power flow. Load sign convention is used, i.e. positive sign means flow out from a node.
Terminal	1..1	Terminal	The terminal associated with the power flow state.

SvShuntCompensatorSections

StateVariables

State variable for the number of sections in service for a shunt compensator.

Native Members

sections	1..1	Simple_Float		The number of sections in service as a continous variable. To get integer value scale with ShuntCompensator.bPerSection.
ShuntCompensator	1..1	ShuntCompensator	The shunt compensator for which the state applies.

SvTapStep

StateVariables

State variable for transformer tap step. This class is to be used for taps of LTC (load tap changing) transformers, not fixed tap transformers. Normally a profile specifies only one of the attributes "position"or "tapRatio".

Native Members

position	1..1	Simple_Float		The floating point tap position. To get integer value scale with range and round off.
TapChanger	1..1	TapChanger	The tap changer associated with the tap step state.

SvVoltage

StateVariables

State variable for voltage.

Native Members

angle	1..1	AngleDegrees		The voltage angle in degrees of the topological node.
v	1..1	Voltage		The voltage magnitude of the topological node.
TopologicalNode	1..1	TopologicalNode	The topological node associated with the voltage state.

TopologicalIsland

Topology

An electrically connected subset of the network. Topological islands can change as the current network state changes: e.g. due to
- disconnect switches or breakers change state in a SCADA/EMS
- manual creation, change or deletion of TopologicalNodes in a planning tool.

-
The angle reference node is the TopologicalNode to which a synchronous machine is connected and referenced from TopologicalIsland.AngleRef_TopologicalNode

Native Members

AngleRef_TopologicalNode	1..1	TopologicalNode	The angle reference for the island. Normally there is one TopologicalNode that is selected as the angle reference for each island. Other reference schemes exist, so the association is typically optional. But for Entso-E, the association is required.

Inherited Members

Inheritance pass: ->IdentifiedObject

name	1..1	String		see IdentifiedObject

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".

-
In the SV profile, TopologicalNode.TopologicalIsland is defined. But there is no need to include this in the instance file. The SV profile does not require to put instances of TopologicalNode into the SV File, so the TopologicalNode.TopologicalIsland need not be an optional association in SV profile.
The "required" [1..1] multiplicity on an attribute or association (as for TopologicalNode.TopologicalIsland) is suggesting that if an instance of the containing class is included in the message, then the attribute or association must be present. It says nothing about whether or not the instance of TopologicalNode is required in the file.

Native Members (ShortCircuit)

Native Members

TopologicalIsland	1..1	TopologicalIsland	A topological node belongs to a topological island.

Abstract Classes

ConductingEquipment

Core

The parts of the power system that are designed to carry current or that are conductively connected through terminals.

Native Members (Operation)

EntsoeStateVariablesProfileVersion

EntsoeStateVariablesProfile

Profile version details

Native Members

baseURI	1..1	String	DefaultValue=http://iec.ch/TC57/61970-456/StateVariables/2	Profile URI used in the Model Exchange header. It uniquely identifies the Profile and its version. It matches URI used for CPSM.
date	0..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/StateVariables2_v19	Entso-E profile URI
version	1..1	String	FixedValue=Entsoe_StateVariables_Edition2_v19	Profile version

IdentifiedObject

Core

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

-
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.

-
IdentifiedObject.name is 32 characters max

-
TopologicalIsland does not use name. But name could be used by the tools to exchange specific information needed by the tools.

Native Members

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

IEC61970CIMVersion

EntsoeStateVariablesProfile

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

-
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.

Native Members

ShuntCompensator

Wires

A shunt capacitor or reactor or switchable bank of shunt capacitors or reactors. A section of a shunt compensator is an individual capacitor or reactor. A negative value for reactivePerSection indicates that the compensator is a reactor. ShuntCompensator is a single terminal device. Ground is implied.

Native Members

TapChanger

Wires

Mechanism for changing transformer winding tap positions.

Native Members

Terminal

Core

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

Native Members

Enumerations

Compound types

Datatypes

Simple_Float

EntsoeDomainProfile

A floating point number. The range is unspecified and not limited.

-
In ENTSO-E profile, Simple_Float range is the IEEE754 simple precision floating point one. It correspond to xs:float datatype

value	1..1	Float	Constraint=>choice=simple