IIDM ‐ XIIDM ‐ JIIDM 1.12 evolutions

Features

Automation systems: Overload management system

TODO

New "Ground" injection

TODO

Examples, in XIIDM

• In node/breaker topology:

<iidm:voltageLevel id="VL1" nominalV="400.0" topologyKind="NODE_BREAKER">
    <iidm:nodeBreakerTopology>
        <!-- ... -->
    </iidm:nodeBreakerTopology>
    <iidm:ground id="GroundNB" name="GroundNB" node="6"/>
</iidm:voltageLevel>

• In bus/breaker topology:

<iidm:voltageLevel id="VL2" nominalV="220.0" topologyKind="BUS_BREAKER">
    <iidm:busBreakerTopology>
        <!-- ... -->
    </iidm:busBreakerTopology>
    <iidm:ground id="GroundBB" name="GroundBB" bus="BUS2" connectableBus="BUS2"/>
</iidm:voltageLevel>

Ratio tap changers in reactive power control mode

Reactive power control mode was added to ratio tap changers:

• RTC regulationMode was introduced (with methods getRegulationMode / setRegulationMode). The possible values are VOLTAGE or REACTIVE_POWER;
• targetV becomes regulationValue(with methods getRegulationValue / setRegulationValue);
• getTargetV and setTargetV were kept as shortcuts as follows. They also ensure backward compatibility:
  • setTargetV automatically switches mode to VOLTAGE (if new targetV is not NaN);
  • getTargetV returns NaN if mode is not VOLTAGE.

Examples, in XIIDM

• In voltage control mode:

<iidm:ratioTapChanger lowTapPosition="0" tapPosition="1" targetDeadband="0.0" loadTapChangingCapabilities="true" regulating="true" regulationMode="VOLTAGE" regulationValue="158.0">
    <iidm:terminalRef id="NHV2_NLOAD" side="TWO"/>
    <iidm:step r="0.0" x="0.0" g="0.0" b="0.0" rho="0.85"/>
    <iidm:step r="0.0" x="0.0" g="0.0" b="0.0" rho="1.00"/>
    <iidm:step r="0.0" x="0.0" g="0.0" b="0.0" rho="1.15"/>
</iidm:ratioTapChanger>

• In reactive power control mode:

<iidm:ratioTapChanger regulating="true" lowTapPosition="0" tapPosition="0" targetDeadband="0.0" loadTapChangingCapabilities="true" regulationMode="REACTIVE_POWER" regulationValue="-10.0">
    <iidm:terminalRef id="T2wT" side="TWO"/>
    <iidm:step r="0.1089" x="0.01089" g="0.8264462809917356" b="0.08264462809917356" rho="0.9"/>
</iidm:ratioTapChanger>

Permanent limit mandatory in presence of temporary limits

It is now forbidden to create operational limits with temporary limits only, a permanent limit is required: an exception is thrown.

To provide backward compatibility with previous IIDM versions, when the permanent limit is missing and temporary limits are present, the following policy is applied:

• if there is a temporary limit with an infinite acceptable duration, its value is used as permanent limit and the said temporary limit is removed;
• else, the permanent limit is computed as a certain percentage of the minimum temporary limits' value: the default percentage is 100%; for IIDM/JIIDM imports, it could be changed using the iidm.import.xml.missing-permanent-limit-percentage parameter.

Changes

TODO or delete