PSS/E is used for transmission planning, interconnection studies, power flow, dynamics, fault and contingency analysis. A project-side model does not need to reproduce an entire utility planning database, but it must represent the proposed facility accurately enough to connect to the utility case without changing the architecture.
1. Start with the receiving utility's requirements
Before assigning bus numbers, confirm the target PSS/E revision, system base, required study scenarios, naming rules, point of interconnection, model boundary and required file set. Ask whether the utility expects a reduced project model, a modified utility case, a sequence-data file, dynamic records, user-written models or a separate single-line.
This decision controls the data model. A technically correct PSS/E 35 record may still fail a PSS/E 34 import, and a valid dynamic record will not attach if its bus number or machine ID differs from the steady-state case.
Record the target revision, base MVA, nominal frequency, bus-number range, POI assumptions, study dispatch and file naming convention in a case manifest.
2. Build the physical topology from the POI inward
Start at the utility point of interconnection and follow each electrically distinct node into the facility. Every voltage level, transformer winding connection, normally open path and parallel circuit should have an explicit representation. Keep the one-line readable, but do not collapse equipment that affects impedance, voltage control, fault current or switching studies.
Give every record a stable identity
Bus numbers are the primary anchors. Branch circuit IDs, transformer IDs, load IDs and machine IDs distinguish parallel devices attached to the same buses. Establish these identifiers once and keep them stable across the RAW, DYR, sequence-data companion, study event definitions and drawings.
- Use one bus for each electrically common node at one nominal voltage.
- Represent parallel transformers and lines as separate records with distinct circuit IDs.
- Include tertiary buses where a three-winding transformer has a physical or modelled tertiary.
- Use in-service status to represent the study state instead of deleting standby equipment.
- Preserve a clear mapping between equipment tags on the single-line and case IDs.
3. Enter study-ready steady-state data
The RAW case is the network foundation. Use utility and manufacturer data wherever it is available; label preliminary values and replace them before submission. Convert impedances to the correct base rather than copying a percent value without its MVA basis.
| Model area | Minimum useful data | Common failure |
|---|---|---|
| Utility source | Nominal kV, voltage setpoint, short-circuit strength or equivalent impedance, X/R and study dispatch | A type-3 swing bus with no machine record |
| Transformers | Winding kV, MVA ratings, pairwise impedance, vector group, taps, control mode and limits | Impedance on the wrong base or an artificial loaded tertiary |
| Lines and cables | Positive-sequence R, X, charging B, length, ratings and status | Mixing ohms, per-unit and distance units |
| Loads | MW, MVAr, status, composition and expected operating cases | Using only MW while reactive demand is hidden |
| Generation and BESS | P/Q dispatch, limits, MVA base, voltage schedule, regulated bus and operating mode | Using capability limits as the actual dispatch |
| Shunts | Installed MVAr, step size, number of steps, limits and controlled bus | Exporting a controlled value outside installed capability |
Choose bus and machine control roles deliberately
A swing bus balances real and reactive mismatch for the solved island and therefore needs a machine or equivalent source record. PV machines hold active power and a voltage schedule within reactive limits. PQ devices hold specified real and reactive injection. Capacitor banks, inverter controls and transformer taps should carry the corresponding voltage or reactive-control behavior rather than giving an ordinary load bus an unexplained source of Q.
4. Solve the intended operating cases and reconcile the balances
Begin with the normal topology and expected maximum load or generation dispatch. Solve the AC power flow, then inspect more than the convergence flag. Check bus voltages, swing-bus MW and MVAr, transformer and branch loading, active and reactive losses, tap positions, reactive limits and the direction of flow at both ends of every path.
A reported mismatch at a non-swing bus is the equation with the largest remaining residual, not necessarily the location of the missing generation. If the solver has genuinely converged, that residual should be below the selected tolerance. If it has not, inspect islanding, invalid impedances, control conflicts and reactive limits before increasing iteration count.
Run architecture-changing contingencies early
Test loss of each critical line, transformer, source, generator, BESS and major shunt. The purpose is not simply to produce an N-1 table. It is to identify whether the proposed redundancy, ratings and voltage support remain workable before the layout and procurement basis are fixed.
5. Add sequence and dynamic data to the same equipment identities
Short-circuit and dynamic models are not separate versions of the project. They extend the solved network. Sequence impedances, grounding connections and neutral impedances must correspond to the same lines, transformers, machines and buses in the steady-state case.
Dynamic records attach to an existing load, machine, plant controller or other device using the bus number and ID expected by the model. Populate model parameters from the relevant manufacturer or validated generic-model documentation. For converter-based resources and large electronic loads, capture control mode, ride-through response, current limits, recovery behavior and protection assumptions rather than relying on a single step response.
Siemens describes PSS/E as supporting extensive standard, vendor-specific and customizable models for power flow, dynamics and renewable technologies. That library is one reason final validation in the target PSS/E environment is important. See the official Siemens PSS/E capability overview.
6. Export, read back and compare before handoff
A text file that looks plausible is not yet a submission package. Export the selected PSS/E revision, open or read it in that same PSS/E version, solve it again and compare the imported case to the source model. Record warnings instead of dismissing them.
- Confirm every section and record is accepted without ignored fields.
- Confirm the swing bus has a corresponding source or machine record.
- Compare bus voltages and angles, swing output, branch flows and transformer taps.
- Load the dynamic records and resolve every undefined model or unmatched device.
- Load the sequence data and run representative balanced and unbalanced faults.
- Package assumptions, source documents, unresolved warnings and the intended study scenario with the files.
The utility reviewer should be able to identify the equipment, import the files, reproduce the intended solved state and understand which values are final, preliminary or controlled.
Where HV Power Flow fits
HV Power Flow brings the one-line, equipment inputs, AC solution, study checks and PSS/E-compatible exchange files into one browser workspace. It is intended to help project teams develop and challenge the architecture before licensed utility validation. It does not replace manufacturer data, the utility's official network case or the professional responsibility for the submission.