Professional Documents
Culture Documents
PSS®E high-performance transmission planning software has supported the power community with
meticulous and comprehensive modeling capabilities since its introduction in 1976. PSS®E-33
introduces several new forms of analysis, Preventative Security Constrained OPF and N-1-1, a
number of new analytical models, the standardization of the Dynamic CONEC and CONET type
models, improvements to data entry and connection codes in Short Circuit, an updated fully
integrated Scenario Manager as well as improvements to basic power flow and dynamic simulation
activities.
PSS®E-33 is built with the Intel Visual FORTRAN (IVF) 12.0 compiler and requires the same for
compiling user-written models. Our original investigations and discussions with Intel led us to
believe that models compiled with IVF 9.1 or 10.1 could be linked against the IVF 12 compiled
PSS®E engine and module files and so we communicated this information to you. Unfortunately,
during our extensive release testing we discovered that this was no longer possible and that
PSS®E-33 requires the use of the IVF 12.0 compiler for user-written models.
In addition, during our testing with various user written models, we discovered that the IVF 12.0
compiler is less forgiving with un-initialized variables than IVF 9.1 or 10.1. User models that are to
be compiled with IVF 12.0 for use with PSS®E-33 should be closely examined for un-initialized
variables, either by eye or with a code inspection/verification tool.
Please note, Distribution Factor Data (DFAX) files constructed by earlier versions of PSS®E cannot
be read by PSS®E-33. They must be rebuilt by activity DFAX in PSS®E-33. Using earlier versions
of DFAX files in PSS®E-33 will result in a program crash.
5/18/2011 1
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
2 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
User-written CONEC and/or CONET type models (i.e., those that generate model calls in CONEC
and CONET subroutines) can be redesigned to the new CCT type model format. One of the key
advantages of converting to the CCT type would be that the CONEC and CONET files would not be
needed, and more importantly, the model themselves need to be compiled only once for a given
release of PSS®E.
The use of CONEC and CONET files is still supported if you choose to run that way.
contingencies. The preventive method enables the system to be prepared for certain contingencies
beforehand, and it does not take into account the system’s post-contingency control capabilities.
Sensitivity Analysis
Sensitivity analysis is a method to systematically study the impacts of changes in system operation
conditions such as MW and MVar power injections on changes in branch flows and bus voltages.
The function can calculate sensitivity factors with either a DC linear network or full AC network and
can be used in the following applications:
• Mitigate System Operating Limit (SOL) violations
• Determine loading contribution
• Increase transfer capability
• Develop cost allocation
4 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
The N-1-1 contingency solution performs an AC power flow to solve the primary contingency,
applies the appropriate system adjustments in accordance with one of three adjustment modes,
and then runs another AC power flow to solve the secondary contingency. The three control modes
are: Local control mode, Corrective action mode and Preventive Security constrained optimal power
flow (PSCOPF) mode. Under each mode, several types of controls are available to adjust system to
meet the specified goals.
5/18/2011 5
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
Interruptible Loads
Each load may be characterized as either interruptible or non-interruptible. This attribute will be
utilized in a future PSS®E release.
6 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
5/18/2011 7
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
A SKIP command to exclude individual branches form the monitored element list generated
as a result of subsequent automatic specification commands.
A command to place branches that are assigned to a line owner into the monitored element
list.
In Contingency Description Data File, two commands have been added:
The ADD and REMOVE commands allow the status change of an individual induction
machine.
Branches that are assigned to a line owner can be outaged, either singly or in pairs.
The ADD and REMOVE commands allow the status change of an individual induction
machine.
The length of the labels in Subsystem Description Data File and Monitored Element Data
File has been increased from 12 to 32.
The size limit on Contingency Analysis Output Files has been removed; previously the limit
is 2GB.
The Contingency Analysis Output Files from both AC Contingency Solution and Multiple
Level Contingency Solution can be processed by Reliability Assessment function. In PSS®E
32 and early, only the output files from Multiple Level Contingency Solution can be used by
Reliability Assessment function.
5/18/2011 9
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
10 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
ABBSVC1 – ABB SVC model (attached to switched shunt device in PSS®E power flow)
WT3G2 – Generic wind turbine model representing a generator connected to the grid via a
power converter (Type – 4 wind machine)
All the models can be used in the standard state-space simulations only.
A new model type called the "induction machine model" has been added to allow dynamic models
to be created for those machines that are designated as induction machines in PSS®E power flow.
Although currently, in version 33, there are no PSS®E standard induction machine models that can
be attached to the induction machines in power flow, PSS®E users can write user-written induction
machine models that key off the induction machines in power flow.
The following models have been converted from the old CONEC-CONET form into a new table-
driven form (i.e., where the model calls are not generated in CONEC and CONET subroutines).
DCTC1 DCTC1T
LOEXR1 LOEXR1T
VTGDCA VTGDCAT
VTGTPA VTGTPAT
FRQDCA FRQDCAT
FRQTPA FRQTPAT
SWCAP SWCAPT
SAT2 SAT2T
OLTC1 OLTC1T
OLPS1 OLPS1T
OLTC3 OLTC3T
OLPS3 OLPS3T
CRANI CRANIT
RUNBK RUNBKT
CHIGAT CHIGATT
5/18/2011 11
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
CEELRI CEELRIT
CMDWAS CMDWAST
CMDWS2 CMDWS2T
CMFORD CMFORDT
The AC Contingency Single Run Report function has been expanded to report load losses due to a
contingency event or tripping action for checking Interconnection Reliability Operating Limits
(IROL).
12 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
5/18/2011 13
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
The Tree View can also be configured to operate as a Slide in/out panel, allowing quick access to
elements but then quickly clearing to present as much of your data as possible.
GUI windows are now easily configurable using location tools found in other applications.
14 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
In addition, many of the global diagram annotation settings have been removed from the Diagram
files and moved to the Application level. These annotation settings are saved in the configuration
file as well, so that different annotation settings may be used for different studies/regions.
5/18/2011 15
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
Compiling and linking user models to create User Model DLLs (.dll)
Compiling and linking user models to create User Model static libraries (.lib)
16 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
PSS®E-33 SNP files are not compatible with previous versions of PSS®E.
PSS®E-33 SLD files are not compatible with previous versions of PSS®E.
As always, most data files are forward compatible. The above items deal with issues of backwards
compatibility.
Distribution Factor Data Files constructed by earlier versions of PSS®E cannot be read by PSS®E-
33. They must be rebuilt by activity DFAX in PSS®E-33.
Historic Achievements
PTI has always recognized that there are issues involved in moving to new releases of PSS®E. To
aid in the process, PSS®E has always been able to recognize previous versions of saved case and
dynamics snapshot files and read them into the current release.
Changes in input file formats and command syntaxes have been documented in the PSS®E
Compatibility with Previous Releases Manual.
PTI has always tried to accommodate changes to data input files to allow old formats to be read
and, where that hasn’t been possible, provided conversion programs. This has been particularly
true for recent releases, and PTI has maintained those conversion programs since rev 23. In recent
years PTI has added auxiliary programs to write out old versions of PSS®E raw data files.
5/18/2011 17
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
PSS®E Version 33
We recognize that customer effort is required to upgrade programs and automation files with a
major release of PSS®E. We’ve made a few targeted improvements to ease the effort required to
upgrade planning capabilities.
Specifically,
1. The header record for Power Flow raw data files now contains a revision number (see
Chapter 5 of the PSS®E Program Operation Manual). With the revision number set, any
version RAW file can be read by activity READ and the proper conversions will be applied
automatically. Adding the version number to existing RAW files or programs that create
them will allow these files to be used directly in PSS®E without applying external converters
or upgrading external programs to write the new format.
2. The header record for Sequence data files now contains a revision number. With the
revision number set, any version SEQ file can be read by activity RESQ and the proper
conversions will be applied automatically. Adding the version number to existing SEQ files
or programs that create them will allow these files to be used directly in PSS®E without
applying external converters or upgrading external programs to write the new format.
3. PTI added APIs for read-change files and read-by subsystem that accept a version
specification. These new APIs can be called directly from Automation files and allow the use
of older version RAW files without having to first apply external converters. For a full
description of these new APIs, see Chapter 1 of the PSS®E Application Program Interface
(API).
4. PTI added a suffix option for RDCH in the Line Mode Interpreter (LMI), RDCH, OPT, that will
allow the specification of a version for the data contained in the RDCH file. This allows the
proper converters to be applied automatically, meaning that PSS®E-30, 31 and 32 RDCH
files don’t need to be modified to be used in PSS®E-33. For more information see the
PSS®E Compatibility with Previous Releases Manual.
5. Where possible, we’ve allowed changes to APIs to accept old values. For example, if a dc
line number is specified for the dc line name, the number is converted to a name.
Where such permissiveness was not possible, the old APIs were kept, and new ones
created, such as BUS_DATA_2. BUS_DATA can still be used, and it will call
BUS_DATA_2 after adjusting the arguments for you.
Refer to Chapter 2 of the PSS®E Application Program Interface (API) for detailed information
on these new API routines.
6. The internal format of the PV and QV results files has changed, so PTI added versioning to
the APIs that read these files to allow the old versions to be read.
7. We’ve enhanced the LMI to read either PSS®E-30, 31, 32 or 33 response files. The mode
of operation is controlled by a new command, VERSION.
In a response file, you can tell the LMI to assume response file commands were written
for PSS®E-30, 31 or 32 and to interpret them accordingly, by setting the first line to
“version 30”, “version 31” or “version 32”. When the response file is terminated, you may
manually reset the LMI processing mode to PSS®E-33 format.
18 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
In an IPLAN program you can tell the LMI to assume response file commands were
written for PSS®E-30, 31 or 32 and to interpret them accordingly by setting the entering
”PUSH ‘version 30’”, ”PUSH ‘version 31’” or ”PUSH ‘version 32’” in the beginning of
your IPLAN program. As above, when the IPLAN program is terminated, you may
manually reset the LMI processing mode to PSS®E-33 format.
We intend to develop the capability to minimize update efforts for existing planning data in future
versions. For more on this see the PSS®E Compatibility with Previous Releases Manual.
Compiler Information
General Information
PSS®E-33 is built using the Intel Visual FORTRAN (IVF) 12.0 compiler and the Microsoft® Visual
Studio 2010 compiler and linker. This is the recommended platform to use for building user-written
extensions to PSS®E-33, such as CONEC, CONET, and user-written dynamics models.
FORTRAN code must be compiled with IVF 12.0 or later. IVF 12.0 comes with the VSPPE option,
which will work with PSS®E-33 as well. The PSS®E Environment Manager, which is delivered with
PSS®E-33, or downloadable from our website, can assist with maintaining environment variables
associated with controlling the compiler versions in use.
Additional Notes
** Please note that purchase of the compilers is not necessary if you are just running PSS®E. The
FORTRAN and C run-time libraries will continue to be included with PSS®E, as in the past. The
purchase of a compiler is required only if you are compiling CONEC and/or CONET, user-written
dynamics models, or programs that call USRCAS.
Intel has offered a special discounted upgrade fee to Siemens PTI customers. To purchase either
the upgrade or a new license of Intel Visual FORTRAN compiler under this offer, you must contact
Frankie Terlecki at frank.terlecki@intel.com. Please be sure Siemens PTI customer is stated in the
subject line.
Documentation
Changes in documentation content include the following:
Two Winding Transformer Zero Sequence Network Diagrams and Connection Codes
Three Winding Transformer Zero Sequence Network Diagrams and Connection Codes
Model Library
The following chapters have been added to the Model Library:
Chapter 23 - Branch Device Models
Chapter 24 - Machine and Wind Protection
Chapter 25 - Two-winding Device Transformer Models
Chapter 26 - Three-winding Device Transformer Models
Chapter 27 - Two-terminal dc Other Models
Chapter 28 - Miscellaneous Other Models
Chapter 29 - Model Functions
API Manual
Documentation for the following APIs is included:
Induction Machine Models APIs are available in section 4.11.
CCT Model APIs are available in section 4.12.
Induction Machine Bus Data 8.27
Induction Machine Data 8.28
Scenario and Event Study APIs 13.11 – 58
20 5/18/2011
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
API Manual continued:
ACCC_SINGLE_RUN_REPORT_3 ACCC_TRIP_COR_3 ACCC_WITH_COR_3
SWSBLZ2 ACCC_SOLUTION_REPORT
5/18/2011 21
Siemens Energy, Inc.
PSS®E-33 Release Notes Power Technologies International
___________________________
© Copyright 1990-2011 Siemens Energy, Inc., Siemens Power Technologies International (Siemens PTI)
Information in this document and any software described herein is confidential and subject to change without notice and does
not represent a commitment on the part of Siemens PTI. The software described in this document is furnished under a license
agreement or nondisclosure agreement and may be used or copied only in accordance with the terms of the agreement. No
part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including
photocopying, for any purpose other than the purchaser’s personal use, without the express written permission of Siemens
PTI.
®
PSS E high-performance transmission planning software is a registered trademark of Siemens PTI in the United States and other
countries.
Microsoft® Visual C/C++ and Microsoft Office Excel®is are registered trademarks of Microsoft Corporation in the United States and
other countries.
Intel® Visual Fortran Compiler for Windows is a trademark of Intel Corporation in the United States and other countries.
The Python™ programming language is a trademark of the Python Software Foundation.
Other names may be trademarks of their respective owners.
22 5/18/2011