> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/model-and-simulation/import-models-from-external-software-or-code/import-from-powerfactory/compatibility-and-limitations.md).

# Compatibility & Limitations

This page describes the supported **PowerFactory** components and features when importing a network model into **HYPERSIM**, as well as the known limitations and constraints.

## Network components <a href="#network-components" id="network-components"></a>

### Nodes <a href="#nodes" id="nodes"></a>

<table><thead><tr><th width="180.25">PowerFactory Component</th><th>Supported Features</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><strong>Terminal (<code>ElmTerm</code>)</strong></td><td><ul><li>ABC phase technology</li><li>Load flow results (i.e., voltage magnitude and phase angle)</li><li><p><strong>Short-Circuit Event</strong> (<code>EvtShc</code>) on a terminal</p><ul><li>Three-phase, two-phase or single-phase.</li><li>Fault clearing event to specify “duration” of the fault.</li></ul></li></ul></td><td><ul><li>All terminals, regardless of their usage (i.e., busbar, junction node or internal node), are imported as buses.</li><li>Short-circuit events with fault reactance are not supported.</li><li>Buses can’t include a “__” (double underscore) in their name, when switches are imported (either through the <em>All switches are added option</em> or the <em>Only switches with events are added</em> option)..</li></ul></td></tr></tbody></table>

### Branches <a href="#branches" id="branches"></a>

## Switches <a href="#switches" id="switches"></a>

<table><thead><tr><th width="180.25">PowerFactory Component</th><th>Supported Features</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><strong>Switch (<code>StaSwitch</code>)</strong></td><td><ul><li>Current state (open/closed)</li><li><p>Event-related data (through associated <strong>Switch Event</strong>)</p><ul><li>Action, execution time and affected phases</li></ul></li></ul></td><td><ul><li>Trigger opening always assumed to be at Current zero crossing (default for both Simulation RMS and EMT).</li></ul><p>Known unsupported features:</p><ul><li>Breaker opening time from TypSwitch</li><li>Per-phase operation delay from “scatter” option</li><li>Transient recovery voltage (TRV) envelope</li></ul></td></tr><tr><td><strong>Breaker/Switch (<code>ElmCoup</code>)</strong></td><td><ul><li>3-Phase Breaker/Switch (without neutral)</li></ul></td><td><p>Known unsupported features:</p><ul><li>Breaker opening time from TypSwitch</li><li>Event-related data (through associated <strong>Switch Event</strong>)</li><li>Per-phase operation delay from “scatter” option</li><li>Transient recovery voltage (TRV) envelope</li></ul></td></tr></tbody></table>

## Lines and Other Non-Transformer Branches <a href="#lines-and-other-non-transformer-branches" id="lines-and-other-non-transformer-branches"></a>

<table><thead><tr><th width="180.25">PowerFactory Component</th><th>Supported Features</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><strong>Line (<code>ElmLne</code>)</strong></td><td><ul><li>Lumped parameter type (PI model)</li><li>Positive sequence model</li><li>Zero sequence model</li><li>Parallel lines</li></ul></td><td><ul><li>Base impedance for PU computations requires the rated voltage parameter (<em>uline</em>) which is only available from Line Type objects (<code>TypLne</code>). This means that lines with other types, such as tower type, geometry tower type, or cable definition, are currently not supported.</li></ul></td></tr><tr><td><strong>Common Impedance (<code>ElmZpu</code>)</strong></td><td><ul><li>3-Phase Model</li><li>Impedance and admittance values in negative sequence equal to those in positive sequence (i.e., z2 = z1 and y2 = y1).</li><li><strong>Case 1</strong>: Positive Sequence without admittance terms and zij = zji</li><li><strong>Case 2</strong>: Positive Sequence without admittance terms and zij != zji</li><li><strong>Case 3</strong>: Zero Sequence included, zij = zji, bj = bi and bj0 = bi0.</li></ul></td><td><ul><li>Conductance parameters (i.e. gi, gj, gi0, gj0) are ignored.</li></ul><p>Known unsupported features:</p><ul><li>Transformer Equivalent</li></ul></td></tr><tr><td><strong>Series Reactor (<code>ElmSind</code>)</strong></td><td><ul><li>3-Phase, Positive Sequence Model</li></ul></td><td><p>Known unsupported features:</p><ul><li>Saturation of the reactance</li></ul></td></tr><tr><td><strong>Series Capacitor (<code>ElmScap</code>)</strong></td><td><ul><li>3-Phase, Balanced, Positive Sequence Model</li></ul></td><td><p>Known unsupported features:</p><ul><li>Losses (i.e., conductance in parallel)</li><li>Metal Oxide Varistor model</li><li>Spark Gap model</li><li>Variable capacitance and conductance via input signals</li></ul></td></tr><tr><td><strong>Series RLC-Filter (<code>ElmSfilt</code>)</strong></td><td><ul><li>3-Phase, Balanced</li></ul></td><td></td></tr></tbody></table>

## Transformers <a href="#transformers" id="transformers"></a>

<table><thead><tr><th width="180.25">PowerFactory Component</th><th>Supported Features</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><strong>3-Phase 2W-Transformer (<code>ElmTr2</code>)</strong></td><td><ul><li><p>Positive Sequence Model</p><ul><li>With or without magnetizing branch (i.e., No Load Current = 0% and No Load Losses = 0 kW).</li><li>Distribution of leakage reactances and resistances</li></ul></li><li>Zero Sequence Model</li><li><p>Ratio Tap Changer Model on either HV or LV side</p><ul><li>Data from Element Type (TypTr2)</li><li>Data from Measurement Report</li></ul></li><li>Y, YN or D-connected windings</li><li><p>Vector Groups</p><ul><li>Y*Y*0</li><li>DD0, DD2</li><li>Y*D1, Y*D11, Y*D5, Y*D7</li><li>DY*1, DY*11, DY*5, DY*7</li></ul></li></ul></td><td><ul><li>Transformers with Y*D5, Y*D7, DY*5 or DY*7 only support positive sequence data.</li><li>Only one tap changer at the time on either HV or LV side.</li><li>Tap changer data is not available in HYPERSIM transformers. Tap changer data is only used to find the tap ratio that is to be applied to the nominal winding voltage in HYPERSIM.</li></ul><p>Known unsupported features:</p><ul><li>Parallel Transformers</li><li>Z or ZN-connected windings</li><li>Phase shifting tap changers</li><li>Tap dependent impedance</li><li>Saturation characteristic</li><li>Hysteresis modelling</li><li>Residual flux</li><li>Stray capacitances</li><li>Auto Transformer</li></ul></td></tr><tr><td><strong>3-Phase 3W-Transformer (<code>ElmTr3</code>)</strong></td><td><ul><li><p>Positive Sequence Model</p><ul><li>With or without magnetizing branch (i.e., No Load Current = 0% and No Load Losses = 0 kW).</li></ul></li><li><p>Tap Changer Model on HV, MV and/or LV sides</p><ul><li>Data from Element Type (TypTr3)</li><li>Tap Modelled at Terminals or at Start Point</li></ul></li><li><p>Vector Groups such that windings are connected in one of the following ways:</p><ul><li>Y, YN</li><li>Delta lagging (D1)</li><li>Delta leading (D11)</li></ul></li></ul></td><td><ul><li>Tap changer data is not available in HYPERSIM transformers. Tap changer data is only used to find the winding tap ratio that is to be applied to the nominal winding voltage in HYPERSIM.</li></ul><p>Known unsupported features:</p><ul><li>Zero Sequence Model</li><li>Z or ZN-connected windings</li><li>Tap Changer data from Measurement Report</li><li>Neutral Conductor / Internal Grounding Impedance (HV, MV and/or LV-sides)</li><li>Phase shifting tap changers</li><li>Tap dependent impedance</li><li>Saturation characteristic</li><li>Hysteresis modelling</li><li>Residual flux</li><li>Stray capacitances</li><li>Auto Transformer</li></ul></td></tr></tbody></table>

### Generators, loads and shunts <a href="#generators-loads-and-shunts" id="generators-loads-and-shunts"></a>

## Sources and generators <a href="#sources-and-generators" id="sources-and-generators"></a>

<table><thead><tr><th width="180.25">PowerFactory Component</th><th>Supported Features</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><p><strong>AC Voltage Source (<code>ElmVac</code>)</strong></p><p>(one terminal)</p></td><td><ul><li><strong>Voltage Source</strong> type</li><li>Positive sequence model</li><li><p>Load flow setpoints given by either:</p><ul><li>Explicit voltage magnitude and phase angle values</li><li>External controllers (i.e., Voltage Control and/or Angle Control)</li></ul></li><li><strong>Extended Ward Equivalent</strong> type</li></ul></td><td><ul><li>The terminal where the source is connected is always assumed to be the controlled node.</li><li><p>Currently supported external controllers:</p><ul><li><strong>Load Flow Controller</strong></li></ul></li><li>Load-flow calculation used by Extended Ward Equivalent source cannot be replicated in HYPERSIM because UCMs do not support dynamic load flow. Load flow results are imported from PowerFactory (i.e., active and reactive power).</li></ul></td></tr><tr><td><strong>Synchronous Machine (<code>ElmSym</code>)</strong></td><td><ul><li><p>3-Phase Model</p><ul><li>Classical Model (i.e. GENCLS)</li><li>Standard Model (i.e. GENSAL, GENSAE, GENROU, GENROE).</li></ul></li><li>D, Y or YN connections</li><li>Parallel machines</li><li><p>Flux Saturation models</p><ul><li><p>Quadratic, Exponential or Tabular input</p><ul><li>d- and q- axis (flux magnitude)</li><li>d-axis (flux magnitude)</li><li>d- and q-axis (flux components)</li><li>d-axis (flux component, d-axis)</li></ul></li></ul></li></ul></td><td><p>Known unsupported features:</p><ul><li>Neutral Conductor / Internal Grounding Impedance</li><li>Coupling reactances (between field and damper winding and between q-axis damper windings)</li><li>Damping Torque (i.e., damping torque coefficients dkd and dke are ignored).</li><li>Model 3.3 (Detailed model)</li><li>Permanent Magnet model</li><li>Asynchronous Starting model</li></ul></td></tr><tr><td><strong>Static Generator (<code>ElmGenstat</code>)</strong></td><td><ul><li>3PH Technology</li><li><p>Constant power model</p><ul><li>Active and Reactive Power setpoints</li></ul></li><li>Internal impedance (Simulation EMT)</li><li>Parallel Units</li></ul></td><td><ul><li>“Local controller” has to be set to “Const. Q“.</li></ul></td></tr></tbody></table>

## Loads and shunts <a href="#loads-and-shunts" id="loads-and-shunts"></a>

<table><thead><tr><th width="180.25">PowerFactory Component</th><th>Supported Features</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><strong>Shunt/Filter RL, RLC, C (<code>ElmShnt</code>)</strong></td><td><ul><li>AC C, R-L and R-L-C types</li><li>3PH-'D', 3PH-'Y' and 3PH-'YN' technologies</li><li>Positive sequence model</li></ul></td><td><ul><li>Parallel conductance in shunt capacitors always assumed to be zero.</li></ul><p>Known unsupported features:</p><ul><li>Tap Changer / Shunt Controller</li><li>Neutral Conductor / Internal Grounding Impedance</li><li>Saturation of the reactance</li><li>Zero sequence model</li></ul></td></tr><tr><td><strong>General Load (<code>ElmLod</code>)</strong></td><td><ul><li>Balanced loads</li><li><p><strong>General Load</strong> Type</p><ul><li>AC, 3PH</li><li>100% Static loads</li></ul></li><li><p><strong>Complex Load</strong> Type</p><ul><li>100% Static loads</li></ul></li></ul></td><td><ul><li>Since to date only <em>static loads</em> are supported, these behave as <em>constant impedance loads</em> after load flow.</li></ul><p>Known unsupported features:</p><ul><li>Load / feeder scaling factors</li><li>Load transformer option (load transformer with zero sequence impedance).</li><li>Load events (<strong>Load Event</strong>)</li></ul></td></tr></tbody></table>

## Standard dynamic models (PSS/E compatible) <a href="#standard-dynamic-models-pss-e-compatible" id="standard-dynamic-models-pss-e-compatible"></a>

{% hint style="info" %}
There are small differences in the implementation of the model in HYPERSIM, with respect to those in PowerFactory. See **Comments / Limitations** column.
{% endhint %}

### Excitation systems <a href="#excitation-systems" id="excitation-systems"></a>

<table><thead><tr><th width="180.25">Model Name</th><th>Supported Versions</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><strong>AC7B</strong></td><td><ul><li><code>avr_AC7B</code> / Version 2022 (Aug2022)</li><li><code>exc_PSSE_AC7B</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.9.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 3%*</li></ul></td></tr><tr><td><strong>AC8B</strong></td><td><ul><li><code>avr_AC8B</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_AC8B</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.11.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>DC3A</strong></td><td><ul><li><code>avr_DC3A</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_DC3A</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.21.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 3%*</li></ul></td></tr><tr><td><strong>ESAC1A</strong></td><td><ul><li><code>avr_ESAC1A</code> / Version 2019 (Oct2019)</li><li><code>exc_PSSE_ESAC1A</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.25.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 2%*</li></ul></td></tr><tr><td><strong>ESAC2A</strong></td><td><ul><li><code>avr_ESAC2A</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_ESAC2A</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.26.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 2%*</li></ul></td></tr><tr><td><strong>ESAC3A</strong></td><td><ul><li><code>avr_ESAC3A</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_ESAC3A</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.27.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>ESDC2A</strong></td><td><ul><li><code>avr_ESDC2A</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_ESDC2A</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.33.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 2%*</li></ul></td></tr><tr><td><strong>ESST1A</strong></td><td><ul><li><code>avr_ESST1A</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_ESST1A</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.34.</p></td><td><ul><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>ESST2A</strong></td><td><ul><li><code>avr_ESST2A</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_ESST2A</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.35.</p></td><td><ul><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>EXAC1</strong></td><td><ul><li><code>avr_EXAC1</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_EXAC1</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.40.</p></td><td><ul><li>Estimated error for excitation voltage signal &#x3C; 2%*</li></ul></td></tr><tr><td><strong>EXAC2</strong></td><td><ul><li><code>avr_EXAC2</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_EXAC2</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.42.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 7%*</li></ul></td></tr><tr><td><strong>EXAC3</strong></td><td><ul><li><code>avr_EXAC3</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_EXAC3</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.43.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>EXDC2</strong></td><td><ul><li><code>avr_EXDC2</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_EXDC2</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.46.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>EXPIC1</strong></td><td><ul><li><code>avr_EXPIC1</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_EXPIC1</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.50.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 3%*</li></ul></td></tr><tr><td><strong>EXST1</strong></td><td><ul><li><code>avr_EXST1</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_EXST1</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.51.</p></td><td><ul><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>EXST3</strong></td><td><ul><li><code>avr_EXST3</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_EXST3</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.54.</p></td><td><ul><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>IEEET1</strong></td><td><ul><li><code>avr_IEEET1</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_IEEET1</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.55.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>IEEET2</strong></td><td><ul><li><code>avr_IEEET2</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_IEEET2</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.56.</p></td><td><ul><li>Saturation function is implemented differently</li><li>Estimated error for excitation voltage signal &#x3C; 3%*</li></ul></td></tr><tr><td><strong>IEEET3</strong></td><td><ul><li><code>avr_IEEET3</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_IEEET3</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.57.</p></td><td><ul><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr><tr><td><strong>SCRX</strong></td><td><ul><li><code>avr_SCRX</code> / Version 2019 (Oct2019)</li><li><code>exc_PSSE_SCRX</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.73.</p></td><td><ul><li>Estimated error for excitation voltage signal &#x3C; 2%*</li></ul></td></tr><tr><td><strong>SEXS</strong></td><td><ul><li><code>avr_SEXS</code> / Version 2019 (Jan2020)</li><li><code>exc_PSSE_SEXS</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 6.74.</p></td><td><ul><li>Estimated error for excitation voltage signal &#x3C; 1%*</li></ul></td></tr></tbody></table>

\* Errors have been computed by signal comparison function (SIGCMP) from **ScopeView.** Simulations have been performed on unit test models where the event was either a setpoint or a load change.

* `res = sigcmp(HYPERSIM Signal, PowerFactory Signal, Tol)`
* The error is the tolerance value that allows to obtain a result of zero along the simulation interval.

### Turbine-governors <a href="#turbine-governors" id="turbine-governors"></a>

<table><thead><tr><th width="180.25">Model Name</th><th>Supported Versions</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><strong>DEGOV1</strong></td><td><ul><li><code>gov_DEGOV1</code> / Version 2019 (Jan2020)</li><li><code>gov_PSSE_DEGOV1</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 7.4.</p></td><td><ul><li>Estimated error for mechanical power/torque signal &#x3C; 1%</li></ul></td></tr><tr><td><strong>HYGOV</strong></td><td><ul><li><code>gov_HYGOV</code> / Version 2019 (Jan2020)</li><li><code>gov_PSSE_HYGOV</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 7.15.</p></td><td><ul><li>Estimated error for mechanical power/torque signal &#x3C; 1%</li></ul></td></tr><tr><td><strong>TGOV1</strong></td><td><ul><li><code>gov_TGOV1</code> / Version 2019 (Jan2020)</li><li><code>gov_PSSE_TGOV1</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 7.40.</p></td><td><ul><li>Controller droop block and initialization of governor setpoints are implemented differently</li><li>The output in HYPERSIM is <code>Tm</code> (mechanical torque) instead of <code>Pm</code> (mechanical power) as in PowerFactory.</li><li>Estimated error for mechanical power/torque signal &#x3C; 1%</li></ul></td></tr><tr><td><strong>TGOV2</strong></td><td><ul><li><code>gov_TGOV2</code> / Version 2019 (Jan2020)</li><li><code>gov_PSSE_TGOV2</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 7.42.</p></td><td><ul><li>Controller droop block and initialization of governor setpoints are implemented differently</li><li>The output in HYPERSIM is <code>Tm</code> (mechanical torque) instead of <code>Pm</code> (mechanical power) as in PowerFactory.</li><li>Estimated error for mechanical power/torque signal &#x3C; 1%</li></ul></td></tr><tr><td><strong>WEHGOV</strong></td><td><ul><li><code>gov_WEHGOV</code> / Version 2019 (Jan2020)</li><li><code>gov_PSSE_WEHGOV</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 7.52.</p></td><td><ul><li>PowerFactory output is equal to HYPERSIM output multiply by the Rated Power Factor of the machine</li><li>Estimated error for mechanical power &#x3C; 3% with <code>gov_PSSE_WEHGOV</code></li><li><code>gov_PSSE_WEHGOV</code> valve dynamics will be estimated to be linear, and with need to me manually modified otherwise</li></ul></td></tr><tr><td><strong>GAST</strong></td><td><ul><li><code>gov_GAST</code> / Version2019 (Jan2020)</li><li><code>gov_PSSE_GAST</code> / Version 2023 (Nov2022)</li></ul><p>V2023 / Reference: PSS-E 35.2.0 Model Library, sec 7.6</p></td><td><ul><li>Estimated error for mechanical power/torque signal &#x3C; 1%</li></ul></td></tr></tbody></table>

## Simulation events <a href="#simulation-events" id="simulation-events"></a>

<table><thead><tr><th width="180.25">Event</th><th>Supported Features</th><th>Comments / Limitations</th></tr></thead><tbody><tr><td><strong>Short-Circuit Event (EvtShc)</strong></td><td><ul><li>Three-phase, two-phase or single-phase.</li><li>Fault clearing event to specify “duration” of the fault.</li></ul><p>** Please refer to Terminal (<code>ElmTerm</code>) for more information.</p></td><td><ul><li>Only <em>Short-Circuit Events</em> on terminals (i.e., <code>ElmTerm</code> objects) are currently supported.</li><li>Short-circuit events with fault reactance are not supported.</li><li>Short-circuit events with zero-crossing clearing type are currently not leading to the same simulation results in HYPERSIM.</li></ul></td></tr><tr><td><strong>Switch Event (EvtSwitch)</strong></td><td><ul><li>Action, execution time and affected phases</li></ul><p>** Please refer to Switch (<code>StaSwitch</code>) for more information.</p></td><td><ul><li>Only <em>Switch Events</em> associated to <code>StaSwitch</code> objects are currently supported.</li></ul></td></tr></tbody></table>

## Power flow computation limitations <a href="#power-flow-computation-limitations" id="power-flow-computation-limitations"></a>

UCMs in HYPERSIM lack support for dynamic load-flow. This has an impact on the import of PowerFactory network models containing loads with the `Complex Load Type` or `Extended Ward Equivalent` voltage sources.

An alternative method for such advanced load flow calculations is suggested. This method involves the following steps:

{% stepper %}
{% step %}

## Fill load flow setpoint data fields

Fill the load flow setpoint data fields in the **Load Flow** tab of the UCM block's mask.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c2f79deff4cf99745620c4811fb6c982390914a7%2Fpowerfactory-load-flow-ucm.png?alt=media" alt=""><figcaption></figcaption></figure>

The field values will very likely include expressions that refer to other component variables. For instance, in the example above the expressions for P and Q are the following:

`P=-50e6*(0.5*(bus3.LF_Voltage/132)^0.9+0.4*(bus3.LF_Voltage/132)^1.7+0.1*(bus3.LF_Voltage/132)^2.1)`

`Q=-20e6*(0.45*(bus3.LF_Voltage/132)^1.0+0.35*(bus3.LF_Voltage/132)^2.5+0.2*(bus3.LF_Voltage/132)^0.5)`
{% endstep %}

{% step %}

## **Execute the load flow until convergence**

Open the **Parameter Form** of the bus to which the component is connected. Go to the **Load Flow Results** tab. Execute the load flow several times until the **Voltage** field value converges.

**Iteration 0:**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-62287f3147f7ad3fc438e4f60c40b04f2eab2b74%2Fpowerfactory-loadflow-iteration-0.png?alt=media" alt=""><figcaption></figcaption></figure>

**Iteration 1:**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5bab9f31ad85015a5532e598cbd44aafc95919d1%2Fpowerfactory-loadflow-iteration-1.png?alt=media" alt=""><figcaption></figcaption></figure>

**Iteration 2:**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c995897398671a2a32f78f62ad3de59014f38ff7%2Fpowerfactory-loadflow-iteration-2.png?alt=media" alt=""><figcaption></figcaption></figure>

**Iteration 3:**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a05180fe0a0736ac24f5799e35be820e3ae350e0%2Fpowerfactory-loadflow-iteration-3.png?alt=media" alt=""><figcaption></figcaption></figure>

**Iteration 4:**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e7ee5ac0e06cbf584503a4d2460f651e45811810%2Fpowerfactory-loadflow-iteration-4.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Synchronous machine control differences <a href="#differences-in-the-implementation-of-synchronous-machine-control-system-models" id="differences-in-the-implementation-of-synchronous-machine-control-system-models"></a>

Components of the **Control Exciters**, **Control Governors** and **Control Stabilizers** libraries in HYPERSIM are based on their respective implementation from a given version of PSS/E. The behavior of these components has been validated against simulation results in that specific version of PSS/E. Where applicable, HYPERSIM components have also referenced IEEE standards such as the “*IEEE Recommended Practice for Excitation System Models for Power System Stability Studies*“ (IEEE Std 421.5-2005).

However, the implementation of a same control component may vary from one version to another of PSS/E, as illustrated with the example below:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-fb977f946679d6355dde5438c8c7d071d9bf5686%2Fpowerfactory-synchronous-machine-differences-.png?alt=media" alt=""><figcaption></figcaption></figure>

It can be noted that the output of the voltage regulator of the model shown in the figure above is limited in the range \[ `F * VRmin` , `F * VRmax`]. It turns out, that the function **F** has different definitions among different PSS/E versions:

* PSS/E 33.4: `F = [1.0 + F1IMF * (ET - 1.0)] * (KE + KD + SE)`
* PSS/E 34.2: `F = [1.0 + F1IMF * (ET - 1.0)]`
* PSS/E 35.1.0: `F = [1.0 + F1IMF * (ET - 1.0)] * (KE + KD + SE)`

PowerFactory, on the other side, also provides **dynamic model** blocks that are compliant with PSS/E. It is not entirely clear, to which version of PSS/E the components from its *v2022 Standard Dynamic Models* library are referring to. But, all the components from its *v2023 Standard Dynamic Models* library are referring to the *PSS/E 35.2.0 Model Library*. Most of HYPERSIM’s dynamic model blocks are referring to *PSS/E 34.2 Model Library*.

Some other typical causes of mismatches in the response of dynamic models are the following:

* Different model initialization.
* Additional calculated inputs which result in offsets at summation point outputs.
* Different implementation of basic blocks such as proportional-integral-derivative (PID) and the exciter saturation characteristic. An example of this last item is shown in the table below, where two mathematical definitions of the saturation characteristic are provided.

| Exponential Function                                                                                                           | Quadratic Function                                                                                                                                                                                                     |
| ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| $$y\_o = y\_i \cdot A \cdot e^{-B,y\_i}$$                                                                                      | $$y\_o = B\sqrt{y\_i - A}$$                                                                                                                                                                                            |
| $$\begin{aligned} A &= SE\_1 \cdot e^{-B,E\_1} \ B &= \frac{\ln!\left(\frac{SE\_2}{SE\_1}\right)}{E\_2 - E\_1} \end{aligned}$$ | <p><span class="math">\begin{aligned} sq &= \sqrt{\frac{E\_1}{E\_2} \cdot \frac{SE\_1}{SE\_2}} \ A &= \frac{E\_1 - E\_2 \cdot sq}{1 - sq} \ B &= \frac{E\_2 \cdot SE\_2}{\sqrt{E\_2 - A}} \end{aligned}</span><br></p> |

## Import of subsystems <a href="#import-of-subsystems" id="import-of-subsystems"></a>

Components will be grouped inside subsystems if the model contain either:

* more than 1 Grid (`ElmNet`)
* any Site (`ElmSite`) or Substation (`ElmSubstat`)

### Example with the PowerFactory 400kV transmission system <a href="#example-with-the-powerfactory-400kv-transmission-system" id="example-with-the-powerfactory-400kv-transmission-system"></a>

## Top level representation <a href="#top-level-representation" id="top-level-representation"></a>

The 4 Grids are imported as subsystems, with the interconnection lines in-between.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8d6c1af7537df5c3564657238af48b943cbaa0b4%2Fpowerfactory-400kv-transmission-system.png?alt=media" alt=""><figcaption></figcaption></figure>

## Representation of the South-East grid <a href="#representation-of-the-south-east-grid" id="representation-of-the-south-east-grid"></a>

The Grid contains 3 Sites, each of them being imported as subsystem.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d951ae946603cbecaea927b23d114c1468127175%2Fpowerfactory-south-east-grid.png?alt=media" alt=""><figcaption></figcaption></figure>

## Representation of the South-East site “SE\_03\_Site” <a href="#representation-of-the-south-east-site-se_03_site" id="representation-of-the-south-east-site-se_03_site"></a>

The Site contains only 1 substation, imported as a subsystem.

The diagram in PowerFactory shows the bus and breakers, but we cannot do that in Hypersim (that doesn’t have the diagram concept PowerFactory has).

In Hypersim, these components will only be visible on the substation level (see next point).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8d4ec667e6ca6918b792953b83563739c970bd44%2Fpowerfactory-south-east-site.png?alt=media" alt=""><figcaption></figcaption></figure>

## Representation of the South-East substation “SE\_03” <a href="#representation-of-the-south-east-substation-se_03" id="representation-of-the-south-east-substation-se_03"></a>

The Substation will display the breakers.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-764055fa033a5c29e3166ffb53d00a9fc78be2ae%2Fpowerfactory-south-east-substation.png?alt=media" alt=""><figcaption></figcaption></figure>

## Limitations <a href="#limitations" id="limitations"></a>

Depending on the available diagrams in the exported XML model, some components may not be correctly located on the schema.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/hypersim/model-and-simulation/import-models-from-external-software-or-code/import-from-powerfactory/compatibility-and-limitations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
