POM
POM
E 32.0
Program Operation Manual
Revised June 2009
Siemens Energy, Inc.
Siemens Power Technologies International
400 State Street, PO Box 1058
Schenectady, NY 12301-1058 USA
+1 518-395-5000
www.siemens.com/power-technologies
Copyright 1990-2009 Siemens Energy, Inc., Siemens Power Technologies International (Siemens PTI)
Information in this manual 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
manual 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 manual may be reproduced or
transmitted in any form or by any means, electronic or mechanical, including photocopying, for any
purpose other than the purchasers personal use, without the express written permission of Siemens PTI.
PSS
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.
Table of Contents
Siemens Energy, Inc., Power Technologies International i
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Contacting Siemens PTI for Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2
Submitting Bug Reports and Feature Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Chapter 1 - Overview
1.1 PSS
E Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
1.3 Extending PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-13
2.6 Files Created By PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-13
PSS
E 32.0
Table of Contents Program Operation Manual
ii Siemens Energy, Inc., Power Technologies International
2.7 File System Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
2.7.1 Multiple Working Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
2.7.2 PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2.1 Startup Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.3 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3.1 Specifying the Maximum Number of Buses . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3.2 Setting Program Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.3.3 Program Run-Time Option Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Saved Case Specific Option Settings. . . . . . . . . . . . . . . . . . . . . . . . 3-6
User Specified Option Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Installation Dependent Option Settings . . . . . . . . . . . . . . . . . . . . . 3-10
3.4 Startup Parameter Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.4.1 WINDOWS.PRM Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.4.2 INI Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Chapter 4 - Operating Modes
4.1 How to Approach PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Activity Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.1 GUI Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.2 Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.2.3 Automation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.3 Interruption of PSS
E 32.0
Program Operation Manual Table of Contents
4.11 Activity Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10
Chapter 5 - Power Flow Data Entry, Modification, and Display Activities
5.1 Retrieving a Power Flow Saved Case File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1
Activity CASE
5.2 Reading Power Flow Raw Data into the Working Case . . . . . . . . . . . . . . . . . . . . . . .5-4
Activity READ
5.2.1 Power Flow Raw Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4
Extended Bus Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Q Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Case Identification Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Bus Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Load Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Fixed Bus Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Generator Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Non-Transformer Branch Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Transformer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Areas, Zones and Owners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Area Interchange Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Two-Terminal DC Transmission Line Data . . . . . . . . . . . . . . . . . . . 5-37
Voltage Source Converter (VSC) DC Transmission Line Data . . . . 5-40
Transformer Impedance Correction Tables. . . . . . . . . . . . . . . . . . . 5-43
Multi-Terminal DC Transmission Line Data. . . . . . . . . . . . . . . . . . . 5-44
Multi-Section Line Grouping Data . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Zone Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Interarea Transfer Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Owner Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
FACTS Device Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
Switched Shunt Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
End of Data Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
5.2.2 Operation of Activity READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-63
Bus Names Input Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
Bus Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
Plant and Machine Sequence Numbers . . . . . . . . . . . . . . . . . . . . . 5-64
Load Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
Fixed Shunt Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
Branch Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
Transformer Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
5.2.3 Change Case Data in a Standard READ . . . . . . . . . . . . . . . . . . . . . . . . . . .5-64
Merging Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
5.2.4 Subsystem READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-65
5.2.5 Reading Power Flow Raw Data Files Created by Previous Releases
of PSSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-66
5.3 Reading Power Flow Data Additions from the Terminal . . . . . . . . . . . . . . . . . . . . . .5-68
Activity TREA
PSS
E 32.0
Table of Contents Program Operation Manual
iv Siemens Energy, Inc., Power Technologies International
5.4 Adding Machine Impedance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
Activity MCRE
5.4.1 Machine Impedance Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
5.4.2 Operation of Activity MCRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
5.4.3 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
5.5 Reading Sequence Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
Activity RESQ
5.5.1 Sequence Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
Change Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
Positive Sequence Generator Impedance Data. . . . . . . . . . . . . . . 5-75
Negative Sequence Generator Impedance Data . . . . . . . . . . . . . . 5-76
Zero Sequence Generator Impedance Data . . . . . . . . . . . . . . . . . 5-76
Negative Sequence Shunt Load Data . . . . . . . . . . . . . . . . . . . . . . 5-77
Zero Sequence Shunt Load Data. . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
Zero Sequence Non-Transformer Branch Data . . . . . . . . . . . . . . . 5-78
Zero Sequence Mutual Impedance Data . . . . . . . . . . . . . . . . . . . . 5-79
Zero Sequence Transformer Data . . . . . . . . . . . . . . . . . . . . . . . . . 5-81
Zero Sequence Switched Shunt Data . . . . . . . . . . . . . . . . . . . . . . 5-90
Zero Sequence Fixed Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . 5-91
5.5.2 Operation of Activity RESQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91
5.5.3 Transformers in the Zero Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92
5.6 Reading Transactions Raw Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99
Activity REMM
5.6.1 Transactions Raw Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99
Participation Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99
Transaction Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100
5.6.2 Operation of Activity REMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101
5.6.3 Implications of the Participation Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-101
5.7 Reading / Changing Power Flow Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103
Activity RDCH
5.7.1 Operation of Activity RDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103
5.7.2 Reading RDCH Data Files Created by Previous Releases of PSSE . . . 5-104
5.7.3 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104
5.8 Changing Service Status and Power Flow Parametric Data . . . . . . . . . . . . . . . . . 5-106
Activity CHNG
5.8.1 Equipment Status Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107
5.8.2 Solution Parameter Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108
5.8.3 Interarea Transfer Data Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-108
5.9 Scaling Loads, Generators, and/or Shunts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109
Activity SCAL
5.9.1 Operation of Activity SCAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-110
5.9.2 Scaling Fixed Shunts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-110
5.9.3 Scaling Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-111
5.9.4 Scaling Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-111
5.9.5 Scaling Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-112
Siemens Energy, Inc., Power Technologies International v
PSS
E 32.0
Program Operation Manual Table of Contents
5.10 Electrically Disconnecting a Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-114
Activity DSCN
5.11 Electrically Reconnecting a Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116
Activity RECN
5.12 Removing Specified Buses and Connected Equipment . . . . . . . . . . . . . . . . . . . . .5-118
Activity EXTR
5.13 Deleting Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120
Activity PURG
5.13.1 Removing Individual Equipment Items . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-120
5.13.2 Removing Outaged Equipment in a Subsystem . . . . . . . . . . . . . . . . . . . . .5-121
5.13.3 Example of Activity PURG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-122
5.13.4 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-122
5.14 Joining Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-124
Activity JOIN
5.14.1 Operation of Activity JOIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-124
5.14.2 Example Progress Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-126
5.15 Splitting Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-127
Activity SPLT
5.15.1 Operation of Activity SPLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-127
5.15.2 Example of Activity SPLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-128
5.16 Tapping a Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-130
Activity LTAP
5.17 Changing Equipment Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-132
Activity MBID
5.18 Moving Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-134
Activity MOVE
5.18.1 Operation of Activity MOVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-134
5.18.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-136
5.19 Renumbering Buses in Auxiliary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-137
Activity RNFI
5.19.1 Bus Renumbering Translation Data File . . . . . . . . . . . . . . . . . . . . . . . . . . .5-137
5.19.2 Operation of Activity RNFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-137
5.20 Changing Area Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-139
Activity ARNM
Activity LDAR
5.20.1 Operation of Activity ARNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-139
5.20.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-140
5.20.3 Example of Activity ARNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-140
PSS
E 32.0
Table of Contents Program Operation Manual
vi Siemens Energy, Inc., Power Technologies International
5.21 Changing Owner Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-143
Activity OWNM
5.21.1 Operation of Activity OWNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-143
5.21.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-144
5.22 Changing Zone Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-145
Activity ZONM
Activity LDZO
5.22.1 Operation of Activity ZONM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-145
5.22.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-146
5.23 Modifying Resistances of Non-Transformer Branches . . . . . . . . . . . . . . . . . . . . . . 5-147
Activity MODR
5.23.1 Operation of Activity MODR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-147
5.23.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-148
5.24 Reading Sequence Data Additions from the Terminal . . . . . . . . . . . . . . . . . . . . . . 5-149
Activity TRSQ
5.25 Changing Sequence Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-150
Activity SQCH
5.26 Checking Branch Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-152
Activity BRCH
5.26.1 Branch Parameter Checks Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-152
5.26.2 Operation of Activity BRCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-154
5.27 Check for Islands Without a Swing Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-156
Activity TREE
5.27.1 Operation of Activity TREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-156
5.27.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-157
5.28 Checking/Changing Controlled Bus Scheduled Voltage . . . . . . . . . . . . . . . . . . . . 5-158
Activity CNTB
5.28.1 Operation of Activity CNTB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-159
5.28.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-160
5.29 Checking/Changing Transformer Adjustment Data . . . . . . . . . . . . . . . . . . . . . . . . 5-162
Activity TPCH
5.29.1 Operation of Activity TPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-163
5.29.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-164
5.30 Changing Adjustment Enable Flags of Transformers . . . . . . . . . . . . . . . . . . . . . . . 5-166
Activity TFLG
5.30.1 Operation of Activity TFLG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-166
Siemens Energy, Inc., Power Technologies International vii
PSS
E 32.0
Program Operation Manual Table of Contents
5.31 Performing Unit Commitment and Economic Dispatch . . . . . . . . . . . . . . . . . . . . . .5-168
Activity ECDI
5.31.1 Economic Dispatch Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . .5-169
Standard Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-169
Supplementary Units of Dispatch Groups . . . . . . . . . . . . . . . . . . . 5-170
5.31.2 Operation of Activity ECDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-171
5.31.3 Viewing Economic Dispatch Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-174
5.31.4 Dispatch Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-174
5.31.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-176
5.32 Displaying the Long Case Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-177
Activity PRTI
5.33 Managing Case Titles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-178
5.33.1 Importing a Long Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-179
Activity RETI
5.33.2 Changing the Long Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-180
Activity CHTI
5.33.3 Editing the Two-Line Case Title or the Long Title . . . . . . . . . . . . . . . . . . . .5-181
Activity EDTR
5.34 Counting System Components in the Working Case . . . . . . . . . . . . . . . . . . . . . . .5-182
Activity SIZE
5.35 Listing Unused Bus Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-184
Activity BUSN
5.36 Displaying Power Flow Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-186
Activity LIST
5.36.1 Operation of Activity LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-186
5.36.2 Listing Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-187
Case Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-187
Bus Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-190
Load Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-190
Plant Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-190
Generator Unit Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-190
Fixed Bus Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-191
Switched Shunt Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-191
Branch Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-191
Line Shunt Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-192
Two-Winding Transformer Data . . . . . . . . . . . . . . . . . . . . . . . . . . 5-192
Three-Winding Transformer Data . . . . . . . . . . . . . . . . . . . . . . . . . 5-193
Transformer Impedance Correction Table Data . . . . . . . . . . . . . . 5-193
Multi-Section Line Grouping Data . . . . . . . . . . . . . . . . . . . . . . . . . 5-194
DC Line Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-194
Area Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195
Interarea Transfer Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195
Zone Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195
Owner Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195
FACTS Device Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-196
PSS
E 32.0
Table of Contents Program Operation Manual
viii Siemens Energy, Inc., Power Technologies International
5.37 Listing Components of a Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-197
Activity EXAM
5.37.1 Operation of Activity EXAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-197
5.37.2 Listing Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-197
5.38 Listing Buses in Alphabetical Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-199
Activity ALPH
5.39 Listing Buses using Partial Bus Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-200
Activity FIND
5.40 Listing Bus Shunts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-202
Activity SHNT
5.41 Listing Outaged Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-204
Activity OUTS
5.42 Listing Sequence Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-206
Activity SQLI
5.42.1 Operation of Activity SQLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-206
5.42.2 Listing Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-207
Bus Load Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-207
Generator Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-207
Fixed Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-207
Switched Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-207
Non-Transformer Branch Data . . . . . . . . . . . . . . . . . . . . . . . . . . 5-208
Line Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-208
Two-Winding Transformer Data . . . . . . . . . . . . . . . . . . . . . . . . . . 5-209
Three-Winding Transformer Data. . . . . . . . . . . . . . . . . . . . . . . . . 5-209
Mutual Impedance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-209
5.43 Listing Sequence Data for a Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-211
Activity SQEX
5.43.1 Operation of Activity SQEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-211
5.43.2 Listing Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-211
5.44 Creating a Saved Case File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-213
Activity SAVE
5.45 Bus Renumbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-214
Activity BSNM
5.45.1 Renumbering Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-215
All Buses Without Area Blocking . . . . . . . . . . . . . . . . . . . . . . . . . 5-215
All Buses With Area Blocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-215
Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-215
Bus Number to Bus Number Translation . . . . . . . . . . . . . . . . . . . 5-216
Bus Name to Bus Number Translation. . . . . . . . . . . . . . . . . . . . . 5-216
Bus Number Packing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-217
5.45.2 Output Tabulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-217
5.45.3 Examples of Activity BSNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-218
5.46 Saving the Working Case in an IEEE Common Format File . . . . . . . . . . . . . . . . . 5-220
Activity RWCM
Siemens Energy, Inc., Power Technologies International ix
PSS
E 32.0
Program Operation Manual Table of Contents
5.47 Saving Machine Impedance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-222
Activity RWMA
5.47.1 Operation of Activity RWMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-222
5.47.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-223
Transfer Machine Data to Another Case. . . . . . . . . . . . . . . . . . . . 5-223
Stability Data in IEEE Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-224
Machine Status Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-224
Split Fractions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-224
5.48 Creating a Power Flow Raw Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-225
Activity RAWD
5.48.1 Operation of Activity RAWD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-226
5.48.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-227
5.49 Creating a Sequence Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-229
Activity RWSQ
5.49.1 Operation of Activity RWSQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-229
5.49.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-230
5.50 Creating a Transactions Raw Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-231
Activity RWMM
5.50.1 Operation of Activity RWMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-231
5.50.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-231
Chapter 6 - Power Flow Solution Activity Descriptions
6.1 About Power Flow Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1
6.2 Power Flow Solution Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
6.2.1 Using Acceleration Factors and Solution Tolerances . . . . . . . . . . . . . . . . . . .6-4
6.2.2 Automatic Power Flow Solution Adjustments . . . . . . . . . . . . . . . . . . . . . . . . .6-5
Adjusting Transformer Off-Nominal Tap Ratio . . . . . . . . . . . . . . . . . 6-5
Adjusting Transformer Voltage Control . . . . . . . . . . . . . . . . . . . . . . . 6-6
Adjusting Transformer Mvar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Adjusting Transformer Phase Shift Angle . . . . . . . . . . . . . . . . . . . . . 6-7
Adjusting Transformer Direct Current (DC) Converter Taps . . . . . . . 6-7
Adjusting Net Interchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Adjusting Switched Shunt Admittance. . . . . . . . . . . . . . . . . . . . . . . . 6-8
6.3 Applying Gauss-Seidel Power Flow Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
Activity SOLV
6.3.1 About Power Flow Iterative Solution Algorithms . . . . . . . . . . . . . . . . . . . . . .6-11
6.3.2 About Power Flow Boundary Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12
6.3.3 Boundary Conditions of Constant MVA Loads . . . . . . . . . . . . . . . . . . . . . . .6-12
6.3.4 Boundary Conditions of Constant Current Loads . . . . . . . . . . . . . . . . . . . . .6-14
6.3.5 Boundary Conditions of Constant Impedance Loads . . . . . . . . . . . . . . . . . .6-15
6.3.6 Boundary Conditions of Composite Loads . . . . . . . . . . . . . . . . . . . . . . . . . .6-16
6.3.7 Boundary Conditions of the Swing Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16
6.3.8 Boundary Conditions of Standard Generators . . . . . . . . . . . . . . . . . . . . . . .6-16
6.3.9 Boundary Conditions of Multiple Identical Generators . . . . . . . . . . . . . . . . .6-18
6.3.10 Boundary Conditions of Multiple Non-Identical Generators . . . . . . . . . . . . .6-18
6.3.11 Operation of Activity SOLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-18
PSS
E 32.0
Table of Contents Program Operation Manual
x Siemens Energy, Inc., Power Technologies International
6.3.12 Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
6.3.13 Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
6.3.14 Switched Shunt Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
6.3.15 FACTS Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Bypassed Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Constant Series Impedance Mode. . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Constant Series Voltage Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
IPFC Master and Slave Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
All Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
6.3.16 DC Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
Capacitor Commutated DC Lines. . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
VSC dc Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
6.3.17 AC Voltage Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Swing Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Setpoint Voltage Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Band Mode Voltage Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
6.3.18 Characteristics of Activity SOLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
6.3.19 Automatic Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
6.4 Applying Modified Gauss-Seidel Power Flow Solution . . . . . . . . . . . . . . . . . . . . . . . 6-35
Activity MSLV
6.5 Applying Fully-Coupled Newton-Raphson Power Flow Solution . . . . . . . . . . . . . . . 6-37
Activity FNSL
6.5.1 Characteristics of Activity FNSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39
Convergence Testing Used in Prior Releases . . . . . . . . . . . . . . . . 6-42
6.5.2 Automatic Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43
Tap Ratio Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
Voltage Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
Mvar Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
DC Line Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47
Phase Shift Angle Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48
Area Interchange Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48
Switched Shunt Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
Automatic Adjustment Solution Parameters. . . . . . . . . . . . . . . . . . 6-50
6.5.3 Non-Divergent Solution Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
Non-Divergent Solution Methodology. . . . . . . . . . . . . . . . . . . . . . . 6-52
Convergence Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
6.6 Applying Decoupled Newton-Raphson Power Flow Solution . . . . . . . . . . . . . . . . . . 6-57
Activity NSOL
6.7 Applying Fixed Slope Decoupled Newton-Raphson Power Flow Solution . . . . . . . . 6-60
Activity FDNS
6.8 Applying Newton-Raphson Power Flow Solution with Inertial / Governor Dispatch . 6-63
Activity INLF
6.8.1 Inertia and Governor Response Data File Contents . . . . . . . . . . . . . . . . . . 6-64
6.8.2 Operation of Activity INLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66
6.8.3 Inertial Power Flow Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67
6.8.4 Governor Response Power Flow Solution . . . . . . . . . . . . . . . . . . . . . . . . . 6-68
6.8.5 Example of a Generator Contingency Analysis Solution . . . . . . . . . . . . . . . 6-69
Siemens Energy, Inc., Power Technologies International xi
PSS
E 32.0
Program Operation Manual Table of Contents
6.8.6 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-70
6.9 Overview: Contingency Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-72
6.9.1 Reliability Testing Criteria for Contingency Analysis . . . . . . . . . . . . . . . . . .6-72
6.9.2 Applying Deterministic Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-75
Applying Transmission Transfer Limit Analysis. . . . . . . . . . . . . . . . 6-75
Applying Voltage Stability Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 6-75
6.9.3 Applying Probabilistic Reliability Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . .6-76
6.9.4 About Generation Dispatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-76
6.9.5 Tripping Simulation and Corrective Action Analysis . . . . . . . . . . . . . . . . . . .6-78
6.9.6 Substation Reliability Assessment Analysis . . . . . . . . . . . . . . . . . . . . . . . . .6-78
6.10 Performing AC Contingency Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-79
Activity ACCC
6.10.1 AC Contingency Solution Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-80
6.10.2 Running AC Contingency Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-83
6.10.3 AC Contingency Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-83
6.10.4 AC Contingency Post Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-85
6.10.5 AC Contingency Result Retrieval Routines . . . . . . . . . . . . . . . . . . . . . . . . .6-85
6.10.6 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-85
6.10.7 Implementing Generation Dispatch Algorithm in Contingency Analysis . . . .6-87
6.10.8 Appending Data to a Contingency Solution Output File . . . . . . . . . . . . . . . .6-88
6.10.9 AC Contingency Single Run Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-89
6.10.10 Single Run Report Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-92
Overload Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-93
Loading Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96
Available Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-98
Non-converged Network Conditions . . . . . . . . . . . . . . . . . . . . . . . 6-100
Corrective Action Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102
6.10.11 AC Contingency Multiple Run Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-105
6.10.12 Multiple Run Output Report Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-109
Contingency Solution Output Files Report . . . . . . . . . . . . . . . . . . 6-110
Monitored Element Summary Report . . . . . . . . . . . . . . . . . . . . . . 6-110
Missing Monitored Elements Report . . . . . . . . . . . . . . . . . . . . . . . 6-110
Missing Monitored Voltage Buses Report . . . . . . . . . . . . . . . . . . . 6-111
Contingency Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-111
Missing Contingencies Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-111
Non-converged Contingencies Report . . . . . . . . . . . . . . . . . . . . . 6-111
Base Case Loading Violations Report. . . . . . . . . . . . . . . . . . . . . . 6-111
Contingency Case All Loading Violations Report . . . . . . . . . . . . . 6-112
Contingency Case Worst Case Loading Violations Report . . . . . . 6-112
Base Case Voltage Violations Reports . . . . . . . . . . . . . . . . . . . . . 6-113
Contingency Case All Voltage Violations Reports. . . . . . . . . . . . . 6-113
Contingency Case Worst Case Voltage Violations Reports . . . . . 6-114
6.11 AC Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-115
6.11.1 Constraints and Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-115
6.11.2 Weighting and Penalty Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-117
6.11.3 AC Corrective Action Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-120
6.11.4 Viewing AC Corrective Actions Results. . . . . . . . . . . . . . . . . . . . . . . . . . . .6-122
6.11.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-124
PSS
E 32.0
Table of Contents Program Operation Manual
xii Siemens Energy, Inc., Power Technologies International
6.12 Performing Multi-Level AC Contingency Solution . . . . . . . . . . . . . . . . . . . . . . . . . 6-125
6.12.1 Terms Used in Multiple-Level Contingency Analysis . . . . . . . . . . . . . . . . 6-126
6.12.2 Power Flow Control Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-127
6.12.3 Multiple Contingency Analysis Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-128
6.12.4 Classification of Contingency Analysis Results . . . . . . . . . . . . . . . . . . . . . 6-130
6.12.5 About Contingency List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-132
6.12.6 Wind Chime Algorithm for Multiple Level Contingency Analysis . . . . . . . . 6-134
6.12.7 About Tripping Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136
6.12.8 Tripping Simulation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136
6.12.9 Tripping Element Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-137
Monitored Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-137
Trip Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-139
Automatic Single Tripping Record . . . . . . . . . . . . . . . . . . . . . . . . 6-140
6.12.10 Corrective Actions Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-142
6.12.11 Operation of Multiple Contingency Analysis Activity . . . . . . . . . . . . . . . . . 6-145
6.12.12 Contingency Analysis Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-145
6.12.13 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-145
6.13 Calculating Probabilistic Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-147
6.13.1 Probabilistic Reliability Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-148
6.13.2 Outage Statistics Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-150
6.13.3 Analyzing Probabilistic Assessment Results . . . . . . . . . . . . . . . . . . . . . . . 6-154
System Probabilistic Index Summary. . . . . . . . . . . . . . . . . . . . . . 6-154
System Loss of Load Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-156
Branch Flow Overloading Indices. . . . . . . . . . . . . . . . . . . . . . . . . 6-156
6.13.4 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-158
6.14 Calculating Substation Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-160
6.14.1 Substation Reliability Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-160
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-160
Run Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-160
Input Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-161
6.14.2 Modeling the Substation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-161
6.14.3 Failure Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-162
Performing the Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
Analyzing Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-167
Substation Component Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-167
Contingency Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-169
Bus Load Curtailment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-173
Substation Load Curtailment Report . . . . . . . . . . . . . . . . . . . . . . 6-175
6.15 Performing PV/QV Analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176
6.16 PV Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-177
6.16.1 Retrieving Results from a Previous PV Analysis . . . . . . . . . . . . . . . . . . . . 6-182
6.16.2 Implementing a Specific PV Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-182
6.17 QV Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-184
6.17.1 Retrieving Results from a Previous QV Analysis . . . . . . . . . . . . . . . . . . . 6-186
6.18 Basic Engineering Guide to PV and QV Curves Applications . . . . . . . . . . . . . . . . 6-187
6.18.1 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-187
6.18.2 PV Analysis (PV Curves) Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-187
6.18.3 QV Analysis (QV Curves) Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-192
Siemens Energy, Inc., Power Technologies International xiii
PSS
E 32.0
Program Operation Manual Table of Contents
Chapter 7 - Linear Network Analysis
7.1 Building the Distribution Factor Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1
Activity DFAX
7.1.1 Linear Network Analysis Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
File Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Special Data Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.1.2 Subsystem Description Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . .7-3
7.1.3 Monitored Element Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6
Flow Monitoring Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Voltage Monitoring Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
7.1.4 Contingency Description Data File Contents . . . . . . . . . . . . . . . . . . . . . . . .7-10
Contingency Case Block Structure . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Automatic Contingency Specification . . . . . . . . . . . . . . . . . . . . . . . 7-15
7.1.5 Operation of Activity DFAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-18
7.1.6 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-19
7.2 Calculating Distribution Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-21
Activity OTDF
7.2.1 Operation of Activity OTDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-21
7.2.2 Output Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-22
7.2.3 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-24
7.3 Estimating Severity Rankings for Single Line Outage Contingencies . . . . . . . . . . . .7-26
Activity RANK
7.3.1 Contingency Ranking Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-26
7.3.2 Contingency Ranking Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-29
7.3.3 Operation of Activity RANK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-30
7.3.4 Analyzing AC Contingency Ranking Results . . . . . . . . . . . . . . . . . . . . . . . .7-31
7.3.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-33
7.4 Applying the DC Linearized Network Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-35
Activity DCLF
7.4.1 DC Linearized Network Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-35
7.4.2 Operation of Activity DCLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-36
7.4.3 Output Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-38
7.4.4 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-41
7.5 Calculating Linearized Network Contingency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-43
Activity DCCC
7.5.1 Operation of Activity DCCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-44
7.5.2 Overload Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-44
7.5.3 Linear Network DC Loading Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-47
7.5.4 Contingency Case Flow Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-49
7.5.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-50
7.6 Performing DC Corrective Action Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-51
7.6.1 About DC Corrective Action Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-51
7.6.2 Operation of DC Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-51
7.6.3 DC Corrective Action Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-52
7.6.4 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-54
PSS
E 32.0
Table of Contents Program Operation Manual
xiv Siemens Energy, Inc., Power Technologies International
7.7 Calculating Transmission Interchange Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55
Activity TLTG
7.7.1 Overview: Transmission Transfer Limit Analysis . . . . . . . . . . . . . . . . . . . . . 7-55
7.7.2 Calculating Transmission Transfer Limits . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56
7.7.3 Transmission Transfer Limit Analysis Options . . . . . . . . . . . . . . . . . . . . . . 7-57
7.7.4 Operation of Activity TLTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59
7.7.5 Analyzing Transfer Limit Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61
7.7.6 Output Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61
7.7.7 Transfer Limit Analysis Flows For Contingency Cases . . . . . . . . . . . . . . . . 7-65
7.7.8 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
7.8 Calculating Sequential Participation Interchange Limits . . . . . . . . . . . . . . . . . . . . . 7-69
Activity SPIL
7.8.1 Subsystem Participation Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . 7-70
7.8.2 Interchange Limits Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
7.8.3 Operation of Activity SPIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74
7.8.4 Analyzing Interchange Limit Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
7.8.5 Output Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
7.8.6 Example Activity SPIL Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
7.8.7 Interchange Limits Contingency Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
7.8.8 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
7.9 Performing Interchange Limit Analysis with Two Opposing Systems . . . . . . . . . . . 7-83
Activity POLY
7.9.1 Interchange Limit Analysis Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-83
7.9.2 Operation of Activity POLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-86
7.9.3 Output Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88
7.9.4 Interchange Limit (Two-Opposing Systems) Graphical Output . . . . . . . . . . 7-91
7.9.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-92
7.10 Midwest MW-Mile Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-94
Activity MWMI
Chapter 8 - Network Reduction
8.1 Overview: Equivalent (Reduced) Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
8.1.1 Nomenclature of Equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
8.2 Methodology of the Electrical Equivalent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8.2.1 Defining Boundaries and Boundary Buses . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
8.2.2 Handling DC Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
8.2.3 Approaching the Network Equivalent Process . . . . . . . . . . . . . . . . . . . . . . . 8-5
8.3 Building an Electrical Equivalent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Activity EEQV
8.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
8.3.2 Network Equivalence Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
8.3.3 Operation of Activity EEQV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
8.3.4 Equivalencing Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
8.3.5 Example: Equivalencing a Power Flow Case . . . . . . . . . . . . . . . . . . . . . . . 8-11
8.3.6 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Siemens Energy, Inc., Power Technologies International xv
PSS
E 32.0
Program Operation Manual Table of Contents
8.4 Applying Net Generation with Load at All Non-Boundary Buses . . . . . . . . . . . . . . . .8-16
Activity GNET
8.4.1 Example of Net Generation with Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-17
8.5 Applying Net Generation with Load at All Buses Except Boundary Buses . . . . . . . .8-20
Activity NETG
8.6 Equivalencing Radial Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-21
Activity EQRD
8.6.1 Operation of Activity EQRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-23
8.6.2 Example: Equivalencing Radial Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-23
8.6.3 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-24
8.7 Equivalencing Radial Buses, with Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-26
Activity RDEQ
8.7.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-27
8.8 Converting Net Boundary Bus Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-29
Activity BGEN
8.9 Building a Three-Sequence Electrical Equivalent . . . . . . . . . . . . . . . . . . . . . . . . . . .8-31
Activity SCEQ
8.9.1 Creating Short Circuit Equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-31
8.9.2 Constructing a Short Circuit Equivalent . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-35
8.9.3 Short Circuit Equivalent Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-35
8.9.4 Operation of Activity SCEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-36
8.9.5 Form of the Equivalent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-36
8.9.6 Example: Short Circuit Equivalencing of a Power Flow Case . . . . . . . . . . .8-37
8.9.7 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-40
Chapter 9 - Unbalanced Fault Analysis
9.1 Overview: Short-Circuit Fault Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1
9.2 Preparing Short Circuit Sequence Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
9.2.1 Short Circuit Change Case Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4
9.2.2 Positive Sequence Generator Impedance Data . . . . . . . . . . . . . . . . . . . . . . .9-4
9.2.3 Negative Sequence Generator Impedance Data . . . . . . . . . . . . . . . . . . . . . .9-5
9.2.4 Zero Sequence Generator Impedance Data . . . . . . . . . . . . . . . . . . . . . . . . .9-5
9.2.5 Negative Sequence Shunt Load Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7
9.2.6 Zero Sequence Shunt Load Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7
9.2.7 Zero Sequence Branch Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-8
9.2.8 Zero Sequence Mutual Impedance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
9.2.9 Zero Sequence Transformer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-11
Analyzing Transformer Phase Shift Impact . . . . . . . . . . . . . . . . . . . 9-18
Analyzing Sequence Impedance Adjustment as a Function of Tap
Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Analyzing Generators and Step-Up Transformers . . . . . . . . . . . . . 9-21
9.2.10 Zero Sequence Switched Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-24
9.3 Appending Sequence Data to the Power Flow Case . . . . . . . . . . . . . . . . . . . . . . . .9-25
PSS
E 32.0
Table of Contents Program Operation Manual
xvi Siemens Energy, Inc., Power Technologies International
9.4 Fault Calculation Modeling Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
9.4.1 Detailed Fault Calculation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
9.4.2 Detailed Fault Calculation Models for DC Lines and FACTS Devices . . . . 9-27
9.4.3 Simplified Fault Calculation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
9.4.4 Special Conditions for Fault Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
9.5 Detailed Unbalanced Fault Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
9.5.1 Bus Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
9.5.2 Phase Closed Unbalances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
9.5.3 Line Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
9.6 Preparing Sequence Network for Unbalanced Network Solution . . . . . . . . . . . . . . . 9-32
Activity SEQD
9.6.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
9.7 Performing Fault Analysis under Unbalance Condition . . . . . . . . . . . . . . . . . . . . . . 9-37
Activity SCMU
9.7.1 Unbalanced Fault Analysis Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
9.7.2 Bus Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
9.7.3 Line Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
9.7.4 Branch with One Open End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
9.7.5 Phase Closed Unbalances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
9.7.6 Pre-Calculation Network Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
9.7.7 Operation of Activity SCMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
9.7.8 Unbalance Condition Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
9.7.9 Example: Unbalance Condition Summary Report . . . . . . . . . . . . . . . . . . . . 9-45
9.7.10 Unbalanced Fault Analysis Detailed Report . . . . . . . . . . . . . . . . . . . . . . . . 9-49
9.7.11 Observation of Transformer Currents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
9.7.12 Working with a Two-Wire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-54
9.7.13 Transmission Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
9.7.14 Transformers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
9.7.15 Secondary Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
9.7.16 Faults on a Two-Phase System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
9.7.17 Examples of Two-Wire Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
9.7.18 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-71
9.8 Performing Detailed Fault Analysis under Unbalance Condition . . . . . . . . . . . . . . . 9-74
Activity SCOP
9.9 Calculating Automatic Sequencing Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-76
Activity ASCC
9.9.1 Automatic Sequencing Fault Selection Options . . . . . . . . . . . . . . . . . . . . . 9-78
9.9.2 Fault Control Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-84
9.9.3 Operation of Activity ASCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-85
9.9.4 Detailed Bus Output Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-85
9.9.5 Example: Automatic Sequencing, 3-Phase Faults, ASCC API . . . . . . . . . . 9-88
9.9.6 Example: Automatic Sequencing, 3-Phase & Single L-G Faults,
ASCC API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-90
9.9.7 Relay File Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-92
9.9.8 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-92
Siemens Energy, Inc., Power Technologies International xvii
PSS
E 32.0
Program Operation Manual Table of Contents
9.10 Calculating Fault Currents to ANSI Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-94
Activity ANSI
9.10.1 ANSI Fault Specification Data File Contents . . . . . . . . . . . . . . . . . . . . . . . .9-95
9.10.2 ANSI Fault Current Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-96
9.10.3 Operation of Activity ANSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-97
9.10.4 ANSI Fault Calculation Output Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-97
9.10.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-100
9.11 Using Classical Fault Analysis Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-101
Activity FLAT
9.11.1 Special Fault Voltage Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-101
9.11.2 Classical Short-Circuit Assumptions Options . . . . . . . . . . . . . . . . . . . . . . .9-101
IEC909 Fault Calculations Options . . . . . . . . . . . . . . . . . . . . . . . . 9-102
9.12 Calculating Short Circuit Currents According to IEC 60909 Standard . . . . . . . . . .9-105
Activity IECS
9.12.1 IEC Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-107
GSU, Equivalent Generator and Motor Data. . . . . . . . . . . . . . . . . 9-108
Transformer Nameplate Winding MVA Data . . . . . . . . . . . . . . . . . 9-110
9.12.2 Fault Control Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-110
9.12.3 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-111
9.13 Calculating Circuit Breaker Interrupting Duty . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-112
Activity BKDY
9.13.1 How PSS
E 32.0
Table of Contents Program Operation Manual
xviii Siemens Energy, Inc., Power Technologies International
Chapter 10 - Power Flow Reports
10.1 Analyzing Power Flow Solution Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
10.2 Producing a Standard Power Flow Solution Report . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Activity POUT
Bus Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
FACTS Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
DC Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Branch Quantities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Fault MVA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
10.3 Producing a Wide-Format Power Flow Solution Report . . . . . . . . . . . . . . . . . . . . . 10-11
Activity LOUT
Bus Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
FACTS Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
DC Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Branch Quantities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Fault MVA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
10.4 Producing a Wide-Format Power Flow Solution Report in Amps . . . . . . . . . . . . . . 10-18
Activity LAMP
Bus Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
FACTS Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
DC Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Branch Quantities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Fault MVA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
10.5 Summarizing Subsystem Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
Activity SUBS
System Swing Bus Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Area Slack Bus Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Component Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Subsystem Totals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Branch Totals by Voltage Level . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
10.6 Summarizing Load Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Activity LODR
10.6.1 Operation of Activity LODR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
10.6.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
10.7 Summarizing Area Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
Activity AREA
10.8 Summarizing Owner Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Activity OWNR
10.9 Summarizing Zone Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38
Activity ZONE
10.10 Reporting Interchange by Area/Owner/Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42
Siemens Energy, Inc., Power Technologies International xix
PSS
E 32.0
Program Operation Manual Table of Contents
10.11 Summarizing Area-to-Area Interchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-43
Activity INTA
10.12 Summarizing Zone-to-Zone Interchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-45
Activity INTZ
10.13 Summarizing Loadings on Ties from Interchange Areas . . . . . . . . . . . . . . . . . . . .10-47
Activity TIES
10.14 Summarizing Loadings on Ties from Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-49
Activity TIEZ
10.15 Viewing Network Limit Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-51
10.16 Producing a Branch Overload Checking Report . . . . . . . . . . . . . . . . . . . . . . . . . . .10-52
Activity RAT3
10.17 Producing a Transformer Overload Checking Report . . . . . . . . . . . . . . . . . . . . . . .10-55
Activity OLTR
10.18 Producing a Transmission Line Overload Checking Report . . . . . . . . . . . . . . . . . .10-58
Activity OLTL
10.19 Producing a Branch Current Ratings Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-61
Activity RATE
10.20 Producing an Out-of-Limits Bus Voltage Report . . . . . . . . . . . . . . . . . . . . . . . . . . .10-64
Activity VCHK
10.21 Producing a Machine Reactive Capability Report . . . . . . . . . . . . . . . . . . . . . . . . . .10-66
Activity GCAP
10.21.1 Machine Capability Curve Data File Contents . . . . . . . . . . . . . . . . . . . . . .10-66
10.21.2 Operation of Activity GCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-68
10.21.3 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-71
10.22 Producing a Generator Bus Limits Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-72
Activity GENS
10.23 Producing a Machine Terminal Limits Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-75
Activity GEOL
10.23.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-78
10.24 Producing a Regulated Bus Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-80
Activity REGB
10.25 Producing a Controlling Transformer Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-83
Activity TLST
10.26 Comparing Power Flow Case Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-86
Activity CMPR
10.27 Comparing Power Flow Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-88
Activity DIFF
10.27.1 Operation of Activity DIFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-88
10.27.2 Bus Related Data Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-91
10.27.3 Branch Related Data Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-94
PSS
E 32.0
Table of Contents Program Operation Manual
xx Siemens Energy, Inc., Power Technologies International
10.28 Displaying Power Flow Solution Differences on a Diagram . . . . . . . . . . . . . . . . . . 10-98
Activity GDIF
10.29 Comparing AC Tie Branches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-100
Activity DFTI
10.30 Reporting DC Network Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-105
Activity MTDC
10.31 Generating a Graphical Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-106
Activity GRPG
10.31.1 GRPG Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-107
Setup Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-107
Miscellaneous Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-108
Drawing Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-109
Text Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-115
Assignment Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-117
Conditional Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-119
Termination Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-120
10.32 Viewing Graphical Output of Fault Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . 10-122
10.32.1 Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-122
10.32.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-125
10.33 Exporting Power Flow Results to Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-141
10.34 Displaying Power Flow Solution on the Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 10-142
Activity GOUT
10.35 Displaying Power Flow Data on the Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-143
Activity GEXM
Chapter 11 - Balanced Switching
11.1 Overview: Balanced Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
11.1.1 Objectives of a Balanced Switching Study . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
11.1.2 Preparing a Power Flow Case for Balanced Switching . . . . . . . . . . . . . . . . 11-4
11.1.3 Establishing the Power Flow Base Case for Balanced Switching . . . . . . . . 11-4
11.1.4 Performing a Balanced Switching Study . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
11.2 Converting Generators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Activity CONG
11.2.1 Converting the Generators for Balanced Switching . . . . . . . . . . . . . . . . . . 11-7
11.2.2 Generator Apparent Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
11.2.3 Generator Step-Up Transformers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
11.2.4 Operation of Activity CONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
11.3 Converting Load Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Activity CONL
11.3.1 Modeling Load Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
11.3.2 Basic Load Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
11.3.3 Converting Load Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
11.3.4 Converting Loads for Balanced Switching . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
11.3.5 Operation of Activity CONL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Siemens Energy, Inc., Power Technologies International xxi
PSS
E 32.0
Program Operation Manual Table of Contents
11.3.6 Example of Load Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-15
11.3.7 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-16
11.4 Reconverting Load Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-18
Activity RCNL
11.4.1 Reconverting Load Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-18
11.4.2 Operation of Activity RCNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-20
11.4.3 Example of Load Reconstruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-20
11.4.4 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-21
11.5 Ordering Network Buses for Matrix Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . .11-22
Activity ORDR
11.6 Factorizing the Network Admittance Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-25
Activity FACT
11.6.1 About the Power Flow Network Admittance Matrix . . . . . . . . . . . . . . . . . .11-25
11.6.2 Operation of Activity FACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-27
11.6.3 Exporting the Power Flow Network Admittance Matrix . . . . . . . . . . . . . . . .11-28
11.7 Solving the Converted Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-30
Activity TYSL
11.7.1 Example:Voltage Rise on Open Line End . . . . . . . . . . . . . . . . . . . . . . . . .11-32
11.7.2 Example: Open Line End Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-34
11.7.3 Example: Motor Starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-34
11.7.4 Example: Fault Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-36
11.7.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-38
Chapter 12 - Transmission Pricing and Open Access
12.1 Overview: Open Access and Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-1
12.2 Managing Transaction Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-2
12.2.1 Transmission Access Calculators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-3
12.3 Calculating Transaction Event Impact on Monitored Elements . . . . . . . . . . . . . . . . .12-4
Activity IMPC
12.3.1 Output Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-5
12.3.2 Example: Transaction Event Impact on Monitored Elements . . . . . . . . . . . .12-5
12.3.3 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-6
12.4 Calculating Line Loading Relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-7
Activity LLRF
12.4.1 Operation of Activity LLRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-8
12.4.2 Output Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-9
Curtailing and Restoring Transactions . . . . . . . . . . . . . . . . . . . . . . 12-9
Distribution Factor Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
12.4.3 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-10
12.5 Making Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-11
Activity ALOC
12.5.1 Output Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-12
12.5.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-13
PSS
E 32.0
Table of Contents Program Operation Manual
xxii Siemens Energy, Inc., Power Technologies International
Chapter 13 - Optimal Power Flow
13.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
13.2 Conventional Power Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
13.3 Optimal Power Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
13.3.1 Objective Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
13.3.2 Constraints and Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
13.3.3 Sensitivities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
13.4 Conventional Power Flow Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
13.4.1 Bus Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
13.4.2 Load Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
13.4.3 Fixed Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
13.4.4 Generator Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
13.4.5 Non-Transformer Branch Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
13.4.6 Transformer Adjustment Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
13.4.7 Area Interchange Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
13.4.8 Two Terminal DC Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
13.4.9 Voltage Source Converter Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
13.4.10 Transformer Impedance Correction Data . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
13.4.11 Multi-Terminal DC Line Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
13.4.12 FACTS Device Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
13.4.13 Switched Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
13.5 Modeling Power Flow Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
13.5.1 Scalar Quadratic Penalties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
13.5.2 Soft Limit Penalties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
13.5.3 Treatment of Transformers and Switched Shunts . . . . . . . . . . . . . . . . . . . 13-10
13.5.4 Treatment of Local Generator Voltage Controls . . . . . . . . . . . . . . . . . . . . 13-10
Treatment of Optimized Generators. . . . . . . . . . . . . . . . . . . . . . . 13-11
Treatment of Non-optimized Generators . . . . . . . . . . . . . . . . . . . 13-11
13.5.5 Reactive Generation Reserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
13.6 OPF Modeling Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
13.6.1 Active Power Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
13.6.2 Adjustable Bus Shunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
13.6.3 Load Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
13.6.4 Adjustable Branch Reactance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
13.6.5 Generator Reactive Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
13.6.6 Generator Period Reserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
13.6.7 Regulated Area Interchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21
13.6.8 Linear Constraint Dependency Equation . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
13.6.9 Other Dependent Variable Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
13.7 Solution Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
13.7.1 The Nonlinear Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
13.7.2 Accommodating Inequality Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
Soft Limit Treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
Hard Limit Barrier Treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
13.7.3 Formulating the Equation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
Iterative Solution Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
Solution Convergence Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
Siemens Energy, Inc., Power Technologies International xxiii
PSS
E 32.0
Program Operation Manual Table of Contents
13.8 Data Input and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-37
13.8.1 PSS
E 32.0
Table of Contents Program Operation Manual
xxiv Siemens Energy, Inc., Power Technologies International
13.10 Optimal Power Flow Solution Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-68
13.10.1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-68
13.10.2 General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-71
13.10.3 Tolerance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
13.10.4 Control Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-76
13.10.5 Reporting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-77
13.11 Solution Results and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-78
13.11.1 OPF Progress Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-78
Problem Size Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-78
Solution Iteration Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-80
Solution Termination Message. . . . . . . . . . . . . . . . . . . . . . . . . . . 13-82
Labeling Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-82
13.11.2 OPF Solution Results Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-84
13.11.3 OPF Optimization Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-84
Infeasible Variable Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-85
Post Solution Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-85
Lagrange Multipliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-87
13.12 Examining OPF Data and Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-88
13.13 Listing Control and Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-89
13.14 Optimal Power Flow Solution Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-92
13.14.1 Solution Termination Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-92
13.14.2 Interface Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-92
13.14.3 Bounded, Infeasible and Opened Voltage Magnitudes . . . . . . . . . . . . . . . 13-93
13.14.4 Bounded and Infeasible Reactive Generation . . . . . . . . . . . . . . . . . . . . . . 13-94
13.14.5 Bounded or Infeasible Line Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-94
13.14.6 Generator Fuel Cost Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-95
13.14.7 Generation Reserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-96
13.14.8 Regulated Voltage Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-96
13.14.9 Tap Changing Transformers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-98
13.14.10Phase Shifting Transformers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-99
13.14.11Added Shunts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-100
13.14.12Switched Shunts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-100
13.14.13Load Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-101
13.14.14Series Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-102
13.14.15Regulated Area Interchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-102
13.15 OPF Raw Data File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-103
13.15.1 Data Modification Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-103
13.15.2 Bus Voltage Attribute Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-103
13.15.3 Adjustable Bus Shunt Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-104
13.15.4 Bus Load Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-104
13.15.5 Adjustable Bus Load Table Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-105
13.15.6 Generator Dispatch Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-105
13.15.7 Active Power Dispatch Table Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-105
13.15.8 Generation Reserve Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-106
13.15.9 Generation Reactive Capability Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-106
13.15.10Adjustable Branch Reactance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-107
13.15.11Piece-wise Linear Cost Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-107
13.15.12Piece-wise Quadratic Cost Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-108
13.15.13Polynomial and Exponential Cost Tables . . . . . . . . . . . . . . . . . . . . . . . . 13-108
13.15.14Period Reserve Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-108
Siemens Energy, Inc., Power Technologies International xxv
PSS
E 32.0
Program Operation Manual Table of Contents
13.15.15Branch Flow Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-109
13.15.16Interface Flow Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-109
13.15.17Linear Constraint Dependency Data . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-110
Chapter 14 - Dynamic Simulation Activity Descriptions
14.1 Reading Dynamics Model Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-2
Activity DYRE
14.1.1 Dynamics Model Raw Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . .14-2
Generator Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Current Compensating Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Stabilizer and Excitation Limiter Models . . . . . . . . . . . . . . . . . . . . . 14-4
Excitation System Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5
Turbine Governor Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5
Turbine Load Controller Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Load Characteristic Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Load Relay Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Line Relay Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Auxiliary-Signal Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
DC Line Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
FACTS Device Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Wind Generator Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Wind Electrical Control Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Wind Turbine Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Wind Pitch Control Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Switched Shunt Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
CONEC and CONET Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
User-Written Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Machine Related Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12
Load-Related Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Line Relay Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Auxiliary Signal Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
DC Line Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
FACTS Device Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Wind Machine Related Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Switched Shunt Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
Other CONEC Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
CONET Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
14.1.2 Operation of Activity DYRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-15
14.1.3 Adding Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-18
14.1.4 Subsystem Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-19
14.1.5 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-20
14.1.6 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-22
14.2 Assigning Simulation Variables to Output Channels . . . . . . . . . . . . . . . . . . . . . . . .14-28
Activity CHAN
14.2.1 Operation of Activity CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-28
14.2.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-31
14.2.3 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-33
PSS
E 32.0
Table of Contents Program Operation Manual
xxvi Siemens Energy, Inc., Power Technologies International
14.3 Saving Dynamics Working Memory in a Binary File . . . . . . . . . . . . . . . . . . . . . . . . 14-34
Activity SNAP
14.3.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-34
14.4 Restoring Dynamics Working Memory from a Binary Snapshot File . . . . . . . . . . . 14-36
Activity RSTR
14.4.1 Restarting From a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-37
14.4.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-38
14.5 Restoring Dynamics Working Memory from a Snapshot File Created in
PSS
E 32.0
Program Operation Manual Table of Contents
14.13 Initializing Turbine Governor Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-65
Activity GSTR
14.13.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-66
14.14 Performing Governor Response Simulation in Time Steps . . . . . . . . . . . . . . . . . . .14-67
Activity GRUN
14.14.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-68
14.15 Building a State Variable Matrix for Linear Dynamic Analysis (LSYSAN) . . . . . . . .14-70
Activity ASTR
14.15.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-74
14.16 Listing Dynamics Model Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-75
Activity DOCU
14.16.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-77
14.17 Listing Dynamics Data Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-79
Activity DLST
14.18 Creating a Dynamics Model Raw Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-81
Activity DYDA
14.18.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-82
14.19 Dumping Dynamic Simulation Output Channels into a Response File . . . . . . . . . .14-85
Activity DMPC
14.20 Creating Dynamic Data Records for Use by Other Activities . . . . . . . . . . . . . . . . .14-87
Activity RWDY
14.20.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-88
14.21 Listing Dynamics Model Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-89
Activity MLST
14.22 Initializing Models for Extended Term Simulation . . . . . . . . . . . . . . . . . . . . . . . . . .14-91
Activity MSTR
14.22.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-95
14.23 Performing Extended Term Simulation in Time Steps . . . . . . . . . . . . . . . . . . . . . .14-97
Activity MRUN
14.23.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-98
14.24 Changing Dynamics Model Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-101
Activity CCON
14.24.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-101
14.25 Assigning Subsystem Simulation Data to Output Channels . . . . . . . . . . . . . . . . .14-103
Activity CHSB
14.25.1 Operation of Activity CHSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-103
14.25.2 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-105
14.25.3 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-107
PSS
E 32.0
Table of Contents Program Operation Manual
xxviii Siemens Energy, Inc., Power Technologies International
Chapter 15 - Program Automation
15.1 What is Program Automation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
15.2 Controlling PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
15.4 Python Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
15.4.1 PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
15.9.1 Start-up Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
15.10 Running a Python Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15
15.11 Line Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
15.11.1 Mixing Line Mode and Batch Commands . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
15.11.2 Immediate Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
15.11.3 Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-17
15.12 Running a Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18
15.12.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18
15.13 Recording User Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20
Activity ECHO
15.13.1 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-21
15.14 Building a Response File, Power Flow Calculation . . . . . . . . . . . . . . . . . . . . . . . . 15-22
Activity PSEB
15.14.1 PSS
E 32.0
Program Operation Manual Table of Contents
15.16 Launching an IPLAN Program File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-45
Activity EXEC
15.16.1 IPLAN Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-45
15.16.2 Interaction With PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-46
15.16.3 The IPLAN Stand-Alone Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-46
15.16.4 Operation of Activity EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-46
Chapter 16 - Result Retrieval
16.1 Python Modules for Result Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-1
16.2 pssarrays.accc_summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-2
16.2.1 CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-2
16.2.2 Automation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-3
16.3 pssarrays.accc_solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-4
16.4 pssarrays.accc_violations_report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-7
16.5 pssexcel.accc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-8
16.6 pssexcel.pv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-9
16.7 excelpy Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-10
16.7.1 Export QV Solution to Excel Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . .16-10
16.7.2 Write Data to Excel Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-13
Chapter 17 - Miscellaneous Activity Descriptions
17.1 Terminating PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-2
Activity STOP
17.2 Applying a User-Written Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-3
Activity USER
17.3 Displaying Help Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-4
Activity HELP
17.4 Selecting Prompt Output Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-5
Activity ODEV
17.5 Selecting Alert Output Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-6
Activity ODEV
17.6 Selecting Progress Output Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-7
Activity PDEV
17.7 Selecting Report Output Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-8
Activity OPEN
17.8 Closing Report Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-9
Activity CLOS
17.9 Setting the Path for Use with & Filenames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-10
Activity PATH
PSS
E 32.0
Table of Contents Program Operation Manual
xxx Siemens Energy, Inc., Power Technologies International
17.10 Changing PSS
E 32.0
Program Operation Manual Table of Contents
18.7 Running a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-25
18.7.1 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-25
18.7.2 Applying Disturbances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-25
18.7.3 Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-27
18.7.4 Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-28
18.8 Procedural Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-29
18.8.1 The Executable Run File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-29
18.8.2 The Converted Saved Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-29
18.8.3 Initial Model Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-30
18.8.4 Retrieving System Model Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-30
18.8.5 Selecting Output Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-31
18.8.6 Running a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-31
18.8.7 Modifying the Network Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-31
18.8.8 Modifying the Dynamic Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-32
18.8.9 A Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-33
18.9 Advanced Uses of CONEC and CONET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-34
18.9.1 Manual Model Addition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-34
18.9.2 Accessing Machine and Load Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-37
18.9.3 Getting Bus Sequence Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-38
18.9.4 Run Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-40
18.10 Extended Term Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-41
18.11 Creating and Viewing the Results of Dynamic Simulations . . . . . . . . . . . . . . . . . . .18-43
18.11.1 General Workflow to View Dynamic Results . . . . . . . . . . . . . . . . . . . . . . .18-43
18.11.2 Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-43
Chapter 19 - Example Data Files
19.1 SAVNW Case Data Input Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-1
PSS
E 32.0
Table of Contents Program Operation Manual
xxxii Siemens Energy, Inc., Power Technologies International
Chapter 21 - Event Studies
21.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
21.1.1 Event Item Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
21.1.2 Event Study Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
21.1.3 Adding an Event Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
21.1.4 Running an Event Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4
Chapter 22 - Scenarios
22.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
22.1.1 General Workflow using Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
22.1.2 Scenario Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Appendix A - Activity Summary
Appendix B - PSSE Documentation
Appendix C - Legacy Activities
C.1 DRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C.2 GRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C.3 SCGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C.4 DRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C.4.1 Drawing Coordinate Data File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Header Record - HD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Terminator Record - EN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Voltage Level Record - VO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Bus Records - BU and BN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Branch Record - LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Transformer Record - TR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
Three-Winding Transformer Record - TT. . . . . . . . . . . . . . . . . . . . . C-9
Two-Terminal dc Transmission Line Record - DC . . . . . . . . . . . . . C-10
Multi-Terminal dc Transmission Line Record - MD . . . . . . . . . . . . C-11
Load Records - LO, LP, LC, and LY. . . . . . . . . . . . . . . . . . . . . . . . C-12
Shunt Record - SH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Generator Record - GE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Facts Device Record - FD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Straight Line Record - SL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Text Specification Record - TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
Clip Specification Record - CL . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
Grid Record - GR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-17
Color Specification Record - CO . . . . . . . . . . . . . . . . . . . . . . . . . . C-17
Symbol Record - SY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-18
Rating Specification Record - RA. . . . . . . . . . . . . . . . . . . . . . . . . . C-20
Voltage Limits Specification Record - VL . . . . . . . . . . . . . . . . . . . . C-20
Diagram Annotation Record - AN. . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Line Annotation Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Bus Annotation Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22
Equipment Annotation Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Activity Annotation Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Siemens Energy, Inc., Power Technologies International xxxiii
PSS
E 32.0
Program Operation Manual Table of Contents
Transformer Annotation Record . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Summation Block Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-24
C.5 BMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25
C.6 WORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25
C.7 XLIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25
C.7.1 Equipment Status Changes and the Spreadsheet View . . . . . . . . . . . . . . C-26
PSS
E 32.0
Table of Contents Program Operation Manual
xxxiv Siemens Energy, Inc., Power Technologies International
List of Figures
Siemens Energy, Inc., Power Technologies International xxxiii
Figure 3-1. Specifying the -buses Option in the PSSE-32 Command Prompt Window . . . .3-3
Figure 5-1. Power Flow Raw Data Input Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7
Figure 5-2. Constant Power Load Characteristic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11
Figure 5-3. Constant Current Load Characteristic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12
Figure 5-4. Implicit GSU Configuration Specified as Part of the Generator . . . . . . . . . .5-16
Figure 5-5. Explicit GSU Configuration Specified Separately from the Generator . . . . .5-17
Figure 5-6. Multiple Generators at a Single Plant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-18
Figure 5-7. Data Set for the Multiple Generators in Figure 5-6 . . . . . . . . . . . . . . . . . . . . .5-18
Figure 5-8. Transmission Line Equivalent Pi Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19
Figure 5-9. Two and Three-winding Transformer Configurations Related to
Data Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23
Figure 5-10. Sample Data for Two-Winding Transformer . . . . . . . . . . . . . . . . . . . . . . . . . .5-33
Figure 5-11. Sample Data for Three-Winding Transformer . . . . . . . . . . . . . . . . . . . . . . . . .5-34
Figure 5-12. Overlapping Areas and Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-35
Figure 5-13. Typical Impedance Correction Factor Curve . . . . . . . . . . . . . . . . . . . . . . . . . .5-44
Figure 5-14. Multi-Terminal DC Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-49
Figure 5-15. FACTS Control Device Setpoints and Limits . . . . . . . . . . . . . . . . . . . . . . . . . .5-57
Figure 5-16. Example Data Record for Combination of Switched Shunts . . . . . . . . . . . . . .5-62
Figure 5-17. Sequence Data Input Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-74
Figure 5-18. Two-Winding Transformer Zero Sequence Connections . . . . . . . . . . . . . . . . .5-85
Figure 5-19. Three-Winding Transformer Zero Sequence Connections . . . . . . . . . . . . . . .5-87
Figure 5-20. Pre-Scaling Load, Generation, Losses and Swing Bus Output . . . . . . . . . . .5-113
Figure 5-21. Post-Scaling Load, Generation, Losses and Swing Bus Output . . . . . . . . . .5-113
Figure 5-22. Bus Disconnect Progress Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-115
Figure 5-23. Purging the Branches Data Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-122
Figure 5-24. Join Buses Summary Report on Relocation of Load . . . . . . . . . . . . . . . . . . .5-126
Figure 5-25. Output Report Summary for Bus Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-128
Figure 5-26. Output Summary of Line Tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-131
Figure 5-27. Branch Move Output Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-136
Figure 5-28. Area and Inter-Area Interchange Information . . . . . . . . . . . . . . . . . . . . . . . .5-141
Figure 5-29. Example Output Report of Area Reassignment . . . . . . . . . . . . . . . . . . . . . . .5-141
Figure 5-30. Modified Area and Inter-Area Information following Reassignment . . . . . . . .5-142
Figure 5-31. Example Output Report of Owner Reassignment . . . . . . . . . . . . . . . . . . . . .5-144
Figure 5-32. Results of Example Transformer Flow Band Check . . . . . . . . . . . . . . . . . . .5-164
Figure 5-33. Incremental Heat Rate Curves Provided in the PSS
E 32.0
List of Figures Program Operation Manual
xxxiv Siemens Energy, Inc., Power Technologies International
Figure 5-35. Summary Results of the Economic Dispatch Process . . . . . . . . . . . . . . . . . 5-173
Figure 5-36. Before and After Machine Terminal Conditions for Economic Dispatch
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-174
Figure 5-37. Assignments for Supplementary Machine Economic Dispatch . . . . . . . . . . 5-175
Figure 5-38. Example Output of Activity SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-183
Figure 5-39. Example Output of Activity BUSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-184
Figure 5-40. Case Summary for the savnw.sav Saved Case File . . . . . . . . . . . . . . . . . . . 5-189
Figure 5-41. Packing Bus Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-218
Figure 5-42. Progress Output Indicating Number of Buses Modified . . . . . . . . . . . . . . . . 5-218
Figure 5-43. Result of Block Renumbering by Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-219
Figure 6-1. Constant MVA Load Characteristic (Top) and Resultant Form of
Current/Voltage Curve (Bottom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Figure 6-2. Constant Power Load Characteristic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Figure 6-3. Constant Current Load Characteristic (Top) and Resultant Form of
Load MVA/Voltage Curve (Bottom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Figure 6-4. Standard PSS
E 32.0
Program Operation Manual List of Figures
Figure 6-29. Outline of Evaluation Procedure Using AC Power Flows for a
Single Contingency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-125
Figure 6-30. Contingency List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-133
Figure 6-31. Wind Chime Approach for 2 Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-135
Figure 6-32. Process of Probabilistic Reliability Assessment . . . . . . . . . . . . . . . . . . . . . .6-148
Figure 6-33. System Reliability Indices Summary in Post-Contingency Mode . . . . . . . . .6-155
Figure 6-34. System Reliability Indices Summary in Post-Corrective Action Mode . . . . . .6-155
Figure 6-35. System Load Curtailment Probabilistic Indices . . . . . . . . . . . . . . . . . . . . . . .6-156
Figure 6-36. Branch Flow Overloading Probabilistic Indices . . . . . . . . . . . . . . . . . . . . . . .6-156
Figure 6-37. Branch Flow Overloading Probabilistic Indices . . . . . . . . . . . . . . . . . . . . . . .6-157
Figure 6-38. Three-State Component Fault Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-163
Figure 6-39. Time Line Illustrating the Steps in a Fault Simulation . . . . . . . . . . . . . . . . . .6-163
Figure 6-40. Two-State Model for Scheduled and Unscheduled Outage . . . . . . . . . . . . . .6-164
Figure 6-41. Example of Outage Statistics Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-165
Figure 6-42. Process to Assess a Failure Mode of a Component in SRA . . . . . . . . . . . . .6-166
Figure 6-43. Sample Substation Component Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-168
Figure 6-44. Sample Contingency Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-170
Figure 6-45. Sample Descriptions of the Contingencies in the Summary Report . . . . . . .6-172
Figure 6-46. Sample Bus Load Curtailment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-174
Figure 6-47. Sample of Substation Load Curtailment Report . . . . . . . . . . . . . . . . . . . . . .6-175
Figure 6-48. Two Terminals Simple Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-187
Figure 6-49. PV Curves Voltage and Incremental Power Transfer Characteristics . . . . . .6-188
Figure 6-50. PV Curves Voltage and Incremental Power Transfer Characteristics
for Bus 203 under Different Network Conditions . . . . . . . . . . . . . . . . . . . . . .6-190
Figure 6-51. PV Curves Voltage and Incremental Power Transfer Characteristics
for Different Buses in Base Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-191
Figure 6-52. Generator Output Versus Power Transfer Curves . . . . . . . . . . . . . . . . . . . . .6-192
Figure 6-53. QV Curves for a Range of System Loading . . . . . . . . . . . . . . . . . . . . . . . . . .6-193
Figure 6-54. QV Curves and Characteristics of a Capacitor Bank Required at
Stable Operating Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-194
Figure 6-55. Compensator Operations and Size on Voltage Stability using QV Curves . .6-195
Figure 6-56. QV Curves under Various Contingencies for Bus 103 . . . . . . . . . . . . . . . . . .6-196
Figure 6-57. QV Curve in Base Case with Increase in Load on Bus 103 . . . . . . . . . . . . .6-198
Figure 6-58. S-Shaped QV Curve on Bus 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-200
Figure 6-59. QV Curves for Different Load Type with Consideration of LTC . . . . . . . . . . .6-201
Figure 7-1. Example Report Listing Distribution Factors . . . . . . . . . . . . . . . . . . . . . . . . . .7-23
Figure 7-2. Application of Line Outage Distribution Factor . . . . . . . . . . . . . . . . . . . . . . . .7-25
Figure 7-3. Typical Contingency Description File from the Contingency Ranking
Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-32
Figure 7-4. Output from Activity DCLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-37
Figure 7-5. Sample Output Listing for activity DCLF Including Change Case . . . . . . . . . .7-39
Figure 7-6. Summary Contingency Report from the DC Contingency Checking Process .7-46
Figure 7-7. Loading Report from the DC Contingency Checking Process . . . . . . . . . . . . .7-48
PSS
E 32.0
List of Figures Program Operation Manual
xxxvi Siemens Energy, Inc., Power Technologies International
Figure 7-8. Sample Output of DC Corrective Action Analysis . . . . . . . . . . . . . . . . . . . . . . 7-53
Figure 7-9. Linear Projection Technique Used in Transfer Limit Analysis . . . . . . . . . . . . 7-56
Figure 7-10. Study System (A) and Opposing System (C). Area B Potentially Limiting . . . 7-57
Figure 7-11. Subsystem file and Power Flow Condition for Transfer Analysis . . . . . . . . . . 7-61
Figure 7-12. Base Case Results for Two Area Transfer Limit Calculation . . . . . . . . . . . . . 7-64
Figure 7-13. Partial Listing of Report for Two Area Transfer Limits for Contingency Cases 7-67
Figure 7-14. Participation Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
Figure 7-15. Sequential Participation Interchange Limit Output for Base Case . . . . . . . . . 7-79
Figure 7-16. Typical Output from Interchange Calculation for Two Opposing System . . . . 7-90
Figure 7-17. Graphical Output from Calculation of Interchange Limit with Two Opposing
Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-92
Figure 8-1. Separation of Complete Network into Study System and External Systems
by Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Figure 8-2. Components of the WORLD Area in the savnw.sav Power Flow Case . . . . . 8-11
Figure 8-3. Pre-Equivalence Power Flow Diagram for the WORLD Area . . . . . . . . . . . . . 8-12
Figure 8-4. Reduced Components of the WORLD Area after Building an
Electrical Equivalent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Figure 8-5. Redrawn One-Line Diagram to Match Topology after Building an
Electrical Equivalent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Figure 8-6. Generation and Load in Power Flow Case savnw.sav . . . . . . . . . . . . . . . . . . 8-18
Figure 8-7. Result of Netting Generation in the LIGHTCO Area . . . . . . . . . . . . . . . . . . . . 8-18
Figure 8-8. Result of Radial Equivalencing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
Figure 8-9. Pictorial Image of Power Flow Case with Equivalenced Sequence Networks 8-32
Figure 8-10. Form of Sequence Equivalents Built the Short-Circuit Equivalencing
Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
Figure 8-11. Pre-Equivalence Power Flow One-Line Diagram Showing the FLAPCO
Area Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
Figure 8-12. Equivalent FLAPCO Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
Figure 9-1. Data Stream for Sequence Data Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Figure 9-2. Mutual Coupling Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Figure 9-3. Mutual Coupling Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Figure 9-4. Two-Winding Transformer Connection Codes . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Figure 9-5. Three-Winding Transformer Connection Codes . . . . . . . . . . . . . . . . . . . . . . . 9-15
Figure 9-6. Representation of a Wye-Delta Transformer With and Without Its
30 Phase Shift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Figure 9-7. Effect of Including and Neglecting 30 Phase Shift in Transformer with
One Grounded and One Ungrounded Winding . . . . . . . . . . . . . . . . . . . . . . . 9-20
Figure 9-8. Generator Modeling in Fault Analysis Database . . . . . . . . . . . . . . . . . . . . . . 9-23
Figure 9-9. Output when Appending Sequence Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Figure 9-10. Using L-G and L-L-G Fault Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
Figure 9-11. Phase Closed Series Unbalances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
Figure 9-12. Allocation of Dummy Buses for In-Line Slider Faults . . . . . . . . . . . . . . . . . . . 9-31
Figure 9-13. Unbalances Modeled in Activity SCMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
Siemens Energy, Inc., Power Technologies International xxxvii
PSS
E 32.0
Program Operation Manual List of Figures
Figure 9-14. Generator Conversion to Norton Equivalent for Fault Calculations . . . . . . . . .9-42
Figure 9-15. Summary from Network Ordering Prior to Fault Calculations . . . . . . . . . . . . .9-42
Figure 9-16. Sequence Thevenin Impedance for Two Line-to-Ground Faults . . . . . . . . . . .9-45
Figure 9-17. Summary Output at Bus 151 with L-G Faults at Buses 151 in
Power Flow Case savnw.sav . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-48
Figure 9-18. Lead Current Flowing Into and Out of a Wye-Delta Transformer . . . . . . . . . .9-50
Figure 9-19. Transformer Zero-Sequence Currents Appearing in Alternative Network
Representations of the Transformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-52
Figure 9-20. Assignment of Zero-Sequence Shunt Branch for Typical Tapped Delta-Wye
Transformers, Solidly Grounded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-53
Figure 9-21. Two-Phase System Configuration for Railway Application . . . . . . . . . . . . . . .9-54
Figure 9-22. Behavior of Transformer with Secondary Windings Parallel to
Single-Phase Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-56
Figure 9-23. Sequence Connections Corresponding to Figure 9-22 . . . . . . . . . . . . . . . . . .9-57
Figure 9-24. Sequence Circuits for Loads on Two-Phase System . . . . . . . . . . . . . . . . . . .9-59
Figure 9-25. Sample System for Two-Phase Example Calculations . . . . . . . . . . . . . . . . . .9-60
Figure 9-26. Raw Data Files for Two-Phase System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-61
Figure 9-27. Data Listings for Two-Phase System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-63
Figure 9-28. Initial Condition Power Flow Solution for Two-Phase Sample System . . . . . .9-65
Figure 9-29. Output from Short-Circuit Solution Reporting Corresponding to Figure 9-27 .9-66
Figure 9-30. Simple L-G Fault at Bus 300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-68
Figure 9-31. Simple Ground Connection at Bus 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-69
Figure 9-32. Secondary System Grounded at Buses 330 and 550 . . . . . . . . . . . . . . . . . . .9-70
Figure 9-33. Current Flows (per unit) from Figure 9-32 . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-71
Figure 9-34. Home Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-78
Figure 9-35. Faults at Home Bus for Each Outgoing Line . . . . . . . . . . . . . . . . . . . . . . . . . .9-79
Figure 9-36. Home Bus and Open Line End Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-80
Figure 9-37. Clarification of Home Bus and < n > Levels Away . . . . . . . . . . . . . . . . . . . . . .9-81
Figure 9-38. Location of Bus 151 and Buses One Level Away in savnw.sav . . . . . . . . . . .9-86
Figure 9-39. Report Output at the Home Bus ( 0 level) for a 3-Phase Fault . . . . . . . . . . . .9-88
Figure 9-40. Current Flows 1 Level Away from Home Bus 151 for Three-Phase Fault . . . .9-89
Figure 9-41. Fault Summary Report with 3-Phase Fault on Bus 151 . . . . . . . . . . . . . . . . . .9-90
Figure 9-42. Results for Three-Phase and Single Phase fault at bus 151 . . . . . . . . . . . . . .9-91
Figure 9-43. Summary and Detailed Report of ANSI Fault Calculation . . . . . . . . . . . . . . . .9-99
Figure 9-44. Transient Phase Currents in Suddenly Applied Short Circuit . . . . . . . . . . . .9-113
Figure 9-45. Forms of Expression of Fault Current at Instant of Circuit Breaker Opening .9-114
Figure 9-46. Relationships Between Machine Time Constants in Radial System . . . . . . .9-118
Figure 9-47. Relationship of Outputs to Offset Fault Current Wave (amps) . . . . . . . . . . .9-123
Figure 9-48. Examples of Unbalanced Network Conditions Requiring a PI Equivalent . . .9-126
Figure 9-49. Output Report for pi-Equivalent shown in Figure 9-50 . . . . . . . . . . . . . . . . . .9-129
Figure 9-50. Diagram of pi-Equivalent and the Branch Power Flow Data . . . . . . . . . . . . .9-130
Figure 10-1. Example Output From Activity POUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7
Figure 10-2. Power Flow Output for Branches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-10
PSS
E 32.0
List of Figures Program Operation Manual
xxxviii Siemens Energy, Inc., Power Technologies International
Figure 10-3. Wide Format Power Flow Output including Branch Currents . . . . . . . . . . . . 10-12
Figure 10-4. Example Output From Activity LOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Figure 10-5. Example Output From Activity LAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Figure 10-6. Example of Load Reduction Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
Figure 10-7. Area Total Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Figure 10-8. Owner Totals Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37
Figure 10-9. Zone Totals Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41
Figure 10-10. Inter-Area Flows by Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-44
Figure 10-11. Inter-Zone Flows by Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46
Figure 10-12. Inter-Area Tie Line Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-48
Figure 10-13. Inter-Zone Tie Line Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-50
Figure 10-14. Report for Branch Loadings, All Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-54
Figure 10-15. Report on Transformer Overloads Based on 80% of RATE A . . . . . . . . . . . 10-57
Figure 10-16. Report on Transmission Line Overloads . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-60
Figure 10-17. Output Format for Branch Overloads Based on 80% of Rate A . . . . . . . . . . 10-63
Figure 10-18. Report for Voltages Out-of-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-65
Figure 10-19. Capability Curve Example for savnw.sav Case . . . . . . . . . . . . . . . . . . . . . . 10-68
Figure 10-20. Report Output for Reactive Power Checking with Capability Curve . . . . . . . 10-70
Figure 10-21. Generator Bus Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-74
Figure 10-22. Report Tabulation for Machine Terminal Conditions in savnw.sav File . . . . 10-77
Figure 10-23. Assumed Capability Curve of Activity GEOL . . . . . . . . . . . . . . . . . . . . . . . . 10-78
Figure 10-24. Regulated Bus Report from the Savnw.sav Power Flow Case . . . . . . . . . . . 10-82
Figure 10-25. Controlling Transformers Report for savnw.sav Power Flow Case . . . . . . . 10-85
Figure 10-26. Result of the Compare Case Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-87
Figure 10-27. Plotting Device Popup Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-106
Figure 10-28. STANDARD Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-113
Figure 10-29. LOWERCASE Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-114
Figure 10-30. ASCC Fault Analysis Annotation Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-124
Figure 10-31. Fault Analysis Annotation Dialog, Total Fault Currents . . . . . . . . . . . . . . . 10-125
Figure 10-32. Slider Diagram, Total Fault Currents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-126
Figure 10-33. Fault Analysis Annotation Dialog, Contributions at Home Bus . . . . . . . . . . 10-127
Figure 10-34. Slider Diagram, Fault Current Contributions at Home Bus . . . . . . . . . . . . . 10-128
Figure 10-35. Fault Analysis Annotation Dialog, Selected Fault . . . . . . . . . . . . . . . . . . . . 10-129
Figure 10-36. Slider Diagram, Fault Currents for a Selected Fault . . . . . . . . . . . . . . . . . . 10-130
Figure 10-37. Fault Analysis Annotation Dialog, Line Outage Fault . . . . . . . . . . . . . . . . . 10-131
Figure 10-38. Slider Diagram, Line Outage Fault Currents . . . . . . . . . . . . . . . . . . . . . . . . 10-132
Figure 10-39. Fault Analysis Annotation Dialog, Three Winding Transformer Winding
Outage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-133
Figure 10-40. Slider Diagram, Three Winding Transformer Winding Outage
Fault Currents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-134
Figure 10-41. Fault Analysis Annotation Dialog, Three Winding Transformer,
1st Line End Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-135
Siemens Energy, Inc., Power Technologies International xxxix
PSS
E 32.0
Program Operation Manual List of Figures
Figure 10-42. Slider Diagram, Three Winding Transformer, 1st Line End Fault Currents .10-136
Figure 10-43. Fault Analysis Annotation Dialog, Three Winding Transformer,
2nd Line End Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-137
Figure 10-44. Slider Diagram, Three Winding Transformer Winding,
2nd Line End Fault Currents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-138
Figure 10-45. Fault Analysis Annotation Dialog, Unbalanced Fault Currents . . . . . . . . . .10-139
Figure 10-46. Slider Diagram, Selected Fault, Unbalanced Fault Currents . . . . . . . . . . . .10-140
Figure 11-1. Time Regimes Considered in Power System Simulations . . . . . . . . . . . . . . . .11-2
Figure 11-2. Standard Power Flow Model and Norton Equivalent Used for Switching
and Dynamic Studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3
Figure 11-3. Switching Analysis Sequence of Processes . . . . . . . . . . . . . . . . . . . . . . . . .11-6
Figure 11-4. Relationship Between PSS
E 32.0
List of Figures Program Operation Manual
xl Siemens Energy, Inc., Power Technologies International
Figure 13-14. Polynomial Cost Equation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-57
Figure 15-1. Response File Recorded by PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Figure 15-2. Python File Recorded by PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Figure 18-1. Dynamic Simulation Basic Logic Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Figure 18-2. Branch Flow Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-36
Figure 18-3. Bus Frequency Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-38
Figure 18-4. Multiple Bus Frequency Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-39
Figure 19-1. SAVNW Power Flow Raw Data File savnw.raw (1 of 2 Sheets) . . . . . . . . . . . 19-3
Figure 19-2. SAVNW Sequence Data File savnw.seq . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Figure 19-3. SAVNW Slider Diagram File savnw.sld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Figure 19-4. SAVNW Breaker Duty Data File savnw.bkd . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Figure 19-5. SAVNW Dynamics Data File savnw.dyr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Figure 19-6. SAMPLE Power Flow Raw Data File sample.raw (1 of 4 Sheets) . . . . . . . . . 19-8
Figure 19-7. SAMPLE Sequence Data File sample.seq . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Figure 19-8. SAMPLE Slider File sample.sld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-13
Figure 20-1. Simple Excitation System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-11
Figure 20-2. Basic DEMOEX Model Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
Figure 20-3. FLECS Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
Figure 20-4. Basic DEMOBL Model Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-26
Figure 22-1. Scenario XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Figure C-1. Graphics Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
List of Tables
Siemens Energy, Inc., Power Technologies International xli
Table 2-1. PSS
E Subdirectories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-14
Table 2-6. PSS
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
Table 6-2. Power Flow Iteration Acceleration Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
Table 6-3. Power Flow Convergence Tolerances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
Table 6-4. Available Automatic Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5
Table 6-5. Transformer Tap Adjustment Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6
Table 6-6. Power Flow Solution ActivitiesSelection Guide . . . . . . . . . . . . . . . . . . . . . . .6-9
Table 6-7. Inertial Power Flow Solution Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-69
Table 6-8. Deterministic Reliability Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-74
Table 6-9. AC Contingency Solution Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-80
Table 6-10. AC Contingency Solution with Generation Dispatch Options . . . . . . . . . . . . .6-82
Table 6-11. AC Contingency Single Run Report Options . . . . . . . . . . . . . . . . . . . . . . . . . .6-89
Table 6-12. AC Contingency Multiple Run Report Options . . . . . . . . . . . . . . . . . . . . . . . .6-105
Table 6-13. AC Corrective Action Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-115
Table 6-14. AC Corrective Action Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-116
Table 6-15. AC Corrective Action Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-120
Table 6-16. Weighting Functions and Factors of Controls . . . . . . . . . . . . . . . . . . . . . . . .6-122
Table 6-17. Multi-Level AC Contingency Solution Power Flow Control Options . . . . . . . .6-127
PSS
E 32.0
List of Tables Program Operation Manual
xlii Siemens Energy, Inc., Power Technologies International
Table 6-18. Multi-Level AC Contingency Solution Multiple Contingency Analysis
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-128
Table 6-19. Classification of Contingency Evaluation Based on Power Flow Solution . . 6-131
Table 6-20. Types of Problems Qualifying a Category I Contingency as a Failure . . . . . 6-131
Table 6-21. Groups within Contingency List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-132
Table 6-22. Multi-Level Contingency Solution Tripping Simulation Options . . . . . . . . . . 6-136
Table 6-23. Multi-Level Contingency Solution Corrective Actions Options . . . . . . . . . . . 6-142
Table 6-24. Running Modes for Multiple Contingency Analysis . . . . . . . . . . . . . . . . . . . . 6-145
Table 6-25. Probabilistic Reliability Assessment Options . . . . . . . . . . . . . . . . . . . . . . . . 6-148
Table 6-26. PV Analysis Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-177
Table 6-27. QV Analysis Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-184
Table 7-1. Contingency Ranking Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Table 7-2. Linearized Network Contingency Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Table 7-3. DC Corrective Actions Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
Table 7-4. Transmission Transfer Limit Analysis Options . . . . . . . . . . . . . . . . . . . . . . . . 7-57
Table 7-5. Sequential Participation Interchange Limits Options . . . . . . . . . . . . . . . . . . . 7-72
Table 7-6. Interchange Limits Analysis Options for Two Opposing Systems . . . . . . . . . 7-83
Table 8-1. Network Equivalence Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Table 8-2. Electrical Equivalencing of Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Table 8-3. Radial Bus Equivalencing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Table 8-4. Radial Bus Equivalencing Options, with Exception . . . . . . . . . . . . . . . . . . . . 8-26
Table 8-5. Net Boundary Bus Mismatch Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Table 8-6. Short Circuit Equivalent Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
Table 9-1. Automatic Sequenceing Short Circuit Calculation Options . . . . . . . . . . . . . . . 9-81
Table 9-2. ANSI Fault Current Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-96
Table 9-3. Short Circuit Calculation Options for IEC 60909 . . . . . . . . . . . . . . . . . . . . . . 9-106
Table 9-4. Breaker Duty Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-119
Table 9-5. Separate Pole Circuit Breaker Calculation Options . . . . . . . . . . . . . . . . . . . 9-127
Table 10-1. Summary of Available PSS
E 32.0
Program Operation Manual List of Tables
Table 12-2. Line Loading Relief Calculator Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-8
Table 13-1. Local Generator Voltage Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
Table 13-2. Optimal Power Flow (OPF) Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-68
Table 13-3. Optimal Power Flow (OPF) Parameters - General Options . . . . . . . . . . . . . .13-71
Table 13-4. Optimal Power Flow (OPF) Parameters - Tolerance Options . . . . . . . . . . . .13-73
Table 13-5. Optimal Power Flow (OPF) Parameters - Control Options . . . . . . . . . . . . . .13-76
Table 13-6. Optimal Power Flow (OPF) Parameters - Reporting Options . . . . . . . . . . . .13-77
Table 13-7. Problem Size Label Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-79
Table 13-8. Jacobian Column Label Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-83
Table 13-9. Jacobian Row Label Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-83
Table 13-10. Variable State Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-86
Table 13-11. Optimal Power Flow (OPF) Data Output Options . . . . . . . . . . . . . . . . . . . . .13-89
Table 14-1. Load-Related Model Subsystem Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-13
Table 14-2. Activity CHAN Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-29
Table 14-3. Dynamic Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-42
Table 14-4. PSS
E Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Table C-1. Options For Branch Coordinate Data Records . . . . . . . . . . . . . . . . . . . . . . . . C-7
Table C-2. Special Options for Open Ended Radial Lines . . . . . . . . . . . . . . . . . . . . . . . . C-8
PSS
E 32.0
List of Tables Program Operation Manual
xliv Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International P-1
Preface
The Siemens PTI Power System Simulator (PSS
E handles power flow, fault analysis (balanced and unbalanced), network equivalent
construction, and dynamic simulation.
PSS
E is bundled with a number of program sections that vary from user to user. The base config-
uration for all installations of PSS
E achieves its broad capabilities by a highly modular structure and, in dynamic simulation, by
encouraging the engineer to introduce user-written subroutines describing the problem of interest
whenever the standard calculation procedures are not appropriate. PSS
E is designed on the premise that the engineer can derive the greatest benefit from compu-
tational tools by retaining the most intimate control over their application. The interactive structure
of PSS
E, therefore, encourages the user to examine the results of each step in the computation
process before proceeding to the next. This assists the engineer in understanding the engineering
capabilities of these tools without having to become a master of the mathematical fine points of
computation. The execution of standard studies such as power flow and basic transient stability on
PSS
E 32.0
Contacting Siemens PTI for Support Program Operation Manual
P-2 Siemens Energy, Inc., Power Technologies International
system dynamics problem for which the requisite equipment models and input data can be
produced.
The standard maximum capacities of PSS
E
Program Capacities lists the dimensional capacities of the various PSS
E arrays at size
levels other than the four standard size levels and the interpolation, extrapolation, and rounding
down (the I/E or S column of Table 3-1) calculations made at non-standard bus size levels.
All PSS
E manuals and reference guides are in PDF format and readily available and viewable with
the Adobe Acrobat Reader (freely downloadable from the Adobe web site).
The PSS
E manuals and reference guides are located on the installation CD in the DOCS folder.
If the option to install documentation with PSS
E installation, a
shortcut to the PSS
E Start menu.
Chapters 1 through 4 of this manual describe the interface of PSS
E data input files. Chapter 20 documents the requirements of user-written dynamic models.
Chapter 21 describes the use of event studies in which the series of events (e.g., faults, switchings,
etc.) to be employed in a dynamics or power flow study are specified, and Chapter 22 describes the
use of scenarios to identify the set of data files to be used in a given study.
The PSS
E Program Operation Manual assumes throughout that the reader is familiar with the
content of the PSS
E Program Application Guide. This manual and all its references to the
PSS
E Program Application Guide apply only to the standard form of the PSS
E package.
Contacting Siemens PTI for Support
If after consulting the documentation and online help you find that additional assistance with PSS
E
is needed, you may contact Siemens PTI via any of the following methods (please send a thorough
description of the problem or question, including files):
Send an email to technical support at pti-psse-support.ptd@siemens.com.
Send a fax to (518) 346-2777, attention PSS
E Support.
Call the telephone support number between the hours of 8:00 a.m. and 5:00 p.m.
Eastern Time, Monday through Friday. Dial (518) 395-5075 and select option 1 for
PSS
E support.
Visit the Siemens PTI Web Site at www.siemens.com/power-technologies and the PSS
E
User Support Web Page.
Please note that access to the PSS
E
support is only available to those users whose companies have purchased or renewed their
PSS
E 32.0 Preface
Program Operation Manual Submitting Bug Reports and Feature Requests
Submitting Bug Reports and Feature Requests
Bug reports and feature requests shoul d be submi tted di rectl y to PSS
E support at
pti-psse-support.ptd@siemens.com. Please provide as much detail as possible. If submitting a
report for a potential bug please include the steps taken, along with pertinent data files and scripts
so that we may accurately reproduce the problem. If an issue does turn out to be a program bug,
one of the following priorities will be assigned to it:
High priority is given to issues that cause the program to crash or produce incorrect
results with no published work around.
Medium priority is given to issues that cause incorrect functionality, however the
problem can be remedied by a published work around.
Low priority is given to those issues that do not fall into the above categories, or are
purely cosmetic in nature.
Every effort is made to address high and medium issues in a PSS
E users.
If it does, it will likely be considered for implementation in a point release or major release of PSS
E.
If several users have the same feature request, the feature may sit higher in the queue than others
for implementation in PSS
E.
Document Conventions
The following conventions are used in PSS
E manuals:
Examples Description
Power Flow > Solution > Parameters Navigation path in a PSS
E GUI menu
[Solution Parameters] dialog Interactive dialog in Graphical User Interface (GUI)
[Spreadsheet]
[Diagram]
Interface windows and views
SOLV,OPT
LIST
User entry the line mode in the Command Line Interface
(CLI) dialog
[F10], [Enter] Keys found on a standard computer keyboard
[OK], [ ], [Close] Action buttons available on a dialog
GUI toolbar button that starts an activity sequence
Set tap ratios to Unity Activity option
Print outaged branches Program option
GENERATOR CONVERSION COMPLETED Message sent to Progress tab
<quantity>, <bus number> Variable in message sent to Progress tab
ENTER OUTPUT DEVICE CODE: Line mode dialog request/response
Progress tab, Report tab Activity results displayed in [Output] view
Preface PSS
E 32.0
Document Conventions Program Operation Manual
P-4 Siemens Energy, Inc., Power Technologies International
OPEN PSS
E manual reference
Indicates additional information of interest.
Indicates important information.
n.a. Abbreviation meaning "not applicable".
Examples Description
Siemens Energy, Inc., Power Technologies International 1-1
Chapter 1
Overview
1.1 PSS
E Functional Description
PSS
E is an integrated set of computer programs that handles the following power system analysis
calculations:
Power flow and related network analysis functions.
Balanced and unbalanced fault analysis.
Network equivalent construction.
Dynamic simulation.
PSS
E is structured around its own array address space (called the working case) along with a
carefully designed set of temporary data files (called the temporary files). These data structures
are set up in a way that optimizes the computational aspects of the key power system simulation
functions: network solution and equipment dynamic modeling. The working case and/or one or
more of the temporary files are operated upon by a comprehensive set of functional program
modules called activities. Each activity performs a distinct computational, input, output, or data
manipulation function needed in the course of power flow, short circuit, equivalent construction, or
dynamic simulation work.
PSS
E is entered by starting its master program module (see Section 3.2: Starting PSS
E). The
master module immediately invites the user to select an activity. The selected activity is immediately
executed, performing its processing operation on the working case and/or one or more of the
temporary files. The activity retains control until either:
Its processing is successfully completed.
Its processing encounters an error condition.
It is interrupted and terminated by the user.
Each of these conditions returns control back to the master module, leaving the working case and
the temporary files such that they reflect the results of the processing by this activity. The master
module again invites the user to select another activity. Any activity may be selected at any time,
but the determination of which activities are meaningful must be made by the user on the basis of
the recent sequencing of activities and the present condition of the working case and the temporary
files.
Complementing the working case and the set of temporary files, each user will generate a library of
power flow Saved Cases and dynamic simulation Snapshots. These, in conjunction with the
temporary files, form a working database. The PSS
E 32.0
PSS
E auxiliary programs.
1.2 PSS
E Operations
The use of PSS
E requires several types of operation on its host computer. Among these are:
Creating and filling files to be used as input files to PSS
E.
Compiling and linking the connection subroutines, CONEC and CONET, and any user-
written dynamic simulation equipment models into the main body of PSS
E.
Running the PSS
E programs.
Running the auxiliary programs.
The first two of these operations require the use of commands and functional programs of the host
computers operating system. The user of PSS
E user needs only a very minimal knowledge of computer system protocol in order to
make productive use of the PSS
Es output messages.
1.3 Extending PSS
E advanced features involving user-written code are implemented through the use of user-
written dynamically linked libraries, or DLLs. When the user starts PSS
E will automat-
ically find it and load it. For example, say you build a DSUSR.DLL in C:\WORKING\ONE. If you
start PSS
E with C:\WORKING\ONE set as your working directory, your custom DSUSR.DLL will
be loaded. If, on the other hand, you start start PSS
E 32.0 Overview
Program Operation Manual PSS
E, and always located first should a DLL with the same name be anywhere else
on the load search paths.
If your results are not what you expect, first make certain that you are loading the correct copies of
the DLL(s) you wish to use.
If you create a customized DLL for the use of PSS
E 32.0
PSS
E-32 Command Prompt. When the compilation is complete, you must execute CLOAD4 at
the PSS
E 32.0 Overview
Program Operation Manual PSS
E. You may edit these files to incorporate your own routines and, in
addition, you may include routines on the command line as with CLOAD4. CLIPLU will compile and
link these routines to create a new IPLUSR.DLL.
1.4.5 CLPSSUSR
CLPSSUSR enables the user to include a new activity in PSS
E) and then running CLPSSUSR, you can compile and link your
new activity into a new PSSUSR.DLL. Starting PSS
E 32.0
PSS
E programs and the file system in sufficient detail to allow the engineer to effectively
perform studies using PSS
E (or any other program), the user must have a path to a directory or folder. A
directory may be viewed as a catalog of files that are somehow related (e.g., they apply to a specific
study). A directory may contain an unlimited number of files and subdirectories. PSS
E always
operates out of a working directory. By default this is the EXAMPLE subdirectory in the main PSS
E
directory.
It is perfectly reasonable, for example, to set up one directory for running the PSS
E programs (a
working directory) and another for the storage of base case power flow and dynamics data files.
Various other working directories may also be established in which to run PSS
E on a variety of
different studies or investigations, each with its own set of data files (see Section 2.7.1, Multiple
Working Directories).
The files containing input data for PSS
E then searches the users home directory and, if the file is not found there, it looks in the
appropriate subdirectory of the PSS
E 32.0
The PSS
Es address space contains a complete set of power flow data. The content
of these arrays is referred to throughout this manual as the working case. The working case is modi-
fied by the power flow activities and is always a valid working case even though its voltages may
not represent a solution of Kirchhoffs laws.
Several PSS
E activities create and access one or more temporary files that are used strictly as
scratch files; each such file is deleted by the activity that created it prior to its termination. The user
of PSS
E does not need to be concerned with names and contents of these files.
There are, however, three temporary files that are often used to preserve the results of certain activ-
ities for subsequent use by other activities. Contents of the files are variable depending upon the
recent sequencing and context of activity executions. The user of PSS
E is used. The names and general functions of these temporary files are:
When temporary files are created, < nnn > is set to a three-digit integer such that the filename is
unique in the directory in which it is created. See also Section 2.7.4, Temporary Files.
2.3 File Classes
The user of PSS
E. PSS
E takes
full advantage of the file management capabilities of the host operating system. This allows PSS
E
to be used at all times without the need to select file assignments before it is started up. As a result,
the user has a great degree of flexibility in the use of files during an interactive problem-solving
session with PSS
E.
YMATnnn Created by the triangular factorization activity FACT, and used by the
triangularized Y matrix network solution activity TYSL, and the dynamic
simulation activities. It is also used as a scratch file by the Newton-
Raphson based power flow solution activities and the circuit breaker
duty analysis activity BKDY.
SEQDnnn Created by the sequence network setup activity SEQD, and used by
the multiply unbalanced network solution activity SCMU, and the sepa-
rate pole circuit breaker duty activity SPCB. It is also used as a scratch
file by the automatic sequencing short circuit calculation activity ASCC,
by the ANSI and IECS fault current calculation activities, and by the
three sequence equivalencing activity SCEQ.
SCMUnnn Created by the multiply unbalanced network solution activity SCMU,
and used by the unbalanced network solution output activity SCOP,
and by the short circuit data retrieval routines SCINIT, SC3WND,
SCBRN2, SCBUS2 and SCMAC2 described in PSS
E Application
Programming Interface (API).
Siemens Energy, Inc., Power Technologies International 2-3
PSS
E activities; and batch and program control files used for directing the
execution of PSS
E.
2. Files created by PSS
E These include: files generated when the users working case and
dynamics working memory are preserved; and output and results files that are either
requested by the user or automatically generated.
The classes of files used by PSS
E and OPF Options Files, the user may assign any name to any file. The
maximum filename or pathname length that PSS
E File Classes
File Class Created By Type Accessible To
Input data files
User via text editor or auxiliary
program
Source PSS
E and user
Saved Case and Snapshot Files PSS
E Binary PSS
E
Output listing files PSS
E Source User
Channel Output Files PSS
E Binary PSS
E and PSSPLT
Response Files
User via text editor or PSS
E
activities ECHO, PSEB, and
PSAS
Source PSS
E and user
PSEB and PSAS Command Files User via text editor Source PSS
E and user
IPLAN Source Program Files User via text editor Source IPLAN compiler and user
IPLAN Executable Program Files IPLAN compiler Binary PSS
E
Python Program Files User via text editor Source PSS
E Binary PSS
E
Results files PSS
E
Source or
Binary
PSS
E and other
programs
Temporary files PSS
E
Source or
Binary
PSS
E
File System PSS
E 32.0
File Classes Program Operation Manual
2-4 Siemens Energy, Inc., Power Technologies International
2.3.1 Input Data Files
PSS
E must, from time to time, accept large volumes of data from external sources. Such large
volumes of data could be entered directly into the PSS
E before PSS
E to feed the data through the appropriate input activity into the PSS
E
working case.
Input data files may be obtained by reading from storage mediums (e.g., CDs) or e-mail attach-
ments from external sources (e.g., other computer installations), or by the typing and file editing
facilities of the host computer. In the case of power flow and dynamics data input, the input data
files may often be created by reading and reformatting data obtained from other computer installa-
tions. While they are not accessible from the PSS
E input format. Section 2.4.2, Specifying Filenames discusses the alternative methods of
creating input data files.
Table 2-2 defines the principal PSS
E, PLINC).
Inertia and Governor
Response Data Files
Machine inertia and governor response data for the generator redispatch used in the
inertial and governor response power flow activity INLF.
Drawing Coordinate
Data Files
Coordinates of busbars, line ends, generators, loads, etc. for the construction of a
one-line diagram via the obsolete activities DRAW, GDIF and SCGR.
Siemens Energy, Inc., Power Technologies International 2-5
PSS
E. When an initial working case has been built, the input data files should be
set aside and all data changes and small additions should be made directly on the working case
from the Spreadsheet View and the data modification activities such as CHNG, RDCH, SQCH,
ALTR, and CCON. Attempts to keep a large input data file up to date with an ongoing power system
study are usually both error prone and time consuming. PSS
E working memory by
activity REMM for use in Transmission Access studies by activities ALOC, IMPC,
and LLRF.
Bus Location Data
FIles
Bus location data that is used in creating or modifying a one-line diagram by Speci-
fying Bus Locations from a File.
Table 2-2. Summary of PSS
E 32.0
File Classes Program Operation Manual
2-6 Siemens Energy, Inc., Power Technologies International
described below, are far more efficient vehicles for maintaining the power flow and dynamic system
database of a study. Table 2-3 shows PSS
E activities always operate upon the working case, it is necessary to load the
required data into the working case before starting any sequence of simulation work. Even though
it is possible to load the working case on a routine basis by using activities such as READ, RESQ,
and DYRE to read input data files, this is discouraged because it would:
1. Be grossly inefficient because input data files are organized for people and must be reorga-
nized by the data input activities to match the computational data structure of PSS
E.
2. Require continuous updating of the input data files as interactive data changes are made in
PSS
E overcomes these problems by using Saved Case and Snapshot Files. These files are
binary images of the power flow working case and dynamics data memory, respectively. To
conserve disk space and minimize the time required to store and retrieve these files, Saved Cases
and Snapshots are compressed in the sense that they do not record unoccupied parts of the data
structure if the system model is smaller than the capacity limits of the program.
Saved Case and Snapshot Files are loaded with copies of these memory images by activities SAVE
and SNAP, respectively. Activities SAVE and SNAP require a filename at the time they are selected.
The user may create as many Saved Cases and Snapshots as desired. Each Saved Case is a
complete power flow description that may be returned to the working case as a new base case at
any time with activity CASE. Each Snapshot File records the exact instantaneous condition of all
dynamic simulation models at the time activity SNAP is executed. Returning a Snapshot to
dynamics working memory and its corresponding Saved Case to the power flow working case
allows an interrupted dynamic simulation run to be continued from the time point at which activity
SNAP was executed, just as if the run had not been stopped in the first place.
2.3.3 Output Listing Files
The majority of PSS
E
Activity
Wtitten by PSS
E
Activity
Power Flow Raw Data File READ RAWD
Machine Impedance Data File MCRE RWMA
Sequence Data File RESQ RWSQ
Dynamics Data File DYRE DYDA
Optimal Power Flow Raw Data File ROPF RWOP
Siemens Energy, Inc., Power Technologies International 2-7
PSS
E
master program module, and to the Channel Output File processing program, PSSPLT.
As with output listing files, it is advisable to minimize the number of Channel Output Files by copying
them to an off-line bulk storage medium if necessary for archival purposes and deleting or reusing
them as soon as the plotting of a simulation run has been completed.
2.3.5 Response Files
Response Files allow the PSS
E. A Response File for the performance of a given calculation contains either or both of the
following:
1. An exact image of the line mode activity command and all of its inputs just as they would be
entered by the user at the console in executing the activity through PSS
Es command line
interface (see Section 4.2.2, Command Line Interface).
2. The batch commands (BAT_), as described in PSS
E.
Constructing a Response File requires familiarity with details of the PSS
E GUI.
Terminal input, including line mode commands, can be recorded using activity ECHO in PSSECMD.
2.3.6 PSEB and PSAS Command Files
PSEB and PSAS Command Files allow the PSS
E 32.0
File Classes Program Operation Manual
2-8 Siemens Energy, Inc., Power Technologies International
files that the user creates with a text editor before starting up PSS
E run assembler activities, PSEB and PSAS, accept such commands, either from a data
input file or directly from the users terminal, and translate them into a PSS
E menu option I/O Control > Run Program Automation File. Python commands may
also be entered directly through PSS
E Options Files
When PSS
E activities
(e.g., the Distribution Factor Data File of activity DFAX for use by activity DCCC) or by other
programs (e.g., the Matrix Output File of activity ASTR for use by LSYSAN).
Similarly, several PSS
E
activities (e.g., the Bus Number Translation File of activity BSNM for use by activity RNFI) or by
other programs (e.g., the Relay Output File of activity ASCC for use by an external relay coordina-
tion program).
Siemens Energy, Inc., Power Technologies International 2-9
PSS
E Data Files
2.3.11 Temporary Files
Any temporary file that is preserved following the completion of the activity that created and filled it
(see Section 2.2, The PSS
E is terminated); and the user has no naming control over the temporary files.
2.4 PSS
E Data Files
2.4.1 File Usage
Before PSS
E can be started up, the user must create and fill those files needed for its input. Files
needed for PSS
E as needed. The
importance of planning and noting the contents of PSS
E
File Planning Sheet is suggested.
The definitions of the various input data files used by PSS
E File Plan-
ning Sheet and a sample of the data to be placed in the user-supplied files is given in Chapter 19
of this manual.
The types of data files used by PSS
E, the activities that use them, and the default extensions used
when specifying filenames are summarized in Table 2-4. Except as described below, whenever a
file type listed in Table 2-4 is being specified to PSS
E 32.0
PSS
E-26 or earlier.
Channel Output out Binary
For dynamics,
one is essen-
tial. More are
optional.
Plot page processing capability
of PSS
E and program
PSSPLT. Built by dynamic
simulation.
Power Flow Raw Data raw Source Optional
READ. Built by RAWD or
format conversion program.
Dynamics Data dyr Source Optional
DYRE. Built by DYDA or
format conversion program.
Machine Impedance Data rwm Source Optional
MCRE. Built by RWMA or
format conversion program.
Sequence Data seq Source Optional
RESQ. Built by RWSQ or
format conversion program.
Optimal Power Flow Raw Data rop Source Optional ROPF. Built by RWOP.
Bus Location Data loc Source Optional GUI one-line diagram.
Drawing Coordinate Data drw Source Optional
Obsolete one-line diagram
definition format file that may
be imported into the Diagram
View.
Graphical Report Data grp Source Optional GRPG.
GRED Library sgf Binary Optional GRPG.
Binary Graphical Report Definition
Data
grb Binary Optional GRPG.
Economic Dispatch Data ecd Source Optional ECDI.
Inertia and Governor Response
Data
inl Source Optional INLF. Built by RWDY.
Breaker Duty Data bkd Source Optional BKDY. Built by RWDY.
Fault Specification Data bkf Source Optional BKDY.
ANSI Fault Specification Data ans Source Optional ANSI.
Fault Control Data fcd Source Optional ASCC, yyy ASCC2 and IECS.
Relay Output rel Source Optional
Built by ASCC, yyy ASCC2
and IECS.
IEC Short Circuit Data iec Source Optional IECS.
Short Circuit Results sc Binary Optional
Slider diagram. Built by yyy
ASCC2 and IECS.
Bus Subsystem Selection Data sbs Source Optional
Recall function. Built by memo-
rize function of the bus
subsystem selector.
Event Study evs Binary Optional Event study functions.
Table 2-4. PSS
E Data Files
Subsystem Description Data sub Source Optional RANK and DFAX.
Monitored Element Data mon Source Optional RANK and DFAX.
Contingency Description Data con Source Optional DFAX. Built by RANK.
Distribution Factor Data dfx Binary Optional
OTDF, DCCC, TLTG, SPIL,
POLY, IMPC, LLRF, the
various ac contingency calcu-
lation functions (e.g., ACCC,
ac corrective actions, etc.), the
PV Analysis function, the QV
Analysis function, and the
Probabilistic Reliability Assess-
ment function and the
Substation Reliability Assess-
ment function. Built by DFAX.
Tripping Element Data trp Source Optional
Multi-level ac contingency
analysis.
Reliability Outage Statistics Data prb Source Optional
The probabilistic reliability
function and the substation
reliability function.
Load Throwover Data thr Source Optional
The various ac contingency
calculation functions, the PV
Analysis function, and the QV
Analysis function.
AC Contingency Solution Output acc Binary Optional
The various ac contingency
calculation reporting functions.
Built by the various ac contin-
gency calculation functions.
PV Solution Output pv Binary Optional
The various PV analysis
reporting functions. Built by PV
Analysis function.
QV Solution Output qv Binary Optional
The various QV analysis
reporting functions. Built by QV
Analysis function.
Subsystem Participation Data prt Source Optional SPIL.
POLY Results Output pol Binary Optional
POLY and POLY previous
results plotting. Built by POLY.
Machine Capability Curve gcp Source Optional GCAP.
Transactions Raw Data mwm Source Optional REMM. Built by RWMM.
Bus Renumbering Translation trn Source Optional
BSNM and RNFI. Built by
BSNM.
FLECS Output flx Source Optional Built by DYRE.
Compiling Command bat Source Optional Built by DYRE and SRRS.
Table 2-4. PSS
E 32.0
PSS
E attempting
to access the specified file in the users current directory; specifying the complete pathname of a
file allows the user access to other directories for which appropriate privileges are assigned. In addi-
tion, PSS
E files over which the user has no naming control are generally accessed from the current
directory or from some other system default directory (e.g., the Temp directory on Windows
systems). This includes files such as the PSS
E Working
Relay Characteristic Data rlc Source Optional
Dynamics channel output file
processing functions. Built by
RWDY.
Response idv Source Optional
. Built by ECHO, PSEB and
PSAS.
PSEB Command pse Source Optional PSEB.
PSAS Command psa Source Optional PSAS.
IPLAN Source Program ipl Source Optional IPLAN compiler.
IPLAN Executable Program irf Binary Optional
EXEC. Built by IPLAN
compiler.
Python Program py Source Optional
Run program automation file
function. Built by recording
function.
Conversion Program Log log Source Optional
Several data conversion
programs.
Matrix Output lsa Binary Optional
Program LSYSAN. Built by
ASTR.
Miscellaneous Output Data dat Source Optional
Built by various functions (e.g.,
RWCM,
OUTPUT_Y_MATRIX).
UCTE Data uct Source Optional
[Open...]. Build by UCTE Data
tab of [Save...].
PSS
E start-up. Built by
OPTN.
Optimal Power Flow Options OPT Binary Optional
PSS
E also looks to the users home directory and to its own master directories for PSS
E
Options Files, for output device parameter files, and for several other types of files if they are not
found in the users current directory; see Section 2.7.3, File Search Path Rules).
2.5 Creating Input Files
As is seen from Table 2-4, there are several source files that are designated as input files to various
PSS
E data files
are described in this manual in the descriptions of the activities that use them.
Input records may not exceed 256 characters.
2.5.1 Via a Text Editor
The primary tool for creating and preparing input data files for PSS
E which, though
not accessible from the PSS
E, Section 1.1,
Auxiliary Program Descriptions.
2.5.3 Via PSS
E
As shown in Table 2-4, several PSS
E input data files. Details on the applications of such activities are provided by individual
descriptions contained in this manual.
2.6 Files Created By PSS
E
Files into which PSS
E. The name of an output file is requested at the time the activity utilizing it is ready for it. If
the specified file does not already exist, it is created and used.
For the case in which the selected file already exists, the user may elect to have PSS
E operate in
either of two modes:
1. The specified file is utilized.
2. The user is informed that the file exists and is given the option of either specifying another
filename or using the designated file.
Generally, whenever an existing file is used for output, its previous contents are overwritten and
the file is lengthened or truncated as required.
File System PSS
E 32.0
File System Details Program Operation Manual
2-14 Siemens Energy, Inc., Power Technologies International
It is the responsibility of the user to ensure that files that are needed for future reference are
not overwritten.
2.7 File System Details
2.7.1 Multiple Working Directories
A simple way of setting up PSS
E Directory Organization
The PSS
E program is usually installed in your Program Files directory; the default installation
directory is C:\Program Files\PTI\PSSE32. However, PSS
E Master Directory consists of subdirectories that contain the files required for
executing PSS
E Subdirectories
Name Description
DEMOS Contains demos of Siemens PTI and third party software.
DOCS
Contains all PSS
E data files and batch files for building user versions of the PSS
E
programs.
IPLUSR User-written IPLAN files.
MODELDRW
Diagram elements for use with CCON (ONLY for installations where the lease
includes the PSS
E Dynamics section).
PSSBIN PSS
E executable files.
PSSHLP PSS
E programs use a variety of parameter and binary files from which to gather specific informa-
tion. Parameter files are standard text files that can be customized for either individual or system-
wide use. These files typically have the extensions .DAT or .PRM such as those for printers, plot-
ters, and the PSS
E programs from
previously developed input files or from specific user input.
PSS
E tries to locate parameter and binary files by sequentially checking three directories. The
three directories are checked in the following order:
Current Working Directory. When started via a shortcut, PSS
E uses
the current directory as the working directory. Refer to Section 2.1 for details on how the working
directory is used.
Home Directory. This directory may be specified (if desired) by setting the Home variable to a
directory path such as Home=C:\WORKDIR (set in PSSE31xx.INI). Setting this variable does not
change the program working directory (see above).
Default Master Directory. Table 2-6 outlines PSS
E Windows environment.
SRCMDL, SRCTBL
Source files used for Dynamics simulation models (ONLY for installations where the
lease includes this option.
SETUP
Programs and data used in setting up your installation. In general, you should not
need to use the files in this directory unless you are doing a node installation from a
server. If you call Siemens PTI for assistance, support personnel may ask you to
use programs in this directory to assist in diagnosing and resolving installation-
related issues.
TMLC
Conductor data files used by TMLC (only for installations where the lease includes
the Transmission Line Constants program section).
WECC
Source code for selected data conversion routines (Western Electricity Coordinating
Council, WECC).
Table 2-6. PSS
E Temp=x:\temp
Table 2-5. PSS
E Subdirectories (Cont.)
Name Description
2-16 Siemens Energy, Inc., Power Technologies International
2.7.4 Temporary Files
The temporary files have the extension BIN and are created in the directory specified by the Temp
parameter in the PSS
E .INI file.
2.7.5 Reserved Filenames
There are a number of files that PSS
E is to be executed. In addition, the filenames ending with .EXE and .BAT located in the subdi-
rectory PSSBIN should be treated as reserved.
2.8 Deleting Files
Any file created by the user or by PSS
E settings file.
IMD3100.INI IMD settings file.
PSSPLT3100.INI PSSPLT settings file.
PSSE.OPT PSS
E options file.
PSSOPF.OPT PSS
E gives the user great freedom in adapting the handling of input, the
recording of cases, and the output to suit the work as observed during its progress. As with all
systems that give a user great flexibility and many options, PSS
E is able, at any time, to write over the contents of a file that had previously been created.
PSS
E does not generally append to files; each time that a user specifies a filename to a PSS
E
file writing activity, such as SAVE or POUT, the writing commences at the start of that file, destroying
the previous contents. Activity OPTN does offer a File overwrite option that can be set to either
Overwrite without asking or Ask first.
This mode of operation has been found in thousands of man-years of use of PSS
E 32.0
File Usage Summary Program Operation Manual
2-18 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 3-1
Chapter 3
Startup
3.1 Preliminaries
When PSS
E is installed on your workstation (refer to the PSSE Installation Guide), the following
steps are recommended prior to starting up PSS
E:
Establish a working directory from which PSS
E
work session (refer to Section 2.3.1, Input Data Files and Section 2.5, Creating Input
Files).
3.2 Starting PSS
E
PSS
E 32.
This is the default location as established during program installation. Other applica-
tions in the PSS
E Windows Start
menu.
From the Windows Explorer application, double-click the psse32.exe file.
C:\Program Files\PTI\PSSE32\PSSBIN is the default directory location of psse32.exe.
An alternate directory location may be specified during program installation.
From the Windows Start menu, select
Programs > PSSE 32 > PSSE-32 Command Prompt and enter psse32.exe (or simply
psse32) at the DOS prompt, followed by [Enter].
Start a PSSE-32 Command Prompt and enter prog params where:
prog = name of program (e.g., IPLAN32) that is to be executed.
params = whatever start-up parameters are appropriate for the program.
Double-click a previously defined PSS
E-32 program.
Startup PSS
E 32.0
Starting PSS
E
(see PSS
E 32.0 Startup
Program Operation Manual Environment
Figure 3-1. Specifying the -buses Option in the PSSE-32 Command Prompt Window
3.3 Environment
The principal power system analysis calculations of PSS
E. The numeric value specified must be an integer multiple of 1,000, between 1,000 and
150,000 inclusive. If this token and its associated numeric value are omitted, PSS
E is started up
at the size level defined in the PSS
E
Options Files, Section 3.3.3, Program Run-Time Option Settings, and PSS
E activity OPTN), or at
the default bus size level determined during program installation if no PSS
E
is started up at 10,000 buses, the maximum number of loads, transformers, and CONs are deter-
Startup PSS
E 32.0
Environment Program Operation Manual
3-4 Siemens Energy, Inc., Power Technologies International
mined by interpolating between the corresponding capacities at the 4,000 and 12,000 bus size
levels, and the maximum number of areas, dc lines, and zero sequence mutuals are the same as
at the 4,000 bus size level.
Table 3-1. Standard Maximum PSS
E Program Capacities
I/E
or S
1,000
Buses
4,000
Buses
12,000
Buses
50,000
Buses
150,000
Buses
TRANSMISSION NETWORK COMPONENTS
Buses (including star point buses of
three-winding transformers)
- 1,000 4,000 12,000 50,000 150,000
Loads I/E 2,000 8,000 24,000 100,000 300,000
Plants I/E 300 1,200 3,600 10,000 26,840
Machines I/E 360 1,440 4,000 12,000 33,050
Wind machines I/E 20 60 120 240 560
Fixed shunts I/E 1,000 4,000 12,000 50,000 150,000
Switched shunts I/E 126 500 1,500 4,000 10,580
Branches (including transformers and
zero impedance lines)
I/E 2,500 10,000 24,000 100,000 300,000
Two-winding transformers (including
three-winding transformer members)
I/E 400 1,600 4,800 20,000 60,000
Three-winding transformers I/E 100 400 1,200 5,000 15,000
Transformer impedance correction
tables
S 16 32 64 96 96
Zero impedance lines I/E 50 200 600 2,500 7,500
Multisection line groupings I/E 100 400 800 1,600 3,710
Multisection line sections I/E 250 1,000 2,000 4,000 9,260
Two-terminal dc transmission lines S 20 30 40 50 50
Voltage source converter (VSC) dc
lines
S 10 20 30 40 40
Multiterminal dc lines S 5 5 5 20 20
Converters per multiterminal dc line S 12 12 12 12 12
dc buses per multiterminal dc line S 20 20 20 20 20
dc circuits per multiterminal dc line S 20 20 20 20 20
FACTS devices S 20 50 100 250 250
Interchange control areas S 100 250 500 1,200 1,200
Interarea transfers S 300 500 1,000 2,000 2,000
Zones S 999 999 999 9,999 9,999
Owners S 999 999 999 1,200 1,200
Machine owner specifications I/E 720 2,880 8,000 24,000 66,100
Branch owner specifications I/E 5,000 20,000 48,000 200,000 600,000
Zero sequence mutual couplings S 500 2,000 3,000 4,000 4,000
Siemens Energy, Inc., Power Technologies International 3-5
PSS
E 32.0 Startup
Program Operation Manual Environment
3.3.2 Setting Program Preferences
The [Program Preferences] dialog, which is accessible from the Edit > Preferences... menu entry,
allows for the selection of variety of program options regarding its operation from the Graphical User
Interface (GUI). Refer to PSS
E calculation and reporting functions recognize one or more program run-time option
settings. When PSS
E run-time options
are established.
The user may override most of the option settings described below during a PSS
E work session
via activity OPTN. Furthermore, the user may change a given option setting several times during a
PSS
E work session with repeated executions of activity OPTN. These option settings may then
DYNAMIC SIMULATION ELEMENTS
Synchronous machines I/E 360 1,440 4,000 12,000 33,050
Constant parameters (CONs) I/E 12,500 40,000 80,000 200,000 515,800
Algebraic variables (VARs) I/E 7,500 16,000 32,000 80,000 206,300
State variables (STATEs) I/E 5,000 20,000 40,000 100,000 257,900
Integer parameters (ICONs) I/E 10,000 20,000 40,000 100,000 257,900
Output channels I/E 750 3,000 8,000 24,000 66,110
User model definitions S 200 200 200 200 200
Activity CHAN/CHSB model entries S 500 2,000 2,000 2,000 2,000
Load model table entries I/E 1,000 4,000 12,000 50,000 150,000
Bus type load models I/E 250 1,000 3,000 12,500 37,500
Owner type load models S 999 999 999 1,200 1,200
Zone type load models S 999 999 999 2,000 2,000
Area type load models S 100 250 500 1,200 1,200
All type load models S 5 10 15 25 25
Line relay model connection table
entries
I/E 25 100 240 1,000 3,000
Auxiliary signal models S 20 30 40 50 50
Auxiliary signal injection point per two-
terminal dc line
S 4 4 4 4 4
Auxiliary signal injection point per
multi-terminal dc line
S 12 12 12 12 12
Auxiliary signal injection point per VSC
dc line
S 2 2 2 2 2
Auxiliary signal injection point per
FACTS device
- 1 1 1 1 1
Table 3-1. Standard Maximum PSS
E 32.0
Environment Program Operation Manual
3-6 Siemens Energy, Inc., Power Technologies International
be preserved in a PSS
E Options File (refer to activity OPTN). Such an Options File may then be
accessed on subsequent initiations of PSS
E as described below.
Each time PSS
E option settings that pertain only to the Optimal Power Flow program section are described
in Sections 13.8.3 and 13.10. They are preserved with Saved Cases and may also be preserved in
an Optimal Power Flow Options File.
Table 3-2. Saved Case Specific PSS
E either by
bus number (numbers option) or extended bus name consisting of the
twelve-character alphanumeric name plus the bus base voltage (names
option). This option does not apply to the bulk data input activities such as
READ, Reading Power Flow Data Additions from the Terminal, RDCH,
MCRE, RESQ, and TRSQ.
Bus output Numbers
Buses are ordered in PSS
E Application Program
Interface (API)).
Voltage output pu
Voltages are tabulated in either per unit or kV. This applies only to
activities LIST, EXAM, GENS, TLST, and Listing Control and Constraint
Data
Voltage input pu
Voltages are reported and entered in the [Spreadsheet]s and activity
CHNG in either per unit or kV.
Siemens Energy, Inc., Power Technologies International 3-7
PSS
E 32.0 Startup
Program Operation Manual Environment
Transmission
line data input
pu
Transmission line (not transformer or generator) impedances are entered
and/or reported in either per unit or ohms; line capacitances are in per unit
or microfarads. This option is recognized in activities CHNG, LIST, EXAM,
and the nontransformer branch [Spreadsheet].
Fault analysis
output units
pu
Fault analysis results are tabulated in either physical units or per unit. This
option is recognized by activities SCMU, SCOP, ASCC, BKDY, ANSI and
IECS.
Fault analysis
output
coordinates
Rectangular
Fault analysis results are tabulated in either rectangular (e.g., MW, Mvar)
or polar (e.g., MVA, angle) coordinates. This option is recognized by
activities SCMU, SCOP, ASCC, BKDY, ANSI and IECS .
Fault analysis
modeling
3-phase
The fault analysis activities SEQD, SCMU, SCOP, ASCC and IECS can
handle either 3-phase systems modeled by positive, negative, and zero
sequence networks, or center-tapped 2-phase systems used in some elec-
tric traction systems modeled by positive and zero sequence networks.
Base frequency 60.0 The system base frequency in Hertz (usually 50 or 60 Hz).
Default rating
set
Rate A
Establishes the default rating used by activities POUT, LOUT, and LAMP.
It also is used as the default value for those activities that allow the user to
select a rating set.
Tap adjustment Disabled
Sets the mode of tap adjustment in power flow solutions.
The Disabled mode suppresses transformer adjustments.
In the Step mode of tap adjustment, transformer taps are adjusted in
multiples of a user-specified tap step.
In the Direct mode of tap adjustment, a simultaneous continuous
adjustment is made of all voltage controlling transformers as well as
all Mvar controlling transformers and all bus voltage magnitudes.
Upon convergence of the main power flow iteration, tap ratios of
controlling transformers are moved to the nearest step and the
solution refined with tap ratios locked at those positions.
Area inter-
change
adjustment
Disabled
Sets the mode of area interchange control in power flow solutions.
The Disabled mode suppresses area interchange control.
If Tie lines only is selected, area swings are adjusted with an areas
net interchange defined as the sum of the flows on all of its tie lines.
If Tie lines and loads is selected, area swings are adjusted where an
areas net interchange includes tie line flows as well as contributions
from loads connected to area buses that are assigned to areas other
than the bus area, and from loads assigned to the area that are
connected to buses assigned to other areas.
Phase shift
adjustment
Disabled Enables or disables phase shift adjustment during power flow solutions.
Table 3-2. Saved Case Specific PSS
E 32.0
Environment Program Operation Manual
3-8 Siemens Energy, Inc., Power Technologies International
Switched shunt
adjustment
Enable all
Sets the mode of switched shunt adjustment during power flow solutions.
The Lock all mode suppresses all switched shunt adjustments
The Enable all mode allows adjustment of all in-service switched
shunts that are not locked
The Enable continuous, disable discrete mode allows adjustment
only of continuous mode swithed shunts
DC tap
adjustment
Enabled
Enables or disables the adjustment of dc transformer taps and of ac trans-
formers controlling a converter of a two-terminal dc line during power flow
solutions.
Non-divergent
Newton power
flow solution
Disabled
Activities FDNS, FNSL and the various ac contingency calculation func-
tions may optionally be executed in a mode in which the voltage vector of
diverging power flow iterations is captured and the solution terminated
prior to blowing up.
Solution
connectivity
check
Enabled
The power flow solution activities may be instructed to perform a network
connectivity check before beginning the voltage solution iterations. This
ensures that all Type 1 and Type 2 buses are connected back to a swing
(Type 3) bus by in-service ac branches.
Three-winding
transformer to
bus reporting
Disabled
When flow into three-winding transformer windings is reported in
activities POUT, LOUT, LAMP, and DCLF, the other two buses connected
to the transformer may optionally be listed.
Out-of-service
branch
reporting
Disabled
In the bus output blocks of activities POUT, LOUT, and LAMP, out-of-
service branches connected to the bus may optionally be listed.
Line shunt
reporting
Disabled
Line shunt powers may optionally be reported in activities POUT, LOUT,
and LAMP.
Non-trans-
former branch
percent loading
units
Current
expressed as
MVA
Percent loadings on non-transformer branches may be either percent MVA
loadings or percent current loadings in the reports of activities POUT,
LOUT, LAMP, RATE, RAT3, OLTR, and the various ac contingency calcu-
lation reporting functions. It is also honored by the single element and
subsystem data retrieval subroutines (refer to PSS
E Application Program
Interface (API)).
Transformer
percent loading
units
MVA
Transformer percent loadings may be either percent MVA loadings or
percent current loadings in the reports of activities POUT, LOUT, LAMP,
RATE, RAT3, OLTR, and the various ac contingency calculation reporting
functions. It is also honored by the single element and subsystem data
retrieval subroutines (refer to PSS
E 32.0 Startup
Program Operation Manual Environment
User Specified Option Settings
The option settings described in Table 3-3 may be preserved in a PSS
E file
writing activity.
Default PSS
E
size level
12000
Defines the default size level of PSS
E
is restarted. This setting may be overridden by the user at the time PSS
E
is initiated by specifying the -buses command line token followed by the
desired bus dimension as described in Section 3.3.1.
Output device
page lengths
24, 58, 60
and 60,
respectively
The number of lines per page on the users terminal (in the Report tab), on
the two primary hard copy output devices, and in disk files are recognized
when these devices are used as the output destination of PSS
E reports.
Table 3-2. Saved Case Specific PSS
E 32.0
Startup Parameter Files Program Operation Manual
3-10 Siemens Energy, Inc., Power Technologies International
Installation Dependent Option Settings
The option settings described in Table 3-4 are not preserved in any PSS
E option subroutine
PSSOPT.
3.4 Startup Parameter Files
Some PSS E programs will search for and use certain parameter files at program startup. Those
programs and their parameter files are listing in Table 3-5 below.
3.4.1 WINDOWS.PRM Files
The term WINDOWS.PRM is a generic name for files of the form WIN*.PRM in Table 3-6 above.
The files are used to define certain parameters for the GUI of those programs, including the toolbar
values. Table 3-6 describes the parameters in the WINDOWS.PRM file.
Table 3-4. Installation Dependent Option Settings
Highest Allowed Bus
Number
Defines the largest permissible number that may be assigned to a bus.
This is set to 999997 at all size levels of PSS
E as supplied by Siemens
PTI. The use of 5 and 6-digit bus numbers should be avoided in cases that
are subsequently processed as special formats where only 4-digit bus
numbers can be accommodated (e.g., IEEE Common Format).
Screen Clearing
Codes
These character codes are written to the users terminal at the beginning of
each page of PSS
E 32.0 Startup
Program Operation Manual Startup Parameter Files
Any parameter can be defined in WINDOWS.PRM. Any TOOLBAR definition will start an entirely
new toolbar definition.
PSSE programs search for the parameter files using the standard search path rules as described
in Section 2.7.3, File Search Path Rules. You can copy the files from the PSSPRM directory to one
of the alternate search path directories for your own customizing.
Node users may wish to modify the PSSPRM line in corresponding *.INI so that it points to a
local directory where they can store copies of the parameter files in order to allow customizing
their operations.
3.4.2 INI Files
The INI files are installed in the Windows directory. They contain all of the start-up and formatting
instructions such as directory location, report window font, and window placement. Use this file to
change such settings as fonts, printer page margins, or positions of frequently used windows. The
format of the file is: parameter=value, divided into sections whose names are contains in brackets.
The order in which the parameters are located in a given section of the file is unimportant. Any
parameter misspelled or incorrectly specified is either ignored or, as with fonts, partly used. Setup
automatically sets the start-up paths at installation time, but you may change them at any time to
suit your particular directory structure. You can override the default INI file and directory location by
specifying the argument, -INI pathname on the target path found in the properties shortcut field of
the programs Windows shortcut.
The following sections are valid in all the INI files listed in Table 3-6:
[Startup] Section: This section is used to define startup parameters for PSS
E. The following
parameters are valid:
Home Defines one of the alternate directories used to automatically search for program, user,
and PSS
E system files.
Path Defines the directory path where PSS
E.
Pssprm Defines the directory path for PSS
E. If this parameter is
not defined, the Windows temporary directory will be used.
Unit Used to specify the unit used for defining other values in this file. Valid values are: inch
or mm.
[FileMapping] Section: Filename: This is a special assignment that allows most files opened inter-
nally to PSS
E 32.0
Startup Parameter Files Program Operation Manual
3-12 Siemens Energy, Inc., Power Technologies International
The following sections are used by PSSPLT and IMD:
[TextMargins] Section: This section is used to define margins associated with all Windows printing
from PSS
E. Remember that the units are defined in the [Startup] section. The following parame-
ters are valid in this section:
LeftMargin Defines the left margin.
RightMargin Defines the right margin.
TopMargin Defines the top margin.
BottomMargin Defines the bottom margin.
[GraphicsMargins] Section: This section is used to define margins associated with all graphics
output using a Windows driver. Remember that the units are defined in the [Startup] section. The
following parameters are valid in this section:
LeftMargin Defines the left margin.
RightMargin Defines the right margin.
TopMargin Defines the top margin.
BottomMargin Defines the bottom margin.
Font Definition Sections: There are several font sections used by PSS
E 32.0 Startup
Program Operation Manual Startup Parameter Files
[ReportBufferSize] Section: This section is used to define the size, in bytes, of each report tab
used by the program. The memory allocated for this is the same for other items dynamically allo-
cated within the program and the total is limited to a size defined when the program is linked. The
following parameters with default values are:
Making these numbers too large could cause the program to crash at startup or fail to allocate
memory later on in its execution.
When examining the *.INI files, keep in mind that anything preceded by a semi-colon (;) repre-
sents a comment and is not read by the program.
Table 3-8. Font Parameters
Font
Parameter Description Valid Values
PointSize
Defines the font size using point size.
The larger the point size, the larger the
font.
Depends on the font chosen; 10 or 12 are
good initial values.
CharsPerInch
Defines the font size using characters
per inch (cpi). The larger the cpi
number, the smaller the font.
Depends on the font chosen; 10 or 12 are
good initial values.
Pitch Specifies the pitch of the font. Fixed, variable.
Family Specifies the font family. Decorative, modern, roman, script, swiss.
Quality Specifies the output quality. Draft, proof.
Weight
Specifies the thickness of the character
to be drawn.
Thin, extralight, light, normal, medium,
semibold, bold, extrabold, heavy.
FaceName
Specifies the font name such as Arial,
Courier New, Helvetica, Times.
Depends on the fonts installed on your
system. A good initial choice for a variable-
pitch font is Arial; a good choice for a fixed-
pitch font is Courier New. These fonts are
installed with Windows and are available on
all machines.
Activity Selector: 5000000
Reports: 5000000
Help: 61440
Startup PSS
E 32.0
Startup Parameter Files Program Operation Manual
3-14 Siemens Energy, Inc., Power Technologies International
This page intentionally left blank.
Siemens Energy, Inc., Power Technologies International 4-1
Chapter 4
Operating Modes
This chapter describes those procedures necessary to access PSS
E activity structure.
4.1 How to Approach PSS
E
The new user, after reading the preceding sections, may form the impression that PSS
E is a
complex and difficult program. It must be recognized, however, that PSS
E is an extremely
powerful tool that allows its user to handle a very broad range of power system calculations using
a single integrated program system. Its apparent complexity is, accordingly, more a function of the
many different types of data needed in power system work than it is a function of PSS
E itself. The
user will find that, after a very few work sessions with PSS
E, driving PSS
E:
1. The roles of the files in handling problem input data and in building up a library of working
cases that represent system conditions at selected stages of a study.
2. The capabilities of the individual PSS
E
Program Application Guide.
After an understanding of PSS
E dynamics study:
Operating Modes PSS
E 32.0
Activity Selection Program Operation Manual
4-2 Siemens Energy, Inc., Power Technologies International
1. Identify all the files that will be needed including input data files, Saved Case Files, Snapshot
Files, and Channel Output Files. Write out a summary listing the names and content of all
of these files using a PSS
E activity or function to be
performed, along with any input data required by it. The manual PSS
E API routines.
When operating PSS
E via the GUI, a single dialog box often provides the equivalent of multiple
API routines or calls to API routines. It can also provide alternatives of several API routines. The
question and answer dialog of the line mode may require several prompts and user responses for
the same functionality. The correspondence between input fields contained in these customized
dialogs to the arguments of the API calls and to the prompts issued when using the line mode
should be self-evident.
When an activity is initiated using either the GUI or command line, it must be completed in the same
mode. The next activity to be executed may then be initiated in either mode.
4.2.1 GUI Windows
The default set of windows displayed when PSS
E by the User
Across the top of the PSS
E GUI Users
Guide for details on activity execution in windows mode.
4.2.2 Command Line Interface
Access to the PSS
E Command Line Interface (CLI) is available by selecting the View > CLI Window
menu entry. Select either PSS
E Command Line Interface (CLI) Users Guide for details on activity execution using
the command line.
4.2.3 Automation Methods
PSS
E may also be operated using any of several program automation methods as described in
Chapter 15.
4.3 Interruption of PSS
E by the User
As an interactive program system, PSS
E interrupts are triggered by pressing the [F10] function key on the keyboard. Pressing the
[F10] function key brings up the Interrupt Handler window, which contains:
A toggle button box containing all the interrupt control codes to which PSS
E activities
are sensitive (see Table 4-1).
A [Resume] pushbutton through which PSS
E. The interrupt control codes to which an individual activity is sensitive are given in the
activity descriptions in Chapters 5 through 17 of this manual; any other interrupt control codes that
are specified to the activity are ignored.
In working with large cases, there may be a delay before an [F10] function keystroke is acknowl-
edged by PSS
E. During this delay, there is no visible evidence that the interrupt request has been
received by PSS
E.
In addition, pressing the [F10] function key before running a PSS
E 32.0
Interruption of PSS
E by the User
NC Suppress convergence monitor.
NM Suppress automatic adjustment monitors.
NV Suppress incorrect plant VAR limit report.
TI Print the present value of simulation TIME.
Table 4-1. Interrupt Codes (Cont.)
Interrupt
Code
Action
Operating Modes PSS
E 32.0
Virtual Output Devices Program Operation Manual
4-6 Siemens Energy, Inc., Power Technologies International
4.4 Virtual Output Devices
PSS
E
API as well. The table below lists the API routine to redirect each type of output, and other
commands that pertain to each output type.
When virtual devices are redirected to files, they can each be directed the same file. Output will
appear in the file in the order in which it was generated by the program.
Progress
Informational messages. This can include intermediate values of solutions, identifying
data from a file, copies of commands entered in the CLI, and warning about data condi-
tions that may or may not warrant further investigation by the user.
Alerts
Error messages. Something didnt work, or some condition was encountered that
prevented the program from performing the task it was asked to do.
Reports
Results of calculations and or analysis, or summaries of data from the programs
memory.
Prompts
The program is asking you a question. The PSS
E 32.0
Automation Program Operation Manual
4-8 Siemens Energy, Inc., Power Technologies International
6 FOR ALTERNATE SPOOL DEVICE
When OPEN has not been run, other reporting activities will display an output selection menu and
will have the following additional choice:
7 FOR PROGRESS DEVICE
In all cases entries of 0 through 7 will be accepted, but values that do not correspond to choices
displayed will default to other valid choices. The values that are skipped represent choices that are
no longer meaningful in the current program, but may still exist in recorded automation files.
4.6 Automation
PSS
E execution other
than by direct user interaction. These can be used to develop macro-type applications, i.e. files of
set procedures to be used interactively, or for unattended operation (batch), where the PSS
E can
run a pre-set series of operations to completion with no further interaction from the user. The oper-
ations can be fixed, or can be implemented in programming languages to whatever level of
complexity is desired. Chapter 15 described these features in detail.
4.7 Extended Modeling in Dynamics Simulation
PSS
Es Dynamics Simulation module comes with hundreds of available models that can be used
for network equipment built into the program. No special steps need to be taken by the user beyond
the data requirements for the models.
Additional models can be provided in user-created libraries. Dsusr.dll is assumed as the default
name for a user-created library and is automatically loaded if it is found. Additional model libraries
can be identified to PSS
E Application
Program Interface (API)).
Not every model can be identified to PSS
E
uses connection routines. These subroutines are called CONEC and CONET, and are normally
built as part of a dsusr.dll file.
Procedures to build user libraries are discussed in Sections 1.3 and 1.4. Model writing is discussed
in Chapter 20.
4.8 Subsystem Selection
Windows Mode
Most PSS
E activities allow the user to specify processing the current subsystem. In addition, the
appropriate [Subsystem Selector] dialog may be opened from the PSS
E
Command Line Interface (CLI) Users Guide. When using PSS
E 32.0
Activity Suffixes Program Operation Manual
4-10 Siemens Energy, Inc., Power Technologies International
required for the calling of user-written plant, load, line relay, auxiliary signal, dc line, and FACTS
device models, respectively. After being prepared using the methodology given in Chapter 18,
these subroutines must be incorporated into the PSS
E. Issuing
the command CLOAD4 (for those user models for which the user would write a model code)
executes the linking command procedure CLOAD4, which builds an executable program file
in the users directory.
4.11 Activity Suffixes
Command line only. Many output reporting activities and several processing activities make use of
the optional suffixes to enable the user to restrict the activitys reporting or processing to a selected
subset of the working case. These are described in detail in PSS
E is used.
If the file to be used is not in a Saved Case File format recognized by this release of PSS
E, the
following error message is generated:
FILE filename NOT IN SAVED CASE FORMAT
Then activity CASE ends. To recover, simply select activity CASE again, specifying a valid Saved
Case File filename.
Run Activity CASE - GUI
File > Open
[Open]
Saved Case file (*.sav)
Run Line Mode Activity CASE - CLI
ACTIVITY?
>>CASE
ENTER SAVED CASE FILENAME:
>>
Interrupt Control Codes
None
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Retrieving a Power Flow Saved Case File Program Operation Manual
5-2 Siemens Energy, Inc., Power Technologies International
If the Saved Case exceeds the current capacity limits of PSS
Es activity SAVE; it
should not be used to attempt to read files written by any other programs.
When picking up Saved Case Files created prior to PSS
E-31 transformer model wherever possible; non-zero transformer charging, and non-zero line
shunts that were not converted, generate an alarm and are set to zero. Non-zero values of line
length for transformers are set to zero but are not logged.
When picking up Saved Case Files created prior to PSS
E-10.
Siemens Energy, Inc., Power Technologies International 5-3
PSS
Es working memory, the settings from the Saved Case are established
and an appropriate message is printed (refer to Section 3.3.3).
Additional Information
PSS
E GUI Users Guide, Section 6.1, Retrieving a Power Flow Saved Case File
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-4 Siemens Energy, Inc., Power Technologies International
5.2 Reading Power Flow Raw Data into the Working Case
Activity READ
The bulk power flow data input activities READ and TREA read hand-typed power flow source data
and enter it into the power flow working case, rearranging it from its original format into a computa-
tionally oriented data structure in the process. The source data records are read from a Power Flow
Raw Data File.
One of several PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-6 Siemens Energy, Inc., Power Technologies International
Q Record
Generally, specifying a data record with a Q in column one is used to indicate that no more data
records are to be supplied to activity READ. This end of data input indicator is permitted anywhere
in the Power Flow Raw Data File except where activity READ is expecting one of the following:
one of the three Case Identification Data records.
the second or subsequent records of the four-record block defining a two-winding
transformer.
the second or subsequent records of the five-record block defining a three-winding
transformer.
the second or third record of the three-record block defining a two-terminal dc transmis-
sion line.
the second or third record of the three-record block defining a VSC dc transmission
line.
the second or subsequent records of the series of data records defining a multi-terminal
dc transmission line.
Siemens Energy, Inc., Power Technologies International 5-7
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-8 Siemens Energy, Inc., Power Technologies International
Case Identification Data
Case identification data consists of three data records. The first record contains six items of data as
follows:
IC, SBASE, REV, XFRRAT, NXFRAT, BASFRQ
where:
When current ratings are being specified, ratings are entered as:
MVA
rated
= \ 3 x E
base
x I
rated
x 10
-6
where:
The next two records each contain a line of text to be associated with the case as its case title. Each
line may contain up to 60 characters, which are entered in columns 1 through 60.
IC :
0 for base case input (i.e., clear the working case before adding data to it)
1 to add data to the working case
IC = 0 by default.
SBASE System MVA base. SBASE = 100.0 by default.
REV PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-10 Siemens Energy, Inc., Power Technologies International
Each load at a bus can be a mixture of loads with three different characteristics: the Constant Power
Load Characteristic, the Constant Current Load Characteristic, and the constant admittance load
characteristic. For additional information on load characteristic modeling, refer to Section 6.3.13,
Load, activities CONL and RCNL, Section 11.3.1, Modeling Load Characteristics and
Section 11.3.2, Basic Load Characteristics.
Each load data record has the following format:
I, ID, STATUS, AREA, ZONE, PL, QL, IP, IQ, YP, YQ, OWNER, SCALE
where:
Load data input is terminated with a record specifying a bus number of zero.
Load Data Notes
The area, zone, and owner assignments of loads are used for area, zone, and owner totaling pur-
poses (e.g., in activities AREA, OWNR, and ZONE) and for load scaling and conversion purposes.
They may differ from those of the bus to which they are connected. The area and zone assignments
of loads may optionally be used during area and zone interchange calculations (refer to Area Inter-
change Control and activities AREA, ZONE, TIES, TIEZ, INTA, and INTZ).
I Bus number, or extended bus name enclosed in single quotes (refer to Extended Bus
Names). No default allowed.
ID One- or two-character uppercase non-blank alphanumeric load identifier used to
distinguish among multiple loads at bus I. It is recommended that, at buses for which
a single load is present, the load be designated as having the load identifier 1. ID = 1
by default.
STATUS Load status of one for in-service and zero for out-of-service. STATUS = 1 by default.
AREA Area to which the load is assigned (1 through 9999). By default, AREA is the area to
which bus I is assigned (refer to Bus Data).
ZONE Zone to which the load is assigned (1 through 9999). By default, ZONE is the zone to
which bus I is assigned (refer to Bus Data).
PL Active power component of constant MVA load; entered in MW. PL = 0.0 by default.
QL Reactive power component of constant MVA load; entered in Mvar. QL = 0.0 by
default.
IP Active power component of constant current load; entered in MW at one per unit
voltage. IP = 0.0 by default.
IQ Reactive power component of constant current load; entered in Mvar at one per unit
voltage. IQ = 0.0 by default.
YP Active power component of constant admittance load; entered in MW at one per unit
voltage. YP = 0.0 by default.
YQ Reactive power component of constant admittance load; entered in Mvar at one per
unit voltage. YQ is a negative quantity for an inductive load and positive for a capaci-
tive load. YQ = 0.0 by default.
OWNER Owner to which the load is assigned (1 through 9999). By default, OWNER is the
owner to which bus I is assigned (refer to Bus Data).
SCALE Load scaling flag of one for a scalable load and zero for a fixed load (refer to SCAL).
SCALE = 1 by default.
Siemens Energy, Inc., Power Technologies International 5-11
PSS
E
GUI Users Guide, Section 11.1.1, Boundary Conditions).
Figure 5-2. Constant Power Load Characteristic
Voltage
0.0
0.6 0.7 0.8 1.0 1.1
0
.
0
1
.
0
1
.
1
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-12 Siemens Energy, Inc., Power Technologies International
Constant Current Load Characteristic
The constant current characteristic holds the load current constant as long as the bus voltage
exceeds 0.5 pu, and assumes an elliptical current-voltage characteristic as shown in Figure 5-3 for
voltages below 0.5 pu.
Figure 5-3. Constant Current Load Characteristic
Fixed Bus Shunt Data
Each network bus at which fixed bus shunt is to be represented must be specified in at least one
fixed bus shunt data record. Multiple fixed bus shunts may be represented at a bus by specifying
more than one fixed bus shunt data record for the bus, each with a different shunt identifier.
Voltage
Current
Power
0.0 0.5 1.0 1.1
0
.
0
0
.
5
1
.
0
1
.
1
Siemens Energy, Inc., Power Technologies International 5-13
PSS
E must be specified in a
generator data record. In particular, each bus specified in the bus data input with a Type code of 2
or 3 must have a generator data record entered for it.
I Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names). No default allowed.
ID One- or two-character uppercase non-blank alphanumeric shunt identifier used to
distinguish among multiple shunts at bus I. It is recommended that, at buses for
which a single shunt is present, the shunt be designated as having the shunt identi-
fier 1. ID = 1 by default.
STATUS Shunt status of one for in-service and zero for out-of-service. STATUS = 1 by
default.
GL Active component of shunt admittance to ground; entered in MW at one per unit
voltage. GL should not include any resistive impedance load, which is entered as
part of load data. GL = 0.0 by default.
BL Reactive component of shunt admittance to ground; entered in Mvar at one per unit
voltage. BL should not include any reactive impedance load, which is entered as
part of load data; line charging and line connected shunts, which are entered as part
of non-transformer branch data; transformer magnetizing admittance, which is
entered as part of transformer data; or switched shunt admittance, which is entered
as part of switched shunt data. BL is positive for a capacitor, and negative for a
reactor or an inductive load. BL = 0.0 by default.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-14 Siemens Energy, Inc., Power Technologies International
Each generator has a single line data record with the following format:
I,ID,PG,QG,QT,QB,VS,IREG,MBASE,ZR,ZX,RT,XT,GTAP,STAT,
RMPCT,PT,PB,O1,F1,...,O4,F4,WMOD,WPF
where:
I Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names). No default allowed.
ID One- or two-character uppercase non-blank alphanumeric machine identifier used
to distinguish among multiple machines at bus I. It is recommended that, at buses
for which a single machine is present, the machine be designated as having the
machine identifier 1. ID = 1 by default.
PG Generator active power output; entered in MW. PG = 0.0 by default.
QG Generator reactive power output; entered in Mvar. QG needs to be entered only if
the case, as read in, is to be treated as a solved case. QG = 0.0 by default.
QT Maximum generator reactive power output; entered in Mvar. For fixed output gener-
ators (i.e., nonregulating), QT must be equal to the fixed Mvar output. QT = 9999.0
by default.
QB Minimum generator reactive power output; entered in Mvar. For fixed output gener-
ators, QB must be equal to the fixed Mvar output. QB = -9999.0 by default.
VS Regulated voltage setpoint; entered in pu. VS = 1.0 by default.
IREG Bus number, or extended bus name enclosed in single quotes, of a remote Type 1
or 2 bus for which voltage is to be regulated by this plant to the value specified by
VS. If bus IREG is other than a Type 1 or 2 bus, bus I regulates its own voltage to
the value specified by VS. IREG is entered as zero if the plant is to regulate its own
voltage and must be zero for a Type 3 (swing) bus. IREG = 0 by default.
MBASE Total MVA base of the units represented by this machine; entered in MVA. This
quantity is not needed in normal power flow and equivalent construction work, but is
required for switching studies, fault analysis, and dynamic simulation.
MBASE = system base MVA by default.
Siemens Energy, Inc., Power Technologies International 5-15
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-16 Siemens Energy, Inc., Power Technologies International
Generator data input is terminated with a record specifying a bus number of zero.
Reactive Power Limits
In specifying reactive power limits for voltage controlling plants (i.e., those with unequal reactive
power limits), the use of very narrow var limit bands is discouraged. The Newton-Raphson based
power flow solutions require that the difference between the controlling equipment's high and low
reactive power limits be greater than 0.002 pu for all setpoint mode voltage controlling equipment
(0.2 Mvar on a 100 MVA system base). It is recommended that voltage controlling plants have Mvar
ranges substantially wider than this minimum permissible range.
For additional information on generator modeling in power flow solutions, refer to Sections 6.3.12
and 6.3.17.
Modeling of Generator Step-Up Transformers (GSU)
Before setting-up the generator data, it is important to understand the two methods by which a
generator and its associated GSU are represented.
The Implicit Method
The transformer data is included on the generator data record.
The transformer is not explicitly represented as a transformer branch.
The generator terminal bus is not explicitly represented.
Figure 5-4 shows that bus K is the Type 2 bus. This is the bus at which the generator will regu-
late/control voltage unless the user specifies a remote bus.
Figure 5-4. Implicit GSU Configuration Specified as Part of the Generator
The Explicit Method
In this method, the transformer data is not specified with the generator data. It is entered separately
(see Transformer Data) in a transformer branch data block.
In Figure 5-5, there is an additional bus to represent the generator terminal. This is the Type 2 bus
where the generator will regulate/control voltage unless the user specifies a remote bus.
WPF Power factor used in calculating reactive power limits or output when WMOD is 2 or
3. WPF = 1.0 by default.
Siemens Energy, Inc., Power Technologies International 5-17
PSS
E
power flow activities may be used and then, any time prior to beginning switching study, fault anal-
ysis, or dynamic simulation work, activity MCRE may be used to introduce the individual machine
impedance and step-up transformer data; activity MCRE also apportions the total plant loading
among the individual machines.
As an example, Figure 5-6 shows three Type 2 buses, each having two connected units. For gener-
ators 1 through 4, the GSU is explicitly represented while for generators 5 and 6 the GSU is implicitly
represented. Figure 5-7 shows the generator data records corresponding to Figure 5-6.
The separate transformer data records for the explicitly represented transformers from buses
1238 and 1239 to bus 1237 are not included in Figure 5-7.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-18 Siemens Energy, Inc., Power Technologies International
Figure 5-6. Multiple Generators at a Single Plant
Figure 5-7. Data Set for the Multiple Generators in Figure 5-6
Non-Transformer Branch Data
Each ac network branch to be represented in PSS
E, the basic transmission line model is an Equivalent Pi connected between network buses.
Figure 5-8 shows the required parameter data where the equivalent Pi is comprised of:
A series impedance (R + jX).
Two admittance branches (jB
ch
/2) representing the lines capacitive admittance (line
charging).
Two admittance branches (G + jB) for shunt equipment units (e.g., reactors) that are
connected to and switched with the line.
I ID PG QG QT QB VS IREG MBASE ZR,ZX RT,XT GTAP STAT RMPCT PT PB
(not specified)
Siemens Energy, Inc., Power Technologies International 5-19
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-20 Siemens Energy, Inc., Power Technologies International
Non-transformer branch data input is terminated with a record specifying a from bus number of
zero.
Zero Impedance Lines
PSS
E provides for the treatment of bus ties, jumpers, breakers, switches, and other low imped-
ance branches as zero impedance lines. For a branch to be treated as a zero impedance line, it
must have the following characteristics:
Its resistance must be zero.
Its magnitude of reactance must be less than or equal to the zero impedance line
threshold tolerance, THRSHZ.
It must be a non-transformer branch.
During network solutions, buses connected by such lines are treated as the same bus, thus having
identical bus voltages. At the completion of each solution, the loadings on zero impedance lines are
determined.
RATEC Third rating; entered in either MVA or current expressed as MVA, according to the
value specified for NXFRAT specified on the first data record (refer to Case Identifi-
cation Data). RATEC = 0.0 by default.
When specified in units of current expressed as MVA, ratings are entered as:
MVA
rated
=
\ 3 x
E
base
x I
rated
x 10
-6
where:
E
base
is the base line-to-line voltage in volts of the buses to which
the terminal of the branch is connected
I
rated
is the branch rated phase current in amperes.
GI,BI Complex admittance of the line shunt at the bus I end of the branch; entered in pu.
BI is negative for a line connected reactor and positive for line connected capacitor.
GI + jBI = 0.0 by default.
GJ,BJ Complex admittance of the line shunt at the bus J end of the branch; entered in pu.
BJ is negative for a line connected reactor nd positive for line connected capacitor.
GJ + jBJ = 0.0 by default.
ST Branch status of one for in-service and zero for out-of-service; ST = 1 by default.
MET Metered end flag;
<1 to designate bus I as the metered end
>2 to designate bus J as the metered end.
MET = 1 by default.
LEN Line length; entered in user-selected units. LEN = 0.0 by default.
Oi Owner number (1 through 9999). Each branch may have up to four owners. By
default, O1 is the owner to which bus I is assigned (refer to Bus Data) and O2, O3,
and O4 are zero.
Fi Fraction of total ownership assigned to owner Oi; each Fi must be positive. The Fi
values are normalized such that they sum to 1.0 before they are placed in the
working case. By default, each Fi is 1.0.
Siemens Energy, Inc., Power Technologies International 5-21
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-22 Siemens Energy, Inc., Power Technologies International
Breaker and Switch Branches
The breakers and switches are represented as non-transformer branches in PSS
E. A non-trans-
former branch with an at sign @ or an asterisk - in the first character of circuit ID is identified as
a breaker or a switch respectively.
Most activities do not honor the breaker and switch circuit ID. Breaker and switch branches are
treated as zero impedance lines if they have characteristics of zero impedance lines; otherwise,
they are treated as regular non-transformer branches. It is recommended that a non-transformer
branch with the breaker circuit ID or switch circuit ID be modeled as a zero impedance line.
Breaker and switch branches are recognized in Substation Reliability Assessment (refer to
Section 6.14, Calculating Substation Reliability) and activity DFAX. Substation Reliability Assess-
ment simulates operations of breakers to isolate faults in a substation and manual switching to
restore the service to supply loads. Distribution Factor File setup activity can process automatic
commands to operate and monitor breakers and switches in Contingency Description Data File and
Monitored Element Data File respectively.
As mentioned in the section Zero Impedance Lines, PSS
E.
When specifying a two-winding transformer between buses I and J with circuit identifier CKT, if a
nontransformer branch between buses I and J with a circuit identifier of CKT is already present in
the working case, it is replaced (i.e., the nontransformer branch is deleted from the working case
and the newly specified two-winding transformer is then added to the working case).
t
1
: t
2
t
1
t
3
t
2
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-24 Siemens Energy, Inc., Power Technologies International
All data items on the first record are specified for both two- and three-winding transformers:
I The bus number, or extended bus name enclosed in single quotes (refer to
Extended Bus Names), of the bus to which Winding 1 is connected. The trans-
formers magnetizing admittance is modeled on Winding 1. Winding 1 is the only
winding of a two-winding transformer for which tap ratio or phase shift angle may be
adjusted by the power flow solution activities; any winding(s) of a three-winding
transformer may be adjusted. No default is allowed.
J The bus number, or extended bus name enclosed in single quotes, of the bus to
which Winding 2 is connected. No default is allowed.
K The bus number, or extended bus name enclosed in single quotes, of the bus to
which Winding 3 is connected. Zero is used to indicate that no third winding is
present (i.e., that a two-winding rather than a three-winding transformer is being
specified). K = 0 by default.
CKT One- or two-character uppercase non-blank alphanumeric transformer circuit identi-
fier; the first character of CKT must not be an ampersand ( & ), at sign ( @ ), or
asterisk ( - ); refer to Multi-Section Line Grouping Data and Section 6.13.2, Outage
Statistics Data File Contents. CKT = 1 by default.
CW The winding data I/O code that defines the units in which the turns ratios WINDV1,
WINDV2 and WINDV3 are specified (the units of RMAn and RMIn are also
governed by CW when |CODn| is 1 or 2):
1 for off-nominal turns ratio in pu of winding bus base voltage
2 for winding voltage in kV
3 for off-nominal turns ratio in pu of nominal winding voltage,
NOMV1, NOMV2 and NOMV3.
CW = 1 by default.
CZ The impedance data I/O code that defines the units in which the winding imped-
ances R1-2, X1-2, R2-3, X2-3, R3-1 and X3-1 are specified:
1 for resistance and reactance in pu on system MVA base and
winding voltage base
2 for resistance and reactance in pu on a specified MVA base and
winding voltage base
3 for transformer load loss in watts and impedance magnitude in pu
on a specified MVA base and winding voltage base.
In specifying transformer leakage impedances, the base voltage values are always
the nominal winding voltages that are specified on the third, fourth and fifth records
of the transformer data block (NOMV1, NOMV2 and NOMV3). If the default NOMVn
is specified, it is assumed to be identical to the winding n bus base voltage.
CZ = 1 by default.
Siemens Energy, Inc., Power Technologies International 5-25
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-26 Siemens Energy, Inc., Power Technologies International
The first three data items on the second record are read for both two- and three-winding trans-
formers; the remaining data items are used only for three-winding transformers:
R1-2, X1-2 The measured impedance of the transformer between the buses to which its first
and second windings are connected.
When CZ is 1, they are the resistance and reactance, respectively, in pu on system
MVA base and winding voltage base.
When CZ is 2, they are the resistance and reactance, respectively, in pu on Winding
1 to 2 MVA base (SBASE1-2) and winding voltage base.
When CZ is 3, R1-2 is the load loss in watts, and X1-2 is the impedance magnitude
in pu on Winding 1 to 2 MVA base (SBASE1-2) and winding voltage base. For
three-phase transformers or three-phase banks of single phase transformers, R1-2
should specify the three-phase load loss.
R1-2 = 0.0 by default, but no default is allowed for X1-2.
SBASE1-2 The Winding 1 to 2 three-phase base MVA of the transformer. SBASE1-2 = SBASE
(the system base MVA) by default.
R2-3, X2-3 The measured impedance of a three-winding transformer between the buses to
which its second and third windings are connected; ignored for a two-winding
transformer.
When CZ is 1, they are the resistance and reactance, respectively, in pu on system
MVA base and winding voltage base.
When CZ is 2, they are the resistance and reactance, respectively, in pu on Winding
2 to 3 MVA base (SBASE2-3) and winding voltage base.
When CZ is 3, R2-3 is the load loss in watts, and X2-3 is the impedance magnitude
in pu on Winding 2 to 3 MVA base (SBASE2-3) and winding voltage base. For
three-phase transformers or three-phase banks of single phase transformers, R2-3
should specify the three-phase load loss.
R2-3 = 0.0 by default, but no default is allowed for X2-3.
SBASE2-3 The Winding 2 to 3 three-phase base MVA of a three-winding transformer; ignored
for a two-winding transformer. SBASE2-3 = SBASE (the system base MVA) by
default.
R3-1, X3-1 The measured impedance of a three-winding transformer between the buses to
which its third and first windings are connected; ignored for a two-winding
transformer.
When CZ is 1, they are the resistance and reactance, respectively, in pu on system
MVA base and winding voltage base.
When CZ is 2, they are the resistance and reactance, respectively, in pu on Winding
3 to 1 MVA base (SBASE3-1) and winding voltage base.
When CZ is 3, R3-1 is the load loss in watts, and X3-1 is the impedance magnitude
in pu on Winding 3 to 1 MVA base (SBASE3-1) and winding voltage base. For
three-phase transformers or three-phase banks of single phase transformers, R3-1
should specify the three-phase load loss.
R3-1 = 0.0 by default, but no default is allowed for X3-1.
SBASE3-1 The Winding 3 to 1 three-phase base MVA of a three-winding transformer; ignored
for a two-winding transformer. SBASE3-1 = SBASE (the system base MVA) by
default.
Siemens Energy, Inc., Power Technologies International 5-27
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-28 Siemens Energy, Inc., Power Technologies International
CONT1 The bus number, or extended bus name enclosed in single quotes (refer to
Extended Bus Names), of the bus for which voltage is to be controlled by the trans-
former turns ratio adjustment option of the power flow solution activities when
COD1 is 1. CONT1 should be non-zero only for voltage controlling transformer
windings.
CONT1 may specify a bus other than I, J, or K; in this case, the sign of CONT1
defines the location of the controlled bus relative to the transformer winding. If
CONT1 is entered as a positive number, or a quoted extended bus name, the ratio
is adjusted as if bus CONT1 is on the Winding 2 or Winding 3 side of the trans-
former; if CONT1 is entered as a negative number, or a quoted extended bus name
with a minus sign preceding the first character, the ratio is adjusted as if bus
|CONT1| is on the Winding 1 side of the transformer. CONT1 = 0 by default.
RMA1,
RMI1
When |COD1| is 1, 2 or 3, the upper and lower limits, respectively, of one of the
following:
Off-nominal turns ratio in pu of Winding 1 bus base voltage when |COD1| is
1 or 2 and CW is 1; RMA1 = 1.1 and RMI1 = 0.9 by default.
Actual Winding 1 voltage in kV when |COD1| is 1 or 2 and CW is 2. No
default is allowed.
Off-nominal turns ratio in pu of nominal Winding 1 voltage (NOMV1) when
|COD1| is 1 or 2 and CW is 3; RMA1 = 1.1 and RMI1 = 0.9 by default.
Phase shift angle in degrees when |COD1| is 3. No default is allowed.
Not used when |COD1| is 0 or 4; RMA1 = 1.1 and RMI1 = 0.9 by default.
VMA1,
VMI1
When |COD1| is 1, 2 or 3, the upper and lower limits, respectively, of one of the
following:
Voltage at the controlled bus (bus |CONT1|) in pu when |COD1| is 1.
VMA1 = 1.1 and VMI1 = 0.9 by default.
Reactive power flow into the transformer at the Winding 1 bus end in Mvar
when |COD1| is 2. No default is allowed.
Active power flow into the transformer at the Winding 1 bus end in MW when
|COD1| is 3. No default is allowed.
Not used when |COD1| is 0 or 4; VMA1 = 1.1 and VMI1 = 0.9 by default.
NTP1 The number of tap positions available; used when COD1 is 1 or 2. NTP1 must be
between 2 and 9999. NTP1 = 33 by default.
TAB1 The number of a transformer impedance correction table if this transformer
windings impedance is to be a function of either off-nominal turns ratio or phase
shift angle (refer to Transformer Impedance Correction Tables), or 0 if no trans-
former impedance correction is to be applied to this transformer winding. TAB1 = 0
by default.
CR1, CX1 The load drop compensation impedance for voltage controlling transformers
entered in pu on system base quantities; used when COD1 is 1. CR1 + j CX1 = 0.0
by default.
Siemens Energy, Inc., Power Technologies International 5-29
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-30 Siemens Energy, Inc., Power Technologies International
The fifth data record is specified only for three-winding transformers:
RMA2,
RMI2
When |COD2| is 1, 2 or 3, the upper and lower limits, respectively, of one of the
following:
Off-nominal turns ratio in pu of Winding 2 bus base voltage when |COD2| is
1 or 2 and CW is 1; RMA2 = 1.1 and RMI2 = 0.9 by default.
Actual Winding 2 voltage in kV when |COD2| is 1 or 2 and CW is 2. No default
is allowed.
Off-nominal turns ratio in pu of nominal Winding 2 voltage (NOMV2) when
|COD2| is 1 or 2 and CW is 3; RMA2 = 1.1 and RMI2 = 0.9 by default.
Phase shift angle in degrees when |COD2| is 3. No default is allowed.
Not used when |COD2| is 0; RMA2 = 1.1 and RMI2 = 0.9 by default.
VMA2,
VMI2
When |COD2| is 1, 2 or 3, the upper and lower limits, respectively, of one of the
following:
Voltage at the controlled bus (bus |CONT2|) in pu when |COD2| is 1.
VMA2 = 1.1 and VMI2 = 0.9 by default.
Reactive power flow into the transformer at the Winding 2 bus end in Mvar
when |COD2| is 2. No default is allowed.
Active power flow into the transformer at the Winding 2 bus end in MW when
|COD2| is 3. No default is allowed.
Not used when |COD2| is 0; VMA2 = 1.1 and VMI2 = 0.9 by default.
NTP2 The number of tap positions available; used when COD2 is 1 or 2. NTP2 must be
between 2 and 9999. NTP2 = 33 by default.
TAB2 The number of a transformer impedance correction table if this transformer
windings impedance is to be a function of either off-nominal turns ratio or phase
shift angle (refer to Transformer Impedance Correction Tables), or 0 if no trans-
former impedance correction is to be applied to this transformer winding. TAB2 = 0
by default.
CR2, CX2 The load drop compensation impedance for voltage controlling transformers
entered in pu on system base quantities; used when COD2 is 1. CR2 + j CX2 = 0.0
by default.
WINDV3 When CW is 1, WINDV3 is the Winding 3 off-nominal turns ratio in pu of Winding 3
bus base voltage; WINDV3 = 1.0 by default.
When CW is 2, WINDV3 is the actual Winding 3 voltage in kV; WINDV3 is equal to
the base voltage of bus K by default.
When CW is 3, WINDV3 is the Winding 3 off-nominal turns ratio in pu of nominal
Winding 3 voltage, NOMV3; WINDV3 = 1.0 by default.
NOMV3 The nominal (rated) Winding 3 voltage base in kV, or zero to indicate that nominal
Winding 3 voltage is assumed to be identical to the base voltage of bus K. NOMV3
is used in converting tap ratio data between values in per unit of nominal Winding 3
voltage and values in per unit of Winding 3 bus base voltage when CW is 3. NOMV3
= 0.0 by default.
Siemens Energy, Inc., Power Technologies International 5-31
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-32 Siemens Energy, Inc., Power Technologies International
Transformer data input is terminated with a record specifying a Winding 1 bus number of zero.
Three-Winding Transformer Notes
The transformer data record blocks described in Transformer Data provide for the specification of
both two-winding transformers and three-winding transformers. A three-winding transformer is
modeled in PSS
E, the user should resolve the cause of the message (e.g., was correct input data
specified?) and use engineering judgement to resolve modeling issues (e.g., is this the best way to
model this transformer or would some other modeling be more appropriate?).
VMA3,
VMI3
When |COD3| is 1, 2 or 3, the upper and lower limits, respectively, of one of the
following:
Voltage at the controlled bus (bus |CONT3|) in pu when |COD3| is 1.
VMA3 = 1.1 and VMI3 = 0.9 by default.
Reactive power flow into the transformer at the Winding 3 bus end in Mvar
when |COD3| is 2. No default is allowed.
Active power flow into the transformer at the Winding 3 bus end in MW when
|COD3| is 3. No default is allowed.
Not used when |COD3| is 0; VMA3 = 1.1 and VMI3 = 0.9 by default.
NTP3 The number of tap positions available; used when COD3 is 1 or 2. NTP3 must be
between 2 and 9999. NTP3 = 33 by default.
TAB3 The number of a transformer impedance correction table if this transformer
windings impedance is to be a function of either off-nominal turns ratio or phase
shift angle (refer to Transformer Impedance Correction Tables), or 0 if no trans-
former impedance correction is to be applied to this transformer winding. TAB3 = 0
by default.
CR3, CX3 The load drop compensation impedance for voltage controlling transformers
entered in pu on system base quantities; used when COD3 is 1. CR3 + j CX3 = 0.0
by default.
Siemens Energy, Inc., Power Technologies International 5-33
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-34 Siemens Energy, Inc., Power Technologies International
Example Three-Winding Transformer Data Records
Figure 5-11 shows the data records for a 300 MVA, 345/138/13.8 kV three-winding transformer
connected to system buses with nominal voltages of 345 kV, 138 kV and 13.8 kV, respectively, and
sample data on 100 MVA system base and winding base voltages of 345 kV, 138 kV and 13.8 kV.
Figure 5-11. Sample Data for Three-Winding Transformer
Adjustable tap
on winding 2
Adjustable tap
on winding 3
I, J, K, CKT, CW, CZ, CM, MAG1, MAG2, NMETR, NAME, STAT, O1, F1, ..., O4, F4
R1-2, X1-2, SBASE1-2, R2-3, X2-3, SBASE2-3, R3-1, X3-1, SBASE3-1, VMSTAR, ANSTAR
WINDV1, NOMV1, ANG1, RATA1, RATB1, RATC1, COD1, CONT1, RMA1, RMI1, VMA1, VMI1,
NTP1, TAB1, CR1, CX1
WINDV2, NOMV2, ANG2, RATA2, RATB2, RATC2, COD2, CONT2, RMA2, RMI2, VMA2, VMI2,
NTP2, TAB2, CR2, CX2
WINDV3, NOMV3, ANG3, RATA3, RATB3, RATC3, COD3, CONT3, RMA3, RMI3, VMA3, VMI3,
NTP3, TAB3, CR3, CX3
t
1
t
2
t
3
Siemens Energy, Inc., Power Technologies International 5-35
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-36 Siemens Energy, Inc., Power Technologies International
Assigning ownership attributes to buses and other equipment allows an additional subdivision of
the network for analysis and documentation purposes. PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-38 Siemens Energy, Inc., Power Technologies International
system where the rectifier and inverter are physically located at the same site and separated only
by a short bus-bar.
The data requirements fall into three groups:
Control parameters and set-points
Converter transformers
The dc line characteristics
Each two-terminal dc transmission line to be represented in PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-40 Siemens Energy, Inc., Power Technologies International
Data on the third of the three dc line data records contains the inverter quantities corresponding to
the rectifier quantities specified on the second record described above. The significant difference is
that the control angle ALFA for the rectifier is replaced by the control angle GAMMA for the inverter.
IPI,NBI,GAMMX,GAMMN,RCI,XCI,EBASI,TRI,TAPI,TMXI,TMNI,STPI,ICI,IFI,ITI,IDI,XCAPI
DC line data input is terminated with a record specifying a blank dc line name or a dc line name of
0.
Two-Terminal DC Line Data Notes
The steady-state two-terminal dc line model used in power flow analysis establishes the initial
steady state for dynamic analysis.
DC line converter buses, IPR and IPI, may be Type 1, 2, or 3 buses. Generators, loads, fixed and
switched shunt elements, other dc line converters, and FACTS device sending ends are permitted
at converter buses.
When either XCAPR > 0.0 or XCAPI > 0.0, the two-terminal dc line is treated as capacitor commu-
tated. Capacitor commutated two-terminal dc lines preclude the use of a remote ac transformer as
commutation transformer tap and remote commutation angle buses at either converter. Any data
provided in these fields are ignored for capacitor commutated two-terminal dc lines.
For additional information on dc line modeling in power flow solutions, refer to Section 6.3.16, DC
Lines.
Voltage Source Converter (VSC) DC Transmission Line Data
The voltage source converter (VSC) two-terminal dc transmission line model is used to simulate
either a point-to-point system or a back-to-back system using voltage source converters.
Each voltage source converter (VSC) dc line to be represented in PSS
E is introduced by reading
a set of three consecutive data records. Each set of VSC dc line data records has the following
format:
'NAME', MDC, RDC, O1, F1, ... O4, F4
IBUS,TYPE,MODE,DCSET,ACSET,ALOSS,BLOSS,MINLOSS,SMAX,IMAX,PWF,MAXQ,MINQ,REMOT,RMPCT
IBUS,TYPE,MODE,DCSET,ACSET,ALOSS,BLOSS,MINLOSS,SMAX,IMAX,PWF,MAXQ,MINQ,REMOT,RMPCT
XCAPR Commutating capacitor reactance magnitude per bridge; entered in ohms.
XCAPR = 0.0 by default.
Siemens Energy, Inc., Power Technologies International 5-41
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-42 Siemens Energy, Inc., Power Technologies International
VSC dc line data input is terminated with a record specifying a blank dc line name or a dc line name
of 0.
VSC DC Line Data Notes
Each VSC dc line converter bus must have the following characteristics:
It must be a Type 1 or 2 bus. Generators, loads, fixed and switched shunt elements,
other dc line converters, and FACTS device sending ends are permitted at converter
buses.
It must not have the terminal end of a FACTS device connected to the same bus.
It must not be connected by a zero impedance line to another bus that violates any of
the above restrictions.
MIN
loss
Minimum converter losses; entered in kW. MIN
loss
= 0.0 by default.
SMAX Converter MVA rating; entered in MVA. SMAX = 0.0 to allow unlimited converter
MVA loading. SMAX = 0.0 by default.
IMAX Converter ac current rating; entered in amps. IMAX = 0.0 to allow unlimited
converter current loading. If a positive IMAX is specified, the base voltage assigned
to bus IBUS must be positive. IMAX = 0.0 by default.
PWF Power weighting factor fraction (0.0 < PWF < 1.0) used in reducing the active power
order and either the reactive power order (when MODE is 2) or the reactive power
limits (when MODE is 1) when the converter MVA or current rating is violated. When
PWF is 0.0, only the active power is reduced; when PWF is 1.0, only the reactive
power is reduced; otherwise, a weighted reduction of both active and reactive
power is applied. PWF = 1.0 by default.
MAXQ Reactive power upper limit; entered in Mvar. A positive value of reactive power indi-
cates reactive power flowing into the ac network from the converter; a negative
value of reactive power indicates reactive power withdrawn from the ac network.
Not used if MODE = 2. MAXQ = 9999.0 by default.
MINQ Reactive power lower limit; entered in Mvar. A positive value of reactive power indi-
cates reactive power flowing into the ac network from the converter; a negative
value of reactive power indicates reactive power withdrawn from the ac network.
Not used if MODE = 2. MINQ = -9999.0 by default.
REMOT Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of a remote Type 1 or 2 bus for which voltage is to be regulated by this
converter to the value specified by ACSET. If bus REMOT is other than a Type 1 or
2 bus, bus IBUS regulates its own voltage to the value specified by ACSET.
REMOT is entered as zero if the converter is to regulate its own voltage. Not used if
MODE = 2. REMOT = 0 by default.
RMPCT Percent of the total Mvar required to hold the voltage at the bus controlled by bus
IBUS that is to be contributed by this VSC; RMPCT must be positive. RMPCT is
needed only if REMOT specifies a valid remote bus and there is more than one
local or remote voltage controlling device (plant, switched shunt, FACTS device
shunt element, or VSC dc line converter) controlling the voltage at bus REMOT to a
setpoint, or REMOT is zero but bus IBUS is the controlled bus, local or remote, of
one or more other setpoint mode voltage controlling devices. Not used if MODE = 2.
RMPCT = 100.0 by default.
Siemens Energy, Inc., Power Technologies International 5-43
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-44 Siemens Energy, Inc., Power Technologies International
Otherwise, the impedances of the transformer windings assigned to the table are made sensitive to
off-nominal turns ratio.
The power flow case stores both a nominal and actual impedance for each transformer winding
impedance. The value of transformer impedance entered in activities READ, Reading Power Flow
Data Additions from the Terminal, RDCH, CHNG, or the transformer [Spreadsheets] is taken as the
nominal value of impedance. Each time the complex tap ratio of a transformer is changed, either
automatically by the power flow solution activities or manually by the user, and the transformer
winding has been assigned to an impedance correction table, actual transformer winding imped-
ance is redetermined if appropriate. First, the scaling factor is established from the appropriate table
by linear interpolation; then nominal impedance is multiplied by the scaling factor to determine
actual impedance. An appropriate message is printed any time the actual impedance is modified.
Figure 5-13. Typical Impedance Correction Factor Curve
Multi-Terminal DC Transmission Line Data
PSS
E is introduced by reading a
series of data records. Each set of multi-terminal dc line data records begins with a record that
defines the number of converters, number of dc buses and number of dc links as well as related
Siemens Energy, Inc., Power Technologies International 5-45
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-46 Siemens Energy, Inc., Power Technologies International
These data records are followed by NDCBS dc bus records of the following format:
IDC, IB, AREA, ZONE, 'DCNAME', IDC2, RGRND, OWNER
where:
ANGMX Nominal maximum ALPHA or GAMMA angle; entered in degrees. No default
allowed.
ANGMN Minimum steady-state ALPHA or GAMMA angle; entered in degrees. No default
allowed.
RC Commutating resistance per bridge; entered in ohms. No default allowed.
XC Commutating reactance per bridge; entered in ohms. No default allowed.
EBAS Primary base ac voltage; entered in kV. No default allowed.
TR Actual transformer ratio. TR = 1.0 by default.
TAP Tap setting. TAP = 1.0 by default.
TPMX Maximum tap setting. TPMX = 1.5 by default.
TPMN Minimum tap setting. TPMN = 0.51 by default.
TSTP Tap step; must be a positive number. TSTP = 0.00625 by default.
SETVL Converter setpoint. When IB is equal to VCONV or VCONVN, SETVL specifies the
scheduled dc voltage magnitude, entered in kV, across the converter. For other
converter buses, SETVL contains the converter current (amps) or power (MW)
demand; a positive value of SETVL indicates that bus IB is a rectifier, and a nega-
tive value indicates an inverter. No default allowed.
DCPF Converter participation factor. When the order at any rectifier in the multi-terminal
dc line is reduced, either to maximum current or margin, the orders at the remaining
converters on the same pole are modified according to their DCPFs to:
SETVL + (DCPF/SUM)-R
where SUM is the sum of the DCPFs at the unconstrained converters on the same
pole as the constrained rectifier, and R is the order reduction at the constrained
rectifier. DCPF = 1. by default.
MARG Rectifier margin entered in per unit of desired dc power or current. The converter
order reduced by this fraction, (1.-MARG)-SETVL, defines the minimum order for
this rectifier. MARG is used only at rectifiers. MARG = 0.0 by default.
CNVCOD Converter code. A positive value or zero must be entered if the converter is on the
positive pole of multi-terminal dc line I. A negative value must be entered for nega-
tive pole converters. CNVCOD = 1 by default.
IDC dc bus number (1 to NDCBS). The dc buses are used internally within each multi-
terminal dc line and must be numbered 1 through NDCBS. No default allowed.
Siemens Energy, Inc., Power Technologies International 5-47
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-48 Siemens Energy, Inc., Power Technologies International
Multi-Terminal DC Line Notes
The following points should be noted in specifying multi-terminal dc line data:
Conventional two-terminal (refer to Two-Terminal DC Transmission Line Data) and
multi-terminal dc lines are stored separately in PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-50 Siemens Energy, Inc., Power Technologies International
Multi-section line grouping data input is terminated with a record specifying a from bus number of
zero.
Multi-Section Line Example
The DUM
i
values on each record define the branches connecting bus I to bus J, and are entered
so as to trace the path from bus I to bus J. Specifically, for a multi-section line grouping consisting
of three line sections (and hence two dummy buses):
The path from I to J is defined by the following branches:
If this multi-section line grouping is to be assigned the line identifier &1, the corresponding multi-
section line grouping data record is given by:
I J &1 1 D1 D2
Multi-Section Line Notes
Up to 10 line sections (and hence 9 dummy buses) may be defined in each multi-section line
grouping. A branch may be a line section of at most one multi-section line grouping.
Each dummy bus must have exactly two branches connected to it, both of which must be members
of the same multi-section line grouping. A multi-section line dummy bus may not be a converter bus
of a dc transmission line. A FACTS control device may not be connected to a multi-section line
dummy bus.
The status of line sections and type codes of dummy buses are set such that the multi-section line
is treated as a single entity with regards to its service status.
When the multi-section line reporting option is enabled (refer to Section 3.3.3 and activity OPTN),
several power flow reporting activities such as POUT and LOUT do not tabulate conditions at multi-
MET Metered end flag:
<1 to designate bus I as the metered end
>2 to designate bus J as the metered end.
MET = 1 by default.
DUM
i
Bus numbers, or extended bus names enclosed in single quotes (refer to Extended
Bus Names), of the dummy buses connected by the branches that comprise this
multi-section line grouping. No defaults allowed.
From To Circuit
I D1 C1
D1 D2 C2
D2 J C3
C1 C2 C3
I J D1 D2
Siemens Energy, Inc., Power Technologies International 5-51
PSS
E user has the ability to assign each bus and load to an area (see Bus Data, Load Data,
Multi-Terminal DC Transmission Line Data, Area Interchange Data and Areas, Zones and Owners).
Furthermore, the user can schedule active power transfers between pairs of areas.
These active power transfers are specified in interarea transfer data records. Each interarea
transfer data record has the following format:
ARFROM, ARTO, TRID, PTRAN
where:
I Zone number (1 through 9999). No default allowed.
ZONAME Alphanumeric identifier assigned to zone I. ZONAME may be up to twelve charac-
ters and may contain any combination of blanks, uppercase letters, numbers and
special characters. ZONAME must be enclosed in single or double quotes if it
contains any blanks or special characters. ZONAME is twelve blanks by default.
ARFROM From area number (1 through 9999). No default allowed.
ARTO To area number (1 through 9999). No default allowed.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-52 Siemens Energy, Inc., Power Technologies International
Interarea transfer data input is terminated with a record specifying a from area number of zero.
Interarea Transfer Data Notes
Following the completion of interarea transfer data input, activity READ generates an alarm for any
area for which at least one interarea transfer is present and where the sum of transfers differs from
its desired net interchange, PDES (refer to Area Interchange Data).
Owner Data
PSS
E allows the user to identify which organization or utility actually owns a facility, a piece of
equipment or a load. Buses (ac and dc), loads, and FACTS devices have provision for an owner,
while machines, ac branches, and VSC dc lines can have up to four different owners. Ownership is
specified as part of the data records for these network elements (see Bus Data, Load Data, FACTS
Device Data, Generator Data, Non-Transformer Branch Data, Transformer Data, Voltage Source
Converter (VSC) DC Transmission Line Data and Multi-Terminal DC Transmission Line Data).
The use of the ownership attribute enables the user to develop reports and to check results on the
basis of ownership and, consequently, be highly specific when reporting and interpreting analytical
results.
Owner identifiers are specified in owner data records. Owner names may be specified either at the
time of raw data input or subsequently via activity CHNG or the owner [Spreadsheet]. Each owner
data record has the following format:
I, 'OWNAME'
where:
Owner data input is terminated with a record specifying an owner number of zero.
TRID Single-character (0 through 9 or A through Z) upper case interarea transfer identifier
used to distinguish among multiple transfers between areas ARFROM and ARTO.
TRID = 1 by default.
PTRAN MW comprising this transfer. A positive PTRAN indicates that area ARFROM is
selling to area ARTO. PTRAN = 0.0 by default.
I Owner number (1 through 9999). No default allowed.
OWNAME Alphanumeric identifier assigned to owner I. OWNAME may be up to twelve charac-
ters and may contain any combination of blanks, uppercase letters, numbers and
special characters. OWNAME must be enclosed in single or double quotes if it
contains any blanks or special characters. OWNAME is twelve blanks by default.
Siemens Energy, Inc., Power Technologies International 5-53
PSS
E accepts data for all of these devices through one generic set of data records. Each FACTS
device to be represented in PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-54 Siemens Energy, Inc., Power Technologies International
MODE Control mode:
For a STATCON (i.e., a FACTS devices with a shunt element but no series
element), J must be 0 and MODE must be either 0 or 1):
0 out-of-service (i.e., shunt link open)
1 shunt link operating.
For a FACTS device with a series element (i.e., J is not 0), MODE may be:
0 out-of-service (i.e., series and shunt links open)
1 series and shunt links operating.
2 series link bypassed (i.e., like a zero impedance line) and
shunt link operating as a STATCON.
3 series and shunt links operating with series link at constant
series impedance.
4 series and shunt links operating with series link at constant
series voltage.
5 master device of an IPFC with P and Q setpoints specified;
another FACTS device must be designated as the slave device
(i.e., its MODE is 6 or 8) of this IPFC.
6 slave device of an IPFC with P and Q setpoints specified;
the FACTS device specified in MNAME must be the master
device (i.e., its MODE is 5 or 7) of this IPFC. The Q setpoint is
ignored as the master device dictates the active power
exchanged between the two devices.
7 master device of an IPFC with constant series voltage setpoints
specified; another FACTS device must be designated as the slave
device (i.e., its MODE is 6 or 8) of this IPFC
8 slave device of an IPFC with constant series voltage setpoints
specified; the FACTS device specified in MNAME must be the
master device (i.e., its MODE is 5 or 7) of this IPFC. The complex
V
d
+ jV
q
setpoint is modified during power flow solutions to reflect
the active power exchange determined by the master device
MODE = 1 by default.
PDES Desired active power flow arriving at the terminal end bus; entered in MW.
PDES = 0.0 by default.
QDES Desired reactive power flow arriving at the terminal end bus; entered in MVAR.
QDES = 0.0 by default.
VSET Voltage setpoint at the sending end bus; entered in pu. VSET = 1.0 by default.
SHMX Maximum shunt current at the sending end bus; entered in MVA at unity voltage.
SHMX = 9999.0 by default.
TRMX Maximum bridge active power transfer; entered in MW. TRMX = 9999.0 by default.
VTMN Minimum voltage at the terminal end bus; entered in pu. VTMN = 0.9 by default.
VTMX Maximum voltage at the terminal end bus; entered in pu. VTMX = 1.1 by default.
Siemens Energy, Inc., Power Technologies International 5-55
PSS
Es FACTS device model contains a shunt element that is connected between the sending
end bus and ground, and a series element connected between the sending and terminal end buses.
A static synchronous condenser (STATCON) or static compensator (STATCOM) is modeled by a
FACTS device for which the terminal end bus is specified as zero (i.e., the series element is
disabled).
VSMX Maximum series voltage; entered in pu. VSMX = 1.0 by default.
IMX Maximum series current, or zero for no series current limit; entered in MVA at unity
voltage. IMX = 0.0 by default.
LINX Reactance of the dummy series element used during power flow solutions; entered
in pu. LINX = 0.05 by default.
RMPCT Percent of the total Mvar required to hold the voltage at the bus controlled by the
shunt element of this FACTS device that are to be contributed by this shunt
element; RMPCT must be positive. RMPCT is needed only if REMOT specifies a
valid remote bus and there is more than one local or remote voltage controlling
device (plant, switched shunt, FACTS device shunt element, or VSC dc line
converter) controlling the voltage at bus REMOT to a setpoint, or REMOT is zero
but bus I is the controlled bus, local or remote, of one or more other setpoint mode
voltage controlling devices. RMPCT = 100.0 by default.
OWNER Owner number (1 through 9999). OWNER = 1 by default.
SET1,
SET2
If MODE is 3, resistance and reactance respectively of the constant impedance,
entered in pu; if MODE is 4, the magnitude (in pu) and angle (in degrees) of the
constant series voltage with respect to the quantity indicated by VSREF; if MODE is
7 or 8, the real (V
d
) and imaginary (V
q
) components (in pu) of the constant series
voltage with respect to the quantity indicated by VSREF; for other values of MODE,
SET1 and SET2 are read, but not saved or used during power flow solutions.
SET1 = 0.0 and SET2 = 0.0 by default.
VSREF Series voltage reference code to indicate the series voltage reference of SET1 and
SET2 when MODE is 4, 7 or 8:
0 for sending end voltage
1 for series current.
VSREF = 0 by default.
REMOT Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of a remote Type 1 or 2 bus where voltage is to be regulated by the
shunt element of this FACTS device to the value specified by VSET. If bus REMOT
is other than a Type 1 or 2 bus, the shunt element regulates voltage at the sending
end bus to the value specified by VSET. REMOT is entered as zero if the shunt
element is to regulate voltage at the sending end bus and must be zero if the
sending end bus is a Type 3 (swing) bus. REMOT = 0 by default.
MNAME The name of the FACTS device that is the IPFC master device when this FACTS
device is the slave device of an IPFC (i.e., its MODE is specified as 6 or 8). MNAME
must be enclosed in single or double quotes if it contains any blanks or special char-
acters. MNAME is blank by default.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-56 Siemens Energy, Inc., Power Technologies International
A unified power flow controller (UPFC) has both the series and shunt elements active, and allows
for the exchange of active power between the two elements (i.e., TRMX is positive). A static
synchronous series compensator (SSSC) is modeled by setting both the maximum shunt current
limit (SHMX) and the maximum bridge active power transfer limit (TRMX) to zero (i.e., the shunt
element is disabled).
An Interline Power Flow Controller (IPFC) is modeled by using two series FACTS devices. One
device of this pair must be assigned as the IPFC master device by setting its control mode to 5 or
7; the other must be assigned as its companion IPFC slave device by setting its control mode to 6
or 8 and specifying the name of the master device in its MNAME. In an IPFC, both devices have a
series element but no shunt element. Therefore, both devices typically have SHMX set to zero, and
VSET of both devices is ignored. Conditions at the master device define the active power exchange
between the two devices. TRMX of the master device is set to the maximum active power transfer
between the two devices, and TRMX of the slave device is set to zero.
Figure 5-15 shows the PSS
E FACTS control device model with its various setpoints and limits.
Each FACTS sending end bus must be a Type 1 or 2 bus, and each terminal end bus must be a
Type 1 bus. Refer to Sections 6.3.15 and Section 6.3.17 for other topological restrictions and for
details on the handling of FACTS devices during the power flow solution activities.
Siemens Energy, Inc., Power Technologies International 5-57
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-58 Siemens Energy, Inc., Power Technologies International
Switched Shunt Data
Automatically switched shunt devices may be represented on a network bus.
The switched shunt elements at a bus may consist entirely of blocks of shunt reactors (each B
i
is a
negative quantity), entirely of blocks of capacitor banks (each B
i
is a positive quantity), or of both
reactors and capacitors.
Each network bus to be represented in PSS
E-32.0.
1 steps and blocks are switched on and off such that the next highest
(or lowest, as appropriate) total admittance is achieved.
ADJM = 0 by default.
STAT Initial switched shunt status of one for in-service and zero for out-of-service;
STAT = 1 by default.
VSWHI When MODSW is 1 or 2, the controlled voltage upper limit; entered in pu.
When MODSW is 3, 4, 5 or 6, the controlled reactive power range upper limit;
entered in pu of the total reactive power range of the controlled voltage controlling
device.
VSWHI is not used when MODSW is 0. VSWHI = 1.0 by default.
VSWLO When MODSW is 1 or 2, the controlled voltage lower limit; entered in pu.
When MODSW is 3, 4, 5 or 6, the controlled reactive power range lower limit;
entered in pu of the total reactive power range of the controlled voltage controlling
device.
VSWLO is not used when MODSW is 0. VSWLO = 1.0 by default.
SWREM Bus number, or extended bus name enclosed in single quotes (refer to Extended
Bus Names), of the bus where voltage or connected equipment reactive power
output is controlled by this switched shunt.
When MODSW is 1 or 2, SWREM is entered as 0 if the switched shunt is to regulate
its own voltage; otherwise, SWREM specifies the remote Type 1 or 2 bus where
voltage is to be regulated by this switched shunt
When MODSW is 3, SWREM specifies the Type 2 or 3 bus where plant reactive
power output is to be regulated by this switched shunt. Set SWREM to I if the
switched shunt and the plant that it controls are connected to the same bus.
When MODSW is 4, SWREM specifies the converter bus of a VSC dc line where
converter reactive power output is to be regulated by this switched shunt. Set
SWREM to I if the switched shunt and the VSC dc line converter that it controls are
connected to the same bus.
When MODSW is 5, SWREM specifies the remote bus to which the switched shunt
for which the admittance setting is to be regulated by this switched shunt is
connected.
SWREM is not used when MODSW is 0 or 6. SWREM = 0 by default.
RMPCT Percent of the total Mvar required to hold the voltage at the bus controlled by bus I
that are to be contributed by this switched shunt; RMPCT must be positive. RMPCT
is needed only if SWREM specifies a valid remote bus and there is more than one
local or remote voltage controlling device (plant, switched shunt, FACTS device
shunt element, or VSC dc line converter) controlling the voltage at bus SWREM to a
setpoint, or SWREM is zero but bus I is the controlled bus, local or remote, of one or
more other setpoint mode voltage controlling devices. Only used if MODSW = 1 or
2. RMPCT = 100.0 by default.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-60 Siemens Energy, Inc., Power Technologies International
Switched shunt data input is terminated with a record specifying a bus number of zero.
Switched Shunt Notes
BINIT needs to be set to its actual solved case value only when the network, as entered into the
working case via activity READ, is to be considered solved as read in, or when the device is to be
treated as locked (i.e., MODSW is set to zero or switched shunt adjustment is disabled during power
flow solutions).
The switched shunt elements at a bus may consist entirely of reactors (each B
i
is a negative quan-
tity) or entirely of capacitor banks (each B
i
is a positive quantity). In these cases, when ADJM is
zero, the shunt blocks are specified in the order in which they are switched on the bus; when ADJM
is one, the shunt blocks may be specified in any order.
The switched shunt devices at a bus may be comprised of a mixture of reactors and capacitors. In
these cases, when ADJM is zero, the reactor blocks are specified first in the order in which they are
switched on, followed by the capacitor blocks in the order in which they are switched on; when
ADJM is one, the reactor blocks are specified first in any order, followed by the capacitor blocks in
any order.
In specifying reactive power limits for setpoint mode voltage controlling switched shunts (i.e., those
with MODSW of 1 or 2), the use of a very narrow admittance range is discouraged. The Newton-
Raphson based power flow solutions require that the difference between the controlling equip-
ment's high and low reactive power limits be greater than 0.002 pu for all setpoint mode voltage
controlling equipment (0.2 Mvar on a 100 MVA system base). It is recommended that voltage
controlling switched shunts have admittance ranges substantially wider than this minimum permis-
sible range.
When MODSW is 3, 4, 5 or 6, VSWLO and VSWHI define a restricted band of the controlled
devices reactive power range. They are specified in pu of the total reactive power range of the
controlled device (i.e., the plant QMAX - QMIN when MODSW is 3, MAXQ - MINQ of a VSC dc line
converter when MODSW is 4, EN
i
B
i
EN
j
B
j
when MODSW is 5 where i are those switched shunt
blocks for which B
i
is positive and j are those for which B
i
is negative, and 2.*SHMX of the shunt
element of the FACTS device, reduced by the current corresponding to the bridge active power
transfer when a series element is present, when MODSW is 6). VSWLO must be greater than or
equal to 0.0 and less than VSWHI, and VSWHI must be less than or equal to 1.0. That is, the
following relationship must be honored:
0.0 < VSWLO < VSWHI < 1.0
The reactive power band for switched shunt control is calculated by applying VSWLO and VSWHI
to the reactive power band extremes of the controlled plant or VSC converter. For example, with
RMIDNT When MODSW is 4, the name of the VSC dc line where the converter bus is speci-
fied in SWREM. When MODSW is 6, the name of the FACTS device where the
shunt elements reactive output is to be controlled. RMIDNT is not used for other
values of MODSW. RMIDNT is a blank name by default.
BINIT Initial switched shunt admittance; entered in Mvar at unity voltage. BINIT = 0.0 by
default.
N
i
Number of steps for block i (0 < N
i
< 9). The first zero value of N
i
or B
i
is interpreted
as the end of the switched shunt blocks for bus I. N
i
= 0 by default.
B
i
Admittance increment for each of N
i
steps in block i; entered in Mvar at unity
voltage. B
i
= 0.0 by default.
Siemens Energy, Inc., Power Technologies International 5-61
PSS
E
3
2
.
0
R
e
a
d
i
n
g
P
o
w
e
r
F
l
o
w
R
a
w
D
a
t
a
i
n
t
o
t
h
e
W
o
r
k
i
n
g
C
a
s
e
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 5-16. Example Data Record for Combination of Switched Shunts
MODSW STAT ADMIN I
791 1 1 1
Siemens Energy, Inc., Power Technologies International 5-63
PSS
E release.
ReadSub Subsystem READ of a Power Flow Raw Data File in the format of the
PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-64 Siemens Energy, Inc., Power Technologies International
data arrays. Bus sequence numbers are assigned sequentially starting with 1 in the order in which
bus data records are read.
Plant and Machine Sequence Numbers
Each bus for which a generator data record is read is assigned a plant sequence number, which
defines the location of its plant-related generator data in the plant data arrays. Data for each plant
contains a machine sequence number assigned for each machine for which a generator data
record is read. This number defines the location of its machine-specific data in the machine data
arrays. Plant and machine sequence numbers are assigned sequentially starting with 1 in the order
in which generator data records are read. It is permissible to enter a generator data record for a bus
that was assigned a type code of 1 or 4 during bus data input. (Refer to Generator Data and activity
MCRE.)
Load Sequence Numbers
Each load introduced into PSS
E 32.0
Reading Power Flow Raw Data into the Working Case Program Operation Manual
5-66 Siemens Energy, Inc., Power Technologies International
1. Add only data from within the subsystem: all buses and their connected equipment in a
specified subsystem contained in the Power Flow Raw Data File are appended to the
working case.
2. Add only the tie branches connected to the subsystem: all branches in the Power Flow Raw
Data File for which both buses are in the working case and only one bus is in a specified
subsystem (ties) are appended to the working case.
3. Add subsystem data and its ties: all buses and their connected equipment in a specified
subsystem as described in (1), along with its ties as described in (2), are appended to the
working case.
An input data item may be used to enable a boundary bus identification option. When this option is
enabled, any in-service bus that is in the specified subsystem and connected to a bus that is not in
the working case may be identified as a boundary bus; the type code of each boundary bus is
changed from 1, 2, or 3 to 5, 6, or 7, respectively. Refer to activity EEQV for further discussion of
boundary buses.
When the subsystem to be processed is specified by voltage level, it is not possible to process
buses at two different voltage levels while omitting those buses at intervening levels. Multiple
executions of activity READ are required to accomplish this.
When appending tie branches to the working case, one (and only one) of the two subsystems that
are to be joined must be specified. Any branch contained in the Power Flow Raw Data File for which
the following conditions are met is appended to the working case:
Both buses are in the working case, regardless of whether they were placed there
during this execution of READ or were already there.
One of the buses is in the specified subsystem and the other is not.
There is not already a branch in the working case between the two buses with the same
circuit identifier or with circuit identifier 99.
This has the effect of joining the separate subsystems contained in the working case by adding all
tie branches running between them.
Data on an area interchange data record is added to the working case if either:
At least one data record for a bus or a load residing in the area was read during the
current execution of activity READ.
The area subsystem option was specified in selecting activity READ and the area was
one of those specified by the user.
Data on zone and owner records is handled using similar criteria.
Data on interarea transfer data records is added to the working case if both the from and to areas
satisfy the criteria above.
5.2.5 Reading Power Flow Raw Data Files Created by Previous Releases of
PSS
E
A Power Flow Raw Data File in the format required for a prior release of PSS
E is able to be
processed by activity READ. Both the standard and subsystem READ functions are able to handle
Power Flow Raw Data Files from as far back as PSS
E-15.
Siemens Energy, Inc., Power Technologies International 5-67
PSS
E
revision numbers corresponding to the various Power Flow Raw Data Files being used
in a study.
At PSS
E-31, a third data item containing the revision number of the release of PSS
E
to which the file format corresponds was added to the first data record (refer to Case
Identification Data). For files in the format required by PSS
E-30,
the user may add this revision number to the first record in the data file so that it con-
tains the first three data items of the current Power Flow Raw Data File:
IC, SBASE, REV
Thus, the use of this method requires that the REV data item be correctly specified.
From an input data item of the appropriate API routine
In this method, the old Power Flow Raw Data File does not require any editing. Rather,
the VERNUM input data item of the ReadRawVersion and ReadSubRawVersion API
routines is a character string designating the PSS
E GUI Users Guide, Section 6.3, Reading Power Flow Raw Data into the Working Case
PSS
E 32.0
Reading Power Flow Data Additions from the Terminal Program Operation Manual
5-68 Siemens Energy, Inc., Power Technologies International
5.3 Reading Power Flow Data Additions from the Terminal
Activity TREA
Activity TREA is special purpose version of activity READ available only in line mode. It is designed
for the purpose of adding a limited amount of equipment to the system contained in the working
case, with data records read from the dialog input device (the terminal keyboard, a Response File,
or an IPLAN program).
Run Line Mode Activity TREA - CLI
ACTIVITY?
>>TREA
ENTER BUS DATA
I, 'BUS NAME', BASKV, IDE, AREA, ZONE, OWNER, VM, VA
>>
Interrupt Control Codes
AB
Additional Information
PSS
E 32.0
Adding Machine Impedance Data Program Operation Manual
5-70 Siemens Energy, Inc., Power Technologies International
Data records may be entered in any order. Input is terminated with a record specifying an I
value of zero.
5.4.2 Operation of Activity MCRE
The MCRE API routine requires the following as input:
The name of the Machine Impedance Data File that is to be read.
A flag indicating how the status of new machines is to be set. These are machines that
are not in the working case at the time activity MCRE is selected, but are added
because of the presence of data records for them in the Machine Impedance Data File.
A flag indicating the treatment of machines for which no data record is specified and
that are at a bus with at least one machine for which a data record is specified.
As activity MCRE processes data records, If a record is encountered on which bus I is not in the
working case, if it does not have a generator (i.e., plant) slot assigned to it, or if an invalid machine
identifier is specified, an appropriate message is printed at the Progress device, the record is
ignored, and processing continues.
If, in attempting to add a machine to the machine data arrays, the maximum number of machines
or machine ownership specifications for which PSS
E 32.0
Adding Machine Impedance Data Program Operation Manual
5-72 Siemens Energy, Inc., Power Technologies International
The power split fractions are used in setting the machine power limits as well as the initial power
output of the machine. Note that the machine split fractions are not retained in the working case or
subsequently written Saved Case Files following termination of activity MCRE.
When a machine is added to the working case by activity MCRE, it inherits the ownership assign-
ment of the bus to which it is attached.
The introduction of multiple machines at a plant into the working case may be accomplished either
via activity MCRE or during the initial input of the network model into the PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-74 Siemens Energy, Inc., Power Technologies International
Figure 5-17. Sequence Data Input Structure
Siemens Energy, Inc., Power Technologies International 5-75
PSS
E working
case for all in-service machines at the bus. The positive sequence values are entered in positive
sequence generator impedance data records in the Sequence Data File. Each positive sequence
generator impedance data record has the following format:
I, ID, ZRPOS, ZXPOS
where:
During the initial input of sequence data (i.e., IC = 0 on the first data record), any machine for which
no data record of this category is entered has its positive sequence generator impedance, ZPOS
(i.e., ZRPOS + j ZXPOS), set equal to ZSORCE, the generator impedance entered in activities
READ, Reading Power Flow Data Additions from the Terminal, RDCH, and MCRE and used in
switching studies and dynamic simulation (refer to Generator Data).
In subsequent executions of activity RESQ (i.e., IC = 1 on the first data record), any machine for
which no data record of this category is entered has its positive sequence generator impedance
unchanged. Note that the generator positive sequence impedance entered in activity RESQ for fault
analysis purposes (ZPOS) is not necessarily the same as the generator impedance (ZSORCE)
used in dynamics, and that it does not overwrite ZSORCE. That is, the two different positive
sequence impedances are specified in the working case simultaneously at different locations.
IC = 0 Indicates the initial input of sequence data for the network contained in the working
case. All buses, generators, branches, switched shunts and fixed shunts for which
no data record is entered in a given category of data have the default values
assigned for those data items.
IC = 1 Indicates change case input of sequence data for the network contained in the
working case. All buses, generators, branches, switched shunts and fixed shunts for
which no data record is entered in a given category of data have those data items
unchanged; i.e., they are not set to the default values.
I Bus number; bus I must be present in the working case as a generator bus.
ID One- or two-character machine identifier of the machine at bus I for which the data
is specified by this record. ID = 1 by default.
ZRPOS Generator positive sequence resistance; entered in pu on machine base (i.e., on
MBASE base). No default is allowed.
ZXPOS Generator positive sequence reactance; entered in pu on machine base (i.e., on
MBASE base). No default is allowed.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-76 Siemens Energy, Inc., Power Technologies International
Positive sequence generator impedance data input is terminated with a record specifying a bus
number of zero.
Negative Sequence Generator Impedance Data
The impedance characterizing each generator in the negative sequence network is entered into the
working case in negative sequence generator impedance data records in the Sequence Data File.
Each negative sequence generator impedance data record has the following format:
I, ID, ZRNEG, ZXNEG
where:
During the initial input of sequence data (i.e., IC = 0 on the first data record), any machine for which
no data record of this category is entered has its negative sequence generator impedance, ZNEG
(i.e., ZRNEG + j ZXNEG), set equal to ZPOS, the positive sequence generator impedance (refer to
Positive Sequence Generator Impedance Data).
In subsequent executions of activity RESQ (i.e., IC = 1 on the first data record), any machine for
which no data record of this category is entered has its negative sequence generator impedance
unchanged.
Negative sequence generator impedance data input is terminated with a record specifying a bus
number of zero.
Zero Sequence Generator Impedance Data
The impedance characterizing each generator in the zero sequence network is entered into the
working case in zero sequence generator impedance data records in the Sequence Data File. Each
zero sequence generator impedance data record has the following format:
I, ID, RZERO, XZERO
where:
I Bus number; bus I must be present in the working case as a generator bus.
ID One- or two-character machine identifier of the machine at bus I for which the data
is specified by this record. ID = 1 by default.
ZRNEG Generator negative sequence resistance; entered in pu on machine base (i.e., on
MBASE base). No default is allowed.
ZXNEG Generator negative sequence reactance; entered in pu on machine base (i.e., on
MBASE base). No default is allowed.
I Bus number; bus I must be present in the working case as a generator bus.
ID One- or two-character machine identifier of the machine at bus I for which the data
is specified by this record. ID = 1 by default.
RZERO Generator zero sequence resistance; entered in pu on machine base (i.e., on
MBASE base). No default is allowed.
XZERO Generator zero sequence reactance; entered in pu on machine base (i.e., on
MBASE base). No default is allowed.
Siemens Energy, Inc., Power Technologies International 5-77
PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-78 Siemens Energy, Inc., Power Technologies International
Zero Sequence Shunt Load Data
Zero sequence shunt loads are entered into the working case in zero sequence shunt load data
records in the Sequence Data File. Each zero sequence shunt load data record has the following
format:
I, GZERO, BZERO
where:
For any bus where no such data record is specified, no shunt load component is represented in the
zero sequence. The zero sequence ground tie created by a grounded transformer winding is
automatically added to whatever zero sequence shunt load and fixed shunt is specified at the bus
when the transformer winding connection code data for the transformer is specified (refer to Zero
Sequence Transformer Data).
Zero sequence admittances corresponding to fixed bus shunts (refer to Fixed Bus Shunt Data) are
specified in the zero sequence fixed shunt data records (refer to Zero Sequence Fixed Shunt Data)
and therefore should not be included in the zero sequence shunt load admittance values.
Zero sequence shunt load data input is terminated with a record specifying a bus number of zero.
Zero Sequence Non-Transformer Branch Data
Zero sequence non-transformer branch parameters are entered into the working case in zero
sequence non-transformer branch data records in the Sequence Data File. Each zero sequence
branch data record has the following format:
I, J, ICKT, RLINZ, XLINZ, BCHZ, GI, BI, GJ, BJ
where:
I Bus number; bus I must be present in the working case.
GZERO Active component of zero sequence shunt load admittance to ground to be repre-
sented at the bus; entered in pu.
BZERO Reactive component of zero sequence shunt load admittance to ground to be repre-
sented at the bus; entered in pu.
I Bus number of one end of the branch.
J Bus number of the other end of the branch.
ICKT One- or two-character branch circuit identifier; a non-transformer branch with circuit
identifier ICKT between buses I and J must be in the working case. ICKT = 1 by
default.
RLINZ Zero sequence branch resistance; entered in pu on system base MVA and bus
voltage base. RLINZ = 0.0 by default.
XLINZ Zero sequence branch reactance; entered in pu on system base MVA and bus
voltage base. Any branch for which RLINZ and XLINZ are both 0.0 is treated as
open in the zero sequence network. XLINZ = 0.0 by default.
BCHZ Total zero sequence branch charging susceptance; entered in pu. BCHZ = 0.0 by
default.
Siemens Energy, Inc., Power Technologies International 5-79
PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-80 Siemens Energy, Inc., Power Technologies International
The following rules must be observed in specifying mutual impedance data:
The maximum number of zero sequence mutual couplings that may be entered at the
standard size levels of PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-82 Siemens Energy, Inc., Power Technologies International
CC Winding connection code indicating the connections and ground paths to be used in
modeling the transformer in the zero sequence network.
For a two-winding transformer, valid values are 1 through 9. They define the
following zero sequence connections that are shown in Figure 5-18.
1 series path, no ground path.
2 no series path, ground path on Winding 1 side.
3 no series path, ground path on Winding 2 side.
4 no series or ground paths.
5 series path, ground path on Winding 2 side (normally only used
as part of a three-winding transformer).
6 no series path, ground path on Winding 1 side, earthing transformer
on Winding 2 side.
7 no series path, earthing transformer on Winding 1 side, ground path
on Winding 2 side.
8 series path, ground path on each side.
9 series path on each side, ground path at the junction point of the two
series paths.
For a three-winding transformer, CC may be specified as a three digit number, each
digit of which is 1 through 7; the first digit applies to Winding 1, the second to
Winding 2, and the third to Winding 3, where the winding connections correspond to
the first seven two-winding transformer connections defined above and shown in
Figure 5-18.
Alternatively, several common zero sequence three-winding transformer connection
combinations may be specified using the single digit values 1 through 6. These
define the zero sequence transformer connections that are shown in Figure 5-19.
The following single digit three-winding connection codes are available, where the
connection codes of the three two-winding transformers comprising the three-
winding transformer are shown in parenthesis in winding number order:
1 series path in all three windings, Winding 1 ground path at the
star point bus (5-1-1).
2 series path in Windings 1 and 2, Winding 3 ground path at the
star point bus (1-1-3).
3 series path in Winding 2, ground paths from windings one and
three at the star point bus (3-1-3).
4 no series paths, ground paths from all three windings at the
star point bus (3-3-3).
5 series path in windings one and three, ground path at the
Winding 2 side bus (1-2-1).
6 series path in all three windings, no ground path (1-1-1).
Siemens Energy, Inc., Power Technologies International 5-83
PSS
E converts the
measured bus-to-bus impedances to winding impedances that are subsequently used in building
Section 5.5.3, Transformers in the Zero Sequence, includes examples of the proper
specification of CC and the remaining transformer data items for several types of
transformers.
CC = 4 by default.
RG, XG Zero sequence grounding impedance for an impedance grounded transformer,
entered in per unit on a system base MVA and bus voltage base.
For a two-winding transformer, ZG = RG + jXG is applied as shown in Figure 5-18 if
the connection code is 2, 3, 5, 6, 7, 8 or 9, and is ignored if the connection code is 1
or 4. PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-84 Siemens Energy, Inc., Power Technologies International
the network matrices. Activities LIST and EXAM tabulate both sets of positive sequence
impedances.
Recall that the service status of a three-winding transformer may be specified such that two of its
windings are in-service and the remaining winding is out-of-service (refer to Transformer Data).
Recall also that data for the three windings of a three-winding transformer is stored in the working
case as three two-winding transformers (refer to Three-Winding Transformer Notes). Ri + jXi is
stored with the two-winding transformer containing winding is data; RG + jXG is stored with the two-
winding transformer containing the data of the winding at which it is applied.
Placing one winding of a three-winding transformer out-of-service may require a change to the zero
sequence data of the two windings that remain in-service. As the fault analysis calculation functions
construct the zero sequence admittance matrix, when a three-winding transformer with one winding
out-of-service is encountered, all data pertaining to the out-of-service winding (i.e., pertaining to the
two-winding transformer containing the data of the out-of-service winding) is ignored. Thus, any
zero sequence series and ground paths resulting from the impedances and connection code of the
out-of-service winding are excluded from the zero sequence admittance matrix. It is the users
responsibility to ensure that the zero sequence impedances and connection codes of the two in-
service windings result in the appropriate zero sequence modeling of the transformer.
Specification of the transformer connection code along with the impedances entered here enables
the fault analysis activities to correctly model the zero sequence transformer connections, including
the ground ties and open series branch created by certain grounded transformer windings. If no
connection code is entered for a transformer, all windings are assumed to be open. Section 5.5.3,
Transformers in the Zero Sequence gives additional details on the treatment of transformers in the
zero sequence network, including examples of specifying data for several types of transformers.
During the initial input of sequence data (i.e., IC = 0 on the first data record), any transformer for
which no data record of this category is entered has it zero sequence winding impedance(s) set to
the same value(s) as its positive sequence winding impedance(s). In subsequent executions of
activity RESQ (i.e., IC = 1 on the first data record), any transformer for which no data record of this
category is entered has its zero sequence transformer data unchanged.
Zero sequence transformer data input is terminated with a record specifying a from bus number of
zero.
Siemens Energy, Inc., Power Technologies International 5-85
PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-86 Siemens Energy, Inc., Power Technologies International
Figure 5-23 (Cont). Two-Winding Transformer Zero Sequence Connections
Set: Zero Sequence Connection:
Winding 1 Winding 2
3.*Z
g2
CC = 5
RG + jXG = Z
g2
Z
t
0
R1 + jX1 = Z
t
0
Z
g
CC = 6
RG + jXG = Z
g
Z
t
0
R1 + jX1 = Z
t
0
CC = 7
RG + jXG = Z
g
Z
g
Z
t
0
R1 + jX1 = Z
t
0
CC = 8
RG + jXG = Z
g1
R2 + jX2 = Z
g2
R1 + jX1 = Z
t
0
Z
t
0
Z
g2
Z
g1
CC = 9
RG + jXG = Z
g
R2 + jX2 = Z
t2
R1 + jX1 = Z
t1
0
Z
t1
0
Z
g
Z
t2
0
t
1
:1
1:t
2
t
1
:1
1:t
2
1:t
2
t
1
:1
t
1
:1 1:t
2
Siemens Energy, Inc., Power Technologies International 5-87
PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-88 Siemens Energy, Inc., Power Technologies International
Figure 5-19 (Cont). Three-Winding Transformer Zero Sequence Connections
b. Zero Sequence, Connection Code = 2 (1-1-3)
Set: Zero Sequence Connections:
CC = 3
R1 + jX1 = Z
0
1
R2 + jX2 = Z
0
2
R3 + jX3 = Z
0
3
RG + jXG = 0.0 + j0.0
Z
1
0 Z
2
0
Z
3
0
1:t
2
c. Zero Sequence, Connection Code = 3 (3-1-3)
Set: Zero Sequence Connections:
CC = 2
R1 + jX1 = Z
0
1
R2 + jX2 = Z
0
2
R3 + jX3 = Z
0
3
Z
1
0
Z
2
0
Z
3
0
t
1
:1 1:t
2
Siemens Energy, Inc., Power Technologies International 5-89
PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-90 Siemens Energy, Inc., Power Technologies International
Figure 5-19 (Cont). Three-Winding Transformer Zero Sequence Connections
Zero Sequence Switched Shunt Data
Zero sequence shunt admittances for switched shunts are entered into the working case in zero
sequence switched shunt data records in the Sequence Data File. Each switched shunt data record
has the following format:
I, BZ1, BZ2, ... BZ8
where:
Data specified on zero sequence switched shunt data records must be coordinated with the corre-
sponding positive sequence data (refer to Switched Shunt Data). The number of blocks and the
number of steps in each block are taken from the positive sequence data.
I Bus number; bus I must be present in the working case with positive sequence
switched shunt data.
BZ
i
Zero sequence reactance increment for each of the steps in block i; entered in pu.
BZ
i
= 0.0 by default.
Set: Zero Sequence Connections:
CC = 6
R1 + jX1 = Z
0
1
R2 + jX2 = Z
0
2
R3 + jX3 = Z
0
3
Z
1
0
Z
2
0
Z
3
0
t
1
:1 1:t
2
1:t
3
f. Zero Sequence, Connection Code = 6 (1-1-1)
Siemens Energy, Inc., Power Technologies International 5-91
PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-92 Siemens Energy, Inc., Power Technologies International
As data records are read, a message is displayed at the Progress device at the start of each new
category of data.
Except for the change code parameter IC in the first data record read by activity RESQ, specifying
a data record with a Q in column one is used to indicate that no more data records are to be supplied
to activity RESQ.
When the fault analysis warning option is enabled (refer to Saved Case Specific Option Settings),
activity RESQ produces the following tabulations:
When IC is zero, a listing of all in-service machines at Type 2 and 3 buses for which no
negative sequence generator impedance is entered. The negative sequence generator
impedance, ZNEG, is set to the positive sequence value, ZPOS.
When IC is zero, a listing of all in-service machines at Type 2 and 3 buses for which no
zero sequence generator impedance is entered. The zero sequence generator imped-
ance, ZZERO, is set to the positive sequence value, ZPOS.
Each of these tabulations may be individually suppressed by entering the AB interrupt control code
(see Section 4.3, Interruption of PSS
E by the User).
5.5.3 Transformers in the Zero Sequence
The fault analysis activities of PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-94 Siemens Energy, Inc., Power Technologies International
For a wye grounded - delta with an earthing transformer two-winding transformer:
2
For a delta with an earthing transformer - wye grounded two-winding transformer:
For wye-grounded with a zig-zag transformer connection:
2
PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-96 Siemens Energy, Inc., Power Technologies International
For a wye grounded - wye grounded three phase core-type two-winding autotransformer solidly
grounded:
Z
20
Z
10
Z
30
P
S
1
2
Z
0
Z
g Z
g2
Set:
CC = 8
R2 + jX2 =
Z
10
Z
30
Z
10
+ Z
20
+ Z
30
RG + jXG =
Z
20
Z
30
Z
10
+ Z
20
+ Z
30
R1 + jX1 =
Z
10
Z
20
Z
10
+ Z
20
+ Z
30 1 2
1 2
Siemens Energy, Inc., Power Technologies International 5-97
PSS
E 32.0
Reading Sequence Data Program Operation Manual
5-98 Siemens Energy, Inc., Power Technologies International
For a delta - wye grounded - delta three-winding autotransformer:
For an autotransformer wye grounded - wye grounded - delta three-winding transformer:
Additional Information
PSS
E 32.0
Reading Transactions Raw Data Program Operation Manual
5-100 Siemens Energy, Inc., Power Technologies International
Transaction Events
Each transaction event consists of a single data record that assigns a set of transaction attributes,
followed by one or more data records that associate participating buses with the transaction event.
The set of transaction attributes are introduced using data records of the form:
ID, ISTAT, MAG, 'LABEL', IPR, CURT
where:
Each transaction attribute record is followed with a group of records that identify the buses partici-
pating in the transaction event. The bus participation records take the form:
I, LV, GV
where:
Negative data may be presented for load or generation values. The interpretation of the participating
bus load and generation values is a function of the participation flag, IPF, presented on the initial
data record. The consequence of the differing treatment is discussed in Section 5.6.3.
Participating bus data input is terminated with a record specifying a bus number of zero.
Transaction event data input is terminated with a record specifying a transaction event number of
zero.
ID Transaction event number. ID = 0 by default.
ISTAT Transaction event status:
0 for out-of-service.
1 for in-service.
ISTAT = 0 by default.
MAG Transaction event magnitude in MW. MAG = 0.0 by default.
LABEL Alphanumeric label assigned to the transaction event. The label may be up to
twenty four characters and must be enclosed in single quotes. LABEL may contain
any combination of blanks, uppercase letters, numbers and special characters.
LABEL is twenty four blanks by default.
IPR Transaction event priority. This integer value priority number is used to group trans-
actions into sets. IPR = 0 by default.
CURT Transaction event curtailment magnitude in MW. CURT = 0.0 by default.
I Bus number. I = 0 by default.
LV Participating bus load value. LV = 0.0 by default.
GV Participating bus generation value. GV = 0.0 by default.
Siemens Energy, Inc., Power Technologies International 5-101
PSS
E.
Activity REMM processes data records from the selected source input stream. REMM prints a
message each time that it starts processing a new category of data.
5.6.3 Implications of the Participation Flag
Each transaction event includes a magnitude and participating load and generation buses. The
participation flag, IPF, affects both the interpretation of the transaction event participating bus load
and generation values and the interpretation of a zero value transaction magnitude.
The transaction magnitude is apportioned among the participating buses, power injections at partic-
ipating buses with positive generation value or negative load value, and power demand at
participating buses with positive load value or negative generation value. The magnitude of power
injection or demand at each participating bus is in proportion to the transaction magnitude and the
bus participation factor, r:
where:
P
i
Active power injection (demand) at bus i in MW.
MAG Transaction event magnitude in MW.
r
i
Participating bus i participation factor.
Er Sum of participation factors for injection (demand) buses associated with the trans-
action event.
P
i
= MAG -
r
i
Er
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading Transactions Raw Data Program Operation Manual
5-102 Siemens Energy, Inc., Power Technologies International
When IPF = 0, the load and generation values are interpreted as fractions of bus total MW (load or
generation). The bus participation factors are then the product of these fractions with the total bus
load or generation as appropriate. Also when IPF = 0, a transaction magnitude value of zero indi-
cates that the transaction magnitude shall take a value equal to the sum of participating power
demand.
When IPF is non-zero (e.g., IPF = 1) the load and generation values are interpreted as participation
factors and no alternate interpretation is implied for a zero value transaction magnitude.
Activity REMM introduces the transaction data into working memory, but this data is not retained in
the working case. Transaction data is not restored to the working memory by use of activity CASE.
The transaction data makes reference to participating buses by bus number. These references are
not altered or affected by bus modifications made through program dialog. For example, if a trans-
action participating bus is eliminated from the working case by dialog with activity JOIN then the
participating bus reference persists in the working memory but is corrupt. The user should ensure
that transaction data which is consistent with the network model is introduced to working memory
before invoking any open access related procedures.
Additional Information
PSS
E
release.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Reading / Changing Power Flow Data Program Operation Manual
5-104 Siemens Energy, Inc., Power Technologies International
working case; data items omitted on the data record have their values unchanged in the working
case (specifically, they are not set to default values as in activity READ).
Activity RDCH prints a warning message at the Progress device if generators have been converted
(see Section 11.2, Converting Generators). After generators are converted, machine impedance
data (MBASE, ZSORCE, XTRAN, and GTAP; refer to Generator Data) must not be changed.
As data records are read, a message is displayed at the Progress device at the start of each new
category of data.
Before it has completed reading its input data, activity RDCH may be ended by entering the AB
interrupt control code (refer to Section 4.3, Interruption of PSS
E
Power Flow Raw Data input in the format required for a prior release of PSS
E is able to be
processed by activity RDCH. The RdchRawVersion API routine is able to handle Power Flow Raw
Data input from as far back as PSS
E to which
the format of the input records corresponds is specified as an input data item to RdchRawVersion.
Upon being presented with such a file, activity RDCH first converts the file from its original format
to the format required by the current release of PSS
E.
Additional Information
PSS
E GUI Users Guide, Section 6.4, Reading / Changing Power Flow Data
PSS
E 32.0
Changing Service Status and Power Flow Parametric Data Program Operation Manual
5-106 Siemens Energy, Inc., Power Technologies International
5.8 Changing Service Status and Power Flow Parametric Data
Activity CHNG
PSS
E permits the user to change all service status, control mode, and other parametric data asso-
ciated with equipment represented in the working case. The appropriate tool for changing working
case data is dependent upon the interface through which PSS
E is being operated.
In the GUI, the primary means of changing individual data items is the [Spreadsheet] (refer to PSS
E
GUI Users Guide, Chapter 2 Spreadsheet View). The [Spreadsheet] may also be used to add new
elements to the working case.
In line mode, the power flow data modification activity CHNG is the primary tool for making data
changes to the working case (refer to PSS
E
Application Program Interface (API) manual are used to change data associated with existing
elements in the working case (these routines may also be used to add new elements to the working
case).
In Response Files and IPLAN programs, activity CHNG and/or the data entry/changing API routines
may be used to change power flow data in the working case.
All of these methods modify the working case but do not affect any file. In particular, they do not
affect any Saved Case File or Power Flow Raw Data File. To have data changes incorporated into
a Saved Case File, activity SAVE must be executed following the implementation of changes in the
working case.
Change Data - GUI
Use [Spreadsheet]
Run Line Mode Activity CHNG - CLI
ACTIVITY?
>>CHNG
ENTER CHANGE CODE:
0 = EXIT ACTIVITY 1 = BUS DATA
2 = GENERATOR DATA 3 = BRANCH DATA
4 = 2 WINDING TRANSFORMER DATA 5 = AREA INTERCHANGE DATA
6 = TWO-TERMINAL DC LINE DATA 7 = SOLUTION PARAMETERS
8 = CASE HEADING 9 = SWITCHED SHUNT DATA
10 = IMPEDANCE CORRECTION TABLES 11 = MULTI-TERMINAL DC DATA
12 = ZONE NAMES 13 = INTER-AREA TRANSFER DATA
14 = OWNER NAMES 15 = MACHINE OWNERSHIP DATA
16 = BRANCH OWNERSHIP DATA 17 = FACTS CONTROL DEVICE DATA
18 = 3 WINDING TRANSFORMER DATA 19 = VSC DC LINE DATA
20 = FIXED BUS SHUNT DATA:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-107
PSS
E activ-
ities such as FNSL or POUT.
If branch status changes isolate a bus, the user must change the bus type code to 4. Activities
TREE and OUTS and the power flow solution network connectivity check option (refer to Saved
Case Specific Option Settings and activity SOLV) aid the user in identifying isolated buses and
islands.
When the specified branch is a member of a multi-section line grouping (refer to Multi-Section Line
Grouping Data), the same status change is automatically implemented for all branches in the multi-
section line. In addition, the bus type codes of the dummy buses are changed to:
The bus type codes of the endpoint buses of the multi-section line grouping are not changed in the
branch status processing. As with single section lines, it is the users responsibility to ensure that
branch statuses and bus type codes are coordinated.
When specifying a branch subject to branch data changes, if a multi-section line grouping is spec-
ified, (i.e., the circuit identifier has an ampersand as its first character; refer to Multi-Section Line
Grouping Data), the user may change the status (and metered end) of the specified multi-section
line grouping. Status changes are implemented as described in the preceding paragraph.
When changing the status of a three-winding transformer, status values of 0 through 4 are permitted
(refer to Transformer Data); the status flags of the three two-winding transformers that comprise the
three-winding transformer are set to the appropriate values. As with multi-section line groupings
and two terminal branches, the bus type codes of the endpoint buses of the three-winding trans-
former are not changed in the branch status processing.
FACTS control devices and dc transmission lines may be blocked in a similar manner. A value of
zero for MODE, the control mode flag, indicates a blocked FACTS device (refer to FACTS Device
Data). A value of zero for MDC, the control mode flag, indicates a blocked dc line (refer to Two-
Terminal DC Transmission Line Data, Multi-Terminal DC Transmission Line Data, and Voltage
Source Converter (VSC) DC Transmission Line Data).
The status of an individual machine at a generator bus may be modified by changing its status flag;
plant total power output and power limits are automatically updated following a change of machine
power or status. A plant may be taken out-of-service either by changing the status of all units at the
bus to zero or by changing the bus type code to 1 or 4 (this is the recommended approach because
4 When the branch is being removed from service.
1 If the branch is being placed in-service and the bus has no generator data associ-
ated with it.
2 If the branch is being placed in-service and the bus has generator data associated
with it. In this case, the individual machine status flags, which are not changed in
this status processing of multi-section lines, determine which machines are actually
returned to service.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Changing Service Status and Power Flow Parametric Data Program Operation Manual
5-108 Siemens Energy, Inc., Power Technologies International
power flow solution activities will run slightly faster). Conversely, for a machine to be treated as in-
service, both its status must have the value 1 and the bus type code must be either 2 or 3.
Similarly, the status of an individual load, fixed shunt, or switched shunt at a bus may be modified
by changing its status. For one of these elements to be treated as in-service, both its status must
have the value 1 and the bus type code must be either 1, 2 or 3. Thus, disconnecting the bus to
which it is connected (i.e., changing the bus type code to 4) also outages any load, fixed shunt, or
switched shunt connected to it; it is not necessary to set the device status to zero.
5.8.2 Solution Parameter Changes
The convergence tolerance used by activities SOLV and MSLV (TOL), as well as that of activities
TYSL and BKDY (TOLTY), specifies largest voltage magnitude change in per unit. In activities
FNSL, FDNS, NSOL, and INLF, the mismatch convergence tolerances TOLN and VCTOLQ specify
largest mismatch in MW and Mvar, and the controlled bus voltage error convergence tolerance,
VCTOLV, specifies largest voltage magnitude change in per unit. The blowup threshold (BLOWUP)
is in units of largest voltage magnitude change in per unit and angle change in radians.
5.8.3 Interarea Transfer Data Changes
When modifying interarea transfer data, changes in transfer MW may optionally be applied to the
desired area net interchange values of both the from and to areas (refer to Area Interchange Data).
The new desired net interchange of the from area is set to its old value plus the change in transfer
MW. Similarly, the to areas desired net interchange is set to its old value minus the transfer MW
change.
Additional Information
PSS
E provides a means by
which not only loads but also generation and fixed bus shunts can be scaled.
The load, generation and shunt scaling activity SCAL enables the user to uniformly increase or
decrease any or all of the following quantities for a specified grouping of loads, fixed shunts, and
machines:
Load active power.
Load reactive power.
Active component of fixed bus shunt admittance.
Positive reactive component of fixed bus shunt admittance (capacitors).
Negative reactive component of fixed bus shunt admittance (reactors).
Generator active power output (positive generation).
Motor active power output (negative generation).
The SCAL API routine includes the following among its inputs:
A designation of the subsystem in which the generation, load and/or shunt is to be pro-
cessed; refer to Section 4.8, Subsystem Selection.
The methods used to specify scaling targets.
The scaling targets.
A flag to either enforce or ignore machine active power limits.
Run Activity SCAL - GUI
Power Flow > Changing > Scale generation, load, shunt (SCAL)
[Scale Powerflow Data]
Run Line Mode Activity SCAL - CLI
ACTIVITY?
>>SCAL
ENTER UP TO 20 BUS NUMBERS
>>
Interrupt Control Codes
None
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Scaling Loads, Generators, and/or Shunts Program Operation Manual
5-110 Siemens Energy, Inc., Power Technologies International
5.9.1 Operation of Activity SCAL
The user specifies either that the entire working case is to be processed or that the generation, load
and/or shunt in a designated bus subsystem is to be processed. Any machine in the specified
subsystem where the active power output is outside of its active power limits generates an alarm.
The reactive components of in-service fixed bus shunts are separated into capacitors and reactors
(inductors), and different scaling may be applied to each category.
Any in-service machine in the subsystem being processed where the active power output is nega-
tive is treated as a motor. Motor totals are excluded from the generator totals; rather, motors are
handled separately and the user is able to apply different scaling to generators and motors. If no
motors are contained in the subsystem being processed, the motor tabulations are suppressed.
When scaling to new total powers, the following rule is applied in determining the individual bus,
load, or machine powers:
Details on the scaling of fixed shunts, loads, and generation are given in Sections 5.9.2,
Section 5.9.3 and Section 5.9.4, respectively.
Pre- and post-scaling subsystem totals are tabulated as in the following example:
PRESENT TOTALS:
LOAD-MW 3200.0 ( 3200.0 SCALABLE, 0.0 FIXED)
LOAD-MVAR 1950.0 ( 1950.0 SCALABLE, 0.0 FIXED)
GENERATION 3248.9
SHUNT-MW 0.0
REACTORS -900.0
CAPACITORS 550.0
NEW TOTALS:
LOAD-MW 3220.0 ( 3220.0 SCALABLE, 0.0 FIXED)
LOAD-MVAR 1962.2 ( 1962.2 SCALABLE, 0.0 FIXED)
GENERATION 3268.9
SHUNT-MW 0.0
REACTORS -900.0
CAPACITORS 550.0
5.9.2 Scaling Fixed Shunts
Shunt totals include only those fixed shunts at buses in the specified subsystem which would be
modeled during network solutions (i.e., in-service fixed bus shunts at non-Type 4 buses). Shunt
quantities are tabulated and scaled as nominal values (i.e., at unity voltage).
The reactive components of in-service fixed bus shunts are separated into capacitors and inductors,
and different scaling may be applied to each category.
Adjust the power such that, at each load, fixed shunt, or machine, the ratio of
individual load, fixed shunt, or machine power to the total power of all loads,
fixed shunts, or machines being processed remains unchanged.
Siemens Energy, Inc., Power Technologies International 5-111
PSS
E 32.0
Scaling Loads, Generators, and/or Shunts Program Operation Manual
5-112 Siemens Energy, Inc., Power Technologies International
When the entire working case is being processed by activity SCAL, all in-service generators in the
working case are processed.
When the subsystem being processed is selected only by bus, all in-service generators at sub-
system buses for which the Type code is 2 or 3 are included in the generator totals and subsequent
scaling.
When the subsystem being processed is selected only by base voltage level, activity SCAL pro-
cesses all in-service generators at each Type 2 or 3 bus where the base voltage falls within the
specified base voltage band.
When a single subsystem selection criterion of area or zone is used, each in-service generator con-
nected to a bus assigned to one of the areas or zones specified is processed (see Bus Data).
When the single subsystem selection criterion of owner is used, each such machine wholly or partly
owned by any of the owners specified is processed (see Generator Data). The owner assignments
of buses are not considered.
When multiple selection criteria are enabled, the area, zone, base voltage, and/or bus selection cri-
teria, if enabled, dictate those buses for which the machines are candidates for processing;
otherwise, all buses are candidates for processing. The owner selection criterion, if enabled, dic-
tates which machines at candidate buses are to be included; otherwise, all machines with positive
active power generation at candidate buses are included.
When active power limits are enforced, any active power limits of machines being scaled that are
negative are temporarily set to zero. When reducing the subsystems active power generation by a
large amount, this prevents any such machines from having their active power settings set to a
negative value as other machines are set at their lower active power limits. The active power limit
totals shown in the display of activity SCAL are calculated using these modified limits.
In scaling generation, it is useful to remember the following points:
Activity SCAL is not a dispatch activity; it merely scales the existing active power output
of in-service machines such that the ratio of machine to total power is retained.
Machine power limits are recognized only if the user selects that option.
If a system swing (Type 3) bus is in the subsystem being scaled, the working case
should be solved so that the swing power, which is included in the total generation, is
reasonable.
If the total generation is being changed by a large amount, the new generator outputs,
as set by activity SCAL, should be examined to verify that machines are set at realistic
operating points. Activities LIST, GENS, and GEOL are helpful for this purpose. (For
these situations, the unit commitment/economic dispatch activity, ECDI may be more
appropriate.)
5.9.5 Scaling Example
In this example, all active power load is scaled by + 2% while maintaining a constant P/Q ratio. No
scaling is be imposed on active power generation. Consequently, the swing bus will need to
generate the increased power as well any additional system losses.
Figure 5-20 shows the total loads, the swing bus power and the system losses in the savnw.sav
Saved Case File prior to scaling. That data includes the total real load (3,200 MW), the total gener-
ation real power (3,258.7 MW) and the total reactive power for bus connected reactors and
Siemens Energy, Inc., Power Technologies International 5-113
PSS
E 32.0
Electrically Disconnecting a Bus Program Operation Manual
5-114 Siemens Energy, Inc., Power Technologies International
5.10 Electrically Disconnecting a Bus
Activity DSCN
The bus disconnection activity DSCN automates the data changes required to electrically isolate a
bus.
The only input to the DSCN API routine is the number of the bus to be disconnected. If the specified
bus is not contained in the working case, an appropriate message is printed at the Alert device.
For each bus processed, its Type code is set to 4 and all ac branches, dc lines, and series FACTS
devices connected to the bus are set to out-of-service. The status flags of bus connected equipment
(e.g., loads, FACTS devices without a series element, etc.) is not changed by activity DSCN; they
are, however, treated as out-of-service because such elements are in-service only if the Type code
of the bus to which they are connected is 1, 2 or 3 (refer to Section 5.8.1, Equipment Status
Changes).
If the bus being processed is the endpoint bus of a multi-section line grouping (refer to Multi-Section
Line Grouping Data), the entire multi-section line grouping is removed from service; i.e., each line
section is set to out-of-service and each dummy bus has its type code set to 4.
Similarly, if the bus being processed is a dummy bus of a multi-section line grouping, the multi-
section line is removed from service (refer to Section 5.8.1, Equipment Status Changes).
If a three-winding transformer (refer to Transformer Data) is connected to the bus being processed,
all three windings of the transformer are removed from service.
For each bus disconnected, a summary of bus type code and branch status changes is printed at
the Progress device. Figure 5-22 shows an example in which five circuits have been removed from
service as a result of disconnecting a bus. This summary, however, does not list the bus connected
equipment that is taken out-of-service as a result of the setting of the bus Type code to 4.
Run Activity DSCN - GUI
Power Flow > Changing > Disconnect / Reconnect bus (DCSN/RECN)
[Disconnect / Reconnect Bus]
OPTION: Disconnect bus
Run Line Mode Activity DSCN - CLI
ACTIVITY?
>>DSCN
ENTER BUS NUMBER:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-115
PSS
E GUI Users Guide, Section 7.1, Changing Service Status and Power Flow Parametric Data
PSS
E 32.0
Electrically Reconnecting a Bus Program Operation Manual
5-116 Siemens Energy, Inc., Power Technologies International
5.11 Electrically Reconnecting a Bus
Activity RECN
The bus reconnection activity RECN automates the data changes required to electrically reconnect
a disconnected (i.e., Type 4) bus. That is, activity RECN is the logical inverse of activity DSCN.
The only input to the RECN API routine is the number of the bus to be reconnected. If the specified
bus is not contained in the working case, an appropriate message is printed at the Alert device.
For each bus processed, if its Type code is 4, it is set to 2 if there is a plant table entry assigned to
the bus or to 1 if no generator data is associated with the bus. Then all branches connected to the
bus for which the to bus is not a Type 4 bus are set to in-service. All two-terminal and multi-terminal
dc lines returned to service are placed in power control mode. All series FACTS devices returned
to service have their control modes set to a positive value as described below. A summary of bus
type code and branch status changes is printed at the Progress tab.
The status flags of bus connected equipment (e.g., loads, FACTS devices without a series element,
etc.) is not changed by activity RECN. If the bus had been disconnected by activity DSCN, they
retain the service status that they had before they were disconnected because DSCN did not
change their status flags (refer to Section 5.10, Electrically Disconnecting a Bus).
If the bus being processed is the endpoint bus of a multi-section line grouping (refer to Multi-Section
Line Grouping Data), the entire multi-section line grouping is returned to service as long as the Type
code of the other endpoint bus is not 4; i.e., each line section is set to in-service and each dummy
bus has its type code set to 1 (if there is no generator data for the dummy bus) or 2 (if there is a
generator slot for the dummy bus).
Similarly, if the bus being processed is a dummy bus of a multi-section line grouping, the multi-
section line is set to in-service as long as the Type codes of neither of the two end point buses is 4
(refer to Section 5.8.1, Equipment Status Changes).
If a three-winding transformer (refer to Transformer Data) is connected to the bus being processed,
all three windings of the transformer are set to in-service as long as the Type codes of neither of the
other two buses connected to the transformer is 4; otherwise, the three-winding transformer
remains out-of-service.
Run Activity RECN - GUI
Power Flow > Changing > Disconnect / Reconnect bus (DCSN/RECN)
[Disconnect / Reconnect Bus]
OPTION: Connect bus
Run Line Mode Activity RECN - CLI
ACTIVITY?
>>RECN
ENTER BUS NUMBER:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-117
PSS
E 32.0
Removing Specified Buses and Connected Equipment Program Operation Manual
5-118 Siemens Energy, Inc., Power Technologies International
5.12 Removing Specified Buses and Connected Equipment
Activity EXTR
The bus removal activity EXTR removes subsystem buses and all equipment connected to them
from the working case, regardless of their service status. Because EXTR irrevocably deletes data
from the working case, it is strongly recommended that a Saved Case File of the working case be
made with activity SAVE prior to using activity EXTR.
The EXTR API routine includes the following among its inputs:
A designation of the subsystem from which buses and their connected equipment are
to be deleted; refer to Section 4.8, Subsystem Selection.
An option to remove generator table entries for out-of-service plants. When enabled,
this option results in the removal of plant table entries for Type 1 buses (i.e., buses at
which the plant is currently out-of-service). The proper selection for this option is
dependent upon the application at hand. When activity EXTR is being used to set up
the working case in preparation for building an equivalent of a subsystem contained
within it, the usual procedure is to enable this option. For other applications, it is often
desirable to retain these plant table allocations if the machines may subsequently be
returned to service.
An option to change the type codes of boundary buses. When enabled, this option
results in adding the value 4 to the bus type codes of boundary buses, which are
retained in the working case following the processing of activity EXTR. A boundary bus
is defined as a bus that is retained in the working case that is connected to a bus that
is deleted. The normal procedure is to disable this option unless some advanced equiv-
alencing operation is to be applied to the resultant working case.
Activity EXTR rebuilds all data arrays in the working case, compacting them to eliminate holes
created by the deleted equipment. New bus sequence numbers, generator sequence numbers, and
so on are assigned.
A three-winding transformer is removed if any of the buses it connects are removed.
A dc transmission line is removed if any of the buses designated as its converter station buses are
deleted.
Run Activity EXTR - GUI
Power Flow > Changing > Delete network elements (PURG/EXTR)
[Delete Buses and Outaged Network Elements]
OPTION: Remove Buses from Case
Run Line Mode Activity EXTR - CLI
ACTIVITY?
>>EXTR
ENTER UP TO 20 BUS NUMBERS
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-119
PSS
E 32.0
Deleting Equipment Program Operation Manual
5-120 Siemens Energy, Inc., Power Technologies International
5.13 Deleting Equipment
Activity PURG
The equipment removal activity PURG deletes designated equipment items from the working case.
Activity PURG may be used to remove either individually specified equipment items or all outaged
items of a specified equipment category that are contained in a specified subsystem of the working
case.
Because PURG irrevocably deletes data from the working case, it is strongly recommended that
a Saved Case File of the working case be made with activity SAVE prior to using activity PURG.
5.13.1 Removing Individual Equipment Items
In the GUI, the primary means of deleting individual equipment items is the [Spreadsheet] (refer to
PSS
E Appli-
cation Program Interface (API) manual are used to remove individual items from the working case.
In Response Files and IPLAN programs, activity PURG,SINGLE and/or the equipment removal API
routines may be used to delete individual items from the working case.
In removing multi-section line groupings, the branches and dummy buses that are members of a
deleted multi-section line grouping are not removed from the working case; only the definition of the
grouping is deleted.
5.13.2 Removing Outaged Equipment in a Subsystem
Activity PURG may be used to remove from the working case all outaged equipment of a desig-
nated equipment category connected to buses within a specified subsystem.
The PURG API routine includes the following among its inputs:
A designation of the subsystem from which out-of-service equipment is to be deleted;
refer to Section 4.8, Subsystem Selection.
An integer indicating the type of equipment to be removed. The following equipment
types are allowed:
- ac branches (non-transformer branches and two-winding transformers)
- Three-winding transformers
- Loads
- Machines
- Plants
- Fixed bus shunts
- Switched shunts
- FACTS devices
- Two-terminal dc lines
- Multi-terminal dc lines
- VSC dc lines
An integer indicating the treatment of out-of-service tie branches to other subsystems.
Such branches may either be kept in the working case or deleted.
When the entire working case is selected for processing, all out-of-service elements of the selected
category are deleted, and the out-of-service tie branches option is ignored.
Otherwise, the area, zone, and/or owner assignments of buses are used to determine which equip-
ment items are to be processed when subsystem selection by area, zone, and/or owner is enabled.
The owner assignments of machines, ac branches, three-winding transformers, and FACTS
devices, and the area, zone, and owner assignments of loads, are not considered.
The option indicating the treatment of outaged subsystem ties applies in the processing of ac
branches, dc lines, FACTS devices, and three-winding transformers. When choosing to remove
out-of-service ties, any outaged branch with at least one bus in the specified subsystem is deleted.
Otherwise, a branch is deleted only if all buses connected by the branch are in the specified
subsystem. In the case of multi-terminal dc lines, only the ac converter buses are considered in
determining if all buses are in the specified subsystem; specifically, the area, zone, and owner
assignments of the dc buses are not considered.
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Deleting Equipment Program Operation Manual
5-122 Siemens Energy, Inc., Power Technologies International
Each deleted item is reported at the Progress device. As the processing of an equipment category
is completed, the number of items of that category that were deleted is tabulated.
Activity PURG deletes subsystem equipment items as follows:
5.13.3 Example of Activity PURG
Figure 5-23 displays the output of activity PURG for ac branches.
Figure 5-23. Purging the Branches Data Category
5.13.4 Application Notes
The user must understand the difference between the use of activity PURG and the changing of the
service status of an equipment item as may be done in activity CHNG (refer to Sections 5.8.1 and
C.7.1) or the [Spreadsheet]. Changing the service status flag simply indicates that the equipment
item is to be ignored during PSS
E GUI Users Guide, Section 7.8, Removing Buses and Connected Equipment
PSS
E Command Line Interface (CLI) Users Guide, Section 4.9, Deleting Equipment
PSS
E 32.0
Joining Buses Program Operation Manual
5-124 Siemens Energy, Inc., Power Technologies International
5.14 Joining Buses
Activity JOIN
The bus joining activity JOIN enables the user to combine pairs of buses, retaining the identity of
one of the two buses. It is intended primarily to bolt together buses that are connected by a low
impedance jumper branch. However, activity JOIN allows any pair of buses to be joined together,
regardless of the impedance of any connecting branches or whether there is a branch between
them at all.
The JOIN API routine includes the following among its inputs:
The number of the bus to be retained.
The number of the bus to be joined to the retained bus; this bus is removed from the
working case.
An integer indicating the treatment of non-zero line shunts on branches and magne-
tizing admittance on transformers that connect the specified buses; these series
elements are removed from the working case. Line shunts of deleted in-service
branches may be handled using one of the following methods:
- They are added to the retained bus as a fixed bus shunt with the identifier LS; if a
shunt with the identifier LS already exists at either of the buses, an available iden-
tifier is assigned.
- They are neglected.
5.14.1 Operation of Activity JOIN
The following conditions generate an alarm at the Alert device and the buses are not joined:
Either of the specified buses is not contained in the working case.
The resulting retained bus would have more machines, loads, or fixed shunts than are
able to be accommodated with unique identifiers.
Either of the buses has a type code of 4 or greater.
The two buses are connected by a three-winding transformer.
Run Activity JOIN - GUI
Power Flow > Changing > Join buses (JOIN)
[Join Buses]
Run Line Mode Activity JOIN - CLI
ACTIVITY?
>>JOIN
ENTER 1 TO ADD LINE SHUNTS OF DELETED
IN-SERVICE BRANCHES TO RETAINED BUS SHUNT:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-125
PSS
E 32.0
Joining Buses Program Operation Manual
5-126 Siemens Energy, Inc., Power Technologies International
Redefined if the topology change results in a valid multi-section line grouping.
Deleted if the redefined grouping violates any of the requirements for multi-section line
groupings (refer to Multi-Section Line Grouping Data).
If sequence data is contained in the working case (refer to RESQ), it is handled appropriately,
including the rerouting or removal of zero sequence mutuals. If the option to move line shunts of
deleted branches to the retained bus is enabled, such zero sequence line shunts are added to the
zero sequence shunt load of the retained bus (refer to Zero Sequence Shunt Load Data). Zero
sequence switched shunts are treated in the same manner as they are in the positive sequence.
5.14.2 Example Progress Output
Figure 5-24. Join Buses Summary Report on Relocation of Load
The example summary report (Figure 5-24) indicates that the load on Bus 3008, with identifier 1,
was moved to bus 154 and its identifier changed to 3 so as to avoid conflict with two existing loads
on that bus.
Additional Information
PSS
E Command Line Interface (CLI) Users Guide, Section 4.4, Joining Buses
PSS
E 32.0
Splitting Buses Program Operation Manual
5-128 Siemens Energy, Inc., Power Technologies International
Loads.
Fixed bus shunts (available only from the GUI; when running activity SPLT in line mode,
any fixed shunts connected to the bus being split remain there).
Switched shunt.
Ac branches.
If the original bus is a dummy bus of a multi-section line grouping, the multi-section line grouping is
either:
Redefined if exactly one of the two branches connected to the original bus is rerouted
to the new bus.
Deleted if neither or both are rerouted to the new bus.
The new bus is given a type code of 1 (or 2 or 3 if generation is moved to it) and the jumper branch
between the original bus and the new bus is set to in-service unless the new bus becomes a dummy
bus of an out-of-service multi-section line grouping; in this case, the bus type code is set to 4 and
the jumper branch is set to out-of-service.
If sequence data is contained in the working case (refer to RESQ), it is handled appropriately,
including the rerouting of zero sequence mutuals. Branches introduced by activity SPLT have their
zero sequence impedances set to j0.0001.
After they have been created with activity SPLT, the data associated with the new bus and branch
may be modified with activity CHNG or with the [Spreadsheet] (and with activity SQCH if sequence
data is contained in the working case) just as any other bus and branch in the working case.
5.15.2 Example of Activity SPLT
Using the savnw.sav Saved Case File, bus 3003 can be split and circuit 2 from bus 3005 reassigned
to the new bus 3020. In the example, the option to move circuit 2 from bus 3005 to the new bus has
been selected. A summary of the changes is shown in the Progress tab (Figure 5-25).
Figure 5-25. Output Report Summary for Bus Split
Siemens Energy, Inc., Power Technologies International 5-129
PSS
E Command Line Interface (CLI) Users Guide, Section 4.5, Splitting Buses
PSS
E 32.0
Tapping a Line Program Operation Manual
5-130 Siemens Energy, Inc., Power Technologies International
5.16 Tapping a Line
Activity LTAP
The line tapping activity LTAP enables the user to introduce a new bus into the working case at a
designated location along a specified ac branch. Any non-transformer branch may be tapped with
activity LTAP.
The LTAP API routine includes the following among its inputs:
The two buses connected by the branch to be tapped.
The circuit identifier of the branch to be tapped.
The location of the new bus relative to the first bus specified in per unit of total line
length.
The number to be assigned to the new bus; the bus number specified must not already
be assigned to another bus in the working case.
The name to be assigned to the new bus.
The base voltage to be assigned to the new bus.
If the specified branch is not contained in the working case, or if it is a transformer, an appropriate
error message is printed.
The new bus is then introduced into the working case and assigned to the area, zone, and owner
of the nearer bus. The new bus is given a bus type code of 1 if the branch being tapped is in-service,
or a type code of 4 if the branch is out-of-service. It is made a passive node with no load, generation,
or shunt elements.
The original branch is split into two branches: one from the original from bus to the new bus, and
one from the new bus to the original to bus, both with appropriate fractions of the original branch
impedance and charging. Line connected shunts on the new branches are set such that the line
connected shunts from the original branch remain at the original from and to bus. Circuit identifiers,
ratings, status, metered ends, and ownership follow from the original branch.
If the original branch was a member of a multi-section line grouping, the groupings definition is
modified to include the two new branches in place of the original branch.
Run Activity LTAP - GUI
Power Flow > Changing > Tap line (LTAP)
[Tap Line]
Run Line Mode Activity LTAP - CLI
ACTIVITY?
>>LTAP
ENTER FROM BUS, TO BUS, CIRCUIT IDENTIFIER
(FROM BUS = 0 TO EXIT):
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-131
PSS
E Command Line Interface (CLI) Users Guide, Section 4.6, Tapping a Line
PSS
E 32.0
Changing Equipment Identifiers Program Operation Manual
5-132 Siemens Energy, Inc., Power Technologies International
5.17 Changing Equipment Identifiers
Activity MBID
PSS
E permits the user to change the following types of alphanumeric identifiers associated with
equipment represented in the working case:
Machine, load, and fixed shunt identifiers.
Circuit identifiers of non-transformer branches, two-winding transformers, three-
winding transformers, and multi-section line groupings.
Two-terminal, multi-terminal, and VSC dc line names.
FACTS device names.
Inter-area transfer identifiers.
The appropriate tool for changing working case equipment identifiers is dependent upon the inter-
face through which PSS
E is being operated.
In the GUI, the primary means of changing individual data items is the [Spreadsheet] (refer to PSS
E
GUI Users Guide, Chapter 2 Spreadsheet View).
In line mode, the equipment identifier modification activity MBID is the primary tool for making these
data changes to the working case (refer to PSS
E Application Program Interface (API) manual are used to change data associated with
existing elements in the working case.
In Response Files and IPLAN programs, activity MBID and/or the identifier changing API routines
may be used to change equipment identifiers in the working case.
Each non-transformer branch is categorized as either a normal branch, a breaker, or a switch by
the first character of its circuit identifier: an at sign ( @ ) for a breaker, an asterisk ( - ) for a switch,
Change Equipment Identifiers - GUI
Use [Spreadsheet]
Run Line Mode Activity MBID - CLI
ACTIVITY?
>>MBID
ENTER 0 TO EXIT 1 FOR MACHINE ID's
2 FOR CIRCUIT ID's 3 FOR INTER-AREA TRANSFER ID's
4 FOR LOAD ID's 5 FOR TWO-TERMINAL DC LINE NAMES
6 FOR MULTI-TERM DC LINE NAMES 7 FOR FACTS DEVICE NAMES
8 FOR 3-WINDING TRANSFORMER IDs 9 FOR VSC DC LINE NAMES
10 FOR SHUNT ID's:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-133
PSS
E 32.0
Moving Equipment Program Operation Manual
5-134 Siemens Energy, Inc., Power Technologies International
5.18 Moving Equipment
Activity MOVE
The equipment transferal activity MOVE allows the user to move specified fixed shunts, switched
shunts, loads, machines, and plants from one bus to another. It also provides for connecting the far
end of specified branches and one winding of a three-winding transformer to different to buses.
5.18.1 Operation of Activity MOVE
Following the selection of the equipment category, the user specifies the equipment to be moved
and the bus to which the equipment is to be transferred. Following each move, a summary of the
action taken is printed at the Progress device.
When rerouting a branch for which the circuit identifier matches that of a branch already existing
between the from bus and the new to bus, the existing branch keeps its original identifier and the
user specifies a new identifier for the rerouted branch. A similar approach is used in the rerouting
of three-winding transformers.
The terms from and to in this network element moving process are not related to the
transformer data attributes that relate to windings and taps. Here the from and to are
used merely to select branches, recognizing that the to end is the end that will be relocated.
For three-winding transformers there are three buses to be selected; the from, to and a third
bus. It is the third bus that can be moved.
In rerouting branches and three-winding transformers, if the new to bus is a dummy bus of a multi-
section line grouping, that line grouping is deleted because the new to bus will have three branches
connected to it following the rerouting.
If the branch being rerouted is a member of a multi-section line grouping and the original to bus is
a dummy bus, the multi-section line grouping is deleted; if the original to bus is an endpoint bus of
the multi-section line grouping, either the grouping is deleted if the new to bus is the other endpoint
bus, or the grouping is redefined.
Run Activity MOVE - GUI
Power Flow > Changing > Move network elements (MOVE)
[Move Network Elements]
Run Line Mode Activity MOVE - CLI
ACTIVITY?
>>MOVE
EQUIPMENT ITEMS WHICH MAY BE MOVED ARE:
1 = AC LINES 2 = SWITCHED SHUNTS
3 = MACHINES 4 = PLANTS
5 = INDIVIDUAL LOADS 6 = ALL LOADS AT A BUS
7 = THREE-WINDING TRANSFORMERS
8 = INDIVIDUAL FIXED SHUNTS 9 = ALL FIXED SHUNTS AT A BUS
ENTER EQUIPMENT CATEGORY CODE:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-135
PSS
E 32.0
Moving Equipment Program Operation Manual
5-136 Siemens Energy, Inc., Power Technologies International
The example displays the savnw.sav Saved Case File. The 500 kV line from bus 151, which termi-
nates at bus 201 will be moved to terminate at bus 202. A summary of the moving action is printed
at the Progress device (Figure 5-27).
Figure 5-27. Branch Move Output Report
5.18.2 Application Notes
Activity MOVE does not check that the working case is in the form required by the power flow solu-
tion activities. The user is advised to use activities such as TREE (to check for islands and system
swing bus specification) and CNTB and EXAM (to check the control parameters of merged plants
and switched shunts) before attempting to solve the modified case.
Additional Information
PSS
E Command Line Interface (CLI) Users Guide, Section 4.7, Moving Equipment
PSS
E activities.
The RNFI API routine includes the following among its inputs:
The type of data file to be processed.
The name of the auxiliary data input file to be processed.
The name of the output file reflecting the bus renumbering.
The name of a Bus Renumbering Translation Data File.
5.19.1 Bus Renumbering Translation Data File
During the bus renumbering process, PSS
E 32.0
Renumbering Buses in Auxiliary Files Program Operation Manual
5-138 Siemens Energy, Inc., Power Technologies International
will be immediately available for use with the renumbered case. The alternative is to allow the
reconstructed file to be printed at the Report device for previewing purposes.
The same file may not be specified for both the auxiliary data input file and the output data file.
That is, activity RNFI is not able to replace the input file with a modified version of the file that
reflects the bus renumbering.
Activity RNFI is able to process the following auxiliary data files:
Sequence Data File (used by activity RESQ)
Drawing Coordinate Data File (obsolete one-line diagram definition format file that may
be imported into the [Diagram] view)
Dynamics Data File (used by activity DYRE)
Machine Impedance Data File (used by activity MCRE)
Economic Dispatch Data File (used by activity ECDI)
Inertia and Governor Response Data File (used by activity INLF)
Breaker Duty Data File (used by activity BKDY)
Fault Specification Data File (used by activity BKDY)
Fault Control Data (used by activity ASCC and IECS)
Machine Capability Curve Data (used by activity GCAP)
Load Throwover Data File (used by the various ac contingency calculation functions,
the P-V Analysis function, and the Q-V analysis function)
ANSI Fault Specification Data File (used by activity ANSI)
Subsystem Description Data File (used by activities DFAX and RANK)
Monitored Element Data File (used by activities DFAX and RANK)
Contingency Description Data File (used by activity DFAX)
Tripping Element Data File (used by Multi-Level AC Contingency Solution)
In processing Dynamics Data Files, data records for User-Written Models are copied to the desti-
nation file without change.
As with all files used in the course of a PSS
E GUI Users Guide, Section 7.17, Renumbering Buses in Auxiliary Data Files
PSS
E 32.0
Changing Area Assignments Program Operation Manual
5-140 Siemens Energy, Inc., Power Technologies International
Following the reassignment process, activity ARNM logs the following occurrences and conditions
at the Progress device (refer to Section 4.4):
The destination area has a blank name and activity ARNM assigns to it the area name
from an area that has a non-blank name and that is emptied during the area reassign-
ment process.
An area no longer has any equipment assigned to it.
An area slack bus is transferred from its original area to an area for which the area slack
bus is specified as zero; the transferred bus is designated the area slack bus of the des-
tination area.
An area slack bus is moved from its original area and its original area still contains other
buses.
Then activity ARNM lists the number of buses and/or loads transferred to the destination area, and
the total number of buses, loads, and dc buses now assigned to the area. If no changes were made,
activity ARNM displays:
NO AREA ASSIGNMENT CHANGES FOR SELECTED SUBSYSTEM
Before activity ARNM ends, any area containing a Type 3 (system swing) bus is checked to ensure
that either that bus or no bus is designated as the area slack bus. Any violations are reported.
5.20.2 Application Notes
When all buses are removed from an area, its desired interchange and interarea transfers are
added to those of the new area. In the case of conflicting interarea transfer identifiers, those trans-
fers originally in the new area keep their original identifiers and new identifiers are assigned to the
reassigned interarea transfers. All changes to interarea transfer identifiers are reported at the
Progress device (refer to Section 4.4). Alternative identifier settings may be implemented via
activity MBID either before or after the execution of activity ARNM.
The user should check the desired area interchanges and interarea transfers whenever only some
of the buses in an area are moved from one area to another.
Activity ARNM does not change the area assignments of dc buses internal to multi-terminal dc lines
(refer to Multi-Terminal DC Transmission Line Data).
5.20.3 Example of Activity ARNM
Suppose that all buses in Area 5 (WORLD) in the savnw.sav Saved Case File needed to be reas-
signed to Area 2 (LIGHTCO). Before the reassignment it is useful to examine the Area information.
Figure 5-28 shows via the [Spreadsheet] View that there are three areas, the total of the three desired
interchanges is 0.0, and the net desired interchanges result from four inter-area transactions, all
involving Area 1 (FLAPCO).
Siemens Energy, Inc., Power Technologies International 5-141
PSS
E 32.0
Changing Area Assignments Program Operation Manual
5-142 Siemens Energy, Inc., Power Technologies International
Figure 5-30. Modified Area and Inter-Area Information following Reassignment
Additional Information
Areas, Zones and Owners
PSS
E 32.0
Changing Owner Assignments Program Operation Manual
5-144 Siemens Energy, Inc., Power Technologies International
Then activity OWNM then lists the number of buses, loads, machines, branches, FACTS devices,
and/or VSC dc lines transferred to the destination owner, and the total number of buses, loads,
machines, branches, dc buses, FACTS devices, and VSC dc lines now assigned to the owner (see
Figure 5-31). If no changes were made, activity OWNM displays:
NO OWNER ASSIGNMENT CHANGES FOR SELECTED SUBSYSTEM
Figure 5-31. Example Output Report of Owner Reassignment
5.21.2 Application Notes
To determine if an equipment item is processed in subsystem mode, for any active attribute (e.g.,
area), if the equipment item possesses the attribute (e.g., loads have an area attribute), it is used;
otherwise (e.g., machines do not have an area attribute), the corresponding attribute of the bus is
used.
When reassigning ownership for machines, branches, and VSC dc lines previously designated as
having multiple owners, each ownership block is assigned to the new owner unless subsystem
specification by owner is enabled. When using subsystem specification by owner, only those owner-
ship blocks previously assigned to the specified owners are reassigned.
When reassigning ownership for FACTS devices, FACTS devices with no terminal bus specified
(e.g., a STATCON) are not candidates for processing when using series element renumbering
option 2 (subsystem tie branches). Series FACTS devices are processed using the same criteria as
ac branches and VSC dc lines (only subsystem branches, only subsystem ties, or both subsystem
branches and ties).
Activity OWNM does not change the owner assignments of dc buses internal to multi-terminal dc
lines (refer to Multi-Terminal DC Transmission Line Data).
Additional Information
Areas, Zones and Owners
PSS
E 32.0
Changing Zone Assignments Program Operation Manual
5-146 Siemens Energy, Inc., Power Technologies International
The destination zone has a blank name and activity ZONM assigns to it the zone name
from a zone that has a non-blank name and that is emptied during the zone reassign-
ment process.
A zone no longer has any equipment assigned to it.
Then activity ZONM lists the number of buses and/or loads transferred to the destination zone, and
the total number of buses, loads, and dc buses now assigned to the zone. If no changes were made,
activity ZONM displays:
NO ZONE ASSIGNMENT CHANGES FOR SELECTED SUBSYSTEM
5.22.2 Application Notes
Activity ZONM does not change the zone assignments of dc buses internal to multi-terminal dc lines
(refer to Multi-Terminal DC Transmission Line Data).
Additional Information
Areas, Zones and Owners
PSS
E 32.0
Modifying Resistances of Non-Transformer Branches Program Operation Manual
5-148 Siemens Energy, Inc., Power Technologies International
When multiple subsystem selection criteria are enabled, the area, zone, and/or base voltage selec-
tion criteria, if enabled, determine those buses whose connected in-service non-transformer
branches are candidates for processing; otherwise, all buses are candidate buses. The owner
selection criterion, if enabled, determines which such branches at candidate buses are to be
processed; otherwise, all such branches at candidate buses are processed.
Activity MODR reports the number of branches where resistances have been modified at the
Progress device.
5.23.2 Application Notes
Activity MODR modifies branch resistances according to the formula:
where:
Refer to Section 7.6 of the PSS
E does not
remember which branches have been modified and which retain their original impedances. After
branch resistances have been modified by activity MODR, care should be exercised in selecting
activity MODR again so that branch resistances are not inadvertently modified twice. Unless the
user is aware of the basis for the initial calculation of branch resistances, the fine tuning of branch
resistances by activity MODR should not be applied.
Note again that it is recommended that the working case be preserved in a Saved Case File
prior to selecting activity MODR.
R
o
Is the initial branch resistance.
RATE
n
Is the specified branch rating (RATEA, RATEB or RATEC).
PERCENT Is the specified base loading percentage.
SCALE Is the specified scaling factor.
MVA Is the larger of the MVA flows at the two ends of branch.
Additional Information
PSS
E 32.0
Changing Sequence Data Program Operation Manual
5-150 Siemens Energy, Inc., Power Technologies International
5.25 Changing Sequence Data
Activity SQCH
The sequence data modification activity SQCH allows the user to make changes to the various
sequence data arrays in the working case. The appropriate tool for changing working case data is
dependent upon the interface through which PSS
E is being operated.
In the GUI, the primary means of changing individual data items is the [Spreadsheet] (refer to PSS
E
GUI Users Guide, Chapter 2 Spreadsheet View). The [Spreadsheet] may also be used to add new
zero sequence mutual elements to the working case.
In line mode, the sequence data modification activity SQCH is the primary tool for making sequence
data changes to the working case (refer to PSS
E
Application Program Interface (API) manual are used to change data associated with existing
elements in the working case (the SEQ_MUTUAL_DATA routine may also be used to add new zero
sequence mutuals to the working case). The name of each of the API routines associated with
sequence data starts with SEQ_.
In Response Files and IPLAN programs, activity SQCH and/or the data entry/changing API routines
may be used to change sequence data in the working case.
Activity SQCH allows access to the following items of data:
Zero and negative sequence shunt load elements. Note that the ground paths corre-
sponding to fixed shunt elements are not included as part of the zero and negative
sequence shunt load elements (refer to Zero Sequence Fixed Shunt Data). In the case
of zero sequence shunt loads, note that the ground ties created by grounded trans-
former windings are not included as part of the shunt load elements (refer to Zero
Sequence Shunt Load Data and Section 5.5.3, Transformers in the Zero Sequence).
Note also that care is required in manipulating exceptional (i.e., non-zero) negative
sequence shunt loads (refer to Negative Sequence Shunt Load Data). In particular,
when changing the positive sequence loading at a bus (with activity CHNG or the
Change Sequence Data - GUI
Use [Spreadsheet]
Run Line Mode Activity SQCH - CLI
ACTIVITY?
>>SQCH
ENTER CHANGE CODE:
0 = EXIT ACTIVITY 1 = BUS SHUNT LOADS (ZERO & NEG SEQS)
2 = GENERATOR IMPEDANCES 3 = ZERO SEQ NONTRANSFORMER BRANCH DATA
4 = ZERO SEQ SWITCHED SHUNTS 5 = ZERO SEQ 2 WINDING TRANSFORMER DATA
6 = ZERO SEQ 3 WINDING TRANSFORMER DATA 7 = ZERO SEQ FIXED SHUNTS:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-151
PSS
E Command Line Interface (CLI) Users Guide, Section 4.14, Changing Sequence Data
See also: Section 5.5, Reading Sequence Data
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Checking Branch Parameters Program Operation Manual
5-152 Siemens Energy, Inc., Power Technologies International
5.26 Checking Branch Parameters
Activity BRCH
The branch parameter checking activity BRCH tabulates those branches where impedances or
other characteristics are such that they may be detrimental to the rate of convergence of one or
more of the power flow solution activities (refer to SOLV, MSLV, FNSL, NSOL, FDNS, INLF, and
ACCC).
The BRCH API routine includes the following among its inputs:
A designation of the subsystem in which branch parameters are to be checked; refer
to Section 4.8, Subsystem Selection.
The selection of one or more checks to be performed.
Threshold or limits values used by several of the checks.
5.26.1 Branch Parameter Checks Available
Table 5-1 describes the branch parameter checks that can be enabled in activity BRCH. For those
checks that use a limit or threshold value, the default value is listed.
Run Activity BRCH - GUI
Power Flow > Check Data > Branch parameters (BRCH)
[Check Branch Parameters]
Run Line Mode Activity BRCH - CLI
ACTIVITY?
>>BRCH
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Table 5-1. Branch Parameter Data Check Options
Data Check
Default Limit
or Threshold
Value Description
Small Reactance 0.0005 pu
Any branch where reactance magnitude is less than threshold value
will be listed. Very small impedance branches not being treated as zero
impedance lines may result in a slowing of the rate of convergence of
the power flow solution activities, and their inability to reach the default
convergence tolerances.
Siemens Energy, Inc., Power Technologies International 5-153
PSS
E 32.0
Checking Branch Parameters Program Operation Manual
5-154 Siemens Energy, Inc., Power Technologies International
When branches are reported by activity BRCH, this does not necessarily mean that their data is
incorrect. Rather, it indicates the potential for difficulties in obtaining a power flow solution which
converges to the specified tolerances.
5.26.2 Operation of Activity BRCH
The user specifies either that the entire working case is to be processed, or that branch data checks
are to be performed for branches that are connected to at least one bus in the specified subsystem.
When a subsystem is being processed and ownership is the only selection criterion, each branch
wholly or partly owned by any of the owners specified is included in subsequent checks (refer to
Non-Transformer Branch Data and Transformer Data). The owner assignments of the branchs
endpoint buses are not considered.
When one or more of the other subsystem selection criteria are enabled, the bus, area, zone, and/or
base voltage selection criteria, if enabled, determine those buses whose connected branches are
candidates for processing; otherwise, all buses are candidate buses. The owner selection criterion,
if enabled, determines which such branches at candidate buses are to be processed; otherwise, all
such branches at candidate buses are processed.
For each of the checks, the report contains the from bus and to bus identifiers and areas, and the
circuit identifier, impedance, charging, and status of each branch tabulated. For the parallel trans-
former and high and low tap ratio checks, the Winding 1 tap ratio and phase shift angle and the
Winding 2 tap ratio are printed in place of the line charging; in the parallel transformer check, trans-
Parallel
Transformers
n.a.
Activity BRCH scans parallel branches between pairs of buses and
generates an alarm for:
Non-transformer and transformer branches in parallel.
Parallel two-winding transformers with different Winding 1
complex tap ratios.
Parallel two-winding transformers with different Winding 2 tap
ratios.
Parallel two-winding transformers with their Winding 1/Winding 2
side relationship reversed.
As in the reactance ratio check, buses connected by zero impedance
lines are treated as the same bus. Transformers listed in this check
have an F or T following the Winding 1 tap ratio to indicate the from bus
or to bus as the Winding 1 side bus.
High Tap Ratio 1.1 Any transformer branch for which the tap ratio of any winding is beyond
the specified limit is tabulated. Transformers listed in this check have an
F or T following the Winding 1 tap ratio to indicate the from bus or to bus
as the Winding 1 side bus.
Low Tap Ratio 0.9
Missing Zero
Sequence
Impedance
n.a.
Branches with a zero sequence impedance of (0.0 + j 0.0) are listed.
This test is bypassed if sequence data is not contained in the working
case.
Table 5-1. Branch Parameter Data Check Options (Cont.)
Data Check
Default Limit
or Threshold
Value Description
Siemens Energy, Inc., Power Technologies International 5-155
PSS
E 32.0
Check for Islands Without a Swing Bus Program Operation Manual
5-156 Siemens Energy, Inc., Power Technologies International
5.27 Check for Islands Without a Swing Bus
Activity TREE
The network continuity checking activity TREE enables the user to identify buses not connected
back to a Type 3 (swing) bus through the in-service ac network. It also tabulates in-service branches
connected to Type 4 (disconnected) buses. Each swingless island may optionally be disconnected.
The TREE API routine includes the following among its inputs:
A flag indicating the calculation phase to be performed during this call of the TREE API
routine:
- Initialization and check for the presence of a swingless island.
- Process the previously detected island as indicated by another input value; then
check for the presence of another swingless island.
An option describing the handling of the previously detected swingless island.
5.27.1 Operation of Activity TREE
The report produced by activity TREE first lists any Type 4 bus with one or more in-service branches
connected to it. Such error conditions usually result from manually isolating a bus by changing its
bus type code and the branch status flags to the appropriate values (with activity CHNG or in the
[Spreadsheet] view) but overlooking one or more branches connected to it. This error may be avoided
by using activity DSCN to electrically disconnect a bus.
Activity TREE then tabulates all Type 3 buses in the working case, followed by a listing of buses
that do not have a type code of 4 and are not looped back to a swing bus. These buses are grouped
by island, and, within each island, in ascending bus number (using the numbers output option) or
alphabetical (using the names output option) order. The tabulation of each island is followed by a
summary of the number of buses and plants in the island along with total island load, shunt, gener-
ation, and var limits.
The tabulations of activity TREE are printed at the Progress device (refer to Section 4.4).
For each swingless island detected in the working case, user input is required to select one of the
following actions:
Disconnect this island, then check for another swingless island.
Leave this island unchanged and check for another swingless island.
Run Activity TREE - GUI
Power Flow > Check Data > Buses not in swing bus tree (TREE)
Run Line Mode Activity TREE - CLI
ACTIVITY?
>>TREE
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 5-157
PSS
E GUI Users Guide, Section 12.4, Check for Islands Without a Swing Bus
PSS
E 32.0
Checking/Changing Controlled Bus Scheduled Voltage Program Operation Manual
5-158 Siemens Energy, Inc., Power Technologies International
5.28 Checking/Changing Controlled Bus Scheduled Voltage
Activity CNTB
The bus scheduled voltage checking activity CNTB tabulates the voltage setpoints and desired
voltage bands of voltage controlling equipment in the working case, and, optionally, allows the user
to specify new scheduled voltages. It also performs certain checks on voltage controlling buses that
are not themselves voltage controlled buses. It may be instructed to process all such buses, or only
those with suspect or conflicting voltage schedules or other errors.
The CNTB API routine includes the following among its inputs:
A designation of the subsystem in which the voltage controlled buses are to be pro-
cessed; refer to Section 4.8, Subsystem Selection.
A flag indicating the calculation phase to be performed during this call of the CNTB API
routine:
- Initialization.
- Voltage setpoint change for a voltage controlled bus.
- Voltage band change for a load drop compensating transformer.
In the initialization phase, the following control flags are specified:
- Process either all voltage controlled and voltage controlling buses in the specified
subsystem, or only those with apparent conflicting voltage objective data or other
errors.
- Report only, or allow scheduled voltage changes.
- Process either all subsystem controlling elements and controlled buses, or only in-
service elements.
In the voltage setoint change phase, the following are specified:
- A flag to indicate either no change for this voltage setpoint, or that a change is to
be implemented.
- When a change is to be implemented, the new voltage setpoint value.
Run Activity CNTB - GUI
Power Flow > Check Data > Check / Change controled bus scheduled voltages (CNTB)
[Check / Change Controlled Bus Scheduled Voltages]
Run Line Mode Activity CNTB - CLI
ACTIVITY?
>>CNTB
ENTER 0 TO INCLUDE ALL ELEMENTS, 1 FOR IN-SERVICE ELEMENTS ONLY:
>>
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 5-159
PSS
E 32.0
Checking/Changing Controlled Bus Scheduled Voltage Program Operation Manual
5-160 Siemens Energy, Inc., Power Technologies International
Generation at a remote bus, which is controlling the voltage at this bus. The type code
of the remote generator bus is printed in the STATUS column.
A switched shunt at the bus itself, if it is not remotely controlling the voltage at some
other bus or the reactive power output of some other voltage controlling device. The
control mode of the switched shunt is printed in the STATUS column.
A switched shunt at a remote bus, which is controlling the voltage at this bus. The type
code of the bus to which the switched shunt is connected and the control mode of the
switched shunt are printed in the STATUS column.
A FACTS device connected to the bus. The devices control mode is printed in the
STATUS column.
A FACTS device at a remote bus, which is controlling the voltage at this bus. The type
code of the bus to which the sending end bus of the FACTS device is connected and
the devices control mode are printed in the STATUS column.
A converter of a VSC dc line connected to the bus itself, if the converter is in ac voltage
control mode and is not remotely controlling the voltage at some other bus. The VSC
dc lines control mode (MDC) and the converters dc control code (TYPE) are printed
in the STATUS column.
A converter of a VSC dc line connected to a remote bus, if the converter is in ac voltage
control mode and is remotely controlling the voltage at this bus. The type code of the
converter bus, the VSC dc lines control mode (MDC), and the converters dc control
code (TYPE) are printed in the STATUS column.
A voltage controlling transformer without load drop compensation. For two-winding
transformers, transformer status is printed; for three-winding transformers, winding
status is printed in the STATUS column.
For each such equipment, the desired voltage setpoint or voltage band, as appropriate, is tabulated.
Activity CNTB lists any suspect voltage control specifications.
Then, if the voltage schedule changing option was selected, the user has the option of specifying a
new scheduled voltage. If a new value is entered, the control parameters are modified accordingly.
For those devices controlling to a voltage band, the band retains its previous voltage spread with
the designated voltage as the midpoint. These data changes are then echoed for verification.
Each voltage controlling transformer with load drop compensation (refer to Transformer Data and
Voltage Control) for which the controlled bus is being processed is then listed, along with the
compensated voltage it would sense and its voltage limits. If the voltage schedule changing option
was selected, the user then has the option of specifying a new voltage band for each such
transformer.
5.28.2 Application Notes
Buses connected together by zero impedance lines (refer to Zero Impedance Lines) are treated as
the same bus. Controlling equipment, along with any error and warning messages, apply to the
combined bus. In interactive mode, each group of buses connected together by zero impedance
lines that has at least one of the buses in the specified subsystem is tabulated once, even if more
than one of its buses is in the specified subsystem. In reporting mode, each such bus is reported in
its usual position in the bus collating sequence.
Siemens Energy, Inc., Power Technologies International 5-161
PSS
E GUI Users Guide, Section 12.2, Checking/Changing Controlled Bus Scheduled Voltage
PSS
E 32.0
Checking/Changing Transformer Adjustment Data Program Operation Manual
5-162 Siemens Energy, Inc., Power Technologies International
5.29 Checking/Changing Transformer Adjustment Data
Activity TPCH
The controlling transformer parameter checking activity TPCH performs several checks on the
adjustment data (refer to Transformer Data) associated with voltage and flow controlling
transformers.
The TPCH API routine includes the following among its inputs:
A flag indicating the calculation phase to be performed during this call of the CNTB API
routine:
- Initialization.
- Perform the selected check of transformer adjustment data.
- Modify adjustment data of transformers failing the current check.
- Exit TPCH.
In the initialization phase, the following is specified:
- A designation of the subsystem in which regulating transformers are to be pro-
cessed; refer to Section 4.8, Subsystem Selection.
In the data checking phase, the following are specified:
- A flag to indicate the type of data check to be performed.
- The threshold value to be used in the specified data check.
In the adjustment data modification phase, the following are specified:
- For tests which can modify either tap steps or voltage bands, a flag to indicate
which of these are to be modified.
- For tests for which both voltage controlling and Mvar controlling transformers were
tablulated, a flag to indicate which types of transformers are to have their data
modified:
both types
only voltage controlling transformers
Run Activity TPCH - GUI
Power Flow > Check Data > Check / Change transformer adjustment data (TPCH)
[Check / Change Transformer Adjustment Data]
Run Line Mode Activity TPCH - CLI
ACTIVITY?
>>TPCH
ENTER UP TO 20 BUS NUMBERS
>>
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 5-163
PSS
E 32.0
Checking/Changing Transformer Adjustment Data Program Operation Manual
5-164 Siemens Energy, Inc., Power Technologies International
Two-winding transformers are listed in the report with their Winding 1 bus as the from bus and with
their Winding 2 bus as the to bus. Three-winding transformers are listed in the report with their
controlling winding bus as the from bus and with their transformer name and winding number as the
to bus. The table is ordered in ascending numerical (using the numbers output option) or alphabet-
ical (using the names option) order by from bus, and, for each from bus, in ascending order by to
bus and circuit identifier, with two-winding transformers first followed by three-winding transformers.
The number of controlling transformer windings failing the check is also reported.
For the tap ratio step increment tests, if any transformers are found failing the test, the user may
elect to modify the steps, and therefore the number of tap positions, of these transformers. If this
option is enabled and there are both voltage and Mvar controlling transformers listed, the user may
have both types changed, only the voltage controlling transformers changed, or only the Mvar
controlling transformers changed to a specified new tap step. From the specified tap step and the
ratio limits of each such transformer, a new value for the number of tap positions is determined.
The remaining checks of activity TPCH are handled in a similar manner. The check for voltage band
less than two tap steps provides for modification of either the voltage band (widened to two tap
steps) or the number of tap positions (increased such that each tap step is no more than half of the
voltage band) of each voltage controlling transformer tabulated.
The tests of the voltage band of voltage controlling transformers against a user specified threshold
provide for the modification of the voltage band of each listed transformer to a specified new band.
For each transformer that has its voltage band adjusted, its voltage limits are set such that the
midpoint of its band is unchanged.
The test of the flow band of MW or Mvar controlling transformers against a user specified threshold
provide for the modification of the flow band of each listed transformer to a specified new band. If
this option is enabled and there are both MW and Mvar controlling transformers listed, the user may
have both types changed, only the MW controlling transformers changed, or only the Mvar control-
ling transformers changed to a specified new flow band. For each transformer that has its flow band
adjusted, its flow limits are set such that the midpoint of its band is unchanged.
As an example use of this function, assume we need to check the controlling Flow band for all MW
controlling transformers in the savnw.sav Saved Case File. Use a threshold Flow band of 5.0 MW.
The result of this example check shows one power controlling transformer with a Flow band of 10
MW compared to the threshold check of 5.0 MW (see Figure 5-32).
Figure 5-32. Results of Example Transformer Flow Band Check
5.29.2 Application Notes
Transformers that control dc line quantities are excluded from the parameter checking of activity
TPCH.
When transformers are reported by activity TPCH, this does not necessarily mean that their
data is incorrect.
Siemens Energy, Inc., Power Technologies International 5-165
PSS
E 32.0
Changing Adjustment Enable Flags of Transformers Program Operation Manual
5-166 Siemens Energy, Inc., Power Technologies International
5.30 Changing Adjustment Enable Flags of Transformers
Activity TFLG
The transformer adjustment enable flag setting activity TFLG allows the user to either enable or
disable the adjustment status of all automatically adjustable transformer windings contained in the
subsystem specified by the user.
The TFLG API routine includes the following among its inputs:
A designation of the subsystem in which the adjustment enable flag of adjustable trans-
former windings is to be modified; refer to Section 4.8, Subsystem Selection.
The setting to be assigned to the adjustment enable flags of subsystem adjustable
transformer windings (refer to Transformer Data).
5.30.1 Operation of Activity TFLG
The user specifies either that the entire working case is to be processed, or that adjustable trans-
formers connecting buses in a designated bus subsystem are to be processed (refer to
Section 4.8).
When a subsystem is being processed and ownership is the only selection criterion, each adjust-
able transformer wholly or partly owned by any of the owners specified has its adjustment enable
flag set to the designated value. The owner assignments of the transformers endpoint buses are
not considered.
When one or more of the other subsystem selection criteria are enabled, the bus, area, zone, and/or
base voltage selection criteria, if enabled, determine those buses whose connected transformer
branches are candidates for processing; otherwise, all buses are candidate buses. The owner
selection criterion, if enabled, determines which controlling transforfmers connecting candidate
buses are to be processed; otherwise, all controlling transformers connecting candidate buses are
processed.
Note that only transformers connecting subsystem buses are processed by activity TFLG;
transformers that are ties from the specified subsystem are not processed.
Activity TFLG sets the sign of the adjustment control mode of those adjustable transformer windings
being processed to the appropriate value.
Run Activity TFLG - GUI
Power Flow > Changing > Transformer adjustment flags (TFLG)...
[Transformer Adjustment Flags]
Run Line Mode Activity TFLG - CLI
ACTIVITY?
>>TFLG
ENTER 0 TO DISABLE, 1 TO ENABLE:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-167
PSS
E GUI Users Guide, Section 7.10, Changing Adjustment Enable Flags of Transformers
PSS
E 32.0
Performing Unit Commitment and Economic Dispatch Program Operation Manual
5-168 Siemens Energy, Inc., Power Technologies International
5.31 Performing Unit Commitment and Economic Dispatch
Activity ECDI
The unit commitment/economic dispatch activity ECDI places machines in a specified subsystem
in- or out-of-service to satisfy a given subsystem minimum capacity. The in-service machines in the
subsystem are then dispatched on the basis of equal incremental cost to meet a specified total
subsystem generation.
Activity ECDI requires minimum and maximum outputs, incremental heat rates, fuel costs, and start-
up priority rankings for all machines to be scheduled. This data exists in source file form in an
Economic Dispatch Data File (*.ecd) that is read during the execution of activity ECDI.
The ECDI API routine includes the following among its inputs:
A flag indicating the calculation phase to be performed during this call of the ECDI API
routine:
- Initialization.
- Specify subsystem.
- Unit commitment and economic dispatch calculation.
- Perform housekeeping and exit the ECDI API.
In the initialization phase, the following is specified:
- The name of the Economic Dispatch Data File to be used.
In the subsystem specification phase, the following is specified:
- A designation of the subsystem in which the generation is to be dispatched; refer
to Section 4.8, Subsystem Selection.
- An initial commitment flag indicating one of the following:
Begin the unit commitment calculation from the current commitment profile.
Determine a new commitment profile (i.e., begin the unit commitment with
all dispatchable units out-of-service).
Run Activity ECDI - GUI
Power Flow > Changing > Economic Dispatch (ECDI)
[Economic Dispatch]
Run Line Mode Activity ECDI - CLI
ACTIVITY?
>>ECDI
ENTER ECONOMIC DISPATCH DATA FILE NAME:
>>
Interrupt Control Codes
AB abandon activity ECDI following the completion of the next dispatch iteration
NC suppress the dispatch convergence monitor
Siemens Energy, Inc., Power Technologies International 5-169
PSS
E 32.0
Performing Unit Commitment and Economic Dispatch Program Operation Manual
5-170 Siemens Energy, Inc., Power Technologies International
The auxiliary program PLINC may be used to plot the incremental heat rate curves of specified
machines. Refer to Additional Resources for PSS
E EXAMPLE directory contains an Economic Dispatch Data File, savnw.ecd, which can
be used in conjunction with the savnw.sav Saved Case File. A plot of those incremental heat rate
curves is shown in Figure 5-33.
Figure 5-33. Incremental Heat Rate Curves Provided in the PSS
E savnw.sav Case
Supplementary Units of Dispatch Groups
A special record format is recognized on which a supplementary unit of a dispatch group is speci-
fied. This record has the following format:
I,ID,PRIOR,FRACT,PRNBUS,PRNMAC,CODFRC
where:
HEMIN Minimum heat input required by the machine when in-service; entered in MBtu/hr. If
X
1
(see below) is greater than zero, HEMIN should be specified as the heat input
required at X
1
MW. No default is allowed.
X
i
,Y
i
Points on the incremental heat rate curve; X
i
values are entered in MW and Y
i
values are entered in Btu/kWh. At least two points, and up to six points, may be
entered. Both X and Y must be in ascending order, with X
1
< PMIN and
X
n
> PMAX. If this machine is the principal unit of a dispatch group, this curve is the
combined curve of all machines in the dispatch group.
I Bus number; bus I must be present in the working case with one or more machines
connected to it.
Siemens Energy, Inc., Power Technologies International 5-171
PSS
E 32.0
Performing Unit Commitment and Economic Dispatch Program Operation Manual
5-172 Siemens Energy, Inc., Power Technologies International
Activity ECDI processes only those machines in the specified subsystem for which valid dispatch
data had been read. Other machines retain their initial status and power outputs. Activity ECDI
summarizes the pre-dispatch condition by tabulating the following:
the pre-dispatch production cost/hour.
the minimum generation, maximum generation, and present total generation of in-ser-
vice units that are to be included in the dispatch.
the present generation of subsystem being dispatched; this includes active power gen-
eration subsystem machines that are to be omitted from the dispatch calculation.
Figure 5-34 shows the result obtained using the savnw.sav Saved Case File and savnw.ecd
Economic Dispatch Data File.
Figure 5-34. Summary of the Predispatch Condition
The first four quantities in the above summary are totals based upon the present power outputs and
dispatch data specified in the Economic Dispatch Data File for those machines initially in-service in
the subsystem to be processed. The final total is the sum of the present power outputs of:
those machines to be included in the dispatch calculation; and
those machines in the specified subsystem for which no dispatch data was provided
(the outputs of these machines will not be changed by activity ECDI).
The values specified for the desired loading and minimum capacity of the units to be dispatched
should be entered as values applying to the machines to be dispatched. Specifically, they must not
include the power outputs assigned to those machines in the specified subsystem for which
dispatch data was not read; the outputs of such machines are not changed by activity ECDI.
Activity ECDI then commences the unit commitment portion of its calculation. Note again that the
status of any machine with a priority ranking of zero is not changed during the unit commitment
portion of activity ECDI, but such machines are included in the economic dispatch calculation.
Neither the status nor power outputs of machines for which either no dispatch data was provided or
for which a data error message was generated, and of machines outside of the specified
subsystem, is changed during the execution of activity ECDI.
If the specified desired minimum capacity is greater than the sum of the maximum power outputs
of the machines currently in-service, activity ECDI places additional units in-service. Machines with
lowest priority rankings are connected first, and, within a given priority ranking, units with the lowest
full load average cost per MW are placed in-service first.
If the specified desired loading is less than the sum of the minimum power outputs of the machines
currently in-service, activity ECDI places units out-of-service. Machines with highest priority rank-
ings are disconnected first, and, within a given priority ranking, units with the highest full load
average cost per MW are placed out-of-service first.
Siemens Energy, Inc., Power Technologies International 5-173
PSS
E 32.0
Performing Unit Commitment and Economic Dispatch Program Operation Manual
5-174 Siemens Energy, Inc., Power Technologies International
5.31.3 Viewing Economic Dispatch Results
Following completion of the dispatch calculation, plant power outputs and reactive power limits are
updated to reflect the commitment and dispatch calculation results.
One method of examining the results is to use activity GEOL (refer to Section 10.23, Producing a
Machine Terminal Limits Report) to look at machine terminal conditions. In Figure 5-36 those condi-
tions can be seen for the savnw.sav Saved Case File before and after the economic dispatch
calculation example described here.
Figure 5-36. Before and After Machine Terminal Conditions for Economic Dispatch Example
Another method for observing the changes resulting from the execution of activity ECDI is to use
activity DIFF (refer to Section 10.27, Comparing Power Flow Cases). Compare generator active
powers in the working case with those in the Saved Case File which contains the pre-dispatch
Saved Case.
5.31.4 Dispatch Groups
A dispatch group provides a means of handling a group of machines that are to be treated as a
single entity in the unit commitment and economic dispatch calculations. A combined cycle plant,
in which multiple steam units and combustion turbines are to be dispatched as one unit, may be
handled as a dispatch group in activity ECDI. The high pressure, low pressure pair of a cross
compound unit may also be treated as a dispatch group.
To specify a dispatch group, any one (and only one) of the machines in the dispatch group must be
designated on a standard Economic Dispatch Data File record (refer to Standard Record Format);
this machine is referred to as the principal unit of the dispatch group. The dispatch data specified
on this data record must be that for the combination of all machines that are members of the
Siemens Energy, Inc., Power Technologies International 5-175
PSS
E 32.0
Performing Unit Commitment and Economic Dispatch Program Operation Manual
5-176 Siemens Energy, Inc., Power Technologies International
records of the supplementary machines in the group (refer to Supplementary Units of Dispatch
Groups).
Recall that, when no value of PMAX is specified in the Economic Dispatch Data File, the machine
limits contained in the working case are used as the dispatch limits (refer to Standard Record
Format). For a dispatch group, the sums of the limits of all machines in the group are used as the
dispatch limits. In this case, it is possible to violate the individual machine limits as contained in the
working case if FRACT is not coordinated with the individual machine limits.
When a subsystem of the working case is being processed by activity ECDI, the subsystem assign-
ment of the principal unit of a dispatch group is taken as the subsystem assignment of the group. If
the principal unit is in the subsystem being processed, its dispatch group is processed even if one
or more of its supplementary units is not in the subsystem. Conversely, if the principal unit is not in
the subsystem being processed, the dispatch group is not processed even if some or all of its
supplementary units are in the subsystem.
5.31.5 Application Notes
If the value specified for the desired minimum capacity is less than the value specified for the
desired loading, it is assumed to be equal to the specified loading by the unit commitment
calculation.
In specifying the desired loading and minimum capacity, the quantity (minimum capacity - loading)
may be thought of as spinning reserve.
The iterative dispatch calculation in activity ECDI uses a binary search technique with an upper limit
of 40 iterations. Convergence is assumed when the difference between dispatched power and
desired power is less than 0.00001 times the desired power. Convergence failure, which is usually
the result of precision limitations, generates an alarm and activity ECDI continues as if convergence
had been achieved.
The dispatch data as read from the Economic Dispatch Data File is not retained in the working
case following termination of activity ECDI. An Economic Dispatch Data File is required for
each execution of activity ECDI.
Additional Information
PSS
E GUI Users Guide, Section 7.12, Performing Unit Commitment and Economic Dispatch
PSS
E 32.0
Managing Case Titles Program Operation Manual
5-178 Siemens Energy, Inc., Power Technologies International
5.33 Managing Case Titles
During the initial input of data into PSS
E.
In addition, the PSS
E includes functions for reading the long title, for modifying the both the case title and the long
title, and for printing the long title.
Both the two line case title and the long title are carried along with the working case as it is saved
and retrieved with activities SAVE and CASE, respectively.
Siemens Energy, Inc., Power Technologies International 5-179
PSS
E Command Line Interface (CLI) Users Guide, Section 3.10.1, Importing a Long Title
PSS
E 32.0
Managing Case Titles Program Operation Manual
5-180 Siemens Energy, Inc., Power Technologies International
5.33.2 Changing the Long Title
Activity CHTI
The long title data change activity CHTI enables the user to modify the contents of individual lines
of the 16-line long title without having to reread the entire set of lines with activity RETI.
Line mode activity CHTI is similar to activity CHNG, involving a prompt and response conversational
dialog.
The LongTitleData API routine is the functional equivalent of activity CHTI.
Both interfaces provide the following capabilities:
Editing the text of one or more title lines while leaving the others unchanged.
Entering the entire long title manually without prior preparation of a Long Title File.
Adding additional long title lines if only the first few title lines had previously been
specified.
Run Activity CHTI - GUI
File > Case titles, short & long (CHTI)
[Case Titles]
Run Line Mode Activity CHTI - CLI
ACTIVITY?
>>CHTI
ENTER LINE NUMBER (CARRIAGE RETURN FOR LINE 1, 0 TO EXIT):
>>
Interrupt Control Codes
None
Additional Information
PSS
E GUI Users Guide, Section 6.9.2, Changing the Case Title and the Long Title
PSS
E 32.0
Counting System Components in the Working Case Program Operation Manual
5-182 Siemens Energy, Inc., Power Technologies International
5.34 Counting System Components in the Working Case
Activity SIZE
The case size summary activity SIZE tabulates the number of components in the working case,
along with the maximum number permitted at the current size level of PSS
E working memory.
The SIZE API routine prints its summary at the Report device (refer to Section 4.4), and requires
no additional inputs.
The following network elements are included in the report of activity SIZE:
An example of the output of activity SIZE is shown in Figure 5-38.
Run Activity SIZE - GUI
File > File Information (SIZE/SHOW/BUSN)
[File Information]
OPTION: List the number of system components
Run Line Mode Activity SIZE - CLI
ACTIVITY?
>>SIZE
Interrupt Control Codes
None
Buses, including generator buses and star
point buses of three-winding transformers.
Plants.
Machines, including wind machines.
Wind machines.
Machine ownership specifications.
Fixed shunts.
Switched shunts.
Loads.
Interarea transfers.
AC branches, including two-winding
transformers (both those that were entered as
two-winding transformers and those that are
members of three-winding transformers) and
zero impedance lines.
Two-winding transformers (both those that
were entered as two-winding transformers and
those that are members of three-winding
transformers).
Three-winding transformers.
Branches treated as zero impedance lines.
Branch ownership specifications.
Multi-section line groupings.
Branches designated as line sections in multi-
section line groupings.
Zero sequence mutual couplings.
Two-terminal dc transmission lines.
Multi-terminal dc transmission lines.
Voltage source converter (VSC) dc lines.
FACTS devices.
Siemens Energy, Inc., Power Technologies International 5-183
PSS
E 32.0
Listing Unused Bus Numbers Program Operation Manual
5-184 Siemens Energy, Inc., Power Technologies International
5.35 Listing Unused Bus Numbers
Activity BUSN
The unused bus number summary activity BUSN tabulates those numbers, from within a user spec-
ified bus number range, which are not assigned to buses in the working case.
The inputs to the BUSN API routine define the desired bus number range (starting and ending bus
numbers).
Activity BUSN lists those numbers in the designated range that are not assigned to a bus in the
working case. It lists single numbers and ranges of numbers (e.g., 1208 THROUGH 1219), as
appropriate. It then reports the number of numbers used and the number of numbers available from
within the designated range. The report of activity BUSN is directed to the Report device.
An example of the output of activity BUSN using the default range is shown in Figure 5-39. The
default range is the complete set of valid bus numbers available in PSSE.
Figure 5-39. Example Output of Activity BUSN
Run Activity BUSN - GUI
File > File information (SIZE/SHOW/BUSN)
[File Information]
OPTION: List unused bus numbers in a range
Run Line Mode Activity BUSN - CLI
ACTIVITY?
>>BUSN
ENTER OUTPUT DEVICE CODE:
>>
Interrupt Control Codes
AB
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE TUE, FEB 03 2009 11:49
PSS(R)E PROGRAM APPLICATION GUIDE EXAMPLE
BASE CASE INCLUDING SEQUENCE DATA
UNUSED BUS NUMBERS BETWEEN 1 AND 999997
1 THROUGH 100
103 THROUGH 150
155 THROUGH 200
207 THROUGH 210
212 THROUGH 3000
3009 THROUGH 3010
3012 THROUGH 3017
3019 THROUGH 999997
23 NUMBERS USED AND 999974 NUMBERS AVAILABLE BETWEEN 1 AND 999997
Siemens Energy, Inc., Power Technologies International 5-185
PSS
E 32.0
Displaying Power Flow Data Program Operation Manual
5-186 Siemens Energy, Inc., Power Technologies International
5.36 Displaying Power Flow Data
Activity LIST
The data listing activity LIST tabulates the power flow working case in a form suitable for problem
data documentation. The report generated by activity LIST is separated into several categories of
data.
The LIST API routine includes the following among its inputs:
A designation of the subsystem for which the data tabulation is to be produced; refer to
Section 4.8, Subsystem Selection.
A designation of the power flow data category to be tabulated.
A designation of the units to be used to display ac voltages:
- The units (per unit or kV) indicated by the voltage output program option setting
(see Saved Case Specific Option Settings).
- The alternate units.
5.36.1 Operation of Activity LIST
The user specifies either that the entire working case is to be processed, or that data items for
equipment in a designated bus subsystem are to be tabulated.
If output for a bus subsystem is being produced, only equipment in the designated subsystem is
included in the report except for the following data categories: the case summary; area data; inter-
area transfer data; owner data; and zone data. Any subsystem filtering applied to a data category
is described in the data category descriptions given in Section 5.36.2, Listing Format.
Ac voltages are normally tabulated in the units indicated by the voltage output program option
setting (either per unit or kV). An input of the LIST API routine provides for the tabulation of ac volt-
ages using the other units. If voltages are to be listed in kV but the base voltage at the bus has not
been specified, its voltage is listed in per unit.
The report of activity LIST is directed to the Report device.
Run Activity LIST - GUI
Power Flow > List Data
[List Data]
OPTION: Powerflow
Run Line Mode Activity LIST - CLI
ACTIVITY?
>>LIST
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 5-187
PSS
E 32.0
Displaying Power Flow Data Program Operation Manual
5-188 Siemens Energy, Inc., Power Technologies International
The BRANCHES summary tabulates ac branches. Its data items are interpreted as follows:
The number of multi-section line groupings and the number of ac branches that are members of
multi-section line groupings are tabulated separately. The total numbers of three-winding trans-
formers, dc transmission lines, and FACTS devices are tabulated separately. Totals by service
status of three-winding transformers, multi-section line groupings, dc lines, and FACTS devices are
not tabulated. The number of loads, plants, machines, wind machines, fixed shunts and switched
shunts is reported, as are the number of areas, zones, and owners that have been defined, and the
number of inter-area transactions.
System totals of generation, load, and so on are tabulated. The quantity shown as SHUNTS is the
sum of fixed bus shunts, switched shunts, line connected shunts, magnetizing admittance of trans-
formers, and the shunt elements of FACTS devices. Losses are the sum of I
2
R and I
2
X losses for
in-service lines plus dc line and FACTS device losses, and do not include charging and line shunt
contributions. The loss and swing bus power totals are meaningful only if the working case repre-
sents a solved system condition. The highest and lowest pu bus voltages are listed along with the
largest individual bus and total system mismatch. Up to twelve swing buses are tabulated in
ascending bus number order; if more than twelve Type 3 buses exist in the case, only twelve of
these are listed.
The second page of the case summary tabulates those buses in the working case with the largest
mismatches. At least one, and up to 25, buses are listed, but not more than the number that can fit
on one page. The list is terminated at a largest mismatch of 0.005 MVA.
The case summary always applies to the complete system, even if activity LIST is reporting
for a bus subsystem.
Figure 5-40 shows the case summary for the savnw.sav Saved Case File.
PE/Q Total number of Type 2 buses that are at a reactive power limit (each of these
buses has its type code set to -2 by the power flow solution activities).
SWING Total number of Type 3 buses.
OTHER Total number of buses having other type codes, including star point buses of out-of-
service three-winding transformers; these are usually Type 4 (i.e., disconnected)
buses and/or those buses identified as boundary buses by activities READ and
EXTR.
TOTAL Total number of ac branches in the case; includes two-winding transformers (both
those that were specified as two-winding transformers and those that are members
of three-winding transformers), branches treated as zero impedance lines, and
branches that are members of multi-section line groupings.
RXB Total number of non-transformer branches with charging (i.e., transmission lines);
excludes zero impedance lines.
RX Total number of non-transformer branches with no charging (e.g., series capacitors,
equivalent branches); excludes zero impedance lines.
RXT Total number of two-winding transformer branches; includes those at nominal ratio
and those that are members of three-winding transformers.
RX=0. Total number of branches treated as zero impedance lines.
IN Total number of in-service branches.
OUT Total number of out-of-service branches.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
D
a
t
a
E
n
t
r
y
,
M
o
d
i
f
i
c
a
t
i
o
n
,
a
n
d
D
i
s
p
l
a
y
A
c
t
i
v
i
t
i
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
D
i
s
p
l
a
y
i
n
g
P
o
w
e
r
F
l
o
w
D
a
t
a
Figure 5-40. Case Summary for the savnw.sav Saved Case File
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE WED, FEB 04 2009 16:36
PSS(R)E PROGRAM APPLICATION GUIDE EXAMPLE SYSTEM SUMMARY
BASE CASE INCLUDING SEQUENCE DATA
---------------------BUSES---------------------- -----GENERATION----- ----SHUNTS----- AREA
TOTAL PQ<>0. PQ=0. PE/E PE/Q SWING OTHER LOADS PLANTS MACHNS WIND FIXED SWITCHED AREAS ZONES OWNRS TRANS
23 7 10 3 2 1 0 8 6 6 0 5 0 3 4 7 4
------------------AC BRANCHES------------------- 3WIND MULTI-SECTION ---DC LINES--FACTS X----- SWING BUSES -----X
TOTAL RXB RX RXT RX=0. IN OUT XFORM LINES SECTNS 2TRM MTRM VSC DEVS 3011 MINE_G 13.800
34 22 1 11 0 34 0 0 2 4 0 0 0 0
TOTAL GENERATION PQLOAD I LOAD Y LOAD SHUNTS CHARGING LOSSES SWING
MW 3258.7 3200.0 0.0 0.0 0.0 0.0 58.7 258.7
MVAR 964.2 1950.0 0.0 0.0 -291.5 1810.1 1115.7 104.0
TOTAL MISMATCH = 0.02 MVA X------- AT BUS --------X THRSHZ PQBRAK BLOWUP SBASE
MAX. MISMATCH = 0.01 MVA 201 HYDRO 500.00 0.000100 0.700 5.00 100.0
HIGH VOLTAGE = 1.04043 PU 211 HYDRO_G 20.000 ADJTHR ACCTAP TAPLIM SWVBND
LOW VOLTAGE = 0.93892 PU 154 DOWNTN 230.00 0.0050 1.0000 0.0500 100.0
X------ SOLV AND MSLV ------X X---------------- NEWTON -----------------X X----- TYSL -----X
ACCP ACCQ ACCM TOL ITER ACCN TOLN VCTOLQ VCTOLV ITER DVLIM NDVFCT ACCTY TOL ITER
1.600 1.600 1.000 0.00010 100 1.00 0.100 0.100 0.000010 20 0.9900 0.9900 1.000 0.000010 20
-------------------------------------------------------------------------------
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE WED, FEB 04 2009 16:36
PSS(R)E PROGRAM APPLICATION GUIDE EXAMPLE WORST
BASE CASE INCLUDING SEQUENCE DATA MISMATCHES
BUS# X-- NAME --X BASKV MW MVAR MVA
201 HYDRO 500.00 0.00 0.00 0.01
211 HYDRO_G 20.000 0.00 0.00 0.01
Power Flow Data Entry, Modification, and Display Activities PSS
E 32.0
Displaying Power Flow Data Program Operation Manual
5-190 Siemens Energy, Inc., Power Technologies International
Bus Data
A bus type code of -2 indicates a Type 2 bus for which generation is at a reactive power limit. This
is set by the various power flow solution activities.
The number of loads independently modeled at the bus is tabulated in the column labeled LOADS.
Similarly, the number of fixed and switched shunts modeled at the bus is tabulated in the columns
labeled FIXED and SWITCHED, respectively.
When reporting for a bus subsystem, the bus data tabulation is restricted to subsystem buses.
Load Data
Data for loads is tabulated in the load data category. Loads are listed in ascending bus order
(numeric or alphabetic), and loads at each bus are in ascending load identifier order.
Loads tabulated are at nominal values (i.e., at 1.0 pu voltage). The nominal constant MVA load
component tabulated is not adjusted by any load multiplier associated with an Optimal Power Flow
adjustable bus load table; the load multiplier is tabulated in the column labeled PSI. Constant admit-
tance loads do not include any shunt elements modeled at the bus (refer to Fixed Bus Shunt Data
and Switched Shunt Data).
The column labeled SCALE reflects the setting of the load scaling flag (refer to Load Data).
When reporting for a bus subsystem, the bus and/or base voltage selection criteria, if enabled,
determine those buses whose connected loads are candidates for reporting; otherwise, all buses
are candidate buses. The area, owner, and/or zone selection criterion, if enabled, determine which
loads at candidate buses are to be reported; otherwise, all loads at candidate buses are reported.
Plant Data
Buses that have plant data associated with them (refer to Plant and Machine Sequence Numbers)
are tabulated in the plant data listing. This tabulation includes plants that are out-of-service (i.e., with
a type code of 1 or 4). The number of machines independently modeled at the plant is tabulated in
the column labeled MCNS.
Any plant that regulates the voltage at a remote bus has the remote bus listed at the right-hand side
of the report. Any plant regulating its own terminal voltage has no entry in the REMOTE BUS field.
When reporting for a bus subsystem, the plant data tabulation is restricted to subsystem buses.
Generator Unit Data
Data for machines is tabulated in the generator unit data category. Machines are listed in ascending
bus order (numeric or alphabetic), and machines in each plant are in ascending machine identifier
order.
For each machine, the bus type code, machine identifier and machine status flag are listed in the
columns labelled CD, ID, and ST, respectively. Recall that the actual status of a machine is deter-
mined both by its status flag and the bus type code (refer to Section 5.8.1, Equipment Status
Changes). For machines that are not designated as wind machines, the columns labelled WMOD
and WPF are blank.
When reporting for a bus subsystem, the bus, area, zone, and/or base voltage selection criteria, if
enabled, determine those buses whose connected machines are candidates for reporting; other-
Siemens Energy, Inc., Power Technologies International 5-191
PSS
E 32.0
Displaying Power Flow Data Program Operation Manual
5-192 Siemens Energy, Inc., Power Technologies International
Line Shunt Data
Data for line connected shunts on non-transformer ac branches is tabulated in the line shunt data
category. This report tabulates branches with a non-zero line connected shunt at either end;
branches with line shunt values of (0.0 + j 0.0) at both ends are omitted from the report.
The line shunt tabulation is ordered in the same manner as is branch data report (refer to Branch
Data). Branches are tabulated in single entry format as in the branch data category except when
full listing (double entry branch) is specified.
Branch status is tabulated in the column labeled ST.
When reporting for a bus subsystem, the bus, area, zone, and/or base voltage selection criteria, if
enabled, determine those buses whose connected branches are candidates for reporting; other-
wise, all buses are candidate buses. The owner selection criteria, if enabled, determines which
branches at candidate buses are to be reported; otherwise, all non-transformer branches at candi-
date buses with a non-zero line shunt at either end, including branches to non-candidate buses (i.e.,
ties), are reported.
Two-Winding Transformer Data
Data for two-winding transformers is tabulated in the two-winding transformer impedance data
listing, in the two-winding transformer winding data listing, and in the two-winding transformer
control data listing. The majority of data items in these report categories correspond to data items
specified in the two-winding transformer data input block (refer to Transformer Data).
The two-winding transformer tabulations are ordered in the same manner as is branch data report
(refer to Branch Data). Transformer branches are tabulated in single entry format as in the branch
data category except when full listing (double entry branch) is specified.
In the transformer impedance and control data listings, the column labeled W1 contains an F if the
bus listed as the from bus is the bus to which Winding 1 of the transformer is connected, or a T if
the to bus is the bus to which Winding 1 is connected.
In the transformer impedance data listing, the column labeled ST is the status flag of the trans-
former, with 0 indicating out-of-service, and 1 indicating in-service. The column labeled MT contains
an F if the bus listed as the from bus is the metered end, or a T if the to bus is the metered end. For
any transformer with an impedance correction table assigned to it, both specified (i.e., nominal) and
corrected (i.e., as modified by application of the transformer impedance correction table) imped-
ances are tabulated.
In the transformer control data listing, the controlled bus number is preceded by a minus sign if it is
on the Winding 1 side of the transformer.
When reporting for a bus subsystem, the bus, area, zone, and/or base voltage selection criteria, if
enabled, determine those buses whose connected two-winding transformers are candidates for
reporting; otherwise, all buses are candidate buses. The owner selection criteria, if enabled, deter-
mines which transformers at candidate buses are to be reported; otherwise, all two-winding
transformer branches at candidate buses, including transformers to non-candidate buses (i.e., ties),
are reported.
Siemens Energy, Inc., Power Technologies International 5-193
PSS
E 32.0
Displaying Power Flow Data Program Operation Manual
5-194 Siemens Energy, Inc., Power Technologies International
When reporting for a bus subsystem, the bus, area, zone, and/or base voltage selection criteria, if
enabled, determine those buses whose connected transformers are candidates for reporting; other-
wise, all buses are candidate buses. The owner selection criteria, if enabled, determines which
transformers at candidate buses are to be reported; otherwise, all transformers at candidate buses
that are assigned to the table, including transformers to non-candidate buses (i.e., ties), are
reported.
Multi-Section Line Grouping Data
Data for multi-section line groupings, along with the ac branches that are their members, is tabu-
lated in the multi-section line grouping data listing. The multi-section line groupings are tabulated in
single entry format as in the branch data category (refer to Branch Data) except when full listing
(double entry branch) is specified.
An asterisk ( - ) follows the identifiers of the bus designated as the metered end.
The branches comprising each grouping are listed in series order starting at the bus listed as the
from bus.
When reporting for a bus subsystem, the bus, area, zone, and/or base voltage selection criteria, if
enabled, determine those endpoint buses whose connected multi-section lines are candidates for
reporting; otherwise, all buses are candidate buses. The owner selection criteria, if enabled, is
applied to each member of the multi-section lines at candidate buses and determines which multi-
section lines are to be reported; otherwise, all multi-section lines at candidate buses, including
those to non-candidate endpoint buses (i.e., ties), are reported.
DC Line Data
Data for dc lines is tabulated in the dc line data listing. The dc line listing has two-terminal lines in
dc line name alphabetical order listed first, followed by multi-terminal lines in dc line name alpha-
betical order, followed by VSC dc lines in dc line name alphabetical order.
In addition to the dc line input data (refer to Two-Terminal DC Transmission Line Data, Voltage
Source Converter (VSC) DC Transmission Line Data and Multi-Terminal DC Transmission Line
Data), solution results are listed. For each converter of a two-terminal or multi-terminal line, the
alpha or gamma angle is printed along with the apparent ac system complex load and the tap
setting.
For each two-terminal line, the dc line current (DCAMPS) and the compounded dc line voltage
(VCOMP) are printed on the first line of the output block, and the dc voltage at each end of the line
is printed with the converter data. The Winding 1 tap ratio (RATIO) of an ac transformer that is
controlling a dc line quantity is shown following the ac transformer identifiers in the output block of
the appropriate dc line.
For each multi-terminal line, the voltage at each dc bus and the current on the dc side of each
converter transformer is printed. For each dc link in the line, the metered end dc bus is listed in the
column labeled MET.
For each VSC dc line, the dc line current (DCAMPS) is printed. For each converter, the apparent
ac system complex generation, the ac current in amps (ACAMPS), and the voltage on the dc side
of the converter are listed.
When reporting for a bus subsystem, the dc line data tabulation is restricted to those dc lines that
are connected to at least one subsystem bus.
Siemens Energy, Inc., Power Technologies International 5-195
PSS
E 32.0
Displaying Power Flow Data Program Operation Manual
5-196 Siemens Energy, Inc., Power Technologies International
FACTS Device Data
Data for FACTS devices is tabulated in the FACTS device sending end data listing and in the
FACTS device terminal end data listing. FACTS devices are ordered in ascending FACTS device
name alphabetical order.
When reporting for a bus subsystem, the bus, area, zone, and/or base voltage selection criteria, if
enabled, determine those buses whose connected FACTS devices are candidates for reporting;
otherwise, all buses are candidate buses. The owner selection criteria, if enabled, determines which
FACTS devices at candidate buses are to be reported; otherwise, all FACTS devices at candidate
buses, including those with a series element connected to a non-candidate bus (i.e., ties), are
reported.
Additional Information
PSS
E 32.0
Listing Components of a Bus Program Operation Manual
5-198 Siemens Energy, Inc., Power Technologies International
Three-winding transformer data is printed in four blocks. The column labeled ST in the first and
second blocks is the three-winding transformer status (0 through 4; refer to Non-Transformer
Branch Data). The column labeled ST in the third block shows the status of the three two-winding
transformers comprising the three-winding transformer. The two winding buses in the third block
where identifiers are followed by an asterisk ( - ) are the two metered end buses, and the other bus
is the non-metered bus. Except for winding impedances, which are derived from the measured
impedances and are tabulated in per unit on system MVA base and winding voltage base, trans-
former impedances, admittances, and winding data are printed in the units specified by CZ, CM,
and CW, respectively. The column labeled CN is the transformers automatic adjustment control
mode.
The adjustable branch reactance device data tabulation includes the to bus and circuit identifier, the
branch reactance multiplier magnitude, the nominal branch reactance, and the device status.
Additional Information
PSS
E GUI Users Guide, Section 8.1.3, Listing Buses and their Connected Equipment
PSS
E 32.0
Listing Buses using Partial Bus Name Program Operation Manual
5-200 Siemens Energy, Inc., Power Technologies International
5.39 Listing Buses using Partial Bus Name
Activity FIND
The bus name to number translation activity FIND enables the user to determine the number of a
bus with a specified extended bus name. In addition, through the use of a string matching character,
activity FIND produces a listing of possible matching names even if the exact spelling of the bus
name and/or its base voltage is not known.
The FIND API routine includes the following among its inputs:
The bus name component of the extended bus name.
The base voltage component of the extended bus name.
The bus name input string consists of up to twelve alphanumeric characters, plus embedded aster-
isks ( - ), which are interpreted as wildcard string matching characters. Each - represents any
number of characters, including zero, which may be embedded between other substrings specified
in name, and up to seven of them may be included between other alphanumeric characters.
Any buses for which the name and base voltage contain the specified substrings are listed at the
Report device in ascending bus number or name order, according to the bus output option currently
in effect (refer to Saved Case Specific Option Settings and activity OPTN).
The following examples illustrate the response of activity FIND to various input values, with the first
column indicating the input for the bus name component, and the second the input for the base
voltage component:
Run Line Mode Activity FIND - CLI
ACTIVITY?
>>FIND
ENTER DESIRED BUS NAME:
Interrupt Control Codes
AB
AB All buses of any base voltage whose name begins with "AB".
AB 230 All 230-kV buses whose name begins with "AB".
-AB 115 All 115-kV buses whose name contains the string "AB" anywhere in its twelve-
character name. Thus the listing produced would include 115-kV buses
"ABCD" and "XYZABC", but not "AXB" or "XAYB".
A-BC All buses of any base voltage whose name begins with "A" and in addition con-
tains the string "BC". Thus the listing produced would include the buses
"ABCXYZ" and "AXYZBC", but not the buses "XABC", "BCA", or "ABXC".
13.8 All 13.8-kV buses.
13 All buses with a base voltage equal to or greater than 13-kV and less than
14-kV.
13.0 All buses with a base voltage of 13.0-kV.
0 All buses for which a base voltage was not specified.
Siemens Energy, Inc., Power Technologies International 5-201
PSS
E 32.0
Listing Bus Shunts Program Operation Manual
5-202 Siemens Energy, Inc., Power Technologies International
5.40 Listing Bus Shunts
Activity SHNT
The bus shunt summary activity SHNT tabulates fixed and/or switched bus shunts contained in the
working case.
The SHNT API routine includes the following among its inputs:
A designation of the subsystem for which the data tabulation is to be produced; refer to
Section 4.8, Subsystem Selection.
A designation of the types of bus shunts to be reported:
- All bus shunts
- Only fixed shunts
- Only switched shunts
The user specifies either that the entire working case is to be processed, or that shunts connected
to buses in a designated bus subsystem are to be tabulated.
The report of activity SHNT is directed to the Report device.
In the report of activity SHNT, buses are ordered as described in Section 4.9. When multiple shunts
are present at a bus, fixed shunts at the bus are listed first in ascending shunt identifier order,
followed by the switched shunt if one is present.
For each shunt tabulated by activity SHNT, the bus number, name, base voltage, and bus type code
are printed, along with the shunts service status and the nominal values (i.e., at one per unit
voltage) of the shunts admittance. The present bus voltage magnitude is printed along with an iden-
tifier indicating whether the shunt is a fixed or switched shunt. For fixed bus shunts, the shunt
identifier is also printed. For switched shunts, the switched shunt control mode and switched shunt
adjustment method are printed along with the minimum (i.e., all reactors switched on) and maximum
(i.e., all capacitors switched on) susceptance values of the switched shunt. If a switched shunt
reactor block is out of sequence (i.e., a reactor block is detected after the first capacitor block), the
calculated maximum value is followed by an asterisk ( - ).
Run Activity SHNT - GUI
Power Flow > List Data
[List Data]
OPTION: Bus shunts
Run Line Mode Activity SHNT - CLI
ACTIVITY?
>>SHNT
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 5-203
PSS
E 32.0
Listing Outaged Equipment Program Operation Manual
5-204 Siemens Energy, Inc., Power Technologies International
5.41 Listing Outaged Equipment
Activity OUTS
The outaged equipment reporting activity OUTS tabulates those components in the working case
that are removed from service.
The OUTS API routine includes the following among its inputs:
A designation of the subsystem for which the data tabulation is to be produced; refer to
Section 4.8, Subsystem Selection.
The user specifies either that the entire working case is to be processed, or that outaged equipment
in a designated bus subsystem is to be tabulated.
The report of activity OUTS is directed to the Report device.
The following outaged equipment is listed by activity OUTS:
Out-of-service non-transformer branches and two-winding transformers
Out-of-service three-winding transformers
Disconnected and isolated buses
Out-of-service plants
Out-of-service machines at in-service plants
Out-of-service loads at in-service buses
Out-of-service fixed shunts at in-service buses
Blocked dc transmission lines
Out-of-service converters at in-service VSC dc lines
Out-of-service FACTS devices.
When a subsystem is being processed and ownership is included among the selection criteria,
branch, machine, load, and VSC dc line ownership rather than bus ownership is used in determining
which branches, machines, loads, and VSC dc lines are contained in the specified subsystem; any
other selection criteria apply to the buses to which the equipment item is connected.
Run Activity OUTS - GUI
Power Flow > List Data
[List Data]
OPTION: Outaged equipment
Run Line Mode Activity OUTS - CLI
ACTIVITY?
>>OUTS
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 5-205
PSS
E 32.0
Listing Sequence Data Program Operation Manual
5-206 Siemens Energy, Inc., Power Technologies International
5.42 Listing Sequence Data
Activity SQLI
The sequence data listing activity SQLI tabulates the sequence data arrays in the working case in
a form suitable for problem data documentation. The report generated by activity SQLI is separated
into several categories of data.
The SQLI API routine includes the following among its inputs:
A designation of the subsystem for which the data tabulation is to be produced; refer to
Section 4.8, Subsystem Selection.
A designation of the sequence data category to be tabulated.
5.42.1 Operation of Activity SQLI
The user specifies either that the entire working case is to be processed, or that data items for
equipment in a designated bus subsystem are to be tabulated.
If output for a bus subsystem is being produced, only equipment in the designated subsystem is
included in the report. Any subsystem filtering applied to a data category is described in the data
category descriptions given in Section 5.42.2, Listing Format.
The report of activity SQLI is directed to the Report device.
The following data categories are available in activity SQLI:
Run Activity SQLI - GUI
Power Flow > List Data
[List Data]
OPTION: Sequence data
Run Line Mode Activity SQLI - CLI
ACTIVITY?
>>SQLI
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
All data
Bus load data
Generator data
Fixed bus shunt data
Switched shunt data
Non-transformer branch data
Line shunt data
Two-winding transformer data
Three-winding transformer data
Mutual data
Siemens Energy, Inc., Power Technologies International 5-207
PSS
E 32.0
Listing Sequence Data Program Operation Manual
5-208 Siemens Energy, Inc., Power Technologies International
sequence values printed on the first line and zero sequence values on the second line. All admit-
tances are printed in per unit.
When reporting for a bus subsystem, the switched shunt data tabulation is restricted to subsystem
buses.
Non-Transformer Branch Data
Data for non-transformer ac branches is tabulated in the branch data category. Branches are
ordered in ascending numerical or alphabetical order by from bus, and, for each from bus, in
ascending order by to bus and circuit identifier.
The non-transformer branch data listing is in single entry format. Each non-transformer ac series
branch appears once in the listing: with the lower ordered bus (number or name) listed as the from
bus.
For a branch treated as a zero impedance line, a Z is printed in the column labeled ZI. For branches
that are not treated as zero impedance lines, this column is left blank.
The column labeled ST is the status flag of the branch, with zero indicating out-of-service and one
indicating in-service.
If a branch is mutually coupled to other branches in the zero sequence network, the mutually
coupled branches are listed following the branch data line. Mutuals are listed one per line in single
entry format. The from bus, to bus and circuit identifier of the coupled branches are printed along
with the mutual impedance. Note that the value printed as the mutual impedance may be the nega-
tive of the value initially entered. Careful inspection of the from and to bus ordering for the branches
involved will show that the tabulation has reversed the bus ordering for one of the pair of lines, and
consequently changed the sign of the complex mutual impedance.
When reporting for a bus subsystem, the bus, area, zone, and/or base voltage selection criteria, if
enabled, determine those buses whose connected branches are candidates for reporting; other-
wise, all buses are candidate buses. The owner selection criteria, if enabled, determines which
branches at candidate buses are to be reported; otherwise, all non-transformer branches at candi-
date buses, including branches to non-candidate buses (i.e., ties), are reported.
Line Shunt Data
Data for line connected shunts on non-transformer ac branches is tabulated in the line shunt data
category. This report tabulates branches with one or more non-zero line connected shunts in the
positive and/or zero sequence networks; branches for which line shunt values are all (0.0 + j 0.0)
are omitted from the report.
The line shunt data listing is in single entry format. Each non-transformer ac series branch with a
non-zero line shunt admittance appears once in the listing: with the lower ordered bus (number or
name) listed as the from bus. Branches are ordered in ascending numerical or alphabetical order
by from bus, and, for each from bus, in ascending order by to bus and circuit identifier.
When reporting for a bus subsystem, the bus, area, zone, and/or base voltage selection criteria, if
enabled, determine those buses whose connected branches are candidates for reporting; other-
wise, all buses are candidate buses. The owner selection criteria, if enabled, determines which
branches at candidate buses are to be reported; otherwise, all non-transformer branches at candi-
date buses with any non-zero line shunt component, including branches to non-candidate buses
(i.e., ties), are reported.
Siemens Energy, Inc., Power Technologies International 5-209
PSS
E 32.0
Listing Sequence Data Program Operation Manual
5-210 Siemens Energy, Inc., Power Technologies International
Zero sequence mutuals are listed in single entry format.
When reporting for a bus subsystem, a mutual coupling is reported if either of the two branches
satisfy the subsystem selection criteria. The bus, area, zone, and/or base voltage selection criteria,
if enabled, determine those buses whose connected branches are candidates for reporting; other-
wise, all buses are candidate buses. The owner selection criteria, if enabled, determines which
branches involved in mutuals at candidate buses satisfy the subsystem selection criteria; otherwise,
all branches involved in mutuals at candidate buses, including branches to non-candidate buses
(i.e., ties), satisfy the subsystem selection criteria.
Additional Information
PSS
E 32.0
Listing Sequence Data for a Bus Program Operation Manual
5-212 Siemens Energy, Inc., Power Technologies International
For dc lines and FACTS devices, the control mode is printed along with the pu powers as seen by
the ac system. For two-terminal dc lines, multi-terminal dc lines, and FACTS devices, the powers
are printed as flowing from the ac system into the device at each of the ac buses to which it is
connected; for VSC dc lines, the powers are printed as flowing into the ac system.
Additional Information
PSS
E GUI Users Guide, Section 8.1.5, Listing Sequence Data for Buses and their Connected
Equipment
PSS
E is used.
Refer to Section 2.4.2, Specifying Filenames for the file specification conventions and to
Section 2.6, Files Created By PSS
E 32.0
Bus Renumbering Program Operation Manual
5-214 Siemens Energy, Inc., Power Technologies International
5.45 Bus Renumbering
Activity BSNM
The bus renumbering activity BSNM enables the user to change the bus numbers of specified
network buses in the working case and retain a tabulation, normally in file form, of the bus number
changes made.
The BSNM API routine includes the following among its inputs:
A flag indicating the method to be used to renumber buses and/or the processing
phase to be performed during this call of the BSNM API routine.
A designation of the subsystem in which bus numbers are to modified if the renum-
bering method is subsystem renumbering; refer to Section 4.8, Subsystem Selection.
Three integer data items; their interpretation and usage is dependent on the value
specified for the method flag during this call of the BSNM API routine.
A character data item that specifies an extended bus name if the renumbering method
is Bus Name to Bus Number Translation.
A character data item that specifies a translation input file if the renumbering method is
a translation method (Bus Number to Bus Number Translation or Bus Name to Bus
Number Translation) with input taken from a file.
A code indicating the disposition of the Output Tabulation of bus number changes
made.
The name of the Bus Renumbering Translation File for recording the bus number
changes made; used if a data file is selected for the output tabulation.
Run Activity BSNM - GUI
Power Flow > Renumber Buses > By Bus Number
By Bus Name
By Packing
By Subsystem
[Renumber Buses by Bus Number]
[Renumber Buses by Bus Name]
[Renumber Buses by Bus Packing]
[Renumber Buses by Subsystem]
Run Line Mode Activity BSNM - CLI
ACTIVITY?
>>BSNM
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 5-215
PSS
E 32.0
Bus Renumbering Program Operation Manual
5-216 Siemens Energy, Inc., Power Technologies International
If any violations are detected, an appropriate message is printed and no bus number changes are
made for the specified subsystem. Otherwise, the subsystem buses are renumbered. Any buses
with numbers already in the specified range are left unchanged.
Bus Number Offset Method
In this method, activity BSNM reassigns bus numbers of the specified subsystem by adding a
constant, either positive or negative, to the bus numbers of all buses in the specified subsystem. If,
for any bus, the resulting bus number is invalid or already assigned to another bus, an appropriate
message is printed and no bus number changes are made for the specified subsystem. Otherwise,
the subsystem buses are renumbered.
Bus Number to Bus Number Translation
In this method, activity BSNM changes the number of a specified bus to a designated new bus
number. The bus that is to have its number changed is designated by its present bus number.
A bus number pair may be specified as an input to the BSNM API routine. Alternatively, a Bus
Renumbering Translation File containing bus number pairs may be specified to the BSNM API
routine; each record of the file must be in the form:
current bus number new bus number
In either case, when specifying an old number, new number pair, the following conditions must be
satisfied:
The first bus specified must be in the working case.
The new bus number must be a valid bus number (i.e., between 1 and 999,997).
The new bus number must not already be assigned to a bus in the working case.
If any violations are detected in processing a bus number pair, an appropriate message is printed
and the corresponding bus number change is not implemented. Otherwise, the bus number change
is made. Activity BSNM then processes the next bus number pair.
Bus Name to Bus Number Translation
In this method, activity BSNM changes the number of a specified bus to a designated new bus
number. The bus that is to have its number changed is designated by its extended bus name.
A bus name, bus number pair may be specified as an input to the BSNM API routine. Alternatively,
a translation input file containing bus name, number pairs may be specified to the BSNM API
routine; each record of the file must be in the form:
'extended bus name' new bus number
In either case, when specifying an bus name, new number pair, the following conditions must be
satisfied:
The first bus specified must be in the working case.
The new bus number must be a valid bus number (i.e., between 1 and 999,997).
The new bus number must not already be assigned to a bus in the working case.
If any violations are detected in processing a bus name, number pair, an appropriate message is
printed and the corresonding bus number change is not implemented. Otherwise, the bus number
change is made. Activity BSNM then processes the next bus name, number pair.
Siemens Energy, Inc., Power Technologies International 5-217
PSS
E 32.0
Bus Renumbering Program Operation Manual
5-218 Siemens Energy, Inc., Power Technologies International
5.45.3 Examples of Activity BSNM
Suppose that Bus Number Packing is performed on the range starting at 101 and ending at 160 for
the savnw.sav Saved Case File. The original and resulting new bus numbers are shown in Figure 5-
41. It can be seen that the original bus range from 101 to 154 has been packed to a range from 101
to 106.
Figure 5-41. Packing Bus Numbers
Figure 5-42 shows the message at the Progress device indicating how many buses have been
modified, along with the tabulation of bus number changes at the Report device. The latter tabula-
tion could have been sent to a specified output file.
Figure 5-42. Progress Output Indicating Number of Buses Modified
Figure 5-43 shows the Progress and Report device output resulting from bus renumbering using
the All Buses With Area Blocking method on the savnw.sav Saved Case File. Each of the three
areas in the case is given a new bus number range.
Siemens Energy, Inc., Power Technologies International 5-219
PSS
E 32.0
Saving the Working Case in an IEEE Common Format File Program Operation Manual
5-220 Siemens Energy, Inc., Power Technologies International
5.46 Saving the Working Case in an IEEE Common Format File
Activity RWCM
The IEEE Common Format output activity RWCM writes the working case as a file in IEEE common
tape format data records. This format is described in "Common Format for Exchange of Solved
Load Flow Data," IEEE Transactions on Power Apparatus and Systems, Vol. PAS-92,
November/December 1973, pp. 1916-1925.
The RWCM API routine includes the following among its inputs:
A code indicating the handling of dc lines and FACTS devices in the IEEE Common
Format data records.
A code indicating the disposition of the IEEE Common Format data records.
The name of the file to which the IEEE Common Format data records are to be written;
used if a data file is selected as the destination for the records written by activity
RWCM.
Refer to Section 2.4.2, Specifying Filenames for the file specification conventions and to
Section 2.6, Files Created By PSS
E 32.0
Saving Machine Impedance Data Program Operation Manual
5-222 Siemens Energy, Inc., Power Technologies International
5.47 Saving Machine Impedance Data
Activity RWMA
The machine impedance data output activity RWMA writes out machine parametric data from the
working case in the form of a Machine Impedance Data File (refer to Section 5.4.1). That is, when
directed to a file, the output of activity RWMA is in a format suitable for input to activity MCRE. A
data file of the form written by activity RWMA is also required by the IEEE stability data output
program, CMDYRE (refer to Additional Resources for PSS
E, CMDYRE).
The RWMA API routine includes the following among its inputs:
A designation of the subsystem from which the machine parametric data is to be
written; refer to Section 4.8, Subsystem Selection.
A code indicating whether to include or exclude data records for out-of-service
machines.
A code indicating the option to use in calculating active power split fractions.
A code indicating the option to use in calculating reactive power split fractions.
A code indicating the disposition of the machine impedance data records.
The name of the Machine Impedance Data File to which the machine impedance data
records are to be written; used if a data file is selected as the destination for the records
written by activity RWMA.
5.47.1 Operation of Activity RWMA
The user specifies either that the entire working case is to be processed, or that machine imped-
ance data in a designated bus subsystem are to be processed.
When a bus subsystem is being processed and ownership is included among the selection criteria,
the owners to which machines (rather than buses) are assigned are used in defining the subsystem
of machines to be processed. The bus, area, zone, and/or base voltage selection criteria, if enabled,
determine those buses whose connected machines are candidates for processing; otherwise, all
buses are candidate buses. All machines at candidate buses that are wholly or partly owned by any
of the owners specified are processed (refer to Generator Data).
Run Activity RWMA - GUI
File > Save
[Save Network Data]
Machine Impedance Data Tab
Run Line Mode Activity RWMA - CLI
ACTIVITY?
>>RWMA
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 5-223
PSS
E 32.0
Saving Machine Impedance Data Program Operation Manual
5-224 Siemens Energy, Inc., Power Technologies International
Stability Data in IEEE Format
A Machine Impedance Data File, along with its corresponding Dynamics Data File (refer to
Section 14.1.1), is required by the auxiliary program CMDYRE to construct a stability data file in
IEEE format. This format is described in "Procedures for the Exchange of Power Plant and Load
Data for Synchronous Stability Studies", IEEE Transactions on Power Apparatus and Systems, Vol.
PAS-100, No. 7 July 1981, pp. 3229-3245.
When the file created by activity RWMA is to be used as input to the auxiliary program CMDYRE,
it is usually appropriate to include only in-service machines and to use generator powers to calcu-
late the power split fractions.
Machine Status Considerations
In determining machine status, both the bus type code and the machine status flag are considered.
A machine is treated as in-service if its status flag is 1 and the bus type code is 2 or 3.
Split Fractions
The split fractions of a machine are calculated as the ratio of the selected machine quantity to the
sum of those quantities of all in-service machines being processed at the bus. If this denominator
is zero and records for out-of-service machines are being included, the denominator is taken as the
sum of the appropriate quantity of all machines being processed at the bus. If it is still zero, the split
fraction is set to the reciprocal of the number of in-service machines being processed at the bus; if
all machines being processed at the bus are out-of-service, the split fraction is set to the reciprocal
of the number of such machines being processed at the bus.
Using this approach, then, the sum of the split fractions of the in-service machines being processed
at a bus, exclusive of numerical round off, is normally unity. The only situation in which this is
violated is in the case where out-of-service machines are included, both in-service and out-of-
service machines are present and being processed at a bus, and the sum of the split fraction quan-
tity is zero for the in-service machines and non-zero for the out-of-service machines.
When generator reactive powers are used in determining the reactive power split fractions, the
working case must be solved to an acceptable mismatch level.
Additional Information
PSS
E 32.0
Creating a Power Flow Raw Data File Program Operation Manual
5-226 Siemens Energy, Inc., Power Technologies International
5.48.1 Operation of Activity RAWD
The user specifies either that the entire working case is to be processed, or that data records for a
designated bus subsystem are to be written.
When a bus subsystem of the working case is specified for processing by activity RAWD, the user
has the ability to select as output for that subsystem one of the following:
All buses in the specified subsystem, all branches having all of its buses in the specified
subsystem, and all bus connected equipment connected to buses in the specified sub-
system. Branches include non-transformer branches, transformers, dc lines, and
FACTS devices with a series element. Bus connected equipment include fixed shunts,
machines, switched shunts, and FACTS devices without a series element. When area,
owner and/or zone are among the subsystem selection criteria, options for the handling
of loads is described next; otherwise, loads are handled in the same manner as other
bus connected equipment.
All branches having one, but not all, of its buses in the specified subsystem.
All buses in the specified subsystem, all branches having at least one of its buses in
the specified subsystem, and all bus connected equipment connected to buses in the
specified subsystem.
When a bus subsystem of the working case is specified for processing by activity RAWD, and area,
owner and/or zone are among the subsystem selection criteria, one of the following options is
selected for the handling of loads:
Include load records for all loads at subsystem buses.
Include load records for subsystem loads at all buses. In this case, the area, owner
and/or zone assignments, as appropriate, of a load is used in determining if its load
record is output; the area, owner and/or zone assignments of the bus to which the load
is connected are not considered. When this option is selected, records for loads that
are connected to buses outside of the subsystem may be included in the output of
activity RAWD, and records for some loads connected to subsystem buses may be
omitted.
Include load records for all loads at subsystem buses and for subsystem loads at non-
subsystem buses.
When the entire working case is being processed and the option to include records for subsystem
tie branches is specified, activity RAWD produces an output tabulation consisting only of branches
between areas. Thus, no bus, load, fixed shunt, generator, switched shunt, area, zone, owner, or
interarea transfer data is output, and the only branch, transformer, transformer impedance correc-
tion table, dc line, and FACTS device data included in the output is for branches with terminals
connected to buses in different areas.
The intended use of the Power Flow Raw Data File that is being written governs the appropriate
form of the Case Identification Data records at the beginning of the file. One of the following
intended uses must be selected:
By activity READ with initialization of the working case (i.e., with IC = 0 on the first data
record).
By activity READ to add data to the working case (i.e., with IC = 1 on the first data
record).
By activity RDCH (i.e., with the case identification data records omitted).
Siemens Energy, Inc., Power Technologies International 5-227
PSS
E 32.0
Creating a Power Flow Raw Data File Program Operation Manual
5-228 Siemens Energy, Inc., Power Technologies International
When the entire working case is processed, an owner data record is written for any owner for which:
at least one bus, load, machine, branch, dc bus, FACTS device, or VSC dc line record
is written
and
the owner has a non-blank owner name (refer to Owner Data).
When a subsystem of the working case is processed, an owner data record is written for any owner
for which:
at least one bus, load, machine, branch, dc bus, or VSC dc line record is written
and
the owner has a non-blank owner name.
An interarea transfer data record is included in the output of activity RAWD for any transaction for
which at least one bus, load, or dc bus record from each of the two areas is written.
While a PSSE Saved Case File is the prefered mechanism for preserving and archiving network
data, a PSSE Power Flow Raw Data File facilitates the merging of network data with another
power flow case (see Merging Cases).
Activity RAWD may be used to set up a Power Flow Raw Data File for use by activity READ in the
data processing phases of advanced network equivalent construction (refer to Section 5.2.5). When
used in this mode, disconnected buses and out-of-service branches should normally not be
included in the output file created by activity RAWD.
Additional Information
PSS
E GUI Users Guide, Section 10.4, Creating a Power Flow Raw Data File
PSS
E 32.0
Creating a Sequence Data File Program Operation Manual
5-230 Siemens Energy, Inc., Power Technologies International
All buses in the specified subsystem, all branches having all of its buses in the specified
subsystem, and all bus connected equipment connected to buses in the specified
subsystem.
All branches having one, but not all, of its buses in the specified subsystem.
All buses in the specified subsystem, all branches having at least one of its buses in
the specified subsystem, and all bus connected equipment connected to buses in the
specified subsystem.
When the entire working case is being processed and the option to include records for subsystem
tie branches is specified, activity RWSQ produces an output tabulation consisting only of branches
between areas. Thus, no machine impedance, shunt load, fixed shunt, and switched shunt data is
output, and the only branch, mutual impedance, and transformer data included in the output is for
branches with terminals connected to buses in different areas.
Refer to Section 2.4.2, Specifying Filenames for the file specification conventions and to
Section 2.6, Files Created By PSS
E 32.0
Creating a Transactions Raw Data File Program Operation Manual
5-232 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 6-1
Chapter 6
Power Flow Solution
Activity Descriptions
6.1 About Power Flow Calculations
The most common power system network simulation is the power flow calculation, described in the
following question:
Calculated answers to this question are the basic means by which the power system is engineered
to serve its load. The power system must operate without overloading transmission lines or trans-
formers, stay within acceptable voltage limits at all buses, and maintain generator reactive power
outputs between acceptable limits.
The power flow problem pertains to balanced steady-state operation of the power system. Because
it considers balanced operation in which all negative- and zero-sequence voltages are zero, the
power flow calculation deals with the positive-sequence model of all system components.
The following are the basic known input data for power flow calculations:
Transmission line impedances and charging admittances.
Transformer impedances and tap ratios.
Admittances of shunt-connected devices such as static capacitors and reactors.
Load-power consumption at each bus of the system.
Real-power output of each generator or generating plant.
Either voltage magnitude at each generator bus or reactive power output of each gen-
erating plant.
Maximum and minimum reactive power output capability of each generating plant.
The quantities to be determined are
The magnitude of the voltage at every bus where this is not specified in the input data.
The phase of the voltage at every bus, except swing buses.
The reactive power output of each plant for which it is not specified.
The real power, reactive power, and current flow in each transmission line and
transformer.
Given the load power consumption at all buses of the electric power system and
the generator power production at each power plant, what is the power flow in each
line and transformer of the interconnecting network?
Power Flow Solution Activity Descriptions PSS
E 32.0
Power Flow Solution Methods Program Operation Manual
6-2 Siemens Energy, Inc., Power Technologies International
The power flow calculation is a network solution problem. The network of transmission lines and
transformers is described by the linear algebraic equation:
I
n
= Y
nn
V
n
(6.1)
where:
If either I
n
or V
n
is known, the power flow calculation is straightforward. In practice, neither I
n
nor
V
n
is known and the task of the power flow program is to devise successive trials of both I
n
and V
n
such that they satisfy both Equation 6.1 and all the load and generation conditions specified in the
problem data. After V
n
has been determined, all individual transmission line and transformer flows
can be obtained directly from the individual component equations.
This chapter contains operational descriptions of the PSS
E includes five power flow solution activities, each of which operates on the bus voltage esti-
mates in the working case to attempt to bring them to a solution of Kirchhoffs laws. Each activity
makes successive adjustments to the bus voltages in accordance with a different iterative scheme.
The iterative schemes are listed in Table 6-1 along with the activity names familiar to users of
previous versions of PSS
E.
Because power flow convergence properties are dependent upon network and load attributes, each
of the five iteration methods has its own strengths and weaknesses. The most significant strengths
and weaknesses are summarized in Table 6-6.
Any of these five methods can fail to converge on the solution of some problems. It is rare, however,
to find a problem that has a solution, but the voltage solution vector cannot be found by the appli-
cation of one or more of the five methods. There are many problems that are difficult or impossible
I
n =
Vector of positive-sequence currents flowing into the network at its nodes
(buses).
V
n =
Vector of positive-sequence voltages at the network nodes (buses).
Y
nn =
Network admittance matrix.
Table 6-1. Available Iteration Schemes in PSS
E
Iterative Scheme Activity Name
Gauss-Seidel SOLV
Modified Gauss-Seidel handles series capacitors MSLV
Full Newton-Raphson FNSL
Decoupled Newton-Raphson NSOL
Fixed-Slope Decoupled Newton-Raphson FDNS
Siemens Energy, Inc., Power Technologies International 6-3
PSS
E 32.0
Power Flow Solution Methods Program Operation Manual
6-4 Siemens Energy, Inc., Power Technologies International
If the iterations are slow, it is possible to use the AB interrupt to cancel whichever solution method
is in progress and, subsequently, select a different solution method to continue.
6.2.1 Using Acceleration Factors and Solution Tolerances
The power flow solution activities use the acceleration factors listed in Table 6-2 and the conver-
gence tolerance values listed in Table 6-3. The power flow working case contains an iteration limit
used by the Gauss-Seidel solutions (ITMX), and another (ITMXN) used by the Newton-Raphson
solutions. The default values of these iteration limits are 100 and 20 iterations, respectively.
Each of these solution parameters is set to a default value based on general experience each time
PSS
E is started up. The user should be prepared to tune these solution parameters. The conver-
gence properties of the Gauss-Seidel solutions are particularly dependent upon the acceleration of
the voltage adjustment process.
These solution parameters can be changed using the data changing activity CHNG or the [Solution
Parameters] dialog. They are all saved and retrieved with the power flow case.
Table 6-2. Power Flow Iteration Acceleration Factors
Iteration Type Name Default Value Applied To
Gauss-Seidel
ACCP
ACCQ
1.6
1.6
Real part of voltage change
Imaginary part of voltage change
Modified Gauss-Seidel
ACCM
ACCP
ACCQ
1.0
1.6
1.6
Complex voltage change at Type 1 buses
Real part of voltage change at Type 2 buses
Imaginary part of voltage change at Type 2 buses
Newton-Raphson ACCN 1.0 Magnitude of voltage change at Type 2 buses only
Table 6-3. Power Flow Convergence Tolerances
Name Used By Default Value Applied To
TOL
Gauss-Seidel
solutions
0.0001 per unit Voltage magnitude change convergence tolerance
TOLN
Newton-Raphson
solutions
0.1 MW and Mvar Mismatch convergence tolerance
VCTOLQ
Newton-Raphson
solutions
0.1 MW and Mvar
Controlled bus reactive power mismatch
convergence tolerance
VCTOLV
Newton-Raphson
solutions
0.00001 per unit Controlled bus voltage error convergence tolerance
Siemens Energy, Inc., Power Technologies International 6-5
PSS
E 32.0
Power Flow Solution Methods Program Operation Manual
6-6 Siemens Energy, Inc., Power Technologies International
the nearest step, locked, and additional iterations made to bring mismatch down to tolerance once
again. Similarly, with direct tap adjustment controlling Mvar, adjustment will not be made until toler-
ance is reached and controlling logic is identical thereafter to that of direct tap adjustment controlling
voltage.
The solution parameters ADJTR and TAPLIM can be changed using the data changing activity
CHNG or the [Solution Parameters] dialog.
Adjusting Transformer Voltage Control
Voltage control by transformer turns ratio adjustments, as described above, will only be made on
transformers having the following conditions: a nonzero regulated bus number, IREG; and a value
of 1 for the transformer enable flag, RF. The tap ratio of each transformer is adjusted to hold a
voltage magnitude between the limits VMIN to VMAX. The voltage magnitude to be controlled is
calculated as follows:
V
c
= |V
IREG
- I
transformer
(CR + jCX)|
where:
The recommended method for suppressing ratio adjustment is to set the transformer control flag to
zero. Ratio adjustment may also be suppressed by setting IREG to 0.
The tap-step ratio should be properly coordinated with the acceptable voltage band (VMAX-VMIN)
because the discrete steps of available tap ratio are recognized. The default tap-step ratio is
0.00625 per unit (0.625%). The band between VMAX and VMIN should normally be twice the
transformer tap-step. A band of 2% is recommended for the normal case of 0.625% tap ratio steps.
A value of 0 for tap-step should only be used to indicate continuously adjustable taps to the direct
tap adjustment algorithm.
Table 6-5. Transformer Tap Adjustment Options
Method
Availability of
Voltage Control
Adjustment
Availability of Voltage
Control Via Direct Tap
Adjustment
Availability of Mvar
Control Via Direct Tap
Adjustment
Gauss-Seidel Yes No No*
* Tap is assumed fixed.
Modified Gauss-Seidel Yes No No*
Full Newton-Raphson Yes Yes Yes
Decoupled
Newton-Raphson
Yes Yes Yes
Fixed-slope, decoupled
Newton-Raphson
Yes Yes Yes
CR + jCX = Compensating impedances entered by the user.
I
transformer =
Current in the transformer calculated on the IREG side of the transformer.
Siemens Energy, Inc., Power Technologies International 6-7
PSS
E 32.0
Power Flow Solution Methods Program Operation Manual
6-8 Siemens Energy, Inc., Power Technologies International
Adjusting Switched Shunt Admittance
Automatically switched shunt devices are normally adjusted according to the rules given in
Section 6.3.14. When this adjustment option is enabled, either all adjustable switched shunts (i.e.,
the switched shunt is in-service and its control mode, MODSW, is not 0) are subject to adjustment,
or only continuous mode switched shunts (i.e., MODSW is 1) are subject to adjustment. This adjust-
ment is normally enabled in all power flow solutions. It can be suppressed, regardless of the values
of MODSW in the Solution Options. Selective locking of automatically switched shunt devices must
be handled by leaving the adjustment feature enabled in the power flow solution and setting
MODSW to 0 at buses where locking is required.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
6
-
9
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
A
c
t
i
v
i
t
y
D
e
s
c
r
i
p
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
M
e
t
h
o
d
s
Table 6-6. Power Flow Solution ActivitiesSelection Guide
Iteration Method/
Old Activity name Advantages Disadvantages Use When Do Not Use When
Convergence
Monitor
Gauss-Seidel Itera-
tion (SOLV)
Tolerant of data errors, insol-
uble conditions in local areas
of network.
Fails gently, indicates areas of
network causing problem.
Cannot handle negative series
reactances.
Acceleration factor must be
tuned to match system for
optimum performance.
Number of iterations increases
as system size increases.
Initial voltage estimates
are poor.
Network has reactive
power problem.
NSOL or FNSL has failed
to converge.
Data is suspect.
Network has series
capacitors or very
low impedance
branches.
Prints bus number of
bus having largest AV
each iteration together
with /AV/ and rectan-
gular components of
AV. /AV/ is printed as
multiple of solution
tolerance.
Modified Gauss-
Seidel Iteration
(MSLV)
Has most advantages of
Gauss-Seidel and is able to
handle series capacitors
between Type 1 buses.
Convergence is very sensitive
to tuning of acceleration factor,
ACCM.
Slight deviation of ACCM from
optimum. Value gives poor
convergence.
As for Gauss-Seidel.
Network has very
low impedance
branches, series
compensation
exceeding about
80%, or series
capacitors
connected directly to
generator buses.
As for Gauss-Seidel.
Full Newton-
Raphson
Iteration(FNSL)
Rapid convergence on well-
conditioned cases.
Small bus mismatches can be
achieved.
Intolerant of data errors.
Cannot start from poor voltage
estimates.
No indication of cause of
problem when failing to
converge.
Can give problems converging
cases where reactive power
limits are restrictive.
Network is conventional
and well-behaved.
Network contains series
capacitors or other nega-
tive series reactance
branches.
Overloading has
produced reactive
power problems.
Prints largest
mismatch (real and
reactive) and voltage
changes (magnitude
and angle) for each
iteration. Identifies the
bus numbers where
these maxima occur.
6
-
1
0
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
A
c
t
i
v
i
t
y
D
e
s
c
r
i
p
t
i
o
n
s
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
M
e
t
h
o
d
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Newton-Raphson
method with real
and reactive power
equations decou-
pled (NSOL)
Rapid convergence on well-
conditioned cases.
Small bus mismatches can be
achieved.
Intolerant of data errors.
Cannot start from poor voltage
estimates.
Cannot handle network with low
X/R ratio branches (e.g.,
equivalents).
No indication of cause of
problem when failing to
converge.
Can give problems converging
cases where reactive power
limits are restrictive.
Poor voltage estimate
and network contains
negative reactive branch.
Network contains
branches with low
X/R ratios.
Overloading has
produced reactive
power problems.
As for Full Newton-
Raphson.
Newton-Raphson
method with real
and reactive power
equations decou-
pled using a fixed
Jacobian matrix
(FDNS)
Rapid convergence on well-
conditioned cases.
Small bus mismatches can be
achieved.
As mismatches are reduced,
rate of improvement may be
allowed.
Intolerant of data errors.
No indication of cause of
problem when failing to
converge.
Can give problems converging
cases where reactive power
limits are restrictive.
Overloading has
produced reactive
power problems.
As for Full Newton-
Raphson.
Table 6-6. Power Flow Solution ActivitiesSelection Guide (Cont.)
Iteration Method/
Old Activity name Advantages Disadvantages Use When Do Not Use When
Convergence
Monitor
Siemens Energy, Inc., Power Technologies International 6-11
PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-12 Siemens Energy, Inc., Power Technologies International
6.3.2 About Power Flow Boundary Conditions
Steps 2 and 3 of the iterative scheme in Section 6.3.2 refer to two aspects of the power flow solution
calculation. The solution of the power flow problem is a set of bus (or node) voltages that simulta-
neously satisfy the network condition, I
n
= Y
nn
v
n
, derived from Kirchhoffs laws, and the boundary
conditions derived from load and generator characteristics, such as P
k
+ jQ
k
= v
k
i
k
*.
The network condition (Equation 6.1) is linear and can be solved without iteration if either the
voltage vector, v
n
, or the current vector, I
n
, is specified. The solution is a direct calculation if v
n
is
specified, and requires a standard computer procedure for solving linear simultaneous equations if
I
n
is given.
The boundary conditions may be specified quite arbitrarily, depending upon the loads that electricity
users choose to connect to the network, and are usually nonlinear. It is the nonlinearity of the
boundary conditions that forces the use of an iterative procedure for power flow solution. It must be
noted though, that while the network condition can be handled in a non iterative, closed-form
manner, it is often advantageous to use an iterative method to solve both the network condition and
the boundary conditions.
In the commonly used power flow iteration procedures:
Gauss-Seidel methods solve both network and boundary conditions by iteration.
Newton-Raphson methods solve the network condition by closed-form calculation,
while using iteration to solve the boundary conditions.
6.3.3 Boundary Conditions of Constant MVA Loads
The most common load boundary condition is a specification of load real and/or reactive power
consumption
Real (v
k
i
k
*
) = -P
k
(6.3)
Imag (v
k
i
k
*
) = -Q
k
(6.4)
This characteristic is not realistic for voltages below approximately 0.8 per unit. All PSS
E power
flow voltage solutions, in both power flow and dynamic simulation, therefore, modify Equation 6.3
and Equation 6.4 to make P
k
and Q
k
functions of the magnitude of the bus voltage as shown in
Figure 6-1.
Siemens Energy, Inc., Power Technologies International 6-13
PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-14 Siemens Energy, Inc., Power Technologies International
Figure 6-2. Constant Power Load Characteristic
6.3.4 Boundary Conditions of Constant Current Loads
Load may be specified as a given active or reactive component of current such that:
(6.5)
(6.6)
Again, because this characteristic is unrealistic for voltages below about 0.5 per unit, all PSS
E
power flow solutions modify (Equation 6.5 and Equation 6.6) to make I
pk
and I
qk
functions of the
magnitude of v
k
, as shown in Figure 6-3.
Real (v
k
i
k
)
|v
k
|
= - I
pk
*
Imag (v
k
i
k
)
|v
k
|
= - I
qk
*
Siemens Energy, Inc., Power Technologies International 6-15
PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-16 Siemens Energy, Inc., Power Technologies International
6.3.6 Boundary Conditions of Composite Loads
All PSS
E network solutions allow the load at each bus to be a composite of arbitrary amounts of
load with each of the characteristics described in the previous subsections. The composite charac-
teristic becomes the boundary condition used in iterative power flow solutions.
The normal practice is to specify the load at each bus initially as a compendium of constant MVA
and constant admittance loads. Subsequently the data can be adjusted to comprise the required
amounts of each characteristic. This course gives compatibility with external power flow data
formats such as the IEEE Common Format. Conversion and construction of load data is facilitated
by activity CONL.
6.3.7 Boundary Conditions of the Swing Bus
Every power flow simulation case must have at least one bus designated as a swing bus. The corre-
sponding boundary condition is:
v
k(complex)
= constant (6.8)
The net real and reactive power inflow to a swing bus are free variables and follow from the power
flow solution, rather than being boundary conditions imposed upon it.
Power flow solution cases must have at least one swing bus in every separate section (island) of
the network. An ac island is defined as the set of all in-service buses such that each bus in the island
may be reached from every other bus in the island through the in-service ac network. If a working
case contains more than one island, any island is either electrically disjoint from all other islands,
or connected to one or more islands by one or more asynchronous ties (e.g., dc lines).
To be a valid power flow case, each ac island in the working case must contain at least one Type 3
(swing) bus. Furthermore, the buses connected by each in-service branch must be in-service (i.e.,
none of them may be Type 4 buses). No swing bus is needed in fault analysis, switching, and
dynamic simulation calculations, although swing buses may be used in these simulations.
When enabled, the solution connectivity checking option checks for the presence of swingless
islands at the start of each power flow solution (activity OPTN).
The user can check that every subsystem of a power system power flow case includes a swing bus
using activity TREE.
6.3.8 Boundary Conditions of Standard Generators
The standard generator arrangement used throughout PSS
E Generator Configuration
The standard generator boundary condition is a specification of real power output at the high
voltage bus, bus k, and of voltage magnitude at some designated bus, not necessarily bus k.
Real (v
k
i
k
*
) = P
k
(6.9)
|V
1
| = V
sched
(6.10)
This characteristic is subject to the following reactive power output limitations:
Q
mn k
s Imag(v
k
i
k
*
) s Q
mx k
(6.11)
which overrides the voltage schedule condition (Equation 6.10).
It is important to recognize that the maximum and minimum reactive power limits assigned to bus k
apply to generator reactive power output measured at the high-voltage bus and not at the generator
terminals. Determination of Q
min k
and Q
max k
must, therefore, recognize the reactive power loss
in the step-up transformer reactance. A reasonable assumption for assigning reactive power limits
to bus k, in this situation, is to subtract a reactive loss corresponding to full load current (1.0 pu)
from the generator terminal reactive power limits.
Because Z
t
has a per-unit value with respect to generator MVA base and Q
min k
, Q
max k
are in
megavars,
Q
limit k
= Q
limit g
- X
t
MBASE (6.12)
for lagging generator terminal power factor, and
Q
limit k
= Q
limit g
+ X
t
MBASE (6.13)
for leading generator terminal power factor, where:
X
t
= Step-up transformer reactance in per unit on generator base.
Q
limit g
= Limiting reactive power in Mvar at generator terminals.
Q
limit k
= Q
min k
or Q
max k
.
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-18 Siemens Energy, Inc., Power Technologies International
6.3.9 Boundary Conditions of Multiple Identical Generators
Multiple, identical generators and generator step-up transformer units may be represented by the
standard model, as shown in Figure 6-4, by specifying the generator MVA base to be the total MVA
rating of all connected generators and specifying Z
t
as the impedance of a single step-up trans-
former on its own single generator rating. This representation is illustrated in Figure 6-5.
Figure 6-5. Identical Generators at Bus
Lumping several identical generators may, for example, be used where startup and shutdown of
individual units in a plant are scheduled to meet increasing and decreasing plant loading. This is
achieved by adjusting P
gen
, Q
max k
, Q
min
k
, and MBASE
k
. No adjustment of Z
t
or of the network
branch data is necessary.
Use of this lump approach to handle multiple units implies that real and reactive power output are
distributed uniformly between them. If loadings of multiple units are not identical, they must be
treated as different generators even though their impedances and other characteristics are iden-
tical. This offers the advantage of having to change only unit status flags to account for a change in
the number of operating units at the plant.
6.3.10 Boundary Conditions of Multiple Non-Identical Generators
A plant having several different generators connected to its high voltage bus cannot be represented
by a single generator model. Correct representation of such plants requires the use of multiple, indi-
vidual generator models at the plant bus.
6.3.11 Operation of Activity SOLV
The power flow solution activity SOLV uses a Gauss-Seidel iterative algorithm to solve for the bus
voltages needed to satisfy the bus boundary conditions contained in the working case.
A quick note of value is that the Gauss-Seidel solution cannot handle negative series reac-
tances (series capacitors) but the Newton and Modified Gauss-Seidel can.
If the power flow solution network connectivity checking option is enabled (refer to Section 3.3.3),
activity SOLV first checks that each non-Type 4 bus is connected back to a Type 3 (swing) bus
through the in-service ac network. If any violations are detected, an appropriate message is printed
and activity SOLV is terminated.
Z
t
Z
t
Z
t
Z
t
nR
MVA
R
MVA
Unit 1
R
MVA
Unit 2
R
MVA Unit n
t :1
t :1
t :1
t :1
Siemens Energy, Inc., Power Technologies International 6-19
PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-20 Siemens Energy, Inc., Power Technologies International
6.3.12 Generation
During the solution, generator buses are treated as follows:
1. Those generators that regulate their own voltage hold their scheduled voltage as long as
their reactive power limits are not violated.
2. Those generators that regulate the voltage of a remote type 1 or 2 bus have their reactive
power output adjusted as required to hold the desired voltage at the remote bus as long as
their reactive power limits are not violated.
3. Those generators that are swing buses (i.e., with a type code of 3) are held at constant
voltage and phase angle. Their active and reactive power outputs are set as required prior
to leaving activity SOLV. The plant active power is shared among the machines at the plant
in proportion to the magnitudes of their active power settings at the time activity SOLV was
initiated; if all machines have an active power setting of 0.0 at the time activity SOLV is
selected, the plant active power is shared in proportion to the MBASEs of the machines at
the plant. For such buses with both generators and synchronous condensers, only the
generators share the swing bus active power output.
4. At the end of activity SOLV, generator plant reactive powers (and active powers for Type 3
buses) are apportioned among the machines at the plant; reactive powers are split so as to
achieve identical power factors at all machines in a plant, except that machine reactive
power limits are honored.
6.3.13 Load
Busbar load data is entered into PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-22 Siemens Energy, Inc., Power Technologies International
Figure 6-7. Constant Current Load Characteristic
6.3.14 Switched Shunt Devices
Buses for which switched shunt data has been specified in activities READ, Reading Power Flow
Data Additions from the Terminal, or RDCH (refer to Switched Shunt Data) are handled according
to the following rules:
1. Automatically switched shunts are permitted only at type 1 and 2 buses. At type 3 (swing)
buses, switched shunts are treated as locked at the value specified as BINIT in activities
READ, TREA, or RDCH (refer to Switched Shunt Data), or as subsequently modified with
activity CHNG or the [Spreadsheet].
2. For those switched shunts designated as locked (i.e., MODSW = 0 or the bus is a type 3
bus), the specified admittance is held constant during the solution.
3. Those switched shunts controlling local or remote bus voltage to a voltage setpoint
(i.e., VSWHI = VSWLO) are handled as follows:
a. Those switched shunts designated as continuous (i.e., MODSW = 2) hold their
scheduled voltage as long as the admittance limits are not violated. The high admit-
tance limit is the admittance when all reactor blocks are switched off and all
capacitor blocks are switched on; the low limit represents all reactor blocks
switched on and all capacitor blocks are switched off. (Note that for reactors, BL<0
and for shunt capacitors, BC>0).
b. Switched shunt devices designated as operating in discrete mode (i.e.,
MODSW= 1) are initially treated as the continuously operating devices described
above. When the network solution convergence tolerance is reached, the dis-
Voltage
Current
Power
0.0 0.5 1.0 1.1
0
.
0
0
.
5
1
.
0
1
.
1
Siemens Energy, Inc., Power Technologies International 6-23
PSS
E
network solution activities, the presence of discretely operating switched shunts as described in
(3b) above may result in more than one network solution iteration being required. Although the
network was expected to be in balance, significant voltage changes may initially be imposed as
these devices are (temporarily) switched to the continuous mode. This may be overcome by locking
the discrete mode switched shunts at their present settings (refer to Section 6.3.19 and Switched
Shunt Adjustment).
6.3.15 FACTS Devices
PSS
Es FACTS device model (refer to FACTS Device Data and Figure 5-15) contains a shunt
element that is connected between the sending bus and ground, and a series element connected
between the sending and terminal buses. A unified power flow controller (UPFC) has both the series
and shunt elements active, and allows for the exchange of active power between the two elements
(i.e., TRMX is positive). A static series synchronous condenser (SSSC) is modeled by setting both
the maximum shunt current limit (SHMX) and the maximum bridge active power transfer limit
(TRMX) to zero (i.e., the shunt element is disabled). An interline power flow controller (IPFC) is
modeled with a pair of series FACTS devices; the shunt current limits (SHMX) of both devices are
set to zero, TRMX of the master device is set to the maximum active power transfer between the
two devices, and TRMX of the slave device is set to zero. A static synchronous condenser
(STATCON) or static compensator (STATCOM) is modeled by a FACTS device for which the
terminal bus is specified as zero (i.e., no series element is present).
For an in-service FACTS device to be modeled during power flow solutions, it must satisfy the
following conditions:
1. The sending bus must be either a type 1 or type 2 bus.
2. The sending bus must not be connected by a zero impedance line to type 3 bus.
Power Flow Solution Activity Descriptions PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-24 Siemens Energy, Inc., Power Technologies International
3. If it is specified, the terminal bus must be a Type 1 bus with exactly one in-service ac branch
connected to it; this branch must not be a zero impedance line and it must not be in parallel
with the FACTS device.
4. If it is specified, the terminal bus must not have a switched shunt connected to it.
5. If it is specified, the terminal bus must not be a converter bus of a dc line.
6. A bus that is specified as the terminal bus of an in-service FACTS device may have no other
in-service FACTS device connected to it. However, multiple FACTS device sending ends on
the same bus are permitted.
7. A bus that is specified as the terminal bus of an in-service FACTS device may not have its
voltage controlled by any remote generating plant, switched shunt, or VSC dc line converter.
The FACTS device model is called at the start of each iteration to set the boundary conditions to be
imposed upon the ac network at the sending and terminal buses during that iteration.
The shunt element at the sending bus is used to hold the voltage magnitude at either the sending
bus or the specified remote bus to VSET, subject to the sending shunt current limit SHMX. This is
handled in power flow solutions in a manner similar to that of synchronous condensers and contin-
uous switched shunts. In terms of the boundary conditions they impose at the buses to which they
are connected, these three devices differ only in their representation of limits: synchronous
condensers have Mvar limits; switched shunts have admittance limits; and the shunt elements of
FACTS devices have current limits. Current in the shunt-connected bridge is determined by both
the shunt Mvar output and the amount of active power transferred between the shunt and the series
elements. If the current limit is violated, sending end voltage control is abandoned and the magni-
tude of the shunt Mvar output is reduced.
The series element may be set to operate in one of eight modes as described in the following
sections.
Normal Mode
The normal operating mode of the series element is enabled by setting the control mode of the
FACTS device to 1 (refer to FACTS Device Data). In unconstrained operation, the series element
is used to maintain the desired active (PDES) and reactive (QDES) power flow between the sending
and terminal buses. If the series current limit (IMX) is violated, the magnitude of the desired reactive
power flow is reduced; if reducing the desired reactive power flow to zero still results in a series
current limit violation, the magnitude of the desired active power flow is reduced as required. With
desired power setpoints established (either as specified or as reduced due to a series current limit
violation), the bus boundary conditions, which are to be presented to the power flow solution, are
determined.
Limits on three quantities may prohibit the series element from maintaining power flow at the estab-
lished active and/or reactive power setpoints: the series voltage magnitude (maximum of VSMX);
the terminal bus voltage magnitude (maximum of VTMX and minimum of VTMN); and the magni-
tude of the active power transfer between the shunt and series-connected bridges (maximum of
TRMX). These limits result in seven possible states of the model:
Siemens Energy, Inc., Power Technologies International 6-25
PSS
E FACTS model will not attempt to solve for the state in which all three of the above quan-
tities are simultaneously held at a limit. Such a state defines an over-constrained problem. In such
a system condition, the FACTS model will usually cycle among model states (5) through (7) above.
It is the users responsibility to decide which of the three limits is to be relaxed, and then make the
appropriate data change.
Bypassed Mode
The bypassed operating mode of the series element is enabled by setting the control mode of the
FACTS device to 2 (refer to FACTS Device Data). In this mode, the series element is solved to a
series voltage magnitude of zero. No limits are enforced other than SHMX, the maximum shunt
current at the sending bus. The solution is identical to that which would be obtained by replacing
the series element with a zero impedance line.
Power Flow Solution Activity Descriptions PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-26 Siemens Energy, Inc., Power Technologies International
Constant Series Impedance Mode
The constant series impedance operating mode of the series element is enabled by setting the
control mode of the FACTS device to 3 (refer to FACTS Device Data). In this mode, the series
element is modeled with a fixed series impedance specified on system base. No limits are enforced
other than SHMX, the maximum shunt current at the sending bus.
Constant Series Voltage Mode
The constant series voltage operating mode of the series element is enabled by setting the control
mode of the FACTS device to 4 (refer to FACTS Device Data). In this mode, the series element is
solved to a specified complex series voltage expressed relative to the value indicated by VSREF
(i.e., relative to either sending end voltage or series current). No limits are enforced other than
SHMX, the maximum shunt current at the sending bus.
IPFC Master and Slave Modes
An Interline Power Flow Controller (IPFC) may be modeled using two series FACTS devices. One
device of this pair must be assigned as the IPFC master device by setting its FACTS device control
mode to 5 or 7; the other must be assigned as its companion IPFC slave device by setting its control
mode to 6 or 8 and specifying the name of the master device in its MNAME (refer to FACTS Device
Data).
In the IPFC model, both devices have a series element but no shunt element. The master device is
solved in the same manner as a series device in Normal Mode when the control mode is 5 or in
Constant Series Voltage Mode when the control mode is 7, except that the active power transfer is
exchanged with the series element of the slave device. The slave device is always solved with its
bridge active power transfer fixed as dictated by the master device; that is, when its control mode
is 6, it is always in one of solution states 4, 6, or 7. When its control mode is 8, the specified value
of series voltage is modified to reflect the active power exchange dictated by the master.
In control mode 8 when VSREF is 1 (i.e., desired series voltage is specified relative to series
current), the specified V
d
is replaced with that calculated from the active power exchange deter-
mined by the master and the series current of the slave. In control mode 8 when VSREF is 0 (i.e.,
desired series voltage is specified relative to sending bus voltage), the specified Vd and Vq are first
transformed to the series current axis, and the resulting Vd is then replaced with that calculated
from the active power exchange determined by the master and the series current of the slave.
Therefore, both devices typically have SHMX set to zero, and VSET of both devices is ignored.
TRMX of the master device is the maximum active power exchange between the two devices, and
TRMX of the slave device is set to zero. QDES of the slave device is ignored.
All Modes
It is possible for the power flow iteration to continue even though its voltage change or mismatch
tolerance has been achieved. This can occur in several model states described above when the
limited quantity is too far away from the limit being held.
The solution of the series FACTS device in all of the above model states except the constant series
impedance mode includes the temporary insertion into the network of ac series and shunt elements
and a corresponding Norton current injection at the sending and terminal buses of the FACTS
device. This technique can improve the convergence properties of the power flow solution. The
insertion of these dummy elements is handled automatically by the FACTS model using the reac-
tance specified as LINX. If the convergence monitor indicates an underaccelerated convergence,
increasing LINX (which decreases its effect) may be helpful. When the shunt element is at a current
Siemens Energy, Inc., Power Technologies International 6-27
PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-28 Siemens Energy, Inc., Power Technologies International
Power orders and/or reactive power limits are reduced such that the following two equations are
simultaneously satisfied:
(P
i
+ AP)
2
+ (Q
i
+ AQ)
2
= SMAX
2
Thus, if PWF is 0.0, only active power is reduced; if PWF is 1.0, only reactive power is reduced;
otherwise, the above equations are applied.
One of two solution strategies is used for solving the conditions at a VSC dc line at each iteration.
The following approach is used when the following three conditions are satisfied: both converters
are in ac voltage control mode; limits are being checked on this iteration; and both converters are
overloaded.
1. At the converter where the amount of overload is greater, relieve the overload as described
above.
2. Solve for the dc current using the specified dc voltage at the voltage controlling converter,
the active power order and the converter loss coefficients at the converter where the over-
loading was relieved, and the dc line resistance.
3. Calculate the active power order at the other converter.
In all other situations, the following solution approach is used:
1. At the power controlling converter, check limits as described above.
2. Solve for the dc current using the specified dc voltage at the voltage controlling converter,
the active power order and the converter loss coefficients at the power controlling converter,
and the dc line resistance.
3. Calculate the active power order at the voltage controlling converter.
4. Check limits at the voltage controlling converter as described above.
5. If a limit is violated at the voltage controlling converter, calculate a new power order for the
power controlling converter and repeat steps 1 and 2.
When activity SOLV is run on a system that had previously been solved by one of the PSS
E
network solution activities, the presence of VSC converters that control ac voltage and which are at
an MVA or current limit usually results in more than one network solution iteration being required.
Although the network should have been in balance, significant voltage changes may initially be
imposed as these devices are solved with limits ignored until convergence is achieved.
AP
AQ
=
P
i
Q
i
x
(1.0 - PWF)
PWF
Siemens Energy, Inc., Power Technologies International 6-29
PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-30 Siemens Energy, Inc., Power Technologies International
The following setpoint mode voltage controlling devices may be modeled in PSS
E:
An in-service generating plant at a type 2 bus may control either local bus voltage or
the voltage at a remote bus. Refer to Generator Data and Section 6.3.12.
A switched shunt for which MODSW is 1 or 2 at a type 1 or 2 bus may control either
local bus voltage or the voltage at a remote bus to a voltage setpoint (refer to Switched
Shunt Data). Such switched shunts for which MODSW = 1 (i.e., discrete control) are
initially treated as continuous, then moved to the nearest step and locked, as described
in (3b) of Section 6.3.14.
A voltage controlling converter of a VSC dc line at a type 1 or 2 bus may control either
local bus voltage or the voltage at a remote bus. To be a voltage controlling converter,
the VSC dc line must be in-service (MDC = 1), the converter must be in-service
(TYPE = 1 or 2), and the ac control mode must be set for voltage control (MODE = 1).
Refer to Voltage Source Converter (VSC) DC Transmission Line Data and VSC dc
Lines.
The shunt element at the sending end of an in-service FACTS device at a type 1 or 2
bus may control either local bus voltage or the voltage at a remote bus. Refer to FACTS
Device Data and Section 6.3.15.
When multiple voltage controlling devices control the same bus voltage, the reactive power require-
ments are shared among the controlling devices in proportion to their RMPCTs, subject to each
devices reactive power, current or admittance limits, as appropriate. The Mvar output of each device
controlling the voltage at bus I is set to the product of the total Mvar required at all devices controlling
the voltage at bus I times a fraction; the numerator of this fraction is RMPCT of the device and the
denominator is the sum of the RMPCTs of all the devices controlling the voltage at bus I. It is the
responsibility of the user to ensure that voltage control specifications for all the setpoint mode
devices controlling the same bus voltage are identical, and that the RMPCT values are such that
the desired reactive power sharing is obtained.
When multiple setpoint mode voltage controlling devices are present at a bus, they should normally
all be specified with the same voltage control objective. Similarly, when multiple setpoint mode
voltage controlling devices are present among a group of buses connected together by zero imped-
ance lines, the same voltage control objective should be specified for all of them. (Recall that buses
connected together by zero impedance lines are treated as the same bus during power flow solu-
tions; refer to Zero Impedance Lines.)
When one or more devices are controlling the voltage at a remote bus, any setpoint mode voltage
controlling devices at the controlled bus should be specified so as to control local bus voltage.
Other than generation at the bus itself, setpoint mode voltage controlling devices at type 3 buses
and at buses connected to type 3 buses through zero impedance lines may not be used for voltage
control purposes. Such devices are handled as follows by the power flow solution activities:
A zero impedance line connected generating plant is held at its present active and reac-
tive power output.
A local or zero impedance line connected switched shunt controlling to a voltage set-
point is locked at its present admittance.
A local or zero impedance line connected VSC dc line is blocked.
A local or zero impedance line connected FACTS device is blocked.
Activity CNTB may be used to check for suspect or erroneous voltage control specifications.
Siemens Energy, Inc., Power Technologies International 6-31
PSS
E:
A switched shunt for which MODSW is 1 at a type 1 or 2 bus may control either local
bus voltage or the voltage at a remote bus to a voltage band (refer to Switched Shunt
Data and Section 6.3.14).
A switched shunt for which MODSW is 3 at a type 1 or 2 bus may control the reactive
power output of a generating plant to fall within a reduced reactive power limit band
(refer to Switched Shunt Data and Section 6.3.14).
A switched shunt for which MODSW is 4 at a type 1 or 2 bus may control the reactive
power output of a voltage controlling VSC dc line converter to fall within a reduced reac-
tive power limit band (refer to Switched Shunt Data and Section 6.3.14).
A switched shunt for which MODSW is 5 at a type 1 or 2 bus may control the admittance
setting of a remote switched shunt to fall within a reduced reactive admittance limit
band (refer to Switched Shunt Data and Section 6.3.14).
A switched shunt for which MODSW is 6 at a type 1 or 2 bus may control the reactive
power output of the shunt element of FACTS device to fall within a reduced reactive
current limit band (refer to Switched Shunt Data and Section 6.3.14).
A transformer may have its Winding 1 turns ratio adjusted to hold the voltage at a des-
ignated bus within a specified band (refer to Transformer Data and Voltage Control).
The terminal end of an in-service FACTS device at a type 1 or 2 bus may deviate from
its desired power setpoints to keep the voltage at the terminal bus within a specified
band. Refer torefer to FACTS Device Data and Section 6.3.15.
6.3.18 Characteristics of Activity SOLV
The Gauss-Seidel and the Modified Gauss-Seidel have much of their operation and characteristics
in common. This section will summarize the aspects of the Gauss-Seidel method. Refer to
Section 6.4 to review differences with the Modified method.
The Gauss-Seidel solution method has five available solution control parameters:
ACCP - Acceleration factor for the real part of the voltage adjustment.
ACCQ - Acceleration factor for the imaginary part of the voltage adjustment.
TOL - Convergence tolerance in pu.
ITMX - Default limit on number of iterations. (= 100)
BLOWUP - Largest voltage change threshold.
The acceleration factor ACCM is used only for the Modified Gauss-Seidel method.
The nodal iterative solution method of activity SOLV uses separate acceleration factors (ACCP and
ACCQ) for the real and imaginary parts of the voltage adjustment. Both of these factors have default
Power Flow Solution Activity Descriptions PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-32 Siemens Energy, Inc., Power Technologies International
values of 1.6, but ACCP need not be equal to ACCQ. The guide to the tuning of the acceleration
factors should be:
If the voltage change on successive iterations is oscillating in magnitude and/or sign,
decrease acceleration.
If the voltage change on successive iterations is decreasing smoothly, convergence
may be improved by increasing acceleration (see Figure 6-8).
The acceleration factors should never be set greater than two, and the optimum seldom exceeds
about 1.8. Although the acceleration must be tuned to the system for optimum performance, devi-
ations from the optimum values do not have a dramatic effect on the number of iterations required.
The normal tolerance value for the Gauss-Seidel solution is 0.0001 per unit. This tolerance is
applied to the largest voltage change in each iteration and convergence is assumed when |AV| is
less than this tolerance. The tolerance may be increased as far as 0.0005 per unit if only approxi-
mate power flows are needed. Reducing the tolerance as low as 0.00001 per unit is permissible to
achieve reduced node mismatches, but such a small tolerance is not recommended because the
convergence of the Gauss-Seidel method becomes very slow as the voltage changes fall below
about 0.0001 per unit.
Figure 6-8. Dependence of Power Flow Convergence on Acceleration Factors
At the completion of each iteration, the largest voltage change is checked against a blowup toler-
ance, which has a default value of 5.0 pu. If the largest change exceeds this tolerance, an
appropriate message is printed and activity SOLV is terminated.
Iteration Number
Largest
|DV|
Under accelerated
ACCN Factor Should
be Increased
Over accelerated
ACCN Factor Should
be Decreased
Optimum
Acceleration
Siemens Energy, Inc., Power Technologies International 6-33
PSS
E 32.0
Applying Gauss-Seidel Power Flow Solution Program Operation Manual
6-34 Siemens Energy, Inc., Power Technologies International
5. Activity SOLV is tolerant of reactive power problems.
6. Activity SOLV is tolerant of data errors and insoluble conditions in local areas of the network.
It is generally well converged everywhere except in the problem areas.
7. When it diverges, it usually fails gently.
6.3.19 Automatic Adjustments
Activity SOLV provides for the following solution options:
1. Adjustment of transformer off-nominal turns ratio to hold the voltage at a designated bus
within a specified band.
2. Adjustment of area swing bus generator powers to hold area net interchange within a spec-
ified band.
3. Flat start.
4. Adjustment of the turns ratios of converter transformers at dc transmission terminals and of
ac network transformers controlling dc line quantities.
5. Adjustment of switched shunt devices. When this adjustment option is disabled, discretely
operating switched shunts are moved to their nearest step, if necessary, and all switched
shunts, including continuously operating devices, are held constant. When this adjustment
option is enabled, either all adjustable switched shunts may be adjusted, or continuous
mode switched shunts are subject to adjustment and discrete mode switched shunts are
locked.
6. Ignoring generator reactive power limits at Type 2 buses with unequal var limits.
PSS
E program option settings exist for adjustments (1), (2), (4), and (5) above. Activity OPTN may
be used to establish the default setting for each of these adjustment options (refer to Section 3.3.3).
Then, on each entry into activity SOLV, these option settings determine which of the adjustment
options are activated.
The default responses corresponding to the adjustments for which a PSS
E 32.0
Applying Modified Gauss-Seidel Power Flow Solution Program Operation Manual
6-36 Siemens Energy, Inc., Power Technologies International
The following rules and convergence characteristics apply to activity MSLV:
1. The presence of negative reactance branches connected to Type 2 or 3 buses usually
causes activity MSLV to diverge.
2. Series capacitors may be represented between Type 1 buses, as long as the level of
compensation does not exceed about 80%.
3. The presence of very low impedance branches (e.g., jumpers with an impedance of j0.0001)
which are not being treated as zero impedance lines (refer to Zero Impedance Lines) often
results in slow convergence as the voltage adjustments get small, and in mismatches at the
buses involved.
4. The number of iterations required to reach the convergence tolerance increases as the
system size increases.
5. Activity MSLV may be used if the initial voltage estimate is poor.
6. Activity MSLV is tolerant of reactive power problems.
7. Activity MSLV is tolerant of data errors and insoluble conditions in local areas of the network.
It is generally well converged everywhere except in the problem areas.
8. The rate of convergence is very sensitive to the tuning of the acceleration factor ACCM.
Modest deviation from the optimum value may result in poor convergence characteristics.
9. Activity MSLV takes somewhat more time per iteration than does activity SOLV, but gener-
ally requires fewer iterations.
Additional Information
PSS
E GUI Users Guide, Section 11.2.6, Modified Gauss-Seidel Power Flow Solution
PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-38 Siemens Energy, Inc., Power Technologies International
The application of generator reactive power limits on the first iteration following a network change
may cause setpoint mode voltage controlling devices to be spuriously placed on a limit (e.g., a
generators reactive power set at the low limit but voltage magnitude less than scheduled voltage).
Activity FNSL prints a summary of any such voltage controlling devices at the Progress tab prior to
returning control back to the PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-40 Siemens Energy, Inc., Power Technologies International
before any scaling down of the change vectors, as described in the preceding paragraph, is applied.
If the largest change exceeds the blowup tolerance, an appropriate message is printed and activity
FNSL is terminated. The blowup check is bypassed if the non-divergent Newton power flow solution
option is enabled (refer to Section 6.5.3).
Convergence is assumed when the following conditions are simultaneously satisfied:
1. The largest active power mismatch at each Type 1 and 2 bus must be less than the
mismatch convergence tolerance, TOLN.
2. The largest reactive power mismatch at those buses at which a PQ boundary condition is
applied must be less than the mismatch convergence tolerance, TOLN. This test applies to
the following categories of Type 1 and 2 buses:
a. Voltage at the bus is not subject to control to a setpoint.
b. Voltage at the bus is subject to control to a setpoint (refer to Setpoint Voltage Con-
trol), but all of the devices participating in the control of bus voltage to its setpoint
are at a reactive power limit.
3. The largest reactive power mismatch at those buses at which a PV boundary condition is
applied must be less than the larger of the controlled bus reactive power mismatch conver-
gence tolerance, VCTOLQ, and TOLN. This test applies to each Type 1 and 2 bus where
voltage is subject to control to a setpoint, and for which at least one of the devices partici-
pating in the control of bus voltage to its setpoint is not at a reactive power limit. While this
test is applied to all such buses, the reactive power mismatch will normally be zero (or very
close to zero) at such buses which have local devices participating in the control of bus
voltage to its setpoint, and at least one of these local devices is not at a reactive power limit.
4. The largest difference between actual and scheduled voltage magnitude in per unit at each
Type 1 and 2 bus where voltage is subject to control to a setpoint, and for which at least one
of the devices participating in the control of bus voltage to its setpoint is not at a reactive
power limit, must be less than the controlled bus voltage error convergence tolerance,
VCTOLV.
The Newton solution might not be able to reduce mismatch to the 0.001 per-unit value because of
the inherent computer precision limit.
Consider a branch with impedance of 0.0001 per unit and voltages close to unity at both ends. The
maximum imprecision in calculation of power flow through the branch is approximately:
Because the bus mismatch imprecision is the sum of the imprecisions in flows into connected
branches, a power flow case including such low-impedance branches is unlikely to reach the default
tolerance of 0.001 per unit.
The default mismatch tolerances (TOLN and VCTOLQ) are 0.1 MW and Mvar (0.001 pu on 100
MVA base), but tolerances as large as 1 MW and Mvar can give acceptable power flow solutions
for many purposes. The default Newton power flow solution mismatch tolerance program option
setting (refer to User Specified Option Settings) is the value assigned to these tolerances when a
new case is read into PSS
E with activity READ. VCTOLQ may be set to a value larger than TOLN
for cases with challenging remote voltage control specifications.
AP 2
AV
Z
-------- 0.0025 per unit = =
Siemens Energy, Inc., Power Technologies International 6-41
PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-42 Siemens Energy, Inc., Power Technologies International
1. Activity FNSL converges in a very few iterations on well-conditioned cases, achieving very
small bus mismatches.
2. Negative reactance branches are permitted in the network.
3. The presence of very low impedance branches (e.g., jumpers with an impedance of j0.0001)
that are not being treated as zero impedance lines (refer to ORDR) may result in the inability
of FNSL to reach the default convergence tolerances. Even with such a network, FNSL is
usually capable of reducing the largest bus mismatch to less than 0.2 MVA.
4. The number of iterations required to reach the convergence tolerances is generally insensi-
tive to system size.
5. Activity FNSL may diverge if the initial voltage estimate is poor.
6. Reactive power problems may cause poor convergence characteristics.
7. Applying generator reactive power limits too early may cause FNSL to diverge.
8. Activity FNSL is intolerant of data errors and insoluble conditions in local areas of the
network.
9. When it diverges, it often fails catastrophically, giving no indication of where the problems
are.
10. Activity FNSL requires the optimal ordering of network nodes. If it detects that a new
ordering is required, a message is printed, activity ORDR is automatically executed, and
activity FNSL continues.
11. The time per iteration with FNSL is longer than that required for the other power flow solution
activities, but fewer iterations are usually needed.
Convergence Testing Used in Prior Releases
The convergence testing described in the preceding section was implemented in PSS
E-30.3. This
section describes the convergence criteria used in earlier releases of PSS
E-30.2.2, set:
Siemens Energy, Inc., Power Technologies International 6-43
PSS
E-29.5.1, set:
VCTOLQ = TOLN
VCTOLV = a large number (e.g., 10.0)
For a Newton-Raphson based power flow solution calculation to be considered converged in
PSS
E-28 and earlier releases, the following conditions must have all been satisfied:
1. The largest active power mismatch at each Type 1 and 2 bus must be less than the
mismatch convergence tolerance, TOLN.
2. The largest reactive power mismatch at the following categories of Type 1 and 2 buses must
be less than the mismatch convergence tolerance, TOLN:
a. Voltage at the bus is not subject to control to a setpoint.
b. Voltage at the bus is subject to control to a setpoint (refer to Setpoint Voltage Con-
trol), but all of the devices participating in the control of bus voltage to its setpoint
are at a reactive power limit.
3. The largest difference between actual and scheduled voltage magnitude in per unit at each
Type 1 and 2 bus where voltage is subject to control to a setpoint, and for which at least one
of the devices participating in the control of bus voltage to its setpoint is not at a reactive
power limit, must be less than TOLN/SBASE.
To match the convergence criterion of PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-44 Siemens Energy, Inc., Power Technologies International
5. Adjustment of the turns ratios of converter transformers at dc transmission terminals and of
ac network transformers controlling dc line quantities.
6. Adjustment of switched shunt devices. When this adjustment option is disabled, discretely
operating switched shunts are moved to their nearest step, if necessary, and all switched
shunts, including continuously operating devices, are held constant. When this adjustment
option is enabled, either all adjustable switched shunts may be adjusted, or continuous
mode switched shunts are subject to adjustment and discrete mode switched shunts are
locked.
7. A non-divergent solution option (refer to Section 6.5.3).
PSS
E program option settings exist for adjustments (1), (2), (3), (5), (6) and (7) above. Activity
OPTN may be used to establish the default setting for each of these adjustment options (refer to
Section 3.3.3). Then, on each entry into activity FNSL, these option settings determine which of the
adjustment options are activated.
The following paragraphs discuss the optional automatic adjustments in more detail. The user is
referred to Section 5.2.1 for additional details on the significance of the control parameters
mentioned below.
Tap Ratio Adjustment
Any two-winding ac transformer represented in the PSS
E working case
may be treated as either: a fixed tap transformer winding; a tap changing transformer winding where
turns ratio may be adjusted to control the voltage at a designated bus; a tap changing transformer
winding where turns ratio may be adjusted to control reactive power flow through the transformer
winding; or a regulating phase shifter winding where phase shift angle may be adjusted to control
active power flow through the transformer winding.
The data values specified for the transformer automatic adjustment control mode and for the two-
terminal dc line ac controlling transformer parameters determine which of the above applies for any
transformer (refer to Transformer Data and Two-Terminal DC Transmission Line Data).
An adjustment monitor is printed at the Progress tab any time an adjustment occurs.
Voltage Control
To be a candidate for automatic tap ratio adjustment as a voltage controlling transformer, an
in-service transformer winding must meet the following conditions:
1. Its automatic adjustment control mode, CODn of Transformer Data, must be set to one.
2. Its specified controlled bus number (CONTn of Transformer Data) must be non-zero, and
bus CONTn must have a bus type code of 1 or 2.
Siemens Energy, Inc., Power Technologies International 6-45
PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-46 Siemens Energy, Inc., Power Technologies International
applied to the voltage error. Setting ACCTAP below its default value of unity reduces the one-to-one
tap movement applied in response to a given voltage error.
The solution parameter TAPLIM, which has a default value of 0.05, defines the maximum ratio
change that may be applied to a transformer during any adjustment calculation; if the STEP of a
transformer exceeds TAPLIM and the controlled voltage is outside of its voltage band, the ratio is
changed by one STEP.
Reducing ACCTAP and/or TAPLIM below their default values may be beneficial on systems with a
high concentration of LTCs or where voltage profile is extremely sensitive to tap settings.
Activities FNSL, NSOL, FDNS, INLF, ACCC, PV Analysis, and QV Analysis also provide for a direct
Newton-based method of tap adjustment, which is enabled by specifying 2 as the tap adjustment
code when selecting adjustment options. In this method, if any tap ratios need to be adjusted, a
simultaneous adjustment is made of all voltage controlling transformers as well as of all Mvar
controlling transformers (refer to Mvar Control) and of all bus voltage magnitudes. Upon conver-
gence of the main power flow iteration, tap ratios of controlling transformers are moved to their
nearest step and the solution refined with tap ratios locked at those positions.
The tap movement deceleration factor, ACCTAP, used in the stepping method described above is
also used in the direct method. It reduces the elements of the voltage error vector used in the
Newton-based direct method. The maximum ratio change solution parameter, TAPLIM, is not used
in the direct method.
In the direct method, compensated limits rather than compensated voltages are used to handle load
drop compensation. The inequality shown above for the discrete method may be expressed in
terms of the voltage magnitude at the controlled bus as follows:
VMIn s (|V
CONTn
| - AV) s VMAn
Adding AV to each term above, the relationship may then be written in terms of compensated limits:
(VMIn + AV) s |V
CONTn
| s (VMAn + AV)
It is possible for the direct method to fail as a result of an overconstrained situation. This is most
likely to occur in radial or tightly looped portions of the network containing several voltage controlling
transformers attempting to control the voltage at multiple buses. Should this occur, tap ratios are
moved to their nearest step and the solution continues with subsequent adjustment of voltage
controlling transformers handled by the discrete method described above.
Mvar Control
To be a candidate for automatic tap ratio adjustment as a Mvar flow controlling transformer, an
in-service transformer winding must meet the following conditions:
1. It automatic adjustment control mode, CODn of Transformer Data, must be set to 2.
2. RMAn and RMIn of Transformer Data define the tap ratio limits of the transformer, and
RMAn must be greater than RMIn.
3. VMAn and VMIn of Transformer Data define the desired Mvar flow limits through the trans-
former, and VMAn must be greater than VMIn. Flow is calculated at the controlling winding
side bus of the transformer and is positive when power is flowing from the controlling winding
side bus into the transformer. When specifying VMAn and VMIn, remember that -100 is
greater than -110!
Siemens Energy, Inc., Power Technologies International 6-47
PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-48 Siemens Energy, Inc., Power Technologies International
Phase Shift Angle Adjustment
To be a candidate for automatic phase shift angle adjustment as a MW flow controlling phase shifter,
an in-service transformer winding must meet the following conditions:
1. Its automatic adjustment control mode, CODn of Transformer Data, must be set to 3.
2. RMAn and RMIn of Transformer Data define the phase shift angle limits in degrees, and
RMAn must be greater than RMIn.
3. VMAn and VMIn of Transformer Data define the desired MW flow limits through the phase
shifter, and VMAn must be greater than VMIn. Flow is calculated at the controlling winding
side bus of the transformer and is positive when power is flowing from the controlling winding
side bus into the transformer. When specifying VMAn and VMIn, remember that -100 MW is
greater than -110 MW!
4. The controlled bus number (CONTn), number of tap positions (NTPn), and compensating
impedance (CRn and CXn) of Transformer Data are ignored.
When phase shift angle adjustment is enabled in activities FNSL, INLF, ACCC, PV Analysis, or QV
Analysis using FNSL, those phase shifters controlling active power flow are checked for adjustment
whenever the largest voltage phase angle change in radians on the previous iteration is less than
the automatic adjustment threshold tolerance, ADJTHR; in activities FDNS, NSOL, ACCC, PV anal-
ysis, or QV analysis using FDNS, this adjustment check occurs following any QV half iteration in
which the largest voltage magnitude change in per unit is less than ADJTHR. MW flow control is not
available in activities SOLV and MSLV. An adjustment monitor is printed on the Progress tab any
time an adjustment occurs.
The phase shift adjustment utilizes a direct method. If any phase shift angles need to be adjusted,
a simultaneous adjustment is made of all regulating phase shifters as well as of all bus voltage
phase angles. ACCTAP and TAPLIM are not used in MW control by phase shifters. The algorithm
is normally able to handle the case of parallel phase shifters with similar flow constraints and angle
limits, and the presence of phase shifters on area interchange boundaries (see below).
When the phase shift adjustment calculation detects a singular matrix, an alarm is printed and the
power flow solution continues with further phase shift adjustment disabled.
Area Interchange Control
Each bus in the PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-50 Siemens Energy, Inc., Power Technologies International
Switched Shunt Adjustment
The significance of switched shunt data and the treatment of switched shunts during power flow
solutions are described in Switched Shunt Data and Section 6.3.14, respectively.
When switched shunt adjustment is enabled, adjustments of switched shunts that control to a
voltage setpoint (refer to rule (3) of Section 6.3.14) occur during each iteration of the power flow
solution activities as described in Setpoint Voltage Control. Switched shunts that control to a voltage
band (refer to rule (4) of Section 6.3.14) are adjusted between network solution iterations. Similarly,
switched shunts that control the reactive power output of another voltage controlling device are
adjusted between power flow iterations.
In adjusting switched shunts that control to a voltage band, the presence of a large number of such
switched shunts among a fairly small number of buses can result in some of them oscillating from
one adjustment cycle to the next. The solution parameter SWVBND specifies the percentage of
switched shunts controlling to a voltage band and for which the voltage at the controlled bus is
outside of the specified band that can be adjusted on any single adjustment cycle. Reducing
SWVBND, thereby decreasing the number of switched shunts that are adjusted on any adjustment
cycle, may be helpful in overcoming such oscillations.
When adjustment of discrete mode switched shunts is enabled in activities SOLV, MSLV, FNSL,
INLF, ACCC, PV Analysis, or QV Analysis using FNSL, such switched shunts are checked for
adjustment whenever the largest voltage magnitude change in per unit on the previous iteration is
less than the automatic adjustment threshold tolerance, ADJTHR; in activities FDNS, NSOL,
ACCC, PV analysis, or QV analysis using FDNS, this adjustment check occurs following any
P-angle half iteration in which the largest voltage phase angle change in radians is less than
ADJTHR.
Automatic Adjustment Solution Parameters
The automatic adjustment threshold tolerance, ADJTHR, the tap movement declaration factor,
ACCTAP, the maximum ratio change solution parameter, TAPLIM, and the voltage band controlling
switched shunt percentage, SWVBND, may be modified with the data changing activity CHNG or
the [Solution Parameters] dialog. They are carried along with the working case as it is saved and
retrieved with activities SAVE and CASE, respectively.
When a new case is read into PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-52 Siemens Energy, Inc., Power Technologies International
Non-Divergent Solution Methodology
The application of the Newton method to the power flow problem calculates a pair of change
vectors: Au for voltage phase angles, and Avmag / vmag
old
for bus voltage magnitudes. In its usual
application, the bus voltages are updated using equations which may be written in the form:
u
new
= u
old
+ (ACCFAC * Au)
vmag
new
= vmag
old
* [1.0 + ACCFAC * (Avmag / vmag
old
)]
where ACCFAC is equal to 1.0.
In the non-divergent solution scheme, ACCFAC is set to 1.0 at the start of each Newton iteration. If
the mismatches that result from the new voltage and angle vectors indicate divergence, the value
of ACCFAC is halved, u
new
and vmag
new
recalculated, and mismatches recalculated. This process
is repeated until either:
the indication of divergence is eliminated. In this case, activity FNSL advances to its
next iteration.
ACCFAC has been reduced to a near zero value without eliminating the indication of
divergence. In this case, activity FNSL is terminated.
The divergence metric used in this inner loop voltage correction is the sum of squares of the MVA
mismatches, expressed in per unit, at all in-service buses in the working case (SUMSQM). The non-
divergent algorithm infers the elimination of divergence when the SUMSQM resulting from the appli-
cation of a set of voltage magnitude and phase angle corrections is less than the SUMSQM at the
start of the iteration multiplied by the improvement factor NDVFCT. That is, a new set of voltages is
accepted if:
SUMSQM
new
< NDVFCT * SUMSQM
old
The non-divergent improvement factor, NDVFCT, which has a default value of 0.99, should never
be greater than 1.0 nor less than or equal to 0.0. With values very close to 1.0, activity FNSL
accepts small reductions in SUMSQM and goes on to the next Newton iteration. As NDVFCT is
reduced, activity FNSL requires larger reductions in SUMSQM before inferring the elimination of
divergence. The setting of NDVFCT is a trade-off between execution time and a possible incre-
mental improvement in total system mismatch level. The user may modify NDVFCT with the data
changing activity CHNG or the [Solution Parameters] dialog.
Up to ten inner loop mismatch calculations are performed, and if SUMSQM has not improved suffi-
ciently by the last attempt (with ACCFAC approximately 0.00195), activity FNSL is terminated. The
voltage vector is set to either its value at the completion of the prior Newton iteration, or to value
corresponding to the last inner loop mismatch calculation, whichever has the smaller value of
SUMSQM.
Convergence Monitor
When the non-divergent solution option is enabled, the standard FNSL convergence monitor (refer
to FNSL) is augmented by two additional columns containing SUMSQM and ACCFAC. In addition,
each inner loop mismatch calculation is reported. Figure 6-10 shows the convergence monitors for
the attempted FNSL solutions of a difficult case, first with the non-divergent solution option disabled,
and then with the non-divergent solution option enabled. DVLIM and NDVFCT are both 0.99.
When the non-divergent solution option is enabled (see Figure 6-10b), the main Newton iteration
mismatch lines are identified in the ITER column as whole numbers, just as they are when the non-
Siemens Energy, Inc., Power Technologies International 6-53
PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-54 Siemens Energy, Inc., Power Technologies International
Figure 6-10. Activity FNSL Convergence Monitor
ITER DELTAP BUS DELTAQ BUS DELTA/V/ BUS DELTAANG BUS
0 5.6995( 151 ) 1.2217( 151 ) 0.07177( 3008 ) 0.14024( 101 )
1 0.5073( 201 ) 0.6370( 205 ) 0.00591( 206 ) 0.00490( 201 )
2 0.0028( 152 ) 0.4046( 206 ) 0.00379( 206 ) 0.00034( 206 )
3 0.0001( 205 ) 2.4734( 3008 ) 0.03639( 3008 ) 0.00266( 206 )
4 0.0065( 154 ) 1.6332( 205 ) 0.03136( 205 ) 0.00779( 101 )
5 0.0253( 205 ) 0.8006( 201 ) 0.08905( 205 ) 0.03293( 101 )
6 0.2468( 205 ) 0.0599( 205 ) 0.17461( 205 ) 0.06537( 101 )
7 0.9226( 205 ) 0.2194( 205 ) 0.13294( 154 ) 0.04131( 101 )
8 0.3062( 205 ) 0.0904( 154 ) 0.13959( 205 ) 0.04873( 101 )
9 0.5686( 205 ) 0.1260( 205 ) 0.08090( 154 ) 0.03244( 101 )
10 0.2733( 205 ) 0.0589( 205 ) 0.82297( 205 ) 0.30216( 101 )
11 7.0235( 206 ) 7.6130( 102 ) 0.99000( 152 ) 4.91214( 206 )
BLOWN UP AFTER 12 ITERATIONS
LARGEST MISMATCH: 495.60 MW 1025.72 MVAR 1139.18 MVA AT BUS 205 [SUB230 230.00]
SYSTEM TOTAL ABSOLUTE MISMATCH: 7280.84 MVA
SWING BUS SUMMARY:
BUS# X-- NAME --X BASKV PGEN PMAX PMIN QGEN QMAX QMIN
3001 MINE -1500.9 9999.0 -9999.0 2959.5* 600.0 -100.0
a. Non-Divergent Solution Option Disabled
Siemens Energy, Inc., Power Technologies International 6-55
PSS
E 32.0
Applying Fully-Coupled Newton-Raphson Power Flow Solution Program Operation Manual
6-56 Siemens Energy, Inc., Power Technologies International
Additional Information
PSS
E GUI Users Guide, Section 11.2.2, Fully-Coupled Newton-Raphson Power Flow Solution
PSS
E 32.0
Applying Decoupled Newton-Raphson Power Flow Solution Program Operation Manual
6-58 Siemens Energy, Inc., Power Technologies International
Figure 6-11. Decoupled Newton-Raphson Convergence Monitor
The solution parameters designating the maximum number of iterations, acceleration, convergence
tolerances, and maximum voltage magnitude change are shared with activity FNSL, while the
blowup threshold and constant power voltage breakpoint (refer to Section 6.3.13) are shared
among all power flow solution activities. The user may modify any of the above solution parameters
with the data changing activity CHNG or the [Solution Parameters] dialog.
Activity NSOL uses an iterative scheme in which the active power-angle calculation is decoupled
from the reactive power-voltage adjustment. It is basically a Newton calculation in which each iter-
ation consists of a pair of half iterations; first, with the voltage magnitudes held constant and new
voltage phase angles determined, then with the phase angles fixed and new voltage magnitudes
calculated.
The rules and characteristics governing the use of activity NSOL are similar to those of activity
FNSL. In addition to those rules enumerated in Section 6.5.1, the following apply:
1. Activity NSOL converges well if fairly uniform X/R ratios are present throughout the network.
2. When the network contains branches with resistance close to or greater than the reactance,
the iteration usually reaches some mismatch level and then begins to diverge, usually
slowly.
3. As the mismatches are reduced, the rate of improvement on successive iterations is slowed.
4. The time per half iteration with activity NSOL is roughly 1/4 of the time per FNSL iteration.
Siemens Energy, Inc., Power Technologies International 6-59
PSS
E GUI Users Guide, Section 11.2.1, Decoupled Newton-Raphson Power Flow Solution
PSS
E 32.0
Applying Fixed Slope Decoupled Newton-Raphson Power Flow Solution Program Operation Man-
6-60 Siemens Energy, Inc., Power Technologies International
6.7 Applying Fixed Slope Decoupled Newton-Raphson Power
Flow Solution
Activity FDNS
The power flow solution activity FDNS uses a fixed-slope decoupled Newton-Raphson iterative
algorithm to solve for the bus voltages needed to satisfy the bus boundary conditions contained in
the working case.
Activity FDNS handles the network connectivity checking option, flat start solution, treatment of
generator reactive power limits, load, generator, switched shunt, FACTS device, and dc line
boundary conditions, selection and application of automatic adjustments, the blowup check, the
scaling of the voltage magnitude change vector, acceleration, convergence criteria, and the non-
divergent solution option, and interrupt control codes in the same way as activity FNSL. The FACTS
device monitor, dc transmission line monitors, largest mismatch tabulation, swing bus summary,
and area interchange violation summary are identical to those of activity FNSL. Refer to
Sections 6.5.1 and 6.5.2 for details.
Activity FDNS is terminated if the voltage magnitude at a bus is driven to very nearly 0.0.
The solution convergence monitor is similar to that of activity FNSL. Each iteration is identified in
the ITER column with its main iteration number, followed by a decimal point, followed by either a
zero (for the angle correction calculation) or a five (for the voltage magnitude correction calculation).
When the non-divergent solution option is enabled, the inner loop mismatch lines are identified as
described above, followed by a second decimal point, followed by the inner loop iteration number.
The solution parameters designating the maximum number of iterations, acceleration, convergence
tolerances, and maximum voltage magnitude change are shared with activity FNSL, while the
blowup threshold and constant power voltage breakpoint (refer to Section 6.3.13) are shared
among all power flow solution activities. The user may modify any of the above solution parameters
with the data changing activity CHNG or the [Solution Parameters] dialog.
Activity FDNS uses an iterative scheme in which the active power-angle calculation is decoupled
from the reactive power-voltage adjustment. It is basically a Newton calculation in which each iter-
ation consists of a pair of half iterations; first with the voltage magnitudes held constant and new
Run Activity FDNS - GUI
Power Flow > Solution > Solve (NSOL/FNSL/FDNS/SOLV/MSLV)
[Loadflow solutions]
Newton Tab OPTION: Fixed slope decoupled Newton-Raphson
Run Line Mode Activity FDNS - CLI
ACTIVITY?
>>FDNS
ENTER ITERATION NUMBER FOR VAR LIMITS
0 FOR IMMEDIATELY, -1 TO IGNORE COMPLETELY:
>>
Interrupt Control Codes
AB, NC, NM, DC, FD, NV
Siemens Energy, Inc., Power Technologies International 6-61
PSS
E 32.0
Applying Fixed Slope Decoupled Newton-Raphson Power Flow Solution Program Operation Man-
6-62 Siemens Energy, Inc., Power Technologies International
the matrix used in the active power-angle solution (B' matrix) of the base case is saved
and then used in power flow solution for a contingency; the changes in the network due
to the contingency are reflected with an additional angle correction vector.
the matrix used in the reactive power-voltage solution (B matrix) remains fixed when
either no bus types switch or bus types switch only from voltage regulating (PV) to reac-
tive power limited (PQ) boundary conditions; the bus type changes are reflected with
an additional voltage corrective vector.
The first technique (using the B' matrix of the base case and the additional angle correction vector
reflecting a contingency) produces the identical voltage angles that would be obtained using the
B' matrix of the contingency case at each iteration during the power flow solution for the contin-
gency. If only bus types switches from PV to PQ occur during an iteration, the B matrix from the
last iteration is used to calculate voltages at the iteration; then the voltages are modified with the
voltage correction vector reflecting bus type switches.
When the tap setting adjustment is enabled in a contingency analysis, minor discrepancies of volt-
ages between the optimized FDNS and the standard FDNS may be found. That is because there
are slight differences in the two methods in the handling of the tap settings in the B matrix.
When the optimized FDNS is enabled in contingency analysis, some matrix calculations are
avoided. Therefore, it typically takes less time to run the contingency calculations than it does when
the standard FDNS solution is used.
Additional Information
PSS
E provides two power flow solutions with inertia/governor re-dispatch to enable the user to
examine system conditions and to obtain a revised generator dispatch for the conditions in which
machine inertia plays the major role in modifying generator output and in which governors play a
more significant role.
The Inertial Power Flow solution gives a quick approximation to system effects in the first 0.5
seconds following a disturbance, during which governor effects are minimal. Generator powers are
principally influenced by machine inertias
The Governor Response solution represents the system several seconds after an event when
governors and exciters have brought the system back to steady-state. The new generator powers
are determined by governor droop and load damping characteristics.
Run Activity INLF - GUI
Power Flow > Solution > N-R solution with inertial governor dispatch (INLF)
[N-R Solution with Inertial / Governor Redispatch]
Run Line Mode Activity INLF - CLI
ACTIVITY?
>>INLF
ENTER 0 FOR INERTIAL SOLUTION
1 FOR GOVERNOR RESPONSE SOLUTION:
>>
Interrupt Control Codes
AB, NC, NM, DC, FD, NV
Power Flow Solution Activity Descriptions PSS
E 32.0
Applying Newton-Raphson Power Flow Solution with Inertial / Governor DispatchProgram Opera-
6-64 Siemens Energy, Inc., Power Technologies International
The inertial and governor response power flow solution activity INLF uses a Newton-Raphson iter-
ative algorithm to solve for the bus voltages needed to satisfy the bus boundary conditions
contained in the working case. The working case is assumed to have appropriate data changes
corresponding to some event imposed upon the solved pre-event power flow case; activity INLF
then solves the network for conditions existing either at about half a second following the event (an
inertial power flow) or at several seconds after the event (a governor response power flow).
Activity INLF can accommodate switching operations that result in islanding and/or load and gener-
ation power unbalances. Swing bus generation changes are redispatched among in-service
generator buses, according to either machine inertial (for an inertial power flow) or governor droop
and damping (for a governor response power flow) characteristics. Data required for the generation
dispatch is specified in an Inertia and Governor Response Data file (refer to Section 6.8.1). Island
average frequencies are estimated and network parameters are made frequency sensitive.
Because INLF permanently changes basic data in the working case to include frequency-depen-
dent effects, it is strongly recommended that a Saved Case file of the working case be made with
activity SAVE prior to using activity INLF.
6.8.1 Inertia and Governor Response Data File Contents
The input stream to activity INLF consists of a series of records in the following format:
I, ID, H, PMAX, PMIN, R, D
where:
Data records may be entered in any order. Input is terminated with a record specifying an I value of
zero.
Any machine for which PMAX = PMIN in the Inertia and Governor Response Data file is treated as
non-dispatchable by activity INLF. Its active power remains at its initial value from the working case
when its islands swing bus generation change is dispatched among the in-service machines in the
island.
I Bus number. Bus I must be present in the working case with a plant sequence
number assigned to it (refer to Plant and Machine Sequence Numbers). No default
is allowed.
ID One- or two-character machine identifier used to distinguish among multiple
machines at a plant (i.e., at a generator bus). ID = 1 by default.
H Machine inertia; entered in pu on MBASE base. H = 4.0 by default.
PMAX Maximum machine active power output; entered in pu on MBASE base. Default
PMAX and PMIN for this machine are set as described in Section 6.8.4.
PMIN Minimum machine active power output; entered in pu on MBASE base. If PMAX
was set to the default value, the value specified for PMIN is ignored, and PMAX and
PMIN for this machine are set as described in Section 6.8.4; otherwise, PMIN = 0.0
by default.
R Governor permanent droop; entered in pu on MBASE base. R = 0.05 by default.
D Turbine damping factor; entered in pu on MBASE base. D = 0.0 by default.
Siemens Energy, Inc., Power Technologies International 6-65
PSS
E 32.0
Applying Newton-Raphson Power Flow Solution with Inertial / Governor DispatchProgram Opera-
6-66 Siemens Energy, Inc., Power Technologies International
6.8.2 Operation of Activity INLF
Activity INLF separates the working case into islands. It generates an alarm and terminates if more
than ten energized islands are detected. Otherwise, it reports the number of islands detected.
Activity INLF allows the user to select the automatic adjustment options to be enabled. As in the
standard power flow solution activities, the default response to the selection request reflects the
current automatic adjustment option settings; refer to Sections 3.3.3 and 6.5.2 and activity OPTN.
Regardless of the selections made, area interchange control is always disabled in activity INLF.
The user must specify the Unit Inertia and Governor Data file containing data records of the form
defined in Inertia and Governor Response Data File Contents. If no file is specified, the default data
described below is used for all machines. If the file does not exist or some other file system error
occurs, an appropriate message is printed. Refer to Section 2.4.1 for the file specification conven-
tions used by activity INLF.
In reading the input file, gross data errors (e.g., H = 0.0) generate an alarm and the corresponding
record is ignored. Data inconsistencies (e.g., PMAX less than initial machine power) generate an
alarm and are fixed and used.
Finally, the user must specify the number of the iteration during which generator reactive power
limits are to be first applied (refer to activity FNSL). When the inertial power flow calculation had
been specified, the default response is -1; otherwise, 99 is the default response (i.e., the same
default used in activities FDNS, FNSL, and NSOL).
Activity INLF checks each island for a swing bus. One (and only one) swing bus must be specified
in each island, and, if no swing bus exists in an island, activity INLF assigns the self-regulating
generator bus with the largest inertial or governor response, as appropriate, as the island swing.
Activity INLF generates an alarm and terminates if:
Any island contains more than one Type 3 bus
A Type 3 bus has no dispatchable in-service machines
An island without a Type 3 bus contains no dispatchable self-regulating generator
buses
An island contains no dispatchable machines.
Activity INLF functions in a manner similar to activity FNSL. Activity INLF provides for the redispatch
of generator powers to allow proper load sharing in a power unbalance condition. This occurs when-
ever the largest angle change in radians during an iteration is less than the automatic adjustment
threshold tolerance, ADJTHR, and any island swing bus power has changed by more than the
mismatch convergence tolerance since the last dispatch. The largest swing bus power change is
tabulated prior to each dispatch calculation.
Island average frequency estimates are updated during the dispatch calculation; they are set to the
average of the dispatchable machine frequencies. All bus and line shunts, admittance loads, line
charging capacitances and line impedances are modified to reflect their dependency on frequency.
Prior to terminating, activity INLF tabulates the frequency estimate and swing bus of each island.
Sections 6.8.3 and 6.8.4 contain details specific to the inertial and governor response power flow
solutions respectively.
Where applicable, activity INLF handles treatment of generator reactive power limits, load, gener-
ator, switched shunt, FACTS device, VSC dc lines, and dc line boundary conditions, the blowup
Siemens Energy, Inc., Power Technologies International 6-67
PSS
E 32.0
Applying Newton-Raphson Power Flow Solution with Inertial / Governor DispatchProgram Opera-
6-68 Siemens Energy, Inc., Power Technologies International
Equation 6.15 assumes that the rate of change of frequency is linear over the half second time
frame.
6.8.4 Governor Response Power Flow Solution
The governor response power flow solution is intended to indicate system conditions that would
exist at least several seconds after the initiation of an event on a steady-state system condition. In
this time frame, it is assumed that voltage regulator and turbine governor effects are influential in
bringing the system to a new steady-state condition, and that changes in generator powers are
determined by governor droop and damping characteristics.
In this solution, generator scheduled voltages are unchanged except as described below, and the
default response to the var limit selection is to honor generator reactive power limits. By default, tap
adjustment by the stepping method (refer to Voltage Control) and phase shift angle adjustment are
enabled, dc taps are unlocked, and switched shunts are active. These settings may be overridden
by the user. Area interchange control and the non-divergent solution option are always disabled.
A generator bus that is specified as an island swing by activity INLF and that was initially at a reac-
tive power limit generates an alarm, and its scheduled voltage is set to its pre-disturbance (i.e., initial
working case) voltage.
For machines for which no data record is successfully read (e.g., if no data file is specified, or if it
does not contain data records for all in-service machines), the following default data, on machine
base (i.e., on MBASE base), is used: R = 0.05 and D = 0.0. When initiated using line mode, PMAX
and PMIN are set to 1.0 and 0.0 respectively for any machine for which no data record is success-
fully read, and to the active power limits contained in the working case (refer to Generator Data) for
any machine for which a data file record was successfully read but PMAX was set to the default
value. The user may specify one of the following methods of assigning default data for PMAX and
PMIN:
Set them to 1.0 and 0.0 respectively for any machine for which no data record is suc-
cessfully read, and to the active power limits contained in the working case (refer to
Generator Data) for any machine for which a data file record was successfully read but
PMAX was set to the default value (Pre Rev-29 approach).
Set them to 1.0 and 0.0 respectively (0.0 to 1.0 for both types).
Set them to the working case active power limits (working case values for both types).
Clearly, the proper specification of MBASE for any machine using default data is essential.
Speed deviation and frequency in per unit of each machine are estimated according to the
equations:
(6.17)
f = 1 + n (6.18)
where D and R are as defined in Section 6.8.1, and P
t
, P
e
, n, and f are as defined in Section 6.8.3.
If, during the solution, the total generation requirement in an island drives all generators in the island
to their high or low power output limits, an appropriate message is printed and activity INLF is
terminated.
n =
P
t
- P
e
D + (1/R)
Siemens Energy, Inc., Power Technologies International 6-69
PSS
E 32.0
Applying Newton-Raphson Power Flow Solution with Inertial / Governor DispatchProgram Opera-
6-70 Siemens Energy, Inc., Power Technologies International
To further examine the solution it is useful to look at the redispatches. In Figure 6-15 the dispatches
are shown for the Base case, the situation subject to inertial redispatch and the situation subject to
governor action.
Inertial redispatch is not controlled by governor action. The amount of power from each unit is a
function of its inertia and it can be seen that some units are producing power above PMAX. This will
slow down the units. Following governor action, machine powers have been reduced to levels at or
within their maximum capabilities.
Figure 6-15. Initial Dispatch Compared to Inertial and Governor Power Flow
Redispatch Levels
6.8.6 Application Notes
The rules and characteristics governing the use of activity INLF are similar to those of activity FNSL
(refer to Section 6.5.1).
It may often be appropriate to precede activity INLF with activity CONL to convert the load boundary
conditions from the typical constant MVA characteristic used in conventional power flow calcula-
Base Case
Inertial
Governor
Siemens Energy, Inc., Power Technologies International 6-71
PSS
E 32.0
Overview: Contingency Analysis Program Operation Manual
6-72 Siemens Energy, Inc., Power Technologies International
6.9 Overview: Contingency Analysis
Contingency analysis covers a variety of analytical investigations performed by both system plan-
ners and operators. The system planners objective is to identify the network elements that will be
required to maintain system operation within planning criteria. The general requirement is to identify
capital investments and operating costs for long term future developments.The system operators
objective is to identify the manner in which the system must be operated to maintain system security
both in the near term (days, weeks, months) with existing network elements or the medium term
(one to three years) during which a limited amount of equipment could be installed.
The basic approach to contingency analysis is to:
Establish generation/demand base case scenarios that are to be tested.
Identify variations of generation and demand for the base cases for the time period of
development or operation.
Identify the tests (contingencies) to be performed for both steady-state and dynamic
analysis and the system conditions that are acceptable or required prior to and during
such contingencies. The tests and required post-contingency conditions are generally
described by Reliability Criteria.
Perform the tests.
6.9.1 Reliability Testing Criteria for Contingency Analysis
Criteria describe tests to be performed and required conditions prior to and during the test condi-
tions. While there may be variations in criteria between electric power utilities, regions and
countries, there is significant commonality.
Typical steady-state tests can include:
Base case with all elements in service.
Single contingencies (N-1). Loss of any transmission line or transformer or generator.
These are often termed probable or credible contingencies.
Double contingencies (N-2). Simultaneous loss of two single-circuit transmission lines,
a double-circuit line or dc bipole. Variations on these contingencies exist worldwide
specifically with respect to the definition of double circuit and the option of non-simul-
taneity of loss (N-1-1). These too are credible or probable contingencies.
Less probable contingences and/or extreme contingencies can include loss of entire
substations or multiple generators.
Typical dynamic testing will include the same family of contingencies and are augmented by repre-
sentation of the severity of the initiating disturbance, which results in the loss of system elements
(three-phase and single-phase faults with normal or delayed clearing times for example).
Acceptable system conditions prior to and subsequent to the contingencies depend on the severity
of the contingency and include:
Voltages within defined normal or emergency limits.
Changes in voltage within defined limits.
Branch loadings within normal or emergency loading limits.
Maintenance or loss of limited amounts of load.
Siemens Energy, Inc., Power Technologies International 6-73
PSS
E
3
2
.
0
O
v
e
r
v
i
e
w
:
C
o
n
t
i
n
g
e
n
c
y
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Table 6-8. Deterministic Reliability Tests
Overview of Deterministic Reliability Tests
Reliability Test Criteria for
Transmission Expansion
Test Conditions Analysis Acceptable Conditions
Normal Steady-State conditions Steady-State Power Flow System within normal loading and voltage limits
Single Contingencies (Credible -
more probable)
Steady-State Power Flow
System within emergency loading and voltage limits
immediately after outage and within normal limits after
system adjustments
Dynamic Analysis Transiently and dynamically stable
Double Contingencies (Credible
- more probable)
Steady-State Power Flow
System within emergency loading and voltage limits
after system adjustment.
Dynamic Analysis Transiently and dynamically stable
Less Probable Contingencies
Supplementary Tests
Steady-State Analysis No voltage collapse or overload cascading
Dynamic Analysis Transiently and dynamically stable
Extreme Contingencies
Supplementary Tests
Steady-State and
Dynamic Analysis
Avoidance of widespread load interruptions, uncon-
trolled cascading and black-outs
Siemens Energy, Inc., Power Technologies International 6-75
PSS
E reporting facilities.
The users response to the results of contingency cases will depend on the study objectives.
A limited system analysis can be performed merely by manually performing the steps outlined in
the basic process. A more detailed analysis, specifically of a large system can involve the simulation
and examination of thousands of contingencies. For this, PSS
E, are described in
Chapter 12 and Section 6.15, Performing PV/QV Analyses.
Applying Voltage Stability Analysis
This type of analysis is similar to transfer limit analysis but is specifically concerned with situations
where voltage control becomes the major factor in determining the power transfer capabilities of a
network. Voltage stability is a phenomenon concerning the eventual collapse of voltage as system
loading is increased and/or power transfers are increased.
Widely accepted measures of a networks vulnerability to voltage instability or collapse are:
Power - Voltage curves (PV) that identify voltage levels in a system as power transfers
increase.
Reactive - Voltage curves (QV) that identify reactive margins versus system voltage
levels.
Both PV and QV curves show limiting operating conditions in a network for both normal and contin-
gency conditions. The procedures for analyzing these conditions with PSS
E are described in
Section 6.15.
Power Flow Solution Activity Descriptions PSS
E 32.0
Overview: Contingency Analysis Program Operation Manual
6-76 Siemens Energy, Inc., Power Technologies International
6.9.3 Applying Probabilistic Reliability Criteria
The behavior of power systems is probabilistic. Loads are always uncertain. The events that cause
the outages my vary, but are always in the form of unplanned events such as lightning strikes, falling
tree limbs, human errors, and so on; these events are thus of a random nature. The weakness of
deterministic reliability analysis is that it does not reflect the probabilistic nature of power system
behavior, but treats every contingency tested equally significant. In deterministic reliability analysis,
every contingency being tested must comply with the acceptable system conditions or is considered
to have failed the test. A failure implies the need for additional system elements (for planning) or an
adjustment of precontingency test conditions (for operations). It is impossible to have zero risk of
system failures in power systems because contingencies are uncontrollable. tn many cases, a deci-
sion must be made to accept a risk as long as it can be technically and financially justified, in other
words keeping risk of system failures within a acceptable range. on the other hand, customers have
the rights to know how often, for how long these outages cause discontinuity of load supply. Prob-
abilistic reliability assessment (see Section 6.13) is provided to answer these questions. The
module uses contingency enumeration technology and consists of a calculation part, which evalu-
ates each contingency and models predefined tripping and corrective action sequences, and an
analysis part, which conducts a detailed analysis on the basis of the evaluated contingency
sequences to calculated following probabilistic indices:
Probabilistic indices of flow overloads
Probabilistic indices of voltage violations
Expected unserved energy
Interrupted power
The basic procedure to perform probabilistic reliability study is:
perform a contingency analysis following the procedure for contingency analysis dis-
cussed in the above section
prepare outage statistics data
perform probabilistic reliability assessment
6.9.4 About Generation Dispatch
Contingency events such as generator outages, the separation of the network into islands and the
shedding of load may lead to imbalances in the power resources and demand for interconnected
ac systems. An individual dispatch mode can be specified for a contingency causing the imbalance.
A DISPATCH keyword should be employed in the contingency specification record that specifies
the contingency, and the record be followed by a group of participating bus specification records
that defines a dispatch group in the Contingency Description Data file (see Section 7.1.4), so that
the change in the boundary condition is allocated among participating generators selected in the
dispatch group.
AC Contingency Analysis also provides an option to perform a common generation dispatch to
handle imbalances for all contingency events. When neither individual dispatch mode nor common
dispatch mode is specified, these imbalances are totally absorbed by the swing bus in the island;
any island without the swing bus is shut down. If both modes are enabled, the common dispatch
acts after generation dispatch is done with the individual dispatch mode for a contingency event.
The common generation dispatch is enabled by selection of one of four dispatch modes and a
dispatch subsystem. Imbalances are then apportioned among machines in the dispatch subsystem
in specified participation factors. For islands without the swing bus, the bus with largest generation
Siemens Energy, Inc., Power Technologies International 6-77
PSS
E 32.0
Overview: Contingency Analysis Program Operation Manual
6-78 Siemens Energy, Inc., Power Technologies International
Steps 3 through 6 in the above list are repeated for each island in the network until a load/generation
balance is attained.
6.9.5 Tripping Simulation and Corrective Action Analysis
A complete contingency analysis for a contingency event includes a power flow solution on the
working base case with the contingency imposed, following sequences including a tripping simula-
tion and a corrective action analysis.
The tripping simulation is discussed in section 6.12.7 and is used to simulate protection relay oper-
ations, system adjustments by operators following a contingency event and a system cascading
failure.
A power flow solution may have any number of operating limit violations, and these problems can
be alleviated by corrective actions. The ac corrective action analysis is formulated as an optimal
power flow problem with the objective of minimizing load curtailment, MW generation re-dispatch,
transformer phase angle adjustment, off-line generator active power dispatch, tap setting adjust-
ment and switched shunt controls. It includes a standard ac power flow solution with local automatic
adjustments, power system network linearization, and a linear programming solution to relieve the
overload and voltage limit violations. Contingency analysis may start with corrective action analysis
enabled to automatically specify corrective actions for each contingency. Corrective action analysis
may be also used to only clean up the current working case. The Corrective Action Analysis is
discussed in Section 6.11.
Recognizing that thermal ratings and voltage limits in a power system may sometimes be treated
as soft limits, the algorithm relaxes the hard limits on the constraints in case of infeasibility, and
returns a solution with some minor violations. Hence, incorporation of the soft limits reduces the like-
lihood of infeasible solutions, which is particularly useful during contingency analysis when a large
number of corrective action solutions may need to be performed automatically.
6.9.6 Substation Reliability Assessment Analysis
Substations are junction points of power transfer between generation and transmission systems, or
transmission and distribution systems. Substations are a critical part of power systems and play an
important role in reliability analysis of power systems. Reliability of a substation is measured in
terms of the frequency and duration of substation related outage events leading to system not
meeting performance criteria. The reliability results could be used for:
comparing substation/network configuration alternatives
evaluating the sensitivity of substation performance to outage statistics
evaluating the sensitivity of substation performance to equipment rating
evaluating the sensitivity of substation performance to load level
determining the impact of equipment maintenance on reliability.
Substation reliability assessment analysis uses state enumeration method, similar to probabilistic
reliability assessment, and is discussed in Section 6.14.
Siemens Energy, Inc., Power Technologies International 6-79
PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-80 Siemens Energy, Inc., Power Technologies International
Figure 6-16. File Path and Process for AC Contingency Analysis
6.10.1 AC Contingency Solution Options
Two AC Contingency Solution functions are described here:
ACCC API (the basic ac contingency solution function)
ACCC_WITH_DSP API (the ac contingency solution with a generation dispatch function to
handle imbalances between power resources and demand that may occur as a result of
applying a contingency).
The following input data is specified to both of these functions (Table 6-9).
Table 6-9. AC Contingency Solution Options
Option Description
Solution options
The desired solution options to be applied during power flow calculations for
obtaining post-contingency states (see Section 6.2)
Tap adjustment:
Lock taps (default)
Stepping
Direct
Area interchange control:
Disabled (default)
Tie lines only
Tie lines and loads
Switched shunt adjustments:
Lock all
Enable all (default)
Enable continuous, disable discrete
Siemens Energy, Inc., Power Technologies International 6-81
PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-82 Siemens Energy, Inc., Power Technologies International
The following additional input data is specified to the ACCC_WITH_DSP API (Table 6-10):
Table 6-10. AC Contingency Solution with Generation Dispatch Options
Option Description
Dispatch Mode Dispatch codes for generation dispatch calculations in ACCC analysis.
Subsystem
machines
(Reserve)
Participating machines are connected to dispatch subsystem buses and have
positive active power generation. Each machine's participation factor is its
reserve (PT-PG or PG-PB) with positive values. If a Unit Inertia and Governor
Data file is specified, machine active power limits are taken from it; otherwise,
the machine active power limits in the working case are used. In generation
dispatch analysis, generator active power limits are adjusted by the following
rules. If PT had been set to the default value, the larger value of PG (its
existing MW output) and machine power base (MVA base) will be used as PT; If
PT of a machine is less than its PG, the PT is set equal to the PG. If PB of a
machine had been set to the default value, it is set to zero; if PB of a machine
is less than its PG, the PB is set equal to the PG.
Subsystem
machines
(Pmax)
Participating machines are connected to dispatch subsystem buses and have
positive active power generation. Each machine's participation factor is its
maximum active power generation with positive values. If a Unit Inertia and
Governor Data file is specified, maximum machine active power limits are taken
from it; otherwise, the maximum machine active power limits in the working case
are used. PT is adjusted by the rules discussed in Dispatch Mode of Machine
Reserve.
Subsystem
machines
(Inertia)
Participating machines are connected to dispatch subsystem buses and have
positive active power generation. Each machine's participation factor is its inertia
constant. For machines for which no data record is successfully read, an inertia
constant of 4.0 on machine base is used.
Subsystem
machines
(Governor
droop)
Participating machines are connected to dispatch subsystem buses and have
positive active power generation. Each machine's participation factor is its
governor permanent droop. For machines for which no data record is success-
fully read, a droop constant of 0.05 on machine base is used.
Dispatch system
Select the subsystem for the generation dispatch. The subsystem is predefined
in a subsystem description file. All subsystem buses with one or more in-service
machines where active power generation is positive are participating in the
generation dispatch. If several islands exist in the system, participating
machines for each island are connected to dispatch subsystem buses in the
island.
Unit Inertia and
Governor Data
File
(*.inl) a required file if the generation dispatch is enabled and either the inertial or
governor droop dispatch method is selected. If the PMAX or reserve method is
selected, the specification of this file is optional. If a file is specified, machine
active power limits are taken from it; otherwise, the machine active power limits
in the working case are used.
Siemens Energy, Inc., Power Technologies International 6-83
PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-84 Siemens Energy, Inc., Power Technologies International
The AC Contingency Multiple Run Report function (refer to Section 6.10.11) may be
used to produce a variety of tabular reports of results from up to nine Contingency Solu-
tion Output files.
The auxiliary program AcccBrwsGrid, which is documented in its Help files, allows
spreadsheet-like manipulations of the results from a single Contingency Solution
Output file.
For branches, loadings printed are MVA loadings. For each monitored non-transformer branch, the
percent loading is either the percent current or the percent MVA loading, according to the non-trans-
former branch percent loading units program option setting (refer to Section 3.3.3 and activity
OPTN).
For monitored transformers, the percent loading is either the percent current or the percent MVA
loading, according to the transformer percent loading units program option setting.
When percent current is used for non-transformer branches or two-winding transformers, both the
MVA loading and percent current loading are taken from the end of the branch with the larger
current loading. If the current loadings at each end are identical, both the MVA loading and the
percent current loading are taken from the end of the branch with the larger MVA loading.
When percent MVA is used for non-transformer branches or two-winding transformers, both the
MVA loading and percent MVA loading are taken from the end of the branch with the larger MVA
loading. If the MVA loadings at each end are identical, both the MVA loading and the percent MVA
loading are taken from the end of the branch listed as the from bus.
For monitored three-winding transformer windings, both the MVA loading and percent loading are
calculated at the winding bus.
The flow across an interface is taken as the sum of the MW flows of its members. For three-winding
transformer windings, the MW loading is calculated at the winding bus as power flowing into the
transformer. For other members, the MW flow is calculated at its metered end in the from bus (i.e.,
the first bus specified in entering the branch; refer to Monitored Element Data File Contents) toward
the to bus direction. The percent loading for each interface is its percent MW loading based on its
MW loading and its interface MW rating from the selected rating set.
The user selects those subsystems where bus voltages are to be monitored, the types of voltage
check (voltage band or deviation from base case values), and threshold values by specifying
records in the Monitored Element Data file (refer to Voltage Monitoring Records). In the AC Contin-
gency Single Run Report function and the AC Contingency Multiple Run Report function, voltage
violations reports are presented in groups corresponding to the MONITOR VOLTAGE data records
specified in the Monitored Element Data file. One (or two if the second r value on the MONITOR
VOLTAGE record is specified) reports are generated for each MONITOR VOLTAGE record to be
processed. Report blocks are printed in the order in which the MONITOR VOLTAGE data records
are contained in the Monitored Element Data file.
Each voltage range record results in a tabulation of those buses from the set of buses defined on
the data record where voltage is below the low voltage threshold (i.e., the first r value on the data
record), followed by the list of buses where voltage is above the high voltage threshold (i.e., the
second r value on the data record).
Each voltage deviation record results in a tabulation of those buses from the set of buses specified
on the data record where voltage drop from their base case values exceeds the voltage drop
threshold (i.e., the first r value on the data record), followed by the list of buses where voltage rise
exceeds the voltage rise threshold (i.e., the second r value on the data record).
Siemens Energy, Inc., Power Technologies International 6-85
PSS
E, and is initiated by
selecting the ACCC Post Processor (AcccBrwsGrid) entry from the PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-86 Siemens Energy, Inc., Power Technologies International
Load Contingencies
When the SET, CHANGE, INCREASE, DECREASE or MOVE contingency commands operate on
LOAD, they operate on the total nominal (i.e., not voltage adjusted) load of the in-service loads
connected to the specified bus. For each load at the bus, its pre-contingent nominal load is the sum
of the nominal constant power, constant current and constant admittance load components; the
effect of any load multiplier associated with an Optimal Power Flow adjustable bus load table is
applied to the constant power component in calculating the total nominal load.
When these contingency commands employ the MW keyword, only those in-service loads at the
specified bus where pre-contingent nominal active power load is positive are modified in these
contingency events.
For the MOVE contingency command, in-service connected load with positive nominal active power
must exist at the FROM bus, and at least one in-service load, regardless of its nominal active power
specification, must be present at the TO bus. Except for the destination bus in the MOVE contin-
gency command, the total active power change is assigned to individual loads at the bus in
proportion to their individual total nominal active power loads. For each participating load at the bus,
its reactive power is modified such that the reactive power to active power ratio remains constant;
the relative proportions of constant power, constant current and constant admittance load compo-
nents also remain constant.
When these contingency commands employ the PERCENT keyword, active and reactive power
components of all three load characteristics of all in-service loads at the bus are both adjusted by
the specified percentage of their pre-contingent nominal load. Thus, the reactive power to active
power ratio remains constant, and the relative proportions of constant power, constant current and
constant admittance load components remain constant. For the MOVE contingency command, in-
service load must be present at both the FROM and TO buses.
In the MOVE contingency command, all nominal active and reactive power load that is removed
from the FROM bus is transferred to the TO bus. Each such load component retains its original load
characteristic (constant power, constant current or constant admittance).
Shunt Contingencies
When the SET, CHANGE, INCREASE, DECREASE or MOVE contingency commands operate on
SHUNT, they operate on the nominal (i.e., at 1.0 pu voltage) shunt admittance of the in-service fixed
shunts connected to the bus; any switched shunt connected to the bus is not affected by these
commands.
When these contingency commands employ the MW keyword and the initial conductance (i.e., the
active power component) of shunt admittance is non-zero, the shunt susceptance (i.e., its reactive
power component) is modified such that the susceptance to conductance ratio remains constant.
When these contingency commands employ the MW keyword and the initial conductance of shunt
admittance is zero, the specified change is applied to the conductance but the susceptance is
unchanged.
When these contingency commands employ the MVAR keyword, the specified change is applied to
the susceptance, but the conductance is unchanged.
When these contingency commands employ the PERCENT keyword, the conductance and suscep-
tance components of all in-service fixed shunts at the bus are both adjusted by the specified
Siemens Energy, Inc., Power Technologies International 6-87
PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-88 Siemens Energy, Inc., Power Technologies International
6.10.8 Appending Data to a Contingency Solution Output File
The Append ACCC function (the APPEND_ACCC API) is used to output system conditions of a
contingency case solution, as contained in a designated Saved Case file, in the form of a Contin-
gency Solution Output file. This is useful for the situation in which the specification and/or solution
of a contingency case exceeds the capability of the AC Contingency Solution function, but the user
wishes to have the contingency case reported along with, and in the same format as, the contin-
gency cases calculated by the AC Contingency Solution function. The user specifies the following
data items:
1. An append output option flag indicating either that the results for the contingency case spec-
ified in 4. below are to be appended to the existing Contingency Solution Output file
specified in 5. below, or that a new Contingency Solution Output file is to be written
containing results for both the base case specified in 3. below and the contingency case
specified in 4. below.
2. The name of the Distribution Factor Data file to be used. This file specifies the network
elements to be monitored. When appending results to an existing Contingency Solution
Output file from a previous execution of the AC Contingency Solution function, the Distribu-
tion Factor Data file must be the same one specified to the AC Contingency Solution
function.
3. The name of the Saved Case file containing the pre-contingency power flow case. The
Saved Case in this Saved Case file must be the same case that was present as the PSS
E
working case when the Distribution Factor Data file specified in 2. above was constructed
with activity DFAX. It must also be the Saved Case from which the contingency case was
formed and where the solution is contained in the Saved Case file specified in 4. below.
4. The name of the Saved Case file containing the contingency case solution where the results
are to be placed in the Contingency Solution Output file specified in 5. below. The contin-
gency case must have been formed by imposing status, boundary condition, and/or other
data changes in the pre-contingency case specified in 3. above, and then solved using one
or more of the power flow solution activities.
5. The name of the Contingency Solution Output file into which the results of the contingency
case specified in 4. above are to be placed. When the append output option flag in 1. above
indicates that the contingency case results are to be appended to an existing Contingency
Solution Output file, the name of that file must be specified here, and it must be compatible
with the Distribution Factor Data file specified in 2. above. This function is able to append to
Contingency Solution Output files created by PSS
E.
6. A contingency label of up to 12 characters used to identify the contingency.
7. The number of text lines to be used to describe the contingency. At least one, and no more
than 16, such lines may be supplied.
8. Text lines of up to 120 characters each of which are used to describe the contingency. The
number of text lines specified must be identical to the value specified in 7. above.
Run Append to AC Contingency Solution Output File - GUI
Power Flow > Reports > Append to AC Contingency solution output file
[Append to AC Contingency Solution Output File]
Siemens Energy, Inc., Power Technologies International 6-89
PSS
E.
The following input data is specified to this function:
Run Activity AC Contingency Report - GUI
Power Flow > Reports > AC Contingency reports
[AC Contingency Reports]
Interrupt Control Codes
AB
Table 6-11. AC Contingency Single Run Report Options
Option Description
Base case rating
Defines line loading limits used in determining overloads in base case. Default is
set in program options (see activity OPTN).
Contingency case rating
Defines line loading limits used in determining overloads in contingency case.
Default is set in program options (see activity OPTN).
Report format
Reports that can be imported into a spreadsheet program:
Spreadsheet overload report
Spreadsheet loading table
Available capacity table
Non-converged network conditions
Reports that are available only for visual inspection:
.Non-spreadsheet overload report
Non-spreadsheet loading table
Report format (continued)
Non-spreadsheet corrective actions report: a report of overloads and
voltage violations in each network condition where corrective actions are
specified to alleviate the violations, overloads and voltage violations in
corresponding post-corrective action network condition, as well as
specified corrective actions (see Section 6.12.10)
Power Flow Solution Activity Descriptions PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-90 Siemens Energy, Inc., Power Technologies International
Exclude interfaces from
the report
Enable or disable (default) exclusion of interface loadings from all reports.
Perform voltage limit
check
The user selects those subsystems where bus voltages are to be monitored, the
types of voltage check (voltage band or deviation from base case values), and
threshold values by specifying records in the Monitored Element Data file (see
Section 7.1.3). In the dialog, however, is the facility to specify the Minimum
contingency case voltage change for range violations.
If enabled (default), buses where out-of-limits voltages in contingency cases
differ from their base case voltages by less than this minimum change parameter
are omitted from any voltage range checking reports. Also, a network condition
is included in the report if the following conditions are satisfied:
The number of buses in the largest disconnected island is greater than or
equal to the threshold.
The number of violations of all three voltage violation categories is greater
than or equal to each respective threshold.
When voltage limit checking is disabled a network condition is included in the
report if the number of buses in the largest disconnected island is greater than or
equal to the threshold.
Exclude elements with
base case loading viola-
tions from contingency
reports
Enable or disable (default) exclusion of monitored branches and interfaces that
show loading violations in the base case from being checked and reported in
overload reports of contingency cases.
Exclude elements with
base case voltage viola-
tions from contingency
reports
Enable or disable (default) exclusion of monitored buses that show voltage
range violations in the base case from the corresponding check in contingency
case reports. This flag applies only to the voltage range violation checks of the
overload reports.
Exclude cases with no
overloads from non-
spreadsheet overload
Enable or disable (default) exclusion of cases with no overloads from the non-
spreadsheet overload report or the non-spreadsheet corrective actions report.
This flag may be used to limit the number of records appearing in these reports.
When disabled, reports identify all converged network conditions; it may indicate
that some network conditions have no monitored element loading violations.
When enabled, reports will identify all network conditions and it may indicate that
some network conditions have no overloaded monitored elements.
Report post-tripping simu-
lation solutions
When enabled, each post-tripping network condition that satisfies the filter
criteria is included in reports from 1 to 6. When disabled (default), post-tripping
network conditions are excluded from reports from 1 to 6 (see Section 6.12.7 for
information about tripping simulation).
Number of low voltage
range violations
Filter limiting the converged network conditions included in a report. (default = 0)
Number of high voltage
range violations
Filter limiting the converged network conditions included in a report. (default = 0)
Number of voltage devia-
tion violations
Filter limiting the converged network conditions included in a report. (default = 0)
Number of buses in the
largest disconnected
island
Filter limiting the converged network conditions included in a report. (default = 0)
Table 6-11. AC Contingency Single Run Report Options
Option Description
Siemens Energy, Inc., Power Technologies International 6-91
PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-92 Siemens Energy, Inc., Power Technologies International
the ITERATION LIMIT EXCEEDED or TERMINATED BY NON-DIVERGENT OPTION
condition with bus and/or system mismatches exceeding the corresponding mismatch
tolerances described above.
the TERMINATED BY CONSOLE INTERRUPT condition.
the SINGULAR JACOBIAN OR 0.0 VOLTAGE condition.
Such network conditions are identified in the non-Spreadsheet overload report and the non-
converged network conditions report, and excluded from all other reports.
The converged network conditions included in a report may be limited by filter criteria. Only those
contingencies that satisfy the filter criteria are reported. The following filter criteria are user
assigned; the first two apply to all network conditions, while the last two apply only to contingency
cases:
Number of low voltage range violations.
Number of high voltage range violations.
Number of voltage deviation violations.
Number of buses in the largest disconnected island.
When voltage limit checking is enabled, a network condition is included in the report if the following
two conditions are satisfied:
1. For contingency cases, the number of buses in the largest disconnected island is greater
than or equal to the threshold.
2. The number of violations of the first two (for bases cases) or all three (for contingency cases)
voltage violation categories is greater than or equal to each respective threshold.
When voltage limit checking is disabled, a contingency case is included in the report if the number
of buses in the largest disconnected island is greater than or equal to the threshold.
Clearly, specifying a zero for any of the filtering criteria disables filtering according to that criteria.
6.10.10 Single Run Report Formats
In each report format, the first page includes a summary of the linear network analysis data files
used in the AC Contingency Solution function along with the percent loading units (MVA or current)
for transformers and non-transformer branches, which are based on the percent loading units
program option settings at the time the AC Contingency Solution function was executed. If the
Contingency Solution Output file was written by PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-94 Siemens Energy, Inc., Power Technologies International
MVA and a percentage loading of 117%. While the MVA flow is apparently less than the branch
rating, it must be remembered that the rating is based on branch current capacity and 100% voltage.
Ratings are assumed to have been entered as:
MVA
rated
= \3 E
base
I
rated
10
-6
where:
For this contingency, the MVA flow shown is concurrent with a voltage of 0.832 pu. This corre-
sponding level of current is 17% higher than the branches current capacity.
The monitored interface listed as suffering an overload is identified in the jdmsavnw.mon file, indi-
cating that the interface comprises the three branches shown (see Figure 6-17).
Figure 6-17. Sample Monitored Interface Description
E
base
= the base voltage in volts of the bus to which the terminal of the branch
is connected.
I
rated
= the rated phase current in amps.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
6
-
9
5
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
A
c
t
i
v
i
t
y
D
e
s
c
r
i
p
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
e
r
f
o
r
m
i
n
g
A
C
C
o
n
t
i
n
g
e
n
c
y
A
n
a
l
y
s
i
s
Figure 6-18. Overload Report from AC Contingency Analysis
a.)
b.)
Power Flow Solution Activity Descriptions PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-96 Siemens Energy, Inc., Power Technologies International
Following the overloaded element list, the report shows buses where voltage falls outside the spec-
ified range that has an upper threshold of 1.50 pu (a value of 1.05 is more adequate) and a lower
threshold of 0.93 pu. The contingency initiating the voltage reduction is indicated by the bus
number. Note that the list of buses outside the range is limited for only two in Figure 6-18. Finally,
following the listing of the overloaded elements and buses outside Range, the report presents a
legend indicating for each contingency name, the details of the disturbance.
In the non-spreadsheet overload report, for each monitored element printed, the pre-contingency
and post-contingency loadings, the rating and the post-contingency percent loading are listed.
Loading Table
Each converged network condition that satisfies the filter criteria described above (refer to
Section 6.10.1) is included in the loading table. Loadings on monitored branches and interfaces are
calculated as described in Section 6.10.3. For each monitored element, the selected rating, loading
and percent loading are reported.
In the non-spreadsheet format, results are reported in tabular form with four contingency cases per
table. Each group of contingency cases contains a page summarizing the contingency cases being
reported. For each contingency, the contingency label and the events defining the contingency are
listed. The summary page is followed by the loading table. For each monitored element, this table
lists its rating, loading, and percentage loading in the base case network solution, and the loading
and percentage loading for each of the contingency cases reported. Any percentage loading above
the specified percentage threshold is followed by an asterisk ( - ). When the multi-section line
reporting option is enabled, all members of each monitored multi-section line are reported.
In the spreadsheet format, the monitored flow results are reported in a table that include the
following fields: the monitored element description, the network condition label, the elements rating,
the elements flow, and the elements percent loading. An asterisk ( - ) is printed between the bus
number and name of the bus at the end of the branch at which the loading and percent loading are
taken. A subsequent table identifies event descriptions for each network condition label.
Single branches are listed first, either in the order in which they were specified in the Monitored
Element Data file, or in ascending numerical or alphabetical order, according to the option selected
during the execution of activity DFAX (refer to Section 7.1.5). When interface loadings are included
in the report, the branch loadings are followed by the loading on interfaces in the order in which they
were specified.
When the voltage limit checks are enabled, each loading table is followed by the voltage violations
report.
In the non-spreadsheet format, the voltage violations report is presented as described in
Section 6.10.3; the report is limited to only those buses with voltage violations. For each bus
printed, both its contingency case and base case values are printed. Any report block for which no
violations are detected is omitted from the report.
In the spreadsheet format, the voltage violations report includes all buses identified by the moni-
toring data records.
In the spreadsheet format, a final table identifies event descriptions for the converged network
conditions tabulated in the report.
Figure 6-19 shows a partial sample of a loading report obtained using the savnw.sav power flow
case.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
6
-
9
7
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
A
c
t
i
v
i
t
y
D
e
s
c
r
i
p
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
e
r
f
o
r
m
i
n
g
A
C
C
o
n
t
i
n
g
e
n
c
y
A
n
a
l
y
s
i
s
Figure 6-19. Sample Loading Report
Power Flow Solution Activity Descriptions PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-98 Siemens Energy, Inc., Power Technologies International
It can be seen in the report that there are eleven monitored elements, two of which are defined inter-
faces. Their ratings, flow and percentage loadings are listed for the base case and subsequently for
each contingency for which a converged case was obtained.
Available Capacity
The available capacity report provides a worst case summary over all converged system conditions
that satisfy the filter criteria. In this report, each monitored element with a non-zero rating in the
specified rating set is printed no more than once: for the system condition (base case or contin-
gency case) in which its available capacity index is smallest.
Two input data items may be specified to control the contents of the available capacity table: the
maximum number of elements in the available capacity table data item may be used to restrict the
table to the < n > monitored elements with the smallest available capacity indices; the cutoff
threshold for the available capacity table data item may be used to restrict the table to those moni-
tored elements where available capacity indices are less than the specified cutoff threshold.
For each monitored element reported, this table lists: its rating; its base case loading; its worst case
loading, percentage loading, available capacity index, and the system condition (the contingency
case label or BASE CASE) in which the worst case loading occurs. The report indicates the number
of other system conditions in which the monitored element has the same available capacity index
as in the tabulated worst case, and the impact on the monitored element.
Base case (the column headed BASE) and worst case (MAXIMUM) loadings are MVA loadings for
branches and MW loadings for interfaces. Element loadings in the corresponding system condition
are tabulated in the column headed IMPACT. For branches, the IMPACTs are either MVA loadings
or current loadings expressed as MVA, according to the transformer and non-transformer branch
percent loading units program option settings; for interfaces, the IMPACTS are MW loadings. Worst
case percentage loadings are also calculated according to the transformer and non-transformer
branch percent loading units program option settings as described in Section 6.10.3. An available
capacity index (the column labeled AVAILABLE) is listed for each tabulated monitored element. The
available capacity index is the difference between the RATING and the IMPACT.
In the available capacity report, monitored elements are printed in order of increasing available
capacity index. Clearly, elements with negative indices are overloaded in the worst case system
condition.
This report is terminated with descriptions of those contingency cases that were identified as worst
case system conditions for one or more monitored elements. This contingency case summary lists
contingency cases in the order in which they were calculated.
Figure 6-20 shows the capacity report for the savnw.sav power flow case. It can be seen that the
Interface West suffers the greatest capacity deficiency, followed by the branches from bus 154 to
buses 153 and 203. Other listed branches and interface show, for the contingencies tested (and
converged) an available capacity for increased flow.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
6
-
9
9
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
A
c
t
i
v
i
t
y
D
e
s
c
r
i
p
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
e
r
f
o
r
m
i
n
g
A
C
C
o
n
t
i
n
g
e
n
c
y
A
n
a
l
y
s
i
s
Figure 6-20. Sample Capacity Report from the savnw.sav Power Flow Case
Power Flow Solution Activity Descriptions PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-100 Siemens Energy, Inc., Power Technologies International
Non-converged Network Conditions
The non-converged network conditions report identifies each network condition that fails to meet
the convergence criteria as described above (refer to Section 6.10.9). The report format is suitable
for import into a spreadsheet program.
The user specified values of bus mismatch converged tolerance and system mismatch converged
tolerance are identified following the report title. A table of non-converged networks is presented
that identifies: the contingency label, the largest bus mismatch magnitude, the system mismatch
magnitude, and the termination condition from the AC Contingency Solution function. A subsequent
table identifies event descriptions for each contingency label.
For the savnw.sav power flow case, Figure 6-21 shows the Report. It can be seen that five contin-
gencies have failed to converge. The user, at this point has the option of re-testing the ac
contingencies using the non-divergent power flow solution with this automated approach or to
examine each contingency heuristically using a variety of solution methods and solution controls.
Often the problem is a lack of voltage support.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
6
-
1
0
1
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
A
c
t
i
v
i
t
y
D
e
s
c
r
i
p
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
e
r
f
o
r
m
i
n
g
A
C
C
o
n
t
i
n
g
e
n
c
y
A
n
a
l
y
s
i
s
Figure 6-21. Non-Converged Network Report Example
Power Flow Solution Activity Descriptions PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-102 Siemens Energy, Inc., Power Technologies International
Corrective Action Report
To have corrective action reports, contingency analysis output file must be produced by multiple-
level contingency analysis initiated with perform corrective actions (see Section 6.12).
Each network condition, which causes violations and for which corrective actions are specified to
relieve the violations, is included in the non-spread sheet corrective action report, if it satisfies the
filter criteria. After each network condition is solved, flow overloads and bus voltage violations are
identified by the operating limits specified prior to multiple level contingency analysis instead of the
rating setting and percent of rating specified in single run ACCC report.
The corrective actions results also depend on running mode specified prior to multiple contingency
analysis. The running mode is specified according to selections of three options in contingency
analysis: perform multiple contingency analysis, perform tripping simulation (see Section 6.12.7)
and perform corrective actions (see Section 6.12.10). When contingency analysis is initiated with
perform tripping simulation, flows and voltages in post-tripping network conditions are checked
against limits, corrective actions are then specified to alleviate flows and voltages violations if any.
To reproduce the complete sequences that had been simulated, and present corrective actions and
violations that had been identified and activated corrective actions during contingency analysis,
some options in AC Contingency Single Run report are not allowed to select, but set by programs
when the report option is a corrective action report as follows:
Enabled:
- Perform voltage limit check
- Report post-tripping simulation solutions
Not enabled:
- Exclude interfaces from report
- Exclude elements with base case loading violations from contingency reports
- Exclude elements with base case voltage range violations from contingency
reports
- Exclude cases with no overloads from non-spreadsheet overload report
Taken from the rating set specified prior to contingency analysis:
- Base case rating
- Contingency rating
- Percent of flow rating
In the summary page, input files and options used in contingency analysis are presented. For each
network condition that satisfies conditions, post-contingency solution is reported first, then followed
by post-tripping solution and post-corrective action solution. Each solution is presented in the
format similar to non-spread sheet overload report format. For each monitored element printed, the
pre-contingency loading, one of post-contingency, post-tripping and post-corrective action loading,
the rating and the corresponding percent loading are listed. For each bus printed, voltage in one of
post-contingency, post-tripping and post-corrective action solutions, base case voltage are printed.
Violations in solutions are followed by correctives actions specified for the network condition.
Corrective actions are grouped by control types: generator active power dispatch, load shedding,
phase shift angle adjustment, off-line generator active power dispatch, tap setting adjustment and
switched shunt control. In each division, the initial value and the change of a control are reported in
Siemens Energy, Inc., Power Technologies International 6-103
PSS
E
3
2
.
0
P
e
r
f
o
r
m
i
n
g
A
C
C
o
n
t
i
n
g
e
n
c
y
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 6-22. Sample Corrective Action Report
Siemens Energy, Inc., Power Technologies International 6-105
PSS
E.
The following input data is specified to this function (Table 6-12):
Run AC Contingency Multiple Run Report - GUI
Power Flow > Reports > Multiple AC Contingency run report
[Multiple AC Contingency Run Report]
Interrupt Control Codes
AB
Table 6-12. AC Contingency Multiple Run Report Options
Option Description
Monitored elements summary
Flag to enable (default) or disable the printing of the Monitored Element
Summary Report.
Missing monitored elements
Flag to enable (default) or disable the printing of the Missing Monitored
Elements Report.
Missing monitored voltage
buses
Flag to enable (default) or disable the printing of the Missing Monitored
Voltage Buses Report
Missing contingencies
Flag to enable (default) or disable the printing of the Missing Contingencies
Report
Non-converged contingencies
Flag to enable (default) or disable the printing of the Non-converged Contin-
gencies Report
Contingency legend
Options for the Contingency Summary Report and the Contingency
Legend. Control options are:
No: contingency summary and legend reports disabled
Complete master legend report only
Reduced contingency legend with each table in which contingencies
are referenced
Both master legend report and a reduced contingency legend with
each table in which contingencies are referenced (default)
Loading violations
Options for the Loading Violations Report. Control options are:
No: loading violation reports disabled
Base case and worst case contingency violations only (default)
Base case and all contingency violations
Base case, worst case contingency, and all contingency violations
Power Flow Solution Activity Descriptions PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-106 Siemens Energy, Inc., Power Technologies International
Voltage violations
Options for the Voltage Violations Report. Control options are:
No: voltage violation reports disabled
Base case and worst case contingency violations only
Base case and all contingency violations
Base case, worst case contingency, and all contingency violations
Column headings
Selection of one of the folowing to be used as a column heading to identify
the run being reported in the column:
AC Contingency report filenames (default)
Saved case filenames as contained in the ac report files
Base case rating set
Rating set to be used in determining base case monitored element loading
violations (default set by activity OPTN)
Rate A, B, C
Contingency case rating set
Rating set to be used in determining contingency case monitored element
loading violations (default set by activity OPTN)
Rate A, B, C
Include interface loading
violations
Flag to enable or disable (default) violation checking and reporting of inter-
face loading violations.
Exclude elements with base
case loading violations from
contingency reports
Flag to enable or disable (default) exclusion of base case loading violations
Exclude elements with base
case voltage range violations
from contingency reports
Flag to enable or disable (default) exclusion of voltage range violations
Percent of flow rating for
reporting
Percent of flow rating for reporting an element in the loading violation
reports (default = 100.00)
Percent of flow rating for
counting in worst case contin-
gency violation reports
This value must be at least as large as Percent of flow rating for reporting
(default = 100.00)
Minimum contingency case
flow change for reporting and
counting
Loading change from a monitored elements base case loading to enable
the checking of its loading in the contingency case loading violation reports.
(default = 0.0, to check all monitored elements)
Minimum contingency case %
loading increase for overload
Change from a monitored elements base case loading to enable the
checking of its loading in the contingency case loading violation reports; the
base case rating set is used in calculating these percent loadings. (default =
0.0, to check all monitored elements)
Minimum contingency case
voltage for reporting in voltage
range violation
Change from a monitored bus base case voltage magnitude to enable the
checking of its voltage in the contingency case voltage range violation
reports. (default = 0.0, to check all buses designated for range checking)
Bus mismatch converged
tolerance (MVA)
Used to treat contingency cases that have small mismatches but failed to
achieve convergence as converged
System mismatch converged
tolerance (MVA)
Used to treat contingency cases that have small mismatches but failed to
achieve convergence as converged.
Table 6-12. AC Contingency Multiple Run Report Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 6-107
PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-108 Siemens Energy, Inc., Power Technologies International
The AC Contingency Multiple Run Report function is designed to work best for the situation in which
different base cases of essentially the same system (e.g., different seasons, loading levels, and/or
years), with the same setting of the transformer percent loading units program option setting, and
with the same setting of the non-transformer branch percent loading units program option setting
are each presented to the AC Contingency Solution function with its Distribution Factor Data file
based on the same set of linear network analysis data files (refer to Section 7.1.1). Typically, each
base case is brought into PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-110 Siemens Energy, Inc., Power Technologies International
Contingency Solution Output Files Report
The Contingency Solution Output files report is always included in the output of the AC Contingency
Multiple Run Report function. This report lists the following for each Contingency Solution Output
file specified:
the name of the Contingency Solution Output file.
the name of the most recently accessed Saved Case file at the time that the AC Con-
tingency Solution function was executed.
the two line case title of the working case at the time that the AC Contingency Solution
function was executed.
the name of the Distribution Factor Data file specified to the AC Contingency Solution
function.
the name of the Subsystem Description Data file specified to, and used by, activity
DFAX in constructing the Distribution Factor Data file.
the name of the Monitored Element Data file specified to, and used by, activity DFAX
in constructing the Distribution Factor Data file.
the name of the Contingency Description Data file specified to, and used by, activity
DFAX in constructing the Distribution Factor Data file.
the percent loading units (MVA or current) for transformers and non-transformer
branches, which are based on the percent loading units program option settings at the
time the AC Contingency Solution function was executed.
if the Contingency Solution Output file was written by PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-112 Siemens Energy, Inc., Power Technologies International
Contingency Case All Loading Violations Report
The Contingency Case All Loading Violations report lists members of the master monitored element
list where loading exceeds the specified reporting percentage of the selected rating in a contingency
case of one or more of the Contingency Solution Output files. This report is included in the output
of the AC Contingency Multiple Run Report function if the value specified for the loading violations
report flag data item is 2 or 3.
For each violation, the report tabulates the label of the contingency causing the loading violation. It
lists MVA loadings for branches and active power loadings for interfaces. Percentage loadings are
calculated as described in Section 6.10.3, according to the transformer and non-transformer branch
percent loading units program option settings.
If a value of 1 is specified for the exclude base case loading violations from contingency case
reports flag, a violation is included in the table only if the element was not in violation in the base
case. If the minimum contingency case loading change data item is positive, a violation is included
in the table only if the elements loading in the contingency case differs from its corresponding base
case loading by the specified value. If the minimum contingency case percent loading increase data
item is positive, a violation is included in the table only if the elements loading in the contingency
case, expressed as its percent loading relative to the its base case rating, exceeds its corre-
sponding base case loading by the specified value. Interface violations are included in the report
only if a value of 1 is specified for the interface option flag data item.
A contingency legend follows this report if the value specified for the contingency legend flag data
item is 2 or 3. For each contingency listed in the report, the contingency legend tabulates the contin-
gency label used to identify the contingency in the AC Contingency Multiple Run Report function
and the events comprising the contingency.
Contingency Case Worst Case Loading Violations Report
The Contingency Case Worst Case Loading Violations report lists members of the master moni-
tored element list where loading exceeds the specified recording percentage of the selected rating
in a contingency case of one or more of the Contingency Solution Output files. This report is
included in the output of the AC Contingency Multiple Run Report function if the value specified for
the loading violations report flag data item is 1 or 3.
This report can be considered a compressed form of the Contingency Case All Loading Violations
report (refer to Contingency Case All Loading Violations Report). Each row of the report lists a moni-
tored element along with the label of the contingency that causes the most severe contingency case
loading violation of that element in one or more of the Contingency Solution Output files. For each
monitored element - Contingency Solution Output file pair (i.e., for each cell in the table) having a
non-blank entry, this report lists the most severe loading violation of the element from among all
contingencies in the Contingency Solution Output file. Thus, while there could be several rows for
the same monitored element in the table, each will be paired with a different contingency label and
each column of the table will have a non-blank cell in at most one of these rows for the same moni-
tored element.
For each violation reported, the report tabulates MVA loadings for branches and active power load-
ings for interfaces. Percentage loadings are calculated as described in Section 6.10.3, according to
the transformer and non-transformer branch percent loading units program option settings. It also
lists a count of the number of contingency cases in this Contingency Solution Output file, including
the contingency case listed, in which the loading on the element exceeds the specified percentage
of flow rating for counting violations.
Siemens Energy, Inc., Power Technologies International 6-113
PSS
E 32.0
Performing AC Contingency Analysis Program Operation Manual
6-114 Siemens Energy, Inc., Power Technologies International
Contingency Case Worst Case Voltage Violations Reports
The Contingency Case Worst Case Voltage Violations reports list members of the master monitored
voltage bus list where voltage magnitude fails the corresponding range or deviation test in a contin-
gency case of one or more of the Contingency Solution Output files. This report is included in the
output of the AC Contingency Multiple Run Report function if the value specified for the voltage
violations report flag data item is 1 or 3.
These reports can be considered a compressed form of the Contingency Case All Voltage Viola-
tions reports (refer to Contingency Case All Voltage Violations Reports). Each row of the report lists
a monitored bus along with the label of the contingency that causes the most severe contingency
case voltage range or deviation violation of that bus in one or more of the Contingency Solution
Output files. For each monitored bus - Contingency Solution Output file pair (i.e., for each cell in the
table) having a non-blank entry, this report lists the most severe voltage violation of the bus from
among all contingencies in the Contingency Solution Output file. Thus, while there could be several
rows for the same monitored bus in the table, each will be paired with a different contingency label
and each column of the table will have a non-blank cell in at most one of these rows for the same
bus.
The voltage violations report is presented as described in Section 6.10.3. For each violation
reported, the report tabulates the voltage magnitude in per unit. It also lists a count of the number
of contingency cases in this Contingency Solution Output file, including the contingency case listed,
in which the bus fails the corresponding range or deviation test.
If a value of 1 is specified for the exclude base case voltage range violations from contingency case
reports flag, a voltage range violation is included in the table only if bus voltage was within the corre-
sponding range in the base case. If the minimum contingency case voltage change data item is
positive, a violation is included in a range violation table only if bus voltage magnitude in the worst
case contingency case differs from its base case voltage magnitude by the specified value.
A contingency legend follows this report if the value specified for the contingency legend flag data
item is 2 or 3. For each contingency listed in the report, the contingency legend tabulates the contin-
gency label used to identify the contingency in the AC Contingency Multiple Run Report function
and the events comprising the contingency.
Additional Information
PSS
E 32.0
AC Corrective Actions Program Operation Manual
6-116 Siemens Energy, Inc., Power Technologies International
Controls are the actions that can be taken to correct branch loading, bus voltage and interface flow
limit violations in a power system. There are six categories of controls modeled in the corrective
actions computation:
Interface MW
flows
Interface flow is defined as the sum of MW flow of its members. Each interface
is specified in terms of the from bus, to bus and circuit identifier of each of its
members. Flow is computed at the from bus end of each circuit in the interface.
If an interface consists of one or more zero impedance branches, or its rating
in the designated rating set is zero, it will be excluded from constraints.
Bus voltages
High and low voltage limits for each bus are defined in per unit. Voltage limits
can be specified on a system-wide basis, for the study area only, or for indi-
vidual areas, zones and buses. If a bus voltage is monitored by several sets of
upper and lower limits, the maximum of upper limits of all sets is selected as
the upper limit and the minimum of lower limits of all sets is selected as the
lower limit for the bus voltage respectively. Note that voltage deviation limits
are not checked in corrective action calculations. For a generator bus, if the
generator has sufficient reactive power generation to maintain its scheduled
voltage, the generator bus is excluded from the constraint set.
Table 6-14. AC Corrective Action Controls
Control Description
Generator
active power
dispatch
Generators in the generator control subsystem that have a adjustable range
are available for corrective action analysis.
Phase shifter
angle
adjustment
The desired MW flow values in the power flow database for participating phase
shifters are ignored in the corrective action analysis. After a corrective action is
performed successfully, the upper and lower limits (VMA and VMI) of a phase
shifter specified in corrective actions are reset based on its flow in post-correc-
tive solution, while the difference between upper and low limits remains
constant.
Load
curtailment
Bus active power load can be curtailed as needed to correct system problems.
The reactive power load is adjusted accordingly to maintain a constant power
factor of load at the bus.
Off-line gener-
ator active
power dispatch
Off-line generators in the off-line generator control subsystem that have a
adjustable range are available for corrective action analysis. The reactive
power outputs of the generators remain zeros. After a corrective action is
performed successfully, off-line generators specified in corrective actions will
be turn on with the upper and lower limits of reactive power set to zeros.
Tap setting
adjustment
The transformers in the tap setting adjustment subsystem that are subject to
voltage control mode are available for corrective action analysis. Voltage
controls of participating transformers are ignored in the corrective action anal-
ysis. After a corrective action is performed successfully, the upper and lower
limits (VMA and VMI) of a transformer specified in corrective actions are reset
based on bus voltage of the controlled bus in post-corrective solution, while the
difference between upper and low limits remains constant.
Table 6-13. AC Corrective Action Constraints (Cont.)
Constraint Description
Siemens Energy, Inc., Power Technologies International 6-117
PSS
E 32.0
AC Corrective Actions Program Operation Manual
6-118 Siemens Energy, Inc., Power Technologies International
Figure 6-24. Load Shedding Control Default Weighting Function
Figure 6-25. Phase Shifter Angle Control Default Weighting Function
Load curtailment should be assigned a much higher weight than generator real power dispatch to
prevent unnecessary load curtailment when generation rescheduling is adequate in relieving the
system problems. Moderate changes of the weights from the default values generally have little
influence on the corrective actions because the sensitivities expressing the effectiveness of indi-
vidual actions tend to dominate. A large weighting factor discourages the control from being
adjusted. Therefore, you can favor certain controls over others by specifying smaller external
weights. However, please note that extremely large or small weights may cause solution problems.
For this reason, it is recommended that weights be limited to the range from 0.1 to 10.
If the limit violations in the power system cannot all be eliminated using the basic control actions, it
may be preferable sometimes to accept certain degree of limit violations instead of applying
Siemens Energy, Inc., Power Technologies International 6-119
PSS
E 32.0
AC Corrective Actions Program Operation Manual
6-120 Siemens Energy, Inc., Power Technologies International
6.11.3 AC Corrective Action Options
The following options are available in the ac corrective actions menu.
Table 6-15. AC Corrective Action Options
Option Description
Solution options
Select the desired solution options to be applied during power flow calculations
with corrective actions (see Section 6.10.1).
Number of ac load
flows
Select the desired number of iterations between execution of the linear program-
ming engine to identify corrective actions and subsequent ac power flow solution
to verify the feasibility of those actions. The specified number of iterations can be
between 1 and 10. Note that, even if a feasible solution appears to have been
found, i.e., the identified corrective actions appear to have been successful, the
iteration between linear programming computation and ac power flow solution
may continue in an attempt to further optimize the solution if not exceeding the
iteration limit. The user needs to select this parameter carefully, based on expe-
rience. On the other hand, if a solution fails at the nth iteration because the ac
power flow diverges, the user may obtain an approximate solution by specifying
the number of ac power flows as n-1 and repeating the calculations.
Mismatch
tolerance
This tolerance will be used to check for the largest active or reactive power
mismatch in the power flow case prior to the start of the ac corrective actions
computation. If this tolerance is exceeded, the process is terminated. This value
is also used as the convergence tolerance for the ac power flow solution
embedded in ac corrective action analysis.
Constraint options Select branch flow rating set, and limit tolerances for monitored elements.
Rating
Specify rating to be used in determination of branch and interface flow over-
loads. The default rating set is established by the program option setting (refer to
Section 3.3.3 and activity OPTN).
Percent of flow
rating
Specify percent of rating to be used in determination of branch and interface flow
overloads.
Branch overload
violation tolerance
The percent of flow rating used in linear programming engine can be adjusted by
specifying a branch overload violation tolerance. e.g., if branch overload viola-
tion tolerance is specified as 0.1% and percent of flow rating is 100%, percent of
rating of 100.1% is used in determination of overload violations in linear
programming algorithm.
Bus voltage viola-
tion tolerance
The limits of bus voltages used in linear programming engine can be adjusted by
specifying bus voltage violation tolerance. The voltage violation tolerance is
applied to both upper and lower voltage limits, if applicable. e.g., if bus voltage
violation tolerance is specified as 0.1%, lower and upper limits of bus voltages
are 0.95 and 1.05 in pu respectively. The adjusted voltage limits are 0.949 and
1.051 respectively.
Control options Select types of control adjustments and specify weighting factors for each type.
Siemens Energy, Inc., Power Technologies International 6-121
PSS
E 32.0
AC Corrective Actions Program Operation Manual
6-122 Siemens Energy, Inc., Power Technologies International
6.11.4 Viewing AC Corrective Actions Results.
After ac corrective actions solution is performed successfully, a corrective action analysis report is
produced. In the report, files used in the analysis, and numbers of constraints and controls are
presented first. Flow overloads and bus voltage violations prior to and post corrective action anal-
ysis are reported. Specified corrective actions are presented in the order of generation dispatch,
load shedding, phase shifter angle adjustment, off-line generator active power dispatch, tap setting
Off-line generator
weighting factor
Specify a weighting factor to adjust the cost factor of active power generation
dispatch of off-line generators. The internal cost factor defined in the programs is
shown in Table 6-16.
Off-line generator
control subsystem
Select the subsystem in which all out-of-service generators with valid range of
adjustments will participate in corrective action analysis.
Enable tap setting
adjustments
Enable to include tap setting adjustment.
Tap setting
weighting factors
Specify a weighting factor to adjust the cost factor of tap setting adjustment. The
internal cost factor defined in the programs is shown in Table 6-16.
Tap setting adjust-
ment subsystem
Select the subsystem in which all in-service transformers designated in voltage
control mode will participate in corrective action analysis.
Enable switched
shunt controls
Enable to include switched shunt reactive power controls.
Switched shunt
weighting factors
Specify a weighting factor to adjust the cost factor of switched shunt reactive
power control. The internal cost factor defined in the programs is shown in
Table 6-16.
Switched shunt
control subsystem
Select the subsystem in which all in-service switched shunts designated in
voltage control mode will participate in corrective actions.
Input Data File
The Distribution Factor Data file is used to provide monitored elements, bus
voltage limits and control subsystems. When creating a Distribution Factor Data
file for corrective action analysis, a Contingency Description Data file where no
contingencies are specified is allowed.
Table 6-16. Weighting Functions and Factors of Controls
Control Weighing Function Internal Weight
Phase shifter Angle V-Curve 2 per 57.4 degrees (0.035 per degree)
MW Generation V-Curve 1 per 100 MW (0.01 per MW)
Load Curtailment Linear 100 per 100 MW (1.0 per MW)
MW generation of Off-
line generator
V-Curve 2 per 100 MW
Tap setting V-Curve 1 per 0.002 pu
MVAR output of
Switched shunt
V-Curve 1 per 100 MVAR
Table 6-15. AC Corrective Action Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 6-123
PSS
E 32.0
AC Corrective Actions Program Operation Manual
6-124 Siemens Energy, Inc., Power Technologies International
6.11.5 Application Notes
The corrective actions solution algorithm does not place a limit on the numbers of controls and
constraints that can be modeled. The computation time of corrective actions solution is approxi-
mately proportional to size of the power system and the number of constraints. Because local
controls are generally more effective in removing violations, it may be preferable to choose the
subsystems in which control actions are allowed to be the same as that in which elements are
monitored.
Operating limit violations caused by incorrect limit settings may have a significant impact on the
optimal solution found. Hence, suspicious limits should be verified and corrected, if necessary, or
even removed from the solution.
Two methods can be used to exclude controls from the corrective actions solution. One is to set the
upper and lower limits of a control to be identical. In addition, to exclude an on-line generator and
off-line generator from the solution, both the upper and lower limits should be equal to the Pgen.
The second method is to specify a control subsystem that does not include undesirable controls in
a particular application.
Because the optimization engine is based on a linear power flow, the result from the linear program-
ming solution is iterated with a standard ac power flow solution until one of following conditions
occurs:
all overloads and voltage violations are resolved,
the adjustable controls are exhausted,
the number of ac power flow solutions reaches the specified value,
the difference of the values of objective function between two consecutive iterations is
less than a tolerance
the ac power flow diverges during the process
When ac corrective actions computation fails because of ac power flow divergence, warning
messages in the progress window indicate at which step the ac power flow diverges. The user may
obtain an approximately optimal solution by specifying the number of ac power flow in ac corrective
actions input menu as one less than the step in the solution failure occurs. Or, if the user finds that
the computation may require more iterations to reach an optimal solution, the desired iteration
number may be increased.
Additional Information
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-126 Siemens Energy, Inc., Power Technologies International
Multiple level AC contingency analysis calculates full AC power flow solutions for the user specified
and automatically selected single or multiple contingencies, monitors voltage and loading condi-
tions and stores the results in a binary file. It will accept a user-specified list of contingencies to be
included in a contingency study as defined in a Contingency Description Data file (see Contingency
Description Data File Contents). Each of these specified contingencies may consist of a combina-
tion of generation and transmission outages. In addition, contingencies may be selected by built-in
automatic contingency rankers. Two such rankers, for branch overload and voltage collapse contin-
gencies (see Section 7.3.1), are integrated during multiple level contingency analysis. There is full
flexibility in defining contingency subsystem; i.e., you can define in which portion of the system you
will allow contingencies automatically selected by rankers. A contingency sub-system may
comprise of specific equipment, a combination of control areas or zones, or the whole database
(see Section 6.10.1).
The multiple contingency solution function performs deterministic reliability assessment for up to
three levels, namely N-1, N-2 and N-3 criterion. User specified and automatically selected contin-
gencies are evaluated individually and in combination with each other as overlapping outages up
to the specified evaluation level. When used in conjunction with the automatic contingency ranker,
a stopping criterion (non-failure cutoff) is applied at each level. This provides the opportunity for
enormous savings in computational evaluation of contingencies. Furthermore, PSS
E has built-in
logic that identifies if a given set of outages has already been evaluated as a contingency, thus
ensuring that an automatic contingency analysis run is comprised only of unique contingencies.
Multiple-level ac contingency analysis models special relay actuation schemes designed to trip or
reconnect a generator or a circuit, and shed or transfer load in response to specified low voltage,
line flow, interface flow, generator output, or line and generator service status. During contingency
analysis, switching will be automatically performed and new power flow solutions obtained when-
ever trip/reconnect relaying sequences are triggered. The tripping simulation can simulate
cascading outages from contingencies.
Multiple-level ac contingency analysis performs corrective action analysis to eliminate flow over-
loads and voltage violations caused by a contingency with the objective of minimizing control
adjustments such as re-dispatch of generations, curtailment of loads and adjustment of phase-
shifting transformers. This can help translate system related reliability measures, such as the loca-
tion and magnitude of branch overloads and bus voltage violations, to customer-impact indices in
terms of the potential amount of service interruptions, which are critical indices in probabilistic reli-
ability assessment.
6.12.1 Terms Used in Multiple-Level Contingency Analysis
Multiple level contingency analysis can perform both simple and complex contingency analysis.
Certain terms used in the implementation and documentation are specific to multiple contingency
analysis use and may not necessarily reflect those of local electric power analysis practice. Some
key definitions of terms applied to multiple contingency analysis are identified as following:
Contingency element: A major component in the network where operation status or set-
points can be changed, e.g., one transmission circuit outage, one machine out-of-service,
one transmission circuit reclosing, a change in load or generation at a bus.
Contingency event: The contingency of one or more elements originating from a single
cause, e.g., each contingency case defined with a block structure in a contingency descrip-
tion file is considered as one contingency event.
Contingency: A contingency condition simulated by PSS
E. Level
may also be viewed as the number of independent causes studied in a contingency; e.g.,
N-1, N-2 and N-3.
Contingency events include:
Single contingency elements, e.g., one transmission circuit outage, and
Multiple contingency elements, e.g., a combination of circuits and, or machines
out-of-service at the same time.
Examples of the latter include outages of multiple circuits terminating at the same bus caused by
bus failures and outages of two circuits on the same right-of-way caused by ROW failure.
When multiple events are combined within a contingency, they are assumed to be occurring simul-
taneously but originating from independent causes, i.e., one event does not trigger the others.
Multiple level contingency analysis is deigned to model up to three events per contingency.
6.12.2 Power Flow Control Options
Table 6-17. Multi-Level AC Contingency Solution Power Flow Control Options
Option Description
Solution options
The desired solution options to be applied during power flow calculations for
obtaining post-contingency states (see Section 6.2)
Tap adjustment:
Lock taps (default)
Stepping
Direct
Area interchange control:
Disabled (default)
Tie lines only
Tie lines and loads
Switched shunt adjustments:
Lock all
Enable all (default)
Enable continuous, disable discrete
Non-divergent
solution
Flag to enable or disable (default) option in the power flow solution of each contin-
gency case.
Adjust phase
shift
Flag to enable or disable (default) option in the power flow solution of each contin-
gency case.
Adjust dc taps
Flag to enable (default) or disable option in the power flow solution of each contin-
gency case.
Solution Engine
Select the desired power flow solution engine to be used in obtaining post-contin-
gency states (see Section 6.2).
Fixed slope decoupled Newton-Raphson (FDNS) (default)
Full Newton-Raphson (FNSL)
Optimized fixed slope decoupled Newton-Raphson (FDNS)
Power Flow Solution Activity Descriptions PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-128 Siemens Energy, Inc., Power Technologies International
6.12.3 Multiple Contingency Analysis Options
Dispatch mode
Dispatch codes for generation dispatch calculations in contingency
analysis (see Table 6-10)
Dispatch system Select the subsystem for the generation dispatch.
Mismatch
tolerance
Tolerance used to check for the largest initial active or reactive power mismatch. If
exceeded, the process is terminated. This value is also used as the convergence
tolerance in power flow solution (see Section 6.2).
Distribution
Factor Data File
(*.dfx) a required file to be build by activity DFAX that corresponds to the network
condition contained in the working case (refer to Section 7.1.6) and to the desired
linear network analysis data files (refer to Section 7.1.1). The bus input option (refer
to Section 3.3.3 and activity OPTN) must have the same setting that was in effect
when activity DFAX filled the specified Distribution Factor Data file. Refer to
Section 2.4.1 for the file specification conventions used by the AC Contingency
Solution function.
Contingency
Solution Output
File
(*.acc) a required file designated by the user as the destination for the results of the
contingency calculations.
Load Throw-
over Data File
( *.thr) an optional file, created by the user, that contains data records of the
following form:
IBUS, JBUS
where IBUS and JBUS are bus numbers. If branch outage contingency events
isolate bus IBUS, the user can elect to move the load to bus JBUS. Bus IBUS
and/or JBUS may be a dummy bus of a multi section line grouping. Data records
may be entered in any order. Input is terminated with a record specifying an IBUS
value of zero.
Unit Inertia and
Governor Data
File
(*.inl) a required file if the generation dispatch is enabled and either the inertial or
governor droop dispatch method is selected. If the PMAX or reserve method is
selected, the specification of this file is optional. If a file is specified, machine active
power limits are taken from it; otherwise, the machine active power limits in the
working case are used.
Table 6-18. Multi-Level AC Contingency Solution Multiple Contingency Analysis Options
Option Description
Multiple contin-
gency analysis
When disabled, all other options in this dialog are disabled.
When enabled, the next-level contingencies (e.g. secondary contingencies of a primary
contingency) of each non-failure contingency (see Section 6.12.4) are to be evaluated.
When enabled with failure cutoff disabled, the next-level contingencies of each failure and
non-failure contingency will be evaluated.
Max level of
contingency
analysis
Level of multiple contingency analysis, up to third level. This option enables the contin-
gency combination selections at less or equal levels.
Table 6-17. Multi-Level AC Contingency Solution Power Flow Control Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 6-129
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-130 Siemens Energy, Inc., Power Technologies International
6.12.4 Classification of Contingency Analysis Results
There are two cutoffs to control the level of multiple contingency analysis and number of contingen-
cies to be evaluated at each level during analysis: failure cutoff and non-failure cutoff.
The failure cutoff is enabled by selecting Enable for multiple contingency analysis option, the next-
level contingencies of a failure contingency that results in operating limit violations will be skipped.
It is most likely that under a failure contingency condition any next-level contingencies will result in
operating limit violations too, so there is no need to apply more contingencies to failure cases.
Enabling failure cutoff can reduce the set of tested contingencies and concentrate studies on more
Small reac-
tance threshold
Reactance threshold; all branches from the contingency list (based on the users
subsystem selection) where magnitude of reactance is less than or equal to this threshold
have their performance indices explicitly calculated.
Line overload
Four control parameters.
Enable: Include single branch outage that causes overloading in the contingency
list.
Min.: The minimum of single branch outages from the overload ranking to be tested
in the list.
Max.: The maximum of single branch outages from the overload ranking to be
tested in the list.
Cutoff: The number of consecutive single branch outages from the overload
ranking that are non-failure
Machine
overload
Four control parameters.
Enable: Include single machine outages from branch overload ranking in the
contingency list.
Min.: The minimum of single machine outages from the overload ranking to be
tested in the list.
Max.: The maximum of single machine outages from the overload ranking to be
tested in the list.
Cutoff: The number of consecutive single machine outages from the overload
ranking that are non-failure.
Voltage
depression
Four control parameters.
Enable: Include single branch outage that causes voltage collapse in the
contingency list.
Min.: The minimum of single branch outages from the voltage collapse ranking to
be tested in the list.
Max.: The maximum of single branch outages from the voltage collapse ranking to
be tested in the list.
Cutoff: The number of consecutive single branch outages from the voltage collapse
ranking that are non-failure.
Islanding
ranking
Two control parameters.
Enable: Include single branch contingencies that result in the formation of an island
of one or more buses, without a swing bus, in the contingency list.
MW threshold: The minimum of active power flow on such branches.
Table 6-18. Multi-Level AC Contingency Solution Multiple Contingency Analysis Options
Option Description
Siemens Energy, Inc., Power Technologies International 6-131
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-132 Siemens Energy, Inc., Power Technologies International
The detected overloaded branches are different with those in post-processed report files
where the different ratings of loading may be applied.
An islanding event occurs when a contingency causes a physical separation of a bus or group of
buses from the base case network. The outage of a radial branch will automatically result in
islanding of a radial bus. If the contingency is a multiple element outage, it may cause multiple
islands. When dispatch mode and dispatch subsystem are specified, contingency analysis will
process islanding events via generation redispatch (see Section 6.9.4), otherwise those islands
without a swing bus will be shut down. The islanding problem has been removed from the failure
criteria since PSS
E-30.3.
The types of events (as differentiated from troubles) occurring during contingency evaluation that
would qualify a contingency as a failure, include:
TRIPPING A contingency where at least one trip specification is actuated (see
Section 6.12.7).
Power flow cases with solutions that are classified as either voltage collapse (Category II) or not
converged (Category III) are excluded from tests of failure.
6.12.5 About Contingency List
Multiple contingency analysis functions work with a contingency event list, also referred to as a
contingency list. The list provides a sequence for evaluating contingencies. However, the true
power of this list lies in the fact that not all contingencies included in it are evaluated by multiple
contingency analyses.
It is useful to think of the contingency list as further divided into contingency groups. Contingency
groups are shown in Table 6-21. The graphic equivalent of this table is shown in Figure 6-30.
In group S, the contingencies are taken directly from a dfax file that is generated with a Contingency
Description Data file (see Contingency Description Data File Contents). These can be viewed as
must-test contingencies; i.e., no matter how system conditions change, it is important to the reli-
ability assessment to consider these contingencies. The Contingency Description Data file may be:
Created by the user based on previous operating or planning experience with a system,
reliability criteria guidelines or some other arbitrary method. The file is thus one that is
created outside of PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-134 Siemens Energy, Inc., Power Technologies International
6.12.6 Wind Chime Algorithm for Multiple Level Contingency Analysis
If a one-level contingency analysis is specified, all must-test events (group S) are evaluated first.
Ranked individual machine outages (group U) follow the gourp S. These ranked machine outages
will be tested one by one until an unbroken sequence of N contingencies without any system prob-
lems has been detected or the maximum of contingencies of group U has been tested. When the
testing of machine outages is complete, either because the list has been exhausted, or because the
stopping criterion has been met, the branch outage events causing system separations (group B1)
are evaluated. A simple screening algorithm that searches for continuity can also automatically
select these events. The final two groups of events in the list are the ranked branch outages from
overload (group B2) and voltage collapse ranking (group B3). These are tested in a similar fashion
as the ranked machine outages, in which the individual branch outages are tested one by one and
the list is truncated after the corresponding stopping criterion is met. Groups B1, B2 and B3 may be
comprised of the same contingencies, albeit with different ranking. Some of these contingencies
may also be included in group S.
The multiple contingency solution procedure is given by the example of a two-level contingency
analysis. If a two-level contingency analysis is to be performed, a newly ordered event list is built
after solving each first-level contingency Power Flow. These secondary ordered event lists may
contain the same categories of outage events as those in the first-level list, with the exclusion of the
initial outage event. New rankings are determined based on the system conditions existing after
each first-level contingency using a linearized network model. This approach is called Wind Chime
approach.
Figure 6-31 illustrates the Wind Chime approach for a two-level contingency run using a contin-
gency level of 2; some other options specified for this run are Enabled with failure cutoff disabled
for Perform multiple contingency analysis option, B for the first level and BB for the second level
analysis, as well as only single branch outages from overload ranking with non-failure cutoff of 2.
Siemens Energy, Inc., Power Technologies International 6-135
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-136 Siemens Energy, Inc., Power Technologies International
The program can still test multiple levels of machines of the same size.
6.12.7 About Tripping Sequence
A contingency analysis may be followed by tripping simulations during multiple level contingency
analysis. Tripping sequences are simulations of events ensuing from automatic monitoring equip-
ment such as relays, and automatic circuit breaking and making equipment such as circuit breakers
and switchers. These sequences are important in order for multiple contingency analysis to obtain
the right post-contingency state. Examples of tripping sequences are:
Transfer of load to another bus on loss of power on a transmission branch.
Switching of lines following outage or overload of another.
Tripping of transmission circuits following extreme overloads.
Tripping sequences may also be used to model other automatic actions such as remedial action
schemes (RAS), special protection schemes (SPS) and operating guides.
6.12.8 Tripping Simulation Options
Table 6-22. Multi-Level Contingency Solution Tripping Simulation Options
Option Description
Perform tripping
simulation
Enable or disable (default) tripping simulation for post-contingencies states.
Number of trip
events per load
flow
After a contingency power flow solution, tripping conditions that trigger tripping
sequences are checked in the order in which tripping events are specified in
Tripping Element Data file (Section 6.12.9). There may be more than one
instance of tripping sequences that are activated. This option sets the number of
trip events that are activated prior to the next power flow solution.
Number of load
flows per
contingency
When a new power flow solution is performed following activation of one or more
tripping sequences, the trip triggers are reset and all the remaining trip
sequences are checked for the new power flow solution. If one or more
remaining tipping sequences satisfy conditions, a new power flow is performed
with activation of these tripping sequences up to Number of trip events per load
flow. This process continues till the number of power flows following a contin-
gency power flow reaches the number of power flows per contingency.
Tripping
Element Data
File
If multiple level contingency analysis is initiated with tripping simulation, this file,
created by the user, is required. It contains tripping data.
Siemens Energy, Inc., Power Technologies International 6-137
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-138 Siemens Energy, Inc., Power Technologies International
To specify one winding of a three-winding transformer for monitoring, the bus to which the winding
is connected must be the first bus specified in the following data record:
[MONITOR]|BRANCH| FROM BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT | ckid] TR r|MW |
|LINE | |CKT | |MVA |
|MVAR |
|AMPS |
|PERCENT| OF |A|
|B|
|C|
When flow monitoring records employ keyword PERCENT, one of rating sets A/B/C must be spec-
ified. Percent loadings of monitored elements based on ratings are specified as either Current or
MVA percent loadings by percent units program settings (see activity OPTN).
Unit Monitoring Record
The data record defines a single machine for monitoring:
[MONITOR]|UNIT | mcid AT BUS bsid TR r |MW |
|MACHINE| |MVA|
|MVAR |
|AMPS |
Interface Monitoring Record
[MONITOR] INTERFACE label TR r |MW/MVA/ MVAR/AMPS|
(branch specification record, see below)
.
.
(branch specification record, see below)
END
where r is trip rating for the monitored interface, if the sum of MW/MVA/ MVAR/AMPS flows at the
from bus end of specified branches is greater than r, trip actions occur. A rating of zero will disable
the monitored interface flow condition. The branch specification record may specify individual two-
winding or non-transformer branches or individual three-winding transformers.
For specifying a two-winding or non-transformer branch the following data specification record is
used:
|BRANCH| FROM BUS bsid TO BUS bsid [|CIRCUIT| ckid]
|LINE | |CKT |
For specifying a three-winding transformer the following data specification record is used:
|BRANCH| FROM BUS bsid TO BUS bsid TO BUS bsid [|CIRCUIT| ckid]
|LINE | |CKT |
Siemens Energy, Inc., Power Technologies International 6-139
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-140 Siemens Energy, Inc., Power Technologies International
The third and fourth data records of this type are similar to the CHANGE record, except the direction
of the change is defined by the first keyword, and r must be a positive number:
|INCREASE| BUS bsid |GENERATION| BY r |MW |
|RAISE | |LOAD | |PERCENT|
|SHUNT |
|DECREASE| BUS bsid |GENERATION| BY r |MW |
|REDUCE | |LOAD | |PERCENT|
|SHUNT |
To transfer load or generation from one bus to another, the following data record is used:
MOVE r |MW | |GENERATION| FROM BUS bsid TO BUS bsid
|PERCENT| |LOAD |
|SHUNT |
See Contingency Description Data File Contents for details.
An in-service machine may be removed from service using the following data record:
REMOVE |MACHINE| mcid FROM BUS bsid
|UNIT |
Similarly, an out-of-service machine may be placed in-service with a record of the form:
ADD |MACHINE| mcid TO BUS bsid
|UNIT |
Automatic Single Tripping Record
A series of single branch tripping events is specified with a record of the form:
SINGLE LINE IN | AREA i | TR r PERCENT OF |A|
| ZONE i | |B|
| OWNER i | |C|
| KV r |
| SYSTEM label |
| SYBSSYTEM label|
In each tripping event, a single branch within a given subsystem is monitored. For non-transformer
branches and two-winding transformers, a branch is tripped when flow at either one of its two bus
ends exceeds the tripping rating. For three-winding transformers, a three-winding transformer is
outaged when the flow at any one of its three winding buses exceeds the tripping rating.
A breaker is a branch where the circuit IDs first character is @, a switch has a - as the first char-
acter of its circuit ID. A series of single breaker and switch tripping events is specified with a record
of the form:
SINGLE BREAKER IN | AREA i | TR r PERCENT OF |A|
| ZONE i | |B|
Siemens Energy, Inc., Power Technologies International 6-141
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-142 Siemens Energy, Inc., Power Technologies International
6.12.10 Corrective Actions Options
When multiple level contingency analysis is initiated with corrective action analysis, if there are
operating limit violations in post-contingency solutions, or in post-tripping contingency solutions if
tripping simulation is enabled and tripping events are activated following a contingency, corrective
actions will be specified to relieve these violations.
Table 6-23. Multi-Level Contingency Solution Corrective Actions Options
Option Description
Perform Correc-
tive Actions
Enable (default) to perform corrective action analysis; disable to disable all corrective
actions options.
Number of AC
load flows
The desired number of iterations between execution of the linear programming engine to
identify corrective actions and subsequent ac power flow solution to verify the feasibility of
those actions. The specified number of iterations can be between 1 and 10.
Note that, even if a feasible solution appears to have been found, i.e., the identified
corrective actions appear to have been successful, the iteration between linear program-
ming computation and AC power flow solution may continue in an attempt to further
optimize the solution if not exceeding the iteration limit.
Branch over-
load violation
tolerance
The percent of flow rating used in linear programming engine can be adjusted by speci-
fying a branch overload violation tolerance. e.g., if branch overload violation tolerance is
specified as 0.1% and percent of flow rating is 100%, percent of rating of 100.1% is used
in determination of overload violations in linear programming algorithm.
Bus voltage
violation
tolerance
The limits of bus voltages used in linear programming engine can be adjusted by speci-
fying bus voltage violation tolerance. The voltage violation tolerance is applied to both
upper and lower voltage limits, if applicable. e.g., if bus voltage violation tolerance is spec-
ified as 0.1%, lower and upper limits of bus voltages are 0.95 and 1.05 in pu respectively.
The adjusted voltage limits are 0.949 and 1.051 respectively.
Control options Types of control adjustments and weighting factors for each type
Enable gener-
ator controls
Enable (default) to include active power generation dispatch controls. The adjustable
range is from PT to PB of each participating machine. Generator active power limits are
taken from a Unit Inertia and Governor Data file (see Section 6.8.1) if the file is specified,
otherwise the values in base case are used.
In corrective action analysis, generator active power limits are adjusted by the following
rules.
If PT had been set to the default value, the larger value of PG (its existing MW
output) and machine power base (MVA base) will be used as PT.
If PT of a machine is less than its PG, the PT is set equal to the PG.
If PB of a machine had been set to the default value, it is set equal to 0.
If PB of a machine is less than its PG, the PB is set equal to the PG.
A machine will be excluded from the controls if its PT is equal to its PB.
Weighting factor
of active power
generation
dispatch
Specify a weighting factor to adjust the cost factor of active power generation dispatch.
The cost of a control adjustment in objective functions is equal to the amount of adjust-
ment times by a adjusted cost factor. The internal cost factor for active power generation
dispatch defined in the programs is shown in Table 6-16; the adjusted cost factor is equal
to the internal factor multiplied by the user defined weighting factor. e.g., if the weighting
factor is set as 1.0, the cost factor for active power generation dispatch of 100 MW will be
1.0.
Siemens Energy, Inc., Power Technologies International 6-143
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-144 Siemens Energy, Inc., Power Technologies International
Weighting factor
of switched
shunt
Specify a weighting factor to adjust the cost factor of switched shunt reactive power
control. The internal cost factor defined in the programs is shown in Table 6-16.
Switched shunt
control
subsystem
Select the subsystem in which all in-service switched shunts designated in voltage control
mode will participate in corrective actions.
Table 6-23. Multi-Level Contingency Solution Corrective Actions Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 6-145
PSS
E 32.0
Performing Multi-Level AC Contingency Solution Program Operation Manual
6-146 Siemens Energy, Inc., Power Technologies International
sequence number in the contingency list, e.g., contingency OVRLOD 2 is from overload ranking and
is the second contingency in the list. the other ranker names are UNIT, VLTAGE and ISLAND. The
labels of multiple contingencies are comprised of sequence number at each level separated by an
underscore ( _ ), e.g., 12_14, the first number represents the 12th contingency in the first level
contingency list, 14th is the number in the secondary contingency list. Another example is
15_16_17, the first number represents the 15th contingency in the first level contingency list, 16th
is the number in the secondary contingency list, the 17th is the number in the tertiary contingency
list.
Post-tripping solutions at the last stage of tripping simulation for each contingency that triggers trip-
ping events are saved into output files in the same format as contingency cases. The label of a post-
tripping solution is generated by the programs, and is comprised of the first ten letters of the label
of the contingency activating tripping actions and ended with /T, which identifies the case as a post-
tripping case. Normally contingency legends for a tripping solution will include tripping labels,
description of the monitored element that triggers the tripping activities, and description of tripping
activities, due to limited space to save the legends, when the number of tripping activities and moni-
tored elements in a tripping solution is more than 32, only tripping labels are saved as contingency
legends.
The post-corrective action solution and activated corrective actions are stored into output files if the
Perform corrective actions option is enabled.
There is no limit on the number of contingencies that can be tested in a contingency analysis, while
the size of a contingency analysis output file is limited by Operating system. When the contingency
analysis file reaches its size limit, contingency analysis is terminated and the rest of contingencies
are ignored.
Siemens Energy, Inc., Power Technologies International 6-147
PSS
E 32.0
Calculating Probabilistic Reliability Program Operation Manual
6-148 Siemens Energy, Inc., Power Technologies International
Figure 6-32. Process of Probabilistic Reliability Assessment
6.13.1 Probabilistic Reliability Assessment
Table 6-25. Probabilistic Reliability Assessment Options
Option Description
Report format
The user selects from among the following reports:
system problem summary
system loss of load
bus loss of load
branch flow overloading
bus voltage violations
contingency summary for
system problem probabilistic indices
system load curtailment probabilistic indices
bus load curtailment probabilistic indices
branch flow overloading probabilistic indices
bus voltage violation probabilistic indices
contingency summary with probabilistic indices
When no probabilistic data is available or the studies are limited in deterministic
reliability area, the users can produce the first six reports for deterministic reli-
ability analysis, and each contingency will have identical statistic data.
Perform contingency
analysis
Calculate and report
probability indices
*.acc Outage statistic data
Outage Statistics Data
Siemens Energy, Inc., Power Technologies International 6-149
PSS
E 32.0
Calculating Probabilistic Reliability Program Operation Manual
6-150 Siemens Energy, Inc., Power Technologies International
6.13.2 Outage Statistics Data File Contents
The Outage Statistics Data file is used to specify frequencies and durations for individual element
outages and user specified contingencies. Outage statistics for individual elements, including non-
transformer branches, transformers and machines, must be specified. They are also used to calcu-
late outage statistics of multiple independent element contingencies for which statistics are not
specified. Statistics for user specified outages can be defined in Outage Statistics Data file or in the
Contingency Description Data file; when both files contain statistics for a user specified contingency,
values are taken from Outage Statistics Data file. When no statistics data is entered for a multiple
element contingency, the contingency is treated as a multiple independent element outage and its
statistics are calculated on the basis of outage statistics of each single element within it. If a user
specified contingency contains one or more FACTs device outages, closing events, or boundary
condition change events, its statistics are set to zeros if not specified. Contingencies generated
automatically by the multiple level contingency analysis are treated as independent multiple
element contingencies, their outage statistics are thus calculated. The following examples illustrate
how to specify outage statistics.
Example 1: There is no need to specify outage statistics of contingencies created by global
command 'DOUBLE', each double branch contingency is treated as a multiple independent outage
and its outage statistics are calculated from frequency and duration of two branches within it.
Example 2: Contingency A has branch B outage. Statistics for contingency A can be specified in the
Outage Statistics Data file or in the Contingency Description Data file. Otherwise its statistics are
equal to the statistics for the outage of branch B. If no invalid outage statistics data record is read
for branch B in Outage Statistics Data file, outage statistics of contingency A are zero.
Example 3: Contingency A has branches B and C outages. Statistics for contingency A can be spec-
ified in the Outage Statistics Data file or in the Contingency Description Data file. If no statistics are
specified for contingency A, its statistics are equal to frequency and duration of the multiple inde-
pendent outaging of branches A and B. If no invalid outage statistics data records are read for either
branch B or C, outage statistics of contingency A are zero.
Example 4: Contingency A has branch B and FACTs device C outages. Statistics for contingency A
can be specified in the Outage Statistics Data file or in the Contingency Description Data file. If no
statistics are specified for contingency A, its statistics are zeros.
Output outage
statistics
Enable or disable (default) output of outage statistics to a file.
Output Outage
Statistics Data File
Required when Output outage statistics option is selected. The file is used to
convert generic statistics to specific statistics for individual components.The
resulting file can be edited and modified for future use. It has the same format as
Outage Statistics Data file.
Table 6-25. Probabilistic Reliability Assessment Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 6-151
PSS
E 32.0
Calculating Probabilistic Reliability Program Operation Manual
6-152 Siemens Energy, Inc., Power Technologies International
component has only two states: in-service or out-of-service. The probability of a component being
out-of-service is the sum of probabilities of three failure modes. When the specification data record
is read by Probabilistic Reliability Assessment function, frequency and duration of a breaker or
switch being out-of-service are calculated as follows:
F=f+fu+fm
D=(f*d+fu*du+fm*dm)/F
In Substation Reliability Assessment analysis, each component can have three failure modes: fault,
unscheduled maintenance and scheduled maintenance outages. When the record is read by
Substation Reliability Assessment function, each pair of frequency and duration values is taken for
the corresponding fault or outage mode. By default, the four optional values are set to zeros.
The following data record defines statistic data of transformers within a subsystem.
TRANSFORMERS |IN | |AREA i | f d
|FROM| |ZONE i |
|OWNER i |
|KV r |
|SYSTEM label|
|SUBSYSTEM label|
Where: f is outage frequency for transformer on site outages, d is outage duration for transformer
on site outages. In using IN keyword, for a three-winding transformer to be included, all of its in-
service windings must be connected to subsystem buses. In using FROM keyword, for a three
winding transformer to be included, one of its in-service windings must be connected to a
subsystem bus.
The following data record defines generic statistic data for a set of machines.
|UNITS | min_size max_size IN |AREA i | f d
|MACHINES | |ZONE i |
|OWNER i |
|KV r |
|SYSTEM label|
|SUBSYSTEM label|
Where: min_size and max_size are minimum and maximum size of generators in the set, the
MBASE of generators are checked against the limits. f is frequency of unit outage, d is duration of
unit outage.
The following data record defines generic statistic data for buses within a subsystem.
|BUSES | IN |AREA i | f d [fu du fm dm]
|ZONE i |
|OWNER i |
|KV r |
|SYSTEM label|
|SUBSYSTEM label|
Siemens Energy, Inc., Power Technologies International 6-153
PSS
E 32.0
Calculating Probabilistic Reliability Program Operation Manual
6-154 Siemens Energy, Inc., Power Technologies International
6.13.3 Analyzing Probabilistic Assessment Results
For each monitored non-transformer branch, the percent loading is either the percent current or the
percent MVA loading, according to the non-transformer branch percent loading units program
option setting (see Section 3.3.3 and activity OPTN) specified when performing contingency anal-
ysis to create Contingency Solution Output files. For monitored transformers, the percent loading is
either the percent current or the percent MVA loading, according to the transformer percent loading
units program option setting.
Three output modes are available when reporting results: post-contingency, post-tripping simula-
tion, and post-corrective actions. Each output mode corresponds to one stage in the evaluation of
a contingency. When performing multiple level contingency analysis (see Section 6.12), a running
mode is specified according to selections of options of perform multiple contingency analysis,
perform tripping simulations and perform corrective actions. The running mode determines how
many stages in a contingency analysis are involved. e.g. if all three options are selected, a contin-
gency and its following sequences: tripping events and corrective actions are simulated and then
each contingency may have one power flow solution with respect to each option stored in the
Contingency Solution Output file, the solution after a contingency being imposed, the one after
simulating tripping events triggered by the contingency, and the last one is after applying corrective
actions that are specified to relieve violations in the second solution. In other words, a contingency
analysis consists of three stages. By specifying output mode option, users have access to power
flow solutions at each stage. If power flow solutions for an output mode do not exist in the output
files, power flow solutions at previous stage will be used for the output mode. e.g., tripping simula-
tion option is disabled prior to contingency analysis, therefore there are no post-tripping solutions
in result files. If output mode is set as post-tripping, reliability results in post-tripping mode are iden-
tical to those in post-contingency mode.
When calculating probabilistic load curtailment indices, results may be quite different in different
output modes, because load curtailments may be caused by contingencies, tripping events, gener-
ation dispatch and corrective actions.
In order to better understand the output, several examples are developed with the savnw.sav power
flow case. The .sub, .mon, and .con files for contingency analysis and an example outage statistics
data file .prb for reliability assessment are provided in the example directory. Contingency analysis
is performed by multiple level contingency analysis function with simulations of tripping and correc-
tive actions sequences.
System Probabilistic Index Summary
Figure 6-33 shows the system reliability indices summary report in post-contingency output mode.
The frequency, average duration and probability for each type of problems are calculated. Impact
indices of overloads and bus voltage violations with respect to voltage limits 'AREA 2 BUSES WITH
VOLTAGE LESS THAN 0.940 (pu)' and 'AREA 2 BUSES WITH VOLTAGE GREATER THAN 1.060
(pu)' are also given. For each type of problems, the number of contingencies causing the problem,
the worst violation as well as the contingency causing the worst violation are reported. The study
subsystem is 'Entire system', study system total indices are reported at the end. The results in post-
corrective actions mode are shown in Figure 6-34. The load curtailments are found in the post-
corrective actions solutions, while voltage violations and overloads are alleviated by corrective
actions. From a system point of view, reliability indices, frequency, average duration and probability,
are almost the same in the two stages. Furthermore, the results in post-contingency mode provides
reliability indices for system problems, and the results in post-corrective actions mode provide
impacts of system problems on electricity customers.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
6
-
1
5
5
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
A
c
t
i
v
i
t
y
D
e
s
c
r
i
p
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
C
a
l
c
u
l
a
t
i
n
g
P
r
o
b
a
b
i
l
i
s
t
i
c
R
e
l
i
a
b
i
l
i
t
y
Figure 6-33. System Reliability Indices Summary in Post-Contingency Mode
Figure 6-34. System Reliability Indices Summary in Post-Corrective Action Mode
FREQ. DURATION PROB. IMPACT NO. OF WORST WORST
<-- F A I L U R E C R I T E R I A --> (OC/Y) (HOURS) (H/Y) CONT. VIOL.
AREA 2 BUSES WITH VOLTAGE LESS THAN 0.940 (PU) 11.9176 10.0 119.1 1.53 13 0.875 17_17
ZONE 5 BUSES WITH VOLTAGE DROP BEYOND 0.060 (PU) 0.3369 10.0 3.4 0.18 2 0.084 14_20
AREA 2 BUSES WITH VOLTAGE GREATER THAN 1.060 (PU) 8.9740 10.0 89.6 0.27 10 1.106 17_17
OVERLOAD (%) 0.4113 9.1 3.7 3.68 6 211.905 14_20
NOT CONVERGE 0.0511 5.0 0.3 6
ENTIRE SYSTEM TOTAL 12.3048 10.0 122.7 20
FREQ. DURATION PROB. IMPACT NO. OF WORST
<-- F A I L U R E C R I T E R I A --> (OC/Y) (HOURS) (H/Y) CONT. VIOL.
AREA 2 BUSES WITH VOLTAGE LESS THAN 0.940 (PU) 1.7018 9.9 16.8 0.29 5
AREA 2 BUSES WITH VOLTAGE GREATER THAN 1.060 (PU) 1.7198 9.8 16.9 0.07 7
ZONE 5 BUSES WITH VOLTAGE RISE BEYOND 0.055 (PU) 0.0043 5.0 0.0 0.00 2
OVERLOAD (%) 0.3361 10.0 3.4 2.49 1
LOSS OF LOAD (MW) 10.5780 10.0 105.8 14026.67 11
NOT CONVERGE 0.0511 5.0 0.3 6
ENTIRE SYSTEM TOTAL 12.3048 10.0 122.7 20
Power Flow Solution Activity Descriptions PSS
E 32.0
Calculating Probabilistic Reliability Program Operation Manual
6-156 Siemens Energy, Inc., Power Technologies International
System Loss of Load Report
The cumulative system loss of load summary provides detailed indices of loss of load for outages
in which one or more buses are separated from the remainder of the network, or load shedding is
performed at certain buses. The cumulative loss of load index represents the amount, frequency
and energy of load lost as given in increments, and accumulated. Incremental step size is 10 MW;
for load curtailment in excess of 1000 MW, it is grouped as one set.
Figure 6-35 shows system loss of load report in post-corrective actions mode. System load curtail-
ments results are dependent on the options used in the multiple level contingency analysis. The
sum of frequency, average duration and probability causing the corresponding amount of load
curtailments are reported. The interrupted power I.P. and Expected Unserved Energy E.U.E. are
provided. Note for E.U.E, the duration is one year (8760 hours). The study subsystem is specified
as 'ENTIRE SYSTEM'
Figure 6-35. System Load Curtailment Probabilistic Indices
Branch Flow Overloading Indices
Figure 6-36 shows the branch flow overload deterministic reliability results, where no outage statis-
tics are required and all contingencies are assumed to have equal statistics. The following items are
calculated: average overload and maximum loading of the overloaded circuit, the number of contin-
gencies that result in overload of this circuit, and the contingency causing maximum overload.
Figure 6-37 shows overload probabilistic indices for each circuit and for the study subsystem.
Specifically, the sum of frequency, average duration and probability of all contingencies resulting in
a circuit overload are reported. The system overload impact index is equal to the sum of overload
impact indices of all circuits. As we can see, the total number of contingencies that result in overload
problem in Figure 6-36 is much bigger than that in Figure 6-37; this is because some contingencies
with overload problems had zero statistics or statistics less than cutoff values.
Figure 6-36. Branch Flow Overloading Probabilistic Indices
<-- LOAD CURTAILMENTS --> FREQ. DURATION PROB. I.P. E.U.E NO. OF WORST CONT.
<----- (MW) -----> (OC/Y) (HOUR) (H/Y) (MW/Y) (MWH/Y) CONT.
80.0 -- 90.0 3.6272 10.0 36.4 290.17 2911.76 2 OVRLOD 14
160.0 -- 170.0 6.8657 10.0 68.9 1098.51 11029.22 2 OVRLOD 17
ENTIRE SYSTEM 10.4928 10.0 105.3 1388.68 13940.98 4
<----- O V E R L O A D E D L I N E S -----> AVG.OVRLOD MAX.LOADING NO. OF WORST CONT.
<------F R O M ------> <------ T O ----->CKT (%) (%) CONT.
ENTIRE SYSTEM 49
203 EAST230 230.00 154 DOWNTN 230.00 92.55 244.85 11 5_9
205 SUB230 230.00 154 DOWNTN 230.00 9.01 120.68 8 15_22
INTERFACE WEST 193.29 296.76 35 1_12
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
6
-
1
5
7
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
A
c
t
i
v
i
t
y
D
e
s
c
r
i
p
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
C
a
l
c
u
l
a
t
i
n
g
P
r
o
b
a
b
i
l
i
s
t
i
c
R
e
l
i
a
b
i
l
i
t
y
Figure 6-37. Branch Flow Overloading Probabilistic Indices
<------ O V E R L O A D E D L I N E S -------> FREQ. DURATION PROB. IMPACT MAX VIO. NO. OF WORST CONT.
<------ F R O M ------> <------ T O ---- -->CKT (OC/Y) (HOUR) (H/Y) (PU) (%) CONT.
ENTIRE SYSTEM 0.4113 9.1 3.7 3.68 0.00 6
203 EAST230 230.00 154 DOWNTN 230.00 0.3518 9.8 3.4 3.62 211.90 3 14_20
205 SUB230 230.00 154 DOWNTN 230.00 0.0744 5.0 0.4 0.06 120.68 4 15_22
Power Flow Solution Activity Descriptions PSS
E 32.0
Calculating Probabilistic Reliability Program Operation Manual
6-158 Siemens Energy, Inc., Power Technologies International
6.13.4 Application Notes
The probabilistic reliability assessment requires a Contingency Solution Output file and a Distribu-
tion Factor Data file. It is required that the working case contain the same network representation
(i.e., the same Saved Case) on which the contingency analysis calculation was based, and that the
same Distribution Factor Data file that was used in contingency analysis be specified; otherwise,
the probabilistic assessment function will terminate. When the base case remains unchanged, but
the Monitored Element Data file and/or the Contingency Description Data file (and therefore the Dis-
tribution Factor Data file) are changed, the contingency analysis must be performed again before
selecting the reliability assessment function. When adding new subsystems in the Subsystem
Description Data file (see Section 7.1.2) without any changes in the Monitored Element Data file
and the Contingency Description Data file, only the Distribution Factor Data file needs to be rebuilt,
the reliability assessment can be performed with the newly created DFAX file without redoing con-
tingency analysis.
The Contingency Solution Output file must be created by the multiple level contingency analysis
function in PSS
E will neglect the probability of the base case, and add up probabilities of all out-
ages with system problems to calculate probabilistic indices. However, the double counting problem
is more prominent because it is most likely that tested outages have system problems if the base
case has problems.
When probabilistic indices are used to compare the relative performance of the system under dif-
ferent operating conditions or with different system configurations, a contingency analysis must be
performed for each initial system condition (base case). The different operating conditions can be
simulated by means of load or dispatch adjustments, or by outages of specific network elements in
the pre-disturbance condition. Different system configurations can be represented using appro-
priate system adjustment activities within PSS
E 32.0
Calculating Substation Reliability Program Operation Manual
6-160 Siemens Energy, Inc., Power Technologies International
6.14 Calculating Substation Reliability
6.14.1 Substation Reliability Assessment
Overview
Station reliability evaluations can augment substation design principles to enable quantitative eval-
uation and comparison of alternative substation configurations. In general, substation reliability
studies are organized into seven steps as follows:
1. Define the system extent and list of components to be included. The study system may
include substation and incoming and outgoing lines/feeders.
2. Gather failure, repair, and maintenance data for each component within the study system.
3. Specify performance criteria for system failure and select the indices to be calculated.
4. Determine models and modeling assumptions.
5. Develop the reliability models mathematically.
6. Perform component failure effects and system analysis of enumerated states.
7. Compute reliability indices.
Run Options
Report format: allows user to select from among the following reports:
Substation component report
Contingency report
Bus load curtailment report
Substation load curtailment report
Branch rating set and Flow rating percentage: Specify branch loading limits. The limits are equal
to the specified rating multiplied by the specified percentage. The ratings are specified in MVA in
the working case. Substation reliability assessment ignores reactive power flow and assumes MW
ratings are equal to MVA ratings.
Frequency cutoff: Specify contingency frequency cutoff value in occurrences per year. Contingen-
cies with frequencies of occurrence lower than the cutoff will be excluded from substation reliability
assessment.
Run Substation Reliability Assessment - GUI
Power Flow > Reliability > Substation reliability assessment
[Substation Reliability Assessment]
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 6-161
PSS
E 32.0
Calculating Substation Reliability Program Operation Manual
6-162 Siemens Energy, Inc., Power Technologies International
DFAX excludes out-of-service buses from a system specification. Each in-service bus has to be
connected to a swing bus (bus type code of 3). DFAX checks the network connectivity by
processing the status of all branches (lines, transformers, breakers and switches/disconnects) and
terminates if a network island without a swing bus is detected. Therefore, a system after processing
by DFAX, will consist only of buses that are in-service (bus type code of no more than 3) and
connected to a swing bus. All substation components to be considered in a study must be
connected to substation buses. In case there are network islands within a substation, each island
must have a pre-assigned swing bus. Because substation reliability assessment does not perform
conventional power flow solutions, the choice of the swing bus has no impact on the substation reli-
ability assessment results.
For instance, in a substation with a main and transfer bus configuration that has the tie breaker
normally open and all branches normally connected to the main bus, the transfer bus will initially be
isolated. In order for the transfer bus to be recognized by DFAX, it must be assigned as a swing bus
so that it will be included in the substation system and available during switching operations when
the main bus fails.
The breakers and switches within the substation system are modeled as special non-transformer
branches with unique first characters in the circuit IDs: @ to designate a breaker and - to designate
a switch. Though not compulsory, the modeling of breakers and switches as zero impedance lines
(each with resistance of zero and reactance less than the zero impedance line threshold) is highly
recommended.
Breakers and switches can operate in either normally-open or normally-closed mode. The two
modes are represented by the ON and OFF statuses, respectively, of the branch.
Each breaker is assumed to have two switches, one on each side, to isolate the breaker for repair
and maintenance. These implicit switches are added automatically during substation reliability
assessment. Switches for isolating other substation components must be explicitly modeled by the
user.
6.14.3 Failure Modes
Substation reliability assessment analysis performs failure modes and effects analyses of arbitrary
bus-breaker configurations and measures the impact of substation equipment failures upon the
resulting power transfer capability of the substation. It can evaluate four modes of equipment fail-
ures as follows:
Fault: Requires operation of circuit breakers to clear the fault and isolate the faulted
component.
Common Mode Fault: A common mode fault refers to simultaneous outages of mul-
tiple components due to a common cause. It requires operation of circuit breakers to
clear the fault and isolate the faulted components. A common mode fault is specified
in the Contingency Description Data file.
Unscheduled Maintenance Outage: Unplanned or uncontrolled removal or transfer to
the open circuit state of the affected component. Component is removed immediately,
no system fault occurs.
Scheduled Maintenance Outage: Controlled or planned removal for inspection, over-
haul, test, etc. Time of removal is controllable to accommodate maintenance crews,
seasonal or weather considerations, load levels, or outage of other components.
Siemens Energy, Inc., Power Technologies International 6-163
PSS
E 32.0
Calculating Substation Reliability Program Operation Manual
6-164 Siemens Energy, Inc., Power Technologies International
Any effect of switching operations during system reconfiguration in step 6 is not considered in the
reliability assessment. Note further that the outage duration is counted from the time of fault or
outage initiation. The model for component repair is based on the following premises:
1. Component outage duration is far longer than the switching time, S;
2. Repair time, R, starts upon completion of switching.
For a single-component or common mode fault, the substation capability is evaluated at two stages:
Post-fault stage consists of steps 1 to 4 in Figure 6-39, corresponding to the period fol-
lowing the fault until reconfiguration can be effected by switching, and
Post-switching stage which consists of steps 5 and 6 corresponding to the period fol-
lowing switching operation until repair is completed.
Each stage is culminated by a check on network connectivity. Equipment that is electrically
connected is identified by processing circuit breaker status and disconnect switch positions. Thus,
equipment that is isolated and the degree of service lost can be determined. Power transfer capa-
bility of the substation is assessed by means of a transportation network flow algorithm (maximum
flow-minimum cut). The frequency (in occurrences per year), duration (in hours), and the probability
(in hours per year) of finding the system in that condition are also computed.
For an unscheduled maintenance or a scheduled outage event, a model with two states, up and
down (repair) states, as shown in Figure 6-40, is used.
Figure 6-40. Two-State Model for Scheduled and Unscheduled Outage
The sequence of switching and assessment for unscheduled maintenance or scheduled mainte-
nance is modeled as follows:
1. Perform switching to remove the component for maintenance, time to switching completion
is S.
2. Assess the effect on the substation. Post-switching state persists until component mainte-
nance is completed, duration is R.
Outage statistics of substation components are specified in the Outage Statistics Data file in the
form of frequency of occurrence and duration; by default they are zeros. The statistics data for
scheduled and unscheduled maintenance outages is optional and used only in substation reliability
study. The duration of an outage mode is repair time only and does not include switching time. In
order to include failures of the implicit switches in the substation reliability assessment, the user
should specify the outage statistics for the switches using a generic input command (see description
in Section 6.13.2). An example of an Outage Statistics Data file is shown in Figure 6-41. The record
to specify the outage statistics data for switches specifies both explicit and implicit switches.
Siemens Energy, Inc., Power Technologies International 6-165
PSS
E 32.0
Calculating Substation Reliability Program Operation Manual
6-166 Siemens Energy, Inc., Power Technologies International
Figure 6-42. Process to Assess a Failure Mode of a Component in SRA
Siemens Energy, Inc., Power Technologies International 6-167
PSS
E
3
2
.
0
C
a
l
c
u
l
a
t
i
n
g
S
u
b
s
t
a
t
i
o
n
R
e
l
i
a
b
i
l
i
t
y
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 6-43. Sample Substation Component Report
Siemens Energy, Inc., Power Technologies International 6-169
PSS
E
3
2
.
0
C
a
l
c
u
l
a
t
i
n
g
S
u
b
s
t
a
t
i
o
n
R
e
l
i
a
b
i
l
i
t
y
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 6-44. Sample Contingency Summary Report
Siemens Energy, Inc., Power Technologies International 6-171
PSS
E
3
2
.
0
C
a
l
c
u
l
a
t
i
n
g
S
u
b
s
t
a
t
i
o
n
R
e
l
i
a
b
i
l
i
t
y
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 6-45. Sample Descriptions of the Contingencies in the Summary Report
Siemens Energy, Inc., Power Technologies International 6-173
PSS
E
3
2
.
0
C
a
l
c
u
l
a
t
i
n
g
S
u
b
s
t
a
t
i
o
n
R
e
l
i
a
b
i
l
i
t
y
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 6-46. Sample Bus Load Curtailment Report
Siemens Energy, Inc., Power Technologies International 6-175
PSS
E 32.0
Performing PV/QV Analyses Program Operation Manual
6-176 Siemens Energy, Inc., Power Technologies International
6.15 Performing PV/QV Analyses
The PV/QV analyses that are described in this chapter are designed for studies of slow voltage sta-
bility, which could be analyzed as a steady-state problem. They are power flow based analyses
used to assess voltage variations with active and reactive power change. Two methods are used to
determine the loading limits imposed by voltage stability under the steady-state conditions.
The PV/QV analyses do not provide solutions to specific problem but function as tools that can be
directed by the user to perform analyses in the solution of problems associated with the steady-
state voltage stability of power systems.
Siemens Energy, Inc., Power Technologies International 6-177
PSS
E 32.0
PV Analysis Program Operation Manual
6-178 Siemens Energy, Inc., Power Technologies International
Contingency-case Solu-
tion options
The contingency-case solution options allow for a different set of automatic
adjustments of the contingency case solutions than those used in the base case
transfer increment solutions (see Section 6.2).
Tap adjustment:
Lock taps
Stepping
Direct
Area interchange control:
Disabled
Tie lines only
Tie lines and loads
Switched shunt adjustments:
Lock all
Enable all
Enable continuous, disable discrete
Enable or disable phase shift adjustments.
Enable or disable dc tap adjustments
Apply contingencies to
base case transfer
solutions
If this option is enabled, the PV_ENGINE_3 API routine is used to calculate the
analysis; PV_ENGINE_3 must be used if the base case and contingency case
solution options are not identical or if a negative minimum transfer increment is
specified.
If this option is disabled, the PV_ENGINE API routine is used to calculate the
analysis.
Solution Engine
Select the solution engines for the series of power flow calculations and
contingency studies to obtain the PV curves (see Section 6.2).
Fixed slope decoupled Newton-Raphson (FDNS) (default)
Full Newton-Raphson (FNSL)
Optimized fixed slope decoupled Newton-Raphson (FDNS)
Non-divergent solution Flag to enable or disable (default) option in each power flow solution.
Var Limit Code
Select the var control options limit code for either of the following cases:
Contingency case initial power flow solution
Subsequent transfer increment cases
The var limit control can be set for either case as follows:
Apply immediately: limit the var output of all generators
Initially ignore, then apply: Ignore var limit at initial iterations and then
apply automatically afterwards
Table 6-26. PV Analysis Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 6-179
PSS
E 32.0
PV Analysis Program Operation Manual
6-180 Siemens Energy, Inc., Power Technologies International
Positive load flag for
transfer dispatch methods
using loads
Select one of the following, if appropriate:
No limits (default)
Enforce non-negative active power constant MVA loads
Mismatch tolerance
Tolerance used to check for the largest initial active or reactive power mismatch.
If exceeded, the process is terminated. This value is also used as the conver-
gence tolerance in the power flow solution of each contingency and transfer
increment case (see Section 6.2).
Initial transfer increment
(MW)
Starting transfer increment value. This value will be the initial transfer increment
step size in MW between the two defined subsystems.
Min monitored bus voltage
in pu for terminating anal-
ysis for this system
condition
Minimum voltage value for termination of calculation. If the low voltage check is
enabled, calculations will stop if any monitored voltage is less than this value.
Transfer increment toler-
ance (MW)
Largest acceptable difference in transfer level between a transfer level for which
a solution is found and a higher transfer level which fails to achieve
convergence.
Maximum incremental
transfer (MW)
Maximum transfer in MW between the two specified subsystems.
Minimum incremental
transfer (MW)
Minimum transfer in MW between the two specified subsystems.
Branch overload threshold
(%)
Threshold in determining branch overloads.
Rating set
Line loading limit used in determining overloads. If the branch loading check is
enabled, calculations will stop if any monitored branches are overloaded beyond
this limit.
Enable the low voltage
check
If enabled, the calculations will stop if any monitored voltage is less than the
minimum monitored voltage specified.
Enable the branch loading
check
If enabled, the calculations will stop if any monitored branches are overloaded
beyond the limit specified by overload threshold and rating set.
Subsystem selection
Subsystems for the power transfer from the study system to the opposing
system.
Distribution Factor Data
File
(*.dfx) a required file to be build by activity DFAX that corresponds to the network
condition contained in the working case (refer to Section 7.1.6) and to the
desired linear network analysis data files (refer to Section 7.1.1). The bus input
option (refer to Section 3.3.3 and activity OPTN) must have the same setting
that was in effect when activity DFAX filled the specified Distribution Factor Data
file. Refer to Section 2.4.1 for the file specification conventions used by the AC
Contingency Solution function.
Table 6-26. PV Analysis Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 6-181
PSS
E 32.0
PV Analysis Program Operation Manual
6-182 Siemens Energy, Inc., Power Technologies International
A negative minimum incremental transfer is specified.
Either PV_ENGINE_3 or PV_ENGINE may be used if both of the following conditions are satisfied:
The same set of automatic adjustments is specified for the base case and contingency
case solutions.
0.0 is specified for the minimum incremental transfer.
The results window for PV analysis will be displayed after calculations are initiated.
Select the type of graph you wish to plot and select the items of interest from the following:
Bus voltages: Plots bus voltages against incremental power transfer of selected base
case or contingencies.
Generator MW: Plots generator MW output against incremental power transfer of selected
base case or contingencies.
Branch MVA Flow: Plots branch MVA against incremental power transfer of selected base
case or contingencies.
Interface MW Flow: Plots interface MW against incremental power transfer of selected
base case or contingencies.
Bus voltage against interface flow: Plots the selected bus voltage against interface flow.
Items in the list may be selected individually or as a continuous set. The results are plotted as a
graph. Graph axis parameters are fully adjustable. Scale values are adjustable for both vertical and
horizontal axes. Additional options are available for printing clarity.
6.16.1 Retrieving Results from a Previous PV Analysis
Select a previously saved PV results file (*.pv). Parameters used for the selected PV analysis will
be shown. These values are for reference only and are not editable.
6.16.2 Implementing a Specific PV Transfer
It is often important to study the performance of the power system at or near the transfer limit that
had been determined by a PV analysis study. The implement PV transfer function may be used to
implement a transfer between designated source and sink systems using the same transfer dis-
patch methods that are available in the PV analysis function.
Run Activity PV Analysis, Previous Results Retrieved - GUI
Power Flow > Solution > PV analysis using previous results
[PV Parameters]
Run Activity PV Transfer - GUI
Power Flow > Solution > Implement PV transfer
[Implement PV Transfer]
Siemens Energy, Inc., Power Technologies International 6-183
PSS
E 32.0
QV Analysis Program Operation Manual
6-184 Siemens Energy, Inc., Power Technologies International
6.17 QV Analysis
Run Activity QV Analysis - GUI
Power Flow > Solution > QV analysis
[QV Analysis]
Interrupt Control Codes
AB
Table 6-27. QV Analysis Options
Option Description
Bus number
Bus number for analysis. Filters may be applied to the bus selector for name
mask, number range, kV range, and bus type.
Solution options
Select solution options for the series of power flow calculations performed to
obtain the QV curves (see Section 6.2).
Tap adjustment:
Lock taps (default)
Stepping
Direct
Area interchange control:
Disabled (default)
Tie lines only
Tie lines and loads
Switched shunt adjustments:
Lock all
Enable all (default)
Enable continuous, disable discrete
Non-divergent solution
Flag to enable or disable (default) option in the power flow solution of each
contingency case.
Adjust phase shift
Flag to enable or disable (default) option in the power flow solution of each
contingency case.
Adjust dc taps
Flag to enable (default) or disable option in the power flow solution of each
contingency case.
Solution Engine
Select the solution engines for the series of power flow calculations and
contingency studies to obtain the PV curves (see Section 6.2).
Fixed slope decoupled Newton-Raphson (FDNS) (default)
Full Newton-Raphson (FNSL)
Optimized fixed slope decoupled Newton-Raphson (FDNS)
Siemens Energy, Inc., Power Technologies International 6-185
PSS
E 32.0
QV Analysis Program Operation Manual
6-186 Siemens Energy, Inc., Power Technologies International
6.17.1 Retrieving Results from a Previous QV Analysis
Select a previously saved QV results file (*.qv). Parameters used for the selected QV analysis will
be shown. These values are for reference only and are not editable.
Run Activity QV Analysis, Previous Results Retrieved - GUI
Power Flow > Solution > QV analysis using previous results
[QV Parameters]
Additional Information
PSS
E 32.0
Basic Engineering Guide to PV and QV Curves Applications Program Operation Manual
6-188 Siemens Energy, Inc., Power Technologies International
(6.20)
where:
The loading of the network can be increased by decreasing the value if Z
LD
. This is done with E
s
,
load power factor and line parameters fixed. From Equation 6.19, as ZLD is decreased gradually
the load power, P
R
, increases, hence the power transmitted will increase. As the value of Z
LD
approaches Z
LN
the value of P
R
starts to decrease gradually due to F. However, from Equation 6.20
as Z
LD
decreases the receiving voltage V
R
decreases gradually.
The plot of the relationship between voltage at the receiving end, V
R
, and the load power, P
R
, as
the power transfer is increased due to increase loading, gives the PV curves similar in characteristic
to the curve shown in Figure 6-49.
PV curves are typically used for the knee curve analysis. It is as named because of its distinctive
shape at the point of voltage collapse as the power transfer increases, as shown in Figure 6-49.
Depending on the transfer path, different buses have different knee point. The buses closer to the
transfer path will normally exhibit a more discernible knee point.
Figure 6-49. PV Curves Voltage and Incremental Power Transfer
Characteristics
Voltage instability occurs at the knee point of the PV curve where the voltage drops rapidly with an
increase in the transfer power flow. The power flow solution will not converge beyond this limit, indi-
cating voltage instability. Operation at or near the stability limit is impractical and a satisfactory
operating condition must be ensured to prevent voltage collapse.
In PSS
E, the PV curves are generated by selecting two subsystems where the power transfer
between the subsystems is incremented in a defined step size for a series of ac power flow calcu-
lations while the bus voltages, generator outputs and the branch flows of the system are monitored.
When the bus voltages are plotted as a function of the incremental power transfer the PV curves
are obtained. One of the subsystems in the study must be defined as the study (source) system and
V
R
= E
s
\
1
F
Z
LD
Z
LN
cos(u - |)
Z
LD
Z
LN
F = 1 + + 2
2
Z
LD
Z
LN
Siemens Energy, Inc., Power Technologies International 6-189
PSS
E 32.0
Basic Engineering Guide to PV and QV Curves Applications Program Operation Manual
6-190 Siemens Energy, Inc., Power Technologies International
Figure 6-50. PV Curves Voltage and Incremental Power Transfer
Characteristics for Bus 203 under Different Network Conditions
Siemens Energy, Inc., Power Technologies International 6-191
PSS
E 32.0
Basic Engineering Guide to PV and QV Curves Applications Program Operation Manual
6-192 Siemens Energy, Inc., Power Technologies International
Figure 6-52. Generator Output Versus Power Transfer Curves
6.18.3 QV Analysis (QV Curves) Applications
In the PV curve analysis we have demonstrated the effect of active power flow on voltage instability.
However, if we revisit Equation 6.19 and Equation 6.20, we see that the power factor of the load
has a significant impact on the overall equations. This is to be expected because the voltage drop
in the line is a function of both active and reactive power transfer. Hence, the QV curves may also
be used to assess voltage stability of the system.
QV curves are used to determine the reactive power injection required at a bus in order to vary the
bus voltage to the required value. The curve is obtained through a series of ac power flow calcula-
tions. Starting with the existing reactive loading at a bus, the voltage at the bus can be computed
for a series of power flows as the reactive load is increased in steps, until the power flow demon-
strates convergence difficulties as the system approaches the voltage collapse point.
Figure 6-53 is a typical of the QV curves that will be generated for a system that is stable at mod-
erate loading and unstable at higher loadings.
Siemens Energy, Inc., Power Technologies International 6-193
PSS
E 32.0
Basic Engineering Guide to PV and QV Curves Applications Program Operation Manual
6-194 Siemens Energy, Inc., Power Technologies International
Figure 6-54. QV Curves and Characteristics of a Capacitor Bank Required at
Stable Operating Point
Figure 6-55 shows the QV curves for a range of capacitor banks with different rating super-imposed
on the system's QV curves under different loading conditions. From the plot we can determine that
capacitor rating of 300 Mvar is required to maintain 1 pu voltage at loading of 1300 MW, 450 Mvar
at 1500 MW and so on.
For the case of very high loading at 1900 MW, even though the capacitor bank rating of 950 Mvar
can maintain a voltage of 1 pu, point B is not a stable operating point. If there is a drop in voltage
from point B to B', the ability of the capacitor to supply reactive power is decreased more than the
drop in requirement of the system. This will result in continuous drop in voltage. Alternatively, if the
voltage is increased above point B, the capacitor will supply more reactive power than the increase
in requirement of the system. This will result in continuous rise in voltage.
Hence, the criterion for stable operating point when using a reactive power compensator is as
follow:
System dQ/dV > Compensator dQcomp/dV
where:
For the case of light loading at 1300 MW with capacitor rating of 300 Mvar, point A is a stable oper-
ating point. If the voltage is increased from point A to A', the capacitor will supply less reactive power
than the increase in system's demand, hence reducing the voltage to 1 pu. Alternatively, if the
voltage is decreased from point A towards the bottom of the QV curve, the capacitor will supply
more reactive power than the system's demand, hence returning the voltage to 1 pu.
dQ/dV is the change of the system's reactive power, Q, with respect to voltage, V.
dQcomp/dV is the change of the compensator's reactive power output, Qcomp, with
respect to voltage, V.
Siemens Energy, Inc., Power Technologies International 6-195
PSS
E
3
2
.
0
B
a
s
i
c
E
n
g
i
n
e
e
r
i
n
g
G
u
i
d
e
t
o
P
V
a
n
d
Q
V
C
u
r
v
e
s
A
p
p
l
i
c
a
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 6-56. QV Curves under Various Contingencies for Bus 103
Siemens Energy, Inc., Power Technologies International 6-197
PSS
E
3
2
.
0
B
a
s
i
c
E
n
g
i
n
e
e
r
i
n
g
G
u
i
d
e
t
o
P
V
a
n
d
Q
V
C
u
r
v
e
s
A
p
p
l
i
c
a
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 6-57. QV Curve in Base Case with Increase in Load on Bus 103
Siemens Energy, Inc., Power Technologies International 6-199
PSS
E
3
2
.
0
B
a
s
i
c
E
n
g
i
n
e
e
r
i
n
g
G
u
i
d
e
t
o
P
V
a
n
d
Q
V
C
u
r
v
e
s
A
p
p
l
i
c
a
t
i
o
n
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 6-58. S-Shaped QV Curve on Bus 108
Siemens Energy, Inc., Power Technologies International 6-201
PSS
E 32.0
Basic Engineering Guide to PV and QV Curves Applications Program Operation Manual
6-202 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 7-1
Chapter 7
Linear Network Analysis
7.1 Building the Distribution Factor Data File
Activity DFAX
The Distribution Factor File setup activity DFAX reads a set of Linear Network Analysis Data Files
(refer to Section 7.1.1) and reflects their contents in a Distribution Factor Data File in preparation for
any of activities OTDF, DCCC, TLTG, POLY, SPIL, IMPC, LLRF, and ACCC. Activity DFAX also
calculates line outage distribution factors and preserves them in the Distribution Factor Data File.
Subsystems of the working case are specified in a Subsystem Description Data File, monitored
elements are specified in a Monitored Element Data File, and contingencies are specified in a
Contingency Description Data File.
The Distribution Factor File setup activity reads a set of Linear Network Analysis Data Files and
reflects their contents in a Distribution Factor Data File in preparation for performing automatic ac
contingency analysis as well as a variety of other analyses including dc contingency testing, gener-
ator contingency analysis and transfer limit identification.
Input for the process of creating the Distribution Factor file is contained in three data files:
Subsystem Description Data file; relevant subsystems of the working case are speci-
fied in this *.sub file.
Monitored Element Data file; network elements to be monitored for problems are
specified in this *.mon file.
Run Activity DFAX - GUI
Power Flow > Linear Network > Build distribution factor data file (DFAX)
[Build Distribution Factor Data File]
Run Line Mode Activity DFAX - CLI
ACTIVITY?
>>DFAX
ENTER FILENAME FOR STORING DISTRIBUTION FACTORS
Interrupt Control Codes
None
Linear Network Analysis PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-2 Siemens Energy, Inc., Power Technologies International
Contingency Description Data file; contingencies to be tested are specified in this
*.con file.
7.1.1 Linear Network Analysis Data Files
This section contains details on the formats of the data input files used by activity DFAX. File Nota-
tional Conventions defines the notational conventions used in the data record descriptions defined
below. Special Data Records describes those records that are common to all of the Linear Network
Analysis Data Files. Section 7.1.2 gives the record formats used in the Subsystem Description Data
File, Monitored Element Data File Contents describes the Monitored Element Data File, and Contin-
gency Description Data File Contents defines the Contingency Description Data File.
File Notational Conventions
In describing the input file syntax, the following notational conventions are used:
Keywords and data values must be separated by one or more blanks.
CAPITALS Keyword that must be specified exactly as shown. No keyword abbreviations are
allowed.
[ ] Items enclosed in square brackets are optional keywords and/or values.
| A| or A| B
|B|
Specify one from the list separated by, or enclosed in, the vertical bars.
bsid Bus identifier; this data value must be a bus number when the numbers input option
is in effect, and an extended bus name (twelve character name plus bus base
voltage) when the names input option is in effect (refer to Section 3.3.3 and activity
OPTN). If an extended bus name contains blanks or special characters, it must be
enclosed in single quotes.
ckid One- or two-character circuit identifier.
mcid One- or two-character machine identifier.
devid FACTS device or dc line name; up to twelve characters. If a device name contains
blanks or special characters, it must be enclosed in single quotes.
i An integer value.
r A floating point value; the decimal point is optional when specifying a whole number
(e.g., 10, 10., and 10.0 all specify the floating point number ten).
file A filename.
label A 12-character label identifier. If a label contains blanks or special characters, it
must be enclosed in single quotes.
Siemens Energy, Inc., Power Technologies International 7-3
PSS
E
reporting and processing activities (refer to Section 4.8).
The portion of the working case to be contained in each subsystem being defined is specified in the
following block structure:
SUBSYSTEM|SYSTEM [label]
(subsystem specification data record)
.
.
(subsystem specification data record)
END
The subsystem specification data records allowed are as described below.
The optional subsystem labels are used on several record types in the Monitored Element and
Contingency Description Data Files; they are also printed in the line mode dialog of activity TLTG,
SPIL, and POLY, which summarizes the subsystems defined and allows the user to select the study
and opposing systems. If no label is specified on a SUBSYSTEM record, the label UNNAMED n is
assigned to the subsystem, where < n > is a unique integer. Up to 100 subsystems may be specified
in a Subsystem Description Data File, and each subsystem must be defined within a single
SUBSYSTEM block structure.
Buses can be selected to be in included in a SUBSYSTEM or SYSTEM using a series of criteria;
that is selecting by BUS, AREA, ZONE, OWNER and KV. Furthermore, buses can be selected on
an individual basis or in groups.
TRACE Enable or disable input tracing. When enabled, each line read from the input file is
written to the Progress tab or the users designated output file; refer to Section 4.4.
Tracing is initially disabled.
ECHO file Write each input line to the designated file; if the filename specification contains any
blanks or slashes ( / ), it must be enclosed in single quotes. Echoing of input records
is useful when data records are being entered interactively and the same set of
input records will be used in subsequent executions of activity DFAX. The file spec-
ified here is completely independent of any file specified to the PSS
E activity
ECHO (refer to Section 15.12, Running a Response File and Section 15.13,
Recording User Actions). Refer to Section 2.4.1 for the file specification conven-
tions used by activity DFAX.
COM Comment line that is ignored during input processing. Any meaningful comments
may be placed on a comment line following the COM keyword.
END End of block structure or end of data input, as appropriate.
Linear Network Analysis PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-4 Siemens Energy, Inc., Power Technologies International
Selecting buses by number requires data records of the following form:
BUS bsid
BUSES bsid bsid
The BUSES record is valid only when the numbers input option is in effect (refer to Section 3.3.3
and activity OPTN), and assigns the designated buses, as well as all buses where bus numbers fall
between the two bus numbers specified, to the subsystem being defined. For example, the data
record BUSES 15 77 may be used to select all buses with numbers from 16 to 76, inclusive.
All buses in selected areas may be assigned to a subsystem with data records in the following
format:
AREA i
AREAS i i
where i is an area number. The AREAS record type assigns all buses in a range of area numbers
to the subsystem being defined. For example, the data record AREAS 5 7 may be used to assign
all buses in areas five, six, and seven to the subsystem.
Similarly, all buses in selected zones and owners may be assigned to a subsystem with data
records of the following form:
ZONE i
ZONES i i
OWNER i
OWNERS i i
Buses at designated voltage levels may be assigned to a subsystem with records of the following
form, where, as above, the KVRANGE record defines a range of voltage levels:
KV r
KVRANGE r r
Note that, in specifying ranges of bus numbers, areas, zones, owners, and voltage levels, the
second value specified must not be preceded with a minus sign. The second number specified
must be greater than the first.
In addition, a join group block structure provides for the specification of a group of buses through
the logical anding of two or more of the five selection criteria described above. A join group has the
following block structure:
JOIN [label]
(subsystem specification data record)
.
.
(subsystem specification data record)
END
where each subsystem specification data record is one of the simple record types (BUS, AREA,
ZONE, OWNER, KV, or the corresponding range of records) described above. The optional JOIN
group label is for the users convenience and is neither used by activity DFAX nor preserved in the
Distribution Factor Data File.
Siemens Energy, Inc., Power Technologies International 7-5
PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-6 Siemens Energy, Inc., Power Technologies International
7.1.3 Monitored Element Data File Contents
This file identifies those elements, or groups of elements that are to be monitored for flow violations
and those buses that are to be monitored for voltage violations.
Flow Monitoring Records
Each monitored element may consist of either a single branch or a group of branches (an interface),
where the flow on an interface is taken as the sum of the flows on the branches comprising the
interface.
Up to 1,000 interfaces are allowed, and the total of single branches plus branches contained in all
interfaces may not exceed the number of branches for which PSS
E is dimensioned. Only
in-service branches are added to the monitored element list.
To specify a single branch for monitoring, the following data record may be used:
To specify one winding of a three-winding transformer for monitoring, the bus to which the winding
is connected must be the first bus specified in the following data record:
If the optional circuit identifier keyword and data value are omitted, a circuit identifier of '1' is
assumed.
As a convenience to save typing, the following block structure may be used to designate a series
of single branches for monitoring where, as above, the default circuit identifier is '1'. Three-winding
transformers cannot be specified using this block structure.
[MONITOR] BRANCHES|LINES
bsid bsid [ckid]
.
.
bsid bsid [ckid]
END
In specifying a branch with the above records, if it is already in the monitored element list in the
specified direction, an appropriate message is printed and the record is ignored. If a branch is
included in the monitored element list in both directions, flows (and distribution factors) for the two
entries are printed in activities OTDF, DCCC, TLTG, SPIL, IMPC, and POLY with equal magnitude
and opposite sign; in activity ACCC, the same results are shown in both directions.
When the multi-section line reporting option is enabled (refer to Section 3.3.3 and activity OPTN),
in-service multi-section line groupings may be specified with the above records. If an in-service
member of a multi-section line grouping is specified, the multi-section line (rather than the specified
member) is added to the monitored element list in the same direction as the specified member.
MONITOR] |BRANCH| FROM BUS bsid TO BUS bsid |CIRCUIT| ckid
|LINE |
|CKT |
[ M O N I T O R ] | B R A N C H | F R O M B U S b s i d T O B U S b s i d T O B U S b s i d | C I R C U I T | c k i d
| L I N E | |C K T |
Siemens Energy, Inc., Power Technologies International 7-7
PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-8 Siemens Energy, Inc., Power Technologies International
For a three-winding transformer to be included, at least one of its in-service windings must be
connected to a subsystem bus, and at least one of its in-service windings must be connected to a
bus that is either not in the subsystem or in the to subsystem, as appropriate; for any such three-
winding transformer, all of its in-service windings connected to subsystem buses are added to the
monitored element list.
For a tie branch between a pair of subsystems to be added to the monitored element list, both of
the following must be satisfied:
1. One bus is in the from subsystem.
2. Another bus is in the to subsystem, and it is not in the from subsystem.
For the case of disjoint subsystems (e.g., TIES FROM AREA 1 TO AREA 2), the selection of tie
branches is clear and unambiguous. However, in the case of overlapping subsystems (e.g., TIES
FROM AREA 1 TO ZONE 5), the user must be aware of the above rules in specifying TIES records.
The possibility exists that, in applying the above criteria, the set of branches included as ties may
not be the same if the from and to subsystems are interchanged. Consider, for example, the
following area and zone assignments:
Furthermore, assume that a branch exists between each pair of buses. The record TIES FROM
AREA 1 TO ZONE 5 would include the branches 1-3, 2-3, and 4-3, but not 1-2, 1-4, or 2-4.
Conversely, the record TIES FROM ZONE 5 TO AREA 1 would include the branches 2-1, 3-1, and
4-1, but not 2-3, 2-4, or 3-4.
When the multi-section line reporting option is enabled (refer to Section 3.3.3 and activity OPTN),
the subsystem assignments of the dummy buses of each multi-section line grouping are ignored; a
multi-section line grouping is treated as a tie branch if and only if its endpoint buses satisfy items
(1) and (2) above. When the multi-section line reporting option is disabled, the multi-section line
grouping definitions are ignored and any member of a multi-section line grouping satisfying items
(1) and (2) above is considered a tie branch.
Bus Area Zone
1 1 10
2 1 5
3 2 5
4 1 5
[MONITOR] TIES FROM |AREA i | TO |AREA i |
|ZONE i | |ZONE i |
|OWNER i | |OWNER i |
|KV r | |KV r |
|SYSTEM label | |SYSTEM label |
|SUBSYSTEM label | |SUBSYSTEM label |
Siemens Energy, Inc., Power Technologies International 7-9
PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-10 Siemens Energy, Inc., Power Technologies International
Voltage Monitoring Records
Buses that are to be monitored for voltage violations by the AC Contingency Solution (refer to
Section 6.10.1) are specified in the Monitored Element Data File. Two types of voltage violations
may be detected.
The following data record defines a voltage band along with a set of buses where voltages are to
be checked against the band.
[MONITOR] VOLTAGE RANGE |ALL BUSES | r [r]
|AREA i |
|ZONE i |
|OWNER i |
|KV r |
|SYSTEM label |
|SUBSYSTEM label|
|BUS bsid |
where the first r value is the lower bound of the per unit voltage band and the optional second r
value is the upper bound. If the upper bound is omitted, the upper end of the band is not checked.
The following data record defines voltage drop and voltage rise deviation thresholds along with a
set of buses where voltage changes in contingency cases from their base case values are to be
checked.
[MONITOR] VOLTAGE DEVIATION |ALL BUSES | r [r]
|AREA i |
|ZONE i |
|OWNER i |
|KV r |
|SYSTEM label |
|SUBSYSTEM label|
|BUS bsid |
where the first r value is the magnitude of voltage drop in per unit and the optional second r value
is the magnitude of voltage rise. If the voltage rise threshold is omitted, the voltage rise check is
omitted.
7.1.4 Contingency Description Data File Contents
Contingency cases are designated in a Contingency Description Data File. While activity OTDF
allows only single event contingencies, the remaining activities provide for contingency cases
consisting of up to sixteen events.
The Contingency Description Data File provides two means by which contingency cases may be
specified. Individual contingency cases consisting of single or multiple events involving bus
boundary condition and/or branch status changes may be specified in a contingency case block
structure (refer to Contingency Case Block Structure). In addition, the selection of a group of single
or double line outage contingency cases may be specified with a single data record (refer to Auto-
matic Contingency Specification).
Siemens Energy, Inc., Power Technologies International 7-11
PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-12 Siemens Energy, Inc., Power Technologies International
Similarly, all windings of an out-of-service three-winding transformer may be placed in-service with
a record of the form:
The outaging of one winding of a three-winding transformer is specified with the following record,
where the default circuit identifier is 1 if this specification is omitted:
Similarly, one winding of a three-winding transformer may be placed in-service with a record of the
form:
The winding to be opened or closed is the winding connected to the first bus specified. Prior to
opening one winding of a three-winding transformer, all three windings of the transformer must be
in-service; prior to closing one winding of a three-winding transformer, the other two windings of the
transformer must be in-service.
An in-service FACTS device or dc line may be blocked with a record of the form:
BLOCK |TWOTERMDC | devid
|MULTITERMDC|
|VSCDS |
|FACTS |
where the four tokens in the selection list allow access to two-terminal dc lines, multi-terminal dc
lines, VSC dc lines, and FACTS devices, respectively.
The settings of an in-service two terminal dc line may be specified with a record of the form:
SET TWOTERMDC devid TO r|MW |
|AMPS|
|KV |
When keyword MW is used, the two terminal dc line must be in power control mode and r is the
power demand to be designated. When keyword AMPS is used, the two terminal dc line must be in
current control mode and r is the current demand to be designated. The scheduled compounded
dc voltage is changed to r when keyword KV is employed.
The outaging of all in-service branches connected to a bus may be specified with a record of the
form:
|DISCONNECT|BUS bsid
|OPEN |
|TRIP |
CLOSE |BRANCH| FROM BUS bsid TO BUS bsid TO BUS bsid |CIRCUIT| ckid
|LINE | |CKT |
|DISCONNECT| THREEWINDING AT BUS bsid TO BUS bsid TO BUS bsid |CIRCUIT| ckid
|OPEN| |CKT |
|TRIP|
CLOSE THREEWINDING AT BUS bsid TO BUS bsid TO BUS bsid |CIRCUIT| ckid
|CKT |
Siemens Energy, Inc., Power Technologies International 7-13
PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-14 Siemens Energy, Inc., Power Technologies International
When the PERCENT keyword is specified, the magnitude of the initial value of the quantity to be
modified is used to determine the amount of the change; i.e.,
In changing either by PERCENT or MW, when the quantity to be modified is initially positive and the
change is a reduction (i.e., r is negative), a negative result is treated as an error condition.
The presence of the optional keyword DISPATCH is handled as described above for the SET data
record.
The next two data record types are similar to the CHANGE record, except the direction of the
change is defined by the first keyword, and r must be a positive number:
|INCREASE| BUS bsid |GENERATION| BY r |MW | [DISPATCH]
|RAISE | |LOAD | |PERCENT|
|SHUNT |
|DECREASE| BUS bsid |GENERATION| BY r |MW | [DISPATCH]
|REDUCE | |LOAD | |PERCENT|
|SHUNT |
The presence of the optional keyword DISPATCH is handled as described above for the SET data
record.
Similarly, keyword MVAR can be used in CHANGE/INCREASE/DECREASE commands to change
reactive power component of bus fixed shunts, e.g.:
|DECREASE| BUS bsid |SHUNT| BY r |MVAR |
|REDUCE |
The following data record is used to transfer load or generation from one bus to another:
MOVE r |MW | |GENERATION| FROM BUS bsid TO BUS bsid
|PERCENT| |LOAD |
|SHUNT |
When transferring MW, the power shift, P
sh
, is set to r; when the PERCENT keyword is specified,
the power shift is calculated as:
where P
orig
is initial load or generation, as appropriate, at the from bus. The power shift is then
subtracted from the original power at the from bus and added to the original power at the to bus.
When the quantity to be modified at the from bus is initially positive, a negative post-shift power at
the from bus is treated as an error condition.
When generation is being transferred, the from bus must have in-service generation. If the to bus
is not a generator bus, an appropriate message is printed and the power shift is treated as negative
load at the to bus. Either of the two buses may be a swing bus.
The keyword MVAR can be used to transfer the reactive power component of bus fixed shunts with
the data record:
P
new
= P
orig
+
r x |P
orig
|
100.
P
sh
=
r x |P
orig
|
100.
Siemens Energy, Inc., Power Technologies International 7-15
PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-16 Siemens Energy, Inc., Power Technologies International
All branches within a specified subsystem may be outaged, either singly or in pairs, by entering the
data record:
|SINGLE | |BRANCH| IN |AREA i |
|DOUBLE | |LINE | |ZONE i |
|BUSDOUBLE| |BREAKER| |OWNER i |
|PARALLEL | |KV r |
|SYSTEM label |
|SUBSYSTEM label|
The DOUBLE, BUSDOUBLE, and PARALLEL contingency specification records all generate
contingency cases consisting of two simultaneous line outages. The DOUBLE record generates all
combinations of double line outage contingencies for all branches where endpoint buses are
contained in the specified subsystem. That is, each branch in the subsystem is outaged in turn with
every other branch in the subsystem. DOUBLE may be viewed as considering independent events
causing simultaneous outages.
The BUSDOUBLE record is more restrictive than the DOUBLE record. For each bus in the specified
subsystem, it generates all combinations of double line outage contingencies for all branches
between that bus and other subsystem buses. BUSDOUBLE may be viewed as considering single
events in substations that affect pairs of branches connected to a substation.
The PARALLEL record is more restrictive than the BUSDOUBLE record. It generates double line
outage contingencies only for parallel branches (i.e., for each contingency case, the two branches
being outaged connect the same pair of subsystem buses). Three-winding transformer contingen-
cies are not generated by the PARALLEL record. PARALLEL may be viewed as considering single
events on rights-of-way that affect pairs of branches on a right-of-way.
In using the SYSTEM or SUBSYSTEM keywords, the label must correspond to a subsystem label
specified in a previously accessed Subsystem Description Data File (refer to Section 7.1.2).
All in-service buses within a specified subsystem may be singly disconnected with the data record:
SINGLE BUS IN |AREA i |
|ZONE i |
|OWNER i |
|KV r |
|SYSTEM label |
|SUBSYSTEM label|
Each single bus outage is converted to as many OPEN BRANCH commands as are required to
open all in-service branches connected to the bus before it is passed to Distribution Factor Data
File.
In-service machines connected to in-service generator buses within a specified subsystem may be
removed from service singly with the data record:
SINGLE |MACHINE| IN |AREA i |
|UNIT| |ZONE i |
|OWNER i |
|KV r |
|SYSTEM label |
|SUBSYSTEM label|
Siemens Energy, Inc., Power Technologies International 7-17
PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-18 Siemens Energy, Inc., Power Technologies International
Branches specified in a SKIP block structure apply only to SINGLE, DOUBLE, BUSDOUBLE, and
PARALLEL contingency specification records that are below it in the Contingency Description Data
File. Multiple SKIP block structures are allowed, and each SKIP block structure appends to the list
of branches to be omitted from outaging as a result of subsequent automatic contingency specifi-
cation records.
When the multi-section line reporting option is enabled and a branch that is a member of a multi-
section line is specified, the multi-section line is excluded from outaging. When the multi-section line
reporting option is disabled and a multi-section line is specified, an error message is printed and the
record is ignored.
7.1.5 Operation of Activity DFAX
Activity DFAX first checks that generators are not converted (refer to CONG) and that each non-
Type 4 bus is connected back to a Type 3 (swing) bus through the in-service ac network. If any viola-
tions are detected, an appropriate message is printed.
The user must specify the filename of the Distribution Factor Data File into which the results of
activity DFAX are saved.
The user defines subsystems of the working case from data records taken from either a designated
Subsystem Description Data File or the dialog input device. Refer to Section 7.1.2 for data input
formats.
Subsystem definitions are required if the Distribution Factor Data File is to be used by activities
TLTG, SPIL, and/or POLY. Activities OTDF, DCCC, IMPC, LLRF, and ACCC do not require
subsystem definitions unless subsystems are referenced in the Monitored Element Data File and/or
the Contingency Description Data File specified below.
The user constructs a monitored element list from data records taken from either a designated
Monitored Element Data File or the dialog input device, as appropriate. Refer to Monitored Element
Data File Contents for data input formats.
The user may have the branches in the monitored element list sorted in the reports of activities
OTDF, DCCC, POLY, IMPC, LLRF, and AC Contingency Solution.
If the sort option is specified, branches are sorted in ascending numerical or alphabetical order
according to the bus output option currently in effect (refer to Section 3.3.3 and activity OPTN).
Branches are sorted by from bus, and, for each from bus, by to bus and circuit identifier.
If the sort option is not specified, monitored branches remain in the same order in which they were
specified in the Monitored Element Data File. In either case, interfaces are reported after all moni-
tored branches in the order in which they were specified in the Monitored Element Data File.
Contingencies may be specified from either a designated Contingency Description Data File or the
dialog input device. Refer to Contingency Description Data File Contents for data input formats.
Activity DFAX reads the Contingency Description Data File, updating internal arrays and transfer-
ring the contingency definitions into the Distribution Factor Data File. Any contingency case
specifications in which errors are detected generate an alarm and are skipped.
Siemens Energy, Inc., Power Technologies International 7-19
PSS
E activities, as follows:
Calculate distribution factors disabled: activities ACCC, IMPC, and LLRF
Calculate distribution factors enabled: activities OTDF, DCCC, TLTG, SPIL, and POLY
If the distribution factor calculation is specified (default = enabled), activity DFAX continues its
processing. If a new ordering of network buses is required, an appropriate message is printed and
activity ORDR is automatically executed. The base case susceptance matrix is then constructed,
followed by the calculation of vectors of line outage distribution factors corresponding to line outage
contingency events contained in the Contingency Description Data File. Whenever a line outage
contingency results in the presence of a swingless island, an appropriate message is printed prior
to calculating the corresponding distribution factor vector.
A Distribution Factor Data File containing this additional information is required by activities OTDF,
DCCC, TLTG, SPIL, and POLY; it may also be used by activities IMPC, LLRF, and ACCC.
Refer to Section 2.4.1 for the file specification conventions used by activity DFAX.
7.1.6 Application Notes
Activity DFAX derives line outage distribution factors from the same linearized network model used
in the dc analogy network solution method of activity DCLF. While injection methods rather than
complete dc power flow solutions are used to calculate line outage distribution factors, the
comments in Section 7.4.4 apply here as well. Note, in particular, the approximate nature of the
linearized network model.
Activity DFAX needs to be executed before using activities OTDF, DCCC, TLTG, SPIL, POLY,
IMPC, LLRF, or ACCC. Because the line outage distribution factors and other information stored in
the Distribution Factor Data File are a function of data organization and network topology in the
working case, it follows that it must be re-executed before entering these activities any time one or
more of the following occurs:
Change of bus type code
Change of machine, load or branch status
Change of branch reactance
Change in the group of branches modeled as zero impedance lines
Change of metered end of a multi-section line when the multi-section line reporting
option is enabled
Addition or removal of buses, branches, machines or loads
Change of any bus attributes by which subsystems, monitored elements, and/or con-
tingencies are specified (e.g., area assignments, base voltages, etc.)
Change to any of the Linear Network Analysis Data Files
Activity DFAX is sensitive to the multi-section line reporting option (refer to Section 3.3.3 and activity
OPTN). Its setting at the time activity DFAX is selected is saved in the Distribution Factor Data File
and overrides the option setting in subsequent executions of activities OTDF, DCCC, TLTG, SPIL,
POLY, IMPC, LLRF, or ACCC.
Linear Network Analysis PSS
E 32.0
Building the Distribution Factor Data File Program Operation Manual
7-20 Siemens Energy, Inc., Power Technologies International
Activity DFAX is sensitive to the bus input option (refer to Section 3.3.3 and activity OPTN). Its
setting at the time activity DFAX is selected governs the manner in which buses must be identified
(i.e., either bus numbers or extended bus names) in the Linear Network Analysis Data Files that are
read for activity DFAX. The setting of the bus input option in subsequent executions of those activ-
ities that require a Distribution Factor Data File as input (i.e., activities OTDF, DCCC, TLTG, SPIL,
POLY, IMPC, LLRF, and AC Contingency Solution) must be identical to that which existed when
activity DFAX was executed.
In defining subsystems, a bus may be assigned to more than one subsystem. Suppose, for
example, that in activity TLTG a study system consisting of all buses in an area is required. Suppose
further that the user wishes to include as monitored elements only those branches in the area at
230 kV and above. This can be accommodated by defining one subsystem to be the entire area and
a second subsystem (using the join group block structure) to contain those buses in the area at or
above 230 kV.
A Distribution Factor Data File specified to one of the analysis functions that utilizes a linear (dc)
network model (e.g., activities such as DCCC, TLTG and LLRF) must specify at least one monitored
branch or one interface. That is, the Monitored Element Data File specified to activity DFAX to
construct such a Distribution Factor Data File must specify at least one monitored branch or one
interface. A Distribution Factor Data File that is to be used only for ac contingency calculations in
which only voltage violations are of interest need not specify any monitored branches or interfaces.
Care should be taken not to include unnecessary END statements in the Linear Network Analysis
Data Files. END statements are used to indicate the termination of block structures as well as the
termination of the data input stream. Improperly placed END statements are often interpreted by
activity DFAX as an end of input data signal. Symptoms of these conditions can occur during the
execution of activities that use such a Distribution Factor Data File; they include monitored elements
that are omitted from output reports and contingency cases that are skipped.
Additional Information
PSS
E GUI Users Guide, Section 13.1, Building the Distribution Factor Data File
PSS
E 32.0
Calculating Distribution Factors Program Operation Manual
7-22 Siemens Energy, Inc., Power Technologies International
The user must enter the name of a Distribution Factor Data File constructed by activity DFAX that
corresponds to the network condition contained in the working case (refer to Section 7.1.6) and to
the desired Linear Network Analysis Data Files (refer to Section 7.1.1). The Distribution Factor Data
File must specify at least one monitored branch or interface. The bus input option (refer to
Section 3.3.3 and activity OPTN) must have the same setting that was in effect when activity DFAX
filled the specified file. Refer to Section 2.4.1 for the file specification conventions used by activity
OTDF.
The Distribution Factor Data File is read, and the base case dc power flow solution is calculated
followed by the processing of the designated contingency cases. Only single event contingencies
are allowed in activity OTDF; changing the status of a three-winding transformer is considered a
multiple event contingency; disconnecting a bus is often a multiple event contingency. Any multiple
event contingencies generate an alarm and are ignored.
Activity OTDF may be terminated by entering the AB interrupt control code.
7.2.2 Output Report Format
Results of activity OTDF are reported in tabular form, with six contingency cases per table. Each
group of contingency cases contains a page summarizing the contingency cases performed. For
each contingency, the contingency label and the data record defining the contingency are listed,
along with the change in power of the affected element (MW shift). For line outage contingencies,
the quantity shown is the base case ac active power flow at the metered end of the line in the from
bus to to bus direction.
The summary page is followed by the distribution factor table. For each monitored element, this
table lists its active power loading in the base case ac network solution as contained in the working
case when activity OTDF was entered, its loading in the base case dc analogy network solution,
along with the distribution factor for each of the cases reported.
Single branches are listed first, either in the order in which they were specified in the Monitored
Element Data File or in ascending numerical or alphabetical order, according to the option selected
during the execution of activity DFAX (refer to Section 7.1.5). These are followed by the interfaces
in the order in which they were specified.
If a line outage contingency forms one or more islands with no Type 3 (swing) bus, such islands are
disconnected. Any monitored branch that is located in the swingless island has dashes printed in
place of its distribution factor. Similarly, any interface that includes such a member has its distribu-
tion factor printed as dashes.
A partial report is shown in Figure 7-1, which is curtailed to show only three of the first six contin-
gencies. Note that the reports shows the data files uses and lists each single contingency
considered prior to listing the distribution factors for each of the lines and interfaces monitored, for
each contingency. The files used are the savnw.con/mon/sub files from the PSS
E EXAMPLE
directory.
As an example, It can be seen the if the nuclear plant at bus 101 is tripped, the SHIFT will be 750
MW, (the units output), and the line from Bus 201 to 151 will show a power flow reduction of 310
MW (which is equal to 750 MW x 0.41339). The base case flow is shown as negative value of 564.8
MW at the Bus 201 end. This is the receiving end of the line. Consequently, the 750 MW shift
coupled with a positive distribution factor will result in a reduce flow towards Bus 201. An ac solution
shows the flow reduces to 255.9 MW. The calculation (-564.8 + 310) gives -254.8 MW (error less
than 0.43%).
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
7
-
2
3
P
S
S
E
3
2
.
0
L
i
n
e
a
r
N
e
t
w
o
r
k
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
C
a
l
c
u
l
a
t
i
n
g
D
i
s
t
r
i
b
u
t
i
o
n
F
a
c
t
o
r
s
Figure 7-1. Example Report Listing Distribution Factors
Linear Network Analysis PSS
E 32.0
Calculating Distribution Factors Program Operation Manual
7-24 Siemens Energy, Inc., Power Technologies International
7.2.3 Application Notes
Activity OTDF uses the same linearized network model as is used in the dc analogy network solu-
tion method of activity DCLF. Thus, in utilizing the distribution factors reported by activity OTDF, the
comments in Section 7.4.4 apply here as well. Note, in particular, the approximate nature of the
linearized network model used by activity OTDF.
Activity OTDF detects the specification of duplicate single line outage contingencies and prints the
distribution factor vector only for the first specification of such a contingency. Any contingency cases
involving bus boundary contingency events or line closure contingency events are not checked for
duplication.
It is recommended that the working case be solved to an acceptable mismatch tolerance prior to
launching activity OTDF. Otherwise, while the distribution factors would be valid, the base case line
flows printed would not.
Each column of distribution factors is a set of sensitivity coefficients describing the effect of the
corresponding contingency on the set of monitored elements. A distribution factor is defined as the
ratio of the change in flow on the monitored element in the pre-contingency and post-contingency
dc power flow solutions to the dc power change on the element involved in the contingency:
Distribution factors are usually used to estimate post-contingency line flows when only pre-contin-
gency (base case) conditions are known:
P
new
= P
base
+ (D.F. AP)
In using distribution factors, the flow directions of P
base
and AP used in the above equation must
be consistent with those assumed when the distribution factors were calculated.
For bus boundary condition contingencies, the distribution factors are expressed relative to a
change in power withdrawn at the bus. Thus, they are identical for increases in generation,
decreases in generation, increases in load and decreases in load. A load increase and a generation
decrease both have a positive AP, while a load decrease and a generation increase both have a
negative AP in deriving post-contingency monitored line flows with the above formula.
Line outage distribution factors are applied using the above equation with AP equal to the flow on
the outaged line before it is opened.
Figure 7-2 is an example that shows the outage of a line carrying 100 MW in the base case. If the
distribution factor for that specific outage is denoted as FIJ for the line from Bus I to Bus L and its
value is equal to 0.05, then the line from Bus I to Bus L will have an increased loading equal to the
100 MW lost from the outaged line multiplied by FIJ, that is 5 MW.
D.F. =
(MW in contingency case) - (MW in base case)
Power Shift
Siemens Energy, Inc., Power Technologies International 7-25
PSS
E GUI Users Guide, Section 13.2, Calculating and Reporting Distribution Factors
PSS
E 32.0
Estimating Severity Rankings for Single Line Outage Contingencies Program Operation Manual
7-26 Siemens Energy, Inc., Power Technologies International
7.3 Estimating Severity Rankings for Single Line Outage
Contingencies
Activity RANK
In large systems with many possible contingencies, especially single branch outages, it is often
useful to minimize the computational and subsequent analyses by identifying the most severe
contingencies prior to performing the contingency analysis.
The contingency ranking activity RANK estimates the severity of designated single branch outage
contingencies and builds a Contingency Description Data File (refer to Contingency Description
Data File Contents) with contingencies specified in decreasing order of their estimated severities.
Contingency rankings using two different performance criteria may be calculated by activity RANK.
Activity RANK may also be instructed to include contingencies that create swingless islands.
7.3.1 Contingency Ranking Methodology
The process of ranking contingencies in order of severity involves the following:
1. Establish the criteria to be considered in formulating the ranking (e.g., overloading, voltage
collapse, etc.).
2. For each criteria established in (1), define a scalar mathematical function that has a large
value for contingencies that stress the system relative to that criteria, and a small value for
those that do not; this function is called a performance index. The performance index should
be such that contingencies resulting in system conditions yielding large valued performance
indices are considered more severe than system conditions with smaller performance
indices.
3. Derive an efficient and accurate procedure for calculating these performance indices for a
large number of possible contingencies.
Activity RANK is able to calculate contingency rankings based on either or both of the following
criteria:
Run Activity RANK - GUI
Power Flow > Linear Network > Single contingency ranking (RANK)
[Single Line Contingency Ranking]
Run Line Mode Activity RANK - CLI
ACTIVITY?
>>RANK
SOLUTION PARAMETERS ARE:
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 7-27
PSS
E 32.0
Estimating Severity Rankings for Single Line Outage Contingencies Program Operation Manual
7-28 Siemens Energy, Inc., Power Technologies International
In the overload ranker, the performance index, PI, is defined as:
where:
Clearly, PI has a small value for system conditions with light branch loadings and a large value when
lines exceed their limits. An increase in PI following a contingency indicates that overall loading on
the branches contributing to PI has increased.
The set of monitored branches in the overload ranker is as defined in a Monitored Element Data
File (refer to Monitored Element Data File Contents). This is normally the same set of monitored
elements that are specified to activity DFAX and subsequently, via the Distribution Factor Data File,
to activities such as DCCC and ACCC.
In the voltage ranker, the performance index is defined as:
where:
PI gives an indication of reactive power losses under different system conditions. As line loadings
increase, their I
2
X losses also increase. This increase in reactive demand generally results in a
depression of system voltages.
The set of monitored branches in the voltage ranker is normally all branches in the working case.
The user may elect to omit those branches for which no rating is specified in a selected rating set.
Having established ranking criteria and defined performance indices to compare the severity of
many contingencies relative to these criteria, we require a procedure for calculating these indices
that is substantially less burdensome than explicitly solving each contingency case. Activity RANK
employs the ranking algorithm described in An Advanced Contingency Selection Algorithm by
T.A. Mikolinnas and B.F. Wollenberg, IEEE Transactions on Power Apparatus and Systems,
Vol. PAS-100, No. 2, February, 1981, pp. 608-617. This algorithm provides for the evaluation of the
performance indices described above without requiring post-contingency branch flows.
P
i
Is the active power flow on branch i.
PMAX
i
Is the rating of branch i.
L Is the set of monitored branches contributing to PI.
X
i
Is the reactance of branch i.
P
i
Is the active power flow on branch i.
L Is the set of monitored branches contributing to PI.
PI =
L
i = 1
P
i
PMAX
i
2
E
PI =
L
i = 1
X
i
P
i
2
E
Siemens Energy, Inc., Power Technologies International 7-29
PSS
E 32.0
Estimating Severity Rankings for Single Line Outage Contingencies Program Operation Manual
7-30 Siemens Energy, Inc., Power Technologies International
7.3.3 Operation of Activity RANK
Activity RANK verifies that at least one of the following parameters:
number of overload contingencies
number of voltage contingencies
contingencies that include swingless islands
is greater than zero, that generators are not converted (refer to CONG), that each non-Type 4 bus
is connected back to a Type 3 (swing) bus through the in-service ac network, and that the largest
initial active power mismatch is within the specified MW mismatch tolerance. If any violations are
detected, an appropriate message is printed and activity RANK is terminated.
If a new ordering of network buses is required, an appropriate message is printed and activity
ORDR is automatically executed.
Activity RANK calculates and prints the largest active power mismatch corresponding to the present
ac solution voltage vector in the working case.
Activity RANK constructs a contingency list that defines those single branch outages that are to be
considered. The user may process the entire working case or specify subsystem data (refer to
Section 4.8) by bus subsystem, area, zone, owner, or basekV. Unless all buses are specified,
activity RANK honors the user specification to either include or omit tie branches from the specified
subsystem in the contingency list.
If the determination of an overload ranking is enabled (i.e., if number of overload contingencies is
greater than zero), the branch ratings to be used are set up according to the specification of contin-
gency case rating, percent of rating, and convert ratings. The appropriate rating set is accessed. If the
convert ratings setting is enabled, these ratings are converted to estimated MW ratings based upon
each branch's reactive power loading at the metered end in the base case ac solution. Finally, the
ratings are modified to reflect the percent of rating specified.
The user may define subsystems of the working case with input data records taken from either the
designated Subsystem Description Data File or the dialog input device, as appropriate. Refer to
Lines, used in voltage
ranker PI
All
Defines the network branches that are to contribute to the
voltage ranker performance index:
Only branches with non-zero value in the rating set
designated by contingency case rating are used
All network branches
Include contingencies
creating swingless islands
Disabled
If enabled, the output of contingencies that result in the for-
mation of an island of one or more buses that contains no
Type 3 (swing) bus is enabled as follows: if the active
power flow on such a branch exceeds the MW threshold
tolerance specified in the base case dc power flow, the
contingency is included in the output of activity RANK.
Such contingencies are omitted from the overload and
voltage ranking calculations.
MW threshold to include
island contingencies
100
Table 7-1. Contingency Ranking Options (Cont.)
Specification Default Description
Siemens Energy, Inc., Power Technologies International 7-31
PSS
E is used to determine an
ordering of the network buses such that sparsity is maintained as the Jacobian matrix is triangular-
ized for ac network solutions or the system admittance matrix is decomposed into its triangular
factors in activities for linearized network analyses.
The user specifies either the filename where contingency specification records are to be stored or
output of the contingency records to the user's terminal.
Contingency rankings are calculated. If overload ranking is enabled, it is determined and the < n >
contingencies with the largest performance indices produce Contingency Description Data File
records. Similarly, if voltage depression ranking is enabled, it is determined and the < m > contin-
gencies with the largest performance indices produce Contingency Description Data File records.
Finally, if islanding contingency output is enabled, any contingency that results in the formation of
a swingless island and for which base case dc power flow loading exceeds the threshold specified
by MW threshold to include island contingencies, produces Contingency Description Data File records.
The working case is restored to its content at the time activity RANK was selected and activity
RANK is terminated.
Refer to Section 2.4.1 for the file specification conventions used by activity RANK.
7.3.4 Analyzing AC Contingency Ranking Results
The user supplies the name of an output file (type *.con) to which the contingency specification
records are to be deposited. If no filename is supplied, the results are written to the Progress tab.
If overload ranking is enabled, the < n > contingencies with the largest performance indices
produce Contingency Description Data File records. Similarly, if voltage depression ranking is
enabled, the < m > contingencies with the largest performance indices produce Contingency
Description Data File records. Finally, if islanding contingency output is enabled, any contingency
that results in the formation of a swingless island and for which base case dc power flow loading
exceeds the threshold specified produces Contingency Description Data File records.
Figure 7-3 shows a subset of the Contingency Description Data file produced by the ranking
process using the savnw.sav power flow case. It can be seen that each contingency included in the
ranked set is identified with either an overload or a voltage label and independently numbered.
7
-
3
2
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
L
i
n
e
a
r
N
e
t
w
o
r
k
A
n
a
l
y
s
i
s
P
S
S
E
3
2
.
0
E
s
t
i
m
a
t
i
n
g
S
e
v
e
r
i
t
y
R
a
n
k
i
n
g
s
f
o
r
S
i
n
g
l
e
L
i
n
e
O
u
t
a
g
e
C
o
n
t
i
n
g
e
n
c
i
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 7-3. Typical Contingency Description File from the Contingency Ranking Process
Siemens Energy, Inc., Power Technologies International 7-33
PSS
E 32.0
Estimating Severity Rankings for Single Line Outage Contingencies Program Operation Manual
7-34 Siemens Energy, Inc., Power Technologies International
In constructing the contingency list, parallel lines between the same pair of buses that have identical
impedances, loss estimates, and line shunt and phase shift active power injections (i.e., they are
identical in the linear network model used by activity RANK) are not all included in the contingency
list. Only one from among such a group of lines is needed. Activity RANK does not check for iden-
tical three-winding transformers connecting the same three buses.
If both overload and voltage depression rankings are being determined in the same execution of
activity RANK, the overload rankings are calculated first and any branch that is identified by the
overload ranker is removed from the contingency list prior to calculating the voltage rankings.
The Contingency Description Data File constructed by activity RANK is a standard source file that
may be edited by the user prior to its being submitted to activity DFAX. Bus identifiers are written
as bus numbers when the numbers input option is in effect, and as extended bus names when the
names input option is in effect (refer to Section 3.3.3 and activity OPTN). That is, when the Contin-
gency Description Data File built by activity RANK is submitted to activity DFAX along with the same
Subsystem Description and Monitored Element Data Files that were used by activity RANK, the files
are compatible with each other and with the requirements of activity DFAX (refer to Section 7.1.1).
Additional Information
PSS
E 32.0
Applying the DC Linearized Network Solution Program Operation Manual
7-36 Siemens Energy, Inc., Power Technologies International
(7.2)
shown in matrix form as
[P] = [B][u] for a system of n buses.
Note that this equation is linear and that the admittance matrix [B] is sparse because there are only
several transmission lines connected to each bus. The solution of this system of equations can be
accomplished efficiently by the numerical technique of triangular factorization. The power injec-
tions, [P], are known, and the phase angles, [u], are computed. After the phase-angle solution has
been determined, the real power flows can be computed using Equation 7.1.
7.4.2 Operation of Activity DCLF
The linearized network solution activity DCLF applies the dc analogy network solution algorithm to
the network modeled in the working case. Optionally, the solution method may also be applied to
that network with the status of a specified ac branch changed. The base case and change case
solutions are tabulated in a single report.
Activity DCLF checks that each non-Type 4 bus is connected back to a Type 3 (swing) bus through
the in-service ac network. If any violations are detected, an appropriate message is printed and
activity DCLF is terminated.
If a new ordering of network buses is required, an appropriate message is printed and activity
ORDR is automatically executed.
The largest active power mismatch corresponding to the present ac solution voltage vector in the
working case is calculated and printed. The user may specify that activity DCLF terminates if the
largest mismatch is greater than 0.5 MW.
The user specifies which of the three ratings are to be used in tabulating line loading percentages
in the output report. The default is the rating set established as the default rating set program option
(refer to Section 3.3.3 and activity OPTN).
For a change case solution calculation, the user must designate either of the following options:
a branch where status is to be changed for the change case solution
a 3-winding transformer where status is to be changed for the change case solution
Data requirements for a non-transformer branch or a two-winding transformer both buses and the
circuit ID. A three-winding transformer is designated by specifying the three buses it connects.
If a branch outage separates the system such that an island with no Type 3 (swing) bus remains,
an appropriate message is printed.
When the multi-section line reporting option is enabled (refer to Section 3.3.3 and activity OPTN),
and either an in-service multi-section line grouping or an in-service member of such a grouping is
specified, the entire grouping is switched (refer to Multi-Section Line Grouping Data and
Section 5.8.1). If the specified multi-section line grouping or member is initially out-of-service,
activity DCLF does not allow it to be switched. In outaging a multi-section line grouping, the type
codes of the interior dummy buses are automatically changed as required by activity DCLF.
P
i
=
u
i
- u
j
X
ij
n
j = 1
E
n
j = 1
E
P
ij
=
Siemens Energy, Inc., Power Technologies International 7-37
PSS
E 32.0
Applying the DC Linearized Network Solution Program Operation Manual
7-38 Siemens Energy, Inc., Power Technologies International
7.4.3 Output Report Format
The general form of the output report of activity DCLF is similar to that of activity LOUT. Figure 7-4
shows an example of the output of activity DCLF.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
7
-
3
9
P
S
S
E
3
2
.
0
L
i
n
e
a
r
N
e
t
w
o
r
k
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
A
p
p
l
y
i
n
g
t
h
e
D
C
L
i
n
e
a
r
i
z
e
d
N
e
t
w
o
r
k
S
o
l
u
t
i
o
n
Figure 7-5. Sample Output Listing for activity DCLF Including Change Case
Linear Network Analysis PSS
E 32.0
Applying the DC Linearized Network Solution Program Operation Manual
7-40 Siemens Energy, Inc., Power Technologies International
The bus information presented includes the number of the area in which the bus is located, the bus
voltage phase angles for the base case and change case dc power flow solutions, generator MW,
and load MW. The value printed as load includes the active power components of all in-service fixed
bus shunts and all in-service loads connected to the bus on the basis of the voltage magnitude at
the bus at the time activity DCLF is initiated.
The star point buses of three-winding transformers (refer to Transformer Data) are not reported by
activity DCLF.
Output for FACTS devices and dc lines appears on the right side of the bus output block as the first
line or lines of branch data (i.e., before output for ac branches). If the dc line or FACTS device power
arrays are zero (e.g., if the case had just been read with activity READ and no ac power flow solu-
tion attempted), an estimate of the dc line and FACTS device powers is used based upon the
scheduled power or current. Otherwise, regardless of the quality of the ac solution upon entry to
activity DCLF, the powers contained in the working case are used.
For non-transformer branches and for two-winding transformers listed, the number, name, base
voltage, and area of the to bus is printed, along with the circuit identifier; for three-winding trans-
formers, the output line contains the string 3WNDTR in the bus number column, the transformer
name in the bus name column, and the winding number in the base voltage column, followed by the
transformer circuit identifier; if the three-winding transformer to bus reporting option is enabled, two
additional lines, containing the bus numbers, names, and base voltages of the two buses connected
to the from bus by the three-winding transformer, are printed, followed by the number of the area in
which the to bus is located. The active power flowing into the line at the from bus and the corre-
sponding percentage of the selected rating are printed for both the base and change case dc
solutions. The selected line rating and the difference in line flow between the base case and change
case solutions are also tabulated.
If the current execution of activity DCLF included only a base case dc solution, the change case
columns of the report are blank. If a change case solution was calculated, a description of the
change case is included in the banner at the top of each page of output. In addition, in the bus output
block for the from and to buses of the branch where status was changed, the branch output line for
this branch is preceded by the character string --->.
If the change case is a line outage that results in the creation of an island without a swing bus,
change case phase angles and line flows from within the swingless island are not tabulated; dashes
are printed in the output report where these values would normally be shown.
When the multi-section line reporting option is enabled (refer to Section 3.3.3 and activity OPTN),
the interior dummy buses of multi-section line groupings (refer to Multi-Section Line Grouping Data)
are not reported. In reporting branches, the far end to bus (rather than the closest dummy bus) of
each multi-section line connected to the from bus is shown as its to bus. Multi-section lines are iden-
tified with an ampersand ( & ) as the first character of their line identifiers in the branch circuit
identifier column (e.g., &1).
Siemens Energy, Inc., Power Technologies International 7-41
PSS
E 32.0
Applying the DC Linearized Network Solution Program Operation Manual
7-42 Siemens Energy, Inc., Power Technologies International
From the foregoing discussion, then, it is strongly recommended that, when using activity DCLF to
check branch outage cases, the working case be solved to an acceptable mismatch tolerance with
a full ac solution prior to initiating activity DCLF. While it does not require a solved system condition,
the only time an unsolved starting point should be provided is in using activity DCLF as a bootstrap
to obtain an estimate of phase angles for a full ac power flow solution.
Additional Information
PSS
E GUI Users Guide, Section 13.5, Running the DC Linearized Network Solution
PSS
E 32.0
Calculating Linearized Network Contingency Program Operation Manual
7-44 Siemens Energy, Inc., Power Technologies International
7.5.1 Operation of Activity DCCC
Activity DCCC verifies that generators are not converted (refer to CONG) and that each non Type 4
bus is connected back to a Type 3 (swing) bus through the in-service ac network. If any violations
are detected, an appropriate message is printed.
If a new ordering of network buses is required, an appropriate message is printed and activity
ORDR is automatically executed.
Activity DCCC calculates and prints the largest active power mismatch corresponding to the present
ac solution voltage vector in the working case.
The Distribution Factor Data File is read, and, if the convert ratings option was enabled at the start
of activity DCCC, ratings from the selected rating set of those monitored branches having a non-
zero rating are modified. For each such branch, the reactive power loading is calculated and a MW
rating is determined under the assumption that the reactive power loading is unchanged under
contingency conditions.
Finally, the base case dc power flow solution is calculated followed by the processing of the desig-
nated contingency cases. If a line outage contingency forms an island with no Type 3 (swing) bus,
a singular submatrix is formed. Such islands are omitted from the network solution of activity DCCC.
Activity DCCC may be terminated by entering the AB interrupt control code.
Two different output reports may be produced by activity DCCC: an overload report and a loading
table.
7.5.2 Overload Report
In the overload report, each network condition (i.e., the base case and each contingency case) is
reported immediately after its calculation. A branch or interface is reported if the following conditions
are satisfied:
Minimum flow change in
overload report
1.0
Overloaded branches in contingency cases for which contin-
gency case flows differ from their base case flows by less than the
minimum contingency case flow change parameter are omitted
from the summary overload report.
Exclude cases with no
overloads from overload
report
disabled
If enabled, those cases for which no overloads are detected are
omitted from the summary overload report.
Distribution Factor Data
File
The user must enter the name of a Distribution Factor Data File
constructed by activity DFAX that corresponds to the network condition
contained in the working case (refer to Section 7.1.6) and to the
desired Linear Network Analysis Data Files (refer to Section 7.1.1).
The Distribution Factor Data File must specify at least one monitored
branch or interface. The bus input option (refer to Section 3.3.3 and
activity OPTN) must have the same setting that was in effect when
activity DFAX filled the specified file. Refer to Section 2.4.1 for the file
specification conventions used by activity DCCC.
Table 7-2. Linearized Network Contingency Options (Cont.)
Specification Default Description
Siemens Energy, Inc., Power Technologies International 7-45
PSS
E
3
2
.
0
C
a
l
c
u
l
a
t
i
n
g
L
i
n
e
a
r
i
z
e
d
N
e
t
w
o
r
k
C
o
n
t
i
n
g
e
n
c
y
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 7-6. Summary Contingency Report from the DC Contingency Checking Process
Siemens Energy, Inc., Power Technologies International 7-47
PSS
E
3
2
.
0
C
a
l
c
u
l
a
t
i
n
g
L
i
n
e
a
r
i
z
e
d
N
e
t
w
o
r
k
C
o
n
t
i
n
g
e
n
c
y
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 7-7. Loading Report from the DC Contingency Checking Process
Siemens Energy, Inc., Power Technologies International 7-49
PSS
E 32.0
Calculating Linearized Network Contingency Program Operation Manual
7-50 Siemens Energy, Inc., Power Technologies International
7.5.5 Application Notes
Activity DCCC uses the same linearized network model as is used in the dc analogy network solu-
tion method of activity DCLF. Thus, the comments in Section 7.4.4 apply here as well. Note, in
particular, the approximate nature of the linearized network model used by activity DCCC. The
proper role of activity DCCC, therefore, should be to focus attention on those system conditions that
deserve more detailed study.
Activity DCCC detects the specification of duplicate single and double line outage contingencies
and calculates the contingency case solution only for the first specification of such a contingency.
Any contingency cases involving bus boundary contingency events, line closure contingency
events, or more than two line outage contingency events are not checked for duplication.
If the convert ratings code is set to one at the start of activity DCCC, any percentage of rating param-
eter is applied after the conversion to estimated MW ratings. Interface ratings are not affected by
the convert ratings solution parameter.
Line loss estimates and line shunts of outaged lines are handled as in activity DCLF (refer to
Section 7.4.4).
It is required that the working case be solved to an acceptable mismatch tolerance prior to entering
activity DCCC.
Additional Information
PSS
E 32.0
Performing DC Corrective Action Analysis Program Operation Manual
7-52 Siemens Energy, Inc., Power Technologies International
7.6.3 DC Corrective Action Results
After a dc corrective actions solution is performed successfully, the program lists monitored
branches that are overloaded, before and, if any, after the corrective actions solution. In the second
part of the report, initial and new values of the controls, as well as changes in controls are reported
also. Figure 7-8 is the sample result of dc corrective actions applied to an example system. Two
branches and an interface flow overloads in the working case are removed by corrective actions,
which involve the adjustments of the phase shifter between buses 203 and 202, and generation at
two generator buses.
Branch overload violation
tolerance
0.10%
Specify branch loading limit tolerance for adjustment of load limits
to be used in linear programming engine. For example, if the toler-
ance is 0.1% and the selected flow rating is 100% of Rate A, the
linear programming algorithm will consider the solution feasible if
the loading of a branch has been reduced within 100.1% of the
rating.
Control options
Select types of control adjustments and specify weighting factors
for each type (see Section 6.11.3).
Input Data File
The Distribution Factor Data File is used to define branch and interface flow
constraints and control subsystems. When creating a Distribution Factor Data
File for dc corrective action, a Contingency Description Data File that specifies
no contingencies is allowed.
Table 7-3. DC Corrective Actions Options (Cont.)
Specification Default Description
Siemens Energy, Inc., Power Technologies International 7-53
PSS
E 32.0
Performing DC Corrective Action Analysis Program Operation Manual
7-54 Siemens Energy, Inc., Power Technologies International
7.6.4 Application Notes
The corrective actions solution algorithm does not place a limit on the number of controls and
constraints that can be modeled. The computation time of a corrective actions solution is approxi-
mately proportional to the number of constraints. Because local controls are generally more
effective in removing violations, it may be preferable to choose the subsystem in which control
actions are allowed to be the same as that in which elements are monitored.
Operating limit violations caused by incorrect limit settings may have a significant impact on the
optimal solution found. Hence, suspicious limits should be verified and corrected, if necessary, or
even removed from the solution.
Two methods can be used to excluded controls from the corrective actions solution. One way is to
set the upper and lower limits of a control equal; another is to carefully define the control subsystem
to exclude those controls that are not desired in a particular application.
Additional Information
PSS
E 32.0
Calculating Transmission Interchange Limits Program Operation Manual
7-56 Siemens Energy, Inc., Power Technologies International
Figure 7-9. Linear Projection Technique Used in Transfer Limit Analysis
7.7.2 Calculating Transmission Transfer Limits
The transmission interchange limit analysis activity TLTG estimates the import or export limits of a
specified subsystem of the working case using a linearized network model. The user designates
this study system in which the total power injection is to be increased (for export limits) or decreased
(for import limits). An opposite change in the total power injection is made in a designated opposing
system. The calculation uses the sensitivity type analysis described in Section 7.7.1.
Power transfer distribution factors relating changes in branch and interface flows to a change in
study system interchange are determined. The maximum study system export or import is then
derived by extrapolation subject to the constraint that no monitored elements exceed a specified
percentage of a selected rating.
This process may then be repeated for a designated set of user specified contingency cases.
The process will perform all the contingencies identified in the contingency description file
processed when building the distribution factor file. Furthermore, the process uses the monitored
list file, which allows the lines to be monitored and interfaced. This feature is important because
these interfaces often define stability limits.
Note that any two subsystems identified in the *.sub file can be used for the transfer analysis.
Furthermore, however, it should be noted that the limits will be found based on only those elements
(lines and interfaces) that are monitored, i.e., included in the *.mon file.
In Figure 7-10 It can be seen that Areas A and C form the study and opposing system, respectively.
Transfers take place directly and via Area B. It is important therefore to monitor lines within Area B
or interfaces between Area B and the other two areas to ensure that the correct limits are identified.
Siemens Energy, Inc., Power Technologies International 7-57
PSS
E 32.0
Calculating Transmission Interchange Limits Program Operation Manual
7-58 Siemens Energy, Inc., Power Technologies International
Base case constraints in
contingency case
Ignore
If set to Include, both base case and contingency case flow
constraints are recognized in calculating the pre-contingency
interchange limits for each contingency case.
If set to Ignore, only the contingency case loadings are consid-
ered (refer to Section 7.7.8).
Add study system ties to
monitored lines
disabled
If enabled, automatically include study system tie lines as
monitored elements.
Minimum contingency case
pre-shift flow change
1.0
Provide the means to ignore those monitored elements
that, in a contingency case, are not significantly affected by
the contingency. If the magnitude change in pre-shift flow
from the base case value is less than the minimum flow
change threshold and the magnitude change in the power
transfer distribution factor from the base case value is less
than the distribution factor change threshold, the monitored
element is ignored.
Minimum contingency case
distribution factor change
0.0000
Study system generation
shift
100
If the value entered is positive, export limits are to be determined;
otherwise, import limits are to be calculated.
The generation shift is apportioned among generator and load
buses in the study system in proportion to the participation factors
specified in the participation block structure of the Subsystem
Description Data File (refer to Section 7.1.2). If no participation
block was entered for the study system, the generation shift is
shared among generator buses in proportion to their plant
MBASEs (i.e., the sum of the MBASEs of in-service machines
with positive active power output at the bus). In this case, there
must be at least one in-service machine with a positive MBASE in
the subsystem. The opposite generation shift is applied to buses
in the first opposing system, again according to their participation
factors or MBASEs.
Using the incremental form of the dc power flow equation (refer to
activity DCLF) and the power shift vector, phase angle changes
are calculated, followed by incremental line flows for all monitored
lines and interfaces. These are transformed into a vector of base
case power transfer distribution factors, and the interchange limit
is determined by extrapolation such that all monitored elements
satisfy their rating constraints.
Subsystem selection
Study System: network subsystem in which the total power injec-
tion is to be increased (for export limits) or decreased (for import
limits). The choices available are those listed in the *.sub type file.
Opposing System: network subsystem in which an opposite
change from that in the Study System is made.
Maximum import / export 99999
Threshold value, number of monitored elements in the
summary report.
Minimum distribution factor
magnitude
0.0
Threshold value for summary report. For small distribution
factors with levels below this threshold there will be no
reporting for the related element.
Table 7-4. Transmission Transfer Limit Analysis Options (Cont.)
Specification Default Description
Siemens Energy, Inc., Power Technologies International 7-59
PSS
E 32.0
Calculating Transmission Interchange Limits Program Operation Manual
7-60 Siemens Energy, Inc., Power Technologies International
the desired Linear Network Analysis Data Files (refer to Section 7.1.1). The Distribution Factor Data
File must specify at least one monitored branch or interface. The bus input option (refer to
Section 3.3.3 and activity OPTN) must have the same setting that was in effect when activity DFAX
filled the specified file. Refer to Section 2.4.1 for the file specification conventions used by activity
TLTG.
The user must specify the study and opposing systems. If no subsystems are defined, an appro-
priate error message is printed and activity TLTG is terminated. If only one subsystem was
specified, the specified subsystem is taken as the study system while the remainder of the working
case is treated as the opposing system. If two subsystems were specified, the default opposing
system is bypassed.
Activity TLTG ensures that there are no buses that are members of both of the selected
subsystems. If any such buses are found, they generate an alarm and activity TLTG is terminated.
The largest active power mismatch corresponding to the present ac solution voltage vector in the
working case is calculated and printed.
If the convert ratings option was enabled at the start of activity TLTG, ratings from the selected rating
set(s) of those monitored branches having non-zero rating(s) are modified. For each such branch,
the reactive power loading is calculated and MW rating(s) are determined under the assumption
that the reactive power loading is unchanged under power transfer and contingency conditions.
Using the incremental form of the dc power flow equation (see Section 7.4.1) and the power shift
vector, phase angle changes are calculated, followed by incremental line flows for all monitored
lines and interfaces. These are transformed into a vector of base case power transfer distribution
factors, and the interchange limit is determined by extrapolation such that all monitored elements
satisfy their rating constraints.
The base case dc network solution is calculated and the solution summarized as in the following
example:
STUDY SYSTEM GENERATION IS 1500.0 MW
OPPOSING SYSTEM GENERATION IS 1748.9 MW
STUDY SYSTEM NET INTERCHANGE IS 282.8 MW
The user may specify a study system generation shift (default = 100). If the value entered is positive,
export limits are to be determined; otherwise, import limits are to be calculated.
The generation shift is apportioned among generator and load buses in the study system in propor-
tion to the participation factors specified in the participation block structure of the Subsystem
Description Data File (refer to Section 7.1.2). If no participation block was entered for the study
system, the generation shift is shared among generator buses in proportion to their plant MBASEs
(i.e., the sum of the MBASEs of in-service machines with positive active power output at the bus).
In this case, there must be at least one in-service machine with a positive MBASE in the subsystem.
The opposite generation shift is applied to buses in the opposing system, again according to their
participation factors or MBASEs. Using the incremental form of the dc power flow equation (refer to
Sections 7.4.4 and 7.5.4) and the power shift vector, phase angle changes are calculated, followed
by incremental line flows for all monitored lines and interfaces. These are transformed into a vector
of base case power transfer distribution factors, and the interchange limit is determined by extrap-
olation such that all monitored elements satisfy their rating constraints.
Siemens Energy, Inc., Power Technologies International 7-61
PSS
E 32.0
Calculating Transmission Interchange Limits Program Operation Manual
7-62 Siemens Energy, Inc., Power Technologies International
ation shift. Loadings on monitored elements are then reported, sorted such that the most restrictive
elements are listed first. Either incremental or total pre-contingency transfer limits, as appropriate,
are listed.
For monitored three-winding transformer windings, flow estimates are calculated at the winding bus
end as power flowing into the transformer. For other monitored branches, flow estimates are calcu-
lated at the metered end in the from bus to to bus direction. The flow across an interface is taken
as the sum of the flows of its members. For three-winding transformer windings, the flow is calcu-
lated at the winding bus as power flowing into the transformer. For other members, the flow is
calculated at its metered end in the from bus (i.e., the first bus specified in entering the branch; refer
to Monitored Element Data File Contents) to to bus direction.
Flow estimates are listed for each of three interchange schedules: with the original generation
profile, with the specified generation shift, and at the generation shift corresponding to the transfer
level limit required for the most restrictive monitored element (i.e., the one listed first). Any flow at
or above the selected percentage of the appropriate rating is followed by an asterisk ( - ). The
power transfer distribution factor relating the change in flow on the monitored element to a change
in study system net interchange is also tabulated, along with the rating of the monitored element;
for branches, this is not the percentage of the rating used in determining the interchange limit, but
either the value of rating as entered in activities such as READ, Reading Power Flow Data Additions
from the Terminal, RDCH, CHNG or the [Spreadsheet], or, if the convert ratings option was selected
at the start of activity TLTG, the estimated MW ratings.
When reporting flows for contingency cases, the events comprising the contingency are listed
followed by flows on the monitored elements sorted as described above. The flow table includes
both the contingency case flows in the same form as the base case report described above, as well
as the base case flows at the transfer level required for the most restrictive monitored element. Note
that if the ignore base case constraints in contingency cases option was specified, only the contin-
gency case constraints are considered in calculating the transfer limit; in this case, base case flows
at the transfer limit may be shown as overloaded because the corresponding constraints are
ignored in the transfer limit calculation.
A summary report tabulates the number of system condition solutions attempted and the number
for which there exists no interchange schedule at which the rating constraint can be satisfied for all
monitored elements (refer to Section 7.7.8). This is followed by a tabulation of monitored elements
for all system conditions that were calculated, in order of increasing incremental or total transfer
capability, as appropriate. The limiting element is listed along with its power transfer distribution
factor, its pre-shift contingency case flow, its rating, and a description of the system condition.
Only those monitored elements satisfying the cutoff threshold solution parameters set at the start
of activity TLTG are included in the summary. After an element has been listed the maximum
number of times < n >, its nth occurrence includes an asterisk ( - ) before its description, and further
reporting of the element is suppressed.
This summary report is reprinted for each selected interface with interface transfer limits and distri-
bution factors rather than study system interchange limits and distribution factors tabulated. All
distribution factors on the interface transfer limits summary report describe changes in monitored
element flow relative to a change in interface flow. The branches that form the interface are listed
on the first page of an interfaces transfer limit summary report.
The final page of the summary report lists those elements that were reported < n > times, sorted by
the number of times they would have been reported.
Siemens Energy, Inc., Power Technologies International 7-63
PSS
E
3
2
.
0
C
a
l
c
u
l
a
t
i
n
g
T
r
a
n
s
m
i
s
s
i
o
n
I
n
t
e
r
c
h
a
n
g
e
L
i
m
i
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 7-12. Base Case Results for Two Area Transfer Limit Calculation
Siemens Energy, Inc., Power Technologies International 7-65
PSS
E 32.0
Calculating Transmission Interchange Limits Program Operation Manual
7-66 Siemens Energy, Inc., Power Technologies International
Only those monitored elements satisfying the cutoff threshold solution parameters set by the user
are included in the summary. After an element has been listed the maximum number of times < n >,
its nth occurrence includes an asterisk ( - ) before its description, and further reporting of the
element is suppressed.
This summary report is reprinted for each selected interface with interface transfer limits and distri-
bution factors rather than study system interchange limits and distribution factors tabulated. All
distribution factors on the interface transfer limits summary report describe changes in monitored
element flow relative to a change in interface flow. The branches that form the interface are listed
on the first page of an interfaces transfer limit summary report.
The final page of the summary report lists those elements that were reported < n > times, sorted by
the number of times they would have been reported.
If a line outage contingency forms an island with no Type 3 (swing) bus, a singular submatrix is
formed. Any monitored branch that is located in the swingless island, as well as any interface that
includes such a branch as a member, has dashes printed where its contingency case results would
normally be printed.
How is the negative transfer limit obtained?
In Figure 7-13 it can be seen that the most severe contingency identifies a negative transfer limit of
-56.5 MW. The contingency is loss of the two units at Buses 101 and 102. In the pre-shift condition,
in which there is a transfer of 278 MW, the branch from Bus 3008 to Bus 154 has a loading of 465
MW but has a thermal capacity of only 440 MW. This loading has to be reduced by 25.4 MW to keep
the branch within its capacity.
The distribution factor is 0.07566. Consequently the transfer has to be reduced by 335 MW (that is
25.4 MW divided by 0.07566) from its current level of 278.7 MW. This, rounding off, is 57 MW less
than the base case (pre-shift) transfer.
7.7.8 Application Notes
Activity TLTG uses the same linearized network model as is used in activity DCLF. Thus, the
comments in Section 7.4.4 apply here as well. Note, in particular, the approximate nature of the
linearized network model used by activity TLTG. The proper role of activity TLTG, therefore, should
be to focus attention on those system conditions that deserve more detailed study.
Activity TLTG detects the specification of duplicate single and double line outage contingencies and
calculates the contingency case solution only for the first specification of such a contingency. Any
contingency cases involving bus boundary contingency events, line closure contingency events, or
more than two line outage contingency events are not checked for duplication.
The values shown as monitored element flows are set as described in Section 7.5.4. The user
selects the base flow value to be used by setting the line flow code solution parameter at the start
of activity TLTG (see above).
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
7
-
6
7
P
S
S
E
3
2
.
0
L
i
n
e
a
r
N
e
t
w
o
r
k
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
C
a
l
c
u
l
a
t
i
n
g
T
r
a
n
s
m
i
s
s
i
o
n
I
n
t
e
r
c
h
a
n
g
e
L
i
m
i
t
s
Figure 7-13. Partial Listing of Report for Two Area Transfer Limits for Contingency Cases
Typical output for Contingency case. Most restrictive transfer limit is negative due to overload prior to shift during contingency.
Partial Summary Listing showing Contingency Testing results in order of Increasing Transfer Capability
Linear Network Analysis PSS
E 32.0
Calculating Transmission Interchange Limits Program Operation Manual
7-68 Siemens Energy, Inc., Power Technologies International
In the contingency case monitored flow tables, transfer limits may be calculated using either of the
following approaches:
1. Both pre-contingency and post-contingency flows must satisfy their appropriate rating
constraints (i.e., both the base case and the contingency case must have no overloads).
2. Only post-contingency constraints need be satisfied.
The user selects the method to be used by setting include/ignore base case constraints in contingency
case at the start of activity TLTG. The setting of this parameter has no effect on the summary report
of activity TLTG; for contingency cases, the transfer capability shown is always the one at which the
monitored element is at its limit in the contingency case. Thus, the setting of this parameter is mean-
ingful only if the full output option is specified.
When the user has specified apply summary minimum distribution factor to report and minimum distribu-
tion factor magnitude is greater than zero, monitored elements with distribution factor magnitudes
below the threshold are ignored in calculating the corresponding monitored element flow table as
well as being omitted from the summary report.
If the convert ratings code is set to one at the start of activity TLTG, any percentage of rating param-
eter is applied after the conversion to estimated MW ratings. Interface ratings are not affected by
the convert ratings solution parameter.
Line loss estimates and line shunts of outaged lines are handled as in activity DCLF (refer to
Section 7.4.4).
It is required that the working case be solved to an acceptable mismatch tolerance prior to entering
activity TLTG.
It is entirely possible that, for a given system condition, there is no interchange schedule at which
the linearized network model results in all monitored elements satisfying their rating constraints.
This could occur, for example, if the pre-shift solution had two overloaded branches, and one
required an increase in interchange to relieve its overload while the other required a decrease in
interchange.
Minimmum pre-shift flow change and minimum distribution factor change values may be used to
exclude from consideration those monitored elements in a contingency case that are not greatly
affected by the contingency. This could result in a situation in which none of the remaining moni-
tored elements have non-zero ratings. Such insoluble conditions are described in the output block
for that condition when full output is selected; when the summary report is chosen, such cases are
identified.
When specifying a rating percentage of other than 100%, note that interface ratings are also scaled
by the specified percentage in checking their flows to determine maximum interchange.
Additional Information
PSS
E 32.0
Calculating Sequential Participation Interchange Limits Program Operation Manual
7-70 Siemens Energy, Inc., Power Technologies International
7.8.1 Subsystem Participation Data File Contents
The Subsystem Participation Data File is used to define participation blocks for one or more of the
subsystems that are defined in the Distribution Factor Data File constructed by activity DFAX and
specified to activity SPIL. The subsystems were in turn defined in the Subsystem Description Data
File (refer to Section 7.1.2) that was read by activity DFAX in the process of constructing the Distri-
bution Factor Data File. The participation data defined in the Subsystem Participation Data File
provides for:
Up to five participation blocks per subsystem.
For each participation block, the fraction of the maximum permissible power shift (spec-
ified in activity SPIL; refer to Section 7.8.3) to be assigned to the block.
For each participation block, the list of buses that are to be included in the block and
their block participation factors.
The Subsystem Participation Data File consists of one or more sets of subsystem data with a line
containing a zero or blanks following the last set of subsystem data. The file format will appear as
shown here:
set of data for a subsystem
set of data for another subsystem
.
.
.
set of data for another subsystem
0 End of participation data
Each set of data for a subsystem contains the subsystem label enclosed in single quotes (refer to
Section 7.1.2), followed by data for up to five participation blocks, followed by line containing a zero:
'label'
data for participation block 1
.
.
.
data for participation block n
0 End of participation data for subsystem 'label'
Siemens Energy, Inc., Power Technologies International 7-71
PSS
E 32.0
Calculating Sequential Participation Interchange Limits Program Operation Manual
7-72 Siemens Energy, Inc., Power Technologies International
7.8.2 Interchange Limits Options
Table 7-5. Sequential Participation Interchange Limits Options
Specification Default Description
MW mismatch tolerance 0.5
Largest initial active power mismatch. Note that the user can
modify the tolerance in steps of 0.1.
Abort if MW mismatch
exceeds tolerance
enabled
Enable or disable termination of activity SPIL if mismatch toler-
ance exceeded.
Base case rating
activity
OPTN
The base case and contingency case rating sets, and the
percentage thereof, define the line loading limits used in deter-
mining overloads.
The user specifies the rating; the default rating set is established
by the program option setting (refer to Section 3.3.3 and activity
OPTN).
Contingency case rating
Percent of rating 100
Convert ratings to esti-
mated MW ratings
disabled
If enabled, ratings of monitored branches are converted to esti-
mated MW ratings based upon each monitored lines reactive
power loading at the metered end in the base case ac solution.
Line flow code
dc base
case
The line flow code defines the base flow to be used in deriving
branch flow estimates.
dc base case
ac base case
Phase shifter in base case Lock
If set to Regulate (in base case), any regulating phase shifter
where adjustment control mode CODn (refer to Transformer Data)
is set to +3 holds its base case flow in all base case shift solu-
tions. If set to Lock, all phase shift angles are locked at their base
case settings.
Add study system ties to
monitored lines
disabled
If enabled, automatically include study system tie lines as
monitored elements.
Minimum contingency case
pre-shift flow change
1.0
Provide the means to ignore those monitored elements
that, in a contingency case, are not significantly affected by
the contingency. If the magnitude change in pre-shift flow
from the base case value is less than the minimum flow
change threshold and the magnitude change in the power
transfer distribution factor from the base case value is less
than the distribution factor change threshold, the monitored
element is ignored.
Minimum contingency case
distribution factor change
0.0000
Siemens Energy, Inc., Power Technologies International 7-73
PSS
E 32.0
Calculating Sequential Participation Interchange Limits Program Operation Manual
7-74 Siemens Energy, Inc., Power Technologies International
7.8.3 Operation of Activity SPIL
Activity SPIL checks that generators are not converted (refer to CONG) and that each non-Type 4
bus is connected back to a Type 3 (swing) bus through the in-service ac network. If any violations
are detected, an appropriate message is printed and activity SPIL is terminated.
If a new ordering of network buses is required, an appropriate message is printed and activity
ORDR is automatically executed.
The user must enter the name of a Distribution Factor Data File constructed by activity DFAX that
corresponds to the network condition contained in the working case (refer to Section 7.1.6) and to
the desired Linear Network Analysis Data Files (refer to Section 7.1.1). The Distribution Factor Data
File must specify at least one monitored branch or interface. The bus input option (refer to
Section 3.3.3 and activity OPTN) must have the same setting that was in effect when activity DFAX
filled the specified file. Refer to Section 2.4.1 for the file specification conventions used by activity
SPIL.
The user must specify the study and opposing systems. If no subsystems are defined, an appro-
priate error message is printed and activity SPIL is terminated. If only one subsystem was specified,
the specified subsystem is taken as the study system while the remainder of the working case is
treated as the opposing system. If two subsystems were specified, the default opposing system is
bypassed.
Activity SPIL checks to ensure that there are no buses that are members of both of the selected
subsystems. If any such buses are found, they generate an alarm and activity SPIL is terminated.
The user may enter the name of a Subsystem Participation Data File that contains subsystem
sequential participation data as described in Section 7.8.1. Refer to Section 2.4.1 for the file spec-
ification conventions used by activity SPIL.
Data specified in this file must be consistent with the subsystem definitions contained in the Distri-
bution Factor Data File accessed above. For each of the study and opposing systems, if the
designated file contains valid sequential participation data, its data is used rather than the partici-
Interchange limit output
Incre-
mental
Incremental: incremental transfer capability
Total: total transfer capability
Elements in flow tables 60000
Limit the flow table for each case reported to the < n > most
restrictive monitored elements.
Apply summary minimum
distribution factor to report
disabled
If enabled, apply the minimum distribution factor magnitude
threshold for including monitored elements in the summary
report to the monitored element flow table of each case
reported when full output is selected.
Optional Interface Output NONE
Summary report is repeated with interface transfer limits
and distribution factors for a selected interface listed rather
than study system transfer limits and distribution factors.
The interface distribution factors listed on the interface
summary report are measures of the changes in monitored
element flows to a change in base case interface flow.
Table 7-5. Sequential Participation Interchange Limits Options (Cont.)
Specification Default Description
Siemens Energy, Inc., Power Technologies International 7-75
PSS
E 32.0
Calculating Sequential Participation Interchange Limits Program Operation Manual
7-76 Siemens Energy, Inc., Power Technologies International
gency Case Flow Calculations. Prior to terminating, an ordered summary report from among all the
cases calculated is tabulated (refer to Section 7.8.5).
The user may specify having the summary report repeated with interface transfer limits and distri-
bution factors for a selected interface listed rather than study system transfer limits and distribution
factors. The interface distribution factors listed on the interface summary report are measures of the
changes in monitored element flows to a change in base case interface flow.
In listing study system buses, opposing system buses, and study system tie lines, the tabulation
may be terminated by entering the AB interrupt control code. In this case, the interrupt is cleared
and processing continues. After the interchange limit calculations have started, activity SPIL may
be terminated by entering the AB interrupt control code.
7.8.4 Analyzing Interchange Limit Results
The significant difference between this Sequential Participation Interchange Limit calculation and
the Two-area Transmission Interchange Limit calculation, described in activity TLTG, is that the
generation shift here is established by sequential participation of specific buses each with its own
participation factor.
When multiple participation blocks are specified in the Subsystem Participation Data File for the
study and/or opposing systems, the study system generation shift and the block participation factors
specified in the Subsystem Participation Data File are used to allocate portions of the specified shift
sequentially among the participation blocks. Within each participation block, its allocation is
assigned to the block's participating buses in proportion to their bus participation factors. Thus, the
sensitivity of each monitored element's flow to an incremental change in study system interchange
is defined by a set of power transfer distribution factors that vary according to the current level of
study system interchange.
7.8.5 Output Report Format
In reporting the base case solution, activity SPIL lists the study system generation, the opposing
system generation, and the study system net interchange corresponding to the network solution
before and after applying the generation shift. This is followed by a tabulation of the pre-shift and
post-shift generation at those study system and opposing system buses participating in the gener-
ation shift. Loadings on monitored elements are then reported, sorted such that the most restrictive
elements are listed first. Either incremental or total pre-contingency transfer limits, as appropriate,
are listed.
For monitored three-winding transformer windings, flow estimates are calculated at the winding bus
end as power flowing into the transformer. For other monitored branches, flow estimates are calcu-
lated at the metered end in the from bus to to bus direction. The flow across an interface is taken
as the sum of the flows of its members. For three-winding transformer windings, the flow is calcu-
lated at the winding bus as power flowing into the transformer. For other members, the flow is
calculated at its metered end in the from bus (i.e., the first bus specified in entering the branch; refer
to Monitored Element Data File Contents) to to bus direction.
Flow estimates are listed for each of three interchange schedules: with the original generation
profile, with the specified generation shift, and at the generation shift corresponding to the transfer
level limit required for the most restrictive monitored element (i.e., the one listed first). Any flow at
or above the selected percentage of the appropriate rating is followed by an asterisk ( - ). The
power transfer distribution factor relating the change in flow on the monitored element to a change
in study system net interchange is also tabulated. When multiple participation blocks were specified
Siemens Energy, Inc., Power Technologies International 7-77
PSS
E EXAMPLE directory.
As an example, a Subsystem Participation Data file was prepared for the two study areas STUDY
and EAST identified in the savnw.sub file. The file is shown in Figure 7-14 where it can be seen that
generators at Buses 101 and 102, in the STUDY subsystem are identified as participating at 20%
and 80% respectively. In the EAST subsystem, the opposing system, there are two participation
Linear Network Analysis PSS
E 32.0
Calculating Sequential Participation Interchange Limits Program Operation Manual
7-78 Siemens Energy, Inc., Power Technologies International
blocks, one of which has a participation of 30% and the other with participation of 70%. Each block
has a participating generator and load bus.
For the purposes of running and example case, a total shift of 100 MW is assumed. In the Report
listing, Figure 7-15, it can be seen that this shifts in the study and opposing systems are apportioned
as defined by the participation block ratios as identified in Figure 7-14.
Figure 7-14. Participation Factors
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
7
-
7
9
P
S
S
E
3
2
.
0
L
i
n
e
a
r
N
e
t
w
o
r
k
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
C
a
l
c
u
l
a
t
i
n
g
S
e
q
u
e
n
t
i
a
l
P
a
r
t
i
c
i
p
a
t
i
o
n
I
n
t
e
r
c
h
a
n
g
e
L
i
m
i
t
s
Figure 7-15. Sequential Participation Interchange Limit Output for Base Case
Linear Network Analysis PSS
E 32.0
Calculating Sequential Participation Interchange Limits Program Operation Manual
7-80 Siemens Energy, Inc., Power Technologies International
It can be seen that the transfer capabilities and participation factors are different from those shown
in Figure 7-12 where sequential participation factors were not used. There, the power shift is appor-
tioned relative to the MBASE value for the machines in the two participating systems.
7.8.7 Interchange Limits Contingency Cases
When reporting flows for contingency cases, the events comprising the contingency are listed
followed by flows on the monitored elements sorted as described above. The flow table includes
both the contingency case flows in the same form as the base case report described above, as well
as the base case flows at the transfer level required for the most restrictive monitored element. Only
the contingency case constraints are considered in calculating the transfer limit; base case flows at
the transfer limit may be shown as overloaded because the corresponding constraints are ignored
in the transfer limit calculation.
A summary report tabulates the number of system condition solutions attempted and the number
for which there exists no interchange schedule at which the rating constraint can be satisfied for all
monitored elements. This is followed by a tabulation of monitored elements for all system conditions
that were calculated, in order of increasing incremental or total transfer capability, as appropriate.
The limiting element is listed along with its power transfer distribution factor, its pre-shift contingency
case flow, its rating, and a description of the system condition.
Only those monitored elements satisfying the cutoff threshold solution parameters set by the user
when launching the calculation process are included in the summary. After an element has been
listed the maximum number of times < n >, its nth occurrence includes an asterisk ( - ) before its
description, and further reporting of the element is suppressed.
This summary report is reprinted for each selected interface with interface transfer limits and distri-
bution factors rather than study system interchange limits and distribution factors tabulated. All
distribution factors on the interface transfer limits summary report describe changes in monitored
element flow relative to a change in interface flow. The branches that form the interface are listed
on the first page of an interfaces transfer limit summary report.
The final page of the summary report lists those elements that were reported < n > times, sorted by
the number of times they would have been reported.
If a line outage contingency forms an island with no Type 3 (swing) bus, a singular submatrix is
formed. Any monitored branch that is located in the swingless island, as well as any interface that
includes such a branch as a member, has dashes printed where its contingency case results would
normally be printed.
Reference can be made to Figure 7-13, which shows the report listing for the two-area Transmis-
sion Interchange Limit calculation. The format for this two area calculation, using sequential
participation factors, is the same. The results, however, will show different interchange limits and
distribution factors.
7.8.8 Application Notes
Activity SPIL uses the same linearized network model as is used in activity DCLF. Thus, the
comments in Section 7.4.4 apply here as well. Note, in particular, the approximate nature of the
linearized network model used by activity SPIL. The proper role of activity SPIL, therefore, should
be to focus attention on those system conditions that deserve more detailed study.
Activity SPIL detects the specification of duplicate single and double line outage contingencies and
calculates the contingency case solution only for the first specification of such a contingency. Any
Siemens Energy, Inc., Power Technologies International 7-81
PSS
E 32.0
Calculating Sequential Participation Interchange Limits Program Operation Manual
7-82 Siemens Energy, Inc., Power Technologies International
described in the output block for that condition when full output is selected; when the summary
report is chosen, such cases are identified.
Such insoluble conditions are described in the output block for that condition when full output is
selected; when the summary report is chosen, such cases are identified.
When specifying a rating percentage of other than 100%, note that interface ratings are also scaled
by the specified percentage in checking their flows to determine maximum interchange.
Additional Information
PSS
E GUI Users Guide, Section 13.9, Calculating Sequential Participation Interchange Limits
PSS
E 32.0
Performing Interchange Limit Analysis with Two Opposing Systems Program Operation Manual
7-84 Siemens Energy, Inc., Power Technologies International
Convert ratings to esti-
mated MW ratings
disabled
If enabled, ratings of monitored branches are converted to esti-
mated MW ratings based upon each monitored lines reactive
power loading at the metered end in the base case ac solution.
Line flow code
dc base
case
The line flow code defines the base flow to be used in deriving
contingency case flow estimates.
dc base case
ac base case
Phase shifter in base case Lock
If set to Regulate (in base case), any regulating phase shifter
where adjustment control mode CODn (refer to Transformer Data)
is set to +3 holds its base case flow in all base case shift solu-
tions. If set to Lock, all phase shift angles are locked at their base
case settings.
Base case constraints in
contingency case
Ignore
If set to Include, both base case and contingency case flow
constraints are recognized in calculating the pre-contingency
interchange limits for each contingency case. If set to Ignore, only
the contingency case loadings are considered (refer to
Section 7.7.8).
Add study system ties to
monitored lines
Disabled
If enabled, automatically include Study System tie lines as
monitored elements.
Maximum allowed
opposing system genera-
tion shift
10000
Places a bound on the permissible generation shift for each
of the opposing systems.
Minimum distribution factor
magnitude
0.0
Defines the minimum distribution factor magnitude
threshold for including monitored elements in the transfer
limit calculation and report. Any monitored element for
which both of its power transfer distribution factor magni-
tudes are below this threshold is ignored during the
processing and reporting of the corresponding system
condition.
Table 7-6. Interchange Limits Analysis Options for Two Opposing Systems (Cont.)
Specification Default Description
Siemens Energy, Inc., Power Technologies International 7-85
PSS
E 32.0
Performing Interchange Limit Analysis with Two Opposing Systems Program Operation Manual
7-86 Siemens Energy, Inc., Power Technologies International
7.9.2 Operation of Activity POLY
Activity POLY checks that generators are not converted (refer to CONG) and that each non-Type 4
bus is connected back to a Type 3 (swing) bus through the in-service ac network. If any violations
are detected, an appropriate message is printed and activity POLY is terminated.
If a new ordering of network buses is required, an appropriate message is printed and activity
ORDR is automatically executed. Activity POLY calculates and prints the largest active power
mismatch corresponding to the present ac solution voltage vector in the working case. The user
may specify that activity TLTG be terminated (default) if this largest mismatch is greater than the
MW mismatch tolerance.
The user must enter the name of a Distribution Factor Data File constructed by activity DFAX that
corresponds to the network condition contained in the working case (refer to Section 7.1.6) and to
the desired Linear Network Analysis Data Files (refer to Section 7.1.1). The Distribution Factor Data
File must specify at least one monitored branch or interface. The bus input option (refer to
Section 3.3.3 and activity OPTN) must have the same setting that was in effect when activity DFAX
filled the specified file. Refer to Section 2.4.1 for the file specification conventions used by activity
POLY.
The user must specify the study and opposing systems. If fewer than two subsystems are defined,
an appropriate error message is printed and activity POLY is terminated. If either two or three
subsystems were specified, the designated subsystem is taken as the study system while the
remaining two subsystems are treated as the opposing systems. If more than three subsystems
were defined, the user specifies the two opposing systems. Activity POLY verifies that there are no
Constraint plot code
Only
feasible
Defines constraint line plotting:
All constraints
Only feasible region boundary
If combi ned cases speci fi ed, al l moni tored el ement
constraint lines that fall within the plotting limits specified by
A interchange are plotted. Otherwise, only those constraint
lines that form the border of the feasible region are plotted;
refer to Section 7.9.3.
Graphic output
Standard
output
Output display:
Standard output: graphic report reduced to fit on page
Two pages per case: page 1 = plotted results; page 2 =
listing of monitored elements corresponding to those
constraint lines that form the border of the feasible
region; refer to Section 7.9.3.
Place
Dialog
window
Output location:
Dialog window
Printer
Output file (results)
POLY Results file (*.pol): output file to which the information
will be written for current or later plotting of the graphical
display of results.
Table 7-6. Interchange Limits Analysis Options for Two Opposing Systems (Cont.)
Specification Default Description
Siemens Energy, Inc., Power Technologies International 7-87
PSS
E 32.0
Performing Interchange Limit Analysis with Two Opposing Systems Program Operation Manual
7-88 Siemens Energy, Inc., Power Technologies International
One final optimal solution is calculated for a combined case. This solution calculation includes
constraints for all system conditions (i.e., the base case and all contingency cases) for which an
individual optimum solution was found. This calculation therefore determines the maximum study
system export (or import, as appropriate) schedule such that no monitored element is overloaded
in the base case or under contingency conditions.
The combined case solution is then reported and, prior to terminating, activity POLY summarizes
the calculated interchange limits for the base case, for all contingency cases, and for the combined
case.
7.9.3 Output Report Format
In reporting the base case solution, activity POLY lists the generation in the study and opposing
systems and the study system net interchange corresponding to the network solution before
applying any generation shift and in the two generation shift cases. This is followed by a tabulation
of the pre-shift and post-shift generation at those study system and opposing system buses partic-
ipating in the generation shifts.
The generation shifts required to achieve the interchange limit (import or export, as appropriate) are
then listed, along with the limiting lines and/or interfaces and their ratings (see Figure 7-16).
For monitored three-winding transformer windings, flow estimates are calculated at the winding bus
end as power flowing into the transformer. For other monitored branches, flow estimates are calcu-
lated at the metered end in the from bus to to bus direction. The flow across an interface is taken
as the sum of the flows of its members. For three-winding transformer windings, the flow is calcu-
lated at the winding bus as power flowing into the transformer. For other members, the flow is
calculated at its metered end in the from bus (i.e., the first bus specified in entering the branch; refer
to Monitored Element Data File Contents) to to bus direction.
Loadings on monitored elements are then reported. The flow estimates are listed for each of four
interchange schedules: with the original generation profile; with the specified generation shift in the
study system and the opposite shift in the first opposing system; with the specified generation shift
in the study system and the opposite shift in the second opposing system; and in the case with
maximum import or export, as appropriate, in which no monitored elements exceed the specified
percentage of the selected rating. Any flow at or above the selected percentage of the appropriate
rating is followed by an asterisk ( - ). The power transfer distribution factors relating the change in
flow on the monitored element to a change in study system net interchange with the opposite
change in the two opposing systems in turn are also tabulated, along with the rating of the monitored
element; for branches, this is not the percentage of the rating used in determining the interchange
limit, but either the value of rating as entered in activities such as READ, Reading Power Flow Data
Additions from the Terminal, RDCH, CHNG or the [Spreadsheet], or, if the convert ratings option was
selected at the start of activity POLY, the estimated MW ratings (see Figure 7-16).
When reporting results for contingency cases, the events comprising the contingency are listed,
followed by the generation shifts required to achieve the transfer limit for the contingency case
being reported, along with the limiting elements. The flow table includes both the contingency case
flows in the same form as the base case report described above, as well as the base case flows at
the transfer limit. Note that if the ignore base case constraints in contingency cases option was
specified, only the contingency case constraints are considered in calculating the transfer limit; in
this case, base case flows at the transfer limit may be shown as overloaded because the corre-
sponding constraints are ignored in the transfer limit calculation.
Siemens Energy, Inc., Power Technologies International 7-89
PSS
E
3
2
.
0
P
e
r
f
o
r
m
i
n
g
I
n
t
e
r
c
h
a
n
g
e
L
i
m
i
t
A
n
a
l
y
s
i
s
w
i
t
h
T
w
o
O
p
p
o
s
i
n
g
S
y
s
t
e
m
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 7-16. Typical Output from Interchange Calculation for Two Opposing System
Siemens Energy, Inc., Power Technologies International 7-91
PSS
E 32.0
Performing Interchange Limit Analysis with Two Opposing Systems Program Operation Manual
7-92 Siemens Energy, Inc., Power Technologies International
Figure 7-17. Graphical Output from Calculation of Interchange Limit with Two Opposing
Systems
7.9.5 Application Notes
Activity POLY uses the same linearized network model as is used in activity DCLF. Thus, the
comments in Section 7.4.4 apply here as well. Note, in particular, the approximate nature of the
linearized network model used by activity POLY. The proper role of activity POLY, therefore, should
be to focus attention on those system and transfer conditions that deserve more detailed study.
Activity POLY detects the specification of duplicate single- and double-line outage contingencies
and calculates the contingency case solution only for the first specification of such a contingency.
Any contingency cases involving bus boundary contingency events, line closure contingency
events, or more than two-line outage contingency events are not checked for duplication.
Siemens Energy, Inc., Power Technologies International 7-93
PSS
E 32.0
Midwest MW-Mile Calculation Program Operation Manual
7-94 Siemens Energy, Inc., Power Technologies International
7.10 Midwest MW-Mile Calculation
Activity MWMI
This activity was incorporated into PSS
E provides the user with the capability to construct an electrical equivalent of all or a sub-
system of the network in the currently open power flow case. The case must be solved to an
acceptable mismatch level. The output of the construction process is a case with part or all of the
original network model replaced by an equivalent representation.
The primary purpose in constructing equivalents is to represent a portion of a network containing
many buses but having only a few boundary buses by a reduced network containing only the
boundary buses and, perhaps, a few selected buses from within the original subnetwork. Histori-
cally, equivalents have often been used to allow the representation of larger areas of major
interconnected systems in studies using computer programs which, due to restrictions imposed by
the computing hardware, were of limited dimensional capacity. Advances in computer technology,
particularly in the area of memory address capability, have lifted these restrictions to the extent that
network modeling capacity is usually no longer an issue. The primary application of equivalents in
modern engineering computers is to achieve improved computational speed in simulations by
removing buses and branches that are not of specific interest but which do influence system
behavior.
8.1.1 Nomenclature of Equivalents
In discussing the application of equivalents, it is useful to adopt the following terminology:
Study System: A group of buses and branches under detailed study. Within the study system,
all components are represented explicitly.
External System: A group of buses and branches that is connected to and influences a study
system, but which does not need to be represented in detail.
Boundary Buses: Buses from which branches run either into a study system, and one or
more external systems, or into more than one external system.
Source System: A power system representation that contains all components of an external
system as a subset of its own components. It is used to solve for the base conditions within
the external system. The source system does not need to include the study system, but
must recognize flows between the external and study system.
Network Reduction PSS
E 32.0
Methodology of the Electrical Equivalent Program Operation Manual
8-2 Siemens Energy, Inc., Power Technologies International
Electrical Equivalent: An artificial group of branches and buses that represents the behavior
of the external system as seen from its boundary buses.
Retained Bus: A bus of the external system that is also a bus of the electrical equivalent. A
retained bus is not necessarily a boundary bus, but all boundary buses are retained buses.
Deleted Bus: A bus of the external system that is not a bus of the electrical equivalent, but
where the effect is represented by the equivalent.
Tie Branch: A branch having one end in one system (study or external) and another end in a
different system. Tie branches are connected to boundary buses at each end.
Area: A group of buses designated in power flow input data for interchange control purposes.
An area may, but does not necessarily, coincide with a study or external system.
8.2 Methodology of the Electrical Equivalent
Activity Methodology
An electrical equivalent is constructed by performing a reduction operation on the admittance matrix
of the external system that is to be represented by the equivalent. The admittance matrix equation
of the external system may be written in the partitioned form
(8.1)
where I
1
and V
1
are node current and voltage at the nodes to be retained and I
2
and V
2
are node
current and voltage at the nodes to be deleted.
The desired form of an equivalent is an equation involving only I
1
and V
1
explicitly, with the I
2
and
V
2
variables assumed to be linearly dependent upon I
1
and V
1
, and recognized implicitly. The
equivalent is obtained by rearranging the second row of Equation 8.1 as
V
2
= Y
4
-1
(I
2
- Y
3
V
1
) (8.2)
and substituting this into the first row of Equation 8.1 to give
I
1
= (Y
1
- Y
2
Y
4
-1
Y
3
)V
1
+ Y
2
Y
4
-1
I
2
(8.3)
The first term of Equation 8.3 specifies a set of equivalent branches and static shunt elements
connecting the retained nodes, while the second term specifies a set of equivalent currents that
must be impressed on the retained nodes to reproduce the effect of load currents at the deleted
nodes. These equivalent currents may be translated into equivalent constant real and reactive
power loads at the retained buses. The equivalent obtained by translating the two terms of Equation
8.3 into equivalent branches, shunts, and loads is exact in the base case for which the current
vector, I
2
, was calculated. When voltage conditions at the boundary buses are changed, the equiv-
alent gives an approximation to the change in power flow into the external system. This
approximation is good as long as the changes are small, but may become unreliable when
boundary bus voltages and power flows into the external system (or its equivalent) deviate from the
base values by large amounts.
I
1
I
2
=
Y
1
Y
2
Y
3
Y
4
V
2
V
1
Siemens Energy, Inc., Power Technologies International 8-3
PSS
E 32.0
Methodology of the Electrical Equivalent Program Operation Manual
8-4 Siemens Energy, Inc., Power Technologies International
Figure 8-1. Separation of Complete Network into Study System and External
Systems by Boundaries
Three special bus type codes are used to designate boundary buses at various stages of the equiv-
alent construction processes:
It can be seen in Figure 8-1 that the area designated as the Study System there are three buses
(buses 198,78 and 77) that are the terminals of lines incoming from the other two areas and there
Type 5 As for Type 1 (load bus); boundary bus or a bus that is not to be deleted by the
equivalencing option, retained bus.
Type 6 As for Type 2 (generator bus); boundary bus.
Type 7 As for Type 3 (swing bus); boundary bus.
911
912
914
917
B B
D R
Study
System
302
13
77
78
198
B
B
B
T
T
T
T
B
R
R
B
550
553
552
551
T
External
System
External
System
Boundary
Boundary
Boundary
D = Deleted Bus
T = Tie Branch
B = Boundary Bus
R = Retained Bus
Siemens Energy, Inc., Power Technologies International 8-5
PSS
E.
Furthermore, PSS
E 32.0
Building an Electrical Equivalent Program Operation Manual
8-6 Siemens Energy, Inc., Power Technologies International
8.3 Building an Electrical Equivalent
Activity EEQV
The power flow equivalent construction activity EEQV constructs an electrical equivalent of a
subsystem of the network contained inside the working case.
1
The input to activity EEQV (i.e., the working case) must be solved to an acceptable mismatch level.
The output of activity EEQV is a working case with part or all of the original network model replaced
by an equivalent representation.
8.3.1 Overview
The equivalent constructed by activity EEQV is exact in the base case from which it was calculated.
It gives an exact reproduction of the self and transfer impedances of the external system as seen
from its boundary buses. The net total of load, generation, and losses in the equivalent matches this
total in the complete external system if the bus voltages in the working case were a valid power flow
solution. However, the load, generation, and loss totals in the equivalent may not individually match
those of the complete external system.
When voltage conditions at the boundary buses of the study system are changed, the equivalent
gives an approximation to the change in power flow into the external system. This approximation is
good as long as the changes are small, but may become unreliable when boundary bus voltages
and power flows into the external system (or its equivalent) deviate from the base values by large
amounts.
An electrical equivalent is, therefore, correctly applied when it represents an external system in
which disturbances or switching operations under study produce only minor effects. Equivalents
should not be applied to network segments in the close vicinity of the disturbances or switchings.
Run Activity EEQV - GUI
Power Flow > Equivalence Networks
[Equivalence Networks]
Build electrical equivalent (EEQV) Tab
Run Line Mode Activity EEQV - CLI
ACTIVITY?
>>EEQV
USER SPECIFIES SUBSYSTEM TO BE EQUIVALENCED
ENTER UP TO 20 BUS NUMBERS
>>
Interrupt Control Codes
None
1
An electrical equivalent of the portion of the working case outside of the specified subsystem may be constructed using
the BAT_XEQV command at the PSS
E Command Prompt.
Siemens Energy, Inc., Power Technologies International 8-7
PSS
E 32.0
Building an Electrical Equivalent Program Operation Manual
8-8 Siemens Energy, Inc., Power Technologies International
8.3.3 Operation of Activity EEQV
First, the portion of the working case to be exempted from the equivalencing activity is (temporarily)
removed from the working case, and all radial and two-point Type 1 buses are calculated as elec-
trical equivalents (refer to RDEQ).
The standard output of activity ORDR is tabulated, and the construction of the equivalent is
completed.
If the user specified activity EEQV to net load and shunt at retained buses, it nets the total equiva-
lent load and shunt at retained buses such that occurrences of load and shunt that cancel at the
bus (e.g., positive load and negative shunts) are eliminated. The component of smaller magnitude
is set to zero with the other component set to the netted quantity. Active and reactive components
at each retained bus are processed independently.
If net load and shunt was disabled, the equivalent load and shunt components at retained buses
remain as calculated by the equivalent construction matrix reduction process.
The equivalent and detailed system sections are then combined.
8.3.4 Equivalencing Methodology
The activity of constructing and using an electrical equivalent can be separated into three steps:
1. Isolating an external system in the working case. Activity EEQV temporarily discards from
the working case all other subsystems (study and external) contained in the source system
Net load and shunt
This option treats the total equivalent load and shunt at retained
buses such that occurrences of load and shunt that cancel at the bus
(e.g., positive load and negative shunts) are eliminated. The compo-
nent of smaller magnitude is set to zero with the other component set
to the netted quantity. Active and reactive components at each
retained bus are processed independently.
Disable to allow the equivalent load and shunt components at
retained buses to remain as calculated by the equivalent construction
matrix reduction process
Minimum generation for
retaining generator buses
Enable to net small plants at Type 2 buses.
The user sets the positive threshold below which Type 2 buses will
have their generation netted with the bus load and its type code
changed to one. This does not apply to boundary Type 2 buses or
area swing buses. Both active and reactive power generation magni-
tudes must be below the threshold. If the threshold specified is zero,
all Type 2 generator buses in the subsystem being calculated as
electrical equivalents are retained.
Branch threshold tolerance
Any equivalent branch where magnitude of impedance is greater than
this tolerance is not retained in the equivalent. The default value is
10 per unit.
Table 8-1. Network Equivalence Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 8-9
PSS
E working case.
The equivalent constructed by activity EEQV is present in the working case along with the unequiv-
alenced portions of the system in the same form as an unequivalenced power flow case. There are
normally no operations required to combine system sections.
Activity EEQV processes only the positive sequence network. If sequence data is included in the
working case, the following message is printed upon entering activity EEQV and processing
continues:
WARNING: SEQUENCE DATA WILL NOT BE EQUIVALENCED
Activity EEQV requires that the working case represent a solved system condition.
In constructing the equivalent, all nonboundary Type 1 buses in the designated external system are
eliminated, and all Type 5, 6, and 7 buses are retained as Type 1, 2, and 3 buses, respectively.
Normally, the boundary buses from within the subsystem being calculated as electrical equivalents
are those connected to buses outside of the specified subsystem. However, when the subsystem
to be calculated as an electrical equivalent is specified by bus only, Type 1 and netted Type 2 buses
specified are calculated as electrical equivalents, with the boundary buses being those buses to
which they are connected and that are not among those specified.
When three or more buses are all connected together by zero impedance lines (refer to Section ),
either all may be calculated as electrical equivalents, all may be retained, or one may be retained.
If the bus type codes are such that more than one but not all the buses in such a group of buses
are to be retained, activity EEQV prints an appropriate message and retains all buses in the group.
Table 8-2. Electrical Equivalencing of Buses
Bus Type Code Treatment By Activity EEQV
1 Bus eliminated
2 and 3 Bus retained
4
Bus ignored in the computation and not included
in the equivalent
5, 6, and 7
Bus retained in the equivalent with 4 subtracted
from its bus type code
Network Reduction PSS
E 32.0
Building an Electrical Equivalent Program Operation Manual
8-10 Siemens Energy, Inc., Power Technologies International
Three-winding transformers are handled as follows:
If all three buses connected by an in-service three-winding transformer are to be
retained, the transformer is explicitly retained.
If at least one of the three buses connected by an in-service three-winding transformer
is to be calculated as an electrical equivalent, the transformer is calculated as an elec-
trical equivalent.
Out-of-service three-winding transformers are ignored in constructing the equivalent
and are omitted from the equivalent.
Activity EEQV automatically retains the converter buses of unblocked dc lines, the sending and
terminal buses of in-service FACTS devices, and buses connected to terminal buses of in-service
FACTS devices.
For any bus where voltage is being controlled by a remote generator, switched shunt, VSC dc line
converter, or FACTS device shunt element, an alarm is printed if the controlled bus is calculated as
an electrical equivalent while the voltage controlling equipment is retained. The controlling equip-
ment is then set to control local bus voltage and the scheduled voltage setpoint or band is not
changed.
For any bus with voltage controlling equipment that is being controlled by a remote switched shunt,
an alarm is printed if the controlled bus is calculated as an electrical equivalent while the controlling
switched shunt bus is retained. The switched shunts control mode is not changed.
Equivalent branches introduced by activity EEQV are assigned the circuit identifier 99.
Equivalent loads introduced by activity EEQV are assigned the load identifier 99. If a load with the
identifier 99 already exists at a retained bus, activity EEQV adds any equivalent load to the load
already modeled as load 99; if such a load is associated with an adjustable bus load table for which
the load multiplier is zero, a mismatch is introduced at the corresponding retained bus.
Equivalent bus shunts introduced by activity EEQV are assigned the shunt identifier 99. If a shunt
with the identifier 99 already exists at a retained bus, activity EEQV adds any equivalent shunt
admittance to the fixed shunt already modeled as shunt 99.
Siemens Energy, Inc., Power Technologies International 8-11
PSS
E 32.0
Building an Electrical Equivalent Program Operation Manual
8-12 Siemens Energy, Inc., Power Technologies International
Figure 8-3. Pre-Equivalence Power Flow Diagram for the WORLD Area
Aftr building an electrical equivalent of the WORLD area, the raw data appears as shown in
Figure 8-4.
It can be seen that the total load of 500 MW in the WORLD area has been retained but allocated to
the retained buses 3004, 3006, 3008 and 3011 with an identifier of 99. Note that bus 3008 already
had a load of 200 MW with an identifier of 1.
The buses at the boundaries have been maintained but now the number of buses is reduced to five.
There are now 6 new branches with in the WORLD area each with a circuit identifier of 99.
WORLD Area Boundary Buses
Siemens Energy, Inc., Power Technologies International 8-13
PSS
E 32.0
Building an Electrical Equivalent Program Operation Manual
8-14 Siemens Energy, Inc., Power Technologies International
Figure 8-5. Redrawn One-Line Diagram to Match Topology after Building an
Electrical Equivalent
Boundary buses
Siemens Energy, Inc., Power Technologies International 8-15
PSS
E
activities, including activity EEQV. That is, it is permissible to construct an equivalent of an external
system that contains an equivalent.
Additional Information
PSS
E 32.0
Applying Net Generation with Load at All Non-Boundary Buses Program Operation Manual
8-16 Siemens Energy, Inc., Power Technologies International
8.4 Applying Net Generation with Load at All Non-Boundary
Buses
Activity GNET
The generation netting activity GNET changes the in-service generation to negative MVA load at all
Type 2 and 3 buses within the subsystem specified by the user.
Prior to running a global network equivalence, or when it is required merely to reduce the number
of generators modelled in a power flow case, generators can be removed by netting their output
with the load at a bus. Generators at all type 2 and 3 buses will be replaced with equivalent negative
load with these exceptions:
Buses that are designated by the user at the start of the activity.
Buses that are indicated by type codes 6 or 7 to be boundary or retained buses.
When replacing generation with an equivalent load, the power flow solution will remain the same,
i.e. re-solving the case after the netting process will not produce a different solution.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. What is different from most of the other subsystem
selections is that, for netting generation, the user can choose to identify those generators that will
be netted (see the inside the selected subsystem in the figure) or choose to identify those genera-
tors that will not be netted (see the outside option).
Activity GNET processes all Type 2 and 3 buses specified as inside the selected subsystem as
follows:
1. The type code is set to 1.
2. A new load entry is introduced at the bus.
3. PL of the new load is set to PG.
4. QL of the new load is set to QG.
Run Activity GNET - GUI
Power Flow > Equivalence Networks
[Equivalence Networks]
Net generation with load (NETG/GNET) Tab
Run Line Mode Activity GNET - CLI
ACTIVITY?
>>GNET
USER SPECIFIES THOSE TO BE NETTED
ENTER UP TO 20 BUS NUMBERS
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 8-17
PSS
E 32.0
Applying Net Generation with Load at All Non-Boundary Buses Program Operation Manual
8-18 Siemens Energy, Inc., Power Technologies International
Figure 8-6. Generation and Load in Power Flow Case savnw.sav
Figure 8-7. Result of Netting Generation in the LIGHTCO Area
Generation
Loads
New loads representing Generation at Bus 206 and Bus 211
Siemens Energy, Inc., Power Technologies International 8-19
PSS
E 32.0
Applying Net Generation with Load at All Buses Except Boundary BusesProgram Operation Man-
8-20 Siemens Energy, Inc., Power Technologies International
8.5 Applying Net Generation with Load at All Buses Except
Boundary Buses
Activity NETG
The generation netting activity NETG changes the in-service generation to negative MVA load at all
Type 2 and 3 buses except those within the subsystem specified by the user.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV.
Activity NETG processes all Type 2 and 3 buses except those specified as outside the selected
subsystem as follows:
1. The type code is set to 1.
2. A new load entry is introduced at the bus.
3. PL of the new load is set to PG.
4. QL of the new load is set to QG.
Activity GNET summarizes processing, listing the number of buses netted with their loads.
When activity NETG introduces a load at a bus, the load is assigned the identifier 99. If a load with
the identifier 99 already exists at the bus, an unused two-digit identifier is assigned.
Because activity NETG processes only Type 2 and 3 buses, those generator buses that have been
designated as boundary buses, and hence have type codes of 6 or 7, do not have their generation
netted (refer to Section 5.2.5 and activity EXTR).
Run Activity NETG - GUI
Power Flow > Equivalence Networks
[Equivalence Networks]
Net generation with load (NETG/GNET) Tab
Run Line Mode Activity NETG - CLI
ACTIVITY?
>>NETG
USER SPECIFIES EXCEPTIONS (I.E., THOSE NOT TO BE NETTED)
ENTER UP TO 20 BUS NUMBERS
>>
Interrupt Control Codes
None
Additional Information
PSS
E
GUI Users Guide, Section 14.1, Building a Network Equivalent; buses that will be calculated as an
electrical equivalent are selected by the Net generation inside the selected subsystem option and
buses that will not be be calculated as an electrical equivalent are selected by the Net generation
outside the selected subsystem option in [Equivalence Networks] dialog.
Activity EQRD builds an electrical equivalent for buses inside the specified subsystem of the
working case.
If sequence data is contained in the working case, the zero sequence network is calculated as an
electrical equivalent along with the positive sequence.
The radial equivalent process determines the buses to be calculated as electrical equivalents based
upon their current electrical connections. Suppose, for example, that bus I is a Type 1 bus con-
nected to two other buses by in-service branches and that there is an out-of-service branch from
bus I to a third bus. Assuming that bus I is not in the subsystem to be exempted from the equiva-
lencing process and that the two-point bus equivalencing option was enabled, bus I will be
calculated as an electrical equivalent.
It is neither necessary nor helpful to build an electrical equivalent of radial or two-point buses prior
to building a global electrical equivalent of a network or subsystem.
Buses that are always retained by this radial/two-point option are those:
Connected by three-winding transformers
Converter station buses of dc lines
Run Activity EQRD - GUI
Power Flow > Equivalence Networks
[Equivalence Networks]
Equivalence radial / 2-point buses (EQRD/RDEQ) Tab
Run Line Mode Activity EQRD - CLI
ACTIVITY?
>>EQRD
ENTER 1 TO EQUIVALENCE RADIAL BUSES ONLY:
>>
Interrupt Control Codes
None
Network Reduction PSS
E 32.0
Equivalencing Radial Buses Program Operation Manual
8-22 Siemens Energy, Inc., Power Technologies International
With FACTS devices connected to them are always retained.
Whenever a two-point bus and its connected branches are calculated as electrical equivalents, the
resulting equivalent branch is assigned the smaller RATEA, RATEB, and RATEC of the connected
branches. If load existed at the two-point bus, the ratings of the equivalent branch should be
checked.
Whenever a two-point bus and its connected branches are calculated as electrical equivalents, the
length assigned to the equivalent branch is the sum of the lengths of the equivalent paths. If parallel
branches existed between a retained bus and the equivalenced bus, the length of that path is
assumed to be the length of the longest of the parallel branches.
Equivalent branches, introduced by the radial equivalencing process, are assigned the circuit iden-
tifier 99. Equivalent branches between the same pair of buses have descending circuit identifiers
assigned starting at 99.
Equivalent loads introduced by the radial equivalencing process, are assigned the load identifier 99.
If a load with the identifier 99 already exists at a retained bus, the process adds any equivalent load
to the load already modeled as load 99. If such a load is associated with an adjustable bus load
table for which the load multiplier is zero, a mismatch is introduced at the corresponding retained
bus.
The user may specify any of the following options:
Table 8-3. Radial Bus Equivalencing Options
Specification Description
Equivalence radial buses only
Limit building an electrical equivalent to only radial buses, otherwise
both radial buses and those buses connected to only two other buses
are to be eliminated.
Suppress equivalence of
transformers
Enable to exclude transformer branches from the equivalencing
process.
Suppress equivalence of zero
impedance lines
Enable to exempt from a bus electrical equivalent any branches
that are treated as zero impedance lines (refer to Section ).
Suppress equivalence of
controlled buses
Enable to suppress building an electrical equivalent of buses where
voltage or reactive power output is controlled by remote generation,
switched shunts, VSC dc line converter, and/or FACTS device shunt
element.
Suppress equivalence of
mutually coupled branches
If sequence data is contained in the working case, and zero sequence
mutual couplings have been specified, any branch (and the buses it
connects) involved in a coupling is suppressed, when this option is
enabled.
Suppress equivalence of area
boundary buses
Keeps area boundaries intact when enabled.
Suppress equivalence of zone
boundary buses
Keeps zone boundaries intact when enabled.
Siemens Energy, Inc., Power Technologies International 8-23
PSS
E 32.0
Equivalencing Radial Buses Program Operation Manual
8-24 Siemens Energy, Inc., Power Technologies International
Figure 8-8. Result of Radial Equivalencing Process
8.6.3 Application Notes
If sequence data is contained in the working case, the zero sequence network is calculated as an
electrical equivalent along with the positive sequence.
Activity EQRD determines the buses to be calculated as electrical equivalents based upon their
current electrical connections. Suppose, for example, that bus I is a Type 1 bus connected to two
other buses by in-service branches and that there is an out-of-service branch from bus I to a third
bus. Assuming that bus I is in the subsystem to be calculated as an electrical equivalent and that
the two-point bus equivalencing option was enabled, bus I is calculated as an electrical equivalent
by activity EQRD.
The use of activity EQRD as a preprocessor to activity EEQV is neither necessary nor helpful.
Purple color indicates lines and bus no
longer bound to the power flow case. The
color is a user choice.
Two new buses added to buses 3005 and
3008. Existing load has identifier of 1. New
load has identifier 99.
Siemens Energy, Inc., Power Technologies International 8-25
PSS
E 32.0
Equivalencing Radial Buses, with Exception Program Operation Manual
8-26 Siemens Energy, Inc., Power Technologies International
8.7 Equivalencing Radial Buses, with Exception
Activity RDEQ
The radial bus equivalencing activity RDEQ builds an electrical equivalent for radial and, optionally,
two-point Type 1 buses outside the specified subsystem of the working case. Activity RDEQ uses
the same equivalencing algorithm as activity EEQV.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV.
The user may specify any of the following options:
Run Activity RDEQ - GUI
Power Flow > Equivalence Networks
[Equivalence Networks]
Equivalence radial / 2-point buses (EQRD/RDEQ) Tab
Run Line Mode Activity RDEQ - CLI
ACTIVITY?
>>RDEQ
ENTER 1 TO EQUIVALENCE RADIAL BUSES ONLY:
>>
Interrupt Control Codes
None
Table 8-4. Radial Bus Equivalencing Options, with Exception
Specification Description
Equivalence radial buses only
Disable to build an electrical equivalent for both radial buses and those
buses connected to only two other buses are to be eliminated
Suppress equivalence of
transformers
Enable to suppress building an electrical equivalent of transformers.
Suppress equivalence of zero
impedance lines
Enable to suppress building an electrical equivalent of zero impedance
lines (refer to Section )
Suppress equivalence of
controlled buses
Enable to suppress building an electrical equivalent of buses where
voltage or reactive power output is controlled by remote generation,
switched shunt, VSC dc line converter, and/or FACTS device shunt
element.
Suppress equivalence of
mutually coupled branches
If sequence data is contained in the working case, and zero sequence
mutual couplings have been specified, any branch (and the buses it
connects) involved in a coupling is suppressed, when enabled.
Suppress equivalence of area
boundary buses
Keeps area boundaries intact when enabled.
Suppress equivalence of zone
boundary buses
Keeps zone boundaries intact when enabled.
Siemens Energy, Inc., Power Technologies International 8-27
PSS
E 32.0
Equivalencing Radial Buses, with Exception Program Operation Manual
8-28 Siemens Energy, Inc., Power Technologies International
branches existed between a retained bus and the equivalenced bus, the length of that path is
assumed to be the length of the longest of the parallel branches.
Equivalent branches introduced by activity RDEQ are assigned the circuit identifier 99. Equivalent
branches between the same pair of buses have descending circuit identifiers assigned starting at
99.
Equivalent loads introduced by activity RDEQ are assigned the load identifier 99. If a load with the
identifier 99 already exists at a retained bus, activity RDEQ adds any equivalent load to the load
already modeled as load 99; if such a load is associated with an adjustable bus load table for which
the load multiplier is zero, a mismatch is introduced at the corresponding retained bus.
Equivalent bus shunts introduced by activity RDEQ are assigned the shunt identifier 99. If a shunt
with the identifier 99 already exists at a retained bus, activity RDEQ adds any equivalent shunt
admittance to the fixed shunt already modeled as shunt 99.
Additional Information
PSS
E 32.0
Converting Net Boundary Bus Mismatch Program Operation Manual
8-30 Siemens Energy, Inc., Power Technologies International
When activity BGEN introduces a machine at a bus, it assigns the machine identifier 99; if a
machine 99 already exists at the bus, an unused two-digit identifier is used. Similarly, when activity
BGEN introduces a load at a bus, the load is assigned the identifier 99; if a load with the identifier
99 already exists at the bus, an unused two-digit identifier is assigned.
Activity BGEN may be terminated by entering the AB interrupt control code.
Additional Information
PSS
E 32.0
Building a Three-Sequence Electrical Equivalent Program Operation Manual
8-32 Siemens Energy, Inc., Power Technologies International
Figure 8-9. Pictorial Image of Power Flow Case with Equivalenced Sequence
Networks
The short-circuit equivalencing process performs a simple network reduction without regard to
loads, transformer phase shift, or pre-event voltages. All generators in the external system are rep-
resented by simple Norton equivalents so that their effective impedances (i.e., Norton shunt
admittances) and positive-sequence source currents can be transferred to the boundary buses by
standard network mathematics. The process operates on a standard fault analysis model but with
FLAT pre-event voltages.
The network reduction is performed by setting up the partitioned admittance matrix of the external
system:
(8.4)
where:
The generator internal impedances, Z
pos
, Z
neg
, Z
zero
, where appropriate, are included in the net-
work as shunt elements and are accounted for by the diagonal terms of the admittance matrix. The
positive-sequence source currents are taken as ISORCE = (1./Z
pos
). The admittance matrix and
equivalent source currents of reduced network are then obtained from the elimination formula:
(I
b
- Y
bn
Y
nn
-1
I
n
) = (Y
bb
- Y
bn
Y
nn
-1
Y
nb
)V
b
(8.5)
b Denotes boundary buses.
n Denotes buses to be deleted.
I
b
, I
n
Contains either zero or generator Norton source current as calculated the generator
conversion process.
External System
Positive
Sequence
Negative
Sequence
Zero
Sequence
Study
System
I
b
I
n
=
Y
bb
Y
bn
Y
nb
Y
nn
V
n
V
b
Siemens Energy, Inc., Power Technologies International 8-33
PSS
E.
The form of the equivalent is illustrated in Figure 8-10. Each sequence equivalent is contained in
the working case as fault analysis data for equivalent branches and generators. Each equivalent is
joined by real tie branches to the study system, which remains in the working case, completely
unaltered.
The generator positive- and negative-sequence source impedances in the power flow case need
not be identical. If they are different, the positive-sequence and negative-sequence reduced admit-
tance matrices will be different. The standard PSS
E 32.0
Building a Three-Sequence Electrical Equivalent Program Operation Manual
8-34 Siemens Energy, Inc., Power Technologies International
Figure 8-10. Form of Sequence Equivalents Built the Short-Circuit
Equivalencing Process
1
Z
pos
--------------
ISORCE
1
Z
pos
--------------
1
Z
neg
--------------
1
Z
zero
----------------
,
1
Z
neg
--------------
1
Z
zero
----------------
,
Real
Branches
to Study
System
Real Branches
to Study
System
Real Branches
to Study System
ISORCE
Equivalent
Source Circuits
1 Z
seq
Equivalent Generator
Source Impedances
Real System
Bus to be Deleted
Boundary
Buses
ISORCE
ISORCE
Equivalent Sequence
Networks After
Equivalencing
Sequence Networks
Prior to Equivalencing
Siemens Energy, Inc., Power Technologies International 8-35
PSS
E 32.0
Building a Three-Sequence Electrical Equivalent Program Operation Manual
8-36 Siemens Energy, Inc., Power Technologies International
8.9.4 Operation of Activity SCEQ
If sequence data is not contained in the working case (i.e., activity RESQ has not been executed),
an appropriate message is printed, the equivalent is constructed in the normal manner, but only the
positive sequence equivalent is valid.
If an equivalent of the entire working case is constructed, Type 5 and 6 buses are retained as Type
1 and 2 buses, respectively. The user may specify subsystem data (refer to Section 4.8) by bus
subsystem, area, zone, owner, or basekV. Activity SCEQ generates an alarm and terminates if
either none or all buses are to be retained.
The portion of the working case to be exempted from equivalencing is (temporarily) removed from
the working case, and all radial and two-point Type 1 buses are calculated as electrical equivalents
(refer to RDEQ). Then the standard output of activity ORDR is tabulated as the processing of the
positive sequence network commences.
The user may specify branch threshold tolerance (default = 10 pu); any equivalent branch where
magnitude of impedance is greater than this tolerance is not retained in the equivalent.
If the actual positive sequence impedance of any transformer in the subsystem to be calculated as
an electrical equivalent differs from its nominal value (refer to Transformer Impedance Correction
Table Data), the user may apply impedance corrction to zero sequence. If applied, the zero sequence
impedance of each such transformer is scaled by the same factor as is its positive sequence imped-
ance. Otherwise, all zero sequence transformers are left at their nominal values (i.e., the values
entered in activities RESQ, TRSQ, or SQCH). The same treatment applies to all transformers in the
subsystem to be calculated as electrical equivalents that are not at nominal impedance.
The processing of the positive and negative sequence networks is completed, and the zero
sequence calculation commences. The summary output of the optimal ordering function is printed,
the zero sequence network equivalent is constructed, and activity SCEQ combines the equivalent
and detailed system sections.
When three or more buses are all connected together by zero impedance lines (refer to Zero Imped-
ance Lines), either all may be calculated as electrical equivalents, all may be retained, or one may
be retained. If the bus type codes are such that more than one but not all the buses in such a group
of buses are to be retained, activity SCEQ prints an appropriate message and retains all buses in
the group.
8.9.5 Form of the Equivalent
The equivalent constructed by activity SCEQ is present in the working case along with the unequiv-
alenced portions of the system in the form required for fault analysis work under classical
assumptions. There are no operations required to combine system sections.
In constructing the equivalent, all nonboundary Type 1 and 2 buses in the designated external
system are eliminated, and all Type 5 and 6 buses are retained as Type 1 or 2 buses, respectively.
Normally, the boundary buses from within the subsystem being calculated as electrical equivalents
Sequence data
output file
(*.seq) Optional. The user can save the equivalents in the form of a Sequence
Data File.
Table 8-6. Short Circuit Equivalent Options
Option Description
Siemens Energy, Inc., Power Technologies International 8-37
PSS
E 32.0
Building a Three-Sequence Electrical Equivalent Program Operation Manual
8-38 Siemens Energy, Inc., Power Technologies International
Figure 8-11. Pre-Equivalence Power Flow One-Line Diagram Showing the
FLAPCO Area Buses
FLAPCO Area Buses
Siemens Energy, Inc., Power Technologies International 8-39
PSS
E 32.0
Building a Three-Sequence Electrical Equivalent Program Operation Manual
8-40 Siemens Energy, Inc., Power Technologies International
8.9.7 Application Notes
Activity SCEQ requires that the working case reflect classical assumptions. In setting up this condi-
tion, activity CONG using the positive sequence machine impedance ZPOS option must be
executed after the execution of activity FLAT with classical fault analysis option.
Activity SCEQ is not capable of handling the case in which zero sequence mutual couplings span
the boundary of the external system to be calculated as an electrical equivalent and the portion of
the system to be retained in detail. Any such mutual generates an alarm, the mutual is ignored, and
processing continues.
Activity SCEQ is not able to build an equivalent of a subsystem in which a dc line or FACTS device
is present. If any dc lines or FACTS devices are encountered, an alarm message is printed but
activity SCEQ continues. Upon completion of activity SCEQ, the user should ensure that any such
dc lines and FACTS devices are blocked before using the case in any fault analysis calculation.
Activity SCEQ prints an appropriate error message if the number of equivalent source nodes (i.e.,
generators), fixed bus shunts, or branches exceeds the capacity limits of PSS
E.
Additional Information
PSS
E 32.0
Overview: Short-Circuit Fault Analysis Program Operation Manual
9-2 Siemens Energy, Inc., Power Technologies International
Recognize the actual spread of internal voltage magnitude and phase angle of gener-
ators as initialized from a solved power flow case.
Recognize loads by converting them to equivalent constant shunt admittance.
The level of system modeling detail used in a fault analysis calculation is controlled by manipulating
the positive-sequence (or power flow) data in the working case into the required form before
commencing fault analysis work. The detailed fault analyses always operate on the assumption that
the system is modeled in the highest level of detail. Results corresponding to a simplified modeling
basis are obtained if appropriate elements of data have null values, simplified calculating algorithms
are not used, and, correspondingly, no computing time advantage is gained by simplifying the
system model. The automatic sequencing short circuit analysis operates on the assumption that
system modeling will most often be at a low level of detail. The analysis, however, can calculate
either on the basis of full detail or a faster algorithm that recognizes only a minimum level of detail.
The overriding principle of fault analysis data management in PSS
E work
session in which the unbalanced network analyses are to be used. After a set of sequence data has
been appended to a power flow file, it accompanies the network as the case is saved and retrieved.
Sequence data may be listed for examination and modified in a manner similar to that of standard
(positive sequence) power flow data. The sequence data appear together with the positive
sequence data in the spreadsheet view.
As for positive sequence data, the raw sequence data file is read in free format with data items sepa-
rated by a comma or one or more blanks. Each category of data except the change code is
terminated by a record specifying an I value of zero. Termination of all data is indicated by a value
of Q.
The Sequence Data File contains 10 groups of records (see Figure 9-1) with each group specifying
a particular type of sequence data required for fault analysis work. Any piece of equipment for which
sequence data is to be entered must be represented as power flow data in the power flow case. If
not, the data will not be accepted.
Figure 9-1. Data Stream for Sequence Data Input
Unbalanced Fault Analysis PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-4 Siemens Energy, Inc., Power Technologies International
9.2.1 Short Circuit Change Case Code
The first record in the Sequence Data File contains a single data item, IC, which has the following
significance:
The use of the change case mode for the appending sequence data is identical to its use in reading
the positive sequence power flow data; that is for the addition of equipment to the power flow case
(e.g., to add a zero sequence mutual coupling parameters). It is not valid to set IC to one for the
initial appending of sequence data. In such a situation, an appropriate message is printed and the
process continues its execution as if IC had been specified as zero.
9.2.2 Positive Sequence Generator Impedance Data
Each network bus to be represented as a generator bus (i.e., as a current source) in the unbalanced
analysis activities must have sequence generator impedances appended to the power flow case for
all online machines at the bus. The positive sequence values are entered in positive sequence
generator impedance data records in the Sequence Data File. Each positive sequence generator
impedance data record has the following format:
I, ID, ZRPOS, ZXPOS
where:
During the initial input of sequence data (i.e., IC = 0 on the first data record), any machine for which
no data record of this category is entered has its positive sequence generator impedance, ZPOS
(i.e., ZRPOS + j ZXPOS), set equal to ZSORCE. This is the generator impedance which would be
entered into the power flow case for use in switching studies and dynamic simulation.
In subsequent appending of sequence data (i.e., IC = 1 on the first data record), any machine for
which no data record of this category is entered has its positive sequence generator impedance
unchanged. Note that the generator positive sequence impedance appended for fault analysis
purposes (ZPOS) is not necessarily the same as the generator impedance (ZSORCE) used in
dynamics, and that it does not overwrite ZSORCE. That is, the two different positive sequence
impedances are present in the power flow file simultaneously at different locations.
IC = 0 Indicates the initial input of sequence data for the network contained in the
power flow case. All buses, generators, branches, and switched shunts for which
no data record is entered in a given category of data have the default values
assigned for those data items.
IC = 1 Indicates change case input of sequence data for the network contained in the
power flow case. All buses, generators, branches, and switched shunts for which
no data record is entered in a given category of data have those data items
unchanged. (Specifically, they are not set to the default values.)
I Bus number; bus I must be present in the working case as a generator bus.
ID One- or two-character machine identifier of the machine at bus I for which data is
specified by this record. ID = 1 by default.
ZRPOS Generator positive sequence resistance; entered in pu on machine base (i.e., on
MBASE base). No default is allowed.
ZXPOS Generator positive sequence reactance; entered in pu on machine base (i.e., on
MBASE base). No default is allowed.
Siemens Energy, Inc., Power Technologies International 9-5
PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-6 Siemens Energy, Inc., Power Technologies International
During the initial input of sequence data (i.e., IC = 0 on the first data record), any machine for which
no data record of this category is entered has its zero sequence generator impedance, ZZERO, set
equal to ZPOS, the positive sequence generator impedance.
In subsequent input of sequence data RESQ (i.e., IC = 1 on the first data record), any machine for
which no data record of this category is entered has its zero sequence generator impedance
unchanged.
Zero sequence generator impedance data input is terminated with a record specifying a bus number
of zero.
Siemens Energy, Inc., Power Technologies International 9-7
PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-8 Siemens Energy, Inc., Power Technologies International
9.2.7 Zero Sequence Branch Data
Each zero sequence branch data record has the following format:
I, J, ICKT, RLINZ, XLINZ, BCHZ, GI, BI, GJ, BJ
where:
The zero sequence network is assumed to be a topological subset of the positive sequence
network. That is, it may have a branch in every location where the positive sequence network has
a branch, and may not have a branch where the positive sequence network does not have a branch.
The zero sequence network does not need to have a branch in every location where the positive
sequence network has a branch.
A branch treated as a zero impedance line in the positive sequence is treated in the same manner
in the zero sequence, regardless of its specified zero sequence impedance.
During the initial input of sequence data (i.e., IC = 0 on the first data record), any branch for which
no data record of this category is entered is treated as open in the zero sequence network
(i.e., the zero sequence impedance is set to zero). In subsequent input of sequence data
(i.e., IC = 1 on the first data record), any branch for which no data record of this category is entered
has its zero sequence branch data unchanged.
Zero sequence branch data input is terminated with a record specifying a from bus number of zero.
I Bus number of one end of the branch.
J Bus number of the other end of the branch.
ICKT One- or two-character branch circuit identifier; a non transformer branch with
circuit identifier ICKT between buses I and J must be in the working case.
ICKT = 1 by default.
RLINZ Zero sequence branch resistance; entered in pu. RLINZ = 0.0 by default.
XLINZ Zero sequence branch reactance; entered in pu. Any branch for which RLINZ
and XLINZ are both 0.0 is treated as open in the zero sequence network.
XLINZ = 0.0 by default.
BCHZ Total zero sequence branch charging susceptance; entered in pu. BCHZ = 0.0
by default.
GI,BI Complex zero sequence admittance of the line connected shunt at the bus I end
of the branch; entered in pu. GI + jBI = 0.0 by default.
GJ,BJ Complex zero sequence admittance of the line connected shunt at the bus J end
of the branch; entered in pu. GJ + jBJ = 0.0 by default.
Siemens Energy, Inc., Power Technologies International 9-9
PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-10 Siemens Energy, Inc., Power Technologies International
6. BIJ1 must be less than BIJ2, and BKL1 must be less than BKL2.
7. Mutuals involving transformers or zero impedance lines are ignored by the fault analysis
solution activities.
Figure 9-2 schematically illustrates a mutual coupling with BIJ1 = 0.0, BIJ2 = 0.4, BKL1 = 0.0 and
BKL2 = 1.0 (the first 40% of the first line coupled with the entire second line).
Figure 9-2. Mutual Coupling Example 1
As a second example, BIJ1 = 0.6, BIJ2 = 1.0, BKL1 = 0.0 and BKL2 = 0.6 (last 40% of the first line
coupled with the first 60% of the second line) might be depicted as follows in Figure 9-3.
Figure 9-3. Mutual Coupling Example 2
Zero sequence mutual impedance data input is terminated with a record specifying a from bus
number of zero.
Siemens Energy, Inc., Power Technologies International 9-11
PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-12 Siemens Energy, Inc., Power Technologies International
In specifying zero sequence impedances for three-winding transformers, note that winding imped-
ances are required, and that the zero sequence impedances default to the positive sequence
winding impedances. Recall that, in specifying positive sequence data for three-winding trans-
formers, measured impedances between pairs of buses to which the transformer is connected, not
winding impedances, are required. PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-14 Siemens Energy, Inc., Power Technologies International
Figure 9-4 (Cont). Two-Winding Transformer Connection Codes
Connection Code: Zero Sequence Connection:
Winding 1 Winding 2
6
7
5
8
3.*Z
g
Z
0
t
t
j
t
i
Z
g
Z
0
t
t
i
Z
g
t
j
Z
t
Z
g2
Z
g
Z
0
t
t
j
t
i
t
i
:1 1:t
j
t
i
:1
t
i
:1
1:t
j
1:t
j
Siemens Energy, Inc., Power Technologies International 9-15
PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-16 Siemens Energy, Inc., Power Technologies International
Figure 9-5. (Cont.) Three-Winding Transformer Connection Codes
c. Zero Sequence, Connection Code = 2 (wye/wye/delta)
d. Zero Sequence, Connection Code = 3 (non-autotransformer delta/wye/delta)
Z
3
0
Z
2
0
Z
1
0
3Zg
Z
3
0
Z
2
0
Z
1
0
For ungrounded neutral:
Z
3
0
=
Z
g
=
or set connection code = 114
For impedance grounded, set:
Z
2
0
= Z
2
+
+ 3Z
g
Z
g
= 0
t
1
:1 1:t
2
1:t
2
Siemens Energy, Inc., Power Technologies International 9-17
PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-18 Siemens Energy, Inc., Power Technologies International
Analyzing Transformer Phase Shift Impact
The use of connection codes establishes only the form of the equivalent circuit to be used; it does
not complete the representation of the transformer. The details of the transformer must be conveyed
to PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-20 Siemens Energy, Inc., Power Technologies International
Figure 9-7. Effect of Including and Neglecting 30 Phase Shift in Transformer with One
Grounded and One Ungrounded Winding
I
f
I
f
A
B
C
I
0
I
1
I
2
I
f
3
--- = = =
a
b
System
I
f
3
---
I
f
3
---
I
f
3
---
I
f
3
---
2I
f
3
-------
I
0
0 =
I
1
I
2
I
f
3
--- = =
I
0
0 =
I
f
I
f
A
C
I
f
3
-------
I
f
3
-------
I
f
3
-------
b
c
System
I
f
I
0
I
1
I
2
I
f
3
--- = = =
B
a
c
I
f
a. 30 Phase Shift Wye-Delta
b. No Phase Shift as if a Wye-Wye
I
1
I
f
3
--- 30 Z =
I
2
I
f
3
--- 30 Z =
Siemens Energy, Inc., Power Technologies International 9-21
PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-22 Siemens Energy, Inc., Power Technologies International
The generator zero-sequence model is the impedance, ZZERO, connected to ground. ZZERO
should be assigned the value (3R
g
+ jX
o
), where:
R
g
= the generator grounding resistance in per unit with respect to
generator base voltage and generator base, MVA.
X
o
= the generator zero-sequence impedance, per unit, with respect to
generator base, MVA.
When the generator step-up transformer is modeled as a part of the generator it is always treated
as a two-winding unit:
Delta-connected on the generator side.
Wye-connected and solidly grounded on the transmission system side.
Radial to the generator.
Plant arrangements where the step-up transformers cannot be modeled in this manner must have
the transformers represented as a part of the transmission system. The plant connections produced
in the three sequences by PSS
E 32.0
Preparing Short Circuit Sequence Data Program Operation Manual
9-24 Siemens Energy, Inc., Power Technologies International
9.2.10 Zero Sequence Switched Shunt Data
Each switched shunt data record has the following format:
I, BZ1, BZ2, ... BZ8
where:
Data specified on zero sequence switched shunt data records must be coordinated with the corre-
sponding positive sequence data. The number of blocks and the number of steps in each block are
taken from the positive sequence data.
The input process will alarm any block for which any of the following applies:
The positive sequence admittance is positive and the zero sequence admittance is
negative.
The positive sequence admittance is negative and the zero sequence admittance is
positive.
The positive sequence admittance is zero and the zero sequence admittance is
nonzero.
The zero sequence admittance switched on at a bus is determined from the bus positive sequence
value, with the same number of blocks and steps in each block switched on.
Zero sequence switched shunt data input is terminated with a record specifying a bus number of
zero.
I Bus number; bus I must be present in the working case with positive sequence
switched shunt data.
BZ
i
Zero sequence admittance increment for each of the steps in block i; entered in
pu. BZ
i
= 0.0 by default.
Siemens Energy, Inc., Power Technologies International 9-25
PSS
E 32.0
Appending Sequence Data to the Power Flow Case Program Operation Manual
9-26 Siemens Energy, Inc., Power Technologies International
1. When IC is zero, a listing of all online machines at Type 2 and 3 buses for which no negative
sequence generator impedance is entered. The negative sequence generator impedance,
ZNEG, is set to the positive sequence value, ZPOS.
2. When IC is zero, a listing of all online machines at Type 2 and 3 buses for which no zero
sequence generator impedance is entered. The zero sequence generator impedance,
ZZERO, is set to the positive sequence value, ZPOS.
Siemens Energy, Inc., Power Technologies International 9-27
PSS
E results with
those obtained from other software packages which usually use a more simple or classical model.
9.4.2 Detailed Fault Calculation Models for DC Lines and FACTS Devices
If any unblocked dc lines or in-service FACTS devices are present in the working case, the user can
specify their treatment in the fault analysis solution. The options are to:
Block the device: Lines and FACTS devices are treated as open circuits (i.e., fully
blocked bridges) in all three sequences, regardless of their actual prefault loadings as
given by the initial condition power flow.
Represent as load: the apparent ac system complex loads are converted to positive
sequence constant admittance load at the buses at which these quantities are injected
into the ac system during normal power flow work. In the negative and zero sequence
networks, dc lines and series FACTS devices are represented as open circuits. The
equivalent positive-sequence shunt admittance is derived from the values of PAC and
QAC given by the initial condition power flow at each converter ac bus.
Neither of these two representations should be regarded as exact. The first may be regarded as
reasonable for the calculation of fault-current duty on circuit breakers because converter controls
are usually designed to limit their fault currents to values equal to or less than normal load current.
Only one of these options may be selected in any execution of the unbalanced network solutions.
The selected option applies to all dc lines and FACTS devices in the working case. The default
handling of these devices is to block.
Unbalanced Fault Analysis PSS
E 32.0
Fault Calculation Modeling Assumptions Program Operation Manual
9-28 Siemens Energy, Inc., Power Technologies International
9.4.3 Simplified Fault Calculation Model
A simplified model representation can be used in PSS
E 32.0
Detailed Unbalanced Fault Types Program Operation Manual
9-30 Siemens Energy, Inc., Power Technologies International
Figure 9-11. Phase Closed Series Unbalances
It should be noted that phase impedances will be placed in parallel with any branch which already
exists, in the power flow case, between the selected buses. If the user wishes to use these models
to represent an unbalance in an existing branch, then that branch must be switched out of services
to avoid duplication (see Section 9.7.5).
9.5.3 Line Faults
The inter sequence solution method used in PSS
E 32.0
Preparing Sequence Network for Unbalanced Network Solution Program Operation Manual
9-32 Siemens Energy, Inc., Power Technologies International
9.6 Preparing Sequence Network for Unbalanced Network
Solution
Activity SEQD
The sequence network set up activity SEQD prepares the working case for the unbalanced network
solution activity SCMU or the separate pole circuit breaker duty activity SPCB. This process
involves taking the positive sequence network (i.e., the power flow case) and the various sequence
data arrays defining the negative and zero sequence networks, and setting up the SEQD temporary
file in the form required by activities SCMU and SPCB. Activity SEQD does not modify the contents
of the working case itself.
If sequence data has not been read into the working case via activity RESQ, an appropriate error
message is printed and activity SEQD is terminated.
If any unblocked dc lines or in-service FACTS devices are present in the working case, the user
must specify their treatment:
Block and ignore
Convert to constant admittance load
If dc lines and FACTS devices are to be represented as load, the apparent ac system complex loads
are converted to positive sequence constant admittance load at the buses at which these quantities
are injected into the ac system during normal power flow work. In the negative and zero sequence
networks, dc lines and series FACTS devices are represented as open circuits.
Only one of these options may be selected in any execution of SEQD and the unbalanced network
solutions which follow. The selected option applies to all dc lines and FACTS devices in the working
case. The default handling of these devices is to block.
If the actual positive sequence impedance of any transformer in the working case differs from its
nominal value (refer to Transformer Impedance Correction Tables), the user must specify the treat-
ment of the zero sequence impedance of all such transformers.
If transformer impedance is applied to zero correction, the zero sequence impedance of each such
transformer is scaled by the same factor as is its positive sequence impedance. Otherwise, all zero
sequence transformer impedances are left at their nominal values (i.e., the values entered in activ-
Run Activity SEQD - GUI
Fault > Setup network for unbalanced solution (SEQD)
[Setup Network for Unbalanced Solution]
Run Line Mode Activity SEQD - CLI
ACTIVITY?
>>SEQD
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 9-33
PSS
E 32.0
Preparing Sequence Network for Unbalanced Network Solution Program Operation Manual
9-34 Siemens Energy, Inc., Power Technologies International
Activity SEQD performs the following computations on the working case:
1. All positive sequence loads are converted to fixed shunt admittances on the basis of the
voltage at each load bus in the working case. This is functionally equivalent to the use of
activity CONL in switching study work.
2. All negative sequence loads, except those for which the user has specified a non-zero nega-
tive sequence shunt load (refer to Negative Sequence Shunt Load Data), are set equal to
the positive sequence values calculated in (1) above.
3. All generator positive sequence sources are initialized and fixed to correspond to their
generator terminal bus conditions in the working case. This is functionally equivalent to the
use of activity CONG in switching study work. This step is performed unless generators
have previously been converted; refer to Application Notes.
4. An ordering for the positive and negative sequence networks is determined and the stan-
dard summary of activity ORDR is printed at the Progress tab. This is functionally
equivalent to the use of activity ORDR in switching study work.
5. The positive and negative sequence admittance matrices are constructed and factorized. In
switching study work this function is handled by activity FACT.
6. The zero sequence network is ordered and the standard summary is printed.
7. The zero sequence network admittance matrix is constructed and factorized.
If, in the process of building the sequence network admittance matrices, isolated buses are
detected, they generate an alarm. Isolated buses in the positive and negative sequence networks
indicate an improperly specified power flow case. Isolated buses in the zero sequence network,
although they have generated alarms, are permitted and require no special treatment. When the
fault analysis warning option is disabled (refer to Section 3.3.3 and activity OPTN), the isolated bus
tabulations are suppressed. In either case, the total number of isolated buses in the sequence
networks is tabulated.
Following completion of the processing of the zero sequence network, any three-winding trans-
formers with two windings in-service and one winding out-of-service are tabulated (refer to Zero
Sequence Transformer Data). The user should verify that the zero sequence impedances and
connection codes of the two in-service windings result in the proper zero sequence modeling of
such three-winding transformers.
Activity SEQD is called without being specifically selected during the execution of activity ASCC and
during calculation and application of unbalanced bus fault and of branch unbalance.
The isolated bus summaries may be terminated by entering the AB interrupt control code.
Siemens Energy, Inc., Power Technologies International 9-35
PSS
E 32.0
Preparing Sequence Network for Unbalanced Network Solution Program Operation Manual
9-36 Siemens Energy, Inc., Power Technologies International
If generators are converted when activity SEQD is selected, the generator conversion calculation
of activity SEQD is bypassed, and the results of the prior execution of activity CONG are used. This
is the case, for example, when an equivalent has been constructed (with activity SCEQ), which
requires the prior execution of activity CONG with ZPOS generator conversion. Similarly, if the char-
acterization of generators using ZSORCE rather than ZPOS was appropriate for a fault analysis
scenario, activity CONG should be executed prior to selecting activity SEQD.
Because activity SEQD builds the sequence network admittance matrices corresponding to the
system in the working case, it follows that it must be re-executed before entering activity SCMU any
time these matrices change, different bus boundary conditions are imposed, or a new system repre-
sentation is brought into the working case. Because activity SEQD prepares the SEQD temporary
file for unbalanced network solutions, it also needs to be re-executed whenever, in the midst of an
unbalanced network study, some other PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-38 Siemens Energy, Inc., Power Technologies International
Figure 9-13. Unbalances Modeled in Activity SCMU
9.7.2 Bus Faults
Bus faults are applied simply by instructing activity SCMU to apply the L-G and L-L-G unbalances,
singly or together at the bus, with the appropriate values of the fault impedances Z
F
and Z
G
(see
Figure 9-13). For example, a line-to-line fault may be applied by selecting the L-L-G unbalance with
infinite impedance specified for Z
G
(i.e., the default value). As a second example, a three phase
fault may be applied by selecting the L-G unbalance on phase one (i.e., A) with Z
F
= 0.0+j0.0
together with the L-L-G unbalance excluding phase one with both Z
F
and Z
G
specified as 0.0+j0.0.
Specifying this condition has been automated by including a special unbalance code for a three
phase fault. It automatically applies both the second L-G and second L-L-G faults at the designated
bus, with all fault impedances set to 0.0+j0.0.
The user must specify the faulted bus. In the case of the L-G unbalance, the user specifies the
faulted phase and the fault impedance; phases one, two and three designate the A, B, and C
phases, respectively. In the case of the L-L-G unbalance, the user specifies the unfaulted phase
and the fault impedances Z
F
and Z
G
. Note again that fault impedances (R + jX) are specified and
that both resistance and reactance must be entered. Fault impedances are specified in per unit of
base impedance.
9.7.3 Line Faults
The intersequence solution method of activity SCMU can apply faults only at buses. The application
of a line fault, therefore, requires the insertion of a dummy bus in the line that is to be subjected to
the line fault. The introduction of dummy buses and rerouting of branches may be handled manually
in the working case before executing activity SEQD. However, activity SCMU provides for the
temporary addition of the required dummy buses and automates the rerouting of branches to the
dummy buses and splitting of the zero sequence mutual couplings on either side of the faulted
dummy bus.
In the application of the fault slider, the line may be represented in two ways: with both ends closed
or with one end opened. In either of these two topologies, one of the following may be applied at
any point along the line:
1. The second L-G fault.
2. The second L-L-G fault.
Z
F
L-G Fault
Z
G
L-L-G Fault
Z
F
In-Line Fault
Open End Fault Two Phases Closed One Phase Closed
Z
F
L-G,
L-L-G, or
3-| Fault
L-G,
L-L-G, or
3-| Fault
Siemens Energy, Inc., Power Technologies International 9-39
PSS
E is dimen-
sioned. In addition, except for the case of a line end fault at the opened end of a line, the following
conditions must be met:
1. The number of branches in the working case must be less than the maximum number for
which PSS
E is dimensioned.
2. The geographical B factors, BIJ1, BIJ2, BKL1, and BKL2, must have been properly specified
for any zero sequence mutual couplings involving the branch (refer to Zero Sequence
Mutual Impedance Data).
The user specifies the branch on which the fault slider is to be imposed. For the case of one end of
a branch opened, a non-transformer branch, a two-winding transformer, or a three-winding trans-
former may be designated. A non-transformer branch or a two-winding transformer is specified by
keeping the default value or entering a zero as the third bus identifier; a three-winding transformer
is designated by specifying the three buses it connects.
In the case of one end of the branch opened, the user specifies the opened end and, except for a
three-winding transformer, the fault location on the line. The fault location is specified by specifying
the fraction of the line between the closed end and the fault point (A factor); the proper designation
is a number greater than zero and less than or equal to one (one would indicate a line end fault).
For a two-winding transformer, an A factor value of one must be specified.
For the case of both ends of the branch closed, the user specifies the fault location by entering the
fraction of the line between the from bus as entered above and the fault point; the number entered
must be greater than zero and less than one.
The user specifies the type of fault (refer to Bus Faults).
Only one line fault may be imposed on the network in any given execution of activity SCMU. Other
bus faults and the phase closed unbalances may be simultaneously applied.
For an in-line slider fault with both ends closed, the faulted line may not be a transformer, and it may
not be open in the zero sequence (i.e., its zero sequence impedance must be non-zero). In the case
of one end opened, the fault must be applied at the line end position if the branch is a transformer.
The summary output for either of the line faults is identical in form to that for bus faults. The faulted
dummy bus is listed as bus 999999 with the name DUMMYBUS. For the one end opened case, the
base voltage of the dummy bus is taken to be the same as the opened end bus. For the case of
both ends closed, the base voltage of the dummy bus will be that of one of the two buses involved.
In the case of one end opened with the fault location other than at the opened end, the opened end
dummy bus is listed as bus 999998 with the name STUB END and the base voltage of the original
bus at the opened end of the line.
Unbalanced Fault Analysis PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-40 Siemens Energy, Inc., Power Technologies International
9.7.4 Branch with One Open End
For the case of one end of a branch opened, a non transformer branch, a two-winding transformer,
or a three-winding transformer may be designated. A non transformer branch or a two-winding
transformer is specified by identifying the two associated buses. A three-winding transformer is
designated by specifying the three buses it connects.
With one end of the branch opened, the user designates the opened end and, except for a three-
winding transformer, the fault location on the branch. For a non-transformer branch, the fault loca-
tion is specified by specifying the fraction of the line between the closed end and the fault point, as
for the slider. The proper designation is a number greater than zero and less than or equal to one
(one would indicate a line end fault). For a two-winding transformer, the value of one must be spec-
ified. For a three-winding transformer, the user can select the open point at any of the three buses
to which the transformer is connected.
In the case of one end opened with the fault location other than at the opened end, the opened end
dummy bus is listed as bus 999998 with the name STUB END and the base voltage of the original
bus at the opened end of the line.
Note that the fault type can be a line-to-ground, a line-to-line-to ground or a 3-phase fault.
9.7.5 Phase Closed Unbalances
The single and double phase closed unbalances of activity SCMU place series elements of the
designated phase impedance between designated buses in the selected phases. The user speci-
fies the pair of buses involved, either the phase to be closed (for the single phase closed unbalance)
or the opened phase (for the double phase closed unbalance), and the phase impedance of the
closed phase(s).
If it is intended to open one or two phases of a branch which already exists, that branch must be
taken out of service in order to be replaced by the unbalance model.
Following the unbalance specification process, a warning message is printed if there are already
any in-service branches between the designated buses. In this case the new series branch, of
which only one or two phases are closed, is placed in parallel with those branches that are already
present. It is the users responsibility to ensure that the working case is in a state such that the appli-
cation of the phase closed unbalance produces the desired overall condition.
The summary output for each of the phase closed unbalances consists of the bus voltage block for
each of the two buses and the branch current block for the unbalance only.
9.7.6 Pre-Calculation Network Setup
The normal sequencing of activities in preparing for fault analysis work is:
1. Set up the positive sequence network at whatever level of detail is required.
2. Append the required sequence data to the power flow case (Section 9.2).
3. Select the unbalances to be simulated and start the calculation.
When the calculation is initiated, the first step in the process is the setting up of the sequence
networks. This involves the preparation of the power flow case for the unbalanced network solution
(as well as for the Separate Pole Circuit Breaker simulation discussed in Section 9.14)
Siemens Energy, Inc., Power Technologies International 9-41
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-42 Siemens Energy, Inc., Power Technologies International
Figure 9-14. Generator Conversion to Norton Equivalent for Fault
Calculations
Figure 9-15. Summary from Network Ordering Prior to Fault Calculations
P+ jQ t:1
~
E
source
ZSORCE or ZPOS
Z
tran
1:GTAP
t -u:1 Z
Z
neg
Z
tran
1:GTAP
t -u:1 Z
Z
zero
Z
tran
1:GTAP
Transf. zero
seq. connections
Power Flow Setup
Unbalanced Fault
Analysis Setup
N
e
g
a
t
i
v
e
S
e
q
u
e
n
c
e
Z
e
r
o
S
e
q
u
e
n
c
e
P
o
s
i
t
i
v
e
S
e
q
u
e
n
c
e
Augment Positive Sequence model
and Append Sequence Data
Siemens Energy, Inc., Power Technologies International 9-43
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-44 Siemens Energy, Inc., Power Technologies International
The following blocks of output are included:
1. Fault type and bus(es) involved.
2. Bus voltages for the bus at which the unbalance is applied. The first line of each bus voltage
block gives the bus zero, positive and negative sequence voltages as well as three times
the zero sequence voltage, and the second line gives the bus phase voltages. When the per
unit option is enabled, values are in per unit of rated line to ground voltage. The phase volt-
ages are line to neutral values. For the phase closed unbalances, the bus voltage block is
printed for both of the buses involved.
3. For the L-G and L-L-G faults, series branch currents flowing in each branch (including any
generator contributions) connected to the faulted node. All currents are tabulated as flowing
into the faulted node and include the effects of line charging capacitance, line connected
shunt admittances, and transformer magnetizing admittance. When the per unit option is
enabled, currents are expressed in per unit of base phase current. The first line gives
sequence components of current as well as three times the zero sequence current, and the
second line gives the phase currents. For non-transformer branches and for two-winding
transformers, the number and name of the bus at the other end of the branch is printed,
along with the circuit identifier; for three-winding transformers, the output line contains the
winding number, the transformer circuit identifier and the transformer name. For the phase
closed unbalances, the only branch series currents tabulated are those represented by the
unbalance.
4. For the L-G and L-L-G faults, the algebraic sum of contributions of all elements tabulated in
(3). The format of these currents is the same as for the series branch currents. This is the
total current apparently flowing to ground at the bus, and it includes any load and fixed shunt
connected to the bus, fault current, and the ac side current of any unblocked dc line or
FACTS device.
5. For the L-G and L-L-G faults, a value of contributions equivalent positive sequence admit-
tance, expressed in rectangular form, in both per unit relative to system base values and in
MVA. This quantity is computed from the sum of contributions in (4) and thus includes any
load, fixed shunt and unblocked dc line and FACTS device elements connected to the bus.
Furthermore, this equivalent admittance is valid only in the case of single ground faults. In
the case where there are no dc line or FACTS device effects included in this admittance, and
only this single unbalance was applied, this shunt admittance in MVA, may be entered as a
shunt replacing the load and shunt elements at the bus, to give the correct positive
sequence equivalent representation of this fault in the dynamic simulation activities.
6. For the L-G and L-L-G faults, the current flowing to ground at the bus exclusive of any fault
current. The format of these currents is the same as in (3) and (4) above, and they include
any load and shunt current at the bus as well as the ac side current of any unblocked dc line
or FACTS device. In the zero sequence, only the load and shunt current is output here;
specifically, the zero sequence ground ties created by grounded transformer windings are
not shown here but are included in the branch contribution output of (3) above. Load and
shunt current output is suppressed if the three sequence shunt and load admittances are all
zero.
7. For the L-G and L-L-G faults, when no phase closed unbalances are applied and only one
bus is involved in the ground faults, fault current is calculated and tabulated in a format
similar to (4) above, and positive sequence equivalent fault admittance is listed in a format
Siemens Energy, Inc., Power Technologies International 9-45
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-46 Siemens Energy, Inc., Power Technologies International
The following blocks of output are included:
1. Fault type and bus(es) involved.
2. Bus voltages for the bus at which the unbalance is applied. The first line of each bus voltage
block gives the bus zero, positive and negative sequence voltages as well as three times
the zero sequence voltage, and the second line gives the bus phase voltages. When the per
unit option is enabled, values are in per unit of rated line to ground voltage. The phase volt-
ages are line to neutral values. For the phase closed unbalances, the bus voltage block is
printed for both of the buses involved.
3. For the L-G and L-L-G faults, series branch currents flowing in each branch (including any
generator contributions) connected to the faulted node. All currents are tabulated as flowing
into the faulted node and include the effects of line charging capacitance and line connected
shunt admittances. When the per unit option is enabled, currents are expressed in per unit
of base phase current. The first line gives sequence components of current as well as three
times the zero sequence current, and the second line gives the phase currents. For non
transformer branches and for two-winding transformers, the number and name of the to bus
is printed, along with the circuit identifier; for three-winding transformers, the output line
contains the winding number, the transformer circuit identifier and the transformer name. For
the phase closed unbalances, the only branch series currents tabulated are those repre-
sented by the unbalance.
4. For the L-G and L-L-G faults, the algebraic sum of contributions of all elements tabulated in
(3). The format of these currents is the same as for the series branch currents. This is the
total current apparently flowing to ground at the bus, and it includes any load connected to
the bus, fault current, and the ac side current of any unblocked dc line or FACTS device.
5. For the L-G and L-L-G faults, a value of contributions equivalent positive sequence admit-
tance is expressed in per unit, rectangular form, relative to system base values. This
quantity is computed from the sum of contributions in (4) and thus includes any load and
unblocked dc line and FACTS device elements connected to the bus. Furthermore, this
equivalent admittance is valid only in the case of single ground faults. In the case where
there are no dc line or FACTS device effects included in this admittance, and only this single
unbalance was applied, this shunt admittance, multiplied by system base MVA, may be
entered as a shunt replacing the load and shunt elements at the bus, to give the correct posi-
tive sequence equivalent representation of this fault in the dynamic simulation activities.
6. For the L-G and L-L-G faults, the current flowing to ground at the bus exclusive of any fault
current. The format of these currents is the same as in (3) and (4) above, and they include
any load and shunt current at the bus as well as the ac side current of any unblocked dc line
or FACTS device. In the zero sequence, only the shunt load is output here; specifically, the
zero sequence ground ties created by grounded transformer windings are not shown here
but are included in the branch contribution output of (3) above. Load and shunt current
output is suppressed if the three sequence shunt and load admittances are all zero.
7. For the L-G and L-L-G faults, when no phase closed unbalances are applied and only one
bus is involved in the ground faults, fault current is calculated and tabulated in a format
similar to (4) above, and positive sequence equivalent fault admittance is listed in a format
similar to (5) above. This admittance, multiplied by system base MVA, would be added to
any shunt at the bus to represent this fault in the dynamic simulation activities.
Siemens Energy, Inc., Power Technologies International 9-47
PSS
E
3
2
.
0
P
e
r
f
o
r
m
i
n
g
F
a
u
l
t
A
n
a
l
y
s
i
s
u
n
d
e
r
U
n
b
a
l
a
n
c
e
C
o
n
d
i
t
i
o
n
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 9-17. Summary Output at Bus 151 with L-G Faults at Buses 151 in Power Flow Case savnw.sav
600 Mvar Shunt at bus 151
Sum of Contributions without the 600 Mvar Shunt
Siemens Energy, Inc., Power Technologies International 9-49
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-50 Siemens Energy, Inc., Power Technologies International
When output is directed to the users terminal, a summary description of each active unbalance is
printed at the top of the first page of output. Otherwise, the unbalance summary is printed on each
page of output.
9.7.11 Observation of Transformer Currents
Grounded wye-delta transformers pose a difficulty in unbalanced fault analysis because they
behave as a shunt path to ground in the zero-sequence, while being series paths in the positive and
negative sequences. There is a distinction between the transformers symmetrical component
equivalent circuits and the actual arrangements of its primary, secondary, and neutral leads.
Consider the currents flowing in the leads of a wye-delta transformer as shown in Figure 9-18. The
wye-connected winding allows zero-sequence current to flow into the transformer leads and thence
to ground via the neutral grounding strap. While the wye-connected winding is certainly a path to
ground, observations at the leads that feed this winding see the zero-sequence current just as if it
were a series current flowing to the bus at the other side. This zero-sequence current in the trans-
former leads must be recognized in calculations of the phase values of the lead currents.
Figure 9-18. Lead Current Flowing Into and Out of a Wye-Delta Transformer
Primary
Leads
Secondary
Leads
I
p1
I
p2
I
p0
I
s1
I
s2
3I
p0
3I
p0
Grounding Strap
Neutral Lead
Tank
Siemens Energy, Inc., Power Technologies International 9-51
PSS
E. When the winding type code approach is used, the implied bus representa-
tion is as shown in Figure 9-19c.
Unbalanced Fault Analysis PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-52 Siemens Energy, Inc., Power Technologies International
Figure 9-19. Transformer Zero-Sequence Currents Appearing in Alternative Network
Representations of the Transformer
Line A
Line B
I
r
I
f
Shunt Reactor
Transformer
I
t
1:t
a. Bus with Grounding via Transformer, Shunt Reactor, and Fault
b. Bus Setup with Transformer Treated as
Bus Ground Path
c. Bus Setup with Transformer Modeled
via Winding Type Codes
I
fo
I
ro
I
to
+
B B
r
1
Z
to
t
2
-------------- + =
I
fo
I
ro
B B
r
=
Z
I
to
1:t
Z
to
Siemens Energy, Inc., Power Technologies International 9-53
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-54 Siemens Energy, Inc., Power Technologies International
9.7.12 Working with a Two-Wire System
PSS
E includes an option, in the detailed unbalanced fault analysis and the automatic sequencing
fault analysis (Section 9.9), to handle certain two- and one-phase systems. This option was imple-
mented primarily to handle certain European electric traction systems having a primary
transmission system of two phases at 180 displacement feeding a single-phase catenary system.
The basic system connections in this system are shown in Figure 9-21, but other two- and one-
phase systems can be handled by the appropriate setup of the sequence network models.
Figure 9-21. Two-Phase System Configuration for Railway Application
The two-phase system modelling assumption is established with the Short circuit phase modeling
run-time option (Section 3.3.3 and activity OPTN). This option allows the selection of two-phase
instead of the conventional three-phase mode. Selecting the two-phase option has the following
effects:
The symmetrical component < a > operator becomes (1+j0), and the negative
sequence is ignored, giving
The base voltage is taken to be the line-to-line voltage at base conditions, and the base
current is taken to be the corresponding line current so that
Line-to-ground voltages in kV are calculated as
V
LG
= 0.5(V
LL base
v
pu
Phase currents in amperes are calculated as
I
p
= I
L base
I
pu
where v
pu
and I
pu
are the per-unit bus voltage and branch current, respectively.
132 kV 12 kV
Secondary of
Generator Step-Up
Transformer
Load
Transformer
i
0
i
1
= 1/2
1 1
1 -1
i
a
i
b
MVA
base
V
LL base
V
2
LL base
2MVA
base
I
L base
=
Z
LG base
=
Siemens Energy, Inc., Power Technologies International 9-55
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-56 Siemens Energy, Inc., Power Technologies International
Figure 9-22. Behavior of Transformer with Secondary Windings Parallel to Single-Phase
Load
The modeling of the load transformer in PSS
E by connection
codes of 2.
i
1p
i
1p
i
1s
2
--------
i
1s
2
--------
i
1s
i
1s
i
0p
i
0p
i
0s
i
0s
0.0
2i
0p
a. Positive-Sequence Behavior
b. Zero-Sequence Behavior
Siemens Energy, Inc., Power Technologies International 9-57
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-58 Siemens Energy, Inc., Power Technologies International
9.7.15 Secondary Circuits
The load on the secondary side of the transformer shown in Figure 9-21 must be modeled
according to its physical connections. Straightforward possibilities are shown in Figure 9-24.
Grounding of one phase of a load does not create a zero-sequence path to ground. A ground must
exist inside the load device in order for it to carry a zero-sequence current; such internal ground
connections exist in the center-tapped load (Figure 9-24a) and in the transmission line section
(Figure 9-24d) as a result of its shunt charging capacitances.
Siemens Energy, Inc., Power Technologies International 9-59
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-60 Siemens Energy, Inc., Power Technologies International
9.7.16 Faults on a Two-Phase System
Faults on the two phase system may be represented by the standard PSS
E
3
2
.
0
U
n
b
a
l
a
n
c
e
d
F
a
u
l
t
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
e
r
f
o
r
m
i
n
g
F
a
u
l
t
A
n
a
l
y
s
i
s
u
n
d
e
r
U
n
b
a
l
a
n
c
e
C
o
n
d
i
t
i
o
n
Figure 9-26. Raw Data Files for Two-Phase System
0, 100.00 / PSSE-30.0 THU, AUG 05 2004 11:22
SMALL TWO PHASE EXAMPLE
100,'GEN-1 ', 10.0000,3, 0.000, 0.000, 1, 1,1.00000, 0.0000, 1
200,'HYDRO ', 132.0000,1, 0.000, 0.000, 1, 1,0.98277, -4.8404, 1
300,'WEST ', 132.0000,1, 0.000, 0.000, 1, 1,0.97469, -5.9957, 1
330,'EAST-LO ', 12.0000,1, 0.000, 0.000, 1, 1,0.96723, -7.2034, 1
400,'EAST ', 132.0000,1, 0.000, 0.000, 1, 1,0.97225, -6.5672, 1
440,'WEST-LO ', 12.0000,1, 0.000, 0.000, 1, 1,0.96527, -7.6463, 1
550,'MAIN-LO ', 12.0000,1, 0.000, 4.000, 1, 1,0.95002, -9.6922, 1
0 / END OF BUS DATA, BEGIN LOAD DATA
330,'1 ',1, 1, 1, 5.000, 2.000, 0.000, 0.000, 0.000, 0.000, 1
440,'1 ',1, 1, 1, 5.000, 2.000, 0.000, 0.000, 0.000, 0.000, 1
550,'1 ',1, 1, 1, 15.000, 8.000, 0.000, 0.000, 0.000, 0.000, 1
0 / END OF LOAD DATA, BEGIN GENERATOR DATA
100,'3 ', 25.130, 6.283, 20.000, 0.000,1.00000, 200, 30.000, 0.00000, 0.20000, 0.00000, 0.00000,1.00000,1, 1.0, 9999.000, -9999.000,
1,1.0000
0 / END OF GENERATOR DATA, BEGIN BRANCH DATA
200, 300,'1 ', 0.01500, 0.15000, 0.02500, 40.00, 40.00, 40.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
200, 400,'1 ', 0.02500, 0.25000, 0.04000, 40.00, 40.00, 40.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
330, 550,'1 ', 0.05000, 0.50000, 0.00000, 15.00, 15.00, 15.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
440, 550,'1 ', 0.05000, 0.50000, 0.00000, 15.00, 15.00, 15.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
0 / END OF BRANCH DATA, BEGIN TRANSFORMER DATA
200, 100, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 1,1.0000
0.00000, 0.33000, 100.00
1.00000, 0.000, 0.000, 35.00, 35.00, 35.00, 1, 200, 1.15000, 0.85000, 1.03000, 1.01000, 49, 0, 0.00000, 0.00000
1.00000, 0.000
330, 300, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 1,1.0000
0.00000, 0.15000, 100.00
1.00000, 0.000, 0.000, 20.00, 20.00, 20.00, 1, 330, 1.15000, 0.85000, 1.00000, 0.98000, 49, 0, 0.00000, 0.00000
1.00000, 0.000
440, 400, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 1,1.0000
0.00000, 0.15000, 100.00
1.00000, 0.000, 0.000, 20.00, 20.00, 20.00, 1, 440, 1.15000, 0.85000, 1.00000, 0.98000, 49, 0, 0.00000, 0.00000
1.00000, 0.000
0 / END OF TRANSFORMER DATA, BEGIN AREA DATA
0 / END OF AREA DATA, BEGIN TWO-TERMINAL DC DATA
0 / END OF TWO-TERMINAL DC DATA, BEGIN VSC DC LINE DATA
0 / END OF VSC DC LINE DATA, BEGIN SWITCHED SHUNT DATA
0 / END OF SWITCHED SHUNT DATA, BEGIN IMPEDANCE CORRECTION DATA
0 / END OF IMPEDANCE CORRECTION DATA, BEGIN MULTI-TERMINAL DC DATA
0 / END OF MULTI-TERMINAL DC DATA, BEGIN MULTI-SECTION LINE DATA
0 / END OF MULTI-SECTION LINE DATA, BEGIN ZONE DATA
0 / END OF ZONE DATA, BEGIN INTER-AREA TRANSFER DATA
0 / END OF INTER-AREA TRANSFER DATA, BEGIN OWNER DATA
0 / END OF OWNER DATA, BEGIN FACTS DEVICE DATA
0 / END OF FACTS DEVICE DATA
a. Power Flow Raw Data
Unbalanced Fault Analysis PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-62 Siemens Energy, Inc., Power Technologies International
Figure 9-26. (Cont.) Raw Data Files for Two-Phase System
0 / PSSE-30.0 THU, AUG 05 2004 11:24
100,'3 ', 0.00000, 0.20000
0 / END OF POSITIVE SEQ. MACHINE IMPEDANCE DATA, BEGIN NEGATIVE SEQ. MACHINE DATA
100,'3 ', 0.00000, 0.20000
0 / END OF NEGATIVE SEQ. MACHINE IMPEDANCE DATA, BEGIN ZERO SEQ. MACHINE DATA
100,'3 ', 0.00000, 0.00000
0 / END OF ZERO SEQ. MACHINE IMPEDANCE DATA, BEGIN NEGATIVE SEQ. SHUNT DATA
0 / END OF NEGATIVE SEQ. SHUNT DATA, BEGIN ZERO SEQ. SHUNT DATA
0 / END OF ZERO SEQ. SHUNT DATA, BEGIN ZERO SEQ. NON-TRANSFORMER BRANCH DATA
200, 300,'1 ', 0.02000, 0.30000, 0.04000, 0.00000, 0.00000, 0.00000, 0.00000
200, 400,'1 ', 0.04000, 0.45000, 0.06500, 0.00000, 0.00000, 0.00000, 0.00000
330, 550,'1 ', 0.04000, 0.80000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000
440, 550,'1 ', 0.04000, 0.80000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000
0 / END OF ZERO SEQ. NON-TRANSFORMER BRANCH DATA, BEGIN ZERO SEQ. MUTUAL DATA
0 / END OF ZERO SEQ. MUTUAL DATA, BEGIN ZERO SEQ. TRANSFORMER DATA
100, 200, 0,'1 ', 2, 0.00000, 0.00000, 0.00000, 0.33000
300, 330, 0,'1 ', 3, 0.00000, 0.00000, 0.00000, 0.15000
400, 440, 0,'1 ', 3, 0.00000, 0.00000, 0.00000, 0.15000
0 / END OF ZERO SEQ. TRANSFORMER DATA, BEGIN ZERO SEQ. SWITCHED SHUNT DATA
0 / END OF ZERO SEQ. SWITCHED SHUNT DATA
Connection codes to
represent parallel-
secondary transformer
connections
b. Sequence Raw Data
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
9
-
6
3
P
S
S
E
3
2
.
0
U
n
b
a
l
a
n
c
e
d
F
a
u
l
t
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
e
r
f
o
r
m
i
n
g
F
a
u
l
t
A
n
a
l
y
s
i
s
u
n
d
e
r
U
n
b
a
l
a
n
c
e
C
o
n
d
i
t
i
o
n
Figure 9-27. Data Listings for Two-Phase System
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE THU, AUG 05 2004 11:30
SMALL TWO PHASE EXAMPLE BUS DATA
BUS# X-- NAME --X BASKV CODE LOADS VOLT ANGLE S H U N T AREA ZONE OWNER
100 GEN-1 10.000 3 0 1.0000 0.0 0.0 0.0 1 1 1
200 HYDRO 132.00 1 0 0.9828 -4.8 0.0 0.0 1 1 1
300 WEST 132.00 1 0 0.9747 -6.0 0.0 0.0 1 1 1
330 EAST-LO 12.000 1 1 0.9672 -7.2 0.0 0.0 1 1 1
400 EAST 132.00 1 0 0.9723 -6.6 0.0 0.0 1 1 1
440 WEST-LO 12.000 1 1 0.9653 -7.6 0.0 0.0 1 1 1
550 MAIN-LO 12.000 1 1 0.9500 -9.7 0.0 4.0 1 1 1
BUS# X-- NAME --X BASKV ID CD ST PSI MVA-LOAD CUR-LOAD Y - LOAD AREA ZONE OWNER
330 EAST-LO 12.000 1 1 1 1.000 5.0 2.0 0.0 0.0 0.0 0.0 1 1 1
440 WEST-LO 12.000 1 1 1 1.000 5.0 2.0 0.0 0.0 0.0 0.0 1 1 1
550 MAIN-LO 12.000 1 1 1 1.000 15.0 8.0 0.0 0.0 0.0 0.0 1 1 1
X----- REMOTE BUS ------X
BUS# X-- NAME --X BASKV COD MCNS PGEN QGEN QMAX QMIN VSCHED VACT. PCT Q BUS# X-- NAME --X BASKV
100 GEN-1 10.000 3 1 25.1 6.3 20.0 0.0 1.0000 0.9828 1.0 200 HYDRO 132.00
BUS# X-- NAME --X BASKV CD ID ST PGEN QGEN QMAX QMIN PMAX PMIN OWN FRACT OWN FRACT MBASE Z S O R C E X T R A N GENTAP
100 GEN-1 10.000 3 3 1 25.1 6.3 20.0 0.0 9999.0-9999.0 1 1.000 30.0 0.0000 0.2000
X------ FROM BUS -------X X------- TO BUS --------X Z S
BUS# X-- NAME --X BASKV BUS# X-- NAME --X BASKV CKT LINE R LINE X CHRGING I T RATEA RATEB RATEC LENGTH OWNR FRACT OWNR FRACT
200 HYDRO 132.00* 300 WEST 132.00 1 0.01500 0.15000 0.02500 1 40.0 40.0 40.0 0.0 1 1.000
200 HYDRO 132.00* 400 EAST 132.00 1 0.02500 0.25000 0.04000 1 40.0 40.0 40.0 0.0 1 1.000
330 EAST-LO 12.000* 550 MAIN-LO 12.000 1 0.05000 0.50000 0.00000 1 15.0 15.0 15.0 0.0 1 1.000
440 WEST-LO 12.000* 550 MAIN-LO 12.000 1 0.05000 0.50000 0.00000 1 15.0 15.0 15.0 0.0 1 1.000
X------ FROM BUS -------X X------- TO BUS --------X XFRMER S W M C C A C T U A L MAGNETIZING Y N O M I N A L
BUS# X-- NAME --X BASKV BUS# X-- NAME --X BASKV CKT X-- NAME --X T 1 T Z M R 1-2 X 1-2 W1BASE MAG1 MAG2 TBL R 1-2 X 1-2
100 GEN-1 10.000 200 HYDRO 132.00 1 1 T T 1 1 0.00000 0.33000 100.0 0.00000 0.00000 0
300 WEST 132.00 330 EAST-LO 12.000 1 1 T T 1 1 0.00000 0.15000 100.0 0.00000 0.00000 0
400 EAST 132.00 440 WEST-LO 12.000 1 1 T T 1 1 0.00000 0.15000 100.0 0.00000 0.00000 0
X------ FROM BUS -------X X------- TO BUS --------X C
BUS# X-- NAME --X BASKV BUS# X-- NAME --X BASKV CKT W WINDV1 NOMV1 ANGLE WINDV2 NOMV2 RATEA RATEB RATEC OWNR FRACT OWNR FRACT
100 GEN-1 10.000 200 HYDRO 132.00 1 1 1.00000 0.0000 0.0 1.00000 0.0000 35.0 35.0 35.0 1 1.000
300 WEST 132.00 330 EAST-LO 12.000 1 1 1.00000 0.0000 0.0 1.00000 0.0000 20.0 20.0 20.0 1 1.000
400 EAST 132.00 440 WEST-LO 12.000 1 1 1.00000 0.0000 0.0 1.00000 0.0000 20.0 20.0 20.0 1 1.000
X------ FROM BUS -------X X------- TO BUS --------X W C X---- CONTROLLED BUS ----X
BUS# X-- NAME --X BASKV BUS# X-- NAME --X BASKV CKT 1 W CN RMAX RMIN VMAX VMIN NTPS BUS# X-- NAME --X BASKV CR CX
100 GEN-1 10.000 200 HYDRO 132.00 1 T 1 1 1.15000 0.85000 1.03000 1.01000 49 -200 HYDRO 132.00
300 WEST 132.00 330 EAST-LO 12.000 1 T 1 1 1.15000 0.85000 1.00000 0.98000 49 -330 EAST-LO 12.000
400 EAST 132.00 440 WEST-LO 12.000 1 T 1 1 1.15000 0.85000 1.00000 0.98000 49 -440 WEST-LO 12.000
9
-
6
4
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
U
n
b
a
l
a
n
c
e
d
F
a
u
l
t
A
n
a
l
y
s
i
s
P
S
S
E
3
2
.
0
P
e
r
f
o
r
m
i
n
g
F
a
u
l
t
A
n
a
l
y
s
i
s
u
n
d
e
r
U
n
b
a
l
a
n
c
e
C
o
n
d
i
t
i
o
n
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 9-27. (Cont.) Data Listings for Two-Phase System
BUS# X-- NAME --X BASKV CODE ZERO SEQ SHUNT NEG SEQ SHUNT POS SEQ SHUNT MVA-LOAD CURRENT-LOAD ADMITTANCE-LOAD
100 GEN-1 10.000 3 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000
200 HYDRO 132.00 1 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000
300 WEST 132.00 1 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000
330 EAST-LO 12.000 1 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0500 0.0200 0.0000 0.0000 0.0000 0.0000
400 EAST 132.00 1 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000
440 WEST-LO 12.000 1 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0500 0.0200 0.0000 0.0000 0.0000 0.0000
550 MAIN-LO 12.000 1 0.0000 0.0000 0.0000 0.0000 0.0000 0.0400 0.1500 0.0800 0.0000 0.0000 0.0000 0.0000
BUS# X-- NAME --X BASKV ID CODE ST ZGEN (ZERO) ZGEN (POSITIVE) ZGEN (NEGATIVE) MBASE X T R A N GENTAP
100 GEN-1 10.000 3 3 1 0.00000 0.00000 0.00000 0.20000 0.00000 0.20000 30.0 0.00000 0.00000 1.0000
X------ FROM BUS -------X X------- TO BUS --------X X- POS AND NEG SEQUENCE -X X---- ZERO SEQUENCE -----X
BUS# X-- NAME --X BASKV BUS# X-- NAME --X BASKV CKT ST ZI LINE R LINE X CHARGING LINE R LINE X CHARGING
200 HYDRO 132.00 300 WEST 132.00 1 1 0.01500 0.15000 0.02500 0.02000 0.30000 0.04000
200 HYDRO 132.00 400 EAST 132.00 1 1 0.02500 0.25000 0.04000 0.04000 0.45000 0.06500
330 EAST-LO 12.000 550 MAIN-LO 12.000 1 1 0.05000 0.50000 0.00000 0.04000 0.80000 0.00000
440 WEST-LO 12.000 550 MAIN-LO 12.000 1 1 0.05000 0.50000 0.00000 0.04000 0.80000 0.00000
X------ FROM BUS -------X X------- TO BUS --------X S W C X-- POS & NEG --X X-------- ZERO SEQUENCE --------X X- WINDING1 -X WINDNG2 MAGNETIZING Y
BUS# X-- NAME --X BASKV BUS# X-- NAME --X BASKV CK T 1 C R X R X RGROUND XGROUND RATIO ANGLE RATIO G B
100 GEN-1 10.000 200 HYDRO 132.00 1 1 T 2 0.00000 0.33000 0.00000 0.33000 0.0000 0.0000 1.00000 0.0 1.00000 0.0000 0.0000
300 WEST 132.00 330 EAST-LO 12.000 1 1 T 3 0.00000 0.15000 0.00000 0.15000 0.0000 0.0000 1.00000 0.0 1.00000 0.0000 0.0000
400 EAST 132.00 440 WEST-LO 12.000 1 1 T 3 0.00000 0.15000 0.00000 0.15000 0.0000 0.0000 1.00000 0.0 1.00000 0.0000 0.0000
Capacitor
bank not
grounded
internally
Connection codes reflect center tapped primary/parallel
secondary transformer arrangements
Siemens Energy, Inc., Power Technologies International 9-65
PSS
E option settings:
50 Hz base frequency.
Two-phase solution mode.
Polar output of fault analysis results.
Figure 9-28. Initial Condition Power Flow Solution for Two-Phase Sample System
Figure 9-28 shows output from activity SCOP corresponding directly to Figure 9-27, with no fault
applied. In this report the negative sequence and b-phase fields have no significance. The a and c
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE TUE, OCT 08 1991 14:58
SMALL TWO PHASE EXAMPLE RATING
SYSTEM FOR PROGRAM APPLICATION GUIDE SET A
BUS 100 GEN-1 10.0 AREA CKT MW MVAR MVA %I 1.0000PU 0.00 100
GENERATION 1 25.1 5.5R 25.7 86 10.000KV
TO 200 HYDRO 132 1 1 25.1 5.5 25.7 73 1.0313UN
BUS 200 HYDRO 132 AREA CKT MW MVAR MVA %I 1.0162PU -4.83 200
1 134.13KV
TO 100 GEN-1 10.0 1 1 -25.1 -3.3 25.3 71 1.0313LK
TO 300 WEST 132 1 1 13.3 2.5 13.5 33
TO 400 EAST 132 1 1 11.8 0.8 11.9 29
BUS 300 WEST 132 AREA CKT MW MVAR MVA %I 1.0087PU -5.91 300
1 133.15KV
TO 200 HYDRO 132 1 1 -13.3 -4.8 14.1 35
TO 330 EAST-LOD12.0 1 1 13.3 4.8 14.1 70 0.9937UN
BUS 330 EAST-LOD12.0 AREA CKT MW MVAR MVA %I 0.9955PU -7.04 330
1 11.946KV
TO LOAD-PQ 5.0 2.0 5.4
TO 300 WEST 132 1 1 -13.3 -4.5 14.0 70 0.9937LK
TO 550 MAIN-LOD12.0 1 1 8.3 2.5 8.6 58
BUS 400 EAST 132 AREA CKT MW MVAR MVA %I 1.0066PU -6.45 400
1 132.88KV
TO 200 HYDRO 132 1 1 -11.8 -4.5 12.6 31
TO 440 WEST-LOD12.0 1 1 11.8 4.5 12.6 63 0.9937UN
BUS 440 WEST-LOD12.0 AREA CKT MW MVAR MVA %I 0.9938PU -7.45 440
1 11.926KV
TO LOAD-PQ 5.0 2.0 5.4
TO 400 EAST 132 1 1 -11.8 -4.3 12.6 63 0.9937LK
TO 550 MAIN-LOD12.0 1 1 6.8 2.3 7.2 48
BUS 550 MAIN-LOD12.0 AREA CKT MW MVAR MVA %I 0.9795PU -9.39 550
1 11.754KV
TO LOAD-PQ 15.0 8.0 17.0
TO SHUNT 0.0 -3.8 3.8
TO 330 EAST-LOD12.0 1 1 -8.2 -2.1 8.5 58
TO 440 WEST-LOD12.0 1 1 -6.8 -2.0 7.1 48
Unbalanced Fault Analysis PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-66 Siemens Energy, Inc., Power Technologies International
phase voltage fields show sequence and phase voltages on a line-to-ground basis. The current
values are in terms of per unit line current.
Figure 9-29. Output from Short-Circuit Solution Reporting Corresponding to Figure 9-27
Comparison of the flow into bus 550 from bus 330 in Figures 9-27 and 9-28 and shows:
Received MVA = 8.5
Receiving voltage = 0.9795 per unit = 11.754 kV (L-L) = 5.877 kV (L-G)
Phase current, I
p
, from Figure 9-27, =
Base phase current =
Per-unit phase current, from Figure 9-27, =
Per-unit phase current, from Figure 9-28, = 0.0867 per unit
SEQUENCE /V0/ AN(V0) /V+/ AN(V+) /V-/ AN(V-)
PHASE /VA/ AN(VA) /VB/ AN(VB) /VC/ AN(VC)
550 (P.U.) 0.0000 0.00 0.9795 -9.39 0.0000 0.00
MAIN-LOD12.0 0.9795 -9.39 0.0000 0.00 0.9795 170.61
SEQUENCE /I0/ AN(I0) /I+/ AN(I+) /I-/ AN(I-)
PHASE /IA/ AN(IA) /IB/ AN(IB) /IC/ AN(IC)
TO 330 1 0.0000 0.00 0.0867 155.97 0.0000 0.00
EAST-LOD12.0 0.0867 155.97 0.0000 0.00 0.0867 -24.03
TO 440 1 0.0000 0.00 0.0722 154.05 0.0000 0.00
WEST-LOD12.0 0.0722 154.05 0.0000 0.00 0.0722 -25.95
SUM OF 0.0000 0.00 0.1589 -24.90 0.0000 0.00
CONTRIBUTIONS 0.1589 -24.90 0.0000 0.00 0.1589 155.10
SEQUENCE /V0/ AN(V0) /V+/ AN(V+) /V-/ AN(V-)
PHASE /VA/ AN(VA) /VB/ AN(VB) /VC/ AN(VC)
330 (P.U.) 0.0000 0.00 0.9955 -7.04 0.0000 0.00
EAST-LOD12.0 0.9955 -7.04 0.0000 0.00 0.9955 172.96
SEQUENCE /I0/ AN(I0) /I+/ AN(I+) /I-/ AN(I-)
PHASE /IA/ AN(IA) /IB/ AN(IB) /IC/ AN(IC)
TO 300 1 0.0000 0.00 0.1407 154.13 0.0000 0.00
WEST 132 0.1407 154.13 0.0000 0.00 0.1407 -25.87
TO 550 1 0.0000 0.00 0.0867 -24.03 0.0000 0.00
MAIN-LOD12.0 0.0867 -24.03 0.0000 0.00 0.0867 155.97
SUM OF 0.0000 0.00 0.0541 -28.84 0.0000 0.00
CONTRIBUTIONS 0.0541 -28.84 0.0000 0.00 0.0541 151.16
MVA
V
LL
=
= 723.2 A
8.5E6
11.754E3
MVA
base
V
LL base
= = 8333.3 A
100E6
12E3
723.2
= 0.08605 per unit
8333.3
Siemens Energy, Inc., Power Technologies International 9-67
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-68 Siemens Energy, Inc., Power Technologies International
Figure 9-30. Simple L-G Fault at Bus 300
LINE TO GROUND FAULT AT BUS 300 [WEST 132] PHASE 1
L-G Z = 0.0000E+00 0.0000E+00
SEQUENCE THEVENIN IMPEDANCES AT FAULTED BUSES:
BUS NAME BSKV ZERO POSITIVE NEGATIVE
300 WEST 132 0.00127 0.11696 0.28804 1.07742 0.00000 0.00000
LINE TO GROUND FAULT AT BUS 300 [WEST 132]:
SEQUENCE /V0/ AN(V0) /V+/ AN(V+) /V-/ AN(V-)
PHASE /VA/ AN(VA) /VB/ AN(VB) /VC/ AN(VC)
300 (P.U.) 0.0960 -172.91 0.0960 7.09 0.0000 0.00
WEST 132 0.0000 0.00 0.0000 0.00 0.1920 -172.91
SEQUENCE /I0/ AN(I0) /I+/ AN(I+) /I-/ AN(I-)
PHASE /IA/ AN(IA) /IB/ AN(IB) /IC/ AN(IC)
FROM 200 1 0.1810 -80.09 0.7558 -80.88 0.0000 0.00
HYDRO 132 0.9368 -80.73 0.0000 0.00 0.5749 98.87
FROM 330 1 0.6400 -82.91 0.0679 -98.25 0.0000 0.00
EAST-LOD12.0 0.7057 -84.37 0.0000 0.00 0.5749 -81.13
SUM OF CONTRIBUTIONS INTO BUS 300 [WEST 132]:
300 0.8208 -82.29 0.8208 -82.29 0.0000 0.00
WEST 132 1.6417 -82.29 0.0000 0.00 0.0000 0.00
CONTRIBUTIONS EQUIVALENT POSITIVE SEQUENCE ADMITTANCE 0.0927 -8.5492
FAULT CURRENT AT BUS 300 [WEST 132]:
300 0.8208 -82.29 0.8208 -82.29 0.0000 0.00
WEST 132 1.6417 -82.29 0.0000 0.00 0.0000 0.00
POSITIVE SEQUENCE EQUIVALENT FAULT ADMITTANCE 0.0927 -8.5492
Load currents
flowing in
c-phase
a-phase fault current contributions
I0 = I1 for a-phase
fault current
Fault current
Siemens Energy, Inc., Power Technologies International 9-69
PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-70 Siemens Energy, Inc., Power Technologies International
Figure 9-32. Secondary System Grounded at Buses 330 and 550
LINE TO GROUND FAULT AT BUS 330 [EAST-LOD12.0] PHASE 1
L-G Z = 0.0000E+00 0.0000E+00
LINE TO GROUND FAULT AT BUS 550 [MAIN-LOD12.0] PHASE 1
L-G Z = 0.0000E+00 0.0000E+00
SEQUENCE THEVENIN IMPEDANCES AT FAULTED BUSES:
BUS NAME BSKV ZERO POSITIVE NEGATIVE
330 EAST-LOD12.0 0.00007********* 0.32217 1.14687 0.00000 0.00000
550 MAIN-LOD12.0 0.04007-99.20067 0.42517 1.25624 0.00000 0.00000
SEQUENCE /V0/ AN(V0) /V+/ AN(V+) /V-/ AN(V-)
PHASE /VA/ AN(VA) /VB/ AN(VB) /VC/ AN(VC)
330 (P.U.) 1.0066 172.51 1.0066 -7.49 0.0000 0.00
EAST-LOD12.0 0.0000 0.00 0.0000 0.00 2.0132 172.51
SEQUENCE /I0/ AN(I0) /I+/ AN(I+) /I-/ AN(I-)
PHASE /IA/ AN(IA) /IB/ AN(IB) /IC/ AN(IC)
FROM 300 1 0.0000 0.00 0.1517 -23.04 0.0000 0.00
WEST 132 0.1517 -23.04 0.0000 0.00 0.1517 156.96
FROM 550 1 0.0386 -26.93 0.0616 155.92 0.0000 0.00
MAIN-LOD12.0 0.0231 160.69 0.0000 0.00 0.1001 -25.18
SUM OF CONTRIBUTIONS INTO BUS 330 [EAST-LOD12.0]:
330 0.0386 -26.93 0.0902 -22.33 0.0000 0.00
EAST-LOD12.0 0.1287 -23.71 0.0000 0.00 0.0518 161.10
CONTRIBUTIONS EQUIVALENT POSITIVE SEQUENCE ADMITTANCE 0.0866 -0.0229
LINE TO GROUND FAULT AT BUS 550 [MAIN-LOD12.0]:
SEQUENCE /V0/ AN(V0) /V+/ AN(V+) /V-/ AN(V-)
PHASE /VA/ AN(VA) /VB/ AN(VB) /VC/ AN(VC)
550 (P.U.) 0.9953 170.86 0.9953 -9.14 0.0000 0.00
MAIN-LOD12.0 0.0000 0.00 0.0000 0.00 1.9906 170.86
SEQUENCE /I0/ AN(I0) /I+/ AN(I+) /I-/ AN(I-)
PHASE /IA/ AN(IA) /IB/ AN(IB) /IC/ AN(IC)
FROM 330 1 0.0386 153.07 0.0616 -24.08 0.0000 0.00
EAST-LOD12.0 0.0231 -19.31 0.0000 0.00 0.1001 154.82
FROM 440 1 0.0000 0.00 0.0614 -23.79 0.0000 0.00
WEST-LOD12.0 0.0614 -23.79 0.0000 0.00 0.0614 156.21
SUM OF CONTRIBUTIONS INTO BUS 550 [MAIN-LOD12.0]:
550 0.0386 153.07 0.1229 -23.93 0.0000 0.00
MAIN-LOD12.0 0.0844 -22.56 0.0000 0.00 0.1615 155.35
CONTRIBUTIONS EQUIVALENT POSITIVE SEQUENCE ADMITTANCE 0.1194 -0.0315
Zero voltage at
grounded point
Note current flow in a-phase conductor even
though it is grounded at both ends
Zero voltage at
grounded point
Algebraic sum of load and ground current
Load
current
Load current
Siemens Energy, Inc., Power Technologies International 9-71
PSS
E treats unbalanced fault analysis as a direct extension of its power flow activities. All that is
needed to perform unbalanced fault calculations on a fully detailed, solved power flow case is to
augment the positive sequence power flow data with the corresponding negative and zero
sequence data, and to use fault analysis activities in place of power flow activities. The working
case always includes provision for negative and zero sequence data values corresponding to the
positive sequence parameters of the appropriate system components. This data may be introduced
into the working case at any time and, after being introduced, it is saved and retrieved by activities
SAVE and CASE, respectively, as an integral part of a Saved Case.
The fault analysis activities of PSS
E 32.0
Performing Fault Analysis under Unbalance Condition Program Operation Manual
9-72 Siemens Energy, Inc., Power Technologies International
impedance or apparent admittance at the entry to any branch (refer to activity SCOP). Multiple
unbalanced conditions may be applied simultaneously.
After the system positive sequence and fault analysis data have been properly coordinated and
saved, the fault analysis process is a direct parallel of the power flow switching study procedure
outlined in Section 9.7.7. The principal steps in a fault analysis calculation are:
1. Set up the power flow case for the pre-switching system condition. When a solved case is
to be the initial condition, the working case must be a solved case. Otherwise, the bus
boundary conditions must correspond to the pre-fault condition (refer to activity FLAT). This
provides the basis for the initialization of all generators and the conversion of all loads to
constant admittance.
2. Change branch and generator status as required, or adjust loads and shunts, to produce the
desired post-switching system conditions excluding unbalances. This may require the use
of activities CHNG and SQCH or the [Spreadsheet].
3. Establish all required sequence network admittance matrices for the post-switching condi-
tion with activity SEQD. When the sequence network setup option is disabled (refer to
Section 3.3.3 and activity OPTN), activity SEQD must be executed by the user before initi-
ating activity SCMU. When the sequence network setup option is enabled, activity SCMU
automatically executes activity SEQD each time it is executed.
4. Apply all unbalances that are to exist in the post-switching condition and solve the resulting
interconnected sequence networks for the complete set of system voltages. This step is
handled by activity SCMU. Activity SCMU will re-establish the network admittance matrices
for the post-switching condition prior to performing the calculations.
5. Use activity SCOP to obtain output as required.
It is important to note the relationship and sequencing of steps 2 through 4. Steps 2 and 3 represent
the setup of the balanced post-switching system condition. In most cases, step 2 is not needed and
the procedure is to use activity SEQD followed by activity SCMU. When calculating multiple fault
cases from the identical pre-switching system condition when no balanced switchings are required
to get to the post-switching conditions, it is not necessary to execute activity SEQD prior to each
fault calculation. Activity SEQD needs to be executed following any equipment status changes, or
any branch, shunt or load data changes with activities CHNG, SQCH, or the [Spreadsheet].
In applying the unbalances shown in Figure 9-13, the following points should be noted:
1. Both resistance and reactance must be specified for each impedance shown. Impedances
are specified in per unit relative to base impedance.
2. It is not necessary to multiply ground fault impedances by three; this is done automatically
by activity SCMU.
3. The branch on which an in-line unbalance is to be applied must be in-service in the power
flow case before activity SEQD is executed. Activity SCMU opens the branch at one end
automatically if the one end opened option is selected and re-establish the network admit-
tance matrices.
4. Only one in-line unbalance may be applied during any execution of activity SCMU. The loca-
tion of this unbalance is automatically assigned the bus number 999999 by activity SCMU.
Siemens Energy, Inc., Power Technologies International 9-73
PSS
E GUI Users Guide, Section 15.2, Running Fault Analysis under Unbalance Condition
PSS
E 32.0
Performing Detailed Fault Analysis under Unbalance Condition Program Operation Manual
9-74 Siemens Energy, Inc., Power Technologies International
9.8 Performing Detailed Fault Analysis under Unbalance
Condition
Activity SCOP
The unbalanced network solution output activity SCOP tabulates the results of activity SCMU. It
allows the user to obtain output of all bus voltages and either branch currents, apparent impedances
or apparent admittances.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV.
The user must choose among the following branch quantities:
Currents (default)
Apparent imedances
Apparent admittances
Activity SCOP recognizes the fault analysis output options (refer to Section 3.3.3), with quantities
printed in either physical units or per unit, and in either rectangular or polar coordinates. These
option settings may be modified with activity OPTN.
The data printed for any bus, i, consists of:
1. Sequence and phase voltages at bus i. This is identical to the bus voltage block described
in Section 9.7.8.
2. Series branch quantity for each branch and machine connected to bus i consisting of either:
a. Branch series currents leaving bus i, in either per unit or amps. These are in the
reverse direction of the currents described in Section 9.7.8.
b. Branch apparent impedances looking down each branch from bus i, expressed in
either per unit or ohms. These apparent impedances are defined as:
Run Activity SCOP - GUI
Fault > Solve and report network with unbalances (SCMU/SCOP)
[Multiple Simultaneous Unbalances]
Solution Output Tab
Run Line Mode Activity SCOP - CLI
ACTIVITY?
>>SCOP
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 9-75
PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-76 Siemens Energy, Inc., Power Technologies International
9.9 Calculating Automatic Sequencing Fault
Activity ASCC
There are two APIs which run activity ASCC.
ASCC api
- allows only three phase and line-to-ground fault types
- can only be run from BAT commands and automation files
- generates text output report in original format
ASCC_2 api
- in addition to three phase and line-to-ground fault types, allows line-line-to-ground
and line-to-line fault types
- allows to display fault currents on slider diagram
- allows to save fault calcualtion results into results file
- allows contour plots of maximum fault currents
- can be run from GUI, BAT commands and automation files
- generates text output report in new format
Requirements / Prerequisites, ASCC
Validly specified power flow case with sequence data appended to it.
Reading Sequence Data
Run Line Mode Activity ASCC - CLI
ACTIVITY?
>>ASCC
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Requirements / Prerequisites, ASCC_2
Validly specified power flow case.
For unbalanced fault calculations, sequence data appended to saved case.
Reading Sequence Data
Run Activity ASCC - GUI
Fault > Automatic sequence fault calculation (ASCC)
[Automatic Sequence Fault Calculation]
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 9-77
PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-78 Siemens Energy, Inc., Power Technologies International
9.9.1 Automatic Sequencing Fault Selection Options
The term home bus refers to any bus location selected for application of either three phase faults
or both three phase and single-line-to-ground faults. Figure 9-34 shows a three bus system in which
Bus I has been selected for fault application L.
Figure 9-34. Home Bus
Bus I is the home bus and if faults are to be selected only at home buses there will be a maximum
of 2 faults applied at Bus I, if both a three phase and a single-line-to-ground fault are applied. With
only a 3-phase fault applied the number of faults will be limited to one.
Figure 9-35 shows the option where a fault is to be applied at the home bus with all circuits in
service and with each outgoing line out of service in turn. In this situation, for this home bus, there
will be 4 faults if only one fault type is selected. If line outages are performed on a selective basis
instead of selecting all outgoing branches, the number of faults applied will clearly be reduced.
Siemens Energy, Inc., Power Technologies International 9-79
PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-80 Siemens Energy, Inc., Power Technologies International
Figure 9-36. Home Bus and Open Line End Faults
The user can select output options for each fault applied, ranging from a tabulation of fault currents
through detailed output of conditions at the home bus along with detailed output for all buses up to
< n > levels away from the home bus.
Figure 9-37 clarifies the concept of < n > levels away. It can be seen that, given the possibility of a
large combination of home buses, line out cases and line open end cases, coupled with a value of
< n > greater than 1, the possibility arises for a very large output listing or file.
In the diagram, for the home bus shown, there are 3 buses which are 1 level away and 2 buses
which are 2 levels away.
The user should take care in selection of the number of fault and output options.
Siemens Energy, Inc., Power Technologies International 9-81
PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-82 Siemens Energy, Inc., Power Technologies International
Impose flat
conditions
If enabled (default), classical fault analysis conditions are assumed for the network in
the working case.
Bus voltages are assumed to be one per unit at zero phase angle.
Constant power, current, and admittance loads are neglected in the
positive and negative sequence networks. Zero sequence shunt loads
are represented.
Generator power outputs are assumed to be zero.
FACTS devices and dc lines are ignored.
Transformer phase shift angles are assumed to be zero. Any transformer
impedance, which is a function of phase shift angle, is assumed to be at
nominal value.
Transformer turns ratios are assumed to be one. This includes generator
step-up transformers, which are modeled as part of the machine
representation (i.e., the GENTAP). Any transformer impedance, which is
a function of turns ratio, is assumed to be at nominal value.
Line charging is neglected in all three sequence networks.
Fixed bus shunts are neglected in all three sequences.
Switched shunts are neglected in all three sequences.
Line shunts and magnetizing admittances are neglected in all three sequences.
The zero sequence ground ties created by grounded transformer
windings are represented; see Section 5.5.3, Transformers in the Zero
Sequence, and Figures 5-18 and 5-19.
If disabled, the level of network modeling and the bus boundary conditions used by
activity ASCC as the pre-fault network condition are as specified in the working case at
the time activity ASCC is selected. If unblocked dc lines or in-service FACTS devices
are present in the working case, the user specifies their treatment in the fault analysis
solution, either to block or to represent dc lines and FACTS devices as load.
Represent dc lines
and FACTS
devices as load
DC lines and FACTS devices can be blocked or represented as load.
If represented as load, the apparent ac system complex loads are converted to positive
sequence constant admittance load at the buses at which these quantities are injected
into the ac system during normal power flow work. In the negative and zero sequence
networks, dc lines and FACTS devices are represented as open circuits. The selected
option applies to all dc lines and FACTS devices in the working case.
Apply transformer
impedance to zero
correction
If the line-to-ground fault option had been selected and the actual positive sequence
impedance of any transformer in the working case differs from its nominal value (refer to
Transformer Impedance Correction Tables), the user may apply transformer impedance
to zero correction. The zero sequence impedance of each such transformer is
scaled by the same factor as is its positive sequence impedance. Otherwise,
all zero sequence transformer impedances are left at their nominal values (i.e.,
the values entered in activities RESQ, TRSQ, or SQCH). The same treatment
applies to all transformers in the system that are not at nominal impedance.
Table 9-1. Automatic Sequenceing Short Circuit Calculation Options (Cont.)
Specification Description
Siemens Energy, Inc., Power Technologies International 9-83
PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-84 Siemens Energy, Inc., Power Technologies International
9.9.2 Fault Control Data File Contents
The Fault Control Data File consists of two groups of records. With the first group of records, buses
may be categorized as not to be faulted. This provides, for example, for the suppression of fault
calculations at dummy buses. In addition, for the purpose of reporting bus conditions for faults at
other buses, each bus may be categorized as being either:
1. Printed and counted in the levels away calculation.
2. Not printed but counted.
3. Not printed and not counted.
This group of records is of the form:
IBUS, FCODE, PCODE
where:
Data records may be entered in any order. This group of records is terminated with a record spec-
ifying an IBUS value of zero.
The hidden star point buses of three-winding transformers are always assumed to have FCODE
and PCODE values of zero. Any other bus for which no data record is read is assigned the default
values given above.
With the second group of records, for any bus to be faulted, the following may be specified:
1. Up to 20 buses where conditions are to be tabulated for all fault cases calculated for this
home bus. These buses are in addition to those printed as a result of the levels away
selection.
2. Up to eight additional branches to be outaged in turn with the home bus faulted. These fault
cases are calculated only if the line out option was selected, and are in addition to the auto-
matic outaging of the branches connected to the home bus. Only non transformer branches
and two-winding transformers may be specified.
Data for each home bus specified here is entered on three consecutive data records as follows:
IBUS
JBUS1, JBUS2, ... JBUS20
I1, J1, CKT1, ... I8, J8, CKT8
where:
IBUS Bus number. Bus IBUS must be present in the working case. No default is allowed.
FCODE Fault code of either zero (suppress faulting of bus IBUS) or one (allow bus IBUS to
be faulted). FCODE = 1 by default.
PCODE Print control code for conditions at bus IBUS when some other bus is faulted.
PCODE may be specified as either zero (no reporting, and not counted in the
levels away calculation), one (no reporting, but counted in the levels away calcula-
tion), or two (reported and counted). PCODE = 2 by default.
IBUS Bus number. Bus IBUS must be present in the working case. No default is allowed.
Siemens Energy, Inc., Power Technologies International 9-85
PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-86 Siemens Energy, Inc., Power Technologies International
Figure 9-38. Location of Bus 151 and Buses One Level Away in savnw.sav
Each page of the detailed bus output report generated by activity ASCC contains a heading block,
which tabulates the current date and time, the two-line case heading, and the home bus number
and name. If the flat conditions option was specified, this is noted; if the line outage or line end
condition is being reported, this is also flagged. If subsystems are being specified by area, zone,
and/or owner, the area, zone, and/or owner, as appropriate, currently being processed are also
identified.
The home bus, the level number, relative to the home bus, of buses where output is printed on the
page, and, if appropriate, a line out or line end identifier are printed on the right side of the banner
block. If line-to-ground faults are being calculated and subsystem selection by area, zone, and/or
owner is enabled, the current area, zone, and/or owner is also printed here. This facilitates the
locating of a desired set of output from within a lengthy report by fanning through the stack of paper.
Voltages, currents and apparent impedances are printed in either physical units (kV L-G, amps and
ohms) or per unit, and in either rectangular or polar coordinates, according to the fault analysis
output options currently in effect (refer to Section 3.3.3 and activity OPTN). If the physical units
option has been enabled and the bus where base voltage is required for the calculation of a quantity
has no base voltage specified for it, the quantity is printed in per unit.
Siemens Energy, Inc., Power Technologies International 9-87
PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-88 Siemens Energy, Inc., Power Technologies International
If the fault current summary table option has been specified, one output line is printed for each fault giving
the fault currents. Fault currents are printed in either amps or per unit, and in either rectangular or
polar coordinates, according to the fault analysis output options currently in effect (refer to
Section 3.3.3 and activity OPTN). If the physical units option has been enabled and the faulted bus
has no base voltage specified for it, fault current is printed in per unit. If line out and/or line end faults
are being calculated, for a given home bus, the bus fault is reported first. Then the line out and/or
line end faults involving each branch connected to the home bus in turn are processed.
9.9.5 Example: Automatic Sequencing, 3-Phase Faults, ASCC API
This case assumes application of only 3-phase faults at bus 151 with full reporting at the home bus
one level away. Faults are applied with all lines in service, with each outgoing line out of service in
turn and with an open line-end fault on each outgoing line in turn. Output is in rectangular
coordinates.
In Figure 9-39, overleaf, the results for the home bus are listed. It can be seen that although there
is a 600 Mvar shunt connected at bus 151, the total shunt current is zero. This is clearly because
the voltage at this bus (the faulted home but is zero).
Note that the listing has been compressed slightly from the original output listing for the portrait
view.
In Figure 9-40, the results are listed for the 1 Level away. It can be seen that there is a listing for the
four immediate neighbors of bus 151, the home bus. The information on branch flows has the same
format as that of the home bus, at the 0 Level because the full report options was selected for these
buses.
Figure 9-39. Report Output at the Home Bus ( 0 level) for a 3-Phase Fault
In Figure 9-40 it can be seen that the immediate neighbors to bus 151 are the buses 101, 102, 152
and 201. Those buses, at 1 level away, are now the AT buses. The flows shown in the tabulation
are from the from buses towards the respective AT buses.
- PSS/E SHORT CIRCUIT OUTPUT THU, FEB 26 2004 11:35 .HOME BUS IS 151.
- PSS/E PROGRAM APPLICATION GUIDE EXAMPLE .NUCPANT 500.0.
- BASE CASE INCLUDING SEQUENCE DATA .
- *** FAULTED BUS IS: 151 [NUCPANT 500.0] *** 0 LEVELS AWAY
AT BUS 151 [NUCPANT 500.00] AREA 1 (PU) U+: 0.0000+J 0.0000
THEV. R, X, X/R: POSITIVE 0.00409 0.01765 4.318
T H R E E P H A S E F A U L T
X--------- FROM --------X AREA CKT I/Z RE(I+) IM(I+) RE(Z+) IM(Z+) APP X/R
101 [NUC-A 21.600] 1 1 PU/PU 9.8734 -11.0030 0.0003 0.0136 45.333
102 [NUC-B 21.600] 1 1 PU/PU 9.8734 -11.0030 0.0003 0.0136 45.333
152 [MID500 500.00] 1 1 PU/PU -0.2319 -6.2545 0.0031 0.0500 16.264
152 [MID500 500.00] 1 2 PU/PU -0.2319 -6.2545 0.0031 0.0500 16.264
201 [HYDRO 500.00] 2 1 PU/PU 3.3729 -16.5469 0.0010 0.0151 14.864
TO SHUNT (P.U.) 0.0000 0.0000
TOTAL FAULT CURRENT (P.U.) 22.6560 -51.0619
Siemens Energy, Inc., Power Technologies International 9-89
PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-90 Siemens Energy, Inc., Power Technologies International
Figure 9-41. Fault Summary Report with 3-Phase Fault on Bus 151
9.9.6 Example: Automatic Sequencing, 3-Phase & Single L-G Faults, ASCC
API
This case assumes application of 3-phase faults and single-line-to-ground faults at bus 151 with full
reporting at the home bus one level away. Faults are applied with all lines in service and output in
polar coordinates. The output will be 3 x zero sequence currents and zero sequence apparent
impedances.
With the single-line-to-ground faults included, the report format is the same as for only 3-phase
faults. The results now append the zero sequence fault current flows in the branches connected to
the home bus. In addition the negative and zero sequence Thevenin impedances are shown,
together with the A phase and sequence voltages at the faulted bus.
With polar coordinates used, it can be seen that the total fault current is 55.8625 / -66.07 pu,
compared to the rectangular coordinate output which, in Figure 9-39, is 22.656 -51.0619 pu. The
listing for < n > levels away will use the same format shown in Figure 9-40 with, in this case, the
zero sequence (L-G) results appended in the right hand columns.
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSS/E THU, FEB 26 2004 11:36
PSS/E PROGRAM APPLICATION GUIDE EXAMPLE SHORT CIRCUIT
BASE CASE INCLUDING SEQUENCE DATA FAULT CURRENTS
| THREE PHASE FAULT
X------ BUS ------X X------ TO BUS ------X CKT RE(I+) IM(I+)
151 [NUCPANT 500.0 P.U. 22.6560 -51.0619
151 [NUCPANT 500.0 101 [NUC-A 21.600] 1 OUT P.U. 12.7826 -40.0589
151 [NUCPANT 500.0 101 [NUC-A 21.600] 1 END P.U. 5.5934 -26.1350
151 [NUCPANT 500.0 102 [NUC-B 21.600] 1 OUT P.U. 12.7826 -40.0589
151 [NUCPANT 500.0 102 [NUC-B 21.600] 1 END P.U. 5.5934 -26.1350
151 [NUCPANT 500.0 152 [MID500 500.00] 1 OUT P.U. 21.9500 -48.2059
151 [NUCPANT 500.0 152 [MID500 500.00] 1 END P.U. 5.0230 -14.4880
151 [NUCPANT 500.0 201 [HYDRO 500.00] 1 OUT P.U. 18.3905 -41.1311
151 [NUCPANT 500.0 201 [HYDRO 500.00] 1 END P.U. 10.0377 -24.6822
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
9
-
9
1
P
S
S
E
3
2
.
0
U
n
b
a
l
a
n
c
e
d
F
a
u
l
t
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
C
a
l
c
u
l
a
t
i
n
g
A
u
t
o
m
a
t
i
c
S
e
q
u
e
n
c
i
n
g
F
a
u
l
t
Figure 9-42. Results for Three-Phase and Single Phase fault at bus 151
PSS/E SHORT CIRCUIT OUTPUT MON, MAR 01 2004 14:53 HOME BUS IS :
PSS/E PROGRAM APPLICATION GUIDE EXAMPLE 151 [NUCPANT 500.00]
BASE CASE INCLUDING SEQUENCE DATA
*** FAULTED BUS IS : 151 [NUCPANT 500.00] *** 0 LEVELS AWAY
RT BUS 151 [NUCPANT 500.00] AREA 1 (PU) V+: / 0.0000/ 0.00 (PU) VA: / 0.0000/ 0.00 V0: / 0.1497/ -159.48
V+: / 0.5799/ 12.13 V-: / 0.4323/ -170.77
THEV. R, X, X/R: POSITIVE 0.00409 0.01765 4.318 NEGATIVE 0.00409 0.01765 4.138 ZERO 0.00019 0.00627 32.847
T H R E E P H A S E F A U L T O N E P H A S E F A U L T
X--------- FROM -------X AREA CKT I/Z /I+/ AN(I+) /Z+/ AN(Z+) APP X/R /3I0/ AN(3I0) /Z0/ AN(Z0) APP X/R
101 [NUC-A 21.600 1 1 PU/PU 14.7835 -48.10 0.0136 88.74 45.333 33.0137 -68.21 0.0000 0.00 0.000
102 [NUC-B 21.600 1 1 PU/PU 14.7835 -48.10 0.0136 88.74 45.333 33.0137 -68.21 0.0000 0.00 0.000
152 [MID500 500.00 1 1 PU/PU 6.2588 -92.12 0.0501 86.48 16.264 0.1865 53.87 0.1044 -95.14 11.121
152 [MID500 500.00 1 2 PU/PU 6.2588 -92.12 0.0501 86.48 16.264 0.1865 53.87 0.1044 -95.14 11.121
201 [HYDRO 500.00 2 1 PU/PU 16.8872 -78.48 0.0512 86.15 14.864 5.7775 -65.40 0.0222 -93.00 19.081
TO SHUNT (P.U.) 0.0000 0.00 0.0000 0.00
TOTAL FAULT CURRENT (P.U.) 55.8625 -66.07 71.6023 -68.21
Unbalanced Fault Analysis PSS
E 32.0
Calculating Automatic Sequencing Fault Program Operation Manual
9-92 Siemens Energy, Inc., Power Technologies International
9.9.7 Relay File Output
The relay output file optionally generated by the automatic sequence fault calculations activity
contains a single-line summary for each fault calculation performed. Each line commences with a
code indicating the type of fault:
The following quantities are tabulated in the indicated column positions of each record
9.9.8 Application Notes
Activity ASCC is a totally self-contained fault analysis calculation. All that is required prior to
entering activity ASCC is a valid power flow case with sequence data appended to it (i.e., with a
activity RESQ having been executed). Bus voltages and boundary conditions must correspond to
the desired pre-fault network condition, unless the flat conditions option is specified.
Activity ASCC may be preceded by activity FLAT to impose different levels of flattening than is
implemented by the flat conditions option of activity ASCC. For example, the flat option of activity
ASCC retains the zero sequence shunt loads (refer to Negative Sequence Shunt Load Data). To
calculate fault cases with these set to zero, the following procedure may be used:
1. Use activity FLAT with classical short circuit assumptions on the unconverted network, setting
tap ratios to unity and line charging to zero and setting shunts to zero in all sequences.
2. Then run activity ASCC without specifying the flat conditions option.
Code Type of Fault
3 Three-phase fault at the home bus
1 Line-to-ground fault at the home bus
30 Three-phase line end fault
10 Line-to-ground line end fault
2-3: Fault code
5-10: Home bus number
12-17: from bus number (0 if the branch is a three-winding transformer) for line out or line
end, or blank
19-24: to bus number for line out or line end, or blank
26-27: Circuit identifier for line out or line end, or blank
29-41: Fault current magnitude in per unit
43-55: Ratio of imaginary/real components of fault current
58-75: Extended bus name of home bus
78-95: Extended bus name of from bus (3WND: followed by the three-winding transformer
name if from bus field is 0), or blank
98-115: Extended bus name of to bus, or blank
Siemens Energy, Inc., Power Technologies International 9-93
PSS
E 32.0
Calculating Fault Currents to ANSI Standards Program Operation Manual
9-94 Siemens Energy, Inc., Power Technologies International
9.10 Calculating Fault Currents to ANSI Standards
Activity ANSI
The ANSI fault current calculation activity ANSI calculates fault currents according to the ANSI stan-
dard C37.5-1979 Guide for Calculation of Fault Currents for Application of AC High-Voltage Circuit
Breakers Rated on a Total Current Basis.
The following input data defining solution and reporting options is specified to ANSI:
The treatment of the zero sequence impedance of all transformers where actual posi-
tive sequence impedance differs from its nominal value (refer to Transformer
Impedance Correction Tables). The zero sequence impedance of each such trans-
former may either be scaled by the same factor as is its positive sequence impedance,
or all zero sequence transformer impedances may be left at their nominal values (i.e.,
the values entered in activities RESQ, TRSQ, or SQCH). The same treatment applies
to all transformers in the system that are not at nominal impedance.
Decay factors to be applied. Decay factors may be obtained from either Figures 1 and
2 of the ANSI standard, which include the effects of both ac and dc decay, or from
Figure 3, which includes only the effects of dc decay.
Resistance scaling factors. For branches and machines with a zero value of resistance,
activity ANSI assigns a non-zero resistance equal to its reactance divided by a scaling
factor. Four such factors (for positive sequence branch impedance, positive sequence
machine impedance, zero sequence branch impedance, and zero sequence machine
impedance) are specified.
Output option, selected from among the following output report formats:
a. Summary output in report format using only the ANSI X matrices (output fields are
separated by blanks).
b. Summary output in spreadsheet input format using only the ANSI X matrices
(output fields are comma delimited).
c. Detailed output in report format using only the ANSI X matrices.
d. Detailed output in report format using both the ANSI R and ANSI X matrices.
e. Summary output in report format using both the ANSI R and X matrices (output
fields are separated by blanks).
f. Summary output in spreadsheet input format using both the ANSI R and X matrices
(output fields are comma delimited).
Run Activity ANSI - GUI
Fault > ANSI fault calculation (ANSI)
[ANSI Fault Current Calculation]
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 9-95
PSS
E 32.0
Calculating Fault Currents to ANSI Standards Program Operation Manual
9-96 Siemens Energy, Inc., Power Technologies International
9.10.2 ANSI Fault Current Calculation Options
Table 9-2. ANSI Fault Current Calculation Options
Option Description
For branches in
positive sequence
Resistance scaling factors (Divisors): For branches and machines with a zero
value of resistance, activity ANSI assigns a non-zero resistance equal to its
reactance divided by a scaling factor. Four such factors (for positive sequence
branch impedance, positive sequence machine impedance, zero sequence
branch impedance, and zero sequence machine impedance) are specified.
For machines in
positive sequence
For branches in zero
sequence
For machines in
zero sequence
Fault multiplying
factors
Decay factors to be applied: Include the effects of one of the following:
dc decrement only
ac and dc decrement
Apply transformer
impedance
correction
Enabled: Scale the zero sequence impedance of all transformers where actual
positive sequence impedance differs from nominal value by the same factor as
is its positive sequence impedance.
Disabled (default): All zero sequence transformer impedances are left at their
nominal values (i.e., the original values used to establish the sequence network
data). The same treatment applies to all transformers in the system that are not
at nominal impedance.
Output format There are six output report format options:
Summary output using ANSI X only (output fields are blank delimited)
Summary output using ANSI X only (output fields are comma delimited)
Detailed output using ANSI X only
Detailed output using ANSI R and X
Summary output using ANSI R and X (output fields are blank delimited)
Summary output using ANSI R and X (output fields are comma delimited)
Fault specifications
From input file: Specify faulted buses, along with their highest operating voltages
and contact parting times, from an ANSI Fault Specification Data file (*.ans) (see
Section 9.10.1).
Interactive: Specify faulted buses using the dialog. Select buses using the Bus to
add to fault list selection field. The user may change the following bus values:
Maximum operating voltage, in pu
Contact parting time, in seconds
Siemens Energy, Inc., Power Technologies International 9-97
PSS
E 32.0
Calculating Fault Currents to ANSI Standards Program Operation Manual
9-98 Siemens Energy, Inc., Power Technologies International
where base voltage is required for the calculation of a quantity has no base voltage specified for it,
the quantity is printed in per unit.
For each faulted bus (i.e., at each at bus), the following quantities are tabulated:
1. The bus number, name, base voltage, and area number in which it is located, with the spec-
ified maximum operating voltage listed below the bus identifiers. This is followed by the
positive sequence bus voltage for the three phase fault case, and the A phase voltage and
the three sequence voltages for the L-G case.
2. The positive and zero sequence ANSI Thevenin impedances at the fault point in per unit,
rectangular coordinates (the positive and negative sequences are identical to the ANSI fault
calculation standard).
3. The machine identifier and currents arriving at the bus from all in-service machines at the
bus. For the L-G fault, three times the zero sequence current (3I
0
) is printed.
4. The from bus number, name, base voltage, area number, and circuit identifier of each non-
transformer branch and two-winding transformer connected to the at bus. The branch quan-
tities tabulated include the current arriving at the at bus from the from bus, the apparent
impedance as seen at the from bus looking down the line toward the at bus (i.e., the V/I ratio
at the from bus), and the ratio of apparent X/R. For the L-G fault, zero sequence quantities
are printed. Branches are printed in ascending from bus numerical or alphabetical order
according to the bus output option in effect.
5. The winding number, transformer name and circuit identifier of each three-winding trans-
former connected to the at bus. The current arriving at the at bus from the transformer is
tabulated. For the L-G fault, zero sequence quantities are printed. Three-winding trans-
formers are printed in ascending transformer name order.
6. The sum of the currents output in (3), (4) and (5) above. These currents are annotated SUM
OF CONTRIBUTIONS.
7. The fault current as calculated from the maximum operating voltage and the ANSI Thevenin
reactance or impedance, as appropriate.
The quantity shown as the sum of contributions will be essentially identical to the quantity shown
as fault current for both three phase and line-to-ground faults when fault currents and contributions
are calculated using only the ANSI X matrices. However, these quantities will normally differ when
the output is calculated using both the ANSI R and ANSI X matrices. This is due to the error intro-
duced by decoupling the complex sequence admittance matrices into pairs of real matrices, using
the real matrices to derive columns of R and X matrices (i.e., the decoupled impedance matrices),
and then coupling the columns back together to get approximations of the complex impedance
matrix columns.
Figure 9-43b shows an example of a detailed report obtained for faults on Bus 151 in the savnw.sav
power flow case.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
9
-
9
9
P
S
S
E
3
2
.
0
U
n
b
a
l
a
n
c
e
d
F
a
u
l
t
A
n
a
l
y
s
i
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
C
a
l
c
u
l
a
t
i
n
g
F
a
u
l
t
C
u
r
r
e
n
t
s
t
o
A
N
S
I
S
t
a
n
d
a
r
d
s
Figure 9-43. Summary and Detailed Report of ANSI Fault Calculation
Unbalanced Fault Analysis PSS
E 32.0
Calculating Fault Currents to ANSI Standards Program Operation Manual
9-100 Siemens Energy, Inc., Power Technologies International
9.10.5 Application Notes
While the working case may represent the network at any level of detail from classical fault analysis
assumptions through a fully solved power flow model, activity ANSI applies classical fault analysis
conditions. Specifically, voltages, loads, machine loadings, bus and line shunts, line charging,
phase shift angles, dc lines, and FACTS devices in the working case are ignored. Tap ratios and
zero sequence mutual couplings are recognized in constructing the decoupled admittance
matrices. It is quite common, and perfectly valid, to have the generator terminal bus isolated in the
zero sequence network. This is, in fact, the usual case because the majority of generator step-up
transformers are delta connected on the generator side and wye connected on the high side. This
is the assumption inherent in the generator modeling when the step-up transformer is represented
as part of the generator data (i.e., XTRAN is non-zero). Activity ANSI prints an alarm message for
any generator with non-zero values of both XTRAN and ZZERO and uses only XTRAN in setting
up the zero sequence ground tie at the Type 2 (high side) bus.
Any bus which is designated as a bus to be faulted, but which has no base voltage specified for it
in the working case, is logged and omitted from the fault calculations of activity ANSI.
Any non-zero branch or machine impedance where resistance is zero in the working case has an
assumed resistance, equal to its reactance divided by a user-specified scaling factor, used when
the corresponding R decoupled admittance matrix is constructed. Such resistances are always
positive. Zero sequence mutual impedances (RM + jXM of Zero Sequence Mutual Impedance Data)
and zero sequence transformer grounding impedances (RG + jXG of Zero Sequence Transformer
Data) are not subjected to this treatment.
Any non-zero zero sequence branch impedance where reactance is zero in the working case has
an assumed reactance, equal to the zero impedance line threshold tolerance (or to 0.00001 if the
zero impedance line threshold tolerance is 0.0), used when the zero sequence X decoupled admit-
tance matrix is constructed. Such reactances are always positive. Machine impedances, zero
sequence mutual impedances (RM + jXM of Zero Sequence Mutual Impedance Data), and zero
sequence transformer grounding impedances (RG + jXG of Zero Sequence Transformer Data) are
not subjected to this treatment.
Although activity ANSI uses the SEQD temporary file (refer to Section 2.2), the execution of activity
SEQD is not required prior to selecting activity ANSI. Activity ANSI sets up this file in the form
required for its fault solution calculation. Note that, because activity ANSI uses this file, the following
activity sequence would not be valid:
1. SEQD
2. SCMU (perhaps several times)
3. ANSI
4. SCMU
Activity SEQD would need to be re-executed following activity ANSI, prior to the second series of
executions of activity SCMU.
Additional Information
PSS
E 32.0
Using Classical Fault Analysis Assumptions Program Operation Manual
9-102 Siemens Energy, Inc., Power Technologies International
8. (Optional)
For shunt option = 1, the following are set to 0.0:
- fixed bus shunts in all three sequences
- switched shunts in all three sequences
- line shunts and magnetizing admittances in positive and negative sequences
For shunt option = 2, the following are set to 0.0:
- fixed bus shunts in all three sequences
- switched shunts in all three sequences
- line shunts and magnetizing admittances in all three sequences
- bus shunt loads in the negative and zero sequences
9. The zero sequence ground ties created by grounded transformer windings are represented;
see Section 5.5.3, Transformers in the Zero Sequence, and Figures 5-18 and 5-19.
IEC909 Fault Calculations Options
The following data changes are implemented in the working case:
1. Voltage magnitudes are either left at their present values or are all set to a specified magni-
tude; phase angles are all set to zero.
2. Constant power, current, and admittance loads are set to zero.
3. Any machine where active power is zero or negative has its active and reactive power
outputs set to zero. All machines where active power outputs are positive have their reactive
power outputs either left unchanged or set such that a specified power factor is maintained.
4. FACTS devices and dc lines are removed.
5. Transformer phase shift angles are set to zero. Any transformer impedance, which is a func-
tion of phase shift angle, is set to its nominal value.
6. Optionally, all transformer turns ratios are set to one. This includes generator step-up trans-
formers, which are modeled as part of the machine representation (i.e., the GENTAP). Any
transformer impedance, which is a function of turns ratio, is set to its nominal value.
7. Optionally, line charging is set to zero.
8. Optionally, shunt elements, including magnetizing admittances of transformers, are set to
zero. The user may elect to have fixed bus shunts and line connected shunts zeroed in only
the positive sequence network or in all three sequences; switched shunts are zeroed in all
three sequence networks.
9. Optionally select a voltage magnitude or leave voltages as in the power flow case.
10. Optionally select a generator power factor or leave generator Mvar unchanged.
When this IEC setup is selected, short circuit currents in conformance with IEC standard 909 can
be calculated for examination of circuit-breaker duties (see Section 9.13).
When run without further specification, activity FLAT sets all bus voltages to one per unit at zero
phase angle. This is not identical in function to the flat start option that may be specified for the
Siemens Energy, Inc., Power Technologies International 9-103
PSS
E 32.0
Using Classical Fault Analysis Assumptions Program Operation Manual
9-104 Siemens Energy, Inc., Power Technologies International
8. Optionally, fixed and switched bus shunt elements are set to zero in all three sequence
networks, and line shunts, including magnetizing admittances of transformers, are set to
zero in the positive and negative sequences. The user may also elect to have negative and
zero sequence shunt loads (refer to Negative Sequence Shunt Load Data and Zero
Sequence Shunt Load Data) and zero sequence line connected shunts set to zero.
When the setup for IEC909 fault calculations is followed by activity BKDY, short circuit currents in
conformance with IEC standard 909 are calculated.
Additional Information
PSS
E GUI Users Guide, Section 15.6, Using Classical Fault Analysis Option
PSS
E working case
to compute short circuit currents according to the IEC 60909 standard.
Activity IECS calculates following currents (refer to the Program Application Guide, Volume I,
Section 10.10.2 for details).
Activity IECS includes the following features.
1. The impedances of synchronous generators, network transformers and power station units
are modified with impedance correction factors when calculating short circuit currents with
the equivalent voltage source at the short circuit location according to IEC 60909 standard.
(The model of a synchronous generator with a step-up transformer (GSU) is called a Power
Station Unit in IEC 60909.)
2. The specification of network subsystems to be processed according to PSS
E standard
selection criteria. Each electrically connected bus in the specified subsystem becomes the
home bus for one or more fault analysis network solutions.
3. The specification of three phase faults (3PH), single-line-to-ground (LG) faults, double-line-
to-ground (LLG) faults and line-to-line (LL) faults at each fault location or any combinations
of these faults.
4. The application of the faults selected in (3) at each home bus selected in (2).
Requirements / Prerequisites
Validly specified power flow case.
For unbalanced fault calculations, sequence data appended to Saved case or
Reading Sequence Data
Run Activity IECS - GUI
Fault > IEC 60909 fault calculation (IECS)
[IEC 60909 Fault Calculation]
Interrupt Control Codes
None
I
"
k
Initial symmetrical short-circuit current (r.m.s) including phase and sequence
components of fault currents
i
p(B)
Peak short-circuit current by Method B of IEC standard 60909
i
p(C)
Peak short-circuit current by Method C of IEC standard 60909
i
b(DC)
DC component of the asymmetrical breaking current
i
b(SYM)
Symmetrical breaking current (r.m.s.)
i
b(ASYM)
Asymmetrical breaking current (r.m.s.)
Unbalanced Fault Analysis PSS
E 32.0
Calculating Short Circuit Currents According to IEC 60909 Standard Program Operation Manual
9-106 Siemens Energy, Inc., Power Technologies International
5. A selection of output options for each fault applied, ranging from a tabulation of fault currents
through detailed output of conditions at the home bus along with detailed output for all buses
up to < N > levels away removed from the home bus.
The original values of all data items in the working case are not modified by activity IECS. That is,
at the termination of activity IECS, the working case is identical in content to what it was at the time
activity IECS was initiated.
The following inputs are required.
Table 9-3. Short Circuit Calculation Options for IEC 60909
Specification Description
Faults to apply
Fault type selection, select either any combination or all:
Three phase faults
Single line to ground fault
Line-line to ground fault
Line to line fault
Line outage
cases
If enabled, the selected fault calculations are repeated at each home bus < n > addi-
tional times: once with each of its < n > connected branches placed out-of-service. In
addition, if any branches have been designated in the Fault Control Data File (refer to
Section 9.9.4) as branches to be outaged for the current home bus, these fault cases
are also calculated.
Line end faults
If enabled, the selected fault calculations are repeated for each home bus at least < n >
additional times: once (twice for any three-winding transformer which has all its wind-
ings in-service) with each of its < n > connected branches opened at the far end, with
the fault located at the line end position. As in activity SCMU, a dummy bus, numbered
999999, is introduced at the opened end of the branch for each line end fault (refer to
Line Faults).
Output option
The possible options are:
Total fault currents
I''k contributions to < N > levels away
Total fault currents and I''k contributions to < N > levels away
Fault location
The possible options are:
Fault at Network bus (default)
Fault at LV bus of Power Station Unit
Fault at Auxiliary Transformer (connected to Power Station Unit) LV bus
Shunt option
Select either of the following options to set fixed shunts, loads and switched shunts
data.
Set shunts to zero is positive sequence
Set shunts to zero is all sequences
Leave shunts unchanged
Line charging
option
Select either of the following options to set line charging susceptance data.
Set line charging to zero in positive sequence
Set line charging to zero in all sequences
Leave line charging unchanged
Siemens Energy, Inc., Power Technologies International 9-107
PSS
E 32.0
Calculating Short Circuit Currents According to IEC 60909 Standard Program Operation Manual
9-108 Siemens Energy, Inc., Power Technologies International
Additional data is needed in the following cases.
If a generator model includes a GSU transformer. It is recommended to represent the
GSU transformer explicitly as a separate power component so as to be able to correctly
modify the generator and transformer impedances as per the IEC 60909 standard.
If a generator in the working case is an equivalent generator representation.
If a generator is a used in the modeling of a synchronous motor.
If a generator is set with QMIN=QMAX, then it is treated as an asynchronous motor. If
this is the case, then additional data is not necessary.
If a transformer winding MVA specified in system MVA base and not nameplate winding
MVA.
There are two groups of records, with each group containing a particular type of data required.
GSU, Equivalent Generator and Motor Data
Each data record has the following format:
I, ID, MCTYPE, UrG, PG, PFactor, PolePair, GSUType, Ix, Jx, Kx, Ckt, PT
where:
I Machine bus number
ID Machine ID
MCTYPE Machine type
MCTYPE =1, for Generator
MCTYPE =2, for Equivalent generator
MCTYPE =3, for Motor
UrG Rated terminal voltage, line-to-line in kV r.m.s. (this need not be the rated bus
voltage)
PG Range of generator voltage regulation in %, e.g., if PG is 5%, enter PG=5.
PG = (UG -UrG)/UrG, where UG is the scheduled generator terminal voltage
= 0 default
PFactor Machine rated power factor
= 1.0 default
PolePair Number of pole pairs if machine is motor (used only if the machine is modeled as
motor), e.g., if the unit has a six pole construction then Polepair=3
GSUType Generator step-up-transformer type
GSUType =0, no GSU, GSU transformer modeled explicitly.
GSUType =1, GSU with OLTC
GSUType =2, GSU without OLTC
Ix GSU transformer I bus number
Jx GSU transformer J bus number
Kx GSU transformer K bus number
Ckt GSU transformer circuit identifier
Siemens Energy, Inc., Power Technologies International 9-109
PSS
E 32.0
Calculating Short Circuit Currents According to IEC 60909 Standard Program Operation Manual
9-110 Siemens Energy, Inc., Power Technologies International
Transformer Nameplate Winding MVA Data
Each data record has the following format:
I, J, K, Ckt, Sbase 1-2, Sbase 2-3, Sbase 3-1
where:
Data records for generating units and motors may be entered in any order and using a free format
with blanks or commas separating each data item in each record. These records are terminated
with a record specifying machine bus number I value of zero. Following is an example of IEC data
for IEC 60909-4, Section 6 network. (Refer PAG for details.)
1 Q1 2
5 Q2 2
6 G3 1 10.5 0.0 0.8
7 M1 3 0.0 0.0 0.88 1
7 M2 3 0.0 0.0 0.89 2
7 M3 3 0.0 0.0 0.89 2
41 G1 1 21.0 0.0 0.85 0 1 4 41 0 T1 12
31 G2 1 10.5 7.5 0.9 0 2 3 31 0 T2
0 /END OF GSU, EQV, GEN, AND MOTOR DATA
0 /END OF TRANSFORMER DATA
9.12.2 Fault Control Data File Contents
The fault control data file contents and format is the same as those used in the fault control data file
of the activity ASCC. The records in this file are treated same way as they are treated in activity
ASCC.
I Winding 1 bus number
J Winding 2 bus number
K Winding 3 bus number ( =0 for two-winding transformer)
Ckt Transformer circuit identifier
Sbase 1-2 Winding 1 to winding 2 Nameplate MVA
Sbase 2-3 Winding 2 to winding 3 Nameplate MVA (not required for two-winding transformer)
Sbase 3-1 Winding 3 to winding 1 Nameplate MVA (not required for two-winding transformer)
Siemens Energy, Inc., Power Technologies International 9-111
PSS
E saved case, if most of the transformer data is specified on system MVA base and trans-
former winding MVA is not actual winding MVA, it is required to provide nameplate transformer
winding MVA as a transformer IEC data record.
Additional Information
PSS
E 32.0
Calculating Circuit Breaker Interrupting Duty Program Operation Manual
9-112 Siemens Energy, Inc., Power Technologies International
9.13 Calculating Circuit Breaker Interrupting Duty
Activity BKDY
The circuit breaker duty analysis activity BKDY calculates and reports circuit breaker interrupting
duty for three phase faults at all buses in a specified subsystem of the working case. The working
case is assumed to represent the pre-fault system condition with generators represented as current
sources.
At each bus in the specified subsystem in turn, activity BKDY applies a three phase fault, calculates
two network solutions, giving the initial alternating fault current and the decremented alternating
fault current at the user specified fault duty time. The decremented dc offset and total fault currents
are then derived, and results tabulated.
As an alternative to the standard subsystem selection procedure used throughout PSS
E, fault
locations and corresponding breaker operating times may be specified in a Fault Specification Data
File (refer to Section 9.13.5).
Machine parametric data required by activity BKDY is specified in a Breaker Duty Data File.
The sudden application of a short-circuit fault to a power system produces currents for which tran-
sient form is shown in Figure 9-44. In the case of a three-phase fault (simultaneously applied in
each phase), the total fault current in each phase consists of the following:
1. An alternating component that decays from an initial subtransient value to a final steady-
state value.
2. A decaying unidirectional component for which initial amplitude is equal to the difference
between the initial instantaneous value of the alternating component of fault current and the
instantaneous current in the phase just prior to fault application.
Depending upon the standard (e.g., ANSI Standard C37.5 1975 or the International Electrotech-
nical Commission standards) the determination of circuit breaker duty requires the calculation of
either of these values:
The maximum instantaneous value of current in any phase at the instant, a few milli-
seconds after fault initiation, when the circuit breaker contacts separate
Run Activity BKDY - GUI
Fault > Circuit breaker interrupting duty (BKDY)
[Circuit Breaker Interrupting Duty]
Run Line Mode Activity BKDY - CLI
ACTIVITY?
>>BKDY
ENTER OUTPUT DEVICE CODE:
>>
Interrupt Control Codes
AB, CM, DC, FD
Siemens Energy, Inc., Power Technologies International 9-113
PSS
E.
Figure 9-44. Transient Phase Currents in Suddenly Applied Short Circuit
|A
Current
|B
|C
DC
Component
DC
Component
DC
Component
Unbalanced Fault Analysis PSS
E 32.0
Calculating Circuit Breaker Interrupting Duty Program Operation Manual
9-114 Siemens Energy, Inc., Power Technologies International
Figure 9-45. Forms of Expression of Fault Current at Instant of Circuit Breaker Opening
To determine these current amplitudes, the following data must be considered:
The alternating current component results from decaying machine internal flux linkages
behind constant subtransient impedances of the machines.
The unidirectional component is, at the instant of fault application, determined by the
value of the alternating component.
Instant of contact parting
a. Instantaneous Peak Current
b. Equivalent Root-Mean-Square Current
*
Siemens Energy, Inc., Power Technologies International 9-115
PSS
E 32.0
Calculating Circuit Breaker Interrupting Duty Program Operation Manual
9-116 Siemens Energy, Inc., Power Technologies International
In general, an exact expression of the unidirectional fault current would involve a number of k and
a coefficients equal to the number of branches in the network. Their determination would require a
calculation of the eigenvalues and eigenvectors of the differential equations:
[L
net
][sL
net
] + [R
net
][i
net
] = 0
where [R
net
+ sL
net
] is the operational impedance matrix of the complete network. This calculation
is impractical for normal system analysis work, and it is usual to approximate the unidirectional fault
current by:
where
T
s
= L
thev
/ R
thev
where L
thev
and R
thev
are the Thevenin impedance (inductance, resistance) at the point of the fault.
9.13.1 How PSS
E contains a special short-circuit calculation which reports circuit breaker interrupting duty for
three phase faults at all buses in a specified subsystem of the working case. It determines the ampli-
tude of the alternating and unidirectional (dc) components of current flowing in symmetrical faults
and in the branches of the network. The alternating and dc components are calculated as indicated
in the previous section for the instant of fault application and for a specified time after the fault initi-
ation. These component amplitudes are then used to determine the following:
The maximum instantaneous current that could flow in any phase at the specified time
after fault application, assuming that the fault was initiated at such a time, in relation to
the voltage wave that the specified time after application corresponds to a current peak
(Figure 9-45).
The rms value of the current at the specified time after fault application (Figure 9-45).
The maximum instantaneous current, I
total peak
, and rms currents, I
total rms
, are determined by
I
total peak
= I
dc
+ I
ac
where:
I
dc
= Instantaneous amplitude of unidirectional component.
I
ac
= Peak amplitude of alternating component.
It is convenient to define an instantaneous rms value of the alternating current component, I
rms
, by
i
dc
= I
ac
(0)e
-t/T
s
I
total rms
=
\
I
2
+ I
2
dc rms
I
rms
=
\
2
I
ac
Siemens Energy, Inc., Power Technologies International 9-117
PSS
E 32.0
Calculating Circuit Breaker Interrupting Duty Program Operation Manual
9-118 Siemens Energy, Inc., Power Technologies International
Figure 9-46. Relationships Between Machine Time Constants in Radial System
9.13.2 Breaker Duty Data File Contents
The input stream to activity BKDY consists of a series of records in the following format:
I, ID, T'do, T"do, T'qo, T"qo, Xd, Xq, X'd, X'q, X"
where:
I Bus number. Bus I must be present in the working case with a plant sequence
number assigned to it (refer to Plant and Machine Sequence Numbers). No default
is allowed.
ID One- or two-character machine identifier used to distinguish among multiple
machines at a plant (i.e., at a generator bus). ID = 1 by default.
T'
do
d axis transient open circuit time constant. No default is allowed.
T"
do
d axis subtransient open circuit time constant. No default is allowed.
T'
qo
q axis transient open circuit time constant. T'
qo
= 0. by default.
T"
qo
q axis subtransient open circuit time constant. No default is allowed.
X
d
d axis synchronous reactance, entered in pu on MBASE base. No default is
allowed.
X
q
q axis synchronous reactance, entered in pu on MBASE base. No default is
allowed.
X'
d
d axis transient reactance, entered in pu on MBASE base. No default is allowed.
X'
q
q axis transient reactance, entered in pu on MBASE base. X'
q
= 0. by default.
X" Subtransient reactance, entered in pu on MBASE base. No default is allowed.
L
d
L'
d
L
d
T'
do
T
qo
L
d
L'
q
L
q
T'
do
T
qo
Z
e
T'
dz
L'
d
L
e
+
L
d
L
e
+
---------------------- T'
do
= T'
qz
L'
q
L
e
+
L
q
L
e
+
---------------------- T'
qo
=
T
dz
L
d
L
e
+
L'
d
L
e
+
----------------------- T
do
= T
qz
L
q
L
e
+
L'
q
L
e
+
----------------------- T
qo
=
Fault
Siemens Energy, Inc., Power Technologies International 9-119
PSS
E 32.0
Calculating Circuit Breaker Interrupting Duty Program Operation Manual
9-120 Siemens Energy, Inc., Power Technologies International
9.13.5 Operation of Activity BKDY
Prior to initiating the calculation process, the user should ensure that the power flow case to be used
is converged to an acceptable mismatch level using one or more of the conventional Gauss-Seidel
or Newton-Raphson solution methods.
In addition, the user should ensure that:
All generator buses are converted from their power flow representation to a constant
Norton current source representation (see Section 11.2).
Load boundary conditions are converted from the conventional constant MVA charac-
teristic used in power flow calculations to a representation suitable for network
conditions involving abnormally low voltages.
The user has the option to perform a bus ordering. If not, PSS
E 32.0
Calculating Circuit Breaker Interrupting Duty Program Operation Manual
9-122 Siemens Energy, Inc., Power Technologies International
All currents are printed in either amps or per unit, and the complex currents in (1) and (2) above in
either rectangular or polar coordinates, according to the fault analysis output options currently in
effect (refer to Section 3.3.3 and activity OPTN). If the physical units option is enabled and the bus
where base voltage is required for the calculation of the current has no base voltage specified for
it, the current is printed in per unit.
In responding to the output option request, the user may suppress the contributions output
described above and limit the reporting to fault currents.
Similarly, the output report may be extended to provide contributions up to < n > levels away from
the faulted bus. A response of 1 to the output option request causes the output for the faulted bus
to be followed by machine and branch contributions output at all buses connected to it. General-
izing, a response of a positive number < n > results in output for the faulted bus, followed by output
for all buses connected to it, followed by output for all buses two buses away from it, and so on up
to < n > levels removed from the faulted bus. In reporting these remote contributions, only the
currents described in (1) and (2) above are tabulated, and a branch is only reported once: at the
end which is closer to (i.e., fewer levels away from) the faulted bus.
When the multi-section line reporting option is enabled (refer to Section 3.3.3 and activity OPTN),
the far end bus (rather than the closest dummy bus) of each multi-section line connected to the bus
being reported (the at bus) is shown as its connected bus (its from bus). Multi-section lines are iden-
tified with an ampersand ( & ) as the first character of their line identifiers in the branch circuit
identifier column (e.g., &1; refer to Multi-Section Line Grouping Data). When reporting remote
contributions, the dummy buses of multi-section lines are neither reported nor counted in the levels
away calculation; i.e., the far end bus is one level removed from the at bus.
Contributions from a three-winding transformer are identified by the winding number, the trans-
former name and the circuit identifier.
9.13.7 Example: Breaker Duty Results Analysis
Figure 9-47 shows a sample output report using polar coordinates and amperes for clarity. The
upper block of output shows decremented values of current based on a contact parting delay time
of zero; hence it describes the intersection of the envelope of the fully offset current wave with the
t = 0
+
axis. The ac component of current is stated in rms terms, the ratio of rms value to amplitude
is 1.414, and the initial value of the dc (unidirectional) current component is 1.414 18569.7 =
26261.5 A. Also, with no decay taking place, the total peak current is twice the amplitude of the ac
component.
The center block of output specifies the situation at 25 milliseconds after fault initiation. Here the ac
component of current has decayed to 16239.1 A, while the dc component has decayed more rapidly
to 13996.6 A. The final output block, corresponding to 0.5 seconds with the dc component having
decayed to essentially zero, shows the expected 1.414 relationship between rms and peak fault
current, when expressed in amperes.
Siemens Energy, Inc., Power Technologies International 9-123
PSS
E 32.0
Calculating Circuit Breaker Interrupting Duty Program Operation Manual
9-124 Siemens Energy, Inc., Power Technologies International
9.13.8 Application Notes
Activity BKDY uses the same type of network solution as does activity TYSL. A typical sequencing
of activities is:
1. A standard power flow is converged to an acceptable mismatch level using one or more of
activities SOLV, MSLV, FNSL, NSOL, or FDNS. It is strongly recommended that the solved
power flow case be saved in a Saved Case File with activity SAVE.
2. Activity CONG is executed to convert generator buses from their power flow representation
to the constant Norton current source representation used in activity BKDY. See also
Figure 11-4.
3. Activity CONL is executed to convert the load boundary conditions from the conventional
constant MVA characteristic used in power flow calculations to a representation suitable for
network conditions involving abnormally low voltages (see also Section 6.3.13).
4. Optionally, activity ORDR is executed to determine a bus ordering of the admittance matrix
such that its sparsity characteristics are preserved. A new ordering is required because the
execution of activity CONG introduces a row and column into the admittance matrix for each
former Type 3 (swing) bus. If this step is omitted, activity BKDY will perform the ordering
function.
5. Optionally, this converted and ordered case may be saved with activity SAVE if switching
solutions are also to be calculated from this base condition.
6. Activity BKDY is entered.
To apply a three phase fault at a bus, activity BKDY temporarily introduces a fixed shunt with a large
negative susceptance at the bus. When activity BKDY is initiated, if the fixed bus shunt table is full,
an appropriate message is printed and activity BKDY is terminated.
In reading the Breaker Duty Data File, a machine is treated as a salient pole machine if either T'
qo
or X'
q
are specified as zero; a machine is treated as an induction machine if X
d
= X
q
and X'
d
= X'
q
;
otherwise, a round rotor machine is assumed. For any in-service machine in the working case for
which no data record is read, the same d and q axis currents are used in the two network solutions
performed for each fault case.
The value specified for subtransient reactance for each machine must be identical to the imaginary
part of ZSORCE (refer to Generator Data) when generators have been converted with activity
CONG, or to the imaginary part of ZPOS (refer to Positive Sequence Generator Impedance Data)
when generators have been converted with activity CONG with generator conversion using fault anal-
ysis positive sequence machine impedance ZPOS.
Regardless of the method of designating buses to be faulted, those buses which are dummy buses
of multi-section lines are skipped as activity BKDY sequences through fault cases when the multi-
section line reporting option is enabled.
Additional Information
PSS
E GUI Users Guide, Section 15.8, Calculating Circuit Breaker Interrupting Duty
PSS
E contains an analytical
process which is designed to calculate positive-sequence pi-equivalents for these cases. The
process constructs positive-sequence equivalents for the following situations:
One open phase, either grounded or not
Two open phases
Mid-line, line-ground, line-line-ground, or three-phase fault
One breaker open
A series of situations where this activity would be used is shown in Figure 9-48. In this series, a line-
ground fault occurs 40% of the way down the line from bus 151 to bus 152. This is the first unbal-
ance condition. Next, the single-pole breaker at one end of the line opens the faulted phase while
the breaker at the other end of the line remains closed (stuck) for a period of time. This is the second
unbalanced condition. Finally, the second breaker opens to leave an unbalanced condition which is
with two phases closed on the line section. The user, in a stability study, may then want to simulate
the results of such a sequence of events.
Run Activity SPCB - GUI
Fault > Separate pole circuit breaker (SPCB)
[Separate Pole Circuit Breaker]
Run Line Mode Activity SPCB - CLI
ACTIVITY?
>>SPCB
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
None
Unbalanced Fault Analysis PSS
E 32.0
Calculating pi-Equivalent, Single Transmission Line Unbalance Program Operation Manual
9-126 Siemens Energy, Inc., Power Technologies International
Figure 9-48. Examples of Unbalanced Network Conditions Requiring a PI Equivalent
In order to be able to simulate the three unbalanced conditions, in a stability case, the user would
have to replace the positive sequence branch, in the power flow case, with a positive sequence PI
equivalent for each of the three conditions, in sequence.
Prior to entering activity SPCB, the PSS
E prepares the power flow case for the unbalanced network solution in a
manner similar to that used at the initiation of the detailed unbalanced fault anal-
ysis described in Section 9.7.6.
Unbalanced Fault Analysis PSS
E 32.0
Calculating pi-Equivalent, Single Transmission Line Unbalance Program Operation Manual
9-128 Siemens Energy, Inc., Power Technologies International
imposed and should result in a positive sequence pi-equivalent which is equivalent to the positive
sequence branch parameters contained in the working case.
9.14.4 Operation of Activity SPCB
If sequence data has not been read into the working case via activity RESQ, or if activity SEQD had
last been executed with the fault analysis option setting at the two phase option, an appropriate
error message is printed and activity SPCB is terminated.
Activity SPCB calculates the columns of the three sequence impedance matrices corresponding to
the specified buses are calculated in submatrix form.
The user describes the unbalance (refer to Transmission Line Unbalances). The positive sequence
pi-equivalent of the branch unbalance is calculated, and the results are printed (refer to
Section 9.14.5).
9.14.5 Output of Activity SPCB
For each transmission line unbalance calculated by activity SPCB, the following data is tabulated
at the selected output device:
1. The admittance matrix terms corresponding to the branch with the selected unbalance
present.
2. A summary description of the branch unbalance.
3. The positive sequence pi-equivalent. This is presented in the form of a branch impedance
(R + jX) and the equivalent line connected shunts at each end of the branch.
The pi-equivalent calculated by activity SPCB may be used in dynamic simulations to model the
branch unbalance. It should replace the branch parameters used in modeling the branch without
the presence of the unbalance.
Figure 9-49 shows the output for a single-line-to-ground fault applied on the branch from bus 151
to bus 152 at a point 40% along the line from bus 151. The fault impedance is zero. Figures 9-50a
and 9-50b show diagrammatic view of the pi-equivalent.
Siemens Energy, Inc., Power Technologies International 9-129
PSS
E 32.0
Calculating pi-Equivalent, Single Transmission Line Unbalance Program Operation Manual
9-130 Siemens Energy, Inc., Power Technologies International
Figure 9-50. Diagram of pi-Equivalent and the Branch Power Flow Data
9.14.6 Application Notes
Activity SPCB may apply branch unbalances only to transmission lines modeled in full detail in both
the positive (and hence, negative) and zero sequences. That is, the proper positive and zero
sequence values of branch impedances and line charging (and/or line connected shunts) must be
contained in the working case. Transformers, series capacitors, zero impedance lines (refer to
Section ) or jumpers may not be subjected to branch unbalances in activity SPCB.
The transmission line to which the unbalance is to be applied must be modeled such that:
1. Y
i
+
or Y
j
+
are non-zero.
2. Y
i
0
and Y
j
0
are non-zero.
3. Y
i
+
and Y
i
0
are different.
4. Y
j
+
and Y
j
0
and different.
where:
Y
i
+ Is the quantity (line shunt + one-half of total line charging) at the bus i end
of the branch in the positive sequence.
Y
i
0 Is the quantity (line shunt + one-half of total line charging) at the bus i end
of the branch in the zero sequence.
Y
j
+
and Y
j
0 Are the corresponding quantities at the bus j end of the branch.
Y=0,0 Y=0,0
B=1.75 B=1.75
0.0026 0.0460
151 152
B=0.0 B=0.0
151 152
0.00249 0.05390
Y=0.92358, j6.14228 Y=0.61572, j3.51151
a) Initial Line Data
b) pi-Equivalent for Line-Ground Fault 40% Down Line From Bus 151
Siemens Energy, Inc., Power Technologies International 9-131
PSS
E 32.0
Calculating pi-Equivalent, Single Transmission Line Unbalance Program Operation Manual
9-132 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 10-1
Chapter 10
Power Flow Reports
10.1 Analyzing Power Flow Solution Results
Activity Analyzing Power Flow Solution Results
PSS
E 32.0
Analyzing Power Flow Solution Results Program Operation Manual
10-2 Siemens Energy, Inc., Power Technologies International
Power flow results can be provided either in a tabular format or in a graphical format using the one-
line slider format.
In the tabular format, power flow output reports may be organized either numerically by ascending
bus number, or alphabetically by bus name. Selection of ordering by numbers or names is made in
the Program Settings (see activity OPTN) where either the Number output option, or the Extended
Name output option may be chosen. Changing between the Number and Extended Name input
options has no effect on the ordering of power flow reports.
All reports, except those selected by the AREA, ZONE and/or OWNER criteria, are made with
buses appearing in pure numeric or alphabetic order. Power flow results reports selected by one or
more of these criteria order the buses numerically or alphabetically within groupings (see
Section 4.9, Subsystem Reporting). As an example, if output is selected by AREA, with Areas 2 and
6 selected, the report will list all buses in Area 2 first and then all buses in Area 6.
Summary of generator terminal loading conditions on either all, or
only overloaded, generators.
Bus subsystem
Summary of generator bus loading conditions on either all, or only
var-limited, generators.
Bus subsystem
Summary of controlling transformers violations Bus subsystem
Generator reactive power capability Bus subsystem
Regulated bus violations and/or conflicts Bus subsystem
Reports on Comparing Power Flow Cases
Report on differences between the working case and a specified
Saved Case
Bus subsystem
Report area, zone, owner, or complete system totals for the
working case and a specified Saved Case
Area, zone or owner
subsystem, as appropriate
Report subsystem tie branch differences between the working
case and a specified Saved Case
Bus subsystem
Table 10-1. Summary of Available PSS
E 32.0
Producing a Standard Power Flow Solution Report Program Operation Manual
10-4 Siemens Energy, Inc., Power Technologies International
that the plant reactive power output is at or beyond the total plant upper reactive power limit, L indi-
cates that it is at or below the total plant lower reactive power limit, and R indicates that it is within
limits. Note that only plant conditions are tabulated in activity POUT. If more than one machine is
modeled at the plant, individual machine conditions may be examined using activities such as LIST,
GEOL, and GCAP (see also Generator Unit Data).
These lines are followed by any non-zero constant power load, constant current load, constant
admittance load, fixed shunt elements, and switched shunt at the bus, with the appropriate identifier
at the left of each line. Note that only totals by load characteristic are tabulated in activity POUT. If
more than one load and/or fixed bus shunt is modeled at the bus, individual load and shunt quanti-
ties may be examined using activities such as LIST and EXAM (see also Generator Unit Data and
Fixed Bus Shunt Data).
Only plant conditions are tabulated. If more than one machine is modeled at the plant, indi-
vidual machine conditions may be examined using the range checking facilities described in
Section 10.15.
FACTS Devices
Output for FACTS devices appears in the bus output block immediately following the bus quantities
output described above, and before output for dc lines and ac branches. In-service FACTS devices
connected to the bus are reported in FACTS device name alphabetical order. If the out-of-service
branch reporting program option setting (refer to Section 3.3.3 and activity OPTN) is disabled, only
in-service FACTS devices are reported. If this option is enabled, out-of-service FACTS devices at
in-service buses are also reported; X is displayed in the various loading and series voltage fields.
For each FACTS device for which the bus being reported is the sending bus of an IPFC master or
slave device, the following data pertaining to the devices active power transfer to its companion
IPFC device is printed:
1. An identifier indicating the type of the companion IPFC device (IPFC MASTER or IPFC
SLAVE).
2. The identifier IPF; this is printed in the circuit identifier column.
3. The active power flowing to the companion IPFC device. If the bus being reported is the
IPFC master and the active power transfer is being held at its limit, its value is followed by
the tag HI.
4. The FACTS device name.
Except for IPFC devices for which the shunt element is 0.0, for each FACTS device for which the
bus being reported is the sending bus, the following data pertaining to the devices shunt element
is printed:
1. An identifier indicating the type of FACTS device shunt element and/or active power transfer
being reported (STATCON SHUNT, SSSC SHUNT, UPFC SHUNT, or IPFC SHUNT).
2. An identifier indicating the type of FACTS device being reported: STA (for a Statcon or
Statcom), SSS (for an SSSC), UPF (for a UPFC) or IPF (for an IPFC); this is printed in the
circuit identifier column.
Siemens Energy, Inc., Power Technologies International 10-5
PSS
E 32.0
Producing a Standard Power Flow Solution Report Program Operation Manual
10-6 Siemens Energy, Inc., Power Technologies International
The following data is printed in the output block of each two-terminal and multi-terminal dc line
converter bus:
1. For two-terminal lines, the number, name, and base voltage of the other converter terminal
bus (to bus); for multi-terminal lines, the number and name of the dc bus to which the ac
converter bus is connected, with the identifier (DC) in the base voltage column.
2. An identifier indicating the type of dc line being reported: 2D (for two-terminal) or MD (for
multi-terminal), and an identifier indicating the type of converter at the from bus: R (for a
rectifier) or I (for an inverter); this is printed in the circuit identifier column.
3. The ac power flowing into the dc line.
4. The converter transformer off-nominal turns ratio, TAPR (or TAPI), followed by a two-char-
acter tag, which is either HI or LO if the ratio is at its high or low limit, respectively; LK if dc
taps were locked during the last power flow solution activity, or if an ac transformer (rather
than this converter transformer) is controlling a dc line quantity; or RG if the ratio is in regu-
lating range.
5. The value of converter angle followed by one of the tags RG, HI or LO if the angle is within
its limits, at or above its nominal high limit, or at or below its steady-state low limit,
respectively.
6. DC line losses calculated as the algebraic sum of the powers flowing into the line from its
converter buses.
7. For two-terminal lines, the numbers and names of the area and zone in which the other
converter bus (to bus) is located. For multi-terminal lines, the numbers and names of the
area and zone in which the dc bus to which the ac converter bus is connected is located.
8. The dc line name.
The following data is printed in the output block of each VSC dc line converter bus:
1. The number, name, and base voltage of the other converter terminal bus (to bus).
2. The identifier VSC; this is printed in the circuit identifier column.
3. The ac power flowing into the dc converter.
4. The percent of MVA rating, where the rating is taken as the more restrictive of IMAX
converted to MVA and SMAX (refer to Voltage Source Converter (VSC) DC Transmission
Line Data).
5. DC line losses calculated as the algebraic sum of the powers flowing into the line from its
converter buses.
6. The numbers and names of the area and zone in which the other converter bus is located.
7. The VSC dc line name.
Figure 10-1 contains partial output from activity POUT for a system in which bus 201 is the rectifier
bus of a two-terminal dc line, and bus 161 is the inverter bus. The output is shown with the numbers
output option in effect.
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
1
0
-
7
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
R
e
p
o
r
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
r
o
d
u
c
i
n
g
a
S
t
a
n
d
a
r
d
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
R
e
p
o
r
t
Figure 10-1. Example Output From Activity POUT
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE WED, JUN 27 2007 16:19
ADDITION OF DC LINE TO BASE CASE DEMO LOAD FLOW RATING %MVA FOR TRANSFORMERS
FOR PSSE MANUAL SET A % I FOR NON-TRANSFORMER BRANCHES
BUS 201 HYDRO 500.00 CKT MW MVAR MVA % 0.9913PU 2.55 X--- LOSSES ---X X---- AREA -----X X---- ZONE -----X 201
FROM GENERATION 600.0 400.0H 721.1 99 495.65KV MW MVAR 2 LIGHTCO 2
TO SHUNT 0.0 294.8 294.8
TO 161 INVJCT 18.500 2DR 641.8 286.2 702.7 1.0000RG 10.94RG 41.76 568.06 1 FLAPCO 1 "1"
TO 151 NUCPANT 500.00 1 -724.8 -51.1 726.6 61 5.35 80.20 1 FLAPCO 1
TO 202 EAST500 500.00 1 315.1 -142.3 345.8 29 2.06 25.76 2 LIGHTCO 2
TO 204 SUB500 500.00 1 367.9 12.5 368.1 31 4.69 46.92 2 LIGHTCO 2
BUS 161 INVJCT 18.500 CKT MW MVAR MVA % 0.9730PU -1.60 X--- LOSSES ---X X---- AREA -----X X---- ZONE -----X 161
18.000KV MW MVAR 1 FLAPCO 1
TO 201 HYDRO 500.00 2DI -600.0 281.9 662.9 0.9875RG 19.08RG 41.76 568.06 2 LIGHTCO 2 "1"
TO 154 DOWNTN 230.00 1 600.0 78.4 605.1 101 1.0000UN 0.00 48.35 1 FLAPCO 1
TO 162 INVTER 18.500 1 0.0 -360.3 360.3 0.00 13.71 1 FLAPCO 1
Power Flow Reports PSS
E 32.0
Producing a Standard Power Flow Solution Report Program Operation Manual
10-8 Siemens Energy, Inc., Power Technologies International
Branch Quantities
Following the output described above, flows for each ac branch connected to the bus are tabulated.
If the out-of-service branch reporting program option setting (refer to Section 3.3.3 and activity
OPTN) is disabled, only in-service branches are reported. If this option setting is enabled, out-of-
service branches at in-service buses are also reported; an X is displayed in the various loading and
losses fields.
Following the output described above, flows for each in-service ac branch connected to the bus are
tabulated.
For non-transformer branches and two-winding transformers, the output line contains the to bus
number, name, and base voltage followed by the branch circuit identifier. For three-winding trans-
formers, the output line contains the string 3WNDTR in the bus number column, the transformer
name in the bus name column, and the winding number in the base voltage column, followed by the
transformer circuit identifier; if the three-winding transformer to bus reporting option is enabled, two
additional lines, containing the bus numbers, names, and base voltages of the two buses connected
to the from bus by the three-winding transformer, are printed.
The active and reactive power flow on the branch is printed as power leaving the from bus (i.e., posi-
tive for outgoing and negative for incoming); MVA flow is also printed.
The percent loading, based on the rating set established as the default rating set program option
setting is then printed (refer to Section 3.3.3, activity OPTN, Non-Transformer Branch Data, and
Transformer Data). For transformers, either percent current or percent MVA loading is reported,
according to the transformer percent loading units program option setting. Similarly, for non-trans-
former branches, either percent current or percent MVA loading is reported, according to the non-
transformer branch percent loading units program option setting.
Branch losses which are printed are taken as I
2
R and I
2
X losses and exclude the line charging, line
connected shunt, and magnetizing admittance components. For three-winding transformers, if the
three-winding transformer to bus reporting option is disabled, total losses on all three windings are
printed on the output line for the three-winding transformer; if this option is enabled, losses on each
winding are listed separately on the line identifying the bus to which the winding is connected.
The number and name of the area and zone in which the to bus is located are printed for non-trans-
former branches and for two-winding transformers. For three-winding transformers, if the three-
winding transformer to bus reporting option is enabled, the numbers and names of the areas and
zones of the two buses connected to the from bus by the three-winding transformer are listed on
the lines identifying them.
For transformers, the turns ratio of the winding connected to the from bus is printed following the
percent loading. A two-character tag is printed adjacent to the ratio, which has the following
significance:
HI The from bus is connected to the Winding 1 side of this regulating two-winding
transformer or to a regulating winding of this three-winding transformer, and the
off-nominal turns ratio is at or beyond its high limit.
LO The from bus is connected to the Winding 1 side of this regulating two-winding
transformer or to a regulating winding of this three-winding transformer, and the
off-nominal turns ratio is at or below its low limit.
Siemens Energy, Inc., Power Technologies International 10-9
PSS
E 32.0
Producing a Standard Power Flow Solution Report Program Operation Manual
10-10 Siemens Energy, Inc., Power Technologies International
Figure 10-2. Power Flow Output for Branches
Fault MVA
For buses where voltage magnitude is less than 10% (such as faulted buses), the quantity FAULT
MVA is printed. This quantity is intended for use following the solution of a balanced fault with
activity TYSL. It is computed using the fixed bus shunt and the bus voltage; as such, it is normally
the sum of fault MVA and the MVA consumed by the fixed bus shunt, if any, on the bus.
Under three phase fault conditions, the solved voltage magnitude at the faulted bus, and usually at
nearby buses, is very small (e.g., 10
-6
pu at the faulted bus). Hence, the voltage correction applied
during the final TYSL iteration may be a large fraction of the solved voltage. Therefore, to ensure
an accurate reporting of FAULT MVA, the acceleration factor applied during the final TYSL iteration
should be 1.0. If the solution requires deceleration to achieve convergence, then, after it converges,
activity TYSL should be repeated one final time with the acceleration factor reset to unity.
Additional Information
PSS
E GUI Users Guide, Section 16.3.1, Producing a Standard Power Flow Solution Report
PSS
E
3
2
.
0
P
r
o
d
u
c
i
n
g
a
W
i
d
e
-
F
o
r
m
a
t
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
R
e
p
o
r
t
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 10-3. Wide Format Power Flow Output including Branch Currents
Siemens Energy, Inc., Power Technologies International 10-13
PSS
E 32.0
Producing a Wide-Format Power Flow Solution Report Program Operation Manual
10-14 Siemens Energy, Inc., Power Technologies International
4. The FACTS device name printed in the transformer ratio and angle columns.
Except for IPFC devices for which the shunt element is 0.0, for each FACTS device for which the
bus being reported is the sending bus, the following data pertaining to the devices shunt element
is printed:
1. An identifier indicating the type of FACTS device shunt element and/or active power transfer
being reported (STATCON SHUNT, SSSC SHUNT, UPFC SHUNT, or IPFC SHUNT).
2. An identifier indicating the type of FACTS device being reported: STA (for a Statcon or
Statcom), SSS (for an SSSC), UPF (for a UPFC) or IPF (for an IPFC); this is printed in the
circuit identifier column.
3. Unless the device being reported is an IPFC, the active power being exchanged between
the shunt and series element.
4. The reactive power being absorbed by the shunt element.
5. The FACTS device name printed in the transformer ratio and angle columns.
6. The rating and percent loading of the shunt element.
If the FACTS device contains a series element, the following data pertaining to it is printed in the
output blocks of its sending and terminal buses:
1. The number, name, base voltage, and area of the other endpoint bus (to bus).
2. An identifier indicating the type of FACTS device being reported: SSS (for an SSSC), UPF
(for a UPFC) or IPF (for an IPFC); this is printed in the circuit identifier column.
3. The power flowing into the series element at the from bus end.
4. The magnitude and phase of the series voltage. If the series voltage magnitude is being held
at its limit (control modes 1, 5 and 6) or if the series voltage magnitude exceeds VSMX
(control modes 2, 3, 4, 7 or 8), its value is followed by the tag H. Otherwise, the tag R is
printed.
5. The percent current loading and rating.
DC Lines
Output for dc transmission lines appears on the right side of the bus output block immediately
following any FACTS device output described above, and before output for ac branches. Two-
terminal, multi-terminal, and VSC dc lines connected to the bus are reported in dc line name alpha-
betical order, with output for two-terminal lines printed first, followed by output for multi-terminal
lines, followed by output for VSC dc lines. If the out-of-service branch reporting program option
setting (refer to Section 3.3.3 and activity OPTN) is disabled, only in-service dc lines are reported.
If this option is enabled, out-of-service dc lines at in-service buses are also reported; an X is
displayed in the various loading fields and other fields indicating dc line conditions.
The power flowing into a dc line is the apparent ac system complex load as seen at the converter
bus. Refer to Sections 6.4.7 and 6.4.9 of the PSS
E 32.0
Producing a Wide-Format Power Flow Solution Report Program Operation Manual
10-16 Siemens Energy, Inc., Power Technologies International
Figure 10-4. Example Output From Activity LOUT
Branch Quantities
Following the output described above, flows for each ac branch connected to the bus are tabulated
on the right side of the bus output block. If the out-of-service branch reporting program option
setting (refer to Section 3.3.3 and activity OPTN) is disabled, only in-service branches are reported.
If this option is enabled, out-of-service branches at in-service buses are also reported; an X is
displayed in the loading fields.
Each branch output line for non-transformer branches and for two-winding transformers contains
the to bus number, name, and base voltage, followed by the number of the area in which the to bus
is located and the branch circuit identifier. For three-winding transformers, the output line contains
the string 3WNDTR in the bus number column, the transformer name in the bus name column, and
the winding number in the base voltage column, followed by the transformer circuit identifier; if the
three-winding transformer to bus reporting option is enabled, two additional lines, containing the bus
numbers, names, and base voltages of the two buses connected to the from bus by the three-
winding transformer, are printed, followed by the number of the area in which the to bus is located.
The active and reactive power flow on the branch is printed as power leaving the from bus (i.e., posi-
tive for outgoing and negative for incoming).
The percent loading, based on the rating set established as the default rating set program option
setting (refer to Section 3.3.3 and activity OPTN) and the corresponding rating are printed on the
far right-hand side of the line. For transformers, either percent current or percent MVA loading is
reported, according to the transformer percent loading units program option setting. Similarly, for
non-transformer branches, either percent current or percent MVA loading is reported, according to
the non-transformer branch percent loading units program option setting.
For transformers, the turns ratio of the winding connected to the from bus is printed. A two-character
tag is printed adjacent to the ratio which has the following significance:
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE THU, JUN 28 2007 8:31
ADDITION OF DC LINE TO BASE CASE DEMO LOAD FLOW %MVA FOR TRANSFORMERS
FOR PSSE MANUAL % I FOR NON-TRANSFORMER BRANCHES
X------ FROM BUS ------X AREA VOLT GEN LOAD SHUNT X---------TO BUS----------X TRANSFORMER RATING
X--NAME--X BASKV BUS# ZONE PU/KV ANGLE MW/MVAR MW/MVAR MW/MVAR X--NAME--X BASKV BUS# AREA CKT MW MVAR RATIO ANGLE % SET A
HYDRO 500.00 201 2 0.9913 2.5 600.0 0.0 0.0 -------------------------------------------------------------------------
2 495.65 400.0H 0.0 294.8 INVJCT 18.500 161 1 2DR 641.8 286.2 1.000RG 10.9RG "1"
EAST500 500.00 202 2 1 315.1 -142.3 29 1200
NUCPANT 500.00 151 1 1 -724.8 -51.1 61 1200
SUB500 500.00 204 2 1 367.9 12.5 31 1200
INVJCT 18.500 161 1 0.9730 -1.6 0.0 0.0 0.0 -------------------------------------------------------------------------
1 18.000 0.0 0.0 0.0 HYDRO 500.00 201 2 2DI -600.0 281.9 0.987RG 19.1RG "1"
DOWNTN 230.00 154 1 1 600.0 78.4 1.000UN 101 600
INVTER 18.500 162 1 1 0.0 -360.3
HI The from bus is connected to the Winding 1 side of this regulating two-winding trans-
former or to a regulating winding of this three-winding transformer, and the off-nominal
turns ratio is at or beyond its high limit.
LO The from bus is connected to the Winding 1 side of this regulating two-winding trans-
former or to a regulating winding of this three-winding transformer, and the off-nominal
turns ratio is at or below its low limit.
RG The from bus is connected to the Winding 1 side of this regulating two-winding trans-
former or to a regulating winding of this three-winding transformer, its adjustment
control mode is set to +1 or +2, the automatic tap ratio adjustment was enabled during
the last power flow solution activity, and the off-nominal turns ratio is within its limits.
Siemens Energy, Inc., Power Technologies International 10-17
PSS
E GUI Users Guide, Section 16.3.2, Wide-Format Power Flow Solution Report
PSS
E 32.0
Producing a Wide-Format Power Flow Solution Report in Amps Program Operation Manual
10-18 Siemens Energy, Inc., Power Technologies International
10.4 Producing a Wide-Format Power Flow Solution Report in
Amps
Activity LAMP
The power flow output activity LAMP prints power flow solution output for the working case. The
data tabulated for each bus printed includes bus voltage and phase angle, generator power output,
loads, bus shunt elements, flows into all connected branches and FACTS devices, and branch
current loadings in amps. Bus mismatch is printed for any bus for which it exceeds 0.5 MVA or kVA,
according to the power output option in effect (refer to Section 3.3.3 and activity OPTN). For buses
where voltage magnitude is less than 10% (such as faulted buses), the quantity FAULT MVA is
printed (refer to Fault MVA).
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. The output report is generated with specified buses
ordered according to the user option, in ascending bus number order (using the numbers output
option) or alphabetical order (using the names output option) (refer to Section 4.9).
The star point buses of three-winding transformers (refer to Transformer Data) are not reported.
When the multi-section line reporting option is enabled (refer to Section 3.3.3 and activity OPTN),
the interior dummy buses of multi-section line groupings (refer to Multi-Section Line Grouping Data)
are not reported.
The output listing of activity LAMP may be terminated by entering the AB interrupt control code.
Activity LAMP formats its report in traditional power flow output style, with bus quantities on the left
side of the page and branch data shown on the right side.
Bus Quantities
The bus identifiers and boundary conditions for each bus reported in activity LAMP are printed on
two lines on the left side of the bus output block. The bus identifiers of bus number, name, and base
voltage are listed followed by the number of the area in which the bus is located and the zone
number directly below it on the second line.
The bus voltage (in pu) and phase angle (in degrees) are printed; if the bus base voltage is specified
for the bus, the bus voltage in kV is printed directly below the pu voltage on the second line. The
generation, load, and shunt at the bus are printed, with active power shown on the first line and
Run Activity LAMP - GUI
Power Flow > Reports > Bus based reports
[Bus Based Reports]
OPTION: Powerflow output / Wide format output and Output with amps both checked
Run Line Mode Activity LAMP - CLI
ACTIVITY?
>>LAMP
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 10-19
PSS
E 32.0
Producing a Wide-Format Power Flow Solution Report in Amps Program Operation Manual
10-20 Siemens Energy, Inc., Power Technologies International
If the FACTS device contains a series element, the following data pertaining to it is printed in the
output blocks of its sending and terminal buses:
The number, name, base voltage, and area of the other endpoint bus (to bus).
An identifier indicating the type of FACTS device being reported: SSS (for an SSSC),
UPF (for a UPFC) or IPF (for an IPFC); this is printed in the circuit identifier column.
The power flowing into the series element at the from bus end.
The magnitude and phase of the series voltage. If the series voltage magnitude is being
held at its limit (control modes 1, 5 and 6) or if the series voltage magnitude exceeds
VSMX (control modes 2, 3, 4, 7 or 8), its value is followed by the tag H. Otherwise, the
tag R is printed.
The total current loading magnitude in amperes if the from bus has its base voltage
specified.
The rating in amperes and percent loading of the series element. If no from bus base
voltage or series current limit was specified, these columns are left blank.
DC Lines
Output for dc transmission lines appears on the right side of the bus output block immediately
following any FACTS device output described above, and before output for ac branches. Two-
terminal, multi-terminal, and VSC dc lines connected to the bus are reported in dc line name alpha-
betical order, with output for two-terminal lines printed first, followed by output for multi-terminal
lines, followed by output for VSC dc lines. If the out-of-service branch reporting program option
setting (refer to Section 3.3.3 and activity OPTN) is disabled, only in-service dc lines are reported.
If this option setting is enabled, out-of-service dc lines at in-service buses are also reported; an X
is displayed in the various loading fields and other fields indicating dc line conditions.
The power flowing into a dc line is the apparent ac system complex load as seen at the converter
bus. Refer to Sections 6.4.7 and 6.4.9 of the PSS
E
3
2
.
0
P
r
o
d
u
c
i
n
g
a
W
i
d
e
-
F
o
r
m
a
t
P
o
w
e
r
F
l
o
w
S
o
l
u
t
i
o
n
R
e
p
o
r
t
i
n
A
m
p
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 10-5. Example Output From Activity LAMP
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSS(tm)E THU, JUN 28 2007 14:20
ADDITION OF DC LINE TO BASE CASE DEMO LOAD FLOW %MVA FOR TRANSFORMERS
FOR PSSE MANUAL % I FOR NON-TRANSFORMER BRANCHES
X------ FROM BUS ------X AREA VOLT GEN LOAD SHUNT X--------- TO BUS ----------X TRANSFORMER RATING
BUS# X-- NAME --X BASKV ZONE PU/KV ANGLE MW/MVAR MW/MVAR MW/MVAR BUS# X-- NAME --X BASKV AREA CKT MW MVAR RATIO ANGLE AMPS % SET A
201 HYDRO 500.00 2 0.9913 2.5 600.0 0.0 0.0 -------------------------------------------------------------------------------
2 495.65 400.0H 0.0 294.8 161 INVJCT 18.500 1 2DR 641.8 286.2 1.000RG 10.9RG 818 "1"
151 NUCPANT 500.00 1 1 -724.8 -51.1 846 61 1386A
202 EAST500 500.00 2 1 315.1 -142.3 403 29 1386A
204 SUB500 500.00 2 1 367.9 12.5 429 31 1386A
161 INVJCT 18.500 1 0.9730 -1.6 0.0 0.0 0.0 ------------------------------------------------------------------------------
1 18.000 0.0 0.0 0.0 201 HYDRO 500.00 2 2DI -600.0 281.9 0.987RG 19.1RG 21263 "1"
154 DOWNTN 230.00 1 1 600.0 78.4 1.000UN 19409 101 600M
162 INVTER 18.500 1 1 0.0 -360.3 11556
Siemens Energy, Inc., Power Technologies International 10-23
PSS
E 32.0
Producing a Wide-Format Power Flow Solution Report in Amps Program Operation Manual
10-24 Siemens Energy, Inc., Power Technologies International
Except for the tags DC and UN, phase shifters are handled in a similar manner. For single section
two-winding transformers with non-zero phase shift angle on the Winding 1 side, no indication of
phase shift is printed in the output block of the Winding 2 side bus.
When the multi-section line reporting option is enabled (refer to Section 3.3.3 and activity OPTN),
the far end to bus (rather than the closest dummy bus) of each multi-section line connected to the
from bus is shown as its to bus. Multi-section lines are identified with an ampersand ( & ) as the first
character of their line identifiers in the branch circuit identifier column (e.g., &1). Transformer infor-
mation is shown only if the line section adjacent to the from bus is a transformer branch, and the
data applies to the winding adjacent to the from bus.
If any of the non-transformer branches reported have a non-zero line shunt at the from bus end, or
if Winding 1 of any transformer branch connected to the from bus has non-zero magnetizing admit-
tance, and the line shunt reporting option is enabled (refer to Section 3.3.3 and activity OPTN), the
branch output lines are followed by lines reporting powers corresponding to each of these admit-
tances. Current magnitudes in amperes are also printed if the from bus has a non-zero base voltage
specified for it. Note that, regardless of the setting of this option, the branch flows reported always
include these components.
Fault MVA
For buses where voltage magnitude is less than 10% (such as faulted buses), the quantity FAULT
MVA is printed. This quantity is intended for use following the solution of a balanced fault with
activity TYSL. It is computed using the fixed bus shunt and the bus voltage; as such, it is normally
the sum of fault MVA and the MVA consumed by the fixed bus shunt, if any, on the bus.
Under three phase fault conditions, the solved voltage magnitude at the faulted bus, and usually at
nearby buses, is very small (e.g., 10
-6
pu at the faulted bus). Hence, the voltage correction applied
during the final TYSL iteration may be a large fraction of the solved voltage. Therefore, to ensure
an accurate reporting of FAULT MVA, the acceleration factor applied during the final TYSL iteration
should be 1.0. If the solution requires deceleration to achieve convergence, then, after it converges,
activity TYSL should be repeated one final time with the acceleration factor reset to unity.
DC The from bus is the Winding 1 side of this two-winding transformer which is regu-
lating alpha, gamma, or dc voltage of a dc line; its adjustment control mode is set to
+4; dc tap adjustment was enabled during the last power flow solution activity; and
the off-nominal turns ratio is within its limits.
LK The from bus is connected to the Winding 1 side of this two-winding transformer or
to any winding of this three-winding transformer, and either this transformer winding
is not a tap changing transformer winding, its adjustment control mode is to zero or
negative, or the automatic tap ratio adjustment was disabled during the last power
flow solution activity.
UN The from bus is not the Winding 1 side of this two-winding transformer.
Additional Information
PSS
E 32.0
Summarizing Subsystem Conditions Program Operation Manual
10-26 Siemens Energy, Inc., Power Technologies International
Following the two-line case heading, the output report of activity SUBS contains a description of the
subsystem where conditions are being summarized. This is followed by the five categories of data
described in the following paragraphs.
System Swing Bus Summary
Each Type 3 bus in the subsystem being reported is listed, one per line. Swing buses are tabulated
in ascending numerical order when the numbers output option is in effect and in alphabetical order
using the names output option. The bus number, name, and base voltage are printed, along with
the number and name of the interchange area in which it is located and the number and name of
the zone to which it is assigned. The total plant active and reactive power output are printed followed
by the total plant MBASE (i.e., sum of the MBASEs of the in-service machines at the plant).
Area Slack Bus Summary
Those buses which are area slack buses for area interchange control purposes are tabulated one
per line in ascending area number order. The area number and name are printed, followed by the
area slack bus number, name, and base voltage and the number and name of the zone in which it
is located. Total plant active and reactive power output and total plant MBASE are tabulated. When
processing a subsystem, only those area slack buses which are included in the specified subsystem
are reported.
Component Totals
The total number of in-service components in the subsystem is listed in the following categories:
Buses.
Plants.
Machines, including wind machines.
Fixed shunts.
Switched shunts.
Loads.
AC branches, including transformers.
Two-winding transformer branches.
DC lines.
FACTS devices.
The total number of plants is calculated as the number of Type 2 and 3 buses in the subsystem, and
the number of machines is the number of in-service machines at these buses. The total number of
loads is calculated as the number of in-service loads at Type 1, 2, and 3 buses in the subsystem.
The totals of ac branches, transformers, and dc lines include those ties from the specified
subsystem to other subsystems in the working case with a nonmetered end bus is in the specified
subsystem; the total number of FACTS devices are those where the sending bus is in the specified
subsystem (refer to Subsystem Totals and Branch Totals by Voltage Level).
The total number of buses does not include the star point bus of any three-winding transformer
where the nonmetered end bus is in the specified subsystem. Each three-winding transformer
where the nonmetered end bus is in the specified subsystem contributes one to the totals of ac
branches and transformers; the three two-winding transformers comprising each such three-
winding transformer do not contribute to these totals.
Siemens Energy, Inc., Power Technologies International 10-27
PSS
E 32.0
Summarizing Subsystem Conditions Program Operation Manual
10-28 Siemens Energy, Inc., Power Technologies International
The subsystem is specified by base voltage and the low end of the voltage range is
greater than zero.
The subsystem is specified by bus and at least one converter bus of the multi-terminal
line is not in the designated subsystem.
Similarly, losses through the grounding resistance of the second dc bus of the converters of a multi-
terminal line are included in the loss totals when activity SUBS processes all buses in the working
case. When a subsystem of the working case is being reported, losses through an individual IDC2
ground path are included or omitted using criteria corresponding to that given for dc links above.
The ac branch losses are taken as I
2
R and I
2
X losses and exclude the line charging and line
connected shunt components. Transformer losses exclude magnetizing admittance components.
When a designated subsystem is being tabulated, the losses, line shunt, and charging components
on any tie line to another subsystem are included in the branch totals if the nonmetered end bus is
in the subsystem being reported (i.e., subsystem boundaries are at the metered end of each tie
branch). For series FACTS devices, terminal end metering is assumed.
Two- and three-winding transformers have their loss and magnetizing admittance contributions
assigned to the voltage level of the Winding 2 side bus. If the second winding of a three-winding
transformer is out-of-service with the remaining windings in-service (i.e., its status value is 2), its
loss and line shunt contributions are assigned to the voltage level of the Winding 3 side bus.
Non-transformer branches with different base voltages at the two ends of the line generate an
alarm, and their contributions are assigned to the lower of the two base voltages. If a base voltage
is specified at only one end of such a branch, its contributions are assigned to that voltage level.
Be careful not to confuse the roles of the nonmetered end bus and the Winding 2 side bus of trans-
formers. The nonmetered end bus of all branches, including transformers, is used to determine if
the branch is included in the subsystem being reported. If a transformer is in the subsystem, the
voltage level of the Winding 2 side bus determines the voltage level totals to which the transformer
contributes.
Additional Information
PSS
E 32.0
Summarizing Load Reduction Program Operation Manual
10-30 Siemens Energy, Inc., Power Technologies International
If the load has a non-zero constant current component:
- The specified complex nominal constant current load.
- The complex nominal constant current load at the present bus voltage.
- The complex nominal constant current load reduction.
Totals of reported quantities are tabulated at the end of each subsystem grouping. An example is
provided in Figure 10-6.
10.6.2 Application Notes
Note that values listed as constant current load are nominal values (i.e., at unity voltage, as shown
in activities such as LIST and in the [Spreadsheet] View). Thus, the values shown as actual constant
current loads are not identical to those reported in the various power flow solution reporting activi-
ties that report loadings in MVA. Clearly, to obtain the MVA corresponding to the reduced current
loadings, multiply the complex value shown as actual nominal constant current load by the voltage
magnitude at the bus.
PQBRAK may be modified using the data changing activity CHNG or the [Solution Parameters]
dialog.
Additional Information
PSS
E
3
2
.
0
P
o
w
e
r
F
l
o
w
R
e
p
o
r
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
S
u
m
m
a
r
i
z
i
n
g
L
o
a
d
R
e
d
u
c
t
i
o
n
Figure 10-6. Example of Load Reduction Report
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE TUE, FEB 24 2009 9:40
PSS/E PROGRAM APPLICATION GUIDE EXAMPLE
BASE CASE INCLUDING SEQUENCE DATA
LOAD REDUCTION FOR VOLTAGE < PQBRAK=0.700 (MVA LOAD) & 0.5 (CURRENT LOAD)
I X--------------CONSTANT MVA LOAD--------------X X--------NOMINAL CONSTANT CURRENT LOAD--------X
BUS# X-- NAME --X BASKV D VOLTAGE SCHEDULED ACTUAL REDUCTION SCHEDULED ACTUAL REDUCTION
153 MID230 230.00 1 0.3361 60.0 30.0 30.5 15.2 29.5 14.8 61.1 30.6 56.1 28.1 5.0 2.5
154 DOWNTN 230.00 1 0.0000 180.0 135.0 0.0 0.0 180.0 135.0 195.4 146.6 0.0 0.0 195.4 146.6
154 DOWNTN 230.00 2 0.0000 120.0 105.0 0.0 0.0 120.0 105.0 130.3 114.0 0.0 0.0 130.3 114.0
203 EAST230 230.00 1 0.2492 90.0 45.0 30.0 15.0 60.0 30.0 94.3 47.2 75.6 37.8 18.7 9.4
205 SUB230 230.00 1 0.1373 360.0 210.0 47.2 27.6 312.8 182.4 386.3 225.3 214.8 125.3 171.5 100.1
3005 WEST 230.00 1 0.4198 30.0 15.0 20.2 10.1 9.8 4.9 30.1 15.1 29.5 14.8 0.6 0.3
3007 RURAL 230.00 1 0.3116 60.0 22.5 27.5 10.3 32.5 12.2 62.4 23.4 55.6 20.8 6.8 2.6
3008 CATDOG 230.00 1 0.2262 60.0 22.5 17.3 6.5 42.7 16.0 63.0 23.6 48.0 18.0 15.1 5.7
TOTALS 960.0 585.0 172.7 84.7 787.3 500.3 1023.0 625.7 479.5 244.7 543.5 381.0
Power Flow Reports PSS
E 32.0
Summarizing Area Totals Program Operation Manual
10-32 Siemens Energy, Inc., Power Technologies International
10.7 Summarizing Area Totals
Activity AREA
The area summary activity AREA provides a tabulation by interchange area of the desired area net
interchange, along with area totals of:
The AREA_2 API tabulates totals by area. The output block for each area and for system totals
consists of two lines: the first contains active power totals and the second the reactive power totals.
The AREA_ZONE API tabulates totals by area along with subtotals by zone for each reported area.
The output block for each area consists of one line for each zone in the area, followed by one line
of area totals.
In both of these reports, the area number and name is printed for each area block reported.
The user specifies the areas to be reported (refer to Section 4.8). Totals for the specified areas are
printed in ascending area number order, followed by the sums of the totals of those areas.
Recall that buses and loads both have area assignments associated with them (refer to Bus Data
and Load Data). One of three load reporting options may be selected for calculating each area's
total load:
Calculate total area load by summing all in-service loads connected to buses that are
assigned to the area. The area assignment of the load is not considered.
Calculate total area load by summing all in-service loads that are assigned to the area.
The area assignment of the bus to which it is connected is not considered.
Calculate three subtotals of area load:
Run Activity AREA - GUI
Power Flow > Reports > Area / owner / zone totals
[Area / Owner / Zone Totals]
OPTION: Report on Areas
Run Line Mode Activity AREA - CLI
ACTIVITY?
>>AREA
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Generation
Load
Bus connected shunt elements, including fixed
shunts, switched shunts and shunt elements of
FACTS devices
Line connected shunt elements, including
magnetizing admittance of transformers
Line charging
Net interchange
Losses
Siemens Energy, Inc., Power Technologies International 10-33
PSS
E 32.0
Summarizing Area Totals Program Operation Manual
10-34 Siemens Energy, Inc., Power Technologies International
A three-winding transformer is considered to be a tie line when the three buses which is connects
are not in the same area. Tie flows are derived from the flows into the transformer at the two
metered ends.
A two-terminal dc transmission line is considered to be a tie line when the converter station buses
are located in different areas. The tie flow is taken as the power flowing into the dc converter from
the ac system at the metered end. For multi-terminal dc lines, if a converter bus and a dc bus to
which it is connected are in different areas, the connection is treated as a tie line and metering on
the dc bus side is assumed. DC links within a multi-terminal dc line are handled in the same manner
as ac branches. A voltage source converter (VSC) dc transmission line is considered to be a tie line
when the converter station buses are located in different areas. The tie flow is taken as the power
flowing into the dc converter from the ac system at the power controlling converter end. Refer to the
PSS
E instal-
lation, has three areas. For this power flow case, the Area totals are shown in Figure 10-7. The load
reporting option that provides for three subtotals of area load is used in this example.
A brief examination of the results shows:
The FLAPCO area is transmitting power to the other two areas although it is exporting
more (278.7 MW) than scheduled (250 MW). This is because the Area Interchange
control was not enabled in the [Loadflow Solutions] window.
LIGHTCO area is receiving 130.8 MW compared to a desired interchange of 100 MW.
The FLAPCO area is receiving 684.6 Mvar from the other two areas.
Total Real Power losses are 58.7 MW
Additional Information
PSS
E
3
2
.
0
P
o
w
e
r
F
l
o
w
R
e
p
o
r
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
S
u
m
m
a
r
i
z
i
n
g
A
r
e
a
T
o
t
a
l
s
Figure 10-7. Area Total Results
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE WED, FEB 25 2009 11:43
PSS(R)E PROGRAM APPLICATION GUIDE EXAMPLE AREA TOTALS
BASE CASE INCLUDING SEQUENCE DATA IN MW/MVAR
TO AREA TO AREA TO NON-
FROM LOAD AT LOAD AT AREA LOAD -NET INTERCHANGE-
GENE- AREA NON-AREA AT AREA TO BUS TO LINE FROM TO TO TIE TO TIES DESIRED
X-- AREA --X RATION BUSES BUSES BUSES SHUNT SHUNT CHARGING LOSSES LINES + LOADS NET INT
1 1500.0 200.0 0.0 1000.0 0.0 0.0 0.0 21.3 278.7 1278.7 250.0
FLAPCO 162.4 100.0 0.0 800.0 349.9 0.0 841.3 438.3 -684.6 115.4
2 1400.0 1500.0 1000.0 0.0 0.0 0.0 0.0 30.8 -130.8 -1130.8 -100.0
LIGHTCO 617.7 850.0 800.0 0.0 -641.4 0.0 623.0 590.4 441.7 -358.3
5 358.7 500.0 0.0 0.0 0.0 0.0 0.0 6.6 -147.9 -147.9 -150.0
WORLD 184.0 200.0 0.0 0.0 0.0 0.0 345.8 87.0 242.9 242.9
COLUMN 3258.7 0.0 0.0 0.0 58.7 0.0 0.0 0.0
TOTALS 964.2 -291.5 0.0 1810.1 1115.7 0.0 0.0
TOTAL LOAD ASSIGNED TO THESE AREAS 3200.0 MW 1950.0 MVAR
TOTAL LOAD CONNECTED TO BUSES IN THESE AREAS 3200.0 MW 1950.0 MVAR
Power Flow Reports PSS
E 32.0
Summarizing Owner Totals Program Operation Manual
10-36 Siemens Energy, Inc., Power Technologies International
10.8 Summarizing Owner Totals
Activity OWNR
The owner summary activity OWNR provides a tabulation by owner of the following owner totals:
Generation.
Load.
Bus connected shunt elements, including fixed shunts, switched shunts and shunt ele-
ments of FACTS devices.
Line connected shunt elements, including magnetizing admittance of transformers.
Line charging.
Losses.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. Totals for the selected owners are printed in
ascending owner number order, followed by the sums of the totals of those owners.
An individual in-service bus load is included in the load totals of the owner to which the load is
assigned; this owner need not be the same owner in which the bus at which the load is connected
is located (refer to Bus Data and Load Data). Similarly, generation, ac branch, VSC dc line, and
FACTS device quantities are assigned to the designated machine, branch, VSC dc line, and FACTS
device owners, respectively.
Line losses are taken as I
2
R and I
2
X losses and exclude the line charging and line connected shunt
components; transformer losses exclude magnetizing admittance components. Series FACTS
device losses are calculated as the algebraic sum of the reactive power flowing into the series
device at its endpoint buses.
Losses on two-terminal dc transmission lines and on branches within multi-terminal dc lines are
assigned to the owner of the nonmetered end. For the connections between each multi-terminal dc
line ac converter bus and the dc bus to which it is connected, metering on the dc bus side is
assumed (i.e., losses are assigned to the owner of the ac bus). Losses on a voltage source
converter (VSC) dc line are calculated as the algebraic sum of the active and reactive powers
Run Activity OWNR - GUI
Power Flow > Reports > Area / owner / zone totals
[Area / Owner / Zone Totals]
OPTION: Report on Owners
Run Line Mode Activity OWNR - CLI
ACTIVITY?
>>OWNR
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 10-37
PSS
E 32.0
Summarizing Zone Totals Program Operation Manual
10-38 Siemens Energy, Inc., Power Technologies International
10.9 Summarizing Zone Totals
Activity ZONE
The zone summary activity ZONE provides a tabulation by zones of the following zone totals:
The ZONE_2 API tabulates totals by zone. The output block for each zone and for system totals
consists of two lines: the first contains active power totals and the second the reactive power totals.
The ZONE_AREA API tabulates totals by zone along with subtotals by area for each reported zone.
The output block for each zone consists of one line for each area in the zone, followed by one line
of zone totals.
In both of these reports, the zone number and name is printed for each zone block reported.
The user specifies the zones to be reported (refer to Section 4.8). Totals for the specified zones are
printed in ascending zone number order, followed by the sums of the totals of those zones.
Recall that buses and loads both have zone assignments associated with them (refer to Bus Data
and Load Data). One of three load reporting options may be selected for calculating each zone's
total load:
Calculate total zone load by summing all in-service loads connected to buses that are
assigned to the zone. The zone assignment of the load is not considered.
Calculate total zone load by summing all in-service loads that are assigned to the zone.
The zone assignment of the bus to which it is connected is not considered.
Calculate three subtotals of zone load:
- The sum of all in-service loads for which both the load and the bus to which it is
connected are assigned to the zone.
Run Activity ZONE - GUI
Power Flow > Reports > Area / owner / zone totals
[Area / Owner / Zone Totals]
OPTION: Report on Zones
Run Line Mode Activity ZONE - CLI
ACTIVITY?
>>ZONE
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Generation
Load
Bus connected shunt elements, including fixed
shunts, switched shunts and shunt elements of
FACTS devices
Line connected shunt elements, including
magnetizing admittance of transformers
Line charging
Net interchange
Losses
Siemens Energy, Inc., Power Technologies International 10-39
PSS
E 32.0
Summarizing Zone Totals Program Operation Manual
10-40 Siemens Energy, Inc., Power Technologies International
as ac branches. A voltage source converter (VSC) dc transmission line is considered to be a tie line
when the converter station buses are located in different zones. The tie flow is taken as the power
flowing into the dc converter from the ac system at the power controlling converter end. Refer to the
PSS
E
3
2
.
0
P
o
w
e
r
F
l
o
w
R
e
p
o
r
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
S
u
m
m
a
r
i
z
i
n
g
Z
o
n
e
T
o
t
a
l
s
Figure 10-9. Zone Totals Results
PTI INTERACTIVE POWER SYSTEM SIMULATOR--PSSE WED, FEB 25 2009 11:45
PSS(R)E PROGRAM APPLICATION GUIDE EXAMPLE ZONE TOTALS
BASE CASE INCLUDING SEQUENCE DATA IN MW/MVAR
TO ZONE TO ZONE TO NON-
FROM LOAD AT LOAD AT ZONE LOAD -NET INTERCHANGE-
GENE- ZONE NON-ZONE AT ZONE TO BUS TO LINE FROM TO TO TIE TO TIES
X-- ZONE --X RATION BUSES BUSES BUSES SHUNT SHUNT CHARGING LOSSES LINES + LOADS
1 0.0 1200.0 0.0 0.0 0.0 0.0 0.0 18.0 -1218.0 -1218.0
FIRST 0.0 900.0 0.0 0.0 349.9 0.0 841.3 289.6 -698.2 -698.2
2 1400.0 1500.0 0.0 0.0 0.0 0.0 0.0 30.8 -130.8 -130.8
SECOND 617.7 850.0 0.0 0.0 -641.4 0.0 623.0 590.4 441.7 441.7
5 358.7 500.0 0.0 0.0 0.0 0.0 0.0 6.6 -147.9 -147.9
FIFTH 184.0 200.0 0.0 0.0 0.0 0.0 345.8 87.0 242.9 242.9
77 1500.0 0.0 0.0 0.0 0.0 0.0 0.0 3.3 1496.7 1496.7
PLANT 162.4 0.0 0.0 0.0 0.0 0.0 0.0 148.8 13.6 13.6
COLUMN 3258.7 0.0 0.0 0.0 58.7 0.0 0.0
TOTALS 964.2 -291.5 0.0 1810.1 1115.7 0.0 0.0
TOTAL LOAD ASSIGNED TO THESE ZONES 3200.0 MW 1950.0 MVAR
TOTAL LOAD CONNECTED TO BUSES IN THESE ZONES 3200.0 MW 1950.0 MVAR
Power Flow Reports PSS
E 32.0
Reporting Interchange by Area/Owner/Zone Program Operation Manual
10-42 Siemens Energy, Inc., Power Technologies International
10.10 Reporting Interchange by Area/Owner/Zone
Reporting Interchange by Area/Owner/Zone
Table 10-2 shows the information provided in the interchange reports on the bases of area and
zone.
There are two types of summary reports: Inter area/zone flow, which provides total flows between
Areas or Zones and Tie line, which provides detailed flows on the tie lines (branches) between the
Areas or Zones.
The output is organized by Area or Zone such that all Areas or all Zones are reported or the rport
may be limited to selected Areas or Zones.
It is useful to note that the inter Area / Zone flow report can be compared to the Totals report
described in Section 10.6.
Table 10-2. Information Provided in Interchange Reports for Areas and Zones
Information Provided Area Zone
Total interchange between Areas (MW, Mvar) Y -
Interchange flows on tie-lines between Areas (MW, Mvar) Y -
Total interchange between Zones (MW, Mvar) - Y
Interchange flows on tie-lines between Zones (MW, Mvar) - Y
Siemens Energy, Inc., Power Technologies International 10-43
PSS
E 32.0
Summarizing Area-to-Area Interchange Program Operation Manual
10-44 Siemens Energy, Inc., Power Technologies International
which it is connected are in different areas, the connection is treated as a tie line and metering on
the dc bus side is assumed. DC links within a multi-terminal dc line are handled in the same manner
as ac branches. A voltage source converter (VSC) dc transmission line is considered to be a tie line
when the converter station buses are located in different areas. The tie flow is taken as the power
flowing into the dc converter from the ac system at the power controlling converter end. Refer to the
PSS
E 32.0
Summarizing Zone-to-Zone Interchange Program Operation Manual
10-46 Siemens Energy, Inc., Power Technologies International
which it is connected are in different zones, the connection is treated as a tie line and metering on
the dc bus side is assumed. DC links within a multi-terminal dc line are handled in the same manner
as ac branches. A voltage source converter (VSC) dc transmission line is considered to be a tie line
when the converter station buses are located in different zones. The tie flow is taken as the power
flowing into the dc converter from the ac system at the power controlling converter end. Refer to the
PSS
E 32.0
Summarizing Loadings on Ties from Interchange Areas Program Operation Manual
10-48 Siemens Energy, Inc., Power Technologies International
A series FACTS device is considered to be a tie line when the sending and terminal buses are
located in different areas. The tie flow is taken as the power flowing into the series element at the
terminal bus end.
The net interchange definition follows that of the most recently enabled setting of the area inter-
change control code via either activity OPTN or a power flow solution activity: tie lines only, or tie
lines plus loads for which the load and the bus to which it is connected are in different areas (refer
to Area Interchange Control).
In the report, the element listed first for each tie is located in the from area, and the second element
is in the to area. The metered bus of each tie branch is designated with an asterisk ( - ). The stan-
dard sign convention is used in printing the tie flows: a positive flow indicates power leaving the from
area.
Activity TIES may be terminated by entering the AB interrupt control code.
A portion of the inter-area tie-line report for the savnw.sav case is seen in Figure 10-12. The report
presents information in order of Area. The figure shows the tie-line flows from Area 1 to Areas 2 and
5. The total flows can be compared with the interchange totals shown in Figure 10-10 (inter-area
flows) and Figure 10-7 (area totals report).
Figure 10-12. Inter-Area Tie Line Report
Additional Information
PSS
E GUI Users Guide, Section 16.1.3, Loadings on Tie Lines from Interchange Areas
PSS
E 32.0
Summarizing Loadings on Ties from Zones Program Operation Manual
10-50 Siemens Energy, Inc., Power Technologies International
A series FACTS device is considered to be a tie line when the sending and terminal buses are
located in different zones. The tie flow is taken as the power flowing into the series element at the
terminal bus end.
The net interchange definition follows that of the most recently enabled setting of the area inter-
change control code via either activity OPTN or a power flow solution activity: tie lines only, or tie
lines plus loads for which the load and the bus to which it is connected are in different zones (refer
to Area Interchange Control).
In the report, the element listed first for each tie is located in the from zone, and the second element
is in the to zone. The metered bus of each tie branch is designated with an asterisk ( - ). The stan-
dard sign convention is used in printing the tie flows: a positive flow indicates power leaving the from
zone.
Activity TIEZ may be terminated by entering the AB interrupt control code.
A portion of the inter-zone tie-line report for the savnw.sav case is seen in Figure 10-13. The report
presents information in order of Zone. The figure shows the tie-line flows from Zone 1 to Zones 2,
5 and 77. The total flows can be compared with the interchange totals shown in Figure 10-11 (inter-
zone flows) and Figure 10-9 (zone totals report).
Figure 10-13. Inter-Zone Tie Line Report
Additional Information
PSS
E GUI Users Guide, Section 16.1.4, Loadings on Tie Lines from Zones
PSS
E enables the user to develop seven different types of reports which can assist in rapidly iden-
tifying network conditions that are outside of required control limits or to indicate controlling
equipment and possible violations and conflicts associated with those controls. The following
summary reports are available:
Summary of branches exceeding specified percentage of selected rating
Summary of buses with voltage outside specified band
Summary of generator terminal loading conditions on either all, or only overloaded,
generators
Summary of generator bus loading conditions on either all, or only var-limited,
generators
Summary of controlling transformers and violations
Generator reactive power and capability
Regulated buses, violations and/or conflicts.
Power Flow Reports PSS
E 32.0
Producing a Branch Overload Checking Report Program Operation Manual
10-52 Siemens Energy, Inc., Power Technologies International
10.16 Producing a Branch Overload Checking Report
Activity RAT3
The branch overload checking activity RAT3 checks each ac branch current loading against desig-
nated branch ratings. For non-transformer branches, loadings are calculated as either current
loadings or MVA loadings, according to the non-transformer branch percent loading units program
option setting. Similarly, for transformer branches, loadings are calculated as either current loadings
or MVA loadings, according to the transformer percent loading units program option setting. Refer
to Section 3.3.3 and activity OPTN. Branch overloads are reported based on a selected ratings set:
RATE A, RATE B or RATE C.
When percent current loadings are calculated, ratings are assumed to have been entered as:
MVA
rated
= \ 3 x E
base
x I
rated
x 10
-6
where:
When percent MVA loadings are calculated, ratings are assumed to have been entered as MVA
ratings.
The user specifies the percentage loading threshold. Any checked branch where loading, including
line charging, line connected shunt, and transformer magnetizing admittance components, exceeds
the specified percentage of rating is reported. The default limit is 100%.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. Output is generated, with all branches having at least
one endpoint bus in the specified subsystem and at least one non-zero rating being checked. Then
the user is given the opportunity to specify another subsystem.
When an owner subsystem is specified, branch ownership rather than bus ownership is used in
determining which branches are contained in the specified subsystem; any other selection criteria
apply to the branchs endpoint buses.
Run Activity RAT3 - GUI
Power Flow > Reports > Limit checking reports
[Limit Checking Reports]
OPTION: Branches Tab; List overloaded both trans and non-trans branches, all ratings
Run Line Mode Activity RAT3 - CLI
ACTIVITY?
>>RAT3
ENTER OUTPUT DEVICE CODE:
>>
Interrupt Control Codes
AB
E
base
Is the branch or transformer winding voltage base in volts.
I
rated
Is the rated phase current in amps.
Siemens Energy, Inc., Power Technologies International 10-53
PSS
E 32.0
Producing a Branch Overload Checking Report Program Operation Manual
10-54 Siemens Energy, Inc., Power Technologies International
Figure 10-14. Report for Branch Loadings, All Ratings
Additional Information
PSS
E
3
2
.
0
P
o
w
e
r
F
l
o
w
R
e
p
o
r
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
r
o
d
u
c
i
n
g
a
T
r
a
n
s
f
o
r
m
e
r
O
v
e
r
l
o
a
d
C
h
e
c
k
i
n
g
R
e
p
o
r
t
10.17 Producing a Transformer Overload Checking Report
Activity OLTR
The transformer overload checking activity OLTR checks transformer branch loadings against designated branch ratings. Loadings are calculated
as either current loadings or MVA loadings, according to the transformer percent loading units program option setting. Refer to Section and
activity OPTN.
When percent current loadings are calculated, ratings are assumed to have been entered as:
MVA
rated
= \ 3 x E
base
x I
rated
x 10
-6
where:
When percent MVA loadings are calculated, ratings are assumed to have been entered as MVA ratings.
Run Activity OLTR - GUI
Power Flow > Reports > Limit checking reports
[Limit Checking Reports]
OPTION: Branches Tab; List overloaded only transformers
Run Line Mode Activity OLTR - CLI
ACTIVITY?
>>OLTR
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
E
base
Is the transformer winding voltage base in volts.
I
rated
Is the rated phase current in amps.
Power Flow Reports PSS
E 32.0
Producing a Transformer Overload Checking Report Program Operation Manual
10-56 Siemens Energy, Inc., Power Technologies International
The user specifies the percentage loading threshold. Any checked transformer branch where
loading, including magnetizing admittance, exceeds the specified percentage of rating is reported.
The default limit is 100%.
The user specifies the rating; the default rating set is established by the program option setting
(refer to Section 3.3.3 and activity OPTN). The report is generated with branches having a non-zero
value for the specified rating being checked.
The user specifies the subsystem of the working case for which the overload check is to be made
(refer to Section 4.8). Output is generated with all transformer branches having at least one
endpoint bus in the specified subsystem being checked.
If an owner subsystem has been specified, branch ownership rather than bus ownership is used in
determining which transformers are contained in the specified subsystem; any other selection
criteria apply to the transformers endpoint buses.
It should be noted, however, that when subsystem selection is by OWNER, it is branch ownership
rather than bus ownership which is used in determining which transformer branches are contained
in the specified subsystem. Any other selection criteria apply to the transformers endpoint buses.
Any transformer where the corresponding rating is zero is not checked for overloading. Any trans-
former branch where loading exceeds the designated percentage of rating generates an alarm. The
loading is calculated at each end of the line and the number of the bus at which the loading is higher
is followed by an asterisk ( - ). The branch loading, rating, and percentage loading are tabulated.
Any transformer where the corresponding rating is zero is not checked for overloading. Any trans-
former where loading exceeds the designated percentage of rating generates an alarm. The loading
is calculated at each end of the transformer, and the number of the bus at the end of the transformer
with the higher loading is followed by an asterisk ( - ). The transformer loading, rating, and
percentage loading are tabulated.
For three-winding transformers, each winding is checked and reported separately. Only those wind-
ings connected to buses in the specified subsystem are processed. For each winding reported, the
bus to which the winding is connected is shown as the from bus, and the winding number and trans-
former name are listed as the to bus.
The output report of activity OLTR lists transformers in single entry list format ordered by from bus
(refer to Branch Data) and grouped as described in Section 4.9.
Thus, activity OLTR functions in exactly the same manner as does activity RATE, except that non-
transformer branches are omitted from the overload checking.
Activity OLTR may be terminated with the AB interrupt control code.
Figure 10-15 shows a sample output from the savnw.sav case with the transformer overload check
performed on the basis of 80% of RATE A.
The overload report lists transformer branches in single entry list format ordered by from bus. Trans-
formers are also listed by AREA so that all transformers overloaded in AREA 1 are listed first
followed by transformers in AREA 2 and AREA 5. Transformers would also be listed by circuit
number if appropriate. This report shows overloads only in AREAS 2 and 5.
Siemens Energy, Inc., Power Technologies International 10-57
PSS
E 32.0
Producing a Transmission Line Overload Checking Report Program Operation Manual
10-58 Siemens Energy, Inc., Power Technologies International
10.18 Producing a Transmission Line Overload Checking Report
Activity OLTL
The transmission line overload checking activity OLTL checks non-transformer branch loadings
against designated branch ratings. Loadings are calculated as either current loadings or MVA load-
ings, according to the non-transformer branch percent loading units program option setting. Refer
to Section and activity OPTN.
When percent current loadings are calculated, ratings are assumed to have been entered as:
MVA
rated
= \ 3 x E
base
x I
rated
x 10
-6
where:
When percent MVA loadings are calculated, ratings are assumed to have been entered as MVA
ratings.
The user specifies the percentage loading threshold. Any checked branch where current loading,
including line charging and line connected shunt components, exceeds the specified percentage of
rating is reported. The default limit is 100%.
The user specifies the rating; the default rating set is established by the program option setting
(refer to Section 3.3.3 and activity OPTN). The report is generated with branches having a non-zero
value for the specified rating being checked.
The user specifies the subsystem of the working case for which the overload check is to be made
(refer to Section 4.8). Output is generated with all non-transformer branches having at least one
endpoint bus in the specified subsystem being checked.
If an owner subsystem has been specified, branch ownership rather than bus ownership is used in
determining which branches are contained in the subsystem; any other selection criteria apply to
the branchs endpoint buses.
Run Activity OLTL - GUI
Power Flow > Reports > Limit checking reports
[Limit Checking Reports]
OPTION: Branches Tab; List overloaded only non-transformer branches
Run Line Mode Activity OLTL - CLI
ACTIVITY?
>>OLTL
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
E
base
Is the base voltage in volts of the bus to which the terminal of the branch is
connected.
I
rated
Is the rated phase current in amps.
Siemens Energy, Inc., Power Technologies International 10-59
PSS
E 32.0
Producing a Transmission Line Overload Checking Report Program Operation Manual
10-60 Siemens Energy, Inc., Power Technologies International
Figure 10-16. Report on Transmission Line Overloads
Additional Information
PSS
E
3
2
.
0
P
o
w
e
r
F
l
o
w
R
e
p
o
r
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
r
o
d
u
c
i
n
g
a
B
r
a
n
c
h
C
u
r
r
e
n
t
R
a
t
i
n
g
s
R
e
p
o
r
t
10.19 Producing a Branch Current Ratings Report
Activity RATE
The branch overload checking activity RATE checks ac branch loadings against designated branch ratings. The user can select from several
types of branch loading checks:
Branch overloads, based on current loading, for transformer and non-transformer branches
Transformer overloads, based on MVA loading
Transmission line (non-transformer branches) overloads based on current loading
Branch current ratings (A, B and C) and percentage loading at each rating
For overload checking purposes, the user can select which of the three ratings is to be used, with the default being the rating set established in
the program options (activity OPTN). The default percentage of rating limit is 100%. This limit can be adjusted up or down in 5% steps.
For non-transformer branches, loadings are calculated as either current loadings or MVA loadings, according to the non-transformer branch
percent loading units program option setting. Similarly, for transformer branches, loadings are calculated as either current loadings or MVA load-
ings, according to the transformer percent loading units program option setting. Refer to Section 3.3.3, activity OPTN, and Case Identification
Data.
Run Activity RATE - GUI
Power Flow > Reports > Limit checking reports
[Limit Checking Reports]
OPTION: Branches Tab; List overloaded both transformer and non-transformer branches
Run Line Mode Activity RATE - CLI
ACTIVITY?
>>RATE
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Power Flow Reports PSS
E 32.0
Producing a Branch Current Ratings Report Program Operation Manual
10-62 Siemens Energy, Inc., Power Technologies International
When percent current loadings are calculated, ratings are assumed to have been entered as:
MVA
rated
= \ 3 x E
base
x I
rated
x 10
-6
where:
When percent MVA loadings are calculated, ratings are assumed to have been entered as MVA
ratings.
Any checked branch where current loading, including line charging, line connected shunt, and
transformer magnetizing admittance components, exceeds the specified percentage of rating is
reported. The default line loading limit is 100%.
The user specifies the rating; the default rating set is established by the program option setting
(refer to Section 3.3.3 and activity OPTN). The report is generated with branches having a non-zero
value for the specified rating being checked.
The user specifies the subsystem of the working case for which the overload check is to be made
(refer to Section 4.8). Output is generated with all branches having at least one endpoint bus in the
specified subsystem being checked.
If an owner subsystem has been specified, branch ownership rather than bus ownership is used in
determining which branches are contained in the subsystem; any other selection criteria apply to
the branchs endpoint buses.
Any branch where the corresponding rating is zero is not checked for overloading. Any branch
where loading exceeds the designated percentage of rating generates an alarm. The loading is
calculated at each end of the branch, and the number of the bus at the end of the branch with the
higher loading is followed by an asterisk ( - ). The branch loading, rating, and percentage loading
are tabulated.
For three-winding transformers, each winding is checked and reported separately. Only those wind-
ings connected to buses in the specified subsystem are processed. For each winding reported, the
bus to which the winding is connected is shown as the from bus, and the winding number and trans-
former name are listed as the to bus.
Activity RATE may be terminated with the AB interrupt control code.
The output report of activity RATE lists branches in single entry list format ordered by from bus (refer
to Branch Data) and grouped as described in Section 4.9.
Figure 10-17 shows a sample output from the savnw.sav case with a branch overload check
performed on the basis of 80% of RATE A
The overload report lists branches in single entry list format ordered by from bus. It can be seen that
branches are also listed by AREA so that all branches overloaded in AREA 1 are listed first followed
by branches in AREA 2 and AREA 5. Branches would also be listed by circuit number if appropriate.
In the table, the right most column shows the percentage loading on 100% of the RATE A level. Only
one branch loading exceeds the 100% limit; the 230/18 kV transformer branch from Bus 205 to Bus
E
base
Is the base voltage in volts of the bus to which the terminal of the branch is
connected.
I
rated
Is the rated phase current in amps.
Siemens Energy, Inc., Power Technologies International 10-63
PSS
E 32.0
Producing an Out-of-Limits Bus Voltage Report Program Operation Manual
10-64 Siemens Energy, Inc., Power Technologies International
10.20 Producing an Out-of-Limits Bus Voltage Report
Activity VCHK
The voltage checking activity VCHK tabulates those buses where voltage magnitude is outside a
specified range. The user specifies voltage setpoints. The default settings result in a tabulation of
buses where voltage is above 1.05 pu or below 0.95 pu.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV.
Activity VCHK produces a listing of those buses where voltage magnitude is greater than VMAX,
followed by a listing of buses where voltage is less than VMIN. Both listings are in ascending numer-
ical (using the numbers output option) or alphabetical (using the names output option) order; refer
to Section 3.3.3 and activity OPTN.
The star point buses of three-winding transformers are neither checked nor reported by activity
VCHK.
Activity VCHK may be terminated with the AB interrupt control code.
Figure 10-18 shows the report generated for the savnw.sav case using a voltage range from 0.97
pu to 1.01 pu. It can be seen that the bus base voltage is listed together with the actual bus voltages
in pu and kV. There are 13 buses with voltages greater than 1.01 pu and 5 buses with voltages less
than 0.97 pu.
Run Activity VCHK - GUI
Power Flow > Reports > Limit checking reports
[Limit Checking Reports]
Out-of-limit bus voltage Tab
Run Line Mode Activity VCHK - CLI
ACTIVITY?
>>VCHK
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 10-65
PSS
E
3
2
.
0
P
r
o
d
u
c
i
n
g
a
M
a
c
h
i
n
e
R
e
a
c
t
i
v
e
C
a
p
a
b
i
l
i
t
y
R
e
p
o
r
t
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
10.21 Producing a Machine Reactive Capability Report
Activity GCAP
The machine capability curve checking activity GCAP reads a data file containing capability curve data and prints a report of machine loading
and limit data. Optionally, machine reactive power limits in the working case may be updated.
10.21.1 Machine Capability Curve Data File Contents
Any machine to be checked must have its capability curve specified in a Machine Capability Curve Data File. Each data record in this file has the
following format:
I, ID, P1, QT1, QB1, P2, QT2, QB2, ... P10, QT10, QB10
where:
Run Activity GCAP - GUI
Power Flow > Reports > Limit checking reports
[Limit Checking Reports]
Reactive capability Tab
Run Line Mode Activity GCAP - CLI
ACTIVITY?
>>GCAP
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
I Bus number. Bus I must be present in the working case with a plant sequence
number assigned to it (refer to Plant and Machine Sequence Numbers). No default
is allowed.
Siemens Energy, Inc., Power Technologies International 10-67
PSS
E 32.0
Producing a Machine Reactive Capability Report Program Operation Manual
10-68 Siemens Energy, Inc., Power Technologies International
Figure 10-19. Capability Curve Example for savnw.sav Case
10.21.2 Operation of Activity GCAP
The user enters the name of the appropriate Machine Capability Curve Data File containing data
records of the form defined in Machine Capability Curve Data File Contents. If the file does not exist
or some other file system error occurs, an appropriate message is printed. Refer to Section 2.4.1
for the file specification conventions used by activity GCAP.
When the input file is successfully opened, activity GCAP processes the data records. If any data
inconsistencies are detected during data input, they generate an alarm and the corresponding
record is ignored. Activity GCAP processes only the valid data records.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. Output is generated with buses ordered as described
in Section 4.9.
When the owner option is specified, each machine wholly or partly owned by any of the owners
specified and for which a data record was successfully read is processed (refer to Branch Data).
The owner assignment of the bus to which the machine is connected is not considered.
The user may update the reactive power limits of all machines reported by activity GCAP.
Siemens Energy, Inc., Power Technologies International 10-69
PSS
E
3
2
.
0
P
r
o
d
u
c
i
n
g
a
M
a
c
h
i
n
e
R
e
a
c
t
i
v
e
C
a
p
a
b
i
l
i
t
y
R
e
p
o
r
t
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 10-20. Report Output for Reactive Power Checking with Capability Curve
Siemens Energy, Inc., Power Technologies International 10-71
PSS
E 32.0
Producing a Generator Bus Limits Report Program Operation Manual
10-72 Siemens Energy, Inc., Power Technologies International
10.22 Producing a Generator Bus Limits Report
Activity GENS
The generating plant summary activity GENS tabulates the loading and voltage conditions at gener-
ator buses. The user must choose among the following report options:
VAR limited plants with unequal VAR limits: only plants at a reactive power limit and
where var limits are unequal
All VAR limited plants: all var-limited plants
On-line plants: all in-service generator buses
All plants: both in-service and out-of-service plants.
The user may also specify that voltage output is printed in alternate units rather than in the default
units (refer to Section 3.3.3 and activity OPTN).
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. Output is generated with buses ordered as described
in Section 4.9.
The output listing of activity GENS may be terminated by entering the AB interrupt control code.
The report of activity GENS includes the bus number, name, base voltage, and type code, along
with the number of machines modeled at the plant where status flags are 1, the number of machines
where status flags are zero, the total plant power outputs and reactive power limits, and scheduled
and actual voltages.
If a plant regulates the voltage of a remote bus, the remote bus identifiers are printed and the actual
voltage printed is that at the remote bus; if a plant regulates its own terminal voltage, the remote
bus fields are blank. Total plant MBASE of machines at the bus where status flags are 1, along with
the numbers of the zone and area in which the bus is located, are also printed. Any plant that is
either a system or area swing is identified with an appropriate tag at the end of the output line.
As the last line of each report, subsystem totals of plant power outputs, var limits, and MBASE are
tabulated.
Figure 10-21 shows a report for All plants from the savnw.sav Saved Case.
Run Activity GENS - GUI
Power Flow > Reports > Limit checking reports
[Limit Checking Reports]
Generator bus Tab
Run Line Mode Activity GENS - CLI
ACTIVITY?
>>GENS
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 10-73
PSS
E
3
2
.
0
P
r
o
d
u
c
i
n
g
a
G
e
n
e
r
a
t
o
r
B
u
s
L
i
m
i
t
s
R
e
p
o
r
t
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 10-21. Generator Bus Report
Additional Information
PSS
E 32.0
Producing a Machine Terminal Limits Report Program Operation Manual
10-76 Siemens Energy, Inc., Power Technologies International
It should be noted that the terminal voltages for those two machines, and the machine at bus 211,
are higher than their scheduled voltages (VSCHED) because these machines are attempting to
control voltage at remote buses rather than at the machine terminals. The Generator Bus report
shows the scheduled voltages and the remote buses (see Figure 10-21).
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
1
0
-
7
7
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
R
e
p
o
r
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
r
o
d
u
c
i
n
g
a
M
a
c
h
i
n
e
T
e
r
m
i
n
a
l
L
i
m
i
t
s
R
e
p
o
r
t
Figure 10-22. Report Tabulation for Machine Terminal Conditions in savnw.sav File
Power Flow Reports PSS
E 32.0
Producing a Machine Terminal Limits Report Program Operation Manual
10-78 Siemens Energy, Inc., Power Technologies International
10.23.1 Application Notes
Activity GEOL calculates and reports the generator terminal conditions for in-service machines.
When the machine step-up transformer is represented explicitly as a network branch, and hence
the Type 2 bus is the generator terminal bus, activity GEOL simply uses the boundary conditions at
the bus in generating the report (refer to Section 11.2.3 and Figure 11-4b).
When the step-up transformer is modeled with the generator data (i.e., XTRAN is non-zero), the
generator bus is the high side bus (see Figure 11-4c). In this case, activity GEOL calculates back
through the step-up transformer impedance to determine the conditions that exist at the generator
terminals.
In performing its overload check, activity GEOL assumes a machine capability curve as shown in
Figure 10-23. The radius of the semicircle in the upper half plane, centered at the origin, is taken as:
When XTRAN is non-zero, the reactive power limits are modified to reflect these limits at the termi-
nals by taking into account losses through the step-up transformer.
Figure 10-23. Assumed Capability Curve of Activity GEOL
When XTRAN is nonzero, the reactive power limits are modified to reflect these limits at the termi-
nals by taking into account losses through the step-up transformer.
The assumed operating region in the capability curve of Figure 10-23 is bounded as follows:
1. On the bottom, by the Q axis.
2. On the top, by the semicircle in the upper half plane.
3. On the left, by the straight line connecting the point QMIN on the Q axis and the point on the
upper half plane circle corresponding to an abscissa of -0.3-MBASE. When QMIN is greater
MBASE
E
t
1.6-MBASE
-0.3-MBASE 0.55-MBASE
P
E
t
2
------
Q
E
t
2
------
QMAX QMIN
Siemens Energy, Inc., Power Technologies International 10-79
PSS
E 32.0
Producing a Regulated Bus Report Program Operation Manual
10-80 Siemens Energy, Inc., Power Technologies International
10.24 Producing a Regulated Bus Report
Activity REGB
In large databases it is important to have the ability to easily identify which bus voltages are being
regulated and which equipment is controlling the regulation. This helps to avoid situations in which
there are potential regulation conflicts.
The regulated bus reporting activity REGB tabulates those buses where voltages are controlled by
generation, switched shunts, voltage controlling transformers, FACTS devices, and/or VSC dc line
converters. Data presented includes the bus number, name, and base voltage of each regulated
bus along with its present voltage magnitude. For each controlling equipment item, the desired
voltage setpoint or voltage band, as appropriate, is listed along with any deviation between actual
and scheduled voltages.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. Output for the voltage controlled buses contained in
the specified subsystem is produced with buses ordered as described in Section 4.9.
Only in-service voltage controlled buses (i.e., buses where type codes are less than 4) are reported
by activity REGB. The following lists the conditions under which the various voltage controlling
equipment items are reported:
For any voltage controlling transformer where load drop compensation impedance (refer to Trans-
former Data) is non-zero, the controlled bus voltage (or, equivalently, the voltage limits) are
compensated as described in Voltage Control. Activity REGB always displays voltage at the
controlled bus. Therefore, limits printed for such transformers are the compensated limits and the
Run Activity REGB - GUI
Power Flow > Reports > Limit checking reports
[Limit Checking Reports]
Regulated buses Tab
Run Line Mode Activity REGB - CLI
ACTIVITY?
>>REGB
ENTER UP TO 20 BUS NUMBERS
>>
Interrupt Control Codes
AB
Generation Bus type code is 2 or 3, and at least one in-service machine is present.
Switched shunt Bus type code is less than 4 and the control mode is 1 or 2.
Transformer Branch is in-service and its adjustment control mode is set to +1.
FACTS device
Control mode is non-zero for sending bus end; control mode is 1, 5 or 7 for terminal
bus end.
VSC dc converter
VSC dc lines control mode (MDC) is 1, the VSC converters ac control mode (MODE)
is 1, and the VSC converters dc control code (TYPE) is not zero.
Siemens Energy, Inc., Power Technologies International 10-81
PSS
E
3
2
.
0
P
r
o
d
u
c
i
n
g
a
R
e
g
u
l
a
t
e
d
B
u
s
R
e
p
o
r
t
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 10-24. Regulated Bus Report from the Savnw.sav Power Flow Case
Additional Information
PSS
E 32.0
Producing a Controlling Transformer Report Program Operation Manual
10-84 Siemens Energy, Inc., Power Technologies International
voltage band are listed, along with the controlled bus, the tap ratio, the ratio limits, and the
number of tap positions. When the load drop compensating impedance is non-zero, the
compensated voltage is printed preceded by an asterisk ( - ) (refer to Transformer Data and
Voltage Control); otherwise, the voltage at the controlled bus is reported.
2. A list of any transformer winding where phase shift angle may be adjusted to control the
active power flow through itself. The data tabulated for these includes the present active
power flow through the phase shifter and the desired flow band, the phase shift angle, and
the angle limits.
3. A list of any transformer winding where ratio may be adjusted to control the reactive power
flow through itself. The present reactive power flow and the desired flow band, the present
tap ratio and its limits, and the number of tap positions are tabulated.
4. A list of those two-winding transformers where ratio may be adjusted to control the firing
angle, extinction angle, or voltage of a dc line. The dc line name, the type of quantity
controlled, its present value and desired band, the present tap ratio and its limits, and the
tap step are tabulated.
Any controlled quantity outside of its desired band is followed by the tag HI or LO as appropriate.
Similarly, if the ratio or phase shift angle of a transformer is at or beyond one of its limits, the appro-
priate identifier is printed.
Figure 10-25 for an example of a Controlling Transformers report from the savnw.sav power flow
case. Controlled buses at 154 and 205 show voltages below their transformers control range (indi-
cated by LO) and the Phase Shifting transformer controlling power flow shows a flow level above
its control range (indicated by HI).
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
1
0
-
8
5
P
S
S
E
3
2
.
0
P
o
w
e
r
F
l
o
w
R
e
p
o
r
t
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
P
r
o
d
u
c
i
n
g
a
C
o
n
t
r
o
l
l
i
n
g
T
r
a
n
s
f
o
r
m
e
r
R
e
p
o
r
t
Figure 10-25. Controlling Transformers Report for savnw.sav Power Flow Case
Additional Information
PSS
E 32.0
Comparing Power Flow Case Totals Program Operation Manual
10-86 Siemens Energy, Inc., Power Technologies International
10.26 Comparing Power Flow Case Totals
Activity CMPR
The case comparison activity CMPR compares the total system values contained in the working
case with those of a designated Saved Case. Either system totals, area totals, zone totals, or owner
totals may be compared. If the Substitute working case after comparison option is selected, then
the currently open case will be replaced by the comparison case after the comparison has been
completed.
One of the two cases to be compared must be present in working memory. When initiated, activity
CMPR requires the user to designate the Saved Case to be compared against the working case.
Refer to Section 2.4.1 for the file specification conventions used by activity CMPR. Any errors
encountered in accessing the designated Saved Case File are handled as in activity CASE. The
user must specify which of the two cases is to remain as the PSS
E working case.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. When comparing cases by area or zone, the user
may specify a difference threshold in either engineering units or percent (default = 0) for the fol-
lowing comparisons:
generation
load
losses
mismatch
interchange
The selection of interchange is disabled when totals by owner or the entire case are being
compared. The report for the designated category is printed in ascending area, zone, or owner
number order, for those areas, zones, or owners selected for which difference meets or exceeds
the designated threshold. The report for any category may be terminated by entering the AB inter-
rupt control code, and a new category may then be selected.
Generally, generation, load, loss, and mismatch subsystem totals are accumulated as shown in
Table 10-3.
Run Activity CMPR - GUI
File > Compare
[Compare] Case Totals tab
[Select Powerflow Comparison Options]
Run Line Mode Activity CMPR - CLI
ACTIVITY?
>>CMPR
ENTER SAVED CASE FILENAME:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 10-87
PSS
E GUI Users Guide, Section 9.1, Comparing Power Flow Case Totals
PSS
E 32.0
Comparing Power Flow Cases Program Operation Manual
10-88 Siemens Energy, Inc., Power Technologies International
10.27 Comparing Power Flow Cases
Activity DIFF
The case comparison activity DIFF compares the entire working case or a subset of the case with
a designated Saved Case. All buses and ac branches may be subjected to the comparison, or the
checks may be restricted to a designated subsystem. If the Substitute working case after compar-
ison option is selected, then the currently open case will be replaced by the comparison case after
the comparison has been completed.
One of the two cases to be compared must be present in working memory. When initiated, activity
DIFF requires the user to designate the Saved Case to be compared against the working case.
Refer to Section 2.4.1 for the file specification conventions used by activity DIFF. Any errors
encountered in accessing the designated Saved Case File are handled as in activity CASE. The
user must specify which of the two cases is to remain as the PSS
E working case.
10.27.1 Operation of Activity DIFF
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV.
The user specifies the bus comparison criteria: to be considered comparable (the same), each case
must contain a bus with:
same bus number
same bus name
same bus number and name
If buses in the two cases are matched using only their extended bus names, each bus in the spec-
ified subsystem must have a unique extended bus name. Alarms are printed at the dialog output
device (refer to Section 4.4) if there are duplicate extended bus names in the specified subsystem
of either the working case or the designated Saved Case. Any buses that have generated alarms
are treated as being outside of the specified subsystem, and processing continues using the
remaining subsystem buses in the two cases.
A heading page is printed at the selected output device containing the case headings of the working
case and the comparison case.
Run Activity DIFF - GUI
File > Compare
[Compare] Powerflow Cases tab
[Select Powerflow Comparison Options]
Run Line Mode Activity DIFF - CLI
ACTIVITY?
>>DIFF
ENTER SAVED CASE FILENAME:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 10-89
PSS
E 32.0
Comparing Power Flow Cases Program Operation Manual
10-90 Siemens Energy, Inc., Power Technologies International
Voltage
Comparison Threshold in Percent or Engineering Units
Voltage threshold (default = 0)
Voltage and angle
Comparison Threshold in Percent or Engineering Units
Voltage threshold (default = 0)
Angle threshold (default = 0)
MBASE & ZSOURCE none
MBASE & ZPOS none
MBASE & ZNEG none
MBASE & ZZERO none
Negative sequence bus shunts Comparison Threshold in Percent or Engineering Units
Zero sequence bus shunts Comparison Threshold in Percent or Engineering Units
Branch status none
Line R, X, B none
Line shunts none
Line ratings
Ratings to compare:
All ratings (default)
Rate A
Rate B
Rate C
Metered end none
Transformers
Ratio threshold
Angle threshold
Flows MW or MVAR (from bus) Comparison Threshold in Percent or Engineering Units
Flows MW or MVAR (from & to) Comparison Threshold in Percent or Engineering Units
Line MW or MVAR losses Comparison Threshold in Percent or Engineering Units
Zero sequence R,X,B none
Zero sequence line shunts none
Connection codes none
Zero sequence mutuals none
Multi-section lines none
Multi-section line metered end none
Bus load status none
Line lengths none
Generator MVAR Comparison Threshold in Percent or Engineering Units
Flows MW (from bus) Comparison Threshold in Percent or Engineering Units
Flows MVAR (from bus) Comparison Threshold in Percent or Engineering Units
Table 10-4. Case Comparison Specifications (Cont.)
Category Additional Specifications
Siemens Energy, Inc., Power Technologies International 10-91
PSS
E 32.0
Comparing Power Flow Cases Program Operation Manual
10-92 Siemens Energy, Inc., Power Technologies International
Machine status check
If a machine exists in both cases, it generates an alarm only if its actual
status, as implied by the combination of the bus type code and the machine
status flag, is different in the two cases (refer to Section 5.8.1). When a
machine exists in only one of the cases, it generates an alarm regardless
of its implied status. For any machine that has generated an alarm, the bus
type code and machine status flag from both of the cases are listed.
Generator MW
Generates an alarm for those generator buses for which the total plant
active power output differs in the two cases by more than a specified toler-
ance. If one case contains in-service generation while in the other either no
generation is modeled at the bus or it is out-of-service, the bus generates
an alarm only if the in-service generation exceeds the threshold tolerance.
Generator MW or MVAR
Similar to generator MW, except that a bus is listed if either the active
or reactive generator power difference in the two cases exceeds
the threshold tolerance.
Bus loads
Allows the user to compare either the total in-service constant MVA,
constant current, or constant admittance load, or the total in-service
nominal load, at each bus in the bus comparison list. If one case contains
in-service load while in the other either no load elements are modeled at
the bus or they are all out-of-service, the bus generates an alarm only if
the in-service load exceeds the threshold tolerance.
Bus shunts
Compares total in-service fixed bus shunts against a designated threshold
tolerance. If one case contains in-service fixed shunt while in the other
either no fixed shunt elements are modeled at the bus or they are all out-of-
service, the bus generates an alarm only if the in-service fixed shunt
exceeds the threshold tolerance.
Switched shunts
If a bus has a switched shunt in only one of the two cases, it generates an
alarm if its magnitude exceeds the tolerance. If the threshold tolerance is
specified as zero, the bus generates an alarm even if the value of the
switched shunt in the case in which it exists is zero.
Voltage
Generates an alarm for buses where voltage magnitudes differ by more
than a specified threshold.
Differences between the two cases (Saved Case value minus working
case value) are tabulated. Any bus where the type code is four in both
cases is skipped. If a bus has a type code of 4 in only one of the two cases,
it is included in the report of these checks.
Voltage and angle
Generates an alarm for buses if either the voltage magnitudes differ by
more than a specified tolerance or the phase angle difference exceeds a
designated threshold.
Differences between the two cases (Saved Case value minus working
case value) are tabulated. Any bus where the type code is four in both
cases is skipped. If a bus has a type code of 4 in only one of the two cases,
it is included in the report of these checks.
MBASE & ZSOURCE
Comparison for machines connected to buses in the bus comparison list
(refer to Generator Data and Section 11.2.2). If a machine exists in both
cases, it generates an alarm if either MBASE or ZSORCE is different.
Where a machine exists in only one of the cases, it generates an alarm.
Table 10-5. Case Comparison Specifications, Bus Data Checks (Cont.)
Category Comparison
Siemens Energy, Inc., Power Technologies International 10-93
PSS
E 32.0
Comparing Power Flow Cases Program Operation Manual
10-94 Siemens Energy, Inc., Power Technologies International
10.27.3 Branch Related Data Checks
Table 10-6. Case Comparison Specifications, Branch Data Checks
Category Comparison
Branch status, Line R,X,B,
Line shunts, Line ratings,
Metered end, Transformers,
Flows MW or MVAR (from
bus), Flows MW or MVAR
(from & to), Line MW or MVAR
losses, Zero sequence, R,X,B,
Zero sequence line shunts,
Connection codes, Zero
sequence mutuals, Multi-
section lines, Multi-section line
metered end, Line lengths,
Flows MW (from bus), Flows
MVAR (from bus), Flows MW
(from & to), Flows MVAR (from
& to), Line MW losses, Line
MVAR losses
Check various branch related data items of branches in the branch and
multi-section line comparison lists. Exceptions are tabulated in single entry
format (refer to Branch Data), ordered in ascending bus numerical or
alphabetical order according to the bus output option in effect at the time
activity DIFF is selected (refer to Section 3.3.3). Bus identifiers and
ordering from the working case are used.
Branch status
If a branch appears in both cases, it generates an alarm if the status
flags differ. Where a branch exists in only one of the cases, it generates
an alarm regardless of its status.
Line R, X, B
Checks for different values of line impedance or charging. If a branch
exists in only one of the cases, it is included in the report. If a branch has
the same value of impedance in the two cases but is treated as a zero
impedance line in only one of the two (i.e., THRSHZ differs in the two
cases; refer to Zero Impedance Lines), it is included in the report. If a
branch is treated as a zero impedance line in both cases, the impedances
are considered equal regardless of their values in the two cases. For three-
winding transformer windings, winding impedances are compared.
Line shunts
If a branch exists in only one of the cases, it is included in the tabulation
only if the line shunt at either end of the branch is non-zero.
Line ratings
For branches for which the selected rating(s) differ, all three ratings from
both cases are tabulated. If a branch exists in only one of the cases, it is
excluded from the report.
Metered end
Activity DIFF reports branches with opposite metered ends in the two
cases. If a branch exists in only one of the cases, it is excluded from the
report.
Transformers
Two-winding transformers and individual windings of three-winding trans-
formers are compared. If a branch exists in both of the cases, it generates
an alarm under any of the following conditions:
It is a two-winding transformer or a three-winding transformer
winding in one case, but not in the other.
It is a two-winding transformer in both cases, but the Winding 1 side
and Winding 2 side relationship is reversed.
It is a two-winding transformer in both cases and its Winding 1 tap
ratio or phase shift angle, or Winding 2 tap ratio, differs.
Siemens Energy, Inc., Power Technologies International 10-95
PSS
E 32.0
Comparing Power Flow Cases Program Operation Manual
10-96 Siemens Energy, Inc., Power Technologies International
Zero sequence R,X,B
Checks for different values of zero sequence line impedance or charging. If
a branch exists in only one of the cases, it is included in the report. If a
branch has the same value of zero sequence impedance in the two cases
but is treated as a zero impedance line in only one of the two (i.e.,
THRSHZ differs in the two cases; refer to Section ), it is included in the
report. If a branch is treated as a zero impedance line in both cases, the
zero sequence impedances are considered equal regardless of their
values in the two cases.
In comparing zero sequence line shunts, if a branch exists in only one of
the cases, it is included in the tabulation only if the zero sequence line
shunt at either end of the branch is non-zero.
Connection codes
In the transformer connection code check, if a branch exists in both of the
cases, it generates an alarm under any of the following conditions:
It is a two-winding transformer or a three-winding transformer
winding in one case, but not in the other.
It is a two-winding transformer in both cases, but the Winding 1 side
and Winding 2 side relationship is reversed.
It is a two-winding transformer in both cases, and its winding
connection codes differ.
It is a winding of a three-winding transformer in both cases, and the
connection codes applied at the winding differ.
If a branch exists in one case and not in the other, it generates an alarm
if it is a transformer. This report lists the connection code from each case,
along with an indication of which bus is the Winding 1 side bus.
Zero sequence mutuals
For mutuals to be checked, the branches coupled must both be members
of the branch comparison list. If a mutual coupling exists in one case but
not in the other, it is reported. If the mutual is in both cases, it generates
an alarm if its mutual impedance, its geographic B factors, or its polarity is
not identical in the two cases (refer to Zero Sequence Mutual Impedance
Data). The report lists one of the branches along with the mutual data on
one line, followed by a line listing the other branch.
Multi-section lines
Compares multi-section groupings for multi-section lines in the multi-
section line comparison list (refer to Multi-Section Line Grouping Data) . If a
multi-section line grouping exists in one case but not in the other, it is
reported. If a multi-section line grouping exists in both cases, it generates
an alarm under either of the following conditions:
Any of its dummy buses in either case is not contained in the bus
comparison list.
It contains different members in the two cases.
The report lists the endpoint buses and multi-section line identifier, with the
bus identifiers taken from the working case. It also lists the members of the
multi-section line as contained in the working case (using bus identifiers
from the working case) and in the comparison case (using bus identifiers
from the comparison case).
Multi-section line metered end
Reports multi-section line groupings with opposite metered ends in the two
cases. If a multi-section line exists in only one of the cases, it is excluded
from the report.
Table 10-6. Case Comparison Specifications, Branch Data Checks (Cont.)
Category Comparison
Siemens Energy, Inc., Power Technologies International 10-97
PSS
E 32.0
Displaying Power Flow Solution Differences on a Diagram Program Operation Manual
10-98 Siemens Energy, Inc., Power Technologies International
10.28 Displaying Power Flow Solution Differences on a Diagram
Activity GDIF
The graphical case comparison activity GDIF calculates differences in power flow solution results
and certain power flow boundary condition data contained in the working case with those of a desig-
nated Saved Case. Results are produced in the Diagram View in a form similar to the display of
power flow output.
Prior to initiating activity GDIF, one of the two cases to be compared must be present in the working
case.
If buses in the two cases are matched using only their extended bus names, each bus must have
a unique extended bus name. Alarms are printed at the dialog output device (refer to Section 4.4)
if there are duplicate extended bus names in either the working case or the designated Saved Case.
A heading page is printed at the Progress tab containing the case headings of the working case
and the comparison case.
GDIF builds a diagram bus list of buses where difference quantities are to be calculated. A bus
comparison list is then constructed. It contains a list of buses for which the following are all true:
1. They are contained in both cases with the same bus number and/or extended bus name, as
appropriate.
2. They are in the diagram bus list.
3. They did not generate an alarm because they had duplicate extended bus names (see
above) in either the working case or the comparison case.
Any bus from the working case which is in the diagram bus list but which is not included in the
comparison case generates an alarm.
Activity GDIF summarizes the number of buses and branches in the working case and in the
comparison case, the number of buses from each case in the diagram bus list, and the number of
buses in the bus comparison list.
It constructs a branch comparison list that contains all ac branches from either case that connect
buses in the bus comparison list. The number of such branches, three-winding transformers, and
multi-section lines is then tabulated.
Run Activity GDIF - GUI
Diagram > Results > Graphical difference data
Run Line Mode Activity GDIF - CLI
ACTIVITY?
>>GDIF
ENTER COORDINATE FILE NAME, BINARY OPTION (-1 TO EXIT):
>>
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 10-99
PSS
E 32.0
Comparing AC Tie Branches Program Operation Manual
10-100 Siemens Energy, Inc., Power Technologies International
10.29 Comparing AC Tie Branches
Activity DFTI
The tie line case comparison activity DFTI compares power flow branch data and solution results
contained in the working case with those of a designated Saved Case. Only ac tie branches from
the designated subsystem are subjected to processing and reporting.
Prior to selecting activity DFTI, one of the two cases to be compared must be present in the working
case. The report of activity DFTI is directed to the Progress tab unless an output destination had
been preselected via activity OPEN.
The following input data defining comparison and reporting options is specified to DFTI:
The subsystem where tie branches are to be compared.
The name of the Saved Case File for which tie branches from the specified subsystem
are to be compared to those of the working case.
The method to be used in matching up buses in the two cases.
Data defining the quantities to be compared and any appropriate comparison options.
The case to be left in PSS
E 32.0
Comparing AC Tie Branches Program Operation Manual
10-102 Siemens Energy, Inc., Power Technologies International
7 Transformers
Two-winding transformers and individual windings of three-winding trans-
formers are compared. If a tie branch exists in both of the cases, it
generates an alarm under any of the following conditions:
It is a two-winding transformer or a three-winding transformer
winding in one case, but not in the other.
It is a two-winding transformer in both cases, but the Winding 1 side
and Winding 2 side relationship is reversed.
It is a two-winding transformer in both cases, and its Winding 1 tap
ratio or phase shift angle, or Winding 2 tap ratio, differs.
It is a winding of a three-winding transformer in both cases, and its
winding tap ratio or phase shift angle differs.
If a tie branch exists in one case and not in the other, it generates an
alarm if it is a transformer. For two-winding transformers, this report lists
the tap ratios of both windings and the Winding 1 phase shift angle from
each case, along with an indication of which bus is the Winding 1 side bus;
for three-winding transformers, the winding ratio is listed in the RATIO1
column and the RATIO2 column has a value of 1.0.
8
Flows MW or MVAR
(from bus)
Compare line flows against a designated threshold tolerance. A branch in
the tie branch comparison list is included in this report under any of the
following conditions:
It is in-service in both cases, and the active or reactive power flow at
the from bus end in the two cases differs by more than the threshold
tolerance.
It exists in both cases with different service status, and its active or
reactive power flow at the from bus end in the in-service case
exceeds the threshold.
It exists in only one of the cases, is in-service, and its active or
reactive power flow at the from bus end exceeds the threshold.
This report tabulates the active and reactive power flowing into the from
bus end of the line in the two cases. Flow differences between the two
cases are printed for each branch reported, both in MW and Mvar and as
percentages of the working case flows. For this comparison, both cases
should be solved to an acceptable mismatch level.
9
Flows MW or MVAR
(from and to buses)
Similar to previous specification, except the flows at both ends of each tie
line are checked against the threshold. For branches reported, from bus
end conditions are shown on the first output line and to bus end conditions
on the second.
Table 10-7. Case Comparison Specifications, AC Tie Branch Data Checks (Cont.)
ref # Specification Description
Siemens Energy, Inc., Power Technologies International 10-103
PSS
E 32.0
Comparing AC Tie Branches Program Operation Manual
10-104 Siemens Energy, Inc., Power Technologies International
In comparing line flows and losses (Flows MW or MVAR (from bus), Flows MW or MVAR (from and to
buses), and Line MW or MVAR losses), a threshold tolerance is used. If the difference between data
items in the two cases is within this tolerance, the item is omitted from the output report. Tolerances
are allowed to be specified either in engineering units (e.g., MW and Mvar), or as a percentage of
the data item values in the working case.
The selected check is made and exceptions are listed as described.
For categories comparing fault analysis data, this data must be present in both cases. At the
completion of activity DFTI, the user designation of which of the two cases is to be left as the PSS
E
working case is honored.
Exceptions are tabulated in up to three groups, each of which is in single entry format (refer to
Branch Data), ordered in ascending bus numerical or alphabetical order according to the bus output
option in effect at the time activity DFTI is selected (refer to Section 3.3.3). The first group contains
tie branches connecting tie point buses which are present in both cases. The second group contains
those tie branches in the working case with at least one of the buses it connects not present in the
designated Saved Case. The third group contains those tie branches in the designated Saved Case
with at least one of the buses it connects not present in the working case.
Bus identifiers and ordering from the working case are used in tabulating the first two groups; bus
identifiers and ordering from the designated Saved Case are used in tabulating the third group.
When reporting individual windings of three winding transformers, winding data is tabulated.
15
Flow MVAR (from
bus)
Similar to flows MW or MVAR (from bus) except that a branch is listed if the
reactive power flow difference in the two cases exceeds the threshold
tolerance.
16
Flow MW (from and to
buses)
Similar to flows MW or MVAR (from and to buses) except that a branch is
listed if the active power flow difference at either end in the two cases
exceeds the threshold tolerance.
17
Flow MVAR (from and
to buses)
Similar to flows MW or MVAR (from and to buses) except that a branch is
listed if the reactive power flow difference at either end in the two cases
exceeds the threshold tolerance.
18 Line MW losses
Similar to line MW or MVAR losses except that a branch is listed if the
active power loss difference in the two cases exceeds the threshold
tolerance.
19 Line MVAR losses
Similar to line MW or MVAR losses except that a branch is listed if the reac-
tive power loss difference in the two cases exceeds the threshold
tolerance.
Additional Information
PSS
E 32.0
Generating a Graphical Report Program Operation Manual
10-106 Siemens Energy, Inc., Power Technologies International
10.31 Generating a Graphical Report
Activity GRPG
The graphic report generating activity GRPG allows the user to generate arbitrary diagrams on a
customer-supported graphics output device from a file.
A dialog requesting selection from among the customer-supported graphics output devices pops
up.
Figure 10-27. Plotting Device Popup Dialog
For terminal display, enter the device number for MS-Windows (color) or MS-Windows (BW). To
close the graphic display and return to the [Terminal Read] dialog, use [Enter].
Run Activity GRPG - GUI
Diagram > Generate graphical report
Graphical Report Data file (*.grp)
GRED Library File (*.sgf)
Graphical Report Definition Data File (*.grb)
Run Line Mode Activity GRPG - CLI
ACTIVITY?
>>GRPG
ENTER INPUT FILE NAME, FILE TYPE OPTION (0=EXIT):
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 10-107
PSS
E 32.0
Generating a Graphical Report Program Operation Manual
10-108 Siemens Energy, Inc., Power Technologies International
Miscellaneous Commands
The miscellaneous commands may be entered at any time during the execution of activity GRPG.
blank or *
Blank lines and lines that contain an asterisk (-) in column one are ignored when process-
ing a GRPG input data file. They may be used to enhance the readability of the input file.
COMMENT string
The COMMENT command simply echoes the command to the users terminal. It is useful
in monitoring the progress during the execution of longer GRPG data files.
HELP [command]
The HELP command is used to display the syntax of a GRPG command. If a GRPG com-
mand is not entered, a list of GRPG commands is displayed.
INCLUDE filename [c] [OFFSET x,y] [c] [SCALE scale]
The INCLUDE command is used to insert commonly used subdrawings into a Graphical
Report Definition Data File. The optional parameters OFFSET and SCALE may be used to
modify the location and size of the subdrawing being INCLUDEd. By default, the subdraw-
ing is not offset or scaled (i.e., x,y = 0.0,0.0 and scale = 1.0).
The file <filename> must be in the form of Graphical Report Definition Data File; specifi-
cally, it may not be a GRED Library File.
ROTATE PLOT angle [c] AROUND x,y
The ROTATE PLOT command causes subsequent plotting to be rotated the specified
angle around the point <x,y>. The most common use of this command is in conjunction with
the INCLUDE command described above. This command must be included after any
INCLUDE ONE-LINE command.
SET ANGLE TO DEGREES|RADIANS
The SET ANGLE command is used to change the units by which angles are specified in
subsequent GRPG commands. By default, angles are specified in degrees.
SET UNITS TO INCHES|CENTIMETERS
The SET UNITS command is used to change the units by which distances are specified in
subsequent GRPG commands. The default is inches.
DECLARE REAL|STRING &label_l [&label_2 ... &label_10]
The DECLARE command is used to define the names of variables to be used in subse-
quent GRPG commands. All variables (labels) must be declared exactly once before they
are used in other GRPG commands. The form of each label is a 12-character string, the
first of which must be an ampersand ( & ); commas and spaces are not allowed in label
names. Up to 10 variables may be defined in a single DECLARE command. A Graphical
Report Definition Data File along with all its INCLUDEd files may have defined up to 2000
REAL variables and 500 STRING variables of up to 60 characters each. REAL variables
are initialized to zero and STRING variables to a single blank at the time they are
DECLAREd.
Siemens Energy, Inc., Power Technologies International 10-109
PSS
E 32.0
Generating a Graphical Report Program Operation Manual
10-110 Siemens Energy, Inc., Power Technologies International
The following commands are described using only one verb, but the description applies to all verbs,
with the action taken defined above.
|DRAW |
|MOVE | LINE [FROM x1,y1] TO x2,y2
|APPEND|
This form of the DRAW LINE command causes a line to be drawn from < x1,y1 > to
< x2,y2 >. If the FROM coordinate < x1,y1 > is omitted, the line is drawn from the current
position to < x2,y2 >.
|DRAW |
|MOVE | LINE FOR x,y
|APPEND|
This form of the DRAW LINE command causes a line to be drawn from the current position
< x0,y0 > to < x0+x,y0+y >.
|DRAW |
|MOVE | VECTOR [FROM x,y] FOR len [c] ANGLE ang [c]
|APPEND|
The DRAW VECTOR command causes a line of length < len > and at the angle < ang > to
be drawn from the coordinate < x,y >. If the from coordinate < x,y > is omitted, the line is
drawn from the current position.
|DRAW |
|APPEND| BOX FROM x1,y1 TO x2,y2 [c] [RADIUS rad]
|SHADE |
This form of the DRAW BOX command results in a rectangle being drawn. The rectangle
is defined by the intersections of horizontal and vertical lines through the points < x1,y1 >
and < x2,y2 >. If the optional radius is included, the corners of the box are rounded with the
specified radius < rad >.
|DRAW |
|APPEND| BOX CENTERED AT x,y WITH SIDES xl BY yl [c] [RADIUS rad]
|SHADE |
This form of the DRAW BOX command results in a box being drawn with the center at the
coordinate < x,y >. The lengths of the sides of the box are specified by < xl > and < yl >. If
the optional radius is included, the corners of the box are rounded with the specified radius
< rad >.
|DRAW |
|APPEND| CIRCLE [c] AT x,y [c] RADIUS rad
|SHADE |
The DRAW CIRCLE command results in a circle with the specified radius being drawn with
the center at the coordinate < x,y >.
Siemens Energy, Inc., Power Technologies International 10-111
PSS
E 32.0
Generating a Graphical Report Program Operation Manual
10-112 Siemens Energy, Inc., Power Technologies International
SET X|Y COORDINATE PLOTTING LIMITS TO min AND max
The SET PLOTTING LIMITS command sets the limits for the portion of the drawing to
which scaled data is mapped. This allows the user to map plotted data into, say, a gridded
area, which was generated by use of the DRAW GRID command. By default, the plotting
limits are the same as the paper limits. This command is normally used in conjunction with
the following command.
SET X|Y COORDINATE DATA LIMITS TO min AND max
The SET DATA LIMITS command sets the limits for data to be plotted via the PLOT com-
mand. As x-y pairs are read from the file, the values are scaled according to where they fall
in the data limit range. Data points outside the data limit range receive no special treatment,
but are plotted outside of the limits set in the SET COORDINATE PLOTTING LIMITS com-
mand. By default, the data limits are the same as the paper limits.
SET PLOT SYMBOL TO number
The SET PLOT SYMBOL command may be used to change the symbol to be drawn by the
PLOT SCATTER PLOT command, where < number > is the number of a symbol from the
font specified in the last SET FONT TYPE command (see Figures 10-28 and 10-29). A
< number > of zero may be specified to use a circle centered around each plotted point; this
is the default if no SET PLOT SYMBOL command is specified. It is recommended that one
of the centered symbols (0 through 14) be specified.
SET SYMBOL [HEIGHT TO size] [c] [ANGLE TO ang] [c]
The SET SYMBOL command may be used to change the height and/or rotational angle of
symbols drawn via the PLOT SCATTER PLOT command. By default, symbols are drawn
with a height of 0.1 in. and rotated zero degrees.
SET LINE TYPE TO type
The SET LINE TYPE command specifies the line pattern to be used when drawing lines to
be of type < type > where < type > is an integer with a range of one to six. A line type of one
is a solid line. Other line patterns are plotting device specific. By default, < type > is one.
SET LINE COLOR TO color
The SET LINE COLOR command specifies the color to be used for subsequent lines and
text to be of color < color >, where < color > is an integer with a range of 1 to 8. On some
devices, however, not all eight colors can be supported. In this case, the value of < color >
is adjusted to a valid color number. The resulting color for each value of < color > is device
dependent. For monochrome plotting devices, the SET LINE COLOR command is ignored.
By default, < color > is one.
SET LINE WIDTH TO width
For monochromatic plotting devices, the SET LINE WIDTH command specifies the line
thickness to be used for subsequent lines. The value of < width > can be 1 through 5. This
command is ignored for plotting devices which support color. By default, < width > is one.
Siemens Energy, Inc., Power Technologies International 10-113
PSS
E 32.0
Generating a Graphical Report Program Operation Manual
10-114 Siemens Energy, Inc., Power Technologies International
Figure 10-29. LOWERCASE Font
Siemens Energy, Inc., Power Technologies International 10-115
PSS
E 32.0
Generating a Graphical Report Program Operation Manual
10-116 Siemens Energy, Inc., Power Technologies International
does not contain lowercase characters, is used by default. The LOWERCASE font, or font
two (see Figure 10-29), contains both uppercase and lowercase characters.
The variable < fontnumber > is a positive integer through which the user may select one of
the hardware fonts available on certain PostScript printers. Refer to Guide to Printing and
Plotting for details on setting up the graphics device parameter file.
SET TEXT [HEIGHT TO size] [c] [ANGLE TO ang] [c]
The SET TEXT command may be used to change the height and/or rotational angle of text
drawn via the WRITE command. By default, text is drawn with a height of 0.1 in. and rotated
zero degrees.
SET PRINT FORMAT TO width,decimal
The SET PRINT FORMAT command specifies the format to be used for printing numeric
data in subsequent WRITE commands. The variable < width > specifies the total width of
the numeric field, including the decimal point and any leading spaces. < decimal > specifies
the number of decimal places to be printed following the decimal point. If the value is too
large to fit in < width > digits, < decimal > is reduced to accommodate it. By default,
< width > is 8 and < decimal > is 2.
WRITE item [item2 ... item10] [AT x,y]
The WRITE command builds an output line of up to 132 characters formed by the concat-
enation of the < items > specified. Items may be quoted or unquoted strings of up to 60
characters, reserved keywords enclosed in percent symbols ( % ), symbol codes enclosed
in angled brackets ( < > ), or ampersand labels. Reserved keywords and symbol codes
must be specified as uppercase characters.
If a quoted string is specified as an item, the quotes are removed before it is appended to
the output line. If the string contains any blanks, commas (,), or slashes (/), it must be
enclosed in single quotes. If a quoted string is to contain quotes, each quote within the
string must be specified as two consecutive quotes.
If a reserved keyword of the form %name% is specified as an item, a value designated by
the reserved name is appended to the output line. If the reserved name %DATE% is spec-
ified, a 17-character string containing the current date is used. If the reserved name
%TIME% is specified, a 5-character string containing the current time is used.
If a string of the form <SYMnnn> is specified as an item, the symbol for which the symbol
number is nnn is appended to the output line. Symbol numbers are dependent upon the
character font specified in the last SET FONT TYPE command (see Figures 10-28 and 10-
29).
If an item is an ampersand label (&label), the value of the corresponding GRPG variable is
appended to the output line. If the variable is of type STRING, the output includes any trail-
ing blanks that are a part of the variables value. If the variable is of type REAL, the value
is formatted according to the specifications in the last SET PRINT FORMAT command.
If < AT x,y > is specified, that coordinate value is used as a reference point for the output
line. the JUSTIFY TEXT command above for more information on text reference points. If
< AT x,y > is not specified, the output line is positioned according to the following:
If text is left justified, the output line is placed at the end of the previous output.
Siemens Energy, Inc., Power Technologies International 10-117
PSS
E working case.
Results are stored in ampersand labels, which must have been previously DECLAREd. When a
form of this command returns more than one value (e.g., a complex power), the values are stored
in consecutively DECLAREd REAL ampersand labels, starting at the one specified in the LET com-
mand. In the following forms of the LET command, if the variable on the left side is < &label >, the
command returns a single value; the variable < &label2 > on the left side indicates that two values
are returned by the command. Whenever a bus identifier is required in the LET command (busid),
either the extended bus name enclosed in single quotes or the bus number may be specified.
Power Flow Reports PSS
E 32.0
Generating a Graphical Report Program Operation Manual
10-118 Siemens Energy, Inc., Power Technologies International
LET &label2 = THE CASE TITLE
Returns the two-line case title in the STRING variables &label2 and the next DECLAREd
STRING ampersand label.
LET &label = THE NAME FOR AREA|ZONE n
Returns the name of the specified area or zone in the STRING variable &label.
LET &label2 = THE INTERCHANGE FROM AREA n TO AREA n
LET &label2 = THE INTERCHANGE FROM ZONE n TO ZONE n
Returns the complex interchange between a pair of areas or zones.
LET &label = THE MW |TRANSACTION| FROM AREA n TO AREA n [IDENTIFIER id]
|TRANSFER |
Returns the specified interarea transfer between a pair of areas in MW. If omitted, a transfer
identifier of 1 is assumed.
LET &label2 = THE NET INTERCHANGE FROM AREA|ZONE n
Returns the complex total interchange from a specified area or zone.
LET &label2 = THE GENERATION|LOAD|LOSSES FOR AREA|ZONE n
Returns the complex total generation, load or losses for a specified area or zone.
LET &label2 = THE SYSTEM GENERATION|LOAD|LOSSES
Returns the complex system total generation, load or losses.
LET &label = THE [EXTENDED] NAME FOR BUS busid
Returns the 8-character bus name or the 12-character extended bus name in the STRING
variable &label.
LET &label2 = THE GENERATION AT BUS busid
Returns the complex generation at the specified bus.
LET &label2 = THE LOAD AT BUS busid [LOADID id]
Returns the complex load at the specified bus. If the optional load identifier is omitted, total
bus load is returned; otherwise, the specified load is returned.
LET &label2 = THE ACTUAL|NOMINAL FIXED|SWITCHED SHUNT AT BUS busid
Returns the complex fixed or switched bus shunt either in MW and Mvar or in admittance.
LET &label = THE BASE VOLTAGE FOR BUS busid
Returns the base voltage of a specified bus.
LET &label = THE VOLTAGE AT BUS busid [ IN PU|KV ]
Returns the voltage magnitude at the specified bus in either per unit or kV. If the units spec-
ification is omitted, per unit voltage is returned.
Siemens Energy, Inc., Power Technologies International 10-119
PSS
E 32.0
Generating a Graphical Report Program Operation Manual
10-120 Siemens Energy, Inc., Power Technologies International
|constant| |constant|
ELSEIF |string | oper |string |
|&label_1| |&label_2|
The ELSEIF command must follow an IF or another ELSEIF command. The logical expres-
sion is evaluated only if the IF and all other preceding ELSEIF commands in the IF com-
mand block had evaluated to a false condition. Otherwise, the ELSEIF command behaves
in the same manner as the IF command.
ELSE
The ELSE command must follow an IF or ELSEIF command. The series of commands fol-
lowing an ELSE command are executed only if the IF and all preceding ELSEIF commands
in the IF command block had evaluated to a false condition.
ENDIF
The ENDIF command terminates each IF command block.
There is an unresolved problem with the ELSEIF command. It is recommended
that, until the problem is corrected, instead of using ELSEIF commands, nested IF
command blocks be used as in the following structural example:
IF ... IF ...
a... a...
ELSEIF ELSE
b... IF ...
ELSE b...
c... ELSE
ENDIF c...
ENDIF
ENDIF
Termination Commands
The termination commands are used to terminate the current plot.
ABORT
The ABORT command is used to terminate the execution of GRPG without the generation
of plotting output.
END [c]
The END command is used to terminate all GRPG data files. If the data file currently being
processed is an INCLUDE file, processing of the INCLUDE file terminates and processing
of the original file resumes. Otherwise, the plotting page is terminated and the prompt for
selection of the desired plotting device is displayed.
Only one drawing in such a file may contain SET PAPER LIMITS and SET PLOT
ORIENTATION commands. It is strongly recommended that it be the first one.
START NEW PLOT
The START NEW PLOT command is used to terminate a plotting page. Additional plotting com-
mands may follow and results in another plot being produced. This command, then, is used
between groups of data records specifying multiple drawings in a single data input file.
Siemens Energy, Inc., Power Technologies International 10-121
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-122 Siemens Energy, Inc., Power Technologies International
10.32 Viewing Graphical Output of Fault Calculations
The fault currents calculated by activity ASCC (ASCC_2 api) and activity IECS (IECS_2 api) can be
displayed on slider diagrams.
10.32.1 Display Options
Fault Calculation Results Displayed
The following types of fault currents can be displayed on one slider diagram:
Total fault currents for all faulted buses and for all fault types considered
Total fault currents and fault current contributions at home bus
Total fault currents and fault current contributions across entire network
Contour diagram of maximum fault currents at each faulted bus considered
Units of Voltage and Currents Displayed
Engineering units are established for a slider diagram using the [Program Settings] dialog. Refer
to Section 17.10, Changing PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-124 Siemens Energy, Inc., Power Technologies International
Figure 10-30. ASCC Fault Analysis Annotation Dialog
Siemens Energy, Inc., Power Technologies International 10-125
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-126 Siemens Energy, Inc., Power Technologies International
Figure 10-32. Slider Diagram, Total Fault Currents
Siemens Energy, Inc., Power Technologies International 10-127
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-128 Siemens Energy, Inc., Power Technologies International
Figure 10-34. Slider Diagram, Fault Current Contributions at Home Bus
Siemens Energy, Inc., Power Technologies International 10-129
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-130 Siemens Energy, Inc., Power Technologies International
Figure 10-36. Slider Diagram, Fault Currents for a Selected Fault
Siemens Energy, Inc., Power Technologies International 10-131
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-132 Siemens Energy, Inc., Power Technologies International
Figure 10-38. Slider Diagram, Line Outage Fault Currents
Siemens Energy, Inc., Power Technologies International 10-133
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-134 Siemens Energy, Inc., Power Technologies International
Figure 10-40. Slider Diagram, Three Winding Transformer Winding Outage Fault Currents
Siemens Energy, Inc., Power Technologies International 10-135
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-136 Siemens Energy, Inc., Power Technologies International
Figure 10-42. Slider Diagram, Three Winding Transformer, 1st Line End Fault Currents
Siemens Energy, Inc., Power Technologies International 10-137
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-138 Siemens Energy, Inc., Power Technologies International
Figure 10-44. Slider Diagram, Three Winding Transformer Winding,
2nd Line End Fault Currents
Siemens Energy, Inc., Power Technologies International 10-139
PSS
E 32.0
Viewing Graphical Output of Fault Calculations Program Operation Manual
10-140 Siemens Energy, Inc., Power Technologies International
Figure 10-46. Slider Diagram, Selected Fault, Unbalanced Fault Currents
Siemens Energy, Inc., Power Technologies International 10-141
PSS
E GUI Users Guide, Section 16.9, Exporting Power Flow Results to Microsoft Excel
E 32.0
Displaying Power Flow Solution on the Diagram Program Operation Manual
10-142 Siemens Energy, Inc., Power Technologies International
10.34 Displaying Power Flow Solution on the Diagram
Activity GOUT
The graphical power flow output activity GOUT has been replaced by a similar function in the
Diagram View of the Graphical User Interface (GUI). The PSS
E 32.0
Displaying Power Flow Data on the Diagram Program Operation Manual
10-144 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 11-1
Chapter 11
Balanced Switching
11.1 Overview: Balanced Switching
The voltage versus current characteristics of synchronous generators are different in different time
regimes. Power system network solutions must, therefore, be categorized according to the condi-
tions just before and at the instant for which the solution is to apply. The time regimes of significance
in network solutions are illustrated in Figure 11-1.
All power system simulations assume that the system is in the steady state for an extended period
prior to the time, t. It is assumed that the first incident of interest, such as a switching operation,
fault, load change, or control setpoint change, occurs at, t. Power flow calculations apply to the
instant, t
(t minus). The power flow generator boundary conditions, therefore, assume that the
system is in the steady state, or more practically, experiencing the gentle motions of normal undis-
turbed operation. Every power flow calculation establishes the condition of the entire transmission
network, outward from generator terminals to load terminals, for an instant, t
.
Balanced Switching PSS
E 32.0
Overview: Balanced Switching Program Operation Manual
11-2 Siemens Energy, Inc., Power Technologies International
Figure 11-1. Time Regimes Considered in Power System Simulations
Any switching operation, fault, significant load change or change of control inputs (governor or exci-
tation system reference) starts the system moving. PSS
. Loads are
commonly assumed to have a constant MVA steady-state characteristic in steady-state power flow
solutions applying to t
, to switching conditions at t
+
, and to system dynamic behavior over an
t Time
t Time
Generator
Internal
Flux
Linkage
Network
Variable,
(Voltage
or Current)
t
Conditions
(Steady-State)
t+
Conditions
(Switching)
Post Disturbance
Conditions
(Dynamics of
System)
Siemens Energy, Inc., Power Technologies International 11-3
PSS
E analytical processes.
Switching, or t
+
, solutions and dynamic simulations require the generator boundary conditions to be
set in accordance with the electromagnetic laws governing rotor flux linkages. Therefore, the power
flow boundary condition in which power output and bus voltage are specified, must be replaced by
a specification of a Thevenin or Norton source where instantaneous value is determined by instan-
taneous values of flux linkages. The generator boundary conditions applying at instants, t
and t
+
,
are illustrated by Figure 11-2. The t
+
boundary condition recognizes that generator rotor flux link-
ages must obey Lenzs and Maxwells laws.
Figure 11-2. Standard Power Flow Model and Norton Equivalent Used for
Switching and Dynamic Studies
e
k
~
P
k
jQ
k
+
Bus k
a. Standard Power Flow Model
Z
t
t
g
:1
e
k
~
E
int
o Z
Z
dyn
-------------------
ISORCE
y
1
Z
dyn
-------------- =
b. Norton Generator Equivalent for Switching and Dynamic Simulation Calculations
Balanced Switching PSS
E 32.0
Overview: Balanced Switching Program Operation Manual
11-4 Siemens Energy, Inc., Power Technologies International
11.1.1 Objectives of a Balanced Switching Study
The objective of a switching study is to calculate the conditions that will exist in the power system
just after a sudden change such as the opening of a transmission line, switching on of a large load,
application of a fault, or tripping of a generator. These calculations are useful, for example:
1.To show the immediate voltage dip caused by switching on of a large motor.
2.To give symmetrical fault duty at a bus.
3.To show the immediate change of flow that will be seen on each tie-line into an area
(before the inertial swing of rotor angles) when one such tie or a generator within the
area is tripped.
4.To show the voltage rise which occurs when a line is opened at one end. This could sepa-
rate a generation plant from the network and result in what is commonly known as load
rejection.
A switching study is a calculation of conditions at time, t
+
. A switching study is, in effect, the calcu-
lation of the transmission system conditions at the first instant, t = t
+
, of a dynamic simulation,
separated from the subsequent calculation of conditions at later instants, t > t
+
. Switching study
results are presented and examined with the same output and limit checking activities as are used
in power flow work studies.
11.1.2 Preparing a Power Flow Case for Balanced Switching
Prior to performing the switching operations, the user must prepare the power flow case. The three
steps are to:
Ensure the power flow case is solved and contains the required generator dynamic
data
Convert the generators to a Norton Equivalent (generator boundary condition, activity
CONG)
Convert the loads to a voltage dependent model (load boundary condition, activity
CONL)
These operations result in a converted power flow case which can be saved in its converted form
for subsequent switching analyses. Note that this converted case should be saved using a different
name because the conversion process is not reversible.
11.1.3 Establishing the Power Flow Base Case for Balanced Switching
The starting point for a switching study is a conventional solved power flow case giving data and
solution corresponding to the pre switching (t
E 32.0
Overview: Balanced Switching Program Operation Manual
11-6 Siemens Energy, Inc., Power Technologies International
Figure 11-3. Switching Analysis Sequence of Processes
Perform the Switching Operation
Open <file> to
Recover Converted
Power Flow Case
Solve Initial Condition Power Flow
Convert Generators
Convert Loads
Order Network
Save the Converted Case t
-
Model
Factorize and Solve the Network
Output the Results
Perform Another Switching
Operation from the Same
Initial Condition
New Initial Condition Required?
Open <file> to Recover
Initial Condition
Power Flow Case
Make Required
Changes to Initial
Condition Power Flow
Siemens Energy, Inc., Power Technologies International 11-7
PSS
E uses the same power flow working case for power flow, fault analysis, and dynamic simu-
lation calculations. The representation of a generator as a voltage behind an apparent impedance,
as required for fault analysis and dynamic simulation, is handled by a Norton equivalent for each
generator.
The data characterizing the Norton equivalent for each generator consists of the machine MVA
base (MBASE) and the machine impedance (ZSORCE). Values for these data items are entered as
generator data via the PSS
E 32.0
Converting Generators Program Operation Manual
11-8 Siemens Energy, Inc., Power Technologies International
[Spreadsheet]. The value specified for ZSORCE may be the generator transient impedance, subtran-
sient impedance, or any other value of impedance that may be a meaningful characterization of the
generator for the study at hand. In addition, the generator step-up transformer may be represented
as part of the generator model itself or explicitly as a network branch (refer to Section 11.2.3). Refer
to Generator Data for additional details on these data parameters. Note that the value of ZSORCE
must be specified on the generator MVA base (i.e., on MBASE base) and that it is a complex
number (resistance and reactance).
The correspondence between the commonly recognized Thevenin equivalent generator represen-
tation and the Norton equivalent used in PSS
E by its terminal and/or high side buses only. Furthermore, the fictitious shunt
branches representing generators are automatically separated from real shunt admittance at the
generator buses so that their presence does not affect power flow output reports from PSS
E. Only
the shunt elements representing actual reactors and capacitors are shown under the heading
SHUNT in PSS
E reports.
ZSORCE and MBASE data need not be entered if the working case being constructed is to be used
only for standard power flow solutions. When no data is entered, MBASE and ZSORCE take on
default values equal to the system base MVA and j1.0 pu, respectively.
The report generated by activity GEOL will not be valid for any generators for which MBASE
and ZSORCE are not specified.
Siemens Energy, Inc., Power Technologies International 11-9
PSS
E (XTRAN = 0.0)
WINDV1:WINDV2
Y = 1. / ZSORCE
RT + jXT
High Side Bus
(Type 2)
Terminal Bus
(Omitted)
Norton
Current
Source
c. Norton Generator Equivalent Used in PSS
E 32.0
Converting Generators Program Operation Manual
11-10 Siemens Energy, Inc., Power Technologies International
11.2.3 Generator Step-Up Transformers
The user may select one of two methods of representing the generator step-up transformer for each
machine.
The traditional method involves representing the step-up transformer as a standard power flow
transformer branch. Both the generator terminal bus and the high side bus are contained in the case
along with a transformer branch between them representing the step-up transformer. The terminal
bus is the Type 2 (or 3) bus and the high side bus has a Type code of 1. This representation is shown
by Figure 11-4b.
The alternative approach is to represent the step-up transformer as part of the generator modeling.
In this method, the high side bus is represented in the power flow case as a Type 2 bus and the
terminal bus is not present. The step-up transformer impedance and off-nominal ratio are repre-
sented by the generator data items XTRAN (i.e., RT + jXT) and GTAP, respectively (refer to
Generator Data). XTRAN is entered on generator base (i.e., on MBASE base) and is a complex
number (resistance and reactance). This representation is shown by Figure 11-4c.
When XTRAN is non-zero (i.e., the generator bus is the high side bus), the generator boundary
conditions (i.e., voltage setpoint, active power output, and reactive power limits) are as seen at the
high side bus. Generator terminal conditions may be examined with activity GEOL.
When XTRAN is zero, PSS
E 32.0
Converting Load Characteristics Program Operation Manual
11-12 Siemens Energy, Inc., Power Technologies International
11.3 Converting Load Characteristics
Activity CONL
The load conversion activity CONL converts the constant MVA load for a specified grouping of
network loads to a specified percentage for constant current or constant admittance load character-
istics of the existing constant MVA load (refer to Load Data and Section 6.3.13).
11.3.1 Modeling Load Characteristics
Normal practice in power flow work is to assume that distribution system tap changers and voltage
regulators have brought customer voltages to nominal values and, hence, that load at the buses
represented in the power flow case may be treated as a constant real and reactive power demand.
It is generally recommended, therefore, that load is treated as constant MVA from one power flow
case to the next.
This is particularly true of conventional planning studies where demand level is a given quantity
which must be maintained under a variety of system normal and abnormal conditions. The
Planners job is to identify the lines and equipment required to sustain the defined demand levels;
it is axiomatic that the demand level is a given (constant MVA).
In steady-state and quasi steady-state operation studies, it is reasonable to recognize the loads
dependence on voltage. Such studies include balanced switching, short-circuit analysis (Chapter 9)
and examination of potential voltage collapse or voltage instability. These are conditions under
which voltage excursions can be significant.
Similarly, under dynamic conditions, which would be simulated with the PSS
E dynamic simulator,
treating loads as purely constant MVA at the reference load value is not acceptable because time
delays in distribution voltage-regulating devices prevent them from adjusting customer voltages in
the period of interest. Furthermore, loads have a frequency dependence. For dynamic studies,
therefore, a variety of load models of varying complexity are available. These models recognize, in
more detail, the specific characteristics of loads such as lighting, heating and motor loads. The
PSS
E Model Library.
Run Activity CONL - GUI
Power Flow > Convert Loads and Generators
[Convert / Reconstruct Loads and Generators]
OPTION: Convert / Reconstruct Loads; Convert constant MVA loads
Run Line Mode Activity CONL - CLI
ACTIVITY?
>>CONL
ENTER UP TO 20 BUS NUMBERS
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 11-13
PSS
E identify the load at each bus and allow the user to indicate the
following components of each load.
All of these components are specified in MW and Mvar. The MW and Mvar values for the constant
current and constant admittance components are the values that would be consumed by these
loads when the bus voltage is unity per unit. The values of these components can be changed,
using the editing facility in the Spreadsheet View or the load can be taken out of service by changing
its status in the Spreadsheet View.
While it is possible to enter bus loads as combinations of constant MVA, constant current and
constant admittance, it is preferable to enter the total load as constant MVA mainly because the
majority of steady-state analysis will be performed at or close to nominal voltage and the total
demand level is critical to the study at hand. It is a simple exercise to convert system loads from the
constant MVA characteristic to either of the voltage dependent characteristics or a combination of
all three depending on the type of analysis being carried out. It is equally simple to reconvert the
loads to have their original characteristic or any other combination.
11.3.3 Converting Load Characteristics
The conversion process in PSS
E 32.0
Converting Load Characteristics Program Operation Manual
11-14 Siemens Energy, Inc., Power Technologies International
S
P =
Final constant MVA load on bus (real, MW, or reactive, Mvar).
S
I =
Final nominal constant current load on bus (real, MW, or reactive, Mvar).
S
Y =
Final nominal constant shunt admittance load on bus (real or reactive).
a,b = Load transfer fractions, (a + b) < 1
(Real and reactive load may be allocated by different a and b values.)
v = Magnitude of bus voltage when load conversion is made.
The conversion and re-allocation process is diagrammed in Figure 11-5.
Figure 11-5. Re-allocation of Constant MVA Bus Load
It is useful to note the following points regarding the load conversions:
1. The conversion is performed only on the constant MVA load.
2. Load converted to constant current and constant admittance is added to any existing load
represented by those characteristics.
3. The load is converted on the basis of the actual voltage at the network buses. Prior to
conversion the working case should be solved to an acceptable mismatch level. Following
conversion, the network is still in balance.
4. The split of load among the three characteristics may be different for the active and reactive
components of load.
5. Admittance load is stored separately from the bus shunt.
Furthermore, following conversion, only the new components are accessible for editing.
Siemens Energy, Inc., Power Technologies International 11-15
PSS
E 32.0
Converting Load Characteristics Program Operation Manual
11-16 Siemens Energy, Inc., Power Technologies International
Figure 11-6. Reference Load Values in Savnw.sav Power Flow Case
Figure 11-7. Converted Loads Re-allocations as per Figure 11-6
11.3.7 Application Notes
The portion of the load which is represented as constant MVA load is converted as specified by
activity CONL. Any of that load to be converted to the constant current and admittance character-
istics is added to the load already represented by those characteristics.
It is useful to note the following points regarding the load conversions:
1. Activity CONL converts only the constant MVA load.
2. Load converted to constant current and constant admittance is added to any existing load
represented by those characteristics.
3. The load is converted on the basis of the actual voltage at the network buses. Thus, activity
CONL requires that the working case be solved to an acceptable mismatch level. Following
completion of activity CONL, the network is still in balance.
4. The split of load among the three characteristics may be different for the active and reactive
components of load.
5. The presence of constant MVA and/or constant current reactive power load may require
slight deceleration in activity TYSL and dynamic simulations for optimum performance.
Siemens Energy, Inc., Power Technologies International 11-17
PSS
E 32.0
Reconverting Load Characteristics Program Operation Manual
11-18 Siemens Energy, Inc., Power Technologies International
11.4 Reconverting Load Characteristics
Activity RCNL
The load reconstruction and conversion activity RCNL reconstructs the constant MVA load for spec-
ified network loads. It then converts the reconstructed MVA load to a specified mixture of the
constant MVA, constant current, and constant admittance load characteristics (refer to Load Data
and Sections 6.3.13 and 11.3).
11.4.1 Reconverting Load Characteristics
It is possible to reconstruct the constant MVA load from a mixture of the three load characteristics
for selected network loads. Subsequently, it is possible to then convert the reconstructed constant
MVA load to a different specified mixture of the constant MVA, constant current, and constant admit-
tance load characteristics. The reconstruction process as illustrated in Figure 11-8. The process
first collects all load back into a single constant MVA load and then reallocates it into constant MVA,
constant current, and constant admittance components in the same manner as the conversion
process.
Run Activity RCNL - GUI
Power Flow > Convert Loads and Generators
[Convert / Reconstruct Loads and Generators]
OPTION: Convert / Reconstruct Loads; Reconstruct loads
Run Line Mode Activity RCNL - CLI
ACTIVITY?
>>RCNL
ENTER LOAD RECONSTRUCTION OPTION:
1 FOR PRESENT VOLTAGE 2 OR 3 FOR UNITY VOLTAGE:
>>
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 11-19
PSS
E 32.0
Reconverting Load Characteristics Program Operation Manual
11-20 Siemens Energy, Inc., Power Technologies International
When reconstructing loads based on unity voltage, the three load components are summed
assuming one per unit voltage, (v = 1.0) and this total load is split among the three load character-
istics as specified. The network will normally not be in balance following this process with this load
reconstruction option.
11.4.2 Operation of Activity RCNL
The user specifies the option to be used in reconstructing the MVA load: present voltage or unity
voltage. Refer to Section 11.4.4 for details on the load reconstruction options. The user may specify
the buses where loads are to be processed (refer to Section 4.8) by area, zone, owner, or basekV.
When processed by basekV, activity RCNL processes all loads at each bus where base voltage falls
within the specified base voltage band. When processed by area, zone, or owner, each load
assigned to one of the areas, zones, or owners specified is converted (refer to Load Data). The
area, zone, or owner assignments of buses (refer to Bus Data) are not considered in these
subsystem specifications.
Activity RCNL prints the the number of loads reconstructed out of the total number of loads in the
working case.
11.4.3 Example of Load Reconstruction
In this example the option to reconstruct using present voltage has been selected and the re-allo-
cation is to 10% of total load for both real and reactive power for constant current and constant
impedance loads.
Section 11.3.6 shows an example conversion process in which Figure 11-6 shows the MVA loads
in the savnw.sav power flow case, as initially defined. That conversion example re-allocates the
loads with the result shown in Figure 11-7. The conversion was done on all loads.
With that converted load as a starting point, the reconstruction can be done based on the realloca-
tions shown in Figure 11-8 above. The result is shown in Figure 11-9.
Figure 11-9. Reconstruction of Loads Based on Global 10% Reallocation
Siemens Energy, Inc., Power Technologies International 11-21
PSS
E 32.0
Ordering Network Buses for Matrix Manipulation Program Operation Manual
11-22 Siemens Energy, Inc., Power Technologies International
11.5 Ordering Network Buses for Matrix Manipulation
Activity ORDR
The optimal ordering activity ORDR determines an ordering of the network buses such that sparsity
is maintained as the Jacobian matrix is triangularized in activities FNSL, NSOL, FDNS, INLF, and
ACCC, or the system admittance matrix is decomposed into its triangular factors in activities FACT
and BKDY and the linearized network analysis activities DCLF, DFAX, DCCC, OTDF, TLTG, SPIL,
and POLY.
Because it changes at least one bus type code, the generator conversion process (activity CONG)
must be followed by an ordering of the network buses such that sparsity is maintained as the Jaco-
bian matrix is triangularized in a variety of PSS
E 32.0
Ordering Network Buses for Matrix Manipulation Program Operation Manual
11-24 Siemens Energy, Inc., Power Technologies International
When the Ignore out-of-service branches option is specified, activity ORDR recognizes the status
of network branches and ignores out-of-service branches in determining the bus ordering. Thus,
when a branch previously out-of-service is returned to service, activity ORDR should be executed
again. Branch status changes that do not isolate a bus do not require repeated executions of activity
ORDR. However, when a large number of branches have been taken out-of-service, this option may
result in a more efficient matrix storage, thereby decreasing both the time and memory required to
perform calculations using the network matrices.
Activity ORDR must be re-executed whenever any of the following takes place:
1. The addition of a bus or branch to the case.
2. A change to the Type code of a bus from 1 or 2 to 3 or 4, or vice versa. Note that this includes
the execution of those PSS
E GUI Users Guide, Section 17.2, Ordering Network Buses for Matrix Manipulation
PSS
Transmission Line
Transmission Line
j
k
i
n
m
Tap Changer
Tap
Changer
Transformer
Shunt Reactor and Capacitors
E 32.0
Factorizing the Network Admittance Matrix Program Operation Manual
11-26 Siemens Energy, Inc., Power Technologies International
Figure 11-12. Equivalent Circuit for Node i of Transmission Network Model
The total current, i
i
, flowing into node i when voltages, v
i
, v
j
, v
k
, v
m
, and v
n
are applied to the
network are determined by adding up the flow into each leg of Figure 11-12 at its connection to node
i. In the case shown above, the total current, i
i
, is zero because there is no source or load connected
there. Hence:
(11.1)
Expansion of Equation 11.1 for the i-th element of I
n
, which is i
i
, gives:
(11.2)
where
y
ih
are the elements of Y
nn
n
t
in
: 1
Z
in
Z
ij
j
B
ij
2
B
ij
2
m
Z
i m
1: t
im
i
k
B
ik
2 B
lik
Y
si
2
Z
ik
B
ik
i
i
= v
i
Y
si
+ (v
i
- v
k
) / z
ik
+
+ (v
i
- v
j
) / z
ij
+
2
2
v
i
B
ij
v
i
B
ik
+ v
i
B
lik
+
+
- v
m
v
i
-
v
n
/ z
im
t
im
t
im
v
i
t
in
/ z
in
i
i
=
n
n = 1
y
ih
v
h E
Siemens Energy, Inc., Power Technologies International 11-27
PSS
E.
Examination of Equation 11.1 shows that only the diagonal element, y
ii
, and four off-diagonal
elements, y
ih
, of the i-th row of the admittance matrix are nonzero. That is, a line or transformer from
bus i to bus j contributes nonzero elements only to the i-th and j-th rows of Y
nn
. Realistic power
systems have between 1.5 and 2 transmission lines or transformers for each node. A transmission
network of 2000 buses might, therefore, be expected to have approximately 4000 branches and,
correspondingly, 8000 nonzero off-diagonal elements in its admittance matrix. This typical bus-to-
branch ratio results in very sparse admittance matrices. In the above example only 8000 out of
(2000) (2000-1), or 0.2% of the off-diagonal elements of Y
nn
are nonzero.
The great majority of modern power flow calculation programs, including those of PSS
E, take
advantage of this sparsity in their management of computer storage. They also take advantage of
procedures that allow the admittance matrix to be manipulated into triangular factor and partial
inverse forms which have similar sparsity properties, but where the number of nonzero off-diagonal
elements is typically two to three times the number of such elements in the original Y
nn
matrix.
Presenting a power flow program with a power system network model, for which original Y
nn
matrix
(or derivatives therefrom) has a number of nonzero elements that exceed the programs allocated
capacity, results in an error condition that prevents the use of some, but not all, of the available
power flow iteration algorithms.
11.6.2 Operation of Activity FACT
The triangular factorization activity FACT decomposes the network admittance matrix (Y matrix) into
its upper and lower triangular factors for use in the triangularized Y matrix network solution (activity
TYSL) or in the network balance of dynamic simulations. This computation also takes place, without
being specifically invoked, by the following functions:
Because activity FACT performs a computation involving the admittance matrix, it follows that it
must be re-executed any time this matrix changes and switching studies or dynamic simulations are
to be run. Thus, in these applications, activity FACT must be rerun any time one or more of the
following occurs:
Change of load characteristic modeling via activities CONL or RCNL.
Change of bus type code.
Change of machine, branch or load status.
Change of machine impedance parameters.
Change of branch impedance or charging.
Change of which branches are modeled as zero impedance lines.
ASCC ASTR BKDY EEQV IECS
MSTR MRUN SEQD SCMU SCEQ
STRT RUN DYNAMICSMODE
Balanced Switching PSS
E 32.0
Factorizing the Network Admittance Matrix Program Operation Manual
11-28 Siemens Energy, Inc., Power Technologies International
Change of transformer ratio or phase shift angle.
Change of bus or line connected shunt.
Change of constant admittance load.
Activity FACT tabulates the number of non-zero diagonal and off-diagonal terms in each factor of
the matrix at the Progress tab.
Activity FACT requires the prior execution of activity CONG, usually activity CONL, and activity
ORDR. Refer also to Section 11.7.5. It prints an appropriate error message and terminates if gener-
ators have not been converted (i.e., activity CONG has not been executed). If activity FACT detects
that a new execution of activity ORDR is required, a message is printed and activity ORDR is auto-
matically executed prior to the factorization.
11.6.3 Exporting the Power Flow Network Admittance Matrix
All or part of the network admittance ( Y ) matrix, as used in the PSS
E power flow solution functions. As such, they include constant admittance loads,
off-nominal tap ratios, and phase shifts, but exclude constant MVA load, constant current load,
generator, switched shunt, dc line, and FACTS device contributions. Furthermore, the admittance
matrix used during the power flow solutions excludes rows and columns for swing (i.e., Type 3)
buses; this function also excludes terms from these rows and columns unless generators are
converted (i.e., activity CONG is executed) prior to initiating this function.
Because the admittance matrix is extremely sparse, its terms are produced as a set of matrix terms,
using external bus numbers, as in the following example:
154, 154, 41.9126 , -404.786
154, 3008, -5.49574 , 44.7801
154, 153, -4.47154 , 40.2439
154, 205, -29.4701 , 297.380
154, 203, -2.47525 , 24.7525
Siemens Energy, Inc., Power Technologies International 11-29
PSS
E GUI Users Guide, Section 17.3, Factorizing the Network Admittance Matrix
PSS
E 32.0
Solving the Converted Case Program Operation Manual
11-30 Siemens Energy, Inc., Power Technologies International
11.7 Solving the Converted Case
Activity TYSL
The triangularized Y matrix network solution activity TYSL is designed for those situations where
the internal flux linkages of generators are assumed to remain unchanged as a load or fault is
switched onto the system, as a line is opened or closed, or as a load is removed. It determines the
instantaneous change in network voltages as the switching operation takes place. This activity is
used for balanced short circuit, motor starting, voltage dip, and initial load rejection overvoltage
studies; this class of studies is called switching studies.
When the flat start option is specified, all bus voltages are reset to unity magnitude at zero phase
angle. Otherwise, the existing voltage vector in the working case is used as the initial voltage esti-
mate. During the solution, generator buses are not treated as they are in power flow solution
calculations. Rather, the Type 2 bus voltages become free variables just as the voltages at Type 1
buses, and a fixed source current is injected into the network at each generator bus (refer to
Figure 11-4).
Activity TYSL handles load boundary conditions and the blowup check in the same way as activity
SOLV. The solution convergence monitor, the dc transmission line monitors for two-terminal and
multi-terminal dc lines, and the mismatch summary are identical to those of activity SOLV. Refer to
Sections 6.3.11 and 6.3.13.
No automatic adjustments are allowed, and switched shunt devices and dc converter transformer
tap settings are locked at their pre-switching settings. A two-terminal or multi-terminal dc transmis-
sion line is blocked for the remainder of the current execution of activity TYSL if, on any iteration,
the ac voltage at a rectifier converter station bus falls below 50% or is insufficient to make margin
order. Shunt elements of FACTS devices hold their pre-switching reactive currents, and series
elements are held at their pre-switching series voltages.
For each in-service VSC dc line, the solution starts with each converter holding the active and reac-
tive power at the time activity CONG was executed. If, on any iteration, the corresponding current
exceeds the converters IMAX, the injection is reduced using the power weighting factor fraction
(PWF) just as in the conventional power flow solution activities. Each converter is treated indepen-
dently, so that any reduction at one converter does not affect the injection at the other end of the
VSC dc line. The dc transmission line monitor for VSC dc lines includes the dc line name, followed
by the ac power injection at each converter bus.
By default, activity TYSL has a convergence tolerance of 0.00001 on voltage change and a limit of
20 iterations. A deceleration factor, which has a default value of unity, is applied to the voltage
Run Activity TYSL - GUI
Power Flow > Solution > Solution for switching studies (TYSL)
[Solution for Switching Studies]
Run Line Mode Activity TYSL - CLI
ACTIVITY?
>>TYSL
Interrupt Control Codes
AB, NC, DC, FD
Siemens Energy, Inc., Power Technologies International 11-31
PSS
E 32.0
Solving the Converted Case Program Operation Manual
11-32 Siemens Energy, Inc., Power Technologies International
11.7.1 Example:Voltage Rise on Open Line End
The calculation of voltage on the open end of a line is often required to examine the conditions
which could be encountered by line connected reactors; by surge arresters and by breakers. The
latter have limits of voltage across the open break within the equipment. Voltage on the line side
could be high while voltage on the system side could have fallen due to loss of the lines incoming
power.
This example will open the line from bus 151 to bus 152, circuit 1, at the end terminating on bus
152, in the savnw.sav power flow case. Figure 11-13 shows the power flow diagram for these
buses.
Figure 11-13. Example Circuits from Bus 151 to Bus 152
One way of performing the breaker operation, is to establish a dummy bus on the circuit from bus
151 to bus 152 which is connected to Bus 152 via a zero impedance line. To open the breaker it
would require taking the zero impedance line out of service (see Figure 11-14). The circuit from bus
151 to the dummy bus 999 will have the same line parameters as the actual circuit from bus 151 to
bus 152 circuit 1. When the zero impedance line between bus 999 and bus 152 is opened, circuit 1
from bus 151 will be connected at bus 151 and hanging open. The post-switching voltage at bus
999 is the line-end voltage of interest together with the voltage at bus 152.
Siemens Energy, Inc., Power Technologies International 11-33
PSS
E 32.0
Solving the Converted Case Program Operation Manual
11-34 Siemens Energy, Inc., Power Technologies International
The sequence of events for this model is:
1. Convert the power flow case (activity CONG) and order the network buses (activity ORDR).
2. Split the bus (activity SPLT) and open the new zero impedance line to create an open ended
line.
3. Factorize the matrix (activity FACT).
4. Perform the Y matrix solution (activity TYSL).
Now the voltages can be examined with a bus based report or by examining the solution shown in
the diagram.
11.7.2 Example: Open Line End Results
It is interesting to look at the bus voltages, in this example, on buses 151, 152 and 9999 for the
power flow condition, for the post switching condition and for a condition obtained by opening the
line in the unconverted power flow case and solving with a conventional solution (e.g., Gauss-
Seidel). This latter case will show conditions after all the voltage regulation devices have had time
to operate to adjust back to set-point voltages (V long-term).
It can be seen that immediately after switching the voltage at bus 152 drops because of the sudden
loss of incoming power and the need for greater voltage support. The voltage at bus 151 rises
slightly because, in part, of unconsumed reactive power from the open line. The line end voltage
has increased from its original level of 1.017 pu to 1.112 pu (see Table 11-1).
Following voltage regulator action, the voltage at all buses has been reduced to a new steady-state
level. The voltage at the open end is elevated but reasonable for sustained operation.
11.7.3 Example: Motor Starting
A fairly common switching study requirement is illustrated by Figure 11-16. One of a pair of large
motors is running under load, and the second one is to be started by switching it directly onto the
bus. The extent of the voltage dip produced by switching on the second motor is needed for the
coordination of overcurrent and undervoltage protection.
The example will assume a load at bus 3006, in the savnw.sav power flow case, to consist of two
large motors which, at full load and unity voltage, draw (7.5 + j3.95) MVA each. The starting current
for one motor is given in specification data as 2.72 times rated current at 0.275 power factor. The
calculation in Figure 11-16 shows that this starting duty corresponds to an initial shunt admittance
of (0.0625 j0.218) per unit, relative to a 100-MVA base (I = YV), and nominal voltage.
Table 11-1. Results of Line Open End Balanced Switching Calculation
Results of Line Open Operation
Bus Number V pre-switch V post-switch V long-term
151 1.012 1.023 1.015
152 1.017 0.996 0.981
9999 -- 1.112 1.104
Siemens Energy, Inc., Power Technologies International 11-35
PSS
E 32.0
Solving the Converted Case Program Operation Manual
11-36 Siemens Energy, Inc., Power Technologies International
11.7.4 Example: Fault Current
Because these examples lie within the realm of balanced switching, the only faults which can be
analyzed are three-phase faults.
In the case of a three-phase fault, the switching operation which is performed before factorization
and solution is the connection of a very large reactive admittance to ground at the fault point. A
value of -j1E9 is adequate. After a solution has been obtained for the instant, t
+
output of results is
handled by the standard power flow output formats such as the bus based reports. Such a bus
based report will provide the fault point and branch information (see Figure 11-18).
Figure 11-18. Calculation of Branch Currents Flowing into a Bus Faulted
through Zero-Impedance
The format of the bus based report will be unchanged except that it will display the net current
flowing to ground at any bus where voltage is below 0.1 per unit. This current value is expressed in
terms of fault MVA where
FAULT MVA = \3 (Base Voltage, kV) (Current, A) 10
-3
i
j
v = 0
v
i
u
i
per unit Z
P
ij
jQ
ij
= MVA
ij
+
P
ij
jQ
ji
+ (0. j0.) + =
MVA
ji
0. =
MVA
jk
0. =
Z
f
(0. j0.) + =
I
kj
MVA
kj
SBASE V
k
E 32.0
Solving the Converted Case Program Operation Manual
11-38 Siemens Energy, Inc., Power Technologies International
11.7.5 Application Notes
Activity TYSL is not a power flow solution; it is unable to handle the power flow style representation
of generator buses (i.e., fixed power and voltage). But, for networks in which generators are repre-
sented by constant internal flux linkages (i.e., following activity CONG), activity TYSL is capable of
producing very small mismatches in only a few iterations. (Note that its default convergence toler-
ance is an order of magnitude smaller than that of activities SOLV and MSLV!). It is much less
sensitive to the values of branch impedances than the other network solution activities.
The use of activity TYSL for switching study network solutions involves operations upon the factor-
ized system admittance matrix. Thus, a typical sequencing of activities is:
1. A standard power flow is converged to an acceptable mismatch level using one or more of
activities SOLV, MSLV, FNSL, NSOL, or FDNS. It is strongly recommended that the solved
power flow case be saved in a Saved Case File with activity SAVE.
2. Activity CONG is executed to convert generator buses from their power flow representation
to the constant Norton current source representation used in activity TYSL. See also
Figure 11-4.
3. Activity CONL is executed to convert the load boundary conditions from the conventional
constant MVA characteristic used in power flow calculations to a representation suitable for
network conditions involving abnormally low or high voltages (refer to Load Data and
Section 6.3.13).
4. Activity ORDR is executed to determine a bus ordering of the admittance matrix such that
its sparsity characteristics are preserved. A new bus ordering is required because the
execution of activity CONG introduces a row and column into the admittance matrix for each
former Type 3 (swing) bus.
5. Optionally, this converted and ordered case may be saved with activity SAVE if several
switching solutions are to be calculated from this base condition.
6. Apply the switching via activity CHNG or the [Solution Parameters] dialog, factorize the corre-
sponding admittance matrix with activity FACT, and balance the network with activity TYSL.
7. The standard power flow output reporting activities (e.g., POUT, VCHK, etc.) are used to
examine the results of the post-switching network solution.
8. Additional switchings may be imposed on the same base condition by retrieving the
converted case saved in step 5 and proceeding to step 6.
Note again that activity TYSL requires that the factorized admittance matrix, representing the
switching operation imposed upon the pre-switching network condition, be present in the admit-
tance matrix temporary file.
Additional Information
PSS
E 32.0
Solving the Converted Case Program Operation Manual
11-40 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 12-1
Chapter 12
Transmission Pricing and
Open Access
12.1 Overview: Open Access and Pricing
Activity Open Access and Pricing
The electric utility industry restructuring, prevalent in the United States and many other countries in
the close of the 20th century has generated interest in analytic tools for transaction processing.
Open Access and Pricing Activities (OPA) have been introduced to the power flow processor to aid
in assessing transaction feasibility, and cost allocation. In PSS
E allocation
function. Transmission loss allocation techniques also are provided.
OPA requires a power flow model, which can be employed to produce a valid dc power flow solution,
be imported into PSS
E 32.0
Managing Transaction Data Program Operation Manual
12-2 Siemens Energy, Inc., Power Technologies International
12.2 Managing Transaction Data
Activity Transaction Data
Each transaction event the user first assigns a set of transaction attributes and then identifies which
buses will be participating in the transaction event. The transaction attributes are the following:
For each transaction event the user identifies which will be the participating buses. For each partic-
ipating bus, the following information is required:
Table 12-1 shows an example transaction data consisting of two transaction events.
ID A Transaction event number. ID = 0 by default.
DESCRIPTION Alphanumeric label assigned to the transaction event. The label may be up to
twenty four characters and may contain any combination of blanks, upper-
case letters, numbers and special characters. LABEL is twenty four blanks by
default.
STATUS Transaction event status: 0 for out-of-service, 1 for in-service. STATUS = 0 by
default.
PRIORITY Transaction event priority. This integer value priority number is used to group
transactions into sets. IPR = 0 by default.
MAGNITUDE Transaction event magnitude in MW. MAG = 0.0 by default.
CURTAILMENT Transaction event curtailment magnitude in MW. CURT = 0.0 by default.
I Bus number. I = 0 by default.
LOAD Participating bus load value. LV = 0.0 by default.Can be negative.
GENERATION Participating bus generation value. GV = 0.0 by default.Can be negative.
Table 12-1. Example of Transaction Data for Two Transactions
Typical Transaction Data
First Transaction
6 UPSTART 1 1 200.0 0.0 Transaction Attributes
3008 1.0000 .0000
Participating Buses
102 .0000 .2667
Second Transaction
5 WORLD 1 1 354.0 0.0 Transaction Attributes
3008 .0000 1.0000
Participating Buses
3007 1.0000 1.0000
3006 1.0000 1.0000
3005 1.0000 1.0000
3004 .0000 1.0000
3003 .0000 1.0000
3002 .0000 1.0000
Siemens Energy, Inc., Power Technologies International 12-3
PSS
E 32.0
Calculating Transaction Event Impact on Monitored Elements Program Operation Manual
12-4 Siemens Energy, Inc., Power Technologies International
12.3 Calculating Transaction Event Impact on Monitored
Elements
Activity IMPC
Activity IMPC computes and reports the incremental MW flow impact on a set of monitored
elements due to a single transaction event.
The user must enter the name of a Distribution Factor Data File constructed by activity DFAX which
corresponds to the network condition contained in the working case (refer to Section 7.1.6) and to
the desired Linear Network Analysis Data Files (refer to Section 7.1.1). The Distribution Factor Data
File must specify at least one monitored branch or interface. The bus input option (refer to
Section 3.3.3 and activity OPTN) must have the same setting that was in effect when activity DFAX
filled the specified file. Refer to Section 2.4.1 for the file specification conventions used by activity
IMPC.
The Distribution Factor Data File defines the monitored element set. It employs the transaction
magnitude, without regard to the curtailment value, to determine the power injections and demands
at participating buses. It employs the linearized solution technique to compute the incremental
element flows. Regulating in-service phase shifting transformers have zero incremental MW flow.
The user may provide the name of an ATC Updates File, which is optional. This file may modify the
monitored interface ratings employed in the report as available transfer capability (ATC). The ATC
Updates File consists of one or more records, each consisting of two fields, a text field which iden-
tifies an interface by twelve character label and a numeric value field which identifies the interface
ATC in MW.
Activity IMPC may be terminated by entering the AB interrupt control code.
The impact calculator produces a report which illustrates the incremental MW flow impacts on each
of the monitored elements, along with the initial available transfer capability (ATC) for the element
and a final ATC which is adjusted for the flow impact due to the transaction. For monitored inter-
faces, a value is provided which illustrates the maximum transaction magnitude that can be
supported by the elements ATC.
Run Activity IMPC - GUI
Trans Access > Calculators > Impact on monitored elements
[Impact on Monitored Elements]
Run Line Mode Activity IMPC - CLI
ACTIVITY?
>>IMPC
ENTER OUTPUT DEVICE CODE:
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 12-5
PSS
E 32.0
Calculating Transaction Event Impact on Monitored Elements Program Operation Manual
12-6 Siemens Energy, Inc., Power Technologies International
Figure 12-1. Results of Impact Calculation
12.3.3 Application Notes
Activity IMPC uses the same linearized network model as activity DCLF. Thus, the comments in
Section 7.4.4 apply here as well. Regulating in-service phase shifting transformers hold constant
MW flow.
Additional Information
PSS
E 32.0
Calculating Line Loading Relief Program Operation Manual
12-8 Siemens Energy, Inc., Power Technologies International
function proceeds to investigate the priorities from highest to lowest priority number until the incre-
mental flow target is satisfied or all transaction priority groups are exhausted.
The line loading relief calculator produces reports which illustrate:
Transaction adjustments which result in a specified incremental flow on a selected
monitored element.
Distribution factors (i.e., sensitivity of monitored element MW flow to transaction mag-
nitude) for all monitored elements and transaction events).
12.4.1 Operation of Activity LLRF
The user must enter the name of a Distribution Factor Data File constructed by activity DFAX which
corresponds to the network condition contained in the working case (refer to Section 7.1.6) and to
the desired Linear Network Analysis Data Files (refer to Section 7.1.1). The Distribution Factor Data
File must specify at least one monitored branch or interface. The bus input option (refer to
Section 3.3.3 and activity OPTN) must have the same setting that was in effect when activity DFAX
filled the specified file. Refer to Section 2.4.1 for the file specification conventions used by activity
LLRF.
When the distribution factor file is identified, the monitored element list (from a *.mon file) is tabu-
lated in the window.
The user specifies the association method for adjustment. Four transaction event adjustment
methods are available:
First in last out (FILO)
Decreasing order of distribution factor magnitude (DF-ORDER)
Distribution factor pro rata (DF-PRO RATA)
Pro rata base on the product of distribution factor with transaction schedule
(DF-SCHED-PRO RATA)
Table 12-2. Line Loading Relief Calculator Functions
Line Loading
Relief Function Calculation
Curtail
or
Restore
Specify the target element from the list of monitored elements and define
the incremental flow target element adjustment value in MW. The con-
ventions for positive and negative element flow are defined when
presenting the monitored element list to activity DFAX.
DF Report Activity LLRF produces a report of transfer distribution factors for all
monitored elements due to all transactions events. Out-of-service trans-
action events will have distribution factors of zero.
Distribution
factor
tolerance
If the reset distribution factor tolerance is specified, activity LLRF
requires a new value of distribution factor tolerance. This tolerance is
employed to preclude those transaction events with negligible effect on
the target monitored element from the transaction adjustment functions
Siemens Energy, Inc., Power Technologies International 12-9
PSS
E 32.0
Calculating Line Loading Relief Program Operation Manual
12-10 Siemens Energy, Inc., Power Technologies International
12.4.3 Application Notes
Activity LLRF uses the same linearized network model as is used in activity DCLF. Thus, the
comments in Section 7.4.4 apply here as well. Regulating in-service phase shifting transformers
hold constant MW flow.
Transaction events may be adjusted by the curtailment or restoration functions when their distribu-
tion factor magnitudes exceed the distribution factor tolerance and are of the correct sign with
respect to the sign of the adjustment MW value (e.g., having opposite sign for curtailment and the
same sign for restoration).
When performing curtailment, the adjustment magnitude limit for each transaction event is equal to
the transaction event magnitude less the initial curtailment magnitude. When performing restoration
the adjustment magnitude limit for each transaction event is equal to the initial transaction event
curtailment magnitude. Adjustments resulting from the curtailment and restoration functions update
the transaction event curtailment magnitude.
Additional Information
PSS
E 32.0
Making Allocations Program Operation Manual
12-12 Siemens Energy, Inc., Power Technologies International
Vector Sum Megawatt-ohm
Branch mileage summary by owner
If specifying Vector Absolute MW-mile, Vector Absolute MW-ohm, Vector MW-ohm, or mileage
summary, the report is produced at the specified output destination.
If specifying Generation on MW-mile shift factors or Generation on MW-ohm shift factors the user
must specify a transaction event. The report for that event is produced at the specified output desti-
nation (refer to Section 4.4).
12.5.1 Output Report Format
Transmission allocation reports and related transaction event worksheets are generated to provide
an accounting basis which illustrates the impact on the transmission system due to transaction
events. The accounting basis may be used to allocate embedded transmission costs or controls
area losses among the various transaction events making use of the transmission networks.
All other reports produced by activity ALOC are formatted for import to a spreadsheet program.
Selections from the Graphical User Interface menu bar result in spreadsheet formatted reports.
Reports formatted for import to a spreadsheet program include an initial record of text fields for use
as column headings in a spreadsheet table. The first field of each subsequent record provides a
row label. All other fields are numeric data.
The Branch Mileage Report contains only the branch mileage summary by owner and is displayed
at the Report tab.
A Vector Absolute MW-Mile (VAMM) method is used to produce the transmission embedded cost
allocation. MW-mile methods are techniques for ascribing the use of the electric power transmission
system among the various beneficiaries. These are accounting practices which rely on engineering
analysis to determine the basis. This basic accounting unit is the product of branch MW flow with
branch length.
The VAMM method determines the impact for each individual transaction event by perturbing each
bus generation associated with the event against the associated event load. For each perturbation,
the absolute value of change in branch flow (i.e., change from the initial condition power flow model)
is multiplied by the branch length in miles, and this result is accumulated in the events MW-Mile
vector, one entry for each branch owner of the power flow model (i.e., each facility owner) as illus-
trated in Equation 12.1.
(12.1)
where:
MWM
ij
= MW-Mile impact for the i
th
owner and j
th
transaction event.
NAG
j
= Number of j
th
transaction event associated generators.
NAL
i
= Number of branches owned by the i
th
owner (transmission facility owner).
AP = Incremental MW branch flow due to perturbing MW generation.
L = Branch length in miles.
MWM
ij
=
NAG
j
NAL
i
k l
E
|AP
l
|L
l
E
Siemens Energy, Inc., Power Technologies International 12-13
PSS
E 32.0
Making Allocations Program Operation Manual
12-14 Siemens Energy, Inc., Power Technologies International
Additional Information
PSS
E 32.0
Making Allocations Program Operation Manual
12-16 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 13-1
Chapter 13
Optimal Power Flow
13.1 Overview
The PSS
E OPF formulates and solves the optimization problem within constraints, and automatically
updates any power flow data values affected by the solution. Upon completion of the solution,
results are presented in one or more formatted reports and output files.
Optimal power flow activities are not sensitive to any interrupt control code options.
The following sections provide more detailed information for:
the optimal power flow analytical model
how it relates to the standard power flow
a description for each power flow data model used within the PSS
E OPF
models employed specifically within the OPF
OPF algorithm and the solution process.
Optimal Power Flow PSS
E 32.0
Conventional Power Flow Program Operation Manual
13-2 Siemens Energy, Inc., Power Technologies International
13.2 Conventional Power Flow
The OPF solves an optimization problem with side conditions. To place this problem in context, the
conventional power flow problem is presented first and then contrasted with the optimal power flow
problem.
The conventional power flow problem solves a series of simultaneous nonlinear equations which
ensure that the net complex power injection at every bus is equivalent to the sum of complex power
flows on each connected branch.
(13.1)
where:
N = Total number of buses,
S
Gi
= Net complex power generation at bus i,
S
Li
= Net complex load at bus i,
S
ij
= Complex power flow on branch connecting buses i and j.
Bus power injections and branch power flows are expressed as functions of complex bus voltage.
Through the iterative solution process, a bus voltage vector is determined which satisfies these
equality constraints to within a mismatch tolerance.
One criteria for a desired solution might require that a dependent variable set, such as a group of
bus voltage magnitudes and branch flows, must satisfy maximum and minimum limits. The power
flow model may offer a set of automatic controls for which the values vary independently as func-
tions of local objectives. For example, generator reactive power varies continuously to control the
machines terminal bus or some remote bus voltage magnitude. Other controlling equipment may
include transformer tap ratios, transformer phase shift angles, susceptive bus shunts, dc converter
control angles, etc.
It is unlikely that sufficient controlling equipment exists such that an individual control may be
assigned to each dependent variable. In addition, the control variable range is limited and may be
insufficient to satisfy a local objective. This latter condition is especially apparent when local objec-
tives conflict. It is necessary therefore, for the analyst to manually vary either the control values or
their local objectives to attempt to achieve a good solution. By observing the impact of parametric
variations, the analyst develops an intuition of the power system model. This is likely to be a long
and tedious process however.
S
Gi
- S
Li
=
N
S
ij
j = 1
E
Siemens Energy, Inc., Power Technologies International 13-3
PSS
E 32.0
Optimal Power Flow Program Operation Manual
13-4 Siemens Energy, Inc., Power Technologies International
transformer phase shift angle, etc., may be assigned a fixed value or assigned upper and lower
limits. Certain dependent variables, such as load bus voltage magnitudes and branch flows, are
assigned upper and lower bounds. It is possible however, for the entire constraint set to not be
simultaneously satisfied. This situation results in an infeasible termination.
Unlike the conventional power flow there is no independent local objective associated with each
control. The solution process adjusts each control to find the setting that satisfies all stipulated
constraints, and further minimizes the objective function. The constraints are applied to, and the
objective is written in terms of a variable set. Two variable types exist in the model: control variables
(also referred to as independent or decision variables) and dependent variables (also referred to as
state variables). These are identified through both the conventional power flow model and the auxil-
iary optimal power flow modeling data.
One primary difference between the optimal power flow solution and a standard power flow solution
when applied to a basic power flow case is that the OPF may introduce barrier terms into the objec-
tive function. These barrier terms come from constraints that have hard limits enforced. Bus voltage
constraints for example have, by default, hard limits automatically introduced for every bus in the
system.
13.3.3 Sensitivities
Each variable, both independent and dependent, has a sensitivity associated with it. Sensitivity
values quantify the expected change in the objective in response to a change in the variable. A
negative sensitivity indicates that an increase in the variables value will decrease the objectives
value. The optimal setting for any variable is one which results in a sensitivity of zero. For some
variables, the optimal setting exists outside of the variables limits. In this case, the OPF will drive
the variable to the limit and report the sensitivity value. The relative size of the sensitivity magni-
tudes direct attention to the constraints or fixed controls that have the most influence on the
objective.
Additional Information
PSS
E GUI Users Guide, Section 19.4, Running the Optimal Power Flow Solution
PSS
E working case.
The following sections identify the conventional power flow models and details how each one is
utilized and modeled within the optimal power flow. The categories are presented in the same order
as they would appear in the PSS
E 32.0
Conventional Power Flow Models Program Operation Manual
13-6 Siemens Energy, Inc., Power Technologies International
13.4.4 Generator Data
One or more machines may be associated with a generator bus (type 2) or a swing bus (type 3).
Active power and reactive power generation and reactive power generation limits are initialized from
the conventional power flow data model. Should the lower limit total equal or exceed the upper limit
total at any bus, the bus is implicitly altered to a load bus (type 1). Bus numbers of remotely regu-
lated voltage buses are retained for reporting purposes and optionally for local voltage control of
nonoptimized equipment, although the remote regulation concept is invalid for optimized controls.
The OPF exercises all optimized controls to satisfy all constraints and beyond that to minimize the
objective function. Generator base MVA, source impedance, implicit step-up transformer imped-
ance, and tap ratio data are ignored by PSS
E OPF.
In the conventional power flow, generator control action is discontinuous. Generators regulate a
single bus voltage magnitude. This voltage is considered fixed and the reactive generation varies
until a reactive generation limit is reached, at which point the regulated voltage becomes free to vary
in one direction and the reactive generation is fixed at the limit. If the regulated voltage should return
to the set point, the voltage once again becomes fixed and the reactive generation is free.
Generator bus voltage magnitudes are control variables that are varied by the OPF to optimally
settle on a value that respect limits. The preferred treatment for nonoptimized generators is the
conventional generator model, but this models discontinuity severely impedes the reliability of the
OPF solution. The PSS
E, but as discussed in
Sections 13.2 and 13.3, optimized controls are adjusted to accommodate the entire optimization
problem, not simply a local objective.
The PSS
E power flow solution activities and stored within the working case. It is therefore
best to perform a power flow solution prior to the OPF solution in order to start with a condition that
has been solved for the dc boundary conditions of interest.
13.4.9 Voltage Source Converter Data
VSC devices are modeled as equivalent load injections, obtained directly from the PSS
E power
flow solution as stored in the working case. It is best to start the OPF solution from a power flow
condition that has already been solved for the boundary conditions of interest.
13.4.10 Transformer Impedance Correction Data
Transformer impedance adjustment as a function of tap position is not accommodated in the
PSS
E OPF. Transformer impedance is initialized to the adjusted impedance and held fixed.
13.4.11 Multi-Terminal DC Line Data
Multi-terminal dc systems are modeled as equivalent active and reactive power demand. All in-
service multi-terminal dc systems within the working case are automatically replaced by equivalent
bus loads. The equivalent dc bus injection is calculated by the PSS
E 32.0
Conventional Power Flow Models Program Operation Manual
13-8 Siemens Energy, Inc., Power Technologies International
13.4.12 FACTS Device Data
FACTS devices are modeled as equivalent active and reactive power demand. During the OPF
solution, all in-service FACTS devices are automatically replaced by equivalent bus loads. The
loads are obtained directly from the equivalent bus injection as calculated by the PSS
E power flow
solution and stored in the working case. It is therefore best to start the OPF solution from a power
flow condition that has already been solved for the boundary conditions of interest.
13.4.13 Switched Shunt Data
Bus shunt control variables are identified by both the auxiliary OPF adjustable bus shunt data model
and the switched shunt model in the conventional power flow data. The adjustable bus shunt data
model is presented in Section 13.6.2.
For switched shunts defined within the power flow, the bus number, control mode, initial value and
switching information for the eight blocks are retained by the program.
By default the switched shunt susceptance is adjusted continuously. Non-regulating switched
shunts and var sites in nonoptimized subsystems are fixed at their initial value (BINIT).
The control mode values of switched shunts that are not fixed are treated as follows:
Modes 1 and 2: The desired voltage limits and the remote bus number are discarded
in lieu of explicit bus voltage limits applied to buses via the OPF Bus Voltage Attribute
Data Record.
Mode 3: Reactive generation limits of regulated generators are also restricted by the
specified band.
Mode 4: Handled the same as modes 1 and 2. Becausebecause VSC are handled as
equivalent bus load injections in the OPF solution, no adjustments are made to VSC
limits.
Mode 5: Admittance limits of switched shunts (local or remote) are also restricted by
the specified band.
Siemens Energy, Inc., Power Technologies International 13-9
PSS
E
N
i = 1
(x
i
- x
io
)
2
Optimal Power Flow PSS
E 32.0
Modeling Power Flow Controls Program Operation Manual
13-10 Siemens Energy, Inc., Power Technologies International
13.5.3 Treatment of Transformers and Switched Shunts
For transformers and switched shunts residing in an area or zone selected for optimization, a zero
cost quadratic penalty is automatically applied. This penalty weight value may be altered through
the OPF solution tolerance for the Quadratic Penalty Coefficient.
Transformers and switched shunts not residing within an optimized subsystem, or those where the
setting has been fixed (either in the power flow model or through the Fix setting), will be treated as
nonoptimized. In this situation, these controls are fixed at their current working case values. There
is the possibility however, for bus voltage penalties to also be imposed on the regulated buses,
although this is done independent of whether the transformer or switched shunt is being treated as
a nonoptimized control.
Discrete transformer tap ratio adjustments or switched shunt adjustments are approximated by
initially treating these controls as continuous. If the option to Round Transformer Tap Ratios and/or
Round Switched Shunt Vars is imposed, then after an optimal solution has been achieved with
continuous treatment, the control is fixed to the nearest discrete value and the problem is resolved
from this condition.
13.5.4 Treatment of Local Generator Voltage Controls
Similar penalty treatments exist for generator voltage controls, but vary depending upon whether
the treatment is applied to an optimized or nonoptimized generator. Nonoptimized generators are
those that are not located in an optimized subsystem. If the Treat all Generators as Non-optimized
option is enabled, then all generators in the system are treated as nonoptimized, independent of
whether they are located within a nonoptimized area or zone.
Using the generator and area designations defined in the one-line diagram of Figure 13-1, the far
right-hand column of Table 13-1 indicates which generators would result in being treated as nonop-
timized based upon the setting of the Treat all generators as non-optimized option and the
subsystem of areas selected for optimization.
Figure 13-1. Generator and Area Designations from the savnw.sav Case
206
101 102
211
3018
3011
Area 5 Area 1 Area 2
Siemens Energy, Inc., Power Technologies International 13-11
PSS
E 32.0
Modeling Power Flow Controls Program Operation Manual
13-12 Siemens Energy, Inc., Power Technologies International
The regulated voltage may be that of a generator bus or a remote non generator bus. The regulating
reactive power supply is the sum of the reactive generation of all the units that regulate the bus.
Note the discontinuity at the upper and lower reactive power generation limits. It is this discontinuity
which confounds modeling this relationship in the OPF, and thus approximations for this treatment
must be employed.
Several different penalty techniques are available for approximating the local control objective at
nonoptimized generators:
bus voltage magnitude soft limit penalties (linear or quadratic),
scalar quadratic penalties
constraint (clamp) equation.
Soft Limit Penalty Techniques: Soft limit penalty techniques are applied on a per bus basis
through the bus voltage magnitude constraints defined at corresponding voltage regulated
buses (see Section 13.9.2). The soft limit penalty introduces an objective function compo-
nent that penalizes the excursion of the regulated voltage magnitude from an offset.
There are two soft limit penalty treatments available: linear and quadratic. Both are
discussed in further detail in Soft Limit Treatment. When applied to nonoptimized generator
units, the soft limit penalty treatment supersedes either the scalar quadratic penalty or
clamp treatments discussed in the following text.
Scalar Quadratic Penalty: A second technique for approximating the local control objective
of nonoptimized generators is by means of a scalar quadratic penalty. This quadratic
penalty is all or none; it may not be selectively applied to certain nonoptimized generator
units. Unless the clamp equation is employed (as discussed below), or a penalty limit is
applied to the individual bus voltage constraint, a quadratic penalty is inherently applied to
all nonoptimized generator units. The default penalty weight of 100.0 may be modified prior
to the OPF solution. Unlike the soft limit penalty weight which may be uniquely defined for
individual bus voltage constraints, this value is applied as a scalar to the entire quadratic
penalty equation. Refer to Section 13.5.1 for further details.
Clamp Treatment: The final penalty technique available for approximating the local control
objective for nonoptimized generators is by means of a constraint, or clamp, equation. This
equation limits the total deviation from the voltage and reactive power relationship
presented in Figure 13-2. Consider the equation,
where:
Q = reactive power generation
V = regulated (local or remote) bus voltage magnitude
V
s
= regulated voltage set-point
N = number of nonoptimized generators
t = clamp tolerance,
E
i = 1
N
(Q
max,i
- Q
i
) max(0, (V
s,i
- V
i
)) + (Q
i
- Q
min, i
) max(0, (V
i
- V
s,i
))
s t
(Q
max,i
- Q
min,i
)
Siemens Energy, Inc., Power Technologies International 13-13
PSS
E OPF interior point solution technique described in Section 13.7.2 prevents a solution
when t equals 0.0. The consequence of having a nonzero clamp tolerance is illustrated in
Figure 13-3. Clamp constraint limits are applied in an attempt to reduce the total error in nonopti-
mized generator performance. The strategy employed in the PSS
E 32.0
Modeling Power Flow Controls Program Operation Manual
13-14 Siemens Energy, Inc., Power Technologies International
13.5.5 Reactive Generation Reserve
A reactive generation reserve objective function component may be included in the opf problem
statement. This objective component will influence the magnitude of reactive power generation held
in reserve. All in-service generators that are members of the optimized subsystem contribute to this
objective. The OPF will adjust the reactive power generation of these generators to achieve a
feasible solution and to balance the cost of this objective component against the other selected
objective components. The reactive generation reserve objective takes the form:
where:
The reactive generation reserve will tend to be minimized by applying a positive objective cost coef-
ficient. The reactive generation reserve will tend to be maximized by applying a negative objective
cost coefficient. The objective component may be applied by enabling the Minimize Reactive
Generation Reserve option, and the cost coefficient may be assigned using the input field labeled
Reactive generation reserve cost ($/MVAR).
NGEN = Number of in-service optimized generators.
= Objective cost coefficient in cost units/Mvar.
Q
MAX
= Maximum reactive power generation limit in Mvar.
Q
GEN
= Reactive power generation in Mvar.
E
NGEN
i = 1
(Q
MAX,i
- Q
GEN,i
)
Siemens Energy, Inc., Power Technologies International 13-15
PSS
E OPF
beyond the conventional power flow models introduced in Section 13.4.
13.6.1 Active Power Generation
Active power generation control variables may be introduced by presenting cost as a function of
active power generation. Individual generator units may be associated with certain active power
controls. The amount of dispatch is adjusted to satisfy the constraints and minimize the total gener-
ation cost component of the objective function. Generators in nonoptimized subsystems that are
associated with an active power dispatch control will participate in the dispatch.
One of three cost curves may be employed to model the control: piece-wise linear, piece-wise
quadratic and polynomial.
13.6.2 Adjustable Bus Shunt
A subset of buses may be identified as susceptive bus shunt adjustment candidates for shunt
compensation. When defined, adjustable bus shunt controls are employed to minimize the total
adjustable bus shunt component of the objective function (refer to Minimize Adjustable Bus Shunts).
The candidate buses for shunt compensation are introduced through the adjustable bus shunt data
records described in Section 13.9.3.
This objective function employs a linear penalty of the following form:
and
where:
The cost, C
i
, is assigned to individual adjustable bus shunt controls, in cost units / per unit Mvar.
Multiple shunt device controls may be assigned to the same bus, with each one distinguished by a
different cost for deployment. For example, a relatively low cost may be assigned to a control
representing an existing installation and a high cost to a control representing a potentially new
installation. In this situation the existing installation is ensured of being deployed to its limit before
any portion of the new capacity is applied.
The shunt control is assigned a minimum and maximum var limit and may operate in both an induc-
tive (-B) and capacitive (+B) range. The resulting shunt value is added to the corresponding fixed
shunt in the power flow model. If no corresponding fixed shunt is found, then a new fixed shunt with
B = adjustable bus shunt susceptance (per unit)
B
CAP,MAX
= capacitive limit (per unit)
B
IND,MAX
= inductive limit (per unit)
C = shunt cost / per unit Mvar
NVARS = number of adjustable shunt candidate buses
F(B) =
NVARS
i = 1
|B
i
|C
i E
B
IND, MAXi
s B
i
s B
CAP, MAXi
Optimal Power Flow PSS
E 32.0
OPF Modeling Extensions Program Operation Manual
13-16 Siemens Energy, Inc., Power Technologies International
the same identifiers as the adjustable bus shunt will be added. If an initial offset (no cost, fixed shunt
component) is desired, it may be included in the power flow model as a fixed shunt prior to the OPF
solution.
13.6.3 Load Adjustment
Any number of predefined loads within the power flow case may be identified as adjustable load
candidates. The constant MVA component of these loads is adjusted by a multiplier to minimize the
total load adjustment component of the objective function. The multiplier may vary continuously
between predefined minimum and maximum limits.
The load adjustment objective function is of the following form:
where:
Bus load is shed at constant power factor. The cost, C
i
, is assigned per candidate load adjustment
group, in cost units / per unit MW. The control is limited between minimum and maximum values
specified as a fraction of initial total load.
MVA
LOAD
= MVA bus load (per unit)
MVA
0
= initial MVA bus load (per unit)
MW
0
=
initial active power bus load (per unit)
+
= load adjustment factor
+
MIN
= minimum load adjustment factor
+
MAX
= maximum load adjustment factor
C = load shed cost / per unit MW
NSHED = number of load shed candidate buses
F(+) =
NSHED
E
i = 1
C
i
MW
0
(1 - +
i
)
i
+
MIN
s +
i
s +
MAX
MVA
LOAD
= +
i
MVA
0
i i
i i
Siemens Energy, Inc., Power Technologies International 13-17
PSS
E 32.0
OPF Modeling Extensions Program Operation Manual
13-18 Siemens Energy, Inc., Power Technologies International
Figure 13-4. Reactive Capability, Q
gen
vs. P
gen
The Q
gen
vs. P
gen
limits description is amenable to the conventional power flow problem because
of the simple inequality treatment of reactive power limits, Q
min
s Q
gen
s Q
max
, fixed voltage
schedule, and fixed active power generation. Becausebecause the OPF is able to dispatch active
power generation and voltage schedule, a more elaborate model that describes the machines
capability is appropriate. This is achieved by replacing the generator representation of P
gen
and
Q
gen
injections at the terminal bus, with one of P
gen
and Q
gen
injections at a point removed from
the terminal bus through direct axis synchronous reactance, as illustrated in Figure 13-5.
Figure 13-5. Alternate Generator Model (Injection Behind Synchronous Reactance, X
d
)
P
gen
Q
gen
L
a
g
L
e
a
d
Efd V
terminal
Q
gen
I
s
Q
gen
P
gen
X
d
Siemens Energy, Inc., Power Technologies International 13-19
PSS
E 32.0
OPF Modeling Extensions Program Operation Manual
13-20 Siemens Energy, Inc., Power Technologies International
Figure 13-7. Vector Arithmetic for Deriving Limits
13.6.6 Generator Period Reserve
A common practice in power system operation is to commit and dispatch generation such that suffi-
cient excess capacity exists to accommodate some reserve constraint. This may be compounded
with a time dimension, such that the reserve capacity must be fully available within a stated number
of minutes, and the units that participate in supplying the reserve are limited by their active power
generation ramp capability and emergency maximum capacity. A minimum generation cost
dispatch may be significantly impacted by these generation period reserve constraints.
The PSS
E OPF generation period reserve model provides for a reserve in MW, and a time period
in minutes, to be stated. Participating generators associated with each of these constraints are also
defined. A maximum unit capability in MW and an active generation ramp rate in MW per minute is
identified for each participating generator. The sum of participating unit reserves must exceed the
reserve constraint. The amount of reserve contributed by each of the participating units is the lesser
of the unit capability minus its active power dispatch, or its ramp rate times the period. This is exem-
plified in the following equation.
I
s
= Q
0pf
/ MVA
r
V
E
fd,min
I
s
*X
d
V
E
fd,max
V
I
s
= I
s,max
ACOS(pf
lag
)
I
s
= I
s,max
ACOS(pf
lead
)
E
fd
m = (E
fd
- E
fd,min
) / (I
s,max
- Q
opf
/MVA
r
)
b = Q
opf
/MVA
r
- mE
fd,min
I
s
*X
d
I
s
*X
d
N
E
i = 1
min((P
max,i
- P
gen,i
), T Ramp
i
) > RES
Siemens Energy, Inc., Power Technologies International 13-21
PSS
E 32.0
OPF Modeling Extensions Program Operation Manual
13-22 Siemens Energy, Inc., Power Technologies International
Each new area interchange constraint model implicitly defines an interface consisting of the
following components:
area tie branches, excluding zero impedance lines;
flows associated with dc lines, multi-terminal dc lines, FACTs and VSC devices;
loads, provided that the option to include loads in area interchange calculations has
been enabled (refer to PSS
E 32.0
Solution Process Program Operation Manual
13-24 Siemens Energy, Inc., Power Technologies International
13.7 Solution Process
13.7.1 The Nonlinear Problem
PSS
E OPF solves a nonlinear problem consisting of an objective function and a linear combina-
tion of equality constraints to form a scalar Lagrangian function of the following form.
L (x, ) = f(x) + []
t
[h(x)] (13.2)
and
h(x) = 0
x
MIN
s x s x
MAX
where:
x = power system variables (control and dependent, column vector),
f(x) = objective function (e.g. active power dispatch cost),
h(x) = equality constraints including bus-power mismatch equations (column vector),
= Lagrange multiplier variable (column vector).
The Lagrangian function is constructed in terms of both the power system variables and the
Lagrange multipliers, thereby resulting in a dual variable problem. The equality constrained optimal
solution is a Lagrangian stationary point, and is determined by equating the functions gradient to
zero and solving for x and . This is the Kuhn-Tucker optimality condition
1
, and the resulting set of
simultaneous equations is referred to as the KT formulation. Solving the KT problem produces a set
of optimally defined power system variables (x), along with the objective function sensitivities to
changes in the constraints ().
The OPF formulation is always nonlinear in x because the constraints include the power flow
mismatch equations. The objective function is also likely to be nonlinear in x either through explicitly
selected components, like active power loss, or the implicit introduction of quadratic penalties.
Therefore, an iterative solution technique which will recognize the limits in x is required. A solution
to the nonlinear problem results from solving a series of simpler subproblems, wherein the
inequality constraints are satisfied at every subproblem.
13.7.2 Accommodating Inequality Constraints
Inequality constraints are imposed through implicit objective terms expressed as a function of the
constrained variable. These limits have two types, hard and soft. Hard limits introduce objective
terms that are asymptotic to the variables limits (i.e. barrier terms), while soft limits introduce objec-
tive terms which are defined in the infeasible region and grow in magnitude as the variable value
departs further from its violated limit (i.e. penalty terms).
Limits imposed on the power system control variables, such as transformer tap settings, are consid-
ered extremes in the equipments physical range, and thus are always treated as hard limits. This
treatment is in addition to the global quadratic penalty that may optionally be imposed on power flow
control values as they move away from their initial values. As discussed in Section 13.5, this
1
Kuhn, H.W. and Tucker, A.W., "Nonlinear Programing", Proceedings of the Second Berkeley Symposium on
Mathematical Statistics and Probability (J. Neyman, ed.), Berkeley, University of California Press, 1951.
Siemens Energy, Inc., Power Technologies International 13-25
PSS
i
x
i
-
(x
i,min
+ x
i,max
)
N
E
i = 1
i
(max(0, x
i
- x
MAX,i
) - min(0, x
i
- x
MIN,i
))
Optimal Power Flow PSS
E 32.0
Solution Process Program Operation Manual
13-26 Siemens Energy, Inc., Power Technologies International
Hard Limit Barrier Treatment
The hard inequality constraints are rigorously enforced at each sub-problem by augmenting the
Lagrangian with objective-like equations in terms of x, x
MAX
, and x
MIN
. These equations, called
barrier functions (B(x)), are continuous and asymptotic to the limits, x
MAX
and x
MIN
, as depicted in
Figure 13-8.
Figure 13-8. Logarithmic Barrier Function
As shown, the function is not defined for values of x outside of the specified range; thus barriers are
formed in which all of x is corralled within a feasible region. The optimization problem itself is infea-
sible if any equality constraint (e.g. bus-power mismatch) requires that x violate this feasible region.
PSS
)
E
N
i = 1
{log(x
i
- x
MIN,i
) + log(x
MAX,i
- x
i
)}
Siemens Energy, Inc., Power Technologies International 13-27
PSS
E 32.0
Solution Process Program Operation Manual
13-28 Siemens Energy, Inc., Power Technologies International
Figure 13-9. Objective Function with Barrier Term
CHNL# 1: 10.0*(1.0 - [X])
14.000 -1.000
CHNL# 1: -LOG(1.0-[X]) * 2.0
14.000 -1.000
CHNL# 1: 10.0*(1.0 - [X]) - LOG(1.0-[X]) * 2.0
14.000 -1.000
BARRIER FUNCTION DESCRIPTION
XMAX BARRIER TERMS ONLY, XMAX = 1.0
THE COMBINED OBJECTIVE FUNCTION
F
R
I
J
A
N
1
0
,
1
9
9
2
1
6
:
1
9
X
POWER
TECHNOLOGIES,
INC.
R
0
.
0
0
.
2
0
0
0
0
0
.
4
0
0
0
0
0
.
6
0
0
0
0
0
.
8
0
0
0
0
1
.
0
0
0
0
FILE: barrier1
E
X
P
L
I
C
I
T
O
B
J
E
C
T
I
V
E
C
O
M
B
I
N
E
D
O
B
J
E
C
T
I
V
E
B
A
R
R
I
E
R
T
E
R
M
Siemens Energy, Inc., Power Technologies International 13-29
PSS
V
x
L(x,
)
V
x
V
L(x,
)
V
L(x,
)
V
x
L(x,
)
V
L(x,
)
Ax
A
=
Optimal Power Flow PSS
E 32.0
Solution Process Program Operation Manual
13-30 Siemens Energy, Inc., Power Technologies International
Figure 13-10. Effects of Reducing the Barrier Coefficient
CHNL# 1: 10.0*(1.0 - [X])
14.000 -1.000
CHNL# 1: -LOG(1.0-[X]) * 2.0
14.000 -1.000
CHNL# 1: 10.0*(1.0 - [X]) - LOG(1.0-[X]) * 2.0
14.000 -1.000
CHNL# 1: -LOG(1.0-[X])
14.000 -1.000
CHNL# 1: 10.0*(1.0 - [X]) - LOG(1.0-[X])
14.000 -1.000
BARRIER FUNCTION DESCRIPTION
XMAX BARRIER TERMS ONLY, XMAX = 1.0
DIMINISHING BARRIER COEFFICIENT
F
R
I
J
A
N
1
0
,
1
9
9
2
1
6
:
2
2
X
POWER
TECHNOLOGIES,
INC.
R
0
.
0
0
.
2
0
0
0
0
0
.
4
0
0
0
0
0
.
6
0
0
0
0
0
.
8
0
0
0
0
1
.
0
0
0
0
FILE: barrier1
E
X
P
L
I
C
I
T
O
B
J
E
C
T
I
V
E
B
A
R
R
I
E
R
C
O
E
F
F
I
C
I
E
N
T
=
2
.
0
B
A
R
R
I
E
R
C
O
E
F
F
I
C
I
E
N
T
=
1
.
0
Siemens Energy, Inc., Power Technologies International 13-31
PSS
E 32.0
Solution Process Program Operation Manual
13-32 Siemens Energy, Inc., Power Technologies International
Iterative Solution Strategy
The solution to the equation formulated in Equation 13.5 provides corrections to the dual variables,
x and , as driven by the right-hand side (RHS) of the system of equations. The solution algorithm
is iterative. It constructs a KT problem formulation about some estimated x and , calculates correc-
tions and updates the variables.The KT problem is formulated using initial estimate of x and , and
iteratively solved to produce corrections in x and .
x = x
old
+ oAx (13.6)
=
old
+ oAx (13.7)
The computed correction, or step (Ax), when added to x, determines the new minimum of the
quadratic equation. From this point a new quadratic equation is developed and a new step is
computed. As x approaches the nonlinear optimum, the minimum of the quadratic equation
converges to the minimum of the nonlinear combined objective. When the quadratic solution esti-
mate is developed for an x that is far from the optimum, the computed step may force some
elements of x to violate their limits. Becausebecause the combined objective is not defined for infea-
sible values of x, it becomes necessary to reduce, or decelerate, the correction to x and take a
smaller Ax step.
Within the OPF iteration log, the step is reported in per unit. A step of 1.0 implies that 100% of the
correction can be added to x' without violating any limits. Otherwise, the reported step is less than
1.0 and the new value indicates by how much the most limiting element of x reduces the correction.
Example
In Figure 13-11, the combined nonlinear objective function for one particular barrier coefficient (in
this case 2.0) is shown by the solid, unlabeled line. Each of the other five lines are different
quadratic approximations to the objective function curve. The values x displayed in the table
provided within the graph indicate the value at which the tangent to the objective function and the
tangent to the quadratic approximation is the same. The x
OPT
values reflect the optimal minimum
of x and in some situations the value of x may need to be corrected so that it achieves a feasible
value as close to x
OPT
as possible. For this particular example, all values greater than 1.0 are
infeasible.
The quadratic curves in Figure 13-11 exhibit a number of situations that may be encountered by the
program during the solution process. The following scenarios illustrate the necessary corrections in
x and the resulting step size.
Scenario A
For the quadratic approximation exhibited by curve A, the value at which the tangent to
the objective function and the tangent to curve A is identical, occurs at x' =.5. The optimal
value of x for this approximation occurs at x
OPT
= 2.0. The optimal correction is therefore
(2.0 - 0.5), resulting in a Ax of +1.5. Because an x
OPT
value larger than 1.0 falls in the
infeasible region, the correction must be truncated to Ax< +.5 to ensure a feasible result.
This results in a reported step of 0.5/1.5, or 0.33333. All of Ax is scaled by the most
limiting element.
Scenario B
For curve B, the condition where the tangents are identical occurs at x=.6 with an optimal
value of x occurring at x
OPT
= 1.0. In this situation, the optimal value of x lies right on the
border of the feasible region and a full correction of Ax = 1.0 - 0.6 = 0.4 can be made.
Because 100% of the step can be made, a value of 1.0 is reported for the step.
Siemens Energy, Inc., Power Technologies International 13-33
PSS
E OPF, the
barrier coefficient is reduced by decreasing its exponent, , at every iteration which results
in a favorable step larger than 0.5. This continues until the final value of the barrier coeffi-
cient is reached, as defined by the power flow Convergence Tolerance value. The expo-
nential decay of the barrier coefficient is illustrated in Figure 13-12.
Scenario C
Likewise to Scenario B, except that the optimal x is at x
OPT
= 0.85. This again is present
in the feasible region resulting in a full optimal correction of 0.15 and a recorded step of
1.0 (100%).
Scenario D
For this particular approximation the values at for the condition x' and the optimal
minimum x
OPT
both occur at 0.8. In this situation, there is no correction required and a
step size of 1.0 is recorded.
Scenario E
This situation is similar to Scenario C except that the corrected step must be taken back-
wards, thereby resulting in a Ax of -0.15.
Optimal Power Flow PSS
E 32.0
Solution Process Program Operation Manual
13-34 Siemens Energy, Inc., Power Technologies International
Figure 13-12. Diminishing the Barrier Coefficient
CHNL# 1: 10.0*(1.0 - [X])
14.000 -1.000
CHNL# 1: 10.0*(1.0 - [X]) - LOG(1.0-[X])
14.000 -1.000
CHNL# 1: 10.0*(1.0 - [X]) - LOG(1.0-[X]) / 10.
14.000 -1.000
CHNL# 1: 10.0*(1.0 - [X]) - LOG(1.0-[X]) / 100.
14.000 -1.000
BARRIER FUNCTION DESCRIPTION
XMAX BARRIER TERMS ONLY, XMAX = 1.0
DIMINISHING BARRIER COEFFICIENT
EXPONENTIAL DECAY
T
U
E
J
A
N
2
1
,
1
9
9
2
1
4
:
2
6
X
0
.
0
0
.
2
0
0
0
0
0
.
4
0
0
0
0
0
.
6
0
0
0
0
0
.
8
0
0
0
0
1
.
0
0
0
0
FILE: barrier1
M
U
=
0
M
U
=
-
1
POWER
TECHNOLOGIES,
INC.
R
Siemens Energy, Inc., Power Technologies International 13-35
PSS
E 32.0
Solution Process Program Operation Manual
13-36 Siemens Energy, Inc., Power Technologies International
Problem ms Infeasible: If the solution is progressing poorly, then the iterative process will be
terminated with the following error message:
Error: Problem ms infeasible.
Identifying an infeasible problem is often heuristic and takes some experience before
becoming proficient at recognizing which actions need to be taken. There are essentially
two places to look at for information: the iteration log and the OPF Report File.
The formatted OPF output report illustrates the objective sensitivities of the constrained
variables. By comparing the relative magnitudes of these sensitivities, the most penalizing
constraints can be identified. Sensitivities are useful even for infeasible terminations in that
they help identify the most effective places where additional control variables may be
needed and/or limits may need to be relaxed.
If, upon examination of the OPF report, nothing appears to be inherently wrong with the
problem statement, the iteration log may provide additional insight into why the solution
may have terminated as infeasible.
An iterate of the solution process is considered to be good when the following criteria is
met:
- The difference between the values of the nonlinear objective function (NL Objec-
tive) in the prior and present iterations is greater than, or equal to, zero. A value
less than zero indicates that the objective function was not significantly reduced in
the prior iteration.
- The ratio of largest mismatch between the present and prior iteration is less than
0.95. A value larger than, or equal to, 0.95 indicates that the mismatch was not sig-
nificantly reduced in the prior iteration.
When one, or both, or the above criteria are not met, the iteration is considered bad and
the iteration number displayed in the solution log is marked with an x. Under certain condi-
tions, the solution process will terminate as infeasible:
- If the value of the barrier is fairly large (greater than 0.011) and the number of suc-
cessive bad iterations equals the Bad iteration coarse limit as specified (refer to
PSS
E
working case, including optimal power flow data and solution settings.
Optimal Power Flow Raw Data File
An ASCII text file containing the optimal power flow control and constraint data records.
Optimal Power Flow Options File, PSSOPF.OPT
A binary file containing the optimal power solution parameter settings. This file may be
used to override default options established at the time the program is initiated.
Optimal Power Flow Spreadsheet View and Data Tables
A set of interactive spreadsheets and tables for viewing and editing optimal power flow
data.
The following sections discuss, in detail, how each of the above files and functions are utilized by
the optimal power flow in the preservation, modification and restoration of optimal power flow data.
13.8.1 PSS
E Saved Case
All data pertaining to the optimal power flow problem statement, including controls, constraints,
objectives and solution parameters are preserved in the PSS
E Saved Case, it
becomes almost unnecessary to refer to any other files.
Existing saved cases may be brought into the working case at any time. When a PSS
E Saved
Case is brought into PSS
E 32.0
Data Input and Storage Program Operation Manual
13-38 Siemens Energy, Inc., Power Technologies International
13.8.2 Optimal Power Flow Raw Data File
Activity ROPF
The OPF Raw Data File populates the working case with new or revised optimal power flow data
and stores only optimal power flow data for use in future sessions. It specifically contains data
records for the controls and constraints of an OPF problem statement. It does not contain any infor-
mation related to stated objectives, tolerances or other solution parameters.
The file itself is in ASCII format and contains a series of data records group together by OPF data
category. The data categories must be entered in a particular order, as defined by Figure 13-13. A
single data record containing only a zero indicates that all entries for a particular data category have
been entered. If no data records are to be entered for a particular category, then only a single zero
needs to be placed in the data file. If a record with a single q is encountered during processing, then
the file is closed and the program does not attempt to read any further data records.
Additional Information
PSS
E GUI Users Guide, Section 19.1, Reading Optimal Power Flow Data
PSS
E 32.0
Data Input and Storage Program Operation Manual
13-40 Siemens Energy, Inc., Power Technologies International
13.8.3 Optimal Power Flow Options File: PSSOPF.OPT
The Optimal Power Flow Options File provides a means for saving and restoring optimal power flow
solution parameter settings between program sessions. When PSS
E Saved Case file, the values of the option settings stored within it may override
all previous settings.
In addition to the options described in Section 3.3.3, there are a number of option settings specific
to the optimal power flow program module. Details of each option can be found in Section 13.10.
The OPF Parameters specified may be saved to the PSSOPF.OPT options file. The resulting
PSSOPF.OPT file is located in the current working directory. The only information that is not
currently stored is that of a subsystem.
Each time PSS
E is initiated, it will look for the existence of the PSSOPF.OPT file using a particular
directory search sequence, as outlined below.
1. The current working directory. If the file is found, the settings within the file will automatically
be applied and further searches in the alternate locations defined in steps 2 and 3 will not
be pursued.
2. The users home directory. If the file is located here, the settings within the file will automat-
ically be applied and further searches in the alternate location defined in step 3 will not be
pursued.
3. The program default directory. If the file is located in the PSS
E
working case. Any optimal power flow data that may have previously existed within the
working case is erased prior to the reading of the rest of the data records contained within
the OPF Raw Data File.
1:
All data within the OPF Raw Data File is to supersede values that currently exist in the
working case. Any data records introduced through the OPF Raw Data File which do not
correspond to an existing record within the working case, are automatically appended to
the data records already within the current working case. Data records which do corre-
spond to an entry within the working case are simply updated to reflect the new values.
Optimal Power Flow PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-42 Siemens Energy, Inc., Power Technologies International
13.9.2 Bus Voltage Constraint Data
OPF Bus Voltage Constraint records define lower and upper voltage limits at each bus existing
within the PSS
E power flow data model. Constraints may only be applied to existing buses; no
new buses may be added through the Bus Voltage Constraint record.
By default, all buses within the working case automatically have OPF Bus Voltage Constraint
records defined. The OPF Bus Voltage records of out of service (type 4) buses can be modified but
the bus and all bus associated models (voltage constraints, bus shunts, loads, etc.) will not be
utilized by the optimal power flow solution process.
Bus Voltage Attribute Data Record
The format for each OPF Bus Voltage Attribute record is:
Bus, Vn
max
, Vn
min
, Ve
max
, Ve
min
, L
typ
, SL
pen
When entered in the OPF Raw Data File each field must be separated by either a space or a
comma. Any blank fields must be delineated by commas. A bus value of zero (0) indicates that no
further bus voltage constraint records are to be processed.
Each bus voltage constraint record is uniquely identified by a bus identifier. The values for each
record is defined as follows:
Bus number, Bus
A number between 1 and 999997. The specified bus number must correspond to a bus
already defined within the power flow working case.
Normal maximum voltage, Vn
max
[9999.0]
The maximum bus voltage magnitude value, entered in pu.
Normal minimum voltage, V
nmin
[-9999.0]
The minimum bus voltage magnitude value, entered in pu.
Emergency maximum voltage, Ve
max
[9999.0]
The maximum emergency bus voltage magnitude value, entered in pu.
To enforce recognition of the minimum and maximum emergency voltage limits during
the OPF solution, select the Impose emergency bus voltage limits solution option. Oth-
erwise the normal voltage limits, as entered above, will be utilized. Refer to Impose
Emergency Bus Voltage Limits for more information.
Emergency minimum voltage, Ve
min
[-9999.0]
The minimum emergency voltage magnitude value, entered in per unit.
Limit type, L
typ
[Hard limit (1)]
One of four limit types may be enforced during the OPF solution:
Reporting only (0)
Only report on violations of the bus voltage limits, taking no action if the volt-
age falls outside of limits.
Hard limit (1)
Siemens Energy, Inc., Power Technologies International 13-43
PSS
E OPF but do impact bus shunts within the power flow data model
after an OPF solution. If a corresponding bus and bus shunt identifier is found, then the BINIT value
will be updated with the new OPF solution value; otherwise a new bus shunt will be added to the
power flow network data. The switched shunt data records defined within the PSS
E power flow
data model are not affected by the OPF Adjustable Bus Shunt data.
The maximum and minimum var limits specified in the Adjustable Bus Shunt records are used in
conjunction with the Minimize Adjustable Bus Shunts objective function. Details of the adjustable
bus shunt model can be found in Section 13.6.2.
An individual bus may have one or more adjustable bus shunts defined, each differentiated by a
unique bus shunt identifier.
Adjustable Bus Shunt Data Record
The format for each Adjustable Bus Shunt record is:
Bus, ID, B
init
, B
max
, B
min
, B
cost
, C
typ
, Stat, C
tbl
When entering records in the OPF Raw Data File, each field must be separated by either a space
or a comma and any fields left blank must be delineated by commas. A bus value of zero indicates
that no further Adjustable Bus Shunt records are to be processed.
The bus number and shunt identifier uniquely identifies each Adjustable Bus Shunt record. The
values for each record are described as follows:
Bus number, Bus
A number between 1 and 999997. The specified bus number must correspond to an
existing bus within the power flow working case.
Optimal Power Flow PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-44 Siemens Energy, Inc., Power Technologies International
Bus shunt identifier, ID
A one or two character identifier that uniquely identifies the bus shunt at the bus. If this
field is left blank, the bus shunt identifier will default to a value of 1.
The bus number and bus shunt identifier may optionally correspond to a fixed shunt
record within the power flow network. If so, then the corresponding fixed shunt data
record will be updated after an OPF solution.
Bus shunt susceptance, B
init
[0.0]
The initial additional shunt value, entered in Mvar at nominal voltage.
Maximum bus shunt susceptance, B
max
[0.0]
The maximum bus shunt limit, entered in Mvar.
To define an initial fixed shunt component, deployed at no cost, enter the desired value
into the main power flow model as a fixed bus shunt with the same bus number and
shunt identifier.
Minimum bus shunt susceptance, B
min
[0.0]
The minimum bus shunt limit, entered in Mvar.
Negative or positive shunt values may be entered for the maximum and minimum bus
shunt susceptance to indicate inductors or capacitors respectively.
Cost scale coefficient, B
cost
[1.0]
The cost coefficient, entered in cost units per Mvar. This coefficient assigns a cost
value to each Mvar employed during the solution process.
For example, one application for the cost scale coefficient is to assign a relatively low
cost to an Adjustable Bus Shunt record representing an existing var installation, and a
high cost to an Adjustable Bus Shunt record representing a potentially new installation.
This higher cost may take into consideration the additional costs associated with the
purchase of new equipment and the labor required for installation. This setup ensures
that vars from the existing installation will likely be employed during solution before any
new vars are applied.
Siemens Energy, Inc., Power Technologies International 13-45
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-46 Siemens Energy, Inc., Power Technologies International
Bus number, Bus
A number between 1 and 999997. The specified number must correspond to a bus
already defined within the power flow working case.
Bus load identifier, LoadID
A one or two character load identifier that uniquely identifies the load at the bus. If left
blank, a default bus load identifier of 1 is assumed.
Adjustable bus load table, Load
tbl
[0]
The adjustable bus load table reference number, as presented in Section 13.9.5.
An adjustable bus load table number of zero indicates that the corresponding bus load
is not being utilized within any OPF Adjustable Bus Load models.
Multiple OPF bus load records may reference the same adjustable bus load table num-
ber.
13.9.5 Adjustable Bus Load Table Data
Adjustable Bus Load Table records define load scaling limits for use in load adjustment studies (load
shedding, power transfer). They are referenced by the OPF Bus Load records defined in
Section 13.9.4 and are used in conjunction with the Minimize Adjustable Bus Loads objective.
Details of the load adjustment model are covered in Section 13.6.3.
An Adjustable Bus Load Table must be defined before it can be referenced by an OPF Bus Load
record. Not all Adjustable Bus Load Tables however have to be referenced by an adjustable bus
load record. Those tables which are defined but not referenced are ignored during the OPF solution
process. There may be up to 1000 Adjustable Bus Load Table records defined within the working
case.
Adjustable Bus Load Table Data Record
The format of each Adjustable Bus Load Table record is:
Tbl, LM, LM
max
, LM
min
, LR, LR
max
, LR
min
, LD
cost
, C
typ
, Stat, C
tbl
When entering data in the OPF Raw Data File each field must be separated by either a space or a
comma. Any fields left blank must be delineated with commas. A load table value of zero indicates
that no further adjustable bus load table records are to be processed.
The adjustable bus load table number uniquely identifies each adjustable bus load table record. The
values for the record are defined as follows:
Adjustable bus load table number, Tbl
An integer number. A value less than four digits in length is most suitable for reporting
purposes.
Load multiplier, LM [1.0]
The initial load adjustment variable, as indicated by +
i
in the load adjustment model of
Section 13.6.3
Maximum load multiplier, LM
max
[1.0]
Siemens Energy, Inc., Power Technologies International 13-47
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-48 Siemens Energy, Inc., Power Technologies International
Status, Stat [In-service (1)]
In-service (1)
Out-of-service (0)
The status switch determines whether the specified Adjustable Bus Load Table should
be considered active or not. Only in-service Adjustable Bus Load Tables and their
associated OPF Bus Loads will be recognized as adjustable bus load candidates.
Cost table cross-reference number, C
tbl
This value is not presently utilized by the program.
13.9.6 Generator Dispatch Data
Generator Dispatch Data records reference Active Power Dispatch Tables (Section 13.9.7) which,
in turn, reference Cost Curves (Sections 13.9.11 to 13.9.13). These relationships, in conjunction
with the Minimize Fuel Cost objective, introduce active power controls for generator dispatch
studies.
All or a portion of the generating units capacity may be made available for dispatch. The active
power dispatch model, including the minimum and maximum active power limits, is defined within
the active power dispatch table record, described in Section 13.9.7.
By default, all machines within the working case that do not already have generator dispatch data
defined, are initialized with default data. When a new generator is added to the power flow network,
a corresponding OPF Generator Dispatch record is automatically created with default values.
Generator Dispatch Data Record
The format for each OPF Generator Dispatch data record is:
Bus, GenID, Disp, DspTbl
When entering data in the OPF Raw Data File each field must be separated by either a space or a
comma. A bus value of zero indicates that no further generator dispatch records are being entered.
Any blank fields must be delineated by commas.
The bus number and machine identifier uniquely identifies each Generator Dispatch record. The
values for each Generator Dispatch data record are described as follows:
Bus number, Bus
A number between 1 and 999997. The specified bus number must correspond to a bus
already defined within the power flow working case.
Machine identifier, GenID
A one or two character identifier that uniquely identifies the machine at the bus. If left
blank, a default machine identifier of 1 is assumed.
Dispatch fraction, Disp [1.0]
The fractional value of the machines total active power output available for participa-
tion in the active power dispatch control.
A value of 1.0 indicates that 100% of the current active power output at the machine
will be employed in the associated active power control.The sum of the dispatch frac-
Siemens Energy, Inc., Power Technologies International 13-49
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-50 Siemens Energy, Inc., Power Technologies International
The lower limit on the total amount of active power available for dispatch, specified in
MW.
Fuel Cost Scale Coefficient, Fuel
cost
[1.0]
A value chosen such that when the product between this value and the associated cost
curve coordinate value produces a result that has cost units of (cost units)/hour.
As an example, if the cost curve table coordinate value has units of MBTU/hour, then
the fuel cost scale coefficient should be entered with units of (cost units)/MBTU.
Cost Curve Type, C
typ
[Polynomial and exponential (1)]
Polynomial and exponential curve (1)
Piece-wise linear curve (2)
Piece-wise quadratic curve (3)
One of three cost curve models may be specified to represent the fuel dispatch curves
of the generator units.
Status, Status [In (1)]
In-service (1)
Out-of-service (0)
The status switch indicates whether the active power dispatch record is an active con-
trol within the OPF problem statement or not. Only in-service active power dispatch
tables and their associated generators will be recognized as active power dispatch can-
didates.
Cost Curve Table Number, C
tbl
[0]
The table number of the cost curve to employ.
Multiple active power dispatch table records may reference the same cost curve. A cost
curve table number of zero indicates that the active power dispatch record, along with
its participating generators will not be utilized within the OPF solution.
13.9.8 Generation Reserve Data
Generation Reserve records define a generating units MW output capability and ramp rate. These
records are used in conjunction with the Period Reserve Constraint records (Section 13.9.14) to
introduce MW reserve constraints into the optimal power flow problem.
Generation Reserve records may be utilized by one or more generation Period Reserve Constraint
records. The period reserve constraint model, as described in Section 13.6.6, provides a means of
imposing a specified MW reserve within a certain time limit (i.e., 200 MW in 10 minutes) by the
participating generator reserve units.
Generation Reserve Data Record
The format for each Generation Reserve record is:
Bus, GenID, Ramp, RTMW
max
Siemens Energy, Inc., Power Technologies International 13-51
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-52 Siemens Energy, Inc., Power Technologies International
The one or two character machine identifier of a valid machine within the working case.
If this field is left blank, a default machine identifier of 1 will be assumed.
Synchronous Reactance, Xd [1.0]
The direct axis synchronous reactance of the machine, entered in pu on machine base.
Stator Current Limit, I
s,max
[1.0]
The generator stator current limit, entered in pu on machine base.
Lagging Power Factor, PF
lag
[1.0]
Real value generator rated lagging power factor.
Leading Power Factor, PF
lead
[1.0]
Real value generator rated leading power factor.
Maximum Reactive Absorption, Q
limit
[1.0]
The maximum reactive absorption limit at zero power factor, entered in pu on machine
base.
Reactive Capability Limit Status, Status [Enabled with fixed E
fd
(4)]
Out-of-service (0)
The program will employ reactive generation limits directly from the power
flow data.
Enabled (1)
The generator is fully enabled with no reactive generation limits.
Enabled with +AE
fd
inhibited (2)
The generator is in service and any increase in the field voltage is inhibited.
Enabled with -AE
fd
inhibited (3)
The generator is in service and any decrease in the field voltage is inhibited.
Enabled with E
fd
fixed (4)
The generator is in service with an invariant field voltage.
The limit status determines how the specified reactive capability record should be
employed in the optimal power flow problem.
13.9.10 Adjustable Branch Reactance Data
Adjustable Branch Reactance records define the reactive compensation limits and associated
costs of adding series var compensation. The data records are used in conjunction with the Mini-
mize Adjustable Branch Reactances objective to identify candidate branches for use in series var
compensation studies. A full description of the adjustable branch reactance model is presented in
Section 13.6.4.
Adjustable Branch Reactance Data Record
The format for each Adjustable Branch Reactance record is:
IBus, JBus, CktID, Xmlt, Xmlt
max
, Xmlt
min
, X
cost
, C
typ
, Status, C
tbl
Siemens Energy, Inc., Power Technologies International 13-53
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-54 Siemens Energy, Inc., Power Technologies International
Out-of-service (0)
The status determines whether the specified Adjustable Branch Reactance record
should be considered active or not. Only in-service Adjustable Branch Reactance
records are recognized as candidates for series var adjustment.
Cost curve table number, Ctbl
This value is not presently utilized by the program.
13.9.11 Piece-wise Linear Cost Data
The Cost Curve data record provides essential information on the fuel cost characteristics of each
participating generator unit. It is used specifically in conjunction with the Minimize Fuel Cost objec-
tive and the Active Power Dispatch tables (Section 13.9.7) for generator dispatch analysis.
The Piece-wise Linear cost model defines a linear relation between a cost, in cost units (i.e., dollars,
pounds, etc.), and a particular control variable value. For example, an active power dispatch model
may reference a piece-wise linear cost curve in order to obtain the relative fuel cost for dispatching
a participating generator unit at a certain active power dispatch level.
The Cost Curve data record provides essential information on the fuel cost characteristics of each
participating generator unit. It is used specifically in conjunction with the Minimize Fuel Cost objec-
tive and the Active Power Dispatch tables (Section 13.9.7) for generator dispatch analysis.
The Piece-wise Linear cost model defines a linear relation between a cost, in cost units (i.e., dollars,
pounds, etc.), and a particular control variable value. For example, an active power dispatch model
may reference a piece-wise linear cost curve in order to obtain the relative fuel cost for dispatching
a participating generator unit at a certain active power dispatch level.
Piece-wise Linear Cost Table Data Record
The format for each Piece-wise Linear Cost Table data record is a multi-line record as follows:
LTbl, Label, N
pairs
x
1
, y
1
...
x
N
, y
N
When entering data records in the OPF Raw Data File, each field must be separated by either a
space or a comma, with blank fields being delineated by commas.
The total number of pairs entered must equal the value specified for N
pairs
.
An Ltbl number of zero indicates that no further piece-wise linear cost table records are to be
processed.
Each Piece-wise Linear Cost Curve Table record is uniquely identified by a linear cost table number.
The values for each record are defined as follows:
Piece-wise linear cost table number, LTbl
An integer number. A number less than four digits in length is most suitable for report-
ing purposes.
Siemens Energy, Inc., Power Technologies International 13-55
PSS
E Auto-
mation commands.
Coordinate Pairs
The individual coordinate pairs. Each pair (x
1
, y
1
through x
N
, y
N
) defines one segment
of the piece-wise linear cost curve.
x
1
x
N
The control variable value. In the typical situation where the cost curve is
representing fuel cost characteristics, this value would define the active
power generation, in MW.
y
1
y
N
The total cost or energy consumption. For the fuel cost model, this value
would typically be entered in cost units / hour.
Piece-wise Linear Cost Table
The Piece-wise Linear Cost Table displays all Piece-wise Linear Cost Tables in the working case.
The subsystem filter has no effect on the list displayed. If there are no Piece-wise Linear Cost
Tables in the working case, the Tables list will be blank.
13.9.12 Piece-wise Quadratic Cost Data
The Cost Curve data record provides essential information on the fuel cost characteristics of each
participating generator unit. It is used specifically in conjunction with the Minimize Fuel Cost objec-
tive and the Active Power Dispatch tables (Section 13.9.7).
The Piece-wise Quadratic Cost Curve model presents the cost, in cost units (i.e., dollars, pounds,
etc.), as a quadratic function of a control variable value. For example, an active power dispatch
model may reference a piece-wise quadratic cost curve to obtain the relative fuel costs for
dispatching a participating generator unit at a certain active power dispatch level.
The Cost Curve data record provides essential information on the fuel cost characteristics of each
participating generator unit. It is used specifically in conjunction with the Minimize Fuel Cost objec-
tive and the Active Power Dispatch tables (Section 13.9.7).
The Piece-wise Quadratic Cost Curve model presents the cost, in cost units (i.e., dollars, pounds,
etc.), as a quadratic function of a control variable value. For example, an active power dispatch
model may reference a piece-wise quadratic cost curve to obtain the relative fuel costs for
dispatching a participating generator unit at a certain active power dispatch level.
Optimal Power Flow PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-56 Siemens Energy, Inc., Power Technologies International
Piece-wise Quadratic Cost Data Record
The format for each Piece-wise Quadratic Cost Table data record is a multi-line record as follows:
QTbl, Label, Cost, N
pairs
x
1
, y
1
...
x
N
, y
N
When entering data records in the OPF Raw Data File, each field must be separated by either a
space or a comma, with any blank fields being delineated by commas.
The total number of pairs entered must equal the value specified for N
pairs
.
A Qtbl number of zero indicates that no further Piece-wise Quadratic Cost Table records are to be
entered.
Each Piece-wise Quadratic Cost Curve Table is uniquely identified by a quadratic cost table
number. The data values for each record are defined as follows:
Piece-wise quadratic cost table number, QTbl
An integer number. A number less than four digits in length is recommended for report-
ing purposes.
The same cost table number may be used for multiple cost curve table types provided
that each table of the same number represents a different cost curve type (i.e., linear
or polynomial).
Cost table label, Label [""]
A descriptive label of no more than 12 characters used to describe the piece-wise qua-
dratic cost table. This label is used for reporting purposes only.
Integration constant, Cost [0.0]
The cost or energy integration constant used to calculate the total fuel cost.
When this value is used in conjunction with the active power dispatch table, it should
be defined in units which, when its product is taken with the fuel cost scale coefficient
defined in the active power dispatch table record, the resultant units are cost units /
hour. For example, if the fuel cost scale coefficient in the active power dispatch table
has units of $/MBTU, then the integration constant should be specified in units of
MBTU/hour.
Number of cost pairs, N
pairs
[0]
The total number of x
i
, y
i
coordinate pairs being entered for this curve. This value is
only used when entering raw data records through either the OPF Raw Data File or
when using PSS
E Automation commands.
Siemens Energy, Inc., Power Technologies International 13-57
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-58 Siemens Energy, Inc., Power Technologies International
Polynomial and Exponential Cost Curve Data Record
The format for each Polynomial and Exponential Cost Curve Table record is:
Ptbl, Label, Cost, Cost
lin
, Cost
quad
, Cost
exp
, Expn
When entering data records into the OPF Raw Data File, each field must be separated by either a
space or a comma with blank fields delineated by commas. A Ptbl number of zero indicates that no
further polynomial and exponential cost table records are being entered.
Each Polynomial and Exponential Cost Curve Table record is uniquely identified by a polynomial
and exponential cost table number. The values for each record are defined as follows:
Polynomial and Exponential cost table number, Ptbl
A numerical identifier. A number less than four digits in length is recommended for
reporting purposes.
The same table number may be used for multiple cost curve tables, provided that each
table represents a different cost curve type (i.e., linear or quadratic).
Cost table label, Label [""]
A string containing a maximum of 12 characters which may be used as a descriptive
label for the polynomial and exponential cost table. This value is used for reporting pur-
poses only.
Integration constant, Cost [0.0]
The cost or energy integration constant used to calculate the total fuel cost.
Linear coefficient, Cost
lin
[0.0]
The linear cost coefficient as indicated by A in the equation given in Figure 13-14.
Quadratic coefficient, Cost
quad
[0.0]
The quadratic cost coefficient as indicated by B in the equation given in Figure 13-14.
Exponential coefficient, Cost
exp
[0.0]
The exponential cost coefficient as indicated by C in the equation given in Figure 13-
14.
Exponent scale factor, Expn [0.0]
The scale factor value which may be applied to the exponent of the exponential term
as indicated by D in the equation given in Figure 13-14.
The values for the integration constant and each of the coefficients should be specified in units that
will allow them to be multiplied by a cost scale value. When the polynomial and exponential table is
used in conjunction with the active power dispatch table, the coefficients and integration constant
should be defined in units which, when a product is taken with the fuel cost scale coefficient defined
in the active power dispatch table record, the resulting value is in units of cost units / hour. For
example, if the fuel cost scale coefficient in the active power dispatch table has units of $/MBTU,
then the integration constant should be specified in units of MBTU/hour.
Siemens Energy, Inc., Power Technologies International 13-59
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-60 Siemens Energy, Inc., Power Technologies International
Status, Status [In (1)]
In-service (1)
Out-of-service (0)
The status switch indicates whether the specified period reserve record should be
included within the OPF problem statement. Only in-service period reserve records will
be included as a reserve constraint.
Participating Units
A list of participating generator reserve units available to the period reserve constraint.
Each unit must already have a corresponding generator reserve data record defined.
Each participating unit is uniquely specified by the following identifiers:
Bus, Bus
The bus number of the bus where the unit is located. When using the
spreadsheet, this value may need to be entered as a bus name, depending
upon the input mode currently in effect.
Unit ID, GenID
The generator unit identifier of the participating generator. A default identi-
fier of 1 is assumed if left blank.
Period Reserve Data Editor
The Period Reserve data editor displays all Period Reserve data records within the working case.
The subsystem filter has no effect on the list displayed. If no Period Reserve records exist in the
working case, the editor will be blank.
13.9.15 Branch Flow Constraint Data
Branch Flow Constraint records define upper and lower flow limits on selected non zero impedance
branches. Four different flow limits may be imposed: MW, MVar, MVA and Ampere. More than one
branch flow constraint type may be defined for the same branch.
Branch Flow Constraint Data Record
The format of each Branch Flow Constraint record is:
IBus, JBus, CktID, BfID, F
max
, F
min
, EF
max
, EF
min
, Ftyp, Ltyp, Lpen,
KBus
When entering records in the OPF Raw Data File, each field must be separated by either a space
or a comma and any fields left blank must be delineated by commas. An IBus number of zero indi-
cates that no further branch flow constraint records are being entered.
The from bus, to bus, third bus (for three-winding transformers), circuit id and flow id uniquely iden-
tify each Branch Flow Constraint record. The values for each record are defined as follows:
From bus number, IBus
The sending bus, specified by a number from 1 through 999997. The number must cor-
respond to an existing bus within the power flow working case.
Siemens Energy, Inc., Power Technologies International 13-61
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-62 Siemens Energy, Inc., Power Technologies International
To enforce recognition of the minimum and maximum emergency flow limits as
opposed to the normal flow limits during the OPF solution, select the Impose Emer-
gency Branch Flow Limits solution option.
Minimum emergency flow limit, EF
min
[0.0]
The minimum emergency flow limit on the specified branch. This limit, in conjunction
with the maximum emergency limit, defines an optional alternate set of flow limits. Val-
ues are specified in physical units appropriate to the flow limit type being specified;
Ampere constraints are specified in MVA.
Flow type, Ftyp [Ampere (4)]
One of four different flow types specified for the constraint:
MW (1)
MVar (2)
MVA (3)
Ampere (4)
Limit type, Ltyp [Hard limit (1)]
One of four constraint limit types enforced during the OPF solution:
Reporting only (0)
Only report on violations of the specified branch flow limits, taking no action
if the branch flow falls outside of limits.
Hard limit (1)
Strictly enforce the specified branch flow limits through the use of barrier
terms.
Soft limit with a linear penalty (2)
Permit branch flows to go outside of their specified branch flow limits, but
penalize excursions along a linear curve. The Soft limit penalty weight, as
defined below, is used in conjunction with this penalty to indicate severity
of excursion.
Soft limit with a quadratic penalty (3)
Permit branch flow limit to go outside of their specified flow limits, but penal-
ize excursions along a quadratic curve. The Soft limit penalty weight, as
defined below, is used in conjunction with this penalty to indicate severity
of excursion.
Refer to Section 13.7.2 for more information on the limit type options.
Soft limit penalty weight, Lpen [1.0]
The penalty weight value applied to either the linear or quadratic soft limit penalty func-
tions. The larger the number, the higher the penalty for branch flow excursions outside
of limits.
Siemens Energy, Inc., Power Technologies International 13-63
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-64 Siemens Energy, Inc., Power Technologies International
Minimum interface flow limit, F
min
[0.0]
The minimum flow limit across the interface, specified in the physical units appropriate
for the specified flow limit type defined below.
If the range between the maximum and minimum interface MW flow limits is less than
0.001, then the minimum interface flow limit is set to the average of the two interface
flow limit values minus 0.1.
Flow type, Ftyp [MW (1)]
One of two valid flow types:
MW (1)
MVar (2)
Limit type, Ltyp [Hard limit (1)]
One of four different limit types:
Reporting only (0)
Only report on violations of the specified interface flow limits, taking no
action if the interface flow falls outside of limits.
Hard limit (1)
Strictly enforce the specified interface flow limits through the use of barrier
terms.
Soft limit with a linear penalty (2)
Permit interface flows to go outside of the specified interface flow limits, but
penalize excursions along a linear curve. The Soft limit penalty weight, as
defined below, is used in conjunction with this penalty to indicate severity
of excursion.
Soft limit with a quadratic penalty (3)
Permit interface flows to go outside of the specified interface flow limits, but
penalize excursions along a quadratic curve. The Soft limit penalty weight,
as defined below, is used in conjunction with this penalty to indicate severity
of excursion.
Refer to Section 13.7.2 for more information on the limit type options.
Soft limit penalty weight, Lpen [1.0]
The penalty weight value applied to either the linear or quadratic soft limit penalty func-
tions. The larger the number, the higher the penalty for interface flow excursions out-
side of the defined interface flow limits.
Participating Branches
A list of branches defining the interface. Each branch is individually specified by the fol-
lowing identifiers:
From bus number, Ibus
The sending bus number (1 through 999997). When using the spreadsheet,
this value may optionally be entered as a bus name, provided that names
input mode is in effect.
To bus number, Jbus
The receiving end bus number (1 through 999997). When using the spread-
Siemens Energy, Inc., Power Technologies International 13-65
PSS
E 32.0
Constraint and Control Data Program Operation Manual
13-66 Siemens Energy, Inc., Power Technologies International
Maximum constraint slack, Slk
max
[0.0]
The constraint equation maximum slack variable limit.
Minimum constraint slack, Slk
min
[0.0]
The constraint equation minimum slack variable limit.
Participating Variables
Any number of participating variables may be included in the linear constraint depen-
dency equation. The variable identifiers must correspond to a record that already exists
within the working case.
Dependency variable type code, Vtyp [0]
A number (1 through 10) corresponding to the type of dependency variable being
added to the constraint equation. The numerical values associated with each vari-
able type are as follows:
(1) Voltage magnitude
(2) Voltage angle
(3) Active power generation
(4) Reactive power generation
(5) Transformer
(6) Branch flow
(7) Interface flow
(8) Adjustable bus shunt
(9) Switched shunt
(10) Load adjustment
Variable identification fields, "ID fields"
Depending upon the variable type code selected above, one or more identification
fields must be specified in order to uniquely identify the record to be employed as
the variable entry. The identification fields corresponding to each of the variable
type codes defined above, are as follows:
1: Bus number (1 through 999997)
2: Bus number (1 through 999997)
3: Active power dispatch table number
4: Bus number (1 through 999997)
Generator identifier [" 1"]
5: From bus number
To bus number
Circuit identifier [" 1"]
Siemens Energy, Inc., Power Technologies International 13-67
PSS
E 32.0
Optimal Power Flow Solution Options Program Operation Manual
13-68 Siemens Energy, Inc., Power Technologies International
13.10 Optimal Power Flow Solution Options
Optimal power flow solution parameters may be applied prior to initiation of the OPF solution. These
solution parameters are used to further define the optimal power flow problem statement and may
direct the program to perform additional functions after the solution process has completed.
The five solution parameter groups are as follows:
Objectives: A list of all available solution objectives. Cost coefficient values are also
listed for those objectives that may have an associated cost applied.
General: A list of general optimal power flow solution options and additional constraint
equation directives that may be activated during the solution process.
Tolerances: A list of solution tolerance values and advanced level solution parameters
that may be altered to influence the progress of the solution algorithm.
Control: A list of options pertaining to the treatment of nonoptimized controls within the
optimal power flow problem statement.
Reporting: A list of output reporting options. These must be defined prior to solution
initiation.
13.10.1 Objectives
More than one objective may be applied simultaneously to formulate a composite objective function.
The exception is the Minimize fuel cost and Minimize active power loss objectives, of which neither
can solve for their respective goals if the other objective is active. This is covered in more detail in
Minimize Fuel Cost and Minimize Active Power Loss.
Table 13-2. Optimal Power Flow (OPF) Objectives
OPF Objective Description
Minimize Fuel Cost
Directs the OPF to find the minimal amount of active power required to serve losses
and loads.
The system swing bus is automatically considered into the problem statement
although its active power generation is fixed at the initial value and not considered
an available control.
In addition to specifying the Minimize fuel cost objective, three key data elements
are essential to the fuel cost model:
Generators for dispatch: Each eligible participating generator in the active
power dispatch model must have a Generator Dispatch record defined. The
information within the Generator Dispatch record includes the percentage of
total generation capacity available for dispatch.
Active power dispatch constraints: Each Generator Dispatch record
references a single Active Power Dispatch Table that defines the minimum
and maximum active power available for dispatch, and references a Cost
Curve Table.
Generator fuel cost curves: Each Active Power Dispatch Table references
one of three available cost models: piece-wise linear, piece-wise quadratic
and polynomial.
Siemens Energy, Inc., Power Technologies International 13-69
PSS
E 32.0
Optimal Power Flow Solution Options Program Operation Manual
13-70 Siemens Energy, Inc., Power Technologies International
Minimize Adjustable
Bus Shunts
Determines the minimal amount of shunt reactors and capacitors that need be
placed at candidate buses. It may be employed in voltage stability studies or to
assist in the minimization of a composite objective function.
Candidate buses for var adjustment must be defined through Adjustable Bus Shunt
records prior to the OPF solution (Section 13.9.3).
To encourage the deployment of vars, particularly for voltage stability studies, it may
be desirable to fix transformer taps, phase shifters and switched shunts (see Fix
Transformer Tap Ratios).
During the OPF solution, var values may optionally be rounded to the nearest
discrete block step by choosing to Round switched shunt vars (see Round
Switched Shunt Vars).
After the solution process has completed, the new shunt additions will automatically
be reflected in the power flow bus data of the working case as bus shunts.
Minimize Adjustable
Bus Loads
Determines the minimal amount of load adjustment to make at candidate buses. It
is most commonly used to study the effects of load shedding to ease voltage
constraint violations due to a severe disturbance on the system. It is possible
however to formulate a problem statement in which the minimization of load addi-
tions, as opposed to load shedding, is the objective.
Candidate buses for load adjustment must be defined through OPF Adjustable Bus
Load records (Section 13.9.4) and Adjustable Bus Load Table records
(Section 13.9.5) prior to the solution.
After the OPF solution process, new load adjustment factors will be reflected in the
value Psi, and displayed with the load values in PSS
E Newton Solution
tolerance, TOLN, and may be modified (refer to PSS
E 32.0
Optimal Power Flow Solution Options Program Operation Manual
13-72 Siemens Energy, Inc., Power Technologies International
Round Switched
Shunt Vars
Directs the OPF solution process to round switched shunt values to their nearest
block setting after an initial solution is obtained and then attempts to continue to a
feasible solution with the switched shunt settings fixed.
This option only applies to switched shunts within the general power flow model. It
does not affect any OPF adjustable bus shunts.
Rounding to the nearest var block attempts to mimic the discrete nature of switched
shunts. During the main OPF solution switched shunt var adjustments are treated
as continuous functions. In some situations the rounding may lead to serious
voltage infeasibilities, particularly if the var block size is rather large. If this should
occur it may be prudent to manually round var settings instead.
When the rounding takes place, upper and lower bus voltage limits may need
to be relaxed to attain a solution. If this should happen, an integer value will
appear to the far right-hand side of the OPF solution iteration log under an
unlabeled column. This value indicates the total number of variables for which
limits needed to be relaxed as a result of rounding.
Automatically Adjust
Bus Voltages for
Feasibility
Temporarily adjusts minimum or maximum bus voltage limits to ensure that the
current voltage is within the specified range.
For example, if the lower and upper voltage limits at a particular bus are set at 0.95
and 1.02 pu respectively, and the initial voltage in the power flow bus data is 0.94,
then the voltage bounds at the bus would temporarily be set to 0.94 and 1.02. Only
the infeasible bound is modified; the actual voltage limits as defined in the corre-
sponding OPF Bus Voltage Attribute data record are not affected.
To permanently change the constraint limits for feasibility, use the Adjust limits
option in the Bus Voltage Attribute Spreadsheet. This option may be selectively
applied to individual OPF bus voltage constraint records or applied to all buses
within a selected subsystem.
Impose Emergency
Bus Voltage Limits
Directs the OPF solution process to employ the maximum and minimum emergency
bus voltage limits defined in the OPF Bus Attribute data records instead of the
normal bus voltage limits. Refer to Bus Voltage Attribute Data Record for further
information.
Impose Emergency
Branch Flow Limits
Directs the OPF solution process to employ the maximum and minimum emergency
branch flow limits defined in the Branch Flow Constraint Data Record instead of the
normal branch flow limits.
Table 13-3. Optimal Power Flow (OPF) Parameters - General Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 13-73
PSS
E 32.0
Optimal Power Flow Solution Options Program Operation Manual
13-74 Siemens Energy, Inc., Power Technologies International
Bad Iteration Coarse
Limit
Specifies the number of bad iterations allowed when the barrier coefficient is
greater than 0.011 (mu greater than -2) before the solution progress is terminated
as being infeasible.
At each iteration of the solution process several criteria are evaluated to assess
whether the solution should continue or be terminated due to infeasibility. In
general, the solution will terminate on an infeasible condition if at least one of the
following conditions are encountered.
the number of successive bad iterations hits a predefined limit, or
the solution process is forced to take an algorithmic step that is smaller than
a predefined minimum tolerance.
As used in the context above, a bad iteration is defined as one in which:
the difference between the nonlinear objective function in the present and
prior iterations is less than zero, or
the ratio of the largest mismatch value between the current and prior
iterations is greater than, or equal to, 0.95.
By default, the coarse limit on the number of bad iterations is set at 3. If the solution
process appears to be making very small progress, it is possible for this limit to be
exceeded. In situations where the mismatch value is making slow, but steady,
progress, and the reduction of the objective is also making some progress, it is
reasonable to try to increase the bad iteration limit.
Bad Iteration Fine
Limit
Specifies the number of bad iterations allowed when the barrier coefficient is less
than, or equal to, 0.011 (mu less than or equal to -2) before the solution progress is
terminated as being infeasible.
By default, the fine limit on the number of bad iterations is set to 10. If the solution
process appears to be making very small progress it is possible for this limit to be
exceeded prematurely. In situations where the mismatch value is making slow, but
steady, progress, and the reduction of the objective is also making some progress,
it is reasonable to try to increase the iteration limit.
Maximum Iteration
Limit
Indicates the maximum number of allowable iterations before the OPF solution
process will end. This value is identical to the Iteration limit (ITMXN) value used for
the Newton power flow solution activities. It may also be modified (refer to PSS
E
GUI Users Guide, Section 11.1, Specifying Solution Parameters).
Convergence
Tolerance
Defines the largest allowable mismatch tolerance in MW and Mvar. For the OPF
solution process to terminate successfully, the largest mismatch must be at, or
below, the convergence tolerance specified.
This value is identical to the largest mismatch in MW and Mvar (TOLN) value used
in the main power flow Newton solutions. It may also be modified (refer to PSS
E
GUI Users Guide, Section 11.1, Specifying Solution Parameters).
Table 13-4. Optimal Power Flow (OPF) Parameters - Tolerance Options (Cont.)
Option Description
Siemens Energy, Inc., Power Technologies International 13-75
PSS
E 32.0
Optimal Power Flow Solution Options Program Operation Manual
13-76 Siemens Energy, Inc., Power Technologies International
13.10.4 Control Options
Table 13-5. Optimal Power Flow (OPF) Parameters - Control Options
Option Description
Treat all Generators
as Non-optimized
Forces all generators in the network to be treated as nonoptimized. This overrides
whether the generator is in an optimized subsystem or not.
Clamp Non-opti-
mized Generators
Applies the clamp equation logic to all nonoptimized generators. This overrides the
quadratic penalty treatment, but does not supersede bus voltage constraints that
may be applied at generator buses.
Values for Final clamp tolerance, Initial clamp tolerance and Clamp slack variable
decay factor may be entered directly into the fields provided.
As described in Clamp Treatment, the OPF solution initializes the problem with the
relatively large Initial clamp tolerance, and then systematically and gradually
reduces this tolerance by the Clamp slack variable decay factor until a value less
than or equal to the Final clamp tolerance is attained. Reductions in both the clamp
equation slack variable and the clamp tolerance are taken when a solution step size
of at least 0.5 is achieved.
For example, with a default initial clamp tolerance of 1.0 and a decay factor of 0.1,
the clamp tolerance will gradually be reduced by 10 (multiplied by 0.1) at each
healthy step of the solution process, until a final tolerance value of 0.0001 is
attained.
The Scale clamp constraint by reactive generator limits option scales the clamp
equation by the maximum of either 1.0 or the difference between the upper and
lower generator reactive limits. This is done internal to the solution to potentially
improve mathematical calculations and should be transparent.
Use Generator
Scheduled Voltage
Directs the solution to hold voltage to the generator scheduled voltage instead of
the current voltage.
Penalty for Fixed
Voltage
The Quadratic penalty treatment of nonoptimized generators is the default if the
Clamp non-optimized generators option is not enabled, and bus voltage constraints
on generator buses are not applied. Quadratic terms are introduced into the objec-
tive function to penalize the excursion of regulated voltage magnitudes from their
offsets. The value specified in the Penalty for fixed voltage field indicates the extent
to which excursions are penalized.
Siemens Energy, Inc., Power Technologies International 13-77
PSS
E 32.0
Solution Results and Reports Program Operation Manual
13-78 Siemens Energy, Inc., Power Technologies International
13.11 Solution Results and Reports
Several output reports may optionally and automatically be generated after the OPF solution:
OPF Progress Summary Report: All information pertinent to the progress of the optimal
power flow solution is contained within this summary. By default, the output is directed
to the progress device but may optionally be directed to an alternate device such as a
file or printer.
OPF Solution Report File: A detailed report containing a summary of the optimal power flow
problem statement, and the resulting control variable settings and sensitivities is pro-
duced. By default, this report is directed to the report device.
OPF Optimization Log File: An OPF Optimization Log File may optionally be generated. In
addition to the information included in the OPF solution report, the log file also contains
problem statement statistics, post solution results, and optionally, a detailed listing of
Lagrange multipliers. The option to produce the OPF Optimization Log File file is set by
enabl i ng the Produce opti mi zati on l og fi l e opti on on the Reporti ng tab of
[OPF - Change Parameters].
The following subsections describe the contents of each of the above output reports and files in
more detail.
13.11.1 OPF Progress Summary Report
During the optimal power flow solution information pertaining to its progress will automatically be
displayed to the Progress tab of the PSS
E 32.0
Solution Results and Reports Program Operation Manual
13-80 Siemens Energy, Inc., Power Technologies International
The problem size information is immediately followed by a qualitative statement indicating the initial
conditions of the optimal power flow problem. An example follows:
Note: There were 3 infeasible variables found.
The sum of the violations is 0.2055,
The largest violation is Efd 206 0.1934.
The first line specifies the number of variables for which initial values violate their stated limits.
The second line specifies the sum of the absolute values of the per unit values for each constraint
violation.
The third line specifies the variable having the largest constraint limit violation, along with the value
in pu. The nomenclature used to identify the variables (i.e., Efd), is defined in Table 13-8.
Solution Iteration Log
A summary of the nonlinear solution progress is displayed to the progress device and, optionally, to
the OPF Optimization Log File. As discussed in Section 13.7.1, the nonlinear nature of the OPF
problem requires that a series of simpler subproblems be solved. At each iterate of the solution
process, one of the subproblems is solved and a row of information is displayed describing the
progress made. This iteration log is the primary means of monitoring the progress of the solution.
The output is of the following form:
----------------------------------------------------------------------------------------------------
Iter Mu NL Objective Norm RHS Mismatch(PU) Row Equation Nearest Variable Step size NE
---- -- ------------ ---------- ------------------------------ ------------------------------ ---
1 0 2.88120E+01 2.42E+02 6.34E+00 RC-Q 206 Flow 153 u 4.58E-01
2x 0 2.95010E+01 1.18E+02 3.39E+00 RC-Q 206 Trns 204 u 7.33E-01
3 -1 3.03835E+01 2.23E+02 9.16E-01 F-eq 153 1.00E+00
4 -2 3.04181E+01 7.35E+01 8.11E-02 Peqn 204 Volt 3018 u 1.01E-01
5 -2 3.02021E+01 2.23E+02 7.37E-02 Peqn 204 Segm +70 3.61E-01
6 -2 2.98706E+01 1.70E+02 4.72E-02 Peqn 204 1.00E+00
7 -3 2.97907E+01 5.33E+00 6.03E-03 Qeqn 153 Segm +70 1.08E-01 1
. . .
The information contained within each row is defined as follows:
Iter: The current subproblem, or iteration number. An x following the number indicates that the
prior iteration was determined to be bad according to the definition given in Problem ms
Infeasible.
Mu: The barrier coefficient exponent, also referred to as the barrier parameter. As discussed
in Initial Barrier Coefficient, the number is the exponent of 10. A value of -3 signifies a
barrier parameter value of 10
-3
, or 0.001.
The barrier parameter is the coefficient in the barrier objective function. The smaller the
barrier parameter, the closer the variables (voltages, taps, and others) can approach their
bounds, if that is the direction that they are driven towards. A large barrier parameter of
about 0.01 will keep just about all variables off their bounds and towards the middle. A small
barrier parameter of 0.00001 ( = 5) or less will allow those variables to get very close to
their limits.
NL Objective: The sum of all the objective components. This value includes all explicitly
defined objectives, as well as any implicit objective terms that may have been introduced
(i.e., terms of the quadratic penalty equation introduced for certain power flow controls
(Section 13.5) or the barrier terms required for constrained variables at a hard limit).
Siemens Energy, Inc., Power Technologies International 13-81
PSS
E 32.0
Solution Results and Reports Program Operation Manual
13-82 Siemens Energy, Inc., Power Technologies International
Solution Termination Message
A termination message will be displayed immediately following the solution progress log. An item-
ized list of the objective functions and their values follows, along with a solution timing report. The
following is one such example:
Optimal Solution Found.
Minimum Fuel cost objective: 29115.463109
Minimum series var objective: 23.121500
Elapsed time: 0 minutes, 0.2 seconds.
CPU time: 0 minutes, 0.1 seconds.
In the above example, the optimal power flow problem minimized fuel cost and adjustable branch
reactances (series compensation).
Labeling Nomenclature
The following two tables define the labeling conventions used in a number of the solution results
tables.
Jacobian Columns: Within the OPF output reports, the power system variables placed in the
columns of the Jacobian matrix are described with an abbreviated label. The labeling
nomenclature consists of a character string followed by an integer number. The character
labels are defined in Table 13-8. The integer number appended to the label corresponds to
one of two values:
- If the number is prefixed with a +, the number that follows is a sequence number.
For example, the label Intf +3 refers to the third interface defined in the working
case.
- If a number is specified without a + prefix, the value simply refers to the identifica-
tion number describing the power system element. For example, the label Angl 101
refers to the angle at bus 101.
Jacobian Rows: The labeling nomenclature used within the OPF reports to describe the
constraints that make up the rows of the Jacobian matrix consists of a character label
followed by a number. The labels are described in Table 13-9. The numbers refer to one of
two values:
- If the number is prefixed with a +, it refers to a sequence number. For example, the
label RTEQ +1 refers to the first generation period reserve constraint defined within
the working case. Sequence numbers are used when the constraint cannot be ref-
erenced back to a power flow bus.
- If the number is not prefixed with a +, the value given is the power flow bus number
for which the constraint equation is defined at. For example, Peqn 101 refers to the
active power constraint equation at bus number 101 in the working case.
Siemens Energy, Inc., Power Technologies International 13-83
PSS
E 32.0
Solution Results and Reports Program Operation Manual
13-84 Siemens Energy, Inc., Power Technologies International
13.11.2 OPF Solution Results Report
An OPF Solution Results Report is automatically produced at the completion of the optimal power
flow solution. It is sent to the report device by default but may be redirected to an alternate device
or file through the I/O Control > Direct report output (OPEN)... menu option.
The OPF Solution Report consists of tables containing summaries of the problem statement control
and constraint variable settings, and their sensitivities to the objective. The report itself is printed in
a format suitable for printing and is necessary for performing post processing and analysis.
It is not possible to send the OPF Report to the Progress View! To avoid potential confusion
that would arise from having output from both the OPF Solution Report and the Solution Iter-
ation Log simultaneously sent to the Progress View and getting mixed together, the OPF Solution
Report information is prevented from being sent to the Progress View. If the device specified by the
I/O Control > Direct report output (OPEN)... menu option is set to the Current progress device, then
the report will automatically be redirected to the report device. This action does not cause the output
of any other activity to be redirected.
13.11.3 OPF Optimization Log
The OPF Optimization Log File is optional and, by default, will not be produced. To produce an Opti-
mization Log File, the Produce optimization log file option must be enabled prior to initiating the
solution. By default the resulting file will be called DETAIL.DAT. An alternate name may be specified
by entering a name directly in the Optimization log input field or selecting from a list of existing files
by clicking [ ] to the right of the input field. Existing files will be overwritten! Refer to Produce
an Optimization Log File for further information on the use of this dialog.
In addition to the information printed within the standard OPF Progress Summary Report discussed
in Section 13.11.1, the Optimization Log File also includes information on problem size statistics
and optionally, a detailed listing of the power system variables and Lagrange multipliers. The
following section describe items that are unique to the Optimization Log File.
RC-Y Generator stator current, to limit reactive capability model mE
fd
+b
RTMW Generation period reserve participating unit
RTEQ Generation period reserve
LNCS Customized linear dependency
AI Regulated area interchange
CGEN Local generator voltage control clamp
Table 13-9. Jacobian Row Label Descriptions (Cont.)
Label Constraint Equation Description
Siemens Energy, Inc., Power Technologies International 13-85
PSS
E 32.0
Solution Results and Reports Program Operation Manual
13-86 Siemens Energy, Inc., Power Technologies International
F: The final status of the variable. This flag may take on one of the following values:
S: The final state of the variable. The state is described by an integer according to the
following table:
Value: The final value of the variable. The units associated with the values correspond to the
following:
- Voltage magnitudes are in per unit;
- Voltage angles are in radians;
- Branch flow constraints (MVA and Ampere) are in terms of their magnitudes
squared;
- Transformer tap ratios are inverted.
Lower: The value of the variables lower bound. The units of the values are as stated within
the definition for Value.
Upper: The value of the variables upper bound. The units of the values are as stated within
the definition for Value.
Cost: The sensitivity of the variable. Whenever a variable reaches an upper or lower bound,
or is fixed, there will be a nonzero entry in this column. The sensitivity values indicate how
much impact it can have on the objective with a small move beyond its boundary limits. All
U: The variable is limited by an upper bound;
L: The variable is limited by a lower bound;
F: The variable is fixed at a given value;
-: The lower bound of the variable has been relaxed;
+: The upper bound of the variable has been relaxed;
I:
The variable is infeasible. Variables that are infeasible are always
displayed in the Optimization Log, independent of whether the full
detailed listing is produced, or not.
Table 13-10. Variable State Values
Variable State, S Variable (x) Condition
0 x = x
min
1 x = x
max
2 x
min
< x < x
max
3 - < x < +
4 x = x
0
(x
0
initial condition)
5 x
min
< x < +
6 - < x < x
max
7 - < x < +
Siemens Energy, Inc., Power Technologies International 13-87
PSS
E 32.0
Examining OPF Data and Results Program Operation Manual
13-88 Siemens Energy, Inc., Power Technologies International
13.12 Examining OPF Data and Results
Optimal power flow data values may be examined through several different functions, including:
Power Flow > List Data... , OPF button
Produces a tabular report of any or all of the OPF constraint and control data within the
working case.
The OPF Solution Report
A tabular report automatically generated subsequent to the OPF solution process. The
report contains a solution summary and sensitivity tables pertaining to the power sys-
tem variables of the OPF problem statement.
OPF > Data... and OPF > Data tables...
Presents the power flow and optimal power flow data in spreadsheets and data tables
suitable for viewing and editing.
Some of these functions provide additional capabilities for editing the data values displayed.
Each subsection of this chapter covers the above program functions in some detail.
Siemens Energy, Inc., Power Technologies International 13-89
PSS
E 32.0
Listing Control and Constraint Data Program Operation Manual
13-90 Siemens Energy, Inc., Power Technologies International
Bus Shunt
All adjustable bus shunt records within the defined subsystem are displayed in the
output report. Multiple bus shunts at the same bus are differentiated by unique
shunt identifiers.
The data values displayed in the table correspond directly to definitions provided in
Adjustable Bus Shunt Data Record. Values listed under Cost type and Cost table
are displayed for completeness but are not utilized by the current release of the
program.
Generator Dispatch
Data
All generator dispatch records referencing an active power dispatch table number
greater than zero and residing within the selected subsystem for printing are listed
in the generator dispatch report. The data values for each generator dispatch
record are defined in Generator Dispatch Data Record.
Generation Reactive
Capability Data
All generation reactive capability data records of machines residing within the
defined subsystem are listed in the output report. Machines are listed in ascending
bus order (numeric or alphabetic) and multiple machines at the same bus are listed
in ascending machine identifier order.
The data values listed under each heading of the record correspond directly to the
definitions provided in Generation Reactive Capability Data Record.
Generation Reserve
Data
All generation reserve data records for machines residing in the defined subsystem
are listed in the output report. Machines are listed in ascending bus order (numeric
or alphabetic) and multiple machines at the same plant bus are listed in ascending
machine identifier order.
The values listed under Ramp rate and Capability correspond directly to the defini-
tions provided in Generation Reserve Data Record.
Interface Flow Con-
straint Data
All interface flow constraint records contained in the working case are listed in the
report. Interfaces are listed in ascending order based upon the interface flow
identifier.
Each interface flow record may contain one or more participating branches that
define the interface. The participating branches are listed to the far right of the
report on separate lines, in ascending from bus order (numeric or alphabetic) and
then ascending to bus order. Parallel circuits between any pair of buses are tabu-
lated in ascending circuit identifier order.
The data values listed within each interface flow constraint data record are defined
in Interface Flow Data Input Values.
Linear Constraint
Dependency Data
All linear constraint dependency records having one or more participating variable
records are listed in ascending linear constraint identifier order within the report.
Participating variable records are displayed to the far right of the output report with
each participating record listed on a separate line.
Each participating variable record is listed in the order in which it is stored in the
working case. The Type code value indicates the type of variable being listed. The
entries listed under the Participating entry description label identify the variable
record being included in the linear constraint dependency equation. These may
include identifiers such as table numbers, branches (from bus, to bus and circuit
identifier) and machines (bus and generator identifier).
The data values listed within each linear constraint dependency data record,
including a description of the variable type codes and their corresponding identi-
fiers, are defined in Linear Constraint Dependency Data Record.
Table 13-11. Optimal Power Flow (OPF) Data Output Options (Cont.)
Report Type Description
Siemens Energy, Inc., Power Technologies International 13-91
PSS
E 32.0
Optimal Power Flow Solution Report Program Operation Manual
13-92 Siemens Energy, Inc., Power Technologies International
13.14 Optimal Power Flow Solution Report
The OPF Solution Report is automatically produced after an OPF solution. By default, output is sent
to the report device but may optionally be redirected to an alternate device through the use of
activity OPEN.
The following sections describe each portion of the OPF Solution Report, in the order in which they
appear in the report.
13.14.1 Solution Termination Summary
A qualitative summary of the power flow problem is output at the top of the report. This information
indicates the initial conditions of the optimal power flow problem statement, as shown below:
Note: There were 4 infeasible variables found.
The sum of the violations is 0.4437,
The largest violation is Efd 206 0.2377.
A complete description of the information presented in this summary can be found in the Solution
Termination Message.
Immediately following the above summary a statement is printed indicating whether an optimal solu-
tion was found or not. Along with this will be an itemized list of each resulting objective function
value.
Optimal Solution Found.
Minimum Fuel cost objective: 29208.031976
Minimum series var objective: 29.271418
If the message states something other than Optimal Solution Found, then the results
presented in the rest of the report will not represent a solved problem! Messages such as
Exceeded maximum number of iterations. or Problem ms infeasible. are analyzed
in Maximum Iteration Limit Exceeded and Problem ms Infeasible respectively.
13.14.2 Interface Flows
Each interface flow constraint record in the working case is displayed in the Interface Flow report.
One table is produced for each interface flow constraint specified.
----- Interface Flow -----: AREA 5 TO AREA 1 Continued.
Minimum and Maximum: -160.000 -155.000, Sensitivity: -513.5541 Status: Constrained
From Bus Name kV Area Zone To Bus Name kV Area Zone MW Flow Mvar Flow Mva Flow
--------------------------------------- --------------------------------------- --------- ----------- ----------
3004 WEST 500.00 5 5 152m MID500 500.00 1 1 -79.770 64.503 102.586
3006 UPTOWN 230.00 5 5 153m MID230 230.00 1 1 -49.223 -27.433 56.351
3008 CATDOG 230.00 5 5 154m DOWNTN 230.00 1 1 -26.026 65.054 70.067
---------- ---------- ----------
Totals: -155.019 102.124 185.635
The top line of the report specifies the name of the interface flow constraint being reported.
Immediately following the Minimum and Maximum: field are two values reflecting the minimum and
maximum interface flow limits defined across the interface. Values are expressed in either MW or
Mvar, depending upon the flow condition defined in the data record.
The Sensitivity: field has a value immediately following it if all following conditions are met: a flow
limit has been reached, the OPF Solution Parameter option to Constrain Interface Flows is enabled,
and the interface flow constraint being reported upon does not have a Limit type of Reporting. The
Siemens Energy, Inc., Power Technologies International 13-93
PSS
E 32.0
Optimal Power Flow Solution Report Program Operation Manual
13-94 Siemens Energy, Inc., Power Technologies International
13.14.4 Bounded and Infeasible Reactive Generation
The Bounded and Infeasible Reactive Generation report displays generators within the selected
subsystem where reactive generation values have reached or violated the upper or lower bound.
Bounded and Infeasible Reactive Generation:
-------------------------------------------
Bus # Name kV ID Variable Description Sensitivity Violation
-------- ------------ ------ -- ------------------------------ ---------- ----------
206 URBGEN 18.000 1 Efd (PU) = 2.2795 -762.
3018 CATDOG_G 13.800 1 Qgen (Mvar) = 109.66 29.7
3018 CATDOG_G 13.800 1 Efd (PU) = 2.4677 741. 0.188
Reactive generation limits (Qmax and Qmin) are introduced through the main power flow generator
model. Additional limits on armature reaction and stator current can be applied using the OPF
generator reactive capability model.
The bus number (Bus #), Name, base kV and machine identifier (ID) describe the reported gener-
ator unit.
The Variable Description column displays the reactive generation value being reported. The labels
may be one of the following:
Qgen (Mvar) - The reactive power injection in Mvars.
Efd (pu) - The armature reaction in per unit.
Is (pu on MVARC) - The stator current value in per unit on generator MVA rating.
The Sensitivity column displays a sensitivity value for generators where reactive generation value
has reached or exceeded a limit, and where sensitivity value is larger than the greater of 0.1 or 10%
of the largest reactive generation related variable sensitivity. Values are shown in Acost/Aper unit
based upon the system MVA.
The Violation column displays the amount by which the reported value has exceeded its limit. Viola-
tions may result in situations where soft limits are applied or reactive capability models have been
employed. In the above report, two violations have occurred at bus 3018, machine identifier 1. The
first violation indicates that the reactive power injection has exceeded the specified limit by 29.7
Mvars. The second violation indicates that the armature reaction limit has been exceeded by 0.188
per unit.
13.14.5 Bounded or Infeasible Line Flows
The Line Flows that are Infeasible or at a Bound report lists branches within the specified
subsystem where flows have reached or violated defined flow limits.
Line Flows that are Infeasible or at a Bound:
---------------------------------------------
From Bus Name kV To Bus Name kV Ckt FlowID Flow Minimum Maximum Violation Sensitivity
--------------------------------------------------------------------------------------------------------------------------
153 MID230 230.00 154 DOWNTN 230.00 1 1 199.905 MVA 0.000 200.000 0.000 -104.858
The From Bus, To Bus, Ckt Id, base kV and Flow Id identify the reported branch.
The Flow, Minimum and Maximum columns reflect the final flow value, the type and units of the
reported flow value and the imposed lower and upper flow limits. Flow limit values reflect either
Normal or Emergency flow limits according to the option selected for the OPF solution (Impose
Siemens Energy, Inc., Power Technologies International 13-95
PSS
E 32.0
Optimal Power Flow Solution Report Program Operation Manual
13-96 Siemens Energy, Inc., Power Technologies International
13.14.7 Generation Reserve
A Generation Reserve summary report is displayed for each generator period reserve constraint in
the working case.
Generation Reserve, 200.00 MW in 5.000 minutes.
Bus # Name kV ID MW Reserve MW Maximum
------ ------------------- -- ------------ ------------
206 URBGEN 18.000 1 50.000 50.000
211 HYDRO_G 20.000 1 150.019 500.000
============ ============
Period MW reserve totals: 200.019 550.000, Sensitivity = 0.161E+04
The header line of each Generation Reserve report indicates the active power reserve, in MW, and
the amount of time, in minutes, by which the reserve constraint must be satisfied.
Within each Generation Reserve report is a list of contributing generator reserve units, identified by
the bus number (Bus #), Name, base kV and machine identifier (ID).
The MW Reserve and MW Maximum columns reflects the final reserve and maximum reserve
capabilities, both in units of MW. The final unit reserves and the maximum values for all participating
reserve units are summed together and given at the bottom of each report.
A Sensitivity value is calculated and displayed to the right of the reserve totals if the final reserve
value has reached the reserve limit specified. The sensitivity value reflects the impact that a one
per unit MW change has on the objective (Acost/Aper unit MW, on system MVA base).
13.14.8 Regulated Voltage Buses
A summary record is produced for every voltage regulated bus located within the selected
subsystem. By default, all regulated buses in all areas are printed.
Summary Table for Regulated Voltage Buses:
------------------------------------------
Bus # Name kV Area MW Pmin Pmax Pchange Voltage Vmin V-Sens
Zone Mvar Qmin Qmax Qchange Lambda Vchange Vmax Q-Sens
--------------------------------------------------------------------------------------------------------------
101 NUC-A 21.600 1 750.00 810.00 -2456.884 1.0499 U 0.9500 -1206.0617
77 154.74 -100.00 600.00 73.541 -0.027 0.0299 1.0500 -0.0270
102 NUC-B 21.600 1 750.00 810.00 -2456.887 1.0499 U 0.9500 -1208.8252
77 154.74 -100.00 600.00 73.543 0.017 0.0299 1.0500 0.0168
206 URBGEN 18.000 2 836.40 900.00 36.401-2609.142 1.0136 0.9500
2 428.08 0.00 600.00 -171.919 -102.021 -0.0101 1.0500 -102.0211
The report for each regulated bus includes two lines of output.
The bus number (Bus #), Name and base kV identify the voltage regulated bus. The Area and Zone
numbers of the bus are shown in the upper and lower lines under the Area and Zone heading.
Under the MW and Mvar heading is the final value of the active power, in MW, and the reactive
power, in Mvar. They are shown in the upper and lower lines of the record, respectively.
Siemens Energy, Inc., Power Technologies International 13-97
PSS
E 32.0
Optimal Power Flow Solution Report Program Operation Manual
13-98 Siemens Energy, Inc., Power Technologies International
gency voltage limits defined in the OPF bus voltage attribute data record depending upon the option
selected prior to the OPF solution (Impose Emergency Bus Voltage Limits).
Under the V-Sens heading, a sensitivity value of the voltage to the objective function is displayed in
the upper line if the voltage is at a limit (as indicated by a U or L after the Voltage value), or is fixed
at the current value (as indicated by an F after the Voltage value). The voltage sensitivity value
reflects the impact that a one per unit adjustment in the voltage has on the comprehensive objective
function (Acost/Aper unit voltage magnitude). This is the same value as shown in the Bounded and
Infeasible Voltage Magnitude report (see Section 13.14.3).
Under the Q-Sens heading, a sensitivity value of the reactive generation to the object is displayed
in the lower line if the reactive power of the bus is at a limit (as indicated by a U or L after the Mvar
value), or fixed (as indicated by an F after the Mvar value). The reactive sensitivity value reflects the
impact that a one per unit adjustment in the reactive power has on the objective (Acost/A per unit
Mvar on system MVA base). This is the same information as shown in the Bounded and Infeasible
Reactive Generation report (see Section 13.14.4).
13.14.9 Tap Changing Transformers
The Summary Table for Tap Changing Transformers reports on all tap ratio varying transformers
within the selected subsystem that have a significant sensitivity value or a change in tap ratio.
Summary Table for Tap Changing Transformers:
--------------------------------------------
From Bus kV Area Zone Voltage Ratio Minimum MW Flow Sensitivity
To Bus kV Area Zone Voltage Change Maximum MV Flow Tap Volt
--------------------------------------------------------------------------------------------------------------
151 NUCPANT 500.00 1 1 1.03227 1.00000 F 0.90000 -748.404 -1133.62749
101 NUC-A 21.600 1 77 1.04992u 1.10000 -82.382 -1206.06170
151 NUCPANT 500.00 1 1 1.03227 1.00000 F 0.90000 -748.404 -1137.12650
102 NUC-B 21.600 1 77 1.04992u 1.10000 -82.384 -1208.82517
152 MID500 500.00 1 1 1.02750 1.01506 0.95000 578.878
153 MID230 230.00 1 1 0.99759 0.00506 ( 2 ) 1.05000 305.148
Each two line transformer record identifies the From Bus, To Bus, base kV, Area and Zone number
of the end buses of the transformer.
The Voltage value reflects the from bus and to bus voltages corresponding to each side of the tap.
A single character displayed to the right of either value indicates whether the voltage is limited by a
lower bound (L), upper bound (u), or has been fixed (f).
The Ratio value reflects the tap ratio, in per unit, and is shown on the upper line of the transformer
record. A single character displayed immediately to the right of this value indicates whether the tap
ratio is limited by a lower bound (L), upper bound (U), or is fixed (F).
A Change value may be displayed under the Ratio value if the final tap ratio, as provided in the top
number, has changed from the initial tap ratio.
To the right of the Change value, in parentheses ( ), is the number of discrete tap steps taken. A
zero per unit change will result in a 0 being printed. If the option to Round Transformer Tap Ratios
had been specified, then the change in tap ratio ought to be an exact multiple of the tap step. The
tap ratio will be annotated with a fixed flag (F) to indicate that tap settings were fixed at their nearest
step during the last phase of the solution process. Tap ratio changes may have occurred during the
first phase of the solution process however, prior to the discretization and display of the fixed flag!
The Minimum and Maximum tap ratio limits are displayed in the upper and lower line of the trans-
former record respectively. These values are obtained from the transformer information in the power
Siemens Energy, Inc., Power Technologies International 13-99
PSS
E 32.0
Optimal Power Flow Solution Report Program Operation Manual
13-100 Siemens Energy, Inc., Power Technologies International
A Sensitivity value is displayed in the upper line of the phase shifting transformer record if the phase
shifter is fixed or constrained by either its upper or lower limit. The value is expressed in units of
Acost/A degrees.
13.14.11 Added Shunts
When the Minimize Adjustable Bus Shunts objective is enabled, all adjustable bus shunts adjusted
during the solution and within the specified subsystem for printing are included in the Summary
Table for Added Shunts.
Summary Table for Added Shunt (Mvar):
-------------------------------------
Bus # Name kV ID Area Zone Initial Final Change Minimum Maximum Cost ($/Mvar) Sensitivity
------- ------------------- -- ----- ----- --------- ---------- ---------- ---------- ---------- ------------- ------------
153 MID230 230.00 1 1 1 0.000 4.217 4.217 -40.000 68.00 1.000
154 DOWNTN 230.00 1 1 1 0.000 68.000 68.000 -40.000 68.00 1.000 -151.0977
------- -------
Total: 0.000 72.217
The bus number (Bus #), Name, base kV, ID, Area and Zone columns provide identification infor-
mation for each adjustable bus shunt control. Multiple adjustable bus shunts defined at a common
bus are listed on separate lines and are uniquely identified by the shunt ID.
The Initial, Final and Change values reflect the initial additional shunt installation (in Mvar), the final
additional shunt value (in Mvar) and the difference between the initial and final values, in Mvars.
The Final value is added to the B-Shunt value of the corresponding fixed shunt within the power
flow data. If no corresponding fixed shunt is found, then a new fixed shunt is added with the given
ID.
The Minimum and Maximum columns display the upper and lower Mvar limits of the adjustable bus
shunt devices.
The Cost value is the cost for each Mvar deployed. The values are obtained directly from the
working case.
A Sensitivity value is reported for each adjustable bus shunt record where the final Mvar value is at
a minimum or maximum Mvar limit. The value is expressed in units of Acost/A per unit susceptance
(Mvar).
The Total number of initial Mvars and final Mvars is displayed at the end of the report.
Only adjustable bus shunt controls for which the final shunt value exceeds 0.1 Mvar or the
nominal shunt value has changed by more than 0.1 Mvar will be included in the solution report!
13.14.12 Switched Shunts
All switched shunt devices that have a significant sensitivity value and are located within the spec-
ified subsystem for printing are included in the Bounded Switched Shunt report.
Bounded Switched Shunts:
------------------------
Bus # Name kV Area Zone Final Mvar Minimum Maximum Sensitivity
--------------------------- ----- ----- ------------ ---------- ---------- ------------
154 DOWNTN 230.00 1 1 45.000 U -45.000 45.00 -100.00
The bus number (Bus #), Name, base kV, Area and Zone columns provide identification information
for each switched shunt.
Siemens Energy, Inc., Power Technologies International 13-101
PSS
E 32.0
Optimal Power Flow Solution Report Program Operation Manual
13-102 Siemens Energy, Inc., Power Technologies International
13.14.14 Series Compensation
When the Minimize Adjustable Branch Reactances objective is enabled, all adjustable branch reac-
tance records within the specified subsystem for printing are processed for inclusion in the
Summary Table for Series Compensation.
Summary Table for Series Compensation:
--------------------------------------
From Bus Name kV Area Zone Psi Psi Max Voltage MW Flow Sensitivity
To Bus Name kV Area Zone X (PU) Psi Min Voltage MV Flow Cost
-------------------------------------------------------------------------------------
201 HYDRO 500.00 2 2 0.305 1.000 1.043 794.387 -2067.50921
204 SUB500 500.00 2 2 0.00916 0.300 0.989 244.003 30.01278
Each adjustable branch reactance record is identified by the From bus, To Bus, base kV level, Area
and Zone of each end bus of the branch.
The Psi value is shown in the upper line of the displayed branch record and reflects the final value
of the reactance multiplier, .
The X (pu) value, displayed below the Psi value, is the resulting branch reactance value, in per unit.
The Psi Max and Psi Min column displays the maximum and minimum reactance multipliers as
defined in the adjustable branch reactance record.
The MW Flow and MV Flow column displays the final MW and Mvar flow on the branch at the from
bus.
A Sensitivity value is displayed in the upper line of the last column if the final reactance multiplier is
at a minimum or maximum limit. The sensitivity value is expressed in units of Acost/A per unit .
A Cost value is reported in the lower line of the last column for situations in which is not equal to
1.0. The cost is in units of cost/per unit .
13.14.15 Regulated Area Interchange
When the option to Regulate Area Interchange is enabled during the OPF solution, a Summary
Table of Area Interchanges is printed for all area interchange constraints, independent of whether
the areas correspond to areas within a printed subsystem or not.
Summary Table of Area Interchange:
----------------------------------
Area # Name MW Value Minimum Maximum Sensitivity
-------- ------------ ---------- ---------- ---------- -----------
1 FLAPCO 284.341 210.000 290.000
2 LIGHTCO -139.979 -140.000 -60.000 492.
5 WORLD -144.362 -160.000 -140.000
The area number (Area #) and Name identify the reported area.
The MW Value indicates the final area interchange value, in MW.
The Minimum and Maximum values are the defined interchange limits, in MW.
A Sensitivity value is reported if the final interchange value is at a minimum or maximum limit. This
value is expressed in units of Acost/A per unit MW (on system MVA base).
Siemens Energy, Inc., Power Technologies International 13-103
PSS
E 32.0
OPF Raw Data File Format Program Operation Manual
13-104 Siemens Energy, Inc., Power Technologies International
Limit type [1]:
0 - Reporting;
1 - Hard limit;
2 - Soft limit, linear;
3 - Soft limit, quadratic.
Soft limit penalty weight. [1.0] {real}
13.15.3 Adjustable Bus Shunt Data
Bus, ID, B
init
, B
min
, B
max
, B
cost
, Ctyp, Status, Ctbl
Bus number, 1 to 999997. {integer}
Adjustable bus shunt identifier. [" 1"] {character*2}
Initial Bus shunt susceptance, in Mvar at nominal voltage. [0.0] {real}
Maximum bus shunt value, in Mvar. [0.0] {real}
Minimum bus shunt value, in Mvar. [0.0] {real}
Cost scale coefficient, in cost units/Mvar. [1.0] {real}
Cost type [1]:
1 - Polynomial and exponential;
2 - Piece-wise linear;
3 - Piece-wise quadratic.
Status [1]:
0 - Out of service;
1 - In service
Cost table cross-reference number. [0] {integer}
13.15.4 Bus Load Data
Bus, LoadID, LoadTbl
Bus number, 1 to 999997. {integer}
Bus load identifier. [" 1"] {character*2}
Adjustable bus load table cross-reference number. [0] {integer}
Siemens Energy, Inc., Power Technologies International 13-105
PSS
E 32.0
OPF Raw Data File Format Program Operation Manual
13-106 Siemens Energy, Inc., Power Technologies International
Cost type [1]:
1 - Polynomial and exponential;
2 - Piece-wise linear;
3 - Piece-wise quadratic.
Status [1]:
0 - Out of service;
1 - In service
Cost table cross-reference number. [0] {integer}
13.15.8 Generation Reserve Data
Bus, GenID, Ramp, RTMW
max
Bus number, 1 to 999997. {integer}
Generator identifier. [" 1"] {character*2}
Unit ramp rate, in MW/minute. [9999.0] {real}
Maximum unit reserve capability, in MW. [9999.0] {real}
13.15.9 Generation Reactive Capability Data
Bus, GenID, Xd, I
s,max
, PF
lag
, PF
lead
, Q
limit
, Status
Bus number, 1 to 999997. {integer}
Generator identifier. [" 1"] {character*2}
Direct axis synchronous reactance, in per unit on MBASE. [1.0] {real}
Stator current limit, in per unit on MBASE. [1.0] {real}
Rated lagging power factor. [1.0] {real}
Rated leading power factor. [1.0] {real}
Maximum reactive absorption limit at 0 power factor, in per unit on MBASE. [1.0] {real}
Reactive capability limit status [4]:
0 - Out of service;
1 - Enabled, without any Q
gen
limits;
2 - Enabled, with +AE
fd
inhibited;
3 - Enabled, with - AE
fd
inhibited;
4 - Enabled, with fixed E
fd
.
Siemens Energy, Inc., Power Technologies International 13-107
PSS
E 32.0
OPF Raw Data File Format Program Operation Manual
13-108 Siemens Energy, Inc., Power Technologies International
13.15.12 Piece-wise Quadratic Cost Tables
QTbl#, Label, Cost, N
pairs
x1, y1
...
xN, yN
Piece-wise quadratic cost table number. {integer}
Cost table label. [" "] {character*12}
Cost integration constant. [0.0] {real}
Number (N) of x
i
, y
i
coordinate pairs. {integer}
N coordinate pairs, each entered on a separate line:
x
1
- control variable value. [0.0] {real};
y
1
- incremental cost or energy consumption. [0.0] {real}
13.15.13 Polynomial and Exponential Cost Tables
PTbl#, Label, Cost, Cost
lin
, Cost
quad
, Cost
exp
, Expn
Polynomial and exponential cost table number. {integer}
Cost table label. [" "] {character*12}
Cost integration constant. [0.0] {real}
Linear cost coefficient. [0.0] {real}
Quadratic cost coefficient. [0.0] {real}
Exponential cost coefficient. [0.0] {real}
Exponent of exponential cost coefficient. [0.0] {real}
13.15.14 Period Reserve Constraint Data
RsvId, MWlimit, T, Status
Bus, GenID
...
0 (terminating zero on the last line of each period reserve constraint record)
Reserve identifier, must be a number from 1 through 15. {integer}
Reserve limit, in MW. [0.0] {real}
Period, in minutes. [9999.0] {real}
Status [1]:
0 - Out of service;
1 - In service
Siemens Energy, Inc., Power Technologies International 13-109
PSS
E 32.0
OPF Raw Data File Format Program Operation Manual
13-110 Siemens Energy, Inc., Power Technologies International
Maximum interface flow, in physical units. [0.0] {real}
Minimum interface flow, in physical units. [0.0] {real}
Flow type [4]:
1 - MW;
2 - Mvar;
Limit type [1]:
0 - Reporting;
1 - Hard limit;
2 - Soft limit, linear;
3 - Soft limit, quadratic.
Soft limit penalty weight. [1.0] {real}
List of participating branches, entered on separate lines as:
Ibus From bus number, 1 through 999997. {integer};
Jbus To bus number, 1 through 999997. {integer};
CktID Branch circuit identifier. [" 1"] {character*2};
Kbus Third bus number, 1 through 999997, if a three-winding transformer is
specified. [0] {integer}.
13.15.17 Linear Constraint Dependency Data
EqID, Label, Slk
max
, Slk
min
Vtyp, "ID fields", Coeff
Vtyp, "ID fields", Coeff
...
0 (terminating zero on the last line of each linear constraint dependency record)
Linear constraint equation identifier. {integer}
Linear constraint equation label. [" "] {character*12}
Maximum constraint slack value. [0.0] {real}
Minimum constraint slack value. [0.0] {real}
List of participating equation variables, each entered on a separate line.
Vtyp is one of the following numbers:
1 - Voltage magnitude;
2 - Voltage angle;
3 - Active generation;
4 - Reactive generation;
5 - Transformer value;
Siemens Energy, Inc., Power Technologies International 13-111
PSS
E GUI Users Guide, Section 19.7, Creating an Optimal Power Flow Raw Data File
PSS
E 32.0
OPF Raw Data File Format Program Operation Manual
13-112 Siemens Energy, Inc., Power Technologies International
This page intentionally left blank.
Siemens Energy, Inc., Power Technologies International 14-1
Chapter 14
Dynamic Simulation Activity
Descriptions
This chapter contains operational descriptions of the PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-2 Siemens Energy, Inc., Power Technologies International
14.1 Reading Dynamics Model Data
Activity DYRE
The dynamics data input activity DYRE reads simulation model data from a Dynamics Model Raw
Data File into the dynamics data arrays in PSS
E working memory.
14.1.1 Dynamics Model Raw Data File Contents
The input stream to activity DYRE consists of a Dynamics Model Raw Data File. This file contains
a group of logical records, each of which defines the location in the network (by bus, machine, load,
dc line, etc.) of a dynamic equipment model from the PSS
E model library.
Each logical record is of the following general format:
BUSID model name data list /
where:
The majority of plant-related models (generators, compensators, stabilizers, excitation limiters,
excitation systems, governors, and turbine load controllers) are specified in data records of the
form:
BUSID model name IM data list /
where IM specifies the machine identifier and the other data items are as described above.
Run Activity DYRE - GUI
File>Open
[Open]
Dynamics Model Raw Data File (*.dyr)
Run Line Mode Activity DYRE - CLI
ACTIVITY?
>>DYRE,ADD
ENTER DYNAMICS DATA SOURCE FILENAME :
>>
Interrupt Control Codes
None
BUSID Is the bus identifier (number or extended bus name) of the bus at which this
equipment model is to be placed (from bus for a line relay model), a dc line or
FACTS device name (in single quotes), area, zone, or owner number, or zero.
'model name' Is the name by which the model is referenced. The model name is limited to
sixteen characters, and must be enclosed in single quotes.
data list Specifies the constant parameters associated with the model. Generally, these
parameters are specified in the order in which constants are listed on the data
sheets in the blocks labeled ICONs and CONs.
Siemens Energy, Inc., Power Technologies International 14-3
PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-4 Siemens Energy, Inc., Power Technologies International
As with the majority of data input records in PSS
E Model Library.
Data records specifying the generator models should have, following the model name, the identifier
of the machine to which the model is being assigned, followed by the ICON data (if applicable) and
CON data in the same order as they appear in the respective model data sheets.
It is to be noted that reactances, H and D are specified on MBASE base as contained in the working
case (refer to Generator Data and Section 11.2.2). In the GENROE, GENROU, GENSAE,
GENSAL, GENDCO and FRECHG models, the value specified for X'' must be identical to the imag-
inary part of ZSORCE as contained in the working case. For the GENCLS and GENTRA models,
the imaginary component of ZSORCE must be identical to the transient reactance, X'. In the
CIMTR1, CIMTR2, CIMTR3 and CIMTR4 models, a single cage induction machine has T'' and X''
set to zero and X' must be identical to the imaginary part of ZSORCE; a double cage machine has
nonzero values for the subtransient data items and X'' must be identical to the imaginary component
of ZSORCE.
Current Compensating Models
Any machine may have a voltage regulator current compensating model specified for it. These
models allow the voltage regulator to sense the voltage either at a remote bus or at a point sepa-
rated from the machine terminals by a specified impedance which must be entered on MBASE
base.
Activity DYRE recognizes the compensating models that are listed in Chapter 2, Compensator
Model Data Sheets of the PSS
E Model Library.
Data records specifying the compensating models should have, following the model name, the iden-
tifier of the machine to which the model is being assigned, followed by the ICON data (if applicable)
and CON data in the same order as they appear in the respective model data sheets.
Stabilizer and Excitation Limiter Models
Any machine for which an appropriate generator/exciter model pair has been specified may have a
power system stabilizer model, a minimum excitation limiter model, and/or a maximum excitation
limiter model specified for it. These units are devices that inject supplementary signals into the
voltage regulator units. Stabilizer signals are usually derived from either generator speed or gener-
ator power in such a way as to improve the damping of generator rotor angle swings. Minimum and
maximum excitation limiters are relatively slow-acting protective devices which limit field voltage,
EFD. The stabilizer model output, and the minimum and maximum excitation limiter model outputs
are accessed as VOTHSG, VUEL and VOEL inputs respectively by the excitation system model.
Siemens Energy, Inc., Power Technologies International 14-5
PSS
E Model
Library.
Data records specifying the stabilizer and excitation limiter models should have, following the model
name, the identifier of the machine to which the model is being assigned, followed by the ICON data
(if applicable) and CON data in the same order as they appear in the respective model data sheets.
In stabilizer models that require a remote bus ICON to be specified, the remote bus ICON must be
specified as zero if a local signal is used.
Excitation System Models
Any machine which is modeled by one of the generator models GENROE, GENROU, GENSAE,
GENSAL, GENDCO, GENTRA, CGEN1 or FRECHG may have an excitation system model speci-
fied for it.
Activity DYRE recognizes the exciter models that are listed in Chapter 6, Excitation System Model
Data Sheets of the PSS
E Model Library.
Data records specifying the excitation system models should have, following the model name, the
identifier of the machine to which the model is being assigned, followed by the ICON data (if appli-
cable) and CON data in the same order as they appear in the respective model data sheets.
Turbine Governor Models
Any machine which is modeled by one of the generator models GENROE, GENROU, GENSAE,
GENSAL, GENDCO, GENTRA, CIMTR1, CIMTR2, CIMTR3, CIMTR4 or CGEN1 may have a
turbine governor model specified for it.
The list of governor models that are recognized by activity DYRE is provided in Chapter 7, Turbine-
Governor Model Data Sheets of the PSS
E Model Library.
For those governor models for which the turbine rating cannot be specified, the turbine governor
data would have to be specified on the base of its generating unit (i.e., on MBASE base).
Data records specifying most of the turbine governor models should have, following the model
name, the identifier of the machine to which the model is being assigned, the ICON data (if appli-
cable), and CON data in the same order as they appear in the respective model data sheets.
For the cross compound models, BUSID and IM specify the high pressure unit. IM is followed by
the bus and machine identifiers of the low pressure unit. The remaining data items are the ICON
data (if applicable) and CON data in the same order as they appear in the respective model data
sheets.
For the IEEE Type 1 models, IEEEG1, TGOV5 and WSIEG1, BUSID and IM specify the machine
at which the model is to be called. If a cross compound is to be modeled, these specify the high
pressure unit, and IM is followed by the bus and machine identifiers of the low pressure unit; other-
wise two data items of zero must be specified following IM.
Dynamic Simulation Activity Descriptions PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-6 Siemens Energy, Inc., Power Technologies International
Turbine Load Controller Models
Any machine which has a turbine governor model may have a turbine load controller model speci-
fied for it. The function of these models is to maintain turbine power at a set value by adjusting the
turbine-governor reference.
The list of turbine load controller models that are recognized by activity DYRE is provided in
Chapter 8, Turbine Load Controller Model Data Sheets of the PSS
E Model Library.
For those governor models for which the turbine rating cannot be specified, the turbine load
controller data would have to be specified on the base of its generating unit (i.e., on MBASE base).
Data records specifying the turbine load controller models should have, following the model name,
the identifier of the machine to which the model is being assigned, the ICON data (if applicable),
and CON data in the same order as they appear in the respective model data sheets.
Load Characteristic Models
Any load in the working case may have a load characteristic model data record specified for it.
The list of load characteristic models that are recognized by activity DYRE is provided in Chapter 9,
Load Characteristic Model Data Sheets of the PSS
E Model Library.
Data records specifying each of the above models should have the form:
BUSID model name IL data list /
where:
Load Relay Models
Any load in the working case may have a load relay model data record specified for it.
The list of load relay models that are recognized by activity DYRE is provided in Chapter 10, Load
Relay Model Data Sheets of the PSS
E Model Library.
Data records specifying each of the above models should have the form:
BUSID model name IL data list /
where:
BUSID Bus number or name for type BL models.
Owner number for type OW models.
Zone number for type ZN models.
Area number for type AR models.
0 for type AL models.
IL Load identifier or - to specify the model for all loads at BUSID.
data list As specified on the model data sheets.
BUSID Bus number or name for type BL models.
Owner number for type OW models.
Zone number for type ZN models.
Area number for type AR models.
0 for type AL models.
Siemens Energy, Inc., Power Technologies International 14-7
PSS
E Model Library.
Data records specifying each of the above models should have the form:
BUSID model name BUSID2 ID RS data list /
where:
The relay slot number (RS) must be either 1 or 2. Up to two models per branch per from bus, or four
models per branch, can be accommodated.
Auxiliary-Signal Models
Activity DYRE recognizes the auxiliary-signal models that are provided in Chapter 12, Auxiliary-
Signal Model Data Sheets of the PSS
E Model Library:
With the exception of models RBKELT and SQBAUT, all other auxiliary-signal models can be asso-
ciated with dc line models (2-terminal dc, multi-terminal dc, VSC dc) and FACTS device models.
RBKELT and SQBAUT can be associated only with 2-terminal dc line models.
Data records for auxiliary-signal models are specified in the form:
BUSID 'model name' DVTYP SGNDX data list /
where:
IL Load identifier or - to specify the model for all loads at BUSID.
data list As specified on the model data sheets.
BUSID Is the branch from bus number or name; this is the end of the line at which the relay
model is placed.
BUSID2 Is the branch to bus number or name.
ID Is the branch circuit identifier.
RS Is the relay slot number.
data list As specified on the model data sheets.
DVTYP Indicates the device type with which the auxiliary-signal is associated, and could be
any of the following:
1 : for two-terminal dc line
2 : for multi-terminal dc line
3 : for VSC dc line
4 : for FACTS device
SGNDX Is the signal injection point number. This is any number 1 through maximum number
of auxiliary-signals that can be associated with the device type under consideration
(refer to Table 3-1 for the maximum number of auxiliary signal injection points, i.e.,
the maximum number of auxiliary-signals that can be attached to each device type).
Dynamic Simulation Activity Descriptions PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-8 Siemens Energy, Inc., Power Technologies International
Each of the above "tableized" auxiliary-signal models calculates the model output and stores it in
the array VAR(L), where L is the starting VAR index for that auxiliary-signal model. Subsequently,
depending on the type of device with which the auxiliary-signal model is associated with, the model
output contained in VAR(L) is then transferred by PSS
E standard arrays,
DC2SIG or DCMSIG or VSCSIG or FCTSIG. The array locations in DC2SIG, DCMSIG, VSCSIG,
and FCTSIG into which VAR(L) is transferred, corresponds to the internal device index, and the
signal index for which the auxiliary-signal model is called.
DC Line Models
DC lines could be one of the following: two-terminal, multi-terminal or VSC dc.
The list of dc two-terminal, multi-terminal, and VSC dc line models recognized by activity DYRE is
provided in Chapter 13, Two-Terminal dc Line Model Data Sheets; Chapter 14, Multi-Terminal dc
Line Model Data Sheets; and Chapter 15, VSC dc Line Model Data Sheets of the PSS
E Model
Library.
Data records for dc line models are specified in the form:
BUSID 'model name' data list /
where:
FACTS Device Model
The list of FACTS device models recognized by activity DYRE is provided in Chapter 16, FACTS
Device Model Data Sheets of the PSS
E Model Library.
Data records for FACTS device models are specified in the form:
BUSID 'model name' data list /
where:
Wind Generator Models
Each in-service wind-machine in the working case must have a wind generator model data record
specified for it. The list of wind generator models that activity DYRE recognizes is provided in
Chapter 17, Generic Wind Generator Model Data Sheets of the PSS
E Model Library.
Data records specifying the wind-generator models should have, following the model name, the
identifier of the machine to which the model is being assigned, followed by the ICON data (if appli-
cable) and CON data in the same order as they appear in the respective model data sheets.
Wind Electrical Control Models
Any wind machine may have an electrical control model specified for it. These models control the
active and reactive power to be delivered to the system. The list of wind electrical control models
recognized by activity DYRE is listed in Chapter 18, Generic Wind Electrical Model Data Sheets of
the PSS
E Model Library.
BUSID Is the dc line name (specified in single quotes).
BUSID Is the FACTS device name (specified in single quotes).
Siemens Energy, Inc., Power Technologies International 14-9
PSS
E Model
Library.
Data records specifying the wind turbine models should have, following the model name, the iden-
tifier of the machine to which the model is being assigned, followed by the ICON data (if applicable)
and CON data in the same order as they appear in the respective model data sheets.
Wind Pitch Control Models
Any wind machine may have a pitch control model specified for it. These models control the blade
pitch angle using the rotor speed and torque command input signals.
Activity DYRE recognizes the pitch control models that are listed in Chapter 20, Generic Wind Pitch
Control Model Data Sheets of the PSS
E Model Library.
Data records specifying the pitch control models should have, following the model name, the iden-
tifier of the machine to which the model is being assigned, followed by the ICON data (if applicable)
and CON data in the same order as they appear in the respective model data sheets.
Switched Shunt Models
Any device that is modeled as a switched shunt in PSS
E Model Library.
Data records specifying switched models should have, following the model name, the ICON data (if
applicable), and CON data in the same order as they appear in the respective model data sheets.
CONEC and CONET Models
The PSS
E model library contains a group of models that are presently called in CONEC and/or
CONET. Some of these models are used to model the dynamic characteristics of equipment, while
others pertain to electric network rather than the dynamic characteristics of the equipment. These
models (called CONEC and CONET models) are listed in Chapter 23, CONEC and CONET Model
Data Sheets of the PSS
E Model Library.
The ICON and CON lists contain the constant data values and are specified in the same order as
they appear in the ICON and CON blocks on the model data sheets.
User-Written Models
In addition to processing data records for most of the models contained in the PSS
E model library,
activity DYRE provides for the processing of records specifying data for user-written models (refer
to Chapter 20 for model writing details and Chapter 18 for information on the PSS
E dynamic simu-
lation structure). For such data records to be handled correctly by activity DYRE:
Dynamic Simulation Activity Descriptions PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-10 Siemens Energy, Inc., Power Technologies International
1. The special formats described below must be used.
2. The models must be written so as to be consistent with the calling sequences assumed
(refer to Section 20.4).
Data records for load characteristic or load relay user-written models must be in the following
format:
BUSID USRLOD IL model name IC IT NI NC NS NV NRI data list /
Data records for line relay user-written models must be in the following format:
BUSID USRREL BUSID2 ID RS model name IC IT NI NC NS NV NRI data list /
Data records for user-written auxiliary-signal models must be specified in the following format:
BUSID USRAUX DVTYP SGNDX model name IC IT NI NC NS NV data list /
Data records for user-written dc line models (two-terminal dc, multi-terminal dc and VSC dc) are
specified in the form:
BUSID USRDCL model name IC IT NI NC NS NV data list /
Data records for user-written FACTS device models are specified in the form:
BUSID USRFCT model name IC IT NI NC NS NV data list /
Data records for user-written switched shunt device models are specified in the form:
BUSID USRSWS model name IC IT NI NC NS NV data list /
Data records for all other types of user-written models must be in the following format:
BUSID USRMDL IM model name IC IT NI NC NS NV data list /
where BUSID, BUSID2, IM, IL, ID, RS, and < model name > are as described at the beginning of
Section 14.1.1, and:
IC Is the user model type code:
0 = Model called from subroutine CONET and not called from subroutine
CONEC.
1 = Generator model.
2 = Current compensating model.
3 = Stabilizer model.
4 = Excitation system model.
5 = Turbine-governor model.
7 = Two-terminal dc line model in PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-12 Siemens Energy, Inc., Power Technologies International
In specifying ICONs, character ICONs (e.g., circuit identifiers) may be specified; they must be
enclosed in single quotes.
The 'model name' is limited to sixteen characters. This string is employed as a subroutine name
within the connection subroutines generated by activity DYRE (refer to Section 14.1.2) so it must
conform to FORTRAN conventions for a subroutine name.
The following paragraphs discuss details specific to various model types. The CALL statements for
these models are generated as defined in Section 20.4.
Machine Related Models
For plant-related model records (i.e., IC values of one through five and nine through eleven), BUSID
and IM designate the bus and machine identifiers respectively. Except as described below, all
machine related models must have a zero specified for IT.
For user-written cross-compound governor model records (i.e., IC values of eleven), BUSID and IM
specify the high-pressure unit. NV is followed by the bus and machine identifiers of the low pressure
unit. The remaining data items are the model constants (NI ICONs followed by NC CONs).
Machine-related user-written models are called at those phases of the dynamic simulation calcula-
tion concerned with the handling of differential equations. Certain generator models such as static
var systems also involve a voltage sensitive current injection during the network balance. For such
models:
1. IC and IT must be specified as one.
2. The model must contain a supplementary ENTRY point with the first character of the model
(SUBROUTINE) name changed to a T.
3. The model is called at its principal entry point for simulation calculations involving the differ-
ential equations, and at its supplementary entry point during the current injection calculation
of the network solution.
The implementation of this type of modeling requirement is referred to as a coordinated call model.
When IC is 24, IT could be 1 or 2:
1 = current injection model, place before IFLAG test in subroutine CONET
2 = metering model, place after IFLAG test in subroutine CONET
NI Is the number of ICONs used by the model (NI < 200).
NC Is the number of CONs used by the model (NC < 500).
NS Is the number of STATEs used by the model.
NV Is the number of VARs used by the model.
NRI Is the number of additional (reserved) ICONs used by the model.
data list Specifies NI ICONs, followed by NC CONs.
Siemens Energy, Inc., Power Technologies International 14-13
PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-14 Siemens Energy, Inc., Power Technologies International
single quotes with which the auxiliary-signal is associated. DVTYP indicates the type of the device
with which the auxiliary-signal is associated (1 for 2-terminal dc line, 2 for multi-terminal dc line, 3
for VSC dc line, 4 for FACTS device). SGNDX is the auxiliary-signal index. This is any number 1
through maximum number of auxiliary-signals that can be associated with the device type under
consideration (refer to Table 3-1 for the maximum number of auxiliary-signals that can be attached
to each device type).
The user-written auxiliary-signal model should calculate the model output and store it in VAR(L),
where L is the starting VAR index for that auxiliary-signal model. Subsequently, depending on the
type of device with which the auxiliary-signal model is associated, the model output contained in
VAR(L) is then transferred by PSS
E simulation model library and which represent generator plant related equipment, load
characteristics, load relays, branch relays, auxiliary signals, dc lines, FACTS device, switched
shunt, and some monitoring functions, and for user supplied models of plant related equipment,
load characteristics, load relays, branch relays, auxiliary signals, dc lines, FACTS device, and
switched shunt models. For all other user supplied models, the association requires a model
subroutine call from one or both the reserved program subroutines: CONEC and CONET (these
may also be referred to, individually or collectively, as the connection subroutines). When they are
required these connection subroutines, containing the appropriate model subroutine references,
are created by activity DYRE and are placed within two resulting files. It is the users responsibility
to supply these subroutines for each dynamic simulation setup. (Refer to Section 18.1 for additional
details on the role of CONEC and CONET in dynamic simulations.)
Activity DYRE performs these major functions as it reads through the Dynamics Model Raw Data
File:
Dynamic Simulation Activity Descriptions PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-16 Siemens Energy, Inc., Power Technologies International
1. It assigns storage locations in the various dynamics data storage arrays for each of the
models referenced (refer to Section 18.1.2).
2. It initializes the constant parameters in these data arrays for each model referenced in the
data file.
3. It creates tables of pointers for programmatic associations of dynamic models with network
equipment where appropriate.
4. It constructs the connection subroutines (refer to Section 18.4).
Activity DYRE requires that the network corresponding to the dynamics data being read is present
in the working case. It further requires that the in-service machines in the working case contain the
proper specification of the machine attributes MBASE, ZSORCE, XTRAN and GENTAP (refer to
Generator Data), and that they be represented as current sources (i.e., with activity CONG having
been executed.
The user specifies the Dynamics Model Raw Data File which contains data records in the form given
in Section 14.1.1.
The user also specifies the files into which activity DYRE is to place the connection subroutines.
Refer to Section 2.6 for the file overwriting conventions used by activity DYRE. If the user does not
provide filenames for either CONEC or CONET files, an image of the corresponding subroutines
CALL statements is written to the users terminal rather than to a file.
After the required files are read into the working case, activity DYRE provides the following
information:
NEXT AVAILABLE ADDRESSES ARE:
CON STATE VAR ICON
nnn nnn nnn nnn
The values < nnn > indicate the next available locations in the corresponding dynamics data arrays.
When PSS
E is started up, these indices are set to one and are subsequently updated by activities
DYRE, CHAN, and CHSB. They may be changed by the user via activity ALTR using the category
of solution parameter changes. These indices are preserved with dynamics working memory as it
is saved and retrieved with activities SNAP and RSTR respectively.
When constructing a new dynamics setup, the normal entry is 1 for each of the starting indices.
When activity DYRE is used in its add models mode (refer to Section 14.1.3), the usual procedure
is to let activity DYRE assign locations in the dynamics data arrays for the models being added
beginning at the next unused slots.
Activity DYRE generates an alarm for any model data record for which either too many, or not
enough, data items have been specified. Upon completing its pass through the Dynamics Model
Raw Data File, activity DYRE builds the connection subroutines and deposits values in locations in
the dynamics data constant arrays.
As it completes each of the model types described above, a summary of the storage locations allo-
cated in the various data storage arrays is printed. A single similar summary is printed for the model
types described in CONEC and CONET Models. These are followed by a summary of the number
of model references read from the Dynamics Model Raw Data File. These tabulations are printed
at the Progress tab.
Siemens Energy, Inc., Power Technologies International 14-17
PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-18 Siemens Energy, Inc., Power Technologies International
14.1.3 Adding Models
Activity DYRE may be operated in an add models mode. The usual procedure in adding models to
an existing (or partially completed) system model is as follows:
1. Initiate PSS
E.
2. Use activity RSTR to restore the Snapshot containing the dynamics data of the existing
system model.
3. Pick up the network model corresponding to the Snapshot accessed in (2).
4. Run activity DYRE,ADD or navigate File > Open > Files of type: Add Dynamics Model Data
(*.dyr) from the GUI menu.
5. Take a Snapshot with activity SNAP.
6. Exit PSS
E in the
standard manner (refer to Sections 4.10 and 18.4.4).
If no additional model calls are generated in the connection subroutine additions files, steps 6
through 8 are not required (see below).
After specifying the appropriate Dynamics Model Raw Data File to activity DYRE in (4) above, the
user enters the names of the files into which activity DYRE is to place any new connection subrou-
tine model calls.
The user should not specify the pair of files containing the versions of these subroutines corre-
sponding to the existing system model; activity DYRE does not append to the specified files but
overwrites the previous contents of existing files. Refer to Section 2.4.1 for the file specification
conventions used by activity DYRE.
The normal response to the request for starting data array indices (refer to Section 14.1.2) is the
default, after which activity DYRE uses the next available locations as contained in the Snapshot
restored in (2) above.
In the add models mode, activity DYRE summarizes the status of the connection subroutines by
printing one of the following messages as explained below.
If the DYRE addition has user models for which compilation is required, and if no model calls were
generated in the connection routines CONEC and CONET, the message generated at the dialog
output device would be:
CONEC & CONET (IF PRESENT) ARE UNCHANGED. COMPILE USER MODELS, AND
CONEC & CONET (IF PRESENT), & CREATE DLL
Siemens Energy, Inc., Power Technologies International 14-19
PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-20 Siemens Energy, Inc., Power Technologies International
Precedence is an issue unique to subsystem models. The data presentation for subsystem models
may involve intersection among the subsystems. The data may contain a presentation for both a
bus-specific model and an area-specific model, and the bus associated with the first model may be
part of the area associated with the second. Therefore a precedence order is provided to accom-
modate subsystem models. The decreasing order of precedence for resolving conflicts is from the
most specific to most general subsystem: bus, owner, zone, area, and all. A model applied to a bus
takes precedence over all conflicting models applied to any other subsystem in which the bus is
located. A model applied to an owner takes precedence over any conflicting model applied to a
zone, area, or all buses.
A precedence order is provided to accommodate conflicts in element identifier as well. A data
record which introduces a subsystem model with a specific element identifier will take precedence
over a subsystem model with a wildcard ('*') identifier.
Models employing programmatic association with network elements may be bypassed. This
includes all models except those connected to the network by subroutine calls within the CONEC
and/or CONET subroutines. When the model is bypassed, its function is excluded from the time
domain simulation without extracting its reference or data from the simulation model. The model
may be restored to an active state through program dialog.
A subsystem model can be bypassed at both the subsystem instance and the element instance.
When a model is bypassed at the subsystem instance the models function is excluded for each
element to which the subsystem model applies. When the subsystem model is bypassed at the
element instance, the models function is excluded for only that element, and the function will be
invoked for all other active elements to which the subsystem model applies.
A bypassed model remains connected to the element. The bypassed model is not superseded by
another active model which could potentially replace it due to precedence. However, if the model is
removed, the next subsystem model in the precedence order automatically connects to the
element. For example, if a Bus Subsystem model with a specific identifier (e.g.'1') were to be
bypassed, another Bus Subsystem model at the same bus with a wildcard (*) identifier does not
replace it. If the element specific model were removed, then the wildcard model applies.
14.1.5 Application Notes
The processing of activity DYRE results in three related but separate sets of data needed in formu-
lating the dynamic system model:
1. Dynamics working memory with its constant data arrays initialized to the model constants
obtained from the data file.
2. A data file containing the FORTRAN subroutine CONEC.
3. A data file containing the FORTRAN subroutine CONET.
After an error-free execution of activity DYRE is completed, and prior to terminating PSS
E, it is
strongly recommended that dynamics working memory be preserved in the form of a Snapshot by
using activity SNAP.
When specifying data for the compensating models (refer to Current Compensating Models), the
user should carefully note the significance of the sign of their data values (refer to the data sheets
in Chapter 2, Compensator Model Data Sheets of the PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-22 Siemens Energy, Inc., Power Technologies International
14.1.6 Error Messages
As it processes the Dynamics Model Raw Data File, activity DYRE generates an alarm for errors
resulting from the conditions listed below. In alarming a data record, the error message block often
includes the first physical line of the offending data record.
1. A model name is encountered which is not recognized. The following error message is
generated:
UNDEFINED MODEL aaaaaa
Activity DYRE ignores the data record and processing continues. In reading Dynamics
Model Raw Data Files prepared for, or generated by, release nineteen or earlier of
PSS
E, data records for the models STAB2 and GAST2 generate an alarm as unde-
fined. These models were replaced by the models STAB2A and GAST2A at PSS
E-
20. For additional details refer to the PSS
E Compatibility
Reference.
2. Too many models of a given type (e.g., two generator models specified for a machine). One
of the following error messages is generated:
DUPLICATE MODEL TYPE: aaaaaa AT BUS nnnn MACHINE n
DUPLICATE MODEL TYPE: aaaaaa AT BUS nnnn LOAD n
DUPLICATE MODEL TYPE: aaaaaa AT AREA nnnn LOAD n
DUPLICATE MODEL TYPE: aaaaaa AT ZONE nnnn LOAD n
DUPLICATE MODEL TYPE: aaaaaa AT OWNER nnnn LOAD n
DUPLICATE MODEL TYPE: aaaaaa FROM BUS nnnn TO BUS nnnn SLOT i
DUPLICATE MODEL TYPE: aaaaaa FOR ALL-TYPE LOAD aa
DUPLICATE MODEL TYPE: aaaaaa WITH SAME SIGNAL INDEX nn
ASSOCIATED WITH 2-TERM DC LINE name
DUPLICATE MODEL TYPE: aaaaaa WITH SAME SIGNAL INDEX nn
ASSOCIATED WITH MULTI-TERM DC LINE name
DUPLICATE MODEL TYPE: aaaaaa WITH SAME SIGNAL INDEX nn
ASSOCIATED WITH VSC DC LINE name
DUPLICATE MODEL TYPE: aaaaaa WITH SAME SIGNAL INDEX nn
ASSOCIATED WITH FACTS DEVICE name
DUPLICATE MODEL TYPE: aaaaaa FOR 2-TERMINAL DC LINE nn
DUPLICATE MODEL TYPE: aaaaaa FOR MULTI-TERMINAL DC LINE name
DUPLICATE MODEL TYPE: aaaaaa FOR VSC DC LINE name
DUPLICATE MODEL TYPE: aaaaaa FOR FACTS DEVICE name
Activity DYRE ignores the data record that generated an alarm (i.e., it uses the data
record previously read) and processing continues.
3. Error in decoding a data record. The standard data input error message is printed followed
by:
RECORD IGNORED
This message is the first physical line of the offending record. In addition to typograph-
ical errors, this error is encountered when the numbers input option is in effect and a
BUSID field on a data record specifies an extended bus name.
4. Error in the specification of the low pressure unit on a data record specifying the cross
compound governor model CRCMGV, IEEEG1, TGOV5 or WSIEG1, the second machine
Siemens Energy, Inc., Power Technologies International 14-23
PSS
E is dimensioned.
8. Too few data items on a record. The following error message is printed followed by a line
indicating that either the record is ignored or that zeros are assumed for the missing data
items:
WARNING: INCOMPLETE DATA RECORD FOR MODEL aaaaaa
9. Too many data items on a record. The following error message is printed followed by the first
physical line of the data record, and processing continues:
EXCESS DATA IGNORED ON RECORD
10. The bus specified on a bus oriented model data record is not in the working case. The
following error message is printed, the record is ignored, and processing continues:
BUS nnnn NOT FOUND
11. Auxiliary-signal models SQBAUT and RBKELT can be used only with two-terminal dc line
models. One of the following error message is printed, the record is ignored, and processing
continues:
AUX. SIGNAL MODEL SQBAUT CAN BE USED ONLY WITH 2-TERM DC LINES
AUX. SIGNAL MODEL RBKELT CAN BE USED ONLY WITH 2-TERM DC LINES
12. The device type (DVTYP) in the auxiliary-signal data record is invalid. This error message
could be due to the following reason:
- DVTYP is a value other than 1 through 4.
The following error message is printed, the record is ignored, and processing contin-
ues:
INVALID DEVICE TYPE
13. The signal index (SGNDX) in the auxiliary-signal data record is invalid. This error occurs if
the SGNDX value specified is less than or equal to zero, or if it is greater than the maximum
number of auxiliary signals that can be associated with the device type.
The following error message is printed, the record is ignored, and processing contin-
ues:
INVALID AUX. SIGNAL INDEX FOR THE DEVICE
Dynamic Simulation Activity Descriptions PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-24 Siemens Energy, Inc., Power Technologies International
14. An invalid two-terminal dc line name is specified either in the data record for a two-terminal
dc line model, or in the auxiliary-signal data record that is associated with a two-terminal dc
line. The following error message is printed, the record is ignored, and processing
continues:
INVALID 2-TERMINAL DC LINE
15. An invalid multi-terminal dc line name is specified either in the data record for a multi-
terminal dc line model, or in the auxiliary-signal data record that is associated with a multi-
terminal dc line. The following error message is printed, the record is ignored, and
processing continues:
INVALID MULTI-TERMINAL DC LINE
16. An invalid VSC dc line name is specified either in the data record for a VSC dc line model,
or in the auxiliary-signal data record that is associated with a VSC dc line. The following error
message is printed, the record is ignored, and processing continues:
INVALID VSC DC LINE NAME
17. An invalid FACTS device is specified either in the data record for a FACTS device model, or
in the auxiliary-signal data record that is associated with a FACTS device. The following
error message is printed, the record is ignored, and processing continues:
INVALID FACTS DEVICE
18. An invalid user model type code (IC) is specified for a user-written model. The following error
message is printed, the record is ignored, and processing continues:
INVALID USER MODEL TYPE CODE: nnn
19. An invalid user model network code (IT) is specified for a user-written model. The following
error message is printed, the record is ignored, and processing continues:
INVALID USER MODEL NETWORK CODE: nnn
20. An invalid combination of model type and network codes is specified for a user-written
model. The following error message is printed, the record is ignored, and processing
continues:
INVALID USER MODEL TYPE/NETWORK CODE COMBINATION
21. Less than zero or more than five hundred array locations in the CON, STATE or VAR array,
or less than zero or more than two hundred array locations in the ICON array, specified for
a user-written model. The following error message is printed, the record is ignored, and
processing continues:
INVALID NUMBER OF ARRAY LOCATIONS: nnn
22. The same user-written model is given different characteristics (IC through NV or NRI) on two
user model data records. The following error message is printed, the record is ignored, and
processing continues:
INCONSISTENT MODEL DEFINITIONS FOR SAME USER MODEL
Siemens Energy, Inc., Power Technologies International 14-25
PSS
E is dimensioned. The
following error message is printed and activity DYRE is terminated:
MACHINE MODEL CONNECTION TABLES FULL--USE DYCH TO PACK TABLES
The Remove unconnected models and Pack models functions of the Dynamics>Model
maintenance menu entry for Plant model may be used to eliminate slots in these
tables for machines not in the working case. Refer to PSS
E is dimensioned.
The following error message is printed and activity DYRE is terminated:
LOAD MODEL CONNECTION TABLES FULL--USE PACK LOAD MODELS FUNCTION
The Remove unconnected models and Pack models functions of the Dynamics>Model
maintenance menu entry for Load model may be used to eliminate slots in these
tables for loads not in the working case. Refer to PSS
E is dimensioned.
The following error message is printed and activity DYRE is terminated:
LINE RELAY CONNECTION TABLES FULL--USE PACK LINE RELAY MODELS FUNCTION
The Remove unconnected models and Pack models functions of the Dynamics>Model
maintenance menu entry for Line relay model may be used to eliminate slots in these
tables for branches not in the working case. Refer to PSS
E 32.0
Reading Dynamics Model Data Program Operation Manual
14-26 Siemens Energy, Inc., Power Technologies International
29. In the add models mode, the number of entries in the dc line connection tables exceeds the
number of table entries for which PSS
E 32.0
Assigning Simulation Variables to Output Channels Program Operation Manual
14-28 Siemens Energy, Inc., Power Technologies International
14.2 Assigning Simulation Variables to Output Channels
Activity CHAN
The output channel selection activity CHAN enables the user to select simulation variables which
are to be monitored during dynamic simulation runs. These quantities may be tabulated and/or
placed into a Channel Output File at regular intervals during a simulation run (refer to activity RUN).
The simulation results, as contained in the Channel Output File, are able to be processed by the
PSS
E plot package following completion of the simulation. Up to six channels can be defined for
interactive plotting during the simulation run.
14.2.1 Operation of Activity CHAN
The user identifies quantities to be placed into output channels and activity CHAN places their
memory addresses and alphanumeric identifiers into the PSS
E 32.0
Assigning Simulation Variables to Output Channels Program Operation Manual
14-30 Siemens Energy, Inc., Power Technologies International
*Notes:
xx Contains the bus number, the extended bus name, and the machine identifier
yy Contains the bus number and the extended bus name.
zz Contains the from bus number, to bus number or, for a three-winding transformer, the
string 3W: followed by the transformer name, and the circuit identifier.
nn Is the VAR or STATE index.
vv Contains the bus number, load identifier, and the extended bus name
(1)
Valid for synchronous machine models only.
(2)
From activity CHSB, SUBS.
When selecting branches for monitoring, up to three buses may be specified. Nontransformer
branches and two-winding transformers are specified by making no entry in the third bus field. For
three-winding transformers, all three buses must be specified. Branch quantities are calculated at
the end of the branch corresponding to the first bus specified. Note that the following categories
generate two output channel assignments for each element selected for monitoring:
Voltage & Angle
Flow (P&Q)
Relay2 (R & X)
Machine apparent impedance
Turbine Load Controller
reference
pu Bus, machine id LCRF xx
Wind velocity pu Bus, wind machine id WVEL xx
Wind turbine speed pu Bus, wind machine id WTSP xx
Wind Pitch degree Bus, wind machine id WPCH xx
Wind aerodynamic torque pu Bus, wind machine id WAET xx
Wind rotor voltage pu Bus, wind machine id WRTV xx
Wind rotor current pu Bus, wind machine id WRTI xx
Wind real power command from
electrical control
pu Bus, wind machine id WPCM xx
WInd reactive power command
from electrical control
pu Bus, wind machine id WQCM xx
Wind Auxiliary control output pu Bus, wind machine id WAUX xx
SUBSYSTEM TOTALS(2) MVA Subsystem number PMECH subsystem
PELEC subsystem
PACCL subsystem
PLOAD subsystem
PE-PL subsystem
Table 14-2. Activity CHAN Summary (Cont.)
Quantity Units Selected By Default Identifier*
Siemens Energy, Inc., Power Technologies International 14-31
PSS
E 32.0
Assigning Simulation Variables to Output Channels Program Operation Manual
14-32 Siemens Energy, Inc., Power Technologies International
by a group of network monitoring models which calculate certain network quantities and place them
into specified locations in the VAR array.
Thus, when activity CHAN is programmed to place bus voltages, branch flows, branch apparent
impedances, machine currents and machine apparent impedances into output channels, it takes
the following steps:
1. It allocates positions in the ICON array and sets these elements to the values required to
designate the bus, branch or machine to be monitored.
2. It allocates positions in the VAR array which are to contain the monitored quantities.
3. It generates entries in the CHAN monitoring model tables for the appropriate model call
(VOLMAG, FLOW1, FLOW3, RELAY2, RELAY3, GENTMC or GENTMZ).
4. As with the other data categories, it establishes the appropriate IPRINT and IDENT array
entries.
During dynamic simulations, model calls corresponding to the model references contained in the
CHAN monitoring model tables are issued each time step at the completion of the network balance.
Thus, after being selected by activity CHAN, these network quantities are automatically calculated
during dynamic simulation runs and placed into output channels.
As activity CHAN assigns each selected simulation quantity to an output channel, it makes a corre-
sponding entry in a set of channel descriptor arrays. These arrays describe the type of quantity
assigned to the channel, and its location in the network in terms of external bus numbers and
machine, load and circuit identifiers (or in a dynamics data array in the case of categories nineteen
and twenty). These arrays are also used in describing the content of each channel in activities ALTR
and DLST.
This information is also used to reconcile differences in the PSS
E 32.0
Saving Dynamics Working Memory in a Binary File Program Operation Manual
14-34 Siemens Energy, Inc., Power Technologies International
14.3 Saving Dynamics Working Memory in a Binary File
Activity SNAP
The snapshot activity SNAP preserves the contents of dynamics working memory in a user speci-
fied Snapshot File. PSS
E GUI Users Guide, Section 20.6, Saving Dynamics Working Memory in a Binary FIle
PSS
E 32.0
Restoring Dynamics Working Memory from a Binary Snapshot File Program Operation Manual
14-36 Siemens Energy, Inc., Power Technologies International
14.4 Restoring Dynamics Working Memory from a Binary Snap-
shot File
Activity RSTR
The snapshot retrieval activity RSTR restores the dynamics data arrays contained in the specified
Snapshot File into dynamics working memory. The contents of working memory are overwritten
while the contents of the specified Snapshot File are unchanged.
The user specifies the name of the file in which the Snapshot is located. If an asterisk ( - ) is spec-
ified as the name of the Snapshot file, the last Snapshot File accessed by either activity RSTR or
activity SNAP during the current session of PSS
E, an error
message is printed.
If the Snapshot exceeds the capacity limits of the size level of PSS
E is
normally not able to be read by earlier releases of the program.
In restoring the output channel specification data, activity RSTR automatically updates the channel
addresses if the Snapshot was taken in a version of PSS
E activities is:
1. Enter PSS
E.
2. Restore the dynamics data with the activity command rstr,temp.snp.
3. Pick up the electrical network using the command case:
case,temp.cnv
4. Proceed with the simulation as if it were not interrupted (activities RUN or ALTR if, before
continuing with the simulation, changes are to be made to the system condition as restored
into memory).
The name of the simulation output file, case1.out in this example, is retained in the Snapshot along
with a file position pointer for the output file. Thus, when restarting from an intermediate point Snap-
shot, the output from the continuation of the run is appended onto the output contained in the output
file, and so the output file should not be changed. It should not have been used for any other
purpose (except for examination with the channel output file processing program) after the simula-
tion was halted and the Snapshot taken.
When the Snapshot contains an initial condition (i.e., it was written in activity STRT), the user does
not need to re-execute activity STRT. However, the user should check, with activity ALTR, that the
simulation output file, as specified in the Snapshot, is the desired output file. If not, an output file
may be established by specifying the appropriate filename in activity ALTR.
Dynamic Simulation Activity Descriptions PSS
E 32.0
Restoring Dynamics Working Memory from a Binary Snapshot File Program Operation Manual
14-38 Siemens Energy, Inc., Power Technologies International
In this situation, it is still advisable to execute activity STRT before proceeding with the simulation
because this allows for:
1. A cross check of dynamics and network data to ensure proper correspondence of the Snap-
shot and Saved Case Files.
2. Specifying a new simulation output file and having it initialized with the output channel head-
ings without having to go through activity ALTR.
14.4.2 Application Notes
If implementing the supplemental file for STAB2A / GAST2A models optionally constructed by
activity RSTR, note that GAST2A requires one more data item than did GAST2. The user should
edit the data file to add the value of T
C
to each GAST2A data record. The STAB2A data records
may be used without change.
Additional Information
PSS
E-26 or Earlier
Activity SRRS
The Dynamics Snapshot Raw Data File retrieval activity SRRS restores the dynamics data arrays
contained in the specified Dynamics Snapshot Raw Data File into dynamics working memory. The
contents of working memory are overwritten while the contents of the specified Snapshot File are
unchanged. Source snapshots could only be created prior to PSS
E-27.
The user specifies the name of the file in which the Snapshot is located. If no file is specified, or a
file system error condition is encountered in opening the designated file, or the specified file is not
in Source Form Snapshot File format, an appropriate error message is displayed.
If the number of CONs, ICONs or output channels contained in the Snapshot File exceeds the
capacity limits of the size level of PSS
E 32.0
Restoring Dynamics Working Memory from a Snapshot File Created in PSS
E-27.
Activity SRRS requires that the network corresponding to the Source Form Snapshot File to be read
be present in the working case at the time activity SRRS is selected.
In restoring the output channel specification data, activity SRRS automatically updates the channel
addresses if the Snapshot was taken in a version of PSS
E-26 or
Earlier
Siemens Energy, Inc., Power Technologies International 14-41
PSS
E GUI Users Guide, Section 20.8, Modifying Data in Dynamics Working Memory
PSS
E 32.0
Modifying Dynamics Model Pointer Tables Program Operation Manual
14-42 Siemens Energy, Inc., Power Technologies International
14.7 Modifying Dynamics Model Pointer Tables
Activity DYCH
The table driven data table maintenance activity DYCH allows the user to interrogate and modify
the data array entries used in associating plant related equipment models with machines repre-
sented in the working case.
Activity DYCH first displays table utilization, the number of current entries and the maximum
allowble number of entries, for the following dynamic tables:
A function selector provides access to the tables. Some selections may be limited to specific
models: load, plant, wind, relay, auxiliary signal, FACTS device, dc line, or switched shunt models.
Run Activity DYCH - GUI
Dynamics>Model maintenance
[Model Maintenance]
Run Line Mode Activity DYCH - CLI
ACTIVITY?
>>DYCH
Interrupt Control Codes
None
Table 14-3. Dynamic Tables
Table Description
Model Connection
Table
Each entry is associated with a specific machine. Normally, there are as many entries
in this table as there are machines in the working case. However, when the working
case differs topologically from that which was present when the simulation model
data was read into PSS
E 32.0
Modifying Dynamics Model Pointer Tables Program Operation Manual
14-44 Siemens Energy, Inc., Power Technologies International
14.7.6 Consistency Check
The consistency checking function loops through all machines in the working case and generates
an alarm for any invalid model combinations. This report is in ascending bus number order when
the numbers output option is in effect, and in alphabetical bus name order using the names option.
For any alarm messages printed by activity DYCH for a given machine, a heading line identifies the
bus and machine being processed. The following conditions generate an alarm:
1. No generator model specified for a machine. The following error message is printed:
NO GENERATOR MODEL. MACHINE STATUS IS IN (or OUT)
The remaining model combination checks in (2) through (12) below are bypassed. In
executing dynamic simulation calculations, all in-service machines must have an active
generator model assigned to them.
2. The generator model reference is bypassed (refer to Section 14.7.8). The following
message is printed:
GENERATOR MODEL BYPASSED. MACHINE STATUS IS IN (or OUT)
The remaining model combination checks in (3) through (12) below are bypassed. In
executing dynamic simulation calculations, all in-service machines must have an active
generator model assigned to them.
3. At a machine with active generator and exciter models (i.e., neither model is bypassed; refer
to Section 14.7.8), the generator model does not allow an excitation system model. The
following error message is printed:
EXCITER MODEL NOT ALLOWED WITH GENERATOR MODEL name
An excitation system is not permitted in combination with the classical generator model
GENCLS, with the static shunt compensator models CSVGN1, CSVGN3, CSVGN4,
CSVGN5 and CSVGN6, with the induction machine models CIMTR1, CIMTR2,
CIMTR3 and CIMTR4, with the DSMES model CDSMS1, or with CBEST, CSMEST
and CSTATT models.
4. At a machine with active generator and stabilizer models, the generator model does not
allow a stabilizer model. The following error message is printed:
STABILIZER MODEL NOT ALLOWED WITH GENERATOR MODEL name
A stabilizer model is not permitted in conjunction with the classical generator model
GENCLS, with the induction machine models CIMTR1, CIMTR2, CIMTR3 and
CIMTR4, with the DSMES model CDSMS1, or with CBEST, CSMEST and CSTATT
models.
5. At a machine with active generator and stabilizer models, a power sensitive stabilizer model
is used in combination with a static var system model. The following error message is
printed:
STABILIZER MODEL name NOT ALLOWED WITH SVS MODEL name
The stabilizer models STAB2A, STAB3, STAB4, STABNI, IVOST, PTIST1 and PTIST3
are not permitted as supplementary signal models for the static shunt compensator
models CSVGN1, CSVGN3, CSVGN4, CSVGN5 and CSVGN6; the STAB1, IEEEST,
Siemens Energy, Inc., Power Technologies International 14-45
PSS
E 32.0
Modifying Dynamics Model Pointer Tables Program Operation Manual
14-46 Siemens Energy, Inc., Power Technologies International
12. At a machine with active generator and turbine-governor models, the torsional shaft model
SHAF25 is used in combination with a generator model other than GENDCO. The following
error message is printed:
SHAF25 MODEL REQUIRES GENDCO GENERATOR MODEL
13. One machine of an active two-machine PSS
E 32.0
Modifying Dynamics Model Pointer Tables Program Operation Manual
14-48 Siemens Energy, Inc., Power Technologies International
14.7.11 Remove Unused CHAN Models
The unused activity CHAN model removal function deletes network monitoring references for which
the monitored element is not contained in the working case. Each deleted model reference is listed
using the same format as in the CHAN model listing function (refer to Section 14.7.10). The CHAN
monitoring model table is then packed so as to remove gaps in the numeric sequence.
Note that, while deleted CHAN model table entries are available to subsequent executions of activ-
ities CHAN and CHSB, the ICON, VAR and output channel entries which are released are not
automatically made available for reuse.
Additional Information
PSS
E GUI Users Guide, Section 20.9, Modifying Dynamics Model Pointer Tables
PSS
E-31, mode switching is not apparent to the user and is retained only for
backwards compatibility.
The power flow link activity LOFL allows the user to execute any power flow activity after having
been operating in dynamics mode.
Activity LOFL is used primarily to:
1. Set up the working case to correspond to the starting condition for a dynamic simulation run.
The activity sequence to be used to set up the initial condition power flow case is:
a. Link to Power Flow Activities from Dynamic Simulation (LOFL)
b. Retrieve a Power Flow Saved Case File (CASE) <file>
c. Return to Dynamic Simulation (RTRN)
where <file> is the name of the Saved Case File containing the initial condition converted
power flow case (refer to Section 18.3).
2. Allow examination of the network conditions existing at any instant during the system distur-
bance being simulated. When run during a state-space or extended term dynamic
simulation calculation, activity LOFL sets the plant and machine power output arrays in the
working case to correspond to those contained in the dynamics data arrays PELEC and
QELEC. Thus, the machine powers at that point in the simulation will be recognized in any
power flow reporting activities which are executed while the power flow linkage is in effect.
When examining network conditions during a dynamics run, any of the power flow reporting
activities may be used. However, these activities, in particular activities such as POUT and
LOUT, do not have a knowledge of any load-related models or other non-plant boundary
condition models that might be active in the simulation; they only recognize the standard
power flow load characteristics (refer to Section 6.3.13). Thus, if network frequency depen-
dence, algebraic load models such as IEELAR, or equipment such as saturable reactors
are being modeled, mismatches will occur at the buses involved. These mismatches repre-
sent the power variation due to these models at the present instant of the simulation.
When examining network conditions during a dynamics run, the user should exercise
caution in executing any power flow activity which modifies the working case unless a
system disturbance or re-initialization of the dynamic simulation is intended. Reporting
activities may be executed without risk of disturbing the dynamic simulation; all other activ-
Run Line Mode Activity LOFL - CLI
ACTIVITY?
>>LOFL
Interrupt Control Codes
None
Dynamic Simulation Activity Descriptions PSS
E 32.0
Linking to Power Flow Activities from Dynamic Simulation Program Operation Manual
14-50 Siemens Energy, Inc., Power Technologies International
ities, particularly activities CASE, CHNG, and all other activities which affect the content of
the working case, should be used with great care during a simulation run.
While the power flow linkage is in effect, dynamics working memory is preserved.
Activity LOFL itself is not sensitive to any interrupt control code options. However, any power flow
activity run while the power flow linkage is in effect is sensitive to the same interrupt control code to
which it responds in normal power flow work.
Additional Information
PSS
E 32.0
Initializing Models for State-Space Simulation Program Operation Manual
14-52 Siemens Energy, Inc., Power Technologies International
The source current (ISORCE) of any such machine is set to zero. The presence of any such
machines renders the initial condition invalid, and activity RUN will not allow itself to be executed
following such an initialization.
Similarly, any two-terminal, multi-terminal, or VSC dc line, any FACTS device, or any switched shunt
device that is under continuous control which is in-service in the working case but which does not
have a dynamic table model assigned to it generates an alarm with one of the following error
messages:
NO ACTIVE TABLE MODEL CALL FOR TWO-TERMINAL DC LINE "name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
NO ACTIVE TABLE MODEL CALL FOR MULTI-TERMINAL DC LINE "name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
NO ACTIVE TABLE MODEL CALL FOR VSC DC LINE "name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
NO ACTIVE TABLE MODEL CALL FOR FACTS DEVICE "name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
NO ACTIVE TABLE MODEL CALL FOR SWITCHED SHUNT AT BUS "bus name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
During the model initialization process, any model variable which is initialized beyond its prescribed
limits (e.g., the voltage regulator output, STATE(K+1), of the IEEE type one excitation system
model, IEEET1) is alarmed with a message of the form:
name AT BUS nnnn MACHINE i INITIALIZED OUT OF LIMITS
where < name > is the model name (e.g., IEEET1), < nnnn > is the bus number, and < i > is the
machine identifier of the model containing the out-of-limits variable. The user should resolve any
such error conditions before running a simulation.
Activity STRT then prints, at the progress report output device, the case heading followed by the
message:
INITIAL CONDITION LOAD FLOW USED n ITERATIONS
A value of < n > greater than one usually (but not always) indicates some sort of modeling error.
Similarly, any two-terminal, multi-terminal, or VSC dc line, any FACTS device, or any switched shunt
device that is under continuous control which is in-service in the working case but which does not
have a dynamic table model assigned to it generates an alarm. The presence of any such dc line,
FACTS or switched shunt device could indicate one of the following:
A table model was assigned to the dc line, FACTS device or the switched shunt, but
the model was later removed. When this condition is detected during activity STRT,
activity RUN will not allow itself to be executed for dc lines and FACTS devices. In the
case of switched shunts, RUN will still be allowed, because the simulation will use the
power flow value of shunt in the admittance matrix.
No table model was ever assigned to the dc line, FACTS, or the switched shunt device,
or that the model assigned is a CONEC and CONET called model. When this condition
is detected during activity STRT, activity RUN will allow itself to be executed.
Siemens Energy, Inc., Power Technologies International 14-53
PSS
E 32.0
Initializing Models for State-Space Simulation Program Operation Manual
14-54 Siemens Energy, Inc., Power Technologies International
ciated are identified. For STATEs that generated an alarm that are assigned to dc line models, the
model and dc line are identified. For STATEs that generated an alarm that are assigned to FACTS
device models, the model and FACTS device are identified. For STATEs that generated an alarm
that are assigned to dc line models, the model and dc line are identified. For STATEs that generated
an alarm that are assigned to switched shunt models, the model and switched shunt device are
identified.
In each case, the ac bus is also identified. In the case of machines, loads, and switched shunts, this
will be the ac bus at which the machine, load or the switched shunt are connected; for two-terminal
dc lines, VSC dc lines, as well as for auxiliary signals attached to these devices, this is the rectifier
ac bus; for multi-terminal dc lines and for auxiliary signals attached to multi-terminal dc lines, this
will be the ac bus associated with converter number one; for FACTS devices and for auxiliary
signals attached to FACTS devices this will be the sending end ac bus.
If no nonzero STATEs are found, activity STRT outputs a message. The absence of suspect initial
conditions generally (though not always) indicates a valid steady state. Conversely, the presence
of initial condition alarms usually indicates some error in setup.
The same types of procedural errors which cause the initial network solution to use more than one
iteration may also result in nonsteady STATEs. In addition, the following situations may cause these
errors:
1. Model variables initialized out of limits. When this occurs, the STATE variable downstream
of the limit violation may also show some perturbation.
2. STATE variables characterized by a high gain and a short time constant. This often occurs
in the voltage regulator transfer function (e.g., a gain of four hundred and a time constant of
0.05 seconds). This can usually be accepted if the value of the derivative is small relative to
the value of the STATE (say, two or three percent).
3. Improperly specified data (e.g., zero time constants where they are not allowed, unrealistic
limits, etc.).
The user specifies the name of the Channel Output File to be used in the subsequent dynamic simu-
lation run. If no filename is specified in response to the above instruction, the writing of the output
channel variable values to a file is suppressed during the simulation run.
The user must specify a Dynamics Snapshot Data File to preserve the initial system condition, as
contained in the dynamics data arrays. If no filename is specified, activity STRT is terminated. If a
Snapshot File name is specified, a Snapshot is taken prior to terminating activity STRT.
Refer to Section 2.4.1 for the file specification conventions used by activity STRT.
The default time step in PSS
E 32.0
Performing State-Space Simulation in Time Steps Program Operation Manual
14-56 Siemens Energy, Inc., Power Technologies International
14.10 Performing State-Space Simulation in Time Steps
Activity RUN
The state-space time simulation activity RUN sequences through time solving the systems differ-
ential equations and the electrical network at each time step. When run, activity RUN generates an
alarm and terminates if activity STRT had not previously been successfully executed or if genera-
tors are not converted.
The user specifies the following simulation options:
Run Activity RUN - GUI
Dynamics>Simulation>Perform simulation (STRT/RUN)
[Perform Dynamic Simulation]
Run Line Mode Activity RUN - CLI
ACTIVITY?
>>RUN
AT TIME = 0.017 ENTER TPAUSE, NPRT, NPLT, CRTPLT:
>>
Interrupt Control Codes
AB, CM, NC, MO, CH, TI
TPAUSE Run to n.nnnn secs : the value of simulated TIME at which the simulation activity is to
be terminated.
Activity RUN steps through time simulating the system, starting at the present value of simu-
lation TIME, until TIME > TPAUSE.
NPRT Print every <n> time steps: integer value defining the interval, in units of the number of
simulation time steps, between the recording of output channel values. This setting
is recorded and becomes the initial value the next time RUN is run.
The values of the first NCHAN output channel variables are written to the Progress tab
every NPRT time steps. They are printed for the present value of TIME, every NPRT time
steps thereafter, and for TIME = TPAUSE. If NPRT is entered as zero, the tabulation of output
channel values is bypassed.
NPLT Write every < n > time steps: integer value defining the interval, in units of the number
of simulation time steps, between the recording of output channel values. This
setting is recorded and becomes the initial value the next time RUN is run.
The values of the first NCHAN output channel variables are written to the Channel Output
File every NPLT time steps. They are written to the file for the present value of TIME, every
NPLT time steps thereafter, and for TIME = TPAUSE. If NPLT is entered as zero (or one),
channel values are written to the output file at the completion of each time step. NPLT has
significance only if a channel output file has been specified either in activities STRT or ALTR.
Siemens Energy, Inc., Power Technologies International 14-57
PSS
E
is operating in its Response File mode, all active Response Files are closed and subsequent
user commands are taken from the users terminal.
CM Print the network solution convergence monitor.
NC Suppress network convergence monitor when the CM suffix was specified in selecting activity
RUN.
MO Print the induction motor local iteration convergence monitor.
CH Print the output channel values at each time step. The value of NPRT which was entered at
the time activity RUN was run is overridden while this option is in effect. When this option is
cleared, the original value of NPRT is restored and the next printing of channels occurs NPRT
time steps from the TIME of the clearing of the option.
TI Print the value of simulation TIME at the users terminal.
Dynamic Simulation Activity Descriptions PSS
E 32.0
Performing State-Space Simulation in Time Steps Program Operation Manual
14-58 Siemens Energy, Inc., Power Technologies International
14.10.1 Application Notes
When setting up a new system model, it is good practice, after a clean run of activity STRT is
obtained, to execute activity RUN for some period of simulation TIME without applying any distur-
bances. This can often reveal time constants which are too small in relation to the simulation time
step, DELT, or other modeling errors. Another useful test is to initiate some system movement with
a minor disturbance and execute the simulation until a new steady state is reached. This might be,
for example, the shedding of a small amount of load, the tripping of a small unit, or the tripping of a
lightly loaded branch.
Activity STRT sets the output control variables NPRT and NPLT to one, and CRTPLT to zero.
On the first subsequent execution of activity RUN, these values are the defaults for these variables.
On following executions of activity RUN, these variables default to the values specified on the
previous execution of activity RUN.
Whenever the value of simulation TIME reaches the time specified for TPAUSE, the time derivative
and network solution calculations are performed with a flag set to inform the simulation that this is
a t
calculation. For any of the channel output options which are active, the appropriate output is
generated regardless of whether the present time step is a print or plot time step as determined by
the variables NPRT, NPLT and CRTPLT. When activity RUN is reentered, with perhaps some
switching operation having been specified, the time step is repeated as a t
+
calculation. Appropriate
channel output is performed at the completion of the time step as determined by the new specifica-
tion of the output control variables. This applies both for the case in which activity RUN has
advanced TIME to the value specified for TPAUSE and when interrupted by the user.
There are several PSS
E is being executed
from a command file with PSS
E host computers.
If the network solution fails to reach its tolerance in the prescribed number of iterations, an alarm is
printed and the simulation continues as though convergence had been achieved. Refer to
Section 18.7 for additional details.
Siemens Energy, Inc., Power Technologies International 14-59
PSS
E 32.0
Initializing Excitation System Models Program Operation Manual
14-60 Siemens Energy, Inc., Power Technologies International
14.11 Initializing Excitation System Models
Activity ESTR
The excitation system performance initialization activity ESTR initializes the dynamic models in
preparation for excitation system performance checking. Activity ESTR is used in conjunction with
activity ERUN to verify excitation system data by simulating the step response of excitation systems
in isolation. (Section 18.5 contains details on the use of this pair of activities.)
Activities ESTR and ERUN, then, are special versions of activity STRT and RUN respectively which
are used in verifying excitation system data. As such, their operating characteristics are similar to
those of activities STRT and RUN.
The user may specify a single bus for processing. Activity ESTR (and the subsequent execution of
activity ERUN) then tests the excitation system response of all machines at the specified bus having
a connected excitation system model. Otherwise, all machines with connected exciter models are
tested.
Following the initialization calculation, activity ESTR prints the case heading followed by the number
of iterations used to calculate the initial power flow. This is followed by the machine initial conditions
summary for all machines being tested in a form identical to that of activity STRT.
The user must specify the name of the Channel Output File to be used in the subsequent exciter
test simulation. If no filename is specified in response to the above instruction, the writing of the
output channel variable values to a file is suppressed during the simulation.
Activity ESTR overrides the user specified set of main output channel assignments (refer to
Section 18.6.1) with a set of channels suitable for excitation system testing and sets all CRT plot
channel selections (refer to Section 18.6.3) to zero. Therefore, activity ESTR does not enable the
user to take an optional Snapshot as does activity STRT. In fact, the user should never overwrite
the main simulation Snapshot File following execution of activity ESTR because its execution
destroys the user specified output channel assignments.
When using line mode, two separate step response tests may be simulated: a response ratio test,
and an open circuit test with a step of the voltage regulator setpoint.
Activity ESTR may be terminated by entering the AB interrupt control code.
Run Activity ESTR - GUI
Dynamics>Simulation>Perform exciter simulation (ESTR/ERUN)
[Perform Exciter Simulation Test]
Run Line Mode Activity ESTR - CLI
ACTIVITY?
>>ESTR
ENTER 0 FOR RESPONSE RATIO TEST
1 FOR OPEN CIRCUIT SETPOINT STEP TEST:
>>
Interrupt Control Codes
AB
Siemens Energy, Inc., Power Technologies International 14-61
PSS
E 32.0
Performing Exciter Simulation in Time Steps Program Operation Manual
14-62 Siemens Energy, Inc., Power Technologies International
14.12 Performing Exciter Simulation in Time Steps
Activity ERUN
The excitation system performance checking activity ERUN simulates the step response of excita-
tion systems in isolation. Activity ERUN performs the test selected in the previous execution of
activity ESTR; the selection of activity ERUN must, therefore, be preceded by activity ESTR.
The user specifies the simulation options TPAUSE, NPRT, NPLT, CRTPLT as in activity RUN. Re-
entering these parameters is necessary because the required activity ESTR has overridden
channel assignments. Recall that activity ESTR overrides the user selected output channel assign-
ments with channel values appropriate for the excitation system response tests and that it sets CRT
plot channel selections to zero. Thus, if the terminal plot option is to be selected in activity ERUN
(i.e., CRTPLT is to be specified as nonzero), the user must reestablish the CRT plot channels and
scales to correspond to the desired quantities (refer to Section 18.6). This must be done after
execution of activity ESTR.
If the value specified for TPAUSE is less than the current value of simulation TIME, activity ERUN
is terminated.
If a Channel Output File has been opened (in the most recent execution of activity ESTR or subse-
quently via activity ALTR), the filename is displayed in a message.
The simulation starts at the present value of simulation TIME.
Activity ERUN responds to the following interrupt control codes:
Run Activity ERUN - GUI
Dynamics>Simulation>Perform exciter simulation (ESTR/ERUN)
[Perform Exciter Simulation Test]
Run Line Mode Activity ERUN - CLI
ACTIVITY?
>>ERUN
AT TIME = 0.000 ENTER TPAUSE, NPRT, NPLT, CRTPLT
>>
Interrupt Control Codes
AB, CH, TI
AB Force a pause by setting TPAUSE to the current value of simulation TIME. This overrides the
value of TPAUSE which was specified at the time activity ERUN was run. In addition, if
PSS
E is operating in its Response File mode, all active Response Files are closed and
subsequent user commands are taken from the users terminal.
CH Print the output channel values at each time step. The value of NPRT which was entered at
the time activity ERUN was run is overridden while this option is in effect. When this option is
cleared, the original value of NPRT is restored and the next printing of channels occurs NPRT
time steps from the TIME of the clearing of the option.
TI Print the value of simulation TIME at the users terminal.
Siemens Energy, Inc., Power Technologies International 14-63
PSS
E 32.0
Performing Exciter Simulation in Time Steps Program Operation Manual
14-64 Siemens Energy, Inc., Power Technologies International
14.12.3 Application Notes
The procedure in simulating the excitation system response tests follows that used in running
conventional state-space dynamic simulations. Instead of using activities STRT and RUN after the
data has been brought into memory, activities ESTR and ERUN are used.
The response tests calculate the excitation system response of either all generating units in the
system with connected excitation system models, or all machines at a bus (designated during
activity ESTR initialization of a single bus) with connected exciter models. Because machines are
operating in isolation, no network solution is required in the simulation. Furthermore, only the gener-
ator and excitation system models are active in these simulations; all other models perform no
calculations. Therefore, these simulations require substantially less computer time than complete
system simulations.
The typical sequencing of PSS
E 32.0
Initializing Turbine Governor Models Program Operation Manual
14-66 Siemens Energy, Inc., Power Technologies International
Activity GSTR overrides the user specified set of output channel assignments (refer to
Section 18.6.1), and the machine speed deviation, SPEED, and turbine mechanical power,
PMECH, for each of the < n > online machines being tested are placed in channels 1 through 2n.
Channel assignments are made in ascending bus number order with SPEEDs in odd numbered
channels and PMECHs in even numbered channels; the identifiers assigned by activity GSTR are
as listed in Table 14-2. Activity GSTR also sets all CRT channel selections (refer to Section 18.6.3)
to zero. Therefore, activity GSTR does not enable the user to take an optional snapshot as does
activity STRT. In fact, the user should never overwrite the main simulation Snapshot File following
execution of activity GSTR because its execution destroys the user specified output channel
assignments.
The machine initial conditions summary of activity GSTR may be terminated with the AB interrupt
control code.
14.13.1 Application Notes
The testing of cross-compound governor models requires that both generator models be active.
Additional Information
PSS
E GUI Users Guide, Section 21.5, Running Governor Response Simulation Test
PSS
E is operating in its Response File mode, all active Response Files are closed and
subsequent user commands are taken from the users terminal.
CH Print the output channel values at each time step. The value of NPRT which was entered at
the time activity GRUN was run is overridden while this option is in effect. When this option is
cleared, the original value of NPRT is restored and the next printing of channels occurs NPRT
time steps from the TIME of the clearing of the option.
TI Print the value of simulation TIME at the users terminal.
Dynamic Simulation Activity Descriptions PSS
E 32.0
Performing Governor Response Simulation in Time Steps Program Operation Manual
14-68 Siemens Energy, Inc., Power Technologies International
Activity GRUN automatically applies the load increment (typically 0.05 to 0.1) specified in activity
GSTR to each unit at TIME equals zero seconds.
This simulation should normally be carried out until at least ten seconds; the simulation may have
to be extended to as long as twenty seconds if hydro units are present.
14.14.1 Application Notes
Using activities GSTR and GRUN to perform this simulation reveals the transient variation of turbine
power and machine speed. All governing units should have a well damped response. Hydro gover-
nors will generally exhibit a somewhat greater overshoot than steam turbine governors, but should
still be well damped, showing no persistent oscillations. A small negative change in hydro turbine
power before it follows a positive change in load power is normal and does not indicate incorrect
governor tuning.
The procedure in simulating the governor response test follows that used in running conventional
state-space dynamic simulations. Instead of using activities STRT and RUN after the data has been
brought into memory, activity GSTR and GRUN are used.
The response test calculates the governor response of either all generating units in the system
with connected governor models, or all machines at a bus (designated during activity GSTR initial-
ization of a single bus) with connected governor models. Because machines are operating in
isolation, no network solution is required in the simulation. Furthermore, only the generator and
turbine-governor models are active in these simulations; all other models perform no calculations.
Therefore, these simulations require substantially less computer time than complete system
simulations.
The typical sequencing of PSS
E GUI Users Guide, Section 21.5, Running Governor Response Simulation Test
PSS
E 32.0
Building a State Variable Matrix for Linear Dynamic Analysis (LSYSAN)Program Operation Manu-
14-70 Siemens Energy, Inc., Power Technologies International
14.15 Building a State Variable Matrix for Linear Dynamic Anal-
ysis (LSYSAN)
Activity ASTR
The state variable matrix construction activity ASTR calculates the initial values of all variables for
each equipment model as a function of the models constant data and the boundary condition at the
bus in the working case at which it is referenced. It then infers the state variable system matrices
and processes them into a form suitable for input into the Linear Dynamic Analysis program,
LSYSAN.
For a valid execution of activity ASTR, dynamics data must be present in dynamics data working
memory and the converted network must be represented in the working case. The normal activity
sequence which precedes activity ASTR is:
1. Restore Dynamics Working Memory from a Binary Snapshot File (RSTR) <file1>
2. Retrieve a Power Flow Saved Case File (CASE) <file2>
where <file1> is the Snapshot File containing the appropriate dynamics model data and output
channel specifications, and <file2> is the Saved Case File containing the converted power flow
case.
When run, activity ASTR generates an alarm and terminates if generators are not converted. It then
ensures that the machine power arrays in the power flow working case are set to their original initial
condition values (they may have been changed by a prior execution of activity STRT or MSTR).
Activity ASTR completes its setup phase by checking for the presence of the factorized network
admittance matrix. If necessary, activity FACT (or activities ORDR and FACT) is executed.
Activity ASTR does a network solution and then, based on the bus boundary conditions, initializes
the state variables (STATEs) and algebraic variables (VARs) of each equipment model. If, in setting
up for the initial network solution, any CIMTR5, CIMWSC, CIM5xx, CLODxx, or IEELxx model
removes constant admittance load from the load at which it is called, an appropriate message is
printed and the network admittance matrix is automatically refactorized prior to commencing the
network solution.
Any machine which is online in the working case but which does not have a generator model
assigned to it generates an alarm with a message of the form:
Run Activity ASTR - GUI
Dynamics>Build matrices for LSYSAN program (ASTR)
[Build Matrices for LSYSAN]
Run Line Mode Activity ASTR - CLI
ACTIVITY?
>>ASTR
ENTER LARGEST DERIVATIVE CHANGE ALLOWED (DEFAULT IS 0.01):
>>
Interrupt Control Codes
AB, CM, NC, MO
Siemens Energy, Inc., Power Technologies International 14-71
PSS
E 32.0
Building a State Variable Matrix for Linear Dynamic Analysis (LSYSAN)Program Operation Manu-
14-72 Siemens Energy, Inc., Power Technologies International
Activity ASTR then summarizes the conditions at each online machine by tabulating the following
quantities:
Terminal voltage (ETERM).
Exciter output voltage (EFD).
Active and reactive power output (PELEC and QELEC).
Power factor.
Machine angle in degrees (ANGLE).
d and q axis currents on machine base.
This report is in ascending bus number order when the numbers output option is in effect, and in
alphabetical bus name order using the names option. Note that for wind machines, because the
quantity EFD is not of any relevance, this is set to zero.
Following the calculation of the system initial condition, the time derivatives (DSTATEs) of all STATE
variables are calculated and then checked for a steady state. The user specifies the largest deriv-
ative change to be allowed. Any STATE for which the time derivative exceeds the specified
threshold generates an alarm; its index is printed along with the values of its time derivative and the
STATE variable itself. For STATEs that have generated an alarm that are assigned to plant-related
models, the model and machine are also identified. For STATEs that have generated an alarm that
are assigned to load-related models, the model and load are also identified. For STATEs that have
generated an alarm that are assigned to auxiliary-signal models, the model and the name of the
device (the two-terminal, multi-terminal or VSC dc line or the FACTS device) with which the auxil-
iary-signal is associated are identified. For STATEs that have generated an alarm that are assigned
to dc line models, the model and dc line are identified. For STATEs that have generated an alarm
that are assigned to FACTS device models, the model and FACTS device are identified. For
STATEs that have generated an alarm that are assigned to switched shunt models, the model and
switched shunt device are identified. In each case, the ac bus is also identified. In each case, the
ac bus is also identified. In the case of machines, loads, and switched shunts, this will be the ac bus
at which the machine, load or the switched shunt.
In the case of machines and loads, this will be the ac bus at which the machine and load are
connected; for two-terminal dc lines, VSC dc lines, as well as for auxiliary signals attached to these
devices, this is the rectifier ac bus; for multi-terminal dc lines and for auxiliary signals attached to
multi-terminal dc lines, this will be the ac bus associated with converter number one; for FACTS
devices and for auxiliary signals attached to FACTS devices this will be the sending end ac bus. If
any such STATE variables are detected, activity ASTR is terminated. As in activity STRT, the pres-
ence of nonsteady STATEs may be caused by a variety of factors (e.g., procedural errors, incorrect
model data, numerical precision).
The user must specify the name of the Matrix Output File into which the system matrices and related
information are to be written. If no filename is specified in response to the above instruction, activity
ASTR is terminated. Refer to Section 2.4.1 for the file specification conventions used by activity
ASTR.
The user specifies those STATE variables to be included in the linear system matrices, either as
single STATEs or range of STATEs to be included in the matrices.
The user specifies the perturbation factor (default = 0.01).
The LSYSAN program provides for up to fifty elements in the system output vector and related
matrices. Activity ASTR treats the output channel selections in dynamics working memory (refer to
activity CHAN and Section 18.6) as potential output quantities. If no output channel selections have
Siemens Energy, Inc., Power Technologies International 14-73
PSS
E 32.0
Building a State Variable Matrix for Linear Dynamic Analysis (LSYSAN)Program Operation Manu-
14-74 Siemens Energy, Inc., Power Technologies International
14.15.1 Application Notes
Activity ASTR converts the system model into its state-space form represented by the following
equations:
x = Ax + Bu
v = Hx + Fu
where x is the state variable vector, u is the vector of input variables, v is the output variable vector,
and A, B, H and F are the real matrices describing the small perturbation behavior of the system.
While zero time constants for certain transfer function blocks such as voltage transducers may be
appropriate for dynamic simulation runs, any such state variable included in the system matrices
described above will result in its row in the A matrix having every term zero. The analysis in the
LSYSAN program prohibits this condition; LSYSAN automatically removes the corresponding row
and column from the A matrix, the corresponding column from the H matrix, and the corresponding
row from the B matrix. Alternatively, the user may exclude such STATEs from the specification of
those STATEs to be included in the linear system. Note that several PSS
E 32.0
Listing Dynamics Model Data Program Operation Manual
14-76 Siemens Energy, Inc., Power Technologies International
4. auxiliary signal models in the following order:
a. two-terminal dc line auxiliary signal models
b. multi-terminal dc line auxiliary signal models
c. VSC dc line auxiliary signal models
d. FACTS device auxiliary signal models
5. dc line models in the following order:
a. two-terminal dc line models
b. multi-terminal dc line models
c. VSC dc line models
6. FACTS device models
7. all models called from subroutines CONEC and CONET
The various dynamic simulation options are also displayed.
Plant-related and load-related models are tabulated in ascending bus numerical (using the numbers
output option) or alphabetical (using the names option) order; multiple elements (machines or
loads) at the same bus are printed in ascending identifier order. Plant- and load-related models for
a given network element are listed together in the report in the same order in which they are called
during a dynamic simulation calculation. For machines, this order is: generator, compensator, stabi-
lizer, minimum excitation limiter, maximum excitation limiter, excitation system, and governor. For
loads, the model order is load characteristic followed by load relay.
Line relay models are also tabulated in ascending bus numerical or alphabetical order. Models on
branches connected to a given bus are listed in ascending order of the other bus; line relay models
on parallel circuits are printed in ascending circuit identifier order.
Auxiliary-signal models are tabulated in ascending bus numerical or alphabetical order. At any bus,
the auxiliary-signal models are listed in the following order: auxiliary models associated with two-
terminal dc lines followed by auxiliary models associated with multi-terminal dc lines followed by
auxiliary models associated with VSC dc lines followed by auxiliary models associated with FACTS
devices.
DC line models are tabulated in ascending bus numerical or alphabetical order. At any bus, dc line
models are listed in the following order: two-terminal dc line models followed by multi-terminal dc
line models followed by VSC dc line models.
FACTS devices, and switched shunt models are also tabulated in ascending bus numerical or
alphabetical order.
Wind machine models (i.e., wind related models attached to machines designated as wind
machines in power flow) are tabulated in ascending bus numerical (using the numbers output
option) or alphabetical (using the names option) order; multiple machines at the same bus are
printed in ascending identifier order. Wind machine related models for a given network element are
listed in the following order: generator, electrical control, mechanical model, pitch control, aerody-
namic model, gust model, and auxiliary control.
The CONEC models are tabulated in the order in which they are called; then the CONET models
are tabulated in the order they are called.
Siemens Energy, Inc., Power Technologies International 14-77
PSS
E 32.0
Listing Dynamics Model Data Program Operation Manual
14-78 Siemens Energy, Inc., Power Technologies International
Additional Information
PSS
E 32.0
Listing Dynamics Data Arrays Program Operation Manual
14-80 Siemens Energy, Inc., Power Technologies International
Additional Information
PSS
E 32.0
Creating a Dynamics Model Raw Data File Program Operation Manual
14-82 Siemens Energy, Inc., Power Technologies International
6. FACTS devices, and switched shunt models are written in ascending numerical or alphabet-
ical bus order, according to the bus output option currently in effect.
7. Wind machine model (i.e., wind related models attached to machines designated as wind
machines in power flow) data records contained in the model connection tables are written
out in ascending numerical or alphabetical bus order, according to the bus output option
currently in effect.
8. Data records for the remaining simulation models are written in the same order in which the
equipment models are referenced in subroutines CONEC and CONET.
In any of the subsystem selection modes the user may specify any of the following types of models:
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV. Output for the appropriate grouping of buses is pro-
duced with buses ordered as described in Section 4.9.
Activity DYDA produces model specification records for any subsystem load-related model
connected to a load which is a member of selected subsystem. This means that, for example, an
Owner type subsystem model is produced when processing a subsystem consisting only of zones
if the Owner type subsystem model is connected to a load which is a member of the selected zones.
14.18.1 Application Notes
Prior to initiating activity DYDA, the following requirements must be met:
1. Dynamics data must be present in working memory (i.e., the appropriate Snapshot File must
be restored into memory with activity RSTR).
2. The corresponding electrical network must be present in the power flow working case as a
converted case.
All models
All plant models
Generator models
Compensator models
Stabilizer models
Minimum excitation limiter models
Maximum excitation limiter models
Excitation system models
Turbine governor models
Load characteristic models
Load relay models
Line relay models
Auxiliary signal models
2-terminal dc line models
N-terminal dc line models
VSC dc line models
FACTS device models
CONEC models
CONET models
Turbine load controller models
Switched shunt models
Wind models
Wind generator models
Wind electrical control models
Wind mechanical models
Wind pitch models
Wind aerodynamic models
Wind gust models
Wind auxiliary control models
Siemens Energy, Inc., Power Technologies International 14-83
PSS
E program
structure (i.e., the createusrdll command to create the user dll must have been executed;
refer to Additional Resources for PSS
E, Createusrdll).
Thus, assuming that the connection subroutines have been linked as described in Section 4.10, the
following activity sequence normally precedes activity DYDA:
1. Restore Dynamics Working Memory from a Binary Snapshot File (RSTR) <file1>
2. Retrieve a Power Flow Saved Case File (CASE) <file2>
where <file1> is the name of the appropriate dynamics data Snapshot File and <file2> is the name
of the corresponding converted power flow Saved Case File.
Data records for plant-related models, load-related models, line relay models, dc line models,
FACTS device models, and auxiliary signal models which are bypassed (i.e., off) are omitted from
the output of activity DYDA. Similarly, data records for such models which are unconnected (i.e.,
the network element to which they are connected is not present in the power flow working case) are
excluded.
In subsystem selection mode in the graphical user interface, when specifying subsystems and
model types, the user should be careful not to write data records for any model more than once.
When writing two machine models (e.g., FRECHG, COMPCC, CRCMGV), a special convention is
used by activity DYDA. The model is assumed to be associated with the first machine of the two for
which it is applied.
When writing auxiliary-signal models, dc line models, and FACTS device models, the following
convention is used: for two-terminal dc lines, and for auxiliary-signal models associated with two-
terminal dc lines, DYDA assumes that the model is associated with the rectifier bus; for multi-
terminal dc lines and auxiliary-signal models combined with multi-terminal dc lines, DYDA assumes
that the model is associated with the the ac bus of the first converter; for VSC dc lines, and for auxil-
iary-signed models combined with VSC dc lines, DYDA assumes that the model is associated with
the first converter; for FACTS devices and auxiliary-signal models combined with FACTS devices,
DYDA assumes that the model is associated with the sending end ac bus.
In subsystem selection mode, a similar convention is used in processing line relay, CONEC, and/or
CONET models following specification of all models, line relay models, CONEC models, or CONET
models. For line relay models and for those CONEC and CONET models that refer to more than
one bus, activity DYDA assumes that the model is associated with the first bus that defines the
equipment being modeled (e.g., for DISTR1, the from bus of the branch).
GUI only: The [Save / Show Dynamics Data] dialog available from the File > Save menu entry
when dynamics data is present in the working case provides an additional control beyond those
available using line mode. This control is the Load model output toggle which includes two condi-
tions: All subsystem models and Selected subsystem models. The toggle is available when bus
selection is limited to one bus subsystem or individually specified buses.
The All subsystem models selection is equivalent to the line mode behavior of activity DYDA.
Selecting the Selected subsystem models condition may further limit the reported model specifica-
tion records of subsystem load-related models.
Dynamic Simulation Activity Descriptions PSS
E 32.0
Creating a Dynamics Model Raw Data File Program Operation Manual
14-84 Siemens Energy, Inc., Power Technologies International
Under either condition the output includes model specification records for Bus type subsystem
models connected to any element which is a member of the selected subsystem. When subject to
the Selected subsystem models condition, the output excludes all non-Bus type subsystem models
for which the subsystem type is not part of the subsystem selection criteria. For example, if the
selected subsystem consists only of zones, then the reported model specification records excludes
all Owner, Area and All type subsystem models, and includes Zone type subsystem models which
are connected to elements in the selected zones.
Additional Information
PSS
E GUI Users Guide, Section 20.10, Creating a Dynamics Model Raw Data File
PSS
E 32.0
Dumping Dynamic Simulation Output Channels into a Response File Program Operation Manual
14-86 Siemens Energy, Inc., Power Technologies International
1. An invalid channel address is assigned to the channel (refer to Section 18.6.1).
2. The channel quantity is a VAR not associated with a CHAN monitoring model or a STATE,
and the option to include these was not enabled.
In the Response File built by activity DMPC, a blank line is included as the response for the starting
channel, VAR and ICON request by activities CHAN and CHSB. Thus, the next available locations
in these arrays at the time the Response File is executed will be used.
Additional Information
PSS
E 32.0
Creating Dynamic Data Records for Use by Other Activities Program Operation Manual
14-88 Siemens Energy, Inc., Power Technologies International
14.20.1 Application Notes
When a Breaker Duty Data File is being written by activity RWDY, a data record is produced for each
machine in the working case which is modeled by one of the following generator models: GENROU,
GENROE, GENSAL, GENSAE, GENDCO, FRECHG, CIMTR1, CIMTR2, CIMTR3 or CIMTR4.
Machines modeled by other machine models are omitted from the Breaker Duty Data File.
When an Inertia and Governor Response Data File is being written by activity RWDY, a data record
is produced for each machine in the working case which is modeled by one of the following gener-
ator models: GENROU, GENROE, GENSAL, GENSAE, GENCLS, GENDCO, GENTRA, CGEN1,
FRECHG, CIMTR1, CIMTR2, CIMTR3 or CIMTR4. Machines modeled as a static var system, by
the CDSMS1, CSMEST, CBEST and CSTATT model, or by a user-written model are omitted from
the Inertia and Governor Response Data File. If the machine has a governor model other than the
SHAF25 model or a user-written model, governor response data is included in its data record; other-
wise, only the machine inertia is written and the remaining data items will take on default values
when the data file is read by activity INLF.
When a Relay Characteristic Data File is being written by activity RWDY, a data record is produced
for each occurrence in the simulation setup of any of the following line relay models for which the
branch is in the working case: CIROS1, SLNOS1, DISTR1, RXR1, SLLP1, and SLYPN1. A data
record is also generated for each RELAY2 and RELAY3 monitoring model reference generated by
activities CHAN and CHSB for which the monitored branch is in the working case. The 16-character
identifier fields are set by activity RWDY so as to identify the branch at which the model is applied.
For the line relay models, each identifier is set to the two bus numbers, the circuit identifier, and the
relay slot number, all separated by dashes (e.g., 7533-248-1-1). For the RELAY2 monitoring model,
each identifier is set to the two bus numbers and the circuit identifier, all separated by dashes (e.g.,
7533-248-1). For the RELAY3 model, each identifier is set to the number of the bus to which the
monitored winding is attached, the three-winding transformer name, and the circuit identifier, all
separated by dashes (e.g., 7533-TRNSFRMR-1); the relay type field is set to RELAY2. These iden-
tifiers may be changed by the user to conform with the naming conventions and to assure
uniqueness.
Additional Information
PSS
E 32.0
Listing Dynamics Model Storage Locations Program Operation Manual
14-90 Siemens Energy, Inc., Power Technologies International
Additional Information
PSS
E 32.0
Initializing Models for Extended Term Simulation Program Operation Manual
14-92 Siemens Energy, Inc., Power Technologies International
Activity MSTR initializes the dynamic simulation by first doing a network solution and then, based
on the bus boundary conditions, initializing the Z-form integration cells (STOREs) and algebraic
variables (VARs) of each equipment model. If, in setting up for the initial network solution, any
CIMTR5, CIMWSC, CIM5xx, CIMWxx, or IEELxx model removes constant admittance load from the
load at which it is called, an appropriate message is printed and the network admittance matrix is
automatically refactorized prior to commencing the network solution.
Any machine which is online in the working case but which does not have a generator model
assigned to it generates an alarm with a message of the form:
NO ACTIVE GENERATOR MODEL CALL FOR MACHINE i AT BUS nnnn
The source current (ISORCE) of any such machine is set to zero. The presence of any such
machines renders the initial condition invalid, and activity MRUN will not allow itself to be executed
following such an initialization.
Similarly, any two-terminal, multi-terminal, VSC dc line, FACTS device, or any switched shunt
device that is in the continuous control mode, which is in-service in the working case but which does
not have a dynamic table model assigned to it generates an alarm with one of the following error
messages:
NO ACTIVE TABLE MODEL CALL FOR TWO-TERMINAL DC LINE "name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
NO ACTIVE TABLE MODEL CALL FOR MULTI-TERMINAL DC LINE "name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
NO ACTIVE TABLE MODEL CALL FOR VSC DC LINE "name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
NO ACTIVE TABLE MODEL CALL FOR FACTS DEVICE "name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
NO ACTIVE TABLE MODEL CALL FOR SWITCHED SHUNT AT BUS "bus name"
PLEASE ENSURE THAT THIS EQUIPMENT HAS A MODEL CALL IN CONEC
The presence of any such dc line, FACTS or switched shunt device could
indicate one of the following:
A table model was assigned to the dc line, FACTS device or the switched shunt, but
the model was later removed. When this condition is detected during activity MSTR,
activity MRUN will not allow itself to be executed.
No table model was ever assigned to the dc line, FACTS, or the switched shunt device,
or the model assigned is a CONEC and CONET called model. When this condition is
detected during activity MSTR, activity MRUN will allow itself to be executed.
During the model initialization process, any model variable which is initialized beyond its prescribed
limits (e.g., the voltage regulator output of the IEEE Type 1 excitation system model, IEEET1)
generates an alarm with a message of the form:
name AT BUS nnnn MACHINE i INITIALIZED OUT OF LIMITS
where < name > is the model name (e.g., IEEET1), < nnnn > is the bus number, and < i > is the
machine identifier of the model containing the out-of-limits variable. The user should resolve any
such error conditions before running a simulation. The presence of such error alarms renders the
initial condition invalid in the sense that the system is not in a steady state; that is, if activity MSTR
Siemens Energy, Inc., Power Technologies International 14-93
PSS
E 32.0
Initializing Models for Extended Term Simulation Program Operation Manual
14-94 Siemens Energy, Inc., Power Technologies International
The format of the network convergence monitor is the same as that of activities TYSL, SOLV, and
STRT.
In the induction machine models CIMTR5, CIMWSC, CIM5xx, CIMWxx, CIMTR3, and CIMTR4, a
local iteration is used in extended term simulations to solve for the equivalent load drawn by the
model at each iteration of the network solution. The induction machine convergence monitor tabu-
lates the load or machine to which the model is connected, the local iteration number, electrical
torque (VAR(L+2)), and the real and imaginary components of the complex machine internal
voltage.
Siemens Energy, Inc., Power Technologies International 14-95
PSS
E Program
Application Guide for details.
Most models supplied with PSS
E Model Library.
Table 14-4. PSS
E 32.0
Initializing Models for Extended Term Simulation Program Operation Manual
14-96 Siemens Energy, Inc., Power Technologies International
Activity MSTR generates an alarm for the use of any of the models listed above and sets a flag such
that activity MRUN will not allow itself to be executed. However, it is not able to detect the presence
of user-written models for which the code has not been modified for use in extended term simula-
tions. Moreover, it is likely that such models will result in other models behaving incorrectly. The test
simulation runs recommended at the beginning of this section are likely to reveal this situation.
Load Characteristic and Relay Models
CLODxx
Auxuliary Signal Models
RBKELT
DC Line Models
CDC1T CDCABT MTDC2T VSCDCT CDC7T
Generic Wind Models
WT3G1 WT3E1 WT3T1 WT3P1 WT1G1
WT2G1 WT3G2 WT4G1 WT2E1 WT4E1
WT12T1 WT12A1
Switched Shunt Models
CHSVCT
CONEC and CONET Models
CASEA1 CDC1 CDCAB1 CDCRL CDCVUP
CEELRI CHESVC CMDWAS DCPOW MTDC02
RBKELR
Additional Information
PSS
E GUI Users Guide, Section 21.6, Running Extended Term Dynamic Simulation
PSS
E 32.0
Performing Extended Term Simulation in Time Steps Program Operation Manual
14-98 Siemens Energy, Inc., Power Technologies International
Activity MRUN responds to the following interrupt control codes:
The form of the network convergence monitor is identical to that of activities STRT, RUN, MSTR,
TYSL, and SOLV in the small and intermediate time step modes. In the large time step (uniform
island frequency) mode, each convergence monitor line is extended to include:
The magnitude of the largest machine angle change as a multiple of the island fre-
quency convergence tolerance.
The number of the bus with the machine experiencing the largest angle change.
The largest machine angle change.
The form of the induction machine convergence monitor is identical to that of activity MSTR.
14.23.1 Application Notes
As discussed in Section 14.22.1, before executing extended term simulations with a system model,
state-space simulations should be performed. A steady-state run of several seconds and a refer-
ence standard simulation of at least ten seconds are recommend. After any suspect modeling has
been resolved, this pair of simulations should be repeated in extended term mode using the same
time step as was used in the state-space simulations.
Activity MSTR sets the output control variables NPRT and NPLT to one, and CRTPLT to zero. On
the first subsequent execution of activity MRUN, these values are the defaults for these variables.
On following executions of activity MRUN, these variables reset to its default values, those values
specified on the previous execution of activity MRUN.
Whenever the value of simulation TIME reaches the time specified for TPAUSE, the transfer func-
tion output and network solution calculations are performed with a flag set to inform the simulation
that this is a t
-
calculation; the Z-form integration array elements (STOREs) are not updated.For any
of the channel output options which are active, the appropriate output is generated regardless of
whether the present time step is a print or plot time step as determined by the variables NPRT, NPLT
and CRTPLT. When activity MRUN is reentered, with perhaps some switching operation having
been specified, the time step is repeated as a t
+
calculation. Appropriate channel output is
performed at the completion of the time step as determined by the new specification of the output
control variables. This applies both for the case in which activity MRUN has advanced TIME to the
value specified for TPAUSE and when interrupted by the user.
AB Force a pause by setting TPAUSE to the current value of simulation TIME. This overrides the
value of TPAUSE which was specified at the time activity MRUN was run. In addition, if
PSS
E is operating in its Response File mode, all active Response Files are closed and
subsequent user commands are taken from the users terminal.
CM Print the network solution convergence monitor.
NC Suppress network convergence monitor when the CM suffix was specified in selecting activity
MRUN.
MO Print the induction motor local iteration convergence monitor.
CH Print the output channel values at each time step. The value of NPRT which was entered at
the time activity MRUN was run is overridden while this option is in effect. When this option is
cleared, the original value of NPRT is restored and the next printing of channels occurs NPRT
time steps from the TIME of the clearing of the option.
TI Print the value of simulation TIME at the users terminal.
Siemens Energy, Inc., Power Technologies International 14-99
PSS
E 32.0
Performing Extended Term Simulation in Time Steps Program Operation Manual
14-100 Siemens Energy, Inc., Power Technologies International
generates an alarm for buses in such islands, and disconnects them. It then calculates a new spar-
sity-preserving ordering (activity ORDR) and rebuilds the factorized admittance matrix (activity
FACT).
If an automatic line switching occurs in uniform island frequency mode which causes changes in
the island assignments of buses (e.g., if a new island is defined), results are unpredictable. Estab-
lishing the relationship of buses to islands occurs only upon entry into activity MRUN and not
following automatic switchings.
If the network solution fails to reach its tolerance in the prescribed number of iterations, an alarm is
printed and the simulation continues as though convergence had been achieved. Refer to
Section 18.7 for additional details.
The computer time per simulation time step is much longer in extended term simulations than it is
in state-space simulations. However, extended term simulations can achieve significant execution
time advantages over state-space simulations when there are significant periods of simulated time
where a much larger simulation time step is appropriate.
Additional Information
PSS
E GUI Users Guide, Section 21.6, Running Extended Term Dynamic Simulation
PSS
E models or
from the user model definition table. Similarly, the starting CON and ICON array indices used by the
model are obtained from the array allocation table (refer to activity DYCH).
The descriptive information on each data item is read from a binary file named MODELS (on most
systems, this file has the extension RWF). When initiated, activity CCON searches the current
directory for this file. If the file is not found locally, activity CCON follows the directory search
sequence described in Section 2.1.
As supplied with PSS
E 32.0
Changing Dynamics Model Constants Program Operation Manual
14-102 Siemens Energy, Inc., Power Technologies International
contained in the file are described as J, J+1, J+2, and so on, and ICONs are described as M, M+1,
and so on.
With the auxiliary program DBUILD31, users may construct customized MODELS files which
include descriptive information on their user-written models. With such a customized MODELS file
in the users current or home directory, activity CCON automatically accesses the users copy rather
than the MODELS file as supplied on the PSS
E, DBUILD.
Additional Information
PSS
E.
14.25.1 Operation of Activity CHSB
The user identifies quantities to be placed into output channels and activity CHSB places their
memory addresses and alphanumeric identifiers into the PSS
E 32.0
Assigning Subsystem Simulation Data to Output Channels Program Operation Manual
14-104 Siemens Energy, Inc., Power Technologies International
The user specifies any of the following quantities for monitoring:
In addition, the user may specify the inclusion of out-of-service equipment. Otherwise, output chan-
nels are generated only for in-service machines, loads, buses or branches, as appropriate. The
default is in-service equipment only.
The user may process the entire working case or specify subsystem data (refer to Section 4.8).
For load and generating-plant quantities, activity CHSB processes all elements in the selected
subsystem. For bus quantities, activity CHSB processes all buses in the specified subsystem. For
branch quantities, activity CHSB processes all branches where endpoint buses are in the specified
subsystem. Output channels are generated, and then the user may select another type of quantity,
service status option, and, if appropriate, subsystem.
Note that categories Voltage & Angle, Flow (P&Q), Relay2 (R&X), and Machine Apparent Impedance
generate two output channel assignments for each element selected for monitoring.
When processing branches between areas or zones, the user must specify ties from either areas
or zones, as appropriate, using the methodology given in Section 4.8. The selected branch quantity
or quantities for all tie branches from each specified area or zone are placed into output channels.
Subsystem power totals may be specified by area, zone, owner, or all buses. This produces
summations by subsystem of: machine electrical power, machine mechanical power, accelerating
power, and load demand.
The user may process the entire working case or specify subsystem data (refer to Section 4.8) by
bus subsystem, area, zone, owner, or basekV.
Machine, Bus, Load, and Branch Quantities
Angle
Pelec
Qelec
Eterm
EFD
Pmech
Speed
Xadifd
Ecomp
Vothsg
Vref
Bus frequency deviation
Voltage
Voltage & Angle
Mach Iterm
Machine Apparent
Impedance
Vuel
Voel
Pload
Qload
Gref
Lcref
Active power command
from wind control
Wind turbine speed
Wind pitch
Wind aerodynamic torque
Wind rotor voltage
Wind rotor current
Wind real power command
from electrical control
Wind reactive power
command from electrical
control
Wind auxiliary control output
Machine, Bus, Load, and Branch Quantities
Tie Line Quantities
Flow (P)
Flow (P&Q)
Flow (MVA) Relay2 (R&X)
Siemens Energy, Inc., Power Technologies International 14-105
PSS
E 32.0
Assigning Subsystem Simulation Data to Output Channels Program Operation Manual
14-106 Siemens Energy, Inc., Power Technologies International
3. It generates entries in the CHAN monitoring model tables for the appropriate model call
(VOLMAG, FLOW1, FLOW3, RELAY2, RELAY3, GENTMC, GENTMZ, PTOTOW, PTOTZN,
PTOTAR, or PTOTAL).
4. As with the other data categories, it establishes the appropriate IPRINT and IDENT array
entries.
During dynamic simulations, model calls corresponding to the model references contained in the
CHAN monitoring model tables are issued each time step at the completion of the network balance.
Thus, after being selected by activity CHSB, these network quantities are automatically calculated
during dynamic simulation runs and placed into output channels.
VARs and STATEs are not valid options in activity CHSB. In order to assign VARs and STATEs to
output channels activity CHAN must be used.
As activity CHSB assigns each selected simulation quantity to an output channel, it makes a corre-
sponding entry in a set of channel descriptor arrays. These arrays describe the type of quantity
assigned to the channel, and its location in the network in terms of external bus numbers, machine
and circuit identifiers, and so on. These arrays are also used in describing the content of each
channel in activities ALTR and DLST.
This information is also used to reconcile differences in the PSS
E working
memory.
When the value specified as the starting channel index exceeds the next available channel value
contained in dynamics working memory, the channels in this gap have their IPRINT, IDENT and
channel descriptor array entries set so as to leave the channel unused. Dynamic simulation quan-
tities may be assigned to such channels in subsequent executions of activity CHAN or CHSB using
the approach given at the end of Sections 14.2.1 and 14.25.1.
As in activity DYRE (refer to Section 14.1.3), the user should take care to take a Snapshot following
successful execution of activity CHSB and prior to terminating PSS
E 32.0
Assigning Subsystem Simulation Data to Output Channels Program Operation Manual
14-108 Siemens Energy, Inc., Power Technologies International
4. In selecting for output a quantity requiring a network monitoring model call, the table accom-
modating the CHAN monitoring model references is full. The following message is printed:
nnnn MONITORING MODELS SPECIFIED--POINTER TABLE FULL
5. In selecting angle statistics, the following message is printed if the function was previously
selected:
ANGLE STATISTICS STARTING AT VAR nnnn ALREADY IN CHANNELS
Additional Information
PSS
E 32.0
Assigning Subsystem Simulation Data to Output Channels Program Operation Manual
14-110 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 15-1
Chapter 15
Program Automation
15.1 What is Program Automation?
Program automation in PSS
E to perform in a file
of some kind (explained in the following sections) and to tell PSS
E
API is described in PSS
E.
Program Automation PSS
E 32.0
Automation Methods in PSS
E
Activity Automation Methods
There are six automation processors in PSS
E:
An embedded Python interpreter (refer to Section 15.4)
The Batch (or BAT_) Command interpreter (Section 15.5)
The Line Mode Interpreter (LMI) (Section 15.11)
The PSS
E.
A Python installer is included in the PSS
E installation package will also install the following freely available third-party extension
modules:
wxPython (http://www.wxpython.org//)
win32all (Python Extensions for Windows) (http://sourceforge.net/projects/pywin32/)
Python files can be in source form (*.py, *.pyw) or byte-compiled (*.pyc). Python Files can be used
in PSS
E Application Program Interface, that can be imported into user programs inside or outside of
the PSS
E GUI:
Program Automation PSS
E 32.0
Python Programs Program Operation Manual
15-4 Siemens Energy, Inc., Power Technologies International
excelpy - provides Python functions to interface with Excel; these functions can be
used to create, populate and format Excel workbooks from Python.
pssarrays - provides Python functions to retrieve PSS
E solution results
pssexcel - provides Python functions to export PSS
Plot API
psspy - provides access to the PSS
E API
Your PSS
E installation will also include the following Python extension modules which can also be
imported into user programs inside or outside of the PSS
E GUI:
bsntools - a set of simple bus name manipulation tools
caspy - provides access to the Saved Case Data Extraction routines (USRCAS)
redirect - some tools to connect I/O streams between PSS
E and Python
dyntools - tools for processing channel output files
wordpy - provides Python functions to interface with Microsoft Word; these functions
can be used to create, populate, and format a Microsoft Word document from Python.
This is especially useful to insert plot files (*.eps, *.wmf, *.png, etc.) created by
PSSPLT/PSSPLOT or any picture file into a Word document.
plot2word - provides a graphical user interface to wordpy for inserting plot/picture files
into a Microsoft Word document.
excelexport - provides a graphical user interface to PSSEXCEL for exporting PSS
E
results into Excel spreadsheets.
These modules are fully supported as part of the PSS
E to execute Python
files and commands. When the PSS
Es progress device.
Note in particular that none of the modules are imported into the local name space. That means, for
example, that to use a PSS
E 32.0
Python Programs Program Operation Manual
15-6 Siemens Energy, Inc., Power Technologies International
One idiosyncrasy of the current embedded interpreter is that results are not automatically echoed
to the terminal as they are in the stand-alone Python interpreter. To view the values of expressions
you must use the print command.
15.4.3 The External Interpreter Environment
Python programs that access PSS
E GUI.
Python is installed with its own command line interpreter, its own integrated Development Environ-
ment (IDE) - called IDLE -, and programs can be written to create their own GUIs. Any of these can
use the PSS
E supplied extension modules in this way, you must first make sure that
the Python import path can find all the modules by name, and that the windows load path can find
any required DLLs. The following example replicates the environment in the embedded interpreter
explained in the preceding section:
>>> import os,sys
>>> sys.path.append(r"C:\Program Files\PTI\PSSE32\PSSBIN")
>>> os.environ['PATH'] = r"C:\Program Files\PTI\PSSE32\PSSBIN;"
+ os.environ['PATH']
>>> os.chdir(r"C:\work_dir")
>>> import psspy
>>> import redirect
>>> _i=psspy.getdefaultint()
>>> _f=psspy.getdefaultreal()
>>> _s=psspy.getdefaultchar()
>>> redirect.psse2py()
>>> psspy.psseinit(80000)
This example assumes the standard PSS
E
GUI and cannot be used in this mode. There are some graphics functions in psspy for which this is
true as well.
Siemens Energy, Inc., Power Technologies International 15-7
PSS
E data files. The following additional rules apply to batch commands, though:
The command name itself is case insensitive, i.e. it doesnt matter whether you use
upper case or lower case letters, or mix them (the documentation will always define
them as all upper case).
The commands may be continued on multiple lines. The interpreter keeps reading data
until all the arguments that it needs for a given API routine are satisfied.
There is a special token, a semi-colon, that can be used to tell the interpreter that it
should return all remaining inputs to default settings for that particular API routine. It
must be a separate token, not part of the previous value. In our example above,
BAT_ABCD 1 34 ;
will reset the third value to the default value, but
BAT_ABCD 1 34;
will return a syntax error because 34; is not a valid integer.
15.5.1 Response Files
Files containing batch commands are called Response Files (*.idv) because they can be mixed with
the older PSS
E command line, which uses files of that type. Response Files can be used in
PSS
E 32.0
Recording Program Operation Manual
15-8 Siemens Energy, Inc., Power Technologies International
15.6 Recording
Activity Recording
The PSS
E commands will record the API routines used to an automation file for later use until the
I/O Control>Stop Recording option is selected.
As an example, suppose you wanted to print power flow results to the Report View for buses 101,
201, 205, 154, and 3001. To record these interactions:
1. Select I/O Control>Start Recording and select the type of file you wish to record: Python
File (*.py) or Response File (*.idv).
2. Specify, say, busout.idv or busout.py as the filename depending on your selection of file type
in Step 1, and open it.
3. Select File>Open, select savnw.sav, and open it.
4. Select Power Flow>Solution>Solve. The power flow solutions dialog is displayed. Solve it
and then close it.
5. Select Power Flow>Reports>Bus based reports. The bus based reports dialog is displayed.
Enter buses 101, 201, 205, 143, 3001 in the text box provided. Select Go and then close it.
6. Select I/O Control>Stop Recording.
Using a text editor, open the file busout.idv (Figure 15-1) or busout.py (Figure 15-2) and you will
see the following
Figure 15-1. Response File Recorded by PSS
E
Figure 15-2. Python File Recorded by PSS
E
@! File:"C:\Program Files\PTI\PSSE31\EXAMPLE\busout.idv", generated on TUE, AUG 17 2004 15:41
BAT_CASE,'C:\Program Files\PTI\PSSE31\EXAMPLE\savnw.sav'
BAT_FDNS,0,0,0,1,1,0,99,0
BAT_BSYS,1,0,0.0,0.0,0,5,101,201,205,154,3001,0,0
BAT_POUT,1,0
# File:"C:\Program Files\PTI\PSSE31\EXAMPLE\busout.py", generated on WED, AUG 18 2004 15:13
psspy.case(r"""C:\Program Files\PTI\PSSE31\EXAMPLE\savnw.sav""")
psspy.fdns([0,0,0,1,1,0,99,0])
psspy.bsys(1,0,[0.0,0.0],0,[],5,[101,201,205,154,3001],0,[],0,[])
psspy.pout(1,0)
Siemens Energy, Inc., Power Technologies International 15-9
PSS
E the input string is entered as a single argument. If the file arg0.py is selected
(say, in the root directory of the C drive) and the string a list of words is entered in the argument
string dialog box, the following will be displayed at the Progress tab:
Executing Python file:C:\LocalDocs\dev\testing\arg0.py
['C:\\arg0.py', 'a list of words']
15.7.2 Arguments in Response Files
The argument string is parsed according to the standard PSS
E itself.
Arguments replace argument designator strings, which are of the form %n%, where < n > is one of
the numbers 1 through 15. Any recording of input lines contains the argument values in place of the
argument designator strings. A Response File may pass an argument that it receives to another
Response File, which it, in turn, initiates. It is usually good practice to place such argument desig-
nators in quotes so that a single argument that contains blanks and/or commas not be interpreted
by the designated Response File as multiple arguments.
Program Automation PSS
E 32.0
Argument Passing Program Operation Manual
15-10 Siemens Energy, Inc., Power Technologies International
An example of an argument would be %1%, which could appear anywhere in the file. In this case
%1% would be replaced by the first value parsed from the argument string. Likewise %5% would
be replaced by the fifth value parsed from the argument string.
Response Files require that all arguments receive values. When a Response File references an
argument that was not passed to it at the time it was initiated, an error condition occurs A useful
technique is to document all arguments referenced in a Response File using the TEXT command
at the beginning of the Response File. This approach will help detect missing argument errors
before any lengthy computations specified in the Response File are performed.
The following are examples of specifying arguments to a response file that can be entered in the
command line:
@INPUT , filename , 'argument 1' , 'argument 2' ... 'argument 15'
or:
@CHAIN , filename , 'argument 1' , 'argument 2' ... 'argument 15'
15.7.3 Arguments in IPLAN Files
The entire argument string is placed in a buffer. The IPLAN command ARGUMENT can then be
used to parse the string in any way - and repeatedly - using the standard PSS
E free-format input
rules. Refer to Section 3.27 of the IPLAN Program Manual.
Siemens Energy, Inc., Power Technologies International 15-11
PSS
E to another. If it is
necessary to acquire these values, always run the API routine to get the current values.
Default values can be specified in references to API routines in Python Files. Data items can be
omitted in Response Files. The concept of default values does not apply to IPLAN programs in
general, but there are some functions that take optional arguments, and because PUSH statements
can contain anything that could be in a Response File, any comments about Response Files will
apply there. All data values are required in PSEB and PSAS files, unless the syntax specifically indi-
cates otherwise.
15.8.1 Defaults in Python Functions
The Python language provides an easy mechanism for permitting optional arguments to functions.
However it requires that each function be coded in such a way as to permit this. Not every one is.
All the functions in the psspy module are coded in this way. For other modules delivered with
PSS
E 32.0
Default Values Program Operation Manual
15-12 Siemens Energy, Inc., Power Technologies International
What this means is that all the functions in psspy recognize special keywords formed by concate-
nating any input list name and the string representation all the possible index values (starting at 1)
and will use them to override just that specific element of the list.
15.8.3 Defaults in Recorded Python Files
When recording is enabled and the Python format is chosen, values for all arguments are specified.
Where default values are recorded, actual values are used except for the following:
in place of default integer values, the variable _i is used.
in place of default float values, the variable _f is used.
in place of default string values (not filenames) the variable _s is used.
This will work directly inside of the PSS
E
15.9 Unattended Execution of PSS
E
Activity Unattended Execution of PSSE
In some cases, it may be desirable to run PSS
E provides command line options that can be used for this purpose. In Section 15.9.1
provides a list of all the available command line options; these four specifically pertain to this
purpose:
note that the initial - is part of the command
-rspfile, -pyfile, and -argstr all expect to be followed by a string
-pyfile will be ignored if -rspfile is specified
-argstr and -embed will be ignored if neither -rspfile nor -pyfile are specified
the command line is blank delimited; if the string specified to -rspfile, -pyfile, or -argstr
contains a blank then the string must be quoted
if the same option is specified more than once, only the last one will be used
notwithstanding the previous point, the order of the options is unimportant
the string value for the -argstr option is the argument string (see Section 15.7)
Provision is made for specifying only Response Files or Python Files. Both of those file types can
use other types of Automation Files so, indirectly at least, any type can be used.
The -embed option has the effect of suppressing the display of the PSS
E in an unattended mode:
PSS
E does not read input from stdin or write to stdout, so pipes cannot be used for
batch execution of PSS
E.
Be aware of the nature of the operating system tool you are using to start PSS
E. In
Microsoft Windows, for example, non-console application programs, such as PSS
E,
are executed asynchronously. This means that should you have a batch file that starts
PSS
E it will not wait for the program to stop before continuing on the next statement
in the batch file.
When running in batch mode (i.e. with a startup automation file specified that stops the
program) the Progress tab and Report tab output should be re-directed to a printer or
file, otherwise output will be sent to windows that would be closed when the program
stops.
-rspfile -pyfile -argstr -embed
Program Automation PSS
E 32.0
Unattended Execution of PSS
E, 1K->150k.
-rspfile Immediately run a Response file.
-pyfile Immediately run a Python file.
-argstr Specify arguments for automation files.
-embed Run without display (until automation file terminates).
-inifile Run program with alternative ini file.
Siemens Energy, Inc., Power Technologies International 15-15
PSS
E 32.0
Line Mode Commands Program Operation Manual
15-16 Siemens Energy, Inc., Power Technologies International
15.11 Line Mode Commands
The line mode was the primary method of controlling PSS
E asks.
The modern GUI has replaced this previously common method of operation, but there is a wealth
of existing Response Files containing line mode commands used to automate PSS
E. Therefore
PSS
E currently contains a feature called the Line Mode Interpreter (LMI) - a new program written
to imitate the traditional line mode of PSS
E API. In a way it is
a translator from line mode to batch commands. It is not a perfect imitation, and those differences
are captured in PSS
E, for those functions it can perform, and for those users who are thoroughly familiar with the
command line (and are good typists), the program can still be operated more quickly from the
keyboard than is physically possible with a point-and-click interface (i.e., a mouse). So while
command line capabilities are not likely to be enhanced in the future, its current operation is consid-
ered to be an important feature of the program.
15.11.1 Mixing Line Mode and Batch Commands
Response files can contain both line mode and batch commands. The batch commands can be
thought of as additional activities of the line mode. They are not, and they are handled very differ-
ently; but for purposes of understanding how they may be combined in the same file, that image
provides the guidelines that need to be followed.
The format of the line mode commands also conforms to the PSS
E.
They are functions of a utility library (a Siemens PTI product) that is used by PSS
E but separately
maintained. Immediate Commands can also be mixed with line mode and batch commands. Unlike
batch commands, however, they can be used anywhere, even in the middle of a series of responses
to a particular activity using the command line. The following list is provided for convenience:
@CHAIN filename - Open the specified file as a chained response file.
@INPUT filename - Open the specified file as a nested response file.
@PAUSE - Temporarily suspend response file operation.
Siemens Energy, Inc., Power Technologies International 15-17
PSS
E 32.0
Running a Response File Program Operation Manual
15-18 Siemens Energy, Inc., Power Technologies International
15.12 Running a Response File
Executing activity IDEV in line mode should be considered an obsolete capability which is retained
for backward compatibility purposes. Executing activity IDEV in the GUI window accesses program
automation file selection.
@INPUT and @CHAIN commands may be issued from Response Files as well as in the
Enter command: field of the PSS
E
remain in synchronism with the responses contained in the Response File.
The @PAUSE and @CONTINUE commands may be abbreviated to as few characters as are
necessary to uniquely identify the @ command.
Activity IDEV itself is not sensitive to interruption by the user. While one or more Response Files
are active, user interruption may be used to close all open Response Files.
Additional Information
PSS
E 32.0
Recording User Actions Program Operation Manual
15-20 Siemens Energy, Inc., Power Technologies International
15.13 Recording User Actions
Activity ECHO
The dialog echoing activity ECHO enables the writing of all subsequent user dialog input to a desig-
nated file, which may subsequently be used as a Operation of activity ECHO.
Users of PSS
Es traditional command line interface will be familiar with the activity ECHO. It
performs a function similar in effect to the recording function in the current program. It is a very
different thing, however, and a remnant of it remains.
ECHO copies terminal input to a file. Because all PSS
E as part
of the interactive dialog. In addition, whenever a PSS
E 32.0
Building a Response File, Power Flow Calculation Program Operation Manual
15-22 Siemens Energy, Inc., Power Technologies International
15.14 Building a Response File, Power Flow Calculation
Activity PSEB
The power flow run assembler activity PSEB allows the user to specify routine power flow runs in
an English-like language. Input to activity PSEB is taken either from a PSEB Command File or from
the dialog input device. This can be in-stream in a Response File, typed into the command line in
the GUI, or entered at the console in PSSECMD. The output from activity PSEB is in the form of a
PSS
E Response File.
15.14.1 PSS
E Power Flow
operations through the use of English-like command macros. PSEB commands are created within
a text file using a text editor. Each record is in the form of a command starting with a verb from a
previously defined vocabulary. The PSEB commands are documented below and in the PSEB
Users Ready Reference.
PSEB commands do not interact with PSS
E dialog:
RECOVER FROM SAVNW.SAV
RECOVER saved case FROM SAVNW.SAV
A dollar sign ( $ ) at the end of a PSEB command line is used to continue the command on the
following line. At least one space must precede the dollar sign. As many physical lines as required
may be used to specify a single PSEB command as long as all lines except the last one are termi-
nated with a dollar sign. This multiline capability may be used with all PSEB commands except the
USE command (see below). In addition, each PSS
E Engineering
Basic PSEB Users Ready Reference sheet. Keywords shown in uppercase letters must be entered
as shown in either upper or lowercase characters.
HOLD [n] IN (saved-case-filename) [NOW]
The HOLD command is used to preserve the power flow working case in the designated
Saved Case File; refer to Section 5.44. When the HOLD command includes the optional
keyword NOW, activity SAVE is immediately executed. In this case, the PSS
E responses
for activity SAVE are not written to the Response File being constructed by activity PSEB.
When the HOLD command does not include the optional keyword NOW, the appropriate
entries in the Response File are made to save the working case during the subsequent
execution of the Response File.
RECOVER [n] FROM (saved-case-filename)
The RECOVER command is used to access the designated Saved Case File; refer to
Section 5.1. Activity CASE is executed immediately and the PSS
E 32.0
Building a Response File, Power Flow Calculation Program Operation Manual
15-24 Siemens Energy, Inc., Power Technologies International
|MW |
|MWP |
|MWI |
|ALTER | |MWY | [ |MW | ]
|CHANGE| |MVAR | LOAD [n] BUS (bus id) [LOAD (id)] TO (R) [ |MVAR| ]
|MVARQ|
|MVARI|
|MVARY|
This form of the ALTER command is used to change a specified component of a designated
load at a designated bus to a specified value. If the optional load identifier tokens are
omitted, a load identifier of 1 is assumed. The second token specified indicates the compo-
nent of load as follows:
The value specified is always in MW or Mvar at unity voltage. Refer to Load Data.
SHED LOAD [n] BUS (bus id)
The SHED command is used to set all loads at the specified bus out-of-service. Refer to
Load Data.
|MW |
|ALTER | |MWG | [|MW |]
|CHANGE| |MVAR | SHUNT [n] BUS (bus id) [SHUNT (id)] TO (R) [|MVAR|]
|MVARB|
This form of the ALTER command is used to change a specified component of a specified
fixed shunt at a designated bus to a specified value. If the optional shunt identifier tokens
are omitted, a shunt identifier of 1 is assumed. The second token specified selects either
the active (MW or MWG) or reactive (MVAR or MVARB) component of bus shunt. Values
entered are in MW or Mvar at unity voltage. The reactive component is specified as a nega-
tive quantity for an inductive load. Refer to Fixed Bus Shunt Data.
|ALTER |
|CHANGE| BUS (bus id) CODE TO (I)
This form of the ALTER command is used to change the bus type code of a designated bus.
Refer to Bus Data.
MW, MWP Active power component, constant power characteristic.
MWI Active power component, constant current characteristic.
MWY Active power component, constant admittance characteristic.
MVAR, MVARQ Reactive power component, constant power characteristic.
MVARI Reactive power component, constant current characteristic.
MVARY Reactive power component, constant admittance characteristic; R is
negative for an inductive load.
Siemens Energy, Inc., Power Technologies International 15-25
PSS
E 32.0
Building a Response File, Power Flow Calculation Program Operation Manual
15-26 Siemens Energy, Inc., Power Technologies International
This form of the RECONNECT command is used to return a specified branch to service. If
the optional circuit identifier tokens are omitted, a circuit identifier of 1 is assumed. The
branch status flag is set to 1; refer to Non-Transformer Branch Data and Section 5.8.1.
|DISCONNECT| [|CKT | ]
|TRIP |THREEWINDING [n] FROM [n] BUS (bus id) TO [n] BUS (bus id) TO [n] BUS (bus id)
[|CIRCUIT| (id)]
|OPEN |
This form of the DISCONNECT command is used to remove all windings of a specified
three-winding transformer from service. If the optional circuit identifier tokens are omitted,
a circuit identifier of 1 is assumed. The transformer status flag is set to zero; refer to Trans-
former Data and Section 5.8.1.
|DISCONNECT| [|CKT | ]
|TRIP |THREEWINDING [n] AT [n] BUS (bus id) TO [n] BUS (bus id) TO [n] BUS (bus id) [|CIRCUIT| (id)]
|OPEN |
This form of the DISCONNECT command is used to remove the winding connected to the
bus specified as the AT bus of a specified three-winding transformer from service. If the
optional circuit identifier tokens are omitted, a circuit identifier of 1 is assumed. The trans-
former status flag is set to 2, 3 or 4; refer to Transformer Data and Section 5.8.1.
|RECONNECT| [|CKT | ]
|CLOSE |THREEWINDING [n] FROM [n] BUS (bus id) TO [n] BUS (bus id) TO [n] BUS (bus id) [|CIRCUIT| (id)]
|RECLOSE |
This form of the RECONNECT command is used to return all windings of a specified three-
winding transformer to service. If the optional circuit identifier tokens are omitted, a circuit
identifier of 1 is assumed. The transformer status flag is set to 1; refer to Transformer Data
and Section 5.8.1.
BLOCK DCLINE (dc id)
The BLOCK command is used to block a specified two-terminal dc line. The control mode
is set to zero; refer to Two-Terminal DC Transmission Line Data.
UNBLOCK DCLINE (dc id)
The UNBLOCK command is used to unblock a specified two-terminal dc line. The control
mode is set to 1 (i.e., the UNBLOCK command assumes power control mode). Refer to
Two-Terminal DC Transmission Line Data.
|SETPOINT|
SET DCLINE (dc id) |SCHEDULE| TO (R)
This form of the SET command is used to change the current or power demand
(SETPOINT) or scheduled dc voltage (SCHEDULE) on a specified two-terminal dc line to
a designated value; refer to Two-Terminal DC Transmission Line Data.
SET LOADFLOW TITLE LINE |1| TO (title)
|2|
This form of the SET command is used to change the designated line of the two-line case
heading to a specified string. The title may be up to 60 characters and must be enclosed in
single quotes; refer to Case Identification Data.
Siemens Energy, Inc., Power Technologies International 15-27
PSS
E 32.0
Building a Response File, Power Flow Calculation Program Operation Manual
15-28 Siemens Energy, Inc., Power Technologies International
Terminate passthru mode (see above) and reinstate PSEB command mode.
|USE |
|COPY| (response-file-filename) [arg1 ... [arg9]]
|IDEV|
The USE command allows the user to include the BAT_ records (refer to PSS
E Applica-
tion Program Interface (API)) and/or PSS
E GUI Users Guide, Section 23.3.3, PSEB Command File, Power Flow Calculation
PSS
E 32.0
Building a Response File, Dynamic Simulation Program Operation Manual
15-30 Siemens Energy, Inc., Power Technologies International
15.15 Building a Response File, Dynamic Simulation
Activity PSAS
The simulation run assembler activity PSAS allows the user to specify dynamic simulation runs in
an English-like language. Input to activity PSAS is taken either from a PSAS Command File or from
the dialog input device. This can be in-stream in a Response File, typed into the command line in
the GUI, or entered at the console in PSSECMD. The output from activity PSAS is in the form of a
PSS
E Response File.
15.15.1 PSS
E Dynamics
simulations through the use of English-like command macros. PSAS commands are created within
a text file using a text editor. Each record is in the form of a command starting with a verb from a
previously defined vocabulary. The PSAS commands are documented below and in the PSAS
Users Ready Reference.
PSAS commands do not interact with PSS
E dialog:
RECOVER FROM SAVNW.SNP AND SAVNW.SAV
RECOVER snapshot and saved case FROM SAVNW.SNP AND SAVNW.SAV
A dollar sign ( $ ) at the end of a PSAS command line is used to continue the command on the
following line. At least one space must precede the dollar sign. As many physical lines as required
may be used to specify a single PSAS command as long as all lines except the last one are termi-
nated with a dollar sign. This multiline capability may be used with all PSAS commands except the
USE command (see below). In addition, each PSS
E Simulation Run
Assembler PSAS Users Ready Reference sheet. Keywords shown in uppercase letters must be
entered as shown in either upper or lowercase characters.
[|NOW |]
HOLD[n]IN(snapshot-filename)AND(saved-case-filename) [|SIZE[S](I1)(I2)(I3)(I4)(I5)|]
The HOLD command is used to preserve dynamics working memory and the power flow
working case in Snapshot and Saved Case Files respectively (refer to activities SNAP and
SAVE). When the HOLD command includes the optional keyword NOW, activity SNAP and
SAVE are immediately executed and the user specifies the number of dynamic simulation
array elements to save in the same manner as when activity SNAP is specifically invoked.
In this case, the PSS
E responses for activity SNAP and SAVE are not written to the
Response File being constructed by activity PSAS.
When the HOLD command does not include the optional keyword NOW, the appropriate
entries in the Response File are made to take a Snapshot and save the working case during
the subsequent execution of the Response File. In this case, the user may optionally
specify the keyword SIZES followed by the number of CONs, STATEs, VARs, ICONs and
output channels to be preserved. If this keyword and its data are omitted, a blank response
is generated in the Response File and, when the Response File is subsequently executed,
activity SNAP preserves up to the next available positions in the respective dynamics data
arrays.
Program Automation PSS
E 32.0
Building a Response File, Dynamic Simulation Program Operation Manual
15-32 Siemens Energy, Inc., Power Technologies International
RECOVER[n] FROM (snapshot-filename) AND (saved-case-filename) [NOFACT] [NOTYSL] [NORETURN]
The RECOVER command is used to access the designated Snapshot and Saved Case
Files (refer to activities RSTR and CASE). Activities RSTR and CASE are executed imme-
diately and the PSS
E responses for activities RSTR, LOFL, and CASE are written to the
Response File being constructed by activity PSAS. The activity commands FACT, TYSL,
and RTRN are included in the Response File unless they are suppressed with one or more
of the optional tokens NOFACT, NOTYSL and NORETURN. If NOFACT is specified,
NOTYSL is assumed. If NORETURN is specified, NOFACT and NOTYSL are also
assumed, and the next PSAS command must be either CONVERT, USE or PASS; the
CONVERT command (see below) generates the RTRN activity command but in passthru
mode (see below), the RTRN activity command must be specified before terminating
passthru mode.
The RECOVER command overwrites dynamics working memory and the power flow
working case. The HOLD command with the NOW option may be used before the
RECOVER command to preserve these two sets of data.
|INITIALIZE| OUTPUT |(filename)| [SNAPSHOT |(filename)|]
|START | |NONE | [ |NONE |]
This form of the START command is used to initialize the dynamic model in preparation for
state-space simulations. The STRT activity command is generated with user specified
channel output and Snapshot filename responses. The reserved token NONE may be used
to indicate that the corresponding filename is not to be specified.
|INITIALIZE| EXTENDED [n] OUTPUT |(filename)| [n]
|START | |NONE |
This form of the START command is used to initialize the dynamic model in preparation for
extended term simulations. The MSTR activity command is generated with a user specified
channel output filename response. The reserved token NONE may be used to indicate no
channel output file is to be specified.
|TO | |CYCLE[S] |
RUN [n] |FOR| (R) |SECOND[S]| [PRINT (I)] [PLOT (I)] [CRTPLT (I)]
The RUN command is used to perform dynamic simulation calculations with activity RUN
or MRUN. If the RUN command is preceded by the START command (see above), the form
of the START command determines whether activities RUN or MRUN is to be used. Other-
wise, state-space simulations are assumed and activity RUN is used. The real value indi-
cates the duration of the simulation calculation and may be specified in either seconds or
cycles. It is the value of simulation time (i.e., TPAUSE) when the token TO precedes it and
an incremental value of time when the token FOR precedes it. The optional integer tokens
and their corresponding keywords allow the user to specify channel printing and plotting
intervals (refer to Section 14.10). By default, PRINT=20, PLOT=5 and CRTPLT=0.
|OFF|
CONVERGENCE MONITOR |ON |
The CONVERGENCE MONITOR command is used to enable or disable the printing of the
network solution convergence monitor during the execution of the PSS
E activity calls
generated by subsequent START and RUN commands (see above). By default, the
convergence monitor is suppressed.
APPLY FAULT [n] BUS (bus id) [n]
Siemens Energy, Inc., Power Technologies International 15-33
PSS
E 32.0
Building a Response File, Dynamic Simulation Program Operation Manual
15-34 Siemens Energy, Inc., Power Technologies International
|LINE | [|CKT | ]
APPLY FAULT [n]|TIE |[n] FROM [n] BUS (bus id) TO [n] BUS (bus id) [n][|CIRCUIT|(id)] [n]
|BRANCH|
This form of the APPLY FAULT command is used to apply a solidly grounded three-phase
fault at the from bus end of a designated non-transformer branch. The Response File being
constructed by activity PSAS includes responses to use activity ALTR to change the line
shunt at the from bus end of the branch to j(-2.-10
7
). If the optional circuit identifier tokens
are omitted, a circuit identifier of 1 is assumed. Refer to Bus Data, activity ALTR and
Section 18.7.2.
|LINE | [|CKT | ]
APPLY FAULT [n] |TIE | [n] FROM [n] BUS (bus id) TO [n] BUS (bus id) [n] [|CIRCUIT| (id)] [n]
|BRANCH|
|Y | |MVA |
|ADMITTANCE| (R1) (R2) |MHO[S]| [BASEKV (R)]
This form of the APPLY FAULT command is used to apply a fault with a specified fault
admittance, (R1) + j(R2), at the from bus end of a designated non-transformer branch. The
Response File being constructed by activity PSAS includes responses to use activity ALTR
to change the line shunt at the from bus end of the branch. (R2) should be entered as a
negative number. If the optional circuit identifier tokens are omitted, a circuit identifier of 1
is assumed. Refer to Non-Transformer Branch Data, activity ALTR and Section 18.7.2.
If the MVA token is specified, the values specified as (R1) and (R2) are divided by the
system base MVA and the active and reactive components respectively of the line shunt at
the from bus end of the branch are set to these values. The fault admittance is therefore
specified on the record is in the same MVA units as is bus shunt (refer to Bus Data).
If the MHO or MHOS token is specified, (R1) and (R2) are entered in mhos and activity
PSAS converts them to the per unit values used for specifying line shunts. If the optional
base voltage tokens are specified, the base voltage specified on the PSAS command is
used in the conversion calculation; otherwise, the base voltage contained in the working
case for the designated from bus is used. In either case, a positive base voltage value is
required.
|LINE | [|CKT | ]
APPLY FAULT [n] |TIE | [n] FROM [n] BUS (bus id) TO [n] BUS (bus id) [n] [|CIRCUIT| (id)] [n]
|BRANCH|
|Z |
|IMPEDANCE| (R1) (R2) OHM[S] [BASEKV (R)]
This form of the APPLY FAULT command is used to apply a fault with a specified fault
impedance, (R1) + j(R2), at the from bus end of a designated non-transformer branch. The
Response File being constructed by activity PSAS includes responses to use activity ALTR
to change the line shunt at the from bus end of the branch. (R2) should be entered as a
positive number and (R1) and (R2) are specified in ohms. Activity PSAS converts them to
the per unit values used for specifying line shunts. If the optional base voltage tokens are
specified, the base voltage specified on the PSAS command is used in the conversion cal-
culation; otherwise, the base voltage contained in the working case for the designated from
bus is used. In either case, a positive base voltage value is required. If the optional circuit
identifier tokens are omitted, a circuit identifier of 1 is assumed. Refer to Non-Transformer
Branch Data, activity ALTR and Section 18.7.2.
Siemens Energy, Inc., Power Technologies International 15-35
PSS
E 32.0
Building a Response File, Dynamic Simulation Program Operation Manual
15-36 Siemens Energy, Inc., Power Technologies International
SHED LOAD [n] BUS (bus id)
The SHED command is used to set all loads to out-of-service at the specified bus. Refer to
Load Data.
|ALTER | |MWG | |LOAD | [|MW |]
|CHANGE| |MVARB| |SHUNT| [n] BUS (bus id) [SHUNT (id)] TO (R) [|MVAR|]
This form of the ALTER command is used to change a specified component of a specified
fixed shunt at a designated bus to a specified value. If the optional shunt identifier tokens
are omitted, a shunt identifier of 1 is assumed. The second token specified selects either
the active (MWG) or reactive (MVARB) component of bus shunt. Values entered are in MW
or Mvar at unity voltage. The reactive component is specified as a negative quantity for an
inductive load. Refer to Fixed Bus Shunt Data.
|ALTER |
|CHANGE| BUS (bus id) CODE TO (I)
This form of the ALTER command is used to change the bus type code of a designated bus.
Refer to Bus Data.
|ALTER | |R| [|CKT | ]
|CHANGE| |X| TO (R) [n] FROM [n] BUS (bus id) TO [n] BUS (bus id) [|CIRCUIT| (id)]
|B|
This form of the ALTER command is used to change the per unit resistance, reactance or
charging of a designated non-transformer branch or two-winding transformer to a specified
value. If the optional circuit identifier tokens are omitted, a circuit identifier of 1 is assumed.
Refer to Bus Data.
DROP PLANT [n] BUS (bus id)
This form of the DROP command is used to disconnect all generation at a specified bus.
The bus type code is set to one; refer to Bus Data and Section 5.8.1.
RECONNECT PLANT [n] BUS (bus id)
This form of the RECONNECT command is used to reconnect generation at a specified
bus. The bus type code is set to two; machine status flags are not changed. Refer to Bus
Data, Generator Data, and Section 5.8.1.
|UNIT |
DROP |GENERATOR| (id) [n] BUS (bus id)
|MACHINE |
|LOAD |
|SHUNT |
This form of the DROP command is used to disconnect a specified machine, load, or fixed
shunt at a designated bus. The machine, load, or shunt status flag is set to zero; refer to
Bus Data, Fixed Bus Shunt Data, and Section 5.8.1.
Siemens Energy, Inc., Power Technologies International 15-37
PSS
E 32.0
Building a Response File, Dynamic Simulation Program Operation Manual
15-38 Siemens Energy, Inc., Power Technologies International
BLOCK DCLINE (dc id)
The BLOCK command is used to block a specified two-terminal dc line. The control mode
is set to zero; refer to Two-Terminal DC Transmission Line Data.
UNBLOCK DCLINE (dc id)
The UNBLOCK command is used to unblock a specified two-terminal dc line. The control
mode is set to one (i.e., the UNBLOCK command assumes power control mode). Refer to
Two-Terminal DC Transmission Line Data.
|POWER |
|CURRENT |
SET [n] DCLINE (dc id) |SETPOINT| TO (R)
|SCHEDULE|
|VOLTAGE |
This form of the SET command is used to change the current or power demand (POWER,
CURRENT, SETPOINT) or scheduled dc voltage (SCHEDULE, VOLTAGE) on a specified
two-terminal dc line to a designated value; refer to Two-Terminal DC Transmission Line
Data.
|VAR|
SET [n] |CON| (I) TO (R)
This form of the SET command is used to change a specified VAR or CON to a designated
value. Refer to activity ALTR and 18.1.2.
|(C)|
SET [n] ICON (I) TO |(I)|
This form of the SET command is used to change a specified ICON to a designated integer
or character value. Refer to activity ALTR and 18.1.2.
|VAR[S]|
SET [n] |CON[S]| (I1) THRU (I2) TO (R1) ... (Rm)
This form of the SET command is used to change up to twenty-five consecutive VARs or
CONs to designated values. Refer to activity ALTR and 18.1.2.
|(C1)| |(Cm)|
SET [n] ICON[S] (I1) THRU (I2) TO |(I1)| ... |(Im)|
This form of the SET command is used to change up to twenty-five consecutive ICONs to
designated integer and/or character values. Refer to activity ALTR and 18.1.2.
[|CYCLE[S] |]
SET [n] STEP TO (R) (n) [|SECOND[S]|] [n]
This form of the SET command is used to change the simulation time step, DELT, to a des-
ignated value. The new time step may be specified in either seconds or cycles. When nei-
ther of the optional tokens is specified, SECONDS is assumed.
Siemens Energy, Inc., Power Technologies International 15-39
PSS
E output channels. It is
used in setting the responses for the starting channel, VAR and ICON indices to be used
by activity CHAN. If a NEXT command is not entered, or if the CHANNEL, VAR and/or
ICON keywords and values are omitted from the NEXT command, a corresponding default
response is generated in the Response File. When the Response File is subsequently
executed, activity CHAN will use the next available location pointers as contained in
dynamics data memory.
PLACE quantity [n] BUS (bus id) [MACHINE (id)] IN CHANNEL[S]
[WITH IDENTIFIER[S] (ident) [AND (ident)]]
This form of the PLACE command is used to assign a single machine quantity (two quan-
tities in the case of MACHAPPIMP) to an output channel. < quantity > may be specified as
one of the following machine related tokens:
If the optional machine identifier tokens are omitted, channels for all machines at the bus
are generated. The user may either specify the channel identifier(s) to be assigned to the
output channel(s) or let activity CHAN assign them. Refer to Tables 14-2 and 18-1, activity
ALTR, and Section 18.6.1.
|BSFREQ |
|VOLTAGE |
PLACE |VOLT&ANG| [n] BUS (bus id) IN CHANNEL[S]
[WITH IDENTIFIER[S] (ident) [AND (ident)]]
This form of the PLACE command is used to assign a single bus quantity (two quantities in
the case of VOLT&ANG) to an output channel. The user may either specify the channel
identifier(s) to be assigned to the output channel(s) or let activity CHAN assign them. Refer
to Tables 14-2 and 18-1, activity ALTR, and Section 18.6.1.
|PLOAD|
PLACE |QLOAD| [n] BUS (bus id) [LOAD (id)] IN CHANNEL[S]
[WITH IDENTIFIER (ident)]
This form of the PLACE command is used to assign a single load quantity to an output
channel. If the optional load identifier token is omitted, channels for all loads at the bus are
generated. The user may either specify the channel identifier to be assigned to the output
channel(s) or let activity CHAN assign it. Refer to Tables 14-2 and 18-1, activity ALTR, and
Section 18.6.1.
PLACE quantity [n] BUSES (I1) THRU (I2) IN CHANNEL[S]
This form of the PLACE command is used to assign a specified machine, bus, or load
related quantity to output channels for all machines, buses, or loads within a designated
bus number range. < quantity > is specified as in the three BUS forms of the PLACE
command given above. Refer to Tables 14-2 and 18-1, activity ALTR, and Section 18.6.1.
ANGLE PELEC QELEC ETERM ECOMP EFD PMECH
VREF SPEED XADIFD VOTHSG VUEL VOEL
MACHAPPIMP MACHITERM
Program Automation PSS
E 32.0
Building a Response File, Dynamic Simulation Program Operation Manual
15-40 Siemens Energy, Inc., Power Technologies International
|FLOWP | [|CKT | ]
PLACE |FLOWPQ | [n] BUS (bus id) TO [n] BUS (bus id) [|CIRCUIT| (id)]
|FLOWMVA|
|RELAY2 |
IN CHANNEL[S] [WITH IDENTIFIER[S] (ident) [AND (ident)]]
This form of the PLACE command is used to assign one or two branch related quantities
to output channels for a designated branch. If the optional circuit identifier tokens are
omitted, a circuit identifier of 1 is assumed. The second token specified indicates quantities
to be monitored as follows:
The user may either specify the channel identifier(s) to be assigned to the output channel(s)
or let activity CHAN assign them. Refer to Tables 14-2 and 18-1, activity ALTR, and
Section 18.6.1.
|3WNDFLOWP |
|3WNDFLOWPQ |
|3WNDFLOWMVA| [|CKT | ]
PLACE |3WNDRELAY3 | [n] BUS (bus id) TO [n] BUS (bus id) TO [n] BUS (bus id) [|CIRCUIT| (id)]
IN CHANNEL[S] [WITH IDENTIFIER[S] (ident) [AND (ident)]]
This form of the PLACE command is used to assign one or two branch related quantities
to output channels for the three-winding transformer winding connected to the first bus
specified. If the optional circuit identifier tokens are omitted, a circuit identifier of 1 is
assumed. The second token specified indicates quantities to be monitored as follows:
The user may either specify the channel identifier(s) to be assigned to the output channel(s)
or let activity CHAN assign them. Refer to Tables 14-2 and 18-1, activity ALTR, and
Section 18.6.1.
|VAR[S] |
PLACE |STATE[S]| (I1) [THRU (I2)] IN CHANNEL[S]
This form of the PLACE command is used to assign one or more consecutive VARs or
STATEs to output channels. Refer to Tables 14-2 and 18-1, activity ALTR, and
Section 18.6.1.
FLOWP One channel containing the active power flow on the branch.
FLOWPQ Two channels containing the active and reactive power flow on the branch.
FLOWMVA One channel containing the MVA flow on the branch.
RELAY2 Two channels containing the apparent impedance on the branch as n by
the RELAY2 model.
3WNDFLOWP One channel containing the active power flow into the winding.
3WNDFLOWPQ Two channels containing the active and reactive power flow into the
winding.
3WNDFLOWMVA One channel containing the MVA flow on the winding.
3WNDRELAY3 Two channels containing the apparent impedance on the winding
as n by the RELAY3 model.
Siemens Energy, Inc., Power Technologies International 15-41
PSS
E Applica-
tion Program Interface (API)) and/or PSS
E 32.0
Building a Response File, Dynamic Simulation Program Operation Manual
15-42 Siemens Energy, Inc., Power Technologies International
CHECK
The CHECK command instructs activity PSAS to bypass the automatic execution of the
Response File which it constructs (refer to Section 15.15.3).
END
The END command terminates PSAS command input. Unless it is otherwise suppressed
(refer to Section 15.15.3), the Response File constructed by activity PSAS is automatically
executed.
ABORT
The ABORT command terminates activity PSAS and bypasses the automatic execution of
the Response File which it has constructed.
HELP
This form of the HELP command displays the list of PSAS commands at the dialog output
device (refer to Section 4.4).
HELP,command
This form of the HELP command displays the syntax format of the specified PSAS
command at the dialog output device (refer to Section 4.4).
15.15.3 Operation of Activity PSAS
The user specifies either:
The name of the appropriate PSAS Command File (refer to Section 2.4.1). If the spec-
ified file does not exist or some other file system related error occurs, an appropriate
error message is printed and the request for the input device is repeated.
Data input from the users terminal. This applies to both interactive and Response File
operation of PSS
E.
The user specifies an output filename. Refer to Section 2.4.1 for the file specification conventions
used by activity PSAS. If a file system error occurs while opening the specified file, an appropriate
error message is printed. If no filename is specified, activity PSAS writes its output into a file for
which the name is of the form PSASnnn.IDV, where < nnn > is a number which is set such that the
resulting filename is a new file in the users directory.
When terminal input had been specified, activity PSAS issues the prompt PSAS: each time it is
ready to accept a new PSAS command. PSAS command input is terminated by entering either the
END or ABORT command.
When input is taken from a PSAS Command File, no prompts are issued. If the input file is not termi-
nated with either the END or ABORT command, the following message is printed:
OUT OF FILE DATA--SWITCH TO TERMINAL INPUT MODE
Additional PSAS command input records may then be entered from the users terminal.
If an error occurs in processing an input record, an appropriate error message is printed, the
offending record is ignored, and processing continues.
Siemens Energy, Inc., Power Technologies International 15-43
PSS
E is being operated in its Response File mode, all active Response Files are closed
and further user inputs to PSS
E 32.0
Building a Response File, Dynamic Simulation Program Operation Manual
15-44 Siemens Energy, Inc., Power Technologies International
The generation of the Response File entries corresponding to previously specified PLACE
commands cancels the parameters established by any previous NEXT command.
Additional Information
PSS
E GUI Users Guide, Section 23.3.4, PSAS Command File, Dynamic Simulation
PSS
E activities
executed under control of an IPLAN program respond to interrupt control codes in their normal
fashion. In addition, the IP interrupt control code may be used to terminate execution of an active
IPLAN program.
15.16.1 IPLAN Programs
IPLAN is high-level programming language designed to be utilized as an enhancement to existing
application programs such as PSS
E. The compiled IPLAN program in binary format is used as input to the IPLAN
simulator which is built into PSS
E.
Compiled IPLAN Files can be used in PSS
E 32.0
Launching an IPLAN Program File Program Operation Manual
15-46 Siemens Energy, Inc., Power Technologies International
15.16.2 Interaction With PSS
E
The IPLAN compiler and simulator recognize the Single Element Data Retrieval routines from the
PSS
E API. They are used in IPLAN CALL statements. This means that IPLAN programs can
assign various values from the PSS
E continues. PSS
E GUI is being used, a read from the dialog input device is forced after the IPLAN program
is loaded. While an IPLAN program is controlling the execution of PSS
E, input to PSS
E is
normally taken from the IPLAN program rather than from the PSS
E continues to accept input from the IPLAN program until either an IPLAN PAUSE, PAUSE
UNTIL, or PAUSE READ statement is executed; or the IPLAN program is terminated. At this time,
PSS
E looks to the dialog input device for its input, or control returns to the GUI.
The input conventions described above apply regardless of whether interactive operation is active,
the execution of the IPLAN program is initiated from a Response File, or the IPLAN program
PUSHes an @INPUT or @CHAIN command or an IDEV,filename activity command. IPLAN
Program Manual gives some examples describing the interaction of Response Files and IPLAN
programs when both are active simultaneously.
While the redirection of input to PSS
E execution results.
For details on the IPLAN programming language, the IPLAN language interface to the PSS
E
working case and dynamics data, and the IPLAN compiler, refer to the IPLAN Program Manual.
Additional Information
PSS
E 32.0
Launching an IPLAN Program File Program Operation Manual
15-48 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 16-1
Chapter 16
Result Retrieval
16.1 Python Modules for Result Retrieval
Activity Python Lists
PSS
E activity results into Python lists. Such lists then can be used to make customized
reports or for further processing using Python scripts. This chapter describes how to invoke these
APIs from PSS
E activity data and results and the EXCELPY module to write the data
and results to Excel spreadsheets.
EXCELPY is an auxiliary module that provides Python functions to create and populate
Excel spreadsheets.
Following sections describe just a few functions and give sample Python commands/code to illus-
trate how to use Python functions available in these modules. These Python commands can be
executed from either PSS
E CLI.
Result Retrieval PSS
E 32.0
pssarrays.accc_summary Program Operation Manual
16-2 Siemens Energy, Inc., Power Technologies International
16.2 pssarrays.accc_summary
Activity pssarrays.accc_summary
16.2.1 CLI
By importing the pssarrays module, the functions defined inside this module are made avail-
able outside of the module.
The accc_summary function can be called in any of the following ways:
Contingency Solution Output file is available in the working folder.
smry = pssarrays.accc_summary(r"savnw.acc")
import pssarrays
smry = pssarrays.accc_summary(r"savnw.acc")
or
smry = pssarrays.accc_summary(accfile=r"savnw.acc")
or
smry = pssarrays.accc_summary(accfile=r"c:\filepath\savnw.acc")
print smry.ierr
0
1
print smry.acccsize.nmline
11
2
print smry.file.acc
C:\Program Files\PTI\PSSE31 Alpha 2\EXAMPLE\savnw.acc
3
print smry.melement
(' 201 HYDRO 500.00 151 NUCPANT 500.00 1', ' 202
EAST500 500.00 152 MID500 500.00 1', ' 203 EAST230
230.00 154 DOWNTN 230.00 1', ' 205 SUB230 230.00 154
DOWNTN 230.00 1', ' 3001 MINE 230.00 3002 E. MINE
500.00 1', ' 3004 WEST 500.00 152 MID500 500.00 1', '
3004 WEST 500.00 3005 WEST 230.00 1', ' 3005 WEST
230.00 3008 CATDOG 230.00 1', ' 3006 UPTOWN 230.00 153
MID230 230.00 1', ' 3008 CATDOG 230.00 154 DOWNTN
230.00 1', ' 3008 CATDOG 230.00 3018 CATDOG_G 13.800 1', '
INTERFACE WEST', ' INTERFACE EAST')
print smry.mvbuslabel
(' 3001 MINE 230.00', ' 201 HYDRO 500.00', ' 202
EAST500 500.00', ' 203 EAST230 230.00', ' 204 SUB500
500.00', ' 205 SUB230 230.00', ' 206 URBGEN 18.000', '
211 HYDRO_G 20.000', ' 3001 MINE 230.00', ' 3002 E. MINE
500.00', ' 3003 S. MINE 230.00', ' 3004 WEST 500.00', '
3005 WEST 230.00', ' 3006 UPTOWN 230.00', ' 3007 RURAL
230.00', ' 3008 CATDOG 230.00', ' 3011 MINE_G 13.800', '
3018 CATDOG_G 13.800')
1
2
Siemens Energy, Inc., Power Technologies International 16-3
PSS
E
automation file to report on the basic data contained within an ACCC output file. Any Python code
can be added to this code to further process the returned values.
import pssarrays
smry = pssarrays.accc_summary(r"savnw.acc")
print smry.ierr
print smry.acccsize.nmline
print smry.file.acc
print smry.melement
print smry.mvbuslabel
3
Result Retrieval PSS
E 32.0
pssarrays.accc_solution Program Operation Manual
16-4 Siemens Energy, Inc., Power Technologies International
16.3 pssarrays.accc_solution
Activity pssarrays.accc_solution
The following Python code example shows how to get ACCC analysis results and write them to a
report.
import pssarrays
reptfile = 'accc_output.txt'
reptnam = open(reptfile,'w')
smry = pssarrays.accc_summary(accfile=r'savnw.acc')
rate = smry.rating.a
stype = 'con'
for lbl in smry.colabel:
soln = pssarrays.accc_solution(accfile=r'savnw.acc',
colabel=lbl,stype=stype,busmsm=0.5,sysmsm=5.0)
if soln == None: continue # contingency solution not found,
# move to next
if soln.ierr !=0: continue # return any non-zero ierr
reptnam.write("CONTINGENCY EVENTS\n")
# (1) contingency events summary
cnvflag = soln.cnvflag
cnvcond = soln.cnvcond
island = ("%d" % soln.island).center(7)
mvaworst = soln.mvaworst
mvatotal = soln.mvatotal
for jj in range(len( soln.codesc)):
desc = soln.codesc[jj]
if jj == 0:
reptnam.write("%(lbl)s %(desc)s %(cnvflag)s \
%(cnvcond)s %(island)s %(mvaworst)11.4f \
%(mvatotal)11.4f\n" % vars())
else:
tmp = 12*' '
reptnam.write("%(tmp)s %(desc)s\n" % vars())
if not cnvflag:
reptnam.write("\n================================\n")
continue # consider solution for converged cases only
# (2) flows
txtstr = ''
Siemens Energy, Inc., Power Technologies International 16-5
PSS
E 32.0
pssarrays.accc_solution Program Operation Manual
16-6 Siemens Energy, Inc., Power Technologies International
reptnam.write("\nGENERATOR DISPATCH\n")
for jj in range(len( soln.gdispbus)):
reptnam.write("%25s %11.2f %11.2f %12s\n" % \
(soln.gdispbus[jj], soln.gendisp[0][jj],
soln.gendisp[1][jj], lbl))
# (6) phase shifter
if stype in ['caction','corrective action','cor'] and \
len( soln.phsftr):
reptnam.write("\nPHASE SHIFTER ANGLE\n")
for jj in range(len( soln.phsftr)):
reptnam.write("%54s %12.2f %11.2f %12s\n" % \
(soln.phsftr[jj], soln.phsftrang[0][jj],
soln.phsftrang[1][jj],lbl))
reptnam.write("\n================================\n")
reptnam.close()
print "ACCC Solution saved in file %s." % reptfile
Siemens Energy, Inc., Power Technologies International 16-7
PSS
E 32.0
pssexcel.accc Program Operation Manual
16-8 Siemens Energy, Inc., Power Technologies International
16.5 pssexcel.accc
Activity pssexcel.accc
Using the pssarrays module, ACCC analysis results are retrieved from an *.acc input file and then,
using the excelpy module, these results are written to Excel Spreadsheets.
The Python commands below create a savnw_acc.xls file and the following worksheets populated
with ACCC Corrective Action solution data from the "savnw.acc" file for contingencies base case
and trip1nuclear. If a colabel value is not provided, all contingencies are considered. Also the
extended bus names of monitored branches and buses are split into three Excel spread columns
(namesplit=True). The argument show=True displays the workbook when it is being populated.
test Summary
test Contingency Events
test Branch Flow
test Interface Flow
test Bus Voltage
Test Load Shed
test Generator Dispatch
test Phase Shifter Angle
import pssexcel
pssexcel.accc(accfile = r"savnw.acc",
string = ['b','e','g','i','l','p','s','v'],
colabel = ['base case', 'trip1nuclear'],
stype = 'cor',
busmsm = 0.5,
sysmsm = 5.0,
rating = 'a',
namesplit = True,
xlsfile = r'savnw_acc.xls',
sheet = 'test',
overwritesheet = True,
show = True
)
In the command above, accfile and string are the only mandatory arguments. The worksheets
to create are defined by the string argument.
Siemens Energy, Inc., Power Technologies International 16-9
PSS
E 32.0
excelpy Examples Program Operation Manual
16-10 Siemens Energy, Inc., Power Technologies International
16.7 excelpy Examples
Activity excelpy Examples
16.7.1 Export QV Solution to Excel Spreadsheet
The following Python code writes QV solution summary and bus voltage results from "savnw.qv" file
to the Excel spreadsheet testqv.xls.
Using the pssexcel.qv function
import pssexcel
pssexcel.qv(qvfile = r"savnw.qv",
string = ['s','v'],
colabel = ['base case', 'trip1nuclear'],
namesplit = False,
xlsfile = r'testqv.xls',
sheet = '',
overwritesheet = True,
show = True
)
Using the pssarrays and excelpy modules
The following example illustrates how the pssarrays and excelpy modules can be used to
export PSS
E 32.0
excelpy Examples Program Operation Manual
16-12 Siemens Energy, Inc., Power Technologies International
minvstp = smry.minvstp[i]
maxvstp = smry.maxvstp[i]
minmvar = smry.minmvar[i]
maxmvar = smry.maxmvar[i]
maxmsm = smry.maxmsm[i]
for j in range(len(smry.codesc[i])):
dsc = smry.codesc[i][j]
if j==0:
conlst.append([srnum,nam,minvstp,maxvstp,minmvar,
maxmvar,maxmsm,dsc])
else:
conlst.append(['' ,'' ,'' ,'' ,'' ,'' ,'' ,dsc])
row += 1
bottomRow,rightCol = qvxls.set_range(row,col,conlst)
qvxls.font_color((row,col,row,rightCol), "dgreen")
qvxls.font((row,col+2,bottomRow,col+3),numberFormat='0.00')
qvxls.font((row,col+4,bottomRow,col+6),numberFormat='0.000')
qvxls.align((row,col),'right')
qvxls.font((row,col,row,rightCol),fontStyle=('Bold',))
qvxls.autofit_columns((row,col+1,row,rightCol))
# done qvsummary worksheet
# populate qvvolts worksheet
mvbuslabel = list(smry.mvbuslabel)
mvbuslabel.insert(0,'VOLTAGE SETPOINT->')
qvxls.set_active_sheet('qvvolts')
row, col = 1, 1
for lbl in colabel:
soln = pssarrays.qv_solution(qvfile,lbl)
if soln==None: continue # contingency solution not found
if soln.ierr !=0: continue # solution with error
contitle = 'CONTINGENCY: ' + lbl.strip()
# assemble data in columns: 1st=MW Transfer, rest=bus voltages
tmplst = [ mvbuslabel ]
for i in range(len(soln.vsetpoint)):
t = list(soln.volts[i])
t.insert(0,soln.vsetpoint[i])
Siemens Energy, Inc., Power Technologies International 16-13
PSS
E 32.0
excelpy Examples Program Operation Manual
16-14 Siemens Energy, Inc., Power Technologies International
]
row=1
col=1
testxls.set_cell(value="How to use EXCELPY module?",
address=(row,col),fontName="Arial",fontSize=12,
fontColor='red',fontStyle=('Bold','italic'))
row = row+2 #add one blank row
bottomRow, rightCol =
testxls.set_range(row,col,testdata,transpose=False)
testxls.font((row,1,row,rightCol),fontStyle='bold',fontColor='blue')
testxls.align((row,1,row,rightCol),alignv='h_center')
testxls.align((row,1,bottomRow,2),alignv='h_center')
testxls.autofit_columns((row,2,row,rightCol))
testxls.font((row,3,bottomRow,3),numberFormat='0.000')
xlsfile = testxls.save(xlsfile)
print "Excel workbook saved to %s file.\n"% xlsfile
Siemens Energy, Inc., Power Technologies International 17-1
Chapter 17
Miscellaneous Activity
Descriptions
This chapter contains operational descriptions of those PSS
E 32.0
Terminating PSS
E
Activity STOP
The PSS
E.
If the working case represents a system condition that may be needed in the future, the user should
ensure that it is preserved in a Saved Case File prior to selecting activity STOP. A similar argument
applies to preserving dynamics working memory in a Snapshot File.
Run Activity STOP - GUI
Run Line Mode Activity STOP - CLI
ACTIVITY?
>>STOP
Interrupt Control Codes
None
Additional Information
PSS
E
Siemens Energy, Inc., Power Technologies International 17-3
PSS
E.
Activity USER is not sensitive to any interrupt control code options.
Run Line Mode Activity USER - CLI
ACTIVITY?
>>USER
Interrupt Control Codes
None
Additional Information
Additional Resources for PSS
E 32.0
Displaying Help Information Program Operation Manual
17-4 Siemens Energy, Inc., Power Technologies International
17.3 Displaying Help Information
Activity HELP
The line mode activity HELP prints brief summary documentation at the Progress device.
For Future PSS
E as prompt, or
dialog, information is sent. The PSS
E 32.0
Selecting Alert Output Destination Program Operation Manual
17-6 Siemens Energy, Inc., Power Technologies International
17.5 Selecting Alert Output Destination
Activity ODEV
Selecting the alert output destination controls where output identified in PSS
E as alert information
is sent. The PSS
E as progress
information is sent. The PSS
E GUI.
The destination specified for progress may be the same file or printer that is used for any or all the
other virtual output devices. Output may be directed to the Report device, in which case progress
output will be handled as part of that output.
When a printer is specified for the progress device, the output is normally not printed until either
progress output is reassigned elsewhere or PSS
E 32.0
Selecting Report Output Destination Program Operation Manual
17-8 Siemens Energy, Inc., Power Technologies International
17.7 Selecting Report Output Destination
Activity OPEN
Selecting the report output destination controls where output identified in PSS
E as report informa-
tion is sent. The PSS
E user.
The line mode activity OPEN instructs the user to select the device to be used for these tabulations
and presents a menu of choices. Specifying either zero or one to the device selection request
assigns report output to the users terminal, or the Report window in the PSS
E GUI.
The destination specified for reports may be the same file or printer that is used for any or all the
other virtual output devices. Output may be directed to the progress device, in which case report
output will be handled as part of that output.
When a printer is specified for the report device, the output is normally not printed until either report
output is reassigned elsewhere or PSS
E 32.0
Setting the Path for Use with & Filenames Program Operation Manual
17-10 Siemens Energy, Inc., Power Technologies International
17.9 Setting the Path for Use with & Filenames
Activity PATH
The directory path specification activity PATH allows the user to specify a directory name. Then,
whenever a simple filename preceded by an ampersand (e.g., &myfile) is specified to a PSS
E file
accessing activity, the file is opened in the directory specified to activity PATH rather than in the
users current directory. Refer to Section 2.4.2.
Run Activity PATH - GUI
I/O Control>Set path for use with "&" filenames (PATH)
[Define PATH by selecting any file in the desired directory]
Run Line Mode Activity PATH - CLI
ACTIVITY?
>>PATH
ENTER PATHNAME PREFIX FOR USE WITH '&' FILE NAMES
>>
Interrupt Control Codes
None
Additional Information
PSS
E GUI Users Guide, Section 24.2, Setting the Path for Use with & Filenames
PSS
E Program Settings
17.10 Changing PSS
E Program Settings
Activity OPTN
The PSS
E option setting activity OPTN enables the user to override most of the default option
settings as established when PSS
E.
When saved, activity OPTN preserves the current settings of most PSS
E options in a PSS
E
Options File (see Sections 17.10.1, 2.3.7, and 3.3.3).
When invoked in line mode, activity OPTN displays the current settings of all options which may be
modified. The user may re-specify any option. Following such a change, the option menu is again
displayed with any new setting shown.
PSS
E is installed
on the system are in effect. These are overridden by the settings contained in a PSS
E Options
File if one is found in the users current or home directory or in the PSS
E follows the directory search sequence described in Section 2.1 when looking for the PSS
E
Options File.
Most PSS
E option settings are stored with the working case when it is saved with activity SAVE.
When a power flow case is retrieved with activity CASE, the option settings contained in it override
those then set in working memory. Any time activity CASE changes an option setting, an appro-
priate message is printed.
Run Activity OPTN - GUI
Misc>Change program settings (OPTN)
[Program Settings]
Run Line Mode Activity OPTN - CLI
ACTIVITY?
>>OPTN
PRESENT OPTION SETTINGS ARE:
Interrupt Control Codes
None
Additional Information
PSS
E 32.0
Returning Activity Selection to Dynamic Simulation Program Operation Manual
17-12 Siemens Energy, Inc., Power Technologies International
17.11 Returning Activity Selection to Dynamic Simulation
Activity RTRN
Note: Starting with PSS
E-31, mode switching is not apparent to the user and need not be done
explicitly. It is retained only for backwards compatibility.
The return to dynamics activity RTRN allows the user to execute any dynamics activity after having
been operating in power flow mode.
Activity RTRN coordinates dynamics model data and network data by performing the following
steps:
1. It coordinates the power flow machine electrical power arrays and the dynamic simulation
machine electrical power arrays.
2. It sets up a translation array (NUMTRM) indexed by internal machine sequence number and
pointing to the associated network bus. Out-of-service machines have their corresponding
NUMTRM entries set to a negative number.
3. It sets up a translation array (NUMLOD) indexed by internal load sequence number and
pointing to the associated network bus. Out-of-service loads have their corresponding
NUMLOD entries set to a negative number.
4. It sets up a translation array (RINCNX) indexed by internal double entry branch index and
pointing to the associated branch relay model connection table entry.
5. It updates internal pointer arrays used in associating dynamic simulation models with the
machine and load indexing contained in the power flow working case.
6. It updates output channel addresses to reflect any changes in the internal sequence
numbering of buses, machines, and loads in the working case.
7. It builds translation arrays DC2CNX, DCMCNX, VSCCNX, and FCTCNX for two-terminal dc
lines, multi-terminal dc lines, VSC dc lines, and FACTS devices, respectively. These arrays
are indexed by the internal device index in the power flow working case and point to the
dynamic model associated with the corresponding two-terminal dc line, multi-terminal dc
line, VSC dc line, or FACTS device, as appropriate.
8. It sets up a translation array (AUXLOC) indexed by internal auxiliary signal model number
and pointing to the internal device index of the two-terminal dc line, multi-terminal dc line,
VSC dc line, or FACTS device associated with the auxiliary signal model.
Run Line Mode Activity RTRN - CLI
ACTIVITY?
>>RTRN
Interrupt Control Codes
None
Siemens Energy, Inc., Power Technologies International 17-13
PSS
E 32.0
Editing the Case Heading or Long Title Program Operation Manual
17-14 Siemens Energy, Inc., Power Technologies International
17.12 Editing the Case Heading or Long Title
Activity EDTR
The title editing activity EDTR allows the user to perform editing operations on the two line case
heading and on the sixteen line long title. It is accessible only as a command line activity. In the GUI
the Case Titles dialog (activity CHTI) provides convenient editing ability. See also activity CHNG.
When either the two line case heading or the sixteen line long title is selected, the user specifies a
valid line number and appropriate editing commands.
The general form of each editing command is XnA where:
As an example, consider the command C2/WX/YZ/, where C specifies the change command, 2
specifies that the change is to be performed twice, and /WX/YZ/ is the argument to the change
command. This command searches the displayed title line for the first two occurrences of WX and
replaces them with YZ.
The / characters used in this example are delimiters and are used to separate the two strings
required by the change command. Valid delimiters are: . / $ % ! : ' " and &. Any one of these delim-
iters may be used as long as it does not occur in either of the specified strings. (The starting, middle,
and ending delimiter characters must, of course, all be the same.)
Several edit commands can be strung together in a single editing command input line. Prior to
executing each editing command input line, an internal edit pointer is initialized to point to column
one of the line being edited. As each edit command of the command input line is executed, this
pointer moves toward the right end of line being edited. In other words, the editing proceeds from
left to right, with each new editing command in the command input line starting where the previous
one ended. For example, the command C/AB/CD/C/WX/TY/ would cause the first occurrence of AB
to be replaced with CD and the first occurrence of WX after the original AB to be replaced with TY.
Whenever an error condition is encountered in performing the operations specified in an editing
command input line, an appropriate error message is printed and the line is unchanged.
Run Line Mode Activity EDTR - CLI
ACTIVITY?
>>EDTR
EDITOR OPTIONS ARE:
Interrupt Control Codes
None
X Is a single letter editing command as described below.
n Is a number in the range of 1 through 32000 (default is 1) which specifies the number of times that
the command is to be executed. Alternatively, n may be specified as an asterisk ( - ), indicating that
the given command is to be executed as many times (perhaps zero times) as possible for the
displayed line.
A Are the argument(s), if any, required for a given command.
Siemens Energy, Inc., Power Technologies International 17-15
PSS
E 32.0
Editing the Case Heading or Long Title Program Operation Manual
17-16 Siemens Energy, Inc., Power Technologies International
Following are several examples of using the editing commands.
Example 1: Simple C(hange) commands.
Assume that a title line originally contains ABCADEF. The edit command C/B/XY/ changes
it to AXYCADEF, while the command C2/A/MN/ results in a line of MNBCMNDEF. Note that
the second change command could have been written as C*:A:MN:, where an asterisk is
used instead of an explicit count and a different delimiter is being used.
Two (or more) change commands can be specified as one EDTR command. For example,
assume that the title line originally contains ABCABCABC and that the edit command
C/B/X/C/A/Q/ is given. The resulting line is AXCQBCABC. Note that the first A was not
changed, because the second C(hange) command started where the first C(hange)
command left off (and not at the beginning of the line).
Example 2: The F(ind), I(nsert), and D(elete) commands.
Assume that a title line originally contains ABCDEF. The edit command F/C/I/NEW/ results
in the title line containing ABNEWCDEF. Note that the string NEW is inserted directly
before the character that was located with the F(ind) command. Starting with the same orig-
inal line, the edit command F/C/D2I/NEW/ results in the title line containing ABNEWEF,
where the D(elete) command has removed the original CD characters.
Example 3: The O(verlay), A(ppend), and M(ove) commands.
Assume once more that the line originally contains ABCDEF. The edit command
F/C/O/xxx/A/stuff/ results in a line containing ABxxxFstuff. Starting with the original line, the
edit command M3O/bigstuff/ results in the title line ABCbigstuff. Note that this command
would have failed if there were not enough room in the title line to hold the additional char-
acters.
Additional Information
PSS
E 32.0
Listing Saved Case or Snapshot Files Program Operation Manual
17-18 Siemens Energy, Inc., Power Technologies International
17.14 Listing Saved Case or Snapshot Files
Activity SHOW
The Saved Case and Snapshot File summary activity SHOW lists the case headings of Saved Case
and Snapshot Files contained in the current directory. This list is printed to the Progress device
(see Section 4.4). Separate lists of Saved Case or Snapshot Files may be specified.
Each file listed is followed by the report of activity SIZE if the file is a Saved Case File, or a tabulation
of the number of dynamics data array elements stored in the file if it is a Snapshot File. In addition,
on some host computers activity SHOW allows the specification of pathnames as well as simple
filenames. The actual implementation of activity SHOW differs among the various host computers
of PSS
E.
Run Activity SHOW - GUI
File>File information (SIZE/SHOW/BUSN)
[File Information]
OPTION: List Save case and Snapshot files
Run Line Mode Activity SHOW - CLI
ACTIVITY?
>>SHOW
ENTER INPUT FILE NAME (0 TO EXIT, 1 FOR TERMINAL):
>>
Interrupt Control Codes
None
Additional Information
PSS
E
work session.
On subsequent executions of activity TIME it prints a summary of elapsed time, in seconds, since
the previous execution of activity TIME, and cumulative times from the point at which the timers
were last initialized. It also prints two additional system dependent timing statistics, at least one of
which indicates CPU utilization. This tabulation, which is printed to the Progress device, is of the
form:
FRI, MAY 23 2003 15:21 ELAPSE heading2 heading3
SINCE LAST "TIME" XX.XXX XX.XXX XX.XXX
CUMULATIVE XX.XXX XX.XXX XX.XXX
Run Activity TIME - GUI
Misc>Reset timing statistics to zero (TIME,INIT)
Misc>Display timing statistics (TIME)
Run Line Mode Activity TIME - CLI
ACTIVITY?
>>TIME, INIT
DAY, MMM DD YYYY H:M - TIMER INITIALIZED
Interrupt Control Codes
None
Additional Information
PSS
E 32.0
Inserting Comments into the Progress Output Program Operation Manual
17-20 Siemens Energy, Inc., Power Technologies International
17.16 Inserting Comments into the Progress Output
Activity TEXT
The null activity TEXT doesnt manipulate power flow data. However, it does provide a mechanism
by which the user may insert descriptive comments in a Response File at any point at which the
next activity to be executed is specified. In addition, it enables the user to insert comments in the
Progress output of the PSS
E GUI Users Guide, Section 23.5, Inserting Comments into the Progress Output
PSS
E 32.0
Inserting Comments into the Progress Output Program Operation Manual
17-22 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International 18-1
Chapter 18
Dynamic Simulation Setup
and Procedures
The user of PSS
E 32.0
Simulation Overview Program Operation Manual
18-2 Siemens Energy, Inc., Power Technologies International
Figure 18-1. Dynamic Simulation Basic Logic Flow
Time Derivative Calculation
Data Assimilation
Initialization
Network Solution
Numerical Integration
Advance Time
Optionally Apply
Disturbances
Output
Siemens Energy, Inc., Power Technologies International 18-3
PSS
E. The equipment modeling requirements of (2) and (3) above are satisfied through the use
of specialized equipment model subroutines, each of which contains the coded equations for
modeling one specific type of equipment. The PSS
E is structured such that users may develop and use their own
model subroutines whenever there is no standard library model which accurately models a given
item of equipment (see Chapter 20).
After equipment models for the system under study are selected, the user must supply the intelli-
gence connecting these models to the machines, buses, dc lines, and other equipment in the
electric network. This information is imbedded within ten subroutines:
TBLCNC Is supplied as a part of PSS
E has the provision to call user written plant and wind related models
directly from TBLCNC and TBLCNT.
Dynamic Simulation Setup and Procedures PSS
E 32.0
Simulation Overview Program Operation Manual
18-4 Siemens Energy, Inc., Power Technologies International
It is the users responsibility to supply the subroutines CONEC and CONET if there are user model
calls in these two subroutines. While subroutines CONEC and CONET bear modeling responsibility,
often they contain no user-written code at all, but are simply a sequence of FORTRAN CALL state-
ments connecting models from the PSS
E dynamic simulation data structure contains a group of named arrays, related to buses,
machines and loads, that comprise quantities that are frequently needed as input and output in
setting up and displaying the results of dynamic simulations. These include arrays such as VOLT,
BSFREQ, MBASE, PELEC, EFD, TPLOAD etc. PSS
E
has the provision to call user written load-related models directly from TBLCNC and
TBLCNT.
USRREL Is responsible for calling user-written line relay models. Calls to USRREL are initi-
ated from TBLCNT. Staring PSS
E
has the provision to call user written FACTS device models directly from TBLCNC
and TBLCNT.
USRDCL Is responsible for calling user-written dc line models. Calls to USRDCL are initiated
from TBLCNC and TBLCNT. Staring PSS
E has
the provision to call user written dc line models directly from TBLCNC and TBLCNT.
Siemens Energy, Inc., Power Technologies International 18-5
PSS
E
supplied models is shown in data sheets; refer to PSS
E Model Library.
Although the user must understand this process, the bookkeeping chore of assigning blocks of
storage locations for each model reference is handled by the PSS
E.
CON Contains constants.
STATE Contains state variables.
VAR Contains algebraic variables.
ICON Contains integer quantities which may be either constants or algebraic variables.
Corresponding to each ICON is an entry in the CHRICN array which may contain
character quantities.
Table 18-1. Dynamic Simulation Arrays
Array Contents Indexed By
Constants:
CON General constants (real) CON number
ICON General constants (integer) ICON number
CHRICN General constants (character) ICON number
MBASE Machine base MVA Machine index
ZSORCE Machine impedance (complex) Machine index
XTRAN Step-up transformer impedance (complex) Machine index
GENTAP Step-up transformer tap ratio Machine index
State Variables:
STATE General state variable array (state-space) STATE number
Dynamic Simulation Setup and Procedures PSS
E 32.0
Simulation Overview Program Operation Manual
18-6 Siemens Energy, Inc., Power Technologies International
Algebraic Variables:
VAR General algebraic variable array VAR number
VOLT Bus pu voltages (complex) Bus sequence number
BSFREQ Bus pu frequency deviations Bus sequence number
ANGLE Machine relative rotor angle (degrees) Machine index
PELEC Machine electrical power (pu on SBASE) Machine index
QELEC Machine reactive power (pu on SBASE) Machine index
ETERM Machine terminal voltage (pu) Machine index
EFD Generator main field voltage (pu) Machine index
PMECH Turbine mechanical power (pu on MBASE) Machine index
SPEED Machine speed deviation from nominal (pu) Machine index
XADIFD Machine field current (pu) Machine index
ECOMP Voltage regulator compensated voltage (pu) Machine index
VOTHSG Stabilizer output signal (pu) Machine index
VUEL Minimum excitation limiter output signal (pu) Machine index
VOEL Maximum excitation limiter output signal (pu) Machine index
TPLOAD Effective MW load (pu on SBASE) Load index
TQLOAD Effective Mvar load (pu on SBASE) Load index
DC2SIG Auxiliary-signal input for 2-terminal dc line models
auxiliary signal index and 2-terminal dc
line index
DCMSIG
Auxiliary-signal input for multi-terminal dc line
models
auxiliary signal index and multi-terminal
dc line index
VSCSIG Auxiliary-signal input for VSC dc line models Auxiliary signal index and VSC index
FCTSIG Auxiliary-signal input for FACTS device models
Auxiliary signal index and FACTS
device index
VRFDBK AVR rate feedback output Machine Index
VFEOUT AVR VFE signal Machine index
WVLCTY * Wind velocity, m/s Wind machine index
WTRBSP * Wind turbine rotor speed deviation (pu) Wind machine index
WPITCH * Pitch angle (degree) Wind machine index
WAEROT * aerodynamic torque (pu on MBASE) Wind machine index
WROTRV * Rotor voltage (pu on MBASE) Wind machine index
WROTRI * Rotor current (pu on MBASE) Wind machine index
WPCMND *
Active power command from wind control (pu on
MBASE)
Wind machine index
WQCMND *
Reactive power command from wind control (pu on
MBASE)
Wind machine index
Table 18-1. Dynamic Simulation Arrays (Cont.)
Siemens Energy, Inc., Power Technologies International 18-7
PSS
E 32.0
Simulation Overview Program Operation Manual
18-8 Siemens Energy, Inc., Power Technologies International
RINCNX Branch relay model connection table index Double entry branch index
INTICN Integer memory array ICON number
STRTAU Starting array indices for auxiliary-signal models
Auxiliary-signal array allocation table
index
STRTFC Starting array indices for FACTS device models FACTS device connection index
STRT2D Starting array indices for two-terminal dc line models two-terminal dc line connection index
STRTMD
Starting array indices for multi-terminal dc line
models
multi-terminal dc line connection index
STRTVS Starting array indices for VSC dc line models VSC dc line connection index
FCTCNX FACTS device connection table index FACTS device index
DC2CNX Two-terminal dc line connection table index Two-terminal dc line index
DCMCNX Multi-terminal dc line connection table index Multi-terminal dc line index
VSCCNX VSC dc line connection table index VSC dc line index
STRTSS Starting array indices for switched shunt models Switched shunt connection index
* Can be used only for wind machine models (i.e., models for machines that are designated as wind
machines in power flow).
Table 18-1. Dynamic Simulation Arrays (Cont.)
Siemens Energy, Inc., Power Technologies International 18-9
PSS
E allows the user to execute power flow activities (i.e., those activities described in Chapter 6)
at any point during a dynamic simulation run. This is accomplished by selecting the network tab on
the PSS
E GUI.
The interface elements for the Dynamics study elements of PSS
E GUI. Moving from the power flow to dynamics window has the effect of setting up
the translation arrays NUMTRM, NUMLOD, RINCNX, FCTCNX, DC2CNX, DCMCNX, VSCCNX
etc. (see Table 18-1), updating the plant-related, load-related, line relay model, FACTS device, VSC
(Voltage Source Converter) dc line connection tables etc., (see Sections 18.1.1 and 18.4), updating
the output channel addresses (see Section 18.6), and transferring control back to dynamic simula-
tion activity selection.
The principal applications of the power flow linkage are to:
1. Set up the power flow working case and to establish the admittance matrix temporary file (if
the factored matrix is not constructed prior to running the dynamic simulation, PSS
E will
run the factorization).
2. Allow examination of the network conditions existing at any instant of a simulation.
The required sequencing of PSS
E 32.0
The Network Model Program Operation Manual
18-10 Siemens Energy, Inc., Power Technologies International
18.3 The Network Model
Every dynamic simulation is based upon a power flow Saved Case that provides it with the required
transmission network data, load data, machine positive sequence characteristic data (i.e., MBASE,
ZSORCE, XTRAN and GENTAP), and the initial network condition from which the dynamic models
are initialized. Thus, the dynamics data structure with its corresponding connection subroutines
described in Section 18.1.2 is augmented by the power flow working case to form a system model
of the form required for dynamic simulations.
The power flow Saved Case must be present in the working case and be converted from its stan-
dard power flow form to the form required for dynamic simulations. In power flow, most generators
are represented by specifying their desired bus voltage magnitudes and active power outputs; their
voltage phase angles and reactive power outputs, within specified limits, are free variables which
are determined by the power flow solution activities. In dynamics, generators are represented by
their Norton equivalents as current sources. This conversion of machines from their power flow
model to their Norton equivalent is handled by activity CONG. The determination of the initial source
current (ISORCE) by activity CONG is based upon the machine power outputs and bus voltages,
along with the impedance data in the working case characterizing each machine. Activity CONG
converts all power flow Type 3 (swing) buses to Type 2.
The constant MVA load representation used in conventional power flow solutions is usually not an
acceptable load characteristic for dynamic simulations. The basic conversion of loads from their
constant MVA representation to an arbitrary combination of constant MVA, current and admittance
is handled by activity CONL. The modeling of loads beyond this level is handled by applying models
from the library of load characteristic models.
It is then recommended that activities FACT and TYSL be executed to fine tune the solution, and
that the converted case be preserved in a Saved Case File. The file specified to activity SAVE
should not be the same one from which the original (unconverted) case was picked up because
the use of activity CONG renders the working case and its Saved Case image invalid for the stan-
dard power flow solution activities, and activity CONG is not reversible.
To summarize, then, the following sequence should be followed in setting up the converted network
model for use in dynamic simulations:
1. Pick up a standard power flow case with activity CASE.
2. Using the power flow solution activities, solve the working case to an acceptable mismatch
level. The bus boundary conditions should represent the desired initial network condition
from which the dynamic simulation is to be initialized.
3. Ensure that the machine characteristic data MBASE, ZSORCE, XTRAN and GENTAP are
properly entered for all machines in the working case (see Generator Data and activities
MCRE and CONL).
4. Preserve the unconverted initial network condition in a power flow Saved Case File with
activity SAVE.
5. Execute activities CONG and CONL.
6. Optionally, execute activities FACT and TYSL. Although not essential, this step is
recommended.
7. Save the converted case in a Saved Case File other than the one specified in (4).
Siemens Energy, Inc., Power Technologies International 18-11
PSS
E is comprised of:
1. The power flow working case, giving a positive sequence representation of the electric
network. A standard power flow case must be augmented by the machine impedance char-
acteristic data MBASE, ZSORCE, XTRAN and GENTAP, and the load and generator
representations must be converted from their power flow modeling to that required by the
dynamic simulation activities. Refer to Sections 18.3 and 6.3.13, Generator Data, and activ-
ities MCRE, CONG, and CONL.
2. Dynamics data working memory which includes: (1) the constants associated with equip-
ment models from the PSS
E program structure.
18.4.1 Subroutines TBLCNC and CONEC
As described in Section 18.1.1, subroutines TBLCNC and CONEC have the principal responsibility
of processing those equipment models involving state variables and differential equations. The
majority of such models are those used in the modeling of generating plant equipment (generators,
power system stabilizers, compensators, excitation limiters, excitation systems, and turbine gover-
nors), some types of load characteristic models, auxiliary signal models, FACTS device models, dc
line models, and switched shunt models, and are called through subroutine TBLCNC.
The form of each model reference in these subroutines is that of a FORTRAN CALL statement
referencing the model name and an argument list. The arguments generally specify the location of
the model in the network and the starting locations in the general purpose storage arrays CON,
STATE, VAR and/or ICON of the block of storage locations reserved for that model reference.
Although implemented differently, plant-related models, load characteristic models, auxiliary signal
models, FACTS device models, dc line models, and switched shunt models called through subrou-
tine TBLCNC receive the same information via their argument lists whenever they are called;
Section 20.5 for details.
Dynamic Simulation Setup and Procedures PSS
E 32.0
The Dynamic Model Program Operation Manual
18-12 Siemens Energy, Inc., Power Technologies International
The construction of the model connection tables for subroutine TBLCNC and of subroutine CONEC,
then, involves the following steps:
1. A model must be selected from the PSS
E.
2. Retrieve the converted power flow Saved Case representing the network to be modeled.
3. Read dynamics data file, and preserve the dynamics working memory in a snapshot file.
Preserve dynamics working memory in a Snapshot File and terminate PSS
E.
4. Incorporate the connection subroutines into the PSS
E interface.
Those models which are not automatically processed by activity DYRE (see Section 14.1.5) are
either set up by activity CHAN (see Sections 14.2.2 and 18.6), they may be treated as User-Written
Models by activity DYRE, or their calls may be manually entered into the connection subroutines by
the user (see Section 18.9).
Dynamic Simulation Setup and Procedures PSS
E 32.0
The Dynamic Model Program Operation Manual
18-14 Siemens Energy, Inc., Power Technologies International
18.4.4 Program Set-Up
Prior to compiling the connection subroutines, the user may add any desired control logic to them;
this is discussed in more detail in Section 18.9. There is however a situation in which the connection
subroutines as generated by activity DYRE require statement insertion by the user. It occurs when
dc lines are being modeled (using one of the following models that are still not in the table-driven
form: CDCRL, CASEA1, CDCVUP, CEELRI, CMDWS2, CMFORD, CHIGAT, CMDWAS) and one
or more of the dc line supplementary signal models are being used. The insertion involves placing
the auxiliary signal into the Other signals VAR, VAR(L), of the dc line model. The procedure is illus-
trated by example.
Suppose dc line 1 is sensitive to a supplementary signal which is formed by summing the outputs
of a pair of PAUX1T models. Suppose the supplementary signal model PAUX1T model stores the
model output in VAR(9) and VAR(20). Note that because PAUX1T is a table-driven model, activity
DYRE does not generate PAUX1T model calls in CONEC. Suppose the dc line is modeled using
the dc line model CMFORD. Because CMFORD model is still not in the table-driven form, activity
DYRE will generate CMFORD model call in subroutine CONEC. A portion of subroutine CONEC as
constructed by activity DYRE appears as follows:
CALL CMFORD ( 1, 206, 73, 31, 3)
C
RETURN
Referring to the CMFORD data sheets (see PSS
E dynamics working memory, prior to executing simulation runs the user must ensure himself
that the system model thus constructed faithfully models the physical power system. A model setup
with unchecked and unreliable data usually produces inaccurate results in system simulations.
There are thousands of data parameters from a wide variety of sources used in a large scale system
simulation study. The checking of each of these for accuracy is no easy task. PSS
E provides for
three levels of model verification:
1. Data parameters are checked for reasonableness. This detects many simple errors such as
transcription errors.
2. The performance of generating units are tested in hypothetical isolated operating conditions
where the effects of excitation and governor action are not masked by the electrical synchro-
nization effect, but are clearly and unambiguously visible.
3. The initialization of the simulation at the predisturbance network operating condition is
checked for model variables initialized outside of prescribed limits and for steady-state
operation.
The following paragraphs discuss these levels of data verification in greater detail.
18.5.1 Parameter Range Checking
Activity DOCU provides documentation of the dynamic simulation setup. For each model, it tabu-
lates the equivalent of a filled in model data sheet. This consists of a listing of the constant data read
from the Dynamics Data Input File along with a statement of the locations assigned in the general
purpose storage arrays by activity DYRE.
However, critical examination of this report for a large system is difficult because of its volume. It is
unlikely that an engineer studying this report would find all errors and it is therefore not a practical
way of locating errors.
Through its interactive dialog, activity DOCU may be operated in a mode which provides an initial
editing of the report and restricts it to those models for which the values of one or more constant
parameters are suspect. Parameters are checked against typical ranges of values. In addition,
certain relational checks between parameters are made (e.g., machine leakage reactance must be
less than subtransient reactance). The suspect parameters are tabulated followed by the standard
model output block.
It must be noted that being flagged by activity DOCU in its data checking mode does not indicate
that parameter values are necessarily wrong; it simply indicates that they deserve to be checked.
Conversely, the absence of warning messages from activity DOCU in this mode does not indicate
that all data is valid. Most power system parameters can fall within reasonable typical value ranges
and still be totally invalid.
Thus, the data checking mode of activity DOCU is intended to detect gross errors such as
misplaced decimal points and as such provides only a rough initial screening for typing and steno-
graphic errors.
As a final point, the preprogrammed typical parameter ranges are set on the assumption that plant
equipment data is specified on actual machine base MVA. The practice of specifying all machine
Dynamic Simulation Setup and Procedures PSS
E 32.0
Model Verification Program Operation Manual
18-16 Siemens Energy, Inc., Power Technologies International
data on a common base (say, 100 MVA) is discouraged because this often results in the spurious
flagging of generator and governor models in the data checking mode of activity DOCU, thus
partially defeating its report editing intent. It is strongly recommended, then, that the machine quan-
tity MBASE in the power flow, on which machine model data is specified, be set to the actual
machine base MVA for each machine, and that model parameters be specified accordingly.
18.5.2 Performance Verification
The proper criterion for judging the correctness of generator, excitation system, and turbine
governor data is not that all parameter values lie within typical ranges, but rather that the parameter
values modeling each item of equipment correspond to correct performance of the unit under test
conditions. Therefore, after data has been checked for gross errors using the reasonable data
check option of activity DOCU, the user should verify that the sets of parameter values in the system
model lead to:
1. Correct steady-state values of all quantities that are normally measured or documented in
normal operation of a generating unit.
2. Correct reproduction of dynamic response tests that may be performed on generating units
and their control systems in isolation.
The following paragraphs describe the tools available to the PSS
E auxiliary program VCV31 produces such a plot for a specified set of machine reac-
tances and saturation data. It also tabulates the steady-state excitation voltage corresponding to a
given loading. The use of program VCV is described in Additional Resources for PSS
E, VCV.
Exciter Response Ratio Test
The data describing the rotating exciter may be checked by simulating an exciter response ratio
test. In this test, the exciter is set up to run at the output voltage and current corresponding to rated
main generator operating point. The voltage regulator setpoint is then raised suddenly by a large
amount to drive the exciter to its ceiling as rapidly as possible.
Siemens Energy, Inc., Power Technologies International 18-17
PSS
E.
2. Restore the Snapshot containing the dynamics data of the system being modeled
(activity RSTR).
3. Retrieve the corresponding converted power flow Saved Case. Note that the generators
must be converted. However, there is no need to factorize the matrices (i.e., activity FACT
is not required) because the transmission network is ignored in this test, with all machines
operating in isolation.
4. From the menu, select the option to perform exciter response ratio simulation. After initial-
izing, run the response ratio simulation to zero seconds (specifying TPAUSE equal to 0).
Then continue the simulation to TPAUSE set at 2 seconds.
The response ratio test is executed simultaneously on either all units in the system or all machines
at a designated bus. Any user-specified output channels (see Section 18.6) are overridden and the
exciter outputs, EFD, of all online machines being tested are placed in output channels.
Activity ESTR overrides the initial generator loadings as contained in the working case and initial-
izes each unit to rated MVA at a user-specified power factor. Following completion of activity ESTR,
it is advisable to check the value of EFD for each machine to ensure that it is as determined by
program VCV31 or from generator test data for rated load. An unacceptable value of full load exci-
tation usually indicates an erroneous specification of the generator saturation data; all generator
data, in particular SE(1.2), should be checked before proceeding.
Activity ERUN reveals both the ceiling value of EFD and the excitation system response ratio for
each unit. The user should examine these values and adjust the excitation loop data if they do not
correspond to the known ceiling and response ratio.
Because the machine initialization to rated MVA is based on the value specified as MBASE for each
machine, the response ratio test is valid only for those machines where data is specified on their
actual MVA base. For operational and additional application details, refer to activities ESTR and
ERUN.
Excitation System Open Circuit Step Response Test
The response ratio test described above provides information on the modeling of exciters but gives
no indication of the correctness of the voltage regulator gains and time constants. These are
checked by ensuring that the excitation system gives stable and effective control of generator
terminal voltage when the machine is operating at rated speed on open circuit (e.g., just before
synchronizing).
This aspect of excitation system performance is readily tested by applying a simple step change of
about five percent to the voltage regulator reference and observing the resulting responses of field
voltage (EFD) and generator terminal voltage (ETERM). The values of excitation system parame-
ters should be such that a well damped but not overly sluggish response is obtained.
The procedure for carrying out this test is as follows:
1. Initiate PSS
E.
2. Restore the Snapshot containing the dynamics data of the system being modeled
(activity RSTR).
Dynamic Simulation Setup and Procedures PSS
E 32.0
Model Verification Program Operation Manual
18-18 Siemens Energy, Inc., Power Technologies International
3. Retrieve the corresponding converted power flow Saved Case. Note that the generators
must be converted. However, there is no need to factorize the matrices (i.e., activity FACT
is not required) because the transmission network is ignored in this test, with all machines
operating in isolation.
4. From the menu, select the option to perform exciter simulation test. After initializing, run the
open circuit simulation to zero seconds (specifying TPAUSE equal to 0). Then continue the
simulation to TPAUSE set at 2 seconds.
The open circuit response test is executed simultaneously on either all units in the system or all
machines at a designated bus. Any user-specified output channels (see Section 18.6) are over-
ridden and the exciter outputs, EFD, and machine terminal voltages, ETERM, of all online machines
being tested are placed in output channels.
Activity ESTR overrides the initial generator loadings as contained in the working case and initial-
izes each unit to the rated terminal voltage on open circuit. Following completion of activity ESTR,
the initial value of EFD for each unit should be slightly greater than the air gap line value of unity
due to saturation in the main generator. An initial open circuit value of EFD exceeding about 1.2 pu
is a fair indication that the generator saturation data is erroneous.
The response to a setpoint step of about 0.05 pu should normally show a slight overshoot but be
well damped with no persistent oscillations. For operational and additional application details, refer
to activities ESTR and ERUN.
Governor Response Test
The principal purpose of the governor response test is to ensure that the governor gain and time
constant parameters correspond to a correctly tuned well damped response. In this test, each
machine is initialized to a given load and the response of the governors to a step change in the load
is measured. The load electrical power is held constant after the step so that the response indicates
the damping due to the turbine and governor loop only.
The procedure for carrying out this test is as follows:
1. Initiate PSS
E.
2. Restore the Snapshot containing the dynamics data of the system being modeled
(activity RSTR).
3. Retrieve the corresponding converted power flow Saved Case. Note that the generators
must be converted. However, there is no need to factorize the matrices (i.e., activity FACT
is not required) because the transmission network is ignored in this test, with all machines
operating in isolation.
4. From the menu, select the option to perform governor response simulation. After initializing,
run the simulation to zero seconds (specifying TPAUSE equal to 0). Then continue the simu-
lation to TPAUSE set at 2 seconds.
The governor test is executed simultaneously on either all units in the system or all machines at a
designated bus. Any user-specified output channels (see Section 18.6) are overridden and the
speed deviations, SPEED, and turbine mechanical powers, PMECH, of all online machines being
tested are placed in output channels.
Siemens Energy, Inc., Power Technologies International 18-19
PSS
E 32.0
Model Verification Program Operation Manual
18-20 Siemens Energy, Inc., Power Technologies International
and to ensure that machine loadings are within turbine governor limits. Activity GEOL is useful for
this check. Other operating point checks that can be made include: a cross check of the operating
point of dc transmission lines with the dynamics data parameters specified for the dc line model,
particularly the voltage dependent current limit; acceptably small mismatches from the power flow
solution; and the selection of load characteristics in establishing the converted case.
These checks can only verify operating point variables outward from the generator terminals. The
checking of the initial condition with respect to variables within the equipment dynamic models is
assisted by the dynamic simulation initialization activity STRT.
Beginning with the generator terminal conditions as contained in the working case, activity STRT
works backward through all dynamic simulation models to determine the initial condition values of
all state, algebraic, and input variables along with those of several of PSS
E 32.0
Simulation Outputs Program Operation Manual
18-22 Siemens Energy, Inc., Power Technologies International
18.6 Simulation Outputs
PSS
E contains no standard set of simulation variables that are recorded to document the results
of a simulation run. Rather, any power system variable that can be represented by an element of
the following dynamics data arrays may be selected as an output of a dynamic simulation run (refer
to Table 18-1):
This is accomplished by assigning the desired value to an output channel. PSS
E
activities CHAN and CHSB. As each output channel variable is assigned, an entry is made in the
following output channel control arrays:
These arrays are preserved with the dynamics data Snapshot as it is saved and retrieved with
activities SNAP and RSTR, respectively.
The arrays IPRINT and IDENT are used during activity STRT and RUN in the process of filling the
Channel Output File. Each variable address is formed by summing the appropriate array base
address and an offset. The array base addresses are installation dependent; they are a function of
the capacity limits for which PSS
E.
IDENT Contains the thirty-two character alphanumeric channel identifiers assigned to each
output channel.
CHNTYP Contains coded descriptions of the type of quantity assigned to each output
channel.
CHNBUS Contains descriptions of the physical location of each output channel quantity.
Siemens Energy, Inc., Power Technologies International 18-23
PSS
E monitoring models which place their results into VARs during the simulation.
These model call references are located in the model connection table arrays, and the corre-
sponding models are called automatically at each time step of the dynamic simulation. Refer to
Sections 14.2.2 and 14.25.2.
Activities CHAN and CHSB are used to establish the set of output channels for which values are to
be recorded during the simulation. They may also be used to append additional output channel
selections to those previously specified, and to modify the simulation variable assignment of indi-
vidual output channels.
Although activity ALTR may be used to add or change output channel assignments, this is not
recommended because this process involves the determination of the channel addresses in
dynamics memory by the user. This, in turn, requires the knowledge of the internal numbering of
buses, machines and loads in the working case to determine the offset to be used in forming the
channel address. Because activities CHAN and CHSB automatically handle the look-up of these
numbers, their use, rather than through the line model activity ALTR, reduces the risk of error in
specifying output channels.
Two separate index pointers used in the processing of output channels are maintained. The variable
NXTCHN points to the next available channel number and is used in setting up the default channel
number responses in subsequent executions of activities SNAP, CHAN and CHSB. The variable
NCHAN, which is normally equal to NXTCHN-1, is sensed by activities STRT and RUN and defines
the number of output channels to be monitored during dynamic simulation runs. NCHAN may be
set to any nonnegative number less than NXTCHN by the user. Both of these pointer variables may
be changed either using the GUI or by running the line model activity ALTR. For operational and
additional application details, refer to activities CHAN and CHSB, respectively.
18.6.2 Channel Output File
Other than as described in Section 18.6.3, the PSS
E 32.0
Simulation Outputs Program Operation Manual
18-24 Siemens Energy, Inc., Power Technologies International
3. The Snapshot and power flow Saved Case used as the initial condition operating point for
the simulation were preserved immediately following a previous execution of activity STRT,
and activity STRT is not to be used again to initialize this simulation. Working memory is set
up in the standard manner (activities RSTR, LOFL, CASE, FACT, and RTRN), a Channel
Output File is specified either using the GUI or with activity ALTR, and activity RUN is
entered.
Unless some specific purpose is to be served, the user should not normally change the Channel
Output File used in a simulation in the middle of a run.
The Channel Output File is a binary file of variable length records. The results of a simulation run,
as recorded in the Channel Output File, may be plotted and/or tabulated upon completion of the
simulation calculation. The processing of this file is handled by PSS
E allows a subset of up to six of the main simulation output channels to be plotted on the
users graphical CRT workstation as the simulation is taking place. To enable this feature:
1. The selected output channels must be assigned to CRT Plot Channels (see below).
2. The control variable CRTPLT, which is specified at the beginning of activity RUN, must be
specified with a value greater than zero.
3. A Channel Output File must be active (see Section 18.6.2).
4. The graphics output device option setting (see Section 3.3.3 and OPTN) must specify a
graphics CRT.
The specification of CRT plot channels, which are numbered one through six, is made either using
the GUI or with activity ALTR after the main simulation output channels have been designated. The
user has to specify the number of the main output channel to be assigned to the selected CRT
channel, along with the scales to be used on the rough plot. Specifying a main channel number of
zero for any of the six CRT plot channels deactivates that CRT channel.
The user is free to modify the CRT channel assignments and/or scales at any time during a simu-
lation run.
Siemens Energy, Inc., Power Technologies International 18-25
PSS
E.
3. Open the power flow case and the dynamics snapshot files.
The above sequence of activities assumes that the Saved Case and the Snapshot files are present,
and that the Snapshot File contains the desired output channel assignments for the simulation run.
Whenever network data is present in the working case and dynamics data is present in PSS
E
working memory, when moving between the power flow and dynamics data spreadsheets, PSS
E
takes care to update the dynamics model connection table array pointers and output channel
addresses to reflect changes in the internal bus, machine, load, and branch numbering of the
working case. These steps correctly set up these arrays in preparation for the dynamic simulation
initialization activity, STRT which initializes all simulation models comprising the system model.
The user may preserve the initial conditions of the dynamic models by taking a Snapshot. The
attainment of a clean STRT is a key point in a simulation study and such a Snapshot often provides
a useful reference in analyzing simulation results. Although such a Snapshot may be used as the
initial condition for future simulations with the same initial condition without repeating activity STRT,
the inclusion of activity STRT in each simulation run is strongly recommended because it provides
for:
1. A cross check for compatibility of the Snapshot and power flow Saved Case; and
2. The specification of a new Channel Output File; one common mistake in using such a Snap-
shot and omitting activity STRT in subsequent simulations occurs when neglecting to
change the Channel Output File, thus unintentionally overwriting the results of a previous
simulation.
The execution of activity STRT contributes only a small fraction of the total job time in a system
simulation; including activity STRT in each simulation to provide the checks described above is well
worth the investment. For operational and additional application details, refer to activity STRT and
Section 18.5.3.
18.7.2 Applying Disturbances
The process of making dynamic simulation runs involves executing activity RUN. Activity RUN
starts from the present value of simulation TIME, and calculates the state of the system, advancing
Dynamic Simulation Setup and Procedures PSS
E 32.0
Running a Simulation Program Operation Manual
18-26 Siemens Energy, Inc., Power Technologies International
TIME until it reaches the value specified as TPAUSE. TPAUSE is designated upon entering
activity RUN.
Activity STRT initializes the value of simulation TIME to minus two time steps. This provides for a
period of steady-state simulation prior to initiating any disturbance. This serves as a further check
on the formulation of the system model and the initial condition operating point, and produces a
corresponding flat segment at the beginning of plots generated by the Output Channel File
processing program, PSSPLT, executed following the completion of the simulation.
Thus, following an error-free execution of activity STRT, activity RUN should be selected with its
first TPAUSE set for TIME equals zero seconds. Some PSS
E load characteristic models modify the load data arrays in the working
case during the execution of activity STRT. This, in turn, requires that any such Saved Case be
established following the execution of activity STRT when any of these types of simulation models
are being used. Therefore, the new Saved Case feature of activity ALTR should be used with
caution during a simulation run.
Activity CHNG is automatically entered and network switching operations may be applied in the
standard manner. Prior to running simulation, PSS
E will
automatically run activity FACT if needed.
While the power flow linkage is in effect, power flow reporting activities such as POUT and GENS
may be executed to examine network conditions at that instant of the simulation. Note that, while
the power flow activities do recognize the basic load characteristics as implemented by
activity CONL, they do not have a knowledge of other boundary condition modeling as implemented
by load characteristic models. Thus, network modeling in a simulation such as loads modeled
beyond the level provided by the basic load characteristics or frequency sensitivity of loads and
network parameters shows as mismatches in power flow output reports. Any dc lines are correctly
reported.
During simulations, particularly while a fault is applied or the system voltages are generally
depressed, the network solution may fail to converge within the prescribed number of iterations. It
is also possible for convergence failure to result from the system reaching an unrealistic state of
stress which relay action in the physical system, which is unmodeled in the simulation, would not
allow.
Any convergence failure is reported with an appropriate message, including the final convergence
monitor line in the same form as is used in activities SOLV, MSLV, and TYSL. The simulation then
continues as if convergence had been achieved.
Convergence failure can often be corrected by decreasing the acceleration factor used and
increasing the number of iterations permitted during the network solution with activity ALTR. It is
advisable to observe the convergence monitor when the iteration is failing to converge and following
a change in acceleration.
18.7.3 Snapshots
Dynamic simulation working memory may be preserved in the form of a Snapshot which is placed
into a Snapshot File by activity SNAP. Among other data items, a Snapshot contains both the
constant parameters associated with the dynamic equipment models and those arrays which
specify the instantaneous condition of the equipment models. It does not, however, contain any
information pertaining to the electric network. As in power flow and fault analysis applications,
network data (i.e., the working case) is preserved in a Saved Case File.
Thus, a system dynamic model is completely specified by the combination of a Snapshot and its
corresponding power flow Saved Case. It is strongly recommended, particularly for the novice user
of PSS
E will automatically execute activity FACT and generate the factored admittance
matrix, if needed, before a dynamic simulation is performed.
Dynamic Simulation Setup and Procedures PSS
E 32.0
Running a Simulation Program Operation Manual
18-28 Siemens Energy, Inc., Power Technologies International
18.7.4 Application Notes
It is permissible in PSS
E to stop a simulation run and examine in detail the results to date, and
then restart the run from that point just as if it had not been interrupted. This is accomplished by first
recording the instantaneous state of the system in Snapshot and Saved Case form. PSS
E may
then be terminated and the Channel Output File of the simulation examined with the plot package
provided with PSS
E. The user should however be careful not to overwrite the original Snapshot
and Saved Case Files on which future simulations may be based.
To continue such an interrupted simulation, PSS
E. Many of the operations are described in detail elsewhere in this manual and are
reviewed here for reference.
18.8.1 The Executable Run File
If the dynamic case has user models, the user dll (usually the dsusr.dll) has to be created. The user
dll will contain references to the user models and to any connection routines that may have been
generated as a result of running activity DYRE.
To create the user dll, the create usrdll program can be used. The create usrdll is GUI driven method
that allows users to compile the model source code and create the dll. An alternative way to create
the user dll is to use the CLOAD4 command which is run via the DOS prompt.
Any time a system model change is implemented by a change to either of the connection subroutine
files, the new versions must be compiled and the user dll file must be rebuilt by again running the
create usrdll tool or by running the CLOAD4 command. See Additional Resources for PSS
E,
Createusrdll.
18.8.2 The Converted Saved Case
The dynamic simulation activities require that the network in the working case be converted from its
power flow representation to the form required for dynamic simulations. The converted case may
initially be set up by:
1. Picking up the appropriate power flow case which must be solved to an acceptable
mismatch level. The solved unconverted case should be preserved in a Saved Case File.
2. Ensuring that the machine characteristic data MBASE, ZSORCE, XTRAN and GENTAP are
correctly specified for all in-service machines. These machine attributes are a part of the
power flow data that is kept with the Saved Case.
3. Converting the generator representation by executing activity CONG.
4. Converting the load representation by executing activity CONL. Selective load conversion
is accommodated by specifying the appropriate bus subsystem, area, zone, owner, or
basekV when invoking activity CONL.
5. Calculating the triangular factors of the system admittance matrix and storing them in the
admittance matrix temporary file by executing activity FACT.
6. Refining the voltage solution by executing activity TYSL.
7. Preserving the converted power flow case in a Saved Case File by executing activity SAVE.
This should not be the same Saved Case File in which the unconverted (i.e., power flow
style) Saved Case is located.
This procedure need be done only once for each initial condition operating point.
Note that the results of the conversion process of steps 3 and 4, and the refined network solution
of step 6 are reflected in the Saved Case of step 7. The triangular factors determined in step 5,
however, are located in the admittance matrix temporary file and are not in the Saved Case File.
Dynamic Simulation Setup and Procedures PSS
E 32.0
Procedural Summary Program Operation Manual
18-30 Siemens Energy, Inc., Power Technologies International
18.8.3 Initial Model Setup
In constructing a new system model from source data, the following steps are used:
1. Set up the converted Saved Case as described in Section 18.8.2.
2. Using the model data sheets for reference, prepare a Dynamics Data Input File in the form
given in Section 14.1.1.
3. Initiate PSS
E
4. Retrieve the converted Saved Case with activity CASE.
5. Execute activity DYRE as described in Section 14.1.2. Specify the filenames into which the
CONEC and CONET subroutines are to be placed, making sure not to overwrite existing
files which the user wishes to retain. Specify starting addresses of one for each of the
general purpose storage arrays. Specify a filename to be used as a compiling file.
6. Use the consistency check for plant models via GUI (available from Dynamics > Model main-
tenance> Consistency Check) to check for modeling inconsistencies as described in
Section 14.7.6. Resolve any error messages printed by activity DYRE and the consistency
check. If necessary, edit the Dynamics Data Input File as required and repeat steps 3
through 6.
7. Preserve dynamics working memory in a Snapshot File by executing activity SNAP.
8. Exit PSS
E.
2. Open the converted network.
3. Open the Snapshot file.
4. Run the simulation. It may be noted that if setting up the factored matrix (i.e., running activity
FACT) is not done by user, PSS
E 32.0
Procedural Summary Program Operation Manual
18-32 Siemens Energy, Inc., Power Technologies International
4. Retrieve the dynamic snapshot file.
5. If desired, add output channels. Then execute dynamic simulations as described in
Section 18.8.6.
This approach assumes that there are no dynamic modeling changes required to model the new
initial condition operating point. Changes to the dynamic model are described in the following
section.
18.8.8 Modifying the Dynamic Modeling
The majority of dynamic modeling changes fall into one of the following two categories:
1. A change to the constant parameters of a model for which the reference already exists.
2. The addition of a new model reference to an existing dynamics setup.
The first type of modeling change is straightforward and requires no modification of the model
connection table arrays or the connection subroutines. Working memory is setup as described in
Section 18.8.4, and the appropriate data changes are entered on the Dynamics spreadsheet, or
with activities CCON, ALTR, or PSAS. Dynamics working memory, with the modified data items, is
then preserved with activity SNAP, either overwriting the original Snapshot or in a new Snapshot
File as appropriate.
The second type of modeling change requires the modification of the intelligence connecting
specific models to network elements: the model connection tables in the case of plant-related, load-
related, line relay models, auxiliary-signal models, FACTS device models, dc line models, switched
shunt models or the connection subroutines for models related to other network elements (see
Section 18.1.1). Furthermore, it may involve either adding a model for an equipment item which was
previously not modeled (e.g., adding a governor to a machine) or replacing one model with another
(e.g., changing an IEEET1 model to an SCRX).
The majority of plant-related, load-related, line relay, auxiliary-signal, FACTS, dc line, and switched
shunt models may be introduced into the dynamic simulation setup using the appropriate spread-
sheet in the Dynamics or Models tab.
All other models must be introduced via activity DYRE (plant-related, load-related, line relay, auxil-
iary-signal, FACTS, and dc line models may also be introduced in this manner). One way to do this
is to edit the original Dynamics Data Input File (or its current version as output by activity DYDA),
and reconstruct the entire dynamics setup. Alternatively, activity DYRE may be used in an add
models mode (see Section 14.1.3); the following approach may be used:
1. Prepare a Dynamics Data Input File in the form shown in Section 14.1.1. Only data records
for the new models should be included.
2. Initiate PSS
E, and retrieve the data for the current system model into working memory as
described in Section 18.8.4 (step 4 may be omitted).
3. Run activity DYRE,ADD, specifying the file created in (1), and files into which the connection
subroutine calls are to be placed. They should not be the same files containing the CONEC
and CONET subroutines for the current version of the system model. Specify the default
next available locations in the dynamics data general purpose storage arrays.
4. Preserve dynamics working memory as updated in (3) by executing activity SNAP.
Siemens Energy, Inc., Power Technologies International 18-33
PSS
E.
6. Merge the CONEC and CONET model calls as generated in the above execution of
activity DYRE with the versions of these subroutines containing the rest of the system model
calls. If models are being replaced, the user must either delete or comment out the model
calls which were replaced so that the resulting connection subroutine contains the new call
and not the old reference.
7. Compile and link to create the user dll.
18.8.9 A Comment
The experienced user of the dynamic simulation activities of PSS
E activities involved.
2. The proper sequencing of these activities required for a given application.
3. The contents of working memory in the context of the recent sequencing of PSS
E
activities.
4. The relationship among the various files involved in the data handling and simulation phases
referenced above.
Dynamic Simulation Setup and Procedures PSS
E 32.0
Advanced Uses of CONEC and CONET Program Operation Manual
18-34 Siemens Energy, Inc., Power Technologies International
18.9 Advanced Uses of CONEC and CONET
As described in Section 18.4, the connection subroutines CONEC and CONET are a vital compo-
nent of the system model. They are, however, simply FORTRAN subroutines and the experienced
PSS
E user may add any desired code to them to handle a wide variety of simulation control and
modeling requirements.
This section describes some typical examples of user-written code in these subroutines. It is not
intended to be an all-encompassing treatment on the subject, but rather to suggest approaches that
might be used to meet specific requirements.
18.9.1 Manual Model Addition
The process of manually adding models to the connection subroutines involves filling out a model
sheet for each model to be added, incorporating the model CALL statement into the connection
subroutine(s), and entering the models constant data parameters into the PSS
E dynamics data
general purpose storage arrays. The procedure is illustrated by example.
Suppose that in a simulation setup, the user wishes to place the branch flow exclusive of line
connected shunt elements for circuit 1 from bus 100 to bus 110 into output channels. The model
FLOW2 may be used to calculate these quantities and place them into VARs. The VARs may then
be assigned to output channels. The following procedure may be used:
1. Enter the constant parameters for the FLOW2 model on its data sheet in the Value column
of the ICON block (see Figure 18-2).
2. Start up PSS
E, restore the Snapshot containing the original simulation data and, using the
dialog for solution parameter changes (available from the GUI menu Dynamics>Simula-
tion>Solution Parameters), note the next available locations in the ICON and VAR arrays
(FLOW2 does not use any CONs or STATEs). Assume that these are listed as 101 and 601
respectively.
3. Assign storage locations in the ICON and VAR arrays for the FLOW2 model. For the ICON
array, we assign locations starting at 101 (the next available location), and ending at 103
(i.e., I+2 from the data sheet). Similarly, in the VAR array, we assign locations 601 and 602
which will hold the MW and Mvar flow; the MVA flow is not needed so L will be set to zero.
The model call can now be written from the completely filled in model data sheet as:
CALL FLOW2 ( 101, 601, 602 0 )
At this point, the next available ICON and VAR indices are 104 and 603, respectively.
4. Modify the CONET subroutine by adding the FLOW2 model call listed in (3). Compile the
revised CONET subroutine and link it to create the user dll.
5. Initiate PSS
E and retrieve the original system model data as detailed in Section 18.8.4.
6. From the GUI menu Dynamics>Simulation>Solution Parameters, or using the solution
parameter changes of activity ALTR, update the next available location pointers for the
ICON and VAR arrays to correspond to the values determined at the end of step 3.
7. Referring to Figure 18-2, set the constant parameters for the new model by setting the ICON
values in the dynamics data spreadsheet for ICON, or with activity ALTR, or by executing an
appropriate Response File generated by the PSS
E 32.0
Advanced Uses of CONEC and CONET Program Operation Manual
18-36 Siemens Energy, Inc., Power Technologies International
FLOW2
Branch Flow Model
Note: Flows do not include the line shunt components.
Model call must be manually inserted into subroutine
CONET after the IFLAG test and data must be entered.
Figure 18-2. Branch Flow Model
CALL FLOW2 (I,N,M,L) from CONET
This model ICONs starting with #_______ I.
It stores the real component of flow
in VAR
#_______ N,
the imaginary component in VAR #_______ M,
and the VA flow in VAR #_______ L
Flow is calculated out of the bus number contained in ICON(I).
N, M, and/or L may be zero to bypass storing of the respective
quantity
VARs # Description
N 601 MW
M 602 Mvar
L 0 MVA
ICONs # Value Description
I 101 100 from bus number
I+1 102 110 to bus number
I+2 103 1 Circuit identifier*
* Enter circuit identifier of -1 to sum flows of all parallel
circuits between the two buses.
Siemens Energy, Inc., Power Technologies International 18-37
PSS
E includes the subroutine GENCHK which may be called by the user in subroutine CONEC
to determine the machine index of a given machine. Its calling sequence is:
CALL GENCHK (IBUS, 'I', K, 'string')
where:
Suppose, for example, the user wished to calculate the accelerating power (ignoring stator losses)
in MW of machine one at bus 100 and place it in a VAR for monitoring during a series of simulation
runs. This could be accomplished as follows:
1. Start up PSS
E, restore the Snapshot containing the simulation data and, using the GUI
menu Dynamics>Simulation>Solution parameters, note the next available location in the
VAR array. In this example, assume it is 714. The coding to be added to subroutine CONEC
will place the calculated quantity in this VAR. Change the next available VAR pointer to 715,
and then, with activity CHAN, assign VAR 714 to an output channel. Preserve these
changes by taking a Snapshot and terminate PSS
E.
2. Edit the source code of subroutine CONEC to include the following FORTRAN statements
just before the RETURN statement:
IF (MODE.NE.2) RETURN
CALL GENCHK ( 100, '1', II, 'IN CONEC' )
IF (II.EQ.0) RETURN
VAR(714) = PMECH(II)*MBASE(II) - PELEC(II)*SBASE
These calculations need be done only in MODE two, hence the logical IF statement. Note
that the PMECH array elements are in pu on machine base, and that the PELEC array
elements are in pu on system base. Thus, the calculated quantity is expressed in MW.
3. Compile the modified CONEC subroutine and create the user dll.
Table 18-1 also identifies several arrays as being indexed by load index. The load index for a given
load is an internal sequence number assigned by PSS
E to the load.
PSS
E includes the subroutine LODCHK, which may be called by the user in subroutine CONET
to determine the load index of a given load. Its calling sequence is:
CALL LODCHK (IBUS, I, K)
IBUS Is the number of the bus.
I Is the machine identifier of the machine for which the index is to be found.
K Is returned as the machine index, or zero if the machine is not found.
string Is text which is included in any error message printed whenever GENCHK cannot
find the specified machine.
Dynamic Simulation Setup and Procedures PSS
E 32.0
Advanced Uses of CONEC and CONET Program Operation Manual
18-38 Siemens Energy, Inc., Power Technologies International
where:
18.9.3 Getting Bus Sequence Numbers
PSS
E includes the subroutine BSSEQN which may be called by the user in subroutine CONEC
or CONET to determine the bus sequence number of a given bus. Its calling sequence is:
CALL BSSEQN (IBUS, I, *alt )
where:
Suppose, for example, the user wished to convert the pu bus frequency deviation at a given bus to
bus frequency in Hertz. This involves a determination of the bus sequence number (see Bus
Sequence Numbers) corresponding to a given bus. The FLECS code fragment shown in Figure 18-
3, inserted before the RETURN statement in subroutine CONEC, determines the bus sequence
number of the bus for which the external number is contained in ICON 101, and stores the corre-
sponding bus frequency in VAR 401.
Figure 18-3. Bus Frequency Example
This fragment of code takes advantage of the following points concerning the PSS
E data structure
and the logic sequence of activity RUN to execute efficiently:
1. It only needs to be executed when the value of the control variable MODE is one (initializa-
tion) or two (time derivative calculation following the network solution).
2. The array INTICN is indexed in the same manner as the array ICON and is available to the
PSS
E model writer (or, in this case, the CONEC twiddler) as a memory location. Its content
is preserved from one entry of subroutine CONEC to the next and in Snapshots.
IBUS Is the number of the bus.
I Is the load identifier of the load for which the index is to be found.
K Is the returned load index, or zero if the load is not found.
IBUS Is the number of the bus for which the bus sequence number is to be found.
I Is returned as the bus sequence number; it is unchanged if the bus is not found.
alt Is the FORTRAN statement label to which BSSEQN returns if the bus is not found.
IF (MODE.GT.2) RETURN
C
WHEN (MODE.EQ.1 .OR. KPAUSE.EQ.2)
. IBUS=ICON(101)
. IS=0
. CALL BSSEQN( IBUS, IS, *10 )
10 . INTICN(101)=IS
...FIN
ELSE IS=INTICN(101)
C
WHEN (IS.EQ.0) VAR(401)=0.
ELSE
VAR(401)=60.*(1.+BSFREQ(IS))
Siemens Energy, Inc., Power Technologies International 18-39
PSS
E
activity commands and responses:
snap,temp.snp
save,temp.sav
stop
Note: The blank line following the selection of activity SNAP activates the default response
for the number of elements to save field in activity SNAP. This sequence of commands
assumes that, if either of the files temp.snp or temp.sav already exists, PSS
E is being
operated in its file overwrite mode (see Section 3.3.3).
Then, in subroutine CONET, insert the following statement after any relay and monitoring model
calls and immediately before statement label 9000:
IF (ITER.GT.ITMXDS) CALL UPAUSE('stop.idv')
The effect of this statement is to force a pause upon detection of convergence failure. Subsequent
dialog input is then taken from the Response File stop.idv, which causes a Snapshot and power flow
Saved Case to be written to the files temp.snp and temp.sav, respectively, and PSS
E to be
terminated.
The UPAUSE run termination routine (supplied with PSS
E model library.
Synchronous machine models operate in one of three modes during extended term simulations:
1. A small time step mode, in which all state variables are handled in the same manner.
2. An intermediate time step or midterm dynamics mode in which the higher frequency modes
of the synchronous machine models GENROU, GENROE, GENSAL, GENSAE and
GENCLS have some extra damping.
3. A large time step or uniform island frequency mode in which, for each electrical island in the
system, an average frequency is determined and all machines in the island take on the
island frequency as their SPEEDs.
Two solution parameters are used to determine which of these three modes is being used: an inter-
mediate mode time step threshold (DLTBKW) and an island frequency time step threshold
(DLTEXT). The simulation time step (DELT) is compared to these threshold values and the simula-
tion mode is set to:
Small time step mode if DELT < DLTBKW.
Intermediate time step mode if DLTBKW < DELT < DLTEXT.
Large time step mode if DELT > DLTEXT.
Dynamic Simulation Setup and Procedures PSS
E 32.0
Extended Term Simulations Program Operation Manual
18-42 Siemens Energy, Inc., Power Technologies International
Default values of the time step thresholds are established when PSS
E is started up,
these parameters are set to 1.0 and 0.0005 respectively. In this mode, the network solution iteration
continues until both the largest voltage change is below its convergence tolerance and the largest
machine angle change is below the island frequency mode convergence tolerance.
The time step thresholds, acceleration factor and convergence tolerance may be changed using
Dynamics>Simulation>Solution Parameters in the GUI, or with activity ALTR and are preserved
with the Snapshot when it is saved with activity SNAP. Care must be taken in changing the time
step thresholds during an extended term simulation (see Section 14.23.1).
The state-space simulation activities utilize the following arrays in their second order explicit inte-
gration calculations:
The extended term simulation activities use the Z-form expression of the trapezoidal integration
algorithm, an implicit integration algorithm (see the PSS
Es address space, the STORMT array occupies the same locations as the STATE and
DSTATE arrays. In state-space simulations, models do not reference their STORMT array
elements, and in extended term simulations, they do not reference their STATE and DSTATE array
elements.
Clearly, in extended term simulations, STATE values placed in output channels or tabulated with
activity DLST are not useful.
STATE Contains the values of the state variables.
DSTATE Contains their time derivatives.
STORE Contains the integrator memory.
State-Space Extended Term
STATE(K) STORE(K)
STORE(K) STORMT(2*K-1)
DSTATE(K) STORMT(2*K)
Siemens Energy, Inc., Power Technologies International 18-43
PSS
E. Multiple channel output files can be open simultaneously and the channels from
these multiple channel files combined on a single plot. Currently, the plotting functionality is only a
subset of the plotting capabilities found in PSSPLT. In future releases, the full functionality of
PSS
E. Therefore, PSS
E.
18.11.1 General Workflow to View Dynamic Results
The results of Dynamic Simulations are the plot channels of various PSS
E can be used to read these binary channel files and display the
plots.
In order to view the plots, a Plot Book has to be created. The Plot Book is configured like an Excel
Worksheet with multiple Plot Pages each capable of displaying several Plots. A Plot in turn can con-
tain several channels/curves/traces. A Plot Book by default will contain on Page with one Plot on
that Page.
After a Plot Book is created, a channel output file has to be opened. The channel output file will
appear in the Tree View, which, when expanded, will display all the channel outputs that were
selected prior to the Dynamic Simulation run.
Any channel output quantity can be viewed by dragging and dropping into the Plot Page.
18.11.2 Recording
Many of the interactions involved in creating and customizing the Plot Book are recordable and can
be played back through the use of Automation files. In future releases, most of the Plot Book inter-
actions will be recordable and available for playback.
Additional Information
PSS
E 32.0
Creating and Viewing the Results of Dynamic Simulations Program Operation Manual
18-44 Siemens Energy, Inc., Power Technologies International
This page intentionally left blank.
Siemens Energy, Inc., Power Technologies International 19-1
Chapter 19
Example Data Files
19.1 SAVNW Case Data Input Files
SAVNW case comprises a simple power system network. It shows how to build a case in PSS
E
and the kind of data input required to study power flow, fault analysis and dynamic behavior of
power system network. A PSS
E 32.0
SAVNW Case Data Input Files Program Operation Manual
19-2 Siemens Energy, Inc., Power Technologies International
PSS
E
3
2
.
0
E
x
a
m
p
l
e
D
a
t
a
F
i
l
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
S
A
V
N
W
C
a
s
e
D
a
t
a
I
n
p
u
t
F
i
l
e
s Figure 19-1. SAVNW Power Flow Raw Data File savnw.raw (1 of 2 Sheets)
0, 100.00 / PSSE-30.0 FRI, JUL 16 2004 11:17
PSSE PROGRAM APPLICATION GUIDE EXAMPLE
BASE CASE INCLUDING SEQUENCE DATA
101,'NUC-A ', 21.6000,2, 0.000, 0.000, 1, 77,1.02000, 16.5466, 11
102,'NUC-B ', 21.6000,2, 0.000, 0.000, 1, 77,1.02000, 16.5466, 11
151,'NUCPANT ', 500.0000,1, 0.000, -600.000, 1, 1,1.01190, 10.8887, 1
152,'MID500 ', 500.0000,1, 0.000, 0.000, 1, 1,1.01707, -1.1152, 1
153,'MID230 ', 230.0000,1, 0.000, 0.000, 1, 1,0.99300, -3.2357, 1
154,'DOWNTN ', 230.0000,1, 0.000, 300.000, 1, 1,0.93892, -9.8857, 1
201,'HYDRO ', 500.0000,1, 0.000, 300.000, 2, 2,1.04000, 6.1599, 22
202,'EAST500 ', 500.0000,1, 0.000, 0.000, 2, 2,1.00879, -1.3172, 2
203,'EAST230 ', 230.0000,1, 0.000, 50.000, 2, 2,0.96651, -6.9180, 2
204,'SUB500 ', 500.0000,1, 0.000, 0.000, 2, 2,0.97873, -3.7331, 2
205,'SUB230 ', 230.0000,1, 0.000, 300.000, 2, 2,0.94902, -9.1798, 2
206,'URBGEN ', 18.0000,2, 0.000, 0.000, 2, 2,1.02361, -2.9699, 22
211,'HYDRO_G ', 20.0000,2, 0.000, 0.000, 2, 2,1.04045, 12.9201, 22
3001,'MINE ', 230.0000,1, 0.000, 0.000, 5, 5,1.02979, -1.3728, 55
3002,'E. MINE ', 500.0000,1, 0.000, 0.000, 5, 5,1.02791, -1.8253, 5
3003,'S. MINE ', 230.0000,1, 0.000, 0.000, 5, 5,1.02332, -2.2538, 5
3004,'WEST ', 500.0000,1, 0.000, 0.000, 5, 5,1.01647, -3.4289, 5
3005,'WEST ', 230.0000,1, 0.000, 0.000, 5, 5,0.99478, -5.1800, 5
3006,'UPTOWN ', 230.0000,1, 0.000, 0.000, 5, 5,0.99404, -3.7922, 5
3007,'RURAL ', 230.0000,1, 0.000, 0.000, 5, 5,0.96370, -8.5380, 5
3008,'CATDOG ', 230.0000,1, 0.000, 0.000, 5, 5,0.95861, -9.0489, 55
3011,'MINE_G ', 13.8000,3, 0.000, 0.000, 5, 5,1.04000, 0.0000, 55
3018,'CATDOG_G ', 13.8000,2, 0.000, 0.000, 5, 5,1.02177, -4.0804, 55
0 / END OF BUS DATA, BEGIN LOAD DATA
153,'1 ',1, 1, 1, 200.000, 100.000, 0.000, 0.000, 0.000, 0.000, 1
154,'1 ',1, 2, 1, 600.000, 450.000, 0.000, 0.000, 0.000, 0.000, 1
154,'2 ',1, 2, 1, 400.000, 350.000, 0.000, 0.000, 0.000, 0.000, 100
203,'1 ',1, 2, 2, 300.000, 150.000, 0.000, 0.000, 0.000, 0.000, 2
205,'1 ',1, 2, 2, 1200.000, 700.000, 0.000, 0.000, 0.000, 0.000, 2
3005,'1 ',1, 5, 5, 100.000, 50.000, 0.000, 0.000, 0.000, 0.000, 5
3007,'1 ',1, 5, 5, 200.000, 75.000, 0.000, 0.000, 0.000, 0.000, 5
3008,'1 ',1, 5, 5, 200.000, 75.000, 0.000, 0.000, 0.000, 0.000, 5
0 / END OF LOAD DATA, BEGIN GENERATOR DATA
101,'1 ', 750.000, 81.194, 600.000, -100.000,1.02000, 0, 900.000, 0.01000, 0.30000, 0.00000, 0.00000,1.00000,1, 100.0, 810.000, 0.000, 11,0.6667, 1,0.3333
102,'1 ', 750.000, 81.194, 600.000, -100.000,1.02000, 0, 900.000, 0.01000, 0.30000, 0.00000, 0.00000,1.00000,1, 100.0, 810.000, 0.000, 11,0.6667, 1,0.3333
206,'1 ', 800.000, 600.000, 600.000, 0.000,0.98000, 205, 1000.000, 0.01000, 0.25000, 0.00000, 0.00000,1.00000,1, 100.0, 900.000, 0.000, 2,0.4000, 22,0.6000
211,'1 ', 600.000, 17.750, 400.000, -100.000,1.04000, 201, 725.000, 0.01000, 0.26000, 0.00000, 0.00000,1.00000,1, 100.0, 616.250, 0.000, 2,0.4000, 22,0.6000
3011,'1 ', 258.656, 104.043, 600.000, -100.000,1.04000, 0, 1000.000, 0.01000, 0.35000, 0.00000, 0.00000,1.00000,1, 100.0, 900.000, 0.000, 55,0.3846, 5,0.3077, 22,0.2308,
11,0.0769
3018,'1 ', 100.000, 80.000, 80.000, 0.000,1.02000, 3008, 130.000, 0.01000, 0.35000, 0.00000, 0.00000,1.00000,1, 100.0, 117.000, 0.000, 55,0.5556, 5,0.4444
0 / END OF GENERATOR DATA, BEGIN BRANCH DATA
151, 152,'1 ', 0.00260, 0.04600, 3.50000, 1200.00, 1300.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
151, 152,'2 ', 0.00260, 0.04600, 3.50000, 1200.00, 1300.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
151, 201,'1 ', 0.00100, 0.01500, 1.20000, 1200.00, 1300.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
152, -202,'1 ', 0.00080, 0.01000, 0.95000, 1200.00, 1300.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
152, 3004,'1 ', 0.00300, 0.03000, 2.50000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
153, 154,'1 ', 0.00500, 0.04500, 0.10000, 300.00, 350.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,0.7500, 100,0.2500
153, 154,'2 ', 0.00600, 0.05400, 0.15000, 300.00, 350.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
153, 3006,'1 ', 0.00100, 0.01200, 0.03000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
154, 203,'1 ', 0.00400, 0.04000, 0.10000, 200.00, 250.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
154, 205,'1 ', 0.00033, 0.00333, 0.09000, 600.00, 660.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
154, 3008,'1 ', 0.00270, 0.02200, 0.30000, 400.00, 440.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,1.0000
201, 202,'1 ', 0.00200, 0.02500, 2.00000, 1200.00, 1300.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 22,1.0000
201, 204,'1 ', 0.00300, 0.03000, 2.50000, 1200.00, 1300.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 22,1.0000
203, -205,'1 ', 0.00500, 0.04500, 0.08000, 200.00, 250.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 2,1.0000
203, -205,'2 ', 0.00500, 0.04500, 0.08000, 200.00, 250.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 2,1.0000
3001, 3003,'1 ', 0.00000, 0.00800, 0.00000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 55,1.0000
3002, 3004,'1 ', 0.00600, 0.05400, 0.09000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 5,1.0000
3003, 3005,'1 ', 0.00600, 0.05400, 0.09000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 5,1.0000
3003, 3005,'2 ', 0.00600, 0.05400, 0.09000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 5,1.0000
3005, 3006,'1 ', 0.00350, 0.03000, 0.07000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 5,1.0000
3005, 3007,'1 ', 0.00300, 0.02500, 0.06000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 5,1.0000
3005, 3008,'1 ', 0.00600, 0.05000, 0.12000, 0.00, 0.00, 1.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 5,1.0000
1
9
-
4
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
E
x
a
m
p
l
e
D
a
t
a
F
i
l
e
s
P
S
S
E
3
2
.
0
S
A
V
N
W
C
a
s
e
D
a
t
a
I
n
p
u
t
F
i
l
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 19-1 (Cont). SAVNW Power Flow Raw Data File savnw.raw (2 of 2 Sheets)
0 / END OF BRANCH DATA, BEGIN TRANSFORMER DATA
151, 101, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 1,1.0000 0.00030, 0.01360, 100.00 1.00000, 0.000, 0.000, 1250.00, 1350.00, 1750.00, 0, 0, 1.10000, 0.90000, 1.10000,
0.90000, 5, 0, 0.00000, 0.00000 1.00000, 0.000
151, 102, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 1,1.0000 0.00030, 0.01360, 100.00 1.00000, 0.000, 0.000, 1250.00, 1350.00, 1750.00, 0, 0, 1.10000, 0.90000, 1.10000,
0.90000, 5, 0, 0.00000, 0.00000 1.00000, 0.000
152, 153, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 1,1.0000 0.00000, 0.00500, 100.00 1.01000, 0.000, 0.000, 2500.00, 3000.00, 3500.00, 1, 154, 1.05000, 0.95000, 1.00000,
0.98000, 33, 0, 0.00000, 0.00000 1.00000, 0.000
201, 211, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 22,1.0000 0.00070, 0.02125, 100.00 1.00000, 0.000, 0.000, 800.00, 1000.00, 1120.00, 0, 201, 1.10000, 0.90000, 1.05000,
0.95000, 5, 0, 0.00000, 0.00000 1.00000, 0.000
202, 203, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 2,1.0000 0.00040, 0.01625, 100.00 1.00000, 0.000, 0.000, 800.00, 1040.00, 1200.00, 3, 0,30.00000,-
30.0000,555.0000,545.0000, 33, 0, 0.00000, 0.00000 1.00000, 0.000
204, 205, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 2,1.0000 0.00030, 0.01500, 100.00 1.00000, 0.000, 0.000, 800.00, 1040.00, 1200.00, 1, 205, 1.05000, 0.95000, 1.00000,
0.98000, 33, 0, 0.00000, 0.00000 1.00000, 0.000
205, 206, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 2,1.0000 0.00026, 0.01333, 100.00 1.00000, 0.000, 0.000, 900.00, 1080.00, 1350.00, 0, 0, 1.10000, 0.90000, 1.10000,
0.90000, 5, 0, 0.00000, 0.00000 1.00000, 0.000
3001, 3002, 0,'1 ',1,1,1, 0.00000, 0.00000,1,' ',1, 55,1.0000 0.00030, 0.01500, 100.00 1.00000, 0.000, 0.000, 800.00, 1040.00, 1200.00, 0, 0, 1.10000, 0.90000, 1.05000,
0.95000, 33, 0, 0.00000, 0.00000 1.00000, 0.000
3001, 3011, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 55,1.0000 0.00020, 0.01000, 100.00 1.00000, 0.000, 0.000, 1300.00, 1560.00, 1820.00, 0, 0, 1.10000, 0.90000, 1.05000,
0.95000, 5, 0, 0.00000, 0.00000 1.00000, 0.000
3004, 3005, 0,'1 ',1,1,1, 0.00000, 0.00000,1,' ',1, 5,1.0000 0.00040, 0.01625, 100.00 1.00000, 0.000, 0.000, 800.00, 1040.00, 1200.00, 0, 0, 1.10000, 0.90000, 1.05000,
0.95000, 33, 0, 0.00000, 0.00000 1.00000, 0.000
3008, 3018, 0,'1 ',1,1,1, 0.00000, 0.00000,2,' ',1, 55,1.0000 0.00021, 0.08500, 100.00 1.00000, 0.000, 0.000, 150.00, 200.00, 250.00, 0, 0, 1.10000, 0.90000, 1.05000,
0.95000, 5, 0, 0.00000, 0.00000 1.00000, 0.000
0 / END OF TRANSFORMER DATA, BEGIN AREA DATA
1, 101, 250.000, 10.000,'FLAPCO '
2, 206, -100.000, 10.000,'LIGHTCO '
5, 3011, -150.000, 10.000,'WORLD '
0 / END OF AREA DATA, BEGIN TWO-TERMINAL DC DATA
0 / END OF TWO-TERMINAL DC DATA, BEGIN VSC DC LINE DATA
0 / END OF VSC DC LINE DATA, BEGIN SWITCHED SHUNT DATA
0 / END OF SWITCHED SHUNT DATA, BEGIN IMPEDANCE CORRECTION DATA
0 / END OF IMPEDANCE CORRECTION DATA, BEGIN MULTI-TERMINAL DC DATA
0 / END OF MULTI-TERMINAL DC DATA, BEGIN MULTI-SECTION LINE DATA
201, 205,'&1', 204
3005, -3008,'&1', 3007
0 / END OF MULTI-SECTION LINE DATA, BEGIN ZONE DATA
1,'FIRST '
2,'SECOND '
5,'FIFTH '
77,'PLANT '
0 / END OF ZONE DATA, BEGIN INTER-AREA TRANSFER DATA
1, 2,'A', 70.00
1, 2,'B', 30.00
1, 5,'A', 100.00
1, 5,'B', 50.00
0 / END OF INTER-AREA TRANSFER DATA, BEGIN OWNER DATA
1,'TRAN 1 '
2,'TRAN 2 '
5,'TRAN 5 '
11,'GEN 1 '
22,'GEN 2 '
55,'GEN 5 '
100,'NO BUSES '
0 / END OF OWNER DATA, BEGIN FACTS DEVICE DATA
0 / END OF FACTS DEVICE DATA
Siemens Energy, Inc., Power Technologies International 19-5
PSS
E
3
2
.
0
S
A
V
N
W
C
a
s
e
D
a
t
a
I
n
p
u
t
F
i
l
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Figure 19-3. SAVNW Slider Diagram File savnw.sld
Siemens Energy, Inc., Power Technologies International 19-7
PSS
E 32.0
SAMPLE Case Data Input Files Program Operation Manual
19-8 Siemens Energy, Inc., Power Technologies International
19.2 SAMPLE Case Data Input Files
Sample case shows the capabilities of PSS
E.
Figure 19-6. SAMPLE Power Flow Raw Data File sample.raw (1 of 4 Sheets)
0, 100.00 / PSS/E-30.0 FRI, JUN 04 2004 17:30
PSS/E-30 SAMPLE CASE
ALL DATA CATEGORIES WITH SEQUENCE DATA
101,'NUC-A ', 21.6000,2, 0.000, 0.000, 1, 1,1.01000, -10.8648, 1
102,'NUC-B ', 21.6000,2, 0.000, 0.000, 1, 1,1.01000, -11.2168, 1
151,'NUCPLNT ', 500.0000,1, 11.120, -600.000, 1, 1,1.00217, -14.0048, 1
152,'MID500 ', 500.0000,1, 1.630, 50.000, 1, 2,1.04364, -23.8464, 1
153,'MID230 ', 230.0000,1, 0.000, 0.000, 1, 3,1.05683, -25.5912, 1
154,'DOWNTN ', 230.0000,1, 2.450, 200.000, 1, 3,0.99173, -33.0040, 1
155,'FACTS TE ', 230.0000,1, 0.000, 0.000, 1, 4,1.01710, -24.1507, 1
201,'HYDRO ', 500.0000,1, 3.670, -500.000, 2, 7,0.98998, -19.1700, 2
202,'EAST500 ', 500.0000,1, 0.000, 0.000, 2, 2,1.02100, -26.1103, 2
203,'EAST230 ', 230.0000,1, 0.000, 50.000, 2, 8,1.00000, -29.5852, 2
204,'SUB500 ', 500.0000,1, 0.000, 0.000, 2, 8,1.03022, -31.3855, 2
205,'SUB230 ', 230.0000,1, 2.780, 300.000, 2, 8,1.00000, -33.6890, 2
206,'URBGEN ', 18.0000,2, 0.000, 0.000, 2, 8,1.00000, -31.2341, 2
207,'DUPONT ', 500.0000,1, 0.000, 0.000, 2, 7,1.01388, -25.4541, 2
211,'HYDRO_G ', 20.0000,2, 0.000, 0.000, 2, 7,1.00000, -14.5144, 2
212,'INVERT1 ', 230.0000,1, 5.130, 400.000, 2, 7,1.02695, -32.0655, 2
213,'INVERT2 ', 230.0000,1, 5.140, 400.000, 2, 7,1.10677, -35.3311, 2
214,'LOADER ', 230.0000,1, 0.000, 0.000, 2, 7,1.07726, -36.7610, 2
215,'URBANEAST1 ', 18.0000,1, 0.000, 0.000, 2, 8,0.98539, -33.6275, 2
216,'URBANEAST1 ', 230.0000,1, 0.000, 0.000, 2, 8,0.99637, -33.6660, 2
217,'URBANEAST1 ', 230.0000,1, 0.000, 0.000, 2, 8,0.99733, -33.6721, 2
218,'URBANEAST1 ', 230.0000,1, 0.000, 0.000, 2, 8,0.99769, -33.6743, 2
301,'NORTH ', 765.0000,3, 0.000, 0.000, 3, 5,1.00000, 0.0000, 3
401,'COGEN-1 ', 500.0000,3, 0.000, 0.000, 4, 9,1.00000, 0.0000, 4
402,'COGEN-2 ', 500.0000,3, 0.000, 0.000, 6, 9,1.00000, 0.0000, 4
3001,'MINE ', 230.0000,1, 0.000, 0.000, 5, 6,1.02324, -4.0850, 5
3002,'E. MINE ', 500.0000,1, 0.000, 0.000, 5, 6,0.99915, -2.4001, 5
3003,'S. MINE ', 230.0000,1, 0.000, 0.000, 5, 6,1.01851, -7.5681, 5
3004,'WEST ', 500.0000,1, 0.000, 0.000, 5, 6,1.01416, -18.5345, 5
3005,'WEST ', 230.0000,1, 0.000, 0.000, 5, 2,1.00500, -19.5401, 5
3006,'UPTOWN ', 230.0000,1, 0.000, 0.000, 5, 4,1.05683, -25.5912, 5
3007,'RURAL ', 230.0000,1, 0.000, 0.000, 5, 4,0.98409, -23.8203, 5
3008,'CATDOG ', 230.0000,1, 0.000, 0.000, 5, 4,0.99000, -25.3430, 5
3009,'URBANWEST1 ', 230.0000,1, 0.000, 0.000, 5, 4,0.99048, -25.3626, 5
3010,'URBANWEST2 ', 21.6000,1, 0.000, 0.000, 5, 4,0.96664, 1.6733, 5
3011,'MINE_G ', 19.4000,3, 0.000, 0.000, 5, 6,1.00000, 0.0000, 5
3018,'CATDOG_G ', 13.8000,2, 0.000, 0.000, 5, 4,0.99000, -21.5731, 5
3021,'WDUM ', 18.0000,1, 0.000, 1320.000, 3, 5,1.00000, -20.3546, 3
3022,'EDUM ', 18.0000,1, 0.000, 1080.000, 3, 5,1.00000, -19.6655, 3
0 / END OF BUS DATA, BEGIN LOAD DATA
152,'1 ',1, 1, 1, 1200.000, 360.000, 868.340, 360.502, 837.794, -351.338, 1
153,'1 ',1, 1, 1, 200.000, 100.000, 0.000, 0.000, 0.000, 0.000, 1
154,'1 ',1, 1, 1, 400.000, 200.000, 0.000, 0.000, 0.000, 0.000, 1
154,'2 ',1, 1, 1, 250.000, 200.000, 0.000, 0.000, 0.000, 0.000, 1
154,'3 ',1, 1, 1, 250.000, 100.000, 0.000, 0.000, 0.000, 0.000, 1
154,'MO',1, 1, 1, 100.000, 80.000, 0.000, 0.000, 0.000, 0.000, 1
203,'1 ',1, 2, 2, 500.000, 250.000, 0.000, 0.000, 0.000, 0.000, 2
205,'1 ',1, 2, 2, 1800.000, 600.000, 0.000, 0.000, 0.000, 0.000, 2
205,'B ',1, 2, 2, 90.000, 5.000, 110.000, 25.000, 20.000, 10.000, 2
205,'C ',1, 2, 2, 60.000, 15.000, 45.000, 5.000, 35.000, 30.000, 2
214,'1 ',1, 2, 2, 500.000, 75.000, 0.000, 0.000, 0.000, 0.000, 2
215,'U1',1, 2, 4, 0.000, 140.000, 0.000, 0.000, 0.000, 0.000, 2
216,'U1',1, 2, 4, 0.000, 12.000, 0.000, 0.000, 0.000, 0.000, 2
217,'U1',1, 2, 4, 0.000, 10.000, 0.000, 0.000, 0.000, 0.000, 2
218,'U1',1, 2, 4, 0.000, 9.000, 0.000, 0.000, 0.000, 0.000, 2
3005,'1 ',1, 5, 5, 100.000, 50.000, 0.000, 0.000, 0.000, 0.000, 5
3007,'1 ',1, 5, 5, 200.000, 75.000, 0.000, 0.000, 0.000, 0.000, 5
3008,'1 ',1, 5, 5, 200.000, 75.000, 0.000, 0.000, 0.000, 0.000, 5
3009,'1 ',1, 5, 4, 1.100, 0.900, 0.000, 0.000, 0.000, 0.000, 5
3010,'1 ',1, 5, 4, 12.000, 5.000, 0.000, 0.000, 0.000, 0.000, 5
0 / END OF LOAD DATA, BEGIN GENERATOR DATA
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
1
9
-
9
P
S
S
E
3
2
.
0
E
x
a
m
p
l
e
D
a
t
a
F
i
l
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
S
A
M
P
L
E
C
a
s
e
D
a
t
a
I
n
p
u
t
F
i
l
e
s
Figure 19-6 (Cont). SAMPLE Power Flow Raw Data File sample.raw (2 of 4 Sheets)
101,'1 ', 750.000, 104.978, 400.000, -100.000,1.01000, 0, 900.000, 0.01000, 0.30000, 0.00000, 0.00000,1.00000,1, 100.0, 800.000, 50.000, 1,0.1289, 2,0.2524, 3,0.1031, 4,0.5156
102,'1 ', 650.000, 112.745, 410.000, -110.000,1.01000, 0, 950.000, 0.01050, 0.32000, 0.00000, 0.00000,1.00000,1, 100.0, 700.000, 33.000, 1,0.3647, 2,0.1838, 3,0.0751, 4,0.3764
206,'1 ', 800.000, 283.913, 500.000, -400.000,1.00000, 0, 1000.000, 0.01060, 0.25100, 0.00000, 0.00000,1.00000,1, 100.0, 850.000, 50.000, 1,0.1034, 2,0.4006, 3,0.0825, 4,0.4135
211,'1 ', 600.000, 87.292, 510.000, -100.000,1.00000, 0, 725.000, 0.01080, 0.26200, 0.00000, 0.00000,1.00000,1, 100.0, 616.000, 30.000, 1,0.1423, 2,0.2210, 3,0.1842, 4,0.4525
301,'1 ', 996.883, 299.543, 700.000, -650.000,1.00000, 0, 1067.000, 0.01090, 0.23000, 0.01400, 0.12600,1.02500,1, 98.0, 1010.000, 320.000, 1,0.1118, 2,0.2184, 3,0.0893, 4,0.5805
301,'2 ', 996.883, 299.543, 710.000, -600.000,1.00000, 0, 1070.000, 0.01100, 0.24000, 0.01100, 0.12700,1.02600,1, 98.0, 1011.000, 321.000, 1,0.1173, 2,0.3200, 3,0.0936, 4,0.4691
301,'3 ', 996.883, 299.543, 720.000, -600.000,1.00000, 0, 1075.000, 0.00800, 0.25000, 0.01200, 0.12800,1.02700,1, 98.0, 1012.000, 322.000, 1,0.1260, 2,0.2268, 3,0.1827, 4,0.4644
401,'1 ', 321.000, 142.325, 600.000, -100.000,1.00000, 0, 600.000, 0.01230, 0.22230, 0.00000, 0.00000,1.00000,1, 90.0, 350.000, 25.000, 1,0.1625, 2,0.2423, 3,0.0990, 4,0.4962
402,'1 ', 321.000, 142.325, 610.000, -110.000,1.00000, 0, 610.000, 0.00450, 0.24320, 0.00000, 0.00000,1.00000,1, 91.0, 351.000, 26.000, 1,0.1588, 2,0.2117, 3,0.1959, 4,0.4335
3011,'1 ', 1316.962, 148.216, 620.000, -120.000,1.00000, 0, 1050.000, 0.00760, 0.35430, 0.00000, 0.00000,1.00000,1, 92.0, 1400.000, 100.000, 1,0.1452, 2,0.1926, 3,0.2677, 4,0.3945
3018,'1 ', 400.000, -0.628, 300.000, -150.000,0.99000, 0, 530.000, 0.08700, 0.35630, 0.00000, 0.00000,1.00000,1, 92.5, 500.000, 50.000, 1,0.1043, 2,0.2037, 3,0.2749, 4,0.4171
3018,'2 ', 100.000, -0.157, 75.000, -75.000,0.99000, 0, 120.000, 0.02400, 0.35530, 0.00000, 0.00000,1.00000,1, 92.5, 110.000, 20.000, 1,0.3003, 2,0.1358, 3,0.2857, 4,0.2782
0 / END OF GENERATOR DATA, BEGIN BRANCH DATA
151, -152,'1 ', 0.00260, 0.04600, 3.50000, 1200.00, 1100.00, 1000.00, 0.01000, -0.25000, 0.01100, -0.15000,1, 150.00, 1,0.2000, 2,0.3000, 3,0.4000, 4,0.1000
151, -152,'2 ', 0.00261, 0.04610, 3.51000, 1205.00, 1105.00, 1005.00, 0.01300, -0.25100, 0.01200, -0.02000,1, 149.00, 5,0.2315, 1,0.3056, 2,0.3704, 3,0.0926
151, -201,'1 ', 0.00100, 0.01500, 1.20000, 1206.00, 1106.00, 1006.00, 0.00000, 0.00000, 0.00000, -1.00000,1, 100.00, 2,0.3600, 3,0.2400, 4,0.3200, 5,0.0800
152, 202,'1 ', 0.00080, 0.01000, 0.95000, 1207.00, 1107.00, 1007.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 200.00, 1,0.3939, 2,0.2273, 3,0.3030, 4,0.0758
152, -3004,'1 ', 0.00300, 0.03000, 2.50000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 201.00, 5,0.2379, 1,0.3033, 2,0.3667, 3,0.0922
153, -154,'2 ', 0.00600, 0.05400, 0.15000, 350.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 80.00, 2,0.2727, 3,0.2727, 4,0.3636, 5,0.0909
153, -3006,'1 ', 0.00000, 0.00010, 0.00000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.00, 1,0.3443, 2,0.2459, 3,0.3279, 4,0.0820
154, 155,'1 ', 0.00500, 0.04500, 0.10000, 400.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 81.00, 5,0.1914, 1,0.2535, 2,0.3065, 3,0.2486
154, -203,'1 ', 0.00400, 0.04000, 0.10000, 400.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 100.00, 2,0.2000, 3,0.3000, 4,0.4000, 5,0.1000
154, -205,'1 ', 0.00033, 0.00333, 0.09000, 600.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 120.00, 1,0.1667, 2,0.2500, 3,0.3333, 4,0.2500
154, -3008,'1 ', 0.00270, 0.02200, 0.30000, 800.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 119.00, 5,0.1925, 1,0.2550, 2,0.3083, 3,0.2442
201, -202,'1 ', 0.00200, 0.02500, 2.00000, 1200.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 300.00, 2,0.1905, 3,0.2857, 4,0.3810, 5,0.1429
201, -207,'C1', 0.00150, 0.01500, 1.25000, 1200.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 250.00, 1,0.2500, 2,0.3750, 3,0.2500, 4,0.1250
203, 205,'1 ', 0.00500, 0.04500, 0.08000, 200.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 70.00, 5,0.1925, 1,0.2550, 2,0.3083, 3,0.2442
204, -207,'C2', 0.00150, 0.01500, 1.25000, 1200.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 300.00, 2,0.2000, 3,0.3000, 4,0.4000, 5,0.1000
205, 212,'1 ', 0.00000, 0.01000, 0.00000, 1250.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 71.00, 1,0.2000, 2,0.3000, 3,0.4000, 4,0.1000
205, -214,'2 ', 0.00200, 0.02500, 2.00000, 1200.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 100.00, 5,0.2100, 1,0.2782, 2,0.3364, 3,0.1755
205, -216,'3 ', 0.00500, 0.04500, 0.08000, 200.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 81.00, 2,0.1818, 3,0.2727, 4,0.3636, 5,0.1818
205, -217,'4 ', 0.00500, 0.04500, 0.08000, 200.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 80.00, 1,0.1667, 2,0.2500, 3,0.3333, 4,0.2500
205, -218,'5 ', 0.00500, 0.04500, 0.08000, 200.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 59.00, 5,0.1650, 1,0.2186, 2,0.2643, 3,0.3521
213, -214,'1 ', 0.00000, 0.01000, 0.00000, 1250.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 0.50, 2,0.1429, 3,0.2143, 4,0.2857, 5,0.3571
3001, -3003,'1 ', 0.00000, 0.00800, 0.00000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 70.00, 1,0.1639, 2,0.2459, 3,0.3279, 4,0.2623
3002, -3004,'1 ', 0.00600, 0.05400, 0.09000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 200.00, 5,0.1925, 1,0.2550, 2,0.3083, 3,0.2442
3003, -3005,'1 ', 0.00600, 0.05400, 0.09000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 90.00, 2,0.2000, 3,0.3000, 4,0.4000, 5,0.1000
3003, -3005,'2 ', 0.00600, 0.05400, 0.09000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 90.00, 1,0.1333, 2,0.2000, 3,0.2667, 4,0.4000
3005, -3006,'1 ', 0.00350, 0.03000, 0.07000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 70.00, 5,0.1650, 1,0.2186, 2,0.2643, 3,0.3521
3005, -3007,'1 ', 0.00300, 0.02500, 0.06000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 80.00, 2,0.1527, 3,0.2290, 4,0.3053, 5,0.3130
3005, -3008,'1 ', 0.00600, 0.05000, 0.12000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,0, 60.00, 1,0.1802, 2,0.2703, 3,0.3604, 4,0.1892
3007, -3008,'1 ', 0.00300, 0.02500, 0.06000, 0.00, 0.00, 0.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 60.00, 5,0.1858, 1,0.2462, 2,0.4023, 3,0.1657
3008, -3009,'1 ', 0.00300, 0.02500, 0.06000, 25.00, 22.00, 18.00, 0.00000, 0.00000, 0.00000, 0.00000,1, 60.00, 1,0.1797, 2,0.2695, 3,0.3594, 4,0.1914
0 / END OF BRANCH DATA, BEGIN TRANSFORMER DATA
101, 151, 0,'T1',2,2,1, 0.17147, 0.10288,2,'NUCA GSU ',1, 1,0.3200, 2,0.3900, 3,0.1400, 4,0.1500
0.00110, 0.09100, 1200.00
21.6000, 21.600, 0.000, 1200.00, 1100.00, 1000.00, 1, 101,22.68000,20.52000, 1.05000, 0.95000, 25, 0, 0.00021, 0.00051
500.000, 500.000
102, 151, 0,'T2',2,1,2, 453750, 0.00260,2,'NUCB GSU ',1, 1,0.2100, 2,0.2500, 3,0.2200, 4,0.3200
0.00012, 0.00760, 1210.00
21.6000, 21.600, 0.000, 1210.00, 1125.00, 1025.00, 1, 102,22.57200,20.62800, 1.04500, 0.95500, 27, 0, 0.00022, 0.00052
500.000, 500.000
152, 153, 0,'T3',2,1,1, 0.00021, 0.00012,2,'MID LTC ',1, 1,0.3500, 2,0.2200, 3,0.2500, 4,0.1800
0.00017, 0.00775, 800.00
475.000, 500.000, 0.000, 800.00, 750.00, 700.00, 1, 154,525.0000,475.0000, 1.00000, 0.98000, 10, 0, 0.00023, 0.00053
230.000, 230.000
152, 3021, 0,'T4',1,2,2, 562500, 0.00280,2,'WDUM DC ',1, 1,0.3900, 2,0.3200, 3,0.1500, 4,0.1400
0.00130, 0.06300, 1500.00
1.10000, 500.000, 0.000, 1500.00, 1400.00, 1350.00, 4, 0,22.57200,20.62800, 1.10000, 0.90000, 33, 2, 0.00000, 0.00000
1.00000, 18.000
152, 3022, 0,'T5',1,2,1, 0.00040, 0.00021,2,'EDUM DC ',1, 1,0.2200, 2,0.2500, 3,0.2100, 4,0.3200
0.00170, 0.07400, 1510.00
1.10000, 500.000, 0.000, 1510.00, 1410.00, 1393.00, 4, 0, 1.10000, 0.90000, 1.10000, 0.90000, 33, 0, 0.00000, 0.00000
1.00000, 18.000
201, 211, 0,'T6',2,1,2, 262500, 0.00300,2,'HYDRO_G XMER',1, 1,0.1400, 2,0.1500, 3,0.3200, 4,0.3900
0.00026, 0.01343, 700.00
1
9
-
1
0
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
E
x
a
m
p
l
e
D
a
t
a
F
i
l
e
s
P
S
S
E
3
2
.
0
S
A
M
P
L
E
C
a
s
e
D
a
t
a
I
n
p
u
t
F
i
l
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l Figure 19-6 (Cont). SAMPLE Power Flow Raw Data File sample.raw (3 of 4 Sheets)
201, 211, 0,'T6',2,1,2, 262500, 0.00300,2,'HYDRO_G XMER',1, 1,0.1400, 2,0.1500, 3,0.3200, 4,0.3900
0.00026, 0.01343, 700.00
500.000, 500.000, 0.000, 700.00, 650.00, 611.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 5, 0, 0.00000, 0.00000
20.0000, 20.000
203, 202, 0,'T7',1,2,1, 0.00095, 0.00046,1,'EAST PS ',1, 1,0.2754, 2,0.3261, 3,0.2899, 4,0.1087
0.00210, 0.05400, 750.00
0.99000, 230.000, 0.143, 750.00, 700.00, 657.00, 3, 0,12.00000,-11.0000,-900.000,-950.000, 33, 1, 0.00000, 0.00000
1.00000, 500.000
204, 205, 0,'T8',1,2,1, 0.00113, 0.00052,2,'SUB LTC ',1, 1,0.3019, 2,0.4245, 3,0.1321, 4,0.1415
0.00370, 0.04500, 800.00
1.03667, 500.000, 0.000, 800.00, 775.00, 717.00, 1, 205, 1.05000, 0.95000, 1.00000, 0.98000, 16, 0, 0.00024, 0.00054
1.00000, 230.000
205, 206, 0,'T9',1,2,1, 0.00113, 0.00052,2,'URB TX ',1, 1,0.1905, 2,0.4643, 3,0.1667, 4,0.1786
0.00160, 0.04800, 900.00
1.01591, 230.000, 0.000, 900.00, 850.00, 799.00, 2, 0, 1.05000, 0.97500,-175.000,-250.000, 12, 0, 0.00000, 0.00000
1.00000, 18.000
205, 215, 216,'3 ',1,2,2, 34200, 0.00228,2,'3WNDSTAT3 ',3, 2,0.2540, 2,0.1746, 3,0.3333, 4,0.2381
0.00103, 0.10000, 150.00, 0.00138, 0.12000, 20.00, 0.00068, 0.07500, 15.00,1.02605, -33.7608
1.00000, 230.000, 0.000, 150.00, 130.00, 120.00,-1, 215, 1.10000, 0.90000, 1.10000, 0.90000, 33, 0, 0.00025, 0.00064
1.10000, 18.000, 0.000, 20.00, 18.00, 15.00,-2, 0, 1.20000, 0.90120,150.0000,80.00000, 33, 0, 0.00012, 0.00046
1.00000, 230.000, 0.000, 15.00, 13.00, 10.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 33, 0, 0.00000, 0.00000
205, 217, 218,'4 ',2,3,2, 6840, 0.00163,2,'3WNDSTAT4 ',4, 2,0.4671, 2,0.1250, 3,0.2379, 4,0.1700
228000, 0.10001, 30.00, 190000, 0.09000, 25.00, 266000, 0.07500, 35.00,0.99757, -33.6734
230.000, 230.000, 0.000, 30.00, 20.00, 10.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 33, 0, 0.00031, 0.00784
230.000, 230.000, 0.000, 25.00, 18.00, 12.00,-1, 217,253.0000,207.0000,20.90000,18.88000, 33, 0, 0.00021, 0.00862
230.000, 230.000, 0.000, 35.00, 26.00, 14.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 33, 0, 0.00024, 0.00394
3002, 3001, 3011,'1 ',1,1,1, 0.00120, 0.00420,2,'3WNDSTAT1 ',1, 1,0.1238, 2,0.2477, 3,0.1548, 5,0.4737
0.00020, 0.02500, 1000.00, 0.00030, 0.01000, 1000.00, 0.00040, 0.01100, 1000.00,0.99014, 1.5613
1.01010, 500.000, 0.000, 1200.00, 1150.00, 1090.00, 1, 3002, 1.10020, 0.92000, 1.16000, 0.93000, 33, 0, 0.00013, 0.00016
1.05000, 230.000, 0.000, 1250.00, 1175.00, 1112.00, 0, 0, 1.10010, 0.90000, 1.14000, 0.91000, 22, 0, 0.00012, 0.00015
1.01000, 19.400, 0.000, 1280.00, 1200.00, 1157.00, 0, 0, 1.10000, 0.91000, 1.10000, 0.92000, 11, 0, 0.00011, 0.00014
3005, 3004, 0,'10',1,1,2, 206250, 0.00340,1,'WEST TX ',1, 1,0.2645, 2,0.4959, 3,0.1157, 4,0.1240
0.00035, 0.00964, 550.00
1.00000, 230.000, 0.000, 550.00, 500.00, 455.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 3, 0, 0.00000, 0.00000
1.00000, 500.000
3008, 3018, 0,'11',2,1,2, 196875, 0.00350,2,'CATDOG_XMER ',1, 1,0.2051, 2,0.2500, 3,0.4487, 4,0.0962
0.00044, 0.01276, 525.00
230.000, 230.000, 0.000, 525.00, 475.00, 423.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 22, 2, 0.00000, 0.00000
13.8000, 13.800
3008, 3009, 3010,'2 ',2,1,1, 0.00021, 0.00012,1,'3WNDSTAT2 ',2, 5,0.8000, 3,0.0500, 2,0.1000, 1,0.0500
0.00515, 0.50000, 20.00, 0.00920, 0.80000, 15.00, 0.00375, 0.41667, 25.00,0.98665, -25.7544
230.000, 230.000, 0.000, 20.00, 18.00, 14.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 33, 0, 0.00000, 0.00000
230.000, 230.000, 0.000, 15.00, 13.00, 9.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 33, 0, 0.00000, 0.00000
21.6000, 21.600, 30.000, 25.00, 19.00, 16.00, 0, 0, 1.10000, 0.90000, 1.10000, 0.90000, 33, 0, 0.00000, 0.00000
0 / END OF TRANSFORMER DATA, BEGIN AREA DATA
1, 101, -2800.000, 10.000,'CENTRAL '
2, 206, -1600.000, 10.000,'EAST '
3, 301, 2900.000, 55.000,'CENTRAL_DC '
4, 401, 300.000, 15.000,'EAST_COGEN1 '
5, 3011, 900.000, 10.000,'WEST '
6, 402, 300.000, 20.000,'EAST_COGEN2 '
0 / END OF AREA DATA, BEGIN TWO-TERMINAL DC DATA
1,1, 7.8543, 1490.65, 525.00, 400.00, 3.9420, 0.15560,'I', 0.00, 20, 1.00000
301, 2,13.00, 7.50, 0.0111, 3.8800, 500.0,0.44000,1.06275,1.10000,0.90000,0.00525, 0, 0, 0,'1 ', 2.0034
3021, 2,21.00,18.50, 0.0000, 3.0470, 230.0,0.95652,1.07500,1.10000,0.80000,0.00625, 0, 152, 3021,'T4', 2.0000
2,1, 8.2000, 1500.00, 525.00, 400.00, 4.1000, 0.15000,'I', 0.00, 20, 1.00000
301, 2,12.00, 8.00, 0.0110, 3.8800, 500.0,0.44000,1.05450,1.11200,0.90000,0.00515, 0, 0, 0,'1 ', 0.0098
3022, 2,20.00,18.00, 0.0120, 3.0470, 230.0,0.95652,1.06250,1.10000,0.80000,0.00625, 0, 152, 3022,'T5', 0.0074
0 / END OF TWO-TERMINAL DC DATA, BEGIN VSC DC LINE DATA
'VDCLINE1 ',1, 0.7100, 1,0.3204, 2,0.3883, 3,0.1942, 4,0.0971
3005,2,2, -209.00, 0.95000, 100.000, 0.100, 50.000, 400.00, 1200.00,0.10000, 100.00, -110.00, 0, 100.0
3008,1,1, 100.00, 0.99000, 90.000, 0.150, 40.000, 350.00, 1200.00,0.15000, 150.00, -140.00, 0, 100.0
'VDCLINE2 ',1, 0.3500, 1,0.3705, 2,0.3597, 3,0.1799, 4,0.0899
203,2,1, -100.00, 1.00000, 100.000, 0.150, 123.000, 200.00, 1200.00,1.00000, 200.00, -150.00, 0, 100.0
205,1,1, 100.00, 1.00000, 93.000, 0.120, 98.000, 250.00, 1250.00,1.00000, 225.00, -250.00, 0, 99.0
0 / END OF VSC DC LINE DATA, BEGIN SWITCHED SHUNT DATA
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
1
9
-
1
1
P
S
S
E
3
2
.
0
E
x
a
m
p
l
e
D
a
t
a
F
i
l
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
S
A
M
P
L
E
C
a
s
e
D
a
t
a
I
n
p
u
t
F
i
l
e
s
Figure 19-6 (Cont). SAMPLE Power Flow Raw Data File sample.raw (4 of 4 Sheets)
152,1,1.04500,0.95500, 0, 100.0,' ', -233.00, 1, -15.00, 2, -5.00, 3, -10.00, 4, -8.00, 5, -7.00, 6, -5.00, 7, -7.00, 8, -4.00
154,1,1.04480,0.96500, 0, 100.0,' ', 124.00, 1, 25.00, 2, 10.00, 2, 15.00, 1, 15.00, 2, 5.00, 3, 3.00, 2, 4.00, 1, 7.00
3005,4,0.98000,0.64000, 3005, 100.0,'VDCLINE1 ', 0.00, 1, 33.35
3021,2,1.00000,1.00000, 0, 100.0,' ', 499.66, 2, 200.00, 1, 100.00, 2, 50.00, 4, 25.00
3022,2,1.00000,1.00000, 0, 100.0,' ', 599.58, 4, 100.00, 2, 50.00, 4, 25.00, 3, 20.00, 2, 20.00
0 / END OF SWITCHED SHUNT DATA, BEGIN IMPEDANCE CORRECTION DATA
1, -30.00, 1.10000, -24.00, 1.09100, -18.00, 1.08400, -12.00, 1.06300, -6.00, 1.03200, 0.00, 1.00000, 6.00, 1.03000, 12.00, 1.06000, 18.00, 1.08000, 24.00, 1.09000, 30.00, 1.11000
2,0.60000, 1.06000,0.70000, 1.05000,0.80000, 1.04000,0.90000, 1.03000,0.95000, 1.02000,1.00000, 1.01000,1.05000, 0.99000,1.10000, 0.98000,1.20000, 0.97000,1.30000, 0.96000,1.40000, 0.95000
0 / END OF IMPEDANCE CORRECTION DATA, BEGIN MULTI-TERMINAL DC DATA
1, 4, 5, 4, 1, 212, 400.00, 0
402, 4,10.00, 8.00, 0.0000,19.0000, 500.0,0.22000,1.01000,1.10000,0.97000,0.01000, 321.00, 1.0000, 0.15000, 3
401, 4,10.00, 8.00, 0.0000,19.0000, 500.0,0.22000,1.01000,1.10000,0.97000,0.01000, 321.00, 1.0000, 0.15000, 3
212, 4,20.00,18.00, 0.0000,10.0000, 230.0,0.45200,1.04000,1.10000,0.90000,0.01000, 500.00, 1.0000, 0.00000, 1
213, 4,20.00,18.00, 0.0000,10.0000, 230.0,0.45200,1.10000,1.10000,0.90000,0.01000, -303.80, 1.0000, 0.00000, 4
1, 401, 4, 4,'DC1 ', 0, 0.0000, 4
2, 212, 2, 2,'DC2 ', 0, 0.0000, 2
3, 402, 4, 4,'DC3 ', 0, 0.0000, 4
4, 213, 2, 2,'DC4 ', 0, 0.0000, 2
5, 0, 4, 4,'DC5 ', 0, 0.0000, 4
1, 5,'1', 29.0000, 0.00
2, 5,'1', 29.0000, 0.00
3, 5,'1', 29.0000, 0.00
4, 5,'1', 29.0000, 0.00
0 / END OF MULTI-TERMINAL DC DATA, BEGIN MULTI-SECTION LINE DATA
201, -204,'&1', 207
0 / END OF MULTI-SECTION LINE DATA, BEGIN ZONE DATA
1,'NORTH_A1 '
2,'MID_A1_A2_A5'
3,'DISCNT_IN_A1'
4,'SOUTH_A1_A5 '
5,'ALL_A3 '
6,'NORTH_A5 '
7,'NORTH_A2 '
8,'SOUTH_A2 '
9,'ALL_A4_A6 '
0 / END OF ZONE DATA, BEGIN INTER-AREA TRANSFER DATA
1, 2,'A', 1000.00
1, 5,'B', -3800.00
2, 4,'C', -300.00
2, 6,'E', -300.00
3, 5,'D', 2900.00
0 / END OF INTER-AREA TRANSFER DATA, BEGIN OWNER DATA
1,'OWNER 1 '
2,'OWNER 2 '
3,'OWNER 3 '
4,'OWNER 4 '
5,'OWNER 5 '
0 / END OF OWNER DATA, BEGIN FACTS DEVICE DATA
1, 153, 0,1, 0.000, 0.000,1.01500, 50.000, 100.000,0.92630,1.13400,1.00000, 0.000, 0.05652, 100.0, 1, 0.00000, 0.00000,0
2, 153, 155,1, 350.000, 40.000,1.01500, 25.000, 9999.000,0.90000,1.10000,1.00000, 0.000, 0.05000, 100.0, 1, 0.00000, 0.00000,0
0 / END OF FACTS DEVICE DATA
Example Data Files PSS
E 32.0
SAMPLE Case Data Input Files Program Operation Manual
19-12 Siemens Energy, Inc., Power Technologies International
Figure 19-7. SAMPLE Sequence Data File sample.seq
0 / PSSE-30.0 FRI, JUN 04 2004 17:30
101,'1 ', 0.01101, 0.30001
102,'1 ', 0.01051, 0.32001
206,'1 ', 0.01061, 0.25101
211,'1 ', 0.01081, 0.26201
301,'1 ', 0.01091, 0.23001
301,'2 ', 0.01101, 0.24001
301,'3 ', 0.00801, 0.25001
401,'1 ', 0.01231, 0.22231
402,'1 ', 0.00451, 0.24321
3011,'1 ', 0.00761, 0.35431
3018,'1 ', 0.08701, 0.35631
3018,'2 ', 0.02401, 0.35531
0 / END OF POSITIVE SEQ. MACHINE IMPEDANCE DATA, BEGIN NEGATIVE SEQ. MACHINE DATA
101,'1 ', 0.01102, 0.30002
102,'1 ', 0.01052, 0.32002
206,'1 ', 0.01062, 0.25102
211,'1 ', 0.01082, 0.26202
301,'1 ', 0.01092, 0.23002
301,'2 ', 0.01102, 0.24002
301,'3 ', 0.00802, 0.25002
401,'1 ', 0.01232, 0.22232
402,'1 ', 0.00452, 0.24322
3011,'1 ', 0.00762, 0.35432
3018,'1 ', 0.08702, 0.35632
3018,'2 ', 0.02402, 0.35532
0 / END OF NEGATIVE SEQ. MACHINE IMPEDANCE DATA, BEGIN ZERO SEQ. MACHINE DATA
101,'1 ', 0.01103, 0.30003
102,'1 ', 0.01053, 0.32003
206,'1 ', 0.01063, 0.25103
211,'1 ', 0.01083, 0.26203
301,'1 ', 0.01093, 0.23003
301,'2 ', 0.01103, 0.24003
301,'3 ', 0.00803, 0.25003
401,'1 ', 0.01233, 0.22233
402,'1 ', 0.00453, 0.24323
3011,'1 ', 0.00763, 0.35433
3018,'1 ', 0.08703, 0.35633
3018,'2 ', 0.02403, 0.35533
0 / END OF ZERO SEQ. MACHINE IMPEDANCE DATA, BEGIN NEGATIVE SEQ. SHUNT DATA
154, 1.00240, 1.04210
201, 0.99240, 0.99042
3005, 1.00920, -1.00340
0 / END OF NEGATIVE SEQ. SHUNT DATA, BEGIN ZERO SEQ. SHUNT DATA
154, 0.99670, 0.98230
201, 0.99267, 0.98423
3005, 0.99467, -0.98423
0 / END OF ZERO SEQ. SHUNT DATA, BEGIN ZERO SEQ. NON-TRANSFORMER BRANCH DATA
151, 152,'1 ', 0.00710, 0.12100, 3.34000, 0.00710, 0.12121, 0.00713, 0.13211
151, 152,'2 ', 0.00712, 0.13200, 3.34200, 0.00712, 0.13232, 0.00724, 0.14323
151, 201,'1 ', 0.00300, 0.04500, 3.60000, 0.00000, 0.00000, 0.00000, 0.00000
152, 202,'1 ', 0.00250, 0.03000, 1.80000, 0.00000, 0.00000, 0.00000, 0.00000
152, 3004,'1 ', 0.00800, 0.08000, 5.00000, 0.00000, 0.00000, 0.00000, 0.00000
153, 154,'2 ', 0.01800, 0.16000, 0.30000, 0.00000, 0.00000, 0.00000, 0.00000
154, 155,'1 ', 1.00000, 0.20000, 2.00000, 0.30000, 3.00000, 0.40000, 4.00000
154, 203,'1 ', 5.00000, 0.23100, 1.00000, 0.30600, 2.00000, 0.37000, 3.00000
154, 205,'1 ', 2.00000, 0.20000, 3.00000, 0.30000, 4.00000, 0.40000, 5.00000
154, 3008,'1 ', 0.00800, 0.06500, 0.60000, 0.00000, 0.00000, 0.00000, 0.00000
201, 202,'1 ', 0.00500, 0.07000, 4.00000, 0.00000, 0.00000, 0.00000, 0.00000
201, 207,'C1', 0.00450, 0.04500, 0.40000, 0.00000, 0.00000, 0.00000, 0.00000
203, 205,'1 ', 0.01500, 0.13000, 0.15000, 0.00000, 0.00000, 0.00000, 0.00000
204, 207,'C2', 0.00450, 0.45000, 0.40000, 0.00000, 0.00000, 0.00000, 0.00000
205, 214,'2 ', 0.00600, 0.07500, 0.80000, 0.00000, 0.00000, 0.00000, 0.00000
205, 216,'3 ', 0.01500, 0.13000, 0.15000, 0.00000, 0.00000, 0.00000, 0.00000
205, 217,'4 ', 0.01500, 0.13000, 0.15000, 0.00000, 0.00000, 0.00000, 0.00000
205, 218,'5 ', 0.01500, 0.13000, 0.15000, 0.00000, 0.00000, 0.00000, 0.00000
213, 214,'1 ', 0.00000, 0.01000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000
3001, 3003,'1 ', 0.00000, 0.00800, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000
3002, 3004,'1 ', 0.01600, 0.16000, 0.20000, 0.00000, 0.00000, 0.00000, 0.00000
3005, 3006,'1 ', 0.00800, 0.08000, 0.15000, 0.00000, 0.00000, 0.00000, 0.00000
3005, 3007,'1 ', 0.00700, 0.07500, 0.12000, 0.00000, 0.00000, 0.00000, 0.00000
3007, 3008,'1 ', 0.00700, 0.07000, 0.12000, 0.00000, 0.00000, 0.00000, 0.00000
3008, 3009,'1 ', 0.00700, 0.07000, 0.12000, 0.00000, 0.00000, 0.00000, 0.00000
0 / END OF ZERO SEQ. NON-TRANSFORMER BRANCH DATA, BEGIN ZERO SEQ. MUTUAL DATA
151, 152,'1 ', 151, 152,'2 ', 0.00210, 0.02200, 0.00000, 1.00000, 0.00000, 1.00000
154, 203,'1 ', 203, 205,'1 ', 0.00110, 0.01200, 0.75000, 1.00000, 0.00000, 0.25000
0 / END OF ZERO SEQ. MUTUAL DATA, BEGIN ZERO SEQ. TRANSFORMER DATA
101, 151, 0,'T1', 3, 0.00480, 0.00720, 0.00010, 0.00771
102, 151, 0,'T2', 3, 0.00481, 0.00721, 0.00013, 0.00773
152, 153, 0,'T3', 1, 0.00000, 0.00000, 0.00019, 0.00794
152, 3021, 0,'T4', 2, 0.00482, 0.00722, 0.00021, 0.00815
152, 3022, 0,'T5', 2, 0.00483, 0.00723, 0.00012, 0.00523
201, 211, 0,'T6', 2, 0.00484, 0.00724, 0.00026, 0.00343
202, 203, 0,'T7', 1, 0.00000, 0.00000, 0.00072, 0.00743
204, 205, 0,'T8', 6, 0.00374, 0.00652, 0.00046, 0.00563
205, 206, 0,'T9', 7, 0.00375, 0.00653, 0.00018, 0.00533
205, 215, 216,'3 ', 2, 0.00000, 0.00000, -0.00015, 0.05833, 0.00530, 0.44166, 0.00390, 0.35834
205, 217, 218,'4 ', 2, 0.00000, 0.00000, 0.00324, 0.00451, 0.00153, 0.08333, 0.00537, 0.05167
3002, 3001, 3011,'1 ', 1, 0.00000, 0.00000, 0.00345, 0.00251, 0.00456, 0.00125, 0.00789, 0.00187
3004, 3005, 0,'10', 5, 0.00376, 0.00654, 0.00036, 0.00991
3008, 3018, 0,'11', 4, 0.00000, 0.00000, 0.00044, 0.01276
3008, 3009, 3010,'2 ', 2, 0.00000, 0.00000, 0.00000, 0.00010, 0.00000, 0.00010, 0.00000, 0.00010
0 / END OF ZERO SEQ. TRANSFORMER DATA, BEGIN ZERO SEQ. SWITCHED SHUNT DATA
152, -0.00900, -0.00910, -0.00920, -0.00930, -0.00940, -0.00950, -0.00960, -0.00970
154, 0.00810, 0.00820, 0.00830, 0.00840, 0.00850, 0.00860, 0.00870, 0.00880
3005, 0.00950
3021, 0.00000, 0.00000, 0.00000, 0.00000
3022, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000
0 / END OF ZERO SEQ. SWITCHED SHUNT DATA
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
1
9
-
1
3
P
S
S
E
3
2
.
0
E
x
a
m
p
l
e
D
a
t
a
F
i
l
e
s
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
S
A
M
P
L
E
C
a
s
e
D
a
t
a
I
n
p
u
t
F
i
l
e
s
Figure 19-8. SAMPLE Slider File sample.sld
Example Data Files PSS
E 32.0
SAMPLE Case Data Input Files Program Operation Manual
19-14 Siemens Energy, Inc., Power Technologies International
This page intentionally left blank.
Siemens Energy, Inc., Power Technologies International 20-1
Chapter 20
Model Writing
This chapter gives an introduction to the fundamentals of writing equipment models for use in the
dynamic simulation of PSS
E.
20.1 Background
The objective of dynamic simulations is to accurately simulate the response of a physical system to
some event. This, in turn, requires that each component affecting the response be faithfully
modeled over the time frame of interest. In PSS
E Model Library contains a wide variety of equipment models which satisfy this require-
ment for the vast majority of generating plant equipment. However, situations may arise in which
there is no library model which corresponds to the differential equations needed to model a given
piece of equipment. To handle this situation, engineers historically have tried to modify the data
characterizing the equipment to fit the block diagram of an existing model. Rather than resorting to
this approach, the PSS
E simulation models.
Model Writing PSS
E 32.0
Prerequisites Program Operation Manual
20-2 Siemens Energy, Inc., Power Technologies International
20.2 Prerequisites
Section 18.1 gives an overview of the dynamic simulation process and the dynamic simulation data
structure as implemented in PSS
E model.
3. Is familiar with the PSS
E models. Each model must make different types of computations at different stages
in the dynamic simulation process.
A set of scalar variables which are present in PSS
E
activities which invoke equipment models set seven flags before calling these modules. These flags
are the variables MODE, KPAUSE, MSTATE, MIDTRM, ITER, IFLAG and IBDOCU. Activities
STRT, RUN, MSTR and MRUN sense the variable KTRIP which must be set by any equipment
models that implement network data changes which affect the network admittance matrix.
At the most basic model writing level, the MODE flag is the most critical of these variables. In state-
space simulations the significance of MODE is as follows:
MODE=1 The model must initialize all of its state variables and algebraic variables. Prior to
the first network solution iteration (i.e., when the variable ITER is zero), load charac-
teristic models which are not coordinated call models (see Section 18.4.2) must set
the initial values of any variables needed in the current injection calculations of
subsequent model calls issued during network solution iterations.
MODE=2 The model must make all computations needed to place time derivatives into the
DSTATE array; each stabilizer model must compute the present value of its output
signal and place it in the appropriate entry in the VOTHSG array; each minimum
excitation limiter model must compute the present value of its output signal and
place it in the appropriate entry in the VUEL array; each maximum excitation limiter
model must compute the present value of its output signal and place it in the appro-
priate entry in the VOEL array.
MODE=3 Each stabilizer model must compute the present value of its output signal and place
it in the appropriate entry in the VOTHSG array; each minimum excitation limiter
model must compute the present value of its output signal and place it in the appro-
priate entry in the VUEL array; each maximum excitation limiter model must
compute the present value of its output signal and place it in the appropriate entry in
the VOEL array; an excitation system model must compute the present value of
excitation system output voltage and place it in the EFD array; a turbine governor
model must compute the present value of turbine mechanical power and place it in
the PMECH array; other models written by users normally have no requirements in
MODE three.
MODE=4 The model must update the PSS
E 32.0
Model Requirements Program Operation Manual
20-4 Siemens Energy, Inc., Power Technologies International
The variable KPAUSE is meaningful in MODEs one through four and indicates the type of time step
calculation being performed by activities RUN, MRUN, ERUN, or GRUN:
Most user-written models need not be sensitive to the variable KPAUSE.
The variable MSTATE is meaningful in MODEs one through four and indicates the type of simulation
being performed by activities STRT/RUN, MSTR/MRUN, ESTR/ERUN, GSTR/GRUN or ASTR:
The LOGICAL variable MIDTRM is meaningful in MODEs one through four and indicates whether
state-space or extended term simulations are being performed:
The variable ITER is meaningful only in MODEs one and three during the network solution calcula-
tion, and it indicates the number of iterations completed during the network solution for the present
value of simulation time. It is usually sensed in MODE one by load characteristic models which are
not implemented as coordinated call models (see Section 18.4.2) and which have initialization
requirements which must be performed prior to any network solution iterations (i.e., when ITER is
zero).
The variable IFLAG is meaningful only in MODEs one and three during the network solution calcu-
lation and is usually sensed by models called from subroutines TBLCNT and CONET. These
subroutines are called once each iteration, and once more following convergence of the network
solution. IFLAG indicates the status of the network solution calculation:
MODE=8 The model is being called to return descriptions of each CON and ICON data input
value used by the model.
KPAUSE=0 Models are being called to make their normal time step calculations.
KPAUSE=1 Models are being called for the value of simulation TIME equal to TPAUSE
_
, just
prior to a pause. Any models which perform local integrations or accumulations,
or which update local transport delay tables, should bypass these calculations.
KPAUSE=2 Models are being called at the first time step following a pause (i.e., for the same
value of simulation TIME as on the last time step calculation).
MSTATE=0 Standard state-space dynamic simulation via activities STRT and RUN, or
activity ASTR.
MSTATE=1 Excitation system response ratio test via activities ESTR and ERUN. Models
other than generator and excitation system models are not called.
MSTATE=2 Excitation system open circuit step response test via activities ESTR and ERUN.
Models other than generator and excitation system models are not called.
MSTATE=3 Governor response test via activities GSTR and GRUN. Models other than
generator and turbine governor models are not called.
MSTATE=4 Extended term dynamic simulation via activities MSTR and MRUN.
MSTATE=5 Dynamics data is present but no initialization activity has been successfully
executed.
MIDTRM=.FALSE. State-space simulation.
MIDTRM=.TRUE. Extended term simulation.
IFLAG=.FALSE. The network solution has not achieved convergence.
Siemens Energy, Inc., Power Technologies International 20-5
PSS
E network
data array values directly. To force a dual time step calculation, KPAUSE must be set to 1 and
KTRIP to the appropriate non-zero value:
When KTRIP of 1 (or -1) is required in RUN and MRUN, care must be taken to ensure that some
other model has not already set KTRIP to -1 (or -3). Therefore, the statement for setting KTRIP is
one of the following:
IF (KTRIP.EQ.0) KTRIP=1
IF (KTRIP.GE.0) KTRIP=-1
KTRIP=-3
IFLAG=.TRUE. The network solution has converged or reached its maximum number of
iterations.
IBDOCU=0 Process all models called.
IBDOCU>0 External bus number; only process models called at bus IBDOCU. Only
models called from subroutines CONEC or CONET need to sense IBDOCU.
KTRIP=0 No dual time step calculation required.
KTRIP=1 In activities RUN and MRUN one or more data changes requiring a dual time step
calculation were implemented, but none of these affect the network admittance
matrix.
KTRIP=-1 In activities STRT and MSTR, one or more load models changed the value of the
constant admittance component of a load. In activities RUN and MRUN, one or
more data changes affecting the admittance matrix have been implemented; no
zero impedance line switchings were implemented.
KTRIP=-3 In activities RUN and MRUN, one or more data changes affecting the admittance
matrix have been implemented; at least one zero impedance line switching was
implemented.
Model Writing PSS
E 32.0
Model Calling Sequence Rules Program Operation Manual
20-6 Siemens Energy, Inc., Power Technologies International
20.4 Model Calling Sequence Rules
When activity DYRE is used to introduce user-written models into a simulation setup, the corre-
sponding records in the Dynamics Data Input File are required to be in the format of the special
USRMDL, USRLOD, USRREL, USRAUX, USRFCT, and USRDCL records described in User-
Written Models. In addition, these models must be written so as to be compatible with the calling
sequences assumed when these models are called from subroutines TBLCNC, TBLCNT, CONEC
or CONET (see Section 18.1.1).
The SUBROUTINE statements for plant-related models must be of the form:
SUBROUTINE modelname (MC, ISLOT)
where:
Using the notation of User-Written Models, at the completion of activity DYRE, the array allocation
table entries for each plant-related model reference are set as follows:
The SUBROUTINE statements for load-related models must be of the form:
SUBROUTINE modelname (LD, ISLOT, ISLOT2)
where:
Using the notation of User-Written Models, at the completion of activity DYRE, the array allocation
table entries for each load-related model reference are set as follows:
MC Is the internal PSS
E load array index for the load at which the model is being
called.
ISLOT Is the internal PSS
E array allocation table index for the shared data for this
model call.
ISLOT2 Is the internal PSS
E array allocation table index for the private data for this
model call.
LDSTRT(1,ISLOT) Contains the index of the first of NC CONs used by the model, or zero if
NC is zero.
LDSTRT(2,ISLOT) Contains the index of the first of NI shared ICONs used by the model, or
zero if NI is zero.
Siemens Energy, Inc., Power Technologies International 20-7
PSS
E double entry line array index for the line at which the
model is being called.
RS Is the relay slot (1 or 2) as specified on the USRREL data record.
ISLOT Is the internal PSS
E 32.0
Model Calling Sequence Rules Program Operation Manual
20-8 Siemens Energy, Inc., Power Technologies International
Using the notation of User-Written Models, at the completion of activity DYRE, the array allocation
table entries for each auxiliary-signal model reference are set as follows:
The auxiliary-signal model output has to be calculated and stored in the first VAR location VAR(L)
where L is the starting VAR index for that auxiliary-signal model (i.e., L=STRTAU(3,ISLOT)). Subse-
quently, depending on the type of device with which the auxiliary-signal model is associated with,
the model output contained in VAR(L) is then transferred by PSS
E standard
arrays, DC2SIG or DCMSIG or VSCSIG or FCTSIG. The array locations in DC2SIG, DCMSIG,
VSCSIG, and FCTSIG into which VAR(L) is transferred, corresponds to the device number (internal
VSC device index for VSC dc lines) and the signal index (i.e., the signal injection point number) for
which the auxiliary-signal model is called.
The SUBROUTINE statements for FACTS device models must be of the form:
SUBROUTINE modelname (IDVX, ISLOT)
where:
Using the notation of User-Written Models, at the completion of activity DYRE, the array allocation
table entries for each FACTS device model reference are set as follows:
ISGX Is the signal injection point number (or the auxiliary-signal index). This is any
number 1 through maximum number of auxiliary-signals that can be associated
with the device type under consideration (see Table 3-1 for the maximum number
of auxiliary-signals that can be attached to each device type).
ISLOT Is the internal PSS
E 32.0
Model Calling Sequence Rules Program Operation Manual
20-10 Siemens Energy, Inc., Power Technologies International
The CALL statements for the two-terminal dc line models that are not yet in a table-driven form (i.e.,
not called from internal PSS
E model are:
1. Determine the block diagram and/or the differential and algebraic equations of the equip-
ment to be modeled.
2. Identify the state variables associated with the model and determine a procedure for
computing their time derivatives.
3. Identify those quantities needed as inputs to the model.
4. Allocate locations in the CON, STATE, VAR and/or ICON arrays as required.
5. Write the model subroutine in FORTRAN or FLECS.
This procedure is best illustrated by an example. Consider the simple excitation system shown in
Figure 20-1. (Note that this example is for illustrative purposes only. In fact, this model is not likely
to be suitable for modeling any excitation system.)
Figure 20-1. Simple Excitation System
The first transfer function block of this model involves one state variable which is shown as E
sensed
,
the voltage transducer output. This transfer function gives the equation:
Cross multiplying and rearranging gives the required expression for the time derivative as:
Similarly, for the second transfer function, the exciter:
V
error
K
1 + sT
e
E
sensed
E
C
1
1 + sT
r
V
ref
Other Signals
0
E
E
fd E
+
+
V
othsg
E
sensed
= E
C
1
1 + sT
r
sE
sensed
=
dE
sensed
=
E
C
- E
sensed
dt T
r
E = V
error
K
1 + sT
e
Model Writing PSS
E 32.0
Writing the Basic Model Program Operation Manual
20-12 Siemens Energy, Inc., Power Technologies International
resulting in:
The limit block is a simple clip (windup limit) prohibiting a negative exciter output voltage. Note that,
because this is an excitation system model, the model output, E
fd
, must be placed in the EFD array
for use by the generator model.
We may now allocate memory locations in the various dynamics data arrays (refer to Table 18-1).
Model inputs:
Model outputs:
Other model variables:
V
error
may be treated as a local variable in our model subroutine because its value need not be
preserved from one time step to the next. The model writer could elect to assign such a quantity to
a VAR if it is desired to place it in an output channel.
Thus, our model requires three CONs (J through J+2), two STATEs (K and K+1), and no VARs or
ICONs. The index I shown above is the machine array index assigned to the machine at which the
model is to be called.
Following the model calling conventions of PSS
E 32.0
Writing the Basic Model Program Operation Manual
20-14 Siemens Energy, Inc., Power Technologies International
In MODE four, the model must update NINTEG if the highest numbered STATE which it uses is
greater than the present value of NINTEG:
NINTEG=MAX(NINTEG,K+1)
MODE's five through six handle the model's responsibilities during activities DOCU and DYDA. In
activities DOCU and DYDA, all model output should be written to the FORTRAN unit number
contained in the variable IPRT. In MODE eight, definitions of CON and ICON input values are placed
in the arrays CON_DSCRPT and ICON_DSCRPT, respectively.
The complete basic model subroutine may now be assembled from the above code fragments as
shown in Figure 20-23. This code references the FLECS procedure shown in Figure 20-3, which
has to be inserted just before the END statement of Figure 20-23.
The following points on this model coding should be noted.
1. The file specified in the INCLUDE statement provides access to the main PSS
E data
arrays and COMMON variables. This syntax can be used for model source codes written
in FLECS as well as pure FORTRAN.
The I of the INCLUDE is in Column 7 for both FLECS and FORTRAN models.
2. The code in Figure 20-23 contains declaration of FORTRAN intrinsic functions, EXTERNAL
subprogram declarations, and type declaration for local variables.
3. This model has not as yet been coded for use in extended term simulations (see
Section 20.9). When MIDTRM is.TRUE., activity MSTR is being executed; the model calls
BADMID which prints an appropriate message and sets a flag which does not allow
activity MRUN to be executed. The model then RETURNs.
The three arguments of subroutine BADMID are the machine array index, the bus
sequence number, and the model name enclosed in single quotes. It is used in plant-
related models which have not been written for use in extended term simulations.
A similar subroutine, BADMDL, is used in load-related models which have not been
expanded for use in extended term simulations. Its three arguments are the load array
index, the bus sequence number, and the model name enclosed in single quotes.
Finally, a subroutine, BADMD2, is used in all other models which have not been expanded
for use in extended term simulations. It has a single argument: the model name enclosed
in single quotes.
4. Any error or progress report messages written in MODEs one through four should be
written to the FORTRAN unit number specified by the variable LPDEV.
5. When this model is used at a machine, the output signal of any excitation limiter model
called at the machine is ignored. Some excitation system models use the sum:
6. VOTHSG(I) + VUEL(I) + VOEL(I)
7. as their single supplementary signal input.
8. ISLOT is undefined in MODE eight. Hence the code for MODE eight appears before the
use of ISLOT.
Siemens Energy, Inc., Power Technologies International 20-15
PSS
E 32.0
Writing the Basic Model Program Operation Manual
20-16 Siemens Energy, Inc., Power Technologies International
Figure 20-23 (Cont). Basic DEMOEX Model Routine
C BUS SEQUENCE NUMBER NEGATIVE IF MACHINE
C IS OFF-LINE, SVS OR INDUCTION MACHINE
C
IB=NUMTRM(I)
IF (IB.LE.0) RETURN
C
IF (MIDTRM) GO TO 900
GO TO (100,200,300,400), MODE
C
C MODE = 1 - INITIALIZE
C
100 STATE(K)=ECOMP(I)
STATE(K+1)=EFD(I)
VREF(I)=ECOMP(I) + EFD(I)/CON(J+1)
IF (EFD(I).LT.0.) WRITE(LPDEV,307) NUMBUS(IB),MACHID(I)
RETURN
C
C MODE = 2 - CALCULATE DERIVATIVES
C
200 DSTATE(K)=(ECOMP(I)-STATE(K))/CON(J)
VERROR=VREF(I)+VOTHSG(I)-STATE(K)
DSTATE(K+1)=(CON(J+1)*VERROR-STATE(K+1))/CON(J+2)
RETURN
C
C MODE = 3 - SET EFD
C
300 EFD(I)=MAX(STATE(K+1),0.)
RETURN
C
C MODE = 4 - SET NINTEG
C
400 NINTEG=MAX(NINTEG,K+1)
RETURN
C
C MODE > 4
C
1000 IM=MACHID(I)
IB=ABS(NUMTRM(I))
IBUS=NUMBUS(IB)
C
IF (MODE.EQ.6) GO TO 2000
C
Siemens Energy, Inc., Power Technologies International 20-17
PSS
E 32.0
Model Writing Notes Program Operation Manual
20-18 Siemens Energy, Inc., Power Technologies International
20.6 Model Writing Notes
To incorporate a model into a dynamics setup after it has been written, compile the model along with
the CONEC and CONET files (if any) and create a dll (typically the dsusr.dll).
Activity DYRE recognizes user-written models and processes them correctly only if:
1. They are specified on the special USRMDL, USRLOD, USRREL, USRAUX, USRFCT, and
USRDCL data records in the Dynamics Data Input File (see User-Written Models).
and
2. They are written assuming the subroutine calling sequences given in Section 20.4.
The model developed in Section 20.5 was written with the calling sequence required for plant-
related models. The corresponding DYRE data record might be:
101 'USRMDL' 1 'DEMOEX' 4 0 0 3 2 0 0.05 100. 0.4 /
User-written models for generating plant equipment, load characteristics and relays, line relays,
auxiliary-signal, FACTS devices, and dc lines must be written so as to be compatible with the
USRMDL, USRLOD, USRREL, USRAUX, USRFCT, and USRDCL data records, respectively,
given in Section . It is strongly recommended that other equipment models also be compatible with
the USRMDL data record requirements; however, user-written models for nonplant equipment
which do not conform to the above constraints may be introduced into a simulation using the
approach described in Section 18.9.1.
While the excitation system model developed in Section 20.5 was required to initialize an entry in
the VREF array, turbine governor, stabilizer and excitation limiter models have no initialization
duties other than initializing their own STATEs and VARs.
Plant-related models use the approach shown in the previous example to obtain machine and bus
array indices.
For user-written cross-compound governor models (i.e., IC is eleven on the USRMDL data record),
the machine index of the low pressure unit is obtained as in the following example:
I2=IBITS(MACNUM(ISLOT),16,16)
where IBITS is the FORTRAN intrinsic function for extracting a sequence of bits, and ISLOT is the
second argument of the models SUBROUTINE statement as in the DEMOEX model.
The DEMOEX model is written under the assumption that all of its constant parameters have
nonzero values. If a constant is allowed to be zero, care must be taken in the model to avoid division
by that constant. A common case is the transfer function of a transducer such as the first STATE in
the DEMOEX model.
Siemens Energy, Inc., Power Technologies International 20-19
PSS
E 32.0
Model Writing Notes Program Operation Manual
20-20 Siemens Energy, Inc., Power Technologies International
Coding such as that shown in this example is suitable for all plant-related models. Models called
from subroutines CONEC and CONET are handled in essentially the same manner but have two
additional duties in activities DOCU and DYDA:
1. The model must determine if selective mode is active, and if so, if it should do anything or
simply RETURN. The following code fragment, assuming a bus type model, with the bus
number contained in ICON(I), handles this function:
IF (IBDOCU.GT.0)
. IF (ICON(I).NE.IBDOCU) RETURN
...FIN
2. For line type models, it becomes a little more complicated. In activity DOCU, both ends of
the branch need to be looked at and, if either is equal to IBDOCU, the model should act. In
activity DYDA, however, only one end (e.g., the from bus of an ac branch) should be
checked so that the record appears only once in the output.
3. In activity DYDA, the model must check for the AB interrupt code before writing its output
record. Code such as in the following code fragment must be inserted before the first
executable statement:
CHARACTER IVEC(1)*2
SAVE IVEC
DATA IVEC/'AB'/
Then the following code is needed immediately preceding the activity DYDA WRITE state-
ment:
CALL CONINT(IVEC,1,JJ)
IF (JJ.NE.0) RETURN
Siemens Energy, Inc., Power Technologies International 20-21
PSS
E
Program Application Guide.
It is strongly recommended that models first be developed, tested and used with activities STRT
and RUN using the modeling techniques described in this section. For users with the Extended
Term Simulation Section of PSS
E 32.0
Coordinated Call Models Program Operation Manual
20-22 Siemens Energy, Inc., Power Technologies International
20.8 Coordinated Call Models
Many equipment models are called during the network solution to calculate current injections which
are dependent on the voltage at the bus to which they are connected. Models that contain both
differential equation responsibilities and current injection responsibilities meet their modeling
requirements in PSS
E Model
Library as well as user-written models, must have their primary entry point name beginning with a
character other than T.
Siemens Energy, Inc., Power Technologies International 20-23
PSS
E 32.0
Writing a Basic Load Model Program Operation Manual
20-24 Siemens Energy, Inc., Power Technologies International
In the models supplementary entry point, the bus sequence number must be determined. If the load
is out-of-service, the model does no further calculations. The starting array index in the CON array
for use in this model call is determined. The coding is:
C
C BUS SEQUENCE NUMBER NEGATIVE IF LOAD IS OUT-OF-SERVICE
C
IB=NUMLOD(I)
IF (IB.LE.0) RETURN
C
C GET STARTING 'CON' INDEX
C
J=LDSTRT(1,ISLOT)
In the above code fragment, I is the load array index and IB is the bus sequence number at which
load I is connected (see Bus Sequence Numbers).
In load characteristic models, it is important to recognize that the network solution subroutine SITER
has already made an injection into the CURNT array corresponding to the values present in the
standard load characteristic array CLODFR. It is the models responsibility, therefore, to inject the
difference between the total load as calculated by the model and the standard load characteristic
already injected. This may be done either by injecting the incremental amount, or by first making an
injection to cancel out the standard injection from CURNT and then injecting the new total load
model injection.
The following code fragment calculates the total load injected by SITER expressed in MVA
(PQOLD), and the total effective load as corrected for frequency sensitivity (PQNEW). It places the
active and reactive components of the effective load into the TPLOAD and TQLOAD arrays, respec-
tively. Finally, it injects the load increment into the CURNT array. The coding is:
C
C CALCULATE TOTAL LOAD FOR STANDARD CHARACTERISTICS
C
VM=ABS(VOLT(IB))
C
PQOLD=CLODFR(1,I)
IF (VM.LT.PQBRAK) PQOLD=PQOLD*CNSTPQ(VM)
C
S=VM*CLODFR(2,I)
IF (VM.LT.0.5) S=S*CNSTCR(VM)
PQOLD=PQOLD+S
C
PQOLD=PQOLD + VM*VM*CONJG(CLODFR(3,I))
C
C CALCULATED DESIRED TOTAL LOAD INJECTION
C
PQNEW=PQOLD*(1.+CON(J)*BSFREQ(IB))
C
TPLOAD(I)=REAL (PQNEW)
TQLOAD(I)=AIMAG(PQNEW)
C
C INJECT LOAD INCREMENT (MODEL INJECTION - STANDARD INJECTION)
Siemens Energy, Inc., Power Technologies International 20-25
PSS
E 32.0
Overview Program Operation Manual
21-2 Siemens Energy, Inc., Power Technologies International
21.1.1 Event Item Type
The following table describes the supported Event Types and their implementation when run in
Dynamics and Power Flow Study modes.
21.1.2 Event Study Properties
The user specifies the general parameters which will be used when the event study is run. All fields
are initially filled with default values, however the user may edit them all.
The following fields are used only if the Event Study is run as a Dynamics Event Study. The values
in these fields have no significance if the Event Study is run as a Power Flow Event Study.
Table 21-1. Supported Event Types
Event Type Dynamics Implementation Power Flow Implementation
Connect Bus Re-connect Bus - RECN Re-connect Bus - RECN
Disconnect Bus Disconnect Bus - DSCN Disconnect Bus - DSCN
Connect Machine Machine Status switch Machine Status switch
Disconnect Machine Machine Status switch Machine Status switch
Connect Load Load Status switch Load Status switch
Disconnect Load Load Status switch Load Status switch
Connect/Close Line
Branch/Transformer Close
Disturbance
Branch/Transformer Status switch
Disconnect/Trip Line
Branch/Transformer Trip
Disturbance
Branch/Transformer Status switch
Bus Fault Bus Fault Disturbance
Multiple unbalanced network solu-
tion - SCMU
Line Fault
Branch/Transformer Line Fault
Disturbance
Multiple unbalanced network solu-
tion - SCMU
Unbalanced Bus Fault
Calculate and Apply Unbalanced
Bus Fault
Multiple unbalanced network solu-
tion - SCMU
Unbalanced Line Fault Calculate and Apply Branch Fault
Multiple unbalanced network solu-
tion - SCMU
Vref Change Vref Change Disturbance (not applicable)
Table 21-2. Dynamics Event Study Properties
Property Description
Study length Total duration of the event study in seconds.
Integration step Time interval, in seconds, between steps.
Tolerance PSS
E 32.0
Overview Program Operation Manual
21-4 Siemens Energy, Inc., Power Technologies International
21.1.4 Running an Event Study
There are two types of event studies, a dynamic study and a power flow study. In order to run a
Dynamic Study, dynamics data must be present. If an event study file has been read into the
program, event items in the active study will also be indicated on the one-line diagram. More that
one Event Item can be associated with any Network Item and only one Event symbol will be
displayed on the Network Item in the diagram.
Admit-
tance/Fault
impedance
R (ohms); default = 0
X (ohms); default = 0
Network Items
User-specified network elements:
Bus
Load
Machine
Branch
3-Winding Transformer
Table 21-3. Event Item Properties (Cont.)
Property Description
Siemens Energy, Inc., Power Technologies International 22-1
Chapter 22
Scenarios
22.1 Overview
Scenarios are groups of files that are used to perform a single study. They can consist of the net-
work files, both Power Flow and Dynamics, in both the raw and binary forms, Slider Diagrams, Bus
Location and Subsystem configuration files, Contingency analysis files (Subsystem Description file,
Monitored Element file, Contingency file, Distribution Factors file) and Sequence and OPF data
files. All the files used in the study can be stored in a Scenario file. The Scenario file is based on
XML so that it is easily readable by all text editors (see Figure 22-1). When a Scenario file is
opened, all the files described in the Scenario file are either opened or set for other functions that
use them. Scenario files provide a convenient way to manage the myriad number of files associated
with a PSS
E 32.0
Overview Program Operation Manual
22-2 Siemens Energy, Inc., Power Technologies International
Figure 22-1. Scenario XML File
22.1.1 General Workflow using Scenarios
The following outline the general workflow using Scenarios. To begin using Scenarios, a New Sce-
nario file is defined. A name is assigned for the Scenario file as well as its location in the directory
structure. This location is important as it serves as the Root Path for all files in the Scenario. If files
that are added to the Scenario are located in the same directory as the Scenario file itself, then they
are saved as the filename plus the Root Path (see Figure 22-1). The Root Path itself is defined in
the Scenario file and can be changed to a different location. This allows us to move the entire Sce-
nario to another machine and use the Scenario file without having to replicate the directory structure
that existed on the original machine. All that need to be done is to open the Scenario file, open the
Scenario Editor, change the Root Path, save it and then re-open the Scenario file. Now all the files
contained within the Scenario file will be opened/loaded automatically.
If a Scenario file already exists, it can be opened through a file selection dialog and all the files con-
tained within will be opened/loaded automatically.
Siemens Energy, Inc., Power Technologies International 22-3
PSS
E 32.0 Scenarios
Program Operation Manual Overview
After a Scenario file has been opened, opening and referencing files in PSS
E will automatically
add them to the Scenario.
The Scenario file can be saved at any time, either to the same name or to a different name.
Closing an open Scenario file will close/unload all files contained in the Scenario.
Files may also be added or removed from an open Scenario through the use of the Scenario Editor.
22.1.2 Scenario Editor
The fields at the top of the dialog list the creation and modification dates of the Scenario as well as
the version of PSS
E for which the Scenario was originally created. They also show the login ID of
the user who created and last updated the Scenario. The RootPath field shows the file path which
is used to complete the files listed in the Scenario. The RootPath is changed by selecting the
browse button [] to the right of the field and using a standard file directory selector dialog to select
the new RootPath. If a file was added to the Scenario in a directory other than that described by the
RootPath, the full path will be described for this file.
The user specifies the type of file to add to the scenario. Certain file types, such as RAW, SAV, DYR
and SNP can only have one instance in a Scenario file. If one already exists, adding a new one will
replace the existing file. Other files types, such as SLD file, can have multiple instances in the
Scenario File.
Scenarios PSS
E 32.0
Overview Program Operation Manual
22-4 Siemens Energy, Inc., Power Technologies International
This page intentionally left blank.
Siemens Energy, Inc., Power Technologies International A-1
Appendix A
Activity Summary
Each PSS
E activity performs a specific single function. Each activity requires that certain data be
present in working memory and/or in one or more of the PSS
E activities, together with their prerequisites and brief descriptions of their functions.
A
-
2
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Table A-1. PSS
E Activities
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
File>New
[New]
Create a new case, case with diagram,
diagram, or plot book.
- - - - - -
File>Open
[Open]
CASE
Open power flow Saved Case file and
establish it as the working case.
Previous contents of the
working case overwritten.
Saved Case file (*.sav)
File>Open
[Open]
DYRE Read a Dynamics Data File
Validly specified power flow
case, solved to an accept-
able mismatch level.
Generators represented as
current sources (activity
CONG must have been
executed).
Dynamics Model Raw Data
File (*.dyr)
File>Open
[Open]
MCRE
Add machines to an existing plant, enter
machine impedance data, and split the
plant loading among individual machines.
Validly specified power flow
case.
Machine Impedance Data
file (*.rwm)
File>Open
[Open]
RDCH
Read power flow source data records
from a file
Validly specified power flow
case.
Power Flow Raw Data file
(*.raw)
File>Open
[Open]
READ
Read power flow source data records
from a file.
If reading change data, the
working case must contain a
validly specified power flow
case.
- - -
File>Open
[Open]
REMM
Read transaction raw data from a Trans-
actions Raw Data File, replacing all
existing transaction data.
Validly specified power flow
case.
Transactions Raw Data File
(*.mwm)
File>Open
[Open]
RESQ Read sequence data for fault analysis
Positive sequence network
where sequence data is to
be read must be present in
the working case.
Sequence Data file (*.seq)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
3
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
File>Open
[Open]
ROPF Read optimal power flow data.
Validly specified power flow
case.
Optimal Power Flow Data
File (*.rop)
File>Open
[Open]
RSTR
Restore dynamics working memory from
a binary Snapshot File
- - -
Dynamics Snapshot Data
File (*.snp)
File>Open
[Open]
SRRS
Read a Source Form Snapshot File into
dynamics working memory. The previous
contents of dynamics working memory
are destroyed.
Validly specified power flow
case, solved to an accept-
able mismatch level.
Generators represented as
current sources (activity
CONG must have been
executed).
Dynamics Snapshot Raw
Data file (*.srs).
File>Save
[Save Network Data]
Case Data
SAVE Create Saved Case file (*.sav)
Validly specified power flow
case.
- - -
File>Save
[Save / Show Dynamics Data]
Dynamics Model Data
DYDA
Write simulation model data in the form of
a Dynamics Data File.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
File>Save
[Save Network Data]
Power Flow Raw Data
RAWD Create Power Flow Raw Data file.
Validly specified power flow
case.
- - -
File>Save
[Save Network Data]
IEEE Format Power Flow Data
RWCM
Write working case as IEEE Common
Format for the Exchange of Solved Load
Flow Cases. The 132-character record
tape format is used.
Validly specified power flow
case.
- - -
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
4
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
File>Save
[Save / Show Dynamics Data]
Machine Parametric Source Data
RWDY
Write dynamic model data of plant-related
models:
Inertia and Governor Response
Data File (for activity INLF)
Breaker Duty Data File (for activity
BKDY)
branch impedance data for
branches with relay models (for the
PSSPLT activity RELY)
Validly specified power flow
case. Dynamics data must
be present in dynamics
working memory.
- - -
File>Save
[Save Network Data]
Machine Impedance Data
RWMA Create Machine Impedance Data file.
Validly specified power flow
case. If generator reactive
powers are to be used in
calculations, the case must
be solved to an acceptable
mismatch level.
Machine impedance data
must be correctly specified
for those machines to be
processed.
File>Save
[Save Network Data]
Transaction Data
RWMM
Write transaction data in format suitable
for activity REMM.
Validly specified power flow
case.
- - -
File>Save
[Save Network Data]
Optimal Power Flow Data
RWOP
Create Optimal Power Flow Raw Data
File
Validly specified power flow
case with optimal power
flow data appended to it.
- - -
File>Save
[Save Network Data]
Sequence Data
RWSQ Create Sequence Data File
Validly specified power flow
case with sequence data
appended to it.
- - -
File>Save
[Save / Show Dynamics Data]
Snapshot Data
SNAP
Save a Snapshot of dynamics working
memory in a binary file.
Dynamics working memory
must contain the appropriate
dynamics data.
- - -
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
5
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
File>Save
[Save / Show Dynamics Data]
Dump Output Channels
DMPC
Write channel selections from an existing
simulation setup to a new Snapshot in
Response File format.
Dynamics data must be
present in dynamics working
memory.
- - -
File>Scenarios>New Scenario
[Save As]
Create a new PSS
E study.
File>Scenarios>Open Scenario
[Open]
Open an existing PSS
E study.
File>Scenarios>Save Scenario Save an existing PSS
E study.
File>Scenarios>Close Scenario
Close an existing PSS
E study without
saving changes.
File>Scenarios>Edit Scenario
[PSS
E Scenario Editor]
Edit an existing PSS
E study.
- - -
File>Compare
Case Totals
CMPR
Compare selected totals of power flow
data and solution results contained in the
working case and a designated Saved
Case.
Validly specified power flow
case. Both cases solved to
an acceptable mismatch
level if comparing losses,
mismatches, or interchange.
Saved Case file (*.sav)
- - -
File>Compare
Powerflow Cases
DIFF
Compare selected power flow data, fault
analysis data, and solution results
contained in the working case and a
designated Saved Case.
Validly specified power flow
case. Both cases solved to
an acceptable mismatch
level if comparing bus volt-
ages, line flows, or line
losses.
Saved Case file (*.sav)
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
6
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
- - -
File>Compare
[Compare]
Tie Lines
DFTI
Compare selected power flow data, fault
analysis data, and solution results of
subsystem tie lines contained in the
working case with a Saved Case.
Validly specified power flow
case. Both cases solved to
an acceptable mismatch
level if comparing line flows
or line losses.
Saved Case file (*.sav)
- - -
File>File information
(SIZE/SHOW/BUSN)
[File Information]
List unused bus numbers in a range
BUSN
List unused bus numbers in a specified
bus number range
Validly specified power flow
case.
- - -
File>File information
(SIZE/SHOW/BUSN)
[File Information]
List Save case and Snapshot files
SHOW List Saved Case and Snapshot files. None
- - -
File>File information
(SIZE/SHOW/BUSN)
[File Information]
List the number of system
components
SIZE List the number of system components. Non-null power flow case.
- - -
File>Case titles, short & long
[Case Titles]
CHTI
Re-enter individual lines of the 16 line
long title.
Non-null power flow case.
- - -
File>Import>Long Title
[Select file containing long case title]
RETI
Accept source data records from a file or
the and place them into the 16 line long
title.
Non-null power flow case.
- - -
File>Import>ECDI File
[Economic dispatch data file]
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
7
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
- - -
File>Import>DRAW file
[Open]
DRAW
Import a one-line diagram of a portion of
the working case from prior version of
PSS
E.
If bus voltages and/or line
flows are to be printed,
validly specified power flow
case solved to an accept-
able mismatch tolerance.
Diagram View
Draw Data file (*.drw)
- - -
File>Import>Image file
[Open]
Diagram View
Bitmap file (*.bmp)
- - -
File>Renumber buses in auxiliary
files (RNFI)
[Renumber Buses in Auxiliary Files]
or
File>Renumber buses in Diagram
(RNFI)
[Bus number translation file]
RNFI
List changes in bus numbers created by
activity BSNM for the auxiliary data input
files used by activities RESQ, GDIF,
DYRE, MCRE, ECDI, INLF, BKDY,
ASCC, GCAP, ACCC, and ANSI.
Validly specified power flow
case.
Bus Number Translation
file (*.trn) containing
records of the form:
old bus # new bus #
- - - File>Exit STOP Close all PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
8
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Diagram>Generate graphical power
flow bus display (GOUT/GEXM)
[Select Bus]
GOUT/G
EXM
Display power flow solution results in
graphical form for one bus at a time.
Validly specified power flow
case solved to an accept-
able mismatch level.
Locate bus (icon only)
[Select Bus]
Locate a specified bus on one-line
diagram.
Validly specified power flow
case solved to an accept-
able mismatch level.
Diagram View
Diagram>Results>Powerflow
results
Display power flow solution results on
one-line diagram.
Validly specified power flow
case solved to an accept-
able mismatch level.
Diagram View
Diagram>Results>Impedance data
Display impedance data from power flow
solution results on one-line diagram
Validly specified power flow
case solved to an accept-
able mismatch level.
Diagram View
Diagram>Results>Graphical differ-
ence data
[Compare Cases on a Diagram]
GDIF
Compare differences in power flow solu-
tion results and power flow boundary
condition data with a Saved Case.
Validly specified power flow
case.
Both cases solved to an
acceptable mismatch level.
Diagram View
Diagram>Results>ASCC Fault anal-
ysis results
[Display Fault Analysis Results]
Display three phase and single line to
ground faults on one-line diagram.
Diagram View
Diagram>Results>IEC Fault Anal-
ysis results
Display IEC fault analysis results on one-
line diagram.
Diagram View
Diagram>Results>Reliability Anal-
ysis results
Display probabilistic reliability results on
one-line diagram.
Diagram View
Diagram>Results>Dynamics Anal-
ysis results
Display IEC fault analysis results on one-
line diagram.
Diagram View
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
9
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Solution>
Parameters
[Solution Parameters]
Power Flow>Solution>Solve
(NSOL/FNSL/FDNS/SOLV/ MSLV)
[Loadflow solutions]
Newton
NSOL
Apply a decoupled Newton-Raphson
power flow iteration to the network
modeled in the working case.
Validly specified power flow
case with voltages that are a
reasonable estimate of a
solution.
Power Flow>Solution>Solve
(NSOL/FNSL/FDNS/SOLV/ MSLV)
[Loadflow solutions]
Newton
FNSL
Apply the Newton-Raphson power flow
iteration to the network modeled in the
working case.
Validly specified power flow
case with voltages that are a
reasonable estimate of a
solution.
Power Flow>Solution>Solve
(NSOL/FNSL/FDNS/SOLV/ MSLV)
[Loadflow solutions]
Newton
FDNS
Apply a fixed slope decoupled Newton-
Raphson power flow iteration to the
network.
Validly specified power flow
case with voltages that are a
reasonable estimate of a
solution.
Power Flow>Solution>Solve
(NSOL/FNSL/FDNS/SOLV/ MSLV)
[Loadflow solutions]
Gauss
SOLV
Apply Gauss-Seidel power flow iteration
to the network.
Validly specified power flow
case with voltages that are a
reasonable estimate of a
solution.
No series capacitors.
Power Flow>Solution>Solve
(NSOL/FNSL/FDNS/SOLV/ MSLV)
[Loadflow solutions]
Gauss
MSLV
Apply modified Gauss-Seidel power flow
iteration to the network modeled in the
working case.
Validly specified power flow
case with voltages that are a
reasonable estimate of a
solution.
The working case may
contain series capacitors
only between Type 1
buses.
Power Flow>Solution>AC contin-
gency solution (ACCC)
[AC Contingency Solution]
ACCC
Calculate and report contingency case
power flow solutions.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Distribution Factor Data
File corresponding to the
network condition.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
1
0
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Solution>Multi-Level
AC contingency solution
[Multi-Level AC Contingency Solution]
Power Flow>Solution>Implement
Generation dispatch
[Implement Generation Dispatch]
Power Flow>Solution>AC correc-
tive actions
[AC Corrective Actions]
Power Flow>Solution>N-R solution
with inertial governor dispatch
(INLF)
[N-R Solution with Inertial / Governor
Redispatch]
INLF
Solve the network contained in the
working case.
Activity INLF may be used either as an
inertial power flow or as a governor
response power flow.
Validly specified power flow
case, solved in the pre-
event condition.
Data changes specified.
No prior power flow solu-
tions in working case.
Inertia and Governor
Response Data File (*.inl)
containing machine data
for all in-service machines.
Power Flow>Solution>Order
network for matrix operations
(ORDR)
[Order Network]
ORDR
Perform the optimal ordering function,
setting up an internal ordering of system
buses to optimize the sparsity of the
Jacobian and triangularized admittance
matrices used in the network solution
activities.
Validly specified power flow
case.
Power Flow>Solution>Factorize
admittance matrix (FACT)
FACT
Decompose the admittance matrix of the
network contained in the working case
into its triangular factors for subsequent
use in activity TYSL and in the network
solution used in dynamic simulations.
Validly specified power flow
case.
Activities CONG and
CONL (normally) executed.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
1
1
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Solution>Solution for
switching studies (TYSL)
[Solution for Switching Studies]
TYSL
Solution intended for the solution of
network conditions at the instant following
the execution of a switching operation or
fault application.
Validly specified power flow
case with voltages corre-
sponding to the preswitching
network condition, and with
impedance data specified
for all machines.
Activities CONG, CONL
(normally), and ORDR
executed.
Switching applied and
activity FACT executed.
Power Flow>Solution>PV
analysis
[PV Analysis]
Power Flow>Solution>PV analysis
using previous results
[PV Parameters]
Power Flow>Solution>Implement
PV transfer
[Implement PV Transfer]
Power Flow>Solution>QV
analysis
[QV Analysis]
Power Flow>Solution>QV analysis
using previous results
[QV Parameters]
Power Flow>Changing>Discon-
nect/Reconnect bus
(DSCN/RECN)
[Disconnect / Reconnect Bus]
DSCN
Perform data changes necessary to elec-
trically disconnect selected buses in the
working case. For each bus specified, the
bus type code is set to four and all
branches connected to the bus are
placed out-of-service.
Validly specified specified
power flow case.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
1
2
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Changing>Discon-
nect/Reconnect bus
(DSCN/RECN)
[Disconnect / Reconnect Bus]
RECN
Perform the data changes necessary to
electrically reconnect selected buses in
the working case.
Validly specified power flow
case.
Power Flow>Changing>Join buses
(JOIN)
[Join Buses]
JOIN
Joins pairs of buses, retaining the identity
of one of the two buses and removing the
other completely from the working case.
Validly specified power flow
case.
Power Flow>Changing>Split buses
(SPLT)
[Split Buses]
SPLT
Split buses, introducing an additional bus
for each split bus.
Validly specified power flow
case.
Power Flow>Changing>Tap line
(LTAP)
[Tap Line]
LTAP
Tap any nontransformer ac branch at a
designated location along the line, intro-
ducing a new bus.
Validly specified power flow
case.
Power Flow>Changing>Move
network elements (MOVE)
[Move Network Elements]
MOVE
Disconnect the to bus ends of selected
branches and reconnect them to different
buses. Move selected loads, switched
shunts, machines and plants.
Validly specified power flow
case.
Power Flow>Changing>Delete
network elements (PURG/EXTR)
[Delete Buses and Outaged Network
Elements]
PURG
Remove outaged equipment from the
working case, packing all tables to
remove gaps in numeric sequence.
Validly specified power flow
case.
Power Flow>Changing>Delete
network elements (PURG/EXTR)
[Delete Buses and Outaged Network
Elements]
Remove Buses from Case
EXTR
Remove buses and their connected
equipment from the working case,
packing all tables to remove gaps in
numeric sequence.
Validly specified power flow
case.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
1
3
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Changing>Scale
generation, load, shunt (SCAL)
[Scale Powerflow Data]
SCAL
Modify total load, generation (positive
generator powers), motor load (negative
generator powers), bus connected capac-
itors, and/or bus connected reactors in a
specified subsystem of the working case.
Validly specified power flow
case. If generation is to be
scaled, and a Type 3 bus is
in the subsystem being
scaled, the working case
must be solved to an
acceptable mismatch level.
Power Flow>Changing>Trans-
former adjustment flags (TFLG)
[Transformer Adjustment Flags]
TFLG
Set the tap adjustment enable flags of all
adjustable transformers connecting spec-
ified buses to either zero (disable) or one
(enable).
Validly specified power flow
case.
Power Flow>Changing>Economic
Dispatch (ECDI)
[Economic Dispatch]
ECDI
Perform a unit commitment and economic
dispatch calculation for machines
residing in the working case.
Validly specified power flow
case.
Economic Dispatch Data
File (*.ecd)
Power Flow>Reports>Area/zone
based reports
[Area / Zone Based Reports]
Inter area/zone flow>Output for Areas
INTA
Summarize area interchange between an
area and every other area. Interchange is
evaluated on the basis of the metering
points designated for each area tie
branch.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports>Area/zone
based reports
[Area / Zone Based Reports]
Inter area/zone flow>Output for Zones
INTZ
Summarize zone interchange between a
zone and every other zone. Interchange
is evaluated on the basis of the metering
points designated for each zone tie
branch.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports> Area/zone
based reports
[Area / Zone Based Reports]
Tie line>Output for Areas
TIES
List a summary of the loadings on all ties
from each interchange area
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
1
4
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Reports> Area/zone
based reports
[Area / Zone Based Reports]
Tie line>Output for Zones
TIEZ
List a summary of the loadings on all ties
from each zone
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports> Area / owner
/ zone totals
[Area / Owner / Zone Totals]
Report on Areas
AREA
Report generation, load, bus shunt, line
shunt, line charging, losses, net inter-
change, desired net interchanges for
areas.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports> Area / owner
/ zone totals
[Area / Owner / Zone Totals]
Report on Owners
OWNR
Report summary of owner totals of gener-
ation, load, bus shunt, line shunt, line
charging, and losses in the working case.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports> Area / owner
/ zone totals
[Area / Owner / Zone Totals]
Report on Zones
ZONE Report zone totals
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports>Bus based
reports
[Bus Based Reports]
Powerflow output>Wide format
output>Output with amps
LAMP
Wide format power flow solution output
activity, including branch current loadings
in amps
Activity LAMP lists the mismatch at a bus
only when it exceeds 0.5 MVA.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports>Bus based
reports
[Bus Based Reports]
Powerflow output>Wide format output
LOUT
Wide format power flow solution output
activity. Activity LOUT lists the mismatch
at a bus only when it exceeds 0.5 MVA.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
1
5
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Reports>Bus based
reports
[Bus Based Reports]
Powerflow output
POUT
Narrow format power flow solution output
activity. List bus mismatch only when it
exceeds 0.5 MVA.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports>Bus based
reports
[Bus Based Reports]
Subsystem summary / totals
SUBS
Summarize conditions of power flow
working case.
Validly specified power flow
case solved to an accept-
able mismatch level.
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Reactive capability
GCAP
Read machine capability curve data and
check var loadings and limits against
Machine Capability Curve Data File.
Machine reactive power limits may be
updated.
Validly specified power flow
case.
Machine Capability Data
File (*.gcp)
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Generator bus
GENS
List generating plant loading data
including power output, reactive power
limits, and scheduled and actual voltage.
The report may be limited to plants at a
reactive power limit, in-service plants, or
all plants.
Validly specified power flow
case. Plant outputs and volt-
ages are valid only if the
working case is solved to an
acceptable mismatch
tolerance.
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Machine terminal
GEOL
Print a summary of in-service machines
including power output, terminal voltage,
and current. The report may be restricted
to overloaded machines.
Validly specified power flow
case. Machine outputs and
voltages are valid only if the
working case is solved to an
acceptable mismatch
tolerance.
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Branches
OLTL
List transmission lines where current
loading is greater than a specified
percentage of the selected rating.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
1
6
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Branches
OLTR
List transformers where MVA loading is
greater than a specified percentage of the
selected rating.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Branches
RAT3
Check current flow in each ac series
branch for which at least one nonzero
rating is specified
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Branches
RATE
Check current flow in each ac series
branch for which a nonzero rating is
specified
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Regulated buses
REGB
List voltage controlled buses and their
controlling equipment: local and remote
generators, switched shunts, trans-
formers, and FACTS devices.
Validly specified power flow
case. Bus voltages are valid
only if the working case is
solved to an acceptable
mismatch tolerance.
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Controlling transformer
TLST
List controlling transformer summary
where ratio or phase shift angle may be
adjusted by the power flow solution
activities
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Power Flow>Reports>Limit
checking reports
[Limit Checking Reports]
Out-of-limit bus voltage
VCHK
List buses where per unit voltage magni-
tude is outside a specified range
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
1
7
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Reports>AC Contin-
gency reports
[AC Contingency Reports]
Power Flow>Reports>Append to
AC Contingency solution output
file
[AC Contingency Reports]
Power Flow>Reports>Multiple AC
Contingency run report
[Multiple AC Contingency Run Report]
Power Flow>Reports>Multi-
terminal DC line solution output
(MTDC)
MTDC
Report network conditions within the dc
network formed by each unblocked multi-
terminal dc line. Results listed include the
dc voltage at each dc bus, flows between
the dc network and the ac converter
station buses, and flows on each dc link
in the network.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Unblocked multiterminal dc
lines must be present in the
working case.
Power Flow>Reports>Export
ACCC, PV/QV results to Excel
[Export PSS
E Data/Result to Excel]
Power Flow>Convert Loads and
Generators
[Convert / Reconstruct Loads and
Generators]
Convert Generators>Use ZSOURCE
CONG
Convert all online machines from their
power flow representation to the Norton
current source model used in dynamic
simulations and switching studies.
Validly specified power flow
case solved to an accept-
able mismatch level.
Machine impedance data
must be correctly specified
for all online machines.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
1
8
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Convert Loads and
Generators
[Convert / Reconstruct Loads and
Generators]
Convert/Reconstruct Loads>Convert
constant MVA loads
CONL
Convert constant MVA loads to a speci-
fied mixture of constant MVA, constant
current, and constant admittance loads. A
different split among the three character-
istics may be specified for the real and
reactive components of load.
Validly specified power flow
case solved to an accept-
able mismatch level.
Power Flow>Convert Loads and
Generators
[Convert / Reconstruct Loads and
Generators]
Convert/Reconstruct Loads
RCNL
Reconstruct power, current, and imped-
ance loads at selected buses and then
convert to a new specified mix of constant
power, current, and impedance
Validly specified power flow
case. If the existing voltage
vector is used in the load
reconstruction, the working
case must be solved to an
acceptable mismatch.
Power Flow>Equivalence
Networks>Net boundary bus
mismatches (BGEN)
[Equivalence Networks]
Net boundary bus mismatches
(BGEN)
BGEN
Model the net inflow at boundary buses
as equivalent generation and/or load. A
bus is assumed to be a boundary bus if
its mismatch exceeds 0.5 MVA.
Validly specified subsystem
of a solved power flow case.
Power Flow>Equivalence
Networks>Build electrical equiva-
lent (EEQV)
[Equivalence Networks]
Build electrical equivalent (EEQV)
EEQV
Build an electrical equivalent of Type 1
buses in the specified subsystem of the
working case.
Validly specified power flow
case solved to an accept-
able mismatch level.
Power Flow>Equivalence
Networks> Equivalence radial / 2-
point buses (EQRD/RDEQ)
[Equivalence Networks]
Equivalence radial / 2-point buses
(EQRD/RDEQ)
EQRD
Build an electrical equivalent of all radial
and, optionally, two-point Type 1 buses,
except those connected to three-winding
transformers.
Validly specified power flow
case solved to an accept-
able mismatch level.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
1
9
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Equivalence
Networks> Equivalence radial / 2-
point buses (EQRD/RDEQ)
[Equivalence Networks]
Equivalence radial / 2-point buses
(EQRD/RDEQ)
RDEQ
Build an electrical equivalent of radial
and, optionally, two-point Type 1 buses,
except those connected to three-winding
transformers. When sequence data is
contained in the working case, the zero
sequence network is also calculated as
an electrical equivalent.
Validly specified power flow
case solved to an accept-
able mismatch level.
Power Flow>Equivalence
Networks>Net generation with
load (NETG/GNET)
[Equivalence Networks]
Net generation with load
(NETG/GNET)
NETG
Net generation with the load at all but
specified generator buses. The type code
of any bus where generation is netted is
changed to one.
Validly specified power flow
case solved to an accept-
able mismatch level.
Power Flow>Equivalence
Networks>Net generation with
load (NETG/GNET)
[Equivalence Networks]
Net generation with load
(NETG/GNET)
GNET
Net the generation with the load at speci-
fied generator buses. The type code of
any bus where generation is netted is
changed to one.
Validly specified power flow
case solved to an accept-
able mismatch level.
Power Flow>Equivalence
Networks>Build three sequence
equivalent (SCEQ)
[Equivalence Networks]
Build three sequence equivalent
(SCEQ)
SCEQ
Build a three sequence equivalent of a
subsystem of the working case under
classical fault analysis assumptions.
Validly specified power flow
case reflecting classical fault
analysis assumptions.
Sequence data included in
the case (activity RESQ).
Power Flow>Linear Network>DC
network solution and report
(DCLF)
[DC Network Solution and Report]
DCLF
Apply the dc analogy network solution
algorithm to the network in the working
case and, optionally, to that network with
the status of a specified branch changed.
Validly specified power flow
case, normally solved to an
acceptable mismatch
tolerance.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
2
0
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Linear Network>Single
contingency ranking (RANK)
[Single Contingency Ranking]
RANK
Estimate the severity of single branch
outage contingencies on the basis of a
linearized network model.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
When ranking contingen-
cies with respect to line
overloading, Subsystem
Description Data File and
Monitored Element Data
File
Power Flow>Linear
Network>Create/modify SUB, MON
and CON configuration files
[Configuration File Builder]
Power Flow>Linear Network>Build
distribution factor data file
(DFAX)
[Build Distribution Factor Data File]
DFAX
Build a Distribution Factor Data File in the
form required by the linear network anal-
ysis activities OTDF, DCCC, TLTG, SPIL,
POLY, IMPC, and LLRF, and by the AC
Contingency Solution.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
For subsystem definition
and monitored element
specification: Subsystem
Description Data File,
Monitored Element Data
File, Contingency Descrip-
tion Data File or manual
entry of data.
Power Flow>Linear Network>DC
contingency checking (DCCC)
[DC Contingency Checking]
DCCC
Estimate contingency case line flows for
single or multiple event contingency
cases on the basis of a linearized network
model.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Distribution Factor Data
File corresponding to the
network condition in the
working case.
Power Flow>Linear Network>DC
corrective actions
[DC Corrective Actions]
Power Flow>Linear Network>Calcu-
late and print distribution factors
(OTDF)
[Select Distribution Factor data file to
calculate factors for]
OTDF
Report distribution factors corresponding
to single event contingency cases for a
set of monitored lines and interfaces.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Distribution Factor Data
File (*.dfx) corresponding
to the network condition.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
2
1
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Linear Network>Trans-
mission interchange limits
calculation (TLTG)
[Transmission Interchange Limits
Calculation]
TLTG
Transmission interchange limits
calculation
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Distribution Factor Data
File corresponding to the
network condition in the
working case
Power Flow>Linear
Network>Sequential participation
interchange limit (SPIL)
[Sequential Participation Interchange
Limit]
SPIL
Estimate the transmission interchange
limits of a specified subsystem on the
basis of a linearized network model. Inter-
change limits are calculated for the base
case and for single or multiple event
contingency cases.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Distribution Factor Data
File corresponding to the
network condition in the
working case.
Subsystem Participation
Data File corresponding to
the subsystem definitions
in the Distribution Factor
Data File.
Power Flow>Linear Network>Inter-
change limits with two opposing
systems (POLY)
[Interchange Limits with Two
Opposing Systems]
POLY
Estimate the transmission interchange
limits of a specified subsystem with two
opposing systems on the basis of a
linearized network model.
Validly specified power flow
case solved to an accept-
able mismatch tolerance.
Distribution Factor Data
File corresponding to the
network condition.
Power Flow>Linear Network>Inter-
change limits calculations (POLY) -
previous results
[Interchange limits with two opposing
systems (POLY) - parameters]
Power Flow>Linear
Network>Midwest MW-mile calcula-
tion (MWMI)
[Midwest MW-miles calculation]
MWMI Supports Midwest ISO planning modules.
Contact Midwest ISO
(http://www.midwes-
tiso.org/home).
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
2
2
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Reliability>Reliability
assessment
[Probabilistic Reliability Assessment]
Power Flow>Reliability>Substation
reliability assessment
[Substation Reliability Assessment]
Power Flow>List Data
[List Data]
Bus names
ALPH
Report buses in the working case in
alphabetical order.
Validly specified power flow
case.
Power Flow>List data
[List Data]
Examine Powerflow / sequence data
EXAM
List power flow data: all components
connected to the bus including all trans-
mission lines, transformers, dc lines, and
FACTS devices originating or terminating
on that bus.
Non-null power flow case.
Power Flow>List Data
[List Data]
Powerflow>All data
LIST
Report power flow data contained in the
working case.
Non-null power flow case.
Power Flow>List Data
[List Data]
OPF
LSTO
Report optimal power flow data contained
in the working case.
Validly specified power flow
case with optimal power
flow data appended to it.
Power Flow>List Data
[List Data]
Outaged equipment
OUTS List outaged equipment. Non-null power flow case.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
2
3
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>List Data
[List Data]
Powerflow>Fixed bus shunts
Powerflow>Switched bus shunts or
Powerflow>Fixed bus shunts
SHNT List bus shunts.
Validly specified power flow
case.
Power Flow>List Data
[List Data]
Examine Powerflow / sequence
data>Sequence data
SQEX
List all sequence data, including trans-
mission lines, transformers, dc lines, and
FACTS devices originating or terminating
on that bus
Non-null power flow case.
Sequence data must be
contained in the working
case (i.e., activity RESQ
must have been executed).
Power Flow>List Data
[List Data]
Sequence data
SQLI List specified category of sequence data
Validly specified power flow
case with sequence data
appended to it.
Power Flow>Check Data>Branch
parameters (BRCH)
[Check Branch Parameters]
BRCH
Perform several checks on the parame-
ters associated with ac branches in the
working case.
Non-null power flow case.
Power Flow>Check Data>Check /
Change controled bus scheduled
voltages (CNTB)
[Check / Change Controlled Bus
Scheduled Voltages]
CNTB
Display local and remote generators,
switched shunts, transformers, and
FACTS devices that control voltage at
buses in a designated subsystem of the
working case during power flow solutions.
Validly specified power flow
case. Bus voltages listed
are valid only if the case is
solved to an acceptable
mismatch level.
Power Flow>Check Data>Check /
Change transformer adjustment
data (TPCH)
[Check / Change Transformer Adjust-
ment Data]
TPCH
Change transformer adjustment data
associated with voltage and flow control-
ling transformers.
Validly specified power flow
case.
Power Flow>Check Data>Buses not
in swing bus tree (TREE)
TREE
List buses not in the tree of a swing bus
by island, along with island load, shunt
and generation totals.
Validly specified power flow
case.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
2
4
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Renumbering Areas /
Owners / Zones
[Renumbering Areas / Owners /
Zones]
Area assignments>Reassign Buses
ARNM Re-assign buses to a specified area
Validly specified specified
power flow case.
Power Flow>Renumbering Areas /
Owners / Zones
[Renumbering Areas / Owners /
Zones]
Area assignments>Reassign
Buses/Loads
LDAR
Change the area numbers of selected
loads in the working case.
Validly specified power flow
case.
Power Flow>Renumbering Areas /
Owners / Zones
[Renumbering Areas / Owners /
Zones]
Reassign
OWNM
Change the ownership assignments of
selected buses, loads, machines,
branches, FACTS devices, and/or VSC
dc lines in the working case.
Validly specified power flow
case.
Power Flow>Renumbering Areas /
Owners / Zones
[Renumbering Areas / Owners /
Zones]
Zone assignments>Reassign
Buses/Loads
LDZO
Change the zone numbers of selected
loads in the working case.
Validly specified power flow
case.
Power Flow>Renumbering Areas /
Owners / Zones
[Renumbering Areas / Owners /
Zones]
Zone assignments>Reassign Buses
ZONM Change zone numbers of buses
Validly specified power flow
case.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
2
5
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Power Flow>Renumber buses>By
Bus Number
[Renumber Buses by Bus Number]
Power Flow>Renumber buses>By
Bus Name
[Renumber Buses by Bus Name]
Power Flow>Renumber buses>By
Packing
[Renumber Buses by Bus Packing]
Power Flow>Renumber buses>By
Subsystem
[Renumber Buses by Subsystem]
BSNM
Change the numbers of selected buses in
the working case. A file recording the bus
number changes may be generated.
Validly specified power flow
case.
Fault>Setup for special fault calcu-
lations (FLAT)
[Setup for Special Fault Calculations]
FLAT
Set the voltages of all buses in the
working case to one per unit at zero
phase angle.
Validly specified power flow
case.
Fault>Setup network for unbal-
anced solution (SEQD)
[Setup Network for Unbalanced
Solution]
SEQD
Build and factorize the three sequence
admittance matrices in preparation for the
unbalanced network solution
activity SCMU and for the branch unbal-
ance activity SPCB.
Setup network for unbalanced solution
may also be performed from the SCMU
and SPCB dialogs.
Validly specified power flow
case, with sequence data
appended, solved to an
acceptable mismatch level
with bus voltages corre-
sponding to prefault network
condition.
Fault>ANSI fault calculation
(ANSI)
[ANSI Fault Current Calculation]
ANSI
Calculate fault currents according to the
ANSI standard C37.5-1979.
Validly specified specified
power flow case with
sequence data appended to
it.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
2
6
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Fault>IEC 60909 fault calculation
(IECS)
[IEC 60909 Fault Calculation]
IECS IEC 60909 fault calculation
IEC Fault Calculation Data
file (*.iec)
Fault Control Data file
(*.fcd)
Fault>Automatic sequence fault
calculation (ASCC)
[Automatic Sequence Fault
Calculation]
ASCC
Calculate and report three phase and
single line to ground faults at all buses in
a specified subsystem.
Validly specified power flow
case with sequence data
appended to it.
Fault>Circuit breaker interrupting
duty (BKDY)
[Circuit Breaker Interrupting Duty]
BKDY
Calculate and report circuit breaker inter-
rupting duty for three phase faults at all
buses in a specified subsystem of the
working case.
Validly specified power flow
case must reflect the pre-
fault network condition.
Generators represented as
current sources (activity
CONG must have been
executed).
Normally, the load charac-
teristics must be modified
with CONL prior to
execution.
Breaker Duty Data File.
Fault>Separate pole circuit breaker
(SPCB)
[Separate Pole Circuit Breaker]
SPCB
Calculate the positive sequence pi-equiv-
alent of a single branch unbalance.
Validly specified power flow
case with sequence data
appended to it. It must be
solved to an acceptable
mismatch level with bus
voltages corresponding to
the preunbalance condition.
The branch to have the
unbalance must be
removed from service.
Fault>Solve and report network
with unbalances (SCMU/SCOP)
[Multiple Simultaneous Unbalances]
SCMU
Solve the network in the presence of
unbalanced conditions and print a
summary report.
Validly specified power flow
case with sequence data
appended to it.
Activity SEQD must be
successfully executed.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
2
7
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Fault>Unbalanced network tabular
output (SCOP)
[Multiple Simultaneous Unbalances]
SCOP
Solve the network in the presence of
unbalanced conditions and print a
summary report.
Validly specified power flow
case.
Activity SCMU must have
successfully solved the
network in the presence of
unbalanced conditions.
OPF>Solve
[OPF Solution]
NOPF
Apply interior point solution to the
nonlinear power flow network.
Validly specified power flow
case with optimal power
flow data appended to it.
OPF>Data
OPF>Data tables
[OPF Data Tables]
OPF>Parameters
[OPF - Change Parameters]
NOPF
Modify any of the optimal power flow
solution option settings currently in effect.
Settings can be saved in an Optimal
Power Flow Options File (pssopf.opt).
Validly specified power flow
case with optimal power
flow data appended to it.
Trans Access>Data
Trans Access>Allocations> Mega-
watt shift factors
[Megawatt Shift Factors]
Trans Access>Allocations> Vector
Absolute MW-mile
Trans Access>Allocations> Vector
Absolute MW-ohm
Trans Access>Allocations> Vector
Sum MW-ohm
ALOC
Generate transmission pricing reports:
Vector Absolute MW-mile allocation
matrix, Vector Absolute MW-mile genera-
tion shift factors, Vector Absolute MW-
ohm allocation matrix, Vector Absolute
MW-ohm generation shift factors, Vector
Sum MW-ohm allocation matrix, branch
mileage summary.
Validly specified power flow
case.
Transaction events must
have been previously intro-
duced into working memory
via activity REMM or the
transaction editor.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
2
8
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Trans Access>Calculators>Impact
on monitored elements
[Impact on Monitored Elements]
IMPC
Report incremental MW flow impact on
monitored elements due to a transaction
event.
Validly specified power flow
case.
Transaction events in
working memory via activity
REMM or the transaction
editor.
Distribution Factor Data
File (*.dfx) corresponding
to the network condition.
Trans Access>Calculators>Line
loading relief by transaction
adjustment
[Line Loading Relief by Transaction
Adjustment]
LLRF
Report line loading relief, including: incre-
mental changes in transaction event
curtailments required to achieve a target
monitored element MW flow adjustment,
distribution factors of monitored element
flow to transaction event magnitude, and
modification of the distribution factor
tolerance.
Validly specified power flow
case.
Transaction events previ-
ously introduced into
working memory via activity
REMM or the transaction
editor.
Distribution Factor Data
File corresponding to the
network condition.
Trans Access>Summa-
ries>Summary of branch mileage
by owner
Dynamics>Simulation>Solution
parameters
[Dynamic Solution Parameters]
Dynamics>Simulation>Simulation
options
[Dynamic Simulation Options]
Dynamics>Simulation>Perform
simulation (STRT/RUN)
STRT
Initialize models for state-space simula-
tion and test initial conditions
Validly specified power flow
case, solved to an accept-
able mismatch level.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
2
9
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Dynamics>Simulation>Perform
simulation (STRT/RUN)
RUN
Advance dynamic simulation through
time, solving the network, calculating time
derivatives, and performing numerical
integration at each time step.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Activity STRT successfully
executed.
Dynamics>Simulation>Perform
exciter simulation (ESTR/ERUN)
[Perform Exciter Simulation Test]
ESTR
Initialize the dynamics models for testing
excitation system response with indi-
vidual units operating in isolation.
Activity ESTR overrides manual selec-
tions of output channel assignments.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Dynamics>Simulation>Perform
exciter response ratio simulation
(ESTR/ERUN)
[Perform Exciter Response Ratio
Simulation Test]
ERUN
Execute simulation of excitation system
response with individual units operating in
isolation.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
ESTR successfully
executed.
Dynamics>Simulation>Perform
extended term simulation
(MSTR/MRUN)
MSTR
Initialize all dynamics models from the
network conditions contained in the
working case in preparation for extended
term simulation calculations (i.e., for
activity MRUN).
Validly specified power flow
case, solved to an accept-
able mismatch level.
Dynamics data must be
present in dynamics working
memory.
All equipment models used
in the system dynamic
model must have been
upgraded for use in the
extended term simulation
mode.
Generators represented as
current sources (activity
CONG must have been
executed).
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
3
0
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Dynamics>Simulation>Perform
extended term simulation
(MSTR/MRUN)
[Perform Extended Term Dynamic
Simulation]
MRUN
Advance the extended term dynamic
simulation through time, solving the
network, calculating time derivatives, and
performing numerical integration at each
time step.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Activity MSTR success-
fully executed.
Dynamics>Simulation>Perform
governor response simulation
(GSTR/GRUN)
[Perform Governor Response
Simulation]
GSTR
Initialize the dynamics models for testing
the governing response of individual units
in isolation. Output channel assignments
are overridden, and the speed deviation
and mechanical power of each machine
with a connected governor model are
placed into output channels.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Dynamics>Simulation>Perform
governor response simulation
(GSTR/GRUN)
[Perform Governor Response
Simulation]
GRUN
Execute a simulation of the governing
response of individual units operating in
isolation.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Activity GSTR successfully
executed.
Dynamics>Channel Setup Wizard
[Channel Setup Wizard]
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
3
1
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Dynamics>Define simulation
output (CHAN)>Bus quantity
[Assign Channels for Bus Quantities]
Dynamics>Define simulation
output (CHAN)>Line quantity
[Assign Channels for Line Quantities]
Dynamics>Define simulation
output (CHAN)>Load quantity
[Assign Channels for Load Quantities]
Dynamics>Define simulation
output (CHAN)>Machine quantity
[Assign Channels for Machine
Quantities]
Dynamics>Define simulation
output (CHAN)>Misc quantity
[Assign Channels for Misc. Quantities]
CHAN
Designate quantities which are to be
monitored during dynamic simulation
calculations
Validly specified power flow
case, solved to an accept-
able mismatch level.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Dynamics>Define simulation
output by subsystem (CHSB)
[Select Channels by Subsystem]
CHSB
Designate quantities which are to be
monitored during dynamic simulation
calculations.
Validly specified power flow
case, solved to an accept-
able mismatch level.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Dynamics>Model maintenance
[Model Maintenance]
DYCH
Perform table maintenance functions for
plant-related dynamics models
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
3
2
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Dynamics>List>Models and data
(DOCU)
[List Dynamics Model Data]
DOCU
Report models referenced in dynamics
setup. The report may be restricted to
those models for which constant data
fails a reasonableness check.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Dynamics>List>Dynamics data
(DLST)
[List Dynamics Data Common]
DLST
Report contents of any or all of the
following:
CON array
VAR array
STATE array
ICON array
Main output channel selections
CRT plot channel selections
Dynamics data must be
present in dynamics working
memory.
Dynamics>List>Model storage
locations
[List Model Storage Locations]
MLST
List plant-related models referenced in
dynamics setup.
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Dynamics>Launch NEVA Eigen-
value analysis
Force Generator Conversion (icon
only)
Update Plot Book (icon only)
Update Dynamic Diagram (icon only)
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
3
3
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Dynamics>Build matrices for
LSYSAN program (ASTR)
[Build Matrices for LSYSAN]
ASTR
Initialize all dynamics models from the
network conditions contained in the
working case and construct the state vari-
able system matrices required by the
Linear Dynamic Analysis program,
LSYSAN.
Validly specified power flow
case, solved to an accept-
able mismatch level.
Dynamics data is located in
dynamics working memory.
Generators represented as
current sources (activity
CONG must have been
executed).
I/O Control>Direct Report output
(OPEN)
[Report Output Destination Selector]
OPEN
Preselect report destination: terminal, file,
or high-speed printing device.
None
I/O Control>Direct Progress output
(PDEV)
[Progress Output Destination
Selector]
PDEV
Assign destination progress report output
to the terminal, a file, or a hard copy
printing device.
None
I/O Control>Direct Prompt output
[Prompt Output Destination Selector]
ODEV
Assign destination of the dialog output of
a Response File or an IPLAN program to
the terminal, a file, or a hard copy printing
device.
None, although in practice,
activity ODEV would be
executed only from a
Response File or an IPLAN
program.
I/O Control>Direct Alert output
[Alert Output Destination Selector]
ODEV
Assign destination of the dialog output of
a Response File or an IPLAN program to
the terminal, a file, or a hard copy printing
device.
None, although in practice,
activity ODEV would be
executed only from a
Response File or an IPLAN
program.
I/O Control>Set path for use with
"&" filenames (PATH)
[Define PATH by selecting any file in
the desired directory]
PATH
Designate a pathname to be used as a
prefix for all filenames to be entered with
an ampersand (&) preceding them.
None
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
3
4
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
I/O Control>Start recording
[Select Program Automation File to
Record]
I/O Control>Stop recording
Record user action for part or all of work
session
None
I/O Control>Run program Automa-
tion file
[Select Program Automation File to
Run]
IPLAN File (*.irf)
EXEC Execute IPLAN Executable Program File
IPLAN Executable
Program File generated by
IPLAN language compiler
program.
I/O Control>Run program Automa-
tion file
[Select Program Automation File to
Run]
Response file (*.idv)
Run Response File
Response File, if a file-
name is specified
I/O Control>Run program Automa-
tion file
[Select Program Automation File to
Run]
PSAS Command file (*.psa)
PSAS
Specify a dynamic simulation run in a
high-level language. Output is a
Response File that is automatically
executed.
None
PSAS Command file
(*.psa)
I/O Control>Run program Automa-
tion file
[Select Program Automation File to
Run]
PSEB Command file (*.pse)
PSEB
Specify a power flow run in a high-level
language. Output is a Response File that
is automatically executed.
None
PSEB Command File
(*.pse)
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
3
5
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
I/O Control>Run program Automa-
tion file
[Select Program Automation File to
Run]
Python file (*.py)
Run Python (*.py) file Python file (*.py)
Misc>Change program settings
(OPTN)
[Program Settings]
OPTN
Modify PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
A
-
3
6
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Line mode only CCON
Modify the constant data values associ-
ated with plant-related dynamic
simulation model references
Validly specified power flow
case.
Dynamics data must be
present in dynamics working
memory.
Generators represented as
current sources (activity
CONG must have been
executed).
Network spreadsheet CHNG Power flow data modification.
Command Line Interface only CLOS
Terminate output to the previous action
initiated by activity OPEN.
None
Command Line Interface only ECHO Copies all terminal input to a file.
Line mode only EDTR
Modify the 2-line case heading and the
16-line long title
Validly specified power flow
case.
Command Line Interface only FIND
Find bus number from bus name or
partial bus name.
Command Line Interface only LOFL
Link to power flow activity selection,
enabling execution of any Command Line
input power flow activity.
PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
S
i
e
m
e
n
s
E
n
e
r
g
y
,
I
n
c
.
,
P
o
w
e
r
T
e
c
h
n
o
l
o
g
i
e
s
I
n
t
e
r
n
a
t
i
o
n
a
l
A
-
3
7
P
S
S
E
3
2
.
0
P
r
o
g
r
a
m
O
p
e
r
a
t
i
o
n
M
a
n
u
a
l
Command Line Interface only RTRN
Return to dynamic simulation activity
selection from power flow activity selec-
tion. Establish connectionsbetween
models and network elements, and
update output channel addresses.
Network spreadsheet SQCH Sequence data modification activity.
Line mode only
Reading
Power
Flow Data
Additions
from the
Terminal
Append data to the working case from the
terminal.
Line mode only TRSQ Sequence data input from terminal.
Command Line Interface only USER Power flow user-written activity.
Table A-1. PSS
E Activities (Cont.)
Icon Navigation, [GUI], Tab Selection
Activity
ID Function
Working Case
Requirement(s) Activity Prerequisite(s)
PSS
E 32.0
Program Operation Manual
A-38 Siemens Energy, Inc., Power Technologies International
Siemens Energy, Inc., Power Technologies International B-1
Appendix B
PSS
E Documentation
PSS
E and its auxiliary programs are documented in a set of manuals. Your installation may not
include all of the documents listed below, depending upon which of the optional program sections
are included in your lease of PSS
E.
PSS
E and interpreting its results. The two part guide can be considered an engi-
neering textbook specifically related to system modeling and techniques within PSS
E for
engineers responsible for planning and operations studies.
The Program Operation Manual and the Program Application Guide discuss the use of PSS
E from
different viewpoints and hence complement each other. The user is encouraged to become familiar
with both of these manuals.
PSS
E GUI Users Guide: describes the use of the power flow functions, Optimal Power Flow
program, and dynamic simulation functions of PSS
E-30.
PSS
E Command Line Interface (CLI) Users Guide: describes the structure and general
operation of PSS
E for those customers who prefer operation using command line input.
PSS
E Model Library: provides data sheets and model descriptions for all dynamic models
supported by PSS
E Application Program Interface (API): describes the interfaces to the various engi-
neering functions of PSS
E. Included are the syntax details for accessing APIs in the batch
command facility introduced at PSS
E-30.
PSS
E 32.0
GUI Users Guide
B-2 Siemens Energy, Inc., Power Technologies International
PSAS Users Ready Reference and PSEB Users Ready Reference: describe the
Command File structures that allow the PSS
E
Response File for immediate execution or for subsequent processing as a standard PSS
E
Response File.
Graphic Report Generator GRPG Users Ready Reference: document summarizing the
commands recognized by activity GRPG.
PSSPLT Program Manual: describes the use of the simulation channel output file processing
program used for plotting dynamics study results.
IPLAN Program Manual: describes the Siemens PTI IPLAN programming language and the
use of the IPLAN compiler. Compiled IPLAN programs may be executed by PSS
E activity
EXEC.
PSS
E.
C.3 SCGR
The graphical fault analysis activity SCGR, which applied a sequence of single faults at buses in
the working case, is no longer supported. You may encounter this activity in a Response file. The
results have been mapped to the active Slider Diagram.
C.4 DRAW
The one-line diagram drawing activity DRAW has been replaced by the Diagram View of the Graph-
ical User Interface (GUI). The PSS
E GUI Users Guide, Section 3.11, Displaying ASCC Fault Analysis Results
Implement Activity DRAW - CLI
ACTIVITY?
>>DRAW
ENTER COORDINATE FILE NAME, BINARY OPTION (-1 TO EXIT):
>>
PSS
E 32.0
DRAW Program Operation Manual
C-2 Siemens Energy, Inc., Power Technologies International
C.4.1 Drawing Coordinate Data File Contents
The selection and position of network elements on each one-line diagram is specified via a user-
supplied Drawing Coordinate Data File. The records in the Drawing Coordinate Data File define the
elements to be drawn, their location on the diagram, and annotation options. A Drawing Coordinate
Data File may be constructed and/or modified manually via the host computers text editor.
The Drawing Coordinate Data File consists of records of the following general form:
record type , option , data values
The record type is a two-character code describing the type and significance of the data contained
on the remainder of the record. The option field (which may be a blank or B) specifies a one- or two-
character code, which designates options to be used in drawing the equipment or graphical element
specified by the record. The occurrence of the single character B in the option field is treated as a
blank option field. The option field should always be preceded and followed by commas. The
remainder of each record specifies positional data and other drawing information.
There are two categories of records: control records and graphical element records. The control
records (types HD, EN, VO, RA, VL, AN, CO, CL, and GR) are used to control the reading of the
file and the specification of diagram options such as character size. The graphical element records
describe the network elements (i.e., the buses, branches, and other equipment), as well as
elements such as text strings, symbols and straight lines, which are to be drawn on the diagram.
Records in the file may appear in any order with the exception of the header record (type HD), which
must be the first line, and the terminator record (type EN), which must be the last line. In addition,
only the GN, BL, and LF summation participation record may be specified between a SU record and
the corresponding EN record of a summation block structure (refer to Summation Block Structure).
In addition, only LI branch records may be specified between TT record and the corresponding EN
record of a three-winding transformer group. (refer to Two-Terminal dc Transmission Line Record -
DC and Multi-Terminal dc Transmission Line Record - MD).
The x- and y-axis coordinate values must not be specified as negative numbers on any data
record.
On any data record on which buses are specified, the bus identifier is taken to be the bus number
when the numbers input option is in effect, and the extended bus name, enclosed in single quotes,
using the names input option (refer to Section 3.3.3 and activity OPTN).
Header Record - HD
The header record, which must be the first record in the Drawing Coordinate Data File, is of the
form:
HD, O, DRAWX, DRAWY, CHRX, XSIZE, 'f', TITLEY
Additional Information
PSS
E 32.0
Program Operation Manual DRAW
where:
DRAWX and DRAWY define the size of the box that is drawn around the one-line diagram. If these
quantities are not entered, activity DRAW calculates the dimensions of the box.
The valid entries in the option field are as follows:
Terminator Record - EN
A terminator record, EN, is required both as the last record of each summation block structure (refer
to Summation Block Structure), as the last record of each three-winding transformer group, and as
the last record of the Drawing Coordinate Data File. If the Drawing Coordinate File is not concluded
with this record, activity DRAW proceeds as if the EN record was encountered.
Voltage Level Record - VO
The voltage level specification record is used to specify three voltage level breakpoints. If voltage
levels are selected during the range checking selection portion of the dialog, the voltage levels
specified on the VO data record are taken as the default base voltage breakpoints.
O Is a valid option (blank, S, N, A, or L); below.
DRAWX Is the length of the horizontal (x-axis) side of the drawing in inches. If DRAWX is
less than 7.5 activity DRAW automatically changes it to 7.5 in.
DRAWY Is the length of the vertical (y-axis) side of the drawing in inches exclusive of the
banner block at the bottom of the drawing.
CHRX Is the character height in inches; default is 0.05 in.
XSIZE Is a scaling factor specified in inches; default is zero. If XSIZE is greater than zero,
activity DRAW does not ask the user if the drawing size is to be changed immedi-
ately preceding the drawing of the diagram. Rather, the drawing size is
automatically scaled by the ratio XSIZE/DRAWX.
f Is a single-character orientation flag enclosed in single quotes. It controls the orien-
tation of text written on lines perpendicular to the title block. If this flag is specified
as R, such text is positioned to be read when viewing the drawing from the right
side (relative to the title block being at the bottom). An L positions such text to be
read from the left side. The flag default is R.
TITLEY Is the length of the vertical (y-axis) side of the banner block at the bottom of the
drawing in inches; default is 0.5 in.; maximum is 2.0 in.
blank Draw a one-line diagram of the portion of the working case as specified in the
Drawing Coordinate Data File.
N No printing on the one-line diagram. This option suppresses all text on the drawing.
This option is useful in the initial debugging of a new Drawing Coordinate Data File.
A Accept the network specified in the Drawing Coordinate Data File. This option is
called the accept mode and is used to draw a diagram of a network not necessarily
part of the working case. If bus numbers are selected in the dialog portion of activity
DRAW, they are printed; if the name option is selected, a dummy name is printed
for each bus. Bus voltages and tap ratios are printed as one per unit. If branch flows
are selected, they are printed as zero; if the impedance option is selected, imped-
ances are printed as zero.
L Same as the A option, but with annotation suppressed.
PSS
E 32.0
DRAW Program Operation Manual
C-4 Siemens Energy, Inc., Power Technologies International
The voltage level specification record is of the form:
VO, O, V1, V2, V3
The option field O is either a blank or F. The F option forces the voltage level annotation option on
the one-line diagram even if this range checking option is not specifically selected in the interactive
dialog of activity DRAW. V1, V2, and V3 are specified in kV in ascending order.
By default, the line used in drawing the bus and its connected branches is generated as follows:
On monochromatic devices, when only two voltage levels are specified, it is suggested that they be
drawn using one and three dots. When any of the three voltage breakpoints is specified as zero, or
is less than or equal to the preceding voltage breakpoint, the corresponding line width or color is not
used to distinguish among buses at different voltage levels. Therefore, if the user wishes to distin-
guish between buses up to 138 kV and those greater than 138 kV, the VO data record could be
entered as VO, ,138,138 or VO, ,138,0.
The default line widths, pen numbers, or colors for designating voltage levels may be overridden by
specifying a CO record (refer to Color Specification Record - CO).
Bus Records - BU and BN
Buses to be included on the one-line diagram are specified in bus data records in the Drawing Coor-
dinate Data File. Bus data records are of the form:
BU, O, IB, X1, Y1, X2, Y2, I1, I2
or:
BN, O, IB, X1, Y1, X2, Y2, I1, I2
where:
On Monochromatic Devices On Pen Plotters On Color CRTs
Base kV < V1 One dot wide Pen # 1 White
V1 < base kV < V2 Two dots wide Pen # 2 Red
V2 < base kV < V3 Three dots wide Pen # 3 Green
V3 < base kV Four dots wide Pen # 4 Blue
O Is a valid option (blank, R, N, V, or S); below.
IB Is the bus identifier (number or name).
X1,Y1 Is the (x,y) coordinate of one end of the bus, specified in inches.
X2,Y2 Is the (x,y) coordinate of the other end of the bus, specified in inches.
I1 Is an integer variable used to control the position of the bus annotation (bus name
and/or number or voltage and/or angle) that is printed at the left end of a horizontal
bus or the top of a vertical bus. I1 is the number of character widths to move the
annotation to the right. A negative value of I1 moves the annotation to the left. I1 is
limited to the integers between -10 and 10 inclusive, and has a default value of zero.
Siemens Energy, Inc., Power Technologies International C-5
PSS
E 32.0
Program Operation Manual DRAW
Bus data record types BU and BN behave identically except in the component checking option of
activity DRAW.
Buses must be either horizontal (Y1 = Y2) or vertical (X1 = X2).
For vertical buses, I1 and I2 values of zero place the respective annotation adjacent to the busbar
on the right side. A value of -1 places the annotation adjacent to the busbar on the left side; values
of -2 through -10 move it additional character widths to the left.
The valid entries in the option field are as follows:
The R option may be used in combination with the N or V option. For example, specifying RN in the
option field causes the voltage annotation to be suppressed and the bus identifier to be written at
the right end of a horizontal bus or the bottom of a vertical bus.
By default, Type 4 buses and their generation, loads, and shunts are drawn with dotted lines and
annotation values other than the bus identifier(s) are either zeros or not displayed. This default
manner of drawing out-of-service equipment may be overridden by specifying a CO record (refer to
Color Specification Record - CO).
The minimum information necessary in a bus data record is:
BU, ,IB, X1, Y1, X2, Y2
Branch Record - LI
The ac transmission lines and transformers to be included on the one-line diagram are specified in
branch data records in the Drawing Coordinate Data File. Branch data records are of the form:
LI, O, IFROM, ITO, ICKT, XF, YF, XT, YT, SDF, SF, SDT, ST
where:
I2 Is an integer variable used to control the position of the bus annotation that is
printed at the right end of a horizontal bus or the bottom of a vertical bus. I2 is the
number of character widths to move the annotation to the right. A negative value of
I2 moves the annotation to the left. I2 is limited to the integers between -10 and 10
inclusive, and has a default value of zero.
blank Print bus voltage and/or angle at the right (if a horizontal bus) or bottom (if a vertical
bus), and the bus identifier (number and/or name) at the opposite end.
R Reverse identifier and voltage fields (identifier at right or bottom, as appropriate).
N Print bus name/number but not voltage or angle.
V Print bus voltage and/or angle but not the bus identifier.
S Suppress all annotation for the bus.
O Is a valid option (blank, F, T, SP, N, A, FA, TA, BX, FX, TX, SX, BN, FN, TN, S, SN,
C, FC, TC, SC, R, RN, X, XA, E, EN, EX, RC, or EC); below.
IFROM Is the from bus identifier.
ITO Is the to bus identifier.
ICKT Is the circuit or multi-section line grouping identifier; default value is '1'.
PSS
E 32.0
DRAW Program Operation Manual
C-6 Siemens Energy, Inc., Power Technologies International
Each branch data record causes a line to be drawn in three line segments: a line from each of the
from and to buses where direction and length are characterized by the parameters SDF and SF at
the from bus and SDT and ST at the to bus, and a line connecting the end points of these two stub
segments. It is recommended that the coordinates be specified such that the length of the line is at
least 0.5 in. to accommodate the line annotation.
A value of zero for SF or ST suppresses the drawing of the stub segment at the corresponding bus'
(x,y) coordinates as specified on the data record; in this case, the corresponding stub direction
code, SDF or SDT, is ignored. This is useful for those situations where it is desirable to have a
branch drawn with more than three line segments. To do this, two or more branch data records are
entered in the Drawing Coordinate Data File for the branch, with the appropriate coordination of the
(x,y) coordinates and use of option field specifications. The following records illustrate an applica-
tion of this approach:
BU, ,10 1.0 0.5 1.0 1.5
BU, ,20 4.5 5.5 5.5 5.5
LI,F ,10 20 1 1. 1. 3. 1. R .125 L 0.
LI,SN,10 20 1 3. 1. 3. 6. U 0. D 0.
LI,T ,10 20 1 3. 6. 5. 5.5 R 0. U .5
ST should also be specified as zero when the R, RN, X, XA, E, EN, EX, RC, or EC option is specified
in the option field (and therefore the to bus is not to be drawn). SF and ST should not be zero if
the corresponding bus is included in the Drawing Coordinate Data File and the corresponding (x,y)
coordinates coincide with coordinates on the busbar. Otherwise, the branch annotation will not be
printed in the proper position.
Branch coordinates should not be specified such that the two stub endpoints coincide or overlap
(i.e., the line connecting the two stubs has zero length or retraces the stub paths).
A pair of tables summarizes the valid entries in the option fields of branch coordinate data records.
Table C-1 applies to branches for which bus coordinate data records for both of its endpoint buses
are included in the Drawing Coordinate Data File. Its columns correspond to the various levels of
line annotation available in activity DRAW:
(1) Print the branch flow at the from bus end (bus IFROM).
(2) Print the branch flow at the to bus end (bus ITO).
(3) Draw a transformer symbol.
(4) Print the tap ratio and, if it is non-zero, the phase shift angle.
XF,YF Is the (x,y) coordinate of the line at the from bus end, specified in inches.
XT,YT Is the (x,y) coordinate of the line at the to bus end, specified in inches.
SDF Is the single character L, R, U, or D (for left, right, up, and down, respectively) indi-
cating the direction of the stub drawn at the from bus.
SF Is the length of the line stub drawn at the from bus. It is specified in inches and may
be entered as zero. The default value is 0.125 in.
SDT Is the single character L, R, U, or D (for left, right, up, and down, respectively) indi-
cating the direction of the stub drawn at the to bus.
ST Is the length of the line stub drawn at the to bus. It is specified in inches and may be
entered as zero. The default value is 0.125 in.
Siemens Energy, Inc., Power Technologies International C-7
PSS
E 32.0
Program Operation Manual DRAW
(5) Print the phase shift angle but not the tap ratio.
(6) Draw a series capacitor symbol.
When one of the series capacitor options C, FC, TC, or SC is specified on a branch coordinate data
record and the branch is either a transformer, a positive reactance branch or being treated as a zero
impedance line, the branch is annotated as if the option blank, F, T, or SN, respectively, had been
specified. For the remaining options listed in the table that include transformer annotation, if the
branch is not a transformer, the transformer annotation columns are ignored and the from and to
buses are annotated as indicated in Table C-1.
Table C-1. Options For Branch Coordinate Data Records
Option
(1) (2) (3) (4) (5) (6)
From Bus
Flow
To Bus
Flow
Transformer
Symbol
Tap Ratio
and Phase
Shift Angle
Phase Shift
Angle
Series
Capacitor
Symbol
blank
F
T
SP
N - -
A
FA
TA
BX
FX
TX
SX
BN
FN
TN
S or SN
C
FC
TC
SC
PSS
E 32.0
DRAW Program Operation Manual
C-8 Siemens Energy, Inc., Power Technologies International
Table C-2 lists those option field values that must be used on branch coordinate data records for
open ended radial lines, where the from bus (bus IFROM) has a bus record included in the Drawing
Coordinate Data File and the to bus (bus ITO) does not. Its columns correspond to the various levels
of line annotation available for such branches:
(1) Print the branch flow at the from bus end (bus IFROM).
(2) Draw a transformer symbol.
(3) Print the tap ratio and, if it is non-zero, the phase shift angle.
(4) Print the phase shift angle but not the tap ratio.
(5) Draw a series capacitor symbol.
The to bus number and/or name is printed at the to bus end of the line in accordance with the bus
annotation option as selected during the dialog of activity DRAW, as specified on the bus annotation
specification record, or as set to default values (refer to Bus Annotation Record).
When one of the series capacitor options RC or EC is specified on a branch coordinate data record
and the branch is either a transformer, a positive reactance branch or being treated as a zero imped-
ance line, the branch is annotated as if the option R or EX, respectively, had been specified. For the
remaining options listed in the table that include transformer annotation, if the branch is not a trans-
former, the transformer annotation columns are ignored and the from bus is annotated as indicated
in Table C-2.
By default, the North American transformer symbol is used where transformer symbols are drawn.
A European transformer symbol may be selected by specifying a transformer annotation specifica-
tion record (refer to Transformer Annotation Record).
By default, out-of-service branches are drawn with dotted lines and no flows are printed. This
default manner of drawing out-of-service equipment may be overridden by specifying a CO record
(refer to Color Specification Record - CO).
In an impedance diagram, the specified option is ignored. The branch impedance is printed at one
end of the line; total line charging and, optionally, a selected line rating are printed at the other end.
For branches with one of the option field values listed in Table C-2, the impedance is printed at the
from bus end and the charging and rating annotation is suppressed.
* If the branch is a transformer, flow is printed on the tapped side; the transformer symbol, tap
ratio, and phase shift angle are not printed. If the branch is not a transformer, flow is printed at
both ends.
Table C-2. Special Options for Open Ended Radial Lines
Option
(1) (2) (3) (4) (5)
From Bus
Flow
Transformer
Symbol
Tap Ratio
and Phase
Shift Angle
Phase Shift
Angle
Series
Capacitor
Symbol
R or RN
X
XA
E or EN
Siemens Energy, Inc., Power Technologies International C-9
PSS
E 32.0
Program Operation Manual DRAW
The minimum information necessary in a branch data record is:
LI, , IFROM, ITO,, XF, YF, XT, YT, SDF,, SDT
Transformer Record - TR
A special two-winding transformer record type is provided to specify transformers when the A or L
option is entered on the header record or the suffix AC is specified in invoking activity DRAW.
Because these options indicate that the network to be drawn is not necessarily in the working case,
the TR record provides the user with the ability to designate that a network branch is a transformer.
When a transformer record is entered, activity DRAW assumes that the tapped side of the
transformer is the from bus (bus IFROM) and the untapped or impedance side is the to bus
(bus ITO). (When executed in non-accept mode (refer to Header Record - HD), DRAW accesses
the working case to determine whether or not a branch is a transformer, as well as determining each
transformers tapped impedance side relationship.)
The format and options of the transformer data record are exactly the same as those of the branch
data record (type LI) described in Branch Record - LI. The TR record behaves as does the LI record
when the diagram is coordinated with the working case.
Three-Winding Transformer Record - TT
Three-winding transformers to be included on the one-line diagram are specified in three-winding
transformer groups in the Coordinate Data File. Each of three-winding transformer groups consists
of:
One three-winding transformer record TT (see below).
Followed by branch records LI (see below).
Followed by one terminator record EN (refer to Terminator Record - EN).
Three-winding transformer records are of the form:
TT, O, IFROM, ITO, ILAST, ICKT, X, Y
where:
EX
RC
EC
O Is a valid option (blank, or S); below.
IFROM Is the Winding 1 bus identifier.
ITO Is the Winding 2 bus identifier.
Table C-2. Special Options for Open Ended Radial Lines
Option
(1) (2) (3) (4) (5)
From Bus
Flow
Transformer
Symbol
Tap Ratio
and Phase
Shift Angle
Phase Shift
Angle
Series
Capacitor
Symbol
PSS
E 32.0
DRAW Program Operation Manual
C-10 Siemens Energy, Inc., Power Technologies International
The valid entries in the option field are as follows:
The three-winding transformer record in the three-winding transformer group are followed by
branch records LI. Refer to Branch Record - LI for the correct form for branch records. There are
two limitations for these records:
IFROM should be 0 to indicated that the branch is a part of three-winding transformer.
The valid options are TN and SN only.
The following records illustrate an example of three-winding transformer group:
TT,' ', 160 152 153 1 5.875 4.000
LI,'TN', 0 153 1 5.875 3.875 5.875 3.250 D 0.125 U 0.125
LI,'TN', 0 152 1 6.000 4.125 6.000 4.750 U 0.125 D 0.125
LI,'TN', 0 160 1 5.750 4.125 4.250 4.250 L 1.500 D 0.125
EN
Two-Terminal dc Transmission Line Record - DC
Two-terminal dc transmission lines to be included on the one-line diagram are specified in dc trans-
mission line data records in the Drawing Coordinate Data File. The dc line data records are of the
form:
DC, O, NDC, X1, Y1, X2, Y2, SDF, SF, SDT, ST
where:
ILAST Is the Winding 3 bus identifier.
ICKT Is the three-winding transformer circuit identifier; default value is '1'.
X,Y Is the (X,Y) coordinate of the reference point of the star point bus, specified in
inches.
blank Print the tap ratio for all windings of the three-winding transformer.
S Suppress all annotation for the three-winding transformer.
O Is a valid option (blank, N, F, FN, T, TN, or S); below.
NDC Is the two-terminal dc line number.
X1,Y1 Is the (x,y) coordinate of the dc line at the rectifier converter station bus, specified in
inches.
X2,Y2 Is the (x,y) coordinate of the dc line at the inverter converter station bus, specified in
inches.
SDF Is the single character L, R, U, or D (for left, right, up, and down, respectively) indi-
cating the direction of the stub drawn at the rectifier bus.
SF Is the length of the line stub drawn at the rectifier bus. It is specified in inches and
may be entered as zero. The default value is 0.125 in.
SDT Is the single character L, R, U, or D (for left, right, up, and down, respectively) indi-
cating the direction of the stub drawn at the inverter bus.
ST Is the length of the line stub drawn at the inverter bus. It is specified in inches and
may be entered as zero. The default value is 0.125 in.
Siemens Energy, Inc., Power Technologies International C-11
PSS
E 32.0
Program Operation Manual DRAW
Each two-terminal dc line data record causes a line to be drawn in three line segments in a similar
manner in which ac branches are drawn. Refer to Branch Record - LI for details on the use of the
data parameters SDF, SF, SDT, and ST.
As with ac branches, it is not permissible to specify a dc lines coordinates and stub lengths such
that the two stub endpoints coincide or overlap.
The valid entries in the option field are as follows:
The power flowing into a dc line is the apparent ac system complex load as n at the converter bus
(i.e., PACR and QACR at the rectifier end, and PACI and QACI at the inverter end).
By default, blocked two-terminal dc lines are drawn with dotted lines and no flows are printed; the
dc symbols are drawn. This default manner of drawing out-of-service equipment may be overridden
by specifying a CO record (refer to Color Specification Record - CO).
For an impedance diagram, the specified option is ignored and the commutating reactances, in
ohms, are printed at each end of the line. The dc line resistance, in ohms, is printed above the
commutating reactance at the rectifier end of the line, and the minimum alpha and gamma angles
are printed at the corresponding dc symbols.
If the A or L option is specified on the header record, or AC is specified in invoking activity DRAW
using line mode, the working case is ignored and the dc line coordinates are not checked against
the coordinates of the appropriate buses because the buses involved are normally determined from
the working case and not from the dc data record.
The minimum information necessary in a dc line data record is:
DC, , NDC, X1, Y1, X2, Y2, SDF,, SDT
Multi-Terminal dc Transmission Line Record - MD
Multi-terminal dc transmission line converters to be included on the one-line diagram are specified
in multi-terminal dc line records in the Drawing Coordinate Data File. Multi-terminal dc data records
are of the form:
MD, NDC, IB, X1, Y1, X2, Y2
where:
blank Print flow at each end. The converter tap settings and dc symbols are drawn.
N No printing of dc symbols or converter tap settings. Flows are printed at both ends.
F Print flow at rectifier bus end only. The converter tap setting and dc symbol are
drawn.
FN No printing of dc symbol or converter tap setting. Print flow at rectifier bus end only.
T Print flow at inverter bus end only. The converter tap setting and dc symbol are
drawn.
TN No printing of dc symbol or converter tap setting. Print flow at inverter bus end only.
S Suppress all printing on the dc line.
NDC Is the multi-terminal dc line number.
PSS
E 32.0
DRAW Program Operation Manual
C-12 Siemens Energy, Inc., Power Technologies International
The length of the line specified by the coordinates (X1,Y1) and (X2,Y2) should be at least 1 in. The
line specified by the coordinates must be either horizontal (Y1 = Y2) or vertical (X1 = X2).
At the end of the line connected to the bus, the power flowing into the dc line (i.e., the apparent ac
system complex load as n at the converter bus) is printed. The dc symbol is drawn at the midpoint
of the line, and the converter alpha or gamma angle, as appropriate, and tap position are printed at
the end of the line segment.
By default, at each converter of a blocked multi-terminal dc line for which an MD record is specified,
the multi-terminal dc line is drawn with a dotted line and the flow, angle and tap are shown as zero;
the dc symbol is drawn. This default manner of drawing out-of-service equipment may be over-
ridden by specifying a CO record (refer to Color Specification Record - CO).
Multi-terminal dc line converters are annotated identically in impedance and flow diagrams.
While the dc link connections within multi-terminal dc lines are not handled automatically by activity
DRAW, the ends of these line segments may be appropriately connected by using straight line
records (refer to Straight Line Record - SL).
Load Records - LO, LP, LC, and LY
Bus loads to be included on the one-line diagram are specified in load data records in the Drawing
Coordinate Data File. Load data records are of the form:
La, O, IB, X1, Y1, X2, Y2
where:
The length of the line specified by the coordinates (X1,Y1) and (X2,Y2) should be at least 0.25 in.;
a longer length may be needed depending on the magnitude of the load and the character size
specified on the HD record. The line specified by the coordinates must be either horizontal
(Y1 = Y2) or vertical (X1 = X2).
The LP, LC, and LY data records are used to display the constant power, constant current, and
constant admittance load characteristics, respectively, of the load at bus IB for which the identifier
is contained in the option field of the data record. If the option field contains a blank, the sum of the
appropriate load characteristic for all in-service loads at bus IB is printed.
IB Is the bus identifier. Bus IB must be a converter station bus of multi-terminal dc line
NDC.
X1,Y1 Is the (x,y) coordinate of the line on the busbar, specified in inches.
X2,Y2 Is the (x,y) coordinate of the end point of the straight line segment, specified in
inches.
La Is either LO, LP, LC, or LY and defines the load characteristic; below.
O Is blank or the load identifier; below.
IB Is the bus identifier.
X1,Y1 Is the (x,y) coordinate of the line on the busbar, specified in inches.
X2,Y2 Is the (x,y) coordinate of the end point of the straight line segment, specified in
inches. This is the end at which the arrow head is drawn.
Siemens Energy, Inc., Power Technologies International C-13
PSS
E 32.0
Program Operation Manual DRAW
The LO data record is used to display the sum of the three load characteristics for the load at bus
IB for which the identifier is contained in the option field. If the option field contains a blank, the total
in-service load at bus IB is printed. The specified load identifier is printed inside of the load symbol.
By default, out-of-service loads are drawn with dotted lines and annotation values are shown as
zero. This default manner of drawing out-of-service equipment may be overridden by specifying a
CO record (refer to Color Specification Record - CO).
In an impedance diagram, nominal loads are printed (i.e., at one pu voltage).
Shunt Record - SH
Bus shunts to be included on the one-line diagram are specified in shunt data records in the
Drawing Coordinate Data File. Shunt data records are of the form:
SH, O, IB, X1, Y1, X2, Y2
where:
The length of the line specified by the coordinates (X1,Y1) and (X2,Y2) should be at least 0.25 in.;
a longer length may be needed depending on the magnitude of the shunt and the character size
specified on the HD record. The line specified by the coordinates must be either horizontal
(Y1 = Y2) or vertical (X1 = X2).
The valid entries in the option field are as follows:
The R option may be used in combination with the L or S options (i.e., RL or RS).
Constant admittance load is not included as bus shunt; these are drawn as loads (refer to Load
Records - LO, LP, LC, and LY).
By default, shunts at Type 4 buses are drawn with dotted lines and annotation values are shown as
zero. This default manner of drawing out-of-service equipment may be overridden by specifying a
CO record (refer to Color Specification Record - CO).
On a flow diagram, shunt MW and Mvar are printed; on an impedance diagram, nominal shunt
values are printed. The sign of the reactive component of shunt admittance determines whether a
capacitor or reactor symbol is drawn. When this quantity is zero, a reactor symbol is drawn if the R
option is specified; otherwise, a capacitor symbol is drawn.
O Is a valid option (blank, L, S or R); below.
IB Is the bus identifier.
X1,Y1 Is the (x,y) coordinate of the line on the busbar, specified in inches.
X2,Y2 Is the (x,y) coordinate of the end point of the straight line segment, specified in
inches. This is the end at which the capacitor or reactor symbol is drawn.
blank The shunt printed is the sum of the fixed shunt and switched shunt devices.
L The shunt printed is the fixed shunt (refer to Bus Data).
S The shunt printed is the switched shunt (refer to Switched Shunt Data).
R When the reactive component of the shunt is zero or when in accept mode, a
reactor symbol is drawn; under these conditions when the R option is not specified,
a capacitor symbol is drawn.
PSS
E 32.0
DRAW Program Operation Manual
C-14 Siemens Energy, Inc., Power Technologies International
Generator Record - GE
Generators to be included on the one-line diagram are specified in generator data records in the
Drawing Coordinate Data File. Generator data records are of the form:
GE, O, IB, X1, Y1, X2, Y2
where:
The length of the line specified by the coordinates (X1,Y1) and (X2,Y2) should be at least 0.25 in.;
a longer length may be needed depending on the magnitude of the generation and the character
size specified on the HD record. The line specified by the coordinates must be either horizontal
(Y1 = Y2) or vertical (X1 = X2).
By default, out-of-service plants and machines are drawn with dotted lines and annotation values
are shown as zero. This default manner of drawing out-of-service equipment may be overridden by
specifying a CO record (refer to Color Specification Record - CO).
On a flow diagram, generator MW and Mvar are printed; on an impedance diagram, the generator
reactive power limits replace the Mvar output on the drawing.
When the option field is left blank, plant totals are printed. Otherwise, the option field specifies the
identifier of a machine in a multimachine plant for which the data is to be printed. The machine iden-
tifier is printed inside the generator circular symbol. Thus, if several machines at a bus are to be
drawn, one generator data record in the Drawing Coordinate Data File is required for each one.
To specify a machine with a machine identifier of B, the option field must be specified as BB (refer
to comments in Drawing Coordinate Data File Contents above).
Facts Device Record - FD
FACTS devices to be included on the one-line diagram are specified in FACTS device data records
in the Drawing Coordinate Data File. FACTS device data records are of the form:
FD, O, FACTID, X1, Y1, X2, Y2, STBDIR, STBLTH, DEVTYP
where:
O Is blank or the machine identifier; below.
IB Is the bus identifier.
X1,Y1 Is the (x,y) coordinate of the line on the busbar, specified in inches.
X2,Y2 Is the (x,y) coordinate of the end point of the straight line segment, specified in
inches. This is the end at which the circle is drawn.
O Is a valid option (blank, B, N, S, T); below.
FACTID Is the facts device identifier.
X1,Y1 Is the (x,y) coordinate of the line connection at the sending bus, specified in inches.
For UPFC and SSSC devices, this is the coordinate point associated with the series
element line connection that connects the send and terminal buses. For a
STATCON device, this is the coordinate point associated with the shunt device
connection line.
Siemens Energy, Inc., Power Technologies International C-15
PSS
E 32.0
Program Operation Manual DRAW
The valid entries in the option field are as follows:
For UPFC and SSSC FACTS devices, a circle with an arrow depicting power flow direction is drawn
midway on the line connecting the sending and terminal buses. For UPFC FACTS devices, two lines
are drawn connecting the shunt rectangle and the circle. By default, out-of-service FACTS devices
are drawn with dotted lines, and annotation values are blanked.
Straight Line Record - SL
Arbitrarily located straight lines to be included on the one-line diagram are specified in straight line
data records in the Drawing Coordinate Data File. Straight line records are of the form:
SL, O, X1, Y1, X2, Y2
where:
X2,Y2 Is the (x,y) coordinate endpoint of the line connection, specified in inches. For
UPFC and SSSC devices, this coordinate is located on the terminal bus and termi-
nates the line connection between the send and terminal buses. For STATCON
devices, this is the coordinate point associated with the end of the shunt device stub
line. The line specified by the coordinates must be either horizontal (Y1 = Y2) or
vertical (X1 = X2).
STBDIR Is the single-character L, R, U, or D (for left, right, up, and down, respectively) indi-
cating the direction of the shunt stub drawing relative to the send bus (X1,Y1)
coordinate. For SSSC and STATCON FACTS devices, this field may be blank and
is ignored.
For horizontal send bus bars, only L,R values are allowed with L assigned as
the default. For vertical send bus bars, only U,D values are allowed with D
assigned as the default. STBDIR is ignored for all SSSC and STATCON devices.
STBLTH Is the length of the shunt stub offset relative to the (X1,Y1) coordinate of the send
bus. It is specified in inches with 0.125 in. as default. For SSSC and STATCON
FACTS devices, this field may be blank and is ignored.
For UPFC FACTS devices, the shunt stub line is drawn starting at the point defined
by the shunt stub drawing direction and the shunt stub offset length relative to
(X1,Y1). The shunt stub line is drawn with a length of 0.2 in. The shunt FACTS
device rectangle and ground symbols are drawn at the end of the shunt stub line.
DEVTYP Is the FACTS device type (1-UPFC device, 2-SSSC device, 3-STATCON). The
default type is 1. This field may be blank and is ignored when DRAW is executed in
non-accept mode.
blank, B Display flows on series, bridge, and shunt elements.
N Do not display any flows.
S Display flows only at send bus and shunt element end.
T Display flow only at terminal bus.
O Is a valid option (blank, D, H, n, Dn, or Hn); below.
X1,Y1 Is the (x,y) coordinate of one end of the line, specified in inches.
X2,Y2 Is the (x,y) coordinate of the other end of the line segment, specified in inches.
PSS
E 32.0
DRAW Program Operation Manual
C-16 Siemens Energy, Inc., Power Technologies International
Straight lines may be used, for example, to designate area boundaries, or to show the dc link
connections within multi-terminal dc lines.
The valid entries in the option field are as follows:
By combining any of these options with the numbers one through eight (e.g., 2, D5), a line width,
pen number or color is designated for the drawing of the straight line. It is the users responsibility
to ensure that the designated number is appropriate for the graphics output device being used (e.g.,
6 would be invalid for a pen plotter with only four pens). If the numeric option is invalid, a device
dependent default is used.
Text Specification Record - TX
The text specification record allows strings of characters to be written anywhere on the one-line
diagram. Text specification records are of the form:
TX, O, X, Y, TSIZ, TANG, '...text...'
where:
The option field is used to designate a line width, pen number or color for the drawing of the text. It
is the users responsibility to ensure that the designated number is appropriate for the graphics
output device being used (e.g., 6 would be invalid for a pen plotter with only four pens). If the
numeric option is invalid, a device dependent default is used.
Clip Specification Record - CL
The clip specification record defines the size of the clipping window where the user may zoom in or
out on a selected portion of the diagram. The clip specification record is of the form:
CL, , X, Y
where:
The clipping window defines the portion of the diagram, which is drawn in pages when zooming is
enabled.
blank Draw solid straight line segment.
D Draw dotted straight line segment.
H Draw dashed straight line segment.
O Is a valid option (blank, or 1 through 8; blank and 1 are equivalent); below.
X,Y Is the (x,y) coordinate of the first character of the text string, specified in inches.
TSIZ Is the character height specified in inches. TSIZ must be between 0.05 and 1.5 in.
TANG Is the angle of rotation of the character string, specified in degrees between 0 and
360; 0 degrees is the angle at which the title lines are written on the diagram.
text Is the character string. It must be enclosed in single quotes and is limited to 40
characters.
X,Y Define the size of the window along the x- and y-axes, respectively, and are speci-
fied in inches.
Siemens Energy, Inc., Power Technologies International C-17
PSS
E 32.0
Program Operation Manual DRAW
There are no options recognized on the clip specification data record.
Grid Record - GR
The grid record enables the overlaying of a coordinate grid upon the one-line diagram. The grid
record is of the form:
GR, , GRDRES
where GRDRES is the grid resolution specified in inches. Horizontal and vertical lines composing
the grid are spaced GRDRES inches apart. GRDRES is restricted to the range 0.1 through 1.0 in.
and has a default value of 0.125 in. If it is less than 0.1 in., lines are drawn 1/10 of an inch apart; if
it is greater than 1.0, lines are drawn 1 in. apart.
There are no options recognized on the grid data record.
Color Specification Record - CO
The color specification record allows the user to override the default line width, pen number, or color
conventions for denoting voltage levels, heavily loaded and out-of-service branches, and buses
where voltages are out-of-limits. The color specification record is of the form:
CO, , EQOUT, LNOVR, BSUND, BSOVR, V1, V2, V3, V4
where:
On color CRTs, the use of color to designate the conditions specified by EQOUT, LNOVR, BSUND,
and/or BSOVR takes precedence over the voltage level color if that option is also enabled.
It is the users responsibility to ensure that the numbers designated on the CO record are appro-
priate for the graphics output device being used (e.g., 6 would be invalid for a pen plotter with only
four pens). If any value is invalid, a device dependent default is used.
EQOUT Defines the line width, pen number, or color to be used in drawing out-of-service
equipment. EQOUT must be between zero and eight. If the default of zero is speci-
fied for EQOUT, out-of-service equipment is drawn with dotted lines.
LNOVR Defines the line width, pen number, or color to be used in drawing heavily loaded
lines. LNOVR must be between zero and eight. If the default of zero is specified for
LNOVR, overloaded lines are drawn with dashed lines.
BSUND Defines the line width, pen number, or color to be used in drawing buses where
voltage magnitudes are below a specified threshold. BSUND must be between zero
and eight. If the default of zero is specified for BSUND, undervoltage buses are
drawn with a dashed line on the bottom portion of the busbar.
BSOVR Defines the line width, pen number, or color to be used in drawing buses where
voltage magnitudes are above a specified threshold. BSOVR must be between zero
and eight. If the default of zero is specified for BSOVR, overvoltage buses are
drawn with a dotted line on the top portion of the busbar.
V1, V2, V3,
V4
Define the line width, pen number, or color to be used in denoting voltage levels
(refer to Voltage Level Record - VO). The values specified must be between zero
and eight. If not entered, V1 through V4 default to one through four, respectively.
PSS
E 32.0
DRAW Program Operation Manual
C-18 Siemens Energy, Inc., Power Technologies International
Symbol Record - SY
The symbol record allows symbols from the graphics character set to be drawn anywhere on the
one-line diagram. The symbol record is of the form:
SY, O, ISYM, X, Y, SIZE, ANGLE
where:
The option field is used to designate a line width, pen number, or color for the drawing of the symbol.
It is the users responsibility to ensure that the designated number is appropriate for the graphics
output device being used (e.g., 6 would be invalid for a pen plotter with only four pens). If the
numeric option is invalid, a device dependent default is used.
O Is a valid option (blank, or 1 through 8; blank and 1 are equivalent); below.
ISYM Is the symbol number assigned to the symbol to be drawn. Figure C-1 shows the
symbols contained in the graphics character set. ISYM must be between 1 and 155.
X,Y Is the (x,y) coordinate of the reference point of the symbol, specified in inches. The
intersections of the dotted lines in Figure C-1 show the reference points for the
symbols contained in the graphics character set.
SIZE Is the symbol height specified in inches. SIZE must be between 0.05 and 1.5 in.
ANGLE Is the angle of rotation of the symbol, specified in degrees between 0 and 360; 0
degrees is the angle at which the title lines are written on the diagram. The symbols
in Figure C-1 are drawn at zero degrees.
Siemens Energy, Inc., Power Technologies International C-19
PSS
E 32.0
Program Operation Manual DRAW
Figure C-1. Graphics Character Set
PSS
E 32.0
DRAW Program Operation Manual
C-20 Siemens Energy, Inc., Power Technologies International
Rating Specification Record - RA
The branch rating specification record specifies the rating set and percentage loading threshold to
be used in identifying heavily loaded branches on the one-line diagram. Using this option, all
branches to be drawn that have a non-zero value for the selected rating and where current loading
at either end exceeds the specified percentage of the selected rating are flagged by being drawn
with dashed lines. This default manner of drawing heavily loaded lines may be overridden by spec-
ifying a CO record (refer to Color Specification Record - CO).
If either the line rating range checking option or one of the % RATING line flow annotation options
is selected, the rating set and percentage loading threshold specified on the RA record are taken
as the default values.
The rating specification record is of the form:
RA, O, RAT, PCTRAT
where:
The valid entries in the option field are as follows:
Voltage Limits Specification Record - VL
The bus voltage limits specification record specifies the voltage range to be used in identifying
buses with high or low voltages. Using this option, buses with a voltage below the specified
minimum have the lower portion of their bus box drawn with a dotted line. Buses with a voltage
above the specified maximum have the upper portion of their bus box drawn with a dashed line.
This default manner of drawing buses outside of voltage limits may be overridden by specifying a
CO record (refer to Color Specification Record - CO).
If the voltage limits range checking option is selected during the interactive dialog of activity DRAW,
the voltage limits specified on the VL record are taken as the default limits.
The voltage limits specification record is of the form:
VL, O, VMIN, VMAX
where:
O Is a valid option (blank or F; below).
RAT Is one of the strings RATE, RATEA, RATEB, or RATEC. If RATE is specified, the
rating set established as the default rating set program option is selected (refer to
Section 3.3.3 and activity OPTN). Otherwise, the designated rating set is selected.
PCTRAT Is the percentage loading threshold. The default value is 100%.
blank The line rating range checking option is initially disabled and may be activated in the
interactive dialog of activity DRAW.
F Force the line rating range checking option on the one-line diagram even if it is not
specifically selected in the interactive dialog.
O Is a valid option (blank or F; below).
VMIN Is the low-voltage threshold limit specified in per unit.
Siemens Energy, Inc., Power Technologies International C-21
PSS
E 32.0
Program Operation Manual DRAW
The valid entries in the option field are as follows:
Diagram Annotation Record - AN
The one-line diagram annotation specification records specify branch, bus, and equipment annota-
tion options. Selections specified on AN records are taken as the default selections during the
interactive dialog of activity DRAW.
As shown in the following paragraphs, the option field on the AN record defines the diagram anno-
tation option being specified.
Line Annotation Record
The line annotation specification record is of the form:
AN, LI, ANNOPT, SGNOPT
The valid entries in the ANNOPT field are as follows:
The valid entries in the SGNOPT field are as follows:
In calculating percentage loading, current expressed as MVA (refer to Non-Transformer Branch
Data and activity RATE) is calculated at the appropriate end(s) of the branch and is used in calcu-
lating the loading percentage. The rating set used is as defined on any RA record (refer to Rating
Specification Record - RA), as defined by the rating set program option setting (refer to activity
OPTN), or as overridden in the program dialog.
VMAX Is the high-voltage threshold limit specified in per unit.
blank The voltage limits range checking option is initially disabled and may be activated in
the interactive dialog of activity DRAW.
F Force the voltage limits range checking option on the one-line diagram even if it is
not specifically selected in the interactive dialog.
MW-MVAR Display MW and Mvar line flows; this is the default line annotation option.
MVA Display MVA line flows.
MVA-PCRATE Display MVA line flows and current loading as a percentage of rating.
MW-PCRATE Display MW line flows and current loading as a percentage of rating.
AMP-PCRATE Display current loadings in amps and as a percentage of rating.
AMP-PUCUR Display current loadings in amps and per unit.
Z Display line impedances and charging.
Z-RATE Display line impedances, charging, and the selected rating.
NONE Suppress branch annotation; transformer and dc symbols that would be drawn
using the other branch annotation options are still drawn.
SIGN Flow direction is indicated using the standard PSS
E 32.0
DRAW Program Operation Manual
C-22 Siemens Energy, Inc., Power Technologies International
When current in amps is selected, the current in per unit is printed for any branch for which the
required bus base voltage has not been entered (i.e., if it is zero).
On an impedance diagram, unless NONE is specified for ANNOPT, the ANNOPT entry is ignored
and branches are annotated as described in Branch Record - LI and Two-Terminal dc Transmission
Line Record - DC.
Bus Annotation Record
The bus annotation specification record is of the form:
AN, BU, NAMOPT, VLTOPT
The valid entries in the NAMOPT field are as follows:
The selection of bus names, which are up to twelve characters, may require adjustment of coordi-
nates in the Drawing Coordinate Data File if the diagram was set up using the numbers output
option (bus numbers are at most six digits).
The valid entries in the VLTOPT field are as follows:
On a flow diagram, when voltage in kV is selected, the voltage in per unit is printed for any bus
where base voltage has not been entered (i.e., if it is zero).
On a flow diagram, voltage and/or angle are printed as zero for any bus where type code is four
(i.e., for disconnected buses).
On an impedance diagram, for any VLTOPT specification except NONE, bus base voltages in kV
are printed.
NAME Display the twelve-character bus name. If a bus has a blank name, no identifier is
printed for the bus. This is the default bus identification option when the names
output option is in effect.
NUMBER Display the bus number. This is the default bus identification option when the
numbers output option is in effect.
BOTH Display the bus name above the bus number.
NONE Suppress bus identification annotation.
VPU Display bus voltage magnitude in per unit. This is the default bus voltage annota-
tion option.
VPU-ANGLE Display bus voltage magnitude in per unit and phase angle in degrees.
VPU-KV Display bus voltage magnitude in per unit and kV.
KV Display bus voltage magnitude in kV.
KV-ANGLE Display bus voltage magnitude in kV and phase angle in degrees.
ANGLE Display bus voltage phase angle in degrees.
NONE Suppress bus voltage annotation.
Siemens Energy, Inc., Power Technologies International C-23
PSS
E 32.0
Program Operation Manual DRAW
Equipment Annotation Record
The equipment annotation specification record specifies the annotation option for load, generator,
shunt, and multi-terminal dc line elements and is of the form:
AN, EQ, ANNOPT
The valid entries in the ANNOPT field are as follows:
On an impedance diagram, unless NONE is specified for ANNOPT, the ANNOPT entry is ignored
and equipment is annotated as described in Multi-Terminal dc Transmission Line Record - MD,
Load Records - LO, LP, LC, and LY, Shunt Record - SH, and Generator Record - GE.
Activity Annotation Record
Activity annotation specification records define the branch annotation conventions to be used when
the Drawing Coordinate Data File is specified to activity GDIF. These records are of the following
form:
AN, AC, ACTNAM, ACTOPT
The valid entries in the ACTNAM field are GDIF and SCGR. An activity annotation record is ignored
unless its ACTNAM field matches the name of the activity being executed.
The valid entries in the ACTOPT field are as follows:
Transformer Annotation Record
The transformer annotation specification record is of the form:
AN, TR, ANNOPT
The valid entries in the ANNOPT field are as follows:
MW-MVAR Display MW and Mvar values. This is the default equipment annotation option.
MVA Display MVA values for load, generator and shunt elements. Multi-terminal dc
lines have MW and Mvar displayed.
NONE Suppress equipment annotation.
IGNORE Ignore the option field on each branch record and display data at both ends of the
branch. Branches where LI or TR coordinate data records contain one of the radial
line option field entries (see Table C-2) are annotated at the from bus end only. The
use of multiple branch records to define the branch path is detected using this
option and such branches are annotated on their first and last line segments. This is
the default convention used by activity SCGR.
HONOR Annotate each branch according to the option field on its branch record. This is the
default convention used by activity GDIF.
NA-SYM Use the North American transformer symbol (symbol number 140 of Figure C-1 for
two-winding transformer and symbol number 155 of Figure C-1 for three-winding
transformer) and display only primary winding for two-winding transformer; this is
the default transformer annotation option.
PSS
E 32.0
DRAW Program Operation Manual
C-24 Siemens Energy, Inc., Power Technologies International
Summation Block Structure
The summation block structure provides for:
Initializing a summing variable; usually, the initial value of the summing variable is zero,
but a non-zero value may be specified.
Specifying individual ac branches, generator buses, and/or load buses where active
power components of line flow, generation, and load, respectively, are added to or sub-
tracted from the summing variable.
Specifying a character string to be printed in front of the calculated value of the sum-
ming variable anywhere on the one-line diagram.
Each summation block structure consists of:
One summation record, SUM or SU (see below).
Optionally followed by one or more summation participation records GN, BL, and LF
(see below).
Followed by one terminator record, EN (refer to Terminator Record - EN).
Summation records are of the form:
SU, O, '...text...', X, Y, TSIZ, TANG, CNST
where:
The option field is used to designate a line width, pen number, or color for the drawing of the text.
It is the user's responsibility to ensure that the designated number is appropriate for the graphics
output device being used (e.g., 6 would be invalid for a pen plotter with only four pens). If the
numeric option is invalid, a device dependent default is used.
EU-SYM Use the European transformer symbol (symbol number 151 of Figure C-1 for two-
winding transformer and symbol number 154 of Figure C-1 for three-winding trans-
former) and display only primary winding for two-winding transformer.
NA-WN2 Use the North American transformer symbol (symbol number 140 of Figure C-1 for
two-winding transformer and symbol number 155 of Figure C-1 for three-winding
transformer) and display both windings of two-winding transformer.
EU-WN2 Use the European transformer symbol (symbol number 151 of Figure C-1 for two-
winding transformer and symbol number 154 of Figure C-1 for three-winding trans-
former) and display both windings of two-winding transformer.
O Is a valid option (blank, or 1 through 8; blank and 1 are equivalent); below.
text Is the character string to be displayed in front of the summing variable's value. It
must be enclosed in single quotes and is limited to 40 characters.
X,Y Is the (x,y) coordinate of the first character of the text string, specified in inches.
TSIZ Is the character height specified in inches. TSIZ must be between 0.05 and 1.5 in.
TANG Is the angle of rotation of the character string, specified in degrees between 0 and
360; 0 degrees is the angle at which the title lines are written on the diagram.
CNST Is the initial value to be assigned to the summing variable. The default value is zero.
Siemens Energy, Inc., Power Technologies International C-25
PSS
E 32.0
Program Operation Manual BMAT
The summation record in the summation block structure may be followed by summation participa-
tion records. These define the generator buses, load buses, and ac branches where active power
components are to be included in the summation. The summation participation records may be
entered in any order and are of the following forms:
GN, O, IB (for bus generation)
BL, O, IB (for bus load)
LF, O, IFR, ITO, ID, DIR (for ac branch flow)
where:
If an element specified on a summation participation record is out-of-service, it does not contribute
to the summation.
The following records illustrate an example of the summation block structure:
SUM, ,'AREA 1 = ', 4.8 2.4 0.12 45. 0.
GN,+,101
GN,+,102
LF,-,151 201 1 F
LF,-,152 202 1 F
BL,-,151
EN
C.5 BMAT
Activity BMAT and the PTI network loss coefficient program, BMATRIX are no longer supplied with
PSS
E.
C.6 WORK
At PSS
E.
It has been replaced by similar functions in the Spreadsheet View of the Graphical User Interface
(GUI). Chapter 2 of the PSS
E 32.0
XLIS Program Operation Manual
C-26 Siemens Energy, Inc., Power Technologies International
C.7.1 Equipment Status Changes and the Spreadsheet View
In addition to modifying parametric data, the service status of equipment in the working case may
be modified from the Spreadsheet View.
Associated with each ac series branch is a status flag which is initially set to one (for in-service) or
zero (for out-of-service) as specified on the branch data record or in the transformer record block
when a new branch is introduced into the working case with activities READ, Reading Power Flow
Data Additions from the Terminal, or RDCH. The status of a branch may be modified by changing
this flag. Out-of-service branches and their data remain with the case as it is saved and retrieved
with activities SAVE and CASE, and are simply ignored during the execution of other PSS
E activ-
ities such as SOLV or POUT.
If branch status changes isolate a bus, the user must change the bus type code to four. Activities
TREE and OUTS and the power flow solution network connectivity check option (see Section 3.3.3
and activity SOLV) aid the user in identifying isolated buses and islands.
When the specified branch is a member of a multi-section line grouping (see Multi-Section Line
Grouping Data), the same status change is automatically implemented in the working case for all
branches in the multi-section line. In addition, the bus type codes of the dummy buses are changed
to:
The bus type codes of the endpoint buses of the multi-section line grouping are not changed in the
status processing of a multi-section line. As with single section lines, it is the users responsibility to
ensure that branch statuses and bus type codes are coordinated.
When changing the status of a three-winding transformer, status values of 0 through 4 are permitted
(see Transformer Data); the status flags of the three two-winding transformers which comprise the
three-winding transformer are set to the appropriate values. As with multi-section line groupings
and two terminal branches, the bus type codes of the endpoint buses of the three-winding trans-
former are not changed in the branch status processing.
FACTS devices may be blocked in a similar manner. A value of zero for MODE, the control mode
flag, indicates a blocked FACTS device (see FACTS Device Data).
The status of individual machines at a generator bus may be modified by changing the machine
status; plant total power output and power limits are automatically updated following a change of
machine power or status. A plant may be taken out-of-service either by changing the status of all
units at the bus to zero or by changing the bus type code to one or four (this is the recommended
approach because power flow solution activities will run slightly faster). Conversely, for a machine
to be treated as in-service, both its status must have the value one and the bus type code must be
either two or three.
Similarly, the status of an individual load at a bus may be modified by changing its load status, and
the status of an individual fixed bus shunt may be modified by changing its shunt status.
4 When the branch is being removed from service.
1 If the branch is being placed in-service and the bus has no generator data associ-
ated with it.
2 If the branch is being placed in-service and the bus has generator data associated
with it. In this case, the individual machine status flags, which are not changed in
this status processing of multi-section lines, determine which machines are returned
to service.