The latest primary version of PSS®E (Power System Simulator for Engineering) Version 36 , released by Siemens PTI
as a major advancement in transmission planning and analysis. This version marks a significant shift in the software's architecture, specifically designed to address modern grid challenges like renewable integration and cybersecurity. Key Features of PSS®E 36
The transition to Version 36 introduces several critical improvements over previous versions like V34 and V35: Version-Independent Dynamic Models
: V36 utilizes model source code and DLLs that are version-independent. This means engineers no longer need to recompile models every time the software is updated, significantly streamlining long-term maintenance. Built-in Model Converter
: To ease the transition, V36 includes an automated converter program that updates existing dynamic models from older formats to the new V36-compatible architecture. Modernized Automation
: Unlike V34, which relied on the deprecated Python 2.7, V36 is built for modern Python™ environments
, offering over 2,000 open APIs for intelligent automation of complex grid studies. Enhanced Renewable Support
: The software is specifically optimized for modeling advanced technologies, time-series data, and harmonic behavior to support the rapid increase in renewable energy scenarios. The Industry Transition (AEMO Case Study) Large-scale operators, such as the Australian Energy Market Operator (AEMO) , have initiated mandatory transitions to PSS®E 36.
: AEMO's transition period began in August 2025, with full industry-wide adoption expected by Drivers for Change
: The primary drivers include the end of support for V34 (October 2024) and the security risks associated with older Python versions used in previous releases. Core Capabilities & File Formats
PSS®E continues to be the "industry standard" for a wide range of analytical functions: PSS®E Version 36 - Siemens
As of my latest knowledge (early 2026), the newest version of PSS/E (Power System Simulator for Engineering) is version 35. It is developed and maintained by Siemens PTI (now part of Siemens Digital Industries Software).
Here is a concise review of PSS/E version 35, focusing on what’s new, what works well, and what doesn’t. psse latest version
Migrating your existing models to the PSSE latest version requires careful planning. Here is a recommended workflow:
.sav, .dyr, and .con files..sav35) not readable by older versions. Always export a RAW file (.raw) as an interchange format.p_volt and q_volt tolerances.I know what you’re thinking: "Upgrading our corporate simulation environment is a nightmare. Model conversion takes weeks."
Here is the reality check. If you are still on Version 34 or earlier, you are actively introducing risk into your planning.
1. FERC Order 2222 Compliance The latest version includes native "aggregate DER" models. As distributed energy resources (rooftop solar, batteries, EVs) bid into wholesale markets, you need to model their aggregate impact on transmission. Old versions can't handle the node count.
2. The "Weak Grid" Study In the last version, if you ran a short circuit at a bus with 90% IBR penetration, the voltage recovery profile was wildly optimistic. Version 35’s new solver correctly models the "transient over-voltage" and "sub-synchronous control interactions" (SSCI) that have caused real-world inverter trips in Texas and the UK.
3. Open Source Interoperability The latest version exports to Matpower 7.0 and IEEE Common Data Format (CDF) without data loss. If you are using GridLAB-D or OpenDSS for distribution, the co-simulation interface is finally plug-and-play.
While the PSSE latest version is powerful, the user community has noted several gaps:
The hardware requirements have increased slightly due to the expanded Python integration and graphical enhancements.
New users can download a 30-day trial (cases up to 500 buses) from the Siemens Digital Industries Software website. Full training courses (self-paced e-learning and instructor-led) are available through Siemens PTI University.
Information based on PSS/E v35.0 release notes and Siemens product documentation as of April 2026. Always refer to official Siemens documentation for the most current features and system requirements.
To "prepare proper paper" (typically referring to the technical documentation or installation materials) for the latest version of PSS®E (Version 36), you must focus on its new architecture, which emphasizes cross-version compatibility and modernized automation [16, 11]. Key Technical Specifications for PSS®E v36
When preparing documentation or system setups, prioritize these specific features of the latest version: The latest primary version of PSS®E (Power System
Version Independent (VINDP) DLLs: The primary breakthrough in Version 36 is the ability to create dynamic link libraries (dll) that are future-proof. Unlike previous versions, a user-defined model (UDM) created in v36 will be compatible with all future PSS®E releases without needing re-compilation [16].
Built-in Model Conversion: For existing projects, v36 includes an automated tool to upgrade older dynamic model source code into the new, standardized format [16].
Python Integration: While older versions relied heavily on specific Python distributions (like 2.7 or 3.4), newer versions require maintaining compatibility with contemporary Python environments for automation scripts and data retrieval [1, 23]. System & Hardware Requirements
To ensure the "paper" (technical setup) is correct, the hardware must support the increased bus dimension capabilities of modern simulations:
Operating System: Current versions are optimized for Windows 10/11 environments [1, 37].
Initialization: After installation, it is standard practice to set the Startup bus dimension (e.g., to 150,000) in the "Change program settings" menu to handle large-scale system cases [9].
Path Length Limits: During the Python component installation, you must disable the path length limit in Windows to prevent errors with long file paths common in simulation projects [1]. Essential Documentation to Include
If you are preparing a project report or technical manual, ensure the following sections are addressed based on Siemens' current guidelines:
Network Data Representation: Use the .raw format for steady-state power flow data as it remains the industry standard for plain-text data management [25, 35].
Grid Compliance: Note that for projects in certain regions (like Fingrid), v36 models are becoming a strict requirement for grid compliance tests starting in 2025/2026 [11].
Model Descriptions: Clearly distinguish between Positive Sequence simulations (the focus of PSS®E) and EMT-level simulations used in software like PSCAD [34]. Helpful Resources for Practitioners
Tutorials & Guides: Highly recommended starting points include the PSSE Introduction to Dynamic Simulation for scripting and the Siemens PSSE Explore trial for students working on networks up to 50 buses [20, 23]. Migration Guide: Upgrading from PSSE 33 or 34
Training: For a "paper" focusing on skill development, resources from Power Projects India provide 100% practical simulation training [21].
As of April 2026, the latest major release of Siemens PSS/E (Power System Simulator for Engineering) is Version 36, with Version 37 planned for release later this year. Major industry entities like AEMO and Hydro-Québec are currently transitioning to Version 36 to address the security risks and performance limitations of older versions. Key Improvements in Version 36
The current version focuses heavily on long-term compatibility and modernizing automation workflows:
Version Independent (VINDP) Dynamic Models: A standout feature allowing users to create dynamic Linked Library (.dll) files that will be compatible with all future PSS/E versions. This removes the historical "pain point" of having to recompile custom models for every new software release.
Built-in Model Conversion: An automated tool that upgrades existing dynamic model source code into the new version-independent format.
Python 3 Integration: Unlike Version 34, which relied on the deprecated Python 2.7, Version 36 uses current Python 3.x standards for its 2,000+ open APIs, improving both security and productivity.
Hybrid Cloud Module: Introduced in version 36.2.0, this allows for scalable on-demand computation and secure remote collaboration.
Enhanced Performance: Supports network models up to 200,000 buses with "lightning-fast" steady-state contingency analysis. Version Lifecycle Status (2026)
Siemens has established a clear support roadmap for the year: PSS®E Version 36 - Siemens
Yes, if:
No, if: