Grid model extensions#

The grid model contains enough data to basically describe supported components and run power flow computations, but it may not be sufficient for more complex studies. The extensions are a way to add additional structured data to a piece of equipment to extend its features. The extensions can be attached to any objects of a network or to the network itself.

Some extensions are mono-variant, meaning the data are identical for all the variants of the network. However, some of them are multi-variants to allow a different value for each variant of the network. It’s typically the case for the LoadDetail extension that give the distribution of the constant part and the thermosensitive part of the consumption.

Note that some extensions provided by PowSyBl aren’t supported in the persistent implementation of IIDM.

Every extension is considered as serializable unless explicitly specified as non-serializable in XML-IIDM.

Active power control#

This extension is used to configure the participation factor of the generator, typically in the case of a load flow computation with distributed slack enabled (with balance type on generator). This extension is attached to a generator or a battery.

Attribute

Type

Unit

Required

Default value

Description

participate

boolean

-

yes

-

The participation status

droop

double

None (repartition key)

no

-

The participation factor equals maxP / droop

participation factor

double

None (repartition key)

no

-

Defines the participation factor explicitly

max targetP

double

MW

no

-

If defined, this limit is used for slack distribution instead of the generator’s maxP

min targetP

double

MW

no

-

if defined, this limit is used for slack distribution instead of the generator’s minP

Here is how to add an active power control extension to a generator:

generator.newExtension(ActivePowerControlAdder.class)
    .withParticipate(true)
    .withDroop(4)
    .withParticipationFactor(1.5)
    .add();

If defined, min targetP and max targetP must be in the [pMin, pMax] interval of the Generator or Battery. The participation status, the participation factor, the max targetP and the min targetP are multi-variants: they can vary from one variant to another.

This extension is provided by the com.powsybl:powsybl-iidm-extensions module.

Branch observability#

This extension models branch flow observability on both sides, obtained after a state estimation.

Attribute

Type

Unit

Required

Default value

Description

quality P1

ObservabilityQuality

MW

no

-

The observability quality of active power on side ONE

quality P2

ObservabilityQuality

MW

no

-

The observability quality of active power on side TWO

quality Q1

ObservabilityQuality

MVar

no

-

The observability quality of reactive power on side ONE

quality Q2

ObservabilityQuality

MVar

no

-

The observability quality of reactive power on side TWO

Observability quality

This extension contains the sub-object ObservabilityQuality.

Attribute

Type

Unit

Required

Default value

Description

standard deviation

double

MW or MVar

yes

-

The standard deviation

redundant

boolean

-

yes

-

Indicates if this value is confirmed by redundancy

This extension is provided by the com.powsybl:powsybl-iidm-extensions module.

Busbar section position#

This extension gives positions information about a busbar section. The busbarIndex gives the position of the busbar section relative to other busbar sections. The sectionIndex gives the position of the busbar section within the corresponding busbar. Note that a busbar is a set of busbar sections. Hence, the sections of the same busbar should have the same busbar index. The busbar indices induce an order of busbars within the voltage level, which usually reflects the busbars physical relative positions. Similarly, the section indices induce an order of sections of the same busbar, which usually reflects their physical relative position.

Connectable position#

This extension gives information about the relative position of connectables to each other in a voltage level. It also indicates the direction of the connectable relative to the busbar section to which it is connected. This is mainly used for visualization.

This extension is created by connectable, this information is available for each side of branches and three-winding transformers.

The attributes of the extension are given below:

Attribute

Type

Unit

Required

Default value

Description

feeder

Feeder

-

no

-

The information for an injection with only one side

feeder1

Feeder

-

no

-

The information on side 1 for a Branch or three-winding transformer

feeder2

Feeder

-

no

-

The information on side 2 for a Branch or three-winding transformer

feeder3

Feeder

-

no

-

The information on side 3 for a three-winding transformer

Depending on the type of connectable, the associated attribute should be filled out: only feeder for injections, feeder1 and feeder2 for branches and feeder1, feeder2 and feeder3 for three-winding transformers.

The attributes of the Feeder class, containing all the position information of the connectable relative to one voltage level, are:

Attribute

Type

Unit

Required

Default value

Description

name

String

-

yes

-

The name associated to the feeder. It is the name that will be displayed on diagrams.

order

Integer

-

no

-

The position of the connectable relative to the others

direction

ConnectablePosition.Direction

-

no

-

The direction of the connectable relative to its connected busbar section. Can be TOP or BOTTOM

Coordinated reactive control#

Some generators can be coordinated to control reactive power in a point of the network. This extension is used to configure the percentage of reactive-coordinated control that comes from a generator. This extension is attached to a generator.

Attribute

Type

Unit

Required

Default value

Description

QPercent

percent [0-100]

-

yes

-

The reactive control percent of participation

Here is how to add a coordinated reactive control extension to a generator:

generator.newExtension(CoordinatedReactiveControlAdder.class)
    .withQPercent(40)
    .add();

Please note that the sum of the \(qPercent\) values of the generators coordinating the same point of the network must be 100.

This extension is provided by the com.powsybl:powsybl-iidm-extensions module.

Discrete measurements#

This extension is used to store discrete measurements (such as tap positions, switch positions, etc.) collected in substations.

Attribute

Type

Unit

Required

Default value

Description

discreteMeasurements

Collection

-

no

-

Contains a collection of DiscreteMeasurement objects

The DiscreteMeasurement class characteristics are the following:

Attribute

Type

Unit

Required

Default value

Description

id

String

-

no

-

The ID of the discrete measurement if it exists

type

DiscreteMeasurement.Type

-

no

-

The type of discrete measurement (TAP_POSITION, SWITCH_POSITION, SHUNT_COMPENSATOR_SECTION, OTHER)

tapChanger

DiscreteMeasurement.TapChanger

-

no

-

The tap changer the discrete measurement is applied on (null if the measurement is not applied to a tap changer)

properties

Map<String, String>

-

no

-

The properties (name and value) associated with the discrete measurement

valueType

DiscreteMeasurement.ValueType

-

no

-

The discrete measurement value type (BOOLEAN, INT or STRING)

value

Object

-

no

-

The discrete measurement value

valid

boolean

-

no

-

The validity status (if true, the discrete measured value cannot be null)

ENTSO-E area#

TODO

HVDC angle droop active power control#

This is an extension dedicated to DC line in order to model AC emulation. For a VSC converter station operating in AC emulation, its active power setpoint is given by

\[P = P0 + k~(ph1 - ph2)\]

Attribute

Type

Unit

Required

Default value

Description

P0

float

MW

yes

-

P0 in the equation

droop

float

MW by degree

yes

-

k in the equation

enabled

boolean

-

yes

-

if the AC emulation is active or not

HVDC operator active power range#

This extension enables to replace the operational limits of a DC line in AC emulation. In that case, the VSC converter stations min active power and max active power are not used.

Generator ENTSO-E category#

TODO

Generator short-circuit#

This extension models the generator data used for short-circuit calculations. Depending on the type of short-circuit study to be performed, either the transient or the sub-transient reactance should be filled. The reactance of the step-up transformer should be filled if the generator has a transformer that is not directly modeled in the network.

Attribute

Type

Unit

Required

Default value

Description

directTransX (X’d)

double

Ω

yes

-

Direct transient reactance of the generator

directSubtransX (X’’d)

double

Ω

no

-

Direct sub-transient reactance of the generator

stepUpTransformerX

double

Ω

no

-

Reactance of the step-up transformer

This extension is provided in the com.powsybl:powsybl-iidm-extensions module.

To add this extension to a generator, the code to be used is:

generator.newExtension(GeneratorShortCircuitAdder.class)
    .withDirectTransX(20)
    .withDirectSubtransX(14)
    .withStepUpTransformerX(10)
    .add();

Battery short-circuit#

This extension models the battery data used for short-circuit calculations. Depending on the type of short-circuit study to be performed, either the transient or the sub-transient reactance should be filled. The step-up transformer reactance should be filled if the battery has a transformer that is not directly modeled on the network.

Attribute

Type

Unit

Required

Default value

Description

directTransX (X’d)

double

Ω

yes

-

Direct transient reactance of the battery

directSubtransX (X’’d)

double

Ω

no

-

Direct sub-transient reactance of the battery

stepUpTransformerX

double

Ω

no

-

Reactance of the step-up transformer

This extension is provided in the com.powsybl:powsybl-iidm-extensions module.

To add this extension to a battery, the code to be used is:

battery.newExtension(BatteryShortCircuitAdder.class)
    .withDirectTransX(20)
    .withDirectSubtransX(14)
    .withStepUpTransformerX(10)
    .add();

Identifiable short-circuit#

This extension models the maximum and minimum short-circuit current admissible for any identifiable.

Attribute

Type

Unit

Required

Default value

Description

ipMin

double

A

no

-

The minimum admissible current

ipMax

double

A

yes

-

The maximum admissible current

This extension is provided in the com.powsybl:powsybl-iidm-extensions module.

To add this extension to a bus, for example, the code to be used is:

bus.newExtension(IdentifiableShortCircuitAdder.class)
    .withIpMin(3000)
    .withIpMax(10000)
    .add();

The code is similar for every identifiable.

Injection observability#

This extension models injection flow observability, obtained after a state estimation.

Attribute

Type

Unit

Required

Default value

Description

quality P

ObservabilityQuality

MW

no

-

The observability quality of active power

quality Q

ObservabilityQuality

MVar

no

-

The observability quality of reactive power

Observability quality

This extension contains the sub-object ObservabilityQuality.

Attribute

Type

Unit

Required

Default value

Description

standard deviation

double

MW or MVar

yes

-

The standard deviation

redundant

boolean

-

yes

-

Indicates if the value is confirmed by redundancy

This extension is provided by the com.powsybl:powsybl-iidm-extensions module.

Line Position#

This extension is attached to a Line and is used to store the geographical coordinates of the Line. The coordinates are stored using latitude and longitude. The extension consists of a list of coordinates that can be used to trace the line on a map.

Attribute

Type

Unit

Required

Default value

Description

coordinates

list<Coordinate>

-

yes

-

The list of points coordinates forming the line

Example of code to get the coordinates of a line :

List<Coordinate> stationCoordinates = network.getLine("L1").getExtension(LinePosition.class)
    .getCoordinates();

This extension is provided in the module com.powsybl:powsybl-iidm-extensions.

When adding the extension, the LinePositionAdder extension should be used.

Example of code to add the extension:

Line line = network.getLine("L1");
line.newExtension(LinePositionAdder.class)
    .withCoordinates(List.of(new Coordinate(48, 2), new Coordinate(48.1, 2.1)))
    .add();

Load asymmetrical#

A balanced load is described by its active power setpoint \(P0\) and its reactive power setpoint \(Q0\). This extension is used to describe the power asymmetry for each ABC phase. In the three-phase representation, the complex power injected at a bus \(i\) is constant for each phase and represented by three complex values:

\[\begin{split} \begin{align} S_{Ai_{Load}}=S_{A}=P_{A}+j.Q_{A} \\ S_{Bi_{Load}}=S_{B}=P_{B}+j.Q_{B} \\ S_{Ci_{Load}}=S_{C}=P_{C}+j.Q_{C} \\ \end{align} \end{split}\]

But for a balanced load flow, the constant power load \(P\) and \(Q\) refer to the positive sequence load. Given that, in balanced conditions, the load for zero and negative sequences should always be zero. However, in real life, power loads are better defined in the ABC three-phase representation. The load extension addresses this issue keeping the default behavior for balanced conditions.

Balanced load flow conditions:

In balanced conditions given the load at bus:

\[ S_{1i_{Load}}=P_{Load}+j.Q_{Load} \]

We must verify:

\[ 0 = -S_{1i_{Load}} +\sum_{j=\delta(i)}^{} S_{1ij} \]

Unbalanced load flow conditions:

We must take into account that many loads are still balanced and information related to balanced loads is sufficient. The extension proposes a delta approach where unbalances are expressed in the extension. Supposing that:

\[ \begin{align} \Delta P_{Ai_{Load}}, \Delta Q_{Ai_{Load}}, \Delta P_{Bi_{Load}}, \Delta Q_{Bi_{Load}}, \Delta P_{Ci_{Load}}, \Delta Q_{Ci_{Load}} \end{align} \]

are provided in input through the extension. The three-phase power values used as inputs of an unbalanced load flow calculation are:

\[\begin{split} \begin{align} S_{Ai_{Load}}=(P_{Load}+\Delta P_{Ai_{Load}})+j.(Q_{Load}+\Delta Q_{Ai_{Load}}) \\ S_{Bi_{Load}}=(P_{Load}+\Delta P_{Bi_{Load}})+j.(Q_{Load}+\Delta Q_{Bi_{Load}}) \\ S_{Ci_{Load}}=(P_{Load}+\Delta P_{Ci_{Load}})+j.(Q_{Load}+\Delta Q_{Ci_{Load}}) \\ \end{align} \end{split}\]

As a consequence, if no extension provided for the load, the unbalanced load flow will use in input:

\[\begin{split} \begin{align} S_{Ai_{Load}}=P_{Load}+j.Q_{Load} \\ S_{Bi_{Load}}=P_{Load}+j.Q_{Load} \\ S_{Ci_{Load}}=P_{Load}+j.Q_{Load} \\ \end{align} \end{split}\]

Attribute

Type

Unit

Required

Default value

Description

deltaPa

double

MW

No

0

The unbalanced part of the active power setpoint at phase A (balanced parts for each phase are described by its active power setpoint \(P0\) and its reactive power setpoint \(Q0\))

deltaQa

double

MVar

No

0

The unbalanced part of the reactive power setpoint at phase A

deltaPb

double

MW

No

0

The unbalanced part of the active power setpoint at phase B

deltaQb

double

MVar

No

0

The unbalanced part of the reactive power setpoint at phase B

deltaPc

double

MW

No

0

The unbalanced part of the active power setpoint at phase C

deltaQc

double

MVar

No

0

The unbalanced part of the reactive power setpoint at phase C

Here is how to add a load detail extension to a load:

load.newExtension(LoadAsymmetricalAdder.class)
        .withDeltaPa(-1)
        .withDeltaQa(1)
        .withDeltaPb(-2)
        .withDeltaQc(2)
        .add();

This extension is provided by the com.powsybl:powsybl-iidm-extensions module.

Load detail#

A load is described by its active power setpoint \(P0\) and its reactive power setpoint \(Q0\). This extension is used to detail :

  • In the total amount of active power what is fixed and what is time-dependent (also called variable). The time-dependent part can be adjusted for production equals consumption.

  • In the total amount of reactive power what is fixed and what is time-dependent (also called variable).

Attribute

Type

Unit

Required

Default value

Description

variableActivePower

double

MW

yes

-

The part of the active power setpoint that is considered variable

fixedActivePower

double

MW

yes

-

The part of the active power setpoint that is considered constant

variableReactivePower

double

MVar

yes

-

The part of the reactive power setpoint that is considered variable

fixedReactivePower

double

MVar

yes

-

The part of the reactive power setpoint that is considered constant

Here is how to add a load detail extension to a load:

load.newExtension(LoadDetailAdder.class)
    .withVariableActivePower(40)
    .withFixedActivePower(20)
    .withVariableReactivePower(5)
    .withFixedReactivePower(2)
    .add();

All of this extension’s attributes are multi-variants: they can vary from one variant to another.

This extension is provided by the com.powsybl:powsybl-iidm-extensions module.

Measurements#

This extension is used to store measurements collected in substations.

Attribute

Type

Unit

Required

Default value

Description

measurements

Collection

-

no

-

Contains a collection of Measurement objects

The Measurement class characteristics are the following:

Attribute

Type

Unit

Required

Default value

Description

id

String

-

no

-

The ID of the measurement if it exists

type

Measurement.Type

-

no

-

The type of measurement (ANGLE, ACTIVE_POWER, VOLTAGE etc.)

properties

Map<String, String>

-

no

-

The properties (name and value) associated with the measurement

value

double

-

no

-

The measurement value

standardDeviation

double

-

no

-

The standard deviation (NaN if not specified)

valid

boolean

-

no

-

The validity status (if true, the measured value cannot be NaN)

side

ThreeSides

-

no

-

The equipment side associated to the measurement

Operating status#

This is an extension of Identifiable, but it is restricted to some identifiable types: busbar sections, all branches, three-winding transformers, HVDC line and a dangling line. The status could be:

  • IN_OPERATION: equipment in service.

  • PLANNED_OUTAGE: outage due to an unscheduled putting out of service of the equipment.

  • FORCED_OUTAGE: outage due to a programmed taking out of service of the equipment.

Reference Priority#

This extension is attached to a Generator, or a BusBarSection or a Load and is used to define the angle reference bus of a power flow calculation, i.e. which bus will be used with a zero-voltage angle. Use this extension before a computation to force the reference bus selection. The support of this feature by Load Flow implementations may vary. For example, the OpenLoadFlow implementation today supports Reference Priorities on generators only when this feature is activated.

The reference bus is defined through the terminal of the equipment and an integer specifying the reference priority. 0 means “do not use as reference”, 1 is “highest priority”, 2 “second priority”, etc.

Attribute

Type

Unit

Required

Default value

Description

Terminal

Terminal

-

yes

-

The reference terminal

Priority

Integer

-

yes

0

The reference priority

ReferencePriority.set(generator, 1);

int priority = ReferencePriority.get(generator); // note: returns zero if none defined

This extension is provided by the com.powsybl:powsybl-iidm-api module.

Reference Terminals#

This extension is attached to a Network and is used to define the angle references of a Power Flow solution. The support of this feature by Load Flow implementations may vary. For example, the OpenLoadFlow implementation today supports writing to the Network the terminals of the reference generators chosen via the Reference Priority extension.

The reference bus is defined through the terminal of the equipment and an integer specifying the reference priority. 0 means “do not use as reference”, 1 is “highest priority”, 2 “second priority”, etc.

Attribute

Type

Unit

Required

Default value

Description

terminals

Set<Terminal>

-

yes

-

The reference terminals

Set<Terminal> referenceTerminals = ReferenceTerminals.getTerminals(network);

ReferenceTerminals.reset(network);

ReferenceTerminals.add(terminal);

This extension is provided by the com.powsybl:powsybl-iidm-api module.

Remote reactive power control#

This extension is used for generators with a remote reactive control.

Attribute

Type

Unit

Required

Default value

Description

enabled

boolean

-

yes

-

If the reactive remote control is activated of not

targetQ

double

MVar

yes

-

The targetQ at remote regulating terminal

regulatingTerminal

Terminal

-

yes

-

The regulating terminal

Slack terminal#

This extension is attached to a voltage level and is used to define the slack bus of a power flow calculation i.e. which bus will be used to balance the active and reactive power in load flow analysis. Use this extension before a computation to force the slack bus selection. You should enable default load flow parameter isReadSlackBus. Use this extension after a computation to attach to the network the slack bus that has been selected by the load flow engine (one by connected component). You should enable default load flow parameter isWriteSlackBus.

The slack bus is defined through the terminal of a connectable that belongs to the bus. It is totally allowed to define a disconnected terminal as slack as the connectable could be reconnected during a grid study.

Attribute

Type

Unit

Required

Default value

Description

Terminal

Terminal

-

yes

-

The slack terminal

SlackTerminal.attach(bus);

This extension is provided by the com.powsybl:powsybl-iidm-api module.

Substation Position#

This extension is attached to a Substation and is used to store the geographical coordinates of the Substation. The coordinates are stored using latitude and longitude.

Attribute

Type

Unit

Required

Default value

Description

coordinate

Coordinate

-

yes

-

The latitude and longitude of the substation

Example of code to get the coordinates of a substation :

Coordinate stationCoordinate = network.getSubstation("P1").getExtension(SubstationPosition.class)
    .getCoordinate();

This extension is provided in the module com.powsybl:powsybl-iidm-extensions.

When adding the extension, the SubstationPositionAdder extension should be used.

Example of code to add the extension:

Substation station = network.getSubstation("P1");
station.newExtension(SubstationPositionAdder.class)
        .withCoordinate(new Coordinate(48, 2))
        .add();

Three-winding transformer phase angle clock#

This extension is used to model the Vector Group of a three-winding transformer. The phase angle clock could be modeled at leg 2, leg 3 or both legs 2 and 3 and of a three-winding transformer (network side). The voltage phase angle displacement is represented with clock hours. The valid values are 0 to 11. This extension is attached to a three-winding transformer.

Attribute

Type

Unit

Required

Default value

Description

PhaseAngleClockLeg2

int [0-11]

hours

yes

-

The voltage phase angle displacement at leg 2

PhaseAngleClockLeg3

int [0-11]

hours

yes

-

The voltage phase angle displacement at leg 3

transformer.newExtension(ThreeWindingsTransformerPhaseAngleClock.class)
    .withPhaseAngleClockLeg2(10)
    .withPhaseAngleClockLeg3(1)
    .add();

This extension is provided by the com.powsybl:powsybl-iidm-extensions module.

Three-winding transformer to be estimated#

This extension is used to indicate if a three-winding transformer tap changer is to be estimated during a state estimation, i.e., if its tap position should be an output of the state estimation.

  • The three-winding transformer model offers the possibility to have up to 3 ratio tap changers and up to 3 phase tap changers. Each tap changer can be estimated or not.

  • If a tap changer is not to be estimated, it should not be changed during a state estimation (its tap position is merely an input of the state estimation).

Attribute

Type

Unit

Required

Default value

Description

NAME

String

-

yes

threeWindingsTransformerToBeEstimated

Name of the extension

Example of code to get the status of the n°1 phase tap changer:

3wt.getExtension(ThreeWindingsTransformerToBeEstimated.class).shouldEstimatePhaseTapChanger1();

This extension is provided in the module com.powsybl:powsybl-iidm-extensions.

When adding the extension, the ThreeWindingsTransformerToBeEstimatedAdder extension should be used.

Example of code to add the extension:

transformer.newExtension(ThreeWindingsTransformerToBeEstimatedAdder.class)
        .withRatioTapChanger1Status(true)
        .add();

Two-winding transformer phase angle clock#

This extension is used to model the Vector Group of a two-winding transformer. The phase angle clock is modeled at side 2 of a two-winding transformer. The voltage phase angle displacement is represented with clock hours. The valid values are 0 to 11. This extension is attached to a two-winding transformer.

Attribute

Type

Unit

Required

Default value

Description

PhaseAngleClock

int [0-11]

hours

yes

-

The voltage phase angle displacement

transformer.newExtension(TwoWindingsTransformerPhaseAngleClockAdder.class)
    .withPhaseAngleClock(3)
    .add();

This extension is provided in the module com.powsybl:powsybl-iidm-extensions.

Two-winding transformer to be estimated#

This extension is used to indicate if a two-winding transformer tap changer is to be estimated during a state estimation, i.e., if its tap position should be an output of the state estimation.

  • A two-winding transformer has a ratio tap changer and/or a phase tap changer. Each tap changer can be estimated or not.

  • If a tap changer is not to be estimated, it should not be changed during a state estimation (its tap position is merely an input of the state estimation).

Attribute

Type

Unit

Required

Default value

Description

NAME

String

-

yes

twoWindingsTransformerToBeEstimated

Name of the extension

Example of code to get the status of the ratio tap changer:

2wt.getExtension(TwoWindingsTransformerToBeEstimated.class).shouldEstimateRatioTapChanger();

This extension is provided in the module com.powsybl:powsybl-iidm-extensions.

When adding the extension, the TwoWindingsTransformerToBeEstimatedAdder extension should be used.

Example of code to add the extension:

Example of code:

transformer.newExtension(TwoWindingsTransformerToBeEstimatedAdder.class)
        .withPhaseTapChangerStatus(true)
        .add();

Voltage per reactive power control#

This extension is used to model voltage control of static VAR compensators. This extension is attached to a static VAR compensator.

Attribute

Type

Unit

Required

Default value

Description

Slope

double

kV per MVar

yes

-

The sensibility of the voltage with respect to reactive power

When this extension is present and the slope greater than zero, the reactive output of the static VAR compensator is defined by:

\[Q = \dfrac{VoltageSetpoint - V}{slope}\]

where \(V\) is the voltage at regulating terminal and \(VoltageSetpoint\) the target value in voltage given as attribute in a static VAR compensator.

Here is how to add a voltage per reactive power control extension to a static VAR compensator:

svc.newExtension(VoltagePerReactivePowerControlAdder.class)
    .withSlope(0.5)
    .add();

This extension is provided by the com.powsybl:powsybl-iidm-extensions module.